ISQXCON

Purpose

This command is used to manage Processor Operations connections during events such as the planned maintenance of processor Support Elements (SEs) or Hardware Management Consoles (HMCs) (that are used by Processor Operations). In order to prevent error retries and recovery actions by Processor Operations, the SUSPENDED status for a target hardware connection and its associated target systems can be set while the SEs/HMCs are not available. After maintenance, a RESUME function allows normal Processor Operations connection processing to continue.

In addition, the STATUS function provides a consolidated summary of important connection-related information in the multi-line message ISQ350I. This is an alternative to the ISQXDST status dialog panels, which provide similar information, available in different panel views.

Syntax

Read syntax diagramSkip visual syntax diagram ISQXCON *entity_name STATUSRESUMEFORCE(ALL)SUSPENDHOLDSUSPENDFORCE(NO)FORCE(fopt)MSGKEEP

Requirements

The requirements for this command to complete successfully are:

  • Processor Operations must be active.
  • The SUSPEND/RESUME functions of this command make use of the NetView DSISVRT VSAM DB to save status variables. If your NetView is not customized to use this facility, the ISQXCON SUSPEND/RESUME functions cannot be used, only the STATUS function will work.

Parameters

entity_name

Is the name of a configured target hardware (processor) in your active Processor Operations policy.

You can use the '*' wildcard as the last character in your thwname specification to let ISQXCON select all target hardware names, which match the partial string preceding the '*' for processing.

Using only the '*' wildcard character as entity_name selects all configured target hardware names.

STATUS
Generates an ISQ350I multi-line message status report for the selected target entity name(s).
RESUME
For the selected entity name(s), the connection path status is first checked to see if it is currently SUSPENDED. If so, it is set to DORMANT. For target hardware connections the configured target system status is set to CLOSED. This enables normal Processor Operations for them. In order to re-establish communication to an entity name, use the ISQXIII command.
For a connection previously put in HOLD mode, normal processing is established, which includes the delivery of events information as ISQ900I messages and to interested operators as ISQ901I messages.
SUSPEND
For the selected entity name(s), the active connections are first CLOSED to end communication. Then the connection path status is changed to SUSPENDED. This status is saved in the DSISVRT to keep it available across NetView recycles. For target hardware, each configured target system of that target hardware is also set to SUSPENDED. In a SUSPENDED state, Processor Operations commands that use this connection will not work. Use the ISQXCON RESUME function to re-enable the entity name connection again for normal Processor Operations.
SUSPEND HOLD
For the selected entity name(s), the active connections are put in HOLD mode. The connection path (session) remains active. However, no more commands can be forwarded to the entity. Events that may still be delivered, are written to the netlog only. They are prefixed with an AOFA9999 token. While in this session mode, event registrations remain in effect as long as the session is not closed (ISQXCLS). Use the ISQXCON RESUME function to re-enable the entity connection again for normal Processor Operations.
FORCE (fopt)
Required parameter of the SUSPEND request and optional parameter of the RESUME request. The parameter controls the processing of the request according to the parameter's specification or fopt. Valid values are:
ALL
For SUSPEND, it causes that in case of an HMC connection, other target hardware connections over this HMC (same IP address) will also be suspended, if not already in SUSPENDED state.

For RESUME, it causes that all previously suspended target hardware connections over the same HMC connection will be resumed.

YES
For SUSPEND, it causes the existing target systems sessions to be closed before the connection path is suspended.

For RESUME, this option is not valid.

NO
For SUSPEND, it causes the request to be executed only if no active target system sessions exist to the target hardware over the connection path to be suspended. FORCE (NO) is the SUSPEND default.

For RESUME, this option is not valid.

MSGKEEP
The Message Output option. If specified, the message output of the command is written to a PIPE KEEP with the name ISQXCON. For compatibility reasons with other Processor Operations commands, the successful completion response ISQ017I is not written to the message KEEP. Use a PIPE with KEEP ISQXCON as its first stage to analyse the message output. Each time the command ISQXCON is executed with the MSGKEEP option, the PIPE KEEP is re-initialized. If the MSGKEEP option is not specified, all ISQXCON messages are written to the NetView console.

Defaults

If no parameters are specified for ISQXCON, this will result in a STATUS request for all configured entity name connections. The resulting messages are written to the NetView console.

If the SUSPEND function is used, the FORCE(NO) option is in effect to prevent an unintended close of active target system sessions.

For the SUSPEND function, if the target hardware entity is connected to an HMC, active target system connections of other target hardware entities with the same HMC IP address are closed as well.

If the connection is SUSPENDED, no Processor Operations session polling is limited.

Usage

When using ISQXCON to manage a single or multiple entity name connections, it is recommended to use the ISQXCON STATUS function first, before suspending or resuming a connection.

Please note that for SUSPENDED connections, no Processor Operations session polling is done.

Restrictions and Limitations

The SUSPEND and the RESUME functions of ISQXCON currently accept only the SNMP connection protocol for target hardware names. TCP/IP connections to PSMs are not supported.

The SUSPEND HOLD function currently accepts only SNMP ISQET32 (SA-BCPii) connections. The SNMP TCP/IP protocol is not supported.

If multiple target hardware connections are processed in a request, the ISQXCON return code is always 0.

Return Codes

0
The command completed successfully. If multiple entity name connections are processed, but one or more connections have set return codes 6,8,10 and 16, use the responded messages ISQ357I - ISQ359I to determine which of the connections failed and the reason.
2
Function/option parameter invalid or missing. The ISQXCON command is not executed.
4
The entity name parameter is not specified or could not be resolved. The ISQXCON command is not executed.
6
Session is active, FORCE (YES) option is required.
8
Connection protocol is not supported.
10
Status is not SUSPENDED.
16
Suspend/Resume HW command failed.
32
The Processor Operations environment does not exist; the ISQXCON command was not processed.