BMC Control-M Campus Setup Guide 05042004

BMC CONTROL-M Campus Setup Guide

Last Revised:

05/04/04


FINALIZED

REVISION CONTROLDocument Title: Author: File Reference: BMC CONTROL-M Campus Setup Guide CMS Technical Services 81003921.doc

Revision History Date10/02/02 11/05/02 11/11/02

ByBEngravido Bengravido Bengravido

ActionRelease of new document Updates to Job Definition Form, Implementation Tasks & Troubleshooting. Added information to Product and Solution Overview, Production Implementation steps and Change Management Procedures. Added text to New Day Procedure and additional information for sysouts. General Edits Edits and Posting Added and clarified information on Quantitative and Control resources

Pages20-25 5-12, 23-27

11/19/02 11/21/02 01/16/03 04/27/03

Bengravido Bengravido JLussier Pallen

20 All All 16-18

Review/Approval HistoryDate05/04/04

ByGmansoor

ActionReviewed and approved for posting.

PagesAll

Last Revised: 05/04/04


FINALIZED

Table of ContentsPageSection 1 Product and Solution Overview............................................................................................... 1 1.1 Solution Overview..................................................................................................................... 1 1.2 Product Overview...................................................................................................................... 1 1.3 Topology / Configuration Diagram ............................................................................................ 2 1.4 Installation / Configuration Variables......................................................................................... 3 1.5 Work Station Requirements..................................................................................................... 11 1.6 Resource Links........................................................................................................................ 11 Section 2 Security Standards and Naming Conventions........................................................................ 12 2.1 Security and Standards........................................................................................................... 12 2.2 User IDs.................................................................................................................................. 12 2.3 Manageability through Naming Standards............................................................................... 13 2.4 Application Names.................................................................................................................. 13 2.5 Scheduling Table Names......................................................................................................... 13 2.6 Calendar Names...................................................................................................................... 14 2.7 Job Owner................................................................................................................................ 14 Section 3 Campus Implementation Requirements................................................................................ 14 3.1 Sample Project Plan - See Section 6........................................................................................ 14 3.2 Request Access....................................................................................................................... 14 3.2.1 Citrix User Account.................................................................................................. 14 3.2.2 BMC CONTROL-M User Account:............................................................................... 16 3.3 Pre-Production Implementation Steps..................................................................................... 16 3.3.1 Getting Started........................................................................................................ 16 3.3.2 Training................................................................................................................... 17 3.4 Campus Contact Requirement................................................................................................. 18 3.5 Test Methodology/Sample Test Plan........................................................................................ 18 3.5.1 Sample Test Plan See Section 7............................................................................. 18 3.6 Implementation Considerations............................................................................................... 18 3.6.1 Alerts....................................................................................................................... 19 3.6.2 Calendars................................................................................................................. 19 3.6.3 Viewpoints............................................................................................................... 19 3.6.4 Shouts...................................................................................................................... 19 3.6.5 New Day Procedure.................................................................................................. 19 3.7 Production Implementation Steps............................................................................................ 20 Section 4 Production Support................................................................................................................ 23 4.1 Operational Availability........................................................................................................... 23 4.2 Backup and Recovery Options ................................................................................................ 24



FINALIZED

4.3 Trouble Shooting..................................................................................................................... 25 4.4 Change Management Procedures............................................................................................ 25 4.5 CMS Help Desk Procedures...................................................................................................... 26 4.6 Problem Management Procedures........................................................................................... 26 4.7 Operational Procedures........................................................................................................... 27 Section 5 CONTROL-M/EM Job Definition Request Form...................................................................... 28 Section 6 Sample Project Plan............................................................................................................... 29 Section 7 Sample CONTROL-M Test Plan............................................................................................... 31



FINALIZED

Section 11.1

Product and Solution Overview

Solution OverviewThis document will provide the framework and functional overview of the BMC CONTROL-M solution as configured and installed in the Unisys environment. Upon review of the CSU environment, it had been decided to install a separate CONTROLM server and separate ENTERPRISE/Manager server for each campus environment. This decision was prompted for several reasons: Ease of securing each campus environment Allow campuses greater flexibility in defining campus naming standards Allow for complete separation of workload at the CONTROL-M and EM levels

Any nightly or weekend batch window processes in the Salt Lake City data center for which a campus expects monitoring and support must be scheduled via CONTROL-M. This includes SQR, Application Engine and COBOL PeopleSoft processes on Unix, Crystal and Nvision PeopleSoft processes on NT and various NT and Unix scripts such as those that FTP files or backup databases. If a PeopleSoft process is to be under CONTROL-M control, it must be run on a Salt Lake City data center server. CONTROL-M cannot be used to schedule and run client based processes, nor will it be used to control processes run on local campus servers. During non-batch window periods, the Salt Lake City data center will notify the CMS help desk if a processing exception occurs. End users will still be able to run processes they are authorized to run through the PeopleSoft process scheduler and may in fact schedule processes to run at a certain time each day through this scheduler. Each campus will determine the extent to which they want end users to utilize process scheduler to run and schedule processes. A campus may also choose to use CONTROL-M to schedule and run these non batch window processes.

1.2

Product OverviewCONTROL-M is a comprehensive production control system whose purpose is to schedule and submit job processes within the PS applications, monitor and analyze the results of job execution, and perform post-processing actions based on execution results. When fully implemented, CONTROL-M automates normal operations and provides capability for total job production in the data center. Operator or user intervention is required only for unforeseen circumstances and for scheduling exceptional jobs. BMC Softwares ENTERPRISE/Manager enables you to control the job production environment for your entire enterprise from a single workstation. ENTERPRISE/Manager also allows you to view production flow and job dependencies and helps you optimize job production easily and efficiently, even in a cross-platform production environment. ENTERPRISE/Manager is part of the CONTROL-M Production Control System and works together with CONTROL-M on all supported platforms. The ENTERPRISE/Manager GUI runs as a Windows application. Other components of ENTERPRISE/Manager can run on either a Windows computer, or a Unix machine. ENTERPRISE/Manager will provide CSU campuses with a graphical representation of their daily production job flows. Through ENTERPRISE/Manager and CONTROL-M


Page 1 of 27


FINALIZED

campuses will be able to view and monitor their jobs in a real-time graphical environment. Campuses will be able to build, alter, and update their job scheduling definitions with ease and efficiency.

1.3

Topology / Configuration DiagramApplication Profile Separation of workload and the securing of workload are paramount to the implementation of the CONTROL-M and ENTERPRISE/EM. Unisys/BMC have designed a physical and logical environment that separates and secures each campus workload. In a Production Village there are 4 Application Servers, 2 Database Servers, 2 Report Servers and one Admin Server. Unisys has configured and loaded BMC's CONTROL-M software (EM, CONTROL-M, PeopleSoft Agent (7.x and 8.x) and a CONTROL-M agent on each application server. This configuration provides the required isolation to give each campus full control of their batch-scheduling environment without the possibility of accidental external access. Network Diagram


Page 2 of 27


FINALIZED

1.4

Installation / Configuration VariablesThis section provides information regarding each component of the BMC product and how the installation and configuration variables were installed. EM Installation The EM installation is the basic standard software install using an existing Oracle database and the existing Oracle client. Control M Installation The Control M installation is the basic standard software install using an existing Oracle database and the existing Oracle client with the upgrade option where required.


Page 3 of 27


FINALIZED

Solaris Agent Installation The Solaris installation is the basic standard software install or upgrade. NT Agent Installation NT scheduling for 7.X: There is no current support under NT 7.x. The campuses cannot schedule NT jobs in a 7.X environment via CONTROL-M due to a bug in the software that is scheduled for a software upgrade in Jan 2003. NT scheduling for 8.x: Campuses can schedule NT jobs in the 8.x environment via CONTROL-M. ENTERPRISE/Manager A single ENTERPRISE/Manager for each campus will be installed on several UNIX Server platforms implemented with Oracle databases and will connect to the separate CONTROL-M Servers via TCP/IP. Access to each EM will be gained through an EM GUI client running on a Citrix server. CONTROL-M/Server for UNIX Fail-over Unisys has chosen not to do CONTROL-M fail-over and have instead decided to make use of other means to provide redundancy. Some of these include hardware RAID 5 and Software RAID 1 on the disks that contain the database itself. We have moved the databases off the CONTROL-M server, and onto the admin server. We are now using Oracle and standard Oracle tools such at archive redo logs, hot backups, and exports to provide the same redundancy as the production databases. Security Unisys/CSU uses system resources on UNIX and NT to control access to the scheduling systems. Unisys will control access to the EM GUI using Citrix. By providing each campus with their own CONTROL-M and EM environments allows for the following: Each campus has full authority to add, remove, and alter the authority granted to its users Each campus has full access to the creation and alteration of Viewpoints (See Section 3.6.3) Each campus controls naming standards. Unisys/CMS recommends the previously established Application name, Calendar name, or Scheduling table naming standards that are documented in BMC CONTROL-M Job Definition Standards and Naming Conventions, located on the CMS website at:http://cms.calstate.edu/T3_MRpt_JS_Security.asp

CONTROL-M Generic Options for PeopleSoft 7.X & 8.x Configuration Values The following table indicates values that can be altered at time of installation or at run time.Command USER Parameter Description PeopleSoft or database owner username (database access ID).


Page 4 of 27


FINALIZED

CONTROL-M Log

The CONTROL-M log entries are kept for 7 days. If sysouts are needed that are older than 7 days open a CMS help desk ticket and sysouts can be retrieved from system backups. If you do not have a DBA, Admin or Developer access to view sysouts open a CMS help desk ticket indicating which days sysouts the campus needs to review. The New Day Procedure should be set to run at 8am

Log containing a complete audit trail of every significant event occurring in the CONTROL-M production environment.

New Day Procedure

Daily scheduling and housekeeping procedures, which run on the Server platform. The CONTROL-M date is advanced to the next day when this procedure runs. A flag representing a user-specified situation or condition. Submission of a job for execution can be made dependent on the existence of one or more prerequisite conditions. Prerequisite conditions are updated and recorded daily in the Conditions/Resources table, performed by the maintenance job CTMCONTB. Sysout is the output from the specific batch job that has been run in CONTROL-M. Alerts in the CONTROL-M/EM Global Alerts window that have been handle by a user. This means that the job failure or alert has been taken care of. As a new job is handled the oldest job is removed.

Prerequisite Conditions

Any Prerequisite Condition older than 5 days is deleted from the prerequisite condition table. This is determined by the prerequisite condition ODAT.

Sysout

The max days to retain sysouts is 7 days This is set to allow no more than 100 handled alerts in the Global Alert window.

Handled Alerts


Page 5 of 27


FINALIZED

CONTROL-M Options for PeopleSoft 7.X Configuration Values Related Guide(s)

CONTROL-M Option for PeopleSoft 7 Administrator Guidehttp://cms.calstate.edu/T3_MRpt_JS_Security.asp

The following table indicates values that can be altered at time of installation or at run time.Command CBLBINDIR Parameter /cblbin Example: /fs761_19/cblbin Description Drive and directory path for COBOL executables. Environment variable COBDIR is set to this value while running client COBOL processes. If you change this value while logged in to PeopleTools, you must exit and restart PeopleTools. PeopleSoft Process Type (e.g., SQR Report, Crystal). Path to Crystal report files (e.g., %PS_HOME%\CRW). 3 Database name used when logging into PeopleSoft. Number of times to try to connect to the database if failure to connect is due to heavy network traffic. Retry is not attempted after an invalid login or password. Sleep interval, in seconds, between each attempt to connect to the database. Database Server name (required for Informix and Sybase). Database type. Debug off/on switch. Valid values: 0 = off, 1 = on. Default: 0. Update job exit status in PeopleSoft database (if RUNSTATUS is not CANCELLED, SUCCESS or UNSUCCESS). Path to the PeopleSoft home directory. Name of the local host machine. Example: /fs761_19 HOSTNAME Production PeopleSoft Scheduler server Example: csu307 for SB INCLUDE LANGUAGE_CD MEMLIB / opt/apps/bmc/ctmagt/ctm/exe_Sol aris/ 1 Path to the SQR/SQC file. Job default language (i.e., ENG, ESP, FRA, GER, UKE, CNE). Full path of directory where the executable script or batch file resides. Process Scheduler default operating system: 1-Client 2-Windows NT Server 3-N/A 4-

CLASS CRWRPTPATH DBNAME DB_RETRY_MAX

SQR Report

DB_RETRY_SLEEP

2

DBSRVR DBTYPE DEBUG EXIT_STATUS_UPDAT E HOMEDIR

ORACLE 0 Y

/

OPSYS


Page 6 of 27


FINALIZED

Command

Parameter

Description UNIX 5-VMS 6-N/A 7-OS/390 8-Windows NT workstation 9-AS/400. The default operating system is used when a process runs on a Process Scheduler Server. To determine the OPSYS value: 1. Select Use, Process System (from the Process Scheduler), or 2. Use the SQL command: select * from PS_PRCSSYSTEM. Set variable OPSYS in the ctmpsft.env file to the same value.

