|
From ACS she gets "Journal not found". From the green screen it works ifshe has *OBJEXIST but returns a not-authorized error if she does not.
Can they run that same SQL from the (shudder) green screen STRSQL?
--
Bryan Dietz
On Nov 9, 2017, at 7:57 AM, Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx>wrote:
schema
Is anyone familiar with the object authorities needed to view the journal
entry details through ACS? We're on ACS version 1.1.7.1 Build 7290.
Our developers are able to do DSPJRN from the green screen but when they
try to view it through ACS they get an SQL exception window.
SQL State: 58004
Vendor Code: -443
Message: {SQL0443] Not authorized to object AAJ001OEX in OEXPRJRN
Cause . . . . . : Either a trigger program, external procedure, or
external function detected and returned an error to SQL. If the error
occurred in a trigger program, the trigger was on table QDBSSUDF2 in
QSYS. If the error occurred in an external procedure or function, thetext
external name is QDBSSUDF2 in schema QSYS. The associated text is Not
authorized to object AAJ001OEX in OEXPRJRN.. If the error occurred in a
trigger program, the associated text is the type of trigger program. If
the error occurred in an external function, the associated text is the
of the error message returned from the external function.to
*PUBLIC has *USE authority to the *SRVPGM QSYS/QDBSSUDF2.
*PUBLIC has *USE authority to the journal library OEXPRJRN and has all
authority to the journal except for *OBJEXIST and *OBJALTER.
They are able to view the journal in the development partition where
*PUBLIC has *CHANGE authority to the journal library and *ALL authority
the journal. I'm hesitant to give *ALL authority to the productionjournal
and would like to reduce it in development.list
Thanks,
Gord
--
Gord Hutchinson
TST Overland Express
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxquestions.
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
link: http://amzn.to/2dEadiD
Help support midrange.com by shopping at amazon.com with our affiliate
--
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
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.