Vince, The NETSTAT ALLC command does not show anything on port 3603. I have very little in my display which is what I would expect...
User Id Conn Local Socket Foreign Socket State ---- -- ---- ----- ------ ------- ------ ----- FTPSERVE 1001 *..FTP-C *..* Listen SMTP 1004 *..SMTP *..* Listen SMTP UDP *..1024 *..* UDP INTCLIEN 1007 *..TELNET *..* Listen INTCLIEN 1005 10.100.5.73..TELNET 172.20.31.17..63168 Established INTCLIEN 1003 10.100.5.73..TELNET 10.80.8.151..49724 Established RSCS 1008 10.100.5.73..8352 10.100.5.71..175 Established RSCS 1009 *..175 *..* Listen I could change the output class to see if that makes a difference but I do have to be careful. The EXEC on the z/VM side uses the class to determine what needs to happen to the output (FTP it to a FTP server where ONBASE can get it, send it to a physical printer, delete it). This is something I will attempt with our test output. I heard back from IBM support and here is their response... Action Taken: I have reviewed the zOS commServer traces. I see a successful connection from zVM @ 10.100.5.73 using ephemeral port 5582 to zOS 10.100.5.71 port 175. This connection stays up and ends right before the connection attempt from zOS ephemeral port 32979 to zVM 10.100.5.73 port 175. Not sure why this connection ended, but I can see that the TCP connection closure for this was initiated by the zVM side. I then see the zOS side initiate the TCP 3-way handshake by sending the SYN packet. This is immediately responded to by the zVM side with a reset packet, hence the econnrefused error on the JES connect attempt. So hopefully a trace on the zVM side was captured to understand why that TCPIP stack is rejecting the connection attempt from zOS to port 175 @ 10.100.5.73 Thanks, Ron McCabe Mutual of Enumclaw -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Vince Getgood Sent: Tuesday, February 12, 2019 12:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: How can I get reports in the Output Queue in SDSF to print Ron, If JES is saying the networking is started, that suggests that the connection between JES and z/VM is good. Your PROFILE TCPIP might tell you what's on port 3603, but the z/VM TCPIP command NETSTAT ALLC should display the connection. If the nje connection is starting, then you should be able to start whatever device is defined on JES to "print" output to z/VM, and the output should start to flow. This COULD be a problem with the actual output being sent across. You said that something seems to start being sent across, and then freezes? Is it the same output every time? Maybe temporarily change the class of that output, and restart the connection? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Confidentiality Notice: This e- mail and all attachments may contain CONFIDENTIAL information and are meant solely for the intended recipient. It may contain controlled, privileged, or proprietary information that is protected under applicable law and shall not be disclosed to any unauthorized third party. If you are not the intended recipient, you are hereby notified that any unauthorized review, action, disclosure, distribution, or reproduction of any information contained in this e- mail and any attachments is strictly PROHIBITED. If you received this e- mail in error, please reply to the sender immediately stating that this transmission was misdirected, and delete or destroy all electronic and paper copies of this e-mail and attachments without disclosing the contents. This e- mail does not grant or assign rights of ownership in the proprietary subject matter herein, nor shall it be construed as a joint venture, partnership, teaming agreement, or any other formal business relationship. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
