MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2008

Re: Weird CPF2116 error in a CL program



fixed

CRPence wrote:
FWiW: Although simpler to just verify by ?CRTDUPOBJ, to see what is the current default for the DATA() parameter, a good reason to perform the DSPOBJD DETAIL(*FULL) is to record the change date/time of the *CMD object, so as to know when probably the CHGCMDDFT took place; to know where in the audit details to search for origin.

True. But in this case, they evidently already knew when and why: it seems that it was done for the convenience of some other program.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact