Hi,
Just chiming in with what we do. Note that I will not attempt to
rationalize any of this!
XXX - IBM supplied DSNs. (CSF.**, BDT.**, etc) Distribution/Target
Libraries. Mostly. Lives in the MCAT.
SYS1 - IBM supplied critical DSNs. (SYS1.PARMLIB, SYS1.MANx, SYS1.SIEALNKE
(?)) Mostly. Lives in the MCAT
SYS2 - IBM/Vendor Loadlibs/Program Libraries that need to be in the LNKLST.
Most are APF-Authorized, some are not. Mostly. Lives in the MCAT.
SYS3 - Vendor Software. (SYS3.CA.TMS.**, etc...). Not in LNKLST. May be
APF-Authorized. Lives in USERCAT.
SYS4 - CICS System files. Copies in SYS2 are LNKLST and APF-Authorized as
appropriate.
SYS5 - NCP. Remember NCP?
SYS6 - SAS. I have NO idea why, but I consider it a tribute to Dr. Merrill
to have an HLQ just for his stuff. (and we don’t' even have SAS these days!)
:-)
Thanks!
BobL
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Jesse 1 Robinson
Sent: Monday, September 25, 2017 5:05 PM
To: [email protected]
Subject: Re: SYS1 names (was SYS3 datasets) [ EXTERNAL ]
I misspoke in my original post. The three-qualifier data set names were our own
choice to preserve the ServerPac qualifier but still fit into our naming
standards. It was not a whimsical choice. We have 7 SAF-plexes to maintain.
Introducing even one new HLQ means a lot of work to make all seven work for us.
So at first we appended SYS1 to the front, making a three qualifier name with
no SAF prep work required. Eventually we decided that the ServerPac HLQ was
pointless and just removed it in subsequent releases. All data sets are now
SYS1.xxxxxxxx with the necessarily unique llq that SMPE knows.
So my real question is whether you set up and maintain the ServerPac HLQs or
just drop them as we do? As I said earlier, I don't see any benefit worth the
trouble they are to manage.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Gibney, Dave
Sent: Monday, September 25, 2017 2:34 PM
To: [email protected]
Subject: (External):Re: SYS1 names (was SYS3 datasets)
My SererPac(s) have always come as TCPIP.llq, CEE.llq, ASM.llq etc. and I've
kept them. We did have a collision once before BMC bought IOA. IBM won ...
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Jesse 1 Robinson
> Sent: Monday, September 25, 2017 2:23 PM
> To: [email protected]
> Subject: SYS1 names (was SYS3 datasets)
>
> ServerPac supplies a number of default names with three qualifiers
> such as SYS1.TCPIP.llq. We routinely eliminate any middle qualifier as
> being both redundant and confusing.
>
> 1. SMPE knows data sets by llq. SMPE cannot manage hlq.mlq1.llq and
> hlq.mlq2.llq concurrently. JCLIN does not know from anything other than llq.
> 2. Who can remember which data set groups have an mlq and which do not?
>
> Does anyone attempt to carry these default names forward to production?
>
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-543-6132 Office ⇐=== NEW
> [email protected]
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Gibney, Dave
> Sent: Monday, September 25, 2017 1:00 PM
> To: [email protected]
> Subject: (External):Re: SYS3 datasets
>
> To my knowledge, we've never had any SYS3 datasets. Kinda makes me
> cringe :) There's still a couple SYS2 from very old habits, but in
> general, we stick with what IBM provides for IBM and usually what the
> ISV suggests for other.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
This e-mail transmission may contain information that is proprietary,
privileged and/or confidential and is intended exclusively for the person(s) to
whom it is addressed. Any use, copying, retention or disclosure by any person
other than the intended recipient or the intended recipient's designees is
strictly prohibited. If you are not the intended recipient or their designee,
please notify the sender immediately by return e-mail and delete all copies.
OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or
disclose the content of all email communications.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
