CA7FIN2

Table of Contents
CA-7 VERIFICATION PROCESS OVERVIEW..........................................................................................2 GATHERING CURRENT CONTROL-M SCHEDULE INFORMATION............................................3 TSO CMI.................................................................................................................................................................3 CONTROL-M SCHEDULE..............................................................................................................................................4 TSO CMR/TSO PRO-J JOB HISTORY.........................................................................................................6 PRO-J SUMMARY REPORT EXAMPLE.............................................................................................................................7 PRO-J DETAIL REPORT EXAMPLE.................................................................................................................................7 CA-7 JOB SCHEDULE INFORMATION REPORT...................................................................................8 VERIFY JOB DEFINITION..............................................................................................................................................9 VERIFY JOB SCHEDULE..............................................................................................................................................10 VERIFY JOB TRIGGERS...............................................................................................................................................12 VERIFY PREDECESSORS AND SUCCESSORS ....................................................................................................................13 VERIFY RESOURCE REQUIREMENTS .............................................................................................................................14 VERIFY OTHER REQUIREMENTS ..................................................................................................................................14 VERIFY SCHEDULE EXECUTION...................................................................................................................................15 CREATING AND SUBMITTING SCHEDULE CHANGE REQUESTS.............................................16 CA-7 HELPFUL HINTS..................................................................................................................................20 PF3.........................................................................................................................................................................20 TOP LINE COMMAND AREA.......................................................................................................................................20 GETTING AROUND IN CA-7.......................................................................................................................................20 CA-7 FUNCTION COMMANDS ....................................................................................................................................20 CA-7 JOB TIME PARAMETERS ...................................................................................................................................20 CA-7 SCHEDULE CONCEPTS ......................................................................................................................................20 LOGGING ON TO CA-7................................................................................................................................21 CA-7 SCREENS AND MENU PANELS.......................................................................................................23 CA-7 COMMAND GUIDE..............................................................................................................................29 CA-7 COMMAND EXAMPLES.....................................................................................................................32 CA-7 SCHIDS.....................................................................................................................................................37 CA-7 CALENDARS...........................................................................................................................................39 FIX CA-7 ABEND..............................................................................................................................................41 DYNAMIC JCL CREATION PROCEDURE FOR CA7...........................................................................44 CA7 OVERRIDE LIBRARY PROCESS .....................................................................................46
CA-7 VERIFICATION CHECKLIST...........................................................................................................48
Date Revised 02/19/98 1 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc
CA-7 Verification Process Overview
Verification of your job schedules in CA-7 will be accomplished in the following four steps: 1. 2. 3. 4. Determine which jobs to verify first. Annual, quarterly, and some on-request jobs may not need to be verified immediately if you do not expect them to execute shortly after CA-7 goes live (in February). If time becomes a problem, verify daily, weekly and other critical job streams first. Generate the CA-7 job schedule information report as described herein. This report will contain virtually all CA-7 scheduling information you will need to complete the verification process. Compare the information in the CA-7 report with information in Control-M for each job in your system(s). Submit a change request to the EDS-SPO Scheduling group for any corrections or modifications to the CA-7 job schedule.
Additional information has been provided in this document that may be useful. If you have any questions, please consult your CA-7 Conversion Team representative.
Gathering Current Control-M Schedule Information
The following information is provided to aid you in gathering information about your current job schedules. This information must be compared with that in CA-7. There are other tools for gathering scheduling information -- forecasts, rplans, etc. This is only a recommended list. Use whatever you feel you need to ensure your schedules are set up correctly in CA7. This information may be viewed online or screen-printed if you prefer to work with hard copies. A recommended approach is to view Control-M information online and work from the printed copy of the CA7 Report.
TSO CMI
For in-conditions and dependencies, run times, calendar and table names, and some schedule information execute the clist TSO CMI [jobname]. This produces a screen similar to the following:
+ * * * * * * * * * * * * * * * * * * * * * * * * * * * * =DISPLAY CONTROL= ONLINE CONTROL/M CROSS REFERENCE I-IN CONDITION (Y) E-EXCLUSIVE (N) SEARCH(WDFNIN31) D-DEPENDENT (Y) **** J O B **** PROJ TABLE WAIT TIME SB DATEMEM WDFNIN31-WDFNIN PWDFN DIN01DLY 07 9999 A INVCAL5A I--WDFNIN6-|WDFNI I-WDFNIN0J-WDFNIN WDFNIN31-WDFNIN PWDFN DIN01MTH 07 9999 O INVCAL5A I-WDFNIN0J-WDFNIN I-WDFNIN60-WDFNIN D-WDFNINPA-WDFNIN PWDFN DIN01DLY 07 9999 O INVCAL5A D-WDFNIN3H-WDFNIN PWDFN DIN01DLY 07 9999 O INVCAL5A D-WDFNIN32-WDFNIN PWDFN DIN01DLY 07 9999 A INVCAL5A D-WDFNIN51-WDFNIN PWDFN DIN01DLY 07 9999 O INVCAL5A D-WDFNINNE-WDFNIN PWDFN DIN01FRI 07 9999 O INVCAL5A D-WDFNIN3B-WDFNIN PWDFN DIN01FRI 07 0400 O INVCAL5A D-WDFNIN32-WDFNIN PWDFN DIN01MTH 07 9999 A INVCAL5A D-WDFNIN33-WDFNIN PWDFN DIN01MTH 07 9999 A INVCAL5A D-WDFNIN51-WDFNIN PWDFN DIN01MTH 07 9999 O INVCAL5A * * * * * * * * * * *
MTWTFSS YYYYY
JFMAMJJASOND YYYYYYYYYYYY YYYYYYYYYYYY
YYYYY YYYYY Y YYYYY Y Y Y Y
YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY
This information is adequate for verifying most on-request jobs and those without specific date/time parameters.
Control-M Schedule
To view all current scheduling information in detail, type E.CM;2 on the command line of the ISPF Primary Option Menu.
----------------------OPTION ===> E.CM;2 0 1 2 3 4 5 6 7 9 A C E L S U T X ISPF PARMS BROWSE EDIT UTILITIES FOREGROUND BATCH COMMAND DIALOG TEST IBM PRODUCTSACCOUNT CHANGES EDS LOCAL SAM USER TUTORIAL EXIT ISPF/PDF PRIMARY OPTION MENU -----------------------FZFJ91 14:51 97/12/17 97.351
Userid Specify terminal and user parameters Time Display source data or output listings Date Create or change source data Julian Perform utility functions Invoke language processors in foreground Submit job for language processing Enter TSO Command, CLIST, or REXX exec Perform dialog testing Additional IBM program development products Display Account Applications Display summary of changes for this release EDS Corporate Applications Display IPC Local Applications System Activity Manager User developed functions Display information about ISPF/PDF Terminate ISPF using log and list defaults
Enter END command to terminate ISPF. ----------------- CONTROL-M SCHEDULING FACILITY - ENTRY PANEL --------------(2) COMMAND ===>
SPECIFY LIBRARY, SCHEDULING TABLE, JOB LIBRARY ===> XXXXX.CTMSC.SCHEDULE TABLE ===> DIN01DLY (Blank for table selection list) JOB ===> WDFNIN01 (Blank for job selection list)
SHOW JOB DOCUMENTATION AUTO-SAVE DOCUMENTATION
===> N ===> Y
(Y/N) (Y/N)
USE THE COMMAND "SHPF" TO SEE PFK ASSIGNMENT
14.53.14
1. 2.
For the library, replace XXXXX with the customer code (PWDOP, PWDFN, PWDS1 ETC.) If you dont know the name(s) of the table(s) on which your job runs, see the section above on TSO CMI. Otherwise, you may leave the table and jobname fields blank, press ENTER, and locate table names beginning with your 3-digit system code and select the table you wish to browse. 3. The same job may be scheduled on several tables (daily, weekly, monthly etc). Be sure to check all tables on which your job is scheduled. NOTE: If you accidentally enter an invalid table name, you will be taken to a blank schedule definition panel and will not be able to exit using PF3. If this happens, type RESET on the command line and then press PF3.
JOB: WDFNIN01 LIB PWDFN.CTMSC.SCHEDULE TABLE: DIN01DLY COMMAND ===> SCROLL===> CRSR +-----------------------------------------------------------------------------+ | MEMNAME WDFNIN01 MEMLIB PWDFN.CTMSC.D%%ODATE.EXECJCL | | USER ID WDFNIN TASKTYPE JOB GROUP WDFNIN PREVENT-NCT2 | | DESC | | SET VAR | | DOCMEM WDFNIN01 DOCLIB PWDFN.CTMSC.DOCLIB | | =========================================================================== | | DOC | | DOC | | =========================================================================== | | DAYS DCAL | | AND/OR O | | WDAYS 1,2,3,4,5 WCAL | | MONTHS 1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10 Y 11 Y 12 Y | | DATES | | DATEMEM INVCAL5A SHIFT RETRO N MAXWAIT 07 D CATEGORY | | MINIMUM PDS | | =========================================================================== | | IN WDFNIN-WDFNIN1R ODAT | | CONTROL | USE THE DOC COMMAND TO SHOW/HIDE JOB DOCUMENTATION 14.53.48 +-----------------------------------------------------------------------------+ | CONTROL | | RESOURCE SYSTEM-INIT-X 0001 | | TIME FROM UNTIL PRIORITY | | =========================================================================== | | OUT WDFNIN-WDFNIN01 ODAT + | | AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS | | SYSOUT OP (C,D,F,N,R) FROM | | RERUN - MAXRERUN RERUNMEM INTERVAL | | STEP RANGE FR (PGM.PROC) . TO . | | ON PGMST ANYSTEP PROCST CODES <C0009 A/O | | DO OK | | DO | | ON PGMST PROCST CODES A/O | | DO | | SHOUT WHEN TO URGN | | MS | ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====
If you have any questions about this information, talk to your team members or your CA7 Conversion Team representative first before calling the EDS-SPO Scheduling group.
TSO CMR/TSO PRO-J Job History

