Autosys Job Management - Release Summary

Unicenter AutoSys Job Management

Release Summary 4.5

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

2003 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

Chapter 1: Overview Documentation ............................................................................... 1–1 Supported Platforms .......................................................................... 1–2 Supported Platforms for asbIII and CCI ......................................................... 1–3 Compatibility with Earlier Versions ............................................................ 1–3 Supported Databases.......................................................................... 1–4 Installation and Upgrade Information .......................................................... 1–5

Installing Unicenter AutoSys JM 4.5 for Windows............................................ 1–5 Unicenter AutoSys JM and Oracle 9i ........................................................ 1–6

Temporary Tablespaces................................................................ 1–6 Rollback Segment ..................................................................... 1–7

Upgrading from an Earlier Version ............................................................. 1–7

Chapter 2: What Is New Unicenter AutoSys JM......................................................................... 2–1 Web Interface ................................................................................ 2–3

Chapter 3: Unicenter Integration Unicenter and Unicenter AutoSys JM ........................................................... 3–1 System Notes................................................................................. 3–2

Contents iii

Chapter 4: Database Notes Oracle Databases ..............................................................................4–1 Sybase Databases..............................................................................4–2

BCP Error.................................................................................4–3 Multiple Event Processors ..................................................................4–3

Microsoft SQL Server Databases ................................................................4–4 DBMaint Script ...............................................................................4–5

iv Release Summary

Chapter

1 Overview

Welcome to Unicenter® AutoSys® Job Management 4.5 (Unicenter AutoSys JM). Unicenter AutoSys JM is an automated control system for scheduling, monitoring, and reporting on jobs in a distributed computing environment. Before you install, review this summary for important additional information.

Documentation The documentation for Unicenter AutoSys JM Version 4.5 is in online format (PDF format) in the documentation directory on the software CD. In addition to this Release Summary, all other manuals can be viewed using Adobe Acrobat Reader. This online documentation is the most current at the time of this release.

In this guide, the term Windows refers to Microsoft Windows operating systems, Windows NT and higher. Unless specifically designated, Windows refers to any Microsoft Windows operating system supported by Unicenter AutoSys JM.

Overview 1–1

Supported Platforms

Supported Platforms Because of the dynamic nature of the various operating systems and databases supported, this list is subject to change. If you have any questions about compatibility, please check the AutoSys Support web page at: supportconnect.ca.com.

This CD contains support for Unicenter AutoSys JM 4.5 for the following platforms and operating system levels.

DEC Alpha Tru64 4.0f, 4.0g, 5.0, 5.1

HP 9000/800, 700, HP-UX 11, 11i

IBM RS/6000, AIX 4.3.3, 5.1, 5.2

Microsoft Windows NT 4.0 SP6, 2000 SP3, XP SP1, 2003

Microsoft Windows 98 (console only)

Sun SPARC Solaris 2.6, 2.7, 2.8, 2.9form Operating System

Red Hat Linux 7.2, 7.3, 8.0, 9.0

SuSE Linux Enterprise Server 8

This CD also contains support for Unicenter AutoSys JM 3.5 for the following platforms and operating system levels.

NCR UNIX 3.0.1, 3.0.2

Pyramid Reliant 5.4.2, 5.4.3

Sequent Dynix 4.2–4.5

Siemens Nixdorf SINIX 5.4.2

Silicon Graphics IRIX 6.2, 6.4, 6.5

1–2 Release Summary

Supported Platforms for asbIII and CCI

Supported Platforms for asbIII and CCI The platforms in the previous section are for Unicenter AutoSys JM without asbIII (CCI). The following platforms are for asbIII with CCI:

In AIX, if the runtime environment file set xlC.rte is below 3.6.6.0, asbIII will not run. Operating System

DEC Alpha Tru64 4.0f

HP 9000/800, 700, HP-UX 11, 11i

IBM RS/6000, AIX 4.3.3, 5.1

Microsoft Windows NT 4.0 SP6, 2000 SP2, XP SP1, 2003

Red Hat Linux 7.2, 7.3, 8.0, 9.0

Sun SPARC Solaris 2.6, 2.7, 2.8, 2.9

