RE: PDM Library List

-----Original Message-----
From: Jeff Crosby [mailto:jlcrosby@fwi.com]

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,

OF COURSE QTEMP is a *TEST library!  The system says so all over the place - for
example:

                                Display Library                      
                                                                     
 Library  . . . . . . :   QTEMP           Number of objects  . :   4 
 Type . . . . . . . . :   TEST            ASP of library . . . :   1 
 Create authority . . :   *SYSVAL                                    

As far as library list models for developers are concerned, I've used all of the
approaches mentioned so far at one time or another.  Any of them can work well,
it's just a matter of choosing the one that best fits the particular system
environment that one finds oneself in.

Dave Shaw
+---
| 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
+---