All of the Job History has now been converted and exists in PRO-J. A CLIST has been created to access this utility by typing TSO PROJ. All jobs are defined to CA-7 as of January 1998 and have been running in quiet mode (triggering but not executing) since then. Run history is listed in PRO-J with a completion status of NOSUB.
------------COMMAND ===> Pro J - Production Job Reporting System ------------ WMR1100 -TIME - 16:10 TERMINAL - 3278
The following reports are available: Summary Report 1 Detail Listings 2 All Jobs 3 Abended Jobs Report : Node Mask : AHIPC* Job Name Mask : * Exclude Job Mask: Start Date/Time : -1 End Date/Time : Report DSN Report Unit FZFJ91 : : SYSDA
(1,2 or 3) (* masking) (* masking) (* masking) 0800 (MMDDYYYY HHMM-default yesterday 0800) 0800 (MMDDYYYY HHMM-default today 0800) (default = SYSDA) (optional)
ACTIVE FOR NODE AHIPC1N
Specifying a Report DSN will create a DASD report otherwise an ISPF panel of the report will be displayed. Note: Job execution information is updated at regular intervals. Recently run jobs may not show up on the reports.
1. 2. 3. 4. 5. 6.
Report - Select either 1 for Summary Report, 2 for All Jobs and 3 for Abended Jobs. Node Mask - AHIPC* . Job Name Mask - Enter job name or part of name and use* as a wild card. Exclude Job Mask - Enter job name to be excluded or part of name and use * as a wild card. Start Date/Time - Enter date or a negative number will give the number of days prior to the current day. For example, -1 will have a start date of yesterday. End Date/Time - Enter date and time of the search criteria.
Pro-J Summary Report Example

---------------COMMAND ===> NODE=(AHIPC* ) Pro J - Production Job Reporting SUMMARY REPORT JOB=(WDOPMR01) Jobs ended Jobs ended normally Jobs ended abnormally Abended CC error JCL error Jobs not submitted ---------------- WMR1100 -EXC JOBS=( )
FROM=( 1/05/1998 08:00) TO=( 1/06/1998 08:00) : : : : : : : 2 1 ( 50.0%) 0 0 0 0 ( ( ( ( 0.0%) 0.0%) 0.0%) 0.0%)
1 ( 50.0%)
Pro-J Detail Report Example

---------------COMMAND ===> NODE=(AHIPC* ) Pro J - Production Job Reporting DETAIL LISTING - ALL JOBS JOB=(WDOPMR01) --------ROW 1 TO 2 OF 2 SCROLL => CSR EXC JOBS=( )
FROM=( 1/05/1998 08:00) TO=( 1/06/1998 08:00) RF COMPLETION LAST PROC RO STATUS STEP STEP -- ----------- -------- -------NOSUB,BE/AF ********************************
NODE JOB JOB ---START--- ---STOP---NAME NAME NO. DATE TIME DATE TIME ------- -------- ----- mmddyy ---- mmddyy ---AHIPC1N WDOPMR01 0 010598 1854 010598 1854 AHIPC1N WDOPMR01 7277 010598 1826 010598 1856 ******************************* BOTTOM OF DATA
CA-7 Job Schedule Information Report
Copy the JCL in SYS4.PROJECT.P351074.CA7SPO(CA7LJOB) to your catalog and modify it as follows: 1. 2. 3. 4. Change all XXXXXX to your logonid. Change all ZZZZZZ to your access code. Change all YYYYYY to your customer/system code (e.g.. WDFNIN, WDOPMR, WDFPTR, WDS144, etc.) Print the output dataset if you wish to work from a hardcopy report.
BROWSE -- SYS4.PROJECT.P351074.CA7SPO(CA7LJOB) - 01.0 LINE 00000000 COL 001 080 COMMAND ===> SCROLL ===> CSR ********************************* TOP OF DATA ********************************** //XXXXXX22 JOB (ZZZZZZ,SC74),'CA-7 LJOB BY CUST/SYS', // CLASS=T, // COND=(4,LE), // MSGCLASS=Y, // MSGLEVEL=(1,1), // REGION=0M, // NOTIFY=XXXXXX, // RESTART=* //* //JS010 EXEC PGM=SASSBSTR, // PARM='0,POOL=(1-8)' //UCC7CMDS DD DISP=SHR,DSN=SYS2.CA-7.COMMDS //SYSPRINT DD DSN=XXXXXX.CA-7.LJOB.YYYYYY, // DISP=(NEW,CATLG,DELETE), // UNIT=PERMDA, // SPACE=(TRK,(1,5),RLSE), // DCB=(SYS3.DSCB, // RECFM=FB,LRECL=133,BLKSIZE=13300) //SYSUDUMP DD SYSOUT=* //SYSOUT DD SYSOUT=* //SYSIN DD * LJOB,JOB=YYYYYY*,LIST=ALL /LOGOFF /* ******************************** BOTTOM OF DATA ********************************
Verify Job Definition

Locate the job information on the CA-7 report for the job you want to verify. The first section of information for each job looks like this:
JOB NAME
----JCL---ID MEMBER
SYSTEM -NAMEWDFNXY
USR MAIN PROSE -ID -ID- DSNBR 000 ALL
SCHED DSNBR
--NUMBER OFSTP DDS RUNS
LAST-RUN DATE/TIME 97316/0400
WDFNWXYZ 011 WDFNWXYZ
*NONE* 001321 000 000 0000
--------------------------- JOB INFORMATION --------------------------N -- SCHD RESOLUTION REQUIRED Y -- LOAD STEP TO BE EXECUTED N -- OVERRIDE OF JCL REQUIRED N -- JOB MARKED AS MAINT ONLY N -- MANUAL VERIFICATION REQD N -- JOB SET FOR HOLD IN REQQ Y -- REQUIREMNTS TO BE LISTED Y -- COMP TRIGGERS OTHER JOBS N -- AUTO-GENERATION OF 7 RMS Y -- JOB ELIGIBLE FOR PROMPTS Y -- ERRORS FOR RQMT NOT USED Y -- JOB SET FOR EXEC ON MAIN Y -- ERRORS FOR DSN NOT FOUND N -- JCL TO BE KEPT IN PRRN/Q . . . . . OWNER= *NONE* JCLLIB= *NUMERIC JCLID* ARFSET= *NONE* LAST MAINTENANCE ON 97.296 AT 09:05:08 VIA DBM BY OPERATOR: VZXY2G CLASS=H,MSGCLASS= ,REGION=0000K,PRTY=000,CPUTM=00000,ELAPTM=0004 TAPE1: CALC=000,MANL=000,TAPE2: CALC=000,MANL=000 DONT SCHEDULE BEFORE 97296 AT 0000
The bolded information above represents the items you must verify. 1. 2. 3. The JCL ID field is the number of the library containing the CHAMP production JCL. This number should be 011 for all JCL residing in PWDS1.SPOCH.JCLPAN. (For other JCL IDs, see the Other Commands section in this document.) SYSTEM NAME should correspond to your CA-7 batch id. Your batch id is NOT your customer/system code. (See the PSI System Authority screen (E.7;P;S from the TSO main menu) for the batch ids you have access to.) JOB MARKED AS MAINT ONLY - This should be Y unless it is a dataset posted job. Dataset posted jobs are defined in DB.3.1, should have MAINT=N on DB.1, the datasets PERM=N on DB.6, and POST AT CLOSE TIME = N on DB.6. Dataset triggering is defined on DB.2.6 and MAINT=Y on the DB.1 is allowable, if no other dataset requirements are needed. JOB SET FOR HOLD IN REQQ - This signals whether the job will come into the request queue on hold. For on-demand jobs the value may be Y. For normally scheduled production jobs, it should be N. If the job comes into the request queue on hold, it will have to be manually released. COMP TRIGGERS OTHER JOBS - Does the completion of this job trigger other jobs to run? NOTE: In CA-7, the lead job in a jobstream is typically scheduled to run at a specific time and the successive jobs are triggered. JOB SET FOR EXEC ON MAIN - Should be Y if you intend this job to run in production.
4. 5. 6.
Verify Job Schedule

Next, locate the section of information in the CA-7 Report that looks like this:
. CONSIDER ABNORMAL END IF 0005 IS LT HIGHEST STEP COND-CODE . # OF TIMES LATE = 0000 # OF TIMES RESTARTED = 0000 ------------------------------ SCHEDULES -----------------------------CALENDAR SCAL977A ID=066 ROLL=D INDEX=+000 SCAL=0A DOTM=0404 LEADTM=0004 SUBTM=0400 STARTM=0400 DAILY ID=065 ROLL=D INDEX=+000 SCAL=0A DOTM=0834 LEADTM=0004 SUBTM=0830 STARTM=0830 DAILY ID=070 ROLL=D INDEX=+000 SCAL=7A DOTM=0404 LEADTM=0004 SUBTM=0400 STARTM=0400 ANNUAL NDAY=365 ID=030 ROLL=D INDEX=+000 SCAL=7A DOTM=0404 LEADTM=0004 SUBTM=0400 STARTM=0400 MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=01 MONTH=ALL MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=02 MONTH=ALL MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=03 MONTH=ALL MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=04 MONTH=ALL MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=05 MONTH=ALL
1.
Condition code information is at the job level and should be the same as Control-M. If no condition code checking is done in Control-M, none will appear here in CA-7. If your job requires step-level condition code checking, (e.g. if JS010 finishes with R0008, abend) then JCL changes will be required. Contact your CA-7 Conversion Team representative for more information. 2. Calendar SCAL977A is the 7-day, actual day calendar. Jobs scheduled for this system can run any day of the week regardless of holidays. This calendar should be the same as the one being used in Control-M. For more information on calendars, see the section on calendars in this document (Page 35). 3. ID - schedule ID (SCHID). If the job is scheduled 7 different ways, it should have 7 SCHIDs. There should be at least 1 SCHID for every job. Refer to the SCHID section in this document on page XX to verify the SCHIDs for your jobs. 4. ROLL, INDEX - If the run date falls on a non-processing day, according to the job calendar, this value tells whether the job should be Rolled, Dropped, or Forward. Valid values are R, D or F. If rolled, the index value tells CA-7 how many days to roll. For example, if index = (+003), the job will run 3 days later. If index = (-003) the job will run 3 days early. Note that with a 7-day processing calendar, there are no non-processing days and this field should always be D. F rolls forward to the next process day. For example, a monthly job runs on the first workday of the month is set up with an RDAY of 1 for each month on calendar 5B. However, on certain months, the first day of the month is on the weekend, which is a non-processing day for the 5B calendar. Putting an F in the ROLL field will cause the job to be scheduled the first day of the month that is also a processing day on that calendar 5. SUBTM - the time the job should be submitted to run. This field is important for scheduled jobs or jobs that have specific time requirements or start times in Control-M. See the Control-M schedule or the CMR history for run time information. 6. DOTM - on the average, the time the job finishes. See the CMR report, WSF2 or if the job is verified a scheduled run day, check job statistics in Control-M. 7. SCAL - The schedule calendar being used for this job. The value '0A', indicates it is not scheduled on any days. For this SCHID, the job must be a one-time run or an on-demand run of the job. The conversion process assigned SCHID 0A to any job whose calendar could not be determined.
8. 9.
Job type values include DAILY, MONTHLY, ANNUAL. Job type should match the SCHID. See the CA-7 SCHID section of this document for further information. NDAY - this is a non-run day, in this case the last day of the year. It tells when the job is NOT scheduled rather than when it is. This is normal for 070 on request jobs. No day is specified for the job to be scheduled, it just is not sheduled on day 365.
Verify Job Triggers

