By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,947 Members | 1,594 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,947 IT Pros & Developers. It's quick & easy.

Unable to Build Stored Procedure

P: n/a
I am trying to create a stored procedure using the DB2 Connect
Development Center. I am able to create the project, connect to the
remote database on the mainframe and create the stored procedure.
However, when I build I get the following message:

[IBM][CLI Driver][DB2] SQL0567N "I01" is not a valid authorization
ID. SQLSTATE=42503
I01.ED_MAINLINE_PERSON - Build failed.

The options for the database connection are as follows:

SQL ID = I01
Package Owner = I01
Build Owner = I01

These are identical to what another programmer uses who can build
stored procedures. We've checked the ACF permissions on the mainframe
and I have the identical rights as the other programmers.

We are stumped and it clearly appears to be some sort of access
problem but we can't figure out what is missing.

One of the programmers had me try and set the current SQL ID in the
command editor and I was unable to. She thought this was significant
but we don't know how to address this.

Help!

Ann Williams

Apr 19 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Hi,

This is a RACF problem. The fact that you cannot issue the command SET
CURRENT SQLID='IO1' means that you do not belong to the RACF group of IO1 -
In the mainframe, do a TSO LU command and it will list out all your groups
that you are allowed to. Ask your RACF administrator to display all the
userids of those who belong to the 'IO1' group.

The other facet is that if you are accessing the mainframe via the JDBC/ODBC
driver, there is an implied userid associated with this and it is quite
possible that this implied userid does not belong to the RACF group of
'IO1'. Did you connect passing a specific userid with password and does this
userid have the privileges associated with creating a procedure, for example
GRANT CREATEIN TO SCHEMA XX blah blah....

HTH,
Ven Ilagan
Sydney
"annoir" <an****@gmail.comwrote in message
news:11*********************@l77g2000hsb.googlegro ups.com...
>I am trying to create a stored procedure using the DB2 Connect
Development Center. I am able to create the project, connect to the
remote database on the mainframe and create the stored procedure.
However, when I build I get the following message:

[IBM][CLI Driver][DB2] SQL0567N "I01" is not a valid authorization
ID. SQLSTATE=42503
I01.ED_MAINLINE_PERSON - Build failed.

The options for the database connection are as follows:

SQL ID = I01
Package Owner = I01
Build Owner = I01

These are identical to what another programmer uses who can build
stored procedures. We've checked the ACF permissions on the mainframe
and I have the identical rights as the other programmers.

We are stumped and it clearly appears to be some sort of access
problem but we can't figure out what is missing.

One of the programmers had me try and set the current SQL ID in the
command editor and I was unable to. She thought this was significant
but we don't know how to address this.

Help!

Ann Williams

Apr 20 '07 #2

P: n/a
On Apr 20, 2:29 am, "Ven Ilagan" <vcila...@optusnet.com.auwrote:
Hi,

This is a RACF problem. The fact that you cannot issue the command SET
CURRENT SQLID='IO1' means that you do not belong to the RACF group of IO1 -
In the mainframe, do a TSO LU command and it will list out all your groups
that you are allowed to. Ask your RACF administrator to display all the
userids of those who belong to the 'IO1' group.

The other facet is that if you are accessing the mainframe via the JDBC/ODBC
driver, there is an implied userid associated with this and it is quite
possible that this implied userid does not belong to the RACF group of
'IO1'. Did you connect passing a specific userid with password and does this
userid have the privileges associated with creating a procedure, for example
GRANT CREATEIN TO SCHEMA XX blah blah....

HTH,
Ven Ilagan
Sydney"annoir" <ann...@gmail.comwrote in message

news:11*********************@l77g2000hsb.googlegro ups.com...
I am trying to create a stored procedure using the DB2 Connect
Development Center. I am able to create the project, connect to the
remote database on the mainframe and create the stored procedure.
However, when I build I get the following message:
[IBM][CLI Driver][DB2] SQL0567N "I01" is not a valid authorization
ID. SQLSTATE=42503
I01.ED_MAINLINE_PERSON - Build failed.
The options for the database connection are as follows:
SQL ID = I01
Package Owner = I01
Build Owner = I01
These are identical to what another programmer uses who can build
stored procedures. We've checked the ACF permissions on the mainframe
and I have the identical rights as the other programmers.
We are stumped and it clearly appears to be some sort of access
problem but we can't figure out what is missing.
One of the programmers had me try and set the current SQL ID in the
command editor and I was unable to. She thought this was significant
but we don't know how to address this.
Help!
Ann Williams- Hide quoted text -

- Show quoted text -
Thanks! I will pass this information along to our administrator.

Annie

Apr 20 '07 #3

P: n/a
On Apr 19, 11:48 am, annoir <ann...@gmail.comwrote:
I am trying to create a stored procedure using the DB2 Connect
Development Center. I am able to create the project, connect to the
remote database on the mainframe and create the stored procedure.
However, when I build I get the following message:

[IBM][CLI Driver][DB2] SQL0567N "I01" is not a valid authorization
ID. SQLSTATE=42503
I01.ED_MAINLINE_PERSON - Build failed.

The options for the database connection are as follows:

SQL ID = I01
Package Owner = I01
Build Owner = I01

These are identical to what another programmer uses who can build
stored procedures. We've checked the ACF permissions on the mainframe
and I have the identical rights as the other programmers.

We are stumped and it clearly appears to be some sort of access
problem but we can't figure out what is missing.

One of the programmers had me try and set the current SQL ID in the
command editor and I was unable to. She thought this was significant
but we don't know how to address this.

Help!

Ann Williams
Hi Ann,

In addition to what Ven said, you need to talk to your administrator
about setting up the Work
Load Manager environment. There is a good chapter in the redbook:
"DB2 for z/OS Stored Procedures,
Through the Call and Beyond", http://publib-b.boulder.ibm.com/abst...7083.html?Open.
that deals with setting up your mainframe for access by DB2
Development Center.

Marichu Scanlon
IBM

Apr 22 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.