IMS PROCESSING HUNG WHEN THE ACTIVE WADS or OLDS RESIDES ON A PHYSICAL DEVICE WHICH HAS SUFFERED A HARDWARE FAILURE.

Flash (Alert)


Abstract

When storage subsystems report a long busy condition on IMS™ log I/O and no
IOTIMING value has been set for the device, IMS hangs until the long busy
is resolved.

Content

To avoid this possible hang condition, IMS recommends the use of the IOTIMING parameter of the MIH statement in the IECIOSxx member of parmlib to abnormally end I/O requests to a volume if a user specified time limit is exceeded.


When IOTIMING is used, an I/O request is abnormally ended. IMS will experience an I/O error and act accordingly by either switching to a new OLDS or a new WADS.

In an XRF environment, where the IMS has been taken over due to inactivity and is no longer the active IMS, this will result in the abnormal termination of that IMS (the old active) . In this case, DBRC will issue ABENDU2480 and message DSP0300I DIAG=ATTEMPTED OLDS SWITCH AFTER TAKEOVER.
This item was added to the Technote Flash database on Feb 5, 2007.


Rate this page:

(0 users)Average rating

Document information


More support for:

IMS
Logger

Software version:

7.1, 8.1, 9.1, 10.1, 11.1, 12.1

Operating system(s):

z/OS

Reference #:

1253731

Modified date:

2013-04-20

Translate my page

Machine Translation

Content navigation