Newsgroups: bit.listserv.ibmtcp-l
Date:         Sun, 4 Oct 1992 22:01:00 PDT
From:         Leonard D Woren <LDW@USCMVSA.BITNET>
Subject:      Re: Cum PTF tape for HTCP221

On Sun, 4 Oct 1992 23:13:40 EDT, Bill Rubin <RUBIN@YKTVMV.BITNET> said:
> The bottom line is that TCP/IP for MVS V2R2.1 shipped a week ago
> Friday (I hope, if anyone has received it, please let me know)

Hi Bill!  Guess who got it last Tuesday (I think).  Manuals in a box
from Mechanicsburg, tapes in another package from somewhere else.  On
the other hand, this may not count, since it was specially arranged.

> there will be no PTFs built for V2R2, all reported bugs
> will be fixed on the 2.2.1 base.

I expected that, so what does the following actually mean?  It seems
to be saying that 2.1 will be supported until December, but 2.2 is
already dead.

> > STATEMENT OF PROGRAM SUPPORT
> >
> >                                 all program services for IBM
> > TCP/IP Version 2 Release 2 for MVS will be provided  at  the
> > IBM  TCP/IP  Version  2  Release 2.1 level. Program services
> > previously announced for IBM TCP/IP Version 2 for MVS (prior
> > to Version 2 Release 2) will be available until December 31,
> > 1992.


> All current customers should also be receiving a similarly worded letter
> from our product manager.

Or a phone call.  ;-)


A cum maint tape was included with the shipment.  Assuming there are
2.2.1 PTFs on it, are they all supposed to be installed as part of the
initial 2.2.1 install?

Comments on installation experience.  The first time that I ran the
APPLY, it died S722 because I had a linecount limit of 100,000
specified.  The reruns with APPLY REDO died multiple times because
most of the target libraries have too-small secondary space specified,
and a second complete copy doesn't fit within 16 extents.  On Monday I
will delete 'TCPIP.V221.*' except for the customized JCL library, and
start over to be sure that I have a clean install.  Since I won't have
to customize the JCL again, I should have runnable stuff in under two
hours.  (I should have stuffed the tapes into the robot before I left
on Friday...)

There are still no DDDEFs built by the CSI init job.

The blksizes for the large FB/80 datasets should be changed to
something much larger.  The installation instructions should probably
suggest this.  I'm using 23440 on 3380s.  Those installing on 3390s
will have to determine another blksize.  23440 saves a significant
amount of space over 6160.  This becomes quite noticable with a 200
cylinder library.  And it makes the brute-force searches that I do go
faster.  :-)


Can I test 2.2.1 using the 2.2 LPA modules?  Can I go production with
2.2.1 using the 2.2 LPA modules?  If not, I assume that it's at least
backward compatible -- 2.2 should run fine with the 2.2.1 LPA modules?
(I ran V1 for months with the 2.1 LPA modules...)  I'd like to test
and maybe even install the new release without an IPL.  These days,
IPLing is a pain and is only done a few times a year.  It would be
very nice if you could implement something like what was done with
JES2, which now loads its formerly-LPA module into CSA from a STEPLIB
during startup.

/Leonard
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU