Using the ProcOps HOLD Session Mode

The ProcOps HOLD session mode is available with active ISQET32 sessions only. You can put an ISQET32 session in the HOLD mode for the following purposes:
  • Disable the usage and automation of an active ISQET32 session.
  • Make a session unavailable for a planned Support Element outage, as an alternative to SUSPEND the session.

When an ISQET32 session is in HOLD mode, any messages that are received from hardware event or operating system are prefixed with an AOFA9999 message token and written to the netlog. No automation is triggered and the CPC or image status information is not updated. Except ISQXCON RESUME, other session management commands are not accepted. You cannot send ISQCCMD common commands to a target hardware or a target system when the related session is in HOLD mode. If you want to stop ProcOps by using the ISQSTOP command, sessions in HOLD mode are terminated. In contrast to sessions in SUSPENDED mode, sessions in HOLD mode do not keep this status across a NetView or SA recycle as HOLD is a transient logical session mode only.

You can put a session in HOLD mode manually by either issuing the ISQXCON thwname SUSPEND HOLD command, or by using the ISQXDST status dialog. On the status dialog, select a target system, type H in the command field and press the Enter key. As a response, the target status in the ISQESUM panel changes to HOLD for the selected system and all other target systems that use the same ISQET32 session to the Support Element.

You can resume a session from HOLD mode manually by either issuing the ISQXCON thwname RESUME command, or by using the ISQXDST status dialog. On the status dialog, select a target system, type R in the command field and press the Enter key. As a response, the target status in the ISQESUM panel changes to INITIALIZED for the selected system and all other target systems that use the same ISQET32 session to the Support Element. If no connection to the Support Element is possible at the time of the resume, the status changes either to CLOSED or SNMP SESSION PROBLEM, depending on the error situation.

You can use the ISQXCON * STATUS command to display the current session status for all configured ProcOps sessions.