Locate the section of information in the CA-7 Report that looks like this:
----------------- TRIGGERED BY JOBS/DATASETS/NETWORKS -----------------JOB=DBAAB5P0 SCHID=037 DOTM=0400 LEADTM=0000 SUBMTM=0400 JOB=DBAMIMIA SCHID=069 DOTM=0400 LEADTM=0000 SUBMTM=0400 --------------------------- TRIGGERED JOBS ---------------------------JOB=DBADAMDB SCHID=065 DOTM=1130 LEADTM=0010 SUBMTM=1130 JOB=DBADAMDB SCHID=066 DOTM=1130 LEADTM=0010 SUBMTM=1130
Compare CA-7 job triggers to dependent jobs and in-conditions in Control-M. Refer to the SCHID section of this document for assistance. 1. 2. 3. 4. Triggered By - The jobs that trigger the listed job. They must be run before your job can start. They are comparable to Control-M in-conditions. If a daily job triggers a weekly job on Wednesday, they will have different SCHIDs. Triggered Jobs - all jobs the listed job triggers. Each of these jobs should have in-conditions of the listed job. They are comparable to dependent jobs in Control-M. QTM can be an alternative to DOTM for triggered jobs. QTM is a set time for a triggered job to wait for requirements before being marked late. This can be used when the scheduled job has a large variance in run time. It can be difficult to identify which triggered jobs go with which SCHID for the listed job. The FSTRUC and FRJOB commands in CA-7 can help. FSTRUC forecasts from a certain job forward, showing all successive jobs and dependencies. FRJOB shows a reverse list from the scheduled job backward. For more information on these commands, see page XX.
If a dependent job or in-condition is not shown in the trigger section of the listing, it may be defined as a predecessor or user requirement in the next section.
Verify Predecessors and Successors

Predecessors and successors are additional job requirements that do not have the same SCHID as the listed job. As the names imply, predecessors are input requirements that must be met before the listed job can run. Successors are jobs that cannot run until the listed job completes.
--------------------------- SUCCESSOR JOBS ---------------------------JOB=WDFNB1D0 SCHID=030 JOB=WDFNCR08 SCHID=070 JOB=WDFNINNQ SCHID=030 JOB=WDFNIN2A SCHID=051
Although this example only shows successors, predecessors would be shown in the same area, with the same information. When verifying, try to match each predecessor and/or successor to one of the schedule variations of the listed job using the SCHIDs
Verify Resource Requirements
The Virtual Resource section shown here is where exclusive resources would be shown. Verify these against the control section of the Control-M schedule.
-------------------- VIRTUAL RESOURCE CONNECTIONS --------------------EXC=EXCLUSIVE-DBAAAM1A SCHID=037 FREE=F EXC=EXCLUSIVE-DBAAAQPD SCHID=037 FREE=F EXC=EXCLUSIVE-DBAAPO1A SCHID=037 FREE=F
Verify Other Requirements

Other requirements can include user requirements, job requirements and data set requirements. The requirements displayed here are comparable to in-conditions in the Control-M schedule. They are requirements that are not necessarily posted by a job. Note that any job which has a requirement of a user daily job will be shown as a user requirement. When the schedules go into production, the user daily requirements will be removed.
---------------- REQUIREMENTS AND NETWORK CONNECTIONS ----------------USR=CPDMDB5-DBAJSM-01 SCHID=070 USR=TCPDMDB5-DBAMB5## SCHID=065 USR=DBAJSM-RELEASE-02 SCHID=066 USR=DBAJSM-RELEASE-03 SCHID=067
Verify Schedule Execution

To verify that your jobs will execute appropriately in CA-7, use the clist TSO PROJ. This clist functions like TSO CMR and displays job run history information. All jobs are defined to CA-7 as of January 1998 and have been running in quiet mode (triggering but not executing) since then. Run history is listed in PRO-J.
Creating and Submitting Schedule Change Requests

If you identify a scheduling problem, complete a scheduling change request and submit it to the EDS-SPO scheduling group. From the TSO main menu, type E.7. On the next screen, type P for PSI (Production Scheduling Interface).
------------------------OPTION ===> p Select Product: 7 11 P J OC X CA-7 CA-11 PSI PRO-J ON-CALL EXIT -
Scheduling Products MENU
--------------------------
Production Job Scheduling Production Job Restart Production Scheduling Interface Production Job Reporting On-Call Support Application
UserID Date Julian Time Terminal
FZFJ91 98/01/05 98.005 07:54 3278
- Return to Previous Menu
Enter END to Exit
----------------------- Production Scheduling Interface ----------------------OPTION ===> 5 01/05/1998 - 07:55 Julian Date: 1998.005 Job Name ===> wdopmr01 System Name ===> wdopop 1 2 3 4 5 L S T X QUEUES ABENDS PRIOR RUN RESOLVE DB MAINTENANCE LOG DISPLAY SYSTEM AUTHORITY TUTORIAL EXIT Queue Activity - Request, Ready, and Active queue information - Production abends, fails, errors, and requeues - Prior Run queue information Data Base Activity - SPARM/ZPARM/Override JCL Resolution - ZPARMs, overrides, resdates, job requests, user rqmts Special Activity Browse CA-7 on-line log Add, delete, and list system ID authority Display information about PSI V4.1 Terminate this session
------------------------ PSI CA-7 Data Base Maintenance ----------------------OPTION ===> 2
Job Name ===> WDOPMR01 1 2 3 4 5 6 USER RQMTS JOB SCHEDULING ZPARM/OVERRIDE ZPARM VALUE RESOLUTION DATE OVERRIDE EDIT -
System Name ===> WDOPOP
Add, delete, and list user requirements. Add, delete, update, and list job requests. Update and list ZPARM and override flags. Add, delete, update, and list ZPARMs. Add, delete, update and list resolution dates. Edit or browse override and reset override flag.
Enter END command to terminate function
--------------------------- Job Scheduling Requests --------------------------OPTION ===> 2 Job Name ===> WDOPMR01 1 2 3 4 ADD JOB CHANGE JOB DELETE JOB LIST REQUESTS System Name ===> WDOPOP
Add a new job. Change an existing job. Delete an existing job. List job requests.
Enter END command to terminate function
The scheduling request is comprised of three screens which request the following information:
------------------------------- Change Request -------------------------------COMMAND ===> Panel 1 of 3 Job Name ===> WDOPMR01 IPC Node ===> ________ System Name ===> WDOPOP Schedule ID ===> ___
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 Lead (run) Time ===> _____ (minutes) ZPARMs or SPARMs Overrides Used ===> _ (Y or N) Condition Code Job Dependence ===> ___ ===> _____ (HH:MM) ===> _ (Y or N)
(highest acceptable cond. code in any job step) ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________
===> ________ ===> ________
Conflicting Jobs ===> ________ ===> ________ Tape Drives Additional Info ===> __
(cartridge) __ (triple density) (maximum in any job step) ===> _______________________________________________________ _______________________________________________________ _______________________________________________________ ===> _______________________________________________________ _______________________________________________________ _______________________________________________________ Enter END to display previous panel
Prose Restart
Press ENTER to save the record
(See the next page for explanatory notes on how to complete the schedule change request screens.)
1. 2. 3.
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. IPC Node - For example, AHIPC1N. Effective Date - Type slashes and use a four-digit year. Day of the month cannot be prior to the current
4. 5. 6. 7. 8.
day. Production JCL Library - Probably PWDS1.SPOCH. JCLPAN. Use the library name where your JCL resides. 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. Mark desired scheduling options with an X. Business means business day and F and L mean first and last. Hence, you may specify first or last business day, first or last actual day, or a specific day of the month. Holiday Roll - Specify if you want the job to roll backward or forward when its normal execution day falls on a holiday. Complete the rest of the information as necessary. Contact the EDS-SPO scheduling group with any questions.
CA-7 Helpful Hints
PF3
Depressing PF3 in CA7 will not return the user to the previously viewed screen. It will return the user to the 'CA7 Primary Option Menu'.
Top Line Command Area

Top line commands can be entered from any CA-7 screen that has a top line command area. Depressing the Home key will place the cursor at the top line command area.
Getting Around in CA-7

