×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
