Re: Object authority issues -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Yep, both are *OWNER. So, that's not it, right?

Here's the command used to create the object...

CRTSQLRPGI OBJ(&OBJLIB/ProgramName) tgtrls(&TgtRls) +
           SRCFILE(&SRCLIB/QRPGLESRC) COMMIT(*NONE) +
           OBJTYPE(*MODULE) CLOSQLCSR(*ENDMOD) +
           DBGVIEW(*SOURCE) USRPRF(*OWNER) +
           DYNUSRPRF(*OWNER)
CRTPGM     PGM(&OBJLIB/ProgramName) MODULE(ProgramName +
           QCAPCMD) ACTGRP(*CALLER) ALWLIBUPD(*YES) tgtrls(&TgtRls) +
USRPRF(*OWNER)

Besides, the error is saying the user does not have authority to the program object, not that he has no access to the SQL files embedded.

Best Regards,

Thomas Garvey

On 10/11/2021 12:23 PM, Mark Waterbury wrote:

Thomas,

For embedded SQL, created with the CRTSQLxxxI commands, there are two separate "adopt user profiles" you must deal with:

User profile . . . . . . . . . . USRPRF *NAMING
and
Dynamic user profile . . . . . . DYNUSRPRF *USER

The "Dynamic" one is used for dynamically PREPAREd and EXECUTEd SQL statements, versus the normal "static" SQL.

Prompt the CRTSQLRPGI command, press F10, then F9, and then put the cursor in those parameter fields and press F1=Help to read all about it.

Mark S. Waterbury

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.