Re: Trigger issue with authority

just on the point about the collision. Once i fix the authority issue.

If one user enters a change to the Physical file, lets call it PF1, and the
trigger gets kicked off. The CL takes about 20 seconds to run. recall the
CL, clears the PF used to hold latest data then re-populates via RPG prgram.

After 5 seconds another user makes a change to PF1. the trigger kicks off
again, and it wants to clear the file. Which is still going to run 15 more
seconds. Does the second trigger wait, those 15 seconds and then kicks off?

is there going to be any problem with this?

I much prefer the message queue idea but if the current way will work, they
seem to be ok with the current way.




On Mon, Aug 4, 2014 at 12:15 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 8/4/2014 9:12 AM, Hoteltravelfundotcom wrote:

I had a case happen that the trigger would not run.

the trigger is on a physical file which has 2 logicals to it. I have a

PF

that will be updated when one field in the PF changes.

When change made and trigger is invoked i run a CL program
which clears my work file and then rebuilds it via RPGLE program.

that is all the CL does, CLear and run the RPG.

But got an error CPF3137 NO Authority to clear, initialize etc.

Do I need now to change the authority on that Temp file I created? the
current is

*PUBLIC * CHANGE

The Knowledge Centre has a page which explains what security is required
for which operation: IBM Knowledge Center - Defining how information can
be accessed

http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzarl/rzarlacctyp.htm?lang=en

There is another way to 'clear' the table; use SQL. DELETE FROM TABLE.

--buck

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