PRIORITY

MEDIUM

PeopleSoft job priority. Valid values: LOW, MEDIUM, HIGH. Both the Server and Agent handle higher priority jobs first. PeopleSoft Operator ID. PeopleSoft users login with this ID. PeopleSoft Server for CONTROL-M Option for PeopleSoft. Path to SQR executables (e.g., %PS_HOME%\SQRBINW, or /home/sqr/syb/bin for SYBASE on UNIX) Path to the SQR directory. See the SQR SERVER Language Reference.

PSFT_OPRID SERVER SQRBIN

BMC CONTROLM /opt/apps/sqr/4.3.4/ora/bin

SQRDIR SQRFLAGS

/opt/apps/sqr/4.3.4/ora/bin Based on campus, PeopleTool release, and campus. Example: -i/fs761_19/SB/sqr/, /fs761_19/CSUfs/sqr/, /fs761_19/sqr/ -m/fs761_19/sqr/ allmaxes.max -ZIF/fs761_19/sqr/ pssqr.unx -XB

TEMPDIR

/brio/brio/tmp/fin Example: /brio/briosb/tmp/fin

Path to current CONTROL-M/Agent temp directory.

TOOLBIN

Path to PeopleSoft and PeopleTools executables (e.g., %PS_HOME%\bin\client\winx86). SYSADM / opt/apps/bmc/ctmagt/ctm/psft/ Example: / opt/apps/bmc/ctmagt/ctm/psft/ffre prd PeopleSoft database Access ID or database owner. Directory used to access configuration scripts and data.

USER WORKINGDIR

RUN_IMMEDIATE

N

Environment file determines the jobs


Page 7 of 27


FINALIZED

Command

Parameter

Description earliest submission time. If RUN_IMMEDIATE=N (the default), the jobs original submission time is used. If RUN_IMMEDIATE=Y, the job's submission time is set to the current run time.


Page 8 of 27


FINALIZED

CONTROL-M Options for PeopleSoft 8.X Configuration Values Related Guide(s)

CONTROL-M Option for PeopleSoft 8 Administrator Guidehttp://cms.calstate.edu/T3_MRpt_JS_Security.asp

The following table indicates values that can be altered at time of installation or at run time.Name MONITOR_USE_MAX_RETR Y Default Values This parameter is set to NO Definition Yes/No flag for a PeopleSoft job that will check every hour to see if the PeopleSoft job is still running. If this parameter is set to YES, it will make the job end NOTOK when the job has run longer than n amount of hours. Debug level. Valid values: 0 - 5. Set to 0 for production mode (debug messages are not generated). For more information about debug levels, see page 2-11 of the CONTROL-M Option for PeopleSoft 8 Administrator Guide. Name of the host machine on which the Application Server is running. This is set to 1 Maximum hours to monitor a job before returning a NOTOK status. Sleep interval (in minutes) for job monitoring. Yes/No flag that indicates whether to write the status of the monitored job to the standard output file. Process output location. This is set to Default Process output format. See OUTDESTFORMAT on page 2-13 of the CONTROL-M Option for PeopleSoft: Version 8 Administrator Guide. Process output type. See OUTDESTTYPE on page 2-14 of the CONTROL-M Option for PeopleSoft: Version 8 Administrator Guide. PeopleSoft operator ID password. Application Server JSL port number. Process type (for example, SQR Report). PROCLOG directory path. Note: The specified value must end with a directory separator. PSUNX Name of the Process Scheduler Server. See RUNLOCATION on page 2-13 of the CONTROL-M Option for PeopleSoft: Version 8 Administrator Guide.

DBGLVL

This parameter is set to 0

HOSTNAME MONITOR_MAX_RETRY

MONITOR_SLEEP_INTERVA L MONITOR_WRITE_STATUS

This is set to 3 This parameter is set to N

OUTDEST OUTDESTFORMAT

OUTDESTTYPE

This is set to Default

PASSWORD PORT PRCSTYPE PROCLOG

This is encrypted for each operator ID

RUNLOCATION


Page 9 of 27


FINALIZED


Page 10 of 27


FINALIZED

1.5

Work Station RequirementsBase hardware and software needed for desktop machine and the preferred browser: Intel 116 Mhz Intel Windows 98 or newer Mac System 8.6 or newer Disk Space 40 meg. Ram 128 meg Web Browser 0 IE 5.5

Each campus will require connectivity to 4Cnet and an ICA Client. User-id setup requirements: Citrix ID and ECS ID (See section 3.2) Citrix When using the Citrix client if you use a MicroSoft or Logitech mouse/trackball, the user defined mouse profile will be picked up by the Citrix applications. If you use a Kensington mouse/trackball, the Citrix-defined profile rules. This is likely a problem mainly for any lefties (or righties) who need their mouse on the left side of their keyboards. If the pointing device is connected to a USB port, the local settings override Citrix regardless of what type of device it is. If the pointing device is connected to the mouse port on the desktop, the Citrix settings rule!

1.6

Resource LinksThe following BMC User Guides provide additional information regarding the BMC CONTROL-M / Enterprise Manager product. All guides are posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.asp CONTROL-M Desktop User Guide CONTROL-M Enterprise Manager User Guide CONTROL-M Enterprise Manager Administrators Guide CONTROL-M Job Parameter and Variable Reference Guide CONTROL-M Option for PeopleSoft 7 Administrators Guide CONTROL-M Option for PeopleSoft 8 Administrators Guide In addition, BMC maintains a full library of support materials, available at:http://www.bmc.com/supportu/prodlist.cfm


Page 11 of 27


FINALIZED

Section 22.1

Security Standards and Naming Conventions

Security and StandardsCSU campuses having their own environment are autonomous in terms of their applications and security of those applications. Essentially, this means that one campus cannot be allowed to affect another campus' processing. Furthermore, one campus cannot view or access another campus' workload. Each campus has the ability to implement their own security, as required. CONTROL-M contains an integral security system that protects the functionality provided by CONTROL-M against unauthorized use or modification. This security system strengthens the standard UNIX security facility and provides an additional application-level security layer. Using the CONTROL-M security system, it is possible to specify which actions each ENTERPRISE/EM user or CONTROL-M user is authorized to perform. These authorizations are implemented as security checks and verifications every time one of the following actions is attempted: Accessing a scheduling table (to add, delete or modify a job definition) Ordering a job Selecting and submitting a job Commands affecting jobs in the Active Jobs file (e.g., Hold, Confirm, Rerun) Maintenance of CONTROL-M entities (e.g., calendars prerequisite conditions).

