z/OS MVS Programming: Sysplex Services Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


User State Field Design Considerations

z/OS MVS Programming: Sysplex Services Guide
SA23-1400-00

The fact that XCF skips certain events is an important consideration in designing the user state field. In general, members should not use the user state field to communicate critical information to other members of the group, because the possibility exists that XCF might not present every user state change.

To communicate critical information to other members of the group, a member should use the XCF signaling service. XCF will either deliver messages, or provide notification that the target member or the target member's system failed. However, XCF might not deliver messages in the sequence in which they were sent. If the sequence of the messages is important, members can save the timestamp, or a sequence number, associated with each message.

The following examples illustrate how the skipping of events relates to the user state field:
  • If you use the user state field to contain a data set name, and the current data set name is all your program needs, it is of no consequence if a user state change is skipped.
  • If you use the user state field to record events with corresponding data, and your program needs only the latest event, the skipping of events does not cause a problem. If your program is tracking every event in a table, then the skipping of events will result in an incomplete table.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014