Re: CHGCMDDFT CMD(CHGPF) NEWDFT('ACCPTHSIZ(*MAX4GB)')

[CRPence <crp@xxxxxxxxxxxxxxxxxxxx>]

  It is IMO _always_ a poor idea to change CHGxxx command defaults from 
*SAME.  Such a change should be limited to CRTxxx commands to prevent 
confusion; i.e. most applications assume nobody would have changed the 
default of a CHGxxx command, and so expect that all non-specified 
parameters will remain *SAME.
  What is an especially bad idea for the noted command, is that the 
noted parameter will effect an asynchronous access path rebuild which 
can impact other applications or even remaining statements in the same 
application; not to mention possible CPU requirement.  I would suggest 
changing only the specific files that need to be changed to allow them 
to restore to the /previous/ release; leaving the command unchanged.