SuSE Linux Enterprise Server 8

Compatibility with Earlier Versions You can run Unicenter AutoSys JM Version 3.4.4 and later Remote Agents with Unicenter AutoSys JM Version 4.5. You must upgrade all other components (including the event processor, Event Server, and Console Utilities) to Version 4.5. Only Unicenter AutoSys JM Versions 3.4.4 and above are supported.

Note: With Unicenter AutoSys JM 4.5, the database does not support executing client utility applications from prior versions. That is, you cannot run a Unicenter AutoSys JM 3.x or 4.0 client utility (sendevent, jil, and so forth) against a Unicenter AutoSys JM 4.5 database. The client utilities must be upgraded to Unicenter AutoSys JM version 4.5 in order for the Unicenter AutoSys JM 4.5 database to accept input.

Overview 1–3

Supported Databases

Supported Databases ■ Sybase System 11.9.2, 12.0, 12.5

Sybase SQL server installation

- 300 MHz Pentium

- 128 MB RAM

- 64 MB swap file

- 486/66 DX2

- 16 MB RAM

■ Oracle 8.0.6, 8i, 9i

Oracle Server installation

- 300 MHz Pentium

- 128 MB RAM

- 128 MB swap file

- Oracle SQL*Net, v2.3, Net 8 installation

- 486/66 DX2

- 16 MB RAM

■ Microsoft SQL Server 7, and 2000

- 300 MHz Pentium

- 128 MB RAM

- 64 MB swap file

Notes:

The swap files should be at least twice the actual RAM size.

Microsoft SQL Server does not run on Windows NT workstations.


Installation and Upgrade Information

Installation and Upgrade Information Before you install this version, read the Installation Guide for your platform for system requirements, installation procedures, and configuration information.

If you are upgrading from a previous version, read the Unicenter AutoSys JM Upgrade Instructions for your platform.

Important! The Xpert component is no longer shipped with Unicenter AutoSys JM 4.5. When upgrading to Unicent r AutoSys JM 4.5, Xpert will be removed from your system. In place of the Xpert component, you should install Unicenter AutoSys JM Web Interface. The Web Interface provides all functionality of Xpert with the exception of Hostscape.

e

Installing Unicenter AutoSys JM 4.5 for Windows

When installing Unicenter AutoSys JM 4.5 for Windows, keep the following in mind:

■ Press the F1 key during the install to display the online help contents. This help describes the configuration options in the setup program.

■ To complete the installation process, you must restart your machine after the following:

1. Installing bundled Sybase.

2. Installing eTrust Access Control

3. Installing the CCI Component

4. Removing the Xpert Component following an upgrade.

■ You can now create the database from the new installation wizard. For more information see the Unicenter AutoSys Job Management for Windows Installation Guide.

Overview 1–5

Installation and Upgrade Information

Unicenter AutoSys JM and Oracle 9i

Temporary Tablespaces

During an installation, you will be asked for the name of the tablespace that will be the temporary tablespace.

Note: For Oracle 9i, the tablespace you specify must be of type temporary, not type permanent. Consult your Oracle DBA if you are not sure of the current tablespace type.

If you do not specify a true “temporary” tablespace, then your auto_install script will fail with the following message:

ORA-12911: permanent tablespace cannot be temporary tablespace

and you will not have a valid database.

If you are using a Windows installation and Oracle 9i, you must run the CreateNewDB script to configure the database and load the database objects. The CreateNewDB script gives you the option of creating the Oracle tablespaces manually, or having the script make the tablespace automatically for you. If you have already created tablespaces to be used before running the CreateNewDB script, then you must verify that the temp tablespace you specified is actually of type temporary, and not type permanent. If you do not specify a true temporary tablespace, then your CreateNewDB script will fail with the ORA-12911 error previously cited, and you will not have a valid database.

However, if you have the CreateNewDB script make your temp tablespace for you, then the script will create this tablespace as type temporary and the rest of the database objects will be created successfully.


Upgrading from an Earlier Version

Rollback Segment

