John,
I'm asking some questions here having tried to sort out Jack Kelly's
problem.
NOAUTOLOG matters only if the procedure mentioned in the PORT statement
entry has a corresponding entry in the AUTOLOG list. Might OMVS appear in
the AUTOLOG list?
Well, I thought I might research OMVS as it appears in the PORT list a bit
further. From the comments in the sample PROFILE.TCPIP file, we find the
following:
<quote>
; The special jobname of OMVS indicates that the PORT is reserved for any
application with the exception of those that use the Pascal API.
; The special jobname of * indicates that the PORT is reserved for any
application, including Pascal API socket applications.
</quote>
So it's only poor Pascal who is not allowed to exist in OMVS .<g>
But I then found the following in section 2.2.1.1.5, "Telnet in its own
address space" of the CS IP Configuration Guide - with revision bars in the
z/OS V1R7.0 version of the manual:
<quote>
Tip: The default PPT entry sets the TN3270 server to non-cancelable. As a
non-cancelable application, the TN3270 server should not be started
automatically by a TCP/IP stack using the AUTOLOG function. If the TCP/IP
stack is recycled, the following messages will be issued repeatedly:
N 0140000 SA6I 2005147 04:59:27.69 STC07087 00000084 EZZ0621I AUTOLOG
FORCING IBMTNSI0, REASON: AUTOLOGGING SCHEDULED
NR0000000 SA6I 2005147 04:59:27.71 STC07087 00000080 IEE838I IBMTNSI0
NON-CANCELABLE - ISSUE FORCE ARM
To prevent this, specify NOAUTOLOG on the PORT reservation statement as
follows:
PORT 23 TCP TN3270D NOAUTOLOG ; TN3270 server
</quote>
Probably it is from here that you got the "NOAUTOLOG" hint.
The examples of services started by INETD in section 2.18.5, "Configuring
TSO and z/OS UNIX Remote Execution servers to use the same port" in CS IP
Configuration Guide do not use the NOAUTOLOG parameter.
This makes sense in combination with the following comment in section
1.6.8.8, "Steps for configuring OMPROUTE", "RIP protocol", in the CS IP
Configuration Guide:
<quote>
If you want to be able to start OMPROUTE from the z/OS shell, use the
special name OMVS as follows:
PORT
520 UDP OMVS
521 UDP OMVS
</quote>
This finally reminded me what the significance of OMVS in the PORT list was.
Although, looking back to CS IP Configuration Reference, it is actually
buried in the description of the PORT statement:
<quote>
The name of the started JCL procedure for the UNIX System Services Kernel
Address Space can be used to allow almost any caller of the bind() socket
API (except for users of the Pascal API) to bind to the port. This name is
typically OMVS unless a different name is explicitly specified in the
STARTUP_PROC parameter of the BPXPRMxx parmlib member.
</quote>
But I kept on through the OMVS search "hits" in the CS IP Configuration
Guide and found the following:
<quote>
To reserve ports 21 and 20 for the FTP server, add the following:
PORT
21 TCP FTPD1 ; FTP server control port
20 TCP OMVS NOAUTOLOG ; FTP server data port
</quote>
But I also found the following from my antique teaching notes:
<quote>
PORT
...
20 TCP FTP NOAUTOLOG DELAYACKS ; FTP default data port
21 TCP FTP DELAYACKS ; FTP server
...
</quote>
In other words, I suspect the CS IP Configuration Guide author did not
appreciate that the NOAUTOLOG advice on the PORT entry for port 20 no longer
applied - but I've been known to be wrong.
Are your comments in support of running both the CS IP TN3270 and z/OS Unix
TELNET servers or just the latter or maybe the former in its own address
space? In other words, what actually do you have working?
What are the "foolish" comments?
Chris Mason
----- Original Message -----
From: "McKown, John" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <IBM-MAIN@BAMA.UA.EDU>
Sent: Thursday, 02 March, 2006 5:11 PM
Subject: Re: inetd to take telnet request
> > -----Original Message-----
> > From: IBM Mainframe Discussion List
> > [mailto:[EMAIL PROTECTED] On Behalf Of Jack Kelly
> > Sent: Thursday, March 02, 2006 9:56 AM
> > To: IBM-MAIN@BAMA.UA.EDU
> > Subject: inetd to take telnet request
> >
> >
> > I was trying to get inetd to take control for telnet sessions
> > (otelnetd
> > and/or tso telnet) but so far I can only get vtam (msg10) to
> > get control.
> > Netstat show mvs tcpip task listening on port 23 (from tcp
> > profile). inetd
> > is listing on port 513 and 540 (from /etc/services).
> >
>
> In your TCPIP params, make the telnet port (23) look the same as the ftp
> port (20). I.e.
>
> 23 TCP OMVS NOAUTOLOG ; Telnet Server
>
>
> This works for me. You currently have INTCLIEN which is the TN3270
> server, despite the foolish comments that IBM put about "telnet" server.
> This is setting the port up as a TN3270 port (aka VTAM port), and not
> allowing "inetd" to open it.
>
> --
> John McKown
> Senior Systems Programmer
> UICI Insurance Center
> Information Technology
----------------------------------------------------------------------
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
