On Mon, 5 Jun 2006 18:21:02 +0200, Chris Mason <[EMAIL PROTECTED]> 
wrote:

>Patrick,
>
>I've been keeping my eye on this thread as the responses flew by hoping a
>definite answer might emerge. The definitive answer doesn't seem to have
>appeared so far.
>
>Many years ago I used to teach TCP/IP for MVS. My last version of the
>presentation in dated November 1995 and I think it corresponds to V3R1.
>
>When I was first confronted with installing TCP/IP for MVS I was appalled 
at
>the mess of libraries, partitioned data sets, that were thrown at you with
>no explanation as to what purpose each served - what a can of worms!
>
>But I was eventually asked to insert a day teaching the MVS flavour of
>TCP/IP into an otherwise basics-cum-OS/2 class. Now I was being forced to
>try to make sense of all these libraries.
>
>So with that background I can report that what I said all that time ago
>about SEZATCP is that it is a library for load modules, it had at that time
>40 members and was used by "started tasks". What I very probably meant by
>"started tasks" is that it seemed to contain the names which followed the
>PGM= operand of the EXEC statement in the many sample task procedure 
members
>which were described in the then "Customization and Administration Guide".
>
>Two rather old pennies.
>
>Chris Mason

Thanks to Chris and others for responding back to my post.

I myself cannot remember when we installed Communications Server, it was 
either in OS/390 2.7 or 2.10.  I use the same TCPIPROC from release to 
release, never making a new one.  I do not know why we have SEZATCP in the 
steplib, I am not sure if it was required way back when or what.  Maybe I 
put it in there as a "just to be sure" measure.  Who knows.  

But in either case I know the SMTP proc has it steplibed, and in searching 
the CS 1.4 Configuration Guide it shows SEZATCP to be steplibed in other 
procs also. 

In searching the z/OS Program Directory it shows SEZATCP as APF authorized 
capable (probably for the steplib issues) and SEZALOAD as LNKLST capable.

So I think I will go that route, taking SEZATCP out of the steplib and only 
having SEZALOAD in the LNKLST.

Thanks again to all who have responded.

Kind Regards,
Patrick Lyon

----------------------------------------------------------------------
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

Reply via email to