Ca7 Operational

ONLINE SYSTEM In order to be able to access the CA-7 online system, terminals must first be defined to CA-7 via the Initialization deck. For security reasons, terminals may be defined individually by address, or you may opt to globally allocate a specific number of terminals from your VTAM pool (virtual terminal support). When defining specific terminals, the security modules give you the ability to restrict who can log onto which terminals and which functions can be done on each. Because individual terminal addresses are not defined under the virtual method, the security modules can only limit the functions on an operator id lever. No support is available to limit functions to specific terminals. LOG ON/LOG OFF Use the /LOGON command to initiate a CA-7 terminal session. Information supplied on the /LOGON command is used to validate user access to CA-7. When CA-7 is accessed via the TPX menu, the /LOGON command is automatically issued using the correct syntax (/LOGON userid,password). Use the /LOGOFF command to inform CA-7 that a terminal is going inactive. Whenever a terminal is to be inactive for some time, it is best to issue a /LOGOFF. This does not return to VTAM. It causes CA-7 to return the terminal to the LOGON screen. In order to return the terminal to VTAM, the /CLOSE command must be issued. This will disconnect the issuing terminal from CA-7.

TERMINAL OPERATIONS Since CA-7 has it’s own online driver, there are some operational characteristics of the terminal you should be aware of. 1.

2. 3.

4.

5. 6. 7.

8.

Once logged onto CA-7, your terminal has two main sections. The first section is the first line of the terminal. This is referred to as the ‘top line’. Any command entered on this line overrides any commands entered in formatted screens. The second section is the rest of the screen. When entering formatted screens, the ‘top line’ will be blank and the formatted screens will start on line #2 of the terminal. When entering commands, the command will remain on the ‘top line’ and the output from the command will start on line #2. The ‘ENTER’ key and the ‘PA01’ key are ‘page forward’ keys. The ‘PA02’ key is a ‘page backward’ key. After issuing commands, you may page forward or backward as often as you like. When the ‘REQUEST COMPLETED’ message is displayed, you are at the end of the listing. You do not have to go to the end of the listing before issuing your next command. The ‘space bar’ may not be used to blank out the ‘top line’ or any numeric fields in the formatted screens. To erase information, use the ‘ERASE EOF’ key on the left side of you keyboard. This key will erase one line or one field, depending on where the cursor is positioned on the screen. Find out how to get to the ‘HOME’ position on your terminal. Since CA-7 has it’s own PF keys, any PF keys defined for other software products will not work under CA-7. Use the ‘tab’ key on your keyboard to jump from field to field on the formatted screens. The job screen is the best place to experiment with them and see what they will do. Using the cursor control keys will slow you down. One you start using the formatted screens, always check the ‘MESSAGE’ line at the bottom of the screen. It will either tell you what to do next, or is there was an error, what the error was. If there is an error, you will always have to re-enter the first character of the FUNCTION before pressing ‘ENTER’. The error message on the formatted screens will say ‘INVALID OR OMITTED xxxxx DATA’, where ‘xxxxx’ is the name of the field with the error. There are no spaces or quotes in any of the CA-7 commands.

Finding out what is going on

2

The LQ command is used to list current activity in the Request, Ready and Active queues. The format of the command is ‘LQ’.

Probably, the most important field on this listing is ‘JOB STATUS’. At a glance, you can tell which jobs are having problems. If an abend, condition code failure or JCL error occurred, it will be recorded in this field. ‘A-Xnnnn’ indicates the job abended. The abend code is listed. ‘R-JCLERR’ indicates the job had a JCL error ‘SKELETON’ indicates the JCL is still being brought into the Request Queue. If this status does not change the next time you enter the ‘LQ’ command, something is wrong with the JCL (it probably does not exist). In this case, cancel the job out of the Request Queue and Demand the job one the JCL problem has been corrected. ‘C-C0000’ indicates the job is going through completion processing ‘R-C0004’ indicates the job failed the condition code check defined for the job. The bad code is listed. ‘R-REQUE’ indicates the job has been requeued back to the request queue. ‘LATE’ indicates the job did not start on time or will not finish on time.

3

The ‘LIST’ command will list everything in abend status. The format of the command is “LIST”.

Another format of the LIST command is ‘LIST,PROSE=YES,JOB=xxxx’, where ‘xxxx’ is either the CA-7 number or actual jobname of the job in abend status. In addition to listing all steps of the abended job and abend information, this format will also list the #RESTART Prose segment for the job is one exists. If Prose has not been defined for the job, or the #RESTART segment has not been set up, you can leave off the ‘PROSE=YES’ subparameter, and still get all the abend information for the job.

4

CONTROLLING CA-7 ACTIVITY CA-7’s TEXT EDITOR CA-7’s Text Editor is used to modify Prose and JCL members. When entering the Text Editor, you will see a screen that looks something like this. PF 00010 //CA7SCHD JOB (Account Information),PRDCTL,CLASS=E,MSGCLASS=K, MSGLEVEL=(1,1)

The cursor is positioned under the ‘P’ in PF. PF is a command which stands for ‘Page Forward’. This command can be changed to: PB HF HB

-

for Page Backward for Half Page Forward for Half Page Backward

TOP

go to the TOP BOT go to the Bottom

When the ‘ENTER’ key is pressed, CA-7 will carry out whatever command is displayed. To copy or move lines, the command formats are: COPY a,s,e,n Where:

and

MOVE a,s,e,n

a = After which line do you want the information copied or moved s = The starting line of information you want copied or moved e = The ending line of information you want copied or moved n = The number of times you want the information copied or moved. (The default is 1 time)

To insert lines, move the cursor to the line sequence number where you want the line(s) inserted. Enter ‘In_’, where ‘n’ is the number of lines to be inserted. SPECIAL NOTE: When inserting lines, the command must be followed by a blank, or CA-7 will pick up the rest of the sequence number as part of the command. To delete lines, you may use the ‘D’ or ‘DD’ functions. NOTE: Once you press ‘ENTER’ when specifying the ‘DD’ function, CA-7 will delete from the first ‘DD’ to the second ‘DD’ or to the end of the current screen display, whichever comes first. To cancel any changes made without saving them to the database or a JCL file, replace the ‘PF’ command with ‘EXIT’ and press ‘ENTER’

5

How to Control What is Happening Jobs in the Request Queue are controlled by going directly into the queue. This is accomplished by entering ‘XQJ’ as a top line command.

The jobs will be listed in alpha/numeric sequence. What you can do to the jobs are the options on the right side of the screen. The cursor is positioned on the ‘Top line’. You must use your tab key to position your cursor next to the job name. By placing a command letter next to a job name, CA-7 will either carry out the command or take you to a secondary screen where you can carry out the command. CANCEL By placing a ‘C’ next to a jobname, you are canceling the job out of the Request Queue. When a job is canceled, job triggers will not be performed and the job will not satisfy requirements for other jobs. This function has been removed from this site. RESTART By placing an ‘F’ next to a jobname, CA-7 will transfer you to the restart screen for the job. From here you can restart, resubmit or force complete the job. HOLD Placing an ‘H’ next to a jobname will hold that job in the Request Queue until a manual release is performed. RQMT POST By placing an ‘X’ next to a jobname, CA-7 will transfer you to the

requirement post screen. From here, you can browse outstanding requirements. You also have the option of satisfying any requirements you choose. EDIT QJCL By placing an ‘E’ next to the jobname, CA-7 will transfer you to the Text Editor and display the job’s JCL currently in the trailer queue. From here, you can perform JCL setup before a job runs and insert overrides before resubmitting for restart.

6

SATISFYING REQUIREMENTS To browse and/or satisfy outstanding requirements for a job, use the ‘X’ option from the XQJ screen. This is the only place where USR and EXT requirements can be satisfied.

