To avoid a potentially lengthy response time when initially displaying
or refreshing the Fault Entry List display, only history file information
that is immediately available is displayed.
An example of a history file that is not immediately available is one that is in use on a
different MVS™ image to the one on which it is being displayed.
In this case, the information displayed is limited to the fault entries currently in the $$INDEX
member of the history file data set, but does not include any new or modified faults that might have
been added to the still cached $$INDEX member which is managed by the IDIS subsystem on the other MVS™ image. As soon as the other IDIS subsystem relinquishes control of the
history file, the updated information is available for display.
If one or more history files are not immediately available, then a message is displayed near the
top of the display as shown in the following example (❶):
By placing the cursor on the number of history files in the updates pending message (❶),
and pressing Enter, the History File Updates Pending display is shown as in the following
example:
This display lists the names of all history files for which the most current information might
not have been available. To return from this display, press PF3, PF12, or Enter.
If the updates pending message is received, and the most current
information is required, then this information is generally shown
when the Enter key is pressed again to perform an implicit refresh.
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.