Configuring the SCRPTLIB

Jobs that run on fault-tolerant workstations can use solely a non-centralized script or a combination of centralized and non-centralized scripts (if they are to take advantage of the SCRPTLIB statements). These jobs must be associated to members of the SCRPTLIB (identified by the EQQSCLIB DD statement of the controller and the daily planning JCL). You also define some keywords such as the user name, the return code, and the variable substitution in the SCRPTLIB.

In relation with the variable substitution in the SCRPTLIB, you can also use IBM Z Workload Scheduler variables, with the exception of the Dynamic-Format variables which require the SETFORM directive. No job tailoring keyword or directive is allowed in theSCRPTLIB, except for the VARSUB keyword.

You must use the JOBREC statement in every SCRPTLIB member to specify the script or command to run. The following statements are optional:

VARSUB: To use the IBM Z Workload Scheduler automatic substitution of variables when the Symphony file is created or when an operation on a fault-tolerant workstation is added to the current plan dynamically.
RECOVERY: To use the IBM Workload Scheduler recovery.

The syntax for centralized scripts is:

VARSUB
   TABLES(GLOBAL|tab1,tab2,..|APPL)		
   PREFIX('char')
   BACKPREF('char')
   VARFAIL(YES|NO)
   TRUNCATE(YES|NO)	
JOBREC
   JOBUSR ('username')
   INTRACTV(YES|NO)
   RCCONDSUC('success condition')

The syntax for non-centralized scripts is:

VARSUB
   TABLES(GLOBAL|tab1,tab2,..|APPL)		
   PREFIX('char')
   BACKPREF('char')
   VARFAIL(YES|NO)
   TRUNCATE(YES|NO)	
JOBREC
   JOBSCR|JOBCMD ('task')
   JOBUSR ('username')
   INTRACTV(YES|NO)
   RCCONDSUC('success condition')
RECOVERY
   OPTION(STOP|CONTINUE|RERUN)
   MESSAGE('message')
   JOBCMD|JOBSCR('task')
   JOBUSR ('username')
   JOBWS('wsname')
   INTRACTV(YES|NO)
   RCCONDSUC('success condition')

The following is an example of a non-centralized script:

VARSUB
   TABLES(APPL)
   PREFIX('&')
   BACKPREF('%')
   VARFAIL(NO)
   TRUNCATE(YES)
JOBREC
   JOBCMD ('ls –l /')
   JOBUSR ('tws')
   INTRACTV(NO)
   RCCONDSUC('(RC=4) OR ((RC>=6) AND (RC<9))')
RECOVERY
   OPTION(RERUN)
   MESSAGE('MESSAGE')
   JOBCMD ('ls /')
   JOBUSR ('&USER')
   JOBWS  ('TWMD')
   INTRACTV(YES)
   RCCONDSUC('(RC=3) OR ((RC>=5) AND (RC<10))')

If in the IBM Z Workload Scheduler database you define a job with a SCRPTLIB member that contains errors, the daily planning batch job sets the status of that job to Failed in the Symphony file. This change of status is not shown in the IBM Z Workload Scheduler interface. You can find the messages that explain the error in the log of the daily planning batch job.

If in the current plan you dynamically add a job whose associated SCRPTLIB member contains errors, the job is not added. You can find the messages that explain this failure in the log of the controller.

However, if you install PTFs UK02507 and UK02508, you can use the end-to-end JOBREC utility that detects errors in your SCRPTLIB definitions before the current plan is generated. See Determining errors in the SCRPTLIB configuration for details.