ca7 11 users guide

CA-7 / CA-11User Guide

1

TABLE OF CONTENTS

IntroductionAbout CA-7 3Action Method Description 3Screen Method Description 3XQ, LQ Panels 4-7

Holding A Job In CA-7 8-9

Editing A Job In CA-7 10

Canceling A Job In CA-7 11-12

Restart/Rerun A Job In CA-7 13-15

Demanding A Job In CA-7 16

Return Codes in CA-7 17-18

Schid’s 19-20

PSI System Authority 21-22

JCL Override 23-24

Adding User Requirements 25-26

Creating & Submitting Change Requests 27-30

CA-7 Commands 31-37

Control-M VS CA-7 Commands 38

2

Introduction to CA-7

For the daily run of jobs, CA-7 does not have a User Daily that runs each morning at 8 a.m. to pull in jobs that will run for that day. Instead, CA-7 will scan lead jobs in a range of 4 hours with increments of 2 hours. For example, at midnight, CA-7 will scan in jobs that will run for the next 4 hours. At 2 a.m., CA-7 will scan again for jobs that will run between the time of 2 a.m. - 6 a.m., etc.

Users on CA-7 will have access to do the following: Hold, edit, cancel, restart/rerun, demand and make temporary scheduling changes to jobs. The Tech Team will resume responsibility with any permanent scheduling changes.

Action Commands:In CA-7, action commands can be entered from any CA-7 panel to produce immediate results.

By hitting the ‘HOME’ key and getting to the home space (top-left portion of your screen), you can type in command strings to do almost anything you want.

Screen Method:This is a mixture of using screens (menus) and commands. The screen method is slower, but it

is easier to use and understand if you are using CA-7 for the first time.

To get into CA-7 from the ISPF main menu, you type:E for EDS Applications7 for Scheduling Products7 for CA-7 (Production Job Scheduling)1 for Online Hit ‘Enter’ for the Main Menu or type an action command to get where you want. (For the quicker method of stacking commands, type E.7;7;1)

***NOTE: Pressing PF3 at any time during your CA-7 session will move you to the CA-7 Primary Option Menu, UNLESS you are editing JCL.

3

XQ, LQ Panels

XQ… Commands The XQ, XQJ, XQN and XQM action commands are used to display jobs in the Request, Ready or Active Queues. Updating of the job status is also allowed. A sample of the actions permitted while in these screens include CANCELling, RESTARTing, HOLDing, RELEASEing, REQUEUEing, UPDATEing and VERIFYing. These screens can also be accessed through the Queue Maintenance Menu (QM.1). The XQ… commands can be modified to include only specific jobs or a specific sequence. Specific command syntax can be found in the CA-7 Commands Guide.

____________________________________________________________________

XQM Command The XQM action command is used to update the status of jobs in the Request, Ready or Active Queues through the CPU JOBS STATUS SCREEN. This screen can also be accessed through the Queue Maintenance Menu (QM.1-M). The XQM command can be modified to specific jobs, job prefix or it can place the jobs in order based on jobname, CA-7 job number or requirement.

The following screen shows an example of the XQ commands and specifically XQM (CPU Jobs Status Screen):

4

XQ… Commands(continued)

The XQ command displays jobs in the order that they entered CA-7. The XQJ command displays jobs alphabetically by jobname. The XQN command displays jobs in numerical order. The XQM command lists jobs in jobname order with a graphical display showing codes identifying the job’s requirements. The table on the following page shows various XQ commands with a description of their output.

XQ Command Syntax XQ, JOB=, Q=, FILL=, LIST=

The following table describes the keywords.

Command Keyword Description

Format Use to clear the screen.XQM The code for the XQM represent

J JobI Internal Data SetE External Data SetU User RequirementN NetworkS Submit TimeH HoldJ JCL OverrideV Verify

JOB Jobname or prefix or CA-7 job numberQ Queue (REQ, RDY, ACT)FILL Function to be completed.

C CancelR RestartH HoldJ JCL OverrideP RSVP (Respond to prompt)Q RequeueR ReleaseS Submit Time OffU UpdateV VerifyX XQMT postE Edit JCL

LIST To select only jobs with a certain type of outstanding requirement (ALL, ANY, JOB, INT, EXT, USR, NWK, SUB, HLD, JCLO, VER, SKEL, BINT)

CLEAR Removes data from the panel

5

XQ----------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS -----------------

F- JOBNAME-- CA7# F-JOBNAME-- CA-7#GMBRINR2 5518 GMBRARCM 4076 JOB: *GMBRAAMA 6701 GMBRCMDX 9636 SEQ: ENTRYGMBRNVD3 4114 GMBRAAMH 6378 QUEUE: REQGMBRINR2 8235 GMBRAAMK 6379 LIST: ALLGMBRINR2 2764 GMBRINGB 4096GMBRINGB 4830 GMBRNVWV 5630 FUNCTIONS:GMBRINR2 4729 GMBRINGB 9660 C=CANCELGMBRINR2 0186 GMBRINR9 7379 F=RESTARTGMBRINDS 5591 H=HOLDGMBRINDS 2823 J=JCLOVRDGMBRCMDX 1978 P=RSVPGMBRINDS 8288 Q=REQUEUEGMBRAAME 5597 R=RELEASEGMBRINDS 4781 S=SUBTM OFFGMBRINDS 0332 U=UPDATEGMBRCMDX 4060 V=VERIFYGMBRINGB 7599 X=RQMT POSTGMBRINGB 2127 E=EDIT QJCL

PROGRAM: QM20 MSG-INDX: 00 -- QM.1-X -- 98.079 / 08:40:12MESSAGE: ENTER FUNCTION IN 'F' FIELD OR ENTER A COMMAND ON THE TOP LINE

**ATTENTION**: To see what a job is waiting for, type ‘X’ (‘RQMT POST’) next to the job.DO NOT TYPE ‘S’! ‘S’ stands for ‘SUBTM OFF’. If a job is waiting only for a time

and you type ‘S’, then you will submit the job. BE CAREFUL!

6

Queue Display The Queue list commands list information from the Request, Ready or Active Commands Queues. The queue information provided will show the status on all CA-7

production activity.____________________________________________________________________

Queue Display The LQ or LQUE commands display jobs in the Request, Ready and Active Action

Commands Queues. The LREQ command displays jobs in the Request Queue. The LRDY

Syntax command displays jobs in the Ready Queue. The LACT command displays jobs in the Active Queue.

The Table on the following page describes each of the Queue Display Action Commands with their possible keyword parameters:

LQ,ST=, JOB=, SEQ=, LIST=, SEG=, SYS=

LQLIST= DATE=98.078 PAGE 0001

JOB QUEUE CA-7 -DAY(DDD) ANDTIME(HHMM)-- CPU SCH ENTRY MST JOBNAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS

GMBRINR2 REQ 5518 072/2355 072/2300 072/2400 *NOEX* 030 SSCN 003 LATEGMBRAAMA REQ 6701 073/1355 073/1000 073/1400 *NOEX* 192 SSCN 001 LATEGMBRINR2 REQ 8235 075/2355 075/2300 075/2400 *NOEX* 030 SSCN 003 LATEGMBRINR2 REQ 2764 077/2355 077/2300 077/2400 *NOEX* 030 SSCN 003 LATEGMBRINGB REQ 4830 072/2025 072/1830 072/2030 *NOEX* 030 SSCN 003 LATEGMBRINR2 REQ 0186 076/2355 076/2300 076/2400 *NOEX* 030 SSCN 003 LATEGMBRINDS REQ 5591 073/0026 073/0001 073/0031 *NOEX* 030 SSCN 001 LATEGMBRINDS REQ 2823 078/0026 078/0001 078/0031 *NOEX* 030 SSCN 001 LATEGMBRCMDX REQ 1978 077/1855 077/1800 077/1900 *NOEX* 030 SSCN 001 LATEGMBRINDS REQ 8288 076/0026 076/0001 076/0031 *NOEX* 030 SSCN 001 LATEGMBRAAME REQ 5597 073/0155 073/0015 073/0200 *NOEX* 192 SSCN 001 LATEGMBRINDS REQ 0332 077/0026 077/0001 077/0031 *NOEX* 030 SSCN 001 LATEGMBRCMDX REQ 4060 078/1855 078/1800 078/1900 *NOEX* 030 SSCN 002GMBRINGB REQ 7599 075/2025 075/1830 075/2030 *NOEX* 030 SSCN 003 LATEGMBRINGB REQ 2127 077/2025 077/1830 077/2030 *NOEX* 030 SSCN 004 LATEGMBRNVD2 REQ 4066 078/1955 078/1800 078/2000 *NOEX* 030 SSCN 001GMBRCMS4 REQ 4067 078/1855 078/1800 078/1900 *NOEX* 030 SSCN 001GMBRARCM REQ 4076 078/1538 *NONE* 078/1538 ALL- 001 DEMD 001 LATEGMBRCMDX REQ 9636 076/1855 076/1800 076/1900 *NOEX* 030 SSCN 001 LATEGMBRAAMH REQ 6378 073/0755 073/0530 073/0800 *NOEX* 192 SSCN 001 LATEGMBRAAMK REQ 6379 073/0955 073/0600 073/1000 *NOEX* 192 SSCN 001 LATEGMBRINGB REQ 9660 076/2025 076/1830 076/2030 *NOEX* 030 SSCN 004 LATEGMBRINR9 REQ 7379 074/1825 074/1630 074/1830 *NOEX* 191 SSCN 001 LATE

SLIF-00 REQUEST COMPLETED AT 15:48:46 ON 98.078

**NOTE: Notice the ‘LATE’ notification in the ‘JOB STATUS’ column. With the job status of LATE, an on-call person will be notified. This is similar to a SHOUT in Control-M. If the job is running properly, the job status will be left blank.

7

Holding A Job Using CA-7

Action Command:.Press the ‘HOME’ key and enter the following command chain:

HOLD,JOB=xxxxxxxx or 9999 (job name or job #)

Note: If the same job is in the queue more than once, then you must use the job # if you use the action command.

This will take you to the EDS Hold Information screen (shown on the followong page). Enter in the correct information and check the XQ screen to see if the job is holding properly.

RELEASE: This command causes normal automatic scheduling activities to be applied to jobs that are in HOLD status in the CA-7 queues. The command is as follows:

RELEASE,JOB=xxxxxxxx or 9999 (job name or job #),Q=REQ or RDY

CAUTION: If you have the same job on hold in the queue more than once, and you use the release command using only the job name, then both jobs will be

released.

Screen Method:1) Press the ‘HOME’ key and enter ‘XQM’ to get the following screen-

XQM-------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS (RQMTS) --------------

F- JOBNAME--- J--I--E--U--N-SHJV F-JOBNAME---J--I--E--U--N-SHJVGMBRAAMA 1 . . . . GMBRINR2 3 . . . . JOB: * GMBRAAME 1 . . . . GMBRINR2 3 . . . . SEQ: JOBNAMEGMBRAAMH 1 . . . . GMBRINR9 1 . . . . QUEUE: REQGMBRAAMK 1 . . . . GMBRNVD2 . . . . . S LIST: ANYGMBRCMDX 1 . . . . GMBRCMDX 1 . . . . FUNCTIONS:GMBRCMDX 1 . . . . S C=CANCELGMBRCMS4 . . . . . S F=RESTART

H GMBRINDS 1 . . . . H=HOLDGMBRINDS 1 . . . . J=JCLOVRDGMBRINDS 1 . . . . P=RSPVGMBRINDS 1 . . . . Q=REQUEUEGMBRINGB 3 . . . . R=RELEASEGMBRINGB 4 . . . . S=SUBTM OFFGMBRINGB 3 . . . . U=UPDATEGMBRINGB 4 . . . . V=VERIFYGMBRINR2 3 . . . . X=RQMT POSTGMBRINR2 3 . . . . E=EDIT QJCL

PROGRAM: QM20 MSG-INDX: 00 -- QM.1-M -- 98.078 / 14:56:00MESSAGE: ENTER FUNCTION IN 'F' FIELD OR ENTER A COMMAND ON THE TOP LINE

2) Place an ‘H’ in the function field next to the job, and press enter to get to the EDS Hold Information screen.

8

----------------------------- EDS HOLD INFORMATION ----------------------------

JOB NAME: GMBRARCM DATE: 03/19/1998 TIME: 14:38:25JOB NUMBER: 4076USER ID: BZ8N7H

USER NAME: JOHN SMITHUSER PHONE: 248-265-1234HOLD DESCRIPTION: TESTING PURPOSES

(MAXIMUM OF 40 CHARACTERS)

PROGRAM: WBZP001 MSG-INDX: 00 -- WBZU0001 --MESSAGE: VIEW/UPDATE HOLD INFORMATION

3) Enter the correct information and press enter to get back to the Queue Maintenance screen.4) If your job is holding properly, an ‘H’ will appear in the ‘SHJV’ column as appears below-

-------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS (RQMTS) --------------F- JOBNAME--- J--I--E--U--N-SHJV F-JOBNAME---J--I--E--U--N-SHJV

GMBRAAMA 1 . . . . GMBRINR2 3 . . . . JOB: * GMBRAAME 1 . . . . GMBRINR2 3 . . . . SEQ: JOBNAMEGMBRAAMH 1 . . . . GMBRINR9 1 . . . . QUEUE: REQGMBRAAMK 1 . . . . GMBRNVD2 . . . . . S LIST: ANYGMBRCMDX 1 . . . . GMBRCMDX 1 . . . . FUNCTIONS:GMBRCMDX 1 . . . . S C=CANCELGMBRCMS4 . . . . . S F=RESTARTGMBRINDS 1 . . . . H H=HOLDGMBRINDS 1 . . . . J=JCLOVRDGMBRINDS 1 . . . . P=RSPVGMBRINDS 1 . . . . Q=REQUEUEGMBRINGB 3 . . . . R=RELEASEGMBRINGB 4 . . . . S=SUBTM OFFGMBRINGB 3 . . . . U=UPDATEGMBRINGB 4 . . . . V=VERIFYGMBRINR2 3 . . . . X=RQMT POSTGMBRINR2 3 . . . . E=EDIT QJCL


Individual Column Requirement Breakdown:‘J’= The number of requirements a specific job has before it can run‘I’= Internal Data Set‘E’= External Data Set‘U’= User Requirement‘N’= Network‘S’= Submit time‘H’= Hold‘J’= JCL override‘V’= Verification

9

Editing JCL In CA-7

Things to remember when editing JCL in CA-7:- The job must be in the queue.- The job you are editing is only for that specific job #. Be careful if there is more than one version of the job in the queue you are editing.- The last person who PF3’s out of the JCL is the one who saves the changes.

JCL ERRORS:If there is a JCL abend or error, check the job in SAM or WSF2. If the job comes down because of a JCL error, then the status of the job will be stuck in ‘RDY’ status, and you will have to REQUEUE the job.

REQUEUE: This command moves jobs from the Ready or Active queue back to the Request queue. This allows the user to utilize CA-7’s job restart facility.

The command is as follows:REQUEUE,JOB=xxxxxxxx,Q=RDY or ACT (Default is both)RDY= READYACT= ACTIVE

Action Command:Press the ‘HOME’ key and enter the following command string:EDIT,JOB=xxxxxxxx

Screen Method:1) Enter ‘XQM’ to get to the following screen, and place an ‘E’ next to the job you would like to edit.



E GMBRINDS 1 . . . . H=HOLDGMBRINDS 1 . . . . J=JCLOVRDGMBRINDS 1 . . . . P=RSPVGMBRINDS 1 . . . . Q=REQUEUEGMBRINGB 3 . . . . R=RELEASEGMBRINGB 4 . . . . S=SUBTM OFFGMBRINGB 3 . . . . U=UPDATEGMBRINGB 4 . . . . V=VERIFYGMBRINR2 3 . . . . X=RQMT POSTGMBRINR2 3 . . . . E=EDIT QJCL


2) That will get you into the JCL.

3) To exit the JCL, press PF-3.

10

Canceling A Job In CA-7

CANCEL: The CANCEL command cancels jobs from the CA-7 queues. The command may typically be used when lack of input for the scheduled run eliminates the need for that run or when a

scheduled run of a job was demanded to run ahead of schedule and should not be run again. Jobs that go into SKELETON (no JCL attached) status must be canceled specifying FORCE=YES. FORCE=YES will clear the CMT (Catalog Management Table) so future runs

will not attempt to use the restart information.

Action Command:Press the ‘HOME’ key and enter the following command chain:CANCEL,JOB=xxxxxxxx or 9999(job name or job #),REASON=___,FORCE=YESUse the job # when you are canceling a job that is in the queue more than once.FORCE=YES is to be used to cancel a SKELETON job or to cancel a job running under CA-11 and is in CA-11 resart status. FORCE=YES will set the CA-11 database back to production status.

Screen Method:1)Enter the ‘XQM’ command in the home-key space, and press enter. That will bring up this screen-



C GMBRINDS 1 . . . . H=HOLDGMBRINDS 1 . . . . J=JCLOVRDGMBRINDS 1 . . . . P=RSPVGMBRINDS 1 . . . . Q=REQUEUEGMBRINGB 3 . . . . R=RELEASEGMBRINGB 4 . . . . S=SUBTM OFFGMBRINGB 3 . . . . U=UPDATEGMBRINGB 4 . . . . V=VERIFYGMBRINR2 3 . . . . X=RQMT POSTGMBRINR2 3 . . . . E=EDIT QJCL


2) Place a ‘C’ in the function field next to the job, and press enter to get the next screen.

11

---------------- CA-7 QUEUE MAINTENANCE - REASON FOR CANCEL ----------------

JOB NAME: GMBRINDSJOB NUMBER: 4781

REASON:

(MAXIMUM OF 40 CHARACTERS)

PROGRAM: QM70 MSG-INDX: 00 -- QM.1-XC -- 98.082 / 13:35:01 MSGS 0001MESSAGE: REASON FOR CANCELING IS REQUIRED

3) Type in the reason for canceling the job, and press enter.

12

Restarting/Rerunning A Job In CA-7

**Note: A job must have ABENDED to use the restart utility. Remember, if the job has a JCL error, then you need to requeue the job (see page 6 for more info).

RESTART: The RESTART command restarts a job awaiting restart in the Request queue. The restart can be performed with or without CA-7.

Action Command:Press the HOME key, and enter this command chain:RESTART,JOB=xxxxxxxx,REASON=,PROCSTRT=,etc.You can restart/end your job at a precise location by adding the following commands after the JOB name in the following order:

PROCSTRT= procedure step to start - CA-11 onlyCaution:Use the PROCSTRT if you need to specify what job step.proc step to start

from. If you do not use this command when using the action command method, then CA-11 will restart from the top of the job.

PROCEND= procedure step to end - CA-11 onlySTPSTRT= jobstep to start - CA-11 onlySTPEND= jobstep to end processing - CA-11 onlyFORCECOMP=YES - forces job complete (flag as normally completed to CA-7 -

ignores abend status)SUP11STP= do not restart with CA-11 (don’t insert RMS step)REASON= 1-40 character reason for restartingBYPGDG= indicates whether or not CA-11 should bypass GDG logic - default is NO

Screen Method:1) Press the ‘HOME’ key and enter the QM.4 command to get this screen-

-------- CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS PROMPT -------- FUNCTION ===> (LEAVE BLANK EXCEPT TO TRANSFER) JOB TO BE RESTARTED =====> SPECIFIC NAME OR CA-7 JOB#

PROGRAM: QM50 MSG-INDX: 00 -- QM.4 -- 98.079 / 08:11:26MESSAGE: SPECIFY DESIRED JOB, TRANSFER OR ENTER A COMMAND ON THE TOP LINE

2) This screen allows you to restart a specific job. Type the job name into the given area and press enter to get the panel displayed on the next page.

13

------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS -----------JOB: GMBRARCM CODE: LAST-STEP: MCNT: 001 CA-7#: 4076 JES#: *NA* NODE-NAME: LOCAL

REASON: Re-start for production cycle.

-- -- RESUBMIT FOR PRODUCTION

-- -- FORCE COMPLETE-- X -- CA-11 RESTART/RERUN PSEUDO: NO

START: JS060.PS010 END:CC: BYPGDG: USAGE: LRTCD: = 0CMT STATUS: CMT SHOWS JOB IS SET FOR PRODUCTION

-- -- SET PARM DATA FOR RMS AND RESUBMITPARM:

-- -- DO NOT INSERT RMS PROC BUT RESUBMIT

PROGRAM: QM50 MSG-INDX: 00 -- QM.4-X -- 98.078 / 14:38:37MESSAGE: 'X' THE DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE

*WARNING* - RESTART/RERUN COULD SCRATCH GOOD DATASETS

Screen Description:

‘RESUBMIT FOR PRODUCTION’= This function will re-run the job from the top without using CA-11

‘FORCE COMPLETE’= This function will clear the CMT (Catalog Management Table) so future first runs of the job will not attempt to use the restart

information. It also considers the job complete and will post the next job in the cycle.

‘CA-11 RESTART/RERUN’= This function will attempt a CA-11 restart.Start - Starting step JOBSTEP.PROCSTEPEnd - Ending step JOBSTEP.PROCSTEP

(used if you wish to end the job before the actual end in the JCL)CC - Indicates an optional CA-11 condition code within the range of 0-0495 to be set

by the RMS step.BYPGDG - A value of ‘Y’ means that CA-11 will bypass / skip GDG restart logic and

will not reset PGENS.USAGE - Optional 1 character codeLRTCD - Highest return code from the previous run / abend - the value can be reset if

needed.‘SET PARM DATA FORRMS AND RESUBMIT’= This function will rerun the job without using CA-11 but the job

will be set to use CA-11 if desired if the job abends again.‘DO NOT INSERT RMSPROC BUT RESUBMIT’= To rerun a job set to restart using CA-11 without using CA-11.

Future abends will have to be rerun because the RMS step has been omitted.

14

***NOTE: The ‘CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS’ panel can also be accessed by the XQM screen. Place an ‘F’ next to the job name to restart and press enter.



F GMBRINDS 1 . . . . H=HOLDGMBRINDS 1 . . . . J=JCLOVRDGMBRINDS 1 . . . . P=RSPVGMBRINDS 1 . . . . Q=REQUEUEGMBRINGB 3 . . . . R=RELEASEGMBRINGB 4 . . . . S=SUBTM OFFGMBRINGB 3 . . . . U=UPDATEGMBRINGB 4 . . . . V=VERIFYGMBRINR2 3 . . . . X=RQMT POSTGMBRINR2 3 . . . . E=EDIT QJCL


------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS -----------JOB: GMBRARCM CODE: LAST-STEP: MCNT: 001 CA-7#: 4076 JES#: *NA* NODE-NAME: LOCAL

