Services Batch Interface › About the 10.2 Services Batch Interface

About the 10.2 Services Batch Interface

Batch programs that require CA IDMS 10.2 services only can use the optional 10.2 services batch interface to access a later release.

Since only 10.2 features are available through this interface, later release features such as SYSIDMS parameters and SQL access are not supported through this interface.

This appendix describes the requirements for using the 10.2 services batch interface.

CA IDMS Installation

The 10.2 services batch interface requires two load modules supplied by the CA IDMS installation process:

• IDML
• B102STUB

Usage

Before you can make use of the interface, z/OS users must copy the B102STUB load module from the appropriate release level CAGJLOAD load library into a load library which will be included in their run-time STEPLIB concatenation and rename the module to IDMSB102.

z/VSE users need to copy the B102STUB.PHASE from their installed CA IDMS sub-library into a sub-library which will be included in their run-time LIBDEF concatenation, and then rename the module to IDMSB102.PHASE.

To use the 10.2 services batch interface, the following conditions must be met:

• The z/OS batch job JCL includes a STEPLIB that contains IDMSB102
• The z/VSE batch job JCL includes a LIBDEF concatenation which contains the IDMSB102 PHASE.
• The batch program is linked with either IDMS (Release 10.2) or IDML
• If the batch program has been relinked with a later version of the IDMS module, it must be relinked with either the 10.2 IDMS module or the IDML module

  Note: A link with IDMSINTB is supported for upward compatibility but is neither required nor recommended for using the 10.2 batch services interface.

• DBNAME must be specified. Since SYSIDMS parameters are not supported through this interface, you can do one of the following:
  • Modify the BIND RUN-UNIT statements in the program to specify the DBNAME parameter; for example:

    BIND RUN-UNIT DBNAME EMPDEMO.
    

  • Update the DBTABLE within the central version to utilize subschema mapping and default dbname parameters; for example:

    DBNAME *DEFAULT
      SUBSCHEMA EMPSS?? MAPS TO EMPSS?? USING DBNAME EMPDEMO;
    

    For more information about updating the DBTABLE, see the CA IDMS Database Administration Guide.

Batch Execution Considerations

Be aware of these considerations when preparing a program to use one of the batch interfaces:

• If the batch program is linked with either IDMS (Release 10.2) or IDML, and IDMSB102 is in a batch program JCL STEPLIB (z/OS) or LIBDEF (z/VSE), the 10.2 services batch interface is always used.
• If the batch program is linked with any later version of the IDMS module, the 10.2 services batch interface will never be used, even if IDMSB102 is in a batch program JCL STEPLIB (z/OS) or LIBDEF (z/VSE).
• To use a later version of the batch interface with an existing 10.2 program, be sure that IDMSB102 is not in a batch program JCL STEPLIB (z/OS) or LIBDEF (z/VSE).
• If the COBOL program has been compiled with the DYNAM option, you must rename the IDML module to IDMS and place it in a separate library. This library must be the first library after the STEPLIB concatenation.
• If signon security is in effect, a valid user ID must be provided for the batch user exit BTCIDXIT, which allows specification of the user ID to be checked by security. A sample BTCIDXIT may be found in the distribution source library.
• If the batch program is linked with either IDMS (Release 10.2) or IDML, then IDMSIN01 functions are not supported and the new items of the delivered IDMS-STATUS routine (dbkey, page group and dbkey format) are not displayed.