×
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.
On Wed04-Apr-2011 11:03 , fbocch2595@xxxxxxx wrote:
The same with customized/modified IBM commands, did anyone have any
issues with them after the upgrade?
While not necessarily _the_ issue alluded.... Issues with customized
commands is a typical problem as effect from improper system change
management. Proper change management would have the same "changes" that
were applied on a prior release, applied again on the current release
after the upgrade completed. So if customized commands remain from the
previous release, then the system change management has not been
properly applied, because those commands first should have been replaced
either by the install or the customization process, and then\second have
been customized.
For examples:
Given the following had been performed on v5r#:
dltcmd altQsys/ibmcommand
crtdupobj ibmcommand qsys *cmd altQsys *same
chgcmddft altQsys/ibmcommand 'parmname(newdefault)'
Then the above requests should have been repeated on v6
Given the following had been performed on v5r#:
chgcmddft qsys/ibmcommand 'parmname(newdefault)'
Then the above request should have been repeated on v6
Regards, Chuck
This mailing list archive is Copyright 1997-2025 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