REASON: Re-start for production cycle.

-- -- RESUBMIT FOR PRODUCTION

-- -- FORCE COMPLETE-- X -- CA-11 RESTART/RERUN PSEUDO: NO

START: JS060.PS010 END:CC: BYPGDG: USAGE: LRTCD: = 0CMT STATUS: CMT SHOWS JOB IS SET FOR PRODUCTION

-- -- SET PARM DATA FOR RMS AND RESUBMITPARM:

-- -- DO NOT INSERT RMS PROC BUT RESUBMIT

PROGRAM: QM50 MSG-INDX: 00 -- QM.4-X -- 98.078 / 14:38:37MESSAGE: 'X' THE DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE

*WARNING* - RESTART/RERUN COULD SCRATCH GOOD DATASETS

4) Include a reason for restarting the job.

5) Place an ‘X’ in the desired REASON, and press enter.

6) This will bring you back to the ‘CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS (RQMTS)’ screen.

15

Demanding A Job In CA-7

***NOTE: Always consult with someone for verification before demanding a job into the queue.

***NOTE: Always force jobs in to execute on HOLD using the DEMANDH or RUNH command so you can double check how it is set up to run.

DEMAND: The DEMAND and DEMANDH commands force immediate scheduling of jobs controlled by CA-7. These commands may be used to schedule jobs that do not have definable

processing cycles and also force early execution of jobs which do have defined processing cycles.

When a DEMAND or DEMANDH command is issued, the job is placed in the Request queue where availability of its input requirements can be monitored. The job will not be submitted

until all of its input requirements have been satisfied.

The DEMAND command forces a job into CA-7 with all requirements and triggers based on the values of the keyword parameters. The DEMANDH command forces a job into CA-7 with all ofrequirements and triggers but on HOLD.

Action Command:Press the ‘HOME’ key and enter the following command string:

DEMANDH,JOB=xxxxxxxx,SCHID=,DOTM=, etc.

DOTM= due out time for the job (hours and minutes); default= current timeJCLID= data set ID containing the execution JCL to be submitted by CA-7JCLLIB= data set name containing the execution JCL to be submitted by CA-7LEADTM= amount of time in hours (0-23) and minutes (0-59); default= one hourSCHID= the schedule-ID to be used for this run (1-255) - default= 1. For example:

If you demand in a job for one time, use SCHID 70. If you want to demand in a cycle, then use the proper SCHID that was assigned.

SET= Special options:SKP: this run will take the place of the next scheduled runNTR: this run will NOT trigger anything elseNDB: the job will process normally but will not update the CA-7 database at

completionTIME= establishes a submit time-of-day requirement for the demanded jobDATE= specifies due-out or submit dates for the demanded jobDEPJOB= specifies one predecessor job which must complete while the demanded job is

waiting

RUN: The RUN and RUNH commands process a CA-7 job without verifying the availability of input requirements or performing the updates which normally follow successful job completion. No requirement posting or job triggering will occur. You do not have to use a SCHID with RUN or RUNH.

The RUN command will immediately submit a job to run without posting any requirements or triggering anything else. The RUNH command places only a HOLD condition on the job with

no other requirements or triggers.

RUNH,JOB=xxxxxxxx,DOTM=, etc.

16

RETURN CODES

GT- Greater thanGE- Greater than or equal toEQ- Equal toLT- Less thanLE- Less than or equal toNE- Not equal toFL- Mark the job abnormally terminated if the named step was flushed

If coded in Control-M as: then Code as the following in CA-7(use on the job definition screen):

1) on anystep <C**** COND-CODE:0 RO:GT

2) on anystep <C0001 COND-CODE:0 RO:LT

3) on anystep C0000 COND-CODE:0 RO:LT



6) on anystep C0200 COND-CODE:200 RO:NE

Examples using return codes for Job Steps that need to be added to the JCL just below the particular job step:

7) In Control-M, if you have: Anystep <C0001 and JS020 <C0016, then on the CA-7 job definition screen, you put COND-CODE: 0 RO: #S

Then you have to code the following in the JCL:

NOTE: Depending on what job step the condition code is for, place the #SCC statements within that specific job step. These # statements need to go after an EXEC statement.

//* //JS020 EXEC PGM=WAAPDSUT//*#SCC,COND=(15,LT,JS020)#JEND //*

17


Then you have to code the following in the JCL:

//* #SCC,COND=(4,LT,JS030)#JEND //*

9) In Control-M, if you have: Anystep <C0001 and JS050.PS010 C0201, then on the CA-7 job definition screen, you put COND-CODE: 0 RO: #S

Then you have to code the following in the JCL: //* #SCC,COND=(201,NE,JS050.PS010) #JEND//*


Then you have to code the following in the JCL: //*#SCC,COND=(4,LT,*-JS060) #SCC,COND=(15,LT,JS060) #JEND//* NOTE: The above is telling us to allow a return code <5 for every job step (*) except (-)

for JS060.

11) In Control-M, if you have: Anystep <C0005 and JS060 C0201, then on the CA-7 job definition screen, you put COND-CODE: 0 RO: #S

Then you have to code the following in the JCL: //*#SCC,COND=(4,LT,*-JS060) #SCC,COND=(201,NE,JS060) #JEND//*

18

SCHID’S

Use The Following SCHID’s When Creating Schedules.

Hourly - Jobs that run every hour (or numerous occasions) on a Daily Schedule

TIME Schedule ID’s

0100 hrs 001

0200 hrs 002

0300 hrs 003

0400 hrs 004

0500 005

ETC

v v

1200 hrs 012

ETC

v v

2300 hrs 023

1159 hrs 024

Day Of The Week: Jobs that are scheduled to run 1 day a week, every week.

1st RUN 1st DUP. 2nd DUP. 3rd DUP.

Monday 031 081 091 141

Tuesday 032 082 092 142

Wednesday 033 083 093 143

Thursday 034 084 094 144

Friday 035 085 095 145

Saturday 036 086 096 146

Sunday 037 087 097 147

Daily A Daily job is a job that is scheduled to run 2 or more days per week.

1st Run 1st Dup 2nd Dup 3rd Dup ETC.

030 040 041 042 043 thru 049

Duplicate jobs use SCHID 040 through 049.

19

Day of the Month: A Day of the Month job is a job that is scheduled to run 1 day a month (every month).

1st Run 1st Dup 2nd Dup

1st day of month 101 151 201

2nd day of month 102 152 202

3rd day of month 103 153 203

4th day of month 104 154 204

v v v v

30th day of month 130 180 230

31st day of month 131 181 231

Monthly: Schedules Less Frequently than Day of Week and Daily jobs.

1st Run 1st Dup 2nd Dup ETC.

051 061 062 063 thru 069

Annual: Using Dates in the Annual field only.


191 192 192 193 thru 200

On Request


070 071 072 073 thru 079

An On Request job is a job with no months and no DDMM or MMDD dates. An On Request job is a job that cannot be defined as:

Day of the Week Daily Day of the Month, or Monthly

20

PSI System Authority

1) Log onto PSI {E.7.P} 2) The first time you go into PSI/Zoom you will need to enter an ‘S’ at the top to get authorization.

----------------------- Production Scheduling Interface ----------------------- OPTION ===> S 04/22/1998 - 14:09 Julian Date: 1998.112 Job Name ===> * System Name ===> * Queue Activity 1 QUEUES - Request, Ready, and Active queue information 2 ABENDS - Production abends, fails, errors, and requeues 3 PRIOR RUN - Prior Run queue information Data Base Activity 4 RESOLVE - SPARM/ZPARM/Override JCL Resolution 5 DB MAINTENANCE - ZPARMs, overrides, resdates, job requests, user rqmts Special Activity L LOG DISPLAY - Browse CA7 on-line log S SYSTEM AUTHORITY - Add, delete, and list system ID authority T TUTORIAL - Display information about PSI V4.1 X EXIT - Terminate this session

