Re: Tracing DRDA server

Scott

On the iSeries you could run a communications trace - this could get you the 
exact bytes coming and going between the iSeries and whatever remote system is 
involved. Then you have your evidence. STRCMNTRC can be used - there are others 
for ending the trace, etc. GO CMDTRC will show them to you, as well as a whole 
bunch or unrelated commands. I find that SST is an easier interface for this - 
there is a option there to handle all this, but you have to be authorized.

Then you get to look at spooled files that might be cryptic (no might about it 
- definitely cryptic) but the info is there.

HTH
Vern


-------------- Original message -------------- 
From: Scott A Schollenberger <SASchollenberger@xxxxxxxxxxxx> 

> Can anyone point me in the direction of information regarding 
> the ability to trace the DRDA server? We have an application from 
> a partner company that sends SQL requests (UPDATE/INSERT) via 
> DB2 Connect to our (or our clients) iSeries. 
> 
> We are in a situation of trying to prove to the partner that they 
> are sending nulls on an UPDATE statement for a table that 
> doesn't accept nulls in this certain field. 
> 
> The QRWTSRVR joblog shows a data mapping error with 
> error code 20 which indicates a null received for the field, 
> but more "proof" is needed. 
> 
> Thanks. 
> ---------------------- 
> 
> Scott A. Schollenberger 
> Director, R&D 
> TENEX Systems, a division of Harris Computer Systems 
> 2011 Renaissance Blvd., Suite 100 
> King of Prussia, PA 19406 
> Phone: 610-239-9988 Ext. 305 
> Fax: 610-239-9995 
> E-mail: saschollenberger@xxxxxxxxxxxx 
> Web: www.tenexsys.com 
> 
> IBM Certified Specialist - eServer i5 iSeries Technical Solutions 
> Implementer V5R3 
> 
> CONFIDENTIALITY NOTICE: This email message, including any attachments, is 
> for the sole use of the intended recipient(s) and contains confidential and 
> privileged information. Any unauthorized review, use, disclosure or 
> distribution is prohibited. If you are not the intended recipient, please 
> contact the sender by reply email and destroy all copies of the original 
> message. 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>