1.1.2.3 Description

DFSRRC00 is used to activate the ARTIBMP/ARTIBMPT server which waits for DFSRRC00 input . The DFSRRC00 parameter is a string passed from the script converted by workbench from JCL. Currently, only 5 sub-parameters contained in the string are supported : “BMP, ${MBR}, ${PSB}, ${IN}, ${CKPTID}”.The remaining sub-parameters in the string are ignored.

If there is no IMS server error, no abend, and the user program has not crashed, the user program return code is the DFSRRC00 return code.

The DFSRRC00 client name format is as follows: “${MBR}-DFSRRC00”. You can use tmadmin to observe currently running BATCH programs.

At the start/end of a transaction/program, a trace line is added to the program invocation log file in the following format: “transaction name, program name, Sstart time, Eend time, group id, server id”

Note:

(when used, "-" indicates an empty value).

Two duplicated FML32 fields (IMS_BMP_APPNAME_ROUTE and IMS_JOB_NAME_ROUTE) could be used as routing fields when DFSRRC00 calls the BMP service. So you could route a specific application program or Batch job to a specific BMP server group. These two FML32 fields are defined in $IMSDIR/include/ROUTEFML.

Note:

16 additional parameters are reserved for future use; currently, they are not supported.

When Oracle Tuxedo security is enabled, environment variable ARTIMS_PROFILE should be used to specify the security profile used for authentication. The value of ARTIMS_PROFILE is the name of the security profile. Two types of security profile are supported: Oracle Wallet and profile created by genimsprofile.

For Oracle Wallet profile:

  • you need to create an Oracle Wallet using Oracle utility "orapki" or "mkstore" in advance. See Authentication Configuration in the Oracle Tuxedo Application Runtime for IMS User Guide for more details.
  • Oracle wallet profile name is prefixed with "file:" string and followed by a directory name pointing to the location of an Oracle Wallet. For example:export ARTIMS_PROFILE="file:/path/to/wallet"