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


Chapter 2 Setting Up the Development Environment : @SCHEDULEMODEL Implementation

@SCHEDULEMODEL Implementation
What is @SCHEDULEMODEL?
The TIBCO Object Service Broker @SCHEDULEMODEL shared table is a parameterized TDS table that contains instances of JCL, Solaris scripts, and batch files. Instances of this table are submitted for processing when users execute rules in batch mode with the use of the SCHEDULE statement. Instances are also used in the TIBCO Object Service Broker Promotion system and by the RULEPRINTER and HLIPREPROCESSOR tools.
@SCHEDULEMODEL supports the use of variable and value substitution; new variables can be defined and subsequently substituted at runtime, and values defined at installation time can be overridden.
Why Allow the Substitution of Variables and Values?
The substitution of variables and values provides a number of advantages to a site:
These values take precedence over the Execution Environment parameters set at installation time.
Users can share instances of the @SCHEDULEMODEL table because information specific to their user IDs can be supplied at runtime.
Implementation Options
At installation time, values used at runtime for some of the instances provided with TIBCO Object Service Broker for the @SCHEDULEMODEL table instances are customized to reflect your site’s standards and naming conventions. Values for any or all of these provided instances, or other instances defined at your site, can be supplied by:
Setup Requirements for Substituting Values from a Table
The following items must be prepared to define additional substitution variables and alternate values, by using a TDS table:
Specify {table.field} references in the table instances of @SCHEDULEMODEL where you plan to use variables defined in the substitution table.
Define and Edit a TDS Table
To prepare a TDS table, complete the following steps:
1.
Define the primary key to hold the values of the TIBCO Object Service Broker user IDs authorized to use instances of the @SCHEDULEMODEL table. The primary key cannot be a composite primary key.
Any appropriate values can be used for the table name, field names, field syntax, and field lengths.
2.
3.
Sample Table
The following example illustrates a single occurrence for the TIBCO Object Service Broker user ID USR40, from the sample substitution table EXTENDEDPROFILE:

 
--- SINGLE OCCURRENCE EDITOR ---
EDITING TABLE : EXTENDEDPROFILE
TABLE TYPE : TDS
COMMAND ==>
------------------------------------------------------------------------------
HURON_USERID : USR40
ACCTINFO : (’9061HRNUSR10000’,#553)
JOBCLASS : A
JOBNAME :
JOBPARM : SYSAFF=*,TIME=30,LINES=999
MSGCLASS : Y
NOTIFY : USR40
REGION : 4096
MSGLEVEL : (1,1)
 
PFKEYS: 1=HELP 2=DOCUMENTATION 3=SAVE 12=CANCEL 13=PRINT 22=DELETE

 
Modify the @SCHEDULEMODEL Instance
To provide a reference between the variable name and its substitution value as stored in the TDS table, complete the following steps:
1.
2.
Use the {table.field} format, in the instance of the @SCHEDULEMODEL table. For example, to reference the EXTENDEDPROFILE table for a value for the variable ACCTINFO, put in:
ACCTINFO ={EXTENDEDPROFILE.ACCTINFO}
Substitution variables in @SCHEDULEMODEL are normally enclosed in delimiters such as braces ({ }). The actual delimiters used at a site are set with the Execution Environment parameters VARLDELIMITER and VARRDELIMITER.
3.
If possible, use a Mod 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.
Sample Instance of @SCHEDULEMODEL
The following example illustrates an extract from a sample instance of @SCHEDULEMODEL containing references to the new variables and providing values for new and existing variables.

 
BROWSING TABLE : @SCHEDULEMODEL(MVS,DOCEXMPL)
COMMAND ==>
SCROLL: P
NUMBER CARD
_ ------ ----------------------------------------------------------------------
_ 10 //{USERID} JOB ({EXTENDEDPROFILE.ACCTINFO}),’TORONTO DOC03’,
_ 20 // NOTIFY={EXTENDEDPROFILE.NOTIFY},
_ 30 // MSGCLASS={EXTENDEDPROFILE.MSGCLASS),
_ 50 // REGION={EXTENDEDPROFILE.REGION},
_ 60 // MSGLEVEL={EXTENDEDPROFILE.MSGLEVEL}
_ 70 /*JOBPARM {EXTENDEDPROFILE.JOBPARM}
_ .
_ .
_ .
_
 
_
_
 
PFKEYS: 1=HELP 5=FIND NEXT 9=RECALL 18=EXCLUDE 13=PRINT 3=END 14=EXPAND

 
See Also
TIBCO Object Service Broker Shareable Tools for more information on the RULEPRINTER and HLIPREPROCESSOR tools.
Installing and Operating for your operating environment for information about supplied instances.
TIBCO Object Service Broker Programming in Rules for information about submitting rules in batch.

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