03.03.2013 Views

Messages and Codes - e IBM Tivoli Composite - IBM

Messages and Codes - e IBM Tivoli Composite - IBM

Messages and Codes - e IBM Tivoli Composite - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Summary of <strong>Tivoli</strong> OPC Version 2 Release 3 Enhancements<br />

Job Scheduling Console<br />

The new <strong>Tivoli</strong> Job Scheduling Console (JSC) is a Java-based, client/server<br />

application. The key advantages of the JSC are the ability to perform<br />

administration <strong>and</strong> operation tasks in a graphical manner <strong>and</strong> the ability to access<br />

multiple OPC controllers from a single console.<br />

The JSC can:<br />

Display lists of objects already defined to OPC, from the database <strong>and</strong> from the<br />

current plan, by using flexible filtering criteria<br />

Work with application descriptions including jobs <strong>and</strong> their dependencies, time<br />

restrictions (input arrival time, deadline, duration), <strong>and</strong> run cycles<br />

Work with special resource <strong>and</strong> workstation definitions<br />

Modify occurrences, workstation status, <strong>and</strong> special resource information from<br />

the current plan.<br />

The JSC retains the OPC security model. Each data access request is validated<br />

by the controller as it is done currently for ISPF users.<br />

The JSC is a real-time interface with OPC <strong>and</strong> can be used concurrently with the<br />

ISPF interface. It is available for various UNIX platforms, Windows NT, <strong>and</strong><br />

Windows 98. The OPC Connector, which is a backend component supporting the<br />

JSC, is available for various UNIX platforms <strong>and</strong> Windows NT.<br />

Catalog Management — Data Availability<br />

The new Catalog Management – Data Availability feature improves OPC<br />

performance for job restart <strong>and</strong> job log retrieval functions. Job runtime information,<br />

for example, the sysout datasets, is maintained locally on the tracked system. The<br />

controller retrieves this information only when needed for catalog management<br />

actions, eliminating the network <strong>and</strong> processing overhead associated with the<br />

transmission of superfluous data. The runtime information at the tracked system is<br />

managed by a new component, the OPC Data Store. Using the OPC Data Store,<br />

OPC Tracker processes are bypassed <strong>and</strong> are dedicated to the time-critical job<br />

submission <strong>and</strong> tracking tasks. A new feature is provided to selectively determine<br />

how long job runtime information is kept in the Data Store. This new feature is<br />

especially useful when a joblog archiving product is used concurrently with OPC.<br />

OS/390 Workload Manager Support<br />

OS/390 Workload Manager, when used in goal mode, provides a new, policy-based<br />

management of deadlines for critical jobs. Some CPU-type operations can now be<br />

marked as critical in OPC. When such a critical operation is late, according to the<br />

specified policy, OPC interfaces with Workload Manager to move the associated job<br />

to a higher performance service class. Thus the job receives appropriate additional<br />

system resource to reduce or eliminate the delay. Several policies are available to<br />

© Copyright <strong>IBM</strong> Corp. 1991, 1999 xiii

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!