Re: ODBC exit point removed; by whom? -- MIDRANGE-L

× 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.

In my case we had a "setup" command that simply ran the ADDEXITPGM command to fix the problem.

Pete

CRPence wrote:

Script(s) that is maintained in order to enable repeating all of the system customizations, beyond just system values, is often referred to as proper /system change management/ :-) Not to imply that the loss of the customizations to the registration facility object in QUSRSYS should be expected, but having a script that establishes what was there before, sure is a nice way to recover as compared to other ways to effect that recovery. :-)

Regards, Chuck

Joe Pluta wrote:

Pete Helgren wrote:

Last time a customer of mine upgraded, the exit point program reference wasn't preserved. We had to reestablish the exit point entry. The library and program were there. But the entry wasn't preserved.

That's not pretty. But that does bring to mind two programs that ought to be in everyone's catalog: a program to set all system
values, and a program to verify them.

Time to write them for my system... <grin>

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.