Re: PDM Library List

OleBlighty wrote:
 
> Call me old fashioned, or maybe I am missing the point...but...doesn't that
> approach leave the door open for possible production database corruption.

Not necessarily.  That the approach I use.  I have *TEST lib(s) at the
top of the library list followed by the *PROD libraries.

I create duplicate copies of production files _that will be updated_
into a *TEST library high in the library list.  Then I do a STRDBG
UPDPRD(*NO).  Any files that are read only are then used from the
production library.  By saying UPDPRD(*NO) on the STRDBG command, the
system insures that I didn't miss any.

FWIW, I have QTEMP at the top of the user portion of the library list. 
The system evidently considers QTEMP a *TEST library because I can
create and update work files in QTEMP while in debug mode with
UPDPRD(*NO).

-- 
-Jeff
+---
| 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
+---