Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!cup.portal.COM!-Cheshire-
From: -Cheshire-@cup.portal.COM (Gary Edward Learned)
Newsgroups: comp.lang.asm370
Subject: SMP Structure
Message-ID: <8906302002.AA13376@jade.berkeley.edu>
Date: 30 Jun 89 00:49:54 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: 11

I have recently inherited an existing shop, with it's SMP Structure in a
somewhat sorry state of affairs.  I am planning on reinstalling most software
in the near future, to get up up to current maintenance levels.  This includes
both IBM and non-IBM software, including CA with it's Activator front-end.
I am looking for suggestions on how to structure the SMP libraries for
ease and usability.  I have a small staff, of 2 (soon to be 3) people, so I
cannot devote endless bodies to managing the environment.  Specifically,
should I set up seperate structures for each software component, or combine
them by S-REL and just have seperate TLIB and DLIB structures for each vendor?
I'm open to suggestion.  Respond either here or via eMail.  Thanks.
Ed Learned