Messages › GTAF and TPCF Messages › MIM2150I

MIM2150I

DIAGNOSE ALLOCATION DISPLAY

Begin managed VARY display ===>
   VARY device status (one or more of the following)
   No managed VARY in progress
   VARY commands purged: nnnnnnnnnn
   Duplicate VARY commands discarded: dddddddddd
   Active VARY device queue
   Dev    State   Option   Source    Requeue#    Queue-Tm    Wait-Rsn
   dddd    state   option   console     rrrrrrrr   tttttttt   reason
   Scheduled VARY device queue
   Dev     State   Option   Source   Requeue#   Queue-Tm   Wait-Rsn
   dddd   state   option   name   rrrrrrrr   tttttttt    reason

End managed VARY display ===>

Reason:

This portion of the DIAGNOSE command response show the state of any managed VARY device request that is actively being processed or that is scheduled to be processed. A maximum of eight different managed devices can be in the process of being varied at any given time. Vary requests in excess of the eight active requests will show as scheduled requests. The display also includes the number of VARY commands purged since CA MIM startup. When a VARY request, is in the process of being purged the State and Option columns displays the text BEING and PURGED respectively.

dddd

Managed device address.

state

Target device state. Can be one of the following:

• ONLINE
• OFFLINE

option

Additional target device state option. Refer to the VARY device command in the IBM publication, “MVS System Commands,” for an explanation of these options. Can be one of the following:

• FORCE
• SHR
• RESET
• UNCOND

name

The name identifies the origin source of the VARY request. The source name can be a console name, *PGMVARY for an intercepted IEEVARYD call, or *INTVARY for an MIA internally issued IEEVARYD call.

nnnnnnnnnn

Number of VARY commands purged from CA MIM startup.

dddddddddd

Number of duplicate VARY commands discarded from CA MIM startup.

rrrrrrrr

The number of times the VARY requested has been requeued for processing because the required device group lock was unavailable for an extended time period.

tttttttt

The approximate amount of time, in seconds, that the VARY request has been outstanding.

reason

The reason that an active VARY request is waiting for processing. Can be one of the following:

Grp Lock

Waiting for control of the device group lock.

VARY dev

Waiting for the IEEVARYD service to complete processing.

Deferred

Request is pending because device is externally allocated.