RE: Consolidating libraries - HELP

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

Sure, lots of other places. To name a few:

1) Hard coded in CLs that run the nightly backups
2) Run-book manuals
3) Stored in a dataarea and/or file for "soft coding" of library names.
4) In SQL scripts in source members
5) In FTP scripts "
6) On client machines in ODBC DSNs
7) ...

I would say that the best you can do is make the fixes you've mentioned and
mention a few of the places you can't check and add the "your mileage may
vary" standard disclaimer.

-Walden

-----Original Message-----
From: GDroke@hmstn.com [mailto:GDroke@hmstn.com]
Sent: Friday, July 28, 2000 12:30 PM
To: MIDRANGE-L@midrange.com
Subject: Consolidating libraries - HELP 


We have just completed coding for consolidating all of our product
application libraries into 3. We've tested it here, and are about to start
beta testing at client sites. We want it to be seamless for the client and
we've done the whole project programmatically. We found and were able to
change the library names in the following: job descriptions,
QUSRLIBL/QSYSLIBL, user profiles, menu commands, menu objects, job schedule
entries. Are there other places that application library names might be
hiding?


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---