| Windows NT
| HP–UX
|TCP/IP communication improvements
| The TCP/IP communication component that enables the controller to
| communicate with the TCP/IP connected tracker agents has been
| restructured to use the standard TCP/IP C–Socket interface. This change
| enables TME 10 OPC for the latest OS/390 releases and provides for the
| use of the standard TCP/IP features, such as the KEEPALIVE option.
|Catalog management enhancements
| The logic that TME 10 OPC uses when determining which catalog
| management actions to perform has been extended to manage the following
| situations:
|Some steps in a job are not executed, but are flushed. The datasets
| referred to in those steps are ignored by the catalog management
| function.
|A dataset referred to with disposition NEW in one step is also referred to
| in other steps. Logic to determine the action to perform in these cases
| has been added to the Catalog Management function.
|Dataset Delete function (EQQDELDS) improvements
| The Dataset Delete function has been enhanced to determine the correct
| action when a dataset referred to with disposition NEW in one step is also
| referred to in other steps. Logic to determine the correct action to perform in
| these cases has been added to the Dataset Delete function. The Dataset
| Delete function has also been improved to do the following:
|Delete datasets for which an expiration date was specified.
|Issue diagnostic information when the IDCAMS DELETE command or
| the DFHSM ARCHDEL command fails to delete a dataset.
|Current plan occurrence limit removal
| The maximum number of occurrences in the current plan has been increased
| from 32767 to 9999999. This enhancement enables you to manage the
| current plan more flexibly when you have large workloads.
|Operations in AD limit removal
| You can now define up to 255 operations in each Application Description.
| This enhancement provides for more flexibility in the definition of the
| workload.
|AD and OI consistency check
| The consistency between the Application Description and the Operator
| Instruction OPC databases is now enforced by OPC. For instance, whenever
| an operation is deleted the associated operator instructions is also deleted.
| Some usability enhancements have also been implemented in the Application
| Description dialogs when defining operator instructions. For instance, you
| can now also access temporary operator instructions.
|JCL editing from Application Description dialogs
| You can now customize the TME 10 OPC dialogs so that a library
| management application used in the customer's environment to manage the
| production jobs can be invoked from the Application Description OPC
| dialogs, thus increasing user productivity. New row commands have been
| added to invoke such an application from the Operation List panel while
| working with an Application Description.
xii TME 10 OPC Messages and Codes