Reason:
Because CICS was COLD STARTED, data synchronization between resources may be lost. Avoid a CICS COLD START, if possible, when data synchronization is critical, as in a production CICS.
The variables in the message text are as follows:
Is the CICS application ID.
Is the name of the MUF.
Is the CICS unit of work in 16 contiguous characters.
This message, unlike messages DC00503I and DC00504I, does not give monitor information here but instead shows blanks. For monitor information connected to this message, see the corresponding CA Datacom/DB message DB00130I as listed in the CA Datacom/DB Message Reference Guide.
Note: Messages DC00501I, DC00502E, DC00503I, and DC00504I can appear multiple times for the same transaction, same CICS task number, if the given task is involved with more than one MUF. See the example that follows in the description of message DC00504I.
Action:
Manually research and resynchronize your data between the different resources. For example, between two or more CA Datacom/DB MUFs, or between a CA Datacom/DB MUF and a resource that is not a CA Datacom/DB resource for this transaction.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|