IBM Global Services Australia

MVS Production Support

a joint venture with Lend Lease and Telstra

Production CONTROL-M Standards

IBM Global Services Australia

PRODUCTION MANAGEMENT GROUP

CONTROL-M STANDARDS

Document Owner: Production Management
Group Manager – Lance Wright
Document Author: Bruno Cimiotti
Business Unit: Enterprise Services
Technical Support
Department: Production Management Group –
Application Management
Mailing address: 18 Winterton Road
Clayton Vic 3168
Voice: + 61 (03) 9253 0727
Email: bruncimi@au1.ibm.com
Total Pages: 35
Document Version: 5.0
Print Date: 30/03/14

This document contains proprietary information. ALL INFORMATION CONTAINED
HEREIN SHALL BE KEPT IN CONFIDENCE. None of this information shall be
divulged to persons other than IBM Global Services employees authorised by the
nature of their duties to receive such information, or individuals or organisations
authorised by IBM Global Services in accordance with existing policy regarding release
of company information.

G:\Prodsupp\standard\PASTMPS.DOC
For Internal IBM GSA Use Only
Enterprise Services

Page 1
Printed 30/03/2014

IBM Global Services Australia
MVS Production Support

a joint venture with Lend Lease and Telstra

Production CONTROL-M Standards

Document Control
Issue No

Issue Date

V3.0

January 1996

V3.1

September 1997

V3.2

August 1998

V4.0

September 1998

V5.0

June 2001

Nature of Amendment
Major revision
Manual IN condition to hold jobs;
General Revision
Annual review of document & Update.
Major Revision.

G:\Prodsupp\standard\PASTMPS.DOC
For Internal IBM GSA Use Only
Enterprise Services

Page 2
Printed 30/03/2014

IBM Global Services Australia
MVS Production Support

a joint venture with Lend Lease and Telstra

Production CONTROL-M Standards

Contents
1.0

1.0 INTRODUCTION.....................................................................................................................................4
1.2 CREATION OF CONTROL-M PRODUCTION BATCH USERID...............................................................4
1.3 FORMAT OF CONTROL-M PRODUCTION BATCH USERID .................................................................4
2.0 JOB SCHEDULING DEFINITIONS STANDARD.........................................................................................5
DAYS, WDAYS, DCAL, WCAL & CONFCAL......................................................................................8
MONTHS...................................................................................................................................................9
MAXWAIT................................................................................................................................................9
2.8 AUTO-ARCHIVE.................................................................................................................................13
2.10 SYSOUT REDIRECTION..................................................................................................................15
2.11 ABEND CODES CAPTURE.................................................................................................................16
2.12 CONTROL-R SUITABILITY & STANDARDS....................................................................................18
SUITABILITY...........................................................................................................................................18
STANDARDS..............................................................................................................................................19
2.13 SHOUT...........................................................................................................................................20
ABBREVIATED SHOUT PARAMETERS......................................................................................................22
3.0 GROUP SCHEDULING STANDARD.......................................................................................................23
3.2 STANDARDS AND CONSIDERATIONS..................................................................................................23
4.0 MIGRATION & CONTROL-M LIBRARIES STANDARD..........................................................................26
5.0 NEW DAY PROCESSING STANDARD...................................................................................................29
.................................................................................................................................................................30
5.2 TELSTRA STANDARD FOR NEW DAY PROCESSING.............................................................................30
6.0 CONTROL-M UTILITIES......................................................................................................................31
COPY OF JCL AVAILABLE ON VI2 – ‘IVPSUPP.CTMFLOW.CNTL(LASER)’...................................32
6.2 MAYBE UTILITY..............................................................................................................................33
WHERE DESIRED OR NECESSARY, THE ABOVE UTILITY MAY BE SET-UP TO ADD CONDITIONS FOR THE
CURRENT OR SPECIFIC ODATE. IN WHICH CASE, THE FOLLOWING CODING WILL APPLY: ....................34
7.0 APPENDIX A......................................................................................................................................35

G:\Prodsupp\standard\PASTMPS.DOC
For Internal IBM GSA Use Only
Enterprise Services

Page 3
Printed 30/03/2014

A 'MVS Userid Details' form must be filled out and signed by the Application Project Manager (and submitted to the Operations Security Group) to request for the userid creation. This form requests for the creation of a surrogate profile and the relevant Control-M datasets. See Appendix A for an example of the form.DOC For Internal IBM GSA Use Only Enterprise Services Page 4 Printed 30/03/2014 .2 Creation of Control-M Production Batch USERID A Production Batch USERID has to be created for EACH application running under Control-M. For more in depth details and examples how to use the many ControlM/R features. Should there be a requirement to deviate from any of the standards mentioned in this document. This document is to be used in conjunction with the ‘OS/390 Applications Batch Scheduling Standards Document’.3 Format of Control-M Production Batch USERID The Production Batch USERID will be created in the following format: PSaaann where: PS = Production Support aaa = Abbreviation of Application Name nn = two digits number Once the userid created.0 Introduction 1. G:\Prodsupp\standard\PASTMPS. consult the Control-M/R User Manual as supplied by the vendor.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 1. a 'Request For Control-M Access For Production' form needs to be filled out by the Production Management Group representative and forwarded to Operations Security and then to the Batch Software Support group. 1.1 Scope The purpose of this document is to outline the standards to be followed by the Production Management Group when building new jobs or jobflows within the Control-M Production environment. PRIOR approval must be obtained from either the respective Team Leaders or the Manager of Production Management Group. 1.

Format: Application Name-Table name For Example: TIPPS-TIPMUTIL G:\Prodsupp\standard\PASTMPS.CNTL.  MEMLIB Refers to the dataset where the job JCL is stored. Must be unique for every Applications and ONLY be defined and set-up to submit jobs on PRODUCTION Lpars.  GROUP Should be unique for each application. Format: TPIOA.0 Job Scheduling Definitions Standard 2.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 2.1 Application & Job Specific Definitions MEMNAME QTIPUT20 MEMLIB TPIOA.  APPL Refers to the name of the application (eg: TIPPS).RUNBOOK  MEMNAME Normally coded with the same name as the ‘JOBNAME’ within the JCL (job card). .D%%ODATE OWNER PSTIP01 TASKTYPE JOB PREVENT-NCT2 APPL TIPPS GROUP TIPPS-TIPHR DESC BACKUP CUSTOMER ORDER FILE OVERLIB SET VAR %%SYMVARXX=VARPROD CTB STEP AT NAME TYPE DOCMEM QTIPUT20 DOCLIB TPIOA.application name.TIPPS. There may be specific instances where this field may be set to Y (yes) but great care must be taken to ensure that you want Control-M to automatically delete datasets when performing a RESTART.CNTL.  PREVENT-NCT2 This field should be left blank to pick up the default of NO for preventing Not Catalog 2 abends.TIPPS.JOB (for the standard batch job/jcl submitted).  TASKTYPE The two most common values coded for this field are: .CYC (for a cyclic job submitted).D%%ODATE  OWNER Refers to the Control-M batch userid.DOC For Internal IBM GSA Use Only Enterprise Services Page 5 Printed 30/03/2014 .

In the example illustrated above.in this example all ‘% %PRD’ references within the JCL will be substituted to ‘2PRD1’. as follows: EDIT TPIOA. the ‘SET VAR’ statement within the ‘Job Scheduling Definition’ is pointing to a member called ‘VARPROD’.  Within all the JCL members belonging to the Application. All job schedules must have a description in this field. // REGION=0M In the above JCL at run time the value ‘%%SYMVARXX’ will be substituted to ‘VARPROD’.TIPPS.application name.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards  DESC Refers to a description on the job’s function.01.TIPPS. However.DOC For Internal IBM GSA Use Only Enterprise Services Columns 00001 Scroll ===> HALF Page 6 Printed 30/03/2014 . // CLASS=%%HIGH.TIPPS.'TIPPS'.  In turn.OVRD For Example: TPIOA. Coded in a free form text format up to 50 characters in length.CNTL %%MEMSYM %%SYMVARXX //* //%%JOBPREF%%. Useful for running one off version of production JCL.00 00072 Command ===> 000012 %%JOBPREF = QTIP 000013 %%MSGCLASS = 4 000014 %%ACCOUNT = QTIPPS000 G:\Prodsupp\standard\PASTMPS. must be removed prior to next scheduled production run to avoid reference being made again to this one off version.CNTL’ will contain all the variable values. Eg: SET VAR %%PRD=2PRD1 . The ‘LIBSYM’/‘MEMSYM’ will be a PDS (dataset) that will house all the variables values. the ‘VARPROD’ member within the LIBSYM ‘TPIOA.OVRD  SET VAR Is used to substitute user defined variables within the JCL at job submission time. Format: TPIOA. // MSGCLASS=%%MSGCLASS.SC06 JOB (%%ACCOUNT). For those Applications using extensive variable substitutions within their JCL. the following is defined as ‘LIBSYM’ and ‘MEMSYM’: //* %%LIBSYM TPIOA. it is recommended to use a ‘LIBSYM’ and a ‘MEMSYM’ to store all the variables values. // MSGLEVEL=%%MSGLEVEL. For Example: BACKUP CUSTOMER ORDER FILE  OVERLIB Refers to the JCL library name that overrides the MEMLIB field.TIPPS.CNTL(VARPROD) .

 DOCLIB Refers to the library name in which the DOCMEM mentioned above resides Format: TPIOA. This member will also contain the actions to be taken by the operator when the job is running/submitted late. as an Endevor package).RUNBOOK G:\Prodsupp\standard\PASTMPS.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards One of the main advantages the above offer is the ability to migrate the ‘VARPROD’ member in production as part of the migration tool and methodologies being used by the Customer or Application (eg.  DOCMEM Refers to a member within the ‘DOCLIB’ containing the Restart/Recovery and/or escalation instructions for when the job abends. NOT used in OUR environment. The name is normally the same as the ‘MEMNAME’ (unless it is a generic runbook used by a number of jobs).DOC For Internal IBM GSA Use Only Enterprise Services Page 7 Printed 30/03/2014 .application name.  CTB STEP AT Is used for CONTROL-B definition.

3.Y 6. run job Monday to Friday. 6 for Friday. 2.Y 10.Y 11.Y 8. WCAL & CONFCAL The above fields are used to specify ‘when’ (date) the intended job is to be scheduled (run). G:\Prodsupp\standard\PASTMPS. & 0 for Saturday.2 Calendar Scheduling Criteria’s Definitions DAYS DCAL * WDAYS MONTHS AND/OR 2.e.g.3. for Control-M set-up on the Telstra Account) is: 1 for Sunday. In the above example the job will run MON-FRI (i.Y 12.4. It is important to note that if any entry is made within the ‘CONFCAL’ field that the ‘DCAL’ & ‘WCAL’ fields are commented with an ‘*’. 5 for Thursday.Y 2.PROD. if more than one calendar name is used within the table.Y 9.Y 3.).Y DATES CONFCAL TIPFRIMN SHIFT MINIMUM PDS RETRO N MAXWAIT 03 D-CAT  DAYS.CAL’. Failure to do so will cause jobs NOT to be scheduled. However. the user can create its own user defined calendar.e.6 WCAL * 1. 4 for Wednesday.DOC For Internal IBM GSA Use Only Enterprise Services Page 8 Printed 30/03/2014 . 3 for Tuesday. it must be prefixed with the Application acronym. DCAL.6). Note: All user defined calendars are stored in one central library – ‘TPIOA. 2 for Monday.4. In the above example a user defined calendar of ‘TIPFRIMN’ has been created. The default for ‘WDAYS’ (i.5. The recommended naming standard for ‘CONFCAL’ is to code it the SAME name as the Control-M schedule (table) member name. every Sunday. last day of the month etc.Y 7.Y 5. For simple run criteria it is recommended to use the ‘DAYS’ or ‘WDAYS’ option (e. WDAYS.Y 4. Refer to the Control-M User Manual for a detail explanation how to use the different combinations of the DAYS and WDAYS options. By so doing it reduces the need to maintain and create new calendars at/before year-end.IOA. For more complex run criteria.5.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 2.

the potential increases for the AJF to become full and this may lead to problems. depending on the Customer or Application requirements. G:\Prodsupp\standard\PASTMPS.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards  MONTHS This field refers to the months the job will be scheduled. A ‘Y’ entry means the job will be scheduled to run on the given month and a ‘N’ or blank means the job will not be scheduled  RETRO The recommended standard is to code this field as ‘N’. This is highly unlikely in our current environment!  MAXWAIT This field refers to how long a job in ‘Wait Status’ will be kept in the AJF after being loaded either manually or at/by the new day processing. The recommended standard is to code at least ‘3’ (for 3 days).DOC For Internal IBM GSA Use Only Enterprise Services Page 9 Printed 30/03/2014 . All other fields must be left blank. If selected (ie. However. Normally applicable to control situations where the computer has not been working for a day or more. ‘Y’) it will set the job to run if the original date has passed. It is important to note that the longer and the more jobs are kept in the AJF. this figure might vary.

). G:\Prodsupp\standard\PASTMPS.  Other values that can be used instead of ODAT are as follows : . the following are the two MANDATORY in-conditions that are to be included on all jobs: . in event of a major problem). Note:  The ‘ODAT’ parameter will be automatically replaced by the current ‘Original Scheduling Date’ when the job is loaded into Control-M for execution.LPAR-ddd-AVAIL STAT . The ‘STAT’ parameter is used. as those conditions are NOT date dependant and therefore not deleted as part of the daily Control-M housekeeping. As illustrated in the above example.  JOB In-Condition The following is the standard for coding job in-condition: . 30 minutes before the IPL the conditions can be deleted to stop any further jobs from being submitted and thus being cancelled in mid-flight.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 2.DOC For Internal IBM GSA Use Only Enterprise Services Page 10 Printed 30/03/2014 .PREV: job's previous scheduled date.'ddd' is the LPAR where the job is EXECUTING.JobName-Table Name-OK ODAT .‘Table Name’ is the name of the Control-M Table the job resides in – must NOT be more than 6 character long. . It can also be useful for the Operators/Operations Analyst before scheduled IPL are performed .OK02 etc.APPLIC-name-AVAIL STAT where: .'name' is the name of the Application the job belongs to.JobName-Table Name-OKnn ODAT where: . The main purpose of having the above two conditions is to allow the flexibility to quickly STOP any further batch jobs from being submitted by simply deleting the two conditions (eg. .nn = is a two numeric digit to be used if the job is running more than once within the same flow – (ie.3 IN-CONDITION Definitions IN LPAR-NI2-AVAIL QTIPBK01-TIPHR-OK STAT ODAT APPLIC-TIPPS-AVAIL QTIPSR06-TIPHR-OK STAT ODAT  MANDATORY In-Condition This field refers to any Prerequisite Conditions that are to be satisfied before the job can run. This may prevent any further and unnecessary abends as soon as problems are identified.OK01.eg. in the 1st run it will be set as …. the 2nd run ….

producing an in-condition) for a downstream application. the following is the standard to be adopted: aaaaaaaa-nnnnnn-OK ODAT where: aaaaaaaa = application name nnnnnn = the Task No.****: .Ddmm: . the following is the standard to be adopted: Application Name-Job Name-OK ODAT where: Application Name = the name of the application SENDING the data or adding the condition.STAT: Production CONTROL-M Standards date and month of schedule date.  INTERFACE In-Condition If the application is interfacing (ie. Important: when using the ‘PREV’ option. requesting the manual hold or name of the person that will request the job to be released. BOTH the job and the job it is dependent on MUST have run on the previous date for the conditions to be satisfied. G:\Prodsupp\standard\PASTMPS.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra . any schedule date. any schedule date.$$$$: . job’s next schedule date. as explained above.  MANUAL In-Condition In circumstances where a MANUAL hold is required on a job.DOC For Internal IBM GSA Use Only Enterprise Services Page 11 Printed 30/03/2014 . Job Name = the Job Name that is creating the data for the downstream application.NEXT: .

If an application has a special requirement. Exemption lists exist where specified conditions are ignored and therefore NOT deleted.6 RESOURCE Definitions (Quantitative & Control) CONTROL REORG-FLEXCAB E RESOURCE BACKUP-FLEXCAB-TAPE 0003 Both the Quantitative and Control resources must include the Application Acronym as part of the name to make identification and ownership easier – as illustrated in the example above. Conditions are deleted from the Condition & Resource File by the Control-M Administrator.DOC For Internal IBM GSA Use Only Enterprise Services Page 12 Printed 30/03/2014 .on the 2nd run it will produce the following ‘out-condition’: JobName-Table Name-OK2 ODAT + and so on. G:\Prodsupp\standard\PASTMPS. Currently the deletion is run once a week as part of the ‘newday’ processing. contact the Control-M administrator to define the special business need.I – Housekeeping of Condition & Resource File As part of the regular housekeeping. the following is the standard to be adopted: . where any condition older than 6 days (or up to 15 days on certain Control-M) are deleted. 2.Y. 2.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 2.on the 1st run it will produce the following ‘out-condition’: JobName-Table Name-OK1 ODAT + .5 F.4 OUT-CONDITION Definitions OUT QTIPUT20-TIPHR-OK ODAT +  JOB Out-Condition The same standards as per the ‘in-condition’ will be applicable JobName-Table Name-OK ODAT + Should a job run more than once within a given table.

If it is ok for the application to run any left over jobs on the next scheduled odate (ie. This will avoid the unnecessary manual intervention and speed up batch jobs restart.MAXRERUN 8 RERUNMEM STEP RANGE FR (PGM. after midday).DOC For Internal IBM GSA Use Only Enterprise Services . 2.8 Auto-Archive AUTO-ARCHIVE Y SYSDB SYSOUT OP (C.R) Y MAXDAYS MAXRUNS FROM  AUTO-ARCHIVE This field controls SYSDATA archiving.D. RERUN . A/O Page 13 Printed 30/03/2014 .N. CODES U0034 INTERVAL 015 TO .IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 2.F. It allows the user to decide whether or not to archive SYSDATA. The standard is to code ‘Y’ (for ‘yes’). 2. In the above example the job will be submitted at 21:00 hrs. if step ‘BACKUP’ fails with code ‘U0034’.9 Automatic Restart It is recommended that wherever possible an automatic rerun is invoked for batch abend .  SYSDB This field archives SYSDATA of all jobs to a common data set. The standard is to code ‘Y’ (for ‘yes’).  In the example below.eg.7 Run TIME Definitions TIME: FROM 2100 UNTIL > The ‘FROM’ field dictates the time (if required) the job will be submitted for processing.PROC) ON PGMST BACKUP PROCST DO RERUN DO G:\Prodsupp\standard\PASTMPS. an automatic rerun will be performed after an interval of ‘15’ minutes. The ‘MAXRERUN’ will be initiated ‘8’ times unless the step ends with a user code other than U0034. for data transmission failure. Control-M by default will NOT allow/submit the job to run. It is important to note that if by 12:00 (midday) on the next day the job has not run. then the greater than sign ‘>’ as indicated in the above example must be coded in the ‘UNTIL’ field.

If any other step fails. Only when this status code is posted do we issue the SHOUT command.MAXRERUN 1 RERUNMEM INTERVAL ON PGMST ANYSTEP PROCST CODES EXERR DO IFRERUN FROM $EXERR . The following is an example how to automatically rerun a job and use Control-R to change the value of a variable in the restart: SET VAR %%CYL=50 RERUN .IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards  The DO SET control statement can be used to alter variables before the job is rerun.  With an Automatic job Restart. then *REC0 must be coded (see example below). the job will have to be manually restarted by the Operations Analyst and the value of %%CYL remains at 50. If the jobs fails in step ‘CREATE’. A/O The initial SET VAR statement sets the value of ‘%%CYL=50’.SYSID=VI2 G:\Prodsupp\standard\PASTMPS. if only one shout message is required for multiple abends. TO DO ON PGMST CREATE PROCST CODES SB37 DO SET VAR= %%CYL=100 DO RERUN 1 NEXT TIME A/O CONFIRM N . it is automatically rerun once after a ‘1’ minute interval and with a value of ‘100 for %%CYL’. ON PGMST ANYSTEP PROCST CODES *REC0 DO SHOUT TO U-ESO URGENCY V = ALERT=Y. *REC0 will determine if a rerun is needed but no more reruns are available.SEVERITY=4.DOC For Internal IBM GSA Use Only Enterprise Services A/O Page 14 Printed 30/03/2014 .PROBLEM=Y. In other words. only the last rerun will raise an alert if the job fails.

CODES ***** TO . .OPT C: will change the output class of the job's SYSOUT.  ON PGMST The standard is to code ‘ANYSTEP’ – this identifies the actions Control-M needs to take (as specified in the subsequent ‘DO’ statements) when the job steps completes. .  CODES The standard is to code ‘*****’ . G:\Prodsupp\standard\PASTMPS.  DO SYSOUT This is the ‘DO’ statement instructing Control-M what to do with the SYSOUT of the completed job. .PROC) ON PGMST ANYSTEP PROCST DO SYSOUT OPT N PRM VIL DO SYSOUT OPT R PRM DO SYSOUT OPT C PRM 4 DO .DOC For Internal IBM GSA Use Only Enterprise Services Page 15 Printed 30/03/2014 .IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 2.PRM 4: will place the SYSOUT in a new output class (‘4’ in the above example). A/O FRM FRM FRM H  STEP RANGE This field contains a number of DO SYSOUT statements which must be defined to allow Control-M to pass the SYSOUT of the job to the relevant Output Management System (eg. .FRM H: instructs Control-M that the output class is being changed (from ‘H’ in the above example).this causes the actions defined in the subsequent ‘DO’ statements to be applied to the job whether it completes processing normally or abnormally. OMCS).OPT N: will change the destination of the SYSOUT .OPT R: will release the SYSOUT from being held (when Control-M receives the SYSOUT it always places it in the held status) .PRM VIL: will place the new system ID (‘VIL’ in the above example) on the SYSOUT of the job so that it is routed to the required Lpar.10 SYSOUT Redirection STEP RANGE FR (PGM.

11 a joint venture with Lend Lease and Telstra Production CONTROL-M Standards Abend Codes Capture The standard is for ALL Application JCL to be ‘self-sufficient’ and have appropriate condition code checking included in them. By so doing this will automatically insert the failed Step Name in the restart window that is invoked by the Operators/Operations Analyst .CONTROL-M ACTIVE ENVIRONMENT ----------------------(3) COMMAND ===> SCROLL===> CRSR O NAME OWNER ODATE JOBNAME JOBID TYP --------. Therefore.CONTROL-M ACTIVE ENVIRONMENT ----------------------(3) COMMAND ===> SCROLL===> CRSR O NAME OWNER ODATE JOBNAME JOBID TYP --------. it will increase maintenance and coding. Note: If Control-R CANNOT be used when restarting the job. STEP01 | | TO STEP . The following is the recommended standard when coding new job definitions: ON PGMST ANYSTEP DO IFRERUN PROCST FROM $EXERR .ie.DOC For Internal IBM GSA Use Only Enterprise Services Page 16 Printed 30/03/2014 . | | RECAPTURE ABEND CODES (Y/N) | | RECAPTURE COND CODES (Y/N) | | STEP ADJUSTMENT (Y/N) | | RESTART PARM MEMBER NAME QREB2440 | +--------------------------------------+ Example 2: WITH CONTROL-R FILTER: ----.STATUS ----------.| | FROM STEP . Example 1: WITHOUT CONTROL-R FILTER: ----. the JCL condition code will dictate when the job should complete successfully or unsuccessfully.UP QREB2440 PSREB01 030998 QREB2440/10334 JOB ENDED "OK" R QREB2450 PSREB01 140998 +--------------------------------------+ ====== >>>>>>>>>>>>>>>>>>> | JOB QREB2450 WILL BE RERUN | <<< ====== | PLEASE CONFIRM (Y/N) | | WITH RESTART Y (?/Y/N) | | ---------------------------------. | | TO STEP . A/O CONFIRM N In the above it is indicating for Control-R to restart the job from the step which failed. CODES EXERR TO . then DO IFRERUN must be omitted and the runbook must clearly state that this job is not Control-R restartable.UP ====== >>>>>>>>>>>>>>>>>>>> TOP OF ACTIVE JOBS LIST <<<<<<<<<<<<<<<<<<<< ====== R QREB2440 PSREB01 030998 +--------------------------------------+ QREB2450 PSREB01 140998 | JOB QREB2440 WILL BE RERUN | ====== >>>>>>>>>>>>>>>>>>> | PLEASE CONFIRM (Y/N) | <<< ====== | WITH RESTART N (?/Y/N) | | ---------------------------------. when they are performing a manual restart. See examples below.| | FROM STEP DELETE . | G:\Prodsupp\standard\PASTMPS.IBM Global Services Australia MVS Production Support 2.STATUS ----------. Should the Control-M definition screen be used to perform ‘condition code checking’.

A selection can be made from this list…. R QREB2450 PSREB01 140998 +--------------------------------------------+ | COMMAND ==> | | O Num Pgm-stp Proc-stp Pgm= Comp | | 001 DELETE STEP01 IEFBR14 C0000 | | 002 STEP02 IEBGENER C0000 | | 003 STEP03 IEBGENER C0000 | | 004 IOATEST STEP04 IOATEST C0080 | | 005 IOATEST STEP05 IOATEST C0000 | | 006 STEP06 IEBGENER C0000 | | 007 STEP07 IEBCOPY C0008 | | 008 STEP08 IKJEFT01 C0000 | | 009 STEP99 ABEND999 FLUSH | | | | Opt: F From T To O Only | +--------------------------------------------+ G:\Prodsupp\standard\PASTMPS.DOC For Internal IBM GSA Use Only Enterprise Services Page 17 Printed 30/03/2014 . a further window is displayed which will list all of the available restart steps within the job.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards | RECAPTURE ABEND CODES (Y/N) | | RECAPTURE COND CODES (Y/N) | | STEP ADJUSTMENT (Y/N) | | RESTART PARM MEMBER NAME QREB2450 | +--------------------------------------+ If a “?” is entered in the ‘WITH RESTART’ field.

Check the runbook for the correct restart action. then do not use Control-R. Every stepname must be unique.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 2. The default value for STEP ADJUSTMENT is Y.A backward reference in the VOL= field will cause Control-R to adjust the restart step to prevent a JCL error. .As a general rule any jobs with a backward reference in the VOL field must be studied to determine if the restart step adjustment matches the restart action as described in the runbook. Every step must have a unique name.A backward reference in the DSN= field is OK and does not require restart step adjustment.  Missing stepname A null stepname will also cause the Control-R step to fail.DOC For Internal IBM GSA Use Only Enterprise Services Page 18 Printed 30/03/2014 . . A checkpoint restart will not be very successful with an empty checkpoint dataset so ensure that GDG’s or DISP=NEW are not used for checkpoint datasets or else preallocate them in a previous step and subsequently refer to them as generation 0 or DISP=SHR.  DISP=MOD Any jobs which writes to a dataset with DISP=MOD probably has to restore the dataset before restarting or else risk duplicate records. The following are the issues that must be considered when using Control-R:  Duplicate stepname A duplicate procstep.  PGM=FTP The EXEC statement must include PARM=‘(EXIT=8’) otherwise a condition code of 0 is always returned and Control-R will not know if the FTP has ended successfully or not. but this must be clearly specified in the runbook if the Operations Analyst are to set this to ‘N’.  GDG usage Control-R will use the same generations as the original job.12 CONTROL-R Suitability & Standards Suitability Control-R may or may not be suitable for some jobs or Applications. Control-R will delete it so that it can be reallocated in the restart. If a new input GDG generation is to be used or the project team do not want the output generation to be scratched and reallocated. Control-R will delete this as part of it’s GDG adjustment processing and this also applies to any checkpoint dataset referred to as DISP=NEW.A backward reference in the PGM= field will not cause Control-R to adjust the restart step but a JCL error will occur.  Backward references .  Checkpoint restarts Some applications use a GDG(+1) as the checkpoint dataset.pgmstep name will cause the Control-R step to fail. .There is a restart option in the Control-R confirmation window which will disable step adjustment. G:\Prodsupp\standard\PASTMPS. .

& 4 will be bypassed..... the job skips all steps and ends OK... To get around this problem.. the condition code will be retrieved from STEP1 and applied to the IF statement. //IF1 IF (STEP1. In this example. The default value for RECAPTURE CONDITION CODES is ‘Y’.. Control-R will restart the job from STEP2 provided RECAPTURE CONDITION CODES is set to N. G:\Prodsupp\standard\PASTMPS. PGM=.. the ‘IF statement’ must be coded with the specific stepname to which it applies: Eg. therefore it must be clearly specified in the runbook if the Operations Analyst are to change the value to ‘N’. therefore STEP2. See the following example: //STEP1 EXEC PGM=.STEP1 = //STEP2 EXEC //STEP3 EXEC //STEP4 EXEC // ENDIF PGM=.... Control-R appears to retrieve CC=0080 from STEP4 and applies this value to the IF1 statement thereby determining that steps 2 to 6 must not be run. ‘errors’ in restarts might occur. PGM=..3... //IF2 IF (RC LE 8 OR RC = 80) THEN //STEP5 EXEC PGM=.. //IF1 IF (RC = 0) THEN //STEP2 EXEC PGM=. //STEP3 EXEC PGM=. Control-M thinks that the job ended successfully with a condition code 0 in all steps that were executed and releases the next job. As the Control-R step has executed and finished with condition code 0.RC = 0) THEN  Bypassing failed steps using Control-R Exercise caution if attempting to use Control-R for restarts where the resolution is to skip the failed step and continue from a subsequent step. 0) THEN PGM=. Ends with CC=0008 If STEP1 has a condition code of 8 and the job is restarted from STEP2 using Control-R.IBM Global Services Australia a joint venture with Lend Lease and Telstra MVS Production Support Production CONTROL-M Standards Standards  It is important to note that when processing COND or IF/THEN/ELSE statements that are not stepname specific.. //STEP6 EXEC PGM=. //STEP4 EXEC PGM=.. //IF2E ENDIF //IF1E ENDIF Ends with CC=0000 Ends with CC=0000 Ends with CC=0000 Ends with CC=0080 This is OK Ends with CC=0000 Ends with CC=0008 Error When Control-R tries to restart from STEP6.DOC For Internal IBM GSA Use Only Enterprise Services Page 19 Printed 30/03/2014 ... See the following example: //STEP1 EXEC // IF (RC. There is a restart option in the Control-R confirmation window that will determine if condition code recapture is performed or not. If there is condition code checking in the jobstream there may be situations where a job will have a status of ENDED OK but none of the job steps have executed apart from the Control-R step.

PROBLEM=Y. SYSID=NI2 This will instruct Solve Operations to: 1) raise an alert.LATE=EXEC V In the above example Solve Operations will generate an alert if the job hasn't finished executing by 0600.13 SHOUT SHOUT information is used to prompt the automation tool (Solve Operations) to automatically issue alerts and generate Problem Dockets.SYSID=NI2.SEVERITY=4.  SHOUT WHEN EXECTIME >n Shout a message if the execution time is greater than a specified time period.SEVERITY=4. after initial submission (see example below).SYSID=NI2 URGN V The following are valid parameters for the ‘SHOUT WHEN’ field:  SHOUT WHEN NOTOK Shouts a message everytime the job ends with an error code. Examples SHOUT WHEN LATE 0600 TO U-ESO URGN MS ALERT=Y.  MS ALERT=Y.  SHOUT WHEN LATESUB Shout a message if the job has not been submitted by the specified time (see example below).DOC For Internal IBM GSA Use Only Enterprise Services Page 20 Printed 30/03/2014 .  URGN V This will instruct Control-M that the message is ‘very urgent’ and to send it immediately.TEXT='message' . 3) make the severity of the problem docket 4 and 4) the system ID NI2 – this refers to the lpar where the job is executing. PROBLEM=Y. SHOUT WHEN NOTOK TO U-ESO MS ALERT=Y. G:\Prodsupp\standard\PASTMPS.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 2.PROBLEM=Y. 2) generate a problem docket.this can be used to send messages to the operator. ALERT=Y.  TO U-ESO This will instruct Control-M to shout the message to the automation tool – Solve Operations.  SHOUT WHEN LATE Shout a message if the job has not finished after a specified period of time – ie. Higher severity number can be allocated for critical jobs.SEVERITY=n.SEVERITY=4.

