Beruflich Dokumente
Kultur Dokumente
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.
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.
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
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
Overview
1
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.
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.
This CD also contains support for Unicenter AutoSys JM 3.5 for the following
platforms and operating system levels.
In AIX, if the runtime environment file set xlC.rte is below 3.6.6.0, asbIII will not
run. Operating System
Overview 1–3
Supported Databases
Supported Databases
■ Sybase System 11.9.2, 12.0, 12.5
- 128 MB RAM
- 64 MB swap file
- 486/66 DX2
- 16 MB RAM
- 128 MB RAM
- 486/66 DX2
- 16 MB RAM
- 128 MB RAM
- 64 MB swap file
Notes:
The swap files should be at least twice the actual RAM size.
If you are upgrading from a previous version, read the Unicenter AutoSys JM
Upgrade Instructions for your platform.
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:
■ 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
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
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.
Rollback Segment
After the parameter has been changed, you must stop and restart your Oracle
Server for the change to take effect.
Overview 1–7
Chapter
What Is New
2
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.
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.
• 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
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.
View Filter
Enables you to view jobs based on a set of criteria.
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 Integration
3
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).
■ 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.
Note: WorldView, 2D map and the auto_wv utility will work with
Unicenter NSM Framework and the full Unicenter product.
■ 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.
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.
Database Notes
4
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.
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:
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 :
Make sure these variables are placed before any SQL Anywhere
environment variables.
To avoid this problem, install the bundled Sybase on a different node than the
one where SQL Anywhere is installed.
BCP Error
You can ignore this message, which is caused by the Sybase application
BCP.EXE. To dismiss the message dialog, click OK.
Since Unicenter AutoSys JM 4.5 supports multiple event processors, there are a
few changes that we recommend making to your Sybase dataserver.
To view the current settings enter the following at an isql or xql prompt:
sp_configure ‘procedure cache percent’
go
To view the current setting for row-level locking, enter the following at an
isql or xql prompt:
sp_configure ‘lock scheme’
Go
■ 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.
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
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.
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
Compatability, 1-3
L
Database
M
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 U
Sybase
Database, 4-2
W
System Notes, 3-2