DFS047A UNABLE TO OBTAIN AUTHORIZATION FOR DATA BASE xxxxxxxx. REASON CODE = zz. PSB= psbname.

Explanation

IMS was unable to obtain database authorization for the database identified by xxxxxxxx. The database appears in one of the DB PCBs contained in psbname during PSB scheduling. The PSB name only appears in the message text if the IMS is an online control region.
Code (hex)
Meaning
01
The requested state and the current authorization state (see RECON data set) are incompatible. The database is authorized by another active or abnormally terminated IMS subsystem, and its authorization state is incompatible with the current authorization request.
02
The database is not registered in the RECON data set.
03
The database is marked as prohibiting further authorization for one of the following reasons: a global /DBRECOVERY, a global /STOP, an UPDATE DB STOP, or a CHANGE.DB(NOAUTH) command.
04
The database is authorized only if the requested state is "READ" or "READ-GO" because of a global /DBDUMP or an UPDATE DB STOP(UPDATES) command.
05
The database is marked as needing an image copy.
06
The database is marked as needing recovery.
07
The database is marked as needing backout. In a data sharing environment, you can use a LIST.DB command to determine which subsystems require back outs for the named database.
08
For sharing within a host, the requesting subsystem is not within the authorized host.
09
One or more subsystems for which the database has been previously authorized are supposed to be active, but the subsystems are not known to IRLM. IRLM=N or another IRLM name might have been specified on the subsystem.
10
The database has been previously authorized to the subsystem.
11
An invalid parameter is found during the database usage compatibility evaluation process. Possibly, the database record in the RECON data set is bad.
12
The current authorization state in DBRC is invalid because of a not authorized error.
13
An error occurred in DBRC while trying to process an authorization request.
14
An error occurred in DBRC while trying to process a change authorization request.
15
The database is already authorized to an active IMS subsystem.
16
The area is not marked as needing recovery for the DEDB initialization utility.
18
The Fast Path area is currently being altered.
19
The data set name of the database data set passed to DBRC does not match the data set name in the RECON data set.
20
Database authorization failed because the database was not registered with DBRC. In addition, the DBRC RECON data sets were initialized with FORCER, which requires that all databases must be registered.

This error might be the result of a mismatch of data set names in the RECON data set and in the dynamic allocation blocks (DFSMDA members).

22
The database is currently authorized to another subsystem.
31
The definition of the HALDB has changed. You must perform a partition structure rebuild before authorization can be granted for the partition. Issue a /START DB command with the OPEN keyword for the HALDB master to perform the rebuild
32
The HALDB needs to be initialized.
33
An attempt has been made to authorize the HALDB master. Authorization can only be requested at the partition level.
34
Partition Initialization is requesting authorization for a partition that does not need to be initialized.
35
The DB partition cannot be authorized until a high key is defined. A key is required because the HALDB master does not use a Partition Selection Routine.
36
Image copy not allowed during HALDB OLR processing.
37
Loading into an M-through-V DBDS of a partition database is not allowed.
38
Offline reorganization is not allowed when HALDB OLR is active and the HALDB OLR is owned by an IMS subsystem.
39
A HALDB partition database can be reorganized online. This release of IMS does not support running database utilities for OLRCAP databases.
40
Batch jobs are not allowed authorization when the REORG INTENT = ON is set for the database. The database is currently being reorganized. Online image copy also fails authorization.
41
The database is quiesced or in the process of being quiesced.
42
The database is not quiesce held and image copy attempting authorization.
43
The randomizer name that was passed is different from the randomizer name stored in the RECON.
45
The database is in the quiesce HOLDALL state. Both read and write activities are not allowed.
80
The partition name table DFSPNT is not initialized for the specified HALDB partition.
81
An error occurred attempting to load the master DMB for the specified HALDB partition.
82
An error occurred attempting to load a DMB of the altered version of a HALDB partition that is identified by DATA BASE = xxxxxxxx in the message text. Message DFS3547E, which is issued to the system console before message DFS047A, contains information about why the DMB could not be loaded.
83
IMS could not build the internal blocks that are required to access a HALDB partition that has a status of ALTER IN PROGRESS in the RECON data set, therefore authorization to the HALDB partition failed. The partition is identified by DATA BASE = xxxxxxxx in the message text. Message DFS1849E, which is issued to the system console before message DFS047A, identifies the reason that the internal blocks could not be built.

System action

A batch region (DL/I or DBB region) terminates with abend 0047. The database is stopped. Dependent regions continue processing, but programs cannot access the database. An attempt to access the database will result in either a BA status code, if the program has issued the INIT call, or in abend 3303, if the program has not issued the INIT call.

For reason codes 41 and 42, the authorization request is denied.

Programmer response

Reason codes 01 through 09 and 15 through 19, indicating a temporary authorization failure, can be corrected by one of the following actions:
  • Wait for a currently authorized subsystem to terminate or enter a /DBRecovery UPDATE DB STOP(ACCESS) to unauthorize the database from the currently authorized subsystems. Batch backout or an emergency restart might be required for an abnormally terminated subsystem. (RC 01, 08 or 15)
  • Verify that the correct log is input to the batch backout utility if DBRC=C is being used. (RC 01)
  • Enter a /START DB or UPDATE DB START(ACCESS), a /DBDUMP or UPDATE DB START(UPDATES), or a CHANGE.DB (auth) command. (RC 03)
  • Enter a /START DB or UPDATE DB START(ACCESS) command. (RC 04)
  • Run the appropriate IMS utility. (RC 05, 06 or 07)
  • Run this IMS subsystem on the host where the database is currently authorized. (RC 08)
  • Wait for the failed subsystems to complete the emergency restart or database backout. (RC 09)
  • Use the DBRC command CHANGE.SUBSYS to indicate that an IMS subsystem is no longer active. (RC 15)
  • Use the DBRC CHANGE.DBDS command to mark an area as needing recovery. (RC 16)
  • Use the DBRC INIT.DBDS command to register a DBDS or DEDB area to DBRC. (RC 18, 19)
  • Wait for the DEDB Alter utility to complete or use the DBRC CHANGE.DB NOALTER command to indicate the DEDB Alter utility is no longer active (RC 18). If the "QUIESCE" status is set in the RECON, use the CHANGE.DBDS NODBQUI command to reset the quiesce status.
  • In ACBSHR=N environment, the DEDB Alter utility changed the randomizer while the IMS was down.
  • Check the RECON data set to determine the correct authorization state.

Reason codes 10 through 14 indicate that a system error has occurred. If these problems persist, contact IBM® for problem determination assistance.

For reason code 33, check the DBDLIB level of the databases to make sure that they match the RECON level.

For reason codes 41, 42, and 45 wait for the quiesce to end and rerun the job which failed authorization. The status of the database can be determined by issuing /DISPLAY DB QSC, /DISPLAY STATUS DB, or Query DB, or LIST.DB DBD(dbname), and examining the output. If the image copy failed, wait for the quiesce to end or until the QUIESCE HELD flag is set on. You can set the QUIESCE HELD flag on by UPD START(QUIESCE) OPTION(HOLD) command processing when quiesce has occurred.

For reason code 82, see message DFS3547E, which is issued to the system console before message DFS047A.

For reason code 83, see message DFS1849E, which is issued to the system console before message DFS047A.

The incompatibility between the requested state and the current authorization state may be caused by the use of different Lock Managers (PI vs IRLM) when accessing the same database from different IMS subsystems. For more information, see Data sharing software requirementsData sharing software requirements.

Problem determination

35

Module

DFSDBAU0