Copyright © Cloud Software Group, Inc. All Rights Reserved |
• version specifies the version of the procedure that you want to start a case of. Specify one of the following flags:
If version is not specified, the following default precedence order is used to select the version to use:
• -sN specifies the precedence order to be used to select the version of any sub-procedure started by the case. Specify one of the following values:
If the -sN flag is not specified, the following default precedence order is used to select the version to use:
Note: For more information about procedure versions see "Using Version Control" in TIBCO iProcess Modeler Procedure Management.
• -c specifies that the command returns the case number of the started case
• -e indicates that case data is embedded in the command file or input stream. See Command File Format.
• -a[D] datafile indicates that case data is supplied in abox format in the datafile. For more information about abox format, see "Using iProcess Abox Files" in TIBCO iProcess Modeler Integration Techniques.
• -P priority specifies the internal message queue priorities. For more information about message priorities, see "Message Prioritizing" in the appropriate TIBCO iProcess Engine (Database) Administrator’s Guide.
• node is the name of the host node, if the procedure is hosted remotely. Enter a hyphen (–) if the procedure is hosted locally.
• procname is the name of the procedure.
• stepname is the step at which to start the case. Enter a hyphen (–) to specify the default start step.
• casedesc is the case description of the case to be started.When all the START commands succeed, the return code from SWBATCH is SW_SUCCESS. If a SWBATCH command fails, SWBATCH will continue to execute the subsequent commands, and the return code will be the same as that of the first failure command.If you use a syntactically incorrect START command, the utility may not return an error message (in verbose mode) indicating that it could not process the command.
1. This example starts a case of procedure HIRING on the local node, with case description test1. No case data is supplied.
2. This example starts a case of procedure HIRING. Case data is supplied in the test1.txt file, which is deleted when the command has been processed.
3. This example starts a case of procedure HIRING on the local node, with case description app123. Case data for the FIRST and LAST (name) fields is embedded after the command, and terminated by the use of the STOP line. See Command File Format.
Copyright © Cloud Software Group, Inc. All Rights Reserved |