The security verifications for these actions are implemented according to the definitions in a database of authorizations. Please see the CONTROL-M/Enterprise Manager Administrator Guide, as posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.asp

2.2

User IDsUser IDs are required to access ENTERPRISE/EM and CONTROL-M. The authorizations given to a user ID allow the user ID to function in the ENTERPRISE/EM environment. The authorizations defined to a user ID restrict the user as to the functions the user may perform and what the user can view. There are 2 major divisions of authorization related to the user ID. group authorizations individual authorizations

Group Authorizations Campuses will be able to define the groups that they will require and the authorization granted to each group. Examples of groups would be operations, production support, and/or development. Group level authorization can be granted to the scheduling tables, calendar names, and actions that can be taken against jobs. Individual Authorizations Security at the user ID level is only required to limit what jobs the user may view and alter. Authorization defined to the user ID will limit the applications that the user


Page 12 of 27


FINALIZED

may access/view. Applications that the user may view will be determined by the two or three character application prefix provided by the campus. Note: An individual user ID will assume the authorization defined to the group that it is added to. Any authorization given to the individual user ID will supercede that of the group. Campuses should consult the CONTROL-M/Enterprise Manager Administrator Guide for information regarding user authorization.http://cms.calstate.edu/T3_MRpt_JS_Security.asp

Through the pilot/CMS project, standards and naming conventions were identified. We recommend the campuses adopt these naming conventions. These standards are documented in BMC CONTROL-M Job Definitions and Naming Standards, as posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.asp

2.3

Manageability through Naming StandardsSeparation of roles and responsibilities within CSU/PeopleSoft and CONTROL-M scheduling environment depends on four pivotal areas defined within ENTERPRISE/EM. The four areas are: application names scheduling table names calendar names job owners

Applying naming standards to each of these areas will provide better manageability. Roles and responsibilities at the campus level (ie system admin, scheduler, operators) can be clearly defined.

2.4

Application NamesApplication names are entered within the definition of a job. Application names define the uppermost structure within ENTERPRISE/EM when viewing jobs. Jobs are viewed first by Application, followed by Group, and finally by the Job itself. By assigning and defining unique Application Names for each campus and securing those Application Names, users are only able to view and alter jobs under that Application. Each campus should define their applications with a two or three-character prefix that relates to the campus. Example: Applications for the San Bernardino campus are prefixed with sb. A San Bernardino campus application should be defined as sb_financial or sb_hrjobs. A Fresno campus application should be defined as fre_ financial or fre_hrjobs. There is no limit to the number of applications that a campus can define. Each campus should use the two or three character identifier associated with their production environment.

2.5

Scheduling Table NamesScheduling tables are where jobs are defined. Each scheduling table represents a grouping of jobs. Access to scheduling tables allows a user to define or alter sensitive data pertaining to jobs.


Page 13 of 27


FINALIZED

Each campus should define their scheduling table names with the two or threecharacter prefix that relates to the campus. Example: Scheduling tables for the San Bernardino campus is prefixed with sb. A San Bernardino scheduling table should be defined as sb_hrprod or sb_fstest. A Fresno scheduling table should be defined as fre_hrprod or fre_fstest. There is no limit to the number of scheduling tables that a campus can define.

2.6

Calendar NamesCalendars are defined to ease the scheduling of multiple jobs with the same date criteria. Within each job definition the user has the ability to select the days of each month of the year in which to schedule a job. This can be a time consuming process if it were required for each and every job. Once a calendar is defined, it can be added to the job and the job will be scheduled by the dates defined in the calendar. Each campus should define their calendar names with the two or three-character prefix that relates to the campus. Example: Calendars for the San Bernardino campus are prefixed with sb. A San Bernardino calendar should be defined as sb_daily or sb_monthly. A Fresno calendar should be defined as fre_daily or fre_monthly. There is no limit to the number of scheduling tables that a campus can define.

2.7

Job OwnerThe Owner field of a job defines the user ID under which the job will be submitted. Once submitted, the job that is executing assumes the authority of the user ID under which it was submitted. HR production jobs will be run as hrpsoft and Financial production jobs will run as fspsoft.

Section 33.1 3.2

Campus Implementation Requirements

Sample Project Plan - See Section 6 Request AccessThere are two types of access required for accessing the BMC/CONTROL-M environment. These included Citrix user accounts and BMC CONTROL-M user accounts. When requesting access a CMS help desk ticket should be opened.

3.2.1 Citrix User AccountCitrix is the solution for application deployment across the CMS Enterprise. The two BMC applications available via Citrix are CONTROL-M Desktop and ENTERPRISE/Manager. Campus users who already have an established Citrix User Account need to request access to CONTROL-M Desktop and Enterprise/Manager via a Service Request ticket to the CMS Central Help Desk.


Page 14 of 27


FINALIZED

Campus users who do not have an established Citrix User Account need to request that one be created via a Service Request to the CMS Help Desk. Access to CONTROL-M Desktop and ENTERPRISE/Manager needs to be specified in this request. The procedure for requesting Users Accounts is documented in Accessing the Technical Environment via Citrix, as posted to the CMS website at:http://cms.calstate.edu/T3_MAccessTechEnv.asp


Page 15 of 27


FINALIZED

3.2.2 BMC CONTROL-M User Account:BMC CONTROL-M User Account is used to access the CONTROL-M environment. Unisys will create the BMC administrator user account for each campus, then the campus administrator has the responsibility for creating all subsequent accounts for their campus. Campuses should consult the CONTROL-M Enterprise Manager Administrator Guide for information regarding user authorization. This guide is posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.asp

3.3

Pre-Production Implementation StepsThe purpose of this section is to provide an overview of requirements or alternatives for pre-production implementation.

3.3.1 Getting StartedImplementation Strategies CSU has taken a phased approach to implementing to CONTROL-M and ENTERPRISE/EM process scheduling. Information should be shared between campuses to facilitate the development of best practices and assist in the transition to a new scheduling tool. While CONTROL-M is a single scheduling tool, how it is used and implemented can differ from campus to campus. Each campus will be required to develop its own implementation plans. The following items are suggestions that may assist in the formulation of individual plans. Analyze Your Environment The current implementation of PeopleSoft and CONTROL-M is centered on the PeopleSoft environment. CSU campuses will need to look closely at what will be converted to CONTROL-M and when. By understanding what will be done and when, campuses can start to plan an implementation strategy. A campus may want to implement a Human Resources schedule prior to their Finance schedule or different parts of each. Converting to the CONTROL-M scheduling system should be an incremental process. When reviewing what will be converted to CONTROL-M, each campus should look to maximize their use of the CONTROL-M automated scheduling system in order to leverage their resources. Any command that is manually entered on a given system can be automated and scheduled with CONTROL-M. Current scheduling practices may include the use of paper schedules where operators enter commands and release jobs on a timed basis. Both of these examples, and more, can be monitored and controlled by CONTROL-M. CONTROL-M is a scheduling system that manages workflow by date, time, resources available dependencies on previous processes, etc. The development and introduction of new PeopleSoft processes is a daily occurrence. Now is the time to start formulating plans for the future implementation of automated process scheduling.


