DFS4637I RSN=00 type name WAS ABLE TO SYNCHRONIZE WITH THE ONLINE SYSTEM SYS3


or

RSN=01 type name WAS NOT ABLE TO SYNCHRONIZE WITH THREAD yyyyyyyy SYS3


or

RSN=02 type name WAS NOT ABLE TO SYNCHRONIZE AS DEDB ALTER WAS STOPPED SYS3


or

RSN=03 type name WAS NOT ABLE TO SYNCHRONIZE WITH THREAD yyyyyyyy SYS3


or

RSN=04 type name FAILED TO SYNCHRONIZE WITH THE ONLINE ENVIRONMENT - RETRY ATTEMPTED SYS3


or

RSN=05 type name TIMED OUT ATTEMPTING TO SYNCHRONIZE WITH THE ONLINE ENVIRONMENT SYS3

Explanation

In the message text, type and name can be either of the following combinations:
AREA areaname
Indicates the name of the DEDB area.
DEDB dedbname
Indicates the name of the DEDB.

The meaning of this message depends on the reason code (RSN=), as follows:

Reason code
Meaning
RSN00
The area or DEDB serialization process finished for area areaname.
RSN01
The area or DEDB serialization process failed. Thread yyyyyyyy was accessing area areaname and did not issue a commit in a timely manner, allowing the DEDB Alter utility to serialize with the thread.
RSN02
The area or DEDB serialization process failed. The DEDB Alter utility was stopped (internally or by using the /STO RGN command) while serialization was in progress.
RSN03
The area or DEDB serialization process failed. Thread yyyyyyyy was accessing area areaname and did not issue a commit in a timely manner, allowing the DEDB Alter utility to serialize with the thread.
RSN04
The area or DEDB serialization process failed for area areaname. Another attempt to serialize the area will be made because TIMEOUT or RETRY YES or both, or because RETRY retry_value was specified as a DEDB Alter utility input option.
RSN05
The area or DEDB serialization process timed out while attempting to serialize the area with active threads.

System action

If the area or DEDB serialization is successful, the DEDB Alter utility continues processing. If the area or DEDB serialization is unsuccessful, the DEDB Alter utility terminates processing without performing the requested DEDB Alter function.

A failure to serialize is caused by a thread not issuing a commit while the DEDB Alter utility is attempting to serialize with online activity. This is normally caused by a long running BMP, or some type of conversational transaction that did not issue a commit due to a lack of activity.

System programmer response

No action is required.

Module

DBFDAQ00