More like a rout*ing* issue. Verify that you can ping outward from z/OS, beginning at the gateway, then working outward.
On Wed, Sep 17, 2008 at 12:28 PM, Scott Ford <[EMAIL PROTECTED]> wrote: > Earl, > > Thank you. It works from Option #6 no problem, I see the logon screen.. > Sounds like a router issue ?? > > > Regards, > Scott Ford > Senior Host Developer | Forging Enterprise Identity | IdentityForge.com > (Main) 678.266.3399 x304 | (Cell) 609.346.0399 | (Fax) 678.266.3399 > [EMAIL PROTECTED] > > This message is for the designated recipient only and may contain > priviledged, proprietary, or otherwise private information. If you have > received it in error, please notify the sender immediately and then delete > the original. Any other use of the email by you is prohibited. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf > Of Earl Buhrmester > Sent: Wednesday, September 17, 2008 12:24 PM > To: [email protected] > Subject: Re: TN3270 port change > > Scott, > > Try this. Logon to tso on that lpar and from a ready prompt enter TELNET > xx.xx.xx.xx 1234 and see if you can connect. That will tell you if the > TN3270 server is functioning on that port. You might also turn on debug > in the TN3270 server. > > > Earl > > > > Scott Ford <[EMAIL PROTECTED]> > Sent by: IBM Mainframe Discussion List <[email protected]> > 09/17/2008 11:13 AM > Please respond to > IBM Mainframe Discussion List <[email protected]> > > > To > [email protected] > cc > > Subject > TN3270 port change > > > > > > > Hi all, > > I just migrated from z/OS 1.6 to z/OS 1.9. My question is as follows: > > Our 1.6 system used a port other than 23 for TN3270 sessions. The port > also > was a non-secure port. I tried the sane methodology, i.e.; changed port 23 > to > port 1234 ( example ) in TCPIP profile and the TN3270 address space STC > parms. I see TN3270 listening but can't connect..what am I missing. I > tried > inside our firewall and outside. I also noticed, I cannot ping the z/OS > system > or can't ping the Ethernet segement it is attached... > > Thanks in advance... > > Scott > IDF > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > > > > > ----------------------------------------- > This e-mail and any attachments are intended only for the > individual or company to which it is addressed and may contain > information which is privileged, confidential and prohibited from > disclosure or unauthorized use under applicable law. If you are > not the intended recipient of this e-mail, you are hereby notified > that any use, dissemination, or copying of this e-mail or the > information contained in this e-mail is strictly prohibited by the > sender. If you have received this transmission in error, please > return the material received to the sender and delete all copies > from your system. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
