|
Alan, I could _maybe_ see where auditors would dislike allowing you to use CRTDUPOBJ from a command line. (kind of dumb but whatever) However, there's no reason why you shouldn't be able to use it in a CL program. Perhaps they'd want somebody else high to create a program to encapsulate the CRTDUPOBJ command you need, which you could then call. Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121
-----Original Message----- From: midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx [mailto:midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx] On Behalf Of Alan Shore Sent: Thursday, January 11, 2007 2:20 PM To: Midrange Systems Technical Discussion Subject: 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 memberscan 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 amnot allowed touse 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 listTo 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.-- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.