DFS3770W SYNCHRONIZING PROCESS TIME OUT DURING START AREA PROCESSING FOR AREA areaname
or
or
or
or
or
or
or
or
or
or
or
Explanation
Subsystem resource synchronization did not finish within a reasonable amount of time. This situation might be a valid condition and might resolve itself. If IMS determines that a hang exists, IMS attempts to resolve the wait. IMS might reject the process and issue the second form of the message, or it might have resolved the hang (allowing the process to retry). In either instance, if the first form of the message terminates without outside intervention, then no action is necessary.
- reason
- Identifies the cause of the exceeded time, and is one of the following
situations:
- CTLBLK SYNC
- IMS must synchronize internal information.
- ALLOC/OPEN ADS
- An ADS is opening as part of an area open or ADS create action.
- UOW LOCK INIT
- IMS is converting to UOW lock mode due to starting a utility.
- STOP AREA
- An area is being stopped. This stop might be due to a command or internal stop.
- START AREA
- An area is starting.
- SHVSO SYNC
- SHVSO information has been internally data synchronized.
- SHSDEPS SYNC
- SHSDEP information has been internally data synchronized.
- areaname
- Identifies the affected area.
System action
If the first form of the message persists, then the originating system (the system receiving the message) is waiting for an action from a sharing partner that is not completing. This situation indicates a hang. The only way to resolve the hang is based on the reason from the first form of the message.
Operator response
Determine if any subsystem participating in block level sharing is experiencing problems. If a subsystem is in a busy state because the processor load is heavy or the processor STOP key was pressed, no action is necessary. If a subsystem is in a wait or loop condition, that subsystem must be terminated by entering a /STOP or MVS MODIFY command; otherwise, the wait or loop condition can continue indefinitely.
Programmer response
If this message has been issued multiple times, the other subsystem is not in a processor-busy condition, the processor STOP key was not pressed, and the other subsystem has a severe problem. Contact IBM® Software Support after appropriate data has been collected. Capture memory dumps of all IMS subsystems in the sysplex.