The user has two options; screen panels or top line commands. Remember PF3 will not return the previous screen. Making the wrong screen choice will force the user to either press PF3 or enter the screen identifier for the appropriate screen as a top line command. An identifier for each screen is displayed on the bottom of that screen. For example, 'MENU' is displayed at the bottom of the 'CA-7 Function Menu' screen. To return to this screen enter MENU as a top line command. Similarly, to get to the 'CA-7 Data Base Maintenance Menu' enter DB as a top line command, and so on.
CA-7 Function Commands

Functions performed from CA-7 screens can also be executed through top line commands. For example, the CA-7 job definition for job DBASAMPL, can be viewed from the 'CA-7 CPU Job Definition' screen (DB.1) or by entering 'LJOB, JOB=DBASAMPL, LIST=ALL' as a top line command from any screen.
CA-7 Job Time Parameters

CA-7 uses times such as due out time, lead-time and submit time. Converting the Control-M schedules to include times was not an exact science. In fact, the method used was 'eyeball estimation'. The conversion team looked at start and end time recorded for a job over the past 6 months to determine the time parameters to use for CA-7 job schedules. For jobs that have not completed by their due out time or jobs that have not started by their submit time; late messages will go to the operators. They have been trained to call the responsible person for late instructions, no exceptions.
CA-7 Schedule Concepts

Each job can have its own unique scheduling criteria. The scheduling criteria is defined to CA-7 on the scheduling screens and stored in the database with the jobs definition. The scheduling criteria can be based on either dates and times or events. Date-and-time scheduling tells CA-7 when to run a job, for example, the last workday of every month. CA-7 uses the calendar referenced on the scheduling screen to determine the exact processing days. Triggering tells CA-7 to process a job after an event, regardless of when that event takes place. The event can be the completion of another job or the creation of a data set. The first job in a job stream is usually scheduled by date and time, and the rest of the jobs are triggered by the lead job. Schedule Ids are numbers from 1 to 255 that are used to identify scheduling variations. Scheduling variations allow the same job to be scheduled in different ways; at different dates and times, with different triggers, with different requirements, etc. If a job is scheduled 5 different ways in Control-M, it will have 5 different SCHIDs in CA-7. There are standards for what SCHIDs mean. See the section on SCHIDs for more information.
Logging On to CA-7
From ISPF Primary Option Menu, type E.7 to display the Scheduling Products MENU. Enter option 7 to display the CA-7 Primary Option Menu.
------------------------OPTION ===> 7 Select Product: 7 11 P J OC X CA-7 CA-11 PSI PRO-J ON-CALL EXIT Production Job Scheduling Production Job Restart Production Scheduling Interface Production Job Reporting On-Call Support Application UserID Date Julian Time Terminal QZMPM9 97/11/12 97.316 11:33 3278 Scheduling Products MENU --------------------------
- Return to Previous Menu
Enter END to Exit
Enter option 1, to display the CA-7 logon screen.

------------------------OPTION ===> 1 CA-7 PRIMARY OPTION MENU -------------------------USERID PREFIX TIME DATE APPLID QZMPM9 QZMPM9 12:47 97/11/12 CA7
0 1
PF KEYS ONLINE
- Specify CA-7/TSO-ISPF PF keys - CA-7/TSO-ISPF Terminal Session - UID Resource =>
EXIT
- Terminate CA-7/TSO-ISPF Interface
Enter END command to terminate CA-7/TSO-ISPF.
MENU (<top line command area) -----------------------------ELECTRONIC DATA SYSTEMS--------------------------CA-7.023 LOGON ACCEPTED, PRESS ENTER FOR MENU OR ENTER COMMAND
USERID
QZMPM9
TERMINAL NAME : VTM001 VTAM APPLID : CA7 LUNAME : A2YCA702
DATE : 97.316 TIME : 12:47:16 LEVEL : V3L2 (9610)
CCCCCCCCCCC AAAAAAAAAA CCCCCCCCCCC AAAAAAAAAA CCC AAA AAA CCC AAAAAAAAAA 0000 CCC AAAAAAAAAA 0000 CCC AAA AAA CCCCCCCCCCC AAA AAA CCCCCCCCCCC AAA AAA
77777777777 77777777777 7777 7777 7777 7777 7777 7777
COPYRIGHT (C) 1988, 1996 COMPUTER ASSOCIATES INTERNATIONAL, INC.
Press the ENTER key to display the CA-7 Function Menu. Note this is the first screen where a top line command can be entered.
CA-7 Screens and Menu Panels
To access the following screens from anywhere in CA-7, type the screen identifier in the top line command area. For example, to display the screen below, type menu in the top line command area. The screen identifier can be found at the bottom of each screen in the middle.
CA-7 Function Menu Panel (Menu)

(top line command area) ---------------------------- CA-7 FUNCTION MENU -----------------------------FUNCTION ===> DB APA AR DB QM RM UT PS AUTOMATED PERFORMANCE ANALYSIS AUTOMATED RECOVERY FACILITY DATA BASE MAINTENANCE QUEUE MAINTENANCE VIRTUAL RESOURCE MANAGEMENT UTILITIES PERSONAL SCHEDULING
HELP - TUTORIAL
PROGRAM: MNU0 MSG-INDX: 00 -- MENU -97.316 / 12:47:22 MESSAGE: SPECIFY DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE
(You will use the Data Base Maintenance option most often in CA-7.)
CA-7 Data Base Maintenance Menu Panel (DB)

--------------------FUNCTION ===> 2 DATA 1 2 3 4 5 6 CA-7 DATA BASE MAINTENANCE MENU ----------------------
BASE DEFINITION FOR: - CPU JOB - SCHEDULING - JOB PREDECESSOR/SUCCESSOR - WORKLOAD DOCUMENTATION - INPUT/OUTPUT NETWORK - DATA SET
OTHER FUNCTIONS AVAILABLE: 7 - JCL LIBRARY MAINTENANCE 8 - TEXT EDITOR 9 - CLEAR THE TEXT EDITOR ACTIVE AREA ACTIVE AREA NOW CONTAINS 0000 LINES OF TEXT
PROGRAM: SDM0 MSG-INDX: 00 -- DB -97.316 / 12:47:42 MESSAGE: SPECIFY DESIRED OPTION OR ENTER A COMMAND ON THE TOP LINE
CA-7 CPU Job Data Base Definition Screen (DB.1)

This screen shows how a job is defined to CA-7.
------------------------- CA-7 CPU JOB DEFINITION -------------------------FUNCTION: LIST (ADD,DELETE,DD,DELPRRN,FORMAT,LIST,UPD) JOB: WDFNRC40 GENERAL: SYSTEM: WDFNIN JOBNET: OWNER: UID: 0 JCL: ID: 11 MEMBER: WDFNRC40 RELOAD: N EXEC: Y RETAIN-JCL: N LIB: REQUIREMENTS: HOLD: N JCL-OVRD: N USE-OVRD-LIB: N VERIFY: N MAINT: Y SATISFACTION LEAD-TIME: JOB: 0 DSN: 0 ARFSET: EXECUTION: MESSAGES: RESOURCES: MAINID: ALL INSERT-RMS: N COND-CODE: 201 RO: LT DONT SCHEDULE -- BEFORE: 99999 0000 AFTER: 99999 0000 LTERM: REQUIREMENT-LIST: Y PROMPTS: Y ERROR MSGS -- RQMTS NOT USED: Y DSN NOT FOUND: Y REGION: 0 CLOCK-TIME: 0022 CPU-TIME: 00000 CLASS: X PRTY: 000 MSGCLASS: TAPE DRIVES...TYPE1: 000 M 000 C TYPE2: 000 M 000 C -- DB.1 -98.006 / 13:37:40
PROGRAM: SM20 MSG-INDX: 00 MESSAGE: LIST SUCCESSFUL
EXECUTION: COND-CODE: CC-value RO: RO-value reads like this: CA-7 will mark the job as ABENDED IF CC-value RO-value HIGHEST CC OF JOB (i.e. ABEND IF 201 IS LESS THAN HIGHEST CC OF JOB, or ABEND >200) (FOR 0 NE, ABEND IF 0 IS NOT EQUAL TO HIGHEST CC OF JOB, or ABEND < > 0) Step Level Condition Coding should have special parameters in the RO-value.
CA-7 Scheduling Menu Panel (DB.2)

--------------------------FUNCTION ===> DATE/TIME SCHEDULING FOR: 1 - CPU JOB 2 - INPUT NETWORK 3 - OUTPUT NETWORK TRIGGER SCHEDULING FOR: 4 - JOB TRIGGERING OTHER CPU JOB(S) 5 - INPUT NETWORK TRIGGERING CPU JOB(S) 6 - DATA SET TRIGGERING CPU JOB(S) OTHER FUNCTIONS AVAILABLE: 7 - MODIFICATION TO RESOLVED SCHEDULE DATES 8 - BASE CALENDAR MAINTENANCE CA-7 SCHEDULING MENU ----------------------------
PROGRAM: SM70 MSG-INDX: 00 -- DB.2 -97.316 / 12:47:59 MESSAGE: ENTER OPTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE
CA-7 CPU Job Scheduling Screen (DB.2.1)

This screen accesses the scheduling information for a particular job. Use FE to list the information. (FE = Fetch and Edit) Only schedulers are allowed to edit this information.
------------------------- CA-7 CPU JOB SCHEDULING --------------------------FUNCTION: FE (CLEAR,DELETE,EDIT,FE,FETCH,REPL,RESOLV,SAVE) JOB: WDFNRCD1 SCAL: (DEFAULT SCAL ID FOR ADDS)
SCHID-COUNT: 000
PROGRAM: SM71 MSG-INDX: 00 -- DB.2.1 -98.006 / 13:41:26 MESSAGE: ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE
------------------ CA-7 CPU JOB SCHEDULING PARAMETER EDIT -----------------FUNCTION: LIST (ADD,DELETE,EXIT,FORMAT,LIST,REPL,SAVE,SR,SS) JOB: WDFNRCD1 SCHID: 70 SCAL: 7A ROLL: D INDEX: 000 DOTM LDTM SBTM 0340 0002 0338
__ __ __
__ DAILY __ WEEKLY __ MONTHLY WEEK: RDAY:
SUN: JAN: JUL:
MON: FEB: AUG:
TUE:
WED:
THU: MAY: NOV:
FRI: JUN: DEC:
SAT:
MAR: APR: SEP: OCT: DAY-OF-WEEK:
__ X __ ANNUAL __ __ SYMETRIC
DAY: /365 START: SPAN:
DEFAULT SCAL: 7A SCHID-COUNT: 001 98.006 / 13:47:14
PROGRAM: SM72 MSG-INDX: 00 -- DB.2.1-E -MESSAGE: LIST FUNCTION SUCCESSFUL
CA-7 Cpu Job Predecessors Screen (DB.3.2)

------------------------ CA-7 CPU JOB PREDECESSORS ------------------------FUNCTION: LIST (FORMAT,LIST,UPD) PAGE 0001 PRED FOR JOB: WDFNCR96 LIST-SCHID: 36 OPT SCHID LEADTM PRED-JOB NEXT-RUN 36 0000 WDFNCR90 YES
OPTIONS: A=ADD,D=DELETE,U=UPDATE,*=PROCESSED,?=ERROR PROGRAM: SM61 MSG-INDX: 00 -- DB.3.2 -98.005 / 13:06:05 MESSAGE: LIST FUNCTION SUCCESSFUL
CA-7 Cpu Job Schedule (DB.2.7)

This is the list of days the schedule will run. 1 means the job will run on that day and 0 means the job will not run on that day. This is an easy way to interpret the schedule information.
--------------FUNCTION: LIST JOB: WDOPMR01 SCHID: 30 JUL AUG SEP OCT NOV DEC JAN FEB MAR APR MAY JUN CA-7 MODIFICATION TO RESOLVED SCHEDULE DATES (FORMAT,LIST,UPD) NETWORK: 1 2 ....5....0 1001111100 1111100111 1100111110 0011111001 1111001111 1100111110 0111110011 1110011111 1110011111 0011111001 1111100111 1100111110 2 3 ....5....0 1111100111 1100111110 0111110011 1111001111 1001111100 0111110011 1110011111 00111110 0011111001 1111001111 1100111110 0111110011 3 1 1 0 1 1 0 1 0 98.005 / 13:20:36 MODSTAT: ---------------
1 ....5....0 1111001111 1001111100 1111100111 1110011111 0011111001 1111100111 1100111110 0111110011 0111110011 1110011111 1001111100 1111100111
PROGRAM: SM80 MSG-INDX: 00 -- DB.2.7 -MESSAGE: LIST FUNCTION SUCCESSFUL FOR SJ002287
CA-7 Command Guide
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
/DISPLAY,ST=JCL
DESCRIPTION and SYNTAX

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 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 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 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 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 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 Use this command to obtain job flow structure information for a job. The LIST=ALL parameter provides the job trigger relationships and the elapsed
/DISPLAY,PRINT=SCH
CANCEL,JOB=,FORCE= ,REASON=
DEMANDH,JOB=,SCHID =nnn
FJOB,FROM=,TO=,SYS =
FJOB,SPAN=,SYS=
FSTRUC,JOB=,LIST=
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 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 Use this command to obtain a list of jobs in CA-7 that have not successfully completed. LIST,JOB=jobname Use this command to obtain the complete list of all calendars known to CA7. LISTDIR,DSN=*SCAL* Use this command to review the JCL contained in the associated JCL library. LJCL,JOB=jobname 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 Use this command to obtain CA-7 information on the jobs in the ready, request and active queues LQ,JOB=jobname Use this command to obtain CA-7 information on the jobs in the request that are in abend status. LQ,JOB=jobname,ST=ABND Use this command to obtain CA-7 information on the jobs in the request that are in late status. LQ,JOB=jobname,ST=LATE Use this command to review the prose for a job. LPROS,JOB=jobname 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 and provides all data relative to the queue. LPRRN,JOB=jobname,LIST=ALL Use this command to review the run log information for jobs in a specified
LDSN,DSN=,LIST=
LIST,JOB=
LISTDIR,DSN=*SCAL*
LJCL,JOB=
LJOB,JOB=
LQ,JOB=
LQ,JOB=,ST=ABND
LQ,JOB=,ST=LATE
LPROS,JOB= LPRRN,JOB=,LIST=
LRLOG,SPAN=,SYS=
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 Use this command to review the calendar setttings. 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 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 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 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 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. XQM,JOB=jobname,Q=REQ or Q=RDY or Q=ACT
PRINT,SCAL=,YEAR=
REQUEUE,JOB=,Q=
RUNH,JOB=
XQJ,JOB=,Q=
XQM,JOB=,Q=
CA-7 Command Examples
Here is a list of helpful commands, their appropriate syntax, and examples. For more information and options for each command, type HELP in the top line command area in CA-7 and enter the name of the command in the field labeled COMMAND.
LJOB
This command is used to obtain a list of information related to a job. LJOB,JOB=[jobname],LIST=ALL
LJOB,JOB=DBAAAM1A,LIST=SCHD JOB=DBAAAM1A LIST=SCHD JOB NAME ----JCL---ID MEMBER SYSTEM -NAMEUSR MAIN PROSE -ID -ID- DSNBR 000 ALL SCHED DSNBR
DATE=97.316 --NUMBER OFSTP DDS RUNS
PAGE 0001 LAST-RUN DATE/TIME 97316/0400
DBAAAM1A 012 DBAAAM1A CPDMDB5
*NONE* 001321 000 000 0000
------------------------------ SCHEDULES -----------------------------CALENDAR SCAL977A ID=066 ROLL=D INDEX=+000 SCAL=0A DOTM=0404 LEADTM=0004 SUBTM=0400 STARTM=0400 DAILY ID=065 ROLL=D INDEX=+000 SCAL=0A DOTM=0834 LEADTM=0004 SUBTM=0830 STARTM=0830 DAILY ID=070 ROLL=D INDEX=+000 SCAL=7A DOTM=0404 LEADTM=0004 SUBTM=0400 STARTM=0400 ANNUAL NDAY=365 ID=030 ROLL=D INDEX=+000 SCAL=7A DOTM=0404 LEADTM=0004 SUBTM=0400 STARTM=0400 MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=01 MONTH=ALL MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=02 MONTH=ALL MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=03 MONTH=ALL MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=04 MONTH=ALL MONTHLY DAY=SUN,TUE,WED,THU,FRI,SAT WEEK=05 MONTH=ALL ID=067 ROLL=D INDEX=+000 SCAL=0A DOTM=0404 LEADTM=0004 SUBTM=0400 STARTM=0400 DAILY SLIA-00 REQUEST COMPLETED AT 16:32:28 ON 97.321
LSCHD
This command lists schedule data and month-by-month schedule day calendars for each SCHID. It is useful when a picture of a calendar with scheduled days is needed. For more information and options for this command, type HELP in the top line command area in CA-7 and enter LSCHD in the field labeled COMMAND. LSCHD,LIST=CALS,JOB=[jobname] PF8 down to the bottom of the displayed information to see a screen similar to this one:
LSCHD,LIST=CALS,JOB=DBAAAM1A LIST=CALS JOB=DBAAAM1A
DATE=97.316
PAGE 0004
******************************************************************************* ** CA-7 SCHEDULE CALENDAR FOR JOB=DBAAAM1A ** ** DATE 97316 ** ** BASE CALENDAR SCAL977A (DEFAULT) ** ******************************************************************************* ** ** ** MONTH 01 JAN ** ** ** ** SUN MON TUE WED THU FRI SAT ** ** ** ** 01 02 03 04 ** ** 05 07 08 09 10 11 ** ** 12 14 15 16 17 18 ** ** 19 21 22 23 24 25 ** ** 26 28 29 30 31 ** ** ** *******************************************************************************
/DISPLAY,ST=JCL
Use this command to display a listing of JCL libraries and their assigned index. When JCL library ID is displayed, this command can be used to find out what the ID number equates to.
/DISPLAY,ST=JCL *** JCL DISPLAY *** DATASET NAME SYS2.CA7.JCLPDS PTASS.PAXCH.JCLPDS PTASS.USRCH.JCLPDS PAH90.IRGCH.JCLPDS PDSCN.SECCM.JCL PPRAD.PAXLB.JCLPDS PNADS.DMTCH.JCLPDS PTASS.CHMCH.JCLPDS PACMD.CTMCH.JCLPDS PNIGP.NGPCH.JCLPDS PTGCC.TXCCH.JCLPDS PTASS.SIMLB.DYNJCL PTASS.USRCH.JCLPDS PEIBS.BSSLB.DYNJCL PEIBS.BSSCM.PROD.JCL PWDFN.OQALB.DYNJCL PWDS1.SPOCH.JCLPAN SYS2.CA7.JCLLIB PSYS3.WAZMA.ZOOMJCL SYS2.CA7.HELP PAGE 0001 VOLSER LTERM NM7LBP NM7LBA NMP008 NMP019 NM7ACA NMP011 NMP008 NM7LBA NMPS02 NMDPDB NMP025 NMP010 NMP008 NMP010 NMDMZD NMDPDB NMP024 NM7LBP NM7LBC NM7LBP MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER MASTER
INDEX ALT 000 001 002 003 004 006 008 009 010 012 013 102 202 103 005 104 011 200 253 255 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A 102 N/A 103 N/A 104 N/A N/A N/A
DSORG PDS PDS PDS PDS PDS PDS PDS PDS PDS PDS PDS PDS PDS PDS PDS PDS PANV PDS PDS PDS
The highlighted data set shown on this display (011) is the production library where CA-7 will pull the JCL from. The DYNAMIC JCL library is the library where JCL that is created by a job in CA-7 is triggered to run. CA-7 handles this with an ALTERNATE LIBRARY (104) definition of the MASTER LIBRARY. (011) JOB A creates JCL for JOB B Scenario with the Schedule for JOB B defined as being triggered by JOB A: 1) JCL for JOB B must not exist in any CA7 defined JCL library (no member or an empty member in the DYNJCL LIBRARY) 2) JOB A is scheduled: 3) JOB A runs creating the JCL for JOB B in the DYNJCL library member. (the last step of JOB B is WAAPINIT on the DYNJCL member emptying it back out, SEE the SYS4.CA7SPO(WAAPINIT) member) 4) JOB B is triggered, pulling the JCL from the ALTERNATE LIBRARY defined since no JCL exists in the MASTER LIBRARY and placing the JCL into the CA7 Trailer Queue for execution. 5) JOB B completes emptying out the member in the DYNJCL library. 6) READY FOR THE NEXT RUN Here is the list of jobs that will need this conversion: JOB A JOB B JOB A - JOB B ======== ========== ========= ========= MDFNINPG - MDFNINPH WDFNINPG - WDFNINPG WDFNIN1Q - WDFNIN1R WDFNIN31 - WDFNIN3F WDFNIN38 - WDFNIN39 WDFNLO76 - WDFNLO76 WDFNRCD3 - WDFNRCD4 WDOPCC01 - WDOPCC02 JOB A JOB B ========= ========= MDFNIN1Q - MDFNIN1R WDFNIN34 - WDFNIN35 MDFNRCD3 - MDFNRCD4 WDOPCC13 - WDOPCC14
FSTRUC
Displays a forecast of a jobstream beginning with a specified job, showing all succeeding jobs. For best results, use the first date-time scheduled job in a jobstream. FSTRUC,JOB=[jobname],TYPE=ALL,LIST=ALL,TRIG=JD,SCHID=[schedule id] Page down (PF8) to view the following information:
FSTRUC,JOB=WDS144WA,TYPE=ALL,TRIG=JD,LIST=ALL,SCHID=31 FSTRUC DATE 01-06-98 NETWORK STRUCTURE FOR CA-7 JOBS START TIME : 01-06-98 AT 1438 HRS LEV# JOB NAME --- WDS144WA............ 001 WDS144WF.......... 001 WDS144WJ.......... 002 WDS144WS........ SYS WDS1QA WDS1QA WDS1QA WDS1QA START DTTM 98006/1438 98006/1650 98006/1659 98006/1650 PAGE 0001
END DTTM TRIGGERING JOB/DSN/SID 98006/1448 :031 98006/1700 WDS144WA :031 98006/1700 WDS144WA :031 98006/1700 WDS144WJ :031
SFC1-00 REQUEST COMPLETED AT 14:38:30 ON 98.006
FRJOB
Displays a reverse jobflow beginning with the specified job. Tells how a job enters the jobstream. FRJOB,JOB=[jobname],TYPE=ALL,LIST=ALL,TRIG=JD,SCHID=[schedule id]
FRJOB,JOB=WDS144WS,TYPE=ALL,LIST=ALL,TRIG=DJ,SCHID=31 FRJOB REVERSE STRUCTURE FOR CA-7 JOBS HDR LEV# JOB NAME --- WDS144WS............ -001 WDS144WJ.......... **** -002 WDS144WA........ SYSTEM WDS1QA WDS1QA WDS1QA
DATE 01-06-98
PAGE 0001
SID TYPE TRIGGERS /DSNBR 031 031 JOB WDS144WS 031 JOB WDS144WJ
/SCHEDULED :**SCHD**
SFC1-00 REQUEST COMPLETED AT 14:42:10 ON 98.006
Note that the jobs are listed in backwards order with the topmost job being the last job in the jobstream.
CA-7 SCHIDs
When requesting a new job be added to CA-7 schedules, the requester must supply the SCHID to the scheduling group. They will not automatically assign a SCHID. Each job should be classified as one of the following: 1) Day of the Week 2) Daily 3) Day of the Month 4) Monthly 5) On Request The following definitions should be used to classify a job: Day of the Week A Day of the Week job is a job that is scheduled to run 1 day a week (every week) and there are no days-of-the-month. Monday jobs Tuesday jobs Wednesday jobs Thursday jobs Friday jobs Saturday jobs Sunday jobs Target SCHID SCHID=031 SCHID=032 SCHID=033 SCHID=034 SCHID=035 SCHID=036 SCHID=037 1st Duplicate SCHID=081 SCHID=082 SCHID=083 SCHID=084 SCHID=085 SCHID=086 SCHID=087 Next Duplicate next available next available next available next available next available next available next available
Duplicate jobs use SCHID 081 through 099 then SCHID 213 through 252. The first duplicate is the Target SCHID + 50, for example: A second Wednesday job is assigned SCHID 83. A third Wednesday job is assigned SCHID 84. Daily A Daily job is a job that is scheduled to run 2 or more days per week. The following definitions clarify this using CONTROL-M terms (where xx is a 2-digit day-of-the-month): A job is scheduled to run on all days-of-the-week (WDAYS) or all days-of-the-month (DAYS) A job has 2 or more days-of-the-week AND one of the following is true: * there are no days-of-the-month * there is an "OR" operator between days-of-the-week and days-of-the-month data * there is a least one minus sign ("-") in days-of-the-month A job has no days-of-the-week and no days-of-the-month and has either a DCAL or a WCAL calendar Daily jobs Target SCHID SCHID=030 1st Duplicate SCHID=040 Next Duplicate next available
Duplicate jobs use SCHID 040 through 049 then SCHID 213 through 252. For example: A second Daily job is assigned SCHID 40. A third Daily job is assigned SCHID 41.
Day of the Month A Day of the Month job is a job that is scheduled to run 1 day a month (every month). The following definitions clarify this using CONTROL-M terms (where xx is a 2-digit day-of-themonth): A job is scheduled to run with 1 day-of-the-month (DAYS) value in the format xx A job is scheduled to run with 1 day-of-the-month value in the format Dxx AND the calendar is ALLDAYS 1st day 2nd day 3rd day ..... 30th day 31st day Target SCHID SCHID=101 SCHID=102 SCHID=103 SCHID=130 SCHID=131 1st Duplicate SCHID=213 SCHID=213 SCHID=213 SCHID=213 SCHID=213 Next Duplicate next available next available next available next available next available
Duplicate jobs use SCHID 213 through 252 A second 25th Day job is assigned SCHID 213. A third 25th Day job is assigned SCHID 214. Monthly A Monthly job is a job that is scheduled less frequently than Day of the Week and Daily jobs. The following definitions clarify this using CONTROL-M terms: A job is scheduled to run using days-of-the-month (DAYS) and/or days-of-the-week (WDAYS) information that cannot be defined as Day of the Week, Daily, or Day of the Month. A job with no months information, but with DDMM or MMDD dates Monthly jobs Target SCHID SCHID=051 1st Duplicate SCHID=061 Next Duplicate next available
Duplicate jobs use SCHID 061 through 069 then SCHID 213 through 252. For example: A second Monthly job is assigned SCHID 61. A third Daily job is assigned SCHID 62. On Request An On Request job is a job with no months and no DDMM or MMDD dates. An On Request job is also a job that cannot be defined as: Day of the Week Daily Day of the Month, or Monthly Target SCHID SCHID=070 1st Duplicate SCHID=071 Next Duplicate next available
On Request jobs
Duplicate jobs use SCHID 071 through 079 then SCHID 213 through 252. For example: A second On Request job is assigned SCHID 71. A third On Request job is assigned SCHID 72.
CA-7 Calendars
If a job in Control-M could not be matched to a calendar in CA-7 (on demand jobs, for example), the conversion program assigned a calendar of SCALyy0A, which has no processing days. RELATIVE DAY CALENDARS are set with SCHONLY=N which means that all days on the calendar are used in the determination of when the job should run from the beginning or end of the month, regardless of the 0's and 1's on the calendar in DB.2.8 screen. If the RDAY your job is set to run on falls on a "0" on the calendar, then the ROLL parameter (DB.2.1 FE screen) action is used, (i.e. the default is D for DROP, N is DO NOT ROLL, F is forward, B is backward the number of INDEX days). PROCESSING DAY CALENDARS are set with SCHONLY=Y which means that only the days marked with a "1" in the calendar DB.2.8 screen are days in which the job is able to run using the DAILY, WEEKLY, MONTHLY, RDAY (only count days with "1"'s), and ANNUAL settings on the (DB.2.1 FE screen).
Description No Run Days Description 5-day calendar 6-day calendar 7-day calendar Description 5-day calendar 6-day calendar 7-day calendar
Relative Day SCALyy0A Relative Day SCALyy5A SCALyy6A SCALyy7A Relative Day (Includes GM Holidays) SCALyy5D SCALyy6D SCALyy7D
Processing Day SCALyy0B Processing Day SCALyy5B SCALyy6B SCALyy7B Processing Day (Includes GM Holidays) SCALyy5E SCALyy6E SCALyy7E
Control-M to CA-7 Calendar Conversion Cross-Comparison Table

Description (CTMCALGM) (CTMCAL5D) (CTMCAL5H) (CTMCAL6D) (CTMCAL6H) (CTMCAL7D) (CTMCAL7H) (CTMCAL7T) (CT2CAL7H) (EVERY21D) (TAXCNECT) (WDDBDBRY) (WDDBDBRZ) (WKLSTYES) (CTMCAL03) (CTMCAL5T) (CTMCAL6M) (CTMCARS ) (CT2CAL5H) (CT2CAL6H) (EVERY14D) (EVROFRDY) (FSTDAYCN) (INVCAL5A) (INVCAL5B) (LSTDAYCN) (LSTDAYCS) (NOVDEC5 ) (TESTCAL ) (WK2STYES) (TESTCAL1) (TESTCAL2) Relative Day SCALyyAN SCALyyBN SCALyyCN CALyyDN SCALyyEN SCALyyFN SCALyyGN SCALyyHN SCALyyIN SCALyyJN SCALyyKN SCALyyLN SCALyyMN SCALyyNN SCALyyON SCALyyPN SCALyyQN SCALyyRN SCALyySN SCALyyTN SCALyyUN SCALyyVN SCALyyWN SCALyyXN SCALyyYN SCALyyZN SCALyy1N SCALyy2N SCALyy3N SCALyy4N SCALyy5N SCALyy6N Processing Day SCALyyAY SCALyyBY SCALyyCY SCALyyDY SCALyyEY SCALyyFY SCALyyGY SCALyyHY SCALyyIY SCALyyJY SCALyyKY SCALyyLY SCALyyMY SCALyyNY SCALyyOY SCALyyPY SCALyyQY SCALyyRY SCALyySY SCALyyTY SCALyyUY SCALyyVY SCALyyWY SCALyyYY SCALyyXY SCALyyZY SCALyy1Y SCALyy2Y SCALyy3Y SCALyy4Y SCALyy5Y SCALyy6Y
Fix CA-7 abend

Within CA-7, type QM.1 (top line command) to enter the Queue Maintenance subsystem. You are presented with the following screen:
------------FUNCTION ===> CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS PROMPT (LEAVE BLANK EXCEPT TO TRANSFER) --------
DESIRED JOB(S) => <jobname> LIST SEQUENCE => J CA-7 QUEUE ID => REQ DISPLAY RQMTS RQMT CRITERIA FILL C F H J P Q => YES => ANY
SPECIFIC, GENERIC OR CA-7# (DEFAULT ALL) J=JOBNAME, N=JOB#, E=QUEUE ENTRY (DEFAULT) RDY OR ACT (DEFAULT IS REQ) (DISPLAY REQUIREMENT INFORMATION) (ALL,ANY,JOB,INT,EXT,USR,NWK,SUB,HLD,JCLO, VER,SKEL,REST,BINT)
FUNCTION => (OPTIONAL) = CANCEL R = RELEASE FROM HOLD STATUS = GO TO RESTART SCREEN S = SATISFY SUBMIT TIME RQMT = PLACE IN HOLD U = GO TO ATTRIBUTE UPDATE SCREEN = REVERSE JCL OVERRIDE RQMT V = REVERSE VERIFY RQMT STATUS = RESPOND TO PROMPTING X = GO TO JOB PREDECESSOR SCREEN = REQUEUE FOR A RESTART E = FETCH QUEUED JCL AND EDIT -- QM.1 -98.006 / 13:22:25
PROGRAM: QM2F MSG-INDX: 13 MESSAGE: NO SUCH JOB(S) FOUND
In order to edit the JCL to fix the abend, it is necessary for the job to be in the Request (REQ) queue. To check and see if the job is in the Request queue, type in the job name at the DESIRED JOB(S) => line and press the <Enter> key. If the job appears on the next screen, it is already in the Request (REQ) queue and JCL modifications are possible by placing an E (EDIT QJCL) in the F column to the left of the jobname.
-------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS (RQMTS) --------F-JOBNAME---J--I--E--U--N-SHJV E <jobname> . . . . . *RST JOB: * SEQ: JOBNAME QUEUE: REQ LIST: ANY FUNCTIONS: C=CANCEL F=RESTART H=HOLD J=JCLOVRD P=RSVP Q=REQUEUE R=RELEASE BE CAREFUL ===> S=SUBTM OFF U=UPDATE V=VERIFY X=RQMT POST E=EDIT QJCL PROGRAM: QM20 MSG-INDX: 00 -- QM.1-M -97.351 / 15:31:49 MESSAGE: ENTER FUNCTION IN 'F' FIELD OR ENTER A COMMAND ON THE TOP LINE
It should be noted that all JCL modifications through this screen are only temporary changes and will not be reflected in the next run of the job if Retain JCL parameter is set to N on the DB.1 screen. If the job does not appear in the Request queue, then it is most likely in the Ready (RDY) queue. Type in the job name at the DESIRED JOB(S) => line on XQM screen and change the CA-7 QUEUE ID => to RDY to view the job in the Ready queue and press the <Enter> key. If the job appears, the next step which is involved is the requeuing of the job which places it back in the Request queue. To requeue the job, type a Q (REQUEUE) in the F column to the left of the jobname.
-------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS (RQMTS) -------------F-JOBNAME---J--I--E--U--N-SHJV Q <jobname> . . . . . *RST JOB: * SEQ: JOBNAME QUEUE: RDY LIST: ANY FUNCTIONS: C=CANCEL F=RESTART H=HOLD J=JCLOVRD P=RSVP Q=REQUEUE R=RELEASE S=SUBTM OFF U=UPDATE V=VERIFY X=RQMT POST E=EDIT QJCL -97.351 / 15:31:49 ENTER A COMMAND ON THE TOP LINE
PROGRAM: QM20 MSG-INDX: 00 -- QM.1-M MESSAGE: ENTER FUNCTION IN 'F' FIELD OR
NOTE: IF THE JOB IS IN SKELETON STATUS IT MUST BE CANCELED WITH FORCE=YES (BY A SCHEDULER OR BATCH OPERATIONS). IF THE JCL HAS AN ERROR, IT MUST BE CORRECTED BEFORE THE JOB IS BROUGHT BACK INTO THE REQUEST QUEUE EITHER IN PSI OVERRIDE OR CHAMP PRODUCTION CHANGE. Shortcut to XQM is XQJ,JOB=jobname to get to the queue where the job resides.
To cancel the job, select the C (CANCEL) option in the F column to the left of the jobname. To restart the job, select the F (RESTART) option in the F column to the left of the jobname.
-------------- CA-7 QUEUE MAINTENANCE - CPU JOBS STATUS (RQMTS) -------------F-JOBNAME---J--I--E--U--N-SHJV F <jobname> . . . . . *RST JOB: * SEQ: JOBNAME QUEUE: RDY LIST: ANY FUNCTIONS: C=CANCEL F=RESTART H=HOLD J=JCLOVRD P=RSVP Q=REQUEUE R=RELEASE S=SUBTM OFF U=UPDATE V=VERIFY X=RQMT POST E=EDIT QJCL -97.351 / 15:31:49 ENTER A COMMAND ON THE TOP LINE
PROGRAM: QM20 MSG-INDX: 00 -- QM.1-M MESSAGE: ENTER FUNCTION IN 'F' FIELD OR
Once the job is in restart status, one of the following options should be chosen:
------------ CA-7 QUEUE MAINTENANCE - CPU JOB IN RESTART STATUS JOB: <jobname> CODE: JCLERR LAST-STEP: MCNT: 002 CA-7#: <job#> JES#: <jes#> NODE-NAME: LOCAL REASON: FIX ABEND OF JOB <jobname>. -- X -- RESUBMIT FOR PRODUCTION ---- FORCE COMPLETE -- CA-11 RESTART/RERUN START: CC: BYPGDG: CMT STATUS: JOB NOT FOUND PSEUDO: END: USAGE: IN CMT
LRTCD: = 0
---
-- SET PARM DATA FOR RMS AND RESUBMIT PARM: -- DO NOT INSERT RMS PROC BUT RESUBMIT
PROGRAM: QM50 MSG-INDX: 00 -- QM.4-X -97.351 / 15:36:18 MESSAGE: 'X' THE DESIRED FUNCTION OR ENTER A COMMAND ON THE TOP LINE
To restart the job, place an X next to the RESUBMIT FOR PRODUCTION option. Note that a reason is required before CA-7 will restart the job. To force complete the job, place an X next to the FORCE COMPLETE option. Important: By forcing complete a job, any successor jobs in the jobstream will execute!
Dynamic JCL Creation Procedure for CA7

In the current Control-M scheduling environment, there is a USERDAILY job that runs creating all of the JCL for that particular days run. This JCL resides in a PDS named Pcust.CTMSC.Dyymmdd.EXECJCL. Each member is a job that could be scheduled that day. Control-M pulls all the JCL from that dataset when the time comes for that job to run. Some JCL is dynamically created each day by another batch job. In this scenario, one member of the execjcl dataset is writing to another member of that same dataset, and usually the job that is creating the new jcl is also an in-condition to the job being created. The first job runs creating fresh JCL for the dynamically created job, then the dynamically created job runs upon completion of the job that created its JCL. Beginning February 23rd, CA7 will be the scheduling product used by the entire SPO account. The CA7 product does not have a USERDAILY job, nor does it have an execjcl dataset. CA7 pulls all JCL from its master library, which is the CHAMP production library. This poses a problem for any job whose JCL is created dynamically. The only way that JCL gets into CHAMPs JCLPAN library is to be promoted from status 2 all the way to production status 1, so it is not possible to dynamically create JCL in the CHAMP production library. An alternative library has been designated that will contain the dynamically created JCL when CA7 is implemented. Jobs that currently dynamically create JCL by writing to the execjcl dataset can in the future create JCL by writing to this new alternate JCL library. The library is PWDFN.OQALB.DYNJCL. It is a PDS with members named for the jobs that are dynamically created. In the Control-M environment, a CHAMP member has to exist in order for Control-M to create a PDS member in the execjcl dataset; this means that JCL that is dynamically created each day still has a production status 1 member in CHAMP, even though the actual JCL that executed probably looks nothing like it. In the CA7 environment, any job that is meant to run out of the alternate library cannot exist in the master library. Only if the member does not exist in the master library will CA7 look to the alternate library. This is where the dynamically created JCL needs to reside. It will never get executed if there is a member in the CHAMP production library. This means that these dynamically created jobs will have to be purged from the production CHAMP JCL library. It is recommended that the job be archived first, then purged, then a new member with the same name created with the archived JCL copied into it. This new member will never be promoted to the production JCLPAN library, and this status 2 member will prevent someone from creating a new job in CHAMP with this same jobname. The alternate JCL library has already been defined to CA7, and members in that PDS can now be created to prepare for the conversion February 23rd. There are no other flags or switches to set in CA7, and the relationship between CA7 and the master and alternate libraries has already been established. If you wish to view the relationship between the master and alternate libraries, go to ISPF option e.7(CA7), option 7(CA7), option 1(Online), hit <enter>, hit <home> to go to the top line, enter the following command /display,st=JCL. A portion of the output is displayed below. *** JCL DISPLAY *** DATASET NAME PAGE 0001 INDEX ALT DSORG VOLSER LTERM
PEIBS.BSSCM.PROD.JCL 005 103 PDS NMDMZD MASTER PWDFN.OQALB.DYNJCL 104 N/A PDS NMDPDB MASTER PWDS1.SPOCH.JCLPAN 011 104 PANV NMP024 MASTER
The JCLPAN library has INDEX (referred to as JCLID # in other places) 011. The next column over is the ALTernate JCLID column. For the JCLPAN library, the alternate is 104, which is the index number to the DYNJCL library, demonstrating that the DYNJCL is an alternate library for any job with JCLID 011, which all jobs at SPO should have. The last thing to do is to make whatever changes are necessary so that jobs dynamically write JCL to the alternate library instead of the execjcl dataset. For example, in Financial job WDFNIN34, all that was necessary was to change the DD names from: //OUTSAV DD DSN=PWDFN.CTMSC.D%%ODATE.EXECJCL(WDFNIN35), to: //OUTSAV DD DSN=PWDFN.OQALB.DYNJCL(WDFNIN35), The JCL for the dynamically created job will be backed up by the creating job in a GDG with 5 generations so that 5 days runs of this job will be kept, similar to the way that 4 days worth of execjcl is kept. Also, the last step of the job that is dynamically created will have to be a WAAPINIT step to initialize the PDS member in the alternate library (the member where the JCL will be written to) to an empty member. See below: //JS010 EXEC PGM=WAAPINIT,COND=(0,NE) //SYSUTD DD DSN=PWDFN.OQALB.DYNJCL(WDFNIN35),DISP=SHR This needs to be done each time the job runs so that the member is empty when you begin writing to it in the next run of the creating job.
CA7 OVERRIDE Library Process

Purpose: The OVERRIDE EDIT function lets a user maintain the account-level JCL overrides. JCL overrides are full replacements for production JCL. These overrides are used as a temporary set of JCL. Overrides are used to correct errors in the job stream or to accommodate a temporary change in the job's processing requirements. To edit an override PDS member, the user must have WRITE authority to the PDS that contains the member. Please read the entire procedure before using. 1. 2. Log onto PSI {E.7.P} You will arrive at the Production Scheduling Interface Screen. a) At JOBNAME, enter a JOBNAME or a * (wildcard) or a combination of each. b) Enter your Customer code / SystemID at the SYSTEM NAME. c) Enter option 5 for DB Maintenance. You will arrive at the PSI CA7 Data Base Maintenance Screen. Your JOBNAME and SYSTEM NAME should carry over. a) Enter option 6 for the Override Edit Screen. You will arrive at the Override Selection List. a) Enter an 'S' in front of your SYSTEM NAME, which should be associated with an OVERRIDE LIBRARY dataset. You will arrive at the List Override Member Screen. 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. CAUTION: Members in the OVERRIDE LIBRARY dataset are NOT automatically deleted by CA-7 for any reason. The member you find in the OVERRIDE LIBRARY dataset may NOT be the current production version of the JOB (jcl) you want to execute from the OVERRIDE LIBRARY dataset. If no members are displayed, then do: 5A else do: 5B a) Enter 'A xxxxxxxx' at the command line, where: A indicates ADD blank indicates separator xxxxxxxx is the jobname desired and IS known to CA-7. a) Select the member you wish to edit by placing the line command 'E' in front of the member you wish to edit. You will arrive at the Edit Screen. Your normal EDIT rules apply. a) Insert a line at the top of the member. b) Type in the inserted line: '//*in=mm/dd/yyyy,out=mm/dd/yyyy,SE=your name' where the 1st mm/dd/yyyy is the date to begin using this JCL the 2nd mm/dd/yyyy is the date to end using this JCL NOTE: Don't forget that CA-7 days are from midnight to midnight, NOT 08:00 a.m. to 08:00 a.m. a) At the command line, type in either pancopy or copy, to add the JCL after the '//*IN' statement. (i) 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. a) Continue to edit the member as appropriate. 'JEM' the Override Member when edit is complete.
3. 4. 5.
2.
2. 3. 4.
5.
6.
Save by touching 'PF3'. The 'Override Member Added' message will appear on the List Override Screen. Go to the CA7 Job Screen {ISPF E.7.7;1 then enter after the logon screen, then DB.1 from the CA-7 FUNCTION screen} a) Use the LIST function on the JOBNAME ADDed to the OVERRIDE LIBRARY. b) Verify that the 'JOBNET' Field has an 'OX' to indicate that the JOBNAME Job is coming from the OVERRIDE LIBRARY. c) Exit the DB.1 screen when the LIST function is complete. As long as the current date is within the IN and OUT dates as specified in 6.B above, the JCL will continue to be run from the OVERRIDE LIBRARY. As soon as the current date falls outside of the IN and OUT dates, this OVERRIDE will no longer be effective, no matter what the JOBNET Field on CA-7 screen DB.1 LIST specifies. When the IN and OUT dates are no longer in effect, 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 also resets the 'OX' field on the CA-7 DB.1 screen.
CA-7 Verification Checklist

Job: Jobflow: Verifier: Validate against the CA7LJOB report. -----------------------------------------------------------------------------------PASS FAIL N/A Is the Job Name and the JCL Member name the sameas your jobname in Control M?: Comments: Is the JCL ID correct?: Comments:
----------------------------- JOB INFORMATION -------------------------------------PASS FAIL N/A Are Ys and Ns correct?: Comments: Does the condition code match Control-M?: Comments:
-------------------------------- SCHEDULES ----------------------------------------PASS FAIL N/A Do days and times and calendar match Control-M?: Comments:
---------------------------------- PROSE ------------------------------------------PASS FAIL N/A Does description match Control-M?: Comments:
----------------------------- SUCCESSOR JOBS --------------------------------------PASS FAIL N/A Are all dependent jobs listed? Comments:
--------------------- REQUIREMENTS AND NETWORK CONNECTIONS ------------------------PASS FAIL N/A Does list match Control-M in-conditions?: Comments:
--------------------- TRIGGERED BY JOBS/DATASETS/NETWORKS -------------------------PASS FAIL N/A Is triggering data set or job correct?: Comments:
----------------------------- TRIGGERED JOBS --------------------------------------PASS FAIL N/A Are all triggered jobs listed?: If not here, are they demanded in by the ARFSET?: Are they unscheduled jobs?: Comments:
-------------------- Function FE from CA-7 Screen AR.3 ----------------------------PASS FAIL N/A Do ARFALERTs match Control-M SHOUTs?: Do DEMANDs match Control-M FORCEJOBs?: Comments:
-----------------------------------------------------------------------------------PASS FAIL N/A Do JCL #SCC statements match Control-M DO NOTOKsfor step level condition codes?: Comments:
-----------------------------------------------------------------------------------PASS FAIL N/A Do scheduled jobs appear in PRO-J at the correct time and on the correct day(s)?: Comments:
---------------------------- Overall Pass/Fail ------------------------------------PASS FAIL Did this job pass all categories?: COMPLETED Date If this job failed any categoried, create a request forall items that failed. Once the request in complete, re-evaluate the failed items Initials_________________ Date__________________ Comments:

CA7FIN2

Uploaded by

Copyright:

Available Formats

CA7FIN2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CA7FIN2

Uploaded by

Copyright:

Available Formats

Table of Contents

CA-7 VERIFICATION CHECKLIST...........................................................................................................48

Date Revised 02/19/98 1 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

CA-7 Verification Process Overview

Date Revised 02/19/98 2 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Gathering Current Control-M Schedule Information

JFMAMJJASOND YYYYYYYYYYYY YYYYYYYYYYYY

YYYYY YYYYY Y YYYYY Y Y Y Y

YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY YYYYYYYYYYYY

Date Revised 02/19/98 3 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

SHOW JOB DOCUMENTATION AUTO-SAVE DOCUMENTATION

USE THE COMMAND "SHPF" TO SEE PFK ASSIGNMENT

Date Revised 02/19/98 4 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Date Revised 02/19/98 5 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

TSO CMR/TSO PRO-J Job History

ACTIVE FOR NODE AHIPC1N

Date Revised 02/19/98 6 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Pro-J Summary Report Example

Pro-J Detail Report Example

Date Revised 02/19/98 7 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

CA-7 Job Schedule Information Report

Date Revised 02/19/98 8 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Verify Job Definition

USR MAIN PROSE -ID -ID- DSNBR 000 ALL

