As others have said, there is no universal rule, just conventions adopted in 
each shop--or in each mind! I personally think that 'SYS3' for 3rd party 
products is a pretty cute mnemonic, but it's certainly not pervasive. One 
requirement that we recently got reminded of is that a link list data sets must 
be cataloged in the master catalog for 'normal' processing. You can use a user 
cataloged data set with restrictions:

"If you plan to use a user catalog, you should be aware that the system will 
not find the data set unless you specify both the name of the data set and the 
volume serial number (VOLSER) of the DASD volume on which the data set resides. 
(This restriction also applies if you are defining the LNKLST concatenation in 
LNKLSTxx.)"

Specifically, we tried to link-list a user catalog library just for an IEFSSNxx 
init routine. Module was not found. So if you plan to use anything other than 
'SYS1' for such purposes, be sure that you put the whole set into MCAT.  

.
.
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 Carmen Vitullo
Sent: Monday, September 25, 2017 10:20 AM
To: [email protected]
Subject: (External):Re: SYS3 datasets

Unfortunately and fortunately I've had the opportunity to work in many 
different shops, the phrase 'almost all shops use SYS3' is just B.S. 


It all comes down to who started or documented the standards for that company 
or site, I've worked for companies that added a site ID to a HLQ, the standards 
were company wide, some sites had rules that OEM or vendor products were 
SYSP1.vender.product.libtype, and when multiple systems joined a sysplex SYS8 
was used for sysplex datasets, so the rule is more a standard for the site or 
company. some very strange and don't make much sense, like the outsourcing 
company I worked for tried to force OEM* to the HLQ for program products, when 
OTHER standards were already in place in a 16 system sysplex with multiple 
customers, try forcing a long standing customer to accept that change :( same 
standards are being used for the Unix directory structure, everyone has an 
opinion on how it should be designed and they're no right or wrong way as long 
as everyone adheres to the standards. 




my 2 cents 




Carmen 


----- Original Message -----

From: "Tony Thigpen" <[email protected]> 
To: [email protected] 
Sent: Sunday, September 24, 2017 9:18:05 PM 
Subject: SYS3 datasets 

We have a staff z/OS systems programmer who claims that: 
"Almost all shops use the SYS3. HLQ to indicate third party software." 

So new software installs *have* to follow that "rule". (Past installs 
did not follow such a rule.) 

I am thinking that this "rule" is really just *his* rule. 

Opinions? 

How many other sites follow such a rule? 

-- 
Tony 


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to