The ADDRESS OPSCTL host environment controls the ECF, MSF ONLY, MSF, and COF, and OSF components.
Returns information about each ECF user logged onto a console.
Enables you to specify a default system name and system wait value for the currently executing REXX program or rule. Only those OPS/REXX functions that support cross system operations and do not allow the explicit setting of a system name and system wait value (for example: OPSVALUE), are applicable.
Tells CA OPS/MVS to initialize the MSF on the local MSF system, to open its VTAM access control block, and to begin communicating with copies of CA OPS/MVS running on remote systems.
Instructs the local copy of CA OPS/MVS to end its sessions with remote CA OPS/MVS copies and to close its VTAM access control block.
This command does one of the following:
Ends the session between local and remote copies of the MSF, or ends the association between a transient data queue and the COF.
Defines to the MSF the systems it can communicate with, or defines to the COF a list of CICS transient data queue names to be selected for AOF processing.
Deletes either specific or all MSF or COF resources that you have defined.
Displays all MSF or COF resources currently defined and their status.
Returns performance information about the OSF server component. This information is useful for tuning OSF-related parameters to meet the performance objectives of your installation.
Returns information about active servers to the external data queue.
Returns status and historical information about the server execution queue to the external data queue.
Causes all pending commands waiting on the OSF execute queue to be immediately discarded. As a result of this command, all existing OSF execute queue statistics are reset to 0 (zero).
Stops the server that has the address space ID nnnn.
Defines a new OPSLOG for future use.
Makes a previously defined OPSLOG definition active for use. In the cases where the OPSLOG is DIV-backed, the data set must exist at the time it is activated.
Makes a previously active, read/write, OPSLOG the live log. This means that new events processed by the CA OPS/MVS subsystem are added to this OPSLOG. There can only be one live OPSLOG. Other than at product startup where there is no prior live log, the prior live log becomes an active log again.
Empties an active, read/write, OPSLOG (it cannot be the live log), which makes it available for use as an empty log.
Lists all of the defined OPSLOGs.
Changes the status of an OPSLOG back to defined.
Deletes an OPSLOG definition.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|