Building IMS (BMP or MPP) applications

 

If you are building batch DL/I programs, see Building z/OS batch applications. To build other applications that run under IMS™ (either as a BMP or an MPP), create JCL that performs these tasks:

  1. Compile (or assemble) the program to produce object code. The JCL for your compilation must include SYSLIB statements that make the product data definition files available to the compiler. The data definitions are supplied in the following WebSphere MQ for z/OS libraries:

    • For COBOL, thlqual.SCSQCOBC

    • For assembler language, thlqual.SCSQMACS

    • For C, thlqual.SCSQC370

    • For PL/I, thlqual.SCSQPLIC

  2. For a C application, prelink the object module created in step 1.

  3. Link-edit the object code created in step 1 (or step 2 for a C/370 application) to produce a load module:

    1. Include the IMS language interface module (DFSLI000).

    2. Include the WebSphere MQ for z/OS IMS stub program (CSQQSTUB). Figure 1 shows fragments of JCL to do this. The stub is language independent and is supplied in library thlqual.SCSQLOAD.

      If you are using COBOL, select the NODYNAM compiler option to enable the linkage editor to resolve references to CSQQSTUB unless you intend to use dynamic linking as described in Dynamically calling the WebSphere MQ stub.

  4. Store the load module in an application load library.

Figure 1. Fragments of JCL to link-edit the object module in the IMS environment 
⋮
//*
//* WEBSPHERE MQ FOR Z/OS LIBRARY CONTAINING IMS STUB
//*
//CSQSTUB   DD  DSN=++HLQ.MQM100++.SCSQLOAD,DISP=SHR
//*
⋮
//LKED.SYSIN DD *
  INCLUDE CSQSTUB(CSQQSTUB)
⋮
/*

Before you run an IMS program, your system administrator must define it to IMS as a WebSphere MQ program and transaction: we can then run it in the usual way.

 

Parent topic:

Preparing your program to run


fg16800_