21

The next thing you need to do is add your system name. Enter an ‘A’ and hit enter.

------------------------------ Authorization List ------------- RECORD DELETED COMMAND ===> A SCROLL ===> PAGE

Line Commands: Primary Commands:

D Delete System Name A Add System Name

System Name Privilege

---------------------------------------------------------------------------- ******************************* Bottom of data ********************************

Then you will enter a system name of gmbrrcm. Note this system name is for all of the BARS gmbr jobs in CA7.

---------------------------- Add Privilege Request ----------------------------COMMAND ===>

System Name ===> gmbrrcm

Upon hitting enter you will be returned to the Authorization screen and it should look as follow.

------------------------------ Authorization List ------------ Row 1 to 1 of 1 COMMAND ===> SCROLL ===> PAGE

Line Commands: Primary Commands: D Delete System Name A Add System Name System Name Privilege ----------------------------------------------------------------------------

_ GMBRRCM READ,WRITE ******************************* Bottom of data ********************************

You can PF3 and go back to the Main Menu.

22

JCL Override Edit Instructions

The OVERRIDE EDIT function lets a user maintain the account-level JCL overrides. JCL overrides are full replacements for the production job. Overrides are used to correct errors in the job stream or to accommodate a temporary change in the job's processing requirements. YOU MUST BE IN PSI to create, modify or delete an OVERRIDE. The user must have PSI WRITE authority on the CA-7 SYSTEM ID the job is defined to. The OVERRIDE LIBRARY is ACF SECURED for PSI use only.

IMPORTANT NOTE: The ZOOM interface to the PSI OVERRIDE EDIT function is not aware of the existence of the ALTERNATE LIBRARY. If you have an OVERRIDE to a DYNAMICALLY CREATED JCL JOB that is in the FUTURE or has EXPIRED, ZOOM will not be able to provide JCL to CA-7 and the job will be placed in SKELETON status.

Please read the entire procedure before using. Additional information can be obtained through PSI HELP and E.DF PSI USERS GUIDE V4.1 document.

1) Log onto PSI {E.7.P} 2) At JOBNAME, enter a JOBNAME or a * (wildcard) or a combination of each.3) Enter your CA-7 SYSTEM ID at the SYSTEM NAME.4) Enter option 5 for DB Maintenance. The following screen will appear:

------------------------ PSI CA-7 Data Base Maintenance --------- ENTER OPTION OPTION ===> Job Name ===> GMBR* System Name ===> GMBRRCM 1 USER RQMTS - Add, delete, and list user requirements. 2 JOB SCHEDULING - Add, delete, update, and list job requests. 3 ZPARM/OVERRIDE - Update and list ZPARM and override flags. 4 ZPARM VALUE - Add, delete, update, and list ZPARMs. 5 RESOLUTION DATE - Add, delete, update and list resolution dates. 6 OVERRIDE EDIT - Edit or browse override and reset override flag.

5) Enter option 6 for the Override Edit Screen. 6) Enter an 'S' in front of your SYSTEM NAME, which should be associated with an OVERRIDE LIBRARY.

--------------------------- Override Selection List --------- ROW 1 TO 1 OF 1 COMMAND ===> SCROLL ===> PAGE Job Name ===> GMBR* System Name ===> GMBRRCM Line Commands: S Select Override Library System Name Override Library ----------------------------------------------------------------------------S GMBRRCM PGMBR.RCMSC.OVERRIDE ******************************* BOTTOM OF DATA ********************************

7) The List Override Member Screen is displayed. If you specified a full or partial JOBNAME, and the OVERRIDE LIBRARY contains JOBs that met the naming scheme entered in JOBNAME, those member(s) will be listed for further selection. If no member matches the selection criteriaEnter 'A xxxxxxxx' at the command line, where: A indicates ADD blank indicates separator xxxxxxxx is the jobname desired and IS defined to CA-7. Select the member you wish to edit by placing the line command 'E' in front of the member name.

23

----------------------------- List Override Member ---------- NO MEMBERS FOUND COMMAND ===> SCROLL ===> PAGE Override Library ===> PGMBR.RCMSC.OVERRIDE Line Commands: Primary Commands: B Browse Override E Edit Override A Add Override Member D Delete Override Name Created Changed Time User ID ----------------------------------------------------------------------------******************************* BOTTOM OF DATA ********************************

CAUTION: Members already in the OVERRIDE LIBRARY dataset are NOT automatically refreshed from the MASTER JCL LIBRARY. If the JCL in the member is expired, delete all lines and obtain a fresh version of production before proceeding.

8) You will arrive at the Edit Screen. Your normal EDIT rules apply.9) Insert on the first line of the member. //*IN=mm/dd/yyyy,OUT=mm/dd/yyyy,SE=your name,PHONE=phone number where the 1st mm/dd/yyyy is the date you want CA-7 to begin using this JCLthe 2nd mm/dd/yyyy is the last date you want CA-7 to use this JCL. For the time being Override JCL will stay in the override library until someone manually deletes them.

10) At the command line, type in either pancopy or copy, to add the original JCL after the '//*IN' statement line.

NOTE: You MUST have JCL statements after the '//*in' line or CA-7 will declare the JOB to be in SKELETON status and the IPC will notify the on call person of the problem.

WARNING: A JEM in the override library does not work. It will cause an abend and kick you out of your JCL member without saving it.

11) Save by pressing 'PF3' or entering SAVE. The 'Override Member Added' message will appear on the List Override Screen.

Override Edit Results

To view the result of adding the OVERRIDE, Go to the CA7 Job Definition Screen DB.1Use the LIST function on the JOBNAME Added to the OVERRIDE LIBRARY. Verify that the 'JOBNET' Field has an 'OX' to indicate that the JOBNAME Job is coming from the PSI OVERRIDE LIBRARY.Exit the DB.1 screen when the LIST function is complete. If the IN and OUT dates have expired or are no longer valid, you may return to the PSI OVERRIDE function and delete the member you placed in the OVERRIDE LIBRARY. This will keep your OVERRIDE LIBRARY maintained. It will also help prevent the reuse of a potentially 'out of date' version of the Jobstream. Deleting the expired member manually also resets the 'OX' field on the CA-7 DB.1 screen to ‘ X’.

Please do not enter a member into the override library unless you are going through PSI/Zoom. By manually editing the library the jobnet flags do not get cleaned up and this will cause CA7 problems. This of course is a donut offense.

24

How to add a User Requirement to a Job in CA-7 for a specific date

From ISPF main menu, go to E.7;PChoose Option 5 for DB MAINTENANCE.Note: We will be using GMBRARGM and the date of 08/01/1998 for our example.Put in GMBRARGM for Job Name , and GMBRRCM for System Name.Hit Enter.

------------------------PRODUCTION SCHEDULING INTERFACE----------------------------

OPTION ===> 5 05/22/1998 - 14:07 Julian Date: 1998.142 Job Name ===> GMBRARGM System Name ===> GMBRRCM Queue Activity 1 QUEUES - Request, Ready, and Active queue information 2 ABENDS - Production abends, fails, errors, and requeues 3 PRIOR RUN - Prior Run queue information Data Base Activity 4 RESOLVE - SPARM/ZPARM/Override JCL Resolution 5 DB MAINTENANCE - ZPARMs, overrides, resdates, job requests, user rqmts Special Activity L LOG DISPLAY - Browse CA7 on-line log S SYSTEM AUTHORITY - Add, delete, and list system ID authority T TUTORIAL - Display information about PSI V4.1 X EXIT - Terminate this session

