Tracker agents
New Tracker Agents are provided to control the workload on:
| Digital OpenVMS
Pyramid MIPS ABI
Shared parm library in Sysplex environment
MVS controllers and trackers can share common controller and tracker
initialization statements and started task JCLs, making it easier to install
many OPC subsystems inside an MVS/ESA sysplex environment.
Controller configuration in Sysplex environment
TME 10 OPC support of MVS/ESA sysplex (base and parallel) has been
extended to enable any one of many cloned controllers on different MVS
images to switch from standby to active status. An OPC controller is started
on each member of the XCF group. The first potential controller that
becomes active is the active controller and the others are standby controllers.
If the active controller fails, a standby controller running in another MVS/ESA
image of the sysplex environment takes over automatically as the active
controller.
Single system image
This enhancement allows OPC TSO dialog users and PIF users to be on a
different MVS/ESA image from the OPC controller. Dialog users and PIF
applications can also be on MVS systems outside the sysplex where the
controller runs. Remote communication is based on APPC.
Extended dialog filter
The dialog filter has been extended to allow more specific search arguments
and to define the interpretation of wildcard characters.
Reparsing of NOERROR
New operator commands allow the operator to dynamically update the
NOERROR table using the NOERROR initialization statements defined by
the OPC PARMLIB member, and to read the statements from a member of
the EQQPARM DD concatenated libraries. In addition a new initialization
statement allows the inclusion of NOERROR statements from members of
the EQQPARM DD concatenated libraries.
PIF extension
Program Interface has been greatly extended to support almost all OPC
database record types.
Job tracking log
This enhancement provides to user exit 11 job tracking records on which an
effective disaster recovery procedure can be based. The customer through
exit 11 receives job tracking records, and can send this data to a remote
controller that, in case of failure of the active controller, will take over as
controller.
GMT clock support improvement
The GMTOFFSET keyword in the OPCOPTS statement lets the user define
an offset between the GMT time set in the MVS system and the actual GMT
time. The OPC controller uses the GMT clock to validate an OPC Tracker
Agent trying to connect; this improvement addresses the need of some users
to have the MVS GMT clock independent of the actual GMT time, while
keeping the ability to use Tracker Agents.
Summary of TME 10 OPC Version 2 Release 2 Enhancements xv
