MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

Re: The maximum number of statements has been reached for the



fixed

Hello Chuk and Charles

When configuring the OLEDB for DB2 Provider you need to supply a (as400)
user & password.
I specified a pseudo user profile we use only for DB gateways.
This User profile did not have the required authority to create SQL
Packages.
So, I temporarily granted this USRPRF a *SECADM autority , created the SQL
packages and then revoked the *SECADM authority.
the Packages created were MSCS001, MSNC001, MSRR001,
MSRS001, MSUR001
Afterwards I ran the GRTOBJAUT for each of these Packages adding Public
*All Aut.

There is no Default library - you have to specify the Library for the
SQLPKGs.

Incidently, I did not choose QGPL but rather a MYQGPL Library
because when upgrading to a new machine I copy all user Libs but I try not
to migrate all of QGPL so old unused objects in QGPL will not be copied to
the new machine.

Thanks again
Gad




On 22-Mar-2014 08:51 -0700, Gad Miron wrote:

I've found that the SQL Packages were not created in the first place
due to lack of authority.
Once authority was granted I've managed to successfully configure
the Linked Server and it is working fine (so far).


For the archives, for the benefit of others who might follow, perhaps
what was the Grant Object Authority (GRTOBJAUT) [or similar] request
performed to effect the [presumed] resolution, could be included.? I
suspect possibly, something like the following was required\effected,
because the SQL packages default to being created in the library QGPL?:

GRTOBJAUT OBJ(QGPL) OBJTYPE(*LIB) USER(whomever) AUT(*ADD)

--
Regards, Chuck


Additionally for the archives...

You can specify on the ODBC/OLEDB/JDBC drivers where you want packages
created. You don't have to take the default. So if you run into a
security team that hesitant to give you authority to the default. You can
always create your own.

Charles


On Sat, Mar 22, 2014 at 7:00 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

On 22-Mar-2014 08:51 -0700, Gad Miron wrote:

I've found that the SQL Packages were not created in the first place
due to lack of authority.
Once authority was granted I've managed to successfully configure
the Linked Server and it is working fine (so far).


For the archives, for the benefit of others who might follow, perhaps
what was the Grant Object Authority (GRTOBJAUT) [or similar] request
performed to effect the [presumed] resolution, could be included.? I
suspect possibly, something like the following was required\effected,
because the SQL packages default to being created in the library QGPL?:

GRTOBJAUT OBJ(QGPL) OBJTYPE(*LIB) USER(whomever) AUT(*ADD)

--
Regards, Chuck
--
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.








Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact