> On Aug 29, 2016, at 6:14 PM, Steve Beaver <[email protected]> wrote: > > Charles -- As an aside for you and maybe others. > > Most SYSPROGS will install a product that contains the VERSION/RELEASE > level mostly to know what we have. > Once we are done testing and over a weekend we will delete the COMMON name > and do a define > Alias that has the COMMON name pointing to the ACTUAL DSN that contains > VERSION/RELEASE name > As Lizette showed you. > > Steve =================SNIP++++++++++++++++++++++
I have a deferent way of doing this but it is a lot harsher . In the TSO logon proc I have a alloc for each ISP* file *WITH* the version and release in the dsn eg (sys1.v1.r3.ISPLLIB) That way I know that if the programmer has his own with a den different it will fail and it will make problem resolution that much simpler. I *HAVE* had someone use an out of date library and it caused not end of grief on my part trying to figure out where the problem was. Especially fun a finger pointing environment it pays to have the ammunition ready for fast rebuttal. In one case well I won’t go into detail but I was quickly able to point the finger at the accuser so he could not say *IBM* was the causer of missing a production window. Ed ps: It made roll out a little more difficult but there was a lot less blaming. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
