DFS0488I DBR | DBD | STA | STO COMMAND COMPLETED. DATAGROUP (groupname)

or

or

or

or

Explanation

The /DBRECOVERY, /DBDUMP, /START, or /STOP command processing is completed. A zero return code indicates that the named database has been successfully processed. The ADS specification is effective only for the /STOP command. The area is only for the /DBRECOVERY, /START, and /STOP commands. A nonzero return code indicates that an unexpected error was encountered while processing.

If the data group contains both full function and Fast Path databases, you might see a command complete message before seeing any messages indicating Fast Path areas did not start successfully.

The /VUNLOAD command completed processing for area xxxxxxxx. DFS0488I is only issued for areas for which the /VUNLOAD command failed, along with the reason code. The reason code indicates the result of the command. A final DFS0488I message is issued to indicate that the command is completed.

For the second form of the message, the return code nn can have the value 00, 04, or 20.

The third and fourth forms of the message are issued to avoid excessive individual messages for successful operations.

When the keyword ALL is specified, one DFS0488I is issued for every database name, area name, or ADS name in error, followed by a final DFS0488I DBR|DBD|STA|STO|VUN COMMAND COMPLETED message. DFS0488I is not issued for each database name, area name, or ADS name with return code of 00 (RC=00 indicates that the command was successful).

This message is only received for the LOCK command that is issued from an OM API.

Return code (Dec)

Meaning

01