Page 16 of 27


FINALIZED

Develop job flows and document them. Many of the process flows within PeopleSoft are based on previously defined processes executed on a legacy system. Tally all of the processes currently in development and being tested and keep account of what you have. This will be essential for a seamless and trouble free implementation. Be accurate. Decide what PeopleSoft processes must be grouped together to form a logical flow. All of the PeopleSoft processing need not be converted at one time. Implement non-critical flows first. As experience with CONTROL-M and ENTERPRISE/EM is gained, implementation into production can become more aggressive. CONTROL-M is only installed on UNIX and NT machines within the current environment. Anything that can be entered and executed on these machines can be scheduled and monitored by CONTROL-M.

Streamline Your Schedule Whenever possible, the campus should attempt to streamline your schedule prior to implementation. One should attempt to eliminate any dead time through proper scheduling techniques. Try and build schedules that do not use time as a factor in the scheduling of a process. An example of this might be that a process is set to execute at 19:00 because a file that the process requires is produced between 17:00 and 18:30. In this example the process would have a minimum of 30 minutes of waiting and possibly up to 120 minutes if the file arrived immediately. By implementing various CONTROL-M techniques, the time required to execute your batch processes can be reduced. Attempt to schedule by events. When scheduling your processes, invoke the use of From Time sparingly. Use this form of job posting as a last resort. When a file is required before a job can be run use the FileWatcher utility. This utility can wait for a file to be created or deleted and when the file is created or deleted any number of jobs can be posted. Do not wait for events to occur on external systems, make full use of IN and OUT conditions When scheduling your process, invoke the use of Confirm sparingly. Confirm requires manual input from an operator and any manual condition can be missed. Campuses should consult the CONTROL-M/Enterprise Manager User Guide for information regarding FileWatcher, From Time and Confirm". This guide is posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.asp

3.3.2 TrainingExposure to PeopleSoft, CONTROL-M and ENTERPRISE/EM Prior to beginning a conversion to CONTROL-M and ENTERPRISE/EM campuses will be required to obtain a working knowledge of the two products. Both CONTROL-M and ENTERPRISE/EM are powerful and complex scheduling and monitoring tools. The products have been designed to require minimal training to get started. Once users become exposed to CONTROL-M and ENTERPRISE/EM and become more comfortable with their basic operation, users can start to explore more advanced scheduling techniques.


Page 17 of 27


FINALIZED

CSU has adopted the policy of train-the-trainer. BMC Software Professional Services has provided product mentoring to the pilot campuses. Through the pilot implementation a CONTROL-M training plan has been developed. Campuses will need to incorporate time into their project plans to include training. Campuses can also contact BMC Professional Services for onsite product mentoring or chose formal classes provided by BMC. Information on formal classes offered by BMC can be found at: www.bmc.com/education/ Campuses can also reference the BMC Training Guide, as posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.asp

3.4

Campus Contact RequirementWhen the each campus begins implementing Control- M, the campus will need to notify your campus liaison and the CMS help desk with the name of the individual at the campus that will primarily be responsible for the tool.

3.5

Test Methodology/Sample Test PlanPrior to building job schedules within CONTROL-M it is assumed that all jobs or PeopleSoft processes have been exercised within a test environment. By testing the processes to be implemented, campuses can obtain several pieces of the information necessary to the successful scheduling of a job. This information would include: Required parameters to be passed to the process such as a date, control numbers, etc. Amount of time that is necessary to complete the process Prerequisite conditions processes that are required to finish successfully prior to the execution of this job Post-requisite conditions processes that should be triggered by the successful completion of this job Scheduling conflicts processes that should not execute while this process is executing Date dependencies dates when the process should be executed It is possible to connect Test platforms to the Production EM and use the Global Conditions facility to pass Conditions between Production and Test environments if so desired.

3.5.1 Sample Test Plan See Section 7 3.6 Implementation ConsiderationsThis section highlights important implementation considerations for the each campus.


Page 18 of 27


FINALIZED

3.6.1 AlertsAlerts are messages that indicate important information for the CONTROL-M EM user. These messages normally indicate when a problem or exception has occurred for a job controlled by CONTROL-M. All alerts are displayed in the Global Alert Client Alerts Window.

3.6.2 CalendarsCalendars are a collection of dates that are used by CONTROL-M to schedule the ordering of jobs.

3.6.3 ViewpointsHundreds of active jobs may exist in the CONTROL-M/EM database at one time. While it is possible to load and view all jobs in the CONTROL-M/EM window, it is more efficient to focus on certain areas( such as specific CONTROL-M installation) or certain types of jobs(such as jobs that ended with errors) and display them according to specific criteria.

Your view of the CONTROL-M/EM environment can be customized with a userdefined ViewPoint. Each ViewPoint contains the following three components: Collection: Which jobs in the enterprise are loaded into memory Hierarchy: How the selected jobs are displayed Filter: Which jobs are displayed in the CONTROL-M/EM window

3.6.4 ShoutsA Shout message is a message sent to one or more destinations if certain specified conditions exist when a job is executed or completes execution. The destinations for Shout messages can include the CONTROL-M /EM Alerts window, the CONTROL-M log, the system console, terminals, or a specific users.

3.6.5 New Day ProcedureOnce a day, at the time specified by the CONTROL-M system parameter Day Time (starting time of working day), CONTROL-M starts the New Day procedure The New Day procedure performs automatic functions that start a new day under CONTROL-M. This procedure is used as a master scheduler for all CONTROL-M activities. Some of the functions performed by the New Day process are: A new Odate (CONTROL-M date) is calculated based on the system date and CONTROL-M system parameter Day Time A selective cleanup of the Active Jobs file is performed. Jobs that have already executed and ended OK, and jobs whose parameter Max Wait has been exceeded (and are not Held), are erased from the Active Jobs file A selective cleanup of prerequisite conditions is performed Jobs whose scheduling date criteria are met are placed in the Active Jobs file.


Page 19 of 27


FINALIZED