During a Windows installation, a rollback segment will be created if you decide to have the installation make your Oracle tablespaces. In Oracle 9i, this rollback will not be created successfully unless your Oracle server has the init.ora file parameter called UNDO_MANAGEMENT set to MANUAL. Before running the installation, consult your Oracle DBA to find out the setting. By default, the parameter UNDO_MANAGEMENT is set to AUTO. To change this parameter, edit the init.ora file on your Oracle 9i server machine by changing the parameter called UNDO_MANAGEMENT from AUTO to MANUAL. The line should look like the following:

UNDO_MANAGEMENT=MANUAL

After the parameter has been changed, you must stop and restart your Oracle Server for the change to take effect.

Note: If you do not specify UNDO_MANAGEMENT to MANUAL in the init.ora file for Oracle 9i, the Windows Installation will produce the following error:

ORA-30019: Illegal rollback Segment operation in Automatic Undo mode.

Upgrading from an Earlier Version If you are upgrading from the Unicenter AutoSys JM 3.4.4, 3.5, or 3.5.1 versions, see the Unicenter AutoSys JM 4.5 upgrade instructions for your platform. You must run the upgrade script for all upgrades. If you are upgrading from a Unicenter AutoSys JM beta version, remove the beta software before installing Unicenter AutoSys JM 4.5.

Overview 1–7

Chapter

2 What Is New

Unicenter AutoSys JM Version 4.5 offers all the functions available in Versions 3.4, 3.5, and 4.0 plus the following new features.

Unicenter AutoSys JM The following functions are new for Unicenter AutoSys JM 4.5.

Asset Level Security Unicenter AutoSys JM incorporates the eTrust™ Access Control (eTrust AC) component to add security functions to Unicenter AutoSys JM. This allows administrators to create a fully secured environment for Unicenter AutoSys JM users. Security levels can now control who has access to use and control key functions such as scheduling jobs, calendars, cycles, machines, global variables, and job ownership. Security functions have been added to prevent unauthorized users from starting or shutting down Unicenter AutoSys JM, disabling security, and accessing the Web Interface views. Using Asset Level Security, administrators can now control which users have access to the assets and features of Unicenter AutoSys JM.

Multiple Installation Options Unicenter AutoSys JM offers the availability of three different installation choices. You now have the option of an Express, Typical, or Custom Installation.

External Job Validation Unicenter AutoSys JM now includes an optional feature, which provides the ability to validate job information before being inserted into the AutoSys database. A custom DLL or Shared Object can be created, which will be loaded by JIL or job editor to appropriately accept, deny, or modify the job before it is submitted to AutoSys.

What Is New 2–1

Unicenter AutoSys JM

Database Enhancements Unicenter AutoSys JM 4.5 database enhancements include increased field length for box name, job name, machine name and job conditions. Modifications to jobs including job deletions are tracked.

Remote Manager External Job Dependency Support Unicenter AutoSys JM provides support for job dependencies for jobs within the Unicenter, CA-7, CA-JobTrac, and CA-Scheduler environments. Unicenter AutoSys JM can now receive job information from these Remote Managers establishing an external dependency (also known as a Unicenter trigger) with an AutoSys job. When a Unicenter AutoSys JM job with an external dependency on a Remote Manager Job has completed, its status will be sent back to the Remote Manager for further processing.

Remote Manager User Authentication Support The Unicenter AutoSys JM 4.5 Broker performs user authentication on all job submission requests from a Remote Manager. As a result, job access rights set either via Unicenter AutoSys JM native security (JIL) or through eTrust AC asset-level security will be honored.

eTrust Access Control Administration The autosys_secure utility has been enhanced with new menu options for the basic administration of eTrust AC. The new eTrust Administration menu option items give authorized users the ability to:

• Enable/disable eTrust AC security within the Unicenter AutoSys JM environment

• Set a password to validate the eTrust AC client database subscription to the eTrust AC server database for policy updates

• Add or remove eTrust AC administrators

• Define valid eTrust AC hosts that can be used to administer the eTrust AC server and authorize eTrust AC administrators to use these hosts to make policy updates

• Add or remove eTrust AC client remote subscribers to the eTrust AC server

