Explanation
User data updates without timestamps have been made to the primary XRC volume volser. The CCHH being updated is cchh. The number of tracks updated is tracks. XRC places the non-timestamped updates on the secondary volume. Be aware that, without a timestamp on the record, applications that do dependent record updates on multiple volumes attached to different storage controls can experience temporary data out-of-synchronization situations.
This message is first issued when X'101'( decimal 257) non-timestamped updates are processed for a volume. Subsequent occurrences of the message are controlled by the value of XRC PARMLIB setting NoTimeStampCount. For information on NoTimeStampCount, see the section on administering your extended remote copy environment in z/OS DFSMS Advanced Copy Services.
System action
XRC functions are active.
System programmer response
- Application systems making updates to XRC-managed volumes do not provide timestamp support. Timestamp support can be missing from non-MVS systems.
- Application programs making updates to XRC-managed volumes bypass the standard MVS™ IOS interfaces to perform their I/O operation. In this case, change the application programs to provide timestamp support.
- A system paging volume is being managed by the XRC data mover. The paging subsystem uses certain functions that bypass normal I/O timestamping, which then causes the ANTX8030W message to be issued for volumes containing system paging data sets. All data has been properly applied to the secondary volumes, and this message can be ignored.
- Concurrent Copy processing for the volume or data sets on the volume starts or stops at the same time an update is being recorded by XRC. This would be most likely to occur when many data sets on a volume are processed by Concurrent Copy.
- SUPPRESSTIMESTAMP parameter in ANTXIN00 parmlib member is defined as YES.
Updates are made to XRC-managed volumes during
IPL, before the ANTAS000 address space has completed initialization.
Updates made during IPL are normally not timestamped to protect the
system from incorrect timestamp values that may be present before
Server Time Protocol (STP) synchronization, and do not normally represent
an error or indicate inconsistent data.
If SUPPRESSTIMESTAMP parameter in ANTXIN00 parmlib member is not defined as YES and all data updates are correctly timestamped and the problem persists, search problem reporting databases for a solution. If no solution exists, contact the IBM® Support Center. Provide the system log and a GTF trace of related system and XRC activity to the volume or volumes that encounter the error.
Source
Extended remote copy (XRC).