Using CMRDJCL
In the event that ARCHIVE fails (a tape-drive error, for example), ARCHPOST will not run and the data set will not be eligible for recording. Even if you specified STOP=NO, the archive-in-progress flag will cause recording to stop if there is no eligible data set.
In a multiple data set environment when you do not specify NONE for ARCHJCL, BMC AMI Ops Monitor for CICS will close a data set when it becomes full, submit the archive proc to off-load the data set, and then try to switch to the next data set. If the next data set has the archive-in-progress flag turned on, BMC AMI OpsM for CICS issues the message FT226W ARCHIVE IN PROGRESS.. every fifteen seconds for two minutes, after which processing stops for this data set and BMC AMI OpsM for CICS issues the messages FT224W NOT ARCHIVED...
At this point, how BMC AMI OpsM for CICS processing continues depends on the number of CMRDETL data sets are in use. For example:
- If your CICS site is using more than two CMRDETL data sets for recording, BMC AMI OpsM for CICS stops recording, and issues the messages FT225E DETAIL FILE COLLECTION STOPPED and FT255I DETAIL TRANSACTION RECORDER FILE IS CLOSED.
If your site is using only two data sets, BMC AMI OpsM for CICS attempts to write to the data set that was just archived. If the archive-in-progress flag is still on for this data set, the application issues the FT226W ARCHIVE IN PROGRESS message until the data set is ready to be used or when the two minutes is reached. After two minutes pass, the application issues the message FT224W NOT ARCHIVED message for this data set, stops recording, and issues the messages FT225E DETAIL FILE COLLECTION STOPPED and FT255I DETAIL TRANSACTION RECORDER FILE IS CLOSED.
For information about resolving the issues related to incomplete archiving of CMRDETL files, see the online Help for the FT226W message.
You must issue the FST2 QOFF and FST2 QON commands to restart recording after resolving the FT226W-related problem.