Control M

CONTROL-M
NEW DIMENSION S O F T WA R E
USER MANUAL
M-514-U9901A
REL. 5.1.4
Copyright 1999 by New Dimension Software Ltd. All rights reserved. First Edition The software described in this document is furnished under a license agreement, and may be used or copied only in accordance with the terms of the agreement. CONTROL-M is a registered trademark of New Dimension Software Ltd. All other New Dimension Software products are trademarks or registered trademarks of New Dimension Software Ltd. Other brand and product names are trademarks or registered trademarks of their respective holders. The information in this document is subject to change without prior notice and does not represent a commitment on the part of New Dimension Software Ltd. New Dimension Software Ltd. assumes no responsibility for any errors that may appear in this document. M-514-U9901A 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2
About This Manual

The CONTROL-M User Manual is the main publication which describes the components and usage of CONTROL-M software. This manual should be used by everyone who will be defining job schedules or who will be actively controlling jobs in the production environment via CONTROL-M. This manual provides detailed information on all CONTROL-M functions and facilities. It contains the following sections:
Section 1
Introduction
CONTROL-M introduction and overview. This section briefly describes the main components of CONTROL-M from a functional perspective, and introduces the user to CONTROL-M facilities and features, concepts and logic. IOA components and concepts are also described. It is highly recommended that all users read this section before reading other sections in the manual.
Section 2
Online Facility
Guide to using CONTROL-M and IOA online facilities. CONTROL-M and IOA screens are illustrated and discussed in logical sequence.
Section 3
Job Production Parameters
Detailed description, accompanied by examples, of the parameters and statements in the CONTROL-M Job Scheduling Definition screen.
Section 4
CONTROL-M Event Manager (CMEM)
Overview of CONTROL-M Event Manager logic and a detailed description of the parameters and statements in CMEM rule definitions. This facility enables CONTROL-M to respond to external events (i.e., events in the MVS environment which occur outside of CONTROL-Ms direct control).
Section 5
JCL and AutoEdit Facility
Guide to the CONTROL-M AutoEdit facility, and its application to JCL. Usage of AutoEdit terms in the JCL can eliminate the need for manual changes to the JCL prior to job submission.
Section 6
Implementation and Maintenance
Important information relating to implementation and maintenance of CONTROL-M. Utilities and console operations are also described.
CONTROL-M Rel. 5.1.4 User Manual
iii
Section 7
Simulation and Forecasting Facility
Guide to simulating the effects of operations and procedures in your production environment and forecasting the potential impact of proposed changes.
Section 8
KSL and the Reporting Facility
Description of the KeyStroke Language (KSL) which emulates the Online facility in batch. The use of KSL scripts for utilities and report generation is discussed. This section also describes special reports available to CONTROL-M users.
Appendix A Editing Job Scheduling Definitions in the Edit Environment

Usage of the IOA Edit environment for editing job scheduling definitions.
Appendix B Editing CMEM Rule Definitions in the Edit Environment

Usage of the IOA Edit environment for editing CMEM rule definitions.
Appendix C AutoEdit Facility in KSL

Description of the AutoEdit facility usage in KSL scripts.
Appendix D MVS WTO Route/Descriptor Codes

List of MVS WTO message route codes and list of MVS WTO descriptor codes.
Index Information New to This Release

Information which is new in Releases 5.0.4 or 5.1.4 is identified by an update line in the left margin of the page.
Information Relating to CONTROLR Users

Certain information presented in the CONTROL-M User Manual is relevant only to CONTROL-M users who also use CONTROL-R. This information is designated by the R symbol in the left margin of the page.
iv
Related Publications
IOA Installation Guide
Step-by-step guide to installing IOA Customization Engine (ICE) application. products using the IOA Installation and
IOA Security Guide

Step-by-step guide to implementing security in IOA products using the IOA Installation and Customization Engine (ICE) application.
IOA Administrator Guide

Information for system administrators about customizing and maintaining IOA products.
IOA Messages and Codes

Comprehensive listing and explanation of all IOA messages and codes.
We Want to Hear From You...

If you have any comments or opinions regarding this publication, we want to hear them. Your feedback will help us improve our documentation to our mutual benefit. Send your remarks by email to publications@ndsoft.com. Please include the name and version of the publication in your email.
This page is intentionally left blank
vi
Table of Contents
Table of Contents
Section 1: Introduction to CONTROL-M
IOA Products and Your Data Center .......................................................................................1-1 CONTROL-M: A Functional Approach ...................................................................................1-1 Main Components.......................................................................................................................1-1 Job Scheduling Definitions ...................................................................................................1-1 Active Jobs File......................................................................................................................1-2 CONTROL-M Monitor...........................................................................................................1-2 Expanded CONTROL-M Functionality.....................................................................................1-2 Automating Job Scheduling: New Day Processing..............................................................1-2 Automatic JCL Update: JCL and AutoEdit Facility ...........................................................1-3 Automated Job Submission...................................................................................................1-3 Monitoring of Resources........................................................................................................1-4 Immediate Detection and Notification of Problems: Shout Facility ...................................1-4 History Jobs File....................................................................................................................1-5 Journaling and Restoration Capability................................................................................1-5 IOA Log Facility ....................................................................................................................1-5 Automated Job Post-Processing............................................................................................1-6 Utilities ..................................................................................................................................1-6 Handling Jobs in the NJE Network .....................................................................................1-6 Handling External Events: CMEM Facility ........................................................................1-7 Scheduling Jobs via Calendars: Calendar Facility..............................................................1-7 Accumulating Statistics: Statistics Facility.........................................................................1-8 Simulating Job Execution and Forecasting Resource Usage: Simulation and Forecasting Facility...............................................................................................................1-9 Automatic Tape Adjustment.................................................................................................1-9 Reporting Facility..................................................................................................................1-9 CONTROL-M Support For CONTROL-M/WorkLoad ............................................................1-10 Job Scheduling Definition Support ....................................................................................1-10 Enhanced Runtime Scheduling Algorithm ........................................................................1-10
vii
Table of Contents
Online User Interface to CONTROL-M.................................................................................. 1-11 Scheduling Definition Facility ........................................................................................... 1-11 Active Environment (Status) Screen: Online Tracking and Control Facility ................. 1-12 CMEM Rule Definition Facility ......................................................................................... 1-12 IOA Conditions/Resources Screen ..................................................................................... 1-13 IOA Log Screen ................................................................................................................... 1-13 IOA Manual Conditions Screen ......................................................................................... 1-13 IOA Calendar Facility ........................................................................................................ 1-14 Online Utility Screens (Under ISPF) ................................................................................ 1-14 CONTROL-M Concepts............................................................................................................. 1-15 IOA Core and CONTROL-M Repository ................................................................................ 1-15 Date Definition Concepts......................................................................................................... 1-16 Date Standards and Date Field Formats ............................................................................... 1-17 Job Ordering and Job Forcing................................................................................................. 1-18 Rerun and Restart ................................................................................................................... 1-18 Order ID ................................................................................................................................... 1-19 SYSDATA ................................................................................................................................. 1-19 Handling of Job Groups........................................................................................................... 1-19 Prerequisite Condition Concept .............................................................................................. 1-20 General ................................................................................................................................ 1-20 Prerequisite Condition Dates............................................................................................. 1-21 Deleting Conditions ............................................................................................................ 1-22 Conditions Requiring Manual Intervention...................................................................... 1-22 Maybe Jobs.......................................................................................................................... 1-22 Quantitative and Control Resources....................................................................................... 1-23 Quantitative Resources ...................................................................................................... 1-23 Control Resources ............................................................................................................... 1-23 Job Priority............................................................................................................................... 1-24 Automatic Job Flow Adjustment............................................................................................. 1-24
viii
Table of Contents
Section 2: Online Facility

IOA Features .................................................................................................................................2-1 General........................................................................................................................................2-1 Customization........................................................................................................................2-1 Environment Support............................................................................................................2-1 Terminal Support ..................................................................................................................2-2 Color Support.........................................................................................................................2-2 Prefixing.................................................................................................................................2-3 Character Masking................................................................................................................2-3 IOA Entry Panel .........................................................................................................................2-4 IOA Primary Option Menu ........................................................................................................2-5 IOA Version Information ....................................................................................................2-10 Multi-screen Control.................................................................................................................2-11 Fast Exit from the IOA Online Facility .............................................................................2-11 Screen Layout ...........................................................................................................................2-12 Commands and PFKeys ...........................................................................................................2-13 Scrolling Commands ...........................................................................................................2-15 LOCATE Command.............................................................................................................2-15 FIND Command ..................................................................................................................2-16 CANCEL and RESET Commands......................................................................................2-16 Online Help ...............................................................................................................................2-17 AutoRefresh Mode ....................................................................................................................2-18 Cancelling AutoRefresh Mode ............................................................................................2-18 IOA Under ISPF .......................................................................................................................2-19 IOA TSO Command Processor Screen.....................................................................................2-20 Transfer of Control Between the TSO Application and the IOA Online Facility ............2-21 Scheduling Definition Facility .............................................................................................. 2-22 General......................................................................................................................................2-22 Accessing the Scheduling Definition Facility ....................................................................2-22 Handling of Job Groups ......................................................................................................2-23 Creating Tables ...................................................................................................................2-24 Creating Job Scheduling Definitions..................................................................................2-25 Performing Operations on Tables and Jobs .......................................................................2-25 Entry Panel ...............................................................................................................................2-27 Fields of the Entry Panel ....................................................................................................2-27 Search Window ....................................................................................................................2-28
ix
Table of Contents
Table List Screen ..................................................................................................................... 2-30 Options of the Table List Screen........................................................................................ 2-30 Commands of the Table List Screen .................................................................................. 2-31 Job List Screen ......................................................................................................................... 2-32 Format of the Job List Screen ............................................................................................ 2-33 Commands of the Job List Screen...................................................................................... 2-33 Options of the Job List Screen ........................................................................................... 2-34 Job Scheduling Definition Screen Defining Schedules....................................................... 2-35 Parameters of the Job Scheduling Definition Screen ....................................................... 2-36 Scheduling Definition for Group Entities ......................................................................... 2-43 Commands of the Job Scheduling Definition Screen........................................................ 2-46 Editing Job Scheduling Definitions in the Edit Environment......................................... 2-47 Job Documentation ............................................................................................................. 2-48 Auto-Save and Saving Documentation.............................................................................. 2-49 Exiting the Scheduling Definition Facility............................................................................. 2-50 Exiting the Job Scheduling Definition Screen .................................................................. 2-51 Exiting the Job List Screen ................................................................................................ 2-51 Exiting the Table List Screen ............................................................................................ 2-52 Exiting the Entry Panel ..................................................................................................... 2-52 Ordering (Scheduling) Jobs..................................................................................................... 2-53 Copying Jobs to Another Table ............................................................................................... 2-55 Deleting Tables ........................................................................................................................ 2-56 Displaying Graphic Jobflow .................................................................................................... 2-57 Displaying a Job Scheduling Plan .......................................................................................... 2-59 Job Scheduling Plan Screen ............................................................................................... 2-60 Tracking and Control Facility ............................................................................................... 2-61 General ..................................................................................................................................... 2-61 Status Screen ........................................................................................................................... 2-62 Display Types of the Status Screen ................................................................................... 2-63 Format of the Status Screen .............................................................................................. 2-64 Commands of the Status Screen ........................................................................................ 2-66 Options of the Status Screen.............................................................................................. 2-69 Job Statuses ........................................................................................................................ 2-71 Filtering the Status Screen Display .................................................................................. 2-74 Global View Screen .................................................................................................................. 2-79 Fields of the Global View Screen ....................................................................................... 2-80 View Graph Screen .................................................................................................................. 2-81 View Graph Screen Format for Color Terminals .............................................................. 2-81 View Graph Screen Format for Non-color Terminals....................................................... 2-83
Table of Contents
Why Screen ...............................................................................................................................2-84 Adding Conditions in the Why Screen ...............................................................................2-86 Deleting a Job ...........................................................................................................................2-88 Delete Confirmation Window..............................................................................................2-89 Log Screen.................................................................................................................................2-90 Zoom Screen ..............................................................................................................................2-91 Zoom Screen for Group Entities .........................................................................................2-94 Exiting the Zoom Screen .....................................................................................................2-95 Confirm Scheduling Window ...................................................................................................2-96 Confirm Rerun Window ...........................................................................................................2-96 Confirm Restart Window (Under CONTROL-R) ....................................................................2-97 Rerun/Restart Window (Under CONTROL-R) .......................................................................2-97 Step List Window....................................................................................................................2-101 R Job Order Execution History Screen .....................................................................................2-102 Format of the Job Order Execution History Screen ........................................................2-103 Displaying Job Sysout .......................................................................................................2-103 Sysout Viewing Screen ...........................................................................................................2-104 Statistics Screen .....................................................................................................................2-105 Fields of the Statistics Screen...........................................................................................2-106 JOBSTAT Command .........................................................................................................2-107 Job Dependency Network Screen ..........................................................................................2-108 Format of Job Dependency Network Information ...........................................................2-109 Commands of the Job Dependency Network Screen .......................................................2-111 History Environment Screen .................................................................................................2-112 Options of the History Environment Screen....................................................................2-113 Force OK Confirmation Window............................................................................................2-113 CMEM Rule Definition Facility ........................................................................................... 2-115 General....................................................................................................................................2-115 Accessing the CMEM Rule Facility ..................................................................................2-115 Creating Tables .................................................................................................................2-116 Creating CMEM Rules ......................................................................................................2-116 Performing Operations on CMEM Tables and Rules ......................................................2-116 Entry Panel .............................................................................................................................2-117 Fields of the Entry Panel ..................................................................................................2-118 Table List Screen ....................................................................................................................2-118 Options of the Table List Screen ......................................................................................2-119 Rule List Screen......................................................................................................................2-119 Options of the Rule List Screen ........................................................................................2-120 Rule Definition Screen Defining Rules...............................................................................2-121
xi
Table of Contents
Event Selection Parameters............................................................................................. 2-122 General Parameters.......................................................................................................... 2-123 Action Parameters ............................................................................................................ 2-123 Commands of the Rule Definition Screen ....................................................................... 2-124 Specifying Comments ............................................................................................................ 2-124 Editing CMEM Rule Definitions in the Edit Environment................................................. 2-125 Exiting the CMEM Rule Definition Facility ........................................................................ 2-126 Exiting the Rule Definition Screen.................................................................................. 2-126 Exiting the Rule List Screen ............................................................................................ 2-127 Exiting the Table List Screen .......................................................................................... 2-128 Exiting the Entry Panel ................................................................................................... 2-128 Deleting Tables ...................................................................................................................... 2-128 Ordering CMEM Rule Tables................................................................................................ 2-129 Condition/Resource Handling.............................................................................................. 2-131 General ................................................................................................................................... 2-131 IOA Conditions/Resources Screen......................................................................................... 2-131 Fields of the IOA Conditions/Resources Screen .............................................................. 2-132 Specifying Retrieval Criteria ........................................................................................... 2-133 Adding Conditions and Resources The ADD Command ............................................. 2-134 Options of the IOA Conditions/Resources Screen ........................................................... 2-136 IOA Manual Conditions Screen ............................................................................................ 2-139 Fields of the IOA Manual Conditions Screen.................................................................. 2-140 Specifying Retrieval Criteria ........................................................................................... 2-140 Options of the IOA Manual Conditions Screen............................................................... 2-141 Adding a New Prerequisite Condition NEW COND Command ................................. 2-143 IOA Log Facility....................................................................................................................... 2-144 General ................................................................................................................................... 2-144 IOA Log Screen ...................................................................................................................... 2-144 Fields of the IOA Log Screen ........................................................................................... 2-145 Commands of the IOA Log Screen ................................................................................... 2-145 Filtering the IOA Log Screen Display ............................................................................. 2-146 IOA Calendar Facility ............................................................................................................ 2-151 General ................................................................................................................................... 2-151 Accessing the Calendar Facility....................................................................................... 2-152 Entry Panel ............................................................................................................................ 2-153 Fields of the Entry Panel ................................................................................................. 2-153 Calendar List Screen ............................................................................................................. 2-154 Options of the Calendar List Screen................................................................................ 2-154 Year List Screen..................................................................................................................... 2-155
xii
Table of Contents
Options of the Year List Screen ........................................................................................2-156 Inserting a New Year ........................................................................................................2-156 Calendar Definition Screen....................................................................................................2-157 Periodic Calendars ............................................................................................................2-158 Deleting Calendars............................................................................................................2-161 Exiting the IOA Calendar Facility ........................................................................................2-162 Exiting the Calendar Definition Screen...........................................................................2-162 Exiting the Year List Screen.............................................................................................2-163 Exiting the Calendar List Screen .....................................................................................2-163 Exiting the Entry Panel ....................................................................................................2-163 Utilities Under ISPF ............................................................................................................... 2-164 General....................................................................................................................................2-164 IOA Online Utilities Menu.....................................................................................................2-164 I1: Add/Check/Delete a Prerequisite Condition ....................................................................2-166 M1: Issue a Job Order ............................................................................................................2-167 M2: Perform Online AutoEdit Simulation ............................................................................2-168 M3: Prepare Simulation/Tape Pull List Job..........................................................................2-172 M4: Parameter Prompting Facilities .....................................................................................2-176 Parameter Prompting Facility (Type 1) ...........................................................................2-177 Parameter Prompting Facility (Type 2) ...........................................................................2-184 M5: Quick Schedule Definition Facility ...............................................................................2-194 M6: End User Job Order Interface ......................................................................................2-202 R1: CONTROL-R Restart Simulation .................................................................................2-203
R2: CONTROL-R Dataset Cleanup .......................................................................................2-205 R3: Prepare the Job Dataset List.........................................................................................2-208 U1: Invoke DOCU/TEXT........................................................................................................2-209
xiii
Table of Contents
Section 3: Job Production Parameters

General........................................................................................................................................... 3-1 General Parameters Summary .............................................................................................. 3-4 Basic Scheduling Parameters Summary ............................................................................... 3-4 Runtime Scheduling Parameters Summary ......................................................................... 3-8 Post-processing Parameters Summary.................................................................................. 3-9 Parameter Descriptions........................................................................................................... 3-11 ADJUST CONDITIONS.......................................................................................................... 3-12 APPL......................................................................................................................................... 3-14 AUTO-ARCHIVE ..................................................................................................................... 3-16
SYSDB................................................................................................................................. 3-16 MAXDAYS........................................................................................................................... 3-16 MAXRUNS .......................................................................................................................... 3-16 CONFCAL ................................................................................................................................ 3-19 SHIFT.................................................................................................................................. 3-20 CONFIRM ................................................................................................................................ 3-23 CONTROL................................................................................................................................ 3-25 CTB STEP ................................................................................................................................ 3-29 AT ........................................................................................................................................ 3-29 NAME.................................................................................................................................. 3-29 TYPE ................................................................................................................................... 3-29 D-CAT....................................................................................................................................... 3-31 DATES...................................................................................................................................... 3-33 DAYS ........................................................................................................................................ 3-35 DCAL ................................................................................................................................... 3-35 AND/OR............................................................................................................................... 3-36 DESC ........................................................................................................................................ 3-42 DO statement ........................................................................................................................... 3-44 DO COND................................................................................................................................. 3-46 DO CTBRULE.......................................................................................................................... 3-50 ARG ..................................................................................................................................... 3-50 DO FORCEJOB ....................................................................................................................... 3-52 TABLE................................................................................................................................. 3-52 JOB ...................................................................................................................................... 3-52 DATE ................................................................................................................................... 3-52 LIBRARY............................................................................................................................. 3-52
xiv
Table of Contents
DO IFRERUN ...........................................................................................................................3-54 FROM...................................................................................................................................3-54
TO .........................................................................................................................................3-55 CONFIRM............................................................................................................................3-55 DO NOTOK...............................................................................................................................3-57 DO OK .......................................................................................................................................3-59 DO RERUN...............................................................................................................................3-61 DO SET .....................................................................................................................................3-63 VAR= ....................................................................................................................................3-63 DO SHOUT ...............................................................................................................................3-66 TO .........................................................................................................................................3-66 URGENCY ...........................................................................................................................3-67 DO SYSOUT .............................................................................................................................3-70 OPT ......................................................................................................................................3-70 PRM......................................................................................................................................3-70 FRM......................................................................................................................................3-70 DOC ...........................................................................................................................................3-77 DOCLIB ....................................................................................................................................3-79 DOCMEM..................................................................................................................................3-81 DUE OUT..................................................................................................................................3-83 GROUP......................................................................................................................................3-85 IN...............................................................................................................................................3-87 INTERVAL................................................................................................................................3-95 MAXWAIT.................................................................................................................................3-97 MEMLIB .................................................................................................................................3-100 MEMNAME ............................................................................................................................3-104 MINIMUM ..............................................................................................................................3-106 MONTHS ................................................................................................................................3-108 ON ...........................................................................................................................................3-110 PGMST...............................................................................................................................3-110 PROCST .............................................................................................................................3-110 CODES ...............................................................................................................................3-111 A/O......................................................................................................................................3-111 ON GROUP-END ...................................................................................................................3-118 OUT .........................................................................................................................................3-120 OVERLIB ................................................................................................................................3-131 OWNER...................................................................................................................................3-133 PDS..........................................................................................................................................3-135 PIPE ........................................................................................................................................3-137
xv
Table of Contents
PREVENT-NCT2 ................................................................................................................... 3-140 PRIORITY .............................................................................................................................. 3-142 RELATIONSHIP ................................................................................................................... 3-144 RERUN-MAXRERUN ........................................................................................................... 3-146 RERUN-RERUNMEM .......................................................................................................... 3-148 RESOURCE ........................................................................................................................... 3-150 RETENTION: # OF DAYS TO KEEP................................................................................... 3-155 RETENTION: # OF GENERATIONS TO KEEP................................................................. 3-157 RETRO ................................................................................................................................... 3-159 SCHEDULE TAG .................................................................................................................. 3-161 SET VAR ................................................................................................................................ 3-164 SHOUT ................................................................................................................................... 3-169 WHEN ............................................................................................................................... 3-169 TO ...................................................................................................................................... 3-170 URGN ................................................................................................................................ 3-171 MS...................................................................................................................................... 3-171 STEP RANGE ........................................................................................................................ 3-174 FR (PGM.PROC) ............................................................................................................... 3-174 TO ...................................................................................................................................... 3-174 SYSOUT ................................................................................................................................. 3-176 OP ...................................................................................................................................... 3-176 FROM ................................................................................................................................ 3-176 TASKTYPE ............................................................................................................................ 3-182 TIME....................................................................................................................................... 3-186 FROM ................................................................................................................................ 3-186 UNTIL ............................................................................................................................... 3-186 WDAYS................................................................................................................................... 3-189 WCAL ................................................................................................................................ 3-189
xvi
Table of Contents
Section 4: CONTROL-M Event Manager (CMEM)

General ...........................................................................................................................................4-1 Types of Events Managed by CMEM ........................................................................................4-1 Types of Actions Which CMEM Can Perform...........................................................................4-2 CMEM Rule Ordering, Triggering and Deactivation ...............................................................4-2 CMEM AutoEdit Variables ........................................................................................................4-3 On Spool Jobs..............................................................................................................................4-3 Creating On Spool Jobs.........................................................................................................4-4 Job On Spool ..........................................................................................................................4-4 CMEM Rule ...........................................................................................................................4-4 Job Scheduling Definition .....................................................................................................4-5 Handling On Spool Jobs........................................................................................................4-5 On Spool Job Definition Considerations ..............................................................................4-6 JCL Management Considerations ........................................................................................4-6 CMEM Support for FTP .............................................................................................................4-7 Rule Parameters Summary....................................................................................................4-8 Event Selection Parameters.......................................................................................................4-9 General Parameters ...................................................................................................................4-9 Action Parameters ......................................................................................................................4-9 Parameter Descriptions .......................................................................................................... 4-10 DESCRIPTION.........................................................................................................................4-11 DO statement............................................................................................................................4-13 DO COND .................................................................................................................................4-14 DO FORCEJOB ........................................................................................................................4-17 DO RULE ..................................................................................................................................4-21 DO SHOUT ...............................................................................................................................4-24 DO STOPJOB ...........................................................................................................................4-27 GROUP......................................................................................................................................4-29 MODE........................................................................................................................................4-31 ON statement............................................................................................................................4-33 ON DSNEVENT .......................................................................................................................4-35 ON JOBARRIV .........................................................................................................................4-40 ON JOBEND.............................................................................................................................4-42 ON STEP...................................................................................................................................4-44 OWNER.....................................................................................................................................4-48 RUNTSEC.................................................................................................................................4-50
xvii
Table of Contents
Section 5: JCL and AutoEdit Facility

General........................................................................................................................................... 5-1 JCL Setup Operation Flow........................................................................................................ 5-4 System Variables ......................................................................................................................... 5-5 Non-Date System Variables ...................................................................................................... 5-5 Date System Variables .............................................................................................................. 5-6 Special System Variables .......................................................................................................... 5-8 User-Defined Variables .............................................................................................................. 5-9 Format of Variable Members.................................................................................................. 5-10 Rules of Variable Resolution .................................................................................................. 5-11 Order of Precedence for Multiple Value Assignments........................................................... 5-14 Control Statements ................................................................................................................... 5-15 %%GLOBAL............................................................................................................................. 5-15 %%GOTO and %%LABEL....................................................................................................... 5-15 %%IF, %%ELSE, %%ENDIF .................................................................................................. 5-16 %%INCLIB and %%INCMEM ................................................................................................ 5-18 %%LIBSYM and %%MEMSYM .............................................................................................. 5-19 %%RANGE............................................................................................................................... 5-20 %%RESOLVE........................................................................................................................... 5-21 %%SET ..................................................................................................................................... 5-21 Operators..................................................................................................................................... 5-22 Functions..................................................................................................................................... 5-23 %%$CALCDTE ........................................................................................................................ 5-23 %%$GREG................................................................................................................................ 5-23 %%$JULIAN ............................................................................................................................ 5-23 %%$LEAP ................................................................................................................................ 5-24 %%$WCALC............................................................................................................................. 5-24 %%$WEEK# ............................................................................................................................. 5-25 %%$WEEKDAY ....................................................................................................................... 5-25 %%CALCDATE........................................................................................................................ 5-26 %%SUBSTR ............................................................................................................................. 5-26 Testing AutoEdit Syntax.......................................................................................................... 5-27 AutoEdit Usage in the Job Scheduling Definition ............................................................ 5-28 Examples ..................................................................................................................................... 5-30 Date Variables.......................................................................................................................... 5-30 ODATE, RDATE and DATE Usage ........................................................................................ 5-31 How to Obtain Date Formats 1 ............................................................................................ 5-32 How to Obtain Date Formats 2 ............................................................................................ 5-32
xviii
Table of Contents
How to Obtain Date Formats 3.............................................................................................5-33 How to Obtain the Previous Months Last Business Date .....................................................5-34 Automatic Job Order for the Next Day ...................................................................................5-35 Tape Clearance System Stage 1............................................................................................5-36 Tape Clearance System Stage 2............................................................................................5-37 Tape Management System.......................................................................................................5-38 Dynamic Job Name...................................................................................................................5-38 Controlling the Target Computer by Class .............................................................................5-39 Controlling the Target Computer by System Affinity ............................................................5-39 %%BLANKn Statement ...........................................................................................................5-40 %%RANGE Statement .............................................................................................................5-41 SYSIN Parameter Containing %% ..........................................................................................5-42 %%INCLIB and %%INCMEM Statements.............................................................................5-42 Boolean IF Logic ....................................................................................................................5-43
Section 6: Implementation and Maintenance

General ...........................................................................................................................................6-1 Implementation ............................................................................................................................6-1 Job Ordering via New Day Processing ......................................................................................6-2 Overview ................................................................................................................................6-2 Sample New Day Processing ................................................................................................6-4 Implementing New Day Processing .....................................................................................6-7 Programs Called During New Day Processing ..................................................................6-12 Alternative Methods of Job Ordering ......................................................................................6-14 Job Ordering Via CLIST CTMCJOBS................................................................................6-15 Job Ordering Via Quick Submit Command CTMQSB ......................................................6-16 Ad Hoc Job Ordering From Special Environments: CTMAJO .........................................6-17 Manual Conditions File and Maybe Jobs ................................................................................6-19 Loading the Manual Conditions File..................................................................................6-19 Using the Manual Conditions File .....................................................................................6-19 Handling Manual Conditions .............................................................................................6-20 Handling Unscheduled Conditions.....................................................................................6-20 Handling Maybe Dependencies ..........................................................................................6-21 Maybe Jobs in Group Scheduling Tables ...........................................................................6-21 CONTROL-M/WorkLoad Considerations................................................................................6-23 Job-Related Considerations for Pipes.................................................................................6-23 System-Related Considerations..........................................................................................6-24
xix
Table of Contents
CONNECT DIRECT Support.................................................................................................. 6-25 REXX Procedure IOACDDR: Dataset Event Definition................................................... 6-25 Event List Screen................................................................................................................ 6-26 Event Definition Screen ..................................................................................................... 6-27 Parameter Prompting Facilities.............................................................................................. 6-29 Parameter Prompting Facility Type 1............................................................................ 6-29 Parameter Prompting Facility Type 2............................................................................ 6-35 Utilities ........................................................................................................................................ 6-43 CTMAESIM Test AutoEdit Syntax...................................................................................... 6-45 CTMBLDAE Build AutoEdit Symbols Member.................................................................. 6-49 CTMBLT Create Scheduling Tables .................................................................................... 6-54 CTMJOB Order Jobs to the Active Jobs File ...................................................................... 6-71 CTMRCAL Produce a Job Plan Report................................................................................ 6-76 CTMRELRS Release Quantitative Resources..................................................................... 6-78 CTMTBUPD Update Job Scheduling Tables ..................................................................... 6-80 CTMXRF Create Cross Reference Reports.......................................................................... 6-91 IOACND Handle Condition/Resource Utilization............................................................... 6-97 Operations Guide .................................................................................................................... 6-100 Activating the CONTROL-M Monitor .................................................................................. 6-100 Shutting Down the CONTROL-M Monitor .......................................................................... 6-100 Modifying the CONTROL-M Sleeping Interval ................................................................... 6-101 New Day Procedure Flow ...................................................................................................... 6-101 Started Tasks ......................................................................................................................... 6-102 CONTROL-M Errors ............................................................................................................. 6-103 CONTROL-M Monitor and JES............................................................................................ 6-103 Cases of JES Malfunction ................................................................................................ 6-103 Special Considerations ..................................................................................................... 6-103 Stopping CMEM Before JES Is Stopped ......................................................................... 6-105 Managing the CMEM Facility .............................................................................................. 6-106 CMEM and CONTROL-O ................................................................................................ 6-106 Activating the CONTROL-M Event Manager (CMEM) Facility ................................... 6-106 Deactivating the CMEM Facility..................................................................................... 6-106 Replacing an Active CMEM Monitor............................................................................... 6-107 Loading of Rules ............................................................................................................... 6-107 Deleting (Deactivating) an Active Rule Table................................................................. 6-109 Displaying Active Rules ................................................................................................... 6-109 Controlling CMEM Rule Operation Mode....................................................................... 6-110 Modifying the CMEM Sleeping Interval ......................................................................... 6-110 Refreshing the CMEM Security Cache............................................................................ 6-111
xx
Table of Contents
Modifying the CONTROL-M Resources Acquisition Exit ....................................................6-111 Loading a New Destination Table .........................................................................................6-112 Performing Deadline Scheduling Calculations.....................................................................6-112 Issuing Operator Commands Via a Job or STC....................................................................6-113 IOA Online Monitor................................................................................................................6-113 General...............................................................................................................................6-113 Activating the IOA Online Monitor..................................................................................6-114 Deactivating the IOA Online Monitor..............................................................................6-114 Controlling the Online Monitor(s) ....................................................................................6-115
Section 7: Simulation and Forecasting Facility

General ...........................................................................................................................................7-1 Simulation Procedure CTMSIM ...............................................................................................7-2 General........................................................................................................................................7-2 Activating the Procedure............................................................................................................7-3 Preparatory Steps.......................................................................................................................7-3 Allocate Active Jobs File .......................................................................................................7-3 Allocate Conditions/Resources File.......................................................................................7-3 Parameters..................................................................................................................................7-4 Input Files...................................................................................................................................7-6 Output Files ................................................................................................................................7-6 CONTROL-M Exits and Simulation Processing.......................................................................7-7 Analyzing the Simulation Run ..................................................................................................7-8 Handling Manual Conditions ...............................................................................................7-9 Tape Pull List Procedure CTMTAPUL................................................................................. 7-10 General......................................................................................................................................7-10 Activating the Procedure..........................................................................................................7-11 Parameters................................................................................................................................7-11 DD Statements .........................................................................................................................7-12 JOB/SCAN DOCU/TEXT Interface .......................................................................................7-12 Problem Determination for Tape Pull List Reports................................................................7-13 Sample Tape Pull List Reports ................................................................................................7-14
xxi
Table of Contents
Section 8: KSL and the Reporting Facility

General........................................................................................................................................... 8-1 KeyStroke Language .................................................................................................................. 8-1 Activating KeyStroke Language Scripts .................................................................................. 8-2 KSL Command and Variable Summary................................................................................... 8-3 Principles of Operation .............................................................................................................. 8-5 Sample KeyStroke Reports and Utilities.................................................................................. 8-9 Language Syntax ..................................................................................................................... 8-11 KSL Commands and Variables............................................................................................... 8-12 Screen Commands ................................................................................................................... 8-12 Flow Commands....................................................................................................................... 8-13 Print Commands ...................................................................................................................... 8-17 Processing Commands ............................................................................................................. 8-19 KSL Variables .......................................................................................................................... 8-22 Special KSL Variables ............................................................................................................. 8-23 Sample KSL Script and its Report Output............................................................................. 8-24 Special Purpose Reports.......................................................................................................... 8-33 CTMRFLW: Scheduling Table Job Flow Report .................................................................... 8-33 EXEC Statement Parameters ............................................................................................ 8-34 Report Parameters.............................................................................................................. 8-34 Fields of the Job Flow Report in Text format.................................................................... 8-39 Sample Job Flow Report Output in Graphic Format ....................................................... 8-40 CTMRAFL: Active Jobs File Job Flow Report........................................................................ 8-44 CTMRPLN: Job Plan Report ................................................................................................... 8-45 CTMRPFL: Job Plan/Flow Report .......................................................................................... 8-49 CTMRNSC: Night Schedule Report........................................................................................ 8-51 CTMROGR: Overnight Execution Graph............................................................................... 8-53 CTMRJDS: Job Dataset Cross Reference Report................................................................... 8-57
Appendixes
Appendix A: Editing Job Scheduling Definitions in the Edit Environment .................A-1 Appendix B: Editing CMEM Rule Definitions in the Edit Environment ......................B-1 Appendix C: AutoEdit Facility in KSL ..................................................................................C-1 Appendix D: MVS WTO Route/Descriptor Codes ............................................................... D-1
Index
xxii CONTROL-M Rel. 5.1.4 User Manual
Section 1: Introduction to CONTROL-M

IOA Products and Your Data Center .......................................................................................1-1 CONTROL-M: A Functional Approach ...................................................................................1-3 Main Components.......................................................................................................................1-3 Job Scheduling Definitions ...................................................................................................1-3 Active Jobs File......................................................................................................................1-4 CONTROL-M Monitor...........................................................................................................1-4 Expanded CONTROL-M Functionality.....................................................................................1-4 Automating Job Scheduling: New Day Processing..............................................................1-4 Automatic JCL Update: JCL and AutoEdit Facility ...........................................................1-5 Automated Job Submission...................................................................................................1-5 Monitoring of Resources........................................................................................................1-6 Immediate Detection and Notification of Problems: Shout Facility ...................................1-6 History Jobs File....................................................................................................................1-7 Journaling and Restoration Capability................................................................................1-7 IOA Log Facility ....................................................................................................................1-7 Automated Job Post-Processing............................................................................................1-8 Utilities ..................................................................................................................................1-8 Handling Jobs in the NJE Network .....................................................................................1-8 Handling External Events: CMEM Facility ........................................................................1-9 Scheduling Jobs via Calendars: Calendar Facility..............................................................1-9 Accumulating Statistics: Statistics Facility.......................................................................1-10 Simulating Job Execution and Forecasting Resource Usage: Simulation and Forecasting Facility.............................................................................................................1-11 Automatic Tape Adjustment...............................................................................................1-11 Reporting Facility................................................................................................................1-11 CONTROL-M Support For CONTROL-M/WorkLoad ............................................................1-12 Job Scheduling Definition Support ....................................................................................1-12 Enhanced Runtime Scheduling Algorithm ........................................................................1-12 Online User Interface to CONTROL-M ..................................................................................1-13 Scheduling Definition Facility ............................................................................................1-13 Active Environment (Status) Screen: Online Tracking and Control Facility ..................1-14 CMEM Rule Definition Facility..........................................................................................1-14 IOA Conditions/Resources Screen ......................................................................................1-15 IOA Log Screen....................................................................................................................1-15 IOA Manual Conditions Screen ..........................................................................................1-15 IOA Calendar Facility .........................................................................................................1-16 Online Utility Screens (Under ISPF) .................................................................................1-16
CONTROL-M Concepts............................................................................................................. 1-17 IOA Core and CONTROL-M Repository ................................................................................ 1-17 Date Definition Concepts......................................................................................................... 1-18 Date Standards and Date Field Formats ............................................................................... 1-19 Job Ordering and Job Forcing................................................................................................. 1-20 Rerun and Restart ................................................................................................................... 1-20 Order ID ................................................................................................................................... 1-21 SYSDATA ................................................................................................................................. 1-21 Handling of Job Groups........................................................................................................... 1-21 Prerequisite Condition Concept .............................................................................................. 1-22 General ................................................................................................................................ 1-22 Prerequisite Condition Dates............................................................................................. 1-23 Deleting Conditions ............................................................................................................ 1-24 Conditions Requiring Manual Intervention...................................................................... 1-24 Maybe Jobs.......................................................................................................................... 1-24 Quantitative and Control Resources....................................................................................... 1-25 Quantitative Resources ...................................................................................................... 1-25 Control Resources ............................................................................................................... 1-25 Job Priority............................................................................................................................... 1-26 Automatic Job Flow Adjustment............................................................................................. 1-26
Introduction: IOA Products and Your Data Center
IOA Products and Your Data Center

The CONTROL-M automated production control system is one of the products available in the IOA (Integrated Operations Architecture) family of products. IOA consists of a fully integrated suite of products designed to help you automate, manage and streamline your mainframe operations. IOA products include: CONTROL-M Automated Production Control and Scheduling System Manages and automates the setup, scheduling, and execution of jobs in your MVS data center. Restart Management System Automates the activities which must be performed when restarting failed jobs, including the scratching and uncataloging of datasets created by failed jobs. Output Management System Automatically schedules and controls every aspect of report processing and distribution, including report decollating, bundling, printing, online viewing and backup. Quick Access Archive Viewing System Provides online access to archived reports and documents via indexed data retrieval. Online Viewing and Manipulation of Reports Enables viewing, editing and printing of reports from the PC. Report Retrieval and Display System Enables end users to retrieve and view pages of reports that reside on mainframe storage in real-time. Indexed reports can be retrieved by index name and value. AFP and XEROX reports can also be retrieved and displayed using CONTROL-D/PC or Page On Demand API. Image Output Management System Enables output from commercial imaging equipment to be imported into CONTROL-D/V for decollation, distribution, viewing, archiving and indexed retrieval. Console Automation System Monitors and automatically responds to messages, commands and dataset events. Desired State Monitoring System Monitors objects in the system and maintains them in specified desired statuses. Outboard Console Automation Allows outboard console automation of multiple platforms via a PC, and provides consolidation and management of messages from multiple consoles via a single point of control.
CONTROL-R
CONTROL-D
CONTROL-V
CONTROL-D/PC CONTROL-D/ Page On Demand
CONTROL-D/ Image
CONTROL-O
CONTROL-O/ COSMOS CONTROL-O/ Server
11
Introduction: IOA Products and Your Data Center
CONTROL-T
Removable Media Management System Increases removable media utilization, controls retention periods, prevents misuse of media, and provides tape library and vault control. Automated Information Integrity System Performs in-stream validation, and accuracy/reasonability checks on information used by data center production tasks (e.g., reports, files, databases).
CONTROL-B
CONTROL-I/2000 Year 2000 Automated Testing and Data Validation Solution Provides a Year 2000 Solution Set that addresses data validation issues, covers the Year 2000 testing lifecycle, and forms the basis for a permanent enterprise-wide automated quality control system. CONTROL-M/ WorkLoad Batch Optimization System Reduces batch processing elapsed time by enabling serial processes to run in parallel. Pipe technology allows communication between batch processes in the same CPU or across a Sysplex while optimizing resource utilization. IOA Cross-Reference Facilitates impact analysis, change management, and the enhancement of IOA product performance by collecting and analyzing data from IOA and non-IOA resources (such as JCL libraries, load module libraries, and source libraries). Automatically locates all references to IOA components, and reports JCL-IOA relationships, IOA-MVS object relationships, and IOA component interrelationships.
IOA/Pathfinder
Related to the IOA family of products is the IOA for the Enterprise family of client/server products which facilitates the automation of MVS and non-MVS platforms.
12
Introduction: CONTROL-M: A Functional Approach Main Components
CONTROL-M: A Functional Approach

CONTROL-M automates job processing in your data center.
It performs virtually all the job handling tasks of computer operators. It provides a user interface which enables the user to intervene in the process of production management. It provides continual data and status information regarding job processing.
CONTROL-M contains many facilities and components. Working together, they automate the data center. This section introduces these facilities and components from a functional perspective, beginning with the major components which comprise the heart of CONTROL-M and progressing to the more minor components which enhance the functionality of CONTROL-M.
Main Components
The following components are essential to CONTROL-M:
Job scheduling definitions. Active Jobs file. CONTROL-M monitor.
Job Scheduling Definitions

A job scheduling definition specifies criteria that identify decisions to be made, and actions to be taken, regarding the handling of a particular job. Each job scheduling definition contains the following sections: General Parameters Basic Scheduling Parameters General information about the job (e.g., identifies the library and member in which the JCL is stored). Criteria according to which CONTROL-M schedules the job.
Runtime Scheduling Parameters Runtime requirements which must be satisfied before CONTROL-M submits the job. Post-processing Parameters Actions CONTROL-M performs after the job ends, depending upon the outcome of job execution (e.g., one set of actions if the job ends OK, another set of actions if an abend occurs).
Job scheduling definitions only need be defined once for each job in the production environment. (The mechanism used to define job scheduling definitions is discussed later.) Once defined, a job scheduling definition is saved. It can be modified later if required, and the changes saved. Job scheduling definitions are stored in members in partitioned datasets (libraries), as follows:
Job scheduling definitions for related applications are generally placed in a single member, called a scheduling table. Multiple scheduling tables are stored in partitioned datasets, called scheduling libraries. Multiple scheduling libraries can be defined.
13
Introduction: CONTROL-M: A Functional Approach Expanded CONTROL-M Functionality
Active Jobs File

As mentioned above, each job scheduling definition contains criteria which determine whether or not the job should be scheduled on a given day. If based on these criteria a job should be scheduled, a copy of its job scheduling definition is placed in a file called the Active Jobs file. (The mechanism by which job scheduling definitions are placed in the Active Jobs file is discussed later.) Only jobs in the Active Jobs file are candidates for submission by the CONTROL-M monitor.
CONTROL-M Monitor
The CONTROL-M monitor handles and controls job processing:
It checks the runtime requirements specified in each job scheduling definition in the Active Jobs file, monitors available resources and conditions in the environment, and if it determines that the conditions and resources required by a job are available, it allocates the resources and submits the job. It monitors the execution of the job. It implements post-processing decisions based on instructions in the job scheduling definition and the results of the job execution.
The CONTROL-M monitor operates continually. It evaluates the production environment and implements decisions.
Expanded CONTROL-M Functionality

Having explained the main components of CONTROL-M, we can now build upon this foundation and explain a number of the facilities, features and capabilities which enhance CONTROL-M.
Automating Job Scheduling: New Day Processing

One of the main purposes of CONTROL-M is to automate job scheduling. We have already explained that basic scheduling criteria for each job are defined in its job scheduling definition, and that a copy of the job scheduling definition is placed in the Active Jobs file when the basic scheduling criteria are satisfied. The mechanism used to place job scheduling definitions automatically in the Active Jobs file is called New Day processing. At a set time each day (defined during installation as the sites start of day), CONTROL-M performs New Day processing, during which:
CONTROL-M performs a number of maintenance and cleanup functions which the operator would otherwise have to perform manually. Job scheduling definitions are selected from the scheduling tables (based on their basic scheduling criteria) and are placed in the Active Jobs file. These jobs can then be submitted and tracked by the CONTROL-M monitor.
The implementation of automated job scheduling and New Day processing, and the components of New Day processing, are discussed in detail in Section 6 of this manual and in Section 3 of the IOA Administrator Guide.
14
Automatic JCL Update: JCL and AutoEdit Facility

In the production environment, JCL must often be manually modified prior to submission of a job, as in the following cases:
Changing a parameter or a date card. Supplying tape numbers in JCL procedures. Eliminating steps under different run conditions (e.g., end of month processing vs. normal daily run).
Manual modification of the JCL is inconvenient at best, and it can be error-prone and lead to serious problems. The JCL and AutoEdit facility offers an automated alternative to manual JCL update. The JCL and AutoEdit facility permits AutoEdit terms (AutoEdit variables, functions and control statements) to be specified in the JCL in place of values which change from job submission to job submission. AutoEdit terms are prefixed by %% which distinguishes them from non-AutoEdit terms. For example, the term %%ODAY is recognized as an AutoEdit term. At time of job submission, AutoEdit terms in the JCL are resolved to (replaced by) their actual values. The inclusion of AutoEdit terms into the job stream can eliminate the need to change JCL once it is defined. AutoEdit usage can be further simplified and enhanced via the Parameter Prompting facility (described in Sections 2 and 6 of this manual). It should be noted that certain AutoEdit terms can also be used within job scheduling definitions. The JCL and the AutoEdit facility is described in detail in Section 5 of this manual.
Automated Job Submission

Once a job has been placed in the Active Jobs file, the CONTROL-M monitor does not submit the job unless all its runtime scheduling criteria (defined in the job scheduling definition) are satisfied. Several types of runtime criteria can be defined. Examples Time Priority Submission must occur during a specified time range. Jobs can be assigned internal priorities, so that if two jobs are ready for submission at the same time, the higher-priority job is submitted first. If two jobs with the same priority are ready for submission, the job with the earlier due out time is submitted first.
Due Out
15
Monitoring of Resources
Three types of runtime criteria require CONTROL-M to monitor the existence of conditions and the availability of resources system-wide. These conditions and resources are mentioned briefly below and are discussed in greater detail under CONTROL-M Concepts later in this section: Quantitative resources Control resources Quantity of a resource required by the job. For example, a job may require two tape drives. Mode (exclusive/shared) in which a resource is required. For example, a backup job may require exclusive access to a specified dataset. User-defined conditions which must exist before a job is submitted. A major use of prerequisite conditions is to establish job dependencies.
Prerequisite conditions
The condition and resource requirements of a job are defined in the job scheduling definition. Existing and available prerequisite conditions and resources are tracked by the CONTROL-M monitor in a file called the IOA Conditions/Resources file. When the prerequisite conditions and resources required by a job are available, the job can be submitted by the monitor (if all other runtime scheduling criteria are satisfied).
Immediate Detection and Notification of Problems: Shout Facility

When a problem or an unexpected situation/delay occurs, CONTROL-M can notify the appropriate personnel. These situations/problems are detected by analysis of a jobs sysout. Notification is issued via the Shout facility, which can send messages to a variety of destinations including the operator console, a TSO user, and the IOA Log file. CONTROL-M can also be instructed to issue a Shout message in the event an exception occurs at time of job submission and/or during job execution (e.g., a job completes before, or later than, its anticipated completion time).
16
History Jobs File

During New Day processing, jobs which have ended OK or expired (according to job scheduling definition parameters) are deleted from the Active Jobs file. If CONTROL-R is installed, these jobs can be placed in the History Jobs file during New Day processing. This is an optional feature which can be activated by the IOA administrator. (Activation of this feature is described under parameter HIST in Section 3 of the IOA Installation Guide.) Jobs in the History Jobs file can be restored (by request) to the Active Jobs file, for subsequent restart. Jobs remain in the History Jobs file until they are deleted according to criteria defined in the job scheduling definition. The contents of the History Jobs file can be viewed from the History Environment screen (described in Section 2 of this manual).
Journaling and Restoration Capability

The CONTROL-M Journal file collects data about changes occurring in the CONTROL-M Active Jobs file and IOA Conditions/Resources file during the CONTROL-M working day. The Journal file is initialized each day during New Day processing. From that point on, for the rest of the working day, the CONTROL-M monitor records all job processing activities (which impact the CONTROL-M Active Jobs file) and all prerequisite condition additions and deletions (to/from the IOA Conditions/Resources file) in the Journal file. If the CONTROL-M Active Jobs file and (optionally) the IOA Conditions/Resources file need to be restored (e.g., following a system crash), utility CTMRSTR can be run to restore the files (from the data in the Journal file) to the status they were in as of any specific time after the last run of the New Day procedure. The CONTROL-M Journal file is initialized each day during New Day processing. Therefore, the time at which the New Day procedure initialized the Journal file is the earliest time to which the CONTROL-M Active Jobs file or the IOA Conditions/Resources file can be restored. Journaling and Restoration is an optional feature which can be activated by the IOA administrator. It is described in Section 3 of the IOA Administrator Guide. (Activation of this feature is described under parameter JRNL in Section 3 of the IOA Installation Guide.)
IOA Log Facility

Messages issued by CONTROL-M are written to the IOA Log file. The IOA Log file is a repository for messages issued by all IOA products. Through the IOA Log facility, the user can examine messages issued by CONTROL-M during the processing of a job.
17
Automated Job Post-Processing

Once the job has executed, the CONTROL-M monitor implements the post-processing instructions defined in the job scheduling definition. Post-processing instructions can be defined for virtually any situation (job ended successfully, job abended, a particular condition code occurred in a particular step, etc.). As part of post-processing, CONTROL-M can do the following:
Add a prerequisite condition to, or delete a prerequisite condition from, the IOA Conditions/Resources file. This can trigger or prevent the submission of a job in the Active Jobs file. Force the placement of a job scheduling definition into the Active Jobs file (regardless of the jobs basic scheduling criteria). Send (shout) a specified message to a specified location via the Shout facility. Change the final status of a job to OK or NOTOK. Handle the jobs SYSOUT. This includes changing its class, deleting it, rerouting it to another node, releasing it for printing, or copying it to another location. Invoke a CONTROL-B rule (if CONTROL-B is active). Rerun a job. Perform an MVS job restart (see parameter OUT in Section 3 of this manual). Perform a CONTROL-R job restart (if CONTROL-R is active). Automatically archive certain portions of the jobs output (if CONTROL-R is active).
Utilities
Utilities provided with CONTROL-M are used to perform a functions and generate reports which assist in the efficient use batch utilities are described in Section 6 of this manual, and described in Section 9 of the IOA Administrator Guide. Online Section 2 of this manual. variety of management of CONTROL-M. Several other batch utilities are utilities are described in
Handling Jobs in the NJE Network

The CONTROL-M monitor handles the control of complex distributed production environments where jobs may be routed for execution to different nodes of the NJE network according to the business needs of the enterprise. CONTROL-M differentiates between host and remote nodes in the NJE network as follows: Host node Remote node NJE network node under which the CONTROL-M monitor is active and the NJE job is submitted to MVS/JES by the monitor. NJE network node to which a job was sent from the host node.
An NJE job is a job submitted by the CONTROL-M monitor for execution on a remote node. CONTROL-M can detect the status of jobs running on a remote node so that once these jobs finish executing, CONTROL-M can assign a status to them.
18
Handling External Events: CMEM Facility

External events are events in the system (e.g., submission of a job) which occur outside the control of the CONTROL-M monitor. The CONTROL-M Event Manager (CMEM) facility enables CONTROL-M to respond to and handle such events. Through rules defined online via the CMEM Rule Definition facility (described in Section 2 of this manual), the user specifies actions CONTROL-M should perform in response to external events. The following types of events are handled by the CMEM facility: Job Arrival Job End Dataset Event Step Arrival of a job on the JES spool, from any source. Completion of a job, regardless of its source. Either the setting of a dataset disposition at deallocation time or the occurrence of a NOT CATLGD 2 event. Termination of a procedure (and optionally, a program) step.
The following actions can be performed by the CMEM facility:
Force one or more CONTROL-M jobs. (See Job Ordering and Job Forcing later in this section.) Add prerequisite conditions to, or delete prerequisite conditions from, the IOA Conditions/Resources file. Stop the job in which the event occurs. If CONTROL-O is active at the site, the following actions can also be performed: Invoke a CONTROL-O rule. Send a message to a specified location via the CONTROL-O Shout facility.
Through the CMEM facility, a job submitted outside the control of the CONTROL-M monitor (e.g., a job submitted by a TSO user) can be brought under the control of the CONTROL-M monitor. Such a job is called an On Spool job, and the control of On Spool jobs is one of the most important functions of CMEM. The CMEM facility, and On Spool jobs, are described in Section 4 of this manual.
Scheduling Jobs via Calendars: Calendar Facility

Specification of scheduling criteria for jobs can be simplified by using calendars. A calendar is a defined schedule (e.g., Mondays through Fridays in each week in each month) which can be applied to jobs. Calendars are defined in the Calendar facility. Each calendar is assigned a unique name which can be specified in job scheduling definitions. A particular calendar (i.e., schedule) only need be defined once. Specifying calendars name in job scheduling definitions causes that calendar to be used to schedule those jobs.
19
Two types of calendars can be defined: regular and periodic. Regular calendars consist of scheduling dates or days (of the week) which can be defined according to monthly patterns. Examples: WEEKDAYS WEEKENDS QUARTERLY Schedules jobs each Monday through Friday in each month. Schedules jobs on every Saturday and Sunday in each month. Schedules jobs on the last date in each quarter: March 31, June 30, September 30, December 31. calendar
Regular calendars are especially useful when many jobs have the same schedule. Defining the schedule once in a calendar, and specifying the calendar name in the job scheduling definition of the jobs with that schedule, makes it unnecessary to individually define that schedule in each job scheduling definition. Periodic calendars are especially useful when scheduling dates do not easily conform to fixed date/day of the week/month patterns. Example: PAYCAL Calendar used for jobs which are scheduled every other Wednesday (e.g., payroll jobs). Scheduling occurs on the first, third, and (if there is one) fifth Wednesday of some months. Scheduling may occur on the second and fourth Wednesday of other months.
The IOA Calendar facility is described in Section 2 of this manual.
Accumulating Statistics: Statistics Facility

As part of the post-processing for each job, CONTROL-M determines the elapsed run time of the job. All accumulated information regarding job execution, including the elapsed run time, is written to the IOA Log file. Periodically, a statistics utility can be used to scan and analyze the IOA Log file. This utility gathers information about each jobs start time, elapsed run time, CPU utilization time, etc. The utility places this information in the Statistics file, where averages of these values can be maintained for each job. Statistics facility averages can be used for several purposes:
Determine if a jobs execution time falls outside of a statistically normal range of time (which would indicate an execution delay or problem). Calculate DUE-IN time for use by the Deadline Scheduling facility (discussed later in this section). Simulate job executions and forecast the impact of changes to the system (described briefly below).
1 10
Simulating Job Execution and Forecasting Resource Usage: Simulation and Forecasting Facility
Using statistics accumulated by the Statistics facility, the Simulation and Forecasting facility simulates the actions of the CONTROL-M monitor under the conditions specified in simulation parameters. The Simulation and Forecasting facility enables you to forecast anticipated job load for a specified time in the future, and to forecast the effects possible changes to the system might have. For example, the impact of:
Removing four tape drives. Increasing CPU power by 30%. Changing the time at which certain jobs are executed.
The Simulation and Forecasting facility can improve the efficiency of your site. It can help with resource and configuration decisions, and it can help with the planning of workload scheduling to achieve maximum utilization of resources.
Automatic Tape Adjustment

The Automatic Tape Adjustment facility collects and analyzes statistics regarding tape drive usage, and automatically allocates the appropriate number of tape drives at job order time. (This facility overrides any tape drive Quantitative resource value specified in the job scheduling definition.) The Automatic Tape Adjustment facility is operational only if optional wish WM2744 is installed. For more information, see Tape Device Usage Statistics in the description of the Statistics screen in Section 2, and the description of parameter RESOURCE in Section 3, of this manual.
Reporting Facility
CONTROL-M supports a comprehensive reporting facility, which can produce the following types of reports:
Keystroke Language Reports These are reports generated via the Keystroke Language (KSL). KSL is a general purpose reporting language, based on the IOA Online facility, capable of producing numerous reports from the database (described later).
Special Purpose Reports These reports include the Job Flow reports which are generally used to track the dependencies between jobs, and the Job Plan reports which are used to anticipate which jobs will be scheduled each day.
Sample reports are provided in the IOA SAMPLE library. The Reporting facility is described in Section 8 of this manual.
1 11
Introduction: CONTROL-M: A Functional Approach CONTROL-M Support For CONTROL-M/WorkLoad
CONTROL-M Support For CONTROL-M/WorkLoad

CONTROL-M provides scheduling support for pipes at sites which have CONTROL-M/WorkLoad installed. A pipe is a processor storage buffer which enables data to be passed between applications without using DASD or tape. CONTROL-M/WorkLoad uses pipes to replace sequential job processing with parallel processing wherever feasible. Jobs and job steps normally run sequentially because they depend on data files which become available only after the application which creates them completes execution. When pipes are used, an application does not need to finish running before the data it generates is available to other applications. This significantly reduces I/O operations and delays, and speeds up processing, because pipes enable movement of data via processor storage instead of writing and reading data to/from external storage. CONTROL-M scheduling support for CONTROL-M/WorkLoad pipes consists of the following components:
Job scheduling definition support. Enhanced runtime scheduling algorithm.
These are described below.
Job Scheduling Definition Support

A PIPE statement can be specified in the CONTROL-M job scheduling definition for each pipe accessed by the job. Each PIPE statement contains the pipe (dataset) name. A participants job scheduling definition will include a PIPE statement for each pipe accessed by the job.
Enhanced Runtime Scheduling Algorithm

Jobs sharing a pipe are called pipe participants. CONTROL-M recognizes each set of interrelated pipes and participants as a single, comprehensive unit called a Collection. All pipe participants are submitted concurrently, after verification that all required resources (e.g., prerequisite conditions, Quantitative resources) are available. This method ensures that participants will not wait for other participants to start executing (e.g., at synchronization points). For more information, see CONTROL-M/WorkLoad Considerations in Section 6 of this manual.
1 12
Introduction: CONTROL-M: A Functional Approach Online User Interface to CONTROL-M
Online User Interface to CONTROL-M

Until now, we have seen how CONTROL-M automates the production environment and we have discussed a number of available facilities which enhance CONTROL-Ms functionality. However, as mentioned earlier, CONTROL-M provides an online user interface which enables the user to:
Interface with most of the previously described facilities. Immediately access up-to-date information from the production environment. Intervene in the process of production management.
The online user interface is provided through online facilities which are accessed via the IOA Primary Option menu. Certain online facilities are unique to CONTROL-M, and other facilities are shared by many or all IOA products. All IOA and CONTROL-M online facilities are discussed in detail in Section 2 of this manual. They are all outlined briefly on the following pages. Note Your IOA administrator can limit the options displayed on a user-by-user basis and can modify option numbers and customize option descriptions. Default options are discussed in this overview.
Scheduling Definition Facility

The CONTROL-M Scheduling Definition facility is accessed through option 2 of the Primary Option menu. It is the main online facility for creating / defining / modifying / deleting:
Scheduling tables. Job scheduling definitions.
In addition, this facility can be used to: Edit a jobs JCL. Manually order or force jobs. Ordering places the requested job in the Active Jobs file only if its basic scheduling criteria are met. Forcing places the requested job in the Active Jobs file regardless of its basic scheduling criteria.
Graphically display a jobflow of the jobs in a table.
1 13
Active Environment (Status) Screen: Online Tracking and Control Facility

The Online Tracking and Control facility is accessed through option 3 of the IOA Primary Option menu. It is the main user interface to the monitoring of the jobs scheduled for the day. This facility consists of a number of screens, each providing the user with relevant information and options. The main screen of this facility is the Active Environment screen. This screen is also called the Status screen because it displays the status of each job order in the Active Jobs file. All screens and windows available in the Online Tracking and Control facility are accessed via the Status screen. In the Online Tracking and Control facility, you can perform the following functions:
View the status of each job order in the Active Jobs file. Place a job in HELD status or free a HELD job. Delete a job order. Obtain a statistical overview of the status of jobs in the Status screen. See the reasons why a job in the Active Jobs file has not been submitted. If job submission is held up due to missing prerequisite conditions, you can optionally add those conditions manually. Display a jobs Log file to view all messages issued for the job. Zoom in on the parameters of a job order. This includes not only the job scheduling definition parameters, but also parameters determined by the CONTROL-M monitor at runtime. Manual update of some of these parameters for the job order is permitted. Confirm the scheduling, rerun, or restart (if CONTROL-R is active), of a job which has been defined as requiring manual confirmation. View the execution history of all orders of a job, and view the job order sysouts. View the accumulated statistics of successful executions of a job. View the list of job dependencies for a specific job (i.e., the predecessor/successor jobs of the selected job) and perform manual job flow adjustment (e.g., priority adjustment).
You can filter which jobs in the Active Jobs file are displayed in the Status screen.
CMEM Rule Definition Facility

The CMEM Rule Definition facility is accessed through option C of the IOA Primary Option menu. CMEM rules enable CONTROL-M to respond to external events. The CMEM Rule Definition facility is an online facility which enables the user to create, define, modify and delete:
CMEM rule tables. CMEM rules.
The user can load rule tables to memory from the CMEM Rule Definition facility. (Rule tables can also be loaded to memory via an operator command.)
1 14
IOA Conditions/Resources Screen

The IOA Conditions/Resources screen is accessed through option 4 of the IOA Primary Option menu. It displays the IOA Conditions/Resources file, which contains the list of all existing prerequisite conditions, Quantitative resources and Control resources. The IOA Conditions/Resources screen enables the user to:
View the IOA Conditions/Resources file. Add or delete prerequisite conditions and/or resources. Change the available quantity of Quantitative resources.
IOA Log Screen

The IOA Log screen, accessed through option 5 of the IOA Primary Option menu, displays the IOA Log file. The IOA Log file contains messages which record every significant event in the life of all jobs/started tasks/rules/missions etc. that are under the control of IOA products. This includes messages generated for normal processing (e.g., job submitted) and error conditions (if any) encountered during processing, and messages directed to the Log file from the Shout facility. The user can filter IOA Log file contents displayed in the IOA Log screen.
IOA Manual Conditions Screen

The IOA Manual Conditions screen is accessed through option 7 of the IOA Primary Option menu. It displays the IOA Manual Conditions file which contains the list of prerequisite conditions which must be added manually. These are IN conditions which are required by scheduled jobs but will not be added by scheduled jobs (i.e., these conditions are not listed as OUT or DO COND conditions in the Active Jobs file). These conditions fall into the following categories:
Conditions which are never automatically added by scheduled jobs because manual confirmation is always desired. For example, TAPE-ARRIVED. Conditions which are normally added automatically by scheduled jobs, but the jobs which add them are not scheduled.
For the conditions listed in the Manual Conditions screen to be added to the IOA Conditions/Resources file, manual intervention is required. The Manual Conditions list is described in Section 6 of this manual. The IOA Manual Conditions screen enables the user to:
View the list of Manual Conditions. Select and add listed conditions, as desired, to the IOA Conditions/Resources file.
1 15
IOA Calendar Facility

The IOA Calendar facility is accessed through option 8 of the IOA Primary Option menu. IOA calendars allow definition of common scheduling patterns which simplify the specification of basic scheduling criteria in job scheduling definitions. The IOA Calendar facility enables the user to create, define, modify and delete IOA calendars.
Online Utility Screens (Under ISPF)

When CONTROL-M and other IOA products (if any) are active under ISPF, a number of utilities and facilities can be activated online. The IOA Online Utilities menu is accessed through option 6 of the IOA Primary Option menu (under ISPF). The IOA Online Utilities menu displays available utilities from which the desired utility or facility can be selected.
1 16
Introduction: CONTROL-M Concepts IOA Core and CONTROL-M Repository
CONTROL-M Concepts
Having discussed CONTROL-M from a functional viewpoint, and having briefly outlined the online user interface to CONTROL-M, it is now worthwhile to discuss certain important concepts in CONTROL-M functioning.
IOA Core and CONTROL-M Repository

A differentiation is made between files belonging to a particular IOA product such as CONTROL-M, and IOA files which are shared among IOA products. Shared IOA files are collectively referred to as the IOA Core. The IOA Core consists of the following files:
IOA Log file File in which all events related to job processing are recorded. IOA Conditions/Resources file File which lists the available conditions and resources identified and tracked by the CONTROL-M monitor.
IOA Manual Conditions file File listing prerequisite conditions which must be added manually (i.e., prerequisite conditions required by jobs which have been ordered to the Active Jobs file and which are not automatically added by other jobs in the Active Jobs file).
IOA Calendar tables Files containing IOA calendar definitions. Dynamic Destination table File containing a list of destinations for messages issued by the IOA Shout facility.
Files belonging to a particular IOA product are called that products repository. The CONTROL-M Repository consists of the following files:
Active Jobs file File used to hold copies of the job scheduling definitions of those jobs which have been ordered that working day.
Scheduling tables Files containing job scheduling definitions. CMEM Rule tables Files containing CMEM rule definitions. Job Statistics file File containing the execution statistics of all jobs. Job Network file File containing dependency information about the jobs in the Active Jobs file.
1 17
Introduction: CONTROL-M Concepts Date Definition Concepts
History Jobs file File containing jobs which ended OK or expired.
Journal file File containing data about changes to the CONTROL-M Active Jobs file and the IOA Conditions/Resources file, which can be used for Restoration purposes.
Date Definition Concepts

IOA recognizes the following types of date definitions. Depending on the IOA product, either all of them, or some of them, are relevant. All these types are relevant for CONTROL-M:
System date Date as supplied by the operating system. This date should be the actual calendar date starting and ending at midnight.
Working date Many sites do not use midnight as the formal time for changing to a new date. A site, for example, may determine that all processing performed between the hours of midnight and 6:00 a.m. belongs to the previous days processing. In this case, the installation working date at the site changes at 6:00 a.m., not at midnight. The working date (i.e., the time at which the date changes at the site) is defined in the CONTROL-M installation parameters. New Day processing generally begins at the start of the new working date.
Original scheduling date Job orders and prerequisite conditions managed by CONTROL-M are assigned an original scheduling date (referred to as ODATE). For a job, the ODATE is the working date on which the job should be scheduled for execution. Example A computer is down for repairs on February 2nd and 3rd. When it is brought up on February 4th, a two-day backlog of jobs must be run in addition to the jobs of the current day. When the Daily procedure scans scheduling tables on February 4th, it places job orders in the Active Jobs file for all three days. Jobs which should have run on February 2nd are assigned an ODATE of February 2nd, jobs for February 3rd are assigned an ODATE of February 3rd, etc. In this manner, each job is executed as if it had run on its originally-scheduled working date.
1 18
Introduction: CONTROL-M Concepts Date Standards and Date Field Formats
Date Standards and Date Field Formats

Date standards and date field formats are indicated in the manual by the following symbols: dd mm yy yyyy Day of the month (01-31) Month (01-12) Last two digits of the year Four digits of the year
1
Whether a field holds a 4-character date (month and day), a 6-character date (month, day and year) or an 8-character date (month, day and year) depends on the field. However, the format of the 4-, 6- or 8-character date depends on the installation-defined date standard in use at the site. IOA supports three date standards. Each standard has an 8-character format, a 6-character format and a 4-character format. Only one standard is defined at any site. These IOA-supported date standards are described in the chart below. Standard MDY DMY YMD 8-Character Date mmddyyyy ddmmyyyy yyyymmdd 6-Character Date mmddyy ddmmyy yymmdd 4-Character Date mmdd ddmm mmdd
1 If a 2-digit year is specified which is less than 56, IOA assumes the 21st century (e.g., 2015 if yy=15). Otherwise, IOA assumes the 20th century (e.g., 1980 if yy=80).
1 19
Introduction: CONTROL-M Concepts Job Ordering and Job Forcing
Job Ordering and Job Forcing

Job ordering is the placing of a job scheduling definition in the Active Jobs file when the jobs basic scheduling criteria are satisfied. Most production jobs are automatically ordered during New Day processing. However, jobs can be manually ordered, as well. Job forcing is the placing of a job scheduling definition in the Active Jobs file regardless of the jobs basic scheduling criteria. Although any job can be forced, job forcing is generally requested for special purpose, or exception, jobs which are not normally scheduled:
Jobs can be automatically forced as part of the post-processing of another job. For example, a particular job may be required only if a certain other job abends. In this case, it is forced during the post-processing for the abended job. Jobs can also be forced manually. For example, a routine job which is generally ordered automatically according to its scheduling criteria can be manually forced, if required, on a day it is not normally scheduled.
Rerun and Restart

Rerun and restart are two distinct, though related, concepts. Rerun is the re-execution of a job from the beginning. Job rerun is a CONTROL-M feature. Restart is the re-execution of a job from a predefined step. Restart is usually performed from the step that failed, although it can be performed from an earlier step, if necessary. Restart utilizes the successful steps from the failed job execution, thereby limiting the amount of processing required to complete successful job execution. This results in lower CPU overhead, and can make a big difference in the timely completion of processing. A basic MVS restart capability is available (see the description of parameter OUT in Section 3 of this manual). This type of restart starts execution of the job from the failed step. However, no auxiliary restart functions are performed. By contrast, at sites in which CONTROL-R is installed, CONTROL-R restart is available. In addition to performing restart from the desired step, with the capability of automatic step rollback when necessary, CONTROL-R automatically performs auxiliary restart functions. These include the cataloging and scratching of datasets, prevention of NOT CATLGD 2 errors, etc. Instructions for rerun and restart can be defined in the job scheduling definition. Rerun is defined via the DO RERUN statement. Restart is defined via the DO IFRERUN statement. They can be defined to be performed automatically or to be performed upon manual confirmation. For more information, see the DO RERUN and DO IFRERUN statements in Section 3 of this manual, and see the CONTROL-R User Manual.
1 20
Introduction: CONTROL-M Concepts Order ID
Order ID
CONTROL-M can handle multiple orders of the same job. To distinguish between the job orders, CONTROL-M assigns each job order a unique order ID. Therefore, it is not uncommon to see the same job name with multiple order IDs, each representing a different job order, in the Status screen.
SYSDATA
SYSDATA is the term used to designate the data in the following three job sysout datasets: 1) job log (console messages); 2) expanded JCL; 3) system output messages. SYSDATA datasets are usually produced for each execution of a job or started task. However, not all three datasets are necessarily present in all cases. For example, in JES2, if a job is canceled by the operator before execution, the system output messages dataset might not be produced. For jobs, the output class for this data is defined by one of the following:
MSGCLASS parameter on the job card, which is added or overwritten by CONTROL-M during job submission. JCL job-level //OUTPUT statement using the JESDS subparameter. Default values defined in JES initialization parameters.
For started tasks, the output class for this data is defined in JES initialization parameters. When CONTROL-R is installed, it uses the SYSDATA to analyze the execution of a job order, beginning with the archived SYSDATA of the most recent non-restarted run.
Handling of Job Groups

Normally, the handling of each job in a table is independent of the handling of the other jobs in the table. Each job is handled according to the criteria specified in its own job scheduling definition. However, the Scheduling Definition facility also supports the handling of jobs as a group. Such jobs are defined in a special scheduling table, called a Group scheduling table. Each Group scheduling table has a special job scheduling definition, called a Group Entity. Group handling criteria for the entire group of jobs are specified in this Group Entity. These include:
Basic Scheduling criteria Runtime Scheduling criteria Post Processing actions
Scheduling criteria to be applied to jobs in the group. Required runtime criteria for all scheduled jobs in the group. Actions to be performed when all scheduled jobs in the group have finished executing with the appropriate status.
1 21
Introduction: CONTROL-M Concepts Prerequisite Condition Concept
Prerequisite Condition Concept

General
The prerequisite condition concept is one of the key concepts of CONTROL-M production control. Prerequisite conditions enable the establishment of job dependencies and, when a job normally requires manual intervention (e.g., determination that a cartridge arrived on-site), ensures that the manual conditions will be satisfied before the job is submitted. A prerequisite condition is a user-defined, descriptive name given to a certain situation or condition. Prerequisite conditions can be specified in any of three types of statements in a job scheduling definition: IN statements OUT statements DO COND statements These statements must be satisfied (i.e., the prerequisite condition must exist) before the job can be submitted. These statements are performed (i.e., the prerequisite conditions are added or deleted) only when the job ends OK. Whether or not these statements are performed (i.e., the prerequisite conditions are added or deleted) depends on the execution results of the job. (DO statements in a job scheduling definition accompany ON statements. The ON statements define step and code criteria. If the specified code criteria are satisfied for the specified step(s), the accompanying DO statements are performed.) In its most basic form, a prerequisite condition is defined in an IN statement in one job, and as an OUT (or DO COND) statement in another job. This makes the execution of the one job dependent on the execution of the other job. Example
1 22
Payroll-calculating job PAYCALC must be run before Payroll-check-printing job PRINTPAY. To create the necessary job dependency, a prerequisite condition is defined as follows:
Prerequisite condition PAYCALC-ENDED-OK is defined as a runtime scheduling criterion in the job scheduling definition for job PRINTPAY. Prerequisite condition PAYCALC-ENDED-OK is defined as a post-processing parameter for job PAYCALC, only when job PAYCALC terminates successfully. Because the condition required by job PRINTPAY will not be created unless job PAYCALC terminates successfully, job PRINTPAYs dependency on job PAYCALC is established.
Job dependencies do not have to be as simple as the above example illustrates. An almost unlimited number of conditions and job dependencies can be created:
Jobs can be dependent on more than one prerequisite condition. Jobs can add and/or delete more than one prerequisite condition. The same prerequisite condition can be added by more than one job (caution should be used). The same prerequisite condition can be used as an IN condition for more than one job.
In Group scheduling tables (described earlier in this section), prerequisite conditions can be defined as IN, OUT and/or DO COND conditions in the Group Entity. In this case, they apply to the entire set of scheduled jobs.
Prerequisite Condition Dates

IN, OUT, and DO COND statements provide a field for specifying a date to accompany each prerequisite condition. An OUT or DO COND prerequisite condition which is added with a particular date cannot satisfy the same IN prerequisite condition if the IN statement specifies a different date. Example JOB_A and JOB_B each run daily, and JOB_B is dependent on JOB_A. (JOB_A has prerequisite condition JOB_A_ENDED_OK as an OUT condition, and JOB_B has the same condition as an IN condition.) The date associated with a condition is important because it is absolutely necessary that, on a given day, JOB_B not be triggered by an occurrence of the condition JOB_A_ENDED_OK from a previous day. Certain Date keywords can be specified in place of, and resolve to, actual date values. For example, keyword ODAT is automatically replaced by the jobs original scheduling date. Another important keyword for use in place of an actual date is STAT. STAT is used as a date reference for conditions which are static (i.e., not date-dependent).
1 23
For example, condition IMS_ACTIVE is added when IMS is brought up, and only deleted if IMS is brought down. The date of the condition is irrelevant to jobs requiring that condition. Therefore, this condition would be referenced with a date value of STAT. Note Prior to IOA Release 5.0.0, date 0101 was (by convention) used to indicate static dates. This convention can still be used, but STAT is the preferred specification because it can never be confused with an intended date value of 0101.
Deleting Conditions
The last job to require a particular prerequisite condition (i.e., in an IN statement) can also mark that condition for deletion (i.e., in an OUT statement). The deletion of unnecessary conditions can serve the following purposes:
It can eliminate unnecessary clutter from the IOA Conditions/Resources file (and screen). When dependent jobs are scheduled multiple times each day, it can prevent the execution of the earlier-scheduled predecessor job from incorrectly causing the submission of the later-scheduled successor job.
Conditions Requiring Manual Intervention

Prerequisite conditions can be used to ensure that a required manual operation has been performed. The following example illustrates such a condition: Example The job scheduling definition of JOB-A specifies prerequisite condition TAPE-ARRIVED as runtime scheduling criteria. When the operator sees that JOB-A is waiting for this condition to be satisfied, the operator can verify that the required external tape has arrived at the site, and then use the online facility to manually add the condition to the IOA Conditions/Resources file (via the Manual Conditions screen, the IOA Condition/Resources screen, or the Why screen). The job can then be submitted by CONTROL-M.
Maybe Jobs
In some cases, job dependencies created by prerequisite conditions are desired only if the predecessor jobs are scheduled. If the predecessor jobs are not scheduled, the dependencies should be ignored. Such dependencies are called Maybe dependencies, and the unscheduled predecessor jobs which should be ignored if they are not scheduled are called Maybe jobs. Conditions set by unscheduled Maybe jobs appear in the Manual Conditions file. The Manual Conditions file and the handling of Maybe jobs is discussed in Section 6 of this manual.
1 24
Introduction: CONTROL-M Concepts Quantitative and Control Resources
Quantitative and Control Resources

To prevent bottlenecks and help guarantee successful execution of jobs, CONTROL-M provides tools to ensure that a job is not submitted for execution until all resources required by the job are available.
Quantitative Resources
Specification of Quantitative resource requirements for a job provides a solution for the allocation of quantitative computer resources (e.g., cartridge drives, CPU utilization, database access-rate). It increases computer throughput by controlling access to these resources, thus preventing execution bottlenecks. CONTROL-M maintains a continuously-updated status of the sites Quantitative resources in the IOA Conditions/Resources file. When a Quantitative resource is specified for a job, CONTROL-M determines if a sufficient quantity of the specified resource is available before submitting the job. When the job is submitted, the specified quantity of resource is allocated to that job and is unavailable to other jobs. When the job finishes executing, the resource is made available to other jobs. The quantity of each resource which is available in the data center is specified using CONTROL-M utilities. An authorized user can dynamically change these quantities manually from the IOA Conditions/Resources screen.
Control Resources
Specification of resource control requirements for a job provides a solution for the problem of resource sharing between different jobs. The mode (Exclusive or Shared) in which a resource is required by a job can be specified. For example, a job which reads a database without performing updates can access the database in Shared mode; any other job requiring read-only access to the database can access the database at the same time. Conversely, a job which updates the database may require Exclusive control of the database at the time of update such that no other jobs can share the database. In the example just presented, the database can be defined as a Control resource, and the type of control required by the job (Exclusive or Shared) can be specified for the resource. CONTROL-M considers the mode of resource usage required when allocating Control resources and prevents jobs whose resource usage is incompatible from executing simultaneously.
1 25
Introduction: CONTROL-M Concepts Job Priority
Job Priority
The job scheduling definition can include a specification of an internal priority for the job. When competing for the same resource, jobs with higher priority take precedence over jobs with lower priority. Users can also assign a critical path priority to jobs which must be submitted with the least delay possible. A job with critical path priority is allocated required resources as the resources become available. When all its required resources are available, the job is submitted. Non-critical jobs are not allocated resources until all required resources are available at the same time.
Automatic Job Flow Adjustment

Predecessor/successor job flows are established through the use of prerequisite conditions which are defined in the job scheduling definition. Successor and predecessor jobs are identified as either immediate or eventual, relative to a specified job:
An immediate predecessor/successor relationship exists between jobs when one job is directly dependent on prerequisite condition(s) added by the other job. An eventual predecessor/successor relationship exists between jobs if their dependency is indirectly established through a chain of immediate predecessor/successor jobs.
From the network of predecessor/successor jobs, critical paths can be identified. A critical path is a chain of jobs which must be executed in their appropriate sequence in order for a specified job to run. A job can have more than one critical path (if different jobs set the same OUT condition, or if a job has OR logic in its IN conditions). The Job Dependency Network screen, accessed via the Status screen, enables you to view the network of predecessor/successor jobs for a specified job and determine the critical paths for the job. Although it is prerequisite conditions which define predecessor/successor job relationships, the actual job flow along a critical path can be greatly impacted by the following runtime scheduling criteria in the job scheduling definition: PRIORITY DUE OUT As mentioned earlier in Job Priority, a PRIORITY value affects the jobs selection order (relative to other jobs). Specifies the time by which the job should finish executing.
In some cases, it may become desirable to adjust the priorities or due-out times of certain job orders.
1 26
Introduction: CONTROL-M Concepts Automatic Job Flow Adjustment
Examples
A high priority successor job is waiting for the submission (and completion) of a lower priority predecessor job. A predecessor job will not terminate early enough for a successor job to terminate by the successors due-out time.
Both types of job flow adjustments can be requested from the Job Dependency Network screen:
Priority Propagation The priority value of each non-Held predecessor/successor job is checked and (if necessary) modified so all jobs in the chain have a priority, and no job has a lower priority than any of its successor jobs.
Deadline Adjustment Starting with the latest eventual successor job in the job flow, the anticipated elapsed time (i.e., anticipated execution time) is subtracted from the DUE OUT time to determine DUE OUT time of that jobs immediate predecessor(s). This process of subtracting elapse times of a job to determine the DUE OUT time of the immediate predecessor job(s) is repeated until the DUE OUT time of the initial or current job is determined. If the user specified an ELAPSE time value in the Online Tracking and Control facility Zoom screen, this value is used for the above calculation. If the user did not specify an ELAPSE time value, the anticipated elapse time is determined by the average runtime taken from the CONTROL-M Statistics file.
The following points should also be noted:
By subtracting a jobs ELAPSE time from its DUE OUT time, the CONTROL-M monitor calculates a DUE IN time (i.e., time by which the job should be submitted) for each job. This value is also displayed in the Job Dependency Network screen. The ELAPSE, DUE OUT, DUE IN and PRIORITY values for a job are also displayed in the Zoom screen, which is accessed via the Status screen. DUE IN, DUE OUT and PRIORITY values can also be manually modified in the Zoom screen, but it is recommended that this not be done, and that automatic job flow adjustment be requested instead.
1 27
Introduction: CONTROL-M Concepts Automatic Job Flow Adjustment
1 28
Section 2: Online Facility

IOA Features .................................................................................................................................2-1 General........................................................................................................................................2-1 Customization........................................................................................................................2-1 Environment Support............................................................................................................2-1 Terminal Support ..................................................................................................................2-2 Color Support.........................................................................................................................2-2 Prefixing.................................................................................................................................2-3 Character Masking................................................................................................................2-3 IOA Entry Panel .........................................................................................................................2-4 IOA Primary Option Menu ........................................................................................................2-5 IOA Version Information ....................................................................................................2-10 Multi-screen Control.................................................................................................................2-11 Fast Exit from the IOA Online Facility .............................................................................2-11 Screen Layout ...........................................................................................................................2-12 Commands and PFKeys ...........................................................................................................2-13 Scrolling Commands ...........................................................................................................2-15 LOCATE Command.............................................................................................................2-15 FIND Command ..................................................................................................................2-16 CANCEL and RESET Commands......................................................................................2-16 Online Help ...............................................................................................................................2-17 AutoRefresh Mode ....................................................................................................................2-18 Cancelling AutoRefresh Mode ............................................................................................2-18 IOA Under ISPF .......................................................................................................................2-19 IOA TSO Command Processor Screen.....................................................................................2-20 Transfer of Control Between the TSO Application and the IOA Online Facility ............2-21 Scheduling Definition Facility .............................................................................................. 2-22 General......................................................................................................................................2-22 Accessing the Scheduling Definition Facility ....................................................................2-22 Handling of Job Groups ......................................................................................................2-23 Creating Tables ...................................................................................................................2-24 Creating Job Scheduling Definitions..................................................................................2-25 Performing Operations on Tables and Jobs .......................................................................2-25 Entry Panel ...............................................................................................................................2-27 Fields of the Entry Panel ....................................................................................................2-27 Search Window ....................................................................................................................2-28
Table List Screen ..................................................................................................................... 2-30 Options of the Table List Screen........................................................................................ 2-30 Commands of the Table List Screen .................................................................................. 2-31 Job List Screen ......................................................................................................................... 2-32 Format of the Job List Screen ............................................................................................ 2-33 Commands of the Job List Screen...................................................................................... 2-33 Options of the Job List Screen ........................................................................................... 2-34 Job Scheduling Definition Screen Defining Schedules....................................................... 2-35 Parameters of the Job Scheduling Definition Screen ....................................................... 2-36 Scheduling Definition for Group Entities ......................................................................... 2-43 Commands of the Job Scheduling Definition Screen........................................................ 2-46 Editing Job Scheduling Definitions in the Edit Environment......................................... 2-47 Job Documentation ............................................................................................................. 2-48 Auto-Save and Saving Documentation.............................................................................. 2-49 Exiting the Scheduling Definition Facility............................................................................. 2-50 Exiting the Job Scheduling Definition Screen .................................................................. 2-51 Exiting the Job List Screen ................................................................................................ 2-51 Exiting the Table List Screen ............................................................................................ 2-52 Exiting the Entry Panel ..................................................................................................... 2-52 Ordering (Scheduling) Jobs..................................................................................................... 2-53 Copying Jobs to Another Table ............................................................................................... 2-55 Deleting Tables ........................................................................................................................ 2-56 Displaying Graphic Jobflow .................................................................................................... 2-57 Displaying a Job Scheduling Plan .......................................................................................... 2-59 Job Scheduling Plan Screen ............................................................................................... 2-60 Tracking and Control Facility ............................................................................................... 2-61 General ..................................................................................................................................... 2-61 Status Screen ........................................................................................................................... 2-62 Display Types of the Status Screen ................................................................................... 2-63 Format of the Status Screen .............................................................................................. 2-64 Commands of the Status Screen ........................................................................................ 2-66 Options of the Status Screen.............................................................................................. 2-69 Job Statuses ........................................................................................................................ 2-71 Filtering the Status Screen Display .................................................................................. 2-74 Global View Screen .................................................................................................................. 2-79 Fields of the Global View Screen ....................................................................................... 2-80 View Graph Screen .................................................................................................................. 2-81 View Graph Screen Format for Color Terminals .............................................................. 2-81 View Graph Screen Format for Non-color Terminals....................................................... 2-83
Why Screen ...............................................................................................................................2-84 Adding Conditions in the Why Screen ...............................................................................2-86 Deleting a Job ...........................................................................................................................2-88 Delete Confirmation Window..............................................................................................2-89 Log Screen.................................................................................................................................2-90 Zoom Screen ..............................................................................................................................2-91 Zoom Screen for Group Entities .........................................................................................2-94 Exiting the Zoom Screen .....................................................................................................2-95 Confirm Scheduling Window ...................................................................................................2-96 Confirm Rerun Window ...........................................................................................................2-96 Confirm Restart Window (Under CONTROL-R) ....................................................................2-97 Rerun/Restart Window (Under CONTROL-R) .......................................................................2-97 R Step List Window....................................................................................................................2-101 Job Order Execution History Screen .....................................................................................2-102 Format of the Job Order Execution History Screen ........................................................2-103 Displaying Job Sysout .......................................................................................................2-103 Sysout Viewing Screen ...........................................................................................................2-104 Statistics Screen .....................................................................................................................2-105 Fields of the Statistics Screen...........................................................................................2-106 JOBSTAT Command .........................................................................................................2-107 Job Dependency Network Screen ..........................................................................................2-108 Format of Job Dependency Network Information ...........................................................2-109 Commands of the Job Dependency Network Screen .......................................................2-111 History Environment Screen .................................................................................................2-112 Options of the History Environment Screen....................................................................2-113 Force OK Confirmation Window............................................................................................2-113 CMEM Rule Definition Facility ........................................................................................... 2-115 General....................................................................................................................................2-115 Accessing the CMEM Rule Facility ..................................................................................2-115 Creating Tables .................................................................................................................2-116 Creating CMEM Rules ......................................................................................................2-116 Performing Operations on CMEM Tables and Rules ......................................................2-116 Entry Panel .............................................................................................................................2-117 Fields of the Entry Panel ..................................................................................................2-118 Table List Screen ....................................................................................................................2-118 Options of the Table List Screen ......................................................................................2-119 Rule List Screen......................................................................................................................2-119 Options of the Rule List Screen ........................................................................................2-120
Rule Definition Screen Defining Rules.............................................................................. 2-121 Event Selection Parameters............................................................................................. 2-122 General Parameters.......................................................................................................... 2-123 Action Parameters ............................................................................................................ 2-123 Commands of the Rule Definition Screen ....................................................................... 2-124 Specifying Comments ............................................................................................................ 2-124 Editing CMEM Rule Definitions in the Edit Environment................................................. 2-125 Exiting the CMEM Rule Definition Facility ........................................................................ 2-126 Exiting the Rule Definition Screen.................................................................................. 2-126 Exiting the Rule List Screen ............................................................................................ 2-127 Exiting the Table List Screen .......................................................................................... 2-128 Exiting the Entry Panel ................................................................................................... 2-128 Deleting Tables ...................................................................................................................... 2-128 Ordering CMEM Rule Tables................................................................................................ 2-129 Condition/Resource Handling.............................................................................................. 2-131 General ................................................................................................................................... 2-131 IOA Conditions/Resources Screen......................................................................................... 2-131 Fields of the IOA Conditions/Resources Screen .............................................................. 2-132 Specifying Retrieval Criteria ........................................................................................... 2-133 Adding Conditions and Resources The ADD Command ............................................. 2-134 Options of the IOA Conditions/Resources Screen ........................................................... 2-136 IOA Manual Conditions Screen ............................................................................................ 2-139 Fields of the IOA Manual Conditions Screen.................................................................. 2-140 Specifying Retrieval Criteria ........................................................................................... 2-140 Options of the IOA Manual Conditions Screen............................................................... 2-141 Adding a New Prerequisite Condition NEW COND Command ................................. 2-143 IOA Log Facility....................................................................................................................... 2-144 General ................................................................................................................................... 2-144 IOA Log Screen ...................................................................................................................... 2-144 Fields of the IOA Log Screen ........................................................................................... 2-145 Commands of the IOA Log Screen ................................................................................... 2-145 Filtering the IOA Log Screen Display ............................................................................. 2-146 IOA Calendar Facility ............................................................................................................ 2-151 General ................................................................................................................................... 2-151 Accessing the Calendar Facility....................................................................................... 2-152 Entry Panel ............................................................................................................................ 2-153 Fields of the Entry Panel ................................................................................................. 2-153 Calendar List Screen ............................................................................................................. 2-154 Options of the Calendar List Screen................................................................................ 2-154
Year List Screen .....................................................................................................................2-155 Options of the Year List Screen ........................................................................................2-156 Inserting a New Year ........................................................................................................2-156 Calendar Definition Screen....................................................................................................2-157 Periodic Calendars ............................................................................................................2-158 Deleting Calendars............................................................................................................2-161 Exiting the IOA Calendar Facility ........................................................................................2-162 Exiting the Calendar Definition Screen...........................................................................2-162 Exiting the Year List Screen.............................................................................................2-163 Exiting the Calendar List Screen .....................................................................................2-163 Exiting the Entry Panel ....................................................................................................2-163 Utilities Under ISPF ............................................................................................................... 2-164 General....................................................................................................................................2-164 IOA Online Utilities Menu.....................................................................................................2-164 I1: Add/Check/Delete a Prerequisite Condition ....................................................................2-166 M1: Issue a Job Order ............................................................................................................2-167 M2: Perform Online AutoEdit Simulation ............................................................................2-168 M3: Prepare Simulation/Tape Pull List Job..........................................................................2-172 M4: Parameter Prompting Facilities .....................................................................................2-176 Parameter Prompting Facility (Type 1) ...........................................................................2-177 Parameter Prompting Facility (Type 2) ...........................................................................2-184 M5: Quick Schedule Definition Facility ...............................................................................2-194 M6: End User Job Order Interface ......................................................................................2-202 R1: CONTROL-R Restart Simulation .................................................................................2-203 R2: CONTROL-R Dataset Cleanup .......................................................................................2-205 R3: Prepare the Job Dataset List.........................................................................................2-208 U1: Invoke DOCU/TEXT........................................................................................................2-209
Online Facility: IOA Features General
IOA Features
General
The Online facility is the basic means of communication between the user and CONTROL-M. Online job scheduling definition gives users the ability to define and modify job production parameters in the CONTROL-M production environment. Online tracking displays the current status of all variables relating to a specific job, a group of jobs or all jobs scheduled under CONTROL-M. Online control allows authorized users to modify variables relating to a specific job, a group of jobs or all jobs scheduled under CONTROL-M. The following pages describe the main features available under the Online facility.
Customization
IOA screens, constants, messages, colors, commands and PFKey definitions can be site-modified to adapt them to local needs. IOA products can be customized globally (i.e., for the whole site) through ICE (Installation and Customization Engine), according to profile variables defined during installation. In addition, IOA products can be customized to respond differently to individual users if these profile variables are specified in User Profile members. For example, depending on the setting of a variable in a particular User Profile member, upon exit from a screen in which changes have been requested, this IOA product may either perform the requested changes automatically or display a confirmation window before performing the changes. Customization issues are discussed in Section 2 of the IOA Administrator Guide. Note Due to customization, the screens and examples illustrated in this manual may differ from the ones used at your site.
Environment Support
The Online facility can be activated under the following environments: TSO (native) TSO/ISPF ROSCOE/ETSO CICS VTAM IMS/DC IDMS/DC COM-PLETE
Cross memory interfaces (to the Online monitor) are optional under native TSO, TSO/ISPF and ROSCOE/ETSO. They are always used under the other environments. There are slight differences in the operation of the Online facility under the different environments. Special notes are provided in this manual where applicable.
21
Terminal Support
IOA supports the following models of the IBM 3270 family of terminals: Model 2 24 lines, 80 columns Model 3 32 lines, 80 columns Model 4 43 lines, 80 columns Model 5 27 lines, 132 columns
1
IOA adjusts to the screen size in order to use the maximum available data area on the screen. Special Character Usage on Terminals In certain cases, special keyboard characters (e.g., $, @) are assigned special meanings. The characters specified appear on standard American terminals but may not be available on other keyboards. In addition, some special characters on your keyboard may be assigned different hexadecimal values than the ones recognized by IOA. If any of these characters is not on your keyboard, or is not assigned the hexadecimal value shown below, use the hexadecimal value shown below to determine which character on your keyboard should be substituted for the missing character. Char $ | @ ! \ Hex Value 5B 4F 7C 5F 5A E0 (On British keyboards, use the pound symbol)
Color Support
When IOA products are activated from a screen with extended seven-color support, IOA makes extensive use of the color attributes of the screen. Like all screen attributes, the color attribute for each field is defined externally to the program and can be locally modified by the site. Notes IOA does not automatically recognize IMS/DC and IDMS/DC terminals as supporting extended color attributes. If your IMS/DC or IDMS/DC terminal supports extended color attributes and you wish IOA to recognize this, refer to the IOA Administrator Guide for more information. At this time, IOA does not support extended color attributes under COM-PLETE. Due to ISPF characteristics, color changes cannot occur in adjacent columns but must be separated by an attribute byte without color (i.e., black). Therefore, some IOA screens have a different appearance under ISPF than under other online environments (e.g., native TSO, CICS).
When using the IOA Online facility under IMS/DC and IDMS/DC, all model types display 24 lines and 80 columns.
22
Prefixing
For fields which automatically support prefixing, selection strings are always treated as prefixes. Selection is made if a segment of the text beginning with the first letter (i.e., any prefix) matches the selection criterion. Examples Assume the following names exist: A3, A4, M, M01, M03, M12, M13, M22, M23, M30, M33, M103, M135, M301. Entry blank A M M1 M13 Matching values All of the above values A3, A4 M, M01, M03, M12, M13, M22, M23, M30, M33, M103, M135, M301 M12, M13, M103, M135 M13, M135
If a field supports prefixing, this fact is indicated in its description.
Character Masking
For fields which support masking, mask characters function as follows: * represents any number of characters (including no characters). ? represents any one character. For fields which do not automatically support prefixing, a prefix value can be specified by ending the selection string with an asterisk. Examples Assume the following names exist: A3, M, M3, M01, M03, M13, M23, M33, M103, M2243. Entry * M?3 M??3 M*3 M* Matching values All of the above values M03, M13, M23, M33 M103 M3, M03, M13, M23, M33, M103, M2243 M, M3, M01, M03, M13, M23, M33, M103, M2243 (since the last character in this example is *, M is treated as a prefix)
If a field supports masking, this fact is indicated in its description.
23
Online Facility: IOA Features IOA Entry Panel
IOA Entry Panel

Enter the IOA Online facility according to the instructions of your IOA administrator. 2 Upon entering the IOA Online facility, the IOA entry panel may be displayed.
-----------------------------IOA ENTRY PANEL ------------------------------
+-----------------------------------------------------------+ | | | USER ID ===> | | | | PASSWORD ===> | | | | NEW PASSWORD ===> ===> | | | +-----------------------------------------------------------+
PLEASE FILL IN USER ID AND PASSWORD AND PRESS ENTER
18.30.18
Type your user ID password and press <ENTER>. If you enter a correct user ID and password, the IOA Primary Option menu (Main menu) is displayed. The IOA Online facility allows three attempts to enter a valid user ID and password combination. After the third unsuccessful attempt, the program is terminated. To change a password, type the new password twice: Once in the NEW PASSWORD field (A) and once in the confirmation field (B).
Display of the IOA entry panel is optional. If your IOA administrator determined that the entry panel should be bypassed, the IOA Primary Option menu is displayed.
24
Online Facility: IOA Features IOA Primary Option Menu
IOA Primary Option Menu

The IOA Primary Option menu (Main menu) is the primary interface to functions available under the various IOA online products and facilities. The options displayed in the menu depend on the IOA online products installed at the site, and the functions and facilities which have been authorized to you. If only CONTROL-M is installed at your site, and you are authorized to access all functions 3 and facilities, the following screen is displayed:
--------------------OPTION ===> 0 1 2 3 4 5 6 7 8 C IP X IOA INFO MAIN MENU JOB SCHEDULE DEF JOB STATUS COND/RES LOG TSO MANUAL COND CALENDAR DEF CMEM DEFINITION PATHFINDER EXIT IOA PRIMARY OPTION MENU ------------------(1) USER M21 DATE 12.12.98 M Version 5.1.4-9901
IOA Version Information IOA Primary Option Menu CTM Job Scheduling Definition CTM Job Status Display IOA Conditions/Resources Display IOA Log Display Enter TSO Command IOA Manual Conditions Display IOA Calendar Definition CTM Event Manager Rule Definition IOA/Pathfinder Cross Reference Terminate Session
PLEASE SELECT OPTION
AND PRESS ENTER OR PRESS THE OPTIONS PFK
17.17.59
To select an option, type the option number/letter in the OPTION field and press <ENTER>. Alternatively, for a number option, press the PFKey with the same number. For example, to select the LOG option, press PF05.
When the Online facility is activated as an ISPF application, option 6 is displayed as: 6 UTILITIES Online Utilities In this case, option 6 activates the Online utilities under ISPF (described at the end of this section). When the Online facility is not activated under TSO or TSO/ISPF, option 6 is inactive.
25
Certain IOA functions and facilities (options) are shared by all IOA products. These include: 0 IOA INFO Display a window containing information about installed IOA products, and the CPU ID and current system date. Press <ENTER> or END (PF03/PF15) to close the window. Redisplay the IOA Primary Option menu. Display and update Conditions/Resources file. the status of the IOA
1 4 5 6 7 8
MAIN MENU COND/RES LOG TSO

4
View audit trail information about jobs, missions and rules scheduled under the supervision of IOA products. Perform TSO commands. Display and facilitate manual operations to be performed during production shifts. Define scheduling calendars. Separately licensed product which cross references the elements and relationships in IOA product files and databases. Exit the Online facility.
MANUAL COND CALENDAR DEF
IP PATHFINDER
X EXIT
These shared functions and facilities are described in detail later in this section. The following functions and facilities (options) are unique to CONTROL-M: 2 3 JOB SCHEDULE DEF JOB STATUS Define/modify job production parameters. Display and update CONTROL-M. status of jobs scheduled under
C CMEM DEFINITION
Define/modify CMEM rules.
When the Online facility is activated as an ISPF application, options 6 is displayed as: 6 UTILITIES Online Utilities In this case, option 6 activates the Online Utilities under ISPF (described at the end of this section). When the IOA Online facility is not activated under TSO or TSO/ISPF, option 6 is inactive.
26
The following IOA Primary Option menu is displayed at sites supporting all currently 5 available IOA mainframe products (under ISPF).
--------------------OPTION ===> IOA 0 4 5 6 7 8 IP X IOA INFO COND/RES LOG TSO MANUAL COND CALENDAR DEF PATHFINDER EXIT IOA PRIMARY OPTION MENU ------------------(1) USER N44 CONTROL-O OR OM OS OL OA OV OC OK RULE DEFINITION MSG STATISTICS RULE STATUS AUTOMATION LOG AUTOMATION OPTS VARIABLE DATABASE COSMOS STATUS KOA RECORDER
CONTROL-D/V A M R T U F MISSION STATUS MISSION DEF REPORT DEF RECIPIENT TREE USER REPORTS PC PACKET STATUS
CONTROL-M/R/L 2 3 C LR LA LS JOB SCHEDULE DEF JOB STATUS CMEM DEFINITION CTM WORKLOAD DEF JOB/PIPE ACTIVITY RULE STATUS
CONTROL-B/I-2000 BB BM BV BR BA BK BALANCING STATUS MISSION DEF DB VARIABLE DEF RULE DEFINITION RULE ACTIVITY KOA RECORDER
CONTROL-T TR TP TV TI TC RULE DEFINITION POOL DEFINITION VAULT DEFINITION INQ/UPD MEDIA DB CHECK IN EXT VOL
AND PRESS ENTER OR PRESS THE OPTIONS PFK
07.58.38
For a description of the options for other IOA products, see the user manuals of the respective products.
When the Online facility is not activated as an ISPF application, option 6 is displayed as: 6 TSO In this case, option 6 activates the TSO processor. When the Online facility is not activated under TSO or TSO/ISPF, option 6 is inactive.
27
Additional options available on the IOA Primary Option Menu when operating CONTROL-M with other IOA products are listed below: LR LA CTM WORKLOAD DEF JOB/PIPE ACTIVITY Define CONTROL-M/WorkLoad rules Display the CONTROL-M/WorkLoad Active Environment screen Display the CONTROL-M/WorkLoad Rule Status screen
At sites where CONTROL-M/WorkLoad is installed
LS
RULE STATUS
A M R
MISSION STATUS MISSION DEF REPORT DEF
Display and update active missions status. Define migration, printing, backup, and restore missions. Define decollating missions (including indexing). Display and update the recipient tree. Display and update the status of user reports. View reports online. Display the status of reports (packets) scheduled for transfer from the mainframe to a PC. At sites where CONTROL-D/V is installed
T U
RECIPIENT TREE USER REPORTS
PC PACKET STATUS
BB BM BV
BALANCING STATUS MISSION DEF DB VARIABLE DEF
Display and update the status of active balancing missions. Define balancing missions. Define, display and update Database variables. Define balancing rules. Display rule activity and the result of invoking CONTROL-B rules. At sites where CONTROL-B is installed
BR BA
RULE DEFINITION RULE ACTIVITY
BK
KOA RECORDER
Record VTAM scripts
At sites where CONTROL-I/2000 is installed
28
OR OM OS OL OA
RULE DEFINITION MSG STATISTICS RULE STATUS AUTOMATION LOG AUTOMATION OPTS
Define rules. View message statistics. View Rule Status screen. Display commands, messages and/or traces. Display available operator productivity tools. Display/modify CONTROL-O variable databases. Record VTAM scripts (if CONTROL-O is installed). At sites where CONTROL-O is installed
OV OK
VARIABLE DATABASE KOA RECORDER
OC
COSMOS STATUS
Display/modify the status of CONTROL-O/ COSMOS-controlled objects and databases.
At sites where CONTROL-O/COSMOS is installed
TR TP TV
RULE DEFINITION POOL DEFINITION VAULT DEFINITION
Define rules. Define pools. Define vaults. At sites where CONTROL-T is installed
TI TC
INQ/UPD MEDIA DB CHECK IN EXT VOL
Display Inquire/Update screen. Check in external volumes.
29
IOA Version Information

Select option 0 in the IOA Primary Option menu to display the IOA Version Information window shown below. This window lists the version and level of each IOA product installed at the site plus the CPU ID and system date. Press <ENTER> or END (PF03/PF15) to exit the window and return to the IOA Primary Option menu.
--------------------OPTION ===> IOA 0 4 5 6 7 8 IP X IOA INFO COND/RES LOG TSO MANUAL CON CALENDAR D PATHFINDER EXIT IOA PRIMARY OPTION MENU ------------------(1) USER N44
CONTROL-M/R/L 2 3 C LR LA LS JOB SCHEDU JOB STATUS CMEM DEFIN CTM WORKLO JOB/PIPE A RULE STATU
CONTROL-D/V CONTROL-O +----------------------------------------------+ | IOA VERSION INFORMATION | | | | IOA Version 5.1.4 level 9901 | | CONTROL - B Version 5.1.4 level 9901 | | CONTROL - D Version 5.1.4 level 9901 | | CONTROL - M Version 5.1.4 level 9901 | | CONTROL - O Version 5.1.4 level 9901 | | CONTROL - R Version 5.1.4 level 9901 | | CONTROL - T Version 5.1.4 level 9901 | | CONTROL - V Version 5.1.4 level 9901 | | CONTROL - L Version 5.1.4 level 9901 | | ECS W Version 5.1.4 level 9901 | | IOA/PATH. X Version 5.1.4 level 9901 | | | | DATE 12.12.98 CPUID 105885 9672 | | | +----------------------------------------------+ AND PRESS ENTER OR PRESS THE OPTIONS PFK
EFINITION ATISTICS TATUS TION LOG TION OPTS LE DATABASE STATUS CORDER
EFINITION EFINITION DEFINITION D MEDIA DB IN EXT VOL
10.19.22
2 10
Online Facility: IOA Features Multi-screen Control
Multi-screen Control
It is not necessary to return to the IOA Primary Option menu to move from one online facility to another. To speed up transfer of control between screens of different facilities and to enable you to manage several online facilities at the same time, transfer control commands can be specified. Transfer commands take you directly from your current screen to the requested screen. Transfer commands can be used to reach any screen which can be accessed via the IOA Primary Option menu at your site. Each transfer control command consists of an equal sign immediately followed by the option on the IOA Primary Option menu which represents the target screen of the transfer. For example, from any screen, specify: =5 =4 =3 =1 to access the IOA Log screen. to access the IOA Conditions/Resources screen. to access the CONTROL-M Status screen (if CONTROL-M is active at your site). to access the IOA Primary Option menu.
If you use a transfer command to reach another screen, the state of the current screen remains unchanged when you return to it via another transfer command. The IOA administrator can globally deactivate any or all of the transfer commands.
Fast Exit from the IOA Online Facility

To exit immediately from the IOA Online facility, type =X on the command line and press <ENTER>. In most cases, the =X command has the same effect as pressing END (PF03/PF15) in all open screens and then specifying X (Exit) in the IOA Primary Option menu. Any window (e.g., Exit Option window) which would be displayed when exiting an open screen is displayed when the =X command is specified. However, when the =X command is specified while definition screens (e.g., Calendar Definition screen) are open, changes to the open definition screens are cancelled. Changes currently in definition facility list screens (e.g., changes to previously closed definition screens) are not cancelled. Those screens and all other open screens are treated as if END (PF03/PF15) has been specified. Note The =X command is intentionally not supported on certain screens.
2 11
Online Facility: IOA Features Screen Layout
Screen Layout
Most IOA screens are divided into four basic areas. (The example shown below is the IOA Log screen.) 1. Screen Description and Messages Line: This line at the top of the screen describes the purpose of the screen. A screen identifier may appear in the upper right corner. This line is also used to display messages. 2. Screen Header and Command Area: This area is used for online commands, and, where applicable, headings of the screen data. 3. Data Area: On some screens, the data area can be scrolled. (See Scrolling Commands below.) 4. Screen Bottom: This area of the screen usually contains a list of available commands or options, or a brief explanation about screen usage. The current time is usually displayed in the lower right corner.
FILTER: COMMAND ===> SHOW LIMIT ON DATE TIME 090998 092144 090998 092144 090998 092150 090998 092150 090998 092156 090998 092157 090998 092157 ---------------- IOA LOG --------------------------------(5) SCROLL===> CRSR ==> DATE 090998 - 090998 ODATE USERID CODE ------------- M E S S A G E ------------090998 M22 SPY254I JOB CT085955 CT085955/01835 SCANNED 090998 M22 SEL208I JOB CT085955 CT085955/01835 ENDED "OK" 090998 M22 SPY254I JOB CT085956 CT085956/01836 SCANNED 090998 M22 SEL208I JOB CT085956 CT085956/01836 ENDED "OK" 090998 IVP SPY254I JOB BRIVPCC BRIVPCC /01843 SCANNED 090998 IVP SEL208I JOB BRIVPCC BRIVPCC /01843 ENDED "OK" 090998 DBA CTM659I FREE OF TASK BRCC0001 ODATE 090998 PERFORMED 090998 092201 090998 M22 SPY281I JOB INTR0004 INTR0004/04371 START 98253.1316 STOP 98253.1316 CPU 0MIN 00.04SEC SRB 0MIN 00.00SEC 0.19 090998 092201 090998 M22 SPY254I JOB INTR0004 INTR0004/04371 SCANNED 090998 092201 090998 M22 SEL206W JOB INTR0004 INTR0004/04371 ABENDED CC SB37 STEP STEP01 090998 092201 090998 M22 SEL219I JOB INTR0004 INTR0004/04371 ENDED "NOT OK" 090998 092208 090998 IVP SEL203I JOB BRCC0001 ELIGIBLE FOR RUN 090998 092208 090998 IVP SUB133I JOB BRCC0001 BRCC0002/01958 SUBMITTED 090998 092208 090998 IVP SEL203I JOB BRCC0002 ELIGIBLE FOR RUN CMDS: SHOW, GROUP, CATEGORY, SHPF 09.43.00
2 12
Online Facility: IOA Features Commands and PFKeys
Commands and PFKeys

Commands are specified by typing a command in the COMMAND field and then pressing <ENTER>, or by pressing a predefined PFKey, or a combination of both. It is not necessary to specify the full command name; the shortest unique abbreviation of the command is sufficient. If the abbreviation is ambiguous, an appropriate message is displayed in the message area. IOA commands are flexible; you can change command syntax, or provide aliases (synonyms) to suit your site. Consult your technical support personnel if you want to add/change a command syntax. The examples provided in this section reflect the original command syntax supplied with this IOA product. PFKey command assignments can be site-customized. It is possible to define PFKeys differently for each screen. Supplied PFKey definitions are consistent throughout most of the screens. For example: PF08 is used to scroll down (forward) on all IOA screens where scrolling is possible. Common PFKey definitions are: PF01/PF13 PF02/PF14 PF03/PF15 PF04/PF16 PF05/PF17 PF06/PF18 PF07/PF19 PF08/PF20 PF10/PF22 PF11/PF23 PF12 PF24 HELP SHOW (where applicable)
6
END (exit current screen and go back one level) RESET (where applicable) FIND (where applicable) =6 (transfer to TSO screen/application or to Utilities screen) UP (scroll backward) DOWN (scroll forward) LEFT or PREV (where applicable) RIGHT or NEXT (where applicable) Under ISPF only the KEYS command SHPF
7
When the IOA Online facility is activated in ISPF mode, (i.e., as an ISPF application), PF02/PF14 are usually assigned the ISPF SPLIT command. See IOA under ISPF later in this section. Disabled under ROSCOE/ETSO, CICS, VTAM, IMS/DC, IDMS/DC, COM-PLETE, and TSO cross memory option.
2 13
To see the PFKey assignment of the screen with which you are working, type reserved command SHPF in the command line and press <ENTER>. A window describing the current PFKey assignment appears on the screen. Press <ENTER> again to close the window.
FILTER: ---------------- IOA LOG --------------------------------(5) COMMAND ===> SCROLL===> CRSR SHOW LIMIT ON ==> DATE 090998 - 090998 DATE TIME ODATE USERID CODE ------ M E S S A G E -------------------090998 092156 090998 IVP SPY254I JOB BRIVPCC BRIVPCC /01843 SCANNED 090998 092157 090998 IVP SEL208I JOB BRIVPCC BRIVPCC /01843 ENDED "OK" 090998 092158 090998 IVP SEL203I JOB BRCC0001 ELIGIBLE FOR RUN 090998 092158 090998 IVP SEL203I JOB BRCC0002 ELIGIBLE FOR RUN 090998 092158 090998 IVP SEL203I JOB BRCC0003 ELIGIBLE FOR RUN 090998 092158 090998 IVP SEL203I JOB BRCCIND ELIGIBLE FOR RUN 090998 092200 090998 IVP SUB133I JOB BRCC0001 BRCC0001/01957 SUBMITTED 090998 092201 090998 IVP SUB133I JOB BRCC0002 BRCC0002/01958 SUBMITTED +----------------------------------------------------------------------------+ | | | ENTER ENTER PF13 HELP | | PF01 HELP PF14 SHOW | | PF02 SHOW PF15 END | | PF03 END PF16 RESET | | PF04 RESET PF17 FIND | | PF05 FIND PF18 =6 | | PF06 =6 PF19 UP | | PF07 UP PF20 DOWN | | PF08 DOWN PF24 SHPF | +----------------------------------------------------------------------------+
If you type text in the COMMAND field and press a PFKey, the text in the COMMAND field is treated as a subparameter of the command assigned to the PFKey. Two additional key definitions are: PA1 PA2 ABORT (forced exit). If you press PA1 while in AutoRefresh mode (described later in this section), AutoRefresh mode is cancelled. Under native TSO and ROSCOE, the first time you press this key, the screen is refreshed. The second consecutive time, a copy of the screen is sent to be printed (or to a file) via DD statement PRTDBG. (For terminal models supporting PA3, it is defined in exactly the same way as PA2.) When the IOA Online facility is activated as an ISPF application, PA2 is controlled by ISPF, and only refreshes the screen. To print the screen, see IOA Under ISPF later in this section. Under other online environments (CICS, VTAM, etc.), PA2 serves as a refresh only. Usually one of the PA keys is assigned a local print function.
2 14
Scrolling Commands
IOA scrolling conventions are very similar to IBMs ISPF conventions. Two basic commands are used for scrolling: UP (PF07/PF19) Scroll up (backward)
DOWN (PF08/PF20) Scroll down (forward) The commands can be specified by typing the command in the COMMAND field or by pressing a predefined PFKey. The scrolling amount is determined by the content of the SCROLL field in the right corner of the screen header. Valid scrolling amounts are: PAGE HALF CRSR MAX Scroll a full page. Scroll half a page. Scroll by cursor position. If the cursor is outside the data area, a full page is scrolled. Scroll maximum available (e.g., UP MAX will scroll to the top).
It is only necessary to type the first letter of the new amount in the SCROLL field in order to change the scrolling amount. A scrolling amount other than that shown in the SCROLL field can be used by specifying the amount directly after the scroll command itself, or by specifying the scroll amount in the COMMAND field and pressing the appropriate scrolling PFKey. The scrolling amount in the SCROLL field remains unchanged. Example If PAGE is the value in the SCROLL field, to scroll to bottom, type M (MAX) in the COMMAND field and press PF08 (DOWN).
LOCATE Command
The LOCATE command can be used in all directory type screens which contain scrollable data (e.g., the Calendar List screen). Syntax:
LOCATE string
The string must be specified as is. It cannot contain blanks; quotes are not required. The search proceeds from the top of the list to the first item in the list which starts with the specified string. The cursor is positioned on the OPTION field at the beginning of the line containing the string, if found, or on the OPTION field of the alphabetically closest preceding value if the specified value is not found.
2 15
FIND Command
The FIND command (and its abbreviation F) can be used in all screens which contain scrollable data to find and display the next occurrence of a character string. Syntax:
FIND string [fromcol] [tocol] [PREV]
Where: string fromcol tocol PREV Search string. Mandatory. First column in the search range. Optional. Last column in the search range. Optional. Requires specification of a fromcol value. Indicator that the search should move backwards (instead of forwards) from the current cursor position. Optional.
The FIND command supports lowercase, uppercase and mixed case arguments (strings). If the string contains blanks, enclose the string with apostrophes (single quotes) or quotation marks (double quotes). For example:
FIND WAIT SCHEDULE
The search for the string proceeds from the current cursor position forward unless PREV is specified. If the string is found, the cursor will be positioned at the start of the string. The column range searched can be limited by specifying fromcol and/or tocol values. To repeat the find (to the next/previous occurrence of the string), press PF05/PF17. Some screens enable the user to limit the number of lines searched by a FIND command. This is discussed in the relevant screen descriptions.
CANCEL and RESET Commands

CANCEL and RESET commands are specified in the COMMAND field. The CANCEL command cancels changes made in a definition screen (e.g., the IOA Calendar Definition screen) and exits the screen. The RESET command or PFKey (PF04/PF16) cancels Edit environment options (see Appendix A) specified in a definition screen. It does not cancel changes already made and it does not exit the screen or cancel Edit environment mode. The RESET PFKey can also be used in any window (e.g., the Show Screen Filter window) to cancel changes and close the window.
2 16
Online Facility: IOA Features Online Help
Online Help
The following types of online help are available for IOA screens:
Screen help Provides information about the entire screen. This help is available on all IOA screens and is accessed by pressing the HELP key (PF01/PF13) while the cursor is positioned on the COMMAND field in the screen.
Line-sensitive help Provides information about the fields on a particular line on a screen. This help is available on several IOA screens. It is accessed by pressing the HELP key (PF01/PF13) while the cursor is positioned on the desired line of the screen.
If line-sensitive help is not supported in a screen, pressing the HELP key (PF01/PF13) from anywhere in the screen displays the beginning of the Help panel.
------------------------------ IOA HELP SCREEN --------------------- (CTMHACT ) COMMAND ===> SCROLL===> CRSR Tracking and Control Facility (Status Screen) ============================================= General ------The Tracking and Control facility provides relevant information about the status of each job and task in the Active environment and enables the user to manually intervene in the processing of jobs. The Active environment contains all the jobs in the Active Jobs file (i.e., all jobs that have recently executed, are currently executing, or are scheduled for possible execution in the near future). The main screen of the Tracking and Control facility is the Status screen (Active Environment screen), which displays a list of all jobs and their statuses in the Active environment. The Status screen is accessed by requesting option 3 on the IOA Primary Option menu. ENTER END OR PF03/PF15 TO EXIT THE HELP SCREEN 11.39.19
Help can be scrolled using standard scrolling conventions. To return to the original screen, use the END command (PF03/PF15). The Help member name appears on the right in the Help screen header. Members containing the Help descriptions can be found in the IOA MSG library.
2 17
Online Facility: IOA Features AutoRefresh Mode
AutoRefresh Mode
Certain IOA screens (as noted in this section where appropriate) support AutoRefresh mode. A screen display in AutoRefresh mode is automatically updated periodically with the most current data. AutoRefresh mode can only be activated under native TSO or under ISPF. AutoRefresh mode is activated by command AUTO. Format of the command is:
AUTO n
where n is any number of seconds within the range of 1 99. The screen is updated when the AUTO command is issued, and then periodically updated according to the interval (in seconds) specified in the AUTO command. A counter at the top of the screen displays the number of times the screen has been refreshed. Example Command AUTO 5 refreshes the screen every 5 seconds.
Cancelling AutoRefresh Mode

Under native TSO, the recommended method of cancelling AutoRefresh mode is as follows: For short interval values: Press <ENTER>. Whenever <ENTER> is pressed (or a command is issued), AutoRefresh mode is automatically canceled at the end of the current interval. Press <ATTN> (PA1) once.
For long interval values:
Under ISPF, press <ATTN> (PA1) or <ESC> once to cancel AutoRefresh mode.
2 18
Online Facility: IOA Features IOA Under ISPF
IOA Under ISPF

The IOA Online facility can be activated as an ISPF application. As such, it can work in ISPF split screen mode like any other ISPF application. Note It is highly recommended that the IOA Online facility not be active in both halves of an ISPF split screen.
The command line of the IOA Online facility is controlled by IOA alone. It is not possible to enter ISPF commands in an IOA screen. Two ISPF commands must be defined to PFKeys: SPLIT SWAP (usually PF02/PF14) (usually PF09/PF21)
The rest of the PFKeys are controlled by IOA PFKey definitions (in the IOA PARM library). It is possible to assign TSO/ISPF commands (e.g., PRINT) to PFKeys or to change PFKey definitions by performing the following steps: 1. Exit from IOA and ISPF to the READY prompt. 2. Type the following command and press <ENTER>:
ISPSTART PANEL(ISR@PRIM) NEWAPPL(CTM)
This command brings you to ISPF. 3. Type the KEYS command and press <ENTER>. A set of key definitions is displayed. 4. Modify the key definitions as desired and exit from ISPF. Notes ISPF KEY definitions for the following ISPF commands take precedence over IOA PFKey definitions: SPLIT, SWAP, KEYS, PRINT, PFSHOW. For example, if PF02 is defined as SPLIT in ISPF, an IOA definition for PF02 will be ignored in online screens. For all other ISPF commands (e.g., UP, DOWN) the key definitions in ISPF are ignored and the PFKey is interpreted according to the definition in the IOA Online facility.
Under ISPF, IOA Option 6 activates the Online Utilities panel (described at the end of this section).
2 19
Online Facility: IOA Features IOA TSO Command Processor Screen
IOA TSO Command Processor Screen

The IOA TSO Command Processor screen can be entered only when the IOA Online facility is activated as a TSO application. It cannot be entered when the IOA Online facility is activated as an ISPF application or activated under a non-TSO environment. The TSO screen enables activation of any TSO command without exiting the IOA Online facility. For example, a typical program activated under the TSO screen is ISPF. Therefore all ISPF/PDF facilities and functions (e.g., editing a member, scanning job output) can be activated while you are working under the IOA Online facility. To activate a TSO command, type the command in the COMMAND field and press <ENTER>.
-------------------------- IOA TSO COMMAND PROCESSOR -----------------------(6) COMMAND ===> ISPF
PLEASE ENTER TSO COMMAND
15.32.52
Note
CLISTs cannot be activated from the TSO screen. To activate a CLIST, first activate ISPF and then execute the CLIST under ISPF.
TSO commands can also be activated directly from any IOA online screen by typing TSO in the COMMAND field.
2 20
Online Facility: IOA Features IOA TSO Command Processor Screen
Transfer of Control Between the TSO Application and the IOA Online Facility
You can return to the IOA Online facility from the TSO application by simply exiting the TSO application in a normal manner. However, this method can be time-consuming and inconvenient if an ISPF application or a similar TSO application is activated. If the TSO application can issue a TSO command, it is possible to transfer control to the IOA Online facility, and vice versa, without exiting the TSO application. While working under the TSO application (e.g., under ISPF), issue the command:
TSO CTMTTRA {n | = n}
where n is the online screen number. The requested IOA screen will be displayed in the same state it was in when you transferred from it. To return to the TSO application, use the =6 command (PF06/PF18). The application will be in the same state it was in when you transferred from it. It is recommended that you simplify transfer between screens by permanently assigning one of your PFKeys under ISPF (or SDSF, etc.) to the command TSO CTMTTRA. Once this key assignment is made, you no longer need to type the full transfer command. Instead, you merely type the IOA option number or code in the COMMAND field and press the assigned PFKey. You will be transferred to the desired IOA screen. Note You must activate ISPF under the IOA Online facility if you want to use the control transfer feature.
2 21
Online Facility: Scheduling Definition Facility General
Scheduling Definition Facility

General
The Scheduling Definition facility enables you definitions for the jobs in your environment. A parameters which correspond to the decisions and the scheduling, submission and post-processing of a to create/view/modify job scheduling job scheduling definition consists of actions of the operator when handling job.
The job scheduling definition for a job needs to be defined only once. Once defined, the definition is saved and used as necessary for managing job processing. Job scheduling definitions can be modified or deleted as required. Job scheduling definitions are stored in members called scheduling tables. Any number of scheduling tables can be defined, and each scheduling table can contain any number of job scheduling definitions. In many production environments, related applications are scheduled together as a group. In these cases, it is common to define all such related applications in a single scheduling table, and to schedule all the jobs in the table together as a group. Scheduling tables (members) are stored in scheduling libraries (partitioned datasets). You can define any number of scheduling libraries. Notes As of CONTROL-M Release 5.0.0, the number of scheduling tables in a library, the number of job scheduling definitions in a scheduling table, and the size of each job scheduling definition, are all calculated dynamically and are not dependent on parameter specification or optional ZAPs. The CONTROL-M Scheduling Definition facility does not support members which have been compressed using the ISPF PACK option.
Accessing the Scheduling Definition Facility

The Scheduling Definition facility contains the following screens:
Scheduling Facility entry panel Table List screen Job List screen Scheduling Definition screen
Allows specification of parameters which determine which screen will be displayed. Displays the list of tables (members) in the specified scheduling library. Displays the list of jobs (job scheduling definitions) in the selected table. Displays the parameters of the selected job scheduling definition or Group Entity. This is the main screen of the facility.
To enter the Scheduling Definition facility, select option 2 on the IOA Primary Option menu. The Scheduling Facility entry panel is displayed. Note Scheduling tables contain scheduling criteria and other job production parameters. They do not contain the JCL of the jobs.
2 22
Handling of Job Groups

A group of jobs whose processing (e.g., scheduling, submission, and post processing) is handled as a group, is defined in its own scheduling table, called a Group scheduling table. This table must be created with G (Group) specified in the TYPE field of the Scheduling Definition facility entry panel. At time of creation of a Group scheduling table, a special scheduling definition, called a Group Entity, is created. The Group Entity is used to define job processing criteria for the group as a whole. These include: Basic Scheduling Criteria Any number of sets of basic scheduling criteria can be specified in the Group Entity. At least one of these sets must be satisfied before the group (i.e., any job in the group) can be scheduled. Each set of basic scheduling criteria in the Group Entity is assigned a unique name called a Schedule Tag. These Schedule Tag names can be specified in job scheduling definitions in the table. When a set of basic scheduling criteria in the Group Entity is satisfied, job scheduling definitions which specify the corresponding Schedule Tag are scheduled that day. Job scheduling definitions can also contain their own basic scheduling criteria, and be scheduled according to those criteria, provided that the group itself can be scheduled. Runtime Scheduling Criteria Before any job in a group can be considered for submission, all group runtime scheduling criteria specified in the Group Entity must be satisfied. Once these are satisfied, a job will be submitted only if its own specified runtime scheduling criteria are satisfied. Post-processing actions can be defined for the group, in the Group Entity. These are performed once the group has finished processing (i.e., all jobs in the group have terminated). These actions can be made conditional upon whether all submitted jobs in the Group scheduling table ended OK, or whether at least one job did not end OK. The Group Entity also contains a field (ADJUST CONDITIONS) which can allow job dependencies based on prerequisite conditions to apply only if predecessor jobs in the group are scheduled.
Post-processing Actions
2 23
CONTROL-M internally tracks each job group and the jobs in the group. Each order of each group of jobs is identified as a unit. The status of each job group which has been ordered can be viewed via option G (Group) of the Job Status screen. Note When the IN conditions of a Group entity are satisfied (e.g., they have been added to the IOA Conditions/Resources file), the jobs in the group begin execution, assuming that their other runtime criteria are satisfied. If jobs in a group have already begun execution and an IN condition for the job group is deleted from the IOA Conditions/Resources file, this change does not affect the processing of the jobs in the group; the jobs continue execution as if all the IN conditions were still satisfied.
Creating Tables
Tables can be created in any of the following ways: 1. By specifying the new table name in the entry panel and pressing <ENTER>. (The name of a new job scheduling definition for the new table can also be specified.) 2. By using the SELECT command (described later) to specify the new table name in the Table List screen and pressing <ENTER>. Upon entering the create table request using either of the above methods, a skeletal job scheduling definition (i.e., one with most fields not filled in) is displayed in the Job Scheduling Definition screen. This job scheduling definition should be filled in and saved. The table will be created and the job scheduling definition will be the first and only job scheduling definition in the Job list of the table. As additional job scheduling definitions are created in the table (described below), they are added to the Job list. Notes Upon exiting the Job List screen, if changes were made in at least one job scheduling definition, an Exit Option window is displayed. One field of the window displays the table name. This value can be changed to a new table name. This will create a new table in which the job scheduling definitions are saved. Under ISPF, tables can also be created using online utility M5. This method is described in Utilities Under ISPF later in this section of the manual, and is not included in this discussion.
2 24
Creating Job Scheduling Definitions

Job scheduling definitions can be created using two basic methods: 1. A skeletal job scheduling definition can be created by specifying the name of a new job scheduling definition in the entry panel. (The table specified in the entry panel can be either a new or an existing table.) In this case, virtually all fields of the job scheduling definition are empty. 2. A copy of an existing job scheduling definition can be created using the INSERT option (described later) in the Job List screen. In this case, most fields of the new job scheduling definition have the same values as the fields in the copied job scheduling definition. Note Under ISPF, job scheduling definitions can also be created using online utility M5. This method is described in Utilities Under ISPF later in this section, and is not included in this discussion.
Performing Operations on Tables and Jobs

Many operations can be performed on tables and on the job scheduling definitions in them. These operations are performed via commands and options in the various screens of the Scheduling Definition facility. Below is a brief summary of some of the major operations possible within the facility. Options and commands which have not yet been explained will be explained in detail following the summary. Accessing (Editing/Browsing) a Table and its Jobs A table (i.e., the job scheduling definitions in the table) can be browsed or edited. When browsed, the table cannot be modified or updated. When the table is edited, new job scheduling definitions can be added and existing job scheduling definitions can be modified or deleted. Browsing, however, has advantages:
Access and exit are quicker than in editing. A job list and job scheduling definitions that are in use by another user can be viewed. Access for browsing might be granted, even though access for editing might be denied due to site security requirements.
To browse a table (and its job list and job scheduling definitions) use the BROWSE option in the Table List screen. Specifying the table name in the entry panel or using the SELECT option in the Table List screen provides edit access. Depending on User profile definitions, if the table requested for editing is in use, either access will be granted in Browse mode or access will not be granted.
2 25
Accessing a Jobs JCL When IOA is activated under ISPF, the member containing the JCL of a job can be accessed via the JCL command in the Job List screen. Whether or not the member can be modified/updated depends on whether the Job List screen was accessed in Browse or Edit mode. Copying a Job to Another Table Jobs can be copied from one table to another via the COPY option in the Job List screen. See Options of the Job List Screen (below). Deleting a Table or a Job Unneeded jobs can be deleted via the DELETE option in the Job List screen (see Options of the Job List Screen). Unneeded tables can be deleted via the DELETE option in the Table List screen. See Deleting Tables (below). Displaying Jobflow in Graphic Format The jobflow of jobs in a table can be displayed in graphic format via the GRAPHIC FLOW option in the Table List screen. See Displaying Graphic Jobflow (below). Manually Scheduling Jobs Manually ordering a job results in its being scheduled only if its basic scheduling criteria are satisfied. Manually forcing a job results in its being scheduled even if its basic scheduling criteria are not satisfied.
To manually order all the jobs in a table, specify the ORDER option for the table in the Table List screen. To manually force all the jobs in a table, specify the FORCE option for the table in the Table List screen. To manually order specific jobs in a table, specify the ORDER option for the jobs in the Job List screen. To manually force specific jobs in a table, specify the FORCE option for the jobs in the Job List screen.
See Ordering (Scheduling) Jobs later in this section. Displaying a Jobs Schedule Plan The schedule of a job for a specified period of time, based on the jobs basic scheduling criteria, can be displayed in calendar format via PLAN option in the Job List screen. See Displaying a Job Schedule Plan later in this section. Saving Modifications All changes made to a table and its job scheduling definitions are kept in memory until the table is exited. Upon exiting the table, the user can choose to save or cancel the changes. See Exiting the Schedule Definition Facility later in this section.
2 26
Online Facility: Scheduling Definition Facility Entry Panel
Entry Panel
The entry panel is displayed upon entering the Scheduling Definition facility (option 2 in the IOA Primary Option menu).
----------- CONTROL-M SCHEDULING DEFINITION FACILITY - ENTRY PANEL ---------(2) COMMAND ===>
SPECIFY LIBRARY, SCHEDULING TABLE, JOB LIBRARY ===> CTM.PROD.SCHEDULE TABLE ===> JOB ===> TYPE OF TABLE ===>
(Blank for table selection list) (Blank for job selection list) ( J Job - default G Group - for new tables only)
SHOW JOB DOCUMENTATION AUTO-SAVE DOCUMENTATION
===> N ===> N
(Y/N) (Y/N)
USE THE COMMAND SHPF TO SEE PFK ASSIGNMENT
23.00.04
Fields of the Entry Panel

Fill in the following fields and press <ENTER>. LIBRARY Name of the desired scheduling library. Mandatory. If this field is specified, and the TABLE and JOB fields are left blank, the list of tables in the specified library is displayed in the Table List screen. TABLE Name of the desired scheduling table or Group scheduling table. Optional. If this field is specified without filling in the JOB field, the list of jobs in the specified member is displayed in the Job List screen. If a new table name is specified, a new job scheduling definition is displayed in the Job Scheduling Definition screen. JOB Name of the desired job scheduling definition. Optional. If this field and the LIBRARY field are filled in, but the TABLE field is left blank, the Search window (described below) is displayed. If this field and the LIBRARY and TABLE fields are specified, the requested job scheduling definition is displayed in the Job Scheduling Definition screen. TYPE Type of scheduling table. This field only requires a value when creating a new table. If you are not creating a new table, this field is ignored and all types of tables are displayed. Valid values are: J (Job) G (Group) Scheduling table for individual jobs. Scheduling table for jobs handled as a group.
2 27
SHOW JOB DOCUMENTATION Determines whether or not job documentation lines (described later) will be displayed when the job scheduling definition is displayed. Y (Yes) N (No) Display documentation lines. Do not display documentation lines.
AUTO-SAVE DOCUMENTATION Determines whether or not changes made to documentation will automatically be saved (i.e., without special prompting) when updating the job scheduling definition. Y (Yes) N (No) Automatically save documentation changes. Do not automatically save documentation changes.
Search Window
The Search window is displayed when a library name and job name, but no table name, are specified in the entry panel. The Search window allows the user to automatically search for the specified job in tables in the specified library. Tables in which the job has been found are selected for display in the Table List screen.
----------- CONTROL-M SCHEDULING DEFINITION FACILITY - ENTRY PANEL ---------(2) COMMAND ===>
SPECIFY LIBRARY, SCHEDULING TABLE, JOB LIBRARY ===> CTM.PROD.SCHEDULE TABLE ===> (Blank for table selection list) JOB ===> CTMCLRES (Blank for job selection list) +-------------------------------------------+ TYPE OF TABLE ===> | | | PLEASE SELECT ONE OF THE FOLLOWING: | | | | 1 - STOP SEARCH IMMEDIATELY | | 2 - ASK AGAIN AFTER 000010 TABLES | SHOW JOB DOCUMENTATION ===> N | 3 - UNCONDITIONAL SEARCH | AUTO-SAVE DOCUMENTATION ===> N | | | NUMBER OF TABLES IN LIBRARY: 000015 | | NUMBER OF SEARCHED TABLES: 000000 | | NUMBER OF SELECTED TABLES: 000000 | | | +-------------------------------------------+ USE THE COMMAND SHPF TO SEE PFK ASSIGNMENT 12.11.54
To close the window without performing any action, press END (PF03/PF15).
2 28
To perform a search action, specify one of the following values and press <ENTER>.
1 STOP SEARCH IMMEDIATELY
The search stops and the window closes.
If no tables were selected (i.e., no tables contained the specified job), an appropriate message is displayed in the entry panel. If at least one table was selected, the Table List screen is displayed with the selected table(s).
ASK AGAIN AFTER number TABLES
Searches the specified number of tables. The search number can be modified.
3 UNCONDITIONAL SEARCH
Searches all tables in the specified library. The bottom of the window displays the following information:
Number of tables in the specified library. Number of tables searched for the job. This figure is cumulative as long as the window is open. For example, if option 2 (ASK AGAIN) is requested three times, each time with a specified search number of 10 tables, this field will display the number 30.
Number of tables selected (i.e., which contain jobs with the specified job name).
2 29
Online Facility: Scheduling Definition Facility Table List Screen
Table List Screen

The Table List screen displays a list of scheduling tables (members) in the specified library. This screen can be entered directly from the entry panel or upon exiting the Job List screen. By default, only table names are listed in the screen. However, if the default has been modified at time of installation, statistical information is displayed for each table name (as shown in the screen example on this page).
LIST OF TABLES IN CTM.PROD.SCHEDULE COMMAND ===> OPT NAME ------------ VV.MM CREATED ADABAS 01.00 98/09/09 APPLNTN 01.00 98/09/09 APPLPRDI 01.00 98/09/09 ARCNIGHT 01.00 98/09/09 ASMBTR1 01.00 98/09/09 ASMBTR2 01.00 98/09/09 BACKUP 01.00 98/09/09 CICSJOBS 01.00 98/09/09 CICSPROD 01.00 98/09/09 CICSTEST 01.00 98/09/09 CICSUPT 01.00 98/09/09 CLIENTS 01.00 98/09/09 DB2EXE 01.00 98/09/09 DLOAD 01.00 98/09/09 MAINDAY 01.00 98/09/09 MAINT 01.00 98/09/09 MAINTPL 01.00 98/09/09 ONSPOOL 01.00 98/09/09 ONSPOOLT 01.00 98/09/09 OPERCLN 01.00 98/09/09 OPTIONS S SELECT O ORDER F FORCE G -------------(2) SCROLL===> CRSR CHANGED SIZE INIT MOD ID 98/09/09 00:50 70 70 0 O01 98/09/09 00:50 180 180 0 O01 98/09/09 00:50 41 41 0 O01 98/09/09 00:50 5 5 0 S07 98/09/09 00:50 9 9 0 S07 98/09/09 00:50 14 14 0 S07 98/09/09 00:50 5 5 0 S07 98/09/09 00:50 70 70 0 O01 98/09/09 00:50 180 180 0 O01 98/09/09 00:50 41 41 0 O01 98/09/09 00:50 5 5 0 S07 98/09/09 00:50 9 9 0 S07 98/09/09 00:50 14 14 0 S07 98/09/09 00:50 5 5 0 S07 98/09/09 00:50 180 180 0 O01 98/09/09 00:50 41 41 0 O01 98/09/09 00:50 5 5 0 S07 98/09/09 00:50 9 9 0 S07 98/09/09 00:50 14 14 0 S07 98/09/09 00:50 5 5 0 S07 GRAPHIC FLOW B BROWSE D DELETE 15.38.37
Use the scrolling PFKeys to scroll the Table list forward (PF08/PF20) and backward (PF07/PF19). To return to the entry panel, press END (PF03/PF15).
Options of the Table List Screen

To request one of the following options, specify the option in the OPT field to the left of the table name(s) and press <ENTER>. S SELECT Display the list of jobs in the table for any purpose, including editing/modification. Only one table can be selected at a time. Display a list of jobs in a table for browsing. Only one table can be browsed at a time. Order all the jobs in the table, provided that their basic scheduling criteria (discussed later in this section) are met. Multiple tables can be ordered.
B BROWSE O ORDER
2 30
Online Facility: Scheduling Definition Facility Table List Screen
FORCE
Order all the jobs in the table, regardless of their basic scheduling parameters (discussed later in this section). Multiple tables can be forced. Display a graphic presentation of the jobflow of the jobs in the table (discussed later in this section). Only one table can be selected for graphic display at a time. Delete the table (member) from the library. Multiple tables can be deleted (discussed later in this section).
G GRAPHIC FLOW
D DELETE
Note
Users whose access to options has been limited by the IOA administrator can only access the Browse option.
Commands of the Table List Screen

The following command can be specified in the COMMAND field of the Table List screen. SELECT Command Command SELECT is used to create a new table in the library. Format of the command is:
SELECT tablename type
If no type is specified, the default type is Job. If there are no jobs currently in the table, the Table List screen is not displayed. Instead:
A skeletal job scheduling definition is displayed in the Job Scheduling Definition screen if a Job scheduling table is being created. A skeletal Group Entity scheduling definition is displayed in the Scheduling Definition screen if a Group scheduling table is being created. If the SELECT command is specified for an existing table, it acts like the S (SELECT) line option (described earlier) and displays the list of jobs in the table.
Note
2 31
Online Facility: Scheduling Definition Facility Job List Screen
Job List Screen

The Job List screen displays the list of jobs in a scheduling table in a specified library. This screen can be entered directly from the entry panel or the Table List screen, or upon exiting from the Job Scheduling Definition screen. Notes The names displayed on the Job List screen are the names of the members that contain the JCL of the jobs (specified in the MEMNAME parameter in the job scheduling definition) or, in the case of started tasks, the name of the STC. If the S (Select) option was specified in the Table List screen for a table which is currently in use (selected) by another user, either the Job List screen is not displayed and the Table List screen remains displayed (the default), or the Job List screen is displayed in Browse mode (if a User Profile definition overrides the default). In either case, an appropriate message is displayed.
JOB LIST LIB: CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR OPT NAME ----- DESCRIPTION --------------------------------------------------STARTBKP START OF DAILY BACKUP BACKPL01 DAILY BACKUP OF DATA SETS FROM APPL-L BACKPL02 DAILY BACKUP OF SPECIAL FILES FROM APPL-L BACKPLW1 WEEKLY BACKUP OF FILES FROM APPL-L #1 BACKPLW2 WEEKLY BACKUP OF FILES FROM APPL-L #2 BACKPLW3 WEEKLY BACKUP OF FILES FROM APPL-L #3 BACKPLW4 WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-L + DASDRPT1 DASD REPORTS AFTER BACKUPS FOR APPL-L DASDRPT2 DASD STATISTICS REPORT AFTER BACKUP FOR APPL-L ENDPLBKP END OF BACKUP INDICATION FOR APPL-L BACKAC01 DAILY BACKUP OF DATA SETS FROM APPL-ACCOUNT BACKAC02 DAILY BACKUP OF SPECIAL FILES FROM APPL-ACCOUNT BACKACW1 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #1 BACKACW2 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #2 BACKACW3 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #3 BACKACW4 WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-ACC + DASDRPT3 DASD REPORTS AFTER BACKUPS FOR APPL-ACCOUNT DASDRPT4 DASD REPORTS AFTER BACKUP FOR APPL-ACCOUNT ENDACBKP END OF BACKUP INDICATION FOR APPL-ACCOUNT BACKDD01 DAILY BACKUP OF DATA SETS FROM APPL-DD OPTIONS S SELECT D DELETE I INSERT O ORDER F FORCE J JCL C COPY P PLAN 15.37.39
Use the scrolling PFKeys to scroll the Job list forward (PF08/PF20) and backward (PF07/PF19).
2 32
Format of the Job List Screen

Next to each job name in the Job list, certain information can be displayed. The type and format of this information depends on whether the screen is displayed in DATA format or in DESC format, and whether or not the list is displayed for a Group scheduling table:
In DESC format, the jobs description, taken from the DESC field of the job scheduling definition, is displayed. Default. In DATA format, the jobs application and group names, taken from the APPL and GROUP fields of the job scheduling definition, are displayed. If the job list is displayed for a Group scheduling table, the type of job scheduling definition is also displayed in the DESC and DATA formats. (Type information is not displayed for regular scheduling tables.) Valid values: E J S Group Entity. This is always the first entry in the Job list. Job Started Task
By default, the job list is displayed in DESC format. To change formats, use the DESC or DATA commands, described below. The order in which the jobs are displayed in the Job List screen can be sorted via the SORT command (described below).
Commands of the Job List Screen

The following commands can be specified in the COMMAND field of the Job List screen. DESC Command Command DESC displays the job description next to the job name. The description is taken from the DESCRIPTION field in the job scheduling definition. DATA Command Command DATA displays the jobs Application name and Group name next to the job name. The Application name and Group name are taken from the corresponding fields in the job scheduling definition. SORT Command Command SORT sorts the list of jobs in the Job List screen according to specified criteria. Format of the command is:
SORT key
Where key is one of the following values: J (Job) G (Group) A (Application) Sorted according to job name. Sorted according to group name. Sorted according to application name.
2 33
Options of the Job List Screen

To request one of the following options, specify the option in the OPT field to the left of the job name(s) and press <ENTER>. Notes Option O (Order) is not available if the Job List screen is displayed for a Group Scheduling table. Options D (Delete), I (Insert) and J (JCL) are not available for Group Entities. If the Job List screen is displayed in Browse mode, options D (Delete) and I (Insert) are not available. S SELECT Display the Job Scheduling Definition screen, with details of the selected job. Only one job can be selected at a time. If the Job List screen is not displayed in Browse mode, the job scheduling definition can be edited and updated. If the Job List screen is displayed in Browse mode, the job scheduling definition can only be browsed; it cannot be modified. D DELETE I INSERT Delete a job from the Job list (member). Multiple jobs can be selected. Insert a new job in the list (member). The Job Scheduling Definition screen appears, with the same details of the job marked I, but the MEMNAME and DESCRIPTION parameters are empty for you to fill in. The new job is added after the job marked I. Only one new job can be inserted at a time. Order a job provided that its basic scheduling criteria (described later in this section) are satisfied. Multiple jobs can be selected. Force a job order regardless of the jobs basic scheduling criteria (described later in this section). Multiple jobs can be selected. Edit the member that contains the JCL of the job. Entering this option brings you directly into the JCL member in ISPF Edit mode. By default, if the JCL member exists in the OVERLIB library (discussed later), that member is edited. If the JCL member does not exist in the OVERLIB library, the member is edited in the MEMLIB library (discussed later). Only one jobs JCL can be edited. Copy the job to another table (described later in this section). Multiple jobs can be selected. Display a schedule plan for the job (described later in this section). Only one jobs schedule plan can be displayed.
O ORDER F J FORCE JCL

8
C COPY P PLAN
Called the E (Edit) option prior to CONTROLM Release 4.0.0, this option is only available when operating CONTROLM under TSO/ISPF.
2 34
Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules
Job Scheduling Definition Screen Defining Schedules

The Job Scheduling Definition screen is used to define, display and modify production parameters of a specific job. This screen can be entered directly from the entry panel or from the Job List screen. Update of parameters is not permitted in Browse mode. Note The format of the Job Scheduling Definition screen for Group Entities is slightly different than the format shown below and is described in Scheduling Definition for Group Entities later in this section.
JOB: BACKPL02 LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME BACKPL02 MEMLIB CTM.PROD.JOBLIB OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y APPL APPL-L GROUP BKP-PROD-L DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L OVERLIB CTM.OVER.JOBLIB SET VAR CTB STEP AT NAME TYPE DOCMEM BACKPL02 DOCLIB CTM.PROD.DOC =========================================================================== SCHEDULE TAG RELATIONSHIP (AND/OR) O DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL WORKDAYS SHIFT RETRO N MAXWAIT 04 D-CAT MINIMUM PDS =========================================================================== IN START-DAILY-BACKUP ODAT CONTROL RESOURCE INIT 0001 CART 0001 PIPE CTM.WKLD.PIPE TIME: FROM UNTIL PRIORITY 00 DUE OUT CONFIRM =========================================================================== OUT BAKCKPL02-ENDED-OK ODAT + AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< ===== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
2 35
Notes
Parameters SCHEDULE TAG (F) and RELATIONSHIP (G) appear only in job scheduling definitions belonging to Group scheduling tables. Parameter PIPE (H) is displayed only if CONTROL-M/WorkLoad is installed. RETENTION parameters # OF DAYS TO KEEP and # OF GENERATIONS TO KEEP (I) are displayed only at sites which use the History Jobs file.
The job scheduling definition occupies more than one screen. Use the scrolling PFKeys to scroll the job scheduling definition forward (PF08/PF20) and backward (PF07/PF19). To delete a parameter on the screen, simply erase it via the EOF key or blank it out. If additional action is required, CONTROL-M issues appropriate instructions.
Parameters of the Job Scheduling Definition Screen

The Job Scheduling Definition screen is divided into the following sections. A. General Job Parameters In this section, you can specify specific information about the job itself in which member and library the JCL is found, who is the owner of the job, etc. B. Basic Scheduling Parameters In this section, you can specify scheduling criteria (e.g., days of the week or month on which the job should be submitted). C. Runtime Scheduling Parameters In this section, you can specify submission criteria including conditions which must be fulfilled (generally, successful completion of a preceding job) before submission of the job, resources required by the job, and time limitations on job submission. D. Post-Processing Parameters In this section, you can specify fixed or conditional actions to perform upon job completion, or upon the execution of specified job steps. For example, you can set conditions which trigger the submission of other jobs, you can send messages to the operator console, or you can rerun the job. These sections are divided by a delimiter line (E). A brief description of all parameters in each section of the Job Scheduling Definition screen is provided on the following pages. A detailed explanation of these parameters is provided in Section 3. Note Parameters marked below with the symbol G can have multiple occurrences. Whenever you fill in the last occurrence of the parameter on the screen, CONTROL-M adds a new empty occurrence of the parameter which you may fill in. The only limit to the number of occurrences is the region size available for the application.
2 36
General Job Parameters

+-----------------------------------------------------------------------------+ MEMNAME BACKPL02 MEMLIB CTM.PROD.JOBLIB OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y APPL APPL-L GROUP BKP-PROD-L DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L OVERLIB CTM.OVER.JOBLIB SET VAR CTB STEP AT NAME TYPE DOCMEM BACKPL02 DOCLIB CTM.PROD.DOC ===========================================================================
MEMNAME MEMLIB OWNER

9
Name of the member which contains the JCL of the job, or name of the started task. Name of the library which contains either the JCL of the job or identifying information and parameters of the started task. ID of a user who requests CONTROL-M services. This field is used for security purposes. Type of task to be performed by CONTROL-M (e.g., job JOB, started task STC). Indicator (Y/N) specifying whether or not to prevent a NOT CATLGD 2 (NCT2) error during job execution. Name of the application to which the jobs group belongs. Name of the group to which the RESERVATIONS, INVENTORY, etc.). job belongs (BACKUPS,
TASKTYPE PREVENT-NCT2 APPL GROUP DESC OVERLIB SET VAR

G
Description of the job (free text) which will be displayed next to the job name in the Job List screen. Name of a library which should override the library specified in MEMLIB. Statement assigning a value to an AutoEdit variable (which can be used in the submitted job). CONTROL-B definition to be activated as the first or last (as specified) step of the job. The type of CONTROL-B definition (rule or mission) and its name are also specified. Name of a member in which the job documentation resides. Name of the library in which the job documentation member resides.
CTB STEP
DOCMEM DOCLIB
OWNER was called USER ID prior to CONTROLM Release 4.0.0.
2 37
Basic Scheduling Parameters Note Parameters SCHEDULE TAG and RELATIONSHIP appear only in job scheduling definitions belonging to Group scheduling tables.
=========================================================================== SCHEDULE TAG RELATIONSHIP (AND/OR) O DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL WORKDAYS SHIFT RETRO N MAXWAIT 04 D-CAT MINIMUM PDS
SCHEDULE TAG RELATIONSHIP
Tag(s) identifying the set(s) of scheduling criteria defined in the Group Entity which can be used to schedule the job. And/Or indicator which determines whether or not the criteria of the specified Schedule tag must be satisfied.
Note
For information on how schedule tag and relationship criteria and other basic scheduling criteria are applied to jobs in Group Tables, see Basic Scheduling Parameters Summary in Section 3 of this manual. Days of the month to schedule the job. A maximum of two lines can be specified. DCAL AND/OR DAYS calendar containing predefined scheduling dates. Conjunctional parameter which links parameters DAYS and WDAYS.
DAYS
WDAYS
Days of the week to schedule the job. A maximum of two lines can be specified. WCAL WDAYS calendar containing predefined scheduling dates.
MONTHS DATES CONFCAL
Months to run the job. Specific dates in the year to run the job. Name of a calendar used to confirm job scheduling dates. SHIFT Indicates if and when a job should be scheduled.
RETRO
Yes/No (Y/N) indicator specifying whether or not the job is to be scheduled (retroactively) after the original scheduling date has passed.
2 38
MAXWAIT D-CAT
Number of extra days within which to try to execute a job if the date of the job has passed. Name of a CONTROL-D report decollating mission category. If specified, the report decollating mission is scheduled whenever the job is scheduled under CONTROL-M. Minimum number of free tracks required by the library specified in parameter PDS. The job is executed if the number of free tracks is less than the minimum. Name of a partitioned dataset to be checked for free space. If the PDS has less than the minimum number of required free tracks (specified in parameter MINIMUM), the job is executed. Not supported for PDSE-type libraries.
MINIMUM
PDS
Runtime Scheduling Parameters

=========================================================================== IN START-DAILY-BACKUP ODAT CONTROL RESOURCE INIT 0001 CART PIPE TIME: FROM UNTIL PRIORITY 00 DUE OUT CONFIRM ===========================================================================
IN
G G G
Prerequisite conditions for the job. Shared or exclusive control over resources required for the job. Quantitative resources required for the job. Name of a dataset that will be replaced by a pipe during the run of the job. Available only at sites in which CONTROL-M/WorkLoad is installed. Time limit (from, until) for job submission. Job priority in receiving CONTROL-M services or critical path priority. Time by which the job must finish executing. Yes/No indicator (Y/N) specifying whether or not manual confirmation is required before the job can be submitted.
CONTROL
RESOURCE PIPE
TIME PRIORITY DUE OUT CONFIRM
2 39
Post-processing Parameters
=========================================================================== OUT BAKCKPL02-ENDED-OK ODAT + AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES C0008 U0048 A/O DO
OUT
Prerequisite conditions to be added and/or deleted when the job finishes OK. When CONTROL-R is not installed, see Section 3 for special use of this parameter for Automatic Job Restart. Indicator (Y/N) specifying whether or not to automatically archive SYSDATA. SYSDB Yes/No indicator specifying whether to archive SYSDATA of jobs to a common dataset (Y) or to unique datasets (N). Maximum number of days (0099) to retain archived SYSDATA of jobs which ended NOTOK. Maximum number of runs (000999) for which the archived SYSDATA should be retained for jobs which ended NOTOK.
AUTO-ARCHIVE
MAXDAYS MAXRUNS
R
RETENTION
Either of the following parameters (but not both) can be used to specify how long the job should remain in the History Jobs file. # OF DAYS TO KEEP Number of days the job should be retained. # OF GENERATIONS TO KEEP Number of runs of the job which should be retained.
SYSOUT RERUN
Action to perform with the jobs sysout when the job finishes OK. The following parameters are used when a DO RERUN is requested: MAXRERUN RERUNMEM Maximum number of reruns to be performed for the job. Name of member to be submitted in case of rerun.
INTERVAL STEP RANGE

G
Amount of time (minutes) to wait between reruns or between cycles of a cyclic job. Step range (FROM/TO PGMST, and optionally PROCST) name to be referenced by ON statements.
2 40
ON
Step/code event criteria which determine if the accompanying DO actions will be performed. PGMST/PROCST Program step (and optionally the procedure step) to check for the specified code criteria. CODES A/O
G
10
Execution event codes (e.g., U0234, SB37, C0004). AND/OR conjunctional parameter which opens (and links) additional ON statements.
DO statements
Actions to be performed when the ON step/code event criteria are satisfied. Valid DO statements are:
PROCST CODES S*** U**** PL-BACKOUT-REQUIRED ODAT + A/O
ON PGMST UPDATE DO COND DO
DO COND
Add/delete a prerequisite condition.

PROCST = BALKPL CODES OK ARG DOREPORT,UPDATEDB A/O
ON PGMST ANYSTEP DO CTBRULE DO
DO CTBRULE
Invoke the CONTROL-B Runtime Environment and execute the specified CONTROL-B rule (which performs the balancing operations defined in the rule on SYSDATA). Arguments can be passed to CONTROL-B. Available only at sites in which CONTROL-B is active.
CODES S*** U**** JOB PLBCKOUT A/O DATE ODAT
ON PGMST UPDATE PROCST DO FORCEJOB TABLE PLPROD LIBRARY GENERAL DO
DO FORCEJOB
Force (schedule) a job(s) under CONTROL-M.

A/O CONFIRM N
ON PGMST ANYSTEP PROCST CODES S0C1 DO IFRERUN FROM GLSTEP01 . GLPROC02 TO GLSTEP05 . GLPROC03 DO
DO IFRERUN
Perform a CONTROL-R restart when the job is manually or automatically rerun.

PROCST CODES C0004 A/O
ON PGMST UPDATE DO NOTOK DO
DO NOTOK
Define the jobs termination status as NOTOK.
10
PGMST and PROCST were called PGMSTEP and PROCSTEP, respectively, prior to CONTROL-M Release 4.0.0.
2 41
ON PGMST ANYSTEP DO OK DO
PROCST
CODES C0008
U0048
A/O
DO OK
Define the event within the job as OK.

ON PGMST ANYSTEP PROCST CODES S0C1 DO IFRERUN FROM GLSTEP01 . GLPROC02 TO GLSTEP05 . GLPROC03 DO RERUN DO A/O CONFIRM N
DO RERUN
Indicate a job should be rescheduled for a rerun.

CODES C0008 U0048 A/O
ON PGMST ANYSTEP PROCST DO SET VAR= %%RUNTYPE=CHK DO
DO SET Note
Assign a value to a CONTROL-M AutoEdit variable. Since DO SET values are dependent upon fulfillment of ON step/codes criteria, the values are assigned after job execution and used for subsequent cyclic runs and rerun.
ON PGMST UPDATE PROCST CODES S*** DO SHOUT TO OPER2 URGENCY R = A BACKOUT OF FILE-XXXX IS GOING TO RUN SOON DO SHOUT TO USER-DBA URGENCY R = ABEND OF THE UPDATE STEP, PLEASE CHECK IT DO U**** A/O
DO SHOUT
Message to be sent to specified location.

CODES S*** U**** A/O FRM
ON PGMST UPDATE PROCST DO SYSOUT OPT C PRM P DO
DO SYSOUT
Action to perform with the jobs sysout.
DO SHOUT WHEN NOTOK MS JOB BACKP02 ENDED NOT OK SHOUT WHEN MS
TO TSO-M44 TO
URGN R URGN
SHOUT
Message to be sent to a specified destination in a specified situation: WHEN TO URGN MS Situations under which to send the message. Destination of the message. Urgency of message. The message (free text). CONTROL-M AutoEdit System variables are supported.
2 42
Scheduling Definition for Group Entities

A Group Entity must be defined for each Group Scheduling table before the job scheduling definitions in the table can be defined. A skeletal scheduling definition for a Group Entity is automatically displayed when creating a Group scheduling table. The scheduling definition for a Group Entity can also be entered directly from the Entry Panel or from the Job List screen. The job scheduling definition for Group Entities varies somewhat from the job scheduling definition for jobs. The parameters of the Group Entity are used to define basic scheduling criteria, runtime scheduling criteria, and post-processing actions to be performed, for the jobs in the group. During New Day processing, if at least one set of basic scheduling criteria in the Group Entity is satisfied, a copy of the Group Entity is placed in the Active Jobs file, and the jobs in the Group Entity become eligible for scheduling. The final status of the Group Entity job order is assigned after all scheduled jobs in the table have been terminated. This Group Entity status is determined by the execution results of those jobs:
If all the scheduled jobs in the table ended OK, the Group Entity is assigned an end status of OK. If at least one scheduled job in the table did not end OK, the Group Entity is assigned an end status of NOTOK.
The performance of post-processing actions defined in the Group Entity is directly affected by the end status of the Group Entity.
2 43
GRP ACCOUNTS_GROUP CTM.PROD.SCHEDULE(GRP) COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ GROUP ACCOUNTS_GROUP MEMNAME ACCOUNTS OWNER N04B APPL DESC ADJUST CONDITIONS N SET VAR DOCMEM ACCOUNTS DOCLIB CTM.PROD.DOC =========================================================================== SCHEDULE TAG ALL_DAYS DAYS ALL DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT =========================================================================== SCHEDULE TAG DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 =========================================================================== IN TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT ON GROUP-END NOTOK DO COND ACCTS-CHK-REQUIRED ODAT + SHOUT WHEN TO URGN USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 18.19.14
The Group Entity scheduling definition supports the same commands and PFKey conventions as any job scheduling definition. Parameters of the Group Entity Scheduling Definition Screen The parameters of the Group Entity scheduling definition are almost identical in appearance and usage as those in a regular job scheduling definition, which are described briefly in Parameters of the Job Scheduling Definition Screen earlier in this section. Differences in the parameters of the Group Entity scheduling definitions are described below. All parameters of the Job Scheduling Definition screen are described in detail in Section 3 of this manual. A. GROUP Name of the group. (This parameter also appears, in a different location, in regular job scheduling definitions.) Mandatory in Group Entities. When defined in a Group Entity, the value is automatically assigned to all job scheduling definitions in the Group table.
2 44
B. MEMNAME
In a Group Entity, this field does not indicate a member name. Instead, it is used to indicate an abbreviated group name. This abbreviated group name is then displayed, when appropriate, in other screens (e.g., the Status screen). Yes/No indicator specifying whether or not prerequisite conditions normally set by predecessor jobs will be removed from job orders if the relevant predecessor jobs are not scheduled. This parameter only appears in the Group Entity, and applies to all jobs in the table awaiting prerequisite conditions from unscheduled jobs. Use of this parameter can simplify the handling of Maybe jobs. Unique identifier to be applied to the accompanying set of scheduling criteria. Multiple sets of scheduling criteria can be defined, each with its own tag. A set of criteria defined in a Group Entity can be applied to a job by specifying the identifying tag in the jobs scheduling definition. At least one set of basic scheduling criteria in the Group Entity must be satisfied before the jobs in that Group scheduling table become eligible for scheduling on any day.
C. ADJUST CONDITIONS
D. SCHEDULE TAG
E. Basic Scheduling Parameters F. Runtime Scheduling Parameters
The Group Entity does not contain parameters DCAT, PDS, and MINIMUM which are found in job scheduling definitions. These parameters (IN, TIME FROM/UNTIL, PRIORITY, DUE OUT, CONFIRM) apply to all scheduled jobs in the group. All runtime scheduling criteria in the Group Entity must be satisfied before any of the scheduled jobs are eligible for submission. (Any runtime criteria defined for a particular job must also be satisfied before the job can be submitted.)
G. Post-processing Parameters
Non-conditional Post-processing parameters (OUT, SHOUT) are performed only if all scheduled jobs in the table have ended OK. Group Entity end status indicator. This parameter appears only in the Group Entity. DO statements immediately following this parameter are performed only if the Group Entity is assigned the indicated status. Valid values are: OK Subsequent DO actions are performed for each job in the group only if the end status of the Group Entity is OK (i.e., all scheduled jobs in the table ended OK). Subsequent DO actions are performed for each job in the group if the end status of the Group Entity is NOTOK (i.e., at least one job in the group ended NOTOK).
ON GROUP-END
NOTOK
2 45
Commands of the Job Scheduling Definition Screen

The following commands can be specified in the COMMAND field of the Job Scheduling Definition screen. FIND Command Command FIND locates a particular string. Described in Commands and PFKeys earlier in this section. DOC Command Command DOC alternately displays/hides Documentation later in this section.) EDIT Command Command EDIT alternately places the job scheduling definition in, and removes the job scheduling definition from, an ISPF-like Edit environment. (See Editing Job Scheduling Definitions in the Edit Environment later in this section for a brief overview. See Appendix A for complete details.) NEXT Command Command NEXT (PF11/PF23) keeps the changes to the current job scheduling definition in memory and automatically displays the next job scheduling definition in the scheduling table. (See Exiting the Job Scheduling Definition Screen later in this section.) PREV Command Command PREV (PF10/PF22) keeps the changes to the current job scheduling definition in memory and automatically displays the previous job scheduling definition in the scheduling table. (See Exiting the Job Scheduling Definition Screen later in this section.) CHANGE Command Command CHANGE replaces an existing string with a new string. Format of the command is:
CHANGE oldstring newstring
the
job
documentation.
(See
Job
where: oldstring newstring Existing string to be replaced. String which replaces the existing string.
If a string contains embedded spaces, enclose the string in apostrophes (') or quotation marks ("). To repeat a CHANGE command, press PF09/PF21.
2 46
Editing Job Scheduling Definitions in the Edit Environment

Job scheduling definition parameters can be edited (moved, copied, deleted, repeated) by performing IOA Line Editing commands, similar to standard ISPF line commands, from within the CONTROL-M Edit environment. The Edit Environment in the Job Scheduling Definition screen is accessed by typing EDIT in the COMMAND field and pressing <ENTER>.
JOB: BACKP02 LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ -- MEMNAME BACKP02 MEMLIB CTM.PROD.JOBLIB -- OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y -- APPL APPL-L GROUP BKP-PROD-L -- DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L -- OVERLIB CTM.OVER.JOBLIB -- SET VAR -- CTB STEP AT NAME TYPE -- DOCMEM BACKP02 DOCLIB CTM.PROD.DOC -- =========================================================================== -- DAYS DCAL -AND/OR -- WDAYS WCAL -- MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y -- DATES -- CONFCAL WORKDAYS SHIFT RETRO N MAXWAIT 04 D CAT -- MINIMUM PDS -- =========================================================================== -- IN START-DAILY-BACKUP ODAT -- CONTROL -- RESOURCE INIT 0001 CART 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
A two-character Line Editing command field, marked by underscores, is displayed for each line on the screen. Editing commands are typed directly onto these underscores. Specified Line Editing commands are processed when <ENTER> is pressed. Details and examples of the editing of job scheduling definitions in the Edit environment are provided in Appendix A.
2 47
Job Documentation
Display/Non-Display of Documentation Depending on the value of the Show Job Documentation field in the Scheduling facility entry panel, job documentation (i.e., DOC lines) will either be displayed or hidden when you first enter the Job Scheduling Definition screen:
If the Show Job Documentation field is set to Y, job documentation is displayed upon entry to the Job Scheduling Definition screen. If the Show Job Documentation field is set to N, documentation is hidden upon entry to the Job Scheduling Definition screen.
DOC Command The DOC command alternately displays/hides the job documentation. Below is an example of the Job Scheduling Definition screen with the documentation (DOC lines) displayed (A).
JOB: BACKPL02 LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME BACKPL02 MEMLIB CTM.PROD.JOBLIB OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y APPL APPL-L GROUP BKP-PROD-L DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L OVERLIB CTM.OVER.JOBLIB SET VAR CTB STEP AT NAME TYPE DOCMEM BACKPL02 DOCLIB CTM.PROD.DOC =========================================================================== DOC THIS JOB BACKS UP SPECIAL "L" FILES. IT PERFORMS THE FOLLOWING STEPS: DOC 1: VERIFY SPACE REQUIREMENTS DOC 2-5: BACKUP THE FILES DOC 6: RECATALOG THE NEW FILES DOC 7: PRINT THE SHORT-VERSION LISTING REPORT DOC =========================================================================== DAYS ALL DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
Note
Users with DOCU/TEXT installed at their site may specify a DOCU/TEXT library and member with up to 132 characters per line. However, if more than the first 71 characters in a line are used, the line is truncated and Browse mode is forced. Browse mode is also forced if a line has an unprintable character.
2 48
Editing Documentation Documentation can be edited when the DOC lines of the Job Scheduling Definition screen are displayed. Modify the DOC lines as desired. When you fill in the last DOC line and press <ENTER>, a new DOC line is displayed. When modifying DOC lines, text must be left in at least one DOC line in order to save the modifications. Changes resulting in an empty DOCMEM member will not be saved. Job Documentation is written to the library/member specified in the DOCLIB and DOCMEM fields on the Job Scheduling Definition screen. Therefore, it is also possible to edit the documentation member directly via ISPF. This is recommended when documentation is lengthy or the editing required is very complex. Note For LIBRARIAN and PANVALET users, the DOC command displays/hides job documentation in Browse mode. Changes to the documentation are not permitted.
Auto-Save and Saving Documentation

Documentation changes can be saved upon exiting the Job Scheduling Definition screen. When there are documentation changes, a Save Documentation window may be displayed depending on the value of the AUTO-SAVE DOCUMENTATION field in the Scheduling Facility entry panel:
If the AUTO-SAVE DOCUMENTATION field was set to Y, documentation changes are automatically saved and the Save Documentation window is not displayed. If the AUTO-SAVE DOCUMENTATION field was set to N, documentation changes are not automatically saved and the Save Documentation window is displayed. This window lets you save or cancel the documentation changes.
JOB: PRUPDT02 LIB CTM.PROD.SCHEDULE TABLE: PRPROD COMMAN +-----------------------------------------------------------+ ===> CRSR +----- | | --------+ MEMN | SAVE DOCUMENTATION ==> (Y/N) | OWNE | | APPL | LIBRARY CTM.PROD.DOC | DESC | MEMBER PRUPDT02 | OVER | | SET +-----------------------------------------------------------+ CTB STEP AT NAME TYPE DOCM =========================================================================== DOC PROGRAMMER RESPONSIBLE - JOHN SMITH DOC MODIFICATIONS: DOC 1. NEW DD CARD ADDED INP002 FOR NEW INPUT FILE - OCT. 1998 DOC 2. ADDITIONAL REPORT CREATED IN STEP 04 - NOV. 1998 DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 123456789101112DATES USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
2 49
Online Facility: Scheduling Definition Facility Exiting the Scheduling Definition Facility
The following parameters can be specified in the Save Documentation window: SAVE DOCUMENTATION Valid values are: Y (Yes) N (No) LIBRARY MEMBER Save documentation changes. Do not save documentation changes.
Name of the library containing the documentation member. Name of the member containing the documentation.
Modify the LIBRARY and MEMBER values if desired, and specify Y or N in the SAVE DOCUMENTATION field; then press <ENTER>. If there are no documentation changes, the Save Documentation window is not displayed.
Exiting the Scheduling Definition Facility

When exiting the Scheduling Definition facility, screens are exited in the following sequence:
Job Scheduling Definition screen Job List screen Table List screen Note If the Table List screen was bypassed when you entered the Scheduling Definition facility (i.e., if you specified a TABLE value in the entry panel), the Table List screen is not displayed upon exiting the Job List screen; instead, the entry panel is displayed.
Entry panel
The commands and options available when exiting screens depend on the screen being exited and on whether or not changes have been made. If changes have been made, the selected exit options and commands will determine whether or not the changes will be saved. Exit options and commands are discussed below on a screen-by-screen basis.
2 50
Exiting the Job Scheduling Definition Screen

Use any of the following commands, or press the corresponding PFKey, to exit the Job Scheduling Definition screen: CANCEL Cancel the changes made to the job scheduling definition and return to the Job List screen.
Note
The following exit commands retain changes to the job scheduling definition in memory. To permanently save the changes to disk, you must request that the changes be saved when you exit the Job List screen. If documentation changes have been made, the Save Documentation window (described earlier in this section) may be displayed.
END (PF03/PF15) NEXT (PF11/PF23) PREV (PF10/PF22)
Keep changes to the job scheduling definition in memory and exit to the Job List screen. Keep changes to the job scheduling definition in memory and display the next job scheduling definition in the Job list. Keep changes to the job scheduling definition in memory and display the previous job scheduling definition in the Job list.
Exiting the Job List Screen

Press END (PF03/PF15) to exit the Job List screen. If changes made to at least one job scheduling definition have been kept in memory (see Exiting the Job Scheduling Definition Screen above) and/or changes have been made to the Job List screen, the Exit Option window is displayed.
JOB LIST LIB: CTM.PROD.SCHEDULE TABLE: BACKUP COMMAN +-----------------------------------------------------------+ ===> CRSR OPT N | PLEASE SELECT EXIT OPTION | --------S | | B | SAVE CREATE | B | | B | LIBRARY CTM.PROD.SCHEDULE | B | TABLE BACKUP | B | | B +-----------------------------------------------------------+ D DASDRPT2 DASD STATISTICS REPORT AFTER BACKUP FOR APPL-L ENDPLBKP END OF BACKUP INDICATION FOR APPL-L BACKAC01 DAILY BACKUP OF DATA SETS FROM APPL-ACCOUNT BACKAC02 DAILY BACKUP OF SPECIAL FILES FROM APPL-ACCOUNT BACKACW1 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #1 BACKACW2 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #2 BACKACW3 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #3 BACKACW4 WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-ACC + DASDRPT3 DASD REPORTS AFTER BACKUPS FOR APPL-ACCOUNT DASDRPT4 DASD REPORTS AFTER BACKUP FOR APPL-ACCOUNT ENDACBKP END OF BACKUP INDICATION FOR APPL-ACCOUNT BACKDD01 DAILY BACKUP OF DATA SETS FROM APPL-DD OPTIONS: S SELECT D DELETE I INSERT O ORDER F FORCE J JCL P PLAN 14.33.48
2 51
The LIBRARY and TABLE fields indicate the library and table in which the job scheduling definitions will be saved. The specified values can be modified (e.g., to save the job scheduling definitions in a new or different table). Fill in the Exit Option window as follows:
To save all changes currently in memory and exit the Job List screen, specify Y (Yes) after the word SAVE or CREATE: Specify Y after SAVE if a table with the same name already exists in the specified library. Specify Y after CREATE if a table with the same name does not exist in the specified library. If you create a new table, the table name does not appear in the Table List screen upon exiting the Job List screen; it first appears when you reenter the Table List screen from the entry panel.
Note
To cancel changes currently in memory and exit the Job List screen, specify N (No) after the word SAVE or CREATE. To close the Exit Option window and remain in the Job List screen (with the changes remaining in memory), press RESET (PF04/PF16).
Exiting the Table List Screen

Press the END key (PF03/PF15) to exit the Table List screen.
Exiting the Entry Panel

Press the END key (PF03/PF15) to exit the entry panel. Note After upgrading from a CONTROL-M release prior to 4.0.0, the first time you exit any previously existing scheduling table, you will receive an Exit Option window whether or not you have made any changes. Enter Y to save.
2 52
Online Facility: Scheduling Definition Facility Ordering (Scheduling) Jobs
Ordering (Scheduling) Jobs

Although job scheduling in the production environment is generally handled by CONTROL-M automatically (see Section 6 for more information), CONTROL-M provides several mechanisms for scheduling jobs manually. Among these are options to manually request job scheduling from the Table List screen and the Job List screen.
When manually requesting job scheduling from the Job List screen, specific jobs are selected. When manually requesting job scheduling from the Table List screen, tables are selected and each request applies to all the jobs in the selected tables.
Either of two options, O (Order) and F (Force), can be used in either of these screens to manually request job scheduling. These options work as follows: O ORDER Basic Scheduling parameters of the job(s) are checked against the requested scheduling date. If the job should be scheduled for that day, a job order is placed on the Active Jobs file. Basic Scheduling parameters of the job(s) are not checked. A job order is placed on the Active Jobs file whether or not the job should be scheduled that day.
FORCE
Note
With one exception, options O (Order) and F (Force) can be used in both the Job List screen and Table List screen for either regular scheduling tables or Group scheduling tables. The exception is: Option O (Order) cannot be specified for individual jobs in Group scheduling tables.
When you use the O and F options, a confirmation window is opened. The default confirmation window is illustrated below. If the default has been modified in the User profile, an alternate confirmation window, requiring double confirmation, is opened.
JOB LIST LIB: CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR OPT NAME --------------------------------------------------------------------STARTBKP +-------------------------------+ BACKPL01 | CONFIRM ODATE 090998 | O BACKPL02 <-----------| ASK FOR EACH ONE Y | BACKPLW1 +-------------------------------+ BACKPLW2 WEEKLY BACKUP OF FILES FROM APPL-L #2 BACKPLW3 WEEKLY BACKUP OF FILES FROM APPL-L #3 BACKPLW4 WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-L + DASDRPT1 DASD REPORTS AFTER BACKUPS FOR APPL-L DASDRPT2 DASD STATISTICS REPORT AFTER BACKUP FOR APPL-L ENDPLBKP END OF BACKUP INDICATION FOR APPL-L BACKAC01 DAILY BACKUP OF DATA SETS FROM APPL-ACCOUNT O BACKAC02 DAILY BACKUP OF SPECIAL FILES FROM APPL-ACCOUNT BACKACW1 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #1 BACKACW2 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #2 BACKACW3 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #3 BACKACW4 WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-ACC + DASDRPT3 DASD REPORTS AFTER BACKUPS FOR APPL-ACCOUNT DASDRPT4 DASD REPORTS AFTER BACKUP FOR APPL-ACCOUNT O ENDACBKP END OF BACKUP INDICATION FOR APPL-ACCOUNT BACKDD01 DAILY BACKUP OF DATA SETS FROM APPL-DD OPTIONS: S SELECT D DELETE I INSERT O ORDER F FORCE J JCL P PLAN 14.33.48
2 53
Online Facility: Scheduling Definition Facility Ordering (Scheduling) Jobs
The default confirmation window contains the following fields: CONFIRM Whether or not to process the order/force request. Valid entries are: Y (Yes) N (No) ODATE Process the order/force request. Cancel the request.
Scheduling date of the job/table, in mmddyy, ddmmyy or yymmdd format (depending on the site standard). The specified date can be modified.
ASK FOR EACH ONE This line is displayed only if more than one order/force option is requested. It determines whether or not individual confirmation is required for each order/force request. Valid values are: Y (Yes) Individual confirmation is required for each order/force request. The specified CONFIRM value (Y or N) applies only to the current order or request. Individual confirmation is not required for each order/force request. The specified CONFIRM operation is applied to all order/force requests. (If CONFIRM is Y, all order/force requests are processed; if CONFIRM is N, no order/force requests are processed.)
N (No)
When you press <ENTER>, the original list screen disappears and various messages appear in a new screen. If the messages span more than one screen, you can scroll up and down the message list. For each job which is successfully scheduled (ordered), the following message appears:
JOB name ODATE date ID=ordered PLACED ON ACTIVE JOBS FILE-description
Press END (PF03/PF15) to return to the Table/Job List screen.
2 54
Online Facility: Scheduling Definition Facility Copying Jobs to Another Table
Copying Jobs to Another Table

To copy one or more jobs from the current table to another table, specify option C (Copy) by the job name(s) in the Job List screen and press <ENTER>. The following window is displayed:
JOB LIST LIB: CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR OPT NAME -------- DESCRIPTION -----------------------------------------------STARTBKP START OF DAILY BACKUP BACKPL01 DAILY BACKUP OF DATA SETS FROM APPL-L BACKPL02 DAILY BACKUP OF SPECIAL FILES FROM APPL-L BACKPLW1 WEEKLY BACKUP OF FILES FROM APPL-L #1 BACKPLW2 +-----------------------------------------------------------+ BACKPLW3 | | C BACKPLW4 | SPECIFY DESTINATION LIBRARY,TABLE AND JOB NAME | DASDRPT1 | | DASDRPT2 | LIBRARY : CTM.PROD.SCHEDULE | ENDPLBKP | TABLE : | BACKAC01 | JOB : BACKPLW4 | BACKAC02 | | BACKACW1 | PRESS END/RESET TO CANCEL ENTER TO PERFORM THE COPY | BACKACW2 +-----------------------------------------------------------+ BACKACW3 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #3 BACKACW4 WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-ACC + DASDRPT3 DASD REPORTS AFTER BACKUPS FOR APPL-ACCOUNT DASDRPT4 DASD REPORTS AFTER BACKUP FOR APPL-ACCOUNT ENDACBKP END OF BACKUP INDICATION FOR APPL-ACCOUNT BACKDD01 DAILY BACKUP OF DATA SETS FROM APPL-DD OPTIONS S SELECT D DELETE I INSERT O ORDER F FORCE J JCL C COPY P PLAN 15.37.39
The window contains the following fields (some fields contain default values which can be modified): Library Table Library containing the table into which the job(s) should be copied. Must be an existing library. Default is the current library. Name of the table into which the job should be copied. Notes A job can only be copied to another table. It cannot be copied to its own table (even if the job is renamed). If the specified table does not exist, the table will be created when the request is performed. Job Name of the job to be copied. If multiple jobs are selected, the window is first displayed with the first selected job. As each request is performed or canceled, the next requested job name appears.
To perform a request, press <ENTER>. To cancel a request, press END (PF03/PF15) or RESET (PF04/PF16).
2 55
Online Facility: Scheduling Definition Facility Deleting Tables
Group entities cannot be copied. If a job in a group scheduling table is copied to a regular scheduling table, it is copied as a regular job (scheduling tags are dropped from the job scheduling definition). If a job in a group table is copied to a non-existing table, the table that is created is a regular table, not a group table. Notes When a job from a regular table is copied to a Group scheduling table, the job will retain its basic scheduling criteria and an empty SCHEDULE TAG field is inserted in the job scheduling definition. When a job from a Group scheduling table is copied to a Group scheduling table, the job retains its original scheduling tags.
Deleting Tables
Tables can be deleted from the Table List screen. To delete tables, specify option D (Delete) by the table names in the Table List screen and press <ENTER>. The confirmation window illustrated below is displayed, in sequence, for each table selected for deletion.
LIST OF TABLES IN CTM.PROD.SCHEDULE -------------(2) COMMAND ===> SCROLL===> CRSR OPT NAME --+--------------------------+ E INIT MOD ID ADABAS | CONFIRM DELETE OPTION | 0 70 0 O01 D APPLNTN <-----------| (Y/N) | 0 180 0 O01 APPLPRDI +--------------------------+ 1 41 0 O01 ARCNIGHT 01.00 98/09/09 98/09/09 00:50 5 5 0 S07 ASMBTR1 01.00 98/09/09 98/09/09 00:50 9 9 0 S07 D ASMBTR2 01.00 98/09/09 98/09/09 00:50 14 14 0 S07 BACKUP 01.00 98/09/09 98/09/09 00:50 5 5 0 S07 CICSJOBS 01.00 98/09/09 98/09/09 00:50 70 70 0 O01 CICSPROD 01.00 98/09/09 98/09/09 00:50 180 180 0 O01 CICSTEST 01.00 98/09/09 98/09/09 00:50 41 41 0 O01 CICSUPT 01.00 98/09/09 98/09/09 00:50 5 5 0 S07 CLIENTS 01.00 98/09/09 98/09/09 00:50 9 9 0 S07 DB2EXE 01.00 98/09/09 98/09/09 00:50 14 14 0 S07 DLOAD 01.00 98/09/09 98/09/09 00:50 5 5 0 S07 MAINDAY 01.00 98/09/09 98/09/09 00:50 180 180 0 O01 MAINT 01.00 98/09/09 98/09/09 00:50 41 41 0 O01 MAINTPL 01.00 98/09/09 98/09/09 00:50 5 5 0 S07 ONSPOOL 01.00 98/09/09 98/09/09 00:50 9 9 0 S07 D ONSPOOLT 01.00 98/09/09 98/09/09 00:50 14 14 0 S07 OPERCLN 01.00 98/09/09 98/09/09 00:50 5 5 0 S07 OPTIONS S SELECT O ORDER F FORCE G GRAPHIC FLOW B BROWSE D DELETE 15.38.37
Specify Y (Yes) in the window to confirm the delete request. Specify N (No) in the window to cancel the delete request.
2 56
Online Facility: Scheduling Definition Facility Displaying Graphic Jobflow
A message is written to the IOA Log file for each table deleted. Note If PDSMAN is operational at your site, $$$SPACE members will not be deleted.
Displaying Graphic Jobflow

The Graphic Jobflow screen provides a graphic presentation of the jobflow dependencies in a given scheduling table. It is displayed when option G (Graphic Flow) is specified for a table in the Table List screen. Use the scrolling PFKeys to scroll the Graphic Jobflow forward (PF08/PF20) and backward (PF07/PF19). Use the shifting PFKeys to shift the Graphic Jobflow right (PF11/PF23) and left (PF10/PF22). The FIND command (PF05/PF17), described earlier in this section, is supported in the Graphic Jobflow screen. To return to the Table list, press the END key (PF03/PF15). Two formats for the Graphic Jobflow screen are available, one for color displays and one for non-color displays. Graphic Jobflow for Color Terminals
---------------------- GRAPHIC JOBFLOW - TABLE PRODYH ---------------------- (2.G) COMMAND ===> SCROLL===> CRSR PRODYJCL ---> PRODYHTK -------------------> PRODYHST
PRODTHC2
--->
PRODYBCK
--->
PRODYIDK
--->
--->
PRODYBTL
--->
PRODYIZN
--->
PRODYEND
PROJYFOT
--->
PROJYMRG
--->
PROJYMTI
--->
PROJYHO1
--->
PROJYHO2
--->
PROJYDPY
--->
PROJYDTK
--->
PROYH11
---
---> PRESS END TO RETURN.
PROJYDLI
---> 15.38.44
LEFT AND RIGHT TO SEE MORE. COLUMNS: 001 - 080
Note
Size limits for the online display are narrower than the size limits for the printed chart. If the chart cannot be displayed online because it is too large, it may still be printed (see Section 8).
2 57
Online Facility: Scheduling Definition Facility Displaying Graphic Jobflow
On color terminals, the colors used to display the boxes and arrows can be changed by request. Available colors are sequenced in a loop. Each request changes to the next color in the sequence. Colors can be changed as follows: Change the color of the boxes Change the color of arrows Press PF04/PF16 Type ARROW in the COMMAND field and press 11 <ENTER>.
Graphic Jobflow for Non-Color Terminals

---------------------- GRAPHIC JOBFLOW - TABLE PRODYH ---------------------- (2.G) COMMAND ===> SCROLL===> CRSR .----------. .----------. .----------. | PRODYJCL |--->| PRODYHTK |--->--->--->--->--->| PRODYHST | ---------- ---------- | | .----------. .----------. .----------. | | .----------. | PRODTHC2 |--->| PRODYBCK |--->| PRODYIDK |--->| |--->| PRODYBTL | ---------- ---------- | | ---------- ---------- | | .----------. .----------. | |--->| PRODYIZN |--->| PRODYEND | ---------- ---------- ---------- .----------. .----------. .----------. | PROJYFOT |--->| PROJYMRG |--->| PROJYMTI | ---------- | | ---------- | | .----------. .----------. | |--->| PROJYHO1 |--->| PROJYHO2 | | | ---------- ---------- | | .----------. .----------. .----------. | |--->| PROJYDPY |--->| PROJYDTK |--->| PROYH11 |------------ | | ---------- | | | | .----------. | | | |--->| PROJYDLI |--->| | | | ---------- ---------- PRESS END TO RETURN. LEFT AND RIGHT TO SEE MORE. COLUMNS: 001 - 080 15.38.44
Note
Size limits for the online display are narrower than the size limits for the printed chart. If the chart cannot be displayed online because it is too large, it may still be printed (see Section 8).
11
PF05/PF17, which changed the color of arrows prior to CONTROL-M Release 5.0.0, now performs the FIND command.
2 58
Online Facility: Scheduling Definition Facility Displaying a Job Scheduling Plan
Displaying a Job Scheduling Plan

To display the scheduling plan of a job/group entity in calendar format, specify option P (Plan) by the job/group entity name in the Job List screen and press <ENTER>. The following window is displayed:
JOB LIST LIB: CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR OPT NAME ----- DESCRIPTION --------------------------------------------------STARTBKP START OF DAILY BACKUP BACKPL01 DAILY BACKUP OF DATA SETS FROM APPL-L BACKPL02 DAILY BACKUP OF SPECIAL FILES FROM APPL-L BACKPLW1 WEEKLY BACKUP OF FILES FROM APPL-L #1 BACKPLW2 WEEKLY BACKUP OF FILES FROM APPL-L #2 BACKPLW3 WEEKLY BACKUP OF FILES FROM APPL-L #3 BACKPLW4 WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-L + DASDRPT1 DASD REPORTS AFTER BACKUPS FOR APPL-L DASDRPT2 DASD STATISTICS REPORT AFTER BACKUP FOR APPL-L ENDPLBKP +---------------------+ BACKAC01 | FROM DATE 110198 | P BACKAC02 <-----------| TO DATE 113098 | BACKACW1 +---------------------+ BACKACW2 BACKACW3 WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #3 BACKACW4 WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-ACC + DASDRPT3 DASD REPORTS AFTER BACKUPS FOR APPL-ACCOUNT DASDRPT4 DASD REPORTS AFTER BACKUP FOR APPL-ACCOUNT ENDACBKP END OF BACKUP INDICATION FOR APPL-ACCOUNT BACKDD01 DAILY BACKUP OF DATA SETS FROM APPL-DD OPTIONS: S SELECT D DELETE I INSERT O ORDER F FORCE J JCL P PLAN 14.33.48
The window contains the following fields with default values which can be modified: FROM DATE TO DATE First date to be included in the job scheduling plan. Default is current working date. Last date to be included in the job scheduling plan. Default is one day less than one month after the current working date.
To display the plan, modify the defaults if desired. Press <ENTER>. The Job Scheduling Plan screen is displayed. To close the window without displaying the plan, press END (PF03/PF15) or RESET (PF04/PF16).
2 59
Online Facility: Scheduling Definition Facility Displaying a Job Scheduling Plan
Job Scheduling Plan Screen

For each month in the requested date range, beginning with the first month in the range, the Job Scheduling Plan screen displays a calendar which indicates the jobs schedule. Note The months (within the date range) in which the job (or jobs for a group schedule) is not scheduled are not displayed.
The dates within the date range on which the job will be scheduled, according to its basic scheduling criteria, are marked with an asterisk. Specify NEXT (PF08/PF11/PF20/PF23) or PREV (PF07/PF10/PF19/PF22) in the COMMAND field, or press the appropriate PFKey, to see the next or previous calendar month in the date range. Press the END key (PF03/PF15) to exit the Job Scheduling Plan screen and return to the Job List screen.
JOB NAME: BACKPL02 COMMAND ===> 01 1999 MON TUE JOB SCHEDULING DATES : 010199 - 310199 SCROLL===> SAT 02 SUN 03
WED
THU
FRI 01
04 * 11 * 18 * 25 *
05 * 12 * 19 * 26 *
06 * 13 * 20 * 27 *
07 * 14 * 21 * 28 *
08 * 15 * 22 * 29 *
09
10
16
17
23
24
30
31
CMDS: NEXT, PREV, END
19.30.51
The screen indicates the following: A. Job B. Range C. Month/Year D. Calendar E. Schedule Name of the job for which the schedule is requested. Requested date range, in mmddyy, ddmmyy, or yymmdd format (depending on the site standard). Month/Year currently displayed. Calendar (day of the week/date) for the currently displayed month. An asterisk under a date indicates that the job is scheduled on that day.
2 60
Online Facility: Tracking and Control Facility General
Tracking and Control Facility

General
The Tracking and Control facility provides relevant information about the status of each job and task in the Active environment and enables the user to manually intervene in the processing of jobs. The Active environment contains all the jobs in the Active Jobs file (i.e., all jobs that have recently executed, are currently executing, or are scheduled for possible execution in the near future). The main screen of the Tracking and Control facility is the Status screen (Active Environment screen), which displays a list of all jobs and their statuses in the Active environment. The Status screen is accessed by requesting option 3 on the IOA Primary Option menu. From the Status screen the user can request specific actions in relation to a job, or request the display of other screens which provide additional information and capabilities. Possible requests include:
Change the screens display type to display different information about the jobs in the Active environment. View only jobs belonging to a specific group. View statistical information about all jobs in the Active environment. Display the reason(s) why a job has not executed. Place a job in hold status. Delete a job from the Active environment. Undelete a job which has been deleted from the Active environment. Free a held job. Display the log messages of a job. Zoom in on the scheduling details of a job and modify certain parameters. Rerun a job. Confirm the restart/rerun of a job. View the list of all runs (job orders) of a particular job, and view the sysout of any or all of those job orders. Display the execution statistics of a job. Display and edit the JCL of a job. Display the list or network of predecessor/successor jobs of a specific job, and display critical path information. Force END OK termination of a job which has not been submitted or which ended NOTOK. Reactivate a job which has disappeared or which has failed with status Reason Unknown. Display the list of archived jobs and restore desired archived jobs to the Active environment.
2 61
Online Facility: Tracking and Control Facility Status Screen
Status Screen
To enter the Tracking and Control facility, select option 3 on the IOA Primary Option menu. The Status screen is displayed.
Filter: COMMAND ===> O Name Owner CICSPROD M22 CICSTEST M22 BRIVPCC IVP BRCC0001 IVP BRCC0002 IVP BRCC0003 IVP BRCCIND IVP BRUPDT02 IVP BRREP001 IVP BRREP002 IVP BRIVPCCE IVP CRCCEND IVP INTR0001 M22 Environment ------ UP <D> (3) SCROLL ==> CRSR Odate Jobname JobID Typ ------------ Status ------------090998 CICSPROD/04368 CST EXECUTING (RUN 1) GROUP=CICS-PROD 090998 CICSTEST/04372 CST EXECUTING (RUN 2) GROUP=CICS-TEST 090998 BRIVPCC /04369 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRCC0001/04382 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRCC0002/04383 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRCC0003/04384 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRCCIND /04385 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRUPDT02/04387 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRREP001/04388 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRREP002/04389 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 / JOB WAIT SCHEDULE GROUP=BR-IVP-CC 090998 / JOB WAIT SCHEDULE GROUP=BR-IVP-CC 090998 / JOB HELD WAIT SCHEDULE GROUP=INTER-PRODUCTION INTR0002 M22 090998 / JOB HELD WAIT SCHEDULE GROUP=INTER-PRODUCTION INTR0003 M22 090998 / JOB WAIT SCHEDULE GROUP=INTER-PRODUCTION INTR0004 M22 090995 INTR0004/04371 JOB ENDED- NOT "OK" - ABENDED Commands: OPt DIsplay Show HIstory RBal REFresh Auto Jobstat SHPF OPt command toggles between Commands and Options display 15.15.48 ------- CONTROL-M Active
It is assumed that the user wants to see the most recently ordered jobs first. Therefore, upon entry to the Status screen, the bottom of the Job list is displayed. Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) on the Status screen. AutoRefresh mode is available in this screen. To exit the Status screen, press the END key (PF03/PF15). For color terminals, jobs with different statuses are displayed in different colors. The 12 following colors have been defined as defaults for the following statuses (discussed later in this section): Blue and White Yellow Red Green Pink Jobs waiting to be scheduled Jobs which are executing or about to execute Jobs which are in error or ended NOTOK Jobs which ended OK or were forced OK Jobs which require special user action (e.g., Wait Confirmation)
12
See your IOA administrator to change color definitions.
2 62
Display Types of the Status Screen

The information in the Status screen can be displayed in different formats (i.e., display types). A number of predefined display types are available. While in the Status screen, the display type can be changed via the DISPLAY command. The DISPLAY command is described in Commands of the Status Screen later in this section. Predefined display types are: D A N Default display type. All info display type. Network display type.
The IOA administrator can use display type support to tailor the display layout by adding lines, fields, changing colors, etc. Additional information about display type support is provided in Customizing IOA Display Format Members in Section 2 of the IOA Administrator Guide. Note Member $$ACTDOC of the IOA MSG library contains information that is useful for customizing the CONTROL-M Status screen and creating/modifying display types for screens 3, 3.N, 3.G and the History Environment screen.
Upon reentering the screen, the last used display type is displayed. The Default (D) and All Info (A) predefined display types, and the fields they contain, are discussed in Format of the Status Screen later in this section. (The Network display type, although available in this screen, is generally useful only in the Job Network Dependency screen, and is described later in this section under that topic.) Primary/Alternate Bottom Lines The last two lines of the Status screen are used to display the list of available commands and options. Because there are too many commands/options to list at once, the list is divided into two parts (each part consisting of two lines) as follows:
Upon entry to the screen, the set of available commands is displayed. Because this list is displayed upon entry to the screen, it is referred to as the Primary Bottom line.
Commands: OPt DIsplay Show HIstory RBal REFresh Auto Jobstat SHPF OPt command toggles between Commands and Options display
15.15.48
Upon request (using command OPT), the set of available options is displayed (in place of the set of commands). The list of available options is referred to as the Alternate Bottom line.
Opt: ? Why L Log H Hold Z Zoom R Rerun A Activate O Force OK V View Sysout N Net D Del F Free S Stat G Group U Undelete J JCL Edit C Confirm 15.46.06
To toggle back and forth between the two sets of bottom lines, specify OPT in the COMMAND field and press <ENTER>. Available commands are described in Commands of the Status Screen, and available options are described in Options of the Status Screen, later in this section.
2 63
Format of the Status Screen

Display Type D (Default) Below is an example of the Default display type. It contains the most relevant information about the job.
Filter: COMMAND ===> O Name Owner CICSPROD M22 CICSTEST M22 BRIVPCC IVP BRCC0001 IVP BRCC0002 IVP BRCC0003 IVP BRCCIND IVP BRUPDT02 IVP BRREP001 IVP BRREP002 IVP BRIVPCCE IVP CRCCEND IVP INTR0001 M22 Environment ------ UP <D> (3) SCROLL ==> CRSR Odate Jobname JobID Typ ------------ Status ------------090998 CICSPROD/04368 CST EXECUTING (RUN 1) GROUP=CICS-PROD 090998 CICSTEST/04372 CST EXECUTING (RUN 2) GROUP=CICS-TEST 090998 BRIVPCC /04369 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRCC0001/04382 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRCC0002/04383 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRCC0003/04384 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRCCIND /04385 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRUPDT02/04387 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRREP001/04388 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 BRREP002/04389 JOB ENDED "OK" GROUP=BR-IVP-CC 090998 / JOB WAIT SCHEDULE GROUP=BR-IVP-CC 090998 / JOB WAIT SCHEDULE GROUP=BR-IVP-CC 090998 / JOB HELD WAIT SCHEDULE GROUP=INTER-PRODUCTION INTR0002 M22 090995 / JOB HELD WAIT SCHEDULE GROUP=INTER-PRODUCTION INTR0003 M22 090995 / JOB WAIT SCHEDULE GROUP=INTER-PRODUCTION INTR0004 M22 090995 INTR0004/04371 JOB ENDED- NOT "OK" - ABENDED Commands: OPt DIsplay Show HIstory RBal REFresh Auto Jobstat SHPF OPt command toggles between Commands and Options display 15.15.48 ------- CONTROL-M Active
Fields of Display Type D (Default) A Filter Name of the currently active screen filter (see Filtering the Status Screen Display later in this section.)
B CONTROL-M Status Indicator of whether CONTROL-M monitor is UP, DOWN or SUSP (suspended). C Display Type Indicator of the currently used display type (e.g., D for the Default display type).
The following is displayed for each job (D): O(ption) Name Owner Odate Jobname JobID Field for requesting options to be activated on jobs. Name of the member containing the jobs JCL, or name of the started task. ID of the owner of the job (formerly called USER ID). Original scheduling date of the job (see Date Definition Concepts in Section 1). Job name (generally available only after job submission). Job number (generally available only after job submission).
2 64
Typ Status
Task type or GRP. Job (task) status (see Job Statuses later in this section).
The following information can be displayed by request (see Commands of the Status Screen later in this section) along with the STATUS information: E Group F Cpu Group name of the job (see GROUP Command). ID of the CPU on which the job is executing or has executed. The CPU ID is displayed only for those jobs subjected to dynamic resource acquisition (i.e., jobs for which CONTROL-M dynamically decided to which CPU they would be submitted). Dynamically acquired resources are identified by a $ character in the Quantitative resource name. (See CPUID Command.) Order ID of the job (see ORDERID Command). Job description (see DESC Command).
Odate Jobname JobID Typ ------------ Status ------------090995 / JOB WAIT SCHEDULE GROUP=NRD-GRP CPU=A ORDERID=0003E ===> DAILY BACKUP-ACCOUNTING
G OrderID H Desc
O Name Owner TO5SP115 TO5
Display Type A (All Info) Below (A) is an example of the All Info display type. In addition to the Default information, it contains statistical information about the job run.
Filter: ------- CONTROL-M Active Environment ------ DOWN <A> - (3) COMMAND ===> SCROLL ==> CRSR O Name Owner Odate Jobname JobID Typ ------------ Status ------------DAILYPRD PRODMNGR 060698 JOB Wait Schedule OrderID 001Q6 Grp CTM-CONTROL MaxRC Time Fr: Due-In: 0859 Time Un: Due-Out: 0859 Res. Use: Y Priority: 00 Late:
Avg Elaps: 0000 RBA: 000002 DAILYSYS SYSTEM 060698 JOB Wait Schedule OrderID 001Q7 Grp CTM-CONTROL MaxRC Res. Use: Y Time Fr: Time Un: Priority: 00 Due-In: 0859 Due-Out: 0859 Late: Avg Elaps: 0000 RBA: 000003 CTMLDNRS PRODMNGR 060698 JOB Wait Schedule OrderID 001Q8 Grp CTM-CONTROL MaxRC Res. Use: Y Time Fr: Time Un: Priority: 00 Due-In: 0859 Due-Out: 0859 Late: Avg Elaps: 0000 RBA: 000004 CTMCLRES PRODMNGR 060698 JOB Wait Schedule Opt: ? Why L Log H Hold Z Zoom R Rerun A Activate O Force OK V View Sysout N Net D Del F Free S Stat G Group U Undelete J JCL Edit C Confirm 14.50.56
2 65
Fields of the Display Type A (All Info) Below is a description of fields in the All Info display type which do not appear in the Default display type. (Fields appearing in the Default display type are described above.) Grp MaxRC Res. Use Time Fr Time Un Priority Due-In Due-Out Late Name of the group. Highest return code returned for the job. Indicates (yes/no) whether or not the job uses (Control and/or Quantitative) resources. Time the job began execution. Time the job ended execution. Priority at which the job executed. Time by which the job was to be submitted. Time by which the job execution should complete. Indicates if the job is late. Valid (late) values are: I X O Avg Elap RBA Late In - the job was submitted late. Late Execution - the execution time was outside predefined limits. Late Out - the job ended outside the predefined time limit.
Average elapsed run time of the job. Relative Byte address of the job in the Active Jobs file.
Commands of the Status Screen

The following commands can be specified in the COMMAND field of the Status screen. OPT Command Command OPT toggles between the Primary Bottom line (composed of most of the available Primary commands) and the Alternate Bottom line (composed of all available options). DISPLAY Command Command DISPLAY is used to change display types. Format of the command is:
DISPLAY x (abbreviated DI x)
where x is the desired display type. For example, DI A displays the All Info display type. HISTORY Command Command HISTORY displays the jobs in the History Jobs file in the History Environment screen (described later in this section).
2 66
SHOW Command Command SHOW either activates the specified screen filter or opens the Show Screen Filter window, depending on the format of the command. Valid formats are: SHOW name EDIT SHOW name SHOW (PF02/PF14) Opens the Show Screen Filter window for the specified filter. Activates the specified filter. Opens the Show Screen Filter window for the currently active filter.
Note
Reserved filter name DEFAULT can be used to activate or edit the default filter for the status screen.
Only jobs conforming to selection criteria specified in the filter are displayed in the Status screen. (See Filtering the Status Screen Display later in this section.) GROUP Command Command GROUP (PF11/PF23) alternately displays/hides the group. When displayed, the name of the group appears after the job status. CPUID Command Command CPUID alternately displays/hides the CPU ID of jobs subjected to dynamic resource acquisition. When displayed, the CPU ID on which the job is running (or executed on) appears after the job status. DESC Command Command DESC alternately displays/hides the description of each job. ORDERID Command Command ORDERID alternately displays/hides the order ID of each job. VIEW Command Command VIEW (PF04/PF16) displays the Global View screen which provides a statistical overview of the status of jobs running under CONTROL-M. (See Global View Screen later in this section.) VIEW GRAPH Command Command VIEW GRAPH (abbreviated V G) displays the View Graph screen which provides a graphic statistical overview of the status of jobs running under CONTROL-M. (See View Graph Screen later in this section.) JOBSTAT Command Command JOBSTAT displays the Statistics screen which provides statistics for the specified job. (See Statistics Screen later in this section.)
2 67
RBAL Command Command RBAL scrolls the Status screen so that the job with the specified relative block address (RBA) is displayed at the top of the screen. Format of the command is:
RBAL rba
(abbreviated RB rba) where rba Relative block address of the job. This command is especially useful for determining which job is using a particular resource. The RBA of the job using a resource is indicated in the IOA Conditions/Resources screen (Screen 4). DUMP Command Command DUMP is intended for use only when specifically requested by the local IOA representative. It is used to set the abend capturing option ON/OFF. (The new screen program is designed to capture any abends resulting from either internal or external events.) Under certain circumstances, a dump may be required and/or requested by the local IOA representative. Valid formats of the command are: DUMP DUMP ON DUMP OFF Toggles between On/Off. Sets the Dump option to Yes. Sets the Dump option to No.
If a Dump is required, the DUMP ON command should be specified. Whenever the Dump is in ON status, the DUMP ON indicator is displayed in the first line of the screen. REFRESH Command Command REFRESH initiates recalculation of job dependency information. Although available in the Status screen, this command is generally used in the Job Dependency Network screen. Therefore, a detailed description of this command is provided in Commands of the Job Dependency Network Screen later in this section.
2 68
Options of the Status Screen

Select an option by specifying it in the Option field to the left of the job order and pressing <ENTER>. Available options are: ? Why Display the Why screen, which shows the reason(s) why the job is in the Wait Schedule status (see Why Screen later in this section). Display the Group Entity (GRP entry), and all jobs that belong to that group. This option can be entered next to a GRP entry, or next to any job that belongs to a group. (Jobs belonging to a group are marked with a G to the right of the group name under display type A.) Option G must be specified as the last option in the screen. When the Group option is requested, the name of the selected group appears in the title line of the screen. H Hold Hold the job order. Only CONTROL-M operations concerning the job order are halted. If the job is currently in the operating systems job queue, or is executing, the job is not held. The HOLD request is recorded in the IOA Log file. The status of the job is changed to REQUESTED HELD. If the CONTROL-M monitor is active, the status changes to HELD. In some cases, a HOLD request may be rejected by the monitor. Delete the job (see Delete Confirmation Window later in this section). Free a held job order. All CONTROL-M operations for the job order are resumed. If the job is currently in the operating systems job queue in HOLD state, the job is not released. The FREE request is recorded in the IOA Log file. The status of the job is changed to REQUESTED FREE. If the monitor is active, the FREE request is accepted after a few seconds. Display the Log screen, which shows all IOA Log messages for the specified job (see IOA Log Screen later in this section). Display the Zoom screen which Zooms in on job details (see Zoom Screen later in this section). Rerun the job. A Rerun window is displayed (described later in this section). Confirm that this job should be scheduled. An appropriate confirmation window is displayed to permit user confirmation (described later in this section).
G Group
D Del F Free
L Z
Log Zoom
R Rerun C Confirm
V View Sysout View the jobs execution history in the Job Order Execution History screen. From this screen, the Sysout Viewing screen (which displays the archived SYSDATA of the job) can be requested. (Both screens are described later in this section.) S Stat Display the Statistics screen, which shows (see Statistics Screen later in this section). job run statistics
Statistics for a job which is not in the Active environment can be displayed using command JOBSTAT (discussed in Statistics Screen).
2 69
13
JCL
Edit the member that contains the JCL of the job. The JCL member is displayed in ISPF Edit mode. By default, if the specified JCL member exists in the OVERLIB library, that member is edited. If the JCL member does not exist in the OVERLIB library, the member is edited in the MEMLIB library.
A Activate
Reactivate a job/started task which has a status of either DISAPPEARED or FAILED REASON UNKNOWN. CONTROL-M searches the MVS/JES queues for the disappeared or failed job (or started task). A job/started task is assigned a DISAPPEARED status if it has been accidentally deleted. (Also, if JES is very busy, it sometimes sets the status of a job/started task to DISAPPEARED even though the job/started task actually exists.) A job/started task is assigned a status of FAILED REASON UNKNOWN whenever CONTROL-M encounters a problem reading the jobs SYSDATA files and therefore cannot check the completion status of the job.
N Net
Display the Job Dependency Network screen which shows all the predecessor and successor jobs for the selected job. (See Job Dependency Network Screen later in this section.) Force the job to complete with ENDED OK status. (See Force OK Confirmation Window later in this section.) Cancel a previously requested Delete. Valid only for jobs deleted by request. The job is returned to its status prior to the delete request. Display the CONTROL-M/WorkLoad Steps Status screen for the selected job. Valid only for jobs under the control of CONTROL-M/WorkLoad. (The CONTROL-M/WorkLoad Steps Status screen is described in Section 2 of the CONTROL-M/WorkLoad User Manual.)
O Force OK U Undelete W WorkLoad
13
Called the E (EDIT) option prior to CONTROL-M Release 4.0.0, this option is available only when operating CONTROL-M under TSO/ISPF.
2 70
Job Statuses
The following job statuses can appear in the Status screen:
WAIT CONFIRMATION (WITH RESTART) Job is waiting for manual restart confirmation. WAIT CONFIRMATION (FOR SCHEDULE) Job is waiting for manual confirmation before it can be scheduled. WAIT SCHEDULE Job is waiting to be scheduled.
WAIT SCHEDULE ON SPOOL Job is waiting to be scheduled but is already in input queue on spool. WAIT SCHEDULE (PIPE) WAIT SUBMISSION WAIT RELEASE GOING TO START SUBMITTED RELEASED STARTED WAIT EXECUTION EXECUTING For CONTROL-M/WorkLoad users. Job is waiting to be scheduled and is a participant in a Pipe (Collection). Job is eligible to be run and is about to be submitted. On Spool job is eligible to be run and is about to be released. Started task is eligible to be run and is about to be activated. Job submitted, but is not yet in the operating systems job queue. On Spool job has been released and is waiting to be executed. Started task started, but is not yet in the operating systems job queue. Job is in the operating systems job queue waiting to be executed. Job is executing.
EXECUTING (SYSOUT IN HOLD STATUS) Job was placed in HOLD status by an operator-issued JES HOLD command before CONTROL-M could read the jobs output.
R
CLEANUP ENDED OK
Job is being run for Cleanup. Job finished executing OK.
ENDED OK FORCED OK Job ended OK due to a Force OK request. ENDED NOT OK Job ended NOT OK.
ENDED NOT OK ABENDED Job abended. ENDED NOT OK JCL ERROR Job failed due to JCL error. ENDED NOT OK FAILED REASON UNKNOWN (This usually occurs following a system crash.)
2 71
ENDED NOT OK DUE TO CC Condition code which is not defined as OK has occurred. ENDED NOT OK RERUN NEEDED Rerun is needed for the job. ENDED NOT OK RERUN WAS NEEDED Rerun was required for the previous execution of the job. ENDED NOT OK TERM ON NCT2 CONTROL-M due to a NOT CATLGD 2 error. NOT SUBMITTED NOT STARTED (WITH RESTART) Submission of the job failed. Starting of the started task failed. The CONTROL-R restart step will be added to the JCL of the job when it is submitted (i.e., a restart will be performed). Job has run (executed) with the CONTROL-R restart step (i.e., a restart has been performed). Job not found in the queue. Check that the job or its sysout has not been accidentally deleted. This status can also appear when JES is very busy. In such a case, CONTROL-M waits for JES until it confirms that the job is lost. not found at least once, this status displays the times (n) CONTROL-M has looked for the job. If 14 still not found after 10 times, the status is DISAPPEARED.
R
(RESTARTED) NOT FOUND
BUT NOT FOUND n TIMES If a job is number of the job is changed to Example
JOB SUBMITTED BUT NOT FOUND 5 TIMES
The job was submitted, but may have been purged. After checking 10 times, CONTROL-M will change the status to DISAPPEARED. DISAPPEARED HELD RUN n PRIOR RUN REQUESTED HELD Job disappeared completely. This status only occurs after a NOT FOUND status. Job is in hold status. Run number. Incremented each time a cyclic task is executed or a job is rerun. Termination status of the previous job (or cyclic task) execution (for jobs that have been rerun). A hold request was issued for the job, but the request has not yet been performed by the CONTROL-M monitor.
14
This default number can be changed by your IOA administrator.
2 72
REQUESTED FREE REQUESTED RERUN DELETED REQUESTED CHANGE
A free request was issued for a held job, but the request has not yet been performed by the CONTROL-M monitor. A rerun request was issued for the job, but the request has not yet been performed by the CONTROL-M monitor. The job order was deleted by an authorized user. Job parameters were changed via the Zoom option, but the request has not yet been performed by the CONTROL-M monitor. An activate request was issued for a job, but the request has not yet been performed by the CONTROL-M monitor.
REQUESTED REACT
PROBLEMS READING SYSOUT Usually means that problems prevent the CONTROL-M monitor from reading the jobs output. LATE LATE SUBMISSION LATE EXECUTION ON OUTPUT QUEUE NJE JOB Job did not finish executing by the time specified in a SHOUT WHEN LATE statement. Job was not submitted by the time specified in a SHOUT WHEN LATESUB statement. Jobs elapsed runtime is outside of the acceptable limits defined in a SHOUT WITHIN EXECTIME statement. Job is on the output queue of the remote NJE node or on the output queue of the host node with a changed job ID. The job is not currently found in either Remote or Host node, but is in the process of transmission between nodes. (Either the job is being transmitted to the Remote node for execution, or the jobs sysdata output is being transmitted to the Host node.) CONTROL-M continues to search for the job until it is located on one of the nodes. The job ID of the NJE job has changed. When the jobs sysdata output was transmitted back to the Host NJE node, the CONTROL-M monitor detected that the original job ID of the NJE job is occupied by another job. The CONTROL-M monitor continues to search for a job to match the new job ID.
NJE JOB (ID CHANGED)
Group Statuses The following Group statuses can appear for the group entity in the Status screen: ACTIVE All runtime criteria for the Group entity have been satisfied, but at least one job in the group has not ended and no job in the group has ended NOTOK. All runtime criteria for the Group entity have been satisfied, but at least one job in the group has not ended and one or more jobs in the group ended NOTOK. All jobs in the group ended OK.
ACTIVE- IN ERROR
ENDED OK
2 73
ENDED NOTOK ORDERING
All jobs in the group have ended. At least one job ended NOTOK. Ordering is in process or has failed; not all jobs have been ordered. (The group remains in this status until all jobs have been ordered or until all jobs belonging to the group are deleted.)
Filtering the Status Screen Display

Screen filters can be used to filter the Status screen display. A filter consists of a set of record selection criteria (selection fields and their values). Only records which conform to selection criteria specified in the filter are displayed in the screen. The IOA administrator can predefine filters and place them in the General profile. Each user can define multiple filters for the screen via the Show Screen Filter window (described below). Each filter belongs to, is assigned a name by, and can only be activated by, the user who defined it. It is stored in the User profile.
15
A predefined default filter (called DEFAULT) is supplied for the Status screen. Site-defined defaults determine whether the last filter used or the DEFAULT filter will be activated upon reentry to the Status screen. To activate an existing filter in the Status screen (without opening the Show Screen Filter window), specify the SHOW command in the COMMAND field, as follows:
SHOW name
where: name Name of the filter to be activated.
Show Screen Filter Window To open the Show Screen Filter window in the Status screen for purposes of creating or modifying a filter, specify the SHOW command in the COMMAND field, as follows:
To open the window for the currently active filter, specify:

SHOW (PF02/PF14)
To open the window for a new or existing filter, specify:

SHOW name EDIT
where: name Name of the filter to be displayed in the Show Screen Filter window.
15
Called the Show Option window prior to CONTROL-M Release 5.0.0.
2 74
The Show Screen Filter window is displayed:

Filter: COMMAND ===> O Name Owner TST144 TEST TST57 TEST TST84 TEST TST43 TEST TST71 TEST TST453 TEST TST44 TEST TST85 TEST TST72 TEST PRD1 PROD ------- CONTROL-M Active Environment ------ UP <D> - (3) +------------------- Show Screen Filter -----------(3.SHOW)+ | Filter Save (Y/N) | | Memname | | Group | | | | In Process Y | Ended Y | State Y | | ------------------------------------------------------ | | Wait Sched Y | Ended "OK" Y | Free Y | | Wait Confirm Y | Not "OK" Y | Held Y | | Wait SUB Y | Rerun Y | On Request Y | | Submitted Y | Disappeared Y | Deleted N | | Wait Exec Y | Abended Y | Late ONLY N | | Executing Y | Unexpected CC Y | | PRD2 PROD | On Output Que Y | JCL Error Y | | | Task Type: Job Cyc Emr Stc Cst Est Ecj Ecs Wrn Grp | PRD3 PROD | Y Y Y Y Y Y Y Y Y Y | | Res Name | DAILYPRD PRODMNG | Resource Type: In Y Out Y Conds Y Resource Y Control Y | DAILYSYS SYSTEM | Owner | CTMLDNRS PRODMNG | Odate: From To Priority | CTMCLRES PRODMNG | Pipe : | Commands: OPt DIsp +----------------------------------------------------------+ OPt command toggles between Commands and Options display 12.25.21
Note
Depending on User Profile definition, field Late ONLY (A) may be replaced by field Late.
Fields of the Show Screen Filter Window The Show Screen Filter window contains the following fields: Filter User-assigned name of the filter. The name specified in the Filter field can be modified. If there are unsaved changes to a filter in memory (see Closing the Show Screen Filter Window below), an asterisk appears to the right of the filter name. Save (Y/N) Specifies whether or not to save modifications to the filter upon closing the window.
The fields listed below define the selection criteria to be applied to the screen. Fill in these selection criteria as desired. Note The selection criteria below marked with the symbol G act on a prefix basis. For example, specifying value D4 in filed MEMNAME will result in the retrieval of all members (jobs) whose names start with D4.
2 75
Memname Group status
Show only jobs of the specified member name(s). A maximum of five member names can be specified. Show only jobs of the specified group(s). A maximum of four groups can be specified. Select only jobs which conform to the status selection criteria. Statuses are divided into three groups under the following headings: In Process, Ended, and State. Notes For statuses under the first two groups (In Process and Ended), the following logic applies:
Specifying Y for a heading enables filtering of jobs with a status listed under that heading on a status-by-status basis. (Specify N by a status to filter jobs with that status out of the display.) Specifying an N for a heading filters out any job with a status listed under that heading, even if the status is marked Y.
(If N is specified for all three headings, no jobs are displayed.) In Process This heading is for statuses of jobs that are not yet finished. Wait Sched Wait Confirm Wait Sub Submitted Wait Exec Executing On Output Que Jobs waiting to be scheduled. Jobs waiting for confirmation. Jobs waiting to be submitted. Jobs submitted but not yet in queue. Jobs waiting to be executed. Jobs which are currently executing. Jobs on the output queue but not yet processed by CONTROL-M (e.g., because of a system crash).
Ended
This heading is for statuses of finished jobs. Ended OK Not OK Rerun Disappeared Abended Unexpected CC JCL Error Jobs that ended OK. Jobs that ended NOTOK. Jobs that require rerun. Jobs that disappeared from the job queue. Jobs that abended. Jobs that ended with a condition code that is not defined as OK. Jobs that ended (or did not run) because of a JCL error.
2 76
Notes
For statuses under group state, the following logic applies:
As with In Process and Ended, specifying Y for a heading enables filtering of jobs with a status under that heading on a status-by-status basis. (Specify N by a status to filter jobs with that status out of the display.) Specifying N treats all statuses under the group as if they were all set to Y, regardless of the value actually specified by each status. This heading is for state criteria which can further filter the statuses under the other headings (e.g., WAIT SCHEDULE HELD, WAIT SCHEDULE). Free, Held, Deleted Jobs which are in the specified state. On Request Jobs for which a change in job status has been requested by a CONTROL-M user, but the request has not yet been processed by the monitor.
State
Late ONLY/Late Jobs that were submitted, or finished executing, late; or jobs with an elapsed execution time outside of specified limits. By default, field Late ONLY is displayed. If the User profile has been modified accordingly, field Late is displayed. If Y (Yes) is specified for field Late ONLY, only late jobs are displayed. If Y is specified for field Late, late jobs are displayed along with other jobs in the display. Whenever N (No) is specified, this criteria has no effect on the display. Task Type Limit the task types of jobs to be displayed. Valid task types are: Job Cyc Emr Stc Cst Est Ecj Ecs Wrn Grp Regular job Cyclic job Emergency job Started task Cyclic started task Emergency started task Emergency cyclic job Emergency cyclic started task Warnings. Supported for historical reasons Group Entity
2 77
Res Name
An additional cross reference for all jobs that are using a Control resource, Quantitative resource, or prerequisite condition. A maximum of two names can be specified. The resources and conditions are searched according to those specified as Y (Yes) in Resource Type (described below). Type of Resource or prerequisite condition to be used to filter the display of the status screen. In Out Conds Resource Control All prerequisite conditions appearing in IN statements. All prerequisite conditions appearing in OUT statements. All prerequisite statements. conditions appearing in DO COND
Resource Type
All Quantitative resources. All Control resources.
Owner Odate
16
Show only jobs of the specified owner(s). A maximum of five owners can be specified. Show only jobs whose original scheduling date falls within the specified From/To date range. Date format is mmddyy, ddmmyy, or yymmdd depending on the site standard. If a From date is specified without a To date, the current date is used as the To date.
Priority Pipe
Show only jobs with the specified priority. Show only job participants in the specified pipe.
Closing the Show Screen Filter Window The filter you have edited can be activated with or without saving changes, depending on the value specified in the Save field, as follows:
To activate and save the filter, specify Y (Yes) in the Save field. Changes to the filter will be permanently saved. To activate the filter without saving it, specify N (No) in the Save field. Changes will be kept in memory only, but not saved.
After specifying a value in the Save field, press one of the following keys: <ENTER> Filtering begins with the first job currently displayed in the screen and continues downward.
PF07/PF19 (UP) Filtering begins with the first job in the Active Job list and continues downward. PF08/PF20 (DOWN) Filtering begins with the last job in the Active Job list and continues upward.
16
OWNER was called USER ID prior to CONTROL-M Release 4.0.0.
2 78
Online Facility: Tracking and Control Facility Global View Screen
The window is closed and the filter will be activated as defined or modified. To cancel changes made in the Show Screen Filter window, use the RESET command (PF04/PF16). The changes are canceled regardless of the value specified in the Save field, the window is closed, and the filter that was previously in effect is restored. By default, using the END command (PF03/PF15) in the window works like pressing <ENTER>. However, the default can be modified so that END works like RESET.
Global View Screen

The Global View screen is displayed by typing the VIEW command (abbreviated V) in the COMMAND field of the Status screen and pressing <ENTER>, or by pressing PF04/PF16 in the Status screen. This screen provides a statistical overview of the status of the jobs running under CONTROL-M. Information is presented by GROUP name, by date (i.e., separate statistics for the same group name on different dates). Note All jobs having the same group name are grouped together, including jobs from different tables of different types.
-------------------------- GLOBAL VIEW - BY GROUP ---------------------(3.VIEW) COMMAND ===> SCROLL===> CRSR TOTAL WAIT SCHEDULE 647 EXECUTING 19 END NOTOK 9 END OK 2014 STAT WS ER * EN WS WS WS ER GROUP--------------CTM-CONTROL PROD-ONSPOOL DD-DAY-PROD BR-IVP-CC SYSTEMS-JOBS PROD-KPL MT-PRODUCTION ODATE #WSC #EXC #END 090997 1 4 090997 43 090997 42 090997 8 28 090997 4 22 090997 47 090997 10 24 090997 9 MEMNAME -----JOB STATUS----CTMCLRES WAIT SCHEDULE P0* ENDED NOTOK S0C4
ER APPL-PROD-INTERNAL
RN PR-PRODUCTION
090997
10
RN VIJ-JOBS COMMANDS:
090997
REFRESH (VIEW DATA)
BRIVPCCE WAIT SCHEDULE SMFCLEAN WAIT SCHEDULE PRDKPL01 WAIT SCHEDULE MTPRQV ENDED NOTOK S0C1 MTRRU04 ENDED NOTOK U0016 2 2 INTPRD02 ENDED NOTOK C0008 INTPRD01 EXECUTING INTPRD1A WAIT EXECUTION 6 24 PRDINP6A EXECUTING PRDRPT99 EXECUTING PRDDFN EXECUTING PRDRPT10 EXECUTING PRDUPD12 EXECUTING PRDUPD14 WAIT EXECUTION 4 42 VIJJBNX ENDED NOTOK NOMEM VIJRUN22 ENDED NOTOK JNRUN END (RETURN TO STATUS SCREEN) 15.35.49
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) on the Global View screen. AutoRefresh mode is available under this screen. To update the screen, press the REFRESH key (PF04/PF16). To return to the Status screen, press the END key (PF03/PF15).
2 79
Online Facility: Tracking and Control Facility Global View Screen
Fields of the Global View Screen

A. Totals line Displays the totals from the data. The following summary information is displayed for all jobs in the Active Jobs file except emergency jobs: WAIT SCHEDULE Total number of jobs waiting to be scheduled. EXECUTING END NOTOK END OK B. Data lines Display the following information about each group: STAT Status of the group: WS ER RN Wait Scheduling. All jobs are waiting to be scheduled (no jobs have begun running). Error. At least one job has finished running and had an error. Running. At least one job is running (executing); not all jobs have finished executing; and no jobs have ended NOTOK. Ended OK. All jobs have finished running and ended OK. Total number of jobs executing. Total number of jobs currently in ended NOTOK status. Total number of jobs that ended OK.
* EN GROUP ODATE #WSC #EXC #END MEMNAME Name of the group.
Original scheduling date of the group (see Date Definition Concepts in Section 1). Number of jobs in Wait Schedule state. Number of jobs executing (or in the input queue). Number of jobs which have finished executing. Name of each active member (job) in the group. The members that will be displayed are:
Executing (or in the input queue). Ended NOTOK. If none of the above is found within the group, the first job which is
waiting to be scheduled. JOB STATUS Status of each job in the group. In case of error, the type of error is shown (e.g., abend code).
2 80
Online Facility: Tracking and Control Facility View Graph Screen
View Graph Screen

The View Graph screen is displayed by typing the VIEW GRAPH command (abbreviated V G) in the COMMAND field of the Status screen and pressing <ENTER>. This screen provides a statistical overview of the status of the jobs running under CONTROL-M, in graph form. Information is presented by GROUP name. Note All jobs having the same group name are grouped together, including jobs from different tables of different types.
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) on the View Graph screen. AutoRefresh mode is available under this screen. To update the screen, type the command REFRESH and press <ENTER>, or press PF04/PF16. To return to the Status screen, press the END key (PF03/PF15). Two formats for the View Graph screen are available, one for color displays and one for non-color displays. They are discussed on the following pages.
View Graph Screen Format for Color Terminals

--------------------------- VIEW GRAPH - BY GROUP --------------------(3.GRAPH) COMMAND ===> SCROLL===> CRSR TOTAL WAIT SCHEDULE 674 EXECUTING 28 END NOTOK 11 END OK 1549 GROUP NAME -------------SUM ----+---10----+---20----+---30----+---40----+---50EBD-PRODUCTION 27 GPL-PRODUCTION 35 MT-PRODUCTION 40 VEJ-JOBS 39 PROD-KPL 16 INTER-PRODUCTION 42 NTN-APPLICATION 35 APPL-PROD-INTERNAL 37 CLIENTS-STATEMENTS 38 PR-PRODUCTION 40 BR-IVP-CC 10 SYSTEMS-JOBS 36 CICS-BATCH-JOBS 28 DD-NIGHT-PROD 37 BKP-PROD-L 10 BKP-PROD-ACCOUNT 9 BKP-PROD-DD 14 FDS-JOBS 39 JJL-NIGHT-PROD 33 COMMANDS: REFRESH (VIEW DATA) END (RETURN TO STATUS SCREEN) 01.26.56
2 81
Fields of the View Graph Screen A. Totals line Displays the totals for the data. The following summary information is a displayed for all jobs in the Active Jobs file except emergency jobs: WAIT SCHEDULE Total number of jobs waiting scheduling. EXECUTING END NOTOK END OK Total number of jobs executing. Total number of jobs currently in ended NOTOK status. Total number of jobs that ended OK.
The data lines display the following information for each group: B. GROUP NAME C. SUM D. JOB GRAPH E. Scale Name of the group. Total number of jobs in the group. Job graph indicates the number of jobs in each status, in each group. Scale line used to simplify reading the number of jobs of each status in the group. The scale used (i.e., the number of jobs represented by each column) automatically adjusts based on the number of jobs in the group containing the most jobs.
Job Graph In the job graph (D), job statuses are differentiated by color, as follows: Blue Yellow Red Green WAIT SCHEDULE EXECUTING END NOTOK END OK
17
For each group in the graph, the number of columns of a particular color depends on the number of jobs having that status.
17
Because this manual is printed in black and white, the different colors in the screen are represented by different shadings in this manual.
2 82
View Graph Screen Format for Non-color Terminals

--------------------------- VIEW GRAPH - BY GROUP --------------------(3.GRAPH) COMMAND ===> SCROLL===> CRSR TOTAL WAIT SCHEDULE 674 EXECUTING 28 END NOTOK 11 END OK 1549 GROUP NAME -------------SUM ----+---10----+---20----+---30----+---40----+---50EBD-PRODUCTION 27 $$$$$%%%%%%%%%%%%%%%%%%%%% GPL-PRODUCTION 35 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% MT-PRODUCTION 40 $$$$$$$$$$+++**%%%%%%%%%%%%%%%%%%%%%%%%% VEJ-JOBS 39 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% PROD-KPL 16 $$$$$$$$$$$$$$$$ INTER-PRODUCTION 42 $$+++++*%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% NTN-APPLICATION 35 *%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% APPL-PROD-INTERNAL 37 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$* CLIENTS-STATEMENTS 38 +++++++%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% PR-PRODUCTION 40 $$$$$$$$$$++%%%%%%%%%%%%%%%%%%%%%%%%%%%% BR-IVP-CC 10 $$$$$$$$$$ SYSTEMS-JOBS 36 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$% CICS-BATCH-JOBS 28 +++++*%%%%%%%%%%%%%%%%%%%%%% DD-NIGHT-PROD 37 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$% BKP-PROD-L 10 $$$$$$$$$$ BKP-PROD-ACCOUNT 9 $$$$$$$$$ BKP-PROD-DD 14 $$$$$$$$$$$$$$ FDS-JOBS 39 +*%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% JJL-NIGHT-PROD 33 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ COMMANDS: REFRESH (VIEW DATA) END (RETURN TO STATUS SCREEN) 01.26.56
Fields of the View Graph Screen A. Totals line Displays the totals for the data. The following summary information is a displayed for all jobs in the Active Jobs file except emergency jobs: WAIT SCHEDULE Total number of jobs waiting scheduling. EXECUTING END NOTOK END OK Total number of jobs executing. Total number of jobs currently in ended NOTOK status. Total number of jobs that ended OK.
The data lines display the following information about each group: B. GROUP NAME C. SUM D. JOB GRAPH E. Scale Name of the group. Total number of jobs in the group. Job graph indicates the number of jobs in each status, in each group. Scale line used to simplify reading the number of jobs of each status in the group. The scale used (i.e., the number of jobs represented by each column) automatically adjusts based on the number of jobs in the group containing the most jobs.
2 83
Online Facility: Tracking and Control Facility Why Screen
Job Graph In the job graph (D), job statuses are differentiated by symbols, as follows: $ + * WAIT SCHEDULE EXECUTING END NOTOK
% END OK For each group in the graph, the number of columns containing a particular symbol depends on the number of jobs having that status.
Why Screen
The Why screen is displayed when the ? (Why) option is specified on the Status screen. The Why screen shows the reason(s) why a job is in WAIT SCHEDULE status.
------------------------ PRUPDT02 SCHEDULING ANALYSIS --------------------(3.?) COMMAND ===> SCROLL===> CRSR OPT DESCRIPTION TIME LIMIT RESOURCE FROM 1730 DB2-POWER HELD HELD HELD HELD HELD CARTRIDGE HELD HELD UNTIL 0200 QUANTITY 0030 PRDKPL01 (Q) QUANTITY GPLIR17A (Q) QUANTITY INTR0002 (Q) QUANTITY PRUPDOLV (Q) QUANTITY MTPRQV (Q) QUANTITY QUANTITY 0002 PRDKPL01 (Q) QUANTITY GPLIR17A (Q) QUANTITY
BY BY BY BY BY BY BY
0022 0020 0015 0010 0025 0001 0002
RESOURCE
IN HOLD STATE CONDITION PRUPDT01-ENDED-OK ODATE 0909 GROUP SCHEDULING ANALYSIS FOR GROUP ACCOUNT (ACCOUNT-GROUP) GROUPS RUNTIME CRITERIA SATISFIED ====== >>>>>>>>>>>>>>>>>>>>> END OF "WHY" LIST <<<<<<<<<<<<<<<<<<<<< =====
OPTION:
A ADD CONDITION
10.32.27
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) on the Why screen. To return to the Status screen, press the END key (PF03/PF15).
2 84
Possible WHY reasons are:
ALL RUNTIME CRITERIA SATISFIED. JOB WILL BE SUBMITTED SOON CONTROL-M MONITOR IS NOT ACTIVE IN HOLD STATE WAIT CONFIRMATION TIME LIMIT FROM hhmm UNTIL hhmm NEXT RERUN/CYCLIC RUN FROM hhmm CONDITION condition-name ODATE mmdd Prerequisite condition required by the job, along with its original scheduling date. RESOURCE resource-name [R] QUANTITY quantity BY priority memname Name and quantity of a Quantitative resource not currently available for the job. For critical path jobs, a job with a higher path priority than the current job is also identified.
CONTROL OVER resource TYPE type BY priority memname [ownership type] Name and type of a Control resource currently being used by another job order whose name is specified. For critical path jobs, path priority of the owner is also identified.
JOB WAIT FOR PIPES COLLECTION PIPE pipename The job was not run for one of the following reasons: CONTROL-M is waiting for the minimum number of participants in the indicated pipe. At least one prerequisite (prerequisite condition, resource, confirmation, etc.) for a participant in the indicated pipe is not satisfied.
If the job belongs to a Group scheduling table, the Why screen displays messages related to both the selected job and the group to which the job belongs. In this case, the reasons indicated above can be applicable to the selected job and/or to the group. To enable the user to distinguish between job reasons and group reasons, the job reasons appear in the screen before the group reasons, and the two sets of reasons are separated by the following line:
GROUP SCHEDULING ANALYSIS FOR GROUP group-memname (groupname)
In addition to the above line, the following reasons can appear only for a job in a Group scheduling table:
JOBS RUNTIME CRITERIA SATISFIED This reason applies to the job. GROUPS RUNTIME CRITERIA SATISFIED This reason applies to the group.
2 85
Adding Conditions in the Why Screen

If the Why screen indicates that a job is waiting for prerequisite conditions, the indicated conditions can be manually added via the Why screen by specifying option A (Add Condition) in the OPT (Option) field next to the condition. Specify option A for every condition to be added, and press <ENTER>. When adding conditions, a Confirmation window may be displayed depending on User profile customization:
By default, when option A is specified in the Why screen, a Confirmation window is displayed only when the conditions date reference is **** or $$$$. Addition of conditions without generic date references is performed without confirmation from the user. If, however, the User profile has been customized accordingly, the following Confirmation window is always displayed when option A is specified.
------------------------ WRUPDT02 SCHEDULING ANALYSIS --------------------(3.?) COMMAND ===> SCROLL===> CRSR OPT DESCRIPTION +-------------------------+ | CONFIRM MMDD 0909 | A CONDITION PROD-WRUPDT03-GO <--------| ASK FOR EACH ONE Y | A CONDITION PROD-WRUPDT03-CHECK +-------------------------+ A CONDITION PROD-WRUPDT03-FLAG ODATE 0909 ====== >>>>>>>>>>>>>>>>>>> END OF "WHY" LIST <<<<<<<<<<<<<<<< =====
OPTION:
A ADD CONDITION
18.15.36
2 86
Fill in or modify the fields of the Confirmation window as follows and press <ENTER>. CONFIRM Confirms whether or not to process the Add Condition request. Valid values are: Y (Yes) N (No) date Process the Add Condition request. Cancel the request.
Date of the listed condition.
If the date reference of the listed condition contains **** or $$$$, the
date field of the window is unprotected and you must explicitly specify the date in the date field.
If the date reference of the listed condition is a specific date (in either
mmdd or ddmm format, depending on the standard in use at the site), the date field of the window is protected and its value cannot be changed. ASK FOR EACH ONE This line is displayed only if more than one Add Condition is requested. It determines whether or not individual confirmation is required for each Add Condition request. Valid values are: Y (Yes) Individual confirmation is required for each Add Condition request. The specified CONFIRM value (Y or N) applies only to the current Add Condition request. Individual confirmation is not required for each Add Condition request. The specified CONFIRM operation is applied to all Add Condition requests. (If CONFIRM is Y, all Add Condition requests are processed; if CONFIRM is N, no Add Condition request are processed.)
N (No)
2 87
Online Facility: Tracking and Control Facility Deleting a Job
Deleting a Job
To delete a job order, specify D (Delete) in the Option field to the left of the job order and press <ENTER>. CONTROL-M only allows deletion of WAIT SCHEDULE jobs, or jobs that have finished executing. A job order must be in HELD status to be deleted. The deletion request is recorded in the IOA Log file. The job is logically deleted (i.e., flagged as deleted) from the Active Jobs file immediately. It is physically deleted (from the disk) the next time cleanup (e.g., New Day processing) is performed. (Logically deleted jobs can be undeleted via option U (Undelete). These are added back to the Active Jobs file with the same status they had prior to deletion.) Notes
Critical path jobs (even in HELD status) which hold a Control or Quantitative
resource can only be deleted via the following steps: 1. Remove the critical path priority of the job via the ZOOM screen (Screen 3.Z). 2. Free the job. 3. When the job reverts to WAIT SCHEDULE status, hold the job. 4. Delete the job.
Group Entities cannot currently be manually deleted from the Active Jobs file. If all
jobs in a group are deleted or ended, they are deleted in the next run of the CONTROL-M New Day procedure. However, the Group Entity will remain in the Active Jobs file until the following run of the CONTROL-M New Day procedure.
2 88
Online Facility: Tracking and Control Facility Deleting a Job
Delete Confirmation Window

When requesting job deletions, a Delete Confirmation window may be displayed depending on User profile customization:
By default, when option D is specified in the Status screen, deletion requests are performed without confirmation from the user. If, however, the User profile has been customized accordingly, the following Delete Confirmation window is displayed, in sequence, for each deletion request.
Filter: ------- CONTROL-M Active Environment ------ UP <D> - (3) COMMAND ===> SCROLL ==> CRSR O Name Owner Odate Jobname JobID Typ ------------ Status ------------PRD1 PROD 070798 JOB Wait Schedule (Pipe) IEFBR14T TEST 070798 M70TEST0/24897 JOB Ended "OK" PRD1 PROD 070798 JOB Wait Schedule (Pipe) IEFBR14T +------------------------+ ded "OK" D SELIGRP <--------| Delete (Y/N) | ded- Not "OK" GRPJOB1 +------------------------+ ded "OK" GRPJOB2 TEST 070798 M70TEST2/24929 JOB Ended "OK" GRPJOB3 TEST 070798 M70TEST3/24930 JOB Ended- Not "OK" - Abended ========= >>>>>>>>>>>>> Bottom of Jobs List <<<<<<<<<<<<< ========
Fill in the window as follows and press <ENTER>.
Specify Y (Yes) in the window to confirm the delete request. Specify N (No) in the window to cancel the delete request.
2 89
Online Facility: Tracking and Control Facility Log Screen
Log Screen
To display the Log screen, specify option L (Log) in the Status screen. The Log screen displays all Log messages of the specified job.
FILTER: -- LOG MESSAGES FOR JOB(S) INTR0004 -----------------(3.LOG) COMMAND ===> SCROLL===> CRSR SHOW LIMIT ON ==> DATE 090998 - 090998 DATE TIME ODATE USERID CODE ------ M E S S A G E -------------------090998 131143 090998 M22 JOB511I JOB INTR0004 ODATE 090998 ID=00019 PLACED ON ACTIVE JOBS FILE 090998 131148 090998 M22 SEL203I JOB INTR0004 ELIGIBLE FOR RUN 090998 131150 090998 M22 SUB133I JOB INTR0004 SUBMITTED 090998 131651 090998 M22 SPY281I JOB INTR0004 INTR0004/04371 START 98253.1316 STOP 98253.1316 CPU 0MIN 00.04SEC SRB 0MIN 00.00SEC 0.19 9QFDSF 090998 131651 090998 M22 SPY254I JOB INTR0004 INTR0004/04371 SCANNED 090998 131652 090998 M22 SEL206W JOB INTR0004 INTR0004/04371 ABENDED CC SB37 STEP STEP01 090998 131652 090998 M22 SEL219I JOB INTR0004 INTR0004/04371 ENDED "NOT OK" 090998 132814 090998 M22 CTM659I RERUN OF TASK INTR0004 ODATE 090998 PERFORMED 090998 132817 090998 M22 SEL220I JOB INTR0004 WILL BE RERUN 090998 132818 090998 M22 SEL203I JOB INTR0004 ELIGIBLE FOR RUN 090998 132818 090998 M22 SUB133I JOB INTR0004 SUBMITTED ======== >>>>>>>>>>>>>>>> NO MORE LOG MESSAGES <<<<<<<<<<<<<<<<< ======== CMDS: SHOW, GROUP, CATEGORY, SHPF 13.24.01
Usage of the Log screen is explained in detail in IOA Log Screen later in this section of the manual. However, if you entered the Log screen via option L on the Status screen instead of via option 5 on the IOA Primary Option menu, the following differences in usage should be noted.
The SHOW command cannot be specified with any parameters or qualifiers. Only filter options related to CONTROL-M (and CMEM) are displayed in the Show Screen Filter window. Only the default job filter can be displayed.
If option L (Log) is specified for multiple jobs in the Status screen, the log displays will be stacked. Each time the END key (PF03/PF15) is pressed, the next log in the stack is displayed, until all logs have been displayed. To return to the Status screen, press END (PF03/PF15).
2 90
Online Facility: Tracking and Control Facility Zoom Screen
Zoom Screen
The Zoom screen zooms in on the details of a specific job order. To display the Zoom screen, specify option Z (Zoom) on the Status screen. Note To save changes made in the Zoom screen, the job must be placed in HELD state before entering the Zoom screen.
----------------------------- CONTROL-M ZOOM SCREEN ----------------------(3.Z) COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME PRDKPL01 MEMLIB CTM.PROD.JOBLIB OWNER M44 TASKTYPE JOB PREVENT-NCT2 APPL PROD GROUP KPL OVERLIB JOBNAME JOBID ODATE 090998 ORDERID 0005C MAXWAIT 04 RESTART DECISION-FROM . TO . CONFIRM N DESC DAILY PRODUCTION - START OF PRODUCTION GROUP KPL SET VAR CTB STEP AT NAME TYPE DOCMEM PRDKPL01 DOCLIB CTM.PROD.DOC =========================================================================== IN DAILY-PROD-KPL-GO 0909 CONTROL DB2-MAIN-FILE E RESOURCE INIT 0001 CART 0001 PIPE CTM.WKLD.PIPE TIME: FROM UNTIL PRIORITY 00 CONFIRM N DUE IN 1311 ELAPSE 0003 DUE OUT 1314 CPU-ID NODE NAME NJE SEARCH COUNTER 00000 =========================================================================== OUT PROD-PRDKPL01-OK 0909 + AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP # OF GENERATIONS TO KEEP SYSOUT OP C (C,D,F,N,R) 2 FROM RERUN - MAXRERUN RERUNMEM INTERVAL NEXT TIME STEP RANGE FR (PGM.PROC) . TO . ON PGMST PROCST CODES A/O DO SHOUT WHEN NOTOK TO OPER2 URGN R MS DAILY PRODUCTION JOB PRDKPL01 ENDED NOT OK. NOTIFY PRODUCTION MANAGER SHOUT WHEN TO URGN MS ====== >>>>>>>>>>>>>>>>>>> END OF JOB PARAMETERS <<<<<<<<<<<<<<<<<<<<<<< ===== ENTER SAVE TO UPDATE CHANGES. 18.33.28
Note
The Zoom screen is displayed in Browse mode if the requested job order is already being zoomed by another user. In this case, updates are not permitted.
The Zoom screen is similar to the Job Scheduling Definition screen used for defining job production parameters, but it is different in several respects:
The Zoom screen contains fields which do not appear in the Job Scheduling Definition screen (and vice versa).
2 91
Some fields on the Zoom screen cannot be modified at all. Other fields can or cannot be modified depending on the status of the job. Changes to a field in the Zoom screen affect only the current job order, not the job scheduling definition.
See the Job Scheduling Definition screen (earlier in this section) for information about most fields in the Zoom screen. Fields of the Zoom screen which are not on the Job Scheduling Definition screen are described below: A. JOBNAME B. JOBID C. ODATE D. ORDERID
E. RESTART
Name of the job (available only after job submission). Job number (available only after job submission). Original scheduling date assigned to the job. Unique job order ID in CONTROL-M. FROM TO Program step (and, optionally, procedure step) names at which to begin processing the job restart. Program step (and, optionally, procedure step) names at which the restarted job will terminate processing. The parameter is optional. If the FROM parameter is specified and the TO parameter is not specified, the job is rerun until the last step.
DECISION
CONFIRM Valid values are: Y (Yes) If the job is to be resubmitted as a result of a DO RERUN statement, manual confirmation will be required (via the Status screen). If the job is resubmitted as a result of a DO RERUN statement, manual confirmation is not required.
N (No)
F. DUE IN
Time by which the job must be submitted in order to be completed by the DUE OUT time. This value is calculated by subtracting the ELAPSE time from the DUE OUT time. Anticipated elapse time (i.e., anticipated job execution time). The value used is the average of the jobs runtimes in the CONTROL-M Statistics file. CPUID on which the job will execute (if $ Quantitative resources were specified). This field will contain the selected $ value, i.e., the CPUID. See the description of parameter RESOURCE in Section 3 for more details. Node on which the job executes (as specified in the JCL).
G. ELAPSE
H. CPU-ID
I. NODE NAME
2 92
J. NJE
When this field contains a Y, the job has been sent for execution to a computer which is connected to a CONTROL-M computer via NJE (i.e., it does not have a shared spool with CONTROL-M). Normally, you should not modify the value in this field. However, if a job was purged from the spool (in the NJE computer), you must notify CONTROL-M of the event by changing this field back to blank. After approximately a minute, the job status changes to DISAPPEARED.
K.
SEARCH COUNTER Number of times CONTROL-M has looked for a job which is not found. (This value is displayed (as n) in the job status BUT NOT FOUND n TIMES.) When this value equals the maximum number 18 of searches allowed, the job status changes to DISAPPEARED. You can change the value of this counter. Two instances in which this might be helpful are:
As the counter approaches the maximum number of searches

allowed, set the SEARCH COUNTER back to zero if you do not want the status changed to DISAPPEARED.
If the search is pointless (e.g., you know the job has been deleted
from spool), change the SEARCH COUNTER to 99999 thereby causing a DISAPPEARED status. L. NEXT TIME For rerun situations or for cyclic jobs which use the INTERVAL option, this field indicates the next time the job will be submitted (if other submission criteria are satisfied). ON PGMST indicator. Indicates if the ON PGMST statement was triggered. Possible values: * blank Note ON PGMST statement was triggered. ON PGMST statement was not triggered. If more than one ON PGMST statement has been joined:
M. *
If the statements are joined by an OR relationship, related DO actions were performed if an asterisk appears in this field for any ON PGMST statement. If the statements are joined by an AND relationship, related DO actions were performed only if an asterisk appears in this field for all joined ON PGMST statement.
Only specific dates, or ****, $$$$, or STAT, can be used as valid condition date references. Therefore, if symbolic date references (such as ODAT or PREV) are specified as condition date references (in the IN, OUT, CODES, COND etc. parameters) in the job scheduling definition, the real date values are derived and displayed in the Zoom screen.
18
The default value is 10. This value can be changed by your IOA administrator, (via optional wish WM1754).
2 93
The restart decision (FROM, TO, CONFIRM) parameters contain a value other than blank only if the DO IFRERUN parameters have been specified in the Job Scheduling Definition screen (Screen 2), and only if the job was executed. When and if the job is restarted, these parameters will be used. The user can modify the value of these parameters. The DOC command can be used to alternately display/hide the documentation (DOC lines). Documentation cannot be updated in the Zoom screen.
Zoom Screen for Group Entities

An example of the Zoom screen for Group Entities is shown below. All information applicable to the regular Zoom screen applies to the Group Entity Zoom screen as well. All fields in the Group Entity Zoom screen also appear in the Zoom screen for regular job scheduling definitions. For a description of the fields in the Group Entity Zoom screen, refer to the descriptions of the regular Zoom screen, the Job Scheduling Definition screen, and the Group Entity screen.
----------------------------- CONTROL-M ZOOM SCREEN ----------------------(3.Z) COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ OWNER N04A TASKTYPE GRP APPL GROUP ACCCOUNTING JOBNAME JOBID ODATE 090998 ORDERID 000IH MAXWAIT 00 DESC SET VAR DOCMEM ACCOUNT DOCLIB CTM.CMEM.DOC =========================================================================== IN TIME: FROM UNTIL PRIORITY CONFIRM N DUE IN 1311 ELAPSE 0003 DUE OUT 1314 =========================================================================== OUT ON GROUP-END OK DO COND ACCOUNTING-OK 0909 + SHOUT WHEN TO URGN MS ====== >>>>>>>>>>>>>>>>>>> END OF JOB PARAMETERS <<<<<<<<<<<<<<<<<<<<<<< =====
ENTER SAVE
TO UPDATE CHANGES.
11.41.46
2 94
Exiting the Zoom Screen

The method of exiting the Zoom screen and saving changes is customizable via the User profile.
By default, END (PF03/PF15) performs a cancel, and the changes are not saved (i.e., no changes are made to the job entry on the Active Jobs file). To save changes, the SAVE command must be specified. If customized, END (PF03/PF15) performs a save. In this case, the following Confirmation window is displayed if changes have been made.
----------------------------- CONTROL-M ZOOM SCREEN ----------------------(3.Z) COMMAND ===> +---------------------------------------+ SCROLL===> CRSR +------------------ | | ---------------+ MEMNAME BACKP02 | CONFIRM CHANGES ==> (Y/N) | OWNER M44 | | APPL APPL-L +---------------------------------------+ L OVERLIB CTM.OVER. JOBNAME JOBID ODATE 090998 ORDERID 0007N MAXWAIT 04 RESTART DECISION-FROM . TO . CONFIRM N DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L SET VAR CTB STEP AT NAME TYPE DOCMEM BACKP02 DOCLIB CTM.PROD.DOC =========================================================================== IN START-DAILY-BACKUP 0909 CONTROL RESOURCE INIT 0001 CART 0001 PIPE TIME: FROM UNTIL PRIORITY 00 CONFIRM N DUE IN 1311 ELAPSE 0003 DUE OUT 1314 CPU-ID NODE NAME NJE SEARCH COUNTER 00000 =========================================================================== OUT BACKPL02-ENDED-OK 0909 + ENTER CANCEL TO IGNORE CHANGES. 18.54.43
Fill in the fields of the window as follows and press <ENTER>:
Specify Y (Yes) in the window to save the changes. Specify N (No) in the window to cancel the changes.
To bypass the window if it is normally displayed, exit the Zoom screen as follows: Specify SAVE in the Zoom screen to save changes (not available in Browse mode). Specify CANCEL in the Zoom screen to cancel changes.
Upon saving changes, the status of the job becomes REQUESTED CHANGE HELD. Wait until the REQUESTED CHANGE status disappears (indicating that the CONTROL-M monitor has accepted the change), and then free the job in the Status screen.
2 95
Online Facility: Tracking and Control Facility Confirm Scheduling Window
Confirm Scheduling Window

If a job scheduling definition contains a value of Y in runtime scheduling parameter CONFIRM, the job requires manual confirmation before it can be considered for submission. When such a job is placed in the Active Jobs file, it appears in the Status screen with status of WAIT CONFIRMATION. To confirm the scheduling of the job for submission, specify option C (Confirm) for the job, in the Status screen. A confirmation window is then opened. The same confirmation window is opened when requesting the rerun of a job in the Status screen. For the description and an example of the confirmation window, see Confirm Rerun Window below.
Confirm Rerun Window

If a job scheduling definition does not contain an appropriate DO RERUN statement, or if the specified MAXRERUN limit was reached, a job will not be automatically rerun if the job execution fails. In such cases, however, rerun of the job can be manually requested by specifying option R (Rerun) in the Status screen. The following confirmation window is opened when either option R (Rerun) or option C (Confirm) is specified in the Status screen. Note If CONTROL-R is available, a different window is opened for job rerun. See Rerun/Restart Window (Under CONTROL-R) later in this section.
Filter: ------- CONTROL-M Active Environment ------ DOWN <D> - (3) COMMAND ===> SCROLL ==> CRSR O Name Owner Odate Jobname JobID Typ ------------ Status ------------PRD71 PROD 070798 JOB Held Wait Schedule PRD453 PROD 070798 JOB Held Wait Schedule PRD44 PROD 070798 JOB Held Wait Schedule PRD85 PROD 070798 JOB Held Wait Schedule PRD72 PROD 070798 JOB Held Wait Schedule DAILYPRD PRODMNGR 070798 JOB Wait Schedule DAILYSYS SYSTEM 070798 JOB Wait Schedule CTMLDNRS PRODMNGR 070798 JOB Wait Schedule CTMCLRES +------------------------+ it Schedule C SELIGRP <--------| Confirm (Y/N) | ded- Not "OK" GRPJOB3 +------------------------+ ded- Not "OK" - Abended DAILYPRD PRODMNGR 070798 JOB Wait Schedule DAILYSYS SYSTEM 070798 JOB Wait Schedule CTMLDNRS PRODMNGR 070798 JOB Wait Schedule CTMCLRES PRODMNGR 070798 JOB Wait Schedule TST3 TEST 070798 JOB Ended "OK" TST3 TEST 070798 JOB Ended "OK" TST1 TEST 070798 JOB Requested Rerun Ended "OK" (Run 2) Opt: ? Why L Log H Hold Z Zoom R Rerun A Activate O Force OK V View Sysout N Net D Del F Free S Stat G Group U Undelete J JCL Edit C Confirm 12.17.59
2 96
Online Facility: Tracking and Control Facility Confirm Restart Window (Under CONTROL-R)
Fill in the window as follows and press <ENTER>: CONFIRM Confirm the job. Valid values are: Y (Yes) Submission or rerun of the job is requested. The status of the job is changed to WAIT SCHEDULE, and the job is eligible for submission by CONTROL-M once all other runtime criteria are satisfied. No action is taken. The status of the job remains unchanged and the job is not submitted.
N (No)
Confirm Restart Window (Under CONTROL-R)

When CONTROL-R is available, and the job scheduling definition of a job whose execution fails contains a DO IFRERUN statement, the job can be restarted. Manual intervention is required for the job restart if the job appears in the Status screen with a status of WAIT CONFIRMATION (WITH RESTART). For a job requiring restart, this status appears when all three of the following conditions exist:
A DO RERUN statement is defined following the DO IFRERUN statement, indicating that the job should be scheduled for restart/rerun. The CONFIRM field in the DO IFRERUN statement contains a value of Y (Yes), indicating that confirmation is required before the job is restarted. A MAXRERUN value greater than zero is defined in the job scheduling definition, but the number of reruns specified in this field has not yet been performed. In this case, restart can be confirmed by specifying option C (Confirm) for the job.
To confirm restart/rerun for such a job, specify option C (Confirm) for the job. A restart confirmation window is then opened. The same confirmation window is opened when requesting the rerun (option R) of a restart job in the Status screen. For the description and an example of the confirmation window, see Rerun/Restart Window (Under CONTROL-R) below.
Rerun/Restart Window (Under CONTROL-R)

When CONTROL-R is available, and the job scheduling definition of a job whose execution fails contains a DO IFRERUN statement, the job can be restarted. Manual intervention is required for the job restart in the following cases:
No DO RERUN statement is defined following the DO IFRERUN statement in the job scheduling definition. In this case, the job appears in the Status screen with a failed job status. The CONFIRM field of the DO IFRERUN statement contains a value of Y (Yes). In this case, job appears in the Status screen with a failed job status. No maximum number of reruns is defined in field MAXRERUN, or the maximum number reruns defined in field MAXRERUN has been performed. In this case, the job appears in the Status screen with a status of ENDED NOT OK RERUN NEEDED.
To manually request rerun/restart for such a job, specify option R (Rerun) for the job.
2 97
Online Facility: Tracking and Control Facility Rerun/Restart Window (Under CONTROL-R)
The following confirmation window is opened when either option R (Rerun) or option C (Confirm) is specified in the Status screen for a job requiring rerun/restart under CONTROL-R.
Filter: ------- CONTROL-M Active Environment ------ DOWN <D> - (3) COMMAND ===> SCROLL ==> CRSR O Name Owner Odate Jobname JobID Typ ------------ Status ------------SALEGRP ACTG 070798 GRP Ended- Not "OK" R GRPJOB3 ACTG 070798 +---------------------------------(3.R)+ ed DAILYPRD PRODMNGR 070798 | Job GRPJOB3 Is to be Rerun | DAILYSYS SYSTEM 070798 | Please Confirm (Y/N) | CTMLDNRS PRODMNGR 070798 | With Restart Y (?/Y/N) | CTMCLRES PRODMNGR 070798 | ---------------------------------- | PRD3 PROD 070798 | From Step/Proc . | PRD3 PROD 070798 | To Step/Proc . | PRD1 PROD 070798 | Recapture Abend Codes (Y/N) | OK" | Recapture Cond Codes (Y/N) | | Step Adjustment (Y/N) | PRD2 PROD 070798 | Restart Parm Member Name GRPJOB3 | OK" +--------------------------------------+ Prior Run: Ended "OK" PRD3 PROD 070798 JOB Requested Rerun Ended "OK" (Run 2) Prior Run: Ended "OK" IEFBR14 TEST 070798 N91NOP /26911 JOB Ended "OK" IEFBR14 TEST 070798 N91NOP /26923 JOB Ended "OK" Opt: ? Why L Log H Hold Z Zoom R Rerun A Activate O Force OK V View Sysout N Net D Del F Free S Stat G Group U Undelete J JCL Edit C Confirm 12.03.10
Fill in the fields of the window as follows, and press <ENTER>: Confirm Valid values are: Y (Yes) Job rerun is requested. The job is returned for possible resubmission by CONTROL-M (provided that all runtime conditions are met). The status of the job is changed according to the value of the With Restart field. No action is taken. The job is not rerun. The status of the job remains unchanged.
N (No) With Restart
This field is applicable only if Y is specified for Confirm. (If N is specified for Confirm, this field is ignored.) Valid values are: Y (Yes) When the job is rerun, it is restarted using the CONTROL-R Restart facilities. The status of the job is changed to WAIT SCHEDULE (WITH RESTART). The CONTROL-R Restart facilities are not used. The status of the job is changed to WAIT SCHEDULE. The Restart Step List window, which contains a list of the jobs steps, is opened. See Step List Window below.
N (No) ?
2 98
From Step/Proc To Step/Proc
The pgmstep (and optionally procstep) names at which the restart of the job is to be attempted. The pgmstep (and optionally procstep) names at which the restarted job will terminate processing. Optional. The From Step/Proc and To Step/Proc fields display from/to step values specified in statement DO IFRERUN. These values can be modified. If a From Step/Proc value is specified, and the To Step/Proc field is blank, the job is rerun up to and including the last step.
Note
To display a list of job steps from which a From Step/Proc and/or To Step/Proc value can be selected, specify a ? symbol in the With Restart field and press <ENTER>. The Step List window, described below, is opened.
Recapture Abend Codes Whether or not abend code recapture should be enabled. This field is applicable only if Y is specified for WITH RESTART. (If N is specified for WITH RESTART, this field is ignored.) Valid values: Y (Yes) N (No) blank Automatic abend code recapture is performed. Abend code recapture is prevented. The job member or the $DEFAULT member in the RESTPARM library is used. If member $DEFAULT is not found, the CONTROL-R default is used to perform the recapture.
Recapture Cond Codes This field is applicable only if Y is specified for With Restart. (If N is specified for With Restart, this field is ignored.) Valid values are: Y (Yes) N (No) blank Automatic condition code recapture is performed. Condition code recapture is prevented. The job member or the $DEFAULT member in the RESTPARM library is used. If member $DEFAULT is not found, the CONTROL-R default is used to perform the recapture.
Step Adjustment This field is applicable only if Y is specified for With Restart. (If N is specified for With Restart, this field is ignored.) Valid values are: Y (Yes) N (No) blank Automatic step adjustment is performed. Step adjustment is prevented. The job member or the $DEFAULT member in the RESTPARM library is used. If member $DEFAULT is not found, the CONTROL-R default is used to perform the recapture.
2 99
Note
Values specified for Recapture Abend Codes, Recapture Cond Codes and Step Adjustment override all other parameter specifications and the default. They apply to the current restart only.
Restart Parm Member Name Name of the member which contains control parameters for the job restart. The specified value must be a valid member name of 1-8 characters. The default value, displayed in the window, is the member which contains the jobs JCL (i.e., the value in the MEMNAME field of the Zoom screen or the Name field of the Status screen). The following points should be noted about From Step/Proc and To Step/Proc values:
Pgmstep name can be any specific program step name or $FIRST. $FIRST resolves to the first step of the job if procstep name is blank. Otherwise, $FIRST resolves to the first step in the procedure identified by procstep. $ABEND and $EXERR are not recognized by CONTROL-R and should not be specified as restart steps in this window. ($ABEND and $EXERR are valid only in job scheduling definitions.) If specifying a procstep name when there are nested procedures, specify the procstep name of the innermost procedure in which the program is included. Entering $FIRST in the first From Step/Proc field followed by $CLEANUP in the adjacent (second) From Step/Proc field will rerun the job for Cleanup (i.e., run the CONTROL-R cleanup step and flush the job). All other parameters entered in the Restart window will be ignored. AutoEdit resolution is performed at time of cleanup job submission. For example, if a job with AutoEdit date variable %%DATE is submitted for cleanup the day after the original run, the resolution of the variable during cleanup will vary from that of the original run.
Note
The RERUN request and, in CONTROL-R, the RESTART decision are recorded in the IOA Log file. If the CONTROL-M monitor is active, the RERUN request is accepted after a few seconds.
2 100
Online Facility: Tracking and Control Facility Step List Window
Step List Window

A list of the job steps from the previous job run, with the completion codes of each step, can be displayed from the Restart window in the Status screen. Steps from this list can then be selected as From Step/Proc and/or To Step/Proc values in the Restart window. To display the list of job steps, specify a ? symbol in the With Restart field of the Restart window, and press <ENTER>. The Step List window, below, is opened. This window within a window contains the list of job steps.
Filter: ------- CONTROL-M Active Environment ------ UP <D> - (3) COMMAND ===> SCROLL ==> CRSR O Name Owner Odate Jobname JobID Typ ------------ Status ------------PRD71 PROD 070798 JOB Held Wait Schedule PRD453 PROD 070798 +---------------------------------(3.R)+ PRD44 PROD 070798 | Job GRPJOB3 Is to be Rerun | PRD85 PROD 070798 | Please Confirm (Y/N) | PRD72 PROD 070798 | +----------- CONTROL-R Step List ------------+ SELIGRP M70 070798 | | Command ==> | R GRPJOB3 M70 070798 | | O Num Pgm-stp Proc-stp Pgm= Comp | TST1 TEST 070798 | | 001 STEP1 IEBGENER C0000 | TST2 TEST 070798 | | 002 STEP2 XYZA7891 S806 | TST3 TEST 070798 | | | DAILYPRD PRODMNGR 070798 | | | DAILYSYS SYSTEM 070798 | | | CTMLDNRS PRODMNGR 070798 +- | | CTMCLRES PRODMNGR 070798 | | IEFBR14 PROD 070798 N9 | | IEFBR14 PROD 070798 N9 | | IEFBR14 PROD 070798 N2 | | IEFBR14 PROD 070798 | Opt: F From T To O Only | ========= >>>>>>>>>>>>> +--------------------------------------------+ = Opt: ? Why L Log H Hold Z Zoom R Rerun A Activate O Force OK V View Sysout N Net D Del F Free S Stat G Group U Undelete J JCL Edit C Confirm 12.43.09
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) in the Step List window. To locate a specific step, specify the LOCATE command in the Command field of the CONTROL-R Stop List window and press <ENTER>. Format of the command is:
LOCATE stepname
Steps selected in the Step List window will appear in the appropriate field of the Restart window. To select steps, specify the appropriate selection value(s) in the Option (O) field by the step name(s). Valid selection values are: F (From) T (To) O (Only) Restart should begin at the indicated step. The indicated step becomes the From Step/Proc parameter. Restart should end at the indicated step. The indicated step becomes the To Whom It May Concern: Step/Proc parameter. Restart should begin and end at the indicated step. The indicated step becomes the From Step/Proc and To Step/Proc parameter. This value cannot be specified with an F or a T value.
2 101
Online Facility: Tracking and Control Facility Job Order Execution History Screen
Note
If a step cannot be used as a From Step/Proc and/or To Step/Proc for restart, the Option field is protected, and an option cannot be specified, for that step.
Pressing the END key (PF03/PF15) closes the Step List window and automatically updates the From Step/Proc / To Step/Proc fields of the Restart window with the appropriate steps. Specifying command RESET, or pressing the RESET key (PF04), closes the Step List window without updating the Restart window.
Job Order Execution History Screen

The Job Order Execution History screen is displayed when option V (View Sysout) is entered on the Status screen. The Job Order Execution History screen lists all runs of the job and displays relevant execution information for each run. This option is used for jobs which have executed at least once and whose SYSDATA has been automatically archived by the CONTROL-M monitor as part of CONTROL-R 19 processing (Auto-Archive = Y).
------------------------ JOB ORDER EXECUTION HISTORY ---------------------(3.V) COMMAND ===> SCROLL===> CRSR MEMNAME MSGCMPR OWNER M05A ORDERID 00051 ODATE 090998 O JOBNAME JOBID DATE START ELAPSED PAGES MAX RC ---------- STATUS ---------PRDYLLM 01318 090998 21:40 1.46 00007 S222 ENDED- NOT "OK" - ABENDED PRDYLLM 01425 090998 21:56 1.21 00014 C0008 ENDED- NOT "OK" DUE TO CC PRDYLLM 01447 090998 22:01 1.50 00014 C0000 ENDED- OK ======= >>>>>>>>>>> BOTTOM OF ACTIVE JOB ORDER HISTORY LIST <<<<<<<<<<< =======
OPTION:
S SELECT
11.41.04
19
The V option does not support the viewing of output on the spool or output which has been archived by a CONTROL-M SYSOUT F function.
2 102
Online Facility: Tracking and Control Facility Job Order Execution History Screen
By default, older data are displayed before more recent data (i.e., in FIFO order first in/first out), so that the first run of the job is shown first. If, however, the User profile has been customized accordingly, data is displayed in LIFO order (last in/first out). The Job Order Execution History screen is preconfigured to the D (Default) display type. Additional display types can be defined by the IOA administrator. To display a different display type on the screen, specify command DISPLAY x (abbreviated DI x) where x is the identifying letter of the display type (e.g., DI D). To return to the Status screen, press the END key (PF03/PF15).
Format of the Job Order Execution History Screen

The following information about the job is displayed in the Default display type of the Job Order Execution History screen. MEMNAME OWNER ORDERID ODATE Name of the member containing the jobs JCL. User ID of the owner of the job. Job order ID. Original scheduling date of the job.
For each execution of the job, the following information is displayed:
O JOBNAME JOBID DATE START ELAPSED PAGES MAX RC STATUS
Option field. Job name. JES job number. Execution date of the job. Start time of the job execution (format hh:mm). Total elapsed time of the job execution (format mmmm.nn where mmmm is minutes, and nn is hundredths of minutes). Number of pages in the sysout. Highest return code of the job execution. Status assigned to the job by CONTROL-M, based on execution results.
Displaying Job Sysout

Job execution sysout, which is displayed in the Sysout Viewing screen, can be requested from the Job Order Execution History screen in the following ways:
To display job sysout for specific executions of the job, specify option S (Select) in the OPTION field of the selected executions and press <ENTER>. To display job sysout for all executions of the job, specify command VIEWALL (abbreviated V) in the COMMAND field and press <ENTER>.
2 103
Online Facility: Tracking and Control Facility Sysout Viewing Screen
Sysout Viewing Screen

The Sysout Viewing screen is displayed when option S (Select) is specified for specific job executions, or when command VIEWALL is specified, in the Job Order Execution History screen.
------------- CONTROL-M/CONTROL-R SYSOUT VIEWING -------- PAGE 1 OF 2 COMMAND ===> SCROLL===> CRSR MEMNAME PRDKPL01 OWNER M22 JOBNAME PRDKPL01 ODATE 090998 ---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8 J E S 2 J O B L O G -- S Y S T E M F D S F -- N O 18.31.20 JOB 8666 $HASP373 PRDKPL01 STARTED - INIT 1 - CLASS A - SYS FDSF 18.31.20 JOB 8666 IEF403I PRDKPL01 - STARTED - TIME=18.31.20 18.35.21 JOB 8666 PRDKPL01.STEP01 .#01; - COMPLETION CODE=0000 18.39.22 JOB 8666 PRDKPL01.STEP01A .#02; - COMPLETION CODE=0000 18.42.22 JOB 8666 PRDKPL01.STEP02 .#03; - COMPLETION CODE=0000 18.50.23 JOB 8666 PRDKPL01.STEP03 .#04; - COMPLETION CODE=0000 18.51.25 JOB 8666 IEF450I PRDKPL01 STEP04 - ABEND S0C4 U0000 - TIME=18.51.25 18.51.25 JOB 8666 PRDKPL01.STEP04 .#05; - COMPLETION CODE=S00C4 - ABENDED#### 18.51.25 JOB 8666 PRDKPL01.STEP05 .#06; - COMPLETION CODE=NOT RUN 18.51.25 JOB 8666 PRDKPL01.STEP06 .#07; - COMPLETION CODE=NOT RUN 18.51.25 JOB 8666 PRDKPL01.STEP07 .#08; - COMPLETION CODE=NOT RUN 18.51.26 JOB 8666 PRDKPL01.STEP08 .#09; - COMPLETION CODE=NOT RUN 18.51.26 JOB 8666 PRDKPL01.STEP09 .#10; - COMPLETION CODE=NOT RUN 18.51.26 JOB 8666 PRDKPL01.STEP10 .#11; - COMPLETION CODE=NOT RUN 18.51.26 JOB 8666 IEF404I PRDKPL01 - ENDED - TIME=18.51.26 18.51.26 JOB 8666 $HASP395 PRDKPL01 ENDED ------ JES2 JOB STATISTICS -----COMMANDS: LEFT, RIGHT, FIND str, FIND str PREV, N n, P n, END 18.56.48
Job orders are displayed in the same order (LIFO/FIFO) in this screen as in the Job Order Execution History screen. To return to the Job Order Execution History screen, press END (PF03/PF15). The following commands are supported: LEFT RIGHT FIND str Shift display to the left.
20
Shift display to the right. Find next occurrence of the string.
FIND str PREV Find previous occurrence of the string. NEXT n PREV n END Scroll forward n number of print pages (can be abbreviated N n). Scroll backward n number of print pages (can be abbreviated P n). Exit the screen.
For color terminals, display colors for the sysout are defined in the User profile. See your IOA administrator if you want to change the default colors.
20
Terminals with 132-character lines display the entire data line. Therefore, LEFT and RIGHT do not affect the display on those terminals.
2 104
Online Facility: Tracking and Control Facility Statistics Screen
Statistics Screen
Either of the following two methods can be used to display the Statistics screen:
Specify the S (STAT) option for any job appearing in the Status screen. Specify command JOBSTAT (described later in this section) in the COMMAND field in the Status screen. Command JOBSTAT can be specified for any job which has statistics, even if the job is not currently in the Active environment.
The Statistics screen shows the most current run statistics for the job. Job statistics are collected for executions which ended OK. A separate set of statistics is collected for each group on each computer in which the job is run. Statistics for a job are retained for a maximum of 20 executions (which ended OK) in each group on each computer.
----------------------------- PLUPDT02 STATISTICS ------------------------(3.S) COMMAND ===> SCROLL===> CRSR JOBID START TIME END TIME ELAPSED CPU SRB USER DATA AVERAGE: SYSID: 1 SMFID: SYS1 27.40 1:16.91 0:20.53 0239 01/02 20:19 01/02 20:45 26.14 0:58.08 0:19.39 0643 02/02 17:56 02/02 18:24 28.42 1:05.18 0:21.08 0399 03/02 20:35 03/02 21:01 26.17 0:58.46 0:19.41 2141 06/02 17:59 06/02 18:25 26.53 0:59.32 0:20.08 0493 07/02 17:40 07/02 18:08 28.40 1:03.44 0:21.07 0619 07/02 20:07 07/02 20:35 28.19 1:03.03 0:21.41 0888 08/02 23:11 08/02 23:39 28.22 1:04.43 0:21.43 1723 09/02 17:52 09/02 18:19 27.56 1:01.59 0:20.44 AVERAGE: SYSID: 2 0248 03/02 17:41 2924 04/02 18:02 0557 05/02 17:44 0591 05/02 20:16 2366 06/02 20:28 2004 09/02 17:49 2889 10/02 19:49 2914 10/02 22:21 SMFID: SYS2 03/02 18:05 04/02 18:28 05/02 18:11 05/02 20:41 06/02 20:52 09/02 18:14 10/02 20:15 10/02 22:48 25.54 24.38 26.20 27.44 25.22 24.07 25.33 26.16 27.14 0:58.22 0:54.46 0:58.55 1:01.32 0:56.34 0:53.17 0:56.32 0:59.35 1:06.30 0:19.20 0:18.08 0:19.44 0:20.36 0:19.11 0:18.25 0:19.19 0:19.10 0:20.13 12.31.15
PRESS END PFK TO RETURN TO STATUS SCREEN
To return to the Status screen, press the END key (PF03/PF15). Notes The IOA administrator determines if statistics are collected at a site. Update of the Statistics file is performed by utility CTMJSA, which should be scheduled periodically. Utility CTMJSA is described in the IOA Administrator Guide. If statistics which exist for a job are not displayed, refresh the display by entering the REFRESH command (PF04/0F16).
2 105
Fields of the Statistics Screen

For each computer with statistics on the job, an Average Statistics line (A) is displayed followed by Individual or Group Entity statistics (B) for each execution. Individual and Group Entity statistics are listed in FIFO order (first in/first out) by date and time the job ended. Average Statistics Line The Average Statistics Line contains the SYSID and SMF ID of the computer for which statistics are calculated, as well as the average ELAPSED, CPU and SRB time for the job on that computer. Individual Execution Statistics JOBID START TIME Job number under JES. Date/time the job began executing. Date format: mmdd or ddmm depending on site standard. Time format: hh:mm (where hh=hours and mm=minutes). Date/time the job finished executing. Same format as START TIME. Elapsed run time. Format: mmmm:nn (where mmmm is minutes and nn is hundredths of minutes). CPU time used. Format mmmm:ss.nn (where mmmm is minutes, ss is seconds and nn is hundredths of seconds). SRB (System Request Block) time used. Format: mmmm:ss.nn (where mmmm is minutes, ss is seconds and nn is hundredths of seconds). Optionally supplied data from the user data area in the CONTROL-M Statistics file (edited by user exit CTMX013).
END TIME ELAPSED CPU SRB USER DATA
Group Entity Execution Statistics Fields of the Group Entity Execution statistics have corresponding fields of the Individual Execution statistics. JOBID START TIME Order ID of the group entity. Date/time the group began executing. Date format: mmdd or ddmm depending on site standard. Time format: hh:mm (where hh=hours and mm=minutes). Date/time the group finished executing. Same format as START TIME. Elapsed time from the time the first job in the group began executing until the time the last job in the group finished executing. 0. 0. Blank. different meanings than
END TIME ELAPSED CPU SRB USER DATA
2 106
Tape Device Usage Statistics If optional wish WM2744 has been applied at your site, tape device usage information is accumulated for every CONTROL-M job execution that ended OK. This information is used by the Automatic Tape Adjustment facility to automatically allocate the appropriate number of tape drives for a job at job order time. (This allocated value overrides any specified tape device usage value in the RESOURCE parameter.) This information (shown below) can be displayed by scrolling to the right of the Statistics screen (via PF11/PF23):
JOBID START DEVICES USED AVERAGE: SYS 0239 01/02 TAPE=1;CARTRIDGE=1; 0643 02/02 TAPE=1;CARTRIDGE=1; 0399 03/02 TAPE=1;CARTRIDGE=1; 2141 06/02 TAPE=1;CARTRIDGE=1; 0493 07/02 TAPE=1;CARTRIDGE=1;
The tape usage information consists of fields JOBID and START date (from the Statistics screen) so that tape usage of a specific job execution can be easily identified, and an additional field, DEVICES USED, which is described below. DEVICES USED Tape device types and number of devices of each type that were used by the job. This field has the following format:
devtype1=quant1;devtype2=quant2;...devtypex=quantx;
where: devtype quant A tape device type used by the job. The number of tape devices of the specified type used by the job.
Tape device types are displayed in the order specified by the IOA administrator in member UNITDEF of the CONTROL-M PARM library. If the tape device usage information occupies more than the visible screen, scroll again to the right (via PF11 or PF23) to view additional device usage information. The maximum length of tape device usage data is 255 characters.
JOBSTAT Command
Command JOBSTAT in the Status screen displays the Statistics screen with the statistics for the specified job. Unlike Option S (STAT), which can only be specified for jobs appearing in the Status screen, command JOBSTAT can be specified for any job. Format of the command is:
JOBSTAT jobname groupname
Specification of a group name is optional, but if no group name is specified, statistics are displayed only for jobs not belonging to any group. Type the command in the COMMAND field in the Status screen, and press <ENTER>.
2 107
Online Facility: Tracking and Control Facility Job Dependency Network Screen
Job Dependency Network Screen

The Job Dependency Network screen is displayed when option N (Network) is specified on the Status screen. The Job Dependency Network screen displays all the predecessor and successor jobs (including eventual successors and predecessors) for the selected job. Job dependencies are determined according the prerequisite IN and OUT conditions of the job. (DO COND statements are not used for this purpose because the dependencies they create are conditional rather than constant.) The Job Dependency Network screen is a special case of the Status screen, and therefore contains most of the same features. For example, filters defined in the Status screen are available in the Job Dependency Network screen (and vice versa). Jobs are listed in job flow order (i.e., level) relative to the selected job. The selected job is indicated by level 0. Predecessor jobs are indicated by a minus sign and successor jobs are indicated by a plus sign. The network of jobs is maintained by the CONTROL-M monitor, and is refreshed only by request. (The REFRESH Command is described in Commands of the Job Dependency Network Screen later in this section.) The time of the last network refresh is displayed on the top line of the Job Dependency Network screen. Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) on the Job Dependency Network screen. To return to the Status screen, press the END key (PF03/PF15). Features of the Job Dependency Network screen which have already been described earlier with the Status screen are not described below. Refer to the Status screen for information about those features. However, the following points should be noted:
The RBAL command of the Status screen is not supported in the Job Dependency Network screen. This difference is also reflected in the Primary Bottom lines of the two screens. The N (Network) display type is specifically oriented to the Job Dependency Network screen, and is therefore described below. (It is also available in, but not very relevant to, the Status screen.) For a description of the fields in the D (Default) display type and the A (All Info) display type, refer to the description of the Status screen earlier in this section.
2 108
Format of Job Dependency Network Information

Display Type N (Network) The Network display type is intended for use by the IOA administrator and operations personnel. Basic information is displayed for each job.
Filter: DEFAULT ------- CONTROL-M NETWORK OF BGPCBHK6 ------ UP <N> - (3) COMMAND ===> SCROLL ==> CRSR O Level ----- N a m e ----- DueIN/Out Elaps Late Prio Res ------ Status -----6 JOBPREP1 1206 1209 0003 9 WAIT SCHEDULE -5 CHECKFL1 1209 1212 0003 9 WAIT SCHEDULE -5 JOBPREP2 1212 1215 0003 9 WAIT SCHEDULE -5 CHECKFL2 1215 1218 0003 9 WAIT SCHEDULE -4 CHECKFL3 1218 1221 0003 9 WAIT SCHEDULE -4 LOGLIST 1221 1224 0003 9 WAIT SCHEDULE -4 FLOWCHK 1224 1227 0003 9 WAIT SCHEDULE -3 MAINTST 1227 1230 0003 9 WAIT SCHEDULE -2 SAMP 1230 1233 0003 9 WAIT SCHEDULE -1 FLOWPRT 1233 1236 0003 9 WAIT SCHEDULE --> RGL1 1236 1239 0003 9 WAIT SCHEDULE +1 RGL2 1239 1242 0003 9 WAIT SCHEDULE +2 RGLCHK 1242 1245 0003 9 WAIT SCHEDULE +3 RGL3 1245 1248 0003 9 WAIT SCHEDULE +4 DELCHK 1248 1251 0003 9 WAIT SCHEDULE +5 DELLOG 1251 1254 0003 2 WAIT SCHEDULE +6 DELRUN 1254 1257 0003 2 WAIT SCHEDULE +7 CLEANUP 1257 1300 0003 2 WAIT SCHEDULE ======== >>>>>>>>>>>>> B O T T O M O F R A N G E <<<<<<<<<<<<< ======== Commands: OPt DIsplay Show HIstory REFresh Auto Jobstat SHPF OPt command toggles between Commands and Options display 15.15.48
2 109
A. Filter
B.
Name of the currently active screen filter (see Filtering the Status Screen Display earlier in this section).
CONTROL-M status Indicator of whether the CONTROL-M monitor is UP, DOWN or SUSP (suspended). Display Type Indicator Indicator of the currently used display type (e.g., N for the Network display type).
C.
The following are displayed for each job (D): O(ption) Level Field for requesting options to be activated. Successor/predecessor level relative to the selected job. The current job is indicated by -->. Predecessor jobs are indicated by a minus sign and successor jobs are indicated by a plus sign. Jobs which have several paths to or from the selected job appear with the shortest possible route as their level number. <-Name of the member containing the jobs JCL, or name of the started task. Due in time time by which the job must be submitted. Due out time time by which the job must finish executing. Elapse time. Expected time (in minutes) for the job to execute. Indication that a job is late. Possible values: X Actual execution has not completed within the expected execution time. Also indicates that SHOUT WHEN EXECTIME was issued. Job was not submitted in time. Also indicates that SHOUT WHEN LATESUB was issued. Job is late. Also indicates that SHOUT WHEN LATE was issued.
Name DueIN DueOut Elaps Late
I O Prio Res
CONTROL-M priority of the job. Indicator that the job accesses Quantitative resources. Values are: blank Y Quantitative resources are not accessed. Quantitative resources are accessed.
Status
Job (task) status.
2 110
Commands of the Job Dependency Network Screen

Except for command REFRESH, detailed descriptions of the Job Dependency Network screen commands can be found in Commands of the Status Screen earlier in this section. Command REFRESH is described below in detail because this command is most relevant to the Job Dependency Network screen. REFRESH Command Command REFRESH causes the CONTROL-M monitor to recalculate job dependencies. During the refresh (i.e., from the time the refresh is initiated until the refresh is completed), a special status message is displayed at the top of the screen. Format of the command is:
REFRESH parm
where parm is the type of refresh to be performed. The following parameters can be specified with the REFRESH command: NET Update the list of dependent jobs in the Job Dependency Network screen. As soon as possible, the monitor recalculates logical dependencies for all job orders currently present in the Active Jobs file and updates the Job Dependency Network screen. Default. Adjust DUE OUT times (if necessary) for all job orders in the Active Jobs file which are not Held. For an explanation of the method used to recalculate DUE OUT time, see Job Flow Adjustment in Section 1. Check and adjust the priority of predecessor jobs. For more information, see Job Flow Adjustment in Section 1. Activates the processes described above (NET, DEADLINE PROPAGATE) simultaneously in the CONTROL-M monitor. and
DEADLINE
PROPAGATE ALL
2 111
Online Facility: Tracking and Control Facility History Environment Screen
History Environment Screen

If CONTROL-R is installed, jobs can be automatically moved from the Active Jobs file to the History Jobs file during the subsequent New Day processing. Jobs in the History Jobs file can be displayed in the History Environment screen. The History Environment screen is a special case of the Status screen. It is displayed when command HISTORY is specified in the Command field in the Status screen.
Filter: DEFAULT ------- CONTROL-M History Environment ------ DOWN - (3) COMMAND ===> SCROLL ==> CRSR O Name Owner Odate Jobname JobID Typ ------------ Status ------------DAILYSYS SYSTEM 070798 JOB Wait Schedule CTMLDNRS PRODMNGR 070798 JOB Wait Schedule CTMCLRES PRODMNGR 070798 JOB Wait Schedule GEN1 PRODMNGR 070798 PRDGEN1 /17048 JOB Ended "OK" GEN2 PRODMNGR 070798 PRDGEN2 /17049 JOB Ended "OK" GEN3 PRODMNGR 070798 PRDGEN3 /17050 JOB Ended "OK" GEN4 PRODMNGR 070798 PRDGEN4 /17051 JOB Ended "OK" GEN5 PRODMNGR 070798 PRDGEN5 /17053 JOB Ended "OK" TPCICS47 TP05 070798 TPCICS47/18081 JOB Ended "OK" TPCICS12 TP01 070798 TPCICS12/18082 JOB Ended "OK" GEN1 PRODMNGR 070798 PRDGEN1 /18084 JOB Ended "OK" GEN2 PRODMNGR 070798 PRDGEN2 /18085 JOB Ended "OK" TPCICS05 TP05 070798 TPCICS05/18090 JOB Ended "OK" Y01ACCB ACCT 070798 Y01ACCB /19053 JOB Ended "OK" Y01ACCC ACCT 070798 Y01ACCB /19150 JOB Ended "OK" Y01ACCD ACCT 070798 Y01ACCB /19230 JOB Ended "OK" Y01ACCE ACCT 070798 Y01ACCB /19232 JOB Ended "OK" Y01ACCF ACCT 070798 Y01ACCB /19233 JOB Ended "OK" Y01ACCG ACCT 070798 Y01ACCB /19501 JOB Ended "OK" Commands: OPt DIsplay Show HIstory RBal REFresh Auto Jobstat SHPF OPt command toggles between Commands and Options display 14.55.34
Because the History Environment screen is a special case of the Status screen, the features of the two screens are almost identical, and are described earlier in this section under the Status screen. Differences between the screens are noted below:
The selection of line options available in the History Environment screen is different than the selection of line options available in the Status screen. Below are the Alternate Bottom lines of the History Environment screen.
Opt: L Log Z Zoom S Stat R Restore J JCL Edit V View Sysout OPt command toggles between Commands and Options display
18.24.15
Note
Option R (Rerun/Restart in the Status screen) becomes the Restore option in the History Environment screen.
Upon exiting the History Environment screen (by pressing PF03/PF15), the Status screen is displayed.
2 112
Online Facility: Tracking and Control Facility Force OK Confirmation Window
Options of the History Environment Screen

Except for option R (Restore), all options available in the History Environment screen are described in Options of the Status Screen earlier in this section. The Restore option, which is available only in the History Environment screen, is described below. R RESTORE Restore the specified job to the Active Jobs file and mark it as deleted in the History Jobs file.
Force OK Confirmation Window

To change the status of a job to ENDED OK, specify option O (Force OK) in the option field to the left of the job order and press <ENTER>. Status changes are performed as follows:
If the job status is WAIT SCHEDULE, the status is changed to ENDED OK without submitting the job. As a result, all resources required by the job will be freed, and all job post-processing will be performed as if the job terminated with status ENDED OK. If the job terminated with status ENDED NOT OK or NOT SUBMITTED, the status is changed to ENDED OK and all post processing is performed as if the job terminated with status ENDED OK. If CONFIRM=Y was specified in the DO IFRERUN parameter in the job scheduling definition, and the user wishes to implement a Force OK request, the user must specify C (Confirmation) and respond with CONFIRM=Y in the restart confirmation window. This will not cause the job to restart, but will instead implement the Force OK request.
Note
Force OK does not work for cyclic jobs. A Force OK request is not performed if the job is currently being executed or rerun. When requesting FORCE OK, the Force OK Confirmation window is displayed (unless the User profile has been modified to suppress the window).
2 113
Online Facility: Tracking and Control Facility Force OK Confirmation Window
Filter: ------- CONTROL-M Active Environment ------ UP <D> - (3) COMMAND ===> SCROLL ==> CRSR O Name Owner Odate Jobname JobID Typ ------------ Status ------------PRFUPRT P15 090998 PRFUPRT /04587 JOB ENDED "OK" PRDKPL02 +------------------------+ DED "OK" PRDKPL03 | | IT SCHEDULE O M44TEST <--------| Force OK (Y/N) | LD WAIT SCHEDULE PRLMBCK | | IT SCHEDULE ====== >>> +------------------------+ S LIST <<<<<<<<<<<<<<<<<< =====
Fill in the window as follows and press <ENTER>.
Specify Y (Yes) in the window to confirm the force OK request. Specify N (No) in the window to cancel the force OK request.
2 114
Online Facility: CMEM Rule Definition Facility General
CMEM Rule Definition Facility

General
The CONTROL-M Event Manager (CMEM) Rule Definition facility enables you to create/view/modify CMEM rules for the handling of events in your environment. A CMEM rule consists of parameters which correspond to the decisions and actions to be taken when handling the occurrence of specified external events. A CMEM rule for a specific situation needs to be defined only once. Once defined, the rule is saved and used as necessary for managing events. CMEM rules can be modified or deleted as required. CMEM rules are stored in members called rule tables. In many environments, several rules can work together as a group to handle a specific situation. In these cases, it is common to define all such related rules in a single rule table. Any number of rule tables can be defined, and each rule table can contain any number of CMEM rules. CMEM rule tables (members) are stored in rule libraries (partitioned datasets). You can define any number of rule libraries. Notes The number of rule tables in a library, the number of rules in a rule table, and the size of each rule definition, are all calculated dynamically and are not dependent on parameter specifications. The CMEM Rule Definition facility does not support members which have been compressed using the ISPF PACK option.
Accessing the CMEM Rule Facility

The CMEM Rule Definition facility contains the following screens:
CMEM Rule entry panel Table List screen Rule List screen Rule Definition screen
Allows specification of parameters which determine which screen will be displayed. Displays the list of tables (members) in the specified CMEM rule library. Displays the list of rules in the selected table. Displays the parameters of the selected CMEM rule. This is the main screen of the facility.
To enter the CMEM Rule facility, select option C on the IOA Primary Option menu. The CMEM Rule entry panel is displayed.
2 115
Online Facility: CMEM Rule Definition Facility General
Creating Tables
CMEM rule tables can be created in one of the following ways: 1. By specifying the new table name in the entry panel and pressing <ENTER>. (The name of a new rule for the new table can also be specified.) Upon using this method to request that a table be created, a skeletal CMEM rule (i.e., one with most fields not filled in) is displayed in the CMEM Rule Definition screen. This rule definition should be filled in and saved. The table will be created and the rule will be the first and only rule in the Rule list of the table. As additional rules are created in the table (described below), they are added to the Rule list. 2. Upon exiting the Rule List screen, if changes have been made to at least one rule, an Exit Option window is displayed. One option of the window allows creation of a new table in which the rules are saved.
Creating CMEM Rules

CMEM rules can be created using the following basic methods: 1. A skeletal rule definition can be created by specifying the name of a new rule in the entry panel. (The table specified in the entry panel can be either a new or an existing table.) In this case, the fields in the rule definition are empty. 2. A basic copy of an existing rule can be created using the INSERT option (described later) in the Rule List screen. In this case, most fields of the new rule definition contain the same values as the fields in the copied rule.
Performing Operations on CMEM Tables and Rules

Many operations can be performed on CMEM rule tables and on the rules contained within them. These operations are performed via commands and options in the various screens of the CMEM Rule Definition facility. Below is a brief summary of some of the major operations possible in the facility. Options and commands which have not yet been explained will be explained in detail following the summary. Accessing (Editing/Browsing) a Table and its Rules A table (i.e., the rules in the table) can be browsed or edited. When browsed, the table cannot be modified or updated. When the table is edited, new rules can be added and existing rules can be modified or deleted. Browsing, however, has advantages:
Access and exit are quicker than in editing. A rule list and/or rules that are in use by another user can be viewed. Access for browsing might be granted, even though access for editing might be denied due to site security requirements.
To browse a table (and its rule list and the rules it contains) use the BROWSE option in the Table List screen.
2 116
Online Facility: CMEM Rule Definition Facility Entry Panel
Specifying the table name in the entry panel or using the SELECT option in the Table List screen provides edit access. Depending on User Profile definitions, if the table requested for editing is in use, either access will be granted in Browse mode or access will not be granted. Deleting a Table or a Rule Unneeded rules can be deleted via the DELETE option in the Rule List screen. See Options of the Rule List Screen below. Unneeded tables can be deleted via the DELETE option in the Table List screen. See Deleting Tables. Ordering Rule Tables Rule tables are ordered via option ORDER or FORCE in the Table List screen. See Ordering CMEM Rule Tables later in this section. Saving Modifications All changes made to a table and its rules are kept in memory until the table is exited. Upon exiting the table, the user can choose to save or cancel the changes. See Exiting the CMEM Rule Definition Facility later in this section.
Entry Panel
The entry panel is displayed upon entering the CMEM Rule Definition facility (option C on the IOA Primary Option menu).
----------------- CMEM RULE DEFINITION FACILITY - ENTRY PANEL --------------(C) COMMAND ===>
SPECIFY LIBRARY, TABLE NAME, RULE NAME LIBRARY TABLE RULE ===> CTM.PROD.RULES ===> ===>
(Blank for table selection list) (Blank for rule selection list)
USE THE COMMAND SHPF TO SEE PFK ASSIGNMENT
22.35.51
2 117
Online Facility: CMEM Rule Definition Facility Table List Screen

Fill in the following fields and press <ENTER>. LIBRARY Name of the desired CMEM rule library. Mandatory. If this field is specified without filling in the TABLE field, the list of tables in the specified library is displayed in the Table List screen. TABLE Name of the desired rule table. Optional. If this field is specified without filling in the RULE field, the list of rules in the specified member is displayed in the Rule List screen. If a new table name is specified, a new rule definition is displayed in the Rule Definition screen. RULE Name of the desired rule. Optional. This field can be specified only if a TABLE value is specified. If specified, the requested rule is displayed in the Rule Definition screen.
Table List Screen

The Table List screen displays a list of rule tables (members) in the specified library. This screen can be entered directly from the entry panel or upon exiting the Rule List screen. By default, only table names are listed in the screen. However, if the default has been modified at time of installation, statistical information is displayed for each table name (as shown below).
TABLES OF LIBRARY CTM.PROD.RULES COMMAND ===> OPT NAME -------------- VV.MM CREATED PRDJACCT 01.06 98/06/06 PRDJPYRL 01.03 98/06/06 PRDJFNC 01.01 98/06/06 PRDJMRKT 01.01 98/06/06 BACKUP 01.01 98/06/06 TESTJ 01.06 98/06/06 ======= >>>>>>>>>>>>>>>> NO MORE TABLES -------------(C) SCROLL===> CRSR CHANGED SIZE INIT MOD ID 98/06/06 14:29 56 56 0 M06 98/06/06 10:11 56 56 0 M86B 98/06/06 13:06 6 6 0 N04A 98/06/06 15:08 5 5 0 N04B 98/06/06 14:35 61 56 0 M06 98/06/06 11:16 6 56 0 M06 IN THIS LIBRARY <<<<<<<<<<<<<<< =======
OPTIONS:
S SELECT
O ORDER
F FORCE
B BROWSE
D DELETE
12.11.50
Use the scrolling PFKeys to scroll the Table list forward (PF08/PF20) and backward (PF07/PF19). To return to the entry panel, press the END key (PF03/PF15).
2 118
Online Facility: CMEM Rule Definition Facility Rule List Screen
Options of the Table List Screen

To request one of the following options, specify the option in the OPT field to the left of the table name(s) and press <ENTER>. S SELECT Display the list of rules in the table for any purpose, including editing/modification. Only one table can be selected at a time. Order all rules in the table (discussed later in this section). Multiple tables can be ordered. Display a list of rules in the table for browsing. Only one table can be browsed at a time. Order all rules in the table. (Because CMEM rules have no Basic Scheduling parameters, this option works like the Order option.) Delete the table (member) from the library (discussed later in this section). Multiple tables can be deleted.
O ORDER B BROWSE F FORCE
D DELETE
Note
Users whose access to options has been limited by the IOA administrator can only access the Browse option.
Rule List Screen

The Rule List screen displays the list of CMEM rules in the specified CMEM table. The following fields are listed for each rule: OPT TYPE Select, Delete and Insert options can be specified in this field. See Options of the rule list screen below. The rules event type. The following event type codes exist: R X D Z Job arrival Job end Dataset Step
DESCRIPTION The rules description (which appears in the DESCRIPTION field of the rule definition). This screen can be entered directly from the entry panel or the Table List screen, or upon exiting from the Rule Definition screen. Note If the S (Select) option was specified in the Table List screen for a table which is currently in use (selected) by another user, either the Rule List screen is not displayed and the Table List screen remains displayed (the default), or the Rule List screen is displayed in Browse mode (if a User Profile definition overrides the default). In either case, an appropriate message is displayed.
2 119
Online Facility: CMEM Rule Definition Facility Rule List Screen
RULES OF LIBRARY: CTM.PROD.RULES TABLE: TESTJ COMMAND ===> SCROLL===> CRSR OPT RULE TYP -------------- DESCRIPTION -------------------------------JOBNAM1 R ON JOB JOBNAM1 ARRIVAL FORCEJOB JOBN*2 R ON JOB JOBN*2 ARRIVAL ADDCOND JOBNAM3 X ON JOB JOBNAM3 JOBEND FORCEJOB JOBN*4 X ON JOB JOBN*4 JOBEND DELCOND JOBDST* D ON JOB JOBDST* DATASET * DELETE FORCEJOB MERGE D ON JOB MERGE DATASET * NCT 2 CICSP D ON JOB CICSP DATASET * CATLG ADDCOND PROD* D ON JOB PROD* DATASET * NCT 2 ======= >>>>>>>>>>>>>>>>> NO MORE RULES IN THIS TABLE <<<<<<<<<<<<<<<<< =======
OPTIONS:
S SELECT
D DELETE
I INSERT
12.22.27
Use the scrolling PFKeys to scroll the Rule list forward (PF08/PF20) and backward (PF07/PF19).
Options of the Rule List Screen

To request one of the following options, specify the option in the OPT field to the left of the rule name(s) and press <ENTER>. Note If the Rule List screen is displayed in Browse mode, options D (Delete) and I (Insert) are not available. Display the Rule Definition screen with details of the specific rule. Only one rule can be selected at a time. If the Rule List screen is not displayed in Browse mode, the rule definition can be edited and updated. If the Rule Definition screen is displayed in Browse mode, the rule definition can only be browsed; it cannot be modified. D DELETE I INSERT Delete a rule from the Rule list (member). Multiple rules can be selected for deletion. Insert a new rule in the list. The Rule Definition screen appears, with the same details of the rule marked I. Only one rule can be inserted at a time.
SELECT
2 120
Online Facility: CMEM Rule Definition Facility Rule Definition Screen Defining Rules
Rule Definition Screen Defining Rules

The Rule Definition screen is used to define, display and modify parameters of a specific CMEM rule. This screen can be entered directly from the entry panel or from the Rule List screen. Update of parameters is not permitted in Browse mode. The rule definition can take up more than one screen. Use the scrolling PFKeys to scroll the rule definition forward (PF08/PF20) and backward (PF07/PF19). To delete a parameter on the screen, simply erase it via the EOF key or blank it out. If additional action is required, CONTROL-M issues appropriate instructions.
RL: BKP* LIB CMEM.PROD.RULES TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON JOBARRIV = BKP* JTYPE AND/OR/NOT OWNER ADMIN GROUP BACKUP MODE PROD RUNTSEC DESCRIPTION MONITOR STARTUP OF BACKUP JOBS DESCRIPTION =========================================================================== /* TELL CONTROL-M TO MONITOR THIS JOB /* DO FORCEJOB = TABLE BACKUP JOB DATE ODAT LIBRARY CTM.PROD.SCHEDULE /* DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
FILL IN RULE DEFINITION. CMDS: EDIT , SHPF
21.00.36
Rule parameters are divided into the following basic groups: A. Event Selection Parameters B. General Parameters C. Action Parameters A brief explanation of available parameters follows. For a detailed explanation of each rule parameter, refer to Section 4 of this manual. Note Parameters marked below with the G symbol can have many occurrences. Whenever you fill in the last occurrence of the parameter on the screen, CONTROL-M adds a new empty occurrence of the parameter which can be filled in. The only limit to the number of occurrences is the region size available for the application.
2 121
Event Selection Parameters

Event Selection parameters specify selection criteria under which actions will be performed by CMEM.
ON JOBARRIV = A* ON JOBARRIV = C* OWNER ADMIN GROUP CICS JTYPE J And/Or/Not O JTYPE J And/Or/Not RUNTSEC
MODE
ON JOBEND = CICSPROD OWNER ADMIN GROUP CICS
JTYPE And/Or/Not MODE PROD RUNTSEC
ON DSNEVENT = JOBNAME PRD00010 DSN PROD.* PROCSTEP PGMSTEP OWNER ADMIN GROUP PRODJOBS
STEPRC MODE
DISP NCT2 JTYPE J And/Or/Not RUNTSEC
ON STEP
= JOB PRD00010 STEPRC OK OWNER CTMCTLM GROUP
PROCSTEP STEP2 JTYPE
PGMSTEP MODE PROD And/Or/Not RUNTSEC NONE
ON statement
Conditions under which the rule is to be performed. Subparameters may be displayed. Valid ON statements are: ON JOBARRIV ON JOBEND ON DSNEVENT Job name (or mask) of a job or started task that arrived on the JES spool from any source. Job name (or mask) of a job or started task which terminated. Name (or mask) of a job/started task/TSO user to be monitored for dataset events (including NOT CATLGD 2 events). Name (or mask) of a job procedure step (and optionally, program step) which terminated, and its desired return code. subparameter which enables linking of ON
ON STEP
AND/OR/NOT
Conjunctional statements.
2 122
General Parameters
The following are General parameters which apply to the rule.
ON JOBARRIV = BKP* OWNER ADMIN GROUP BACKUP DESCRIPTION MONITOR STARTUP OF BACKUP JOBS DESCRIPTION JTYPE AND/OR/NOT MODE PROD RUNTSEC
OWNER GROUP MODE RUNTSEC DESCRIPTION
ID of user requesting CMEM services. Logical name of a group of rules. CMEM rule operation mode. Type of runtime security checks to be performed by the rule. Free-text description of the rule definition which will appear in the Rule List screen.
Action Parameters
Action parameters specify actions to be performed by CMEM. DO statement
DO COND DO
Actions to be performed when the rule is triggered. They are performed sequentially. Valid DO statements are illustrated below:
= FILE-RECEIVED ODAT +
DO COND
Add/delete a prerequisite condition.

DATE ODAT
DO FORCEJOB = TABLE BACKUP JOB LIBRARY CTM.PROD.SCHEDULE DO
DO FORCEJOB
DO STOPJOB DO
Force one or more jobs under CONTROL-M.
DO STOPJOB
Stop execution of the remaining steps of the job which triggered the rule.
The following DO statements are available only if CONTROL-O is installed.

DO SHOUT = TO TSO-DBA URGENCY U SYSTEM MESSAGE DB2 MASTER ENDED - PLEASE CHECK! DO
DO SHOUT
Issue a message to a console, TSO user, ROSCOE user, IOA Log or the system administrator using the CONTROL-O Shout facility.
= PROCFILE %%$DSN PRODRULE LIBRARY CTO.PROD.RULES OWNER PROD
DO RULE TABLE DO
DO RULE
Invoke a CONTROL-O rule from within the current rule.
2 123
Online Facility: CMEM Rule Definition Facility Specifying Comments
Commands of the Rule Definition Screen

The following commands can be specified in the COMMAND field of the Rule Definition screen. EDIT Command Command EDIT alternately enters/exits the Edit environment of the Rule Definition screen. The Edit environment provides ISPF-like line editing commands to the Rule Definition screen. See Appendix B for additional information. NEXT Command Command NEXT (PF11/PF23) displays the next rule definition in the table. PREV Command Command PREV (PF10/PF22) displays the previous rule definition in the table. CMNT Command Command CMNT (PF04/PF16) inserts comment lines before the current line specified by the cursors position. See Specifying Comments below for additional information. Commands used to exit the Rule Definition screen are described later.
Specifying Comments
Comments are free text descriptions of rule definition parameters which are stored in a rule definition. It is recommended that comments be inserted within rule definitions for clarification and documentation purposes. Comments are not processed during rule execution. Any of several methods can be used to insert comment lines.
Position the cursor at the line before which the comment should be inserted, and press CMNT (PF04/PF16). A comment line is opened beginning with the symbol /*. To insert additional lines, fill in the current line and press <ENTER>. Type command CMNT in the COMMAND field and move the cursor to the line before which the comment should be inserted. Press <ENTER>. To insert comments between DO statements an additional method is available. Type /* in an empty DO statement and press <ENTER>.
2 124
Online Facility: CMEM Rule Definition Facility Editing CMEM Rule Definitions in the Edit Environment
Comment usage is illustrated in the following Rule Definition screen:

RL: BKP* LIB CMEM.PROD.RULES TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON JOBARRIV = BKP* JTYPE AND/OR/NOT OWNER ADMIN GROUP BACKUP MODE PROD RUNTSEC DESCRIPTION MONITOR STARTUP OF BACKUP JOBS DESCRIPTION =========================================================================== /* TELL CONTROL-M TO MONITOR THIS JOB /* DO FORCEJOB = TABLE BACKUP JOB DATE ODAT LIBRARY CTM.PROD.SCHEDULE /*m DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
An unlimited number of comment lines can be specified within a rule definition.
Editing CMEM Rule Definitions in the Edit Environment

Rule Definition parameters can be edited (moved, copied, deleted, repeated) via CMEM Line Editing commands, similar to standard ISPF line commands, from within the CMEM Edit environment. The Edit environment in a Rule Definition screen is accessed by typing EDIT in the COMMAND field and pressing <ENTER>.
RL: BKP* LIB CMEM.PROD.RULES TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ __ ON JOBARRIV = BKP* JTYPE AND/OR/NOT __ OWNER ADMIN GROUP BACKUP MODE PROD RUNTSEC __ DESCRIPTION MONITOR STARTUP OF ACKUP JOBS __ DESCRIPTION __ =========================================================================== __ /* TELL CONTROL-M TO MONITOR THIS JOB __ /* __ DO FORCEJOB = TABLE BACKUP JOB DATE ODAT __ LIBRARY CTM.PROD.SCHEDULE __ /* __ DO __ =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
2 125
Online Facility: CMEM Rule Definition Facility Exiting the CMEM Rule Definition Facility
A two-character Line Editing command field, marked by underscores, is displayed for each line on the Rule Definition screen. Editing commands are typed directly onto these underscores. Specified Line Editing commands are processed when <ENTER> is pressed. Details and examples of the editing CMEM rule definitions in the Edit environment are provided in Appendix B.
Exiting the CMEM Rule Definition Facility

When exiting the CMEM Rule Definition facility, screens are exited in the following sequence:
Rule Definition screen Rule List screen Table List screen Note If the Table List screen was bypassed when you entered the CMEM Rule Definition facility (i.e., if you specified a TABLE value in the entry panel), the Table List screen is not displayed upon exiting the Rule List screen; instead, the entry panel is displayed.
Entry panel
The commands and options available when exiting screens depend on the screen being exited and on whether or not changes have been made. If changes have been made, the selected exit options and commands will determine whether or not the changes are saved. Exit options and commands are discussed below on a screen-by-screen basis.
Exiting the Rule Definition Screen

Use any of the following commands, or press the corresponding PFKey, to exit the Rule Definition screen: CANCEL END (PF03/PF15) Note Cancel the changes made to the rule and return to the Rule List screen. Keep changes to the rule in memory and exit to the Rule List screen.
Command END retains changes to the rule in memory. To permanently save the changes to disk, you must request that the changes be saved when you exit the Rule List screen.
2 126
Online Facility: CMEM Rule Definition Facility Exiting the CMEM Rule Definition Facility
Exiting the Rule List Screen

Use the END command (PF03/PF15) to exit the Rule List screen. If changes made to at least one rule have been kept in memory (see Exiting the Rule Definition Screen) and/or if any changes have been made to the Rule List screen, the Exit Option window is displayed.
RULES OF LIBRARY: CTM.PROD.RULES TABLE: TESTJ COMMAN +-----------------------------------------------------------+ ===> CRSR OPT R | PLEASE SELECT EXIT OPTION | --------J | | J | SAVE CREATE | J | | J | LIBRARY CTM.PROD.RULES | J | TABLE BACKUP | FORCEJOB M | | C +-----------------------------------------------------------+ ADDCOND P ======= >>>>>>>>>>>>>>>>> NO MORE RULES IN THIS TABLE <<<<<<<<<<<<<<<<< =======
OPTIONS:
S SELECT
D DELETE
I INSERT
13.00.12
Fill in the Exit Option window as follows: The LIBRARY and TABLE fields indicate the library and table in which the rule definitions will be saved. The specified values can be modified (e.g., to save the rule definitions in a new or different table).
To save all changes currently in memory and exit the Rule List screen, specify Y (Yes) after the word SAVE or CREATE: Specify Y after SAVE if a table with the same name already exists in the specified library. Specify Y after CREATE if a table with the same name does not exist in the specified library. If you create a new table, the table name does not appear in the Table List screen upon exiting the Rule List screen; it first appears when you reenter the Table List screen from the entry panel.
Note
To cancel changes currently in memory and exit the Rule List screen, specify N (No) after the word SAVE or CREATE. To close the Exit Option window and remain in the Rule List screen (with the changes remaining in memory), press the RESET key (PF04/PF16).
2 127
Online Facility: CMEM Rule Definition Facility Deleting Tables
Exiting the Table List Screen

Press the END key (PF03/PF15) to exit the Table List screen.

Press the END key (PF03/PF15) to exit the entry panel.
Deleting Tables
Tables can be deleted from the Table List screen. To delete tables, specify option D (Delete) by the table names in the Table List screen and press <ENTER>. The confirmation window illustrated below is displayed, in sequence, for each table selected for deletion.
TABLES OF LIBRARY CTMP.V500TST.RULES -------------(C) COMMAND ===> SCROLL===> CRSR OPT NAME -------------- VV.MM CREATED CHANGED SIZE INIT MOD ID PRDJACCT 01.06 98/06/06 98/06/06 14:29 56 56 0 M06 PRDJPYRL 01.03 98/06/06 98/06/06 10:11 56 56 0 M86B PRDJFNC +--------------------------+ 6 6 0 N04A PRDJMRKT | CONFIRM DELETE OPTION | 5 5 0 N04B D BACKUP <-----------| (Y/N) | 61 56 0 M06 TESTJ +--------------------------+ 6 56 0 M06 ======= >>>>>>>>>>>>>>>> NO MORE TABLES IN THIS LIBRARY <<<<<<<<<<<<<<< =======
OPTIONS:
S SELECT
O ORDER
F FORCE
B BROWSE
D DELETE
13.05.52
Specify Y (Yes) in the window to confirm the delete request. Specify N (No) in the window to cancel the delete request. A message is written to the IOA Log file for each table deleted. Note If PDSMAN is operational at your site, $$$SPACE members will not be deleted.
2 128
Online Facility: CMEM Rule Definition Facility Ordering CMEM Rule Tables
Ordering CMEM Rule Tables

A rule definition which resides in a library is not active until it has been ordered. Rule tables can be ordered automatically when CMEM is started (as described in the IOA Administrator Guide) or they can be ordered manually. Regardless of the method used to order them, CMEM rule tables only need to be ordered once. Once a rule table is ordered, it remains active unless replaced or deleted by an operator command, or until CMEM is stopped. When rule definitions are updated or modified, the rule table should be ordered again. The newly ordered version of the rule table will automatically replace the previous version of the rule table. (Rule tables can be deleted from the Active environment by an operator command. See Section 6 of this manual for details.) To order a rule table, specify option O (Order) or F (Force) in the OPT field to the left of the table name in the Table List screen. (Because there are no basic scheduling criteria in CMEM rules, the Order and Force options work the same way.) More than one rule table can be ordered at the same time. When you order rule tables, the following default confirmation window is opened (if the default has been modified in the User profile, a confirmation window requiring double confirmation is opened):
TABLES OF LIBRARY CTM.PROD.RULES -------------(C) COMMAND ===> SCROLL===> CRSR OPT NAME -------------- VV.MM CREATED CHANGED SIZE INIT MOD ID PRDJACCT 01.06 98/06/06 98/06/06 14:29 56 56 0 M06 PRDJPYRL +-------------------------------+ 56 0 M86B PRDJFNC | CONFIRM ODATE 060698 | 6 0 N04A O PRDJMRKT <-----------| ASK FOR EACH ONE Y | 5 0 N04B O BACKUP +-------------------------------+ 56 0 M06 TESTJ 01.06 98/06/06 98/06/06 11:16 6 56 0 M06 ======= >>>>>>>>>>>>>>>> NO MORE TABLES IN THIS LIBRARY <<<<<<<<<<<<<<< =======
OPTIONS:
S SELECT
O ORDER
F FORCE
B BROWSE
D DELETE
12.11.50
2 129
Online Facility: CMEM Rule Definition Facility Ordering CMEM Rule Tables
CONFIRM
Whether or not to process the order request. Valid values are: Y (Yes) N (No) Process the request. Cancel the request.
ODATE
Current date (in mmddyy, ddmmy or yymmdd format, depending on the site-standard).
ASK FOR EACH ONE This line is displayed only if more than one table order is requested. It determines whether or not individual confirmation is required for each order request. Valid values are: Y (Yes) Individual confirmation is required for each order request. The specified CONFIRM value (Y or N) applies only to the current order or request. Individual confirmation is not required for each order request. The specified CONFIRM operation is applied to all order requests. (If CONFIRM is Y, all order requests will be processed; if CONFIRM is N, no order requests will be processed.)
N (No)
When you press <ENTER>, the results of the order request are displayed in a message at the top of the screen. If more than one message is required, the original list screen disappears and the messages appear in a new screen. If the messages span more than one screen, you can scroll up and down on the messages list. Press the END key (PF03/PF15) to return to the Table List screen.
2 130
Online Facility: Condition/Resource Handling General
Condition/Resource Handling
General
Two options (option 4 and option 7) in the IOA Primary Option menu are directly related to the handling of IOA conditions and resources. The screens displayed by these options are discussed on the following pages.
IOA Conditions/Resources Screen

The IOA Conditions/Resources screen displays all existing Control resources, Quantitative resources and prerequisite conditions. To enter this screen, select option 4 in the IOA Primary Option menu. Use of the IOA Conditions/Resources screen requires a basic understanding of prerequisite conditions (used for establishing job dependencies), Quantitative resources (used for avoiding dynamic resource contention) and Control resources (used for controlling parallel use of resources by jobs). These subjects are discussed in Section 1 of this manual.
-------------------------- IOA CONDITIONS/RESOURCES ------------------------(4) COMMAND ===> SCROLL ===> CRSR PREFIX ===> COND Y CONTROL Y RES Y STAT Y DATE 0909 - 0909 OPT TYPE CONDITION/RESOURCE DATE USE QUANTITY MAX *P RBA IOAID CONTROL CONTROLM E (00000) 01 RESOURCE TAPEP 0003 0003 RESOURCE CPU1 0098 0100 RESOURCE CPU2 0197 0200 RESOURCE TAPEP Q 0002 (00091) 01 RESOURCE CPU1 Q 0002 (00091) 01 RESOURCE CPU2 Q 0003 (00092) 01 RESOURCE TAPEP R 0002 1 (00093) 01 COND BR-BRIVPCC-ENDED-OK 0909 COND BR-BRCC0001-ENDED-OK 0909 COND BR-BRCC0002-ENDED-OK 0909 COND BR-BRCC0003-ENDED-OK 0909 COND BR-BRCCIND-ENDED-OK 0909 COND BR-BRUPDT02-ENDED-OK 0909 COND BR-BRREP001-ENDED-OK 0909 COND BR-BRREP002-ENDED-OK 0909 COND GL-GLINP001-ENDED-OK 0909 COND EBD-APPL-STARTED 0909 COND CICS-PROD-IS-UP STAT OPTIONS: D DELETE C CHANGE COMMANDS: ADD 14.07.08
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) in the IOA Conditions/Resources screen. To return to the IOA Primary Option menu, press the END key (PF03/PF15).
2 131
Online Facility: Condition/Resource Handling IOA Conditions/Resources Screen
Fields of the IOA Conditions/Resources Screen

The information displayed in each screen line (A) is: OPT TYPE Option to be activated on the condition/resource. Type of condition/resource: COND CONTROL RESOURCE Prerequisite condition Control resource Quantitative resource
CONDITION/RESOURCE Name of the condition/resource. DATE USE Original date reference of a prerequisite condition (format mmdd or ddmm depending on the site standard, or the value STAT). Resource usage indicator for Control or Quantitative resources. Valid values depend on the type of resource. For Control resources, valid values are: E S The resource is being used in Exclusive mode. The resource is being used in Shared mode.
For Quantitative resources, valid values are: blank Q R QUANTITY The line indicates the initial definition for the resource. The line indicates an instance of resource usage. The line indicates an unfulfilled critical path request (i.e., request with an *-type priority) for the resource.
Quantity of a Quantitative resource. What the quantity represents depends on the value in the USE field, as follows: USE blank QUANTITY Quantity available. If the maximum quantity is more than 1 but only 1 is available, 0001 is displayed in pink. If the maximum quantity is more than 1 but none is available, 0000 is displayed in red. Quantity in use by the particular process. Quantity requested by the particular process, but unfulfilled.
Q R MAX *P
Maximum available quantity of a Quantitative resource. Priority of the job requesting a CONTROL-M resource using *-type priority. (See parameter PRIORITY in Section 3 of this manual for more information.)
2 132
RBA
Internal CONTROL-M ID (relative block address) of the job currently holding a CONTROL-M resource. An RBA value of 000000 indicates that the resource was added manually. Control resources in shared mode do not display an RBA. Note To determine which job is using a particular resource, specify the RBA of the resource when specifying the RBAL command in the Status screen. (See RBAL Command in Commands of the Status Screen earlier in this section of the manual.)
IOAID
ID of the IOA installation which is using the particular Control or Quantitative resource. This value is significant when multiple IOA installations share the same resources.
Specifying Retrieval Criteria

The user can control the type and amount of information displayed in the screen by specifying retrieval criteria (B). PREFIX prefix Limits the display to conditions and/or resources with the specified prefix. Default: blank (no limit). To limit the display to conditions and/or resources containing a specific string, specify the string preceded by an *. For example, if *OK is specified, the following are included in the display:
UPDATE-ENDED-OK OK-RUN OK
COND
Determines whether or not prerequisite conditions are displayed. Valid values: Y (Yes) N (No) Display prerequisite conditions. Default. Do not display prerequisite conditions.
CONTROL
Determines whether or not Control resources are displayed. Y (Yes) N (No) Display Control resources. Default. Do not display Control resources.
RES
Determines whether or not Quantitative resources are displayed. Y (Yes) N (No) Display Quantitative resources. Default. Do not display Quantitative resources.
STAT
Determines whether or not prerequisite conditions with a date value of STAT are displayed. (Applies only if Y is specified for COND.) Y (Yes) N (No) Include prerequisite conditions with a date value of STAT. Do not include prerequisite conditions with a date value of STAT.
2 133
DATE from to Limits the display of prerequisite conditions to the specified date range. Valid values: from Earliest date in the date range, in mmdd or ddmm format (depending on the site standard). The default value is three days prior to the current date. This default can be modified in the Profile Variable member by the IOA administrator. Latest date in the date range, in mmdd or ddmm format (depending on the site standard). The default value is the current date.
to
Adding Conditions and Resources The ADD Command

The ADD command adds conditions and resources to the IOA Conditions/Resources file. Specify this command in the COMMAND field, and press <ENTER>. Format of the command is:
ADD type
Where type is one of the following: COND Add a prerequisite condition. Special care should be taken when adding prerequisite conditions, because added conditions can trigger job submission. Add a Quantitative resource. Quantitative resources should be added only by authorized personnel. Add a Control resource. A Control resource entry can be added manually even if a job is holding the resource.
RESOURCE CONTROL
2 134
When the ADD command is specified, an appropriate window is opened. The window shown below opens when ADD COND is specified.
-------------------------- IOA CONDITIONS/RESOURCES ------------------------(4) COMMAN +---------------------------------------------------------+ L ===> CRSR PREFIX | PLEASE FILL IN COND NAME, DATE AND PRESS ENTER | 0909 - 0909 OPT TY | | A IOAID CO | NAME ===> DDMM ===> | 00) 01 RE | | RE +---------------------------------------------------------+ RE RESOURCE TAPEP Q 0002 (00091) 01 RESOURCE CPU1 Q 0002 (00091) 01 RESOURCE CPU2 Q 0003 (00092) 01 RESOURCE TAPEP R 0002 1 (00093) 01 COND BR-BRIVPCC-ENDED-OK 0909 COND BR-BRCC0001-ENDED-OK 0909 COND BR-BRCC0002-ENDED-OK 0909 COND BR-BRCC0003-ENDED-OK 0909 COND BR-BRCCIND-ENDED-OK 0909 COND BR-BRUPDT02-ENDED-OK 0909 COND BR-BRREP001-ENDED-OK 0909 COND BR-BRREP002-ENDED-OK 0909 COND GL-GLINP001-ENDED-OK 0909 COND EBD-APPL-STARTED 0909 COND CICS-PROD-IS-UP STAT OPTIONS: D DELETE C CHANGE COMMANDS: ADD 14.07.08
Fill in the window fields as described below according to the specified ADD command: ADD COND ADD RESOURCE ADD CONTROL Specify the name of the prerequisite condition. The current working date is displayed as the default date. This date can be modified. Specify the name of the Quantitative resource and the quantity to be added. Specify the name of the Control resource and the control type (E Exclusive; S Shared). Notes If a CONTROL resource is manually added with a type of E (Exclusive) no jobs in WAIT SCHEDULE status which require this resource will be submitted. If a CONTROL resource is manually added with a type of S (Shared) no jobs in WAIT SCHEDULE status which require exclusive access to this resource will be submitted. After filling in the window, press <ENTER> to add the condition or resource. To close the window without adding the condition or resource, press the RESET key (PF04/PF16).
2 135
Options of the IOA Conditions/Resources Screen

The following options can be specified for conditions/resources by typing the option in the OPT field to the left of the resource or condition name and pressing <ENTER>. Available options: D DELETE C CHANGE Delete a condition/resource from the list. The event is recorded in the IOA Log file. Change the maximum available quantity of a Quantitative resource. The event is recorded in the IOA Log file.
These options are discussed in detail on the following pages. Deleting Conditions and Resources The DELETE Option To delete conditions/resources, specify D (Delete) in the OPT field to the left of the conditions and resources being deleted and press <ENTER>. A confirmation window may be displayed, depending on User profile customization:
By default, conditions/resources are deleted without confirmation from the user. If, however, the User profile has been customized accordingly, a confirmation window is displayed with an arrow pointing to a delete request (beginning with the first request).
-------------------------- IOA CONDITIONS/RESOURCES ------------------------(4) COMMAND ===> SCROLL ===> CRSR PREFIX ===> COND Y CONTROL Y RES Y STAT Y DATE 0909 - 0909 OPT TYPE CONDITION/RESOURCE DATE USE QUANTITY MAX *P RBA IOAID COND SALARY-PRSL01A-OK 0909 COND SALARY-PRSL002-OK 0909 +----------------------+ COND SALARY-PRSL003-OK 0909 | CONFIRM | D COND CBT-TAPE-ARRIVED 0909 <---------| ASK FOR EACH ONE Y | D COND KPL-PRKPL03-OK 0909 +----------------------+ COND KPL-PRKPL04-OK 0909 ======== >>>>>>>>>>>>>>>> B O T T O M O F L I S T <<<<<<<<<<<<<<<< ========
OPTIONS:
D DELETE
C CHANGE
COMMANDS: ADD
14.07.08
2 136
If a confirmation window is displayed, fill in the window as follows and press <ENTER>: CONFIRM Whether or not to process the delete request. Valid values: Y (Yes) N (No) Process the request. Cancel the request.
ASK FOR EACH ONE This line is displayed only if more than one delete is requested. It determines whether or not individual confirmation is required for each delete request. Valid values: Y (Yes) Individual confirmation is required for each delete request. The specified CONFIRM operation applies only to the current order or request. Individual confirmation is not required for each delete request. The specified CONFIRM operation is applied to all delete requests. (If CONFIRM is Y, all delete requests will be processed; if CONFIRM is N, no delete request will be processed.)
N (No)
Changing the Quantity of a Resource The CHANGE Option To request a change to the maximum available quantity of a resource, specify C (Change) in the OPT field to the left of the resource and press <ENTER>. The following window is opened.
-------------------------- IOA CONDITIONS/RESOURCES ------------------------(4) COMMAN +---------------------------------------------------------+ L ===> CRSR PREFIX | PLEASE FILL IN QUANT RES NAME, COUNT AND PRESS ENTER | 0909 - 0909 OPT TY | | A IOAID CO | NAME ===> TAPEP COUNT ===> | 00) 01 C RE | | RE +---------------------------------------------------------+ RE RESOURCE TAPEP Q 0002 (00091) 01 RESOURCE CPU1 Q 0002 (00091) 01 RESOURCE CPU2 Q 0003 (00092) 01 RESOURCE TAPEP R 0002 1 (00093) 01 COND BR-BRIVPCC-ENDED-OK 0909 COND BR-BRCC0001-ENDED-OK 0909 COND BR-BRCC0002-ENDED-OK 0909 COND BR-BRCC0003-ENDED-OK 0909 COND BR-BRCCIND-ENDED-OK 0909 COND BR-BRUPDT02-ENDED-OK 0909 COND BR-BRREP001-ENDED-OK 0909 COND BR-BRREP002-ENDED-OK 0909 COND GL-GLINP001-ENDED-OK 0909 COND EBD-APPL-STARTED 0909 COND CICS-PROD-IS-UP STAT OPTIONS: D DELETE C CHANGE COMMANDS: ADD 14.07.08
2 137
The NAME value in the window is protected and cannot be changed. Parameter COUNT consists of two values: sign and quantity. Fill in parameter COUNT as follows and press <ENTER>: sign Valid values (one character): + Add the specified quantity to the current maximum available quantity to give a new maximum available quantity. Subtract the specified quantity from the current maximum available quantity to give a new maximum available quantity. Set the maximum available quantity quantity. to the specified
blank quantity
Quantity to be used to adjust the maximum quantity of the resource (four digits) according to the specified sign. Leading zeros are required.
2 138
Online Facility: Condition/Resource Handling IOA Manual Conditions Screen
IOA Manual Conditions Screen

The IOA Manual Conditions screen displays a list of prerequisite conditions that should be confirmed manually by operations personnel. The list of manual conditions is created by utility IOALDNRS. The utility is described in Section 9 of the IOA Administrator Guide. The utility scans the jobs in the CONTROL-M Active Jobs file and/or missions in the CONTROL-D Active Missions file for all conditions requested in IN parameters which:
Are not resolved by an OUT statement. Are not resolved by ON PGMST/DO COND statements. Do not exist in the IOA Conditions/Resources file.
The conditions conforming to the above criteria are to be manually added and are therefore placed in the IOA Manual Conditions file. This file is used as a checklist for manual operations which operations personnel are expected to perform. To enter the IOA Manual Conditions screen, select option 7 on the IOA Primary Option menu.
--------------------------- IOA MANUAL CONDITIONS --------------------------(7) COMMAND ===> SCROLL ===> CRSR PREFIX ===> PENDING Y ADDED Y STAT Y DATE 0909 - 0909 OPT TYPE CONDITION COND USR-GOT-TAX-TAPE COND DBA-RUN-UPDATE COND OP-EXTERNAL-TAPE-OK COND USR-GOT-BANK-TAPE COND OP-SHUT-THE-SYSTEM COND DBA-START-MPMXXX COND USR-GOT-SALARY-TAPE COND OP-COMMUNICATION-DOWN ======== >>>>>>>>>>>>>>>> B O T T O DATE ADDED 0909 0909 Y 0909 Y 0909 0909 0909 0909 Y 0909 M O F L I S T <<<<<<<<<<<<<<<< ========
OPTIONS: A ADD TO COND/RES LIST (SCREEN 4) E ERASE
COMMANDS: NEW 18.33.47
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) on the IOA Manual Conditions screen. To exit the IOA Manual Conditions screen, press END (PF03/PF15).
2 139
Fields of the IOA Manual Conditions Screen

The information displayed on each screen line (A) is: OPT TYPE CONDITION DATE ADDED Option to be activated on the condition. Type of condition, i.e., COND for prerequisite condition. Condition name. Date reference of prerequisite condition. Format is either mmdd or ddmm depending on the site standard, or the date value STAT. Whether or not the condition has been manually added to the IOA Conditions/Resources file. Y (Yes) N (No) Condition has been added. Condition has not been added.
Specifying Retrieval Criteria

The user can control the type and amount of information displayed in the screen by specifying retrieval criteria (B). PREFIX prefix If specified, limits the display to conditions with the specified prefix. To display only conditions containing a specific string, specify the string preceded by an *. Example If *OK is specified, the following conditions are included in the display:
UPDATE-ENDED-OK OK-RUN OK
PENDING
Determines whether or not conditions not yet added are displayed. Valid values: Y (Yes) N (No) Display pending conditions. Do not display pending conditions.
ADDED
Determines whether or not added conditions are displayed. Valid values: Y (Yes) N (No) Display added conditions. Do not display added conditions.
STAT
Determines whether or not prerequisite conditions with a date value of STAT are displayed. Valid values: Y (Yes) N (No) Display prerequisite conditions with a date value of STAT. Do not display prerequisite conditions with a date value of STAT.
2 140
DATE from to Limits the display of prerequisite conditions to the specified date range. Valid values: from Earliest date in the date range, in mmdd or ddmm format (depending on the site standard). The default value is three days before the current date. Latest date in the date range, in mmdd or ddmm format (depending on the site standard). The default value is the current date.
to
Options of the IOA Manual Conditions Screen

To add a condition to the IOA Conditions/Resources file or to erase a condition from the Manual Conditions file, specify the appropriate option in the OPT field to the left of the condition name and press <ENTER>. Valid options: A ADD Add the condition in the IOA Conditions/Resources file (Screen 4), and mark it Added (Y) in the IOA Manual Conditions file. The event is recorded in the IOA Log file. Erase (Delete) a condition from the IOA Manual Conditions file. This does not affect the IOA Conditions/Resource file. This option is discussed in more detail below.
E ERASE
Erasing (Deleting) Conditions To erase prerequisite conditions, specify E in the OPT field to the left of the condition names being erased and press <ENTER>. A confirmation window may be displayed, depending on User profile customization:
By default, condition(s) are deleted without confirmation from the user. If, however, the User profile member has been customized accordingly, a confirmation window is displayed with an arrow pointing to an erase request (beginning with the first request).
2 141
--------------------------- IOA MANUAL CONDITIONS --------------------------(7) COMMAND ===> SCROLL ===> CRSR PREFIX ===> PENDING Y ADDED Y STAT Y DATE 0909 - 0909 OPT TYPE CONDITION DATE ADDED COND DAILY-PROD-KPL-GO 0908 COND SALARY-GROUP-GO 0908 COND SALARY-PROMPTED-OK 0908 +----------------------+ COND SALARY-TAPE-ARRIVED 0908 | CONFIRM | E COND PROD-PRUPDT03-GO 0909 <---------| ASK FOR EACH ONE Y | E COND PROD-INTAPE-OK 0909 +----------------------+ COND OP-START-BACKUP-180D 0909 COND OP-START-PRINT-STD 0909 COND OP-START-RESTORE-ADH 0909 ======== >>>>>>>>>>>>>>>> B O T T O M O F L I S T <<<<<<<<<<<<<<<< ========
If a confirmation window is displayed, fill in the window as follows and press <ENTER>: CONFIRM Whether or not to process the erase (delete) request. Valid values: Y (Yes) N (No) Process the request. Cancel the request.
ASK FOR EACH ONE This line is displayed only if more than one erase is requested. It determines whether or not individual confirmation is required for each erase request. Valid values: Y (Yes) Individual confirmation is required for each erase request. The specified CONFIRM operation applies only to the current order or request. Individual confirmation is not required for each erase request. The specified CONFIRM operation is applied to all erase requests. (If CONFIRM is Y, all erase requests are processed; if CONFIRM is N, no erase request are processed.)
N (No)
2 142
Adding a New Prerequisite Condition NEW COND Command

To add a prerequisite condition to the IOA Manual Conditions file, type NEW COND in the COMMAND field and press <ENTER>. A window is opened.
--------------------------- IOA MANUAL CONDITIONS --------------------------(7) COMMAN +---------------------------------------------------------+ L ===> CRSR PREFIX | PLEASE FILL COND NAME AND DATE AND PRESS ENTER | 0908 - 0909 OPT TY | | CO | NAME ===> MMDD ===> | CO | | CO +---------------------------------------------------------+ CO COND OP-SHUT-THE-SYSTEM 0909 COND DBA-START-MPMXXX 0909 COND USR-GOT-SALARY-TAPE 0909 Y COND OP-COMMUNICATION-DOWN 0909 ======== >>>>>>>>>>>>>>>> B O T T O M O F L I S T <<<<<<<<<<<<<<<< ========
In the NAME field of the window, type the name of the condition to be added. If the condition should have a date other than the current working date, specify the date in the date field (DDMM or MMDD, depending on the site standard) of the window.
To add the condition, press <ENTER>. To close the window without adding the condition, press RESET (PF04/PF16). Adding a new condition to the IOA Manual Conditions file does not affect the IOA Conditions/Resources file.
Note
2 143
Online Facility: IOA Log Facility General
IOA Log Facility

General
The IOA Log facility places automatically generated messages, which record significant events in the life of a job, in the IOA Log file. Significant events recorded in the IOA Log file include normal processing occurrences (e.g., job submitted) as well as error conditions encountered during processing (e.g., job abends). Message from the Shout facility notifications can be directed to the IOA Log file. User remarks can also be recorded in the IOA Log file.
IOA Log Screen

The Log screen enables you to view the information contained in the Log file. To enter the Log screen, select option 5 on the IOA Primary Option menu. Upon entry, the screen displays the most recent messages currently in the Log file.
FILTER: COMMAND ===> SHOW LIMIT ON ==> DATE 090998 090998 090998 090998 090998 090998 090998 TIME 092144 092144 092150 092150 092156 092157 092157 ---------------- IOA LOG -------------------------------(5) SCROLL===> CRSR DATE 090998 - 090998
ODATE 090998 090998 090998 090998 090998 090998 090998
USERID M22 M22 M22 M22 IVP IVP DBA
CODE SPY254I SEL208I SPY254I SEL208I SPY254I SEL208I CTM659I SPY281I
090998 092201 090998 M22
090998 092201 090998 M22 090998 092201 090998 M22 090998 092201 090998 M22
SPY254I SEL206W SEL219I
090998 092208 090998 IVP SEL203I 090998 092208 090998 IVP SUB133I 090998 092208 090998 IVP SEL203I CMDS: SHOW, GROUP, CATEGORY, SHPF
------------- M E S S A G E ------------JOB CT085955 CT085955/01835 SCANNED JOB CT085955 CT085955/01835 ENDED "OK" JOB CT085956 CT085956/01836 SCANNED JOB CT085956 CT085956/01836 ENDED "OK" JOB BRIVPCC BRIVPCC /01843 SCANNED JOB BRIVPCC BRIVPCC /01843 ENDED "OK" FREE OF TASK BRCC0001 ODATE 090998 PERFORMED JOB INTR0004 INTR0004/04371 START 98253.1316 STOP 98253.1316 CPU 0MIN 00.04SEC SRB 0MIN 00.00SEC 0.19 JOB INTR0004 INTR0004/04371 SCANNED JOB INTR0004 INTR0004/04371 ABENDED CC SB37 STEP STEP01 JOB INTR0004 INTR0004/04371 ENDED "NOT OK" JOB BRCC0001 ELIGIBLE FOR RUN JOB BRCC0001 BRCC0002/01958 SUBMITTED JOB BRCC0002 ELIGIBLE FOR RUN 09.43.00
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) in the IOA Log screen. To return to the IOA Primary Option menu, press END (PF03/PF15).
2 144
Online Facility: IOA Log Facility IOA Log Screen
Fields of the IOA Log Screen

A. SHOW LIMIT ON Identifies which non-yes/no selection criteria were specified in the Show Screen Filter window (USERID, MEM/MIS, JOBNAME, CATEGORY, GROUP). For more information, see Filtering the IOA Log Screen Display below. B. The following information is displayed for each message in the IOA Log screen: DATE TIME ODATE USERID CODE MESSAGE Date on which the message was issued. Time at which the message was issued. Working date on which the message was issued. Format is mmddyy, ddmmyy or yymmdd, depending on the site standard. User ID of the job issuing the message, or user ID of the user writing to the log. IOA message code. The message. If the message is longer than the space available on the screen, the message is split and continues on the following line. Messages relating to a job have the following format:
tasktype memname jobname/jobid message
Limiting the Date Range of Log Information C. fromdate todate The log information displayed in the screen can be limited to the specified date range in mmddyy, ddmmyy or yymmdd format (depending on the site standard). If the DATE and/or the ODATE value for a message is in the specified range, the message is included in the IOA Log display. Valid values: fromdate todate Earliest date in the date range. Latest date in the date range.
Commands of the IOA Log Screen

The following commands can be specified in the COMMAND field. SHOW Command Command SHOW either activates the specified screen filter or opens the Show Screen Filter window, depending on the format of the command. Valid formats are: SHOW name EDIT SHOW name SHOW (PF02/PF14) Opens the Show Screen Filter window for the specified filter. Activates the specified filter. Opens the Show Screen Filter window for the currently active filter.
Only jobs conforming to selection criteria specified in the filter are displayed in the IOA Log screen. (See Filtering the IOA Log Screen Display below.)
2 145
GROUP Command Command GROUP alternately displays/hides the GROUP name (if any) which is associated with the relevant job/mission/rule definition. When displayed, the name of the group appears after the job/mission/rule status. CATEGORY Command (at Sites Where CONTROL-D Is Active) Command CATEGORY alternately displays/hides the CATEGORY of the relevant CONTROL-D mission. This command applies to CONTROL-D generated messages only. When displayed, the name of the category appears after the mission status.
Filtering the IOA Log Screen Display

Screen filters can be used to filter records in the IOA Log screen. A filter consists of a set of record selection criteria (selection fields and their values). Only records which conform to the selection criteria specified in the filter are displayed in the screen. The IOA administrator can predefine filters and place them in the General profile. Each user can define multiple filters for the screen, via the Show Screen Filter window (described below). Each filter belongs to, is assigned a name by, and can only be activated by, the user who defined it.
21
A predefined default filter (called DEFAULT) is defined for the IOA Log screen. Site-defined defaults determine whether the last filter used or the DEFAULT filter will be activated upon reentry to the IOA Log screen. To activate an existing filter in the IOA Log screen (without opening the Show Screen Filter window), specify the SHOW command in the COMMAND field, as follows:
SHOW name
where: name Name of the filter to be activated.
Show Screen Filter Window To open the Show Screen Filter window to create or modify a filter, specify the SHOW command as follows:
To open the window for the currently active filter, specify:

SHOW (PF02/PF14)
To open the window for a new or existing filter, specify:

SHOW name EDIT
where: name Name of the filter to be displayed in the Show Screen Filter window.
21
Called the Show Option window prior to IOA Release 5.0.0.
2 146
The following Show Screen Filter window is displayed when only CONTROL-M is installed or when the IOA Log screen was requested via option L (Log) in the Status screen.
FILTER: COMMAND ===> SHOW LIMIT O DATE TIME 090998 14131 +-------------------- IOA LOG SHOW SCREEN ---------------(3.LOG) | FILTER SAVE (Y/N) | | CM : D JOB M JOB SHOUT USER GENERAL D INT M INT STAT | | Y Y Y N N N N Y | | CMEM : GENERAL | | | | | | | | | | | | | | | | CODE | | URGENCY: REGULAR Y URGENT Y VERY-URGENT Y | | TASK TYPE CM: JOB CYC EMR STC CST EST ECJ ECS WRN GRP | | Y Y Y Y Y Y Y Y Y Y | | | | | | USERID | | MEM/MIS | | JOBNAME | | CATEGORY | | GROUP | +--------------------------------------------------------------+
090998 14131 090998 14131 090998 14153 090998 14155
090998 14155 090998 14155 090998 14173 090998 14174
090998 14174 090998 14174 CMDS: SHOW,
Fields of the Show Screen Filter Window The Show Screen Filter window contains the following fields: FILTER User-assigned name of the filter. The name specified in the FILTER field can be modified. If changes to a filter have not been saved (see Closing the Show Screen Filter Window below), an asterisk is displayed to the right of the filter name. SAVE (Y/N) Specifies whether or not to save modifications to the filter upon closing the window.
Fields which define the selection criteria to be applied to the screen are described below. Fill in the selection criteria as desired. Notes The IOA administrator can limit which installed IOA products and options each user can access. However, because all IOA products and the messages they issue are integrated, it may be important for users to see the messages of products and options to which they have no access. Therefore, the types of messages for all IOA products are listed in the Show Screen Filter window of the IOA Log screen, and by default, the messages of all installed products are listed in the IOA Log screen. The selection criteria marked with symbol G act on a prefix basis. For example, specifying job name D4 will cause the retrieval of all jobs whose names start with D4.
2 147
CM message type
To limit the type of log messages displayed, specify Y (Yes) or N (No) under the desired message type. Valid CONTROL-M message type codes: D JOB M JOB SHOUT USER Messages related to jobs produced during New Day processing. Job-related messages produced by the CONTROL-M monitor. The majority of job messages are of this type. Messages written to the Log file by parameter SHOUT (see parameter SHOUT in Section 3). Messages resulting from manual intervention of authorized users in the operation of CONTROL-M; e.g., the addition of a prerequisite condition, HOLD or RERUN of the job, etc. General messages on CONTROL-M operation. Internal messages generated during New Day processing. For use mainly by maintenance personnel. Certain CMEM messages, and internal messages of the CONTROL-M monitor. Statistical information about job execution.
GENERAL D INT M INT STAT
CMEM message type To limit the type of log messages displayed, specify Y (Yes) or N (No) under the desired message type. Valid CONTROL-M message type codes: Valid CMEM message type code:
G CODE
URGENCY TASK TYPE
GENERAL
General messages on CMEM operation.
Show only IOA Log file messages with the specified message ID(s) or prefix(es). A maximum of 6 message IDs (or prefixes) can be specified. Mark Y (Yes) or N (No) to specify the desired urgency of messages. Urgent and very urgent messages are highlighted. When job messages are selected, limit the task types to be displayed. Specify Y to include or N to exclude the following task types: JOB CYC EMR STC CST EST ECJ ECS WRN GRP Regular job. Cyclic job. Emergency job. Started task. Cyclic started task. Emergency started task. Emergency cyclic job. Emergency cyclic started task. Warnings. Supported for historical reasons only. Group Entity.
2 148
USERID
Show only messages of the specified user ID(s). A maximum of five user IDs can be specified.
Notes
Selection criteria GROUP, MEM/MIS and JOBNAME, described below, only affect the display of messages related to a job. Messages not related to a job are not affected by these selection criteria and will be displayed unless suppressed by other selection criteria. CATEGORY is not relevant to CONTROL-M.
MEM/MIS
G G
Limit displayed job messages to the specified member name(s). A maximum of five member names can be specified. Messages not related to a job are not affected by this show limit. Limit displayed job messages to the specified job name(s). A maximum of five job names can be specified. Messages not related to a job are not affected by this show limit. CONTROL-D category. This selection field is not relevant to CONTROL-M and does not filter CONTROL-M jobs. Limit displayed job messages to the specified group(s). A maximum of four groups can be specified. Messages not related to a job are not affected by this show limit.
JOBNAME
CATEGORY GROUP
Show Screen Filter Window (at Sites Where Multiple IOA Products Are Active) The Show Screen Filter window displays different selection criteria depending on which IOA products are operational at your site. The Show Screen Filter window at sites where all IOA mainframe products are installed is illustrated below.
FILTER: COMMAND ===> SHOW LIMIT O DATE TIME 090998 21354 090998 22040 090998 22040 090998 22040 090998 22040 090998 22040 090998 22040 090998 090998 090998 090998 23034 23040 23040 23040 +-------------------- IOA LOG SHOW SCREEN -------------------(5) | FILTER SAVE (Y/N) | | CM : D JOB M JOB SHOUT USER GENERAL D INT M INT STAT | | Y Y Y Y Y N N N | | CO+CMEM: GENERAL SHOUT JOBS GENERAL W PIPE W JOB W | Y Y Y | | CD+CV : SBSYS REP MIS SHOUT USER GENERAL DAILY MONIT STAT | | Y Y Y Y Y Y N N N | | CB : RUNTIME SHOUT DAILY GENERAL STATISTICS | | Y Y Y Y Y | | CT : GENERAL SHOUT REAL-TIME UTILITIES | | Y Y Y Y | | CODE | | URGENCY: REGULAR Y URGENT Y VERY-URGENT Y | | TASK TYPE CM: JOB CYC EMR STC CST EST ECJ ECS WRN GRP | | Y Y Y Y Y Y Y Y Y Y | | CD: REP PRT BKP/MIG RST EMR NOEMR CYC NOCYC | | Y Y Y Y Y Y Y Y | | USERID | | MEM/MIS | | JOBNAME | | CATEGORY | | GROUP | +--------------------------------------------------------------+
090998 23040 090998 23040 090998 23040 CMDS: SHOW,
2 149
See the previous pages for a description of the CONTROL-M selection criteria. For descriptions of the selection options for other IOA products, see the user manuals of the respective products. Note The IOA administrator can limit which installed IOA products and options each user can access. However, because all IOA products and the messages they issue are integrated, it may be important for users to see the messages of products and options to which they have no access. Therefore, the types of messages for all IOA products are listed in the Show Screen Filter window of the IOA Log screen, and by default, the messages of all installed products are listed in the IOA Log screen.
Closing the Show Screen Filter Window An edited filter can be activated with or without saving changes, depending on the value specified in the SAVE field, as follows:
To activate and save the filter, specify Y (Yes) in the SAVE field. Changes to the filter are permanently saved. To activate the filter without saving it, specify N (No) in the SAVE field. Changes are kept in memory only, but are not saved.
After specifying a value in the SAVE field, press one of the following PFKeys: <ENTER> PF07 (UP) PF08 (DOWN) Filtering begins with the first message currently displayed in the screen and continues downward. Filtering begins with the first message in the IOA Log file and continues downward. Filtering begins with the last message in the IOA Log file and continues upward.
The window is closed and the filter is activated as defined or modified. To cancel changes made in the Show Screen Filter window, press RESET (PF10/PF22). The changes are canceled regardless of the value specified in the SAVE field, the window is closed, and the filter that was previously in effect is restored. By default, pressing END (PF03/PF15) in the window works like pressing <ENTER>. However, the default can be modified so that pressing END works like pressing RESET.
2 150
Online Facility: IOA Calendar Facility General
IOA Calendar Facility

General
The IOA Calendar facility enables you to create/view/modify job calendar definitions. Calendars simplify the scheduling of IOA product jobs/missions/rules, etc. When a particular schedule is used in many job scheduling, mission, and/or rule definitions, a calendar can be defined for that schedule, and that calendars name can be specified in all the job/mission/rule definitions which use that particular schedule. For example, calendars can be defined to handle the normal scheduling needs for workdays, holidays, weekends, beginning of month, end of month, etc. Exception calendars can also be created. A calendar definition consists of parameters which specify whether or not scheduling should occur on a specified date in a specified year. Calendar definitions are stored in members. A member usually contains multiple calendar definitions, as follows:
A member contains the calendars required for a specific type of scheduling need. For example, calendar member WORKDAYS may contain the calendar definitions for normal workday scheduling. Each calendar definition in that member defines the schedule for a given year. For example, calendar member WORKDAYS may contain calendar definitions 1998, 1999, and 2000. Each of those definitions contains the normal workday schedule for the corresponding year.
The Calendar facility also allows the definition of varied work periods throughout the year, in special calendars called periodic calendars. A calendar definition needs to be defined only once. Once defined, the definition is saved and used as necessary for scheduling. Calendar definitions can be modified or deleted as required. Any number of calendar members can be defined. Calendar members are stored in calendar libraries (partitioned datasets). Generally, one calendar library is defined at time of installation, and referenced by DD statement DACAL. Note The IOA Calendar facility does not support members which have been compressed using the ISPF PACK option.
2 151
Online Facility: IOA Calendar Facility General
Accessing the Calendar Facility

The Calendar facility contains the following screens: Calendar Facility entry panel Calendar List screen Year List screen Calendar Definition screen Allows specification of parameters which determine which record(s) will be displayed in subsequent screens. Displays the list of calendar members in the specified calendar library. Displays the list of years for which there is a calendar definition in the selected calendar member. Displays the parameters of the selected calendar for the selected year. This is the main screen of the facility.
To enter the Calendar facility, select Option 8 in the IOA Primary Option menu. The Calendar Facility entry panel is displayed. Depending on the values specified in the entry panel, you can bypass the Calendar List screen and/or the Year List screen.
2 152
Online Facility: IOA Calendar Facility Entry Panel
Entry Panel
The entry panel is displayed upon entering the Calendar facility (option 8 in the IOA Primary Option menu).
--------------------- IOA CALENDAR FACILITY - ENTRY PANEL ------------------(8) COMMAND ===>
SPECIFY LIBRARY, CALENDAR, YEAR LIBRARY ===> IOA.PROD.CAL CALENDAR ===> YEAR ===>
(Blank for calendar selection list) (Blank for year selection list)
USE THE COMMAND "SHPF" TO SEE PFK ASSIGNMENT
10.58.42

Fill in the following fields and press <ENTER>. LIBRARY Name of the desired calendar library. Mandatory. If this field is specified without filling in the CALENDAR field, the list of calendars in the specified library is displayed in the Calendar List screen. CALENDAR Name of the desired calendar member. Optional. If this field is specified without filling in the YEAR field, the list of years in the specified calendar member is displayed in the Year List screen. YEAR Year of the desired calendar definition. Optional. This field can be specified only if a CALENDAR value is also specified. If specified, the calendar definition is displayed in the Calendar Definition screen.
2 153
Online Facility: IOA Calendar Facility Calendar List Screen
Calendar List Screen

The Calendar List screen displays a list of calendars (members) in the specified library. This screen can be entered directly from the entry panel or upon exiting the Year List screen. By default, only calendar names are listed in the screen. However, if the default has been modified at time of installation, statistical information is displayed for each calendar name (as shown in the following screen below).
CALENDARS IN LIB IOA.PROD.CAL ------------(8.D) COMMAND ===> SCROLL===> CRSR OPT NAME ------------ VV.MM CREATED CHANGED SIZE INIT MOD ID BANKDAYS 01.00 98/06/30 98/06/30 09:50 104 104 0 IOAPROD DAYSOFF 01.00 98/06/30 98/06/30 09:50 30 30 0 IOAPROD HOLIDAYS 01.00 98/06/30 98/06/30 09:50 15 15 0 IOAPROD PERIOD1O 01.00 98/06/30 98/06/30 09:50 45 45 0 IOAPROD SPDAYCLN 01.01 98/11/25 98/11/25 17:43 26 26 0 L3051 SPMONCLN 01.01 98/06/30 98/11/26 15:00 117 104 0 M16A SPWEKCLN 01.01 98/06/30 98/11/26 15:10 117 104 0 M16A STOCKDAY 01.00 98/06/30 98/06/30 09:50 45 45 0 IOAPROD WORKDAYS 01.01 98/11/25 98/11/25 17:43 26 26 0 L3051 ======= >>>>>>>>>>>>>>>> NO MORE CALENDARS IN LIBRARY <<<<<<<<<<<<<<<< ======
OPTIONS:
S SELECT
B BROWSE
D DELETE
13.54.14
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) on the Calendar list. To return to the entry panel, press END (PF03/PF15).
Options of the Calendar List Screen

To request one of the following options, specify the option in the OPT field to the left of the calendar name(s), and press <ENTER>. S SELECT Display the list of years for the calendar for any purpose, including editing/modification. Only one calendar can be selected at a time. Display the list of years for the calendar for browsing. Only one calendar can be selected at a time. Delete the calendar (member) from the library. Multiple calendars can be selected.
B BROWSE D DELETE
2 154
Online Facility: IOA Calendar Facility Year List Screen
Year List Screen

This screen displays the list of years for which a specified calendar is defined. This screen can be entered directly via the entry panel or the Calendar List screen, or upon returning from the Year Definition screen. Note If the S (Select) option was specified in the Calendar List screen for a calendar which is currently in use (selected) by another user, either the Year List screen is not displayed and the Calendar List screen remains displayed (the default), or the Year List screen is displayed in Browse mode (if a User profile definition overrides the default). In either case, an appropriate message is displayed.
If a calendar description was defined in the Calendar Definition screen, the definition is displayed to the right of the year.
LIST OF YEARS IN IOA.PROD.CAL CALENDAR WORKDAYS COMMAND ===> SCROLL===> CRSR OPT NAME --------------------------------------------------------------------1997 REGULAR WORKING DAYS IN 1997 1998 REGULAR WORKING DAYS IN 1998 1999 REGULAR WORKING DAYS IN 1999 ======= >>>>>>>>>>>>>>>> NO MORE YEARS IN CALENDAR <<<<<<<<<<<<<<<< =====
OPTIONS:
S SELECT
D DELETE
I INSERT
W INSERT BY WEEK DAYS
08.52.54
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) in the Year list. To return to the Calendar List screen press END (PF03/PF15).
2 155
Online Facility: IOA Calendar Facility Year List Screen
Options of the Year List Screen

To request one of the following options, specify the option in the OPT field to the left of the year and press <ENTER>. Note If the Year List screen is displayed in Browse mode, options D (Delete) and I (Insert) and W (Insert By Week Days) are not available. Display the Calendar Definition screen for the specific year. Parameters can be edited and updated only if the Calendar Definition screen is not displayed in Browse mode. If the Calendar Definition screen is displayed in Browse mode, the screen can only be browsed and parameters cannot be modified. D DELETE I INSERT Delete the calendar definition for the specified year. Insert a new year in the Year List screen and display the Calendar Definition screen with a predefined year definition for editing. The predefined calendar definition will be defined with the same dates as the year by which the I (Insert) request was specified. For more information, see Inserting a New Year below.
SELECT
W INSERT BY WEEK DAYS Insert a new year in the Year List screen and display the Calendar Definition screen with a predefined year definition for editing. The predefined year definition will be defined with the same days of the week as the year by which the W (Insert by Week Days) request was specified. For more information, see Inserting a New Year below.
Inserting a New Year

All calendar definitions identified in the same Year list usually have the same fixed scheduling pattern. Often, this scheduling pattern is entirely based on either dates within a month or on days of the week within the month. For example:
Calendar QUARTERLY might always indicate scheduling for the last day of March, June, September and December (i.e., scheduling pattern based on dates). Calendar WEEKEND might always indicate scheduling all Saturdays and/or Sundays in each month (i.e., scheduling pattern based on days of the week).
This scheduling pattern also applies to new calendar definitions resulting from the insertion of a new year in the Year List screen. When a year is inserted in the Year list, the IOA Calendar facility automatically generates a calendar definition for the new year based on the scheduling pattern of the calendar by which the insert request was specified. This frees the user from having to manually define the new calendar. This automatically generated calendar definition is displayed and can be modified.
2 156
Online Facility: IOA Calendar Facility Calendar Definition Screen
In calendar definitions, scheduling date is described by both the date (month and day) and the day of the week. Because a particular date usually falls on a different day of the week in different years, it is necessary to indicate whether the scheduling pattern is based on the date or on the days of the week. This is indicated via the specified insert option:
To define the calendar with the same scheduling dates (although corresponding days of the week may vary, e.g., calendar QUARTERLY described above), specify option I (INSERT). To define the calendar so that jobs are scheduled on the same weekdays as in the previous calendar (although the corresponding dates may vary, e.g., calendar WEEKEND described above), specify option W (INSERT BY WEEK DAYS). If the scheduling pattern is mixed (e.g., calendar HOLIDAYS always indicates scheduling on both January 1 and the first Monday in September), specify the more appropriate option and correct the new calendar definition manually.
Calendar Definition Screen

This screen is used to define, display and modify dates in a calendar for a specific year. This screen can be entered directly from the entry panel or from the Year List screen.
--------------------------- IOA CALENDAR - WEEKDAYS ----------------------(8.Y) COMMAND ===> SCROLL===> CRSR YEAR 1998 REGULAR WORKDAYS IN 1998 -----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 01 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y -----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 02 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y -----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 03 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y -----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 04 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y -----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 05 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y -----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 06 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y -----S-------------S-------------S-------------S-------------S-------------S--TYPE Y IN ALL THE EXECUTION DAYS 14.37.10
Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) in the calendar definition screen.
2 157
Fields of the Calendar Definition Screen A. YEAR Year of the calendar. This value can be modified. When modified, the values indicated for each date in each month (described below) are shifted to the appropriate day of the week. User-supplied free-text description of the calendar. Optional. To designate a calendar as periodic, reserved string ==PERIODIC== must be specified in the first 12 positions of the description field. Any text can be specified in the rest of the description field. (See Periodic Calendars below.) C. month/dates Each month of the year (01 12) of the calendar consists of the following: C1. C2. C3. C4. Separator line. Sunday (or Saturday) is marked S (according to the site-specified default). Month identifier (0112). Date identifier for the updatable field underneath. Updatable field for defining execution dates. Valid values: Y N or blank + Select the job on that date. Do not select the job for execution on that date. For a relative calendar, closest next date. For a relative calendar, closest previous date.
22
B. description
select the select the
22
Periodic Calendars
Some jobs must be scheduled periodically, according to schedules which are not easily expressed in terms of fixed days and dates within months. In these cases, monthly, or even yearly, scheduling definition is awkward. For example:
A payroll job needs to be scheduled every other Wednesday: In some months, the job may be scheduled on the first, third, and even fifth, Wednesday in the month. In other months, it may be scheduled on the second and fourth Wednesday in the month. In some years, the job may be scheduled beginning on the first Wednesday of the year. In other years, it may be scheduled beginning on the second Wednesday of the year.
22
A relative calendar is a calendar used in a formula to create other calendars. It cannot be specified in a DCAL/WCAL/CONFCAL field. See utility IOABLCAL in Section 9 of the IOA Administrator Guide for details.
2 158
A job must be scheduled every 25 days, regardless of date. Such a job will be scheduled on different dates each month and each year.
IOA allows definition of special calendars, called periodic calendars, for these scheduling requirements. To designate a calendar as periodic, reserved string ==PERIODIC== must be specified in the first 12 positions of the description field. Any text can be specified in the rest of the description field.
COMMAND ===> YEAR 1998 SCROLL===> CRSR ==PERIODIC== GENERAL WORK DAY CALENDAR
In a periodic calendar you cannot mark the days as Y and N. Instead, you mark them with a period identifier. A period identifier can be any letter from A to Z (except Y and N), any 23 number (0-9), or any other printable sign. Period identifiers do not have to be consecutive and they can overlap. A period in a periodic calendar can span more than one year.
-----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 12 A B A B A
Below is an example of a periodic calendar:

-----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 09 A A A A A A A A A A A B B B B B B B B B B -----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 10 C C C C C C C C C C C C C C C C C C C C C C
In the above calendar, period A starts on September 1st and ends on September 15th. Days which are not marked are non-working days (because they do not belong to any period in this calendar).
23
If you need more characters, use characters within the hexadecimal range 4A F9.
2 159
The following periodic calendar spans more than one year. Period A starts on December 13th and ends on December 21st, 1998. Period B starts on December 14th, 1998 and ends on January 7th, 1999.
-----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 12 A B A B A -----S-------------S-------------S-------------S-------------S-------------S---
-----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 01 B B -----S-------------S-------------S-------------S-------------S-------------S---
If the number of days between periods with the same identifier is more than 33, it is 24 considered a new period. For example:
-----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 03 A B A B A -----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 04 B B -----S-------------S-------------S-------------S-------------S-------------S---
There are 34 days between the period B indicators of March 19th, 1999 and April 22nd, 1999. In this case, a new period begins on April 22nd, 1999. See parameters DAYS and WDAYS in Section 3 of this manual for a description of the use of periodic calendars.
24
To change the 33-day default, see your IOA administrator.
2 160
Deleting Calendars
To delete calendars, specify option D (Delete) by the calendar names in the Calendar List screen and press <ENTER>. The following confirmation window is displayed, in sequence, for each calendar selected for deletion.
CALENDARS IN LIB IOA.PROD.CAL ------------(8.D) COMMAND ===> +--------------------------+ SCROLL===> CRSR OPT NAME --| CONFIRM DELETE OPTION | E INIT MOD ID D BANKDAYS <-----------| (Y/N) | 4 104 0 IOAPROD DAYSOFF +--------------------------+ 0 30 0 IOAPROD HOLIDAYS 01.00 98/06/30 98/06/30 09:50 15 15 0 IOAPROD PERIOD1O 01.00 98/06/30 98/06/30 09:50 45 45 0 IOAPROD D SPDAYCLN 01.01 98/11/25 98/11/25 17:43 26 26 0 L3051 SPMONCLN 01.01 98/06/30 98/11/26 15:00 117 104 0 M16A SPWEKCLN 01.01 98/06/30 98/11/26 15:10 117 104 0 M16A STOCKDAY 01.00 98/06/30 98/06/30 09:50 45 45 0 IOAPROD WORKDAYS 01.01 98/11/25 98/11/25 17:43 26 26 0 L3051 ======= >>>>>>>>>>>>>>>> NO MORE CALENDARS IN LIBRARY <<<<<<<<<<<<<<<< ======
OPTIONS:
S SELECT
B BROWSE
D DELETE
13.54.14
Specify Y (Yes) in the window to delete the calendar. Specify N (No) in the window to cancel the delete request. If PDSMAN is operational at your site, $$$SPACE members will not be deleted.
Note
For each calendar deleted, a message is written to the IOA Log file.
2 161
Online Facility: IOA Calendar Facility Exiting the IOA Calendar Facility
Exiting the IOA Calendar Facility

When exiting the Calendar facility, screens are exited in the following sequence:
Calendar Definition screen Year List screen Calendar List screen Note If the Calendar List screen was bypassed as you entered the Calendar facility (i.e., if you specified a CALENDAR value in the entry panel), the Calendar List screen is not displayed upon exiting the Year List screen; instead, the entry panel is displayed.
Calendar Facility entry panel
The commands and options available when exiting screens depend on the screen being exited and on whether on not changes have been made. If changes have been made, the selected exit options and commands will determine whether or not the changes will be saved. Exit options and commands are discussed below on a screen by screen basis.
Exiting the Calendar Definition Screen

Use any of the following commands, or press the corresponding PFKey, to exit the Calendar Definition screen: CANCEL Cancel the changes made to the calendar definition and return to the Year List screen.
Note
The following exit commands retain changes to the calendar definition in memory. To permanently save the changes to disk, you must also request that the changes be saved when you exit the Year List screen. Keep changes to the calendar definition in memory and exit to the Year List screen. Keep changes to the calendar definition in memory and display the next calendar definition in the Year list. Keep changes to the calendar definition in memory and display the previous calendar definition in the Year list.
END (PF03/PF15)/ NEXTYEAR (PF11/PF23) PREVYEAR (PF10/PF22)
2 162
Online Facility: IOA Calendar Facility Exiting the IOA Calendar Facility
Exiting the Year List Screen

Press END (PF03/PF15) to exit the Year List screen. If changes made to at least one calendar definition have been kept in memory (see Exiting the Calendar Definition Screen) and/or if any changes have been made to the Year List screen, the Exit Option window is displayed.
LIST OF YEARS IN IOA.PROD.CAL CALENDAR WORKDAYS COMMAN +-----------------------------------------------------------+ ===> CRSR OPT N | PLEASE SELECT EXIT OPTION | --------1 | | 1 | SAVE CREATE | 1 | | ====== | LIBRARY IOA.PROD.CAL | << ===== | TABLE WORKDAYS | | | +-----------------------------------------------------------+
OPTIONS:
S SELECT
D DELETE
I INSERT
W INSERT BY WEEK DAYS
08.53.50
Fill in the Exit Option window as follows: The LIBRARY and TABLE (member) fields indicate the library and member in which the calendar definitions will be saved. The specified values can be modified (e.g., to save the calendar definitions in a different member).
To save all changes currently in memory and exit the Year List screen, specify Y (Yes) after the word SAVE or CREATE: Specify Y after the word SAVE if a member with the same calendar name already exists in the specified library. Specify Y after the word CREATE if a member with the same calendar name does not exist in the specified library. If you create a new calendar member, the member name does not appear in the Calendar List screen upon exiting the Year List screen; it first appears when you reenter the Calendar List screen from the entry panel.
Note
To cancel changes currently in memory and exit the Year List screen, specify N (No) after the word SAVE or CREATE. To close the Exit Option window and remain in the Year List screen (with the changes remaining in memory), press RESET (PF04/PF16).
Exiting the Calendar List Screen

Press END (PF03/PF15) to exit the Calendar List screen.

Press END (PF03/PF15) to exit the entry panel.
2 163
Online Facility: Utilities Under ISPF General
Utilities Under ISPF

General
Several IOA facilities can only be activated under ISPF. To activate these facilities, select option 6 on the IOA Primary Option menu (under ISPF) or activate CLIST IOAUTIL from the TSO Command Processor. The IOA Online Utilities menu is displayed.
IOA Online Utilities Menu

Depending on the IOA products available at your site, different online utility options are displayed. The IOA Online Utilities menu below is displayed when CONTROL-M and CONTROL-R are available at your site.
------------------------------ ON-LINE UTILITIES -----------------------------OPTION ===> USERID - M21 TIME - 18:06 TERMINAL - 3278 I1 M1 M2 M3 M4 M5 M6 R1 R2 R3 R4 U1 X PREREQ CONDITION JOB ORDER ISSUE AUTOEDIT SIMUL SIMUL/TAPE PULL PARAM PROMPTING QUICK SCHEDULE USER INTERFACE CONTROL-R SIMUL DATASET CLEANUP JOB DATASET LIST STANDALONE DOCU/TEXT EXIT Add/Check/Delete a Prerequisite Condition Issue a Job Order Perform an AutoEdit Simulation Prepare Simulation/Tape Pull List Job Parameter Prompting Facilities Quick Schedule Definition End-User Job Order Interface CONTROL-R Simulation CONTROL-R Dataset Cleanup Prepare a Job Dataset List CONTROL-R Standalone Invoke DOCU/TEXT
- Exit This Menu
Note
The IOA administrator can remove user authority to access option 6 on the IOA Primary Option menu. In this case, the IOA Online Utilities menu is not displayed.
2 164
Online Facility: Utilities Under ISPF IOA Online Utilities Menu
The IOA Online Utilities menu below is displayed when all IOA products are active.
------------------------------ ON-LINE UTILITIES -----------------------------OPTION ===> USERID - N25 TIME - 16:28 TERMINAL - 3278 D1 D2 D3 D4 I1 M1 M2 M3 M4 M5 M6 R1 R2 R3 R4 T1 U1 X DECOLLATING PRINT BACKUP/MIGRATION RESTORE PREREQ CONDITION JOB ORDER ISSUE AUTOEDIT SIMUL SIMUL/TAPE PULL PARAM PROMPTING QUICK SCHEDULE USER INTERFACE CONTROL-R SIMUL DATASET CLEANUP JOB DATASET LIST STANDALONE CONTROL-T SIMUL DOCU/TEXT EXIT Schedule a Report Decollating Mission Schedule a Printing Mission Schedule a Backup/Migration Mission Schedule a Restore Mission Add/Check/Delete a Prerequisite Condition Issue a Job Order Perform an AutoEdit Simulation Prepare Simulation/Tape Pull List Job Parameter Prompting Facilities Quick Schedule Definition End-User Job Order Interface CONTROL-R Simulation CONTROL-R Dataset Cleanup Prepare a Job Dataset List CONTROL-R Standalone Simulate CONTROL-T Rules Invoke DOCU/TEXT Exit This Menu
CONTROL-M, IOA and most CONTROL-R utility options (beginning M, R, I and U) are described on the following pages. For the descriptions of other utilities on the menu, see the user manuals of the relevant products. Notes CONTROL-R utility option R4 is described under Operating CONTROL-R in Standalone Mode in Section 1 of the CONTROL-R User Manual. The DOCU/TEXT utility (option U1) is available only at sites which have installed DOCU/TEXT Specify the desired option number in the OPTION field and press <ENTER>.. Online utility screens utilize standard ISPF profile capabilities. Quick transfer to a utility can be performed by specifying =opt from another utility screen, or =6.opt from a non-utility screen (e.g., IOA Log screen), where opt is the option on the IOA Online Utilities menu. Examples =M1 =6.M1 Transfers control to the Job Order Issue utility from another utility. Transfers control to the Job Order Issue utility from the Table List screen.
2 165
Online Facility: Utilities Under ISPF I1: Add/Check/Delete a Prerequisite Condition
I1: Add/Check/Delete a Prerequisite Condition

This utility adds prerequisite conditions to, checks the existence of prerequisite conditions in, and deletes prerequisite conditions from, the IOA Conditions/Resources file. The utility screen (below) can be displayed in the following ways:
Select option I1 in the Online Utilities menu. Activate CLIST IOACCND from the TSO Command Processor.
----------------------COMMAND ===> PREREQUISITE CONDITION UTILITY ----------------------
FUNCTION CONDITION NAME
===> ADD ===> SALARY_RPT_OK
(ADD/CHECK/DELETE) (Up to 20 characters)
Enter either date or STAT: CONDITION DATE ===> STAT (DDMM OR STAT)
ENTER YES TO CONTINUE
===> YES
To activate the utility, fill in the following fields and press <ENTER>: FUNCTION Function to be performed. Valid values are: ADD CHECK DELETE CONDITION NAME CONDITION DATE Add the specified condition Conditions/Resources file. to the IOA
Check if the specified condition exists in the IOA Conditions/Resources file. Delete the specified condition Conditions/Resources file. from the IOA
Name of the prerequisite condition (1 20 characters) to be added, checked, or deleted. 4-character date associated with the specified condition. Valid values: date STAT Valid date in mmdd or ddmm format, depending on the site standard. Static. Value assigned to conditions which are not date-dependent (e.g., DATABAS-OK).
2 166
Online Facility: Utilities Under ISPF M1: Issue a Job Order
ENTER YES TO CONTINUE Confirmation field to help prevent the unintentional addition or deletion of a condition. When blank, the operation is not performed. Specify YES to add, check, or delete the condition. To exit the screen without activating the utility, press PF03/PF15.
M1: Issue a Job Order

This utility is used to issue manual job orders. Although most job orders are requested by User Daily jobs which are automatically submitted by CONTROL-M, it is sometimes necessary to issue a job order manually. Two situations in which manual job orders may be desirable are:
To order an ad hoc job. To issue a job order for a different working date. For example: To reschedule a job run from the 1st of the next month to the 30th of this month. To reschedule the run of an entire scheduling table from the 4th of the month to the 5th of the month because all job runs in the table must be performed again.
The utility screen (below) is displayed in the following ways:
Select option M1 on the Online Utilities menu. Activate CLIST CTMJOBRQ from the TSO Command Processor.
---------------------------COMMAND ===> JOB REQUEST UTILITY ----------------------------
SCHEDULING LIBRARY TABLE NAME JOB NAME SCHEDULED RUN DATE FORCED SCHEDULING ENTER YES TO CONTINUE GROUP CALENDAR LIBRARY
===> CTM.PROD.SCHEDULE ===> ===> ===> 06 06 98 ===> NO ===> ===> ===> IOA.PROD.CAL (Optional) (* for all jobs) (ODATE - format MM DD YY) (YES,NO)
To activate the utility, fill in the following fields and press <ENTER>: SCHEDULING LIBRARY TABLE NAME Name of the scheduling library containing the table/job(s) to be scheduled. Scheduling table (member) name.
2 167
Online Facility: Utilities Under ISPF M2: Perform Online AutoEdit Simulation
JOB NAME SCHEDULED RUN DATE FORCED SCHEDULING
Name of the job to be scheduled. An asterisk (*) can be specified to order all jobs in the table. Original scheduling date of the job(s). Defaults to the current working date. Determines whether or not the job(s) should be forced. Valid values are: Y (YES) Schedule the job(s) even if the requested date is not a scheduling date for the job according to its Basic Scheduling parameters. Schedule the job(s) only if the requested date satisfies the jobs Basic Scheduling criteria. Jobs in Group scheduling tables must be forced. Merely ordering them is not sufficient.
N (NO)
Note
ENTER YES TO CONTINUE Confirmation field to help prevent the job(s) from being unintentionally run. When blank, the job(s) will not run. Specify YES to enable the job run. GROUP CALENDAR LIBRARY If specified, only jobs belonging to the specified group (in the specified table) will be scheduled. Name of the calendar library (if used) for scheduling the job(s).
To exit the screen without activating the utility, press PF03/PF15.
M2: Perform Online AutoEdit Simulation

This utility checks AutoEdit control statement syntax in jobs. It is essential that the syntax of AutoEdit control statements be checked while the member is being prepared. Otherwise, CONTROL-M may detect an AutoEdit syntax error during job submission in the production environment and cancel the submission. The utility can be initiated either online (through this screen) or via batch procedure CTMAESIM. For more information, see Testing AutoEdit Syntax in Section 5 of this manual. To activate the utility online, display the utility screen in either of the following ways:
Select option M2 on the Online Utilities menu Activate CLIST CTMCAES from the TSO Command Processor
Utility CTMCAES can operate in either JCL Library mode or Scheduling Library mode: In JCL Library mode, the utility checks the AutoEdit statements in the jobs JCL. In Scheduling Library mode, the utility not only checks the AutoEdit statements in the jobs JCL, it also checks the impact that SET VAR statements in the job scheduling definition have on the jobs JCL.
2 168
This facility simulates the actions of the CONTROL-M submission mechanism and produces a printed report of the process. The output of the simulation process is a standard print file containing:
Input control statements Log messages of the submission process Actual lines that will be submitted under the same conditions During AutoEdit simulation, some variables may not contain valid or expected values. For example, %%$TAG will always be blank and %%ORDERID will be ZZZZZ.
------------------- PERFORM CONTROL-M AUTOEDIT SIMULATION --------------------COMMAND ===> SPECIFY JCL LIBRARY OR SCHEDULE LIBRARY INFORMATION JCL LIBRARY MODE: JCL LIBRARY MEMBER NAME OWNER APPLICATION NAME GROUP NAME SCHEDULING LIBRARY MODE: SCHEDULING LIBRARY TABLE NAME JOB NAME PARAMETER LIBRARY WDATE ODATE FUNCTION
Note
===> CTM.PROD.JCL ===> BRCCIND ===> M21 ===> ===> ===> ===> ===> ===> ===> ===> ===> CTMP.PROD.PARM 09 09 98 (DD MM YY) 09 09 98 (DD MM YY) LIST (LIST/SUBSCAN/SUBMIT)
Enter YES to continue
===>
The submission simulation utilizes control statements which are written to DD statement DASIM. These control statements are based on the parameters described below. Depending on the mode in which the utility operates, either JCL Library mode or Scheduling Library mode parameters (but not both) must be specified. In addition, General simulation parameters should also be specified. To activate the utility, fill in the parameters and press <ENTER>.
2 169
JCL Library Mode Parameters JCL LIBRARY MEMBER NAME OWNER APPLICATION NAME GROUP NAME Name of the JCL library from which the required JCL is to be submitted by the AutoEdit simulation. Name of the JCL member to be submitted by the AutoEdit simulation. User ID of the jobs owner. Name of the application as specified in field APPL in the job scheduling definition. Name of the group to which the job belongs.
Scheduling Library Mode Parameters SCHEDULING LIBRARY TABLE NAME JOB NAME Notes Name of the library containing the job scheduling definition. Name of the scheduling table containing the job scheduling definition. Name of the job scheduling definition.
When specifying Scheduling Library Mode parameters, values for owner, application name, and the jobs JCL library and member are not specified because the utility takes these values directly from the specified job scheduling definition. The name of the JCL member is obtained from the OVERLIB parameter (if specified) instead of the MEMLIB member.
General Parameters PARAMETER LIBRARY WDATE ODATE FUNCTION Name of the library which contains the member(s) referenced by AutoEdit statement %%GLOBAL. Working date of the job. Original scheduling date of the job. Function to be performed by the simulation. Valid values are: LIST The utility simulates submission of the member from the designated library using the specified date and user ID parameters. CONTROL-M checks the JCL. The output is displayed on the terminal. The JCL is not actually submitted. CONTROL-M attempts to resolve the AutoEdit statements. If successful, the JCL member lines are also written to the file referenced by DD statement DASUBMIT and the member is submitted by the utility for execution. In this case, MVS also checks the JCL. This option can also be used to submit jobs when the CONTROL-M monitor is not active (e.g., if there is a severe technical problem).
SUBMIT
2 170
SUBSCAN
This function is similar to SUBMIT except that it adds a TYPRUN=SCAN parameter to the job card before performing simulation. As a result, the job is submitted and the JCL is checked by MVS but the job is not executed. This option is available at sites where product JOB/SCAN is installed, but only if the utility is activated from the Online Utilities menu. (This option is not displayed and cannot be used if the utility is activated via a CLIST or batch procedure.) This function is similar to SUBMIT except that if CONTROL-M finds no JCL errors, JCL is checked by the JOB/SCAN product before it is written to the file referenced by DD statement DASUBMIT.
JOBSCAN
Confirmation field to help prevent the simulation job(s) from being unintentionally run. When blank, the job(s) will not run. Specify YES to enable the job run.
To exit the screen without activating the utility, press PF03/PF15.
2 171
Online Facility: Utilities Under ISPF M3: Prepare Simulation/Tape Pull List Job
M3: Prepare Simulation/Tape Pull List Job

This screen is used to activate the Simulation procedure or the Tape Pull List procedure. The screen can be displayed in the following ways:
Select option M3 from the Online Utilities menu Activate CLIST CTMCSIM from the TSO Command Processor
------- CONTROL-M SIMULATION AND FORECASTING FACILITY AND TAPE PULL LIST ----COMMAND ===> RUN SIMULATION From Until ON Todays-current AJF Another day - DATE Create new AJF Order daily jobs Keep output AJF,RES Parameters member REPORTS Jobs left Night schedule TAPE PULL LIST Report by VOLSER Report by TIME Report by JOBNAME Report by DSN Parameters member ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> Y 9805050900 9805051600 Y N N Y SIMPARM Y Y (Y-to run, N-skip to reports) (Format YYMMDDhhmm) (Format YYMMDDhhmm) (Y/N If "N", fill in the date) (DD MM YY) (Y/N) (Y/N) (Y/N) (Simulation parameters) (Y/N) (Y/N)
N (Y/N) INVOKE JOBSCAN Y (Y/N) JCL Checking Y (Y/N) Errors Only N (Y/N) Space Report N (Y/N) TAPULPRM (Tape pull parameters) ===> YES or END key to EXIT
===> Y ===> N ===> Y
(Y/N) (Y/N) (Y/N)
The Simulation facility simulates the actions of the CONTROL-M monitor under the conditions specified in the simulation parameters. Online simulation is performed in the CPU without updating the simulation input files, or without performing any other I/O. Note At sites supporting the JOB/SCANDOCU/TEXT Interface, the lower portion of the Simulation screen is modified to contain the INVOKE JOBSCAN parameters.
The Tape Pull List procedure creates a list of all tapes to be mounted in a specified period, taking into account the expected order of job execution and the order of creation of tape datasets. The list can be sorted and edited in various ways. This utility also provides the following benefits:
It checks the syntax of all AutoEdit statements in all jobs which are planned for the given period. It checks the JCL syntax. It produces a list of datasets which are not available. These are usually input datasets due to arrive, but they may indicate JCL errors. (See CTMRNSC: Night Schedule Report in Section 8 of this manual.)
2 172
Note
For the Tape Pull List procedure to execute properly, authority must be granted for the submission of jobs to the internal reader (INTRDR).
For more information about Simulation and Tape Pull List procedures, see Section 7 of this manual. To activate this online utility, fill in the following fields and press <ENTER>: RUN SIMULATION Whether or not to run the simulation. Valid values are: Y (Yes) Run the simulation. The results of the simulation run are kept in the Log file and the Active Jobs file (AJF) and can be used for producing reports and/or the tape pull list. Do not run the simulation. Use the results of a prior simulation to produce reports and/or the tape pull list.
N (No) From Until ON
Simulation start date and time (yymmddhhmm). Simulation end date and time (yymmddhhmm).
Todays-current AJF Whether or not to use todays data (i.e., the data currently in the Active Jobs file) as input for the simulation. Valid values are: Y (Yes) Use todays data. In this case, it is recommended to run the simulation after todays jobs have been placed on the Active Jobs file via New Day processing. Use data from the Another Day DATE. date specified in field
N (No)
Another day DATE Date to use for scheduling/ordering simulation jobs. Format ddmmyy, mmddyy, or yymmdd, depending on the site standard. A valid date must be specified when not using todays data (i.e., if N is specified in field Todays-current AJF). Create new AJF Whether or not to allocate a new Active Jobs file to contain new jobs for the simulation. Valid values are: Y (Yes) Allocate a new Active Jobs file. This value must be specified when not using todays data (i.e., if N is specified in field Todays-current AJF). Do not allocate a new Active Jobs file. This value should be specified when using todays data (i.e., if Y is specified in field Todays-current AJF).
N (No)
2 173
Order daily jobs
Whether or not to load into the new Active Jobs file all the jobs which are scheduled to execute on the specified date. Valid values are: Y (Yes) Load the jobs into the Active Jobs File. A User Daily step will be entered into the job. This step will schedule all the jobs based on their basic scheduling criteria. (It is the users responsibility to ensure that the Table list for this job is up-to-date.) This value must be specified when not using todays data and when creating a new Active Jobs file (i.e., if N is specified in field Todays-current AJF and Y is specified in Create new AJF). N (No) Do not load the jobs into the Active Jobs File. This value is generally specified when using todays data or when not creating a new Active Jobs file (i.e., if Y is specified in field Todays-current AJF or N is specified in field Create new AJF). When N is specified in Create new Active Jobs File, the simulation can still be run again (e.g., the simulation can be rerun with different simulation criteria, such as a different number of tape drives).
Keep output AJF,RES Specifies whether or not to save the output Active Jobs file and Conditions/Resources file (i.e., the files as they appear at the end of the simulation). The output files should be kept if you plan to produce reports (e.g., Jobs Left report) based on these files. Valid values are: Y (Yes) N (No) Keep the output files. Do not keep the output files.
Parameters member Name of the member in the CONTROL-M PARM library which contains the simulation parameters. This member must contain parameter INTERVAL, but it also can contain other parameters (e.g., ADD COND). REPORTS Reports to be produced. Valid values for each report are Y (Yes) or N (No). If Y is specified the report is generated. If N is specified the report is not be generated. This part of the panel is often site-modified. A description of the reports available by default is provided. Jobs left If Y is specified, produces a report that lists the jobs that did not end OK by the end of the simulation (jobs in status WAIT SCHEDULE, EXECUTING, ENDED NOTOK, etc.). This report is identical to KeyStroke Sample report REP3LEFT in the IOA Sample library. If Y is specified, produces a report that provides a job execution time summary. (See CTMRNSC: Night Schedule Report in Section 8 for more information.)
Night schedule
2 174
TAPE PULL LIST
Specifies whether or not to run the Tape Pull List procedure. The accompanying Report by fields specify whether or not to generate the particular Tape Pull reports. Valid values for this field and the accompanying fields are Y (Yes) and N (No). Y (Yes) N (No) Run the procedure (or report). Do not run the procedure (or report).
A description of available Tape Pull reports follows. Report by VOLSER If Y is specified, produces a report sorted by volume serial number (this includes all tapes from the tape library). Report by TIME If Y is specified, produces a report sorted by the expected mount time.
Report by JOBNAME If Y is specified, produces a report sorted by job name. Report by DSN If Y is specified, produces a report sorted by dataset name.
Parameters member Name of the member in the CONTROL-M PARM library which contains the Tape Pull parameters. This member must contain parameter INTERVAL, but it also can contain other parameters (e.g., ADD COND). INVOKE JOBSCAN These parameters apply only if the JOB/SCAN-DOCU/TEXT Interface is installed at your site. Valid values for the accompanying fields are Y (Yes) or N (No). Only one Y value can be specified. Y (Yes) JOBSCAN is invoked, the check is performed, and the appropriate report is displayed in the utility output. The specified check is ignored.
N (No) JCL Checking
If Y is specified, checks the JCL specified in the member referenced by DD statement DAJCLOUT for errors and checks for adequate DASD disk space allocation. If Y is specified, checks for JCL errors only. If Y is specified, checks for adequate DASD disk space allocation only.
Errors Only Space Report
Enter YES to continue This field helps prevent the simulation or tape pull list job(s) from being unintentionally run. When blank, the job(s) will not run. Specify YES to enable the job run. The file of the simulation job as tailored to your specifications will be displayed in ISPF EDIT. You can submit it, save it for future use, etc. To exit the screen without activating either facility, press PF03/PF15.
2 175
Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities
M4: Parameter Prompting Facilities

CONTROL-M Parameter Prompting facilities provide an automatic online interface for assigning AutoEdit parameter values. These facilities prompt the user for values requiring manual modification. These facilities eliminate the need to remember which AutoEdit parameters require assignment each day, the location of AutoEdit members, and the manual conditions which need to be added (Screen 7). To display the Parameter Prompting entry panel (below), select option M4 on the Online Utilities menu.
------------------- CONTROL-M PARAMETER PROMPTING ----------------------------OPTION ===> USERID - M14 TIME - 21:05 TERMINAL - 3278
1 2
CTMCFMNU CTMCAMNU
Parameter Prompting Facility - TYPE 1 Parameter Prompting Facility - TYPE 2
EXIT
Terminate this menu
Two different prompting facilities are available:
Parameter Prompting facility TYPE 1 Parameter Prompting facility TYPE 2
Using these facilities requires a basic understanding of JCL, the AutoEdit facility, and the concept of prerequisite conditions. After reviewing these pages, select the Parameter Prompting facility which best suits your environment.
2 176
Parameter Prompting Facility (Type 1)

After selecting option 1 of the CONTROL-M Parameter Prompting entry panel, the following screen is displayed:
------ CONTROL-M - PARAMETER PROMPTING FACILITY (TYPE 1) PRIMARY MENU ------(P) OPTION ===>
DEFINE PARAMETERS AND CREATE A NEW MASTER TABLE
UPDATE PARAMETERS AND SET CONDITIONS
PARAMETER DESCRIPTION WILL BE DISPLAYED CONTROL-M FILES PREFIX ===> IOA.PROD
===> YES
(YES/NO)
ENTER
END
COMMAND OR
PF3
TO TERMINATE
Note
You can enter this screen directly by activating CLIST CTMCFMNU.
This screen displays the following options: 1. Define Parameters and Create a New Master Table This option defines groups of parameters. The definition and association with any prerequisite condition is performed only once per parameter. 2. Update Parameters and Set Conditions This option is accessed daily (or multiple times in one day) to assign values to parameters and set prerequisite conditions. The Parameters Description field (A) applies to option 2 of this screen and will be explained later in this section. The CONTROL-M files Prefix (B) used at your site appears as a default. Files with this prefix are accessed by the Parameter Prompting facility to add prerequisite conditions. Usually, there is no need to change the value of this field.
2 177
Option 1: Define Parameters and Create a New Master Table

After selecting option 1 of the Parameter Prompting facility (Type 1) Primary menu, the following screen is displayed:
---- CONTROL-M - P.P.F. - DEFINE PARAMETERS AND CONDITIONS ---------------(P.1) COMMAND ===> TABLE NAME PREFIX ===> LIBRARY ===> CTM.PROD.PROMPT
Please fill in the Table Name Prefix and press ENTER ENTER END COMMAND OR PF3 TO TERMINATE
Fill in a Table Name Prefix (a maximum of three characters) and press <ENTER>. A Master table is usually defined for a group of AutoEdit parameters controlled by one person/project. The library in which the prompting tables will be placed appears as a default and can be changed. This is usually a different library than the scheduling tables library.
2 178
If the table does not exist (i.e., you are attempting to define a new table), the following screen is displayed:
---- CONTROL-M - P.P.F. - MASTER TABLE DEFINITION ----------------------(P.1.2) COMMAND ===> CTMB14E MASTER TABLE TAPTMSTR WAS NOT FOUND. YOU MAY CREATE IT, OR EXIT TABLE NAME PREFIX ===> TAP DESCRIPTION LIBRARY ===> EXTERNAL TAPE DATA ===> CTM.PROD.PROMPT
Please fill in the Table Description and press ENTER
ENTER
END
COMMAND OR
PF3
TO TERMINATE
You can create a new table or exit the screen. To create a new table, enter a table description and press <ENTER>.
2 179
Define Parameters and Conditions Screen After creation of a new table, or if the table exists, the following screen is displayed. If the table exists, the previously defined parameters and associated conditions are displayed for modification.
---- CONTROL-M - P.P.F - DEFINE PARAMETERS AND CONDITIONS -------- ROW 1 OF 2 COMMAND ===> SCROLL ===> PAGE PARM PREFIX ===> TABLE NAME : TAPTMSTR -------------------------------------------------------------------------------_ PARM ===> IRS_TAPE CONDITION ===> IRS-TAPE-ARRIVED VALUE ===> DESC. ===> WEEKLY TAPE FROM IRS --------------------------------------------------------------------------------_ PARM ===> A_BANK_TAPE CONDITION ===> MN-A-BANK-TAPE-READY VALUE ===> XXXX DESC. ===> TAPE FROM BANK GROUP A ****************************** Bottom of Data ********************************
This screen is used to define, display and modify parameters and optional prerequisite conditions which will be used for prompting on a daily basis. Specifying Retrieval Criteria The display of parameters can be limited to parameters beginning with a specific prefix by filling in the PARM PREFIX field (A). To display the first occurrence of a parameter at the top of a screen, use the line command L xxxx, where xxxx is a specific parameter or parameter prefix. Define Parameters and Conditions Screen Format The following information (B) can be defined, displayed, or modified for each parameter: PARM CONDITION Name of the AutoEdit parameter. Name of a prerequisite condition to be added to the IOA Conditions/Resources file when this parameter is updated. Optional. A default parameter value. Optional. A meaningful description of the parameter.
VALUE DESC
2 180
Define Parameters and Conditions Screen Options To request one of the following options, specify the option in the field (C) to the left of the word PARM and press <ENTER>. DELETE REPEAT ADD INSERT Delete a parameter from the table. Duplicate a parameter. Add a parameter (same as option R). Insert a new parameter in the table. INSERT typed on the Command line will insert a new parameter at the top of the table.
Changes made to a parameter are updated in the plan when you press <ENTER>. (Whether or not an option is specified.) Define Parameters and Conditions Screen How to Exit To exit the Define Parameters and Conditions screen, press END (PF03/PF15). If additions/modifications have been made, the following Save window is displayed:
---- CONTROL-M - P.P.F. - DEFINE PARAMETERS AND CONDITIONS -------------------COMMAND +-----------------------------------------------------------+ | PLEASE SELECT EXIT OPTION | | | | SAVE (Y/N) | | | | LIBRARY CTM.PROD.PROMPT | | TABLE TAP | | | +-----------------------------------------------------------+
Specify Y (Yes) to save the changes. Specify N (No) to cancel the changes.
2 181
Option 2: Update Parameters and Set Conditions

---- CONTROL-M - P.P.F. - TABLE SELECTION ----------------------- Row 1 FROM 3 COMMAND ===> SCROLL ===> PAGE TABLE PREFIX ===> ------------------------------------------------------------------------------_ TABLE NAME ===> BAK DATE ===> 09 / 09 LIBRARY : CTM.PROD.PROMPT DESCRIPTION: BACKUP CRITERIA _ TABLE NAME ===> REP DATE ===> 09 / 09 LIBRARY : CTM.PROD.PROMPT DESCRIPTION: REPORTING CRITERIA _ TABLE NAME ===> TAP DATE ===> 09 / 09 LIBRARY : CTM.PROD.PROMPT DESCRIPTION: EXTERNAL TAPE DATA ******************************** Bottom of Data *******************************
This screen displays a list of Daily Prompting tables available for update. A Daily table is a copy of a Master Table specific to a particular business day. It is accessed in order to assign values to (previously defined) parameters and to set conditions. The Daily table can be accessed multiple times on the same day. When you enter this screen, the current date is displayed for each Daily Table. You can overwrite the date to select a different date. To select a table, enter any character in the selection field (A) to the left of TABLE NAME and press <ENTER>. The display of tables can be limited to those tables beginning with a prefix of 1 to 3 characters by filling in the TABLE PREFIX field. To display the first occurrence of a table at the top of the screen, use the line command L xxxx, where xxxx is a specific parameter or parameter prefix (under the command line).
2 182
Update Parameters and Set Conditions Screen After table selection, the following screen is displayed:
---- CONTROL-M - P.P.F. - UPDATE PARAMETERS AND SET CONDITIONS --- Row 1 FROM 2 COMMAND ===> SCROLL ===> PAGE PARM PREFIX ===> TAPT1112 UPDATED ON ------------------------------------------------------------------------------_ VALUE ===> OF ===> IRS-TAPE WEEKLY TAPE FROM IRS _ VALUE ===> XXXX OF ===> A-BANK-TAPE 09 09 TAPE FROM BANK GROUP A ****************************** Bottom of Data ********************************
This screen displays a list of all AutoEdit parameters for which values can be entered. After a parameter value is updated on the screen, all changes are immediately saved in the Daily table. Any manual condition associated with this parameter prompt is added to the IOA Conditions/Resources file. Press END (PF03/PF15) to exit the screen. Update Parameters and Set Conditions Screen Format The following information is presented for each parameter: VALUE OF Description Default value of the parameter. This value can be modified. Parameter name. This description appears only if the value YES was specified in the PARAMETER DESCRIPTION WILL BE DISPLAYED field on the Parameter Prompting facility (Type 1) Primary menu. The date of update is displayed in either mm dd or dd mm format depending on the site standard.
Date Updated
Enter any character in the selection field (A) to the left of the VALUE field to add the condition without changing a value. The display of parameters can be limited to parameters beginning with a specific prefix by filling in the PARM PREFIX field (under the command line). To display the first occurrence of a parameter at the top of a screen, use the line command L xxxx, where xxxx is a specific parameter or parameter prefix.
2 183
Parameter Prompting Facility (Type 2)

After selecting option 2 of the CONTROL-M Parameter Prompting entry panel, the following menu is displayed:
---- CONTROL-M - PARAMETER PROMPTING FACILITY (TYPE 2) PRIMARY MENU --------(P) OPTION ===>
CREATE AND UPDATE A MASTER PLAN
FETCH A PLAN (CTMFETCH)
EXEC
A PLAN (CTMEXEC)
ENTER
END
COMMAND OR
PF3
TO TERMINATE
Note
You can enter this screen directly by activating CLIST CTMCAMNU.
This screen displays three options: 1. CREATE AND UPDATE A MASTER PLAN This option defines groups of parameters in a Master Prompting Plan. 2. FETCH A PLAN (CTMFETCH) This option places a User Prompting Plan (a copy of the Master Prompting Plan) and related job scheduling definitions in Daily libraries. A fetch is required before assigning parameter values and ordering plan execution with Option 3. 3. EXEC A PLAN (CTMEXEC) This option assigns values to parameters and orders a Plan for execution.
2 184
Option 1: Create and Update a Master Plan

After selecting Option 1 of the Parameter Prompting facility (Type 2) Primary menu, the following screen is displayed:
---- CONTROL-M - P.P.F. - DEFINE OR UPDATE A MASTER PLAN -----------------(P.1) COMMAND ===>
PLAN NAME IS: PLAN NAME PREFIX ===> REPTS
LIBRARY
===> CTM.PROD.PLANMSTR
Please fill in the Plan Name Prefix and press ENTER
ENTER
END
COMMAND OR
PF3
TO TERMINATE
A Master Plan is usually defined for a group of jobs and their AutoEdit parameters which are controlled by one person/project. Specify a maximum of six characters in PLAN NAME PREFIX and press <ENTER>. The name of the default library in which the Master Plan will be placed is displayed. It can be changed.
2 185
If the plan does not exist (i.e., you are defining a new plan), the following screen is displayed:
---- CONTROL-M - P.P.F. - MASTER PLAN DEFINITION -----------------------(P.1.2) COMMAND ===> CTMF52E MASTER PLAN REPTS WAS NOT FOUND. YOU MAY CREATE IT, OR EXIT PLAN PREFIX NAME ===> REPTS DESCRIPTION LIBRARY ===> DAILY REPORTS ===> CTM.PROD.PLANMSTR
Please fill in the Plan Description and press ENTER
ENTER
END
COMMAND OR
PF3
TO TERMINATE
You can create a new plan or exit the screen. To create a new plan, enter a plan description and press <ENTER>.
2 186
Define Parameters in the Master Plan After creation of a new plan, or if the requested plan exists, the following screen is displayed. If the plan exists, the previously defined parameters are displayed for modification.
---- CONTROL-M - P.P.F. - DEFINE PARAMETERS IN THE MASTER PLAN --- ROW 1 OF 3 COMMAND ===> SCROLL ===> CSR PARM PREFIX ===> PLAN NAME: REPTS ------------------------------------------------------------------------------_ PARM NAME ===> REPT_NAME OCCUR NO. ===> 01 JOB NAME ===> SLSREPTS PROMPT IND ===> Y (Y/N) DEFAULT ===> TYPE ===> NONBLANK,MAXL 8 MESSAGE ===> Enter name of sales report required ------------------------------------------------------------------------------_ PARM NAME ===> DEPT_NUMBER OCCUR NO. ===> JOB NAME ===> ******** PROMPT IND ===> Y (Y/N) DEFAULT ===> 035 TYPE ===> NUM,MAXL 3 MESSAGE ===> Enter department number (used for all reports) ------------------------------------------------------------------------------_ PARM NAME ===> REPT_NAME OCCUR NO. ===> 02 JOB NAME ===> EXPREPTS PROMPT IND ===> Y (Y/N) DEFAULT ===> TYPE ===> NONBLANK,MAXL 8 MESSAGE ===> Enter name of expense report required ****************************** Bottom of Data ********************************
This screen is used to define, display and modify parameters which will be used for prompting on a daily basis. Define Parameters in the Master Plan Screen Format The following information can be defined, displayed, or modified for each parameter: PARM NAME OCCUR NO. Name of the AutoEdit parameter. Occurrence number (2 digits). Differentiates between use of the same parameter name for different purposes in different jobs (e.g., assign OCCUR NO. 01 to occurrence of %%PARM1 in Job A; assign OCCUR NO. 02 to occurrence of %%PARM1 in Job B). Name of the job using the parameter. If the parameter and its assigned value are shared by more than one job in the plan, enter ******** in this field. It is not necessary to redefine the parameter. (If the value assigned is different for each job, refer to parameter OCCUR NO. above.)
JOB NAME
2 187
PROMPT IND
Prompting Indicator: Y (Yes) N (No) Promptable. The user will be prompted for a value for this parameter. Non-promptable. The value is fixed in the Master Prompting Plan and will not be modifiable in the EXEC phase.
DEFAULT
Default value for the parameter which will be displayed during the EXEC phase. This field is mandatory (non-promptable). if PROMPT IND is set to N
BLANK Type the word BLANK to set a value of . TYPE Type of parameter value which can be entered. A validation check is performed during both the plan definition and EXEC phases. Valid types are: NUM ALPHA CHAR BLANK NONBLANK MINL n Limits the value to digits only (0-9). Limits the value to letters only (a-z, A-Z, and $,#,@). Alphanumeric. Field must be blank. Any non-blank value. Limits the value to a specified minimum character length, where n is any number between 1 and 70. Limits the value to a specified maximum character length, where n is any number between 1 and 70.
MAXL n
MINL, MAXL, and NONBLANK can be combined with NUM or ALPHA. (Example: NUM MAXL 8 limits the parameter value to a numeric value with a maximum length of 8 characters.) MESSAGE Prompting message to be displayed during the EXEC phase.
The display of parameters can be limited to parameters beginning with a specific prefix by filling in the PARM PREFIX field (under the command line). To display the first occurrence of a parameter at the top of a screen, use the line command L xxxx, where xxxx is a specific parameter or parameter prefix.
2 188
Define Parameters in the Master Plan Screen Options To request one of the following options, specify the option in the field (A) to the left of the words PARM NAME and press <ENTER>. D DELETE R REPEAT A ADD I INSERT Delete a parameter from the plan. Duplicate a parameter. Add a parameter (same as option R). Insert a new parameter in the plan. INSERT typed on the Command line will insert a new parameter at the top of the plan.
Changes made to a parameter are updated in the plan when you press <ENTER>. (Whether or not an option is specified.) Define Parameters in the Master Plan Screen How to Exit To exit the Define Parameters in the Master Plan screen, type one of the following commands on the command line: END CANCEL Keep all plan changes, and exit. Exit without saving plan changes.
Option 2: Fetch a Plan (CTMFETCH)

---- CONTROL-M - P.P.F. ------ FETCH A PLAN ------------------------------(P.2) COMMAND ===>
PLAN NAME PLAN NAME SUFFIX OVERRIDE DAILY PLAN ODATE
===> REPTS ===> ===> NO ===> 090998 (For multiple plans in the same day) (YES / NO)
Please fill in the Plan Name and press ENTER
MASTER SCHEDULING LIB DAILY SCHEDULING LIB MASTER PLANS LIB DAILY PROMPT PLANS LIB MASTER JCL LIB DAILY JCL LIB ENTER END COMMAND OR
===> ===> ===> ===> ===> ===>
CTM.PROD.SCHEDULE CTM.PROD.SCHD CTM.PROD.PLANMSTR CTM.PROD.PLAN CTM.PROD.JCLPROMP CTM.PROD.JCLP
PF3
TO TERMINATE
2 189
This screen places a daily User Prompting Plan (a copy of the Master Prompting Plan) and related job scheduling definitions in Daily libraries. Fill in the details in the screen (libraries and the current date appear as defaults) and press <ENTER>. The PLAN NAME is the same as the Master Prompting Plan PREFIX. You can designate two characters to serve as a suffix to the Plan Name. This permits execution of a specific plan more than once a day. Valid values for OVERRIDE DAILY PLAN are: YES A duplicate fetch of a plan (with a suffix, if one has been designated) replaces an existing copy of a plan with the same PLAN NAME (and same suffix) for that day. Multiple fetches of a plan are not permitted on the same day. Default.
NO
Option 3: Exec/Order a Plan (CTMEXEC)

---- CONTROL-M - P.P.F. ---- EXEC / ORDER A PLAN -------------------------(P.3) COMMAND ===>
PLAN NAME PLAN NAME SUFFIX REMAINING PARAMETERS ODATE FORCED FROM TIME
===> REPTS ===> ===> NO ===> 090998 ===>
(Blank for plan selection list) (For multiple plans in the same day) (YES / NO)
Please fill in the Plan Name (or blanks) and press ENTER
DAILY SCHEDULING LIB USER PROMPT PLANS LIB DAILY PARAMETERS LIB
===> CTM.PROD.SCHD ===> CTM.PROD.PLAN ===> CTM.PROD.AEDI
ENTER
END
COMMAND OR
PF3
TO TERMINATE
This screen orders a plan for parameter updating and plan execution. Fill in the details in the screen (libraries and the current date appear as defaults) and press <ENTER>. The PLAN NAME is the same as the Master Prompting Plan PREFIX. You can designate two characters to serve as a suffix to the PLAN NAME. This permits execution of a specific plan more than once a day. The REMAINING PARAMETERS field determines whether or not you will be automatically prompted in the Update Parameter Values screen for parameter values which have yet to be updated for active plans. YES: Prompt. NO: Do not prompt.
2 190
The ODATE field specifies the original scheduling date for executing the plan. The FORCED FROM TIME field specifies a time (format hhmm) before which the jobs cannot run. If you leave PLAN NAME blank on the Exec/Order a Plan screen, the Plan Selection screen is displayed:
---- CONTROL-M - P.P.F. - PLAN SELECTION ------------------------- Row 1 FROM 2 COMMAND ===> SCROLL ===> PAGE PLAN PREFIX ===> PLAN ORDERED ALREADY: ------------------------------------------------------------------------------_ PLAN NAME ===> REPTS ===> NO ORDER TIME : _ PLAN NAME ===> BACKUP ===> YES ORDER TIME : ****************************** Bottom of Data ******************************
This screen displays a list of active Daily Plans. PLAN ORDERED ALREADY: (A) indicates whether or not the plan was already ordered. If the plan has already been ordered, it is possible to select a plan for parameter value updating only. To select a plan, enter any character in the field (B) to the left of the PLAN NAME.
2 191
Update Parameter Values Screen After selecting a plan from the Plan Selection screen or specifying a particular plan on the Exec/Order a Plan screen, the Update Parameter Values screen is displayed:
---- CONTROL-M - P.P.F. - UPDATE PARAMETER VALUES ---------------- ROW 1 FROM 3 COMMAND ===> SCROLL ===> CSR PARM PREFIX ===> PLAN NAME: REPTS ------------------------------------------------------------------------------_ PARM NAME ===> REPT_NAME OCCUR NO. ===> 01 NO DEFAULT VALUE ===> Enter name of sales report required _ PARM NAME ===> DEPT_NUMBER OCCUR NO. ===> DEF EXISTS VALUE ===> 035 Enter department number (used for all reports) _ PARM NAME ===> REPT_NAME OCCUR NO. ===> 02 NO DEFAULT VALUE ===> Enter name of expense report required ****************************** Bottom of Data ******************************
This screen displays a list of all AutoEdit parameters for which values can be entered. Press END (PF03/PF15) to exit the screen. The display of parameters can be limited to plans beginning with a specific prefix via the PARM PREFIX field (under the command line). To display the first occurrence of a parameter at the top of the screen, specify line command L xxxx, where xxxx is a specific parameter or parameter prefix. After all variables in a plan have been updated or have had their defaults approved, you will receive screen messages indicating the jobs from each plan which were ordered automatically. Format of the Update Parameter Values Screen PARM PREFIX PLAN NAME PARM NAME VALUE MESSAGE Plan prefix. If a value is specified for this field, the display of parameters is limited to plans beginning with the specified prefix. Name of the User Prompting Plan ordered for execution. Name of the parameter available for update. Default value of the parameter. This value can be modified; embedded blanks are permitted. Prompting message.
2 192
OCCUR NO.
Occurrence number (2 digits). Differentiates between use of the same parameter name for different purposes in different jobs (e.g., assign OCCUR NO. 01 to occurrence of %%PARM1 in Job A; assign OCCUR NO. 02 to occurrence of %%PARM1 in Job B). Indication of default: NO DEFAULT DEF EXISTS No associated default value. Parameter has an associated default value which has not yet been approved by the user.
DEFAULT STATUS
DEF CONFIRMED Default value has been approved. DEF CHANGED SELECTION FIELD Special Options A special option, activated by specifying YES in the REMAINING PARAMETERS field on the Exec/Order a Plan screen, will prompt you automatically for parameter values which have yet to be updated from all active plans (i.e., those plans fetched for the day). The parameters are presented on consecutive Update Parameter Values screens. REMAINING PARAMETERS YES NO You are presented with remaining (non-updated) parameters from active plans. After updating the current plan, the Exec/Order a Plan screen will be displayed or, if Plan Name was left blank, the Plan Selection screen containing all active plans will be displayed. Default. Default value is not being used. Parameter has been assigned a different value.
Type S in this field (A) to accept the default, if a default exists.
2 193
Online Facility: Utilities Under ISPF M5: Quick Schedule Definition Facility
M5: Quick Schedule Definition Facility

The Quick Schedule Definition facility is an automatic online interface for creating scheduling tables for jobs having common scheduling parameters. This facility speeds up the process of defining a schedule by eliminating the need to individually define parameters for each job and its job interdependencies. Twenty-one jobs and their interdependencies can be defined on one screen with CONTROL-M automatically providing space for additional jobs. The utility can be requested in the following ways:
Select option M5 on the Online Utilities menu Activate CLIST CTMQUICK from the TSO Command Processor
Quick Schedule Definition Process

Four simple steps are performed one time only in order to create a complete scheduling table for an unlimited number of jobs. No. 1. 2. Step Create a skeleton job. Specify general table information and prerequisite conditions format. List job interdependencies. Exit the Quick Schedule Definition facility. Where Performed Screen 2, Scheduling Definition facility. Quick Schedule Definition entry panel.
3. 4.
Quick Definition Job List screen. Note: The scheduling table is automatically created upon exit from the Quick Schedule Definition facility.
These steps are described in detail below. Step 1: Create a Skeleton Job In this step you create a job in a scheduling table to be used as a skeleton, or model, for all the jobs in the automatically created scheduling table (output table). Enter the CONTROL-M Scheduling Definition facility and create a standard CONTROL-M scheduling table containing one skeleton job. (See Scheduling Definition Facility earlier in this section if you are not familiar with job scheduling under CONTROL-M.) Specify in the skeleton job all parameter values which are to be common to (the same in) all the jobs in the automatically created table. It is not necessary to specify IN and OUT parameters. IN and OUT prerequisite conditions will be automatically created by CONTROL-M in the output scheduling table. MEMNAME, MEMLIB, and DOCLIB fields are overridden by CONTROL-M during automatic table creation. The data in all other fields will be copied into each of the new jobs in the output table. Therefore, it is important to verify the data carefully.
2 194
%%JOBNAM and %%JOBNAME Variables If variable %%JOBNAM (a non-AutoEdit variable specific to the Quick Schedule Definition facility) is specified in a SHOUT statement, it is resolved during table creation to the member name in each job. If system variable %%$JOBNAME is specified in a SHOUT statement, it is resolved at runtime to the name of the job. Step 2: Specify General Table Information and Prerequisite Conditions Format In this step, you display the Quick Schedule Definition entry panel and specify general table information and the desired format for automatically defined prerequisite conditions. The entry panel can be displayed either by requesting option M5 on the Online Utilities menu, or by activating CLIST CTMQUICK from the TSO Command Processor. The following screen is displayed:
------------------- CONTROL-M QUICK SCHEDULE DEFINITION ----------------------COMMAND ===> SPECIFY LIBRARY, OUTPUT SCHEDULING TABLE, SKELETON SCHEDULING TABLE LIBRARY TABLE SKELETON ===> CTM.PROD.SCHEDULE ===> PAYROLL ===> DAILY
(Scheduling table to be created) (Skeleton scheduling table) (T: your TSO User ID) (S: OWNER from the skeleton table)
OWNER in the output table S
PREREQUISITE CONDITIONS FORMAT (CHOOSE ONE) GROUP-FROMJOB-SUFFIX ===> Y FROMJOB-TOJOB-SUFFIX ===> N PREFIX-FROMJOB-TOJOB ===> N PREFIX OR SUFFIX ===> OK GROUP ===> FINANCE SERVICES (For group-fromjob-suffix option) (Y/N) (Y/N) (Y/N)
Fill in the following general table information fields: LIBRARY TABLE SKELETON Name of the library which contains the skeleton member created in Step 1 and which will contain the output scheduling table. Name of the scheduling table to be created. Member name of the model scheduling table containing common parameter values (created in Step 1 above). The member must exist in the library specified above.
2 195
OWNER
Value to be specified in the OWNER field in the output scheduling definitions. Valid values are: T S Your TSO user ID is used as the value for OWNER in the output tables. The value of OWNER in the skeleton table is used for OWNER in the output tables.
To exit this screen, press END (PF03/PF15). Prerequisite Condition Format Fields Job dependencies are established via prerequisite conditions which are defined in the job scheduling definitions. The utility defines prerequisite conditions automatically. Therefore, naming conventions for these conditions must be specified. Prerequisite conditions created by the utility must consist of a combination of the following elements: fromjob Name of the predecessor job in the dependency. For example, if JOB-A must terminate before JOB-B can be submitted, JOB-A is the fromjob. tojob groupname prefix suffix Note Name of the successor job in the dependency. For example, if JOB-B must be submitted after JOB-A terminates, JOB-B is the tojob. Name of the group to which the jobs in the dependency belong. Constant to be added as a prefix to the condition. Constant to be added as a suffix to the condition. Job dependencies are defined in Step 3 (described below).
CONTROL-M can create prerequisite conditions based on the above elements in three different formats. These formats are described below. Select one of the formats by specifying Y (Yes) to the right of one desired format, and N (No), to the right of the remaining two formats. IN and OUT prerequisite conditions are automatically created in the job scheduling definitions in the selected format. GROUP-FROMJOB-SUFFIX If Y is specified, creates conditions with the format: groupname-fromjob-suffix (e.g.,BACKUP-BKP00010-OK). If Y is specified, creates conditions with the format: fromjob-tojob-suffix (e.g., BKP00010-BKP00020-OK). If Y is specified, creates conditions with the format: prefix-fromjob-tojob (e.g.,VALCHECK-BKP00010-BKP00020).
FROMJOB-TOJOB-SUFFIX PREFIX-FROMJOB-TOJOB
2 196
Both of the following fields affect the above formatted conditions. The GROUP field also affects the GROUP value in the job scheduling definition. PREFIX OR SUFFIX Constant to be used as a prerequisite condition prefix or suffix (depending on the format selected). Mandatory. 1-9 characters. 1-20 character group name (no embedded spaces) to be used in the job scheduling definitions. Optional, except for format GROUP-FROMJOB-SUFFIX (for which it is mandatory). If specified, the value in this field is used as the GROUP value in the created job scheduling definitions (i.e., in place of the GROUP value in the skeleton). If format GROUP-FROMJOB-SUFFIX format is requested, an * can be specified in this field. In this case, the group name is omitted from the prerequisite condition (e.g., BKP00010-OK), but the created job scheduling definitions will still contain the group name defined in the skeleton. Proceeding to the Job List Screen Once you have filled in the fields in the Quick Definition entry panel, press <ENTER>.
GROUP
If the table which you specified in the TABLE field does not already exist in the library, the Job List screen is displayed and you can proceed with Step 3. If the table which you specified in the TABLE field already exists in the library, the Overwrite Confirmation window is displayed:
------------------- CONTROL-M QUICK SCHEDULE DEFINITION ----------------------COMMAND ===> +-----------------------------------------------------------+ | | | LIBRARY CTM.PROD.SCHEDULE | | TABLE PAYROLL | | | | ALREADY EXISTS. | | | | THIS PROCEDURE WILL OVERWRITE THE DATA IN THE TABLE. | | | | DO YOU WISH TO CONTINUE (Y/N) | | | +-----------------------------------------------------------+
Specify Y (Yes) to overwrite the existing table. The current contents of the table are erased, and an empty table (Job List screen) is displayed.
2 197
Specify N (No) if you do not wish to overwrite the current contents of the table. The window is closed. You can now specify a different table name in the TABLE field and press <ENTER> again.
Step 3: Specify Job Interdependencies In this step you will fill in a list of jobs, a description of each job, and the jobs upon which they depend. After you fill in the Quick Schedule Definition entry panel (and, if necessary, the Overwrite Confirmation window) and press <ENTER>, the Job List screen is displayed:
JOB LIST LIB: CTM.PROD.SCHEDULE COMMAND ===> O NR MEMNAME DEPENDS ON-------------1 CHECKCAL *TIME-CARDS-DONE 2 CHECKPRT 3 GOVTREPT CHECKCAL 4 BANKTAPE 1 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 TABLE: PAYROLL SCROLL===> PAGE DESCRIPTION ------------------------------CALCULATE CHECKS PRINT CHECKS REPORTS TO GOVERNMENT REPORTS FOR MANAGEMENT
Fill in one line for each job (the fields are detailed below). CONTROL-M provides additional lines on the screen, as necessary. When you have finished filling in the list, press <ENTER>. The entries will be validated. Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) on the Job List screen. Fields in the Job List Screen O NR MEMNAME DEPENDS ON Field for specifying options (described below) . Line number. This number can be referenced in the DEPENDS ON field of another job. Name of the member containing the JCL of the job. Jobs and/or external prerequisite condition(s) on which this job depends. Valid formats for the dependencies are: name Name of the job (MEMNAME) upon which the current job depends.
2 198
position-number
Number of the job on the screen. This number is automatically adjusted when an option changes the position of the current job or the job upon which it depends. Minus sign represents the previous job in the list. Name of an external prerequisite condition, i.e., a prerequisite condition other than job inter-dependencies which are automatically created. It must be preceded by an asterisk (*) and be the last dependency entered on the job line. The date reference ODAT is automatically associated with the in-condition.
*in-condition
More than one dependency can be listed by separating each name by a comma. Format types may be mixed on a line. Examples CHECKCAL 1 *SALES-DATA 3,*SALES-DATA Job CHECKCAL Job on line 1 of the list Job on the preceding line An external IN condition Job on line 3 of the list plus an external IN condition.
DESCRIPTION Description of the job in free text. Options of the Job List Screen To use one of the following options, specify the option in the O field to the left of the line number. These options are similar to ISPF line commands. I P R D A B C M Insert a blank line immediately after the current line. Insert a blank line immediately preceding this line. This enables addition of data before the first line in the list. Repeat this line immediately after the current line. Delete this line. If a job depends upon this line, you will receive an error message. Indicates that the target of a copy or move is directly after this line. Indicates that the target of a copy or move is directly before this line. Copy this line to the target. Move this line to the target.
After performing requested options, CONTROL-M automatically handles renumbering and adjusts the relevant DEPENDS ON parameter values on the screen.
2 199
Step 4:
Exit the Quick Schedule Definition Facility (and Create the Scheduling Table)
To exit the Quick Schedule Definition facility after entering the data for a table, press the END (PF03/PF15) key. An Exit Option window is opened:
JOB LIST LIB: CTM.PROD.SCHEDULE TABLE: PAYROLL COMMAN +--------------------------------------------------------------+ | PLEASE SELECT EXIT OPTION | | | | SAVE CREATE | | | | LIBRARY CTM.PROD.SCHEDULE | | TABLE PAYROLL | | | +--------------------------------------------------------------+
The schedule can be saved (to replace a table of the same name that previously existed in the library), or created (to store a new table in the library), by specifying Y in the appropriate exit option. The job schedule is automatically created as you exit. If N is specified, the table is not saved, and the schedule is not produced. You will return to the Utilities screen or other screen depending on how you entered the utility. If no changes have been made, the Exit Option window is not opened. To exit to the Quick Schedule Definition entry panel without saving your entries (and without creating the job schedule), press RESET (PF04).
2 200
The screen below illustrates job GOVTREPT selected from the jobs listed in the Job List screen in Step 3 above. Note particularly the automatically created MEMNAME, IN and OUT parameters, and the job name inserted into the SHOUT message by using the %%JOBNAM variable.
JOB: GOVTREPT LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME GOVTREPT MEMLIB CTM.PROD.JOBLIB OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y APPL APPL-L GROUP BKP-PROD-L DESC REPORTS TO GOVERNMENT OVERLIB SET VAR CTB STEP AT NAME DOCMEM GOVTREPT DOCLIB =========================================================================== DAYS DCAL AND/OR O WDAYS ALL WCAL MONTHS 1- N 2- N 3- N 4- N 5- N 6- N 7- Y 8- N 9- Y 10- N 11- N 12- N DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN FINANCE-CHECKCAL-OK ODAT CONTROL RESOURCE TIME: FROM UNTIL PRIORITY 00 DUE OUT CONFIRM =========================================================================== OUT FINANCE-GOVTREPT-OK ODAT + AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST PROCST CODES A/O DO SHOUT WHEN NOTOK TO TSO-M44 URGN R MS JOB GOVTREPT ENDED "NOT OK" SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< ===== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 20.28.53
2 201
Online Facility: Utilities Under ISPF M6: End User Job Order Interface
M6: End User Job Order Interface

By ordering jobs via the End User Job Order Interface, an end user can bypass the rest of the CONTROL-M Online facility. The Job List screen (below) can be displayed in the following ways:
Select option M6 on the Online Utilities menu Activate CLIST CTMJBINT from the TSO Command Processor
JOB LIST LIB: CTM.PROD.SCHEDULE TABLE: M22JBINT COMMAND ===> SCROLL===> CRSR OPT NAME --------------------------------------------------------------------PAYCALC PAYROLL RUN PAYPOST POST PAYROLL REPORTING ====== >>>>>>>>>>>>>>>>>>> NO MORE JOBS IN TABLE <<<<<<<<<<<<<<<< =====
This screen displays a list of jobs which the particular user is permitted to order. (The IOA administrator determines which jobs each user is permitted to order.) Use the scrolling PFKeys to scroll forward (PF08/PF20) and backward (PF07/PF19) on the Job List screen. Press END (PF3/PF15) to exit the screen. To order jobs, specify S in the OPT field to the left of each job to be ordered and press <ENTER>. For each job selected, in sequence, a window displaying the job and the date is displayed. The user can change the date in the window. From the window:
Press <ENTER> to complete the order request. Press PF03/PF15 to cancel the order request. Press PF04/PF16 to cancel the changes and exit the Job List screen.
2 202
Online Facility: Utilities Under ISPF R1: CONTROL-R Restart Simulation
R1: CONTROL-R Restart Simulation

A CONTROL-R Restart simulation can be performed to validate the results of a CONTROL-R restart before a job is run in the real-time environment. Restart simulation enables you to see what actions will be taken by CONTROL-R without actually performing the restart. The CONTROL-R Simulation panel (below) can be displayed in the following ways:
Select option R1 on the Online Utilities menu Activate CLIST CTRCSIM directly from the TSO Command Processor
------------------------ CONTROL-R SIMULATION -----------------------COMMAND ===> ACTION REQUIRED: ===> R-Restart Simulation P-Prevent NCT2 Simulation
R
JCL LIBRARY MEMBER NAME ORDER ID RESTART FROM FROM TO TO PARAMETERS: PGMSTEP PROCSTEP PGMSTEP PROCSTEP ===> CTM.PROD.JCL ===> Job to be restarted ===> Job order identifier
===> ===> ===> ===>
($FIRST/pgmstep name) (Optional) (Optional) (Optional)
AUTO-EDIT PARAMETERS: OWNER GLOBAL AUTO-EDIT LIBRARY WDATE ODATE Enter YES to continue
===> ===> ===> ===> ===>
M21 CTM.PROD.PARM 09 09 98 (MM DD YY) 09 09 98 (MM DD YY)
To run a restart simulation, fill in the parameters of the Simulation panel, specify YES in the last field of the screen, and press <ENTER>. To exit the Simulation panel, press END (PF03/PF15).
Action Required Parameters

ACTION REQUIRED JCL LIBRARY MEMBER NAME ORDER ID Select either R- Restart or P- Prevent NCT2 simulation. Library containing the original job being submitted. Name of the member containing the JCL for the job to be restarted. Job order identifier of the specific job run to be restarted.
2 203
Online Facility: Utilities Under ISPF R1: CONTROL-R Restart Simulation
Restart Parameters
FROM PGMSTEP FROM PROCSTEP TO PGMSTEP TO PROCSTEP Name of the program step at which a job restart is to be attempted. Name of the procedure step at which a job restart is to be attempted. Name of the program step at which a restarted job is to terminate. Name of the procedure step at which a restarted job is to terminate.
AutoEdit Parameters
OWNER Owner (called USER ID prior to IOA Release 4.0.0).
GLOBAL AUTOEDIT LIBRARY| Library containing globally defined AutoEdit variables. WDATE ODATE Current working date. Original scheduling date of the job.
CONTROL-R Simulation Process

Using the parameters from the Simulation panel, the JCL member is read from the library, its AutoEdit parameters are processed, a CONTROLR step is placed in the job stream, and the edited job is submitted. The job runs and stops after the CONTROLR step. It is then possible to see the results of the submitted job.
2 204
Online Facility: Utilities Under ISPF R2: CONTROL-R Dataset Cleanup
R2: CONTROL-R Dataset Cleanup

To perform dataset adjustment without performing the actual restart, a CONTROL-R dataset cleanup can be performed. The CONTROL-R Dataset Cleanup panel (below) can be displayed in the following ways:
Select option R2 on the Online Utilities menu Activate CLIST CTRCCLN in the TSO Command Processor
------------------------ CONTROL-R DATA SET CLEANUP -----------------------COMMAND ===>
CLEANUP PARAMETERS JCL LIBRARY MEMBER NAME ORDER ID FROM FROM TO TO PGMSTEP PROCSTEP PGMSTEP PROCSTEP
===> CTM.PROD.JCL ===> Job JCL member ===> Job order identifier ===> ===> ===> ===> ($FIRST/pgmstep name) (Optional) (Optional) (Optional)
AUTOEDIT PARAMETERS: OWNER GLOBAL AUTOEDIT LIBRARY WDATE ODATE Enter YES to continue
===> ===> ===> ===> ===>
M21 CTM.PROD.PARM 05 05 98 (MM DD YY) 05 05 98 (MM DD YY)
To perform dataset cleanup from a specific step, specify the step name in the appropriate FROM PGMSTEP / FROM PROCSTEP field(s). To perform dataset cleanup for the whole job, enter $FIRST in field FROM PGMSTEP. Note It is recommended that the Restart Window of the Status screen be used instead of this utility for full job cleanup. Dataset cleanup is more easily performed using the Restart window (specify $FIRST.$CLEANUP as the FROM step name). In addition, dataset cleanup from the Restart Window resolves all AutoEdit variables, including SET VAR statements.
When you have filled in the desired parameters, specify YES in the last field of the screen, and press <ENTER>. To exit the Dataset Cleanup panel, press END (PF03/PF15).
2 205
Cleanup Parameters
JCL LIBRARY MEMBER NAME ORDER ID FROM PGMSTEP FROM PROCSTEP TO PGMSTEP TO PROCSTEP Library containing the original job. Name of the member containing the JCL for the job. Job order identification of the specific job run. Name of the program step at which dataset adjustment is to be attempted. Name of the procedure step at which dataset adjustment is to be attempted. Name of the program step at which dataset adjustment is to terminate. Name of the procedure step at which dataset adjustment is to terminate.
AutoEdit Parameters
OWNER Owner.
GLOBAL AUTOEDIT LIBRARY Library containing globally defined AutoEdit variables. WDATE ODATE Current working date. Original scheduling date of the job.
2 206
CONTROL-R Dataset Cleanup Process

Using the parameters from the Dataset Cleanup panel, the JCL member is read from the library, its AutoEdit parameters (except SETVAR parameters) are processed, a CONTROLR step is placed in the job stream and the edited job is submitted. The CONTROLR step performs the necessary dataset adjustment (including step adjustment, if necessary) and then stops. No further job steps are executed. The following points should be noted about From Step/Proc and To Step/Proc values:
Pgmstep name can be any specific program step name or $FIRST. $FIRST resolves to the first step of the job if procstep name is blank. Otherwise, $FIRST resolves to the first step in the procedure identified by procstep. $ABEND and $EXERR are not recognized by CONTROL-R and should not be specified as restart steps in this window. ($ABEND and $EXERR are valid only in job scheduling definitions.) If specifying a procstep name when there are nested procedures, specify the procstep name of the innermost procedure in which the program is included. Entering $FIRST in the first From Step/Proc field followed by $CLEANUP in the adjacent (second) From Step/Proc field will rerun the job for Cleanup (i.e., run the CONTROL-R cleanup step and flush the job). All other parameters entered in the Restart window will be ignored. AutoEdit resolution is performed at time of submitting the cleanup job. For example, if a job with AutoEdit date variable %%DATE is submitted for cleanup the day after the original run, the resolution of the variable during cleanup will vary from that of the original run.
Note
2 207
Online Facility: Utilities Under ISPF R3: Prepare the Job Dataset List
R3: Prepare the Job Dataset List

This screen is used to prepare the list of permanent datasets used in a job. The list is generated in the Statistics file. This utility is generally run as a preliminary step before generating the Job Dataset Cross Reference Report, which requires the list of datasets for the job as input. For more information, see CTMRJDS: Job Dataset Cross Reference Report in Section 8 of this manual. The utility screen (below) can be displayed in the following ways:
Select option R3 from the Online Utilities menu. Activate CLIST CTMJDSN from the TSO Command Processor.
---------------COMMAND ===> CONTROL-R JOB DATASET LIST ----------------
R
JCL LIBRARY MODE: JCL LIBRARY MEMBER NAME SCHEDULING LIBRARY MODE: SCHEDULING LIBRARY TABLE NAME JOB NAME AUTOEDIT PARAMETERS: OWNER GLOBAL AUTOEDIT LIBRARY WDATE ODATE ENTER YES TO CONTINUE ===> ===>
===> CTM.PROD.SCHEDULE ===> ===>
===> ===> ===> ===> ===>
N04 CTM.PROD.PARM 07 07 98 (MM DD YY) 07 07 98 (MM DD YY)
Utility CTMJDSN allows specification of one job at a time. It can operate in either JCL Library mode or Scheduling Library mode:
In JCL Library mode, the utility checks the job (member) specified in the specified JCL library. In Scheduling Library mode, the utility checks the specified job in the specified scheduling table/library.
The utility adds a step to the job to prevent the execution of other steps in the job. The job is then submitted. The datasets required are listed in the Statistics file, and the job is stopped before it can execute.
2 208
Online Facility: Utilities Under ISPF U1: Invoke DOCU/TEXT25
Depending on the mode in which the utility operates, either JCL Library mode or Scheduling Library mode parameters (but not both) must be specified. To activate the utility, fill in the appropriate parameters and press <ENTER>:
JCL Library Mode Parameters

JCL LIBRARY MEMBER NAME Library which contains the jobs JCL. Name of the member containing the JCL for the job.
Scheduling Library Mode Parameters

SCHEDULING LIBRARY TABLE NAME Name of the library containing the job scheduling definition. Name of the table containing the job scheduling definition. Name of the job scheduling definition.
JOB NAME
AutoEdit Parameters
OWNER User ID of the jobs owner.
GLOBAL AUTOEDIT LIBRARY AutoEdit library containing globally defined AutoEdit variables. WDATE ODATE Current working date. Original scheduling date of the job.
ENTER YES TO CONTINUE Confirmation field to help prevent unintentional job submission. When blank, the request is ignored. Specify YES to enable the job request. To exit the screen without activating the utility, press PF03/PF15.
U1: Invoke DOCU/TEXT25

This option provides a direct interface to DOCU/TEXT. It can be activated by requesting option U1 on the Online Utilities menu or by activating CLIST CTMCDOCU directly. Refer to your DOCU/TEXT user manual for details about product usage.
25
This option is available only at sites which have installed DOCU/TEXT, a product of Diversified Systems Software, Inc. which provides automated, online JCL documentation.
2 209
Online Facility: Utilities Under ISPF U1: Invoke DOCU/TEXT25
2 210
Section 3: Job Production Parameters

General ...........................................................................................................................................3-1 General Parameters Summary ...............................................................................................3-4 Basic Scheduling Parameters Summary................................................................................3-4 Runtime Scheduling Parameters Summary ..........................................................................3-8 Post-processing Parameters Summary ..................................................................................3-9 Parameter Descriptions .......................................................................................................... 3-11 ADJUST CONDITIONS...........................................................................................................3-12 APPL .........................................................................................................................................3-14 AUTO-ARCHIVE......................................................................................................................3-16 SYSDB..................................................................................................................................3-16 MAXDAYS ...........................................................................................................................3-16 MAXRUNS...........................................................................................................................3-16 CONFCAL.................................................................................................................................3-19 SHIFT...................................................................................................................................3-20 CONFIRM .................................................................................................................................3-23 CONTROL.................................................................................................................................3-25 CTB STEP .................................................................................................................................3-29 AT .........................................................................................................................................3-29 NAME...................................................................................................................................3-29 TYPE ....................................................................................................................................3-29 D-CAT........................................................................................................................................3-31 DATES.......................................................................................................................................3-33 DAYS .........................................................................................................................................3-35 DCAL....................................................................................................................................3-35 AND/OR ...............................................................................................................................3-36 DESC .........................................................................................................................................3-42 DO statement............................................................................................................................3-44 DO COND .................................................................................................................................3-46 DO CTBRULE ..........................................................................................................................3-50 ARG ......................................................................................................................................3-50 DO FORCEJOB ........................................................................................................................3-52 TABLE .................................................................................................................................3-52 JOB.......................................................................................................................................3-52 DATE....................................................................................................................................3-52 LIBRARY .............................................................................................................................3-52
DO IFRERUN .......................................................................................................................... 3-54 FROM .................................................................................................................................. 3-54
TO ........................................................................................................................................ 3-55 CONFIRM ........................................................................................................................... 3-55 DO NOTOK .............................................................................................................................. 3-57 DO OK ...................................................................................................................................... 3-59 DO RERUN .............................................................................................................................. 3-61 DO SET..................................................................................................................................... 3-63 VAR= ................................................................................................................................... 3-63 DO SHOUT .............................................................................................................................. 3-66 TO ........................................................................................................................................ 3-66 URGENCY .......................................................................................................................... 3-67 DO SYSOUT............................................................................................................................. 3-70 OPT...................................................................................................................................... 3-70 PRM ..................................................................................................................................... 3-70 FRM ..................................................................................................................................... 3-70 DOC .......................................................................................................................................... 3-77 DOCLIB.................................................................................................................................... 3-79 DOCMEM................................................................................................................................. 3-81 DUE OUT ................................................................................................................................. 3-83 GROUP..................................................................................................................................... 3-85 IN .............................................................................................................................................. 3-87 INTERVAL............................................................................................................................... 3-95 MAXWAIT ................................................................................................................................ 3-97 MEMLIB................................................................................................................................. 3-100 MEMNAME............................................................................................................................ 3-104 MINIMUM ............................................................................................................................. 3-106 MONTHS................................................................................................................................ 3-108 ON........................................................................................................................................... 3-110 PGMST .............................................................................................................................. 3-110 PROCST ............................................................................................................................ 3-110 CODES .............................................................................................................................. 3-111 A/O ..................................................................................................................................... 3-111 ON GROUP-END .................................................................................................................. 3-118 OUT ........................................................................................................................................ 3-120 OVERLIB ............................................................................................................................... 3-131 OWNER .................................................................................................................................. 3-133 PDS ......................................................................................................................................... 3-135 PIPE........................................................................................................................................ 3-137
PREVENT-NCT2....................................................................................................................3-140 PRIORITY ...............................................................................................................................3-142 RELATIONSHIP ....................................................................................................................3-144 RERUN-MAXRERUN ............................................................................................................3-146 RERUN-RERUNMEM ...........................................................................................................3-148 RESOURCE ............................................................................................................................3-150 RETENTION: # OF DAYS TO KEEP ...................................................................................3-155 RETENTION: # OF GENERATIONS TO KEEP .................................................................3-157 RETRO ....................................................................................................................................3-159 SCHEDULE TAG ...................................................................................................................3-161 SET VAR .................................................................................................................................3-164 SHOUT....................................................................................................................................3-169 WHEN ................................................................................................................................3-169 TO .......................................................................................................................................3-170 URGN.................................................................................................................................3-171 MS ......................................................................................................................................3-171 STEP RANGE .........................................................................................................................3-174 FR (PGM.PROC)................................................................................................................3-174 TO .......................................................................................................................................3-174 SYSOUT ..................................................................................................................................3-176 OP.......................................................................................................................................3-176 FROM.................................................................................................................................3-176 TASKTYPE .............................................................................................................................3-182 TIME .......................................................................................................................................3-186 FROM.................................................................................................................................3-186 UNTIL ................................................................................................................................3-186 WDAYS ...................................................................................................................................3-189 WCAL .................................................................................................................................3-189
Job Production Parameters: General
General
Job scheduling definitions consist of parameters which correspond to the decisions made and actions performed when handling the scheduling, submission and post-processing of a job. Job scheduling definitions are defined in the Job Scheduling Definition screen (shown below), the main screen of the Scheduling Definition facility. Notes Fields SCHEDULE TAG (A) and RELATIONSHIP (B) only appear in job scheduling definitions belonging to Group scheduling tables. Parameter PIPE (C) is displayed only if CONTROL-M/WorkLoad is installed. RETENTION parameters # OF DAYS TO KEEP and # OF GENERATIONS TO KEEP (D) are displayed only at sites which use the History Jobs file.
JOB: BACKPL02 LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME BACKPL02 MEMLIB CTM.PROD.JOBLIB OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y APPL APPL-L GROUP BKP-PROD-L DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L OVERLIB CTM.OVER.JOBLIB SET VAR CTB STEP AT NAME TYPE DOCMEM BACKPL02 DOCLIB CTM.PROD.DOC =========================================================================== SCHEDULE TAG RELATIONSHIP (AND/OR) O DAYS DCAL
AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL WORKDAYS SHIFT RETRO N MAXWAIT 04 D-CAT MINIMUM PDS =========================================================================== IN START-DAILY-BACKUP ODAT CONTROL RESOURCE INIT 0001 CART 0001 PIPE CTM.WKLD.PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT BAKCKPL02-ENDED-OK ODAT + AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< ===== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
31
If the scheduling table is a Group scheduling table, a Group Entity (shown below) must be defined before the job scheduling definitions.
GRP ACCOUNTS_GROUP CTM.PROD.SCHEDULE(GRP) COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ GROUP ACCOUNTS_GROUP MEMNAME ACCOUNTS OWNER N04B APPL DESC ADJUST CONDITIONS N SET VAR DOCMEM ACCOUNTS DOCLIB CTM.PROD.DOC =========================================================================== SCHEDULE TAG ALL_DAYS DAYS ALL DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 =========================================================================== SCHEDULE TAG DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 =========================================================================== IN TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT ON GROUP-END NOTOK DO COND ACCTS-CHK-REQUIRED ODAT + SHOUT WHEN TO URGN USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 18.19.14
Most parameters in the Group Entity definition are the same as in the job scheduling definition, but they apply to the group as a whole. Therefore:
At least one set of basic scheduling criteria in the Group Entity must be satisfied before any job in the group can be scheduled. Runtime scheduling criteria in the Group Entity must be satisfied before any job in the group can be executed. Post-processing statements in the Group Entity are applied only after all jobs in the group have finished executing.
32
The following parameters in the Group Entity are not found in the job scheduling definition: A. ADJUST CONDITIONS B. ON GROUP-END Usage and operation of the Scheduling Definition facility, including entry and exit of the Job Scheduling Definition screen, is described in Section 2 of this manual. In addition to defining jobs via the Scheduling Definition facility, jobs can also be defined using batch utility CTMBLT (see Section 6 of this manual) or using online utility QUICKDEF. (Utility QUICKDEF, the Quick Schedule Definition facility, is available under ISPF only. See Section 2 of this manual.) Prior to CONTROL-M Release 5.0.0, Job parameters could also be defined via a set of Assembler macro instructions. Utility CTMBLT makes this method obsolete. Therefore, Assembler macro instructions are supported for backward compatibility only. New parameters appearing in Release 5.0.0 or higher have not been added to this set of macro instructions. This section provides a detailed description of the job scheduling definition parameters and statements. The parameters of the Job Scheduling Definition screen are divided into the categories listed below.
General Parameters Basic Scheduling Parameters Runtime Scheduling Parameters Post-processing Parameters
A brief summary of the parameters in each category is provided on the following pages. This is followed by a detailed description of each parameter, in alphabetical order.
33
Job Production Parameters: General General Parameters Summary
General Parameters Summary

General parameters provide general information about the job and certain information required by the JCL. Information about the following parameters is provided in this section: MEMNAME MEMLIB OWNER TASKTYPE
R
Member containing the JCL. Library containing the JCL member. Owner of the job. Type of job or task. Whether or not to prevent NOT CATLGD 2 errors during non-restarted executions of the job. Application to which the job belongs. Group to which the job belongs. Brief description of the job. Library containing a special case JCL for the job. Mechanism for setting the value of a JCL user-defined variable. CONTROL-B step to be added to the jobs execution. Member containing detailed information about the job. Library containing the member specified in parameter DOCMEM. Detailed job documentation.
PREVENT NCT2 APPL GROUP DESC OVERLIB SET VAR CTB STEP DOCMEM DOCLIB DOC
The following General parameter is in the Group Entity only: ADJUST CONDITIONS Allows conditions to be removed from job orders if the predecessor jobs which set the conditions are not scheduled.
Basic Scheduling Parameters Summary

Basic Scheduling parameters determine if the job is a candidate for execution on a specific date. If a job is a candidate for execution on a specific date, a job order is automatically placed in the Active Jobs file during New Day processing. Each job order placed in the Active Jobs file is associated with an original scheduling date. This is the date the job should run according to the Basic Scheduling parameters. This date is not necessarily the same as the current system date or the current working date. See Date Definition Concepts in Section 1 of this manual. Basic Scheduling parameters and subparameters allow different methods of expressing a job schedule. Parameter SCHEDULE TAG appears only in Group tables, in both job scheduling definitions and in the Group Entity.
34
Job Production Parameters: General Basic Scheduling Parameters Summary
Each set of basic scheduling criteria in the Group Entity must be uniquely labeled by a SCHEDULE TAG value. At least one Schedule Tag must be defined. In job scheduling definitions, SCHEDULE TAG is optional. Each specified SCHEDULE TAG value in the job scheduling definition must match a SCHEDULE TAG value in the Group Entity. The associated basic scheduling criteria can then be applied to the job. Parameter RELATIONSHIP appears only in job scheduling definitions in Group scheduling tables. Parameter RELATIONSHIP defines the relationship (AND/OR) between schedule tag criteria and the jobs own basic scheduling criteria (i.e., whether one, or both sets of criteria are to be satisfied). The Basic Scheduling parameters (except SCHEDULE TAG and RELATIONSHIP) are listed below by category. When defining basic scheduling criteria for jobs in regular or Group scheduling tables, or when defining basic scheduling criteria for Group Entities, the following rules apply to these categories of parameters:
Parameters must be selected from one and only one of the first three categories (A, B, or C). Parameters in the last two categories (D and E) are optional.
Category A MONTHS DAYS WDAYS CONFCAL Category B DATES WDAYS CONFCAL Category C Schedule the job if the number of free tracks in the specified partitioned dataset (PDS) is less than the minimum number of tracks specified. This set of criteria is intended for jobs/started tasks which clean, compress or enlarge libraries or which issue warning messages if the minimum number of free tracks is not available. PDS MINIMUM Category D RETRO Schedule the job even if the original scheduling date has passed. PDS to be checked for minimum number of tracks. Minimum number of tracks. Schedule the job on specified dates. Schedule the job on specified days of the week. Confirm scheduling days against a specified calendar. Schedule the job during the specified months. Schedule the job on specified days (in the above-specified months) and/or select days from a specified calendar. Schedule the job on specified days of the week (in the above-specified months) and/or select days from a specified calendar. Confirm scheduling days against a specified calendar.
35
Category E MAXWAIT D-CAT Maximum number of days to keep the job in the Active Jobs file awaiting execution after its original scheduling date has passed. CONTROL-D category of the job. (Documented as CATEGORY prior to CONTROL-M release 5.1.4.) the
Each Basic Scheduling parameter is described in this section. However, interrelationships between some of these parameters are described briefly below. DAYS/DCAL WDAYS/WCAL These parameters are all optional.
Parameter DAYS identifies days of the month on which the job should be scheduled (e.g., first day of the month, third working day of the month). Several formats are available for specifying DAYS values. Parameter WDAYS identifies days of the week on which the job should be scheduled (e.g., the first day of the week, the second day of each week). Several formats are available for specifying WDAYS values. A calendar name can be specified in the DCAL and/or WCAL fields. A calendar specifies working days days of the year on which a job can be scheduled. Calendars and the IOA Calendar facility are discussed in Section 2. When both the DAYS and DCAL parameters are specified, they work as a complementary unit, as described later in this section. Similarly, when both WDAYS and WCAL are specified, they also work as a complementary unit as described later in this section. When values for both DAYS (/DCAL) and WDAYS (/WCAL) are specified in the same job scheduling definition, the resulting schedule is determined by the value specified in field AND/OR. CONFCAL/SHIFT A calendar specified in CONFCAL is not used for job scheduling, but is used instead for validating a scheduled date. Only jobs which have satisfied all other specified basic scheduling criteria are checked against the CONFCAL calendar. If the day is a working day in the CONFCAL calendar, the job is scheduled on that day. Otherwise, the job is either shifted to (scheduled on) another day according to the value specified in parameter SHIFT, or the job is not scheduled (if no SHIFT value has been specified). CONFCAL calendars are especially useful for handling holidays and other scheduling exceptions. Defining a Schedule Internal Scheduling Logic When defining scheduling tables, it is useful to understand the IOA Scheduling facility logic which determines whether or not to order a job on a specific day. This logic is described below. 1. DAYS/DCAL parameters are checked independently and a first tentative scheduling decision is created. 2. WDAYS/WCAL parameters are checked independently and a second tentative scheduling decision is created.
36
3. A third tentative scheduling decision is created based on the above two decisions and the AND/OR value linking them. (If DAYS/DCAL are not specified, this third temporary scheduling decision is identical to the second scheduling decision. If WDAYS/WCAL are not specified, this third scheduling decision is identical to the first scheduling decision. 4. If CONFCAL/SHIFT are specified, this third scheduling decision is adjusted according to the CONFCAL/SHIFT criteria. 5. This third scheduling decision (as adjusted) becomes the final scheduling decision. The IOA Scheduling facility decides whether or not to schedule a job based on this final scheduling decision. Scheduling Jobs in Group Scheduling Tables The following scheduling algorithm applies to Group scheduling tables: 1. Before jobs in a group can be scheduled, the group must be eligible for scheduling (i.e., at least one of the tagged sets of basic scheduling criteria in the Group Entity has been satisfied). 2. If (and only if) the group is eligible for scheduling, each job scheduling definition in the scheduling table is individually checked for possible scheduling. For each job scheduling definition: 3. Schedule tags in the job scheduling definition are checked sequentially beginning with the first tag. If the criteria of a schedule tag are satisfied, no further checks are performed on the remaining schedule tags. The criteria belonging to the satisfied tag are used in the scheduling algorithm. 4. The RELATIONSHIP parameter (AND/OR) is checked. If a schedule tag was satisfied and the defined relationship is OR, the satisfied schedule tag is sufficient and the job is scheduled according to this tags criteria. No further checks are performed. If a schedule tag was not satisfied and the defined relationship is AND (i.e., the job requires that the schedule tag be satisfied), the job is not scheduled. No further checks are performed. If a schedule tag was satisfied and the defined relationship is AND, or if a schedule tag was not satisfied and the defined relationship is OR, the jobs basic scheduling criteria must be satisfied (i.e., the algorithm continues with the next step).
5. The jobs basic scheduling criteria are checked. If the jobs basic scheduling criteria are not satisfied, the job is not scheduled. If the jobs basic scheduling criteria are satisfied, the job is scheduled.
(The jobs basic scheduling criteria, not the scheduling tag criteria, are used for scheduling. This is a concern only if there are conflicting MAXWAIT values in the scheduling tag criteria and the jobs basic scheduling criteria. In this case, the MAXWAIT value from the jobs basic scheduling criteria is used.)
37
Job Production Parameters: General Runtime Scheduling Parameters Summary
Group Scheduling Flowchart
Runtime Scheduling Parameters Summary

Runtime Scheduling parameters define job submission criteria. The job will not be submitted unless all submission criteria are satisfied. The following criteria can be defined: IN CONTROL RESOURCE PIPE TIME PRIORITY DUE OUT CONFIRM Required prerequisite condition(s). Required exclusive or shared Control resources. Quantitative resources and the required quantity. Name of each dataset that will be replaced by a pipe during the run of the job. Available only at sites utilizing CONTROL-M/WorkLoad. Time range during which the job must be submitted. Job priority and critical path priority. Time by which the job must finish executing (which can determine the time by which the job must be submitted). Manual confirmation required before the job is submitted.
38
Job Production Parameters: General Post-processing Parameters Summary
Post-processing Parameters Summary

Actions to be performed after job execution generally depend on the results of the job execution:
Certain actions may be required when the job ends successfully. Certain actions may be required when the job fails, depending on the reason for failure. Certain actions may be required in any and all situations.
The CONTROL-M monitor tracks each job execution. Following a jobs termination, the CONTROL-M monitor checks the execution results of each step in the job. Based on the results, the CONTROL-M monitor determines a final status of the job. Either of two final job statuses can be assigned: OK NOTOK Job ended OK. This status is usually assigned when all steps in the job end with a condition code less than or equal to C0004. Job ended NOTOK. This status is assigned when any step ends with a condition code greater than or equal to C0005. It is also assigned if the job abends or is not run. The following statuses are subsets of end status NOTOK: JRUN EXERR JFAIL Job not run due to JCL syntax error. Execution error (i.e., after the job has started running). JCL error was encountered during job step initiation. This status is also a subset of status EXERR.
If a post-processing error occurs after a job ends OK (including FORCE OK), it indicates that there is a problem with the post-processing statements defined in the job scheduling definition. For example, a post-processing statement may have indicated an action that the owner of the job was not authorized to perform. Post-processing parameters can be divided into the following groups: Parameters Performed When the Job Ends OK OUT AUTO-ARCHIVE Adds or deletes prerequisite conditions. Archives sysout. Specifies retention criteria of a job in the History Jobs file. Specifies sysout processing.
RETENTION SYSOUT
Conditional Processing / Processing in All Situations Most conditional processing is specified via a combination of ON and DO statements. ON/DO statement definition consists of defining ON statement step/code events (e.g., ON PGMST STEP1 CODE C0016) followed by DO statement actions (e.g., DO SHOUT, DO FORCEJOB) which are performed when the ON step/code criteria are satisfied. A range of steps for use in the ON statement can be defined in parameter STEP RANGE.
39
Job Production Parameters: General Post-processing Parameters Summary
ON/DO statements also specify actions which should be performed in any and all cases. To ensure that the ON statement is activated for all step/code events, specify reserved word ANYSTEP as the ON step name and ***** as the ON code. DO statements allow specification of a wide variety of actions to be performed when the ON criteria are satisfied: DO OK DO NOTOK DO RERUN DO COND DO SYSOUT DO SHOUT DO FORCEJOB DO SET DO CTBRULE
R
Set the status of the step to OK. Set the status of the step to NOTOK. Rerun the job. Add/Delete prerequisite conditions. Handle sysout processing. Send a message. Force a job. Set the value of an AutoEdit variable. Activate a CONTROL-B rule. Perform CONTROL-R job restart.
DO IFRERUN
Special Case Post-processing Parameters SHOUT RERUN Sends a message to a specified destination in specified situations (e.g., if the job was submitted late). Parameters used only for automatic job rerun: MAXRERUN RERUNMEM INTERVAL Maximum number of times to rerun the job. Member containing the JCL to be used for rerun.
Minimum time interval between runs of a rerun or cyclic job (this parameter acts as a Runtime Scheduling parameter for the subsequent rerun/cyclic runs of the job).
Group Entity Post-processing Parameters The following parameter is found only in the Group Entity definition: ON GROUP-END Table-processing termination status which determines whether or not the accompanying DO statements are performed.
The following DO statements are permitted following an ON GROUP-END statement: DO COND DO FORCEJOB DO NOTOK Note DO OK DO SET DO SHOUT
Statements DO OK and DO NOTOK change the final status of the group (not the status of each job or job step in the group).
3 10
Job Production Parameters: Parameter Descriptions
Parameter Descriptions
Parameter descriptions are provided in alphabetical order in the following format: Purpose Format Purpose of the parameter. Graphic illustration of how the parameter appears in the Job Scheduling Definition screen, followed by a detailed description of the parameters format and, where relevant, subparameters and valid values. Detailed information about the usage and functioning of the parameter. Examples illustrating how the parameter might be used in a job scheduling definition.
General Information Examples
3 11
ADJUST CONDITIONS
General Job Parameter
ADJUST CONDITIONS
Determines whether or not to ignore the requirement for a prerequisite condition by successor jobs in a Group scheduling table (if the prerequisite condition was not added to the IOA Conditions/Resources file because a predecessor job in the group was not scheduled). This parameter appears in the Group Entity only and applies only to Group scheduling tables.
Format
Optional. Valid values are: Y (Yes) Ignore the requirement for an IN prerequisite condition normally added to the IOA Conditions/Resources file by a predecessor job if the predecessor job is not scheduled. Do not ignore the requirement for an IN condition. (No job in the group will be scheduled unless the jobs IN condition criteria are satisfied.) Default.
N (No)
General Information
This parameter is applied to all jobs in the Group scheduling table. It defines job dependencies in the group as being conditional or absolute. Absolute job dependency means that each job in a Group scheduling table should run only after all its predecessor jobs in the group have run. In this case, all prerequisite IN conditions for a job must exist in the IOA Conditions/Resources file before the job can run. To achieve absolute job dependency, specify a value of N for parameter ADJUST CONDITIONS. Conditional job dependency means that each job in the group should wait for its predecessor jobs to run only if the predecessor jobs in the group are scheduled. If the predecessor job which normally adds a prerequisite condition to the IOA Conditions/Resources file is not scheduled, the requirement for that prerequisite condition should be ignored so that the successor job can run (provided other runtime scheduling criteria are satisfied). In this case, specify a value of Y for parameter ADJUST CONDITIONS. Ignoring an IN condition affects only the job order. The ignored condition does not appear in the Zoom screen. The original job scheduling definition remains unchanged.
3 12
ADJUST CONDITIONS
Example
If a predecessor job is not scheduled, successor job orders will ignore the requirement for the prerequisite conditions the predecessor job would have normally placed in the IOA Conditions/Resources file.
GRP ACCOUNTS_GROUP CTM.PROD.SCHEDULE(GRP) COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ GROUP ACCOUNTS_GROUP MEMNAME ACCOUNTS OWNER N04B APPL DESC ADJUST CONDITIONS Y SET VAR DOCMEM ACCOUNTS DOCLIB CTM.PROD.DOC =========================================================================== SCHEDULE TAG ALL_DAYS DAYS ALL DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 =========================================================================== SCHEDULE TAG SUNDAYS DAYS 01 DCAL AND/OR WDAYS WCAL USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 16.44.31
3 13
APPL
APPL
Descriptive name of the application to which the jobs group belongs. Used as a common descriptive name for a set of related groups (of jobs).
Format
APPL specifies an application name of 1-20 characters. Only trailing blanks are allowed. By default (which can be modified in the User Profile), the parameter is optional.
General Information
The parameter facilitates the handling of groups of production jobs. Note Use of parameter APPL is highly recommended to facilitate implementation of 1 Enterprise Controlstation functions and future CONTROL-M options.
See the Enterprise Controlstation User Guide
for details.
3 14
APPL
Example
Job OPERCOMP belongs to group MAINTENANCE, which is part of application OPER.
JOB: OPERCOMP LIB CTM.PROD.SCHEDULE TABLE: OPER COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME OPERCOMP MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP MAINTENANCE DESC JOB RUN ON THE 1ST OF THE MONTH OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM OPERCOMP DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE INIT 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 15
AUTO-ARCHIVE
PostProcessing Parameter
AUTO-ARCHIVE
Controls SYSDATA archiving.
Format
R
Optional. Parameter AUTO-ARCHIVE consists of the following subparameters: AUTO-ARCHIVE Determines whether or not SYSDATA is to be archived. Valid values are: Y (Yes) N (No) Archive SYSDATA. Default. Do not archive SYSDATA. If this value is specified for a job, CONTROL-R restart of the job and SYSDATA viewing under CONTROL-M will not be possible.
SYSDB
Determines whether all SYSDATA outputs are to be archived to one pre-designated dataset or whether each SYSDATA output is to be archived to its own dataset. Valid values: Y (Yes) SYSDATA of all jobs containing a SYSDB value of Y are archived to a common dataset. When the common dataset is full, another is automatically allocated and used by the system. This is the recommended method (see below). Default. SYSDATA of each job containing a SYSDB value of N is archived to a unique dataset.
N (No) MAXDAYS
Maximum number of days to retain archived SYSDATA value for jobs ended NOTOK. Must be a 2-digit number in the range 00 98 or 99. 99 means retain for an unlimited number of days (until deleted by request). Maximum number of runs for which the archived SYSDATA should be retained when the job ended NOTOK. Must be a 3-digit number in the range of 000 998 or 999. 999 means retain the SYSDATA of all runs.
MAXRUNS
3 16
AUTO-ARCHIVE
General Information
Subparameter AUTO-ARCHIVE allows you to decide whether or not to archive SYSDATA. (For a definition of SYSDATA, see SYSDATA in Section 1 of this manual.) While archiving SYSDATA is normally desirable, it might not be desirable for cyclic jobs, started tasks, or frequently repeated jobs that do not require restart. If archiving, subparameter SYSDB allows you to decide whether SYSDATA for different jobs should be archived to a common dataset (Y) or whether a separate dataset should be used for each run (N). If Y is specified, a single archived SYSDATA dataset is used for archiving until it is full. Then, another SYSDATA dataset is allocated and used. This is the recommended method. Creating a separate dataset for each run is not recommended because:
Creating many datasets consumes a large amount of space in the disk VTOC. Each dataset is allocated on a track basis. If the SYSDATA does not completely fill the track, large amounts of disk space may be wasted.
Subparameters MAXDAYS and MAXRUNS define retention criteria for the archived SYSDATA of jobs that ended NOTOK. Defaults are defined in the CONTROL-R installation parameters. You can specify either or both parameters to override the defaults. If both parameters are specified, retention is limited by the condition which is fulfilled first. When archiving SYSDATA, it is highly recommended that value 99 not be specified in parameter MAXWAIT (described in this section) for cyclic jobs/started tasks. Otherwise, these jobs, which are never automatically deleted from the Active Jobs file, can cause the disk to fill up with unnecessary archived SYSDATA. Notes Specified parameters take effect only during execution of the New Day procedure (CONTDAY) or utility CTMCAJF. Therefore, it is possible to find more generations of the same job than the current value of MAXRUNS. Whenever a job is deleted from the Active Jobs file, its SYSDATA is deleted regardless of MAXDAYS or MAXRUNS.
3 17
AUTO-ARCHIVE
Example
Archive the SYSDATA to a common dataset. Retain the archived SYSDATA for 7 days or 20 runs, whichever occurs first.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS 07 MAXRUNS 020 RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION
11.17.00
3 18
CONFCAL
Basic Scheduling Parameter
CONFCAL
Name of a calendar used to confirm the scheduling of the job. See also DAYS, WDAYS and DATES.
Format
Optional. CONFCAL subparameters are described below. Note If the new (expanded) portion of the SHIFT subparameter is not used, CONFCAL and SHIFT work as they did in previous releases. If this new portion is used, CONFCAL and SHIFT work differently. Specifies a valid calendar (member) name of 1-8 characters. A calendar specified in CONFCAL is used for:
CONFCAL
Validating scheduling dates.

and/or
Determining the scheduled work day.

Jobs to be scheduled on a day, based on other specified Basic Scheduling criteria, are checked against the CONFCAL calendar:
If the day is a working day in the CONFCAL calendar, the job is

tentatively scheduled on that day. (This day is referred to below as the original scheduling date.) Actual scheduling of the job is then determined by the value specified for subparameter SHIFT.
If the day is not a working day in the CONFCAL calendar, the SHIFT
subparameter is checked. Depending on the SHIFT value, the job may be scheduled on an earlier or later day, may be scheduled on that day, or may be cancelled.
3 19
CONFCAL
SHIFT
Determines when and if the job should be scheduled. Optional. Note If no CONFCAL calendar is specified, no value can be specified for subparameter SHIFT, and this field has no effect on job scheduling.
The value specified for subparameter SHIFT has the following format: xyyy where: x How to shift scheduling of the job if the original scheduling day of the job is not a working day in the CONFCAL calendar. Valid values: blank > No shifting occurs. The job is not scheduled. Default. Job scheduling is shifted to the next working day in the CONFCAL calendar. Additional shifting may or may not be performed, depending on the yyy value (described below). Job scheduling is shifted to the previous working day in the CONFCAL calendar. Additional shifting may or may not be performed, depending on the yyy value (described below). Tentatively schedule the job for the current day (even if not a working day). Additional shifting may or may not be performed, depending on the yyy value (described below). Prior to CONTROL-M Release 5.1.4, subparameter SHIFT consisted of only the x value.
<
Note
yyy
Shifts scheduling of the job forward or backward the specified number of working days (as defined in the CONFCAL calendar). Valid values: blank Do not reshift job scheduling. Default. If the original scheduling day is a working day, no shifting occurs. If the original scheduling day is not a working day, no shifting, beyond that indicated by the x value, occurs. +nn Shift job scheduling forward to next nth working day.
3 20
CONFCAL
nn
Shift job scheduling backward to the previous nth working day.
A value from 62 to +62 can be specified. Note If the result of shifting by yyy days is a day which is not allowed (i.e., n was specified for that day in the DAYS parameter of the job scheduling definition), the job is shifted again to the next allowed working day (for a forward shift) or to the previous allowed working day (for a backward shift).
The interaction between the x value and the yyy value is as follows:
If the original scheduling day of the job is a working day in the

CONFCAL calendar, the x value is ignored and the yyy value determines when the job is scheduled.
If the original scheduling day of the job is not a working day in the
CONFCAL calendar, job scheduling is shifted according to the x value and then shifted again according to the yyy value (if specified) to determine when the job is scheduled. Note If the original scheduling day is not a working day and the x value is blank, the job is not scheduled (regardless of whether or not a yyy value is specified).
General Information
CONFCAL calendars are especially useful for handling holidays and other scheduling exceptions. If not specified, jobs are scheduled according to other basic scheduling criteria without confirmation. CONFCAL should not contain the name of a periodic calendar. If it does, no day will pass the confirmation. Parameter CONFCAL cannot be used with parameters PDS and MINIMUM.
3 21
CONFCAL
Example
This example is based on the following assumptions:
The current month is January 1998. Working days are defined in calendar WORKDAYS which contains the following working days (indicated by Y) for January 1998:
------S-------------S-------------S-------------S-----------1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 N Y N N Y Y Y Y Y N N Y Y Y Y Y N N Y Y Y Y Y N N Y Y Y Y Y N
Start of the week is defined as Monday.
Schedule the job for three working days after each Thursday, if Thursday is defined as a working day in calendar WORKDAYS. If Thursday is a holiday, shift the job one working day forward and reschedule the job three working days after the following workday.
WDAYS 4 CONFCAL WORKDAYS SHIFT >+03
The job is scheduled on the days of the month indicated by an asterisk:

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA
In this example, a holiday occurs on Thursday, January 1st. The > value shifts the job to Friday the 2nd (the next working day according to the CONFCAL calendar). The +03 value then shifts scheduling of the job three working days forward to Wednesday, January 7th.
3 22
CONFIRM
Runtime Scheduling Parameter
CONFIRM
Ensures manual confirmation before the job is submitted.
Format
Optional. Valid values: Y (Yes) Confirmation required. The job is not submitted unless manual confirmation is entered in the Status screen. No confirmation required. The job can be automatically submitted by CONTROL-M without manual confirmation. Default.
N (No)
General Information
If CONFIRM = Y, the job appears in the Status screen with a WAIT CONFIRMATION (FOR SCHEDULE) status. Option C (Confirm) must then be specified in the Status screen for the job to be submitted. When the job is confirmed in the Status screen, the CONFIRM value in the Zoom screen changes to N. If CONFIRM = N or blank, the job is automatically submitted by CONTROL-M at the first available opportunity. Note In the case of cyclic jobs, confirmation applies to the first run only. Once confirmed, the job will be recycled without waiting for subsequent confirmation.
3 23
CONFIRM
Example
Job OPERCOMP requires manual confirmation in order to be eligible for submission. Manual confirmation can be provided from the Status screen once the job is displayed with a status of WAIT CONFIRMATION (FOR SCHEDULE).
JOB: OPERCOMP LIB CTM.PROD.SCHEDULE TABLE: OPER COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME OPERCOMP MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP MAINTENANCE DESC JOB RUN ON THE 1ST OF THE MONTH OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM OPERCOMP DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE INIT 0001 PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM Y USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 24
CONTROL
CONTROL
Ensures exclusive and/or shared control over runtime resources.
Format
Optional. A maximum of two resources can be specified in each CONTROL line. Upon specifying the second resource in a CONTROL line and pressing <ENTER>, a new line is opened (for specifying additional resources). Each CONTROL specification consists of the following mandatory subparameters: res-name state User-supplied, descriptive name of 120 characters used to identify the resource. Type of control the job requires of the resource. Valid values: E S The job requires exclusive control of the resource during processing. The job requires shared control of the resource during processing.
General Information
Parameter CONTROL is used to control parallel execution of jobs. If a job requires a resource in exclusive state, it cannot share usage of that resource with another job (i.e., the jobs cannot run in parallel). For example:
If JOBA requires exclusive control of a resource which is already in use by a different job, JOBA must wait until the other job frees the resource regardless of whether the other job is using the resource in shared or exclusive state. If JOBA already has exclusive control of a resource, any job requiring that resource must wait until JOBA frees the resource, regardless of whether the job requires the resource in shared or exclusive state.
If a job requires a resource in shared state, that job can run in parallel with other jobs requiring the same resource in shared state. For example:
3 25
CONTROL
If JOBA requires shared control of a resource which is already in shared use by a different job(s), JOBA can use that resource at the same time. If JOBA already has shared control of a resource, any job requiring that same resource in shared state can use that resource at the same time.
However:
If JOBA requires shared control of a resource which is already in exclusive use by a different job, JOBA must wait until the other job frees the resource. If JOBA already has shared control of a resource, any job requiring that same resource in exclusive state must wait until JOBA frees the resource.
For more information, see Quantitative and Control Resources in Section 1 of this manual.
Example
The following three screens (job definitions) indicate how parameter CONTROL can control resource usage. All three job definitions require resource (disk) DISK-VS0020:
The first job, BKPVS020, is a backup job which requires exclusive control of disk DISK-VS0020. The other two jobs, CMPRSJOB and CMPRSSRC, are both compress jobs. They do not require exclusive control (i.e., they can share control) of disk DISK-VS0020.
The result is as follows:
Jobs CMPRSJOB and CMPRSSRC can be run in parallel with each other, but neither can run in parallel with job BKPUS020. If job BKPVS020 is running, jobs CMPRSJOB and CMPRSSRC must wait. If either job CMPRSJOB and/or CMPRSSRC is running, job BKPVS020 must wait.
3 26
CONTROL
This is the first of the three jobs in the example (job BKPVS020).
JOB: BKPVS020 LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME BKPVS020 MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP BACKUP DESC FULL VOLUME BACKUP OF DISK VS0020 OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM BKPVS020 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS 3,0 WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL DISK-VS0020 E RESOURCE USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
This is the second of the three jobs in the example (job CMPRSSRC).
JOB: CMPRSSCR LIB CTM.PROD.SCHEDULE TABLE: OPMAINT COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME CMPRSSCR MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP OPER-MAINT DESC COMPRESS JOB OF GSD.DEPO.SCR OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM CMPRSSCR DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01 DCAL AND/OR WDAYS WCAL MONTHS 123456789101112DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM 025 PDS GSD.DEPO.SCR =========================================================================== IN CONTROL DISK-VS0020 S RESOURCE USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 27
CONTROL
This is the third of three jobs in the example (job CMPRSJOB).

JOB: CMPRSJOB LIB CTM.PROD.SCHEDULE TABLE: OPMAINT COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME CMPRSJOB MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP OPER-MAINT DESC COMPRESS JOB OF GSD.DEPO.JOB OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM CMPRSJOB DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 123456789101112DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM 020 PDS GSD.DEPO.JOB =========================================================================== IN CONTROL DISK-VS0020 S RESOURCE USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 28
CTB STEP
CTB STEP
Adds CONTROL-B steps as the first and/or last step of the jobs execution.
Format
Optional. Parameter CTB STEP consists of the following subparameters: AT Indicates where to place the CONTROL-B step in the job. Mandatory. Valid values: START END NAME TYPE The indicated CONTROL-B step should become the first step of the job. The indicated CONTROL-B step should become the last step of the job.
Name of the CONTROL-B entity. Must be a valid name of a CONTROL-B rule or mission. Mandatory. Type of CONTROL-B entity. Mandatory. Valid values: RULE MISSION Entity is a CONTROL-B rule. Entity is a CONTROL-B mission.
ARGUMENTS Note
Arguments to be passed to the CONTROL-B step. Optional.
The ARGUMENTS line is not displayed until the CTB STEP line is filled in and <ENTER> is pressed.
General Information
A maximum of two CTB STEP statements (i.e., one START statement and one END statement) can be specified. Upon filling in the first CTB STEP line on the screen and pressing <ENTER>, the ARGUMENTS line and the second CTB STEP line are displayed. If the second CTB STEP line is filled in and <ENTER> is pressed, its ARGUMENTS line is displayed.
3 29
CTB STEP
Multiple arguments must be separated by a comma without a space because they are automatically passed to the CONTROL-B step as a PARM=arguments parameter in the steps JCL. CONTROL-M uses the status returned by CONTROL-B as it would use the return status of any job step.
If CONTROL-B returns a status of OK or TOLER (within accepted tolerances), CONTROL-M considers the step as having ended OK. f CONTROL-B returns a status of NOTOK or ABEND, CONTROL-M considers the job step as having ended NOTOK.
Example
After successfully performing salary calculations, job SACALC01 invokes rule CHKCALC to ensure that the results are reasonable, and then sets OUT condition SALARY-OK.
JOB: SACALC01 LIB CTM.PROD.SCHEDULE TABLE: SALARY COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME SACALC01 MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL SAL GROUP SALARY DESC SALARY CALCULATIONS OVERLIB SET VAR CTB STEP AT END NAME CHKCALC TYPE RULE ARGUMENTS %%ODATE CTB STEP AT NAME TYPE DOCMEM SACALC01 DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01,15 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT SALARY-OK ODAT + USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 30
D-CAT
D-CAT
Name of a CONTROL-D report decollating mission category that should be scheduled under CONTROL-D when the job is scheduled under CONTROL-M. Note Prior to CONTROL-M Release 5.1.4, parameter D-CAT was called CATEGORY.
Format
Optional. Parameter D-CAT must be 1-20 characters, or * for all categories. If this parameter is specified when CONTROL-D is not installed, New Day processing stops immediately after this job. (See Section 6 of this manual for a description of New Day processing.)
General Information
If the parameter is specified, whenever the job is scheduled, a search is made in the CONTROL-D report decollating mission library for a job (member) with the name specified in parameter MEMNAME (described in this section) and with the same category. (No search is made in the case of job restarts.) The selected category is forced and placed in the CONTROL-D Active Missions file (i.e., the jobs output should be decollated by CONTROL-D). If D-CAT is set to *, all categories of the 2 job are forced under CONTROL-D.
If optional wish WM0983 is applied at your site, selected categories are scheduled (i.e., not forced).
3 31
D-CAT
Example
The job output should be decollated by the CONTROL-D report decollating mission category DAILY.
JOB: GNRLDR12 LIB CTM.PROD.SCHEDULE TABLE: GNRLDR COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME GNRLDR12 MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL GENERAL GROUP GENERAL-LEDGER DESC GENERAL LEDGER DAILY REPORTS OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM GNRLDR12 DOCLIB CTM.PROD.DOC =========================================================================== DAYS ALL DCAL WORKDAYS AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT DAILY MINIMUM PDS =========================================================================== IN CONTROL RESOURCE USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 32
DATES
DATES
Dates, by month and day, on which the job should be scheduled for execution.
Format
Optional. Valid values are 4-character dates, in either mmdd or ddmm format, depending on the site standard. A maximum of 12 dates can be specified.
General Information
The job is scheduled for execution only on the dates specified in parameter DATES. Parameter DATES cannot be used with parameters PDS, MINIMUM, MONTHS, DAYS, and DCAL. To specify more than 12 dates for one job, define the dates in a calendar (instead of using this parameter) and specify the calendar in subparameter DCAL (or WCAL). The relationship between DATES and WDAYS/WCAL is OR. If the job should be scheduled according to the DATES parameter or according to the WDAYS/WCAL combination, it will be scheduled.
3 33
DATES
Example 1
Schedule a job for the 15th of January (mmdd format).
DATES 0115
Example 2
Schedule job PRDKPL01 for the 21st of June and the 21st of December (ddmm format).
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME PRDKPL01 MEMLIB CTM.PROD.JCL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL KPL GROUP PROD-KPL DESC DAILY PRODUCTION - START OF APPL-PROD-KPL OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM PRDKPL01 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES 2106 2112 CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN START-DAILY-PROD-KPL ODAT CONTROL DB2-MAIN-FILE E RESOURCE INIT 0001 CARTRIDGE 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 34
DAYS
DAYS
Days of the month on which the job should be scheduled. See also WDAYS and CONFCAL.
Format
Optional. Parameter DAYS specifies days of the month on which the job should be scheduled, provided other basic scheduling criteria are met. Values for DAYS can be specified alone, or they can be specified together with a calendar specified in subparameter DCAL. DAYS/DCAL can also be specified together with WDAYS/WCAL (described under WDAYS in this section of the manual). Parameter DAYS consists of the following subparameters: DAYS Days of the month on which to schedule a job. (The months in which to order jobs are specified in parameter MONTHS, described later in this section.) Various formats (described later) can be used to specify DAYS (e.g., 2 means the second day of the month, L2 means the day before the last day of the month, D1PA means the first day in period A). Name of a calendar containing a predefined set of dates (referred to as working days) on which a job should be scheduled. A specified value must be either a valid member name of 1-8 characters, or an * to indicate that the calendar specified in parameter CONFCAL should be used for scheduling. See the IOA Calendar facility in Section 2 of this manual for more information on how to define, use and modify calendars. Notes A calendar specified in DCAL does not have to exist when defining parameter DAYS. It must exist when the job is being ordered. Existing job definitions from previous releases which specify DAYS values and a DATEMEM calendar will automatically have the calendar name placed in the DCAL field when accessed by this CONTROL-M release.
DCAL
3 35
DAYS
AND/OR
Conjunctional parameter used to link parameters DAYS and WDAYS when both are specified. A (AND) O (OR) Both DAYS (/DCAL) and WDAYS (/WCAL) criteria must be met in order for a job to be scheduled. DAYS (/DCAL) and/or WDAYS (/WCAL) criteria must be met for a job to be scheduled. Default.
If A (AND) is specified when either DAYS or WDAYS is specified (but not both), the missing DAYS or WDAYS value is automatically set to ALL. Assuming all other basic scheduling criteria are met:
When DAYS are specified without DCAL, the job is scheduled on the specified days (in the specified months). When DCAL is specified without DAYS, the job is scheduled on all working days marked in the DCAL calendar. When DAYS and DCAL are both specified, scheduling depends on the combination of working days defined in the calendar and the values/format of parameter DAYS (described below). When both DAYS and WDAYS criteria are specified, scheduling depends on the AND/OR subparameter connecting them.
Valid Formats for DAYS

Valid formats for parameter DAYS, and how they relate to DCAL, are described below. In the following non-periodic scheduling formats:
n is any integer from 1 to 31. Multiple values can be expressed (separated by commas) in any order. DCAL should not contain the name of a periodic calendar. All days of the month. If ALL is specified, other DAYS values cannot be specified with it. If a DCAL calendar is not defined, schedule the job on all days in the month. If a DCAL calendar is defined, schedule the job only on the working days indicated in the calendar.
ALL
n,...
Specific days of the month. If a DCAL calendar is not defined, schedule the job on the specified days. If a DCAL calendar is defined, schedule the job only when a day is defined as a working day in both the DAYS parameter and the DCAL calendar.
+n,...
Days of the month in addition to the working days specified in the DCAL calendar. DCAL is mandatory.
3 36
DAYS
n,...
Days of the month on which a job cannot be ordered. These values take precedence over all other Basic Scheduling parameters (i.e., the job is not ordered, even if schedulable according to DCAL calendar working days, WDAYS, or other criteria). DCAL is mandatory. Order the job on the indicated day if it is a working day in the DCAL calendar; otherwise, order the job on the next working day that is not negated by a n value in this parameter. This format is frequently used for holiday handling. DCAL is mandatory. Order the job on the indicated day if it is a working day in the DCAL calendar; otherwise, order the job on the last previous working day that is not negated by a n value in this parameter. This format is frequently used for holiday handling. DCAL is mandatory. Order the job on the nth working day from the beginning of the month. DCAL is mandatory. Order the job on all working days except the nth working day from the beginning of the month. DCAL is mandatory. Order the job on the nth day (or nth working day if DCAL is defined) counting backward from the end of the month. DCAL is optional. If DCAL is defined, order the job on all working days except the nth working day counting backward from the end of the month. If DCAL is not defined, order the job on all days except the nth day counting backward from the end of the month. DCAL is optional.
>n,...
<n,...
Dn,... Dn,... Ln,... Ln,...
In the following periodic scheduling formats:
n is any integer from 1 to 63, and i is any valid period identifier. If the number of days between periods with the same identifier is more than 33 (this value can be changed by the IOA administrator), it is considered a new period. The name of a periodic calendar must be specified in DCAL. See IOA Calendar Facility in Section 2 for details about periodic calendars. Order the job on the nth day of period i from the beginning of the period. An * can be specified as the n value to represent all days and/or as the i value to represent all periods. Order the job on all days of period i except the nth day of period i from the beginning of the period. An * can be specified as the i value to represent all periods. Order the job on the nth day of period i counting backward from the last day of the period. An * can be specified as the i value to represent all periods. Order the job on all days of period i except the nth day of period i counting backward from the last day of the period. An * can be specified as the i value to represent all periods.
DnPi,...
DnPi,...
LnPi,...
LnPi,...
3 37
DAYS
General Information
Negative values take precedence over positive values when determining whether or not a job should be scheduled on a certain date. If a negative value (i.e., format n, Dn, Ln, DnPi, or LnPi) in either the DAYS or WDAYS field prevents a job from being scheduled on a date, the job will not be scheduled on that date even if a positive value (e.g., Ln) would otherwise result in the job being scheduled on that date. A maximum of eight periodic values (i.e., of type DnPi, DnPi, LnPi, and LnPi) can be designated in any desired order. If periodic and non-periodic values are mixed when specifying parameter DAYS, processing will depend on the calendar type specified in parameter DCAL:
If a non-periodic calendar is specified in DCAL, only non-periodic values in parameter DAYS are processed; periodic values are ignored. In this case, negative periodic values (i.e., DnPi, LnPi) are also ignored and do not supersede other values. If a periodic calendar is specified in DCAL, all periodic values in parameter DAYS are processed and all non-periodic values are ignored.
Parameter MONTHS is ignored when periodic values are specified in parameter DAYS. Parameter DAYS cannot be used with parameters PDS, MINIMUM, and DATES.
Examples
The examples in this section are based on the following assumptions:
The current month is August 1998. Working days are defined in calendar WORKDAYS which contains the following working days (indicated by Y) for August 1998. WDAYS are defined as days beginning on Monday.
---S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Periodic calendar PERIDAYS contains the following periodic definition for August 1998. These examples assume that all other days of this calendar are blank.
---S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 B C A A B B C A A B B C A A B B C A A B B
Start of the week is defined as Monday. Weeks start on the following dates in August 1998: 3rd, 10th, 17th, 24th, and 31st.
At the end of each example, asterisks in a August 1998 calendar indicate the days on which the job is scheduled.
3 38
DAYS
Example 1
Schedule the job on the 17th day and the last day of the month.
DAYS 17,L1

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO
Example 2
Schedule the job on all working days of the month except the 6th day of the month, and also schedule the job on the 1st day of the month.
DAYS DCAL +1,-6 WORKDAYS

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO * * * * * * * * * * * * * * * * * * * * *
Example 3
Schedule the job on all working days of the month except the first and last working days, and except the 17th day, of the month.
DAYS DCAL -D1,-17,-L1 WORKDAYS

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO * * * * * * * * * * * * * * * * * *
Example 4
Schedule the job on the 8th day of the month. If it is not a working day, schedule the job on the closest preceding working day.
DAYS DCAL <8 WORKDAYS

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO *
3 39
DAYS
Example 5
Schedule the job on the 1st day of period A, and on all days, except the 2nd day, of period B. Do not schedule the job on the 5th day of the month.
DAYS DCAL -5,D1PA,-D2PB PERIDAYS

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO * * * * * * * *
Example 6
Schedule the job on each Monday and on the 1st day of the month.
DAYS AND/OR WDAYS 1 OR 1

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO * * * * * *
Example 7
Schedule the job on the 3rd day of the month provided it is a Monday.
DAYS AND/OR WDAYS 3 AND 1

Example 8
Schedule the job on the last Monday of the month.
DAYS AND/OR WDAYS L1,L2,L3,L4,L5,L6,L7 AND 1

3 40
DAYS
Example 9
Schedule the job on the 1st, 7th and 15th days of the month if they are both Saturdays and working days. If the day of the month (1st, 7th, 15th) is not a Saturday, do not schedule the job. If the day of the month is a Saturday, but it is not a working day, schedule the job on the next working day.
DAYS AND/OR WDAYS CONFCAL SHIFT 1,7,15 AND 6 WORKDAYS >

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO * *
Example 10
Schedule the job to run on the first Friday after the 15th of the month.
DAYS AND/OR WDAYS 16,17,18,19,20,21,22 AND 5

3 41
DESC
DESC
Description of the job to be displayed in the Job List screen.
Format
Optional. Parameter DESC specifies text of 1-50 characters.
General Information
Parameter DESC is informational. It does not affect job processing. The description specified in parameter DESC appears to the right of the job name in the Job List screen. It is intended to let the user know the purpose of (or some other key information about) the job. The text can be specified in any language. Note If the current job was converted from another job scheduling product (e.g., CA-7), the string SCHEDULE-PREV-DAY or SCHEDULE-PREV-ONLY may appear in the DESC field for the job group. This string causes all scheduled runs of the job to be shifted back one day.
To specify more detailed job documentation, see Job Documentation in Section 2 of this manual.
3 42
DESC
Example
Job OPERCOMP will appear in the Job List screen with the description: JOB RUN ON THE 1ST OF THE MONTH.
JOB: OPERCOMP LIB CTM.PROD.SCHEDULE TABLE: OPER COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME OPERCOMP MEMLIB CTM.PROD.JCL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP MAINTENANCE DESC JOB RUN ON THE 1ST OF THE MONTH OVERLIB SET VAR@SCREENTEXT = CTB STEP AT NAME TYPE DOCMEM OPERCOMP DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE INIT 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 43
DO statement
DO statement
Actions to perform when the ON step/codes event criteria are satisfied.
Format
Optional. Specify DO statements as follows:
Type the action keyword (e.g., COND) in the DO field and press <ENTER>. In many cases, subparameter fields will be displayed. Fill in the subparameter(s) and press <ENTER> again.
Multiple DO statements can be specified. After entering a DO statement, another DO line is automatically displayed. The following are valid DO actions. Each is discussed in detail, later. DO COND DO CTBRULE Adds and/or deletes prerequisite conditions. Invokes a CONTROL-B rule.
DO FORCEJOB Forces one or more jobs under CONTROL-M. DO IFRERUN
R
DO NOTOK DO OK DO RERUN DO SET DO SHOUT DO SYSOUT
Specifies CONTROL-R restart parameters if a rerun is necessary for the job. Sets the job step status to NOTOK. Sets the job step status to OK. Reschedules the job (for rerun). Sets the value of an AutoEdit variable. Sends a message to a specified destination. Handles of the jobs output.
3 44
DO statement
General Information
DO statements are generally paired with preceding ON PGMST/PROCST/CODES statements (described later in this section). Their implied relationship is: IF THEN On step/codes-event criteria (specified PGMST/PROCST/CODES statements) are satisfied, Perform all actions specified in the DO statements. in the ON
All specified DO statements have an AND relationship. To add an empty DO statement between two existing DO statements, type the > character over the first letter in the DO field of the earlier DO statement, and press <ENTER>.
Example
DO >OND
OND is restored to its original value when <ENTER> is pressed (e.g., the > character disappears). To delete unwanted DO statements, either delete the DO keyword and press <ENTER> or specify appropriate Line Editing commands in the Edit environment (described in Appendix A).
3 45
DO COND
DO COND
Add or delete prerequisite conditions if the accompanying ON step/code criteria are satisfied. Note Statements DO COND and OUT are similar. If you are familiar with one of them, you can easily use the other. You should, however, be familiar with the differences outlined below in OUT/DO COND Differences.
Format
Optional. Type COND in the DO field and press <ENTER>. Fields are provided for the subparameters described below. A maximum of two prerequisite conditions can be specified in each DO COND line. Upon specifying one or two prerequisite condition in a line and pressing <ENTER>, a new line is opened (for specifying additional DO statements). Each DO COND statement consists of the following mandatory subparameters: cond-name User-supplied, descriptive name of 1-20 characters used to identify the condition. Note A condition name should not begin with the | symbol and should not contain parentheses () because these characters are used in defining Boolean logic for conditions.
dateref
4-character date reference. Valid values: date ODAT PREV Specific date (in either mmdd or ddmm format, depending on the site standard). Resolves to the original scheduling date. Default. Resolves to the previous date on which the job should have been scheduled, according to its basic scheduling criteria (or ODATE1 for a forced job).
3 46
DO COND
NEXT
Resolves to the next date on which the job will be scheduled, according to its basic scheduling criteria (or ODATE+1, for a forced job.). Static. Indicates that the condition (e.g., IMS-ACTIVE) is not date-dependent. STAT replaces the 0101 date values specified for such conditions prior to IOA Release 5.0.0. Although 0101 can still be specified, STAT is preferred because it cannot be confused with an actual date. Any scheduling date. Valid only with opt= . Any scheduling date. Valid only with opt= .
STAT
Note
**** $$$$
If a date reference is not specified, the value ODAT is automatically inserted upon pressing <ENTER>. opt Indicates whether to add or delete the specified prerequisite condition. Valid values: + Add (create) the prerequisite condition Delete the prerequisite condition
General Information
When a DO COND statement is activated, the specified prerequisite condition(s) are added to or deleted from the IOA Conditions/Resources file according to the specified opt value. Prerequisite conditions are usually used to establish job dependencies or ensure manual intervention when required.
To establish a job dependency, define a prerequisite condition in an OUT or DO COND statement in the job that should run first, and in an IN statement in the job that should run afterwards. The job containing a prerequisite condition in its IN statement is not submitted unless that prerequisite condition has been added manually or by the job containing an OUT or DO COND statement. An OUT statement is used to add the prerequisite condition if the job ends OK. Statement DO COND to add the prerequisite condition if the step/codes event criteria specified in the accompanying ON statement are satisfied.
If the IN prerequisite condition can only be satisfied by manual intervention (e.g., TAPE1-ARRIVED is set by the operator after an external tape has arrived on-site), performance of the required manual intervention before job submission is ensured.
OUT and DO COND statements can also be used to delete prerequisite conditions. The jobs OUT statement can be used to delete the prerequisite condition after the job ends OK. A DO COND statement can be used to delete prerequisite conditions if the accompanying ON step/code criteria are satisfied.
3 47
DO COND
These statements are generally used to delete prerequisite conditions either to prevent a particular job from running or when the condition is no longer needed by any other jobs in the Active Jobs file. DO COND functions are performed after the functions of the OUT parameter.
If a prerequisite condition is added by the OUT parameter and deleted by the DO COND parameter, the combined effect is the deletion of the prerequisite condition. If a prerequisite condition is deleted by the OUT parameter and added by the DO COND parameter, the combined effect is the addition of that prerequisite condition.
(For more information, see descriptions of parameters IN, ON and OUT in this section.) The following are examples of prerequisite conditions:
IMS-ACTIVE JOB_PAYCALC_ENDED_OK TAPE1_LOADED
All prerequisite conditions are associated with a date reference which is used to distinguish between different runs of the same job with different scheduling dates. If, for example, a condition is being deleted, only the condition matching the specified date will be deleted. The same condition associated with a different date will not be deleted. When adding or deleting prerequisite conditions, the date associated with the prerequisite condition can be a specific 4-character date or one of the following symbolic dates: ODAT PREV STAT NEXT **** / $$$$ Adds or deletes the prerequisite condition with the original scheduling date of the job. Adds or deletes the prerequisite condition with the previous scheduling date of the job (or ODATE1 for a forced job). Adds or deletes prerequisite condition with the date value STAT. Adds or deletes the prerequisite condition with the next scheduling date of the job (or ODATE+1 for a forced job). Valid only when deleting prerequisite conditions. Either of these values results in the deletion of all matching prerequisite conditions regardless of date.
Prerequisite conditions created by statement DO COND can trigger the execution of other jobs or processes. Prerequisite conditions deleted by statement DO COND can prevent the execution of jobs and processes whose IN statements require those prerequisite conditions. If two or more DO COND statements are contradictory, statements performed earlier are overridden by statements which are performed later. For more information regarding prerequisite conditions, see Prerequisite Condition Concept in Section 1 of this manual.
3 48
DO COND
OUT / DO COND Differences Statements OUT and DO COND have the following differences:
Statement OUT is applied only if the job ends OK. DO COND statements are associated with accompanying ON statements and are applied only if the accompanying ON step/code criteria are satisfied. An OUT statement appears in each job scheduling definition. No DO COND statement appears unless specified. To specify a DO COND statement, type COND in an empty DO field and press <ENTER>. DO COND statements are processed after OUT statements and can therefore override OUT statements. MVS restart can only be requested from an OUT statement, not a DO COND statement.
Example
The following example provides a simplified demonstration of how CONTROL-M can be used to monitor IMS. Prerequisite conditions, CHANGE-ACCUMULATION and LOGCLOSE-NEEDED, can be used as IN prerequisite conditions to trigger the execution of IMS maintenance jobs which depend on those conditions.
JOB: IMSPROD LIB CTM.PROD.SCHEDULE TABLE: IMSPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT IMS-ACTIVE **** AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST STEP01 PROCST CODES U0421 A/O DO COND CHANGE ACCUMULATION ODAT + DO ON PGMST STEP01 PROCST CODES U0428 A/O DO COND LOGCLOSE-NEEDED ODAT + DO ON PGMST STEP01 PROCST CODES U0426 A/O DO SHOUT TO U-DBA URGENCY V = *** IMSPROD ABENDED WITH U0426 **** DO ON PGMST PROCST CODES A/O DO USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 49
DO CTBRULE
DO CTBRULE
Invokes a CONTROL-B rule to be executed during the processing of a specific program step. Available only at sites utilizing CONTROL-B.
Format
Optional. Type CTBRULE in the DO field and press <ENTER>. The following subparameters are displayed: name Name of the CONTROL-B rule which should be executed. The CONTROL-B rule contains all balancing specifications to be performed. The rule name can be a maximum of eight characters. Mandatory. Arguments that are passed to the CONTROL-B rule. Separate multiple arguments by commas. A maximum of 45 characters can be specified. Optional.
ARG
General Information
When DO CTBRULE is specified, balancing is performed by the CONTROL-B Runtime environment according to the specified rule definition and using the specified arguments. The CONTROL-B Runtime environment is invoked once for each DO CTBRULE statement in the job scheduling definition. Note If DO CTBRULE is specified under ON PGMST ANYSTEP, the CONTROL-B Runtime environment is invoked only once.
When CONTROL-M calls a CONTROL-B rule, CONTROL-B System variable SYSOPT contains the value CTMWORK. This variable can then be tested within the CONTROL-B rule definition to determine if CONTROL-M invoked the CONTROL-B Runtime environment. When the CONTROL-B Runtime environment is invoked by CONTROL-M (i.e., CONTROL-B System variable SYSOPT is set to CTMWORK), CONTROL-B can analyze and balance SYSDATA. For more information about invoking CONTROL-B rules from CONTROL-M job scheduling definitions, see to Interface in CONTROL-M in Section 10 of the CONTROL-B User Manual.
3 50
DO CTBRULE
Example
If the job ends OK, execute CONTROL-B balancing rule GOVTBAL.
JOB: GOVTREPT LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT FINANCE-GOVTREPT-OK ODAT + AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES OK A/O DO CTBRULE = GOVTBAL ARG DOREPORT,10,%%ODATE DO ON PGMST PROCST CODES A/O DO SHOUT WHEN NOTOK TO TSO-M44 URGN R MS JOB GOVTREPT ENDED "NOT OK" SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
11.17.00
3 51
DO FORCEJOB
DO FORCEJOB
Force one or more jobs under CONTROL-M.
Format
Optional. Type FORCEJOB in the DO field and press <ENTER>. The following subparameters are displayed: TABLE JOB DATE Name of CONTROL-M scheduling table. Job name. If this field is blank, all jobs in the specified table are forced. 6-character scheduling date for the job(s). Valid values: date ODAT DATE LIBRARY Specific date (in either mmddyy, ddmmyy or yymmdd format, depending on the site standard). Resolves to the CONTROL-M original scheduling date of the job. Default. Resolves to the current system date.
Name of the scheduling library containing the specified table.
General Information
Statement DO FORCEJOB schedules jobs under CONTROL-M even if the jobs are not normally scheduled on the specified date (according to the jobs Basic Scheduling parameters). It is similar to the FORCE option in the CONTROL-M Rule List screen or Table List screen. If the DO FORCEJOB statement specifies a job name belonging to multiple jobs in the table, the first job in the table with that job name is forced. Without the DO FORCEJOB statement, emergency jobs and jobs which run in special circumstances would require daily scheduling or manual forcing (from the Online facility). By defining appropriate ON criteria and DO FORCEJOB statements, emergency or other special jobs can be automatically forced when required without being previously scheduled.
3 52
DO FORCEJOB
Example
On any system or user abend on any step in job PRDKPL01, force emergency job PRDKPLSP.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT PRDKPL01-ENDED-OK ODAT + AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) A FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES S*** U**** A/O DO FORCEJOB TABLE EMRJOBS JOB PRDKPLSP DATE ODAT LIBRARY CTM.PROD.SCHEDULE DO ON PGMST PROCST CODES A/O DO SHOUT WHEN NOTOK TO TSO-T43 URGN R MS PRDKPL01 ENDED NOT OK, PLEASE CHECK IT SHOUT WHEN LATE 0200 TO U-SHIFT-MANAGER URGN R MS PRDKPL01 WAS NOT SUBMITTED YET, PLEASE CHECK WHY SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< ===== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 53
DO IFRERUN
DO IFRERUN
Job steps to be executed during restart of a job. Available only at sites utilizing CONTROL-R.
Format
R
Optional. Type IFRERUN in the DO field and press <ENTER>. The following subparameters are displayed: FROM Step at which the job should be restarted. Mandatory. Valid values: pgmstep pgmstep.procstep $FIRST $ABEND Program step within the job stream (see note). Program step within the called procedure (see note). First step of the job. Step of the job which ended NOTOK due to system abend, user abend, condition code C2000 (PL/1 abend) or JFAIL (job failed on JCL error). $ABEND is a subset of $EXERR (below). First step of the abended procedure. This reserved keyword instructs CONTROL-M to run a CONTROL-R dataset cleanup for the job. Dataset cleanup is performed from the first step of the job. The job itself is not restarted Job step which ended with any error, including an abend, or which ended with a condition code which is redefined via the ON/DO statements as ENDED NOTOK.
$FIRST.$ABEND $FIRST.$CLEANUP
$EXERR
3 54
DO IFRERUN
TO
Step at which the restarted job should terminate. Optional. Valid values: pgmstep pgmstep.procstep Program step within the job stream (see note). Program step within the called procedure (see note).
If not specified, the restarted job terminates at the last job step that would normally be executed. Note For both FROM and TO steps, pgmstep is the name of the step (EXEC statement) which executes the program from which to begin or end the restart:
//pgmstep EXEC PGM=program
procstep is the name of the step (EXEC statement) which invokes the procedure from which the above pgmstep program is executed:
//procstep EXEC procedure
pgmstep and procstep values can each be 1 8 characters. When specifying a procstep when the procedures are nested, the innermost procstep in which the program is included should be specified. CONFIRM Specifies whether or not a manual confirmation is required before the job is restarted. Valid values: Y (Yes) N (No) Confirmation required. The job restart is not submitted unless a manual confirmation is entered in the Status screen. No confirmation required. The job restart can be automatically submitted (via the DO RERUN statement) without a manual confirmation. Default.
General Information
When statement DO IFRERUN is specified, the rerun is performed by the CONTROL-R Restart facility using the specified restart subparameters.
When DO IFRERUN is specified with a CONFIRM value of N (No): If a DO RERUN statement follows, the job is automatically submitted for rerun. If a DO RERUN statement does not follow, the job is not automatically rerun. Instead, the job remains displayed with its error status in the Status screen. In this case, to submit the job for rerun/restart, specify option R (Rerun) in the Status screen. The Rerun (with Restart) Confirmation Window is displayed. Request the restart/rerun from the window.
When DO IFRERUN is specified with a CONFIRM value of Y (Yes), the job appears in the Status screen with a WAIT CONFIRMATION (WITH RESTART) status and is not restarted unless confirmed. Specify option C (Confirm) to open the Confirm window to restart the job.
3 55
DO IFRERUN
For more information about job restart, refer to the description of the Status screen in Section 2 of this manual. When a job is submitted for restart, if $FIRST is specified in the FROM subparameter, a $FIRST step specification is passed as is to the CONTROLR step. If $ABEND or $EXERR is specified, the specified $ABEND or $EXERR value is first resolved to the appropriate step by the CONTROL-M monitor and then passed to the CONTROLR step. If $FIRST.$ABEND is specified, the CONTROL-M monitor determines which procedure abended and then passes the $FIRST step specification for that procedure to the CONTROLR step. For information regarding the CONTROLR step, refer to Section 2 of the CONTROL-R User Manual. CONTROL-M parameter MAXRERUN determines the maximum number of times the restart/rerun can be performed. (See RERUN-MAXRERUN in this section of the manual.)
Example
If the job abends on any step, restart (and automatically rerun) the job from the first abended step.
JOB: PRDKL02 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN 2 RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST UPDA CODES S**** U**** C2000 A/O DO IFRERUN FROM $ABEND TO CONFIRM N DO RERUN DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
15.26.42
3 56
DO NOTOK
DO NOTOK
Set the status of the job step to NOTOK if the accompanying ON step/code criteria are satisfied. If specified in a Group Entity, the termination status of the group is set to NOTOK.
Format
Optional. Type NOTOK in the DO field and press <ENTER>. DO NOTOK has no subparameters.
General Information
Statement DO NOTOK can change the status of a job step from OK to NOTOK. This results in the job having a final termination status of ENDED NOTOK. When specified in a Group Entity, statement DO NOTOK changes the termination status of the group (not the status of jobs or job steps). The following paragraphs describe the relationship of job step status and the final termination status of the job.
CONTROL-M determines the status of each individual step in a job before determining the final status of the job. After examining the results of a job step, CONTROL-M automatically assigns a status of OK or NOTOK to the step: By default (which can be changed by the IOA administrator) any job step ending with a condition code of C0000 through C0004 is assigned a status of OK. If any other condition code, system or user abend code, or user event is generated, the step is automatically assigned a status of NOTOK.
In general, if any of the steps in a job ends with a status of NOTOK, the job is assigned a final status of ENDED NOTOK. For a job to be assigned a final status of ENDED OK, each step in the job must be assigned a status of OK.
3 57
DO NOTOK
This logic suits most situations and should not be changed. However, there may be a situation in which CONTROL-M assigned a step a status of OK, but the status should be changed to NOTOK. Such a situation is described below:
The job ended with a condition code of C0004, but in this particular situation, it is better that the step have a status of NOTOK and the entire job be assigned a status of ENDED NOTOK.
DO NOTOK cannot be specified for the same ON step/code event as DO OK. When a DO NOTOK statement is performed for a step, the final status of the job is ENDED NOTOK, even if was previously set to ENDED OK.
Example
When PROCSTEP UPDA in PGMSTEP STEP06 finishes executing with a condition code of C0004, it is considered NOTOK.
JOB: PRDKPL02 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST STEP06 PROCST UPDA CODES C0004 A/O DO NOTOK DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
15.16.03
3 58
DO OK
DO OK
Set the status of the job step to OK if the accompanying ON step/code criteria are satisfied. If specified in a Group Entity, the termination status of the group is set to OK.
Format
Optional. Type OK in the DO field and press <ENTER>. DO OK has no subparameters.
General Information
Statement DO OK can change the status of a job step from NOTOK to OK. If all steps of a job have a status of OK the job is assigned a final termination status of ENDED OK. When specified in a Group Entity, statement DO OK changes the termination status of the group (not the status of jobs or job steps). The relationship between job step status and the final termination status of the job is as follows: CONTROL-M determines the status of each individual step in a job before determining the final status of the job. After examining the results of a job step, CONTROL-M automatically assigns a status of OK or NOTOK to the step:
By default (which can be changed by the IOA administrator) any job step ending with a condition code of C0000 through C0004 is assigned a status of OK. If any other condition code, system or user abend code, or user event is generated, the step is automatically assigned a status of NOTOK.
In general, if any of the steps in a job ends with a status of NOTOK, the job is assigned a final status of ENDED NOTOK. For a job to be assigned a final status of ENDED OK, each step in the job must be assigned a status of OK.
3 59
DO OK
This logic suits most situations and should not be changed. However, there may be a situation in which CONTROL-M assigned a step a status of NOTOK, but the status should be changed to OK. Several such exceptional situations are described below:
The NOTOK status is inappropriate for the job step. For example, a condition code greater than C0004 was returned for a step with which had an acceptable result. The NOTOK status is appropriate for the job step, but the job step is not critical, and should not affect the final job status. User events created via exit CTMX003 always result in a NOTOK status unless DO OK is specified.
DO OK cannot be specified for the same ON step/code event as DO NOTOK and DO RERUN. A DO OK statement cannot alter the status of a step for which any of the following codes apply: JLOST, *UKNW, *REC0, JNSUB, JNRUN. If specified for a step satisfied by any of these codes the DO OK statement is ignored. (See Valid Codes in the description of the ON statement later in this section.)
Example
When PROCSTEP UPDA in PGMSTEP STEP08 finishes executing with a condition code less than C0008, it is considered OK.
JOB: PRDKPL02 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST STEP08 PROCST UPDA CODES <C0008 A/O DO OK DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
15.16.03
3 60
DO RERUN
DO RERUN
Reschedules the job (for rerun) if the accompanying ON step/code criteria are satisfied.
Format
Optional. Type RERUN in the DO field and press <ENTER>. DO RERUN has no subparameters.
General Information
Statement RERUN is intended for situations in which a job should be rescheduled following an unsuccessful job run. It causes another order of the job to be placed in the Active Jobs file. Normally, rerun job orders are placed in the Active Jobs file with a status of WAIT SCHEDULE, where they wait to be submitted like any other job. However, other parameters (i.e., CONFIRM, DO IFRERUN) can affect the status of the rerun job order, and the jobs submission and processing:
A Y value specified in parameter CONFIRM indicates that manual confirmation is desired before submitting the rerun job order. In this case, the rerun job order is placed in the Active Jobs file with a status of WAIT CONFIRMATION (FOR SCHEDULE). (The job can be confirmed via option C (Confirm) in the Status screen.) A DO IFRERUN statement before the DO RERUN statement indicates that a restart is desired instead of a full rerun. The job order is placed in the Active Jobs file with a status of WAIT SCHEDULE WITH RESTART, where the job waits to be submitted from the indicated restart step. (Confirmation can also be required for restart jobs. This, too, is performed from the Status screen.) See parameter DO IFRERUN earlier in this section.
For information regarding confirmation, see Confirm Rerun Window and Rerun/Restart Window (Under CONTROL-R) in Section 2 of this manual.
3 61
DO RERUN
Job rerun is also affected by parameters MAXRERUN, RERUNMEM and INTERVAL.
MAXRERUN specifies the maximum number of times the job should be scheduled for rerun. RERUNMEM specifies the JCL member to be used for the rerun (if different from the jobs normal JCL member). INTERVAL specifies the number of minutes to wait between reruns.
These parameters are described in this section of this manual. DO RERUN cannot be specified for a cyclic job/started task. DO RERUN cannot be specified for the same ON step/code event as DO OK. DO RERUN should not be specified for steps which have a specified ON statement code value of OK. DO RERUN should not be specified for steps which have a specified ON statement code value of NOTOK because many of the causes of a NOTOK status preclude the possibility of a successful job rerun (e.g., JCL not found). Instead, specify an ON statement code value of EXERR to accompany the DO RERUN statement. When a DO RERUN statement is performed for a job (i.e., the accompanying ON step/codes criteria are satisfied), the previously run job is automatically assigned a final status of ENDED NOTOK, even if the job would have otherwise had a status of ENDED OK.
Example
If job EF145TS abends during step name COLLECT, try to run another job from member EF145TSR that will continue from the same place.
JOB: EF145TS LIB CTM.PROD.SCHEDULE TABLE: EFPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN 2 RERUNMEM EF145TSR INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST COLLECT PROCST CODES S*** U**** A/O DO RERUN DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
11.17.00
3 62
DO SET
DO SET
Assigns a value to an AutoEdit variable which can be used to set up the JCL of the next submission of a cyclic or rerun/restarted job. Note Statements SET VAR and DO SET are similar. If you are familiar with one of them, you can easily use the other. You should, however, be familiar with the differences outlined below in SET VAR / DO SET Differences.
Format
Optional. Type SET in the DO field and press <ENTER>. The following subparameter is displayed: VAR= User-defined variable and the value to be assigned. Mandatory. Replace the %%?=? prompt with the desired parameter, in the format: %%variable=expression where: %%variable expression Valid AutoEdit user-defined variable. Any of the following components, provided that it resolves to a single value:
Value (e.g., 5). AutoEdit system variable or previously user-defined variable (e.g., %%ODATE). defined
Note
To specify embedded blanks in a DO SET expression,

use AutoEdit variable %%BLANKn (e.g., %%A=TODAY%%BLANK1.IS%%BLANK1.SUNDAY).
3 63
DO SET
General Information
Statement DO SET can only be activated if the accompanying ON criteria are satisfied after the job ends. The statement is generally used to assign a value to an AutoEdit variable in the JCL of a cyclic or rerun/restarted job. The advantage of using AutoEdit variables in the JCL is that the JCL can be submitted with different values for different executions without actually changing the JCL. The JCL of the job can contain two types of AutoEdit variables:
System variables which are assigned values by the system. User-defined variables for which the user must supply values.
One method of supplying a value for a user-defined variable is by defining the variable and its value in a DO SET statement. An unlimited number of DO SET statements can be specified. At time of job submission, AutoEdit variables in the JCL are resolved in order in which they appear in the JCL. If an AutoEdit variable cannot be resolved, the job is not submitted. Note If the JCL contains an AutoEdit variable which is resolved in a subsequent run by a DO SET statement, the variable must be resolved by some other method (e.g., a SET VAR statement) in the original run, or the job will not be submitted.
Multiple AutoEdit variables (and constants) can be joined together into a complex user-defined variable. To resolve a complex user-defined variable, its component variables must first be resolved. Therefore, simple user-defined variables which comprise a complex user-defined variable must be either:
-or-
Specified in a previous SET VAR or DO SET statement.
Defined earlier in the JCL with a %%SET control statement.
The JCL Setup and AutoEdit facility is described in detail in Section 5 of this manual. SET VAR / DO SET Differences Statements SET VAR and DO SET are similar but have the following differences:
SET VAR is always applied before the job is submitted. DO SET is a Post-Processing parameter whose accompanying ON step/code criteria can only be satisfied during a job run. Therefore, DO SET is only be applied if its accompanying ON step/code criteria are satisfied. Even then, the result of a DO SET statement can only be applied the next time the job is submitted (i.e., for cyclic and rerun/restarted jobs). Statement SET VAR appears in each job scheduling definition. Statement DO SET does not appear unless specified. To specify a DO SET statement, type SET in an empty DO field and press <ENTER>. In statement SET VAR, the parameter value is specified after the keyword VAR. In statement DO SET, the parameter value is specified after the keyword VAR=.
3 64
DO SET
Example
If the job execution fails on any step due to a system or user abend, resolve the %%PARM parameter in the JCL to RESTART, restart from the first abended step, and automatically rerun.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT PRDKPL01-ENDED-OK ODAT + AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN 2 RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 A/O DO IFRERUN FROM $ABEND . TO . CONFIRM N DO RERUN DO SET VAR= %%PARM=RESTART DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
11.17.00
3 65
DO SHOUT
DO SHOUT
Sends (shouts) a message to a destination when a specific situation occurs. Note Statement DO SHOUT is similar to the SHOUT statement. If you are familiar with the SHOUT statement, you can easily use the DO SHOUT statement. You should, however, be familiar with the differences outlined below in SHOUT/DO SHOUT Differences.
Format
Optional. Type SHOUT in the DO field and press <ENTER>. The following subparameters are displayed: TO Destination of the message. (1-16 characters). Mandatory. Valid values: U-userid or USERID-userid Writes the message to the IOA Log file under the specified user ID. userid must be 1-8 characters. OPER[n] Sends a rollable message to the operator console. n is an optional 2-digit route code. If a route code is not specified, the default routes are Master Console and Programmer Information (1 and 11). Route codes are listed in Appendix D. Sends an unrollable, highlighted message to the operator console. n is an optional 2-digit route code. If a route code is not specified, the default routes are Master Console and Programmer Information (1 and 11). Route codes are listed in Appendix D.
OPER2[n]
[TSO-logonid | T-logonid][;Nn|;Mm|;NnMm|;Lname] Sends the message to the user identified by the logonid. logonid is mandatory (1-7 characters). An optional second value, indicating the computer and/or node (e.g., Mm) of the TSO logonid, can be specified, as follows:
3 66
DO SHOUT
Under JES2
Valid values are Nn, Mm or NnMm, where: m n Machine ID (the computer in JES2, not the 4-character SMF ID). 1-2 character JES/NJE node ID.
Under JES3
The only valid value is Lname, where: name Logical JES name of the machine (i.e., as used in JES3 command *T, not the MVS/SMF system ID). A shout to a TSO user performs a TSO SEND command which may require authorization at the receiving node.
Note
URGENCY
Urgency. Valid values: R U V Regular. Default. Urgent. Very urgent.
Message text. Maximum length: 70 characters. IOA AutoEdit system variables are supported and automatically resolved (replaced) at the time the SHOUT message is issued. See Section 5 of this manual for usage information.
General Information
The message is sent to the required destination when the accompanying ON statement criteria are satisfied. Subparameter TO When TO=USERID-userid, the message is written to the IOA Log file under the user ID specified in the parameter. When TO=OPER[n], the message is sent to the operator console (route code n). If the n value is omitted, the message is sent to all consoles. See Appendix D. When TO=OPER2[n], an unrollable, highlighted message is sent to the operator console (route code n). If the n value is omitted, the message is sent to all consoles. See Appendix D. When TO=TSO-logonid or T-logonid, the message is sent to the TSO logon ID. When a second value is used, the message is sent to the TSO logon Id in the specified computer/node (machine ID). When Enterprise Controlstation is installed, to shout the message to the Enterprise Controlstation specify reserved keyword U-ECS as the TO value.
3 67
DO SHOUT
To determine the machine ID under JES2, specify JES command $LSYS. Notes The TO field is also controlled by the IOA Dynamic Destination table. The TO field is first checked against the IOA Dynamic Destination table. If the table contains an entry that matches the TO value, the entrys content is used as the target for the shouted message. The entire TO field is used. Therefore, when directing the message to a remote user, do not append Nn or Mm. Instead, do this in the IOA Dynamic destination table itself. See Destination Table in Section 2 of the IOA Administrator Guide.
Subparameter URGENCY The URGENCY value indicates the urgency level of the message In addition, if the destination is USERID-userid (or U-userid), the user can control, according to urgency, which messages will be displayed when the IOA Log file is accessed. Urgent and very urgent messages are highlighted on the screen. For more details, see IOA Log Facility in Section 2. SHOUT / DO SHOUT Differences Statements SHOUT and DO SHOUT have the following differences:
Statement DO SHOUT is applied only if the accompanying ON criteria are satisfied. Therefore statement DO SHOUT does not contain subparameters for specifying when to perform the shout. By contrast, statement SHOUT requires that a value be specified (in subparameter WHEN) indicating when to shout the message. (Messages can be shouted when the job ends OK or NOTOK, when the job is late for submission or completion, or when the job runs too long.)
A SHOUT statement appears in each job scheduling definition. Statement DO SHOUT does not appear unless specified. To specify a DO SHOUT statement, type SHOUT in an empty DO field and press <ENTER>. The SHOUT URGN subparameter is equivalent to the DO SHOUT URGENCY subparameter. The SHOUT MS subparameter is equivalent to the DO SHOUT = subparameter.
3 68
DO SHOUT
Example
If the job is not run because of a JCL error, notify the user who sent the job.
JOB: SACALC01 LIB CTM.PROD.SCHEDULE TABLE: SALARY COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES JNRUN A/O DO SHOUT TO TSO-U0014 URGENCY U = *** JCL ERROR IN SALARY JOB *** DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
11.17.00
An urgent message is sent to the user ID that requested the job.
3 69
DO SYSOUT
Post-Processing Parameter
DO SYSOUT
Controls handling of job output if the accompanying ON step/code criteria are satisfied. Note Statements SYSOUT and DO SYSOUT are similar. If you are familiar with one of them, you can easily use the other. You should, however, be familiar with the differences outlined below in SYSOUT/DO SYSOUT Differences.
Format
Optional. Type the word SYSOUT in the DO field and press <ENTER>. The following subparameters are displayed: OPT Sysout option code. Mandatory. Valid values: F D R C N PRM Copy the job output to file. Delete (purge) the job output. Release the job output. Change the class of the job output. Change the destination of the job output.
Relevant sysout data. Mandatory and valid only if the specified OPT value is F, C or N. Valid values depend on the OPT value, as follows: F C N File name. New class (1 character). An asterisk (*) indicates the jobs original MSGCLASS. New destination (1-8 characters).
FRM
FROM class. Optional. Limits the sysout handling operation to only sysouts from the specified class. Note If a FROM class is not specified, all sysout classes are treated as a single, whole unit.
3 70
DO SYSOUT
General Information
The CONTROL-M monitor, unless otherwise instructed, leaves the job sysout in HELD class in the output queue. Parameter DO SYSOUT is used to request additional handling of these held sysouts when the accompanying ON criteria are satisfied. The CONTROL-M monitor sends all sysout handling requests to JES which processes the instructions. If, however, the copying of sysouts to a file is requested (option F), CONTROL-M requests the sysouts from JES and then CONTROL-M directly writes the sysouts to the file. Since only one SYSOUT statement can be defined in a job scheduling definition, DO SYSOUT statements can be used, as follows, to specify additional sysout handling instructions when the job ends OK:
To define DO SYSOUT statements that operate like a SYSOUT statement (i.e., that operate only when the job ends OK), define their accompanying ON statement with pgmstep value ANYSTEP and code value OK.
The interrelationship between multiple sysout operations (via statements SYSOUT and DO SYSOUT) is described below in Multiple Sysout Operations. Sysout Handling Operations Which sysouts are affected by sysout handling operations depends on whether the sysouts are under JES2 or JES3, as follows: Under JES2: Operations are performed on all of the jobs held sysouts (or held portions of sysouts) unless otherwise restricted to a specific FROM class via subparameter FRM. Operations are performed only on the jobs sysouts in the CONTROL-M held class (specified in CONTROL-M installation parameter HLDCLAS) unless further restricted to a specific FROM class via subparameter FRM.
Under JES3:
Sysout handling operations are listed below:
Copying sysouts to a file (OPT=F) The jobs sysouts are copied (not moved) to the file specified in the data subparameter. The file name specified in the data subparameter can contain AutoEdit System variables. (No other AutoEdit terms can be specified.) If the AutoEdit variables cannot be resolved, the sysout is not copied. CONTROL-M allocates the file with DISP=(NEW,CATLG,DELETE) using the unit and space attributes specified in the CONTROL-M installation parameters. Sysouts can be archived by copying them. However, to reduce overhead, this method is recommended only for small sysouts.
Deleting sysouts (OPT=D) The jobs sysouts are deleted (purged) from the output queue. Note This operation works on all sysouts under JES2 or JES3 (regardless of held status/ class) unless otherwise restricted by the FRM subparameter.
3 71
DO SYSOUT
Releasing sysouts (OPT=R) The jobs sysouts are released for printing. Changing the class of sysouts (OPT=C) The jobs sysouts are changed to the output class specified in the data subparameter. Ensure that you specify a meaningful target output class. The following points should be noted: Changing a sysout class to a released class changes the class name. It does not, however, release the sysout because the sysout attributes do not change (due to JES logic). To ensure that the sysout will be released, use DO SYSOUT statements to release the sysout after changing its class. For example:
DO SYSOUT OPT C PRM R FRM A DO SYSOUT OPT R PRM FRM A
Changing a sysout class to a dummy class does not purge the sysout because the sysout attributes do not change (due to JES logic). To save a jobs original MSGCLASS and to restore it at output processing time, specify a data value of *. The sysouts are changed to the jobs original class.
Moving sysouts to a new destination (OPT=N) The jobs sysouts are moved to the output destination specified in the data subparameter. Ensure that you specify a meaningful target output destination.
Multiple Sysout Operations If multiple DO SYSOUT (or SYSOUT/DO SYSOUT) operations are not specified for the same FROM class, the order in which the operations are performed is not significant. However, if different DO SYSOUT (or SYSOUT/DO SYSOUT) operations affect the same FROM class, or if multiple operations are specified without a FROM class, the order and method of implementation is significant. CONTROL-M merges different operations for the same FROM class into a combined instruction to JES. Likewise, CONTROL-M merges different operations without a FROM class into a combined instruction to JES. Operations without a specified FROM class treat the entire held sysout as a whole unit, and are therefore not merged with sysout handling requests for a specific FROM class. JES does not necessarily process multiple sysout-handling instructions in the order they are issued by CONTROL-M. Therefore, the processing results can vary if the merged instructions to JES include both FRM=a specified close and FRM=blank. It is therefore highly recommended that a job scheduling definition not contain both FROM class and no FROM class sysout handling instructions which will become operational under the same situation(s). When CONTROL-M merges a set of operations into a combined instruction, some operations override or cancel other operations, and some operations are performed along with other operations. This is described below.
3 72
DO SYSOUT
Operation Merging and Performance CONTROL-M performs all copy to file operations (option F) first. After performing all copy to file operations, CONTROL-M merges all operations performed on a specific FROM class. After merging operations on specific FROM classes, CONTROL-M merges the operations performed on the sysout as a whole (i.e., subparameter FRM=blank). CONTROL-M then passes the merged sets of instructions to JES for processing. The resulting combination of operations can vary depending on whether the operation that was merged with a DO SYSOUT operation is a SYSOUT operation or another DO SYSOUT operation. Generally, DO SYSOUT operations override, or are performed along with, SYSOUT statements. The following chart and the accompanying numbered explanations indicate the result of merging multiple DO SYSOUT statements. Note For information about merging a SYSOUT and a DO SYSOUT statement, see Operation Merging and Performance in the description of parameter SYSOUT.
The order of precedence in which CONTROL-M processes/merges operations is as follows: 1) DO SYSOUT=F Copy to file operations are performed first (directly by CONTROL-M) for DO SYSOUT statements (whether or not FROM class is specified). Then, other operations are performed. 2) DO SYSOUT = D (Delete)
3 73
DO SYSOUT
This operation supersedes all other DO SYSOUT operations (except copy to file operations described above). Superseded operations are ignored (i.e., not performed). 3) DO SYSOUT combinations of R, C and N In general, combinations of R, C, and N requests are merged (i.e., are all performed). The exceptional cases indicated in the chart are described below: If multiple C requests come from DO SYSOUT statements, perform only one of the requests. (This combination should not normally be specified.) If multiple N requests come from DO SYSOUT statements, perform the request which occurs first.
SYSOUT / DO SYSOUT Differences SYSOUT and DO SYSOUT statements have the following differences:
The SYSOUT statement is applied only if the job ends OK. DO SYSOUT statements are associated with accompanying ON statements and are applied only if the accompanying ON step/code criteria are satisfied. A SYSOUT statement appears in each job scheduling definition. A DO SYSOUT statement is not displayed unless requested. To request a DO SYSOUT statement, type SYSOUT in an empty DO field and press <ENTER>. Only one SYSOUT statement can be defined in the job scheduling definition. An unlimited number of DO SYSOUT statements can be requested. The SYSOUT OP subparameter is equivalent to the DO SYSOUT OPT subparameter. The SYSOUT data subparameter is equivalent to the DO SYSOUT PRM subparameter. The SYSOUT FROM subparameter is equivalent to the DO subparameter. SYSOUT FRM
3 74
DO SYSOUT
Example 1
If a job finishes executing OK, delete (purge) the sysout (DO SYSOUT OP D). If the job finishes executing with condition code 0050-0059 in step STEP02, set the jobs end status to OK and release the sysout for printing. If the job abends, move the sysout to class D.
JOB: SACALC01 LIB CTM.PROD.SCHEDULE TABLE: SALARY COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES OK A/O DO SYSOUT OPT D PRM FRM ON PGMST STEP02 PROCST CODES C005* A/O DO OK DO SYSOUT OPT R PRM FRM DO ON PGMST ANYSTEP PROCST CODES U**** S**** A/O DO SYSOUT OPT C PRM D FRM DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< ===== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 75
DO SYSOUT
Example 2
Use of the Sysout Archiving Facility The MSGCLASS of the job is X (a held class). Reports are produced in class D. The desired actions are:
Archive the JCL messages and all the held output in class X (the SYSPRINT datasets, job log, etc.). If the job finishes executing OK, release the reports for print and delete the MSGCLASS sysouts. If the job finishes executing NOTOK, delete the reports and keep the MSGCLASS (JCL, job log, etc.) output in hold status.
JOB: GPLUPDT1 LIB CTM.PROD.SCHEDULE TABLE: PRODGPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES ***** A/O DO SYSOUT OPT F PRM GPL.%%JOBNAME.D%%ODATE.N%%JOBID.T%%TIME FRM X DO ON PGMST ANYSTEP PROCST CODES OK A/O DO SYSOUT OPT D PRM FRM X DO SYSOUT OPT R PRM FRM D DO ON PGMST ANYSTEP PROCST CODES NOTOK A/O DO SYSOUT OPT D PRM FRM D DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
Notice the use of the AutoEdit symbols in the name of the file to be archived. The symbol %%JOBNAME is replaced with the job name, %%ODATE by the original scheduling date, etc., producing a file name such as PRD.PADD0040.D980303.N01342.T170843. The file can be viewed by using ISPF Browse. A list of the jobs outputs can be produced using ISPF option 3.4. For example, retrieval by the prefix PRD.PAPD0040.D9803 will list all the names of the sysouts of the job in the month of March 1998. It is possible to browse, edit, print, etc. the desired sysout. Note The File operation (sysout archival) is intended for small sysouts (e.g., JCL, sort messages) and not for large volume reports. When the CONTROL-M monitor is performing file operations, it does not analyze the results of other jobs. Therefore, if large files are archived, production throughput may suffer.
3 76
DOC
DOC
Detailed job documentation. This field can be displayed or hidden by request.
Format
Optional. Upon filling in a DOC line with text and pressing <ENTER>, a new DOC line is opened for specifying additional documentation text.
General Information
DOC lines are used for specifying job documentation. Upon entry to the job scheduling definition, DOC lines are displayed only if a Y value had been specified in field SHOW JOB DOCUMENTATION in the Scheduling Definition Facility entry panel. Command DOC can be used in the job scheduling definition to toggle between the display/nondisplay of job documentation. The information specified in the DOC lines is saved in the member and library specified in parameters DOCMEM and DOCLIB. This member can also be edited directly via ISPF edit. When modifying DOC lines in the job scheduling definition, text must be left in at least one DOC line in order to save the modifications. Changes resulting in an empty DOCMEM member are not saved when exiting the job scheduling definition. For more information regarding job documentation, including the saving of job documentation changes, see Job Documentation in Section 2 of this manual.
3 77
DOC
Example
The steps performed by the L-file backup job are documented in the DOC lines.
JOB: BACKPL02 LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME BACKPL02 MEMLIB CTM.PROD.JOBLIB OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y APPL APPL-L GROUP BKP-PROD-L DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L OVERLIB CTM.OVER.JOBLIB SET VAR CTB STEP AT NAME TYPE DOCMEM BACKPL02 DOCLIB CTM.PROD.DOC =========================================================================== DOC THIS JOB BACKS UP SPECIAL "L" FILES. IT PERFORMS THE FOLLOWING STEPS: DOC 1: VERIFY SPACE REQUIREMENTS DOC 2-5: BACKUP THE FILES DOC 6: RECATALOG THE NEW FILES DOC 7: PRINT THE SHORT-VERSION LISTING REPORT DOC =========================================================================== DAYS ALL DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 78
DOCLIB
DOCLIB
Name of the library in which the member specified in DOCMEM resides.
Format
Optional. Parameter DOCLIB identifies a valid dataset name of 1-44 characters. The default is either defined at time of installation or is blank.
General Information
The library can be any standard partitioned dataset. The record length must be 80. Any number of documentation libraries can be used at a site. However, only one documentation library can be specified in each job scheduling definition. Note Users with DOCU/TEXT installed at their sites can specify a DOCU/TEXT library and member with up to 132 characters per line. However, if more than the first 71 characters in a line are used, the line is truncated and Browse mode is forced. Browse mode is also forced if a line contains an unprintable character. Changes to the documentation are not permitted in Browse mode.
3 79
DOCLIB
Example
Job documentation is written to member PRDKPL01 in library CTM.PROD.DOC.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME PRDKPL01 MEMLIB CTM.PROD.JCL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 Y APPL KPL GROUP PROD-KPL DESC DAILY PRODUCTION - START OF APPL-PROD-KPL OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM PRDKPL01 DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN START-DAILY-PROD-KPL ODAT CONTROL DB2-MAIN-FILE E RESOURCE INIT 0001 CARTRIDGE 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 80
DOCMEM
DOCMEM
Name of the member which contains job documentation.
Format
Optional. DOCMEM identifies a valid member name of 1-8 characters. The default is either defined during installation or is blank.
General Information
DOCMEM identifies a member which is in the library identified by parameter DOCLIB. This member is used to save detailed documentation written in the DOC lines of the Job Scheduling Definition screen (or Status Zoom screen). When you enter the Job Scheduling Definition screen for the first time, DOCMEM defaults to the value of MEMNAME. You can change this value, but it is recommended that you not do so. Note Users with DOCU/TEXT installed at their sites can specify a DOCU/TEXT library and member with up to 132 characters per line. However, if more than the first 71 characters in a line are used, the line is truncated and Browse mode is forced. Browse mode is also forced if a line contains an unprintable character. Changes to the documentation are not permitted in Browse mode.
3 81
DOCMEM
Example
Job documentation is written to member PRDKPL01 in library CTM.PROD.DOC.
3 82
DUE OUT
DUE OUT
Time by which the job should finish executing.
Format
Optional. The format for the parameter is: hhmm Time the job is due out (based on a 24-hour clock) where: hh mm Hour the job is due out. Minute the job is due out.
General Information
Parameter DUE OUT is used to specify a time by which the job should finish executing. When two jobs with the same priority are available for submission, CONTROL-M submits the job with the earlier DUE OUT time first. When a DUE OUT time is specified, the CONTROL-M monitor uses this DUE OUT time, and the anticipated elapse time (i.e., the anticipated execution time), to calculate a DUE IN time for the job. The DUE IN time is the time by which the job must be submitted in order to finish executing by the DUE OUT time. (The anticipated elapse time is the average of the execution times of the job recorded in the CONTROL-M Statistics file.) If DUE OUT time is not specified, the default DUE OUT time is the last minute of the working day. Automatic adjustment of DUE OUT times can be requested from the Job Dependency Network screen. For more information, see Automatic Job Flow Adjustment in Section 1 and Job Dependency Network Screen in Section 2 of this manual.
3 83
DUE OUT
Example
Job DISKLOG2 should finish execution by 6:00 a.m.
JOB: DISKLOG2 LIB CTM.PROD.SCHEDULE TABLE: ADABAS COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME DISKLOG2 MEMLIB * OWNER DBA TASKTYPE CST PREVENT-NCT2 APPL DBA GROUP DBA-LOG DESC CLEAN DISK LOG 2 OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM DISKLOG2 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR O WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 99 D-CAT MINIMUM PDS =========================================================================== IN DBA-CLEAN-LOG-2 **** CONTROL RESOURCE TAPE 0001 PIPE TIME: FROM UNTIL PRIORITY DUE OUT 0600 CONFIRM USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 17.14.10
3 84
GROUP
GROUP
Group to which a job belongs.
Format
Parameter GROUP identifies a group name of 1-20 characters. Only trailing blanks are allowed.
In a Group Entity, the parameter is mandatory. In jobs in a Group scheduling table, the field is protected and contains the GROUP name specified in the Group Entity.
By default (which can be modified in the User profile), the parameter is optional for jobs in regular scheduling tables. The same value does not have to be specified for all jobs in the table.
General Information
The way in which parameter GROUP is applied depends on the type of scheduling table in which the job scheduling definitions appear:
In a Group scheduling table, the parameter affects job scheduling as well as the retrieval and display of information. In a regular scheduling table, the parameter affects the retrieval and display of information. It does not affect job scheduling.
Group Job Scheduling When a Group scheduling table is created, a value for parameter GROUP must be specified in the Group Entity. This value is automatically applied to the GROUP field in all job scheduling definitions in the table. Jobs in a Group scheduling table cannot be individually ordered. Jobs in this type of table can only be ordered as a group. (They can, however, be individually forced.) A group must be eligible for scheduling (i.e., a set of basic scheduling criteria in the Group Entity must be satisfied) before jobs in the Group scheduling table can be scheduled.
3 85
GROUP
Basic scheduling criteria, runtime scheduling criteria, and post-processing parameters in the Group Entity apply to all scheduled jobs in the group. For more information, see Handling of Job Groups in Sections 1 and 2, and see Scheduling Jobs in Group Scheduling Tables under Basic Scheduling Parameters Summary earlier in this section.
Retrieving and Displaying Information

Regardless of scheduling table type, parameter GROUP can be used as a selection criterion which can make retrieval and display of information more efficient. For example, display of information in the Status screen can be limited to jobs belonging to a specific group. The group name appears in all important messages relating to the groups jobs. Note Use of parameter GROUP is highly recommended in all job scheduling definitions to 3 facilitate implementation of Enterprise Controlstation functions.
Example
Job OPERCOMP (in a regular scheduling table) belongs to the MAINTENANCE group.
JOB: OPERCOMP LIB CTM.PROD.SCHEDULE TABLE: OPER COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME OPERCOMP MEMLIB CTM.PROD.JCL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP MAINTENANCE DESC JOB RUN ON THE 1ST OF THE MONTH OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM OPERCOMP DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE INIT 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
See the Enterprise Controlstation User Guide for details.
3 86
IN
IN
Prerequisite conditions which must be satisfied before the job can run.
Format
Optional. A maximum of two prerequisite conditions can be specified in each IN line. When you specify the second prerequisite condition in a line and press <ENTER>, a new line is opened for specifying additional prerequisite conditions. Each specified prerequisite condition consists of the following mandatory subparameters: cond-name User-supplied, descriptive name of 1-20 characters used to identify the condition. Mandatory. Note A condition name should not begin with the | symbol, and should not contain parentheses ( ), because these characters can be affixed to a prerequisite condition to apply Boolean logic. (See AND/OR Relations below.)
dateref
4-character date reference. Mandatory. Valid values: date ODAT PREV Specific date (in either mmdd or ddmm format, depending on the site standard). Resolves to the original scheduling date. Default. Resolves to the previous date on which the job should have been scheduled, according to its basic scheduling criteria (or ODATE1 for a forced job). Note for Group Scheduled Jobs If an asterisk (*) has been specified in the SCHEDULE TAG field, PREV is resolved to the nearest previous date which satisfies one or more Schedule Tags in the Group entity.
3 87
IN
STAT
Static. Indicates that the condition (e.g., IMS-ACTIVE) is not date-dependent. Note STAT replaces the 0101 date values specified for such conditions prior to IOA Release 5.0.0. Although 0101 can still be specified, STAT is preferred because it cannot be confused with an actual date.
**** $$$$
Any scheduling date. Any scheduling date.
If a date reference is not specified, value ODAT is automatically inserted when you press <ENTER>.
General Information
A job cannot be submitted unless all the prerequisite condition criteria specified in the IN statement(s) have been satisfied. Prerequisite conditions are usually used to establish job dependencies or to ensure manual intervention when required:
To establish job dependency, define a prerequisite condition in an OUT or DO COND statement in the job that should run first, and in an IN statement in the job that should run afterwards. The job containing a prerequisite condition in its IN statement is not submitted unless that prerequisite condition has been added manually or by the job containing the OUT or DO COND statement. An OUT statement adds the prerequisite condition if the job ends OK. The DO COND statement adds the prerequisite condition if the step/codes event criteria specified in the accompanying ON statement are satisfied.
If the IN prerequisite condition can only be satisfied by manual intervention (e.g., TAPE1-ARRIVED is set by the operator after an external tape arrives on-site), performance of the required manual intervention before job submission can be ensured.
OUT and DO COND statements can also be used to delete prerequisite conditions which are no longer needed. If an IN prerequisite condition for a job is not an IN prerequisite condition for any other job, you can use the jobs OUT statement to delete the prerequisite condition after the job ends OK. For more information, see the descriptions of the OUT, ON and DO COND statements in this section and Prerequisite Condition Concept in Section 1 of this manual. The following are examples of prerequisite conditions:
All prerequisite conditions are created with a date reference. When specifying a prerequisite condition as an IN condition, you must specify the date for the condition. Only a prerequisite condition with the specified date can satisfy the IN requirement.
3 88
IN
For more information regarding prerequisite conditions, see Prerequisite Condition Concept in Section 1 of this manual. AND/OR Relations When specifying multiple IN conditions, an AND relationship is normally assumed. An OR relationship can be indicated by specifying the | (OR) symbol (HEX 4F) at the beginning of a condition. Parentheses can also be specified to further clarify the AND/OR relationship between prerequisite conditions. Examples Prerequisite conditions A and B must exist in order for the job to be submitted: IN A B
Prerequisite conditions A and E must exist in order for the job to be submitted. Additionally, at least one of the conditions B, C, or D must also exist: IN A (|B |C |D) E
Either prerequisite conditions A, B and C, or conditions D, E, and F must exist for the job to be submitted: IN | (A B C) | (D E F)
3 89
IN
Example 1
Schedule the job that produces the salary statistics report for top management when the set of jobs that calculates the salaries finishes OK. (When the set of jobs that calculates the salaries finishes OK, it creates the prerequisite condition SALARY-OK.) The report will be produced twice a month, for the 1st and for the 15th. The 15ths report is produced only if the 15ths prerequisite condition SALARY-OK exists (signifying that the 15ths salary job ended OK). The existence of the 1sts prerequisite condition SALARY-OK does not cause submission of the 15ths report.
JOB: EBDRPT1A LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDRPT1A MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP EBD-PRODUCTION DESC EBD PRODUCTION SALARY REPORTS OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDRPT1A DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01,15 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12-Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 06 D-CAT MINIMUM PDS =========================================================================== IN SALARY-OK ODAT CONTROL RESOURCE USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 90
IN
Example 2
This example is similar to Example 1. A monthly total report must be produced based on data from the last two runs, and the job must run when IMS is active.
JOB: EBDRPT1A LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDRPT1A MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP EBD-PRODUCTION DESC EBD PRODUCTION REPORTS OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDRPT1A DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01,15 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12-Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 06 D-CAT MINIMUM PDS =========================================================================== IN SALARY-OK ODAT SALARY-OK PREV IMS-ACTIVE STAT CONTROL RESOURCE USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
Prerequisite condition IMS-ACTIVE is based on a static condition that exists only when IMS is active. IMS itself can be monitored by CONTROL-M. When IMS is not active, CONTROL-M deletes the prerequisite condition IMS-ACTIVE, thus preventing abends of jobs that depend on IMS.
3 91
IN
Example 3
Assume that there is a group of jobs that runs every day of the week except Saturday and Sunday. It is very important that some of the jobs scheduled for the different days of the week will not run simultaneously. The order of these jobs must be maintained even if there are delays.
JOB: EBDUPDT2 LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDUPDT2 MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP EBD-PRODUCTION DESC EBD PRODUCTION UPDATE OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDUPDT2 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS 2,3,4,5,6 WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12-Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 08 D-CAT MINIMUM PDS =========================================================================== IN DEPOSITS PREV CONTROL RESOURCE USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
The job is submitted only if the prerequisite condition DEPOSITS of the previous schedule date exists. The prerequisite condition DEPOSITS is created only after the group of jobs called DEPOSITS finishes.
3 92
IN
Example 4
This report should run after the database has been updated by either of two jobs, EBDUPDT2 or EBDUPDT3, but only if IMS is active.
JOB: EBDRPT6C LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDRPT6C MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP EBD-PRODUCTION DESC EBD PRODUCTION DATABASE REPORTS OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDRPT6C DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01,15 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12-Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 04 D-CAT MINIMUM PDS =========================================================================== IN |EBD-EBDUPDT2-ENDED ODAT |EBD-EBDUPDT3-ENDED ODAT IMS-ACTIVE STAT CONTROL USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
This job is submitted only if IMS is active and if job EBDUPDT2 (or EBDUPDT3) finished executing.
3 93
IN
Example 5
Use of parentheses in the IN conditions is demonstrated in the following example. Job EDBCLEAN requires that two conditions be satisfied before submission. The first must be either condition CICSP1-IS-UP or condition CICSP2-IS-UP. The second must be either condition OPR-CLEAN-REQUEST or condition SYS-CLEAN-REQUEST.
JOB: EBDCLEAN LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDCLEAN MEMLIB CTM.PROD.JOBLIB OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y APPL EBD GROUP EBD-MAINT DESC OVERLIB CTM.OVER.JOBLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDCLEAN DOCLIB =========================================================================== DAYS ALL DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12-Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN (CICSP1-IS-UP 0101 ??CICSP2-IS-UP) 0101 (OPR-CLEAN-REQUEST ODAT ??SYS-CLEAN-REQUEST) ODAT USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
Example 6
The following example provides a further explanation of the concept of the schedule date reference:
MEMNAME MEMLIB DAYS MONTHS IN EBDRPT6D EBD.PROD.JOB 01,15,20 1- N 2- N 3- N 4- N 5- N 6- N 7- Y 8- N 9- Y 10- N 11- N 12- N EBD-REPORTS-READY ****
Today is the 15th of September. The date reference values resolved in this job are written in mmdd date format: ODAT PREV **** 0915 0901 Any date reference.
3 94
INTERVAL
INTERVAL
Minimum number of minutes to wait between reruns or cyclic runs of a job. See also TASKTYPE (Cyclic).
Format
Optional. Valid values are any three-digit number in the range of 000 255. The default represents 000, which means there is no minimum time interval between runs.
General Information
Parameter INTERVAL ensures a minimum interval between runs of the same job (reruns or cyclic runs). Once the job has run, the CONTROL-M monitor will not rerun or resubmit the job until the specified number of minutes has passed. The job will also not be resubmitted unless all runtime submission criteria (resources, conditions, etc.) are satisfied.
3 95
INTERVAL
Example
A backup for an ADABAS database failed because the database was being used by another user. It will be tried again after 15 minutes.
JOB: ADBBKPS LIB CTM.PROD.SCHEDULE TABLE: ADABAS COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN 9 RERUNMEM INTERVAL 015 STEP RANGE FR (PGM.PROC) . TO . ON PGMST BACKUP PROCST CODES U0034 A/O DO RERUN DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
11.17.00
3 96
MAXWAIT
MAXWAIT
Number of extra days the job can wait in the Active Jobs file for submission.
Format
Optional. Valid values are any two-digit number in the range of 00-98, or 99. A leading zero is required. 00 nn Job is not executed if it did not execute on the original scheduling date. Default. Where nn = 01-98. If the job did not execute on its original scheduling date, it is given an additional number of days to execute. It can remain in the Active Jobs file up to nn days awaiting execution. Job remains in the Active Jobs file (until deleted manually), even if the job finished executing.
99
If no value is specified, the value 00 is automatically inserted.
General Information
Parameter MAXWAIT is used to overcome the problem of delays in production. A job that is scheduled for execution on a specific day does not always get executed that same day. This may be due to a number of reasons, such as hardware failure, a heavy production workload, or a bug in one of the jobs predecessors. Therefore, it may be desirable to specify an additional number of days that the job should remain in the Active Jobs file awaiting execution. When a job cannot be submitted for execution within the specified time limits, an appropriate message is written to the IOA Log file, and the job is deleted from the Active Jobs file. Jobs scheduled as a result of a Y value in the RETRO parameter are always given at least one day within which to execute, even if the MAXWAIT parameter indicates that they should no longer be in the Active Jobs file. (This occurs when the current working date exceeds the original scheduling date by more than the number of days specified in parameter MAXWAIT on the day the job is scheduled via RETRO=Y.) For more information see parameter RETRO later in this section.
3 97
MAXWAIT
Emergency jobs are also disregarded if their specified MAXWAIT periods have passed. An emergency job that belongs to a specific group (specified in parameter GROUP) and whose MAXWAIT period has not passed is not deleted from the Active Jobs file until all of the regular jobs that belong to the same group have finished executing. This is in case the job will be needed at a later stage. MAXWAIT Values for Jobs in a Group Scheduling Table The MAXWAIT value for jobs in a Group scheduling table is normally determined by the MAXWAIT parameter in the Group entity. If optional wish WM2890 has been applied at your site, the MAXWAIT value is instead determined by the value of the MAXWAIT parameter in the job scheduling definition for each job in the group. Note If a job in a group is forced, the MAXWAIT value is determined by the value of the MAXWAIT parameter in the job scheduling definition (regardless of whether or not wish WM2890 has been applied).
Example 1
If the jobs original scheduling date has passed, give the job an extra three days to be submitted.
JOB: OPERJOB LIB CTM.PROD.SCHEDULE TABLE: OPER COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME OPERJOB MEMLIB CTM.PROD.JCL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP MAINTENANCE DESC JOB RUN IN FIRST HALF OF THE MONTH OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM OPERJOB DOCLIB CTM.PROD.DOC =========================================================================== DAYS 02,04,06 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 03 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE INIT 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
Assume that the job will not run due to the absence of the required runtime resources. The job that is scheduled for the 2nd of the month can wait from the 2nd through the 5th to be executed.
3 98
MAXWAIT
On the 6th, the MAXWAIT period expires and the job scheduled for the 2nd will not be executed. The jobs scheduled for the 4th and 6th will wait for execution until the 7th and 9th.
Example 2
The job can wait for execution indefinitely, until the runtime requirements for the job are satisfied:
MAXWAIT 99
Example 3
Schedule the job for every working day, whether or not the computer is active. Give the job an extra day in which to be submitted. Assume that calendar WORKDAYS, specified in parameter DCAL, contains the values 15, 16, 18, and 19. The computer was offline from the 16th up to and including the 18th, and the 15th was the last date that the job was scheduled for execution.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME PRDKPL01 MEMLIB CTM.PROD.JCL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL KPL GROUP PROD-KPL DESC DAILY PRODUCTION - START OF APPL-PROD-KPL OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM PRDKPL01 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL WORKDAYS AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 01 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
Today is the 19th. The job is scheduled three times with the different original scheduling dates of the 16th, 18th and 19th. The 16ths and 18ths jobs will be disregarded on the 20th if they have not yet executed. The 19ths job will be disregarded only on the 21st.
Example 4
Schedule the job for every working day, whether or not the computer is active. If it does not execute within the scheduled day, remove it from the Active Job file:
MAXWAIT 00
3 99
MEMLIB
MEMLIB
For a job (or warning messages): Name of the library containing the member specified in parameter MEMNAME. For a started task: Required started task information. See also OVERLIB.
Format
Mandatory. Format of the parameter depends on whether the job scheduling definition applies to a job (or warning messages) or a started task:
For a job (or warning messages): Valid values are a valid dataset name of 1-44 characters or one of the following reserved values: DUMMY USER=name GENERAL For dummy jobs. For user-defined libraries. Specifies the library referenced by DD statement DALIB in the CONTROLM procedure.
For a started task: Any of the following formats can be used for the MEMLIB value: *.taskid cpuid,stcparms Where taskid is the task ID. The STC will be activated in the computer in which the CONTROL-M monitor is active. Where cpuid is the ID of the computer in which the STC should be activated (see value cpuid below); stcparms represents STC parameters. Where cpuid is the ID of the computer in which the STC should be activated. Valid cpuid values: * The same computer where the CONTROL-M monitor is active.
cpuid
3 100
MEMLIB
Under JES2: Nn Mm Where n is the JES/NJE node ID. Where m is the machine ID. (This is the ID of the computer in JES, not the 4-character SMF ID. You can use the $LSYS JES command to determine the JES ID.) Where n is the JES/NJE node ID, and m is the machine ID.
NnMm
Under JES3 Lname Where name is the logical JES name of the machine (i.e., as used in the JES3 command *T, not the SMF system ID).
General Information
Whether the job scheduling definition applies to a job, warning messages, or a started task is determined by the values defined in parameter TASKTYPE (described later in this section). AutoEdit variables can be specified and will be resolved. Even the machine ID, which is relevant for started task initiation, can be automatically replaced based on resource allocation (see Section 5). For Jobs (or Warning Messages) The library can be any standard partitioned dataset (PDS or PDSE), LIBRARIAN or PANVALET. The record length must be 80. The library and the member do not have to exist when the job production parameters are defined. Their existence is checked by CONTROL-M before actual submission of the job. If, during the access to a library by CONTROL-M (before submission), the library is held exclusively by another user (e.g., TSO user, job, etc.), the monitor will try to access the library every few seconds until the library is released and the job can be submitted. Use of the library name DUMMY is intended for scheduling events (e.g., adding a prerequisite condition without actually running the job). If the library name DUMMY is used, the job is not submitted (submission and sysout checking is skipped). In this case, the job is assumed to have ended OK (ON PGMST...DO processing is not performed), and all Post-Processing parameters associated with an ENDED OK status are activated (OUT, SHOUT WHEN OK). If the library name is GENERAL, the job is submitted from the library referenced by DD statement DALIB of the CONTROLM procedure. This library must be a partitioned dataset or a concatenation of partitioned datasets. The prefix USER= should be specified when a special type of user library is used. When using this prefix, the member is not read by CONTROL-M using the normal mechanism. Instead CONTROL-M submission exit (CTMX002) should be coded to handle access and submission of the library and member. See the IOA SECUDATA library for examples of the exit. A started task is activated in the specified computer ID (by the JES ID, not the MVS/SMF ID). If the computer ID is followed by a comma and parameters, the parameters are applied to the started task.
3 101
MEMLIB
Example 1
Submit the job from member IMSBKUP in library SYS2.IMS.JOB:
MEMNAME IMSBKUP MEMLIB SYS2.IMS.JOB
Example 2
Activate started task COLCTSMF in the computer where the CONTROL-M monitor is operating:
MEMNAME COLCTSMF MEMLIB *,DATE=%%ODATE
On September 9, the STC will be activated by issuing the operator command:

S COLCTSMF,DATE=980909
Example 3
Activate started task GTF in the computer in which the CONTROL-M monitor is operating; task ID is G01:
MEMNAME GTF MEMLIB *.G01
The STC is activated by issuing the operator command:

S GTF.G01
Example 4
Activate started task COLCTSMF on JES node 1:
MEMNAME COLCTSMF MEMLIB N1,DATE=%%ODATE
Example 5
Activate started task COLCTSMF on machine 1 on JES node 1:
MEMNAME COLCTSMF MEMLIB N1M1,DATE=%%ODATE
3 102
MEMLIB
Example 6
The JCL for the job OPERCOMP is stored in library CTM.MOD.JCL.
3 103
MEMNAME
MEMNAME
Name of the member that contains one of the following (depending on the defined task type):
JCL of the job Started task procedure Warning message(s) For a Group Entity, this parameter has a different meaning. See For a Group Entity below.
Note
See also MEMLIB.
Format
Mandatory. MEMNAME identifies a valid member name of 1-8 characters. For On Spool jobs, mask characters * and ? are supported. For details, see the description of mask characters in Section 2 and See On Spool Jobs in Section 4 of this manual. Note CONTROL-M does not support members which have been compressed using the ISPF PACK option.
General Information Parameter MEMNAME identifies a member whose contents are determined by the task type of the job scheduling definition (See parameter TASKTYPE later in this section):
If TASKTYPE contains the value JOB, CYC, EMR or ECJ, the job scheduling definition is defined for a job and parameter MEMNAME identifies the member which contains the JCL of the job. If TASKTYPE contains the value STC, CST, EST or ECS, the job scheduling definition is defined for a started task and parameter MEMNAME identifies the member which contains the started task procedure. If TASKTYPE contains the value WRN, the job scheduling definition is defined for warning messages and parameter MEMNAME identifies the member which contains the warning messages.
3 104
MEMNAME
For a Job The member name can be the same as or different than the job name. The member can contain the JCL of more than one job. In this case, CONTROL-M submits all the jobs in the member, but only monitors the execution and results of the members first job. Therefore, it is highly recommended that each member contain the JCL of only one job. For a Group Entity In a Group Entity, parameter MEMNAME does not indicate a member name. Instead, MEMNAME is used for descriptive purposes in certain screens (e.g., in the NAME field of the Status screen).
Example
The JCL for job CTM.PROD.JCL. OPERCOMP is located in member OPERCOMP in library
3 105
MINIMUM
MINIMUM
Minimum number of free tracks required by the library specified in parameter PDS. See also PDS.
Format
Optional; however, if PDS is specified, MINIMUM is mandatory. Parameter MINIMUM specifies the minimum number of free tracks required. This must be a positive 3-digit number (leading zeros will be inserted if necessary). Parameter MINIMUM cannot be used with parameters DAYS, WDAYS, MONTHS, CONFCAL, RETRO and DATES.
General Information
Parameters MINIMUM and PDS are always used together and are never used with other Basic Scheduling parameters. Parameter PDS identifies a library, and parameter MINIMUM specifies the minimum number of free tracks required by that library. These parameters are intended for use (i.e., definition) in jobs/started tasks which compress, clean and/or enlarge libraries, or which issue a warning message to the IOA Log file (i.e., if TASKTYPE=WRN) if the minimum number of free tracks is not available. If parameters MINIMUM and PDS are defined for a job, the scheduling of the job is not related to or dependent upon any date criteria. Instead, the job is scheduled if the actual number of free tracks available in the specified library is below the specified minimum at time of daily job ordering. The job/started task can then compress, clean, or enlarge the library (or issue the appropriate warning). Note MINIMUM does not work with PDSE-type libraries because they always appear to be 100 percent full. MINIMUM only checks current extents.
3 106
MINIMUM
Example 1
Schedule the job when there are less than 20 unused tracks in the library ALL.PARMLIB.
JOB: OPERCOMP LIB CTM.PROD.SCHEDULE TABLE: OPER COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME OPERCOMP MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP OPER-MAINT DESC COMPRESS OF ALL.PARMLIB OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM OPERCOMP DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 123456789101112DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM 020 PDS ALL.PARMLIB =========================================================================== IN CONTROL RESOURCE INIT 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
Example 2
Send a warning message when there are less than 50 unused tracks in library USER.LIBRARY:
MEMNAME TASKTYPE PDS MINIMUM MSG001 WRN USER.LIBRARY 050
3 107
MONTHS
MONTHS
Months of the year in which the job should be scheduled.
Format
Optional. The months in the year are represented by a number 1 through 12. A value can be specified for each month. Valid values: Y (Yes) N (No) or blank Schedule the job in that month. Default. Do not schedule the job in that month.
General Information
The job is scheduled for execution only during the months in which a value of Y is specified. Parameter MONTHS cannot be used with parameters PDS, MINIMUM and DATES. When parameter MONTHS is used, at least one of the following must be specified: DAYS, DCAL, WDAYS or WCAL. When specified with one of these parameters, parameter MONTHS works as a filter to limit the job schedule. Parameter MONTHS is ignored when periodic values are specified in parameter DAYS or WDAYS.
Example 1
Schedule a job only in March and September:
MONTHS 1- N 2- N 3- Y 4- N 5- N 6- N 7- N 8- N 9- Y 10- N 11- N 12- N
3 108
MONTHS
Example 2
Schedule job OPERCOMP on the first day of every month.
3 109
ON
ON
Job processing step/code event criteria which determine whether or not the accompanying DO statements are performed. See also STEP RANGE.
Format
Optional. ON statements define event criteria consisting of possible codes resulting from execution of job steps under CONTROL-M. The ON statement consists of the subparameters described below. When used, at least one step and one code must be specified. Subparameters: PGMST 1-8 characters. Mandatory. Valid values are: pgmstep Name of the step (EXEC statement) which executes the program to be checked for the specified codes:
//pgmstep EXEC PGM=program
ANYSTEP ON criteria are satisfied if the code criteria are satisfied in any of the job steps. If ANYSTEP is specified with codes OK, NOTOK, EXERR or *UKNW, the ON criteria are satisfied only if the entire job ends with the particular status code. *range * indicates that a step range, not a step name, is specified. range is the name of a step range defined in parameter STEP RANGE. For more information refer to parameter STEP RANGE in this section of the manual.
PROCST
1-8 characters. Optional. Valid values: procstep Name of the step (EXEC statement) which invokes the procedure from which the above PGMST program is executed:
//procstep EXEC procedure
If the value of PGMST is ANYSTEP, any step in the procedure will trigger the DO actions if the codes criteria are satisfied.
3 110
ON
CODES
Return code(s) and/or status(es) returned upon termination of the specified job step(s) which will satisfy the step/code event criteria. At least one code must be specifed. Codes can be condition codes, user abend codes, system abend codes, various end codes and statuses, and certain keywords. Codes are discussed below in General Information. Optional. Specifying either A (And) or O (Or) opens a new ON statement in the ON block (described later) and links the new statement to the statement containing the A/O specification, as follows: A (And) Indicates AND logic between the two ON statements. ON block criteria are satisfied only if both ON statements are satisfied. Indicates OR logic between the two ON statements. ON block criteria are satisfied if either (or both) ON statements are satisfied.
A/O
O (Or)
General Information
ON statements are usually, but not necessarily, followed by user-specified DO actions. The implied relationship between ON statements and associated DO statements is: IF THEN ON statement step/code event criteria are satisfied. Perform the associated DO statements.
The combination of ON statements and DO statements enables you to specify post-processing actions whose performance depends on the execution results of job steps executed under CONTROL-M. Multiple ON Statements / ON Blocks In a new job scheduling definition, an empty ON statement is followed by an empty DO statement. Additional ON statements can be opened in the job scheduling definition as follows:
When you fill in an ON step and code value and press <ENTER>, new, empty ON and DO statements are opened following the current ON/DO statements. The new ON/DO statements, if filled in, are not logically connected to the preceding ON/DO statements. They constitute a new ON block/DO block. Multiple ON blocks are normally interpreted sequentially. When you fill in the A/O (And/Or) subparameter of an ON statement, an empty ON statement is opened immediately (i.e., before the accompanying DO statement). The specified And/Or value logically connects the new ON statement to the preceding ON statement. These two ON statements constitute a single ON block. Example
ON PGMST STEP1 ... CODES C0004 ... A/O A ON PGMST STEP5 ... CODES S0C4 ... A/O DO SHOUT ...
In the above ON/DO statements, for the DO SHOUT action to be performed, STEP1 must end with a condition code of C0004 and STEP5 must end with system abend S0C4.
3 111
ON
To add an empty ON statement between two existing ON statements, type the > character over the first letter in the ON PGMST value of the previous ON line, and press <ENTER>. Example If the program step name is STEP1:
ON PGMST >TEP1
adds an empty ON line after the current ON statement. Step name STEP1 is restored to its original value when <ENTER> is pressed (i.e., the > character disappears). To delete unwanted ON statements, specify appropriate Line Editing commands in the Edit environment (described in Appendix A). Within an ON block, the relationship between ON statements is determined by the connecting A/O subparameters. However, there is no connection between ON blocks. Each ON block is examined separately in the order defined. If the conditions of an ON block are satisfied, the accompanying DO actions are performed. The conditions of more than one ON block can be satisfied; therefore, more than one set of DO statements can be performed. Example One ON block specifies STEP1 as the program step and >C0004 as the code. A second ON block specifies ANYSTEP as the program step and >C0008 as the code. If STEP1 results in a condition code of C0016, the ON step/code event criteria for both ON statements are satisfied, and the DO actions accompanying both ON blocks are performed. ON Statement Steps Within an ON statement, the specified step is generally a program step, specified in field PGMST. It can be a program executed directly within the job stream (in which case no PROCST value is specified) or it can be a program executed by a called procedure (in which case the called procedure is specified in PROCST). If the JCL contains nested procedures, the name of the EXEC procedure statement which invokes the most deeply nested procedure (i.e., the procedure which immediately invokes the PGM step) should be specified in PROCST. The same step name can appear in different ON statements in the same ON block (or different ON blocks). Value ANYSTEP can be specified in field PGMST. In general, it indicates that the DO statements should be performed if the specified codes are found in any step(s). However, for codes, OK, NOTOK, EXERR or *UKNW, the value ANYSTEP indicates that the criteria will be satisfied only if the entire job terminates with the indicated code. If you want to check if the codes occur in a range of steps instead of a specific step, the range of steps can be specified and assigned a user-defined name in the STEP RANGE statement (described later in this section). The user-defined name can then be specified in the PGMST field, preceded by an * to indicate that it is a step range (not a step name).
3 112
ON
Example STEP RANGE assigns the user-defined name DF2 to indicate pgmstep range STEP20 through STEP29A. If *DF2 is specified in ON PGMST, the ON step/code criteria will be satisfied if any of the codes result from any of the steps in the range STEP20 through STEP29A. ON Statement Codes Codes can be condition codes, user abend codes, system abend codes, various end codes and statuses, and certain keywords. They can also be prefaced by certain qualifiers. All of these are described below. A maximum of 245 codes can be specified for any ON step statement, as follows:
Each line of an ON statement contains fields for specification of up to four codes. Whenever a fourth code on a line is specified, and <ENTER> is pressed, a new line within the same ON statement is opened, allowing specification of up to another four codes.
Valid codes: Cnnnn Sxxx Unnnn *xxxx Step condition code, where nnnn is a 4-digit value. Step system abend code, where xxx is a 3-character hex value. Step user abend code, where nnnn is a 4-digit value. Any step completion code (condition, system abend, user abend) that matches the string, where x can be any alphanumeric character in user-defined events (which are turned on by EXIT 3 see your IOA administrator for usage). Any step completion (including JCL error and non-execution of the job or step). Jobs sysout was lost. Job was canceled during execution or re-execution. Job failed due to JCL error. Job failed due to security requirements (only under ACF2). Job not submitted. Submission of a job or initiation of a started task failed for any reason. A PGM step finished executing OK (by default with a condition code of C0004 or less). This value can be specified only with step value ANYSTEP. A PGM step (or the job) finished executing NOTOK. This code covers all types of failures, including non-execution errors (e.g., job not run, JCL error, job not submitted), and (by default) any condition code greater than C0004. This value can only be specified with step value ANYSTEP.
***** JLOST JNRUN JFAIL JSECU JNSUB OK
NOTOK
3 113
ON
EXERR
Any type of execution error. It is the same as NOTOK, but is triggered only if the job has actually started executing. This value can only be specified with step value ANYSTEP. A NOT CATLGD 2 or NOT RECATLGD 2 event occurred in the job step. The default result of this event is a NOTOK status for the step. A message containing the dataset name will be written to the IOA Log file. Note See your IOA administrator if you do not wish to be alerted to NOT RECATLGD 2 events.
*NCT2
*TERM *REC0
Job terminated by CMEM due to an NCT2 event. Rerun (recovery) is needed, but no more reruns are available. Note This status code is REC followed by a zero (not the letter O).
*UKNW
An unknown error occurred, usually as a result of a computer crash during job execution. This value can only be specified with step value ANYSTEP. Job was queued for re-execution. If a DO OK statement is specified in the job scheduling definition, it is ignored for steps for which any of the following codes apply: JLOST, *UNKW, *REC0, JNSUB, JNRUN.
*$EJ Note
Code Qualifiers and Relationships Any character in a condition code, system abend code or user abend code can be replaced by an asterisk (*). An asterisk means any value for the character it replaces. For example, if S*13 is specified, the code criteria for the step will be satisfied by codes S013, S613, S913, etc. The following qualifiers can be used in certain cases: > < N Greater than. Valid as a qualifier for condition codes and user abend codes. Less than. Valid as a qualifier for condition codes and user abend codes. Specifies not to perform the accompanying DO statements if the specified code exists in the step. Valid as a qualifier for condition codes, user abend codes and system abend codes. The N qualifier indicates that the DO statements should not be performed if the specified condition exists. It does not indicate that the DO statements should be performed if the specified condition does not exist.
Note
The relationship between multiple codes in an ON statement is OR (i.e., the appearance of any of the codes in the specified step will satisfy the ON criteria), except for range specifications (e.g., >10 <40).
3 114
ON
However, code criteria qualified by N take precedence over all other code criteria. If a code which is specified with an N qualifier is generated by the specified step, accompanying DO actions are not performed even if other ON code criteria are satisfied.
Examples
If >C0008 NC0020 are specified, the codes criteria will be satisfied (and the DO statements performed) by the appearance of any condition code greater than 8 except condition code 20. If the following are specified:
>U0999 NU1341 S*** NS*37<C0004
The DO actions will be triggered by one of the following: A condition code less than C0004 A user abend code greater than U0999 except U1341 Any system abend code except Sx37 (i.e., except S037, S137, etc.)
If only code NC0008 is specified: The accompanying DO statements will never be performed. The specified value only indicates when not to perform the DO actions. There is no indication when the DO actions should be performed.
Example 1
Any program step resulting in condition code C0008 or C0016 is considered OK.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST UPDA CODES C0008 C0016 A/O DO OK DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
15.16.03
3 115
ON
Example 2
When procedure step UPDA in program step STEP08 finishes executing with a condition code less than C0008, it is considered OK.
JOB: PRDKPL02 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST STEP08 PROCST UPDA CODES <C0008 A/O DO OK DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
15.16.03
3 116
ON
Example 3
When any program step in the step range DF2 (STEP20 STEP29A) finishes executing with any system or user abend code, except U2030, rerun the job, and shout the indicated message to TSO logon ID P43.
JOB: PRDKPL03 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE DF2 FR (PGM.PROC) STEP20 . TO STEP29A . STEP RANGE FR (PGM.PROC) . TO . ON PGMST *DF2 PROCST CODES S*** U**** NU2030 A/O DO RERUN DO SHOUT TO TSO-P43 URGENCY R = JOB PRDKPL03 ABENDED; THE JOB IS RERUN DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
15.16.03
3 117
ON GROUP-END
ON GROUP-END
Table-processing termination status, for a group, which determines whether or not the accompanying DO statements are performed. Found in Group Entities only.
Format
Optional. Multiple ON GROUP-END parameters can be defined. Upon specifying an ON GROUP-END value and pressing <ENTER>, a new ON GROUP-END statement, followed by a blank DO statement, is opened. Valid values: OK NOTOK Process the accompanying DO statements if all scheduled jobs in the group ended OK. Process the accompanying DO statements if at least one scheduled job in the group ended NOT OK.
General Information
Parameter ON GROUP-END enables specification of DO statements to be performed when the processing of the group ends with the indicated status. When a job in the group ends NOTOK, the DO statements accompanying an ON GROUP-END NOTOK parameter are performed. If the job that ended NOTOK is subsequently successfully rerun, so that the termination status of the group changes to OK, the DO statements accompanying an ON GROUP-END OK parameter are then performed. The following DO statements can be specified following an ON GROUP-END statement: DO COND DO FORCEJOB DO NOTOK DO OK DO SET DO SHOUT
Statements DO OK or DO NOTOK change the final status of the group (not the status of each job or job step in the table).
3 118
ON GROUP-END
Use of parameter ON GROUP-END in the Group Entity can frequently reduce the number of individual DO statements which would otherwise require definition in individual job scheduling definitions. For example, suppose that following the processing of the table, you want to force a particular job if any of the jobs in the table ENDED NOTOK.
This result can be achieved by defining an ON GROUP-END NOTOK statement (in the Group Entity) followed by the appropriate DO FORCEJOB statement. To achieve this result without use of the ON GROUP-END parameter, the following steps would be necessary: In each job scheduling definition in the table, define an appropriate condition which would be added to the IOA Conditions/Resources file when the job ends NOTOK. In the table, define an additional job to be performed after the other jobs in the table have terminated. This job would have as an IN condition the condition added by the job(s) which ended NOTOK, and would force the appropriate job.
Example
If a job in the Group scheduling table ACCOUNTS ended NOTOK, add condition ACCTS-CHK-REQUIRED.
GRP ACCOUNTS_GROUP CTM.PROD.SCHEDULE(GRP) COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 =========================================================================== SCHEDULE TAG DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 =========================================================================== IN TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT ON GROUP-END NOTOK DO COND ACCTS-CHK-REQUIRED ODAT + SHOUT WHEN TO URGN USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 18.19.14
3 119
OUT
OUT
Add or delete prerequisite conditions when the job ends OK. Note
Statements OUT and DO COND are similar. If you are familiar with one of them, you can easily use the other. You should, however, be familiar with the differences outlined below in OUT / DO COND Differences.
Format
Optional. A maximum of two prerequisite conditions can be specified in each OUT line. Upon specifying the second prerequisite condition in a line and pressing <ENTER>, a new line is opened for specifying additional prerequisite conditions. Each specified prerequisite condition consists of the following mandatory subparameters: cond-name User-supplied, descriptive name of 1-20 characters which identifies the condition.
Note
A condition name should not begin with the | symbol and should not contain parentheses (), because these characters can be affixed to a prerequisite condition name to apply Boolean logic when checking for the existence of the condition. (See the description of parameter IN for details.) 4-character date reference. Valid values: date ODAT PREV Specific date (in either mmdd or ddmm format, depending on the site standard). Resolves to the original scheduling date. Default. Resolves to the previous date on which the job should have been scheduled, according to its basic scheduling criteria (or ODATE1 for a forced job). Resolves to the next date on which the job will be scheduled according to its basic scheduling criteria (or ODATE+1 for a forced job).
dateref
NEXT
3 120
OUT
STAT
Static. Indicates that the condition (e.g., IMS-ACTIVE) is not date-dependent. Note STAT replaces the 0101 date value specified for such conditions prior to IOA Release 5.0.0. Although 0101 can still be specified, STAT is preferred because it cannot be confused with an actual date.
**** $$$$
Any scheduling date. Valid only with opt= . Any scheduling date. Valid only with opt= .
If a date reference is not specified, value ODAT is automatically inserted When you press <ENTER>. opt Indicates whether to add or delete the specified prerequisite condition. Valid values: + Add (create) the prerequisite condition. Delete the prerequisite condition.
General Information
If the job ends OK, the prerequisite conditions are added to or deleted from the IOA Conditions/Resources file according to the specified opt value. Prerequisite conditions are usually used to establish job dependencies or to ensure manual intervention when required:
To establish job dependency, define a prerequisite condition in an OUT or DO COND statement in the job that should run first, and in an IN statement in the job that should run afterwards. The job containing a prerequisite condition in an IN statement is not submitted unless that prerequisite condition has been added manually or by a job containing the OUT or DO COND statement. An OUT statement is used to add the prerequisite condition if the job ends OK. The DO COND statement is used to add the prerequisite condition if the step/codes event criteria specified in the accompanying ON statement are satisfied.
If the IN condition can only be satisfied by manual intervention (e.g., TAPE1-ARRIVED is set by the operator after an external tape has arrived on-site), performance of the required manual intervention before job submission can be ensured.
OUT and DO COND statements can also be used to delete prerequisite conditions. The jobs OUT statement can be used to delete a prerequisite condition after the job ends OK. A DO COND statement can be used to delete prerequisite conditions if the accompanying ON step/code criteria are satisfied. These statements are generally used to delete prerequisite conditions either to prevent a particular job from running or when the condition is no longer needed by any other jobs in the Active Jobs file. DO COND functions are performed after the functions of the OUT parameter:
3 121
OUT
If a prerequisite condition is added by the OUT parameter and deleted by the DO COND parameter, the combined effect is the deletion of the prerequisite condition. If a prerequisite condition is deleted by the OUT parameter and added by the DO COND parameter, the combined effect is the addition of that prerequisite condition.
(For more information, see the descriptions of parameters IN, ON and DO COND earlier in this section.) The following are examples of prerequisite conditions:
All prerequisite conditions are associated with a date reference which is used to distinguish between different runs of the same job with different scheduling dates. If, for example, a condition is being deleted, only the condition matching the specified date will be deleted. The same condition from a different date will not be deleted. Prerequisite conditions created by parameter OUT can trigger the execution of other jobs or processes. Prerequisite conditions deleted by parameter OUT can prevent the scheduling of jobs and processes that require those prerequisite conditions in their IN parameter. For more information regarding prerequisite conditions, see Prerequisite Condition Concept in Section 1 of this manual. OUT Conditions for Group Entities Prerequisite conditions which are specified for Group entities in OUT statements and/or in ON GROUP-END DO COND statements enable you to establish dependencies between Group scheduling tables, and between Group scheduling tables and other jobs. When all jobs in a Group scheduling table are ended or deleted, prerequisite conditions are added to or deleted from the IOA Conditions/Resources file according to the OUT statements and/or ON GROUP-END DO COND statements in the Group entity. Note A Group entity can be reassigned a status of ACTIVE after specified prerequisite conditions have already been added/deleted. For example, if a job in the Group scheduling table was deleted while in WAIT SCHEDULE status and was then undeleted after the prerequisite conditions were added/deleted, the Group entity returns to ACTIVE status.
3 122
OUT
MVS Job Restart For sites in which CONTROL-R is not installed, CONTROL-M provides a mechanism for automatic implementation of MVS restarts in certain situations. The mechanism, however, requires definition before the original submission of the job. Therefore, it is only useful for jobs in which automatic restart is always desirable (when necessary). Note MVS restart is not recommended and must be used with caution. MVS restart does not perform automatic File catalog adjustment, GDG (Generation Dataset Group) adjustment, condition code recapture, abend code recapture, or dataset scratching. Unless these functions are manually handled without error, the results of an MVS restart can be unpredictable or damaging.
The mechanism for automatic implementation of MVS restart is the definition of a special OUT condition in the job scheduling definition. The value of the condition is:
@#ODAT -
Where: @# ODAT condition date option Do not define this type of restart (i.e., this OUT condition) if a CONTROL-R restart will be used for the job, or the results can be unpredictable.
Note
This restart will be implemented in the following situations if the CONTROL-M monitor ended the job NOT OK (i.e., a DO OK did not impact the final status):
The job abended. The job failed due to JCL error. One of the steps ended with a condition code of C2000 (abend of a PL/1 program).
When the special OUT condition is defined in the job scheduling definition and the job ends as described above, the CONTROL-M monitor automatically appends the name of the failing step to the OUT condition of the job order. The OUT condition in the job order (i.e., as seen in the Zoom screen) therefore appears as follows:
@#-procstep.pgmstep
Before a job is submitted, the CONTROL-M monitor checks the job order for an OUT condition beginning @# . When the monitor detects condition @#-procstep.pgmstep, it automatically inserts an MVS step in the JCL of the job, so that the job begins from the indicated procstep.pgmstep. For the job to be restarted from procstep.pgmstep, the job must be rerun. This can be the result of a rerun (manual or automatic) or the result of a cyclic job run. The @# procstep.pgmstep value appearing in the Zoom screen can be deleted (in which case restart is not performed), or changed to a different procstep.pgmstep, so that restart begins from a different step.
3 123
OUT
Even if a special OUT condition (name or prefix @# ) is not defined in the job scheduling definition, an MVS restart can be implemented by specifying OUT condition @# procstep.pgmstep (for the desired restart step) in the Zoom screen. Note It is also possible to specify OUT condition @# procstep.pgmstep in the job scheduling definition, but this is not recommended. If @# procstep.pgmstep is specified in the job scheduling definition, the job will always begin at the specified step (never at the first step) even on the initial run.
When using MVS job restart, every step in the job must have a unique procstep.pgmstep name. CONTROL-M does not check for duplicate stepnames. OUT / DO COND Differences OUT and DO COND statements are similar but have the following differences:
Statement OUT is applied only if the job ends OK. DO COND statements are associated with ON statements and are applied only if the associated ON step/code criteria are satisfied. An OUT statement appears in each job scheduling definition. No DO COND statement appears unless specified. To specify a DO COND statement, type COND in an empty DO field and press <ENTER>. DO COND statements are processed after OUT statements and can therefore override OUT statements. MVS restart can only be requested in an OUT statement, not a DO COND statement.
3 124
OUT
Example 1
This example consists of two jobs (screens):
SACALC01 SARPT001
Calculates salaries Generates the Salary Statistics report
The report should be generated after the salaries have been successfully calculated. Job SACALC01 runs first.
JOB: SACALC01 LIB CTM.PROD.SCHEDULE TABLE: SALARY COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME SACALC01 MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL SAL GROUP SALARY DESC SALARY CALCULATIONS OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM SACALC01 DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01,15 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT SALARY-OK ODAT + USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
When job SACALC01 ends OK, the prerequisite condition SALARY-OK is added. This will trigger the execution of job SARPT001 that requires the condition in order to run.
3 125
OUT
Job SARPT001 is not run unless job SACALC01 ended OK.

JOB: SARPT001 LIB CTM.PROD.SCHEDULE TABLE: SALARY COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME SARPT001 MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL SAL GROUP SALARY DESC SALARY STATISTICS REPORT OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM SARPT001 DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01,15 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN SALARY-OK ODAT CONTROL RESOURCE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
The report (job SARPT001) is produced twice a month for the 1st and for the 15th. The 15ths report is produced only if the 15ths prerequisite condition SALARY-OK exists. The existence of the 1sts prerequisite condition SALARY-OK does not cause submission of the 15ths report (job SARPT001). The 1sts jobs SACALC01 and SARPT001 (report), do not have to run on the 1st of the month. Suppose the salary job (SACALC01) finishes executing (OK) on the 3rd, the prerequisite condition SALARY-OK for the 1st is added, because the prerequisite condition is schedule date dependent.
3 126
OUT
Example 2
Some jobs (e.g., IMSBDUPD) must run only when the IMS is active (IMS-ACTIVE):
MEMNAME DAYS IN IMSDBUPD 1,15 IMS-ACTIVE STAT
The prerequisite condition IMS-ACTIVE is generic, and it only exists when IMS is active. IMS itself is monitored by CONTROL-M. When IMS is brought down successfully, CONTROL-M deletes the prerequisite condition IMS-ACTIVE for all schedule dates. This prevents the abending of jobs that depend on IMS (such as job IMSDBUPD in the above example). Job IMSDBUPD will not be submitted if the prerequisite condition IMS-ACTIVE does not exist.
JOB: IMSPROD LIB CTM.PROD.SCHEDULE TABLE: IMSPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME IMSPROD MEMLIB GENERAL OWNER SYS1 TASKTYPE CST PREVENT-NCT2 APPL IMS GROUP IMS-PROD DESC IMS PRODUCTION OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM IMSPROD DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 99 D-CAT MINIMUM PDS =========================================================================== IN DEPOSITS PREV CONTROL RESOURCE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT IMS-ACTIVE **** USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 127
OUT
Example 3
A group of jobs runs every day of the week except Saturday and Sunday. Several of the different jobs for the different days must not run in parallel, and job sequence must be maintained even in case of delay.
JOB: EBDUPDT2 LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDUPDT2 MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP EBD-PRODUCTION DESC EBD PRODUCTION UPDATE OF DEPOSITS OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDUPDT2 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS 2,3,4,5,6 WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 08 D-CAT MINIMUM PDS =========================================================================== IN DEPOSITS PREV CONTROL RESOURCE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT DEPOSITS ODAT + USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
The job will be submitted only if the previous schedule dates prerequisite condition DEPOSITS exists. If the job finishes OK, the prerequisite condition DEPOSITS of the same schedule date is added, which will in turn trigger the next days job.
3 128
OUT
Example 4
The following is an example of a job set for Automatic Restart (using CONTROL-M only) in case of abend. Note This type of restart should not be used when CONTROL-R restart is used for the job, or results may be unpredictable.
JOB: EBDUPDT2 LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDUPDT2 MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP EBD-PRODUCTION DESC EBD PRODUCTION UPDATE OF DEPOSITS OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDUPDT2 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS 2,3,4,5,6 WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 08 D-CAT MINIMUM PDS =========================================================================== IN DEPOSITS PREV CONTROL RESOURCE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT DEPOSITS ODAT + @#ODAT USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 129
OUT
Example 5
The following example serves as a further explanation of the schedule date reference concept:
MEMNAME MEMLIB DAYS MONTHS OUT EBDUPDT2 EBD.PROD.JOB 1,15,20 1- N 2- N 3- N 4- N 5- N 6- N 7- Y 8- N 9- Y 10- N 11- Y 12- N EBD-INPUT-READY **** -
Today is the 15th of September. The date reference values resolved in this job are in mmdd date format: ODAT PREV NEXT **** 0915 0901 0920 Any date reference
3 130
OVERLIB
OVERLIB
Name of a JCL library which should override the library specification in parameter MEMLIB. See also MEMLIB.
Format
Optional. Valid values:
A valid dataset name of 1-44 characters. AutoEdit variables can be specified. The reserved value DUMMY (for dummy jobs).
General Information
Parameter OVERLIB enables submission of a modified copy of the jobs actual JCL, without changes to either the regular JCL (in the MEMLIB library) or the job scheduling definition. The library containing the jobs regular JCL member is specified in parameter MEMLIB. When temporary changes are desired, the JCL member can be copied to the library specified in the OVERLIB field and modified as needed. Note When copying the regular JCL member to the OVERLIB library, do not change the member name. CONTROL-M always looks for a JCL member whose name matches the MEMNAME value.
If member MEMNAME is found in the OVERLIB JCL library, that member is used. Otherwise, the member is taken from the MEMLIB library. When the job is scheduled, the OVERLIB field is scanned. If it is not empty, CONTROL-M resolves AutoEdit variables in the field (if any are specified), and then searches the OVERLIB library for the member specified in field MEMNAME. The override can be canceled by deleting member MEMNAME from the OVERLIB library. If member MEMNAME is not found in the OVERLIB library, the member is taken from the MEMLIB library. (Alternatively, the override can be canceled by deleting the OVERLIB specification from the job scheduling definition.) Note OVERLIB cannot be specified for a started task.
3 131
OVERLIB
The library may be any standard partitioned dataset, LIBRARIAN or PANVALET. The record length must be 80. GENERAL or USER= (which are valid MEMLIB values) cannot be specified in field OVERLIB. The library and the member do not have to exist when parameter OVERLIB is defined. Their existence is checked by CONTROL-M before actual submission of the job. If, during the access to a library by CONTROL-M (before submission), the library is held exclusively by another user (e.g., TSO user, job), the monitor re-tries to access the library every few seconds until the library is released and the job can be submitted. Use of the library name DUMMY is intended for scheduling events (e.g., adding a prerequisite condition without actually running the job). If the library name DUMMY is used, the job is not submitted (submission and sysout checking is skipped). The job is assumed to have ended OK (ON PGMST...DO processing is not performed). All Post-processing parameters associated with an ENDED OK status are activated (OUT, SHOUT WHEN OK, etc.).
Example
If a special, modified version of BACKPL02 JCL is required, it will be defined in CTM.OVER.JOBLIB. This JCL will then be used instead of the JCL in CTM.PROD.JOBLIB.
JOB: BACKPL02 LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME BACKPL02 MEMLIB CTM.PROD.JOBLIB OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y APPL APPL-L GROUP BKP-PROD-L DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L OVERLIB CTM.OVER.JOBLIB SET VAR CTB STEP AT NAME TYPE DOCMEM BACKPL02 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL WORKDAYS SHIFT RETRO N MAXWAIT 04 D-CAT MINIMUM PDS =========================================================================== IN START-DAILY-BACKUP ODAT CONTROL RESOURCE INIT 0001 CART 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 132
OWNER
OWNER
User who requests CONTROL-M services.
Format
Mandatory. OWNER must be 1-8 characters.
General Information
Parameter OWNER is used by CONTROL-Ms internal security mechanism to determine which operations each user is authorized to perform and which information each user is authorized to access. For example, access to options and information on the Status screen can be limited via parameter OWNER. Parameter OWNER can also facilitate selection and handling of production jobs. Parameter OWNER is passed to external security products, such as RACF, ACF2 and TOP SECRET. Default OWNER is dependent on the sites online environment (CICS, TSO, etc.). For TSO and TSO/ISPF environments, the TSO user ID is the default. For non-TSO environments (e.g., CICS), the default is the terminal ID.
4
OWNER was called USER ID prior to CONTROL-M Release 4.0.0.
3 133
OWNER
Example
Job OPERCOMP belongs to owner SYS1.
JOB: OPERCOMP LIB CTM.PROD.SCHEDULE TABLE: OPER COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME OPERCOMP MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL OPER GROUP MAINTENANCE DESC JOB RUN ON THE 1ST OF THE MONTH OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM OPERCOMP DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE INIT 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 134
PDS
PDS
Partitioned dataset (library) which should be checked for the minimum number of required free tracks (specified in parameter MINIMUM). See also MINIMUM.
Format
Optional; however, if MINIMUM is specified, PDS is mandatory. Parameter PDS specifies a dataset name of 1-44 characters. Parameter PDS cannot be used with any of the following parameters: DAYS, WDAYS, MONTHS, CONFCAL, RETRO and DATES.
General Information
The dataset must be cataloged, and it must be a partitioned dataset. Parameters MINIMUM and PDS are always used together and are never used with other Basic Scheduling parameters. Parameter PDS identifies a library. Parameter MINIMUM specifies the minimum number of free tracks required by that library. These parameters are intended for use (i.e., definition) in jobs/started tasks which compress, clean and/or enlarge libraries, or which issue a warning message to the IOA Log file (i.e., if TASKTYPE=WRN). If parameters MINIMUM and PDS are defined for a job, the scheduling of the job is not related to or dependent upon any date criteria. Instead, the job is scheduled if the actual number of free tracks available in the specified library is below the specified minimum when the New Day procedure is run. The job/started task can then compress, clean, or enlarge the library (or issue the appropriate warning). Note Parameter PDS does not work with PDSE-type libraries because they always appear to be 100 percent full.
3 135
PDS
Example
Check library SYS1.LINKLIB for a minimum of 20 unused tracks.
JOB: MSG001 LIB CTM.PROD.SCHEDULE TABLE: OPER COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME MSG001 MEMLIB GENERAL OWNER SYS1 TASKTYPE WRN PREVENT-NCT2 APPL OPER GROUP OPER-MAINT DESC INDICATE COMPRESS IS NEEDED FOR SYS1.LINKLIB OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM MSG001 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 123456789101112DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM 020 PDS SYS1.LINKLIB =========================================================================== IN CONTROL RESOURCE USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
Member MSG001 in CONTROL-Ms GENERAL JCL library contains a warning message to compress the library.
3 136
PIPE
PIPE
Indicates a dataset to be replaced by a pipe with the same name. Displayed only if CONTROL-M/WorkLoad is installed.
Format
Optional. Valid value is a valid dataset name (1-44 characters). Each time a dataset/pipe name is specified and <ENTER> is pressed, a new empty line is displayed to allow specification of an additional dataset/pipe name.
General Information
Pipes are storage buffers which are used to replace datasets. Pipes are defined in, and used by, CONTROL-M/WorkLoad to replace sequential processing with parallel processing. For example, normally (without pipes) if JOB1 writes to dataset DS1 and then JOB2 reads dataset DS1, JOB2 will wait until JOB1 is terminated before reading the dataset. However, if a pipe is used to replace dataset DS1, then as JOB1 writes data to pipe DS1, JOB2 can use the data without waiting for termination of JOB1. Each pipe and its relevant parameters are defined in a CONTROL-M/WorkLoad rule. Each pipe must be defined with the same name as the dataset it is replacing. When a job is to use a pipe instead of a dataset, the name of the dataset/pipe must be specified in the PIPE parameter of the CONTROL-M job scheduling definition for the job. For more information about Pipe processing, see Job-Related Considerations for Pipes in Section 6 of this manual.
3 137
PIPE
Example
This example consists of two job scheduling definitions. In job CTLIVPWR and job CTLIVPRD, dataset CTL.IVP.FILE is replaced by a pipe with the same name. (Jobs, such as CTLIVPWR below and CTLIVPRD on the following page, are called a Collection because they are pipe participants of the same pipe.) Job CTLIVPWR
JOB: CTLIVPWR LIB CTMT.PROD.SCHEDULE TABLE: CTLIVP COMMAND ===> SCROLL===> CRSR ------------------------------------------------------------------------------MEMNAME CTLIVPWR MEMLIB CTM.IVP.JCL OWNER E02A TASKTYPE JOB PREVENT-NCT2 APPL GROUP DESC CONTROL-M/WORKLOAD VERIFICATION - WRITER JOB OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM CTLIVPWR DOCLIB CTMT.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT. MINIMUM PDS =========================================================================== IN CTLIVPWR-IN ODAT CONTROL RESOURCE PIPE CTL.IVP.FILE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 13.18.25
3 138
PIPE
Job CTLIVPRD
JOB: CTLIVPRD LIB CTMT.PROD.SCHEDULE TABLE: CTLIVP COMMAND ===> SCROLL===> CRSR ------------------------------------------------------------------------------MEMNAME CTLIVPRD MEMLIB CTM.IVP.JCL OWNER E02A TASKTYPE JOB PREVENT-NCT2 APPL GROUP DESC CONTROL-M/WORKLOAD VERIFICATION - READER JOB OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM CTLIVPRD DOCLIB CTMT.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CTLIVPWR-OUT ODAT CONTROL RESOURCE PIPE CTL.IVP.FILE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 13.22.07
3 139
PREVENT-NCT2
PREVENT-NCT2
Handles NOT CATLGD 2 (NCT2) errors during non-restarted executions of the job.
Format
Y (Yes) N (No)
Prevent NCT2 errors by deleting and uncataloging old datasets. This value is not valid for started tasks. Do not prevent NCT2 errors. Halt processing if an NCT2 error is detected. Simulate prevention of NCT2 errors without impacting processing.
F (Flush) L (List)
The default is set in CONTROL-R installation parameters.
General Information
According to the value specified, parameter PREVENT NCT2 instructs CONTROL-R how to handle NOT CATLGD2 error situations in non-restarted reruns:
When value Y is specified:

CONTROL-R deletes and uncatalogs all datasets which can cause NCT2 errors during execution (unless the dataset name is included in an EXCLUDE DSN statement in the Restart Control parameters). NCT2 errors are thereby prevented. The list of GDG datasets is generated, via CTR301I messages, in the sysout of the job. (For information on the EXCLUDE DSN statement, refer to the descriptions of the Restart Control parameters in Section 2, and the $Default parameter member in Section 3 of the CONTROL-R User Manual.)
When value F is specified:

If an NCT2 error is detected, processing is halted and an appropriate error message is generated.
3 140
PREVENT-NCT2
When value L is specified:

NCT2 error prevention is simulated. The list of GDG datasets is generated, via CTR301I messages, in the sysout of the job (as with option Y), but no delete/uncatalog actions are performed against the datasets.
When value N is specified:

No special action is taken. NCT2 errors are not prevented. If a value of Y, F, or L is specified (i.e., if some kind of special NCT2 processing is desired), a CONTROLR step is automatically added as a first step to the submitted job. Parameter PREVENT NCT2 has no impact on restarts, because restart automatically deletes old datasets when required (i.e., restart automatically prevents NCT2 errors).
Example
Prevent NOT CATLGD 2 errors for job PRDKPL01.
3 141
PRIORITY
PRIORITY
Internal CONTROL-M job priority.
Format
Optional. Parameter PRIORITY indicates a 1-2 character alphanumeric priority. An asterisk (discussed later) can also be specified. The default is blank, which is the lowest priority.
General Information
Priority helps determine the order in which jobs in the Active Jobs file are processed by CONTROL-M. Priority is determined in ascending order where: blank < A < Z < 0 < 9 < * In general, the job with the highest priority code executes first if all its other runtime scheduling requirements are satisfied. When not all runtime requirements for a high priority job are satisfied (e.g., a job requires two tape drives but only one is available), a job with a lower priority whose other runtime requirements are satisfied can be run earlier. This, however, is not always desirable. A job may be so important that lower priority jobs should not be submitted until the important job has executed. Such a job is called a critical path job. Critical path priority can be indicated by prefixing the priority with an asterisk (*). A priority prefixed by an asterisk, e.g., priority *5, indicates that CONTROL-M should submit the job before submitting any regular (non-*) priority jobs (e.g., priority 10) and before submitting any critical path jobs of lower priority (e.g., priority *3), even if the resources required for those other jobs are available. Critical path priority is applied only after all the IN conditions for the job exist. Note Critical path priority applies to contention for Quantitative resources and for Control resources required in exclusive state. Critical path priority does not apply to contention for Control resources required in shared state.
3 142
PRIORITY
Example 1
Job EBDIN001s priority level is 07, and it requires three tapes. Job EBDIN002s priority level is 02, and it requires only one tape:
MEMNAME RESOURCE PRIORITY MEMNAME RESOURCE PRIORITY EBDIN001 TAPE 0003 07 EBDIN002 TAPE 0001 02
If only two tapes are available, job EBDIN002 will be submitted.
Example 2
Job EBDUPDTs priority level is *5, and it requires two tapes. Job EBDEXECs priority level is 04, and it requires one tape:
MEMNAME RESOURCE PRIORITY MEMNAME RESOURCE PRIORITY EBDUPDT TAPE 0002 *5 EBDEXEC TAPE 0001 04
If one tape is available, neither job will be submitted. When two tapes become available, job EBDUPDT will be submitted.
Example 3
Job EBDBKPs priority level is *8, and it requires three tapes. Job EBDMAINTs priority level is *7, and it requires one tape:
MEMNAME RESOURCE PRIORITY MEMNAME RESOURCE PRIORITY EBDBKP TAPE 0003 *8 EBDMAINT TAPE 0001 *7
If one tape is available, neither job will be submitted. When three tapes become available, job EBDBKP will be submitted.
3 143
RELATIONSHIP
RELATIONSHIP
Indicates the relationship (AND/OR) between schedule tag criteria and the jobs own basic scheduling criteria (i.e., whether either set of criteria, or both sets of criteria, are to be satisfied). This parameter appears in job scheduling definitions in Group tables only.
Format
Optional. Valid values: O (Or) A (And) If either set of criteria (a schedule tag or the jobs basic scheduling criteria) are satisfied, the job is scheduled. Default. Both a schedule tag and the jobs basic scheduling criteria must be satisfied.
General Information
For jobs in Group scheduling tables, two types of basic scheduling criteria can be specified: Schedule Tags Basic Scheduling Criteria Pointers to sets of Group criteria (i.e., basic scheduling criteria defined for the table in the Group Entity). Basic scheduling criteria defined in, and belonging to, the job scheduling definition. They are not connected to Group criteria.
In some cases, it may be required that both sets of criteria be satisfied. In other cases, satisfaction of either set of criteria is sufficient for job scheduling. This parameter allows specification of the required combination:
When either set of criteria is sufficient, specify value O (OR relationship). When both sets of criteria are required, specify value A (AND relationship).
If an AND relationship is specified when no schedule tags are defined in the job, will the job never be scheduled.
3 144
RELATIONSHIP
Example
Create a table of employee hours each payday and on the last day of the year.
JOB: TABHOURS LIB CTM.PROD.SCHEDULE TABLE: ACCOUNTS COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME TABHOURS MEMLIB CTM.PROD.JCL OWNER N04B TASKTYPE JOB PREVENT-NCT2 APPL GROUP ACCOUNT_GROUP DESC TABULATE EMPLOYEE HOURS OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM TABHOURS DOCLIB CTM.PROD.DOC =========================================================================== SCHEDULE TAG PAYDAYS SCHEDULE TAG RELATIONSHIP (AND/OR) O DAYS 31 DCAL AND/OR WDAYS WCAL MONTHS 1- N 2- N 3- N 4- N 5- N 6- N 7- N 8- N 9- N 10- N 11- N 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN ODAT USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 18.36.07
3 145
RERUN-MAXRERUN
RERUN-MAXRERUN
Maximum number of automatic reruns to be performed for the job.
Format
Optional. Valid values are 0 9. Default: 0 (no automatic reruns).
General Information
When a job is first run, the MAXRERUN field in the Active environment (i.e., in the Zoom screen) contains the same value as parameter MAXRERUN in the job scheduling definition. However, in the Active environment MAXRERUN works as a reverse-counter of automatic reruns: Each time the job is automatically rerun, the value is decreased by one until the field contains a value of zero. The automatic rerun process works as follows:
The CONTROL-M monitor determines that automatic rerun is possible only if the job ENDS NOTOK and a specified DO RERUN statement is activated during post-processing. If the monitor determines that automatic rerun is possible, it sets the jobs status to ENDED NOTOK RERUN NEEDED. The monitor then checks the value of MAXRERUN in the Active environment. If the value is zero, automatic rerun is not possible and the job is not submitted for rerun. If the value is greater than zero, rerun is possible and the monitor will submit the job for rerun when all runtime criteria are satisfied. Runtime criteria include not only criteria in the Runtime Scheduling parameters, but also parameter INTERVAL which specifies the minimum allowable interval between runs of the same job. The JCL for the rerun job is taken from the member specified in parameter RERUNMEM. If no RERUNMEM value is specified, the JCL for the rerun is taken from the jobs regular JCL member specified in parameter MEMNAME.
MAXRERUN applies only to automatic reruns. The MAXRERUN counter is not affected by reruns performed manually (i.e., via option Rerun in the Status screen). Parameter MAXRERUN cannot be specified for cyclic jobs and cyclic started tasks.
3 146
RERUN-MAXRERUN
Example 1
A tape I/O error occurred. Try two more times. If there are two more failures, give up:
RERUN - MAXRERUN 2 RERUNMEM ON PGMSTEP STEP01 PROCSTEP DO RERUN INTERVAL CODES S613
Example 2
When a job abends for any reason, try to restart it two more times (at the abended step).
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT PRDKPL01-ENDED-OK ODAT + AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN 2 RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 A/O DO IFRERUN FROM $ABEND . TO . CONFIRM N DO RERUN DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
11.17.00
3 147
RERUN-RERUNMEM
RERUN-RERUNMEM
Name of the JCL member to use when the job is automatically rerun.
Format
Optional. Parameter RERUNMEM identifies a valid member name of 1 8 characters.
General Information
Although parameter RERUNMEM can be used to specify the name of a JCL member to use for automatic rerun, the following points should be noted:
Parameter DO FORCEJOB provides a more flexible alternative to parameter RERUNMEM. CONTROL-R users can use parameter DO IFRERUN to restart the failed job instead of using RERUNMEM to rerun the job.
The automatic rerun process works as follows:
The CONTROL-M monitor determines that automatic rerun is possible only if the job ENDS NOTOK and a specified DO RERUN statement is activated during post-processing. If the monitor determines that automatic rerun is possible, it sets the jobs status to ENDED NOTOK RERUN NEEDED. The monitor then checks the value of MAXRERUN in the Active environment. If the value is zero (or no MAXRERUN value was specified), automatic rerun is not possible and the job is not submitted for rerun. If the value is greater than zero, rerun is possible and the monitor will submit the job for rerun when all runtime criteria are satisfied. Runtime criteria include not only the Runtime Scheduling parameters, but also parameter INTERVAL which specifies the minimum allowable interval between runs of the same job. The JCL for the rerun job is taken from the member specified in parameter RERUNMEM. If no RERUNMEM value is specified, the JCL for the rerun is taken from the jobs regular JCL member specified in parameter MEMNAME.
Rules applying to parameter MEMNAME also apply to parameter RERUN. The member name can be the same as, or different from, the job name.
3 148
RERUN-RERUNMEM
The member specified in RERUNMEM should be in the library specified in parameter MEMLIB. Parameter RERUNMEM overrides the MEMNAME value in the JCL, and the MEMNAME value becomes irrelevant for reruns. Parameter RERUNMEM cannot be specified for cyclic jobs and cyclic started tasks. Parameter RERUNMEM cannot be specified if a DO IFRERUN statement is specified.
Example
If job EF145TS abends during step name COLLECT, try to run another job from member EF145TSR that will continue from the same place.
JOB: EF145TS LIB CTM.PROD.SCHEDULE TABLE: EFPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN 2 RERUNMEM EF145TSR INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST COLLECT PROCST CODES S*** U**** A/O DO RERUN DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
11.17.00
3 149
RESOURCE
RESOURCE
Quantitative resources and their quantities required by the job.
Format
Optional. A maximum of two Quantitative resources can be specified in each RESOURCE line. Upon specifying the second Quantitative resource in a line and pressing <ENTER>, a new line is opened (for specifying additional Quantitative resources). Each specified Quantitative resource consists of the following mandatory subparameters: res-name quantity User-supplied, descriptive name of 1-20 characters to identify the quantitative resource. Quantity of the resource required by the job. The specified value must be four digits (all leading zeros must be specified).
General Information
Quantitative resource specification can be used to prevent resource contention. Quantitative resources (e.g., tape drives, CPU, access rates to the spool) and their maximum available quantities are defined for the site via the IOA Conditions/Resources screen (Screen 4). Note If optional wish WM2744 (Automatic Tape Adjustment) is installed, any tape drive value defined in parameter RESOURCE is automatically overridden during job ordering, and is replaced by a value determined by the Automatic Tape Adjustment facility. For more information, refer to Tape Device Usage Statistics in the description of the Statistics screen in Section 2 of this manual.
Example
TAPE 12 CPU 80 WORK-SPACE 3000
3 150
RESOURCE
To eliminate bottlenecks and maximize throughput, a site can quantify processing power and assign it a resource name, such as CPU or LPU (logical processing units). The more powerful the CPU, the greater the maximum quantity that can be assigned to it. Parameter RESOURCE is used to specify the quantity of a resource required by the job. Before a job is submitted, CONTROL-M verifies that the required quantities of resources, defined via RESOURCE statements, are available (i.e., that they are not in use by another job):
If they are available, CONTROL-M allocates them to the job, and they become unavailable to other jobs until they are freed. If the resources required by the job are unavailable, the job is not submitted.
Resource Allocation in Multi-CPU Environments In multi-CPU environments, several resource allocation possibilities exist. One possibility is to operate as if there is one large CPU and resource pool. In this case, no logical differentiation between CPUs is made, and the CONTROL-M monitor assigns resources, including CPU processing power, from the total resources available. Another possibility is to differentiate between CPUs and optionally to logically associate quantities of resources with specific CPUs. This is generally achieved via the use of common identifiers (e.g., a suffix). For example, suppose a site has three CPUs of differing processing capability. The following representative resources and quantities might be defined in the IOA Conditions/Resources file:
CPU-A 50 CPU-B 75 CPU-C 100
In this example, it might also be desired to logically categorize other resources according to CPU. For example, if 12 tape drives are available, the following resources and quantities might also be defined in the IOA Conditions/Resources file:
TAPE-A 3 TAPE-B 4 TAPE-C 5
If this kind of differentiation is used, different resources in the job scheduling definition can be specified with different suffixes, and the job will still run (e.g., a quantity of CPU-A can be specified along with a quantity of TAPE-B). Rather than specifying a particular identifier when requesting a resource, resources can be requested generically by specifying a $ in place of the identifier (e.g., CPU-$ or TAPE-$). The $ indicates to CONTROL-M that it should select a specific resource (i.e., a resource with an identifier) to replace the generic resource (i.e., the resource with the $). If a $ is specified for all required resource identifiers, the CONTROL-M monitor will not assign the resources unless it can assign all resources with the same identifier (e.g., all resources with identifier A or all resources with identifier B).
3 151
RESOURCE
When using the generic $ identifier, you can use one of the following methods to ensure a specific CPU will be used for processing the job:
Use JCL AutoEdit system variable %%$SIGN to extract the CPU identifier assigned by the CONTROL-M monitor and then to assign the job to that same CPU. (A description of System variable %%$SIGN and an example of its usage is provided in Section 5 of this manual.) Use CONTROL-M submit exit CTMX002.
CONTROL-M exit CTMX004 can also be used to help prevent bottlenecks caused by resource contention. (For more information on CONTROL-M exits CTMX002 and CTMX004, see Section 10 of the IOA Administrator Guide.)
Example 1A
There are 12 tape drives in the data center connected to a single computer. Two tape drives must always remain free for emergencies. Therefore, only 10 drives can be used for production. The defined available quantity is set as follows: TAPE 0010. Any user (job) wanting to use tape drives must specify the number of tapes required in the job parameters.
JOB: EBDINPUT LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDINPUT MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP EBD-PRODUCTION DESC EBD PRODUCTION COLLECT INPUT TAPES OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDINPUT DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12-Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 04 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE TAPE 0002 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
CONTROL-M checks if there are two tape drives available. If there are, the tape drives are given to the job. The total number of free tapes is now eight. When the job finishes executing, the tape drives are returned to the general pool. Suppose that many jobs are using tapes, and the available quantity is only one. A job which requires two tape drives will have to wait. The job will not be submitted until the required number of tapes are available.
3 152
RESOURCE
An authorized person decides that only one tape unit is needed for emergencies and adds one tape unit to the global quantity available for use. Now the maximum number of tape drives is eleven, and the number of available tape drives is two. The job will be submitted.
Example 1B
The data center discussed in the previous example is expanding. It now has two computers and 20 tape drives. The tape drive distribution is: CPU1 only CPU2 only 8 6
Transferable 6 Currently, CPU1 is connected to four transferable drives, one transferable drive is connected to CPU2, and one transferable drive is out of order. The situation is presented to CONTROL-M as follows:
TAPE1 12 TAPE2 7
A job requests three tape drives, on any computer.

JOB: EBDINPUT LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDINPUT MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP EBD-PRODUCTION DESC EBD PRODUCTION COLLECT INPUT TAPES OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDINPUT DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12-Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 04 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE TAPE$ 0003 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
The result is that the available quantity of either TAPE1 or TAPE2 is reduced by three. The CONTROL-M scheduling algorithm makes the optimal decision as to which of the two computers to send the job. It is possible to intervene in this selection process. (For more information, see user exit CTMX004 in Section 10 of the IOA Administrator Guide.)
3 153
RESOURCE
Example 1C
A job requests three tape drives on CPU1.
JOB: EBDINPUT LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME EBDINPUT MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP EBD-PRODUCTION DESC EBD PRODUCTION COLLECT INPUT TAPES OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM EBDINPUT DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12-Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 04 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE TAPE1 0003 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
The result is that the available quantity of the resource TAPE1 is reduced by three. The tape drive that was out of order has been fixed. An operator makes it available for use by jobs running on CPU2 by correcting the global available quantities to:
TAPE2 8
The shift manager decides to assign two tapes from CPU1 to CPU2. The new situation as seen by CONTROL-M:
TAPE1 10 TAPE2 10
3 154
RETENTION: # OF DAYS TO KEEP


Number of days to retain the job in the History Jobs file. Note
At sites which do not use the History Jobs file, this parameter is not relevant and is not displayed.
Format
Optional. Valid values: 001 999 blank Retain the job for the specified number of days. Retain the job according GENERATIONS TO KEEP. to parameter RETENTION: # OF
General Information
Jobs in the History Jobs file are easier to restore to the Active Jobs file (e.g., for restart) than jobs archived to CDAM. Therefore, it may be desirable to retain a job in the History Jobs file for a period of time. # OF DAYS TO KEEP enables specification of a fixed number of days to keep the job in the History Jobs file. Once the specified number of days has been reached, the job is automatically deleted from the History Jobs file during the next New Day processing. # OF DAYS TO KEEP and # OF GENERATIONS TO KEEP are mutually exclusive. A value can be specified for either, but not both. Notes When changing job criteria from retention-days to retention-generation (or vice-versa), previous job criteria are lost and will not be acted upon. For retention criteria to hold across job executions, the jobs must be identical in all respects. (For example, if a job is transferred to a different group, it is treated as a different job for purposes of retention. In this case, retention values are reset, and retention is calculated from the moment of transfer.)
3 155

Example
Retain the archived job in the History Jobs file for 30 days.
JOB: PRDKPL02 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ RESOURCE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN 3 RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O CODES DO IFRERUN FROM $ABEND . TO . CONFIRM Y DO RERUN DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< ===== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 07.06.04
3 156
RETENTION: # OF GENERATIONS TO KEEP

Maximum number of generations of the job to keep in the History Jobs file. Note At sites which do not use the History Jobs file, this parameter is not relevant and is not displayed.
Format
Optional. Valid values: 01 - 99 blank Retain the specified number of generations of the job. Retain the job according to parameter RETENTION: # OF DAYS TO KEEP.
General Information
Jobs in the History Jobs file are easier to restore to the Active Jobs file (e.g., for restart) than jobs archived to CDAM. Therefore, it may be desirable to retain several of the most current generations of the job in the History Jobs file. # OF GENERATIONS TO KEEP enables specification of the number of generations of the job to keep in the History Jobs file. Once the specified number of generations has been reached, as a new generation is added to the History Jobs file, the earliest remaining generation is deleted. # OF DAYS TO KEEP and # OF GENERATIONS TO KEEP are mutually exclusive. A value can be specified for either, but not both. Notes When changing job criteria from retention-days to retention-generation (or vice versa), previous job criteria are lost and will not be acted upon. For retention criteria to hold across job executions, the jobs must be identical in all respects. (For example, if a job is transferred to a different group, it is treated as a different job for purposes of retention. In this case, retention values are reset, and retention is calculated from the moment of transfer.)
3 157

Example
Retain up to 10 generations of the archived job in the History Jobs file.
JOB: PRDKPL02 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ RESOURCE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP # OF GENERATIONS TO KEEP 10 SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN 3 RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O CODES DO IFRERUN FROM $ABEND . TO . CONFIRM Y DO RERUN DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< ===== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 07.6.04
3 158
RETRO
RETRO
Enables the job to be scheduled after its original scheduling date has passed.
Format
Optional. Valid values: Y (Yes) Allow scheduling of the job after its original scheduling date has passed. Do not allow scheduling of the job after its original scheduling date has passed. Default.
N (No)
General Information
Parameter RETRO is used to control situations where the computer has not been working for a day or more due to holiday, hardware failure, etc. When such situations occur, it is necessary to instruct CONTROL-M whether or not the job should be retroactively scheduled for the days when the computer (or CONTROL-M) was inactive.
When Y is specified for parameter RETRO, job orders are placed in the Active Jobs file for all the days the job should have been originally scheduled. Scheduling occurs from the last scheduling date to the current working date, provided that those days were included in one of the Basic Scheduling parameters (DAYS, DCAL, etc.). Each job order placed on the Active Jobs file is associated with a different original scheduling date. See parameter MAXWAIT for additional information. When N is specified for parameter RETRO, the job is scheduled only if the current working date is a date on which the job is normally scheduled.
Parameter RETRO cannot be used with parameters MINIMUM and PDS, nor in group scheduled jobs.
3 159
RETRO
Example 1
Schedule the job only on specified days of the month. If the date has passed, do not schedule the job.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME PRDKPL01 MEMLIB CTM.PROD.JCL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL KPL GROUP PROD-KPL DESC DAILY PRODUCTION - START OF APPL-PROD-KPL OVERLIB SET VAR DOCMEM PRDKPL01 DOCLIB CTM.PROD.DOC =========================================================================== DAYS 15,16,18,19,20 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE PIPE TIME: FROM UNTIL PRIORITY CONFIRM USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
Assume the computer was offline from the 16th up to (and including) the 18th, and the 15th was the last date that the job was scheduled for execution. Today is the 19th. Therefore, the job is only scheduled for execution on the 19th.
Example 2
Schedule the job for all working days, whether or not the computer is active:
DCAL WORKDAYS RETRO Y
Assume the WORKDAYS calendar contains the dates 15, 16, 18, and 19, and the same conditions as above exist. The job is scheduled three times with the original scheduling dates: the 16th, the 18th and the 19th.
3 160
SCHEDULE TAG
SCHEDULE TAG
Identifies a set of scheduling criteria for Group scheduling. This parameter appears only in Group scheduling tables. See also RELATIONSHIP.
Format
For Group Entities For job scheduling definitions
Mandatory. characters.
Any
alphanumeric
value
of
20
Optional. Must be either a schedule tag value defined in the Group Entity, or the value *.
Upon specifying a schedule tag value and pressing <ENTER>, a new SCHEDULE TAG field is opened (for specifying additional schedule tags). In Group Entities, a new set of basic scheduling parameters is opened with the new SCHEDULE TAG field to allow specification of criteria to be associated with the new tag.
General Information
A Group Entity contains sets of basic scheduling criteria to be applied to job scheduling definitions in the Group scheduling table. Each set of basic scheduling criteria in the Group Entity is assigned a unique label, specified in the SCHEDULE TAG field, which is used for referencing that set of criteria. At least one SCHEDULE TAG, with basic scheduling criteria, must be defined in the Group Entity. To apply any set(s) of Group Entity basic scheduling criteria to a job scheduling definition, specify the schedule tag name(s) of the desired criteria in the SCHEDULE TAG field(s) in the job scheduling definition. If multiple SCHEDULE TAG values are specified in the job scheduling definition, tags are checked sequentially during job scheduling to determine if the criteria are satisfied. Once a set of schedule tag criteria are satisfied, no other schedule tags in the job are checked.
3 161
SCHEDULE TAG
An asterisk (*) can be specified as a SCHEDULE TAG value in the job scheduling definition. When checks are performed for a SCHEDULE TAG with a value of *, the first set of basic scheduling criteria in the Group Entity which is satisfied on the particular day is applied to the job. Each job scheduling definition can have its own basic scheduling criteria defined, independent of the schedule tag criteria in the Group Entity. Jobs in a Group scheduling table are eligible for scheduling on a particular day only if at least one set of basic scheduling criteria in the Group Entity are satisfied. If a group is eligible for scheduling on a particular day, a job in the group is scheduled in any of the following cases:
The value in parameter RELATIONSHIP is O (OR), and either the jobs basic scheduling criteria or a set of its schedule tag criteria (or both) are satisfied. The value in parameter RELATIONSHIP is A (AND), and its basic scheduling criteria and a set of its schedule tag criteria are both satisfied.
Example 1A
For a Group Entity: The Group Entity for group ACCOUNTS_GROUP (in Group scheduling table ACCOUNTS) contains two sets of basic scheduling parameters. One set is identified by schedule tag ALL_DAYS, and the other set is identified by schedule tag SUNDAYS.
GRP ACCOUNTS_GROUP CTM.PROD.SCHEDULE(GRP) COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ GROUP ACCOUNTS_GROUP MEMNAME ACCOUNTS OWNER N04B APPL DESC ADJUST CONDITIONS N SET VAR DOCMEM ACCOUNTS DOCLIB CTM.PROD.DOC =========================================================================== SCHEDULE TAG ALL_DAYS DAYS ALL DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT =========================================================================== SCHEDULE TAG SUNDAYS DAYS DCAL AND/OR WDAYS 01 WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT =========================================================================== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 18.19.14
3 162
SCHEDULE TAG
Example 1B
For a job scheduling definition: Schedule job TABHOURS when the basic scheduling criteria identified by schedule tag ALL_DAYS in the Group Entity (in Example 1A) are satisfied.
JOB: TABHOURS LIB CTM.PROD.SCHEDULE TABLE: ACCOUNTS COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME TABHOURS MEMLIB CTM.PROD.JCL OWNER N04B TASKTYPE JOB PREVENT-NCT2 APPL GROUP ACCOUNT_GROUP DESC TABULATE EMPLOYEE HOURS OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM TABHOURS DOCLIB CTM.PROD.DOC =========================================================================== SCHEDULE TAG ALL_DAYS SCHEDULE TAG RELATONSHIP (AND/OR) O DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO N MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 18.36.07
3 163
SET VAR
SET VAR
Assigns a value to an AutoEdit variable which can be used to set up the jobs JCL. Note Statements SET VAR and DO SET are very similar. If you are familiar with one of them, you can easily use the other. You should, however, be familiar with the differences outlined below in SET VAR / DO SET Differences.
Format
Optional. Valid values must be specified in the format: %%variable=expression where: %%variable expression User-defined AutoEdit variable. Any of the following components, provided it resolves to a single value:
Value (e.g., 5). AutoEdit system variable or previously defined user-defined variable
(e.g., %%ODATE). Note To specify embedded blanks in a SET VAR expression, use AutoEdit variable %%BLANKn (e.g., %%A = TODAY%%BLANK1.IS%%BLANK1.SUNDAY).
General Information
Parameter SET VAR is generally used to assign a value to an AutoEdit variable in the jobs JCL. The value is assigned at time of job submission. The advantage of using AutoEdit variables in the JCL is that the JCL can be submitted with different values for different executions without actually changing the JCL.
3 164
SET VAR
The JCL of the job can contain two types of AutoEdit variables:
System variables which are assigned values by the system. User-defined variables for which the user must supply values.
One method of supplying a value for a user-defined variable is by defining the variable and its value in a SET VAR statement. An unlimited number of SET VAR statements can be specified. Upon filling in a SET VAR statement and pressing <ENTER>, a new blank SET VAR statement is displayed. At time of job submission, AutoEdit variables in the JCL are resolved in sequence. If an AutoEdit variable cannot be resolved, the job is not submitted. Multiple AutoEdit variables (and constants) can be joined together into a complex user-defined variable. To resolve a complex user-defined variable, its component variables must first be resolved. Therefore, simple user-defined variables which comprise a complex user-defined variable must be either:
-or-
Specified in a previous SET VAR statement.
Defined earlier in the JCL with a %%SET control statement.
JCL Setup and the AutoEdit facility are described in depth in Section 5 of this manual. SET VAR / DO SET Differences SET VAR and DO SET statements are similar but have the following differences:
SET VAR is always applied before the job is submitted. DO SET is a Post-processing parameter whose accompanying ON step/code criteria can only be satisfied during a job run. Therefore, DO SET can only be applied if its accompanying ON step/code criteria are satisfied, and the value specified in the DO SET statement cannot be used until the next submission of the job (i.e., for cyclic and rerun/restarted jobs). Statement SET VAR appears in each job scheduling definition. Statement DO SET does not appear unless specified. To specify a DO SET statement, type SET in an empty DO field and press <ENTER>. In statement SET VAR, the parameter value is specified after the keyword VAR. In statement DO SET, the parameter value is specified after the keyword VAR=.
3 165
SET VAR
Example 1
In this example, AutoEdit statements in the job scheduling definition and the JCL allocate space for the job. If the job abends due to insufficient space, the AutoEdit statements adjust the allocated space and rerun or restart the job. The following step in the jobs JCL sets the quantity of available space to five units of whatever type (track or cylinder) is specified in the job scheduling definition.
//STEP10 EXEC PGM=MYPGM //OUTFILE DD DSN=NEWFILE,DISP=(NEW,CATLG,DELETE), // SPACE=(%%SPACE_TYPE,5),UNIT=SYSDA
The job scheduling definition contains the following SET VAR statement which sets the space type to track:
SET VAR %%SPACE_TYPE = TRK
In this case, the second line in the above DD statement resolves to:
// SPACE=(TRK,5),UNIT=SYSDA
The job scheduling definition also contains the following statements which are activated if the job abends due of lack of space (code S*37). These statements change the space type to cylinder (which will provide enough space), and rerun the job. (If CONTROL-R is active, the job will be restarted from the abended step.)
ON PGMST STEP10 CODES S*37 DO SET %%SPACE_TYPE = CYL [DO IFRERUN FROM $ABEND] ===> If CONTROL-R is active DO RERUN
If the job abends due to insufficient space, the second line of the earlier JCL DD statement resolves to:
// SPACE=(CYL,5),UNIT=SYSDA
when the job is submitted for rerun (or restart).
3 166
SET VAR
Examples 2A and 2B
The following examples show how one job scheduling definition and one JCL member can be used for both the test environment and the production environment by changing the value of only one parameter parameter SET VAR. Assume the following JCL for the job:
//PRDKPL01 JOB //STEP01 EXEC //STEP02 EXEC //STEP03 EXEC 0,M22,CLASS=A,MSGCLASS=X,REGION=4000K %%PROC%%.INPT %%PROC%%.UPDT %%PROC%%.RPTS
Example 2A
The following job scheduling definition replaces the %%PROC variable in the EXEC statements of the JCL with procedure name prefix TEST.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME PRDKPL01 MEMLIB CTM.PROD.JCL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL KPL GROUP PROD-KPL DESC DAILY PRODUCTION - START OF APPL-PROD-KPL OVERLIB SET VAR %%PROC=TEST SET VAR CTB STEP AT NAME TYPE DOCMEM PRDKPL01 DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN START-DAILY-PROD-KPL ODAT CONTROL DB2-MAIN-FILE E USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
When statement SET VAR is used to specify %%PROC=TEST, the JCL will be resolved as follows:
//PRDKPL01 JOB //STEP01 EXEC //STEP02 EXEC //STEP03 EXEC 0,M22,CLASS=A,MSGCLASS=X,REGION=4000K TESTINPT TESTUPDT TESTRPTS
3 167
SET VAR
Example 2B
The job scheduling definition has now been modified to replace the procedures (%%PROC) used in the job with production (PROD) procedures.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ MEMNAME PRDKPL01 MEMLIB CTM.PROD.JCL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL KPL GROUP PROD-KPL DESC DAILY PRODUCTION - START OF APPL-PROD-KPL OVERLIB SET VAR %%PROC=PROD SET VAR CTB STEP AT NAME TYPE DOCMEM PRDKPL01 DOCLIB CTM.PROD.DOC =========================================================================== DAYS 01 DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN START-DAILY-PROD-KPL ODAT CONTROL DB2-MAIN-FILE E USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
When statement SET VAR is used to specify %%PROC=PROD, the JCL will be resolved as following:
//PRDKPL01 JOB //STEP01 EXEC //STEP02 EXEC //STEP03 EXEC 0,M22,CLASS=A,MSGCLASS=X,REGION=4000K PRODINPT PRODUPDT PRODRPTS
3 168
SHOUT
SHOUT
Sends (shouts) a message to a destination when a specific situation occurs. Note The SHOUT statement is similar to statement DO SHOUT. If you are familiar with the DO SHOUT statement, you can easily use the SHOUT Statement. You should however, be familiar with the differences outlined in SHOUT/DO SHOUT Differences in the description of DO SHOUT earlier in this section.
Format
Optional. Upon filling in the SHOUT statement and pressing <ENTER>, a new SHOUT statement is opened. Each SHOUT statement consists of four subparameters: WHEN (situation), TO (destination), URGN (urgency), and MS (message text). WHEN Situation in which to send the message. Valid values: OK NOTOK RERUN The message is sent if the job ends OK. The message is sent if the job ends NOTOK. The message is sent if the job is rerun and DO RERUN is specified in ON PGMST.
LATESUB time The message is sent if the job is not submitted by the specified time, where time is in format hhmm or an *. If * is specified, the CONTROL-M monitor uses the jobs calculated DUE IN time (as displayed in the Zoom screen) to determine if the job was not submitted on time (see Automatic Job Flow Adjustment in Section 1 of this manual).
3 169
SHOUT
LATE time
The message is sent if the job does not finish executing by the specified time, where time is either in format hhmm or an *. If * is specified, the CONTROL-M monitor uses the jobs calculated DUE OUT time (as displayed in the Zoom screen) to determine if the job is late (see Automatic Job Flow Adjustment in Section 1 of this manual).
EXECTIME limit The message is sent if the jobs elapsed runtime is outside a specified limit. The limit can be expressed as a runtime limit, or as a deviation from the jobs average runtime. Valid formats for limit are (where n is a 3-digit non-zero value): >n <n +n Jobs elapsed runtime is greater than n minutes. n cannot exceed 999. Jobs elapsed runtime is less minutes. n cannot exceed 999. than n
Jobs elapsed runtime exceeds the jobs average execution time by at least n minutes. n cannot exceed 999. Jobs elapsed runtime is at least n minutes less than the jobs average execution time. n cannot exceed 999. Jobs elapsed runtime exceeds the jobs average execution time by at least n%. n cannot exceed 900. Jobs elapsed runtime is at least n% less than the jobs average execution time. n cannot exceed 99.
+n%
n%
TO
Destination of the message. (1-16 characters). Mandatory. Valid values: U-userid or USERID-userid Writes the message to the IOA Log file under the specified user ID. userid must be 1-8 characters. OPER[n] Sends a rollable message to the operator console. n is an optional 2-digit route code. If a route code is not specified, the default routes are Master Console and Programmer Information (1 and 11). Route codes are listed in Appendix D. Sends an unrollable, highlighted message to the operator console. n is an optional 2-digit route code. If a route code is not specified, the default routes are Master Console and Programmer Information (1 and 11). Route codes are listed in Appendix D.
OPER2[n]
[TSO-logonid | T-logonid][;Nn|;Mm|;NnMm|;Lname] Sends the message to the user identified by the logonid. logonid is mandatory (1-7 characters).
3 170
SHOUT
An optional second value, indicating the computer and/or node (e.g., Mm) of the TSO logonid, can be specified as follows:
Under JES2:
Valid values are Nn, Mm or NnMm, where: m n Machine ID (the computer in JES2, not the 4-character SMF ID). 1-2 character JES/NJE node ID.
Under JES3:
The only valid value is Lname, where: name Logical JES name of the machine (i.e., as used in JES3 command *T, not the MVS/SMF system ID).xe "TSO SEND Command:SHOUT Parameter" A shout to a TSO user performs a TSO SEND command which may require authorization at the receiving node.
Note
URGN
MS
Message text. Maximum length: 70 characters.
General Information
The message is sent to the specified destination when the WHEN condition is satisfied. The relationship between multiple SHOUT statements is OR (i.e., each statement is evaluated and performed independently of the others). CONTROL-M AutoEdit system variables in the message text are supported and automatically resolved (replaced) when the SHOUT message is issued. (See Section 5 of this manual for more information.) Subparameter WHEN If SHOUT WHEN EXECTIME values are stated with a + or sign (i.e., when elapsed runtime is compared to average runtime), the shout applies only if there is a current Job Statistics file for the job (containing statistics for at least one of the last 20 runs of the job). If a current Job Statistics file exists, all available elapsed-time statistics for the last 20 job runs are averaged to generate the average runtime, and the current runtime is compared to this figure according to the specified criteria. If no Job Statistics file exists, or if the file is not current (i.e., there are no elapsed-time statistics for any of the last 20 job runs), the SHOUT is not applied.
3 171
SHOUT
Note
Your IOA administrator can tell you if the job has a Statistics file, and if the Statistics file is updated after each job run.
If EXECTIME values are negative (i.e., n; n%), the check can be performed only after the job has finished running. When EXECTIME values are positive (i.e., +n; +n%), the check can be performed (and if the elapsed runtime limits are exceeded, the message can be shouted) before the job has finished running. Relative EXECTIME limits should not exceed 24 hours. When relative EXECTIME limits exceed 24 hours (e.g., if +n(%) of the average runtime exceeds 24 hours), the message is shouted if and when processing reaches 24 hours. If a relative EXECTIME is not specified prior to job submission, but is specified afterwards (i.e., the job is held, the parameters changed in the Zoom screen, and the job is then freed), the EXECTIME value is ignored. Subparameter TO When TO=USERID-userid, the message is written to the IOA Log file, under the user ID specified in the parameter. When TO=OPER[n], the message is sent to the operator console (route code n). If the n value is omitted, the message is sent to all consoles. See Appendix D. When TO=OPER2[n], an unrollable, highlighted message is sent to the operator console (route code n). If the n value is omitted, the message is sent to all consoles. See Appendix D. When TO=TSO-logonid or T-logonid, the message is sent to the TSO logonid. When a second value is used, the message is sent to the TSO logon ID in the specified computer/node (machine ID). When Enterprise Controlstation is installed and TO is set to the reserved keyword U-ECS, the message is sent to the Enterprise Controlstation. To determine the machine ID under JES2, specify JES command $LSYS. Notes The TO field is also controlled by the IOA Dynamic Destination table. The TO field is first checked against the IOA Dynamic Destination table. If the table contains an entry that matches the TO value, the entrys content is used as the target for the shouted message. The entire TO field is used. Therefore, when directing the message to a remote user, do not append ;Mm or ;Nn. Instead, do this in the destination table. See IOA Dynamic Destination Table in Section 2 of the IOA Administrator Guide. Subparameter URGN The URGN value indicates the urgency of the message. In addition, if the destination is USERIDuserid (or Uuserid), the user can control, according to urgency, which messages are displayed when the IOA Log file is accessed. Urgent and very urgent messages will be highlighted on the screen. For more details, see IOA Log Facility in Section 2 of this manual.
3 172
SHOUT
Example 1
If the job finishes executing OK, write a message to the IOA Log file under the specified user ID:
MEMNAME GPLSP0007 DAYS 01,15 SHOUT WHEN OK TO U-SHIFTMNGR URGN R MS I HAVE FINISHED FOR TONIGHT
The message is written to the log under CONTROL-M userid-SHIFTMNGR.
Example 2
When IMS is not active, send a message to all operators.
JOB: IMSPROD LIB CTM.PROD.SCHEDULE TABLE: IMSPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE FR (PGM.PROC) . TO . ON PGMST PROCST CODES A/O DO SHOUT WHEN OK TO OPER2 URGN R MS ******* IMS IS NOT ACTIVE ******* SHOUT WHEN NOTOK TO OPER2 URGN R MS ******* IMS IS NOT ACTIVE - ENDED ABNORMALLY ******* SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
11.17.00
If IMS finishes executing, an unrollable message is sent to the operator. A different message is sent if IMS terminates abnormally.
3 173
STEP RANGE
STEP RANGE
Step range in the job which can be used in an ON PGMST statement. See also ON.
Format
Optional. STEP RANGE consists of the following subparameters: STEP RANGE FR (PGM.PROC) Name for the range. A name of 1-7 characters can be specified. Only trailing blanks are allowed in this field. First pgmstep or pgmstep.procstep in the range. Note pgmstep is the step name in the EXEC statement which identifies the program to be executed:
//pgmstep EXEC PGM=pgmname
procstep is the step name in the EXEC statement which invokes the procedure:
//procstep EXEC procname
pgmstep values and procstep values can each be 1-8 characters in length. TO Last pgmstep (or pgmstep.procstep) in the range. See the note above in subparameter FR. Subparameter TO is optional. If blank, its value defaults to the last step in the job.
3 174
STEP RANGE
General Information
Whenever a STEP RANGE statement is specified, it eliminates the need to define separate ON PGMST/PROCST/CODES statements and accompanying DO actions for each step in the range. The defined STEP RANGE name can be used (without redefining the range) in subsequent ON PGMST/PROCST/CODES statements, by specifying the step range name, preceded by an asterisk, in the ON PGMST field. (See the ON PGMST/PROCST/CODES parameter in this section of the manual.) Any number of step ranges can be specified. After entering a STEP RANGE parameter, another STEP RANGE parameter line is automatically displayed.
Example
Define program steps STEP20 through STEP29A as step range DF2. If any of these steps produce any system or user abend (except user abend U2030), rerun the job and shout a message to TSO-P43.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP (C,D,F,N,R) FROM RERUN - MAXRERUN RERUNMEM INTERVAL STEP RANGE DF2 FR (PGM.PROC) STEP20 . TO STEP29A . STEP RANGE FR (PGM.PROC) . TO . ON PGMST *DF2 PROCST CODES S**** U**** NU2030 A/O DO RERUN DO SHOUT TO TSO-P43 URGENCY R = JOB PRDKPL03 ABENDED, THE JOB IS RERUN DO ON PGMST PROCST CODES A/O DO SHOUT WHEN TO URGN MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
11.17.00
3 175
SYSOUT
SYSOUT
Controls handling of job output after the job ended OK. Note
Statements SYSOUT and DO SYSOUT are similar. If you are familiar with one of them, you can easily use the other. You should, however, be familiar with the differences outlined below in SYSOUT / DO SYSOUT Differences.
Format
Optional. SYSOUT consists of the following subparameters: OP Sysout option code. Mandatory. Valid values: F D R C N data Copy the job output to file. Delete (purge) the job output. Release the job output. Change the class of the job output. Change the destination of the job output.
Relevant sysout data. Mandatory and valid only if the specified OP value is F, C, or N. Valid values depend on the OP value, as follows: F C N File name. New class (1 character). An asterisk (*) indicates the jobs original MSGCLASS. New destination (1-8 characters).
FROM
FROM class. Optional. Limits the sysout handling operation to only those sysouts from the specified class. Note If a FROM class is not specified, all sysout classes are treated as a single, whole unit.
3 176
SYSOUT
General Information
When a job ends OK, the CONTROL-M monitor, unless otherwise instructed, leaves the job sysout in HELD class in the output queue. Parameter SYSOUT is used to request additional handling of these held sysouts when the job ends OK. The CONTROL-M monitor sends all sysout handling requests to JES which processes the instructions. If, however, the copying of sysouts to a file is requested (option F), CONTROL-M requests the sysouts from JES and then CONTROL-M directly writes the sysout to the file. Only one SYSOUT statement can be defined in a job scheduling definition. To specify additional sysout handling instructions (in addition to the one SYSOUT statement), define appropriate DO SYSOUT statements:
DO SYSOUT statements are activated when their accompanying ON step/code event criteria are satisfied. To define DO SYSOUT statements that act like a SYSOUT statement (i.e., that operate only when the job ends OK), define their accompanying ON statement with pgmstep value ANYSTEP and code value OK.
(For more information, see parameters ON and DO SYSOUT in this section of the manual.) The interrelationship between multiple sysout operations (via statements SYSOUT and DO SYSOUT) is described below in Multiple Sysout Operations. Sysout Handling Operations Which sysouts are affected by sysout handling operations depends on whether the sysouts are under JES2 or JES3, as follows: Under JES2: Operations are performed on all of the jobs held sysouts (or held portions of sysouts) unless otherwise restricted to a specific FROM class via subparameter FROM. Operations are performed only on the jobs sysouts in the CONTROL-M held class (specified in CONTROL-M installation parameter HLDCLAS) unless further restricted to a specific FROM class via subparameter FROM.
Under JES3:
Sysout handling operations are listed below:
Copying sysouts to a file (OPT=F) The jobs sysouts are copied (not moved) to the file specified in the data subparameter. The file name specified in the data subparameter can contain AutoEdit System variables. (No other AutoEdit terms can be specified.) If the AutoEdit variables cannot be resolved, the sysout is not copied. CONTROL-M allocates the file with DISP=(NEW,CATLG,DELETE) using the unit and space attributes specified in the CONTROL-M installation parameters. Sysouts can be archived by copying them to a file. However, to reduce overhead, this method is recommended only for small sysouts.
3 177
SYSOUT
Deleting sysouts (OPT=D) The jobs sysouts are deleted (purged) from the output queue. Note This operation works on all sysouts under JES2 or JES3 (regardless of held status/ class) unless otherwise restricted by the FROM subparameter.
Releasing sysouts (OPT=R) The jobs sysouts are released for printing. Changing the class of sysouts (OPT=C) The jobs sysouts are changed to the output class specified in the data subparameter. Ensure that you specify a meaningful target output class. The following points should be noted: Changing a sysout class to a released class changes the class name. It does not, however, release the sysout because the sysout attributes do not change (due to JES logic). To ensure that the sysout will be released, use DO SYSOUT statements to release the sysout after changing its class. For example,
DO SYSOUT OPT C PRM R FRM A DO SYSOUT OPT R PRM FRM A
Changing a sysout class to a dummy class does not purge the sysout because the sysout attributes do not change (due to JES logic). To save a jobs original MSGCLASS and to restore it at output processing time, specify a data value of *. The sysouts are changed to the jobs original class.
Moving sysouts to a new destination (OPT=N) The jobs sysouts are moved to the output destination specified in the data subparameter. Ensure that you specify a meaningful target output destination.
Multiple Sysout Operations If multiple SYSOUT/DO SYSOUT operations are not specified for the same FROM class, the order in which the operations are performed is not significant. However, if different SYSOUT/DO SYSOUT operations affect the same FROM class, or if multiple operations are specified without a FROM class, the order and method of implementation is significant. CONTROL-M merges different operations for the same FROM class into a combined instruction to JES. Likewise, CONTROL-M merges different operations without a FROM class into a combined instruction to JES. Operations without a specified FROM class treat the entire held sysout as a whole unit, and are therefore not merged with sysout handling requests for a specific FROM class. JES does not necessarily process multiple sysout-handling instructions in the order they are issued by CONTROL-M. Therefore, the processing results can vary if the merged instructions to JES include both FROM=a specified class and FROM=blank.
3 178
SYSOUT
It is highly recommended that a job scheduling definition not contain both FROM class and no FROM class sysout handling instructions which will become operational under the same situation(s). When CONTROL-M merges a set of operations into a combined instruction, some operations override or cancel other operations, and some operations are performed along with other operations. This is described below. Operation Merging and Performance CONTROL-M performs all copy to file operations (option F) first. After performing all copy to file operations, CONTROL-M merges all operations performed on a specific FROM class. After merging operations on specific FROM classes, CONTROL-M merges the operations performed on the sysout as a whole (i.e., subparameter FROM=blank). CONTROL-M then passes the merged sets of instructions to JES for processing. Generally, DO SYSOUT operations override, or are performed along with, SYSOUT statements. The following chart and the accompanying numbered explanations indicate the result of merging SYSOUT and DO SYSOUT statements.
3 179
SYSOUT
The order of precedence in which CONTROL-M processes/merges operations is as follows: 1. SYSOUT=F and DO SYSOUT=F Copy to file operations are performed first (directly by CONTROL-M) for both SYSOUT and DO SYSOUT statements (whether or not FROM class is specified). Then, other operations are performed. 2. DO SYSOUT = D (Delete) This operation supersedes all SYSOUT operations (except copy to file operations described above). Superseded operations are ignored (i.e., not performed). 3. DO SYSOUT = R, C, or N, accompanied by a SYSOUT D (Delete) request The DO SYSOUT statement is performed, and the SYSOUT delete request is ignored. 4. SYSOUT/DO SYSOUT combinations of R, C and N In general, combinations of R, C, and N requests are merged (i.e., are all performed). The exceptional cases are described below: For DO SYSOUT = R (Release job output) accompanied by a SYSOUT C (Change class) request: Perform just the DO SYSOUT R request and ignore the SYSOUT C request. For C (Change class) requests from both a SYSOUT and a DO SYSOUT statement: Perform just the DO SYSOUT request and ignore the SYSOUT request. For N (New Destination) requests from both a SYSOUT and a DO SYSOUT statement: Perform just the DO SYSOUT request and ignore the SYSOUT request. SYSOUT / DO SYSOUT Differences SYSOUT and DO SYSOUT statements have the following differences:
The SYSOUT statement is applied only if the job ends OK. DO SYSOUT statements are associated with accompanying ON statements and are applied only if the accompanying ON step/code criteria are satisfied. A SYSOUT statement is displayed in each job scheduling definition. A DO SYSOUT statement is not displayed unless requested. To request a DO SYSOUT statement, type SYSOUT in an empty DO field and press <ENTER>. Only one SYSOUT statement can be defined in the job scheduling definition. An unlimited number of DO SYSOUT statements can be requested. The SYSOUT OP subparameter is equivalent to the DO SYSOUT OPT subparameter. The SYSOUT data subparameter is equivalent to the DO SYSOUT PRM subparameter. The SYSOUT FROM subparameter is equivalent to the DO subparameter. SYSOUT FRM
3 180
SYSOUT
Example 1
Delete the sysout after the job has finished executing OK:
MEMNAME DAYS SYSOUT EBMANT1 1,15 OPT D (C,D,F,N,R)
Example 2
If the job finishes OK, reroute the sysout to printing class A.
JOB: EBDMANT2 LIB CTM.PROD.SCHEDULE TABLE: EBDPROD COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ DOCMEM EBDMANT2 DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 04 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE PIPE TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM =========================================================================== OUT AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP SYSOUT OP C (C,D,F,N,R) A FROM RERUN - MAXRERUN RERUNMEM INTERVAL USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
3 181
TASKTYPE
TASKTYPE
Type of task.
Format
Mandatory. Valid TASKTYPE values: JOB CYC STC CST EMR ECJ EST ECS WRN Batch job. Default Cyclic job Started task (STC) Cyclic STC Emergency job Emergency cyclic job Emergency STC Emergency cyclic STC Warning message
General Information
The job scheduling definition can belong to one of three basic types of tasks:
Job Started Task Warning Message(s)
Jobs and started tasks can be normal (i.e., submitted/activated once) or cyclic. Furthermore, it is possible to define emergency versions of jobs and started tasks (normal and/or cyclic). Accordingly, the three basic types of tasks are indicated by the following TASKTYPE values: Job: JOB, CYC, EMR, ECJ
3 182
TASKTYPE
Started Task: Warning:
STC, CST, EST, ECS WRN
Jobs and Started Tasks A regular job is submitted to the JES input queue for execution; it then waits in the queue like any job submitted under the OS/MVS Operating System. After the job finishes executing, CONTROL-M analyzes the results and decides what actions to take. The job will not be submitted again unless the RERUN statement is performed. (For additional information, see parameter MAXRERUN.) Started tasks differ from jobs in that they are not submitted to the queue; instead, they are invoked by an operator START command issued by CONTROL-M. (For details on passing parameters to started tasks, see parameter MEMLIB in this section.) Note PREVENT-NCT2 = Y cannot be specified for started tasks (STCs).
A cyclic job or a cyclic started task is recycled for additional possible executions after CONTROL-M has analyzed its execution results. The job or started task will execute again only after the number of minutes specified in parameter INTERVAL has passed since the last execution and the rest of its runtime scheduling criteria have been satisfied. Note It is highly recommended that a cyclic job delete the prerequisite conditions that triggered its operation. Otherwise the job might continually be resubmitted.
If a cyclic job is executing at the time the New Day procedure is run, the New Day procedure changes the job to a non-cyclic job and handles the job accordingly. Use of the cyclic option excludes the use of RERUN and DO RERUN parameters. (For additional information, see parameter MAXRERUN.) Emergency Jobs/Started Tasks Note Emergency jobs/started tasks are supported for backward compatibility, but we recommend redefining them as regular jobs/started tasks activated by DO FORCEJOB statements. CONTROL-R users can also use statement DOIFRERUN. Statements DO FORCEJOB and DO IFRERUN are described elsewhere in this section.
An emergency job or emergency started task can be used to overcome any irregularities in normal execution. The job remains in the Active Jobs file, waiting to be scheduled, until all regular jobs of the same GROUP finish executing OK and are checked by CONTROL-M. Then, when the emergency job is no longer needed, the job is automatically removed from the Active Jobs file. (For additional information, see parameter MAXWAIT.) Note It is highly recommended that parameter GROUP be specified if you define emergency jobs. If it is not specified, the job may stay indefinitely in the Active Jobs file.
Emergency jobs can be filtered out of the job display in the Status screen and filtered out of reports.
3 183
TASKTYPE
Warning Messages Note Utility IOANOTE described in Section 6 of this manual can also be used to issue warning messages. It is recommended that utility IOANOTE be used in place of this tasktype wherever possible.
For tasktype WRN, a warning message(s) is sent to the IOA Log file when the job is ordered. The message(s) is taken from the member specified in parameter MEMNAME. Note A job defined with tasktype WRN is not placed in the Active Jobs file.
Example1
Submit a regular job:
MEMNAME GNRLDR01 TASKTYPE JOB
Example 2
Start a started task:
MEMNAME CICSPROD TASKTYPE STC
Example 3
Start an emergency job:
MEMNAME RESTORE2 TASKTYPE EMR
3 184
TASKTYPE
Example 4
Job OPERCOMP is a regular job.
3 185
TIME
TIME
Time limits (FROM, UNTIL) for submitting the job.
FR OM U N TIL
Format
Optional. TIME consists of two subparameters: FROM and UNTIL. Either or both subparameters can be specified. The FROM and UNTIL fields can contain valid times in the format hhmm (where hh is hour and mm is minute). Character > can be specified in field UNTIL.
General Information
FROM and UNTIL times define a window of opportunity for job submission. A job can only be submitted during the specified submission window. If either a FROM or an UNTIL value is missing (i.e., not specified), the New Day Processing time is used as the default for the missing value. Therefore:
To create a submission window from a particular time until time of New Day processing, specify the desired From time in field FROM and leave field UNTIL blank. Example
FROM 22:00 UNTIL (blank)
creates a submission window from 10:00 p.m. until New Day Processing time.
To create a submission window from time of New Day processing until a particular time, specify the desired Until time in field UNTIL and leave field FROM blank. Example
FROM (blank) UNTIL 13:00
creates a submission window from New Day processing until 1:00 p.m. When both a FROM and an UNTIL value are specified, the relationship of New Day Processing time to these values (on a physical clock) determines the submission window. The logic is as follows:
3 186
TIME
If, when you move forward on the physical clock from the New Day Processing time, you arrive at the FROM time before you arrive at the UNTIL time, it means that New Day processing does not fall between the FROM time and UNTIL time. In this case, the submission window runs from the FROM time to the UNTIL time, regardless of when the job was ordered. Example1 Assume a New Day Processing time of 8:00 a.m.
FROM 14:00 UNTIL 22:00
creates a submission window from 2:00 p.m. until 10:00 p.m. (a period of 8 hours) Example2 Assume a New Day Processing time of 10:00 p.m.
creates a submission window from 11:00 p.m. until 5:00 a.m. (a period of 6 hours) Example3 Assume a New Day Processing time of 10:30 p.m.
creates a submission window from 11:00 p.m. until 10:00 p.m. (a period of 23 hours)
If, when you move forward on the physical clock from the New Day Processing time, you arrive at the UNTIL time before you arrive at the FROM time, it means that New Day processing falls between the FROM time and UNTIL time. Batch jobs are frequently scheduled for submission from night until the morning. Therefore, when New Day Processing time intervenes between the FROM time and the UNTIL time, it is likely that, following New Day Processing, the site still wants the job to be submitted up until the UNTIL time (without first waiting for the FROM time of the New day). For this reason, if New Day Processing comes between the FROM time and the UNTIL time, then regardless of when the job was ordered, the job is eligible for submission from both: The FROM time until New Day Processing time. New Day Processing time until the UNTIL time.
The actual effect is that the submission window consists of all times except the interval from the UNTIL time until the FROM time. Example Assume a New Day Processing time of 4:00 a.m.
creates a submission window from 11:00 p.m. until 4:00 a.m. and from 4:00 a.m. until 6:00 a.m., giving a net submission window from 11:00 p.m. until 6:00 a.m. (The job cannot be submitted from 6:00 a.m. until 11:00 p.m.)
3 187
TIME
Character > in the UNTIL field indicates that CONTROL-M should attempt to submit the job at the FROM time if specified, and if this is not possible, CONTROL-M should submit the job as soon afterwards as possible, even at a later date (unless the MAXWAIT period has expired). Example Assume a New Day Processing time of 8:00 a.m.
FROM 22:00 UNTIL >
creates a submission window that begins at 10:00 p.m. If the job has not been submitted by the end of day, it can be submitted at any time from the beginning of the next day. The FROM parameter is ignored when a job is rerun/restarted on a subsequent day. Specifying the same time in both the FROM and the UNTIL fields has the same impact as specifying no value in both fields.
Example
Submit the job after midnight:
JOB: OPGENBKP LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+* MEMNAME OPGENBKP MEMLIB GENERAL OWNER SYS1 TASKTYPE JOB PREVENT-NCT2 APPL EBD GROUP BACKUP DESC OPER GENERAL BACKUP OVERLIB SET VAR CTB STEP AT NAME TYPE DOCMEM OPGENBKP DOCLIB CTM.PROD.DOC =========================================================================== DAYS DCAL AND/OR WDAYS WCAL MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y DATES CONFCAL SHIFT RETRO Y MAXWAIT 00 D-CAT MINIMUM PDS =========================================================================== IN CONTROL RESOURCE PIPE TIME: FROM 0000 UNTIL PRIORITY DUE OUT CONFIRM USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
In this example, if the start time of the new workday is 6:00 a.m., this job can only be submitted between the hours of midnight and 6:00 a.m.
3 188
WDAYS
WDAYS
Days of the week on which the job should be scheduled. See also DAYS and CONFCAL.
Format
Optional. Parameter WDAYS specifies days of the week on which jobs should be scheduled, provided other basic scheduling criteria are met. Values for WDAYS can be specified alone, or they can be specified together with a calendar specified in subparameter WCAL. WDAYS/WCAL can also be specified together with DAYS/DCAL (described under DAYS earlier in this section of the manual). WDAYS subparameters are described below: WDAYS Days of each week in the month on which to schedule a job. (The months in which to order jobs are specified in parameter MONTHS.) Various formats (described later) can be used to specify WDAYS (e.g., 2 means the second day of the week, L2 means the day before the last day of the week). Note At time of installation, the IOA administrator selects either Sunday or Monday as the first day of the week. Your IOA administrator can tell you whether the week begins on Sunday or Monday at your site. The first six days of the week are coded 1 through 6. The last day of the week is coded 0 (zero). All examples in this section assume Monday is the first day of the week. In these examples, Monday = 1, Tuesday = 2, ..., Saturday = 6, and Sunday = 0. WCAL Name of a calendar containing a predefined set of dates (referred to as working days) on which a job should be scheduled. A specified value must be either a valid member name of 1-8 characters, or an * to indicate that the calendar specified in parameter CONFCAL should be used for scheduling. See IOA Calendar Facility in Section 2 of this manual for more information about how to define, use and modify calendars.
3 189
WDAYS
Note
A calendar specified in WCAL does not have to exist when defining parameter WDAYS. However, it must exist when the job to be ordered. Existing job definitions from previous releases which specify WDAYS values and a DATEMEM calendar will automatically have the calendar name placed in the WCAL field when accessed by this CONTROL-M release.
Assuming all other basic scheduling criteria are met:
When WDAYS are specified without WCAL, the job is scheduled on the specified days of the week. When WCAL is specified without WDAYS, the job is scheduled on the working days marked in the WCAL calendar. When WDAYS and WCAL are both specified, scheduling depends on the combination of working days defined in the calendar and the values/format of parameter WDAYS (described below). When both DAYS and WDAYS criteria are specified, scheduling depends on the connecting AND/OR value specified. (See subparameter AND/OR in parameter DAYS for more information.)
Valid Formats for WDAYS

Valid formats for parameter WDAYS, and how they relate to WCAL, are described below. In the following non-periodic scheduling formats: n is an integer from 1 to 6 or 0 (zero), where 1 = the first day of the week (Sunday or Monday, depending on the standard at your site) and 0 = the last day of the week (Saturday or Sunday).
Multiple values can be expressed (separated by commas) in any order. WCAL should not contain the name of a periodic calendar. All days of the week. If ALL is specified, other WDAYS values cannot be specified with it. If a WCAL calendar is not defined, schedule the job on all days in the week. If a WCAL calendar is defined, schedule the job only on the working days indicated in the calendar.
ALL
n,...
Specific days of the week. If a WCAL calendar is not defined, schedule the job on the specified days. If a WCAL calendar is defined, schedule the job only when a day is defined as a working day both in the WDAYS parameter and in the WCAL calendar.
3 190
WDAYS
+n,... n,...
Days of the week in addition to the working days specified in the WCAL calendar. WCAL is mandatory. Days of the week on which a job cannot be ordered. These values take precedence over all other Basic Scheduling parameters (i.e., the job is not ordered, even if schedulable according to WCAL calendar working days, DAYS, or other criteria). WCAL is mandatory. Order the job on the indicated day if it is a working day in the WCAL calendar; otherwise, order the job on the next working day (within the 5 next seven days ) that is not negated by a n value in the parameter. This format is frequently used for holiday handling. WCAL is mandatory. Order the job on the indicated day if it is a working day in the WCAL calendar; otherwise, order the job on the last previous working day 4 (within the preceding seven days ) that is not negated by a n value in the parameter. This format is frequently used for holiday handling. WCAL is mandatory. Order the job on the nth working day from the beginning of the week. WCAL is mandatory. Order the job on all working days except the nth working day from the beginning of the week. WCAL is mandatory. Order the job on the nth working day counting from the end of the week. WCAL is mandatory. Order the job on all working days except the nth working day counting backward from the end of the week. WCAL is mandatory. (Where m = 16). If WCAL is defined, order the job on the nth working day of the mth week of the month. If WCAL is not defined, order the job on the mth appearance of the nth day of the week during the month. A maximum of eleven DnWm values can be specified. WCAL is optional.
>n,...
<n,...
Dn,... Dn,... Ln,... Ln,... DnWm,...
In the following periodic scheduling formats:
n is any integer from 0 to 6, and i is any valid period identifier. WDAYS periodic identifiers are counted on a week by week basis. Calculations do not cross week boundaries (unlike DAYS periodic identifiers which can cross month boundaries). The name of a periodic calendar must be specified in WCAL. Refer to the IOA Calendar facility in Section 2 for details concerning periodic calendars. Order the job on the nth day of period i in each week, from the beginning of the week. An * can be specified as the i value to represent all periods.
DnPi,...
If none of those seven days is a working day, the job is not ordered.
3 191
WDAYS
DnPi,...
Order the job on all days except the nth day of period i in each week, from the beginning of the week. An * can be specified as the i value to represent all periods. Order the job on the nth day of period i in each week, counting backward from the last periodic day of the week. An * can be specified as the i value to represent all periods. Order the job on all days in period i except the nth day of period i in each week, counting from the last periodic day of the week. An * can be specified as the i value to represent all periods.
LnPi,...
LnPi,...
A maximum of eight periodic values can be specified in any desired order.
General Information
Negative values take precedence over positive values when determining whether or not a job will be scheduled on a certain date. If a negative value (i.e., format n, Dn, Ln, DnPi, or LnPi) in either the DAYS or WDAYS field prevents a job from being scheduled on a date, the job will not be scheduled on that date even if a positive value (e.g., Ln) would otherwise result in the job being scheduled on that date. If periodic and non-periodic values are mixed when specifying parameter WDAYS, processing will depend on the calendar type specified in parameter WCAL:
If a non-periodic calendar is specified in WCAL, only non-periodic values in parameter WDAYS are processed; periodic values are ignored. In this case, negative periodic values (i.e., DnPi, LnPi) are also ignored and do not supersede other values. If a periodic calendar is specified in WCAL, all periodic values in parameter WDAYS are processed; and all non-periodic values are ignored.
Parameter MONTHS is ignored when periodic values are specified in parameter WDAYS. Parameter WDAYS cannot be used with parameters PDS and MINIMUM. When Ln and/or Dn values are specified in a week which overlaps two months, the MONTHS value of the earlier month determines whether or not Dn or Ln values are applied in the week:
If the first day of the week falls in a month with a MONTHS value of Y, all Dn and Ln values in that week are applied, even those falling in the next/previous month when that month has a MONTHS value of N. If the first day of the week falls in a month with a MONTHS value of N, no Dn or Ln values in that week are applied (not even if those falling in the next/previous month when that month has a MONTHS value of Y).
3 192
WDAYS
Examples
The examples in this section are based on the following assumptions:
The current month is August 1998. Working days are defined in calendar WORKDAYS which contains the following working days (indicated by Y) for August 1998:
---S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Periodic calendar PERIDAYS contains the following periodic definition for August 1998. These examples assume that all other days of this calendar are blank.
---S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 B C A A B B C A A B B C A A B B C A A B B
Start of the week is defined as Monday. Weeks start on the following dates in August 1998: 3rd, 10th, 17th, 24th, and 31st.
At the end of each example, asterisks in a August 1998 calendar indicate the days on which the job is scheduled.
Example 1
Schedule the job on every Sunday and Monday.
WDAYS 0,1

* *
* *
* *
* *
* *
Example 2
Schedule the job on all working days and on all Saturdays.
WDAYS WCAL +6 WORKDAYS

* * * * * *
* * * * * *
* * * * * *
* * * * * *
3 193
WDAYS
Example 3
Schedule the job on Sunday, if it is a working day. If Sunday is not a working day, schedule the job on the first preceding working day that is not a Friday.
WDAYS WCAL -5,<0 WORKDAYS

Example 4
Schedule the job on Monday of the 1st week.
WDAYS D1W1

Example 5
Schedule the job on all working days except Mondays and Fridays.
WDAYS WCAL -D1,-L1 WORKDAYS

* * *
* * *
* * *
* * *
Example 6
Each week, schedule the job on the 1st day of period A, and on all days, except the second day of period B, in that week.
WDAYS WCAL D1PA,-D2PB PERIDAYS

3 194
WDAYS
Example 7
Schedule the job on each Monday and on the 1st day of the month.
DAYS AND/OR WDAYS 1 OR 1

Example 8
Schedule the job on the 3rd day of the month provided it is a Monday.
DAYS AND/OR WDAYS 3 AND 1

Example 9
Schedule the job on the last Monday of the month.
DAYS AND/OR WDAYS L1,L2,L3,L4,L5,L6,L7 AND 1

Example 10
Schedule the job on the 1st, 7th and 15th day of the month if they are both Saturdays and working days. If the day of the month (1st, 7th, 15th) is not a Saturday, do not schedule the job. If the day of the month is a Saturday, but it is not a working day, schedule the job on the next working day.
DAYS AND/OR WDAYS CONFCAL SHIFT 1,7,15 AND 6 WORKDAYS >

3 195
WDAYS
This page intentionally left blank.
3 196
Section 4: CONTROL-M Event Manager (CMEM)

General ...........................................................................................................................................4-1 Types of Events Managed by CMEM ........................................................................................4-1 Types of Actions Which CMEM Can Perform...........................................................................4-2 CMEM Rule Ordering, Triggering and Deactivation ...............................................................4-2 CMEM AutoEdit Variables ........................................................................................................4-3 On Spool Jobs..............................................................................................................................4-3 Creating On Spool Jobs.........................................................................................................4-4 Job On Spool ..........................................................................................................................4-4 CMEM Rule ...........................................................................................................................4-4 Job Scheduling Definition .....................................................................................................4-5 Handling On Spool Jobs........................................................................................................4-5 On Spool Job Definition Considerations ..............................................................................4-6 JCL Management Considerations ........................................................................................4-6 CMEM Support for FTP .............................................................................................................4-7 Rule Parameters Summary....................................................................................................4-8 Event Selection Parameters.......................................................................................................4-9 General Parameters ...................................................................................................................4-9 Action Parameters ......................................................................................................................4-9 Parameter Descriptions .......................................................................................................... 4-10 DESCRIPTION.........................................................................................................................4-11 DO statement............................................................................................................................4-13 DO COND .................................................................................................................................4-14 DO FORCEJOB ........................................................................................................................4-17 DO RULE ..................................................................................................................................4-21 DO SHOUT ...............................................................................................................................4-24 DO STOPJOB ...........................................................................................................................4-27 GROUP......................................................................................................................................4-29 MODE........................................................................................................................................4-31 ON statement............................................................................................................................4-33 ON DSNEVENT .......................................................................................................................4-35 ON JOBARRIV .........................................................................................................................4-40 ON JOBEND.............................................................................................................................4-42 ON STEP...................................................................................................................................4-44 OWNER.....................................................................................................................................4-48 RUNTSEC.................................................................................................................................4-50
CONTROL-M Event Manager: General Types of Events Managed by CMEM
General
The CONTROL-M Event Manager (CMEM) facility enables CONTROL-M to perform specified actions in response to external events. External events are events in the system which occur outside CONTROL-Ms direct control (e.g., submission of a job not under the control of the CONTROL-M monitor). The CMEM facility is an optional facility based on a monitor and a subsystem. The CMEM facility utilizes sets of user-defined rules that specify event(s) to monitor and actions to perform if a specified event occurs. These rules are defined online via the CMEM Rule Definition facility. Multiple rules can be defined in a table (member) in a standard partitioned dataset (library). Related rules are usually defined in the same table. Multiple tables can be defined in a library, and multiple CMEM rule libraries can be defined. Note Prior to CONTROL-M Release 5.0.0, CMEM had no online Rule Definition facility. Instead, all CMEM rules were collected into one CMEM table, and each rule was referred to as a CMEM event. If your site utilized a CMEM table prior to CONTROL-M Release 5.0.0, your IOA administrator can convert the table to rule tables (members) via utility CTM2RUL. This utility is described in Section 3 of the IOA Installation Guide.
Types of Events Managed by CMEM

The CMEM facility handles the following events, which can be specified in ON statements in the rule: DSNEVENT Dataset disposition (e.g.,cataloged, deleted or kept) during step termination or dynamic deallocation, or the occurrence of a NOT CATLGD 2 event (when a dataset name is created in a job step but not cataloged because its name already exists in the MVS catalog). Specified in an ON DSNEVENT statement in the rule. Arrival of a job on the JES spool from any source. Examples: Jobs submitted by a TSO user or by CICS, or jobs received over an NJE network. Specified in an ON JOBARRIV statement in the rule. JOBEND STEP Completion of a job regardless of its source. Specified in an ON JOBEND statement in the rule. Termination of a job step. Specified in an ON STEP statement in the rule.
JOBARRIV
41
CONTROL-M Event Manager: General Types of Actions Which CMEM Can Perform
Types of Actions Which CMEM Can Perform

Any combination of the following actions can be performed when the specified event occurs. They are specified in DO statements in the rule: Add/delete a prerequisite condition Prerequisite conditions can be added to or deleted from the IOA Conditions/Resources file. This can trigger the submission of jobs in the Active Jobs file. Specified in a DO COND statement in the rule.
Force a job or table A CONTROL-M scheduling table or individual job can be forced (i.e., ordered to the Active Jobs file regardless of its basic scheduling criteria). Specified in a DO FORCEJOB statement in the rule. Jobs can be forced for one of the following reasons: To start a new process in CONTROL-M (i.e., new job submission). To enable CONTROL-M to assume full control of an externally submitted job which triggers the event. These jobs are referred to as On Spool jobs. See On Spool Jobs later in this section.
Stop the job in which the event occurs At the end of the current job step, terminate the job in which the event occurred. Specified in a DO STOPJOB statement in the rule.
The following actions can be defined if CONTROL-O is installed: Invoke a CONTROL-O rule CONTROL-O rules can be invoked within the current rule. Specified in a DO RULE statement in the rule. Send a message Messages can be sent to specified locations via the CONTROL-O Shout facility. Specified in a DO SHOUT statement in the rule.
CMEM Rule Ordering, Triggering and Deactivation

CMEM tables are usually ordered (loaded to memory) when CMEM is started. They can also be refreshed/loaded by an operator command, or manually via the FORCE option in the CMEM Table List screen. A CMEM rule in memory is triggered (i.e., all its DO statements are performed) by the occurrence of the event(s) specified in the rules ON statement(s). More than one rule can be triggered by the occurrence of an event. An event triggers each rule whose ON statement matches the event. Generally, all actions from all triggered rules are performed. (The one exception occurs when multiple rules are triggered by the same job arrival event and each of the triggered rules contains DO FORCEJOB statements. In this case, the DO FORCEJOB statements of the first triggered rule are performed, but the DO FORCEJOB statements of the other rules triggered by the event are not performed. See On Spool Jobs later in this section.) CMEM rules remain activated (i.e., in memory) until they are overridden by the reloading of the rule table or deleted by an operator command.
42
CONTROL-M Event Manager: General CMEM AutoEdit Variables
CMEM AutoEdit Variables

The CMEM facility supports its own set of AutoEdit variables. No other AutoEdit variables can be used by the CMEM facility. Furthermore, in CONTROL-M, these variables can only be specified in CMEM rules, not in job scheduling definitions or JCL. CMEM AutoEdit variables are resolved upon triggering of the rule. Available CMEM AutoEdit variables are: %%$Dn nth qualifier of the dataset name. (For example, if the dataset name is AAA.BBB.CCC, %%$D2 resolves to BBB.) Valid only for rules containing an ON DSNEVENT statement. Name of the dataset handled by the rule. Valid only for rules containing an ON DSNEVENT statement. Disposition of the dataset handled by the rule. Valid only for rules containing an ON DSNEVENT statement. Possible values are: C Cataloged D Deleted K Kept N NOT CATLG2 R Retained S Scratched
%%$DSN %%$DSNDISP
U Uncataloged %%$JNAME %%$SABEND %%$STEPCC %%$UABEND Job name. Valid in rules for all types of events. System abend code of the step whose termination triggered the rule. Completion code of the step whose termination triggered the rule. User abend code of the step whose termination triggered the rule.
On Spool Jobs
On Spool jobs are jobs or started tasks which are submitted externally to CONTROL-M (e.g., jobs submitted by TSO users or CICS, or jobs received over the NJE network) but which are brought under the control of the CONTROL-M monitor via a CMEM rule. The CMEM rule which causes a job to be an On Spool job (i.e., which brings the external job under the control of the CONTROL-M monitor) must be an ON JOBARRIV rule with a DO FORCEJOB statement. To inform CONTROL-M that this is an On Spool job and not a regular FORCEJOB request, the job scheduling definition forced by the DO FORCEJOB must match the arriving job (as described below). CONTROL-M controls the entire life cycle of the job, from determining when to execute the job to performing job post-processing, according to the forced job scheduling definition.
43
CONTROL-M Event Manager: General On Spool Jobs
CONTROL-M processes On Spool jobs slightly differently than it processes regular jobs. CONTROL-M does not submit the job because the job has already been submitted. Instead, CONTROL-M releases the job (if held) when the runtime scheduling criteria are met. Once the job starts execution (whether or not the job previously required releasing), it is controlled by CONTROL-M in the same way that CONTROL-M controls regular jobs. CONTROL-M waits for the job to finish, reads its sysout, and performs all post-processing actions defined in the job scheduling definition.
Creating On Spool Jobs

The following components are necessary to create On Spool jobs: 1. Job on spool 2. CMEM rule 3. Job scheduling definition Below is a detailed explanation of what should be defined for each of the above components to create an On Spool job.
Job On Spool
The job should have the following characteristics:
The job should be submitted with TYPRUN=HOLD to delay its execution and permit CONTROL-M to determine when to run the job. The MSGCLASS sysout of the job: For JES3 users For JES2 users Must be equal to the CONTROL-M SYSOUT held class. Can be any held SYSOUT class.
This enables CONTROL-M to read the jobs sysout and perform post-processing according to the job scheduling definition.
CMEM Rule
The CMEM rule definition must contain the following:
ON JOBARRIV statement The job name specified in the ON JOBARRIV statement in this rule must match the name of the job to be monitored. It can be a full job name, or it can be a mask if a group of jobs should be monitored. See ON JOBARRIV later in this section.
DO FORCEJOB statement The first DO FORCEJOB statement in the rule must force a matching job scheduling definition (described immediately below). See also DO FORCEJOB later in this section.
44
Job Scheduling Definition

The job scheduling definition should have the following characteristics:
The job scheduling definition must be forced by the first DO FORCEJOB statement in the CMEM rule. The MEMNAME value in the job scheduling definition must match the name of the external job. A mask can be specified in the MEMNAME field if the same job scheduling definition is used for more than one job. Appropriate runtime scheduling criteria for the job must be defined in the job scheduling definition. This enables CONTROL-M to control the execution of the job (i.e., when the job should be run). Desired post-processing actions must be defined in the job scheduling definition.
Handling On Spool Jobs

On Spool jobs are handled as follows:
When the job arrival event occurs, CONTROL-M forces the requested table/job. If the MEMNAME value in the requested table/job does not match the name of the arriving job, the table/job is forced and processed regularly by CONTROL-M (a job is submitted when its runtime scheduling criteria are met, etc.). If the MEMNAME value in the requested table/job matches the name of the arriving job, the job becomes an On Spool job and CONTROL-M performs the following actions: Replaces the MEMNAME mask (if a mask was specified in MEMNAME) with the name of the arriving job. Assigns the job ID of the job that triggered the event to the forced job. Forces the job.
The forced job appears in the Status screen with status WAIT SCHEDULE ON SPOOL.
CONTROL-M starts processing the forced job when all runtime scheduling criteria defined in the job scheduling definition are satisfied. If there are no runtime scheduling criteria in the job scheduling definition, CONTROL-M starts processing the job immediately. CONTROL-M looks for the job in the spool (to release it, if required). If the external job is waiting for execution in HELD state (i.e., if the job arrives on spool with TYPRUN=HOLD), CONTROL-M releases it for execution. Otherwise, CONTROL-M verifies that the job is still in the spool (waiting for execution, executing or ended) before deciding to perform post-processing.
CONTROL-M waits for the job to finish execution, reads its SYSOUT, analyzes the execution results and performs all the post-processing actions defined in the job scheduling definition.
45
On Spool Job Definition Considerations

Job Forcing Considerations Only one On Spool job can be created in response to a job arrival event. However, in several cases, multiple DO FORCEJOB actions might match the arriving job. Each of these cases and the job forcing logic applied to them (to prevent multiple On Spool processes for the same external job) are described below.
The job arrival rule contains multiple DO FORCEJOB requests. (Each might match the arriving job.) In this case, job forcing logic is as follows: The On Spool process (the match between the external job name and MEMNAME) is performed for the first DO FORCEJOB in the first matching job arrival rule only: If a match is found, the job will be an On Spool job. If a match is not found, the job will not be an On Spool job, even if subsequent DO FORCEJOB actions might match.
In either case, all subsequent DO FORCEJOB statements in the same rule (if they exist) are handled normally (i.e., not as forcing On Spool jobs).
The DO FORCEJOB forces a table in which more than one MEMNAME matches the arriving job. In this case, job forcing logic is as follows: If a table containing more than one job is forced (by the first DO FORCEJOB statement in the rule, as described above), the first matching job causes the job to be an On Spool job. All the other jobs in the table are forced as regular CONTROL-M jobs, even if they match the job name of the external job.
Multiple job arrival rules are triggered by the same job arrival event, and each rule contains one or more DO FORCEJOB statements which might match the arriving job. In this case, job forcing logic is as follows: Only the DO FORCEJOB statements from the first triggered rule are executed (as described above). DO FORCEJOB from all other triggered job arrival rules are ignored.
JCL Management Considerations

When defining JCL, the following issues should be considered:
Any attempt to rerun the job (i.e., as a cyclic job, by a DO RERUN statement, or by a manual rerun request) might fail if the JCL of the job is not found in the library specified in the MEMLIB parameter of the job scheduling definition. If the job is not submitted with TYPRUN=HOLD, CONTROL-M cannot determine when the job will run, even if runtime scheduling criteria are defined. In this case, the job might start executing before all the runtime scheduling criteria are satisfied. Post-processing, however, is not performed by CONTROL-M until the runtime scheduling criteria are satisfied. The JCL of the On Spool job cannot contain AutoEdit statements and SETVAR statements in the job scheduling definition are ignored. This is because the job is not submitted by CONTROL-M.
46
CONTROL-M Event Manager: General CMEM Support for FTP
CMEM Support for FTP

CMEM actions can be triggered by the transfer of files by FTP products. To enable CMEM rules to be triggered by such file transfers, perform the following steps: 1. Insert MSGLEVEL=(1,1) in the started task (STC) of the FTP product by doing one of the following:
Customize member JESxPARM in the SYS1.PARMLIB library. Modify the job statement in the PROCLIB library member that contains the procedure JCL for the FTP started task (STC).
2. Start the CMEM monitor with at least one rule that refers to the STC of the FTP product. This rule can be a dummy rule that forces CMEM to monitor the FTPs started task. 3. Initialize the started task of the FTP product. 4. Modify existing rules and/or order new rules. Rules which have been modified or ordered before a file reaches the FTP server will be applied to files subsequently transferred by the FTP product. Note CMEM triggers rules when the requirements of an ON DSNEVENT statement are satisfied. If an FTP product fails to transmit a dataset and issues an error message about the failure, CMEM cannot react to the error message. However, CONTROL-O rules can be used to react to FTP product messages.
47
CONTROL-M Event Manager: Rule Parameters Summary
Rule Parameters Summary

RL: JOBNAM1 LIB CTM.PROD.RULES TABLE: CMEMRULE COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON JOBARRIV = JOBNAM1 JTYPE SMFID SYSTEM And/Or/Not OWNER CTMCTLM GROUP MODE PROD RUNTSEC NONE DESCRIPTION CONVERSION: ON JOB JOBNAM1 ARRIVAL FORCEJOB DESCRIPTION =========================================================================== DO FORCEJOB = TABLE TABLE1 JOB DATE ODAT LIBRARY CTM.PROD.SCHEDULE DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
The parameters of the CMEM Rule Definition screen are divided into the following categories:
Event Selection Parameters General Parameters Action Parameters
A brief summary of the parameters in each category is provided on the following pages. This is followed by a detailed description of each parameter in alphabetical order.
48
CONTROL-M Event Manager: Rule Parameters Summary
Event Selection Parameters

The following parameters identify the events which trigger the rule. ON statement Event criteria which must be satisfied for the rule to be triggered. Subparameters may be displayed. Valid ON statements: ON DSNEVENT ON JOBARRIV ON JOBEND ON STEP Name (or mask) of the job to be monitored for dataset or NCT2 events. Job name (or mask) of a job or started task that arrived on the JES spool from any source. Job name (or mask) of a job or started task which terminated. Job step whose termination is to be monitored for a specified return code or status.
Subparameters of these parameters are described in the detailed description of each parameter later in this section.
General Parameters
The following parameters contain general information about the rule. OWNER GROUP MODE RUNTSEC ID of user who requests CMEM services. Name of a group of rules. CMEM rule operation mode. Type of runtime security checks to be performed for the rule.
DESCRIPTION Free-text description of the rule definition.
Action Parameters
The following parameters (DO statements) specify actions to be performed. DO statement Action to be performed when the rule is triggered. Subparameters may be displayed. Valid DO statements are: DO COND DO FORCEJOB DO STOPJOB Add/delete a prerequisite condition. Force a job order under CONTROL-M. Stop execution of the remaining steps of the job which triggered the rule.
The following actions can be defined if CONTROL-O is installed: DO RULE DO SHOUT Invoke a CONTROL-O rule from within the current rule. Issue a message to a specified destination using the Shout facility.
49
CONTROL-M Event Manager: Parameter Descriptions
Parameter Descriptions
Parameter descriptions are provided in the following format: Purpose Format Purpose of the parameter. Graphic illustration of how the parameter appears in the CMEM Rule Definition screen, followed by a detailed description of the parameters format and, where relevant, subparameters and valid values.
General Information Detailed information about the usage and functioning of the parameter. Examples Examples illustrating how the parameter might be defined and used in a CMEM rule definition.
4 10
DESCRIPTION
General Parameter
DESCRIPTION
Description of the rule to be displayed in the Rule List screen.
General Parameter
Format
Optional. Parameter DESCRIPTION consists of one or more lines which can contain free text. Each line is 61 characters in length. Upon specifying text in a DESCRIPTION line and pressing <ENTER>, a new DESCRIPTION line is opened.
General Information
Parameter DESCRIPTION does not affect rule processing. The text specified in the first DESCRIPTION line appears to the right of the rule name in the Rule List screen. It is intended to let the user know at a glance the purpose of (or some other key information about) the rule. The text can be specified in any language.
4 11
DESCRIPTION
General Parameter
Example
The description START THE BATCH SHIFT will appear next to the rule name in the Rule List screen.
RL: CICSPROD LIB CTM.PROD.RULES TABLE: STCS COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON JOBEND = CICSPROD JTYPE SMFID SYSTEM And/Or/Not OWNER ADMIN GROUP CICS MODE PROD RUNTSEC DESCRIPTION START THE BATCH SHIFT DESCRIPTION =========================================================================== /* INFORM CONTROL-M THAT THE BATCH CAN BE STARTED DO COND = START-BATCH ODAT + DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 12
DO statement
Action Parameter
DO statement
Actions to perform when the rule is triggered.
Action Parameter
Format
At least one DO statement must be specified in each rule. Specify DO statements as follows:
Type the action keyword (e.g., COND) in the DO field and press <ENTER>. When required, subparameter fields will be displayed. Fill in the subparameter(s) and press <ENTER> again.
Multiple DO statements can be specified. After entering a DO statement, another DO line is automatically displayed. Multiple DO statements have an AND relationship and are performed sequentially. The following are valid DO actions. Each is discussed individually in this section of the manual. DO COND DO FORCEJOB DO STOPJOB Adds and/or deletes one or more prerequisite conditions. Forces a job. Stops execution of the job which triggered the rule, at the end of the current step.
If CONTROL-O is installed: DO RULE DO SHOUT Invokes a CONTROL-O rule. Sends a message to a specified destination.
4 13
DO COND
Action Parameter
DO COND
Add or delete prerequisite conditions.
Action Parameter
Format
Optional. Type the word COND (or its abbreviation CON) in the DO field and press <ENTER>. Specify the following subparameters are displayed: condition dateref User-supplied, descriptive name of 1-20 characters used to identify the condition. Only trailing blanks are permitted. 4-character date reference associated with the condition. Valid values: date ODAT DATE STAT Specific date (in mmdd or ddmm format, depending on the site standard). Resolves to the current installation working date. Default. Resolves to the current system date. Static. Indicates that the condition (e.g., IMS-ACTIVE) is not date-dependent. Note STAT replaces the 0101 date value specified for such conditions prior to IOA Release 5.0.0. Although 0101 can still be specified, STAT is preferred because it cannot be confused with an actual date.
**** /$$$$ All dates. Valid only for deleting prerequisite conditions. Either value (**** or $$$$) results in the deletion of all matching prerequisite conditions regardless of date. condopt Indicator of whether to add or delete the prerequisite condition. Valid values: + Add the prerequisite condition. Delete the prerequisite condition.
4 14
DO COND
Action Parameter
General Information
When a rule containing a DO COND statement is triggered, the designated prerequisite condition(s) are added or deleted (as specified) from the IOA Conditions/Resources file by the CONTROL-M monitor. A prerequisite condition can define any user-specified situation. The following are a few examples of prerequisite conditions:
IMS-ACTIVE WEEKEND SALARY-OK
Prerequisite conditions created or deleted by the DO COND parameter can activate or deactivate CONTROL-O rules, or trigger (or stop) the execution of processes (jobs, etc.) in CONTROL-M, CONTROL-D and other environments. CMEM AutoEdit System variable %%$JNAME and, for ON DSNEVENT events, variables %%$Dx, %%$DSN, or %%$DSNDISP can be specified in condition names in DO COND statments and will be replaced (resolved) at time of rule triggering. See CMEM AutoEdit Variables earlier in this section. Representative dates (e.g., ODAT) are resolved to the actual corresponding date in the site-standard format.
Example 1
When job CICSPROD ends, this rule sets the condition necessary for the batch shift to begin.
21.00.36
4 15
DO COND
Action Parameter
Example 2
When a dataset with name prefix TRAN arrives via file transfer product CONNECT DIRECT (formerly called NDM), add prerequisite condition FILE-RECEIVED to notify CONTROL-M that the dataset was received.
RL: NDM LIB CTM.PROD.RULES TABLE: MGT COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON DSNEVENT = NDM JTYPE SMFID SYSTEM DSN TRAN.* DISP CATLG PROCSTEP PGMSTEP STEPRC OK And/Or/Not OWNER ADMIN GROUP NDM MODE RUNTSEC DESCRIPTION NOTIFY CONTROL-M THAT TRAN DATASET ARRIVED VIA NDM DESCRIPTION =========================================================================== DO COND = FILE-RECEIVED ODAT + DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 16
DO FORCEJOB
Action Parameter
DO FORCEJOB
Force a job(s).
Action Parameter
Format
Optional. Type the word FORCEJOB (or its abbreviation F) in the DO field and press <ENTER>. The following subparameters are displayed: TABLE JOB Name of a scheduling table, up to eight characters. Mandatory. Name of the job to be triggered. Optional. If blank, all jobs in the table are forced. If AutoEdit System variable %%$JNAME is specified, it resolves to the name of the job that triggered the rule. LIBRARY DATE Name of the Mandatory. scheduling library containing the specified table.
Scheduling date of the job. Valid values: date ODAT DATE Specific 6-character date (in format mmddyy, ddmmyy, or yymmdd, depending on the site standard). Resolves to the current installation working date. Default. Resolves to the current system date.
General Information
DO FORCEJOB places a job order in the CONTROL-M Active Jobs file, even if the jobs basic scheduling criteria are not satisfied. See Job Ordering and Job Forcing in Section 1 of this manual. The DO FORCEJOB statement in CMEM enables CONTROL-M to order CONTROL-M scheduling tables based on the occurrence of an event (job arrival, job end, dataset event, step event). The DO FORCEJOB statement is executed by the CONTROL-M monitor.
4 17
DO FORCEJOB
Action Parameter
If the CONTROL-M monitor is not active, the DO FORCEJOB request is queued and performed when the CONTROL-M monitor becomes active. DO FORCEJOB logic works differently for job arrival events than for job end, dataset or step events: Job End Events DO FORCEJOB statements specified in a job end rule are performed only if the terminating job is under CONTROL-M control. Dataset or Step Events DO FORCEJOB statements specified in a dataset or step event rule are performed regardless of where the job was submitted. Job Arrival Events For the first DO FORCEJOB statement in a rule:
If the job which triggered the job arrival event was submitted by CONTROL-M, the DO FORCEJOB statement is ignored. If the job which triggered the job arrival event was not submitted by CONTROL-M, CONTROL-M forces the requested table/job. CONTROL-M scans the forced table looking for a job whose MEMNAME value matches (or is a mask for) the name of the job whose arrival triggered the rule. If a matching job is found, it becomes an On Spool job. See Creating On Spool Jobs earlier in this section of the manual. All other jobs (i.e., if a matching job was not found or more than one job was ordered) are not On Spool jobs and are processed normally by CONTROL-M.
For the other DO FORCEJOB statements in the same rule:
The DO FORCEJOB is performed regardless of the source of the job. The table is forced.
DO FORCEJOB is not executed if a preceding ON JOBARRIV rule with a DO FORCEJOB action was already executed for this event.
4 18
DO FORCEJOB
Action Parameter
Example 1
Control all jobs not submitted by CONTROL-M.
RL: * LIB CTM.PROD.RULES TABLE: JOBS COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON JOBARRIV = * JTYPE J SMFID SYSTEM And/Or/Not OWNER ADMIN GROUP EXTJOBS MODE RUNTSEC DESCRIPTION CONTROL ALL JOBS NOT SUBMITTED BY CONTROL-M DESCRIPTION =========================================================================== DO FORCEJOB = TABLE ANYJOB JOB DATE ODAT LIBRARY CTM.PROD.SCHEDULE DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
Scheduling table ANYJOB should contain at least one job scheduling definition.
4 19
DO FORCEJOB
Action Parameter
Example 2
Control all jobs submitted by CICS. These fall into the following groups: Jobs whose name starts with A and jobs whose name starts with C.
RL: A* LIB CTM.PROD.RULES TABLE: JOBS COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON JOBARRIV = A* JTYPE J SMFID SYSTEM And/Or/Not O ON JOBARRIV = C* JTYPE J SMFID SYSTEM And/Or/Not OWNER ADMIN GROUP CICS MODE RUNTSEC DESCRIPTION CONTROL ALL JOBS SUBMITTED BY CICS (BEGINNING WITH A* OR C*) DESCRIPTION =========================================================================== DO FORCEJOB = TABLE CICSJOB JOB %%$JNAME DATE ODAT LIBRARY CTM.PROD.SCHEDULE DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
Scheduling table CICSJOB should contain at least two job scheduling definitions:
One should contain a MEMNAME value beginning with A. Another should contain a MEMNAME value beginning with B.
4 20
DO RULE
Action Parameter
DO RULE
Action Parameter
Invoke a CONTROL-O rule from within the current rule. Available only if CONTROL-O is installed.
Format
Optional. Type the word RULE (or its abbreviation RU) in the DO field and press <ENTER>. The following subparameters are displayed: rulename Name of the CONTROL-O rule to be executed. A maximum of eight characters can be specified. Note The rule to be executed must contain an ON RULE statement with the same rule name specified in this parameter.
args
Optional input/output arguments to be passed to the rule can be specified (following the rulename and separated from it by a blank). Arguments must be valid AutoEdit expressions separated by commas. An unlimited number of arguments can be specified. However, the combined length of the rulename and arguments cannot exceed 45 characters. Value of the OWNER field in the invoked rule. This subparameter is used for security purposes. Optional. Name of the CONTROL-O rule table in which the invoked rule resides. ALL, when specified, implies that the invoked rule may reside in any rule table. If a table name is not specified, the current rule table is assumed by default. Name of the CONTROL-O rule table library where the invoked rule resides. ALL, when specified, implies that the invoked rule may reside in any rule table library. If a library name is not specified, the current rule table library is assumed by default.
OWNER TABLE
LIBRARY
4 21
DO RULE
Action Parameter
General Information
To define a DO RULE statement in a CMEM rule, and to access a CMEM rule containing a DO RULE statement, CONTROL-O must be installed. Note To order a CMEM rule containing a DO RULE statement and to invoke the CONTROL-O rule specified in the CMEM DO RULE statement, CONTROL-O must be active.
When a DO RULE statement is encountered during rule processing, CONTROL-O invokes the specified rule. When processing of the invoked rule is completed, processing continues sequentially from the point after the DO RULE statement in the initial (calling) rule. When a DO RULE statement is executed, the specified rule is searched for among the loaded rules according to the specified rule name, table, library, and owner. If the rule is found but is not active (e.g., the runtime scheduling criteria are not satisfied), the invoked rule will not be executed and the calling rule will continue execution with the next DO statement. The CMEM calling rule can pass an argument string as input to the called rule. This argument string can contain CMEM AutoEdit expressions which are resolved at time of rule execution. The argument string can be accessed by the called rule via CONTROL-O System variable %%$ARGS. If a called rule calls another CONTROL-O rule, the %%$ARGS values passed in the earlier call will be overwritten by the %%$ARGS values passed by the later call. For information about the AutoEdit facility in CONTROL-O, see Section 4 of the CONTROL-O User Manual. A CONTROL-O rule specified with an ON RULE statement can be invoked any number of times by DO RULE calls. A called CONTROL-O rule can invoke other CONTROLO rules via DO RULE statements. Nesting of DO RULE calls (e.g., rule 1 calls rule 2, which calls rule 3) up to 20 deep is supported. A CONTROL-O rule can be called recursively.
4 22
DO RULE
Action Parameter
Example
When a dataset named PROD.TRAN.* is cataloged by TCPIP, invoke a CONTROL-O rule which will start a task to process it.
RL: TCPIP LIB CTM.PROD.RULES TABLE: TRANS COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON DSNEVENT = TCPIP JTYPE SMFID SYSTEM DSN PROD.TRAN.* DISP CATLG PROCSTEP PGMSTEP STEPRC OK And/Or/Not OWNER ADMIN GROUP TCPIP MODE RUNTSEC DESCRIPTION WHEN DATASET PROD.TRAN.* IS CATALOGED BY TCIP, DESCRIPTION START A TASK TO PROCESS IT DESCRIPTION =========================================================================== /* START A STARTED TASK TO PROCESS THE RECEIVED FILE. /* WHEN THE DATASET IS CATALOGED, INVOKE RULE PROCFILE. /* PARAMETERS PASSED ARE THE STC NAME AND THE TIMEOUT VALUE. DO RULE = PROCFILE %%$DSN OWNER PROD TABLE PRODRULE LIBRARY CTO.PROD.RULES DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 23
DO SHOUT
Action Parameter
DO SHOUT
Action Parameter
Send (shout) a message to a destination. Available only if CONTROL-O is installed.
Format
Optional. Type the word SHOUT (or its abbreviation SH) in the DO field and press <ENTER>. The following subparameters are displayed: TO Destination of 1-16 characters in length. Valid values: U-userid or USERID-userid Writes the message to the IOA Log file under the specified user ID. userid must be 1-8 characters.
rrr OPER [dd ] - -ccc Sends the message to operator consoles, on the basis of the optional subparameters (dd, rrr, and ccc) described below:
dd rrr Descriptor code (from 0 to 16). The list of descriptor codes is provided in Appendix D. Route code (from 0 to 128). The list of message route codes is provided in Appendix D. Route code and console ID are mutually exclusive. Console ID number (preceded by a hyphen) of the console to which the message is to be shouted. Console ID and route code are mutually exclusive.
-ccc
; Nn ; Mm TSO logonid ; NnMm ; Lname

Sends the message to the user identified by the specified logon ID. logonid is mandatory (1-7 characters).
4 24
DO SHOUT
Action Parameter
An optional second value, indicating the computer and/or node (e.g., Nn) of the TSO logonid, can be specified, as follows:
Under JES2
Valid values are Mm, Nn or NnMm, where: m n Machine ID (the computer in JES2, not the 4-character SMF ID). 1-2 character JES/NJE node ID.
Under JES3
Valid values are Lname, where: name Logical JES name of the machine (i.e., as used in JES3, command *T, not the MVS/SMF system ID). A shout to a TSO user performs a TSO SEND command which may require authorization at the receiving node.
Note
URGENCY
MESSAGE
Message text.
General Information
When TO=USERID-userid, the message is written to the IOA Log file under the specified user ID. When TO=OPER is specified, the message is sent either to all operator consoles or to operator consoles selected according to a specified route code or console ID number. The descriptor code determines the type of message displayed. These parameters are optional and can be assigned any valid value. (Valid Route codes and Descriptor codes are listed in Appendix D.) Dashes ( ) are used to separate the parameters specified. Examples OPER OPER2 OPER-5 OPER2-5 OPER--4 Send the message to all operator consoles. Send a highlighted unrollable message (descriptor code 2) to all operator consoles. Send a message to operator consoles associated with route code 5. Send a highlighted unrollable message to operator consoles associated with route code 5. Send a message to operator console ID 04.
4 25
DO SHOUT
Action Parameter
OPER2--4
Send a highlighted unrollable message (descriptor code 2) to operator console ID 04.
When TO=TSO-logonid, the message is sent to the specified TSO logonid. If the ;... option is used, the message is sent to the TSO logon ID in the specified computer (machine ID, node ID). Note If the value specified in the TO field is defined in the Dynamic Destination table, the TO field value is interpreted according to the definition in that table. See IOA Dynamic Destination Table in Section 2 of the IOA Administrator Guide.
It is also possible to shout to a ROSCOE user. See your IOA administrator for additional information. The URGENCY subparameter is mandatory. Using this subparameter with the TO=USERID-userid option has the following effect: When the IOA Log file is accessed by the user from the Online facility, the user can define, and therefore restrict, the type of messages that will be displayed according to their urgency. Both urgent and very urgent messages are highlighted on the screen.
Example
When started task DB2MSTR ends, issue a message to the DBA who is on duty. Notice the use of the generic TSO user name, which the Dynamic Destination table interprets to be one or more TSO users.
RL: DB2MSTR LIB CTM.PROD.RULES TABLE: STCS COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON JOBEND = DB2MSTR JTYPE S SMFID SYSTEM And/Or/Not OWNER ADMIN GROUP DB2 MODE RUNTSEC DESCRIPTION WARN DBA THAT DB2 MASTER ENDED DESCRIPTION =========================================================================== DO SHOUT = TO TSO-DBA URGENCY U MESSAGE DB2 MASTER ENDED - PLEASE CHECK! DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 26
DO STOPJOB
Action Parameter
DO STOPJOB
Stop execution of the job which triggered the rule after the current step.
Action Parameter
Format
Optional. Type STOPJOB (or its abbreviation ST) in the DO field and press <ENTER>.
General Information
When DO STOPJOB is performed, the job which triggered the rule is terminated after the current step, and no further steps (including those marked COND=EVEN or COND=ONLY) are executed. An appropriate message is written to the job log. If the stopped job is controlled by CONTROL-M, it terminates with a status of ENDED NOTOK. DO STOPJOB is not executed for TSO users. DO STOPJOB is meaningful only:
For dataset events or step events When there are additional steps in a job or started task
4 27
DO STOPJOB
Action Parameter
Example
If the production dataset disposition is NOT CATLGD 2, stop the job.
RL: PROD* LIB CTM.PROD.RULES TABLE: JOB COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON DSNEVENT = PROD* JTYPE J SMFID SYSTEM DSN PROD.* DISP NCT2 PROCSTEP PGMSTEP STEPRC And/Or/Not OWNER ADMIN GROUP PRODJOBS MODE RUNTSEC DESCRIPTION STOP THE JOB ON NCT2 DISPOSITION DESCRIPTION =========================================================================== /* STOP THE JOB DO STOPJOB DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 28
GROUP
General Parameter
GROUP
Name of the group to which the rule belongs.
General Parameter
Format
Optional. Name of 1-20 characters (no embedded blanks).
General Information
Parameter GROUP is used to provide more convenient handling of rules. It enables retrieval of information on a group basis. The group name appears in all important IOA Log file messages relating to the groups rules.
4 29
GROUP
General Parameter
Example
The rule which instructs CONTROL-M to start the batch shift when CICSPROD ends belongs to group CICS.
21.00.36
4 30
MODE
General Parameter
MODE
Rule operation mode.
General Parameter
Format
Optional. Valid values (and their abbreviations) for parameter MODE: PROD TEST LOG P T L Standard Production mode. The rule is processed normally. Default. Test mode. Actions are not performed, but are written to a test journal. Log mode. The rule is processed normally and all identified events and actions are written to a test journal.
General Information
Test mode provides the opportunity to test the effects of a rule definition without actually performing the specified DO actions. Log mode provides a transition between Test and Production mode. Like Production mode, Log mode enables performance of the specified DO actions. However, Log mode also records the trace information in the test journal for tracking purposes. When tracking of the performed actions for test purposes is no longer required, the rule can be placed in Production mode. For sites in which CONTROL-O is not installed, or in which the CONTROL-O Automation Log facility is not active, the trace information is written to the sysout referenced by DD statement DAACTLOG. For CONTROL-O sites in which the Automation Log facility is active, the trace information is recorded in the Automation log. See Section 2 of the CONTROL-O User Manual for details.
4 31
MODE
General Parameter
Example
The rule which instructs CONTROL-M to start the batch shift when CICSPROD ends is activated in Production mode.
21.00.36
4 32
ON statement
Event Parameter
ON statement
Event selection criteria which will trigger performance of the rule.
Event Parameter
Format
Mandatory. At least one ON statement must be specified. Type an ON statement (or its abbreviation) in the ON field and press <ENTER>. Additional subparameters will be displayed. The following are valid ON statements (and their abbreviations). Each is described in detail later in this section. ON DSNEVENT ON JOBARRIV ON JOBEND ON STEP D JA JE S Name (or mask) of a job, started task, or TSO user to be monitored for dataset events. Job name (or mask) of a job or started task that arrived on the JES spool from any source. Job name (or mask) of a job or started task which terminated. Name (or mask) of a procedure step (and optionally, program step) to be monitored for termination.
The following subparameter is always displayed in each specified ON statement: And/Or/Not Conjunctional parameter for linking ON statements. Optional. Specifying a value for this subparameter opens a new ON statement and links the newly-opened statement to the current ON statement. When multiple ON statements are specified, the combinations of ON statements which can satisfy the selection criteria depend on the And/Or/Not values linking those ON statements. The logic applied to And/Or/Not subparameters is described in General Information below.
4 33
ON statement
Event Parameter
Valid values: A (And) Indicates AND logic between the two statements. If both ON statements are true, the event criteria are satisfied. Indicates OR logic between the preceding and following ON statements. If either statement is true, the event criteria are satisfied. Indicates AND NOT logic between the two statements. If the prior statement is true and the subsequent statement is false, the event criteria are satisfied.
O (Or)
N (Not)
General Information
Upon specifying an ON parameter and pressing <ENTER>, additional fields (subparameters) are displayed. Each ON parameter and its subparameters comprise an ON statement. At least one ON statement is required in a rule definition. Additional ON statements can be specified using the And/Or/Not option. The first eight characters of the event name appear as the rules name in the Rule List screen. And/Or/Not Subparameter Logic AND and NOT logic are applied before OR logic. NOT means AND NOT as represented below: A NOT B is interpreted as: A AND (NOT B) A OR B AND C is interpreted as: A OR (B AND C) A AND B OR C NOT D is interpreted as: [(A AND B) OR (C AND NOT D)] Use of OR logic reduces the amount of redundant data in the CMEM rule library and improves rule management. Note When specifying multiple ON statements, ensure that the statements are not mutually exclusive or not connected by an AND parameter. Rules containing mutually exclusive ON statements connected by an AND parameter will never be triggered. For example:
ON DSNEVENT AND ON DSNEVENT JOBA STEPB JOBA STEPA
Character Masking The following mask characters can be specified in ON statement values: * ? Represents any number of characters, including no characters. Represents any one character.
4 34
ON DSNEVENT
Event Parameter
ON DSNEVENT
Monitor a dataset disposition event.
Event Parameter
Format
Optional. Type D (DSNEVENT) in the ON field and press <ENTER>. The following subparameters are displayed: jobname JTYPE Name (or mask) of the job to be monitored for dataset events. Mandatory. Type of job to be monitored for dataset events: J (Job) S (STC) T (TSU) blank Batch job. Started task. TSO user. Any type of job. Valid only if STEPRC is blank (i.e., the rule is processed immediately upon detection of the dataset event). Default.
If JTYPE is specified, only a dataset event occurring in a job of the specified type can trigger the rule. SMFID SYSTEM DSN SMF ID of the CPU to monitor for dataset events. Mask characters (* and ?) are supported. Default: current CPU. Name of the system to monitor for dataset events. Mask characters (* and ?) are supported. Default: current system. Name of dataset (or mask) to be monitored for this event within the selected jobs. Mandatory.
4 35
ON DSNEVENT
Event Parameter
DISP
Dataset disposition. Mandatory. The abbreviation (i.e., the first letter) of the desired value can be specified. Valid values: CATLG DELETE UNCATLG KEEP RETAIN SCRATCH ALL NCT2 Cataloged (including SMS-managed files and ROLLED-IN SMS-managed GDG files). Deleted. Uncataloged. Kept (including SMS-managed files). Cataloged or Kept. Deleted and uncataloged (SMS managed files). Any of the above dispositions. Occurrence of a NOT CATLG 2 event when a dataset was created in a previous job step, but not cataloged at deallocation because its name already exists in the MVS catalog. Any of the above dataset dispositions (including NCT2).
* PROCSTEP
Name or mask of a step invoking a procedure or, for a started task, task ID. Optional. If omitted, all procedure steps in the selected jobs are monitored. Note When a started task is initiated, it can be assigned a task ID. For example, in command S GTF.G, the task ID of GTF is G. If a task ID is not specified, MVS assigns a default task ID to the started task, as follows:
For a system started task with stepname IEFPROC, MVS sets an

internal task ID.
For other started tasks, the default task ID equals the procedure
(started task) name. Therefore, when using CMEM to monitor system started tasks, if no task ID is specified in the START command, parameter PROCSTEP should not be specified. PGMSTEP Name (or mask) of a step invoking a program. Optional. If omitted, all program steps in the selected jobs are monitored. Note When a system started task with stepname IEFPROC is initiated, MVS assigns the step a default program step name. Therefore, when using CMEM to monitor these system started tasks, parameter PGMSTEP should not be specified.
4 36
ON DSNEVENT
Event Parameter
STEPRC
Determines at which point in the job step, and under what conditions in the job step, the DO statements will be performed. Valid values: blank If no completion code is specified, the rule is executed immediately upon detection of the specified dataset event.
If any of the following values is specified for STEPRC, execution of the DO statements is delayed until the end of the monitored job step and is dependent upon how the jobstep ended: OK NOTOK **** Cnnnn Snnn Unnnn Step ended with a condition code of zero. Step ended with a non-zero code. Step ended (with any code). Step ended with the indicated condition code. Step ended with the indicated system abend code. Step ended with the indicated user abend code.
Asterisks can be specified instead of code digits; condition codes and abends can be preceded by code qualifiers (<, >, N). See General Information below. And/Or/Not Conjunctional parameter which opens a new ON statement and links it to the previous ON statement. Optional. Valid values: A (And) O (Or) N (Not) Indicates AND logic between the two ON statements. Indicates OR logic between the preceding and following sets of ON statements. Indicates AND NOT logic between the two ON statements.
General Information
ON DSNEVENT rules are triggered by the setting of dataset disposition at time of deallocation (during step termination or dynamic deallocation). DO statements in the rule are executed either immediately upon detection of the dataset event or at the end of the job step which caused the dataset event, depending on the value specified in subparameter STEPRC (described above). Immediate execution is useful for performing actions when datasets are dynamically deallocated via long-running address spaces (e.g., CICS, TSO users, and file transfer monitors). ON DSNEVENT rules only intercept dataset events for jobs, started tasks, or TSO users that started after the rule was ordered. Note To monitor dataset events for a job, started task or TSO user, the job, started task or TSO user must have MSGLEVEL=(1,1) and message IEF403I or IEF125I should appear in the job log.
4 37
ON DSNEVENT
Event Parameter
ON DSNEVENT rules do not intercept dataset events (e.g., cataloging, uncataloging, or scratching) when they are performed via MVS CATALOG or SCRATCH macros. The following restrictions apply to ON DSNEVENT statements:
An ON DSNEVENT statement should not be specified with any other type of ON statement in a rule. Different STEPRC values should not be specified in the same rule. If they are, the last specified value will be used.
Specification of values for optional subparameters PROCSTEP, PGMSTEP and STEPRC limits the situations that can satisfy the step termination event. Conversely, if a subparameter is blank, that subparameter is ignored. Example
If a PGMSTEP and PROCSTEP value are both specified, the rule is triggered only if the specified PGMSTEP is completed in the specified PROCSTEP. If a PGMSTEP value is specified without a PROCSTEP value, the rule is triggered if the PGMSTEP is completed anywhere within the job stream.
Subparameter STEPRC When specifying a condition code or abend code in subparameter STEPRC, any character(s) in the code can be replaced by an asterisk (*). An asterisk means any value for the character it replaces. For example, if S*13 is specified, the code criteria will be satisfied by codes S013, S613, S913, etc. When specifying condition and/or abend codes, the following qualifiers can be used as indicated: > < Greater than. Valid for condition codes and user abend codes. Less than. Valid for condition codes and user abend codes.
N Triggers the rule if the specified code does not exist in the step. Valid as a qualifier for condition codes, user abend codes, and system abend codes. Prior to CONTROL-M Release 5.0.0, parameter STEPRC was called WHEN. Corresponding parameter values are listed below: STEPRC Value blank OK **** Corresponding WHEN Statement WHEN=IMMED WHEN=STEPENDOK WHEN=STEPEND
Subparameters SMFID and SYSTEM The default values for subparameters SMFID and SYSTEM are the current system. If no value is specified for either SMFID or SYSTEM, the rule is triggered only by events that occur in the current system.
4 38
ON DSNEVENT
Event Parameter
Example
When a new production dataset is created, trigger a backup job.
RL: PRDJ0003 LIB CTM.PROD.RULES TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON DSNEVENT = PRDJ0003 JTYPE SMFID SYSTEM DSN PROD.* DISP CATLG PROCSTEP PGMSTEP STEPRC OK And/Or/Not OWNER ADMIN GROUP BACKUP MODE PROD RUNTSEC DESCRIPTION NEW DATASET CREATED - TRIGGER A BACKUP JOB DESCRIPTION =========================================================================== /* SCHEDULE A CONTROL-M JOB TO HANDLE THE BACKUP /* DO FORCEJOB = TABLE BACKUP JOB BACKUP DATE ODAT LIBRARY CTM.PROD.SCHEDULE /* DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 39
ON JOBARRIV
Event Parameter
ON JOBARRIV
Monitor a job arrival event on the JES spool.
Event Parameter
Format
Optional. Type JA (JOBARRIV) in the ON field and press <ENTER>. The following subparameters are displayed: name JTYPE Job name (or mask). Mandatory. (See Character Marking in Section 2 of this manual.) Type of job which can trigger the rule. Optional. Valid values: J (JOB) S (STC) T (TSU) Blank SMFID SYSTEM And/Or/Not Batch job Started task TSO user If no value is specified, the rule can be triggered by any type of job. Default.
SMF ID of the CPU to monitor for dataset events. Mask characters (* and ?) are supported. Default: current CPU. Name of the system to monitor for dataset events. Mask characters (* an ?) are supported. Default: current system. Conjunctional parameter which opens a new ON statement and links it to the previous ON statement. Optional. Valid values: A (And) O (Or) N (Not) Indicates AND logic between the two ON statements. Indicates OR logic between the preceding and following sets of ON statements. Indicates AND NOT logic between the two ON statements.
4 40
ON JOBARRIV
Event Parameter
General Information
ON JOBARRIV statements can be used to trigger CONTROL-M actions based on the appearance of a job on the JES spool. Combination of an ON JOBARRIV statement and a DO FORCEJOB statement, can be used to control an external job via CONTROL-M. Such a job is called an On Spool job. For more information, see On Spool Jobs earlier in this section. The default values for subparameters SMFID and SYSTEM are the current system. If no value is specified for either SMFID or SYSTEM, the rule is triggered only by events that occur in the current system.
Example
Backup jobs submitted outside CONTROL-M should be monitored by CONTROL-M.
RL: BKP* LIB CTM.PROD.RULES TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON JOBARRIV = BKP* JTYPE SMFID SYSTEM And/Or/Not OWNER ADMIN GROUP BACKUP MODE PROD RUNTSEC DESCRIPTION MONITOR EXTERNAL BACKUP JOBS DESCRIPTION =========================================================================== /* TELL CONTROL-M TO MONITOR THIS JOB /* DO FORCEJOB = TABLE BACKUP JOB DATE ODAT LIBRARY CTM.PROD.SCHEDULE /* DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 41
ON JOBEND
Event Parameter
ON JOBEND
Monitor a job termination event.
Event Parameter
Format
Optional. Type JE (JOBEND) in the ON field and press <ENTER>. The following subparameters are displayed: name JTYPE Job name (or mask). Mandatory. Type of job whose termination can trigger the rule. Optional. Valid values: J (JOB) S (STC) T (TSU) blank SMFID SYSTEM And/Or/Not Batch job Started task TSO user If no value is specified, the rule can be triggered by the termination of any type of job. Default.
SMF ID of the CPU to monitor for dataset events. Mask characters (* and ?) are supported. Default: current CPU. Name of the system to monitor for dataset events. Mask characters (* and ?) are supported. Default: current system. Conjunctional parameter which opens a new ON statement and links it to the previous ON statement. Optional. Valid values: A (And) O (Or) N (Not) Indicates AND logic between the two ON statements. Indicates OR logic between the preceding and following sets of ON statements. Indicates AND NOT logic between the two ON statements.
4 42
ON JOBEND
Event Parameter
General Information
ON JOBEND statements can be used to trigger CONTROL-M actions based on the termination of a job. The default values for subparameters SMFID and SYSTEM are the current system. If no value is specified for either SMFID or SYSTEM, the rule is triggered only by events that occur in the current system.
Example
Instruct CONTROL-M to start the batch shift when CICSPROD ends.
21.00.36
4 43
ON STEP
Event Parameter
ON STEP
Monitor a job step termination event.
Event Parameter
Format
Optional. Type S (STEP) in the ON field and press <ENTER>. The following subparameters are displayed: job JTYPE Name (or mask) of the job to be monitored for step termination. Mandatory. Type of job to be monitored for step termination. Optional. Valid values: J (Job) S (STC) blank Batch job. Started task. Any type of job. Default.
If JTYPE is specified, only the termination of steps from the specified type of job can trigger the rule. SMFID SYSTEM PROCSTEP SMF ID of the CPU to monitor for dataset events. Mask characters (* and ?) are supported. Default: current CPU. Name of the system to monitor for dataset events. Mask characters (* and ?) are supported. Default: current system. Name (or mask) of a step invoking a procedure or, for a started task, task ID. Optional. If omitted, all procedure steps in the selected job(s) are monitored.
4 44
ON STEP
Event Parameter
Note
When a started task is initiated, it can be assigned a task ID. For example, in command S GTF.G, the task ID of GTF is G. If a task ID is not specified, MVS assigns a default task ID to the started task, as follows:
For a system started task with stepname IEFPROC, MVS sets an

internal task ID.
For other started tasks, the default task ID equals the procedure
(started task) name. Therefore, when using CMEM to monitor system started tasks, if no task ID is specified in the START command, parameter PROCSTEP should not be specified. PGMSTEP Name (or mask) of a step invoking a program. Optional. If omitted, all program steps in the selected job(s) are monitored. Note When a system started task with stepname IEFPROC is initiated, MVS assigns the step a default program step name. Therefore, when using CMEM to monitor these system started tasks, parameter PGMSTEP should not be specified.
STEPRC
Return codes(s) and/or status(es) returned upon termination of the specified step(s) which will satisfy the step termination criteria. Valid values: blank/**** Step ended (i.e., with any code or status). If no value or four asterisks are specified, the return code or status is irrelevant. OK NOTOK Cnnnn Snnn Unnnn Step ended with a condition code of 0. Step ended with a non-zero code. Step ended with the indicated condition code. Step ended with the indicated system abend code. Step ended with the indicated user abend code.
Asterisks can be specified instead of code digits; condition codes and abends can be preceded by code qualifiers (<, >, N). See General Information below. And/Or/Not Conjunctional parameter which opens a new ON statement and links it to the previous ON statement. Valid values: A (And) O (Or) N (Not) Indicates AND logic between the two ON statements. Indicates OR logic between the preceding and following sets of ON statements. Indicates AND NOT logic between the two ON statements.
4 45
ON STEP
Event Parameter
General Information
ON STEP rules are triggered when specified job steps terminate with specified return codes or statuses. Specification of values for optional subparameters PROCSTEP, PGMSTEP and STEPRC limits the situations that can satisfy the step termination event. Conversely, if a subparameter is blank, that subparameter is ignored.
If a PGMSTEP and PROCSTEP value are both specified, the rule is triggered only if the specified PGMSTEP is completed in the specified PROCSTEP. If a PGMSTEP value is specified without a PROCSTEP value, the rule is triggered if the PGMSTEP is completed anywhere within the job stream.
Subparameter STEPRC When specifying a condition code or abend code in subparameter STEPRC, any character(s) in the code can be replaced by an asterisk (*). An asterisk means any value for the character it replaces. For example, if S*13 is specified, the code criteria will be satisfied by codes S013, S613, S913, etc. When specifying condition and/or abend codes, the following qualifiers can be used as indicated: > < Greater than. Valid for condition codes and user abend codes. Less than. Valid for condition codes and user abend codes.
N Triggers the rule if the specified code does not exist in the step. Valid as a qualifier for condition codes, user abend codes, and system abend codes. Subparameters SMFID and SYSTEM The default values for subparameters SMFID and SYSTEM are the current system. If no value is specified for either SMFID or SYSTEM, the rule is triggered only by events that occur in the current system.
4 46
ON STEP
Event Parameter
Example When step STEP2 in job PRD00010 is completed, add a prerequisite condition indicating that a file has been created.
RL: PRD00010 LIB CTM.PROD.RULES TABLE: CMEMRULE COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON STEP = PRD00010 JTYPE SMFID SYSTEM PROCSTEP STEP2 PGMSTEP STEPRC OK And/Or/Not OWNER CTMCTLM GROUP MODE PROD RUNTSEC NONE DESCRIPTION FOLLOWING STEP2 IN JOB PRD00010 ADD A CONDITION DESCRIPTION INDICATING THAT THE FILE WAS CREATED DESCRIPTION =========================================================================== DO COND = FILE-CREATED ODAT + DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 47
OWNER
General Parameter
OWNER
ID of the user who is requesting CMEM services.
General Parameter
Format
Mandatory. Name of 1-8 characters.
General Information
Parameter OWNER is primarily used by CMEMs internal security mechanism to determine which actions the user is authorized to perform. It is used in conjunction with external security products such as CA-TOP SECRET, CA-RACF and CA-ACF2. Note Prior to CONTROL-M Release 5.0.0, CMEM events were defined in member ONSPTAB. The owner of member ONSPTAB is always CTMCTLM and cannot be changed. As of Release 5.0.0, the ONSPTAB member must be converted to one or more CMEM rules via migration utility CTM2RULE. By default, the CTM2RULE utility assigns owner CTMCTLM to these CMEM rules. If required, this owner can be changed for each CMEM rule either via the CTM2RULE utility or via screen C. For more information about converting the ONSPTAB member to CMEM rules, see Converting CMEM Events to CMEM Rules under the topic Installation Considerations in Section 3 of the IOA Installation Guide.
4 48
OWNER
General Parameter
Example
The rule used to monitor the arrival of backup jobs belongs to the system administrator.
RL: BKP* LIB CTM.PROD.RULES TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON JOBARRIV = BKP* JTYPE SMFID SYSTEM And/Or/Not OWNER ADMIN GROUP BACKUP MODE PROD RUNTSEC DESCRIPTION MONITOR STARTUP OF BACKUP JOBS DESCRIPTION =========================================================================== /* TELL CONTROL-M TO MONITOR THIS JOB /* DO FORCEJOB = TABLE BACKUP JOB DATE ODAT LIBRARY CTM.PROD.SCHEDULE /* DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 49
RUNTSEC
General Parameter
RUNTSEC
Runtime security environment for the rule.
General Parameter
Format
Optional. The abbreviation (i.e., the first letter) of the desired value can be specified. Valid values: NONE OWNER TRIGGER blank Runtime security checks are not performed for this rule. Runtime security checks are performed using the user ID entered in the OWNER field of the rule. Runtime security checks are performed using the user ID associated with the started task/TSO user/batch job which invoked the rule. If CONTROL-O is not active, the default is OWNER. If CONTROL-O is active, runtime security checks will or will not be performed depending on the value of Global parameter RUNTDFT (NONE, OWNER, or TRIGGER) in member CTOPARM as specified at time of CONTROL-O installation. Value TRIGGER applies only to ON DSNEVENT, ON STEP, or ON JOBEND event rules. If the value TRIGGER is specified for an ON JOBARRIV event rule, the value is treated as OWNER.
Note
General Information
Parameter RUNTSEC is used by the CMEM security interface for interaction with external security products, such as CA-RACF, CA-TOP SECRET, and CA-ACF2. For more information see the IOA Security Guide. CMEM security checks are carried out in two stages: at order time and at runtime. At order time, security checks are carried out to ascertain whether or not the rules owner (as specified in subparameter OWNER) is authorized to code each one of the rule statements.
4 50
RUNTSEC
General Parameter
At runtime, additional security checks are carried out to determine whether or not the user who owns the rule (RUNTSEC = OWNER) or the user who triggered the rule (RUNTSEC = TRIGGER) is authorized to execute a DO COND or DO FORCEJOB statement defined in the rule.
Example
Perform a backup using security ID of the job which triggered the rule.
RL: PRDJ0003 LIB CTM.PROD.RULES TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ ON DSNEVENT = PRDJ0003 JTYPE SMFID SYSTEM DSN PROD.* DISP CATLG PROCSTEP PGMSTEP STEPRC OK And/Or/Not OWNER ADMIN GROUP BACKUP MODE PROD RUNTSEC TRIGGER DESCRIPTION NEW DATASET CREATED - TRIGGER A BACKUP JOB DESCRIPTION =========================================================================== /* SCHEDULE A CONTROL-M JOB TO HANDLE THE BACKUP /* DO FORCEJOB = TABLE BACKUP JOB BACKUP DATE ODAT LIBRARY CTM.PROD.SCHEDULE /* DO =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
21.00.36
4 51
RUNTSEC
General Parameter
4 52
Section 5: JCL and AutoEdit Facility

General ...........................................................................................................................................5-1 JCL Setup Operation Flow ........................................................................................................5-4 System Variables ..........................................................................................................................5-5 Non-Date System Variables.......................................................................................................5-5 Date System Variables ...............................................................................................................5-6 Special System Variables ...........................................................................................................5-8 User-Defined Variables...............................................................................................................5-9 Format of Variable Members.................................................................................................. 5-10 Rules of Variable Resolution.................................................................................................. 5-11 Order of Precedence for Multiple Value Assignments............................................................5-14 Control Statements................................................................................................................... 5-15 %%GLOBAL..............................................................................................................................5-15 %%GOTO and %%LABEL .......................................................................................................5-15 %%IF, %%ELSE, %%ENDIF ...................................................................................................5-16 %%INCLIB and %%INCMEM .................................................................................................5-18 %%LIBSYM and %%MEMSYM...............................................................................................5-19 %%RANGE................................................................................................................................5-20 %%RESOLVE ...........................................................................................................................5-21 %%SET ......................................................................................................................................5-21 Operators .................................................................................................................................... 5-22 Functions .................................................................................................................................... 5-23 %%$CALCDTE .........................................................................................................................5-23 %%$GREG ................................................................................................................................5-23 %%$JULIAN.............................................................................................................................5-23 %%$LEAP .................................................................................................................................5-24 %%$WCALC .............................................................................................................................5-24 %%$WEEK#..............................................................................................................................5-25 %%$WEEKDAY........................................................................................................................5-25 %%CALCDATE.........................................................................................................................5-26 %%SUBSTR ..............................................................................................................................5-26 Testing AutoEdit Syntax ......................................................................................................... 5-27 AutoEdit Usage in the Job Scheduling Definition ............................................................ 5-28
Examples ..................................................................................................................................... 5-30 Date Variables.......................................................................................................................... 5-30 ODATE, RDATE and DATE Usage ........................................................................................ 5-31 How to Obtain Date Formats 1 ............................................................................................ 5-32 How to Obtain Date Formats 2 ............................................................................................ 5-32 How to Obtain Date Formats 3 ............................................................................................ 5-33 How to Obtain the Previous Months Last Business Date .................................................... 5-34 Automatic Job Order for the Next Day................................................................................... 5-35 Tape Clearance System Stage 1........................................................................................... 5-36 Tape Clearance System Stage 2........................................................................................... 5-37 Tape Management System ...................................................................................................... 5-38 Dynamic Job Name.................................................................................................................. 5-38 Controlling the Target Computer by Class ............................................................................ 5-39 Controlling the Target Computer by System Affinity ........................................................... 5-39 %%BLANKn Statement .......................................................................................................... 5-40 %%RANGE Statement ............................................................................................................ 5-41 SYSIN Parameter Containing %%.......................................................................................... 5-42 %%INCLIB and %%INCMEM Statements ............................................................................ 5-42 Boolean IF Logic.................................................................................................................... 5-43
JCL and AutoEdit Facility: General
General
In the production environment, it is often necessary to manually modify JCL prior to submission of a job, as in the following cases:
Changing a parameter or a date card Supplying tape numbers in JCL procedures Eliminating steps under different run conditions (e.g., end of month processing vs. normal daily run)
Manual modification of JCL is inconvenient at best, and it can, in fact, be error-prone and lead to serious problems. The AutoEdit facility offers an automated alternative to manual JCL modification. This facility permits AutoEdit terms (described in this section) to be specified in the JCL in place of values which change from job submission to job submission. At time of job submission, these terms are resolved to their actual values. The inclusion of AutoEdit terms in the job stream can eliminate the need to continually change the JCL. (Some AutoEdit terms can also be used in job scheduling definitions.) AutoEdit terms are prefaced by a %% symbol, which distinguishes them from nonAutoEdit terms. For example, the term %%ODAY is recognized as an AutoEdit term. The components of the AutoEdit facility are described briefly on the following pages and in greater detail later in this section.
51
Variables Variables are the main components of the AutoEdit facility. Variables are used to replace manually-changed values, generally within the JCL. AutoEdit variables can be either of the following types:
System Variables AutoEdit System variables are predefined variables which represent information about the system. For example, AutoEdit System variable %%ODATE is replaced by the jobs original scheduling date.
User-Defined Variables In contrast to System variables, user-defined variables are created by the user. The user must provide the value (or the tools to derive the value) which will replace the variable at time of job submission. For example, the user can define a variable, %%SPACE-TYPE, to represent the type of storage unit (cylinder or track) on disk. User-defined variables can be either of the following types: Global Local Variables which are defined, and their values set, in members identified as Global members. Variables which are defined, and their values set, in any of the following locations:
Members identified as Local members %%SET statements in the jobs JCL SET VAR and DO SET statements in the job scheduling definition
User-defined variables are discussed in detail later in this section. Note AutoEdit terms must be placed within the job stream submitted by CONTROL-M, not within a catalogued JCL procedure.
Control Statements AutoEdit control statements in the JCL define the environment for user-defined variables. The AutoEdit facility supports many AutoEdit control statements, which will be discussed in detail later. Some of the more important Control Statements are described here briefly. %%GLOBAL member Identifies a member which contains a set of user-defined global variables and their assigned values. %%LIBSYM library /%%MEMSYM member Identifies a member and library which contain a set of user-defined local variables and their assigned values. %% SET %%variable = expression Sets a value to a user-defined variable in the JCL.
52
Operators AutoEdit operators modify the values of AutoEdit variables in the JCL. For example, in the following statement, operator %%PLUS assigns a number to a scratch tape that is one higher than the previously assigned tape number:
//* %%SET %%SCRATCH = %%SCRATCH %%PLUS 1
Functions AutoEdit functions perform functions on specified AutoEdit variables in the JCL. For example, in the following statement, function %%CALCDATE sets AutoEdit variable %%NEXTDAY to one day after the current System variable %%ODATE:
//* %%SET %%NEXTDAY = %%CALCDATE %%ODATE +1
The format of a function statement depends on the function. AutoEdit Components in the Job Scheduling Definition Although the most important and common use of AutoEdit components is in JCL setup, certain AutoEdit components can also be used in the job scheduling definition. Job scheduling definition statements SET VAR and DO SET assign values to user-defined variables. These statements perform a similar function as, and work together with, %%SET control statements specified in the JCL. Other job scheduling definition statements (e.g., SYSOUT, SHOUT, MEMLIB) allow specification of System variables. JCL Setup and AutoEdit Features The rest of this section contains a description of the following JCL Setup and AutoEdit topics:
JCL Setup Operation Flow System Variables User-Defined Variables Format of Variable Members Rules of Variable Resolution Control Statements Operators Functions Testing AutoEdit Syntax AutoEdit Usage in the Job Scheduling Definition Examples
53
JCL and AutoEdit Facility: JCL Setup Operation Flow
JCL Setup Operation Flow

All JCL setup operations are performed during job submission. At this time, CONTROL-M processes the JCL of the job line by line. CONTROL-M scans each line for AutoEdit terms (identified by the %% symbol) and tries to resolve them. CONTROL-M resolves all AutoEdit terms in a line before it moves to the next line. All changes made during JCL processing (e.g., variable resolution) are retained only until CONTROL-M has finished submission of the job. CONTROL-M resolves System variables by taking the values from the system. Values for user-defined variables can be taken from any of several possible sources (described below). When CONTROL-M detects a user-defined variable in the JCL line being processed, it checks these possible sources in a specific order until a value is found for the variable. CONTROL-M creates a user-defined variable environment in which it places each user-defined variable and its value. The potential sources for user-defined variable values are listed below in the order in which they are generally checked:
System variable values %%SET control statements These statements can be specified in JCL lines, including JCL comment lines. They assign values to variables.
SET VAR and DO SET statements These statements can be specified in the job scheduling definition. They can be used to define new variables, or to assign new values to existing variables. SET VAR statements can affect all job submissions. DO SET statements can override values specified by a SET VAR or previous DO SET statement. However, since DO SET statements are post-processing parameters, they only affect subsequent runs of a job (rerun/restarted jobs).
Local variables and values defined in members specified in %%LIBSYM / %%MEMSYM control statements These members define local variables and specify their values. Members are searched in the order they appear in the JCL.
Global variables and values defined in members specified in %%GLOBAL control statements These members define global variables and specify their values. Members are searched in the order they appear in the JCL.
The order in which CONTROL-M checks potential sources for possible AutoEdit variable resolution is important because once CONTROL-M has resolved a variable, it generally stops checking other sources. (Potential values from other sources are ignored, and resolved values are not overridden except by %%SET statements in subsequent JCL lines.)
54
JCL and AutoEdit Facility: System Variables Non-Date System Variables
Because JCL is processed sequentially one line at a time, the line being processed can only be affected by external members and %%SET control statements that have previously been processed. If a line contains an undefined variable which will only be defined in a subsequent line, the variable cannot be resolved. By default, if CONTROL-M cannot resolve a variable, it stops submission of the job. This default, however, can be overridden by specifying the %%RESOLVE control statement with a value of NO or OFF (described later in this section). To stop submission of a job because of an unresolved variable, CONTROL-M creates an intentional JCL error which prevents execution of the jobs already submitted JCL. The job ends with the status NOT SUBMITTED for reason JNSUB. The erroneous JCL remains on the spool, but does not affect other job executions except those that depend on the successful execution of this job. Values changed during job submission remain in effect only until CONTROL-M finishes submission of the job. Therefore, a change made to a global variable (via the %%SET control statement) affects only submission of that job and does not affect any other job submission or the value of the global variable in the external variable member.
System Variables
CONTROL-M System variables are predefined, commonly-used variables whose values are automatically updated and maintained by CONTROL-M. The System variable format is:
%%var
where: var Name of the System variable.
Each variable resolves to the corresponding system value. The length of the line is changed accordingly. For example:
//EJ%%ODATE JOB (0,l5, ... // EXEC ACCOUNTS,DAY=%%ODAY,MONTH=%%OMONTH
If the original scheduling date is June 3, 1998, the variables are resolved as follows:
//EJ980603 JOB (0,l5, ... // EXEC ACCOUNTS,DAY=03,MONTH=06
Non-Date System Variables

The following AutoEdit System variables are supported by CONTROL-M (in both JCL and in job scheduling definitions): %%. %%APPL %%BLANK %%BLANKn %%GROUP Concatenation symbol. Application to which the job belongs. Blank. Resolves to n blanks, where n is a number between 1 and 99. Group to which the job belongs.
55
JCL and AutoEdit Facility: System Variables Date System Variables
%%JOBNAME %%ORDERID %%OWNER %%RN %%TIME
Name of the submitted job. In a Group Entity SHOUT statement, it resolves to blanks. Unique job order ID under CONTROL-M (5 characters). Owner of the job, as specified in the scheduling definition. Run number (can exceed one for cyclic and rerun/restarted jobs). Time of day (format hhmmss).
%%$MEMNAME Name of the JCL member from which the job is submitted. %%$QNAME %%$SCHDLIB %%$SCHDTAB %%$SIGN Qname (unique identifier) of the monitor which submitted the job. Name of the scheduling library which contains the job scheduling definition of the job. Name of the scheduling table which contains the job scheduling definition of the job. 1-character ID of the computer on which the job is running. Common uses:
When the $ mask character is used as a generic indicator in

Quantitative resources. See parameter RESOURCE in Section 3 of this manual.
When assigning system affinity

(e.g., /*JOBPARM SYSAFF=CPU%%$SIGN). See Controlling the Target Computer by System Affinity later in this section. %%$TAG Name of the schedule tag by which the job was scheduled. If the Group scheduling table was forced, or if the job was scheduled based on basic scheduling criteria other than a schedule tag, this value resolves to blanks.
Date System Variables

Many System variables specify dates, or parts of dates, in various formats. Therefore, it is useful to understand the categories of dates with which CONTROL-M is concerned. Dates are divided into the categories listed below. For a description of these categories, see Date Definition Concepts in Section 1 of this manual:
Working Date System variables which specify working dates begin %%R (%%RDATE, %%RDAY, etc.). Original Scheduling Date System variables which specify original scheduling dates begin %%O (%%ODATE, %%ODAY, etc.).
System Date System variables which specify system dates have no special prefix other than %% (%%DATE, %%DAY, etc.).
Although these types of dates are resolved in Gregorian format, Julian formats can also be requested (%%JULDAY, %%OJULDAY and %%RJULDAY).
56
JCL and AutoEdit Facility: System Variables Date System Variables
The following date AutoEdit System variables are supported by CONTROL-M in JCL and in certain job scheduling definition parameters. (See AutoEdit Usage in the Job Scheduling Definition for more information.): %%$CENT %%DATE %%DAY %%MONTH %%YEAR %%WEEK %%WDAY First two digits in the current year (e.g., 19 in the year 1998). Current system date (format yymmdd). Current system day (format dd). Current system month (format mm). Current system year (format yy). Current week in the year (i.e., 01 52). Current system day of the week (Example: 1=Sunday, 2=Monday and 1 0=Saturday). First two digits of the year in which the job was originally scheduled. Original scheduling date of the job (format yymmdd). Original scheduling day of the job (format dd). Original scheduling month of the job (format mm). Original scheduling year of the job (format yy). Original scheduling week of the job (i.e., 01 52). Original scheduling day of the week of the job (format d; Example: 1 1=Sunday, 2=Monday and 0=Saturday). First two digits of the current working year. Current working date (format yymmdd). Current working day (format dd). Current working month (format mm). Current working year (format yy). Current working week (i.e., 01 52). Current working day of the week (format d; Example: 1=Sunday, 1 2=Monday and 0=Saturday). Current system day (Julian format jjj). Original scheduling day of the job in the year (Julian format jjj). Current working day of the year (Julian format jjj).
%%$OCENT %%ODATE %%ODAY %%OMONTH %%OYEAR %%OWEEK %%OWDAY
%%$RCENT %%RDATE %%RDAY %%RMONTH %%RYEAR %%RWEEK %%RWDAY
%%JULDAY %%OJULDAY %%RJULDAY

1
Start of the week at a site depends upon an IOA installation parameter which specifies whether 1=Sunday or 1=Monday. Your IOA administrator can tell you whether the week begins on Sunday or Monday at your site. The above reference assumes 1=Sunday, 2=Monday, 6=Friday, 0=Saturday.
57
JCL and AutoEdit Facility: System Variables Special System Variables
The following AutoEdit System variables, prefixed %%$, resolve to dates having 4-character years: %%$DATE %%$YEAR %%$ODATE %%$OYEAR %%$RDATE %%$RYEAR %%$JULDAY %%$OJULDAY %%$RJULDAY Current system date (format yyyymmdd). Current system year (format yyyy). Original scheduling date of the job (format yyyymmdd). Original scheduling year of the job (format yyyy). Current working date (format yyyymmdd). Current working year (format yyyy). Current system day (Julian format yyyyjjj). Original scheduling day of the job in the year (Julian format yyyyjjj). Current working day of the year (Julian format yyyyjjj).
Special System Variables

The following System variables can only be resolved after the job has ended and can therefore only be used in Post-Processing parameters (e.g., SHOUT, DO IFRERUN) of the job scheduling definition. These variables will contain a blank value if the job ends OK or if no step in the job was run. %%JOBCC %%MAXRC %%STEP Final status of the job. Highest return code in the job execution. For abended jobs, this variable resolves to blanks. Job program step and procedure step (if it is defined) which triggered the post-processing instruction.
The following System variable can only be resolved after job submission and can therefore only be used in Post-Processing parameters (e.g., SHOUT, DO IFRERUN) of the job scheduling definition. This variable will contain a blank value if the job ends OK or if no step in the job was run. %%JOBID JES job number.
58
JCL and AutoEdit Facility: User-Defined Variables
User-Defined Variables
The ability to specify user-defined variables provides additional flexibility. You can define your own variables and assign values to them. CONTROL-M will automatically edit the job stream accordingly. This facility is especially useful when it is necessary to share parameters or other information (e.g., tape numbers) among jobs. A user-defined variable can be any non-reserved alphanumeric string (characters @#$_ are also valid) beginning with %% (except strings beginning with %%$). CONTROL-M assumes all such strings to be user-defined variables. Note CONTROL-M assumes that any string beginning with %%$ is a system variable or function.
User-defined variables are defined as either local variables or global variables. Most user-defined variables are defined as local variables. Unlike System variables, which are predefined and which receive their values from the system at time of job submission, two steps are performed for utilizing user-defined variables:
The first step consists of specifying (defining) user-defined variables, usually within the JCL, instead of values that require manual modification. The second step consists of providing values to replace the user-defined variables at time of job submission. (Since these are not System variables whose values are provided by the system, the user must specify the appropriate values.)
User-defined variables can, however, take their values from system variables (e.g., %%SET %%VERSION = %%ODATE). Generally, a set of user-defined variables and the values to be assigned to them are specified in a member whose name is specified in a %%MEMSYM control statement. (The member should reside in the library specified in the accompanying %%LIBSYM statement. Control statements %%LIBSYM and %%MEMSYM are described later in this section.) Any number of such members can be defined and each can contain any number of user-defined variables. For example, the user may specify variable %%BRANCH_TAPE in a JCL statement:
//S001.INPUT DD VOL=SER=%%BRANCH_TAPE
In the %%MEMSYM member which assigns values, the user might specify:
%%BRANCH_TAPE=045673
Local variables can also be defined, and their values set, by a SET VAR or DO SET statement in the job scheduling definition, and/or by a %%SET statement in the JCL. Local variables are used only within the job stream. The value of a local variable can be changed within the job stream by CONTROL-M (via a SET VAR, DO SET or %%SET statement), but the changed value is kept only in memory for use during submission of that job stream. The value is not passed to another job stream and CONTROL-M does not change the value in %%MEMSYM.
59
JCL and AutoEdit Facility: Format of Variable Members
Global variables are a special type of user-defined variable intended for passing variable values from other IOA products to CONTROL-M. Global variables are defined, and their values set, in members defined via %%GLOBAL control statements (described later in this section). Other IOA products (e.g., CONTROL-O and CONTROL-B) can update the values of the variables in the global member, and CONTROL-M can then access the updated value. Local variable definitions are given precedence over global variable definitions. A globally set value of a variable can be overridden by a %%SET statement in the JCL, by a SET VAR or DO SET statement in the job scheduling definition, or by defining the same variable locally in a %%MEMSYM member. Multiple AutoEdit variables can be joined with each other and with constants (e.g., JOB_%%JOBID_ENDED_OK). This is discussed in more detail in Rules of Variable Resolution below.
Format of Variable Members

A variable member (referenced by %%GLOBAL or %%LIBSYM statements) must be a member in a partitioned dataset with a record length of 80. It can contain the following types of lines:
Remark line: Line starting with an asterisk (*) in column 1. Remark lines are not processed Assignment line: Line which assigns a value to a variable. The format is:
%%varname=value
To designate a null value, the value should be omitted. Example

* Last banking day in each month * %%LAST_BANKING_DAY_9801=980130 %%LAST_BANKING_DAY_9802=980227 %%LAST_BANKING_DAY_9803=980331 %%LAST_BANKING_DAY_9804=980430 %%LAST_BANKING_DAY_9805=980529 %%LAST_BANKING_DAY_9806=980630 %%LAST_BANKING_DAY_9807=980731 %%LAST_BANKING_DAY_9808=960831 %%LAST_BANKING_DAY_9809=960930 %%LAST_BANKING_DAY_9810=961030 %%LAST_BANKING_DAY_9811=961130 %%LAST_BANKING_DAY_9812=961230
5 10
JCL and AutoEdit Facility: Rules of Variable Resolution
Rules of Variable Resolution

By default, columns 1 72 of JCL lines are searched for variables which are then analyzed and resolved. If column 72 contains an asterisk (*), the active range for resolution is columns 1 71 (to support continuation lines). Multiple AutoEdit variables (and constants) can be joined together into a complex term. When a term contains multiple variables, those variables are resolved from right to left. The methods of joining multiple variables together are described below.
Two variables can be joined to form a single complex variable by linking them together (e.g., %%A%%B). Example 1 Given: Resolve: Explanation:
%%A=1, %%B=2, %%A2=100 %%A%%B
The process of resolution is as follows: Initial expression to resolve Resolve %%B Replace %%B with value 2
%%A%%B 2 %%A2
(%%A%%B partially resolves to a single variable %%A2) Resolve %%A2 Solution: Example 2 Given: Resolve: Solution: The day is the 3rd of the month.
//SYSBKP DD UNIT=TAPE,VOL=SER=%%BACKUP_TAPE_%%ODAY, %%A%%B resolves to 100 100
This statement partially resolves to:

//SYSBKP DD UNIT=TAPE,VOL=SER=%%BACKUP_TAPE_03,
%%BACKUP_TAPE_03 is a single user-defined variable. If the value of this variable is known to CONTROL-M as EE1022, the statement would fully resolve to:
//SYSBKP DD UNIT=TAPE,VOL=SER=EE1022,
5 11
Two variables can be concatenated into two distinct but joined variables by placing a period between them (e.g., %%A.%%B). Example 1 Given: Resolve: Explanation:
%%A=1, %%B=2, %%A2=100 %%A.%%B
The process of resolution is as follows: Initial expression to resolve Resolve %%B (The partially resolved variable now reads Resolve %%A (The partially resolved variable now reads Final resolution of the two values (based on the rule that two variables joined by a period resolve to a concatenated value)
%%A.%%B 2 %%A.2) 1 1.2) 12
Solution: Example 2
%%A.%%B resolves to 12
On the 4th of December, %%ODAY.%%OMONTH resolves to 0412 (If the expression had been written %%ODAY%%OMONTH (without the period), it would have partially resolved to %%ODAY12, which is a user-defined variable requiring further resolution.)
Two variables can be concatenated into two distinct variables joined by a period by placing two periods between them (e.g., %%A..%%B). Example 1 Given: Resolve: Explanation:
%%A=1, %%B=2, %%A2=100 %%A..%%B
The process of resolution is similar to the resolution of two variables joined by one period: Initial expression to resolve Resolve %%B (The partially resolved variable now reads Resolve %%A (The partially resolved variable now reads Final resolution of the two values (based on the rule that two variables joined by two periods resolve to two values joined by a period)
%%A..%%B 2 %%A..2) 1 1..2) 1.2
Solution:
%%A..%%B resolves to 1.2
5 12
Example 2 On the 4th of December, %%ODAY..%%OMONTH resolves to 04.12
A constant can be appended to a variable by prefixing the constant with the concatenation symbol %%. For example, in expression %%AA%%.UP, constant UP is appended to variable %%AA. Without symbol %%., the constant would be treated as part of the variable (e.g., expression %%AAUP consists of one variable). The %%. symbol is not required if the constant precedes the variable (e.g., UNIT%%AA) since the %% prefix of the variable differentiates it from the constant. Example Given: Resolve: Explanation:
%%MODE = PROD CTM.%%MODE%%.01.JCL
The process of resolution is as follows: Initial expression to resolve Resolve %%MODE

CTM.%%MODE%%.01.JCL PROD
(The partially resolved variable now reads CTM.PROD%%.01.JCL) Final resolution (based on the rule that symbol %%. joins a constant to a variable)
CTM.PROD01.JCL
Solution: Note
CTM.%%MODE%%.01.JCL resolves to CTM.PROD01.JCL
To separate a constant (JCL) from a variable (%%MODE) by a period, specifying the period is sufficient. For example: CTM.%%MODE.JCL would resolve to CTM.PROD.JCL.
5 13
JCL and AutoEdit Facility: Rules of Variable Resolution Order of Precedence for Multiple Value Assignments
Order of Precedence for Multiple Value Assignments

If a particular AutoEdit variable can receive a value from more than one source, an order of precedence is necessary to determine which of the possible values is assigned. The following chart indicates the order of precedence. The chart works as follows:
Each row in the chart represents a possible source of a value for a variable. In each column, a single pair of value sources (rows) are selected and compared for precedence: The source which takes precedence in the pair is identified by label P. The other source in the pair is identified by label O.
When many sources of value assignments are available for a variable, use the chart to compare those sources one pair at a time, as follows:
From the list of available sources for the particular variable, select any two sources and use the chart to eliminate the source of lower priority. The list now has one less source available. Repeat this process until only the source of highest priority remains. Paired Combinations of Value Sources O P O O P P P O O P P O O P P O P O
Source of Value Assignment SET VAR (Job Scheduling Definition) JCL SET (earlier) JCL SET (later) LIBSYM LIBSYM2 GLOBAL GLOBAL2 Notes
JCL SET can apply to an actual AutoEdit SET statement in the JCL or to AutoEdit SET statements embedded within an INCLIB member referenced in the JCL. LIBSYM represents a member specified in an earlier statement; LIBSYM2 represents a different member specified in a later statement. The same applies to GLOBAL and GLOBAL2 respectively.
If there are multiple value assignments for the same variable in the one member, the last assignment in that member is used for the above calculation.
5 14
JCL and AutoEdit Facility: Control Statements %%GLOBAL
Control Statements
Control statements define the AutoEdit environment and control AutoEdit processing. Control statements can appear anywhere in the JCL member to be submitted. When a control statement is detected in a JCL line (e.g., in a JCL remark statement), the line containing the control statement is submitted as part of the job. If the control statement appears in a non-JCL line (e.g., a line beginning without a // symbol), the control statement is resolved and the resolved value can be applied to subsequent JCL lines, but the control statement is not submitted as part of the job. Available control statements are discussed on the following pages.
%%GLOBAL
Control statement %%GLOBAL defines a member which contains a set of user-defined variables and values assigned either by other IOA products or manually by the user. Before job submission, the CONTROL-M monitor reads this member from the library referenced by DD statement DAGLOBAL in the CONTROL-M procedure. The content of the member is added to the user-defined variable environment of the job. You can specify more than one %%GLOBAL statement for a job. Each statement is added to the user-defined variable environment of the job. If CONTROL-M fails to access the variable member (member not found, etc.), the job is not submitted and a warning message is issued to the user who requested the job. The format of the %%GLOBAL control statement is:
//* %%GLOBAL memname
where: memname Example

//* %%GLOBAL TAPES //* %%GLOBAL CURRENCY
Valid member name of 1-8 characters.
%%GOTO and %%LABEL

Control statements %%GOTO and %%LABEL provide the AutoEdit facility with GO TO logic, permitting simple inclusion or exclusion of job steps, DD statements, input date, etc. The format of statements %%GOTO and %%LABEL is:
%%GOTO labelname %%LABEL labelname
The %%GOTO statement transfers control to the location in the program designated by a matching %%LABEL statement. The search for a matching %%LABEL labelname is only performed downward (i.e., loops are not supported). All statements between a %%GOTO statement and its matching %%LABEL statement are not processed (i.e., no statements are submitted and AutoEdit statements are not resolved). Statements %%GOTO and %%LABEL are generally used in conjunction with %%IF, %%ELSE, and %%ENDIF control statements. Examples at the end of this section demonstrate how these statements can be combined.
5 15
JCL and AutoEdit Facility: Control Statements %%IF, %%ELSE, %%ENDIF
%%IF, %%ELSE, %%ENDIF

Control statements %%IF, %%ELSE, and %%ENDIF provide the AutoEdit facility with Boolean IF logic capability. These statements, in conjunction with control statements %%GOTO and %%LABEL, permit branching based on submission time criteria. Job steps, DD statements, etc. are easily excluded or included. The format of statements %%IF, %%ELSE, %%ENDIF is:
%%IF conditional-expression statements [%%ELSE] statements %%ENDIF
where: conditional-expression Condition which determines whether or not the accompanying statements will be performed. If the condition is satisfied, the statements accompanying the %%IF statement are performed and the statements accompanying the %%ELSE statement (if specified) are not performed. If the condition is not satisfied, the statements accompanying the %%ELSE statement (if specified) are performed and the statements accompanying the %%IF statement are not performed. The format of a conditional-expression is:
operand operator operand
where: operand operator Any character string. It can contain AutoEdit terms. One of the valid comparison operators listed below.
Valid operators: Operator EQ NE GT GE LT LE statements Meaning is equal to is not equal to is greater than is greater than or equal to is less than is less than or equal to
Any statements specified in the JCL member, including AutoEdit statements, JCL statements and non-JCL statements.
5 16
JCL and AutoEdit Facility: Control Statements %%IF, %%ELSE, %%ENDIF
If an operand contains AutoEdit terms, they are resolved into a character string before the conditional expression is analyzed. An operand must not resolve to a null value (as in CLISTs). If it is possible that an operand will resolve to a null value, place a character before the first and second operands in a way that would not affect the comparison. For example, if %%A and/or %%C in the statement:
%%IF %%A GT %%C
might resolve to null, use a substitute expression such as:

%%IF B%%A GT B%%C
Operands are compared as character strings from left to right. For example: 91 is greater than 1000 (because 9 is greater than 1). An %%IF expression must be terminated with an %%ENDIF statement. The %%ELSE statement is optional. When the %%IF expression is true, all JCL statements (including non-AutoEdit statements) between the %%IF expression and its %%ELSE statement (or its matching %%ENDIF statement when no %%ELSE statement is present) are submitted by CONTROL-M provided that all AutoEdit variables are resolved. When the %%IF expression is not true and an %%ELSE statement exists, only statements between the %%ELSE statement and the matching %%ENDIF statement are submitted. %%IF statements can be nested. Example
%%IF expression %%IF expression statements . [ %%ELSE ] . %%ENDIF %%ELSE %%IF expression statements . [ %%ELSE ] . %%ENDIF %%ENDIF
An unlimited number of nested %%IF statements can be specified.
5 17
JCL and AutoEdit Facility: Control Statements %%INCLIB and %%INCMEM
%%INCLIB and %%INCMEM

Control statements %%INCLIB and %%INCMEM define a library and a member which are to be included in the current job stream. These statements are useful for inserting the following types of information into the JCL:
JCL statements and/or parameters to be passed to the JCL (e.g., sysin). AutoEdit control statements, including other %%INCLIB and %%INCMEM statements.
The format of the statement is:

%%INCLIB libname %%INCMEM memname
where: libname memname Valid dataset name (1-44 characters) of a cataloged partitioned dataset (library) with a record length of 80. Valid member name of 1-8 characters.
You can specify multiple %%INCLIB and %%INCMEM statements in a job. More than one job may contain identical %%INCLIB and %%INCMEM statements, permitting maintenance of common, standardized code. The %%INCMEM member is read by the CONTROL-M monitor just before job submission, and the members contents are submitted as part of the current job. As a result:
A member created by one job in the job stream can be used by a later job in the job stream. If a job in the job stream updates a member and the member is subsequently used by a later job in the job stream, the later job accesses the updated member.
If the %%INCLIB statement is resolved within the JCL, ensure that there are no unnecessary blank lines in the %%INCMEM member. If CONTROL-M fails to access the included member (member not found, etc.), the job is not submitted and a warning message is issued. Note If optional wish WM2354 has been applied at your site, you can indicate the number of times that a job should retry accessing the variable member. The number of retries and the interval between retries is specified in parameter DATA in member IOADFLTC of the IOA MAC library. An eight-digit value is specified for this parameter.
The first four digits indicate the number of CONTROL-M intervals to wait between
retries. The CONTROL-M interval is specified via installation parameter INTERVAL in member CTMPARM, and can be viewed via the following operator command:
F CONTROLM,SHOWPARM
The last four digits indicate the maximum number of retries before CONTROL-M
issues a message to the IOA log that the job was not submitted and assigns the job a status of NOTOK.
5 18
JCL and AutoEdit Facility: Control Statements %%LIBSYM and %%MEMSYM
%%LIBSYM and %%MEMSYM

Control statements %%LIBSYM and %%MEMSYM define a library and a member which contain a set of user-defined variables and their assigned values. The member is read by CONTROL-M before submission, and its content is added to the user-defined variable environment of the job. It is possible to specify more than one %%LIBSYM or %%MEMSYM statement for one job. Each statement is added to the user-defined variable environment of the specific job. If CONTROL-M fails to access the variable member (member not found, security constraints, etc.), the job is not submitted and a warning message is issued to the user who requested the job. Note If optional wish WM2354 has been applied at your site, you can indicate the number of times that a job should retry accessing the variable member. The number of retries and the interval between retries is specified in parameter DATA in member IOADFLTC of the IOA MAC library. An eight-digit value is specified for this parameter.
The first four digits indicate the number of CONTROL-M intervals to wait between
retries. The CONTROL-M interval is specified via installation parameter INTERVAL in member CTMPARM, and can be viewed via the following operator command:
F CONTROLM,SHOWPARM
The last four digits indicate the maximum number of retries before CONTROL-M
issues a message to the IOA log that the job was not submitted and assigns the job a status of NOTOK. The format of the statement is:
%%LIBSYM libname %%MEMSYM memname
where: libname memname Valid dataset name of 1-44 characters. It must be a cataloged partitioned dataset (library) with a record length of 80. Valid member name of 1-8 characters.
5 19
JCL and AutoEdit Facility: Control Statements %%RANGE
%%RANGE
Control statement %%RANGE limits the performance of AutoEdit functions to a specified column range. The contents of all columns outside the range remain unchanged. This statement is useful when values must be specified in specific columns and when not every AutoEdit statement should be resolved. The format of the statement is:
%%RANGE fromcol tocol
where: fromcol tocol First column in the range. Valid values are 180. The default (without a range statement) is 1. Last column in the range. Valid values are 180. tocol must be a value equal to or greater than fromcol. The default (without a range statement) is 72.
The %%RANGE statement can prevent the shifting of constants and variables which appear after an AutoEdit variable in the same line. By limiting AutoEdit resolution to a specified range, all constants/variables outside the specified range are kept in their original positions regardless of the length of the resolved variables. Each %%RANGE statement is valid until a new %%RANGE statement is specified. Note, however, that the placement of the subsequent %%RANGE statement must be within the column range of the preceding %%RANGE statement (or it will not be recognized as an AutoEdit statement). Note The minimum length of a %%RANGE statement with two-digit fromcol and tocol values is 12 characters. Therefore, a range of fewer than 12 columns should not be specified, or you will not be able to use a subsequent %%RANGE statement to expand the range back to the regular line length.
Example This example shows how statement %%RANGE affects the resolution of a line. In the original JCL, the %%RANGE statement affects the second occurrence of the AutoEdit variable, but not the first. In the submitted JCL, note the impact on the positioning of constant CONSTANT. The original JCL:
%%SET %%A_VERY_LONG_VARIABLE = XXX %%A_VERY_LONG_VARIABLE CONSTANT %%RANGE 1 25 %%A_VERY_LONG_VARIABLE CONSTANT
The submitted JCL:

%%SET %%A_VERY_LONG_VARIABLE = XXX XXX CONSTANT %%RANGE 1 25 XXX CONSTANT
5 20
JCL and AutoEdit Facility: Control Statements %%RESOLVE
%%RESOLVE
By default, CONTROL-M must resolve all AutoEdit terms in the JCL or the job is not submitted. This default can be overridden by specifying %%RESOLVE NO. Valid %%RESOLVE statements are: %%RESOLVE NO Try to resolve AutoEdit terms. If an AutoEdit term cannot be resolved, submit the job with the AutoEdit term as is. %%RESOLVE YES %%RESOLVE MUST %%RESOLVE (blank) If YES, MUST or blank is specified and a subsequent AutoEdit term cannot be resolved, the job is not submitted. %%RESOLVE OFF Do not try to resolve AutoEdit terms except for other %%RESOLVE statements. Submit the job with AutoEdit terms as is. Each %%RESOLVE statement remains in effect until the next %%RESOLVE statement in the JCL is encountered.
%%SET
Control statement %%SET sets values of user-defined variables. The statement can be placed in any part of the JCL stream. The format of the statement is:
%%SET %%varname = expression
where: varname expression Valid user-defined variable. Must resolve to a value according to the rules described in Rules of Variable Resolution earlier in this section or submission of the job is canceled (unless a %%RESOLVE NO control statement is specified). An expression can consist of a:
Value (e.g., 5) Variable (e.g., %%ODATE) Combination

Example 1
%%SET %%BACKUP_UNIT = TAPE
of values, variables, operators, (e.g., %%GENERATION_NUMBER %%PLUS 1)
functions,
etc.
User-defined variable %%BACKUP_UNIT is assigned the value TAPE. Example 2

%%SET %%BACKUP_UNIT_%%WDAY = EE%%OMONTH.%%ODAY
On Sunday the 24th of September, user-defined variable %%BACKUP_UNIT_1 is assigned the value EE0924.
5 21
JCL and AutoEdit Facility: Operators
Example 3
//* %%SET %%SCRATCH = %%SCRATCH %%PLUS 1 //SYSUT1 DD UNIT=TAPE,VOL=SER=EE%%SCRATCH,DISP=...
When the initial value of SCRATCH is 3017, the result in the submitted member is:
//* %%SET %%SCRATCH = 3017 %%PLUS 1 //SYSUT1 DD UNIT=TAPE,VOL=SER=EE3018,DISP=...
Operators
AutoEdit operators are used to add or subtract values from AutoEdit variables in the JCL. These operators can only be specified in a %%SET statement. Valid AutoEdit operators: %%PLUS %%MINUS Adds a value to an AutoEdit variable. Subtracts a value from an AutoEdit variable.
AutoEdit operators are generally used as follows:

%% SET variable = operand operator operand
where: operand operator Expression which resolves to a numeric value. %%PLUS or %%MINUS.
Only one operator can be specified in each %%SET statement. Example Increase the number of generations (%%GENERATION_NUMBER) by one:
// %%SET %%GENERATION_NUMBER = %%GENERATION_NUMBER %%PLUS 1
If the value of %%GENERATION_NUMBER was initially 1, it will be set to 2.
5 22
JCL and AutoEdit Facility: Functions %%$CALCDTE
Functions
AutoEdit functions perform operations on specified AutoEdit variables in the JCL. These functions can only be specified in %%SET statements. The following AutoEdit functions are supported by CONTROL-M:
%%$CALCDTE
Function %%$CALCDTE operates like function %%CALCDATE (described below), except that the initially specified date must be in (or resolve to) format yyyymmdd, the resulting date is in yyyymmdd format, and the maximum number of days to be added or subtracted is not limited to 366. Example
//* %%SET %%A = %%$CALCDTE %%$ODATE -1
If the original scheduling date is February 1, 1998: %%A is assigned a value of 19980131
%%$GREG
Function %%$GREG converts a Julian date (with a 4-character year) to a Gregorian date (with a 4-character year). The format of function %%$GREG is:
%%$GREG date
where: date Example

//* %%SET %%A = %%$GREG 1998196
Must be (or resolve to) a date in Julian format yyyyddd.
%%A is assigned a value of 19980715
%%$JULIAN
Function %%$JULIAN converts a Gregorian date (with a 4-character year) to a Julian date (with a 4-character year). The format of function %%$JULIAN is:
%%$JULIAN date
where: date Example

//* %%SET %%A = %%$JULIAN 19980715
Must be (or resolve to) a date in format yyyymmdd.
%%A will be assigned a value of 1998196
5 23
JCL and AutoEdit Facility: Functions %%$LEAP
%%$LEAP
%%$LEAP determines whether or not a specified Gregorian date (with a 4-character year) falls in a leap year. If the date is in a leap year, the variable resolves to 1. If the date is not in a leap year, the variable resolves to 0. The format of function %%$LEAP is:
%%$LEAP date
where: date Must be (or resolve to) a date in format yyyymmdd.
Leap years are years whose last two digits are evenly divisible by 4, excluding those years which are divisible by 100 but not by 400. Therefore, 2000 is a leap year but the years 2100, 2200 and 2300 are not. Example
//* %%SET %%A = %%$LEAP %%$ODATE
%%A will be assigned a value of 0 for dates in the year 1998.
%%$WCALC
Function %%$WCALC performs a shift from the specified date to a working date in the specified calendar, according to indicated instructions. The format of function %%$WCALC is:
%%$WCALC date instruction calendar
where: date instruction Must be (or resolve to) a date in format yyyymmdd. Shift instructions. Valid values: +n n > Shift to the next nth working date in the calendar. Shift to the previous nth working date in the calendar. If the specified date is not a current working date, shift to the next working date in the calendar. (If the specified date is a working date, do not shift.) If the specified date is not a current working date, shift to the previous working date in the calendar. (If the specified date is a working date, do not shift.)
<
calendar Example
Name of the calendar to check for working dates.
//* %%SET %%A = %%$WCALC 19980715 +1 EXCPTCAL //* %%SET %%A = %%$WCALC 19980715 > EXCPTCAL
If calendar EXCPTCAL (for 1998) contains consecutive working dates 07/14 and 07/21 in both %%SET statements, %%A will resolve to 19980721 If calendar EXCPTCAL (for 1998) contains consecutive working dates 07/15 and 07/20: In the first %%SET statement (with the +1), %%A will resolve to 19980721 In the second %%SET statement (with the >), %%A will resolve to 19980715
5 24
JCL and AutoEdit Facility: Functions %%$WEEK#
%%$WEEK#
Function %%$WEEK# calculates in which week of the year (1 53) a specified date with a 4-character year falls. The format of function %%$WEEK# is:
%%$WEEK# date
where: date Note Must be (or resolve to) a date in format yyyymmdd. The day of the week on which January 1st falls, and the site-defined start of week, are considered when the week number is calculated.
Example
//* %%SET %%A = %%$WEEK# 19980715
%%$WEEKDAY
%%$WEEKDAY calculates on which day of the week a specified date (with a 4-character year) falls. The resolved value is an integer from 1 through 6 or 0, where 1 corresponds to the first day of the week (Sunday or Monday, depending on the site-standard) and 0 corresponds to the last day of the week (Saturday or Sunday). The format of function %%$WEEKDAY is:
%%$WEEKDAY date
where: date Example

//* %%SET %%A = %%$WEEKDAY 19980715 %%A will be assigned a value of 4 (Wednesday)
Must be (or resolve to) a date in format yyyymmdd.
5 25
JCL and AutoEdit Facility: Functions %%CALCDATE
%%CALCDATE
Function %%CALCDATE performs date manipulation by adding or subtracting a specified number of days from a specified date. Note Function %%CALCDATE is supported for backward compatibility. To enhance year 2000 readiness and to avoid the limit of 366 on the number of days which can be added or subtracted, use function %%$CALCDTE.
The format of function %%CALCDATE is: %%CALCDATE date quantity where: date quantity Must be (or resolve to) a date in format yymmdd. Number (or numeric AutoEdit expression) of days (from 1 to 366) to add or subtract from the date.
Example
//* %%SET %%A = %%CALCDATE %%ODATE -1
If the original scheduling date is February 1, 1998:

%%SUBSTR
Function %%SUBSTR extracts a substring from a string. The format of function %%SUBSTR is:
%%SUBSTR string startpos length
where: string startpos length String from which the substring will be extracted. Character position in the original string from which the extraction will begin. Number of characters to extract.
A new string is created composed of the characters extracted from the original string. startpos and length must be a numeric value or AutoEdit expression which is greater than zero. If startpos + length 1 is greater than the string length, submission of the member is stopped. Example
//* %%SET %%A = %%$CALCDTE %%$ODATE -1 //* %%SET %%AMON = %%SUBSTR %%A 5 2
On July 1, 1998:
%%A will be assigned a value of 980630 %%AMON will be assigned a value of 06
5 26
JCL and AutoEdit Facility: Testing AutoEdit Syntax
Testing AutoEdit Syntax

When CONTROL-M detects an AutoEdit syntax error in a JCL member during submission, the submission is canceled by CONTROL-M. Therefore, it is essential to check the syntax of AutoEdit statements while the member is being prepared. Furthermore, when the syntax is correct, you may want to verify that the AutoEdit statements return the desired results. For example, you may want to check that you specified the correct AutoEdit date variables for a job that performs end-of-year processing. Utility CTMAESIM tests AutoEdit syntax and JCL setup. This utility simulates the actions of the CONTROL-M submission mechanism (which performs AutoEdit processing and JCL setup) and produces a printed report of the process. Utility CTMAESIM can operate in either JCL Library mode or Scheduling Library mode:
In JCL Library mode, the utility checks the AutoEdit statements in the jobs JCL. In Scheduling Library mode, the utility not only checks the AutoEdit statements in the jobs JCL, it also checks the impact that SET VAR statements in the job scheduling definition have on the jobs JCL.
The utility enables system programmers to check the operation of CONTROL-M submission exit CTMX002 without affecting production. Utility CTMAESIM can be activated via a batch procedure or the Online facility, as follows: Batch procedure Online facility Via procedure CTMAESIM Via option M2 in the Online Utilities menu or via CLIST CTMCAES
The utility requires specification of various parameter statements which determine how the simulation will work and which provide necessary information for the simulation. Although the simulation works in much the same manner whether activated via a batch procedure or online, the following differences depend on the method of activation:
Batch activation allows specification of multiple sets of parameter statements. Online activation allows specification of only one set of parameter statements. Batch activation allows inclusion or omission of parameter RDR=INTRDR (described below). This parameter cannot be specified online. Command JSCAN (available only at sites where JOB/SCAN is installed) can only be specified if the utility is activated via the Online Utilities menu. It cannot be specified if the utility is activated via batch or via CLIST CTMCAES. Character masking is not supported in the Online utility. In the batch utility, character masking is supported for the member name in JCL Library mode, and for the job name in Scheduling Library mode. Valid mask characters are: * ? Represents any number of characters (including no characters) Represents any one character
5 27
JCL and AutoEdit Facility: AutoEdit Usage in the Job Scheduling Definition
Parameter SETVAR, which can be specified outside the job scheduling definition, is supported in batch mode only. However, SET VAR statements in the job scheduling definition can be checked in both online and batch mode. Parameter PARAMETER LIBRARY is specified only in the Online utility. In batch mode, this library is referenced by DD statement DAGLOBAL.
In addition, depending on the command type specified in a parameter statement, the resulting JCL lines can also be written to the output file referenced by DD statement DASUBMIT. When the JCL is written to the output file referenced by DD statement DASUBMIT, the output file can be routed to an internal reader by specifying parameter RDR=INTRDR in the EXEC statement. In this case, DD statement DASUBMIT is allocated as SYSOUT=(class,INTRDR) and the job is submitted. Submission of the job enables the JCL to be checked by MVSs JCL checking mechanism. Note DD statement DASUBMIT can also be used by the AutoEdit Simulation facility to submit jobs for execution in emergency situations (e.g., the CONTROL-M monitor is inoperative due to a severe technical problem).
When activated via ISPF, the utilitys functioning is similar to its functioning when activated from batch with parameter RDR=INTRDR specified. Utility CTMAESIM, as activated from the Online facility, is described in Section 2 of this manual. Utility CTMAESIM, as activated via a batch procedure, is described in Section 6 of this manual.
AutoEdit Usage in the Job Scheduling Definition

Certain AutoEdit components can be used in job scheduling definitions. In job scheduling definitions, AutoEdit components in certain statements (SET VAR and DO SET) directly affect JCL. In other statements (SYSOUT/DO SYSOUT, SHOUT/DO SHOUT, MEMLIB and OVERLIB) they do not affect the JCL. In the job scheduling definition, AutoEdit components can be specified in the following parameters:
SET VAR and DO SET statements These two job scheduling definition statements and the %%SET control statements are used to assign values to user-defined variables in the JCL. Example In this example, AutoEdit statements in the job scheduling definition and the JCL allocate space for the job. If the job abends due to insufficient space, the AutoEdit statements adjust the allocated space and rerun or restart the job. The following step in the jobs JCL sets the quantity of available space to five units of whatever type (track or cylinder) is specified in the job scheduling definition.
//STEP10 EXEC PGM=MYPGM //OUTFILE DD DSN=NEWFILE,DISP=(NEW,CATLG,DELETE), // SPACE=(%%SPACE_TYPE,5),UNIT=SYSDA
5 28
JCL and AutoEdit Facility: AutoEdit Usage in the Job Scheduling Definition
The job scheduling definition contains the following SET VAR statement which sets the space type to track:
SET VAR %%SPACE_TYPE = TRK
In this case, the second line in the above DD statement resolves to:
// SPACE=(TRK,5),UNIT=SYSDA
The job scheduling definition also contains the following statements which are activated if the job abends due of lack of space (code S*37). These statements change the space type to cylinder (which will provide enough space), and rerun the job. (If CONTROL-R is active, the job will be restarted from the abended step.)
ON STEP STEP10 CODES S*37 DO SET %%SPACE_TYPE = CYL [DO IFRERUN FROM $ABEND] DO RERUN
===> If CONTROL-R is active
If the job abends as above, the second line of the earlier JCL DD statement resolves to:
// SPACE=(CYL,5),UNIT=SYSDA
when the job is submitted for rerun (or restart).
SYSOUT/DO SYSOUT File names for SYSOUT/DO SYSOUT handling can be specified using AutoEdit variables whenever SYSOUT option F (copy to file or sysout archiving) is specified. For example:
SYSOUT OP F PRM GPL.%%JOBNAME.D%%ODATE.%%JOBID.T%%TIME
SHOUT/DO SHOUT AutoEdit variables can be used in shouted messages. For example:
MSG JCL ERROR IN JOB %%JOBID %%STEP
MEMLIB/OVERLIB AutoEdit variables can be used in the MEMLIB and OVERLIB fields to specify the appropriate library. For example:
OVERLIB CTM.LIB.JCL.OVER%%ODATE
5 29
JCL and AutoEdit Facility: Examples Date Variables
Examples
Date Variables
Original Scheduling %%ODATE %%ODAY %%OMONTH %%OYEAR %%OWDAY %%OJULDAY The original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //STEP01 EXEC PDUPDATE //SYSIN DD * %%DATE //
Current Working %%RDATE %%RDAY %%RMONTH %%RYEAR %%RWDAY %%RJULDAY
Computer %%DATE %%DAY %%MONTH %%YEAR %%WDAY %%JULDAY
Format yymmdd dd mm yy n (0-6) jjj
The JCL submitted on June 6, 1998:

//PDPA0001 JOB (......),BILL,CLASS=A //STEP01 EXEC PDUPDATE //SYSIN DD * 980606 //
5 30
JCL and AutoEdit Facility: Examples ODATE, RDATE and DATE Usage
ODATE, RDATE and DATE Usage

The original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A .... //STEP02 EXEC PDPRINT,BUSDATE=%%ODATE //SYSIN DD * EXAMPLE-RDATE=%%RDATE EXAMPLE-DATE=%%DATE //
On July 24th, we need to run the 22nd, 23rd, and 24th (of the same job) because of delays. On the Active Jobs file we can find three job orders:
PDPA0001 of 980722 PDPA0001 of 980723 PDPA0001 of 980724
The job of the 22nd is submitted on July 24th at 2300. The result is:
//PDPA0001 JOB (......),BILL,CLASS=A .... //STEP02 EXEC PDPRINT,BUSDATE=980722 //SYSIN DD * EXAMPLE-RDATE=980724 EXAMPLE-DATE=980724 //
The job of the 23rd is submitted on July 25th at 0025. The result is:
The job of the 24th is submitted on July 25th, 1998 at 0300. The result is:
5 31
JCL and AutoEdit Facility: Examples How to Obtain Date Formats 1
How to Obtain Date Formats 1

Format ddmmyy: %%ODAY.%%OMONTH.%%OYEAR Lets follow the variable substitution by stages for June 24, 1998:
%%ODAY.%%OMONTH.98 %%ODAY.06.98 %%ODAY.0698 24.0698 240698
Remember
Variable substitution is performed from right to left. A period (.) between two AutoEdit variables will be omitted.

Format dd mmm yy (where mmm is the month in character format): The original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //* %%GLOBAL CHARMON //STEP02 EXEC PDPRT3 //SYSIN DD * %%ODAY %%MONTH_IN_CHAR_%%OMONTH %%OYEAR //
Member CHARMON (in the CONTROL-M Global library) contains:

* * MONTHS IN CHAR FORMAT * %%MONTH_IN_CHAR_01 = JAN %%MONTH_IN_CHAR_02 = FEB %%MONTH_IN_CHAR_03 = MAR . . %%MONTH_IN_CHAR_12 = DEC
The symbols substitution by stages:

%%ODAY %%ODAY %%ODAY 24 JUN %%MONTH_IN_CHAR_%%OMONTH 98 %%MONTH_IN_CHAR_06 98 JUN 98 98
The submitted member:

//PDPA0001 JOB (......),BILL,CLASS=A //* %%GLOBAL CHARMON //STEP02 EXEC PDPRT3 //SYSIN DD * 24 JUN 98 //
5 32
JCL and AutoEdit Facility: Examples How to Obtain Date Formats 3

Format ddmmmyy (where mmm is the month in character format): According to the preceding example, we might try the following original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //* %%GLOBAL CHARMON //STEP02 EXEC PDPRT3 //SYSIN DD * %%ODAY.%%MONTH_IN_CHAR_%%OMONTH.%%OYEAR //
Variable substitution by stages would proceed as follows:

%%ODAY %%MONTH_IN_CHAR_%%OMONTH.98 %%ODAY %%MONTH_IN_CHAR_06.98 %%ODAY %%MONTH_IN_CHAR_0698
However, this will result in the following error: Symbol %%MONTH_IN_CHAR_0698 is not resolved. This error would not have occurred had we tried the following original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //* %%GLOBAL CHARMON //* %%SET %%A = %%MONTH_IN_CHAR_%%OMONTH //STEP02 EXEC PDPRT3 //SYSIN DD * %%ODAY.%%A.%%OYEAR //
5 33
JCL and AutoEdit Facility: Examples How to Obtain the Previous Months Last Business Date
How to Obtain the Previous Months Last Business Date

//PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.SYMBOLS %%MEMSYM LBUSMON //STEP02 EXEC PDPRT3 //SYSIN DD * %%LAST_BUSINESS_DATE_IN_PREV_MONTH_OF_%%OMONTH.%%OYEAR //
Member LBUSMON in library CTM.LIB.SYMBOLS contains:

* * LAST BUSINESS DATE IN THE PREVIOUS MONTH * %%LAST_BUSINESS_DATE_IN_PREV_MONTH_OF_0198 %%LAST_BUSINESS_DATE_IN_PREV_MONTH_OF_0298 . %%LAST_BUSINESS_DATE_IN_PREV_MONTH_OF_0698 . %%LAST_BUSINESS_DATE_IN_PREV_MONTH_OF_1298 . .
= 971230 = 980130 = 980529 = 981130
Variable substitution by stages (during June 1998):

%%LAST_BUSINESS_DATE_IN_PREV_MONTH_OF_%%OMONTH.98 %%LAST_BUSINESS_DATE_IN_PREV_MONTH_OF_06.98 %%LAST_BUSINESS_DATE_IN_PREV_MONTH_OF_0698 980529
5 34
JCL and AutoEdit Facility: Examples Automatic Job Order for the Next Day
Automatic Job Order for the Next Day

In many data centers it is necessary to run certain jobs ahead of time on a regular basis (e.g., run today with the business date of tomorrow). The %%$CALCDTE and %%SUBSTR functions can be used to permit automatic scheduling of such jobs on a daily basis by the CONTROL-M monitor. (The output is in mmddyy format.)
//TOMDAILY JOB (....),BILL,CLASS=A //* %%SET %%A = %%$CALCDTE %%$ODATE +1 //* %%SET %%DD = %%SUBSTR %%A 7 2 //* %%SET %%MM = %%SUBSTR %%A 5 2 //* %%SET %%YY = %%SUBSTR %%A 3 2 //STEP01 EXEC PGM=IKJEFT01,REGION=1000K,DYNAMNBR=30 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * CTMCJOBS SCHEDLIB(CTM.LIB.SCHEDULE) TABLE(SDP00) ODAT(%%MM.%%DD.%%YY) //
AutoEdit functions %%$CALCDTE and %%SUBSTR can be used for any date calculation which is needed in a production environment.
5 35
JCL and AutoEdit Facility: Examples Tape Clearance System Stage 1
Tape Clearance System Stage 1

The original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.SYMBOLS %%MEMSYM TAPES //STEP02 EXEC PDINP3 //S001.INPUT DD VOL=SER=%%FEDERAL_BANK_TAPE //
The member TAPES in library CTM.LIB.SYMBOLS contains:

* * EXTERNAL TAPES LIST * %%FEDERAL_BANK_TAPE = 045673 %%IRS_TAPE = XXXXX %%STOCK_EXCHANGE_TAPE = YYYYYY . .
The submitted JCL:

//PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.SYMBOLS %%MEMSYM TAPES //STEP02 EXEC PDINP3 //S001.INPUT DD VOL=SER=045673 //
The use of a central member for all external tapes is a very simple management tool. The minute a tape arrives, its number is typed in the member, and the tape is sent to the computer room. There is no need to keep the tapes at hand on the schedulers table until the job is submitted. The function of receiving tapes can be centralized, controlled, and independent of the production process.
5 36
JCL and AutoEdit Facility: Examples Tape Clearance System Stage 2
Tape Clearance System Stage 2

The example provided on the previous page has one basic weakness. It cannot handle delays. If a certain job does not run one day, and on the next day it must be run twice (once for each execution day), there is a danger of overriding the tape number in the control member. To solve this problem, lets improve our tape clearance system.
//PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.SYMBOLS %%MEMSYM TAPE%%OMONTH.%%ODAY //STEP02 EXEC PDINP3 //S001.INPUT DD VOL=SER=%%FEDERAL_BANK_TAPE //
Member TAPE0714 in library CTM.LIB.SYMBOLS contains:

: * * EXTERNAL TAPES LIST * %%FEDERAL_BANK_TAPE = 045673 %%IRS_TAPE = XXXXX %%STOCK_EXCHANGE_TAPE = YYYYYY . .
There are other advantages:
The ability to roll back several dates without losing the dynamic parameters. Complete documentation of a tapes usage.
Use a CONTROL-M job to automatically create a member, TAPEmmdd, for each scheduling date, based on a master copy. For example:
// EXEC PGM=IEBCOPY . //SYSIN DD * C I=IN, O=OUT S M=((TAPES,TAPE%%OMONTH.%%ODAY))
5 37
JCL and AutoEdit Facility: Examples Tape Management System
Tape Management System

The original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.TAPES %%MEMSYM PDTAPES //STEP02 EXEC PDBKP3 //S001.OUTPUT DD VOL=SER=%%PDTAPE_0001_%%OWDAY //
Member PDTAPES in library CTM.LIB.TAPES contains:

* * TAPES OF DP APPLICATION * %%PDTAPE_0001_1 = 045673 %%PDTAPE_0001_2 = 045683 %%PDTAPE_0001_3 = 045677 %%PDTAPE_0001_4 = 043433 %%PDTAPE_0001_5 = 045543 %%PDTAPE_0001_6 = 045556 %%PDTAPE_0001_7 = 045666 * %%PDTAPE_0010_1 = 046600
We have created a cycle of seven tapes to be used by this application.
Dynamic Job Name

The required format:
//PDPAddxx JOB (......),BILL,CLASS=A
where: dd is the business day of the month, and xx varies according to the job in the application. The solution:
//PDPA%%ODAY%%.xx JOB (......),BILL,CLASS=A
5 38
JCL and AutoEdit Facility: Examples Controlling the Target Computer by Class
Controlling the Target Computer by Class

CONTROL-M can dynamically decide to which computer to send a job. The following examples demonstrate the relation between CONTROL-M resource acquisition parameters and local JCL standards implementation. Note This example assumes that a $ generic resource was specified in the job scheduling definition. (For more information, see Resource Allocation in Multi-CPU Environments in the description of parameter RESOURCE in Section 3 of the CONTROL-M User Manual.)
//* %%GLOBAL CLASSES //PDPA0001JOB(.....),BILL,CLASS=%%FAST_CLASS_OF_%%$SIGN
Member CLASSES in the CONTROL-M Global library contains:

* * DEFINITIONS OF CLASSES IN THE COMPUTERS * %%FAST_CLASS_OF_1 = A %%FAST_CLASS_OF_2 = D %%FAST_CLASS_OF_3 = K %%SLOW_CLASS_OF_1 = W . .
Controlling the Target Computer by System Affinity

Note This example assumes that a $ generic resource was specified in the job scheduling definition. (For more information, see Resource Allocation in Multi-CPU Environments in the description of parameter RESOURCE in Section 3 of the CONTROL-M User Manual.)
//* %%GLOBAL SYSAFF //PDPA0001 JOB (......),BILL,CLASS=A /*J SYSAFF=%%NAME_OF_COMPUTER_%%$SIGN
Member SYSAFF in the CONTROL-M Global library contains:

* * NAMES OF THE COMPUTERS * %%NAME_OF_COMPUTER_1 = SYSA %%NAME_OF_COMPUTER_2 = SYSB %%NAME_OF_COMPUTER_3 = TEST
The submitted JCL (for CPU ID 2):

//* %%GLOBAL SYSAFF //PDPA0001 JOB (......),BILL,CLASS=A /*J SYSAFF=SYSB
5 39
JCL and AutoEdit Facility: Examples %%BLANKn Statement
%%BLANKn Statement
A program expects to receive the day of the week and the time of day as structured input:
Day of the week in column 1 Time of day in column 11
The original JCL:

//PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.SYMBOLS %%MEMSYM DAYTIME .... //STEP02 EXEC PDPRT3 //SYSIN DD * %%H%%OWDAY%%.%%TIME //
Member DAYTIME in library CTM.LIB.SYMBOLS contains the following AutoEdit user symbols:
%%H1 = SUNDAY%%BLANK4 %%H2 = MONDAY%%BLANK4 %%H3 = TUESDAY%%BLANK3 %%H4 = WEDNESDAY%%BLANK1 %%H5 = THURSDAY%%BLANK2 %%H6 = FRIDAY%%BLANK4 %%H0 = SATURDAY%%BLANK2 Variable substitution by stages: %%H%%OWDAY%%.%%TIME %%H%%OWDAY.085300 %%H1.085300 SUNDAY 085300 The submitted JCL: //PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.SYMBOLS %%MEMSYM DAYTIME .... //STEP02 EXEC PDPRT3 //SYSIN DD * SUNDAY 085300 //
5 40
JCL and AutoEdit Facility: Examples %%RANGE Statement
%%RANGE Statement
The original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.SYMBOLS %%MEMSYM LBUSMON //STEP02 EXEC PDPRT3 //* + + + + //SYSIN DD * %%LAST_BUSINESS_DATE_IN_%%OMONTH REPORT1 //
The constant REPORT should be in column 40. The submitted JCL:

//PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.SYMBOLS %%MEMSYM LBUSMON //STEP02 EXEC PDPRT3 //* + + + + //SYSIN DD * 030498 REPORT1 //
The correct solution:

//PDPA0001 JOB (......),BILL,CLASS=A //* %%LIBSYM CTM.LIB.SYMBOLS %%MEMSYM LBUSMON //STEP02 EXEC PDPRT3 //* + + + + //* %%RANGE 1 39 //SYSIN DD * %%LAST_BUSINESS_DATE_IN_%%OMONTH REPORT1 //
5 41
JCL and AutoEdit Facility: Examples SYSIN Parameter Containing %%
SYSIN Parameter Containing %%

Disabling AutoEdit Resolution The original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //STEP02 EXEC PDPRT3 //SYSIN DD * %%VAR // EXEC ... //
Do not resolve the AutoEdit variable on this line.

PARM=%%ODATE
The solution:
//PDPA0001 JOB (......),BILL,CLASS=A //STEP02 EXEC PDPRT3 //SYSIN DD * %%RESOLVE NO %%VAR %%RESOLVE YES // EXEC ... //
Do not resolve the AutoEdit variable on this line.

PARM=%%ODATE
If RESOLVE=NO, the line is submitted as is if an AutoEdit term cannot be resolved.
%%INCLIB and %%INCMEM Statements

The original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //STEP01 EXEC PDPRPT1 .... //* %%INCLIB CTM.LIB.COMJCL %%INCMEM PDPRPT2 //
Member PDPRPT2 in library CTM.LIB.COMJCL contains:

//STEP02 //SYSIN %%DATE EXEC PDPRPT2 DD *
The submitted JCL (on June 6, 1998):

//PDPA0001 JOB (......),BILL,CLASS=A //STEP01 EXEC PDPRPT1 .... //* %%INCLIB CTM.LIB.COMJCL %%INCMEM PDPRPT2 //STEP02 EXEC PDPRPT2 //SYSIN DD * 980606 //
5 42
JCL and AutoEdit Facility: Examples Boolean IF Logic
Boolean IF Logic
Example 1 This example illustrates CONTROL-Ms ability to perform Boolean IF logic. The original JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //* //* %%IF %%TIME LT 120000 //* %%SET %%PGMA = MORNPGM //* %%ELSE //* %%SET %%PGMA = AFTPGM //* %%ENDIF //* //STEP01 EXEC PGM=%%PGMA ... //
The submitted JCL at 1:00 p.m.

//PDPA0001 JOB (......),BILL,CLASS=A // //* %%IF %%TIME LT 120000 //* %%ELSE //* %%SET %%PGMA = AFTPGM //* %%ENDIF // //STEP01 EXEC PGM=AFTPGM ... //
The %%IF expression is not true since it is past 12:00 noon; therefore, the statements following %%ELSE are executed. The program executed in STEP01 is AFTPGM.
5 43
JCL and AutoEdit Facility: Examples Boolean IF Logic
Example 2 This example illustrates the use of CONTROL-Ms conditional logic in conjunction with CONTROL-M INCLUDE and GO TO logic.
//PDPA0001 JOB (......),BILL,CLASS=A //* //* %%IF %%WDAY NE 1 //* %%GOTO RUN_DAILY //* %%ELSE //* %%INCLIB CTM.LIB.COMJCL %%INCMEM MONTHLY //* %%ENDIF //* //* %%LABEL RUN_DAILY //STEPDAI EXEC PGM=DAILY ... //
Member MONTHLY in library CTM.LIB.COMJCL:

//STEPMON ... EXEC PGM=MONTHLY
On the first day of the month both the DAILY and MONTHLY programs will run. The submitted JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //* //* %%IF 1 NE 1 //* %%ELSE //* %%INCLIB CTM.LIB.COMJCL %%INCMEM MONTHLY //STEPMON EXEC PGM=MONTHLY ... //* %%ENDIF //* //* %%LABEL RUN_DAILY //STEPDAI EXEC PGM=DAILY ... //
On any other day of the month only the DAILY program will run. The submitted JCL:
//PDPA0001 JOB (......),BILL,CLASS=A //* //* %%IF 2 NE 1 //* %% GOTO RUN_DAILY //* %%ELSE //* %%ENDIF //* //* %%LABEL RUN_DAILY //STEPDAI EXEC PGM=DAILY ... //
5 44
Section 6: Implementation and Maintenance

General ...........................................................................................................................................6-1 Implementation ............................................................................................................................6-1 Job Ordering via New Day Processing ......................................................................................6-2 Overview ................................................................................................................................6-2 Sample New Day Processing ................................................................................................6-4 Implementing New Day Processing .....................................................................................6-7 Programs Called During New Day Processing ..................................................................6-12 Alternative Methods of Job Ordering ......................................................................................6-14 Job Ordering Via CLIST CTMCJOBS................................................................................6-15 Job Ordering Via Quick Submit Command CTMQSB ......................................................6-16 Ad Hoc Job Ordering From Special Environments: CTMAJO .........................................6-17 Manual Conditions File and Maybe Jobs ................................................................................6-19 Loading the Manual Conditions File..................................................................................6-19 Using the Manual Conditions File .....................................................................................6-19 Handling Manual Conditions .............................................................................................6-20 Handling Unscheduled Conditions.....................................................................................6-20 Handling Maybe Dependencies ..........................................................................................6-21 Maybe Jobs in Group Scheduling Tables ...........................................................................6-21 CONTROL-M/WorkLoad Considerations................................................................................6-23 Job-Related Considerations for Pipes.................................................................................6-23 System-Related Considerations..........................................................................................6-24 CONNECT DIRECT Support ..................................................................................................6-25 REXX Procedure IOACDDR: Dataset Event Definition ...................................................6-25 Event List Screen ................................................................................................................6-26 Event Definition Screen ......................................................................................................6-27 Parameter Prompting Facilities ..............................................................................................6-29 Parameter Prompting Facility Type 1.............................................................................6-29 Parameter Prompting Facility Type 2.............................................................................6-35 Utilities ........................................................................................................................................ 6-43 CTMAESIM Test AutoEdit Syntax ......................................................................................6-45 CTMBLDAE Build AutoEdit Symbols Member...................................................................6-49 CTMBLT Create Scheduling Tables.....................................................................................6-54 CTMJOB Order Jobs to the Active Jobs File .......................................................................6-71 CTMRCAL Produce a Job Plan Report ................................................................................6-76 CTMRELRS Release Quantitative Resources .....................................................................6-78
CTMTBUPD Update Job Scheduling Tables ..................................................................... 6-80 CTMXRF Create Cross Reference Reports.......................................................................... 6-91 IOACND Handle Condition/Resource Utilization............................................................... 6-97 Operations Guide .................................................................................................................... 6-100 Activating the CONTROL-M Monitor .................................................................................. 6-100 Shutting Down the CONTROL-M Monitor .......................................................................... 6-100 Modifying the CONTROL-M Sleeping Interval ................................................................... 6-101 New Day Procedure Flow ...................................................................................................... 6-101 Started Tasks ......................................................................................................................... 6-102 CONTROL-M Errors ............................................................................................................. 6-103 CONTROL-M Monitor and JES............................................................................................ 6-103 Cases of JES Malfunction ................................................................................................ 6-103 Special Considerations ..................................................................................................... 6-103 Stopping CMEM Before JES Is Stopped ......................................................................... 6-105 Managing the CMEM Facility .............................................................................................. 6-106 CMEM and CONTROL-O ................................................................................................ 6-106 Activating the CONTROL-M Event Manager (CMEM) Facility ................................... 6-106 Deactivating the CMEM Facility..................................................................................... 6-106 Replacing an Active CMEM Monitor............................................................................... 6-107 Loading of Rules ............................................................................................................... 6-107 Deleting (Deactivating) an Active Rule Table................................................................. 6-109 Displaying Active Rules ................................................................................................... 6-109 Controlling CMEM Rule Operation Mode....................................................................... 6-110 Modifying the CMEM Sleeping Interval ......................................................................... 6-110 Refreshing the CMEM Security Cache............................................................................ 6-111
Modifying the CONTROL-M Resources Acquisition Exit ....................................................6-111 Loading a New Destination Table .........................................................................................6-112 Performing Deadline Scheduling Calculations.....................................................................6-112 Issuing Operator Commands Via a Job or STC....................................................................6-113 IOA Online Monitor................................................................................................................6-113 General...............................................................................................................................6-113 Activating the IOA Online Monitor..................................................................................6-114 Deactivating the IOA Online Monitor..............................................................................6-114 Controlling the Online Monitor(s) ....................................................................................6-115
Implementation and Maintenance: General Job Ordering via New Day Processing
General
This section provides details required for implementation and maintenance of CONTROL-M by the user and operator. For implementation and maintenance of CONTROL-M by the IOA administrator, see Section 3 of the IOA Administrator Guide. This section is divided into the following main parts: Implementation Concepts and hints for successful implementation of CONTROL-M. Topics in this section require familiarity with background information presented in Section 1 of this manual, and familiarity with relevant information presented in other sections. Detailed descriptions of utilities which are used to maintain the CONTROL-M environment. A brief description of all utilities available with CONTROL-M is also provided. Many of these utilities are described in Section 9 of the IOA Administrator Guide. Operations Guide Information, instructions and commands used to interact with the mainframe environment in which CONTROL-M operates.
Utilities
Implementation
The following implementation concepts and instructions are discussed in this section of the manual:
Job Ordering via New Day Processing Alternative Methods of Job Ordering Manual Conditions List and Maybe Jobs CONTROL-M/WorkLoad Considerations CONNECT DIRECT Support (formerly called NDM Support) Parameter Prompting Facilities
61
Implementation and Maintenance: Implementation Job Ordering via New Day Processing
Job Ordering via New Day Processing

Overview
The CONTROL-M monitor is usually activated as a started task and remains active 24 hours a day. At a set time each day (defined via installation parameters), New Day processing is performed by the CONTROL-M monitor. New Day processing consists of both automatic cleanup from the previous days job ordering and automatic ordering of jobs for the new day. The main components related to New Day processing are:
Scheduling tables and job scheduling definitions New Day procedure and User Daily jobs Date Control records Active Jobs file
New Day processing is automated via the New Day procedure (called the General Daily prior to IOA Release 5.0.0) and User Daily jobs. The main purpose of the New Day procedure and User Daily jobs is to call programs that:
Scan scheduling tables to select jobs for scheduling. Schedule the selected jobs (i.e., place copies of the selected job scheduling definitions as job orders in the Active Jobs file).
Both the New Day procedure and each User Daily job must have its own Date Control record. A Date Control record is a member in the CONTROL-M PARM library in which relevant date information is placed during New Day processing. This date information is used to manage job orders. Selection of jobs is based on the Date Control record, the current date, and the Basic Scheduling parameters of the jobs in the scheduling tables. Each time the User Daily job is run, the current working date is placed in the Date Control record. The Basic Scheduling parameters of each job in the scheduling table are checked against this date to see if the job should be placed in the Active Jobs file.
62
New Day processing generally works as follows:
The New Day procedure is performed at the predefined time each day. The New Day procedure: Schedules User Daily jobs. Schedules maintenance jobs. These jobs call programs which perform cleanup after the previous days processing. If a cyclic job is executing at the time the New Day procedure is run, the New Day procedure changes the job to a non-cyclic job and handles the job accordingly. If a job which was not submitted on its original scheduling date contains > in its TIME UNTIL field, when the New Day procedure is next run, the procedure deletes the > and TIME FROM specification from the job order. This makes the job immediately eligible for execution.
Notes
If CONTROL-R is installed and the History Jobs file is active, jobs deleted from the Active Jobs file during cleanup can be placed in the History Jobs file.
User Daily jobs (scheduled by the New Day procedure) select and schedule all other jobs for that day.
63
Sample New Day Processing

CONTROL-M is supplied with several sample components which can be used for New Day processing. To effectively implement New Day processing at your site, you should first understand how these sample components operate. When you understand the operation of the sample components, you can then customize New Day processing based on site requirements. Sample New Day processing components are described below. Sample Components Provided With CONTROL-M At time of installation, each site is provided with the following:
New Day Procedure A single New Day procedure is provided. Its default name is CONTDAY (the name can be changed). This procedure should have wide authorization for accessing scheduling tables and jobs.
User Daily Jobs Two sample User Daily jobs are provided: DAILYPRD DAILYSYS Contains sample JCL for scheduling production jobs. Contains sample JCL for scheduling system jobs.
These sample User Daily jobs are defined in table MAINDAY in the SCHEDULE library. These jobs activate User Daily procedure CTMDAILY which is responsible for ordering the production jobs. It is generally advisable to use these sample User Daily jobs to create separate User Daily jobs according to department (or other functional entity) and according to authorization. This is described later in this section.
Maintenance Jobs Two maintenance jobs are provided: CTMCLRES CTMLDNRS Activates utility IOACLRES Conditions/Resources file. which cleans the IOA
Activates utility IOALDNRS which creates and loads the Manual Conditions file. (This utility is normally run after all User Daily jobs have executed.)
These maintenance jobs are defined in table MAINDAY in the SCHEDULE library. Utility IOALDNRS is described later in this section. Utility IOACLRES is described in the utility section of the IOA Administrator Guide.
Scheduling Table: MAINDAY A scheduling table called MAINDAY is provided in the SCHEDULE library. This table contains User Daily jobs (DAILYSYS and DAILYPRD) and maintenance jobs (CTMCLRES and CTMLDNRS).
64
Date Control Records The following Date Control records (members) are in the CONTROL-M PARM library: DATEREC DATERECU Defined for New Day procedure CONTDAY. Sample Date Control record for User Daily jobs.
Called Programs The New Day procedure and User Daily jobs call programs which perform various steps of New Day processing (checking the Date Control record, selecting job orders, etc.). These programs are described in Programs Called During New Day Processing later in this section.
How the Sample Components Perform New Day Processing The sample components perform New Day processing as follows: During New Day processing, the New Day procedure accesses its Date Control record, scans table MAINDAY, and selects and loads the maintenance jobs and User Daily jobs to the Active Jobs file.
65
The User Daily and maintenance jobs placed in the Active Jobs file are submitted by CONTROL-M according to their runtime scheduling criteria. When a User Daily job is executed, it accesses its own Date Control record, scans the scheduling tables defined to it, selects jobs, and places the selected job orders in the Active Jobs file. (User Daily jobs can also schedule maintenance jobs as required.)
Note
User Daily jobs are not restricted to New Day processing. Although User Daily jobs are normally executed immediately after they are ordered by the New Day procedure, they can be executed at any time defined in their Runtime Scheduling parameters. Furthermore, they can be ordered at any time by any of the methods described in Alternative Methods of Job Ordering later in this section.
66
Date Control Record and Enhanced Daily Checkpointing A Date Control record must be defined for each User Daily job. This record is usually defined by the IOA administrator. The Date Control record for User Daily jobs consists of six fields. At different stages in New Day processing (i.e., before or after the execution of specific called programs which perform New Day processing), the current original scheduling date is placed in one of these date fields. This enables CONTROL-M to manage the process of job ordering. Furthermore, if New Day processing is interrupted at any point, the values in these fields can indicate which called program was in use when the interruption occurred. If the interruption occurred during job ordering, it is desirable to identify the last job ordered so that ordering can continue from that point. An optional second record in the Date Control member, the Enhanced Daily Checkpoint record, enables this identification. The Enhanced Daily Checkpoint record contains fields which store information about the last ordered job: JCL member name, internal sequence number, order ID, and the group to which the job belongs:
If Enhanced Daily Checkpointing is implemented, this information indicates from where job ordering was interpreted, and enables job ordering to continue from that point during recovery. If Enhanced Daily Checkpointing is not implemented, when the User Daily is rerun, all jobs in the scheduling table are considered for scheduling (including jobs which were already scheduled by the interrupted run.)
Both the Date Control record and the Enhanced Daily Checkpoint record have a fixed format, discussed below in Implementing New Day Processing. Note If input scheduling tables are modified prior to rerunning User Daily jobs (or the New Day procedure), the checkpointed job and internal sequence number might not match. In this case, rerun of the User Daily job(s) is not allowed and manual intervention is required.
Implementing New Day Processing

Overview As indicated above, sample User Daily jobs DAILYSYS and DAILYPRD are supplied with CONTROL-M in scheduling table MAINDAY. In theory, it is not necessary to use User Daily jobs. It is possible (but not recommended) to place all job scheduling definitions in one or more tables and have them scheduled by the New Day procedure. It is also possible (and also not recommended) to maintain only the two sample User Daily jobs provided with CONTROL-M, and to order all user jobs through the User Daily DAILYPRD.
67
The recommended way of automating the production environment via New Day processing is by:
Defining a different scheduling table for each group of related jobs. Defining a different User Daily job for each department, application, or similar entity.
Such implementation provides the following advantages: Improved Performance Many User Daily jobs running in parallel can order an entire days production jobs in significantly less time than it would take one User Daily to order all jobs one at a time. The IOA administrator can make each department responsible for its own User Daily job(s) and scheduling table(s) and for controlling its own job ordering. While maintaining sole authorization for the New Day procedure, the IOA administrator can limit each departments authorization to its own User Daily jobs. Problems encountered in one User Daily job do not necessarily affect the job ordering of other User Daily jobs.
Ease of Administration
Increased Security
Minimization of Problems
Implementation Tasks It is recommended that the following tasks (described below) be performed when implementing New Day processing:
Decide which User Daily jobs are needed (and for which tables). Use the sample JCL to create JCL for each User Daily job. Create User Daily job scheduling definitions and customize table MAINDAY. Decide whether or not to use Enhanced Daily Checkpointing. Create Date Control records. Notes Date Control records cannot be contained in a PDSE-type library. The New Day procedure and its accompanying Date Control record are defined at time of installation. They require no further implementation.
Ensure subsequent runs of utility IOALDNRS if necessary
Decide Which User Daily Jobs Are Needed (and for Which Tables) A job scheduling definition is defined for each job, and each job scheduling definition is placed in a scheduling table. Usually, related job scheduling definitions are grouped into their own scheduling table. Based on the scheduling tables defined at your site, and the jobs they contain, decide what User Daily jobs you require, and which scheduling tables each User Daily job will scan.
68
Use the Sample JCL to Create JCL for Each User Daily Job Create the JCL for each User Daily job by selecting one of the alternative methods of identifying scheduling tables (below) and customizing the JCL accordingly.
Method 1
DSN=sched_library(table)
This method requires that the user specify the name of a scheduling table and library directly in the JCL.
//DAILY EXEC CTMDAILY //DACHK DD DISP=SHR,DSN=parm_lib(date_control_record) //DAJOB DD DISP=SHR,DSN=sched_library(table1) // DD DISP=SHR,DSN=sched_library(table2) // DD DISP=SHR,DSN=sched_library(table3)
Method 2
DSN=parm_library(member)
//DAILY EXEC CTMDAILY //DACHK DD DISP=SHR,DSN=parm_lib(date_control_record) //DAJOB DD DISP=SHR,DSN=parm_library(member)
This method requires that the user specify a parm_library and member containing ORDER requests which identify scheduling libraries, scheduling tables and jobs to schedule and/or in-stream ORDER requests following //DAJOB DD * Method 2 provides the following advantages over Method 1: Changes required can be made to the member in the parm_library without changing the JCL of the User Daily job. Individual jobs can be specified.
When using Method 2, specify at least one ORDER statement and, optionally, SELECT/IGNORE statements. The Date Control record is referenced by DD statement DACHK. See utility CTMJOB later in this section for the syntax, parameter descriptions and functionality of the ORDER, SELECT and IGNORE statements.
69
Create User Daily Job Scheduling Definitions and Customize Table MAINDAY The supplied sample User Daily jobs, DAILYPRD and DAILYSYS, scan the scheduling tables referenced by DD statement DAJOB. However, different authorization is granted to each of these User Daily jobs. Use these sample User Daily jobs to create a User Daily job for each department in table MAINDAY. Assign the authorizations accordingly. Each User Daily job should scan a different set of scheduling tables than the other User Daily jobs. It is common in many sites for the IOA administrator to create a customized User Daily job for each department and then turn the scheduling table over to the control of the department. The department can then modify the scheduling table (and job scheduling definitions) as necessary. Although User Daily jobs can execute immediately after the jobs have been placed in the Active Jobs file, a site may choose to delay execution of a User Daily. To delay the submission of a User Daily, the User Dailys runtime scheduling criteria should be defined accordingly. Note If groups of User Daily jobs are executed at different times, IOALDNRS should be run again after each group of User Daily jobs is run.
Additional maintenance jobs can be added to table MAINDAY as necessary. Decide Whether or Not Enhanced Daily Checkpointing Will Be Used Enhanced Daily Checkpointing enables automatic rerun of the job ordering process to resume from the unsuccessfully ordered job, if New Day processing terminates during job ordering (due to system crash, etc.). The decision of whether or not to implement Enhanced Daily Checkpointing can be made separately for each User Daily job (i.e., the same decision does not have to be made for all User Daily jobs). Implementation of Enhanced Daily Checkpointing requires definition of a second date control record in the Date Control record member. (The format of this record is described below in Create Date Control records.) This second record stores information which identifies jobs already ordered to the Active Jobs file. This, in turn, allows New Day processing to continue ordering jobs without redundancy. Create Date Control Records Date Control records are members in the CONTROL-M PARM library. A different Date Control record must be defined for each User Daily job. It is usually defined only once for each job, and from then on it is usually updated by the User Daily job. If Enhanced Daily Checkpointing is implemented, a second Date Control record must be defined for each User Daily job. The length of the User Daily Date Control record is 80 characters. The format of the dates in the record is mmddyy, ddmmyy or yymmdd, depending on the site standard. The following chart shows the format of the Date Control record, and indicates when the User Daily adds the original scheduling date values to the fields in the record:
6 10
Column 01-06 18-23
Value Added date1 date2
Description User Daily adds the ODATE before the User Daily procedure is begun. User Daily adds the ODATE before the job ordering process begins for jobs being scheduled based on DATES, DAYS and/or DCAL parameters. User Daily adds the ODATE after the job ordering process ends for jobs being scheduled based on DATES, DAYS and/or DCAL parameters. User Daily adds the ODATE before the job ordering process begins for jobs being scheduled based on WDAYS and/or WCAL parameters. User Daily adds the ODATE after the job ordering process ends for jobs being scheduled based on WDAYS and/or WCAL parameters. In the User Daily Date Control records, these columns must be blank. User Daily adds the ODATE upon completion of all processing.
25-30
date3
43-48
date4
50-55
date5
60-65 67-72
blank date6
The format of the second Date Control record, which is required only if Enhanced Daily Checkpointing is used, is shown below. Constant or Value Added JOB= blank ,SERIAL_NO= blank ,ORDERID= blank ,GROUP= blank
Column 01-04 05-12 13-23 24-28 29-37 38-42 43-49 50-69
Description Constant. In this area, CONTROL-M stores the MEMNAME value of the last ordered job. Constant (note the comma before the "S"). In this area, CONTROL-M stores its internal sequence number of the last ordered job. Constant (note the comma before the "O"). In this area, CONTROL-M stores the order ID of the last ordered job. Constant (note the comma before the "G"). In this area, CONTROL-M stores the group name of the last ordered job.
When creating this record, the user should:
Specify the indicated constants (e.g., JOB=) in the appropriate columns. Leave blank the columns indicated as blank. These columns are filled in by the User Daily during processing.
6 11
Ensure Subsequent Runs of Utility IOALDNRS if Necessary If all User Daily jobs are scheduled to run in parallel, utility IOALDNRS only needs to run once, after the User Daily jobs have finished execution. However, if User Daily jobs are executed at various times during the day, utility IOALDNRS should run after each group of User Daily jobs is executed. This can be ensured by having each group of User Daily jobs set the appropriate prerequisite conditions to ensure the execution of IOALDNRS.
Programs Called During New Day Processing

The most important programs in New Day processing are CTMILY and CTMILU.
The New Day procedure executes program CTMILY. Each User Daily calls procedure CTMDAILY which executes program CTMILU.
Programs CTMILY and CTMILU both execute other programs which implement New Day processing. The programs called by CTMILY and CTMILU are listed in the table below. Both CTMILY and CTMILU read the member referenced by DD statement DAPROG and activate the programs listed in the member. The format for each record in the program list is: Columns 01-08 10-11 Description Program name. Maximum return code allowable in the preceding program. If a higher return code is encountered in the preceding program, the current program is not executed. Program arguments.
13-70
6 12
The programs called by the program CTMILY (the New Day procedure) and by program CTMILU (User Daily jobs) are shown in the following chart: Called By Program CTMILY CTMILU Purpose CTMCHK Checks the current date and its relation to the Date Control record (see below). When called by CTMILY, the program always asks the computer operator to verify that CONTROL-M is activated on the correct date. When called by CTMILV, the program asks the computer operator to verify that CONTROL-M is activated on the correct date only if value CONFIRM is specified as the argument (anywhere within columns 13-70). CTMFRM Reformats the CONTROL-M Active Jobs file and the IOA Conditions/Resources file: CONTROL-M Active Jobs File By default (i.e., if no SELECT/IGNORE statements are specified), the following jobs are erased from the Active Jobs file and the file is compressed:
Jobs which have already executed and ended OK (regardless of parameter MAXWAIT). Jobs whose exceeded. MAXWAIT parameter has been
Emergency jobs which are not needed.
IOA Conditions/Resources File This program erases all prerequisite conditions whose data is the same as the new CONTROL-M working date. This prevents jobs from being submitted for execution due to prerequisite conditions set on the same date in the preceding year. (You can customize the New Day procedure to suppress the erasure of the next days conditions by using an IGNORE COND * statement and utility CTMCLRES. See Section 3 of the IOA Administrator Guide for details.) At start of execution, this program creates a backup copy of the Active Jobs file for recovery purposes (BKP file). CTMEDA CTMJOB Signals to the CONTROL-M monitor that the Active Jobs file was successfully formatted. Places job orders in the Active Jobs file according to the date in the Date Control record and the data in the scheduling table(s) supplied. Marks the end of the Daily run.
CTMPDA
6 13
Implementation and Maintenance: Implementation Alternative Methods of Job Ordering
If CONTROL-R is installed and the History Jobs file is active, program CTMFRM is run again via CTMILY, this time against the History Jobs file: Called By Program CTMILY CTMILU CTMFRM Purpose Compresses the CONTROL-M History Jobs file by removing jobs whose retention criteria (RETENTION: # OF DAYS/GENERATIONS TO KEEP) are no longer satisfied.
If CONTROL-R is installed, step DELARCH is run after the conclusion of program CTMILY. This step runs the following: Called By Program CTMILY CTMILU CTMDAS Purpose Scratches archived SYSDATA of jobs deleted by program CTMFRM.
Alternative Methods of Job Ordering

Under CONTROL-M, job ordering is normally performed automatically via the New Day procedure and User Daily jobs during New Day processing, as described earlier in this section. However, at times it is desirable to perform job ordering using methods other than the New Day procedure and User Daily jobs. For example, it may be necessary to schedule ad hoc jobs, or to order jobs for a different working date (e.g., reschedule a job run from the first of next month to the thirtieth of this month, or reschedule the run of an entire scheduling table from the fourth of the month to the fifth of the month because all job runs in the table must be performed again). CONTROL-M provides several alternative methods of job ordering. Some methods of job ordering are performed online; others in batch. Some are performed automatically; others are performed manually. Below is a list of facilities and functions that enable jobs to be ordered without the New Day procedure and User Daily jobs. Table/Job List screen Enables jobs to be ordered from Online facility screens. See Ordering (Scheduling) Jobs in the description of the Scheduling Definition facility in Section 2 of this manual. Allows job ordering via utility (or CLIST) CTMJOBRQ. See M1: Issue a Job Order in Section 2 of this manual. Allows job ordering via utility (or CLIST) CTMJBINT. See M6: End User Job Order Interface in Section 2 of this manual. Described under Utilities later in this section.
Job Order panel End User Job Order interface
Utility CTMJOB
6 14
Utility CTMBLT CLIST CTMCJOBS Quick submit command CTMQSB Job ordering from special environments
Described under Utilities later in this section. Allows job ordering directly from the TSO environment. See Job Ordering Via CLIST CTMCJOBS below. Allows job ordering via CONTROL-M submit command CTMQSB (instead the ISPF submit command). See Job Ordering Via Quick Submit Command CTMQSB below. Facilitates job ordering from other environments (CICS, ROSCOE, etc.). See Ad Hoc Job Ordering From Special Environments: CTMAJO below.
Job Ordering Via CLIST CTMCJOBS

Job orders can be requested from the TSO environment via CLIST CTMCJOBS. You will be prompted to enter a value for CTMSMEM. The required response is SCHEDLIB(library) plus any of the arguments listed below whose default value is not suitable for the job order. You will also be prompted to enter a value (YES or NO) for argument FORCE. This CLIST has the following arguments: SCHEDLIB(library) CALLIB(calendar) Name of the scheduling %OLPREFM%.SCHEDULE library. Mandatory. Default:
Name of the calendar library to be allocated. Optional. Default: %OLPREFA&.CAL (Required only if the job scheduling definition contains a calendar name in parameter DCAL, WCAL and/or CONFCAL.)
TABLE(table) JOB(jobname) ODAT(dateref)
Name of the scheduling table. Optional. You will probably want to specify this argument. Name of the job to order. Optional. Default: ALL, which results in ordering all jobs in the specified table. Original scheduling date to apply to the job order requests. Optional. Default: the value (DATE or ODAT) specified for Work Mode Profile variable PSCHDTYP via the ICE customize option. See Section 2 of the IOA Administrator Guide for details. Valid values: date ODATE Valid six-character date (in mmddyy, ddmmyy, or yymmdd format, depending on the site standard). Resolves to the current working date.
GROUP(group) FORCE(YES|NO)
Name of the group to which the job belongs. Optional. Indicates whether or not to force the job(s). Mandatory. Valid values: YES NO Force the job. Do not force the job.
Note
Individual jobs in a Group scheduling table cannot be ordered, but can be forced.
Example
CTMCJOBS SCHEDLIB(CTM.PROD.SCHEDULE) TABLE(AP00) ODAT(090998)
6 15
Job Ordering Via Quick Submit Command CTMQSB

In many instances, the contents of the job are determined by an end user before submission. For example, a user may maintain a member which contains the JCL and parameters of a certain report. When someone requests the report, the user edits the member (e.g., using ISPF), changes the parameters of the report, and uses the ISPF SUBMIT command to submit the job. As described in the previous paragraphs, CONTROL-M can detect such jobs when they appear on spool, and control their execution. However, there are a few disadvantages to this method. The primary disadvantage is in handling job abends. When an On Spool job abends, it is not clear which JCL member should be submitted to perform a rerun. For example, in the above example, if the JCL has not been saved (e.g., the user exited ISPF EDIT using the CANCEL command), there is no original member from which to perform the rerun. This problem can be overcome via CONTROL-M command CTMQSB. When submitting a job, use command CTMQSB instead of the regular ISPF SUBMIT command. Just type it in the command line and press <ENTER>. (You may have to prefix it by the % character to designate a CLIST.) It is possible to replace the ISPF SUBMIT command with CONTROL-Ms CTMQSB command. For more information, see step Install ISPF Support in the CONTROL-M Installation Procedure in the IOA Installation Guide. If the member contains JCL cards which start with //*CONTROLM then special processing takes place (i.e., the member is not submitted). The CONTROL-M submit command looks for two //*CONTROLM cards with the following format (order and position in the job are not important):
//*CONTROLM TABLE scheduling-tables-library table-name //*CONTROLM JCL JCL-library
The current JCL member is written to the specified JCL library. The name of the member is composed of the first three letters of the TSO user ID, and the CONTROL-M order ID (5 characters). This method ensures that the name is unique. The scheduling table is read from the specified library. The submit command assumes that the table contains only one job definition. If the table contains definitions for more than one job, only the first job definition is taken into account; the remainder are ignored. CONTROL-M command CTMQSB replaces the original library and member names with the names of the JCL library and member where the job has been stored (see above). The user ID is replaced by the TSO user ID. To avoid accumulation of old members, it is advisable that a new (empty) JCL library be used each day. CONTROL-M job order security exit CTMX001 is invoked (as under CTMJOBRQ). If the job order is valid, it is placed on the CONTROL-M Active Jobs file. The job is then submitted based on the regular job scheduling criteria (e.g., IN, CONTROL, TIME, etc). Scheduling tables which are referred to by //*CONTROLM statements should not be included in a regular batch Daily. They should contain a skeleton of a job order. For example: reports which require IMS to be up, reports which use a lot of IDMS resources, update to certain VSAM files, etc.
6 16
It is possible to force the use of the CONTROL-M submit facility. When the CONTROL-M CTMQSB command is activated, the contents of the member to be submitted are passed to CONTROL-M user exit CTMX010. This exit can automatically add //*CONTROLM cards to the submitted member. Use of this technique results in a completely scheduled environment. All submitted jobs will be under CONTROL-M control. Notes Each member processed via command CTMQSB should contain only one job. If one of these members contains more than one job, all the jobs are submitted; however, a message is produced for only the last job. If the job is ordered, CONTROL-M submits all the jobs in the member, but controls only the first job. CTMQSB requires allocation of files SYSPRINT and DACKPT. CONTROL-D users: The D-CAT field of the job scheduling table is ignored for jobs which are scheduled using the CONTROL-M CTMQSB command. This means that a report decollating mission will not be automatically ordered for jobs which are scheduled by the CTMQSB command.
Ad Hoc Job Ordering From Special Environments: CTMAJO

Sometimes it becomes necessary to order ad hoc jobs from any of various environments (CICS, ROSCOE, etc.). To handle such a need, a special program, CTMAJO, is supplied with CONTROL-M. Since program CTMAJO is not environment dependent, the IOA administrator must develop an application which enables the program to be used with the particular environment. (One such application, CTMQSC, is supplied with CONTROL-M. CTMQSC, described earlier in this section, is for use with CTMAJO under ISPF.) Program CTMAJO accepts the following parameters:
Jobs JCL which is already loaded into memory Name of an ad hoc JCL library in which to place the JCL Name of a scheduling library Name of a scheduling table (in the above library) containing a single, skeletal, job scheduling definition Requested scheduling date
To handle the ad hoc request, CTMAJO performs the following: Takes the JCL of the job to be submitted from memory and writes it to the specified ad hoc JCL library, using a unique member name. Takes the skeletal job scheduling definition from the scheduling table in the scheduling library, and loads the job scheduling definition to the Active Jobs file. When placing the job order in the job scheduling definition, CONTROL-M overwrites the MEMNAME value from the skeleton with the name of the ad hoc JCL member. It also specifies the requested scheduling date.
6 17
The job then comes under the control of the CONTROL-M monitor:
If runtime scheduling criteria are specified in the skeletal job scheduling definition, the job is not submitted until those criteria are satisfied. If post-processing parameters are specified, they are performed upon completion of the job.
Using CTMAJO to order ad hoc jobs under special environments is preferable to bringing jobs under CONTROL-M control as On Spool jobs because when CTMAJO is used, the JCL is available, if necessary, for job rerun. (With On Spool jobs, the JCL member may not be known.) For a sample call to utility CTMAJO, see member ROSORDER in the IOA SAMPLE library.
6 18
Implementation and Maintenance: Implementation Manual Conditions File and Maybe Jobs
Manual Conditions File and Maybe Jobs

The Manual Conditions file contains a list of prerequisite conditions which are required by jobs in the Active Jobs file but which will not be available (i.e., added to the IOA Conditions/Resources file) unless there is some form of user intervention.
Loading the Manual Conditions File

Conditions are added to the Manual Conditions file via utility IOALDNRS. This utility is run during New Day processing, but it should also be run following the addition of a set of jobs in the Active Jobs file. Utility IOALDNRS checks the IN conditions required by scheduled jobs against the conditions available in the IOA Conditions/Resources file and against the OUT conditions which can be set by the scheduled jobs. All IN conditions which are not in the IOA Conditions/Resources file and which are not listed as OUT conditions in a scheduled job are added to the Manual Conditions file.
Using the Manual Conditions File

The Manual Conditions file provides the user with a list of conditions for which manual intervention is required if the conditions are to be added to the IOA Conditions/Resources file. To utilize this list effectively, the user should distinguish between two types of conditions in the list because each requires a different type of intervention. From the user perspective, the two types of conditions are: Manual Conditions Conditions which always require manual intervention and are therefore never automatically added by jobs as OUT or DO COND conditions. Example Job-X, which requires that a tape has arrived before the job is submitted, contains IN prerequisite condition TAPE-ARRIVED. This condition should not be automatically added to the IOA Conditions/Resources file by a job, but should instead be manually added by the operator only after the tape has arrived. Unscheduled Conditions Conditions which can be added automatically by a job, but which appear in the Manual Conditions list because none of the jobs scheduled that day will set the condition. Example Job-B requires IN condition JOB-A-ENDED-OK. This condition is added as an OUT condition by Job-A. Job-B is scheduled on a day during which Job-A is not scheduled. The distinction between the two types of conditions mentioned above is important because the user will want to respond to each type differently, as described below.
6 19
Handling Manual Conditions

The handling of Manual Conditions, as defined above, is fairly straightforward. In the above example, the user clearly does not want the condition added automatically, nor does the user want the condition ignored. Simply put, Job-X should not be run unless the required tape has arrived at the site, in which case the operator adds the condition. For this type of condition, the only desired manual intervention is the adding of the condition at the appropriate time. This can be performed via option A (Add) in the Manual Conditions screen.
Handling Unscheduled Conditions

The handling of Unscheduled Conditions, as defined above, is more complex because it concerns the issue of normal dependency versus Maybe dependency: Normal Dependency A successor job is always dependent on the predecessor job, whether or not the predecessor job is scheduled. With this type of dependency, using the example cited above, successor Job-B should not be submitted because predecessor Job-A was not scheduled and executed. In this case, the dependency should not be ignored. unscheduled prerequisite condition is not added manually. Maybe Dependency The
A successor job is dependent on the predecessor job only if the predecessor job is scheduled that day. If the predecessor job is not scheduled that day, the successor job should still be submitted provided that other runtime scheduling criteria are satisfied. In this case, the predecessor job is referred to as a Maybe job. With this type of dependency, using the example cited above, successor job Job-B should be submitted (provided all other runtime scheduling criteria are satisfied) because predecessor job Job-A was not scheduled. In this case, the dependency should be ignored or bypassed. Methods for ignoring Maybe dependencies are described below.
6 20
Handling Maybe Dependencies

The most common method of handling Maybe job dependencies is to add the unscheduled conditions of Maybe jobs to the IOA Conditions/Resources file. However, examining each condition in the Manual Conditions list to determine if it is an unscheduled condition from a Maybe job, and manually adding each Maybe job unscheduled condition, is a difficult process. The process can be greatly simplified, and automated, via the following steps: 1. Define a Unique Prefix for Maybe Job Prerequisite Conditions When Maybe dependencies are defined, the prerequisite IN, OUT and DO COND conditions should all have the same unique prefix (i.e., a prefix which is not used for other prerequisite conditions). Using a unique prefix symbol makes it easier to see unscheduled conditions of Maybe jobs in the Manual Conditions list. Normally, this prefix is either symbol # or @. Note If your site utilizes MVS restarts and uses symbol @ in OUT conditions for the restart, this symbol should not be used as a prefix for Maybe job conditions. In this case, the # symbol should be used for Maybe conditions.
2. Use KeyStroke Language utility ADDMNCND to add the prerequisite conditions. KSL utility ADDMNCND automatically adds all conditions with a specified prefix in the Manual Conditions file to the IOA Conditions/Resources file. By specifying the above-defined unique prefix symbol in the utility, unscheduled conditions from Maybe jobs are automatically added, making manual adding of the conditions unnecessary. After the above two steps have been implemented, the only manual intervention required for unscheduled conditions of Maybe jobs is the executing of KSL utility ADDMNCND.
Maybe Jobs in Group Scheduling Tables

The above implementation for handling unscheduled conditions of Maybe jobs can be applied to jobs and conditions in all types of scheduling tables. However, an alternative method is available for conditions and jobs in Group scheduling tables. Rather than add the unscheduled conditions of Maybe jobs to the IOA Conditions/Resources file, the unscheduled conditions can be removed as runtime scheduling criteria for the successor job orders. The Group Entity definition in Group scheduling tables contains a field ADJUST CONDITIONS. If a value of Y is specified in field ADJUST CONDITIONS, CONTROL-M checks the scheduled jobs for unscheduled conditions.
6 21
Unscheduled conditions normally added by other jobs in the same Group scheduling table are removed from the IN statements of the scheduled job orders:
These conditions will not appear in the Zoom screen. They are not, however, deleted from the original job scheduling definition. These conditions also do not appear in the Manual Conditions file. Therefore, there is no real advantage to defining them with a unique prefix, unless they are used as IN conditions for jobs in a different table.
The following points should be noted:
Unscheduled conditions normally added by jobs in other scheduling tables are not removed from the job order. They appear in the Manual Conditions file. As indicated above, ADJUST CONDITIONS applies only to jobs in the same Group scheduling table. By contrast, utility IOALDNRS detects unscheduled conditions of Maybe jobs across scheduling tables, and KSL utility ADDMNCND adds these conditions to the IOA Conditions/Resources file regardless of scheduling table.
For more information, see ADJUST CONDITIONS in Section 3 of this manual.
6 22
Implementation and Maintenance: Implementation CONTROL-M/WorkLoad Considerations
CONTROL-M/WorkLoad Considerations
CONTROL-M/WorkLoad is a batch optimization system which enables effective parallel processing and efficient resource utilization in the MVS environment using MVS Pipe technology.
Job-Related Considerations for Pipes

The following job-related issues should be considered when using the PIPE parameter in a CONTROL-M job scheduling definition:
When using pipes for jobs submitted by CONTROL-M, the PIPE parameter must be used if parallel submission of all pipe participants is to be ensured. Normally (i.e., when pipes are not used), prerequisite conditions ensure desired flow of predecessor and successor jobs.
However, when values are specified in the PIPE parameters of interrelated job scheduling definitions, CONTROL-M uses them to create Collections. The jobs in a Collection are not submitted until all prerequisite conditions required by all jobs in the Collection are satisfied. If a dependency exists between an OUT condition of one job and an IN condition of another job in the same Collection, it will prevent submission of all the jobs in the Collection. CONTROL-M resolves this problem by automatically deleting the IN condition, thus bypassing the dependency between the jobs in the Collection and enabling the submission of the jobs. Notes
If a jobs IN condition was deleted by CONTROL-M as described above,

CONTROL-M deletes this condition from the Active Jobs file but not from the Scheduling table. Therefore, if that job is removed from the Collection or its PIPE statement is deleted (in the Active Jobs file via the Zoom screen), the IN condition will not reappear until the job is reordered.
To allow integration between CONTROL-M and CONTROL-M/WorkLoad, the pipe

name specified in the CONTROL-M job scheduling definition must be identical to the pipe name specified in the CONTROL-M/WorkLoad rule. Currently, this requirement is not forced by CONTROL-M.
Jobs cannot be run in parallel in the following cases: A Control resource is used exclusively by one or more participants in a Collection. TIME FROM/UNTIL specifications for the jobs do not overlap.
Each of these cases should be considered individually at time of implementation. For example, if exclusive use of a Control resource was intended to ensure serial access to a dataset which is now accessed via a pipe, the Control resource may need to be converted to a shared resource, or removed altogether.
6 23
Implementation and Maintenance: Implementation CONTROL-M/WorkLoad Considerations
When PIPE definitions are added, the Quantitative resources defined for the jobs in the Collection should be checked to see if some of the defined resources are no longer necessary (e.g., if a pipe replaces a tape dataset, the tape resource may not be required). Such resources should be removed from the job scheduling definition. In a non-Sysplex environment, all jobs which are part of a Collection should run in the same system. Therefore, it is recommended to avoid using resources prefixed by a dollar sign ($) in jobs that are part of a Collection, to ensure that all the jobs are submitted to the same system.
Enhanced Runtime Scheduling Algorithm When jobs that are part of a Collection are scheduled, CONTROL-M treats the Collection as one unit of work for processing runtime scheduling criteria in the following ways:
CONTROL-M ensures that the required number of participants (as defined for the pipe in the CONTROL-M/WorkLoad rule) access each pipe in the Collection. If a participant is missing, the jobs in the Collection are not submitted. This ensures that a job is not submitted when its participants are not scheduled on that day. CONTROL-M analyzes all resources (e.g., prerequisite conditions, Quantitative resources, time limits) required by all jobs in the Collection as a single set. All participants are submitted together when all the resources required by the set are available. This ensures the parallel submission of all pipe participants. To ensure that the jobs will start execution on time, it is recommended that initiators be handled as Quantitative resources. This ensures that submitted jobs do not wait for initiators and delay other jobs in the Collection.
CONTROL-M checks if the CONTROL-M/WorkLoad monitor is active before submitting the jobs in the Collection. If the CONTROL-M/WorkLoad monitor is not active, the jobs in the Collection are not submitted. This ensures that, when submitted, the jobs will run in parallel using pipes.
System-Related Considerations
The following system-related issues should be considered when using the PIPE parameter in a CONTROL-M job scheduling definition.
Parallel processing changes resource usage in the system. All resources required for all the jobs in the Collection must be available when the jobs are submitted. This means that more resources (e.g., initiators, tape drives, CPUs) are required for shorter time periods; they become available after the jobs using the pipe finish execution. Therefore, when using pipes, resource usage in the system in which the jobs will run should be reviewed to ensure that all required system resources are available at the time the jobs will be submitted.
The change in resource usage may necessitate changing the maximum quantities defined for CONTROL-M to satisfy the changed requirements.
6 24
Implementation and Maintenance: Implementation CONNECT DIRECT Support
CONNECT DIRECT Support

CONTROL-M supports CONNECT DIRECT software which creates dataset events (i.e., the appearance of a dataset) on the system. CONNECT DIRECT support enables dataset events to automatically trigger CONTROL-M operations (i.e., the adding and/or deleting of prerequisite conditions, and/or the triggering of jobs) to handle these events. Dataset event definitions are created and modified by the CONTROL-M user via online Event Definition and Event List screens. Note Prior to Release 5.1.4, CONNECT DIRECT Support was called NDM Support. See CONNECT DIRECT Support in Section 3 of the IOA Administrator Guide for information about the implementation and operation of this feature.
CONNECT DIRECT support includes the following phases:
Dataset Event Definition (REXX Procedure IOACDDR) At least one Event list must be defined. An Event list is a list composed of dataset names and, for each dataset name, the operations which should be triggered by the dataset event. Event lists are defined/modified in the Dataset Event Definition facility which is activated via REXX procedure IOACDDR (described below).
Automatic Operation Triggering Upon Dataset Appearance (Module IOADDR) Once Event lists are defined, they can be used to trigger operations which are based on dataset events. See your CONTROL-M administrator if you need more information about the operation of this feature.
REXX Procedure IOACDDR: Dataset Event Definition

Event Lists are defined/modified in the Dataset Event Definition facility screens which are activated via REXX procedure IOACDDR. The interface to the utility consists of two screens:
Event List screen Event Definition screen
Lists all dataset events defined by the user. This screen is displayed upon entry to the utility. Used to define/modify specific events. When modifying an existing event, only a section of the Event Definition screen, called the Event Modification screen, is displayed.
Note
When the utility is accessed for the first time (i.e., when no events are yet defined for the user), the Event List screen is not displayed. Instead, the Event Definition screen is displayed directly. After one or more events are defined, the Event List screen is displayed upon entry to the utility.
Your user ID is automatically displayed at the top of both screens because CONTROL-M checks security authorization before implementing the request. Only one user at a time can edit a particular Event list. Other users can access that Event list in browse mode only.
6 25
The following types of operations can be specified for events in the Event list: JOB COND A job can be ordered (or forced). A prerequisite condition can be added or deleted.
Event List Screen

The Event List screen (shown below) lists dataset events which are already defined.
EVENT LIST - M21.NDM.TAB(M21) ------------------------------- ROW 1 TO 2 OF 2 COMMAND ===> SCROLL ===> CSR S - Select, I - Insert, D - Delete - List Of Dsnames ----------------------------- TYPE -------------------------- M21.LIB* COND - M21.LIB* JOB ******************************* BOTTOM OF DATA ********************************
For each defined event, the screen displays the name of the dataset and the type of operation the event should trigger. Only one operation can be specified for each occurrence of a dataset name in the list. However, the same dataset name can be specified multiple times thereby allowing multiple operations to be specified for the same dataset event. Specify one of the following options to the left of a dataset name and press <ENTER>: S I (Select) (Insert) Display the selected event in the Event Modification screen. The event can then be modified, if desired. Add a new event below the selected event. The Event Definition screen is displayed with no entry. Delete the selected entry. A confirmation window is displayed (default: No).
D (Delete)
6 26
Event Definition Screen

The Event Definition screen is shown below.
---------------------- M21 EVENT DEFINITION SCREEN ------------------------COMMAND ===> SCROLL ===> CSR DSNAME ===> --------------------------- JOB TYPE PARAMETERS --------------------------SCHED. LIB. ===> TABLE NAME ===> JOB NAME ===> ODATE ===> (Date/Odat) OR ===> (MM DD YY) FORCED SCHED. ===> (Yes/No) -------------------------- COND TYPE PARAMETERS --------------------------FUNCTION ===> (Add/Delete) CONDITION NAME ===> CONDITION DATE ===> (Date/Wdate) OR ===> (MM DD)
The screen is divided into three sections of parameters. DSNAME Name of the dataset event (i.e., the dataset whose appearance will trigger the operation).
JOB TYPE PARAMETERS Define the parameters in this section only if the event should trigger the scheduling of a job. Parameters include: SCHED. LIB. TABLE NAME JOB NAME ODATE Library containing the job scheduling definition of the job to be scheduled. Table containing the job scheduling definition of the job to be scheduled. Name of the job to be scheduled. If blank, the entire table is ordered. Date to schedule the job. Valid values are ODAT or a 4-character date in mmdd or ddmm format (depending on the site standard). Indicates whether or not to force the job if it would not otherwise be scheduled. Valid values: Yes No Force the job. Do not force the job. Default.
FORCED SCHED.
6 27
COND TYPE PARAMETERS
Define the parameters in this section only if the event should trigger the adding or deleting of a prerequisite condition. FUNCTION Function to perform. Valid values: Add Delete CONDITION NAME CONDITION DATE Add the specified condition Delete the specified condition. condition to be added or
Prerequisite deleted.
Date associated with the prerequisite condition. Valid values are ODAT or a 4-character date in mmdd or ddmm format (depending on the site standard).
To define an event and corresponding operation, fill in the DSNAME and either the JOB or the COND type parameters (only one type can be used in each definition), and press <ENTER>. Note If you selected an existing event in the Event List screen, only the screen section relating to that event (JOB or COND) is displayed and the screen is called the Event Modification screen. Modify the event as desired and press <ENTER>.
6 28
Implementation and Maintenance: Implementation Parameter Prompting Facilities
Parameter Prompting Facilities

It is assumed that the reader is familiar with the following CONTROL-M facilities and concepts: JCL and AutoEdit facility; prerequisite conditions; Manual Conditions (Screen 7) and utility IOALDNRS. CONTROL-M provides two different types of Parameter Prompting facilities. The online use of the two Parameter Prompting facilities is described in Section 2 of this Manual. This section provides an explanation of how the Parameter Prompting facilities work, how they differ from each other, and how to choose the facility which best suits your environment. In addition, certain preparatory steps are detailed.
Parameter Prompting Facility Type 1

The Parameter Prompting facility Type 1 is an ISPF table-based facility which provides automatic prompting for AutoEdit parameter values and setting of prerequisite conditions. It is the recommended method for operations personnel to automate the updating of AutoEdit parameter members. CONTROL-Ms JCL and AutoEdit facility eliminates the need for frequent manual changes to job parameters. However, there are usually a few job parameter changes that cannot be automated, e.g., tape serial numbers, which are unknown prior to tape arrival. These types of parameters require manual modification by the user (generally operations personnel).
6 29
Old Method Lets consider the typical solution to this problem in prior releases of CONTROL-M. We will use an example of CONTROL-Ms handling of the daily arrival of IRS tape number 123456.
The illustration above represents the CONTROL-M for handling the IRS tape.
one-time
definitions
required
to
prepare
1. JOB A requires input of the IRS tape number before it can run. The job must be defined in a CONTROL-M scheduling table with an IN prerequisite condition of IRS-TAPE-ARRIVED. 2. The JCL for JOB A must include %%LIBSYM and %%MEMSYM control statements pointing to AutoEdit Library CTM.LIB.SYMBOLS and AutoEdit member TAPES. 3. AutoEdit member TAPES contains several AutoEdit parameters (from various jobs), including parameter %%IRS_TAPE.
6 30
On a given day, the Manual Conditions file created by utility IOALDNRS indicates that the prerequisite condition IRS-TAPE-ARRIVED must be added manually by the user. This serves as a reminder to the operations personnel that a job is waiting for an IRS tape number. When the tape arrives, the user must perform two steps (as illustrated below):
1. Access AutoEdit member TAPES and assign value 123456 to the %%IRS_TAPE parameter. 2. Enter Screen 7 to manually add condition IRS-TAPE-ARRIVED. When the condition IRS-TAPE-ARRIVED has been added to the IOA Conditions/Resources file (and assuming all other runtime conditions are met), the CONTROL-M monitor submits the job. When the job is submitted, the value of %%IRS_TAPE in the JCL of JOB A is updated by the value in the TAPES member. Job parameter VOL=SER=%%IRS_TAPE resolves to VOL=SER=123456.
6 31
New Method Now lets examine the way the same problem is resolved using the Parameter Prompting facility Type 1.
The illustration above represents the one-time definitions required to prepare CONTROL-M for handling the IRS tape when using Parameter Prompting facility Type 1. 1. JOB A requires input of the IRS tape number before it can run. The job must be defined in a CONTROL-M scheduling table with IN prerequisite condition IRS-TAPE-ARRIVED. 2. The JCL for JOB A includes %%LIBSYM and %%MEMSYM control statements pointing to the CTM.PROD.PROMPT prompting parameters library and the TAPM%%OMONTH.%%ODAY daily AutoEdit member. 3. Using the first option of the Parameter Prompting facility Type 1, groups of AutoEdit parameters which require value assignment are defined once. These parameters are grouped into a Master Prompting table, the Master table. Default parameter values can be assigned. In addition, prerequisite conditions to be associated with parameters are designated. In this example, several parameters from various jobs have been defined in the TAP Master table, including the %%IRS_TAPE parameter from JOB A. Prerequisite condition IRS-TAPE-ARRIVED has been associated with this parameter.
6 32
When the tape arrives, the user only performs one step (illustrated below):
The user selects the TAP table from a list of Master tables and is presented with Daily Prompting table TAPT1112, an automatically created copy of the Master table for the current date. The Daily Prompting table consists of parameter names, (optional) descriptions, and default values. The user updates the %%IRS_TAPE parameter with the value 123456. The facility automatically adds condition IRS-TAPE-ARRIVED Conditions/Resources file and updates daily AutoEdit member TAPM1112. Summary By using Parameter Prompting facility Type 1, it is only necessary to update the Daily table. The user no longer needs to remember which AutoEdit parameters in which AutoEdit symbol member require changing, nor the prerequisite conditions which require setting. The Parameter Prompting facility automatically handles updating of the AutoEdit member, and adds any required conditions to the IOA Conditions/Resources file. to the IOA
6 33
Usage Notes JCL Modifications JCL members for jobs containing AutoEdit parameters defined in Master tables must be modified as follows: The %%LIBSYM control statement must point to the CONTROL-M PROMPT library. The %%MEMSYM control statement member name must be in the following format:
@@@M%%OMONTH.%%ODAY
where @@@ is the Table Name Prefix defined in Option 1 of the facility. %%OMONTH.%%ODAY can be replaced with any date variable or date constant in the format mmdd. IOALDNRS Utility The Parameter Prompting facility automatically adds conditions to the IOA Conditions/Resources file after parameter update. These conditions no longer require submission through Screen 7, and therefore do not need to appear on the Manual Conditions file. You can use the IGNORE IN parameter in utility IOALDNRS (described later in this section) to exclude these parameters from the file.
6 34
Parameter Prompting Facility Type 2

The Parameter Prompting facility Type 2 is a manual job scheduling facility which provides automatic prompting for AutoEdit parameter values. On a given day, the user selects the scheduling table(s) for execution. The user is then automatically prompted for parameter values required for the execution of the jobs scheduled to run on the specified date. This type of prompting facility is recommended for use in a distributed environment where user departments are responsible for manually scheduling (ordering) their jobs, and specifying required parameters. A sample application of this type of scheduling facility is the maintenance of confidential salary information in a payroll department. The payroll department usually retains control over its jobs and their input parameters. The Parameter Prompting facility Type 2 has three major phases: Definition Phase
1. Scheduling Table First, a scheduling table is defined using the CONTROL-M Online facility. The scheduling table contains job scheduling information for all of a departments jobs. Any number or type of jobs with any valid date scheduling criteria can be designated. The table is placed in a Master Scheduling Tables library. 2. Master Prompting Plan Next, using the first option of the Parameter Prompting facility Type 2, a Master Prompting Plan (MPP) is defined containing all AutoEdit variables used by all the jobs in the scheduling table. Any default values can be assigned. Value validity checks can also be defined. The MPP is placed in the Master Prompting Plan library.
6 35
FETCH Phase
The second option of the Parameter Prompting facility - Type 2, FETCH A PLAN, allows the user to select a plan for execution by CONTROL-M on a specific day. When a FETCH option is executed for a specific PLANID (or all PLANIDs with a specific suffix), a daily scheduling table is automatically created. The Daily Scheduling table, a subset of the Master Scheduling table, is placed in the Daily Scheduling Tables library. The Daily Scheduling table contains the job definition of all of the jobs in the Master Scheduling table scheduled to run on the specified date, based on each jobs scheduling criteria. The FETCH also creates a User Prompting Plan (UPP), a subset of the Master Prompting Plan, which is placed in the Daily Prompting Plan library. The UPP contains only parameters which are required by the jobs scheduled to run on the specified date. A Daily JCL library is also created containing JCL for todays jobs.
6 36
EXEC Phase The third option of this facility, EXEC A PLAN, permits the user to update or accept the default values of all the parameters appearing in the daily UPP. A daily AutoEdit parameters member, which will be accessed at the time of job submission, is automatically created and placed in the Daily AutoEdit Parameter library.
Once values have been assigned to all the parameters, the prerequisite condition RUN-%%PLANID is added. %%PLANID is resolved to the PLANID (and suffix if supplied) designated in the FETCH phase. The Daily Scheduling table is then ordered by CONTROL-M. The jobs are placed on the Active Jobs file and will run based on their scheduling parameters; i.e., a job will be submitted only when all scheduling criteria (other prerequisite conditions, etc.) have been met. Tailoring to User Needs The Parameter Prompting facility Type 2 is usually activated from the CONTROL-M ISPF Utilities screen. However, it is possible to activate the FETCH and EXEC phases using the following CLISTS: CTMFETCH CTMEXEC For fetching a plan (FETCH phase) For executing a plan (EXEC phase)
6 37
CTMFETCH CLIST When CLIST CTMFETCH is activated, the FETCH A PLAN screen is displayed:
---- CONTROL-M - P.P.F. ------ FETCH A PLAN ------------------------------(P.2) COMMAND ===> PLAN NAME PLAN NAME SUFFIX OVERRIDE DAILY PLAN ODATE ===> ===> ===> NO ===> 080898 (For multiple plans in the same day) (YES / NO)
Please fill in the Plan Name and press ENTER
MASTER SCHEDULING LIB DAILY SCHEDULING LIB MASTER PLANS LIB DAILY PROMPT PLANS LIB MASTER JCL LIB DAILY JCL LIB
===> ===> ===> ===> ===> ===>
CTMP.V514.SCHEDULE CTMP.V514.SCHD CTMP.V514.PLANMSTR CTMP.V514.PLAN CTMP.V514.JCLPROMP CTMP.V514.JCLP
PLAN NAME PLAN NAME SUFFIX OVERIDE DAILY PLAN
Plan name (1 to 6 characters). Mandatory. Two character suffix to be added to the PLAN NAME in daily libraries. Changing the suffix permits multiple daily plans. Whether or not to replace an existing plan. Valid values: YES A duplicate fetch of a plan (with suffix, if one has been designated) replaces an existing copy of a plan with the same PLAN NAME (and same suffix) for that day. Multiple fetches of a plan are not permitted on the same day (default).
NO ODATE
Specific date for which the plan is to be fetched. Default is the current working date. Another date (in mmddyy, ddmmyy or yymmdd format, depending on the site standard) can be specified. Name of the Master Scheduling Tables library.
MASTER SCHEDULING LIB
DAILY SCHEDULING LIB Name of the Daily Scheduling Tables library. The last qualifier of the library name cannot exceed 4 characters. (The CLIST concatenates the date to this daily library name.) MASTER PLANS LIB DAILY PROMPT PLANS LIB Name of the Master Prompting Plans library. Name of the User Daily Prompting Plans library. The last qualifier of the library name cannot exceed 4 characters. (The CLIST concatenates the date to this daily library name.)
6 38
MASTER JCL LIB DAILY JCL LIB
Name of the Master JCL library. Name of the Daily JCL library. The last qualifier of the library name cannot exceed 4 characters. (The ** symbol concatenates the date to this daily library name.)
CTMEXEC CLIST When CLIST CTMEXEC is activated, the EXEC / ORDER A PLAN screen is displayed:
---- CONTROL-M - P.P.F. ---- EXEC / ORDER A PLAN -------------------------(P.3) COMMAND ===> PLAN NAME PLAN NAME SUFFIX REMAINING PARAMETERS ODATE FORCED FROM TIME ===> ===> ===> NO ===> 080898 ===> (Blank for plan selection list) (For multiple plans in the same day) (YES / NO)
Please fill in the Plan Name (or blanks) and press ENTER
DAILY SCHEDULING LIB USER PROMPT PLANS LIB DAILY PARAMETERS LIB
===> CTMP.V514.SCHD ===> CTMP.V514.PLAN ===> CTMP.V514.AEDI
NAME PLAN PLAN NAME SUFFIX REMAINING PARAMETERS
Plan name (1 to 6 characters). Mandatory. Two-character suffix used to specify a specific plan. Continuation instructions. Valid values: YES The user is automatically presented with remaining (non-updated) parameters from all active plans. After updating the current plan, the user is given options for choosing another plan (default).
NO ODATE
Specific date on which the plan will be ordered. Default is the current working date. Another date (in mmddyy, ddmmyy, or yymmdd format depending on the site standard) can be specified. Specific time in format hhmm, before which the jobs cannot run. Name of the Daily Scheduling Tables library. Name of the User Prompting Plans library. Name of the Daily Parameters library.
FORCED FROM TIME DAILY SCHEDULING LIB USER PROMPT PLANS LIB DAILY PARAMETERs LIB
6 39
Usage Notes
The PLAN NAME can be up to six characters in length. Use of the SUFFIX parameter in the FETCH phase permits creation of multiple Daily User Prompting Plans based on one Master Prompting Plan. This also makes it possible to duplicate (by overriding) a fetch of the same plan by setting the OVERRIDE DAILY PLAN parameter to YES on the FETCH A PLAN screen. Each job defined in the Master Scheduling table must contain an IN prerequisite condition in the format:
RUN-%%PLANID
This prerequisite condition is added during the EXEC phase only after all parameters for a specific plan are assigned in the EXEC phase. %%PLANID resolves to the PLAN NAME (and SUFFIX) designated in the FETCH phase. Since each plan can be ordered multiple times for the same scheduling date, it is highly recommended to distinguish between the dependencies of the jobs in the plan based on PLAN NAME. Every prerequisite condition used for inter-plan dependency should contain the string %%PLANID. It will be automatically replaced by the PLANID during the FETCH phase.
The JCL of each job must be modified as follows: The first AutoEdit control statement must point to an AutoEdit Parameters library and member PLANID. Member PLANID will contain the unique PLANID of the job (automatically handled by CONTROL-M). Example
%%LIBSYM CTM.PROD.SYMBOLS %%MEMSYM PLANID
The second AutoEdit control statement must point to the Daily AutoEdit Parameters library and member %%PLANID. CONTROL-M will automatically resolves %%PLANID to the PLAN NAME designated in the FETCH phase. The Daily AutoEdit Parameter library should be suffixed by a date parameter which is resolved by CONTROL-M. Example:
%%LIBSYM CTM.PROD.AEDI%%OMONTH.%%ODAY %%MEMSYM %%PLANID
Member %%PLANID of each plan (in the Daily AutoEdit Parameter library) contains four values of configuration tables. Example
%%CONF1=INDICES %%CONF2=WEEKCHAR %%CONF3= %%CONF4=
To use the configuration tables parameters technique, insert the following AutoEdit statement in the JCL of each job:
//* %%INCLIB CTM.PROD.PARM %%INCMEM PPF2CONF
6 40
The MEMLIB parameter of each job definition in the scheduling table must point to the Daily JCL library. The library name is suffixed by the AutoEdit date variable(s). Example
CTM.PROD.JCLP%%OMONTH.%%ODAY
Occurrence numbering: It is recommended that all AutoEdit parameter names of jobs in the same plan be unique. In some plans, duplicate names may be unavoidable, and more than one job may share the same AutoEdit parameter name. If the parameters are to be assigned different values (i.e., used for different purposes), each parameter must be assigned a different OCCUR NO during definition of the Master Prompting Plan. A %%SET statement specifying the OCCUR NO. must be included in the JCL of the associated jobs as follows:
%%SET %%OC# = 01
When the AutoEdit parameter member is created, each AutoEdit parameter will include the OCCUR NO. as a suffix.
Using of the Parameter Prompting facility Type 2 requires customizing the CONTROL-M submit exit (CTMX002). See member CTMX2PPF in the IOA SECUDATA library for information about modifying the exit.
Maintenance Utilities The following jobs are located in the CONTROL-M JCL library. PPF2DEL This job can be run to delete sets of daily libraries according to specified date criteria.
//PPF2DEL JOB ACCNT,CTM,CLASS=A //* //* THIS JOB DELETES SETS OF DAILY LIBRARIES CREATED 3,4,and 5 //* DAYS PRIOR TO THE CURRENT DATE (%%ODATE). //* //************************************************************* %%SET %%DT3 = %%CALCDATE %%ODATE - 3 %%SET %%DELDATE3 = %%SUBSTR %%DT3 3 4 %%SET %%DT4 = %%CALCDATE %%ODATE - 4 %%SET %%DELDATE4 = %%SUBSTR %%DT4 3 4 %%SET %%DT5 = %%CALCDATE %%ODATE - 5 %%SET %%DELDATE5 = %%SUBSTR %%DT5 3 4 //DELLIB EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE CTM.PROD.PLAN%%DELDATE3 DELETE CTM.PROD.SCHD%%DELDATE3 DELETE CTM.PROD.JCLP%%DELDATE3 DELETE CTM.PROD.AEDI%%DELDATE3 DELETE CTM.PROD.PLAN%%DELDATE4 DELETE CTM.PROD.SCHD%%DELDATE4 DELETE CTM.PROD.JCLP%%DELDATE4 DELETE CTM.PROD.AEDI%%DELDATE4 DELETE CTM.PROD.PLAN%%DELDATE5 DELETE CTM.PROD.SCHD%%DELDATE5 DELETE CTM.PROD.JCLP%%DELDATE5 DELETE CTM.PROD.AEDI%%DELDATE5 //
6 41
PPF2DAY This job allocates the daily libraries which are to be used by the Parameter Prompting facility Type 2. It also copies the required jobs from the Master JCL library to the Daily JCL library. These are time-consuming tasks normally performed as part of the FETCH and EXEC phases of the Online facility. By scheduling this job daily under CONTROL-M, the time required to execute the FETCH and EXEC phases is reduced.
6 42
Implementation and Maintenance: Utilities
Utilities
The following list provides a short description of each utility used in the CONTROL-M environment. Following each short description is a reference which indicates where the utility is documented. Note Some utilities prefixed by IOA replace corresponding utilities prefixed by CTM from earlier releases of CONTROL-M. In such cases, the CONTROL-M utilities remain supported for your convenience; however, we recommend using the IOA utilities. Tests the syntax of AutoEdit control statements (described later in this section). Converts regular scheduling tables to Group scheduling tables (described in Section 9 of the IOA Administrator Guide). Builds an AutoEdit symbols member using an IOA calendar as input (described later in this section). Creates CONTROL-M scheduling tables (described later in this section). Compresses, cleans or changes the size of the CONTROL-M Active Jobs file (described in Section 9 of the IOA Administrator Guide). Allocates and formats the CONTROL-M Active Jobs file (described in Section 9 of the IOA Administrator Guide). Allocates and formats the CONTROL-M Journal file (described in Section 9 of the IOA Administrator Guide). Orders jobs into the Active Jobs file (described later in this section). Accumulates job statistical data in the CONTROL-M Job Statistics file (described in Section 9 of the Administrator Guide). Creates a calendar for each job defined in CONTROL-M showing the actual execution date(s) of the job (described later in this section). Releases Quantitative resources from a job step (described later in this section). Restores the Active Jobs File (described in Section 9 of the IOA Administrator Guide). Activates the Simulation and Forecasting facility (described in Section 7 of this manual). Produces a Tape Pull list (described in Section 7 of this manual). Updates CONTROL-M group/job scheduling definition parameters in batch mode (described later in this section). Produces a variety of cross reference reports (described later in this section). Builds scheduling calendars (described in Section 9 of the IOA Administrator Guide).
CTMAESIM CTMBGRP CTMBLDAE CTMBLT CTMCAJF CTMFRCKP CTMFRJNL CTMJOB CTMJSA CTMRCAL CTMRELRS CTMRSTR CTMSIM CTMTAPUL CTMTBUPD CTMXRF IOABLCAL
6 43
Implementation and Maintenance: Utilities
IOACLRES IOACND IOACOPRS IOACPLOG IOAFRLOG IOAFRNRS IOAFRRES IOALDNRS IOANOTE IOAOPR IOATEST IOAVCND
Cleans the IOA Conditions/Resources file (described in Section 9 of the IOA Administrator Guide). Handles utilization of prerequisite conditions and resources (described later in this section and in Section 9 of the IOA Administrator Guide). Copies or changes the size of the IOA Conditions/Resources file (described in Section 9 of the IOA Administrator Guide). Copies the IOA Log file to a sequential file or to another Log file (described in Section 9 of the IOA Administrator Guide). Allocates and formats an IOA Log file (described in Section 9 of the IOA Administrator Guide). Allocates and formats an IOA Manual Conditions file (described in Section 9 of the IOA Administrator Guide). Allocates and formats an IOA Conditions/Resources file (described in Section 9 of the IOA Administrator Guide). Loads/creates the IOA Manual Conditions file (described in Section 9 of the IOA Administrator Guide). Writes a message to the IOA Log file (described in Section 9 of the IOA Administrator Guide). Issues operator commands Administrator Guide). (described in Section 9 of the IOA
Simulates various events in the production environment (described in Section 9 of the IOA Administrator Guide). For VM/CMS environments. Sets prerequisite conditions in a CONTROL-M monitor running on an NJE-connected MVS machine. (See the description of utility IOACND later in this section and in Section 9 of the IOA Administrator Guide.) Verifies installation and produces reports on the status of various IOA files (described in Section 9 of the IOA Administrator Guide).
IOAVERFY
6 44
Implementation and Maintenance: Utilities CTMAESIM Test AutoEdit Syntax
CTMAESIM Test AutoEdit Syntax

Utility CTMAESIM simulates the actions of the CONTROL-M submission mechanism. It checks AutoEdit syntax and JCL setup. A command specified in an input statement determines how the simulation works. For more information, see Section 5 of this manual. Parameters The utility receives the following parameters via DD statement DASIM. Either JCL Library Mode parameters or Scheduling Mode parameters (but not both) must be specified to run the utility. These parameters determine the mode in which the utility operates. In addition, the other General simulation parameters should be specified. JCL Library Mode Parameters LIBRARY MEMBER OWNER APPL JCL library name. Member name. Character masking is supported (in batch only). Owner ID. Optional. Name of the application (as specified in field APPL in the job scheduling definition). Optional.
Scheduling Library Mode SCHEDLIB TABLE JOB Notes Name of the library containing the job scheduling definition. Name of the scheduling table containing the job scheduling definition. Name of the job scheduling definition. Character masking is supported. When specifying Scheduling Library Mode parameters, the owner, application name, jobs JCL library and jobs JCL member are not specified because the utility takes these values directly from the specified job scheduling definition. If a value is specified for parameter OVERLIB in the job scheduling definition, that value (instead of parameter MEMLIB) is used as the name of the JCL member.
General Parameters WDATE ODATE SETVAR Working date. Optional. Original scheduling date of the job. Optional. Assigns values to AutoEdit variables (in batch only): In JCL Library mode, parameter SETAVAR assigns AutoEdit variable values without referencing the scheduling library. In Scheduling Library mode, parameter SETAVAR can be used to test values which are not set in the job scheduling definition. $SIGN Assigns a value to the %%$SIGN System variable.
6 45
command
Determines how the simulation works. Valid values: LIST SEND CONTROL-M checks the JCL and writes the results to SYSPRINT only. Same as LIST. This command is supported for reasons of backward compatibility. Command LIST is the preferred command. CONTROL-M checks the JCL and writes the results to both SYSPRINT and to the file referenced by DD statement DASUBMIT. If RDR=INTRDR is specified, the job is submitted for execution and the JCL is also checked by MVS.
SUBMIT
SUBSCAN Same as SUBMIT except that a TYPRUN=SCAN statement is added to the job card. If RDR=INTRDR is specified, the job is submitted but not executed. The JCL is checked by MVS. Any number of members can be submitted for testing in one simulation run. If multiple members are specified, not all parameters need to be specified for each member. The first member always requires a complete set of parameters. Subsequent members require specification of the member name, command, and any parameter statements whose values differ from the values of the preceding member. For all unspecified parameters, the simulation uses the corresponding value provided for the preceding member as the default. Below is an example of multiple member specification where only the member name varies, in JCL Library mode:
OWNER WDATE ODATE MEMBER LIBRARY LIST MEMBER LIST MEMBER LIST member3 member2 owner ID 060698 060698 member1 jcl.library
6 46
Below is an example of multiple member specification where the owner also varies (both member2 and member3 are from owner-b), in JCL Library mode.
OWNER WDATE ODATE MEMBER LIBRARY LIST OWNER MEMBER LIST MEMBER LIST member3 owner-b member2 owner-a 060698 060698 member1 jcl.library
Below is an example of multiple job specification in Scheduling Library mode.

ODATE SCHEDLIB TABLE JOB LIST JOB LIST TABLE JOB LIST scheduling-table2 job name3 job name2 060698 scheduling-library scheduling-table1 job name1
Activating the Utility

// .... JOB .... // EXEC CTMAESIM //DASIM DD *
Return Codes 0 Other Operation performed successfully Operation failed
6 47
Example 1 The following jobs will be checked by CONTROL-M and if no errors are found, they will be submitted (but not executed) and checked by the MVS JCL-checking mechanism.
// . . . JOB . . . // EXEC CTMAESIM,RDR=INTRDR //DASIM DD * USERID SY01 WDATE 060698 ODATE 060698 $SIGN 2 MEMBER JOBDAY01 LIBRARY SYS3.CTM.JOBS SUBMIT OWNER SY01 WDATE 060698 ODATE 060698 MEMBER JOBWEKLY LIBRARY SYS3.CTM.JOBS SUBMIT
Example 2 The following jobs will be checked in Scheduling Library mode and the results will appear in the sysout.
// . . . JOB . . . // . . . EXEC CTMAESIM,RDR=INTRDR //DASIM DD * ODATE 060698 SCHEDLIB SYS3.CTM.JOBS TABLE DEFSCHED3 JOB TAPE01 LIST JOB TAPE02 LIST TABLE DEFSCHD4 JOB JOB1 LIST
6 48
Implementation and Maintenance: Utilities CTMBLDAE Build AutoEdit Symbols Member
CTMBLDAE Build AutoEdit Symbols Member

Utility CTMBLDAE automatically builds an AutoEdit symbols member using an IOA calendar as input. For every scheduled date in the specified calendar, the utility creates one line in an AutoEdit member. The content of this line is determined according to a user-defined generation (GEN) card. The GEN card is a string used to create records in the output member (one record for each scheduled date in the calendar). This utility can be used together with utilities CTMRCAL and IOABLCAL which produce calendars. These calendars can also be used as input to utility CTMBLDAE. Note This utility must be executed outside of the CONTROL-M environment or with a %%RESOLVE OFF AutoEdit statement preceding the SYSIN parameter.
Parameters The parameters for utility CTMBLDAE are specified in blocks in the SYSIN file. Blocks consist of the following mandatory parameters (described below).
CALLIB=input-calendar-library CALMEM=input-calendar-member OUTLIB=output-library OUTMEM=[/]output-member GEN=string ENDCAL
More than one block of parameters can be specified. Each parameter must be specified in each block. However, the parameters in each block may be specified in any order. Note In a parameter block, each parameter should be specified only once. However, if a parameter is specified more than once in a block, only the last occurrence of the parameter in the block is accepted.
If more than one parameter block is specified, each parameter block must be delimited by parameter ENDCAL. Comment lines can be specified by coding * in column 1.
Blocks of parameters are specified in the following format: CALLIB CALMEM OUTLIB OUTMEM Name of the library containing the calendar to be used as input to the utility. Name of the member containing the calendar to be used as input to the utility. Name of the library to which the AutoEdit member created by the utility should be written. Name to be assigned to the AutoEdit member created by the utility.
6 49
GEN
String which forms the basis of the AutoEdit variables created by the utility. The usual format for this string is:
variable=expression
where: variable expression User-defined AutoEdit variable. Value or expression which resolves to a specific value.
The variable and/or the expression can contain any of the following reserved words (substrings) which are replaced with the corresponding date values: ODAT NEXT PREV ODAY OMONTH OYEAR $ODAT $NEXT $PREV $OYEAR $OCENT Date scheduled in the calendar in yymmdd format. Next date scheduled in the calendar in yymmdd format. Previous date scheduled in the calendar in yymmdd format. Day scheduled in the calendar in dd format. Month scheduled in the calendar in mm format. Year scheduled in the calendar in yy format. Date scheduled in the calendar in yyyymmdd format. Next date scheduled in yyyymmdd format. Previous date scheduled in the calendar in yyyymmdd format. Year scheduled in the calendar in yyyy format. The first two digits in the yyyy date format (e.g., 19 in 1998).
Note
Values PREV, $PREV, NEXT and $NEXT are relative expressions that are intended for use with ODATE and/or other date expressions.
ENDCAL
Delimits parameter blocks. Mandatory.
Handling Duplicate Members Using PARM=MERGE If the user specifies the same output member (i.e., the same OUTLIB/OUTMEM combination) in more than one block, normally only the results of the last occurrence of that member are saved. To retain the results of all occurrences of that output member, the user should specify PARM=MERGE in the JCL EXEC statement. If this statement is specified, the results of each occurrence of the output member are concatenated in the member. If the OUTMEM parameter is specified as OUTMEM=/member-name, PARM=MERGE is ignored for the block.
6 50

// // EXEC CTMBLDAE
Return Codes 0 8 and above Example 1

// EXEC CTMBLDAE //SYSIN DD * CALLIB=CTM.PROD.CAL CALMEM=PAYROLL OUTLIB=CTM.PROD.SYMBOLS OUTMEM=PAYCHECK GEN=%%DATE_TYPE_OF_ODAT=REGULAR //
Operation performed successfully Operation failed
Input calendar PAYROLL looks as follows (in January 1999):
-----S-------------S-------------S-------------S-------------S-------------S--1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 2 3 4 5 6 7 8 9 + 1 09 Y Y Y Y -----S-------------S-------------S-------------S-------------S-------------S---
An AutoEdit table named PAYCHECK is created:

%%DATE_TYPE_OF_990908=REGULAR %%DATE_TYPE_OF_990915=REGULAR %%DATE_TYPE_OF_990922=REGULAR %%DATE_TYPE_OF_990929=REGULAR
Example 2 A job requires as input a dataset whose name contains the date PREFIX.%%RL%% created on the date of the programs last run. The JCL for the job contains the following statements:
//JCL JOB //* %%LIBSYM CTM.PROD.SYMBOLS %%MEMSYM RLPREVD // EXEC PGM=RLPGM //SYSUT1 DD DSN=PREFIX.%%RL%%ODATE,DISP=SHR //SYSUT2 DD DSN=PREFIX.%%RL%%ODATE,DISP=(NEW,CATLG)
Utility CTMBLDAE is submitted with the following statements:

%%RESOLVE OFF CALLIB=CTM.PROD.CAL CALMEM=RLRUN OUTLIB=CTM.PROD.SYMBOLS OUTMEM=RLPREVD GEN=%%RLODAT=RLPREV
6 51
Input calendar RLRUN looks as follows (in January 1999):
An AutoEdit symbols member named RLPREVD is created:

%%RL990907=RL990831 %%RL990914=RL990907 %%RL990921=RL990914 %%RL990928=RL990921 %%RL991005=RL990928
The submitted JCL DD statements on January 14, 1999:

//SYSUT1 //SYSUT2 DD DD DSN=PREFIX.RL990907,DISP=SHR DSN=PREFIX.RL990914,DISP=(NEW,CATLG)
Example 3 For JOB2, CTMBLDAE merges all the GEN statements for member PAYCHECK.
//JOB2 JOB // EXEC CTMBLDAE,PARM=MERGE //SYSIN DD * CALLIB=CTM.PROD.CAL CALMEM=PAYROLL OUTLIB=CTM.PROD.SYMBOLS OUTMEM=PAYCHECK GEN=%%DATE_TYPE_OF_ODAT=REGULAR ENDCAL CALLIB=CTM.PROD.CAL CALMEM=PAYROLL OUTLIB=CTM.PROD.SYMBOLS OUTMEM=PAYCHECK GEN=%%DATE_TYPE_OF_$ODAT=REGULAR ENDCAL CALLIB=CTM.PROD.CAL CALMEM=PAYROLL OUTLIB=CTM.PROD.SYMBOLS OUTMEM=PAYCHECK GEN=%%DATE_TYPE_OF_ODAT_NEXT=REGULAR ENDCAL //
6 52
Input calendar PAYROLL looks as follows (in January 1999):
An AutoEdit table named PAYCHECK is created:

%%DATE_TYPE_OF_990908=REGULAR %%DATE_TYPE_OF_990915=REGULAR %%DATE_TYPE_OF_990922=REGULAR %%DATE_TYPE_OF_990929=REGULAR %%DATE_TYPE_OF_19990908=REGULAR %%DATE_TYPE_OF_19990915=REGULAR %%DATE_TYPE_OF_19990922=REGULAR %%DATE_TYPE_OF_19990929=REGULAR %%DATE_TYPE_OF_990908_990915=REGULAR %%DATE_TYPE_OF_990915_990922=REGULAR %%DATE_TYPE_OF_990922_990929=REGULAR
6 53
Implementation and Maintenance: Utilities CTMBLT Create Scheduling Tables
CTMBLT Create Scheduling Tables

Utility CTMBLT automatically builds CONTROL-M scheduling tables (containing job scheduling definitions) according to a set of specified input statements, and optionally orders or forces them. This utility replaces the CTMJOB macro used prior to CONTROL-M Release 5.0.0 to define jobs. The utility builds scheduling tables which can contain multiple job scheduling definitions. At least one scheduling table must be defined in each library specified. At least one job scheduling definition must be defined in each table. See Activating the Utility for a description of other output files created by the utility. Parameters Utility CTMBLT receives parameters from an input file referenced by DD statement DAINPRM. The syntax of the input statements is:
[LIBRARY=libraryname {MEM-OVERWRITE=Y|N|ADD|ORDER|FORCE} {ADD-GLOBAL=Y|N} [ TABLE=tablename {Global Parameter Statements} [ MEMNAME=jobname Mandatory Local Parameter Statements {Optional Local Parameter Statements} ] ] ]
Note the following points about the above syntax:
Parameters enclosed in braces { } are optional. Parameters not enclosed in braces { } are mandatory.
1
The set of parameters enclosed in a matching pair of brackets [ ] can be specified more than once. The line length is 80. The first 79 characters may contain parameters and/or comments. Parameters can start in any column of the line. No spaces should be included between keywords and parameters. One parameter is permitted per line. Subparameters can follow a main parameter on the same line, separated from the main parameter by a comma. Comments can be placed on the same line, separated from the parameter by a space.
Mandatory parameters do not need to be defined locally if their corresponding Global definitions have been provided.
6 54
The parameters specified in the input file are divided into two groups:
General Parameters These parameters specify scheduling library names (LIBRARY), scheduling table names (TABLE), and job scheduling definition names (MEMNAME). This group of parameters also contains two control parameters (MEM-OVERWRITE and ADD-GLOBAL) described below.
Job Scheduling Definition Parameters These parameters correspond to the parameters of the Job Scheduling Definition screen. They can be defined in two ways: Local Global Apply only to the job scheduling definition for which they are specified. Apply to all job scheduling definitions in the table in which they are specified.
The sequence in which the parameters appear in the input file is important as it determines:
Which job scheduling definition belongs in which table, and which table belongs in which library. Whether job scheduling definition parameters are interpreted as Global or Local.
The parameters of the input file are described below, according to group. General Parameters LIBRARY Name of the library in which the scheduling table is saved. Mandatory.
Parameter LIBRARY must be specified as the first input parameter to

the utility.
Parameter LIBRARY must be followed by at least one TABLE

parameter.
The
LIBRARY parameter applies to all subsequent TABLE parameters until another LIBRARY parameter or the end of the input file is encountered .
6 55
MEM-OVERWRITE Determines how the table (and its jobs) should be handled. This parameter can be specified only once per LIBRARY= control parameter and, if specified, must be placed before the first TABLE parameter. Valid values: Y N Overwrite the current table if a table with the same name already exists in the library. Do not overwrite the current table if a table with the same name already exists in the library. Display an error message. Default. If the table does not exist, it is added to the library. If a table with the same name already exists, the new jobs are added to the existing table.
ADD
ORDER/FORCE Do not write the table to a library. Directly order/force jobs to the Active Jobs file without creating CONTROL-M job scheduling definitions. Warning Exercise caution if specifying Y in this parameter because the old contents of all overwritten members will be irretrievably lost.
ADD-GLOBAL
Controls processing when job scheduling definition parameters have both Local and Global definitions. This parameter is relevant only for job scheduling definition parameters which can be specified more than once in a job definition. For all other job scheduling definitions, only the Local definition is used. Local parameter definitions are always applied. This parameter determines whether or not Global definitions will be added to the Local definitions. This parameter can be specified only once per LIBRARY= Control parameter and must be placed before the first TABLE parameter. Valid values: Y N Add Global parameter definitions after the Local parameter definitions. Default. Ignore Global parameter definitions. are both specified,
Note
If parameters MEM-OVERWRITE and ADD-GLOBAL MEM-OVERWRITE must be specified before ADD-GLOBAL.
6 56
TABLE
Name of the scheduling table (member) to be created.
A table name should be a valid partitioned dataset (PDS) member

name.
At least one TABLE parameter must be specified after each LIBRARY

parameter.
At least one MEMNAME parameter (identifying a job scheduling

definition) must follow each TABLE parameter.
The TABLE parameter applies to all subsequent job scheduling

definitions until the next TABLE parameter or the end of the input file is encountered. MEMNAME JCL member name of the job (and therefore the name of the job 2 scheduling definition). Since each job scheduling definition applies to a specific JCL member, the name assigned to the job scheduling definition is the name of the JCL member. At least one MEMNAME parameter must be specified after each TABLE parameter. Each occurrence of parameter MEMNAME indicates the beginning of a new job scheduling definition. Job Scheduling Definition Parameters These parameters correspond to the parameters of the CONTROL-M Job Scheduling Definition screen. For a detailed description of what each parameter does, refer to Section 3. Each parameter is briefly described in the Job Scheduling Definition Parameter Tables later in this section. Parameters IN, CONTROL, RESOURCE and OUT can be repeated by specifying more than one value for the parameter. Example:
IN=(condname,date,condname,date...)
Multiple occurrences for job scheduling definition parameters can also be defined (when permitted) by repeating the keyword for each occurrence. Example:
SETVAR=%%A=%%ODAT SETVAR=%%B=53
Normally, these parameters are defined for the specific job scheduling definition in which they appear (i.e., they are defined as Local). To simplify specification of the input parameters for the utility, all job scheduling definition parameters in a table (except MEMNAME, which is treated as a General parameter) can also be defined as Global. These Global definitions are used as defaults for all jobs in the table. Global definition of specific parameters is achieved by placing such parameters between the TABLE parameter and the first MEMNAME parameter in the table.
Although MEMNAME is a job scheduling definition parameter, it is included here as a general parameter because it determines the name of the job scheduling definition and it cannot be defined globally.
6 57
If both Global and Local values for a parameter are specified, the value of the Local parameter is used. The Global parameter definition may or may not be used depending on the following:
For parameters that do not permit multiple occurrences, the Local value is used and the Global value is ignored. For parameters that permit multiple occurrences: If Local values appear and N was specified in parameter ADD-GLOBAL, Global values are ignored. If Y was specified in parameter ADD-GLOBAL, Global values are used in addition to Local values.
Parameters MEMLIB and OWNER are mandatory and must be defined either locally or globally. Input job scheduling definition parameters (Global and Local) are validated in the same manner as in the online environment. The validation checks which are applied are CONTROL-M release-dependent. Calling CTMBLT from Another Program CTMBLT can be called from another program. The calling program passes required control statements to CTMBLT via a table residing in memory (rather than from a dataset referenced by DD statement DAINPRM). To call CTMBLT from another program and pass to CTMBLT a table of control statements residing in memory, three parameters must be specified in the calling statement: nnn linecount taddress Number of parameters that follow (valid value must be 2). This parameter must be a Halfword. Number of control statements being passed to CTMBLT. This parameter must be a Fullword. Address of the the table residing in memory. This table contains CTMBLT control statements (each element in the table must be an 80byte, card image).
For example, in Assembler the following statement format would be used:

CALL CTMBLT,(nnn,linecount,taddress)
If CTMBLT is unable to build a job scheduling table, a non-zero return code is placed in register 15 (R15) and an error message is written to the file referenced by DD statement DAMSG. Building Tables in Memory Followed by Immediate Ordering CTMBLT can create job scheduling tables in memory (instead of in a scheduling library) and ORDER or FORCE them. This functionality enables users to ORDER or FORCE jobs to the Active Jobs file without saving CONTROL-M job scheduling definitions in a scheduling library.
6 58
To create scheduling tables in memory and then ORDER or FORCE them, use the same parameters as when creating scheduling tables in a library. However, note the following syntax points:
LIBRARY=libname
This parameter must be specified but since no library is actually being created or accessed, any name can be specified.
MEM-OVERWRITE={ORDER|FORCE}[({SDATE|WDATE|yymmdd})] The MEM-OVERWRITE= statement must be specified in the above syntax. An ORDER or
FORCE action must be specified, followed by one of the following date references:
WDATE SDATE yymmdd
Current CONTROL-M working date (Default). Current system date. Any valid 6 character date.
When specifying ORDER or FORCE the following DD statements must be included in the execution JCL: DALOG DACAL DACKPT SYSPRINT DASTAT DAUNITDF IOA LOG file. IOA Calendar library (if jobs specify DCAL, WCAL or CONFCAL parameters). CONTROL-M Active Jobs file. SYSOUT message file. CONTROL-M Statistics file. Optional. Tape drive unit addresses for CONTROL-M Automatic Tape Drive Adjustment. Optional.
Note
If either DASTAT or DAUNITDF DD statements are omitted from the JCL, Automatic Tape Drive Adjustment will not be operative.
6 59

// job card //S1 EXEC PGM=CTMBLT,REGION=0K //STEPLIB DD DISP=SHR,DSN=ioa.loadlib //DAMSG DD SYSOUT=* //DATABERR DD error-file //DAINPRM DD parameter-file
Considerations
DD statement STEPLIB is only necessary if CTMBLT does not reside in a system link-listed library. The file referenced by DD statement DAMSG holds all messages produced by the utility. This file can alternatively be specified as a dataset instead of a sysout print file. The file referenced by DD statement DATABERR holds parameters from the file referenced by DD statement DAINPRM which could not be processed due to syntax errors or other errors. Parameters in the file referenced by DD statement DAINPRM can be specified either as in-stream data or as 80-byte card image data. It is unnecessary to specify DD statements for scheduling libraries because the utility dynamically allocates job scheduling libraries according to parameter LIBRARY.
Return Codes 0 8 Utility CTMBLT ended successfully An error occurred while analyzing the input stream See the output referenced by DD statement DAMSG for a message indicating the cause of the problem. Correct the definitions and resubmit the job. 12 Severe error Check the output of the job for messages indicating the source of the problem. If you are unable to correct the problem, contact your IOA administrator. Note To create Group scheduling tables, first create standard scheduling tables via utility CTMBLT, and then process the tables via utility CTMBGRP.
Example 1 The following example creates two scheduling tables (INITJOBS and PRDDAILY) in the CTM.PROD.SCHEDULE library. In table INITJOBS, two job scheduling definitions (PNADCICW and PNADCIC1) are created. In table PRDDAILY, one job scheduling definition (CHKACC) is created. Global parameters GROUP=INIT-JOBS-1 and MEMLIB=GENERAL are defined for table INITJOBS, and apply to the two job scheduling definitions in that table. They are identified as Global definitions because they are positioned between parameter TABLE=INITJOBS and parameter MEMNAME=PNADCICW, which is the first MEMNAME parameter in the table.
6 60
//BUILD EXEC PGM=CTMBLT //STEPLIB DD DISP=SHR,DSN=<IOA-LOAD-LIBRARY> //PUNCH DD SYSOUT=* //DAMSG DD SYSOUT=* //DATABERR DD SYSOUT=* //DAINPRM DD * LIBRARY=CTM.PROD.SCHEDULE MEM-OVERWRITE=N ADD-GLOBAL=Y TABLE=INITJOBS GROUP=INIT-JOBS-1 MEMLIB=GENERAL MEMNAME=PNADCICW OWNER=OPSUSER DESC=CO - POST ONLINE COPY IMAGE FOR PHASE3 IN=(PNADCICW-OK,PREV) OUT=(PNADCICW-OK,ODAT,+) MEMNAME=PNADCIC1 OWNER=OPSUSER OUT=(PNADCIC1-OK,ODAT,+) TABLE=PRDDAILY MEMNAME=CHKACC MEMLIB=GENERAL OWNER=OPSUSER TASKTYP=JOB GROUP=CHECK-ACCOUNTS WDAYS=(2,3,4,5) IN=(PNADCICW-OK,ODAT) ONPGM STEP=ANYSTEP CODES=NOTOK DO=SYSOUT SYSOUT-OP=C SYSOUT-FRM=R SYSOUT-PRM=M SHOUT-WHEN=NOTOK DEST=OPER-12 MSG=JOB CHKACC HAS AN ERROR CHECK IT URG=U CTBSTART CTBS-TYPE=RULE CTBS-NAME=CHKBRL CTBS-ARGS=1 TO 45 CHARS CTBEND CTBETYPE=MISSION CTBE-NAME=ENDMI1 CTB-ARGS=1 TO 45 CHARS
6 61
Example 2 In the following example, the MEM-OVERWRITE statement indicates that scheduling tables TABLE1 and TABLE2 are created in memory and immediately ordered. In table TABLE1, a job scheduling definition, MYMEM1, is created and then ordered. In table TABLE2, a job scheduling definition, MYMEM2, is created and forced. (Both jobs are ordered or forced without saving external job scheduling definitions.)
//S1 EXEC PGM=CTMBLT,REGION=0K //STEPLIB DD DISP=SHR,DSN=ioa.loadlib //DAMSG DD SYSOUT=* //DAPRINT DD SYSOUT=* //DATABERR DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSPRINT DD SYSOUT=* //DACKPT DD DISP=SHR,DSN=ctm.ajf //DALOG DD DISP=SHR,DSN=ioa.log //DACAL DD DISP=SHR,DSN=ioa.calendar.lib //DASTAT DD DISP=SHR,DSN=ctm.statfile //DAUNITDF DD DISP=SHR,DSN=ctm.parm(UNITDEF) //DAINPRM DD * LIBRARY=name1 MEM-OVERWRITE=ORDER(WDATE) ADD-GLOBAL=Y TABLE=TABLE1 GROUP=GROUP1 MEMLIB=GENERAL MEMNAME=MYMEM1 OWNER=CTMBLT DESC='ORDER JOB MYMEM1 DAYS=ALL OUT=(MYMEM1-OK,ODAT,+) LIBRARY=name2 MEM-OVERWRITE=FORCE TABLE=TABLE2 GROUP=GROUP2 MEMLIB=GENERAL MEMNAME=MYMEM2 OWNER=CTMBLT DESC='FORCE JOB MYMEM2' IN=(MYMEM1-OK,ODAT) //
(Since the tables are created in memory, any library name can be specified. It does not need to correspond to an actual library or file.)
6 62
Example 3 The following, simplified example calls CTMBLT from another program and passes required control statements to CTMBLT. CTMBLT uses a table in memory to force job MYJOB. In this example, a DAINPRM DD statement was not needed to execute the JCL. (Usually situations require CTMBLT control statements to be read from an external file or dynamically constructed into a GETMAINed area within the program.)
CALL CTMBLT,(TWO,LINECNT,TBLADDR) LTR R15,R15 BNZ error-routine ... TWO DC H2 LINECNT DC F6 NUMBER OF CTMBLT CONTRL STATEMENTS TBLADDR DC A(INCORETB) INCORETB DS 0CL80 TABLE OF CTMBLT CARD-IMAGE CONTROL STATEMENTS DC CL80LIBRARY=*INCORE* DC CL80MEM-OVERWRITE=FORCE DC CL80TABLE=MYTABLE DC CL80MEMLIB=GENERAL DC CL80MEMNAME=MYJOB DC CL80OWNER=CTMBLT
Job Scheduling Definition Parameter Tables The following parameters can be defined as Local or Global parameters. Note the following:
A + in Column + indicates that multiple occurrences are allowed. An M in Column M indicates that the parameter is mandatory.
6 63
Table 1: General Job Definition PARAMETER MEMLIB OWNER TASKTYP + M M M VALUE 1-44 characters 1-8 characters 3 characters JOB (Default) CYC EMR ECJ STC CST EST ECS PREVENT-NCT2 APPL GROUP DESC OVERLIB SETVAR + Y/N/F/L/blank (Default: blank) 1-20 characters 1-20 characters 1-50 characters 1-44 characters 1-66 characters %%varname=value DESCRIPTION Library containing JCL member User-identification Type of procedure Regular job Cyclic job Emergency job Emergency cyclic job Started task (STC) Cyclic started task Emergency started task Emergency cyclic STC Prevent NOT CATLGD 2 errors Application name Group name Description of job Overriding JCL library name Set AutoEdit value If value contains delimiter characters (e.g., commas), enclose the entire parameter text in quotes or apostrophes (e.g., %%varname=value). Documentation member
DOCMEM
1-8 characters Default: same as MEMNAME; To leave DOCMEM blank, specify DOCMEM = /
DOCLIB
1-44 characters
Documentation library
6 64
Table 2: Scheduling Criteria PARAMETER DAYS PERIOD DCAL RELATION WDAYS WPERIOD WCAL MONTHS + + + + + + M VALUE 1-3 characters See Section 3 4-5 characters (DnPi/LnPi) 1-8 characters A/O 1-4 characters See Section 3 4-5 characters (DnPi/LnPi) 1-8 characters DESCRIPTION Scheduling days Periodic scheduling days DAYS calendar name AND/OR relation between DAYS/WDAYS Weekly scheduling days Periodic weekly scheduling days WDAYS calendar name
1-3 characters MONTHS scheduling 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, ALL. (Default: all values)
DATES CONFCAL SHIFT
4 characters 1-8 characters 4 characters blank < > @ 2-3 characters blank nn +nn
DATES scheduling Confirmation calendar name Shift on confirmation calendar No shift Shift one workday back Shift one workday forward Ignore confirmation Additional shift No additional shift Shift n days backward Shift n days forward Retroactive selection Maximum days job is retained
RETRO MAXWAIT
Y/N (Default: N) 2 digits (00...98,99) Default: 00
6 65
PARAMETER D-CAT MINIMUM PDS IN
VALUE 1-20 characters 3 digits 1-44 characters
DESCRIPTION Category for CONTROL-D Minimum tracks left free Full name of PDS Library to be checked IN condition Name of IN condition Date reference of IN condition
(cond,date) cond 1-20 characters date 4 characters
Boolean characters |( } Note: Closing parenthesis ) is not supported. Instead of this character, use the closing brace } (hex value D0) CONTROL + (control,type) control 1-20 characters type S/E Control resource Name of Control resource Usage type: Shared/ Exclusive Quantitative resource Name of resource Quantity of resource CONTROL-M/WorkLoad 3 pipe name Earliest time to submit job Latest time to submit job Submit as soon as possible Priority Time by which the job should finish executing
RESOURCE
(resource,number) resource 1-20 digits number 4 characters
PIPE
pipe name (1 to 44 characters) hhmm hhmm >
TIMEFROM TIMEUNTIL
PRIORITY DUE-OUT
1-2 characters hhmm
This field is supported only if CONTROL-M/WORKLOAD is installed at your site
6 66
PARAMETER CONFIRM CTBSTART CTBS-TYPE
VALUE Y/N none RULE/MISSION
DESCRIPTION Confirmation for scheduling Define CONTROL-B step as first job step Type of CONTROL-B entity associated with the CTBSTART step Name of the CONTROL-B mission or rule associated with the CTBSTART step Arguments passed to CONTROL-B
CTBS-NAME
1-8 characters
CTBS-ARGS CTBEND CTBE-TYPE
1-45 characters within apostrophes
RULE/MISSION
Type of CONTROL-B entity associated with the CTBEND step Name of the CONTROL-B mission or rule associated with the CTBEND step Arguments passed to CONTROL-B
CTBE-NAME
1-8 characters
CTBE-ARGS
1-45 characters within apostrophes
6 67
Table 3: Post-Processing Parameters PARAMETER OUT + + M VALUE (out,date,option) out date 1-20 characters 4 characters Name of OUT condition Date reference Function: ADD/DELETE Archive SYSDATA DESCRIPTION
option +/AUTOARC Y (Default) N SYSDB Y (Default) N MAXDAYS MAXRUNS SYSOUT-OP SYSOUT-FRM SYSOUT-PRM 2 digits 3 digits 1 character (C,F,N,D,R) 1 character For SYSOUT-OP: C 1 character F 1-44 characters N 8 characters D none R none MAXRERUN RERUNMEM INTERVAL RET-DAYS RET-GENS STEPRNG FROMPGM FROMPROC TOPGM + 1 character 1-8 characters 3 digits 3 digits 2 digits 1-7 characters 1-8 characters 1-8 characters 1-8 characters
Archive to common dataset
Expiration period Max number of runs SYSOUT option SYSOUT option FROM CLASS SYSOUT parameter according to SYSOUT option SYSOUT-OP
Maximum number of reruns Name of rerun job Minutes between reruns Retention number of days Retention number of generations Step Range name FROM PGM STEP in step range FROM PROC STEP in step range TO PGM STEP in step range
6 68
PARAMETER TOPROC ONPGM STEP PROCS CODES ON-RELATE DO=action DO=COND CONDS DO=FORCEJOB FORCE-TAB FORCE-JOB FORCE-DATE FORCE-LIB DO=IFRERUN IFRERN-FROM IFRERN-TO IFRERN-CONF DO=CTB CTB-RULE CTB-ARG DO=SET SETVAR DO=SHOUT MSG DEST
VALUE 1-8 characters
DESCRIPTION TO PROC STEP in step range Identifies the beginning of an ON block
+ + + + + + 1-8 characters 1-8 characters (5 chars,5 chars,...) A/O OK,NOTOK,RERUN (no subparameters)
PROGRAM STEP name for ON block PROC STEP name for ON block ON block codes AND/OR relation DO action performed if ON block is performed
(out,date,option)
OUT condition
1-8 characters 1-8 characters 6 characters 1-44 characters
Table name Job name Date Library name
1-16 characters 1-16 characters Y/N
From To Confirm
1-45 characters 1-36 characters
Rule name Arguments
1-66 characters %%varname=value
See earlier SETVAR
1-55 characters 1-16 characters
SHOUT message SHOUT destination
6 69
PARAMETER URG
VALUE 1 character (R,U,V)
DESCRIPTION SHOUT urgency This subparameter must always be the last subparameter in the block, (i.e., after TIME, MSG, and DEST).
DO=SYSOUT SYSOUT-OP SYSOUT-FRM SYSOUT-PRM 1 character (C,F,N,D,R) 1 character For SYSOUT-OP: C 1 character F 1-44 characters N 8 characters D none R none SHOUT-WHEN TIME + OK/NOTOK/EXECTIME. .. 4 characters Indicates start of SHOUT block SHOUT on LATE/LATESUB/EXECTIME. Defaults to 0000 when no TIME value is specified for the LATE/LATESUB parameters. This subparameter must precede subparameter DEST. SHOUT message SHOUT destination SHOUT urgency This subparameter must always be the last subparameter in the block, (i.e., after TIME, MSG, and DEST). SYSOUT option SYSOUT option FROM CLASS SYSOUT parameter according to SYSOUT option SYSOUT-OP
MSG DEST URG
1-70 characters 1-16 characters 1 character (R,U,V)
6 70
Implementation and Maintenance: Utilities CTMJOB Order Jobs to the Active Jobs File
CTMJOB Order Jobs to the Active Jobs File

CTMJOB is a job ordering utility which can be invoked from one of the following:
Job step Called program from a TSO environment and/or application program (e.g., batch, CICS).
Job ordering instructions are passed to CTMJOB via one of the following:
DD statement DAJOB. When ordering jobs via DD statement DAJOB, job orders can be specified either: By concatenating scheduling tables in the JCL (Method 1) This method requires that the user specify the name of a scheduling table and library directly in the JCL, in format DSN=sched_library(table). For example:
//step EXEC PGM=CTMJOB //DAJOB DD DISP=SHR,DSN=sched_library(table1) // DD DISP=SHR,DSN=sched_library(table2) // DD DISP=SHR,DSN=sched_library(table3)
As ORDER control statements (Method 2)

//step EXEC PGM=CTMJOB //DAJOB DD DISP=SHR,DSN=parm_library(member)
where member contains ORDER, SELECT, IGNORE statements. -or//step EXEC //DAJOB ORDER . . . [SELECT TAG [IGNORE TAG . . . PGM=CTMJOB DD * tagname1] tagname2]
Format of the ORDER, SELECT and IGNORE statements is described below. Method 2 provides the following advantages over Method 1: Changes required can be made to the member in the PARM library without changing the JCL. Individual jobs can be specified.
PARM parameter in an EXEC statement in the JCL. This method can only be used for ordering a single table or job. See Activating the Utility below for an example.
6 71
Format of the ORDER, SELECT, and IGNORE Statements ORDER, SELECT and IGNORE statements must be in the following format:
ORDER {DSN=schedlib|DDNAME=dd|DD=dd},{MEMBER=table|MEM=table}[,JOB=jobnm] [,ODATE=date|DATE=date][,FORCE] [SELECT TAG tagname1] [IGNORE TAG tagname2]
At least one ORDER statement must be specified. SELECT/IGNORE statements are optional. Multiple statements of each type are permitted. Parameters ORDER Indicates a specific table member (or job) to be ordered. DSN=schedlib Name of the scheduling library. Either this parameter or parameter DDNAME=, but not both, must be specified.
DDNAME=dd | DD=dd Pre-allocated ddname which points to the scheduling library. Either this parameter or parameter DSN=, but not both, must be specified. MEMBER=table | MEM=table Name of the scheduling table which contains the job scheduling definitions. Mandatory. JOB={jobnm | *} Name of a job scheduling definition in the scheduling table. Optional. If a job name is not specified, or if an asterisk (*) is specified, the entire table is processed. ODATE={date | ODATE | DATE} | DATE={date |ODATE | DATE} Order date of the job(s) in the table (in mmddyy, ddmmyy, or yymmdd format, depending on the site standard). This parameter overrides the checkpoint date specified in DD statement DACHK. Optional. The default is the date from the checkpoint record. Valid values: date Specific order date in mmddyy, ddmmyy, or yymmdd format (depending on the site standard). CONTROL-M working date. System date.
ODATE DATE FORCE
Places the job(s) order in the Active Jobs file regardless of the jobs Basic Scheduling parameters. Optional.
6 72
SELECT TAG tagname/IGNORE TAG tagname Schedule Tags whose associated jobs should or should not be ordered. A Schedule Tag is a set of Basic Scheduling criteria specified in a Group Entity which is used to schedule specific jobs in the Group Definition table. (For more information, see the description of parameter SCHEDULE TAG in Section 3 of this manual.) SELECT TAG/IGNORE TAG statements can be specified only if the table specified in the preceding ORDER statement is a Group Scheduling table.
SELECT TAG statements indicate Schedule Tags to be used to select

jobs to be ordered.
IGNORE TAG statements indicate Schedule Tags to be used to

prevent jobs from being ordered. Each SELECT TAG statement or IGNORE TAG statement must appear on a separate line. Each block of SELECT TAG/IGNORE TAG statements must be preceded by an ORDER statement. An asterisk (*) can be included as a masking character for the suffix of the Schedule Tag name (or for the entire Schedule tag name). (See Character Masking in Section 2 of this manual for more information.) Any number of SELECT TAG and IGNORE TAG statements can be specified. SELECT/IGNORE TAG Logic By default, all Schedule Tags for the Group Entity in the specified Group Scheduling table are selected. Therefore, to ignore specific Schedule Tags and select all others, you need only specify the appropriate IGNORE TAG statement. (See Example 1 under SELECT/IGNORE TAG Examples below.) If a Schedule Tag name matches more than one SELECT TAG/IGNORE TAG statement, the first statement which matches the Schedule Tag name is applied. To select specific Schedule Tags and ignore all others, first indicate the specific Schedule Tags to be selected in SELECT TAG statements and then specify a generic IGNORE TAG statement as the last statement in that SELECT TAG/IGNORE TAG block. (See Example 2 under SELECT/IGNORE TAG Examples below.) The scheduling of specific jobs depends on whether or not optional keyword FORCE is specified in the preceding ORDER statement:
If FORCE is not specified, Schedule Tags specified in an IGNORE TAG statement are treated as if their basic scheduling criteria are not satisfied (i.e., no jobs are scheduled according to these tags). A job is scheduled when either of the following is true for the jobs scheduling definition: O (Or) is specified for parameter RELATIONSHIP; and the basic scheduling criteria and/or the scheduling criteria of a selected Schedule Tag associated with the job are satisfied. A (And) is specified for parameter RELATIONSHIP; and both the basic scheduling criteria and the criteria of a selected Schedule Tag are satisfied.
6 73
Note
If no Schedule tag is specified for a job, the scheduling of that job is dependent only on the basic scheduling criteria of the job.
If FORCE is specified, a job is scheduled if either of the following conditions exists: At least one of the selected Schedule Tags is associated with the job. No Schedule Tags were specified in the job scheduling definition. Example 1
ORDER DSN=mylib,MEMBER=sample IGNORE TAG ACCT*
Ignores all Schedule Tags with a prefix of ACCT. All other Schedule Tags are automatically selected. Example 2
ORDER DSN=mylib,MEMBER=sample SELECT TAG ACCT1 SELECT TAG ACCT2 IGNORE TAG *
Selects only Scheduled tags ACCT1 and ACCT2 and ignores all others. Activating the Utility
//S1 EXEC //STEPLIB //DALOG //DACHK //DACHK //SYSPRINT //DAJOB PGM=CTMJOB[,PARM=parameters] DD DISP=SHR,DSN=ioa.loadlib DD DISP=SHR,DSN=ioa.log DD DISP=SHR,DSN=ctm.daterec DD DISP=SHR,DSN=ctm.ajf DD message file DD scheduling tables or ORDER statements
Note the following:
DD statement STELIB is only necessary if CTMJOB does not reside in a system linklisted library. DD statement DACHK, which references the Date Control record, is described in detail in Implementing New Day Processing earlier in this section. The file referenced by DD statement SYSPRINT holds all messages produced by the utility. This file can alternatively be specified as a dataset or a system print file. DD statement DAJOB is described in detail on the first page of this utility description. When activating the utility, parameter PARM=NODACHK can be specified in the EXEC statement. When PARM=NODACHK is specified, the Date Control record is ignored (and DD statement DACHK is unnecessary).
Note
Examples
The following example shows how to specify job order statements using the PARM statement in the EXEC card:
//ORDERJOB EXEC PGM=CTMJOB, // PARM=ORDER DSN=IOA.PROD.SCHEDULE TABLE=TABLE1 JOB=SORT ODATE=070798
6 74
To invoke CTMJOB from a batch assembler program, specify the call as shown below:
CALL CTMJOB,(JOBPARM),VL . . JOBPARM DC Y(LORDERREQ) ORDERREQ DC CORDER DSN=IOA.PROD.SCHEDULE TABLE=TABLE1 JOB=SORT DATE=070798
To invoke CTMJOB from TSO, issue the following command:

CALL ioa.prod.load(CTMJOB) ORDER DSN=IOA.PROD.SCHEDULE TABLE=TABLE1 JOB=SORT,DATE=070798
The following example shows how to specify job order statements via DD statement DAJOB.
//ORDERJOB EXEC PGM=CTMJOB //ORDERDD DD DSN=IOA.PROD.SCHEDULE DISP=SHR //DAJOB DD * ORDER DDNAME=ORDERDD MEMBER=TABLE1 FORCE ORDER DDNAME=ORDERDD MEMBER=TABLE2 ORDER DDNAME=ORDERDD MEMBER=TABLE3 JOB=JOB1 . . . //
To invoke CTMJOB from a CICS application, parameters should be passed to the API CTMCIOR via a COMMAREA described by the DSECT CTMCIAOR. (The API and DSECT can be found in the IOA CICSSAMP library.) Program CTMCIOR passes the parameters to CTMJOB. The following example shows how the API is called from a CICS application using fields defined in the DSECT.
PARMAREA DS PARMARLN EQU MVC MVC MVC MVC EXEC (CMORDLEN)C *-PARMAREA CMORDDSN,DSNAME PARAMETERS CMORDTBL,TBLNAME CMORDJOB,JOBNAME CMORDDAT,DATE CICS LINK PROGRAM (CTMCIOR) COMMAREA (PARMAREA) LENGTH (=Y(PARMARLN)) . . . DC CL44CTM.PROD.SCHEDULE DC CL8DEFSCHD1 DC CL8JOBA DC CL6090998
* *
DSNAME TBLNAME JOBNAME DATE
Return Codes 0 4 Operation performed successfully At least one job was not ordered because of: missing calendar, PREV / NEXT date conditions missing, Exit1 cancelled the order, or no job orders were requested Operation failed
8 and above
6 75
Implementation and Maintenance: Utilities CTMRCAL Produce a Job Plan Report
CTMRCAL Produce a Job Plan Report

This utility produces a Job Plan report for one or more jobs. For each job in the plan, it creates a calendar which contains all the dates on which the job is scheduled to execute during the plans time frame. The name of the calendar created for each job scheduling definition is the name of the job in parameter MEMNAME. This calendar is completely valid for all purposes. It can be viewed using Option 8 (Calendars) of the IOA Primary Option menu and it can be used by any CONTROL-M or IOA utility. The utility is composed of two steps:
The first step activates the regular CTMRPLN report. (For more information about this report, see Section 8 of this manual.) The second step produces calendars for the job schedules analyzed by the first step. The calendars are written to the library referenced by DD statement DACAL (of the second step). The sample utility is supplied with the library prefix.version.CALJOB (which is not automatically allocated during CONTROL-M installation).
If there are multiple jobs with the same name, each job causes the program to assign a unique calendar name. To maintain cross-references between job and calendar names, a DAXREF file is created which cross-references every calendar to its corresponding job name. When PARM=MERGE is specified in the JCL EXEC statement of the second step, jobs with the same name create only one calendar containing all schedule days merged from all jobs with the same name. When PARM=REPLACE is specified in the JCL EXEC Statement of the second step, jobs with the same name cause any pre-existing calendars with that name to be replaced. Parameters The parameters for the first step of the utility are identical to the parameters for the CTMRPLN report: REPSTART yymmdd REPEND yymmdd REPTYPE n Start date of report. Mandatory. End date of report. Mandatory. Type of report. Optional. Valid values are: 0 1 2 Day by day list of planned jobs. Default. Month by month table of planned jobs. Month by month table of planned jobs and a job description of each job. This type of report requires a laser printer or a wide printer.
SORTBY {MEMNAME|GROUP}
Sort option. Default is MEMNAME. This parameter is relevant only for REPTYPE 0 (described above).
6 76
Implementation and Maintenance: Utilities CTMRCAL Produce a Job Plan Report
IGNORE CALENDAR calname
Ignore jobs which reference calendar calname. Optional. A maximum of eight IGNORE statements can be specified. This statement excludes jobs from the report if any of the following criteria apply to their Basic Scheduling parameters:
The specified calendar is referenced. All the months are specified as Y. The WDAYS (or DAYS) are defined as ALL (or are left blank in the scheduling table).
Activating the Utility (and Example) The utility can be activated for one or many scheduling tables (concatenated to DD statement DAPLNJOB). CTMRPLN treats all scheduling table entries with the same job name and group name as a single job, and outputs one line containing all the dates that the job can run.
//JOBCAL EXEC CTMRCAL //PLAN.DAPLNJOB DD DISP=SHR,DSN=scheduling-library(table1) // DD DISP=SHR,DSN=scheduling-library(table2) // DD DISP=SHR,DSN=scheduling-library(table3) //PLAN.DAPLNPRM DD * REPSTART 980101 REPEND 981231 REPTYPE 1 //
Return Codes 0 Other Operation performed successfully Operation failed
6 77
Implementation and Maintenance: Utilities CTMRELRS Release Quantitative Resources
CTMRELRS Release Quantitative Resources

This utility releases (deallocates) Quantitative resources which are allocated to, but no longer needed by, a job which is still executing. The utility can be used only for jobs which are submitted by the CONTROL-M monitor. It cannot be used for started tasks activated by the CONTROL-M monitor. A job can only request the release of resources which are allocated to it. The utility is useful in situations in which Quantitative resources (e.g., TAPES) used in the first step(s) of the job are not needed in later steps of the job. If the utility is not used, the resources are released only at the end of the job. (Alternatively, such resources could be released by dividing the job into two jobs.) After the appropriate step, the utility notifies CONTROL-M that the resource is not needed so CONTROL-M can use the resource for other jobs. The release is recorded in the following ways: In the jobs sysout as a message on the operator console, and as an event in the IOA Log file. If it is necessary to release resources during a job step, the utility can also be called as a program from within the application program using program name CTMRLR, as described below in Activating the Utility (and Examples). Notes The Simulation and Forecasting facility does not use this utility; instead it releases the resources only at the end of job execution. Therefore, actual production results may be better than the simulation results. If the IOA Conditions/Resources file is shared across multiple CPUs, use an enqueue manager (such as MIM or GRS) to prevent simultaneous update of the file. See the description of parameters QNAME and SHRQNAM in Section 2 of the IOA Installation Guide for more information. Parameters Parameters can be received by the utility in two ways: via DD statement DARELIN (or SYSIN) or via PARM=... Multiple commands can be specified in the same control statement. Parameters can be specified in either of the following formats:
RELEASE RESOURCE res-name-1 quant-1; res-name2 quant-2; ...
or
CHANGE RESOURCE res-name-1 quant-1; res-name-2 quant-2; ...
where res-name-n quant-n 1 20-character name of the Quantitative resource. 1 4-digit value indicating a quantity, as follows:
When the RELEASE format is used, the specified quantity is deducted

from the resources allocated to the job.
When the CHANGE format is used, the quantity of resources allocated

to the job is changed to the specified quantity.
6 78
Implementation and Maintenance: Utilities CTMRELRS Release Quantitative Resources
Example Assume 10 initiators (INIT) are allocated to a job:
If RELEASE RESOURCE INIT 3 is specified, 7 initiators will remain

allocated.
If CHANGE RESOURCE INIT 3 is specified, 3 initiators will remain

allocated. Activating the Utility (and Examples) As a step in the job:
//REL EXEC CTMRELRS RELEASE RESOURCE TAPE 1
From an application program:

LA L BALR LTR BNZ ... DC DC EQU DC R1,PARMCNDA R15,=V(CTMRLR) R14,R15 R15,R15 ERROR AL2(PARMCNDE-PARMCOND+2) RELEASE RESOURCE ADABAS-POWER 0005 * A(PARMCOND)
PARMCOND PARMCNDE PARMCNDA
Note
Program CTMRLR works in 24-bit addressing mode. The program is reusable but not re-entrant.
Return Codes 0 other Operation performed successfully Operation failed
6 79
Implementation and Maintenance: Utilities CTMTBUPD Update Job Scheduling Tables
CTMTBUPD Update Job Scheduling Tables

Utility CTMTBUPD updates CONTROL-M group/job scheduling definition parameters in batch mode. Utility CTMTBUPD receives parameters from an input file referenced by DD statement DAINPRM. This file contains the following types of statements and parameters:
Selection statements which specify job scheduling definition selection criteria. Statements containing update parameters which specify values to be added to, changed in, or deleted from, the job scheduling definition fields. Utility control statements which control the operation of the utility. Comment statements (which contain an asterisk in column one).
The parameters in these statements are discussed under Parameters below. These statements must not contain sequence numbers in columns 72-80.
Parameters
Selection Control Statement The selection control (SEL) statement is mandatory. This statement contains selection parameters which specify on which scheduling tables, job scheduling definitions, applications, groups and/or group schedule-tags the utility is to operate. Format:
SEL [TBL=tablename][,JOB=jobname][,APPL=appl-name][,GRP=group-name][,TAG=schedule-tag]
where: tablename jobname Scheduling table(s) in the scheduling library to be selected. Job scheduling definition(s) in the scheduling tables to be selected. This parameter should match the value of parameter MEMNAME in the job scheduling definition. Application(s) to be selected. This parameter should match the value of parameter APPL in the job scheduling definition. Group(s) to be selected. This parameter should match the value of parameter GROUP in the job scheduling definition. Group schedule tag(s) to be selected. This parameter should match the value of parameter SCHEDULE TAG in the Group Entity scheduling definition.
appl-name group-name schedule-tag
The selection control statement must precede all update parameters, must begin in column 1, and must be entirely contained in one record. Note the following points:
Any, all or none of the above parameters can be specified in any order in the SEL statement. If no parameters are specified, every job in every scheduling table in the scheduling library is modified by the subsequent update parameters.
Note
6 80
Each parameter can appear no more than one time in any SEL statement, and it can have no more than one value assigned to it. Prefix values can be specified by placing an asterisk at the end of the value string (see Utility Control Statements later in this utility description). When multiple parameters are specified, they are connected by an implicit logical AND relationship. When parameter TAG is specified, only basic scheduling parameters (DAYS, WDAYS, etc.) in Schedule Tag(s) of Group entities are processed. Only the first matching Schedule Tag in a Group Entity is processed. The Schedule Tag name itself can be changed. To exclude modifications to Group Entity fields, specify parameter JOB. A selection group consists of a SEL statement followed by associated update parameters, and closed by an ENDSEL statement:
ENDSEL
Multiple SEL groups can be specified in a single execution of utility CTMTBUPD.
Update Parameters
Update parameters generally correspond to the parameters of the CONTROL-M Job Scheduling Definition screen. Not all fields in the Job Scheduling Definition screen can be updated via the utility. Fields which can be updated are listed and described below. For a detailed description of each parameter, see Section 3 of this manual. Fields to be updated can fall into either of two categories:
Fields easily updated by simple specification of the new value. Fields which require complex value specifications.
Fields Easily Updated The fields in the table below can be updated by specifying the new desired values in the following format:
parmname=new-value
where: parmname new-value Name of the parameter in the job scheduling definition New value for the parameter
A brief description of each parmname follows. Note An asterisk in column * indicates that a prefix value can be specified for the parameter. If an asterisk is specified following a character string, the character string is treated as a prefix (i.e., only the characters preceding the * are replaced).
6 81
Parameter APPL AUTOARC CATEGORY CONFCAL CONFIRM DATES DAYS DCAL DESC DOCLIB DOCMEM DUE-OUT GROUP INTERVAL MAXDAYS MAXRERUN MAXRUNS MAXWAIT MEMLIB MEMNAME OVERLIB OWNER PREVENT-NCT2 PRIORITY RELATION RETDAYS RETGENS RETRO
* *
Value 1-20 characters Y/N 1-20 characters 1-8 characters Y/N 4 digit dates, separated by commas See Section 3 1-8 characters 1-50 characters
Description Application name Archive SYSDATA Category for CONTROL-D Confirmation calendar name Confirmation for schedule DATES scheduling Scheduling days DAYS calendar name Description of job Documentation library name Documentation member name Due out time Group name Minutes between reruns Expiration period Maximum number of reruns Maximum number of runs Maximum days job is retained Library containing JCL member JCL member name Overriding JCL library name User-identification Prevent NOT CATLGD 2 errors Priority AND/OR relation Maximum number of days to retain Maximum number of generations to retain Retroactive selection
* *
1-44 characters 1-8 characters [+/-]hhmm
1-20 characters 3 digits 2 digits 1 digit 3 digits 2 digits
* * * *
1-44 characters 1-8 characters 1-44 characters 1-8 characters Y/N/F/L 1-2 characters A/O 3 digits 2 digits Y/N
6 82
Parameter SHIFT SHIFT-EXT SYSDB TAG TASKTYPE TIMEFROM TIMEUNTIL WCAL WDAYS Notes
Value 1 character: >, <, @, blank 3 characters: nn, or blank Y/N
Description Shift on confirmation calendar See parameter SHIFT in Section 3 Archive to common dataset Schedule Tag name Type of task (job, started task, etc.) Earliest time to submit job Latest time to submit job, submit as soon as possible WDAYS calendar name Weekly scheduling days
1-20 characters 3 characters [+/-]hhmm [+/-]hhmm,> 1-8 characters See Section 3
1. Blank can be specified as the value for any parameter in the above table except parameters MEMLIB, MEMNAME and OWNER. 2. Certain parameters cannot be specified with other parameters. For example, when parameter DATES is specified, parameters MONTHS and RELATION cannot be specified. See the descriptions of the various parameters in Section 3 of this manual for the rules governing valid parameter combinations. 3. Multiple values for parameters DAYS and WDAYS must be specified in a single statement separated by commas. 4. For Group scheduling tables, to update parameters defined in Schedule Tags (DAYS, WDAYS, etc.) or to change the Schedule Tag name, selection parameter TAG must be specified. A Schedule Tag name of * cannot be changed, and a Schedule Tag name cannot be changed to *. To delete a Schedule Tag and all of its corresponding job scheduling definitions from the Group Entity, specify the name of the Schedule Tag to be deleted in the TAG selection parameter and specify a null TAG= update parameter. 5. For parameters TIMEFROM, TIMEUNTIL and DUE-OUT, the hhmm value can be preceded by a + or -. This indicates that the specified hhmm value is to be added to or subtracted from the existing (non-blank) hhmm value in the FROM, UNTIL, DUE OUT parameter in the job scheduling definition.
6 83
Fields Requiring Complex Updates For purposes of update by this utility, these fields are divided into two categories: Condition/Resource Parameters Miscellaneous Parameters This category includes parameters IN, OUT, CONTROL and RESOURCE. This category includes parameters SETVAR and MONTHS.
Each of these categories requires a different method of handling.
Condition/Resource Parameters
Updates to parameters IN, OUT, CONTROL and RESOURCE require statements that often provide additional information beyond just the new value. The format of the update statement for condition/resource parameters is: parmname,[N=(name,qualifier)][,O=(name,qualifier)][,P={position|*}] where: parmname N= ... Parameter to be updated (IN, OUT, CONTROL or RESOURCE) in the job scheduling definition. New parameter value. This parameter is used without an O= parameter when adding a new condition/resource, and is used with an O= parameter when replacing an existing condition/resource value. Subparameters are: name qualifier O= ... Condition or resource name. Parameter qualifier (e.g., condition date, resource quantity). See Subparameter Qualifier below.
Old (existing) parameter value. This parameter is used without an N= parameter when deleting an existing condition/resource, and is used with an N= parameter when replacing an existing condition/resource value. Subparameters are: name qualifier Condition or resource name. Parameter qualifier (e.g., condition date, resource quantity). See Subparameter Qualifier below.
P= ...
Starting character position. This parameter is used when partial names are specified in parameter N= or O= (i.e., for generic updating). See Partial Names (Generic Changes) below.
6 84
The following points should be noted:
Parameter parmname is mandatory. An N= parameter, an O= parameter, or both an N= and O= parameter, must be specified. Parameter P= must be specified if parameter N= or parameter O= in the statement is to be treated as a partial value (i.e., not a full 20-character name padded with trailing blanks).
The specified parameters must be in the order indicated in the format statement (i.e., parmname must be first, N= cannot follow O= or P=, and O= cannot follow N= or P=). When parameters N= and O= are both specified, the length of the name value need not be the same for each of the parameters. Whether this statement applies to an IN, OUT, CONTROL or RESOURCE parameter is determined by the parmname value. This, in turn, determines the format and valid values of the subparameters in parameters N= and O=: Valid values for subparameter qualifier are generally determined by the values allowed in job scheduling definitions. In many cases, question marks can be specified as the value for subparameter qualifier. Question marks indicate that the specified qualifier (i.e., subparameters in the job scheduling definition such as condition date or resource quantity) will not be considered in processing. This topic is discussed at greater length later.
Note
Format and valid values for subparameter qualifier are described immediately below. Usage of these values, including question marks, is discussed later. Subparameter Qualifier
When parmname = IN, subparameter qualifier is four characters. Valid values: Valid date value for parameter IN (date, ODAT, PREV, STAT, **** or $$$$ ) ???? (four question marks)
When parmname = OUT, subparameter qualifier is five characters. Either: Two concatenated values: date opt Valid, 4-character date or symbolic date value for parameter OUT (date, ODAT, NEXT, PREV, STAT, **** or $$$$) Valid OUT option (+ or -) (e.g., ODAT+)
????? (five question marks)
When parmname = RESOURCE, subparameter qualifier is four characters. Valid values: Valid 4-digit resource quantity for parameter RESOURCE ???? (four question marks)
6 85
When parmname = CONTROL, subparameter qualifier is one character. Valid values: Valid status values for parameter CONTROL (E or S) ? (one question mark)
Updating Conditions/Resources Note Use of partial names is described later.
When updating various types of conditions and resources (IN, OUT, RESOURCE or CONTROL as identified in parameter parmname), the type of update performed is determined by the combination of N= and O= parameters specified. Specify these parameters as follows:
To delete an existing condition or resource, specify the condition/resource name in an O= parameter (but do not specify an N= parameter), as follows: To delete a specific occurrence of the condition/resource, specify the occurrence value in subparameter qualifier. To delete all occurrences of the condition or resource, specify question marks in the subparameter qualifier.
To add a new condition or resource, specify the condition/resource name in parameter N= and specify a value in subparameter qualifier (but do not specify parameter O=). Question marks cannot be specified in subparameter qualifier. To replace or change the value of an existing condition/resource, specify both parameter N= and parameter O=. Apply the following rules to achieve the desired result. To change a condition/resource name, specify the new name in parameter N= and the old name in parameter O=. To leave the condition/resource name unchanged, (i.e., when only changing qualifiers), specify the same name in both the N= and O= parameter. To change the qualifier of a condition/resource, specify the new value in subparameter qualifier in parameter N=. To leave the existing qualifier of the condition/resource unchanged (e.g., when changing only the condition/resource name), set subparameter qualifier to question marks in parameter N=. To change only a specific occurrence of an existing condition/resource, specify the existing occurrence data in subparameter qualifier of parameter O=. To change all occurrences of an existing condition/resource, set subparameter qualifier to question marks in parameter O=.
6 86
Partial Names (Generic Changes) Parameter P=position is used to indicate that names in parameters N= and O= are partial names. (When parameter P= is not specified, the condition/resource names in both parameter N= and parameter O= are treated as full 20-byte names, padded with trailing blanks if necessary.) Either of two values can be specified for subparameter P:
A 1 or 2-digit numeric value less than or equal to 20, indicating a character position within the condition or resource name in the job scheduling definition. This character position represents the first character position of the name to be used. When a numeric value is specified, the name specified in parameter N= and/or parameter O= is assumed to be a partial name which begins at the specified position in the condition/resource name. Example Assume parameters O=BKP and P=5 are specified. If parameter N= is not specified, condition/resource TAPEBKP01 would be deleted. If parameter N=BAC is specified, condition/resource TAPEBKP01 would be renamed TAPEBAC01.
P=* This value indicates that the character string in the condition/resource name field which matches the name/string specified in parameter O= should be replaced by the name/string specified in parameter N=, regardless of character position. In this case, multiple replacements can occur. If, in attempting to replace a string with a longer string, the condition/resource name would become longer than 20 characters, the change is not performed. Note When parameter P=* is specified, the value of subparameter qualifier in both parameter N= and parameter O is treated as if ?s were specified.
Miscellaneous Parameters
The following parameters are used to add, update, or delete job scheduling parameters which can occur multiple times in the job scheduling definition: SETVAR The format of parameter SETVAR is:
SETVAR=%%variable=var-value
If the variable name obtained by resolving %%variable is found in the job scheduling definition, its original value is replaced by var-value. Otherwise, a new SETVAR parameter is created by setting the resolved variable name to var-value. If var-value is null, the variable to which %%variable resolves is deleted from the job scheduling definition.
6 87
MONTHS
The format of parameter MONTHS is: MONTHS=xxxxxxxxxxxx (12-character value). where each x can be Y, N, blank or ?. Each blank, Y or N value replaces the original value of the corresponding month in parameter MONTHS. Each value of ? causes the corresponding month in parameter MONTHS to be retained.
Note
No update parameter in the file referenced by DD statement DAINPRM can appear more than once in a SEL group.
Utility Control Statements

SCHDMAX=nnnnn Maximum number of job scheduling tables in the CONTROL-M job scheduling library specified in the CTMSCH DD statement. The SCHDMAX control statement must precede the first SEL group. 1-5 digits. Default: 10000. Maximum number of lines contained in a job scheduling table. The SLINMAX control statement must precede the first SEL group. 1-5 digits. Default: 40000. End of a SEL group. Mandatory if more than one SEL group is specified.
SLINMAX=nnnnn
ENDSEL
To specify an alternate prefix indicator in place of the default (*), specify control statement GENERIC-CHAR=alt-char where: alt-char Alternate character. Any single character, except blank, comma, period and question mark.
Control statement GENERIC-CHAR can appear anywhere in the DAINPRM file and can be specified multiple times with different values.
JCL Required to Execute CTMTBUPD

The following JCL is required to execute utility CTMTBUPD:
//jobname JOB //S1 EXEC PGM=CTMTBUPD,REGION=5000K //STEPLIB DD DISP=SHR,DSN=load.lib //CTMSCH DD DISP=SHR,DSN=ctm.scheduling.lib //DAMSG DD SYSOUT=* //DAINPRM DD * utility parameter statements /*
6 88
Example 1 In every job scheduling definition:
Change: DAYS value to: D7,-5,+9 WDAYS value to: L1,D2W3 PRIORITY value to: *5 MEMLIB prefix to: NEWPREF.
Add Control resource ENQUE-RES in share mode. Delete AutoEdit variable %%ABC (via SETVAR). Add one hour to all FROM time values.
To make the above changes, place the following statements in the DAINPRM file:
SEL DAYS=D7,-5,+9 WDAYS=L1,D2W3 PRIORITY=*5 CONTROL,N=(ENQUE-RES,S) SETVAR=%%ABC= MEMLIB=NEWPREF.* TIMEFROM=+0100 ENDSEL
Example 2 In job scheduling definitions beginning with XYZ in tables beginning with QRS:
Change all underscore characters to dashes in the IN and OUT conditions. Change quantitative resources which begin with prefix TAPE to prefix CARTRIDGE. Change Exclusive Control resource EXCLUSIVE_RES to Shared Control resource SHARE_RES.
To make the above changes, place the following statements in the DAINPRM file:
SEL TBL=QRS*,JOB=XYZ* IN,N=(-,????),O=(_,????),P=* OUT,N=(-,?????),O=(_,?????),P=* RESOURCE,N=(CARTRIDGE,????),O=(TAPE,????),P=1 CONTROL,N=(SHARE_RES,S),O=(EXCLUSIVE_RES,E) ENDSEL
6 89
Example 3 In all job scheduling definitions in group GROUP1 whose application name begins with OLD:
Change the application name prefix to NEW. Add IN condition NEW-COND with a date option of PREV. Change OUT condition OUT-COND to OUT-COND with a date option of ODAT+, regardless of the conditions original date. Specify that jobs should not be scheduled in April and May. Do not change the monthly scheduling criteria for any other months. Delete all the quantitative resources which have value DISK3330 beginning in column 5 of the resource name.
To make the above changes, code the DAINPRM file as follows:

SEL GRP=GROUP1,APPL=OLD* APPL=NEW* IN,N=(NEW-COND,PREV) OUT,N=(OUT-COND,ODAT+),O=(OUT-COND,?????) MONTHS=???NN??????? RESOURCE,O=(DISK3330,????),P=5 ENDSEL
Example 4 In all Group scheduling definitions, in schedule tags whose names begin with GRP-TAG:
Change: DAYS value to: D1P* DCAL value to: PERIODIC CONFCAL value to: blanks MONTHS value to: blanks
To make the above changes, code the DAINPRM file as follows:

SEL TAG=GRP-TAG* DAYS=D1P* DCAL=PERIODIC CONFCAL= MONTHS= ENDSEL
6 90
Implementation and Maintenance: Utilities CTMXRF Create Cross Reference Reports
CTMXRF Create Cross Reference Reports

Utility CTMXRF produces the following cross reference reports:
Calendar/Job Name Condition Name Job Name/Scheduling Table Name Resources/Job Name Library Name/Job Name Schedule Tag/Job Name Time/Job Name
Utility CTMXRF receives parameters from an input file referenced by DD statement DAXRFIN. This input file can contain the following types of statements:
Cross reference report action statements, which specify types of reports. Control statements, which control the operation of the utility. Comment statements, which contain an asterisk in column one.
DAXRFIN must be a DD card image file and the control statements must begin in column one. Embedded blanks are not allowed.
Cross Reference Report Action Statements

Format of the cross reference report action statement is:
XRF=report-type[,PARM=parm]
Valid values for report-type: CAL Produces the Calendar/Job Name Cross Reference report. This report identifies job definitions that use a calendar and indicates whether the calendar is a DCAL, WCAL or CONFCAL calendar. To restrict the report to jobs whose calendar name begins with the prefix calpref, specify PARM=calpref*. CND Produces the Job Condition Name Cross Reference report. This report lists conditions that are contained in:
CONTROL-M job scheduling tables CONTROL-O/CONTROL-T rules CONTROL-D/V/B report/mission conditions (IN, OUT, DO COND)
Each entry in the report indicates the table name, job name, product code (M for CONTROL-M, O for CONTROL-O, etc.), condition type (I=IN, O=OUT, C or T=DOCOND), and status (+/-) for the condition. To restrict the report to condition names which begin with the prefix condpref, specify PARM=condpref*. To restrict the report to a specific condition date reference, specify PARM=|dateref where dateref can be a specific date reference (in ddmm or mmdd format according to the site standard), or a specific date keyword such as STAT, PREV, NEXT, ****.
6 91
JOB
Produces the Job Name/Scheduling Table Name Cross Reference report. This report identifies which job scheduling tables contain jobs. To restrict the report to tables whose job names begin with the prefix jobpref, specify PARM=jobpref*.
RES
Produces the Resources/Job Name Cross Reference report. This report identifies CONTROL-M jobs or CONTROL-O rules that use resources and indicates the type, quantity and state of the resources. To restrict the report to resource names which begin with the prefix respref, specify PARM=respref*.
LIB
Produces the Library Name/Scheduling Table Name Cross Reference report. This report identifies which jobs specify MEMLIB, OVERLIB, DOCLIB or PDS libraries. To restrict the report to libraries of a specific type, specify PARM=libtype. Valid libtype values: MEM, OVR, DOC and PDS.
TAG
Produces the Schedule Tag Name/Job Name Cross Reference report. This report identifies which jobs or groups specify schedule tags. To restrict the report to jobs/groups whose schedule tags begin with the prefix tagpref, specify PARM=tagpref*.
TIM
Produces the Time/Job Name Cross Reference report. This report identifies jobs with a time criteria (TIME FROM, TIME UNTIL or DUE OUT TIME). To group reports by time intervals, specify PARM=n, where n=2, 3 or 4.
n=2 groups jobs by hourly intervals. n=3 groups jobs by 10 minute intervals. n=4 groups jobs by 1 minute intervals.
Utility Control Statements

Utility control statements are only necessary if the program default values are inadequate. SCHDMAX=nnnnn SLINMAX=nnnnn Maximum number of members in the CONTROL-x library(ies) being searched. 1-5 digits. Default: 10000. Maximum number of lines contained in a member of the CONTROL-x library(ies). 1-5 digits. Default: 40000.
All utility control statements must precede the first action statement.
6 92
JCL Required to Execute CTMXRF

The following JCL is used to execute utility CTMXRF:
//jobname //S1 //STEPLIB //CTMSCH //CTMSCH2 //CTORUL //CTTRUL //CTDMIS //CTDRPT JOB EXEC DD DD DD DD DD DD DD PGM=CTMXRF,REGION=5000K DISP=SHR,DSN=load.lib DISP=SHR,DSN=ctm.scheduling.lib DISP=SHR,DSN=ctm.scheduling.lib2 DISP=SHR,DSN=cto.rules.lib DISP=SHR,DSN=ctt.rules.lib DISP=SHR,DSN=ctd.prtmis.lib DISP=SHR,DSN=ctd.report.lib <=== Change or Delete <=== Change or Delete <=== Change or Delete <=== Change or Delete <=== Change or Delete <=== Change or Delete <=== Change or Delete
//CTBMIS DD DISP=SHR,DSN=ctb.balmis.lib //DAMSG DD SYSOUT=* //SYSOUT DD SYSOUT=* //DARPT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SORTIN DD UNIT=SYSALLDA,SPACE=(TRK,50) //SORTWK01 DD UNIT=SYSALLDA,SPACE=(TRK,50) //SORTWK02 DD UNIT=SYSALLDA,SPACE=(TRK,50) //SORTWK03 DD UNIT=SYSALLDA,SPACE=(TRK,50) //DAXRFIN DD * utility parameter statements /*
Example Produce the following cross reference reports:
Condition name cross reference reports for all STAT (static) conditions. Calendar name cross reference of all calendars in use in the CONTROL-M job scheduling library. Three time/job name cross reference reports (FROM, UNTIL and DUE OUT time) grouped by 10 minute time intervals.
To produce the above reports, code the file referenced by DD statement DAXRFIN as follows:
XRF=CND,PARM=|STAT* XRF=CAL XRF=TIM,PARM=3
6 93
Sample Output Reports

Job Name / Table Name Cross Reference Report
CONTROL-M 5.1.4 JOB-NAME/TABLE-NAME CROSS REFERENCE REPORT NEW DIMENSION SOFTWARE, LTD =========================================================================================== JOBNAME CYCLIC DAILYPRD DAILYSYS DEMO1 DISKLOG1 DROOR DUMMY EMPTY ENDEV* ENDEVOR EXIT2JOB E05TEST1 FIRSTJOB IEFBR14 T A B L E DEMO MAINDAY MAINDAY N86 ADABASM N86 E01SCHED DEMO SENDEVOR SENDEVOR OPHIR4 E05TEST N86 DANNY N86 N A M E S
PAGE
N88dsktp N88GRP
N88GRP1
Resource Name / Job Name Cross Reference Report

CONTROL-M 5.1.4 RESOURCE NAME/JOB NAME CROSS REFERENCE REPORT NEW DIMENSION SOFTWARE, LTD =========================================================================================== RESOURCE NAME ASA TYP TABLENAM JOB/RULE C N88TST JOB13 N88TST2 JOB13 N88TST4 JOB13 Q N88dsktp WAIT C N88TST JOB4 N88TST2 JOB4 C ADABASM BACKUP12 C ADABASM BACKUPF7 C DEMO BEACH T MK MKJOBARR T MK MKJOBARR T MK MKJOBARR C NU1 JOB1 C NU1 JOB2 QU/ST E E E 0010 S S E E E 1111 22220333+ E E TABLENAM N88TST N88TST2 N88TST4 N88TEST N88TST N88TST2 ADABASM MK MK MK NU1 NU1 JOB/RULE JOB63 JOB63 JOB63 WAIT JOB52 JOB52 READF7 STR2 STR2 STR2 JOB2 JOB2 QU/ST E E E 0010 S S S 1111 22220333+ S NU1 E NU1 TABLENAM JOB/RULE QU/ST N88TST1 JOB63 E N88TST3 JOB63 E N88TEST1 N88TST1 JOB52 N88TST3 JOB52
PAGE
CARTINIT CONT1 DBA-ADAFILE-12 DBA-ADAFILE-7 DISK-MVS003 DORES DORES2 DORES3 E02.NU1
S S
JOB2 JOB2
S E
Calendar Name / Job Name Cross Reference Report

CONTROL-M 5.1.4 CALENDAR NAME/JOB NAME CROSS REFERENCE REPORT NEW DIMENSION SOFTWARE, LTD =============================================================== CALENDAR TYP TABLENAM ALLWEEK W CALENDW ALLYEAR D CALENDY CALENDM HOLIDAY C N88GRP CONFC C E01SCHED DCAL D E01SCHED WCAL W E01SCHED WEEKCAL W N88GRP WORKDAYS W CALENWK JOB/GRP JOB3 VACN NIS3 VACN DUMMY DUMMY DUMMY VACN WKDAY TABLENAM JOB/GRP N88TEST N88TEST IEFBR14 NIS4 TABLENAM JOB/GRP N88TEST N88TEST JOB1 NIS5 TABLENAM JOB/GRP N88TEST JOB2 PAGE 1
TABLENAM JOB/GRP N88TEST NIS1
6 94
Schedule Tag / Job Name Cross Reference Report

CONTROL-M 5.1.4 SCHEDULE TAG/JOB NAME CROSS REFERENCE REPORT NEW DIMENSION SOFTWARE, LTD =============================================================== SCHEDULE TAG A SCHEDTAG1000 SCHEDTAG1001 SCHEDTAG1002 SCHEDTAG1002 ALL TABLENAM A1 GRP N88GRP N88GRP N88GRP N88GRP N88GRP1 JOB/GRP A T4 GRP1 GRP2 GRP3 GRP4 GRPTEST TABLENAM JOB/GRP ECSGRP ECSGR1 GRP T5 TABLENAM JOB/GRP ECSGRP J1 GRP T6 TABLE JOB/GRP ECSGR GRP PAGE 1
TABLE JOB/GRP
N88GRP1
IEFBR14
N88GRP1
IEFBR15
From - Until - Due Out Time / Job Name Cross Reference Reports
CONTROL-M 5.1.4 FROM TIME/JOB NAME CROSS REFERENCE REPORT ** INTERVAL=60 MINUTES ** NEW DIMENSION SOFTWARE, LTD =============================================================== TIME 0000 0600 0800 1100 1400 1700 TABLENAM ADABASM MAINDAY DEMO N86 N88TST TABLE01 JOB/GRP NOMPM CTMCLRES BEACH DEMO1 JOB100 BACKUPF7 TABLENAM JOB/GRP TABLENAM JOB/GRP TABLENAM JOB/GRP TABLENAM JOB/GRP PAGE 1
N86 N88TST1 M37A
FIRSTJOB N86 JOB100 N88TST2 M37BR14
IEFBR14 JOB100
N88TST3
JOB100
N88TST4
JOB100
CONTROL-M 5.1.4 UNTIL TIME/JOB NAME CROSS REFERENCE REPORT ** INTERVAL=60 MINUTES ** NEW DIMENSION SOFTWARE, LTD =============================================================== TIME 0900 1700 1900 2100 2300 TABLENAM MAINDAY DEMO M37A N86 TABLE01 JOB/GRP TABLENAM JOB/GRP TABLENAM JOB/GRP CTMCLRES M37A M37BR14 BEACH M37BR14 DEMO1 N86 FIRSTJOB N86 IEFBR14 BACKUPF7 TABLENAM JOB/GRP TABLENAM JOB/GRP
PAGE
CONTROL-M 5.1.4 DUEOUT TIME/JOB NAME CROSS REFERENCE REPORT ** INTERVAL=60 MINUTES ** NEW DIMENSION SOFTWARE, LTD =============================================================== TIME 1200 1500 2000 TABLENAM N86 N88GRP N88TST JOB/GRP IEFBR14 QQQQ JOB100 TABLENAM JOB/GRP N88TEST N88TST1 NIS4 JOB100 TABLENAM JOB/GRP N88TEST N88TST2 NIS5 JOB100 TABLENAM JOB/GRP TABLENAM JOB/GRP
PAGE
N88TST3
JOB100
N88TST4
JOB100
Condition Name Cross Reference Report

CONTROL-M 5.1.4 CONDITION NAME CROSS REFERENCE REPORT NEW DIMENSION SOFTWARE, LTD =============================================================== CONDITION-NAME + %%APPLID-RUNNING A JOHN1-OK JOHN2-OK JOHN3-OK ANG-1 ANG1WT1 ANG1WT1-OUT TABLE JOB/RUL/CAT O E06QA ANG1RD1 MI SAMPLES CONTROL OT+ N88TST JOB22 MC+ N88TST1 JOB42 MC+ M37A M37BR14 MI M37A M37BR14 MI M37A M37BR14 MO+ E01ANLZ ANG1RD1 MI E06QA ANG1RD1 MI E02OS390 ANG1RD1 MI TABLE JOB/RUL/CAT O TABLE JOB/RUL/CAT O TABLE PAGE 1
JOB/RUL/CAT O
N88TST N88TST1 M37A M37A
JOB42 JOB72 M37BR14 M37BR14
MC+ N88TST MC+ N88TST1 MO+ MI M37A
JOB92 JOB22 M37BR1
MC+ N88TST1 MC+ N88TST2 MO+
JOB22 JOB42
MC+ MC+
E01ANLZ ANG1WT1 E06QA ANG1RD2 E02OS390 ANG1RD2
MO+ MI E06QA ANG1WT MI E02OS390 ANG1WT
MO+ MO+
6 95
Library Name / Job Name Cross Reference Report

CONTROL-M 5.1.4 LIBRARY NAME/JOB NAME CROSS REFERENCE REPORT NEW DIMENSION SOFTWARE, LTD =============================================================== LIBRARY NAME * CTL.DUMMY.LIB CTM.V214.JCLP%%OMONTH.%%ODAY CTMP.UPG5.DOC CTMP.V500.DOC TYP MEM MEM MEM DOC TABLENAM ADABASM CTLJCLTB REPTS A1 ECSGRP DOC CTRDEMO JOBNAME DISKLOG1 CTLJOB REPTSJ1 A J2 PRODJOB1 PAGE 1
TABLENAM JOBNAME TABLENAM JOBNAME ADABASM DISKLOG2 ADABASM MPMXXX REPTS ECSGRP N88GRP CTRDEMO REPTSJ2 A4 ECSGRP IEFBR16 N88TEST PRODJOB2 CTRDEMO
G3 SYSOUT PRODJOB3
6 96
Implementation and Maintenance: Utilities IOACND Handle Condition/Resource Utilization
IOACND Handle Condition/Resource Utilization

This utility adds, verifies the existence of, deletes, or modifies prerequisite conditions and resources in the IOA Conditions/Resources file. It can be activated by the operator as a started task (STC), from TSO, or from within a user program. The addition, deletion, modification or verification is recorded in the following ways: in the jobs sysout, as a message on the operator console, and as an event in the IOA Log file. Parameters can be received by the utility in two ways: via DD statement DACNDIN (or SYSIN), or via PARM=. The parameters required depend on whether prerequisite conditions, control resources or quantitative resources are being processed. If it is necessary to add, delete, verify or modify prerequisite conditions or resources during a job step, the utility can be called as a procedure from within the application program using procedure name CTMCND, as described in Activating the Utility(and Examples) below. Parameters for Processing Prerequisite Conditions
action COND condition condition-date
where: action Action to be performed by the utility. Valid actions: ADD DELETE CHECK condition condition-date Add the specified prerequisite condition. Delete the specified prerequisite condition. Verify the existence of the specified prerequisite condition.
1-20 character prerequisite condition. Date associated with the prerequisite condition. Valid values: date DATE WDATE STAT Any specific date (in format mmdd or ddmm, depending on the site standard) Current system date. IOA Installation working date. Static. Indicates that the condition (e.g., IMS-ACTIVE) is not date-dependent.
Date character-masking for DELETE and CHECK functions is supported as follows: * Represents any value in the corresponding position of the date (format mmdd or ddmm, depending on the site standard). Up to four asterisks can be specified. For example: **** *2*2 Any date Valid date combinations of: Months: February and December Days: 02, 12, and 22
6 97
Parameters for Processing Control Resources

action CONTROL resource control
where: action Action to be performed by the utility. Valid actions: ADD DELETE resource control Add the specified Control resource under the specified type of control. Delete the specified resource which is under the specified type of control.
Resource name. Type of control. Valid values are: E S Exclusive control. Shared control.
Parameters for Processing Quantitative Resources

action RESOURCE resource quantity
where: action Action to be performed by the utility. Valid actions: ADD DELETE Add the specified Quantitative resource with the quantity specified. quantity is mandatory. Delete the resource (and the entire existing quantity). quantity must not be specified.
CHANGE Adjust the existing quantity of the Quantitative resource to or by the value specified in quantity. quantity is mandatory. resource quantity Quantitative resource name. Quantity of the Quantitative resource. For CHANGE actions, valid values are n, +n, or n where n is an integer. When n is specified without a + or - sign, the quantity of the Quantitative resource is set to n. When +n or n is specified, the quantity is increased or decreased by n. For ADD actions, valid values can only have the format n, where n is the quantity of the Quantitative resource to be added. Activating the Utility (and Examples) As a job step:
//CND1 EXEC IOACND ADD COND JOB-A-ENDED-OK 0505 DELETE COND JOB-A-DID-NOT-RUN 0505 CHANGE RESOURCE TAPES -1 ADD RESOURCE INIT-CPUA 3 DELETE RESOURCE INIT-CPUB ADD CONTROL PROD-DATA-BASE E
6 98
As a job containing AutoEdit variables, submitted through the CONTROL-M monitor:

//CND1 EXEC IOACND ADD COND AR-FILE-009-CREATED %%OMONTH.%%ODAY
As an operator command:
S IOACND,PARM=ADD COND END-CICS 0102
As a called procedure in an application program:

CALL LTR BNZ ... PARMCOND DC DC CTMCND,(PARMCOND),VL R15,R15 ERROR AL2(80) CL80ADD COND CICS-FILE-CLOSED 0102
Note
Program IOACND works in 24-bit addressing mode. The program is reusable but not re-entrant.
Return Codes ADD 0 8 12 and above DELETE 0 8 12 and above CHECK 0 8 12 and above CHANGE 0 8 12 and above Note for VM/CMS Users If you are working in a VM/CMS environment, utility IOAVCND can be used to set prerequisite conditions in a CONTROL-M monitor running on an NJE-connected MVS machine. The EXEC statement for utility IOAVCND utilizes standard IOACND input and sends a job to the MVS node to set the conditions. Example
EXEC IOAVCND ADD COND VM-READY STAT
Prerequisite condition or resource added Prerequisite condition or resource already exists Function failed Prerequisite condition or resource deleted Prerequisite condition to be deleted does not exist Function failed Prerequisite condition exists Prerequisite condition does not exist Function failed Quantity of Quantitative resource adjusted successfully Quantitative resource does not exist Function failed
6 99
Implementation and Maintenance: Operations Guide Activating the CONTROL-M Monitor
Operations Guide
Activating the CONTROL-M Monitor
The CONTROL-M monitor operates 24 hours a day as a started task (STC). Usually the monitor is automatically activated as part of the IPL process. To activate the monitor manually, use the following operator command:
S CONTROLM
For more information, see Start CONTROL-M in Section 3 of the IOA Installation Guide. If the monitor is successfully activated, the following message appears on the operator console:
CTM100I CONTROL-M MONITOR STARTED
If you try to activate an additional CONTROL-M monitor with the same IOA components in the same computer environment where a CONTROL-M monitor is active, the new (i.e., additional) monitor immediately shuts down and a relevant message is issued. Note It is possible to activate more than one monitor in the same computer environment (e.g., PROD and TEST version) by defining a different IOA environment (and a different QNAME) for each monitor. For more details, see Activating More Than One Monitor in Section 3 of the IOA Installation Guide.
Shutting Down the CONTROL-M Monitor

To shut down the CONTROL-M monitor, use the following operator command:
P CONTROLM
After a few seconds (up to a minute), the CONTROL-M monitor shuts down and the following messages appear on the operator console:
CTM107I SHUT DOWN UPON REQUEST FROM OPERATOR CTM120I CONTROL-M MONITOR SHUTTING DOWN (not highlighted) (highlighted, unrollable)
In case of emergency, the CONTROL-M monitor can be canceled. However, this is not recommended. If the monitor is canceled, the reports produced from the IOA Log may not be complete. Note When you shut down the CONTROL-M monitor, all other CONTROL-M facilities (e.g., CMEM), IOA Online monitors and every Online facility session can remain active.
6 100
Implementation and Maintenance: Operations Guide Modifying the CONTROL-M Sleeping Interval
Modifying the CONTROL-M Sleeping Interval

Periodically, at a predefined interval, CONTROL-M wakes up and checks what it has to do. This interval is set via a CONTROL-M installation parameter and can be changed by the system administrator. In addition, the interval can be altered by the operator command:
F CONTROLM,INTERVAL=nn
where nn represents the interval in seconds. It is recommended that the interval be modified by automatic commands invoked by the CONTROL-M monitor itself according to predefined conditions and time ranges, and not manually by the operator. At most sites, the interval should be longer during the day (when fewer batch production jobs are executing) and shorter during the night. The optimal sleeping interval depends on the processing power of the machine. Depending on the machine processing power indicated below, the sleeping interval should usually not be less than the number of seconds indicated:
For machines with less than 20 MIPS For machines with 2050 MIPS For machines with over 50 MIPS
10 seconds 56 seconds 4 seconds
There is no practical benefit in setting the interval to less than these minimums. Doing so can slow down CONTROL-M operation. When the modification is accepted by CONTROL-M, the following message appears on the operator console from which the modify command was issued:
CTM123I CONTROL-M INTERVAL IS SET TO nn SECONDS
New Day Procedure Flow

Once a day, at a time set by the IOA administrator, the CONTROL-M monitor begins New Day processing by going into a suspended state and issuing the following messages (the first is a highlighted, unrollable message):
CTM113I CONTROL-M MONITOR monitor NEW DAY PROCESSING STARTED CTML00I CONTROL-M MONITOR monitor PROCESSING SUSPENDED CTML07W CONTROL-M MONITOR monitor WAITING FOR NEWDAY PROCEDURE
Shortly after that last message is issued, started task CONTDAY (the New Day procedure) is automatically activated.
When CONTDAY finishes executing without any problems, the following messages are issued, and the CONTROL-M monitor exits the suspended state and resumes normal processing:
CTML01I CONTROL-M MONITOR monitor PROCESSING RESUMED CTML02I CONTROL-M MONITOR monitor NEW DAY PROCESSING COMPLETE
6 101
Implementation and Maintenance: Operations Guide Started Tasks
If a problem occurs during CONTDAY processing, the CONTROL-M monitor prompts the operator for an appropriate response via the following messages:
CTML05W NEW DAY PROCESSING ERROR DETECTED CTML06W REPLY "R" FOR RETRY OR "E" FOR END
The operator should try to correct the problem and request that CONTROL-M retry New Day processing. Halting New Day processing (option E) should only be requested if the problem cannot be corrected.
During New Day processing, CONTDAY checks the system date and time against what it expects to find in the CONTROL-M control files. If they do not match, the operator is prompted with the following messages:
CTM426W GENERAL "DAILY" DID NOT RUN FOR nnnnnn DAYS CTM427W IS IT TRUE? (ANSWER "YES" OR "NO") CTM428W YOUR ANSWER IS:
If the computer has not been working for a few days (e.g., a hardware failure or holiday); your response should be YES. If the computer was IPLed with the wrong date: Your response should be NO, the date on the computer should be checked and corrected, and you should restart procedure CONTDAY. If the date on the computer is correct and was working the previous day, the IOA administrator should be called to check the cause of the problem.
Notes
To rerun User Daily jobs from the beginning (after a failure) all dates (16) must be restored to their previous value before attempting the rerun. If the CONTROL-M monitor has been down for more than 28 days, the previous working date (i.e., the current working date minus 1) should be manually specified as date values 16.
Started Tasks
CONTROL-M can activate started tasks as well as jobs. The JES2/JES3 definitions required to support started tasks are described in Section 3 of the IOA Installation Guide. Note CONTROL-M can activate a maximum of 150 started tasks with the same name at one time.
When working in a multi-CPU environment, CONTROL-M can also activate started tasks in CPUs other than the CPU in which the CONTROL-M monitor is active. Under JES2, the CONTROL-M monitor activates started tasks in other CPUs by using command $Mm, where m is the appropriate system ID. This system ID is defined in the JES2 initialization check as follows:
MASDEF SID(n)=cccc
-orSn SID=cccc (under older releases)
6 102
Implementation and Maintenance: Operations Guide CONTROL-M Errors
For further details, refer to IBMs publication JES2 Initialization and Tuning (SC23-0046 or equivalent). JES2 will fail a $Mm command if m is the ID of the system in which the CONTROL-M monitor itself is working. Therefore, when CONTROL-M is ordered to activate a started task in a specific system, it checks whether a $Mm command or a regular MVS START command should be issued. To ensure that this check is performed correctly, you must define in the CPUS installation parameter (in CTMPARM) all the CPUs in your computer complex. Under JES3, the CONTROL-M monitor activates started tasks in other CPUs by issuing a *T cccc JES3 command, where * is the JES3 command prefix, and cccc is the required system ID. This system ID is defined in the JES3 initialization deck (INISHDECK) as follows:
MAINPROC,NAME=cccc,SYSTEM=JES3,...
CONTROL-M Errors
If a critical internal error is detected in the CONTROL-M monitor, the monitor automatically shuts itself down and the following highlighted unrollable message is issued to the operator console:
CTM121S CONTROL-M MONITOR ENDED WITH ERROR
If there is an abend in one of the CONTROL-M monitors tasks, the monitor abends with user abend code U0006. If this occurs, contact the IOA administrator.
CONTROL-M Monitor and JES

Cases of JES Malfunction
The CONTROL-M monitor uses JES services to receive information about the status of the jobs running in the system. If CONTROL-M detects a critical error in JES operation, it shuts itself down. This precaution prevents incorrect submission of jobs due to a JES malfunction. In this case, one of the following highlighted, unrollable messages is displayed on the operator console:
CTM168S CONTROL-M SHUTTING DOWN CTM256S CONTROL-M SHUTTING DOWN - COMMUNICATION TO "JES" NOT AVAILABLE - COMMUNICATION TO "JES" NOT AVAILABLE
Special Considerations
CONTROL-M uses JES services to read the jobs output. This is the way in which CONTROL-M analyzes how the job finished executing. It is important to remember the following limitations:
Jobs which are submitted by CONTROL-M can be canceled by the operator. It is important, however, not to purge their outputs. Therefore JES commands $PJnnn, $CJnnn,P and similar commands must not be used.
6 103
Implementation and Maintenance: Operations Guide CONTROL-M Monitor and JES
Job output for jobs submitted by CONTROL-M should not be released for printing other than by CONTROL-M. Therefore, MVS JES2 command $TO, MSP JES command $0, and similar commands should not be activated on the jobs output. If operator command $HJ JES is issued for the job, the job must be released from held status before CONTROL-M can read the jobs output. Otherwise, the job status is changed to EXECUTING (SYSOUT IN HOLD STATUS).
If the CONTROL-M monitor cannot read a jobs sysout, the following message appears on the operator console:
CTM262W n UNSUCCESSFUL ATTEMPTS TO READ JOB DATA BY SUBSYSTEM REQUEST. RETRY CONTINUES
Message CTM262W does not necessarily indicate a serious problem. Examples
When a job is not run due to a JCL error, only two sysout datasets exist for the job. Therefore, CONTROL-M cannot read the expected third sysout dataset, and the above message is displayed. When JES is very busy, a period of up to a minute (in extreme cases) may pass between the time the job has finished executing and the time JES enables CONTROL-M to read its sysout (i.e., JES is stuck in the output processing stage).
By default, CTM262W is displayed every 5 times the CONTROL-M monitor attempts to read the job sysout and does not succeed. If after 20 attempts the CONTROL-M monitor still cannot read the sysout, the following message is displayed:
CTMD50S READING JOB DATA BY SUBSYSTEM REQUEST FAILED AFTER n ATTEMPTS. LAST RC rc FILE filename jobname/jobid
The above two default values can be changed using installation defaults. On the other hand, message CTM262W can indicate serious problems with the jobs sysout. Below is a list of problems which can cause this message to appear.
When a jobs output has been released for print (i.e., no longer in held output), the jobs output should be printed or purged. In a multi-computer environment the following chain of events may occur: CONTROL-M monitor submits the job from computer A. Computer A crashes (or is shut down). CONTROL-M monitor is activated on computer B and the job executes in computer B. When the job finishes executing, CONTROL-M cannot read the jobs output and message CTM262W appears.
This is caused by the job waiting to be handled by the JES of computer A. This problem can be overcome by assigning the job to computer B using JES command $TJnnn,S=sysid. CONTROL-M then reads the output, and the message disappears from the operator console.
6 104
Implementation and Maintenance: Operations Guide CONTROL-M Monitor and JES
Message CTM262W Summary Whenever message CTM262W appears, wait a minute or two. If the message continues to appear every few seconds for the same job, take the following steps:
Issue JES2 commands $DJnnn and $LJnnn, and scan the results. Check if the jobs output is in held class (the job waits for print). If yes, the CONTROL-M monitor cannot analyze the output so you must analyze it manually. Print or purge the output of the job. Make sure that the job order in CONTROL-M is not HELD. Wait for a minute until the status of the job changes to DISAPPEARED. Do not forget to ADD/DELETE conditions according to the result of the run. Do this manually in the IOA Conditions/Resources screen.
(To stop the message from appearing on the operator console while you are checking the problem, hold the job order in the Status screen. Remember to release it once you have resolved the problem.)
If the job is waiting for output processing, check if the job (not the output) is held (by a previously issued $HJ command). If the job is held, release it via JES2 command $AJnn. If the job is waiting for output processing by a system ID which is currently not active, try to resolve the problem via JES command $TJnn (described above).
Stopping CMEM Before JES Is Stopped

Before shutting down the JES subsystem, deactivate CMEM using the command:
P CTMCMEM
If this is not done, warning messages (about OPEN DEBs) will be issued. Under some conditions, these messages might be followed by an SC03 abend in JES. This will not cause any harm, since JES has finished all of its processing at this time. After JES is brought up, CMEM should be re-started using the command:
S CTMCMEM
6 105
Implementation and Maintenance: Operations Guide Managing the CMEM Facility
Managing the CMEM Facility

The CONTROL-M Event manager (CMEM) handles events occurring outside the control of the CONTROL-M monitor. CMEM consists of a monitor which uses the IOA subsystem to perform predefined actions in response to system events (e.g., arrival of a specified job on the job spool).
CMEM and CONTROL-O

If CONTROL-O is installed, CONTROL-O performs CMEM functions via its own monitor and subsystem facilities. CONTROL-O the IOA subsystem use the same subsystem name. Before starting CONTROL-O, CMEM should be deactivated. (See Deactivating the CMEM Facility below.) When CONTROL-O is shut down, the CMEM facility is also shut down. To restart CONTROL-O CMEM support after CONTROL-O has been shut down, issue the following operator command: (This should only be done in an emergency situation.)
S CONTROLO,TYPE=CTOCMEM
Activating the CONTROL-M Event Manager (CMEM) Facility

It is recommended that CMEM be active in every computer in the data center (not just in the computer where the CONTROL-M monitor is working). However, it is possible that in your data center CMEM does not operate in all the computers. (This option is controlled by the CONTROL-M installation parameters.) The CMEM monitor must operate 24 hours a day. The usual way to ensure this is to automatically initialize the CMEM monitor during the IPL process (see Section 3 of the IOA Installation Guide). To activate the CMEM Subsystem manually, use the operator command:
S CTMCMEM
Deactivating the CMEM Facility

It is not normally necessary to deactivate (i.e., shut down) the CMEM monitor. However, CMEM shutdown might be necessary for either of the following reasons.
To resolve a problem that cannot otherwise be resolved. In this case, the monitor should be immediately restored to minimize the impact of the shutdown on the work environment. To clean up (erase) all loaded CMEM tables from memory, or stop all CMEM functionality (e.g., for a system shutdown).
To stop and immediately restart the CMEM facility, replace the active CMEM monitor by starting a new CMEM monitor. (See Replacing an Active CMEM Monitor below for more information.)
6 106
When the monitor replacement method is not applicable, and a complete shutdown is required, issue one of the following operator commands:
F CTMCMEM,STOP
-orP CTMCMEM
CMEM shuts down after a few minutes. Note CMEM rules are not triggered for dataset events and step termination events caused by jobs that start when CMEM is down.
Replacing an Active CMEM Monitor

If a CMEM monitor is currently active, and a new CMEM monitor is started (via operator command S CTMCMEM), the current CMEM monitor passes execution control to the new CMEM monitor and then shuts down. It is not necessary to reload the rule tables. They are passed from the current monitor to the new one. Therefore, to stop and immediately restart the CMEM monitor with minimum interference to on-going work, issue the following operator command:
S CTMCMEM
Loading of Rules
Rules are normally loaded automatically as described in Section 3 of the IOA Administrator Guide. However, manual intervention is possible, as described below. Manual Loading of Rules The CMEM list specified during startup contains a list of rule tables to be activated by CMEM when it is started. To load additional tables, or to replace a currently active table with a new (updated) copy of the rules in the table, use one of the following options: Option 1 Enter the CMEM Online facility (=C), and use the FORCE option in the Table List screen. Option 2 Issue the following operator command:
F CTMCMEM,C=library(table)
where: C= library table Load a CMEM rule. Each rule is loaded by the CMEM monitor and is activated. Rule library name. Rule table name (or mask).
6 107
Examples
F CTMCMEM,C=CTM.PROD.RULES(DATASET)
Loads table DATASET from CTM.PROD.RULES

F CTMCMEM,C=CTM.PROD.RULES(*)
Loads all tables from CTM.PROD.RULES

F CTMCMEM,C=CTM.PROD.RULES(PROD*)
Loads tables whose name starts with PROD from CTM.PROD.RULES Replacing All CMEM Rule Tables in One CPU To replace all loaded CMEM tables with those in the CMEM list (referenced by DD statement DACTMLST), use the following operator command:
F CTMCMEM,C=ALL[,REBUILD]
If the REBUILD option is specified, CMEM rule tables not listed in the CMEM list are deleted. If the REBUILD option is not specified, previously loaded CMEM rule tables are replaced by a new copy of the rule table, and unchanged tables are left intact. Replacing All CMEM Rules Tables in All CPUs All CMEM rules in all the CPUs where the CMEM monitor is active can be reloaded at the same time. The reload process is performed in the same way as the automatic loading is performed during start-up of the CMEM monitor. All active rules are deleted, and all rule tables specified in the CMEM list referenced by DD statement DACTMLST are loaded. To replace all rules in all the CPUs issue the following command:
F CONTROLM,NEWCONLIST
Specifying this command is the same as specifying F CTMCMEM, C=ALL,REBUILD in all CPUs. CONTROL-M informs the CMEM monitor running in each CPU about this command request. Rule tables that were manually loaded and/or do not appear in the CMEM list are deleted during execution of the above operator command.
6 108
Deleting (Deactivating) an Active Rule Table

An active CMEM rule table can be manually deactivated via the following operator command:
F CTMCMEM,D=library(table)
where: D= library table Example

F CTMCMEM,D=CTM.PROD.RULES(PRODTAB1)
Deactivate a CMEM rule table. Each rule is deactivated by the CMEM monitor. Rule library name. Rule table name (or mask).
Displaying Active Rules

A list of the active CMEM rules (up to a maximum of 1000 rules) can be displayed on the operator console. To display the list, enter operator command:
F CTMCMEM,DISPLAY
This command displays a list of all active rules in the CMEM facility with the following information: Rule Type Rule name. The name which appears in the first ON statement in the rule definition. Rule type. Valid types: R X D Z Table Status Library Priority JOBARRIVAL JOBEND DSNEVENT STEP
Name of the table containing the rule. Rule status. Valid status is ACTIVE. Name of the library containing the rule member. Internal CMEM rule scanning priority.
6 109
Controlling CMEM Rule Operation Mode

The mode of operation for a CMEM rule is determined by parameter MODE in its rule definition. Sometimes it is useful to override the operation mode of all active rules and verify that events and actions are recorded in a particular way. For example:
Ensure a trace of all rules (i.e., all events and actions are recorded) to facilitate analysis of the interaction between rules. Record (trace) only the triggering of every rule.
Global trace operations are requested via operator commands, as follows: 1. Activate a complete trace:
F CTMCMEM,LOG=ALL
All rules are traced as if they were defined with mode LOG. This operator command should only be used temporarily for specific tests because extended use of LOG mode can adversely affect CMEM performance. 2. Trace rule triggering only:
F CTMCMEM,LOG=TRIGGER
Only rule triggering is traced for all rules. However, rules defined with mode LOG are fully traced. 3. Restore the default operation mode (as defined in the rule definition) for each rule:
F CTMCMEM,LOG=DEFAULT
Modifying the CMEM Sleeping Interval

CMEM wakes up every few seconds. This time interval is defined in the CONTROL-M installation parameters and can be changed by the system administrator. In addition, the interval can be modified by the operator command:
F CTMCMEM,INTERVAL=nn
Where nn represents the interval in seconds. When the modification is accepted by CMEM, the following message appears on the operator console:
CME123I CMEM INTERVAL IS SET TO nn SECONDS
6 110
Implementation and Maintenance: Operations Guide Modifying the CONTROL-M Resources Acquisition Exit
Refreshing the CMEM Security Cache

CMEM security modules use a security block to identify each user for which an authority check is performed. The first time a users security authorization is checked, CMEM creates a security block for that user. The security block can then optionally be saved for the next time the users security authorization is checked. Security blocks saved for subsequent checks are kept in the CMEM security cache. The CMEM security cache holds security blocks for the last 30 users whose security authorization was checked. Changes made to a users security authorization (since the last time that the users security block was created) are not automatically included in the users security block in the CMEM security cache. However if a users security authorization has been changed, and there is no security block in the CMEM security cache for that user, changes made to the users security authorization will be in effect the next time the users security authorization is checked. To immediately include new user authorization information in the CMEM security cache, refresh the security cache via the following operator command:
F CTMCMEM,NEWSECDEF
This command refreshes all user authorization information in the CMEM security cache. When the modification is accepted, the following message appears on the operator console:
CME251I RUNTIME SECURITY REFRESH ENDED OK
Modifying the CONTROL-M Resources Acquisition Exit

CONTROL-M allows the user to modify the CONTROL-M scheduling algorithm via CONTROL-M user exit CTMX004. The user can assign weight (importance) to quantitative resources (such as tapes, CPU, etc.). This exit is loaded when the CONTROL-M monitor is started. To replace the current exit by a new one (with a new set of weights), use the operator command:
F CONTROLM,CTMX004
6 111
Implementation and Maintenance: Operations Guide Loading a New Destination Table
Loading a New Destination Table

The IOA Shout facility allows the user to specify messages to be sent to various destinations. Destinations in a production environment are not necessarily fixed. For example, the TSO logon ID of the Shift Manager is different in every shift. The Dynamic Destination table enables the user to specify a group name destination and which final destinations it represents. When the CONTROL-M monitor is started, destination table CTMDEST is loaded. To replace destination table CTMDEST with a new table, use the operator command:
F CONTROLM,NEWDEST=table
where: table Name of the new destination table.
After a few seconds, a message describing the result of the operation will appear on the operator console from which the modify command was issued.
Performing Deadline Scheduling Calculations

It is possible that within a network of predecessor/successor jobs, the combination of DUE OUT criteria will not be satisfied (e.g., a job is DUE OUT before it can be submitted or finish executing), or a high priority job will be delayed because of a low priority predecessor. To handle these cases, the operator can request automatic adjustment of DUE OUT and/or PRIORITY values of all jobs. To request DUE OUT adjustment, issue the command:
F CONTROLM,DEADLINE
To shift the DUE OUT time forward or backward, issue the command:
F CONTROLM,SDOUT={+|-}nnn
where: + and nnn Indicate whether the DUE OUT time should be shifted forward (later) or backward (earlier). The number of minutes to shift the DUE OUT time. From 1 to 999 minutes can be specified.
To request PRIORITY adjustment, issue the command:

F CONTROLM,PROP
The priorities of predecessor/successor jobs will be automatically adjusted.
6 112
Implementation and Maintenance: Operations Guide Issuing Operator Commands Via a Job or STC
Issuing Operator Commands Via a Job or STC

Utility IOAOPR can be used to issue operator commands (MVS, JES2, JES3, VTAM, etc.). It can be activated as a job step or as a started task, and allows full control over when a command should be issued and what to do afterwards. It is also possible to send the command to any computer (because CONTROL-M can schedule a started task in any computer). For a description of utility IOAOPR, see Section 9 of the IOA Administrator Guide.
IOA Online Monitor

General
CONTROL-M support can be implemented by using an online monitor which supplies CONTROL-M services to the following online environments:
CICS IMS/DC IDMS/DC VTAM COM-PLETE ROSCOE TSO There is no connection or dependency between the CONTROL-M monitor and the IOA Online monitor. Each one can be brought up and down regardless of the other.
Note
An IOA Online monitor can support only a limited number of users. Therefore, it is possible to bring up more than one online monitor. Each online monitor must have a different name. The general naming convention which is supplied is:
IOAOMONx
where x can be any valid job name character, a different one for each online monitor.
6 113
Implementation and Maintenance: Operations Guide IOA Online Monitor
Activating the IOA Online Monitor

Each IOA Online monitor usually operates 24 hours a day as a started task. Usually the Online monitor is automatically activated as part of the IPL process by the operator command:
S IOAOMONx
(where x is the monitor ID) If the Online monitor is successfully activated, the following message appears on the operator console:
CTM777I monitor-name ONLINE MONITOR INITIALIZATION STARTED
After a few seconds the following message should appear:

CTM778I monitor-name ONLINE MONITOR INITIALIZATION COMPLETED
If you try to activate more than one IOA Online monitor with the same monitor ID in the same computer, it will immediately shut down and a relevant message will be issued. Note The IOA Online monitor uses cross-memory services to communicate with other address spaces requesting services. Like other address spaces using cross-memory services, whenever the IOA Online monitor is shut down, the address space entry in the MVS Address Space Vector Table (ASVT) remains non-reusable until the next IPL, and the message IEF3521 is issued (in some MVS releases). If the IOA Online monitor is brought up and down many times, the ASVT may become full. New address spaces will not be started, and an immediate IPL may be required. To prevent this problem, set large enough values in MVS initialization parameters MAXUSER, RSVSTRT and RSVNONR in member IEASYSXX in SYS1.PARMLIB. Information about these parameters can be found in the MVS Initialization and Tuning Reference manual.
Deactivating the IOA Online Monitor

To deactivate the monitor, use the operator command:
P IOAOMONx
(where x is the monitor ID)
6 114
Controlling the Online Monitor(s)

The IOA Online monitor supplies online services to many users. Therefore, it is necessary to control what is happening inside each monitor. A series of operator commands which enable such control are described below. Displaying a List of All Active Users Enter the operator command:
F IOAOMONx,DISPLAY
(where x is the monitor ID) The following list appears on the operator console from which the modify command has been issued:
CTM645I MONITOR USER PGM APPLID TERMINAL START LASTUSED ST CTM646I monitor user pgm applid terminal start hhhhmmss status
Message CTM646I appears for every user in the IOA Online monitor. The following data is displayed for each user: MONITOR USER PGM APPLID TERMINAL START LAST USED ST Name of the IOA Online monitor. User ID. Name of the program which is active. Application ID (see the IOA Installation Guide for an explanation). Terminal ID under the Online monitor. Start time (the hour and minute that the user entered the IOA Online facility). The last time the user performed an action with the Online facility (hour:minute:second). Status: W A Canceling an Active User To cancel a specific user who is currently active under the online monitor, enter the operator command:
F IOAOMONx,CANCEL USER=userid
Waiting for input (from the terminal) Active working
(where x is the monitor ID) As a result, the user application is terminated and the following message appears on the operator console from which the modify command was issued:
CTM795I monitor-name USER userid CANCELED
6 115
This page intentionally left blank.
6 116
Section 7: Simulation and Forecasting Facility

General ...........................................................................................................................................7-1 Simulation Procedure CTMSIM ...............................................................................................7-2 General........................................................................................................................................7-2 Activating the Procedure............................................................................................................7-3 Preparatory Steps.......................................................................................................................7-3 Allocate Active Jobs File .......................................................................................................7-3 Allocate Conditions/Resources File.......................................................................................7-3 Parameters..................................................................................................................................7-4 Input Files...................................................................................................................................7-6 Output Files ................................................................................................................................7-6 CONTROL-M Exits and Simulation Processing.......................................................................7-7 Analyzing the Simulation Run ..................................................................................................7-8 Handling Manual Conditions ...............................................................................................7-9 Tape Pull List Procedure CTMTAPUL................................................................................. 7-10 General......................................................................................................................................7-10 Activating the Procedure..........................................................................................................7-11 Parameters................................................................................................................................7-11 DD Statements .........................................................................................................................7-12 JOB/SCAN DOCU/TEXT Interface .......................................................................................7-12 Problem Determination for Tape Pull List Reports................................................................7-13 Sample Tape Pull List Reports ................................................................................................7-14
Simulation and Forecasting Facility: General
General
The Simulation and Forecasting facility consists of two components.
Simulation procedure CTMSIM Tape Pull List procedure CTMTAPUL
Simulation procedure CTMSIM tests the potential impact of proposed changes to the configuration or production environment. It answers What if? questions, such as: What if we ...
add or remove four tape drives from the system? enlarge the CPU power by 30%? run a particular set of applications daily instead of weekly?
The Simulation procedure can also be used to forecast production runs such as the next 24-hour run, end-of-month run, etc. In this way, possible irregularities in the schedule can be foreseen. Tape Pull List procedure CTMTAPUL creates a report of all tapes to be mounted for a specific period. By running the procedure on a daily basis, all tapes required for the daily production run can be prepared in advance for the operator or the robotic tape library. The Tape Pull List procedure uses the output of the Simulation procedure as input. Therefore, the Simulation procedure must be executed before the Tape Pull List procedure can be executed. (However, the Simulation procedure can be executed without executing the Tape Pull List procedure.)
71
Simulation and Forecasting Facility: Simulation Procedure CTMSIM General
Simulation Procedure CTMSIM

General
The Simulation procedure simulates the CONTROL-M monitor flow for a specified period without actual job submission and without output processing. It takes into consideration all scheduling criteria including prerequisite conditions, time limits, quantitative and control resources. CONTROL-M and IOA files used as input to the simulation process are not updated as a result of this process. The statuses of the files after simulation are written to special simulation output files. The simulation assumes that each job ended execution with a condition code of 0. The following CONTROL-M and IOA files are used as input in the Simulation procedure. These files may either be actual production files or special files created specifically for forecasting purposes. AJF RES STAT Active Jobs file IOA Conditions/Resources file CONTROL-M Statistics file
The simulation produces the following output files: SIMOAJF SIMORES SIMLOG Simulation Output Active Jobs file Simulation Output Conditions/Resources file Simulation Output Log file
The Simulation procedure can contain several steps prior to the actual simulation processing step, depending on the environment to be used as input to the simulation run. For example:
It may be desirable to use the production Active Jobs file as input. It may be necessary to simulate a specific days run without relating to the current production jobs. It may be necessary to resolve manual conditions prior to the simulation run so that all jobs are submitted.
72
Simulation and Forecasting Facility: Simulation Procedure CTMSIM Activating the Procedure
Activating the Procedure

The procedure can be invoked directly (i.e., // EXEC CTMSIM), or via a job generated by option M3 of the Online Utilities menu. Option M3 is the preferred method of generating the job stream for the procedure because the Online utility can automatically perform certain necessary preparatory steps (mentioned above). If the Online utility is not used, the user should add these steps, as necessary, to the JCL. Online utility M3 is discussed in M3: Prepare Simulation/Tape Pull List Job in Section 2 of this manual.
Preparatory Steps
The following preparatory steps should be added, as needed, to the simulation job.
Allocate Active Jobs File

DD statement DACKPTIN references a file with the format of the Active Jobs file. It can refer to either of the following files:
Production Active Jobs file. If this file is used, it only needs allocation. Test file used to simulate jobs planned for a future working day. If a test file is used, an initial job step must allocate and format the simulation Active Jobs file. A date record is then generated for the date of the simulation. A User Daily job step then loads the required job orders into the simulation Active Jobs file.
This preparatory step can be automatically generated via online utility M3. All jobs in the Active Jobs file participate in the simulation. For jobs which are currently executing at the time the simulation is running, it is assumed that they have already executed half of their average elapsed time.
Allocate Conditions/Resources File

DD statement DARESF references the Conditions/Resources file. It can refer to either of the following files:
Production IOA Conditions/Resources file. If this file is used, it only needs allocation. Test file, which can be used to handle manual conditions under simulation. If your production run uses manual conditions which are normally added later in the day, these should be incorporated into the simulation. A method of incorporating manual conditions is described later in Handling Manual Conditions (These steps cannot be requested via online utility M3.)
73
Simulation and Forecasting Facility: Simulation Procedure CTMSIM Parameters
Parameters
The following parameters are passed to the utility via DD statement DASIMPRM (or SYSIN). SIMSTART SIMEND Date and time at which the simulation should start (in yymmddhhmm format). Mandatory. Date and time at which the simulation should end (in yymmddhhmm format). Mandatory.
Note
The interval between specified SIMSTART and SIMEND values must not exceed one working day. Simulation interval in minutes. The simulation clock advances by the interval specified. The shorter the interval, the more accurate the simulation will be, but the longer the simulation will take to run. The specified interval should not exceed one working day. Mandatory. For a job that has no execution statistics, this statement is used to indicate the jobs expected execution time. Optional. If the simulation encounters a job without statistics and this statement is not supplied, a default execution time of three minutes is used. Format of parameter NEWJOB is as follows:
NEWJOB memname EXECTIME mmmm.xx [GROUP groupname][CPUID i]
INTERVAL mm
NEWJOB
The following subparameters can be specified: memname Name of the member containing the jobs JCL. This value helps identify the job order in the Active Jobs file. Mandatory. Expected execution time, where mmmm is the number of minutes and xx is hundredths of minutes. (This is the same format used in the sysout Log message of the job.) Mandatory. Name of the group to which the job belongs. This value helps identify the job order in the Active Jobs file. Optional. CPU ID. In a multiple CPU environment, the job can have different execution times on different CPUs. Therefore, it is useful to specify the expected elapsed time for each CPU on which the job may run. i should have the same value as $SIGN (described in System Variables in Section 5 of this manual). Optional.
mmmm.xx
groupname
74
Simulation and Forecasting Facility: Simulation Procedure CTMSIM Parameters
OLDJOB
For a job with execution statistics, this statement can be used to override the statistically-estimated execution time. For example, a longer execution time can be specified to test the effect of adding more input data to the job. Optional. Format of parameter NEWJOB is as follows:
OLDJOB memname EXECTIME mmmm.xx [GROUP groupname][CPUID i]
The same subparameters described above for parameter NEWJOB can be specified for parameter OLDJOB. ADD/DELETE Add or delete (as specified) a prerequisite condition of a specific ODATE (original scheduling date) at a specified simulation date/time. Format of parameter ADD/DELETE is as follows:
{ADD|DELETE} COND condname odate ONDAYTIME yymmddhhmm
The following subparameters can be specified: ADD|DELETE condname odate yymmddhhmm Action to be performed. Mandatory. Name of the condition to be added or deleted. Mandatory. Original scheduling date associated with the condition. Mandatory. Simulation date and time at which the condition should be added or deleted. Mandatory.
CHANGE RESOURCE Change the quantity of a given resource at a specified simulation date/time. Format of parameter ADD/DELETE is as follows:
CHANGE RESOURCE resname quantity ONDAYTIME yymmddhhmm
The following subparameters can be specified: resname quantity Name of the resource whose quantity should be changed. Mandatory. Change in quantity for the resource. The quantity change can be specified in any of the following formats: nnnn +nnnn nnnn yymmddhhmm Set the quantity to the specified value. Add the specified quantity to the current quantity. Subtract the specified quantity from the current quantity.
Simulation date and time at which the resource quantity should be changed. Optional.
75
Simulation and Forecasting Facility: Simulation Procedure CTMSIM Input Files
Input Files
The simulation procedure accepts the following input files:
Active Jobs file See Preparatory Steps above. Job Execution Statistics file DD statement DASTAT references the CONTROL-M Job Execution Statistics file. This file contains job execution statistics, including the execution elapsed time.
IOA Conditions/Resources file See Preparatory Steps above.
Output Files
The simulation run produces the following output files:
Simulation Messages file DD statement DASIMOUT references a sequential file containing a list of the simulation parameters used, and special messages for error codes, warning situations, etc. In addition, it contains all the SHOUT messages to TSO/ROSCOE users and to the computer operator.
SIMLOG Simulation Log file DD statement DALOGOUT references a sequential output file in a format similar to that of the IOA Log file. At the end of the simulation process, this file contains all the log messages describing events which occurred during the simulation run (e.g., JOB SUBMITTED, JOB ENDED OK, COND xxxx ADDED). This file can be used as input to all CONTROL-M reports which are normally produced from the IOA Log file. The standard set of reports which are produced from the IOA log can be used to analyze the simulation run. Therefore, it is not necessary to write special simulation reports.
SIMOAJF Active Jobs file DD statement DACKPTOU references a file in the format of the Active Jobs file. All jobs which were present in the input Active Jobs file are written to this file with the status assigned to them during the simulation run (e.g., ENDED OK, EXECUTING, WAIT SCHEDULE). The file can be scanned online or in batch mode using standard CONTROL-M facilities.
SIMORES Conditions/Resources file DD statement SIMORES Conditions/Resources file. references a file in the format of the IOA
All conditions, Quantitative resources and Control resources which were present at the end of the simulation run are written to this file. The file can be scanned online or in batch mode using standard CONTROL-M facilities.
76
Simulation and Forecasting Facility: Simulation Procedure CTMSIM CONTROL-M Exits and Simulation Processing
CONTROL-M Exits and Simulation Processing

The CONTROL-M Simulation and Forecasting facility functions in much the same way as the CONTROL-M monitor, but is activated without performing real I/O. Therefore, some of the exits activated under the CONTROL-M monitor are also activated during simulation. Exit CTMX003 (output scanning) is invoked once for each job. The exit does not receive any sysout. Since the simulation assumes that each job ended execution with a condition code of 0, this exit can also be used to add events for certain jobs which end with a non-zero condition code which influences the job flow. Exit CTMX002 is not activated in simulation mode. If the same exit is to be used in both the production and simulation environments, it may be necessary to determine which environment is currently active. Field MCTSMIND in the MCT can be checked as follows to determine whether or not the exit is running under simulation:
TM BO MCTSMIND,MCTSIMYS SKIPPROD ARE WE UNDER SIMULATION? YES, SKIP PRODUCTION LOGIC
Sample Input
// EXEC CTMSIM //SIM.DACKPTIN DD DSN=XXX.CTM.PROD.TESTAJF,DISP=SHR //SIM.SYSIN DD * SIMSTART 9806060900 SIMEND 9806062200 INTERVAL 15 NEWJOB D4TRY1 EXECTIME 2.30 NEWJOB D4TRY2 EXECTIME 100.00 CPUID 1 NEWJOB D4TRY2 EXECTIME 120.00 CPUID 2 CHANGE RESOURCE TAPE -3 ONDAYTIME 9806061600 ADD COND IR-TAPE-ARRIVED 0606 ONDAYTIME 9806061800 ADD COND END-CICS 0606 ONDAYTIME 9806062100 //
. . SIM076I SIMULATION STARTED SIMSTART 9812122100 SIMEND 9812122130 INTERVAL 55 ADD COND TAP-TEST-OK 0606 ONDAYTIME 9806062102 ADD COND TAP-TEST2-OK 0606 ONDAYTIME 9806062102 ADD COND PUL2-OK 0606 ONDAYTIME 9806062102 ADD COND PUL1-OK 0606 ONDAYTIME 9806062102 ADD COND PUL2-OK 0606 ONDAYTIME 9806062102 NEWJOB ASMMCTD EXECTIME 0001.00 NEWJOB ASMMCTM EXECTIME 0001.00 21.00.00 RUN100I CONTROL-M MONITOR STARTED 21.00.00 SIM087W MEMBER PRDJBREG LIBRARY PROD.DAILY.JOBS 21.00.00 SIM087W MEMBER PRDJBDAY LIBRARY PROD.DAILY.JOBS 21.02.45 CTM567I COND PUL2-OK ODATE 0606 ADDED 21.02.45 CTM567I COND PUL1-OK ODATE 0606 ADDED 21.02.45 CTM587I COND PUL2-OK ODATE 0606 ALREADY EXISTS 21.02.45 CTM567I COND TAP-TEST2-OK ODATE 0606 ADDED 21.02.45 CTM567I COND TAP-TEST-OK ODATE 0606 ADDED 21.31.10 SIM098I TASK EXECDAY DID NOT FINISH EXECUTING 21.31.10 SIM098I TASK PRDTEST DID NOT FINISH EXECUTING 21.31.10 SIM099I TASK MPMXXX STILL WAITS SCHEDULE 21.31.10 SIM099I TASK MPMTST STILL WAITS SCHEDULE 21.31.10 RUN120I CONTROL-M MONITOR SHUTTING DOWN 21.31.10 SIM078I SIMULATION ENDED
- DEFAULT ELAPSED TIME USED - DEFAULT ELAPSED TIME USED
77
Simulation and Forecasting Facility: Simulation Procedure CTMSIM Analyzing the Simulation Run
Analyzing the Simulation Run

A number of tools can be used to analyze the simulation run and to diagnose problems which may have occurred during simulation processing.
Output of the Simulation Run Output of the KSL Step Night Schedule Report Online Simulation Environment Utility CTMRAFL
These tools are described below. Output of the Simulation Run DD statement DASIMOUT references summary information about the simulation run. It specifies which jobs ran, which are still in WAIT SCHEDULE status, and which are still executing when the simulation terminates. The following tools can be used to ascertain why certain jobs remain in WAIT SCHEDULE status when the simulation run is terminated. Output of the KSL Step KSL script REP3LEFT can be executed after the simulation step. REP3LEFT generates a report which shows the reason(s) why certain jobs are still in WAIT SCHEDULE status at the end of the simulation run. This report can be requested as an option via online utility M3. Night Schedule Report This report provides a summary of each job which has within the time interval of the simulation run. This report can be requested as an option via online utility M3. Online Simulation Environment A special online environment can be created for the allocation of the files written by the simulation run. The online environment should include the following allocations: DD statement DACKP DD statement DARESF DD statement DALOG Allocated to file SIMOAJF Allocated to file SIMORES Allocated to file SIMLOG
The online environment can be used to determine not only which jobs were submitted, but which jobs are waiting to be scheduled and why they remained in WAIT SCHEDULE status at the termination of the simulation run. Utility CTMRAFL Utility CTMRAFL (described in Section 8 of this manual) can be run on the simulation input Active Jobs file to obtain information on job dependencies and manual conditions. Utility CTMRAFL does not check the IOA Conditions/Resources file. Therefore, conditions listed as manual conditions may actually exist in the IOA Conditions/Resources file.
78
Simulation and Forecasting Facility: Simulation Procedure CTMSIM Analyzing the Simulation Run
Handling Manual Conditions

The following steps should be performed to incorporate manual conditions into the Conditions/Resources file which will be used in the simulation procedure. 1. Create a Conditions/Resources file and a Manual Conditions file to be used for simulation only. This may be done using members FORMRES and FORMNRS in the IOA INSTALL library. File names RES and SNC can be changed to SIMRES and SIMSNC respectively. File names NRS and NSN can be changed to SIMNRS and SIMNSN respectively. 2. Using utility CTMCOPRS, copy the contents of the production IOA Conditions/Resources file into the simulation Conditions/Resource file created in Step 1 above. 3. Using utility IOALDNRS, load the manual conditions into simulation NRS file SIMNRS. The following overrides should be specified when using procedure IOALDNRS: DDname DANRES DANSINC DARESF DASINC DSname Suffix NRS NSN RES SNC Override Suffix SIMNRS SIMNSN SIMRES SIMSNC
4. Run utility ADDCMND to add the required manual conditions to the simulation Conditions/Resources file. 5. The following overrides should be specified for the simulation step: DDname DARESF DASINC DSname Suffix RES SNC Override Suffix SIMRES SIMSNC
79
Simulation and Forecasting Facility: Tape Pull List Procedure CTMTAPUL General
Tape Pull List Procedure CTMTAPUL

General
The Tape Pull List procedure creates a list of all tapes to be mounted in a specified period. The list can be sorted and edited in various ways. Examples
All tapes to be mounted, sorted by the expected mount time. All tapes, sorted by volume serial number. It is highly recommended that the simulation be run from the current time (i.e., not from a future time). Otherwise, the Tape Pull list results may be inaccurate because new tape files may be cataloged in the time remaining before the start of the simulation run.
Note
The procedure takes into account the expected order of job execution and the order of creation of tape datasets. The procedure also does the following:
Checks the syntax of all AutoEdit statements in all jobs which are planned for the given period. Checks the JCL syntax. Produces a list of datasets which are still missing for the execution. These are usually input datasets due to arrive, but they may be JCL execution errors. For the Tape Pull List procedure to be executed properly, the internal reader (INTRDR) must have authority to submit jobs.
Note
The Tape Pull List procedure uses files from the Simulation procedure as input. In preparation for the Tape Pull List procedure, the Simulation procedure should be run using the production CONTROL-M Active Jobs file and IOA Conditions/Resources file. The Tape Pull List procedure works as follows:
The procedure looks for SUBMISSION messages in the simulation output LOG file. For each submission message, it looks for the appropriate job having a WAIT SCHEDULE status on the simulation input Active Jobs file. If a job is found, the Tape Pull List procedure actually submits the job with the TYPRUN=SCAN parameter, reads the SYSOUT of the job, retrieves the dataset information, and produces the required reports.
The procedure recognizes tape datasets by either the appropriate unit specification in the JCL (e.g., UNIT=TAPE) or by retrieving information from the system catalog. It is therefore not necessary to have all tape datasets cataloged in the MVS catalog. Note A highlighted warning message appears on the operator console while the jobs are being submitted. During this stage, the operator console may display several messages regarding the job submission. The highlighted message disappears at the end of this stage.
7 10
Simulation and Forecasting Facility: Tape Pull List Procedure CTMTAPUL Activating the Procedure
The procedure can detect that a certain tape will be used by more than one job, and which job will create it, as illustrated in the following example. Job A creates a new generation of a tape dataset:
//OUTUPD DD DSN=PFX.DATA(+1),DISP=(,CATLG),...
Job B (a successor of Job A) accesses to the same dataset:

//INUPD DD DSN=PFX.DATA(0),DISP=SHR
The procedure detects that Job A is the creator of the dataset used by Job B and reports the same tape volser for both jobs.
After the jobs sysout has been analyzed, the sysout is deleted from spool. The next stage of the procedure produces reports according to the requested parameters, described below.
Activating the Procedure

The Tape Pull List procedure is activated as follows:
// EXEC CTMTAPUL //TAPULIN DD * parameters
Parameters
REPBYVOL REPBYTIME REPBYJOB REPBYDSN Produce a report sorted by volume serial number (volser). All tapes from the tape library are included. Produce a report sorted by the expected mount time. Produce a report sorted by job name. Produce a report sorted by dataset name.
JCLFILE {YES|NO|ONLY} When the value YES or ONLY is specified, the procedure writes a copy of every submitted job to the file referenced by DD statement DAJCLOUT. If ONLY is specified, the procedure does not submit the jobs (with TYPRUN=SCAN), the Tape Pull reports are not created, and the procedure is run to create the JCL file only. The default is NO. IGNORE DSN dsn IGNORE JOB jobname Dataset name (or prefix) that should not appear in the report. (If the last character of dsn is *, it is treated as a prefix.) Job name (or prefix) that should not appear in the report. (If the last character of jobname is *, it is treated as a prefix.)
The Tape Pull List job can be prepared using the (ISPF) Simulation panel (option M3 in the IOA Online Utilities menu). A special section of the panel is designated for Tape Pull List parameters. If you wish to run the Tape Pull List procedure, specify Y next to the field TAPE PULL LIST and specify Y next to the desired reports. The default control parameters member name will appear on the screen. This member contains IGNORE statements (procedure parameters). JOB/SCAN parameters are discussed above. After filling in the parameters, you will enter the edited JCL of a job to run the simulation and the procedure. You can submit it, or save it for future use.
7 11
Simulation and Forecasting Facility: Tape Pull List Procedure CTMTAPUL DD Statements
DD Statements
The following DD statements are used by procedure CTMTAPUL: DALOGIN DACKPTIN TAPULIN DATAPNAM Output Log file of the Simulation facility (which is input for the Tape Pull List procedure). Active Jobs file used as input to the simulation (it remains unmodified). Procedure parameters. Member containing a list of local names used by the site to describe tape units and cassettes/cartridges. (CONTROL-M recognizes IBM-supplied names such as 3400.) The format of each line in the list is: Col 1-8 Col 9 Unit-name One of the following indicators: T C D DAREPOUT TAPULOUT DAJCLOUT Report(s) output. Messages (of the procedure). Job stream of the jobs that will be submitted during the specified period. (See JOB/SCAN DOCU/TEXT Interface below.) Tape Cassette/Cartridge DASD
JOB/SCAN DOCU/TEXT Interface

For users of JOB/SCAN-DOCU/TEXT. When parameter JCLFILE is specified, every job which is submitted by the procedure for JCL scan is also written to DD statement DAJCLOUT. At the end of execution of the procedure, this dataset (if allocated) contains all jobs which will be submitted during the execution period according to the order of submission. This file can be used as input to JOB/SCAN DOCU/TEXT products. In sites using the JOB/SCAN DOCU/TEXT Interface, the lower portion of online utility M3 (described in Section 2 of this manual) contains INVOKE JOB/SCAN parameters.
7 12
Simulation and Forecasting Facility: Tape Pull List Procedure CTMTAPUL Problem Determination for Tape Pull List Reports
Problem Determination for Tape Pull List Reports

The following conditions must be satisfied before the Tape Pull List procedure can forecast tapes for a specific job:
The submission message must be present in the simulation output Log file. The corresponding job has a WAIT SCHEDULE status in the simulation input Active Jobs file.
Reports are not produced if one or more of the following situations exist:
None of the submitted jobs required tapes. Jobs requiring tapes were not submitted by the simulation because their submission criteria were not satisfied. An invalid Active Jobs file was specified as an input for the Tape Pull List procedure. An invalid Log file was specified as an input for the Tape Pull List procedure. JCLFILE ONLY was specified as an input parameter for the procedure. No reports were requested from the procedure through the input parameters (i.e., no reports was the default). The procedure does not recognize tape datasets. See Tape Pull List Utility under CONTROL-M Customization in Section 3 of the IOA Installation Guide.
7 13
Simulation and Forecasting Facility: Tape Pull List Procedure CTMTAPUL Sample Tape Pull List Reports
Sample Tape Pull List Reports

PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD. TAPE PULL LIST ====================
JOBNAME USER ODATE TIME MEMNAME VOLSER LAB# TYPE DISP DSNAME PROCNAME STEPNAME DDNAME ---------------------------------------------------------------------------------------------------------------------------------SMFSAVE M05 080898 09:06 SMFSAVE 110050 0001 T M-O<+> BKP.MONTH.CONT02(+0) STEP3 TAPE1 110051 T 110048 0001 T M-O BKP.MONTH.CONT02(-1) STEP3 TAPE2 110049 T 110058 0001 T M-O BKP.MONTH.CONTO2(-2) STEP3 TAPE3 110059 T PRDINPUT M05 080898 09:02 PRDINPUT 996713 0001 T NEW PRD.TP.FILE1(+1) ST1 DD1 S#0001 0001 C NEW PRDW.FILE.GDG.GRPM1(+1) BADSTEP BADD1 100047 0001 T M-O BKP.WEEK.CONT01(-2) ASTEP1 OUT0 PRDUPDT1 M05 080898 09:09 PRDUPDT1 114003 0001 T OLD PRDW.FILE.GDG.GRP11(+0) RES TAP1GDG0 114002 0001 T OLD PRDW.FILE.GDG.GRP11(-1) RES TAP1GDG2 S#0004 0001 T NEW BKP.MONTH.CONT01(+1) RESTORE CYCLIC DACYCT 114003 0001 T OLD PRDW.FILE.GDG.GRP11(+0) RESTORE CYCLIC TAPEGDG0 $#0005 0001 C NEW PRDO.TP.UPDT1 RESTORE CYCLIC CASSFILE PRDRPT2C M05 080898 09:19 PRDRPT2C $#0006 0001 T NEW PRD.TP.DAILY.REPORTS ASTEP1 OUT 113492 0001 T OLD PRD.CART.RPT2C BACKUP CYCLIC DACYCT $#0007 0001 T NEW BKP.MONTH.CONT02(+1) BACKUP CYCLIC DACYCT PRDRPT2D M05 080898 09:22 PRDRPT2D 114003 0001 T OLD PRDW.FILE.GDG.GRP11(+0) ST1 TAPE0 T00001 0001 T NEW PRD.SNG1912.TAPE1(+1) ST1 TAPE1 T00002 0002 T NEW PRD.SNG1912.TAPE1(+2) ST1 TAPE11 994529 0001 T NEW PRDW.FILE.GDG.GRP21(+0) ST2 TAPE01 997892 0003 T NEW PRD.SNG1912.TAPE2(+1) ST2 TAPE2 S#0008 0001 T NEW &&NEWTEMP ST2 TAPETMP 996638 T NEW BKP.MONTH.CONT01(+3) ST2 TAPE8O2 PRDEXE2E M05 080898 09:25 PRDEXE2E T00002 0002 T OLD PRD.SNG1912.TAPE1(+0) STEP1 INTAPE1 T00001 0001 T OLD PRD.SNG1912.TAPE1(-1) STEP1 INTAPE11 S#0007 0001 T OLD BKP.MONTH.CONT02(+0) STEP2 TAPE5<+> 110050 0001 T OLD BKP.MONTH.CONT02(-1) STEP2 TAPE6 110051 T 110048 0001 T OLD BKP.MONTH.CONT02(-2) STEP2 TAPE7 110049 T 110058 0001 T OLD BKP.MONTH.CONT02(-3) STEP2 TAPE8 110059 T 110056 0001 T OLD BKP.MONTH.CONT02(-4) STEP2 TAPE9 110057 T SORTBY JOBNAME (REPBYJOB)
7 14
PRODUCED BY CONTROL-M 5.1.4 TAPE PULL LIST NEW DIMENSION SOFTWARE, LTD. =================== DSNAME JOBNAME MEMNAME VOLSER DISP TYPE PROCNAME STEPNAME DDNAME -------------------------------------------------------------------------------------------------------------------<+>&&NEWTEMP PRDRPT2D PRDRPT2D S#0008 NEW T ST2 TAPETMP BKP.MONTH.CONT01(+1) PRDUPDT1 PRDUPDT1 S#0004 NEW T RESTORE CYCLIC DACYCT BKP.MONTH.CONT01(+3) PRDRPT2D PRDRPT2D 996638 NEW T ST2 TAPE8O2 BKP.MONTH.CONT01(+0) SMFSAVE SMFSAVE 110050 M-O T STEP3 TAPE1 110051 M-O T STEP3 TAPE1 PRDEXE2E PRDEXE2E S#0007 OLD T STEP2 TAPE5 BKP.MONTH.CONT02(+1) PRDRPT2C PRDRPT2C S#0007 NEW T BACKUP CYCLIC DACYCT BKP.MONTH.CONT02(-1) SMFSAVE SMFSAVE 110048 M-O T STEP3 TAPE2 PRDEXE2E PRDEXE2E 110050 OLD T STEP2 TAPE6 110051 OLD T STEP2 TAPE6 BKP.MONTH.CONT02(-2) SMFSAVE SMFSAVE 110058 M-O T STEP3 TAPE3 110059 M-O T STEP3 TAPE3 PRDEXE2E PRDEXE2E 110048 OLD T STEP2 TAPE7 100049 OLD T STEP2 TAPE7 BKP.MONTH.CONT02(-3) PRDEXE2E PRDEXE2E 110058 OLD T STEP2 TAPE8 110059 OLD T STEP2 TAPE8 BKP.MONTH.CONT02(-4) PRDEXE2E PRDEXE2E 110056 OLD T STEP2 TAPE9 110057 OLD T STEP2 TAPE9 BKP.WEEK.CONT01(-2) PRDINPUT PRDINPUT 100047 M-O T ASTEP1 OUT0 PRD.SNG1912.TAPE1(+0) PRDEXE2E PRDEXE2E T00002 OLD T STEP1 INTAPE1 PRD.SNG1912.TAPE1(+1) PRDRPT2D PRDRPT2D T00001 NEW T ST1 TAPE1 PRD.SNG1912.TAPE1(+2) PRDRPT2D PRDRPT2D T00002 NEW T ST1 TAPE11 PRD.SNG1912.TAPE1(-1) PRDEXE2E PRDEXE2E T00001 OLD T STEP1 INTAPE11 PRD.SNG1912.TAPE2(+0) PRDEXE2E PRDEXE2E 997892 OLD T STEP2 INTAPE2 PRD.SNG1912.TAPE2(+1) PRDRPT2D PRDRPT2D 997892 NEW T ST2 TAPE2 PRD.TP.FILE1(+1) PRDINPUT PRDINPUT 996713 NEW T ST1 DD1 PRDW.FILE.GDG.GRPM1(+0) PRDINPUT PRDINPUT S#0001 OLD C BADSTEP BADD2 PRDW.FILE.GDG.GRPM1(+1) PRDINPUT PRDINPUT S#0001 NEW C BADSTEP BADD1 PRDW.FILE.GDG.GRPM8(+1) PRDINPUT PRDINPUT S#0003 NEW T ASTEP1 TAPEGDG8 PRDW.FILE.GDG.GRP11(+0) PRDINPUT PRDINPUT 114002 OLD T ASTEP1 TAPEGDG0 PRDUPDT1 PRDUPDT1 114003 OLD T RES TAP1GDG0 PRDRPT2D PRDRPT2D 114003 OLD T ST1 TAPE0 T00002 NEW T ST1 TAPE12 PRDW.FILE.GDG.GRP11(+1) PRDINPUT PRDINPUT 114003 NEW T ASTEP1 TAPEGDG2 PRDW.FILE.GDG.GRP11(-0) PRDINPUT PRDINPUT 114002 OLD T ASTEP1 TAPEGDG1 PRDUPDT1 PRDUPDT1 114003 OLD T RES TAP1GDG1 PRDRPT2D PRDRPT2D 114003 OLD T ST2 TAPE01 PRDW.FILE.GDG.GRP11(-0) PRDUPDT1 PRDUPDT1 114002 OLD T RES TAP1GDG2 SORTBY DSNAME (REPBYDSN)
7 15
PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD.
TAPE PULL LIST ===================
VOLSER TYPE JOBNAME ODATE TIME DISP LAB# DSNAME --------------------------------------------------------------------------------S#0001 C PRDINPUT 080898 22:02 NEW 0001 PRDW.TESTFILE.GDG.GRPM1(+1) S#0002 T PRDINPUT 080898 22:02 NEW 0001 PRD.TP.TRANS S#0003 T PRDINPUT 080898 22:02 NEW 0001 PRDW.TESTFILE.GDG.GRPM8(+1) S#0004 T PRDUPDT1 080898 22:09 NEW 0001 BKP.MONTH.CONT01(+1) T00001 T PRDRPT2D 080898 22:22 NEW 0001 PRD.SNG1912.TAPE1(+1) T00002 T PRDRPT2D 080898 22:22 NEW 0002 PRD.SNG1912.TAPE1(+2) 100000 T PRDINPUT 080898 22:02 OLD 0001 PRDW.TESTFILE.GDG.GRPM8(+0) 100047 T PRDINPUT 080898 22:02 M-O 0001 BKP.WEEK.CONT01(-2) 100048 T PRDINPUT 080898 22:02 M-O 0001 BKP.WEEK.CONT01(-2) 110048 T SMFSAVE 080898 22:06 M-O 0001 BKP.MONTH.CONT02(-1) PRDEXE2E 080898 22:25 OLD 0001 BKP.MONTH.CONT02(-2) 110049 T SMFSAVE 080898 22:06 M-O 0001 BKP.MONTH.CONT02(-1) PRDEXE2E 080898 22:25 OLD 0001 BKP.MONTH.CONT02(-2) 110050 T SMFSAVE 080898 22:06 M-O 0001 BKP.MONTH.CONT02(+0) PRDEXE2E 080898 22:25 OLD 0001 BKP.MONTH.CONT02(-1) PRDRUN2F 080898 22:28 M-O 0001 BKP.MONTH.CONT02(-2) 110051 T SMFSAVE 080898 22:06 M-O 0001 BKP.MONTH.CONT02(+0) PRDEXE2E 080898 22:25 OLD 0001 BKP.MONTH.CONT02(-1) PRDRUN2F 080898 22:28 M-O 0001 BKP.MONTH.CONT02(-2) 996713 T PRDINPUT 080898 22:02 NEW 0001 PRD.TP.FILE1(+1) 997892 T PRDRPT2D 080898 22:22 NEW 0003 PRD.SNG1912.TAPE2(+1) PRDEXE2E 080898 22:25 OLD 0003 PRD.SNG1912.TAPE2(+0)
SORTBY VOLUME
(REPBYVOL)
7 16
PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD.
TAPE PULL LIST ===================
ODATE TIME VOLSER TYPE JOBNAME DISP DSNAME ------------------------------------------------------------------------080898 22:02 996713 T PRDINPUT NEW PRD.TP.FILE1(+1) S#0001 C NEW PRDW.FILE.GDG.GRPM1(+1) 100047 T M-O BKP.WEEK.CONT01(-2) S#0002 T NEW PRD.TP.TRANS 080898 22:06 110050 T SMFSAVE M-O BKP.MONTH.CONT02(+0) 110051 T 100048 T M-O BKP.MONTH.CONT02(-1) 110049 T 110058 T M-O BKP.MONTH.CONT02(-2) 110059 T 080898 22:09 114003 T PRDUPDT1 OLD PRDW.FILE.GDG.GRP11(+0) 114002 T OLD PRDW.FILE.GDG.GRP11(-1) S#0004 T NEW BKP.MONTH.CONT01(+1) 114003 T OLD PRDW.FILW.GDG.GRP11(+0) S#0005 C NEW PRDO.TP.UPDT1 080898 22:19 S#0006 T PRDRPT2C NEW PRD.TP.DAILY.REPORTS 113492 T OLD PRD.CART.RPT2C S#0007 T NEW BKP.MONTH.CONT02(+1) 080898 22:22 114003 T PRDRPT2D OLD PRDW.FILE.GDG.GRP11(+0) T00001 T NEW PRD.SNG1912.TAPE1(+1) T00002 T NEW PRD.SNG1912.TAPE1(+2) 994529 T NEW PRDW.FILE.GDG.GRP21(+0) 997892 T NEW PRD.SNG1912.TAPE2(+1) S#0008 T NEW &&NEWTEMP 996638 T NEW BKP.MONTH.CONT01(+3) 080898 22:25 T00002 T PRDEXE2E OLD PRD.SNG1912.TAPE1(+0) TOOOO1 T OLD PRD.SNG1912.TAPE1(-1) S#0007 T OLD BKP.MONTH.CONT02(+0) 110050 T OLD BKP.MONTH.CONT02(-1) 110051 T 110048 T OLD BKP.MONTH.CONT02(-2) 110049 T 110058 T OLD BKP.MONTH.CONT02(-3) 110059 T 110056 T OLD BKP.MONTH.CONT02(-4) 110057 T
SORTBY TIME
(REPBYTIM)
7 17
7 18
Section 8: KSL and the Reporting Facility

General ...........................................................................................................................................8-1 KeyStroke Language ...................................................................................................................8-1 Activating KeyStroke Language Scripts ...................................................................................8-2 KSL Command and Variable Summary....................................................................................8-3 Principles of Operation...............................................................................................................8-5 Sample KeyStroke Reports and Utilities ..................................................................................8-9 Language Syntax ......................................................................................................................8-11 KSL Commands and Variables............................................................................................... 8-12 Screen Commands ....................................................................................................................8-12 Flow Commands .......................................................................................................................8-13 Print Commands.......................................................................................................................8-17 Processing Commands..............................................................................................................8-19 KSL Variables...........................................................................................................................8-22 Special KSL Variables..............................................................................................................8-23 Sample KSL Script and its Report Output .............................................................................8-24 Special Purpose Reports ......................................................................................................... 8-33 CTMRFLW: Scheduling Table Job Flow Report.....................................................................8-33 CTMRAFL: Active Jobs File Job Flow Report ........................................................................8-44 CTMRPLN: Job Plan Report....................................................................................................8-45 CTMRPFL: Job Plan/Flow Report ...........................................................................................8-49 CTMRNSC: Night Schedule Report ........................................................................................8-51 CTMROGR: Overnight Execution Graph ...............................................................................8-53 CTMRJDS: Job Dataset Cross Reference Report ...................................................................8-57
KSL and the Reporting Facility: General
General
This section deals with the following related topics:
KeyStroke Language (KSL) The KeyStroke Language is a general purpose language which simulates, in batch, keystrokes entered in the IOA Online facility. KSL statements (commands) are specified in programs called scripts.
Reporting facility Two types of reports are available under CONTROL-M: Reports produced in batch by KSL scripts. CONTROL-M special reports which cannot readily be produced using the Online facility or KSL.
Some CONTROL-M reports are produced from information in the IOA Log file. Other reports are produced from the Active Jobs file, Jobs Statistics file, Job Network file and from scheduling tables. KSL scripts and the Reporting facility can be activated at any time, even if the CONTROL-M monitor is not active.
KeyStroke Language
The most common use of KSL scripts is to generate reports from the IOA Core and IOA product repositories. Utilities are also frequently written in KSL scripts. KSL represents a new concept in mainframe environment reporting and maintenance. If you are familiar with KSL, you can write your own scripts to create reports and utilities. A KSL script only needs to be defined once, after which it can be used repeatedly. The IOA SAMPLE library contains examples of KSL scripts. Member $$DOC in the SAMPLE library contains an index of these samples. Note The user submitting a KSL script must be authorized to perform the online functions performed by the script, or the script will not execute successfully.
81
KSL and the Reporting Facility: KeyStroke Language Activating KeyStroke Language Scripts
Activating KeyStroke Language Scripts

Procedure IOARKSL activates KeyStroke Language scripts:
//KSL EXEC IOARKSL //DAKSLPRM DD * parameters //
Some of the following DD statements are often used in the procedure: DAKSLPRM DAKSLOUT The script input parameters. Record length must be 80. Columns 73 to 80 are ignored. A list of all invoked command members and error/execution messages. When TRACE ON is activated, this list contains all executed commands and screen images of the input/output screen functions performed during script execution. The script output. Name of a partitioned dataset containing script members (for command CALLMEM ). Multiple libraries can be concatenated.
DAKSLREP DACALL
The KeyStroke Language can also be activated as a started task. Specify the script name and parameters in the procedure:
S IOARKSL,PARM=scriptname script-parameters
A KSL program can terminate with the following return codes: 0 8 12 other Ended OK Error in input parameters Severe execution error Generated by the script
82
KSL and the Reporting Facility: KeyStroke Language KSL Command and Variable Summary
KSL Command and Variable Summary

A brief summary of each command is listed below. The commands are grouped into categories. Within each category, the commands are listed alphabetically. Screen Commands CLEAR CURSOR ENTER FIND Paxx Pfxx SCREENSIZE TYPE Flow Commands CALL CALLMEM END EXEC GOTO IFSCREEN IFVAR LABEL MAXCOMMAND PAUSE RETURN Print Commands BOTTOMLINE BOTTOMSIZE HEADERLINE HEADERSIZE PAGESIZE PRINTLINE Specifies a footer message. Sets the size of bottom margin area. Specifies a header message. Sets the size of top margin area. Sets page size. Prints the indicated line. Calls an external program. Calls an external script. Terminates the script normally. Executes an external program. Branches to a labeled script command. Checks status of screen and reacts accordingly. Compares two values and reacts accordingly. Identifies a statement to which script execution should branch. Limits the number of times a statement can be executed. Pauses script for a specified number of hundredths of seconds. Returns to the calling script. Presses <CLEAR> keyboard key. Moves the cursor. Presses <ENTER> keyboard key. Searches for text on screen. Presses Program Attention keys. Presses Program Function keys. Sets size of screen. Operates the keyboard by typing text.
83
KSL and the Reporting Facility: KeyStroke Language KSL Command and Variable Summary
PRINTNEWPAGE PRINTSCREEN SETLINE TRACE
Skips to a new page. Prints screen contents starting from the specified cursor position. Sets the contents of a line for printing. Activates the Trace (debug) facility.
Processing Commands ALLOC CLOSEFILE FREE GETFILE OPENFILE PUTFILE SETOGLB SETOLOC SETVAR SHOUT Dynamically allocates (and assigns an identifying name to) a dataset. Closes the specified dataset. Dynamically frees (and releases an identifying name from) a dataset. Stores the contents of the sequential dataset record into a variable. Opens a dataset for either read, write or update access. Writes the contents of a KSL variable to a dataset. Creates a Global AutoEdit variable or changes its value. Creates a local AutoEdit variable or changes its value. Creates a variable or changes a variables value. Sends a message to a specified destination.
KSL Special Variables %variable %A1-%A9 %CALLRC %FINDRC %MSG %RC %SCRCOL %SCRLINE User-defined KSL variable set by a KSL command (e.g., SETVAR). Arguments to pass to a script. Return code of the last CALL. Return code of the last FIND. Text of script termination which is logged. Return code of the script. Current column position of the cursor. Current line position of the cursor.
AutoEdit Variables and Functions AutoEdit variables and functions start with %%$ and are set by a SETOLOC statement. These variables and functions are described in detail in Appendix C of this manual.
84
KSL and the Reporting Facility: KeyStroke Language Principles of Operation
Principles of Operation
To write a script, imagine that you are using the IOA Online facility. KSL is composed of screen control commands and editing commands. Screen control commands correspond to operations of the terminal keys. Editing commands are required to edit the printed page. At the beginning of the script, you are positioned at the IOA Primary Option menu and, as in the Online facility, the cursor is positioned in the Option field. To explain how KSL works, a simplified example of a script that prints the contents of a specific job scheduling definition is illustrated below: 1. TYPE 2 2. ENTER 3. TYPE DPTT.CTM.SCHEDULE 4. CURSOR NEWLINE 5. TYPE APD 6. CURSOR NEWLINE 7. TYPE APDP0020 8. ENTER 9. PRINTSCREEN 3 23 10. END
1
If the IOA entry panel is mandatory at your site, you will be positioned at the entry panel and you should include commands that will type and enter your user ID and password first.
85
This script produces a printout of the first screen of the job scheduling definition. The explanation below describes each step in the example above. 1. TYPE 2 2. ENTER Equivalent to typing option 2 in the IOA Primary Option menu. Equivalent to pressing <ENTER> on your terminal. As a result, you are entering the Online Scheduling Facility entry panel. On entry to the screen, the cursor is always positioned on the library name field. Type the scheduling library name. 4. CURSOR NEWLINE 5. TYPE APD 6. CURSOR NEWLINE 7. TYPE APDP0020 8. ENTER 9. PRINTSCREEN 3 23 10. END The cursor moves to the table name field. Type the scheduling table name. The cursor moves to the job name field. Type the job name. The job scheduling definition for the specified job is displayed in the Job Scheduling Definition screen. The contents of the screen from line 3 through 23 are printed. End of report.
3.
TYPE DPTT.CTM.SCHEDULE
The KeyStroke Language is a representation of your keystrokes while you are working with the Online facility. Everything that you can display on the screen, you can print. Every selection criterion which can be applied online can be applied in batch mode. The same language is used to work on the screen and on the output of the KSL script. An important advantage of using KSL is that once a script is created, it can be stored in a member in a library. This enables requests to be submitted in batch mode as often as required (daily, weekly, monthly, etc.) and during off-peak hours not convenient for online requests.
86
The following example expands the previous script into a more general purpose script. 1. TYPE 2 2. ENTER 3. TYPE DPTT.CTM.SCHEDULE 4. CURSOR NEWLINE 5. TYPE APD 6. CURSOR NEWLINE 7. TYPE APDP0020 8. ENTER 9. LABEL PRTSCR 10. PRINTSCREEN 3 23 11. CURSOR POS 23 2 12. IFSCREEN GOTO ENDREPORT 13. IFSCREEN ======= > GOTO ENDREPORT If the last line of data on the screen is either blank or the end-of-data message, do not print any more job data. Position the cursor on the Command field in the screen. Scroll down one more page. Go to label PRTSCR and print the screen (loop again). Position the cursor on the last line of the jobs data on the screen. Define a label to which we will later branch from another command (GOTO) .
14. CURSOR HOME 15. PF08 16. GOTO PRTSCR 17. LABEL ENDREPORT 18. END
This script is easy to define, but filling in a different library, table name or job name each time you want to print a job scheduling definition is awkward. It would be much easier if you could supply the library name, table name and job name at the time the script is executed. In fact, you can do just that. Scripts can be defined with special variables (e.g., %A1, %A2, described later in this section) instead of hard-coded values. When activating the script, the values for the special variables can be passed as parameters. In the following example, special variable %A3 represents the job name, %A2 represents the table name, and %A1 represents the library name. Other features, such as a header for the report produced by this script, are also presented.
87
1. HEADERSIZE 5 2. BOTTOMSIZE 1 3. HEADERLINE 3 1 SCHEDULE DEFINITION OF JOB 4. HEADERLINE 3 28 %A3 5. HEADERLINE 3 38 TABLE 6. HEADERLINE 3 48 %A2 7. HEADERLINE 3 58 LIBRARY 8. HEADERLINE 3 68 %A1 9. HEADERLINE 4 1 ------------------------- 10. HEADERLINE 5 11. TYPE 2 12. ENTER 13. TYPE %A1 14. CURSOR BTAB 15. CURSOR NEWLINE 16. TYPE %A2 17. CURSOR BTAB 18. CURSOR NEWLINE 19. TYPE %A3 20. ENTER 21. LABEL PRTSCR 22. PRINTSCREEN 3 23 23. CURSOR POS 23 2 24. IFSCREEN GOTO ENDREPORT 25. IFSCREEN ======= > GOTO ENDREPORT 26. CURSOR HOME 27. PF08 28. GOTO PRTSCR 29. LABEL ENDREPORT 30. PF03 31. PF03 32. PF03 33. RETURN
88
KSL and the Reporting Facility: KeyStroke Language Sample KeyStroke Reports and Utilities
Assume that the above script is kept in member REPJOB. You can produce a printout of two jobs from a scheduling library via the following request:
//KSL EXEC IOARKSL CALLMEM REPJOB DPTT.CTM.SCHEDULE APD APDP0020 CALLMEM REPJOB DPTT.CTM.SCHEDULE APD APDP0035 END
Sample KeyStroke Reports and Utilities

The IOA SAMPLE library contains sample scripts for a variety of reports and utilities. One of the scripts, in member REPJBDEF, produces a listing of job scheduling parameters for:
A specific table. All jobs in a specific table. All jobs in all tables in a library.
Each script invokes CALLMEM members to perform its functions. Note If you choose to modify an existing sample report or utility, it is recommended that you save the changed report under a different name and keep the original report unchanged. This precaution can help in error detection if the altered KSL script does not run as expected.
Scripts for the following reports are in the IOA SAMPLE library: CTMSCALL REP3ALLJ REP3GRUP REP3LEFT Printout of all CONTROL-M screens (for documentation and training). Status of all the jobs currently in the Active Jobs file (tonights schedule, last nights schedule). Status of all the jobs of specified group(s). All jobs still in the Active Job File which did not run during the previous night (wait schedule, ended NOT OK, executing) and the reasons for the problems. All Log messages of last nights restarted jobs. Statistical summary of what should be done tonight, or job status in the morning. Archived sysout of last nights jobs. Status of all jobs using tapes. Status of all jobs of the specified user ID(s). All jobs in the Active Jobs file having a WAIT SCHEDULE status. All abends in a given period. All IOA Log file messages of a specified period. All emergency (recovery) jobs which were activated in a given period.
REP3RSHS REP3STAT
REP3SYSM REP3TAPE REP3USER REP3WHY REP5ABND REP5ALL REP5EMR
89
KSL and the Reporting Facility: KeyStroke Language Sample KeyStroke Reports and Utilities
REP5EXP REP5GRDT REP5GRUP REP5MANL

R
Night exception report. All Log messages for specific group(s) during a specific period. All IOA Log file messages of specified group(s). All manual interventions in a given period. Manual Restart Confirmation report. All IOA Log file messages of specified message code(s) for a specific period. All NOT CATLGD 2 events in a given period. Restart detail report in a given period. Job statistics for jobs run at night. All Log messages of specified user(s). Manual operations to be performed at night. Printout of calendar definitions. Calendars cross-reference. IN conditions cross-reference. Print job definitions/job documentation. Job statistics of a single job. Graphic Jobflow for the specified table. Execution time saved by restarting, instead of rerunning, a job.
REP5MNCN REP5MSGD REP5NCT2
REP5RSTR REP5STAT REP5USER REP7COND REP8CAL REPCRCAL REPCRCON REPJBDEF REPJSTAT REPTBFLW
RPRSAVE
Scripts for the following utilities are in the IOA SAMPLE library: ADDMNCND CHANGRES CHECKCND CNGOVRLB CREATRES DELCNDAL DELMNCND GLBCHANG HOLDGRUP JOBORDER MAYBEJOB NEWMNCND Add manual conditions based on prefix. Change the quantity of a quantitative resource. Check the existence of a prerequisite condition. Assign a value to the OVERLIB field in job scheduling definitions. Create a Control or Quantitative resource. Delete all occurrences of a prerequisite condition. Delete all occurrences of a manual condition. Sample global change to scheduling table. Hold a group of jobs. Schedule (order) tables and/or jobs. Add prerequisite conditions for maybe jobs. Add a new manual condition.
8 10
KSL and the Reporting Facility: KeyStroke Language Language Syntax
REPCNDLL RERUNJOB
Create a dataset of all conditions which exist in the Conditions/Resources file. Rerun a job.
You can use the above examples to design scripts for your own reports utilities.
Language Syntax

A command line is processed from column 1 to 72. A command cannot exceed column 72. Columns 73 to 80 are ignored. A command line can contain all blanks. A command line with * in column 1 is considered a remark. Each line in a script can optionally have one continuation line. To add a continuation line, place an asterisk (*) in column 72 of the initial line. A KSL variable must start with the character % and can be 2-40 characters long. A blank designates the end of the variable name. KSL variables are only accessible by the KSL script in which they are defined. Any reference to the same variable in another command member (or in another invocation of the same command member) is totally independent and has no effect on the current member environment. The value of an AutoEdit variable applies in all command members invoked by a KSL script. To share information between a KSL script and other command members invoked in the same KSL run, either store the information in local AutoEdit variables, or specify the relevant information via the CALL, CALLMEM, or EXEC command. Values for the variables %A1%A9 (arguments) cannot be set by the SETVAR command. They can only be specified as parameters of a CALLMEM command. Special variables %RC and %MSG are also valid during the same invocation of a command member. Therefore, if you use the SETVAR command to assign a value to the variable %RC and then execute RETURN, the value of the variable is lost. Special AutoEdit variables and functions must start with characters %%. They are set using command SETOLOC and are resolved according to the same rules which apply to the IOA AutoEdit facility. When an expression contains both KSL and special AutoEdit variables and functions, the KSL variables are resolved first. A label is valid through the same invocation of a command member. Any reference to the same label in another command member (or in another invocation of the same command member) is totally independent and has no effect on the current member environment. We strongly recommend that the TRACE ON command be activated when performing an update function with the KeyStroke Language. It is, of course, more convenient to write new reports with the TRACE ON. The IOA SAMPLE library contains general purpose command members which can be used to solve typical report functions (e.g., scroll and print).
8 11
KSL and the Reporting Facility: KSL Commands and Variables Screen Commands
KSL scripts may not work in a customized environment. For this reason, it is highly recommended that you run KSL using backup libraries which specify the default values for the IOA environment. KSL and CONTROL-M have different AutoEdit processors. Therefore, if a KSL script containing KSL AutoEdit terms is submitted under CONTROL-M, the CONTROL-M AutoEdit %%RANGE statement should be used in the JCL to ensure that the CONTROL-M AutoEdit processor skips (i.e., does not process) the KSL script.
Note
KSL Commands and Variables

The KSL Language commands are described below. Braces ({ }) indicate that one of the items listed between the braces must be specified. Square brackets ([ ]) denote optionality; none or several of the items listed between the brackets can be specified. Certain commands accept KSL and/or AutoEdit variables. When both KSL and AutoEdit variables are specified, KSL variables are resolved (replaced) first.
Screen Commands
CLEAR CURSOR Equivalent to pressing the <CLEAR> key on the keyboard. Depending on the parameters listed below, CURSOR moves the cursor to the: BTAB HOME NEWLINE Beginning of the previous unprotected input field on the screen. First unprotected input field on the screen. First unprotected input field which appears on the line following the current cursor position line.
POS line-no col-no Specific position on the screen. line-no and col-no can contain constants, or any valid expression consisting of KSL variables and/or AutoEdit variables. TAB ENTER Beginning of the next unprotected input field on the screen.
Equivalent to pressing the <ENTER> key on the keyboard.
FIND {textstring|expression} Searches for text on the screen from the current position of the cursor. If the text is found, the cursor is positioned at the beginning of the text. See special variable %FINDRC for more information. textstring A character string constant. When specifying constants, quotes are not necessary unless spaces are embedded in textstring. To specify a quote inside the text, use two consecutive single quotes. Expression consisting of constants, KSL variables, and/or AutoEdit variables.
expression
8 12
KSL and the Reporting Facility: KSL Commands and Variables Flow Commands
PA01-PA03 PF01-PF24
Equivalent to pressing program attention keys on the keyboard. Equivalent to pressing program function keys on the keyboard.
SCREENSIZE line-no col-no Defines the logical terminal size. Valid terminal sizes: 24 lines x 80 columns 32 lines x 80 columns 43 lines x 80 columns 27 lines x 132 columns TYPE{textstring|expression} Operates the keyboard by typing the text on the screen from the current position of the cursor. If the text is too long for the current field, an error message is produced and the script stops executing. textstring A character string constant. When specifying a constant, the text must be enclosed in single quotes (). To specify a quote inside the text, use two consecutive single quotes. Expression consisting of KSL variables and/or AutoEdit variables. The expression must be enclosed in single quotes (). (Default)
expression
Flow Commands
CALL progname [argument1 argument2 ... argumentn] Calls an external program (progname). The arguments are optional. A maximum of nine arguments can be passed. Use command CALL when the called program expects to receive a list of parameters. The parameters are passed in a format compatible with ASSEMBLER, COBOL and FORTRAN. progname Name of the called program. progname can consist of a constant, or may contain any valid KSL and/or AutoEdit expression. Any text (not containing blanks), constant, KSL variable, or AutoEdit variable to be sent to the called program. (The variable data can contain blanks.)
argumentx
Note
The return code of the called program is stored in special variable %CALLRC (described later in this section).
CALLMEM memname [argument1 argument2 ... argumentn] Calls a predefined KSL script which is located in member memname in the library allocated to DD statement DACALL. The arguments are optional. A maximum of nine arguments can be passed.
8 13
The following process is used for argument resolution (replacement) and syntax checking: Execution branches to the first instruction in the called member. All arguments in the called member are replaced by values assigned in command CALLMEM. Then, a syntax check is performed, and if it is successful, the script continues execution from the first instruction. memname can consist of a constant, or can contain any valid KSL or AutoEdit expression. An argument can consist of any text (not containing blanks) or a KSL and/or AutoEdit variable. (The variable data can contain blanks.) Arguments are replaced in the order in which they are specified. Variable %A1 is replaced by the value of the first argument of command CALLMEM. Variable %A2 is replaced by the value of the second argument, etc. If an argument is omitted, a null value is assumed. Execution of the called member continues until command RETURN is activated (see command RETURN). Command END terminates the entire script. It is possible to activate other CALLMEM commands from the CALLMEM member. A recursive call is also allowed. Note The return code of the called program is stored in variable %CALLRC (described later in this section).
END
Indicates the end of the KSL script. This is a mandatory command in the main script commands list. When activated at any level, the script is terminated.
EXEC progname [argument1 argument2 ... argumentn] Calls an external program (progname). The arguments are optional. A maximum of nine arguments can be passed. Use command EXEC when the called program expects to receive an argument in a format similar to JCLs EXEC PGM argument format. (All arguments are merged into a single argument.) progname Name of the called program. progname can consist of a constant, or can contain any valid KSL and/or AutoEdit expression. Text to be passed to the called program. An argument can consist of any text (not containing blanks), constant, or a KSL and/or AutoEdit variable. (The variable data can contain blanks.)
argumentx
Note
The return code of the called program is stored in variable %CALLRC (described later in this section).
GOTO label-name Branches to the specified label name (which must be in the same command member).
8 14
textstring expression COLOR col IFSCREEN GOTO label ATTR attr HILITE hilite BEEP
If all parts of the conditional expression evaluate to true, script flow branches to the specified label name (which must be in the same command member). At least one parameter must be specified. A parameter cannot be specified more than once within the same conditional expression. Each part of the conditional expression is true if the: textstring Text on the screen at the current cursor position is equal to the specified text. The text must be enclosed in single quotes (). To specify a quote inside the text, use two consecutive single quotes. Text on the screen at the current cursor position is equal to the specified expression. expression consists of KSL variables and/or AutoEdit variables. expression must be enclosed in single quotes. Color of the screen at the current cursor position is equal to the specified color (col). Valid col values: WHITE RED PINK TURQUOISE ATTR attr GREEN BLUE YELLOW NOCOLOR
expression
COLOR col
Screen attribute at the current cursor position is equal to the specified attribute (attr). Valid attr values: U P L H D N S UL UH UD Unprotected Protected Low intensity High intensity Dark Numeric Skipped Unprotected and low intensity Unprotected and high intensity Unprotected and dark
8 15
NL NH ND PL PH PD SPL SPH SPD
Numeric and low intensity Numeric and high intensity Numeric and dark Protected and low intensity Protected and high intensity Protected and dark Skipped, protected and low intensity Skipped, protected and high intensity Skipped, protected and dark
HILITE hilite Highlight of the screen at the current cursor position is equal to the hilite value specified. Valid hilite values: REVERSE USCORE BLINK NONE BEEP Terminal beep. Reverse video Underline Blink No highlight
IFVAR operand operator operand GOTO labname where: operand operator A KSL variable or constant and/or AutoEdit variable. Constants must be enclosed in single quotes. One of the following operators. Used to compare the specified operands. Operator Meaning EQ NE GT GE LT LE labname is equal to is not equal to is greater than is greater than or equal to is less than is less than or equal to
Label name to which script will branch. Specified via command LABEL (described below). Operands are compared as character strings from left to right. For example, 91 is greater than 1000, because 9 is greater than 1.
Note
8 16
KSL and the Reporting Facility: KSL Commands and Variables Print Commands
IFVAR is used together with command GOTO to permit branching based on different runtime conditions. If the condition is true, flow branches to the specified label name (must be in the same command member). LABEL name Defines a label to which script flow can branch. Maximum length: 50 characters.
MAXCOMMAND max Maximum number of commands that can be executed in the script. Default: 400. This is designed to prevent an accidental loop. PAUSE n Where n= hundredths of seconds. Causes the script to wait the specified amount of time.
RETURN[return-code|expression] Returns to the calling script. return code Must be a number from 0 to 4095. When command RETURN is activated, control is passed to the command after the CALLMEM command in the calling member. Variable %CALLRC in the calling member is set to the value of the return code. Default is 0. Expression consisting of KSL variables and/or AutoEdit variables.
expression
Print Commands
BOTTOMLINE line-no pos-in-line {textstring|varname} Assigns contents to a line in the page footer. The footer contents are valid throughout the script until overridden by another BOTTOMLINE command for the same line in overlapping positions. Command BOTTOMSIZE overrides the current BOTTOMLINE specifications. line-no pos-in-line textstring varname Relative number of the line in the footer. Relative position in the line in the footer. Must be enclosed in single quotes (). To specify a quote inside the text, use two consecutive single quotes. KSL variable.
BOTTOMSIZE line-no Specifies the number of lines in the report bottom (footer) (1 minimum 15 maximum). The bottom size is valid throughout the script until a new BOTTOMSIZE command is activated. HEADERLINE line-no pos-in-line{textstring|varname} Assigns contents to a line in the page header. The header contents are valid throughout the script until overridden by another HEADERLINE command for the same line in overlapping positions. Command HEADERSIZE overrides the current HEADERLINE specifications. line-no pos-in-line Relative number of the line in the header. Relative position in the line in the header.
8 17
KSL and the Reporting Facility: KSL Commands and Variables Print Commands
textstring varname
Must be enclosed in single quotes (). To specify a quote inside text, use two consecutive single quotes. KSL variable.
HEADERSIZE line-no Specifies the number of lines in the report header (1 minimum 15 maximum). The header size is valid throughout the script until a new HEADERSIZE command is activated. PAGESIZE line-no col-no Defines the maximum size of a printed page. line-no col-no Number of lines in the page. Default: 60. In the current IOA release, the column number must be 132.
PRINTLINE line-no Prints the contents of the line identified by line-no (a number from 1-9999). PRINTNEWPAGE Skips to a new page. Each occurrence of command PRINTNEWPAGE in a KSL script must be preceded by commands SCREENSIZE, PAGESIZE, HEADERSIZE and BOTTOMSIZE. PRINTSCREEN from-line until-line Prints the screen contents of the specified line range. from-line until-line The first line of screen contents to be printed. The last line of screen contents to be printed.
SETLINE identifier pos-in-line {textstring|varname} Assigns contents to a line which is about to be printed. identifier pos-in-line textstring varname Number (from 1-9999) which identifies a line. Number which identifies a position in the line. Must be enclosed in single quotes (). To specify a quote inside the text, use two consecutive single quotes. KSL variable.
TRACE {ON|OFF} Simplifies problem resolution using the Trace (debug) facility while defining a script. ON Start producing a complete printed output of every command execution, screen I/O, and command member invocation. It is highly recommended that KSL utilities which are performing updates of any database operate with TRACE ON to simplify problem resolution. Command TRACE can be activated any number of times within a script to turn on/off the Trace facility. Stop producing the printed trace. Default.
OFF
8 18
KSL and the Reporting Facility: KSL Commands and Variables Processing Commands
Processing Commands
ALLOC DD ddname DS dsname[MEM memname][{SHR|OLD|MOD}] Dynamically allocates the dataset dsname to the specified DD name. memname Member name for PDS members. Mandatory for PDS members. Must be left blank for non-PDS members. memname can be any valid member name consisting of a constant, KSL variable, or AutoEdit variable. Any valid DD name consisting of a constant, KSL variable, or AutoEdit variable. Any valid dataset name consisting of a constant or KSL variable.
ddname dsname
SHR, OLD,MOD Specify the dataset disposition. Optional. Default is SHR. Before a dataset can be accessed (e.g., with OPENFILE, GETFILE), it must be allocated and assigned a DD name. Similarly, when the dataset no longer needs to be accessed, the dataset and DD name should be released (see command FREE). The DD name should be unique within a job step. CLOSEFILE ddname Closes sequential dataset ddname. ddname Any valid DD name consisting of a constant, KSL variable, or AutoEdit variable.
FREE DD ddname Dynamically frees the dataset allocated to the specified DD name. (The DD name is assigned by command ALLOC.) This command should be activated when a dataset no longer needs to be accessed by the script. GETFILE ddname INTO varname Stores the contents of the next record in the sequential file referenced by ddname into the specified variable. ddname varname Any valid DD name consisting of a constant, KSL variable, or AutoEdit variable. A KSL variable name where contents will be stored.
INPUT OPENFILE ddname OUTPUT [ENDFILE label] UPDATE

Opens sequential dataset ddname for access. ddname INPUT OUTPUT Any valid DD name consisting of a constant, KSL variable, or AutoEdit variable. Opens the sequential dataset as a read-only file. No changes can be made to the file. Allows data to be written to the file (write access).
8 19
UPDATE
Allows the file to be read and modified (read/write access). Default.
ENDFILE label Specifies a label name to which script processing flow branches when the end of sequential dataset ddname is reached. ENDFILE is mandatory when ddname is opened for INPUT or UPDATE access. PUTFILE ddname FROM varname Writes the contents of variable varname in the next record of the sequential file referenced by ddname. ddname varname Note Any valid ddname consisting of a constant or KSL variable. Specifies a KSL variable whose contents will be written. AutoEdit variables (i.e., variables beginning %%) cannot be used with a PUTFILE command. Instead, such a variable should be passed to a KSL variable (i.e., a variable beginning with a single %). The KSL variable should be specified in the PUTFILE command.
%%var = value SETOGLB %%var = expression %%autoedit - control - statement

Assigns the appropriate value to the variable name. This command is used to create (set) a global AutoEdit variable. expression may contain a KSL variable. Note This command is only available if CONTROL-O is installed at your site. Global AutoEdit variables can only be used when the CONTROL-O monitor is up. See statement DO SET in Section 3 of the CONTROL-O User Manual for more information.
%%var = value SETOLOC %%var = expression %%autoedit - control - statement

Assigns the value of the expression to the variable name. This command is used to create (set) a Local AutoEdit variable. expression may contain a KSL variable. SETVAR varname CURSOR length Assigns extracted text to variable varname. This command is used to create (set) variables. varname length Name of KSL variable in which the text is stored. The length (in characters) of the extracted text. The text at the current cursor position of the specified length is extracted and assigned to the variable name.
8 20
SETVAR varname DATA{textstring|expression} Assigns a text string to variable varname. This command is used to create (set) variables. varname textstring Name of KSL variable in which the text is stored. textstring is assigned to the variable name. textstring is a character string constant. When specifying a constant, the text must be enclosed in single quotes (). To specify a quote in the text, type two consecutive single quotes. Expression containing KSL variables and/or AutoEdit symbols. expression must be enclosed in single quotes if it contains embedded blanks.
expression
SETVAR varname SCREEN from-line from-col length Assigns extracted text to variable varname. This command is used to create (set) variables. varname Name of KSL variable in which the text is stored.
Variable value is determined by the screen contents at a specific screen position. The screen position is specified by: from-line from-col length Starting from this line position, screen contents are extracted. Starting from this column position, screen contents are extracted. The length in characters of the extracted text.
SHOUT TO destination [URGENCY urgency] TEXT {textstring|expression} Sends (shouts) a text string to the specified destination. destination Specifies a destination of 116 characters in length. Valid destination values are: OPER[-n] Sends the message to the operator console. n is the route code and must be a 2-digit number. Sends an unrollable, highlighted message to the operator console. n is the route code and must be a 2-digit number.
OPER2[-n]
; Nm ; Mm TSO - logonid ; NnMm ; Lname

Sends the message to a TSO user. logonid must be 17 characters, and may contain valid KSL and/or AutoEdit variables.
8 21
KSL and the Reporting Facility: KSL Commands and Variables KSL Variables
When the ; option is used: Under JES2 Mm where m is the machine ID. (This is the ID of the computer in JES2, not the 4-character SMF ID. You can use the $LSYS JES command to determine the JES ID.)
Nn or NnMm where n is the JES/NJE node ID (up to 2 characters), and m is the machine ID Under JES3 Lname where name is the logical JES name of the machine (as used in the JES3 command *T, not the MVS/SMF system ID).
textstring
Indicates the text that should be sent. textstring is a constant character string. Quotes will appear in textstring exactly as they are typed in the KSL script. Expression containing KSL and/or AutoEdit variables can be specified. Quotes will appear in text exactly as they are typed in the KSL script. Indicates how critical the situation is. Optional. Valid values: R Regular. Default. U Urgent V Very urgent
expression
urgency
KSL Variables
KSL variables can be used to add flexibility to a KSL script. These variables are assigned via a KSL command (e.g., SETVAR) and are resolved during the run of the KSL script. A KSL variable must start with % and can be 2-40 characters long. A blank designates the end of the variable name. Notes The second character in a KSL variable name must not be a percent sign. KSL assumes that a variable beginning with %% is an AutoEdit variable. If a KSL script is to search for a prerequisite condition whose name begins with a single percent sign (%), KSL will assume it is a KSL user-defined variable and will not recognize the searched-for condition.
KSL variables are only accessible by the KSL script in which they are defined. A reference to the same variable in another command member (or in another invocation of the same command member) is totally independent and has no effect on the current member environment. When an expression contains both KSL and special AutoEdit variables and functions, KSL variables are resolved first. For more information about syntax and KSL variables, see Language Syntax earlier in this section.
8 22
KSL and the Reporting Facility: KSL Commands and Variables Special KSL Variables
Special KSL Variables

Some KSL variables are reserved by, and have a special meaning for, KSL: %A1-%A9 Passes the specified arguments to a called script. The number corresponds to the position of the argument in command CALLMEM. The argument is replaced throughout the called script member at invocation time. Contains the return code specified in the RETURN command when returning from command CALLMEM. Also contains the return code from programs called via the CALL or EXEC commands. Provides the return code of the result of the last FIND. If the last FIND was successful, %FINDRC has a value of 0. If the last FIND was unsuccessful, %FINDRC has a value of 4. Specifies text assigned at script termination which appears as a message in the jobs SYSLOG and the script execution listing. Only the value of variable %MSG at the script member issuing command END is displayed. Supplies the return code of the script. The value at successful script termination will be the condition code of the step. Valid values: 0-4095. Current column position of the cursor. Current line position of the cursor.
%CALLRC
%FINDRC
%MSG
%RC %SCRCOL %SCRLINE
8 23
KSL and the Reporting Facility: KSL Commands and Variables Sample KSL Script and its Report Output
Sample KSL Script and its Report Output

The following is a sample KSL script.
110.08.44 KSL401I A KEYSTROKE REPORT STARTED ** * * * THIS SMALL REPORT CAN DO MORE THAN ITS SIZE CAN TELL.. * * * * THE PARAMETERS TO THE REPORT SHOULD BE: * * * * CALLMEM REPSCHED LIBRARY TABLE JOBNAME DOC-OPT * * * * LIBRARY - MUST BE A NAME OF A SCHEDULING TABLES PARTITIONED * * DATA SET * * * * TABLE - A NAME OF A SPECIFIC TABLE IN THE LIBRARY OR * * 'ALL' FOR ALL THE SCHEDULING TABLES IN THE * * LIBRARY * * * * JOBNAME - A NAME OF A SPECIFIC JOB IN THE TABLE OR * * 'ALL' FOR ALL THE JOBS IN THE SCHEDULING * * TABLE(S) * * * * DOC-OPT - 'DOC' PRINT WITH JOB DOCUMENTATION * * 'NODOC' PRINT WITHOUT JOB DOCUMENTATION * * * ** TRACE OFF 999999 SETVAR %TEMP DATA CTM.PROD.SCHEDULE CALLMEM REPSCHED %TEMP PRODYH ALL NODOC END
8 24
A GENERAL REPORT ROUTINE TO PRINT JOB SCHEDULE(S)
* * ARGUMENTS * A1 LIBRARY * A2 TABLE NAME * A3 JOBNAME * A4 DOC - WITH JOB DOCUMENTATION * NODOC - NO JOB DOCUMENTATION * * IF TABLE = ALL - A LIST OF ALL THE TABLES IN THE LIBRARY AND * ALL THE JOB SCHEDULES IN THEM * * IF JOBNAME = ALL - A LIST OF ALL THE JOBS IN THE TABLE(S) * * SCREEN SIZE 24 80 IS A MUST IN THIS REPORT - DO NOT CHANGE IT * SCREENSIZE 24 80 PAGESIZE 60 132 HEADERSIZE 2 BOTTOMSIZE 2 CURSOR HOME TYPE 2 ENTER * * WE ARE NOW POSITIONED ON THE JOB SCHEDULING ENTRY SCREEN SEE WHAT TYPE OF REPORT IS NEEDED
CURSOR HOME CURSOR NEWLINE TYPE CURSOR BTAB TYPE %A1 CURSOR BTAB SETVAR %LIB CURSOR 44 CURSOR TAB TYPE CURSOR BTAB TYPE %A2 CURSOR BTAB SETVAR %TABLE CURSOR 8 TYPE TYPE CURSOR BTAB TYPE %A3 CURSOR BTAB SETVAR %JOB CURSOR 8 TYPE TYPE TYPE N IFVAR %A4 EQ NODOC GOTO NODOC-DEFINE CURSOR BTAB TYPE Y LABEL NODOC-DEFINE TYPE N ENTER CURSOR POS 1 2 IFSCREEN LIST GOTO CHECK-OPTION
8 25
* * *
AN ERROR OCCURRED WHILE TRYING TO ENTER THE ZOOM SCREEN
SETLINE 2003 10 SETLINE 2001 10 ***** ERROR WHILE TRYING TO ENTER LIST OF TABLES SETLINE 2001 60 ***** SETLINE 2002 10 THE ERROR MESSAGE WAS: SETVAR %ERR SCREEN 1 1 80 SETLINE 2004 10 %ERR PRINTLINE 2003 PRINTLINE 2001 PRINTLINE 2002 PRINTLINE 2003 PRINTLINE 2004 SETVAR %MSG DATA >>> ERROR IN REPORT EXECUTION - SEE DETAILS INSIDE SETVAR %RC DATA 20 GOTO TO-MAIN-SCREEN1 LABEL CHECK-OPTION IFVAR %A2 EQ ALL GOTO ALL-TABLES *----------------------------------------------------------------* * PRINT SCHEDULE DEFINITION OF A SPECIFIC JOB IN A SCHEDULING TABLE * *----------------------------------------------------------------LABEL SPECIFIC-JOB CALLMEM RPDLOCV %TABLE ENTER CURSOR POS 1 2 IFSCREEN CTM557 GOTO TABLE-NOT-FOUND CALLMEM RPDLOCV %TABLE ENTER TYPE B ENTER ENTER CURSOR POS 1 2 IFSCREEN IOAE31E GOTO JOB-LIST-ERROR IFSCREEN CTM720E GOTO EMPTY-TABLE IFVAR %A3 EQ ALL GOTO ALL-JOBS CALLMEM RPDLOCV %JOB ENTER CURSOR POS 1 2 IFSCREEN CTM557 GOTO JOB-NOT-FOUND CALLMEM RPDLOCV %JOB ENTER TYPE S ENTER * * *
PRINT THE JOB DEFINITION
LABEL PRINT-JOB-DEFINITION CALLMEM REPZOOM %LIB %TABLE %JOB IFVAR %CALLRC EQ 0 GOTO TO-MAIN-SCREEN4 SETVAR %MSG DATA >>> ERROR IN REPORT EXECUTION - SEE DETAILS INSIDE SETVAR %RC DATA 20 GOTO TO-MAIN-SCREEN4
8 26
******************************************************************** * PRINT A LIST OF TABLES IN A LIBRARY AND * * FOR EACH TABLE PRINT THE JOBS LIST AND * * FOR EACH JOB IN THE TABLE PRINT THE JOB DEFINITION * ******************************************************************** LABEL ALL-TABLES CALLMEM REPTBLST CURSOR HOME TYPE M PF07 CURSOR POS 4 3 IFSCREEN ====== CURSOR HOME CURSOR TAB TYPE C * * *
GOTO TO-MAIN-SCREEN2
LOOP ON ALL THE TABLES AND ENTER THE JOBS LIST SCREEN OF EACH
LABEL CHECK-EMPTY SETVAR %SPACE SCREEN 4 7 8 IFVAR %SPACE NE $$$SPACE GOTO PRINT-TABLES-LOOP CURSOR HOME CURSOR NEWLINE CURSOR NEWLINE PF08 LABEL PRINT-TABLES-LOOP CURSOR HOME CURSOR NEWLINE TYPE B SETVAR %TABLE SCREEN 4 7 8 ENTER ENTER CURSOR POS 1 2 IFSCREEN IOAE31E GOTO JUMP-TO-NEXT IFSCREEN CTM720E GOTO EMPTY-TABLE CALLMEM REPJBLST %TABLE %LIB IFVAR %CALLRC EQ 0 GOTO PRINT-JOB-LIST-3 * * IN CASE OF ERROR, CLEAN THE COMMAND FIELD AND THE S NEAR THE * TABLE NAME * LABEL EMPTY-TABLE SETLINE 2003 1 SETLINE 2001 1 ******** ERROR IN JOB LIST SCREEN ******* SETLINE 2002 1 THE ERROR MESSAGE WAS: SETVAR %ERR SCREEN 1 1 80 SETLINE 2004 1 %ERR SETLINE 2005 2 LIBRARY: SETLINE 2005 14 %LIB SETLINE 2005 45 TABLE: SETLINE 2005 52 %TABLE PRINTLINE 2003 PRINTLINE 2001 PRINTLINE 2002 PRINTLINE 2004 PRINTLINE 2005 SETVAR %RC DATA 24
8 27
SETVAR %MSG DATA >>> EMPTY MEMBER WAS FOUND >>> CURSOR HOME ===> TYPE CANCEL ENTER GOTO TO-MAIN-SCREEN1 LABEL JUMP-TO-NEXT SETVAR %INVLD SCREEN 1 2 54 SETLINE 3001 1 %INVLD SETLINE 3001 55 %TABLE PRINTLINE 3001 CURSOR HOME CURSOR NEWLINE TYPE GOTO PRINT-TABLES-LOOP-CONT * * PREPARE TO ENTER THE SCHEDULE DEFINITION OF EACH JOB * LABEL PRINT-JOB-LIST-3 CURSOR HOME TYPE M PF07 * * LOOP ON ALL THE JOBS IN THE JOBS LIST SCREEN * LABEL PRINT-JOBS-LOOP-3 CURSOR POS 4 3 IFSCREEN ====== GOTO END-JOBS-LIST-3 CURSOR HOME IFVAR %A3 EQ ALL GOTO LOOK-FOR-ALLJOBS CALLMEM RPDLOCV %JOB ENTER CURSOR POS 1 2 IFSCREEN CTM557 GOTO JOB-NOT-FOUND CALLMEM RPDLOCV %JOB ENTER GOTO LOOK-FOR-JOB LABEL LOOK-FOR-ALLJOBS CURSOR NEWLINE
Scroll ==
LABEL LOOK-FOR-JOB TYPE S ENTER CURSOR POS 1 2 IFSCREEN IOAE02I GOTO PRINT-JOB-DEFINITION-3 CURSOR POS 3 2 IFSCREEN +----- GOTO PRINT-JOB-DEFINITION-3 SETLINE 2003 10 SETLINE 2001 10 ***** ERROR WHILE TRYING TO ENTER ZOOM SCREEN ***** SETLINE 2002 10 THE ERROR MESSAGE WAS: SETVAR %ERR SCREEN 1 1 80 SETLINE 2004 10 %ERR PRINTLINE 2003 PRINTLINE 2001 PRINTLINE 2002 PRINTLINE 2003 PRINTLINE 2004 PRINTNEWPAGE
8 28
CURSOR CURSOR TYPE CURSOR GOTO
HOME NEWLINE HOME PRINT-JOBS-LOOP-CONT-3
LABEL PRINT-JOB-DEFINITION-3 CALLMEM REPZOOM %LIB %TABLE %JOB PF03 GOTO PRINT-JOBS-LOOP-CONT-3 LABEL PRINT-JOBS-LOOP-CONT-3 CURSOR HOME IFVAR %A3 NE ALL GOTO END-JOBS-LIST-3 CURSOR POS 4 3 IFSCREEN ====== GOTO END-JOBS-LIST-3 *PRINTNEWPAGE CURSOR HOME TYPE C CURSOR POS 5 2 PF08 GOTO PRINT-JOBS-LOOP-3 * * *
EXIT THE JOBS LIST SCREEN (TYPE N FOR NO SAVE IN THE EXIT WINDOW)
LABEL END-JOBS-LIST-3 PF03 GOTO PRINT-TABLES-LOOP-CONT * * *
CONTINUE TO LOOP ON THE TABLES LIST
LABEL PRINT-TABLES-LOOP-CONT CURSOR HOME TYPE C CURSOR POS 5 2 PF08 CURSOR POS 4 3 IFSCREEN ====== GOTO TO-MAIN-SCREEN2 *PRINTNEWPAGE GOTO PRINT-TABLES-LOOP ******************************************************************** * PRINT A LIST OF JOBS IN A GIVEN SCHEDULING TABLE AND THE * * DEFINITION OF EACH JOB * ******************************************************************** LABEL ALL-JOBS CALLMEM REPJBLST %TABLE %LIB CURSOR HOME TYPE M PF07 CURSOR POS 4 3 IFSCREEN ====== GOTO TO-MAIN-SCREEN3 LABEL PRINT-JOBS-LOOP CURSOR HOME CURSOR NEWLINE TYPE S SETVAR %JOB SCREEN 4 7 8 ENTER
8 29
CURSOR POS 3 2 IFSCREEN +----- GOTO PRINT-JOB-DEFINITION-2 SETLINE 2003 10 SETLINE 2001 10 ***** ERROR WHILE TRYING TO ENTER ZOOM SCREEN ***** SETLINE 2002 10 THE ERROR MESSAGE WAS: SETVAR %ERR SCREEN 1 1 80 SETLINE 2004 10 %ERR PRINTLINE 2003 PRINTLINE 2001 PRINTLINE 2002 PRINTLINE 2003 PRINTLINE 2004 SETVAR %MSG DATA >>> ERROR IN REPORT EXECUTION - SEE DETAILS INSIDE SETVAR %RC DATA 20 GOTO TO-MAIN-SCREEN3 LABEL PRINT-JOB-DEFINITION-2 CALLMEM REPZOOM %LIB %TABLE %JOB PF03 LABEL PRINT-JOBS-LOOP-CONT CURSOR NEWLINE PF08 CURSOR POS 4 3 IFSCREEN ====== GOTO TO-MAIN-SCREEN3 PRINTNEWPAGE GOTO PRINT-JOBS-LOOP LABEL TABLE-NOT-FOUND SETLINE 2003 10 SETLINE 2001 2 *** TABLE SETLINE 2001 12 %TABLE SETLINE 2001 21 NOT FOUND IN : SETLINE 2001 36 %A1 *** PRINTLINE 2003 PRINTLINE 2003 PRINTLINE 2001 PRINTLINE 2003 SETVAR %RC DATA 8 GOTO TO-MAIN-SCREEN2 LABEL JOB-NOT-FOUND SETLINE 2003 10 SETLINE 2001 2 *** JOB SETLINE 2001 10 %JOB SETLINE 2001 19 NOT FOUND IN THE TABLE SETLINE 2001 42 %TABLE SETLINE 2001 50 *** PRINTLINE 2003 PRINTLINE 2001 PRINTLINE 2003 SETVAR %RC DATA 4 IFVAR %A2 EQ ALL GOTO PRINT-JOBS-LOOP-CONT-3 SETVAR %RC DATA 8 GOTO TO-MAIN-SCREEN3
LABEL JOB-LIST-ERROR SETLINE 2003 10 SETLINE 2001 10 **** ERROR WHILE TRYING TO ENTER JOBS LIST SETLINE 2001 53 SCREEN **** SETLINE 2002 10 THE ERROR MESSAGE WAS: SETVAR %ERR SCREEN 1 1 80 SETLINE 2004 10 %ERR PRINTLINE 2003
8 30
PRINTLINE 2001 PRINTLINE 2002 PRINTLINE 2003 PRINTLINE 2004 SETVAR %MSG DATA >>> ERROR IN REPORT EXECUTION - SEE DETAILS INSIDE SETVAR %RC DATA 20 GOTO TO-MAIN-SCREEN2 LABEL TO-MAIN-SCREEN4 PF03 LABEL TO-MAIN-SCREEN3 PF03 LABEL TO-MAIN-SCREEN2 PF03 LABEL TO-MAIN-SCREEN1 PF03 END
8 31
Output #1 from the sample KSL Script:

KEYSTROKE REPORTING LANGUAGE (REL 5.1.4) DATE 08/08/98 TIME 10.08 PAGE 000001
LIST OF JOBS TABLE: PRODYH LIB: CTM.PROD.SCHEDULE ============================================================================= --------------------------------------------------------------------------PRODYIDK UPDATE # 1 PRODYHST UPDATE # 2 PRODYJCL CREATE INPUT FILES # 2 PRODYBTL REPORTS FOR BRANCHES PRODYHTK PROCESS INPUT DATA FOR PRODYHST PRODYHC2 CREATE INPUT FILE # 2 PRODYBCK PROCESS INPUT DATA FOR PRODYIDK PRODYIZN REPORTS FOR BRANCH MANAGERS PRODYEND REPORTS FOR MAIN OFFICE PROJYFOT BEGIN OF EVENING PROCESS PROJYMRG EVENING UPDATE PROCEDURE PROJYMTI VERIFICATION PROCESS OF EVENING UPDATE PROJYHO1 SPECIAL CALCULATIONS FOR ACCOUNTING DEPARTMENT PROJYHO2 REPORTS FOR ACCOUTING DEPARTMENT PROJYDPY UPDATE OF ON-LINE FILES PROJYDTK REPORTS OF ON-LINE FILES PROJYDLI CREATE DUAL ON-LINE FILE PROYH11 YH APPLICATION UPDATE PROJYFIN CLEAN-UP FOR YH APPLICATION PROJYBNK VERIFICATION OF BRANCH BALANCES PROJEND FINAL YH APPLICATION PROCEDURE PROLYPAR NIGHT INPUT COLLECTION # 1 PROLYDOC BACKUP FILES STATUS REPORTS PROLYFMZ REPORTS FOR MAIN OFFICE PROLYDEL DELETE TEMPORARY "REPORT" FILES PROLYBME CREATE EXTERNAL TAPE PROLYDM2 ARCHIVE YH APPLICATION DATA SETS #2 PROLYDM1 ARCHIVE YH APPLICATION DATA SETS #1 ======= >>>>>>>>>>>>>>>>>>> NO MORE JOBS IN TABLE <<<<<<<<<<<<<<<< =======
Output #2 from the sample KSL Script:

NEW DIMENSION SOFTWARE, LTD. IOA KEY-STROKE REPORTING LANGUAGE (REL 5.1.4) DATE 08/08/98 TIME 10.12 PAGE 000001
SCHEDULE DEFINITION OF MEMBER PRODYBCK IN TABLE PRODYH LIBRARY CTM.PROD.SCHEDULE ====================================== +----------------------------------------------------------------------------+ | MEMNAME PRODYBCK MEMLIB CTM.PROD.SCHEDULE | | OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y | | APPL APPL-L GROUP BKP-PROD-L | | DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L | | OVERLIB CTM.OVER.SCHEDULE | | SET VAR | | CTB STEP AT NAME TYPE | | DOCMEM PRODYBCK DOCLIB CTM.PROD.DOC | | =========================================================================== | | DAYS DCAL | | AND/OR | | WDAYS WCAL | | MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y | | DATES | | CONFCAL WORKDAYS SHIFT RETRO N MAXWAIT 04 D-CAT | | MINIMUM PDS | | =========================================================================== | | IN START-DAILY-BACKUP ODAT | | CONTROL | | RESOURCE INIT 0001 CART 0001 | | | | TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM | | =========================================================================== | | OUT BAKCKPL02-ENDED-OK ODAT + | | AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS | | SYSOUT OP (C,D,F,N,R) FROM | | RERUN - MAXRERUN RERUNMEM INTERVAL | | STEP RANGE FR (PGM.PROC) . TO . | | ON PGMST PROCST CODES A/O | | DO | | SHOUT WHEN TO URGN | | MS | ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< ======
8 32
KSL and the Reporting Facility: Special Purpose Reports CTMRFLW: Scheduling Table Job Flow Report
Special Purpose Reports

The following reports are provided as jobs in the JCL library.
CTMRFLW: Scheduling Table Job Flow Report

Report CTMRFLW provides job flow information about jobs in scheduling tables. The report can generate two types of output:
Job Flow Report Displays the job dependencies of the jobs in the scheduling table(s). This output is always generated. Jobs are presented in order of execution. The jobs can be sorted by group, in which case, they are presented in order of execution by group. This report can be generated in the following formats: Text format Chart format Report consists of printed text. This format is always generated. A graphic presentation of job dependencies (in addition to the text format). Job flow is displayed from left to right (i.e., leftmost jobs are not dependent on other jobs). When sorted by group, one group appears in each chart.
Note
The Job Flow chart can also be viewed online by specifying option G (Graphic Jobflow) in the Table list screen in the Scheduling Definition facility. See Section 2 for details.
Cross Reference lists Lists the conditions and resources added/deleted/required by the jobs in the tables. Three separate lists can be produced: Prerequisite conditions list Control resource list Quantitative resource list
The contents of each list are sorted alphabetically. The Cross Reference lists can be useful for identifying various job requirements. For example: Jobs which require more than three tape drives. Jobs which require IMS to be active before they can be executed. Jobs which update a particular VSAM file. Job interdependency.
By default, the number of lines in a report page is 60. This default can be modified in the EXEC statement. Furthermore, by default, all jobs in the scheduling table(s) are included in the report. This default can be modified in the EXEC statement by specifying a successor or a predecessor job:
If you specify a successor job, information is provided only for the predecessor jobs leading up to that successor job. If you specify a predecessor job, information is provided only for the successor jobs which follow that predecessor job.
8 33
EXEC Statement Parameters

//CTMRFLW EXEC CTMRFLW[,] [PARM=LINECNT=linecount[,SUCCESR=jobname|PREDESR=jobname]]
The following parameters can be included in the EXEC statement: LINECNT SUCCESR Number of lines per report page. This parameter does not impact the chart format. Default: 60. Name of the successor job. If specified, only predecessor jobs of this job will be included in the report. This parameter cannot be specified if parameter PREDESR is specified. Name of the predecessor job. If specified, only successor jobs of this job will be included in the report. This parameter cannot be specified if parameter SUCCESR is specified.
PREDESR
Report Parameters
Report parameters are optional. They are supplied via DD statement DAFLWPRM (or SYSIN). JOBSDD ddname DDname of the library. If specified, all members of the library are processed by the utility. This makes it unnecessary to specify a concatenation of DD statements (one statement for each table) in the JCL. GROUP [ALL|UNITED|groupname] Indicates which groups to include in the report, and the sort order of the information included. Valid values: ALL Sorts the jobs according to group as defined in the parameter GROUP in the job scheduling definitions. Jobs are displayed in order of execution within each group. Default. All the jobs in the scheduling table(s) are considered as one group. Jobs are displayed in order of execution. Includes the jobs of only the groups specified. Up to 20 groups can be specified, each on a different GROUP line., Jobs are displayed in order of execution within each group. Group names should not be specified if ALL or UNITED is specified. Character masking of specified group names is supported, as follows: ? * represents any one character. represents any number of characters (including no characters).
UNITED groupname
8 34
CONTROLO
If specified, CTMRFLW reads the CONTROL-O table specified in DD statement DACTO. CTMRFLW then marks all manual conditions added by CONTROL-O rules with an asterisk (*), to distinguish them from other manual conditions. If this parameter is not specified, the CONTROL-O table is not read.
JOBFLOW XREFCOND REPORT XREFCNTL XREFQUANT

Indicates the type of report to print. Each REPORT line can contain only one report type, but multiple REPORT lines can be specified. If no REPORT lines are specified, all report types are printed. Valid values: JOBFLOW XREFCOND XREFCNTL Job Flow report Cross Reference list Prerequisite conditions Cross Reference list Control resources
XREFQUANT Cross Reference list Quantitative resources CHART [YES|NO] Indicates whether or not to print the Job Flow report in Graphic (chart) format. Valid values: YES NO Note Produce a chart in addition to the Job Flow report. Produce only the Job Flow report. Default. The following parameters apply only if CHART YES is specified (i.e., the chart is to be produced).
PRINTER [LASER|IMPACT] Type of printer on which the chart is to be produced. Valid values: LASER IMPACT Note IBM 38xx laser printer or compatible only. Default. Any impact printer (1403, 3211, 3203, 3262, etc.). If you are using a laser printer but you specify the printer as IMPACT, the report will be printed to the laser printer, but no graphic features will be printed.
FONT font-code Valid only if PRINTER LASER is specified. FONT affects the quality and type of drawing in the chart. Valid font-codes: 1 2 3 4 9 Fine line. Medium line. Default. Heavy line. Very small characters. High-quality IBM character set. This font is not available at all IBM sites. Contact your IBM representative if you do not have this font.
8 35
LINESIZE col-no Maximum number of columns in a line of the logical page, where col-no is a multiple of 16, between 16 and 240. Default: 128. PAGESIZE line-no Maximum number of lines in a logical page, where line-no is a multiple of 4, between 12 and 120. Default: 80. Note The logical PAGESIZE and LINESIZE must not exceed that of the physical page. For best results, define the maximum PAGESIZE and LINESIZE that the physical page can accommodate.
PAGESEQ [YES|NO] A chart may exceed the physical page size of the paper in width and in length. In such cases, the chart will be printed on multiple pages of paper. Use the PAGESEQ parameter to assist in placing the physical pages in order. Valid values: YES Default: Page location is printed on the upper right hand corner of the chart in the format:
PAGE = xx,yy
where: xx yy Example PAGE = 01,02 indicates that the currrent page is the first page from the left and the second from the top. NO Page location is not printed. Positional page number from the left side of the chart Positional page number from the top of the chart
Example Chart Page Sequence If a chart spans three pages in length and two pages in width, combine the sequentially printed pages 1, 2, 3, 4, 5 and 6 in the following order: 1 2 3 4 5 6
8 36
Example JCLs for Text Format: The following JCL produces a Job Flow report in text format:
//CTMRFLW //DAJOB // // // EXEC DD DD DD DD CTMRFLW DISP=SHR,DSN=LIB(TABLE1) DISP=SHR,DSN=LIB(TABLE2) DISP=SHR,DSN=LIB(TABLE3) DISP=SHR,DSN=LIB(TABLE4) . . .
List of scheduling tables to be included in Job Flow report

. . . //DAFLWPRM DD GROUP UNITED *
The following sample JCLs produce a Job Flow report in chart (as well as text) format. Example 1
//CTMRFLW //DAJOB // // // CTMRFLW DISP=SHR,DSN=LIB(TABLE1) DISP=SHR,DSN=LIB(TABLE2) DISP=SHR,DSN=LIB(TABLE3) DISP=SHR,DSN=LIB(TABLE4) . . . . . //DAFLWPRM DD * CHART YES GROUP UNITED PRINTER LASER FONT 1 PAGESIZE 80 LINESIZE 160 // EXEC DD DD DD DD
Example 2
//CTMRFLW EXEC CTMRFLW //ALLTBL DD DISP=SHR,DSN=LIB //DAFLWPRM DD * JOBSDD ALLTBL CHART YES GROUP UNITED PRINTER LASER FONT 1 PAGESIZE 80 LINESIZE 160 //
8 37
Sample Output Job Flow Report in Text Format Below is a sample Job Flow report in text format. A description of the report fields follows:
PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD. JOBS FLOW REPORT - BY GROUP =========================== DAILY-PROD-YH GROUP
LVL MEMBER DEPEND ON DESCRIPTION TYP CALENDR CMP,DAYS IN WEEK/MONTH GROUP DEPENDENT MANUAL COND TAPE --------------------------------------------------------------------------------------+--------------------------------------------1 PRODYJCL CREATE INPUT FILES # 2 M BANKDAYS | YH-INPUT-FILE-2-OK 0001 FROM 1700 UNTIL 0645 | 1 PRODYHC2 CREATE INPUT FILE # 2 M BANKDAYS | YH-INPUT-FILE-2-OK 0001 1 PROJYFOT BEGIN OF EVENING PROCESS M BANKDAYS | YH-START-EVENING-RUN 1 PROLYPAR NIGHT INPUT COLLECTION # 1 M STOCKDAY | YH-NIGHT-INPUT-1-OK 0001 FROM 2300 UNTIL | 1 PROLYPAG NIGHT INPUT COLLECTION # 2 M DAYSOFF | YH-NIGHT-INPUT-2-OK 0001 FROM 2200 UNTIL | 2 PRODYHTK PRODYJCL PROCESS INPUT DATA FOR M BANKDAYS | PRODYHST FROM 1000 UNTIL 1400 | 2 PRODYBCK PRODYHC2 PROCESS INPUT DATA FOR M BANKDAYS | PRODYIDK | 2 PROJYMRG PROJYFOT EVENING UPDATE PROCEDURE M BANKDAYS | 2 PROLYKLT PROLYPAR MERGE OF INPUT FILES M BANKDAYS | 0002 PROLYPAG | 3 PRODYIDK PRODYBCK UPDATE # 1 M BANLDAYS | 3 PROJYMTI PROJYMRG VERIFICATION PROCESS OF M BANKDAYS | EVENING UPDATE | 3 PROJYHO1 PROJYMRG SPECIAL CALCULATIONS FOR M BANKDAYS | ACCOUNTING DEPARTMENT | 3 PROJYDPY PROJYMRG UPDATE OF ON-LINE FILES M BANKDAYS | 3 PROLYUPD PROLYKLT NIGHT UPDATE PROCEDURE M BANKDAYS | 4 PRODYHST PRODYHTK UPDATE # 2 M BANKDAYS | PRODYIDK FROM 1000 UNTIL 1445 | 4 PRODYIZN PRODYIDK REPORTS FOR BRANCH MANAGERS M BANKDAYS | <+>4 PROJYHO2 PROJYHO1 REPORTS FOR ACCONTING M-BANKDAYS | DEPARTMENT | 4 PROJYDTK PROJYDPY REPORTS OF ON-LINE FILES W BANKDAYS >1 | 4 PROJYDLI PROJYDPY CREATE DUAL ON-LINE FILE W BANKDAYS >1<+> | 4 PROLYMIZ PROLYUPD NIGHT UPDATE PROCEDURE - NEW M BANKDAYS | UPDATE | 5 PRODYBTL PRODYHST REPORTS FOR BRANCHES M BANKDAYS | FROM 1000 UNTIL 1445 | 5 PRODYEND PRODYIZN REPORTS FOR MAIN OFFICE M BANKDAYS | 5 PROYH11 PROJYDTK YH APPLICATION UPDATE W BANKDAYS >1 | PROJYDLI | 5 PROLYBCK PROLYMIZ BACKUP MAIN FILE M BANKDAYS | 0001 5 PROLYFMZ PROLYMIZ REPORTS FOR MAIN OFFICE M BANKDAYS L01 | 5 PROLYBME PROLYMIZ CREATE EXTERNAL TAPE M BANKDAYS L01 | 0001 5 PROLYDM1 PROLYMIZ ARCHIVE YH APPLICATION DATA M BANKDAYS >01 | 0001 SET #1 | 6 PROJYFIN PROJYDPY CLEAN-UP FOR YH APPLICATION M BANKDAYS | PROYH11 | 6 PROLYDOC PROLYBCK BACKUP FILES STATUS REPORTS M BANKDAYS | 6 PROLYDEL PROLYFMZ DELETE TEMPORARY "REPORT" M BANKDAYS L01 | FILES | 6 PROLYDM2 PROLYDM1 ARCHIVE YH APPLICATION DATA M BANKDAYS >01 | 0001 SETS #2 | 7 PROJYBNK PROJYFIN VERIFICATION OF BRANCH M BANKDAYS | BALANCES | 8 PROJEND PROJYBNK FINAL YH APPLICATION M BANKDAYS L01 | PROCEDURE |
8 38
Fields of the Job Flow Report in Text format

The following information is presented for each job in the Job Flow report. LVL Submission level of the job in the group, e.g., 1 first job in the group, 2 a job which depends on one (or more) job(s) in Level 1, etc. The member name (from parameter MEMNAME). The names of the members (jobs) in the group which are prerequisites for execution of the job. Short description of the job optionally supplied in the job scheduling definition. Schedule type. Possible values: M W D C F CALENDR scheduling data By DAYS, MONTH and/or DCAL parameters. By WDAYS, MONTH and/or WCAL parameters. By the DATES parameter. By PDS and MINIMUM parameters. Confirmation by CONFCAL calendar.
MEMBER DEPEND ON DESCRIPTION TYP

2
Name of the calendar, if scheduled by a calendar. The days in the month, or the days of the week, or specific dates, or the name of the library to be checked for free space. If a time limit is specified for the job, it will appear as well. Prerequisite condition which is added (created) by a job belonging to another group. Prerequisite conditions which should be added manually (i.e., conditions which are not added automatically by any job analyzed in the job flow). Quantity required for a Quantitative resource whose name starts with TAPE.
GROUP DEPENDENT MANUAL COND
TAPE
Job flows which are cyclic can be defined to CONTROL-M. Since it is impossible to determine which job in a cycle will run first, the Job Flow report program makes an arbitrary decision where to break the cycle. The job selected is marked by an asterisk (*) to the left of the member name, and a warning message is issued.
M and W schedule types can be preceded by an AND sign (&) or an OR sign (|), indicating AND/OR logic.
8 39
Sample Job Flow Report Output in Graphic Format
8 40
Sample Prerequisite Condition Cross Reference List

PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD. CROSS REFERENCE LIST - PREREQUISITE CONDITIONS ==============================================
CONDITION ODATE TYPE OPT GROUP NAME MEMBER ---------------------------------------------------------------------------------------+-----PROJ-FIN-MAY-GO ODAT IN DAILY-PROD-YH PROJYFIN PROJ-FIN-MAY-GO ODAT OUT + DAILY-PROD-YH PROYH11 PRCH-BCK-END ODAT IN DAILY-PROD-YH PRODYIDK PRCH-BCK-END ODAT OUT + DAILY-PROD-YH PRODYBCK PRCH-BTL-END ODAT OUT + DAILY-PROD-YH PRODYBTL PRCH-END-END ODAT OUT + DAILY-PROD-YH PRODYEND PRCH-HTK-END ODAT IN DAILY-PROD-YH PRODYHST PRCH-HTK-END ODAT OUT + DAILY-PROD-YH PRODYHTK PRCH-HTK-END ODAT CODES + DAILY-PROD-YH PRODYJCL PRCH-IDK-END ODAT IN DAILY-PROD-YH PRODYHST PRCH-IDK-END ODAT IN DAILY-PROD-YH PRODYIZN PRCH-IDK-END ODAT OUT + DAILY-PROD-YH PRODYIDK PRCH-IZN-END ODAT IN DAILY-PROD-YH PRODYEND PRCH-IZN-END ODAT OUT + DAILY-PROD-YH PRODYIZN PRCH-JCL-END ODAT IN DAILY-PROD-YH PRODYHTK PRCH-JCL-END ODAT OUT + DAILY-PROD-YH PRODYJCL JOBS-DHT-END ODAT IN DAILY-PROD-YH PRODYBTL JOBS-DHT-END ODAT OUT + DAILY-PROD-YH PRODYHST JOBS-KLT-END ODAT IN DAILY-PROD-YH PRODYBCK JOBS-KLT-END ODAT OUT + DAILY-PROD-YH PRODYHC2 PROJ-BNK-END ODAT IN DAILY-PROD-YH PROJEND PROJ-BNK-END ODAT OUT + DAILY-PROD-YH PROJYBNK PROJ-DLI-END ODAT IN DAILY-PROD-YH PROYH11 PROJ-DLI-END ODAT OUT + DAILY-PROD-YH PROJYDLI PROJ-DPY-END ODAT IN DAILY-PROD-YH PROJYDTK PROJ-DPY-END ODAT IN DAILY-PROD-YH PROJYDLI PROJ-DPY-END ODAT IN DAILY-PROD-YH PROJYFIN PROJ-DPY-END ODAT OUT + DAILY-PROD-YH PROJYDPY PROJ-DTK-END ODAT IN DAILY-PROD-YH PROYH11 PROJ-DTK-END ODAT OUT + DAILY-PROD-YH PROJYDTK PROJ-FIN-END ODAT IN DAILY-PROD-YH PROJYBNK PROJ-FIN-END ODAT OUT + DAILY-PROD-YH PROJYFIN PROJ-FOT-END ODAT IN DAILY-PROD-YH PROJYMRG PROJ-FOT-END ODAT OUT + DAILY-PROD-YH PROJYFOT PROJ-HO1-END ODAT IN DAILY-PROD-YH PROJYHO2 PROJ-HO1-END ODAT OUT + DAILY-PROD-YH PROJYHO1 PROJ-HO2-END ODAT OUT + DAILY-PROD-YH PROJYHO2 PROJ-MRG-END ODAT IN DAILY-PROD-YH PROJYMTI PROJ-MRG-END ODAT IN DAILY-PROD-YH PROJYHO1 PROJ-MRG-END ODAT IN DAILY-PROD-YH PROJYDPY PROJ-MRG-END ODAT OUT + DAILY-PROD-YH PROJYMRG PROJ-MTI-END ODAT OUT + DAILY-PROD-YH PROJYMTI PROJ-RCV-UEGP ODAT CODES + DAILY-PROD-YH PROJYFOT PRDL-BCK-END ODAT IN DAILY-PROD-YH PROLYDOC PRDL-BCK-END ODAT OUT + DAILY-PROD-YH PROLYBCK PRDL-BME-END ODAT OUT + DAILY-PROD-YH PROLYBME PRDL-DEL-END ODAT OUT + DAILY-PROD-YH PROLYDEL PRDL-DMS-END ODAT IN DAILY-PROD-YH PROLYDM2 PRDL-DMS-END ODAT OUT + DAILY-PROD-YH PROLYDM1 PRDL-DM2-END ODAT OUT + DAILY-PROD-YH PROLYDM2 PRDL-DOC-END ODAT OUT + DAILY-PROD-YH PROLYDOC PRDL-FMZ-END ODAT IN DAILY-PROD-YH PROLYDEL PRDL-FMZ-END ODAT OUT + DAILY-PROD-YH PROLYFMZ
8 41
Sample Control Resources Cross Reference List

PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD. CROSS REFERENCE LIST - CONTROL RESOURCES ========================================
RESOURCE NAME S/E GROUP NAME MEMBER ---------------------------------------------------------------------------------------+--------HN.KDAM.INPUT S DAILY-PROD-YH PRODYHC2 PRAD-ADAKOV-M203UTIL E DAILY-PROD-YH PRODYBCK PRAD-ADAKOV-M206UTIL E DAILY-PROD-YH PROLYBCK PRAD-MPM203-IN-USE S DAILY-PROD-YH PRODYHST PRAD-MPM203-IN-USE S DAILY-PROD-YH PRODYJCL PRAD-MPM203-IN-USE S DAILY-PROD-YH PRODYBTL PRAD-MPM203-IN-USE S DAILY-PROD-YH PRODYHC2 PRAD-MPM203-IN-USE S DAILY-PROD-YH PRODYBCK PRAD-MPM203-IN-USE S DAILY-PROD-YH PRODYIDK PRAD-MPM203-IN-USE S DAILY-PROD-YH PRODYIZN PRAD-MPM206-IN-USE S DAILY-PROD-YH PRODYHC2 PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJYFOT PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJYMTI PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJYHO1 PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJYHO2 PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJYDPY PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJYDTK PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJYDLI PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJYFIN PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJYBNK PRAD-MPM206-IN-USE S DAILY-PROD-YH PROJEND PRAD-MPM206-IN-USE S DAILY-PROD-YH PROLYKLT PRAD-MPM206-IN-USE S DAILY-PROD-YH PROLYUPD PRAD-MPM206-IN-USE S DAILY-PROD-YH PROLYMIZ PRAD-MPM206-IN-USE S DAILY-PROD-YH PROLYBCK PRAD-MPM206-IN-USE S DAILY-PROD-YH PROLYDOC PRAD-MPM206-IN-USE S DAILY-PROD-YH PROLYFMZ PRAD-MPM206-IN-USE S DAILY-PROD-YH PROLYDEL PRAD-MPM206-IN-USE S DAILY-PROD-YH PROLYDM2 PRAD-MPM206-IN-USE S DAILY-PROD-YH PROLYDM1 PRAD-M206F093-IN-USE S DAILY-PROD-YH PROJYDPY PRAD-M206F093-IN-USE S DAILY-PROD-YH PROJYDTK PRAD-M206F093-IN-USE S DAILY-PROD-YH PROJYDLI PRAD-M206F093-IN-USE S DAILY-PROD-YH PROLYKLT PRAD-M206F093-IN-USE S DAILY-PROD-YH PROLYUPD PRAD-M206F093-IN-USE S DAILY-PROD-YH PROLYDOC PRAD-M206F093-IN-USE S DAILY-PROD-YH PROLYFMZ PRPR-ADAKOV-M203F008 S DAILY-PROD-YH PRODYHC2 PRPR-ADAKOV-M203F021 E DAILY-PROD-YH PRODYHC2 PRPR-ADAKOV-M203F021 E DAILY-PROD-YH PRODYBCK PRPR-ADAKOV-M203F021 E DAILY-PROD-YH PRODYIDK PRPR-ADAKOV-M203F022 E DAILY-PROD-YH PRODYHC2 PRPR-ADAKOV-M203F022 E DAILY-PROD-YH PRODYBCK PRPR-ADAKOV-M203F022 E DAILY-PROD-YH PRODYIDK PRPR-ADAKOV-M203F023 E DAILY-PROD-YH PRODYHC2 PRPR-ADAKOV-M203F023 E DAILY-PROD-YH PRODYBCK PRPR-ADAKOV-M203F023 E DAILY-PROD-YH PRODYIDK PRPR-ADAKOV-M203F024 E DAILY-PROD-YH PRODYHC2 PRPR-ADAKOV-M203F024 E DAILY-PROD-YH PRODYBCK PRPR-ADAKOV-M203F024 E DAILY-PROD-YH PRODYIDK PRPR-ADAKOV-M203F024 S DAILY-PROD-YH PRODYHST PRPR-ADAKOV-M203F025 E DAILY-PROD-YH PRODYBCK PRPR-ADAKOV-M203F025 E DAILY-PROD-YH PRODYIDK
8 42
Sample Quantitative Resources Cross Reference List

PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD. CROSS REFERENCE LIST - QUANTITATIVE RESOURCES =============================================
RESOURCE NAME NUMBER GROUP NAME MEMBER -------------------------------------------------------------------------------------+----------INIT-E 0001 DAILY-PROD-YH PRODYEND INIT-E 0001 DAILY-PROD-YH PROLYPAR INIT-E 0001 DAILY-PROD-YH PROLYPAG INIT-U 0001 DAILY-PROD-YH PRODYHTK INIT-U 0001 DAILY-PROD-YH PROJYFOT INIT-U 0001 DAILY-PROD-YH PROJYHO1 INIT-U 0001 DAILY-PROD-YH PROJYHO2 INIT-U 0001 DAILY-PROD-YH PROJYDTK INIT-U 0001 DAILY-PROD-YH PROJYFIN INIT-W 0001 DAILY-PROD-YH PRODYIZN INIT-W 0001 DAILY-PROD-YH PROJYMRG INIT-W 0001 DAILY-PROD-YH PROJYMTI INIT-W 0001 DAILY-PROD-YH PROJYDPY INIT-W 0001 DAILY-PROD-YH PROJYDLI INIT-W 0001 DAILY-PROD-YH PROJYBNK INIT-W 0001 DAILY-PROD-YH PROJEND INIT-W 0001 DAILY-PROD-YH PROLYKLT INIT-W 0001 DAILY-PROD-YH PROLYUPD INIT-W 0001 DAILY-PROD-YH PROLYMIZ INIT-W 0001 DAILY-PROD-YH PROLYBCK INIT-W 0001 DAILY-PROD-YH PROLYFMZ INIT-W 0001 DAILY-PROD-YH PROLYDEL MPM203 0001 DAILY-PROD-YH PRODYHST MPM203 0001 DAILY-PROD-YH PRODYJCL MPM203 0001 DAILY-PROD-YH PRODYBTL MPM203 0001 DAILY-PROD-YH PRODYHC2 MPM203 0001 DAILY-PROD-YH PRODYBCK MPM203 0001 DAILY-PROD-YH PRODYIDK MPM203 0001 DAILY-PROD-YH PRODYIZN MPM206 0001 DAILY-PROD-YH PRODYHC2 MPM206 0001 DAILY-PROD-YH PROJYFOT MPM206 0001 DAILY-PROD-YH PROJYMTI MPM206 0001 DAILY-PROD-YH PROJYHO1 MPM206 0001 DAILY-PROD-YH PROJYHO2 MPM206 0001 DAILY-PROD-YH PROJYDPY MPM206 0001 DAILY-PROD-YH PROJYDTK MPM206 0001 DAILY-PROD-YH PROJYDLI MPM206 0001 DAILY-PROD-YH PROJYFIN MPM206 0001 DAILY-PROD-YH PROJYBNK MPM206 0001 DAILY-PROD-YH PROJEND MPM206 0001 DAILY-PROD-YH PROLYKLT MPM206 0001 DAILY-PROD-YH PROLYUPD MPM206 0001 DAILY-PROD-YH PROLYMIZ REEL 0001 DAILY-PROD-YH PROLYKLT REEL 0001 DAILY-PROD-YH PROLYFMZ TAPE 0001 DAILY-PROD-YH PRODYJCL TAPE 0001 DAILY-PROD-YH PRODYHC2 TAPE 0001 DAILY-PROD-YH PROLYPAR TAPE 0001 DAILY-PROD-YH PROLYPAG TAPE 0001 DAILY-PROD-YH PROLYBCK TAPE 0001 DAILY-PROD-YH PROLYBME
8 43
KSL and the Reporting Facility: Special Purpose Reports CTMRAFL: Active Jobs File Job Flow Report
CTMRAFL: Active Jobs File Job Flow Report

CTMRAFL provides job flow information about the jobs in the Active Jobs file. Information is sorted by group and presented in execution order by group. In most respects, CTMRAFL and CTMRFLW are identical:
Both CTMRAFL and CTMRFLW provide a Job Flow report and a Cross Reference. The two reports use virtually the same parameters. The reports have almost identical report output (in text format).
The basic differences between report CTMRAFL and CTMRFLW are:
Report CTMRFLW provides information about jobs in scheduling tables, report CTMRAFL provides information about jobs in the Active Jobs file. Report CTMRAFL does not accept SYSIN report parameters. Report CTMRAFL provides the Job Flow report in text format only; therefore the graphic format parameters of report CTMRFLW do not apply to report CTMRAFL. In CTMRAFL, original scheduling date (ODATE) information (from the Active Jobs file) is provided in the report output. In CTMRFLW, other scheduling information extracted from the job scheduling definitions (TYP, CALENDR, scheduling data) is provided.
When utilizing the sample JCL provided for CTMRFLW, be sure to modify the EXEC statement. For CTMRAFL, the EXEC statement should read:
//RAFL EXEC CTMRAFL
(instead of: //CTMRFLW EXEC CTMRFLW).
8 44
KSL and the Reporting Facility: Special Purpose Reports CTMRPLN: Job Plan Report
CTMRPLN: Job Plan Report

This report provides a list of all the jobs which are planned for a specified range of dates. The report is available in the following basic formats:
Type 0 Report
Displays a day by day list of planned jobs (in the specified date range). The jobs displayed for each day can be sorted according to member-name or according to group. For each member in the list, the member-name, group and description are displayed. Displays a month by month table of planned jobs (in the specified date range), indicating days on which the jobs are planned for execution. This format is useful for drawing the entire months plan. This report is identical to the Type 1 report, except that it also displays the job description for each job. Note Type 2 reports require a laser printer or a wide printer.
Type 1 Report
Type 2 Report
Report parameters are supplied via DD statement SYSIN (or DAPLNPRM). Note It is possible to change the default number of lines per page (60) by using PARM=LINECNT=xxx in the EXEC statement of the job.
Parameters REPSTART yymmdd REPEND yymmdd REPTYPE n JOBSDD ddname Start date of report. Mandatory. End date of end of report. Mandatory. Type of report (0, 1 or 2). Default: 0. DDname of the library. If specified, all members of the library are processed by the utility. This makes it unnecessary to specify a concatenation of DD statements (one statement for each table) in the JCL.
SORTBY {MEMNAME|GROUP} Sort option. Default: MEMNAME. This parameter is relevant only for REPTYPE 0. IGNORE CALENDAR calname Ignore jobs which reference calendar calname. This statement is optional. A maximum of eight IGNORE statements can be supplied. This statement excludes a job from the report if its MONTHS parameter is filled with Y values and either of the following criteria is satisfied:
WDAYS is defined as ALL (or blank) and its associated WCAL is specified in the IGNORE statement. DAYS is defined as ALL (or blank) and its associated DCAL is specified in the IGNORE statement.
8 45
Example of JCL
//PLAN //DAPLNJOB // // EXEC DD DD DD CTMRPLN DISP=SHR,DSN=scheduling-library(table1) DISP=SHR,DSN=scheduling-library(table2) DISP=SHR,DSN=scheduling-library(table3) . . . *
//DAPLNPRM DD
Sample Input Parameters

REPSTART REPEND REPTYPE SORTBY 980601 980630 0 MEMNAME
8 46
REPSTART REPEND REPTYPE SORTBY
980601 980630 0 MEMNAME
PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD. JOBS PLANNED FOR MONDAY 06/01/98
JOBS PLAN REPORT ================
FROM 980601 UNTIL 980630
MEMNAME GROUP DESCRIPTION ------------------------------------------------------------------------------------------- BRCCIND BR-IVP-CC PREPARE SPECIAL UPDATE INFO BRCC0001 BR-IVP-CC PERFORM QUALITY CHECKING ON INPUT DATA PROD1-A BRCC0002 BR-IVP-CC COLLECT INPUT DATA SETS FOR PROD1-B EXECUTION BRCC0003 BR-IVP-CC FINAL INPUT DATA SETS VARIFICATION BRIVPCC BR-IVP-CC COLLECT INPUT DATA SETS FOR PROD1-A EXECUTION BRIVPCCE BR-IVP-CC UPDATE JOB OF EXTRA BALANCING BRREP001 BR-IVP-CC PRODUCE SUM REPORTS BRREP002 BR-IVP-CC PRODUCE SPECIAL REPORTS BRUPDT02 BR-IVP-CC UPDATE JOB CRCCEND BR-IVP-CC NOTIFY END OF PRODUCTION PROCESS MTFIT01 MT-PRODUCTION MT INPUT RUN # 1 MTFIT02 MT-PRODUCTION MT INPUT RUN # 2 MTFIT03 MT-PRODUCTION MT INPUT RUN # 3 MTFIT04 MT-PRODUCTION MT INPUT RUN # 4 MTFIT05 MT-PRODUCTION MT INPUT RUN # 5 MTFRTH01 MT-PRODUCTION MT MERGE INPUT FILES MTRUN001 MT-PRODUCTION MT UPDATE - FIRST RUN MTRUN002 MT-PRODUCTION MT UPDATE - SECOND RUN MTTRD02 MT-PRODUCTION MT REPORTS MTUPDT MT-PRODUCTION MT UPDATE TO ON-LINE FILES PRDDRPT1 PROD-KPL REPORTS AFTER PRODUCTION UPDATES FOR PROD-KPL PRDDRPT2 PROD-KPL REPORTS AFTER PRODUCTION EXECUTION FOR PROD KPL PRDKPLW1 PROD-KPL WEEKLY PRODUCTION INPUT FILES FROM PROD-KPL #1 PRDKPLW2 PROD-KPL WEEKLY PRODUCTION UPDATE OF PROD-KPL #2 PRDKPLW3 PROD-KPL WEEKLY PRODUCTION UPDATE OF PROD-KPL #3 PRDKPLW4 PROD-KPL WEEKLY EXECUTIONS AFTER DAILY FROM PROD-KPL PRDKPL01 PROD-KPL DAILY PRODUCTION - START OF APPL-PROD-KPL PRDKPL02 PROD-KPL DAILY PRODUCTION - COLLECT TAPE FILES OF PROD-KPL PRDTT001 PR-PRODUCTION TAPE COLLECTION FOR PR PRODUCTION PRERRPRT PR-PRODUCTION ERROR REPORTS FOR APPLICATION PR PRFKL01 PR-PRODUCTION STATISTICS REPORTS FOR PR APPLICATION PRUPDOLV PR-PRODUCTION UPDATE ON-LINE REPORTS
8 47
REPSTART REPEND REPTYPE SORTBY
980601 980630 1 MEMNAME
PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD. JOBS PLANNED FOR 06 1998
JOBS PLAN REPORT ================
FROM 980601 UNTIL 980630
BRCCIND BRCC0001 BRCC0002 BRCC0003 BRIVPCC MTFIR01 MTFIT01 MTFIT02 MTFIT03 MTFIT04 MTFIT05 MTFRTH01 MTRUN001 MTRUN002 MTSCN01 MTTRD01 MTTRD02 MTUPDT PRDDRPT1 PRDDRPT2 PRDKPLW1 PRDKPLW2 PRDKPLW3 PRDKPLW4 PRDKPL01 PRDKPL02 PRDTT001 PRDTT01 PRERRPRT PRFKL01 PRPRTH01 PRRPT01 PRRPT02 PRRPT03 PRRPT04 PRRPT05 PRTRD01 PRTRD04 PRUPDOLV
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO TU WE TH FR SA SU MO<+> TUE +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | | * | * | * | * | * | | | * | * | * | * | * | | | * | * | * | * | * | | | * | * | * | * | * | | | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * | * | * | * | * | | | * | * | * | * | * | | | * | * | * | * | * | | | * | * | * | * | * | | | * | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | * | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | | * | * | * | | | | | | | | | | | | | | | | | | | | | | | | | | | * | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | * | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | * | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * | * | * | * | * | | * | * |
8 48
KSL and the Reporting Facility: Special Purpose Reports CTMRPFL: Job Plan/Flow Report
CTMRPFL: Job Plan/Flow Report

CTMRPFL provides job flow information for jobs in a scheduling table which are scheduled in a specified date range. CTMRPFL can best be understood in context of the features (and limitations) of the following reports, described earlier in this section: CTMRPLN CTMRFLW Produces a list of all jobs which are planned for a specified date range. However, this report does not contain job flow information. Produces a job flow report for jobs in a scheduling table. However, this report includes jobs regardless of whether or not they are scheduled in a particular date range (i.e., it does not exclude unscheduled jobs). Produces a job flow report for all jobs currently in the Active Jobs file.
CTMRAFL
CTMRPFL uses the same parameters as, and combines the features of, CTMRPLN and CTMRFLW, as follows:
CTMRPLN parameters are used to generate a list of jobs scheduled in a specified date range. This list is then used, in combination with the CTMRFLW parameters, to generate a job flow report for those jobs in the specified scheduling table which are included in the list.
CTMRPFL can generate the same reports (Job Flow, Cross Reference) in the same formats (text, chart) as CTMRFLW. CTMRPFL also generates a report identical to the CTMRPLN report. (This report output can be suppressed. However, the list required as input for the job flow report is generated.) CTMRPFL utilizes two sets of parameters:
The first set of parameters, input via DD statement SYSIN1, is identical to those of CTMRPLN. However, only REPTYPE values 1 or 2 should be used. (In CTMRPLN, REPTYPE 0 can also be specified.) The second set of parameters, input via DD statement SYSIN2 is identical to those of CTMRFLW. For detailed information on the parameters used by CTMRPFL, see the descriptions of reports CTMRPLN and CTMRFLW.
Note
8 49
KSL and the Reporting Facility: Special Purpose Reports CTMRPFL: Job Plan/Flow Report
Example JCL
//M71PLFL5 //PLFL //DAPLNJOB // JOB ,M71,CLASS=A EXEC CTMRPFL DD DISP=SHR,DSN=scheduling-library(table1) DD DISP=SHR,DSN=scheduling-library(table2) . . . //DACAL DD DISP=SHR,DSN=calendar-library //SYSIN1 DD * REPSTART 980606 REPEND 980606 REPTYPE 2 //SYSIN2 DD * GROUP UNITED CHART YES PAGESEQ YES PAGESIZE 60 LINESIZE 160 PRINTER IMPACT //
8 50
KSL and the Reporting Facility: Special Purpose Reports CTMRNSC: Night Schedule Report
CTMRNSC: Night Schedule Report

This report provides a summary of each job which has executed within the specified time range, including its start-time, end-time, elapsed time, CPU time and system-ID. The report can be sorted by combinations of group name, job start-time, and job end-time. Report parameters are supplied via DD statement SYSIN (or DANSCPRM). Columns 73-80 of each card are ignored. Note It is possible to change the default number of lines per page (60) by using PARM=LINECNT=xxx in the EXEC statement of the job.
Parameters REPSTART yymmddhhnn REPEND yymmddhhnn Date and time of start of night schedule report information. Date and time of end of night schedule report information. Sort by end-time/start-time/group Sort by end-time/group/start-time Sort by group/end-time/start-time Sort by group/start-time/end-time Sort by start-time/group/end-time Sort by start-time/end-time/group
ENDTIME STARTTIME ENDTIME GROUP GROUP ENDTIME SORTBY GROUP STARTTIME STARTTIME GROUP STARTTIME ENDTIME
INCLUDE GROUPNAME groupname INCLUDE JOBNAME jobname
Group name or mask to be included (to a maximum of 10). Job name or mask to be included (to a maximum of 10).
Example of JCL
//RNSC EXEC CTMRNSC //DALOGIN DD ... A log file.
The input of the report is a file in the format of the IOA Log file. It can be the IOA Log (for a report of last nights schedule) or the Simulation log (for a report of a forecasted night schedule).
8 51
KSL and the Reporting Facility: Special Purpose Reports CTMRNSC: Night Schedule Report
Example of Instructions
REPSTART 9806061600 REPEND 9806062300 SORTBY STARTTIME ENDTIME
15.08.00 NSC391I NIGHT SCHEDULE REPORT STARTED REPSTART 9806062000 REPEND 9806062200 SORTBY STARTTIME ENDTIME 15.08.07 NSC393I NIGHT SCHEDULE REPORT ENDED PRODUCED BY CONTROL-M (5.1.4) NIGHT SCHEDULE REPORT FROM 98/06/06-20:00 NEW DIMENSION SOFTWARE, LTD. ===================== UNTIL 98/06/06-22:00 MEMBER JOBNAME JOBID STARTED ENDED ELAPSED GROUP-NAME CPUTIME SYSID BRIVPCC BRIVPCC 03370 06/06/98-20:00 06/06/98-20:35 35:12 BR-PRODUCTION 2:16.02 SYS1 BRCC0001 BRCC0001 03381 06/06/98-20:01 06/06/98-20:46 46:27 BR-PRODUCTION 4:02.03 SYS1 BRCC0002 BRCC0002 03409 06/06/98-20:01 06/06/98-20:19 18:41 BR-PRODUCTION 1:00.05 SYS2 BRCC0003 BRCC0003 03414 06/06/98-20:06 06/06/98-20:16 10:02 BR-PRODUCTION 0:42.43 SYS1 PRUPDT02 PRUPDT02 03483 06/06/98-20:08 06/06/98-20:23 15:36 PR-APPLICATION 1:15.28 SYS2 CRCCEND CRCCEND 03484 06/06/98-20:13 06/06/98-20:23 20:01 CR-GROUP 2:19.31 SYS2 INTR0001 INTR0001 03577 06/06/98-20:13 06/06/98-21:01 48:19 INTER-APPLICATION 5:16.06 SYS2 INTR0002 INTR0002 03578 06/06/98-20:13 06/06/98-20:19 6:58 INTER-APPLICATION 0:26.52 SYS2 BRCCIND BRCCIND 03601 06/06/98-20:19 06/06/98-20:31 12:17 BR-PRODUCTION 0:21.26 SYS2 BRUPDT02 BRUPDT02 03618 06/06/98-20:44 06/06/98-21:20 36:10 BR-PRODUCTION 3:47.20 SYS1 BRREP001 BRREP001 03617 06/06/98-20:45 06/06/98-21:02 17:34 BR-PRODUCTION 2:42.51 SYS1 BRREP002 BRREP002 03625 06/06/98-20:45 06/06/98-20:57 12:03 BR-PRODUCTION 1:37.24 SYS2 PRDKPL01 PRDKPL01 03627 06/06/98-20:52 06/06/98-21:25 33:48 KPL-PRODUCTION 4:45.25 SYS1 PRDKPL02 PRDKPL02 03628 06/06/98-21:11 06/06/98-21:27 16:51 KPL-PRODUCTION 2:59.37 SYS2 CRSREF PRCRREF 03638 06/06/98-21:11 06/06/98-21:36 25:00 USER-CROSS REF 6:14.02 SYS2 BRIVPCCE BRIVPCCE 03869 06/06/98-21:12 06/06/98-21:57 45:14 BR-PRODUCTION 2:01.54 SYS1 INTR0003 INTR0003 03917 06/06/98-21:15 06/06/98-21:59 44:43 INTER-APPLICATION 1:39.49 SYS2 INTR0004 INTR0004 03923 09/09/98-21:15 06/06/98-21:16 1:36 INTER-APPLICATION 0:05.86 SYS2 PRYHINP PRYHINP 03929 09/09/98-21:24 06/06/98-21:40 16:35 YH-DAILY-PRODUCTION 2:05.83 SYS2
SORTBY
STARTTIME ENDTIME
8 52
KSL and the Reporting Facility: Special Purpose Reports CTMROGR: Overnight Execution Graph
CTMROGR: Overnight Execution Graph

The Overnight Execution Graph provides a clear and easy way to display job workloads for the purposes of planning or adjustment. Group execution times are graphically presented. The graph can be used to display both previous execution times, and anticipated future execution times. The report can be used to point out problems in job execution flow (e.g., certain jobs not executing at certain times, too many jobs executing at a given time, etc.), or simply to provide general information about job flow and work load. For example:
By running the report in the morning, the Operations Manager can get a picture of the production workload from the night before, and assess the need for adjustments to the job flow. On the 15th of the month, the report can simulate end-of-month processing, to facilitate planning.
The report is designed as follows: For specified intervals within a time range, the graph indicates whether or not any job executions for the group occurred during the interval. An asterisk (*) indicates job execution for the group during the time interval. A blank space indicates no job execution for the group during the interval. The report can be requested in either of two presentation modes:
Single mode Each group is represented on one line. For each group, no more than one * can appear in each time interval. An * indicates that at least one job in the group was executing during that time interval.
Parallel mode The number of lines representing each group varies. For each group, the number of *s within a time interval varies according to the number of jobs in the group executing in that interval. Multiple *s for the same group/time interval appear on successive lines.
Note
Multiple *s for a time interval (in the same or different group) do not necessarily indicate simultaneous execution. They can indicate separate execution times within the same interval.
Input for the report is extracted from either the IOA Log file (for actual execution results) or the Simulation Log (for forecasted results). Report parameters are supplied via DD statement SYSIN (or DAOGRPRM). Columns 73-80 of each card are ignored.
8 53
Parameters Note It is possible to change the default number of lines per page (60) by specifying PARM=LINECNT=xxx in the EXEC statement of the job. Earliest start date and time for jobs included in the report. Latest end date and time for jobs included in the report. Time interval, in minutes, for which job execution in a group is indicated. Each interval is represented by one column of the report. Valid values: 01 60.
REPSTART yymmddhhmm REPEND yymmddhhmm INTERVAL nn
Note
The total number of intervals (columns) must not exceed 210 and the start and end dates must not be more than nine days apart, or an error message is displayed and the report is not run. Presentation mode of the report. Single Parallel Represent all job executions group/interval by a single *. for a
MODE {SINGLE|PARALLEL}
Represent multiple job executions for a group/ interval separately, by multiple *s.
GROUP {groupname|ALL}
Groups to be included in the report. Up to 10 individual group names can be specified, or the value ALL can be specified to display all groups.
Example of JCL
//CTMROGR //DALOGIN //DAOGRPRM EXEC CTMROGR DD . . . A log file DD * REPSTART 9806062000 REPEND 9806072300 INTERVAL 05 MODE PARALLEL GROUP ALL
//
8 54
PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD. MODE DISPLAYED: SINGLE
OVERNIGHT EXECUTION GRAPH =========================
FROM 98/06/06 11:15 UNTIL 98/06/07-10:30 IN 15 MINUTE INTERVALS
START END ELAPSED GROUP NAME TIME TIME TIME <..12..13..14..15..16..17..18..19..20..21..22..23..00..01..02..03..04..05..06..07..08..09..10..> -----------------------------------------<---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|--> BR-COND-UPDATE 13:40 05:34 954 * ** * BR-GENERAL 13:00 07:23 1103 **** * ** * * ************** PR-BATCH-JOBREQ 07:02 07:05 3 * PROD-KPL-ALOC001 19:34 03:47 493 * * PROD-KPL-ALOC002 19:31 03:32 481 * * PROD-KPL-FREE001 19:24 01:02 338 * * PROD-KPL-FREE002 18:23 02:46 503 * * PROD-KPL-FREE003 18:23 00:00 337 * * * PROD-KPL-FREE004 18:23 06:00 697 * * PROD-CONTROLD 12:00 12:02 2 * PR-CICSP-ALOC001 18:33 23:55 322 * * PR-CICSP-ALOC002 18:33 23:55 322 * * PR-CICSP-ALOC003 18:34 23:55 321 * * PR-CICSP-ALOC004 18:34 00:12 338 * * PR-CADACAD3 04:04 04:04 * PR-CADACAD6 04:16 04:16 * PR-CADACMC6 02:11 02:11 * PR-CADAC186 18:30 18:39 9 * PR-CADAOAD3 04:38 04:38 * PR-CADAOAD6 05:36 05:36 * PR-CADAOMC6 02:25 02:25 * PR-JOBDAILY-1 17:00 07:01 841 * * Q-PR-CLOCK 04:00 04:02 2 * Q-PR-CONTM 03:01 08:00 299 * Q-PR-EADA-BACKUP 16:14 06:48 874 *** ************ ****** ** * * ** Q-PR-EADA-CHEKPOINT 07:30 08:07 37 *** Q-PR-GENERAL 16:00 06:51 891 * ** * ****** Q-PR-INITS 14:52 08:10 1038 * ** * * *** *
8 55
PRODUCED BY CONTROL-M 5.1.4 NEW DIMENSION SOFTWARE, LTD. MODE DISPLAYED: PARALLEL
OVERNIGHT EXECUTION GRAPH =========================
FROM 98/06/06 11:15 UNTIL 98/06/07-10:30 IN 15 MINUTE INTERVALS
START END ELAPSED GROUP NAME TIME TIME TIME <..12..13..14..15..16..17..18..19..20..21..22..23..00..01..02..03..04..05..06..07..08..09..10..> ----------------------------------------<---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|--> BR-COND-UPDATE 13:40 05:34 954 * ** * * BR-GENERAL 13:00 07:23 1103 *** * * * * ***** * ****** * * * * * ****** ** * * * * * *** * * *** * * ** * * *** * ** *** * * * * * * * * * * * * * * * * * * * ** * * ** * ** *** ** PR-BATCH-JOBREQ 07:02 07:05 3 * * PROD-KPL-ALOC001 19:34 03:47 493 * * PROD-KPL-ALOC002 19:31 03:32 481 * * PROD-KPL-FREE001 19:24 01:02 338 * * PROD-KPL-FREE002 18:23 02:46 503 * * PROD-KPL-FREE003 18:23 00:00 337 * * * PROD-KPL-FREE004 18:23 06:00 697 * * PROD-CONTROLD 12:00 12:02 2 * * * PR-CICSP-ALOC001 18:33 23:55 322 * * PR-CICSP-ALOC002 18:33 23:55 322 * * PR-CICSP-ALOC003 18:34 23:55 321 * * PR-CICSP-ALOC004 18:34 00:12 338 * * PR-CADACAD3 04:04 04:04 * PR-CADACAD6 04:16 04:16 * PR-CADACMC6 02:11 02:11 * PR-CADAC186 18:30 18:39 9 * * PR-CADAOAD3 04:38 04:38 * PR-CADAOAD6 05:36 05:36 * PR-CADAOMC6 02:25 02:25 * PR-JOBDAILY-1 17:00 07:01 841 * * * Q-PR-CLOCK 04:00 04:02 2 * Q-PR-CONTM 03:01 08:00 299 * * Q-PR-EADA-BACKUP 16:14 06:48 874 *** ************ **** ** * * * * *** ** ** Q-PR-EADA-CHEKPOINT 07:30 08:07 37 * *** Q-PR-GENERAL 16:00 06:51 891 * ** * * **** ***** Q-PR-INITS 14:52 08:10 1038 * ** * * *** * ** * * ** * * * * * *
8 56
KSL and the Reporting Facility: Special Purpose Reports CTMRJDS: Job Dataset Cross Reference Report
CTMRJDS: Job Dataset Cross Reference Report

Report CTMRJDS provides a cross reference, by dataset, of jobs which access the dataset. For the report to be generated, it is first necessary to generate a list of datasets accessed by the job. This list can be generated in either of the following ways:
Use the Job Dataset List utility (IOA Online Utility option R3, described in Section 2 of this manual). Use supplied procedure CTMJDS (described below) to generate the list for one or all of the jobs in a scheduling table.
In either case, the Job Dataset list is generated in the Statistics file.
Procedure CTMJDS Generating the Job Dataset List

Procedure CTMJDS can be used to generate the Job Dataset list in the Statistics file. This list is required by the procedure which generates the Job Dataset Cross Reference report.
The following parameters are supplied to CTMJDS.

//JDSN EXEC CTMJDS //SYSIN DD * SCHEDLIB CTM.PROD.SCHEDULE TABLE N04 JOB @BR14 [{WDATE|ODATE} date] SUBMIT //
SCHEDLIB TABLE JOB WDATE ODATE SUBMIT
Name of the scheduling library. Mandatory. Scheduling table member name. Mandatory. Name of one single job, or asterisk for the whole table. Mandatory. Working date of the job, in 6character date format according to the site standard. Optional. Original scheduling date of the job, in 6character date format according to the site standard. Optional. CONTROL-M attempts to resolve the AutoEdit statements. If successful, the JCL member lines are also written to the file referenced by DD statement DASUBMIT and the member is submitted by the utility for execution. In this case, MVS also checks the JCL. This option can also be used to submit jobs when the CONTROL-M monitor is not active (e.g., if there is a severe technical problem). Mandatory.
Parameters for utility CTMRJDS are submitted in blocks. If multiple blocks are specified, all mandatory parameters must be specified in each block. (WDATE and ODATE are always optional.)
8 57
KSL and the Reporting Facility: Special Purpose Reports CTMRJDS: Job Dataset Cross Reference Report
Procedure CTMRJDS Generating the Dataset Cross Reference Report Once the Job Dataset list has been generated, the Dataset Cross Reference report can be generated by procedure CTMRJDS. The report can be generated in either of the following formats:
Condensed (short) format. Expanded (long) format which provides additional information.
The following parameters should be supplied to procedure CTMRJDS: DSN=dspref Generic dataset prefix. For example: DSN=SYS1. lists all jobs which refer to datasets with a prefix of SYS1. Note Mask characters (* and ?) cannot be specified as part of this prefix.
REPTYPE=SHORT/LONG
Report format. Valid values are: SHORT LONG Lists all jobs that refer to the given dataset. Default. Lists each job on a separate line, along with step name(s), ddname(s), disposition, etc.
Example of JCL
//JDSN EXEC CTMRJDS //SYSIN DD * DSN=C REPTYPE=SHORT
Sample output for the report, in expanded format, is shown below.

DATE: 1998/07/07 DATASET NAME TIME: 14:37 CROSS REFERENCE - DATASET NAME WITH JOBNAME GROUP JOBNAME PROCNAME STEPNAME STEPNUM PAGE 00001 DDNAME VOLSER DISP
----------------------------------------------------------------------------------------------------------------------------------CTM.PROD.SCHEDULE SYS-MAINT SYS-MAINT SYS-MAINT ACCT-GROUP-B ( Y03.PROD005.JCL SYS-MAINT SYS-MAINT SYS-MAINT ACCT-GROUP-B ( N29P01 N29P N29Q00 S33Z001 FIRST FIRST LAST STEP1 STEP001 MERGE PRINT COUNT 2 2 2 2 SYSUT1 SYSUT1 SORTOUT S33 FDSYM8 FDSYM8 FDSYM8 FDSYM8 SHR SHR SHR SHR N29Y8901 FIRST N29Y8902 FIRST N29Y8903 LAST S33Z001 STEP1 STEP001 MERGE PRINT COUNT 2 2 2 2 SYSUT1 SORTIN SORTIN SYSTT1 FDSYM8 FDSYM8 FDSYM8 FDSYM8 SHR SHR SHR SHR
00004 JOBS FOR DATASET )
00004 JOBS FOR DATASET )
8 58
Appendixes
Appendix A: Appendix B: Appendix C: Appendix D: Editing Job Scheduling Definitions in the Edit Environment Editing CMEM Rule Definitions in the Edit Environment AutoEdit Facility in KSL MVS WTO Route/Descriptor Codes
INDEX
Appendix A: Editing Job Scheduling Definitions in the Edit Environment

Job scheduling definition parameters can be edited (moved, copied, deleted, repeated) by performing IOA Line Editing commands, similar to standard ISPF line commands, from within the Edit environment. The Edit environment in the Job Scheduling Definition screen is accessed by typing EDIT in the COMMAND field and pressing <ENTER>.
JOB: BACKP02 LIB CTM.PROD.SCHEDULE TABLE: BACKUP COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ __ MEMNAME BACKP02 MEMLIB CTM.PROD.JOBLIB __ OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y __ APPL APPL-L GROUP BKP-PROD-L __ DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L __ OVERLIB CTM.OVER.JOBLIB __ SET VAR __ CTB STEP AT NAME TYPE __ DOCMEM BACKP02 DOCLIB CTM.PROD.DOC __ =========================================================================== __ DAYS DCAL __ AND/OR __ WDAYS WCAL __ MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y __ DATES __ CONFCAL WORKDAYS SHIFT RETRO N MAXWAIT 00 D-CAT __ MINIMUM PDS __ =========================================================================== __ IN START-DAILY-BACKUP ODAT __ CONTROL __ RESOURCE INIT 0001 CART 0001 USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 11.17.00
A two-character Line Editing command field, marked by underscores, is displayed for each line on the screen. Editing commands are typed directly onto these underscores. Note Edit commands cannot be applied to the first line of an IN block or an OUT block.
Incorrectly specified Line Editing commands can be corrected by typing over them correctly. Line Editing commands can be deleted by blanking them out or by specifying the RESET command in the COMMAND field. Specified Line Editing commands are processed when <ENTER> is pressed. CONTROL-M performs Automatic Syntax Checking to ensure that definition is still syntactically correct after editing. If an edit will scheduling definition, a message is displayed at the top of the screen performed. See "Maintaining Valid Job Scheduling Definitions" in recommendations for editing job scheduling definitions. the job scheduling invalidate the job and the edit is not this appendix for
A1
All operations available in the Job Scheduling Definition screen can be performed while in the Edit environment (e.g., parameter values can be changed; the job scheduling definition can be saved and exited). To exit the Edit environment, re-type EDIT in the COMMAND field and press <ENTER>. Line Editing command fields are removed from the display. Line Editing commands can be performed on the following: Single Lines One single line on the screen. Examples: Additional lines of parameter IN. Single-lined DO statement (such as DO COND). Logical Lines All parameter lines for a specific parameter, including its subparameters. Examples: Statement DO SHOUT, whose subparameters are distributed over more than one line. Single-lined DO statement (such as DO COND). Logical Blocks Functional group of parameter lines. Job scheduling definitions consist of at least one logical block an ON block. Example: Multiple Lines ON block, which consists of its respective parameter lines and the DO statement lines.
User-specified group of parameter lines. Example: A series of DO statement.
Line Editing Commands

The Edit environment supports six types of Line Editing commands. Delete commands DS DL DB DD D Delete a single line. Delete a logical line. Delete a logical block. Delete lines between two DD specifications. Delete a single line, unless CONTROL-M determines that the line is a logical line, in which case CONTROL-M deletes the logical line. Copy a single line. Copy a logical line. Copy a logical block. Copy lines between two CC specifications. Copy a single line, unless CONTROL-M determines that the line is a logical line, in which case CONTROL-M copies the logical line.
Copy commands
CS CL CB CC C
A2
Copy commands are used in conjunction with Location commands. The line(s)/block(s) is placed at the position indicated by Location command A or B (described below). Move commands MS ML MB MM M Move a single line. Move a logical line. Move a logical block. Move lines between two MM specifications. Move a single line, unless CONTROL-M determines that the line is a logical line, in which case CONTROL-M moves the logical line.
Move commands are used in conjunction with Location commands. The line(s)/block(s) is placed at the position indicated by Location command A or B (described below). Repeat commands RS RL RB RR R Repeat a single line. Repeat a logical line. Repeat a logical block. Repeat lines between two RR specifications. Repeat a single line, unless CONTROL-M determines that the line is a logical line, in which case CONTROL-M repeats the logical line.
The repeated line(s)/block(s) is placed immediately after the line(s)/block(s) that has been repeated. Insert command Location commands I (Insert) Insert a new logical line/block after the logical line/block marked with an I.
Indication of the position where lines/blocks should be placed. A (After) Indicates that lines/blocks should be placed after the line marked with an A.
B (Before) Indicates that lines/blocks should be placed before the line marked with a B. Location commands A and B are used in conjunction with Copy (C, CS, CL, CC, CB), and Move (M, MS, ML, MM, MB) commands.
A3
Maintaining Valid Job Scheduling Definitions

Since job scheduling definitions must be syntactically correct at all times, the user should consider the following issues when specifying Line Editing commands:
The result of a Line Editing command is dependent on the line on which the command is specified. For example, command D deletes either a single or a logical line based on the line type. Logical lines form a unit and cannot be separated. When a logical command is specified within a logical line (i.e., on a subparameter line or an additional parameter line), the specified operation is performed on the entire logical line.
Block commands should be specified on the main line(s) of the block. For example, to delete an ON block, command DB (Delete Block) should be specified on the ON line. Blank parameter lines are added automatically by CONTROL-M (to allow the user to specify additional parameters), and cannot be deleted. It is recommended that, wherever possible, commands D, C, R, and M be used for editing (instead of DS, DL, CS, CL, RS, RL, MS, and ML) because these commands automatically retain the logical structure of the job scheduling definition.
A4
Example 1 Before:
Insert additional DO statements within a DO block using command I (Insert).
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +--------------------------------------------------------------------------+ __ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS __ SYSOUT OP (C,D,F,N,R) FROM __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ STEP RANGE FR (PGM.PROC) . TO . __ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O __ CODES I_ DO IFRERUN FROM $ABEND . TO . CONFIRM Y __ DO RERUN __ DO __ ON PGMST PROCST CODES A/O __ DO __ SHOUT WHEN TO URGN __ MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
14.47.22
After:
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +-------------------------------------------------------------------------+ __ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS __ SYSOUT OP (C,D,F,N,R) FROM __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ STEP RANGE FR (PGM.PROC) . TO . __ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O __ CODES __ DO IFRERUN FROM $ABEND . TO . CONFIRM Y __ DO __ DO RERUN __ DO __ ON PGMST PROCST CODES A/O __ DO __ SHOUT WHEN TO URGN __ MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
14.49.42
A5
Example 2 Before:
Delete an ON PGMST block. Use of the DB (Delete Block) command is the preferred method. The DB command removes all parameters, comments, continuation lines, and separator lines of the specified block. DB must be specified on a main line of the block (i.e., ON PGMST). In this example, the ON PGMST block (indicated by A) will be deleted.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +--------------------------------------------------------------------------+ __ =========================================================================== __ OUT __ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ SYSOUT OP (C,D,F,N,R) FROM __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ STEP RANGE FR (PGM.PROC) . TO . DB ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O __ CODES __ DO IFRERUN FROM $ABEND . TO . CONFIRM Y __ DO RERUN __ DO __ ON PGMST PROCST CODES A/O __ DO __ SHOUT WHEN TO URGN __ MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
14.52.02
After:
The ON PGMST ANYSTEP block has been deleted.

JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +--------------------------------------------------------------------------+ __ =========================================================================== __ OUT __ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ SYSOUT OP (C,D,F,N,R) FROM __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ STEP RANGE FR (PGM.PROC) . TO . __ ON PGMST PROCST CODES A/O __ DO __ SHOUT WHEN TO URGN __ MS ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
14.53.58
A6
Example 3 Before:
Move multiple DO statements from one sub-block to another. Command MM (Multiple Move) is specified at the beginning and end of the DO statements that will be moved. Command A (After) specifies the location after which these lines will be placed.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +--------------------------------------------------------------------------+ __ OUT __ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ SYSOUT OP (C,D,F,N,R) FROM __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ STEP RANGE FR (PGM.PROC) . TO . __ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O __ CODES __ DO IFRERUN FROM $ABEND . TO . CONFIRM Y __ DO RERUN MM DO COND STEP5_DONE ODAT + __ DO SHOUT TO TSO-M22 URGENCY R MM = STEP STEP05 PROCESSED __ DO __ ON PGMST STEP05 PROCST CODES S*** A/O A_ DO IFRERUN FROM $ABEND . TO . CONFIRM N __ DO __ ON PGMST PROCST CODES A/O __ DO __ SHOUT WHEN TO URGN __ MS USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 15.03.25
After:
The two specified DO statements have been moved to the specified location.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +--------------------------------------------------------------------------+ __ OUT __ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ SYSOUT OP (C,D,F,N,R) FROM __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ STEP RANGE FR (PGM.PROC) . TO . __ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O __ CODES __ DO IFRERUN FROM $ABEND . TO . CONFIRM Y __ DO RERUN __ DO __ ON PGMST STEP05 PROCST CODES S*** A/O __ DO IFRERUN FROM $ABEND . TO . CONFIRM N __ DO COND STEP5_DONE ODAT + __ DO SHOUT TO TSO-M22 URGENCY R __ = STEP STEP05 PROCESSED __ DO __ ON PGMST PROCST CODES A/O __ DO __ SHOUT WHEN TO URGN __ MS USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 15.06.09
A7
Example 4 Before:
Copy ON PGMST and some of its DO statements to another ON PGMST block. Command CC (Multiple Copy) is specified at the beginning and the end of the parameters that will be copied. Command B (Before) specifies the location before which these lines will be placed.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +--------------------------------------------------------------------------+ __ OUT __ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ SYSOUT OP (C,D,F,N,R) FROM __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ STEP RANGE FR (PGM.PROC) . TO . __ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O __ CODES __ DO IFRERUN FROM $ABEND . TO . CONFIRM Y __ DO RERUN __ DO CC ON PGMST STEP05 PROCST CODES S*** A/O __ DO IFRERUN FROM $ABEND . TO . CONFIRM N CC DO COND STEP5_DONE ODAT + __ DO SHOUT TO TSO-M22 URGENCY R __ = STEP STEP05 PROCESSED __ DO B ON PGMST PROCST CODES A/O __ DO __ SHOUT WHEN TO URGN __ MS USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 15.17.22
After:
The specified ON PGMST and DO statements have been copied.

JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +--------------------------------------------------------------------------+ __ SYSOUT OP (C,D,F,N,R) FROM __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ STEP RANGE FR (PGM.PROC) . TO . __ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O __ CODES __ DO IFRERUN FROM $ABEND . TO . CONFIRM Y __ DO RERUN __ DO __ ON PGMST STEP05 PROCST CODES S*** A/O __ DO IFRERUN FROM $ABEND . TO . CONFIRM N __ DO COND STEP5_DONE ODAT + __ DO SHOUT TO TSO-M22 URGENCY R __ = STEP STEP05 PROCESSED __ DO __ ON PGMST STEP05 PROCST CODES S*** A/O __ DO IFRERUN FROM $ABEND . TO . CONFIRM N __ DO COND STEP5_DONE ODAT + __ DO __ ON PGMST PROCST CODES A/O __ DO USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 15.19.53
A8
Example 5 Before:
Insert a continuation line between existing continuation lines. It is recommended that command RS (Repeat Single) or R (Repeat) be used to repeat the previous line.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +--------------------------------------------------------------------------+ __ RESOURCE __ PIPE __ TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM __ =========================================================================== __ OUT __ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ SYSOUT OP (C,D,F,N,R) FROM __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ STEP RANGE FR (PGM.PROC) . TO . __ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 C3000 A/O A RS CODES C4000 C5000 C6000 C7000 __ CODES C1200 __ ON PGMST STEP04 PROCST CODES ***** A/O __ DO IFRERUN FROM $ABEND . TO . CONFIRM Y __ DO RERUN __ DO __ ON PGMST STEP05 PROCST CODES S*** A/O __ DO IFRERUN FROM $ABEND . TO . CONFIRM N __ DO COND STEP5_DONE ODAT + __ DO SHOUT TO TSO-M22 URGENCY R __ = STEP STEP05 PROCESSED USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 15.22.46
After:
The continuation line has been repeated. The repeated line can be modified as necessary.
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL COMMAND ===> SCROLL===> CRSR +--------------------------------------------------------------------------+ __ RESOURCE __ PIPE __ TIME: FROM UNTIL PRIORITY DUE OUT CONFIRM __ =========================================================================== __ OUT __ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS __ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP __ SYSOUT OP (C,D,F,N,R) FROM __ RERUN - MAXRERUN 3 RERUNMEM INTERVAL __ STEP RANGE FR (PGM.PROC) . TO . __ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 C3000 A/O A __ CODES C4000 C5000 C6000 C7000 __ CODES C4000 C5000 C6000 C7000 __ CODES C1200 __ ON PGMST STEP04 PROCST CODES ***** A/O __ DO IFRERUN FROM $ABEND . TO . CONFIRM Y __ DO RERUN __ DO __ ON PGMST STEP05 PROCST CODES S*** A/O __ DO IFRERUN FROM $ABEND . TO . CONFIRM N __ DO COND STEP5_DONE ODAT + __ DO SHOUT TO TSO-M22 URGENCY R USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 15.23.46
A9
A 10
Appendix B: Editing CMEM Rule Definitions in the Edit Environment

General
CMEM rule definition parameters can be edited (moved, copied, deleted, repeated) by performing IOA Line Editing commands, similar to standard ISPF line commands, from within the IOA Edit environment. The Edit environment in a Rule Definition screen is accessed by typing EDIT in the COMMAND field and pressing <ENTER>.
RL: JOBNAM1 LIB CTM.PROD.RULES TABLE: CMEMRULE COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ __ ON JOBARRIV = JOBNAM1 JTYPE SMFID SYSTEM And/Or/Not __ OWNER CTMCTLM GROUP MODE PROD RUNTSEC NONE __ DESCRIPTION CONVERSION: ON JOB JOBNAM1 ARRIVAL FORCEJOB __ DESCRIPTION __ =========================================================================== __ DO FORCEJOB = TABLE TABLE1 JOB DATE ODAT __ LIBRARY CTM.PROD.SCHEDULE __ DO __ =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
20.10.46
A two-character Line Editing command field, marked by underscores, is displayed for each line on the Rule Definition screen. Editing commands are typed directly onto these underscores. Incorrectly specified Line Editing commands can be corrected by typing over them correctly. Line Editing commands can be deleted by blanking them out or by specifying the RESET command in the COMMAND field. Specified Line Editing commands are processed when <ENTER> is pressed. The CMEM facility performs Automatic Syntax Checking to ensure that the rule definition is still syntactically correct after editing. If an edit will invalidate the rule definition, a message is displayed at the top of the screen and the edit is not performed. See Maintaining Valid Rule Definitions in this appendix for guidelines and recommendations for editing rule definitions.
B1
All operations available in the Rule Definition screen can be performed while in the Edit environment (e.g., parameter values can be changed, the Rule Definition screen can be saved and exited). To exit the Edit environment, re-type EDIT in the COMMAND field and press <ENTER>. Line Editing command fields are removed from the display. Line Editing commands can be performed on any single ON/DO statement or on a block of ON/DO statements. All lines of a single statement (e.g., the two lines of a DO FORCEJOB statement) constitute a logical line.
Line Editing Commands

The following types of Line Editing commands exist in the Edit environment. Delete commands DS/DL DD D Copy commands CS/CL CC C Deletes a logical line. Deletes lines between two DD specifications. Deletes a line. CMEM determines whether to delete a single or logical line based on the parameter on the line. Copies a logical line. Copies lines between two CC specifications. Copies a line. CMEM determines whether to copy a single or logical line based on the parameter on the line.
Copy commands are used in conjunction with Location commands. The line(s) is placed at the position indicated by Location command A or B. Move commands MS/ML MM M Moves a logical line. Moves lines between two MM specifications. Moves a line. CMEM determines whether to move a single or logical line based on the parameter on the line.
Move commands are used in conjunction with Location commands. The line(s) is placed at the position indicated by Location command A or B. Repeat commands RS/RL RR R Repeats a logical line. Repeats lines between two RR specifications. Repeats a line. CMEM determines whether to repeat a single or logical line based on the parameter on the line.
The repeated line(s) is placed immediately after the line(s) that has been repeated. Insert command I (Insert) Inserts a new logical line/block after the logical line marked with an I.
B2
Location commands
Indication of the position where lines should be placed. A (After) Indicates that lines should be placed after the line marked with an A.
B (Before) Indicates that lines should be placed before the line marked with a B. Location commands A and B are used in conjunction with Copy (C, CS, CL, CC), and Move (M, MS, ML, MM) commands.
Maintaining Valid Rule Definitions

Since rule definitions must be syntactically correct at all times, the user should consider the following issues when specifying Line Editing commands:
The result of a Line Editing command is dependent on the line on which the command is specified. For example, command D deletes either a single or a logical line based on the line type. Logical lines function as a unit and cannot be separated. When a logical command is specified within a logical line (i.e., on a subparameter line, or a continuation line), the specified operation is performed on the entire logical line.
Blank parameter lines added automatically by CMEM (to allow the user to specify additional parameters) cannot be deleted.
It is recommended that, wherever possible, commands D, C, R, and M be used for editing (instead of DS, DL, CS, CL, RS, RL, MS, and ML) because these commands automatically retain the logical structure of the rule definition.
B3
Example
Before:
Repeat a DO block in the Rule Definition screen.
RL: JOBNAM1 LIB CTM.PROD.RULES TABLE: CMEMRULE COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ __ ON JOBARRIV = JOBNAM1 JTYPE SMFID SYSTEM And/Or/Not __ OWNER CTMCTLM GROUP MODE PROD RUNTSEC NONE __ DESCRIPTION CONVERSION: ON JOB JOBNAM1 ARRIVAL FORCEJOB __ DESCRIPTION __ =========================================================================== R_ DO FORCEJOB = TABLE TABLE1 JOB DATE ODAT __ LIBRARY CTM.PROD.SCHEDULE __ DO __ =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
20.10.46
After:
The DO block has been repeated.
RL: JOBNAM1 LIB CTM.PROD.RULES TABLE: CMEMRULE COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ __ ON JOBARRIV = JOBNAM1 JTYPE SMFID SYSTEM And/Or/Not __ OWNER CTMCTLM GROUP MODE PROD RUNTSEC NONE __ DESCRIPTION CONVERSION: ON JOB JOBNAM1 ARRIVAL FORCEJOB __ DESCRIPTION __ =========================================================================== __ DO FORCEJOB = TABLE TABLE1 JOB DATE ODAT __ LIBRARY CTM.PROD.SCHEDULE __ DO FORCEJOB = TABLE TABLE1 JOB DATE ODAT __ LIBRARY CTM.PROD.SCHEDULE __ DO __ =========================================================================== ======= >>>>>>>>>>>>>>> END OF RULE DEFINITION PARAMETERS <<<<<<<<<<<<<<< =====
20.32.47
B4
Appendix C: AutoEdit Facility in KSL

The AutoEdit facility provides additional data manipulation capabilities. It is composed of the following types of AutoEdit symbols and instructions:
System variables User-defined variables Operators Functions
These components can be used in certain KSL commands (as described in Section 8 of this manual) and are resolved according to the AutoEdit rules described in this appendix. Note KSL and CONTROL-M have different AutoEdit processors. Therefore, if a KSL script containing KSL AutoEdit terms is submitted under CONTROL-M, the CONTROL-M AutoEdit %%RANGE statement should be used in the JCL to ensure that the CONTROL-M AutoEdit processor skips (i.e., does not process) the KSL script.
System Variables System variables are predefined, commonly used variables whose values are automatically updated and maintained by the AutoEdit facility. The System variable format is: %%$var Where var represents the name of the System variable. Each AutoEdit variable begins with %%. Each variable resolves to (is replaced by) the corresponding system value. AutoEdit System variables are described on the following pages. Example
TYPE %%$DATE
resolves on the 12th of December 1998 to:

TYPE 981212
C1
AutoEdit System Variables: Note The symbol following an AutoEdit System variable indicates that if the variable is specified without the $ in the prefix, the variable will still be supported. Concatenation character.
%%. %%$BLANK
Resolves to one blank.
%%$BLANKn
Resolves to n blanks, where n is a number between 1 and 99. Hexadecimal number resulting from the conversion of decimal number 31 num. The largest number that can be converted is 2147483647 (i.e., 2 1). Example: %%$D2X 4095 converts to FFF.
%%$D2X num
%%$DATE %%$DAY
Current system date (format yymmdd). Current system day (format dd).
%%$JULDAY
Current system day (Julian format jjj).
%%$LENGTH varname Length of variable varname. %%$MONTH
Current system month (format mm). MVS product release (eight characters) under which IOA is running. Examples: SP3.1.1, SP4.2.2 Indicates a null variable (a variable with length 0). Return code from a %%$PARSE function. Indicated whether the parsed string matched all string patterns in the template. Possible values: 0 4 The parsed string fully matched the string patterns in the template. At least one string pattern in the template was not matched.
%%$MVSLEVEL %%$NULL
%%$PARSRC
%%$RDATE %%$RDAY
Current working date (format yymmdd). Current working day (format dd).
%%$RJULDAY %%$RMONTH
Current working day of the year (Julian format jjj). Current working month (format mm).
C2
%%$RWDAY
Current working day of the week. Format is d, where d is 1 through 6 or 0 (e.g., 1=Sunday, 2=Monday, ... 6=Friday, 0=Saturday).
1
%%$RYEAR %%$SMFID
Current working year (format yy). The SMF ID of the CPU running the KSL script.
%%$SSNAME
Name of the IOA subsystem.
%%$SUBSTR varname pos len Substring of variable varname starting at position pos with length len. %%$TIME
Time of day (format hhmmss).
%%$UNDEF
Indicates an undefined variable. This variable can be used:
To test whether or not a variable is defined:

IF %%variable EQ %%$UNDEF
To delete a variable:
SETOLOC = %%variable = %%$UNDEF %%$WDAY
Current system day of the week. Format is d, where d is 1 through 6 or 0 (e.g., 1=Sunday, 2=Monday, ... 6=Friday, 0=Saturday).
2
%%$Wn varname
The nth word (a comma or a blank may serve as a delimiter) of variable varname. n may be a value from 1 99. For example, %%$W3 %%MESSAGE represents the third word in the original user-defined message text.
%%$WORDS varname Number of words in variable varname. Delimiters are commas and/or blanks within the variable. %%$X2D string Numeric decimal string resulting from the conversion of the hexadecimal number string. The maximum number that can be converted is 7FFFFFFF. Example: %%$X2D FFF converts to 4095. %%$YEAR
Current system year (format yy).
Start of the week depends on an IOA installation parameter specifying whether 1=Sunday or 1=Monday. See your IOA administrator for your site standard. Start of the week depends on an IOA installation parameter specifying whether 1=Sunday or 1=Monday. See your IOA administrator for your site standard.
C3
User-Defined Variables The user-defined variables capability is designed to provide additional flexibility. You can define your own symbols via KSL command SETOLOC and use them in other KSL commands. They will automatically be resolved when the KSL is executed. A user-defined variable can be any alphanumeric string starting with %%. The characters @ # $ _ are also valid. Lowercase characters are not translated to uppercase characters upon resolution. When the AutoEdit facility identifies a string that starts with %%, the string is assumed to be an AutoEdit variable or instruction. If the string is a reserved AutoEdit symbol or a System variable, it is interpreted as such. Otherwise the string is assumed to be a user-defined variable. Rules of Variable Substitution A KSL command can contain expressions including both KSL and AutoEdit variables. Variable substitution is performed in the following order: 1. All KSL variables (i.e., variables preceded by a single % character) are substituted sequentially from left to right. Example
TYPE %A %%$PLUS 1
Assuming that the value of %A is 1, variable substitution begins as follows (the KSL variable is substituted):
TYPE 1 %%$PLUS 1
2. If the resulting expression contains AutoEdit symbols (i.e., symbols beginning with %%), the expression is further resolved (in the above example, TYPE 1 %%$PLUS 1 would resolve to TYPE 2) according to the following rules: Variables are substituted sequentially from right to left until the symbol is assigned a value. 3. The largest number that can be handled by mathematical AutoEdit operations is 2 1 (i.e., 2147483647).
31
C4
Example
%%SMF_TAPE_%%DAY,
resolves on the third of the month to:

%%SMF_TAPE_03,
The AutoEdit facility then tries to resolve the symbol %%SMF_TAPE_03. Assuming the value of the symbol in the Global environment is EE1022, the result is: EE1022 To concatenate two symbols, separate them with a period. Before AutoEdit variables are concatenated, trailing blanks are eliminated. Example
%%DAY.%%MONTH
resolves on the 3rd of December to: 0312 Note Specification of %%DAY%%MONTH would result in an attempt to resolve %%DAY12 (a user-defined variable).
To put a period between two symbols, use two consecutive periods. Example
%%DAY..%%MONTH
resolves on the 3rd of December to: 03.12 To concatenate a symbol and a constant, use %%. (concatenation symbol). Example
A91%%DAY%%.UP
resolves on the 3rd of December to: A9103UP Note Specification of A91%%DAYUP would result in an attempt to resolve %%DAYUP (a user-defined variable).
C5
AutoEdit Operators AutoEdit operators can be used in conjunction with AutoEdit symbols. Valid AutoEdit operators are: %%$PLUS %%$MINUS %%$TIMES %%$DIV Note Add two operands. Subtract the second operand from the first operand. Multiply one operand by another operand. Divide the first operand by the second operand. To ensure compatibility with IOA releases prior to Release 5.0.0, operators %%$PLUS and %%$MINUS are also supported if specified without the dollar sign.
The format for use of AutoEdit symbols and operators is:

operand operator operand
Only one operator can be used in an expression. Operands must resolve into positive numeric constants. The final result is translated into a character string. For example:
SETOLOC %%x = %%x %%$PLUS 1
User-defined variable %%x is incremented by one. %%$CALCDATE Function The %%$CALCDATE function performs date calculations based on a specified date. Format:
%%$CALCDATE date quantity
where: date quantity Date in yymmdd format. Number (or numeric AutoEdit expression) of days to add or subtract from the date (from 1 to 366). To ensure compatibility with IOA releases prior to Release 5.0.0, this statement is also supported if written as %%CALCDATE. %%$CALCDATE operates on Gregorian dates only; %%JULDAY) cannot be specified. Julian dates (such as
Notes
Example
SETOLOC %%A = %%$CALCDATE %%$RDATE -1
On February 1, 1998:
SETOLOC %%A = 980131
C6
%%$SUBSTR Function The %%$SUBSTR function extracts a substring from the input string. Format:
%%$SUBSTR strng startpos len
where: strng startpos len Note Input string from which the substring is extracted. First character of the input string to extract. Number of characters to extract. To ensure compatibility with IOA releases prior to Release 5.0.0, this statement is also supported if written as %%SUBSTR.
A string is returned composed of the specified number of characters from the input string beginning with the character in the specified starting position. startpos and len must be numbers (or numeric AutoEdit expressions) and greater than zero. If (startpos + len 1) is greater than the strng length, the function is not executed and the value returned is null. Example
SETOLOC %%A = %%$CALCDATE %%$RDATE -1 SETOLOC %%AMON = %%$SUBSTR %%A 3 2
On December 1, 1998:
SETOLOC %%A = 981130 SETOLOC %%AMON = 11
C7
%%$TIMEINT Function The %%$TIMEINT function calculates the time interval between two given times (specified in any order). Format:
%%$TIMEINT time1 time2
time1 and time2 are constants or variables in yydddhhmmss format. yy ddd hh mm ss two-digit year Julian day hours minutes seconds
The resulting time interval is in format: ddddd hh mm ss Example

SETOLOC %%A = %%$TIMEINT 98120070000 98119060000
number of days hours minutes seconds
The result is: 00001010000.
C8
%%$PARSE Function The %%$PARSE function is a powerful tool that offers extensive string manipulation capabilities in the AutoEdit environment. This function, which is similar to the REXX PARSE command in the TSO/E environment, can be used to analyze and extract information from various AutoEdit strings. The %%$PARSE function parses a specified string (i.e., splits the specified string into substrings) according to a specified template. A template consists of variables and patterns which determine the parsing process. Format:
SETOLOC %%$PARSE strng template
where: strng template Example

SETOLOC %%S = THIS IS A SAMPLE STRING SETOLOC %%T = A1 A2 A3 A4 A5 SETOLOC %%$PARSE %%S %%T
AutoEdit variable that contains the string to be parsed. AutoEdit variable or constant that contains the template.
The %%$PARSE function assigns substrings of the specified string to the specified variables according to the specified template. The SETOLOC statements in the above example provide the same result as the following statements:
SETOLOC SETOLOC SETOLOC SETOLOC SETOLOC %%A1 %%A2 %%A3 %%A4 %%A5 = = = = = THIS IS A SAMPLE STRING
The parsing process involves the following stages: 1. The string is broken into substrings, from left to right, using the patterns in the template. 2. Each substring is parsed into words, from left to right, using the variable names in the template.
C9
Template elements are:
String Patterns Position Patterns Variables Place holders (dummy variables)
The rules of parsing are detailed below. Parsing Words Scanning is performed from left to right and words in the string (leading and trailing blanks excluded) are matched one by one with the variables named in the template. The last variable named in the template will contain the remaining part of the string, including leading and trailing blanks. Up to 30 variable names can be specified in a parsing template. The following situations can be encountered:
The number of words in the string matches the number of variables in the template: Each of those variables will contain one word of the string. The last variable will contain the last word in the string including leading and/or trailing blanks. The number of words in the string is smaller than the number of variables named in the template: The first variables will each contain one word of the string and the extra variables will receive a value of NULL (a string of 0 character length). The number of words in the string is greater than the number of variables in the template: All variables, but the last one, will contain one word of the string and the last variable named in the template will contain the remaining part of the string, including leading and trailing blanks.
Example The statements below (which include a %%$PARSE function):

SETOLOC %%S = THIS IS A SAMPLE STRING SETOLOC %%T = A1 A2 A3 SETOLOC %%$PARSE %%S %%T
have the same result as the following statements:

SETOLOC %%A1 = THIS SETOLOC %%A2 = IS SETOLOC %%A3 = A SAMPLE STRING
C 10
Using Dummy Variables (Place Holders) A single period can be used as a dummy variable in the template. This is useful when the corresponding word in the string does not need to be stored in a named variable. Example The following statements (which include a %%$PARSE function):
SETOLOC %%S = THIS IS A SAMPLE STRING SETOLOC %%T = . . . A4. SETOLOC %%$PARSE %%S %%T
have the same result as the following statement:

SETOLOC %%A4 = SAMPLE
Using Patterns in Parsing Patterns can be included in the template. Their purpose is to divide the string into substrings prior to the process of parsing into words. Parsing will then be performed, as previously described, on the substrings and not on the original string. The following types of patterns are available: String Pattern Numeric (Positional) Pattern Using String Patterns The string is scanned from left to right for a substring that matches the string pattern. The following situations may occur: 1. A match is found (a substring within the string is identical to the given string pattern): The original string is divided into two substrings. The first substring (up to, but not including, the string pattern) is parsed into words using the variables named before the string pattern on the template. Parsing continues from the character following the matched string. Example
SETOLOC %%S = THIS IS A SAMPLE STRING SETOLOC %%T = A1 A2 SAMPLE A3 A4 A5 SETOLOC %%$PARSE %%S %%T
Character string delimited by quotes (to distinguish it from a variable name). Number (signed or unsigned).
A match is found since the string SAMPLE is part of the original string. System variable %%$PARSRC can be used to check if all strings specified in the template were matched during the parsing process (discussed earlier in this section).
C 11
The original string is divided into two substrings while the matched part of the string is excluded. Parsing of the first substring will use the variables listed before the match on the template while parsing of the second substring will use the variables listed after the match: First substring: THIS IS A As a result of parsing: A1=THIS A2=IS A Second substring: STRING As a result of parsing: A3=STRING A4=NULL A5=NULL 2. A match is not found (there is no substring identical to the given string pattern within the string): It is assumed that a match is found at the end of the string. The first substring consists of the entire string and it is parsed using only the variables named before the string pattern on the template. Parsing continues from the character following the matched string (the end of the string, in this case). Example
SETOLOC %%S = THIS IS A SAMPLE STRING SETOLOC %%T = A1 A2 A3 EASY A4 A5 SETOLOC %%$PARSE %%S %%T
A match is not found since the string EASY does not exist in the original string. First substring: THIS IS A SAMPLE STRING As a result of parsing: A1=THIS A2=IS A3=A SAMPLE STRING Second substring: NULL As a result of parsing: A4=NULL A5=NULL
C 12
Using Numeric Patterns Within the Template Numeric patterns are numbers which mark positions within the string. They are used to break the original string into substrings at the position indicated by the number. The position specified can be absolute or relative:
An absolute position is specified by an unsigned number. A relative position is specified by a signed number (positive or negative). It determines a new position within the string, relative to the last position.
Last position refers to one of the following:
The start of the string (position 1) if last position was not specified previously. The starting position of a string pattern if a match was found. The end of the string if the string pattern was not matched. The last position specified by a numeric pattern.
If the specified position exceeds the length of the string, the numeric pattern is adjusted to the end of the string. Similarly, if the specified position precedes the beginning of the string (negative or zero numeric pattern), the beginning of the string is used as the last position. Example 1 A parsing template with an absolute numeric pattern:
SETOLOC %%S =THIS IS A SAMPLE STRING SETOLOC %%T = A1 A2 11 A3 A4 A5 SETOLOC %%$PARSE %%S %%T
First substring: THIS IS A (up to, not including, position 11) As a result of parsing: A1=THIS A2=IS A Second substring: SAMPLE STRING (from position 11, to the end of the string). As a result of parsing: A3=SAMPLE A4=STRING A5=NULL (0 length string)
C 13
Example 2 A parsing template with a relative numeric pattern:

SETOLOC %%S =THIS IS A SAMPLE STRING SETOLOC %%T = A1 A2 +10 A3 A4 A5 SETOLOC %%$PARSE %%S %%T
Last position is the beginning of the string (position 1). Position marked within the string is 1 + 10 = 11. First substring: THIS IS A (up to, not including, position 11) As a result of parsing: A1=THIS A2=IS A Second substring: SAMPLE STRING (from position 11, to the end of the string). As a result of parsing: A3=SAMPLE A4=STRING A5=NULL (0 length string) Using More Than One Pattern and Combining Pattern Types in the Template Both types of patterns (string and numeric) can be intermixed in the same template. Up to 30 patterns and up to 30 variable names can be specified. Scanning of the string proceeds from the beginning of the string until first pattern (if any). 1. String pattern a match was found: The substring that precedes the match with the pattern is parsed using the variables named in the template before the pattern, with the last variable receiving the end of the substring, including leading/trailing blanks. 2. String pattern a match was not found: Since no match was found within the string, it is assumed that a match is found at the end of the string. The whole string is parsed using only the variables named in the template before the pattern. 3. Numeric pattern (absolute). The absolute numeric pattern points to a position within the string. The beginning of the string is position 1. The string is divided into two substrings. The first substring extends from the beginning of the string and up to, but not including, the position that corresponds to the numeric pattern. This substring is parsed using the variables named in the template before the pattern.
C 14
If the absolute numeric pattern specifies a position beyond the length of the string, it is readjusted to the first position beyond the length of the string and the entire string is parsed using the variables named in the template before the pattern. 4. Relative numeric pattern: The relative numeric pattern (a signed number) specifies a position within the string, relative to the last position. 5. Last position: If the relative numeric pattern is the first pattern within the template, the last position is the beginning of the string. If the relative numeric pattern is not the first pattern within the template and the previous pattern was numeric, the last position is that specified by the previous numeric pattern. If the relative numeric pattern is not the first pattern within the template and the previous pattern was a string, the last position is that of the starting character of the match (if there was a match) or the position following the end of the string (if there was no match). As a result of what was just explained:
If a pattern was not matched until the end of the string and the following pattern is a string pattern, this new string pattern will be ignored since the starting point for the new scan is the end of the string. If a pattern was not matched until the end of the string and the following pattern is a numeric pattern, then the scan and subsequent parsing will resume from the new position indicated by that numeric pattern.
C 15
Example 1 A parsing template with two absolute numeric patterns (with the second position preceding the first): The following statements:
SETOLOC %%S = THIS IS A SAMPLE STRING SETOLOC %%T = A1 A2 11 A3 6 A4 SETOLOC %%$PARSE %%S %%T
have the same result as the following DO SET statements:

SETOLOC SETOLOC SETOLOC SETOLOC %%A1 %%A2 %%A3 %%A4 = = = = THIS IS A SAMPLE STRING IS A SAMPLE STRING
First substring: THIS IS A (up to, not including, position 11) As a result of parsing: A1=THIS A2=IS A Second substring: SAMPLE STRING from position 11 and up to the end of the string. Because the next pattern, position 6, precedes the previous position, it cannot limit this second substring. As a result of parsing: A3=SAMPLE STRING Third substring: IS A SAMPLE STRING (from position 6 to the end of the string) As a result of parsing: A4=IS A SAMPLE STRING
C 16
Example 2 A parsing template with one absolute and one relative numeric pattern:
SETOLOC %%S = THIS IS A SAMPLE STRING SETOLOC %%T = A1 6 A2 +3 A3 SETOLOC %%$PARSE %%S %%T
First substring: THIS (beginning of the string up to, not including, position 6). As a result of parsing: A1=THIS Second substring: IS (from position 6 up to, not including, position 6+3=9) As a result of parsing: A2=IS Third substring: A SAMPLE STRING (from position 9 to the end of the string) As a result of parsing: A3=A SAMPLE STRING Example 3 A parsing template with two relative numeric patterns: The following statements:
SETOLOC %%T = A1 A2 +40 A3 -13 A4 A5 SETOLOC %%S = THIS IS A SAMPLE STRING SETOLOC %%$PARSE %%S %%T

SETOLOC SETOLOC SETOLOC SETOLOC SETOLOC %%A1 %%A2 %%A3 %%A4 %%A5 = = = = = THIS IS A SAMPLE STRING %%NULL SAMPLE STRING
The first numeric pattern specifies a position at column 40. This is beyond the end of the string so position is reset to column 24 (end of string + 1). as a result, the whole string is parsed to words using variables A1 and A2. The second numeric pattern specifies a position at column 11 (end of the string + 1 minus 13) which precedes the position (40 readjusted to 24) previously specified; therefore the data from the last position (which is the end of the string) to the end of the string is parsed to words using variable A3 (A3 is set to NULL). The data (from column 12 to the end of the string) is parsed to words using variables A4 and A5.
C 17
Example 4 Combining string pattern and numeric pattern: The following statements:
SETOLOC %%S = THIS IS A SAMPLE STRING SETOLOC %%T = A1 A A2 +3 A3 SETOLOC %%$PARSE %%S %%T

SETOLOC %%A1 = THIS IS SETOLOC %%A2 = A S SETOLOC %%A3 = AMPLE STRING
The pattern specifies a string (A) which is matched at column 9. The data before column 9 is parsed to words using variable A1. The numeric pattern (+3) specifies a position at column 12 by using relative position. The data from column 9 to column 12 is parsed to words using variable A2. The remaining data (from column 12 to the end of the string) is parsed to words using variable A3.
C 18
Appendix D: MVS WTO Route/Descriptor Codes

MVS WTO Message Route Codes
Route Code 1 2 3 4 5 6 7 8 9 10 11 12 13-20 21-28 29-40 41 42 43-64 65-96 97-128 Type of Information Master console action Master console information Tape pool Direct access pool Tape library Disk library Unit record pool Teleprocessing control System security System/error maintenance Programmer information Emulation Reserved for customer use Reserved for subsystem use Reserved for IBM use JES3 job status General information about JES2 or JES3 Reserved for JES use Messages associated with particular processors Messages associated with particular devices
For more detailed information regarding route codes, refer to the IBM publication Routing and Descriptor Codes, GC38-1102.
D1
MVS WTO Descriptor Codes

Descriptor Code 1 2 3 4 5 6 7 8 9 10 11 12-16 Significance of Code System failure Immediate action required Eventual action required System status Immediate command response Job status Application program/processor Out-of-line message Operators request TRACK command response Critical eventual action required Reserved for future use
For more detailed information regarding descriptor codes, refer to the IBM publication Routing and Descriptor Codes, GC38-1102.
D2
Index
Index
'
Character FIND Command, 2-16 Job Graph, 2-84 RESOURCE Parameter, 3-151 User-Defined Variable, 5-9, C-4 $$$$ Date Reference IN Parameter, 3-88 OUT Parameter, 3-121 Schedule Date, 3-47 $$ACTDOC Member Customization, 2-1 Customizing Status Screen, 2-63 $$DOC Member SAMPLE Library, 8-1 $0 JES Command CONTROL-M Monitor, 6-104 $ABEND DO IFRERUN Statement, 3-54, 3-56 Restart Confirmation Window, 2-100, 2-207 $CJ JES Command CONTROL-M Monitor, 6-104 $CLEANUP Value Rerun/Restart Window, 2-100 $DEFAULT Member Restart Window, 2-99 $EXERR DO IFRERUN Statement, 3-54, 3-56 Restart Confirmation Window, 2-100, 2-207 $FIRST DO IFRERUN Statement, 3-54 DO IFRERUN Statement, 3-56 Restart Confirmation Window, 2-100, 2-207 $FIRST Value Rerun/Restart Window, 2-100 $FIRST.$ABEND DO, 3-54 $FIRST.$CLEANUP DO IFREFUN Statement, 3-54 Restart Confirmation Window, 2-207 $HJ JES Command CONTROL-M Monitor, 6-104
Sign Change Resource Window, 2-138 Job Dependency Network, 2-108 OUT Parameter, 3-121 Quick Schedule Definition, 2-199 Relative Calendar, 2-158
!
! Character CTMQSB Command, 6-16 Hex Value, 2-2
#
# Character Maybe Job Prefix, 6-21 User-Defined Variable, 5-9, C-4 Character Hex Value, 2-2 # OF DAYS TO KEEP Retention Parameter, 3-155 RETENTION Parameter, 3-157 # OF GENERATIONS TO KEEP RETENTION Parameter, 3-155, 3-157 # Symbol Maybe Conditions, 6-21 #END Field Global View Status, 2-80 #EXC Field Global View Screen, 2-80 #WSC Field Global View Screen, 2-80
$
$ Character AutoEdit Operators, C-6 Hex Value, 2-2
CONTROL-M Rel. 5.1.4 - User Manual
I1
Index
$LSYS Command JES2, 3-101 Machine ID Under JES2, 3-68, 3-172 $PJ JES Command CONTROL-M Monitor, 6-104 $SIGN Parameter Testing AutoEdit Syntax, 6-45 $TO JES2 Command CONTROL-M Monitor, 6-104
%
% Symbol AutoEdit Variable, 8-22 Job Graph, 2-84 SHOUT Parameter, 3-170 %% Concatenation Symbol, 5-13 %% Prefix User Defined Variable, 5-9 %% Symbol AutoEdit Term, 1-5, 5-1 AutoEdit Variable, 8-22 Calendar Date, 5-6 Concatenation, 5-5, 5-13 %%$ Prefix System Variable, 5-9 %%$ARGS CONTROL-O System Variable, 4-22 %%$BLANK System Variable, C-2 %%$BLANKn System Variable, C-2 %%$CALCDATE Function Comparison with %%$CALCDTE, 5-23 KSL, C-6 %%$CALCDTE Function Comparison with %%$CALCDATE, 5-26 Description, 5-23 Example, 5-35 %%$CENT First Two Digits of the Year, 5-7 %%$D2X System Variable, C-2
%%$DATE System Variable, C-2 %%$DAY System Variable, C-2 %%$DIV AutoEdit Operator, C-6 %%$Dn CMEM AutoEdit Variable, 4-3, 4-15 %%$DSN CMEM AutoEdit Variable, 4-3 %%$DSNDISP CMEM AutoEdit Variable, 4-3 %%$GREG Function Julian to Gregorian Conversion, 5-23 %%$JNAME CMEM AutoEdit Variable, 4-3, 4-15 %%$JULDAY System Variable, C-2 %%$JULIAN Function Gregorian to Julian Conversion, 5-23 %%$LEAP Function Leap Year Analysis, 5-24 %%$LENGTH System Variable, C-2 %%$MEMNAME System Variable, 5-6 %%$MINUS AutoEdit Operator, C-6 %%$MONTH System Variable, C-2 %%$MVSLEVEL System Variable, C-2 %%$NULL System Variable, C-2 %%$OCENT System Variable, 5-7 %%$ORDERID AutoEdit Simulation, 2-169 %%$PARSE Function Example, C-10, C-13, C-16 KSL, C-9 %%$PARSRC System Variable, C-2, C-12 %%$PLUS AutoEdit Operator, C-6
I2
Index
%%$QNAME Monitor Identifier, 5-6 %%$RCENT System Variable, 5-7 %%$RDATE System Variable, C-2 %%$RDAY System Variable, C-2 %%$RJULDAY Julian Working Day, 5-8 System Variable, C-2 %%$RMONTH System Variable, C-2 %%$RWDAY System Variable, C-3 %%$SABEND CMEM AutoEdit Variable, 4-3 %%$SCHDLIB System Variable, 5-6 %%$SCHDTAB System Variable, 5-6 %%$SIGN Quantitative Resource, 5-6 Testing AutoEdit Syntax, 6-45 %%$SMFID System Variable, C-3 %%$SSNAME System Variable, C-3 %%$STEPCC CMEM AutoEdit Variable, 4-3 %%$SUBSTR System Variable, C-3 %%$SUBSTR Function KSL, C-7 %%$TAG AutoEdit Simulation, 2-169 Schedule Tag Name, 5-6 %%$TIME System Variable, C-3 %%$TIMEINT Function KSL, C-8 %%$TIMES AutoEdit Operator, C-6 %%$UABEND CMEM AutoEdit Variable, 4-3
%%$UNDEF System Variable, C-3 %%$var System Variable, C-1 %%$WCALC Function Working Date Shift, 5-24 %%$WDAY System Variable, C-3 %%$WEEK# Function Week of Year, 5-25 %%$WEEKDAY Function Day of Week Analysis, 5-25 %%$Wn System Variable, C-3 %%$WORDS System Variable, C-3 %%$X2D System Variable, C-3 %%$YEAR System Variable, C-3 %%. System Variable, C-2 %%A.%%B, 5-12 %%APPL Application, 5-5 %%BLANK Blank, 5-5 %%BLANKn DO SET Statement, 3-63 n Blanks, 5-5 %%BLANKn AutoEdit Variable SET VAR Parameter, 3-164 %%CALCDATE AutoEdit Function, 5-3 %%CALCDATE Function Description, 5-26 %%DATE Example, 5-30 System Date, 5-7, 5-8 %%DAY System Day, 5-7 %%ELSE Control Statement Example, 5-43 JCL Setup, 5-16
I3
Index
%%ENDIF Control Statement Example, 5-43 JCL Setup, 5-16 %%GLOBAL AutoEdit Statement, 2-170, 5-2, 5-10 JCL Setup, 5-4, 5-10, 5-15 Variable Member, 5-10 %%GOTO Control Statement Example, 5-44 JCL Setup, 5-15 %%GROUP Job Group, 5-5 %%IF Control Statement Example, 5-43 JCL Setup, 5-16 Nesting, 5-17 %%INCLIB Control Statement Example, 5-42 JCL Setup, 5-18 %%INCMEM Control Statement Example, 5-42 JCL Setup, 5-18 %%JOBCC Final Job Status, 5-8 %%JOBID JES Job Number, 5-8 %%JOBNAM Variable SHOUT Statement, 2-195, 2-201 %%JOBNAME Variable SHOUT Statement, 2-195 Submitted Job Name, 5-6 %%JULDAY Julian Day, 5-7, 5-8 %%LABEL Control Statement Example, 5-44 JCL Setup, 5-15 %%LIBSYM Control Statement, 6-32 AutoEdit Statement, 5-2 JCL Setup, 5-4, 5-19 Library Specification, 5-9 PROMPT Library, 6-34 Variable Member, 5-10 %%MAXRC Highest Return Code, 5-8
%%MEMSYM Control Statement, 6-32 AutoEdit Statement, 5-2 JCL Setup, 5-4, 5-19 Member Specification, 5-9 Table Name Prefix, 6-34 %%MINUS Operator AutoEdit, 5-22 %%MM.%%DD.%%YY Example, 5-35 %%MONTH Month of the Job, 5-7 System Month, 5-7 %%O ODATE, 5-6 %%ODATE Date of the Job, 5-7, 5-8 Example, 5-31 %%ODAY Day of the Job, 5-7 Example, 5-32 %%ODAY.%%A.%%OYEAR Example, 5-33 %%OJULDAY Julian Day of the Job, 5-7, 5-8 %%OMONTH Example, 5-32 %%ORDERID Job Order ID, 5-6 %%OWDAY Day of the Week of the Job, 5-7 Example, 5-38 %%OWDAY.%%TIME Example, 5-40 %%OWEEK Week of the Job, 5-7 %%OWNER Job Owner, 5-6 %%OYEAR Example, 5-32 Year of the Job, 5-7, 5-8 %%PLANID Inter-plan Dependency, 6-40 %%PLUS Operator AutoEdit, 5-3, 5-22
I4
Index
%%R Installation Working Date, 5-6 %%RANGE Control Statement Example, 5-41 JCL Setup, 5-20 %%RANGE Statement Minimum Length, 5-20 %%RDATE Example, 5-31 Working Date, 5-7, 5-8 %%RDAY Working Day, 5-7 %%RESOLVE Control Statement Example, 5-42 JCL Setup, 5-5, 5-21 %%RESOLVE NO Control Statement AutoEdit Logic, 5-21 JCL Setup, 5-21 %%RESOLVE OFF AutoEdit Statement, 6-49 %%RESOLVE YES Control Statement Example, 5-42 %%RJULDAY Julian Working Day, 5-7 %%RMONTH Working Month, 5-7 %%RN Run Number, 5-6 %%RWDAY Working Day of the Week, 5-7 %%RWEEK Working Week, 5-7 %%RYEAR Working Year, 5-7, 5-8 %%SET %%variable AutoEdit Control Statement, 5-2 %%SET Control Statement Global Variable, 5-5 JCL Setup, 5-4, 5-21 Local Variable, 5-9 OCCUR NO, 6-41 SET VAR Parameter, 3-165 User-Defined Variable, 5-9 %%SIGN System Variable, 3-152
%%STEP Latest Program Step, 5-8 %%SUBSTR Function Example, 5-35 KSL, C-7 String Extraction, 5-26 %%TIME Example, 5-40, 5-43 Time of Day, 5-6 %%variable DO SET Statement, 3-63 %%WDAY Day of the Week, 5-7 %%WEEK Week of the Year, 5-7 %%YEAR System Year, 5-7, 5-8 %A1-%A9 KSL Variable, 8-11, 8-23 %CALLRC KSL Variable, 8-13, 8-23 Return Code, 8-17 %CRLINE KSL Variable, 8-23 %FINDRC KSL Variable, 8-23 %MSG KSL Variable, 8-23 %RC KSL Variable, 8-11, 8-23 %SCRCOL KSL Variable, 8-23
(
() Characters DO COND, 3-46 IN Parameter, 3-89 Prerequisite Condition, 3-87, 3-120
*
* Character CONFCAL Calendar, 3-35, 3-189 CTMTBUPD Utility, 6-81 D-CAT Parameter, 3-31
I5
Index
DO SYSOUT Statement, 3-72 JCL, 5-11 Job Graph, 2-84 Job Scheduling, 6-72 Masking, 2-3 MEMNAME Value, 4-19 ON PGMST Statement, 3-175 ON Statement, 3-110, 3-112 ON Statement CODES, 3-113 PRIORITY Parameter, 3-142 Quick Schedule Definition, 2-199 Remark Line, 5-10 SHOUT Parameter, 3-169 Subparameter Qualifier, 6-87 SYSOUT Parameter, 3-176, 3-178 * in DCAL Parameter CONFCAL Calendar, 3-35 * in WCAL Parameter CONFCAL Calendar, 3-189 * Symbol SCHEDULE TAG Field, 3-87 *$EJ Code ON Statement CODES, 3-114 **** Date Reference IN Parameter, 3-88 OUT Parameter, 3-121 Schedule Date, 3-47 ***** Code ON Statement CODES, 3-113 *.taskid MEMLIB Parameter, 3-100 *in-condition Quick Schedule Definition, 2-199 *NCT2 Code ON Statement CODES, 3-114 *P Field Conditions/Resources, 2-132 *Priority Conditions/Resources, 2-132 *range PGMST Parameter, 3-110 *REC0 Code ON Statement CODES, 3-114 *T Command JES Name, 3-67, 3-171
JES3, 3-101, 6-103 Started Task Under JES3, 6-103 *UKNW Status ON Statement, 3-112
.
. Character AutoEdit Variable, 5-12 .. Character AutoEdit Variable, 5-12
/
/ Character Date Format, 1-19 /* Symbol DO Statement Command, 2-124 //*CONTROLM Quick Submit Command, 6-16 //OUTPUT Statement SYSDATA Output Class, 1-21
?
? Character Masking, 2-3 Subparameter Qualifier, 6-85 ? Option Status Screen, 2-69, 2-84 ? Symbol Confirm Rerun Window, 2-99 Restart Window, 2-101
@
@ Character Hex Value, 2-2 Maybe Job Prefix, 6-21 MVS Restarts, 3-123, 6-21 User-Defined Variable, 5-9, C-4 @ Symbol Maybe Jobs, 6-21 @# MVS Restart, 3-123 @#-procstep.pgmstep OUT Condition, 3-124
I6
Index
@#procstep.pgmstep MVS Restart, 3-123
>
> Character DO Statement, 3-45 ON Statement CODES, 3-114 TIME Parameter, 3-186 > Symbol TIME UNTIL Field, 6-3
|
| Character DO COND Statement, 3-46 Hex Value, 2-2 Prerequisite Condition, 3-120
3 +
+ Sign Change Resource Window, 2-138 DO COND Statement, 3-47 Job Dependency Network, 2-108 Job Graph, 2-84 OUT Parameter, 3-121 Relative Calendar, 2-158 SHOUT Parameter, 3-170 33-Day Default Periodic Calendar, 2-160, 3-37
A
A Line Edit Command, A-3, B-3 A Option Manual Conditions, 2-141, 6-20 Parameter Prompting, 2-181 Status Screen, 2-70 A/O Parameter ON Statement, 3-111 Abend Capturing Option DUMP Command, 2-68 Abend Code ON Statement, 3-113 S*37, 3-166 Abend Code Recapture Rerun Confirmation, 2-99 Abend Report REP5ABND Utility, 8-9 ABENDED Status Show Screen Filter, 2-76 ABORT Command PA1 Key, 2-14 ACF2, 3-133 Action Keyword DO Statement, 3-44 Action Parameter DO Statement, 4-13 ACTION REQUIRED Parameter CONTROL-R Simulation, 2-203 ACTIVATE Option Status Screen, 2-70 Active Environment Screen Status Screen, 2-61
<
< Character ON Statement CODES, 3-114 <060> Character SHOUT Parameter, 3-170 <062> Character ON Statement, 3-112 SHOUT Parameter, 3-170 <196> Sign DO COND Statement, 3-47 SHOUT Parameter, 3-170 <MS>CHANGE<D> Command[CHANGE Command] Scheduling Definition, 2-46
=
==PERIODIC== Reserved String, 2-158 =6 Command PF06/PF18, 2-13, 2-21 =X Command Fast Exit, 2-11 Online Facility Exit, 2-11
I7
Index
ACTIVE IN ERROR Status Status Screen, 2-73 Active Jobs File, 2-173 CTMRAFL Report, 8-44 Daily Subsystem, 3-4 Description, 1-4 Display, 1-14 DO FORCEJOB Statement, 4-17 Job Scheduling, 6-2 MAXWAIT Parameter, 3-97 New Day Processing, 1-4 PRIORITY Parameter, 3-142 Restoration, 1-7 SYSDATA Deletion, 3-17 TASKTYPE Parameter, 3-183 Active Missions File D-CAT Parameter, 3-31 ACTIVE Status Group Entity, 3-122 Status Screen, 2-73 Active User Cancelling, 6-115 Active User List Displaying, 6-115 Ad Hoc Job Job Scheduling, 6-14 ADD Command Conditions/Resources, 2-134 ADD COND Command Conditions/Resources, 2-135 ADD COND Parameter Simulation, 7-5 Add Condition Option Why Screen, 2-86 ADD CONTROL Command Conditions/Resources, 2-135 Add Option Manual Conditions, 6-20 ADD Option Manual Conditions, 2-141 Parameter Prompting, 2-181, 2-189 ADD RESOURCE Command Conditions/Resources, 2-135 ADDED Field Manual Conditions, 2-140
ADD-GLOBAL Parameter CTMBLT Utility, 6-56 Adding Conditions/Resources, 2-134 Manual Conditions, 2-140 Addition Operator %%PLUS Operator, 5-22 ADDMNCND KSL Script, 8-10 ADDMNCND Utility Maybe Jobs, 6-21 ADJUST CONDITIONS Parameter Description, 3-12 Group Entity, 2-23, 2-45, 3-3, 6-21 AELIBNM Parameter CTMEXEC CLIST, 6-39 ALL Argument REFRESH Command, 2-111 All Info Display Type Status Screen, 2-65 ALLOC Command KSL, 8-19 AMODE 24 IOACND Utility, 6-99 AND/OR Parameter DAYS/WDAYS Parameter, 3-6, 3-36, 3-190 IN Parameter, 3-89 And/Or/Not Logic CMEM ON Statement, 4-34 And/Or/Not Parameter CMEM ON Statement, 4-33 ON DSNEVENT Statement, 4-37 ON JOBARRIV Statement, 4-40 ON JOBEND Statement, 4-42 ON STEP Statement, 4-45 AND/OR/NOT Subparameter CMEM Rule Definition, 2-122 ANYSTEP Value PGMST Parameter, 3-110, 3-112 APF Authorized New Day Processing, 6-12 APPL Parameter Description, 3-14 Example, 3-15
I8
Index
Testing AutoEdit Syntax, 6-45 UtilityCTMTBUPD, 6-82 Application Name APPL Parameter, 3-14 APPLICATION NAME Parameter AutoEdit Simulation, 2-170 Archiving SYSDATA, 3-16 Sysout, 3-76 ARG Parameter DO CTBRULE Statement, 3-50 ARGUMENTS Parameter CTB STEP Parameter, 3-29 ARROW Command Change Color, 2-58 ASK FOR EACH ONE Field CMEM Rule Order Window, 2-130 Conditions/Resources Confirmation, 2-137 Manual Conditions Confirmation, 2-142 Scheduling Confirmation, 2-54 Why Screen Confirmation, 2-87 Assembler Macro Instructions, 3-3 Assignment Line Variable Member, 5-10 Asterisk * Character;; Masking;, 5-10 ASVT Online Monitor, 6-114 AT Parameter CTB STEP Parameter, 3-29 ATTN Key AutoRefresh Mode, 2-18 AUTO Command AutoRefresh Mode, 2-18 AUTO SAVE DOCUMENTATION Field Entry Panel, 2-28 AUTO SAVE DOCUMENTATION Field Entry Panel AutoSave Documentation, 2-28 AUTOARC Parameter Utility CTMTBUPD, 6-82 AUTO-ARCHIVE Parameter Description, 3-16 Example, 3-18
AutoEdit Expression DO RULE Statement, 4-21 AutoEdit F, 5-25 AutoEdit Facility Boolean Logic, 5-16 Control Statement, 5-15, 6-40 JCL Modification, 5-1 JCL Setup, 1-5 Job Scheduling, 5-3, 5-28 KSL, C-1 Setting Variable Values, 5-21 Syntax Checking, 2-168, 5-27 AutoEdit Function %%$CALCDTE, 5-23 %%$GREG, 5-23 %%$JULIAN, 5-23 %%$LEAP, 5-24 %%$WCALC, 5-24 %%$WEEK, 5-25 %%$WEEKDAY, 5-25 %%CALCDATE, 5-26 %%SUBSTR, 5-26 AutoEdit Variables, 5-3 JCL Setup, 5-26 AutoEdit Operator %%MINUS, 5-22 %%PLUS, 5-3, 5-22 Boolean Logic, 5-16 KSL, C-6 AutoEdit Parameter CONTROL-R Simulation, 2-204 Dataset Cleanup, 2-206 OCCUR NO Suffix, 6-40 Parameter Prompting, 2-176, 2-180, 2-183, 2-187, 2-192, 6-29, 6-35 AutoEdit Resolution Rerun/Restart Window, 2-100 AutoEdit SET Statement JCL SET, 5-14 AUTOEDIT SIMUL Option Online Utilities Menu, 2-164 AutoEdit Simulation CTMAESIM Utility, 2-168 AutoEdit Statement %%RESOLVE OFF, 6-49
I9
Index
CMEM On Spool Job, 4-7 CTMEXEC CLIST, 6-40 Syntax Checking, 7-10 AutoEdit Symbol DO SYSOUT Statement, 3-76 AutoEdit Symbols Member Creation, 6-49 AutoEdit Syntax Checking, 2-168, 5-27 CTMAESIM Utility, 5-27 CTMSCIM Utility, 2-172 Testing, 2-168, 5-27 AutoEdit Variable %%SIGN, 3-152 CMEM, 4-15 Concatenation, 5-12 Description, 5-2 DO SET Statement, 3-64, 5-28 DO SET Statement, 3-63 DO SHOUT Statement, 3-67 DO Statement, 3-44 KSL Script, 8-4, 8-11 Linking, 5-11 MEMLIB Parameter, 3-101, 5-29 Multiple, 5-11 OVERLIB Parameter, 3-131, 5-29 Precedence, 5-14 Resolution, 5-11, C-4 SET VAR Parameter, 3-164 SETOLOC Statement, 8-4 Setting a Value, 3-63, 3-164, 5-14 System Variable, 5-5 Value Assignment, 5-14 Automatic Restart Restart ..., 3-54 Automatic Tape Adjustment Description, 1-11 RESOURCE Parameter, 3-150 WM2744 Wish, 1-11 Automatic Tape Adjustment Facility, 2-107 Automation Log MODE Parameter, 4-31 AUTOMATION LOG Option Primary Option Menu, 2-9
AUTOMATION OPTIONS IOA Primary Option Menu, 2-9 AutoRefresh Mode Global View Screen, 2-79 PA1 Key, 2-14 Screen Updating, 2-18 Status Screen, 2-62 View Graph Screen, 2-81 AutoSave Documentation, 2-28, 2-49 Average Statistics Line Statistics Screen, 2-106
B
B Line Edit Command, A-3, B-3 B Option Table List Screen, 2-30 BA Option Primary Option Menu, 2-8 BACKUP/MIGRATION Option Utilities Menu, 2-165 Balancing Specifications DO CTBRULE Statement, 3-50 BALANCING STATUS Option Primary Option Menu, 2-8 Basic Scheduling Parameters Group Entity, 2-45 Scheduling Definition, 2-38 Summary, 3-4 Batch Job TASKTYPE Parameter, 3-182 Batch Procedure CTMAESIM, 2-168 BK Option Primary Option Menu, 2-8 BLANK Value Parameter Prompting, 2-188 BM Option Primary Option Menu, 2-8 Boolean Logic Example, 5-43 JCL Setup, 5-16 BOTTOM Command Scrolling, 2-15 Bottom Line Primary/Alternate, 2-63
I 10
Index
BOTTOMLINE Command KSL, 8-17 BR Option Primary Option Menu, 2-8 Branching %%GOTO Control Statement, 5-15, 5-43 Browse Mode CMEM Rules, 2-116 DOCU/TEXT, 2-48 DOCU/TEXT Library, 3-79, 3-81 Job List Screen, 2-32 Year List Screen, 2-155 Zoom Screen, 2-91 BROWSE Option Calendar List, 2-154 CMEM Table List, 2-119 Table List Screen, 2-25, 2-30 BUT NOT FOUND n TIMES Status Screen, 2-72 BV Option Primary Option Menu, 2-8 Bypassing Event List Screen, 6-25 Table List Screen, 2-126
C
C Line Edit Command, A-2, B-2 C Option Job List Screen, 2-34 Status Screen, 2-69 Calendar Cross Reference, 8-10 DATES Parameter, 3-33 DAYS Parameter, 3-36 Deleting, 2-161 Example, 3-38, 3-193 Job Scheduling Plan, 2-60 Periodic, 1-10 Regular, 1-10 WDAYS Parameter, 3-190 Calendar Date System Variable, 5-6 CALENDAR DEF Option Primary Option Menu, 2-6
Calendar Definition Screen Description, 2-157 Exiting, 2-162 Fields, 2-158 Calendar Facility Adding a Year, 2-156 Calendar List, 2-154 Definition, 2-157 Description, 2-151 Entering, 2-152 Entry Panel, 2-153 Exiting, 2-162 Generation, 6-50 Inserting a Year, 2-156 Overview, 1-16 Periodic, 2-158 Scheduling Jobs, 1-9 Screens, 2-152 Year List, 2-156 Calendar Facility Entry Panel Exiting, 2-163 Fields, 2-153 CALENDAR Field Calendar Facility Entry Panel, 2-153 Calendar Generation CTMBLDAE Utility, 6-49 Calendar Input CTMBLDAE Utility, 6-49 CALENDAR LIBRARY Field Job Order Utility, 2-168 Calendar List Screen Description, 2-154 Exiting, 2-163 Options, 2-154 Year List Exit, 2-163 Calendar Name DCAL Parameter, 3-35 Calendar Name / Job Name Cross Ref CTMXRF Utility, 6-94 Calendar Option Primary Option Menu, 2-6 Calendar, Periodic Description, 2-158 Example, 2-159
I 11
Index
Calendar/Job Name Report CTMXRF Utility, 6-91 Calendars CONFCAL Calendar, 6-91 DCAL Calendar, 6-91 WCAL Calendar, 6-91 CALENDR Field Job Flow Report, 8-39 CALL Command KSL, 8-13 CALLIB Parameter CLIST CTMCJOBS, 6-15 CTMBLDAE Utility, 6-49 CALLMEM Command KSL, 8-11 CALMEM Parameter CTMBLDAE Utility, 6-49 CANCEL Command Calendar Definition, 2-162 CMEM Rule Definition, 2-126 Description, 2-16 Scheduling Definition, 2-51 Zoom Screen, 2-95 CATEGORY Command IOA Log Screen, 2-146 CATEGORY Field Job Scheduling Table, 6-17 CATEGORY Parameter. See D-CAT Parameter Utility CTMTBUPD, 6-82 CB Line Edit Command, A-2 CC Line Edit Command, A-2, B-2 CHANGE Option Conditions/Resources, 2-136, 2-137 CHANGE RESOURCE Parameter Simulation, 7-5 CHANGRES KSL Script, 8-10 Character Hex Value, 2-2 Character Masking Masking, 2-3 CHART Parameter CTMRFLW Report, 8-35 CHECKCND KSL Script, 8-10
Checkpointing New Day Processing, 6-7, 6-10 CICS CMEM On Spool Job, 4-3 Environment, 2-1, 3-133 Online Monitor, 6-113 OWNER Parameter, 3-133 PF06/PF18, 2-13 CL Line Edit Command, A-2, B-2 Class Allocation, 5-39 DO SYSOUT Statement, 3-70 Sysout, 3-72, 3-178 SYSOUT Parameter, 3-176 CLEANUP Option Online Utilities Menu, 2-164 Cleanup Parameter Dataset Cleanup, 2-206 CLEANUP Status Status Screen, 2-71 CLEAR Command KSL, 8-12 CLIST Activation, 2-20 CLIST CTMCAES AutoEdit Syntax Testing, 2-168 CLIST CTMCAMNU Parameter Prompting, 2-184 CLIST CTMCDOCU DOCU/TEXT Product, 2-209 CLIST CTMCFMNU Parameter Prompting, 2-177 CLIST CTMCSIM Simulation/Tape Pull, 2-172 CLIST CTMEXEC Parameter Prompting, 6-38, 6-39 CLIST CTMFETCH Parameter Prompting, 6-37 CLIST CTMJBINT End User Job Order, 2-202 Job Ordering, 6-14 CLIST CTMJOBRQ Job Ordering, 2-167, 6-14 CLIST CTMPROMPT Quick Schedule Definition, 2-194
I 12
Index
CLIST CTMQUICK Quick Schedule Definition, 2-195 CLIST CTRCCLN Dataset Cleanup, 2-205 CLIST CTRCSIM CONTROL-R Simulation, 2-203 CLIST IOACCND Prerequisite Condition Utility, 2-166 CLIST IOAUTIL Online Utilities, 2-164 CLOSEFILE Command KSL, 8-19 Closing Exiting, 2-150 CMEM DEFINITION Option Primary Option Menu, 2-6 CMEM Entry Panel Exiting, 2-128 CMEM Facility Actions, 4-2 AutoEdit Statement, 4-7 AutoEdit Variables, 4-15 CICS Job, 4-3 CONTROL-M Monitor, 6-100, 6-101 CONTROL-O, 1-9, 6-106 Deactivating, 6-106 Description, 4-1 DO FORCEJOB Statement, 4-17 Event Types, 1-9, 4-1 External Events, 1-9 Forced Job, 4-5, 4-17 FTP Support, 4-7 JES Deactivation, 6-105 Monitor, 6-107 On Spool Job, 1-9, 4-3 Operator Commands, 6-108 Overview, 1-14 Rule Management, 4-2 Security Cache, 6-111 Sleeping Interval, 6-110 WTO Descriptor Codes, D-2 CMEM List DACTMLST DD Statement, 6-108 CMEM Message Type Show Screen Filter, 2-148
CMEM Monitor Replacing, 6-107 Sleeping Interval, 6-101 CMEM On Spool Job On Spool Job, 4-18 CMEM Option Primary Option Menu, 2-6, 2-115, 2-117 CMEM Rule And/Or/Not Logic, 4-34 Browsing, 2-116 Comments, 2-124 Components, 4-4 CONTROL-O Rule, 4-9 Creation, 2-116 Dataset Event, 4-1, 4-35 Definition, 4-8 DESCRIPTION Parameter, 4-11 Displaying, 6-109 DO COND Statement, 4-2, 4-14 DO FORCEJOB Statement, 4-2, 4-17 DO RULE Statement, 4-21 DO SHOUT Statement, 4-24 DO Statement, 4-2, 4-9, 4-13 DO STOPJOB Statement, 4-2, 4-27 Editing, 2-117 GROUP Parameter, 4-29 Job Arrival, 4-40 Job Scheduling Definition, 4-5 Loading, 6-107 Management, 4-2 MODE Parameter, 4-31 ON DSNEVENT Statement, 4-1, 4-3, 4-33, 4-35 ON JOBARRIV Statement, 4-1, 4-4, 4-33, 4-40 ON JOBEND Statement, 4-1, 4-33, 4-42 On Spool Job, 4-3 ON Statement, 4-33 ON STEP Statement, 4-1, 4-33, 4-44 OWNER Parameter, 4-48 Parameters, 4-8 Prerequisite Condition, 4-2, 4-14 Screen, 4-8, 4-12, 4-26, 4-28, 4-32, 4-39, 4-41, 4-43, 4-51 Simulation, 4-31 Trace Operations, 6-110
I 13
Index
CMEM Rule Definition Commands, 2-124 Description, 2-121 Editing, 2-125 Entry Panel, 2-118 Exiting, 2-126 CMEM Rule Facility Description, 2-115 Exiting, 2-126 ISPF Pack Option, 2-115 Screens, 2-115 TEST Mode, 4-31 CMEM Rule List Browse Mode, 2-119 Exiting, 2-127 Options, 2-120 Screen, 2-118, 4-11 CMEM Rule Table Conversion, 4-1 Creation, 2-116 Deactivating, 6-109 Deletion, 2-128 List, 2-119 Ordering, 2-129, 4-2 REBUILD Option, 6-108 CMEM Security Cache, 6-111 RUNTSEC Parameter, 4-50 CMEM Sleeping Interval Modifying, 6-110 CMEM Table Ordering, 2-117 CMEM Table List Exiting, 2-128 Options, 2-118 Statistics, 2-118 CMNT Command CMEM Rule Definition, 2-124 CNGOVRLB KSL Script, 8-10 CODE Criteria Screen Filter, 2-148 CODE Field Log Screen, 2-145
CODES Parameter ON Statement, 3-111, 3-113 Collection WorkLoad Implementation, 6-24 Color Support Box Color, 2-58 Graphic Jobflow, 2-57 Job Graph, 2-82 Online Facility, 2-2 Status Screen, 2-62 View Graph Screen, 2-81 COLUMN Range %%RANGE Control Statement, 5-20 Combinatorial Logic CMEM ON Statement, 4-34 Command Line Screen Layout, 2-12 Commands =6, 2-13, 2-21 ABORT, 2-14 ADD COND, 2-135 ADD CONTROL, 2-135 ADD RESOURCE, 2-135 ADD Resources, 2-134 AUTO, 2-18 BOTTOM, 2-15 CANCEL, 2-16, 2-51, 2-95, 2-126 CATEGORY, 2-146 Change Color, 2-58 CMEM Rule Definition, 2-124 CMNT, 2-124 Conditions/Resources Screen, 2-135 CPUID, 2-67 CTMQSB, 6-15, 6-16 CTMTTRA, 2-21 DATA, 2-33 DESC, 2-33, 2-67 DISPLAY, 2-63, 2-66 DOC, 2-48 DOWN, 2-13, 2-15 DUMP, 2-68 EDIT, 2-47, 2-124, 2-125, A-1 END, 2-13, 2-51, 2-79, 2-126, 2-150 Exit Online Facility, 2-11 FIND, 2-13, 2-16, 2-57
I 14
Index
GROUP, 2-67, 2-146 HELP, 2-13, 2-17 HISTORY, 2-66, 2-112 ISPF, 2-19 ISPF SPLIT, 2-13 JCL, 2-26 JES HOLD, 2-71 JES2, 6-103 Job Dependency, 2-111 Job Dependency Network, 2-111 JOBSTART, 2-106 JOBSTAT, 2-67, 2-105, 2-107 KEYS, 2-13, 2-19, 2-105 KSL, 8-3, 8-12 L Parameter Prefix, 2-19, 2-180, 2-182, 2-188, 2-192 Line Editing, A-2 LIST, 6-46 LOCATE, 2-15, 2-101 Location, A-3 Log Screen, 2-145 Move, A-3 NEW COND, 2-143 NEXT, 2-124 Online Facility, 2-13 OPT, 2-66 ORDERID, 2-67 PREV, 2-124 PRINT, 2-14, 2-19 Quick Submit, 6-15, 6-16 RBAL, 2-68 REFRESH, 2-14, 2-18, 2-68, 2-79, 2-108, 2-111 RESET, 2-13, 2-16, 2-52, 2-79, 2-127, 2-150, 2-163, 2-200, A-1 Rule Editing, B-1 SAVE, 2-95 Scheduling Definition, 2-46 Scrolling, 2-15 SELECT, 2-24, 2-31 SHOW, 2-13, 2-67, 2-74, 2-145 SHPF, 2-14 SMn, 6-102 SORT, 2-33 SPLIT, 2-13, 2-19 Status Screen, 2-66
SUBMIT, 6-46 SUBSCAN, 6-46 SWAP, 2-19 Sysout Viewing, 2-104 Table List Screen, 2-31 TOP, 2-15 TSO, 2-20 TSO CTMTTRA, 2-21 UP, 2-13, 2-15 Utilities Transfer, 2-13 VG, 2-67, 2-81 VIEW, 2-67, 2-79 VIEW GRAPH, 2-67, 2-81 VIEWALL, 2-103 Comment CMEM Rule Definition, 2-124 Comparison Operator AutoEdit Logic, 5-16 COM-PLETE Color Support, 2-2 Environment, 2-1 Online Monitor, 6-113 PF06/PF18, 2-13 Components CONTROL-M, 1-3 Compression Job CONTROL Parameter, 3-26 Computer Allocation Example, 5-39 Computer ID Started Task, 3-101 Concatenation %% Symbol, 5-5, 5-13 AutoEdit Variable, 5-12 Logic, 5-11 COND Field Conditions/Resources, 2-133 COND Type Event List Operation, 6-26 COND TYPE Parameter, 6-28 COND/RES Option Primary Option Menu, 2-6 Condition Code CTMBLT Utility, 6-60
I 15
Index
ON Statement, 3-113 Condition Code Recapture Restart Confirmation, 2-99 CONDITION DATE Field Event Definition, 6-28 Prerequisite Condition Utility, 2-166 CONDITION Field Parameter Prompting, 2-180 CONDITION Name Manual Conditions, 2-140 Condition Name Cross Ref CTMXRF Utility, 6-95 CONDITION NAME Field Event Definition, 6-28 Prerequisite Condition Utility, 2-166 Condition Names Report CTMXRF Utility, 6-91 Condition Parameter DO COND Statement, 4-14 CONDITION/RESOURCE Field Conditions/Resources, 2-132 Conditional Processing DO Statement, 3-9 IF, THEN, ELSE, 5-16, 5-43 ON Statement, 3-9 Conditions/Resources Add/Check/Delete Utility, 2-166 Date References, 6-85 Delete Option, 2-136 Description, 2-131 Fields, 2-132 Forecasting, 7-1 Handling, 1-6, 1-25, 2-131 IOACND Utility, 6-97 IOALDNRS Utility, 6-19 Manual Conditions, 2-143 Options, 2-136 Overview, 1-15 Parameters, 6-84 Partial Name Changes, 6-87 Restoration, 1-7 Retrieval Criteria, 2-133 Simulation and Forecasting, 7-2 Updating, 6-86
condopt Parameter DO COND Statement, 4-14 CONFCAL Calendar, 6-91 CONFCAL Calendar Schedule Validation, 3-6 Scheduling Logic, 3-7 CONFCAL Parameter Description, 3-19 Example, 3-22 MINIMUM Parameter, 3-106 PDS Parameter, 3-135 Periodic Calendar, 3-21 Utility CTMTBUPD, 6-82 Configuration Table AutoEdit Statement, 6-41 CONFIRM Field CMEM Rule Table Order, 2-130 Conditions/Resources, 2-137 Manual Conditions, 2-142 Rerun Confirmation Window, 2-97 Restart Confirmation Window, 2-98 Scheduling Confirmation, 2-54 Why Screen Confirmation, 2-87 Zoom Screen, 2-92 CONFIRM Option Status Screen, 2-69 CONFIRM Parameter Description, 3-23 DO IFRERUN Statement, 3-55 Example, 3-24 CONFIRM Parameter (CTM) Utility CTMTBUPD, 6-82 Confirm Rerun Window Status Screen, 2-96 Confirm Restart Window Status Screen, 2-97 Confirm Scheduling Window Status Screen, 2-96 Confirmation Window CMEM Rule Table, 2-130 Customization, 2-1 DO IFRERUN Statement, 3-55 Force OK, 2-113 Manual Conditions, 2-141
I 16
Index
Manual Scheduling, 2-53 Why Screen, 2-86 Zoom Screen, 2-95 CONNECT DIRECT File Transfer Example, 4-16 CONNECT DIRECT Support Dataset Event, 6-25 CONTDAY Started Task New Day Procedure, 6-101 CONTROL-xe "CONTROL-D:Options" Options, 2-8 CONTROL Field Conditions/Resources, 2-133 CONTROL Parameter Description, 3-25 Example, 3-26 Logic, 3-26 Control Resource Adding, 2-134 Conditions/Resources, 2-131 Critical Path Priority, 3-142 Cross Reference List, 8-33, 8-42 Definition, 1-25 IOACND Utility, 6-98 Job Flow Report, 8-33 Runtime Criteria, 1-6 Show Screen Filter, 2-78 CONTROL Resource Manual Addition, 2-135 Control Statement AutoEdit, 5-15 CONTROL-B CTB STEP Parameter, 3-29 DO CTBRULE Statement, 3-50 Options, 2-8 Primary Option Menu, 2-7 Product Description, 1-2 CONTROL-D D-CAT Parameter, 3-31 Options, 2-8 Primary Option Menu, 2-7 Product Description, 1-1 CONTROL-D/Image Product Description, 1-1
CONTROL-D/Page On Demand Product Description, 1-1 CONTROL-D/PC Product Description, 1-1 CONTROL-I/2000 Options, 2-8 Primary Option Menu, 2-7 Product Description, 1-2 CONTROL-M Concepts, 1-17 Implementation, 6-1, 6-7 Maintenance, 6-1 Operations Guide, 6-100 Overview, 1-3 Parameter Prompting, 2-177 Primary Option Menu, 2-7 Product Description, 1-1 Sample Components, 6-4 Utilities, 6-43 CONTROL-M Monitor Activating, 6-100 Description, 1-4 Internal Error, 6-103 JES Commands, 6-103 Online Monitor, 6-113 Operations Guide, 6-100 Post-processing, 1-8 QNAME, 6-100 Shutting Down, 6-100 Simulation Facility, 2-172 Sleeping Interval, 6-101 Started Task, 6-100 CONTROL-M Repository. See Repository CONTROL-M Status Field Status Screen, 2-64 CONTROL-M/WorkLoad CONTROL-M Support, 1-12 Implementation, 6-23 Options, 2-8 PIPE Parameter, 3-137 Primary Option Menu, 2-7 Product Description, 1-2 Rule Def Option, 2-8 System-Related Considerations, 6-24
I 17
Index
Control-O Options, 2-9 CONTROL-O %%$ARGS System Variable, 4-22 Automation Log, 4-31 CMEM Facility, 1-9, 6-106 CMEM Rule, 4-2, 4-9 DO SHOUT Statement, 4-24 MODE Parameter, 4-31 Primary Option Menu, 2-7 Product Description, 1-1 Rule Invocation, 4-2 Shout Facility, 1-9, 4-9 CONTROLO Parameter CTMRFLW Report, 8-35 CONTROL-O Rule DO RULE Statement, 4-21 CONTROL-O/COSMOS Options, 2-9 Product Description, 1-1 CONTROL-O/PC Product Description, 1-1 CONTROL-R CTRCSIM Utility, 2-203 Dataset Cleanup, 2-207 History Jobs File, 1-7, 6-3 Options, 2-7 Product Description, 1-1 Rerun Confirmation, 2-97 Restart, 1-20, 2-72, 3-54 Restart Window, 2-97 Simulation, 2-203 CONTROL-R Dataset Cleanup Online Utilities Menu, 2-205 Restart Confirmation Window, 2-207 CONTROL-R Restart DO IFRERUN Statement, 3-54 Job Status, 2-72 CONTROL-R SIMUL Option Online Utilities Menu, 2-164 CONTROL-R Simulation Panel CTRCSIM Utility, 2-203 CONTROLR Step, 2-207
CONTROL-T Options, 2-9 Primary Option Menu, 2-7 Product Description, 1-2 CONTROL-T SIMUL Option Utilities Menu, 2-165 CONTROL-V Primary Option Menu, 2-7 Product Description, 1-1 Copy Commands Edit Environment, A-2, B-2 Copy Option Job List Screen, 2-34 COPY Option Job List Screen, 2-26 Copying Jobs, 2-56 Sysout, 3-71, 3-73, 3-177, 3-180 COSMOS STATUS Option Primary Option Menu, 2-9 COUNT Parameter Change Resource Window, 2-138 CPU Field Status Screen, 2-65 CPU ID Version Information Window, 2-10 CPU Time Field Statistics Screen, 2-106 CPU Time, Average Statistics Screen, 2-106 CPU Time, Group Statistics Screen, 2-106 cpuid MEMLIB Parameter, 3-100 CPUID Command Status Screen, 2-67 CPU-ID Field Zoom Screen, 2-92 CPUS Installation Parameter CTMPARM Library, 6-103 CREATE Field Exit Option Window, 2-52
I 18
Index
CREATRES KSL Script, 8-10 Crictical Path Jobs Deleting, 2-88 Critical Path Deleting a Job, 2-88 Job Dependency, 1-26 PRIORITY Parameter, 3-142 Resource Allocation, 1-26 Cross Memory Interface Online Monitor, 2-1, 6-114 Cross Reference Calendar, 8-10 CTMRFLW Report, 8-33 Prerequisite Condition, 8-10, 8-41 Quantitative Resource, 8-43 Cross Reference Reports CTMXRF Utility, 6-91 CRSR Scrolling Amount, 2-15 CS Line Edit Command, A-2, B-2 CST Task Type Show Screen Filter, 2-77, 2-148 CTB STEP Parameter Description, 3-29 Example, 3-30 CTM2RUL Utility CMEM Table Conversion, 4-1 CTMAESIM Utility AutoEdit Syntax, 2-168, 5-27 Description, 6-45 LIST Command, 6-46 Summary, 6-43 CTMAJO Program Job Ordering, 6-17 Work Flow, 6-17 CTMBGRP Utility CTMBLT, 6-60 Group Scheduling Table, 6-60 Summary, 6-43 CTMBLDAE Utility CTMRCAL Calendar, 6-76 Description, 6-49 Example, 6-51 Summary, 6-43
CTMBLT Utility Assembler Macro, 3-3 Called From Another Program, 6-58 Description, 6-54 Example, 6-60 Job Scheduling, 6-57 Summary, 6-43 CTMBUPD Utility Summary, 6-43 CTMCAES CLIST CTMAESIM Utility, 5-27 TSO Command, 2-168 CTMCAES Option CTMAESIM Utility, 5-27 CTMCAJF Utility AUTO-ARCHIVE Parameter, 3-17 Summary, 6-43 CTMCAMNU Option Parameter Prompting Entry Panel, 2-176 CTMCFMNU Option Parameter Prompting Entry Panel, 2-176 CTMCLRES IOACLRES, 6-4 Maintenance Job, 6-4 CTMCND Procedure Example, 6-99 IOACND Utility, 6-97 CTMCSIM CLIST TSO Command, 2-172 CTMDAILY Procedure User Daily Job, 6-4, 6-12 CTMDEST Destination Table Loading, 6-112 CTMEXEC CLIST Example, 6-40 Parameter Prompting, 6-37 CTMEXEC Option Parameter Planning, 2-190 Parameter Printing, 2-184 CTMFETCH CLIST Parameter Prompting, 6-37 CTMFETCH Option Parameter Prompting, 2-184, 2-189
I 19
Index
CTMFRCKP Utility Summary, 6-43 CTMFRJNL Utility Summary, 6-43 CTMFRM Program New Day Processing, 6-14 CTMILU Program CTMDAILY Procedure, 6-12 CTMILY Program New Day Processing, 6-12 CTMJBINT CLIST TSO Command, 2-202 CTMJBINT Utility End User Job Order, 2-202 Job Ordering, 6-14 CTMJDS Procedure CTMRJDS Report, 8-57 CTMJDSN CLIST TSO Command, 2-208 CTMJDSN Utility Job Dataset List, 2-208 CTMJOB Program Job Ordering, 6-14 CTMJOB Utility Description, 6-71 Example, 6-74 Summary, 6-43 CTMJOBRQ CLIST TSO Command, 2-167 CTMJOBRQ Utility Job Order Request, 2-167 Job Ordering, 6-14 CTMJSA Utility Statistics File Update, 2-105 Summary, 6-43 CTMJTXRF Utility Job Name / Table Name Xref Report, 6-92 CTMLDNRS IOALDNRS, 6-4 CTMLDNRS Utility Maintenance Job, 6-4 CTMQSB Command CTMX010 User Exit, 6-17 Job Ordering, 6-16
CTMQSC Application CTMAJO Program, 6-17 CTMQUICK CLIST TSO Command, 2-194 CTMQUICK Option Online Utilities Menu, 2-195 CTMQUICK Utility Example, 2-201 Quick Schedule Definition, 2-194 Tables, 2-24 CTMRAFL Report Comparison with CTMRPFL, 8-49 Description, 8-44 JCL, 8-44 CTMRCAL Utility Description, 6-76 Example, 6-77 Summary, 6-43 CTMRELRS Utility Description, 6-78 Example, 6-79 Summary, 6-43 CTMRFLW Report Comparison with CTMRPFL, 8-49 Example, 8-38 JCL, 8-34 JCL, 8-37 Parameters, 8-34 CTMRFLW Report Description, 8-33 CTMRJDS Report Dataset Cross Reference, 8-57 CTMRLR Program Example, 6-79 Quantitative Resource Release, 6-78 CTMRNSC Report Description, 8-51 Example, 8-53 JCL, 8-51 Parameter, 8-51 CTMROGR Report Description, 8-53 JCL, 8-54 Parameters, 8-54
I 20
Index
CTMRPFL Report Description, 8-49 CTMRPLN Report Comparison with CTMRPFL, 8-49 Description, 8-45 JCL, 8-46 Parameters, 8-45 CTMRSTR Utility Restoration, 1-7 Summary, 6-43 CTMSCALL KSL Script, 8-9 CTMSCH DD Statement, 6-88, 6-92 CTMSIM Procedure Simulation Procedure, 7-2 CTMSIM Utility Summary, 6-43 CTMTAPUL Procedure Tape Pull List, 7-1, 7-10, 7-11 CTMTAPUL Utility Summary, 6-43 CTMTBUPD Utility JCL, 6-88 Job Scheduling Table Update, 6-80 CTMWORK SYSOPT Variable, 3-50 CTMX001 Exit CTMQSB Command, 6-16 CTMX002 Exit CTMAESIM Utility, 5-27 MEMLIB Parameter, 3-101 Parameter Prompting, 6-41 RESOURCE Parameter, 3-152 Simulation, 7-7 CTMX003 Exit Simulation, 7-7 CTMX004 Exit Quantitative Resources, 6-111 RESOURCE Parameter, 3-152 CTMX004 User Exit Scheduling Algorithm, 3-153 CTMX010 User Exit CTMQSB Command, 6-17 CTMX013 Exit Statistics Screen, 2-106
CTMX2PPF Member IOA SECUDATA Library, 6-41 CTMXREF Utility Control Statements, 6-92 CTMXRF Report Condition Name Cross Ref, 6-95 CTMXRF Utility Calendar Name / Job Name Cross Ref, 6-94 Description, 6-91 Due Out Time / Job Name Cross Ref, 6-95 From Time / Job Name Cross Ref, 6-95 JCL, 6-93 Job Name / Table Name Cross Ref, 6-94 Job Name Cross Ref, 6-95 Library Name / Job Name Cross Ref, 6-96 Resource Name / Job Name Cross Ref, 6-94 Schedule Tag / Job Name Cross Ref, 6-95 Summary, 6-43 Until Time / Job Name Cross Ref, 6-95 CTRCCLN CLIST CONTROL-R Dataset Cleanup, 2-205 TSO Command. See CTRCCLN Utility Dataset Cleanup, 2-205 CTRCSIM CLIST TSO Command, 2-203 CTRCSIM Utility CONTROL-R Simulation, 2-203 CURSOR Command KSL, 8-12 Customizing MAINDAY Table, 6-10 Online Facility, 2-1 Options, 1-13 CYC Task Type Show Screen Filter, 2-77, 2-148 Cyclic Job AUTO-ARCHIVE Parameter, 3-17 CONFIRM Parameter, 3-23 INTERVAL Parameter, 3-95 Job Flow Report, 8-39
I 21
Index
New Day Procedure, 6-3 TASKTYPE Parameter, 3-182 Cyclic Jobs Force OK, 2-113 Cyclic Started Task TASKTYPE Parameter, 3-182
D
D JOB Message Type Show Screen Filter, 2-148 D Line Edit Command, A-2, B-2 D Option Job List Screen, 2-34 Parameter Prompting, 2-181 Status Screen, 2-69, 2-88 Table List Screen, 2-31 Year List Screen, 2-156 DAACTLOG DD Statement MODE Parameter, 4-31 DACAL DD Statement Calendar Library, 6-76 DACALL DD Statement IOARKSL Procedure, 8-2 DACKPTIN DD Statement Simulation Active Jobs File, 7-3 Tape Pull List, 7-11 DACKPTOU DD Statement Simulation Active Jobs File, 7-6 DACTMLST DD Statement CMEM Rule Table, 6-108 DAFLWPRM DD Statement CTMRFLW Report, 8-34 DAGLOBAL Statement %%GLOBAL Control Statement, 5-15 PARAMETER LIBRARY Parameter, 5-28 Daily AutoEdit Member Parameter Prompting, 6-37 Daily Checkpointing Checkpointing, 6-7 Daily JCL Library Allocation, 6-42 Deletion, 6-41 Daily JLC Library Parameter Prompting, 6-36
Daily Plan Parameter Prompting, 2-191, 6-36 Daily Prompting Table Daily Table, 2-182 Daily Scheduling Table Parameter Prompting, 6-36 Daily Subsystem DCAL Calendar, 3-35 D-CAT Parameter, 3-31 Issue a Job Order, 2-166 Daily Table Table Selection Screen, 2-182, 6-33 DAILYPRD User Daily Job, 6-4, 6-7 DAILYSYS User Daily Job, 6-4 DAINPRM DD Statement CTMBLT Utility, 6-54, 6-60 CTMTBUPD Utility, 6-88 DAJCLOUT DD Statement JOB/SCAN - DOCU/TEXT, 7-12 Tape Pull List, 7-11, 7-12 DAJOB DD Statement CTMJOB Utility, 6-71 User Daily Job, 6-10 DAKSLOUT DD Statement IOARKSL Procedure, 8-2 DAKSLPRM DD Statement IOARKSL Procedure, 8-2 DAKSLREP DD Statement KSL Script, 8-2 DALIB DD Statement MEMLIB Parameter, 3-100 DALOGIN DD Statement Tape Pull List, 7-11 DALOGOUT DD Statement Simulation Log File, 7-6 DAMSG DD Statement CTMBLT Utility, 6-60 DANRES DD Statement Simulation, 7-9 DANSCPRM DD Statement CTMRNSC Report, 8-51 DANSINC DD Statement Simulation, 7-9
I 22
Index
DAOGRPRM DD Statement CTMROGR Report, 8-53 DAPLNJOB DD Statement CTMRCAL Utility, 6-77 DAPLNPRM DD Statement CTMRPLN Report, 8-45 DARELIN DD Statement CTMRELRS Utility, 6-78 DAREPOUT DD Statement Tape Pull List, 7-12 DARESF DD Statement Simulation Conditions/Resources, 7-3 Simulation Conditions/Resources, 7-9 DASIM DD Statement CTMAESIM Parameters, 6-45 DASIMOUT DD Statement Simulation Messages, 7-6 DASIMPRM DD Statement Simulation Parameter, 7-4 DASINC DD Statement Simulation, 7-9 DASTAT DD Statement Automatic Tape Drive Adjustment, 6-59 Simulation Statistics, 7-6 DASUBMIT DD Statement AutoEdit Simulation, 2-170 CTMAESIM Utility, 5-28 Emergency Execution, 5-28 DATA Command Job List Screen, 2-33 DATA Format Job List Screen, 2-33 DATA Parameter IOADFLTC Member, 5-18, 5-19 Database Update IN Parameter, 3-93 DATABERR DD Statement CTMBLT Utility, 6-60 DATAPNAM DD Statement Tape Pull List, 7-12 Dataset Cleanup CONTROL-R, 2-205 Dataset Disposition ON DSNEVENT Statement, 4-35
Dataset Event CONNECT DIRECT Support, 6-25 IOACDDR REXX Procedure, 6-25 ON DSNEVENT, 4-1, 4-3, 4-33 ON DSNEVENT Statement, 4-35 DATASET Event CMEM, 4-1 DO FORCEJOB Statement, 4-18 Dataset Job Cross Reference CTMRJDS Report, 8-57 Dataset Name CMEM, 4-3 Date Calculation %%$CALCDATE Function, C-6 %%$CALCDTE Function, 5-35 Date Control Record Checkpointing, 6-7, 6-10 Format, 6-10 New Day Processing, 6-2 PARM Library, 6-5, 6-10 PDSE-Type Library, 6-8 User Daily Job, 6-7 Date Definition Overview, 1-18 Date Field Why Screen Confirmation, 2-87 DATE Field Conditions/Resources, 2-132 Job Order Execution History, 2-103 Log Screen, 2-145 Simulation/Tape Pull, 2-173 Date Format Definition, 1-19 Date Masking IOACND Utility, 6-97 DATE Parameter CTMEXEC CLIST, 6-39 CTMFETCH CLIST, 6-38 DO FORCEJOB Statement, 4-17 Date Range Log Screen, 2-145 DATE Range Job Scheduling Plan Screen, 2-60 Log Screen, 2-145 Manual Conditions, 2-141
I 23
Index
Date Reference DO COND Statement, 3-47, 4-14 Generic, 3-91 IN Parameter, 3-87, 3-94 January 1st, 1-24, 3-47, 4-14 OUT Parameter, 3-120, 3-130 Prerequisite Condition, 1-23, 3-48 STAT, 1-24, 3-47, 4-14 Zoom Screen, 2-93 DATE Reference Manual Conditions, 2-140 Date References Conditions/Resources, 6-85 Date Standards Overview, 1-19 Date Updated Field Parameter Prompting, 2-183 Date Variable Example, 5-30 JCL Setup, 5-6 DATEMEM Calendar WCAL Parameter, 3-189 DATEREC Date Control Record, 6-5 DATERECU Date Control Record, 6-5 dateref Parameter DO COND Statement, 4-14 Dates Field Calendar Definition, 2-158 DATES Parameter DAYS Parameter, 3-38 Description, 3-33 Example, 3-34 MINIMUM Parameter, 3-106 PDS Parameter, 3-135 Utility CTMTBUPD, 6-82 DATES Range Field Conditions/Resources, 2-134 DAUNITDF DD Statement Automatic Tape Drive Adjustment, 6-59 DAXREF File CTMRCAL Utility, 6-76 DAXRFIN DD Statement CTMXRF Utility, 6-91
Day of the Week First, 3-189 WDAYS Parameter, 3-189 DAYJCLB Parameter CTMFETCH CLIST, 6-39 DAYS Parameter CONFCAL Parameter, 3-21 DATES Parameter, 3-33 DCAL Field, 3-6 Description, 3-35 Example, 3-38 Format, 3-35, 3-36 Logic, 3-38 MINIMUM Parameter, 3-106 Negative Value, 3-38 PDS Parameter, 3-135 Scheduling Logic, 3-6 Utility CTMTBUPD, 6-82 DAYTBLB Parameter CTMEXEC CLIST, 6-39 CTMFETCH CLIST, 6-38 DB Line Edit Command, A-2 DB VARIABLE DEF Option Primary Option Menu, 2-8 DCAL Calendar, 6-91 DCAL parameter Periodic Calendar, 3-37 DCAL Parameter Calendar Name, 3-35 Calendar Type, 3-38 DATES Parameter, 3-33 DAYS Parameter, 3-6 MAXWAIT Example, 3-99 Non-Periodic Calendar, 3-36 Utility CTMTBUPD, 6-82 D-CAT Field Ignored by CTMQSB Command, 6-17 D-CAT Parameter Category E. See D-CAT Parameter Description, 3-31 Example, 3-32 DD Line Edit Command, A-2, B-2 DD Statement DAACTLOG, 4-31
I 24
Index
DACALL, 8-2 DACKPTIN, 7-3, 7-12 DACKPTOU, 7-6 DACTMLST, 6-108 DAFLWPRM, 8-34 DAINPRM, 6-54, 6-60 DAJCLOUT, 7-12 DAJOB, 6-10 DAKSLOUT, 8-2 DAKSLPRM, 8-2 DAKSLREP, 8-2 DALIB, 3-100 DALOGIN, 7-12 DALOGOUT, 7-6 DAMSG, 6-60 DANSCPRM, 8-51 DAOGRPRM, 8-53 DAPLNJOB, 6-77 DAPLNPRM, 8-45 DARELIN, 6-78 DAREPOUT, 7-12 DARESF, 7-3 DASIM, 6-45 DASIMOUT, 7-6 DASIMPRM, 7-4 DASTAT, 7-6 DASUBMIT, 2-171, 5-28 DATABERR, 6-60 DATAPNAM, 7-12 PRTDBG, 2-14 STEPLIB, 6-60 TAPULIN, 7-12 TAPULOUT, 7-12 DD Statement DACAL, 6-76 Deadline Adjustment Job Flow, 1-27 DEADLINE Argument REFRESH Command, 2-111 Deallocation Quantitative Resource, 6-78 Debugging TRACE ON Parameter, 8-2 Decollating Mission D-CAT Parameter, 3-31
DECOLLATING Option Utilities Menu, 2-165 Default Display Type Job Dependency Network, 2-109 Job Order Execution History, 2-103 Status Screen, 2-64 DEFAULT Field Parameter Prompting, 2-188 Default Filter Log Screen, 2-146 Status Screen, 2-74 DEFAULT Filter Status Screen, 2-67 DEFAULT STATUS Field Parameter Prompting, 2-193 Define Parameters and Conditions Exiting, 2-181 Fields, 2-180 Options, 2-181 Screen, 2-180 Type 1 Option 1, 2-178 Define Parameters in Master Plan Fields, 2-187 Options, 2-189 Screen, 2-187 DEL Option Status Screen, 2-69 DELARCH Step New Day Processing, 6-14 DELCNDAL KSL Script, 8-10 Delete Command Edit Environment, A-2 Delete Commands Edit Environment, B-2 DELETE COND Parameter Simulation Parameter, 7-5 Delete Confirmation Window Status Screen, 2-89 Table List Screen, 2-56 Delete Option Status Screen, 2-88 Table List Screen, 2-56 DELETE Option Calendar List, 2-154
I 25
Index
CMEM Rule List, 2-120 CMEM Table List, 2-119, 2-128 Conditions/Resources, 2-136 Event List Screen, 6-26 Job List Screen, 2-26, 2-34 Parameter Prompting, 2-181, 2-189 Table List Screen, 2-26, 2-31 Year List, 2-156 DELETED Status Show Screen Filter, 2-77 Status Screen, 2-73 Deleting Calendar, 2-161 CMEM Table, 2-128 Crictical Path Jobs, 2-88 DO Statement, 3-45 Manual Conditions, 2-141 MSGCLASS Sysout, 3-76 ON Statements, 3-112 Prerequisite Condition, 3-48 Prerequisite Conditions, 1-24 Sysout, 3-71, 3-73, 3-178, 3-180 Table in Table List, 2-128 DELMNCND KSL Script, 8-10 DEPEND ON Field Job Flow Report, 8-39 Dependency Maybe Job, 6-21 DEPENDS ON Field Quick Schedule Definition, 2-198 DESC Command Job List Screen, 2-33 Status Screen, 2-67 DESC Field Parameter Prompting, 2-180 Status Screen, 2-65 DESC Format Job List Screen, 2-33 DESC Parameter Description, 3-42 Example, 3-43 DESC Parameter (CTM) Utility CTMTBUPD, 6-82
Description Field Parameter Prompting, 2-183 DESCRIPTION Field Calendar Definition, 2-158 Job Flow Report, 8-39 Quick Schedule Definition, 2-199 Rule List Screen, 2-119 DESCRIPTION Parameter CMEM Rule, 4-11 Example, 4-12 Scheduling Definition, 2-34 Descriptor Codes MVS WTO, D-2 Destination DO SHOUT Statement, 3-68, 4-24, 4-26 DO SYSOUT Statement, 3-70 SYSOUT Parameter, 3-176 Destination Table CTMDEST Loading, 6-112 Devices Tape Usage, 2-107 DEVICES USED Field Statistics Screen, 2-107 DI IFRERUN Statement RERUNMEM Parameter, 3-149 D-INT Message Type Show Screen Filter, 2-148 DISAPPEARED Status Activate Option, 2-70 Show Screen Filter, 2-76 Status Screen, 2-72 Zoom Screen, 2-93 DISP Parameter ON DSNEVENT Statement, 4-36 Display Command Status Screen, 2-63 DISPLAY Command Job Order Execution History Screen, 2-103 Status Command, 2-66 Display Type Status Screen, 2-63 Display Type A Status Screen, 2-65
I 26
Index
Display Type D Status Screen, 2-64 Display Type Field Status Screen, 2-64 Display Type Indicator Job Dependency Network, 2-110 DL Line Edit Command, A-2, B-2 DO Action DO Statement, 2-41 DO COND Statement CMEM Rule, 4-2, 4-14 Conflicts, 3-48 Definition, 3-46 DO Statement Action, 3-44 Example, 3-49, 4-15 Logic, 3-47 OUT Parameter, 3-49, 3-124 Prerequisite Condition, 1-22, 3-88, 4-15 DO CTBRULE Statement Description, 3-50 DO Statement Action, 3-44 Example, 3-51 DO FORCEJOB Statement Active Jobs File, 4-17 CICS Job, 4-20 CMEM On Spool Job, 4-6 CMEM Rule, 4-2, 4-17 Dataset Event, 4-18 Description, 3-52, 4-17 DO Statement Action, 3-44 Example, 3-53, 4-19 Logic, 4-18 RERUNMEM Parameter, 3-148 TASKTYPE Parameter, 3-183 DO IFRERUN Parameter CONFIRM=Y, 2-113 DO IFRERUN Statement Description, 3-54 DO Statement Action, 3-44 Example, 3-56 Job Rerun, 2-99 RERUNMEM Parameter, 3-148 Scheduling Definition, 2-94 DO NOTOK Statement DO Statement Action, 3-44
DO OK Statement Description, 3-59 DO Statement Action, 3-44 ON Statement Codes, 3-114 DO RERUN Statement CMEM On Spool Job, 4-6 DO Statement Action, 3-44 Zoom Screen, 2-92 DO RULE Calls Nesting, 4-22 DO RULE Statement AutoEdit, 4-21 CONTROL-O Rule, 4-2, 4-21 Example, 4-23 DO SET Statement AutoEdit Statement, 5-28 Description, 3-63 DO Statement Action, 3-44 Example, 3-65 JCL Setup, 5-4 SET VAR Parameter, 3-64, 3-165 User-Defined Variables, 5-3 DO SHOUT Statement CMEM CONTROL-O, 4-2 CMEM Rule, 4-24 CONTROL-O, 4-24 DO Statement Action, 3-44 Dynamic Destination Table, 4-26 Example, 3-69, 4-26 JES, 4-25 Shout Facility, 3-66 DO SHOUT<S> Statement Route Codes, 4-25 DO Statement CMEM Rule, 4-2, 4-9, 4-13 CMEM Rule Definition, 2-123 Description, 3-44 Logic, 3-45 Post-Processing Parameters, 2-41 Summary, 3-10 DO STOPJOB Statement CMEM Rule, 4-2, 4-27 Description, 4-27 Example, 4-28
I 27
Index
DO SYSOUT Statement Archiving Facility, 3-76 Description, 3-70 Diagram, 3-73 DO Statement Action, 3-44 Example, 3-75 Logic, 3-72 Merging, 3-73 SYSOUT Parameter, 3-177, 3-180 SYSOUT Parameter, 3-74 DOC Command Scheduling Definition, 2-46, 2-48 Zoom Screen, 2-94 DOC Lines Scheduling Definition, 2-49, 3-81 Status Zoom Screen, 3-81 DOCLIB Field Scheduling Definition, 2-49 DOCLIB Parameter Description, 3-79 Example, 3-80 DOCLIB Parameter (CTM) Utility CTMTBUPD, 6-82, 6-83 DOCMEM Field Scheduling Definition, 2-49 DOCMEM Member DOCLIB Library, 3-79 DOCMEM Parameter Description, 3-81 Example, 3-82 DOCMEM Parameter (CTM) Utility CTMTBUPD, 6-82 DOCU/TEXT, 3-79, 3-81 Browse Mode, 2-48 Interface, 2-165, 2-209, 7-12 JCL Documentation, 2-209 Online Utilities Menu, 2-164 Option, 2-164 Option U1, 2-165 Utility, 2-165 Documentation AUTO-SAVE Field, 2-30, 2-49 DESC Parameter, 3-42 Editing, 2-49 Saving, 2-49
Scheduling Definitions, 2-48 Screen Printouts, 8-9 SHOW JOB Field, 2-28 DOIFRERUN Statement TASKTYPE Parameter, 3-183 DOWN Command PF08/PF20, 2-13, 2-15 DS Line Edit Command, B-2 DSN Parameter ON DSNEVENT Statement, 4-35 DSN=parm_library(member) User Daily Job, 6-9 DSN=sched_library(table) User Daily Job, 6-9, 6-71 DSNAME Parameter Event Definition, 6-27 DSNEVENT Statement. See ON DSNEVENT DUE IN Field Zoom Screen, 2-92 DUE IN Time DUE OUT Parameter, 3-83 Due Out Runtime Criteria, 1-5 DUE OUT Adjustment Operator Command, 6-112 DUE OUT Parameter Description, 3-83 Example, 3-84 Job Flow, 1-26 DUE OUT Time REFRESH Command, 2-111 SHOUT Parameter, 3-169 Zoom Screen, 2-92 DUEIN Field Job Dependency Network, 2-110 DUEOUT Field Job Dependency Network, 2-110 DUE-OUT Parameter Utility CTMTBUPD, 6-82 Dummy Class DO SYSOUT Statement, 3-72 SYSOUT Parameter, 3-178 DUMMY Library MEMLIB Parameter, 3-100
I 28
Index
OVERLIB Parameter, 3-131 DUMP Command Status Screen, 2-68 Dynamic Destination Table DO SHOUT Statement, 3-68, 4-26 Loading, 6-112 SHOUT Parameter, 3-172
E
E Option Job List Screen, 2-32 Manual Conditions, 2-141 New Day Processing, 6-101 Status Screen, 2-70 ECJ Task Type Show Screen Filter, 2-77, 2-148 ECS Task Type Show Screen Filter, 2-77, 2-148 EDIT Command CMEM Rule Definition, 2-124 Job Scheduling Definition, A-1 Scheduling Definition, 2-46 Edit Environment, A-1 CMEM Rules, 2-125 Description, A-1 Example, A-5 Line Editing Commands, 2-47 EDIT Option. See also JCL Option Status Screen, 2-70 Editing CMEM Rule Definition, 2-125 CMEM Rules, 2-116 Documentation, 2-49 Example, A-5 Job JCL, 2-34, 2-70 Rule Definitions, B-1 Scheduling Definition, 2-47, A-1 ELAPS Field Job Dependency Network, 2-110 ELAPSE Field Zoom Screen, 2-92 ELAPSE Time Job Flow, 1-27 ELAPSE TIME DUE OUT Parameter, 3-83
ELAPSED Field Job Order Execution History, 2-103 ELAPSED Run Time Field Statistics Screen, 2-106 ELAPSED Time, Average Statistics Screen, 2-106 ELAPSED Time, Group Statistics Screen, 2-106 Emergency Execution DASUBMIT DD Statement, 5-28 Emergency Job MAXWAIT Parameter, 3-98 TASKTYPE Parameter, 3-182 EMR Task Type Show Screen Filter, 2-77, 2-148 End Code ON Statement, 3-113 END Command Calendar Definition, 2-162 CMEM Rule Definition, 2-126 KSL, 8-14 PF03/PF15, 2-13 Scheduling Definition, 2-51 Show Screen Filter, 2-79, 2-150 Year List, 2-163 END NOT OK Status END NOTOK Status, 2-61 ENDED NOT OK ..., 2-113 END NOTOK Field Global View Screen, 2-80 View Graph Screen, 2-82 END NOTOK Status Job Graph, 2-82, 2-84 END OK Field Global View Screen, 2-80 Job Graph, 2-82 View Graph Screen, 2-82 END OK Status ENDED OK Status, 2-45 END TIME Field Statistics Screen, 2-106 End User Job Order Interface Job Ordering, 6-14 Utility CTMJBINT, 2-202
I 29
Index
ENDED, 2-71 ENDED NOT OK ABENDED Status Status Screen, 2-71 ENDED NOT OK DUE TO CC Status Status Screen, 2-72 ENDED NOT OK JCL ERROR Status Status Screen, 2-71 ENDED NOT OK RERUN WAS NEEDED Status Status Screen, 2-72 ENDED NOT OK TERM ON NCT2 Status Status Screen, 2-72 ENDED NOT OK Status Status Screen, 2-71 TERMINATE Option, 2-113 ENDED NOTOK Status DO STOPJOB Statement, 4-27 ENDED NOTOOK Status Status Screen, 2-74 ENDED OK Status Job Graph, 2-84 Show Screen Filter, 2-76 Status Screen, 2-71, 2-73 TERMINATE Option, 2-113 ENDED Status Show Screen Filter, 2-76 Enhanced Daily Checkpoint Record Checkpointing, 6-7 Enqueue Manager CTMRELRS Utility, 6-78 ENTER Command KSL, 8-12 ENTER Key Auto-Refresh Mode, 2-18 Enter YES Field Prerequisite Condition Utility, 2-167 Simulation/Tape Pull, 2-175 ENTER YES TO CONTINUE Job Datatset List, 2-209 ENTER YES TO CONTINUE Field Job Order Utility, 2-168 Enterprise Constrolstation DO SHOUT Statement, 3-67 Enterprise Controlstation APPL Parameter, 3-14
GROUP Parameter, 3-86 Product Description, 1-2 Entry Panel Auto-Save Documentation, 2-28, 2-49 Calendar Facility, 2-153 CMEM Rule Definition, 2-118 CMEM Rule Facility, 2-117 Exiting, 2-52 IOA, 2-4 Parameter Prompting, 2-176 Scheduling Facility, 2-25, 2-27, 2-52 Table Creation, 2-24 Environment Online Facility, 2-1 Environment Specification SET VAR Parameter, 3-167 EQ Operator %%$UNDEF, C-3 AutoEdit Facility, 5-16 ERASE Option Manual Conditions, 2-141 Error CONTROL-M Monitor, 6-103 Errors Only Field Simulation/Tape Pull, 2-175 EST Task Type Show Screen Filter, 2-77, 2-148 Event Definition Screen, 6-27 Event List IOACDDR REXX Procedure, 6-25 Screen, 6-26 Event Modification Screen, 6-25, 6-27 Event Modification Screen Selected via Event List Screen, 6-28 Event Selection Parameter CMEM Rule, 2-122, 4-9 Exclusive Control CONTROL Parameter, 3-25 Exclusive Resource WAIT SCHEDULE Status, 2-135 EXEC A PLAN Option Parameter Prompting, 6-37
I 30
Index
EXEC Phase Parameter Prompting, 2-188 EXEC progname Command KSL, 8-14 Exec/Order a Plan Parameter Prompting, 2-190, 2-193 EXECTIME Limit SHOUT Parameter, 3-170 Execute a Plan CTMEXEC CLIST, 6-37 EXECUTING (SYSOUT IN HOLD STATUS) Status Screen, 2-71 EXECUTING Field Global View Screen, 2-80 View Graph Screen, 2-82 EXECUTING Status Job Graph, 2-82, 2-84 Show Screen Filter, 2-76 Execution Delay MAXWAIT Parameter, 3-97 Execution Error ON Statement, 3-113 Execution Information Job Order Execution History, 2-102 Statistics Facility, 1-10 EXECUTION TIME DUE OUT Parameter, 3-83 EXERR Code ON Statement CODES, 3-114 EXERR Status Description, 3-9 ON Statement, 3-112 Exit CTMX001, 6-16 CTMX002, 3-101, 3-152, 5-27, 6-41, 7-7 CTMX003, 7-7 CTMX004, 3-152, 6-111 CTMX013, 2-106 Exit Command Online Facility, 2-11 EXIT Option Online Utilities Menu, 2-164 Parameter Prompting Entry Panel, 2-176 Primary Option Menu, 2-6
Exit Window Job List Screen, 2-51 Rule List Screen, 2-127 Year List, 2-163 Exiting Calendar Facility, 2-162 CMEM Entry Panel, 2-128 CMEM Rule Facility, 2-126 CMEM Rule List, 2-127 CMEM Table List, 2-128 Define Parameters in Master Plan, 2-189 Job List, 2-52 Job Scheduling, 2-50 Quick Schedule Definition, 2-200 Scheduling Definition, 2-50 Show Screen Filter, 2-78, 2-150 Year List, 2-163 External Tape Example, 5-36
F
F Option Job List Screen, 2-34 Status Screen, 2-69 Table List Screen, 2-26, 2-31, 2-53 FAILED REASON UNKNOWN Status Activate Option, 2-70 Fast Exit Online Facility, 2-11 Fetch a Plan CTMFETCH CLIST, 6-37 Parameter Prompting, 2-189 FETCH A PLAN Option Parameter Prompting, 6-36 Field-Sensitive Help Online Facility, 2-17 File Name DO SYSOUT Statement, 3-70 SYSOUT Parameter, 3-176 File Prefix Parameter Prompting, 2-177 File Transfer Example, 4-16
I 31
Index
File Transfer to PC PC PACKET STATUS Option, 4-16 Filter Job Dependency Network, 2-108, 2-110 Filter Activation SHOW Filter Name, 2-145 Filter Field Status Screen, 2-64 FILTER Field Show Screen Filter, 2-75, 2-147 Filtering Log Screen, 2-146 Status Screen, 2-74 FIND Command Description, 2-16 Graphic Jobflow Screen, 2-57 Job Scheduling Definition Screen, 2-46 KSL, 8-12 PF05/PF17, 2-13 PF05/PF17 key, 2-58 FIND or Searching LOCATE Command, 2-15 Flow Commands KSL, 8-3, 8-13 FLUSH Value PREVENT-NCT2 Parameter, 3-140 FONT Parameter CTMRFLW Report, 8-35 FORCE Argument ORDER Record, 6-72 Force Job CMEM, 4-2 Force OK Cyclic Jobs, 2-113 Force OK Confirmation Window Description, 2-113 FORCE OK Confirmation Window Status Screen, 2-113 FORCE OK Option Status Screen, 2-113 FORCE Option CMEM Table List, 2-119, 2-129, 4-2, 6-107 DO FORCEJOB Statement, 3-52 Job List Screen, 2-26, 2-34
Manual Scheduling, 2-53 Table List Screen, 2-26, 2-31, 2-53 FORCE Parameter CLIST CTMCJOBS, 6-15 CTMJOB Utility, 6-74 FORCED FROM TIME Field Parameter Prompting, 2-191 FORCED SCHEDULING Field Job Order Utility, 2-168 Forcing Jobs Overview, 1-20 Forecasting Overview, 1-10, 1-11 Resource Release, 6-78 Simulation, 1-10 FR Parameter STEP RANGE Parameter, 3-174 FREE Command KSL, 8-19 FREE Option Status Screen, 2-69 FREE Status Show Screen Filter, 2-77 Free Tracks MINIMUM Parameter, 3-106 PDS Parameter, 3-135 FRM Parameter DO SYSOUT Parameter, 3-70 FROM Class DO SYSOUT Statement, 3-70, 3-72 SYSOUT Parameter, 3-176, 3-178 FROM DATE Field Date Range Window, 2-59 FROM Field Zoom Screen, 2-92 FROM PGMSTEP Field CONTROL-R Dataset Cleanup, 2-205 FROM PGMSTEP Parameter CONTROL-R Simulation, 2-204 Dataset Cleanup, 2-206 FROM PROCSTEP Parameter CONTROL-R Simulation, 2-204 Dataset Cleanup, 2-206 FROM STEP Restart Step List Window, 2-101
I 32
Index
FROM STEP Field Restart Confirmation Window, 2-99 From Step/Proc $FIRST/$CLEANUP Rerun/Restart Window, 2-100 FROM Time TIME Parameter, 3-186, 3-188 fromcol Parameter FIND Command, 2-16 FROMJOB Field Quick Schedule Definition, 2-197 FTP CMEM Support, 4-7 FTP Started Task CMEM Support, 4-7 FUNCTION Field Prerequisite Condition Utility, 2-166 FUNCTION Parameter AutoEdit Simulation, 2-170
G
G Option Table List Screen, 2-31, 8-33 GE Operator AutoEdit Facility, 5-16 GEN Card AutoEdit Symbols Member, 6-49 GEN Parameter CTMBLDAE Utility, 6-50 General Job Definition Parameter Tables, 6-63 General Job Parameter Scheduling Definition, 2-37 GENERAL Library DALIB DD Statement, 3-101 MEMLIB Parameter, 3-100 OVERLIB Parameter, 3-132 GENERAL Message Type Show Screen Filter, 2-148 General Parameters CMEM Rule, 4-9 CMEM Rule Definition, 2-123 CTMBLT Utility, 6-55 Summary, 3-4 General Profile Status Screen Filter, 2-74, 2-146
Generic Resource Example, 5-39 GETFILE Command KSL, 8-19 GLBCHANG KSL Script, 8-10 GLOBAL AUTOEDIT LIBRARY Job Dataset List, 2-209 GLOBAL AUTOEDIT LIBRARY Parameter CONTROL-R Simulation, 2-204 Dataset Cleanup, 2-206 GLOBAL Control Statement %%GLOBAL, 5-15 Global Parameter CTMBLT Utility, 6-55 Global Profile Customizing, 2-1 Global Variable AutoEdit, 5-2 JCL Setup, 5-9 Priority, 5-10 Global view Screen Fields, 2-80 Global View Screen Group Statistics, 2-79 Status Screen, 2-67 GOING TO START Status Status Screen, 2-71 GOTO Command KSL, 8-14 Graphic Display Job Status, 2-67 Graphic Flow Option Table List Screen, 2-57 GRAPHIC FLOW Option Table List Screen, 2-26, 2-31 Graphic Format Parameters CTMRAFL Report, 8-44 Graphic Jobflow Display Width, 2-57 KSL Script, 8-10 Screen, 2-57 Graphic Jobflow Option Table List Screen, 8-33
I 33
Index
Graphical Information View Graph Screen, 2-81 GROUP Command Log Screen, 2-146 Status Screen, 2-67 GROUP Criteria Screen Filter, 2-149 GROUP Dependent Job Flow Report, 8-39 Group Entities Active Jobs File, 2-88 Group Entity Display, 2-69 Group Scheduling Table, 3-2 Group-Handled Jobs, 1-21, 2-24 ON GROUP-END Parameter, 3-118 OUT Conditions, 3-122 Parameters, 2-44 Prerequisite Condition, 1-23 Scheduling Definition, 2-43 Statistics Screen, 2-106 Task Type, 2-77 Zoom Screen, 2-94 GROUP Field Global View Screen, 2-80 Group Entity, 2-44 Job Order Utility, 2-168 Quick Schedule Definition, 2-197 Show Screen Filter, 2-76 Status Screen, 2-65 Group Handled Jobs, 2-24 Group Name GROUP Parameter, 3-85 GROUP NAME Field View Graph Screen, 2-82 GROUP NAME Parameter AutoEdit Simulation, 2-170 Group Option Status Screen, 2-69 Group Output CTMRFLW Report, 8-40 GROUP Parameter CLIST CTMCJOBS, 6-15 CMEM Rule, 4-29 CTMRFLW Report, 8-34
CTMROGR Report, 8-54 Description, 3-85 Emergency Jobs, 3-183 Example, 3-86 Group Entity, 2-44 MAXWAIT Parameter, 3-98 Utility CTMTBUPD, 6-82 Group Scheduling Group Entity, 1-21, 2-43 Job List Screen, 2-32 Logic, 3-7 MAXWAIT Parameter, 3-98 Option O, 2-53 Parameters, 2-44 Group Scheduling Table CTMBGRP Utility, 6-60 Force Job via Online Utilities Menu, 2-168 FORCE Parameter, 6-15 Group Entity, 3-2 Maybe Jobs, 6-21 REMOVE UNSCHED CONDITIONS Field, 6-22 Group Statistics Global View Screen, 2-79 View Graph Screen, 2-81 Group Status Status Screen, 2-73 Group Status Field Global view Screen, 2-80 Group-Handled Jobs, 2-24 Description, 1-21 Groupname Argument JOBSTART Command, 2-107 GRP Entry Status Screen, 2-69 GRP Task Type Show Screen Filter, 2-77, 2-148 GT Operator AutoEdit Facility, 5-16
H
H Option Status Screen, 2-69
I 34
Index
HALF Page Scrolling Amount, 2-15 HEADERLINE Command KSL, 8-17 HEADERSIZE Command KSL, 8-18 Held Class SYSOUT Parameter, 3-177 HELD Class DO SYSOUT Statement, 3-71 HELD Status CMEM On Spool Job, 4-5 Job Deletion, 2-89, 2-113 Show Screen Filter, 2-77 Status Screen, 2-72 Zoom Screen, 2-91 Help Line Sensitive, 2-17 Online Help, 2-17 HELP Command PF01/PF13, 2-13, 2-17 Hexadecimal Character Periodic Calendar, 2-159 Hexadecimal Value Special Character, 2-2 HIST Installation Parameter CONTROL-R, 1-7 HISTORY Command Status Screen, 2-66, 2-112 History Environment Screen Description, 2-112 Options, 2-112 RESTORE Option, 2-113 History Jobs File # OF DAYS TO KEEP, 3-155 # OF GENERATIONS TO KEEP, 3-157 CONTROL-R, 6-3 Description, 1-7 HLDCLAS Installation Parameter DO SYSOUT Statement, 3-71 SYSOUT Parameter, 3-177 HOLD Option Status Screen, 2-69 HOLDFRUP KSL Script, 8-10
Host Node NJE Network, 1-8
I
I Line Edit Command, A-3, B-2 I Option Job List Screen, 2-34 Parameter Prompting, 2-181 Year List Screen, 2-156 I1 Option Online Utilities Menu, 2-166 IBM 3720 Terminals, 2-2 IDMS/DC Color Support, 2-2 Environment, 2-1 Online Monitor, 6-113 PF06/PF18, 2-13 IEASYSXX Member SYS1.PARMLIB Library, 6-114 IEF125I Message ON DSNEVENT Statement, 4-37 IEF3521 Error Message Address Space Vector Table, 6-114 IEF403I Message ON DSNEVENT Statement, 4-37 IEFPROC Stepname ON DSNEVENT Statement, 4-36 ON STEP Statement, 4-45 IF Logic Example, 5-43 IFSCREEN Command KSL, 8-15 IFVAR Command KSL, 8-16 IGNORE DSN Parameter Tape Pull List, 7-11 IGNORE IN Parameter IOALDNRS Utility, 6-34 IGNORE JOB Parameter Tape Pull List, 7-11 IGNORE Parameter CTMRCAL Utility, 6-77 CTMRPLN Report, 8-45 IGNORE Statement CTMJOB Utility, 6-71
I 35
Index
IGNORE TAG Logic CTMJOB Utillity, 6-73 IGNORE TAG Parameter User Daily Job (CTM), 6-73 IGNORE TAG tagname CTMJOB Utility, 6-73 Implementation Checkpointing, 6-7, 6-10 CONNECT DIRECT Support, 6-25 Date Control Record, 6-10 Job Scheduling, 6-2, 6-14 Manual Conditions, 6-19 New Day Procedure, 6-2 New Day Processing, 6-7 Parameter Prompting, 6-29 User Daily Job, 6-2, 6-8 IMS/DC Color Support, 2-2 Environment, 2-1 Online Monitor, 6-113 PF06/PF18, 2-13 IMS-ACTIVE Prerequisite Condition, 3-127 IN Conditions Job Dependency, 2-108 IN Parameter Description, 3-87 Example, 3-90 Logic, 3-89, 3-94 Quick Schedule Definition, 2-194 IN Prerequisite Condition IOALDNRS Utility, 6-19 IN PROCESS Status Show Screen Filter, 2-76 IN Statement Manual Conditions, 2-139 Prerequisite Condition, 1-22 INCLIB Control Statement %%INCLIB, 5-18 INCLUDE GROUPNAME Parameter CTMRNSC Report, 8-51 INCLUDE JOBNAME Report CTMRNSC Report, 8-51 Information about Job DESC Parameter, 3-42
INQ/UPD MEDIA DB Option IOA Menu, 2-9 INSERT BY WEEK DAYS Option Year List, 2-156 Insert Command Edit Environment, A-3, B-2 INSERT Option CMEM Rule List, 2-120 Event List Screen, 6-26 Job List Screen, 2-25, 2-34 Parameter Prompting, 2-181, 2-189 Year List, 2-156 Installation Working Date Working Date, 5-6 Internal Sequence Number Checkpointing, 6-7 Interval Periodic Calendar, 2-160 INTERVAL Parameter CTMPARM Member, 5-18 CTMROGR Report, 8-54 Description, 3-95 Example, 3-96 RERUNMEM Parameter, 3-148 Simulation, 7-4 Simulation/Tape Pull, 2-174 TASKTYPE Parameter, 3-183 Utility CTMTBUPD, 6-82 INTRDR Internal Reader Submit Authority, 2-172 Tape Pull List, 7-10 INVOKE JOB/SCAN Simulation/Tape Pull, 2-175 Tape Pull List, 7-12 IOA Under ISPF, 2-19 IOA Conditions/Resources. See Conditions/Resources IOA Core Description, 1-17 IOA Entry Panel Description, 2-4 IOA for the Enterprise Platform Automation, 1-2
I 36
Index
IOA INFO Option Primary Option Menu, 2-6 IOA Log Facility, 2-144 Description, 1-7 Post-processing, 1-8 IOA Log File Log File, 8-53 IOA Manual Conditions. See Manual Conditions IOA Menu Primary Option Menu, 2-5 IOA Online Monitor Online Monitor, 6-113 IOA Options Options, 2-7 IOA Primary Option Menu Primary Option Menu, 2-5 IOA Products Summary, 1-1 IOA Screens Screens, 1-14, 2-21 IOA SECUDATA Library SECUDATA Library, 3-101 IOA/Pathfinder Product Description, 1-2 IOA/PATHFINDER Primary Option Menu, 2-6 IOABLCAL Utility CTMRCAL Calendar, 6-76 Summary, 6-43 IOACCND CLIST TSO Command Processor, 2-166 IOACCND Utility Prerequisite Condition, 2-166 IOACDDR REXX Procedure Dataset Event Definition, 6-25 IOACLRES Utility Conditions/Resources, 6-4 Summary, 6-44 IOACND Utility Description, 6-97 Example, 6-98 Summary, 6-44 IOACOPRS Utility Summary, 6-44
IOACPLOG Utility Summary, 6-44 IOADFLTC Member IOA MAC Library, 5-18 IOAFRLOG Utility Summary, 6-44 IOAFRNRS Utility Summary, 6-44 IOAFRRES Utility Summary, 6-44 IOAID Field Conditions/Resources, 2-133 IOALDNRS Utility Manual Conditions, 2-139, 6-4, 6-19, 6-31 Parameter Prompting, 6-34 Summary, 6-44 User Daily Job, 6-10 IOALog Screen. See Log Screen IOANOTE Utility Summary, 6-44 Tasktype WRN, 3-183 IOAOPR Utility Description, 6-113 Summary, 6-44 IOARKSL Procedure KSL, 8-2 IOATEST Utility Summary, 6-44 IOAUTIL CLIST Online Utilities, 2-164 IOAVCND Utility Description, 6-99 Summary, 6-44 IOAVERFY Utility Summary, 6-44 IPL Required ASVT Full, 6-114 ISPF Auto-Refresh Mode, 2-18 Color Support, 2-2 ISPF Application Option 6, 2-5 ISPF Commands Priority, 2-19
I 37
Index
ISPF Pack Option Calendar Facility, 2-151 ISPF PACK Option, 3-104 Scheduling Definition, 2-22 ISPF SPLIT Command PF02/PF14, 2-13 ISPF/PDF Facilities Online Facility, 2-20 ISPF/PDF Primary Option Menu ISPF KEYS Command, 2-19 ISPSTART Command ISPF Keys, 2-19
J
J Option Job List Screen, 2-34 Status Screen, 2-70 JCL CTMRFLW Report, 8-34, 8-37 CTMRNSC Report, 8-51 CTMROGR Report, 8-54 CTMRPLN Report, 8-46 Editing, 2-70 JCL Check Field Simulation/Tape Pull, 2-175 JCL Command Job List Screen, 2-26 JCL Documentation DOCU/TEXT Product, 2-209 JCL Edit Job List Screen, 2-34 Status Screen, 2-70 JCL Error Intentional, 5-5 ON Statement, 3-113 JCL ERROR Status Show Screen Filter, 2-76 JCL Expanded SYSDATA, 1-21 JCL Library CTMQSB Command, 6-16 OVERLIB Parameter, 3-131 PPF2DAY Job, 6-42 PPF2DEL Job, 6-41 Special Reports, 8-33
JCL Library Mode AutoEdit Syntax Testing, 2-168, 5-27 Parameters, 2-170, 4-40, 6-45 JCL LIBRARY Parameter AutoEdit Simulation, 2-170, 6-45 CONTROL-R Simulation, 2-203 Dataset Cleanup, 2-206 Job Dataset List, 2-209 JCL Management CMEM On Spool Job, 4-6 JCL Member OVERLIB Library, 3-131 RERUNMEM Parameter, 3-148 JCL Member Name OVERLIB Parameter, 2-170 JCL Modification OVERLIB Parameter, 3-131 JCL Option Job List Screen, 2-34 Status Screen, 2-70 JCL SET AutoEdit SET Statement, 5-14 JCL Setup %%ELSE Control Statement, 5-16 %%ENDIF Control Statement, 5-16 %%GLOBAL Control Statement, 5-15 %%GOTO Control Statement, 5-15 %%IF Control Statement, 5-16 %%INCLIB Control Statement, 5-18 %%INCMEM Control Statement, 5-18 %%LABEL Control Statement, 5-15 %%LIBSYM Control Statement, 5-19 %%MEMSYM Control Statement, 5-19 %%RANGE Control Statement, 5-20 %%RESOLVE Control Statement, 5-21 %%SET Control Statement, 5-21 AutoEdit, 1-5, 5-2, 5-23 Control Statement, 5-15 CTMAESIM Utility, 5-27 Date Variable, 5-6, 5-30 DO SET Statement, 5-4 Global Variable, 5-9 Modification, 3-131, 5-1 Nested Expressions, 5-17 Operators, 5-16
I 38
Index
Syntax Checking, 5-27, 7-10 Sysout Archiving, 5-29 System Variable, 5-5 User Daily Job, 6-9 User-Defined Variable, 5-9 Variable Resolution, 5-11 Work Flow, 5-4 JCL Statement AutoEdit Variable, 3-64 MEMNAME Parameter, 3-104 Syntax Checking, 5-27, 7-10 JCL Syntax Checking, 5-27, 7-10 CTMSCIM Utility, 2-172 JCLFILE Parameter DAJCLOUT DD Statement, 7-12 Tape Pull List, 7-11 JES Command CONTROL-M Monitor, 6-103 JES Deactivation CMEM Deactivation, 6-105 JES HOLD Command Job Status, 2-71 JES Initialization SYSDATA Output Class, 1-21 JES Instruction DO SYSOUT Statement, 3-72 SYSOUT Parameter, 3-178 JES Malfunction CONTROL-M Monitor, 6-103 JES Spool ON JOBARRIV Statement, 4-40 JES2 cpuid, 3-101 DO SHOUT Statement, 3-67, 4-25 DO SYSOUT Statement, 3-71 SHOUT Parameter, 3-171 Started Task, 6-102 SYSOUT Parameter, 3-177 JES3 cpuid, 3-101 DO SHOUT Statement, 3-67, 4-25 DO SYSOUT Statement, 3-71 SHOUT Parameter, 3-171 Started Task, 6-103
SYSOUT Parameter, 3-177 JESDS Subparameter SYSDATA Output Class, 1-21 JESxPARM Member CMEM Support for FTP, 4-7 JFAIL Code ON Statement CODES, 3-113 JFAIL Status Description, 3-9 JLOST Code ON Statement CODES, 3-113 JNRUN Code ON Statement CODES, 3-113 JNSUB Code ON Statement CODES, 3-113 JNSUB Reason NOT SUBMITTED Status, 5-5 Job Job Name / Scheduling Table Name Xref Report, 6-92 Job Activation Option Status Screen, 2-70 Job Arrival Event CMEM, 4-1, 4-40 DO FORCEJOB Statement, 4-18 Job Arrival Rules CMEM On Spool Job, 4-6 Job Chain DO COND Statement, 3-49 IN Parameter, 3-92 Job Dataset Cross Reference CTMRJDS Report, 8-57 Job Deletion Status Screen, 2-89, 2-113 Job Dependency %%PLANID, 6-39 Critical Path, 1-26 Job Flow, 1-27 Job Flow Report, 8-33 Maybe Job, 6-20 Predecessor/Successor Job, 1-26 Prerequisite Condition, 1-23, 3-88 REFRESH Command, 2-68 Job Dependency Network Commands, 2-111
I 39
Index
Description, 2-108 NET Option, 2-70 Quick Schedule Definition, 2-198 Job Documentation DESC Parameter, 3-42 Documentation, 2-48, 2-49 Job End Event CMEM, 4-1, 4-33 DO FORCEJOB Statement, 4-18 Job Execution Statistics, 2-105 Job Execution Time DUE OUT Parameter, 3-83 JOB Field Entry Panel, 2-27 Job Filter Log Screen, 2-90 Job Flow Adjustment, 1-14, 1-26 ELAPSE Time, 1-27 Manual Modification, 1-27 Job Flow Report CTMRAFL Report, 8-44 CTMRFLW Report, 8-33 Cyclic Job Flow, 8-39 Fields, 8-39 JCL, 8-37 Job Dependency, 8-33 Prerequisite Condition, 1-26 Scheduling Data, 8-39 Text Format, 8-38 Job Forcing CMEM On Spool Job, 4-6 Definition, 1-20 Logic, 4-6 Job Graph ENDED OK Status, 2-113 JOB GRAPH Line View Graph Screen, 2-82, 2-83 Job Interdependency Job Dependency, 2-198 Job List Exit Window Table Creation, 2-24 Job List Screen Commands, 2-33 COPY Option, 2-26
Delete Job, 2-32 Description, 2-32 Edit JCL, 2-34 Exiting, 2-51 Fields, 2-198 Format, 2-33 Job Ordering, 6-14 Manual Scheduling, 2-53 Options, 2-26, 2-34, 2-199 Quick Schedule Definition, 2-198 Scheduling Definition, 2-24 Job Log SYSDATA, 1-21 Job Name Example, 5-38 Job Scheduling Plan Screen, 2-60 MEMNAME Matching, 4-6 Job Name / Table Name Cross Ref CTMXRF Utility, 6-94 Job Name Cross Ref CTMXRF Utility, 6-95 JOB NAME Field Job Order Utility, 2-168 Parameter Prompting, 2-187 Job Name Parameter ON JOBARRIV Statement, 4-40 ON JOBEND Statement, 4-42 JOB NAME Parameter AutoEdit Simulation, 2-170 Event Definition, 6-27 Job Dataset List, 2-209 Job Name/Scheduling Table Name Report CTMXRF Utility, 6-91 Job On Spool On Spool Job, 4-4 Job Order Execution History Screen Description, 2-102 Fields, 2-103 Status Screen View Option, 2-69 JOB ORDER ISSUE Option Online Utilities Menu, 2-164 Job Ordering Ad Hoc, 6-17 CLIST CTMCJOBS, 6-15 CTMCJOBS CLIST, 6-15
I 40
Index
Definition, 1-20 End User Job Order, 2-202 Event List, 6-26 Example, 5-35 Job Order Panel, 6-14 Order ID, 1-21 Quick Submit Command, 6-16 Utility, 2-167 JOB Parameter CLIST CTMCJOBS, 6-15 DO FORCEJOB Statement, 3-52, 4-17 ON STEP Statement, 4-44 Testing AutoEdit Syntax, 6-45 Job Parameters Scheduling Definition, 2-37 Job Plan Report CTMRCAL Utility, 6-76 CTMRPLN Report, 8-45 Job Priority Priority..., 1-26 Job Production Scheduling ..., 3-3 Job Reactivate Option Status Screen, 2-70 Job Rerun. See Rerun Job Restart. See Restart Job Run Statistics Statistic..., 2-105 JOB SCAN AutoEdit Simulation, 2-171 JOB SCHEDULE DEF Option Primary Option Menu, 2-6 Job Scheduling Alternative Methods, 6-14 AutoEdit Facility, 5-3, 5-28 CTMAJO Program, 6-17 CTMBLT Utility, 6-55 CTMJOB, 6-14 CTMQSB Command, 6-16 Implementation, 6-2, 6-14 New Day Processing, 6-2 Parameter Tables, 6-63 Screen, 2-35 Table List Screen, 6-14
Job Scheduling Definition Calendar Facility, 1-9 CMEM Rule, 4-5 Commands, 2-46 DOC Lines, 3-81 Group-Handled Jobs, 2-24 New Day Processing, 1-4 Parameters, 1-3 Storing, 1-3 Job Scheduling Plan Calendar Format, 2-59 Screen, 2-60 Job Scheduling Tables Updating, 6-80 Job Statistics Statistic..., 8-10 Job Status Description, 3-9 Status Screen, 2-71 JOB STATUS Field Global View Screen, 2-80 JOB STATUS Option Primary Option Menu, 2-6 Job Submission Manual Confirmation, 3-23, 3-55 Scheduling Criteria, 1-5 Job Sysout Sysout..., 1-21 Job Task Type TASKTYPE Parameter, 3-182 JOB Task Type Show Screen Filter, 2-77, 2-148 Job Termination DO STOPJOB Statement, 4-27 ON JOBEND Statement, 4-42 JOB Type Event List Operation, 6-26 Job Type Parameter ON JOBARRIV Statement, 4-40 ON JOBEND Statement, 4-42 JOB TYPE Parameter Event Definition, 6-27 JOB WAIT FOR PIPES COLLECTION Why Screen, 2-85
I 41
Index
Job Workload Overnight Execution Graph, 8-53 JOB/PIPE ACTIVITY Option Primary Option Menu, 2-8 JOB/SCAN Product AutoEdit Simulation, 2-171 JOB/SCAN-DOCU/TEXT INVOKE JOBSCAN Parameters, 7-12 Simulation/Tape Pull, 2-172 Tape Pull List, 7-12 JOBARRIV Statement. See ON JOBARRIV JOBARRIVAL Job Arrival, 4-1 ON JOBARRIV, 4-1 JOBEND Statement. See ON JOBEND Jobflow Graphic Display, 2-57 JOBID Field Statistics Screen, 2-106 Status Screen, 2-64 Zoom Screen, 2-92 JOBNAME Criteria Screen Filter, 2-149 JOBNAME Field Job Order Execution History, 2-103 Status Screen, 2-64 Zoom Screen, 2-92 JOBNAME Parameter ON DSNEVENT Statement, 4-35 JOBORDER KSL Script, 8-10 Jobs Left Field Simulation/Tape Pull, 2-174 JOBSDD DD Name CTMRFLW Report, 8-34 CTMRPLN Report, 8-45 JOBSTAT Command Status Screen, 2-67, 2-105, 2-107 JODID Field Job Order Execution History, 2-103 Joining Concatenation, 5-12 Journal File Overview, 1-18
Journaling Description, 1-7 JRNL Installation Parameter Journalling, 1-7 JRUN Status Description, 3-9 JSECU ON Statement CODES, 3-113 JTYPE Parameter ON DSNEVENT Statement, 4-35 ON JOBARRIV Statement, 4-40 ON JOBEND Statement, 4-42 ON STEP Statement, 4-44 Julian Date %%$CALCDATE, C-6 JCL Setup, 5-6
K
Keyboard Character Hexadecimal Value, 2-2 KEYS Command ISPF/PDF Primary Option Menu, 2-19 PF12, 2-13 KOA RECORDER Option Primary Option Menu, 2-8, 2-9 KSL AutoEdit Facility, C-1 AutoEdit Variables, 8-4 Commands, 8-3, 8-12 Description, 8-1 Flow Commands, 8-3, 8-13 Overview, 1-11 Principles of Operation, 8-5 Print Commands, 8-3, 8-17 Processing Commands, 8-4, 8-19 Reports, 8-9 Sample Script, 8-6, 8-7 Screen Commands, 8-12 Scripts, 8-2 Special Variables, 8-4 Started Task, 8-2 Syntax, 8-11 Utilities, 8-11 Variable Resolution, C-4 Variables, 8-3, 8-12, 8-22
I 42
Index
KSL ADDMNCND Utility Maybe Jobs, 6-21 KSL Sample Report Example, 8-32 KSL Sample Script Example, 8-24 KSL Script Library Member, 8-6 KSL Variables KSL Script, 8-4, 8-12, 8-22 Special, 8-23
L
L IBRARY Field CMEM Entry Panel, 2-118 L Command Parameter Prompting, 2-180, 2-182, 2-188 L Option Status Screen, 2-69, 2-90 LA Option Primary Option Menu, 2-8 LABEL Command KSL, 8-17 LABEL Control Statement %%LABEL, 5-44 LASER Printer Specified as IMPACT, 8-35 Last Working Date Example, 5-34, 5-41 LATE EXECUTION Status Status Screen, 2-73 LATE Field Job Dependency Network, 2-110 Show Screen Filter, 2-75 LATE ONLY Status Show Screen Filter, 2-77 LATE Status Show Screen Filter, 2-77 Status Screen, 2-73 LATE SUBMISSION Status Status Screen, 2-73 LATE TIME Value SHOUT Parameter, 3-170
LATESUB Value SHOUT Parameter, 3-169 LE Operator AutoEdit Facility, 5-16 Leap Year Definition, 5-24 LEVEL Field Job Dependency Network, 2-110 LIBRARIAN, 3-101, 3-132 Job Documentation, 2-49 Library Maintenance, 3-106, 3-135 LIBRARY Field Calendar Facility Entry Panel, 2-153 CMEM Entry Panel, 2-118 CMEM Rule Exit Option, 2-127 Exit Option Window, 2-52 Parameter Prompting, 2-178, 2-185 Quick Schedule Definition, 2-195 Scheduling Facility Entry Panel, 2-27 Year List Exit Window, 2-163 Library Member MEMNAME Parameter, 3-104 Library Name MEMLIB Parameter, 3-100 Library Name / Job Name Cross Ref CTMXRF Utility, 6-96 LIBRARY Parameter CTMAESIM Utility, 6-45 CTMBLT Utility, 6-55, 6-60 DO FORCEJOB Statement, 3-52, 4-17 DO RULE Statement, 4-21 Save Documentation Window, 2-50 Library/Job Name Report CTMXRF Utility, 6-91 Line Editing Edit Environment, A-1, A-2, B-1, B-2 Example, A-5 Job List Screen, 2-199 Recommendations, A-3 Line Editing Commands, A-2, A-3, B-1, B-2 Line Number Field Quick Schedule Definition, 2-198 LINECNT Parameter CTMRFLW Procedure, 8-34
I 43
Index
LINESIZE Parameter CTMRFLW Report, 8-36 Linking Concatenation, 5-11 LIST Command CTMAESIM Utility, 6-46 LIST Function AutoEdit Simulation, 2-170 LIST Value PREVENT-NCT2 Parameter, 3-140 Local Parameter CTMBLT Utility, 6-55 Local Variable AutoEdit, 5-2 Global Variable, 5-10 JCL Setup, 5-9 LOCATE Command Description, 2-15 Restart Step List Window, 2-101 Location Commands Edit Environment, A-3, B-3 Log File CONTROL-M Log Screen, 2-90 CTMROGR Report, 8-53 IOA Log File, 1-17 IOA Log Screen, 2-144 LOG Mode CMEM Rule Simulation, 4-31 Log Option Status Screen, 2-90 LOG Option Primary Option Menu, 2-6 Status Screen, 2-69 Log Screen CATEGORY Command, 2-146 Commands, 2-145 CONTROL-M Log Screen, 2-90 Description, 2-144 Fields, 2-145 Filtering, 2-146 GROUP Command, 2-146 IOA Log Screen, 2-144 Job Messages, 2-144 MESSAGE TYPE Codes, 2-148 Overview, 1-15
Stacking Multiple Jobs, 2-90 LR Option Primary Option Menu, 2-8 LT Operator AutoEdit Facility, 5-16 LVL Field Job Flow Report, 8-39
M
M JOB Message Type Show Screen Filter, 2-148 M Line Edit Command, A-3, B-2 M1 Option Online Utilities Menu, 2-167 M2 Option Online Utilities Menu, 2-168 M3 Option Online Utilities Menu, 2-172, 7-11 M4 Option Online Utilities Menu, 2-176 M5 Option Online Utilities Menu, 2-194 M6 Option Online Utilities Menu, 2-202 Main Menu Primary Option Menu, 2-5 MAINDAY Table Customization, 6-10 SCHEDULE Library, 6-4 Maintenance Libraries, 3-106, 3-135 Manual JCL Override, 6-93 MANUAL COND Field Job Flow Report, 8-39 MANUAL COND Option Primary Option Menu, 2-6 Manual Conditions Add Condition, 2-143 Description, 2-139 Fields, 2-140 Loading, 6-19 Maybe Job, 6-19 Options, 2-141 Overview, 1-15
I 44
Index
Unscheduled Condition, 6-19 Manual Conditions File Manual Intervention, 6-19 Overview, 1-17 Unscheduled Conditions, 6-20 Manual Confirmation CONFIRM Parameter, 3-23 DO IFRERUN Statement, 3-55 Rerun Confirmation, 2-96 Restart Confirmation, 2-97 Manual IN Condition JCL_OVERIDE Prefix, 6-93 Manual Intervention IN Parameter, 3-88 OUT Parameter, 3-121 Prerequisite Condition, 1-15, 1-24 Manual Reruns MAXRERUN Parameter, 3-146 Rerun Confirmation, 2-96 Restart Confirmation, 2-97 Manual Scheduling Scheduling, Manual, 2-53 Masking Description, 2-3 ON Statement, 4-34 ON Statement CODES, 3-114 Master Console SHOUT Parameter, 3-170 Master Plan Parameter Prompting, 2-185 Master Plan Creation Parameter Prompting, 2-184 Master Plan PREFIX Parameter Prompting, 2-190 Master Prompting Plan Parameter Prompting, 6-35 Master Scheduling Table Parameter Prompting, 6-35 Master Table Creation Parameter Prompting, 2-177 MAX Scrolling Amount, 2-15 MAX Field Conditions/Resources, 2-132
MAX RC Field Job Order Execution History, 2-103 MAXCOMMAND Command KSL, 8-17 MAXDAYS Parameter AUTO-ARCHIVE Parameter, 3-16 Utility CTMTBUPD, 6-82 MAXRERUN Limit Manual Job Rerun, 2-96 MAXRERUN Parameter Example, 3-146 INTERVAL Parameter, 3-146 Logic, 3-146 RERUNMEM Parameter, 3-148 Utility CTMTBUPD, 6-82 MAXRUNS Parameter AUTO-ARCHIVE Parameter, 3-16 Utility CTMTBUPD, 6-82 MAXUSER Parameter MVS Initialization, 6-114 MAXWAIT Parameter, 3-98 Basic Scheduling Criteria, 3-7 Description, 3-97 Example, 3-99 ODATE, 3-97 Utility CTMTBUPD, 6-82 Maybe Dependency Maybe Job, 1-24 Unscheduled Condition, 6-20 Maybe Job ADDMNCND Utility, 6-21 Group Scheduling Table, 6-21 Job Dependency, 1-24 Manual Conditions, 6-19 Prerequisite Condition Prefix, 6-21 Maybe Jobs @ OUT Conditions, 6-21 MAYBEJOB KSL Script, 8-10 MB Line Editing Command, A-3 MCT Simulation, 7-7 MCTSMIND Simulation, 7-7
I 45
Index
MEM/MIS Criteria Log Screen Filter, 2-149 MEMBER Field Job Flow Report, 8-39 MEMBER NAME Parameter AutoEdit Simulation, 2-170 CONTROL-R Simulation, 2-203 Dataset Cleanup, 2-206 Job Dataset List, 2-209 MEMBER Parameter CTMAESIM Utility, 6-45 Save Documentation Window, 2-50 Member Specification %%GLOBAL Control Statement, 5-15 MEMLIB Library JCL Member, 2-70 MEMLIB Parameter AutoEdit Variable, 5-29 Daily JCL Library, 6-41 Description, 3-100 Example, 3-102 OVERLIB Parameter, 3-131 Started Task, 3-100, 3-101 System Variables, 5-3 Utility CTMTBUPD, 6-82 MEMNAME Criteria Log Screen Filter, 2-149 Status Screen Filter, 2-76 MEMNAME Field CMEM Rule, 4-5 Global View Status Screen, 2-80 Group Entity, 2-45 Job Name Matching, 4-6 Job Order Execution History, 2-103 Quick Schedule Definition, 2-198 Show Screen Filter, 2-76 MEMNAME Parameter CTMBLT Utility, 6-57 D-CAT Parameter, 3-31 Description, 3-104 Example, 3-105 Group Entity, 2-45 MAXRERUN Parameter, 3-146 OVERLIB Library, 3-131 Scheduling Definition, 2-34
Utility CTMTBUPD, 6-82 MEMNAME Value CMEM On Spool Job, 4-5 CTMRCAL Calendar, 6-76 DOCMEM Default, 3-81 Job Scheduling, 6-17 Simulation, 7-4 MEM-OVERWRITE Parameter CTMBLT Utility, 6-56 MEMSYM Control Statement %%MEMSYM, 5-19 MERGE Value CTMRCAL Utility, 6-76 Message Content Group Name, 3-86 MESSAGE Field Log Screen, 2-145 Parameter Prompting, 2-188, 2-192 Message File Simulation, 7-6 Message Generation DO SHOUT Statement, 3-66 DO Statement, 3-44 SHOUT Parameter, 3-169 Message Handling Log File, 1-15, 2-144 Shout Facility, 1-6 Message Line Screen Layout, 2-12 MESSAGE Parameter DO SHOUT Statement, 4-25 Message Route Codes MVS WTO, D-1 MESSAGE TYPE Screen Filter, 2-148 Message Type Criteria Log Screen Filter, 2-148 MINIMUM Parameter CONFCAL Parameter, 3-21 DATES Parameter, 3-33 DAYS Parameter, 3-38 Description, 3-106 Example, 3-107 MONTHS Parameter, 3-108 PDS Parameter, 3-135
I 46
Index
WDAYS Parameter, 3-192 M-INT Message Type Show Screen Filter, 2-148 MINUS Operator %%MINUS, 5-22 MISSION DEF Option IOA Primary Option Menu, 2-8 MISSION STATUS Option IOA Menu, 2-8 Mission, CONTROL-B CTB STEP Parameter, 3-29 ML Line Edit command, B-2 ML Line Edit Command, A-3 MM Line Edit Command, A-3, B-2 MODE Parameter CMEM Rule, 4-31, 6-110 Example, 4-32 MODE Report CTMROGR Report, 8-54 Monochrome Terminal Color Support, 2-2 Graphic Jobflow Screen, 2-58 Month Field Calendar Definition, 2-158 Job Scheduling Plan Screen, 2-60 MONTHS Parameter DATES Parameter, 3-33, 3-108 Description, 3-108 Example, 3-108 Job Scheduling Definition, 6-88 MINIMUM Parameter, 3-106 PDS Parameter, 3-135 Periodic Value, 3-38, 3-192 Move Commands Edit Environment, A-3, B-2 MPP Master Prompting Plan, 6-35 MS Line Edit command, B-2 MS Line Edit Command, A-3 MS Parameter SHOUT Parameter, 3-171 MSG Library Help Member, 2-17 MSG STATISTICS Option IOA Primary Option Menu, 2-9
MSGCLASS Parameter SYSDATA Output Class, 1-21 MSGCLASS Sysout CMEM On Spool Job, 4-4 DO SYSOUT Statement, 3-72 SYSOUT Parameter, 3-176, 3-178 MSGLEVEL=1,1 ON DSNEVENT Statement, 4-37 MSTJCLB Parameter CTMFETCH CLIST, 6-39 Multi-Screen Control Transfer Command, 2-11 MVS Initialization MAXUSER Parameter, 6-114 RSVNONR Parameter, 6-114 RSVSTRT Parameter, 6-114 MVS Restart @ Character, 6-21 OUT Parameter, 3-123 procstep.pgmstep, 3-124 MVS WTO Codes Descriptor, D-2 Message Route, D-1
N
N (New) Parameter Conditions Resources, 6-84 N Option Status Screen, 2-70 N Qualifier DO Statement, 3-114 NAME Field Change Resource Window, 2-138 Job Dependency Network, 2-110 Manual Conditions Window, 2-143 Status Screen, 2-64 NAME Parameter CTB STEP Parameter, 3-29 NE Operator AutoEdit Facility, 5-16 Nested Expressions JCL Setup, 5-17 NET Argument REFRESH Command, 2-111
I 47
Index
NET Option Status Screen, 2-70, 2-108 NEW COND Command Manual Conditions, 2-143 New Day Procedure Implementation, 6-2 Work Flow, 6-101 New Day Processing Checkpoint Restart, 6-7 Checkpointing, 6-10 Description, 1-4 Implementation, 6-7 Job Ordering, 6-2 Programs, 6-12 Recommendations, 6-8 Sample, 6-4 System Date, 6-101 User Daily Job, 6-3 Work Flow, 6-3, 6-5 NEW PASSWORD Field IOA Entry Panel, 2-4 NEWJOB Parameter Simulation, 7-4 NEWMNCND KSL Script, 8-10 NEXT Command Job Scheduling Plan, 2-60 Rule Definition, 2-124 Scheduling Definition, 2-46, 2-51 NEXT TIME Field Zoom Screen, 2-93 NEXT Value Schedule Date, 3-47, 3-120 NEXTYEAR Command Calendar Definition, 2-162 Night Exception Report REP5EXP Utility, 8-10 Night Schedule Field Simulation/Tape Pull, 2-174 Night Schedule Report CTMRNSC Report, 8-51 Sample, 8-53 NJE Field Zoom Screen, 2-93
NJE Job CMEM On Spool Job, 4-3 NJE JOB Status Status Screen, 2-73 NJE Network CONTROL-M Monitor, 1-8 NODACHK PARM=, 6-74 node ID JES2, 3-101 NODE NAME Field Zoom Screen, 2-92 Non-Color Display Monochrome Terminal, 2-2 Non-Periodic Calendar DCAL Parameter, 3-36 WCAL Parameter, 3-190 Non-Periodic Scheduling Format, 3-36, 3-190 NOT CATLGD 2 CMEM, 4-1 DO STOPJOB Statement, 4-28 Job Status, 2-72 REP5NCT2 Utility, 8-10 NOT FOUND Status Status Screen, 2-72 NOT OK Status Show Screen Filter, 2-76 NOT STARTED Status Status Screen, 2-72 NOT SUBMITTED Status JNSUB Reason, 5-5 Status Screen, 2-72 NOTOK Status Description, 3-9 Group Entity, 2-43, 2-45 ON Statement, 3-112 NOTOK Value ON Statement CODES, 3-113 SHOUT Parameter, 3-169 NR Field Quick Schedule Definition, 2-198 NULL Value %%$PARSE Function, C-10
I 48
Index
Numeric Pattern %%$PARSE Function, C-13
O
O (Old) Parameter Conditions Resources, 6-84 O Option Job List Screen, 2-34 Status Screen, 2-113 Table List Screen, 2-30, 2-53 OC Option Primary Option Menu, 2-9 OCCUR NO Suffix AutoEdit Parameter, 6-41 OCCUR NO. Field Parameter Prompting, 2-187, 2-193 ODAT IN Parameter, 3-87 Prerequisite Condition, 1-23 Schedule Date, 3-46, 3-120 ODAT Parameter CLIST CTMCJOBS, 6-15 ODATE CTMAESIM Utility, 6-45 Date Control Record, 6-11 Definition, 1-18 DO FORCEJOB Statement, 3-52 Example, 5-30 System Variable, 5-6 ODATE Field Global View Screen, 2-80 Job Order Execution History, 2-103 Log Screen, 2-145 Parameter Prompting, 2-191 Scheduling Confirmation, 2-54 Show Screen Filter, 2-78 Status Screen, 2-64 Zoom Screen, 2-92 ODATE Parameter AutoEdit Simulation, 2-170, 8-57 CONTROL-R Simulation, 2-204 Dataset Cleanup, 2-206 Job Dataset List, 2-209 OF Field Parameter Prompting, 2-183
OK Status Description, 3-9 Group Entity, 2-43, 2-45 ON Statement, 3-112 Post-Processing Parameters, 3-9 OK Value ON Statement CODES, 3-113 SHOUT Parameter, 3-169 OLDJOB Parameter Simulation, 7-5 ON Block DO Statement, 3-112 ON Statement, 3-111 ON CODE Parameter ON Statement, 3-110 ON DSNEVENT Statement And/Or/Not Parameter, 4-37 CMEM Parameters, 4-9 CMEM Rule, 4-1, 4-3, 4-33, 4-35 CMEM Rule Definition, 2-122 Dataset Event, 4-35 Example, 4-39 MSGLEVEL=1,1, 4-37 RUNTSEC=TRIGGER, 4-50 ON Field Simulation/Tape Pull, 2-173 ON GROUP-END Parameter Definition, 3-118 Group Entity, 2-45, 3-3 ON JOBARRIV Rule CMEM Rule, 4-3 DO FORCEJOB Statement, 4-18 ON JOBARRIV Statement CMEM Parameters, 4-9 CMEM Rule, 4-1, 4-4, 4-33, 4-40 CMEM Rule Definition, 2-122 Example, 4-41 Job Arrival, 4-1 ON JOBEND Statement CMEM Parameters, 4-9 CMEM Rule, 4-1, 4-33, 4-42 CMEM Rule Definition, 2-122 Example, 4-43 Job End, 4-1 RUNTSEC=TRIGGER, 4-50
I 49
Index
ON OUTPUT Q Status Show Screen Filter, 2-76 ON OUTPUT QUEUE Status Status Screen, 2-73 ON PGMST ANYSTEP DO CTBRULE Statement, 3-50 ON Statement, 3-110 ON PGMST Indicator Zoom Screen, 2-93 ON PGMST Parameter ON Statement, 3-110 ON PGMST Statement Combinatorial Logic, 2-93 Step Range, 3-174 ON REQUEST Status Show Screen Filter, 2-77 On Spool Job AutoEdit Statement, 4-7 CMEM Facility, 1-9 CMEM Rule, 4-2 Components, 4-4 DO FORCEJOB Statement, 4-18 Forcing Logic, 4-6 Job Flow, 4-5 MEMNAME Parameter, 3-104 NJE Job, 4-3 ON JOBARRIV Statement, 4-41 SETVAR Statement, 4-7 Status, 2-71 TYPERUN=HOLD, 4-4, 4-6 ON Statement CMEM Parameters, 4-9 CMEM Rule, 4-33 CMEM Rule Definition, 2-122 Codes, 3-113 Combinatorial Logic, 4-34 Conditional Processing, 3-9 Description, 3-110 Example, 3-113, 3-115 Logic, 3-111, 3-114 Masking, 4-34 Multiple, 3-111 Specified Step, 3-112 ON STEP Statement CMEM Parameters, 4-9
CMEM Rule, 4-1, 4-44 CMEM Rule Definition, 2-122 Online Facility Calendar Facility, 2-151 Documentation, 2-48 Exiting, 2-11 Help Screen, 2-17 Overview, 1-13, 2-1 Screen Layout, 2-12 Status Screen, 2-61 Tracking and Control, 1-14 TSO Application, 2-21 Under ISPF, 2-19 Online Monitor Activating, 6-114 Deactivating, 6-114 Description, 6-113 Online Utilities Menu Utility Screen, 1-16, 2-164 OP Parameter SYSOUT Parameter, 3-176 OPENFILE Command KSL, 8-19 OPER Value DO SHOUT Destination, 3-66 SHOUT Parameter, 3-170 OPER2 Value DO SHOUT Destination, 3-66 SHOUT Parameter, 3-170 Operations Guide CONTROL-M, 6-100 Operator Command DUE OUT Adjustment, 6-112 F CONTROLM,CTMX004, 6-112 F CONTROL-M,DEADLINE, 6-112 F CONTROLM,INTERVAL=, 6-101 F CONTROLM,NEWCONLIST, 6-108 F CONTROLM,NEWDEST, 6-112 F CONTROLM,PROP, 6-112 F CTMCMEM, 6-107 F CTMCMEM,D=library, 6-109 F CTMCMEM,DISPLAY, 6-109 F CTMCMEM,INTERVAL=, 6-110 F CTMCMEM,LOG=, 6-110 F CTMCMEM,NEWSECDEF, 6-111
I 50
Index
F IOAOMONx,CANCELUSER, 6-115 F IOAOMONx,DISPLAY, 6-115 IOACND Utility, 6-99 IOAOPR Utility, 6-113 Online Monitor, 6-115 P CONTROLM, 6-100 P CTMCMEM, 6-107 P IOAOMONx, 6-114 PRIORITY Adjustment, 6-112 S CONTROLM, 6-100 S CONTROLO,TYPE=, 6-106 S CTMCMEM, 6-105, 6-106, 6-107 S IOAOMONx, 6-114 S IOASTERM, 6-105 OPT Command Status Screen, 2-66 OPT Field Conditions/Resources, 2-132 Manual Conditions, 2-140 Rule List Screen, 2-119 opt Parameter DO COND Statement, 3-47 OUT Parameter, 3-121 OPT Parameter DO SYSOUT Statement, 3-70 Option ? Status Screen, 2-69, 2-84 Option 0 Primary Option Menu, 2-6 Option 1 Parameter Prompting Entry Panel, 2-176 Parameter Prompting Type 1 Menu, 2-177 Parameter Prompting Type 2 Menu, 2-184 Primary Option Menu, 2-6 Year List, 2-157 Option 2 Parameter Prompting Entry Panel, 2-176, 2-184 Parameter Prompting Type 1 Menu, 2-177, 2-182 Parameter Prompting Type 2 Menu, 2-184, 2-189
Primary Option Menu, 1-13, 2-6, 2-22, 2-27 Option 3 Parameter Prompting Type 2 Menu, 2-184, 2-190 Primary Option Menu, 1-14, 2-6, 2-61 Option 4 Primary Option Menu, 1-15, 2-6, 2-131 Option 5 Primary Option Menu, 1-15, 2-6, 2-144 Option 6 Online Utilities, 2-19 Primary Option Menu, 1-16, 2-5, 2-6, 2-164 Option 7 Primary Option Menu, 1-15, 2-6, 2-139 Option 8 Primary Option Menu, 1-16, 2-6, 2-152 Option A IOA Primary Option Menu, 2-8 Job List Screen, 2-199 Manual Conditions, 2-141, 6-20 Parameter Prompting, 2-181, 2-189 Status Screen, 2-70 Why Screen, 2-86 Option B Calendar List, 2-154 CMEM Table List, 2-119 Job List Screen, 2-199 Table List Screen, 2-30 Option BA Primary Option Menu, 2-8 Option BB Primary Option Menu, 2-8 Option BK Primary Option Menu, 2-8 Option BM Primary Option Menu, 2-8 Option BR Primary Option Menu, 2-8 Option BV Primary Option Menu, 2-8 Option C Job List Screen, 2-34, 2-199 Primary Option Menu, 1-14, 2-6, 2-115, 2-117
I 51
Index
Status Screen, 2-69 Option Code DO SYSOUT Statement, 3-70 SYSOUT Parameter, 3-176 Option D Calendar List, 2-154 CMEM Rule List, 2-120 CMEM Table List, 2-119, 2-128 Conditions/Resources, 2-136 Event List Screen, 6-26 Job List Screen, 2-34, 2-199 Parameter Prompting, 2-181, 2-189 Status Screen, 2-69, 2-88, 2-113 Table List Screen, 2-31, 2-56 Year List, 2-156 Option D1 Utilities Menu, 2-165 Option D2 Utilities Menu, 2-165 Option D3 Utilities Menu, 2-165 Option D4 Utilities Menu, 2-165 Option E Manual Conditions, 2-141 New Day Processing, 6-102 Status Screen, 2-70 Option F AutoEdit Variable, 5-29 CMEM Table List, 2-119, 2-129 IOA Menu, 2-8 Job List Screen, 2-34 Manual Scheduling, 2-53 Restart Step List Window, 2-101 Status Screen, 2-69 Table List Screen, 2-26, 2-31 Option Field Job Dependency Network, 2-110 Quick Schedule Definition, 2-198 Status Screen, 2-64 Option G Status Screen, 2-69 Table List Screen, 2-31, 2-57, 8-33 Option H Status Screen, 2-69
Option I CMEM Rule List, 2-120 Event List Screen, 6-26 Job List Screen, 2-34, 2-199 Parameter Prompting, 2-181, 2-189 Option I1 Online Utilities Menu, 2-164, 2-166 Option IP Primary Option Menu, 2-6 Option J Job List Screen, 2-34 Status Screen, 2-70 Option L Status Screen, 2-69, 2-90 Option LA Primary Option Menu, 2-8 Option LR Primary Option Menu, 2-8 Option M IOA Menu, 2-8 Job List Screen, 2-199 Option M1 Online Utilities Menu, 2-164, 2-167 Option M2 Online Utilities Menu, 2-164, 2-168 Option M3 Online Utilities Menu, 2-164, 2-172, 7-11 Option M4 Online Utilities Menu, 2-164, 2-176 Option M5 Online Utilities Menu, 2-164, 2-194 Option M6 Online Utilities Menu, 2-164, 2-202 Option N Status Screen, 2-70, 2-108 Option O Group Scheduling, 2-53 Job List Screen, 2-34 Manual Scheduling, 2-53 Restart Step List Window, 2-101 Status Screen, 2-70 Option OA IOA Primary Option Menu, 2-9
I 52
Index
Option OC Primary Option Menu, 2-9 Option OL IOA Primary Option Menu, 2-9 Option OM IOA Primary Option Menu, 2-9 Option OR IOA Primary Option Menu, 2-9 Option OS IOA Primary Option Menu, 2-9 Option OV Primary Option Menu, 2-9 Option P Job List Screen, 2-34, 2-59, 2-199 Option PRINT Utilities Menu, 2-165 Option R IOA Menu, 2-8 Job List Screen, 2-199 Parameter Prompting, 2-181, 2-189 Status Screen, 2-69, 2-96, 2-97 Option R1 Online Utilities Menu, 2-164, 2-203 Option R2 Online Utilities Menu, 2-164, 2-205 Option R3 Online Utilities Menu, 2-208 Option R4 Online Utilities Menu, 2-165 Option S CMEM Rule List, 2-120 CMEM Table List, 2-119 End User Job Order, 2-202 Event List Screen, 6-26 Job List Screen, 2-34 Job Order Execution History, 2-103 Status Screen, 2-69, 2-105 Table List Screen, 2-30 Year List, 2-156 Option T IOA Menu, 2-8 Restart Step List Window, 2-101 Option T1 Utilities Menu, 2-165
Option TI IOA Primary Option Menu, 2-9 Option TP IOA Menu, 2-9 Option TR IOA Menu, 2-9 Option TV IOA Menu, 2-9 Option U IOA Menu, 2-8 Status Screen, 2-70 Option U1 Online Utilities Menu, 2-164, 2-209 Option V Status Screen, 2-69, 2-102 Option W Status Screen, 2-70 Year List, 2-157 Option X Online Utilities Menu, 2-164 Primary Option Menu, 2-6 Option Z Status Screen, 2-69 Options Activate, 2-70 AUTOMATION LOG, 2-9 AUTOMATION OPTION, 2-9 BALANCING DEF, 2-8 BALANCING STATUS, 2-8 CALENDAR DEF, 2-6 Calendar List, 2-154 CHANGE, 2-136, 2-137 CHECK IN EXT VOL, 2-9 CLEANUP, 2-164 CMEM, 2-115, 2-117 CMEM DEFINITION, 2-6 CMEM Rule List, 2-120 CMEM Table List, 2-119 COND/RES, 2-6 CONFIRM, 2-69 CONTROL-T SIMUL, 2-165 COSMOS STATUS, 2-9 Cross Memory, 2-13 CTM WORKLOAD DEF, 2-8 CTMEXEC, 2-184, 2-190
I 53
Index
CTMFETCH, 2-184, 2-189 CTMQUICK, 2-195 DB VARIABLE DEF, 2-8 Define Parameters and Conditions, 2-178, 2-181 Define Parameters in Master Plan, 2-189 DEL, 2-69 DELETE, 2-26, 2-31, 2-34, 2-56, 2-88, 2-119, 2-120, 2-128, 2-136, 2-156, 2-181, 2-189 Delete Condition/Resource, 2-136 DOCU/TEXT, 2-164 EDIT, 2-34, 2-70 EXIT, 2-6, 2-164 FORCE, 2-26, 2-31, 2-34, 2-53, 2-129 FORCE OK, 2-113 FREE, 2-69 GRAPHIC FLOW, 2-26, 2-31, 2-57 Graphic Jobflow, 8-33 GROUP, 2-69 HOLD, 2-69 INFO, 2-6 INQ/UPD MEDIA DB, 2-9 INSERT, 2-25, 2-34, 2-120, 2-157, 2-181, 2-189, 6-26 IOA INFO, 2-6 IOA Primary Option Menu, 2-7 ISPF Application, 2-5 ISPF PACK, 2-22, 2-151 ISPF Primary Option Menu, 2-19 JCL, 2-34, 2-70 Job Activation, 2-70 Job List, 2-25, 2-34, 2-199 JOB ORDER ISSUE, 2-164 Job Reactivate, 2-70 JOB SCHED DEF, 2-6 JOB STATUS, 2-6 JOB/PIPE ACTIVITY, 2-8 KOA RECORDER, 2-9 KOA RECORDER:, 2-8 LOG, 2-6, 2-69, 2-90 M4, 2-176 M6, 2-202 MANUAL COND, 2-6 Manual Conditions, 2-141
Master Plan, 2-184 Master Table Creation, 2-177 MISSION DEF, 2-8 MISSION STATUS, 2-8 MSG STATISTICS, 2-9 NET, 2-70 ORDER, 2-26, 2-30, 2-34, 2-53, 2-119 PACK, 2-22, 2-151 Parameter Definition, 2-177 Parameter Prompting, 2-164, 2-177, 2-181 Parameter Updating, 2-177 PC PACKET STATUS, 2-8 PLAN, 2-26, 2-34, 2-59 Prerequisite Condition, 2-164, 2-177 Primary Option Menu, 2-7 PRINT, 2-165 QUICK SCHEDULE, 2-164 R3, 2-208 Reactivate, 2-70 RECIPIENT TREE, 2-8 REPORT DEF, 2-8 RERUN, 2-69, 2-96 RESTORE, 2-165 RULE ACTIVITY, 2-8 RULE DEFINITION, 2-8, 2-9 RULE STATUS, 2-8, 2-9 Status Screen, 2-69, 2-105 Table List Screen, 2-30, 8-33 TERMINATE, 2-70 TSO, 2-6 UNDELETE, 2-70 UPDATE, 2-181, 2-189 USER INTERFACE, 2-164 USER REPORTS, 2-8 UTILITIES, 2-5 VARIABLE DATABASE, 2-9 VIEW, 2-69, 2-102 WHY, 2-69, 2-84 WORKLOAD, 2-70 Year List Screen, 2-156 ZOOM, 2-69 OR Option IOA Primary Option Menu, 2-9
I 54
Index
Order a Job DO FORCEJOB Statement, 3-52 DO Statement Action, 3-44 Next Day, 5-35 Order Daily Jobs Field Simulation/Tape Pull, 2-174 Order ID Multiple Orders, 1-21 ORDER ID Parameter CONTROL-R Simulation, 2-203 Dataset Cleanup, 2-206 ORDER Option CMEM Table List, 2-119 Job List Screen, 2-26, 2-34 Manual Scheduling, 2-53 Table List Screen, 2-26, 2-30 ORDER Parameter User Daily Job (CTM), 6-72 ORDER Statement CTMJOB Utility, 6-71 ORDERID Command Status Screen, 2-67 ORDERID Field Job Order Execution History, 2-103 Status Screen, 2-65 Zoom Screen, 2-92 Ordering Jobs End User Job Order, 2-202 Job List Screen, 2-34 Job Ordering Utility, 2-167 Next Day, 5-35 Overview, 1-20 Ordering Rules CMEM Rule Table, 2-129 ORDERING Status Status Screen, 2-74 Original Scheduling Date ODATE, 1-18, 3-97, 5-6 OUT Condition Group Entity, 3-122 OUT CONDITION @#-procstep.pgmstep, 3-124 OUT Conditions Job Dependency, 2-108
OUT Parameter Description, 3-120 DO COND Statement, 3-49, 3-124 Example, 3-125 Job Chain, 3-128 Logic, 3-122 MVS Restart, 3-123 Prerequisite Condition, 3-88 Quick Schedule Definition, 2-194 OUT Prerequisite Condition IOALDNRS Utility, 6-19 OUT Statement Prerequisite Condition, 1-22 OUTLIB Parameter CTMBLDAE Utility, 6-49 Output Class SYSDATA, 1-21 Sysout, 3-178 OV Option Primary Option Menu, 2-9 OVERLIB Field CNGOVRLB Utility, 8-10 OVERLIB Library JCL Member, 2-70, 3-131 MEMNAME Parameter, 3-131 OVERLIB Parameter AutoEdit Variable, 5-29 CTMAESIM Utility, 6-45 Description, 3-131 JCL Member Name, 2-170 Utility CTMTBUPD, 6-82 Overnight Execution Graph CTMROGR Report, 8-53 OVERRIDE DAILY PLAN Field Parameter Prompting, 2-190 OVERRIDE DAILY PLAN Options FETCH A PLAN Screen, 6-40 OVERTLIB Parameter Example, 3-132 Overwrite Confirmation Quick Schedule Definition, 2-197 OWNER AutoEdit Parameter Job Dataset List, 2-209 OWNER Field Job Order Execution History, 2-103
I 55
Index
Quick Schedule Definition, 2-196 Show Screen Filter, 2-78 Status Screen, 2-64 OWNER Parameter AutoEdit Simulation, 2-170 CMEM Rule, 4-48 CONTROL-R Simulation, 2-204 CTMAESIM Utility, 6-45 Dataset Cleanup, 2-206 Description, 3-133 DO RULE Statement, 4-21 Example, 3-134 Utility CTMTBUPD, 6-82
P
P Option Job List Screen, 2-34 P Parameter Conditions Resources, 6-84 PA01-PA03 Command KSL, 8-13 PA1 Key ABORT Command, 2-14 AutoRefresh Mode, 2-14 Auto-Refresh Mode, 2-18 PA2 Key PRINT Command, 2-14 REFRESH Command, 2-14 PA3 Key Key Definition, 2-14 PAGE Scrolling Amount, 2-15 PAGES Field Job Order Execution History, 2-103 PAGESEQ Parameter CTMRFLW Report, 8-36 PAGESIZE Command KSL, 8-18 PAGESIZE Parameter CTMRFLW Report, 8-36 PANVALET, 3-101, 3-132 Job Documentation, 2-49 PARAM PROMPTING Option Online Utilities Menu, 2-164
Parameter Definition Parameter Prompting, 2-177, 2-180, 2-187 PARAMETER LIBRARY Parameter AutoEdit Simulation, 2-170 Parameter Passing MEMLIB Parameter, 3-101 Parameter Prompting AutoEdit Parameter, 2-180, 2-183 Daily Prompting Tables, 2-182 Daily Scheduling Table, 6-36 Daily Table, 2-182, 6-33 Define Parameters Option, 2-178 Definition Phase, 6-35 EXEC Phase, 6-37 FETCH Phase, 6-36 File Prefix, 2-177 IRS Tape Example, 6-30 Master Plan, 2-185 Master Table, 2-177 New Method, 6-32 Old Method, 6-30 Scheduling Table, 6-35 Type 1, 2-177, 6-29 Type 2, 2-184, 6-35 Parameter Syntax CTMBLT Utility, 6-54 Parameter Table Post-Processing, 6-67 Scheduling Criteria, 6-65 Parameter Update Parameter Prompting, 2-177 Parameters Basic Scheduling, 2-38 CMEM Rule Facility, 2-122 General Job, 2-37 Group Scheduling, 2-44 Job Scheduling, 1-3 Multiple Occurrences, 2-36 Post-Processing, 2-40 Runtime Scheduling, 2-39 Scheduling Definition, 2-36 Summary, 3-3 Tape Pull List, 7-11
I 56
Index
Parenthesis () Characters, 3-87 PARM Field Parameter Prompting, 2-180 PARM Library Date Control Record, 6-5, 6-10 PARM NAME Field Parameter Prompting, 2-187, 2-192 PARM Parameter CTMRCAL Utility, 6-76 PARM PREFIX Field Parameter Prompting, 2-180, 2-183, 2-188, 2-192 Update Parameter Values, 2-192 PARM= NODACHK, 6-74 Parsing Logic %%$PARSE Function, C-14 Parsing Template %%$PARSE Function, C-11, C-13, C-16 Parsing Text %%$PARSE Function, C-9 Passing Arguments ARGUMENTS Parameter, 3-29 DO CTBRULE Statement, 3-50 Password Online Facility, 2-4 PAUSE Command KSL, 8-17 PC PACKET STATUS Option IOA Primary Option Menu, 2-8 PDS Parameter CONFCAL Parameter, 3-21 DATES Parameter, 3-33 DAYS Parameter, 3-38 Description, 3-135 MINIMUM Parameter, 3-106 MONTHS Parameter, 3-108 WDAYS Parameter, 3-192 PDSE Library, 3-135 PDSE-type Libraries MINIMUM Parameter, 3-106 PDSE-Type Library Date Control Records, 6-8
PDSMAN $$$SPACE Members, 2-57, 2-128, 2-161 PENDING Conditions Manual Conditions, 2-140 PERIODIC Reserved String, 2-159 Periodic Calendar DCAL Parameter, 3-37 Example, 3-38, 3-193 WCAL Parameter, 3-191 Periodic Scheduling Format, 3-37, 3-191 Periodic Value MONTHS Parameter, 3-108 PF01/PF13 HELP Command, 2-13, 2-17 PF01-PF24 Command KSL, 8-13 PF02/PF14 ISPF SPLIT Command, 2-13 SHOW Command, 2-13 Show Screen Filter, 2-74, 2-145 SPLIT Command, 2-19 PF03/PF15 Calendar Definition, 2-162 CMEM Rule Definition, 2-126 END Command, 2-13 Scheduling Definition, 2-51 Show Screen Filter, 2-79, 2-150 Year List, 2-163 PF04/PF16 Box Color, 2-58 CMEM Rule Command, 2-124 CMEM Rule Exit Option, 2-127 Global View Screen, 2-79 Job List Exit Window, 2-52 REFRESH Command, 2-79 RESET Command, 2-13 Status Screen, 2-67, 2-79 Year List, 2-163 PF05/PF17 FIND Command, 2-13, 2-16, 2-57 PF06/PF18 =6 Command, 2-13, 2-21
I 57
Index
PF07/PF19 Filtering, 2-150 Show Screen Filter, 2-78 UP Command, 2-13, 2-15 PF08/PF20 DOWN Command, 2-13, 2-15 Filtering, 2-150 Show Screen Filter, 2-78 PF09/PF21 SWAP Command, 2-19 PF10/PF22 Calendar Definition, 2-162 Scheduling Definition, 2-51 Show Screen Filter, 2-79, 2-150 PF11/PF23 Calendar Definition, 2-162 Log Screen, 2-145 Scheduling Definition, 2-51 Status Screen, 2-67 PF12 KEYS Command, 2-13 PF24 SHPF Command, 2-13 PFKey Definition Online Facility, 2-13 PRINT Command, 2-19 TSO CTMTTRA, 2-21 PFKey Display SHPF Command, 2-14 PGMST Parameter ON Statement, 3-110 PGMSTEP Parameter ON DSNEVENT Statement, 4-36 ON STEP Statement, 4-45 pgmstep.procstep DO IFRERUN Statement, 3-54 PIPE Field Show Screen Filter, 2-78 PIPE Parameter CONTROL-M/WorkLoad, 3-1, 3-8 Description, 3-137 Summary, 2-39 WorkLoad Implementation, 6-23 Pipe Participant Definition, 1-12
PIPE Statement Deleted via Zoom Screen, 6-23 Pipes CONTROL-M/WorkLoad, 1-12 Job Scheduling Definition, 1-12 Job-Related Considerations, 6-23 Plan Description Parameter Prompting, 2-186 Plan Name Parameter Prompting, 2-190 PLAN NAME Master Prompting Plan PREFIX, 2-190 PLAN NAME Field Parameter Prompting, 2-192 Plan Name Prefix Parameter Prompting, 2-185 PLAN NAME PREFIX Parameter Prompting, 2-185 Plan Option Job List Screen, 2-59 PLAN Option Job List Screen, 2-26, 2-34 PLAN ORDERED ALREADY Field Parameter Prompting, 2-191 Plan Selection Screen Parameter Prompting, 2-191, 2-193 PLANID Parameter CTMEXEC CLIST, 6-39 CTMFETCH CLIST, 6-38 Daily Scheduling Table, 6-36 PLANID Suffix CTMFETCH CLIST, 6-38 POOL DEFINITION Option IOA Primary Option Menu, 2-9 Post-Processing CONTROL-M Monitor, 1-8 Parameter Table, 6-67 System Variable, 5-8 Post-Processing Parameters DO SET Statement, 3-165 Group Entity, 2-45 Scheduling Definition, 2-40 Summary, 3-9 Post-processing Statement Error, 3-9
I 58
Index
Pound Symbol Hex Value, 2-2 PPF2DAY Job JCL Library, 6-42 PPF2DEL Job JCL Library, 6-41 Precedence AutoEdit Variable Assignment, 5-14 Predecessor Job Job Dependency, 1-26, 2-108 REFRESH Command, 2-111 PREDESR Parameter CTMRFLW Procedure, 8-34 Prefix Maybe Job Prerequisite Condition, 6-21 PREFIX Field Conditions/Resources, 2-133 Manual Conditions, 2-140 Prefixing Description, 2-3 PREREQ CONDITION Option Online Utilities Menu, 2-164 Prerequisite Condition % Sign, 8-22 Add/Check/Delete Utility, 2-166 Adding, 2-134, 2-143, 3-121 CMEM Rule, 4-2 Conditions/Resources, 2-131 CONTROL-M Files Prefix, 2-177 Cross Reference, 8-10, 8-33, 8-41 Date Reference, 1-23, 3-48 Deleting, 1-24, 2-136, 2-141, 3-121 Description, 1-22 DO COND Statement, 3-46, 4-15 DO Statement, 3-44 Erasing, 2-136, 2-141 Example, 1-23, 3-90, 3-126 Format, 2-195 Group Entity, 1-23, 3-122 IMS-ACTIVE, 3-127 IN Parameter, 3-87 IOACDDR Utility, 6-26 IOACND Utility, 6-97 IOALDNRS Utility, 6-19 IRS-TAPE-ARRIVED, 6-30
Job Dependency, 1-23, 1-26 Job Flow Report, 8-33 Manual Conditions, 1-15, 2-139 Manual Intervention, 1-24, 3-88, 3-121 Maybe Job, 6-21 OUT Parameter, 3-120 Parameter Prompting, 2-177, 2-180 Quick Schedule Definition, 2-196, 2-198 RUN-%%PLANID, 6-37, 6-40 Runtime Criteria, 1-6 Show Screen Filter, 2-78 STAT, 1-23 Unscheduled Condition, 6-21 Why Screen, 2-86 PREV Command Job Scheduling Plan, 2-60 Rule Definition, 2-124 Scheduling Definition, 2-46, 2-51 PREV keyword FIND command, 2-46 PREV Value FIND Command, 2-16 IN Parameter, 3-87 Schedule Date, 3-46, 3-120 PREVENT-NCT2 Parameter Description, 3-140 Example, 3-141 Utility CTMTBUPD, 6-82 PREVYEAR Command Calendar Definition, 2-162 Primary Option Menu Description, 2-5 Option 4, 2-131 Option 6, 2-164 Option 7, 2-139 Option 8, 2-152 Option S, 2-144 Options, 2-6 PRINT Command PA2 Key, 2-14 PFKey Definition, 2-19 Print Commands KSL, 8-3, 8-17 PRINT Option Utilities Menu, 2-165
I 59
Index
Print Screen CTMSCALL Utility, 8-9 KSL Command, 8-18 PRINTER Parameter CTMRFLW Report, 8-35 Printing Sysout, 3-72, 3-178, 3-180 PRINTLINE Command KSL, 8-18 PRINTNEWPAGE Command KSL Command, 8-18 PRINTSCREEN Command KSL, 8-18 PRIOR RUN Status Status Screen, 2-72 Priority Conditions/Resources, 2-132 Global Variable, 5-10 Local Variable, 5-10 Overview, 1-26 Runtime Criteria, 1-5 Sysout Operations, 3-180 SYSOUT Operations, 3-73 User-Defined Variable, 5-4 PRIORITY Adjustment Operator Command, 6-112 PRIORITY Field Show Screen Filter, 2-78 PRIORITY Parameter Description, 3-142 Example, 3-143 Job Flow, 1-26 Logic, 3-142 Utility CTMTBUPD, 6-82 PRM Parameter DO SYSOUT Statement, 3-70 PRMTBLB Parameter CTMFETCH CLIST, 6-38 PROBLEMS READING SYSOUT Status Status Screen, 2-73 Processing Commands KSL, 8-4, 8-19 PROCST Parameter ON Statement, 3-110
PROCSTEP Parameter ON DSNEVENT Statement, 4-36 ON STEP Statement, 4-44 PROD Mode CMEM Rule Simulation, 4-31 Production Delay MAXWAIT Parameter, 3-97 Productivity Tools Option OA, 2-9 Profile Customization, 2-1 Programmer Information SHOUT Parameter, 3-170 PROMPT IND Field Parameter Prompting, 2-188 PROMPT Library %%LIBSYM Statement, 6-34 Prompting Plan AutoEdit Variables, 6-29, 6-35 PROPAGATE Argument REFRESH Command, 2-111 PRTDBG DD Statement PA2 Key, 2-14 PRTY Field Job Dependency Network, 2-110 PUTFILE Command KSL, 8-20
Q
QNAME CONTROL-M Monitor, 6-100 Quantative Resources WorkLoad Implementation, 6-24 Quantitative Resource Adding, 2-134 Changing, 2-137, 8-43 CHANGRES KSL Script, 8-10 Conditions/Resources, 2-131 Critical Path Priority, 3-142 Cross Reference, 8-33, 8-43 Definition, 1-25 Deleting, 2-136 IOACND Utility, 6-98 Job Flow Report, 8-33 Release, 6-78
I 60
Index
RESOURCE Parameter, 3-150 Runtime Criteria, 1-6 Show Screen Filter, 2-78 QUANTITY Field Conditions/Resources, 2-132 Quantity Parameter Change Resource Window, 2-138 Quick Schedule Definition CTMQUICK Utility, 2-194 Example, 2-201 Exiting, 2-200 Overwrite Confirmation Window, 2-197 Screen, 2-195 QUICK SCHEDULE Option Online Utilities Menu, 2-164 Quick Submit Command Job Ordering, 6-16 QUICKDEF Utility ISPF Online Utility, 3-3
R
R Line Edit Command, A-3, B-2 R Option Parameter Prompting, 2-181 Status Screen, 2-69, 2-96 R1 Option Online Utilities Menu, 2-203 R2 Option Online Utilities Menu, 2-205 R3 Option Online Utilities Menu, 2-208 R4 Option Online Utilities Menu, 2-165 RACF, 3-133 RANGE Control Statement %%RANGE, 5-20 RB Line Edit Command, A-3 RBA Status Screen, 2-68 RBA Field Conditions/Resources, 2-68, 2-133 RBAL Command Job Dependency Network, 2-108 Status Screen, 2-68, 2-133
RDR=INTRDR Parameter CTMAESIM Utility, 5-27, 6-46 Reactivate Option Status Screen, 2-70 REBUILD Option CMEM Rule Table, 6-108 RECAPTURE CONDITION CODES Field Restart Confirmation Window, 2-99 RECIPIENT TREE Option IOA Primary Option Menu, 2-8 Record Selection Criteria Status Screen, 2-74 REFRESH Command Global View Screen, 2-79 Job Dependency Network, 2-108, 2-111 PA2 Key, 2-14 Status Screen, 2-68 RELATION Parameter Utility CTMTBUPD, 6-82 RELATIONSHIP, 2-35 RELATIONSHIP Field Group Scheduling Table, 3-1 RELATIONSHIP Parameter Description, 3-144 Group Scheduling, 2-36 Group Scheduling Logic, 3-7 Group Scheduling Table, 3-5 Relative Byte Address RBA, 2-68 RELEASED Status Status Screen, 2-71 REMAIN Parameter CTMEXEC CLIST, 6-39 REMAINING PARAMETERS Field Parameter Prompting, 2-190 Update Parameter Values, 2-193 Remark Line Variable Member, 5-10 Remote Node NJE Network, 1-8 REMOVE UNSCHED CONDITIONS Group Entity, 6-21 Parameter, 3-12 REP3ABND KSL Script, 8-9
I 61
Index
REP3ALLJ KSL Script, 8-9 REP3GRUP KSL Script, 8-9 REP3LEFT KSL Script, 8-9 REP3LEFT Report Simulation/Tape Pull, 2-174 REP3RSHS KSL Script, 8-9 REP3STAT KSL Script, 8-9 REP3SYSM KSL Script, 8-9 REP3TAPE KSL Script, 8-9 REP3USER KSL Script, 8-9 REP3WHY KSL Script, 8-9 REP5ABND Utility Abend Report, 8-9 REP5ALL KSL Script, 8-9 REP5EMR KSL Script, 8-9 REP5EXP KSL Script, 8-10 REP5GRDT KSL Script, 8-10 REP5GRUP KSL Script, 8-10 REP5MANL KSL Script, 8-10 REP5MNCN KSL Script, 8-10 REP5MSGD KSL Script, 8-10 REP5NCT2 KSL Script, 8-10 REP5RSTR KSL Script, 8-10 REP5STAT KSL Script, 8-10
REP5USER KSL Script, 8-10 REP7COND KSL Script, 8-10 REP8CAL KSL Script, 8-10 REPBYDSN Parameter Tape Pull List, 7-11 REPBYJOB Parameter Tape Pull List, 7-11 REPBYTIME Parameter Tape Pull List, 7-11 REPBYVOL Parameter Tape Pull List, 7-11 REPCNDLL KSL Utility, 8-11 REPCRCAL KSL Script, 8-10 REPCRCON KSL Script, 8-10 Repeat Commands Edit Environment, A-3, B-2 REPEAT Option Parameter Prompting, 2-181, 2-189 REPEND Parameter CTMRCAL Utility, 6-76 CTMRNSC Report, 8-51 CTMROGR Report, 8-54 CTMRPLN Report, 8-45 REPJBDEF KSL Script, 8-10 REPJEDEF Member SAMPLE Library, 8-9 REPJSTAT KSL Script, 8-10 REPLACE Parameter CTMFETCH CLIST, 6-38 REPLACE Value CTMRCAL Utility, 6-76 REPLACE YES Option CTMFETCH CLIST, 6-40 Report Job Name / Scheduling Table Name Xref, 6-92
I 62
Index
REPORT BY DSN Field Simulation/Tape Pull, 2-175 REPORT BY JOB Field Simulation/Tape Pull, 2-175 REPORT BY TIME Field Simulation/Tape Pull, 2-175 REPORT BY VOLSER Field Simulation/Tape Pull, 2-175 Report Decollating D-CAT Parameter, 3-31 REPORT DEF Option IOA Primary Option Menu, 2-8 Reporting Facility KSL, 8-1 Overview, 1-11 REPORTS Field Simulation/Tape Pull, 2-174 Repository Description, 1-17 REPSTART Parameter CTMRCAL Utility, 6-76 CTMRNSC Report, 8-51 CTMROGR Report, 8-54 CTMRPLN Report, 8-45 REPTBFLW KSL Script, 8-10 REPTYPE Parameter CTMRCAL Utility, 6-76 CTMRPLN Report, 8-45 REQUESTED CHANGE HELD Status Zoom Screen, 2-95 REQUESTED CHANGE Status Status Screen, 2-73 REQUESTED FREE Status FREE Option, 2-69 Status Screen, 2-73 REQUESTED HELD Status HOLD Option, 2-69 Status Screen, 2-72 REQUESTED REACT Status Status Screen, 2-73 REQUESTED RERUN Status Status Screen, 2-73 Rerun Definition, 1-20
Rerun Confirmation Window CONTROL-R, 2-97 Manual Job Rerun, 2-96 Rerun Interval INTERVAL Parameter, 3-95 Rerun Job Example, 5-28 RERUN MAXRERUN Parameter Description, 3-146 RERUN NEEDED Status RERUNMEM Parameter, 3-148 RERUN NEEDED Status MAXRERUN Parameter, 3-146 Rerun Option Status Screen, 2-96 RERUN Option Status Screen, 2-69, 3-146 TASKTYPE Parameter, 3-183 RERUN Parameter Automatic Rerun, 3-146 Example, 3-147, 3-149 JCL Member, 3-148 Rerun Request DO Statement, 3-44 RERUN Status Show Screen Filter, 2-76 RERUN Value SHOUT Parameter, 3-169 Rerun/Restart Window $FIRST/$CLEANUP Values, 2-100 Rerun/Restart Window Status Screen, 2-97 RERUNJOB KSL Script, 8-11 RERUNMEM Parameter Description, 3-148 DO RERUN Statement, 3-148 Example, 3-149 Logic, 3-148 MAXRERUN Parameter, 3-146 RES Field Conditions/Resources, 2-133 Job Dependency Network, 2-110 RES NAME Field Show Screen Filter, 2-78
I 63
Index
RESET Command CMEM Rule Exit Option, 2-127 Description, 2-16 Edit Environment, A-1 Exit Option, 2-52 PF04/PF16, 2-13, 2-16 Quick Schedule Definition, 2-200 Scheduling Facility Exit Option, 2-52 Show Screen Filter, 2-79, 2-150 Year List, 2-163 RESOLVE Control Statement %%RESOLVE, 5-21 Resource Conditions/Resources, 2-68 Resource Acquisition CTMX004 Exit, 6-111 Resource Allocation Critical Path, 1-26 Resource Contention Critical Path Priority, 3-142 Resource Control CONTROL Parameter, 3-25 Resource Name / Job Name Cross Ref CTMXRF Utility, 6-94 RESOURCE Parameter Automatic Tape Adjustment, 3-150 Description, 3-150 Example, 3-152 Logic, 3-151 WM2744 Wish Override, 2-107 RESOURCE TYPE Field Show Screen Filter, 2-78 Resource Utilization Critical Path, 1-26, 3-142 Forecasting, 6-78 IOACND Utility, 6-97 Priority, 3-142 Simulation, 6-78 Tape Devices, 2-107 Resource Window Conditions/Resources, 2-137 Resources Updating, 6-86 Resources/Job Name Report CTMXRF Utility, 6-91
Restart CONTROL-R, 1-20 Definition, 1-20 DO IFRERUN Statement, 3-54 RESTART DECISION Field Zoom Screen, 2-92, 2-94 Restart Job DO IFRERUN Statement, 3-54 OUT Parameter, 3-129 Restart MVS OUT Parameter, 3-123, 3-129 Restart Parameter CONTROL-R Simulation, 2-204 DO Statement, 3-44 RESTART PARM MEMBER NAME Field Restart Confirmation Window, 2-100 Restart Simulation CTRCSIM Utility, 2-203 Restart Step OUT Parameter, 3-124 Restart Step List Window, 2-101 RESTARTED Status Status Screen, 2-72 Restoration Active Jobs File, 1-7 Conditions/Resources, 1-7 RESTORE Option History Environment Screen, 2-113 Utilities Menu, 2-165 RETDAYS Parameter Utility CTMTBUPD, 6-82 RETENTION Parameter, 3-155 # OF DAYS TO KEEP, 3-155, 3-157 # OF GENERATIONS TO KEEP, 3-155, 3-157 History Jobs File, 2-36, 3-1 Retention Period SYSDATA, 3-16 RETGENS Parameter Utility CTMTBUPD, 6-82 Retrieval Criteria Selection Criteria, 2-133 RETRO Parameter Description, 3-159 MAXWAIT Parameter, 3-97
I 64
Index
MINIMUM Parameter, 3-106 PDS Parameter, 3-135 Utility CTMTBUPD, 6-82 RETURN Command KSL, 8-17 REXX Procedure IOACDDR Dataset Event List, 6-25 RL Line Edit Command, A-3, B-2 ROSCOE DO SHOUT Statement, 4-26 Online Monitor, 6-113 PA2 Key, 2-14 ROSCOE/ETSO Environment, 2-1 PF06/PF18, 2-13 RPRSAVE KSL Script, 8-10 RR Line Edit Command, A-3, B-2 RS Line Edit Command, A-3, B-2 RSVNONR Parameter MVS Initialization, 6-114 RSVSTRT Parameter MVS Initialization, 6-114 Rule ... CMEM Rule ..., 4-8 RULE ACTIVITY Option Primary Option Menu, 2-8 Rule Def Option CONTROL-M/WorkLoad, 2-8 Rule Definition Editing, B-1 Maintaining Validity, B-3 RULE DEFINITION Option IOA Primary Option Menu, 2-9 Primary Option Menu, 2-8, 2-9 RULE Field CMEM Entry Panel, 2-118 RULE STATUS Option IOA Menu, 2-9 Primary Option Menu, 2-8 Rule Table Automatic Creation, 2-194 CMEM, 2-115 Rule, CONTROL-B CTB STEP Parameter, 3-29
rulename Parameter DO RULE Statement, 4-21 RUN n Status Status Screen, 2-72 RUN SIMULATION Field Simulation/Tape Pull, 2-173 Run Statistics Statistic ..., 2-105 RUN-%%PLANID Prerequisite Condition, 6-37, 6-40 Runtime Criteria Job Submission, 1-5 Runtime Scheduling CTM/WorkLoad, 6-24 Pipe Algorithm, 1-12 Runtime Scheduling Parameters Scheduling Definition, 2-39 Summary, 3-8 RUNTSEC Parameter Example, 4-51 Security Check, 4-50
S
S Option End User Job Order, 2-202 Job List Screen, 2-34 Status Screen, 2-69, 2-105 Table List Screen, 2-30 Year List Screen, 2-156 S*37 Abend Code SET VAR Parameter, 3-166 SAMPLE Library KSL Scripts, 8-9 SAVE (Y/N) Field Show Screen Filter, 2-75 SAVE Command Zoom Screen, 2-95 SAVE DOCUMENTATION Parameter Save Documentation Window, 2-50 Save Documentation Window Scheduling Definition, 2-49 SAVE Field Exit Option Window, 2-52 Screen Filter, 2-147
I 65
Index
Scale Line View Graph Screen, 2-82, 2-83 SCHDMAX= Control Statement, 6-88, 6-92 SCHED. LIB. Parameter Event Definition, 6-27 SCHEDLIB Parameter CLIST CTMCJOBS, 6-15 Schedule Date Job Scheduling Plan Screen, 2-60 OUT Parameter, 3-121 SCHEDULE Library MAINDAY Table, 6-4 Schedule Tag / Job Name Cross Ref CTMXRF Utility, 6-95 SCHEDULE TAG Field Group Scheduled Job, 3-87 Group Scheduling Table, 3-1 SCHEDULE TAG Parameter Description, 3-161 Group Entity, 2-23, 2-45 Group Scheduling, 2-36, 2-38, 3-5 Schedule Tag/Job Name Report CTMXRF Utility, 6-91 SCHEDULED RUN DATE Field Job Order Utility, 2-168 SCHEDULE-PREV-DAY Value DESC Parameter, 3-42 SCHEDULE-PREV-ONLY Value DESC Parameter, 3-42 Scheduling Basic Parameters, 3-4 Description, 3-1 DO FORCEJOB Statement, 3-52 Example, 3-1 General Parameters, 3-3 Logic, 3-6, 3-7, 3-36 Manual, 2-53 Non-Periodic, 3-36, 3-190 Periodic, 3-37, 3-191 Runtime Parameters, 3-8 TASKTYPE Parameter, 3-182 Scheduling Analysis Why ..., 2-84 Scheduling Analysis Screen Why Screen, 2-84
Scheduling Criteria Group Entity, 2-23 Job Submission, 1-5 Parameter Table, 6-65 Scheduling Definition Calendar Facility, 2-151 Commands, 2-46 Creation, 2-25 Deletion, 2-26, 2-56 Description, 2-22 Documentation, 2-48 Editing, 2-47, A-1 Entry Panel, 2-27 Exiting, 2-50 Graphic Jobflow, 2-57 Group Entity, 2-43 Group-Handled Jobs, 2-24 Job List, 2-32 Job Plan, 2-59 Manual, 2-53 Ordering Jobs, 2-53 Overview, 1-13 Parameters, 2-36 Reports, 8-39, 8-44 Screen, 2-22, 2-35 Search Window, 2-28 Table List, 2-30 Scheduling Definition Facility Scheduling ... Job Scheduling, 3-1 Scheduling Information CTMRAFL Report, 8-44 Job Flow Report, 8-39 Job Scheduling Plan Screen, 2-60 Scheduling Library DO FORCEJOB Statement, 3-52 Job Scheduling, 1-3 Scheduling Library Mode AutoEdit Syntax Testing, 2-168, 5-27 Parameter, 2-170, 6-45 SCHEDULING LIBRARY Parameter AutoEdit Simulation, 2-170, 6-45 Job Dataset List, 2-209 Job Order Utility, 2-167
I 66
Index
Scheduling Logic DAYS Parameter, 3-36 Description, 3-6 Scheduling Table Creation, 6-54 DO FORCEJOB Statement, 3-52 Job Scheduling, 1-3 Parameter Prompting, 6-35 Scheduling Table Name / Job Name Xref Report, 6-92 User Daily Job, 6-8 SCHTBLB Parameter CTMFETCH CLIST, 6-38 Screen Commands KSL, 8-12 Screen Control Online Facility, 2-21 Screen Exit CANCEL Command, 2-16 Screen Help Line Sensitive, 2-17 Online Facility, 2-17 Screen Layout Online Facility, 2-12 Screen Printing CTMSCALL Utility, 8-9 ISPF LIST File, 2-19 PA2 Key, 2-14 Screen Transfer TSO CTMTTRA Command, 2-21 Screens Active Environment, 2-62 AutoEdit Simulation, 2-169 Calendar Definition, 2-157 Calendar Facility, 2-152, 2-162 Calendar Facility Entry Panel, 2-153 Calendar List, 2-154 CMEM Online Entry Panel, 2-117 CMEM Rule Definition, 2-121, 2-125, 4-8, 4-12, 4-26, 4-28, 4-32, 4-39, 4-41, 4-43, 4-51, B-1 CMEM RULE Definition, 4-23 CMEM Rule Facility, 2-115 CMEM Rule List, 2-119 CMEM Table List, 2-118
Conditions/Resources, 2-131, 2-135, 2-136 CONTROL-M Simulation, 2-172 CONTROL-R Simulation, 2-203 Define or Update a Master Plan, 2-185 Define Parameters and Conditions, 2-178, 2-180 Define Parameters in Master Plan, 2-187 Edit Environment, 2-47, 2-125, A-1, B-1 Entry Panel, 2-27, 2-153 Event Definition, 6-27 Event List, 6-26 Event Modification, 6-25, 6-28 Exec/Order a Plan, 2-190 Fetch a Plan, 2-189 Forecasting Facility, 2-172 Global View, 2-79 Graphic Jobflow, 2-57 Group Scheduling, 2-43 IOA Entry Panel, 2-4 IOA Help, 2-17 IOA Log, 2-12, 2-14, 2-144 IOA Primary Option Menu, 2-5, 2-7 IOA TSO Command Processor, 2-20 Issue a Job Request, 2-167 Job Dependency Network, 2-109 Job List, 2-32, 2-53, 2-59, 2-198, 2-202 Job Log, 2-90 Job Order Execution History, 2-102 Job Scheduling Definition, 2-35, 2-48, 2-60, 2-201, 3-1, 3-15, 3-18, 3-24, 3-27, 3-32, 3-34, 3-43, 3-51, 3-53, 3-56, 3-65, 3-69, 3-75, 3-80, 3-82, 3-84, 3-86, 3-90, 3-96, 3-98, 3-102, 3-105, 3-107, 3-115, 3-125, 3-132, 3-134, 3-136, 3-141, 3-147, 3-149, 3-152, 3-167, 3-173, 3-175, 3-181, 3-184, A-1 Jobflow, 2-57 Manual Conditions, 2-139, 2-141, 2-143 Master Plan Definition, 2-186 Master Table Definition, 2-179 Online Utilities, 2-164, 2-165 Parameter Prompting Facility, 2-178 Parameter Prompting Type 1 Menu, 2-177
I 67
Index
Parameter Prompting Type 2 Menu, 2-184 PFKey Window, 2-14 Plan Selection, 2-191 Prerequisite Condition Utility, 2-166 Primary Option Menu, 2-5, 2-7 Quick Schedule Definition, 2-195 Scheduling Analysis, 2-84 Scheduling Definition, 2-22 Scheduling Facility Entry Panel, 2-27 Scheduling Group, 2-43 Set Conditions, 2-183 Show Screen Filter, 2-147, 2-149 Simulation, AutoEdit, 2-168 Simulation, CONTROL-M, 2-172 Simulation, CONTROL-R, 2-203 Statistics, 2-105 Status Screen, 2-62 Sysout Viewing, 2-104 Table List, 2-30, 2-56 Table Selection, 2-182 Tape Pull List, 2-172, 7-12 TSO Command Processor, 2-20 Update Parameters, 2-183, 2-192 Utilities Menu, 2-165 View Graph, 2-81 Why, 2-84 Year List, 2-155 Zoom, 2-91, 2-94 SCREENSIZE Command KSL, 8-13 SCROLL Field Screen Header, 2-15 Scrolling Commands, 2-15 SDOUT Command, 6-112 SEARCH COUNTER Field DISAPPEARED Status, 2-93 Zoom Screen, 2-93 Search Window Scheduling Definition Entry Panel, 2-28 Searching FIND Command, 2-16
SECUDATA Library CTMX002 Exit, 3-101 Security CMEM Rule, 4-48 OWNER Parameter, 3-133 RUNTSEC Parameter, 4-50 Security Cache CMEM, 6-111 SEL Group DAINPRM DD Statement, 6-88 SELECT Command Table Creation, 2-24 Table List Screen, 2-31 Select Option Job Order Execution History, 2-103 SELECT Option Calendar List, 2-154 CMEM Rule List, 2-120 CMEM Table List, 2-119 Event List, 6-26 Job List, 2-34 Table List, 2-25, 2-30 Year List, 2-156 SELECT Statement CTMJOB Utility, 6-71 SELECT TAG ORDER Parameter (CTM), 6-73 SELECT TAG Logic CTMJOB Utillity, 6-73 SELECT TAG tagname CTMJOB Utility, 6-73 Selection Criteria CMEM Actions, 2-122 Conditions/Resources, 2-133 Parameter Prompting, 2-180 Show Screen Filter, 2-75, 2-147 Status Screen, 2-74 Selection Criteria Field Show Screen Filter, 2-75 SELECTION FIELD Parameter Prompting, 2-193 SEND Command CTMAESIM Utility, 6-46 Set Conditions Screen, 2-180
I 68
Index
SET Control Statement %%SET, 5-21 SET Statement JCL SET, 5-14 SET VAR Parameter AutoEdit Variable, 3-164 Description, 3-164 DO SET Statement, 3-64, 3-165 Example, 3-166 SET VAR Statement AutoEdit Statement, 5-28 JCL Setup, 5-4 User-Defined Variables, 5-3 SETLINE Command KSL, 8-18 SETOGLB Command KSL, 8-20 SETOLOC Command %%$PARSE Function, C-9 %%$UNDEF, C-3 KSL, 8-20 User-Defined Variable, C-4 SETOLOC Statement AutoEdit Variables, 8-4 Setting Variable Values AutoEdit, 5-21 SETVAR Command KSL, 8-11 SETVAR CURSOR Command KSL, 8-20 SETVAR DATA Command KSL, 8-21 SETVAR Parameter Job Scheduling Definition, 6-87 Testing AutoEdit Syntax, 6-45 SETVAR SCREEN Command KSL, 8-21 SETVAR Statement CMEM On Spool Job, 4-7 Shared Control CONTROL Parameter, 3-25 Shared Resource WAIT SCHEDULE Status, 2-135 SHIFT Parameter CONFCAL Calendar, 3-6
CONFCAL Parameter, 3-20 Utility CTMTBUPD, 6-83 SHIFT-EXT Parameter Utility CTMTBUPD, 6-83 SHOUT Command KSL, 8-21 Shout Destination Table Loading, 6-112 Shout Facility CONTROL-O, 1-9 DO SHOUT Statement, 3-66 Problem Notification, 1-6 Shout Message AutoEdit Variable, 5-29 SHOUT Message Type Show Screen Filter, 2-148 SHOUT Parameter Description, 3-169 DO SHOUT Statement, 3-68 Job Statistics File, 3-171 Logic, 3-171 System Variables, 5-3 WHEN LATE, 3-170 SHOUT Statement %%JOBNAM/%%JOBNAME Variables, 2-195 Post-Processing Parameters, 2-42 SHOUT WHEN EXECTIME Message Job Dependency Network, 2-110 SHOUT WHEN LATE Message Job Dependency Network, 2-110 SHOUT WHEN LATESUB Message Job Dependency Network, 2-110 SHOW Command Log Screen, 2-90, 2-145, 2-146 PF02/PF14, 2-13 Show Screen Filter, 2-146 Status Screen, 2-67, 2-74 SHOW JOB DOCUMENTATION Entry Panel, 2-28 Show Job Documentation Field Entry Panel, 2-48 SHOW LIMIT ON Field Log Screen, 2-145
I 69
Index
Show Option Window. See also Show Screen Filter Show Screen Filter Activating, 2-74, 2-146 Exiting, 2-78, 2-150 Fields, 2-75, 2-147 Log Screen, 2-146 SHOW Command, 2-146 Status Screen, 2-74 SHOWPARM Operator Command Display Parameter Values, 5-18 SHPF Command PF24, 2-13 Show PFKey, 2-14 SIMEND Parameter Simulation, 7-4 SIMLOG Output File Simulation, 7-2, 7-6 SIMOAJF Output File Simulation, 7-2, 7-6 SIMORES Output File Simulation, 7-2, 7-6 SIMSTART Parameter Simulation, 7-4 SIMUL/TAPE PULL Option Online Utilities Menu, 2-164 Simulation Active Jobs File, 7-1, 7-2, 7-6 Analyzing the Run, 7-8 AutoEdit Statement, 5-27 CMEM Rules, 4-31 CONTROL-R Restart, 2-203 CTMAESIM Utility, 5-27 CTMCSIM CLIST, 2-172 CTMX002, 7-7 Description, 7-1 Input Files, 7-2, 7-6 INVOKE JOBSCAN, 2-172 Manual Conditions, 7-9 Message File, 7-6 MODE Parameter, 4-31 Output Files, 7-2, 7-6 Overview, 1-11 Parameters, 7-4 Resource Release, 6-78
Screens, 2-172, 2-203 Tape Pull List, 7-10 Simulation Facility CTMCSIM Utility, 2-172 Simulation Log CTMROGR Report, 8-53 Simulation Panel CONTROL-R, 2-203 Simulation Parameter Simulation/Tape Pull, 2-174 Simulation/Tape Pull Utility CLIST CTMCSIM, 2-172 SKELETON Field Quick Schedule Definition, 2-195 Skeleton Job Quick Schedule Definition, 2-194 SLACK TIME DUE OUT Parameter, 3-83 Sleeping Interval CMEM, 6-110 CONTROL-M, 6-101 INTERVAL Parameter, 3-95 SLINMAX= Control Statement, 6-88, 6-92 SMF ID Field Statistics Screen, 2-106 SMFID Parameter ON DSNEVENT Statement, 4-35 ON JOBARRIV Statement, 4-40 ON JOBEND Statement, 4-42 ON STEP Statement, 4-44 SMn Command JES2 Started Task, 6-102 SORT Command Job List Screen, 2-33 SORTBY Parameter CTMRCAL Utility, 6-76 CTMRPLN Report, 8-45 Space Allocation SET VAR Parameter, 3-166 Space Report Field Simulation/Tape Pull, 2-175 Special Catalog Tape Pull List, 7-11 Special Variables KSL, 8-4, 8-7, 8-23
I 70
Index
SPLIT Command PF02/PF14, 2-13, 2-19 Split Screen Mode Online Facility, 2-19 SRB Time Field Statistics Screen, 2-106 SRB Time, Average Statistics Screen, 2-106 SRB Time, Group Statistics Screen, 2-106 START Command TASKTYPE Parameter, 3-183 START Field Job Order Execution History, 2-103 START TIME Field Statistics Screen, 2-106 STARTED Status Status Screen, 2-71 Started Task Activation, 6-102 AUTO-ARCHIVE Parameter, 3-17 CONTROL-M Monitor, 6-100 KSL, 8-2 MEMLIB Parameter, 3-100, 3-102 MEMNAME Parameter, 3-104 OVERLIB Parameter, 3-131 Show Screen Filter, 2-77 TASKTYPE Parameter, 3-182 Started Task Under JES2 SMm Command, 6-102 STAT Date Reference DO COND Statement, 3-47, 4-14 IN Parameter, 3-88 OUT Parameter, 3-121 Prerequisite Condition, 1-23 Prerequisite Condition Utility, 2-166 STAT Field Conditions/Resources, 2-133 Global view Screen, 2-80 Manual Conditions, 2-140 STAT Message Type Show Screen Filter, 2-148 STAT Option Status Screen, 2-69, 2-105
State (Mode of Control) CONTROL Parameter, 3-25 STATE Status Show Screen Filter, 2-77 Statement DO SET Statement, 5-4 Global Variable, 5-9 Local Variable, 5-9 Operators, 5-16 Statistical Information Global View Screen, 2-79 Job Status, 2-67 REP5STAT Utility, 8-10 Statistics Screen, 2-105 View Graph Screen, 2-81 Statistics Group Entity, 2-106 Tape Device, 2-107 Tape Devices, 2-107 Statistics Facility Execution Information, 1-10 Statistics File SHOUT Parameter, 3-171 Statistics Screen Fields, 2-106 Job Run Statistics, 2-105 JOBSTAT Command, 2-107 Status Screen, 2-67 status Field Show Screen Filter, 2-76 STATUS Field Job Dependency Network, 2-110 Job Order Execution History, 2-103 Status Screen, 2-65 Status Screen Commands, 2-66 Display Type, 2-63 Fields, 2-64, 2-66 Filtering, 2-74 Format, 2-64 Functions, 1-14, 2-61 Group Statu, 2-73 Job Deleting, 2-69, 2-88 Job Statuses, 2-71 Manual Confirmation, 3-55
I 71
Index
Options, 2-69, 2-105 RBA, 2-68 WAIT CONFIRMATION Status, 3-23 Status Zoom Screen DOC Lines, 3-81 Status, CONTROL-M Job Dependency Network, 2-110 STC Started Task, 3-100 STC Task Type Show Screen Filter, 2-77, 2-148 STEP ADJUSTMENT Field Restart Confirmation Window, 2-99 Step Event CMEM, 4-1 DO FORCEJOB Statement, 4-18 Step List Window Restart Window, 2-101 Step Range Example, 3-117 PGMST Parameter, 3-112 STEP RANGE Parameter Description, 3-174 Example, 3-113, 3-175 pgmstep.procstep, 3-174 STEP Statement. See ON STEP STEPLIB DD Statement CTMBLT Utility, 6-60 STEPRC Parameter ON DSNEVENT Statement, 4-37, 4-38 ON STEP Statement, 4-45 String Extraction %%$SUBSTR Function, C-7 String Manipulation %%$PARSE Function, C-9 String Pattern %%$PARSE Function, C-11 String Search LOCATE Command, 2-15 SUBMIT Command CTMAESIM Utility, 6-46 From ISPF, 6-16 ISPF, 6-16 Quick Submit, 6-16
SUBMIT Function AutoEdit Simulation, 2-170 SUBMITTED Status Show Screen Filter, 2-76 Status Screen, 2-71 SUBSCAN Command CTMAESIM Utility, 6-46 SUBSCAN Function AutoEdit Simulation, 2-171 Substring String, C-7 Subtraction Operation %%MINUS, 5-22 SUCCESR Parameter CTMRFLW Procedure, 8-34 Successor Job Job Dependency, 1-26 Job Dependency Network, 2-108 SUFFIX Field Quick Schedule Definition, 2-197 SUFFIX Parameter CTMEXEC CLIST, 6-39 CTMFETCH CLIST, 6-38 SUM Field View Graph Screen, 2-82 SWAP Command PF09/PF21, 2-19 Symbol IN Parameter, 3-89 Syntax Checking AutoEdit Statement, 5-27, 7-10 CTMSCIM Utility, 2-172 Edit Environment, A-1 JCL Statements, 7-10 SYSDATA Definition, 1-21 SYSDATA Archiving AUTO-ARCHIVE Parameter, 3-16 SYSDATA Deletion Active Jobs File, 3-17 SYSDATA Viewing AUTO-ARCHIVE Parameter, 3-16 SYSDB Parameter AUTO-ARCHIVE Parameter, 3-16 Utility CTMTBUPD, 6-83
I 72
Index
SYSID Field Statistics Screen, 2-106 SYSIN DD Statement %% Parameter, 5-42 SYSOPT = CTMWORK CONTROL-B System Variable, 3-50 SYSOUT Archiving Option F, 5-29 Sysout Dataset SYSDATA, 1-21 Sysout destination SYSOUT Parameter, 3-178 Sysout Destination DO SYSOUT Statement, 3-72 Sysout Operations Archiving Facility, 3-76 Class Change, 3-72, 3-178 Copying, 3-71, 3-73, 3-177, 3-180 Displaying, 2-103 DO SYSOUT Statement, 3-71 Merging, 3-73, 3-179 Moving, 3-72, 3-178 Multiple, 3-72, 3-178 Printing, 3-72, 3-178, 3-180 Priority, 3-180 Releasing, 3-72, 3-178 SYSDATA Definition, 1-21 Viewing Screen, 2-104 SYSOUT operations Priority, 3-73 SYSOUT Operations SYSOUT Parameter, 3-177 Sysout Option Code DO SYSOUT Statement, 3-70 SYSOUT Parameter, 3-176 SYSOUT Option F AutoEdit Variable, 5-29 SYSOUT Parameter Description, 3-176 DO SYSOUT Statement, 3-74, 3-180 Example, 3-181 Logic, 3-178 System Variables, 5-3 SYSPRINT DD Statement CTMAESIM Utility Results, 6-46
System Abend Code ON Statement, 3-113 System Date %%$CALCDATE, C-6 Definition, 1-18 DO FORCEJOB Statement, 3-52 JCL Setup, 5-6 New Day Processing, 6-102 System Output Messages SYSDATA, 1-21 SYSTEM Parameter ON DSNEVENT Statement, 4-35 ON JOBARRIV Statement, 4-40 ON JOBEND Statement, 4-42 ON STEP Statement, 4-44 System Started Task Monitoring via CMEM, 4-36 System Variable %%$ Prefix, 5-9 AutoEdit, 5-2, 5-5, C-1 Date Variable, 5-6 DO SET Statement, 3-64 JCL Setup, 5-5 MEMLIB Parameter, 5-29 Post-Processing, 5-8 Resolution, 5-4 SET VAR Parameter, 3-165 SHOUT Parameter, 5-3 SYSOPT = CTMWORK, 3-50 SYSOUT Parameter, 5-3
T
T Option Status Screen, 2-70 Table Browse Mode, 2-25 Creation, 2-24, 2-31, 2-116 Deletion, 2-26, 2-56 Scheduling Libraries, 2-22 Search Window, 2-28 Table Description Parameter Prompting, 2-179 TABLE Field CMEM Entry Panel, 2-118 Entry Panel, 2-27
I 73
Index
Quick Schedule Definition, 2-195 Scheduling Facility Exit Option, 2-52 Year List Exit Window, 2-163 Table Information Quick Schedule Definition, 2-195 Table Library Parameter Prompting, 2-178 Table List CMEM Table List, 2-30 Statistical Information, 2-30 Table List Screen CMEM Rule Facility, 2-118 Commands, 2-31 Delete Confirmation, 2-56 Description, 2-30 Exiting, 2-52 Graphic Jobflow Option, 8-33 Job Ordering, 6-14 Manual Scheduling, 2-53 New Table, 2-52 Options, 2-25, 2-30 Table Name Field Entry Panel, 2-25 TABLE NAME Field Job Order Utility, 2-167 TABLE NAME Parameter AutoEdit Simulation, 2-170 Event Definition, 6-27 Job Dataset List, 2-209 Table Name Prefix Parameter Prompting, 2-178, 6-33 TABLE Parameter CLIST CTMCJOBS, 6-15 CTMBLT Utility, 6-57 DO FORCEJOB Statement, 3-52, 4-17 DO RULE Statement, 4-21 Testing AutoEdit Syntax, 6-45 TABLE PREFIX Field Table Selection Screen, 2-182 Table Selection Screen Parameter Prompting, 2-182 Tape Adjustment. See Automatic Tape Adjustment Tape Device Statistics, 2-107
Tape Devices Statistics, 2-107 Tape Drive RESOURCE Parameter, 3-152 TAPE Field Job Flow Report, 8-39 Tape Pull List Catalogs, 7-11 CTMCSIM Utility, 2-172 DD Statements, 7-12 JOB/SCAN-DOCU/TEXT, 7-12 Parameters, 7-11 Problem Determination, 7-13 Recommendations, 7-10 Sample Report, 7-14 Simulation, 7-10 Work Flow, 7-10 TAPE PULL LIST Field Simulation/Tape Pull, 2-175 TAPE PULL LIST Parameter Simulation, 7-11 TAPULIN DD Statement Tape Pull List, 7-12 TAPULOUT DD Statement Tape Pull List, 7-12 Target Computer Example, 5-39 TASK TYPE Criteria Screen Filter, 2-148 TASK TYPE Field Show Screen Filter, 2-77 taskid Format MEMLIB Parameter, 3-100 TASKTYPE Parameter Description, 3-182 Example, 3-184 MEMLIB Parameter, 3-101 MEMNAME Parameter, 3-104 Utility CTMTBUPD, 6-83 Tasktype WRN Warning Message, 3-184 TC Option Primary Option Menu, 2-9 Terminal Support Online Facility, 2-2
I 74
Index
TERMINATE Option Status Screen, 2-70 TEST Mode CMEM Rule Simulation, 4-31 Testing AutoEdit Syntax, 5-27 Text Parsing %%$PARSE Function, C-9 TI Option Primary Option Menu, 2-9 Time Runtime Criteria, 1-5 TIME Field Log Screen, 2-145 Time Interval %%$TIMEINT Function, C-8 TIME Parameter CTMEXEC CLIST, 6-39 Description, 3-186 TIME UNTIL Field > Symbol, 6-3 Time/Job Name Report CTMXRF Utility, 6-91 TIMEFROM Parameter Utility CTMTBUPD, 6-83 TIMEUNTIL Parameter Utility CTMTBUPD, 6-83 TO DATE Field Date Range Window, 2-59 TO Destination DO SHOUT Statement, 3-66, 3-67 SHOUT Parameter, 3-170, 3-172 TO Field Zoom Screen, 2-92 TO Parameter DO SHOUT Statement, 4-24 STEP RANGE Parameter, 3-174 TO PGMSTEP Parameter CONTROL-R Simulation, 2-204 Dataset Cleanup, 2-206 TO PROCSTEP Parameter CONTROL-R Simulation, 2-204 Dataset Cleanup, 2-206 TO Step DO IFRERUN Statement, 3-55
Restart Step List Window, 2-101 TO STEP Field Restart Confirmation Window, 2-99 Tocol Parameter FIND Command, 2-16 TOP Command Scrolling, 2-15 TOP SECRET, 3-133 Totals Line Global view Screen, 2-80 View Graph Screen, 2-82 TP Option Primary Option Menu, 2-9 TR Option Primary Option Menu, 2-9 TRACE Command KSL, 8-18 TRACE ON Parameter Debugging, 8-2 Trace Operation CMEM Rule, 6-110 Tracking and Control Description, 1-14 Tracking and Control Facility Online Facility, 2-61 Transfer Command Multi-Screen Control, 2-11 Transfer of Control TSO/Online Facility, 2-13, 2-21 Transfer to TSO/Utilities PF06/PF18, 2-13 TSO AutoRefresh Mode, 2-18 Commands, 2-20 Control, 2-13, 2-21 Environment, 2-1 Option 6, 2-5 PA2 Key, 2-14 Screen, 2-20 TSO Application Online Facility, 2-21 TSO Command Processor Screen, 2-20 TSO Cross Memory Option PF06/PF18, 2-13
I 75
Index
TSO CTMTTRA Command Transfer to IOA, 2-21 TSO Environment Online Monitor, 6-113 OWNER Parameter, 3-133 TSO Job CMEM On Spool Job, 4-3 DO STOPJOB Statement, 4-27 TSO Option Primary Option Menu, 2-6 TSO SEND Command DO SHOUT Statement, 3-67, 4-25 TSO Transfer Commnand PF06/PF18, 2-13 TSO User id Quick Schedule Definition, 2-196 TSO/ISPF Environment, 2-1, 2-34, 2-70 TV Option VAULT DEFINITION, 2-9 TYP Field Job Flow Report, 8-39 Status Screen, 2-65 TYPE 1 Parameter Prompting, 2-176 TYPE 2 Parameter Prompting, 2-176 TYPE Command KSL, 8-13 TYPE Field Conditions/Resources, 2-132 Entry Panel, 2-27 Manual Conditions, 2-140 Parameter Prompting, 2-188 Rule List Screen, 2-119 Type of Task TASKTYPE Parameter, 3-182 TYPE Parameter CTB STEP Parameter, 3-29 TYPRUN=HOLD CMEM On Spool Job, 4-4, 4-6 TYPRUN=SCAN Parameter AutoEdit Simulation, 2-171 Tape Pull List, 7-10, 7-11
TYPRUN=SCAN Statement CTMAESIM Utility, 6-46
U
U1 Option Online Utilities Menu, 2-209 U-ECS Reserved Keyword Enterprise Controlstation, 3-67 UNDELETE Option Status Screen, 2-70 Underscore _ Character, 5-9 UNEXPECTED CC Status Show Screen Filter, 2-76 UNITDEF Member CONTROL-M PARM Library, 2-107 Unscheduled Condition Manual Conditions, 6-19 UNTIL Time TIME Parameter, 3-186 Unused Tracks MINIMUM Parameter, 3-106 PDS Parameter, 3-135 UP Command PF07/PF19, 2-13, 2-15 UPDATE Option Parameter Prompting, 2-181, 2-189 Update Parameters Fields, 2-183, 2-192 Screen, 2-183, 2-192 Type 1 Option 1, 2-182 Utility CTMTBUPD, 6-81 Updating Job Scheduling Tables, 6-80 UPP User Prompting Plan, 6-36 UPPTBLB Parameter CTMFETCH CLIST, 6-38 UPPTBLB Parameter CTMEXEC CLIST, 6-39 URGENCY Field Screen Filter, 2-148 URGENCY Parameter DO SHOUT Statement, 3-67, 3-68, 4-25
I 76
Index
URGN Parameter SHOUT Parameter, 3-172 URGN Parameter SHOUT Parameter, 3-171 USE Field Conditions/Resources, 2-132 User Abend Code ON Statement, 3-113 User Daily Job Checkpointing, 6-10 Customization, 6-10 DAILYPRD, 6-7 DAILYSYS, 6-4, 6-7 Date Control Record, 6-7 Description, 6-6 Implementation, 6-2 New Day Procedure, 6-3 Scheduling Table, 6-8 USER DATA Field Statistics Screen, 2-106 USER DATA, Group Statistics Screen, 2-106 User Defined Variable %% Prefix, 5-9 User ID Online Facility, 2-4 USER ID Screen Filter, 2-149 USER ID Parameter. See also OWNER Parameter USER INTERFACE Option Online Utilities Menu, 2-164 USER Message Type Show Screen Filter, 2-148 User Plan User Prompting Plan, 2-190 User Profile Customizing, 2-1 Status Screen Filter, 2-74 User Prompting Plan Parameter Prompting, 2-189, 6-36 USER REPORTS Option IOA Primary Option Menu, 2-8 USER=Library MEMLIB Parameter, 3-100
OVERLIB Parameter, 3-132 User-Defined Variable AutoEdit, 5-2, C-4 DO SET Statement, 3-63, 3-64, 5-3 JCL Setup, 5-9 SET VAR Parameter, 3-165 Source Priority, 5-4 USERID Field Log Screen, 2-145 USERID Parameter CTMBLT Utility, 6-58 USERID Value DO SHOUT Destination, 3-66 SHOUT Parameter, 3-170 Utilities CLIST IOAUTIL, 2-164 Conditions/Resources File, 2-166 CONTROL-M, 6-43 CTM2RUL, 4-1 CTMAESIM, 2-168, 5-27 CTMBLDAE, 6-49 CTMBLT, 6-54 CTMJBINT, 2-202 CTMJOBRQ, 2-167, 6-14 CTMJSA, 2-105 CTMQUICK, 2-194 CTMRCAL, 6-76 CTMRELRS, 6-78 CTMSIM, 6-43, 7-1 CTMTAPUL, 7-1 CTMTBUPD, 6-80, 6-88 CTMXRF, 6-93 CTRCSIM, 2-203 Fast Transfer, 2-165 IOABLCAL, 6-76 IOACND, 6-97 IOALDNRS, 2-139, 6-4, 6-10, 6-14, 6-19, 6-31, 6-34 IOAOPR, 6-113 IOAVCND, 6-99 Job Order, 2-167 Prerequisite Condition, 2-166 Under ISPF, 2-164 UTILITIES Option Primary Option Menu, 2-5
I 77
Index
Utilities Transfer Command PF06/PF18, 2-13 Utility CTMJTXRF, 6-92 Job Name / Table Name Xref Report (CTMJTXRF), 6-92
V
V Option Status Screen, 2-69, 2-102 VALUE Field Parameter Prompting, 2-180, 2-183, 2-192 VARIABLE DATABASE Option Primary Option Menu, 2-9 Variable Member Format, 5-10 Retries, 5-18, 5-19 Variable Resolution Concatenation, 5-12 Example, C-5 Logic, 5-11 Rules, C-4 Variable Substitution Variable Resolution, C-4 Variables AutoEdit, Date, Global, KSL, Local, System, User-Defined ..., 5-5 VAULT DEFINITION Option IOA Primary Option Menu, 2-9 Version Information Primary Option Menu, 2-10 VG Command Status Screen, 2-67, 2-81 VIEW Command Status Screen, 2-67, 2-79 VIEW GRAPH Command Status Screen, 2-67, 2-81 View Graph Screen Color Terminals, 2-81 Fields, 2-82, 2-83 Format, 2-81 Group Statistics, 2-81 Non-color Terminals, 2-83
View Option Status Screen, 2-102 VIEW Option Status Screen, 2-69 VIEWALL Command Job Order Execution History, 2-103 VOL=SER=%%VOLSER Example, 5-37, 5-38 VTAM Environment, 2-1 Online Monitor, 6-113 PF06/PF18, 2-13
W
W Option Year List Screen, 2-156 WAIT CONFIRM Status Show Screen Filter, 2-76 WAIT CONFIRMATION (FOR SCHEDULE) Status Status Screen, 2-71 WAIT CONFIRMATION (WITH RESTART) Status Status Screen, 2-71 WAIT CONFIRMATION Status CONFIRM Parameter, 3-23 WAIT EXEC Status Show Screen Filter, 2-76 WAIT EXECUTION Status Status Screen, 2-71 WAIT RELEASE Status Status Screen, 2-71 WAIT SCHEDULE (WITH RESTART) Status Job Rerun, 2-98 WAIT SCHEDULE Field Global View Screen, 2-80 View Graph Screen, 2-82 WAIT SCHEDULE ON SPOOL Status CMEM Forced Job, 4-5 Status Screen, 2-71 WAIT SCHEDULE Status Cause or Reason, 2-85 CONTROL Resources, 2-135 Group Entity, 3-122
I 78
Index
Job Deletion, 2-89, 2-113 Job Graph, 2-82, 2-84 Job Rerun, 2-97, 2-98 REP3WHY Utility, 8-9 Screen Status, 2-71 Show Screen Filter, 2-76 TERMINATE Option, 2-113 WAIT SUB Status Show Screen Filter, 2-76 WAIT SUBMISSION Status Status Screen, 2-71 Warning Message MEMNAME Parameter, 3-104 TASKTYPE Parameter, 3-182 WCAL Calendar, 6-91 WCAL Field WDAYS Parameter, 3-6 WCAL Parameter Calendar Name, 3-189 Calendar Type, 3-192 Non-Periodic Calendar, 3-190 Periodic Calendar, 3-191 Utility CTMTBUPD, 6-83 WDATE Parameter AutoEdit Simulation, 2-170, 8-57 CONTROL-R Simulation, 2-204 CTMAESIM Utility, 6-45 Dataset Cleanup, 2-206 Job Dataset List, 2-209 WDAYS Parameter Description, 3-189 Example, 3-193 Format, 3-190 Logic, 3-190, 3-192 MINIMUM Parameter, 3-106 Negative Value, 3-192 PDS Parameter, 3-135 Scheduling Logic, 3-6 Utility CTMTBUPD, 6-83 WCAL Field, 3-6 WHEN Parameter ON DSNEVENT Statement, 4-38 SHOUT Parameter, 3-169, 3-171
Why Scheduling Analysis, 2-84 Why Option Status Screen, 2-84 WHY Option Status Screen, 2-69 Why Screen Adding Conditions, 2-86 Example, 2-84 WAIT SCHEDULE Status, 2-84 WHY Screen Reasons, 2-85 Window Exit RESET Command, 2-16 Windows ADD Conditions, 2-135 Calendar Delete, 2-161 CMEM Rule Exit Option, 2-127 CMEM Rule Table Order, 2-129 CMEM Table Deletion, 2-128 Conditions/Resources Delete, 2-136 CONTROL-R Rerun Confirmation, 2-97 Delete Calendar, 2-161 Delete Conditions/Resources, 2-136 Manual Condition Add, 2-143 Manual Condition Delete, 2-141 Overwrite Confirmation, 2-197 Quick Schedule Definition Exit, 2-200 Rerun Confirmation, 2-96 Resource Quantity, 2-137 Save Documentation, 2-50 Scheduling Facility Exit Option, 2-51 Show Screen Filter, 2-75, 2-147, 2-149 Status Screen Delete, 2-89 Why Screen Confirmation, 2-87 Year List Exit, 2-163 Zoom Screen Confirmation, 2-95 Wish WM1754 Search Counter, 2-93 WITH RESTART Field Restart Confirmation Window, 2-98 WITH RESTART Status Status Screen, 2-72
I 79
Index
WM2354 Wish, 5-18, 5-19 WM2744 Wish, 2-107 Automatic Tape Adjustment, 3-150 WM2890 Wish MAXWAIT Parameter, 3-98 Working Date Definition, 1-18 System Variable, 5-6 Working Days WDAYS Parameter, 3-189 WORKLOAD Option Status Screen, 2-70 WRN Task Type Show Screen Filter, 2-77, 2-148 WTO Descriptor Codes, D-2 WTO Message Route Codes, D-1
Y
Year Definition Screen Calendar Definition Screen, 2-1 YEAR Field Calendar Definition, 2-158 Calendar Facility Entry Panel, 2-153 Job Scheduling Plan Screen, 2-60 Year List Screen Description, 2-155 Exiting, 2-163 Options, 2-156
Z
Z Option Status Screen, 2-69, 2-91 ZOOM Option Status Screen, 2-69 Zoom Screen Example, 2-91 Exiting, 2-95 Fields, 2-92 Group Entity, 2-94 Job Order Information, 2-91 MAXRERUN Parameter, 3-146 SHOUT Parameter, 3-172
X
X Command Online Facility Exit, 2-11 XRF Parameter CTMXRF Utility, 6-91
I 80

Control M

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Control M

Uploaded by

Copyright:

Available Formats

CONTROL-M

About This Manual

Job Production Parameters

CONTROL-M Event Manager (CMEM)

JCL and AutoEdit Facility

Implementation and Maintenance

CONTROL-M Rel. 5.1.4 User Manual

Simulation and Forecasting Facility

KSL and the Reporting Facility

Appendix A Editing Job Scheduling Definitions in the Edit Environment

Appendix B Editing CMEM Rule Definitions in the Edit Environment

Appendix C AutoEdit Facility in KSL

Appendix D MVS WTO Route/Descriptor Codes

Index Information New to This Release

Information Relating to CONTROLR Users

IOA Security Guide

IOA Administrator Guide

IOA Messages and Codes

We Want to Hear From You...

CONTROL-M Rel. 5.1.4 User Manual

This page is intentionally left blank

CONTROL-M Rel. 5.1.4 User Manual

CONTROL-M Rel. 5.1.4 User Manual

Section 2: Online Facility

CONTROL-M Rel. 5.1.4 User Manual

CONTROL-M Rel. 5.1.4 User Manual

CONTROL-M Rel. 5.1.4 User Manual

CONTROL-M Rel. 5.1.4 User Manual

CONTROL-M Rel. 5.1.4 User Manual

Section 3: Job Production Parameters

CONTROL-M Rel. 5.1.4 User Manual

DO IFRERUN ...........................................................................................................................3-54 FROM...................................................................................................................................3-54

CONTROL-M Rel. 5.1.4 User Manual

CONTROL-M Rel. 5.1.4 User Manual

Section 4: CONTROL-M Event Manager (CMEM)

CONTROL-M Rel. 5.1.4 User Manual

Section 5: JCL and AutoEdit Facility

CONTROL-M Rel. 5.1.4 User Manual

Section 6: Implementation and Maintenance

CONTROL-M Rel. 5.1.4 User Manual

CONTROL-M Rel. 5.1.4 User Manual

Section 7: Simulation and Forecasting Facility

CONTROL-M Rel. 5.1.4 User Manual

Section 8: KSL and the Reporting Facility

Section 1: Introduction to CONTROL-M

CONTROL-M Rel. 5.1.4 User Manual

CONTROL-M Rel. 5.1.4 User Manual

Introduction: IOA Products and Your Data Center

IOA Products and Your Data Center

CONTROL-D/PC CONTROL-D/ Page On Demand

CONTROL-O/ COSMOS CONTROL-O/ Server

CONTROL-M Rel. 5.1.4 User Manual

Introduction: IOA Products and Your Data Center

CONTROL-M Rel. 5.1.4 User Manual

Introduction: CONTROL-M: A Functional Approach Main Components

CONTROL-M: A Functional Approach

Job scheduling definitions. Active Jobs file. CONTROL-M monitor.

Job Scheduling Definitions

CONTROL-M Rel. 5.1.4 User Manual

Introduction: CONTROL-M: A Functional Approach Expanded CONTROL-M Functionality

Active Jobs File

Expanded CONTROL-M Functionality

Automating Job Scheduling: New Day Processing