RE: DASD partitioning

[Rob Berendt <rob@xxxxxxxxx>]

If you MUST maintain the same file and library names then your options are 
limited:
1)  See if you can get around having different library names.
2)  Wait until V4R4 and partition your system.
3)  Unload the live software and restore the test software after hours.
4)  Buy another 400.





Marcia.Winder@CIBC.com on 03/09/99 11:20:21 AM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      

Subject:        RE: DASD partitioning

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

Marcia

        -----Original Message-----
        From:   Emilio Padilla [SMTP:vpadilla@guate.net]
        Sent:   Monday, March 08, 1999 6:08 PM
        To:     MIDRANGE-L@midrange.com
        Subject:        Re: DASD partitioning

        Hi marcia, Couldyou explain a little more what are you tryingo to
do?
        Running to version of OS/400?
        running Os/400 and ssp?
        running thirdparty software?

        Emilio

        -----Original Message-----
        From: Winder, Marcia <Marcia.Winder@CIBC.com>
        To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
        Date: Monday, March 08, 1999 5:03 PM
        Subject: DASD partitioning


        >Can anyone tell me how I can partition the DASD on my AS/400 510 in
order
        to
        >run two different versions of the same software concurrently?
        >
        >
        >Marcia
        >+---
        >| 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
        +---
+---
| 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
+---