DFS2971W OLR INITIALIZATION|RESUMPTION FAILED FOR NAME=partname MASTER=mastername PST=pstnumber RC=xx RS=yyOR DFS2971W OLR TERMINATED FOR NAME=partname MASTER=mastername PST=pstnumber RC=xx RS=yyOR DFS2971W OLR WILL NOT BE RESUMED FOR NAME=partname MASTER=mastername PST=pstnumber RC=xx RS=yy

Explanation

First form of the message: For the reason indicated by the return and reason codes, the HALDB online reorganization did not complete the OLR initialization process to either start or resume the OLR.

Second format of the message: For the reason indicated by the return and reason codes, the OLR terminated before all records were copied from the input to the output set of data sets.

The message text includes the name of the master (mastername), the program specification block number (pstnumber), and the return and reason codes. For the exact cause of the termination, see the return and reason codes in the following table:
Table 1. Return and reason codes for DFS2971W
Return code (hex) Reason code (dec) Description

04

(module: DFSORP00)

 04 Unexpected return code from ISWITCH
08 DFSBCB GET for QSAV failed
12 DFSCWU create work unit failed
16 IMS was restarted with COLDSYS, COLDBASE, or COLD START.
20 Restart authorization failed.
24 Deferred stop or close due to error during XRF takeover
28 LCRE enqueue failed.
32 The SET ownership call failed; possible causes:
  • The partition database is not capable of having OLR run against it.
  • The REORG INTENT flag is set on in the partition database. The partition is being reorganized.
36 The OLR was terminated because FFROLR=D was specified.
40 LSO=Y environment is invalid.

08

(module: DFSORP00 or DFSORP10)

 01 GETMAIN for OLR work area failed. Issued by module DFSORP10.
02 Scheduling of the OLR PSB failed. Issued by module DFSORP10.
03 Output data set creation or validation failed. Issued by module DFSORP10.
04 DFSBCB GET for QSAV failed. Issued by module DFSORP10.
05 Timer ITASK creation failed. Issued by module DFSORP10.
06 Database in error because backout failed. Issued by module DFSORP10.
17 Another command is in progress. Issued by module DFSORP00.
90 Internal error. The command entered is not processed because of an internal error.
C6 OLR scheduling failed. Issued by module DFSORP00.
1E7 Unsupported DBD changes detected. The ACB member for the specified database contains a structural change that is not supported by the ALTER option. See message DFS1849E for the reason code that identifies the unsupported change.
1ED Required internal HALDB control blocks were not initialized or accessible. Issued by module DFSORP00.
1EE Alter processing could not be resumed on this IMS system because all partitions that remain to be altered are owned by one or more other IMS systems. Issued by module DFSORP00.
254 OLR scheduling failed due to partition selection exit-routine that was not found or not loaded.
8031 Open error for partition. Issued by module DFSORP10.

0C

(module: DFSORP10)

   Partition selection failed
8031 Open error for partition
C030 Authorization failure
Cxxx Other partition selection failures

10

(module: DFSORP10)

 nnnn Pseudoabend during partition selection (decimal value). The value of nnnn is the abend code returned by the issuing module. For more information about the cause of the abend, see IMS abend codes.

14

(module: DFSORP10, for errors detected in DFSORP20)

 01 A /TERMINATE OLREORG command with no options was initiated.
02 Buffer handler call for PHDAM failed
03 Buffer handler call for PHIDAM failed
04 GBIDP lock failure during cursor update
05 GZIDP lock failure during cursor update
06 Buffer handler failure during cursor update
07 Notify failure during cursor update
0A Duplicate key found during key-sequenced data set (KSDS) insert in the primary index database
0B Update Data Set Control Block (DSCB) failed

18

(module: DFSORP10, for errors detected in DFSORP20)

 nnnn Pseudoabend during DFSORP20 processing (decimal value). The value of nnnn is the abend code returned by the issuing module. For more information about the cause of the abend, see IMS abend codes.

1C

(module: DFSORP10, for errors detected in DFSORP30)

 nnnn Backout failure. The value of nnnn is the abend code returned by the issuing module. For more information about the cause of the abend, see IMS abend codes.
02 OLR terminated by a /TERMINATE OLREORG command with the FORCE option
03 Key with all X'FF' found, or error doing chain maintenance
04 OLR termination with the ABORT was initiated.

20

(module: DFSORP10, for errors detected in DFSORP30)

 nnnn Pseudoabend during DFSORP30 processing (decimal value). The value of nnnn is the abend code returned by the issuing module. For more information about the cause of the abend, see IMS abend codes.

24

(module: DFSORP10, for errors detected in DFSORP30)

 status code Unexpected status code from internal DL/I call
28 LCRE enqueue failed
28 nnnn HALDB online reorganization error occurred. Termination was initiated. A pseudoabend was set.

The value of nnnn is the abend code returned by the issuing module. For more information about the cause of the abend, see IMS abend codes.

28

(module: DFSORP10, DFSDOCA0)

 04 The OLR for the named partition is not automatically resumed during the restart of the failed subsystem due to Fast Database Recovery processing.
Important: A PST=00000 indicates the DFS2971W message was issued when not running under a dependent region PST, such as during Fast Database Recovery processing or during OLR initialization before ITASK creation.

System action

First format of the message: For an INITIATE OLREORG command that tried to start a new online reorganization, the cursor-active status is not recorded in the RECON. In this case, the database records in the partition are still contained in the original set of data sets that were in use before the command was entered.

For an automatic or command-initiated resumption of an online organization for which the cursor-active status was already recorded in the RECON:
  • The cursor-active status is still in effect.
  • The database records in the partition are still contained in two sets of data sets, both of which are required for continued use of the partition.
  • No additional database records were copied from the input to the output set of data sets.

Second form of the message: The cursor-active status for the partition was already recorded in the RECON, and the database records in the partition are still contained in two sets of data sets, both of which are required for continued use of the partition.

System programmer response

After the problem is corrected, start or resume the HALDB online reorganization with the INITIATE OLREORG command or else run an offline reorganization.

Problem determination

1, 6, 27

Module

DFSORP00, DFSORP10 (For errors detected in DFSORP20, DFSORP30)