>On Wednesday, 06/14/2006 at 05:44 AST, Craig Dudley ><[EMAIL PROTECTED]> wrote: >> Hi, >> I am trying to track down a DTCPIN0005E problem. During the debugging >> I did a TRACE IUCV followed by a PING xxx.xxx.xxx.xxx (DEBUG. >> >> The trace showed: >> >> trace iucv >> Ready; T=0.01/0.01 14:17:59 >> >> ping xxx.xxx.xxx.xxx (debug >> PING: Debugging Enabled >> -> 010B735E IUCV B2F0A000 00EDE2B0 CC 0 DCLBFR >> B >> -> 010B84C6 IUCV B2F0A000 00D07118 CC 1 IUCVCONN >> B >> -> 01059B2E IUCV B2F00000 00000000 CC 0 RTRVBFR >> B >> DTCPIN0005E Unable to obtain STACK buffer size: EDC5122I Input/output >> error. >> Ready(00008); T=0.06/0.07 14:18:11 > Alan,
>You can find all the reasons for CC=1 on IUCV CONNECT in the CP >Programming Services book. "TRACE IUCV CMD D T0.40;baseF" will display >the output IPARML on the CONNECT. Using the book, locate the IPRCODE, >detailing why the CONNECT failed. > I did and found it couldn't find the virtual machine of my 2nd stack. Further investigation showed my TCPIPUSERID value was in lowercase. I changed to uppercase and resolved the issue. >Since you state that TCPIPUSERID is correct (and you don't have bogus >copies of TCPIP DATA laying around), then the IPRCODE is needed. > I didn't have any spurious (surplus?) TCPIP DATA files lying around. >Feel free to open a PMR on this, btw. It should not be necessary for you >to TRACE IUCV to find out what's wrong. > I agree. I did open a PMR. Will send number to you separately. Thanks -- Craig Dudley Manager, Mainframe Technical Support Group Office of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1506 Fax 603-271-1516 >Alan Altmark >z/VM Development >IBM Endicott
