|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] There is no way to do that. And the object information varies from one object to the next. And even if you could then the question is do you want it to tell you if someone changed the object after the command or not? For example if someone ran: CRTPRTF FILE(MYLIB/MYFILE) SRCFILE(MYLIB/QDDSSRC) CHGPRTF FILE(MYLIB/MYFILE) LPI(8) Should it return CRTPRTF FILE(MYLIB/MYFILE) SRCFILE(MYLIB/QDDSSRC) or CRTPRTF FILE(MYLIB/MYFILE) SRCFILE(MYLIB/QDDSSRC) LPI(8) A good change management system will detect this and allow you to handle this accordingly. I don't know everything about our change management system but I know it tells us if something was changed outside of the system, when we go to propagate a new change. Kind of nerve racking on SQLRPGLE though. Everytime you run these it updates the program with the access path information. Then the change management tells us it was changed outside of the system. I don't think it flags the differences though. That would be nice. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Smith, Nelson" <NSmith@lincare.com> Sent by: midrange-l-admin@midrange.com 11/05/2002 08:58 AM Please respond to midrange-l To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> cc: Fax to: Subject: RE: Create Commands Correct. I would like some way to extract from an object, how that particular object was created. What parms were used at the time of creation. You would think that information would be part of the object, but I haven't found any way to get at it. > -----Original Message----- > From: Vern Hamberg [SMTP:vhamberg@centerfieldtechnology.com] > Sent: Monday, November 04, 2002 2:35 PM > To: midrange-l@midrange.com > Subject: Re: Create Commands > > Loyd > > I have to look at that API. But that returns information about how a > command was created. I think this question is how to derive the parameters > used on a command to create a given object, like a program or data area or > whatever. Is that right? > > Let's here it for levels of indirection! > > Vern > > At 01:07 PM 11/4/02 -0600, you wrote: > >Yes, it is the QCDRCMDI API. You can see it in use with the "recreate > command" > >utility RECRTCMD found at http://www.alltel.net/~craigru/jcrcmdv4.html. > > > >HTH, > >Loyd > > > >On Fri, 1 Nov 2002 15:00:49 -0500, "Smith, Nelson" <NSmith@lincare.com> > wrote: > > > > >Is there an API that would return the create command parameters that > were > > >used to create a given object? > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. ************************************************************************************************************************************************************************************************************ This message originates from Lincare Holdings Inc. It contains information which may be confidential or privileged and is intended only for the individual or entity named above. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message. All personal messages express views solely of the sender, which are not to be attributed to Lincare Holdings Inc., and may not be copied or distributed without this disclaimer. If you received this message in error, please notify us immediately at MailAdmin@lincare.com or (800) 284-2006. ************************************************************************************************************************************************************************************************************ _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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-2025 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.