There is nothing who wants to talk to VTAM at the moment. VTAM has to wait for incoming connections e.g. from a 3270 emulation. But if the lines are not active, there cannot be a connection established. It is the same as a real OSA. The receiver in the error message description is the adapter itself which does not respond. The XCA is only the door through which others can connect to VTAM, but the door must be open i.e. the lines of the XCA definition must be active first.
regards Franz Josef Pohlen ----- Original Message ----- From: "Stephen Frazier" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, February 17, 2006 7:07 PM Subject: Re: [VMESA-L] problem with vm vtam on tserver > That is good. If the state had not been open then we would have found the > problem. VTAM is telling you that there is nothing on the other end of the cable > to talk to. Or nothing that it recognizes. What is out there and is it > configured correctly to talk to VTAM? > > [EMAIL PROTECTED] wrote: > > > Hi Stephen, > > > > the response to display devstate e40 is before and after activating the > > ETH1XCA majornode the same: "Filename: /dev/net1 State: OPEN". There comes > > no error messages on the flexes console. > > > > Franz Josef > > > -- > Stephen Frazier > Information Technology Unit > Oklahoma Department of Corrections > 3400 Martin Luther King > Oklahoma City, Ok, 73111-4298 > Tel.: (405) 425-2549 > Fax: (405) 425-2554 > Pager: (405) 690-1828 > email: stevef%doc.state.ok.us > >
