Re: ADDEXITPGM issue

[Bruce Vining <bvining@xxxxxxxxxxxxxxx>]

In addition be aware that you are assigning the exit program to the proxy
command in QSYS. Someone could bypass your efforts by directly using
QDEVTOOLS/CRTBNDRPG and/or QSQL/CRTSQLRPGI.

As an aside, this exposure of only changing the proxy commands is one I
find quite often. I just love how some think limiting authority to
QSYS/STRSQL stops me from using STRSQL (I just use QSQL/STRSQL) :)

Bruce Vining

On Wed, Aug 5, 2015 at 12:50 AM, Flensburg, Carsten <Flensburg@xxxxxxxxxx>
wrote:

> Hello Gad,
>
> It seems that you have a blank character between the command name and the
> library name in your PGMDTA parameter:
>
> PGMDTA(*JOB 20 'CRTSQLRPGI QSYS')
>
> The command name occupies 10 bytes, and the library part of the qualified
> command name therefore ends up as ' QSYS', which due to the beginning blank
> character is not a valid object name.
>
> Cheers,
> Carsten
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Gad Miron
> Sent: 5. august 2015 07:33
> To: midrange-l@xxxxxxxxxxxx
> Subject: ADDEXITPGM issue
>
> Hello guys
>
> Need help with the following issue:
>
> Some years ago I created a pre/post-processing method to execute CMDs/PGMs
> embedded in an RPG source before or after compilation (like setting the
> library list, running OPNQRYs, OVRDBF etc.)
>
> This pre-processing is invoked by an exit point attached to  CRTBNDRPG /
> CRTRPGMOD CMDs (thanks to Bruce Vining for his advice) like this:
> ADDEXITPGM EXITPNT(QIBM_QCA_CHG_COMMAND) FORMAT(CHGC0100) PGMNBR(1)
> PGM(ACUMGPL/RPGEXITPGM)
> PGMDTA(*JOB 20 ‘CRTBNDRPG QSYS’)
>
> I now try to do the same for SQLRPGLE programs but the following
>
> ADDEXITPGM EXITPNT(QIBM_QCA_CHG_COMMAND) FORMAT(CHGC0100) PGMNBR(3)
> PGM(ACUMGPL/RPGEXITPGM) PGMDTA(*JOB 20 'CRTSQLRPGI QSYS')
>
> fails with CPF0197 Value  QSYS/CRTSQLRPGI is not a valid name.
>
> oddly, this ADDEXITPGM does accept CRTSQLRPG (Create SQL RPG Program)
>
>
> This communication is intended only for use by the addressee.It may
> contain confidential or privilegedinformation.
> If you receive this communication unintentionally, please inform us
> immediately and delete this e-mail and any attachments.
> Warning: Although we have taken reasonable precautions to ensure no
> viruses are present in this email, we cannot accept
> responsibility for any loss or damage arising from the use of this email
> or attachments.
> --
> 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.