× 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 16-Apr-2015 17:05 -0500, Monnier, Gary wrote:
On 04/16/2015 10:43 AM John Allen wrote:
<<SNIP>>
Exit point QIBM_QCA_CHG_COMMAND with format CHGC0100 does not
exist.
<<SNIP>>

If you are not seeing the exit points with WRKREGINF I wonder if
they were damaged or possibly deleted.

What happens when you run RMVEXITPGM?

RMVEXITPGM EXITPNT(QIBM_QCA_CHG_COMMAND) FORMAT(CHGC0100)
PGMNBR(*ALL)


FWiW: I would expect the same error, because the combination of EXITPNT(QIBM_QCA_CHG_COMMAND) and FORMAT(CHGC0100) are what is missing from the object QUSEXRGOBJ in QUSRSYS; i.e. likely the request would be unable to remove all exit-programs from an exit-point that does not exist. According to [the very ancient] v5r1m0 APAR SE10152, an installation-exit program for v5r2m0 QUSRSYS apparently runs in post-install phase, or calls a separate program, that will add those Exit Point definitions and corresponding Format name(s). That APAR implies that same effect seen not only after install, but merely post-restore, so after RSTOBJ QUSEXRGOBJ QUSRSYS dev_name *EXITRG is requested; no mention if scratch only, or if restore-over\slip restore both are corrective that way, and no mention if the safest bet is to restore from an request to SAVOBJ QUSEXRGOBJ QUSRSYS dev_name *EXITRG performed immediately prior.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.