|
View previous topic :: View next topic
|
| Author |
Message |
srajendran2
New User
Joined: 13 May 2008
Posts: 56
Location: Chennai
|
|
| Back to top |
|
 |
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Googling connect direct debug mode returned about 9,270,000 hits and one of the first (for me) was www-01.ibm.com/support/docview.wss?uid=swg21544213 which states
| Quote: |
The "debug" trace is the mechanism for capturing various types of activity within Connect:Direct OS/390 as well as between it and other nodes and operating system components. It can be initiated to trace activity for a single process with a single remote node a single C /Plex server or the entire Connect:Direct region or plex. Typically a bit string of 8C00006E captures what is required by support to allow them to diagnose a problem. This bit string should be used unless otherwise instructed.
To trace a single process specify the DEBUG keyword parameter on the PROCESS statement similarly to below:
MYPROC PROCESS SNODE=remote_node DEBUG=8C00006E |
So DEBUG=02000000 will work for what you want. |
|
| Back to top |
|
|
srajendran2
New User
Joined: 13 May 2008
Posts: 56
Location: Chennai
|
|
|
|
| Thank you for your reply. I will try the option and let you know the results. |
|
| Back to top |
|
|
srajendran2
New User
Joined: 13 May 2008
Posts: 56
Location: Chennai
|
|
|
|
| I used DEBUG=02000000, the trace information was present in APITRACE & NDMCMDS. So DEBUG=02000000 worked. |
|
| Back to top |
|
|
|
|
