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 [email protected]. Please include the name and version of the publication in your email.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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 Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

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

CONTROL-M Rel. 5.1.4 User Manual

15

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

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

CONTROL-M Rel. 5.1.4 User Manual

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

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.

CONTROL-M Rel. 5.1.4 User Manual

17

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

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

CONTROL-M Rel. 5.1.4 User Manual

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

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.

CONTROL-M Rel. 5.1.4 User Manual

19

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

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

CONTROL-M Rel. 5.1.4 User Manual

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

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.

CONTROL-M Rel. 5.1.4 User 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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

1 13

Introduction: CONTROL-M: A Functional Approach Online User Interface to CONTROL-M

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

CONTROL-M Rel. 5.1.4 User Manual

Introduction: CONTROL-M: A Functional Approach Online User Interface to CONTROL-M

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.

CONTROL-M Rel. 5.1.4 User Manual

1 15

Introduction: CONTROL-M: A Functional Approach Online User Interface to CONTROL-M

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Introduction: CONTROL-M Concepts Prerequisite Condition Concept

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).

CONTROL-M Rel. 5.1.4 User Manual

1 23

Introduction: CONTROL-M Concepts Prerequisite Condition Concept

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

1 27

Introduction: CONTROL-M Concepts Automatic Job Flow Adjustment

This page is intentionally left blank

1 28

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

21

Online Facility: IOA Features General

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: IOA Features General

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

25

Online Facility: IOA Features IOA Primary Option Menu

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: IOA Features IOA Primary Option Menu

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

PLEASE SELECT OPTION

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.

CONTROL-M Rel. 5.1.4 User Manual

27

Online Facility: IOA Features IOA Primary Option Menu

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: IOA Features IOA Primary Option Menu

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.

CONTROL-M Rel. 5.1.4 User Manual

29

Online Facility: IOA Features IOA Primary Option Menu

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

PLEASE SELECT OPTION

10.19.22

2 10

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

2 13

Online Facility: IOA Features Commands and PFKeys

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: IOA Features Commands and PFKeys

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.

CONTROL-M Rel. 5.1.4 User Manual

2 15

Online Facility: IOA Features Commands and PFKeys

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility General

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

CONTROL-M Rel. 5.1.4 User Manual

2 23

Online Facility: Scheduling Definition Facility General

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility General

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.

CONTROL-M Rel. 5.1.4 User Manual

2 25

Online Facility: Scheduling Definition Facility General

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

2 27

Online Facility: Scheduling Definition Facility Entry Panel

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Entry Panel

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).

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Job List Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

2 33

Online Facility: Scheduling Definition Facility Job List Screen

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

2 35

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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.

CONTROL-M Rel. 5.1.4 User Manual

2 37

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

2 39

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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.

CONTROL-M Rel. 5.1.4 User Manual

2 41

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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.

CONTROL-M Rel. 5.1.4 User Manual

2 43

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

2 45

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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.

CONTROL-M Rel. 5.1.4 User Manual

2 47

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Job Scheduling Definition Screen Defining Schedules

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Scheduling Definition Facility Exiting the Scheduling Definition Facility

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

CONTROL-M Rel. 5.1.4 User Manual

2 51

Online Facility: Scheduling Definition Facility Exiting the Scheduling Definition Facility

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Status Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

2 63

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

2 65

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Status Screen

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.)

CONTROL-M Rel. 5.1.4 User Manual

2 67

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Status Screen

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).

CONTROL-M Rel. 5.1.4 User Manual

2 69

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Status Screen

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.)

CONTROL-M Rel. 5.1.4 User Manual

2 71

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

2 73

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Status Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

2 75

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

2 77

Online Facility: Tracking and Control Facility Status Screen

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

2 81

Online Facility: Tracking and Control Facility View Graph Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility View Graph Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Why Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

2 85

Online Facility: Tracking and Control Facility Why Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Why Screen

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)

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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 <<<<<<<<<<<<< ========

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 16.28.18

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

2 91

Online Facility: Tracking and Control Facility Zoom Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Zoom Screen

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).

CONTROL-M Rel. 5.1.4 User Manual

2 93

Online Facility: Tracking and Control Facility Zoom Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Zoom Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Rerun/Restart Window (Under CONTROL-R)

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.

CONTROL-M Rel. 5.1.4 User Manual

2 99

Online Facility: Tracking and Control Facility Rerun/Restart Window (Under CONTROL-R)

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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>.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

2 105

Online Facility: Tracking and Control Facility Statistics Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Statistics Screen

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>.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Job Dependency Network Screen

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

CONTROL-M Rel. 5.1.4 User Manual

2 109

Online Facility: Tracking and Control Facility Job Dependency Network Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Tracking and Control Facility Job Dependency Network Screen

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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 <<<<<<<<<<<<<<<<<< =====

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

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

2 117

Online Facility: CMEM Rule Definition Facility Table List Screen

Fields of the Entry Panel

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

2 121

Online Facility: CMEM Rule Definition Facility Rule Definition Screen Defining Rules

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: CMEM Rule Definition Facility Rule Definition Screen Defining Rules

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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 <<<<<<<<<<<<<<< =====

