Viewing a transaction trace


Each transaction might comprise several messages.

In the Transaction Trace panel, each line in the table represents a single message. The type of message is indicated by the code in the Type column. Codes from input messages from the client begin with the greater than (>) symbol. Codes for output messages to the client begin with the less than (<) symbol.

(PTFs BQQ3969 and BQQ3973 applied)

In the Transaction Trace panel, you can modify the Start Date Time field to start your transaction trace search from a different date and time. Also, the Records Count field allows you to enter a value from 1 through 9999 to indicate the maximum number of transaction trace entries to process.

File  Display  Help                                
------------------------------------------------------------------------------
                               Transaction Trace                 Row 1 from 18
                                     Commands: Locate Select SORT REFresh RESet
Start Date Time 10172018 : 040705 (MMDDYYYY:HHMMSS)         Records Count 100_  
Type 'S' to Display report. Then press Enter.                                  
A Timestamp         Type Client   Userid   Exit     DataStor Transact Response
        Filters. .  ____ ________ ________ ________ ________ ________ Time(sec)
_ 18/10/16 05:25:11 >CM1 BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART              
_ 18/10/16 05:25:12 <    BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART              
_ 18/10/16 05:25:12 >CM1 BOLAXD1  BOLAXD1  HWSSMPL0 TEST     PART              
_ 18/10/16 05:25:12 <    BOLAXD1  BOLAXD1  HWSSMPL0 TEST     PART      0.010893
_ 18/10/16 05:25:13 >CM1 BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART              
_ 18/10/16 05:25:13 <    BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART      0.005791
_ 18/10/16 05:25:13 >CM1 BOLAXD1  BOLAXD1  HWSSMPL0 TEST     PART              
_ 18/10/16 05:25:13 <    BOLAXD1  BOLAXD1  HWSSMPL0 TEST     PART      0.005519
_ 18/10/16 05:25:14 >CM1 BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART              
_ 18/10/16 05:25:14 <    BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART      0.006248
_ 18/10/16 05:25:14 >CM1 BOLAXD1  BOLAXD1  HWSSMPL0 TEST     PART              
_ 18/10/16 05:25:14 <    BOLAXD1  BOLAXD1  HWSSMPL0 TEST     PART      0.005755
_ 18/10/16 05:25:14 >CM1 BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART              
_ 18/10/16 05:25:14 <    BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART      0.005485
_ 18/10/16 05:25:15 >CM1 BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART              
_ 18/10/16 05:25:15 <    BOLAXD1  BOLAXD1  HWSSMPL0 AD5R     PART      0.006056
                                                                              
Command ===>_________________________________________________ Scroll ===> CSR  

To filter a display

To filter on a specific client, such as SYM35M02, type a unique portion of the client name (SYM35) under the Client heading and press Enter. Only entries that begin with SYM35 are displayed.

Note

Filtering criteria remain in effect until you delete the criteria or issue the RESET command.

