|
|
|
CA MIA monitors the progress of managed device VARY activity and provides the means to generate notifications, on a cyclical basis, should the VARY activity for a given device exceed an installation specified threshold.
Note: For more information about establishing the threshold and interval for VARY delay processing, see the description of the VARYDELAY keyword of the SETOPTION GTAF command in the Statement and Command Reference Guide.
When CA MIA detects that the attempt to VARY a managed device has exceed the specified threshold, it issues a highlighted MIM2211 console message on a cyclical basis until the VARY activity completes. CA MIA also directly notifies CA OPS/MVS of the VARY delay event and permits CA OPS/MVS to evaluate the VARY delay event in an )API rule. The )API rule can instruct CA MIA to continue waiting for the VARY to complete in which case CA MIA will continue waiting and the cyclical process will repeat again if the VARY device activity does not complete within the next VARYDELAY interval. Alternatively, the )API rule can instruct CA MIA to terminate the VARY device activity, in which case, CA MIA abends the target task processing the VARY device that is being delayed.
The CA MIA VARY device delay event is presented to CA OPS/MVS and can be processed by the following rule:
)API MIM2211
The available OPS/REXX variables and value for a CA MIA VARY device delay event are:
MiMgr
Current release
Service level
MIM2211
MIM2211
1 to 8 character CA MIM internal task name. This task name can be correlated to the CA MIM DISPLAY TASK command response.
8 character z/OS TCB address of the MIMTPVDV task that is experiencing the VARY device delay.
This variable is a read-write character variable. The variable is initialized to the character string 'CONTINUE' by CA MIA before the VARY delay event is presented to CA OPS/MVS. The )API rule can leave the ACTION variable unchanged in which case CA MIA will continue to wait for the VARY device to complete. Otherwise, the )API rule can change the ACTION variable to the text string 'ABORT' which will instruct CA MIA to terminate the VARY device processing that is being delayed.
MIM2211W VARY devn state delayed by nnn seconds. The format of the API.TEXT variable is the same as the MIM2211W console message. The MIM2211W message ID within the text is subject to message ID prefixing as controlled by the CA MIM command, SETOPTION MIM MSGPREFIX keyword.
Specifies the target device number
Can be either 'ONLINE' or 'OFFLINE'
Specifies the number of seconds that have elapsed since the VARY device was initiated.
Member APIMIMGR of HLQ.OPS.SAMPLE.RULES demonstrates how to use the MIM2211 API.
CA MIA monitors managed device VARY activity and generates notification when a VARY command for a given device is requeued by z/OS. z/OS requeues a VARY command when ENQ resources necessary for z/OS to serialize a VARY command with other system functions cannot be obtained within 5 seconds. VARY REQUEUE Notification occurs when the number of times that a VARY command has been requeued exceeds an installation specified threshold.
Note: For more information about establishing the threshold for VARY REQUEUE Notification, see the description of the VARYRQNTFY keyword of the SETOPTION GTAF command in the CA MIM Statement and Command Reference Guide.
When CA MIA detects that the number of times that a VARY command for a managed device has been requeued exceeds the VARYRQNTFY threshold, it issues a MIM2225 console message. This message is issued on an iterative basis until the VARY activity completes. CA MIA also directly notifies CA OPS/MVS of the VARY REQUEUE event and permits CA OPS/MVS to evaluate the VARY REQUEUE event in an ‘)API rule’. The ‘)API rule’ can instruct CA MIA to continue to retry the VARY command. In this case CA MIA will reset the requeue counter for the VARY command. The VARY REQUEUE Notification process will repeat again if the SYSIEFSD ENQ contention issue remains in effect. Alternatively, the ‘)API rule’ can instruct CA MIA to terminate the VARY device activity. In this case, CA MIA will not retry the VARY command and will remove it from the CA MIA VARY command processing queue.
The CA MIA VARY Requeue Notification event is presented to CA OPS/MVS and can be processed by the following rule:
)API MIM2225
The available OPS/REXX variables for a CA MIA VARY Requeue Notification event are:
Variable Value
MiMgr
Current release
Service level
MIM2225
MIM2225
1 to 8 character CA MIM internal task name. This task name can be correlated to the CA MIM DISPLAY TASK command response.
8 character z/OS TCB address of the MIMTPVDV task that has been requeued.
This variable is a read-write character variable. The variable is initialized to the character string 'CONTINUE' by CA MIA before the VARY delay event is presented to CA OPS/MVS. The )API rule can leave the ACTION variable unchanged. In this case, CA MIA will continue to retry the VARY command until it eventually completes when ENQ contention has been relieved. Alternatively, the )API rule can change the ACTION variable to the text string 'ABORT'. The ‘ABORT’ ACTION variable instructs CA MIA NOT to retry a VARY command that has been requeued due to ENQ contention.
MIM2225W VARY 078F OFFLINE REQUEUED - SYSIEFSD Q4 ENQ CONTENTION. The format of the API.TEXT variable is the same as the MIM2225W console message. The MIM2225W message ID within the text is subject to message ID prefixing as controlled by the CA MIM command, SETOPTION MIM MSGPREFIX keyword.
Specifies the target device number
Can be either ONLINE or OFFLINE.
Member APIMIMNW of HLQ.OPS.SAMPLE.RULES demonstrates how to use the MIM2225 API.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |