>> I then bring down TCPIP and bring it up again and it works . This remember me a similar problem some years ago. Looks like the OSA LCS startup needs a time to become operational greather than the TCPIP ipl. Supposing this running on one 9672... One circumvention was delay the TCPIP ipl: Putting a 'CP SLEEP 1 MIN' before 'XAUTOLOG TCPIP' into AUTOLOG1 profile exec. Regards, ______________________________________________ Clovis
From: ssda...@jerusalem.muni.il To: IBMVM@listserv.uark.edu Date: 14/04/2011 04:38 Subject: starting tcpip Sent by: The IBM z/VM Operating System <IBMVM@listserv.uark.edu> Hi list I have a consistent problem starting TCPIP after a VM cold start. As far as I can understand it's about initializing the OSA connection (cuu = 500-501) I get DTCPC3080I PCCA3 initializing: DTCPRI385I Device LCS1: DTCPRI386I Type: LCS, Status: Not started DTCPRI387I Envelope queue size: 0 DTCPRI388I Address: 0500 DTCPC3045E PCCA3 device LCS1: Error getting XA subchan id for 0000500 or 00000501 DTCPC3082E PCCA3 shutting down: DTCPRI385I Device LCS1: DTCPRI386I Type: LCS, Status: No status available DTCPRI387I Envelope queue size: 0 DTCPRI388I Address: 0500 I then bring down TCPIP and bring it up again and it works . What's going on ? Thanks David Sosnovitch City of Jerusalem, Israel
