DB2 subsystem again giving problem

This forum provides the support of Dezhi Mainframe systems. Please post your questions about logon, usage of our mainframe environment.

Moderators: sysprog, prino, sfan, steve-myers, Tim001

DB2 subsystem again giving problem

Postby cool123 » Sun 28 Aug 2011, 16:45

DB2 susbystem address spaces running fine ie DB8G* from SDSF are all up.
However DB2 SPUFI and ADMIN TOOL Won't work.
SPUFI gives below error
SUBSYSTEM RESOURCE NEEDED FOR PLAN DSNESPRR, AUTH ID E204949, AND SUBSYSTEM DB8G IS NOT AVAILABLE
FEEDBACK - REASON CODE X'00D70024' TYPE X'00000220' RESOURCE NAME- DSN810.DSNDBC.DSNDB06.SYSUSER.I0001.A001

This shows SPUFI RELATED PLAN DSNESPRR needs rebind,but this rebind won't work until underlying & required VSAM file is recreated
DSN810.DSNDBC.DSNDB06.SYSUSER.I0001.A001 on Z6DB81( like other DB2 related VSAM files which exist on this non SMS managed volume)


Admin tool also shows same error message:
SQLCODE : -923 DSNTIAR CODE : 0

DSNT408I SQLCODE = -923, ERROR: CONNECTION NOT ESTABLISHED: DB2 ACCESS,
REASON 00D70024, TYPE 00000220, NAME DSN810.DSNDBC.DSNDB06.SYSUSER.I0-
001.A001
DSNT418I SQLSTATE = 57015 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNAET03 SQL PROCEDURE DETECTING ERROR

Admin tool also needs rebind of admin tool relted packages, ie ADB.
Again rbind wont work till underlying required vsam files exist.

Due to unknown reasons following VSAM files r corrupted or not existing
DSN810.DSNDBD.DSNDB06.SYSPKAGE.*
DSN810.DSNDBD.DSNDB06.SYSPLAN.*
DSN810.DSNDBD.DSNDB06.SYSUSER.*

These need to be recreated on Z6DB81 volume, same as other DB2 related vsam files exist.This is a non SMS managed volume and only sysprog can do it.
Once done,rebind plan for admin tool and spufi and then DB2 can be accessed using tools or it wont work.
cool123
 
Posts: 6
Joined: Mon 20 Jun 2011, 15:48

Return to Dezhi systems: Mainframe

Who is online

Users browsing this forum: No registered users and 0 guests

cron