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



If you have a list of users that you only want access to this maybe you
could restrict access to the command either directly or with an authorizaton
list. If you only have 3 folks you want to have access to it then you would
probably want them having access to whether it was QCTL and or QINTER.
Access to the command might be needed in either subsystem. You could
probably get real fancy with some sort of exit program but not sure totally
what you want to do.

On Wed, Sep 15, 2010 at 10:32 PM, Chamara Withanachchi
<chamaraw@xxxxxxxxxx>wrote:

Dear All,

I want to restrict PWRDWNSYS command to be entered only from the QCLT,
DSP01
how can I achieve this. Will QIBM_QWC_PWRDWNSYS Exit point can be used for
this purpose?


--
Regards,

Chamara Withanachchi
IBM Certified Power System Expert
RPG Programmer
(owner of www.rpgiv.info)

WWW.RPGIV.INFO <http://www.rpgiv.info/>
Mob: +94 77 1678646
chamaraw@xxxxxxxxxx

i want to be future ready. i want control. i want an i.
--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



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.