Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Milestone 8: Configuring IMS/DB support


If you are installing Code Debug TSO and Code Debug IMS with IMS/DB support, perform this milestone to do database definition (DBD) and program specification block (PSB) gens for the sample programs.

If your site is not using—and does not plan to use—IMS/DB support, go to Milestone 9: Configure IMS/DC Support.

Roles Involved

IMS DBA is required for this milestone.

Tasks

Complete the following task to enable IMS/DB support.

Task 8.1 Create Input and Database Files

  1. Use the XTUPDATE macro to configure the JCL in SLXTINST(JCL006). “Stretched” members BTSIN and BTSINX will be placed in SLXTSAMP.
    1. If required, replace the VOL=SER=DDDDDD statement on the SYSUT2 DD with a valid VOL=SER and uncomment the card.
  2. Submit the job. It should complete with a return code of 0.

Task 8.2 DBD and PSB Gens

  1. Using your site’s standard JCL for running a DBDGEN, point to SLXTSAMP(XPEDDBDG) as the DBD source. Run this job and verify that the XPGSAMD DBD is correctly created.
  2. Using your site’s standard JCL for running a PSBGEN, generate the appropriate PSBs based on the Code Debug TSO options for which your site is licensed:

    SLXTSAMP Members for PSBGENs

    Language

    PSB

    PSB Source
    SLXTSAMP Member

    COBOL or Assembler

    TRIIMSM

    PSBIMSM

    PL/I

    TRIIMSMP

    PSBIMSMP

    C

    TRIIMSMC

    PSBIMSMC

  3. Copy SLXTSAMP(TRIDATA) to a sequential data set with RECFM=F, LRECL=80, and BLKSIZE=80.

Task 8.3 IMS/DB Installation Verification

To verify that the IMS/DB support is properly customized, the Code Debug IVP programs listed in the following table are used. The base product has four sets of IVP programs, one set for each programming language supported by Code Debug TSO and Code Debug IMS.

IMS/DB IVP Programs

Language

Program/SLXTSAMP Member

COBOL

TRIIMSM, TRIRPT, and TRITST
(TRIIMSM calls TRITST and TRIRPT)

PL/I

TRIIMSMP, TRIRPTP, and TRITSTP
(TRIIMSMP calls TRITSTP and TRIRPT)

ASSEMBLER

TRIIMSMA, TRIRPTA. and TRITSTA
(TRIIMSMA calls TRITSTA and TRIRPTA)

C

TRIIMSMC, TRIRPTC, and TRITSTC
(TRIIMSMC calls TRITSTC and TRIRPTC)

Preparations for Testing the IMS/DB IVPs

The programs in above table  are contained in the SLXTSAMP library. Use the specific Language Processor (LP) to compile or assemble the sample programs in the listed order (TRITST*, then TRIRPT* followed by TRIIMSM*). Some main routines statically link to subroutines higher in the list.

See to the BMC AMI Common Shared Services User/Reference Guide for information on using the correct LP (COBOL, PL/I, Assembler, or C).

Optionally, you can access the online BMC AMI Common Shared Services Compile Facility by selecting option 1 (PREPARE) from the Code Debug TSO Primary Menu.

  • The COBOL programs must be link-edited with a specific entry point:
    • If you compile using the PREPARE option, use the following for the SYSLIN Control field of the LINKEDIT Step panel of the compile:
      SYSLIN Control Statements:
      ===> ENTRY DLITCBL

    • If you compile outside of Code Debug, include the following entry statement in the LKED step:
      //LKED.SYSLIN DD *
      ENTRY DLITCBL
  • The SYSLMOD output from these compiles should not be directed to the Code Debug TSO LOADLIB library, but to a data set available to your application programmers for training sessions. For example, you could create a data set named CPWR.XT.TRAINLIB.
  • To verify that the compile was successful and that a source listing member was created, check the listing under the DDNAME CWPERRM for a message similar to the following:
    LISTING pgmname DATED nn/nn/nn AT nn.nn.nn SUCCESSFULLY WRITTEN TO CWPDDIO

Initiating the Verification Test Session

  1. Select 1 (PREPARE) from the Code Debug TSO Primary Menu.
  2. Select 4 (EDIT ALLOCATION LIST) from the Program Preparation Menu.
  3. In the Other Partitioned or Sequential data set area of the Edit File List screen, type 'hlq.SLXTSAMP(FAUIMSM)' and press Enter. The Edit File List 1 figure is displayed.
  4. On the first line of the allocation list, type the DDNAME of INFILE. In the DSNAME field, enter the name of the sequential, non-blocked copy of the SLXTSAMP(TRIDATA) that you created in DBD and PSB Gens. Remember to enclose the name in single quotes if it is fully qualified.
  5. On the next two lines, enter OUTFILE and SYSOUT in the DDNAME field and TERM in the DSNAME field.
  6. Press PF3. If a create screen is displayed, the wrong DSN name was entered. Check your input and try again. If all input is correct, the Edit File List entry screen is displayed again with the short message Allocation List Saved.
  7. Press PF4 (RETURN) to return to the Code Debug TSO Primary Menu.
  8. Select 2 (TSO) from the Code Debug TSO Primary Menu. The Standard test screen is displayed.
  9. Type SETUP and press Enter. The Setup Menu is displayed.
  10. Select 0 (ENVIRONMENT) from the Setup Menu. The Environments Menu is displayed.
  11. Select 3 (IMS) from the Environments Menu. The IMS Setup Menu is displayed.
  12. Select 1 (LOADLIBS) from the Setup Menu.
  13. On the Load Module Libraries screen, specify the application load library that contains the language-specific IVP load module. Also specify your Language Environment (LE) run-time library (usually CEE.SCEERUN).
  14. Press Enter.
  15. If the IMS libraries you are using to test the program were not established as site-wide defaults, select I (IMS) from the Setup Menu. This lets you override the following DDNAMEs for your test only:
    IMS    DFSVSAMP  PARMS     PROCLIB
    IMSACB IEFRDER   DFSRESLB  SYSPUNCH
  16. After all your IMS data sets are specified, enter END (or press PF3) until you return to the IMS test screen.
  17. Specify the language-specific program in the Program ===> field.
  18. Specify the language-specific PSB in the PSB ===> field.
  19. Program Type should be DLI.
  20. PARM Passing Option should be STD.
  21. In the File List/JCL Member ===> field, enter the data set/member name of the FAU
     ('cpwr.xt.SLXTSAMP(FAUIMSM)').
  22. Press Enter to begin the Code Debug TSO debugging session. The message area contains the lines Allocating User Datasets, then Allocating CODE DEBUG TSO Datasets. On a blank screen, the message Entering CODE DEBUG TSO Test Environment is displayed along with information about the test. Then the source for the TRIMAIN program is displayed.
  23.  Type GO 1 on the COMMAND line and press Enter. The execution arrow will be on the next statement. The execution status message indicates that you are BEFORE program-name:line-number.
  24. Press PF12 (GO). The Triangle Report is written to the screen.
  25. Press Enter until you return to the Source screen with a TEST COMPLETED message, indicating that your program executed successfully.
  26. Press PF4 (EXIT) to exit the test session.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*