The requested state and the current authorization state (see the 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 global command was not able to synchronize with all data sharing partners. The command was completed on the subsystem that received this message, but the partners must be interrogated to determine if the command completed successfully.

03

The database is marked as prohibiting further authorization for one of the following reasons; a global /DBRRECOVERY, a global /STO, or a DBRC CHANGE.DB(NOAUTH) command.

04

An error occurred at the close of the database. For detailed information about the reason codes, refer to message DFS730I.

Module DFSMDA00 can also issue return code 4 if dynamic allocation or deallocation failed. This code indicates an interface problem between another IMS module and the IMS dynamic allocation module, DFSMDA00. This code can also indicate a missing or bad DFSMDA00 member.

For a /VUNLOAD command, the area specified was not found in any data space or coupling facility structure. Verify that the area name is correct. Issue a /DISPLAY FPVIRTUAL command to find which areas are in data spaces or coupling facility structures.

For the second form of the message, this return code indicates that the /UNLOCK SYSTEM command was only partially successful. At least one tolerated block or CI could not be purged. Enter the /UNLOCK SYSTEM command again later.

Return code 04 can also mean that the database is authorized only if the requested state is "READ" or "READ-GO" because of a global /DBD 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.

08

Dynamic allocation failed (from DFSMDA00). This code indicates that the IMS dynamic allocation module (DFSMDA00) received a nonzero return code from MVS dynamic allocation.

For a /VUNLOAD, /STOP AREA GLOBAL, /DBRECOVERY AREA GLOBAL, or /STOP ADS command, an attempt to get the VUNLOAD lock for an area in a coupling facility structure failed. The /VUNLOAD, /STOP AREA GLOBAL, /DBRECOVERY AREA GLOBAL, or /STOP ADS command is terminated. The VUNLOAD, STOP, or DBR processing is not done.

09

During authorization change processing, IRLM could not identify one or more subsystems. You might have IRLM=N or another IRLM name specified on the subsystem.

11

An invalid parameter was found during the evaluation process for database-usage compatibility. The database record in the RECON data set might be invalid.

12

Dynamic allocation or deallocation failed because no storage was available from DFSMDA00.

Return code 12 can also mean that the current authorization state in DBRC is invalid because of an unauthorization error.

14

The named database cannot be started because of one of the following possible conditions:

• DBRC has already authorized other READ access users in the other IMS subsystem to access the database. The granted authorization level for the other subsystem is incompatible with the original authorization level for the current subsystem because of the last /DBDUMP command issued. As a consequence, the original authorization level cannot be restored for the current subsystem.
• The changed database authorization level has been requested through the /STA DB ACCESS command. The request for the change in the ACCESS parameter failed because the database was incompatible with the authorization level currently held in the other IMS subsystem.

Return code 14 can also mean that an error occurred in DBRC while trying to process a change authorization request.

15

The duplicate AREA entry on the /DBRECOVERY AREA command is ignored. The area was already unauthorized by DBRC.

16

Dynamic allocation or deallocation failed because of a system error. For detailed information about the reason codes, refer to message DFS2498I.

20

For the /UNLOCK SYSTEM command, one of the following conditions occurred:

• There were no EEQEs to purge.
• The /UNLOCK command was entered on an IMS system that is not XRF-capable.
• The /UNLOCK command was entered on an active system that was not a previous alternate system. This command must be entered only on the alternate system.
• The /UNLOCK command was entered on the alternate system before the alternate system completed the XRF takeover. This command must be entered on the alternate system only after one or more of the following events have occurred:
  • The failing active system has terminated
  • The processor containing the failing active system has been reset
  • I/O prevention on the active system is complete

21

One of the following occurred:

• A VLOCK request cannot be granted when processing a /START AREA, or a /VUNLOAD AREA command. The area is marked as STOPPED. One sharing IMS system is holding the retained VLOCK exclusive.
• While processing either a /VUNLOAD AREA, or a /START AREA command, an IMS sharing partner noted an inconsistency in the VSO options between the DEDB area control block (DMAC) on DASD and the DMAC in storage. The area is marked as STOPPED.

  Issue a /START AREA command to correct the inconsistency.

• During /VUNLOAD, or a /START AREA command processing, an IMS sharing partner noted an inconsistency in VSO options between the DMAC on DASD and the DMAC in storage. The AREA is stopped. Issue a /START AREA command to correct the inconsistency.
• During /START AREA command processing, an IXLFORCE command is issued to delete any failed persistent connections from a prior failed system. The IXLFORCE command was not able to delete the failed persistent connection. In this case, the following messages are generated:
  • DFS2783A UNABLE TO DELETE FAILED-PERSISTENT CONNECTION TO STR: SSSSSSSSSSSSSSSS REASON=RRRR
  • DFS0488I STA COMMAND COMPLETED. AREA= XXXXXXXX RC=21

24

A command with the ALL keyword is not processed for a Fast Path MSDB. If /START DB ALL access is entered, module DFSDBDR0 does not include MSDBs.

28

The named database cannot be started because of the following conditions:

• The request to change the database authorization level to a data entry database (DEDB) has been requested through the /START DB ACCESS command. The change of an authorization level to a DEDB cannot be done because the referenced DEDB is in use by a region.
• Changing the DEDB access intent requires stopping the scheduling of all PSBs that have access to the target DEDB. This code might require stopping regions in which PSBs associated with WFI transactions are currently scheduled, and stopping the transactions or PSBs for non-WFI transactions.

31

A /START AREA command failed because the area is marked as recovery-needed in the DBRC RECON data set, or the DBRC RECON indicates that there are no available area data sets for the area.

34

Because a /START DB ACCESS command was issued, a change database authorization request was made from IMS to DBRC. The encoded database state returned from DBRC was set to a value of zero.

35

A backout error occurred for the database. A /START command for the database is invalid until a /DBRECOVERY command is issued and batch backout is performed.

37

One of the following events occurred:

• A write error occurred for the database. The command issued is invalid until a /DBRECOVERY command is issued.
• A request for a new dataspace was issued during the open processing for a shared VSO area. Refer to message DFS2444I, that precedes message DFS0488I.

38

A /START DB command was not run because the database was being extended during an IMS XRF takeover, and I/O Prevention was not yet complete. You cannot start the database until IMS knows that I/O Prevention is complete.

39

A /START DB command specifying ACCESS=RO or RD is invalid while incomplete, restartable back outs exist for the database. IMS must have update or exclusive access to the database to redo the incomplete back outs. The command is not processed for the specified database.

41

The area is not loaded into the Coupling Facility. This code does not prevent access to the area unless this code is preceded by message DFS2819A.

42

The named HALDB partition cannot be processed in response to a /START DB command because of an error in the Partition Structure Manager. Check the system console for related DFS0415W messages.

43

The named database cannot be processed in response to a /DBRECOVERY command because one or more in-doubt EEQEs exist for the database and the NODBR keyword was specified in the DFSVSMxx member of the IMS PROCLIB data set.

44

When the /STOP ADS command is entered, the ADS of the named ddname is already stopped. This /STOP ADS command is ignored.

45

A /DBR, /DBD, /STA, or /STO command was issued against the named database or HALDB partition that is QUIESCED or has QUIESCE in progress. Try the command again after the QUIESCE has been released. If the quiesce is in a held state, release it with an UPDATE DB STOP(QUIESCE) command.

50

A /DBRECOVERY, /START, or /STOP command was issued with AREAGROUP or DBGROUP, where the AREAGROUP contained a specified database or the DBGROUP contained a specified area. The command is not processed for databases in an AREAGROUP or areas in a DBGROUP.

On a system that is defined to support Fast Path, the keyword 'MSDB' was entered on a /START, /STOP, or /DBRECOVERY command. (MSDB is allowed on /DBDUMP.) The keyword is ignored and the remainder of the command is processed.

52

A /DBRECOVERY or /START command was entered for a database that was in the process of being recalled from HSM. The command process is not performed at this time. The /DBRECOVERY command must be entered again after the database is recalled. The /START command will be automatically performed after the recall is complete.

54

There is a discrepancy between the number of ADS allocated by IMS and the number of ADS known to DBRC. Correct the discrepancy, then reissue the /DBRECOVERY or /STOP command to deallocate the data sets.

55

The command failed because the FF DB or FP area is currently being recovered.

56

An error occurred while attempting to open the named database or HALDB partition. Check the System Console for message DFS0730I to determine the reason for the failure.

57

The named database is a HALDB master and is invalid with the OPEN keyword. However, a partition structure rebuild is attempted if needed and if only one HALDB master was specified in the command. No rebuild is attempted if more than one database name is listed in the command.

58

The named HALDB partition cannot be processed in response to a /DBDUMP, /DBRECOVERY, /START, or /STOP command. It is still in use by an active HALDB OLR. The command is not processed for the HALDB partition named in the message. However, processing continues for any other databases or HALDB partitions specified in the command.

60

The command failed because the area has been deleted by Online Change.

62

The named database failed directory initialization or the DBB or PSB pool space was not large enough to accommodate the blocks. Check the system console for messages that reference this database.

70

The named database or HALDB partition failed authorization. Check the system console for messages that are related to the authorization failure. Check the status of the named database or HALDB master if no messages related to the authorization failure are found.

71

OPEN keyword processing could not continue for the named HALDB partition because a /DBRECOVERY command has been issued for the HALDB master. Start the HALDB master and then reissue the command to start the HALDB partition. This situation can also occur if the partition has been deleted and a partition structure rebuild has occurred. You can perform a partition structure rebuild by issuing a /START DB haldbmst OPEN command or UPD DB NAME(haldbmst) START(ACCESS) OPTION(OPEN) command, where haldbmst is the master of the partition, or by issuing a qualified GU call for a key in the key range of the partition. You can use the LIST.RECON command to determine if the partition exists or has been deleted.

72

Partition DBM build failed for the named HALDB partition. Check the System Console for DFS0415W messages to determine the reason for the failure.

73

DMB build processing failed for the named database or HALDB partition. Check the system console for DFS0561 or DFS0592I messages to determine the reason for the failure.

74

DMB build processing failed for the named database or HALDB partition because the data management block pool (DMB pool) is too small to hold all the required data management blocks. Change the appropriate parameter to make the pool larger and restart the system. Message DFS0992I might also be issued.

75

DMB build processing failed for the named database or HALDB partition. IMS detected a DMB pool shortage while attempting to load the DMB block for the named database or HALDB partition. The size of the DMB pool must be large enough to accommodate all DMBs that are actively being used. Change the appropriate parameter to make the pool larger and restart the system.

76

DMB build processing failed for the named database or HALDB partition. Check the System Console for DFS0564I messages to determine the reason for the failure.

77

DMB build processing failed for the named database or HALDB partition. An unexpected return code was received. Check the system console for any related messages and contact IBM® Software Support.

79

The command was issued for a database that is still being processed by Restart Parallel Database Open. Wait for that process to complete and try the command again.

80

The named DEDB database cannot be started in a non-FP system.

81

This message is generated because the user issued a /VUN command for an area in a database that was read authorized. The /VUN command must be entered on an IMS subsystem that has update authorization for the database.

82

A /DBR, /STO or /VUN area command was issued against an area that is quiesced. Stop the quiesce by issuing a UPDATE AREA STOP(QUIESCE) command and issue the command again.

83

For the /UNLOCK command, an internal start database (/STA ) command failed because of Common Service Area (CSA) shortage. Issue a manual /STA DB command for each database that has received message DFS0451I with the text IEQE FOUND.

84

The /START, /STOP, /DBR, or /DBD command for the database could not be processed because the resource is in the process of being imported from the IMS change list or the import from the change list failed. The resource cannot be acted on by the type-1 command until it is successfully imported.