DFS3303I PSB psbname PCB pcbname DBD dbdnamexxxx JOBNAME jobnameRGN nnn

Explanation

This message precedes pseudoabend 3303 when an application program scheduled with PSB psbname tries to make an incompatible DL/I call to database PCB psbname. During DL/I scheduling of the PSB, database dbdname had condition xxxx. Depending on the condition, DL/I calls to this database are partially or totally restricted.

This message precedes only those 3303 abends caused by DL/I attempts to access data in a database that was unavailable when the program was scheduled, and the program had not issued the DL/I INIT STATUS call.

xxxx is one of the following:
CF FAIL
A coupling facility failure occurred. The database cannot be accessed until recovery is done and data sharing resumes.
INVDBVER
An invalid version number for a full-function database was specified on a PCB or an INIT VERSION call that was issued by the application program. The specified database version number must be equal to or less than version number of the current database that is active in the IMS system. Also, a database version cannot be specified on a PCB if database versioning is not enabled. Database versioning is enabled by specifying DBVERSION=Y in the database section of the DFSDFxxx PROCLIB member.
INVDBCHG
The current database structure of a full-function database contains a change that is not supported by database versioning. Prior versions of the database are incompatible with the current version and can not be accessed. The changes that are supported by database versioning are:
  • Increasing the size of a segment
  • Adding new fields without changes made to existing fields
LOCKED
The identified database was security locked using the /LOCK command.
NOACCESS
The database ACCESS was set to "RO" and the PCB processing intent (PROCOPT) was greater than "GO". Since ACCESS "RO" only allows database read without integrity, any processing intent implying integrity is not valid.
NOCATALG
The IMS catalog is not enabled. Database versioning requires the IMS catalog.
NO DBRC
The PCB pcbname refers to a HALDB, but the use of DBRC was suppressed for this batch job.
NODELETE
DL/I DLET calls to this database were not allowed at scheduling because a restricted or unavailable database was involved in a logical relationship or a secondary index. Delete calls cannot be processed because they can require updating of a logically related or secondary index database that is unavailable or is unavailable for update.
NOTAUTHD
At the time of DL/I scheduling, the database was not authorized, or could not be authorized by DBRC. Message DFS047A was issued. DL/I does not allow any calls to this database.
NOUPDATE
Either the database ACCESS for the identified database was RD, or a /DBD command was issued for the database. When the database ACCESS is RD (either explicitly, or implicitly because of a /DBD command), DL/I calls such as ISRT, REPL, or DLET are not allowed. This condition can also be caused by unavailable or restricted access to a logically related or secondary index database that might have to be updated on an ISRT, REPL, or DLET call.
NOUPDRRL
An unauthorized user tried to update a database that is using Restricted Update mode. The database has RREPL set to ABEND. If it is a full-function database, DFS3303I message is issued with the keyword NOUPDRRL and with the 3303 abend that indicates that updates are not possible when RREPL is enabled.
NOSTORAG
A storage error occurred while building the internal blocks that are required to satisfy a request for a version of a full-function database other than the current version.
NOVERFND
The requested version of a full-function database cannot be found in the IMS catalog.
PARTUNAV
An attempt was made to reference a partition in the HALDB database indicated by dbdname, but the partition was unavailable.
STOPPED
A /STOP or a /DBR command was issued against the identified database. DL/I does not allow database access when the database is stopped.
SYSTEM
The IMS system made the database temporarily unavailable. One possible reason is that an XRF takeover occurred, and the database must be reverified.

System action

The IMS online dependent region identified by OS jobname and region number is abnormally terminated.

If a BMP, the region is terminated with abend 3303, but for an MPP, the database is stopped, but the region is not terminated.

The message being processed is placed on the suspend queue unless the SERIAL=YES option was specified on the TRANSACT macro. In this case, the transaction is stopped. When a message is placed on the suspend queue for the first time, a counter for the transaction is incremented by one.

Operator response

(master terminal) Correct the database condition; then start the database.

To drain the suspend queue and reset USTOPPED status for those transactions processed by programs authorized to access the started database, issue the /START DATABASE or UPDATE DB START(ACCESS) command.

To drain the suspend queue for the started transaction and reset the USTOPPED status, issue the /START TRAN or UPDATE TRAN START(SUSPEND) command.

To drain the suspend queue for all transactions, issue the /DEQ SUSPEND command.

For more information about how the suspend queue works, see IMS Version 15.6 System Administration.