Thomas Berg wrote:
And how do You solve the situation when the vendor have their own macros
they want to have in maclib (and doesn't supply their own lib) that
overwrites previously existing macors (if we would choose to install as
instrucyed) ?
Or when you have several different version that You had to use/have
installed in parallel ?
BTW, are you aware that sometimes vendors have install JCL that uses
their own invented HLQ, say like "SILLY.MACLIB" or "OUR.OWN.LINKLIB" etc.
At my installations we handled vendor products by:
1) requiring a unique high-level index for each product and version
2) maintaining an index alias (sans release/version number) to the
tested production version
3) supplying/modifying procedures to refer to the production alias, with
an override for testing and special needs.
4) When the vendor didn't rely on a discrete macro library, build one,
and add appropriate assembly procedures.
Vendor installs were run on a test system before coming anywhere near
production. The convention made installation a bit more difficult, but
made maintenance and user documentation trivial. In one case we had an
LPA member conflict, solved inelegantly by renaming the member and its
references.
Gerhard Postpischil
Bradford, VT
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