We recommend the New Day Procedure time for CSU be set to 08:00 AM. It should be noted that the New Day time is the time that the date changes within CONTROL-M. For instance, if the date is the 5th of January, the date recognized by CONTROL-M as the 6th of January will not occur until 08:00 AM on the 6th. The actual date in CONTROL-M is not updated until the New Day process occurs. In the previous example, the date in CONTROL-M would continue to reflect the 5th of January until 08:00 AM on the 6th. This must be taken in account when scheduling jobs for the early AM. Jobs that would execute at 03:00 AM would actually be scheduled for the 5th or previous day. For more information, please see the CONTROL-M/Enterprise Manager User Guide, as posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.asp Please note that once the New Day Procedure executes it is a campus responsibility to review and verify that the scheduling tables and jobs are ready for execution.

3.7

Production Implementation StepsBatch processing can conflict with Change Management activities as a result the following procedure must be followed as you are defining jobs to BMC. Quantitative Resources must be set up in CONTROL-M before any jobs can be defined. Setup requirements and responsibilities are as follows. CONTROL-M SETUP ( Pre-Setup for each CMS Control-M Implementation. No action required.) Quantitative Resources named H_MAX_RUN (for HRSA) and F_MAX_RUN (for Finance), both with a value of 9999, must be setup in CONTROL-M. See Section 5-1 of the CONTROL-M Job Parameter and Variable Reference Guide, as posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.asp A Quantitative Resource is a variable that is normally used for resources such as tape drives. This procedure uses this variable to turn batch processing on or off. Control Resources named H_RUNNING_JOBS (for HRSA) and F_RUNNING_JOBS (for Finance) are created at runtime in CONTROL-M. See Section 5-1 of the CONTROL-M Job Parameter and Variable Reference Guide, as posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.asp A Control Resource is a variable that is normally used to represent a resource such as a database. This procedure uses this variable to ensure no conflicting jobs are running at the time of the Change / Maintenance window. JOB DEFINITIONS (Done by the Campus) All campus jobs must be defined as requiring one Quantitative Resource. At the time of job execution, CONTROL-M will go out and check for 1 available resource to satisfy the job requirement. If the resource is found, the job will run, if not found, the job will not run. Campuses can manipulate the value of the


Page 20 of 27


FINALIZED

Quantitative Resources at any time (via a job or manually). Setting the value to zero will prevent any jobs from starting. Setting the value to 9999 will allow jobs to start. It is the responsibility of the campus to ensure no jobs are executing at the scheduled time of the Change / Maintenance window. All campus jobs must be defined as requesting shared use of the Control Resource. This is done by setting the type value of the Control Resource to S in the job definition. SETUP OF CONTROL JOBS 1, 2, 3 AND 4 (Done by Unisys) After the campus has setup the Quantitative Resources and the Control Resources, three Control Batch Jobs need to be set up by Unisys. Control Job #1 is executed at the beginning of the Change / Maintenance window to ensure that no new batch jobs can start. Control Job #2 is executed immediately following Control Job #1 to verify there are no batch jobs currently executing that could conflict with the Change / Maintenance tasks. Control Job #3 is executed at the end of the Change / Maintenance window to notify CONTROL-M that batch processing can resume. Control Job #4 checks the value of the Quantitative Resources. All jobs are found in the UN_MAINT scheduling table. Control Job #1 H_Zero_MAX_RUN and F_Zero_MAX_RUN Control Job #1 sets the value of the appropriate Quantitative Resource to zero. (This is the on-and-off switch and a value of zero prevents any new job from starting.) The campus to set the value of the Quantitative Resource to zero can use this job. Control Job #2 H_Check_for_Running_JOBS and F_Check_for_Running_JOBS Control Job #2 will enter the system requiring exclusive use of the appropriate Control Resource. Since all batch jobs were defined to require shared usage of this resource, Control Job #2 cannot run concurrently with any other job. If Control Job # 2 executes, it means that it no other jobs for Finance or HRSA are running. If Control Job # 2 fails to start, it means that some other job is running using the Control Resource. If this occurs, either the job that is executing must be cancelled, or the Change/ Maintenance activities must wait for the job to finish or be re-scheduled. Control Job #2 is the verification mechanism that ensures no jobs are running It is the responsibility of the campus to make sure no jobs are running by using Control Job #2. It is also the responsibility of the campus to take action if they find that jobs are running. Control Job #3 H_Reset_MAX_RUN and F_Reset_MAX_RUN As the last step of the Change / Maintenance activity, Control Job #3 is executed and sets the value of the appropriate Quantitative Resource to 9999. This allows the batch cycle to resume. Unisys will execute Control Job #3 at the end of each Change / Maintenance. Control Job #4 H_Check_MAX_RUN and F_Check_MAX_RUN Control Job #4 checks the value of the Quantitative Resources. The output is put in the sysout for the job.


Page 21 of 27


FINALIZED

ORDER OF EXECUTION The following is the sequence of processing: 1) 2) 3) 4) Batch Processing - Campus Batch Processing halted by setting the appropriate Quantitative Resource to zero (Control Job #1 can be used for this)- Campus Verification that no jobs are running (Control Job #2 can be used for this) Campus Change / Maintenance window - Unisys (a) (b) 5) Change / Maintenance tasks Control Job #3

Batch Processing resumes - Campus

To Review: Setup StepsThe following are the setup steps to be done by the Campus or Unisys for this procedure.

1) Campus Sets up a Quantitative Resource named H_MAX_RUN and onenamed F_MAX_RUN, both with the value of 9999 in CONTROL-M

2) Campus Sets up a Control Resource named H_RUNNING_JOBS and onenamed F_RUNNING_JOBS in CONTROL-M.

3) Campus Defines each job to use "1" of the appropriate 9999 QuantitativeResources upon execution.

4) Campus Defines each job to require "shared" use of the appropriate ControlResource.

5) Unisys builds a job that sets the value of the appropriate QuantitativeResource to 0.

6) Unisys builds a job that sets the value of the appropriate QuantitativeResource to 9999.

7) Unisys builds a job that requests exclusive use of the appropriate ControlResource.

The following table represents implementation tasks that the campus should complete during the beginning stages of their implementation.

Implementation Tasks 1. 2. 3. 4. Determine whom the BMC security administrator will be and request via CMS help desk ticket for a BMC Security Admin user id and password. PeopleSoft security administrator on campus needs to create a BMC user id and profile. BMC campus security administrator needs to create a user-id and password for Unisys. Request a Citrix id and password via a CMS help desk ticket.


Page 22 of 27


FINALIZED

5. 6. 7. 8. 9.

BMC/Sys Admin passwords need to be encrypted by CMS Central. Open a CMS help desk ticket. Determine who and what groups will be working within the CONTROL-M product. Define BMC security user ids and groups. Identify all jobs that will be scheduled thru BMC by application. Develop processing Calendars Complete job definition request form on all jobs to be processed through CONTROL-M. Naming conventions for the job definition form should be campus_application_job_date. Once completed they must be submitted to CMS Central via a CMS help desk ticket. (See Section 5) Develop process flow chart by daily, weekly, monthly, quarterly and annual processing. Develop job dependencies/pre-requisites. Develop test job stream to be tested in the non-production environment.

10. 11. 12.

Section 4

Production Support

This section will provide campuses with information regarding operational availability, backup and recovery procedures, troubleshooting techniques, change management procedures, CMS help desk procedures, problem management procedures and operational procedures.

4.1

Operational AvailabilityAvailability will be 24 x 7 x 365 with the exception of scheduled maintenance, which will be coordinated with the campus. For more information, please refer to the following documents on the CMS website: http://cms.calstate.edu/T4_MHelpDesk.asp - Standard and after-hours problem resolution and escalation procedures. - Problem management procedures http://cms.calstate.edu/T3_MOperationalStatusRpts.asp - Data center service level agreement


Page 23 of 27


FINALIZED

4.2

Backup and Recovery OptionsBMC Backup Procedures BMC starts at system boot time and runs 24x7. Software is backed up during the normal nightly OS backup, which begins at 22:00 hours, system time. The Oracle databases are backed up during the normal Oracle hot backups and begin at 02:05 hours for production each night. All backup data is copied to tape beginning at 08:00 hours system time the following morning for normal distributions including offsite recovery. Recovery Procedures There are five (5) pieces to the CONTROL-M product and they are listed below including impacts if any: Citrix Applications EMGUI EMGUI is used to monitor the active scheduling environment. It enables the campus to modify the active environment ie, rerun or delete a job. Scheduled jobs will continue to execute but the campus will be unable to view and monitor the processing. Log information and job history is continuing to be collected during this failure. If failure occurs contact the CMS help desk for resolution. The campus-scheduling administrator for job setups, defining calendars, and scheduling tables etc uses CTM DESKTOP. If the CTM DESKTOP fails users cannot create new or make perm modifications to job calendars, tables, etc. This would not affect pre-existing job definitions or job schedules all pre-existing processes would execute as defined.

EM Server EM Server is the service that communicates with the EMGUI and DESKTOP. If for any reason that service is not operational, the above noted functions of the EMGUI and DESKTOP would not function. CONTROL-M Server CONTROL-M Server is the engine that drives all scheduling activities. If this service should fail no jobs would be executed. The campus could still create new jobs, make permanent changes to existing jobs, (etc), but no jobs would execute through the CTM server until service was re-established. If the CMT server is down for extended period time, the campus may consider running outside of CTM. CONTROL-M Agent CONTROL-M Agent is the interface between CONTROL-M and the application you are processing. If the CONTROL-M Agent fails the campus will be unable to execute jobs in that application. Option for PeopleSoft configured for specific database instances. If the option fails the campus will no longer be able to run jobs thru CONTROL-M on the database instance. Jobs in execution at time of failure will attempt to run and will end at notok. If any of the above scenarios occur, campuses should report the problem to the CMS Help Desk.


Page 24 of 27


FINALIZED

4.3

Trouble ShootingWhen troubleshooting BMC problems, please refer to the CONTROL-M Desktop User Guide and CONTROL-M/Enterprise Manger User Guide, as posted to the CMS website at: http://cms.calstate.edu/T3_MRpt_JS_Security.aspDescription of Problem Steps to Take Toward Resolution

BMC/CONTROL-M: Operator is unable to access Control- M and has no response from system.

"YOUR TERMINAL SERVICES TEMPORARY LICENSE WILL EXPIRE IN 14 DAYS."

1. Log into the Citrix server 2. Launch ESC Gui application 3. Log into EM 4. Select file Open View point 5. Select all jobs in the new window 6. Select tools Order/Force 7. In new window select test job 8. CONTROL-M = the CONTROL-M to be tested 9. Table = Table with test job 10.Job = the test job itself 11.Click order 12.Watch for job to run 13.If it turns Green all is ok and BMC is operational. 14.If it turns Red a CMS help desk ticket should be opened. Refer to section 4.5 (Problem Management Procedures) for information that must be provided to the help desk when opening a ticket. 1. Open REGEDIT.EXE. On your Windows desktop click Start and then Run. Type REGEDIT.EXE in the open field and hit enter. 2. Find the following registry entry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLice nsing\Store

3. Remove any LICENSE0000 and LICENSE001 entries in the Store folder. 4. Reboot the PC After completing the steps above and rebooting the PC the license message should be gone. If the same problem appears notify the CMS help desk for resolution. Refer to the CONTROL-M/Enterprise Manager User Guide, as posted to the CMS website at:http://cms.calstate.edu/T3_MRpt_JS_Security.asp

Error Messages

4.4

Change Management ProceduresEach campus is responsible for notifying CMS/Unisys via a CMS help desk ticket for any changes to nightly processing schedule. Changes to your environment must go through the Change Management Process. For example, if you change a job dependency, job run time, create a new job, or make any other change to the environment after it has been turned over to Unisys to monitor, the change MUST go


Page 25 of 27


FINALIZED

through the Change Management Process with a new Job Definition Form submitted via the CMS Help Desk. Unisys shall monitor CSU-provided schedules including job initiation and job completion as agreed upon via the change control procedure. Unisys will develop and document specific change management procedures, which cover scheduling, setup, dependencies, initiation, and recovery processes. Unisys shall be responsible for adhering to campus-defined documentation concerning job recovery/restart procedures. Unisys will provide batch-processing support for CONTROL-M 24 hours a day 7 days a week. Please see the document Change Management Procedures, as posted to the CMS website at: http://cms.calstate.edu/T3_MAccessTechEnv.asp

4.5

CMS Help Desk ProceduresThe CMS Help Desk should be contacted whenever there is a problem using BMC/CONTROL-M. The CMS Help Desk may be contacted via phone, email, or through opening a Help Desk ticket directly through the CMS Help Desk tracking system.

Standard Business Hours Monda yFriday (562) 951HELP 7:00 AM - 7:00 PM

After Hours Monda y Friday (562) 951HELP 7:00 pm to 7:00 am and Weekends cmshelp@calstate. edu

cmshelp@calstate. edu

Documents outlining the CMS Help Desk Operations are posted to the CMS website at: http://cms.calstate.edu/T4_MHelpDesk.asp

4.6

Problem Management ProceduresThe purpose of Problem Management Procedures is to ensure that management is aware of any problems affecting the production environment and that prompt and timely action is taken to resolve the issue and provide a means for allocating appropriate resources to ensure maximum systems availability and end-user computing services. This procedure outlines the workflow and accountabilities related to managing resolution of a problem and appropriate problem escalation, no matter where the identification of a problem originated. A problem is defined as an operational, environmental, network or application related deficiency that causes the respective system not to function as it was originally intended or designed. A production problem, by definition, means that the application, system or systems component is not operating as it is designed to, and may potentially have impact to business operations and/or service level agreements, therefore it must be addressed with a high degree of urgency and focus.


Page 26 of 27


FINALIZED

The CMS Help Desk system is to be used to document and manage the resolution of any problem affecting or potentially affecting the production environment. The CMS Problem Management Procedures are located on the CMS website at: http://cms.calstate.edu/T3_MAccessTechEnv.asp There is specific information in reference to BMC/CONTROL-M that the campus user should have before they contact the CMS Help Desk. The campus user should have answers to the following questions when they contact the CMS Help Desk: What is the job name? Which CONTROL-M or EM server? On which node id is the job running? On what instance was the job running? When was the job supposed to have run? What, if any, error message did you get? To what is the owner field of the job? Has the job run successfully before? If so has anything changes since then? What status does the job show in EM?

4.7

Operational ProceduresWhen a campus job exception or error occurs Unisys will perform the following instructions. 1) Unisys will review the Job Definition Form for instructions on how to proceed. 2) If needed, Unisys will contact the CMS help desk and a Help Desk ticket will be opened. 3) If needed, the CMS help desk will notify the campus contact to discuss the issue and resolution. 4) Unisys staff will not restart any BMC jobs unless requested to do so.

5) If needed, CSU campus will inform the CMS help desk of the status of the jobwithin a pre- defined timeframe. 6) If needed, CMS help desk will inform the Unisys help desk of status of the job once they have been notified by the campus. 7) Unisys will perform recovery/restart instructions as applicable. The CMS help desk ticket will remain open until the campus confirms that the issue is resolved or will not be addressed at that time.


Page 27 of 27


FINALIZED

Section 5Date: __________

CONTROL-M/EM Job Definition Request FormSubmitted by: __________ Reviewed by: _____________

Contact Information: __________________________________________ext:____________ Process Name: _____________________________ Oracle SID: (Jobname)

_____________________________ (DB Instance name, eg. fsbprd)

Process Type: ______________________________ Run Control ID:________________ Server Name: Schedule: _____________________________ (hostname of process server) From Time: ___________ Till Time: ___________

Time to complete: __________

Contact: ____________________________

Dates (MM/DD): _________________________________________________________ Days: __________________________ Weekdays________________________________ Months: Jan __ Feb __ Mar __ Apr __ May __ Jun __ Jul __ Aug __ Sep __ Oct __ Nov __ Dec __ Calendar: ____________________ Priority: _________ Cyclic: Y/N Prerequisite Jobs (In Conditions): ______________________________________________________________________ Post Jobs (Out Conditions): _______________________________________________________________________ not ok Condition: Action/Instructions to be Taken: Delete ________________________________________________________________________ late sub Condition: Action/Instructions to be Taken: Confirm _______________________________________________________________________ late time Condition: Action/Instructions to be Taken: Confirm


Page 28 of 27


FINALIZED

_______________________________________________________________________

Section 6

Sample Project Plan

ID 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

Task Name CONTROL-M ECS Release 6.10 Q7 - Front Door Process - Project Mobilized Product and Solution Overview * Set up working meetings Deliver Campus Setup Guide Q6 - Requirements Distributed/Defined High Level System Topology * Q5 - System Security Requirements Work Station requirements and setup if required User-ids Formal request to Help desk Setup user-ids for Citrix Setup user-ids for EM Q4 - Environments Designed (Research and Detail Design) Unisys Operational Readiness Information Q3 - Test Planning, Design, Documentation, Training Backup/Recovery Plan Training Identify individuals to be trained Training agenda walk through Training class Q2 - Site Acceptance/Deployment Help Desk Requirements Application Manageability Checklist Product Installation & Testing Campus testing CR - Implementation Change Request for test Install CONTROL-M software on DC Server Install EM software on EM server

Duration Resource Name 24.75 days 5.25 days 1 day 1 day 1 day 1 day 1 day 2 days 2 days 2 days 1 day 1 day 0.5 days 1 day 1 day 5.5 days 1 day 3.5 days 1 day 0.5 days 2 days 14.5 days 1 day 1 day 14.5 days 14.5 days 1 day 1 day 1 day Unisys Unisys Unisys CMS/ Unisys Unisys Campus CMS CMS/Campus Unisys Unisys CMS Unisys Unisys/Campus Campus Unisys Unisys Unisys CMS


Page 29 of 27


FINALIZED

30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49

Configure Gui, GAS, Gateway, GCS Install and configure agents and PeopleSoft options on dev Load component interface and set passwords as required Test Configuration Build Calendars, triggers etc on test bases Test job scheduling Q1 - Readiness Review (Go / No go) Q1 review Go\No Go Q0 Production Campus Go Live CR - Issue change request for production cutover Install and configure agents and PeopleSoft options on prod Load component interface and set passwords as required Cutover to production databases Change node id of jobs Change environment variable to correct Oracle SID Change Oracle SID Validate production environment Back out (if required) Project Closure and Lessons Learned Session

1 day 1 day 1 day 1 day 5 days 3 days 1 day 1 day 5 days 4 days 1 day 1 day 1 day 1 day 1 day 1 day 1 day 1 day 1 day 1 day

Unisys Unisys CMS Campus Campus Campus Unisys/CMS

Unisys Unisys CMS

Campus Campus Campus Campus Unisys Unisys/CMS


Page 30 of 27


FINALIZED

Section 7

Sample CONTROL-M Test Plan

Sample CONTROL-M Test PlanTest1. 2. 3. 4. 5. 6. 7. 8. 9. 10 . Sign-on to CONTROLM Create a calendar Schedule a job Schedule a job with a job dependency Schedule a job with a time dependency Schedule a string of jobs

How to TestSign-on to CONTROL-M using issued user-id and password Create from the calendar definition window a calendar for a specific job After creation of a calendar execute the job process Execute a job process and its dependency processes Execute a job with a time dependency Execute a series of job processes

Expected ResultsSuccessfully sign on into CONTROL-M A successful creation of a scheduling calendar Successful completion of a job A successful completion with a job dependency A successful time dependent job completion Multiple jobs complete successfully


Page 31 of 27