--NUMBER OFSTP DDS RUNS

LAST-RUN DATE/TIME 97316/0400

WDFNWXYZ 011 WDFNWXYZ

*NONE* 001321 000 000 0000

Date Revised 02/19/98 9 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Verify Job Schedule

Date Revised 02/19/98 10 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Date Revised 02/19/98 11 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Verify Job Triggers

Date Revised 02/19/98 12 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Verify Predecessors and Successors

Date Revised 02/19/98 13 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Verify Resource Requirements

Verify Other Requirements

Date Revised 02/19/98 14 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Verify Schedule Execution

Date Revised 02/19/98 15 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Creating and Submitting Schedule Change Requests

Scheduling Products MENU

UserID Date Julian Time Terminal

FZFJ91 98/01/05 98.005 07:54 3278

- Return to Previous Menu

Enter END to Exit

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

Date Revised 02/19/98 16 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

System Name ===> WDOPOP

Enter END command to terminate function

Enter END command to terminate function

Date Revised 02/19/98 17 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Effective Date ===> __________ (MM/DD/YYYY) ===> ____________________________________________

Production JCL Library

===> ________ ===> ________

Press ENTER to save the record

Date Revised 02/19/98 18 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

Date Revised 02/19/98 19 /var/www/apps/conversion/current/tmp/scratch3622/103865124.doc

CA-7 Helpful Hints

NONE 001321 000 000 0000

Effective Date ===> (MM/DD/YYYY) ===> __________________________________

===> ===>

DAILY WEEKLY __ MONTHLY WEEK: RDAY:

NONE 001321 000 000 0000