To display a report

  1. Type an S next to each timestamp that you want included in the report.You can scroll to select more time stamps.

    The following figure shows sample report #1:

    Commands: ROUTe SAVE                                                            
    ******************************** Top of Data ***********************************
    READ input message from client Port=3545 IP=172.17.8.68 (MVSSYSMV.BMC.COM)       
    Time: _ 06/03/10 15:11:00   Length: 500  Time in exit: 0.000046 seconds          
    *******************************************************************************  
    * IRM Header                                           Exit Results              
    * MsgID:    '*SAMPLE*'                                 Output Length:    944    
    * ClientID:  SYM35M02   Protocol:    CM1 Send-Commit   Clientid:    SYM35M02    
    * DataStor:  R61P       Confirm:     No                Return Code:        0    
    * Group:                Socket type: Transaction       Reason Code:        0    
    * UserID:    UserID     Flow type:   Default                                    
    * TranCode:  PART       Return MFS:  No                User Exit RC:     N/A    
    * LTERM:                Purge:       No                Router RC:          0    
    * Timer:      secs.     Syncpt:      No                Governor RC:        0    
    *******************************************************************************  
    * Values used for affinity checking                 Router results               
    * TranCode:  PART       MsgID:   '*SAMPLE*'         First DataStor:   R81I      
    * User:      UserID     Port:     11255             Affinity matched: None.     
    * Group:                DataStor: R61P              # matching DS:    135       
    * ClientID:  SYM35M02   IP Addr:  xxx.xxx.xxx.xxx   Final DataStor:   R81I      
    *******************************************************************************
  2. To view more of the report, page down.

    The following figure shows sample report #2:

     >CM1 Message from Client (truncated ----- EBCDIC -----  
       0. 000001F4 00500000 5CE2C1D4 D7D3C55C *...4.&..*SAMPLE**  
      10. 00000000 00000000 E2E8D4F3 F5D4F0F2 *........SYM35M02*  
      20. 00200040 61C4C9E2 40404040 D9F6F1D7 *... PART    R61P*  
      30. 40404040 40404040 40404040 D9C9C8D1 *            RIHJ*  
      40. C5D94040 40404040 40404040 5C5C5C5C *ER          *****  
      50. 5C5C5C5C 019C0000 61C4C9E2 40D3E3C5 *****....PART LTE*  
      60. D9D440D9 F65C4040 40404040 40404040 *RM R6*          *  
      70. 40404040 40404040 40404040 40404040 *                *  
     <<<< Above line repeats 5 times >>>>                         
      D0. 40404040 40404040 40404040          *            *      
                                                                 
          ----Message to IMS (truncated)----- ----- EBCDIC -----  
       0. 01400000 00000000 00000000 0000A0F0 *. .............0*  
      10. 00000000 00000000 00000000 00010000 *................*  
      20. 00480020 00000000 00000000 00000000 *................*  
      30. 00000000 00000000 00000000 00000000 *................*  
      40. 00000000 00000000 00000000 00000000 *................*  
      50. 00000000 00000000 00000000 00004040 *..............  *  
      60. 40404040 40400000 006AC614 0902D9C9 *      ...F...RI*  
      70. C8D1C5D9 40400903 40404040 40404040 *HJER  ..        *  
      80. 00000000 00000000 00000000 00000000 *................*
    <<<< Above line repeats 4 times >>>>                         
     D0. 00000100 0000D9F8 F1C94040          *......R81I  *
  3. To view the rest of the report, page down.

    The following figure shows sample report #3:

     IMS Connect control blocks:                                    
          -------------HWSEXPRM-------------- ----- EBCDIC -----   
       0. D9C5C1C4 22068AE4 213EB5A0 22062080 *READ...U........*   
      10. 000001F4 22063040 00000426 80000000 *...4... ........*   
      20. D9C9C8D1 C5D9F240 00020DD9 AC110844 *RIHJER2 ...R....*   
                                                                  
          -----------SVT 21364688------------ ----- EBCDIC -----   
       0. E2E5E340 F1F1F2F5 F5404040 C4C5D3C4 *SVT 11255   DELD*   
      10. E4D4D4E8 BE42E51B D6198DC1 00000000 *UMMY..V.O..A....*   
      20. 21368E80 21D3C4A0 00019488 21D48000 *.....LD...mh.M..*   
      30. 21D22000 D9C5C3E5 00800000 00000000 *.K..RECV........*   
      40. 00000000 00000000 00000000 00000000 *................*   
      50. 213806B0 BE42DE9D 00000000 00000000 *................*   
      60. 21D1D270 00000000 00000000 00000000 *.JK.............*   
      70. BE42E51B D619E341 00000000 00000000 *..V.O.T.........*   
      80. BE42E51B D619F181                   *..V.O.1a*           
                                                                  
          --------------CTTOKEN-------------- ----- EBCDIC -----   
       0. E3C3D7C3 21D22000 00000000 21451890 *TCPC.K..........*   
      10. 21D2F000 A130A018 2BF70000 0004A000 *.K0.~....7......*   
      20. 00000000 00020DD9 AC110844 00000000 *.......R........*   
      30. 00000000 C8E6E2E2 D4D7D3F0 21476180 *....HWSSMPL0../.*   
      40. 00000426                            *....*

    To interpret trace data, see Trace-and-Journal-commands.

To change HEX dump format

  1. From the action menu, select Display=> Options.
  2. Page down to HEX dump format.
  3. Type the number of the format to use.

To print or save a report

Use command line commands ROUTE and SAVE.

 

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