We also use SYS1.CEE instead of IBMs supplied CEE HLQ. (grrr). I like the IBM ADCD method of DFHnnn for CICS as HLQ etc.
On Mon, Sep 25, 2017 at 4:18 PM, Edward Gould <[email protected]> wrote: > > On Sep 24, 2017, at 9:18 PM, Tony Thigpen <[email protected]> wrote: > > > > 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 > > Tony: > > It depends on the oem product. If I know the history of the product then > its simple issue. Keep the sys3 datasets around for the life of the > product. Some products I just do not trust and I play games with datasets. > A *LONG* time ago I had a vendor that updated this one specific dataset > everytime it ran. I did not want to get write authority to the users. I > created a “test.product.update” and let the people update it. If it got > clobbered which it invariable did I would copy over the sys3 dataset for > that product “test.product.update” I won’t name the product as I had a > loathing for them. I kept there midnight called to a minimum bu doing that. > > Ed > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