Enter 1 for USER RQMTS.Hit Enter.

------------------------ PSI CA-7 Data Base Maintenance ------------------OPTION ===> 1 Job Name ===> GMBRARGM System Name ===> GMBRRCM 1 USER RQMTS - Add, delete, and list user requirements. 2 JOB SCHEDULING - Add, delete, update, and list job requests. 3 ZPARM/OVERRIDE - Update and list ZPARM and override flags. 4 ZPARM VALUE - Add, delete, update, and list ZPARMs. 5 RESOLUTION DATE - Add, delete, update and list resolution dates. 6 OVERRIDE EDIT - Edit or browse override and reset override flag.

If there are no user requirements for this specific job, then the message NO RECORDS SELECTED will be in the upper right hand corner. To pull up a list of jobs, you can use part of the job name followed by an * (ex: GMBRAR* ).

To add a job, type A at the command and Hit Enter.

25

----------------------- List Data Base User Requirement NO RECORDS SELECTEDCOMMAND ===> A SCROLL ===> PAGE Job Name ===> GMBRARGM System Name ===> GMBRRCM Apply Date ===> 08/01/1998 (MM/DD/YYYY) Line Commands: Primary Commands: D Delete requirement S Display requirement A Add requirement System Apply A Requirement Added Job Name Name Date P User Requirement... On At By ---------------------------------------------------------------------------

Fill in the following fields, if they are not there automatically. Make sure the date format is MM/DD/YYYY. When you have filled out all of the fields, then hit Enter.

The job now has a User Requirement for 08/01/1998 and will not run until the SE removes the extra requirement which happens to be a Hold.

------------------------- ADD User Requirement --COMMAND ===> System Name ===> GMBRRCM Job Name ===> GMBRARGM Apply Date ===> 08/01/1998 (MM/DD/YYYY) SE Name ===> JOHN SMITH SE Phone ===> 8-365-1234 Requirement ===> Hold the job for production.

26

Creating and Submitting Schedule Change Requests

Creating / Submitting Schedule Change Requests

If you identify a scheduling problem, complete a scheduling change request.

From the TSO main menu, type E.7. On the next screen, type P for PSI (Production Scheduling Interface).

--------------------------------------- Scheduling Products MENU ---------------------------------------OPTION ===> p

Select Product:

7 CA-7 - Production Job Scheduling UserID - FZFJ91 11 CA-11 - Production Job Restart Date - 98/01/05 P PSI - Production Scheduling Interface Julian - 98.005 J PRO-J - Production Job Reporting Time - 07:54 OC ON-CALL - On-Call Support Application Terminal - 3278

X EXIT - Return to Previous Menu

Enter END to Exit

----------------------------------------- Production Scheduling Interface ----------------------------------------OPTION ===> 5 01/05/1998 - 07:55

Julian Date: 1998.005Job Name ===> wdopmr01System Name ===> wdopop

Queue Activity1 QUEUES - Request, Ready, and Active queue information 2 ABENDS - Production abends, fails, errors, and requeues 3 PRIOR RUN - Prior Run queue information

Data Base Activity4 RESOLVE - SPARM/ZPARM/Override JCL Resolution 5 DB MAINTENANCE - ZPARMs, overrides, resdates, job requests, user rqmts

Special Activity L LOG DISPLAY - Browse CA-7 on-line log S SYSTEM AUTHORITY - Add, delete, and list system ID authority T TUTORIAL - Display information about PSI V4.1 X EXIT - Terminate this session

27

Creating / Submitting Schedule Change Requests(continued)

----------------------------------- PSI CA-7 Data Base Maintenance ----------------------------------OPTION ===> 2

Job Name ===> WDOPMR01 System Name ===> WDOPOP

1 USER RQMTS - Add, delete, and list user requirements. 2 JOB SCHEDULING - Add, delete, update, and list job requests. 3 ZPARM/OVERRIDE - Update and list ZPARM and override flags. 4 ZPARM VALUE - Add, delete, update, and list ZPARMs. 5 RESOLUTION DATE - Add, delete, update and list resolution dates. 6 OVERRIDE EDIT - Edit or browse override and reset override flag.

Enter END command to terminate function

------------------------------------ Job Scheduling Requests ------------------------------------OPTION ===> 2

Job Name ===> WDOPMR01 System Name ===> WDOPOP

1 ADD JOB - Add a new job. 2 CHANGE JOB - Change an existing job.3 DELETE JOB - Delete an existing job.4 LIST REQUESTS - List job requests.

Enter END command to terminate function

28

Scheduling Requests The scheduling request is comprised of three screens which request the following information:

------------------------------------------ Change Request -------------------------------------------------COMMAND ===> Panel 1 of 3 Job Name ===> WDOPMR01 System Name ===> WDOPOP Schedule ID ===> ___ IPC Node ===> ________ Effective Date ===> __________ (MM/DD/YYYY) Production JCL Library ===> ____________________________________________ SE to Contact for Questions: Name ===> ____________________ Office Phone ===> ______________ Dial-8 Prefix ===> ___ (nnn) Job Type ===> _ ( T riggered, S cheduled) -Triggered Job: Triggering Job Name ===> ________ (job that will trigger WDS144WE) or -Scheduled Job: Day of Week ===> Sun _ Mon _ Tue _ Wed _ Thu _ Fri _ Sat _ (X) or Monthly ===> J _ F _ M _ A _ M _ J _ J _ A _ S _ O _ N _ D _ (X) Business: F _ L _ (X) or Actual: F _ L _ (X) or Day of Month: __ (01-31) or On Request ===> _ (X) Holiday Roll ===> _ ( B ack, F orward, N o roll, D rop) -All Jobs: Submit Time ===> _____ (HH:MM) Due Out Time ===> _____ (HH:MM) Lead (run) Time ===> _____ (minutes) ZPARMs or SPARMs ===> _ (Y or N) Overrides Used ===> ___ (Y or N) Condition Code ===> ___ (highest acceptable cond. code in any job step) Job Dependence ===> ________ ________ ________ ________ ________ ===> ________ ________ ________ ________ ________ Conflicting Jobs ===> ________ ________ ________ ________ ________ ===> ________ ________ ________ ________ ________ Tape Drives ===> __ (cartridge) __ (triple density) (maximum in any job step) Additional Info ===> _______________________________________________________ _______________________________________________________ _______________________________________________________ Prose Restart ===> _______________________________________________________ _______________________________________________________ _______________________________________________________ Press ENTER to save the record Enter END to display previous panel

(See the next page for explanatory notes on how to complete the schedule change request screens.)

29

Explanatory Notes: 1. Schedule ID - You will need to supply the appropriate schedule id. If the job runs on different schedules at different times, be sure to use the right SCHID for the change you are requesting. If your jobs requires changes for more than one SCHID, separate change requests will be needed.

2. IPC Node - For example, AHIPC1N.

3. Effective Date - Type slashes and use a four-digit year. Day of the month cannot be prior to the current day.

4. Production JCL Library - Probably PWDS1.SPOCH. JCLPAN. Use the library name where your JCL resides.

5. Triggered jobs are those which run when a preceding job completes. Typically, the first job in a job stream is scheduled with a set date and time and the succeeding jobs are triggered.

6. Mark desired scheduling options with an ‘X.’ “Business” means “business day” and ‘F’ and ‘L’ mean “first” and “last.” Since, you may specify first or last business day, first or last actual day, or a specific day of the month.

7. Holiday Roll - Specify if you want the job to roll backward or forward when its normal execution day falls on a holiday.

8. Complete the rest of the information as necessary. Contact the PMG scheduling group with any questions.

30

CA-7 Commands

