Customer reports no data when they hyperlink from CHISTDD to BMC AMI Ops Monitor for DB2 TRLTRAC view: BBMXV325I There is no data that satisfies your request |
The following online help text can be found by pressing PF1 on the Subsystem ID field on the CHISTDD view. The hyperlink from MVCICS task performance history into MVDB2 to examine the thread history goes to the TRLTRAC view to display the thread information from the MVDB2DC trace. It uses the CICS to DB2 correlator in the form network.luname.uow which is passed to DB2 from CICS. For this hyperlink to work, certain conditions must be met. o The MVDB2DC trace must be running for the target DB2 subsystem. o The DB2 Connection must be defined with the ACCOUNTREC attribute set to UOW or TASK. o The DB2 Entry for the transaction must be defined with the ACCOUNTREC attribute set to UOW or TASK. The hyperlink sets the time span for searching the MVDB2DC trace data from the start of the CICS task to approximately 15 minutes after the task has ended. If the task is very recent, the MVDB2DC trace data may not yet be available. If the customer has verified the conditions documented above, the following can be done to assist in the troubleshooting of no data by determining exactly what data is being passed from CHISTDD to TRLTRAC: 1. Set the context to the SSID of the PAS and go to the DUMP view. Enter BBKKANC to the right of Block/Table Name and press Enter. Change offset x'38' circled below from '0' (zero) to '4' and use the 'Z' (zap) line command and press Enter. Please note that in order to do these updates in the DUMP view, your UBBPARM member BBIISP00 must have: PKZAP=YES In addition, the user must have authority to this resource: BBM.&PRODUCT.&SERVER.&INTTABLE.&INTACTION.OA 2. You will see a confirmation screen like this: 3. Change the 'N' to 'Y' and press Enter. You will then see a screen like this: 4. Recreate your issue - try the hyperlink from CHISTDD to TRLTRAC. 5. Go to the BBI Journal and look for a message like this: BBK0T6EB DB2 - {BBMTH1P0|CWACTION} 00160 CONTEXT SYSNAME:SJSC MVDB2; ; PUTS SZ3 DA0C927BCC9C4E22;PUTS DMRDUR 0000035A4F8B34AE;PUTS SZ19 'U .TCPC0078.C927BCCA2360' 6. Print and send the active BBI Journal to BMC. Also send a screen print of the CHISTD view for the corresponding task. 7. Go back to the DUMP view (set context to PAS) and reverse your update from above - change 40000000 back to 00000000. It is very important you change this back because otherwise you will have many diagnostics messages coming out. |