DFS0535I RC=01, yyyy ALREADY RUNNING


or

RC=03, AREA LOCK FAILED

or

RC=04, AREA IS STOPPED

or

RC=05, AREA FAILED TO OPEN

or

RC=06, 2ND CI UPDATE AND/OR NOTIFY FAILED

or

RC=07, UOW LOCK MODE INITIATION FAILED

or

RC=08, INSUFFICIENT STORAGE FOR AREA PRIVATE BUFFER POOL. STORAGE REQUESTED=nnnnnnnK. STR MGR RC=xxx

or

RC=09, PRIVATE BUFFER POOL ALREADY EXISTS sysid

or

RC 10, COULD NOT GET AN AWE sysid

or

RC 11, INVALID REQUEST SENT TO DBFPAPB0 sysid

or

RC=12,  AREA IS IN A QUIESCE STATE sysid

Explanation

A process was attempted but could not complete for the reason listed in the message.
  • RGN=r, xxxx CONN PROCESS ATTEMPTED AREA a, PCB LABEL z

    Process xxxx was not started. Process xxxx can be:

    HSRE
    High Speed Reorganization utility
    HSSP
    High Speed Sequential Processing
    PREL
    VSO preload process

    Region r identifies the affected region.

  • xxxx DISC PROCESS ATTEMPTED AREA a
    Process xxxx could not disconnect. Process xxxx can be:
    HSRE
    High Speed Reorganization utility
    HSSP
    High Speed Sequential Processing
    PREL
    VSO preload process
  • RC=01, yyyy ALREADY RUNNING
    Process yyyy is active on the area or has not disconnected from the area. Process yyyy can be:
    DA00
    DEDB Alter utility
    HSRE
    High Speed Reorganization utility
    HSSP
    High Speed Sequential Processing
    MDLO
    DEDB Sequential Dependent Delete utility
    MMHO
    DEDB area data set Compare utility
    MRIO
    DEDB area data set Create utility
    MSCO
    DEDB Sequential Dependent Scan utility
    PREL
    VSO preload process
  • RC=03, AREA LOCK FAILED

    Process xxxx failed to acquire the area lock for the area.

  • RC=04, AREA IS STOPPED

    Process xxxx cannot run on a stopped area.

  • RC=05, AREA FAILED TO OPEN

    The attempt to open area a failed.

  • RC=06, 2ND CI UPDATE AND/OR NOTIFY FAILED

    Process xxxx failed because the IRLM notify failed or there was an error in the second CI update.

  • RC=07, UOW LOCK MODE INITIATION FAILED

    The transition to UOW locking mode was unsuccessful. A probable cause is a failure in the notify process to a sharing subsystem.

  • RC=08, INSUFFICIENT STORAGE FOR AREA PRIVATE BUFFER POOL. STORAGE REQUESTED=nnnnnnnK. STR MGR RC=xxx.

    Unable to create private buffer pool; sufficient storage was not available. In the message, nnnnnnn is the number of 1014 bytes of storage requested, and xxx is the return code set by the IMS storage manager.

  • RC=09, PRIVATE BUFFER POOL ALREADY EXISTS sysid

    Process xxxx requested the creation of the area private buffer pool but the buffer pool exists already.

  • RC 10, COULD NOT GET AN AWE sysid

    The request for an AWE control block failed to process xxxx.

  • RC 11, INVALID REQUEST SENT TO DBFPAPB0 sysid

    An invoking module passed an invalid request code to DBFPAPB0.

  • RC=12, AREA IS IN A QUIESCE STATE sysid

    The process cannot run on a quiesced area.

System action

The action the system takes are listed for the different forms of the message:
  • RGN=r, xxxx CONN PROCESS ATTEMPTED AREA a, PCB LABEL z

    Process xxxx terminates.

  • xxxx DISC PROCESS ATTEMPTED AREA a

    Process xxxx terminates without disconnecting.

  • RC=12, AREA IS IN A QUIESCE STATE sysid

    The utility terminates.

System programmer response

The actions to take are listed for the different forms of the message:
  • RGN=r, xxxx CONN PROCESS ATTEMPTED AREA a, PCB LABEL z

    See the accompanying DFS0535I message.

  • xxxx DISC PROCESS ATTEMPTED AREA a

    See the accompanying DFS0535I message.

  • RC=01, yyyy ALREADY RUNNING

    Run the utility or process again when process yyyy has completed. This message can also be issued if a previous process did not complete successfully; if so, issue a /STOP and /START command pair for the area to allow the requested process to run. If this message is received in a data sharing environment, issue the /STOP and /START command pair on all sharing subsystems.

  • RC=03, AREA LOCK FAILED

    Determine the cause of the lock failure and correct the problem. If a disconnect did not complete because of an area lock failure, a /STOP and /START command pair might be required to allow other processes to run.

  • RC=04, AREA IS STOPPED

    Issue a /START command to start the area.

  • RC=05, AREA FAILED TO OPEN

    See message DFS3702I to determine why the open failed.

  • RC=06, 2ND CI UPDATE AND/OR NOTIFY FAILED

    See accompanying messages for more information.

  • RC=07, UOW LOCK MODE INITIATION FAILED

    Correct the failing component and rerun.

  • RC=08, INSUFFICIENT STORAGE FOR AREA PRIVATE BUFFER POOL

    Run process xxxx again when storage is available.

  • RC=09, PRIVATE BUFFER POOL ALREADY EXIST sysid

    This indicates a logic error in the software. Run process xxxx again. If the error still occurs, contact IBM® Software Support.

  • RC=10, COULD NOT GET AN AWE sysid

    Run process xxxx again when storage is available.

  • RC=11, INVALID REQUEST SENT TO DBFPAPB0 sysid

    This indicates a logic error in the software. Run process xxxx again. If the error still occurs, contact IBM Software Support.

  • RC=12, AREA IS IN A QUIESCE STATE sysid

    Stop the quiesce by issuing a UPDATE AREA STOP(QUIESCE) command, and rerun the named utility.

Programmer response

Ensure that no HSSP process or utility is active in an area before restarting the HSSP job.

Module

DBFPMSG0, DBFPSET0, DBFUHDR0