I respectfully disagree. There are some exit points that have special
considerations related to ending and restarting, but "many" as in "...many
of the points..." strikes me as being a bit too broad. Looking at the exit
point documentation I do find the following Usage Note as #1:
For better run-time performance, each job retrieves a list of the
QIBM_QSP_SECURITY registered exit programs at the first spool command or
API, and this list is used for the life of the job. If a new program is
registered for the exit point, any jobs already running on the system will
ignore the new exit program. If an exit program is deregistered, any jobs
already running will continue to call the program unless it is deleted or
moved to another library. If a registered exit program is replaced, all
jobs (including those that are already running on the system) will call the
I'm not sure if any of these points apply here as the original note didn't
indicate what had been done explicitly (job wise). I do suspect that, in
addition to the above Usage Note, that the exit point might remove the exit
program (within the same job) if it finds the *pgm doesn't exist. I could
see this happening just to avoid the performance hit of constantly trying
to resolve to non-existing *pgms.
On Fri, Jan 24, 2020 at 9:30 AM Rich Loeber <rich@xxxxxxxxx> wrote:
The exit points are very closely tied to the IBM i OS. For many of the
points, making a change in the program requires that you end and restart
a related server function in the IBM i OS. Bringing your system into
restricted state and then restarting will accomplish that but you may
find it too drastic. For the exits, you cannot just recompile a program
and expect the exit to recognize the new program.
Rich Loeber - @richloeber
Kisco Information Systems
On 1/24/2020 9:10 AM, Sune Elvig via MIDRANGE-L wrote:
We have implemented a user exit program and registered the as
QIBM_QSP_SECURITY with format SPSY0200.
The program is implemented in CL.
Today we wanted to change the logic in the program.
I changed the source and recompiled the program.
Now the user exit is not called at all.
We have tried to remove the user exit entirely using RMVEXITPGM and
it again with ADDEXITPGM.--
The user exit program still does not get called even after being removed
Do you have any suggestions?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.