SHOUT WHEN EXECTIME > mmm TO U-ESO URGN MS ALERT=Y.LATE=SUB V In the above example Solve Operations will generate an alert if the job hasn't been submitted by 2100.PROBLEM=Y.SYSID=NI2.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards SHOUT WHEN LATESUB 2100 TO U-ESO URGN MS ALERT=Y.SYSID=NI2.PROBLEM=Y.nnn TO U-ESO URGN MS ALERT=Y.SEVERITY=4.SYSID=NI2.LATE=EXECTIME V In the above example Solve Operations will generate an alert if the job finishes executing within mmm minutes The examples illustrated below shows shout parameters that depend on the existence of job statistics for the job in question.PROBLEM=Y.SEVERITY=4. SHOUT WHEN EXECTIME . SHOUT WHEN EXECTIME PARAMETER IGNORED SUB133I JOB TESTSHEX TESTSHEX/11591 SUBMITTED SPY254I JOB TESTSHEX TESTSHEX/11591 SCANNED SEL208I JOB TESTSHEX TESTSHEX/11591 ENDED "OK" SHOUT WHEN EXECTIME + nnn TO U-ESO URGN MS ALERT=Y. This shows shout parameters being ignored due to missing job statistics. 180394 112544 170394 IV04557 180394 112548 170394 IV04557 180394 112554 170394 IV04557 180394 112809 170394 IV04557 180394 112814 170394 IV04557 SEL203I JOB TESTSHEX ELIGIBLE FOR RUN SUB1A7I JOB TESTSHEX MISSING JOB STATISTICS. See example log statements below for job 'TESTSHEX'.LATE=EXECTIME V In the above example Solve Operations will generate an alert if the job elapsed runtime is nnn minutes more than its average elapsed runtime.PROBLEM=Y.SEVERITY=4.SYSID=NI2.SYSID=NI2. SHOUT WHEN EXECTIME < mmm TO U-ESO URGN MS ALERT=Y.PROBLEM=Y.SEVERITY=4. the shout command won't work and an error message will be sent to the log file.LATE=EXECTIME V In the above example Solve Operations will generate an alert if the job total elapsed runtime is nnn minutes less than its average elapsed runtime.SEVERITY=4. G:\Prodsupp\standard\PASTMPS.LATE=EXECTIME V In the above example Solve Operations will generate an alert if the job hasn't finished executing within mmm minutes.DOC For Internal IBM GSA Use Only Enterprise Services Page 21 Printed 30/03/2014 . If the job has not run before.

