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 11: Configuring BTS support


If you are installing Code Debug TSO and Code Debug IMS with BTS support, you must do program specification block (PSB) gens for the sample programs.

If your site is not using—and does not plan to use—BTS support, go to Milestone-12-Enabling-high-performance-breakpointing.

Roles Involved

The following person is required for this milestone:

Important

IMS DBA

Tasks

Complete the following tasks to configure BTS support.

Task 11.1 PSB Gens

If you installed IMD/DC support in Milestone-9-Configuring-IMS-DC-support and have already generated PSBs for XPEDTRAN, XPEDTRNP, XPEDTRNA, and XPEDTRNC, skip ahead to BTS Installation Verification.

Create the PSBs required for the BTS sample verification programs.

  1. Perform PSBGENs for the Code Debug IMS programs using your site’s standard PSBGEN utility JCL with the corresponding sample library SLXTSAMP members as input.

    SLXTSAMP Members for PSBGENs

    PSBGENs

    PSB Source
    SLXTSAMP Member

    ADSIM001

    IMS003I1

    ADSIM013

    IMS003I2

    XPSTOP

    IMS003I3

    ADSIM016

    IMS003I4

  2. Perform the PSBGENs applicable to the Code Debug TSO options for which your site is licensed.

    PSBGENs for Licensed Options

    Language

    PSBGENs

    PSB Source
    SLXTSAMP Member

    COBOL

    XPEDTRAN

    PSBDTRAN

    PL/I

    XPEDTRNP

    PSBDTRNP

    C

    XPEDTRNC

    PSBDTRNC

    Assembler

    XPEDTRNA

    PSBDTRNA

Task 11.2 BTS Installation Verification

To verify that the BTS support is properly customized, the Code Debug IVP programs listed in the following table are used.

BTS IVP Programs

Language

Program/SAMPLIB Member

COBOL

XPEDTRAN

PL/I

XPEDTRNP

ASSEMBLER

XPEDTRNA

C

XPEDTRNC

Preparations for Testing the BTS 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.

See to the BMC AMI Common Shared Services User/Reference Space 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 program 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 2 (TSO) from the Code Debug TSO Primary Menu.
  2. Select 4 (BTS) from the Environments Menu.
  3. Type SETUP and press Enter.
  4. Select 1 (LOADLIBS) from the Setup Menu.
  5. 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).
  6. Press Enter.
  7. 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  MONITOR   PARMS    PROCLIB
    IMSACB IEFRDER   DFSRESLB  SYSPUNCH
  8. After all your IMS data sets are specified, enter END (or press PF3) until you return to the BTS test screen.
  9. Specify the language-specific program in the Program ===> field.
  10. In the BTSIN ===> field, type 'CPWR.XT.SLXTSAMP(BTSIN)'. (Change the high-level node to your standard Code Debug TSO qualifier.)
  11. Program Type should be DLI.
  12. PARM Passing Option should be STD.
  13. Press Enter to begin the Code Debug TSO debugging session. The screen clears, then displays several lines of BTSOUT data, concluding with the prompt:
    ENTER BTS COMMAND OR /FORMAT OR /*
  14. Type program-name THIS IS A TEST and press Enter. You will see additional BTS messages, then three asterisks (***).
  15. Press Enter and the source for the program (XPEDTR*) is displayed.
  16. 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.
  17. Press PF12 (GO). On the bottom of the screen and continuing onto the next screen, you receive all your standard BTS output.
  18. Press Enter until the program source is once again displayed.
  19. Press PF12 (GO). You will receive more BTS messages.
  20. Press Enter. This message will be displayed:
    NON-CONVERSATIONAL INPUT MESSAGE FOLLOWS   THIS IS A TEST
  21.  Press Enter to receive the BTS message:
    ENTER BTS COMMAND OR /FORMAT OR /*
  22. Type /* and press Enter.
  23. Press Enter to return to the Code Debug BTS menu.


 

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