|
It sounds like your work file is a "permanent" file (I.e. it residesin
a library other than QTEMP). If this is true, then your triggerprogram
seems a trifle perilous. What happens if another user does an updateto
the PF and "fires" the trigger when your RPG is rebuilding the workfile
from an earlier trigger "fire"?a
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
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 containsinformation
which may be confidential or privileged and is intended only for thethe
individual or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use
contents of this message.not to
All personal messages express views solely of the sender, which are
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.
list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.