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" <annoir@gmail.com> wrote in message
news:1177008486.811269.33370@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
>