When VTAM/SNA went to Multi Systems Networking Facility (MSNF) in the 1980s, shops suddenly needed to take the whole world into account when exposing heretofore 'private' node names. Most shops had a SYSA, which would not do when everyone began interconnecting.
IBM's recommendation at the time was to prefix outward-facing node names with the SHARE installation code, such as SCE. Shops following that convention would unlikely collide with another installation. When we adopted system symbols in the 90s, we followed a similar strategy. All of our in-house symbols begin 'SCE'. Never had a conflict. Also serves to mark such symbols as home-grown. . . 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 robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, December 31, 2018 8:01 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: System Symbols On Mon, 31 Dec 2018 08:29:19 +0000, Sean Gleann wrote: > >As for "This is the sort of thing that should be routinely provided by >the OS." - a huge YES! to that, and other associated values like 'first >working day of the week/month/year' and so on. >Its a crying shame that the only other way of getting such values in >to a jobstream - that I know of! - is by spending $many for something >like CA-7 or Tivoli. > I have routinely kept JCL wrapped in UNIX shell scripts, as here-documents (think "instream") in which I can routinely do such things with command substitution. z/OS UNIX is a boon, and the (incremental) price is right. And Peter R. has clarified that it's not customers but IBM that's advised to use SYS as a prefix. Should ISVs yet stay with registered componend prefixes? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
