RE: Allocating a display file

Joe,

We do the same on our R&D lpar.
We don't add the "new" library to the library list, but it's included in our jobd library lists.
We have a "new" library for each library that exist for the application.
It's easier to manage when having to move objects back to their original library.

To move objects back during restricted stated, we TAATOOL MOVALLOBJ.
Moves all objects from one library to another library.

Any object with locks "in use" cannot be moved.
Programs are the exception to the rule.
They do not create locks and thus can be moved.

We also have an "old" library which is NOT in the library list.
We move programs that are being updated to the "old" library.
Updated programs get moved to "NEW".
If a job is still running calling this program, it will not fail, even though program is no longer in the library lsit.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Monday, April 02, 2018 12:21 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Allocating a display file

Yes, our production works like that. I'll just have to live with something a bit less robust on development.

Does it work like a program promote-- move the old to QRPLOBJ and install the new one; anyone using the old one works out of QRPLOBJ??

If you need to lock the file-- move it to a library all by itself and allocate the library??

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Joe Pluta
Sent: Monday, April 02, 2018 11:53 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Allocating a display file

I'm sure this is nothing new, and probably goes back to the S/38 days,
but it's new to me, so...

I just tried to allocate a display file.  I wanted to make sure nobody
had it before I change the display file and its underlying program. 
Lo and behold I get a CPF0894 error which basically says I can't
allocate a display file.  It certainly seems this limitation has been
around for a very long time, but I've never run into it before.

I'm just wondering if anybody else has ever felt a need to exclusively
lock a display file and if so, how they got around this particular error.

Thanks!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD