Re: Trigger issue with authority

true, it is a perm file. Is there any way this can work, or must I scrap
this idea?

What this is, there is a screen display program that shows orders in
various stages of work, i.e. picking, packing, engraving etc. I had
created a large sql to do the same, but when i ran this SQL in
Crystal reports, it had a limit there of how many lines of SQL you can
have, it passed it. To make views would be more time consuming but maybe is
the best way at this point.

Instead of views, I made an RPG prgram that will create the same data,
basically the same program with just what I need. then the trigger on it.




On Mon, Aug 4, 2014 at 9:35 AM, Briggs, Trevor (TBriggs2) <
TBriggs2@xxxxxxxxxxx> wrote:

It sounds like your work file is a "permanent" file (I.e. it resides in
a library other than QTEMP). If this is true, then your trigger program
seems a trifle perilous. What happens if another user does an update to
the PF and "fires" the trigger when your RPG is rebuilding the work file
from an earlier trigger "fire"?

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Hoteltravelfundotcom
Sent: Monday, August 04, 2014 9:12 AM
To: Midrange Systems Technical Discussion
Subject: Trigger issue with authority

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

i am also on their with *ALL.
--
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 message originates from Lincare Holdings Inc. It contains information
which may be confidential or privileged and is intended only for the
individual or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the
contents of this message.
All personal messages express views solely of the sender, which are not to
be attributed to Lincare Holdings Inc., and may not be copied or
distributed without this disclaimer.
If you received this message in error, please notify us immediately at
MailAdmin@xxxxxxxxxxx or (800) 284-2006.

************************************************************************************************************************************************************************************************************

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