SHOUT WHEN NOTOK TO U-ESO URGN V MS ALERT=Y.SYSID=B01.TEXT=‘TEST MSG’ The above parameters can be abbreviated to: SHOUT WHEN NOTOK TO U-ESO URGN V MS ALERT=Y.PRI=7.SEV=3.PRIORITY=7. Both the abbreviated form and full form of these parameters are accepted in these fields.DOC For Internal IBM GSA Use Only Enterprise Services Page 22 Printed 30/03/2014 .IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards Abbreviated SHOUT Parameters The Solve Operations/Control-M interface has been modified to accept abbreviations of the SHOUT parameters SEVERITY and PRIORITY to allow more space for TEXT messages.PROBLEM=Y.SEVERITY=3.SYSID=B01.PROBLEM=Y.TEXT=‘TEST MSG TEST MSG TEST’ G:\Prodsupp\standard\PASTMPS.

the main restriction is that Conditions will only be adjusted (satisfied automatically) if the jobs are from the same group.IBM Global Services Australia MVS Production Support 3. This table must be created with the Group attribute as specified in the entry panel. is created. G:\Prodsupp\standard\PASTMPS. must first be converted using the utility CTMBGRP. Jobs that are to be handled as a group (this includes their scheduling. called a Group Entity. a special scheduling definition. The Group Entity is used to define job processing criteria for the group as a whole. See the Control-M User Manual for more details. the use of the Group Scheduling Facility is recommended.2 Standards and Considerations Standards GROUP ENTITY naming standard: Application Name-Table Name Eg: FLEXCAB-BILLING SCHEDULE TAG naming standard: Application Name _ meaningful run criteria Eg: FLEXCAB_MON_FRI Considerations  Any scheduling changes (eg.0 3. 3. do not run the flow on Friday) can be simply made and controlled via the ‘SCHEDULE TAG’ in the Group Entity). Refer to the Control-M User Manual for more information.  Any Application schedules/tables that have been created in the ‘normal’ fashion but would like to start using Group Scheduling. submission and post-processing) must be defined in their own scheduling table called a Group scheduling table.  Using the option ‘ADJUST CONDITIONS’ in the Group Entity is an alternative to using the ‘IOALDNRS’ and ‘ADDMNCND’ utilities. At time of creation of a Group scheduling table.DOC For Internal IBM GSA Use Only Enterprise Services Page 23 Printed 30/03/2014 . However. With batch runs that contain a large number of batch jobs.1 a joint venture with Lend Lease and Telstra Production CONTROL-M Standards Group Scheduling Standard Overview Defining Scheduling Tables as 'Group Scheduling' is another option that may be suitable and used when defining the Application under Control-M. It does not allow the flexibility for job dependencies (conditions) across different flows but within the same application to be managed using this method.

Y 4.Y 9.Y 10.Y 2.DOC For Internal IBM GSA Use Only Enterprise Services Page 24 Printed 30/03/2014 .Y 7.Y 10.Y 11.Y 2.Y 2.RUNBOOK | | =========================================================================== | | SCHEDULE TAG FLEXCAB_MONTHLY | | DAYS L01 DCAL | | AND/OR A | | WDAYS 1 WCAL | Run:Last day of | MONTHS 1.FLEXCAB.Y 4.Y 7.Y 12.Y 11.3.4.Y 5. Example of a Control-M flow using Group Scheduling Group Entity & Schedule Tag DEFINITIONS: | GROUP FLEXCAB-BILLING MEMMNAME FLEXCAB | | OWNER IV04702 | | APPL FLEXCAB | | DESC GROUP SCHEDULING FOR TIPPS | Group Entity | ADJUST CONDITIONS Y | | SET VAR | | DOCMEM FLEXCAB DOCLIB TPIOA.Y 8.5.Y 6.6 WCAL | | MONTHS 1.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards  Individual jobs from within a table cannot be manually ordered when using Group Scheduling.Y 6.  The Group Entity can be used to add a condition or force another table/job on completion of ALL the jobs within the table.Y | | DATES | | CONFCAL SHIFT RETRO N MAXWAIT 00 | | =========================================================================== | The idea behind the Group Scheduling concept is for individual jobs within the actual jobflow to refer to the one Group Entity and Schedule Tags as defined above.Y 9.  The Group Entity cannot be ‘DELETED’ or ‘FORCE OK’ from the AJF.Y | month is Sunday | DATES | | CONFCAL SHIFT RETRO N MAXWAIT 00 | | =========================================================================== | | SCHEDULE TAG FLEXCAB_MON_FRI | | DAYS DCAL | | AND/OR | Run:Monday-Friday | WDAYS 2. they will need to be ‘forced’ in. | MEMNAME QFCBSTRT MEMLIB DUMMY | | OWNER IV04702 TASKTYPE JOB PREVENT-NCT2 | G:\Prodsupp\standard\PASTMPS.Y 3.Y | | DATES | | CONFCAL SHIFT RETRO N MAXWAIT 03 | | =========================================================================== | | SCHEDULE TAG FLEXCAB_WEEKLY | | DAYS DCAL | | AND/OR | Run:Friday | WDAYS 6 WCAL | | MONTHS 1.Y 12. Instead.Y 11.Y 4.Y 12.Y 5. In the example below job QFCBSTRT is referring to the Schedule Tag – ‘FLEXCAB_MON_FRI’.Y 9.Y 7.Y 8.Y 8.Y 10.Y 6.Y 5.Y 3.Y 3.

Y 9.Y 10Y 11.Y 3.Y 5.Y 6.IBM Global Services Australia MVS Production Support | APPL a joint venture with Lend Lease and Telstra FLEXCAB Production CONTROL-M Standards GROUP FLEXCAB-BILLING | | DESC JOB TO INDICATE START OF THE BILLING FLOW | | OVERLIB | | SET VAR %%SYMVARXX=VARPROD | | SET VAR | | CTB STEP AT NAME TYPE | | DOCMEM QFCBSTRT DOCLIB TPIOA.Y | | DATES | | CONFCAL SHIFT RETRO N MAXWAIT 00 D CATEGORY | | MINIMUM PDS | G:\Prodsupp\standard\PASTMPS.DOC For Internal IBM GSA Use Only Enterprise Services Page 25 Printed 30/03/2014 .Y 2.Y 12.Y 8.FLEXCAB.Y 7.RUNBOOK | | ============================================================ =============== | | SCHEDULE TAG FLEXCAB_MON_FRI ← | | SCHEDULE TAG | | RELATIONSHIP (AND/OR) O | | DAYS DCAL | | AND/OR | | WDAYS WCAL | | MONTHS 1.Y 4.

DOC For Internal IBM GSA Use Only Enterprise Services Page 26 Printed 30/03/2014 .D%%ODATE.START.application name.DISP=SHR //* //STEP30 EXEC PGM=IEFBR14 //SYSUT1 DD DISP=(OLD. // SPACE=(CYL. // DCB=TPIOA.PREPROD (staging library used to make any changes or park any work currently in progress) Refer to the ‘CTMSCHED.START.SCHEDULE.SCHEDULE.0 4.START.TPIOA.'START' //* %%SET %%DSNDEL=%%CALCDATE %%ODATE -4 //* //STEP10 EXEC PGM=IEFBR14 //SYSUT1 DD DISP=(NEW. TPIOA.START. It also recommended for a back-up copy of the Application Schedule Library (ie.START.DISP=SHR //SYSUT2 DD DSN=TPIOA. A separate Migration Control-M Table must be set-up with jobs to migrate the relevant components.RLSE).2 Schedule Libraries The following is the naming standard for Applications Schedule Libraries: .CATLG).SCHEDULE.SCHEDULE (library from which jobs are ordered from and referred to by the User Daily) .TPIOA.(5.application name.SCHEDULE.UNIT=GENUSER.D%%ODATE.DSN=TPIOA. The golden rule that must be adhered to is that NO Production job must be activated to run in Control-M unless a valid JCL and Runbook member has been reviewed and migrated into their respective libraries as described below.SCHEDULE. 4.TPIOA.SCHEDULE //* //STEP20 EXEC PGM=IEBCOPY //SYSIN DD DUMMY //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=TPIOA.1 a joint venture with Lend Lease and Telstra Production CONTROL-M Standards Migration & Control-M Libraries Standard Migration to Production All migrations to the Application Production environment must be done under the control of Control-M.application name.D%%DSNDEL /* G:\Prodsupp\standard\PASTMPS.MASTER (master library containing the CURRENT version of all the production flows) .1.DOC’ document for the process to be followed when making any updates to the Application Control-M Schedules libraries.50). The following is a sample JCL to perform this function: //QSTASCHD JOB IQCASQE000. // DSN=TPIOA.application name.IBM Global Services Australia MVS Production Support 4.DELETE).SCHEDULE.SCHEDULE) to be taken daily prior to start of business hours.

D%%ODATE’ dataset must be created at midday everyday as part of the New Day processing.CNTL.CNTL. To ensure consistency across Applications.'CREATE JCL DSN' //* %%SET %%DSNDEL=%%CALCDATE %%ODATE -5 //CREATE EXEC PGM=IEFBR14 //SYSUT1 DD DISP=(NEW.D940124 The above set-up allows the Operations Group to edit the JCL if required but only affect the Current batch run of the application and not any future runs.5.DISP=SHR //* //DELETE EXEC PGM=IEFBR14 //SYSUT1 DD DISP=(OLD.3 a joint venture with Lend Lease and Telstra Production CONTROL-M Standards JCL Library All JCL that are executed by the Application within its Control-M Production environment are done so from the following library: TPIOA.application name.RSLE).applname. // DSN=TPIOA.(10. // SPACE=(CYL.CNTL.UNIT=GENUSER.applname.DELETE). the ‘D% %ODATE’ value will be substituted to the current scheduling date of Control-M. // DSN=TPIOA. // DCB=TPIOA.CNTL.application name.D%%ODATE.CNTL) to the Odate JCL Library as described above.CNTL. then the JCL dataset when loaded into Control-M will be: TPIOA.applname.IBM Global Services Australia MVS Production Support 4.applname. the following is the recommended naming standard for this JCL copy job: QaaaCNTL (where aaa = abbreviation of the application name) //QaaaCNTL JOB acctcode. Creation of the D%%ODATE JCL dataset The ‘TPIOA.CNTL.D%%ODATE When jobs are ordered into Control-M for processing.D%%ODATE.applname.application name.DOC For Internal IBM GSA Use Only Enterprise Services Page 27 Printed 30/03/2014 .CNTL.DISP=SHR //SYSUT2 DD DSN=TPIOA.D%%DSNDEL //* An explanation of the JCL: G:\Prodsupp\standard\PASTMPS.DCB //* //COPY EXEC PGM=IEBCOPY //SYSIN DD DUMMY //SYSPRINT DD SYSOUT=* //SYSUT1 DD DSN=TPIOA.application name.500). When the Application flows/jobs are initially set-up under Control-M a Job/JCL (see below) must also be created to enable all JCL to be copied from the Master JCL Library (TPIOA.CATLG). For Example: if the current ODATE of Control-M is 940124.

 Step COPY will copy all JCL members… From: ‘TPIOA.5 RUNBOOK Library The naming standard for the Runbook Library is as follows: TPIOA.D%%ODATE’  Step DELETE will delete the JCL dataset that is 5 day old.RUNBOOK G:\Prodsupp\standard\PASTMPS.  Step CREATE will create a new JCL dataset to be used for the current processing day. This means that the JCL dataset will be kept for 5 days before the oldest generation is deleted (by the DELETE step).application name.CNTL’ To: ‘TPIOA.application name. 4.4 OVERRIDE Library The Override library may be used to store and execute one off version of current production JCL.application name.OVRD 4. The naming standard for this library is as follows: TPIOA.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards  %%SET statement will give a value to the %%DSNDEL. In the above example a value of 5 will be given.DOC For Internal IBM GSA Use Only Enterprise Services Page 28 Printed 30/03/2014 .CNTL.application name.

SCHEDULE(STAALLDY) // DD DISP=SHR.START.START. The naming standard is as follows: UDaaaDLY were: aaa = abbreviation of the application name/acronym The following is a sample JCL for a User Daily: //UDSTADLY JOB (IQCASQE000). The User Daily allows Application tables (jobflows) to be automatically selected and loaded into the Control-M AJF at new day processing.START.DATEREC=UDSTADLY //DAJOB DD DISP=SHR.SCHEDULE(STAJCOPY) // DD DISP=SHR. The naming standard for this table is as follows: USRDLYS Within the above table individual User Daily members will be created for the Application (in most cases one User Daily per application will suffice). //* //PRD EXEC CTMDAILY.'START USER DAILY'.DSN=TPIOA.SCHEDULE(STACALDR) // DD DISP=SHR.1 Application User Dailies All Applications set-up to run under Control-M must have at least one User Daily created for it.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 5.START.DSN=TPIOA.0 New Day Processing Standard 5. //* THERE MUST BE ONE DATE RECORD MEMBER PER USER-DAILY.DSN=TPIOA.DSN=TPIOA. G:\Prodsupp\standard\PASTMPS. //* //* DD DAJOB(CONCATENATED) POINTS TO THE SCHEDULE TABLES.DOC For Internal IBM GSA Use Only Enterprise Services Page 29 Printed 30/03/2014 . The standard is for a separate Control-M Table to be created for the User Daily.SCHEDULE(STADAILY) /* Note: It is recommended that due to the critical nature of the User Daily. it is set-up to generate a Problem Docket with a Severity of 3 for any failures/abends. //* //* DD DACHK POINTS TO THE MEMBER OF THE DATE RECORD.CLASS=H //* //* THIS USER DAILY WILL ORDER IN JOBS SCHEDULED //* TO RUN FOR THE NEXT 24 HOUR PERIOD.

Due to the above. the following consideration is to be noted: Normal calendar days 00:00 31/10/95 1/11/95 11:59 12:00  23:59 00:00 1/11/ 95 ODATE days 2/11/95 23:59 11:59 12:00 2/11/95  The top box represent normal calendar days and the lower box represent a Control-M ODATE day. To have a job run at 08:00 2/11/95. it must be defined (within the Control-M Calendar) as ODATE 20:00 1/11/95.IBM Global Services Australia MVS Production Support 5. G:\Prodsupp\standard\PASTMPS.2 a joint venture with Lend Lease and Telstra Production CONTROL-M Standards Telstra Standard for New Day Processing The current standard for Telstra Control-M New Day Processing is from MIDDAY to MIDDAY.DOC For Internal IBM GSA Use Only Enterprise Services Page 30 Printed 30/03/2014 . This means to have a job run at 20:00 1/11/95. it must be defined (within the Control-M Calendar) as ODATE 08:00 1/11/95.

