OPCA PCS Policy Item
The panel shown in Figure 1 appears if you select the OPCA PCS policy item from the Policy Selection panel for OPC controller details.
COMMANDS HELP
------------------------------------------------------------------------------
AOFPOCS OPC Controller details
Command ===>
Entry Type : Controller details PolicyDB Name : USER_PDB
Entry Name : OPC_OCS_1 Enterprise Name : USER_ENTERPRISE
OPC PCS entry name: OPC_OCS_1
Enter or update the following table names:
Netview domain name. . . SYSPLEX
OPC controller subsystem X
OPC Special resources NO (YES NO ALL)
The OPCA PCS automation definition defines the NetView domain that the OPC Controller resides on and specifies the MVS subsystem name for the OPC Controller system.
Fill in the following fields:
- NetView domain name
- Specify the parameter as either a NetView domain ID (up to five characters) or the keyword SYSPLEX. If a domain ID is specified, it indicates that the OPC Controller always runs on the specified domain. The keyword SYSPLEX indicates that the OPC Controller may be run on any one of the systems in the local sysplex.
- OPC controller subsystem
- The MVS subsystem name of the OPC Controller as defined in
the IEFSSNxx member.
When defining the OPC Controller as a separate application, the subsystem name and job name must be this OPC controller subsystem name.
- OPC Special resources
- The following entries are valid:
- YES
- The OPC special resources will be set for any SA z/OS-monitored subsystem that is specified in the
OPC special resource definitions panel (see Figure 1). Ensure that OPC
Special Resources are defined if using this option.
If YES is specified, but no OPC Special Resources are defined, then it is processed as NO during configuration file build.
- NO
- No Special Resources will be set. This is the default.
- ALL
- Special Resources will be set for all SA z/OS Monitored subsystems. No Special Resource entries are required.