Jim
As Luis indicated in his reply, the new default value must be enclosed in
apostrophes when using CHGCMDDFT:
CHGCMDDFT CMD(CRTSQLRPGI) NEWDFT('DATFMT(*ISO)')
;-)
-sjl
"CRPence" wrote in message
news:mailman.1345.1406062290.8590.rpg400-l@xxxxxxxxxxxx...
On 22-Jul-2014 13:34 -0500, James Newman, CDP wrote:
<<SNIP>> I can't get the date format option changed in the compile.
When I do:
CHGCMDDFT CMD(CRTSQLRPGI) NEWDFT(DATFMT(*ISO))
I get a message saying "Errors detected while changing defaults".
Anyone see what I'm typing wrong?
The error msg CPF6260 "Errors detected while changing defaults." is
the Escape message for a failed Change Command Default (CHGCMDDFT)
request. As the "Recovery" for the message states, to determine the
origin for that exception [to see the diagnostic condition that led to
the exception being logged], one must refer-to\see "the previously
listed messages."
I presume previously logged diagnostic could be msg CPD0093 "DATFMT
not valid for parameter NEWDFT." as a condition being diagnosed due to
the value that was specified in the NEWDFT() parameter was not specified
as a string; i.e. was not quoted\delimited with apostrophes as shown in
<
http://archive.midrange.com/rpg400-l/201407/msg00281.html> Not
specified as a string, the Command Analyzer (CA) can get /confused/
about the embedded parentheses; in that case I believe the CA passes
only the token DATFMT to the Command Processing Program (CPP) [QCDCHDFT]
of the CHGCMDFT command. To verify that is the effect, the command
could be typed on a command line, as shown below; beyond the quoted
request, this one is prefixed by a question mark character to force
prompting:
? CHGCMDDFT CMD(CRTSQLRPGI) NEWDFT(DATFMT(*ISO))
midrange.com
