![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Submits a batch job to a particular queue, views the status of the batch jobs, and views the queues that are available. (E)
Developer’s workbench
• $BATCHOPT is the version of this tool called from within a rule.
• If you want to submit a batch job to a queue as part of a rule or application, use the SCHEDULE statement with the TO clause.TIBCO Object Service Broker Programming in Rules for information about the SCHEDULE statement. See TIBCO Object Service Broker for z/OS Installing and Operating for information about defining queues.
Most of these fields are filled in for you with default values. You can change these values, and you must provide values for the Queue Name and Rule Name fields.The following fields describe the attributes for the rule that you want to execute in batch (refer to the Rule Settings in Batch Submission Main Menu Illustrated).You must provide the name of the queue that executes your TIBCO Object Service Broker rule in batch mode. The queue name is validated to ensure that a queue with that name exists. To view valid queue names, place the cursor in this field and press PF2. A screen similar to the following appears:
You can select a queue from the screen by typing an S next to the queue name and pressing PF3.To see the definition of a queue, use the fourth option (Queue Definition) on the main menu shown in Batch Submission Main Menu Illustrated.
Provide the name of the rule to be executed in batch mode. The rule name is not validated. Enter the order of libraries to search for the rule: S - System library only; I - Installation library, then system library; L - Local library, installation library, then system library. Enter the name of the local library to access as the local library when the requested rule is executed. Parameter Values If the requested rule has arguments, enter the values here, separated by commas. Single quotation marks are not necessary. Currently, you can submit only your own requests for batch jobs; therefore, this field defaults to your user ID and you cannot change it. Batch Command Name Enter the name of the batch command that you created to run your batch request. You can create or modify batch commands with the Build Batch Commands option on the main menu shown in Batch Submission Main Menu Illustrated. To view a list of all the batch commands you created, place the cursor on the BATCH COMMAND NAME field and press PF2 to display the LIST OF JCL NAMES screen:
You can select a batch command by typing an S next to the batch command name and pressing Enter.
Security Group Specify the security group that is in effect when the rule is run in batch mode. You can specify any of your valid groups. Browse Mode Specify whether the rule runs in browse mode or update mode. Y indicates browse mode and N indicates update mode.The following fields describe the print file options (Output Settings in Batch Submission Main Menu Illustrated) for the output generated by the rule run in batch. All these print options are optional. If you do not specify anything for the output settings, the batch server uses the default options specified in the queue definition.
Print Destination Enter the symbolic name of the printer. If you want to include the node name of the printer, specify the print destination in the form:
• node - The node name
• char - A non-alphanumeric character that separates the node name from the printer name
• printer - The printer name Number Of Copies If the output data should be printed or punched on a special output form, enter Y. This flag takes effect in z/OS only. External Writer If you want to direct system output to an unsupported device, you can specify an external routine to direct the output. You must leave this field blank if you specify a node name in the Print Destination field. Enter the FCB (Forms Control Block) value for the type of output format. Enter the UCS (Universal Character Set) value that should be used for printing the output data set.Instead of entering information in all the fields for a batch job request, you can recall the specifications for a previous request by pressing PF4. A screen similar to the following appears:
Use PF11 to scroll to the right to view more of the attributes for previous requests. To select a request, use the S line command; to delete a request, use the D line command.After displaying the selected request on your Submit Batch Request screen, you can modify it to suit your present needs. After entering the information, use one of the following PF keys:If you choose the Build Batch Commands option from the Batch Submission Main menu, you see a screen similar to the following:
• You can select one of the batch command names that you previously defined by placing the cursor next to the name and pressing Enter. Each person has a private copy of the *DEFAULT* batch command and these can be individually customized.
• You can create new batch commands by typing a new name in the Create New Batch Command field and pressing Enter to display a screen similar to the following:
In this environment, you can enter batch commands and edit them with the TED editing facility (refer to TED). When you build your batch command, you can use the following symbols, which are filled in for you when the job is submitted:
• {USERID} - This is replaced with the requestor user ID as specified in the Requestor Id field of the Submit Batch Request Screen (refer to Submit Batch Request Option).
• {TDS} - This is replaced with the communications identifier (for example, VTAM name) that identifies the Data Object Broker that is connected to the batch server.All the TED commands are available. A particularly helpful command for copying existing batch commands is the COPY command. Specify the text table that is your source of data and the data is copied to the table that you are currently editing with TED. For example, to copy the default batch command (named *DEFAULT*) of user USR50, type the following on the command line:@BATCH_JCL is a text table that requires a user ID and the name of the batch command as parameters. For more information about @BATCH_JCL refer to the TIBCO Object Service Broker for z/OS Installing and Operating manual.
You can add more steps to the batch command provided in the default. Do not, however, add a step to execute the requested rule because this step is appended to the end of the batch command when the batch request is submitted.If you choose the View Batch Status option from the Batch Submission Main menu, you see a screen similar to the following:
This screen shows all the requests that you submitted. The screen is refreshed every time you press Enter. The following information is provided:
Rule Name Queue Name FAILED - The execution of the request failed.You can use the D line command to remove requests from the queue, and if the status is SUBMITTED or EXECUTING, you must remove the job from the operating system.NOTE: View Batch Status cannot replace your normal methods of monitoring batch jobs because TIBCO Object Service Broker has no knowledge of jobs that fail due to batch command errors or cancellation by an operator. Submit Date The date that you submitted your request to the queue, not the date when the actual job was submitted to the operating system Submit Time The time that you submitted your request to the queue, not the time when the actual job was submitted to the operating systemIf you choose the Queue Definition option from the Batch Submission Main menu, you see a screen similar to the following one. For more information about defining new queues, refer to the TIBCO Object Service Broker for z/OS Installing and Operating manual.
The example screen shows four existing queues: AFTERNOON, IMMEDIATE, OVERNIGHT, and SUNDAY. To view the definition of one of these queues, position your cursor on the field beside the name of that queue and press Enter. The definition of the queue appears as shown here:
The time in seconds that the batch server waits when the queue becomes empty The number of times the batch server goes into a wait state before shutting itself down Print Destination The name of the printer where you want the batch job output sent. If you want to include the node name of the printer, specify the print destination in the form: node- The node name; char - A non-alphanumeric character that separates the node name from the printer name; printer - The printer name Number Of Copies Whether the output data should be printed or punched on a special output form External Writer Specifies the external routine that directs the output, if the system output is to be directed to an unsupported device (Universal Character Set) Describes the character set that should be used for printing the output data set
The default print option values defined on the Queue Definition screen are used when the user submitting a batch request does not supply those values on the Submit Batch Request screen or through a call to $BATCHOPT.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |