This chapter includes the following topics:
-
Overview
-
Preparations
-
Main Components of Control-M
-
Online Facility Primary Options
-
Introduction to the Scheduling Definition Facility
-
Introduction to the Active Environment Screen
-
Toggling Between Display of Commands and Options
-
Filtering the Active Environment Display
-
Confirming a Job Order
-
Checking the Log for the Job from the Active Environment Screen
-
Checking the Sysout for the Job
-
Holding and Deleting Active Environment Screen Job Orders
-
-
Return to the Scheduling Definition Facility
-
Saving Job Scheduling Definitions
-
Selecting a Table from the Table List Screen
-
Formats of the Job List Screen
-
-
Exiting the Online Facility
-
Review
-
Recommended Reading
-
Overview
Control-M is an automated production control and scheduling system that manages and automates the setup, scheduling and execution of jobs in the z/OS data center.
The Control-M for z/OS Getting Started Guide provides you with an introduction to the functionality of Control-M, and teaches you how to use Control-M, one step at a time, with each step building upon what was learned in the previous step. Of necessity, the explanations of topics in this book are not comprehensive. For comprehensive explanations of topics, you should refer to the relevant guide, such as the Control-M for z/OS User Guide, INCONTROL for z/OS Administrator Guide, and so on.
The first chapter of the Control-M for z/OS User Guide provides an introduction to Control-M. You might find it useful to read that chapter before using this guide; however, you can still easily use this guide without having read that chapter in the User Guide.
This guide begins with a discussion of the main components of Control-M:
-
Scheduling Definition facility
-
Tracking and Control facility: Active Environment screen
Before you are introduced to the main components of Control-M, you should prepare the jobs that you will need in order to perform the exercises in this chapter.
Preparations
Create the JCL for two trivial jobs, identified throughout this guide as IDJOB1 and IDJOB2. Define the jobs to execute IEFBR14. For purposes of this guide, identify the JCL library as CTM.TEST.JCL.
Main Components of Control-M
Control-M automates the setup, scheduling, and execution of jobs in the z/OS environment. This is essentially a two-step process:
-
You must tell Control-M how you want job processing handled.
-
Job scheduling and processing instructions are provided through the Scheduling Definition facility, a main component of Control-M.
-
You specify these instructions in job scheduling definitions that you define in the Job Scheduling Definition screen. Each job scheduling definition must be defined only once; it can then be used as often as needed. Job scheduling definitions are stored in tables, or members, in a scheduling library.
-
-
Using the instructions you provided in the job scheduling definitions, Control-M automatically tracks and controls the setup, scheduling, and execution of the job. Control-M provides you with constant feedback on job processing, and enables you to manually intervene in the processing of jobs, through a series of screens.
-
"Tracking and Control facility" is a general term that applies to the screens that provide feedback on job processing, and enable manual intervention. The main screen in this facility is the Active Environment screen, which provides status and other information for currently scheduled and recently completed jobs, and accepts your commands and instructions. The Active Environment screen also acts as a gateway to other screens in the Tracking and Control facility.
-
You will take a first look at these components by doing the following in your first set of exercises:
-
You will use the Scheduling Definition facility to create job scheduling definitions for the two trivial jobs you just defined.
-
You will make submission of the first job dependent on a manual intervention performed in the Active Environment screen.
-
You will make submission of the second job dependent on successful completion of the first job.
-
-
You will order the jobs.
-
You will observe the results in the Active Environments screen. Along the way, you will become familiar with several commands, options and windows in the Active Environment screen. You will also become familiar with the Control-M Log screen.
To do this, enter the IOA Online facility, take a look at the main components of Control-M, and perform the exercises.
Online Facility Primary Options
The primary options of the Online facility are displayed when you enter the IOA Primary Option menu. Several of these options relate to Control-M. Through most of this guide, you will concentrate on two options:
-
Option 2, which provides access to the Scheduling Definition facility
-
Option 3, which provides access to the Active Environment screen, the main screen of the Tracking and Control facility.
-
Request Option 2 from the IOA Primary Option menu, to access the Scheduling Definition facility.
The Scheduling Definition Facility entry panel is displayed.
Figure1Control-M Scheduling Definition Facility - Entry Panel
Copy
----------- CONTROL-M SCHEDULING DEFINITION FACILITY - ENTRY PANEL ---------(2)
COMMAND ===>
SPECIFY LIBRARY, TABLE, JOB
LIBRARY ===> CTM.TEST.SCHEDULE
TABLE===>(Blank for table selection list)
JOB===>(Blank for job selection list)
SMART TABLE===>(Y - for new SMART Table
SHOW JOB DOCUMENTATION===> N(Y/N)
AUTO-SAVE DOCUMENTATION===> N(Y/N)
USE THE COMMAND SHPF TO SEE PFK ASSIGNMENT23.00.04
Introduction to the Scheduling Definition Facility
You are about to create a Control-M job scheduling definition for each of the jobs, IDJOB1 and IDJOB2, that you just defined. The JCL member name of the job should be used as the name of its corresponding job scheduling definition.
Job scheduling definitions are stored in tables (members) in a scheduling library. A default scheduling library name automatically appears in the entry panel. Ensure that you use a test library or your own work library. You should not use the JCL library.
For purposes of illustration in this guide, the scheduling library is identified as CTM.TEST.SCHEDULE. In this library, you will be creating a table called IDGS1. Use your unique identifier as the first characters of the table name.
You can now begin defining the job scheduling definition for IDJOB1.
-
Fill in the LIBRARY, TABLE, and JOB name fields in the entry panel. The request appears similar to Figure 2.
Figure2Control-M Scheduling Definition Facility - Entry Panel
Copy
----------- CONTROL-M SCHEDULING DEFINITION FACILITY - ENTRY PANEL ---------(2)
COMMAND ===>
SPECIFY LIBRARY, TABLE, JOB
LIBRARY ===> CTM.TEST.SCHEDULE
TABLE===> IDGS1(Blank for table selection list)
JOB===> IDJOB1(Blank for job selection list)
SMART TABLE===>(Y - for new SMART Table)
SHOW JOB DOCUMENTATION===> N(Y/N)
AUTO-SAVE DOCUMENTATION===> N(Y/N)
USE THE COMMAND SHPF TO SEE PFK ASSIGNMENT23.00.04After entering the entry panel request, the Job Scheduling Definition screen is displayed. A full job scheduling definition, which contains more lines than your screen can display, is illustrated in Figure3.
The first line in the screen, which is displayed above the COMMAND line, contains the same information about the job that you provided in the entry panel.
Figure3Job Scheduling Definition Screen
Copy
JOB: JOB1LIB CTM.TEST.SCHEDULETABLE: IDGS1
COMMAND ===>SCROLL===> CRSR
+-----------------------------------------------------------------------------+
MEMNAME IDJOB1MEMLIB
OWNERIDTASKTYPE JOBPREVENT-NCT2DFLTN
APPLGROUP
DESC
OVERLIBSTAT CAL
SCHENVSYSTEM IDNJE NODE
SET VAR
CTB STEP ATNAMETYPE
DOCMEMIDJOB1DOCLIB
===========================================================================
DAYSDCAL
AND/OR
WDAYSWCAL
MONTHS1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y
DATES
CONFCALSHIFTRETRO N MAXWAIT 00D-CAT
MINIMUMPDS
DEFINITION ACTIVE FROMUNTIL
===========================================================================
IN
CONTROL
RESOURCE
PIPE
FROM TIME+DAYSUNTIL TIME+DAYS
DUE OUT TIME+DAYSPRIORITYSACCONFIRM
TIME ZONE:
===========================================================================
OUT
AUTO-ARCHIVEYSYSDBYMAXDAYSMAXRUNS
RETENTION:# OF DAYS TO KEEP# OF GENERATIONS TO KEEP
SYSOUT OP(C,D,F,N,R)FROM
MAXRERUNRERUNMEMINTERVALFROM
STEP RANGEFR (PGM.PROC).TO.
ON PGMSTPROCSTCODESA/O
DO
SHOUT WHENTIME+DAYSTOURGN
MS
======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
COMMANDS: EDIT, DOC, PLAN, JOBSTAT11.17.00The Job Scheduling Definition screen is divided into sections, with each section separated from another by a line of equal signs (= =). Later, you will learn more about these sections and the fields they contain. The following table describes the fields of the Job Scheduling Definition screen that you will complete during these exercises.
Table1Job Scheduling Definition Screen Field Descriptions
Field
Description
MEMNAME
Name of the member that contains the JCL of the job.
MEMLIB
Name of the library that contains the JCL of the job.
GROUP
Name of the group to which the job belongs.
DESC
Free text description of the job.
DAYS
Days of the month to schedule the job.
CONFIRM
Yes/No indicator (Y/N) specifying whether manual confirmation is required before the job can be submitted.
OUT
Prerequisite conditions to be added and/or deleted when the job ends OK
-
Fill in the fields as indicated in the following table.
Table2Values for Job Scheduling Definition Screen Fields
Field
Value to Enter (in Bold), and Explanation
MEMNAME
IDJOB1. This value, taken from the entry panel, already appears, because you specified the JCL member name in the JOB field of the entry panel.
MEMLIB
Name of the library containing JCL member IDJOB1. For purposes of illustration, you should use CTM.TEST.JCL
GROUP
IDGRP1. This name will later be used to filter the display of jobs in the Active Environment screen by Group name.
DESC
THIS JOB MUST BE RUN BEFORE IDJOB2 (to remind you what this job does).
DAYS
ALL (Schedule the job every day.)
CONFIRM
Y (Yes - you want manual confirmation for the job.)
OUT
IDJOB1-ENDED-OK ODAT+(After specifying IDJOB1-ENDED-OK, press Tab to get to the field in which to enter ODAT.)
The Job Scheduling Definition screen is displayed as shown in Figure4.
Figure4Job Scheduling Definition Screen Showing Completed Fields
Copy
JOB: IDJOB1LIB CTM.TEST.SCHEDULETABLE: IDGS1
COMMAND ===>SCROLL===> CRSR
+-----------------------------------------------------------------------------+
MEMNAME IDJOB1MEMLIBCTM.TEST.JCL
OWNERIDTASKTYPE JOBPREVENT-NCT2DFLTN
APPLGROUP IDGRP1
DESCTHIS JOB MUST BE RUN BEFORE IDJOB2
OVERLIBSTAT CAL
SCHENVSYSTEM IDNJE NODE
SET VAR
CTB STEP ATNAMETYPE
DOCMEMIDJOB1DOCLIB
===========================================================================
DAYSALLDCAL
AND/OR
WDAYSWCAL
MONTHS1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y
DATES
CONFCALRETRO N MAXWAIT 00D-CAT
MINIMUMPDS
DEFINITION ACTIVE FROMUNTIL
===========================================================================
IN
CONTROL
RESOURCE
PIPE
FROM TIME+DAYSUNTIL TIME+DAYS
DUE OUT TIME+DAYSPRIORITY 00SACCONFIRM Y
TIME ZONE:
===========================================================================
OUTIDJOB1-ENDED-OKODAT +
AUTO-ARCHIVESYSDBMAXDAYSMAXRUNS
RETENTION:# OF DAYS TO KEEP# OF GENERATIONS TO KEEP
SYSOUT OP(C,D,F,N,R)FROM
MAXRERUNRERUNMEMINTERVALFROM
STEP RANGEFR (PGM.PROC).TO.
ON PGMSTPROCSTCODESA/O
DO
SHOUT WHENTIME+DAYSTOURGN
MS
======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
COMMANDS: EDIT, DOC, PLAN, JOBSTAT11.17.00 -
Exit the Job Scheduling Definition screen. The Job List screen is displayed.
Figure5Job List Screen
Copy
JOB LISTLIB: CTM.TEST.SCHEDULETABLE: IDGS1
COMMAND ===>SCROLL===> CRSR
OPTNAME ----- DESCRIPTION ---------------------------------------------------
IDJOB1THIS JOB MUST BE RUN BEFORE JOB2
====== >>>>>>>>>>>>>>>>NO MORE JOBS IN TABLE<<<<<<<<<<<<<<<<<<< =====
OPTIONS S SEL D DEL I INS O ORDER F FORCE J JCL C COPY P PLN T JOBSTAT 15.37.39The format of the Job List screen may be different than the format indicated in the screen example shown above. The different formats of the Job List screen will be discussed later in this chapter. The following procedure will ensure that you are working with the desired format.
-
Enter DESC in the COMMAND field of the Job List screen.
-
The Job List screen has the same format as the screen example shown above.
-
The Job List screen contains the list of jobs in the table. In this case, since you created a new table and only one job, there is only one job (IDJOB1) in the list. Notice that the description you provided in the job scheduling definition appears next to the job name in the Job List screen.Providing useful identifying information in the DESC field of the job scheduling definition can help you with job identification in the Job List screen.
-
You will now create the job scheduling definition for IDJOB2. You could do this much the same way that you created IDJOB1, that is, by returning to the entry panel and there specifying the name IDJOB2. But instead, you will create the job from the Job List screen.
-
-
Type I (Insert) in the OPT (Option) field to the left of the entry for IDJOB1, and press Enter.
Copy
JOB LISTLIB: CTM.TEST.SCHEDULETABLE: IDGS1
COMMAND ===>SCROLL===> CRSR
OPTNAME ----- DESCRIPTION ---------------------------------------------------
IIDJOB1THIS JOB MUST BE RUN BEFORE IDJOB2
====== >>>>>>>>>>>>>>>>NO MORE JOBS IN TABLE<<<<<<<<<<<<<<<<<<< =====The Job Scheduling Definition screen is displayed. When you create a new job using the I (Insert) option in the Job List screen, the newly created job contains most of values defined in the job by which you specified the Ioption. Only the MEMNAME, DOCMEM, and DESCRIPTION values are not carried over; instead, these fields are left blank.
Copy
JOB:LIB CTM.TEST.SCHEDULETABLE: IDGS1
COMMAND ===>SCROLL===> CRSR
+-----------------------------------------------------------------------------+
MEMNAMEMEMLIBCTM.TEST.JCL
OWNERIDTASKTYPE JOBPREVENT-NCT2 Y DFLTN
APPLGROUP IDGRP1
DESC
OVERLIBSTAT CAL
SCHENVSYSTEM IDNJE NODE
SET VAR
CTB STEP ATNAMETYPE
DOCMEMDOCLIB
===========================================================================
DAYSALLDCAL
AND/OR
WDAYSWCAL
MONTHS1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y
DATES
CONFCALSHIFTRETRO N MAXWAIT 00D-CAT
MINIMUMPDS
DEFINITION ACTIVE FROMUNTIL
===========================================================================
IN
CONTROL
RESOURCE
PIPE
TIME: FROMUNTILPRIORITY 00DUE OUTSACCONFIRM Y
TIME ZONE:
===========================================================================
OUTIDJOB1-ENDED-OKODAT +
AUTO-ARCHIVESYSDBMAXDAYSMAXRUNS
RETENTION:# OF DAYS TO KEEP# OF GENERATIONS TO KEEP
SYSOUT OP(C,D,F,N,R)FROM
MAXRERUNRERUNMEMINTERVALFROM
STEP RANGEFR (PGM.PROC).TO.
ON PGMSTPROCSTCODESA/O
DO
SHOUT WHENTIME+DAYSTOURGN
MS
======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
COMMANDS: EDIT, DOC, PLAN, JOBSTAT11.17.00 -
Type IDJOB2 in the MEMNAME field. The DOCMEM field will automatically be filled in with the same value. Leave the DESC field blank.
Copy
+-----------------------------------------------------------------------------+
MEMNAME IDJOB2MEMLIBCTM.TEST.JOBLIB
OWNERM44TASKTYPE JOBPREVENT-NCT2 Y DFLTN
APPLGROUP IDGRP1
DESC
OVERLIBSTAT CAL
SCHENVSYSTEM IDNJE NODE
SET VAR
CTB STEP ATNAMETYPE
DOCMEMIDJOB2DOCLIB
=========================================================================== -
In the IN field, define the same value you had defined as the OUT value inJOB1 (IDJOB1-ENDED-OK ODAT). You should press Tab before typing ODAT, as you did in IDJOB1. The + from the OUT value is not specified. After defining the IN value, delete the Y from the CONFIRM field.
Copy
===========================================================================
INIDJOB1-ENDED-OKODAT
CONTROL
RESOURCE
PIPE
FROM TIME+DAYSUNTIL TIME+DAYS
DUE OUT TIME+DAYSPRIORITY 00SACCONFIRM
TIME ZONE:
=========================================================================== -
Change the plus sign (+) to a minus sign (-) in the OUT statement.
Copy
===========================================================================
OUTIDJOB1-ENDED-OKODAT -
AUTO-ARCHIVESYSDBMAXDAYSMAXRUNSThe IN and the OUT fields are used for specifying conditions. These conditions can be used to create job dependencies.
In this exercise, you used condition IDJOB1-ENDED-OK to ensure that IDJOB2 would not be submitted until IDJOB1 successfully completed:
-
You made IDJOB1-ENDED-OK an IN condition for IDJOB2, which means that IDJOB2 cannot be run until this condition exists, that is, until IDJOB1-ENDED-OK has been created.
-
You made IDJOB1-ENDED-OK an OUT condition of IDJOB1, specifying a plus sign in the appropriate place in the condition definition, which means that the condition will only be created after IDJOB1 completed successfully.
Therefore, IDJOB1 must complete successfully before IDJOB2 can be submitted.
Specifying the same condition as an OUT condition with a minus sign in IDJOB2 removes the condition once IDJOB2 has successfully ended. This ensures that an old occurrence of the condition will not satisfy the IN criteria.
Every condition has an associated date value. This can be an explicitly defined date, such as 0909, or a valid keyword value that represents a date. ODAT is a keyword value that defaults to the current original scheduling date of the job. The original scheduling date, and other date concepts, are discussed in Chapter5, "AutoEdit and JCL."
-
-
Exit the job scheduling definition for IDJOB2. The Job List screen is displayed. IDJOB2 now appears in the list, but since you did not define a description for it, no description appears for the job.
Figure6Job List Screen
Copy
JOB LISTLIB: CTM.TEST.SCHEDULETABLE: IDGS1
COMMAND ===>SCROLL===> CRSR
OPTNAME -------- DESCRIPTION ------------------------------------------------
IDJOB1THIS JOB MUST BE RUN BEFORE IDJOB2
IDJOB2
====== >>>>>>>>>>>>>>>>>>>NO MORE JOBS IN TABLE<<<<<<<<<<<<<<<< =====
OPTIONS S SEL D DEL I INS O ORDER F FORCE J JCL C COPY P PLN T JOBSTAT 14.58.14Notice the options at the bottom of the Job List screen. You will now use one of them, the O (Order) option, to order these two jobs.
-
Request option O (Order) in the OPT field for both IDJOB1 and IDJOB2.
-
If a confirm window is displayed, confirm the job order by entering Y in the CONFIRM field.
Figure7Confirm Window
Copy
JOB LISTLIB: CTM.TEST.SCHEDULETABLE: IDGS1
COMMAND ===>+-------------------------------+SCROLL===> CRSR
OPTNAME ---|CONFIRM YODATE 020201| -----------------
OIDJOB1<===========|ASK FOR EACH ONEY|
OIDJOB2+-------------------------------+
====== >>>>>>>>>>>>>>>>>>>NO MORE JOBS IN TABLE<<<<<<<<<<<<<<<< =====
For each job ordered, the Job Order Messages screen with messages similar to the following will be displayed:Figure8Job Order Messages Screen
Copy
------------------------ CONTROL-M JOB ORDER MESSAGES --------------------(2.O)
COMMAND ===>SCROLL===> CRSR
-------------------------------------------------------------------------------
19.40.14 JOB501I CTMJOB STARTED
19.40.16 JOB528I MEMBER IDJOB1ID=0006I ODATE 020201 PLACED ON ACTIVE JOBS F
19.40.16 JOBD6BI NUMBER OF JOBS ORDERED -1
19.40.16 JOB525I CTMJOB ENDED
======= >>>>>>>>>>>>>>>>>>END OF MESSAGE LIST<<<<<<<<<<<<<<<<<<< ===== -
Press PF03/PF15 or enter the END command to exit the Job Order Messages screen each time it is displayed.
-
The Job List screen is displayed.
-
You can now enter the Active Environment screen and check the results of the job orders. You do not have to return to the IOA Primary Option Menu to request Option 3, the Active Environment screen. Instead, by preceding an option with an equal sign (=), you can move directly there from where you are.
-
-
Enter =3 in the COMMAND field.
-
The Active Environment screen is displayed.
-
Introduction to the Active Environment Screen
The Active Environment screen is your main interface to the Tracking and Control facility. It lists currently scheduled jobs. These jobs may or may not have already been submitted, and may or may not have already completed their executions.
Figure9Control-M Active Environment Screen
Copy
Filter:------- Control-MActiveEnvironment ------ UP<D>(3)
COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobID Typ ------------ Status -------------
CICSPROD M22020201 CICSPROD/04368 CST EXECUTING (RUN 1) GROUP=CICS-PROD
CICSTEST M22020201 CICSTEST/04372 CST EXECUTING (RUN 2) GROUP=CICS-TEST
BRIVPCCIVP020201 BRIVPCC /04369 JOB ENDED "OK"GROUP=BR-IVP-CC
BRCC0001 IVP020201 BRCC0001/04382 JOB ENDED "OK"GROUP=BR-IVP-CC
BRCC0002 IVP020201 BRCC0002/04383 JOB ENDED "OK"GROUP=BR-IVP-CC
BRCC0003 IVP020201 BRCC0003/04384 JOB ENDED "OK"GROUP=BR-IVP-CC
BRCCINDIVP020201 BRCCIND /04385 JOB ENDED "OK"GROUP=BR-IVP-CC
BRUPDT02 IVP020201 BRUPDT02/04387 JOB ENDED "OK"GROUP=BR-IVP-CC
BRREP001 IVP020201 BRREP001/04388 JOB ENDED "OK"GROUP=BR-IVP-CC
BRREP002 IVP020201 BRREP002/04389 JOB ENDED "OK"GROUP=BR-IVP-CC
BRIVPCCE IVP020201/JOB WAIT SCHEDULEGROUP=BR-IVP-CC
CRCCENDIVP020201/JOB WAIT SCHEDULEGROUP=BR-IVP-CC
INTR0001 M22020201/JOB HELD WAIT SCHEDULE
GROUP=INTER-PRODUCTION
INTR0002 M22020201/JOB HELD WAIT SCHEDULE
GROUP=INTER-PRODUCTION
INTR0003 M22020201/JOB WAIT SCHEDULE
GROUP=INTER-PRODUCTION
INTR0004 M22020201 INTR0004/04371 JOB ENDED- NOT "OK" - ABENDED
Commands: OPt DIsplay Show HIstory RBal REFresh Auto Jobstat SHPF Note Table
OPt command toggles between Commands and Options display15.15.48This screen is most probably displaying a number of jobs from your site that are not relevant to these exercises. Soon, you will filter the display so that only the relevant jobs are displayed. But first, look at the list of available commands or options at the bottom of the screen.
Toggling Between Display of Commands and Options
The bottom two lines of the Active Environment screen list either the commands or options available in the screen. Upon entry to the screen, the list of commands is displayed.
Commands: OPt DIsplay Show HIstory RBal REFresh Auto Jobstat SHPF Note Table
OPt command toggles between Commands and Options display15.15.
The first command listed is OPt, and the bottom line actually explains that command OPt can be used to toggle between the command display and the option display.
-
Enter OPT in the COMMAND field to toggle to the option display. The list of available options is displayed at the bottom of the screen.
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 Confirm15.46.0
-
Again, enter OPT in the COMMAND field to redisplay the list of available commands at the bottom of the screen.
Commands: OPt DIsplay Show HIstory RBal REFresh Auto Jobstat SHPF Note Table
OPt command toggles between Commands and Options display15.15.48
One or the other of the two lists will be particularly relevant for different steps, and you will be instructed, as necessary, to display the appropriate screen. Now that the Command display appears, notice the SHOW command. You will be using the SHOW command in the next set of steps.
Filtering the Active Environment Display
As mentioned above, when you enter the active environment the screen is probably displaying a number of jobs from your site that are not relevant to these exercises. The following steps show how you can filter the display.
-
Enter SHOW in the COMMAND field. The Show Screen Filter window is displayed.
Figure10Show Screen Filter Window
Copy
--------------------------- Show Screen Filter ---------------------(3.SHOW)-
FilterSave(Y/N) Desc:
Memname
Group
Sch LibTbl
======== In Process Y ======= | EndedY | ======= State Y ========
---------------------------------------------------------------------------
Wait SchedYWait timeY | Ended "OK"Y | FreeYForced OK Y
Wait ConfYWait CondY | Not "OK"Y | HeldYTbl HeldY
Wait SUBYWait quantY | RerunY | On ReqYCMEM Forc Y
SubmittedYWait contrl Y | DisappearedY | DeletedNNoteY
Wait ExecYTbl ActiveY | AbendedY | LateNRestarted Y
ExecutingY| Unexpected CCY | PseudoN
On Out Queue Y| JCL ErrorY |
Task Type: Job Cyc Emr Stc Cst Est Ecj Ecs Tbl Tbc
YYYYYYYYYY
Res Name
Resource Type: In Y Out Y Conds Y Resource Y Control Y
Owner
Odate:FromToPriority
JobAppl
CPU IdLPAR
-----------------------------------------------------------------------------
OPt command toggles between Commands and Options display11.07.49The Show Screen Filter window enables you to filter the display based on certain fields and values. The following steps explain what you need to know in order to create the filter for use in these exercises. Filtering is explained in greater detail in A Closer Look At Filters .
-
Specify that you want to create and save a filter called IDGS by entering IDGS in the Filter field, and Y in the Save field. Specify a description for the filter by typing GS-EXERCISES in the Desc field.
-
Define the filtering criteria by specifying IDGRP in the Group field. The filter appears as shown below:
Copy
+------------------- Show Screen Filter -----------(3.SHOW)+
|FilterIDGSSave Y (Y/N) Desc: GS-EXERCISES|
|Memname|
|GroupIDGRP|
|Sch LibTbl________|The Group field works on a prefix basis. By assigning the IDGRP prefix value, the filter will only display jobs whose Group name begins with IDGRP. This means only the current jobs in group IDGRP1. In later chapters, it will also display jobs belonging to groups idGRP2, idGRP3, and so on.
-
Press Enter to exit the window. The Active Environment now displays only IDJOB1 and IDJOB2.
Figure11Filtered Display in the Active Environment Screen
Copy
Filter: IDGS------- Control-MActiveEnvironment ------ UP<D> - (3)
COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobIDTyp ----------- Status ------------
IDJOB1ID020201JOB Wait Confirmation (for
Schedule)
IDJOB2ID020201JOB Wait Schedule
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ========
Confirming a Job Order
When you examine the Active Environment screen you will see the following:
-
A data line for each job order displays information about the job. This information includes the job name, job owner and the job order date (ODATE), as well as other information.
-
the status of each job order is displayed in the Status field for each data line.
When you examine the status of these jobs you will see the following:
-
The status of IDJOB1 is Wait Confirmation (for schedule).
-
The status of IDJOB2 is Wait Schedule.
Wait Confirmation (for schedule) status is displayed because you defined this job to require job confirmation.
Wait Schedule status is displayed because IDJOB2 cannot be scheduled, or submitted, until its prerequisite IN condition, IDJOB1-ENDED-OK,has been satisfied, and this can only occur after IDJOB1 successfully ends.
To confirm that JOB1 should be submitted you need to enter the appropriate option in the O (option) field by the job name.
-
Enter OPT in the COMMAND field to toggle the command/option display.
The list of available options is displayed at the bottom of the screen.
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 20.59.34
You can now see that to confirm the scheduling of a job, you should enter line command C (Confirm).
-
Enter C in the O (option) field, to the left of IDJOB1.
Copy
Filter: IDGS------- Control-MActiveEnvironment ------ UP<D> - (3)COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobIDTyp ----------- Status ------------
c IDJOB1ID020201JOB Wait Confirmation (for
Schedule)
IDJOB2ID020201JOB Wait Schedule
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ======== -
If a confirmation window is displayed, that is, if double confirmation is required, specify Y (Yes) in the confirmation window.
Figure12Confirmation Window
Copy
Filter: IDGS------- Control-MActiveEnvironment ------ UP<D> - (3)
COMMAND ===>SCROLL ==> CRSR
O Name+------------------------+ ---------- Status -------------
C IDJOB1<========|ConfirmY(Y/N)| Wait Confirmation (for
+------------------------+ Schedule)
IDJOB2ID020201Wait Schedule
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ========The Status field display changes for each of the two jobs, as they are executed.
-
Keep pressing Enter in the Active Environment screen.
If you press Enter quickly enough, you will note the following progression:
-
IDJOB1 changes status to Wait Submission.
-
IDJOB1 changes status to Submitted.
-
IDJOB1 changes status to Ended "OK".
-
IDJOB2 changes status to Wait Submission.
-
IDJOB2 changes status to Submitted.
-
IDJOB2 changes status to Ended "OK".
At the end of the process, the screen is displayed as follows:
Copy
Filter: IDGS------- Control-MActiveEnvironment ------ UP<D> - (3)
COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobIDTyp ----------- Status ------------
IDJOB1ID020201 M21JOB1 /21309JOB Ended "OK"
IDJOB2ID020201 M21JOB2 /21310JOB Ended "OK"
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ======== -
Checking the Log for the Job from the Active Environment Screen
You can use the L (Log) option of the Active Environment screen to check the job log for these jobs. The log is then displayed in the Control-M Log screen. If this option is specified for multiple jobs in the Active Environment screen, the log displays will be stacked. Each time PF03/PF15 is pressed, the next log in the stack is displayed, until all logs have been displayed.
Figure13 Log Option in the Active Environment Screen
Copy
Filter: IDGS------- Control-MActiveEnvironment ------ UP<D> - (3)
COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobIDTyp ----------- Status ------------
L IDJOB1ID020201 M21JOB1 /21309JOB Ended "OK"
L IDJOB2ID020201 M21JOB2 /21310JOB Ended "OK"
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ========-
Type L (Log) in the O (Option) field to the left of IDJOB1 and IDJOB2, and then press Enter. The log for IDJOB1 is displayed.
Figure14Control-M Log Screen
Copy
--------------------- LOG MESSAGES FOR JOB(S) IDJOB1-----------------(3.LOG)
COMMAND ===>SCROLL===> CRSR
SHOW LIMIT ON ==> USERID GROUP MEM/MISDATE 020201 - 020201
DATETIMEODATEUSERIDCODE------ M E S S A G E --------------------
020201 151226 020201 IDJOB511I JOB IDJOB1 OID=001JT ODATE 020201
TASK=ID /OS35/ID - PLACED ON AJF - THIS
JOB MUST BE RUN BEFORE IDJOB2
020201 151908 020201 IDCTM65AI JOB IDJOB1 OID=001JT ODATE 020201
CNFSCHED PERFORMED BY ID
020201 151911 020201 IDSEL203I JOB IDJOB1 OID=001JT ELIGIBLE FOR RUN
020201 151912 020201 IDSUB133I JOB IDJOB1 M21 /24861 OID=001JT
SUBMITTED FROM LIBRARY (P) CTM.TEST.JCL
020201 151917 020201 IDSPY28GI JOB IDJOB1 M21 /24861 OID=001JT TAPE
DRIVE UNITS USED=00 00
020201 151917 020201 IDSPY281I JOB IDJOB1 M21 /24861 OID=001JT START
01033.1519 STOP 01033.1519 CPU 0MIN
00.02SEC SRB 0MIN 00.00SEC 0.03 7AOS35
020201 151917 020201 IDSPY254I JOB IDJOB1 M21 /24861 OID=001JT SCANNED
020201 151918 020201 IDSEL250I JOB IDJOB1 M21 /24861 OID=001JT
CONDITION "IDJOB1-ENDED-OK ODATE 0202"
ADDED; RUN NUMBER=00001
020201 151918 020201 IDSEL208I JOB IDJOB1 M21 /24861 OID=001JT ENDED
"OK"
CMDS: SHOW, GROUP, CATEGORY, SHPF15.22.58You can see the clear progression of messages that were generated as the job executed under the control of Control-M. You can scroll the display forward to see additional lines.
-
Press PF03/PF15.
-
Press PF03/PF15 again.
The Active Environment screen is redisplayed.
As an alternative to using the Log option in the Active Environment screen to request the log display for specific jobs, you can use Option 5 (LOG) of the IOA Primary Option menu to request display of the IOA Log screen. This screen displays the log for all INCONTROL for z/OS products. You can then filter the display in much the same way that you filtered the display of the Active Environment screen.
The log for IDJOB2 is displayed.
Checking the Sysout for the Job
If Control-M/Restart is installed at your site, and the SYSDATA for a job is automatically archived, you can view the Sysout for that job.
To do so, you must first specify option V (View Sysout) for the job, in the Active Environment screen. This option displays the Job Order Execution History screen, which, as its name indicates, displays the execution history of the job. From the list of job executions, you can decide the job for which you want to view the Sysout.
To see the Sysout of a particular run of the job, specify option S (Select) next to the specific job execution in the Job Order Execution History screen. The sysout for the job is then displayed in the Sysout Viewing screen.
If Control-M/Restart is not operational at your site, or if SYSDATA is not archived, skip the remaining exercises in this section, and proceed to the topic "Holding and Deleting Active Environment Screen Job Orders" below.
Enter option V for job IDJOB1 to check the sysout of job IDJOB1.
The Job Order Execution History screen for IDJOB1 is displayed.
Figure15Job Order Execution History Screen
Copy
------------------------ JOB ORDER EXECUTION HISTORY ---------------------(3.V)
COMMAND ===>SCROLL===> CRSR
MEMNAME IDJOB1OWNER IDORDERID 001S3ODATE 020201
O JOBNAMEJOBIDDATESTART ELAPSED PAGES MAX RC --------- STATUS ---------
S M2132166020201 18:050:00 00003ENDED "OK"
======= >>>>>>>>>>> BOTTOM OF ACTIVE JOB ORDER HISTORY LIST <<<<<<<<<<< =======
OPTION:S SELECT02.52.14The Job Order Execution History screen, and the Sysout Viewing screen shown below, are discussed in Navigating the Active Environment.
-
Enter option S for the job run of IDJOB1 to request the desired Sysout.
The Sysout Viewing screen is displayed. You can scroll down and up, and right and left, through the Sysout.
Figure 16 Sysout Viewing Screen
Copy
------------- CONTROL-M/CONTROL-R SYSOUT VIEWING ------PAGE1 OF3
COMMAND ===>SCROLL===> CRSR
MEMNAME IDJOB1OWNER IDJOBNAME M21ODATE 020201
----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----81J E S 2J O BL O G--S Y S T E MO S 3 5--N O
0
18.05.20 JOB25002 ---- FRIDAY, 02 FEB 2001 ----
18.05.20 JOB25002IRR010IUSERID STCUSERIS ASSIGNED TO THIS JOB.
18.05.20 JOB25002ICH70001I STCUSERLAST ACCESS AT 18:03:22 ON FRIDAY, FEBRU
18.05.20 JOB25002ICH70001I STCUSERLAST ACCESS AT 18:03:22 ON FRIDAY, FEBRU
18.05.20 JOB25002$HASP373 M21STARTED - INIT 3- CLASS A - SYS OS35
18.05.20 JOB25002IEF403I M21 - STARTED - TIME=18.05.20
18.05.20 JOB25002-CPU (Total)Elapse
18.05.20 JOB25002-JobnameStepname ProcStepRCI/O hh:mm:ss.thhh:mm:
18.05.20 JOB25002-IDS100000.02
18.05.20 JOB25002IEF404I ID- ENDED - TIME=18.05.20
18.05.20 JOB25002-
18.05.20 JOB25002-M21Job Service Totals000.02
18.05.21 JOB25002$HASP395 M21ENDED
0------ JES2 JOB STATISTICS ------
-02 FEB 2001 JOB EXECUTION DATE
-8 CARDS READ
-44 SYSOUT PRINT RECORDS
COMMANDS: LEFT, RIGHT, FIND str, FIND str PREV, N n, P n, END18.17.39 -
Exit the Sysout Viewing screen, and then exit the Job Order Execution History screen, to the Active Environment screen.
Holding and Deleting Active Environment Screen Job Orders
Although it is unnecessary to delete these job orders from the Active Environment screen—they will probably be automatically deleted during New Day processing, which is discussed in Chapter7, "Job Ordering and New Day Processing"—you should do so anyway, as part of the lesson.
-
Type D (Delete) in the O (Option) field for both jobs, as shown below, and press Enter.
Figure17Delete Option in the Active Environment Screen
Copy
Filter: IDGS------- Control-MActiveEnvironment ------ UP<D> - (3)
COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobIDTyp ----------- Status ------------
D IDJOB1ID020201 M21/21309JOB Ended "OK"
D IDJOB2ID020201 M21/21310JOB Ended "OK"
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ========The jobs are not deleted. Instead, a message appears at the top of the screen, as shown below:
Copy
CTM653E CANNOT DELETE TASK IDJOB1 ODATE 020201 - NOT HELDUP<D> - (3)
COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobIDTyp ----------- Status ------------
D IDJOB1ID020201 M21/24861JOB Ended "OK"
D IDJOB2ID020201 M21/24866JOB Ended "OK"
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ========The message, CTM653E CANNOT DELETE TASK IDJOB1 ODATE 020201 - NOT HELD, indicates that the first requested deletion, that of job IDJOB1, could not be performed because the job is not Held. In fact, any action that affects a job order, or the status of a job order, cannot be performed until the job order is placed in Held status. To hold a job order, specify option H (Hold).
-
Replace the D option by each of the jobs with an H option and press Enter to place the jobs in Held status.
The status of each job order changes to Requested Held Ended "OK", and messages at the top of the screen indicate the change. The last issued message for IDJOB2 remains displayed at the top of the screen.
Copy
CTM659I HOLD OF TASK IDJOB2 GROUP "IDGRP1 " ODATE 020201 PERFORMED- (3)
COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobIDTyp ----------- Status ------------
IDJOB1ID020201 M21/24861JOB Requested Held Ended "OK"
IDJOB2ID020201 M21/24866JOB Requested Held Ended "OK"
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ======== -
Press Enter again.
The status of each job now changes to Held Ended "OK", and the message disappears.
Copy
Filter: IDGS------- Control-MActiveEnvironment ------ UP<D> - (3)
COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobIDTyp ----------- Status ------------
IDJOB1ID020201 M21/24861JOB Held Ended "OK"
IDJOB2ID020201 M21/24866JOB Held Ended "OK"
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ======== -
Once again, specify the D option by each of the jobs.
-
If a Delete Confirmation window is displayed, confirm the Delete request.
Messages at the top of the screen indicate that the jobs orders are deleted, and the last issued message for IDJOB2 remains displayed. The job orders no longer appear in the screen.
Copy
CTM659I DELETE OF TASK IDJOB2 GROUP "IDGRP1 " ODATE 020201 PERFORMED(3)
COMMAND ===>SCROLL ==> CRSR
O NameOwnerOdateJobnameJobIDTyp ----------- Status ------------
========= >>>>>>>>>>>>>Bottom of Jobs List<<<<<<<<<<<<< ========Do not confuse deleting a job order from the Active Environment screen with deleting a job scheduling definition from the Job List screen. Deleting the job order impacts only that order. The job scheduling definition itself remains unaffected and can be ordered again. If you delete a job scheduling definition from the Job List screen, the job scheduling definition itself is gone, and the job can no longer be ordered from the table.
Return to the Scheduling Definition Facility
In this chapter, you will do a little more work in the Scheduling Definition facility.
Saving Job Scheduling Definitions
So far, you have created and exited two job scheduling definitions—for IDJOB1 and IDJOB2. But they are currently only in memory; you have not saved them.
You can now save the job scheduling definitions. To do that you must first return to the Scheduling Definition facility.
-
Enter =2 in the COMMAND field.
The Job List screen is displayed.
-
Exit the Job List screen.
The Exit option window is displayed. This window prompts whether you want to save the job scheduling definitions you created.
Figure18Job List Screen Exit Option Window
Copy
JOB LISTLIB: CTM.TEST.SCHEDULETABLE: IDGS1
COMMAN +-----------------------------------------------------------+===> CRSR
OPTN |PLEASE SELECT EXIT OPTION|---------
i ||
i |SAVECREATE|
===== ||<<< =====
|LIBRARY CTM.TEST.SCHEDULE|
|TABLEIDGS1|
||
+-----------------------------------------------------------+
OPTIONS S SEL D DEL I INS O ORDER F FORCE J JCL C COPY P PLN T JOBSTAT 16.22.13The LIBRARY and TABLE fields indicate the library and table in which the job scheduling definitions were defined. The specified values can be modified, for example, to save the job scheduling definitions in a different table.
The window also contains SAVE and CREATE fields. The Exit Option window enables you to perform many actions.
-
To create a new table in a library and save the job scheduling definitions in that table, specify Y (Yes) in the CREATE field of the window, leaving the SAVE field blank, and exit the window.
Because you specified a new table name in the entry panel—one that had not previously existed—you are now going to permanently create that table as well. Therefore, the values you entered in this chapter are the values that you will use.
If you changed the library and table fields of the window to reflect a currently non-existing table, you would also use these values.
-
To save the job scheduling definitions in an existing table in a library, specify Y (Yes) in the SAVE field of the window, leaving the CREATE field blank, and exit the window. This procedure should be used even if you change the library and or table fields to a different, but existing, table.
-
To cancel the changes you made, specify N (No) in the both the SAVE and CREATE fields of the window, and exit the window.
-
To close the Exit Option window and remain in the Job List screen, with the changes remaining in memory, press PF04/PF16 to execute the RESET command.
-
-
Specify Y in the CREATE field and leave the SAVE field blank.
The new table is created and the job scheduling definitions are saved in the table. The Entry Panel is displayed.
Normally, when you exit the Job List screen, the Table List screen is displayed. However, if the Table List screen was bypassed when you entered the Scheduling Definition facility, that is, if you specified a TABLE value in the entry panel, which you did, the Table List screen is not displayed upon exiting the Job List screen; instead, the Entry Panel is displayed.
Selecting a Table from the Table List Screen
You can now enter the Table List screen so that it displays your newly created table.
-
Ensure that correct library name is entered in the LIBRARY field of the entry panel and that the TABLE field is blank.
The Table List screen is displayed. Unless you are using a library dedicated to this set of exercises, other table names appear in the Table list screen.
Figure19Control-M Table List Screen
Copy
LIST OF TABLES IN CTM.TEST.SCHEDULE-------------(2)
COMMAND ===>SCROLL===> CRSR
OPTNAME ------------ VV.MMCREATEDCHANGEDSIZEINITMODID
ADABAS01.00 98/09/09 00/05/09 00:5070700 O01
APPLNTN01.00 98/09/09 00/05/09 00:501801800 O01
APPLPRDI01.00 98/09/09 00/05/09 00:5041410 O01
ARCNIGHT01.00 98/09/09 00/05/09 00:50550 S07
ASMBTR101.00 98/09/09 00/05/09 00:50990 S07
ASMBTR201.00 98/09/09 00/05/09 00:5014140 S07
BACKUP01.00 98/09/09 00/05/09 00:50550 S07
CICSJOBS01.00 98/09/09 00/05/09 00:5070700 O01
CICSPROD01.00 98/09/09 00/05/09 00:501801800 O01
CICSTEST01.00 98/09/09 00/05/09 00:5041410 O01
CICSUPT01.00 98/09/09 00/05/09 00:50550 S07
CLIENTS01.00 98/09/09 00/05/09 00:50990 S07
DB2EXE01.00 98/09/09 00/05/09 00:5014140 S07
DLOAD01.00 98/09/09 00/05/09 00:50550 S07
MAINDAY01.00 98/09/09 00/05/09 00:501801800 O01
MAINT01.00 98/09/09 00/05/09 00:5041410 O01
MAINTPL01.00 98/09/09 00/05/09 00:50550 S07
ONSPOOL01.00 98/09/09 00/05/09 00:50990 S07
ONSPOOLT01.00 98/09/09 00/05/09 00:5014140 S07
OPERCLN01.00 98/09/09 00/05/09 00:50550 S07
OPTIONS S SELECTO ORDERF FORCEG GRAPHIC FLOWB BROWSED DELETE 15.38.37Among the options of the Table List screen are the options S (Select) and B (Browse). Both these options bring you to the Job List screen, where the list of jobs in the table are displayed, but each displays the Job List screen in a different mode:
-
The Select option displays the Job List screen in Edit mode. When you then select a job from the Job List screen, you can edit and update the job scheduling definition.
-
The Browse option displays the Job List screen in Browse mode. When you then select a job from the Job List screen, the job scheduling definition can be viewed, but it cannot be edited or updated.
You will not edit the job scheduling definition at this point, so use the B(Browse) option.
-
-
Either page down until the table name is visible, or perform an ISPF LOCATE to locate your table. Ensure that the cursor is in the OPTION field for your table.
-
Specify option B (Browse) in the OPTION field next to your table.
The Job List screen is displayed in Browse mode. The screen displays the two defined jobs in your table.
Figure20Job List Screen
Copy
JOB LISTLIB: CTM.TEST.SCHEDULETABLE: IDGS1
COMMAND ===>SCROLL===> CRSR
OPTNAME ----- DESCRIPTION ---------------------------------------------------
IDJOB1THIS JOB MUST BE RUN BEFORE IDJOB2
IDJOB2
====== >>>>>>>>>>>>>>>>NO MORE JOBS IN TABLE<<<<<<<<<<<<<<<<<<< =====
OPTIONS S SEL D DEL I INS O ORDER F FORCE J JCL C COPY P PLN T JOBSTAT 15.37.39From the Job List screen, you can now use the S (Select) option to browse either the IDJOB1 or the IDJOB2 job scheduling definition in the table.
In addition to the screen shown above, there are other possible formats of the Job List screen.
Formats of the Job List Screen
You had previously used the DESC command to ensure the desired format of the screen. This command confirmed that you wanted the display type that shows the description of the job, as taken from the DESC field in the job scheduling definition, to be displayed next to the job name.
Table3 describes the commands used to display other information.
Table3Commands to Display Job List Screen Formats
| Command | Description |
|---|---|
| DATA | Command DATA displays the Application name and Group name of the job next to the job name. The Application name and Group name are taken from the corresponding fields in the job scheduling definition. |
| STAT | Command STAT displays, next to the job name, the following ISPF-like statistical information about the job: Version and modification numbers, creation date, last modification date, and userID. |
Alternate between specifying the DATA, STAT, and DESC commands in the COMMAND field of the Job List screen, and note the differences in the display following the entry of each command. Ensure that the last command you enter is DESC, because that is the format you are using in the exercises in this guide.
Whichever format you use, the actual jobs listed in the screen, that is, jobs IDJOB1 and IDJOB2, remain the same. The format of the Job List screen does not affect which jobs are listed. It only affects the accompanying data that is displayed for those jobs.
Exiting the Online Facility
You have now finished the most of the exercises in this chapter of the guide. All that remains is to learn to exit the IOA Online facility.
Leave the online facility by exiting one screen at a time, until you have exited the entire online facility.
-
Press PF03/PF15 or enter the END command.
The Table List screen is displayed.
-
Press PF03/PF15 or enter the END command.
The Entry panel is displayed.
-
Press PF03/PF15 or enter the END command.
The IOA Primary Option Menu is displayed.
-
Enter X in the COMMAND field of the IOA Primary Option menu.
The IOA Online facility is exited.
Review
In this chapter you
-
accessed the following screens of the scheduling definition facility
-
Entry Panel
-
Table List screen
-
Job List screen
-
Job Scheduling Definition screen
-
-
created a job scheduling definition directly from the Entry panel, and then created a second job scheduling definition by using the I (Insert) option in the Job List screen
-
learned about and utilized the following job scheduling definition fields while creating your job scheduling definitions
-
MEMNAME
-
MEMLIB
-
GROUP
-
DESC
-
DAYS
-
IN
-
CONFIRM
-
OUT
-
-
defined one of the jobs to require manual confirmation before submission
-
used IN and OUT conditions to create a dependency between the two jobs
-
ordered the two jobs from the Job List screen
-
viewed messages in the Job Order Messages screen
-
moved between facilities using an =x command instead of returning to the IOA Primary Option menu
-
displayed the Active Environment screen, and toggled between display of the list of commands and the list of options at the bottom of the screen
-
defined a filter and filtered the Active Environment display
-
learned about statuses in the Active Environment screen
-
used the C (Confirm) option in the Active Environment screen to manually confirm a job
-
observed changes to job statuses in the Active Environment screen
-
used the L (Log) option in the Active Environment screen to display the message log for the job orders in the Control-M Log screen
-
used the V option to display the Job Order Execution History screen and from there displayed the Sysout of a job execution in the Sysout Viewing screen
-
used the H (Hold) option so that you could delete job orders from the Active Environment screen
-
used the D (Delete) option in the Active Environment screen to delete the job orders when they were no longer needed
-
used the Exit Option window of the Job List screen to create a new table and save your two job scheduling definitions in the table
-
learned the difference between the S (Select) and B (Browse) options of the Table List screen
-
changed the format of the Job List screen
-
exited the Online facility by working your way up the screen hierarchy as you exited individual screens
Recommended Reading
Before continuing with the next chapter, you should read the following in the Control-M for z/OS User Guide
-
In Chapter 1
-
Introduction to Control-M components
-
Prerequisite condition concept
-
Date concepts
-
-
In Chapter 2
-
Introduction to the Scheduling Definition Facility
-
Description of the following Scheduling Definition Facility screens including their formats, options and commands
-
Entry Panel
-
Table List screen
-
Job List screen
-
-
Description of the layout of the Job Scheduling Definition screen and the fields in the screen
-
Topics "Exiting the Scheduling Definition Facility" and "Ordering (Scheduling) Jobs" in the Scheduling Definition facility description
-
Introduction to the Active Environment screen and the description of its fields
-
Descriptions of the Control-M and IOA Log screens
-
-
In Chapter 3
Detailed descriptions of the parameters you have already used: CONFIRM, DAYS, DESC, GROUP, IN, MEMLIB, MEMNAME, OUT
The description of the parameter DAYS is quite detailed. Read it for a general understanding of parameter usage and possible parameter formats, without trying to memorize all the detail. For now, you can skip the information related to subparameters DCAL and AND/OR.