Multiple Super Users Unicenter AutoSys JM adds the capability for a Super User to create multiple Super Users. A Super User can also be assigned to a specific domain or host name. This allows access only from that assigned domain or host machine. This provides added usability along with new security and access control.


Web Interface

Generic File Watcher This new feature allows a user to specify a generic file watcher. When the file watcher finds the first file that matches the criteria, it will start monitoring that file. If other files show up after the file watcher starts to monitor, they will be ignored.

License Unicenter AutoSys JM 4.5, licensing no longer uses gatekeeper. Instead, CA’s lic98 licensing library is used to license Unicenter AutoSys JM. Unlike prior versions of Unicenter AutoSys JM where Event Processor (EP) and all clients (Remote Agent (RA) and Console Utilities) were licensed, Unicenter AutoSys JM 4.5 checks for EP and RA license only.

Web Interface The following functions are new for Unicenter AutoSys JM 4.5 Web Interface.

Web Graphical User Interface Enhancements The Web Interface GUI provides additional monitoring, editing, and administrative capabilities. The Web Interface GUI now provides the capability to view selected remote agent files. These interface enhancements integrate with the new security functions in Unicenter AutoSys JM 4.5.

Unicenter AutoSys JM Xpert The ability to simulate jobs according to their runtime.

Total Job Management Provides a GUI to create, modify and delete jobs in the Unicenter AutoSys JM database.

Real Time Job Flow Provides you a realistic view of the job dependency relations in the Unicenter AutoSys JM environment. Job flows are automatically arranged based on their dependencies.

Multiple Installation Options Unicenter AutoSys JM offers the availability of three different installation choices. You now have the option of an Express, Typical, or Custom Installation.

View Filter Enables you to view jobs based on a set of criteria.

What Is New 2–3

Web Interface

Rule Based View Simplifies the creation of the personalized view for the administrator. Allowing statically selected jobs to be displayed in a saved view, while dynamically updating the view based on predefined rules.

Across Instance Job Flow Allows jobs from different instances to be displayed in the same job flow.

Alarm Management In addition to viewing the alarms, you can respond, acknowledge, close the alarm, or see a record of who responded to the alarm in the database.

eTrust AC Security You can now enforce all of the security policies defined in the autosys policy manage database (pmdb). In addition, during installation the local Access Control database is installed on the Web server machine.

Unicenter AutoSys JM Security The Web Interface supports the native security as defined in Unicenter AutoSys JM, including support for the super user.

Dual Unicenter AutoSys JM Server support Currently active server names will be shown on the browser.

Remote Command Service The Remote Command Service enables the Unicenter AutoSys JM Web Interface to perform such requests as user authentication when mapping a Unicenter AutoSys JM Web Interface user to a Unicenter AutoSys JM user, processing JIL requests and servicing log requests (Event Processor, Remote Agent or Job Log).


Chapter

3 Unicenter Integration

Unicenter AutoSys JM 4.5 can be installed and run as a stand-alone product or as an option in Unicenter, the enterprise management tool from Computer Associates International, Inc. (CA).

Unicenter and Unicenter AutoSys JM The two primary ways in which Unicenter AutoSys JM 4.5 works with Unicenter are defined following:

■ WorldView For Windows Users Only: WorldView includes the Real World Interface and provides an extensive set of tools to enable you to customize any view of your enterprise according to its logical structure. The 2D map in WorldView allows you to visualize the objects stored in the Common Object Repository (CORe.) The Unicenter AutoSys JM class and Unicenter AutoSys JM instances (Unicenter AutoSys JM objects) are added and deleted in the COR using the “autosys_wv” utility. Unicenter AutoSys JM applications for the instances can be launched from the 2D map. When Unicenter AutoSys JM is integrated with Unicenter® Network and Systems Management (Unicenter NSM) Framework, Unicenter AutoSys JM becomes a managed object. Unicenter NSM will store information about the AutoSys class and its objects (Unicenter AutoSys JM instances) in the CORe.

Once Unicenter NSM Framework is installed, Unicenter NSM Framework creates a default repository. The repository is called “hostname_TNGDB.” To perform any operation in the repository, you need to connect to the repository.

