IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Connect Direct - using DEBUG=TRACE Bits


IBM Mainframe Forums -> All Other Mainframe Topics
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
srajendran2

New User


Joined: 13 May 2008
Posts: 56
Location: Chennai

PostPosted: Tue May 08, 2018 3:08 am
Reply with quote

Hi,

My COBOL program calls DGADCHLA API to SUBMIT a file transmission. I would like to enable API trace for specific file transmissions with long file names.

I have gone through the information given in the below link

www.ibm.com/support/knowledgecenter/en/CD_PROC_LANG/com.ibm.help.cdprocstmtsparams.doc/cdproc_stmt_zos_Process_Parameters.html

Could someone please help me understand what do they mean by "Specify these bits using hexidecimal notation."? can't I just specify DEBUG=02000000?

Also I understand that RADBDD07 DD name should be coded in JCL to get the trace information. should I also code APITRACE DDNAME? [/url]
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2475
Location: Netherlands, Amstelveen

PostPosted: Tue May 08, 2018 1:07 pm
Reply with quote

DD-statements : www.ibm.com/support/knowledgecenter/en/SSFGBN_5.1.1/com.ibm.help.cdzos.admin.doc/ZOS_DD_Statements_in_Startup_JCL.html
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8569
Location: Dubuque, Iowa, USA

PostPosted: Tue May 08, 2018 6:44 pm
Reply with quote

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 Cicon_biggrin.gif/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
View user's profile Send private message
srajendran2

New User


Joined: 13 May 2008
Posts: 56
Location: Chennai

PostPosted: Tue May 08, 2018 8:19 pm
Reply with quote

Thank you for your reply. I will try the option and let you know the results.
Back to top
View user's profile Send private message
srajendran2

New User


Joined: 13 May 2008
Posts: 56
Location: Chennai

PostPosted: Thu May 10, 2018 12:57 am
Reply with quote

I used DEBUG=02000000, the trace information was present in APITRACE & NDMCMDS. So DEBUG=02000000 worked.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> All Other Mainframe Topics

 


Similar Topics
Topic Forum Replies
No new posts ZOS Connect EE Vs z/OS client web ena... All Other Mainframe Topics 0
No new posts DEBUG COMMENT command not adding to log IBM Tools 1
No new posts Debug set up for COBOL module but ope... IBM Tools 1
No new posts KSDS direct READ clause after READ NEXT JCL & VSAM 0
No new posts Issue in NDM : Connect Direct All Other Mainframe Topics 0
Search our Forums:

Back to Top