October 7, 1999 11:03 AM
(in response to Kenneth Kornblum)
We have one SDSNEXIT per DB2 subsystem, and that's the method I've
If you use the method suggested, you'll have to have a different
DSNZPARM for each DB2 subsystem, since this is located in SDSNEXIT,
specify that unique name in each -START DB2 command.
You'll also have to devise a procedure for the occasions when you
PTFs to DB2 (you want to test them first before applying them to a
system) and when you upgrade to a new version of DB2 (you normally
upgrade one subsystem at a time).
MVS systems programmers seem to like to push for putting DB2
the LINKLIST, but I've found this usually causes more problems than
worth. It seems to be most troublesome on those occasions when you
PTFs to DB2 or upgrade to a new version. There are always some
put in a STEPLIB or JOBLIB card when they shouldn't or leave them
they shouldn't. This generates a lot of problem calls, and you have
a lot of research to see which library they're using.
>At 09:52 AM 10/7/99 -0500, Michael Bancale wrote:
>We currently have one SDSNEXIT loadlib for each DB2 Subsystem.
>recall the reason we choose this method but we did. Now one of
>guys has asked if we could only have one SDSNEXIT loadlib to
put in our link
>list and not have to steplib this guy.
>What is the standard practice?
>[login to unmask email]
>Texas Farm Bureau Insurance Company
William D. Welch
University of California, Berkeley
Central Computing Services, 502 Banway
[login to unmask email]