So conventions are on a shop basis. Whatever the shop wants to use, is the convention
I have known some shops to use this SYS1CA for all CA Products SYS1IBM for all IBM products SYS1ORC for all Oracle products and so on I have known some shops to use this SYS1 - all IBM Products SYS2 - Vendor A products SYS3 - Vendor B products And so on. When they got to SYS9 - they began to uses SYSA Some shops do SYS1 - Only MCAT products then use second level qualifier to identify vendor - IBM CA etc When some shops install Serverpac, they use CEE for LE, BPX, etc that is the names used by IBM When some shops install Serverpac, they change the IBM names in server pac to shop standards - SYS1.CEE rather than CEE Everything is based on what the shop standards are. So bottom line, No Standard for naming convention. Each shop makes that determination. And that standard is affected by your SAF product and application naming convetions. SYS3 is not a standard in the business to indicate a 3rd party vendor. HTH Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Tony Thigpen > Sent: Sunday, September 24, 2017 7:18 PM > To: [email protected] > 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 Thigpen > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
