Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 17 Processing Asynchronously in Batch Mode : Editing @SCHEDULEMODEL

Editing @SCHEDULEMODEL
Provided Default Instances
You can copy and modify the default instances of the @SCHEDULEMODEL table that are provided with TIBCO Object Service Broker. The following generic default instances are provided for general usage:
Other instances are provided for specific tasks such as printing and for promotions.
About the Default JCL
The default JCL, @SCHEDULEMODEL(MVS,*DEFAULT*), executes the program S6BBATCH. This program runs a new TIBCO Object Service Broker Execution Environment where the rule can be processed asynchronously.
Example of Customized JCL
The following is an extract of customized batch JCL:

 
_ 60 //HURON EXEC PGM=S6BBATCH,REGION=4096K,
_ 80 //PARM=('TDS={TDS},RULE=INCOME_TAX')
_ 91 //HRNIN DD *
_ 92  {TEST},
_ 93  SEA={SEARCH},
_ 94  C={CHARSET},
_ 95  L=REPORT
_ 96 /*

 
About the Example
The customized JCL specifies the REPORT local library and the INCOME_TAX rule. This ensures that when the INCOME_TAX rule is scheduled for batch processing the local library is always REPORT and the rule that is executed is always INCOME_TAX.
About the Default Windows Batch Program and Solaris Script
The default batch program, @SCHEDULEMODEL(NT,*DEFAULT*) and the default script, @SCHEDULEMODEL(UNIX,*DEFAULT*), execute the utility osBatch. This utility starts a new Execution Environment where the rule can be processed asynchronously.
As well, the following @SCHEDULEMODEL table instances for “NT” and for “UNIX” should not be modified: *DEFAULT*, APPLY_CHANGE, APPLY_PROM, TREE, XRF. These instances should contain the following occurrences:
Windows
 
10
20
30
40
50
60
70
80
90
100
110
120
130
140
150
OSBATCH DOB={DOB} "R={RULE}({PARM})" \
U={USERID} P={PASSWORD} \
EENAME={EENAME} \
L={LIBRARY} I={INSTLIB} \
SEA={SEARCH} AC=T \
TEST={TEST} BROWSE={BROWSE} \
SESSIONLOGCLEAR={SESSIONLOGCLEAR} \
MSGLOGMAX={MSGLOGMAX} \
TRANMAXNUM={TRANMAXNUM} \
CHARSET={CHARSET} \
"PRINTDEST={DEST}" \
DSBIFTYPE={DSBIFTYPE} \
DSIXFTYPE={DSIXFTYPE} \
DSFIELDSEP={DSFIELDSEP} \
"DSDIR={DSDIR}"
Solaris
 
10
20
30
40
50
60
70
80
90
100
110
120
130
140
150
osBatch DOB={DOB} "R={RULE}({PARM})" \
U={USERID} P={PASSWORD} \
EENAME={EENAME} \
L={LIBRARY} I={INSTLIB} \
SEA={SEARCH} AC=T \
TEST={TEST} BROWSE={BROWSE} \
SESSIONLOGCLEAR={SESSIONLOGCLEAR} \
MSGLOGMAX={MSGLOGMAX} \
TRANMAXNUM={TRANMAXNUM} \
CHARSET={CHARSET} \
"PRINTDEST={DEST}" \
DSBIFTYPE={DSBIFTYPE} \
DSIXFTYPE={DSIXFTYPE} \
DSFIELDSEP={DSFIELDSEP} \
"DSDIR={DSDIR}" &
Editing Instances of @SCHEDULEMODEL
You use the Table Editor to create new instances or modify existing instances of the @SCHEDULEMODEL table.
If possible, use a Model 5 3270 terminal (or its equivalent, if you are emulating a 3270 terminal) to edit the table. If you do not use a Mod 5 terminal, you must edit the table with the Single Occurrence Editor.
Data in the Card field of the @SCHEDULEMODEL table is limited to 72 characters. A command in the table can be continued over several lines by including a continuation character (\) at the end of the line. TIBCO Object Service Broker removes this character to pass a single line to the operating system.
See Also
TIBCO Object Service Broker for z/OS Installing and Operating for details about the instances of @SCHEDULEMODEL supplied with TIBCO Object Service Broker.
TIBCO Object Service Broker for z/OS External Environments about the parameters for S6BBATCH. Also refer to this manual about the PARM statement and the HRNIN DD statement, both of which are used in this sample JCL.
TIBCO Object Service Broker for Open Systems Utilities about the parameters for osBatch.
TIBCO Object Service Broker Managing Data about using the Table Editor.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved