Information
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.

Setting Remote Trap


  1. On a blank CICS screen, type XPED and press Enter. The Code Debug CICS Primary Menu will be displayed.
  2. Select the session control option by typing 1 in the COMMAND field and pressing Enter. The Session Control Menu appears.

Session Control Menu

 ---------------------- SESSION CONTROL MENU (1) ------------------C024
COMMAND ===>
MODULE:          CSECT:


   1  LIST BREAKPOINTS    - Display breakpoints for a single program
   3  LIST ABENDS         - Display abends associated with the session
   4  TRACE SUMMARY       - Display program trace entrie
   5  SAVED TRAPS         - Display saved local or remote traps
   6  TRAP SUMMARY        - Display local or remote traps
   7  INTERCEPT SUMMARY   - Display active intercepts
   8  STORAGE PROTECTION  - Set storage protection options
   9  USER LABELS         - Define user labels
   M  MONITOR SUMMARY     - Display active MONITOR entries
   N  NEWCOPY PROGRAMS    - NEWCOPY (phasein) programs
   P  RESOURCE SUMMARY    - Display count of breakpoints and keeps

3. Type 6 in the COMMAND field and press Enter. The Trap Summary screen (1.6) appears. This screen is used to specify the terminals to be monitored for abends and/or breakpoints.

The display on your screen will show an entry for your terminal. When the XPED and XPRT transactions are used, an abend trap is automatically set for the terminal on which these transactions are entered.

In this example, you know the transaction that is causing the problem. Set an abend trap for a remote terminal.

4. Type ALL in the NETNAME and TERM fields.

5. Type XCCC in the TRAN field.

6. Type an asterisk (*) in the PROGRAM field and press Enter to specify that all programs involved in transaction XCCC are monitored.

In following figure, for example, three traps have been set:

–For any transaction entered from terminal A011.

–For XCCC transaction regardless of its origin. This means that all transactions and programs executed are monitored for abends, as well as any programs involved in the transaction XCCC. If abend situations occur, the information is displayed on your terminal.

–The third trap is an enhanced trap. If an abend occurs in any program beginning with CWDEM running at terminal A999, and the initial commarea associated with the task contains the string “test” starting in position 16 for a length of 4, the information is displayed on your terminal. Also, any breakpoints in programs beginning with CWDEM will be taken if the initial commarea meets the criteria above and the transaction was started on terminal A999.

7. Press Clear to return to a blank CICS screen.

Setting a Trap on the Trap Summary Screen (1.6)

 ------------------------------- TRAP SUMMARY (1.6) -----------------------C024
COMMAND ===>                                                   SCROLL ===> CSR
MODULE:          CSECT:
MODE: TERM   (IP TERM or ALL)     NO IP TRAPS                     ENTRY 000001
LINE COMMANDS:   A (After)   B (Before)   C (Copy)   D (Delete)   I (Insert)
                 M (Move)    S (Save)

 CMD   USERID     NETNAME     TERM     TRAN     PROGRAM   TRAP ABEND
       IF ...................... TRAP CONDITION .......................
 ----------------------------------------------------------------------
  _    ********   ********    A011     ****     ********     YES
       IF
  _    ********   ********    ****     XCCC     ********     YES
       IF
  _    ********   ********    A999     ****     CWDEM***     YES
       IF INITCOMM(16:4) = T'TEST'
  _    ________   ________    ____     ____     ________     ___
       IF

 

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

BMC AMI DevX Code Debug for CICS 17.02