The cursor is positioned on the ‘Top line’. You must use your tab key to position your cursor next to the requirement, and place an ‘X’ next to the requirement to be satisfied. If you are just browsing, press ‘ENTER’. CA-7 will return you to the XQJ screen. HELPFUL HINT: If you want to browse outstanding requirements for multiple jobs, place an ‘X’ on the left side of all the jobs you want displayed. CA-7 will display the requirements for each job, one job at a time. By pressing ‘ENTER’; the next job will be displayed. If you do not want to look at the rest of the jobs you already selected, go to the top line and enter a new command. Additional Commands to view the Request Queue In addition to the XQJ command, there are other commands that can be used to view the request queue. XQ displays all jobs in the order they enter the CA-7 queue XQN displays all jobs in numerical order XQM displays all jobs in job name sequence with a requirements summary

7

DATA SETS Data sets pop up all over CA-7. From automatically building data set requirements to triggering in production jobs based on the creation of specific data sets. Each area involved in CA-7 will be discussed. INT vs EXT When CA-7 encounters a data set used by a job under it’s control, CA-7 checks the disposition field for all occurrences of the data set. If CA-7 finds an occurrence with a DISP=NEW, the data set is known as an internal (INT) data set (the creation of the data set is internal to CA-7’s knowledge). Internal data set requirements will automatically be satisfied if the data set is created by a job under it’s control. If CA-7 never finds a DISP=NEW for a data set, the data set is then known as an external (EXT) data set (the creation of the data set is external to CA-7’s knowledge). External data set requirements will never be automatically satisfied. External data sets are usually marked as ‘PERM’ on the DSN screen. External data set requirements will have to be manually satisfied at run time.

8

RESTARTING JOBS When a job has an abnormal termination, it is returned to the Request Queue. At this time, another requirement is added to the job (RESTART REQUIRED). It is assumed that JCL overrides will need to be made. To make JCL changes, use the ‘E’ option from the XQJ screen. This will take you to the Text Editor where a copy of the job’s JCL from the Trailer Queue is displayed. Make all necessary changes. Once they have been made, change the ‘PF’ command to ‘JCLSR’. ‘JCLSR’ is 3 commands in one. ‘JCL’ will do a syntax check on your submission JCL. If there are errors, the screen will change, the errors will be listed, and the errors will be explained to you. Press ‘ENTER’ to return to the Text Editor and correct your mistakes. When no errors are encountered, CA-7 will do a save (S) and replace (R ). The ‘S’ will save the changes you made into your active area. The ‘R’ will replace the JCL in the Trailer Queue. NOTE: It is not necessary to do the ‘JCL’ command, but the ‘SR’ is mandatory. Once the ‘SR’ is issued, CA-7 will return you to the XQJ screen. Now, select the ‘F’ option. This will take you to the RESTART screen.

9

The cursor will be positioned in the ‘REASON’ option. A Reason-For-Rerun must be entered. If AUTOS is on or a ‘PRE’ command has been issued from CA-11, the starting step will be displayed in the START field. (Remember, this field will be blank if the first step is the starting step). If you agree with the starting step, place an ‘X’ in the RESTART option and hit ‘ENTER’. If you do not agree with the step name in the START field, change it before pressing ‘ENTER’. The ‘CC’ and ‘BYPGDG’ fields are also available at rerun/restart time if you require them under CA-11. *** NOTE: If the RMS step did not successfully complete during a production run, you must select the ‘RESUBMIT’ option. If you select the ‘RESTART’ option, CA-11 will rerun the current production cycle. If the CA-11 message line indicates the job is set for production in the CMT, a Resubmit function should be performed.

10

CANCEL vs FORCE COMPLETE The ‘CANCEL’ top line command says to cancel a job out of CA-7’s queues. When a cancel is issued, job triggers will not be performed and requirements will not be satisfied for other jobs. (Cancel a job when it is called in by mistake or you do not want to finish running a job stream when a job abends). ‘FORCE COMPLETE’ is an option from the RESTART screen. ‘FORCE COMPLETE’ says to get rid of a job in abend status and treat it as a normal EOJ. Forcing complete a job will cause CA-7 to perform any triggers defined in the data base and will satisfy requirements for other jobs. (When using the ‘FORCE COMPLETE’ option from the restart screen, you are required to specify a Reason-for-Rerun). Forcing complete a job under CA-7 will also set the job back to production in CA-11’s data base. This keeps both data bases in sync.

CANCEL COMMAND Jobs are canceled from any queue by using the top line ‘CANCEL’ command. The format of the command is CANCEL,JOB=nnn Where: ‘nnn’ is the CA-7 job number assigned to the job. ***Note: Canceling a job from either the Ready or Active queues will not cancel the job from JES. CA-7 never touches jobs once they have been submitted to JES.

If a job is set for rerun under CA-11, the about command cannot be used. To cancel a job that is set for rerun, your command format is: CANCEL,FORCE=YES,JOB=nnn The ‘FORCE=YES’ sub-parameter will set the job back to production in CA-11’s data base. This keeps both data bases in sync.

11

DEMAND vs RUN There are two commands available which manually bring jobs into the Request Queue. They are ‘DEMAND’ and ‘RUN’. The ‘DEMAND’ command is used to schedule on-request work (recoveries, restores, user requested job, etc.). When used, any requirements defined for the job will be honored, and when the job terminates successfully, any triggers defined in the data base will be performed and requirements will be satisfied for other jobs. The format of the ‘DEMAND’ command is: DEMANDH,JOB=jobname The ‘H’ on the end of the command instructs CA-7 to put the job on hold in the Request Queue. The ‘H’ is optional. However, if you demand in a job that does not have any requirements, the job will immediately submit to JES. If you do not want the trigger processing to take place, ‘SET=NTR’ must be added to the command. The ‘RUN’ command is used to schedule additional runs of a job and reruns (jobs that have completed successfully and are no longer in a CA-7 queue). The ‘RUN’ command will not do what the ‘DEMAND’ command does. No requirements are honored, triggers will not be performed and requirements will not be satisfied for other jobs. The format of the ‘RUN’ command is: RUNH,JOB=jobname,SCHID=nnn The ‘H’ on the end of the command instructs CA-7 to put the job on hold in the Request Queue. The ‘H’ is optional. However, if you demand in a job that does not have any requirements, the job will immediately submit to JES. The ‘SCHID’ field can actually be specified on both commands. This gives you the capability of selecting specific schedule ID’s. Remember, that SCHID’s give you the ability to define multiple versions of a job based on trigger, requirement and/or JCL changes. In a rerun situation, you want to be extra careful in selecting a SCHID in case there are JCL changes involved. The ‘LPRRN,JOB=jobname’ command will tell you the last SCHID used.

12

By using CA-7’s restart screen, there is no need to do a ‘PRE R’ command under CA-11 to set up a job for a rerun. Issue the ‘RUNH’ command to bring the job into the Request Queue. (Be sure to specify the correct SCHID). 2. Select the ‘F’ option from XQJ. 3. When the RESTART screen is displayed, select the RESTART option and fill in any of the restart fields required for the rerun. (Be sure to specify you rerun code in the REASON field). 4. When you are ready to release the job, use the ‘X’ option from XQJ to satisfy the HOLD requirement. 1.

CALLING JOBS IN EARLY Normal circumstances do not require operators to request work to be processed early. If jobs are not being brought into the Request Queue when they are ready to run, they should be defined better in the data base. However, circumstances are not always normal. To call in a job early that is calendar scheduled, use the ‘SET=SKP’ parameter of the ‘DEMAND’ command DEMAND,SET=SKP,JOB=jobname,SCHID=nnn This indicates the next scheduled cycle is to be skipped. ***NOTE: This will not work for triggered jobs.

13

