ISQXLOC

Purpose

The ISQXLOC command locks access to a ProcOps entity to serialize operations to that console with other operator tasks. Entities can be either target system names together with a console designator.

Requirements

The requirements for this command to complete successfully are:

• Processor operations must be active.
• The entity must not be locked by another task.
• The target_system_ProcOps_name syntax requires that the addressed target system be initialized.

Parameters

target_system_ProcOps_name

Is the name of the target system.

OC

Specifies the active operator console (not valid for the coupling facility).

SC

Specifies the active system console (not valid for the OCF-based processors).

target_hardware_name

Is the name of the target hardware.

S

Specifies the active system console.

Defaults

None.

Usage

All processor operations commands that require serialization automatically lock the entity when they start and unlock the entity when they complete.

The lock prevents processor operations from sending requests to an entity —they are rejected unless issued by the same task that issued the ISQXLOC command—until the lock is removed by the ISQXUNL command (see ISQXUNL).

If you are going to issue several commands to an entity, you can issue the ISQXLOC command to lock access to the entity to ensure the commands are processed without interruption by commands from other tasks. When you are finished with this sequence of commands, issue the ISQXUNL command to unlock access to the entity.

If the ISQXLOC command is issued within an automation procedure, or within a set of called automation procedures, the locked entity should be unlocked (using the ISQXUNL command) after all processing of the automation procedure is completed. It is not normally necessary to lock an entity for the processing of an automation procedure because of the serialization of the ISQEXEC command.

Any change in lock status is reflected in the status facility.

Restrictions and Limitations

The following restrictions or limitations apply to this command:

• The parameters are not checked for validity.
• Once obtained by a task, another task cannot obtain the lock until it is released by the owning task.
• An ISQXLOC command issued from within a locked sequence of commands is rejected.

Return Codes

0

The ISQXLOC command completed successfully.

4

The entity was already locked by the current task.

8

You used syntax that is not valid, specified an entity that is not valid, or in the case that the entity is a target system, it is not initialized.

12

The entity is locked by another task.

32

The processor operations environment does not exist; the ISQXLOC command was not processed.

Any return codes greater than 8 that are not listed above indicate that an error occurred in the NetView CNMLOCK service.