Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!SCFVM.BITNET!XRJDM
From: XRJDM@SCFVM.BITNET (Joe McMahon)
Newsgroups: comp.lang.asm370
Subject: Re: SMP Structure
Message-ID: <8906302015.AA13493@jade.berkeley.edu>
Date: 30 Jun 89 18:59:20 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.bitnet@jade.berkeley.edu>
Distribution: inet
Organization: The Internet
Lines: 24

Ed Learned asked about what to do with a system which is disorganized.

   1) Decide on how things should look (i.e., IBM stuff under SYS1, local under
      SYS2., other vendors under SYS3., system work datasets under SYS4., etc.)
   2) Order a CBIPO for all of the existing IBM software, plus anything new
      are to be installing during the cleanup
   3) Install the CBIPO. If you don't have a large number of local mods, this
      should be pretty easy (1 serior or 1 mid-level + 1 junior should be able
      to do it).

Separate TLIB/DLIB for each vendor will not work unless the things in question
do not make any mods to the system; otherwise, some maintenance won't be easy
to out on. The IPO recommendation, which seems to work fine, is a SYSTEM CSI,
an IMS/CICS CSI, and an NCP CSI. You will need dups of these if you use (and I
hope you do) a floor system and a test system.

Step one is actually one of the more difficult parts of the whole thing. We
used (at my last job) a CBIPO to get to a stable, controlled level of system
under MVS/370 so that we could make a transition to MVS/XA. We planned the
whole thing using the Harvard Project Manager so we could have a day-by-day
plan of exactly how much needed to be done each day and by whom. It worked
well for us -- we won a company achievement award :-).

--- Joe M.