RE: *SQLPKG created by remote BIND from DB2 z/OS and authorisation

Solved!

Actually, the solution is simple, not to say obvious... As I know the SQL name of the object, all I need to do is use SQL to tell the remote system what I want.

GRANT EXECUTE ON <collection>.<member> TO PUBLIC

Does the trick.

I used DSNREXX to get the SQL across, because that is flexible in how to set up the connection, based on parameters. It does require the DSNREXX SQL package to be bound to the remote location, but that is one-time set-up.

Thanks to all who gave suggestions.

Jantje.



-----Original Message-----
From: Jan Moeyersons <jan.moeyersons@xxxxxx>
Sent: Monday, August 6, 2018 6:09 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: *SQLPKG created by remote BIND from DB2 z/OS and authorisation

Bummer... The name of the object in the library corresponding to the collection is not the name as I see it on the source system. When I bind a member called ETAPOC, the *SQLPKG is called ETAPO00001. If there is only ever a single one, I might get away with it, but as soon as there are more, I am not sure anymore which one it is I need to change the authority on.

Jantje.



-----Original Message-----
From: Jan Moeyersons <jan.moeyersons@xxxxxx>
Sent: Monday, August 6, 2018 12:31 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: *SQLPKG created by remote BIND from DB2 z/OS and authorisation

Yes, it is part of a script. Good suggestion. We could indeed add that command after the object has been created.

Thanks,

Jantje.


-----Original Message-----
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Sent: Saturday, August 4, 2018 6:00 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: *SQLPKG created by remote BIND from DB2 z/OS and authorisation

My question is: How can I go about on mainframe, during program

preparation, to tell the iSeries that the authority on the *SQLPKG
must be different from the default settings?

If this is part of a setup script, there are several ways to run a remote command on IBM i from z/OS.

You could add a short command to do the authority change that way after the script has already created the package.

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately.