ISQEXEC
Purpose
The ISQEXEC command sends a command to a target control task to be processed. Commands sent by ISQEXEC are processed by the target control task in the order in which they are presented.
Syntax
Requirements
The requirements for this command to complete successfully are:
- Processor operations must be active.
- The target entity specified with target_system_name or target_ensemble_name must be initialized. If target_ensemble_name was specified, at least one target system running on that hardware must be initialized.
Parameters
- target_system_name
- Specifies the name of the target system.
- SC
- Specifies the active system console connection.
- target_hardware_name
- Specifies the name of the target hardware (processor).
- S
- Specifies the active system console connection.
- target_ensemble_name
- Specifies the name of the target ensemble. (zEnterprise® ensemble for zBX management)
- command
- Is the name of the user automation command to be processed.
Defaults
None.
Usage
The main advantage of the ISQEXEC command is that it frees the operator station task (OST) for other work because commands issued by ISQEXEC are processed by a target control task rather than in the OST.
You may require that a set of commands to a target connection are
processed in the order in which the commands are presented (that is,
serially). ISQEXEC is processed by a target control task, which ensures
that the commands are processed in the correct order. A set of commands
to be processed serially can be packaged in an automation procedure
and be called by the ISQEXEC command, for example:
ISQEXEC target_system_name console_connection exec_name exec_operandsYou can write automation procedures that issue ISQSEND commands. ISQSEND sends commands to a target system. You can enter the ISQEXEC command in the NCCF command line to cause an automation procedure to be processed.
Restrictions and Limitations
The following restrictions or limitations apply to this command:
- Do not issue ISQXDST, ISQHELP, or ISQXOPT with ISQEXEC.
- Do not issue any user automation with ISQEXEC that results in a full-screen panel.
- ISQEXEC does not lock a target console connection; the serialized commands can be interrupted by commands from other tasks. See Usage.
Return Codes
- 0
- The ISQEXEC command completed successfully and it caused the command to be queued to a target control task.
- 8
- The command syntax is not correct.
- 10
- The specified target system was not initialized.
- 12
- An internal error occurred.
- 32
- The processor operations environment does not exist. The ISQEXEC command was not processed.