COND=(0.DACHART DD SYSOUT=A.UNIT=SYSDA.LRECL=180. // DCB=(RECFM=FB. NOTIFY=IV00000.CTMFLOW.OUTLIM=20000 /* /* //STEP3 EXEC PGM=IKJEFT01 //SYSTSPRT DD SYSOUT=X //SYSTSIN DD * VPSPRINT 'IVPSUPP. MSGLEVEL=(1.SCHEDULE(table name) DD * CHART YES GROUP UNITED PRINTER LASER FONT 9 PAGESIZE 96 LINESIZE 176 PAGESEQ YES /* //STEP1.DEST=T140DD11.PRTDBG DD SYSOUT=A.HOLD=YES /* /* //STEP2 EXEC PGM=KERIN1.DSORG=PS) //SYSPRINT DD SYSOUT=X.CTMFLOW.BLKSIZE=4500.1 Printing Job Flows The following is a sample JCL to print a jobflow/table from an Application Schedule library: //IV00000A // // //* //STEP01 //DAJOB //DAFLWPRM JOB '00000000'.MSGCLASS=X. // SPACE=(CYL.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 6.DEST=T140DD11.DACHART1 DD SYSOUT=A.CTMFLOW.COND=EVEN //DELETE DD DSN=IVPSUPP. // DCB=(RECFM=FB. // DISP=(NEW.COND=EVEN //SYSTSPRT DD SYSOUT=X //SYSTSIN DD * G:\Prodsupp\standard\PASTMPS.BLKSIZE=4500.HOLD=YES //STEP1.DISP=SHR //FT05F001 DD DSN=&&PRINT0.LRECL=180.DOC For Internal IBM GSA Use Only Enterprise Services Page 31 Printed 30/03/2014 .HOLD=YES //STEP1.HOLD=YES //STEP1.HOLD=YES //STEP1.DELETE).CLASS=A EXEC CTMRFLW DD DISP=SHR.DSN=TPIOA.DEST=T140DD11.CTMFLOW.0 Control-M Utilities 6.DEST=T140DD11.DEST=T140DD11.DELETE) /* /* //STEP5 EXEC PGM=IKJEFT01.PRNTFILE' T140DD11 NONUM NOHDR CCHAR /* /* //STEP4 EXEC PGM=IEFBR14.40).DELETE) //FT06F001 DD DSN=IVPSUPP.LOAD.PRNTFILE.PASS.DISP=(OLD.DSORG=PS) //STEP1.DACHART4 DD SYSOUT=A.DISP=(OLD. // SPACE=(TRK.LT) //STEPLIB DD DSN=IVPSUPP.PRNTFILE.DELETE.DISP=(NEW.1).OUTLIM=20000 //SYSOUT DD SYSOUT=X.UNIT=SYSDA.DELETE.'PROD SUPP XXXXX'.DELETE).DAREPORT DD SYSOUT=A.40).CATLG.applicname.DACHART9 DD DSN=&&PRINT0.

IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards VPSPRINT 'IVPSUPP.CTMFLOW.CTMFLOW.CNTL(LASER)’ G:\Prodsupp\standard\PASTMPS.CNTL(DONTDELE)' T140DD11 NONUM NOHDR CCHAR /* Copy of JCL available on VI2 – ‘IVPSUPP.DOC For Internal IBM GSA Use Only Enterprise Services Page 32 Printed 30/03/2014 .

condition specified as an Out-Condition on any job currently in AJF.THE CONDITION IS LOADED //* INTO THE MANUAL CONDITIONS FILE.DOC For Internal IBM GSA Use Only Enterprise Services Page 33 Printed 30/03/2014 . This might be applicable in instances whereby a daily job is dependant on a monthly job that is only schedule to run on the last day of the month. //* THE CONDITION IS IGNORED. G:\Prodsupp\standard\PASTMPS. .2 a joint venture with Lend Lease and Telstra Production CONTROL-M Standards MAYBE Utility The MAYBE utility is useful for instances where particular job inconditions will not be satisfied for that processing day and therefore needs to be added to allow the job/flow to run as per normal.condition already exits in the conditions/resources file If none of the above apply. In-Conditions) beginning with CONFIRM and HYP. It is important to note that this utility will scan the conditions of EVERY jobs/applications currently in the AJF. If any of the following scenarios exists. the condition will be added to the Manual Condition File.condition is to be added by a ‘DO COND’ statement. The following is a sample JCL for the ‘IOALDNRS’ utility: //QCIMLOAD JOB QPCIM199. the condition will NOT be added when running this utility: . The ‘IGNORE’ statement mentioned in the JCL will exclude any conditions (ie. IF NOT. 2. ALL PREREQUISITE //* CONDITIONS ARE CHECKED. THIS JOB WILL ALSO //* IGNORE CONDITIONS SPECIFIED WITH THE PREFIX GIVEN IN //* THE IGNORE STATEMENT BELOW.REGION=0M /*XEQ VI2 //* //* THIS JOB SCANS EVERY JOB IN THE AJF.IBM Global Services Australia MVS Production Support 6. The first job executing program ‘IOALDNRS’ will scan the AJF and check all the prerequisite conditions. IF THE IN CONDITION IS ADDED //* BY EITHER A 'DO COND' STATEMENT OR AN OUT PARAMETER. // CLASS=H.MSGCLASS=4. A number of ignore statements can be specified depending on the Application’s requirements. . This utility will be set-up to run as two separate jobs. //* THE EXISTING MANUAL CONDITIONS LIST IS NOT DESTROYED. //* //STEP1 EXEC IOALDNRS //DALNRIN DD * IGNORE IN CONFIRM IGNORE IN HYP CONTROLM YES ADDMODE /* Notes: 1. IF ADDMODE IS SPECIFIED.'CONTROLM UTILITY’. //* OR ALREADY EXISTS IN THE CONDITIONS/RESOURCES FILE.

* * * * ARGUMENT: * * A1 PREFIX PREFIX OF CONDITION(S) TO BE ADDED * * A2 DATE (DDMM).) to the conditions & resource file. In which case. The following is the sample JCL to perform the above: //QCIMPOST JOB QPCIM199. * * * * THIS CAN BE USED TO HANDLE 'MAY-BE JOBS' WITH * * 'MAY-BE CONDITIONS'.DOC For Internal IBM GSA Use Only Enterprise Services Page 34 Printed 30/03/2014 . OR 'NULL' FOR ANY DATE * * * * * *--------------------------------------------------------------* TRACE OFF MAXCOMMAND 999999 CALLMEM SCRSET CALLMEM ADDCOND7 QCIM NULL END Where desired or necessary. FOR ADDITIONAL INFORMATION * * PLEASE REFER TO THE MANUAL. * * * * BEFORE OPERATING THIS KSL. GREAT CARE must be taken when using this option. the following coding will apply: * * *---------------------------------------------------------------------* TRACE OFF MAXCOMMAND 999999 CALLMEM SCRSET CALLMEM ADDCOND7 QCIM %%ODAY. Therefore. SCREEN 7 PERHAPS SHOULD * * BE RE-FRESHED VIA UTILITY CTMLDNRS.%%OMONTH CALLMEM ADDCOND7 QCIM %%CYCL%%ODAY.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards The second jobs will check the manual condition file and add any conditions with the specified prefix (in the example below – QCIM. By so doing this will achieve the end result of satisfying those conditions that will not be met for that processing day. the above utility may be set-up to add conditions for the current or specific ODATE.MSGCLASS=4 /*XEQ VI2 // EXEC CTMRKSL *--------------------------------------------------------------* * FUNCTION: * * UTILITY TO ADD A MANUAL CONDITION IN SCREEN 7.%%OMONTH (If running Cycles eg Fcabs) END ***** NOTE – VERY IMPORTANT ***** It is MANDATORY to specify the Application jobname prefix in this utility (in the above example QCIM). Failure to do so will cause conditions belonging to other Applications to be satisfied and jobs to be prematurely started.’CONTROLM UTILITY’.. // CLASS=H. G:\Prodsupp\standard\PASTMPS. If in doubt consult one of the Application Management Team Leaders.

. ________________ On ** Only send this form AFTER the Controlm batch userid has been created. CONTROL-M BATCH USERID HAS BEEN CREATED FOR USE ON THE FOLLOWING DOMAINS : (Please indicate domains explicitly or type ALL for all domains) LPAR/S : ____________________________________________________________ DEFAULT RACF GROUP : . FCTMRapp. ** This section is to be completed and actioned by System Management. ph (03) 9253-7151. APPLICANTS NAME : ______________________________________ APPLICATION NAME : ( ) .SUBMIT please PERMIT STC USERID TO READ SURROGAT CLASS PROFILE indicate (Y/N) : ___ please FACILITY CLASS PROFILES CREATED ? indicate (Y/N) : ___ please PERMIT CTM ACCESS GROUPS TO FACILITY CLASS PROFILES ? please indicate (Y/N) : ___ G:\Prodsupp\standard\PASTMPS. APPLICATION SUPPORTED BY CPS ? indicate (Y/N) : ___ Completed by: ________________________________ / / . HOST/DOMAIN APPLICATION RESIDES ON : CONTROL-M HOST : . ** ** Please email this form to David J Timms. ** This section is to be completed and actioned by System Security. System Management.DOC For Internal IBM GSA Use Only Enterprise Services Page 35 Printed 30/03/2014 .0 Appendix A Sample 'REQUEST FOR CONTROL-M ACCESS' Form REQUEST FOR CONTROL-M ACCESS FOR PRODUCTION. or OIM ASSIGNMENT NAME : ( ) . FCTMNapp app = __ __ __ ? ** Please email this form to System Security. CONTROL-M BATCH USERID : . please Contact No. FCTMUapp. CTM RACF access groups created ? indicate (Y/N) : ___ CREATE SURROGAT CLASS PROFILE: indicate (Y/N) : ___ please userid.IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards 7. This section is to be completed and actioned by applicant.

** If the userid was created for an application.OVRD TPIOA. G:\ISM\CONTROLM\CTRMFORM. ** Archive hardcopy in processed forms file. .DOC G:\Prodsupp\standard\PASTMPS. please email this form to Production Support applicant. CONTROL-M DATASETS TO BE CREATED : TPIOA. . . ________________ On ** Please return to System Management when this section completed.SCHEDULE TPIOA.CNTL TPIOA.RUNBOOK RACF DATASET PROFILES CREATED: indicate (Y/N) : ___ please PERMISSION'S TO RACF D/S PROFILES GRANTED : indicate (Y/N) : ___ please DATASETS CREATED : indicate (Y/N) : ___ please CONNECT USERID TO GROUP FCTMAPS or FCTMTSP indicate (Y/N) : ___ please Completed by: ________________________________ Contact No. ________________ On / / .IBM Global Services Australia MVS Production Support a joint venture with Lend Lease and Telstra Production CONTROL-M Standards PERMIT SYS3 DATASET PROFILES ? indicate (Y/N) : ___ please SETR REFR RAC(FACI) command issued ? indicate (Y/N) : ___ please Completed by: ________________________________ / / . Contact No. .DOC For Internal IBM GSA Use Only Enterprise Services This form : Page 36 Printed 30/03/2014 . ** This section is to be completed and actioned by System Management.