FILL IN RULE DEFINITION. CMDS: EDIT , SHPF

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 <<<<<<<<<<<<<<< =====

FILL IN RULE DEFINITION. CMDS: EDIT , SHPF

21.00.36

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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.

Exiting the Entry Panel

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Condition/Resource Handling IOA Conditions/Resources Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

2 133

Online Facility: Condition/Resource Handling IOA Conditions/Resources Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Condition/Resource Handling IOA Conditions/Resources Screen

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).

CONTROL-M Rel. 5.1.4 User Manual

2 135

Online Facility: Condition/Resource Handling IOA Conditions/Resources Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Condition/Resource Handling IOA Conditions/Resources Screen

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

CONTROL-M Rel. 5.1.4 User Manual

2 137

Online Facility: Condition/Resource Handling IOA Conditions/Resources Screen

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

2 139

Online Facility: Condition/Resource Handling IOA Manual Conditions Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Condition/Resource Handling IOA Manual Conditions Screen

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).

CONTROL-M Rel. 5.1.4 User Manual

2 141

Online Facility: Condition/Resource Handling IOA Manual Conditions Screen

--------------------------- 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 <<<<<<<<<<<<<<<< ========

OPTIONS: A ADD TO COND/RES LIST (SCREEN 4) E ERASE

COMMANDS: NEW 18.33.47

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Condition/Resource Handling IOA Manual Conditions Screen

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 <<<<<<<<<<<<<<<< ========

OPTIONS: A ADD TO COND/RES LIST (SCREEN 4) E ERASE

COMMANDS: NEW 18.33.47

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.)

CONTROL-M Rel. 5.1.4 User Manual

2 145

Online Facility: IOA Log Facility IOA Log Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: IOA Log Facility IOA Log Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

2 147

Online Facility: IOA Log Facility IOA Log Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: IOA Log Facility IOA Log Screen

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,

CONTROL-M Rel. 5.1.4 User Manual

2 149

Online Facility: IOA Log Facility IOA Log Screen

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

Fields of the Entry Panel

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

2 157

Online Facility: IOA Calendar Facility Calendar Definition Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: IOA Calendar Facility Calendar Definition Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

2 159

Online Facility: IOA Calendar Facility Calendar Definition Screen

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: IOA Calendar Facility Calendar Definition Screen

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

Exiting the Entry Panel

Press END (PF03/PF15) to exit the entry panel.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M2: Perform Online AutoEdit Simulation

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>.

CONTROL-M Rel. 5.1.4 User Manual

2 169

Online Facility: Utilities Under ISPF M2: Perform Online AutoEdit Simulation

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M2: Perform Online AutoEdit Simulation

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

Enter YES to continue

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.

CONTROL-M Rel. 5.1.4 User Manual

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)

Enter YES to continue

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M3: Prepare Simulation/Tape Pull List Job

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)

CONTROL-M Rel. 5.1.4 User Manual

2 173

Online Facility: Utilities Under ISPF M3: Prepare Simulation/Tape Pull List Job

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M3: Prepare Simulation/Tape Pull List Job

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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.

CONTROL-M Rel. 5.1.4 User Manual

2 177

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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>.

CONTROL-M Rel. 5.1.4 User Manual

2 179

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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.

CONTROL-M Rel. 5.1.4 User Manual

2 181

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

Option 2: Update Parameters and Set Conditions

After selecting option 2 of the Parameter Prompting facility (Type 1) Primary menu, the following screen is displayed:
---- 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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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.

CONTROL-M Rel. 5.1.4 User Manual

2 183

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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.

CONTROL-M Rel. 5.1.4 User Manual

2 185

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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

CONTROL-M Rel. 5.1.4 User Manual

2 187

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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)

After selecting option 2 of the Parameter Prompting facility (Type 2) Primary menu, the following screen is displayed:
---- 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

CONTROL-M Rel. 5.1.4 User Manual

2 189

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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)

After selecting option 3 of the Parameter Prompting facility (Type 2) Primary menu, the following 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

===> 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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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.

CONTROL-M Rel. 5.1.4 User Manual

2 191

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M4: Parameter Prompting Facilities

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M5: Quick Schedule Definition Facility

%%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.

CONTROL-M Rel. 5.1.4 User Manual

2 195

Online Facility: Utilities Under ISPF M5: Quick Schedule Definition Facility

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M5: Quick Schedule Definition Facility

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.

CONTROL-M Rel. 5.1.4 User Manual

2 197

Online Facility: Utilities Under ISPF M5: Quick Schedule Definition Facility

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M5: Quick Schedule Definition Facility

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.

CONTROL-M Rel. 5.1.4 User Manual

2 199

Online Facility: Utilities Under ISPF M5: Quick Schedule Definition Facility

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

CONTROL-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF M5: Quick Schedule Definition Facility

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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).

CONTROL-M Rel. 5.1.4 User Manual

2 205

Online Facility: Utilities Under ISPF R2: CONTROL-R Dataset Cleanup

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-M Rel. 5.1.4 User Manual

Online Facility: Utilities Under ISPF R2: CONTROL-R Dataset Cleanup

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

2 209

Online Facility: Utilities Under ISPF U1: Invoke DOCU/TEXT25

This page is intentionally left blank

2 210

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

31

Job Production Parameters: General

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

CONTROL-M Rel. 5.1.4 User Manual

Job Production Parameters: General

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

35

Job Production Parameters: General Basic Scheduling Parameters Summary

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

CONTROL-M Rel. 5.1.4 User Manual

Job Production Parameters: General Basic Scheduling Parameters Summary

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.)

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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.

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

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

CONTROL-M Rel. 5.1.4 User Manual

3 11

ADJUST CONDITIONS
General Job Parameter

ADJUST CONDITIONS

General Job Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

ADJUST CONDITIONS
General Job Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

3 13

APPL
General Job Parameter

APPL

General Job Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

APPL
General Job Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

3 15

AUTO-ARCHIVE
PostProcessing Parameter

AUTO-ARCHIVE
Controls SYSDATA archiving.

PostProcessing Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

AUTO-ARCHIVE
PostProcessing Parameter

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.

CONTROL-M Rel. 5.1.4 User Manual

3 17

AUTO-ARCHIVE
PostProcessing Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

CONFCAL
Basic Scheduling Parameter

CONFCAL
Name of a calendar used to confirm the scheduling of the job. See also DAYS, WDAYS and DATES.

Basic Scheduling Parameter

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.

CONTROL-M Rel. 5.1.4 User Manual

3 19

CONFCAL
Basic Scheduling Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

CONFCAL
Basic Scheduling Parameter

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.

CONTROL-M Rel. 5.1.4 User Manual

3 21

CONFCAL
Basic Scheduling Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

CONFIRM
Runtime Scheduling Parameter

CONFIRM
Ensures manual confirmation before the job is submitted.

Runtime Scheduling Parameter

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.

CONTROL-M Rel. 5.1.4 User Manual

3 23

CONFIRM
Runtime Scheduling Parameter

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-M Rel. 5.1.4 User Manual

CONTROL
Runtime Scheduling Parameter

CONTROL

Runtime Scheduling Parameter

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:

CONTROL-M Rel. 5.1.4 User Manual

3 25

CONTROL
Runtime Scheduling Parameter

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-M Rel. 5.1.4 User Manual

CONTROL
Runtime Scheduling Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

3 27

CONTROL
Runtime Scheduling Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

CTB STEP
General Job Parameter

CTB STEP

General Job Parameter

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.

CONTROL-M Rel. 5.1.4 User Manual

3 29

CTB STEP
General Job Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

D-CAT
Basic Scheduling Parameter

D-CAT

Basic Scheduling Parameter

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).

CONTROL-M Rel. 5.1.4 User Manual

3 31

D-CAT
Basic Scheduling Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DATES
Basic Scheduling Parameter

DATES

Basic Scheduling Parameter

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.

CONTROL-M Rel. 5.1.4 User Manual

3 33

DATES
Basic Scheduling Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DAYS
Basic Scheduling Parameter

DAYS
Days of the month on which the job should be scheduled. See also WDAYS and CONFCAL.

Basic Scheduling Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

3 35

DAYS
Basic Scheduling Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DAYS
Basic Scheduling Parameter

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,...

CONTROL-M Rel. 5.1.4 User Manual

3 37

DAYS
Basic Scheduling Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DAYS
Basic Scheduling Parameter

Example 1
Schedule the job on the 17th day and the last day of the month.
DAYS 17,L1

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 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

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 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

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 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

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 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 *

CONTROL-M Rel. 5.1.4 User Manual

3 39

DAYS
Basic Scheduling Parameter

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

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 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

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 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

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 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 8
Schedule the job on the last Monday of the month.
DAYS AND/OR WDAYS L1,L2,L3,L4,L5,L6,L7 AND 1

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 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 40

CONTROL-M Rel. 5.1.4 User Manual

DAYS
Basic Scheduling Parameter

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 >

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 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

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 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 *

CONTROL-M Rel. 5.1.4 User Manual

3 41

DESC
General Job Parameter

DESC
Description of the job to be displayed in the Job List screen.

General Job Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DESC
General Job Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

3 43

DO statement
PostProcessing Parameter

DO statement

PostProcessing Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DO statement
PostProcessing Parameter

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).

CONTROL-M Rel. 5.1.4 User Manual

3 45

DO COND
PostProcessing Parameter

DO COND

PostProcessing Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DO COND
PostProcessing Parameter

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.

CONTROL-M Rel. 5.1.4 User Manual

3 47

DO COND
PostProcessing Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DO COND
PostProcessing Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

3 49

DO CTBRULE
PostProcessing Parameter

DO CTBRULE

PostProcessing Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DO CTBRULE
PostProcessing Parameter

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 <<<<<<<<<<<<<<<< =====

USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION

11.17.00

CONTROL-M Rel. 5.1.4 User Manual

3 51

DO FORCEJOB
PostProcessing Parameter

DO FORCEJOB
Force one or more jobs under CONTROL-M.

PostProcessing Parameter

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

CONTROL-M Rel. 5.1.4 User Manual

DO FORCEJOB
PostProcessing Parameter

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