Note: WorldView, 2D map and the auto_wv utility will work with Unicenter NSM Framework and the full Unicenter product.

Unicenter Integration 3–1

System Notes

■ Event Management You can configure Unicenter AutoSys JM to publish events for every job to the Unicenter Event Management Console. This console provides a view of activity across a network of systems, including the desired level of event processing in Unicenter AutoSys JM.

To integrate Unicenter AutoSys JM 4.5 with Unicenter, follow these steps:

1. Install Unicenter first. See the Unicenter documentation for instructions.

2. Next, install AutoSys 4.5, following the instructions in the Unicenter AutoSys Job Management for UNIX Installation Guide, or the Unicenter AutoSys Job Management for Windows Installation Guide.

Use the instructions following under Integrating with Unicenter to complete the integration for Windows, located in this chapter.

System Notes Unicenter AutoSys JM 4.5 integrates with Unicenter Event Management differently from the previous version of Unicenter AutoSys JM 3.5.1.

In Version 3.5.1, the Remote Agent reported events to Unicenter when they were sent to the Event Server. Unicenter NSM Framework Agent or Event Agent must have been installed on each remote machine, with Unicenter AutoSys JM set to report to it.

In Version 4.5, the Event Processor reports events to Unicenter when processed. Unicenter NSM Framework Agent or Event Agent must be installed on the event processor machine.

If you upgrade your Event Processor from Version 3.5.1 to Version 4.5 but do not upgrade all of your Remote Agents, you need to disable Unicenter event reporting on the Remote Agents to avoid reporting the same events twice.

For more information about Unicenter Integration, see the Appendix Unicenter Integration in the Unicenter AutoSys Job Management for Windows User Guide, or the Unicenter AutoSys Job Management for UNIX User Guide.


Chapter

4 Database Notes

The following chapter describes uses and procedures for the different databases supported by Unicenter AutoSys JM 4.5.

Oracle Databases Oracle and the Hong Kong Time Zone Setting:

If your Windows machine is using the Hong Kong time zone and you run the CreateNewDB utility, you will get Oracle internal errors. If you see these errors please contact your Oracle support representative.

You can work around this problem by setting the time zone to something other than Hong Kong, then running the CreateNewDB utility. When the process completes, reset your time zone to Hong Kong.

Database Notes 4–1

Sybase Databases

Sybase Databases Installing Bundled Sybase with SQL Anywhere:

You may encounter problems after installing the Unicenter AutoSys JM 4.5 bundled Sybase on a node that already has SQL Anywhere installed. If you are unable to start the dataserver and get error 2140, you may be missing some required registry entries. Modify your registry as follows:

1. Create a new key called “server” under:

hkey_local__machine\ software\sybase

2. Create a new key called “local” under:

hkey_local_machine\ software\sybase\server

3. Create a new key called “parameters” under:

hkey_local_machine\ software\sybase\server\local

4. Create the following name-value pairs under:

hkey_local_machine\software\sybase\server\local\parameters

key:

Arg0 -dc:\autosys.prd\sql10\data\master.dat

Arg1 -slocal

Arg2 -ec:\autosys.prd\sql10\install\errorlog

Arg3 -ic:\autosys.prd\sql10\ini

Arg4 -mc:\autosys.prd\sql10

where :

c:\autosys.prd Represents the Unicenter AutoSys JM base directory.

5. Start the SYBSQL_LOCAL service.

6. Add the following environment variables to the “system” path:

%SYBASE% %SYBASE%\bin

Make sure these variables are placed before any SQL Anywhere environment variables.

7. Restart your system.

To avoid this problem, install the bundled Sybase on a different node than the one where SQL Anywhere is installed.


Sybase Databases

BCP Error

Running the Unicenter AutoSys JM provided Perl script, AUTOBCP.NT, with a Sybase database will occasionally cause the following Dr. Watson for Windows Fatal Error message to appear:

Could not attach to the application. Windows Error Code = 87.

You can ignore this message, which is caused by the Sybase application BCP.EXE. To dismiss the message dialog, click OK.

Multiple Event Processors

