Re: DASD partitioning

Hi Marcia, as Bob said, if you could change your library names, that's the
way to go.  If you can't, (I will try to explain this but this could work
depending on the application), you could use member in your actual files and
use the same library and files, this will cost a little on performance but,
on your entrance program you will have to do a ovrdbf to all the files on
your library.  (This could work only if the application allow it).  BE
REALLY CAREFUL, you are going to be using the same objects so if the
program's delete and object you will loose both environments
-----Original Message-----
From: Bob Larkin <blarkin@wt.net>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Wednesday, March 10, 1999 12:10 AM
Subject: Re: DASD partitioning


>Marcia,
>You do not have to use the same library names. If the software forces you
to, I
>would recommend re-examining your choice of vendors. It make this bold
statement
>because the library list is the best tool for maintaining test and
production
>environments on the same machine. It has been my experience that any
package that
>attempts to prevent this is not a good package. It is usually a port from
another
>platform, by a vendor that does not have a clue about the AS/400.
>
>You want to segregate data between production and test environments.
Programs,
>display files, printer files you will probably wish to share. Data should
reside
>in another library. in this instance, a library list handles the job well.
for
>example:
>    Production                Test
>    PRODDATA         TESTDATA
>    PROGLIB             PROGLIB
>    DISPLAYLIB        DISPLAYLIB
>
>If the production data is in the same library as the programs, you can
still
>place a test library above the program library in the library list. Unless
the
>software is REALLY lame, it will allow the system to find the first
occurence of
>the file in the library list.
>
>Bob
>Winder, Marcia wrote:
>
>> Hi Emilo, Thanks for responding, let me see if I can explain a little
>> further.
>>
>> We are currently running V4R1 on our system, the software I asked about
>> though is 3rd party. One version of the 3rd party software must
communicate
>> with our mainframe in a production environment. The other version is in a
>> test environment which does not need to communicate with the mainframe.
>> However, we must maintain the same file and library names in both
>> environments. The only way we figured to do this was to partion the disk.
>> ANY IDEAS???
>>
>

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