If a shared update conflict (error DMS0D99)
occurs when opening a directory file, the behavior of ARCHIVE depends on whether the call comes from an interactive task or a batch task:
interactive task
ARCHIVE attempts to open the directory file again during the maximum wait time. The maximum wait time is defined in the SHUPDW parameter in the parameter file. If the directory file is still locked after the maximum wait time, the ARCHIVE run is aborted with the messageARC0149
.batch task (e.g. an HSMS server task)
ARCHIVE attempts to open the directory file again during the maximum wait time. If the directory file is still locked after the maximum wait time, the messageARC0852
is issued at the operator terminal. The run is then terminated or continued, depending on the reponse.If the run is continued and the directory file is still locked, ARCHIVE attempts to open the directory file during the maximum wait time, before the message
ARC0852
is issued again.