RE: Creating a physical AND Logical file

CRTDUPOBJ requires *OBJMGT authority to the file being duplicated
(because you are also duplicating the authorities).  It is wise not to
give end users *OBJMGT authority to production files (that would give
them rights to Clear the file, among other things).

However, you could give the program *OBJMGT rights to the source LF and
then have the user profile adopt the program owner's rights.  That's an
easy case for adopted authority.

jte

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Fisher, Don
Sent: Thursday, January 11, 2007 11:11 AM
To: Midrange Systems Technical Discussion
Subject: RE: Creating a physical AND Logical file

I'd be interested in hearing the rationale against preventing

production

programs from using CRTDUPOBJ.

The only thing that jumps out at me is you didn't specify the member

name

within the DTAMBRS.

There is another alternative here.  You could add a member to the

physical

and logical files and use OVRDBF to make the program use those

members.

When the program is finished, the members can be removed.

Good luck.

Donald R. Fisher, III
Project Manager
RoomStore, Inc.
(804) 784-7600 ext. 2124
dfisher@xxxxxxxxxxxxx

<clip>
Okay - due to auditing constraints and other things, I am not allowed

to

use CRTDUPOBJ
<clip>
CRTLF FILE(QTEMP/LOGFILE) DTAMBRS((QTEMP/PHYSFILE))
The logical file gets created but with NO member
<clip>

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.