HP XP7 Smart Manager for Mainframe Messages (TK916-96002, May 2014)
Table Of Contents

Explanation and recommended actionsMessage textMessage ID
The suspend processing started when the timeout period elapsed
because this period elapsed before the journal of the ATTIME suspend
times for the ATTIME suspend function was acquired, or the suspend
processing started at the ATTIME suspend time because the Continuous
Access Journal copy pair was in the suspend status at the ATTIME
suspend time.
Check the following because the backup for the specified time might
not have been acquired:
• Status of the Continuous Access Journal copy pair path
• Value specified for the TIMEOUT parameter of the YKSUSPND
command
• Status of the Business Copy copy pair volumes (the Continuous
Access Journal consistency time and status during the suspension)
• Status of the Continuous Access Journal copy pair volumes
After checking the results, if necessary, use the YKSUSPND command
to cancel the ATTIME suspend information, and then re-acquire the
backup.
ii (hexadecimal number)
consistency group ID for Business Copy (00-7F)
jj (hexadecimal number)
Journal group number specified for the sub consistency group ID
for the Continuous Access Journal that links with Business Copy
gg (hexadecimal number)
Generation ID (00-FF)
ATTIME-suspend-time (GMT)
ATTIME suspend time: YYYYMMDD-HH:MM:SS.NNNNNN
YYYY: Year
MM: Month
DD: Day
HH: Hour
MM: Minute
SS.NNNNNN: Second
The timeout limit expired during the
wait for the reservation time of the
CAJ ATTIME suspension. (CT ID=ii,
R-JNL=jj, GENID=gg, TIME=AT-
TIME-suspend-time)
YKZ409E MSG
SC=24 RC=24
Table 46 List of messages (message ID YKZ41x - YKZ91x)
Explanation and recommended actionsMessage textMessage ID
Copygroup SUPFnc does not sup-
port CAJ Errorlevel.
YKZ410E MSG
SC=36 RC=36
#1
Messages208