ADDING TEMPORARY REQUIREMENTS Temporary job and user requirements can be added to a job while it is in the Request Queue. This is accomplished by using the ‘ADDRQ’ command. The formats of this command are: ADDRQ,JOB=jobname,DEPJOB=depname ADDRQ,JOB=jobname,USR=user requirement Where ‘jobname’ is the name of the job receiving the requirement and ‘depname’ is the name of the job that is to be the requirement. Once the DEPJOB terminates successfully, the requirement will automatically be satisfied. The ‘user requirement’ can be up to 36 characters. If more information is needed, issue the command multiple times until all requirements have been added.

JCL SCREEN The JCL screen is used to make JCL changes to a job before it is brought into the Request Queue. To get to the JCL screen, enter ‘JCL’ as a top line command.

14

MAKING TEMPORARY JCL CHANGES To make temporary JCL changes for the next run of a job: 1.

Enter ‘FE’ for the function

2. Enter the job name to be changed in the MEMBER field 3. The index number will default to the JCL-ID defined to the member in the Job Screen 4. Press ‘ENTER’ 5.

Make all desired changes to the JCL. When finished, change the ‘PF’ command to ‘JCLS’ or ‘SAVE’

6.

When CA-7 returns you to the JCL screen, change the function to ‘SAVE’

7. Go to the DSN field and press your ‘ERASE EOF’ key 8. Tab over to the JCL-ID field and enter ‘254’ 9. Your cursor is now in the VOL-SER field. Press your ‘ERASE EOF’ key 10. Press ‘ENTER’ The message at the bottom of the JCL screen should now read ‘SAVE FUNCTION SUCCESSFUL (JCL SET FOR RETREIVAL FROM OVRD-LIB)’. This indicates the next time the job enters the Request Queue, CA-7 will pull the JCL from the 254 library, and store it in the Trailer Queue for that run. The JCL will be deleted from the 254 upon successful completion of the job. The next production run will use a copy of the JCL from the production library. If you need to make additional changes, specify ‘254’ in step #3. When all changes have been made, change the ‘PF’ command to ‘JCLSR’ or ‘SR’ If you change your mind and do not want to use the changed JCL for the next run, specify ‘DELETE’ in the FUNCTION field, the job name in the MEMBER field, and ‘254’ in the JCL-ID field. This will put JCL retrieval for the job back to normal.

15

CA-7 also provides a number of functions which can be accomplished with statements which begin with a # in position 1. These statements may be located anywhere within the execution JCL after the JOB statement (PROCLIB members containing these statements are not seen by CA-7 and including them there would thus serve no purpose). They may be scheduled with #Jx statements if desired, however, they may be included by themselves if conditional inclusion is not necessary. The following statements may be placed in the execution JCL: #HLD

Places the job on HOLD. Similar to the HOLD command and the job screen HOLD option

#JCL

Sets a JCL override requirement

#MSG

Sends messages to the master station at job submission time. The syntax for this command is #MSG,message-text

#NOX

Makes this run nonexecutable

#NTR

Turns off triggering by successful job completion for this run. Similar to the DEMAND command with SET=NTR option.

#SCC

Defines step level condition code checking criteria.

NOTE: All the functions listed above must be done prior to the JCL entering the Request Queue.

16

REPLACING TRAILER QUEUE JCL In some abend situations, you may find it easier to ‘replace’ the JCL in the Trailer Queue rather than enter numerous overrides through XQJ. This can be accomplished by using both the JCL and QJCL screens. 1.

Enter ‘JCL’ on the top line to get to the JCL screen

2.

Enter ‘FETCH’ for the function

3. Enter the job name to be retrieved in the MEMBER field 4. Enter the index number where the new JCL member resides 5.

Press ‘ENTER’ (You just brought a copy of the JCL into your Active Area)

6.

Enter ‘QJCL’ on the top line to get to the QJCL screen.

7.

At the QJCL screen, enter ‘REPL’ for the function

8. In the JOB field, enter the name of the job whose JCL is to be replaced 9.

Press ‘ENTER’ (You just replaced the job’s JCL with what was in your Active Area)

10. When ready, resubmit the job using the RESTART option of the XQJ screen.

17

HOW DO I FIND OUT WHAT IS GOING TO HAPPEN Forecasting under CA-7 indicates what should happen based on what is defined to the data base. There are two types of forecasts, standard forecasts and ‘Q’ forecasts. A ‘Q’ forecast indicates a forecast is to be done starting with what is currently in the Request, Ready and Active queues, and is to include all jobs to be scheduled for the time frame selected. **NOTE: If a job stream triggers jobs that will run past a forecast time frame, they will still be included in the forecast output. To find out what jobs will be processing, enter ‘FQJOB,SPAN=hh’ where ‘hh’ is the number of hours you want to forecast. This forecast command is normally used by operations. Issue it at shift turnover time for the next 8 hours to see what will be processing on your shift. Later on, issue it again with a shorter time span to see what will be executing the rest of your shift.

The forecast command is also good to see when you will be finished with production work after a CPU outage. After CA-7 is brought back up, issue the forecast command specifying enough hours to cover the rest of you scheduled production window. Since CA-7 knows what is left to run and how long it runs, the forecast will reflect new estimated completion times for the jobs.

18

Since standard forecast commands such as ‘FJOB’ never look at what is currently in the queue, you have to specify specific start date and times. The formats for this command is as follows: FJOB,FROM=(mmddyy,hhmm),TO=( mmddyy,hhmm) or SPAN=hh The default for ‘yy’ is the current year. The default for ‘hhmm’ is ‘0000’

The output from this forecast is the same as the ‘Q’ counterpart except that jobs from the Request, Ready and Active queues will not be considered. The ‘FJOB’ forecast is good to see what will happen this weekend, this end of month, etc.

19

FORECAST STRUCTURES After schedules and triggers have been defined for a job stream, it is always a good idea to verify the structures as CA-7 sees them. The FSTRUC command is used for this purpose. A structure can be listed for: A specific system

‘FSTRUC,SYS=system,SCHID=nnn’

Starting at a specific job

‘FSTRUC,JOB=jobname,SCHID=nnn’

The default SCHID is ‘001’. A forecast structure should be issued for each SCHID defined in the data base. The date and time information listed for the first job is the date and time when you issued the command. FSTRUC lists what would happen IF the jobs were to run at the time the command was issued. Below is a sample forecast structure for the Canada A/P system. The LEV# column indicates the jobs level from the originating job. For example, 002 indicates that job is on the second level of triggers from the originating job within the structure. A job without a level number is either time scheduled, or it is not triggered by another job under the requested SCHID.

20

How do I find out what has happened? The ‘LJES’ command can be used to list JES job numbers for jobs in the Active and Prior Run queues. The format of this command is ‘LJES’. This format will list all jobs currently in the Active Queue.

Another command format you may be interest in is: LJES,Q=*,JOB=jobname This format will list all occurrences of the specified jobname from both the Active and Prior Run queues.

21

The Prior Run Queue keeps a record of the last good run of every job under CA-7’s control. The format of the command is: LPRRN,JOB=jobname

**NOTE: Since the Prior Run Queue can be a rather large file, it is recommended you always limit the display by specifying a specific or generic job name as part of the command.

22

The Run log contains a record of all job and network occurrences for the last five calendar days. The format of the command is ‘LRLOG’. This will display the log for the current day (00:00 - 23:59).

To limit this display to all occurrences of a specific job, enter ‘LRLOG,JOB=jobname’. To get all occurrences of a job for the last five days, enter ‘LRLOG,DATE=*,JOB=jobname’. The ‘LRLOG,DATE=*’ command format will list all records for the last five days. To get information for a specific day, use the ‘DATE=*yyddd’ sub-parameter on the above examples, where ‘yyddd’ is the year and Julian day to be listed.

23

HELP Command formats are stored in the HELP library. To get into this facility, enter ‘HELP’ as a top line command.

This works similar to all online tutorial facilities. Enter the application value for the category you are interested in, and CA-7 will provide you with the rest.

*** End of Document ***

24