RE: Creating a physical AND Logical file

Thanks for your reply Donald
The rationale unfortunately is not up for argument, only to say that it IS
an auditing concern.
And yes - I did place a value in the member name within DTAMBRS, and ended
up with the same results as without that member name
We are on V5r4. I wonder if there is some ptf for this?



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx

midrange-l-bounces@xxxxxxxxxxxx wrote on 01/11/2007 02:11:06 PM:

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.