Since Unicenter AutoSys JM 4.5 supports multiple event processors, there are a few changes that we recommend making to your Sybase dataserver.

1. Upgrade the procedure cache to at least 40 percent.

To view the current settings enter the following at an isql or xql prompt:

sp_configure ‘procedure cache percent’ go

To change the value to 40 percent, enter the following:

sp_configure ‘procedure cache percent’, 40 go

Note: In Sybase 12.5, the configuration parameter is called procedure cache memory, not procedure cache percent. For Sybase 12.5 users, we recommend this setting be doubled from its default value.

2. Turn on row-level locking.

To view the current setting for row-level locking, enter the following at an isql or xql prompt:

sp_configure ‘lock scheme’ Go

If row-level locking is turned on, it will be set to ‘datarows’.

To turn on row-level locking, enter the following at an isql or xql prompt:

sp_configure ‘lock scheme’, 0, datarows go


Microsoft SQL Server Databases

Microsoft SQL Server Databases Unicenter AutoSys JM 4.5 for Windows supports Microsoft SQL Server Version 7.0 and 2000.

When using Microsoft SQL Server, keep the following in mind:

■ When you install your Microsoft SQL Server, change the Sort Option to “Dictionary order, Case-sensitive,” and add the Additional Network Support to “TCP/IP Sockets.” The Network Support should be both Named Pipes and TCP/IP Sockets.

■ If you are using Microsoft SQL Server as your Unicenter AutoSys JM Event Server, you must install the appropriate Microsoft SQL Server client utilities on each Event Processor and Remote Agent machine, and you must ensure that there is database connectivity between the Event Server, Event Processor, and Remote Agent machines.

■ If you are running Unicenter AutoSys JM with Microsoft SQL Server databases as your Event Servers, you must do one of the following:

Install all of the Unicenter AutoSys JM components for a specific instance on machines that are in the same domain.

Give all Unicenter AutoSys JM users user accounts (with at least Guests Group Membership) on the database machines.

If you do not configure your Microsoft SQL Server machines in one of these ways, users will not be able to access the database through the GUIs or run Unicenter AutoSys JM jobs (as the Owner of the job). With Microsoft SQL Server, each user must have the proper user permissions on the database machine to access the Microsoft SQL Server database. You must meet Microsoft SQL Server security requirements in order for Unicenter AutoSys JM users to access the database.


DBMaint Script

DBMaint Script In previous versions of Unicenter AutoSys JM, there was only a single Event Processor. When it came time to run the DBMaint script, the Event Processor would stop processing events to run DBMaint. With multiple Event Processors, only one event processor is required to run DBMaint, the other event processors will continue processing events during this time. The default DBMaint script shipped with Unicenter AutoSys JM should continue to run as designed. However, if you have modified your DBMaint script, you may reevaluate what it does and make sure that it will not be affected by having an event processor processing events while it is running.


Index

I A

Installation Upgrade Information, 1-5 AutoSys

license keys, 2-3 Installing Unicenter AutoSys JM 4.5 Oracle 9i, 1-6 Windows, 1-5

C

L Compatability, 1-3

license keys, 2-3 D

M Database Microsoft SQL Server, 4-4 Oracle, 4-1 Microsoft SQL Server Supported, 1-4 Database, 4-4 Sybase, 4-2 Multiple Event Processors, 4-3

DBMaint, 4-5

Documentation, 1-1 O

E Oracle Database, 4-1 Information, 1-6 Event Processor Rollback Segment, 1-7 Multiple, 4-3

Index–1

S

Supported Databases, 1-4

Supported Platforms, 1-2 asblll and CCI, 1-3 Unicenter AutoSys JM 3.5, 1-2 Unicenter AutoSys JM 4.5, 1-2

Sybase Database, 4-2

System Notes, 3-2

U

Unicenter Integration, 3-1 System Notes, 3-2 Unicenter AutoSys JM, 3-1

Upgrading From an Earlier Version, 1-7

W

What Is New, 2-1 Unicenter AutoSys JM, 2-1 Web Interface, 2-3

Index–2 User Guide

Documents

Autosys Job Management - Release Summary