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



Denis,

You may also want to consider writing a :Command Analyzer" exit.  There are two exit points defined, QIBM_QCA_CHG_COMMAND and  QIBM_QCA_RTV_COMMAND, for "Command Analyzer Change" and "Command Analyzer Retrieve" respectively.

Using these exits, you can examine all of the  parameters passed to any (registered) command, and you can change parameter values  before the  command executes.   (You could even run an entirely different command.)

See:
    http://www.securemyi.com/articles/artcmdexit1.htm
and
http://www.securemyi.com/articles/artcmdexit2.htm

for examples of how to use these exits.

Hope that helps,

Mark S. Waterbury

> On 10/6/2017 3:12 PM, Denis Robitaille wrote:
Thanks for the info.

I was hoping of a way to stop the change from happening but I have to agree with your interpretation and the one from other who responded.

Thanks again for your response.


Denis Robitaille
Chef de service TI – Solution d’entreprise
Infrastructure et opérations

CASCADES CENTRE DES TECHNOLOGIES
412 Marie Victorin
Kingsey falls(Québec) Canada J0A 1B0
Tél : 819 363 6100 Poste :52130
Cell : 819 352 9362


-----Message d'origine-----
De : MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Bruce Vining
Envoyé : 6 octobre 2017 14:53
À : Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Objet : Re: Looking fo an exit point format definition

As there is no feedback interface to tell the system "don't do it" I would be tempted to use format CHGP0100 and if I see a value of *NO for PWDEXP to issue a CHGUSRPRF setting the value back to *YES. I have done such a thing (though not for PWDEXP) in the past. I one item I would suggest is that if you're thinking of implementing the exit program using RPG you may want to consider having a CL front end to the RPG program and adding a parameter when calling the RPG program so that the RPG program can return the CHGUSRPRF command to run, and then run it out of the CL program (assuming the added parameter is not all blanks). If you try to run the CHGUSRPRF out of the RPG program you may find yourself in recursive calls...

On Fri, Oct 6, 2017 at 1:10 PM, Denis Robitaille < denis_robitaille@xxxxxxxxxxxx> wrote:

Hello all,

I want to write an exit program to be called when the CHGUSPRF command
is called.

I found out that the exit point is QIBM_QSY_CHG_PROFILE It has 2
format. I want to use the CHGP0200 format which is used before the
changed is made to the user profile.

But, for the love of me I can not find the definition of this format.
I tried looking in the Knowledge center, numerous google search and I
come up empty.

Can anyone point me in the right direction?

Thanks

[cid:image001.jpg@01D1F7D9.2487F9B0]<http://www.cascades.com/_home>

Denis Robitaille
Chef de service TI - Solution d'entreprise Infrastructure et
opérations

CASCADES CENTRE DES TECHNOLOGIES
412 Marie Victorin
Kingsey falls(Québec) Canada J0A 1B0
Tél : 819 363 6100 Poste :52130
Cell : 819 352 9362



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



--
Regards,
Bruce
--
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 ...

Follow-Ups:
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.