I've worked with QIBM_QZDA_SQL1 , QIBM_QZDA_SQL2 and QIBM_QZDA_INIT
Exit Points and both have same issue. I have a CL configured as an
Exit Point Program to record all SQL connections and I've tried even
killing running jobs, ending *DRDA, *DDM, host server *DATABASE,
Prestart Jobs, bringing down QUSRWRK and all sort of strange things.
Sometimes it worked, sometimes not.
El jue., 23 ago. 2018 a las 9:47, Rob Berendt (<rob@xxxxxxxxx>) escribió:

I think Diego was just being more inclusive and trying to get all possible
jobs which may be using that exit point.
But if what you're doing is working for you then all is good.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "DrFranken" <midrange@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 08/23/2018 10:36 AM
Subject: Re: RMVEXITPGM needs an IPL??
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



So the KB seems to conflict with what Diego mentions. It does not say
anything about an IPL being required.

From the KB:

"Exit program(s) removed after a job has started may continue to be
called for that existing job."

This is exactly what I expected would happen. It's not perfect but far
better than requiring an IPL. At least NEW jobs would no longer be
impacted by the exit point thus 'Stopping the bleeding'

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 8/23/2018 10:24 AM, Rob Berendt wrote:
Look it up in the Knowledge Center <ducking and running...>

Exit program(s) removed after a job has started may continue to be
called
for that existing job.

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/apis/xopendbf.htm


Rob Berendt

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD




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.