Overview This document provides information about the most commonly used CA-7 commands and their associated parameters. Only the commonly used parameters are listed. This document is not a substitute for the Computer Associates CA-7 Command Guide; details regarding the options listed and the additional options available can be found in the Command Guide.

COMMAND DESCRIPTION AND SYNTAX/DISPLAY,ST=JCL Use this command to obtain information about the JCL libraries attached

to CA-7. The ST=JCL parameter provides information about the JCL libraries and their associated ID number.

/DISPLAY,ST=JCL

/DISPLAY,PRINT=SCH Use this command to obtain information about the values for schedule scan (SSCAN). The PRINT=SCH parameter provides information about SSCAN such as the INCR, SPAN and QDWELL intervals and the next run.

/DISPLAY,PRINT=SCH

CANCEL,JOB=,FORCE=,REASON=

Use this command to cancel a job in CA-7 skeleton (*SKL) mode when the skeleton mode is an error. This command will not cause any job requirement posting or triggering. If the jobname is not unique, then you must supply the CA-7 job number. Obtain the job number by issuing the top-line CA-7 command: XQJ,JOB=jobname.

CANCEL,JOB=jobname or CA-7 job number,FORCE=YES,REASON=description

DEMANDH,JOB=,SCHID=nnn

Use this command to request a job to run in CA-7. This command will place a HOLD on the job which must be posted. A reason for the hold will be required.

The SCHID parameter should be a value that does not exist for the given job if triggering is not to be done. If triggering is needed, then the appropriate SCHID should be supplied. Requirement posting will occur even if triggering does not. A parameter of SET=NTR may be used if no triggering is to occur; this may be supplied in addition to the non-existent SCHID value.

DEMANDH,JOB=jobname,SCHID=nnn

FJOB,FROM=,TO=,SYS= Use this command to obtain forecasted job execution information for jobs in a specified system for a specified date and time period.

FJOB,FROM=(mmddyy,hhmm),TO=(mmddyy,hhmm),SYS=system name

FJOB,SPAN=,SYS= Use this command to obtain forecasted job execution information for jobs in a specified system for a specified future time span in hours.

FJOB,SPAn=hh,SYS=system name

COMMAND DESCRIPTION AND SYNTAXFSTRUC,JOB=,LIST= Use this command to obtain job flow structure information for a job. The

LIST=ALL parameter provides the job trigger relationships and the

31

elapsed time of each job

FSTRUC,JOB=jobname,LIST=ALL

LACT,JOB=,SYS= Use this command to obtain CA-7 information on jobs in the active queue. The JOB=jobname parameter can be a specific job or can be a generic mask such as JOB=GSAJ*. The SYS=system name parameter can be either an ‘*’ indicating all systems or the value must be a specific system name.

LACT,JOB=jobname or SYS=system name

LDSN,DSN=,LIST= Use this command to obtain information about a dataset. The DSN parameter can be used with the dataset name or dataset number if known. The LIST=ALL parameter provides information about the dataset, the using jobs and any documentation entries.

LDSN,DSN=dataset name or dataset number,LIST=ALL

LIST,JOB= Use this command to obtain a list of jobs in CA-7 that have not successfully completed.

LIST,JOB=jobname

LISTDIR,DSN=*SCAL* Use this command to obtain the complete list of all calendars known to CA-7.

LISTDIR,DSN=*SCAL*

LJCL,JOB= Use this command to review the JCL contained in the associated JCL library.

LJCL,JOB=jobname

LJOB,JOB= Use this command to obtain miscellaneous information about a job. The LIST=ALL parameter provides information about the job requirements, triggers and characteristics or attributes.

LIST=TRIG parameter provides information about the job triggers.

LJOB,JOB=jobname,LIST=ALL or LIST=TRIG

LQ,JOB= Use this command to obtain CA-7 information on the jobs in the ready, request and active queues

LQ,JOB=jobname

LQ,JOB=,ST=ABND Use this command to obtain CA-7 information on the jobs in the request that are in abend status.

LQ,JOB=jobname,ST=ABND

LQ,JOB=,ST=LATE Use this command to obtain CA-7 information on the jobs in the request that are in late status.

LQ,JOB=jobname,ST=LATE

COMMAND DESCRIPTION AND SYNTAXLPROS,JOB= Use this command to review the prose for a job.

LPROS,JOB=jobname

LPRRN,JOB=,LIST= Use this command to review the last run of a job. The information is obtained from the prior-run queue. The LIST=ALL parameter is optional

32

and provides all data relative to the queue.

LPRRN,JOB=jobname,LIST=ALL

LRLOG,SPAN=,SYS= Use this command to review the run log information for jobs in a specified system for the specified span of time in hours.

LRLOG,SPAN=hh,SYS=system name

LSCHD,JOB=,LIST= Use this command to obtain information about the schedule(s) for a job. The SCAL=SIDnnn parameter provides the schedule information for a specific schedule identifier (SCHID). (The ‘nnn’ in the SIDnnn should be the SCHID.) The LIST=BYSID parameter provides scheduling information for all SCHIDs. This is useful if a job has multiple SCHIDs. A month-by-month calendar is displayed for both parameters.

LSCHID,JOB=jobname,LIST=SIDnnn or LIST=BYSID

PRINT,SCAL=,YEAR= Use this command to review the calendar settings. The SCAL value is the last two (2) characters of the calendar name. The YEAR= is optional. The default is the year the command is issued. The year parameter is the last two (2) positions of the year.

LPRINT,SCAL=xx,YEAR=yy

REQUEUE,JOB=,Q= Use this command to move a member from the ready (RDY) or active (ACT) Queue to the request (REQ) Queue. The Q=queue name parameter is optional. If the Q=queue name parameter is not used, then the RDY and ACT Queues are both searched and the job is placed in the REQ Queue. This command must be used whenever a job enters the REQ Queue in skeleton mode (no JCL attached to job).

REQUEUE,JOB=jobname,Q=ACT or Q=RDY

RUNH,JOB= Use this command to execute a special run of a job so that requirements will not be posted, and triggering will not occur. This command places a HOLD on the job which must be posted.

RUNH,JOB=jobname

XQJ,JOB=,Q= Use this command to review and/or perform actions on the request queue. The JOB=jobname parameter may be a specific jobname or generic such as JOB=GSAJKN*. The Q=queue name parameter is optional and the queue name may be REQ (request), RDY (ready) or ACT (active). The list is displayed in jobname sequence.

If no members are found matching the jobname criteria, the QUEUE MAINTENANCE panel is displayed.

XQM,JOB=jobname,Q=REQ or Q=RDY or Q=ACT

COMMAND DESCRIPTION AND SYNTAXXQM,JOB=,Q= Use this command to review and/or perform actions on the request queue.

The JOB=jobname parameter may be a specific jobname or generic such as JOB=GSAJKN*. The Q=queue name parameter is optional and the queue name may be REQ (request), RDY (ready) or ACT (active). The list is displayed in jobname sequence and a summary of the requirements is displayed.

If no members are found matching the jobname criteria, the QUEUE MAINTENANCE panel is displayed.

33

XQM,JOB=jobname,Q=REQ or Q=RDY or Q=ACT

34

Commonly Used CA-7 Commands

COMMON REQUESTS COMMANDADDING A REQUIREMENT TO A JOB THAT IS ALREADY IN THE REQUEST QUEUE:

ADDRQ,JOB=XXXXXXXX,DEPJOB=XXXXXXXX

OR

ADDRQ,JOB=XXXXXXXX,USR=MESSAGE UP TO 36 CHARACTERS

CANCEL A JOB FORM THE QUEUE: CANCEL,JOB=NNNN,FORCE=YES,REASON=UP TO 40 CHARACTERS (NNNN=CA-7 NUMBER)

DISPLAY/VIEW CALENDARS: DB.2.8 OR A TOP LINE COMMAND OF CALMOD

