ibm tivoli workload schedulerpublib.boulder.ibm.com/tividd/td/tws/sc32-1275-01/en_us/...explains the...
TRANSCRIPT
-
IBM
Tivoli
Workload
Scheduler
Troubleshooting
and
Error
Messages
Version
8.2
(Maintenance
Release
April
2004)
SC32-1275-01
���
-
IBM
Tivoli
Workload
Scheduler
Troubleshooting
and
Error
Messages
Version
8.2
(Maintenance
Release
April
2004)
SC32-1275-01
���
-
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
“Notices”
on
page
117.
Refreshed
Edition
(April
2004)
This
edition
applies
to
version
8,
release
2,
modification
0
of
IBM
Tivoli
Workload
Scheduler
(product
number
5698-WSH)
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
©
Copyright
International
Business
Machines
Corporation
1991,
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
Who
Should
Read
This
Manual
.
.
.
.
.
.
.
. v
What
This
Manual
Contains
.
.
.
.
.
.
.
.
. v
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Publications
for
Tivoli
Workload
Scheduler
.
.
. vi
Publications
for
Tivoli
Workload
Scheduler
for
z/OS
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Accessing
Publications
Online
.
.
.
.
.
.
. viii
Ordering
Publications
.
.
.
.
.
.
.
.
. viii
Providing
Feedback
about
Publications
.
.
.
. viii
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. ix
Contacting
IBM
Software
Support
.
.
.
.
.
.
. ix
Conventions
Used
in
This
Manual
.
.
.
.
.
.
. ix
Typeface
conventions
.
.
.
.
.
.
.
.
.
.
. ix
Operating
system-dependent
variables
and
paths
.
. x
Part
1.
Error
Messages
.
.
.
.
.
.
. 1
Chapter
1.
Mailman
Messages
.
.
.
.
. 3
Chapter
2.
Writer
Messages
.
.
.
.
.
. 7
Chapter
3.
Downloader
Messages
.
.
.
. 9
Chapter
4.
Jobman
Messages
.
.
.
.
. 13
Chapter
5.
Batchman
Messages
.
.
.
. 17
Chapter
6.
Conman
Messages
.
.
.
.
. 23
Chapter
7.
Stageman
Messages
.
.
.
. 25
Chapter
8.
Schedulr
Messages
.
.
.
. 27
Chapter
9.
Compiler
Messages
.
.
.
. 29
Chapter
10.
Jobmon
Messages
.
.
.
. 33
Chapter
11.
Customize
Messages
.
.
. 37
Chapter
12.
Tivoli
Workload
Scheduler
Connector
Messages
.
.
.
.
.
.
.
. 43
Chapter
13.
SSL
Messages
.
.
.
.
.
. 45
Chapter
14.
Netman
Messages
.
.
.
. 47
Part
2.
Troubleshooting
.
.
.
.
.
. 51
Chapter
15.
Introduction
to
Troubleshooting
.
.
.
.
.
.
.
.
.
.
. 53
Product
Maintenance
.
.
.
.
.
.
.
.
.
.
. 53
Databases
.
.
.
.
.
.
.
.
.
.
.
.
.
. 53
Reporting
.
.
.
.
.
.
.
.
.
.
.
.
.
. 55
Maintaining
the
File
System
.
.
.
.
.
.
.
. 55
Chapter
16.
Diagnostic
Tools
.
.
.
.
. 57
Trace
Logging
.
.
.
.
.
.
.
.
.
.
.
.
. 57
Autotrace
Feature
.
.
.
.
.
.
.
.
.
.
. 57
Snapshot
Tools
.
.
.
.
.
.
.
.
.
.
.
.
. 57
Metronome
.
.
.
.
.
.
.
.
.
.
.
.
. 57
Auditing
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 58
Enabling
the
Audit
Feature
.
.
.
.
.
.
.
. 59
Auditing
Log
Format
.
.
.
.
.
.
.
.
.
. 59
Audit
Log
Header
.
.
.
.
.
.
.
.
.
.
. 62
Sample
Audit
Log
Entries
.
.
.
.
.
.
.
. 63
Chapter
17.
Troubleshooting
Installation
and
Configuration
.
.
.
.
. 65
Installing
on
Windows
DataCenter
Servers
.
.
.
. 65
Installing
on
Windows
2000
.
.
.
.
.
.
.
.
. 65
Unremoved
Temporary
Files
on
Windows
2000
65
Tivoli
Workload
Scheduler
Re-installation
Fails
via
ISMP
.
.
.
.
.
.
.
.
.
.
.
.
.
. 65
Checking
for
Post
Installation
Failures
.
.
.
.
. 66
Cleaning
Up
Tivoli
Workload
Scheduler
Installations
67
Uninstalling
on
Unix
.
.
.
.
.
.
.
.
.
. 67
Cleaning
Up
on
Windows
.
.
.
.
.
.
.
. 69
Troubleshooting
the
Tivoli
Workload
Scheduler
Connector
Installation
.
.
.
.
.
.
.
.
.
.
. 70
Checking
that
the
Connector
Has
Properly
Installed
.
.
.
.
.
.
.
.
.
.
.
.
.
. 70
Removing
TMF_JSS
and
the
Connector
.
.
.
. 72
Checking
that
the
Connector
has
Properly
Uninstalled
.
.
.
.
.
.
.
.
.
.
.
.
. 73
Collecting
Troubleshooting
Documentation
.
.
. 74
Updating
the
Security
File
After
Installing
the
Connector
.
.
.
.
.
.
.
.
.
.
.
.
.
. 75
Installation
Logs
.
.
.
.
.
.
.
.
.
.
.
.
. 75
Unattended
Installation
Using
the
twsinst
Script
101
Uninstalling
via
ISMP
on
Windows
2000
.
.
.
. 102
Chapter
18.
Performance
and
Availability
.
.
.
.
.
.
.
.
.
.
.
. 103
Optimizing
the
Network
.
.
.
.
.
.
.
.
. 103
Planning
Space
for
Queues
.
.
.
.
.
.
.
. 104
Tuning
Mailman
Servers
.
.
.
.
.
.
.
.
. 105
How
Tivoli
Workload
Scheduler
Resolves
the
Windows
User
Name
Account
.
.
.
.
.
.
.
. 106
Windows
2000
and
Terminal
Services
.
.
.
.
. 107
Using
a
Temporary
Directory
on
Unix
.
.
.
.
. 107
©
Copyright
IBM
Corp.
1991,
2004
iii
||
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-
Chapter
19.
Common
Problems
and
Troubleshooting
Scenarios
.
.
.
.
. 109
Part
3.
Appendixes
.
.
.
.
.
.
.
. 115
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 117
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 118
Glossary
.
.
.
.
.
.
.
.
.
.
.
.
. 119
iv
Error
Messages
-
Preface
Tivoli®
Workload
Scheduler
Error
Messages
provides
details
of
the
error
messages
that
might
be
encountered
during
the
operating
of
the
Tivoli
Workload
Scheduler.
Maintenance
Release
This
is
a
maintenance
refresh
of
the
corresponding
IBM
Tivoli
Workload
Scheduler
Version
8.2
manual,
form
number
SC32–1275–00.
It
contains
updates
for
the
following
APARs:
v
IY48139
v
IY50132
v
IY50136
v
IY50574
v
IY51294
v
IY51312
v
IY52994
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
manual
for
the
corresponding
information.
Who
Should
Read
This
Manual
This
guide
is
designed
to
help
operators
deal
with
any
error
messages
they
encounter
during
their
work
with
Tivoli
Workload
Scheduler.
The
guide
lists
all
existing
Tivoli
Workload
Scheduler
error
messages
and
provides
information
in
terms
of
explanation,
system
action,
operator
response,
and
other
details.
Such
details
do
not
appear
online
with
the
message
texts,
but
are
reported
in
this
book.
What
This
Manual
Contains
This
manual
contains
the
following
sections:
Part
I.
Part
I
contains
the
following
chapters:
v
Chapter
1,
“Mailman
Messages,”
on
page
3
Describes
the
error
messages
generated
by
the
Mailman
component.
v
Chapter
2,
“Writer
Messages,”
on
page
7
Describes
the
error
messages
generated
by
the
Writer
component.
v
Chapter
3,
“Downloader
Messages,”
on
page
9
Describes
the
error
messages
generated
by
the
Downloader
component.
v
Chapter
4,
“Jobman
Messages,”
on
page
13
Describes
the
error
messages
generated
by
the
Jobman
component.
v
Chapter
5,
“Batchman
Messages,”
on
page
17
Describes
the
error
messages
generated
by
the
Batchman
component.
v
Chapter
6,
“Conman
Messages,”
on
page
23
©
Copyright
IBM
Corp.
1991,
2004
v
|
|||
|
|
|
|
|
|
|
|||
-
Describes
the
error
messages
generated
Conman
component.
v
Chapter
7,
“Stageman
Messages,”
on
page
25
Describes
the
error
messages
generated
by
the
Stageman
component.
v
Chapter
8,
“Schedulr
Messages,”
on
page
27
Describes
the
error
messages
generated
by
the
Schedulr
component.
v
Chapter
9,
“Compiler
Messages,”
on
page
29
Describes
the
error
messages
generated
by
the
Compiler
component.
v
Chapter
10,
“Jobmon
Messages,”
on
page
33
Describes
the
error
messages
generated
by
Jobmon
component
v
Chapter
11,
“Customize
Messages,”
on
page
37
Describes
the
error
messages
generated
by
the
Customize
component.
v
Chapter
12,
“Tivoli
Workload
Scheduler
Connector
Messages,”
on
page
43
Describes
the
error
messages
generated
by
the
Tivoli
Workload
Scheduler
Connector.
v
Chapter
13,
“SSL
Messages,”
on
page
45
Describes
the
error
messages
generated
SSL
component.
v
Chapter
14,
“Netman
Messages,”
on
page
47
Describes
the
error
messages
generated
by
the
Netman
component.
Part
II.
Troubleshooting
Part
II
contains
the
following
chapters:
v
Chapter
15,
“Introduction
to
Troubleshooting,”
on
page
53
Gives
and
Introduction
to
Troubleshooting.
v
Chapter
16,
“Diagnostic
Tools,”
on
page
57
Gives
an
overview
of
the
Tivoli
Workload
Scheduler
diagnostic
tools.
v
Chapter
17,
“Troubleshooting
Installation
and
Configuration,”
on
page
65
Describes
issues
dealing
with
the
installation,
removal,
and
configuration
of
Tivoli
Workload
Scheduler.
v
Chapter
18,
“Performance
and
Availability,”
on
page
103
Describes
Performance
and
Availability.
v
Chapter
19,
“Common
Problems
and
Troubleshooting
Scenarios,”
on
page
109
Describes
Common
Problems
and
Trobleshooting
Scenarios.
Publications
This
section
lists
publications
in
the
Tivoli
Workload
Scheduler
for
z/OS
library
and
any
other
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online,
how
to
order
Tivoli
publications,
and
how
to
make
comments
on
Tivoli
publications.
Publications
for
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
vi
Error
Messages
-
Explains
the
Tivoli
Workload
Scheduler
command
line,
understanding
how
extended
and
network
agents
work,
and
integrating
Tivoli
Workload
Scheduler
with
NetView®
and
with
Tivoli
Business
Systems
Manager.
v
IBM
Tivoli
Workload
Scheduler
for
Applications
User’s
Guide,
SC32-1278
Describes
installing,
using,
and
troubleshooting
for
the
Tivoli
Workload
Scheduler
extended
agents.
v
IBM
Tivoli
Workload
Scheduler
for
Applications
Release
Notes,
SC32-1279
Provides
last-minute
information
about
the
Tivoli
Workload
Scheduler
extended
agents.
v
IBM
Tivoli
Workload
Scheduler
AS/400®
Limited
FTA
User’s
Guide,
SC32-1280
Describes
installing,
configuring,
and
using
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
Tivoli
Workload
Scheduler
Plus
module.
v
IBM
Tivoli
Workload
Scheduler
Release
Notes,
SC32-1277
Explains
late-breaking
information
about
Tivoli
Workload
Scheduler.
Publications
for
Tivoli
Workload
Scheduler
for
z/OS
The
following
documents
are
available
in
the
Tivoli
Workload
Scheduler
for
z/OS
library:
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning,
SC32-1265
Describes
how
to
customize
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
Tivoli
Workload
Scheduler
suite.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Installation
Guide,
SC32-1264
Describes
how
to
install
Tivoli
Workload
Scheduler
for
z/OS.
v
IBM
Job
Scheduling
Console
Release
Notes,
SC32-1258
Provides
information
about
working
with
Tivoli
Workload
Scheduler,
regardless
of
platform,
from
a
common
GUI.
v
IBM
Job
Scheduling
Console
User’s
Guide,
SC32-1257
Provides
information
about
working
with
Tivoli
Workload
Scheduler,
regardless
of
platform,
from
a
common
GUI.
v
IBM
Tivoli
Workload
Scheduler
for
z/OS
Licensed
Program
Specifications,
GI11-4208
Provides
planning
information
to
plan
about
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
Preface
vii
-
Provided
with
the
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.
Accessing
Publications
Online
The
product
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
print
PDF
documents
on
other
than
letter-sized
paper,
select
the
Fit
to
page
check
box
in
the
Adobe
Acrobat
Print
dialog.
This
option
is
available
when
you
click
File
→
Print.
Fit
to
page
ensures
that
the
full
dimensions
of
a
letter-sized
page
print
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
Error
Messages
http://publib.boulder.ibm.com/tividd/td/tdprodlist.htmlhttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.ibm.com/software/tivoli/order-lit/http://www.ibm.com/software/sysmgmt/products/support
-
Accessibility
Accessibility
features
help
users
with
a
physical
disability,
such
as
restricted
mobility
or
limited
vision,
to
use
software
products
successfully.
With
this
product,
you
can
use
assistive
technologies
to
hear
and
navigate
the
interface.You
can
also
use
the
keyboard
instead
of
the
mouse
to
operate
all
features
of
the
graphical
user
interface.
For
additional
information,
see
the
Accessibility
Appendix
in
the
Tivoli
Workload
Scheduler
Installation
Guide.
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
e-mail
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
The
manual
uses
several
typeface
conventions
for
special
terms
and
actions.
These
conventions
have
the
following
meanings:
Information
type
Style
convention
Example
Commands
All
capital
letters
CREATE
References
in
the
text
to
fields
on
panels
All
capital
letters
QUANTITY
Input
you
should
type
in
panel
fields
Monospace
MYAPPLICATION
First
time
new
term
introduced
Italics
Application
Typeface
conventions
This
guide
uses
the
following
typeface
conventions:
Bold
v
Lowercase
commands
and
mixed
case
commands
that
are
otherwise
difficult
to
distinguish
from
surrounding
text
v
Interface
controls
(check
boxes,
push
buttons,
radio
buttons,
spin
buttons,
fields,
folders,
icons,
list
boxes,
items
inside
list
boxes,
multicolumn
lists,
containers,
menu
choices,
menu
names,
tabs,
property
sheets),
labels
(such
as
Tip:,
and
Operating
system
considerations:)
v
Column
headings
in
a
table
v
Keywords
and
parameters
in
text
Preface
ix
http://techsupport.services.ibm.com/guides/handbook.html
-
Italic
v
Citations
(titles
of
books,
diskettes,
and
CDs)
v
Words
defined
in
text
v
Emphasis
of
words
(words
as
words)
v
Letters
as
letters
v
New
terms
in
text
(except
in
a
definition
list)
v
Variables
and
values
you
must
provide
Monospace
v
Examples
and
code
examples
v
File
names,
programming
keywords,
and
other
elements
that
are
difficult
to
distinguish
from
surrounding
text
v
Message
text
and
prompts
addressed
to
the
user
v
Text
that
the
user
must
type
v
Values
for
arguments
or
command
options
Operating
system-dependent
variables
and
paths
This
guide
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.
x
Error
Messages
-
Part
1.
Error
Messages
©
Copyright
IBM
Corp.
1991,
2004
1
-
2
Error
Messages
-
Chapter
1.
Mailman
Messages
This
chapter
lists
the
error
messages
issued
by
Mailman.
AWSBCV001E
Error
Batchman
abended,
Status:
Status
Explanation:
Mailman
issues
this
message
when
Batchman
terminates
unexpectedly.
Status
contains
an
exit
status
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV003E
Error
creating
Program.
Error
number
System
Error
Explanation:
Mailman
was
unable
to
start
the
Batchman
process.
Program
is
the
fully
qualified
name
for
the
Batchman
program.
System
Error
is
the
operating
system
error
message.
Operator
Response:
Make
sure
that
the
Batchman
executable
exists
and
that
it
has
the
correct
file
access
permission.
If
the
problem
persists,
contact
your
local
service
representative
for
assistance.
AWSBCV004E
Error
creating
Program.
Error
number
System
Error
Explanation:
Mailman
was
unable
to
start
a
Mailman
server
process.
Program
is
the
fully
qualified
name
for
the
Batchman
program.
System
Error
is
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV005E
Error
opening
File.
Error
Error
Explanation:
Mailman
was
unable
to
open
for
writing
either
the
Courier.msg
or
the
Intercom.msg
files.
Courier.msg
is
opened
when
Mailman
is
running
on
a
Standard
Agent
CPU.
File
is
the
fully
qualified
name
for
the
message
file.
Error
is
a
message
that
describes
the
error
and
includes
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV008E
Error
can
not
open
input
file,
Error
Error
Explanation:
Mailman
is
unable
to
open
its
message
file,
Mailbox.msg.
This
message
is
also
issued
if
a
Mailman
server
process
is
unable
to
open
its
message
file
pobox/[server].msg.
Error
is
a
message
that
contains
information
about
the
error
and
includes
the
operating
system
error
message.
Operator
Response:
″Too
many
open
files″
is
one
of
the
possible
system
messages
returned.
The
problem
comes
either
from
your
Tivoli
Workload
Scheduler
user
or
from
your
system.
One
of
them
has
reached
its
opened
files
limit
(typically
64
for
a
single
user).
You
can
see
the
user’s
limits
with
the
’limit’
command.
The
file
limit
is
the
’descriptor’
line
for
csh
users.
Take
one
of
the
following
actions:
v
Add
the
following
lines
in
your
system
parameters
file(/etc/system)
and
reboot
the
system:
set
rlim_fd_max
=
4096
set
rlim_fd_cur
=
1024
This
may
consume
slightly
more
available
memory,
but
it
speeds
up
the
system.
v
Modify
your
Tivoli
Workload
Scheduler
user
environment
(the
following
stands
for
a
csh
user):
limit
descriptors
nnn
by
replacing
nnn
with
a
value
greater
than
the
one
you
got
with
’limit’.
AWSBCV009E
Error
opening
PO
Box
for
CPU
Name,
Error
Error
Message
Explanation:
Mailman
is
not
able
to
open
a
message
file
in
the
Tivoli
Workload
Scheduler
directory
named
pobox.
The
message
file
in
the
pobox
directory
contains
messages
that
could
not
be
delivered.
CPU
Name
specifies
the
name
of
the
message
file.
Error
message
describes
the
error
and
includes
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV012E
Error
reading
input
mailbox,
Error
Error
Message
Explanation:
Mailman
was
unable
to
read
a
message
from
its
local
mailbox,
Mailbox.msg,
or
[Server].msg
for
a
server
Mailman.
Error
Message
describes
the
error
and
includes
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
©
Copyright
IBM
Corp.
1991,
2004
3
-
AWSBCV015E
Error
writing
to
PO
Box
for
CPU
Name,
Error
Error
Message
Explanation:
Mailman
was
unable
to
write
a
message
record
to
the
pobox
file
associated
with
a
CPU.
CPU
Name
is
the
name
of
the
CPU
to
which
the
message
is
sent.
Error
Message
describes
the
error
and
includes
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV037E
Error
reading
Sinfonia.
Error:
Error
Message
Explanation:
Mailman
encountered
an
error
while
it
was
reading
the
Sinfonia
file.
Mailman
sends
the
Sinfonia
file
to
each
CPU
at
initialization/link
time.
Error
Message
contains
the
fully
qualified
name
of
the
Sinfonia
file
and
includes
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV038E
Error
opening
Sinfonia
Explanation:
Mailman
failed
to
allocate
the
memory
necessary
to
store
the
records
that
are
to
be
read
from
the
Sinfonia
file.
Mailman
reads
the
records
during
the
Symphony
download
to
a
CPU.
Operator
Response:
Check
if
the
system
has
enough
memory
available.
Otherwise
try
to
close
all
the
applications
you
don’t
need.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBCV062E
Error
opening
Symphony,
Error:
Error
Message
Explanation:
Mailman
encountered
an
error
when
attempting
to
open
the
Symphony
file.
Error
Message
contains
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV066E
Error
clearing
on
PO
Box
for
File.
Error:
Error
Message
Explanation:
Mailman
encountered
an
error
while
rereading
a
record
from
the
message
file.
Mailman
processes
message
records
in
the
following
way:
1.
It
reads
a
record.
2.
It
processes
the
record.
3.
It
removes
the
record
from
the
message
file.
File
is
the
name
of
the
file
that
Mailman
is
processing.
Error
Message
contains
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV067E
Error
reading
PO
Box
for
File.
Error:
Error
Message
Explanation:
Mailman
encountered
an
error
while
trying
to
read
a
message
from
a
message
file
in
the
pobox
directory.
File
is
the
name
of
the
file
that
Mailman
is
processing.
Error
Message
contains
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV068E
Error
clearing
read
on
Mailbox.
Error:
Explanation:
Mailman
processes
record
messages
in
the
following
way:
1.
It
reads
a
record.
2.
It
processes
the
record.
3.
It
removes
the
record
from
the
message
file.
Mailman
issues
this
error
when
the
length
of
the
reread
record
does
not
match
the
length
of
the
record
when
it
was
first
read.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV069E
Error
CPU
Name
not
found
in
Symphony
Explanation:
Mailman
cannot
find
the
CPU
name
of
either
this
node
or
of
the
master
CPU
in
the
Symphony
file.
CPU
Name
is
the
name
of
the
CPU
that
Mailman
cannot
find.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV076E
Error
writing
CPU
info
to
Symphony
for
CPU
Name.
Error:
System
Error
Explanation:
Mailman
could
not
write
a
CPU
record
in
the
Symphony
file.
CPU
Name
is
the
name
of
the
CPU
Mailman
is
trying
to
write
of.
System
Error
contains
the
operating
system
error
message.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV088E
Error
writing
to
intercom.
Error:
Error
Message
Explanation:
Mailman
encountered
an
error
when
it
tried
to
write
a
mailbox
record
to
the
Intercom.msg
message
file.
The
message
could
not
be
sent
to
Batchman.
Error
Message
contains
the
operating
system
error
message.
Often,
the
operating
system
error
message
is
AWSBCV015E
•
AWSBCV088E
4
Error
Messages
-
″End
of
file″.
This
means
that
the
internal
size
limit
has
been
reached.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
Administrator
Response:
In
response
to
the
″End
of
file″
error
message,
expand
the
message
file
using
the
evtsize
utility.
To
have
files
permanently
increased
in
size
internally,
insert
and
set
the
EVSIZE
variable
to
the
desired
size
in
the
″StartUp″
command
file
(before
the
run
of
Netman)
in
the
Tivoli
Workload
Scheduler
user’s
home
directory.
AWSBCV095E
Error
writing
to
server
Server
Name.
Error:
Error
Message
Explanation:
Mailman
was
unable
to
pass
a
message
to
a
Mailman
server.
Messages
are
passed
to
a
Mailman
server
process
by
writing
mailbox
records
to
its
pobox/[server].msg
file.
See
the
’server’
keyword
in
the
CPU
definition
for
an
explanation
of
Mailman
server
processes.
Server
Name
is
the
name
of
the
Mailman
server
to
which
the
message
is
sent.
Error
Message
describes
the
error
and
includes
the
operating
system
error
message.
Often,
the
operating
system
error
message
is
″End
of
file″.
This
means
that
the
internal
size
limit
has
been
reached.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
Administrator
Response:
In
response
to
the
″End
of
file″
error
message,
expand
the
message
file
using
the
evtsize
utility.
To
have
files
permanently
increased
in
size
internally,
insert
and
set
the
EVSIZE
variable
to
the
desired
size
in
the
″StartUp″
command
file
(before
the
run
of
Netman)
in
the
Tivoli
Workload
Scheduler
user’s
home
directory.
AWSBCV097E
Error:
Not
a
remote
and
no
batchman
Explanation:
Mailman
cannot
access
the
Batchman
program
file.
Batchman
does
not
run
on
Standard
Agent
CPUs,
but
is
needed
for
Fault
Tolerant
CPUs.
Operator
Response:
Make
sure
that
the
Batchman
executable
exists
and
that
it
has
correct
file
access
permission.
If
the
problem
persists,
contact
your
local
service
representative
for
assistance.
AWSBCV107E
Error:
CPU
Name
not
found
in
Symphony
Explanation:
Mailman
cannot
find
a
CPU
record
in
the
Symphony
file.
CPU
Name
is
the
name
of
the
CPU
whose
record
Mailman
cannot
find.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV110E
Error
Jobman
abended.
Status:
Exit
Status
Explanation:
This
message
is
issued
when
a
Mailman
process
running
on
a
standard
agent
CPU
acknowledges
that
Jobman
has
terminated
unexpectedly.
Exit
Status
contains
the
Jobman
exit
status.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV113E
Master
mailman
gone
without
quit
Explanation:
This
message
is
issued
by
a
Mailman
server
process
when
the
parent
Mailman
process
has
terminated
unexpectedly.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV114E
Error
setting
traps:
Error
Message
Explanation:
Mailman
issues
this
message
when
it
is
unable
to
set
the
termination
signal
handling
routines.
Error
Message
contains
the
operating
system
error
message.
Operator
Response:
This
is
a
system
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV115E
Error
finding
the
new
manager
CPU
CPU
Name,
Error
Message
Explanation:
Mailman
is
unable
to
find
the
new
manager
CPU
in
the
Symphony
file
during
a
switch
manager
command.
CPU
Name
is
the
name
of
the
new
manager
CPU.
Error
Message
is
the
operating
system
error.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV117E
Error:
Switching
managers
in
domain
Domain
Name
Explanation:
Mailman
was
unable
to
switch
domain
managers.
Domain
Name
is
the
name
of
the
domain
where
the
switch
was
taking
place.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV118E
Error:
writing
Symphony
header
Explanation:
Mailman
was
unable
to
update
the
Symphony
record
header
during
the
initialization
process.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV095E
•
AWSBCV118E
Chapter
1.
Mailman
Messages
5
-
AWSBCV119E
Error:
Can’t
find
this
cpu’s
record
in
Symphony
Explanation:
Mailman
is
unable
to
find
in
the
Symphony
file
the
CPU
record
for
the
CPU
on
which
it
is
running.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCV124E
Error
linking
to
1,
SSL
authorization
requested
but
not
supported
Explanation:
Mailman
is
unable
to
connect
using
the
SSL
due
to
an
inconsistent
TWS
network
configuration.
Most
common
reason
for
this
error
is
an
inconsistent
Security
Level.
For
example:
parent
DM
(no
securitylevel
specified)
|
X
communication
is
not
possible
|
DM
(securitylevel
on
or
force)
Operator
Response:
Verify
on
the
Master
Domain
Manager
which
is
the
security
level
of
the
Workstations
that
cannot
communicate.
AWSBCV119E
•
AWSBCV124E
6
Error
Messages
-
Chapter
2.
Writer
Messages
This
chapter
lists
the
error
messages
generated
by
Writer.
AWSBCW003W
Error
opening
connection
to
mailman.
Error
Error
Text
Explanation:
Writer
cannot
connect
to
the
remote
Mailman.
The
socket
descriptor
passed
to
Writer
by
Netman
is
invalid.
Error
Text
is
a
string
indicating
that
the
socket
descriptor
is
invalid.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW011W
Error
in
(Symphony
rec):
Error
Text
Explanation:
An
error
occurred
while
converting
a
Symphony
record
from
network
to
host
byte
order.
Error
Text
contains,
when
available,
the
record
type,
the
expected
record
type
and
the
record
number.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW012W
Error
receiving
record:
Error
Text
Explanation:
Writer
was
unable
to
read
a
record
from
Mailman.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW014W
Error
opening
mailbox
file:
Error
Text
Explanation:
Writer
is
unable
to
open
the
mailbox.msg
message
file.
Error
Text
is
a
string
that
describes
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW015W
Error
writing
mailbox
file:
Error
Text
Explanation:
Writer
is
unable
to
write
to
the
message
file
mailbox.msg.
Error
Text
is
a
string
that
describes
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW016W
Error
sending
LinkInit
rec:
Error
Text
Explanation:
Writer
is
unable
to
send
the
initialization
process
Link
Init
record
to
Mailman.
Error
Text
is
a
string
that
describes
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW017W
Error
sending
LinkAck
rec:
Error
Text
Explanation:
Writer
is
unable
to
send
a
LinkAck
record
to
Mailman
to
acknowledge
that
a
packet
has
been
received
correctly.
Error
Text
is
a
string
that
describes
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW018W
Error
sending
LinkNack
rec:
Error
Text
Explanation:
Writer
is
unable
to
indicate
to
Mailman
with
a
LinkNack
record
that
there
was
a
communication
error
while
receiving
an
initialization
packet.
Error
Text
is
a
string
that
describes
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW019W
Error
sending
LinkCmd
rec:
Error
Text
Explanation:
Writer,
when
exiting
on
error,
is
unable
to
send
an
unlink
command
record
to
Mailman.
Error
Text
is
a
string
that
describes
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW020W
Error:
expecting
StopSymphony
rec,
received:
Error
Text
Explanation:
Writer
received
an
incorrect
command
during
workstation
initialization.
Writer
expected
a
″stop
Symphony″
command
after
mailman
downloaded
the
Symphony
file.
Error
Text
is
not
used.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
©
Copyright
IBM
Corp.
1991,
2004
7
-
AWSBCW021W
Error:
Unexpected
StopSymphony
record
received:
Error
Text
Explanation:
Writer
received
a
″stop
Symphony″
record
when
Mailman
was
not
downloading
the
Symphony
file.
Error
Text
is
not
used.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW025W
Error:
Too
few
arguments
Explanation:
Writer
is
started
by
Netman
with
an
incorrect
number
of
arguments.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW027W
Error
unable
to
create
stdlist
Explanation:
Writer
is
unable
to
create
its
stdlist
file.
Writer
creates
its
own
stdlist
file
when
the
″merge
stdlists″
option
is
set
to
″no″
in
the
localopts
file.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW033W
Error:
Could
not
allocate
storage
for
comarea
Explanation:
Writer
could
not
allocate
memory
for
internal
data
structures.
Operator
Response:
Check
if
the
system
has
enough
memory
available.
Otherwise,
try
to
close
all
the
applications
that
you
do
not
need.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBCW045W
Error
writing
an
″SY″
init
record
to
the
Mailbox
Explanation:
Writer
is
unable
to
write
an
″init
synchronization″
message
to
Mailman.
Mailman
uses
this
message
to
start
its
Symphony
synchronization
process.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW047E
Error
creating
process;
error
number
number
Explanation:
Writer
is
unable
to
create
the
specified
process,
where:
process
Is
the
name
of
the
process.
error
Is
the
operating
system
error
number.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBCW021W
•
AWSBCW047E
8
Error
Messages
||
||
||
||
||
-
Chapter
3.
Downloader
Messages
This
chapter
lists
the
error
messages
issued
by
Downloader.
AWSBDG001E
Error
opening
connection
to
client,
Error
Error
Text
Explanation:
Downloader
cannot
connect
to
the
remote
client.
The
socket
descriptor
passed
to
Downloader
by
Netman
is
invalid.
Error
Text
is
a
string
indicating
that
the
socket
descriptor
is
invalid.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBDG002E
Error
unable
to
create
stdlist
Explanation:
Downloader
is
unable
to
create
its
stdlist
file.
Downloader
creates
its
own
stdlist
file
when
the
″merge
stdlists″
option
is
set
to
″no″
in
the
localopts
file.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBDG005E
Error:
Too
few
arguments
Explanation:
Downloader
is
started
by
Netman
with
an
incorrect
number
of
arguments.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBDG007E
Error
sending
record:
Error
Text
Explanation:
Downloader
was
unable
to
send
a
record.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBDG008E
Error
receiving
record:
Error
Text
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER,
is
downloading
a
centralized
script
to
this
workstation,
but
the
downloader
was
unable
to
read
one
of
the
records.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
The
information
is
retrieved
from
from
the
operating
system.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBDG009E
Error:
Could
not
allocate
storage
for
comarea
Explanation:
Downloader
could
not
allocate
memory
for
internal
data
structures.
Operator
Response:
Check
if
the
system
has
enough
memory
available.
Otherwise,
try
to
close
all
the
applications
that
you
do
not
need.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBDG011E
Error
writing
File
Namefile:
Error
Text
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER,
is
downloading
a
centralized
script
to
this
workstation.
The
downloader
has
to
write
the
script
in
File
Name
temporary
file
but
it
is
unable
to
write
in
it.
The
download
of
the
script
fails.Error
Textis
a
string
that
describes
the
reason
for
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
Act
according
to
the
information
retrieved
from
the
operating
system
to
remove
the
cause
of
the
error.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBDG012E
Error
openingFile
Namefile:Error
Text
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER,
is
downloading
a
centralized
script
to
this
workstation.
The
downloader
has
to
write
the
script
in
File
Name
temporary
file
but
it
is
unable
to
open
it.
The
download
of
the
script
fails.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
Act
according
to
the
information
retrieved
from
the
operating
system
to
remove
the
cause
of
the
error.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBDG013E
Error
changing
access
mode
to
File
Name
file:Error
Text
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER
is
downloading
a
centralized
script
to
this
workstation.
The
downloader
has
to
write
the
script
in
File
Name
temporary
file
but
it
is
unable
to
set
the
correct
access
mode.
The
download
of
the
script
fails.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
The
©
Copyright
IBM
Corp.
1991,
2004
9
-
information
is
retrieved
from
the
operating
system.
Operator
Response:
Act
according
to
the
information
retrieved
from
the
operating
system
to
remove
the
cause
of
the
error.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBDG014E
Error
closing
File
Name
file:Error
Text
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER
is
downloading
a
centralized
script
to
this
workstation.
The
downloader
has
written
the
script
in
File
Name
temporary
file
but
it
is
unable
to
close
the
file.
The
download
of
the
script
fails.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
Act
according
to
the
information
retrieved
from
the
operating
system
to
remove
the
cause
of
the
error.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBDG015E
Error
converting
from
UTF-8
file
File
Name1to
local
file
File
Name2
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER
is
downloading
a
centralized
script
to
this
workstation.
The
downloader
has
written
the
script
in
File
Name1
temporary
file
but
it
is
unable
to
convert
it
from
UTF-8
to
local
file
File
Name2.
The
download
of
the
script
fails.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBDG016E
Error
the
buffer
is
too
long
Explanation:
In
a
End-to-end
configuration
the
program
is
sending
a
packet
to
downloader
but
the
buffer
is
too
long.
Operator
Response:
This
is
an
internal
error.
Contact
your
local
support
representative
for
assistance.
AWSBDG017E
Error
downloading
file:
Error
text
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER,
is
downloading
a
centralized
script
to
a
target
workstation.
The
download
of
the
script
has
failed.
Error
Text
is
a
string
that
describes
the
cause
of
the
error.
Operator
Response:
Check
for
other
messages
explaining
the
cause
of
the
error
in
the
downloader
log
on
the
target
workstation.
If
no
message
is
present,
contact
your
local
support
representative
for
assistance.
AWSBDG019E
Error
getting
File
Name
file
status
information:
Error
text
Explanation:
Downloader
in
unable
to
retrieve
status
information
for
file
File
Name.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
Operator
Response:
Contact
your
local
support
representative
for
assistance.
AWSBDG021E
Error
creating
directory
Dir
Name:
Error
text
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER,
is
downloading
a
centralized
script
to
a
target
workstation.
The
downloader
has
to
write
the
script
in
a
temporary
file
in
the
Dir
Name
directory,
but
it
is
unable
to
create
the
directory.
The
download
of
the
script
fails.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
Act
according
to
the
information
retrieved
from
the
operating
system
to
remove
the
cause
of
the
error.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBDG022E
Error
writing
file
on
target
machine
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER,
is
downloading
a
centralized
script
to
a
target
workstation,
but
the
download
has
failed.
Operator
Response:
Check
for
other
messages
explaining
the
cause
of
the
error
in
the
downloader
log
on
the
target
workstation
and
contact
your
local
support
representative
for
assistance.
AWSBDW072E
Error
occurred
removing
centralized
script
File
Name:
Error
text
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER,
has
downloaded
a
centralized
script
to
this
workstation
into
the
temporary
file
File
Name.
After
the
script
execution,
jobman
is
not
able
to
remove
the
temporary
file.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
Manually
remove
the
File
Name
file.
Act
according
to
the
information
retrieved
from
the
operating
system
to
remove
the
cause
of
the
error.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBDG014E
•
AWSBDW072E
10
Error
Messages
-
AWSBDW073E
Error
occurred
changing
owner
of
centralized
script
File
Name:
Error
text
Explanation:
In
a
End-to-end
configuration
the
translator
thread,
running
on
OPCMASTER,
has
downloaded
a
centralized
script
to
this
workstation
into
the
temporary
file
File
Name.
Before
the
script
execution,
for
centralized
script
is
possible
to
specify
a
different
owner
for
the
script,
but
jobman
is
not
able
to
change
the
owner
to
the
new
one.
Error
Text
is
a
string
that
describes
the
reason
for
the
error.
The
information
is
retrieved
from
the
operating
system.
Operator
Response:
Act
according
to
the
information
retrieved
from
the
operating
system
to
remove
the
cause
of
the
error.
If
the
problem
persists,
contact
your
local
support
representative
for
assistance.
AWSBDW073E
Chapter
3.
Downloader
Messages
11
-
12
Error
Messages
-
Chapter
4.
Jobman
Messages
This
chapter
lists
the
error
messages
issued
by
Jobman.
AWSBDW001E
Setgid()
failed
with
errno
=
System
Error
Number
Explanation:
Jobman
cannot
set
the
process
group
id
to
the
group
id
of
the
logon
user.
System
Error
Number
contains
the
operating
system
error
message.
Operator
Response:
This
is
a
system
error.
Contact
your
local
support
representative
for
assistance.
AWSBDW002E
Setuid()
failed
with
errno
=
System
Error
Number
Explanation:
Jobman
cannot
set
the
process
user
id
to
the
user
id
of
the
logon
user.
System
Error
Number
contains
the
operating
system
error
message.
Operator
Response:
Check
the
job
properties
in
the
plan
list
from
the
JSConsole
or
the
sj
schedid.jobid;L
command
in
Conman
to
obtain
the
user
id
under
which
Tivoli
Workload
Scheduler
is
attempting
to
launch
the
job.
Verify
this
is
a
valid
user
on
the
system.
If
incorrectly
documented,
fix
the
definition
in
the
database.
You
can
either
rerun
the
job
with
the
from
option
(specifying
the
same
name
of
the
job)
or
submit
the
job
into
the
plan.
Administrator
Response:
If
the
user
is
not
defined
in
the
system,
define
user
then
resubmit
the
job
or
rerun
existing.
If
user
is
not
defined
and
is
erroneous
modify
job
definition
and
resubmit
job
with
an
alias.
AWSBDW003E
Chdir()
failed
with
errno
=
System
Error
Explanation:
Jobman
cannot
change
the
current
working
directory
to
the
home
directory
of
the
logon
user.
System
Error
is
the
operating
system
error
message.
Operator
Response:
This
is
a
system
error.
Contact
your
local
support
representative
for
assistance.
AWSBDW004E
Exec
failed
with
errno
=
System
Error
Explanation:
Jobman
could
not
execute