Oh, and code autorestart on the device if it is not there already. 

Marcy Cortes 

"This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Daniel Allen
Sent: Wednesday, August 01, 2007 8:58 AM
To: [email protected]
Subject: Re: [IBMVM] TCPIP under z/VM problem

Here is the TCPIP reader log:

 04:20:01 DTCOSD309W Received adapter-initiated Stop Lan        
                              ***** 08/01/07 *****             
04:20:01 DTCOSD082E OSD shutting down:                         
04:20:01 DTCPRI385I    Device [EMAIL PROTECTED]:                        
04:20:01 DTCPRI386I       Type: OSD, Status: Ready             
04:20:01 DTCPRI387I       Envelope queue size: 0                
04:20:01 DTCPRI388I       Address: 0103                        
04:20:01 DTCQDI001I QDIO device [EMAIL PROTECTED] device number 0103:   
04:20:01 DTCQDI007I   Disable for QDIO data transfers    

My question is why ? Is there something in the setup of TCPIP doing this
? Or do we have a flaky OSD card ?      


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Jones
Sent: Wednesday, August 01, 2007 8:44 AM
To: [email protected]
Subject: Re: TCPIP under z/VM problem

It's very simple, Daniel, and you don't need a printer....:-)

By default the TCPIP service virtual machine spools (routes) it's
console to the TCPMAINT user id. To see what's in the TCPIP console, do
this:

1) log onto TCPMAINT
2) see what's in it's reader queue: RDRL
3) there should be some lines in the RDRL display that look like this:
(none)   (none)   CON T TCPIP    ZVMV5R20 NONE      128  7/21    16:44
These, if there is more than one, are the console logs of the TCPIP
server.
4) move the cursor to the latest one, and hit PF 11 (peek).  You will
then be put into an XEDIT session where you can scroll up and down the
console, and see any error or warning messages that TCPIP might have
produced.
5) the PEEK command, by default, only shows the first 200 lines in the
console log file; if the console log is bigger than that, you will need
to enter the following command against the console log file you want to
look at:
   PEEK / (FOR *
This tells peek to show all of the lines on the console file.

Let us know if you need more assistance. Good luck.

Daniel Allen wrote:
> I did a Q PRINT and there is a file called TCPIP. I have done a quick 
> review of CMS Primer and CMS User Guide. We do not have a printer. How

> do I look at the file ?
> 
> 
> 
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] 
> On Behalf Of David Kreuter
> Sent: Wednesday, August 01, 2007 8:12 AM
> To: [email protected]
> Subject: Re: TCPIP under z/VM problem
> 
> This is not normal. Pls check the console log of TCPIP or TCPMAINT.
> Terminating the connection could be related to a bunch of things, some

> debugging is required.
> David
> 
> 
> -----Original Message-----
> From: The IBM z/VM Operating System on behalf of Daniel Allen
> Sent: Wed 8/1/2007 11:06 AM
> To: [email protected]
> Subject: [IBMVM] TCPIP under z/VM problem
>  
> Recently our z/VM 5.2 system is losing connectivity to TCPIP. I force 
> TCPIP and xautolog TCPIP. Everything is fine again. This has happened 
> twice within two days. The z/OS system running under z/VM was okay.
> Has anyone seen this behavior ?
>  
>  
> 
> **********************************************************************
> This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they 
> are addressed. Any unauthorized review, use, disclosure or 
> distribution is prohibited. If you are not the intended recipient, 
> please contact the sender by reply e-mail and destroy all copies of
the original message.
> **********************************************************************

--
DJ
V/Soft

Reply via email to