Well, I've been able to determine that triggers appear to be the same on our
system as on the customer box with the OEM software, so therefore likely not
a problem. I compared a system without the OEM software to one that has the
OEM software on it and I don't see much in the way of differences at the
object level. All the triggers are after Insert, update, and delete, and
since I'm just reading that can't be the source of the issue.
I'm going to have to dig into it a bit further to determine why a query
runs great on our system, and fails with trigger issues on the customer box.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Krill, Coy
Sent: Monday, September 25, 2017 2:24 PM
To: Midrange Systems Technical Discussion
Subject: RE: Remove (temporaritly) Triggers
Dspfd will show you the code that created the view or you can pull the code
out of qsys2.sysviews. I'm still on v7r2 so I don't have that collection to
check what the tables are.
Coy Krill
Core Processing Administrator/Analyst
Washington Trust Bank
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: 2017 September 25 12:15
To: 'Midrange Systems Technical Discussion'
Subject: RE: Remove (temporaritly) Triggers
Importance: Low
Would that not disable all the triggers on the system? I'm only after the
ones for the security collection. The rest of them need to stay in place.
So the root question is do we know the names of the tables that are used
with the QSYS2.AUTHORITY_COLLECTION view? Maybe a naïve question, but an
honest one at least. I've not delved into those tables much yet.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Monday, September 25, 2017 2:06 PM
To: Midrange Systems Technical Discussion
Subject: Re: Remove (temporaritly) Triggers
I believe the HA products do this by disabling the triggers. Such as
CHGPFTRG STATE(*DISABLED)
Production:
Trigger Description
Trigger name . . . . . . . . . . . . . . . : TRG QSYS_TRIG_ERPLXF_
____IIM________000002
Trigger library . . . . . . . . . . . . . : ERPLXF
Trigger state . . . . . . . . . . . . . . : STATE *ENABLED
Trigger status . . . . . . . . . . . . . : *OPERATIVE
Trigger event . . . . . . . . . . . . . . : TRGEVENT *INSERT
Trigger time . . . . . . . . . . . . . . : TRGTIME *AFTER
Allow repeated change . . . . . . . . . . : ALWREPCHG *NO
Program Name . . . . . . . . . . . . . . : PGM SYS638B
Library . . . . . . . . . . . . . . . . : ERPLXPTFO
H/A:
Trigger state . . . . . . . . . . . . . . : STATE *DISABLED
Trigger status . . . . . . . . . . . . . : *OPERATIVE
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: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 09/25/2017 02:58 PM
Subject: Remove (temporaritly) Triggers
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Folks:
I am working on a security project where we are using V7R3 and the authority
collection capability. The goal is to analyze the data and set up object
access in a much better way.
The Customer has purchased several products from Help Systems, to bolster
their tooling, to which I have no problem at all, they are very reasonable
products, they do however present a challenge. Apparently they put
several
triggers on the database tables that QSYS2.AUTHORITY_COLLECTION uses, so we
cannot write our own SQL against it to do any special reporting we might
wish to do that might not be included in the tooling.
How do I disable the trigger(s) temporarily? I thought CHGPFTRG would work
but I have not been successful yet.
--
Jim Oberholtzer
Agile Technology Architects
--
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
--
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 electronic mail message and any attachments may contain confidential or
privileged information and is intended for use solely by the
above-referenced recipient. Any review, copying, printing, disclosure,
distribution, or other use by any other person or entity is strictly
prohibited under applicable law. If you are not the named recipient, or
believe you have received this message in error, please immediately notify
the sender by replying to this message and delete the copy you received
---------------------------------------------------------------------
--
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
midrange.com