DEMANDING A JOB: DEMANDH,JOB=XXXXXXXX,SCHID=XX,TIME=XXXX,LEADTM=XXXX,DOTM=XXXX,TYPE=RES,SET=SKP,SET=NTR

TYPE=RES: SO JOB CAN BE SET FOR RESTART AT A CERTAIN STEP

SET=SKP: TO BYPASS THE NEXT SCHEDULE

SET=NTR: DISABLE JOB TRIGGERS

DISPLAY JCL-ID LIBRARIES: /DISPLAY,ST=JCLVAR

DISPLAY SCAN TIMES: /DISPLAY,PR=SCH

DISPLAY CALENDAR NAMES: LISTDIR,DSN=*SCAL*

FORECASTING YOUR SCHEDULE: FJOB,FROM=(MMDDYY,HHMM),TO=(MMDDYY,HHMM), JOB=XXXXXXXX OR SYS=CUSTSYS

FJOB,FROM=(MMDDYY,HHMM),SPAN=XX,JOB=XXXXXXXX OR SYS=CUSTSYS

FJOB,SYS=CUSTSYS,FROM=MMDDYY,SPAN=XX,TRIG=N (WILL NOT SHOW TRIGGERED JOBS)

TO DO A FORECAST AND PRINT OUT THE DESCRIPTION INFORMATIONON DB.4.1:

LIST=WP

FORECASTING USING A REVERSE JOB FLOW. IT ANSWERS THE QUESTION, HOW DOES THIS JOB GET INTO THE SYSTEM.

FRJOB=JOBNAME,SCHID=SCHEDULE ID

TO VERIFY IF YOUR JOB TRIGGERS ARE SET UP CORRECTLY, US THE FOLLOWING COMMAND:

FSTRUC,JOB=XXXXXXXX,SCHID=XX,FROM=MMDDYY

JCL CHECK JCK,JOB=********

INCLUDE STATEMENTS WITHIN THE JCL.

#J1 - JOB INCLUDE

#JO - JOB OMIT

35

COMMON REQUESTS COMMAND#NOX - MAKES THIS RUN NON-EXECUTABLE

TO DISPLAY JOBS THAT ARE ACTIVE: LACT

LIST JOBS SHOWING UP LATE: LACT,ST=LATE

LIST JCL, SHOWS WHERE THE JCL RESIDES:

LJCL,JOB=XXXXXXXX

LIST JES JOB # LJES,JOB=XXXXXXXX,Q=ACT {ACTIVE QUEUE(DEFAULT)}

LJES,JOB=XXXXXXXX,Q=PRN (LPRRN QUEUE)

LJES,JOB=XXXXXXX,Q=* (ALL QUEUES)

LIST INFORMATION ABOUT A JOB:

TO DISPLAY ALL JOBS FOR A CUST/SYS CODE: LJOB,SYS=XXXXXXXX

TO DISPLAY ALL INFORMATION ABOUT A JOB: LJOB,=XXXXXXXX,LIST=ALL

TO DISPLAY JOBS DEPENDENCIES FOR A JOB: LJOB,=XXXXXXXX,LIST=DEPJ

LJOB,=XXXXXXXX,LIST=RQJOB

TO DISPLAY JOB INPUT REQUIREMENTS: LJOB,=XXXXXXXX,LIST=RQMT

LJOB,=XXXXXXXX,LIST=RQUSR

TO DISPLAY SCHEDULE INFORMATION: LJOB,=XXXXXXXX,LIST=SCHD

TO DISPLAY ALL JOBS THAT TRIGGER THIS JOB, AS WELL AS ALL JOBS THAT THIS JOB WILL TRIGGER: LJOB,=XXXXXXXX,LIST=TRIG

JOBS LOCKED UP: LLOCK,JOB=*

IF REPLY IS JOB SCHEDULE INFORMATION IS LOCKED, DO A RESOLVE ON SCHEDULE

TO DISPLAY THE PRIOR RUN OF A JOB: LPRRN,JOB=XXXXXXXX OR LPRRN,JOB=XXXXX*

TO LIST CURRENT REQUIREMENTS OF JOBS IN THE REQUEST QUEUE:

LQ,LIST=RQMT,JOB=XXXXXXXX

TO DISPLAY THE JOBS IN THE REQUEST QUEUE IN JOB ORDER:

LQ,SEQ=JOB

TO FIND OUT WHAT JOBS ARE ON HOLD:

LQ,SEQ=JOB,ST=HELD

TO DISPLAY THE JOBS WAITING IN THE READY QUEUE:

LRDY

TO DISPLAY THE JOBS IN THE READY QUEUE THAT HAVE AN ABNORMAL STATUS:

LRDY,ST=RSTR

TO DISPLAY THE JOBS IN THE LREQ,ST=LATE,SEQ=JOB OR SEQ=DOTM

36

COMMON REQUESTS COMMANDREQUEST QUEUE THAT ARE FLAGGED AS LATE (CAN DISPLAY IN EITHER JOB NAME SEQUENCE OR IN DUE OUT TIME ORDER).

TO DISPLAY JOBS IN THE REQUEST QUEUE THAT HAVE AN ABNORMAL STATUS:

LREQ,ST=RSTR

RUN LOG INFORMATION:

CAN BE USED FOR LAST FIVE DAYS

LRLOG,JOB=XXXXXX*,DATE=*YYDDD (DDD=JULIAN DATE)

LIST SCHEDULES:

TO DISPLAY SCHEDULE DATES AND CALENDAR. LSCHD,JOB=XXXXXXXX,LIST=CALS

TO DISPLAY SCHEDULE DATES FOR A JOB. LSCHD,JOB=XXXXXXXX,LIST=SCHD

37

Control-M vs CA-7 Functions

Control-M Option CA-7 Command/Option? - Why XQ -Option X

H - Hold HOLD,JOB=xxxxxxxxXQ -Option H

D - Delete XQ -Option C (not for skeleton jobs)CANCEL,JOB=xxxxxxxx,REASON=___CANCEL,JOB=xxxxxxxx,REASON=___,FORCE=YES(FORCE=YES is for skeleton jobs)

F - Free XQ -Option RRELEASE,JOB=xxxxxxxx

L - Log LRLOG,JOB=xxxxxxxx,DATE=yyddd,ST=ALLE.7.P(PSI/ZOOM) -Option L

Z - ZoomTo add in conditions ADDRQ,JOB=xxxxxxxx,DEPJOB=depjob or USR=description

To post in-conditions XRQ,JOB=xxxxxxxx or XQ -Option X

To change a job’s submit time XQ -Option USUBTM,JOB=xxxxxxxx,TIME=hhmm

To remove a job’s submit time XQ -Option SSUBTM,JOB=xxxxxxxx

To FORCE a job complete RESTART,JOB=xxxxxxxx,FORCECOMP=YES

To change a job’s due-out time XQ -Option UADDSHC,JOB=xxxxxxxx,TIME=mmmm(1-1440 minuets)

R - Rerun/RestartControl-M XQ -Option F (Place X next to Resubmit for Production)

RESTART,JOB=xxxxxxxx,REASON=___

Control-R XQ -Option F (Place X next to CA-11 Restart)RESTART,JOB=xxxxxxxx,PROCSTRT=procstep,STPSTRT=jobstep,REASON=___

V - View Can’t view output in CA-7 - To see the JES2 job number compared to the CA-7 job number: LJES (if job is active)

- in SAM look at the JCL portion of the output directly under job card.

S - Stat LPRRN,JOB=xxxxxxxxLPRRN,JOB=xxxxxxxx,LIST=JCL(list JCL from last good

run.)

E - Edit XQ -Option E

38

ca7 11 users guide

Documents