To use the trace for problem determination, you must start the following:
When you start the GTF, specify the USRP option. You are prompted to enter a list of event identifiers (EIDs). The EIDs used by WebSphere MQ are:
Sometimes, if an error occurs that you cannot solve yourself, you might be asked by your IBM(R) support center to supply other, internal, trace information for them to analyze. The additional type of trace is:
You can also use the JOBNAMEP option, specifying the batch, CICS(R), IMS(TM), or TSO job name, to limit the trace output to specific jobs. Figure 11 illustrates sample startup for the GTF, specifying the four EIDs, and a jobname. The lines shown in bold type like this are the commands that you enter at the console; the other lines are prompts and responses.
For more information about starting the GTF trace, see the MVS Diagnosis: Tools and Service Aids manual.
START GTFxx.yy £HASP100 GTFxx.yy ON STCINRDR £HASP373 GTFxx.yy STARTED *01 AHL100A SPECIFY TRACE OPTIONS R 01,TRACE=JOBNAMEP,USRP TRACE=JOBNAMEP,USRP IEE600I REPLY TO 01 IS;TRACE=JOBNAMEP,USRP *02 ALH101A SPECIFY TRACE EVENT KEYWORDS - JOBNAME=,USR= R 02,JOBNAME=(xxxxMSTR,xxxxCHIN,zzzzzzzz),USR=(5E9,5EA,5EE) JOBNAME=(xxxxMSTR,xxxxCHIN,zzzzzzzz),USR=(5E9,5EA,5EE) IEE600I REPLY TO 02 IS;JOBNAME=(xxxxMSTR,xxxxCHIN,zzzzzzzz),USR=(5E9,5EA,5EE) *03 ALH102A CONTINUE TRACE DEFINITION OR REPLY END R 03,END END IEE600I REPLY TO 03 IS;END AHL103I TRACE OPTIONS SELECTED-USR=(5E9,5EA,5EE) AHL103I JOBNAME=(xxxxMSTR,xxxxCHIN,zzzzzzzz) *04 AHL125A RESPECIFY TRACE OPTIONS OR REPLY U R 04,U U IEE600I REPLY TO 04 IS;U AHL031I GTF INITIALIZATION COMPLETE where: xx is the name of the GTF procedure to use, and yy is an identifier for this occurrence of GTF trace. xxxx is the name of the queue manager and zzzzzzzz is a batch job or CICS region name. Up to 5 job names can be listed.
When using GTF, specify the primary job name (CHINIT, CICS, or batch) in addition to the queue manager name (xxxxMSTR).
Use the START TRACE command, specifying type GLOBAL to start writing WebSphere MQ records to the GTF. To define the events that you want to produce trace data for, use one or more of the following classes:
CLASS | Event traced |
---|---|
2 | Record the MQI call and MQI parameters when a completion code other than MQRC_NONE is detected. |
3 | Record the MQI call and MQI parameters on entry to and exit from the queue manager. |
After the trace has started, you can display information about, alter the properties of, and stop, the trace with the following commands:
To use any of the trace commands, you must have one of the following:
For information about these commands, see the WebSphere MQ Script (MQSC) Command Reference manual.
When you stop the GTF, you must specify the additional identifier (yy) used at startup. Figure 12 illustrates a sample stop command for the GTF. The commands shown in bold type like this are the commands that you enter at the console.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsaq0388 |