Re: Trigger blocking

Peter,

A perfect block would probably be faster, although I don't know how
significant it would be. As you say, it would also have major audit
implications.

I just read the MTU (Memo To Users) for each release, but since we're still
back at 6.1 (and compiling back to V5R4), it's not that important to me...
:(

Rory

On Wed, Aug 29, 2012 at 5:47 PM, Peter Connell <Peter.Connell@xxxxxxxxxx>wrote:

Rory,
Yes I should have said mentioned it rather than described it.
My solution works very well, ( I use a pointer to a flag in a *USRSPC). A
perfect block would be better and faster although the ability to block a
trigger may have serious audit implications.
I'm not always up to speed with the potential benefits of each OS release.
Peter

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Rory Hewitt
Sent: Thursday, 30 August 2012 12:35 p.m.
To: RPG programming on the IBM i / System i
Subject: Re: Trigger blocking

Peter,

Actually, you didn't 'describe the mechanism' - you just said it '[...]the
trigger is designed to abort immediately where there is an exemption.'. I
don't know exactly what method you're using, and whether I or anyone on
this list can come up with a method which might be simpler or provide
better performance than what you're currently getting. I don't know whether
you're asking the question because you're simply looking for a supported
system solution or because your current user-defined solution isn't working
as well as you would like.

That all being said, the quick answer is that unfortunately, there is no
'system' means of disabling a trigger at the job-level.

Rory

On Wed, Aug 29, 2012 at 4:57 PM, Peter Connell <Peter.Connell@xxxxxxxxxx

wrote:

Rory,
There are always concurrent apps that must not be blocked so option 1
is not possible.
I've already described the mechanism I use instead of option 2.

What I'm really asking is if IBM have since exposed a method to the
user domain that can set some switch that they may already deploy
within the system domain.

Peter

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.


#####################################################################################

This correspondence is for the named person's use only. It may contain
confidential
or legally privileged information, or both. No confidentiality or
privilege is waived
or lost by any mistransmission. If you receive this correspondence in
error, please
immediately delete it from your system and notify the sender. You must not
disclose,
copy or rely on any part of this correspondence if you are not the
intended recipient.
Any views expressed in this message are those of the individual sender,
except where
the sender expressly, and with authority, states them to be the views of
Veda.
If you need assistance, please contact Veda on either :-
Australia 1300-762-207 or New Zealand +64 9 367 6200
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.