"Larry Williams" <larryw@ix.netcom.com> wrote in message
news:tkoeovghchv1qjj6k5744ggbich2246n3c@4ax.com...
> I have been installing DB2 for a couple of daya, I'm a member of the
> Partnerword IBM group so we get these cool prebuilt systems on CD, one
> CD just contains DB2 and related stuff, I unzip the file to one of my
> MP3000 drives, connect the catalog, add aliases, and viola, instant
> DB2 7.1, so I fire it up, and spend the morning happiliy doing "GRANT
> SYSADM to user" using steplibs to the new libs. Then I IPL to add the
> entries ti linklist (yea, I know you can dynam that stuff, but I
> wanted a nice clean clpa, clean CSA, etc)
>
> after that all my Grant attempts just get this mess:
>
> Rollback done
> SQLCODE : -805 DSNTIAR
> CODE : 0
>
> DSNT408I SQLCODE = -805, ERROR: DBRM OR PACKAGE NAME
> S390LOC..ADBMAIN.16524BA-
> D043195D0 NOT FOUND IN PLAN ADB. REASON 03
> DSNT418I SQLSTATE = 51002 SQLSTATE RETURN CODE
> DSNT415I SQLERRP = DSNXEPM SQL PROCEDURE DETECTING ERROR
> DSNT416I SQLERRD = -250 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
> DSNT416I SQLERRD = X'FFFFFF06' X'00000000' X'00000000'
> X'FFFFFFFF'
> X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION
>
> All I changed was PROG00 and the list of HFS data mounts, just like
> the parmlib on the prebuilt system shows, and note the s390loc and
> adbmain have two dots between them.
>
> I then reloaded the db2 pack, no difference, put the old parmlib
> changes back, no help... HELP!!!!!
>
> TIA
> Larry

The DB2 package name with the problem is D043195D0, which may also be the
program name if you can figure out what the program is, it might help.

Note for future reference that the reason code is 03.

You can look up -805 (reason code 03) in the Messages and Codes manual. It
should be on your CD in PDF format, but if you don't have one, it can be
downloaded from the IBM site. I looked at it and I doubt you can fix it if
you are not familiar with DB2 and the application.

I assume you have IBM support with this software, so I would call them.