RE: Stop users from pressing C during session error

Hey,

So that means we can either prohibit the reply 'C' for some messages, if not, at least notify the IT department without the user knowing!

What is meant exactly by <For some inquiry messages,> ? Is there a list of these messages?

Has anyone written a reply handling exit program that they'd like to share?

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Bruce Vining
Envoyé : jeudi 4 juin 2009 01:20
À : 'Midrange Systems Technical Discussion'
Objet : RE: Stop users from pressing C during session error

On the first part:

If you are on V5R2 or later and want to be informed of (or
override/prevent) inquiry message responses then you might be
interested in
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/
apis/XREPLY.ht
m

If you are on V6R1 and want to prevent the user from even
seeing the inquiry message then you might be interested in
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/
apis/xinqext.h
tm This exit was covered in my V6R1 API Update at COMMON,
Summit, and elsewhere.

Bruce Vining

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tom Liotta
Sent: Tuesday, June 02, 2009 4:19 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Stop users from pressing C during session error

David FOXWELL wrote:

<snip users replying 'C' to errors...>

Is there a way of preventing users from doing this kind of

thing, or

at

least a way of getting informed when the information gets logged?

David:

For the first part, preventing the users from doing what?
Replying with a 'C'? or seeing such a message in the first place?

The unfortunately correct answer is not to allow such
messages ever to be sent. Instead, handle the problem that
results in the message.
There are lots of ways to set up handlers for both expected
and unexpected conditions.

There is at least one vendor -- Tango/04 as noted earlier (a
PowerTech partner) -- that has a product related to this, but
I don't know enough about it to say if it applies. I'm not
aware of other vendors though there might be ones.

For the second part, at least one thought comes to mind. Rob
noted that initial programs can be set for users but not
termination programs. I suppose something like a *JOB scope
message function could be set up by an initial program (or
routing program or
elsewhere) that examines the joblog before closing down.
Messages might then be forwarded to an appropriate destination.

It's just an idea. Maybe it will spark others.

Tom Liotta

--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone 253-872-7788 x313
253-479-1416
Fax 253-872-7904
http://www.powertech.com
--
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.

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