Embed Size (px)
Citation preview
IBM
Tivoli
Workload
Scheduler
Release
Notes
Version
8.2
(Maintenance
Release
April
2004)
SC32-1277-01
���
IBM
Tivoli
Workload
Scheduler
Release
Notes
Version
8.2
(Maintenance
Release
April
2004)
SC32-1277-01
���
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
“Notices”
on
page
25.
Refreshed
Edition
(April
2004)
This
edition
applies
to
version
8,
release
2,
modification
level
0
of
IBM
Tivoli
Workload
Scheduler
(program
number
5698-WSH)
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
©
Copyright
International
Business
Machines
Corporation
1999,
2004.
All
rights
reserved.
US
Government
Users
Restricted
Rights
–
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
Contents
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Maintenance
Release
.
.
.
.
.
.
.
.
.
.
. v
Contacting
IBM
Software
Support
.
.
.
.
.
.
. v
Conventions
Used
in
This
Manual
.
.
.
.
.
.
. v
Typeface
conventions
.
.
.
.
.
.
.
.
.
. v
Operating
system-dependent
variables
and
paths
vi
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Publications
for
IBM
Tivoli
Workload
Scheduler
vi
Publications
for
IBM
Tivoli
Workload
Scheduler
for
z/OS
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Softcopy
Collection
Kit
for
IBM
Tivoli
Workload
Scheduler
for
z/OS
.
.
.
.
.
.
.
.
.
.
. vii
Related
publications
.
.
.
.
.
.
.
.
.
. viii
Accessing
Publications
Online
.
.
.
.
.
.
. viii
Ordering
Publications
.
.
.
.
.
.
.
.
. viii
Providing
Feedback
about
Publications
.
.
.
. viii
Chapter
1.
About
This
Release
.
.
.
.
. 1
New
Features
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1
Wizard-guided
Installation
Process
.
.
.
.
.
. 1
Ability
to
Choose
the
Type
of
Agent
to
Install
.
. 1
Secure
Authentication
and
Encryption
.
.
.
.
. 2
Work
Across
Firewalls
.
.
.
.
.
.
.
.
.
. 2
Centralized
Security
Mechanism
.
.
.
.
.
.
. 2
Integration
with
Data
Warehousing
.
.
.
.
.
. 3
Job
Return
Code
Mapping
.
.
.
.
.
.
.
.
. 3
Extended
Autotrace
Feature
.
.
.
.
.
.
.
. 3
Enhanced
Time
Zone
Support
.
.
.
.
.
.
. 3
New
Options
for
Handling
Time
Constraints
.
. 3
Event
State
Management
.
.
.
.
.
.
.
.
. 4
Interoperability
Notes
.
.
.
.
.
.
.
.
.
.
. 4
End-to-end
Environment
.
.
.
.
.
.
.
.
. 4
Compatibility
Notes
.
.
.
.
.
.
.
.
.
.
.
. 5
Chapter
2.
Installation
and
Upgrade
Notes
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
System
Requirements
.
.
.
.
.
.
.
.
.
.
. 7
IBM
Tivoli
Workload
Scheduler
Requirements
.
. 7
Software
Requirements
.
.
.
.
.
.
.
.
.
.
. 8
Installation
Methods
and
Supported
Operating
Systems
.
.
.
.
.
.
.
.
.
.
.
.
.
. 10
Installation
Program
Software
Requirements
.
. 11
Installation
Notes
.
.
.
.
.
.
.
.
.
.
.
. 12
The
Installation
CDs
.
.
.
.
.
.
.
.
.
. 12
Installing
Using
the
twsinst
Script
.
.
.
.
.
. 13
Upgrade
Notes
.
.
.
.
.
.
.
.
.
.
.
.
. 13
End-to-end
Environment
.
.
.
.
.
.
.
.
. 13
Chapter
3.
Product
Limitations,
Problems,
and
Workarounds
.
.
.
.
. 15
Software
Limitations
.
.
.
.
.
.
.
.
.
.
. 15
Software
Problems
and
Workarounds
.
.
.
.
.
. 16
Fixed
Defects
.
.
.
.
.
.
.
.
.
.
.
.
.
. 20
Chapter
4.
Internationalization
Notes
23
Enabling
Language
Support
.
.
.
.
.
.
.
.
. 23
Software
Limitations,
Problems
and
Workarounds
23
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 25
Open
Source:
Test
.
.
.
.
.
.
.
.
.
.
.
. 26
Open
Source:
OpenSSL
.
.
.
.
.
.
.
.
.
. 27
LICENSE
ISSUES
.
.
.
.
.
.
.
.
.
.
. 27
OpenSSL
License
.
.
.
.
.
.
.
.
.
.
. 27
Original
SSLeay
License
.
.
.
.
.
.
.
.
. 28
Open
Source:
SNMP
Library
.
.
.
.
.
.
.
.
. 29
Open
Source:
Time
Zone
Library
.
.
.
.
.
.
. 29
Toolkit
of
Tivoli
Internationalization
Services
.
.
. 29
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 30
©
Copyright
IBM
Corp.
1999,
2004
iii
||
iv
IBM
Tivoli
Workload
Scheduler
Release
Notes
Preface
This
Release
Notes
document
provides
important
information
about
IBM®
Tivoli®
Workload
Scheduler,
Version
8.2.
These
notes
are
the
most
current
information
for
the
product
and
take
precedence
over
all
other
documentation.
Review
these
notes
thoroughly
before
installing
or
using
this
product.
Maintenance
Release
This
is
a
maintenance
refresh
of
the
corresponding
IBM
Tivoli
Workload
Scheduler
Version
8.2
release
notes,
form
number
SC32–1277–00.
It
contains
an
update
for
APAR
IY50766
and
updates
the
list
of
open
problems
after
the
product
refreshes
via
fixpack.
Throughout
the
book,
the
changed
or
new
sections
are
marked
by
revision
bars.
If
your
version
of
the
product
has
not
been
fixed
for
a
particular
APAR,
refer
to
the
original
version
of
the
release
notes
for
the
corresponding
information.
Contacting
IBM
Software
Support
If
you
have
a
problem
with
any
Tivoli
product,
you
can
contact
IBM
Software
Support.
See
the
IBM
Software
Support
Guide
at
the
following
Web
site:
http://techsupport.services.ibm.com/guides/handbook.html
The
guide
provides
information
about
how
to
contact
IBM
Software
Support,
depending
on
the
severity
of
your
problem,
and
the
following
information:
v
Registration
and
eligibility
v
Telephone
numbers
and
addresses,
depending
on
the
country
in
which
you
are
located
v
Information
you
must
have
before
contacting
IBM
Software
Support
Conventions
Used
in
This
Manual
This
manual
uses
several
conventions
for
special
terms
and
actions,
operating
system-dependent
commands
and
paths.
Typeface
conventions
This
manual
uses
the
following
IBM-style
typeface
conventions:
Bold
Commands
(except
those
in
all
capital
letters)
are
displayed
in
bold
font.
Italic
Variables
and
values
you
must
provide
are
displayed
in
italic
font.
Words
and
phrases
that
are
emphasized
are
also
displayed
in
italic
font.
Monospace
Code
examples,
output,
text
you
must
type,
and
system
messages
are
displayed
in
monospace
font.
©
Copyright
IBM
Corp.
1999,
2004
v
|
||||
|||
Operating
system-dependent
variables
and
paths
This
manual
uses
the
UNIX®
convention
for
specifying
environment
variables
and
for
directory
notation.
When
using
the
Windows®
command
line,
replace
$variable
with
%
variable%
for
environment
variables
and
replace
each
forward
slash
(/)
with
a
backslash
(
\)
in
directory
paths.
Note:
If
you
are
using
the
bash
shell
on
a
Windows
system,
you
can
use
the
UNIX
conventions.
Publications
This
section
lists
publications
in
the
IBM
Tivoli
Workload
Scheduler
library.
It
also
describes
how
to
access
Tivoli
publications
online,
how
to
order
Tivoli
publications,
and
how
to
make
comments
on
Tivoli
publications.
Publications
for
IBM
Tivoli
Workload
Scheduler
The
following
manuals
are
available
in
the
IBM
Tivoli
Workload
Scheduler
library:
v
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide,
SC32-1273
Describes
planning
and
installing
IBM
Tivoli
Workload
Scheduler.
v
IBM
Tivoli
Workload
Scheduler
Reference
Guide,
SC32-1274
Explains
the
IBM
Tivoli
Workload
Scheduler
command
line,
understanding
how
extended
and
network
agents
work,
and
integrating
IBM
Tivoli
Workload
Scheduler
with
NetView®
and
with
IBM
Tivoli
Business
Systems
Manager.
v
IBM
Tivoli
Workload
Scheduler
Troubleshooting
and
Error
Messages,
SC32-1275
Interprets
IBM
Tivoli
Workload
Scheduler
error
messages,
and
provides
sources
of
information
that
will
help
you
in
solving
problems
with
IBM
Tivoli
Workload
Scheduler.
v
IBM
Tivoli
Workload
Scheduler
Job
Scheduling
Console
Release
Notes,
SC32-1258
Provides
information
about
working
with
IBM
Tivoli
Workload
Scheduler,
regardless
of
platform,
from
a
common
GUI.
v
IBM
Tivoli
Workload
Scheduler
Job
Scheduling
Console
User’s
Guide,
SC32-1257
Provides
information
about
working
with
IBM
Tivoli
Workload
Scheduler,
regardless
of
platform,
from
a
common
GUI.
v
IBM
Tivoli
Workload
Scheduler
for
Applications
User’s
Guide,
SC32-1278
Describes
installing,
using,
and
troubleshooting
for
the
IBM
Tivoli
Workload
Scheduler
extended
agents.
v
IBM
Tivoli
Workload
Scheduler
for
Applications
Release
Notes,
SC32-1279
Provides
last-minute
information
about
the
IBM
Tivoli
Workload
Scheduler
extended
agents.
v
IBM
Tivoli
Workload
Scheduler
AS/400®
Limited
Fault-tolerant
Agent
User’s
Guide,
SC32-1280
Describes
installing,
configuring,
and
using
IBM
Tivoli
Workload
Scheduler
fault-tolerant
agents
on
AS/400.
v
IBM
Tivoli
Workload
Scheduler
Plus
Module
User’s
Guide,
SC32-1276
Explains
setting
up
and
using
the
IBM
Tivoli
Workload
Scheduler
Plus
module.
vi
IBM
Tivoli
Workload
Scheduler
Release
Notes
Publications
for
IBM
Tivoli
Workload
Scheduler
for
z/OS
The
following
documents
are
available
in
the
IBM
Tivoli
Workload
Scheduler
for
z/OS
library:
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
,
SC32-1265
Describes
how
to
customize
IBM
Tivoli
Workload
Scheduler
for
z/OS.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Diagnosis
Guide
and
Reference,
SC32-1261
Provides
information
to
help
diagnose
and
correct
possible
problems
when
using
the
product.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
General
Information,
SC32-1256
Describes
the
benefits
of
the
entire
IBM
Tivoli
Workload
Scheduler
suite.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Getting
Started,
SC32-1262
Describes
concepts
and
terminology
of
IBM
Tivoli
Workload
Scheduler
for
z/OS™
and
provides
instructions
to
get
you
working
with
the
product
as
soon
as
possible.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Installation
Guide,
SC32-1264
Explains
how
to
install
IBM
Tivoli
Workload
Scheduler
for
z/OS.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Licensed
Program
Specifications,
GI11-4208
Provides
planning
information
about
IBM
Tivoli
Workload
Scheduler
for
z/OS.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Managing
the
Workload,
SC32-1263
Explains
how
to
plan
and
schedule
the
workload
and
how
to
control
and
monitor
the
current
plan.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Memo
to
Users,
GI11-4209
Provides
a
summary
of
changes
for
the
current
release
of
the
product.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Messages
and
Codes,
SC32-1267
Explains
messages
and
codes.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Program
Directory,
GI11-4203
Provided
with
the
IBM
Tivoli
Workload
Scheduler
for
z/OS
installation
tape,
describes
all
of
the
installation
materials
and
gives
installation
instructions
specific
to
the
product
release
level
or
feature
number.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Programming
Interfaces,
SC32-1266
Provides
information
to
write
application
programs.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Quick
Reference,
SC32-1268
Provides
a
quick
and
easy
consultation
reference
to
operate
the
product.
Softcopy
Collection
Kit
for
IBM
Tivoli
Workload
Scheduler
for
z/OS
All
the
books
in
the
library,
except
the
licensed
publications,
are
available
in
displayable
softcopy
form
in
the
following
collection
kits:
v
IBM
Online
Library
Omnibus
Edition
OS/390®
Collection
Kit,
SK2T-6700.
v
IBM
Online
Library
z/OS
Software
Products
Collection
Kit,
SK2T-4270.
You
can
read
the
softcopy
books
on
CD-ROMs
using
these
IBM
licensed
programs:
v
Softcopy
Reader
v
BookManager®
READ/2
v
BookManager
READ/DOS
v
BookManager
READ/6000
Preface
vii
All
the
BookManager
programs
need
a
personal
computer
equipped
with
a
CD-ROM
disk
drive
(capable
of
reading
disks
formatted
in
the
ISO
9660
standard)
and
a
matching
adapter
and
cable.
For
additional
hardware
and
software
information,
refer
to
the
documentation
for
the
specific
BookManager
product
you
are
using.
Updates
to
books
between
releases
are
provided
in
softcopy
only.
Related
publications
The
Tivoli
Software
Glossary
includes
definitions
for
many
of
the
technical
terms
related
to
Tivoli
software.
The
Tivoli
Software
Glossary
is
available,
in
English
only,
at
the
following
Web
site:
http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm
Accessing
Publications
Online
The
documentation
CD
contains
the
publications
that
are
in
the
product
library.
The
format
of
the
publications
is
PDF,
HTML,
or
both.
To
access
the
publications
using
a
Web
browser,
open
the
infocenter.html
file.
The
file
is
in
the
appropriate
publications
directory
on
the
product
CD.
IBM
posts
publications
for
this
and
all
other
Tivoli
products,
as
they
become
available
and
whenever
they
are
updated,
to
the
Tivoli
Software
Information
Center
Web
site.
The
Tivoli
Software
Information
Center
is
located
at
the
following
Web
address:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
Click
the
IBM
Tivoli
Workload
Scheduler
link
to
access
the
product
library.
Note:
If
you
documents
on
other
than
letter-sized
paper,
select
the
Fit
to
page
check
box
in
the
Adobe
Acrobat
window.
This
option
is
available
when
you
click
File
→
Print.
Fit
to
page
ensures
that
the
full
dimensions
of
a
letter-sized
page
on
the
paper
that
you
are
using.
Ordering
Publications
You
can
order
many
Tivoli
publications
online
at
the
following
Web
site:
http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi
You
can
also
order
by
telephone
by
calling
one
of
these
numbers:
v
In
the
United
States:
800-879-2755
v
In
Canada:
800-426-4968
In
other
countries,
see
the
following
Web
site
for
a
list
of
telephone
numbers:
http://www.ibm.com/software/tivoli/order-lit/
Providing
Feedback
about
Publications
If
you
have
comments
or
suggestions
about
Tivoli
products
and
documentation,
complete
the
customer
feedback
survey
at
the
following
Web
site:
http://www.ibm.com/software/sysmgmt/products/support
viii
IBM
Tivoli
Workload
Scheduler
Release
Notes
Chapter
1.
About
This
Release
This
chapter
describes
this
release
of
IBM
Tivoli
Workload
Scheduler,
Version
8.2.
It
includes
the
following
sections:
v
New
Features
v
“Interoperability
Notes”
on
page
4
v
“Compatibility
Notes”
on
page
5
New
Features
IBM
Tivoli
Workload
Scheduler
Version
8.2
features
the
following
enhancements:
v
Wizard-guided
installation
process
v
Ability
to
choose
the
type
of
agent
to
install
v
Secure
authentication
and
encryption
v
Work
across
firewalls
v
Centralized
security
mechanism
v
Data
warehousing
v
Job
return
code
mapping
v
Extended
autotrace
feature
v
Enhanced
time
zone
support
v
New
options
for
handling
expired
time
constraints
for
jobs
and
job
streams
v
Event
state
management
Wizard-guided
Installation
Process
An
InstallShield
wizard
is
provided
to
guide
you
in
performing
the
following
installation
procedures:
v
Install
a
new
instance
of
IBM
Tivoli
Workload
Scheduler
v
Upgrade
IBM
Tivoli
Workload
Scheduler
from
previous
versions
v
Add
a
new
feature
to
the
existing
IBM
Tivoli
Workload
Scheduler
installation
v
Promote
an
existing
installation
v
Uninstall
IBM
Tivoli
Workload
Scheduler
The
wizard
is
available
for
only
Tier–1
platforms.
See
Table
3
on
page
10
for
Tier
1
and
Tier
2
supported
platforms.
See
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
for
more
information
about
this
method
of
installation.
Ability
to
Choose
the
Type
of
Agent
to
Install
On
Tier
1
platforms,
you
can
select
the
type
of
agent
to
install
and
only
the
binaries
required
by
that
agent
are
installed.
For
example,
you
can
select
to
install
a
standard
agent,
a
fault-tolerant
agent,
a
master
domain
manager,
or
a
backup
master.
See
the
installation
overview
in
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
©
Copyright
IBM
Corp.
1999,
2004
1
Secure
Authentication
and
Encryption
Security
is
enhanced
for
connections
between
protected
and
non-protected
domains
by
applying
the
authentication
and
encryption
mechanism
based
on
the
Secure
Sockets
Layer
(SSL)
protocol.
SSL
uses
digital
certificates
to
authenticate
the
identity
of
a
workstation.
The
IBM
Tivoli
Workload
Scheduler
administrator
must
plan
how
authentication
will
be
used
within
the
network:
v
Use
one
certificate
for
the
entire
IBM
Tivoli
Workload
Scheduler
network.
v
Use
a
separate
certificate
for
each
domain.
v
Use
a
separate
certificate
for
each
workstation.
SSL
support
is
automatically
installed
with
IBM
Tivoli
Workload
Scheduler,
version
8.2.
To
activate
SSL
support,
the
administrator
must
perform
the
following
actions:
v
Set
up
a
private
key,
a
certificate,
and
a
trusted
Certificate
Authority
(CA)
list.
v
Set
the
SSL
local
options.
v
Add
the
SSL
attributes
to
the
workstation’s
definition
in
the
database.
See
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
for
more
information.
Work
Across
Firewalls
For
previous
versions
of
IBM
Tivoli
Workload
Scheduler,
running
the
commands
to
start
or
stop
a
workstation
or
to
get
the
job
standard
list
requires
opening
a
direct
TCP/IP
connection
between
the
originator
and
the
destination
nodes.
In
a
firewall
environment,
this
forces
users
to
break
the
firewall
to
open
a
direct
communication
path
between
the
master
and
each
fault-tolerant
agent
in
the
network.
Version
8.2
features
a
new
configurable
attribute,
behindfirewall,
in
the
workstation’s
definition
in
the
database.
You
can
set
this
attribute
to
ON
to
indicate
that
a
firewall
exists
between
that
particular
workstation
and
the
IBM
Tivoli
Workload
Scheduler
master,
and
that
the
link
between
the
domain
manager
and
the
workstation
(which
can
be
another
domain
manager
itself)
is
the
only
allowed
link
between
the
respective
domains.
Also,
for
all
the
workstations
having
this
attribute
set
to
ON,
the
commands
to
start
or
stop
the
workstation
or
to
get
the
job
standard
list
will
be
transmitted
through
the
domain
hierarchy
instead
of
opening
a
direct
connection
between
the
master
(or
domain
manager)
and
the
workstation.
See
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
for
more
information.
Centralized
Security
Mechanism
A
new
global
option
makes
it
possible
to
change
the
security
model
in
the
IBM
Tivoli
Workload
Scheduler
network.
If
you
use
this
option,
then
the
security
files
for
the
fault-tolerant
agents
in
the
network
can
be
created
or
modified
only
on
the
master.
The
IBM
Tivoli
Workload
Scheduler
administrator
takes
charge
of
creating,
updating,
and
distributing
the
security
files
for
all
the
agents
where
a
user
access
is
required.
Setting
this
global
option
triggers
a
security
mechanism
to
identify
and
trust
the
IBM
Tivoli
Workload
Scheduler
network
corresponding
to
that
master.
You
can
continue
to
use
the
traditional
security
model
if
you
prefer,
by
using
the
default
setting
of
this
global
option.
See
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
for
more
information.
2
IBM
Tivoli
Workload
Scheduler
Release
Notes
Integration
with
Data
Warehousing
Because
your
environment
contains
many
products
and
services
that
manage
and
monitor
your
IT
enterprise,
storing
this
data,
generating
reports,
and
analyzing
the
data
becomes
a
complex
task.
Tivoli
Enterprise™
Data
Warehouse
allows
you
to
collect
this
data
in
one
place,
a
central
data
warehouse,
and
enables
you
to
construct
an
end-to-end
view
of
your
enterprise
and
view
its
components
independent
of
specific
applications.
IBM
Tivoli
Workload
Scheduler
provides
a
Tivoli
Enterprise
Data
Warehouse
enablement
pack
to
consolidate
scheduling
data
in
the
Tivoli
Enterprise
Data
Warehouse
database.
Locate
the
documentation
for
the
warehouse
enablement
pack
on
the
IBM
Tivoli
Workload
Scheduler
Installation
Disk
2,
in
the
path
tedw_apps_etl/aws/pkg/v820/doc/TivoliWorkloadScheduler8.2_for_TEDW.doc.
Job
Return
Code
Mapping
Formerly,
IBM
Tivoli
Workload
Scheduler
considered
a
job
to
have
executed
successfully
if
it
terminated
with
a
return
code
of
zero,
and
to
have
abended,
if
it
terminated
with
a
return
code
different
than
zero.
You
can
now
define
a
logical
expression
to
represent
which
return
codes
are
to
be
considered
successful.
The
ability
to
define
the
job
as
successful
or
failed
allows
more
flexibility
in
controlling
the
job
execution
flow
depending
on
the
result
of
the
job
execution.
Refer
to
the
IBM
Tivoli
Workload
Scheduler
Reference
Guide
for
more
information.
Extended
Autotrace
Feature
This
is
a
built-in
flight-recorder-style
trace
mechanism
that
logs
all
activities
performed
by
the
IBM
Tivoli
Workload
Scheduler
processes.
In
case
of
product
failure
or
unexpected
behavior,
this
feature
can
be
extremely
effective
in
finding
the
cause
of
the
problem.
In
case
of
problems,
you
are
asked
to
create
a
trace
snap
file
by
issuing
some
simple
commands.
The
trace
snap
file
is
then
inspected
by
the
Tivoli
support
team,
which
uses
the
logged
information
as
an
efficient
problem
determination
base.
The
autotrace
feature,
already
available
with
version
8.1,
has
now
been
extended
to
run
on
additional
platforms.
Refer
to
IBM
Tivoli
Workload
Scheduler
Troubleshooting
and
Error
Messages
for
more
information
about
this
feature.
Enhanced
Time
Zone
Support
This
version
increases
the
granularity
of
the
supported
time
zones.
In
fact,
it
considers
the
fact
that
locations
that
belong
to
the
same
time
zone,
may
nevertheless
follow
different
daylight
savings
timetables.
See
the
appendix
on
time
zones
in
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide.
New
Options
for
Handling
Time
Constraints
Jobs
and
job
streams
are
constrained
by
the
start
times
and
deadlines
specified
for
them,
and
also
by
any
dependencies
they
have
on
the
completion
of
other
jobs
or
job
streams.
A
deadline
specifies
the
time
within
which
a
job
or
job
stream
must
complete.
To
aid
you
in
determining
the
status
of
jobs
and
job
streams,
the
following
enhancements
have
been
implemented:
v
The
status
of
jobs
and
job
streams
that
have
reached
their
deadline
but
have
not
yet
started,
or
have
not
yet
finished
running
are
displayed
by
the
Job
Scheduling
GUI
and
messages
are
logged
to
the
message
log.
Chapter
1.
About
This
Release
3
v
A
message
is
issued
for
jobs
and
job
streams
that
have
reached
the
start
time
specified
for
them,
but
cannot
start
because
of
pending
dependencies
on
other
jobs
or
job
streams.
v
Using
the
Job
Scheduling
Console
or
the
command
line
interface,
queries
enable
you
to
filter
jobs
and
job
streams
for
the
following
information:
–
Jobs
or
job
streams
whose
start
times
have
been
reached,
but
have
not
yet
started
running
–
Jobs
or
job
streams
whose
deadlines
have
been
reached,
but
have
not
yet
started
running
–
Jobs
or
job
streams
whose
deadlines
have
been
reached,
but
have
not
yet
completed
runningv
New
options
enable
you
to
start
jobs
or
job
streams
whose
deadlines
have
been
reached
but
have
not
yet
started.
In
such
cases,
notifications
are
sent
by
issuing
a
message
to
Batchman
and
the
console
log;
and
an
event
is
sent
to
the
Tivoli
Enterprise
Console®
and
the
IBM
Tivoli
Business
Systems
Manager.
Refer
to
the
IBM
Tivoli
Workload
Scheduler
Reference
Guide
for
more
information.
Event
State
Management
In
this
release,
new
Tivoli
Enterprise
Console
events
and
rules
have
been
implemented
related
to
the
new
job
and
job
stream
time
constraint
options.
You
can
define
which
jobs
are
considered
key
jobs
and
have
events
sent
to
the
Tivoli
Enterprise
Console
reporting
not
just
the
final
state,
but
also
intermediate
job
states
of
all
key
jobs.
You
can
also
customize
Tivoli
Enterprise
Console
rules
to
automatically
submit
jobs
when
specific
events
are
received.
Refer
to
the
IBM
Tivoli
Workload
Scheduler
Plus
Module
User’s
Guide
for
information
about
creating
and
customizing
new
Tivoli
Enterprise
Console
rules.
Interoperability
Notes
This
section
contains
information
about
the
interoperability
of
IBM
Tivoli
Workload
Scheduler.
The
term
interoperability
is
defined
as
whether
different
versions
of
IBM
Tivoli
Workload
Scheduler
can
communicate
with
each
other.
IBM
Tivoli
Workload
Scheduler,
Version
8.2
fault-tolerant
agents
and
Extended
Agents
can
coexist
with
IBM
Tivoli
Workload
Scheduler,
Versions
7.0
and
8.1
master
domain
managers.
IBM
Tivoli
Workload
Scheduler,
Versions
7.0
and
8.1
standard
agents
can
coexist
with
IBM
Tivoli
Workload
Scheduler,
Version
8.2
master
domain
managers.
See
Defect
160731
in
the
section
“Software
Problems
and
Workarounds”
on
page
16
for
a
known
interoperability
problem.
Version
8.1
Applications
Extensions
do
not
discover
IBM
Tivoli
Workload
Scheduler
version
8.2
engine
instance.
An
interoperability
problem
exists
between
version
8.1
Applications
Extension
on
an
IBM
Tivoli
Workload
Scheduler,
Version
8.2
engine.
The
version
8.1
Applications
Extension
is
unable
to
detect
an
installation
of
the
IBM
Tivoli
Workload
Scheduler,
Version
8.2
engine.
You
must
install
the
version
8.2
Applications
Extension
to
be
able
to
communicate
with
the
version
8.2
engine.
End-to-end
Environment
In
an
end-to-end
environment,
the
same
interoperability
conditions
exist.
IBM
Tivoli
Workload
Scheduler,
Version
8.2
fault-tolerant
agents
and
Extended
Agents
can
coexist
with
IBM
Tivoli
Workload
Scheduler
for
z/OS,
Version
8.1
IBM
Tivoli
4
IBM
Tivoli
Workload
Scheduler
Release
Notes
Workload
Scheduler,
Versions
7.0
and
8.1
standard
agents
can
coexist
with
IBM
Tivoli
Workload
Scheduler
for
z/OS,
Version
8.2.
Compatibility
Notes
This
section
contains
information
about
the
compatibility
of
IBM
Tivoli
Workload
Scheduler.
The
term
compatibility
is
defined
as
whether
different
versions
of
IBM
Tivoli
Workload
Scheduler
can
communicate
with
different
versions
of
a
base
product.
IBM
Tivoli
Workload
Scheduler,
Version
8.2
is
compatible
with
the
following
Tivoli
Management
Framework
releases:
v
Tivoli
Management
Framework,
Versions
3.7.1,
and
3.7.B
(for
Linux)
v
Tivoli
Management
Framework,
Version
4.1
IBM
Tivoli
Workload
Scheduler,
Version
8.2
is
compatible
with
the
following
products:
v
Tivoli
Enterprise
Console,
Version
3.7.1,
3.8,
via
the
Tivoli
Plus
Module
v
IBM
Tivoli
Business
Systems
Manager,
Version
2.1.1
v
NetView
Version
7.x
for
distributed
platforms
v
Tivoli
Enterprise
Data
Warehouse
Version
1.1
v
Tivoli
Distributed
Monitoring
Version
3.7,
via
the
Tivoli
Plus
Module
Chapter
1.
About
This
Release
5
6
IBM
Tivoli
Workload
Scheduler
Release
Notes
Chapter
2.
Installation
and
Upgrade
Notes
This
chapter
contains
installation
and
upgrade
information
for
IBM
Tivoli
Workload
Scheduler.
Methods
of
installing
and
upgrading
are
described
in
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide.
Topics
in
this
chapter
include:
v
“System
Requirements”
v
“Software
Requirements”
on
page
8
v
“Installation
Notes”
on
page
12
v
“Upgrade
Notes”
on
page
13
System
Requirements
This
section
describes
the
hardware
requirements
for
IBM
Tivoli
Workload
Scheduler
and
includes
information
such
as
machine
types
and
disk
space.
IBM
Tivoli
Workload
Scheduler
consists
of
the
following
components
and
optional
features:
v
Engine,
configured
as
a
master
(MDM),
backup
master
(BKM),
fault-tolerant
agent
(FTA),
or
standard
agent
(SA)
v
Tivoli
Management
Framework
(TMF)
v
Connector
(TWSConn)
v
Tivoli
Plus
Module
(TWSPlus)
v
Language
Packs
(LP)
v
Java™
Virtual
Machine
(JVM)
v
License
agreement
files
(LA)
IBM
Tivoli
Workload
Scheduler
Requirements
The
following
table
summarizes
the
minimum
disk
space
requirements
of
the
binaries
related
to
IBM
Tivoli
Workload
Scheduler
components
and
features
on
supported
Tier
1
platforms.
©
Copyright
IBM
Corp.
1999,
2004
7
See
Table
3
on
page
10
for
a
list
of
Tier
1
platforms.
Table
1.
Disk
space
requirements,
in
megabytes,
for
IBM
Tivoli
Workload
Scheduler
components
and
features
Component/Feature
AIX®
Solaris
HP-UX
Linux
Intel
Linux
OS/390
Windows
MDM
101
79
76
146
75
31
BKM
101
79
76
146
75
31
FTA
66
51
51
48
46
25
SA
62
48
48
40
43
23
TMF
150
150
150
150
150
150
TWSConn
20
20
20
20
20
10
TWSPlus
5
5
5
5
5
5
JVM*
20
20
30
20
20
20
LA*
1
1
1
1
1
1
LP
0.5
0.5
0.5
0.5
0.5
0.5
*The
JVM
and
LA
components
apply
only
to
installations
using
the
ISMP
wizard
and
silent
installation
methods.
Note:
This
table
does
not
include
the
space
required
to
operate
IBM
Tivoli
Workload
Scheduler.
You
must
consider
the
additional
space
required
for
log
files,
temporary
files
that
are
placed
on
the
local
hard
drive,
the
number
of
jobs
managed
by
IBM
Tivoli
Workload
Scheduler,
and
the
period
of
time
you
choose
to
retain
log
files.
The
following
table
summarizes
the
minimum
disk
space
requirements
of
the
binaries
related
to
installing
IBM
Tivoli
Workload
Scheduler
fault-tolerant
agent
(including
language
packs)
on
supported
Tier
2
platforms.
See
Table
3
on
page
10
for
a
list
of
Tier
2
platforms.
Table
2.
Disk
space
requirements
for
fault-tolerant
agent
on
Tier
2
Tier
2
Platform
Disk
space
(MB)
Compaq
Tru64
90
SGI
Irix
61
IBM
Sequent®
Dynix
65
SuSE
Linux
Enterprise
Server
for
iSeries™
and
pSeries™
50
Software
Requirements
This
section
describes
the
software
requirements
for
IBM
Tivoli
Workload
Scheduler
and
includes
information
such
as
supported
operating
systems
and
required
patches.
The
following
table
identifies
the
supported
versions
for
each
of
the
listed
platforms
known
at
the
time
of
publication
and
also
lists
which
components
are
supported
on
which
operating
systems.
8
IBM
Tivoli
Workload
Scheduler
Release
Notes
Platform
Master
FTA
Connector
and
Job
Scheduling
Services
Job
Scheduling
Console
IBM
AIX
Version
4.3.3,
5.1,
5.2
X
X
X
X
HP-UX
Pa-Risc
Version
11.0,
11i
X
X
X
X
Sun
Solaris
Version
7,
8,
9
X
X
X
X
Microsoft®
Windows
NT®
Version
4.0
with
SP6a
X
X
X
X
Microsoft
Windows
2000
Professional,
with
SP3
X
X
Microsoft
Windows
2000
Server,
Advanced
Server,
with
SP3
X
X
X
X
Microsoft
Windows
XP
Professional
with
SP1
X
X
Microsoft
Windows
Terminal
Server
X
Red
Hat
Linux
(Intel)
Version
7.2,
7.3
X
X
X
X
Red
Hat
Linux
for
S/390
(kernel
2.4.9,
31
bit)Version
7
X
X
X
SuSE
Linux
Enterprise
Server
for
zSeries
(kernel
2.4,
64
bits)Version
7
X
SuSE
Linux
Enterprise
Server
for
S/390®
and
zSeries
(kernel
2.4,
31
bits)Version
7
X
X
X
SuSE
Linux
Enterprise
Server
for
x86
Version
8
X
X
X
X
SuSE
Linux
Enterprise
Server
for
iSeries
and
pSeries
(kernel
2.4,
31
bits)
Version
7
X
IBM
OS/400®
Version
5.1,
5.2
X
IBM
Sequent
Dynix
Version
4.5.1,
4.6.1
X
Compaq
Tru64
Version
5.1
(former
OSF
versions)
X
SGI
Irix
Version
6.5.x
X
Chapter
2.
Installation
and
Upgrade
Notes
9
Platform
Master
FTA
Connector
and
Job
Scheduling
Services
Job
Scheduling
Console
Notes:
1.
Fault-tolerant
agents
can
be
defined
as
domain
managers
on
operating
systems
where
the
master
domain
manager
is
supported.
For
example,
a
master
is
not
supported
on
Microsoft
Windows
XP
Pro
and
therefore
a
fault-tolerant
agent
cannot
be
defined
as
a
domain
manager
on
this
operating
system.
2.
Refer
to
the
IBM
Tivoli
Workload
Scheduler
Job
Scheduling
Console
Release
Notes
for
more
information
about
the
Job
Scheduling
Console
supported
platforms
and
requirements.
Installation
Methods
and
Supported
Operating
Systems
The
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
makes
reference
to
Tier
1
and
Tier
2
supported
platforms.
The
installation
method
you
select
depends
on
the
platform
on
which
you
are
installing
the
product.
The
following
table
identifies
the
Tier
1
and
Tier
2
supported
platforms
and
the
installation
methods
supported
by
each
platform.
Table
3.
Installation
methods
and
supported
operating
systems
Platform
Tier
Operating
System
Installation
Method
Tier
1
Red
Hat
Linux
for
Intel
Red
Hat
Linux
for
S/390
Sun
Solaris
HP-UX
AIX
Windows
NT
Windows
2000
Professional,
Server,
Advanced
Server
Windows
XP
Professional
ISMP
and
Silent
Install
Sun
Solaris
HP-UX
AIX
twsinst
script
Red
Hat
Linux
for
Intel
Red
Hat
Linux
for
S/390
Sun
Solaris
HP-UX
AIX
Windows
NT
Windows
2000
Professional,
Server,
Advanced
Server
Windows
XP
Pro
Software
Distribution
10
IBM
Tivoli
Workload
Scheduler
Release
Notes
Table
3.
Installation
methods
and
supported
operating
systems
(continued)
Platform
Tier
Operating
System
Installation
Method
Tier
2
Compaq
Tru64
SGI
Irix
IBM
Sequent
Dynix
SuSE
Linux
Enterprise
Server
for
iSeries
and
pSeries
customize.sh
Installation
Program
Software
Requirements
To
use
the
installation
programs
on
your
computer,
your
operating
system
must
be
able
to
run
Java
Runtime
Environment
(JRE)
Version
1.3.1.
Some
platforms
require
maintenance
levels
to
support
JRE
1.3.1.
Refer
to
the
following
table
for
the
patches
required
by
each
operating
system.
For
supported
platforms
not
included
in
this
table,
no
additional
patches
are
required.
Table
4.
Patches
Required
to
Run
JRE
1.3.1
Operating
System
Patch
Required
to
Run
JRE
1.3.1
IBM
AIX
Version
4.3.3
AIX
4330–10
Recommended
Maintenance
Level.
IBM
AIX
Version
5.1
AIX
5100–02
Recommended
Maintenance
Level.
This
requires
that
APAR
IY19375
be
previously
applied
and
committed.
If
you
are
using
one
of
the
supported
non-UTF8
CKJ
locales,
one
of
the
following
filesets
(available
on
the
AIX
5.1
base
CD)
is
required:
v
X11.fnt.ucs.ttf
(for
ja_JP
or
Ja_JP)
v
X11.fnt.ucs.ttf_CN
(for
zh_CN
or
Zh_CN)
v
X11.fnt.ucs.ttf_KR
(for
ko_KR)
v
X11.fnt.ucs.ttf_TW
(for
zh_TW
or
Zh_TW)
For
Japanese
users:
if
you
are
using
Japanese
Input
Method,
you
may
apply
the
following
PTFs
to
avoid
some
Input
Method-related
problems.
v
jkit.Wnn6.base
2.2.0.2
(PTF
U479697
or
APAR
IY22917)
(Wnn6
user
only)
v
X11.motif.lib
5.1.0.15
(PTF
U479604
or
APAR
IY22933)
(AIX
5.1
user
only)
Solaris
Operating
Environment
Versions
7,
8,
9
Patch
Clusters
dated
January
2002
or
later.
Hewlett
Packard
PA-RISC
Versions
11.0,
11i
Operating
system
patches
should
be
installed
before
you
install
the
product.
To
determine
which
patches
have
been
installed
on
your
computer,
login
as
root
and
run:
/usr/sbin/swlist
-l
product
To
support
JRE
1.3.1.05,
you
should
have:
v
For
HP-UX
11.0,
Quality
Pack
QPK1100
v
For
HP-UX
11i,
Quality
Pack
GOLDQPK11i
Chapter
2.
Installation
and
Upgrade
Notes
11
Installation
Notes
This
section
describes
information
related
to
the
installation
procedure.
See
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
for
detailed
information
about
the
installation
procedure.
The
Installation
CDs
The
following
CDs
are
required
to
start
the
installation
process:
IBM
Tivoli
Workload
Scheduler
Installation
Disk
1
Includes
images
for
AIX,
SOLARIS,
HP-UX,
and
WINDOWS
IBM
Tivoli
Workload
Scheduler
Installation
Disk
2
Includes
images
for
LINUX
and
Tier
2
platforms.
For
Windows
platforms,
the
SETUP.exe
file
is
located
in
the
Windows
folder
on
IBM
Tivoli
Workload
Scheduler
Installation
Disk
1.
On
UNIX
platforms,
there
are
two
different
SETUP.bin
files.
The
first
is
located
in
the
root
directory
of
the
installation
CD,
and
the
second
is
located
in
the
folder
of
the
UNIX
operating
system
on
which
you
are
installing:
Using
the
SETUP.bin
in
the
Root
Directory
You
can
use
this
setup
program
to
run
all
types
of
installations.
It
copies
some
images
to
the
local
file
system
to
allow
unmounting
of
CDs.
It
must
be
run
as
explained
below
and
a
cleanup
procedure
is
required
at
the
end
of
the
installation.
This
setup
program
requires
approximately
the
following
amount
of
disk
space
in
the
temporary
directory:
v
100
MB
for
installing
the
Job
Scheduling
Console.
v
200
MB
for
installing
IBM
Tivoli
Workload
Scheduler.
Before
installing,
make
sure
you
have
this
disk
space
in
addition
to
the
minimum
space
required
to
store
the
product
files.
To
launch
the
installation,
run
the
following
command
from
the
command
line:
./SETUP.bin
[-is:tempdir
<temporary_directory>]
where,
./SETUP.bin
Without
the
optional
parameter
specified,
some
installation
files
and
directories
are
copied
to
the
temporary
directory
set
on
the
local
machine.
Ensure
that
you
manually
delete
the
following
files
and
directories
copied
to
your
temporary
directory
after
the
installation
process
completes:
v
SETUP.jar
v
TWS_size.txt
v
media.inf
v
Tivoli_TWS_LP.SPB
v
RESPONSE_FILE
directory
v
TWS_CONN
directory
v
TWSPLUS
directory
v
the
directory
named
after
the
operating
system
-is:tempdir
<temporary_directory>
This
parameter
is
optional.
You
can
specify
a
temporary
working
directory
12
IBM
Tivoli
Workload
Scheduler
Release
Notes
|||||
|
|
||
different
from
the
temporary
directory
set
on
the
local
machine
by
replacing
the
<temporary_directory>
variable.
Ensure
that
you
delete
the
<temporary_directory>
you
specify
after
the
installation
process
completes.
Using
the
SETUP.bin
in
the
UNIX
Operating
System
Folders
As
an
alternative,
you
can
run
the
installation
using
this
setup
if
you
have
copied
the
installation
images
locally
or
are
installing
from
a
fileserver
and
not
from
the
installation
CD.
Installing
Using
the
twsinst
Script
When
you
run
the
twsinst
script
to
install
IBM
Tivoli
Workload
Scheduler,
output
messages
are
recorded
in
the
/tmp/twsinst.NNNN.log
file,
where,
NNNN
is
the
twsinst
process
number.
This
log
file
can
be
useful
for
problem
determination.
Refer
to
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
for
detailed
information
about
installing
the
product
using
the
twsinst
script.
Upgrade
Notes
This
section
describes
additional
information
related
to
the
upgrade
procedure.
See
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
for
detailed
information
about
the
upgrade
procedure.
You
can
upgrade
a
master
domain
manager,
a
domain
manager,
a
fault-tolerant
agent,
and
a
standard
agent
from
the
IBM
Tivoli
Workload
Scheduler
Version
7.0
and
8.1
to
the
current
8.2
version.
IBM
Tivoli
Workload
Scheduler,
Version
8.2
supports
backward
compatibility
and
you
can,
therefore,
upgrade
your
network
gradually,
at
different
times,
and
in
no
particular
order.
You
can
upgrade
top-down
(that
is,
upgrade
the
master
first,
then
the
domain
managers
and
then
the
fault-tolerant
agents),
as
well
as
upgrade
bottom-up
(that
is,
start
with
the
fault-tolerant
agents
and
then
upgrade
in
sequence
leaving
the
master
last.
However,
if
you
upgrade
the
master
first,
some
new
version
8.2
functions,
(firewall
support,
centralized
security)
will
not
work
until
the
whole
network
is
upgrade.
Note:
Ensure
the
workstation
on
which
you
are
performing
the
upgrade
has
the
latest
patch
level
installed.See
Defect
160731
in
the
section
“Software
Problems
and
Workarounds”
on
page
16
for
a
known
interoperability
problem.
End-to-end
Environment
The
upgrade
path
documented
in
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
is
valid
also
for
an
end-to-end
environment,
provided
that
OPCMASTER
is
the
master
of
the
network.
Chapter
2.
Installation
and
Upgrade
Notes
13
14
IBM
Tivoli
Workload
Scheduler
Release
Notes
Chapter
3.
Product
Limitations,
Problems,
and
Workarounds
This
chapter
contains
product
limitations,
problems,
and
workarounds
for
IBM
Tivoli
Workload
Scheduler,
Version
8.2.
It
includes
the
following
sections:
v
“Software
Limitations”
v
“Software
Problems
and
Workarounds”
on
page
16
v
“Fixed
Defects”
on
page
20
Software
Limitations
The
following
are
software
limitations
that
affect
IBM
Tivoli
Workload
Scheduler,
Version
8.2:
v
A
Full,
Customize,
or
Add
Feature
installation
that
includes
the
installation
of
the
Tivoli
Management
Framework
and
additional
language
packs,
prompts
you
to
provide
the
installation
images
of
first,
the
Tivoli
Management
Framework
server,
and
second,
the
Tivoli
Management
Framework
language
support
which
are
located
on
different
CDs.
If
you
install
the
Tivoli
Management
Framework
server
from
the
CD
(and
not
from
a
fileserver
or
from
images
copied
locally
on
your
machine),
then
you
must
also
install
the
languages
from
CD
and
not
from
any
other
source.
v
On
Windows
supported
platforms,
for
a
new
installation,
if
you
specify
an
existing
user,
a
password
check
is
not
performed
during
the
installation
process,
so
if
an
invalid
password
is
specified,
the
installation
is
erroneously
reported
as
successful,
however,
the
product
does
not
function
properly.
To
correct
the
problem,
set
the
correct
password
for
the
Tivoli
Workload
Scheduler
(for
TWSuser)
and
Tivoli
Netman
(for
TWSuser)
services
in
the
Services
panel.
v
A
known
problem
exists
for
company
names
containing
blank
spaces,
double
quotation
marks,
or
both.
The
installation
methods
sensitive
to
these
characters
are
the
ISMP
installation
program
and
the
twsinst
script.
ISMP
installation
program
A
new
installation
or
upgrade
fails
if
the
company
name
contains
blank
spaces
AND
is
enclosed
in
double
quotation
marks.
For
an
upgrade,
if
your
current
installation
of
IBM
Tivoli
Workload
Scheduler,
version
7.0
or
8.1
specifies
a
company
name
containing
blank
spaces
AND
enclosed
in
double
quotation
marks
(″)
in
the
globalopts
file,
for
example,
"My
Company",
the
upgrade
procedure
will
fail.
Before
performing
the
upgrade
procedure,
edit
the
globalopts
file
located
in
the
path
TWShome/mozart/globalopts,
by
removing
the
double
quotation
marks.
Blank
spaces
are
permitted.
twsinst
script
If
your
current
installation
of
IBM
Tivoli
Workload
Scheduler,
version
7.0
or
8.1
specifies
a
company
name
containing
blank
spaces
in
the
globalopts
file,
the
upgrade
procedure
or
the
promote
of
an
existing
CPU
will
fail.
Before
you
perform
an
upgrade
or
a
promote
of
an
existing
CPU,
ensure
that
the
company
name
does
not
contain
blank
characters.
You
can
verify
the
existence
of
blank
characters
and
remove
them
from
the
company
name
by
modifying
the
related
entry
in
the
TWShome/mozart/globalopts
file.v
On
Windows
supported
platforms,
when
specifying
the
TWSuser,
if
you
specify
a
domain
user,
specify
the
name
as
domain_name\user_name.
If
you
specify
a
©
Copyright
IBM
Corp.
1999,
2004
15
local
user
that
has
the
same
name
as
a
domain
user,
specify
the
name
as
system_name\user_name.
In
this
case,
the
local
user
must
already
be
defined
on
the
Windows
workstation
before
running
the
installation.
If
it
is
not
already
defined,
the
installation
is
unable
to
create
it.
v
On
Windows
supported
platforms,
two
installations
cannot
coexist
on
the
same
workstation
if
they
have
the
same
TWSuser
name
where
one
is
a
local
user
account
and
the
other
is
a
domain
user
account.
v
Due
to
a
known
ISMP
problem,
tracked
with
ID
FSPI5KZDGW,
uninstallation
of
Tivoli
Workload
Scheduler
via
ISMP
on
Windows
2003
does
not
complete.
As
a
workaround
while
the
problem
is
resolved,
you
can
install
JRE
1.41_05
on
your
computer
and
run
the
uninstall.jar
file
directly
from
the
_uninst
directory.
Software
Problems
and
Workarounds
The
following
are
software
problems
and
workarounds
that
affect
IBM
Tivoli
Workload
Scheduler,
Version
8.2.
v
APAR
IX82140:
It
is
impossible
to
install
IBM
Tivoli
Workload
Scheduler
in
directories
that
have
names
containing
spaces.
v
Defect
89937:
Jnextday
shows
errors
when
no
instances
of
the
connector
are
installed
but
the
Tivoli
Framework
is
installed.
Jnextday
still
runs
successfully.
v
Defect
90218:
You
may
receive
the
following
misleading
message
if
you
perform
a
MAKESEC
command
while
another
user
uses
CLI
COMPOSER:
MAKESEC:AWS11140308I
Error
renaming
MAKESEC:c:\win32app\maestro/../unison/Security.temp
to
MAKESEC:c:\win32app\maestro/../unison/Security:
File
exists
The
same
message
may
also
be
issued
if
you
perform
a
MAKESEC
command
while
the
connector
is
running.
To
avoid
getting
this
message,
close
all
connector
instances
by
using
WMAEUTIL.
See
the
IBM
Tivoli
Workload
Scheduler
Reference
Guide,
Version
8.2.
v
Defect
91096:
You
will
receive
the
following
message
when
you
use
the
conman
display
job
if
the
database
is
not
present
on
the
FTA:
WS22020072
No
qualified
entries.
v
Defect
92861:
A
job
stream
with
autodoc
jobs
should
display
the
correct
task
type
unless
the
cpu
is
missing
and
it
should
have
task
type
information
based
on
the
autodoc
information.
Currently,
if
you
remove
an
autodoc
job
from
the
jobs
database,
it
is
displayed
as
unknown
task
type.
Also,
if
two
job
streams
contain
the
same
autodoc
job,
as
a
command
in
one,
and
as
a
script
in
the
other,
the
Job
Scheduling
Console
displays
incorrect
task
type
for
at
least
one
of
them.
If
you
save
the
job
stream
with
incorrect
task
type
the
command
will
change
to
script
or
vice-versa.
v
Defect
93759:
You
may
receive
incorrect
status
information
when
you
issue
the
stop
command
for
all
FTAs
in
a
domain
instance.
The
MDM
is
stopped
before
the
FTAs.
Therefore,
the
MDM
displays
the
available
information
at
the
time
it
stops,
regardless
of
changes
in
the
FTA
status.
v
Defect
94279:
During
the
spring
daylight
savings
time
change
(01:59:59–03:00:00),
UNIX
and
Windows
platforms
behave
differently.
For
example:
–
on
Windows
supported
platforms:
conman
submit
job
at=02xx
is
set
to
01xx
–
on
HP-UX:
conman
submit
job
at=02xx
is
set
to
03xxv
Defect
94701:
If
composer
is
unable
to
retrieve
the
maestro
user
password
entry
information
from
UNIX,
it
performs
a
core
dump
instead
of
issuing
an
error
message.
This
is
due
to
DNS/NIS
configuration
problems.
16
IBM
Tivoli
Workload
Scheduler
Release
Notes
||||
v
Defect
112282:
When
there
is
no
Symphony
file
on
the
engine,
the
connector
shows
as
inactive
(black
cross)
on
the
Job
Scheduling
Console
and
issues
the
following
an
error
message:
GJS087E:
Selected
engine
not
available
Explanation:
Unable
to
initialize
TWS
Connector
plan
auditing
v
Defect
114905:
Add
a
new
job
definition
in
the
command
line
interface
using
the
COMPOSER
NEW
or
the
COMPOSER
ADD
MYFILE
commands
(where
MYFILE
is
the
file
in
which
the
new
job
is
defined).
If
the
name
of
the
new
job
already
exists,
the
job
definition
is
replaced
without
confirmation.
v
Defect
117187:
It
is
not
possible
to
sequentially
submit
two
job
streams
with
the
same
alias.
Although
no
error
message
is
issued,
the
second
job
fails
to
be
submitted.
An
error
message
is
displayed
only
if
you
submit
the
second
job
after
the
plan
has
been
updated.
v
Defect
118505:
On
Windows
supported
platforms,
if
you
launch
Visual
Basic
programs
that
end
in
error,
IBM
Tivoli
Workload
Scheduler
does
not
show
the
ABEND
status.
You
need
to
add
an
errorlevel
check
such
as
the
following
at
the
end
of
file
jobmanrc.cmd:
call
%ARGS%
REM
Add
errorlevel
check
to
handle
abends
properly
if
errorlevel
1
exit
:out
IBM
Tivoli
Workload
Scheduler
then
abends
the
job
for
anything
which
exits
not
zero.
v
Defect
119489:
The
following
example
of
a
new
job
stream
definition
shows
a
known
problem
in
specifying
the
workstation
for
a
job
in
the
follows
keyword:
SCHEDULE
MASTER#SCHED1
on
workdays
:
CPU1#JOB1
CPU2#JOB2
follows
CPU1#JOB1
end
In
order
to
save
this
definition,
you
must
write
CPU2#JOB2
follows
JOB1
and
not
CPU2#JOB2
follows
CPU1#JOB1
v
Defect
122169:
On
Windows
supported
platforms,
if
you
specify
an
installation
directory
name
that
includes
blank
spaces,
the
installation
process
does
not
complete.
You
are
then
required
to
manually
remove
the
failed
installation
from
the
registry.
v
Defect
122315:
This
defect
applies
to
Tivoli
Workload
Scheduler
8.1
networks
where
both
feature
levels
1.1
and
1.2
of
the
Job
Scheduling
Console
are
being
run.
If
you
modify
a
job
stream
in
the
database
from
the
Job
Scheduling
Console
1.2
(which
uses
the
new
run
cycle
feature),
you
will
no
longer
be
able
to
open
that
job
stream
from
the
Job
Scheduling
Console
1.1.
v
Defect
124441:
On
the
Tivoli
Plus
Module
Versions
7.0
and
8.1,
the
monitored
resource
’Host
Status’
cannot
be
found
in
the
TWS
Central
Monitors
collection.
v
The
CONMAN
KILL
JOBSELECT
command
does
not
work
if
the
job
is
defined
on
an
Extended
Agent.
The
job
does
show
in
the
ABEND
status,
but
the
associated
process
is
not
killed.
Chapter
3.
Product
Limitations,
Problems,
and
Workarounds
17
v
Defect
124817:
On
UNIX,
if
the
StartUp
command
has
been
issued
by
the
root
user
and
it
is
later
called
by
the
maestro
user,
a
message
similar
to
the
following
may
be
issued:
The
file
access
permissions
do
not
allow
the
specified
action.
/usr/tws1/maestro/trace/init_trace[22]:/usr/tws1/maestro/trace/ffdc:
0403-005
Cannot
create
the
specified
file.
This
has
no
consequences
on
system
startup.
To
avoid
receiving
this
message,
issue
the
StartUp
command
as
maestro
user.
v
Defect
152313:
CONSOLE
command
does
not
work
on
Windows
NT/2000.
The
CONSOLE
command
does
not
work
on
Windows
2000
and
Windows
NT.
v
Defect
153530:
When
performing
IBM
Tivoli
Workload
Scheduler
operations,
temporary
files
are
written
to
the
temporary
directory
set
on
the
local
machine.
WORKAROUND:
Ensure
that
the
TWSuser
performing
operations
has
read/write
access
to
this
directory.
v
Defect
155385:
Version
8.1
Applications
Extensions
do
not
discover
IBM
Tivoli
Workload
Scheduler
version
8.2
instance.
An
interoperability
problem
exists
between
version
8.1
Applications
Extensions
on
an
IBM
Tivoli
Workload
Scheduler,
Version
8.2
engine.
The
Version
8.1
Application
Extension
is
unable
to
detect
an
installation
of
the
IBM
Tivoli
Workload
Scheduler,
Version
8.2
engine.
You
must
install
the
version
8.2
Application
Extension
to
be
able
to
communicate
with
the
version
8.2
engine.
v
Defect
156829:
Submitted
jobs
disappear
in
plan.
When
you
submit
a
large
number
of
jobs,
the
submitted
jobs
may
require
some
time
before
they
are
displayed
in
the
plan.
v
Defect
157536:
Components
file
is
not
located
in
/usr/unison/path.
If
Tivoli
Workload
Scheduler,
Version
8.1
was
installed
using
the
UNISON_COMPONENT_FILE
variable,
and
the
installation
was
not
performed
in
the
default
installation
path,
the
installation
program
for
IBM
Tivoli
Workload
Scheduler
version
8.2
does
not
discover
the
installed
product.
WORKAROUND:
Copy
the
components
file
to
the
/usr/unison
folder.
The
upgrade
process
is
successful,
but
the
components
file
is
not
updated,
therefore,
if
you
subsequently
run
the
installation
program,
it
discovers
the
IBM
Tivoli
Workload
Scheduler
version
8.1
instance
instead
of
the
IBM
Tivoli
Workload
Scheduler
version
8.2
instance.
v
Defect
157942:
Problem
running
link
of
fault-tolerant
agent
from
master.
Link
or
unlink,
and
start
and
stop
commands
issued
from
a
master
domain
manager
or
domain
manager
towards
a
fault-tolerant
agent
connected
to
a
subordinate
domain
manager
are
not
supported.
v
Defect
159230:
TOS
error
occurred
with
Windows
2000
and
NT
fault-tolerant
agents.
In
case
a
TOS
error
is
logged
in
the
fault-tolerant
agent
log,
perform
the
following
steps:
1.
Stop
the
fault-tolerant
agent.
2.
Open
the
$user_maestro/TWSCCLog.properties
file
in
a
text
editor.
3.
Change
the
entry
twsHnd.logFile.className=ccg_multiproc_filehandler
to
read
twsHnd.logFile.className=ccg_filehandler.
This
setting
disables
synchronous
access
to
the
log
file.
Note:
This
problem
has
been
fixed
in
8.2-TWS-Fixpack
02.
v
Defect
159342:
Incorrect
linefeed
in
the
messages
containing
″\n″.
Carriage
returns
are
inserted
in
error
in
the
log
files
whenever
a
″\n″
occurs
causing
directory
names
to
be
broken.
For
example″
\network″
reads
″etwork″.
18
IBM
Tivoli
Workload
Scheduler
Release
Notes
|
v
Defect
159757:
Switchmgr
has
no
effect
if
backup
was
not
started
in
a
TWS
environment.
To
execute
the
switchmgr
command,
start
the
netman
process
for
the
backup
domain
manager
in
an
environment
set
as
follows:
PATH=$PATH:TWSHOME
DIR:TWSHOME
DIR/bin
Note:
This
problem
has
been
fixed
in
8.2-TWS-Fixpack
01.
v
Defect
159782:
Incorrect
error
messages
when
actions
are
not
permitted
on
a
job.
For
example,
if
the
user
tries
to
perform
an
unauthorized
operation
on
an
object,
the
wrong
error
message
is
displayed.
If
the
user
tries
to
add
a
job
in
the
database,
an
error
message
is
displayed
even
if
the
user
is
authorized
to
perform
the
operation,
but
the
operation
is
correctly
performed.
Note:
This
problem
has
been
fixed
in
8.2-TWS-Fixpack
01.
v
Defect
159791:
Display
access
to
prompt,
parms,
resource
in
the
security
file.
The
settings
defined
in
the
security
file
for
DISPLAY
access
to
prompts,
parameters
and
resources
do
not
prevent
higher-level
operations
on
the
specified
objects.
For
example,
when
the
user
tries
to
create
prompts,
parameters,
or
resources,
the
operation
is
performed
even
though
the
DISPLAY
access
is
not
granted.
A
wrong
error
message
is
displayed
when
you
try
to
create
a
prompt,
but
the
prompt
is
created.
Note:
This
problem
has
been
fixed
in
8.2-TWS-Fixpack
01.
v
Defect
159849:
Using
NetView
receive
error
message
for
tws
command.
Using
NetView,
an
error
occurs
when
using
the
command
line.
v
Defect
159954:
User
name
and
password
fields
during
migration
using
ISMP
installation
program.
When
performing
an
upgrade
on
Windows
operating
systems
using
the
installation
program,
the
user
name
and
password
fields
for
the
IBM
Tivoli
Workload
Scheduler
user
for
which
the
product
is
being
upgraded
are
editable,
while
they
should
be
read-only.
v
Defect
160126:
Misleading
information
running
conman
on
a
standard
agent.
When
running
conman
on
a
standard
agent,
information
on
Batchman
is
returned
in
error,
as
this
service
is
not
installed
on
standard
agents.
v
Defect
160128:
Elapsed
time
displayed
with
negative
values.
When
running
conman
ss
the
results
displayed
in
the
Elapsed
time
column
might
be
incorrect.
Note:
This
problem
has
been
fixed
in
8.2-TWS-Fixpack
01.
v
Defect
160136:
Promote
of
an
engine
installed
in
a
directory
different
from
the
″$HOME
dir″.
When
promoting
an
agent,
you
must
specify
the
installation
directory
if
the
agent
was
not
installed
in
the
default
directory.
v
Defect
160688:
Default
value
of
adapter.working.dir
in
TBSM
adapter.config
file
should
be
customizable.
The
default
value
of
adapter.working.dir
is
a
dot
character
(.).
In
this
case,
the
clagent
cannot
start
and
you
receive
the
following
message:
CLAGENT:*
AWSBJB008E
Adapter
Error
:
Unable
to
create
a
transport
WORKAROUND:
Change
the
default
value
of
adapter.working.dir
to
an
absolute
or
relative
path
to
which
the
TWSuser
has
write
access.
v
Defect
160731:
FTA
(7.0->8.2,
Win2k)
cannot
connect
to
MDM
(7.0,
AIX).
When
you
upgrade
a
version
7.0
fault-tolerant
agent
on
Windows
platforms
to
version
8.2,
the
upgraded
fault-tolerant
agent
cannot
connect
to
a
version
7.0
master
domain
manager
on
AIX.
The
problem
is
due
to
a
defect
on
the
version
7.0
Chapter
3.
Product
Limitations,
Problems,
and
Workarounds
19
|
|
|
|
master
domain
manager
that
has
been
fixed
with
APAR
IY44864.
APAR
IY44864
is
a
prerequisite
before
performing
a
bottom-up
migration
for
Tivoli
Workload
Scheduler
7.0.
v
Defect
160764:
Unable
to
unmount
the
CD-ROM
on
UNIX.
After
you
install
from
the
installation
CD
using
the
twsinst
script,
you
are
unable
to
unmount
the
CD.
WORKAROUND:
End
the
netman
process
which
automatically
starts
up
after
the
installation,
and
then
unmount
the
CD.
Alternatively,
copy
the
contents
of
the
CD
to
a
temporary
directory,
and
run
the
installation.
v
Defect
160781:
The
value
of
THIS_CPU
parameter
in
the
software
package
block
must
not
contain
spaces,
however,
the
default
value
is
erroneously
THIS
CPU,
which
contains
a
space.
v
Defect
160860:
A
known
problem
documented
by
Tivoli
Enterprise
Console,
APAR
IY34596,
the
Tivoli
Enterprise
Console
Adapter
may
crash
on
Windows
platforms
when
receiving
an
event
from
IBM
Tivoli
Workload
Scheduler.
Please
refer
to
Tivoli
Enterprise
Console
support
for
receiving
the
Fixpack
that
includes
IY34596.
v
Defect
160930:
Batchman
goes
down
if
you
list
more
than
43
events.
Batchman
goes
down
if
you
list
more
than
43
events
in
the
EVENTS
parameter
within
the
BmEvents.conf
file.
v
The
following
compatibility
problem
may
occur
when
an
FTA
running
version
8.1
has
direct
access
to
the
database
of
a
master
that
runs
version
7.0.
If
you
update
database
objects
from
the
FTA
by
using
new
features
of
version
8.1,
the
master
will
not
be
able
to
apply
those
updates.
Fixed
Defects
All
APARs
and
defects
reported
in
Fixpack
5,
PTF
Number:
U485968,
in
addition
to
the
following
list
of
APARs
and
defects,
have
been
integrated
into
this
release:
v
IY32436
(
defect
153045)
The
state
for
jobs
running
at
jnextday
is
not
updated
correctly.
This
results
in
loss
of
jobs
at
jnextday.
v
IY35182
Follows
on
a
schedule
at
schedule
level
does
not
hold
after
jnextday.
v
IY36118
FTAs
do
not
link
to
master
after
jnextday,
because
of
corruption
in
the
compressed
sinfonia
file
from
master.
v
IY36608
JOBMON
stops
responding
on
TWS
8.1.
v
IY37705
CPU
LIMIT=0
not
honored
on
xa.
v
IY38726
Cannot
browse
joblog
on
dynix
fta
via
jsc
or
command
line
after
applying
8-1-TWS-0006.
v
IY38717
Bacthman
abend
on
master
due
to
jobtable
exceeds
32000.
v
IY38732
On
Linux
TWS
connector
error
to
submit
job
with
parms.
v
IY38795
Batchman
crashes
when
crossing
the
barrier
of
65535
records.
v
IY38683
Some
characters
are
garbled
when
viewing
job
stdlist
files.
v
IY39396
Conman
sj
gives
bad
output
after
efix
for
IY38795.
v
IY39399
Conman
switchmgr
does
not
work
on
win2k
when
mailman
servers
are
used.
v
IY41986
TWS
performance
is
adversely
affected
when
more
than
65535
jobs.
v
IY42018
KILL
command
can
corrupt
a
message
queue.
v
IY44102
Stageman
tries
to
use
a
record
number
(32768)
in
Symphony
file
v
IY34857
(con
defect
155158)
Cancelled
schedule
carried
forward
if
using
non-expanded
databases
and
flagged
as
carry
forward.
v
Defect
155375
Composer
coredump
when
trying
to
disp
or
del
a
schedule.
20
IBM
Tivoli
Workload
Scheduler
Release
Notes
v
Defect
94789
Recovery
jobs
that
run
on
a
workstation
other
than
that
of
the
original
job
are
not
launched
if
the
recovery
job
workstation
is
a
not
a
full-status
FTA.
Chapter
3.
Product
Limitations,
Problems,
and
Workarounds
21
22
IBM
Tivoli
Workload
Scheduler
Release
Notes
Chapter
4.
Internationalization
Notes
This
chapter
describes
specific
requirements,
notes,
limitation,
problems,
defects,
and
corrections
for
the
international
versions
of
IBM
Tivoli
Workload
Scheduler,
Version
8.2.
Enabling
Language
Support
Refer
to
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
for
information
about
enabling
language
support.
Software
Limitations,
Problems
and
Workarounds
This
section
describes
software
limitations,
problems,
and
workarounds
for
international
versions
of
IBM
Tivoli
Workload
Scheduler,
Version
8.2.
v
Defect
93843:
The
length
limitation
of
name/prompt
in
Japanese
is
shorter
than
in
English.
In
messages
and
helps,
the
maximum
length
of
name/prompt
is
described
as
16
ASCII
characters,
but
in
Japanese,
the
maximum
length
is
only
5
characters.
The
following
are
the
English
and
double-byte
character
set
(DBCS)
length
limitations
for
names:
Scheduling
Object
English
limit
(ascii
characters)
DBCS
limit
(DBCS
characters)
cpu
name
16
5
domain
name
16
5
cpuclass
name
16
5
schedule
name
16
5
job
name
40
13
parm
name
8
2
prompt
name
8
2
prompt
size
200
66
resource
name
8
2
calendar
name
8
2
JCL
file
name
4095
1365
file
basename
28
9
file
equation
120
40
v
Defect
123119:
The
installation
program
stops
if
you
specify
a
directory
name
that
contains
non-ANSI
characters.
v
Defect
123602:
On
the
Japanese
version
on
Linux,
not
all
the
objects
that
are
actually
defined
are
listed
by
composer.
v
Defect
123608:
You
cannot
submit
a
job
file
of
Japanese
file
name
by
the
CONMAN
SBF
command.
The
problematic
Japanese
file
name
includes
0x5c
code
as
the
second
byte.
If
you
specify
the
file
name
to
include
0x5c
code
as
a
command
parameter
of
CONMAN
SBF,
conman
returns
the
following
error:
AWS22020071
No
qualified
entries
©
Copyright
IBM
Corp.
1999,
2004
23
Other
Japanese
names
not
including
0x5c
code
encounter
no
problems.
v
Defect
123653:
On
Windows
supported
platforms,
it
is
not
possible
to
create
a
calendar
with
a
name
in
Japanese
with
the
MAKECAL
command.
v
Defect
124195:
On
both
Windows
and
UNIX
platforms,
echoed
messages
include
corrupted
Japanese
when
issued
CLI
includes
Japanese
as
the
parameter.
This
is
just
an
appearance
problem,
so
the
commands
are
submitted
correctly
and
are
displayed
correctly
on
the
Job
Scheduling
Console.
v
Defect
159660:
DIVT:
ISMP:
Some
Japanese
characters
are
not
displayed
correctly
on
HP-UX.
On
HP-UX,
some
Japanese
characters
in
the
installation
program
are
garbled.
v
On
UNIX,
you
must
set
the
LANG
variable
in
the
.profile
(for
ksh)
or
applicable
file
for
other
shells.
v
You
must
set
the
LANG
variable
in
jobmanrc
for
batchman
to
use
the
configuration
in
the
language
catalogs.
By
default,
if
the
date
format
is
changed
and
LANG
is
not
set,
the
catalog
is
C
and
reports
default
to
mm/dd/yy
format.
v
For
double-byte
languages
on
Windows
supported
platforms,
you
must
use
Notepad
as
the
editor.
Specify
editor
in
the
Variable
field
of
the
System
Properties
dialog
box
and
specify
notepad
in
the
Value
field.
v
For
western
European
languages,
you
must
set
the
code
page
and
change
the
font
to
Lucida
before
executing
the
Tivoli
Workload
Scheduler
CLI.
The
command
is
chcp
1252.
This
is
documented
in
the
Tivoli
Framework
release
notes
as
a
known
problem
of
Microsoft
Windows.
v
To
view
extended
characters
in
any
editor
or
DOS
window,
you
must
set
the
TWS_TISDIR
environment
variable.
You
can
use
the
TWShome
path.
v
You
must
set
MAESTRO_OUTPUT_STYLE=LONG
to
see
all
of
the
extended
character
set
in
the
CLI.
For
example,
if
the
job
stream
name
is
three
Chinese
characters,
the
total
is
nine
bytes.
The
job
stream
field
in
the
conman
SHOWJOB
command
is
eight
characters,
and
the
third
character
appears
corrupted.
v
All
information
is
stored
and
passed
as
UTF8.
For
Asian
languages,
each
character
is
three
bytes
long.
The
e
accent,
a
accent,
etc.
characters
in
the
European
languages
are
two
bytes
long.
Keep
this
in
mind
when
planning
object
names.
v
On
Windows
and
UNIX
platforms,
you
must
set
the
TWS_TISDIR
environment
variable
manually
before
you
run
a
command.
Refer
to
the
IBM
Tivoli
Workload
Scheduler
Planning
and
Installation
Guide
for
details.
24
IBM
Tivoli
Workload
Scheduler
Release
Notes
Notices
This
information
was
developed
for
products
and
services
offered
in
the
U.S.A.
IBM
may
not
offer
the
products,
services,
or
features
discussed
in
this
document
in
other
countries.
Consult
your
local
IBM
representative
for
information
on
the
products
and
services
currently
available
in
your
area.
Any
reference
to
an
IBM
product,
program,
or
service
is
not
intended
to
state
or
imply
that
only
that
IBM
product,
program,
or
service
may
be
used.
Any
functionally
equivalent
product,
program,
or
service
that
does
not
infringe
any
IBM
intellectual
property
right
may
be
used
instead.
However,
it
is
the
user’s
responsibility
to
evaluate
and
verify
the
operation
of
any
non-IBM
product,
program,
or
service.
IBM
may
have
patents
or
pending
patent
applications
covering
subject
matter
described
in
this
document.
The
furnishing
of
this
document
does
not
give
you
any
license
to
these
patents.You
can
send
license
inquiries,
in
writing,
to:
IBM
Director
of
Licensing
IBM
Corporation
North
Castle
Drive
Armonk,
NY
10504-1785
U.S.A.
For
license
inquiries
regarding
double-byte
(DBCS)
information,
contact
the
IBM
Intellectual
Property
Department
in
your
country
or
send
inquiries,
in
writing,
to:
IBM
World
Trade
Asia
Corporation
Licensing
2-31
Roppongi
3-chome,
Minato-ku
Tokyo
106,
Japan
The
following
paragraph
does
not
apply
to
the
United
Kingdom
or
any
other
country
where
such
provisions
are
inconsistent
with
local
law:
INTERNATIONAL
BUSINESS
MACHINES
CORPORATION
PROVIDES
THIS
PUBLICATION
″AS
IS″
WITHOUT
WARRANTY
OF
ANY
KIND,
EITHER
EXPRESS
OR
IMPLIED,
INCLUDING,
BUT
NOT
LIMITED
TO,
THE
IMPLIED
WARRANTIES
OF
NON-INFRINGEMENT,
MERCHANTABILITY
OR
FITNESS
FOR
A
PARTICULAR
PURPOSE.
Some
states
do
not
allow
disclaimer
of
express
or
implied
warranties
in
certain
transactions,
therefore,
this
statement
might
not
apply
to
you.
This
information
could
include
technical
inaccuracies
or
typographical
errors.
Changes
are
periodically
made
to
the
information
herein;
these
changes
will
be
incorporated
in
new
editions
of
the
publication.
IBM
may
make
improvements
and/or
changes
in
the
product(s)
and/or
the
program(s)
described
in
this
publication
at
any
time
without
notice.
Any
references
in
this
information
to
non-IBM
Web
sites
are
provided
for
convenience
only
and
do
not
in
any
manner
serve
as
an
endorsement
of
those
Web
sites.
The
materials
at
those
Web
sites
are
not
part
of
the
materials
for
this
IBM
product
and
use
of
those
Web
sites
is
at
your
own
risk.
©
Copyright
IBM
Corp.
1999,
2004
25
IBM
may
use
or
distribute
any
of
the
information
you
supply
in
any
way
it
believes
appropriate
without
incurring
any
obligation
to
you.
Licensees
of
this
program
who
wish
to
have
information
about
it
for
the
purpose
of
enabling:
(i)
the
exchange
of
information
between
independently
created
programs
and
other
programs
(including
this
one)
and
(ii)
the
mutual
use
of
the
information
which
has
been
exchanged,
should
contact:
IBM
Corporation
2Z4A/10111400
Burnet
Road
Austin,
TX
78758
U.S.A.
Such
information
may
be
available,
subject
to
appropriate
terms
and
conditions,
including
in
some
cases
payment
of
a
fee.
The
licensed
program
described
in
this
document
and
all
licensed
material
available
for
it
are
provided
by
IBM
under
terms
of
the
IBM
Customer
Agreement,
IBM
International
Program
License
Agreement
or
any
equivalent
agreement
between
us.
This
information
contains
examples
of
data
and
reports
used
in
daily
business
operations.
To
illustrate
them
as
completely
as
possible,
the
examples
include
the
names
of
individuals,
companies,
brands,
and
products.
All
of
these
names
are
fictitious
and
any
similarity
to
the
names
and
addresses
used
by
an
actual
business
enterprise
is
entirely
coincidental.
If
you
are
viewing
this
information
in
softcopy
form,
the
photographs
and
color
illustrations
might
not
appear.
Open
Source:
Test
Copyright
(c)
1992,
1993,
1994
The
Regents
of
the
University
of
California.
All
rights
reserved.
This
code
is
derived
from
software
contributed
to
Berkeley
by
Kenneth
Almquist.
Redistribution
and
use
in
source
and
binary
forms,
with
or
without
modification,
are
permitted
provided
that
the
following
conditions
are
met:
1.
Redistributions
of
source
code
must
retain
the
above
copyright
notice,
this
list
of
conditions
and
the
following
disclaimer.
2.
Redistributions
in
binary
form
must
reproduce
the
above
copyright
notice,
this
list
of
conditions
and
the
following
disclaimer
in
the
documentation
and/or
other
materials
provided
with
the
distribution.
3.
All
advertising
materials
mentioning
features
or
use
of
this
software
must
display
the
following
acknowledgement:
This
product
includes
software
developed
by
the
University
of
California,
Berkeley
and
its
contributors.
4.
Neither
the
name
of
the
University
nor
the
names
of
its
contributors
may
be
used
to
endorse
or
promote
products
derived
from
this
software
without
specific
prior
written
permission.
THIS
SOFTWARE
IS
PROVIDED
BY
THE
REGENTS
AND
CONTRIBUTORS
``AS
IS’’
AND
ANY
EXPRESS
OR
IMPLIED
WARRANTIES,
INCLUDING,
BUT
NOT
LIMITED
TO,
THE
IMPLIED
WARRANTIES
OF
MERCHANTABILITY
AND
26
IBM
Tivoli
Workload
Scheduler
Release
Notes
FITNESS
FOR
A
PARTICULAR
PURPOSE
ARE
DISCLAIMED.
IN
NO
EVENT
SHALL
THE
REGENTS
OR
CONTRIBUTORS
BE
LIABLE
FOR
ANY
DIRECT,
INDIRECT,
INCIDENTAL,
SPECIAL,
EXEMPLARY,
OR
CONSEQUENTIAL
DAMAGES
(INCLUDING,
BUT
NOT
LIMITED
TO,
PROCUREMENT
OF
SUBSTITUTE
GOODS
OR
SERVICES;
LOSS
OF
USE,
DATA,
OR
PROFITS;
OR
BUSINESS
INTERRUPTION)
HOWEVER
CAUSED
AND
ON
ANY
THEORY
OF
LIABILITY,
WHETHER
IN
CONTRACT,
STRICT
LIABILITY,
OR
TORT
(INCLUDING
NEGLIGENCE
OR
OTHERWISE)
ARISING
IN
ANY
WAY
OUT
OF
THE
USE
OF
THIS
SOFTWARE,
EVEN
IF
ADVISED
OF
THE
POSSIBILITY
OF
SUCH
DAMAGE.
Open
Source:
OpenSSL
This
product
includes
software
developed
by
the
OpenSSL
Project
for
use
in
the
OpenSSL
Toolkit.
(http://www.openssl.org/)
LICENSE
ISSUES
The
OpenSSL
toolkit
stays
under
a
dual
license,
i.e.
both
the
conditions
of
the
OpenSSL
License
and
the
original
SSLeay
license
apply
to
the
toolkit.
See
below
for
the
actual
license
texts.
Actually
both
licenses
are
BSD-styleOpen
Source
licenses.
In
case
of
any
license
issues
related
to
OpenSSL
please
contact
OpenSSL
License
Copyright
(c)
1998-2001
The
OpenSSL
Project.
All
rights
reserved.
Redistribution
and
use
in
source
and
binary
forms,
with
or
without
modification,
are
permitted
provided
that
the
following
conditions
are
met:
1.
Redistributions
of
source
code
must
retain
the
above
copyright
notice,
this
list
of
conditions
and
the
following
disclaimer.
2.
Redistributions
in
binary
form
must
reproduce
the
above
copyright
notice,
this
list
of
conditions
and
the
following
disclaimer
in
the
documentation
and/or
other
materials
provided
with
the
distribution.
3.
All
advertising
materials
mentioning
features
or
use
of
this
software
must
display
the
following
acknowledgment:
″This
product
includes
software
developed
by
the
OpenSSL
Project
for
use
in
the
OpenSSL
Toolkit.
(http://www.openssl.org/)″.
4.
The
names
″OpenSSL
Toolkit″
and
″OpenSSL
Project″
must
not
be
used
to
endorse
or
promote
products
derived
from
this
software
without
prior
written
permission.
For
written
permission,
please
contact
5.
Products
derived
from
this
software
may
not
be
called
″OpenSSL″
nor
may
″OpenSSL″
appear
in
their
names
without
prior
written
permission
of
the
OpenSSL
Project.
6.
Redistributions
of
any
form
whatsoever
must
retain
the
following
acknowledgment:
″This
product
includes
software
developed
by
the
OpenSSL
Project
for
use
in
the
OpenSSL
Toolkit
(http://www.openssl.org/)″
THIS
SOFTWARE
IS
PROVIDED
BY
THE
OpenSSL
PROJECT
``AS
IS’’
AND
ANY
EXPRESSED
OR
IMPLIED
WARRANTIES,
INCLUDING,
BUT
NOT
LIMITED
TO,
THE
IMPLIED
WARRANTIES
OF
MERCHANTABILITY
AND
FITNESS
FOR
A
PARTICULAR
PURPOSE
ARE
DISCLAIMED.
IN
NO
EVENT
SHALL
THE
OpenSSL
PROJECT
OR
ITS
CONTRIBUTORS
BE
LIABLE
FOR
ANY
DIRECT,
INDIRECT,
INCIDENTAL,
SPECIAL,
EXEMPLARY,
OR
CONSEQUENTIAL
Notices
27
DAMAGES
(INCLUDING,
BUT
NOT
LIMITED
TO,
PROCUREMENT
OF
SUBSTITUTE
GOODS
OR
SERVICES;
LOSS
OF
USE,
DATA,
OR
PROFITS;
OR
BUSINESS
INTERRUPTION)
HOWEVER
CAUSED
AND
ON
ANY
THEORY
OF
LIABILITY,
WHETHER
IN
CONTRACT,
STRICT
LIABILITY,
OR
TORT
(INCLUDING
NEGLIGENCE
OR
OTHERWISE)
ARISING
IN
ANY
WAY
OUT
OF
THE
USE
OF
THIS
SOFTWARE,
EVEN
IF
ADVISED
OF
THE
POSSIBILITY
OF
SUCH
DAMAGE.
This
product
includes
cryptographic
software
written
by
Eric
Young
This
product
includes
software
written
by
Tim
Hudson
Original
SSLeay
License
Copyright
(C)
1995-1998
Eric
Young
All
rights
reserved.
This
package
is
an
SSL
implementation
written
by
Eric
Young
The
implementation
was
written
so
as
to
conform
with
Netscape
SSL.
This
library
is
free
for
commercial
and
non-commercial
use
as
long
as
the
following
conditions
are
adhered
to.
The
following
conditions
apply
to
all
code
found
in
this
distribution,
be
it
the
RC4,
RSA,
lhash,
DES,
etc.,
code;
not
just
the
SSL
code.
The
SSL
documentation
included
with
this
distribution
is
covered
by
the
same
copyright
terms
except
that
the
holder
is
Tim
Hudson
Copyright
remains
Eric
Young’s,
and
as
such
any
Copyright
notices
in
the
code
are
not
to
be
removed.
If
this
package
is
used
in
a
product,
Eric
Young
should
be
given
attribution
as
the
author
of
the
parts
of
the
library
used.
This
can
be
in
the
form
of
a
textual
message
at
program
startup
or
in
documentation
(online
or
textual)
provided
with
the
package.
Redistribution
and
use
in
source
and
binary
forms,
with
or
without
modification,
are
permitted
provided
that
the
following
conditions
are
met:
1.
Redistributions
of
source
code
must
retain
the
copyright
notice,
this
list
of
conditions
and
the
following
disclaimer.
2.
Redistributions
in
binary
form
must
reproduce
the
above
copyright
notice,
this
list
of
conditions
and
the
following
disclaimer
in
the
documentation
and/or
other
materials
provided
with
the
distribution.
3.
All
advertising
materials
mentioning
features
or
use
of
this
software
must
display
the
following
acknowledgement:
″This
product
includes
cryptographic
software
written
by
Eric
Young
The
word
’cryptographic’
can
be
left
out
if
the
routines
from
the
library
being
used
are
not
cryptographic
related
:-).
4.
If
you
include
any
Windows
specific
code
(or
a
derivative
thereof)
from
the
apps
directory
(application
code)
you
must
include
an
acknowledgement:
″This
product
includes
software
written
by
Tim
Hudson
THIS
SOFTWARE
IS
PROVIDED
BY
ERIC
YOUNG
``AS
IS’’
AND
ANY
EXPRESS
OR
IMPLIED
WARRANTIES,
INCLUDING,
BUT
NOT
LIMITED
TO,
THE
IMPLIED
WARRANTIES
OF
MERCHANTABILITY
AND
FITNESS
FOR
A
PARTICULAR
PURPOSE
ARE
DISCLAIMED.
IN
NO
EVENT
SHALL
THE
AUTHOR
OR
CONTRIBUTORS
BE
LIABLE
FOR
ANY
DIRECT,
INDIRECT,
INCIDENTAL,
SPECIAL,
EXEMPLARY,
OR
CONSEQUENTIAL
DAMAGES
(INCLUDING,
BUT
NOT
LIMITED
TO,
PROCUREMENT
OF
SUBSTITUTE
GOODS
OR
SERVICES;
LOSS
OF
USE,
DATA,
OR
PROFITS;
OR
BUSINESS
28
IBM
Tivoli
Workload
Scheduler
Release
Notes
INTERRUPTION)
HOWEVER
CAUSED
AND
ON
ANY
THEORY
OF
LIABILITY,
WHETHER
IN
CONTRACT,
STRICT
LIABILITY,
OR
TORT
(INCLUDING
NEGLIGENCE
OR
OTHERWISE)
ARISING
IN
ANY
WAY
OUT
OF
THE
USE
OF
THIS
SOFTWARE,
EVEN
IF
ADVISED
OF
THE
POSSIBILITY
OF
SUCH
DAMAGE.
The
licence
and
distribution
terms
for
any
publically
available
version
or
derivative
of
this
code
cannot
be
changed.
i.e.
this
code
cannot
simply
be
copied
and
put
under
another
distribution
licence
[including
the
GNU
Public
Licence.]
Open
Source:
SNMP
Library
Copyright
1988,
1989
by
Carnegie
Mellon
University
All
Rights
Reserved
Permission
to
use,
copy,
modify,
and
distribute
this
software
and
its
documentation
for
any
purpose
and
without
fee
is
hereby
granted,
provided
that
the
above
copyright
notice
appear
in
all
copies
and
that
both
that
copyright
notice
and
this
permission
notice
appear
in
supporting
documentation,
and
that
the
name
of
CMU
not
be
used
in
advertising
or
publicity
pertaining
to
distribution
of
the
software
without
specific,
written
prior
permission.
CMU
DISCLAIMS
ALL
WARRANTIES
WITH
REGARD
TO
THIS
SOFTWARE,
INCLUDING
ALL
IMPLIED
WARRANTIES
OF
MERCHANTABILITY
AND
FITNESS,
IN
NO
EVENT
SHALL
CMU
BE
LIABLE
FOR
ANY
SPECIAL,
INDIRECT
OR
CONSEQUENTIAL
DAMAGES
OR
ANY
DAMAGES
WHATSOEVER
RESULTING
FROM
LOSS
OF
USE,
DATA
OR
PROFITS,
WHETHER
IN
AN
ACTION
OF
CONTRACT,
NEGLIGENCE
OR
OTHER
TORTIOUS
ACTION,
ARISING
OUT
OF
OR
IN
CONNECTION
WITH
THE
USE
OR
PERFORMANCE
OF
THIS
SOFTWARE.
Open
Source:
Time
Zone
Library
Copyright
(c)
1985,
1987,
1988
The
Regents
of
the
University
of
California.
All
rights
reserved.
Redistribution
and
use
in
source
and
binary
forms
are
permitted
provided
that
the
above
copyright
notice
and
this
paragraph
are
duplicated
in
all
such
forms
and
that
any
documentation,
advertising
materials,
and
other
materials
related
to
such
distribution
and
use
acknowledge
that
the
software
was
developed
by
the
University
of
California,
Berkeley.
The
name
of
the
University
may
not
be
used
to
endorse
or
promote
products
derived
from
this
software
without
specific
prior
written
permission.
THIS
SOFTWARE
IS
PROVIDED
``AS
IS’’
AND
WITHOUT
ANY
EXPRESS
OR
IMPLIED
WARRANTIES,
INCLUDING,
WITHOUT
LIMITATION,
THE
IMPLIED
WARRANTIES
OF
MERCHANT[A]BILITY
AND
FITNESS
FOR
A
PARTICULAR
PURPOSE.
Toolkit
of
Tivoli
Internationalization
Services
Copyright
1990,
by
Alfalfa
Software
Incorporated,
Cambridge,
Massachusetts.
All
Rights
Reserved
Notices
29
Permission
to
use,
copy,
modify,
and
distribute
this
software
and
its
documentation
for
any
purpose
and
without
fee
is
hereby
granted,
provided
that
the
above
copyright
notice
appear
in
all
copies
and
that
both
that
copyright
notice
and
this
permission
notice
appear
in
supporting
documentation,
and
that
Alfalfa’s
name
not
be
used
in
advertising
or
publicity
pertaining
to
distribution
of
the
software
without
specific,
written
prior
permission.
ALPHALPHA
DISCLAIMS
ALL
WARRANTIES
WITH
REGARD
TO
THIS
SOFTWARE,
INCLUDING
ALL
IMPLIED
WARRANTIES
OF
MERCHANTABILITY
AND
FITNESS,
IN
NO
EVENT
SHALL
ALPHALPHA
BE
LIABLE
FOR
ANY
SPECIAL,
INDIRECT
OR
CONSEQUENTIAL
DAMAGES
OR
ANY
DAMAGES
WHATSOEVER
RESULTING
FROM
LOSS
OF
USE,
DATA
OR
PROFITS,
WHETHER
IN
AN
ACTION
OF
CONTRACT,
NEGLIGENCE
OR
OTHER
TORTIOUS
ACTION,
ARISING
OUT
OF
OR
IN
CONNECTION
WITH
THE
USE
OR
PERFORMANCE
OF
THIS
SOFTWARE.
Trademarks
IBM,
Tivoli,
the
Tivoli
logo,
Tivoli
Enterprise,
Tivoli
Enterprise
Console,
AIX,
AS/400,
OS/400,
BookManager,
Dynix,
OS/390,
pSeries,
iSeries,
NetView,
and
Sequent,
z/OS
are
trademarks
or
registered
trademarks
of
International
Business
Machines
Corporation
or
Tivoli
Systems
Inc.
in
the
United
States,
other
countries,
or
both.
Intel
is
a
registered
trademark
of
Intel
Corporation.
Microsoft,
Windows,
Windows
NT,
and
the
Windows
logo
are
registered
trademarks
of
Microsoft
Corporation
in
the
United
States,
other
countries,
or
both.
UNIX
is
a
registered
trademark
of
The
Open
Group
in
the
United
States
and
other
countries.
Java
and
all
Java-based
trademarks
and
logos
are
trademarks
or
registered
trademarks
of
Sun
Microsystems,
Inc.
in
the
United
States
and
other
countries.
Other
company,
product,
and
service
names
may
be
trademarks
or
service
marks
of
others.
30
IBM
Tivoli
Workload
Scheduler
Release
Notes
����
Program
Number:
5698-WSH
Printed
in
USA
SC32-1277-01
