Re: Using CHGCMDDFT

you wrote:

> CHGCMDDFT is one of the most powerful, and most dangerous command
available
> on the system.  I really have a love/hate relationship with this command.
> (Mostly hate!)
> <snip>
> In theory this command sounds like a good idea, right?  Well maybe?  But
as
> an application provider, if I cannot count on the fact that any QSYS
> command has the correct defaults, what do I do?  Do I specify the default
> value (that I expect) in every command in every CL program that I code?
> Tough stuff!  What happens what a new parameter with an completely new
> default is added in a future release?  Scary stuff!
> 
You can't count on common sense, either.  I once found that the CRTRPGPGM
command my team was using had a generation severity level of 30! It allowed
undefined variables and endless DOs, among other things.  And no one seemed
to know anything about the change.  Think twice before you change command
defaults.  

As for using nomax on all your files, watch out for that too.  Every few
years I see or hear of a run away job that was looping through a write of
endless records to some file in a batch update, usually something being run
off hours. Nomax will let that go until someone terminates it, or all
available disk is consumed and the system comes down.  Instead, consider
putting some thought into how large you expect the individual file to get,
then give it a much larger number.

JMO
kk
___________________
Kathleen Kostuck   
pager (414) 402-0820       fax (414) 495-4986
kkostuck@execpc.com
AS400 Solutions
___________________
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---