Copyright © Cloud Software Group, Inc. All Rights Reserved

Customization of the TIBCO Object Service Broker @SCHEDULEMODEL Table

During installation, you must customize some of the supplied @SCHEDULEMODEL table instances. In particular, tailor the JCL statements in several table instances to reflect your site’s standards and naming conventions. You can execute in batch mode through the @SCHEDULEMODEL table by means of the SCHEDULE statement. @SCHEDULEMODEL JCL is also used in the Promotion system.

Here are the related references:

•	For information on the @SCHEDULEMODEL table and the SCHEDULE statement, see the TIBCO Object Service Broker Programming in Rules and TIBCO Object Service Broker Application Administration manuals.

•	For details on @SCHEDULEMODEL JCL for promotions, see the TIBCO Object Service Broker Managing Deployment manual.

Step 1: Log In and Invoke the Table Editor

Do the following:

1.	Log in to TIBCO Object Service Broker as SYSADMIN with USER EXEC.

2.	Invoke the Table Editor for each of the specified instances. For example, on the command line, type the following and press Enter:

COMMAND ==> ED @SCHEDULEMODEL('MVS','*DEFAULT*')

Step 2: Edit Table Instances

Edit the instances in table @SCHEDULEMODEL, as follows:

1.	For all table instances, customize the JCL JOB card parameters: account code, name, and message class.

Table instance @SCHEDULEMODEL (MVS,*DEFAULT*) is for general users.

2.	For all table instances, except @SCHEDULEMODEL (MVS, PROM_ALLOC), change all DD statements with a last qualifier of AUTH to $HLQNONV$.$INSTVER$.AUTH, where $HLQNONV$ and $INSTVER$ are OSEMOD installation variables; for example, OSB.SMP60.AUTH.

 

Pay particular attention to the JOB card for jobs submitted by multiuser address spaces, such as the Native Execution or CICS environments. Unless your z/OS external security product has cross-authorized the environmental user identification to submit jobs on behalf of TIBCO Object Service Broker-defined users, your jobs might fail on submission if you have not deleted or commented out the parameter USER={USER} on the associated @SCHEDULEMODEL job card.

When a rule causes a job submission, TIBCO Object Service Broker automatically substitutes the parameter within the curly brackets ({}) with the current value for the parameter within the brackets. For user identifications such as SYSADMIN, the external security manager is unlikely to recognize the user identification SYSADMIN on the JOB card and, subsequently, Job Entry Subsystem (JES) fails the job before execution with a message like this one:

IRR012I VERIFICATION FAILED. USER PROFILE NOT FOUND.

or this one:

IEF642I EXCESSIVE PARAMETER LENGTH IN THE NOTIFY FIELD.

If the NOTIFY parameter is used, the job could fail with the following message:

IKJ144I UNDEFINED USERID(S) uuuuuuu

Table Instances and Functions of JCL

The following table describes JCL’s table instances and functions.

MVS,*DEFAULT*	Applies if the object of a SCHEDULE command is a rule and no matching @SCHEDULEMODEL instance exists.
MVS,@HLL_COBJCL	Processes TIBCO Object Service Broker statements embedded in a COBOL program. It sends the source to the HLI preprocessor in the TIBCO Object Service Broker environment and then redirects the output as input to a PROC to compile and link COBOL. To learn how to use COBOL programs with the TIBCO Object Service Broker host language interface, see the TIBCO Object Service Broker for z/OS External Environments manual.
MVS,APPLY_CHANGE	Used by the Promotion system to apply a change request in a source system in batch.
MVS,APPLY_PROM	Used by the Promotion system to apply a change request in a target system in batch.
MVS,PROM_ALLOC	Allocates data sets used by the Promotion system.
MVS,SPOOLSTRIP	Prints output in multiple session environments, such as CICS or Native Execution. Ensure that the External Environment parameter PRINTSPOOLCLASS points to a non-HELD JES SYSOUT output class. Otherwise, the following error occurs: S6BDP001E - IEFSSREQ ERROR - R15=X’00’ - SSOBRETN=X’04’
MVS,TREE	Used by the PR print rules option on the workbench if Hardcopy is set to Y on a print-tree request.
MVS,XRF	Used by the PR print rules option on the workbench if Hardcopy is set to Y on a cross-reference request.

Specified Variables

Do not change the following substitution variables, which represent Execution Environment parameters. For details on those parameters, see the TIBCO Object Service Broker Parameters manual.

{ACTION}	The type of invocation for the initial user-rule specified in the RULE parameter.
{BROWSE}	A specification of whether the session’s first transaction can update TDS tables and external databases.
{CHARSET}	The default national character set.
{CLASS}	The default JES SYSOUT class for output generated with the TIBCO Object Service Broker print facilities. Note: In a JES3 environment, ensure that the output class specified in the user profile options is one that is defined to JES3 as External Writer Held. The SYSUT2 statement in the SPOOLSTRIP JCL contains a hard-coded class so that no substitution of the Class parameter from the user profile occurs.
{COPIES}	The number of copies to print of a report generated by TIBCO Object Service Broker.
{DB2LOG}	A specification of whether the Execution Environment is to log DB2 server commands for the purpose of creating STATIC SQL handlers.
{DEST}	The default printer destination for output generated by TIBCO Object Service Broker.
{FCB}	The name of a Forms Control Buffer (FCB) to be used during the printing of output generated by TIBCO Object Service Broker.
{FORM}	The name of a form on which JES SYSOUT output generated by TIBCO Object Service Broker is to be printed.
{INSTLIB}	The name of the library that holds the rules for the installation promoted from the local libraries.
{LIBRARY}	The name of the local library for rules calls.
{MDL}	The model Execution Environment communications identifier.
{PARM}	The arguments for the rule for batch processing. Wraps alphanumeric values in double single quotation marks: two at the start and two at the end.
{PARS}	The arguments for the rule for batch processing. Wraps alphanumeric values in single single quotation marks: one at the start and one at the end.
{PASSWORD}	The user’s login password to be passed to TIBCO Object Service Broker.
{PRINTDEST}	The default printer destination for output generated by TIBCO Object Service Broker.
{RULE}	The name and arguments of the first application rule to be invoked after processing of login rules. Does not apply to SDK (C/C++) or SDK (Java) sessions.
{SEARCH}	The library search environment for the first rule to be executed.
{SYSTEMLIB}	The name of the rules library that contains the rules shipped with TIBCO Object Service Broker.
{TDS}	The communications identifier (COMMID) of the Data Object Broker to which to connect.
{TEST}	A specification of whether to run user sessions in test mode.
{UCS}	The name of a universal character set (UCS) for printing the JES SYSOUT output generated by TIBCO Object Service Broker.
{USERID}	The session user ID for TIBCO Object Service Broker.
{VARLDELIMITER}	The character that serves as the left delimiter for enclosing substituted variables in @SCHEDULEMODEL.
{VARRDELIMITER}	The character that serves as the right delimiter for enclosing substituted variables in @SCHEDULEMODEL.
{XWTR}	The name of an external writer (XWTR) for printing output generated by TIBCO Object Service Broker.

For details on the PR print rules option on the workbench, see the section on the RULEPRINTER tool in the TIBCO Object Service Broker Shareable Tools manual.

Do not name a print destination in the JES complex S6BDRPRT, which is the name of the TIBCO Object Service Broker offline print utility that generates and prints output from the Native Execution Environment and CICS. S6BDRPRT runs the SPOOLSTRIP job, which operates incorrectly if the print destination is called S6BDRPRT.

Step 3: Save Changes

Press PF3 to save the changes.

Copyright © Cloud Software Group, Inc. All Rights Reserved