00E50063   

Explanation

A resource access request (RARQ) was issued to a function vector list entry (FVLE) that is valid but unauthorized for this allied user at this time. This abend occurs if a request is issued out of sequence. For example, two consecutive CREATE THREAD requests would give this result. This abend also occurs if a request is issued that is never authorized for the caller. For example, it occurs if a BATCH protocol user issues a PREPARE request. A program call (PC) is issued to module DSN3ABND, which issues the X'04E' abend with this reason code.

System action

The task issuing the RARQ is abended. However, DB2® recovery may translate this abend to a return code 256 with this reason code.

Operator response

Notify the system programmer.

System programmer response

If you suspect an error in DB2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.

Problem determination

This is a user error. The issuer of the RARQ was not authorized to use the requested function at this time. The following diagnostic information is available:
  • An entry in the DB2 trace table is made for entry to module DSN3ABND. The items traced are the RALE and the FVLE of the intended DSNARARQ request. To determine the sequence of DSNARARQ requests, examine the previous trace table entries for the same execution block (EB).
  • An application dump is requested with DB2-supplied control blocks. This includes the FRB associated with the intended DSNARARQ request. Fields FRBRALE and FRBFVLE contains the indexes for the intended request.
Collect the following diagnostic items:
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
  • Dynamic dump, taken to SYS1.DUMPxx data set, by DB2 (04E and 04F abends).
  • SYSABEND, SYSUDUMP, or SYSMDUMP output.
  • Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.