Você está na página 1de 549

Tivoli Workload Scheduler


Version 8.5.1

Messages

SC23-9114-01
Tivoli Workload Scheduler
®


Version 8.5.1

Messages

SC23-9114-01
Note
Before using this information and the product it supports, read the information in “Notices” on page 525.

This edition applies to version 8, release 5, modification level 1 of IBM Tivoli Workload Scheduler (program number
5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions.
This edition replaces SC23-9114-00.
© Copyright International Business Machines Corporation 2001, 2009.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
List of tables . . . . . . . . . . . . v Plan libraries messages - BIN . . . . . . . . 135
Comm_api messages - BIO . . . . . . . . . 138
About this publication . . . . . . . . vii Connector messages - BIP . . . . . . . . . 140
Customize messages - BIS . . . . . . . . . 141
What is new in this release . . . . . . . . . vii
Demo scripts messages - BIY . . . . . . . . 148
What is new in this publication . . . . . . . vii
Router messages - BJG . . . . . . . . . . 149
Who should read this publication . . . . . . . vii
Migration messages - BJH . . . . . . . . . 151
Publications . . . . . . . . . . . . . . viii
Dataxtract messages - BWX. . . . . . . . . 153
Accessibility . . . . . . . . . . . . . . viii
Calendar - CAL . . . . . . . . . . . . 155
Tivoli technical training . . . . . . . . . . viii
CCMDB integration messages - CCM . . . . . 157
Support information . . . . . . . . . . . viii
Change and configuration management database
messages - CDM . . . . . . . . . . . . 158
Chapter 1. Introduction to messages . . 1 Clustering messages - CDW . . . . . . . . 160
What is new in the messages . . . . . . . . . 1 Command line messages - CLI . . . . . . . 166
How to find a message . . . . . . . . . . . 2 Std utility messages - DDW . . . . . . . . 172
Message sets in subcomponent code order. . . . 4 SSL messages - DEB . . . . . . . . . . . 173
Message sets in subcomponent name order . . . 7 Events file messages - DEC . . . . . . . . . 178
IBM Tivoli message format . . . . . . . . . 10 Security messages - DEJ . . . . . . . . . . 180
Message number . . . . . . . . . . . 10 Miscellaneous command messages - DEK . . . . 190
Message text . . . . . . . . . . . . . 11 Workstation parsing messages - DEM . . . . . 192
Message help . . . . . . . . . . . . . 11 FIFO messages - DEQ . . . . . . . . . . 202
Utilities library list messages - DEU . . . . . . 203
Chapter 2. Message help . . . . . . . 13 TIS library messages - DEV. . . . . . . . . 204
Event management messages - AEM . . . . . . 14 Condition expression parsing messages - DFH . . 205
Action helper messages - AHL . . . . . . . . 15 Event Configuration messages - ECM . . . . . 207
Allocation repository messages - ALR . . . . . 16 Netman messages - EDW . . . . . . . . . 208
Audit service messages - AUD . . . . . . . . 17 Enterprise Java Bean- EJE . . . . . . . . . 215
Event counter messages - BAT . . . . . . . . 19 Event rule builder messages - ERB . . . . . . 218
Utility program messages - BCT . . . . . . . 22 Event rule parser messages - ERP . . . . . . 219
SSL messages (symaccs) - BCU . . . . . . . . 23 Object monitor plug-in messages - ETO . . . . 221
Mailman messages - BCV. . . . . . . . . . 24 Event processing messages - EVP. . . . . . . 222
Writer messages - BCW . . . . . . . . . . 27 Enterprise workload manager messages - EWL . . 223
Monman messages - BCX. . . . . . . . . . 28 File monitor plug-in messages - FMP . . . . . 225
Dload messages - BCZ. . . . . . . . . . . 31 Tivoli Enterprise Console event forwarder plug-in
Scribner messages - BDB . . . . . . . . . . 33 messages - FWD . . . . . . . . . . . . 226
NetView/OpenView messages - BDC. . . . . . 34 Generic action messages - GAP . . . . . . . 227
Downloader messages - BDG . . . . . . . . 35 Generic event plug-in messages - GEP . . . . . 228
Appserverman messages - BDJ . . . . . . . . 39 Gentwsevn messages - GTW . . . . . . . . 229
Jobman messages - BDW . . . . . . . . . . 41 Calendar messages - ICA . . . . . . . . . 231
Jobtable access messages - BDX. . . . . . . . 43 Job management messages - ITA . . . . . . . 232
Mailbox messages - BDY . . . . . . . . . . 45 Job definition base notify service messages - JBN 241
Report headers and subheaders messages - BEC . . 46 Command line messages - JCL . . . . . . . 242
Parms messages - BEE . . . . . . . . . . . 47 Connectors messages - JCO. . . . . . . . . 257
Ftbox messages - BEG . . . . . . . . . . . 48 Common services messages - JCS. . . . . . . 278
Web library messages - BEH . . . . . . . . . 49 Common objects messages - JDB . . . . . . . 282
Users program messages - BEI . . . . . . . . 56 Job definition service messages - JDD . . . . . 287
Batchman messages - BHT . . . . . . . . . 58 Job dispatcher messages - JDE . . . . . . . . 288
Conman messages - BHU. . . . . . . . . . 61 WebSphere Java 2 Enterprise Edition job executor
Stageman messages - BHV . . . . . . . . . 93 for CAS - JEJ . . . . . . . . . . . . . 304
Object parsing messages - BHW . . . . . . . 99 Job management for REST services messages - JMR 306
Logman messages - BHX . . . . . . . . . 102 Job definition notify service messages - JNT . . . 307
Schedulr messages - BHZ . . . . . . . . . 103 Object management messages - JOM . . . . . 308
Composer messages - BIA . . . . . . . . . 106 Planner messages - JPL . . . . . . . . . . 320
Scheduling language parser messages - BIB . . . 119 Job Submission Description Language editor
Compiler messages - BID . . . . . . . . . 130 messages - JSD . . . . . . . . . . . . . 338
General and miscellaneous messages - BII . . . . 134 Job definition service messages - JSV . . . . . 343

© Copyright IBM Corp. 2001, 2009 iii


Symphony file processing messages - JSY . . . . 344 Tivoli Workload Scheduler Bridge messages - TSA 421
z/OS Connector messages - JZC . . . . . . . 349 Time scheduler - TSS . . . . . . . . . . . 425
z/OS Connector installation messages - JZI . . . 351 Tivoli Dynamic Workload Console messages - UI 434
Message logger plug-in messages - MSL . . . . 388 Tivoli Dynamic Workload Console message set
Mail sender plug-in messages - MSP . . . . . 389 ranges . . . . . . . . . . . . . . . 434
Plug-in manager messages - PMG . . . . . . 390 User interface messages . . . . . . . . . 435
Resource advisor agent - RAA. . . . . . . . 391 Event management messages . . . . . . . 507
Resource Advisor EJB messages - RAE . . . . . 392 Modelling messages . . . . . . . . . . 509
Plan extractor messages - REP . . . . . . . . 398 Ajax messages . . . . . . . . . . . . 517
Resource repository messages - RRP. . . . . . 400 Table messages . . . . . . . . . . . . 518
Resource advisor agent cache messages - RSE . . 407 Graphical functions messages . . . . . . . 519
Job repository data access object messages - SED 408 Plug-in validator messages - VAL . . . . . . 521
Utility messages - SUL . . . . . . . . . . 409
Action plug-in messages - TAP . . . . . . . 411 Notices . . . . . . . . . . . . . . 525
EIF event management messages - TEL. . . . . 412 Trademarks . . . . . . . . . . . . . . 526
Tivoli Enterprise Portal integration messages - TEP 413
Mailbox messages - TMB . . . . . . . . . 418
Index . . . . . . . . . . . . . . . 529
Time planner messages - TPL . . . . . . . . 419
Tivoli Provisioning Manager messages - TPM . . 420

iv IBM Tivoli Workload Scheduler: Messages


List of tables
1. Messages, by subcomponent code . . . . . 4 3. Tivoli Dynamic Workload Console error and
2. Messages, by subcomponent name . . . . . 7 warning messages code ranges. . . . . . 434

© Copyright IBM Corp. 2001, 2009 v


vi IBM Tivoli Workload Scheduler: Messages
About this publication
IBM® Tivoli® Workload Scheduler: Messages provides help for error and warning
messages issued by the main components of IBM Tivoli Workload Scheduler (often
called the engine), and the Tivoli Dynamic Workload Console.

It does not include details of the error or warning messages that are issued by the
installation, either of the engine components or of the Tivoli Dynamic Workload
Console. These can be found in the Tivoli Workload Scheduler: Planning and
Installation Guide.

If the information does not sufficiently explain the situation you have encountered,
you should consult the Tivoli Workload Scheduler: Troubleshooting Guide, which has
extended error scenarios for many situations, as well as information about
diagnostic tools and how to obtain support.

What is new in this release


For information about the new or changed functions in this release, see Tivoli
Workload Automation: Overview.

| For information about the APARs that this release addresses, see the Tivoli
| Workload Scheduler Download Document at http://www.ibm.com/support/
| docview.wss?rs=672&uid=swg24024804, and Tivoli Dynamic Workload Console
| Download Documents at http://www.ibm.com/support/docview.wss?rs=672
| &uid=swg24024805.

What is new in this publication


This section describes what has changed in this publication since version 8.5.

In this publication, sections have been added for messages from all new functions,
such as those related to the Tivoli dynamic workload broker.

Contrary to the practice in other publications, new or changed messages are not
highlighted with change bars. This is because the information here is used purely
for reference, and information indicating that a message is new or changed is not
going to be useful to you in understanding what has occurred, and how you
should proceed.

Who should read this publication


This publication is designed to help users understand any error or warning
messages they encounter while working with Tivoli Workload Scheduler or the
Tivoli Dynamic Workload Console.

It does not include details of the error or warning messages that are issued by the
installation, either of the engine components or of the Tivoli Dynamic Workload
Console. These can be found in the Tivoli Workload Scheduler: Planning and
Installation Guide.

The help consists of an explanation of what has happened (where the message
itself requires further explanation), the action that the system has taken, and the
© Copyright IBM Corp. 2001, 2009 vii
Who should read

response that the user must provide. These details do not appear online with the
message texts, and are documented only in this publication.

Publications
Full details of Tivoli Workload Scheduler publications can be found in Tivoli
Workload Automation: Publications. This document also contains information on the
conventions used in the publications.

A glossary of terms used in the product can be found in Tivoli Workload Automation:
Glossary.

Both of these are in the Information Center as separate publications.

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 full information with respect to the Tivoli Dynamic Workload Console, see the
Accessibility Appendix in the Tivoli Workload Scheduler: User's Guide and Reference,
SC32-1274.

For full information with respect to the Job Scheduling Console, see the
Accessibility Appendix in the Tivoli Workload Scheduler: Job Scheduling Console User’s
Guide.

Tivoli technical training


For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:

http://www.ibm.com/software/tivoli/education

Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
Online
Go to the IBM Software Support site at http://www.ibm.com/software/
support/probsub.html and follow the instructions.
IBM Support Assistant
The IBM Support Assistant (ISA) is a free local software serviceability
workbench that helps you resolve questions and problems with IBM
software products. The ISA provides quick access to support-related
information and serviceability tools for problem determination. To install
the ISA software, go to http://www.ibm.com/software/support/isa.
Troubleshooting Guide
For more information about resolving problems, see the problem
determination information for this product.

viii IBM Tivoli Workload Scheduler: Messages


For more information about these three ways of resolving problems, see the
appendix on support information in Tivoli Workload Scheduler: Troubleshooting Guide.

About this publication ix


x IBM Tivoli Workload Scheduler: Messages
Chapter 1. Introduction to messages
This publication provides help for error or warning messages that are encountered
while working with Tivoli Workload Scheduler or the Tivoli Dynamic Workload
Console.

It does not include details of the error or warning messages that are issued by the
installation, either of the engine components or of the Tivoli Dynamic Workload
Console. These can be found in the Tivoli Workload Scheduler: Planning and
Installation Guide.

This introductory chapter is divided into the following sections:


v “What is new in the messages” describes how the messages have been improved
in this version of the product.
v “How to find a message” on page 2 tells you how to find the message or
messages you are interested in.
v “IBM Tivoli message format” on page 10 describes the IBM Tivoli message
format used by Tivoli Workload Scheduler, telling you how the message codes
are constructed and how the different categories of message help can be used. It
also includes an explanation of how old message codes map to the new codes.
The second chapter contains the messages, each message set being in a separate
section. Only messages with message help are documented in this guide. For
messages without help, if you have any problems understanding the message or
are not sure how to resolve the problems that they indicate, contact IBM Software
Support for assistance.

Note: This guide does not contain any details of Informational messages, as they
are complete within themselves, and do not need further explanation.

What is new in the messages


Of the messages documented in this section, some are new messages and some
have been improved since previous versions.

All of this has the following implications:


New messages texts are different
The changes to the message texts mean that many messages are different in
version 8.5.1 than in some previous versions of Tivoli Workload Scheduler,
and in some cases the differences are substantial. The improved text better
describes the impact of the condition that provoked the message because
the message text contains more information.

Note: None of these messages has changed meaning - all that has changed
is the wording of the message.
New messages are only at new or upgraded workstations
The new versions of the messages are only available at workstations that
you have upgraded to version 8.5.1, or where you have made a fresh
installation of version 8.5.1. Messages at other workstations, and in

© Copyright IBM Corp. 2001, 2009 1


What is new in the messages

particular, messages at z/OS® workstations in an end-to-end environment,


are at the level of the version of Tivoli Workload Scheduler on that
workstation.
Message help is more useful
The message help information has been changed so that in cases where the
problem can be corrected by an operator action, a better explanation of the
problem is provided and there is an improved list of steps to take. The list
starts by checking for, and dealing with, the most common cause, and
leads you, if this is not the answer, to the less common causes.
For those messages where you need to seek assistance from IBM Software
Support, the help information says so in a direct and explicit way, so that
you do not spend time trying to resolve problems that are caused by
internal errors.
New message help is applicable to all versions
For all changed messages, the message help can be used for problem
resolution in all versions of Tivoli Workload Scheduler that are compatible
with version 8.5.1. On workstations that have not yet been upgraded to
version 8.5.1, or z/OS workstations in an end-to-end environment where
an upgrade is not available, look up the message code first in this guide,
remembering that the message text does not correspond, and then use all
the information in the new message text and message help to solve the
problem.
If you cannot find a message from a previous version in this publication, it
means that it is no longer being used, and has been removed from the
current message set. In this event, check earlier versions of this publication
for the message help.
No change bars used in this guide
Change bars have not been used to highlight these changes in this guide
because their presence for every message would not have been useful.

How to find a message


You can find a message in one of the following three ways:
Look for a specific message
The messages are presented in separate sections for each subcomponent
code (message set) in alphabetic order of subcomponent codes. To look for
a particular message use the page headers to locate it.
For example, to find message AWSBHT001E, use the headers on each page as
in a dictionary to find the message. This message is documented on page
58.
Look for a set of messages having a specific subcomponent code
Consult the table of subcomponents in “Message sets in subcomponent
code order” on page 4, which is ordered by message subcomponent code. In
addition, for the Tivoli Dynamic Workload Console, consult “Tivoli
Dynamic Workload Console message set ranges” on page 434 where the
ranges of message codes used by the console are explained.
For example, if you want to find the messages for subcomponent code
BHT, locate ″BHT″ in Table 1 on page 4 and turn to the indicated page.
This message set is documented on page 58.
Look for a set of messages for a named subcomponent
Consult the table of subcomponents in “Message sets in subcomponent

2 IBM Tivoli Workload Scheduler: Messages


How to find a message

name order” on page 7, which is ordered by subcomponent name. In


addition, for the Tivoli Dynamic Workload Console, consult “Tivoli
Dynamic Workload Console message set ranges” on page 434 where the
ranges of message codes used by the console are explained.
For example, if you want to find the messages for subcomponent batchman,
locate ″batchman″ in Table 2 on page 7 and turn to the indicated page. This
message set is documented on page 58.

Note: If you cannot locate a message in this publication, it may be that no help is
available for it. If the meaning of the message is not clear, contact IBM
Software Support for assistance.

Chapter 1. Introduction to messages 3


How to find a message

Message sets in subcomponent code order


Table 1. Messages, by subcomponent code
Subcomponent code Subcomponent (message set) Page number
AEM Event management 14
AHL Action helper 15
ALR Allocation repository 16
AUD Audit service 17
BAT Event counter 19
BCT Utility programs 22
BCU SSL (symaccs) 23
BCV Mailman 24
BCW Writer 27
BCX Monman 28
BCZ Dload 31
BDB Scribner 33
BDC NetView/OpenView 34
BDG Downloader 35
BDJ Appserverman 39
BDW Jobman 41
BDX Jobtable access 43
BDY Mailbox 45
BEC Report headers and subheaders 46
BEE Parms 47
BEG Ftbox 48
BEH Web library 49
BEI Users program 56
BHT Batchman 58
BHU Conman 61
BHV Stageman 93
BHW Object parsing 99
BHX Logman 102
BHZ Schedulr 103
BIA Composer 106
BIB Scheduling language parsing 119
BID Compiler 130
BII General and miscellaneous 134
BIN Plan libraries 135
BIO Comm_api 138
BIP Connector (JSS/mapper layer) 140
BIS Customize (messages maintained for 141
backwards compatibility)
BIY Demo scripts 148

4 IBM Tivoli Workload Scheduler: Messages


How to find a message

Table 1. Messages, by subcomponent code (continued)


Subcomponent code Subcomponent (message set) Page number
BJG Router 149
BJH Migration 151
BWX dataxtract 153
CAL Calendar 155
CCM CCMDB integration 157
CDM Change and configuration management 158
database
CDW Clustering 160
CLI Dynamic workload broker command line 166
DDW Std utilities 172
®
DEB IPC utilities (UNIX ) - SSL 173
DEC Events file 178
DEJ Security 180
DEK Miscellaneous commands 190
DEM Workstation parser 192
DEQ FIFO 202
DEU Utilities library list 203
DEV TIS library 204
DFH Condition expression parsing 205
ECM Event Configuration 207
EDW Netman 208
EJE Enterprise Java Bean 215
ERB Event rule builder 218
ERP Event rule parser 219
ETO Object monitor plug-in 221
EVP Event processing 222
EWL Enterprise workload manager 223
FMP File monitor plug-in 225
®
FWD Tivoli Enterprise Console event forwarder 226
plug-in
GAP Generic action plug-in 227
GEP Generic event plug-in 228
GTW Gentwsevn 229
ICA Calendar 231
ITA Job management 232
JBN Job definition base notify service 241
JCL Command line 242
JCO Connectors 257
JCS Common services 257
JDB Common objects 282

Chapter 1. Introduction to messages 5


How to find a message

Table 1. Messages, by subcomponent code (continued)


Subcomponent code Subcomponent (message set) Page number
JDD Job definition jobdef service 287
JDE Job dispatcher 288
JEJ WebSphere Java 2 Enterprise Edition job 304
executor for CAS
JMR Job management for REST services 306
JNT Job definition notify service 307
JOM Object management 308
JPL Planner 320
JSD Job Submission Description Language 338
editor
JSV Job definition service 343
JSY Symphony object management 344
JZC z/OS Connector 349
JZI z/OS Connector installation 351
MSL Message logger plug-in 388
MSP Mail sender plug-in 389
PMG Plug-in manager 390
RAA Resource advisor agent 391
RAE Resource advisor EJB 392
REP Plan extractor 398
RRP Resource repository 400
RSE Resource advisor agent cache 407
SED Job repository data access object 408
SUL Utility 409
TAP Action plug-in 411
TEL EIF event management 412
TEP Tivoli Enterprise Portal integration 413
TMB Mailbox processing 418
TPL Time planner 419
TPM Tivoli Provisioning Manager 420
TSA Tivoli Workload Scheduler Bridge 421
TSS Time scheduler 425
UI Tivoli Dynamic Workload Console - see 434
“Tivoli Dynamic Workload Console
message set ranges” on page 434 for details
of message ranges used.
VAL Plug-in validator 521

6 IBM Tivoli Workload Scheduler: Messages


How to find a message

Message sets in subcomponent name order


Table 2. Messages, by subcomponent name
Subcomponent (message set) Subcomponent code Page number
Action helper AHL 15
Action plug-in TAP 411
Allocation repository ALR 16
Appserverman BDJ 39
Audit service AUD 17
Batchman BHT 58
Calendar CAL 155
Calendar ICA 231
CCMDB integration CCM 157
Change and configuration management CDM 158
database
Clustering CDW 160
Command line JCL 242
Common objects JDB 282
Common services JCS 278
Compiler BID 130
Composer BIA 106
Condition expression parsing DFH 205
Conman BHU 61
Connector BIP 140
Connectors JCO 257
Customize BIS 141
Dataxtract BWX 153
Demo scripts BIY 148
Downloader BDG 35
Dynamic workload broker command line CLI 166
Dynamic Workload Console UI 434
EIF event management TEL 412
Enterprise Java Bean EJE 215
Enterprise workload manager EWL 223
Event counter BAT 19
Event management AEM 14
Event Configuration ECM 207
Event processing EVP 222
Event rule builder ERB 218
Event rule parser ERP 219
Events file DEC 178
FIFO DEQ 202
File monitor plug-in FMP 225

Chapter 1. Introduction to messages 7


How to find a message

Table 2. Messages, by subcomponent name (continued)


Subcomponent (message set) Subcomponent code Page number
Ftbox BEG 48
Generic action plug-in GAP 227
Generic event plug-in GEP 228
Gentwsevn GTW 229
IPC utilities (UNIX) - SSL DEB 173
Job definition base notify service JBN 241
Job definition jobdef service JDD 287
Job definition notify service JNT 307
Job definition service JSV 343
Job dispatcher JDE 288
Jobman BDW 41
Job management ITA 232
Job management for REST services JMR 306
Job repository data access object SED 408
Job Submission Description Language JSD 338
editor
Jobtable access BDX 43
JSS/mapper layer BIP 140
Logman BHX 102
Mail sender plug-in MSP 389
Mailbox BDY 45
Mailbox processing TMB 418
Mailman BCV 24
Message logger plug-in MSL 388
Miscellaneous commands DEK 190
Monman BCX 28
Netman EDW 208
®
NetView BDC 34
Object management JOM 308
Object monitor plug-in ETO 221
Object parsing BHW 99
OpenView BDC 34
Parms BEE 47
Plan extractor REP 398
Plan libraries BIN 135
Planner JPL 320
Plug-in manager PMG 390
Plug-in validator VAL 521
Report headers and subheaders BEC 46
Resource advisor agent RAA 391

8 IBM Tivoli Workload Scheduler: Messages


How to find a message

Table 2. Messages, by subcomponent name (continued)


Subcomponent (message set) Subcomponent code Page number
Resource advisor agent cache RSE 407
Resource advisor EJB RAE 392
Resource repository RRP 400
Router BJG 149
Schedulr BHZ 103
Scheduling language parsing BIB 119
Scribner BDB 33
Security DEJ 180
SSL DEB 173
SSL (symaccs) BCU 23
Stageman BHV 93
Std utilities DDW 172
Symphony object management JSY 344
Time scheduler TSS 425
Time planner TPL 419
TIS library DEV 204
Tivoli Dynamic Workload Console UI 434
Tivoli Enterprise Console event forwarder FWD 226
plug-in
Tivoli Enterprise Portal integration TEP 413
Tivoli Provisioning Manager TPM 420
Tivoli Workload Scheduler Bridge TSA 421
Users program BEI 56
Utility SUL 409
Utility programs BCT 22
Utilities library list DEU 203
Web library BEH 49
WebSphere Java 2 Enterprise Edition job JEJ 304
executor for CAS
Workstation parser DEM 192
Writer BCW 27
z/OS Connector messages JZC 349
z/OS Connector installation messages JZI 351

Chapter 1. Introduction to messages 9


Message format

IBM Tivoli message format


This section explains the format of the message that is displayed on your screen or
written in a log file. All messages have a message number and a message text.
Many of the error and warning messages also have help. Only messages with
message help are documented in this part of the guide. The help consists of an
explanation of the message, a description of what the system does, and
information about what you must do to resolve the problem.

These items are described in more detail in the following sections.

Message number
Tivoli Workload Scheduler message numbers (codes) have the following format:
AWS<component_code><numeric_identifier><severity>

where the parts of the message are as follows:


AWS The product prefix. This value is used for all Tivoli Workload Scheduler
messages, except those of the z/OS Connector, which use EQQ (the
product code for IBM Tivoli Workload Manager for z/OS).
<component_code>
The three-digit (occasionally two-digit) alphabetic code for the Tivoli
Workload Scheduler component, for example ″BAT″. The values used by
Tivoli Workload Scheduler are listed in “Message sets in subcomponent
code order” on page 4.
<numeric_identifier>
A three-digit (occasionally four-digit) numeric identifier that is unique
within any combination of prefix and component code.
<severity>
The severity indicator, as follows:
I Informational: Informational messages provide users with
information or feedback about normal events that have occurred or
are occurring, or request information from users in cases where the
outcome is not negative, regardless of the response.
Examples:
v The status request is processing.
v The files were successfully transferred.
v Do you want to save your output in file a or in file b?

Note: Informational messages issued by Tivoli Workload Scheduler


are not documented in this guide, as they are complete in
themselves and require no further information or
explanation. This also applies to informational messages
giving the usage of the product’s commands – if you require
more information than is given on the screen, refer to Tivoli
Workload Scheduler: User's Guide and Reference.
W Warning: Warning messages indicate that potentially undesirable
conditions have occurred or could occur, but the program can
continue. Warning messages often ask users to make decisions
before processing continues.
Examples:

10 IBM Tivoli Workload Scheduler: Messages


Message format

v The replay table could not be sent. The link to Agent_name


proceeds with a reduced replay protocol.
v A file already exists with the same name. Do you want to
overwrite this file?
E Error: Error messages indicate problems that require intervention
or correction before the program can continue.
Examples:
v The specified file could not be found.
v You are out of space on the x drive. The file cannot be saved to
this drive.

An example of an error message number is as follows:


AWSBAT003E

Message text
Every attempt has been made to represent the message text exactly as it appears to
the user in the displayed or written message. Any differences that occur are
usually occasioned by the different layout of the book (in two columns) with
respect to the message display panel or log.

Where the system has included variable information in the message text, this
variable information is represented in this guide by an italicized label, describing
the type of information referred to by the variable.

For example, if the message text that appears on your screen is as follows:
The replay table could not be sent.
The link to TRC8470 proceeds with a reduced replay protocol.

the message text shown in the guide would be as follows:


The replay table could not be sent.
The link to Agent_name proceeds with a reduced replay protocol.

In this case the label Agent_name tells you that the information that is inserted by
the system is the name of the agent which could not receive the replay table.

Message help
In Chapter 2, “Message help,” on page 13 you can find help for many of the more
important error and warning messages. This help provides the following:
Explanation
An explanation, where necessary, of the message text.
System action
A description of what the system or process does as a result of the
condition that caused the message.
Operator response
What you must do in response to the condition that caused the message.
Often you are able to resolve such conditions yourself, but sometimes you
are asked to contact IBM Software Support.
See also
A reference to any Tivoli Workload Scheduler publication that might give
you assistance with understanding or resolving the problem.

Chapter 1. Introduction to messages 11


Message format

Locating message help in this guide


See “How to find a message” on page 2 for a description of how to find the
message or message set for which you require help information.

12 IBM Tivoli Workload Scheduler: Messages


Chapter 2. Message help
This chapter contains message help for many of the messages issued by the Tivoli
Workload Scheduler engine and command line, and the Tivoli Dynamic Workload
Console. The messages are organized in alphabetical order of message within
alphabetical order of subcomponent (message set). Each subcomponent is in a
separate section. For a description of how to search for specific messages or sets,
see “How to find a message” on page 2.

© Copyright IBM Corp. 2001, 2009 13


AWSAEM001E • AWSAEM005W

Event management messages - AEM


This section lists error and warning event management messages that could be
issued.

The message component code is AEM.

Scheduler administrator to verify the Tivoli Workload


AWSAEM001E An internal error has occurred. The
Scheduler installation.
property
"com.ibm.tws.event.configuration.manager"
is not found in the
TWSConfig.properties file.
Explanation: The class that manages the event
processor must be defined in the TWSConfig.properties
file. You should use the
com.ibm.tws.event.configuration.manager key to define
it.
System action: The operation cannot be performed.
Operator response: Contact IBM Software Support for
assistance.

AWSAEM002E An internal error has occurred while


loading or initializing the DAO factory
class "factory_class".
Explanation: See message.
factory_class identifies the name of a DAO factory class
as defined in the TWSConfig.properties file.
System action: The operation cannot be performed.
Operator response: Contact the Tivoli Workload
Scheduler administrator to verify the Tivoli Workload
Scheduler installation.

AWSAEM003E Unable to execute the operation


because this workstation is not the
Event Processor Manager.
Explanation: If the workstation is not the Event
Processor Manager, is not possible to run the event
manager operations: starteventprocessor and
stopeventprocessor.
System action: The operation cannot be performed.
Operator response: Contact the Tivoli Workload
Scheduler administrator to verify the Tivoli Workload
Scheduler installation.

AWSAEM005W This workstation "workstation" is not


the Event Processor Manager.
Explanation: See message.
workstation identifies the active workstation.
System action: The operation cannot be performed.
Operator response: Contact the Tivoli Workload

14 IBM Tivoli Workload Scheduler: Messages


AWSAHL001E

Action helper messages - AHL


This section lists error and warning action helper messages that could be issued.

The message component code is AHL.

AWSAHL001E The action plug-in "plug-in_name" is


not valid.
Explanation: The loaded plug-in "plug-in_name" is not
valid: either no plug-in has been loaded or it is not the
action plug-in.
System action: The operation cannot be performed.
Operator response: Redefine the trigger rule to invoke
the correct action plug-in.

Chapter 2. Message help 15


AWKALR001E • AWKALR081E

Allocation repository messages - ALR


This section lists error and warning allocation repository messages that could be
issued.

The message component code is ALR.

AWKALR001E Unable to create the JSDL string from AWKALR007E Unable to create the EPR from the
the SDO. string.
Explanation: See message text. Explanation: See message text.
System action: The operation is not performed. System action: The operation is not performed.
Operator response: The error message points the user Operator response: The error message points the user
to the root cause of the problem. to the root cause of the problem.

AWKALR002E Unable to create the EPR string from AWKALR081E Unable to create an allocation record
the SDO. in the allocation repository database.
Explanation: See message text. Explanation: See message text.
System action: The operation is not performed. System action: None
Operator response: The error message points the user Operator response: Check the error log for
to the root cause of the problem. information about cause of the database access failure.

AWKALR003E No resources are available for


deletion for allocation ID:"allocationID".
Explanation: See message text.
System action: The operation is not performed.
Operator response: The error message points the user
to the root cause of the problem.

AWKALR004E No allocation is available for deletion


for allocation ID:"allocationID".
Explanation: See message text.
System action: The operation is not performed.
Operator response: The error message points the user
to the root cause of the problem.

AWKALR005E Unable to find any resources for


allocation ID:"allocationID".
Explanation: See message text.
System action: None
Operator response: Check the allocation ID and try
again

AWKALR006E Unable to create the JSDL from the


string.
Explanation: See message text.
System action: The operation is not performed.
Operator response: The error message points the user
to the root cause of the problem.

16 IBM Tivoli Workload Scheduler: Messages


AWKAUD050W • AWKAUD104E

Audit service messages - AUD


This section lists error and warning audit service messages that could be issued.

The message component code is AUD.

AWKAUD050W The audit property setting AWKAUD100E Unable to find the audit
"property_name" is not specified or is configuration file "audit_file_path". Using
blank in the auditing configuration file. the default configuration settings.
Using the default value: "default_value".
Explanation: The auditing configuration file does not
Explanation: See message text. exist or is not readable. Default configuration settings
are used.
System action: The operation is performed using the
default value. System action: The operation is performed using the
default settings.
Operator response: None.
Operator response: Check that the audit configuration
file exists and that is readable. Create a new audit
AWKAUD051W The directory name specified in the
configuration file if it is missing.
audit property "property_name" is not
valid. Using default value:
"default_value". AWKAUD101E Unable to instantiate the "audit_type"
event type.
Explanation: See message text.
Explanation: The audit service is unable to instantiate
System action: The operation is performed using the
the specified event type. The class path might be
default value.
corrupted.
Operator response: None.
System action: The operation is not performed.
Operator response: Verify the installation and check
AWKAUD052W The audit file prefix "prefix_value" is
whether the jar files have been deleted.
not valid or the auditing file path is too
long. Using the default value
"default_value". AWKAUD102E Unable to instantiate the
"provider_name" Auditing Event Provider.
Explanation: See message text.
Explanation: The audit service is trying to instantiate
System action: The operation is performed using the
an unknown or unsupported Auditing Event Provider.
default value.
System action: The operation is not performed.
Operator response: None.
Operator response: Check whether an unsupported
Auditing Event Provider is specified in the audit
AWKAUD053W The audit file prefix is not specified
configuration file.
or is blank. Using the default value
"default_value".
AWKAUD103E Unable to log the "event_type" audit
Explanation: See message text.
event type.
System action: The operation is performed using the
Explanation: The audit service is unable to process
default value.
events of the specified type.
Operator response: None.
System action: The operation is not performed.
Operator response: Check whether an unsupported
AWKAUD054W The audit property "property_name" is
auditing event consumer is specified in the audit
not valid, is negative, or exceeds the
configuration file.
maximum supported value. Using the
maximum value as default default_value.
AWKAUD104E Unable to process the "event_type"
Explanation: See message text.
audit event type.
System action: The operation is performed using the
Explanation: The audit service is unable to process
default value.
events of the specified type.
Operator response: None.
System action: The operation is not performed.

Chapter 2. Message help 17


AWKAUD105E

Operator response: The file system might be full or


the audit log file is not write-protected.

AWKAUD105E Unable to use the directory specified


for audit logs. The specified path and
the filename might exceed the maximum
length for files in the current operating
system. Using: "new_file_location".
Explanation: The audit service is unable to process
events of the specified type.
System action: The operation is performed using the
file name and path specified in the message.
Operator response: The file system might be full or
the auditing log file is write-protected.

18 IBM Tivoli Workload Scheduler: Messages


AWSBAT002I • AWSBAT012E

Event counter messages - BAT


This section lists error and warning messages that could be issued by the event
counter used by the fault-tolerant switch manager feature.

The message component code is BAT and the old message set code is 019 in the
″maestro″ message catalog.
Operator response: Restart the process. If the problem
AWSBAT002I The event counter is successfully
persists, contact IBM Software Support for assistance.
initializing, workstation counter on the
hard drive has been updated : message See also: The event counter troubleshooting section for
more information.
Explanation: While initializing its event counter, the
process found that the file on the hard disk drive
pointed to an old Symphony run number. The file has AWSBAT008E The process could not retrieve a value
been updated. This message is shown once for each from the event counter.
JnextPlan.
Explanation: This is an internal error. Either the event
counter is corrupted or the workstation identified by
AWSBAT003E The event counter failed to initialize the event counter does not exist.
for the following reason: "error_message"
System action: The event counter and the Enable
Explanation: The event counter failed to initialize for switch fault tolerance feature both stop. The process
the reason detailed in the error_message. continues.
System action: The Enable switch fault tolerance feature Operator response: Restart the process. If the problem
is no longer functioning. The process continues. persists, contact IBM Software Support for assistance.
Operator response: Correct the reported problem and See also: The event counter troubleshooting section for
restart the process. more information.
See also: The event counter troubleshooting section for
more information. AWSBAT011W The event counter received a message
with a lower ID-number (ID_number)
than a message previously received from
AWSBAT004E The event counter has failed after
the same workstation.
encountering the following problem:
"error_message" Explanation: The message might be displayed while
switch manager is running or after an error has
Explanation: The event counter failed for the reason
occurred with Tivoli Workload Scheduler.
detailed in the error_message.
System action: The event counter is updated to use
System action: The event counter and the Enable
the new value. The process continues.
switch fault tolerance feature both stop. The process
continues. Operator response: None.
Operator response: Correct the reported problem and
restart the process. AWSBAT012E The process could not write the
received ID-number to the event
See also: The event counter troubleshooting section for
counter.
more information.
Explanation: This is an internal error.
AWSBAT005E The event counter failed to initialize System action: The process continues. Events routed
while attempting to load its table with through this workstation from the moment this
workstation names from the Symphony message is displayed until the moment the process is
file. The following gives more details of restarted are ignored by the Enable switch fault tolerance
the error: system_error. feature.
Explanation: This is an internal error. The event Operator response: Restart the process. If the problem
counter initialization failed for the indicated persists, contact IBM Software Support for assistance.
system_error.
See also: The event counter troubleshooting section for
System action: The event counter and the Enable more information.
switch fault tolerance feature both stop. The process
continues.

Chapter 2. Message help 19


AWSBAT015E • AWSBAT057E

See also: The event counter troubleshooting section for


AWSBAT015E The event counter could not be saved
more information.
because the following error occurred:
error_message
AWSBAT055E A new event counter file could not be
Explanation: The event counter table could not be
created, and there is no saved file.
saved for the reason detailed in the error_message.
Explanation: There is no saved version of the event
System action: The Enable switch fault tolerance feature
counter file, but when the process attempted to create a
stops. The process continues.
file, it failed.
Operator response: Correct the problem reported, and
System action: The process continues. Events routed
restart the process.
through this workstation since the last JnextPlan up to
See also: The event counter troubleshooting section for when the process is restarted are ignored by the Enable
more information. switch fault tolerance feature.
Operator response: Check the following:
AWSBAT053E The run-number in the Symphony file v Does an event counter file exist? If it does, contact
is higher than the current Symphony IBM Software Support for assistance.
run-number.
v Is there enough free disk space available in the
Explanation: Either writer or mailman found that the product’s installation directory to create the file? If
Symphony file on the hard disk drive referred to a higher not, free up more space.
Symphony run number than that stored in the process. v Are the security permissions on the installation
There are two possibilities: directory correct? If not, correct the permissions.
1. An occurrence of JnextPlan took place while the
process was running, without the process being Restart the process.
restarted
2. The Symphony file or the EventCounter file has been If the problem persists, contact IBM Software Support
changed manually or by a process outside Tivoli for assistance.
Workload Scheduler.
System action: The process continues. Events routed AWSBAT056E The following operating system error
through this workstation since the last JnextPlan up to has affected the functionality of the
when the process is restarted are ignored by the Enable process: "error_code".
switch fault tolerance feature.
Explanation: The operating system error indicated by
Operator response: The operator response depends on error_code has occurred, and the process cannot
the cause of the error: continue with full functionality.
v If the cause of the error was 1), an internal error has System action: The Enable switch fault tolerance feature
occurred; contact IBM Software Support for stops. The process continues.
assistance.
Operator response: Fix the operating system error.
v If the cause of the error was 2), either reinstate the
Restart the process.
original version of the Symphony file or delete the
EventCounter file (<InstallDir>\ftbox\EventCounter) See also: The event counter troubleshooting section for
before restarting the process. more information.
See also: The event counter troubleshooting section for
more information. AWSBAT057E The event counter file is corrupt.
Explanation: The process is trying to use the saved
AWSBAT054E The saved event counter file could not version of the event counter file, but it is corrupted.
be opened.
System action: The process continues. Events routed
Explanation: A saved version of the event counter through this workstation since the last JnextPlan up to
exists, but the process was not able to open the file. when the process is restarted are ignored by the Enable
switch fault tolerance feature.
System action: The process continues. Events routed
through this workstation since the last JnextPlan up to Operator response: Delete the event counter file and
when the process is restarted are ignored by the Enable restart the process.
switch fault tolerance feature.
See also: The event counter troubleshooting section for
Operator response: Delete the event counter file and more information.
restart the process. If the problem persists, contact IBM
Software Support for assistance.

20 IBM Tivoli Workload Scheduler: Messages


AWSBAT058E • AWSBAT059E

AWSBAT058E The event counter failed to initialize.


Explanation: Some fields hold incorrect values.
System action: The process continues. Events routed
through this workstation since the last JnextPlan up to
when the process is restarted are ignored by the Enable
switch fault tolerance feature.
Operator response: Restart the process. If the problem
persists, contact IBM Software Support for assistance.
See also: The event counter troubleshooting section for
more information.

AWSBAT059E The event counter failed to initialize.


Explanation: Some fields are empty.
System action: The process continues. Events routed
through this workstation since the last JnextPlan up to
when the process is restarted are ignored by the Enable
switch fault tolerance feature.
Operator response: Restart the process. If the problem
persists, contact IBM Software Support for assistance.
See also: The event counter troubleshooting section for
more information.

Chapter 2. Message help 21


AWSBCT305E • AWSBCT888E

Utility program messages - BCT


This section lists utility program error and warning messages that could be issued.

The message component code is BCT and the old message set code is 071 in the
″maestro″ message catalog.

AWSBCT305E The delete utility is unable to


continue because of the following
unexpected Windows error accessing the
user details: error_description.
Explanation: The delete utility is unable to retrieve the
name of the current user. There might be a problem of
permissions if you are not logged on as Administrator.
error_description is the error returned by the Windows
API NetUserGetInfo.
System action: The delete utility cannot proceed.
Operator response: If you are not already logged on
as Administrator, log on as Administrator and re-issue
the command.
If you are logged on as Administrator, contact IBM
Software Support for assistance.

AWSBCT888E Cpuinfo cannot show information


about workstation "workstation" because
is not included in the current Symphony
file.
Explanation: See message.
workstation identifies the workstation which is the
subject of the cpuinfo utility, but which is not in the
Symphony file.
System action: Cpuinfo stops without producing any
output.
Operator response: Check that you have typed the
workstation name correctly. If you find an error, correct
it and retry the utility.
If you have typed the name correctly, and were
expecting the workstation to be in the plan, check the
job or job stream in the plan that you thought was
using the workstation.

22 IBM Tivoli Workload Scheduler: Messages


AWSBCU007E • AWSBCU150W

SSL messages (symaccs) - BCU


This section lists symaccs error and warning messages that could be issued when
using SSL.

The message component code is BCU and the old message set code is 072 in the
″maestro″ message catalog.

AWSBCU007E An error has occurred in the common


area used to access the Symphony file.
Explanation: The error is probably due to a memory
corruption. It is a symaccs error.
System action: The program might stop.
Operator response: If Tivoli Workload Scheduler has
not yet stopped, stop and restart it. If the error occurs
again contact IBM Software Support for assistance.
See also: The chapter in this guide on ’Symphony file
corruption’.

AWSBCU150W SSL authorization is required to


connect to the following workstation
workstation_name
Explanation: See message. The most common reason
for this error is an inconsistent Security Level. For
example, the workstation where mailman is running
could be enabled for SSL but the target workstation is
not. workstation_name is the name of the workstation
you cannot connect to.
System action: The program proceeds to process other
workstations.
Operator response: Use composer or the Job
Scheduling Console to verify the security level of the
Workstation that cannot communicate. Enable or
disable SSL as appropriate and where appropriate, to
ensure that both this workstation and the target
workstation have compatible SSL settings.
See also: See the chapter on setting security in the
Planning and Installation Guide for more information
about SSL.

Chapter 2. Message help 23


AWSBCV012E • AWSBCV036W

Mailman messages - BCV


This section lists error and warning messages that could be issued by the mailman
component.

The message component code is BCV and the old message set code is 073 in the
″maestro″ message catalog.

AWSBCV012E Mailman cannot read a message in a AWSBCV035W Mailman was unable to link to
message file. The following gives more workstation: workstation_name; the
details of the error: "error_message". messages are written to the PO box.
Explanation: Mailman was unable to read a message Explanation: Mailman was unable to link to the
from its local mailbox: Mailbox.msg, or [Server].msg for workstation workstation_name, for an unknown reason.
a server mailman.
System action: All messages for this workstation are
error_message describes the error and includes the written to the message file in the PO box directory
operating system error message. (pobox). Mailman attempts, at a configurable interval,
to re-establish the link to the workstation. As soon it
System action: Mailman continues.
succeeds, the messages in the PO box are sent to the
Operator response: Contact IBM Software Support for workstation. Mailman proceeds.
assistance.
Operator response: If you are not expecting the
workstation to be unavailable, do the following:
AWSBCV024W Mailman has lost communication 1. Use the ping command to check the workstation’s
with the following workstation: availability. If it is now available, you can link to it
workstation_name. manually, or leave mailman to relink to it
Explanation: The writer of the workstation, identified automatically.
by workstation_name, is either busy, or is not responding 2. Verify that netman on the workstation is working,
due to communication problems. running StartUp on the workstation if it is not.

System action: No further messages are processed for 3. Verify that netman on the workstation is listening
this workstation. Mailman proceeds. on the specified netman port, by checking that the
netman port specified in the database definition is
Operator response: Use the ping command to verify the same as the port specified in the localopts file
that the workstation is accessible in the network. If you on the workstation.
are able to access the workstation, unlink and re-link
the workstation, using the conman commands unlink If you want to change the frequency with which
<workstation_name> and link <workstation_name>. mailman attempts to relink to the workstation, modify
If the problem persists, contact IBM Software Support the appropriate parameter in the localopts file.
for assistance.
If you want to attempt to relink manually to the
workstation launch the conman command link
AWSBCV025W Mailman has unlinked from <workstation_name>.
workstation: workstation_name.
Explanation: Mailman has not received a AWSBCV036W Mailman cannot link to the
communication from the workstation identified by following workstation: workstation_name
workstation_name for a period longer than its configured because it has an incompatible
time-out period, so it unlinks from the workstation. Symphony file.
System action: No further messages are processed for Explanation: Mailman encountered a problem while
this workstation. Mailman proceeds. trying to link to its parent workstation:
Operator response: Verify that the workstation is workstation_name because the workstation has an
available and working, using the ping command. If it incompatible Symphony file and needs to be initialized
is, take no action; if it is not, take whatever network first. Probably the run number of the Symphony file on
action or action at the workstation that is necessary to the workstation is less than the run number of the child
allow the connection to be remade. If you want to Symphony file.
remake the connection manually, use the conman A new Symphony file cannot be sent, because the
command link <workstation_name>. workstation mailman is trying to link to is not its
domain manager.

24 IBM Tivoli Workload Scheduler: Messages


AWSBCV040W • AWSBCV122E

System action: Mailman proceeds. 3. If the link command gives an error, investigate and
correct the reason for the error and then repeat this
Operator response: Verify that workstation_name can
step.
connect to this workstation and if it can, remove its
Symphony file. 4. Then retry the operation.

See also: The chapter in this guide on ’Symphony file


corruption’. AWSBCV102I Mailman is already linked to
workstation_name, using TCP.

AWSBCV040W Mailman cannot link to the Explanation: Mailman tries to link to


following workstation: workstation_name. workstation_name, but discovers that it is already linked,
using TCP.
Explanation: Mailman is trying to link to the
workstation: workstation_name and either the writer workstation_name is the name of workstation mailman is
service on the workstation is unavailable or the version trying to link to.
of the Tivoli Workload Scheduler at the workstation is System action: Mailman proceeds.
not compatible with the version of mailman.
Operator response: None.
System action: The operation on the workstation is
not performed. Mailman proceeds.
AWSBCV103I Mailman is already linked to
Operator response: Verify that the workstation is workstation_name, using DS.
working correctly. Verify that the version of Tivoli
Workload Scheduler on the workstation is correct, by Explanation: Mailman tries to link to
issuing the conman command v, or by using the Job workstation_name, but discovers that it is already linked,
Scheduling Console options to determine the version. using DS.
Look at the stdlist file on the workstation for more workstation_name is the name of the workstation
information about the possible causes. The file can be mailman is trying to link to.
found in the directory <InstallDir>\stdlist\logs.
System action: Mailman proceeds.
AWSBCV056I Mailman has tried to link to a Operator response: None.
workstation (workstation_name) to which
it is already linked.
AWSBCV121E Mailman cannot link to the following
Explanation: Mailman started to perform the actions workstation: workstation_name, which is a
needed to make a TCP link, but discovered that the domain manager but is running a
workstation is already linked. version prior to 6.0.

System action: Mailman proceeds. Explanation: Mailman encountered an error trying to


link to a workstation which is not running Tivoli
Operator response: None. Workload Scheduler version 6.0 or later, but is defined
as a domain manager. The link is not allowed because
AWSBCV099E Mailman has lost communication it will cause problems in the network.
with workstation: workstation_name. workstation_name is the name of the workstation
Explanation: The writer of the workstation is not mailman is trying to link to.
running or is not responding due to communication System action: Mailman proceeds.
problems.
Operator response: Install Tivoli Workload Scheduler
workstation_name is the name of the workstation that is version 6.0 or later on the indicated workstation.
not responding to mailman.
System action: Mailman stops. AWSBCV122E Mailman cannot link to workstation:
Operator response: Take the following steps: workstation_name.
1. Verify that the workstation is available by using the Explanation: There are two possible reasons:
ping command to check both if it is available and if 1. The most probable reason is that the writer on the
its answer time is acceptable. workstation is at a version prior to 6.0.
2. If the workstation is available, unlink and relink the 2. The Symphony file could be corrupt.
workstation using the conman commands unlink
<workstation_name> and link
workstation_name is the name of the workstation
<workstation_name>.
mailman is trying to link to.
System action: Mailman proceeds.

Chapter 2. Message help 25


AWSBCV124E • AWSBCV135W

Operator response: Verify the version of Tivoli


Workload Scheduler on the indicated workstation,
using the conman v command, or the Job Scheduling
Console.
v If the version is prior to 6.0, install Tivoli Workload
Scheduler version 6.0 or later on the workstation.
v If the version is 6.0 or later contact IBM Software
Support for assistance.
See also: The chapter in this guide on ’Symphony file
corruption’.

AWSBCV124E Mailman is unable to connect to


workstation workstation_name using SSL
due to an inconsistency in the Tivoli
Workload Scheduler network
configuration.
Explanation: See message. The most common reason
for this error is an inconsistent Security Level. For
example, the workstation where mailman is running
could be enabled for SSL but the target workstation is
not. workstation_name is the name of the workstation
you cannot connect to.
System action: Mailman proceeds to process other
workstations.
Operator response: Verify on the Master Domain
Manager the security level of the workstation that has
the problem. Enable or disable SSL as appropriate and
where appropriate, to ensure that both this workstation
and the target workstation have compatible SSL
settings.
See also: See the chapter on setting security in the
Planning and Installation Guide for more information
about SSL.

AWSBCV135W Mailman is in isolated state and


cannot open any outbound connection.
Explanation: This workstation is an old domain
manager that still has to perform the demotion from
domain manager to full status fault-tolerant agent.
During this phase, the old domain manager must not
connect to other agents in the network, so it was
restarted in isolated mode.
This warning explains the error that usually precedes it
in the log about a failed link attempt.
System action: Mailman proceeds. This state continues
until the switchmgr command is processed.
Operator response: Wait for the old domain manager
to process the switchmgr command and give up its
status of domain manager.
If for urgent reasons the old manager must connect
with the rest of the network, stop and restart the agent.
It restarts in a non-isolated state.

26 IBM Tivoli Workload Scheduler: Messages


AWSBCW002W • AWSBCW041E

Writer messages - BCW


This section lists error and warning messages that could be issued by the writer
component.

The message component code is BCW and the old message set code is 074 in the
″maestro″ message catalog.
Operator response: Shutdown all Tivoli Workload
AWSBCW002W Writer cannot find a valid "wr read"
Scheduler processes on the workstation. Unlink and
value in the localopts file. The value
relink the workstation after Tivoli Workload Scheduler
found is as follows: wr_read. The default
processes have been stopped.
value is used.
Explanation: The "wr_read" option in the localopts
AWSBCW041E Writer stops because it has not
file is the number of seconds that the writer process
received any incoming messages during
waits for an incoming message before checking for a
the period specified in the localopts file
termination request from netman. It is either not
for the option "wr unlink". The total cpu
specified or the wr_read value is not a valid number or
time is as follows: time
is out of range. The default value (150 seconds) is used.
Explanation: time is the total time used by the process.
wr_read is the value specified in the localopts file. A
value given here of "Unknown" means that no value System action: Writer stops.
was found in the localopts file.
Operator response: Verify that the domain manager
System action: Writer proceeds using the default (or the parent if the node is a Domain Manager) is
value. working and that there are no network problems
preventing the domain manger from contacting the
Operator response: If the default value is not what
workstation.
you require, set a valid value for the wr_read option in
the localopts file. When you have resolved whatever caused the timeout,
if the workstation is defined to autolink you need take
no further action. Otherwise, relink the workstation
AWSBCW025E Writer is started by netman with an
from the domain manager.
incorrect number of arguments.
Explanation: See message.
System action: Writer stops.
Operator response: This is an internal error. Contact
IBM Software Support for assistance.

AWSBCW037E Writer cannot initialize this


workstation because mailman is still
active.
Explanation: Writer cannot initialize this workstation
(download the Symphony file) because mailman is still
active. The parent workstation cannot send the new
version of Symphony file.
System action: Writer stops.
Operator response: Force the stop of the mailman
process with the conman command stop.

AWSBCW038E Writer needs the exclusive access to


the Symphony and Sinfonia files in
order to initialize the workstation.
Either batchman or mailman is using
one or other of the files.
Explanation: See message.
System action: Writer proceeds.

Chapter 2. Message help 27


AWSBCX001E • AWSBCX012E

Monman messages - BCX


This section lists error and warning monman messages that could be issued.

The message component code is BCX.


Operator response: Attempt to resolve the operating
AWSBCX001E An internal error has occurred.
system error. Use the limit command to see the user’s
Monman cannot read a message in a
file limits (the file limit is the ’descriptor’ line for csh
message file. The following gives more
users).
details of the error: "error_message".
If the problem is with the number of files open, take
Explanation: Monman was unable to read a message
one of the following actions, according to whether the
from its local mailbox: Monbox.msg.
problem is with the operating system limits or a user’s
error_message describes the error and includes the limits:
operating system error message. v Add the following lines to your system parameters
System action: Monman continues. file (/etc/system) and reboot the system:
set rlim_fd_max = 4096
Operator response: Contact IBM Software Support for
assistance. 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
AWSBCX002E An internal error has occurred.
environment (the following is correct for a csh user):
Monman could not set the termination
signal handling routines. The following limit descriptors nnn where nnn is a value greater
gives more details of the error: than the value revealed by the limit command.
"error_message".
Restart Monman.
Explanation: As message.
error_message contains the operating system error AWSBCX011E The Event Integration Facility
message. configuration file (file) cannot be
System action: Monman stops. written; the operating system gives the
following error: error_message
Operator response: Contact IBM Software Support for
assistance. Explanation: Monman is unable to write the
configuration file for the Event Integration Facility, the
component used to send the events.
AWSBCX005E An internal error has occurred.
Monman encountered the following file is the name of the file with the configuration that
error when attempting to open the Monman is attempting to write.
Symphony file: "error_message". error_message is a message that contains information
Explanation: error_message contains the operating about the error and includes the operating system error
system error message. message.

Operator response: Contact IBM Software Support for System action: Monman stops.
assistance. Operator response: Attempt to resolve the operating
system error.
AWSBCX007E A message file cannot be opened; the Restart Monman.
operating system gives the following
error: error_message
AWSBCX012E An internal error has occurred. The
Explanation: Monman is unable to open one of its Event Integration Facility initialization
message file: Monbox.msg or Moncmd.msg. has failed.
error_message is a message that contains information Explanation: Monman is unable to initialize the Event
about the error and includes the operating system error Integration Facility, the component used to send the
message. events.
A possible reason is that either your Tivoli Workload System action: Monman stops.
Scheduler user or your system has too many files open
(a typical user is limited to 64 files). Operator response: Contact IBM Software Support for
assistance.
System action: Monman stops.

28 IBM Tivoli Workload Scheduler: Messages


AWSBCX013E • AWSBCX021E

v That the file exists


AWSBCX013E An internal error has occurred. A
parsing error has occurred reading the v That the file is in the correct directory
following event "event". v That the file has read permission
Explanation: Monman is unable to parse the event, it v That there is sufficient disk space to open and read a
will be discarded and not sent to the event processor. file
v That there are sufficient file descriptors available to
System action: Monman discards the current event
open a file.
and will not sent it to the event processor. Monman
continues
Correct any errors that you find, and perform the
Operator response: Contact IBM Software Support for action again.
assistance.

AWSBCX018E An error has occurred writing the file


AWSBCX015E An error has occurred opening the "file_name".
temporary file "file_name" for writing.
Explanation: See message.
Explanation: See message.
file_name is the file that cannot be written.
file_name is the file that cannot be opened.
System action: The action stops.
System action: The action stops.
Operator response: Check the following:
Operator response: Check the following: v That the file exists
v That there is sufficient disk space to open and read a v That the file is in the correct directory
file
v That the file has write permission
v That there are sufficient file descriptors available to
open a file. v That there is sufficient disk space to write the file

Correct any errors that you find, and perform the Resolve the problem and rerun the operation.
action again.
AWSBCX019E The zip file "file_name" was built
AWSBCX016E An error has occurred opening the file incorrectly. The Unzip process is
"file_name" for reading. stopped with an error.

Explanation: See message. Explanation: See message.

file_name is the file that cannot be opened. file_name is the zip file built incorrectly.

System action: The action stops. System action: The operation is not performed.

Operator response: Check the following: Operator response: Contact IBM Software Support for
assistance.
v That the file exists
v That the file is in the correct directory
AWSBCX020E An error has occurred extracting the
v That the file has read permission file "file_name". The Unzip process is
v That there is sufficient disk space to open and read a stopped with an error.
file
Explanation: See message.
v That there are sufficient file descriptors available to
open a file. file_name is the zip file that cannot be unzipped.
System action: The action stops.
Correct any errors that you find, and perform the
action again. Operator response: Contact IBM Software Support for
assistance.
AWSBCX017E An error has occurred opening the file
"file_name" for writing. AWSBCX021E An error has occurred before
completing the unzip process.
Explanation: See message.
Explanation: See message.
file_name is the file that cannot be opened.
System action: The action stops.
System action: Deployconfig action stops.
Operator response: Contact IBM Software Support for
Operator response: Check the following: assistance.

Chapter 2. Message help 29


AWSBCX022E • AWSBCX023W

AWSBCX022E Monman encountered an error when


attempting to open the Mailbox.msg
file. The following gives more details of
the error: error_message
Explanation: Monman is unable to open the
Mailbox.msg file.
error_message is a message that contains information
about the error and includes the operating system error
message.
A possible reason is that either your Tivoli Workload
Scheduler user or your system has too many files open
(a typical user is limited to 64 files).
System action: Monman stops.
Operator response: Attempt to resolve the operating
system error. Use the limit command to see the user’s
file limits (the file limit is the ’descriptor’ line for csh
users).
If the problem is with the number of files open, take
one of the following actions, according to whether the
problem is with the operating system limits or a user’s
limits:
v Add the following lines to 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 is correct for a csh user):
limit descriptors nnn where nnn is a value greater
than the value revealed by the limit command.

Restart Monman.

AWSBCX023W The Event Driven Workload


Automation feature is disabled,
Monman stops.
Explanation: The Event Driven Workload Automation
feature has been disabled by optman, which set the
enEventDrivenWorkloadAutomation option to NO.
Monman exits, as it is not required in this
configuration.
System action: Monman stops.
Operator response: None.

30 IBM Tivoli Workload Scheduler: Messages


AWSBCZ003E • AWSBCZ110E

Dload messages - BCZ


This section lists error and warning Dload messages that could be issued.

The message component code is BCZ and the old message set code is 077 in the
″maestro″ message catalog.
System action: The operation cannot be performed.
AWSBCZ003E The object ID must start with an
alphabetic character. Operator response: Shorten the parameter name and
resubmit the operation.
Explanation: See message.
System action: The operation cannot be performed.
AWSBCZ106E The prompt name exceeds the
Operator response: Correct the object ID and resubmit maximum length of max_prompt bytes.
the operation.
Explanation: See message.
max_prompt is the maximum length for the prompt
AWSBCZ004E The object ID contains at least one
name.
character that is not valid. Valid
characters are 0-9, a-z, dashes and System action: The operation cannot be performed.
underscores.
Operator response: Shorten the prompt name and
Explanation: See message. resubmit the operation.
System action: The operation cannot be performed.
AWSBCZ107E The variable table name exceeds the
Operator response: Correct the object ID and resubmit
maximum length of max_vartable bytes.
the operation.
Explanation: See message.
AWSBCZ103E The description exceeds the maximum max_vartable is the maximum length for the variable
length of max_description bytes. table.
Explanation: See message. System action: The operation cannot be performed.
max_description is the maximum length for the Operator response: Shorten the variable table name
description. and resubmit the operation.
System action: The operation cannot be performed.
AWSBCZ108E The variable description exceeds the
Operator response: Shorten the description and
maximum length of max_desc bytes.
resubmit the operation.
Explanation: See message.
AWSBCZ104E The resource name exceeds the max_desc is the maximum length for the variable
maximum length. The maximum for the description.
workstation is max_workstation bytes and
the maximum for the resource is System action: The operation cannot be performed.
max_resource Operator response: Shorten the description and
Explanation: See message. resubmit the operation.

max_workstation and max_resource are the maximum


lengths for the workstation and resource names. AWSBCZ109E The variable name exceeds the
maximum length of max_var bytes.
System action: The operation cannot be performed.
Explanation: See message.
Operator response: Shorten the resource name and
resubmit the operation. max_var is the maximum length for the variable name.
System action: The operation cannot be performed.
AWSBCZ105E The parameter name exceeds the Operator response: Shorten the variable name and
maximum length of max_parameter bytes. resubmit the operation.
Explanation: See message.
max_parameter is the maximum length for the parameter AWSBCZ110E The variable value exceeds the
name. maximum length of max_value bytes.

Chapter 2. Message help 31


AWSBCZ111E • AWSBCZ116E

Explanation: See message.


AWSBCZ116E The variable variable is already present
max_value is the maximum length for the variable. in the variable table variable_table

System action: The operation cannot be performed. Explanation: See message.

Operator response: Shorten the variable value and Duplicates are not allowed in a variable table
resubmit the operation.
System action: The operation cannot be performed.
Operator response: Delete or rename the duplicated
AWSBCZ111E The syntax of the variable table is
variable.
incorrect. The token token is expected at
this point.
Explanation: See message.
System action: The operation cannot be performed.
Operator response: Check the syntax of the variable
table and resubmit the operation.

AWSBCZ112E A syntax error was detected in the list


of variables.
Explanation: See message.
System action: The operation cannot be performed.
Operator response: Check the syntax of the variable
table list and resubmit the operation..

AWSBCZ113E The value of the variable must be a


string enclosed in quotation marks.
Explanation: See message.
The value specified for a variable is not in the correct
format.
System action: The operation cannot be performed.
Operator response: Correct the format of the specified
value and resubmit the operation..

AWSBCZ114E The variable table variable_table


contains syntax errors.
Explanation: See message.
System action: The operation cannot be performed.
Operator response: Correct the syntax of the variable
table and resubmit the operation..

AWSBCZ115E The maximum number of errors that


can be displayed for the variable table
has been reached.
Explanation: See message.
System action: No further validation of the input is
performed.
Operator response: Correct the syntax of the variable
table and resubmit the operation..

32 IBM Tivoli Workload Scheduler: Messages


AWSBDB004W • AWSBDB005E

Scribner messages - BDB


This section lists error and warning scribner messages that could be issued.

The message component code is BDB and the old message set code is 079 in the
″maestro″ message catalog.

AWSBDB004W The timeout value "!1" is not valid.


The default value has been used.
Explanation: You have supplied a timeout value that
is not in the correct format. It must be the numeric
value of the number of seconds required for the
timeout to be used by scribner. For example, the value
for 30 seconds must be "30", not "30s" or "30 secs".
System action: scribner uses its default timeout value.
Operator response: If you want to apply a timeout
value different from the default, shut down the
scribner process and rerun the scribner command,
supplying a correctly formatted timeout value.

AWSBDB005E There is a syntax error. Too few


parameters have been supplied.
Explanation: The scribner process requires the link
parameters to be passed to it. These parameters have
not been supplied correctly.
System action: The scribner process cannot start.
Operator response: Rerun the scribner command,
supplying the correct linking parameters.

Chapter 2. Message help 33


AWSBDC102E

NetView/OpenView messages - BDC


This section lists error and warning NetView and OpenView messages that could
be issued.

The message component code is BDC and the old message set code is 080 in the
″maestro″ message catalog.

AWSBDC102E Tivoli Workload Scheduler is not


correctly installed on this system:
"computer".
Explanation: The program has found an error or
inconsistency in the installation of Tivoli Workload
Scheduler.
System action: The program stops.
Operator response: The Tivoli Workload Scheduler
component installed on the indicated computer must be
reinstalled.

34 IBM Tivoli Workload Scheduler: Messages


AWSBDG001E • AWSBDG009E

Downloader messages - BDG


This section lists error and warning messages that could be issued by the
downloader component.

The message component code is BDG and the old message set code is 084 in the
″maestro″ message catalog.
Explanation: error_text is a string that describes the
AWSBDG001E Downloader cannot connect to the
reason for the error. The information is retrieved from
remote client. The socket descriptor
the operating system.
passed to downloader by netman is not
valid. The following gives more details System action: Downloader stops. The centralized
of the error: error_text. script is not correctly downloaded.
Explanation: error_text is a string giving more details. Operator response: This is an internal error. Contact
IBM Software Support for assistance.
System action: Downloader stops. The centralized
script is not correctly downloaded.
AWSBDG008E Downloader could not read a record
Operator response: This is an internal error. Contact
from the centralized script. The
IBM Software Support for assistance.
following gives more details of the error
by the operating system: error_text
AWSBDG002E Downloader is unable to create the
Explanation: In an end-to-end configuration the
stdlist file.
translator thread, running on OPCMASTER, is
Explanation: Downloader creates its own stdlist file downloading a centralized script to this workstation,
when the merge stdlists option is set to no in the but downloader was unable to read one of the records.
localopts file.
error_text is a string that describes the reason for the
System action: Downloader stops. The centralized error. The information is retrieved from the operating
script is not correctly downloaded. system.
Operator response: This is an internal error. Contact System action: Downloader stops. The centralized
IBM Software Support for assistance. script is not correctly downloaded.
Operator response: This is an internal error. Contact
AWSBDG005E Downloader is started by netman IBM Software Support for assistance.
with an incorrect number of arguments.
Explanation: See message. AWSBDG009E Downloader could not allocate
memory for internal data structures
Operator response: This is an internal error. Contact
(comarea).
IBM Software Support for assistance.
Explanation: See message.
AWSBDG006W The download for file file_name has System action: Downloader stops. The centralized
been stopped by the client (the domain script is not correctly downloaded.
manager on z/OS).
Operator response: Check the following:
Explanation: See message. 1. Verify if the workstation has enough memory
file_name is the name of the centralized script file that available. Information about the memory
could not be downloaded. requirements of Tivoli Workload Scheduler is
provided in the Release Notes. If not, you might need
System action: Downloader stops. The centralized to increase the memory of the workstation or make
script is not correctly downloaded. changes in memory management and paging to
Operator response: See the associated messages issued make more memory available to downloader. Rerun
either before or after this one that indicate the detail of downloader.
why the download did not complete successfully. 2. If the workstation memory is adequate, try closing
all the applications that you do not need, and then
rerun downloader.
AWSBDG007E Downloader was unable to send a
record. The following gives more details 3. If the problem persists, reboot the workstation, and
of the error by the operating system: then rerun downloader.
error_text 4. If the problem persists, contact IBM Software
Support for assistance.

Chapter 2. Message help 35


AWSBDG011E • AWSBDG014E

See: The Release Notes for details of memory When you have resolved the problem, rerun
requirements. downloader.
If the problem persists, contact IBM Software Support
AWSBDG011E Downloader cannot save the for assistance.
downloaded centralized script in the
following temporary file: "file_name ".
AWSBDG013E Downloader cannot change the access
The following operating system error
mode of the following temporary file
was received: error_text.
where the downloaded centralized script
Explanation: In an end-to-end configuration the is saved: "file_name ". The following
translator thread, running on OPCMASTER, is operating system error was received:
downloading a centralized script to this workstation. error_text.
Downloader tries to save the script in a temporary file,
Explanation: In an end-to-end configuration the
(file_name), but is unable to write the file. The
translator thread, running on OPCMASTER is
download of the script fails.
downloading a centralized script to this workstation.
error_text is a string that describes the reason for the Downloader tries to save the script in a temporary file,
error. The information is retrieved from the operating (file_name), but is unable to set the correct access mode.
system. The download of the script fails.
System action: Downloader stops. The centralized error_text is a string that describes the reason for the
script is not correctly downloaded. error. The information is retrieved from the operating
system.
Operator response: Attempt to resolve the problem
indicated in the error_text. System action: Downloader stops. The centralized
script is not correctly downloaded.
If the error_text reveals a problem with disk space or
access rights, check the <TWS_home> file system to Operator response: Attempt to resolve the problem
ensure that there is sufficient space, and that the user indicated in the error_text.
has write permission.
If the error_text reveals a problem with disk space or
When you have resolved the problem, rerun access rights, check the <TWS_home> file system to
downloader. ensure that there is sufficient space, and that the user
has write permission.
If the problem persists, contact IBM Software Support
for assistance. When you have resolved the problem, rerun
downloader.
AWSBDG012E Downloader cannot open the If the problem persists, contact IBM Software Support
following temporary file where the for assistance.
downloaded centralized script is saved:
"file_name ". The following operating
AWSBDG014E Downloader cannot close the
system error was received: error_text.
following temporary file where the
Explanation: In an end-to-end configuration the downloaded centralized script is saved:
translator thread, running on OPCMASTER, is "file_name ". The following operating
downloading a centralized script to this workstation. system error was received: error_text.
Downloader tries to save the script in a temporary file,
Explanation: In an end-to-end configuration the
(file_name), but is unable to open the file. The download
translator thread, running on OPCMASTER is
of the script fails.
downloading a centralized script to this workstation.
error_text is a string that describes the reason for the Downloader tries to save the script in a temporary file,
error. The information is retrieved from the operating (file_name), but is unable to close the file. The download
system. of the script fails.
System action: Downloader stops. The centralized error_text is a string that describes the reason for the
script is not correctly downloaded. error. The information is retrieved from the operating
system.
Operator response: Attempt to resolve the problem
indicated in the error_text. System action: Downloader stops. The centralized
script is not correctly downloaded.
If the error_text reveals a problem with disk space or
access rights, check the <TWS_home> file system to Operator response: Attempt to resolve the problem
ensure that there is sufficient space, and that the user indicated in the error_text.
has write permission.
If the error_text reveals a problem with disk space or
access rights, check the <TWS_home> file system to

36 IBM Tivoli Workload Scheduler: Messages


AWSBDG015E • AWSBDG022E

ensure that there is sufficient space, and that the user


AWSBDG019E Downloader cannot obtain file status
has write permission.
information for the following file:
When you have resolved the problem, rerun file_name. The following gives more
downloader. details of the error: error_text.

If the problem persists, contact IBM Software Support Explanation: Downloader in unable to retrieve status
for assistance. information for file file_name.
error_text is a string that describes the reason for the
AWSBDG015E Downloader cannot convert the error.
temporary file where the downloaded
System action: Downloader stops. The centralized
centralized script is saved from UTF-8 to
script is not correctly downloaded.
the local file format. The UTF-8 file is
the following: "file_name1" and the local Operator response: Contact IBM Software Support for
file that cannot be created is the assistance.
following: "file_name2".
Explanation: In an end-to-end configuration the AWSBDG021E Downloader cannot create the
translator thread, running on OPCMASTER is following directory where the
downloading a centralized script to this workstation. downloaded centralized script is saved:
Downloader has saved the script in a temporary file "directory_name". The following operating
(file_name1) but it is unable to convert this file from system error was received: error_text.
UTF-8 to the local file format (file_name2). The
Explanation: In an end-to-end configuration the
download of the script fails.
translator thread, running on OPCMASTER, is
System action: Downloader stops. The centralized downloading a centralized script to a target
script is not correctly downloaded. workstation. Downloader tries to save the script in a
temporary file, but is unable to create the directory for
Operator response: This is an internal error. Contact
the file. The download of the script fails.
IBM Software Support for assistance.
error_text is a string that describes the reason for the
error. The information is retrieved from the operating
AWSBDG016E Downloader is receiving a centralized
system.
script file, but a packet is too long for
the buffer. System action: Downloader stops. The centralized
script is not correctly downloaded.
Explanation: See message.
Operator response: Attempt to resolve the problem
System action: Downloader stops. The centralized
indicated in the error_text.
script is not correctly downloaded.
If the error_text reveals a problem with disk space or
Operator response: This is an internal error. Try
access rights, check the <TWS_home> file system to
rerunning the operation. If the problem persists, contact
ensure that there is sufficient space, and that the user
IBM Software Support for assistance.
has write permission.
When you have resolved the problem, rerun
AWSBDG017E Downloader cannot download a
downloader.
centralized script. The following
operating system error was received: If the problem persists, contact IBM Software Support
error_text for assistance.
Explanation: In an end-to-end configuration the
translator thread, running on OPCMASTER, is AWSBDG022E Downloader cannot write the
downloading a centralized script to a target downloaded centralized script in a
workstation. The download of the script has failed. temporary file on the target workstation.
error_text is a string that describes the cause of the Explanation: In an end-to-end configuration the
error. translator thread, running on OPCMASTER, is
downloading a centralized script to a target
System action: Downloader stops. The centralized
workstation, but the download has failed.
script is not correctly downloaded.
System action: Downloader stops. The centralized
Operator response: Check the downloader log on the
script is not correctly downloaded.
target workstation for other messages that give details
of the cause of the error. If no messages can be found, Operator response: Check the downloader log on the
contact IBM Software Support for assistance. target workstation for other messages that give details
of the cause of the error. If no messages can be found,

Chapter 2. Message help 37


contact IBM Software Support for assistance.

38 IBM Tivoli Workload Scheduler: Messages


AWSBDJ003E • AWSBDJ008E

Appserverman messages - BDJ


This section lists error and warning appserverman messages that could be issued.

The message component code is BDJ.

AWSBDJ003E The application server has stopped AWSBDJ007W The "auto-restart" flag (see
unexpectedly or failed. "localopts") is set to false, so the
application server is not restarted by the
Explanation: The application server monitor
application server monitor.
(appservman) has detected that the application server
is no longer running, but that it has not been stopped Explanation: The application server monitor
by the user. (appservman) has detected that the application server
has failed.
System action: The application server monitor checks
the policies defined in the localopts file to decide However, the policies in the localopts files indicate
whehter the application server should be restarted. that the application server is not to be restarted.
Operator response: See the application server logs to System action: The application server monitor does
diagnose the problem that is causing the application not restart the application server. It stops.
server to fail. If you are not able to solve the problem
Operator response: See the application server logs to
contact IBM Software Support for assistance.
diagnose the problem that is causing the application
server to fail. If you are not able to solve the problem
AWSBDJ005E Cannot restart the application server. contact IBM Software Support for assistance.
See the application server log for the
To restart the application server run a "conman
reason.
startappserver" or "StartUp" command.
Explanation: See message.
To permit the application server monitor to
System action: The application server monitor has automatically restart the application server, change the
failed to restart the application server. The application value of the "Appserver auto restart" option in the
server monitor (appservman) stops. localopts file.
Operator response: See the application server logs to
diagnose the problem that has caused the start of the AWSBDJ008E The application server has been
application server to fail. If you are not able to solve restarted more times than the configured
the problem contact IBM Software Support for maximum (see "localopts"), so the
assistance. application server will not be restarted
by the application server monitor.
To restart the application server run a "conman
startappserver" or "StartUp" command. Explanation: The application server monitor
(appservman) has detected that the application server
has failed.
AWSBDJ006E Cannot stop the application server. See
the application server log for the reason. The application server monitor has already restarted
the application server one or more times, and the
Explanation: See message.
policies in the localopts files indicate that the
System action: The application server monitor application server should no longer be restarted
(appservman) has failed to stop the application server. automatically by the application server monitor (it
might be failing repeatedly for the same reason).
The application server monitor stops. However, the
application server is probably still running. System action: The application server monitor does
not attempt to restart the application server. It stops.
Operator response: See the application server logs to
diagnose the problem that is causing the application Operator response: See the application server logs to
server to fail. If you are not able to solve the problem diagnose the problem that is causing the application
contact IBM Software Support for assistance. server to fail. If you are not able to solve the problem
contact IBM Software Support for assistance.
To manually stop the application server run the
following command:"wastools/stopWas -direct -user To restart the application server run a "conman
<username> -password <password>". startappserver" or "StartUp" command.
To allow the application server monitor to continue
restarting the application server automatically in these
circumstances, change the value of the "Appserver max

Chapter 2. Message help 39


AWSBDJ009E • AWSBDJ016E

restarts" option in the localopts file. You might also Software Support for assistance.
want to change the value of the "Appserver count reset
interval" option.
AWSBDJ016E An internal error occurred while
reading the Appservrbox message
AWSBDJ009E The application server was up before queue.
failing for less time than the configured
Explanation: An internal error has occurred.
minimum (see "localopts"), so the
application server will not be restarted System action: The application server monitor stops.
by the application server monitor.
Operator response: This is an internal error. Contact
Explanation: The application server monitor IBM Software Support for assistance.
(appservman) has detected that the application server
has failed. The monitor restarted the application server,
which failed again in a shorter time than the minimum
restart time as determined by the policies in the
localopts files.
System action: The application server monitor does
not attempt to restart the application server. It stops.
Operator response: See the application server logs to
diagnose the problem that is causing the application
server to fail. If you are not able to solve the problem
contact IBM Software Support for assistance.
To restart the application server run a "conman
startappserver" or "StartUp" command.
To allow the application server monitor to continue
restarting the application server automatically in these
circumstances, change the value of the "Appserver min
restart time" option in the localopts file.

AWSBDJ012E An internal error occurred while


opening the "Appserverbox" message
queue.
Explanation: The application server monitor
(appservman) was not able to open the Appserverbox
message queue.
System action: The application server monitor stops.
Operator response: Check the access permissions of
the Appserverbox.msg file. If you have solved the
problem, stop and restart the application server, which
automatically restarts the application server monitor. If
you are not able to solve the problem contact IBM
Software Support for assistance.

AWSBDJ013E An internal error occurred while


opening the "Mailbox" message queue.
Explanation: The application server monitor
(appservman) was not able to open the Mailbox
message queue.
System action: The application server monitor stops.
Operator response: Check the access permissions of
the Mailbox.msg file. If you have solved the problem,
stop and restart the application server, which
automatically restarts the application server monitor. If
you are not able to solve the problem contact IBM

40 IBM Tivoli Workload Scheduler: Messages


AWSBDW002E • AWSBDW009E

Jobman messages - BDW


This section lists error and warning messages that could be issued by the jobman
component.

The message component code is BDW and the old message set code is 100 in the
″maestro″ message catalog.
When you have corrected the problem, either rerun the
AWSBDW002E The user ID used to launch this job
job using the from option (specifying the same name of
is not valid. The operating system error
the job) or submit the job into the plan.
is: system_error_number.
Explanation: To launch a job, a user ID must have the
AWSBDW005E The JCL file "file_name" could not be
following characteristics:
launched. The operating system error is:
v It must be a valid user ID for the computer on which system_error_number.
the job is launched
Explanation: system_error_number contains the
v It must be defined in the mozart database with
operating system error message number. file_name is the
permission to launch jobs.
name of the JCL file Tivoli Workload Scheduler is
trying to launch.
Further, the user ID must be supplied correctly when
the job is launched, either from the command line or System action: The program stops.
from the mozart database.
Operator response: Verify that the JCL file specified in
the job definition is correct, the file exists and it is
system_error_number contains the operating system error
readable and executable by the Tivoli Workload
message.
Scheduler user. Rerun or submit an ad-hoc job after the
problem has been resolved.
Internal error: Setuid() failed with the indicated error.
System action: Jobman proceeds. AWSBDW009E The following operating system error
Operator response: Follow this procedure: occurred retrieving the password
structure for either the logon user, or the
1. Check the job properties in the plan list from the
user who owns a file or external
Job Scheduling Console, or use the sj
dependency: system_error.
schedid.jobid;L command in conman to obtain the
user ID with which Tivoli Workload Scheduler is Explanation: This message is a warning when
attempting to launch the job. checking a file dependency or when getting the status
2. Verify that the user ID has been supplied correctly. of an external dependency.
If not, modify the job definition used to launch the It is an error when trying to launch a job. Jobman
job to identify a different user that has the rights to cannot retrieve the password structure from the system
launch jobs on this workstation. for either the logon user, the Check File user (CFuser),
3. If the correct user ID has been supplied, verify that or the Get Status user (GSuser).
the user ID is defined in the mozart database as a
user with the rights to launch jobs. If it is not, you system_error is the operating system error message.
need to either change the user in the job definition The logon must be a valid user on the system where
to a user that has the rights to launch jobs on this the job is being launched or check file or get status is
workstation, or define the original user ID to have being requested. It has a different meaning according to
these rights in the mozart database. Note that only a the platform.
Tivoli Workload Scheduler administrator can do
v UNIX: The user logon does not exist.
this.
v Windows: The problem might be caused by a
4. If the user ID is defined in the mozart database with
confusion between local or domain accounts;
rights to launch jobs, verify that the user ID is
however the logon must be valid and must be
defined in the operating system. If it is not, you
correctly associated with the password stored in the
need to define the user ID to the operating system,
Symphony file and the userdata database.
using the operating system’s standard procedures
for creating a user. Note that you might not have Operator response: If the user was documented
the rights to do this; you might have to log on as incorrectly in the plan, update the value in the database
Administrator or root. and use the rerun command with the from option so
that Tivoli Workload Scheduler can read the original
definition or resubmit the job into the plan.

Chapter 2. Message help 41


AWSBDW039E • AWSBDW078W

AWSBDW039E Jobman or jobmon could not resolve


an external dependency on job
"external_job". The operating system error
is: system_error.
Explanation: external_job is the name of the external
job (<workstation>#<external_job>). system_error is the
operating system error message.
This is a message that is embedded in other error
messages.
System action: Jobman proceeds.
Operator response: Check the response associated
with the error specified by system_error. When you have
located the error, rerun or reschedule the job, as
appropriate.

AWSBDW057E The job "job_name" was not launched


for this reason: error_message.
Explanation: job_name is the name of the job.
error_message contains the reason for the failure. It is
another Tivoli Workload Scheduler message.
System action: Jobman proceeds.
Operator response: Check the indicated message and
implement the associated operator response.
Contact IBM Software Support for assistance if the
resolution to the problem is not clear.

AWSBDW078W The promotion value specified in


the "localopts" file is greater than zero.
Values that are greater than zero are not
valid and are set to -1.
Explanation: Positive promotion values do not work
correctly and decrease system performance.
System action: Jobmon automatically set the
promotion value to -1.
Operator response: Check the values defined in the
"localopts" file and assign the correct promotion values.

42 IBM Tivoli Workload Scheduler: Messages


AWSBDX001E • AWSBDX005E

Jobtable access messages - BDX


This section lists jobtable access error and warning messages that could be issued.

The message component code is BDX and the old message set code is 101 in the
″maestro″ message catalog.
v 8 = write
AWSBDX001E Jobman has found a problem with its
internal job table. See the message help System action: Jobman continues, but the action that
for details. you or jobman were trying to perform is ignored.
Explanation: This message can be provoked by two Operator response: Verify if the job in question is
different situations: running, using the operating system tools. If it is, try to
1. Jobman expected to find an entry for a running job perform your action manually, for example using a
in its internal job table, but there are no more shell command.
entries to be read (end-of-table encountered). This is If it is not running, and you expected it to be, contact
an internal error. IBM Software Support for assistance.
2. Jobman tried to add a new job to the job table, but
the table is full. There are too many jobs running,
The maximum is determined by the jm job table size AWSBDX004E Jobman could not open the jobtable
parameter in the localopts file. file. The operating system error is:
error_message.
System action: Jobman continues, but the job that it is
trying to manage is ignored (it might be run later when Explanation: The following are the two most
the number of running jobs has reduced). commonly occurring possibilities:
1. The maximum size of the jobtable (maximum
Operator response: Check how many jobs are running number of entries, as defined in the option jm job
using the operating system tools. If you have reached table size in the localopts file), is set to 0.
the maximum indicated in the localopts file, you must
either explicitly stop an existing job, or wait for jobs to 2. Jobman could not find an existing jobtable file.
finish as normal, before you can run any new jobs. If
you believe that the maximum number of jobs is likely error_message is a system error message, giving more
to be exceeded on other occasions, you might want to details about the cause of the error.
consider increasing the value of the jm job table size System action: Jobman stops.
parameter (if you make any changes, you have to stop
and restart jobman for them to take effect). Operator response: Verify if the option jm job table size
in the localopts file is equal to 0. If it is 0, change the
If you have not reached the maximum number of jobs, value to a positive integer value, for example 1024.
this is an internal error; contact IBM Software Support
for assistance. If the jm job table size option is already a positive
integer, an existing jobtable file was not found. Use
the error_message to determine why the file could not be
AWSBDX002E You or jobman tried to perform an opened. Also search in the log file for entries that
action on a job that is either not indicate that Jobman failed to create the file or had
running or is not within jobman’s some other problem with the file. When you have
internal job table. Probably the job has identified the cause of the problem, rerun jobman by
terminated. If it is still running, an running the start command for the workstation.
internal error has occurred. The action
that cannot be performed is the See also: See the Planning and Installation Guide for
following: "action_number". details about the options in the localopts file and their
default values.
Explanation: action_number is a number indicating the
action that was being performed when the error
occurred: AWSBDX005E Jobman received the following
operating system error while handling
v 1 = open
the jobtable file: error_number.
v 2 = read
Explanation: The system calls that can fail are: lock,
v 3 = add
fcntl, open, write, lseek, and read. error_number is the
v 4 = update operating system error number, which indicates what
v 5 = delete problem was encountered.
v 6 = lock System action: Jobman stops.
v 7 = unlock

Chapter 2. Message help 43


AWSBDX007E • AWSBDX008E

Operator response: Resolve the problem indicated in


the operating system error message.
Check the file system of <TWS_home> to ensure that there
is sufficient space, and that the user has write
permission. If jobman has stopped, when you have
resolved the problem, rerun jobman.
If the problem persists, contact IBM Software Support
for assistance.

AWSBDX007E Jobman cannot add a new entry to the


job table because the job does not have
a valid job number.
Explanation: This is an internal error.
System action: Jobman continues, but the job in
question is not run.
Operator response: Contact IBM Software Support for
assistance.

AWSBDX008E Jobman tried to perform the action


"action_number" but the job table is not
locked. This is an internal error.
Explanation: action_number is a number indicating the
action that was being performed when the error
occurred:
v 1 = open
v 2 = read
v 3 = add
v 4 = update
v 5 = delete
v 6 = lock
v 7 = unlock
v 8 = write
System action: The action is not performed. Jobmon
could not be correctly initialized. Jobman might stop.
Operator response: This is an internal error. Contact
IBM Software Support for assistance.

44 IBM Tivoli Workload Scheduler: Messages


AWSBDY102E • AWSBDY119E

Mailbox messages - BDY


This section lists mailbox error and warning messages that could be issued.

The message component code is BDY and the old message set code is 102 in the
″maestro″ message catalog.

AWSBDY102E An internal error has occurred. The


program cannot access the mailbox or
ftbox common area in memory. The
pointer to the mailbox common area is
NULL or the area is not initialized.
Explanation: See message.
System action: The program might stop, depending
on the circumstances of the error.
Operator response: Contact IBM Software Support for
assistance.

AWSBDY118E Tivoli Workload Scheduler


encountered a nonexistent mailbox
record type. The problem was
encountered in the following source
code file: "file_name" at line:
"line_number". The call was
mb_e_2_i_HDR() and the unexpected
mailbox record type is as follows:
record_type.
Explanation: This is an internal error. It might occur if
one or more workstations in your network are running
an old version of Tivoli Workload Scheduler.
file_name and line_number are source code information.
record_type is the unexpected record type.
System action: The program continues.
Operator response: Contact IBM Software Support for
assistance.

AWSBDY119E Tivoli Workload Scheduler received a


mailbox record incompatible with the
version of the product. The problem
was encountered in the following source
code file: "file_name" at line:
"line_number". The call was mb_e_2_i()
and the unexpected mailbox record type
is as follows: record_type.
Explanation: The Mailbox.msg file is not compatible
with the expanded Symphony file version.
file_name and line_number are source code information.
record_type is the unexpected record type.
System action: The program continues.
Operator response: Contact IBM Software Support for
assistance.

Chapter 2. Message help 45


AWSBEC110E • AWSBEC112E

Report headers and subheaders messages - BEC


This section lists error and warning report headers and subheaders messages that
could be issued.

The message component code is BEC and the old message set code is 106 in the
″maestro″ message catalog.
If you cannot find any error, rerun the report generator.
AWSBEC110E Cannot open file "file_name".
If the problem persists, contact IBM Software Support.
Explanation: The report generator program cannot
open the indicated file.
System action: The report generator program stops.
Operator response: Verify the following:
v That the file exists.
v That the user of Tivoli Workload Scheduler can
access the file in all modes.
v That the file has not been locked by another process.
Correct any errors you find and rerun the report
generator.

If you cannot find any error, rerun the report generator.


If the problem persists, contact IBM Software Support.

AWSBEC111E An error occurred while writing file


"file_name".
Explanation: The report generator program cannot
write the indicated file.
System action: The report generator program stops.
Operator response: Verify the following:
v That the user of Tivoli Workload Scheduler has write
access to the directory in which the file needs to be
written.
v That there is sufficient space in the file system where
the file is to be written.
Correct any errors you find and rerun the report
generator.

If you cannot find any error, rerun the report generator.


If the problem persists, contact IBM Software Support.

AWSBEC112E An error occurred while reading file


"file_name".
Explanation: The report generator program cannot
read the indicated file.
System action: The report generator program stops.
Operator response: Verify the following:
v That the user of Tivoli Workload Scheduler has read
access to the file.
v That the file has not been locked by another process.
Correct any errors you find and rerun the report
generator.

46 IBM Tivoli Workload Scheduler: Messages


AWSBEE007E • AWSBEE008E

Parms messages - BEE


This section lists error and warning parms messages that could be issued.

The message component code is BEE and the old message set code is 108 in the
″maestro″ message catalog.

AWSBEE007E You do not have "build" permission


for the "parms -build" command that
creates and maintains the parameters
database.
Explanation: You have tried to build the local
parameters database but your user ID does not have
"build" permission in the Security file.
System action: The build of the parameters database
cannot be performed.
Operator response: Either ask your Tivoli Workload
Scheduler Administrator to give you "build" permission
for this action and retry, or log off and log again with a
user ID that has "build" permission for this action.

AWSBEE008E A syntax error occurred. The parameter


name exceeds the maximum length of
max_vartable bytes.
Explanation: You have supplied a parameter name
that is too long.
System action: The submitted command cannot be
performed.
Operator response: Change the parameter name so
that it is no longer than the indicated maximum length
and retry the operation.

Chapter 2. Message help 47


AWSBEG201E • AWSBEG203E

Ftbox messages - BEG


This section lists error and warning messages that could be issued by the routines
that maintain the ftbox directory.

The message component code is BEG and the old message set code is 110 in the
″maestro″ message catalog.
any program that subsequently needs to access a file in
AWSBEG201E The following directory could not be
the ftbox directory fails.
created: directory_name. The following
error was returned from the operating Operator response: Check if the<TWSuser> has the
system: error_code authority to change the ownership of the ftbox
directory. Grant these rights if they are not already
Explanation: The ftbox directory could not be created.
granted. When you have resolved the problem, if the
System action: The program goes ahead. However, Tivoli Workload Scheduler processes are still running,
any program that subsequently needs to access a file in stop them by issuing a stop command for the
the ftbox directory fails. workstation. Then issue a start command for the
workstation.
Operator response: Check the file system of
<TWS_home> to ensure that there is sufficient space, and If the problem persists, contact IBM Software Support
that the user has write permission. When you have for assistance.
resolved the problem, if the Tivoli Workload Scheduler
processes are still running, stop them by issuing a stop
command for the workstation. Then issue a start
command for the workstation.
If the problem persists, contact IBM Software Support
for assistance.

AWSBEG202E Access rights to the following


directory could not be set: directory_name.
The following error was returned from
the operating system: error_code
Explanation: The access rights to the ftbox directory
could not be changed.
System action: The program goes ahead. However,
any program that subsequently needs to access a file in
the ftbox directory fails.
Operator response: Check if the<TWSuser> has the
authority to change the access rights to the ftbox
directory. Grant these rights if they are not already
granted. When you have resolved the problem, if the
Tivoli Workload Scheduler processes are still running,
stop them by issuing a stop command for the
workstation. Then issue a start command for the
workstation.
If the problem persists, contact IBM Software Support
for assistance.

AWSBEG203E A change of ownership could not be


made to the following directory:
directory_name. The following error was
returned from the operating system:
error_code
Explanation: The owner of the ftbox directory cannot
be changed.
System action: The program goes ahead. However,

48 IBM Tivoli Workload Scheduler: Messages


AWSBEH001E • AWSBEH006E

Web library messages - BEH


This section lists error and warning messages that could be issued by the routines
that use the Web library.

The message component code is BEH and the old message set code is 111 in the
″maestro″ message catalog.
files and ensure that the "protocol" keyword is defined
AWSBEH001E The connection configuration file
and identifies a valid protocol.
"file_name" containing the connection
properties cannot be found. Alternatively, supply the protocol as a command
parameter.
Explanation: The error occurred while trying to open
the file that contains the connection properties. The files See: The Reference Manual for the full syntax of the
checked are the useropts and localopts files. connection parameters.
The command line client does not have the connection
configuration data to contact the server. AWSBEH004E The target host port is not defined in
the connection configuration file or the
file_name identifies the configuration file that cannot be
supplied command parameters.
found.
Explanation: "Port" is one of the required parameters
System action: The operation cannot be performed.
for the connection to the command line server.
Operator response: Check whether and why this file
The command line client does not have the connection
is missing. If it has been renamed or moved to another
configuration data to contact the server.
location, rename it or move it back and retry the
operation. If the file cannot be found, uninstall and System action: The operation cannot be performed.
reinstall Tivoli Workload Scheduler on this computer.
Operator response: Check the useropts and localopts
files and ensure that the "port" keyword is defined and
AWSBEH002E The target host computer is not identifies a valid port.
defined in the connection configuration
file or the supplied command Alternatively, supply the port as a command parameter.
parameters. See: The Reference Manual for the full syntax of the
Explanation: "Host" is one of the required parameters connection parameters.
for the connection to the command line server.
The command line client does not have the connection AWSBEH005E The user is not defined in the
configuration data to contact the server. connection configuration file or the
supplied command parameters.
System action: The operation cannot be performed.
Explanation: "User" is one of the required parameters
Operator response: Check the useropts and localopts for the connection to the command line server.
files and ensure that the "host" keyword is defined and
identifies a valid host. The command line client does not have the connection
configuration data to contact the server.
Alternatively, supply the host as a command parameter.
System action: The operation cannot be performed.
See: The Reference Manual for the full syntax of the
connection parameters. Operator response: Check the useropts and localopts
files and ensure that the "username" keyword is
defined and identifies the user making the connection.
AWSBEH003E The protocol is not defined in the
connection configuration file or the Alternatively, supply the user as a command parameter.
supplied command parameters. See: The Reference Manual for the full syntax of the
Explanation: "Protocol" is one of the required connection parameters.
parameters for the connection to the command line
server. AWSBEH006E The password is not defined in the
The command line client does not have the connection connection configuration file or the
configuration data to contact the server. supplied command parameters.

System action: The operation cannot be performed. Explanation: "Password" is one of the required
parameters for the connection to the command line
Operator response: Check the useropts and localopts server.

Chapter 2. Message help 49


AWSBEH007W • AWSBEH012E

The command line client does not have the connection System action: The operation cannot be performed.
configuration data to contact the server.
Operator response: Check that you have supplied the
System action: The operation cannot be performed. correct name and path for the file. Correct the error
found and retry the operation.
Operator response: Check the useropts and localopts
files and ensure that the "password" keyword is
defined and identifies the password of the user making AWSBEH010E An internal error has occurred. A
the connection. function has tried to initialize the HTTP
libraries more than once.
Alternatively, supply the password as a command
parameter. Explanation: See message.
See: The Reference Manual for the full syntax of the System action: The operation is not performed.
connection parameters.
Operator response: Contact IBM Software Support for
assistance.
AWSBEH007W The supplied protocol "protocol" is not
valid. It must be "http" or "https".
AWSBEH011E An error occurred while contacting the
Explanation: "Protocol" is one of the required server "server_name" on port
parameters for the connection to the command line "port_number".
server.
Explanation: See message.
protocol is the value that is not valid.
server_name identifies the server that cannot be
The command line client does not have the connection contacted.
configuration data to contact the server.
port_number identifies the port being used for the
System action: The operation cannot be performed. communication.
Operator response: Check the supplied value of the System action: The operation is not performed.
"protocol" keyword and change it to a valid value
Operator response: Check that the connection
("http" or "https").
parameters (the keywords: host, protocol, port,
See: The Reference Manual for the full syntax of the username, password, proxy, and timeout in the
connection parameters. localopts file or supplied with the command) are
correct. Check that the server is accessible in the
network by pinging it. Fix any errors found and retry
AWSBEH008E The user options properties file
the operation.
"file_name" could not be opened or was
not found.
AWSBEH012E The supplied file "file_name" could not
Explanation: The error occurred while opening the
be found or opened.
user file that contains the connection properties.
Explanation: See message.
file_name identifies the user file that cannot be opened.
System action: The operation is not performed.
The command line client does not have the connection
configuration data to contact the server. Operator response: Check that the file has been
correctly identified. If not, retry the operation,
System action: The operation cannot be performed.
identifying the file correctly.
Operator response: Check whether and why this file
If it has been correctly identified, verify the following:
could not be opened. If it has been renamed or moved
to another location, rename it or move it back and retry v That the file exists. If it does not, create it.
the operation. If the file cannot be found, uninstall and v That the user of Tivoli Workload Scheduler can
reinstall Tivoli Workload Scheduler on this computer. access the file in all modes. If it does not, change the
access permissions.
AWSBEH009E The connection configuration file v That the file has not been locked by another process.
"file_name" identified in the command by If it has, close that process.
the "-file" keyword could not be opened Retry the operation. If the problem persists, contact
or was not found. IBM Software Support for assistance.
Explanation: The command line client does not have
the connection configuration data to contact the server.
file_name identifies the connection parameters file that
cannot be opened.

50 IBM Tivoli Workload Scheduler: Messages


AWSBEH013E • AWSBEH021E

Operator response: The quoted error message might


AWSBEH013E An internal error has occurred.
help you to identify the problem and resolve it, in
WebLib could not allocate memory for
which case retry the operation. If you cannot identify
processing the supplied file.
or solve the problem, contact IBM Software Support for
Explanation: See message. assistance.
System action: The operation is not performed.
AWSBEH018E An error occurred while setting the
Operator response: The file might be too large. Retry
credentials for user ID "user".
the operation with a smaller file. If the problem
persists, contact IBM Software Support for assistance. Explanation: An error occurred when setting the
credentials with the AXIS HTTP libraries.
AWSBEH014E An error occurred while reading the user identifies the user whose credentials cannot be set.
supplied file "file_name".
System action: The operation is not performed.
Explanation: See message.
Operator response: Verify the connection and the user
System action: The operation is not performed. ID and password supplied. If the details are not correct,
correct them and retry the operation. If they are correct,
Operator response: Verify the following:
contact IBM Software Support for assistance.
v That the user of Tivoli Workload Scheduler has read
access to the file. If it does not, change the access
permissions. AWSBEH019W The format of the proxy server
"proxy_server" and its port "port" is not
v That the file has not been locked by another process.
valid.
If it has, close that process.
Explanation: See message.
Retry the operation. If the problem persists, contact
IBM Software Support for assistance. proxy_server and port identify the proxy server
connection information that is not valid.
AWSBEH015E An internal error occurred while System action: The operation is not performed.
initializing the AXIS HTTP libraries.
Operator response: Verify the proxy server and port
Explanation: See message. information supplied. The proxy_server must be a
correctly formed server name, expressed either as a
System action: The operation is not performed.
host name or an IP address. The port must be a number
Operator response: If this is the first time you have between 1 and 65535. Do not supply the colon
tried using the command line client it might be that the separator (:) between server and port; it is supplied by
libraries were not installed correctly, in which case the software. Correct the error and retry the operation.
uninstall and reinstall the command line client, and
retry the operation.
AWSBEH021E The user "user" is not authorized to
If this is not the first time, retry the operation, and if access the server on host "host" using
the error persists, contact IBM Software Support for port "port".
assistance.
Explanation: There has been an authentication failure
on contacting the server.
AWSBEH016E An error occurred while contacting
System action: The operation is not performed.
the server using the AXIS HTTP
libraries. Operator response: Check the following:
Explanation: See message. v Check the supplied values for the indicated fields.
v Check that the user details in the Security file are
System action: The operation is not performed.
correct, and that the user has permission to access
Operator response: Check that the server is accessible the server.
in the network by pinging it. Fix any errors found and v Ensure that your SSL configuration and certificates
retry the operation. If the problem persists, contact IBM are correct.
Software Support.
v If you have made any changes to the SSL
configuration on the server, ensure that the
AWSBEH017E An internal error has occurred "error" application server has been restarted.
while using the AXIS HTTP libraries.
Correct any errors and retry the operation.
Explanation: See message.
System action: The operation is not performed.

Chapter 2. Message help 51


AWSBEH022E • AWSBEH029E

AWSBEH022E The server on host "host" cannot be AWSBEH026E It was not possible to establish an
contacted. SSL communication with the server on
host: "host" using port "port" because of
Explanation: The indicated server cannot be contacted.
the following error: "error".
System action: The operation is not performed.
Explanation: The server can be contacted but the SSL
Operator response: Check that the server is running handshake failed.
and the network is up. Ping the server from the client.
System action: The operation is not performed.
If there is no network problem between the client and
Operator response: Check that the following
the server, check the supplied values for the
parameters in the useropts or localopts file: "port",
connection. Ensure that your SSL configuration and
"clisslcipher", and "clisslservercertificate" match the
certificates are correct. If you have made any changes
required values on the server. Correct any errors and
to the SSL configuration on the server, ensure that the
retry the operation.
application server has been restarted. Correct any errors
and retry the operation.
AWSBEH027E The connection parameters were not
specified completely in your "useropts"
AWSBEH023E Unable to establish communication
or "localopts" file. Correct the file, or
with the server on host "host" using port
submit the connection parameters as
"port".
part of the command syntax.
Explanation: The indicated server can be contacted,
Explanation: See message.
but is not listening on the indicated port.
System action: The command is not performed.
System action: The operation is not performed.
Operator response: Do one of the following:
Operator response: Check that you are using the
correct port number. Check if there is a firewall in place v Edit the "useropts" or "localopts" file, correct the
between the client and the server that is blocking the connection parameters, save the file and resubmit the
indicated port. Correct any errors and retry the command.
operation. v Create a file, insert the connection parameters, save
the file, and resubmit the command, identifying the
file of connection parameters with the "-file"
AWSBEH024E The connection with the server on
attribute.
host "host" has timed out.
v Resubmit the command, adding the connection
Explanation: The timeout is supplied as one of the parameters to the command line as arguments. Run
connection parameters, either as part of the command, <command_name> -U to determine the syntax, or
in a file of connection parameters, or by default from look in the Reference Manual.
the useropts or localopts file.
See: Reference Manual for full details of the connection
System action: The operation is not performed. parameters and their syntax.
Operator response: Increase the value of the timeout
parameter and retry the command. AWSBEH028E The SSL connection using GSKit
(FIPS 140-2 mode active) with the server
AWSBEH025E The server response cannot be fails.
understood. There is a probably a Explanation: See message.
mismatch with language variables,
codesets, codepages, or other System action: The command is not performed.
configuration elements of the Operator response: Check the certificate in the
international communication localopts.
environment.
See: Reference Manual for full details of the connection
Explanation: See message. parameters, certificates, and their syntax.
System action: The operation is not performed.
Operator response: Check that the language variables, AWSBEH029E The SSL connection using OpenSSL
codesets, codepages, or other configuration elements of Toolkit with the server fails.
the international communication environment match on Explanation: See message.
the client and server. Correct any error you find and
retry the command. System action: The command is not performed.
Operator response: Check the certificate in the
localopts.

52 IBM Tivoli Workload Scheduler: Messages


AWSBEH100E • AWSBEH109E

See: Reference Manual for full details of the connection Otherwise, solve the network connection problem and
parameters, certificates, and their syntax. then retry the operation.

AWSBEH100E There is a syntax error in the AWSBEH105E The following HTTP response failure
connection parameters. was received from the server:
"HTTP_return_code".
Explanation: See message.
Explanation: See message.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Check the supplied connection
parameters. You might have mistyped a keyword, or Operator response: Use the information in the
omitted a separator between keywords or between a HTTP_return_code to diagnose and resolve the problem.
keyword and its value. Correct the error and retry the
Check that the server is running and the network is up.
operation.
Ping the server from the client.
If the network is working correctly, the problem might
AWSBEH101E An internal error occurred while
have been temporary. Retry the command.
initializing the WebLib HTTP libraries.
Otherwise, solve the HTTP problem and then retry the
Explanation: See message.
operation.
System action: The operation is not performed.
Operator response: Ensure that the connection AWSBEH106E There is a syntax error. The required
parameters are correct. Retry the operation. If the value for keyword "keyword" is missing.
problem persists, contact IBM Software Support for
Explanation: Each keyword must have an associated
assistance.
value. After the indicated keyword the corresponding
value was not found.
AWSBEH102E No valid command was supplied.
System action: The operation is not performed.
Explanation: You submitted a command string from
Operator response: Verify the syntax of the command.
the command line client but it did not contain a
Correct the error and retry the operation.
recognizable command.
System action: The operation is not performed.
AWSBEH107E There is a syntax error. The supplied
Operator response: Verify the syntax of the command. date is not in the format specified in the
Correct the error and retry the operation. useropts or localopts files.
Explanation: See message.
AWSBEH103E Too many commands have been
System action: The operation is not performed.
supplied, or a command has been
duplicated. Operator response: Either reissue the command using
the correct date format or change the date format in the
Explanation: The command line string contains too
useropts or localopts file.
many commands, or a command has been submitted
twice. Each command string must comprise one
command and its associated attributes. AWSBEH108E There is a syntax error. The format of
the time in the date is incorrect.
System action: The operation is not performed.
Explanation: See message.
Operator response: Verify the syntax of the command.
Correct the error and retry the operation. System action: The operation is not performed.
Operator response: Either reissue the command using
AWSBEH104E The following HTTP communication the correct time format or change the time format in
failure has occurred: "HTTP_return_code". the useropts or localopts file.
Explanation: See message.
AWSBEH109E There is a syntax error. The time zone
System action: The operation is not performed.
is not valid.
Operator response: Check that the server is running
Explanation: See message.
and the network is up. Ping the server from the client.
System action: The operation is not performed.
If the network is working correctly, the problem might
have been temporary. Retry the command. Operator response: Reissue the command using the

Chapter 2. Message help 53


AWSBEH110E • AWSBEH116E

correct time format or change the time format in the


AWSBEH113E There is a syntax error. A keyword has
useropts or localopts file.
been used more than once.
Explanation: See message.
AWSBEH110E There is a syntax error. A start or
finish time in the format "hhmm" is System action: The operation is not performed.
required when you specify a time zone
Operator response: Check the command syntax.
in the "-from" or "-to" options.
Reissue the command, supplying only one instance of
Explanation: One of the following has occurred: each valid keyword.
v The plan "-from" or "-to" time has not been explicitly
defined when a time zone has been used. When you AWSBEH114E There is a syntax error. The "-to"
specify a time zone for the plan "-from" or "-to" date keyword has been specified, but also
you cannot use the default time and so must define the "-for" or the "-days" keywords,
it explicitly. This is to avoid any ambiguity between which is not allowed.
the time zone of the master domain manager and the
time zone defined in the command. If no time zone Explanation: You can extend a plan for a period of
is specified, the default "-from" or "-to" time uses the hours (-for), or a period of days (-days), or both, or
time zone of the master domain manager. until a specific date and time (-to), but you cannot use
-to with the -for and -days keywords.
v You have supplied a plan "-from" or "-to" time that is
not in the format hhmm (note that you must enter the System action: The operation is not performed.
leading zero if the start time is less than 1000).
Operator response: Check the command syntax.
System action: The submitted command cannot be Reissue the command, supplying either "-to", or one or
performed. both of the "-for" or "-days" keywords.
Operator response: Correct the "-from" or "-to" time
definition and retry the command. AWSBEH115E The file "file" does not exist or you do
not have read access to the file.
AWSBEH111E The following internal error occurred Explanation: See message.
while opening the Symphony file:
"error". System action: The operation is not performed.

Explanation: See message. Operator response: Check that the file is identified
correctly, retrying the command with the correct file
System action: The confirm action cannot be executed path and name if it is not.
Operator response: Verify the following: If it is identified correctly, verify the following:
v That the Symphony file exists. Run JnextPlan to v That the file exists, creating it if not.
create it if not. v That the user of Tivoli Workload Scheduler has read
v That the user issuing the command has access rights access to the file.
to the Symphony file. Change the user permissions, v That the file has not been locked by another process.
if not.
Correct any errors you find and rerun the command.
Retry the command. If the problem persists, contact
IBM Software Support for assistance.
AWSBEH116E An error occurred while converting
the globalopts option "globalopts_option"
AWSBEH112W There is a syntax error. The "-from" to the database global option
parameter was ignored because you are "db_global_option".
trying to extend a plan.
Explanation: See message.
Explanation: You are trying to extend the plan, for
which action the "-from" parameter is not required. System action: The operation is not performed.
System action: The command is processed, ignoring Operator response: Check the connection to the
the "-from" parameter. server. If the connection is broken solve the connection
problem and retry the command. If the problem
Operator response: To avoid the reproduction of this persists, contact IBM Software Support for assistance.
message, do not supply a "-from" parameter when you
are extending a plan.

54 IBM Tivoli Workload Scheduler: Messages


AWSBEH118E

AWSBEH118E There is a syntax error. The time


format for the "-for" value is not
"[h]hhmm".
Explanation: See message.
System action: The submitted command cannot be
performed.
Operator response: Correct the value of the "-for" time
definition and retry the command.

Chapter 2. Message help 55


AWSBEI001E • AWSBEI013E

Users program messages - BEI


This section lists error and warning users program messages that could be issued.

The message component code is BEI and the old message set code is 112 in the
″maestro″ message catalog.

AWSBEI001E User "user_name" does not exist. AWSBEI009E An error has occurred. The user
"user_name" has not been updated or
Explanation: See message.
added.
System action: The submitted command cannot be
Explanation: See message.
performed.
System action: The submitted command cannot be
Operator response: Verify that the correct user name
performed.
has been supplied. Correct the user name and retry the
operation. Operator response: Check the log file for any other
messages that might help you to understand what has
happened. Correct the problem and retry the operation.
AWSBEI002E The file "file_name" is empty, or an
error occurred during the conversion of
the contents of the file to UNICODE. AWSBEI010E Cannot open the file "file_name".
No user has been added to or updated Operating system error: "os_error".
in the local database.
Explanation: See message.
Explanation: See message.
System action: The submitted command cannot be
System action: The submitted command cannot be performed.
performed.
Operator response: Use the operating system error
Operator response: Check that the file exists in the message os_error to determine what the problem is.
correct location. Check that the user performing the Correct the problem and retry the operation.
operation has permission to open the file. Check that
the file is not empty. Check the log file for any other
AWSBEI011E The Unicode (UTF-8) name of the
messages that might help you to understand what has
workstation is too long to be stored.
happened. Correct the problem and retry the operation.
Explanation: See message.
AWSBEI003W An internal error has occurred. Cannot System action: The submitted command cannot be
open the audit log file. performed.
Explanation: See message. Operator response: Provide a shorter name.
System action: The submitted command cannot be See also: Reference Guide for rules about workstation
performed. names.
Operator response: Contact IBM Software Support for
assistance. AWSBEI012E The Unicode (UTF-8) name of either
the domain or the user is too long to be
stored.
AWSBEI007E You are not authorized to run this
command. Explanation: See message.
Explanation: You have tried to add, display, delete or System action: The submitted command cannot be
modify a user but your user ID does not have correct performed.
permission in the Security file.
Operator response: Provide a shorter name.
System action: The submitted command cannot be
performed. See also: Reference Guide for rules about domain and
user names.
Operator response: Either ask your Tivoli Workload
Scheduler Administrator to give you "correct"
permission for this action and retry, or log off and log AWSBEI013E The Unicode (UTF-8) password is too
again with a user ID that has the permission for this long to be stored.
action. Explanation: See message.

56 IBM Tivoli Workload Scheduler: Messages


System action: The submitted command cannot be
performed.
Operator response: Provide a shorter password.
See also: Reference Guide for rules about user
passwords.

Chapter 2. Message help 57


AWSBHT001E • AWSBHT021E

Batchman messages - BHT


This section lists error and warning messages that could be issued by the batchman
component.

The message component code is BHT and the old message set code is 201 in the
″maestro″ message catalog.
expired or the account is locked (only for Windows
AWSBHT001E The job "job_name" in file "file_name"
jobs). In this case change the user password using
has failed with the error: error_message
composer
Explanation: Batchman encountered an error v The JCL file name you specified for the job is
launching a job. The job has been put in the state FAIL. incorrect or the file cannot be found (both UNIX and
This can happen for many reasons: Windows). Verify the JCL name you specified in the
v Jobman is not able to open the stdlist file where it job definition exists in the correct directory.
redirects the job standard output and error, because v Access rights to the JCL file or the Tivoli Workload
either it cannot find the directory or it cannot create Scheduler binaries are not correct. Verify that the JCL
it. has the right access rights.
v If the job is run from a file, the user might not have
access to the file.
AWSBHT015W Batchman cannot release a job stream
v The job must run on a hosted extended agent and from its dependencies because the job
the user who must launch the job does not have stream is not in the "holding" state that
permission to access the extended agent method. is required to allow it to be updated.
v Jobman is not able to read the entry of the job in the
Explanation: This message explains why an event has
internal jobtable.
been discarded.
v Jobman is not able to update the record in the
internal jobtable. The situation can occur when a job stream changes its
state before the event that required a release of the
v Jobman cannot retrieve the user’s password.
dependencies (generated by conman or the Job
v The user is not authorized to run the job as root. Scheduling Console) arrived at the workstation where
v Jobman failed to set the GID for the secondary user batchman is running.
group.
System action: Batchman continues, but the event is
v Jobman failed to set the GID for the primary user ignored.
group.
Operator response: No action is required.
v Jobman failed to set the UID.
v Jobman cannot change to the home directory of the
user. AWSBHT016W Batchman cannot release a job from
its dependencies because the job is not
v Jobman failed to set the SID.
in the "holding" state that is required to
v Jobman is not able to launch the MONITOR for the allow it to be updated.
job.
Explanation: This message explains why an event has
v Jobman is not able to fork the job process.
been discarded.
job_name is the name of the job The situation can occur when a job changes its state
(<workstation>#<job_stream >.<job>) that batchman is before the event that required a release of the
launching. file_name is the name of the JCL file. dependencies (generated by conman or the Job
error_message describes the error and includes the Scheduling Console) arrived at the workstation where
operating system error message. batchman is running.
System action: Batchman proceeds. The job has not System action: Batchman continues, but the event is
been launched. ignored.
Operator response: Use the error_message to solve the Operator response: No action is required.
problem.
The most common causes are the following: AWSBHT021E Batchman has received an event to
v The password you specified for the user (within the add a new job stream to the plan, but a
userdata mozart database) is wrong, not valid, job stream with that name already exists
in the Symphony file.
Explanation: See message.

58 IBM Tivoli Workload Scheduler: Messages


AWSBHT027W • AWSBHT069E

System action: Batchman continues, but the event is These could be any of the following:
ignored. v When the command was issued, the resource name
Operator response: Check if two job streams with the was typed incorrectly. Reissue the command, typing
same name have been submitted in quick succession the resource name correctly.
(either the same job stream twice, or 2 different job v When the command was issued, the resource name
streams but with the same name). Normally, you are was typed correctly, but the command identified the
not able to submit two job streams with the same wrong job stream or job. Reissue the command,
name, but it is possible that a synchronization error has typing the job stream or job name correctly.
occurred if they were submitted in quick succession. v The command was issued in error, attempting to
If you have submitted the same job stream twice, you release a resource from a job stream or job that had
need take no action - the second occurrence is ignored. never depended on that resource. Take no action.
v Two operators separately issued the command to
If you have submitted two different job streams with
release the dependencies at about the same time. The
the same name, resubmit the second job stream using
first command to arrive at the workstation has been
an alias name.
correctly processed. The second command would
give this error. Take no action.
AWSBHT027W Batchman has received an event to
add a new job to a job stream, but a job
AWSBHT056E Batchman was unable to add a
with that name already exists in the job
dependency to a job stream or job,
stream in the Symphony file.
because the number of dependencies in
Explanation: See message text. Two or more jobs with the record is already equal to the
the same name can only be present in the "USERJOBS" maximum allowed (40).
job stream.
Explanation: See message.
System action: Batchman continues, but the event is
System action: Batchman, but the event is ignored.
ignored.
Operator response: Wait until the next plan
Operator response: Check if two jobs with the same
generation (JnextPlan) to add a dependency. Even if
name have been submitted in quick succession (either
you delete one or more dependencies from the job
the same jobs twice, or 2 different jobs but with the
stream or job, you can probably not add a new
same name). Normally, you are not able to submit two
dependency until after the next JnextPlan.
jobs with the same name, but it is possible that a
synchronization error has occurred if they were
submitted in quick succession. AWSBHT061E Batchman has received a mailbox
record indicating that the following job
If you have submitted the same job twice, you need
has stopped unexpectedly: job_name
take no action - the second occurrence is ignored.
(job_number).
If you have submitted two different jobs with the same
Explanation: job_name is the name of the job
name, resubmit the second job using an alias name.
(<workstation>#<job_stream>.<job>).
job_number is the number assigned to the job.
AWSBHT044E Batchman could not find the entry for
the following resource: "resource_name" System action: Batchman continues. The indicated job
in the dependency list for the following has stopped.
job stream or job: job_stream_or_job.
Operator response: Use internal policies to determine
Explanation: A conman release sched command has how to handle the stopped job. All jobs depending on
been issued to release the dependencies on the the stopped job wait until the job is rerun successfully
indicated job stream or job. However, the command or until it is cancelled. Stopped jobs that have the
refers to a resource that batchman cannot find as a continue recovery option do not prevent dependent jobs
dependency for job stream or job. from running.
resource_name is the resource name that cannot be
found. AWSBHT069E The following job stream is in the
"stuck" state: job_stream_name.
job_stream_or_job is the name of the job stream or job
that depends on the resource. Explanation: A job steam might become "stuck" for
any of the following reasons:
System action: Batchman proceeds.
v Jobs in the job stream cannot launch because they
Operator response: You need to contact the person depend on a job that has failed. This is the most
who issued the conman release sched command, and common reason.
determine the circumstances in which it was issued.

Chapter 2. Message help 59


AWSBHT070I • AWSBHT229I

v Operator intervention is required for a reply to a create a second resource called, for example,
prompt on one of the jobs in the job stream. "more_tape" and allocate 50 to it, reducing the value of
v A job on which another depends cannot launch "tape" also to 50 (to maintain the same total value).
because its priority is zero. Allocate these two resources equally to the 40 jobs or
job streams so that if all of the jobs were running at the
job_stream_name is the name of the job stream that is same time the total number of holders of either "tape"
stuck. or "more_tape" would be 20, and would never exceed
32.
System action: Batchman continues. The indicated job
has stopped.
AWSBHT210E Batchman encountered an error
Operator response: For a failed job, use your internal because the user name is not defined in
policies to determine how to handle it. You can either the Symphony file.
cancel the job to satisfy the other job dependencies or
rerun it again successfully. Explanation: See message.

For a prompt, reply to the active prompt to change the System action: Batchman proceeds.
status and free a "stuck" job. Operator response: This is an internal error. Contact
For a zero priority, altering the value to any number IBM Software Support for assistance.
greater than 0 changes the status and frees a "stuck"
job. AWSBHT228W The deadline for job stream
job_stream_name has already passed.
AWSBHT070I The following job stream has stopped Explanation: The processing of the job stream is
with one or more failed (abended) jobs: running late and the deadline for completion has
job_stream_name. already passed.
Explanation: See message. System action: Batchman continues to process the job
System action: Batchman continues. The indicated job stream.
stream has completed and stopped. Operator response: None
Operator response: Use internal policies to determine
how to handle the failed job or jobs. AWSBHT229I The latest time that the following job
can start has already passed.job_name.
AWSBHT089E A resource cannot be allocated to a Explanation: See message (corresponds to the Until
job or a job stream because the time in legacy Maestro).
maximum number of resource holders
(32) has been reached. job_name is the name of the job that is late.

Explanation: For each resource defined in a job stream System action: Batchman proceeds.
or job, batchman creates a holder for that resource and Operator response: Use the conman submit command
that job stream or job. Batchman can manage a if you want to run the indicated job.
maximum of 32 active holders for each resource. This
means that no more than 32 job streams or jobs can use
the same resource at the same time.
System action: Batchman continues. The resource is
ignored.
Operator response: Check in the log to determine the
job or job stream that wanted to use the resource. This
job or job stream might need to be rerun when some of
the instances of the required resource have been freed.
If the condition that has given rise to the error is one
that might re-occur, modify the job streams or jobs and
the resource definitions. Split the resource into two or
more resources maintaining the same number of
resource instances between all of them. Distribute these
resources between the job streams or jobs.
For example, suppose you have a resource called "tape"
that has a value of "100". If you have 40 jobs that need
to run at the same time and all need this resource,

60 IBM Tivoli Workload Scheduler: Messages


AWSBHU001E • AWSBHU009E

Conman messages - BHU


This section lists error and warning messages that could be issued by the conman
component.

The message component code is BHU and the old message set code is 202 in the
″maestro″ message catalog.

AWSBHU001E Conman encountered an error when AWSBHU003E Conman encountered an error while
attempting to open the Symphony file: initializing because the Security file
the file does not exist or conman could does not exist or could not be found.
not find it. The following gives more The following gives more details of the
details of the error: error_text. error: error_text
Explanation: See message. Explanation: See message.
error_text is the error message. It supplies you with error_text is an error message.
more details about the error causes.
System action: Conman stops.
System action: The command is not processed.
Operator response: Verify if this file exists. If it does
Operator response: If the Symphony file exists verify not, try to recreate it, as follows:
that the owner is the Tivoli Workload Scheduler user 1. Run the wmaeutil command to stop the connectors.
and that the user has permission to access and modify
2. Run the makesec command to create the Security
it. If the program is not able to read the Symphony file or
file. On Windows you must use the wmaeutil
the Symphony file is not present, follow the procedure
command before using the makesec command,
described in the section in this guide on "Symphony
while on UNIX they can be performed in either
file corruption".
sequence.
See also: The chapter in this guide on ’Symphony file 3. Restart conman.
corruption’.
See also: The chapter on setting security in the
Reference Manual for more details.
AWSBHU002E Conman encountered an error when
attempting to open either the
Mailbox.msg file or the Intercom.msg AWSBHU004E The job logon name you specified is
file. The following gives more details of not valid.
the error: error_text. Explanation: You have issued a command that
Explanation: The file might not exist, or conman includes the job parameter logon or streamlogon. The
might not have permission to access it. value for this parameter includes the string "\\", which
is not valid in a user id.
error_text contains more details about the causes of this
error. System action: The command is not processed.

System action: The command is not processed. Operator response: Modify the value of the job
parameter logon or streamlogon, and resubmit the
Operator response: Check that both of these files command.
exist, and that conman has permission to access them.
To recreate these files, follow this procedure:
AWSBHU009E Conman encountered a problem
1. Run the conman stop command with a wait
trying to read the Symphony file. The
argument
following gives more details of the
2. Run the conman start command. error: error_text

If the problem occurred on z/OS, a memory dump has Explanation: See message.
been taken to aid IBM Software Support with problem error_text is the error message, which provides you
determination. If the problem persists, contact IBM with more details about the error causes.
Software Support, supplying the following information:
System action: Conman stops.
v A tar file of the Tivoli Workload Scheduler work
directory (<TWS_home>) Operator response: Check if the Symphony file exists. If
v The memory dump. it does, verify that the owner is the Tivoli Workload
Scheduler user and that the user has the rights to
See also: The Reference Manual for more details about access and modify it. If the program is not able to read
start and stop commands. the Symphony file or the Symphony file does not exist,

Chapter 2. Message help 61


AWSBHU010E • AWSBHU023E

follow the procedure described in the chapter in this


AWSBHU018E A value specified for a range-limited
guide on "Symphony file corruption".
numeric argument is above the
See also: The chapter in this guide on ’Symphony file maximum permitted value. The
corruption’. permitted range is from: "minimum" to
"maximum".

AWSBHU010E For record # record_number, conman Explanation: See message.


found an incorrect Symphony file record
minimum is the minimum permitted value. maximum is
type: "record_type_found". It was
the maximum permitted value.
expecting the following type:
"record_type_expected". System action: The command is not processed.
Explanation: See message. Operator response: Check the syntax of the issued
command and verify that the values of any
record_number is the record number.
range-limited arguments are within the indicated range.
record_type_expected is the record type expected. Then re-issue the command.

record_type_found is the record type found. See also: The Reference Manual.

System action: Conman stops.


AWSBHU021E The agent on workstation:
Operator response: Try to recreate the Symphony file. workstation_name cannot be started
Follow the procedure described in the chapter in this because it has not got the latest
guide on "Symphony file corruption". If the problem Symphony file version.
persists, contact IBM Software Support for assistance.
Explanation: This error occurs when you use the start
See also: The chapter in this guide on ’Symphony file command to start an agent on a remote workstation
corruption’. that has not been linked for some reason.
workstation_name is the remote workstation name.
AWSBHU016E One of the values specified for a
numeric argument is not numeric. System action: The command is not processed.

Explanation: You have specified a non-numeric value Operator response: Use the conman link command to
to an argument of a command that is expected to be initialize the workstation.
numeric.
See also: The Reference Manual for more details about
System action: The command is not processed. the link command.

Operator response: Check the syntax of the issued


command and verify that the values supplied for all AWSBHU022E The time value specified as an
the arguments are syntactically correct. Then re-issue argument is incorrect. It must be
the command. numeric, between 0000 and 2359.

See also: The Reference Manual. Explanation: See message. Tivoli Workload Scheduler
uses a form of the 24-hour clock without a separator
between minutes and hours, so that, for example, 9:30
AWSBHU017E A value specified for a range-limited a.m. is written as 0930 and 3 p.m. as 1500.
numeric argument is below the
minimum permitted value. The System action: The command is not processed.
permitted range is from: "minimum" to
Operator response: Check the syntax of the issued
"maximum".
command and verify that the values of any time
Explanation: See message. arguments are between 0000 and 2359. Then re-issue
the command.
minimum is the minimum permitted value. maximum is
the maximum permitted value. See also: The Reference Manual.

System action: The command is not processed.


AWSBHU023E You have issued an "opens" job
Operator response: Check the syntax of the issued qualifier with incorrect syntax.
command and verify that the values of any
range-limited arguments are within the indicated range. Explanation: See message.
Then re-issue the command.
System action: The command is not processed.
See also: The Reference Manual.
Operator response: Check the syntax of the issued
command and verify that the values of opens job

62 IBM Tivoli Workload Scheduler: Messages


AWSBHU024E • AWSBHU034E

qualifiers are syntactically correct. Then re-issue the


AWSBHU028E The "recovery" action is not correct. It
command.
must be one of the following: STOP,
See also: The Reference Manual for details of the CONTINUE, RERUN.
conman job qualifiers syntax.
Explanation: You have supplied a recovery action that
is incorrectly typed, or not supported. Only the
AWSBHU024E The mozart directory cannot be following are permitted:
accessed or is missing some files. v recovery=STOP
Explanation: Usually this error happens when the v recovery=CONTINUE
mozart database on the master domain manager is not v recovery=RERUN
accessible to the workstation where you issued the
command, and in one of the following situations: System action: The command is not processed.
v You have tried to add a prompt dependency to a job Operator response: Reissue the command, supplying
or job stream. one of the permitted recovery actions.
v You have tried to submit a job or job stream that has See also: The Reference Manual for full details of the
a prompt dependency. command syntax.
System action: The command is not processed.
Operator response: Verify the mozart directory AWSBHU032E You have issued a "rerun" command
properties. If you want to manage a prompt that does not uniquely identify a
dependency, the mozart directory (<TWSHome>/mozart) workstation.
on the master domain manager must be accessible, Explanation: Conman shows this error when the
either mounted or shared. If the mozart directory is rerun command you issued does not identify a unique
shared and mounted, verify that the Tivoli Workload workstation name in the from argument. This
Scheduler user has the rights to access its files. command cannot be applied to more than one
If you have found an error, correct it and re-issue the workstation at one time.
command. System action: The command is not processed.
If you cannot find any error, contact IBM Software Operator response: Specify the correct workstation
Support for assistance. name in the from argument, without the use of
wildcards, and rerun the command.
AWSBHU025E Conman either cannot find the job See also: The Reference Manual for ’Selecting job
stream in the Symphony file, or the stream in commands’ and the description of the rerun
specified workstation name is not command.
correct.
Explanation: See message. AWSBHU033E You have supplied more instances of
System action: The command is not processed. a dependency option than are permitted
by the issued command.
Operator response: Take the following steps:
Explanation: See message.
1. Look in the Symphony file and verify if the job
stream exists and if its name has been correctly System action: The command is not processed.
specified.
Operator response: Rerun the command specifying
2. If the job stream details are correct, verify that the the correct number of dependency options.
workstation name identifies an existing workstation.
See also: The Reference Manual for more details about
3. If an error is found, correct it and re-issue the
dependencies.
command.
4. If no error is found, the Symphony file might be
corrupt. In this case follow the procedure described AWSBHU034E You have not supplied a mandatory
in the chapter in this guide on "Symphony file selection argument (job, or job stream,
corruption". for example).
Explanation: You have issued a command that has a
If the problem persists, this is an internal error, and mandatory selection argument (to select a job, or job
contact IBM Software Support for assistance. stream, for example) and you did not specify one. The
See also: The Reference Manual for ’Selecting job selection specifies the object or set of objects the
stream in commands’. See also the chapter in this guide command acts on.
on ’Symphony file corruption’. System action: The command is not processed.

Chapter 2. Message help 63


AWSBHU035E • AWSBHU041E

Operator response: Rerun the command specifying a Operator response: Correct the argument keyword to
valid selection argument. one shown in the list , and re-issue the command.
See also: The Reference Manual for details of all See also: The Reference Manual for details of the syntax
command arguments. of the command.

AWSBHU035E You have issued a command with a AWSBHU040E You have issued a command
dependency keyword (follows, needs, containing an incorrect delimiter. The
opens, prompt), but the value associated accepted delimiters are the following:
with the keyword is not valid. delimiters
Explanation: See message. Explanation: See message.
System action: The command is not processed. delimiters is a list of accepted delimiters or qualifiers for
this command.
Operator response: Check that the value associated
with the dependency keyword is syntactically correct, A delimiter or qualifier is a special character that
and that any object it refers to exists. Correct the error separates two commands, selection items, parameters,
and re-issue the command. or values in an argument. There are several types:
See also: The Reference Manual for details of the syntax v The command delimiter: "$" - separates one
of the dependency keywords. command from the next command.
v The argument delimiter: ";" - separates arguments.
AWSBHU037E Conman has stopped with the v The repetition delimiter: "," - separates different
following internal error: "Non-valid trap values, for example range values.
action". v The value delimiter: "=" - separates a keyword and
its value.
Explanation: See message.
v The selection qualifier: - separates selection items
System action: Conman stops.
– "+" - indicates additional selection criteria
Operator response: Contact IBM Software Support for – "~" - indicates exclusion criteria.
assistance.
System action: The command is not processed.

AWSBHU038E Conman cannot run the command Operator response: Correct the delimiter you have
because the command string has too used to conform to the supplied list and to correspond
many characters. to the indicated usage.

Explanation: See message. The number of characters See also: The Reference Manual..
accepted by the command line is operating
system-dependent. AWSBHU041E You have entered the following
System action: The command is not processed. command: "command ", which requires
access to the Symphony file. However,
Operator response: Check your operating system either the Symphony file does not exists
documentation to determine the maximum acceptable or conman cannot find it.
length. Change the command to conform to this
restriction. You might need to divide the command into Explanation: See message.
two or more commands. command is the conman command requiring the
See also: The Reference Manual for details of the Symphony file.
command syntax, and to find ways of reducing the System action: The command is not processed.
number of characters in the command.
Operator response: Follow this procedure:
1. Look for the Symphony file
AWSBHU039E You have issued a command
containing an incorrect argument 2. If the Symphony file exists verify that the owner is
keyword. The acceptable keywords for the Tivoli Workload Scheduler user and that the
this command are as follows: user has the rights to access and modify it
keyword_list 3. If the Symphony file exists, and the access
permissions are correct, it means that it is
Explanation: See message.
corrupted. Follow the procedure described in the
keyword_list is the list of accepted argument keywords. chapter in this guide on "Symphony file
corruption".
System action: The command is not processed.

64 IBM Tivoli Workload Scheduler: Messages


AWSBHU042E • AWSBHU047E

4. If the Symphony file is not present, follow the


AWSBHU045E You have issued the following
procedure described in the chapter in this guide on
command: "command " with one or more
"Symphony file corruption".
arguments, but this command does not
have any arguments.
When you have completed the corrective action, retry
the command. Explanation: See message. For example, use the
command redo to edit and re-issue the previous
See also: The chapter in this guide on ’Symphony file command, but it does not have any arguments. If you
corruption’. type redo showjobs, this message is displayed.
command is a conman command.
AWSBHU042E You have entered the following
command: "command", which requires System action: The command is not processed.
access to the current (latest) Symphony
Operator response: Reissue the command without
file. However, the Symphony file that
arguments.
conman has found does not contain the
latest production plan. See also: The Reference Manual.
Explanation: See message.
AWSBHU046E Conman has encountered an internal
command is the conman command requiring the
error; encountering the following
Symphony file.
incorrect selection type: "selection_type".
System action: The command is not processed. The problem was encountered in the
following source file "file_name", at line
Operator response: Set the production plan (Symphony "line_number".
file) to the current, using the conman setsym
command. Explanation: See message.

See also: The Reference Manual. selection_type is the selection type found.
file_name and line_number identify the line of source
AWSBHU043E You have issued a command that code where the problem was found.
specifies a dependency. However, either
System action: Conman stops.
conman cannot find the dependency in
the Symphony file, or the command has Operator response: Contact IBM Software Support for
an invalid dependency argument. assistance.
Explanation: See message.
AWSBHU047E A command has been supplied
System action: The command is not processed.
without its required selector.
Operator response: Follow this procedure:
Explanation: Conman commands have the following
1. Check the dependency argument that you supplied structure:
is valid and correctly formed.
v The command name

Verify if the object on which the dependency relies v A selector that identifies the object or objects on
exists in the Symphony file. which the command acts. The selector might or
might not use a keyword. For example, the showjobs
See also: The Reference Manual for more details. command has no keyword; you just enter the
identifier of the job you want to look at. However,
the adddep command uses the keywords: job and
AWSBHU044E You have issued a command with a
sched, to identify whether it is acting on a job or a
file dependency, but the path name of
job stream.
the file you have supplied is not fully
qualified (absolute). v One or more arguments that control the action of the
command on the object or objects
Explanation: See message.
System action: The command is not processed. You have not supplied an identifiable selector.

Operator response: Re-issue the command using a System action: The command is not processed.
fully qualified filename. Operator response: Re-issue the command, adding a
See also: The Reference Manual. valid selector after the command name and before the
arguments.
See also: The Reference Manual for full details of the
syntax of the command.

Chapter 2. Message help 65


AWSBHU048E • AWSBHU051E

AWSBHU048E A command has been supplied with AWSBHU050E You have issued a command with a
an ambiguous selector. selector keyword, but the supplied
selector keyword is not valid for this
Explanation: Conman commands have the following
command.
structure:
v The command name Explanation: Conman commands have the following
structure:
v A selector that identifies the object or objects on
which the command acts. The selector might or v The command name
might not use a keyword. For example, the showjobs v A selector that identifies the object or objects on
command has no keyword; you just enter the which the command acts. The selector might or
identifier of the job you want to look at. However, might not use a keyword. For example, the showjobs
the adddep command uses the keywords: job and command has no keyword; you just enter the
sched, to identify whether it is acting on a job or a identifier of the job you want to look at. However,
job stream. the adddep command uses the keywords: job and
v One or more arguments that control the action of the sched, to identify whether it is acting on a job or a
command on the object or objects job stream.
v One or more arguments that control the action of the
The selector supplied does not unambiguously identify command on the object or objects
the object on which the command must act. The
command might require a selector keyword that you The selector keyword supplied is not a valid selector
have not supplied. keyword for this command.
System action: The command is not processed. System action: The command is not processed.
Operator response: Re-issue the command, ensuring Operator response: Re-issue the command, adding a
that the selector contains a keyword, if required, and valid selector after the command name and before the
that the syntax indicated in the Reference Manual has arguments.
been followed.
See also: The Reference Manual for full details of the
See also: The Reference Manual for more details. syntax of the command.

AWSBHU049E You have issued a command with a AWSBHU051E You have issued a command with a
selector keyword, but the supplied valid selector keyword, but have
selector keyword is not valid. omitted to identify the object.
Explanation: Conman commands have the following Explanation: Conman commands have the following
structure: structure:
v The command name v The command name
v A selector that identifies the object or objects on v A selector that identifies the object or objects on
which the command acts. The selector might or which the command acts. The selector might or
might not use a keyword. For example, the showjobs might not use a keyword. For example, the showjobs
command has no keyword; you just enter the command has no keyword; you just enter the
identifier of the job you want to look at. However, identifier of the job you want to look at. However,
the adddep command uses the keywords: job and the adddep command uses the keywords: job and
sched, to identify whether it is acting on a job or a sched, to identify whether it is acting on a job or a
job stream. job stream.
v One or more arguments that control the action of the v One or more arguments that control the action of the
command on the object or objects command on the object or objects

The selector supplied is not a valid selector keyword. You have probably issued a command with its selector
keyword, but have not included the object identifier.
System action: The command is not processed.
For example, issuing adddep job without identifying
Operator response: Re-issue the command, adding a which job.
valid selector after the command name and before the
System action: The command is not processed.
arguments.
Operator response: Re-issue the command, adding a
See also: The Reference Manual for full details of the
valid selector after the command name and before the
syntax of the command.
arguments.
See also: The Reference Manual for more details.

66 IBM Tivoli Workload Scheduler: Messages


AWSBHU052E • AWSBHU060E

AWSBHU052E You have issued a command with the AWSBHU056E You have used the fence command,
job qualifier "state", but the identified but did not supply a value for the new
state is not appropriate for the object priority level, or you supplied it with an
identified in the command. incorrect syntax.
Explanation: See message. For example, stuck is not a Explanation: See message.
valid state for a job and pend is not a valid state for a
System action: The command is not processed.
job stream.
Operator response: Re-issue the fence command
System action: The command is not processed.
providing a value for the priority level. You can enter a
Operator response: Change the value of the state numeric value from 0 to 101, "hi" (= 100), or "go".
argument to a valid state for the object of the
See also: The Reference Manual for full details of the
command, and re-issue the command.
fence command.
See also: The Reference Manual for details of the values
available when the state argument can be used.
AWSBHU058E The command issued for workstation
workstation_name cannot be performed,
AWSBHU053E You have issued a command that because the workstation is an extended
identifies a file, but the path name of agent, where the command is not
the file you have supplied is not fully supported.
qualified (absolute).
Explanation: See message.
Explanation: See message.
workstation_name is the extended agent workstation
System action: The command is not processed. name.
Operator response: Re-issue the command using a System action: The command is not processed.
fully qualified file name.
Operator response: You cannot use this command on
See also: The Reference Manual for full details of the the selected workstation. If you have selected the
command syntax. extended agent workstation in error, change the
command to identify a different workstation and
re-issue the command. If you have selected the wrong
AWSBHU054E You have issued a "show..." command
command, issue a different command.
other than "showjobs", and have used
the argument "argument" without its
associated ";deps" argument. AWSBHU059E You have identified a file name that
has a base name greater than
Explanation: The ;info argument is only used on its
maximum_length bytes. This file name is
own in the showjobs command. In all other commands
not permitted.
where it appears, it is one possible value of the ;deps
argument. Explanation: The file base name is the name of the
file, including the extension and the dot separator, but
System action: The command is not processed.
excluding the directory names in the full path. For
Operator response: Correct the syntax and re-issue the example, "myfilename.txt" is 14 bytes.
command.
maximum_length is the longest file base name accepted.
See also: The Reference Manual.
System action: The command is not processed.
Operator response: Shorten the name of the file so
AWSBHU055E You have used one of the limit
that it is no greater than the value of the
commands, but did not supply a value
maximum_length indicated and re-issue the command.
for the limit, or you supplied it with an
incorrect syntax. See also: The Reference Manual.
Explanation: See message.
AWSBHU060E You have issued a command that has
System action: The command is not processed.
attempted to modify or delete the
Operator response: Re-issue the limit command EXTERNAL job stream. This is not
providing a value for the limit. You can enter 0 through permitted.
1024.
Explanation: The EXTERNAL job stream is used to
See also: The Reference Manual for details of the monitor the status of internetwork dependencies, and
specific command. cannot be modified or deleted.
System action: The command is not processed.

Chapter 2. Message help 67


AWSBHU061E • AWSBHU064E

Operator response: To modify an internetwork If this error arises from this activity, an internal
dependency for a given job you have to use the error has occurred.
conman adddep and deldep commands on that job.
current_manager is the name of the current domain
See also: The Reference Manual for more details about
manager. new_manager is the workstation that you want
the adddep and deldep commands.
to become the new domain manager.
System action: The command is not processed.
AWSBHU061E The domain manager of this
workstation cannot be found in the Operator response: The response depends on what
Symphony file. you were doing when the error occurred:
Explanation: The circumstances are one of the 1. If you were using switchmgr, repeat the command
following: selecting as new_manager a fault-tolerant agent
belonging to your domain. Alternatively, if the
v You issued a switchmgr command specifying a
new_manager workstation is in the domain of the
domain and a new manager.
current_manager, contact IBM Software Support for
v You issued a start command with the mgr option on assistance.
this workstation.
2. If you were using the start ;mgr command, contact
IBM Software Support for assistance.
In either case, you tried to switch to a domain manager
that conman cannot find in the Symphony file.
AWSBHU064E The domain manager "new_manager" is
System action: The command is not processed.
not a fault-tolerant agent.
Operator response: If Tivoli Workload Scheduler is
Explanation: There are two possibilities:
running several switchmgr or start commands from
several workstations, it is possible that it has not 1. You are using the switchmgr command to switch
completed one or more of the commands, and until the domain manager of your domain to a
those commands are completed cannot successfully run workstation that is not a fault-tolerant agent.
this command. Wait until it has completed these 2. You issued a start command with the ;mgr option
activities. on a workstation which is not a fault-tolerant agent
(this method of switching domain managers is
If the problem persists, contact IBM Software Support
deprecated - use the switchmgr command).
for assistance.
new_manager is the workstation that you want to
AWSBHU062W The MGR option is valid only on become the new domain manager.
the local workstation. Ignoring it.
A backup domain manager has to be a fault-tolerant
Explanation: A command has been issued remotely
agent that operates in full status mode, because it has
using the MGR option, which is valid only on the local
to be updated with the status of jobs and job streams
workstation.
running on all other workstations in its domain and in
System action: The command is processed, ignoring subordinate domains.
the MGR option.
System action: The command is not processed.
Operator response: None.
Operator response: The response depends on what
you were doing when the error occurred:
AWSBHU063E The domain manager 1. If you were using switchmgr, repeat the command
"current_manager" is not in the same selecting as new_manager a fault-tolerant agent
domain as the workstation that you operating in full status mode. Alternatively, if the
want to become the new domain new_manager workstation is operating in full status
manager: "new_manager". mode, contact IBM Software Support for assistance.
Explanation: There are two possibilities: 2. If you were using the start ;mgr command, you
1. You are using the switchmgr command to switch cannot run it on this workstation. You must either
the domain manager of your domain to a choose a different fault-tolerant agent, or promote
fault-tolerant agent not belonging to your domain. this agent to be fault-tolerant (see the Planning and
Installation Guide for details.)
2. You issued a start command with the ;mgr option
on the local workstation, to make it exchange roles
with its current domain manager (this method of
switching domain managers is deprecated - use the
switchmgr command).

68 IBM Tivoli Workload Scheduler: Messages


AWSBHU065E • AWSBHU068E

3. If the program is not able to read the Symphony file


AWSBHU065E The specified new domain manager is
or the Symphony file is not present, see the chapter in
not full status.
this guide on "Symphony file corruption". If the
Explanation: There are two possibilities: problem persists, an internal error has occurred, and
1. You are using the switchmgr command to switch contact IBM Software Support for assistance.
the domain manager of your domain to a See also: The Reference Manual for details of the
fault-tolerant agent that is not full status. switchmgr command, and this guide for a description
2. You issued a start command with the ;mgr option of how to solve a corruption of the Symphony file.
on a fault-tolerant agent that is not full status (this
method of switching domain managers is
AWSBHU067E A manager workstation has not been
deprecated - use the switchmgr command).
specified for the switchmgr command.
A backup domain manager has to operate in full status Explanation: See message.
mode, because it has to be updated with the status of
System action: The switchmgr command is not
jobs and job streams running on all other workstations
processed.
in its domain and in subordinate domains.
Operator response: Rerun the switchmgr command
System action: The command is not processed.
ensuring that you supply a domain and a manager
Operator response: The response depends on what workstation.
you were doing when the error occurred:
See also: The Reference Manual for details of the
1. If you were using switchmgr, repeat the command switchmgr command.
either selecting a fault-tolerant agent operating in
full status mode or first setting the mode of the
chosen workstation to full status. AWSBHU068E The following workstation supplied
to the switchmgr command is not in the
To do this, run the composer mod command with
Symphony file: workstation_name.
the ’cpu=<workstation>’ option. When the editor
displays the workstation definition, set the fullstatus Explanation: See message. The workstation that you
option to on. Then run JnextPlan. See the Reference want to become the domain manager must be a
Manual for more details. fault-tolerant agent operating in full status mode.
2. If you were using the start ;mgr command, either workstation_name is the workstation not found in the
choose a different fault-tolerant agent operating in Symphony file.
full status mode on which to run the command, or
change the mode of this workstation, as described System action: The command is not processed.
for the switchmgr command, above.
Operator response: The procedure to follow is as
See also: The Reference Manual. follows:
1. Verify if the supplied workstation name is correct
AWSBHU066E The domain you supplied to the and is a fault-tolerant agent operating in full status
switchmgr command is not in the mode. If it is not, either select a different
Symphony file. workstation that satisfies these criteria, or modify
the selected workstation to satisfy them; then rerun
Explanation: See message. the command.
System action: The switchmgr command is not 2. If the supplied workstation name is correct and the
processed. workstation must have been found in the Symphony
file, the user who issued the command might not
Operator response: The procedure to follow is as have access rights to the Symphony file. Verify that
follows: the owner of the file is the Tivoli Workload
1. Verify if the supplied domain is correct and exists. Scheduler user and that this user has the rights to
If it is not, select a valid domain and rerun the access and modify it. If any of these are not true,
command. correct the problem and rerun the command.
2. If the supplied domain name is correct and the 3. If the program is not able to read the Symphony file
domain must have been found in the Symphony file, or the Symphony file is not present, see the chapter in
the user who issued the command might not have this guide on "Symphony file corruption". . If the
access rights to the Symphony file. Verify that the problem persists, an internal error has occurred, and
owner of the file is the Tivoli Workload Scheduler contact IBM Software Support for assistance.
user and that this user has the rights to access and
See also: The Reference Manual for details of the
modify it. If any of these are not true, correct the
switchmgr command, and this guide for a description
problem and rerun the command.
of how to solve a corruption of the Symphony file.

Chapter 2. Message help 69


AWSBHU069E • AWSBHU075E

System action: The command is not processed.


AWSBHU069E Too many parameters have been
supplied to this switchmgr command. Operator response: Verify that the owner of the files
or the directory selected is the Tivoli Workload
Explanation: See message.
Scheduler user, and that that user has the right to
System action: The command is not processed. access it. Change the user permissions if needed. If the
problem persists, contact IBM Software Support for
Operator response: Rerun the command with the
assistance.
correct syntax.
See also: The Reference Manual for the correct syntax
AWSBHU072E There are no objects that match the
of this command.
selection you have entered.
Explanation: See message.
AWSBHU070E The following domain name could
not be found in the Symphony file: System action: The command is not processed.
domain_name.
Operator response: Check if the object you are trying
Explanation: You have issued a command referring to to select exists. If it exists, you might be using an
a domain name that is not in the Symphony file. incorrect selection format. For example if you use the
selection format wkstation#jobstream.job to select jobs,
domain_name is the domain not found in the Symphony
the workstation has to be the workstation where the job
file.
stream exists, not the workstation where the job is run.
System action: The command is not processed. On the other hand, if you use the format wkstation#job,
the workstation refers to the workstation where the job
Operator response: The procedure to follow is as is run. Verify you are using the right selection format
follows: for the object the command acts on and rerun the
1. Verify if the supplied domain is correct and exists. command.
If it is not, select a valid domain and rerun the
command. See also: The Reference Manual for details of the syntax
and descriptions and examples of how to select objects.
2. If the supplied domain name is correct and the
domain ought ot have been found in the Symphony
file, the user who issued the command might not AWSBHU073E The mozart database does not exist,
have access rights to the Symphony file. Verify that or cannot be opened or accessed. The
the owner of the file is the Tivoli Workload following gives more details of the
Scheduler user and that this user has the rights to error: error_text.
access and modify it. If any of these are not true,
Explanation: See message.
correct the problem and rerun the command.
3. If the program is not able to read the Symphony file error_text is an optional error message. It provides you
or the Symphony file is not present, see the chapter in with more details about the cause of the error.
this guide on "Symphony file corruption". If the System action: Conman stops if it requires the mozart
problem persists, an internal error has occurred, and database to continue. If it can continue in the absence
contact IBM Software Support for assistance. of the file it does so.
See also: The Reference Manual for details of the Operator response: Check that the mozart database
switchmgr command, and this guide for a description exists, is in the correct directory, and that the user has
of how to solve a corruption of the Symphony file. the right to open it. Check also that there is sufficient
disk space for the file to be opened.
AWSBHU071E An error was encountered accessing
the following file: file_name. The AWSBHU075E The following incorrect conman
following gives more details of the command has been used: command.
error: error
Explanation: See message.
Explanation: Conman encountered an error during
the retrieving of the selected file or file list. If you used command is the incorrect command.
the setsym command, conman cannot access the list of System action: The command is not processed.
archived Symphony files or the Symphony file you
selected. Operator response: Check the correct format of the
command you want to use in the Reference Manual.
error is either a Symphony file access error message or a
system error, or an error number. file_name is the file See also: The Reference Manual.
conman is trying to open. If the object is a file list, this
field is blank.

70 IBM Tivoli Workload Scheduler: Messages


AWSBHU076E • AWSBHU084E

AWSBHU076E Conman cannot process the issued AWSBHU080E An internal error has occurred. The
command. The following error occurred: following keyword is not correct:
error_text# "keyword_number". The problem was
encountered in the following source file
Explanation: error_text indicates the reason for the
"file_name", at line "line_number".
problem.
Explanation: Conman does not recognize a keyword.
System action: The command is not processed.
keyword_number is an internal code identifying the
Operator response: Check the error_text for more
keyword that conman does not recognize.
details about the problem.
file_name and line_number identify the line of source
See also: The Reference Manual
code where the problem occurred.
System action: Conman stops.
AWSBHU077E The issued "show" command does not
indicate the object or objects which you Operator response: Contact IBM Software Support for
want the command to show. assistance.
Explanation: See message.
AWSBHU081E An internal error has occurred. The
System action: The command is not processed.
following record type is not a valid
Operator response: Reissue the command using the mailbox record type: "record_type". The
correct syntax. problem was encountered in the
following source file "file_name", at line
See also: The Reference Manual. "line_number".
Explanation: Conman does not recognize a record
AWSBHU078E An internal error has occurred. The type in a mailbox file.
following command number is not
correct for the show command: record_type is the internal record type that conman does
"command_number". The problem was not recognize.
encountered in the following source file
file_name and line_number identify the line of source
"file_name", at line "line_number".
code where the problem occurred.
Explanation: command_number is an internal code
System action: Conman stops.
identifying the command that is not valid.
Operator response: Contact IBM Software Support for
file_name and line_number identify the line of source
assistance.
code where the problem was found.
System action: Conman stops.
AWSBHU083E The issued command cannot be
Operator response: Contact IBM Software Support for applied to the USERJOBS job stream.
assistance.
Explanation: The USERJOBS job stream is a special job
stream that includes all the jobs that are not in the job
AWSBHU079E An internal error has occurred. stream CARRYFORWARD started in the previous
CmdLink needs more workspace; it Production Plan. In the USERJOBS job stream you
needs: "required_space", but only: cannot run commands like cancel, altpri, limit, or
"available_space" is available. rerun.

Explanation: Conman cannot allocate enough space System action: The command is not processed.
for a work buffer.
Operator response: Check that you have used the
required_space is the required space. available_space is the correct command and have not identified the
available space. USERJOBS job stream by mistake.

System action: Conman stops. See also: The Reference Manual for details of the
commands that can be run against the USERJOBS job
Operator response: Contact IBM Software Support for stream.
assistance.

AWSBHU084E The issued command cannot be


applied to the JOBS job stream.
Explanation: The JOBS job stream is a special job
stream that includes all the Ad-Hoc jobs you submit
without specifying a target job stream (argument

Chapter 2. Message help 71


AWSBHU085E • AWSBHU093E

INTO). On this job stream you cannot run commands


AWSBHU090E The job indicated by the "from"
like cancel.
parameter does not exist in the database.
System action: The command is not processed.
Explanation: See message.
Operator response: Check that you have used the
System action: The command is not processed.
correct command and have not identified the JOBS job
stream by mistake. Operator response: Reissue the rerun command,
selecting a valid job name for the from parameter.
See also: The Reference Manual for details of the
commands that can be run against the JOBS job stream. See also: The Reference Manual.

AWSBHU085E This job or job stream is not in the AWSBHU091E The alias or step name supplied for
correct state to apply the issued the job or job stream is not valid.
command.
Explanation: You have either specified an alias name
Explanation: See message. in a submit command or a step name in a rerun
command. The name supplied is not valid. It must start
System action: The command is not processed.
with an alphabetic character, and must contain only
Operator response: Check that you have correctly alphanumeric characters, dashes, and underscores.
identified the job or job stream. Check which states are
System action: The command is not processed.
acceptable for running commands. Wait until the job or
job stream is in the correct state and reissue the Operator response: Rerun the command, supplying a
command. valid alias.
See also: The Reference Manual for the list of states See also: The Reference Manual for a description of
accepted by the command. how to use these aliases.

AWSBHU087E The selected job stream has already AWSBHU092E This job or job stream has too many
been cancelled. dependencies.
Explanation: You cannot add a dependency to, submit Explanation: The maximum number of dependencies
a job to, or kill a job in a cancelled job stream. that you can add to a job or a job stream is 40.
System action: The command is not processed. System action: The job or job stream is not processed.
Operator response: Check that you have correctly Operator response: Rerun the job or job stream,
identified the job stream and have issued the correct defining fewer than 40 dependencies. Note: you might
command. find that removing some dependencies to replace them
with others does not work. For example, if you want to
See also: The Reference Manual.
add 2 dependencies and you have reached the limit of
40, deleting 5 dependencies to add 2 might not work.
AWSBHU088E You cannot rerun user jobs. In these cases replan your job dependencies.

Explanation: See message. See also: The Reference Manual for more details.

System action: The command is not processed.


AWSBHU093E The issued rerun command did not
Operator response: Select a valid job to rerun. specify the step name to use after the
";step" parameter.
AWSBHU089E This parameter is only valid when Explanation: See message.
using the "from" parameter with the
rerun command. System action: The command is not processed.
Explanation: You tried to rerun the job using an "at" Operator response: Reissue the rerun command,
or a "pri" dependency without specifying the "from" supplying the parameter ;step=<step_name> if you
keyword. want to rename the job.
System action: The command is not processed. See also: The Reference Manual for details of the rerun
command.
Operator response: The at and pri dependencies can
only be used if you specify the from parameter.
See also: The Reference Manual for the correct syntax
for the rerun command.

72 IBM Tivoli Workload Scheduler: Messages


AWSBHU094E • AWSBHU112E

permitted syntax for this command.


AWSBHU094E The following dependency keyword
is an unknown dependency:
"dependency_keyword". The problem was AWSBHU097E You have not specified a values for a
encountered in the following source file command qualifier that requires one.
"file_name", at line "line_number".
Explanation: See message.
Explanation: Conman does not recognize the
dependency keyword. System action: The command is not processed.

dependency_keyword is an internal code. Operator response: Correct the command syntax and
rerun the command.
file_name and line_number identify the line in the source
code where the problem was found. See also: The Reference Manual for details of the
permitted syntax for this command.
System action: Conman stops.
Operator response: Probably the Tivoli Workload AWSBHU098E An internal error has occurred. The
Scheduler keyword you are using is not valid for the following internal command is not a
current command. See the Reference Manual for more valid command: command_number. The
details about the valid keywords that you can pass to problem was encountered in the
the command. following source file "file_name", at line
"line_number".
If you are using valid syntax and the error persists,
contact IBM Software Support for assistance. Explanation: Conman has encountered an internal
error.
See also: The Reference Manual.
command_number is an internal code. It represents the
command that conman does not recognize.
AWSBHU095E The job stream or job dependency
dependent_job_stream_or_job was not file_name and line_number identify the line in the source
found in the Symphony file. code where the problem was found.
Explanation: dependent_job_stream_or_job is the System action: Conman stops.
dependent job stream or job name identified by the
"follows" dependency keyword. Operator response: Retry the command. If the error
persists contact IBM Software Support for assistance.
System action: The command is not processed.
Operator response: Select a valid job name and rerun AWSBHU099E The supplied path name exceeds the
the command. You must select a job using the complete maximum size, which is: maximum_size.
format
(<workstation_of_the_job_stream>#<job_stream>.<job> Explanation: See message.
or <job_stream>.<job>). maximum_size is the maximum number of bytes
You can use the ’nocheck’ option. In this case, conman accepted in the path name.
does not check for the existence of the System action: The command is not processed.
<job_stream>.<job> in the Symphony file. However,
batchman does check its existence, and shows an error Operator response: Verify if the file name that you
message in the stdlist if the <job_stream>.<job> does inserted is correct. If it is, move it to a shorter path
not exist. name or rename directories in the path to have shorter
names. Rerun the command using the shorter path.
See also: The Reference Manual.
See also: The Reference Manual.

AWSBHU096E You have specified a range of values


for a command qualifier that does not AWSBHU112E The supplied job specification is not
accept ranges. in the correct format. You can use only
<workstation>#<job> or <job>.
Explanation: Conman gives this error when the
command string includes a range (a value followed by Explanation: See message.
a comma) and the command itself or the qualifier used System action: The command is not processed.
in this command does not accept ranges of values.
Operator response: A job specification is normally one
System action: The command is not processed. of the following:
Operator response: Correct the command syntax and v <workstation>#<job_stream>.<job>
rerun the command. v <job_stream>.<job>
See also: The Reference Manual for details of the v <workstation>#<job>

Chapter 2. Message help 73


AWSBHU114E • AWSBHU121E

v <job>
AWSBHU117E The "switchmgr" command cannot be
completed. The workstation proposed as
However, for this command conman only accepts the the new domain manager:
latter two formats (highlighted). "proposed_manager" is not in the supplied
See also: The Reference Manual for full details. domain: "domain_name".
Explanation: See message.
AWSBHU114E The supplied "switchmgr" command proposed_manager is the proposed domain manager
did not identify the domain, the new identified in the command.
manager, or both.
domain_name is the domain where you want to switch
Explanation: See message. the manager.
System action: The command is not processed. System action: The command is not processed.
Operator response: Reissue the switchmgr command, Operator response: Reissue the command, selecting as
ensuring to identify the domain name and the new proposed_manager a fault-tolerant agent operating in
manager name. full-status mode and belonging to the domain.
See also: The ’switchmgr’ command syntax in the
Reference Manual. AWSBHU119E Wild cards are not permitted in the
domain name parameter of the
AWSBHU115E The user that has issued a "start ;mgr" "switchmgr" command.
or a "switchmgr" command does not Explanation: You have used one or more wildcards
have "stop" rights to the current domain (such as: ’@’ or ’?’) in the specification of the domain
manager: "current_manager". Conman name.
therefore cannot start the new manager:
"proposed_manager". System action: The command is not processed.
Explanation: See message. Operator response: Rerun the command, supplying a
fully qualified domain name.
current_manager is current domain manager.
See also: The Reference Manual for more details about
proposed_manager is the proposed domain manager. domain selection.
System action: The command is not processed.
Operator response: Either the Security file must be AWSBHU121E Conman could not identify the parent
modified to give the user the required access, or a domain of the following workstation:
different user that has this access must issue the workstation_name.
command. Explanation: See message.
See also: The Planning and Installation Guide. workstation_name is a workstation for which the parent
domain could not be found.
AWSBHU116E The user that has issued a "start ;mgr" System action: The command is not processed.
or a "switchmgr" command does not
have "start" rights to the new domain Operator response: Verify the JnextPlan stdlist file
manager: "proposed_manager". to discover if there was a problem during the creation
of the plan (Symphony file). Solve the problem and
Explanation: See message. create a new plan.
proposed_manager is the proposed domain manager. Alternatively, it could be possible that the Symphony file
System action: The command is not processed. is corrupted. See the chapter in this guide on
"Symphony file corruption".
Operator response: Either the Security file must be
modified to give the user the required access, or a If the problem persists, contact IBM Software Support
different user that has this access must issue the for assistance.
command. See also: The chapter in this guide on ’Symphony file
See also: The Planning and Installation Guide. corruption’.

74 IBM Tivoli Workload Scheduler: Messages


AWSBHU122E • AWSBHU131E

AWSBHU122E The supplied command includes both AWSBHU130E The issued command cannot be used.
the options "short" and "single", which It is not allowed by the "centralized
are mutually exclusive. security" option, which is enabled for
this domain.
Explanation: See message.
Explanation: See message.
System action: The command is not processed.
System action: The command is not processed.
Operator response: Correct the syntax to include
either the short or the single option, but not both, and Operator response: Check that it is correct that
rerun the command. centralized security is enabled for the domain:
See also: The Reference Manual for details of the syntax v If it is not, disable the enable centralized security global
of this command. option using optman. However, note that this change
is not effective until next JnextPlan.
v If it is, check if the security options on the master
AWSBHU123E The supplied command includes the
domain manager permit this command to be used:
option "single", which can only be used
when a Job Number is supplied. – If the security options do not permit the command
to be used, consider changing them. However, any
Explanation: See message. changes that you make are not effective until the
System action: The command is not processed. next JnextPlan.
– If the security options permit the command to be
Operator response: Reissue the command, identifying used, the local Symphony file might be corrupt. See
the job by means of its job number (the number that the chapter in this guide on "Symphony file
follows the "#J" in the output of the show job corruption".
command).
See also: The chapter in this guide on ’Symphony file
See also: The Reference Manual for full details. corruption’.

AWSBHU126E A time zone has been specified in a AWSBHU131E Conman has been unable to obtain
time dependency, but time zone use has information about the remote
not been enabled for workstation: workstation "workstation_name" because
workstation_name centralized security, which is enabled
Explanation: See message. for this domain, does not allow it to.

workstation_name is the name of the workstation where Explanation: See message.


the time dependency is to be resolved. System action: The command is not processed.
System action: The command is not processed. Operator response: Check that it is correct that
Operator response: Either rerun the command centralized security is enabled for the domain:
without specifying a time zone or enable time zone use v If it is not, disable the enable centralized security global
at the indicated workstation. option using optman. However, note that this change
is not effective until next JnextPlan.
See also: The Planning and Installation Guide for more
details. v If it is, check if the security options on the master
domain manager permit information to be obtained
from remote workstations:
AWSBHU129E The issued "submit" command
– If the security options do not permit such
includes more than one "nocheck"
information to be obtained, consider changing
keyword after a "follows" keyword,
them. However, any changes that you make are
which is not permitted.
not effective until the next JnextPlan.
Explanation: See message. – If the security options permit such information to
System action: The command is not processed. be obtained, the local Symphony file might be
corrupt. See the chapter in this guide on
Operator response: Rerun the command, supplying "Symphony file corruption".
not more than one nocheck keyword after each follows
keyword. See also: The chapter in this guide on ’Symphony file
corruption’.
See also: The Reference Manual for a description of the
’submit’ command.

Chapter 2. Message help 75


AWSBHU132E • AWSBHU141E

expression, correct it and re-issue the command.


AWSBHU132E You have issued a "show jobs"
command, but the information you are
requesting can only be supplied if the AWSBHU138E The issued "submit" command
keyword "keys" is specified in the includes more than one "wait" keyword
command. after a "follows" keyword, which is not
permitted.
Explanation: See message.
Explanation: See message.
System action: The command is not processed.
System action: The command is not processed.
Operator response: Re-issue the command using the
correct syntax. Operator response: Rerun the command, supplying
not more than one wait keyword after each follows
keyword.
AWSBHU133E You have supplied a return code
condition expression that is longer than See also: The Reference Manual for a description of the
the maximum number of bytes ’submit’ command.
permitted, which is: number.
Explanation: See message. AWSBHU139E The issued "submit" command
includes a "wait" keyword, but you have
System action: The command is not processed.
not supplied the associated numeric
Operator response: Re-issue the command, supplying wait value.
a return code condition expression that is within the
Explanation: See message.
maximum number of bytes permitted.
System action: The command is not processed.
AWSBHU134E You have supplied a script path name Operator response: Rerun the command, supplying a
and a return code condition expression, numeric value for the wait keyword in the format
which are together longer than the wait=<number>, where <number> is the wait period in
maximum number of bytes permitted, seconds, between 0 and 1200.
which is: number.
See also: The Reference Manual for a description of the
Explanation: See message. ’submit’ command.
System action: The command is not processed.
AWSBHU140E The issued "submit" command
Operator response: Re-issue the command, supplying
includes a "wait" keyword, but the
a script path name and a return code condition
associated numeric wait value (seconds)
expression that are together within the maximum
is not between 0 and 1200.
number of bytes permitted.
Explanation: See message.
AWSBHU135E You have supplied a return code System action: The command is not processed.
condition expression that is enclosed in
mismatched or missing quotes. Operator response: Rerun the command, supplying a
numeric value for the wait keyword in the range 0 to
Explanation: The return code condition expression 1200.
must be enclosed (preceded and followed) by the
double quotes character ("). See also: The Reference Manual for a description of the
’submit’ command.
System action: The command is not processed.
Operator response: Re-issue the command, supplying AWSBHU141E The issued "submit" command
a return code condition expression that is enclosed by includes a non-numeric or incorrect
the double quotes character ("). value for a time parameter. The valid
values are from: "minimum_value" to
"maximum_value".
AWSBHU136E You have supplied a return code
condition expression that could not be Explanation: See message.
validated by Conman. The following
gives more details of the error: error_text. minimum_value to maximum_value is the valid range of
numeric values.
Explanation: See message.
System action: The command is not processed.
System action: The command is not processed.
Operator response: Rerun the command, supplying a
Operator response: Check the syntax of the

76 IBM Tivoli Workload Scheduler: Messages


AWSBHU142E • AWSBHU149E

valid numeric value for the time parameter that is about specifying job streams.
within the indicated range.
See also: The Reference Manual for a description of the AWSBHU146E There is a syntax error. The job
’submit’ command. stream ID must be between 1 and 16
bytes long.
AWSBHU142E The issued "submit" command Explanation: See message.
includes a date which is not valid or is
System action: The command is not processed.
not in the correct format. The accepted
format is: "date_format". Operator response: Resubmit the command,
specifying a valid job stream ID.
Explanation: See message.
See also: The Reference Manual for more information
date_format is the permitted format.
about specifying job streams.
System action: The command is not processed.
Operator response: Rerun the command, supplying a AWSBHU147E The keywords "keyword_1" and
valid date in the indicated format. "keyword_2" are mutually exclusive. You
cannot supply both of them.
See also: The Reference Manual for a description of the
’submit’ command. Explanation: See message.
keyword_1 and keyword_2 are the mutually exclusive
AWSBHU143E The action associated with the keywords.
"onuntil" attribute is not correct. It must
System action: The command is not processed.
be one of the following: "suppr", "cont",
"canc". Operator response: Verify the syntax of command.
Resubmit the command specifying only one of the two
Explanation: See message.
indicated keywords.
System action: The command is not processed.
See also: The Reference Manual for more information
Operator response: Rerun the command, supplying a about the syntax of the commands.
valid action for the onuntil attribute.
See also: The Reference Manual for a description of the AWSBHU148E The keyword "keyword" cannot be
’submit’ command. used because the Symphony file was
created by a previous version of Tivoli
Workload Scheduler.
AWSBHU144E There is a syntax error. The schedule
time is not valid or is not in the correct Explanation: keyword is the keyword that cannot be
format. The correct format is "hhmm" or used with a Symphony file created by a previous
"hhmm localopts_date_format". version of Tivoli Workload Scheduler.
Explanation: See message. System action: The command is not processed.
date_format is the permitted format for the date from Operator response: Verify the syntax of command.
the localopts file, for example, "yymmdd". Resubmit the command, omitting the indicated
keyword, or upgrade the workstation where the
System action: The command is not processed.
Symphony file was created to the latest version.
Operator response: Rerun the command, supplying a
See also: The Reference Manual for more information
valid date in the indicated format.
about the syntax of the commands.
See also: The Reference Manual for a description of the
’submit’ command.
AWSBHU149E The job stream or job dependency
dependent_job_stream_or_job with the
AWSBHU145E There is a syntax error. The job specified schedule time was not found
stream ID can contain only in the Symphony file.
alphanumeric characters.
Explanation: dependent_job_stream_or_job is the
Explanation: See message. dependent job stream or job name identified by the
"follows" dependency keyword.
System action: The command is not processed.
System action: The command is not processed.
Operator response: Resubmit the command,
specifying a valid job stream ID. Operator response: Select a valid job stream or job
name and rerun the command.
See also: The Reference Manual for more information

Chapter 2. Message help 77


AWSBHU150W • AWSBHU157E

You can use the ’nocheck’ option. In this case, conman System action: The command is not processed.
does not check for the existence of the
Operator response: Verify the syntax of command.
<job_stream>.<job> in the Symphony file. However,
Resubmit the command specifying the indicated
batchman does check its existence, and shows an error
keywords correctly.
message in the stdlist if the <job_stream>.<job> does
not exist. See also: The Reference Manual for more information
about the syntax of the commands.
See also: The Reference Manual.

AWSBHU154E Either the "nocheck" argument or the


AWSBHU150W An internal error has occurred.
"schedid" argument have been supplied
The program is unable to initialize the
without the required job stream ID.
GSKit libraries.
Explanation: See message.
Explanation: A problem has occurred with the
installation or configuration of the GSKit libraries, or System action: The command is not processed.
both, and they cannot be initialized.
Operator response: Rerun the command, supplying a
System action: The program cannot commence a valid job stream ID with both the "nocheck" and the
secure connection, so stops. "schedid" arguments when they are used.
Operator response: This is an internal error. Contact See also: The Reference Manual for a description of the
IBM Software Support for assistance. ’submit’ command.

AWSBHU151E The supplied date is not valid or is AWSBHU155E You have submitted a command to be
not in the correct format. The correct scheduled as a job (submit docommand)
format is "localopts_date_format". but have not included the command.
Explanation: See message. Explanation: See message.
date_format is the permitted format for the date from System action: The command is not processed.
the localopts file, for example, "yymmdd".
Operator response: Rerun submit docommand ,
System action: The command is not processed. supplying a the command to be scheduled.
Operator response: Rerun the command, supplying a See also: The Reference Manual for a description of the
valid date in the indicated format. ’submit’ command.
See also: The Reference Manual for a description of the
’submit’ command. AWSBHU156E The workstation you specified is
already the event processor.
AWSBHU152E There is more than one job stream Explanation: You have tried to set a workstation as
instance with the given name. You must the new event processor, but it is already the event
refer to a single instance by specifying processor.
either the job stream ID or the
scheduled start time. System action: The command is not processed.

Explanation: See message. Operator response: Check why the selected


workstation is already the event processor. It might be
System action: The command is not processed. because another person has performed the operation
you are trying to perform, or because you typed the
Operator response: Rerun the command, supplying
workstation name incorrectly. Correct the error and
also either the job stream ID or the scheduled start
retry the operation.
time, to uniquely identify the instance of the job stream
in the plan.
AWSBHU157E You have issued a command
See also: The Reference Manual for a description of the
containing at least one incorrect
’submit’ command.
argument keyword.
Explanation: The command contains at least one
AWSBHU153E The keyword "keyword_1" can only be
unsupported keyword.
supplied if the keyword "keyword_2" is
specified. System action: The command is not processed.
Explanation: See message. Operator response: Correct the syntax and retry the
command.
keyword_1 must be supplied only with keyword
keyword_2.

78 IBM Tivoli Workload Scheduler: Messages


AWSBHU410E • AWSBHU509E

See also: The Reference Manual for details of the syntax


AWSBHU504E You have issued a command with a
of the command.
time-related dependency, but have
omitted the keyword "day[s]".
AWSBHU410E The workstation name parameter has
Explanation: You have issued a command with an at,
not been specified for the
until, or deadline dependency. You have also entered a
"command_name" command.
"+" delimiter and a numeric value, which can only be
Explanation: See message. used if accompanied by the keyword day[s].

System action: The operation is not performed. The day[s] qualifier is optional, but if it is present it
must be preceded by the "+" delimiter and a numeric
Operator response: Rerun the command ensuring that value. Similarly, if the delimiter and value are present,
you specify a workstation. so must the qualifier.
See also: The Reference Manual for details of the For example, +5 days.
command.
System action: The command is not processed.

AWSBHU411E Wild cards are not permitted in the Operator response: Re-issue the command, with the
workstation name parameter of the following correction
"command_name" command. v If you intended to supply a day[s] qualifier, add the
Explanation: You have used one or more wildcards keyword to the command string.
(such as: ’@’ or ’?’) while specifying the workstation v If you did not intend to supply a day[s] qualifier,
name. remove the "+" delimiter and the numeric value.
System action: The operation is not performed. See also: The Reference Manual for full details of the
command syntax.
Operator response: Rerun the command, specifying a
fully qualified workstation name.
AWSBHU508E You do not have access to this file or
See also: The Reference Manual for more details about database object.
workstation selection.
Explanation: See message.
AWSBHU412E Too many parameters have been System action: The command is not processed.
supplied to the "command_name"
Operator response: If you are using the display
command.
command, verify that the current user has the rights to
Explanation: See message. access the file that the user is trying to display.
System action: The operation is not performed. In other cases, verify that the object name selected is
correct and that the current user has the Tivoli
Operator response: Rerun the command with the Workload Scheduler Security rights to apply the
correct syntax. command action for the object.
See also: The Reference Manual for the correct syntax When you have identified and corrected the problem
of this command. re-issue the command.
See also: The ’Security Notes’ section of the Planning
AWSBHU503E You have included one or more and Installation Guide for more information about
keywords that are not required for this security.
command. The point beyond which the
keywords are not required is indicated.
AWSBHU509E The requested file cannot be found.
Explanation: See message.
Explanation: See message.
System action: The command is not processed.
System action: The command is not processed.
Operator response: Re-issue the command using the
parameters and keywords only up to the indicated Operator response: Verify the name of the file you
position. want to access. Re-issue the command, ensuring that
the file is specified as fully or partially qualified, as
See also: The Reference Manual for details of the required by the command syntax.
command syntax.
See also: The Reference Manual for details of the syntax
of commands.

Chapter 2. Message help 79


AWSBHU510E • AWSBHU522E

AWSBHU510E The following job already exists: AWSBHU516E You have not supplied a valid alias of
"workstation#job_stream.job". Use the the job you are trying to resubmit.
"rerun" command or supply an "alias"
Explanation: You are trying to resubmit a job. A
with the "submit" command.
resubmitted job cannot have the same name as the
Explanation: See message. original job; it must instead be supplied with an alias
that has a different value from the original job name.
workstation#job_stream.job is the job name that already
exists. System action: The command is not processed.
System action: The command is not processed. Operator response: Resubmit the command, using the
;alias option with a valid new job name. See the
Operator response: If you intended to run a new job,
Reference Manual for more details.
select a different job name. Use the sj command to list
the current jobs in the Symphony file. See also: The Reference Manual.
If you intended to rerun an existing job, use the rerun
command or the submit command with the alias AWSBHU517E The required information cannot be
option. displayed.
See also: The Reference Manual for details of the Explanation: Conman gives this error because it
indicated commands and options. cannot display a file. There are two possibilities:
v No job file: You are trying to display a job file, but
AWSBHU512E The issued command operates on an the job was defined by a command and not in a file.
existing job. However, conman cannot v Remote job: You are trying to display a job
find the indicated job in the Symphony scheduled on another workstation for which the
file, and it is not an external job. definition file is not available locally.
Explanation: See message. System action: The command is not processed.
System action: The command is not processed. Operator response: Use the command sj; info to see
how the job is defined, whether as a command or in a
Operator response: Re-issue the command, identifying
file. This also tells you whether the job is locally or
an existing job by its job name or number.
remotely defined.
Use the sj command to list the current jobs in the
See also: The Reference Manual, in the section
Symphony file.
’Selecting jobs in Commands’.
See also: The Reference Manual for more details about
the command you issued.
AWSBHU518E You cannot add dependencies to a job
or job stream in the "adding" status, or
AWSBHU513E The following job stream already to a job in an "in order" job stream.
exists: "job_stream_name". Supply an
Explanation: You tried to add dependencies to a job
"alias" with the "submit" command.
or job stream but either the job or job stream status is
Explanation: See message. adding or this job belongs to an in order job stream.

job_stream_name is the job stream name. An in order job stream is one where the definition
specifies, by use of the in order keyword, that jobs must
System action: The command is not processed. be run in their definition order.
Operator response: If you intended to run a new job System action: The command is not processed.
stream, select a different job stream name. Use the sc
command to list the current job streams in the Symphony Operator response: If you need to add dependencies
file. to an in order job stream, you need to redefine the job
stream.
If you intended to rerun an existing job stream, use the
submit command with the alias option. See also: The Reference Manual for more details.

See also: The Reference Manual for details of the


indicated commands and options. AWSBHU522E The supplied job name is not in the
database.
Explanation: See message.
System action: The command is not processed.
Operator response: Select a valid job name and rerun
the command.

80 IBM Tivoli Workload Scheduler: Messages


AWSBHU523E • AWSBHU531E

See also: The Reference Manual.


AWSBHU528E A file-descriptor or disk-space error
occurred when conman attempted to
AWSBHU523E You have issued a "link" or an display a JCL file.
"unlink" command on a standalone
Explanation: Conman could not open a work file to
workstation (on which mailman is not
display a JCL file. Either the process has opened too
running).
many file descriptors or there is insufficient storage
Explanation: See message. space available.

System action: The command is not processed. This is an operating system error given by the I/O
library function fdopen.
Operator response: Check that it is correct that the
workstation is standalone. If so, do not use the System action: The command is not processed.
command.
Operator response: Increase the number of file
descriptors a process can open or verify that there is
AWSBHU524E The issued command incorrectly ends enough space available on the file system.
with a delimiter.
If the problem persists, contact IBM Software Support
Explanation: The last character in the command string for assistance.
ends with a delimiter (for example: ";" or "="). This
implies that a keyword or value is missing, because all
AWSBHU529E The following error occurred while
delimiters must be followed by a keyword or value.
conman was displaying a JCL file:
System action: The command is not processed. "error_number".

Operator response: Re-issue the command, either Explanation: Conman gave this error because a
omitting the delimiter or supplying the keyword or system error occurred while it was reading the JCL file.
value that is required by the syntax to follow it.
error_number is the operating system error number,
See also: The Reference Manual for full details of the returned from I/O library function ferror, issued by
syntax for commands. the function fgets().
System action: The command is not processed.
AWSBHU526E The following internal error occurred
Operator response: Verify that the file system is
when conman attempted to display a
working properly and is not full.
JCL file: "error_message".
If the problem persists, contact IBM Software Support
Explanation: See message.
for assistance.
error_message is an operating system error message
returned by the function pipe().
AWSBHU530E The following error occurred while
System action: The command is not processed. conman was writing a work file when
displaying a JCL file: "error_number".
Operator response: Re-issue the command. If the
problem persists, contact IBM Software Support for Explanation: See message.
assistance.
error_number is the system error number, returned from
I/O Library function fprintf.
AWSBHU527E A file-descriptor or disk-space error
System action: The command is not processed.
occurred when conman attempted to
open a JCL file for display. Operator response: Verify that the file system is
working properly and is not full.
Explanation: Conman could not open a JCL file.
Either the process has opened too many file descriptors If the problem persists, contact IBM Software Support
or there is insufficient storage space available. for assistance.
This is an operating system error given by the I/O
Library function fdopen. AWSBHU531E Conman was unable to access the
mozart database or was unable to find a
System action: The command is not processed.
parameter within the database.
Operator response: Increase the number of file
Explanation: See message.
descriptors a process can open or verify that there is
enough space available on the file system. System action: The command is not processed.
If the problem persists, contact IBM Software Support Operator response: Verify that all parameters used in
for assistance. the command have been defined in the mozart

Chapter 2. Message help 81


AWSBHU532E • AWSBHU540E

database, and that the database itself is available and System action: The command is not processed.
viable. Re-issue the command.
Operator response: Re-issue the command, selecting a
See also: The Reference Manual for details on how to valid workstation name.
define and use parameters.
See also: The Reference Manual for information on how
to identify workstations.
AWSBHU532E You have either entered too many
parameters, or the expansion of the
AWSBHU536E The following domain is empty:
parameters you have entered has
domain_name.
exceeded the internal parameter buffer.
Explanation: See message.
Explanation: You can supply a maximum of 20
parameters to this command, and when the parameters domain_name is the name of the empty domain.
are fully expanded they must not occupy more than
4095 bytes. System action: The command is not processed.

System action: The command is not processed. Operator response: This is an internal error. Contact
IBM Software Support.
Operator response: Re-issue the command, reducing
the number of parameters, or re-specify the parameters
to be shorter. AWSBHU537E You have issued the "link" or
"unlink" command to the following
See also: The Reference Manual for more details about workstation within the same domain
the maximum length of various fields. and neither is the domain manager:
workstation_name. This is not allowed.
AWSBHU533E Conman has found a problem with Explanation: The link or unlink commands can only
the syntax of the issued command, but be issued to a workstation in the same domain which is
is unable to determine more precisely a parent or a child of the workstation where the
the nature of the problem. command is issued, not to a peer workstation.
Explanation: See message. workstation_name is the local workstation that you
cannot link to or unlink from.
System action: The command is not processed.
System action: The command is not processed.
Operator response: Check the syntax of the command.
If it is incorrect, re-issue the command with the correct Operator response: If you intended to link to or
syntax. unlink from the domain manager, re-issue the
command, identifying the domain manger workstation.
If the command syntax seems to be correct, an internal
See the Reference Manual
error has occurred. Contact IBM Software Support for
assistance. See also: The Reference Manual for more details about
using the link and unlink commands.
AWSBHU534E The workstation selected for this job
is not a workstation but a workstation AWSBHU539E An internal error has occurred while
class. linking to or unlinking from the
following workstation:
Explanation: The syntax "<workstation_class>#<job>" is
"workstation_name":
not correct. You cannot submit a job to run on a
workstation class. Explanation: The internal message is the following:
"Unknown link case encountered".
System action: The command is not processed.
workstation_name is the workstation name that cannot
Operator response: Re-issue the command, defining
be linked to or unlinked from.
the job to run on a workstation.
System action: The command is not processed.
See also: The Reference Manual for information on how
to identify workstations. Operator response: This is an internal error. Contact
IBM Software Support for assistance.
AWSBHU535E The following workstation is not in
the Symphony file: workstation_name. AWSBHU540E Conman cannot find any domains in
the Symphony file.
Explanation: See message.
Explanation: See message.
workstation_name is the name of the workstation not
found. System action: The command is not processed.

82 IBM Tivoli Workload Scheduler: Messages


AWSBHU541E • AWSBHU548E

Operator response: This normally indicates a problem


AWSBHU544E The supplied path name is longer
with the Symphony file.
than the maximum allowed:
If the Symphony file exists, verify that the owner is the maximum_bytes.
Tivoli Workload Scheduler user and that this user has
Explanation: See message.
the permissions to access and modify the Symphony file.
If you find a problem, correct it and re-issue the System action: The command is not processed.
command.
Operator response: Re-issue the command using a
If the Symphony file is not present or is unreadable, path name shorter than the maximum indicated.
follow the instructions in the chapter in this guide on
See also: The Reference Manual.
"Symphony file corruption".
See also: The chapter in this guide on ’Symphony file
AWSBHU545E You have supplied a path name that
corruption’.
does not match the workstation type:
"workstation_type".
AWSBHU541E You have tried to issue a "start"
Explanation: See message.
command to the following workstation:
"remote_workstation", which is not a child workstation_type is the workstation type of the
of the local workstation: workstation.
"local_workstation".
The type of path to be supplied depends on the type of
Explanation: You cannot start or stop a workstation workstation, as follows:
which is not at a lower point in the Tivoli Workload v UNIX: the path must be specified as a Posix path.
Scheduler hierarchy than the local workstation.
v WNT: the path must be specified as a DOS path.
local_workstation is the local workstation name.
System action: The command is not processed.
remote_workstation is the workstation name you were
trying to start. Operator response: Re-issue the command, supplying
the path in the correct format.
System action: The command is not processed.
Operator response: If you need to start the AWSBHU546E You have supplied either a "tz" or a
remote_workstation, issue the start command from its "timezone" keyword but did not supply
domain manager, or from any other workstation which the time zone name.
is at a higher point in the hierarchy, or from the
remote_workstation itself. Explanation: See message.
System action: The command is not processed.
AWSBHU542E Conman has verified that the versions Operator response: Re-issue the command, supplying
of the Symphony and Database files a time zone name after the tz or timezone keyword.
(Mastsked version) are different.
See also: The Reference Manual for a list of the valid
Explanation: See message. time zone names.
System action: The command is not processed.
Operator response: This is an internal error. Contact AWSBHU547E You have supplied a time zone name
IBM Software Support for assistance. that is longer than 40 bytes.
Explanation: See message.
AWSBHU543E You have supplied the "interactive" System action: The command is not processed.
qualifier keyword to the "submit jobs"
command, which is not valid. Operator response: Re-issue the command, supplying
a valid time zone name, shorter than 40 bytes.
Explanation: See message.
See also: The Reference Manual for a list of the valid
System action: The command is not processed. time zone names.
Operator response: The interactive option is only valid
with sbf and sbd commands. If you want to submit a AWSBHU548E You have supplied a time zone name
job as interactive and this job is defined in the mozart that is not valid.
database, you have to run composer and modify the
job stream containing the job. Explanation: See message.

See also: The Reference Manual for details about System action: The command is not processed.
composer usage.

Chapter 2. Message help 83


AWSBHU549W • AWSBHU559E

Operator response: Re-issue the command, supplying more details about the error causes.
a valid time zone name.
The error is probably one of the following:
See also: The Reference Manual for a list of the valid v The clbox.msg file already exists but the Tivoli
time zone names. Workload Scheduler user does not have write access
to the file.
AWSBHU549W There is a logic error in the v There is insufficient space to create the file.
time-related dependencies. The "until" v The process has exceeded the maximum number of
time occurs before the "at" time. file descriptors.
Explanation: See message. System action: The command is not processed.
System action: The job to which this warning relates Operator response:
is added to the plan. However, it can never run.
1. Verify from the error message where the problem is.
Conman proceeds.
2. Fix the problem and re-issue the command.
Operator response: The simplest way to deal with this
problem is to resubmit the job with an alias, correcting
the dependency logic problem so that the job can run. AWSBHU557W There is a logic error in the
time-related dependencies. The
See also: The Reference Manual for more details about "deadline" time occurs before the "at" or
dependencies. "until" time.
Explanation: See message.
AWSBHU550W There is a logic error in the
time-related dependencies. The System action: The job to which this warning relates
dependency is circular. is added to the plan. However, it can never run.
Conman proceeds.
Explanation: See message.
Operator response: The simplest way to deal with this
System action: The job to which this warning relates problem is to resubmit the job with an alias, correcting
is added to the plan. However, it can never run. the dependency logic problem so that the job can run.
Conman proceeds.
See also: The Reference Manual for more details about
Operator response: The simplest way to deal with this dependencies.
problem is to resubmit the job with an alias, correcting
the dependency logic problem so that the job can run.
AWSBHU558W There is a syntax error in the
See also: The Reference Manual for more details about time-related dependencies. The
dependencies. "onuntil" keyword was specified but the
"until" time was not supplied.
AWSBHU551E You are trying to add the same Explanation: See message.
dependency twice.
System action: The job to which this warning relates
Explanation: See message. is added to the plan. However, it can never run.
System action: The command is not processed. Conman proceeds.

Operator response: Re-issue the command, omitting Operator response: The simplest way to deal with this
the duplicated dependency. problem is to resubmit the job with an alias, correcting
the syntax error so that the job can run.

AWSBHU553E An error has occurred while starting See also: The Reference Manual for more details about
an internal component (clagent). dependencies.

Explanation: See message.


AWSBHU559E The following workstation
System action: The command is not processed. "remote_workstation" cannot be stopped,
Operator response: This is an internal error. Contact because it is in a peer or parent domain
IBM Software Support for assistance. of the following local workstation,
which is not a domain manager:
"local_workstation".
AWSBHU556E The following error occurred while
opening the "clbox.msg" file: "error_text". Explanation: A workstation which is not a domain
manager can only stop workstations in child domains.
Explanation: See message.
System action: The command is not processed.
error_text is an error message. It supplies you with

84 IBM Tivoli Workload Scheduler: Messages


AWSBHU560E • AWSBHU611W

Operator response: To stop the indicated workstation, parameter and reissue the command.
issue the stop command from the workstation itself, its
domain manager, or any workstation in a parent
AWSBHU609E The value specified for the "-timeout"
domain.
connection parameter is not valid. It
must be the number of seconds that the
AWSBHU560E The command "startmon" cannot be command line client is to wait for a
performed, because the Event Driven connection before timing out.
Workload Automation feature is
Explanation: The "-timeout" parameter is one of the
disabled.
connection parameters, supplied as part of the
Explanation: The Event Driven Workload Automation command, in a file of connection parameters, or by
feature has been disabled by optman, which set the default from the useropts or localopts file. It must be
enEventDrivenWorkloadAutomation option to NO. expressed as a number (of seconds). For example, the
value for 30 seconds must be "30", not "30s" or "30
Monman cannot be started.
secs".
System action: The command is not processed.
System action: The operation is not performed.
Operator response: You cannot use this command
Operator response: Retry the command, changing the
when the Event Driven Workload Automation feature
value of the timeout parameter to be a number of
is disabled.
seconds.

AWSBHU600E There is a logic error in the follows


AWSBHU610E The credentials to connect to the
dependencies. The dependency
remote server have not been specified.
circular_dep is circular.
Explanation: When you use the command line client,
Explanation: See message.
it needs to connect to the remote server at the master
circular_dep is the dependency which refers directory or domain manager. For this it requires connection
indirectly to itself. parameters that are supplied as part of the command,
in a file of connection parameters, or by default from
System action: The command is not processed. the useropts or localopts file.
Operator response: Check the details of the supplied conman could not find a set of these parameters to
command. Check the indicated dependency and establish a connection.
determine why it is circular. It might be directly
circular, in that you have erroneously made the System action: The operation is not performed.
scheduled object dependent on itself, or it might be
Operator response: Do one of the following:
more complex with, for example, job A dependent on
job B, which is dependent on job C, which is dependent v Edit the useropts or localopts file and insert the
on job A. Correct the error and resubmit the command. communication parameters. Save the file and rerun
the command.
See also: The Reference Manual for more details about
v Reissue the command, supplying the connection
dependencies.
parameters as command options, or in a file.
See also: The Reference Manual for details of the syntax
AWSBHU606E An error occurred while saving the
of the connection parameters.
user options file:"file"
Explanation: See message.
AWSBHU611W Conman could not initialize the
System action: The operation is not performed. HTTP or HTTPS connection.

Operator response: Verify that there is sufficient space Explanation: Conman is running on a fault-tolerant
in the indicated file system, and that the user of Tivoli agent using the command line client. If the connection
Workload Scheduler has permission to write files in the fails to the command line server on the master domain
indicated directory. manager, conman can continue with limited
functionality, but the connection must be remade before
too much time elapses.
AWSBHU607E The value specified for the "-protocol"
connection parameter is not valid. It System action: conman continues.
must be "http" or "https".
Operator response: You can continue using conman,
Explanation: See message. especially if you think that the connection problem is
temporary.
System action: The operation is not performed.
Operator response: Correct the "-protocol" connection

Chapter 2. Message help 85


AWSBHU612E • AWSBHU619E

However, you must take steps before too long to See also: The Reference Manual for more details about
re-establish the connection. submitting job streams.

AWSBHU612E The port specified by the "-port" AWSBHU615E The submitted job refers to a
connection parameter is not numeric. recovery job which could not be found
in the database.
Explanation: See message.
Explanation: See message.
System action: The operation is not performed.
System action: The submitted command cannot be
Operator response: Locate where you have supplied
performed.
the connection parameters, correct the port, and reissue
the command. Operator response: Check the details of the job you
have submitted. You might have made a mistake when
identifying the recovery job. Check that the job you
AWSBHU613E There are insufficient units of
want to use as the recovery job is available in the
resource "resource" available. The job
database. Resubmit the job, specifying an existing
requires "required_resources" units but
recovery job.
only "available_resources" are available.
See also: The Reference Manual for more details about
Explanation: See message.
submitting job.
resource identifies the resource.
required_resources is the number of requested units of AWSBHU616E More than one job stream matches
the specified resource. your selection.
Uniquely identify the job stream by
available_resources is the number of available units of the specifying its ID or schedule time.
specified resource.
Explanation: See message.
System action: Conman does not proceed.
System action: The submitted command cannot be
Operator response: Check the job requirements. performed.
Determine why the number of available resource units
is inadequate. Try and increase the number of available Operator response: Resubmit the command, uniquely
units or decrease the number of required units, or both. identifying the job stream to be submitted using the
See if it is possible to modify the job so that it uses related job stream ID or schedule time.
fewer resources. Perhaps you can divide into two or
See also: The Reference Manual for more details about
more separate jobs, each of which uses fewer resources.
submitting job streams.
Perhaps you can schedule the job to run on a different
workstation with more resources.
AWSBHU618E The "bulk_discovery" was not
Make whatever modifications you think are necessary
performed because no configuration file
and rerun the job.
was found.
See also: The Reference Manual for more details about
Explanation: The bulk discovery command was not
resources.
forwarded to batchman because the integration
configuration file was not found.
AWSBHU614E No job stream was submitted to
System action: The submitted command cannot be
batchman. It is possible that the
performed.
workstation where the job stream was
defined is set to "ignore". Operator response: Verify that the BmEvents.conf file
is in the TWS home directory. Rerun the bulk discovery
Explanation: No job stream was received by the
command.
server, so no job stream could be submitted to
batchman.
AWSBHU619E The following error occurred
System action: The conman submit sched command
obtaining the monitoring configuration
cannot be processed.
file for workstation "workstation_name":
Operator response: Check that there is nothing in the error_message.
job stream definition that would prevent it from being
Explanation: See message.
scheduled. In particular, check whether the workstation
is set to check "ignore" and that the scheduled time is System action: The operation is not performed.
within the range of the current plan. Correct any errors
Operator response: Contact IBM Software Support for
you find and resubmit the job stream.
assistance.

86 IBM Tivoli Workload Scheduler: Messages


AWSBHU624W • AWSBHU632E

have selected the wrong command, issue a different


AWSBHU624W Either the application server or
command.
appservman, or both, on workstation
"workstation_name" is already stopped.
AWSBHU630E The command issued for workstation
Explanation: See message.
"workstation_name" cannot be performed,
System action: The operation is not performed. because the workstation is a fault
tolerant agent, where the command is
Operator response: The action to take depends on the
not supported.
final outcome you want:
v If you just want the application server to be Explanation: See message.
restarted, issue the command: startWas -direct -user workstation_name is the fault tolerant agent workstation
<user_name> -password <password>. This starts the name.
application server, bypassing appservman. If it is not
stopped, you will receive an appropriate message, System action: The submitted command cannot be
which means that it is appservman which has performed.
stopped. You can restart appservman by issuing the Operator response: You cannot use this command on
command startappserver. the selected workstation. If you have selected the fault
v If you want to stop the application server, but are tolerant agent workstation in error, change the
not certain if it has already stopped, issue the command to identify a different workstation and
command: stopWas -direct -user <user_name> re-issue the command. If you have selected the wrong
-password <password>. This stops the application command, issue a different command.
server, bypassing appservman. If you get a message
that the application server is stopping, it means that
appservman is stopped. AWSBHU631E The command issued for workstation
"workstation_name" cannot be performed,
v If you want both the application server and because the workstation is a standard
appservman to be restarted, issue the command: agent or broker workstation, where the
startappserver. This starts both. If appservman is not command is not supported.
stopped you will receive an appropriate message,
which means that it is the application server which is Explanation: See message.
stopped.
workstation_name is the standard agent or broker
workstation name.
AWSBHU625W The option WAIT is not supported
System action: The submitted command cannot be
for remote workstations. It is ignored.
performed.
Explanation: See message.
Operator response: You cannot use this command on
System action: The operation is not performed. the selected workstation. If you have selected the
standard agent or broker workstation in error, change
Operator response: Choose a supported option and the command to identify a different workstation and
retry the operation. re-issue the command. If you have selected the wrong
command, issue a different command.
AWSBHU626W The application server is not
installed for the local workstation. AWSBHU632E The command issued for workstation
Explanation: A command to start or stop the "workstation_name" cannot be performed,
application server has been run, but the application because the command is not supported.
server is not installed, probably because it is not part of Explanation: See message.
the current configuration.
workstation_name is the workstation name.
The application server is normally installed on the
master domain manager and backup master domain System action: The submitted command cannot be
manager. The application server is installed on other performed.
domain managers and fault-tolerant agents only if the
Operator response: You cannot use this command on
Connector has been installed.
the selected workstation. If you have selected the
System action: The operation is not performed. workstation in error, change the command to identify a
different workstation and re-issue the command. If you
Operator response: You cannot use this command on have selected the wrong command, issue a different
the selected workstation. If you have selected the command.
workstation in error, change the command to identify a
different workstation and re-issue the command. If you

Chapter 2. Message help 87


AWSBHU633W • AWSBHU703E

See also: The Reference Manual for full details of the


AWSBHU633W The event processor workstation is
Workload Service Assurance feature.
set to "ignore" in the production plan.
Explanation: See message.
AWSBHU700E There is a syntax error. A job name,
System action: The operation is not performed. file name or keyword is missing in the
submitted command.
Operator response: Change the workstation setting to
a value other than ignore. You can perform this Explanation: See message.
operation using either the composer command or the
System action: The command is not processed.
Job Scheduling Console.
Operator response: Check the syntax of the command
See also: The Reference Manual for full details of the
in the Reference Manual and resubmit it, adding the
parameters for the composer command line client.
missing item.
See also: The Reference Manual for full syntax of the
AWSBHU634E The command "command_name" cannot
command.
be performed, because the event
processor workstation is set to "ignore"
in the production plan. AWSBHU701E There is a syntax error. The submitted
command appears to contain extra or
Explanation: See message.
duplicated characters, or unmatched
command_name is the issued command. brackets.
System action: The submitted command cannot be Explanation: Conman has verified that additional
performed. characters appear to be attached to a valid keyword or
other parameter. For example, you might have
Operator response: Change the workstation setting to
duplicated a character in a keyword, or the "dot" in a
a value other than ignore. You can perform this
file name.
operation using either the composer command or the
Job Scheduling Console. Alternatively, you have used a pair of brackets in the
command, but the opening bracket does not match the
See also: The Reference Manual for full details of the
closing bracket. For example, you have put an opening
parameters for the composer command line client.
round bracket "(" and a closing square bracket "]".
System action: The command is not processed.
AWSBHU635E A syntax error occurred. The variable
table name must start with an Operator response: Check the syntax of the command
alphabetic character and contain only in the Reference Manual and resubmit it, omitting the
alphanumeric characters. The maximum extra character or characters.
length is 80 bytes.
See also: The Reference Manual for full syntax of the
Explanation: See message. command.
System action: The submitted command cannot be
performed. AWSBHU703E There is a syntax error. The
workstation name must start with an
Operator response: Change the name of the variable
alphabetic character and contain only
table to conform to the rules indicated in the message
alphanumeric characters, dashes, and
and resubmit the command.
underscores.
See also: The Reference Manual for full details of the
Explanation: See message.
variable table.
System action: The command is not processed.
AWSBHU636E The Workload Service Assurance Operator response: Check the syntax of the command
feature is not enabled. in the Reference Manual and resubmit it, supplying a
correctly formatted workstation name.
Explanation: See message.
See also: The Reference Manual for details of how to
Workload Service Assurance is a feature which can be
identify a workstation.
enabled or disabled. At present it is disabled.
System action: The submitted command cannot be
performed.
Operator response: Use optman to enable the
Workload Service Assurance feature.

88 IBM Tivoli Workload Scheduler: Messages


AWSBHU705E • AWSBHU717I

AWSBHU705E There is a syntax error in the AWSBHU712E There is a syntax error. The prompt
workstation name. The "#" symbol was name must be between 1 and 8 bytes
found more than once. long.
Explanation: See message. Explanation: See message.
System action: The command is not processed. System action: The command is not processed.
Operator response: Check the syntax of the command Operator response: Resubmit the command,
in the Reference Manual and resubmit it, omitting the supplying a correctly formatted prompt name.
additional "#" character.
See also: The Reference Manual for details of how to
See also: The Reference Manual for details of how to identify a prompt.
identify a workstation.
AWSBHU713E There is a syntax error. The prompt
AWSBHU707E There is a syntax error. The job name must start with an alphabetic
stream name must start with an character and contain only alphanumeric
alphabetic character and contain only characters, dashes, and underscores.
alphanumeric characters, dashes, and
Explanation: See message.
underscores.
System action: The command is not processed.
Explanation: See message.
Operator response: Resubmit the command,
System action: The command is not processed.
supplying a correctly formatted prompt name.
Operator response: Check the syntax of the command
See also: The Reference Manual for details of how to
in the Reference Manual and resubmit it, supplying a
identify a prompt.
correctly formatted job stream name.
See also: The Reference Manual for details of how to
AWSBHU715E There is a syntax error. The resource
identify a job stream.
name must be between 1 and 8 bytes
long and workstation name must be
AWSBHU710E There is a syntax error. The job name between 1 and 16 bytes
must start with an alphabetic character
Explanation: See message.
and contain only alphanumeric
characters, dashes, and underscores. System action: The command is not processed.
Explanation: See message. Operator response: Resubmit the command,
supplying a correctly formatted resource name.
System action: The command is not processed.
See also: The Reference Manual for details of how to
Operator response: Check the syntax of the command
identify a resource.
in the Reference Manual and resubmit it, supplying a
correctly formatted job name.
AWSBHU716E There is a syntax error. The resource
See also: The Reference Manual for details of how to
name must start with an alphabetic
identify a job.
character and contain only alphanumeric
characters, dashes, and underscores.
AWSBHU711E There is a syntax error. The submitted
Explanation: See message.
command has a job as its object but the
job name has not been supplied. System action: The command is not processed.
Explanation: See message. Operator response: Resubmit the command,
supplying a correctly formatted resource name.
System action: The command is not processed.
See also: The Reference Manual for details of how to
Operator response: Check the syntax of the command
identify a resource.
in the Reference Manual and resubmit it, supplying a
correctly formatted job name.
AWSBHU717I There is a syntax error. Priority might
See also: The Reference Manual for details of how to
be "HI", "GO", or 0-99.
identify a job.
Explanation: See message.
System action: The command is not processed.
Operator response: Resubmit the command,

Chapter 2. Message help 89


AWSBHU718I • AWSBHU728E

supplying a correctly formatted priority specification.


AWSBHU725E There is a syntax error in the
See also: The Reference Manual for details of how to specification of a network dependency.
specify the priority. You have submitted a "Network ID"
enclosed in quotes, but either the quote
characters that you used before and after
AWSBHU718I There is a syntax error. Priority must the ID are mismatched, or one of them
be a numeric value from 0 to 99, "hi" (= is missing.
100), "or go" (= 101).
Explanation: See message.
Explanation: See message.
System action: The command is not processed.
System action: The command is not processed.
Operator response: Rerun the command, ensuring
Operator response: Resubmit the command, that if you need to use quotes to enclose the ID, that
supplying a correctly formatted priority specification. you use the same type of quote character both before
See also: The Reference Manual for details of how to and after the ID.
specify the priority. See also: The Reference Manual.

AWSBHU719E There is a syntax error. You cannot AWSBHU726E There is a syntax error in the
specify a priority higher that 99 (use specification of a network dependency.
"hi" (= 100), "or go" (= 101) instead. The Network ID has not been specified.
Explanation: See message. Explanation: See message.
System action: The command is not processed. System action: The command is not processed.
Operator response: Resubmit the command, Operator response: Rerun the command, specifying
supplying a correctly formatted priority specification. the Network ID before the network delimiter "::"
See also: The Reference Manual for details of how to See also: The Reference Manual.
specify the priority.

AWSBHU727E There is a syntax error in the


AWSBHU721E The supplied user name is too long. specification of a network dependency.
The name can contain up to 47 bytes. If You have defined a network
the name contains special characters it dependency which requires the use of
must be enclosed in quotes ("). quotes, but either the quote characters
Explanation: See message. that you used are mismatched, or one of
them is missing.
System action: The command is not processed.
Explanation: See message.
Operator response: Resubmit the command,
supplying a correctly formatted user name. System action: The command is not processed.

See also: The Reference Manual for details of how to Operator response: Rerun the command, ensuring
specify the user name. that if you need to use quotes that you use the same
type of quote character, and enter both of them.

AWSBHU723E There is a syntax error in the See also: The Reference Manual.
specification of a network dependency.
The syntax of the command indicates AWSBHU728E You have issued a command that
that you wanted to enter a Network ID includes an exclamation point (!), which
to identify a workstation in a different is the delimiter for a domain name.
network, but the ID is blank. However, the exclamation point is not
Explanation: See message. preceded by a valid domain name.

System action: The command is not processed. Explanation: See message.

Operator response: Rerun the command, entering a System action: The command is not processed.
valid Network ID before the network delimiter "::". Operator response: Re-issue the command ensuring
See also: The Reference Manual. that the domain name immediately precedes the
exclamation point (there must be no space between
them).

90 IBM Tivoli Workload Scheduler: Messages


AWSBHU729E • AWSBHU739E

See also: The Reference Manual for details of the syntax


AWSBHU736E There is a syntax error. The alias
of the issued command.
name must start with an alphabetic
character and contain only alphanumeric
AWSBHU729E There is a syntax error. The domain characters, dashes, and underscores.
name must be between 1 and 16 bytes
Explanation: See message.
long.
System action: The command is not processed.
Explanation: See message.
Operator response: Resubmit the command,
System action: The command is not processed.
supplying a correctly formatted alias name.
Operator response: Resubmit the command,
See also: The Reference Manual for details of how to
supplying a correctly formatted domain name.
identify a domain.
See also: The Reference Manual for details of how to
identify a domain.
AWSBHU737E Conman encountered a system error
when attempting to retrieve either the
AWSBHU730E There is a syntax error. The domain current input mode or the current
name must immediately be followed by output mode of the console.
a workstation name.
Explanation: The following internal error has
Explanation: See message. occurred: "Operating system error given on termios.h
Library function tcgetattr or console function
System action: The command is not processed. GetConsoleMode".
Operator response: Resubmit the command, System action: Conman stops.
identifying the workstation as
<domain>!<workstation>, without any spaces between Operator response: This is an internal error. Contact
the exclamation point and the workstation name. IBM Software Support for assistance.

See also: The Reference Manual for details of how to


identify a workstation. AWSBHU738E Conman encountered a system error
when attempting to set either the
console input mode or the console
AWSBHU731E There is a syntax error. The domain output mode.
name must start with an alphabetic
character and contain only alphanumeric Explanation: The following internal error has
characters, dashes, and underscores. occurred: "Operating system error given on termios.h
Library function tcsetattr or console function
Explanation: See message. SetConsoleMode".
System action: The command is not processed. System action: Conman stops.
Operator response: Resubmit the command, Operator response: This is an internal error. Contact
supplying a correctly formatted domain name. IBM Software Support for assistance.
See also: The Reference Manual for details of how to
identify a domain. AWSBHU739E The supplied user is not in the
Symphony file.
AWSBHU733E There is a syntax error in the domain Explanation: See message.
name. The delimiter "!" has been typed
more than once. System action: The command is not processed.
Explanation: See message. Operator response: If an incorrect user name has been
used, resubmit the command, supplying a valid user
System action: The command is not processed. name.
Operator response: Resubmit the command, with just If the user name supplied is correct, the Symphony file
one exclamation point delimiter separating the domain might be corrupt. See the chapter on "Symphony file
from the workstation. corruption" in this guide.
See also: The Reference Manual for details of how to If the problem persists, there is an internal error. In this
identify a domain. case, contact IBM Software Support for assistance.
See also: See the chapter on ’Symphony file
corruption’ in this guide.

Chapter 2. Message help 91


AWSBHU740E • AWSBHU748E

See also: The Reference Manual for more information


AWSBHU740E The new password and the
about specifying jobs.
confirmation password do not match.
Explanation: You are trying to change your password,
AWSBHU746E There is a syntax error in the
but the two versions of the new password that you
specification of a network dependency.
supplied are not the same.
Either the Network ID is missing or it is
System action: The command is not processed. longer than 40 bytes.
Operator response: Resubmit the command, ensuring Explanation: See message text.
to type the new password correctly, twice.
System action: The command is not processed.
Operator response: Resubmit the command, ensuring
AWSBHU741E Conman is unable to open the audit
that the network dependency is correctly specified.
log file.
See also: See the Reference Manual for more details
Explanation: Conman is unable to open the audit log
about Network selection in command line.
file because the open() system call failed for some
unspecified reason.
AWSBHU747E There is a syntax error. The job alias
System action: The command you entered has not
name must be between 1 and 40 bytes.
been executed. Conman continues accepting commands
Explanation: See message.
Operator response: Verify the following before
resubmitting the command: System action: The command is not processed.
v Verify that the user has write access to the audit Operator response: Resubmit the command, ensuring
directory: (<TWS_home>/audit). to specify a valid job alias name.
v Ensure that there is sufficient space in the file system
of the audit directory. See also: The Reference Manual for more information
about specifying job aliases.

AWSBHU743E There is a syntax error in the name. It


must be between 1 and 16 bytes. AWSBHU748E There is a syntax error. The job
stream alias name must be between 1
Explanation: See message. and 16 bytes.
System action: The command is not processed. Explanation: See message.
Operator response: Resubmit the command, ensuring System action: The command is not processed.
to specify a valid workstation name.
Operator response: Resubmit the command, ensuring
See also: The Reference Manual for more information to specify a valid job stream alias name.
about specifying workstations.
See also: The Reference Manual for more information
about specifying job stream aliases.
AWSBHU744E There is a syntax error. The job
stream name must be between 1 and 16
bytes.
Explanation: See message.
System action: The command is not processed.
Operator response: Resubmit the command, ensuring
to specify a valid job stream name.
See also: The Reference Manual for more information
about specifying job streams.

AWSBHU745E There is a syntax error. The job name


must be between 1 and 40 bytes.
Explanation: See message.
System action: The command is not processed.
Operator response: Resubmit the command, ensuring
to specify a valid job name.

92 IBM Tivoli Workload Scheduler: Messages


AWSBHV001E • AWSBHV021E

Stageman messages - BHV


This section lists error and warning messages that could be issued by the stageman
component.

The message component code is BHV and the old message set code is 203 in the
″maestro″ message catalog.
2. If the workstation memory is adequate, try closing
AWSBHV001E An unspecified error was encountered
all the applications that you do not need, and then
building the following message file
rerun JnextPlan.
message_file
3. If the problem persists, reboot the workstation, and
Explanation: Stageman was either unable to build the then rerun JnextPlan.
message file Mailbox.msg or to write an initialization or
4. If the problem persists, contact IBM Software
synchronization record in it.
Support for assistance.
System action: Stageman stops.
See also:: The Release Notes for details of memory
Operator response: Check the file system of requirements.
<TWS_home>/Mailbox.msg to ensure that there is
sufficient space, and that the user has write permission.
AWSBHV020I Stageman has exceeded the internal
When you have corrected the problem, rerun JnextPlan.
limit of 10 duplicate carry forward job
stream instances.
AWSBHV004E An internal error has occurred.
Explanation: See message text.
Stageman has found an incorrect record
in the Symphony file. Stageman System action: Stageman stops.
expected record number "record_number"
to be of type "record_type", but it was Operator response: This is an internal error. It could
not. be the result of a Symphony file corruption. See the
chapter on "Symphony file corruption" in this guide.
Explanation: record_number is the record that
stageman read from the Symphony file. If you have solved the problem, rerun JnextPlan.

record_type is the record type that it was expecting. If the problem persists, contact IBM Software Support
for assistance.
System action: Stageman stops.
See also:: See the chapter on ’Symphony file
Operator response: This is an internal error. It might corruption’ in this guide.
be that the Symphony file is corrupt. See the chapter on
"Symphony file corruption" in this guide. If the
problem persists, contact IBM Software Support for AWSBHV021E An internal error has occurred.
assistance. Stageman has encountered an error
while reading a record from the
See also:: See the chapter on ’Symphony file Symphony file.
corruption’ in this guide.
Explanation: The most likely cause is that the number
of the record it is trying to read exceeds the maximum
AWSBHV019E There is not enough memory to run value allowed or exceeds the actual number of records
stageman. in the Symphony file. Other possible causes are:
Explanation: See message text. v the fstat() or lseek() system calls failed.
v the read() system call failed due to a physical I/O
System action: Stageman stops.
error or to a bad Symphony file descriptor.
Operator response: Check the following: v the read operation was interrupted by a signal.
1. Verify if the workstation has enough memory
System action: Stageman stops.
available. Information about the memory
requirements of Tivoli Workload Scheduler is Operator response: This is an internal error. It might
provided in the Release Notes. If not, you might need be that the Symphony file is corrupt. See the chapter on
to increase the memory of the workstation or make "Symphony file corruption" in this guide. If the
changes in memory management and paging to problem persists, contact IBM Software Support for
make more memory available to stageman. Rerun assistance.
JnextPlan.
See also:: See the chapter on ’Symphony file
corruption’ in this guide.

Chapter 2. Message help 93


AWSBHV022E • AWSBHV027E

AWSBHV022E An internal error has occurred. AWSBHV026E The old Symphony file cannot be
Stageman has encountered a record of renamed to the following file name:
an unknown type while creating the "file_name"
Symphony file.
Explanation: Stageman is trying to archive the old
Explanation: Stageman is trying to create the new Symphony file by renaming it or copying it as
Symphony file with job streams carried forward from the "<TWS_home>/schedlog/M<date_time_stamp>". The
previous plan period’s production, plus job streams rename and the copy have failed.
from the new plan period’s production. To do this it
file_name is the actual name that stageman wants to
has to write the file, resource, and job records for each
give the file.
of these job streams to the new Symphony file. While
writing them, stageman encountered a record of Possible reasons for this are as follows:
unknown type. v The file system is full.
System action: Stageman stops. v Stageman does not have write permission in the
archive directory.
Operator response: This is an internal error. Contact
IBM Software Support for assistance. v Another file already exists with the same name.
v The archive directory is on a mountable file system
that is not mounted.
AWSBHV023E The number of carryforward job
streams exceeds the maximum allowed v The file name stageman wants to use is not
by the Symphony file. permitted by the operating system.

Explanation: A Symphony file in non-expanded mode System action: Stageman proceeds, without archiving
supports a maximum of 676 carryforward job streams. the old Symphony file. The new Symphony file is valid.
A Symphony file in expanded mode supports, in theory, Operator response: The failure to create the archive
5.4 trillion carryforward job streams, but this number is does not impact the correct functioning of Tivoli
in practice reduced by the size limitation of the file. Workload Scheduler. However, attempt to resolve the
System action: Stageman stops. problem so that the following plan period’s old
Symphony file can be correctly archived. Check the
Operator response: Reduce the number of possible causes above to determine what has gone
carryforward job streams. If you are in non-expanded wrong, and correct the error.
Symphony mode, consider moving to expanded mode if
possible (only if there are no MPE systems in your Check the file system of <TWS_home>/schedlog/
network). M<archive_date> to ensure that there is sufficient space,
and that the user has write permission. Delete old
If a job stream is being carried forward longer than archived Symphony files that are no longer needed.
necessary, you can limit the number of days it is
carried forward by specifying the UNTIL time + n days When you have corrected the problem, rerun JnextPlan.
dependency on the job stream itself.
AWSBHV027E The old Symphony file cannot be
AWSBHV024E An internal error has occurred. saved as the following file name:
Stageman has encountered a record from "file_name"
the old Symphony file that is neither a Explanation: Stageman encountered an error
job stream nor a job record. Index: attempting to close the old Symphony file. The file
"sym_rec_array_index", type record_type cannot be saved.
Explanation: While carrying forward the old Symphony file_name is the new name (<TWS_home>/schedlog/
file records for unfinished job streams and jobs, M<date_time_stamp>) of the file that stageman was
stageman encountered a record that was neither a job trying to save.
stream nor a job record.
Possible reasons for this are as follows:
sym_rec_array_index is an index in an array containing
information about each Symphony file record. v The file system is full.
v Stageman does not have write permission in the
record_type is the record type of the Symphony file record archive directory.
in error.
v Another file already exists with the same name.
System action: Stageman stops. v The archive directory is on a mountable file system
Operator response: This is an internal error. Contact that is not mounted.
IBM Software Support for assistance. v The file name stageman wants to use is not
permitted by the operating system.

94 IBM Tivoli Workload Scheduler: Messages


AWSBHV028E • AWSBHV037W

System action: Stageman proceeds. <TWS_home>/Symphony to ensure that there is sufficient


space, that the user has write permission, and that
Operator response: The failure to create the archive
there is not already a Symphony file present. You might
does not impact the correct functioning of Tivoli
want to delete old archived Symphony files that are no
Workload Scheduler. However, attempt to resolve the
longer needed from the <TWS_home>/schedlog/
problem so that the following plan period’s old
directory.
Symphony file can be correctly archived. Check the
possible causes above to determine what has gone When you have corrected the problem, rerun JnextPlan.
wrong, and correct the error.
If the problem persists, contact IBM Software Support
Check the file system of <TWS_home>/schedlog/ for assistance.
M<archive_date> to ensure that there is sufficient space,
and that the user has write permission. Delete old
AWSBHV034W The following job has dependencies
archived Symphony files that are no longer needed.
not carried forward:
When you have corrected the problem, rerun JnextPlan. "workstation_name#job_name".
Explanation: The indicated job has dependencies in
AWSBHV028E The new Symphony file cannot be the production plan (Symphony file), but the jobs on
renamed to the following file name: which it is dependent are not in the Symphony file. This
"file_name". is because those jobs were not in a carryforward job
stream. Stageman adds a prompt for every job not
Explanation: Stageman is unable to rename the
found.
Symnew file to "<TWS_home>/Symphony".
workstation_name#job_name identifies the job with the
file_name is the actual name that stageman wants to
missing dependencies.
give the file.
System action: Stageman proceeds.
Possible reasons for this are as follows:
v The file system is full. Operator response: Respond to the "prompts" to
release the job. You might need to add those jobs in a
v Stageman does not have write permission in the
carryforward job stream.
directory.
v Another file already exists with the same name. See also:: The Reference Manual for more details.

System action: Stageman stops, without saving the


new Symphony file. AWSBHV035W The following job stream has
dependencies not carried forward:
Operator response: Check the file system of "job_stream_name".
<TWS_home>/Symphony to ensure that there is sufficient
space, that the user has write permission, and that Explanation: The indicated job stream has
there is not already a Symphony file present. You might dependencies in the production plan (Symphony file),
want to delete old archived Symphony files that are no but the jobs on which it is dependent are not in the
longer needed from the <TWS_home>/schedlog/ Symphony file. This is because those jobs were not in a
directory. carryforward job stream. Stageman adds a prompt for
every job not found.
When you have corrected the problem, rerun JnextPlan.
job_stream_name identifies the job stream with the
If the problem persists, contact IBM Software Support missing dependencies.
for assistance.
System action: Stageman proceeds.

AWSBHV029E The new Symphony file cannot be Operator response: Respond to the "prompts" to
saved. release the job stream. You might need to add those
jobs in a carryforward job stream.
Explanation: Stageman is unable to save the Symphony
file in "<TWS_home>/Symphony". See also:: The Reference Manual for more details.

Possible reasons for this are as follows:


AWSBHV037W The following job stream or job is in
v The file system is full.
the "adding" state, and has not been
v Stageman does not have write permission in the carried forward:
directory. "workstation#job_stream_or_job".
v Another file already exists with the same name.
Explanation: See message.
System action: Stageman stops, without saving the
workstation#job_stream_or_job is the name of the job
new Symphony file.
stream or job which is in the adding state.
Operator response: Check the file system of

Chapter 2. Message help 95


AWSBHV038E • AWSBHV046E

System action: Stageman proceeds, but the job or job


AWSBHV043E Stageman cannot create the new
stream is not added to the plan.
Symphony file because the settings in
Operator response: Add the carryforward option to the the global options or the localopts file
job stream’s definition. indicate that this workstation is not the
master domain manager.

AWSBHV038E Stageman has been unable to get Explanation: See message.


exclusive access to the Symphony file.
System action: Stageman stops.
You need to shutdown the Tivoli
Workload Scheduler processes. Operator response: Verify that this workstation is the
master domain manager by checking that the master
Explanation: See message.
variable in the global options identifies this
System action: Stageman stops. workstation.

Operator response: v If it does not, run stageman from the master domain
manager.
1. Unlink the workstation and shutdown the Tivoli
Workload Scheduler processes. v If this is the master domain manager, the probable
cause is that the workstation specified by the thiscpu
2. Stop the connectors if present variable in the localopts option file and the
3. Rerun stageman. workstation specified by the master variable in the
global options, are not the same. Change the
localopts file so that they are the same, save the file,
AWSBHV039W No "carry job states" are specified in
stop all Tivoli Workload Scheduler processes, and
the global options. The default behavior
rerun stageman.
of allowing all states has been used.
Explanation: The carry job states setting in the global
AWSBHV044E Stageman is unable to open the
options determines the jobs, by state, that are to be
mailbox file Mailbox.msg. The
included in job streams that are carried forward. If you
following operating system error
make no specific setting, all jobs are included.
message was given: "error_number".
System action: Stageman proceeds.
Explanation: See message.
Operator response: If the job state selection is not
System action: Stageman stops.
what you require, change the carry job states setting in
the global options using optman, stop all Tivoli Operator response: This is an internal error. Contact
Workload Scheduler processes and restart stageman. IBM Software Support for assistance.
See also:: See the ’Optional Customization Topics
(Global Options)’ section in the Planning and Guide. AWSBHV045E An error occurred while opening the
following file: "file_name". The following
gives more details of the error:
AWSBHV040W Only jobs in the following states are
"error_text".
carried forward: "job_states", as defined
in the global options (carry job states). Explanation: See message.
Explanation: See message. file_name is either Symnew or Symphony file. error_text is
the text of the error message indicating why the file
job_states is the list of states of job streams that are
could not be opened.
carried forward.
System action: Stageman stops.
System action: Stageman proceeds.
Operator response: This is an internal error. Contact
Operator response: If the job state selection is not
IBM Software Support for assistance.
what you require, change the carry job states setting in
the global options using optman, stop all Tivoli
Workload Scheduler processes and restart stageman. AWSBHV046E An error occurred while writing the
Symphony file. The following gives
If you want jobs in all states to be carried forward, set
more details of the error: error_text.
the carry job states setting in the global options to null,
using optman. Explanation: Stageman is unable to write to the
Symphony file. One possible reason is that Sinfonia does
See also:: See the ’Optional Customization Topics
not have read permission.
(Global Options)’ section in the Planning and Guide.
error_text is a message indicating why.
If the Sinfonia file is unreadable, error_text could

96 IBM Tivoli Workload Scheduler: Messages


AWSBHV047W • AWSBHV070E

include the symaccs error AWSBCU007E. The full text required argument with the correct syntax.
of the combined message in these circumstances would
To view the stageman syntax, issue the command
be: Error writing the Symphony file: An error has occurred
stageman -U, or look in the Reference Manual.
in the common area used to access the Symphony file.
See also:: The Reference Manual for full details of the
System action: Stageman stops.
stageman syntax.
Operator response: Check the file system of
<TWS_home>/Sinfonia to ensure that there is sufficient
AWSBHV067E The following option is not a valid
space and that the user has read permission. You might
option for this command: "option";
want to delete old archived Symphony files that are no
maybe it has been typed incorrectly.
longer needed from the <TWS_home>/schedlog/
directory. Explanation: See message.
When you have corrected the problem, rerun JnextPlan. System action: Stageman does not start.
If the problem persists, contact IBM Software Support Operator response: Rerun stageman, supplying the
for assistance. required options with the correct syntax.
To view the stageman syntax, issue the command
AWSBHV047W The following job stream: stageman -U, or look in the Reference Manual.
workstation#job_stream"was carried
forward, even though its workstation is See also:: The Reference Manual for full details of the
not present in the Symphony file. stageman syntax.

Explanation: See message.


AWSBHV068W Stageman has been invoked with the
workstation#job_stream is the name of the job stream "option" option, but other options or
whose workstation is not present. arguments have also been supplied. To
use this option supply it without other
System action: Stageman proceeds and carries
options or arguments.
forward the job stream.
Explanation: See message.
Operator response: Check if the job stream contains
any jobs for an operative workstation. If not, cancel the System action: Stageman does not start.
job stream, so that at the plan generation, stageman
does not carry it forward. Operator response: Rerun stageman, supplying the
-parse option on its own. If you did not intend to use
the -parse option, omit it.
AWSBHV065E In the options for stageman there is
an option that has a required argument, To view the stageman syntax, issue the command
but that argument has not been stageman -U, or look in the Reference Manual.
supplied. The option in question is as See also:: The Reference Manual for full details of the
follows: "option". stageman syntax.
Explanation: For example, stageman was run without
either yes, no, or all specified as the argument to the AWSBHV069W The following logfile name begins
-carryforward option. with "-": "log_file_name"
System action: Stageman does not start. Explanation: The log_file_name must not begin with
Operator response: Rerun stageman, adding the "-", but with an alphanumeric character.
missing argument. log_file_name is the name of the logfile.
To see the stageman syntax, issue the command System action: Stageman proceeds without writing to
stageman -U, or look in the Reference Manual. the log file.
See also:: The Reference Manual for full details of the Operator response: This is an internal error. Contact
stageman syntax. IBM Software Support for assistance.

AWSBHV066E The following argument: "argument" is AWSBHV070E Stageman has been submitted with
not valid for the "option" option; perhaps both the "-log" and "-nolog" options,
it has been typed incorrectly. which are mutually exclusive.
Explanation: See message. Explanation: See message.
System action: Stageman does not start. System action: Stageman does not start.
Operator response: Rerun stageman, supplying the Operator response: Rerun stageman, supplying either

Chapter 2. Message help 97


AWSBHV074E • AWSBHV082E

the -log or the -nolog option, but not both. problem persists, contact IBM Software Support for
assistance.
To view the stageman syntax, issue the command
stageman -U, or look in the Reference Manual. See also:: See the chapter on ’Symphony file
corruption’ in this guide.
See also:: The Reference Manual for full details of the
stageman syntax.
AWSBHV081W The pending predecessor
"workstation_name#job_stream_name" has
AWSBHV074E The previous Symphony file is
not been found in the new Production
expanded but the Symnew file is in
Plan as expected. The pending
non-expanded mode. They cannot be
predecessor is marked as an orphan
merged to form the new Symphony file.
predecessor, which must be released or
Explanation: Stageman tried to merge an expanded replaced before the job or job stream in
old Symphony file and a non-expanded Symnew file to which it was defined can be run.
create the new Symphony file. One possibility is the
Explanation: See message text.
following:
1. The databases were expanded, and a Symphony file System action: Stageman marks the pending
was generated. predecessor as an orphan and continues.
2. Then a non-expanded database was restored from Operator response: Check the orphan predecessor
the backup in the mozart directory. dependencies in the Production Plan and release them
3. Compiler was then run to generate a non-expanded to allow the dependent job or job stream to start, or
Symnew file. replace them with dependencies on existing jobs or job
streams.
4. Finally stageman was run, generating this error.
System action: Stageman stops.
AWSBHV082E The previous Symphony file and the
Operator response: If it was your intention to switch Symnew file have the same run number.
to non-expanded mode, then you must remove the They cannot be merged to form the new
expanded Symphony file before rerunning stageman. Symphony file.

Otherwise, correct the database problem by running Explanation: Stageman tried to merge a Symphony file
dbexpand or by restoring the last known good and a Symnew file with the same run number to create
database files in expanded mode. Rerun stageman once the new Symphony file. Probably stageman has been run
the expanded mode files are present. twice on the same Symnew file without resetting the plan
or deleting the Symphony file.

AWSBHV076E Unable to open the audit log. System action: Stageman stops.

Explanation: Stageman is unable to open the audit log Operator response: If it was your intention to recover
file because the open() system call failed for some the Symphony file, you must reset the plan and run
reason. JnextPlan or you have to replace the Symphony file with
the previous one that is archived in the schedlog
System action: Stageman stops. directory before rerunning stageman.
Operator response: Verify access permissions to make Otherwise, rerun JnextPlan. If the error is still present
sure stageman has permission to write to the audit contact IBM Software Support for assistance.
directory: <TWS_home>/audit).
Verify that there is sufficient space in this fileset to
open a file.
When you have resolved the problem, rerun JnextPlan.

AWSBHV080E Stageman is trying to access a record


in the old Symphony file which has a
record number higher than the final
record in the file.
Explanation: See message text.
System action: Stageman stops.
Operator response: This is an internal error. It might
be that the Symphony file is corrupt. See the chapter on
"Symphony file corruption" in this guide. If the

98 IBM Tivoli Workload Scheduler: Messages


AWSBHW001E • AWSBHW022E

Object parsing messages - BHW


This section lists object parsing error and warning messages that could be issued.

The message component code is BHW and the old message set code is 204 in the
″maestro″ message catalog.
Explanation: See AWSBHU711E.
AWSBHW001E A job name, file name or keyword is
missing in the submitted command.
AWSBHW013E There is a syntax error. The prompt
Explanation: See AWSBHU700E.
name must be between 1 and 8 bytes
long.
AWSBHW002E The submitted command appears to
Explanation: See AWSBHU712E.
contain extra or duplicated characters.
Explanation: See AWSBHU701E.
AWSBHW014E There is a syntax error. The prompt
name must start with an alphabetic
AWSBHW003E There is a syntax error in the name. character and contain only alphanumeric
It must be between 1 and 16 bytes. characters, dashes, and underscores.
Explanation: See AWSBHU743E. Explanation: See AWSBHU713E.

AWSBHW004E There is a syntax error in the name. AWSBHW016E There is a syntax error. The resource
It must start with an alphabetic name must be between 1 and 8 bytes
character and contain only alphanumeric long.
characters, dashes, and underscores.
Explanation: See AWSBHU715E.
Explanation: See AWSBHU703E.
AWSBHW017E There is a syntax error. The resource
AWSBHW006E There is a syntax error in the name must start with an alphabetic
workstation name. The "#" symbol was character and contain only alphanumeric
found more than once. characters, dashes, and underscores.
Explanation: See AWSBHU705E. Explanation: See AWSBHU716E.

AWSBHW007E There is a syntax error. The job AWSBHW019W There is a syntax error. Priority must
stream name must be between 1 and 16 be a numeric value from 0 to 99, "hi" (=
bytes. 100), "or go" (= 101).
Explanation: See AWSBHU744E. Explanation: See AWSBHU718E

AWSBHW008E There is a syntax error. The job AWSBHW020E There is a syntax error. You cannot
stream name must start with an specify a priority higher that 99 (use
alphabetic character and contain only "hi" (= 100), "or go" (= 101) instead.
alphanumeric characters, dashes, and
Explanation: See AWSBHU719E.
underscores.
Explanation: See AWSBHU707E.
AWSBHW022E There is a syntax error. The supplied
user name is not valid. The name can
AWSBHW011E There is a syntax error. The job name contain up to 47 bytes. If the name
must start with an alphabetic character contains special characters the full name
and contain only alphanumeric must be enclosed in quotes (").
characters, dashes, and underscores.
Explanation: See message.
Explanation: See AWSBHU710E.
System action: The command is not processed.
Operator response: Resubmit the command,
AWSBHW012E There is a syntax error. The command
supplying a correctly formatted user name.
has a job as its object but the job name
has not been supplied. See also: The Reference Manual for details of how to
specify the user name.

Chapter 2. Message help 99


AWSBHW038E • AWSBHW049E

See also: The Reference Manual for details of the


AWSBHW038E There is a syntax error. The calendar
command syntax.
name must be between 1 and 8 bytes
long. It must also start with an
alphabetic character and contain only AWSBHW046E There is a syntax error. The required
alphanumeric characters, dashes, and workstation name is missing. Specify a
underscores. workstation name or remove the
workstation delimiter.
Explanation: See message.
Explanation: The delimiter that precedes the definition
System action: The command is not processed.
of a workstation name was found in the command
Operator response: Resubmit the command, string, but the workstation name was not specified.
supplying a correctly formatted calendar name.
System action: The submitted command cannot be
See also: The Reference Manual for details of the performed.
command syntax.
Operator response: Resubmit the command, providing
a correctly formatted object definition.
AWSBHW039E There is a syntax error. The
See also: The Reference Manual for details of the
parameter name must be between 1 and
command syntax.
8 bytes long. It must start with an
alphabetic character and contain only
alphanumeric characters, dashes, and AWSBHW047E There is a syntax error. The event
underscores. rule name must start with an alphabetic
character and contain only alphanumeric
Explanation: See message.
characters, dashes, and underscores.
System action: The command is not processed.
Explanation: See message.
Operator response: Resubmit the command,
System action: The submitted command cannot be
supplying a correctly formatted parameter name.
performed.
See also: The Reference Manual for details of the
Operator response: Resubmit the command, providing
command syntax.
a correctly formatted object definition.
See also: The Reference Manual for details of the
AWSBHW040E There is a syntax error. The prompt
command syntax.
name must be between 1 and 8 bytes
long. It must start with an alphabetic
character and contain only alphanumeric AWSBHW048E A syntax error occurred. The variable
characters, dashes, and underscores. table name must not exceed 80 bytes. It
must start with an alphabetic character
Explanation: See message.
and contain only alphanumeric
System action: The command is not processed. characters, dashes, and underscores.
Operator response: Resubmit the command, Explanation: See message.
supplying a correctly formatted prompt name.
System action: The submitted command cannot be
See also: The Reference Manual for details of the performed.
command syntax.
Operator response: Resubmit the command,
supplying a correctly formatted object definition.
AWSBHW045E There is a syntax error. You cannot
See also: The Reference Manual for details of the
specify both dates in a "valid in"
command syntax.
argument using the "@" wildcard.
Explanation: The command has been supplied with a
AWSBHW049E A syntax error occurred. The variable
"valid in" argument, which requires two dates to define
name must not exceed 16 bytes. It must
the period in which the job can be run. One or other of
start with an alphabetic character and
these dates can use the "@" wildcard to mean "any", but
contain only alphanumeric characters,
not both.
dashes, and underscores.
System action: The command is not processed.
Explanation: See message.
Operator response: Resubmit the command,
System action: The submitted command cannot be
supplying a correctly formatted "valid in" argument.
performed.
Operator response: Resubmit the command,

100 IBM Tivoli Workload Scheduler: Messages


AWSBHW050E • AWSBHW051E

supplying a correctly formatted object definition.


See also: The Reference Manual for details of the
command syntax.

AWSBHW050E A syntax error occurred. The


character "." is duplicated in the
variable.
Explanation: See message.
System action: The submitted command cannot be
performed.
Operator response: Resubmit the command,
supplying a correctly formatted variable.
See also: The Reference Manual for details of the
command syntax.

AWSBHW051E A syntax error occurred. The value


specified for the variable must start
with an alphabetic character and contain
only alphanumeric characters, dashes,
and underscores.
Explanation: The correct command syntax is: ren
vb=Current_VariableTable_name.Variable_name
New_Variable_name
You can omit VariableTable_name if the variable is
defined in the default variable table.
System action: The submitted command cannot be
performed.
Operator response: Resubmit the command,
supplying a correctly formatted variable.
See also: The Reference Manual for details of the
command syntax.

Chapter 2. Message help 101


AWSBHX021E • AWSBHX027W

Logman messages - BHX


This section lists error and warning messages that could be issued by logman.

The message component code is BHX and the old message set code is 205 in the
″maestro″ message catalog.
System action: Logman stops.
AWSBHX021E An error occurred opening the
temporary file "file_name". Operator response: An internal error has occurred.
Contact IBM Software Support for assistance.
Explanation: See message.
file_name is the file that cannot be opened.
AWSBHX027W The value specified for the
System action: Logman stops. "-timeout" connection parameter is not
valid. It must be the number of seconds
Operator response: Check the following:
that the command line client is to wait
v That the file exists for a connection before timing out.
v That the file is in the correct directory
Explanation: The "-timeout" parameter is one of the
v That the file has read permission connection parameters. These are supplied: as part of
v That there is sufficient disk space to open and read a the command, in a file of connection parameters, or by
file default from the useropts or localopts file. It must be
v That there are sufficient file descriptors available to expressed as a number (of seconds). For example, the
open a file. value for 30 seconds must be "30", not "30s" or "30
secs".
Correct any errors that you find, and restart logman. System action: The operation is not performed.
Operator response: Retry the command, changing the
AWSBHX022E An internal error occurred while value of the timeout parameter to be a number of
initializing the HTTP communication. seconds.
The library returned this error
"error_message".
Explanation: See message.
error_message is the reason for the error returned by the
library.
System action: Logman stops.
Operator response: An internal error has occurred.
Contact IBM Software Support for assistance.

AWSBHX023E An internal error occurred while


sending data to the server. The error
message is "error_message".
Explanation: See message.
error_message is the reason for the error.
System action: Logman stops.
Operator response: An internal error has occurred.
Contact IBM Software Support for assistance.

AWSBHX024E An internal error has occurred. The


server has returned an error code.
RC=server_return_code
Explanation: See message.
server_return_code is the return code returned by the
server.

102 IBM Tivoli Workload Scheduler: Messages


AWSBHZ001E • AWSBHZ010E

Schedulr messages - BHZ


This section lists error and warning messages that could be issued by the schedulr
component.

The message component code is BHZ and the old message set code is 207 in the
″maestro″ message catalog.
See also: The Release Notes for details of memory
AWSBHZ001E Schedulr cannot be run on this
requirements.
workstation, because the settings in the
global options or the localopts file
indicate that this workstation is not the AWSBHZ003W The submitted job stream has not
master domain manager. been found or the job stream name is
too long.
Explanation: See message.
Explanation: See message.
A common reason for this problem is that the
procedure for switching to the backup master domain System action: The program proceeds.
manager has not been followed correctly.
Operator response: Resubmit the command, ensuring
System action: The program stops. that all job streams that you ask schedulr to use exist,
and have correctly-formed valid names.
Operator response: Verify that this workstation is the
master domain manager by checking that the master See also: The Reference Manual for details about job
variable in the global options identifies this stream names and how to invoke them for schedulr.
workstation.
v If it does not, run schedulr from the master domain AWSBHZ008E Schedulr was unable to open the
manager. prodsked file for the following reason:
v If this is the master domain manager, the probable "error_message".
cause is that the workstation specified by the thiscpu
variable in the localopts option file and the Explanation: Some possible reasons are that the file
workstation specified by the master variable in the has been locked, or the user running schedulr does not
global options, are not the same. Change the have the rights to open it.
localopts file so that they are the same, save the file, error_message describes the error and includes the
stop all Tivoli Workload Scheduler processes, and operating system error message.
rerun schedulr.
System action: The program stops.

AWSBHZ002E There is not enough memory Operator response: Attempt to correct the error given
available to run schedulr. in the message. In any case it is worthwhile removing
the old prodsked file if it exists, and verifying that the
Explanation: See message. user of Tivoli Workload Scheduler has access rights to
System action: The program cannot start. the Tivoli Workload Scheduler home directory.

Operator response: Check the following:


AWSBHZ009E You have supplied a date with the
1. Verify if the workstation has enough memory "-date" option, but the supplied date is
available. Information about the memory not in the correct format.
requirements of Tivoli Workload Scheduler is
provided in the Release Notes. If not, you might need Explanation: See message.
to increase the memory of the workstation or make
System action: Schedulr prompts you for a new date.
changes in memory management and paging to
make more memory available to schedulr. Rerun Operator response: Provide a date in the correct
schedulr. format: "<mm>/<dd>/<[yy]yy>".
2. If the workstation memory is adequate, try closing
all the applications that you do not need, and then AWSBHZ010E Schedulr has encountered the
rerun schedulr. following error when trying to find a
3. If the problem persists, reboot the workstation, and job stream in the mastsked database:
then rerun schedulr. "error_text"
4. If the problem persists, contact IBM Software Explanation: See message.
Support for assistance.
error_text is the message indicating why the error

Chapter 2. Message help 103


AWSBHZ011E • AWSBHZ017E

occurred. The mastsked database might be corrupted. error_message contains the reason for the error and
includes the operating system error message. The
System action: Schedulr stops.
calendars database might be corrupted.
Operator response: To rebuild the mastsked database,
System action: Schedulr stops.
run composer and issue the build mastsked command.
Rerun schedulr. If the problem persists, contact IBM Operator response: To rebuild the calendars database,
Software Support for assistance. run composer and issue the build calendars command.
Rerun schedulr. If the problem persists, contact IBM
Software Support for assistance.
AWSBHZ011E Schedulr encountered the following
error while checking to see if a date is
defined for a particular calendar in the AWSBHZ015E Schedulr encountered the following
calendars database: "error_text". error while trying to lock the mastsked
or job.sched databases: "error_message"
Explanation: See message.
Explanation: See message. These databases are locked
error_text is the message indicating why the error
before schedulr starts selecting the job streams that are
occurred. The calendars database might be corrupted.
to be included in the production period. Schedulr
System action: Schedulr stops. might not be able to lock the mastsked and job.sched
databases because the databases might be locked by
Operator response: To rebuild the calendars database, another process.
run composer and issue the build calendars command.
Rerun schedulr. If the problem persists, contact IBM error_message contains the reason for the error and
Software Support for assistance. includes the operating system error message.
System action: Schedulr stops.
AWSBHZ012E Schedulr encountered the following
Operator response: Determine if another process has
error while searching for a specific
locked the databases, using the operating system tools
calendar in the calendars database:
(for example, fuser). Wait till that process has finished,
"error_text".
or stop it if you are certain that you can safely do so.
Explanation: See message. Rerun schedulr. If the problem persists, contact IBM
Software Support for assistance.
error_text is the message indicating why the error
occurred. The calendars database might be corrupted.
AWSBHZ016E An internal error has occurred. While
System action: Schedulr stops. processing the mastsked database,
Operator response: To rebuild the calendars database, schedulr was unable to add a job stream
run composer and issue the "build calendars" dependency to the internal table used
command. Rerun schedulr. If the problem persists, by the resolve dependencies functions.
contact IBM Software Support for assistance. Explanation: The internal error is: "Not allowed to call
resolve function".
AWSBHZ013E Schedulr encountered the following System action: Schedulr stops.
error while reading a job stream from
the mastsked database: "error_message". Operator response: This is an internal error. Contact
IBM Software Support for assistance.
Explanation: See message text.
error_message contains the reason for the error and AWSBHZ017E An internal error has occurred.
includes the operating system error message. The Schedulr was unable to add a job
mastsked database might be corrupted. stream dependency to the internal table
System action: Schedulr stops. used by the resolve dependencies
functions.
Operator response: To rebuild the mastsked database,
run composer and issue the build mastsked command. Explanation: The internal error is: "Bad dependencies
Rerun schedulr. If the problem persists, contact IBM passed to resolver".
Software Support for assistance. System action: Schedulr stops.
Operator response: This is an internal error. Contact
AWSBHZ014E Schedulr encountered the following IBM Software Support for assistance.
error while reading dates from the
calendars database: "error_message".
Explanation: See message.

104 IBM Tivoli Workload Scheduler: Messages


AWSBHZ023E • AWSBHZ030E

includes the operating system error message.


AWSBHZ023E Schedulr encountered an error parsing
the contents of the job streams in the System action: Schedulr stops.
mozart database.
Operator response: Determine if another process has
Explanation: A previous message has given details of locked the calendars database. Wait till that process
the error. has finished, or stop it. Rerun schedulr. If the problem
persists, contact IBM Software Support for assistance.
System action: Schedulr stops.
Operator response: Solve the problem as described in
AWSBHZ030E Schedulr is unable to find the
the previous error message. Rerun schedulr.
"calendar" calendar specified in the
following job stream:
AWSBHZ024E Schedulr has encountered the "workstation_name#job_stream".
following error while trying to initialize
Explanation: See message text.
the Security file: "error_message".
workstation_name is the name of the workstation where
Explanation: See message.
the job stream is defined. job_stream is the name of the
error_message describes the error and includes the job stream. calendar is the name of the calendar that
operating system error message. cannot be found.
System action: Schedulr stops. System action: Schedulr stops.
Operator response: Check if the Security file exists. If Operator response: Confirm that the calendar
it does, delete it and then recreate it. specified in the job stream does not exist in the
calendars database:
If it does not exist, create it.
v If it does not exist, either remove the reference to the
Create or recreate the Security file as follows: calendar from your job stream, change the reference
1. Run the wmaeutil command to stop the connector. to an existing calendar, or create the calendar with
2. Run the makesec command to create the Security composer. Then rerun schedulr.
file. v If it does exist, there is an internal error; contact IBM
Software Support for assistance.
See also: The chapter on setting security in the
Reference Manual for more details.

AWSBHZ025E The user that launched schedulr does


not have the correct permissions for the
schedulr actions.
Explanation: To run schedulr, the user must have
build access to the file object in the Tivoli Workload
Scheduler Security file.
System action: Schedulr stops.
Operator response: Do one of the following:
v Edit the Security file to give the user the correct
rights, stop all Tivoli Workload Scheduler processes
and rerun schedulr.
v Log off and log on again as a user with the rights to
run schedulr.
See also: The chapter on setting security in the
Reference Manual for more details.

AWSBHZ029E Schedulr encountered the following


error while trying to lock the calendars
database: "error_message".
Explanation: The calendars database is locked before
schedulr starts selecting the job streams that are to be
included in the production period.
error_message contains the reason for the error and

Chapter 2. Message help 105


AWSBIA002E • AWSBIA022E

Composer messages - BIA


This section lists error and warning messages that could be issued by the composer
component.

The message component code is BIA and the old message set code is 208 in the
″maestro″ message catalog.
Explanation: The program has encountered an internal
AWSBIA002E The identifier "identifier" is required at
error trying to allocate memory for the indicated
this point,
internal_storage_item.
but has not been supplied.
System action: Composer cannot perform the update
Explanation: See message.
required.
identifier is the identifier expected at this point in the
Operator response: This is an internal error. Contact
command.
IBM Software Support for assistance.
System action: Composer cannot perform the update
required.
AWSBIA018E Job "job_identifier" is already present in
Operator response: Check the syntax of the object the job stream.
definitions. See the Reference Manual for full details.
Explanation: You cannot add the job identified by the
Correct the error and reissue the command.
indicated job_identifier to the job stream, because it is
See: The Reference Manual for full details of the syntax already present, and multiple jobs cannot coexist.
of the object definitions.
System action: Composer cannot perform the update
required.
AWSBIA003E A parameter or identifier has been
Operator response: Check the job definition. Reissue
supplied where it is
the command, identifying a different job that does not
not required.
exist in the job stream, or using an alias to give the job
Explanation: See message. a separate identity.
System action: Composer cannot perform the update
required. AWSBIA021E Job "job_name" does not exist in job
stream
Operator response: Check the syntax of the object
"workstation#job_stream_name".
definitions. See the Reference Manual for full details.
Correct the error and reissue the command. Explanation: The issued command identifies a job that
is not in the job stream.job_name is the job that does not
See: The Reference Manual for full details of the syntax
exist.
of the object definitions.
workstation#job_stream_name identifies the job stream
which is the subject of the command.
AWSBIA004E The delimiter "delimiter" is required at
this point, System action: Composer cannot perform the update
but has not been supplied. required.
Explanation: See message. Operator response: Check the job definition. Reissue
the command, identifying an existing job.
delimiter is the delimiter expected at this point in the
command.
AWSBIA022E A file system error "error_message"
System action: Composer cannot perform the update
occurred building the temporary file
required.
"temporary_file_name".
Operator response: Check the syntax of the object
Explanation: See message.
definitions. See the Reference Manual for full details.
Correct the error and reissue the command. System action: Composer cannot perform the update
required.
See: The Reference Manual for full details of the syntax
of the object definitions. Operator response: Check the file system error
message. This might indicate a problem that you can
resolve, such as: file system full, insufficient file
AWSBIA017E An internal error has occurred.
descriptors, or incorrect file permissions. If you can
Out of memory trying to allocate
resolve the problem, do so. If not, contact IBM Software
"internal_storage_item".
Support for assistance.

106 IBM Tivoli Workload Scheduler: Messages


AWSBIA030E • AWSBIA087E

See the Reference Manual for full details of the syntax.


AWSBIA030E An error has occurred opening the
Correct the error and reissue the command.
redirected output file "file_name"
identified by the MAESTROLP variable.
AWSBIA043E Validation for object "object_ID": errors:
Explanation: The ;offline keyword has been used to
error_count; warnings warning_count.
redirect the output. The MAESTROLP variable is set to
redirect the output to a file, but the file cannot be Explanation: The validation of the indicated object has
opened. found errors, warnings, or both.
file_name is the file that is nominated as the redirected object_ID identifies the object that is the subject of the
output file that cannot be opened. command.
System action: Composer cannot perform the update error_count is the number of errors found.
required.
warning_count is the number of warnings found.
Operator response: Perform the following checks:
System action: Composer cannot perform the update
1. Check that the file path is correct, and that if the required.
path includes spaces it has been included between
double quotes. Operator response: This message will have been
2. Check that the directory has write permission for preceded by error messages, warning messages, or
the user performing the command. both. Follow the instructions for each message to
correct them, and resubmit the command.
3. Check that there is sufficient disk space in the file
set for a file to be opened.
4. Check that the operating system has sufficient file AWSBIA047E An error occurred while accessing the
descriptors available to open the file. definition file
"file_name".
Correct any errors and retry the command. Explanation: See message.file_name identifies the file
containing the object definitions that cannot be
accessed.
AWSBIA031E An error has occurred writing the
redirected output file "file_name" System action: Composer cannot perform the update
identified by the MAESTROLP variable. required.
Explanation: The ;offline keyword has been used to Operator response: Check the syntax of the command.
redirect the output. The MAESTROLP variable is set to Perform the following checks:
redirect the output to a file, but an error occurred while 1. Check that the file exists, that the path is correct,
writing to the file. and that if the path includes spaces it has been
file_name is the file that is nominated as the redirected included between double quotes.
output file that cannot be opened. 2. Check that the file has read permission for the user
performing the command.
System action: Composer cannot perform the update
required. 3. Check that there is sufficient disk space in the file
set for a file to be opened.
Operator response: Perform the following checks:
4. Check that the operating system has sufficient file
1. Check that the file has not been deleted by another descriptors available to open the file.
user
2. Check that there is sufficient disk space in the file Correct any errors and retry the command.
set for a file to be written.
AWSBIA087E There is a syntax error in the
Correct any errors and retry the command.
command.
Explanation: See message.
AWSBIA037E The only keyword allowed at this
point is ";offline". System action: Composer cannot perform the update
required.
Explanation: The syntax of the object definition
language determines that the only permissible keyword Operator response: Check the syntax of the issued
at this point is ";offline", but something else is present command. Use the command composer -u to view the
instead of "offline". usage of the command, or look in the Reference Manual.
Correct the error and reissue the command.
System action: Composer cannot perform the update
required. See: The Reference Manual for full details of the
command syntax.
Operator response: Check the object definition syntax.

Chapter 2. Message help 107


AWSBIA088E • AWSBIA107W

AWSBIA088E An internal error error has occurred AWSBIA098E A file system error "error_message"
while trying to resolve dependencies. occurred closing the temporary file
"temporary_file_name".
Explanation: See message.
Explanation: See message.
error is a code that refers to a list in the program code
of potential errors. System action: Composer cannot perform the update
required.
System action: Composer cannot perform the update
required. Operator response: Check the file system error
message. This might indicate a problem that you can
Operator response: This is an internal error. Contact
resolve, such as: file system full, insufficient file
IBM Software Support for assistance.
descriptors, or incorrect file permissions. If you can
resolve the problem, do so. If not, contact IBM Software
AWSBIA089E The keyword "keyword" was expected Support for assistance.
at this point.
Explanation: You have issued a validate command, AWSBIA105E A file system error file_system_error has
but following the name of the file to be validated the occurred opening the script or jcl file
only permitted (optional) keyword is "keyword". file_name.

System action: Composer cannot perform the update Explanation: See message.
required.
file_system_error is the error given by the operating
Operator response: Check the object definition syntax. system.
See the Reference Manual for full details of the syntax.
file_name identifies the file
Correct the error and reissue the command.
System action: Composer cannot perform the update
See: The Reference Manual for full details of the object
required.
definition syntax.
Operator response: Check the operating system
documentation to determine the nature of the file
AWSBIA090I For file "definition_file": errors
system error. If you can correct the error, do so and
error_count, warnings warning_count.
retry the operation. If you cannot correct the error
Explanation: See message. contact IBM Software Support for assistance.

definition_file is the file that is being validated.


AWSBIA106W The job stream definition has one or
error_count and warning_count are the respective counts more warnings.
of errors and warnings.
Explanation: The job stream definition has been
System action: If any errors have occurred composer validated and accepted, but one or more warnings were
does not perform the requested update. issued.
Operator response: This message will have been System action: You are asked whether composer is to
preceded by error messages, warning messages, or perform the update.
both. Follow the instructions for each message to
correct them, and resubmit the command. Operator response: Check the preceding warning
message or messages. If the situations indicated by the
warning or warnings are acceptable, answer "y" to the
AWSBIA097E A file system error "error_message" question "Do you want to update?".
occurred writing the temporary file
"temporary_file_name". If not, answer "n" to the question "Do you want to
update?", correct the job stream definition and reissue
Explanation: See message. the command.
System action: Composer cannot perform the update
required. AWSBIA107W The workstation definition has one or
Operator response: Check the file system error more warnings.
message. This might indicate a problem that you can Explanation: The workstation definition has been
resolve, such as: file system full, insufficient file validated, but one or more warnings were issued.
descriptors, or incorrect file permissions. If you can
resolve the problem, do so. If not, contact IBM Software System action: You are asked whether composer is to
Support for assistance. perform the update.
Operator response: Check the preceding warning
message or messages. If the situations indicated by the

108 IBM Tivoli Workload Scheduler: Messages


AWSBIA147E • AWSBIA282E

warning or warnings are acceptable, answer "y" to the If it is already in use, retry the operation, supplying a
question "Do you want to update?". valid port number.
If not, answer "n" to the question "Do you want to
update?", correct the workstation definition and reissue AWSBIA280E There is an error in the connection
the command. parameters for composer. The port
specified by the "-port" connection
parameter is not numeric.
AWSBIA147E The "first_time_zone_definition" differs
from "second_time_zone_definition" for Explanation: See message.
"job_or_job_stream". A time zone need be
System action: The composer command line client
specified just once, or all instances of it
cannot connect to its server. The submitted command
must be equal.
cannot be performed.
Explanation: A time zone need only be specified once
Operator response: Check the composer connection
in a job or job stream definition. If you choose to
parameters. Correct the value defined for the "-port"
specify it more than once, all instances of the time zone
parameter so that it is the valid numeric port number
definition must be equal.
of the composer command line server, and retry the
Note: a job can have a different time zone definition command.
than that of its job stream.
See: The Reference Manual for full details of the
first_time_definition is one of the time definitions. connection parameters for the composer command line
client.
second_time_definition is another time definition that has
a different time zone specification.
AWSBIA281E The composer command line client
job_or_job_stream identifies the job or job stream that
cannot connect to its server. The value
cannot be scheduled.
specified for the "-protocol" connection
System action: The job or job stream cannot be parameter is not valid. It must be "http"
scheduled. or "https".

Operator response: Correct the job or job stream Explanation: See message.
definition so that either the time zone specification
System action: The composer command line client
occurs only once, or so that each time definition has
cannot connect to its server. The submitted command
exactly the same time zone specification. Note that a
cannot be performed.
job can have a different time zone definition than that
of its job stream. Operator response: Check the composer connection
parameters. Correct the value defined for the
Use composer to reschedule the job or job stream.
"-protocol" parameter so that it is the valid protocol to
use for communication with the composer command
AWSBIA272W The specified "tcpaddr" value line server, and retry the command. Valid values are
"TCP/IP_port" is not in the range 1 to "http" (insecure) or "https" (secure).
65535. The following value of "!2" is
See: The Reference Manual for full details of the
used instead, calculated as the modulus
connection parameters for the composer command line
of the input value divided by 65536.
client.
Explanation: The supplied TCP/IP port number is out
of range. A default value has been calculated using the
AWSBIA282E The composer command line client
modulus of your input value divided by 65536 (the
cannot connect to its server. The value
modulus is defined as the remainder left after the input
specified for the "-timeout" connection
value has been divided by 65536 the maximum integral
parameter is not valid. It must be the
number of times). For example, if you input a port
number of seconds that the command
value of 300001 (which is greater than 65535), the
line client is to wait for a connection
program divides it by 65536 an integral number of
before timing out.
times (4), giving a remainder of 37857. This remainder
is called the modulus, and is used as the port value. Explanation: See message.
System action: The program continues, using the System action: The composer command line client
indicated default value. cannot connect to its server. The submitted command
cannot be performed.
Operator response: Check the indicated port number
used. If it is not already in use, you need take no Operator response: Check the composer connection
action, other than to register the value used for future parameters. Correct the value defined for the "-timeout"
reference. parameter so that it is the number of seconds that the

Chapter 2. Message help 109


AWSBIA283E • AWSBIA293E

command line client is to wait for a connection with


AWSBIA285E An internal error has occurred.
the command line server before timing out, and retry
Composer cannot open the temporary
the command.
file "temporary_file" for reading.
See: The Reference Manual for full details of the
Explanation: See message.temporary_file is the name
connection parameters for the composer command line
and path of the temporary file that cannot be opened
client.
for reading.
System action: The submitted command cannot be
AWSBIA283E An internal error has occurred.
performed.
Composer cannot open the temporary
file "temporary_file". Operator response: Perform the following checks:
Explanation: See message.temporary_file is the name v Check that there is sufficient space on the file system
and path of the temporary file that cannot be opened. where your temporary files are created
v Check that the user of the command line client has
System action: The submitted command cannot be
read permission in the temporary files directory
performed.
v Check that you have not reached the maximum
Operator response: Perform the following checks: number of open file descriptors allowed by the
v Check that there is sufficient space on the file system operating system
where your temporary files are created
v Check that the user of the command line client has Correct any problems you find and retry the command.
write permission in the temporary files directory
If no problems are identified, this is an internal error,
v Check that you have not reached the maximum
and contact IBM Software Support for assistance.
number of open file descriptors allowed by the
operating system
AWSBIA286E Total errors: error_count.
Correct any problems you find and retry the command.
Explanation: The total errors that occurred during a
composer "update" or "delete" command.
If no problems are identified, this is an internal error,
and contact IBM Software Support for assistance. System action: None.
Operator response: Check the individual messages to
AWSBIA284E An internal error has occurred. determine the nature of the errors. Correct them and
Composer cannot open the temporary resubmit the command.
file "temporary_file" for writing.
Explanation: See message.temporary_file is the name AWSBIA287W Total warnings: warning_count.
and path of the temporary file that cannot be opened
Explanation: The total warnings that occurred during
for writing.
a composer "update" or "delete" command.
System action: The submitted command cannot be
System action: None.
performed.
Operator response: Check the individual messages to
Operator response: Perform the following checks:
determine the nature of the warnings. Take any
v Check that there is sufficient space on the file system appropriate action.
where your temporary files are created
v Check that the user of the command line client has
AWSBIA293E An internal error has occurred.
write permission in the temporary files directory
Composer was not able to initialize the
v Check that you have not reached the maximum HTTP or HTTPS connection.
number of open file descriptors allowed by the
operating system Explanation: See message.
System action: The submitted command cannot be
Correct any problems you find and retry the command. performed.

If no problems are identified, this is an internal error, Operator response: Check that the connection
and contact IBM Software Support for assistance. parameters are valid. If you find an error, correct it and
resubmit the command.
If the connection parameters are valid, resubmit the
command, because the problem might have been only
temporary.

110 IBM Tivoli Workload Scheduler: Messages


AWSBIA294E • AWSBIA309E

If the problem persists, contact IBM Software Support the workstation or job stream to which it belongs (or
for assistance. both), you must make the changes in separate actions.
For example, if you want to rename both a job stream
See: The Reference Manual for full details of the
and a job which belongs to it, first issue a rename
connection parameters for the composer command line
command for one, and then a second rename command
client.
for the other.
See: The Reference Manual for full details of the
AWSBIA294E An internal error has occurred. The
scheduling language syntax.
composer command line server could
not authenticate the client.
AWSBIA301W The scheduling language syntax
Explanation: See message.
check for object "object_ID" has produced
System action: The submitted command cannot be the following number of warnings
performed. warning_count.

Operator response: Check that the connection Explanation: See message.


parameters are valid. If you find an error, correct it and
System action: Composer has successfully completed
resubmit the command.
all of the commands, but some warnings were issued.
If the connection parameters are valid, resubmit the
Operator response: Check the warning messages
command, because the problem might have been only
issued by composer. Take any appropriate action.
temporary.
If the problem persists, contact IBM Software Support
AWSBIA304W An inconsistency in the workstation
for assistance.
definition has been ignored. The secure
port identified in the "secureaddr"
AWSBIA297E The job stream, or the workstation on keyword has been ignored because the
which it runs, cannot be renamed "securitylevel" keyword has not been
because another job stream already supplied.
exists with the supplied name. Two job
Explanation: See message.
streams can only have the same name if
one has been created, not renamed, as a System action: The action relating to the workstation
version of the other (with different definition is completed successfully. The workstation
valid-from dates). does not use secure (SSL) communications.
Explanation: A job stream is identified by the job Operator response: Check the scheduling language
stream name and the workstation or workstation class syntax. If you intended to define secure communication
it is to run on. But different versions of the job stream for this workstation modify the workstation parameters
can exist with different valid-from dates, but only again to set the "securitylevel" keyword to the value
provided they are created as such. An existing job you require (you need to re-supply the SSL port with
stream cannot be renamed to become a version of the "secureaddr" keyword).
another existing job stream.
See: The Reference Manual for full details of the
job_stream identifies the job stream which already exists. scheduling language syntax.
System action: The submitted command cannot be
performed. AWSBIA309E The "validto" date must be greater
than the "validfrom" date in run cycle
Operator response: If you want the job stream to
"run_cycle" defined in job stream
become a version of another job stream, you must
"job_stream".
create it as such. If you selected an existing job stream
name by mistake, select a different job stream name Explanation: See message.
that does not exist and retry the rename operation.
run_cycle identifies the run cycle with the incompatible
dates.
AWSBIA298E If you want to rename a job, the
job_stream identifies the job stream to which the run
associated workstation and job stream
cycle belongs.
cannot be renamed in the same action.
System action: The operation is not performed.
Explanation: See message.
Operator response: Reissue the command, ensuring
System action: The rename command cannot be
that the "validto" date is greater than the "validfrom"
performed.
date.
Operator response: If you want to rename a job and

Chapter 2. Message help 111


AWSBIA310E • AWSBIA323W

AWSBIA310E The "validto" date must be greater AWSBIA321I The credentials to connect to the
than the "validfrom" date in a run cycle remote server have not been specified.
defined in job stream "job_stream".
Explanation: When you use the command line client,
Explanation: See message. it needs to connect to the remote server at the master
domain manager. For this it requires connection
job_stream identifies the job stream to which the run
parameters that are supplied as part of the command,
cycle belongs.
in a file of connection parameters, or by default from
System action: The operation is not performed. the useropts or localopts file.

Operator response: Reissue the command, ensuring conman could not find a set of these parameters to
that the "validto" date is greater than the "validfrom" establish a connection.
date.
System action: The operation is not performed.
Operator response: Do one of the following:
AWSBIA315E There is a syntax error. The syntax of
either the "follows" or the "matching" v Edit the useropts or localopts file and insert the
keywords is not correct. communication parameters. Save the file and rerun
the command.
Explanation: See message.
v Reissue the command, supplying the connection
System action: The creation or modification of the job parameters as command options, or in a file.
stream definition is not successful.
See: The Reference Manual for details of the syntax of
Operator response: Check the scheduling language the connection parameters.
syntax. Correct the syntax of the "matching" or
"follows" keywords and resubmit the command.
AWSBIA322W The local prompt text in job stream
See: The Reference Manual for full details of the "job_stream" exceeds the maximum
scheduling language syntax. length allowed of max_prompt bytes. It
has been truncated.

AWSBIA316E An internal error has occurred. The Explanation: See message.


file "file" could not be read.
job_stream identifies the job stream for which the
Explanation: See message. prompt cannot be created or modified.

System action: The operation is not performed. max_prompt indicates the maximum number of bytes
that you can use for the prompt.
Operator response: Check that the file exists, and has
not been renamed, moved, or deleted. Check that the System action: The submitted command cannot be
user has permission to read it. If you find a problem, performed.
correct it and retry the command. Otherwise contact
Operator response: Check the input command.
IBM Software Support for assistance.
Shorten the prompt length until it is less than the
indicated maximum.
AWSBIA317E An internal error has occurred. The
file "file" could not be opened due to a
AWSBIA323W The total units for the resource
memory allocation error.
"resource" in job stream "job_stream" is
Explanation: See message. "resource_units" units, which exceeds the
maximum number of resource units:
System action: The operation is not performed. max_resource_units.
Operator response: Contact IBM Software Support for Explanation: See message.
assistance.
resource identifies the resource that has exceed the
maximum number of resource units.
AWSBIA320E An error occurred while trying to save
the user options file "file". job_stream identifies the job stream for which the
resource cannot be created or modified.
Explanation: See message.
resource units indicates the total number of resource
System action: The operation is not performed. units in the job stream.
Operator response: Verify that there is sufficient space max_resource_units indicates the maximum number of
in the indicated file system, and that the user of Tivoli resource units you can specify.
Workload Scheduler has permission to write files in the
indicated directory.

112 IBM Tivoli Workload Scheduler: Messages


AWSBIA324E • AWSBIA330W

System action: The submitted command cannot be


AWSBIA327W The "fullstatus" field has been
performed.
supplied as "on" for extended agent
Operator response: Check the input command. "agent", for which it is not required. It
Reduce the number of resource units so that it is less has been set to "off".
than the indicated maximum.
Explanation: See message.
System action: Processing continues, treating the
AWSBIA324E The total units for the resource
"fullstatus" field as if it had been defined as "off".
"resource" in job "job" is "resource_units"
units, which exceeds the maximum Operator response: No action is required, but to avoid
number of resource units: receiving this warning in future ensure to not specify
max_resource_units. the "fullstatus" field when defining an extended agent.
Explanation: See message.
AWSBIA328W The "behindfirewall" field has been
resource identifies the resource that has exceed the
supplied for extended agent "agent", for
maximum number of resource units.
which it is not required. It has been
job identifies the job for which the resource cannot be ignored.
created or modified.
Explanation: See message.
resource units indicates the total number of resource
System action: Processing continues, ignoring the
units in the job.
"behindfirewall" field.
max_resource_units indicates the maximum number of
Operator response: No action is required, but to avoid
resource units you can specify.
receiving this warning in future ensure to not specify
System action: The submitted command cannot be the "behindfirewall" field when defining an extended
performed. agent.

Operator response: Check the input command.


Reduce the number of resource units so that it is less AWSBIA329W The "securitylevel" field and the
than the indicated maximum. "secureaddr" fields have been supplied
for extended agent "agent", for which
they are not required. They have been
AWSBIA325W The local prompt text in job "job" ignored.
exceeds the maximum length allowed of
max_prompt bytes. It has been truncated. Explanation: See message.

Explanation: See message. System action: Processing continues, ignoring the


"securitylevel" field and the "secureaddr" fields.
job identifies the job for which the prompt cannot be
created or modified. Operator response: No action is required, but to avoid
receiving this warning in future ensure to not specify
max_prompt indicates the maximum number of bytes the "securitylevel" field and the "secureaddr" fields
that you can use for the prompt. when defining an extended agent.
System action: The submitted command cannot be
performed. AWSBIA330W The "autolink" field has been
Operator response: Check the input command. supplied as "on" for extended agent
Shorten the prompt length until it is less than the "agent", for which it is not required. It
indicated maximum. has been set to "off".
Explanation: See message.
AWSBIA326W The "server" field has been supplied System action: Processing continues, treating the
for extended agent "agent", for which it "autolink" field as if it had been defined as "off".
is not required. It has been ignored.
Operator response: No action is required, but to avoid
Explanation: See message. receiving this warning in future ensure to not specify
System action: Processing continues, ignoring the the "autolink" field when defining an extended agent.
"server" field.
Operator response: No action is required, but to avoid
receiving this warning in future ensure to not specify
the "server" field when defining an extended agent.

Chapter 2. Message help 113


AWSBIA331W • AWSBIA339W

System action: Processing continues, ignoring the


AWSBIA331W The "fullstatus" field has been
"secureaddr" field.
supplied as "on" for standard agent or
broker workstation "agent", for which it Operator response: If you had not intended to define
is not required. It has been set to "off". secure communications for this workstation, no action
is required, but to avoid receiving this warning in
Explanation: See message.
future ensure to not specify the "secureaddr" field when
System action: Processing continues, treating the defining a workstation.
"fullstatus" field as if it had been defined as "off".
However, if you had intended to define secure
Operator response: No action is required, but to avoid communications, modify the workstation definition,
receiving this warning in future ensure to not specify setting the appropriate values for the "securitylevel"
the "fullstatus" field when defining a standard agent or and "secureaddr" fields.
broker workstation.
AWSBIA336W The "method" field has been supplied
AWSBIA332W The "fullstatus" field has been for workstation "workstation", for which
supplied as "off" for domain manager it is not required. It has been ignored.
"domain_manager", which is not correct. It
Explanation: See message.
has been set to "on".
System action: Processing continues, ignoring the
Explanation: See message.
"method" field.
System action: Processing continues, treating the
Operator response: No action is required, but to avoid
"fullstatus" field as if it had been defined as "on".
receiving this warning in future ensure to not specify
Operator response: No action is required, but to avoid the "method" field when defining a workstation.
receiving this warning in future ensure to specify the
"fullstatus" field as on when defining a domain
AWSBIA337W The "manager" field has been
manager.
supplied for domain "domain", for which
it is not required as it is now obsolete.
AWSBIA333W The "server" field has been supplied It has been ignored.
for domain manager "domain_manager",
Explanation: See message.
for which it is not required. It has been
ignored. System action: Processing continues, ignoring the
"manager" field.
Explanation: See message.
Operator response: No action is required, but to avoid
System action: Processing continues, ignoring the
receiving this warning in future ensure to not specify
"server" field.
the "manager" field when defining a domain.
Operator response: No action is required, but to avoid
receiving this warning in future ensure to not specify
AWSBIA338W The "domain" field has been supplied
the "server" field when defining a domain manager.
for extended agent "agent", for which it
is not required. It has been ignored.
AWSBIA334W The "resolvedep" field has been
Explanation: See message.
supplied for workstation "workstation",
for which it is not required. It has been System action: Processing continues, ignoring the
ignored. "domain" field.
Explanation: See message. Operator response: No action is required, but to avoid
receiving this warning in future ensure to not specify
System action: Processing continues, ignoring the
the "domain" field when defining an extended agent.
"resolvedep" field.
Operator response: No action is required, but to avoid
AWSBIA339W The "securitylevel" field has been
receiving this warning in future ensure to not specify
supplied for extended agent "agent", but
the "resolvedep" field when defining a workstation.
the "secureaddr" field (SSL port) has
not. The default value of 31113 is used
AWSBIA335W The "secureaddr" field has been for "secureaddr".
supplied for workstation "workstation",
Explanation: See message.
but the "securitylevel" field has not. It
has been ignored. System action: Processing continues, using the value
of "31113" for the "secureaddr" field.
Explanation: See message.

114 IBM Tivoli Workload Scheduler: Messages


AWSBIA340W • AWSBIA346E

Operator response: Verify that port 31113 on the Operator response: Check the command syntax.
master domain manager is the correct port for secure Resubmit the command supplying the filter criteria
communications. If it is not, modify the extended agent only once.
description to correct the value.
See: The Reference Manual for full details of the
If the port number is correct, no action is required, but command syntax.
to avoid receiving this warning in future ensure to
specify the "secureaddr" field when defining an
AWSBIA344E The supplied filter criteria is not valid
extended agent.
for the supplied object of the command.
The filter for the object of this
AWSBIA340W The "host" field has been supplied for command requires keyword
standard agent or broker workstation "valid_keyword".
"agent", for which it is not required. It
Explanation: See message.
has been replaced by the domain to
which the workstation belongs. For example, you have issued the command list js=@;
filter workstation=abc123 but "workstation" is not a
Explanation: A standard agent or broker workstation
valid filter keyword for a job stream.
must have its host field set to the value of the domain
in which it resides. valid_keyword is the correct filter keyword to use with
the object of this command.
System action: Processing continues, treating the
"host" field as if it had been defined as the domain of System action: The command is not processed.
the agent.
Operator response: Check the command syntax.
Operator response: No action is required, but to avoid Resubmit the command supplying the correct keyword
receiving this warning in future ensure to specify the in the filter criteria.
"host" as the workstation’s domain when defining a
standard agent or broker workstation. See: The Reference Manual for full details of the
command syntax.

AWSBIA341W The "host" field has been supplied for


workstation "workstation", for which it is AWSBIA345E The supplied filter criteria is not valid
not required. It has been ignored. for the supplied object of the command.
The filter for the object of this
Explanation: See message. command requires one of the following
keywords "valid_keywords_list".
System action: Processing continues, ignoring the
"host" field. Explanation: See message.
Operator response: No action is required, but to avoid For example, you have issued the command list js=@;
receiving this warning in future ensure to not specify filter workstation=abc123 but "workstation" is not a
the "host" field when defining an extended agent. valid filter keyword for a job stream.
valid_keywords_list is the list of correct filter keywords
AWSBIA342E The filter keyword "incorrect_keyword" to use with the object of this command.
cannot be used for the supplied object.
System action: The command is not processed.
Explanation: See message.
Operator response: Check the command syntax.
incorrect_keyword is the filter keyword that is not correct Resubmit the command supplying one of the correct
for the supplied object. keywords in the filter criteria.
System action: The command is not processed. See: The Reference Manual for full details of the
command syntax.
Operator response: Check the scheduling language
syntax. Resubmit the command supplying a valid
keyword. AWSBIA346E No filter criteria has been supplied
after the "filter" keyword. Use the
See: The Reference Manual for full details of the
following criteria: "filter_criteria".
scheduling language syntax.
Explanation: See message.
AWSBIA343E The supplied filter criteria cannot be filter_criteria is the type of filter criteria available for
used twice. this command on this object.
Explanation: See message. System action: The command is not processed.
System action: The command is not processed. Operator response: Check the command syntax.

Chapter 2. Message help 115


AWSBIA347E • AWSBIA352W

Resubmit the command supplying the filter criteria or


AWSBIA350W The keywords "schedtime" and "at"
omitting the "filter" keyword.
can be specified only once. The last
See: The Reference Manual for full details of the value is used.
command syntax.
Explanation: See message.
One or both of the keywords "schedtime" and "at" has
AWSBIA347E No filter criteria has been supplied
been specified more than once for a job or job stream.
after the "filter" keyword. Use the
following criteria: System action: The command is processed, using the
"valid_filter_criteria_list". last value issued.
Explanation: See message. Operator response: Check that the last value issued
was the one you wanted to use. If it was, you need
valid_filter_criteria_list is a list of the types of filter
take no action. If it was not you need to redo the
criteria available for this command on this object.
operation, setting the "schedtime" and "at" keywords to
System action: The command is not processed. the required values.

Operator response: Check the command syntax. See: The Reference Manual for full details of the
Resubmit the command supplying the filter criteria command syntax.
from the list or omitting the "filter" keyword.
See: The Reference Manual for full details of the AWSBIA351E The rename command does not
command syntax. support the "cpu " keyword because it is
ambiguous. To rename cpu objects use
the specific keywords for workstation
AWSBIA348E The supplied keyword is not valid for "ws", workstation class "wscl", or
the supplied object. The command on domain "dom".
this object requires keyword
"valid_keyword". Explanation: See message.

Explanation: See message. System action: The submitted command cannot be


performed.
valid_keyword is the correct keyword to use with the
object of this command. Operator response: To rename a workstation use the
"ws " or "workstation " keyword.
System action: The command is not processed.
To rename a workstation class use the "wscl " or
Operator response: Check the command syntax. "workstationclass " keyword.
Resubmit the command supplying the correct keyword.
To rename a domain use the "dom " or "domain
See: The Reference Manual for full details of the "keyword.
command syntax.
See: The Reference Manual for full details of the
command syntax.
AWSBIA349E The supplied keyword is not valid for
the supplied object. The command on
this object requires one of the following AWSBIA352W The IPv6 address you entered is an
keywords "valid_keywords_list". IPv4-mapped address and might not be
supported on some platforms.
Explanation: See message.
Explanation: Some operating systems do not support
valid_keyword_list is the list of correct keywords to use IPv4-mapped IPv6 addresses, either because the IPv6
with the object of this command. and IPv4 stacks are separate, or because of security
System action: The command is not processed. concerns.

Operator response: Check the command syntax. System action: The command is processed only if the
Resubmit the command supplying one or more operating system accepts this type of address.
keywords from the indicated list. Operator response: If the operating system does not
See: The Reference Manual for full details of the accept IPv4-mapped IPv6 addresses, replace it with a
command syntax. regular IPv4 or IPv6 address.

116 IBM Tivoli Workload Scheduler: Messages


AWSBIA353W • AWSBIA511I

AWSBIA353W The IPv6 address you entered is an AWSBIA357E There is a syntax error in the XML file.
IPv4-compatible address and might not An opening tag for a "comment" tag has
be supported on some platforms. been found before the closing tag of the
previously opened comment.
Explanation: Some operating systems do not support
IPv4-compatible IPv6 addresses, either because the IPv6 Explanation: See message.
and IPv4 stacks are separate, or because of security
System action: The submitted command cannot be
concerns.
performed.
System action: The command is processed only if the
Operator response: Correct the syntax of the XML file
operating system accepts this type of address.
and retry the operation.
Operator response: If the operating system does not
accept IPv4-compatible IPv6 addresses, be ready to
AWSBIA358E There is a syntax error in the XML file.
replace the address with a regular IPv4 or IPv6
The encoding used is not that of the
address.
locale.
Explanation: See message.
AWSBIA354W The IPv6 address you entered is a
Link Local address. Its scope is limited System action: The submitted command cannot be
to the same data link and the interface performed.
is not portable.
Operator response: Correct the syntax of the XML file
Explanation: Link Local addresses work only between and retry the operation.
two nodes on the same data link and cannot be
forwarded by routers. Different data links cannot
establish any sort of communication. Also, the local AWSBIA359E There is a syntax error in the XML file.
name of the outgoing interface might not match the The XML version is missing from the
interface name of the remote host. header, so the file cannot be parsed.

System action: The command might not be processed. Explanation: See message.

Operator response: Replace with a regular IPv6 System action: The submitted command cannot be
address. performed.
Operator response: Correct the syntax of the XML file
AWSBIA355E There is a syntax error in the XML file. and retry the operation.
The closing "Eventrule" tag has been
found without a corresponding opening AWSBIA360E There is a syntax error. You can not
tag. change the "vartable" of a variable. You
Explanation: See message. can change only the variable name.

System action: The submitted command cannot be Explanation: See message.


performed. System action: The submitted command cannot be
Operator response: Correct the syntax of the XML file performed.
and retry the operation. Operator response: Correct the syntax and retry the
See: The Reference Manual for full details of the command.
command syntax.
AWSBIA511I First migration step: errors "error_count",
AWSBIA356E There is a syntax error in the XML file. warnings "warning_count".
The closing "comment" tag has been Explanation: See message.
found without a corresponding opening
tag. error_count and warning_count are the respective counts
of errors and warnings.
Explanation: See message.
System action: Composer cannot perform the required
System action: The submitted command cannot be update.
performed.
Operator response: This message will have been
Operator response: Correct the syntax of the XML file preceded by error messages, warning messages, or
and retry the operation. both. Follow the instructions in the message help for
each message to correct them, and resubmit the
command.

Chapter 2. Message help 117


AWSBIA512I

AWSBIA512I Second migration step: errors


"error_count", warnings "warning_count".
Explanation: See message.
error_count and warning_count are the respective counts
of errors and warnings.
System action: Composer cannot perform the required
update.
Operator response: This message will have been
preceded by error messages, warning messages, or
both. Follow the instructions in the message help for
each message to correct them, and resubmit the
command.

118 IBM Tivoli Workload Scheduler: Messages


AWSBIB001E • AWSBIB009E

Scheduling language parser messages - BIB


This section lists scheduling language parser error and warning messages that could
be issued.

The message component code is BIB and the old message set code is 209 in the
″maestro″ message catalog.
Operator response: Correct the job stream definition
AWSBIB001E There is a syntax error. The time
and resubmit the command.
specified in the "at", "until", or
"deadline" time definitions must be See also: The Reference Manual for full details of the
between 0000 and 2359 (hhmm). scheduling language syntax.
Explanation: See message.
AWSBIB007E There is a syntax error. The job name
System action: The submitted command cannot be
is not syntactically valid. The name
performed.
must start with a letter, and can contain
Operator response: Correct the job stream definition alphanumeric characters, dashes and
and resubmit the command. underscores. It can contain up to 40
bytes.
See also: The Reference Manual for full details of the
scheduling language syntax. Explanation: See message.
System action: The submitted command cannot be
AWSBIB002E There is a syntax error. The job "limit" performed.
must be between 0 and 1024.
Operator response: Correct the job stream definition
Explanation: See message. and resubmit the command.
System action: The submitted command cannot be See also: The Reference Manual for full details of the
performed. scheduling language syntax.
Operator response: Correct the job stream definition
and resubmit the command. AWSBIB008E There is a syntax error. The resource
name is not syntactically valid. The
See also: The Reference Manual for full details of the
name must start with a letter, and can
scheduling language syntax.
contain alphanumeric characters, dashes
and underscores. It can contain up to 8
AWSBIB004W There is a syntax error. Priority must bytes.
be a numeric value from 0 to 99, "hi" (=
Explanation: See message.
100), "or go" (= 101).
System action: The submitted command cannot be
Explanation: See message.
performed.
System action: The submitted command cannot be
Operator response: Correct the job stream definition
performed.
and resubmit the command.
Operator response: Correct the job stream definition
See also: The Reference Manual for full details of the
and resubmit the command.
scheduling language syntax.
See also: The Reference Manual for full details of the
scheduling language syntax.
AWSBIB009E There is a syntax error. The prompt
name is not syntactically valid. The
AWSBIB006E There is a syntax error. The job stream name must start with a letter, and can
name is not syntactically valid. The contain alphanumeric characters, dashes
name must start with a letter, and can and underscores. It can contain up to 8
contain alphanumeric characters, dashes, bytes.
and underscores. It can contain up to 16
Explanation: See message.
bytes.
System action: The submitted command cannot be
Explanation: See message.
performed.
System action: The submitted command cannot be
Operator response: Correct the job stream definition
performed.
and resubmit the command.

Chapter 2. Message help 119


AWSBIB010E • AWSBIB027E

See also: The Reference Manual for full details of the System action: The submitted command cannot be
scheduling language syntax. performed.
Operator response: Correct the job stream definition
AWSBIB010E There is a syntax error. The calendar and resubmit the command.
name is not syntactically valid. The
See also: The Reference Manual for full details of the
name must start with a letter, and can
scheduling language syntax.
contain alphanumeric characters, dashes
and underscores. It can contain up to 8
bytes. AWSBIB023E There is a syntax error in the job
statement in the job stream definition.
Explanation: See message.
The user name associated with the
System action: The submitted command cannot be "streamlogon" keyword is not
performed. syntactically valid. The name can
contain up to 47 bytes. If the name
Operator response: Correct the job stream definition
contains special characters they must be
and resubmit the command.
enclosed in quotes (").
See also: The Reference Manual for full details of the
Explanation: See message.
scheduling language syntax.
System action: The submitted command cannot be
performed.
AWSBIB011E There is a syntax error. The recovery
job name is not syntactically valid. The Operator response: Correct the job stream definition
name must start with a letter, and can and resubmit the command.
contain alphanumeric characters, dashes
See also: The Reference Manual for full details of the
and underscores. It can contain up to 40
scheduling language syntax.
bytes.
Explanation: See message.
AWSBIB026E There is a syntax error. A non-valid
System action: The submitted command cannot be date has been specified. The date format
performed. is determined by the value in the
"useropts" file.
Operator response: Correct the job stream definition
and resubmit the command. Explanation: See message. If the format cannot be
found in the useropts file, it is obtained from the
See also: The Reference Manual for full details of the
localopts file.
scheduling language syntax.
System action: The submitted command cannot be
performed.
AWSBIB014E There is a syntax error in the job
statement in the job stream definition. Operator response: Correct the job stream definition
The required "streamlogon <username>" and resubmit the command.
argument has not been supplied.
See also: The Reference Manual for full details of the
Explanation: See message. scheduling language syntax.
System action: The submitted command cannot be
performed. AWSBIB027E There is a syntax error. The "at"
keyword can be specified for a job or its
Operator response: Correct the job stream definition
job stream (not both).
and resubmit the command.
Explanation: See message.
See also: The Reference Manual for full details of the
scheduling language syntax. System action: The submitted command cannot be
performed.
AWSBIB016E There is a syntax error in the job Operator response: Correct the job stream definition
statement in the job stream definition. and resubmit the command.
The "streamlogon" user name is not
See also: The Reference Manual for full details of the
syntactically valid. The name must be
scheduling language syntax.
no more than 47 bytes, and cannot
contain periods or other special
characters.
Explanation: See message.

120 IBM Tivoli Workload Scheduler: Messages


AWSBIB028E • AWSBIB039E

See also: The Reference Manual for full details of the


AWSBIB028E There is a syntax error. The "until"
scheduling language syntax.
keyword can be specified for a job or its
job stream (not both).
AWSBIB035E There is a syntax error. The required
Explanation: See message.
"on" keyword is missing.
System action: The submitted command cannot be
Explanation: See message.
performed.
System action: The submitted command cannot be
Operator response: Correct the job stream definition
performed.
and resubmit the command.
Operator response: Correct the job stream definition
See also: The Reference Manual for full details of the
and resubmit the command.
scheduling language syntax.
See also: The Reference Manual for full details of the
scheduling language syntax.
AWSBIB029E There is a syntax error. The "needs"
keyword can be specified for a job or its
job stream (not both). AWSBIB036E There is a syntax error. The job stream
definition does not start with the
Explanation: See message.
"schedule" keyword.
System action: The submitted command cannot be
Explanation: See message.
performed.
System action: The submitted command cannot be
Operator response: Correct the job stream definition
performed.
and resubmit the command.
Operator response: Correct the job stream definition
See also: The Reference Manual for full details of the
and resubmit the command.
scheduling language syntax.
See also: The Reference Manual for full details of the
scheduling language syntax.
AWSBIB033E The file file_name could not be opened.
Explanation: This message can be displayed for either
AWSBIB038E There is a syntax error. An object
a user file or an internal work file. If it is a user file
identifier (for example,
you might be able to correct the error. If it is an
a job name) is missing.
internal file it might be an internal error.
Explanation: See message.
System action: The submitted command cannot be
performed. System action: The submitted command cannot be
performed.
Operator response: Check the displayed file name.
v If it is a user file, make sure that the file exists, is in Operator response: Correct the job stream definition
the correct directory, and has the correct permissions and resubmit the command.
for the Tivoli Workload Scheduler. See also: The Reference Manual for full details of the
v If it is not a user file, ensure that the indicated scheduling language syntax.
directory has sufficient disk space to open a file, and
that the operating system has sufficient file
descriptors available AWSBIB039E There is a syntax error. A numeric
value (for example,
the priority value) has not been
If you identify an error, correct it and rerun the
supplied.
command. If not, this is an internal error, and contact
IBM Software Support for assistance. Explanation: See message.
System action: The submitted command cannot be
AWSBIB034E There is a syntax error in the job performed.
statement of the job stream definition.
A duplicate keyword has been supplied. Operator response: Correct the job stream definition
and resubmit the command.
Explanation: See message.
See also: The Reference Manual for full details of the
System action: The submitted command cannot be scheduling language syntax.
performed.
Operator response: Correct the job stream definition
and resubmit the command.

Chapter 2. Message help 121


AWSBIB040E • AWSBIB051E

AWSBIB040E There is a syntax error. An object AWSBIB044E There is a syntax error. A time-related
identifier (for example, keyword (for example, "every") has been
a job name) or the "@" wildcard is supplied, but its value is either missing
missing. or is not a valid time specification.
Explanation: See message. Explanation: See message.
System action: The submitted command cannot be System action: The submitted command cannot be
performed. performed.
Operator response: Correct the job stream definition Operator response: Correct the job stream definition
and resubmit the command. and resubmit the command.
See also: The Reference Manual for full details of the See also: The Reference Manual for full details of the
scheduling language syntax. scheduling language syntax.

AWSBIB041E There is a syntax error. A date-related AWSBIB045E There is a syntax error. An "opens"
keyword has been supplied (for keyword has been supplied, but its
example, "deadline") but it is not value is either missing or is not a valid
followed by a date or day specification, file name.
or a calendar or iCalendar name.
Explanation: See message.
Explanation: See message.
System action: The submitted command cannot be
System action: The submitted command cannot be performed.
performed.
Operator response: Correct the job stream definition
Operator response: Correct the job stream definition and resubmit the command.
and resubmit the command.
See also: The Reference Manual for full details of the
See also: The Reference Manual for full details of the scheduling language syntax.
scheduling language syntax.
AWSBIB047E There is a syntax error. An "except"
AWSBIB042E There is a syntax error. A "day", keyword has been supplied, but its
"weekday", or "workday" keyword has value is either missing or is not a valid
been supplied, but it is not preceded by date specification, day specification,
an offset value. calendar or iCalendar name.
Explanation: See message. Explanation: See message.
System action: The submitted command cannot be System action: The submitted command cannot be
performed. performed.
Operator response: Correct the job stream definition Operator response: Correct the job stream definition
and resubmit the command. and resubmit the command.
See also: The Reference Manual for full details of the See also: The Reference Manual for full details of the
scheduling language syntax. scheduling language syntax.

AWSBIB043E There is a syntax error. A dependency AWSBIB051E There is a syntax error. The "prompt"
specification or other keyword has been supplied, but is not
keyword is missing, or an incorrect followed by a prompt name or the
keyword has been supplied. prompt text enclosed in quotes.
Explanation: See message. Explanation: See message.
System action: The submitted command cannot be System action: The submitted command cannot be
performed. performed.
Operator response: Correct the job stream definition Operator response: Correct the job stream definition
and resubmit the command. and resubmit the command.
See also: The Reference Manual for full details of the See also: The Reference Manual for full details of the
scheduling language syntax. scheduling language syntax.

122 IBM Tivoli Workload Scheduler: Messages


AWSBIB052E • AWSBIB059E

AWSBIB052E There is a syntax error. The "end" AWSBIB056E There is a syntax error. The supplied
keyword has not been found to stop the file name is longer than the maximum
job stream definition. of maximum_file_name_length bytes.
Explanation: See message. Explanation: See message.
System action: The submitted command cannot be maximum_file_name_length is the maximum number of
performed. bytes permitted in the file name (excluding the path
information).
Operator response: Correct the job stream definition
and resubmit the command. System action: The submitted command cannot be
performed.
See also: The Reference Manual for full details of the
scheduling language syntax. Operator response: Correct the job stream definition
and resubmit the command.
AWSBIB053E There is a syntax error. A file name has See also: The Reference Manual for full details of the
been supplied with an incorrect syntax. scheduling language syntax.
Explanation: See message.
AWSBIB057E There is a syntax error. The supplied
System action: The submitted command cannot be
"abendprompt" is longer than the
performed.
maximum of abendprompt_length bytes.
Operator response: Correct the job stream definition
Explanation: See message.
and resubmit the command. Ensure that the file name
is fully qualified. abendprompt_length is the maximum number of bytes
permitted in the abendprompt.
See also: The Reference Manual for full details of the
scheduling language syntax. System action: The submitted command cannot be
performed.
AWSBIB054E There is a syntax error. The supplied Operator response: Correct the job stream definition
fully qualified path name is longer than and resubmit the command.
the maximum of
See also: The Reference Manual for full details of the
maximum_path_name_length bytes.
scheduling language syntax.
Explanation: See message.
maximum_path_name_length is the maximum number of AWSBIB058E There is a syntax error. The supplied
bytes permitted in the path name. Windows domain name is not
syntactically valid. The name can
System action: The submitted command cannot be
contain up to 16 bytes (including the
performed.
backslash), and the user name can
Operator response: Correct the job stream definition contain up to 31 bytes.
and resubmit the command.
Explanation: See message.
See also: The Reference Manual for full details of the
System action: The submitted command cannot be
scheduling language syntax.
performed.
Operator response: Correct the job stream definition
AWSBIB055E There is a syntax error. The supplied
and resubmit the command.
logon name is longer than the maximum
of maximum_logon_name_length bytes. See also: The Reference Manual for full details of the
scheduling language syntax.
Explanation: See message.
maximum_logon_name_length is the maximum number of
AWSBIB059E There is a syntax error. The supplied
bytes permitted in the logon name.
"timezone" keyword is not followed by
System action: The submitted command cannot be valid time zone information.
performed.
Explanation: See message.
Operator response: Correct the job stream definition
System action: The submitted command cannot be
and resubmit the command.
performed.
See also: The Reference Manual for full details of the
Operator response: Correct the job stream definition
scheduling language syntax.
and resubmit the command.

Chapter 2. Message help 123


AWSBIB060E • AWSBIB067E

See also: The Reference Manual for full details of the


AWSBIB064E There is a syntax error. The dates
scheduling language syntax.
specified with the "on" and "except"
keywords are not compatible. For
AWSBIB060E There is a syntax error. The supplied example, you might have defined the
"timezone" keyword is not followed by same date or dates for both.
a time zone name.
Explanation: See message.
Explanation: See message.
System action: The submitted command cannot be
System action: The submitted command cannot be performed.
performed.
Operator response: Correct the job stream definition
Operator response: Correct the job stream definition and resubmit the command.
and resubmit the command.
See also: The Reference Manual for full details of the
See also: The Reference Manual for full details of the scheduling language syntax.
scheduling language syntax.
AWSBIB065E There is a syntax error. The "deadline"
AWSBIB061E There is a syntax error. The supplied offset can be specified for a job or its
time zone name is not a recognized time job stream (not both).
zone.
Explanation: See message.
Explanation: See message.
System action: The submitted command cannot be
System action: The submitted command cannot be performed.
performed.
Operator response: Correct the job stream definition
Operator response: Correct the job stream definition and resubmit the command.
and resubmit the command.
See also: The Reference Manual for full details of the
See also: The Reference Manual for full details of the scheduling language syntax.
scheduling language syntax.
AWSBIB066E There is a syntax error in the job
AWSBIB062E There is a syntax error. The supplied statement in the job stream definition.
time zone name is longer than 40 bytes. The "rccondsucc" keyword defines a
return code success condition expression
Explanation: See message. which is longer than the maximum
System action: The submitted command cannot be number of bytes allowed:
performed. maximum_expression_length.

Operator response: Correct the job stream definition Explanation: See message.
and resubmit the command. maximum_expression_length is the maximum number of
See also: The Reference Manual for full details of the bytes that can be included in the expression.
scheduling language syntax. System action: The submitted command cannot be
performed.
AWSBIB063E There is a syntax error. The scheduler Operator response: Correct the job stream definition
has determined that a job statement has and resubmit the command.
commenced but it is not preceded by
the ":" character. See also: The Reference Manual for full details of the
scheduling language syntax.
Explanation: See message.
System action: The submitted command cannot be AWSBIB067E There is a syntax error. The return code
performed. condition expression: expression is not
Operator response: Correct the job stream definition syntactically valid.
and resubmit the command. Explanation: See message.expression is the expression
See also: The Reference Manual for full details of the which is not valid.
scheduling language syntax. System action: The submitted command cannot be
performed.
Operator response: Correct the job stream definition
and resubmit the command.

124 IBM Tivoli Workload Scheduler: Messages


AWSBIB068E • AWSBIB208E

See also: The Reference Manual for full details of the See also: The Reference Manual for full details of the
scheduling language syntax. scheduling language syntax.

AWSBIB068E The time in the "relative from <time> AWSBIB201E There is a syntax error. An object
to <time>" clause of the "matching" or identifier (for example,
"follows" keyword is not in the valid a job name) must begin with an
format "[+/-][h]hhmm" (where mm is alphabetic character.
between 00-59).
Explanation: See message.
Explanation: See message.
System action: The submitted command cannot be
System action: The submitted command cannot be performed.
performed.
Operator response: Correct the job stream definition
Operator response: Correct the job stream definition and resubmit the command.
and resubmit the command.
See also: The Reference Manual for full details of the
See also: The Reference Manual for full details of the scheduling language syntax.
scheduling language syntax.
AWSBIB202E There is a syntax error. An object
AWSBIB069E The time in the "from <time> to identifier (for example,
<time>" clause of the "matching" or a job name) contains non valid
"follows" keyword must be between characters.
0000-2359.
Explanation: See message.
Explanation: See message.
System action: The submitted command cannot be
System action: The submitted command cannot be performed.
performed.
Operator response: Correct the job stream definition
Operator response: Correct the job stream definition and resubmit the command.
and resubmit the command.
See also: The Reference Manual for full details of the
See also: The Reference Manual for full details of the scheduling language syntax.
scheduling language syntax.
AWSBIB206E There is a syntax error. More than one
AWSBIB070E There is a syntax error. An "at" or a parameter was specified.
"schedtime" keyword has been specified
Explanation: See message.
with a time specification, but is not
followed by a "timezone/tz" or System action: The submitted command cannot be
"day"keyword, or a right bracket. performed.
Explanation: See message. Operator response: Correct the job stream definition
and resubmit the command.
System action: The submitted command cannot be
performed. See also: The Reference Manual for full details of the
scheduling language syntax.
Operator response: Correct the job stream definition
and resubmit the command.
AWSBIB208E There is a syntax error. The number of
See also: The Reference Manual for full details of the
job stream dependencies exceeds the
scheduling language syntax.
maximum number allowed.
Explanation: See message.
AWSBIB200E There is a syntax error. An object
identifier (for example, System action: The submitted command cannot be
a job name) is longer than the maximum performed.
number of bytes.
Operator response: Correct the job stream definition
Explanation: See message. and resubmit the command.
System action: The submitted command cannot be See also: The Reference Manual for full details of the
performed. scheduling language syntax.
Operator response: Correct the job stream definition
and resubmit the command.

Chapter 2. Message help 125


AWSBIB209E • AWSBIB221E

AWSBIB209E There is a syntax error. The number of AWSBIB216E There is a syntax error. Expected the
job dependencies exceeds the maximum keyword set: "from <time> to <time>".
number allowed.
Explanation: See message.
Explanation: See message.
System action: The submitted command cannot be
System action: The submitted command cannot be performed.
performed.
Operator response: Correct the job stream definition
Operator response: Correct the job stream definition and resubmit the command.
and resubmit the command.
See also: The Reference Manual for full details of the
See also: The Reference Manual for full details of the scheduling language syntax.
scheduling language syntax.
AWSBIB217E There is a syntax error. Expected the
AWSBIB213E There is a syntax error. A blank name keyword set: "relative from <time> to
has been supplied. <time>" (<time> is expressed as
HHMM, and the permitted values are
Explanation: See message.
between 0000 and 2359)
System action: The submitted command cannot be
Explanation: See message.
performed.
System action: The submitted command cannot be
Operator response: Correct the job stream definition
performed.
and resubmit the command.
Operator response: Correct the job stream definition
See also: The Reference Manual for full details of the
and resubmit the command.
scheduling language syntax.
See also: The Reference Manual for full details of the
scheduling language syntax.
AWSBIB214E There is a syntax error. The "onuntil"
keyword has a non-valid value. Valid
values are "suppr", "cont" or "canc". AWSBIB219E There is a syntax error. More than one
"matching" keyword has been supplied.
Explanation: See message.
Explanation: See message.
System action: The submitted command cannot be
performed. System action: The submitted command cannot be
performed.
Operator response: Check the syntax of the job stream
definition. Change the value of the "onuntil" keyword Operator response: Correct the job stream definition
to one of the indicated valid values and retry the and resubmit the command.
operation.
See also: The Reference Manual for full details of the
See also: The Reference Manual for full details of the scheduling language syntax.
scheduling language syntax.
AWSBIB220E There is a syntax error. A non-valid job
AWSBIB215E There is a syntax error. Either the alias has been supplied.
"follows" or "matching" keyword is not
Explanation: See message.
followed by one of the following
keywords: "previous", "sameday", System action: The submitted command cannot be
"relative from", or "from". performed.
Explanation: See message. Operator response: Correct the job stream definition
and resubmit the command.
System action: The submitted command cannot be
performed. See also: The Reference Manual for full details of the
scheduling language syntax.
Operator response: Correct the job stream definition
and resubmit the command.
AWSBIB221E There is a syntax error. A non-valid
See also: The Reference Manual for full details of the
runcycle name has been supplied.
scheduling language syntax.
Explanation: See message.
System action: The submitted command cannot be
performed.

126 IBM Tivoli Workload Scheduler: Messages


AWSBIB222E • AWSBIB228E

Operator response: Correct the job stream definition scheduling language syntax.
and resubmit the command.
See also: The Reference Manual for full details of the AWSBIB226E There is a syntax error. A "day[s]"
scheduling language syntax. offset for a "relative from <time> to
<time>" or a "from <time> to <time>"
clause has been supplied that is greater
AWSBIB222E Duplicated runcycle name.
than the maximum of maximum_offset
Explanation: This is a parser error, please check the days.
scheduling language
Explanation: See message.
maximum_offset is the maximum number of offset days
AWSBIB223E There is a syntax error. A value has
of the "relative from" or "from" clause.
been supplied for a "description"
keyword that is longer than the System action: The submitted command cannot be
maximum length of performed.
maximum_description_length bytes.
Operator response: Correct the job stream definition
Explanation: See message. and resubmit the command.
maximum_description_length is the maximum length of See also: The Reference Manual for full details of the
the value of the "description" keyword. scheduling language syntax.
System action: The submitted command cannot be
performed. AWSBIB227E There is a syntax error. An "day[s]"
offset for an "at", "until", or "deadline"
Operator response: Correct the job stream definition
clause has been supplied that is greater
and resubmit the command.
than the maximum of maximum_offset
See also: The Reference Manual for full details of the days.
scheduling language syntax.
Explanation: See message.
maximum_offset is the maximum number of offset days
AWSBIB224E There is a syntax error. An external
of the "at", "until", or "deadline" clause.
string dependency has been supplied
that is longer than the maximum length System action: The submitted command cannot be
of maximum_description_length bytes. performed.
Explanation: See message. Operator response: Correct the job stream definition
and resubmit the command.
maximum_description_length is the maximum length of
the external string dependency. See also: The Reference Manual for full details of the
scheduling language syntax.
System action: The submitted command cannot be
performed.
AWSBIB228E There is a syntax error. An "every"
Operator response: Correct the job stream definition
keyword has been supplied with a rate
and resubmit the command.
not in the range 0 - maximum_rate.
See also: The Reference Manual for full details of the
Explanation: See message.
scheduling language syntax.
maximum_rate is the maximum value that the
"every"rate can have. The rate is in the format hhmm.
AWSBIB225E There is a syntax error. An iCalendar
name has been supplied that is longer System action: The submitted command cannot be
than the maximum length of performed.
maximum_description_length bytes.
Operator response: Correct the job stream definition
Explanation: See message. and resubmit the command.
maximum_description_length is the maximum length of See also: The Reference Manual for full details of the
the iCalendar name. scheduling language syntax.
System action: The submitted command cannot be
performed.
Operator response: Correct the job stream definition
and resubmit the command.
See also: The Reference Manual for full details of the

Chapter 2. Message help 127


AWSBIB229E • AWSBIB320W

AWSBIB229E An iCalendar cannot be empty. AWSBIB317E The path of a filename in the opens
dependencies and its qualifier cannot
Explanation: This is a parser error, please check the
exceed "dependency_file_name_max_length"
scheduling language
bytes.
Explanation: See message.
AWSBIB230E There is a syntax error. The keyword
"keyword" is not correct at this position. System action: The submitted command cannot be
performed.
Explanation: See message.
Operator response: Correct the job stream definition
keyword is the keyword that is out of position.
and resubmit the command.
System action: The submitted command cannot be
See also: The Reference Manual for full details of the
performed.
scheduling language syntax.
Operator response: Correct the job stream definition
and resubmit the command.
AWSBIB318E You cannot specify a time zone for the
See also: The Reference Manual for full details of the run cycle time dependencies.
scheduling language syntax.
Explanation: See message.
System action: The submitted command cannot be
AWSBIB231E There is a syntax error. A "relative
performed.
from <time> to <time>" or a "from
<time> to <time>" clause has been Operator response: Correct the job stream definition
supplied where the "from" time is later and resubmit the command.
than the "to" time.
See also: The Reference Manual for full details of the
Explanation: See message. scheduling language syntax.
System action: The submitted command cannot be
performed. AWSBIB319E There is an error in the job definition.
The sum of the "docommand" string and
Operator response: Correct the job stream definition
the "rccondsucc" string must not be
and resubmit the command.
greater than maximum_length bytes.
See also: The Reference Manual for full details of the
Explanation: See message.
scheduling language syntax.
maximum_length is the maximum length of the sum of
the "docommand" string and the "rccondsucc" string.
AWSBIB315E Either a job or job stream identifier is
missing, or the matching criteria is not System action: The submitted command cannot be
valid. performed.
Explanation: See message. Operator response: Correct the job definition and
resubmit the command.
System action: The submitted command cannot be
performed. See also: The Reference Manual for full details of the
scheduling language syntax.
Operator response: Correct the job stream definition
and resubmit the command.
AWSBIB320W The specified keyword is not allowed
See also: The Reference Manual for full details of the
in a job definition outside a job stream.
scheduling language syntax.
Explanation: See message.
AWSBIB316E There is a syntax error. A "recovery" System action: The submitted command cannot be
action has been supplied that is not performed.
"stop", "continue", or "rerun".
Operator response: Correct the job definition and
Explanation: See message. resubmit the command.
System action: The submitted command cannot be See also: The Reference Manual for full details of the
performed. scheduling language syntax.
Operator response: Correct the job stream definition
and resubmit the command.
See also: The Reference Manual for full details of the
scheduling language syntax.

128 IBM Tivoli Workload Scheduler: Messages


AWSBIB321E • AWSBIB322E

AWSBIB321E A variable table name is expected at


this point, but was not supplied.
Explanation: See message.
System action: The operation is not performed.
Operator response: Correct the variable table reference
in the job stream definition and retry the operation.
See also: The Reference Manual for full details of the
scheduling language syntax.

AWSBIB322E The variable table name exceeds the


maximum length of
maximum_variable_table_size bytes.
Explanation: maximum_variable_table_size is the
maximum size in bytes of the variable table.
System action: The operation is not performed.
Operator response: Correct the variable table reference
in the job stream definition and retry the operation.
See also: The Reference Manual for full details of the
scheduling language syntax.

Chapter 2. Message help 129


AWSBID001E • AWSBID006E

Compiler messages - BID


This section lists error and warning messages that could be issued by the compiler
component.

The message component code is BID and the old message set code is 211 in the
″maestro″ message catalog.

AWSBID001E Compiler cannot find the "thiscpu" AWSBID005E There is a syntax error in the compiler
option in the local options file command. An incorrect date
(localopts). specification ("date") has been found
either in the production schedule file
Explanation: See message.
("file_name"), or as an argument to the
System action: Compiler stops. "-date" option.

Operator response: Add the thiscpu option to the Explanation: The production schedule file name is
localopts file. either the default prodsked or the file specified with the
-input option.

AWSBID002E Compiler cannot find the "master" date is the date string that is not correct.
option in either the localopts file or the
file_name is the name of the production schedule file.
global options.
System action: Compiler does not start.
Explanation: See message.
Operator response: Locate whether the error was in
System action: Compiler stops.
the supplied -date option or in the indicated file.
Operator response: Add the "master" option to the v If the error was in the -date option, resubmit the
global options, using optman. command with a valid date argument in the format .
v If the error was in the file, edit it. Make sure that the
AWSBID003E Compiler cannot be run on this date specified in the first line that contains the
workstation, because the settings in the following string " Production Schedule for <date>" is
global options or the localopts file correct and in the following format:
indicate that this workstation is not the "<mm>/<dd>/<[yy]yy>". Then resubmit the
master domain manager. command.
Explanation: See message.
AWSBID006E Compiler was unable to open the
A common reason for this problem is that the production schedule file: "file_name". The
procedure for switching to the backup master domain following gives more details of the
manager has not been followed correctly. error: "system_error".
System action: Compiler does not start. Explanation: file_name is the name of the production
Operator response: Verify that this workstation is the schedule file. system_error contains the operating system
master domain manager by checking that the master error message.
variable in the global options identifies this System action: Compiler stops.
workstation.
v If it does not, run compiler from the master domain Operator response: Read the error message and see if
manager. you can identify the error and correct it, resubmitting
the command. If the error message is not sufficiently
v If this is the master domain manager, the probable explanatory, make the following checks:
cause is that the workstation specified by the thiscpu
variable in the localopts option file and the 1. Verify that you have supplied the correct name for
workstation specified by the master variable in the the production schedule file (the default name is
global options, are not the same. Change the prodsked when submitting the command. If you
localopts file so that they are the same, save the file, made an error, resubmit the command with the
stop all Tivoli Workload Scheduler processes, and corrected file name.
rerun compiler. 2. If the file name has been correctly supplied, check
that this file exists, in the correct directory. If you
find an error, rename or move the file and resubmit
the command.
3. If the file is present, check that the user running
compiler has read permission for the file. If it does

130 IBM Tivoli Workload Scheduler: Messages


AWSBID007E • AWSBID011E

not, either change the permissions for the user or make sure that all databases are either all
for the file, and resubmit the command. non-expanded (0) or all expanded (1). Use the
Alternatively, log off and log on again as a user dbexpand command to convert all databases to the
with the correct permissions and resubmit the expanded version.
command.
If the database cannot be opened because of a failure to
4. If the user is correct, check that there is sufficient allocate memory, use the operating system tools to
space in the fileset of the file. If there is not, make determine how much memory compiler is using and
more space and resubmit the command. whether it is leaking memory. If it is leaking memory,
5. If the file space is sufficient, check that the contact IBM Software Support for assistance.
processes running on the workstation have not
exceeded the maximum number of available file
AWSBID009E There is a syntax error in the compiler
descriptors (see your operating system
command. The "-date" option has been
documentation for more information). Close any
supplied, but the date that follows the
applications that are holding open large numbers of
option is not valid: "date"
files, or use the operating system tools to enable a
larger number of descriptors, and resubmit the Explanation: date is the date specified with -date
command. option, that is not valid.
System action: Compiler cannot start.
AWSBID007E Compiler is unable to add the
workstation records to the Symphony Operator response: Resubmit the command with a
file. The following gives more details of valid date argument in the format: "-date
the error: "error_message" <mm>/<dd>/<[yy]yy>".

Explanation: error_message contains the reason for the


error. AWSBID010E Compiler was unable to read calendar
information from the database. The
The following is a list of possible reasons why this following gives more details of the
error could occur: error: error_message
v Compiler encounters an error when it accesses the Explanation: error_message contains the reason for the
cpudata database. error.
v Compiler encounters an error when it writes to the
Symphony file. System action: Compiler stops.

v Compiler could not find a definition for the master Operator response: Check the error message and
workstation on the cpudata database. resolve the error that is described. Then rerun
compiler.
System action: Compiler stops.
If the error seems to be a problem with the calendar
Operator response: When compiler cannot access the data itself, rebuild the calendars database. To do this
cpudata database or write to the Symphony file, the run composer and issue the "build calendars"
error_message can be used to determine the cause and command. Rerun compiler. If the problem persists,
the appropriate response. contact IBM Software Support for assistance.
When compiler cannot find the master workstation in
the cpudata database, add the master workstation AWSBID011E Compiler was unable to read date
definition to the database. The name of the master information from the following calendar
workstation must match the names specified in the in the "calendar" database. The following
localopts file and the global options maintained by gives more details of the error:
optman. Then rerun compiler. "error_message".
Explanation: calendar is the name of the calendar, the
AWSBID008E Compiler has found a database dates of which compiler is trying to read.
incompatibility (expanded/non-
expanded) or is unable to allocate error_message contains the reason for the error.
memory to access the databases. The
System action: Compiler stops.
following gives more details of the
error: "error_message". Operator response: Check the error message and
resolve the error that is described. Then rerun
Explanation: error_message contains the reason for the
compiler.
error.
If the error seems to be a problem with the calendar
System action: Compiler stops.
data itself, rebuild the calendars database. To do this
Operator response: Use the dbinfo all command to run composer and issue the build calendars command.

Chapter 2. Message help 131


AWSBID012E • AWSBID019E

Rerun compiler. If the problem persists, contact IBM operating system. Wait till that process has finished, or
Software Support for assistance. stop it, if you are sure it is safe to do so. Rerun
compiler. If the problem persists, contact IBM Software
Support for assistance.
AWSBID012E Compiler was unable to add the
following calendar to the Symphony
file: "calendar". The following gives more AWSBID016E Compiler was unable to lock the
details of the error: error_message resources database. The following gives
more details of the error: "error_message".
Explanation: calendar is the name of the calendar you
are trying to add. Explanation: It is possible that another process has
locked the database.
error_message contains the reason for the error.
error_message contains the reason for the error.
System action: Compiler stops.
System action: Compiler stops.
Operator response: This is an internal error. Contact
IBM Software Support for assistance. Operator response: Determine if another process has
locked the resources database using the tools of your
operating system. Wait till that process has finished, or
AWSBID013E Compiler did not find the definition
stop it, if you are sure it is safe to do so. Rerun
for the master domain manager
compiler. If the problem persists, contact IBM Software
workstation in the cpudata database.
Support for assistance.
Explanation: Compiler reads workstation records
from the cpudata database and adds them to the
AWSBID017E Compiler was unable to lock the
Symphony file.
prompts database. The following gives
System action: Compiler stops. more details of the error: "error_message".

Operator response: Add the master domain manager Explanation: It is possible that another process has
workstation definition to the database with composer. locked the database.
If the definition is already in the database, make sure
error_message contains the reason for the error.
that the entries for thiscpu in the localopts file and
master in the global options match the name of the System action: Compiler stops.
master domain manager workstation in the database.
Operator response: Determine if another process has
When you have found and resolved the problem, rerun locked the prompts database using the tools of your
compiler. operating system. Wait till that process has finished, or
stop it, if you are sure it is safe to do so. Rerun
compiler. If the problem persists, contact IBM Software
AWSBID014E There is a syntax error in the compiler
Support for assistance.
command. An incorrect number of
options was supplied.
AWSBID018E Compiler was unable to lock the
Explanation: See message text.
cpudata database. The following gives
System action: Compiler cannot start. more details of the error: "error_message".

Operator response: To see the correct syntax for Explanation: It is possible that another process has
compiler, run the command: compiler -U, or look up locked the database.
the command in the Reference Manual.
error_message contains the reason for the error.
See: The Reference Manual for details of the compiler
System action: Compiler stops.
syntax.
Operator response: Determine if another process has
locked the cpudata database using the tools of your
AWSBID015E Compiler was unable to lock the jobs
operating system. Wait till that process has finished, or
database. The following gives more
stop it, if you are sure it is safe to do so. Rerun
details of the error: "error_message".
compiler. If the problem persists, contact IBM Software
Explanation: It is possible that another process has Support for assistance.
locked the database.
error_message contains the reason for the error. AWSBID019E Compiler was unable to lock the
calendars database. The following gives
System action: Compiler stops. more details of the error: "error_message".
Operator response: Determine if another process has Explanation: It is possible that another process has
locked the jobs database using the tools of your locked the database.

132 IBM Tivoli Workload Scheduler: Messages


AWSBID020E • AWSBID029W

error_message contains the reason for the error. System action: Compiler stops.
System action: Compiler stops. Operator response: This is an internal error. Contact
IBM Software Support for assistance.
Operator response: Determine if another process has
locked the calendars database using the tools of your
operating system. Wait till that process has finished, or AWSBID025E Compiler was unable to lock the
stop it, if you are sure it is safe to do so. Rerun userdata database. The following gives
compiler. If the problem persists, contact IBM Software more details of the error: "error_message".
Support for assistance.
Explanation: It is possible that another process has
locked the database.
AWSBID020E Compiler was unable to unlock the
error_message contains the reason for the error.
jobs database. The following gives more
details of the error: "error_message". System action: Compiler stops.
Explanation: error_message contains the reason for the Operator response: Determine if another process has
error. locked the userdata database using the tools of your
operating system. Wait till that process has finished, or
System action: Compiler stops.
stop it, if you are sure it is safe to do so. Rerun
Operator response: This is an internal error. Contact compiler. If the problem persists, contact IBM Software
IBM Software Support for assistance. Support for assistance.

AWSBID021E Compiler was unable to unlock the AWSBID026E Compiler was unable to unlock the
resources database. The following gives userdata database. The following gives
more details of the error: "error_message". more details of the error: "error_message".
Explanation: error_message contains the reason for the Explanation: error_message contains the reason for the
error. error.
System action: Compiler stops. System action: Compiler stops.
Operator response: This is an internal error. Contact Operator response: This is an internal error. Contact
IBM Software Support for assistance. IBM Software Support for assistance.

AWSBID022E Compiler was unable to unlock the AWSBID027E Compiler was unable to read the user
prompts database. The following gives information from the database and add
more details of the error: "error_message". it to the Symphony file. The following
gives more details of the error:
Explanation: error_message contains the reason for the
"error_message".
error.
Explanation: error_message contains the reason for the
System action: Compiler stops.
error.
Operator response: This is an internal error. Contact
System action: Compiler stops.
IBM Software Support for assistance.
Operator response: This is an internal error. Contact
IBM Software Support for assistance.
AWSBID023E Compiler was unable to unlock the
cpudata database. The following gives
more details of the error: "error_message". AWSBID029W You cannot initialize the "centralized
security" option because your database
Explanation: error_message contains the reason for the
is in non-expanded mode.
error.
Explanation: See message text.
System action: Compiler stops.
System action: Compiler stops.
Operator response: This is an internal error. Contact
IBM Software Support for assistance. Operator response: Use the composer dbexpand
command to convert all databases to the expanded
version, or use the normal security model
AWSBID024E Compiler was unable to unlock the
(non-centralized).
calendars database. The following gives
more details of the error: "error_message".
Explanation: error_message contains the reason for the
error.

Chapter 2. Message help 133


AWSBII010W • AWSBII017E

General and miscellaneous messages - BII


This section lists error and warning general and miscellaneous messages that could
be issued.

The message component code is BII and the old message set code is 216 in the
″maestro″ message catalog.
v That there is sufficient space in the file system where
AWSBII010W Cannot update the file "old_file". A new
the directory is to be created. If not, create more
file "new_file" was created. You must
space.
replace the old file with the new file.
v That the parent directory has create permission for
Explanation: The program was not able to update the the Tivoli Workload Scheduler user.
configuration file old_file (useropts). Maybe the file was
locked by another process. The program has saved the When you have solved the problem retry the operation.
changes it needed to make, giving the file this name:
new_file. AWSBII017E An internal error has occurred.
System action: The program continues. The program is unable to initialize the
GSKit libraries.
Operator response: Manually replace the old_file with
the new_file, as soon as possible. Explanation: A problem has occurred with the
installation or configuration of the GSKit libraries, or
both, and they cannot be initialized.
AWSBII014E Your command line interface settings
cannot be modified to allow the input System action: The program cannot commence a
of the password. secure connection, so stops.

Explanation: The program needs to modify the Operator response: This is an internal error. Contact
settings of your command line interface so that you can IBM Software Support for assistance.
enter the password in a secure way. It was not able to
do this. You cannot use the command line interface to
run this program.
System action: The operation is not performed.
Operator response: Verify with your system support if
the command line interface on your computer can be
modified to allow the interaction required to let you
enter a password in a secure way (it needs to reset the
echo input). If not, consult the Tivoli Workload
Scheduler documentation and choose a different way of
achieving the same objective.

AWSBII015E The new password and the confirmation


password do not match.
Explanation: See message.
System action: You are asked to re-input the
passwords.
Operator response: Check the values you supplied,
and when requested input the correct password and
confirm it.

AWSBII016E An internal error has occurred. The


directory "!1" cannot be created.
Explanation: See message.
System action: The operation is not performed.
Operator response: Verify the following:

134 IBM Tivoli Workload Scheduler: Messages


AWSBIN001E • AWSBIN013I

Plan libraries messages - BIN


This section lists error and warning messages that could be issued by the plan
libraries that are used by several components.

The message component code is BIN and the old message set code is 221 in the
″maestro″ message catalog.

AWSBIN001E The workstation: "workstation" has not AWSBIN006E An internal error occurred while
been initialized yet. starting workstation "workstation".
Explanation: See message. Explanation: See message.
System action: The operation is not performed. System action: The operation is not performed.
Operator response: Initialize the specified workstation Operator response: Contact IBM Software Support for
and retry the operation. assistance.

AWSBIN002E The workstation "workstation" is AWSBIN007W The "manager" option is valid only
already active. on the local workstation. It has been
ignored.
Explanation: See message.
Explanation: See message.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: None.
Operator response: Run the command locally or use a
command supported on a remote workstation.
AWSBIN003E The workstation "workstation"
identified as the target for a switch
manager operation is not a fault-tolerant AWSBIN008E The start command cannot be issued
agent. to workstation "workstation", because it is
not hosted by "host_workstation".
Explanation: The switch manager operation can only
be performed if the target workstation is a Explanation: See message.
fault-tolerant agent.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Specify the correct host for the
Operator response: Choose a target workstation that workstation.
is a fault-tolerant agent.
AWSBIN009E An error occurred while starting
AWSBIN004E The domain manager does not have workstation: "workstation".
the "fullstatus" field set to "on".
Explanation: See message.
Explanation: See message.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Contact IBM Software Support for
Operator response: Set the "fullstatus" field to "on" assistance.

AWSBIN005E The domain manager "domain_manager" AWSBIN011W Workstation "workstation" has already
is not in the same domain as the local stopped.
workstation "workstation".
Explanation: See message.
Explanation: See message.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Issue a command appropriate to
Operator response: Change the domain of either the the workstation status.
local workstation or the domain manager. You can
perform this operation using either the composer
AWSBIN013I The stop command has been issued on
command or the Job Scheduling Console.
workstation "workstation".
Explanation:

Chapter 2. Message help 135


AWSBIN014E • AWSBIN051E

System action: The operation is not performed.


AWSBIN020E An error occurred while running
Operator response: command: command_name#
Explanation: See message.
AWSBIN014E A "link" or "unlink" command has
System action: The operation is not performed.
been issued on workstation "workstation"
to link to or unlink from a peer Operator response: Contact IBM Software Support for
workstation within the same domain, assistance.
which is not allowed.
Explanation: See message. AWSBIN031E Workstation "workstation" is not in
domain "domain". The domain manager
System action: The operation is not performed.
cannot be switched.
Operator response: You can issue the link or unlink
Explanation: See message.
commands on higher or subordinate domains.
System action: The operation is not performed.
See also: The Reference Manual for more details about
link and unlink commands. Operator response: Select a workstation in the same
domain as the domain manager.
AWSBIN015E A "link" or "unlink" command has
been issued on workstation "workstation", AWSBIN032W Workstation "workstation" is already
but the domain of the workstation being the manager of domain "domain".
linked to or unlinked from is not
Explanation: See message.
subordinate to the domain of the local
workstation. System action: The operation is not performed.
Explanation: See message. Operator response: None.
System action: The operation is not performed.
AWSBIN040E Unable to obtain information about
Operator response: You can issue the link or unlink
the remote workstation
commands on higher or subordinate domains.
"workstation_name" because centralized
See also: The Reference Manual for more details about security, which is enabled for this
link and unlink commands. domain, does not allow it to.
Explanation: See message.
AWSBIN016E Monitoring is already active for
System action: The operation is not performed.
workstation "workstation".
Operator response: Contact the Tivoli Workload
Explanation: See message.
Scheduler Administrator for more information on
System action: The operation is not performed. security settings.
Operator response: None.
AWSBIN050E An internal error has occurred. An
unexpected record type has been found
AWSBIN017E Monitoring is already stopped for
in the Symphony file.
workstation "workstation".
Explanation: See message.
Explanation: See message.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Contact the Tivoli Workload
Operator response: None.
Scheduler administrator.

AWSBIN018I A "command_name" command was


AWSBIN051E This operation cannot be performed
issued for workstation "workstation".
on job stream "workstation#job_stream".
Explanation:
Explanation: See message.
System action:
System action: The operation is not performed.
Operator response:
Operator response: See the Tivoli Workload Scheduler
documentation for information on supported
operations.

136 IBM Tivoli Workload Scheduler: Messages


AWSBIN052E • AWSBIN091E

AWSBIN052E The job stream has already been AWSBIN091E An error occurred obtaining the
cancelled. monitoring configuration file for
workstation "workstation_name": The
Explanation: See message.
workstation does not support
System action: The operation is not performed. monitoring.

Operator response: None. Explanation: See message.


System action: The operation is not performed.
AWSBIN053E An error has been found in file
Operator response: Select a workstation where the
"file_name" at line line_number. The
monitoring function is supported.
program could not obtain the
workstation names in workstation class
"workstation_class".
Explanation: See message.
System action: The operation is not performed.
Operator response: Contact the Tivoli Workload
Scheduler administrator for information on the file.

AWSBIN054E The following internal error has


occurred in the TRANS module:
error_message
Explanation: You have submitted an ad hoc job
stream. During the processing, the job stream is
transformed into a Symphony file record before being
processed. The module (TRANS) that performs this
transformation has encountered an unexpected error.
System action: The program that called the TRANS
module continues, but the ad hoc job stream is
discarded.
Operator response: Contact IBM Software Support for
assistance.

AWSBIN055E Job stream "workstation#job_stream" was


not found in the database. The job
stream cannot be submitted.
Explanation: See message.
System action: The operation is not performed.
Operator response: Check the job stream name and
the database records.

AWSBIN090E The following error occurred while


obtaining the monitoring configuration
file for workstation "workstation_name":
error_message
Explanation: See message.
System action: The operation is not performed.
Operator response: See the error message for further
details on the problem.

Chapter 2. Message help 137


AWSBIO039E • AWSBIO041E

Comm_api messages - BIO


This section lists error and warning comm_api messages that could be issued.

The message component code is BIO and the old message set code is 222 in the
″maestro″ message catalog.
with the internal ID "myalias", so the job stream
AWSBIO039E The variable "variable" could not be
cannot be created and this message is issued.
found.
System action: The submit operation is not
Explanation: The variable could not be found in any
performed.
database.
Operator response: Choose a different alias and
System action: The operation is not performed.
resubmit the job stream. If there are particular reasons
Operator response: Check that this variable is defined why you must use this alias, wait until after a plan
in the global or local database. If the variable does not extension before resubmitting the job stream.
exist, define it and rerun the operation that needs to
use it.
AWSBIO041E The job cannot be submitted because
the job or job alias "job_name_or_alias"
AWSBIO040E The supplied job stream alias "alias" already exists.
cannot be used, because another job
Explanation: When a job is submitted, the program
stream has been submitted in this plan
checks to see if a duplicate job or duplicate alias
instance with the same alias.
already exists in the Symphony file. The program
Explanation: When a job stream is submitted with an follows these rules:
alias, the internal ID of the submitted job stream is set v Two jobs without aliases cannot exist with the same
to the value of the alias. This is so that follows name, irrespective of whether they were put in the
dependencies can be created where the aliased job plan by planner or by a normal submission to the
stream instances are predecessors. If you subsequently current plan.
submit the same or a different job stream, using the
v Two aliases cannot exist with the same name,
same alias, the software detects the duplication and
irrespective of whether they were supplied explicitly,
does not submit the job stream, issuing this message.
or generated by the program.
The potential for duplication only exists within the v The program only generates an alias if you are: a)
same unextended plan. Whenever you extend the plan, performing an ad-hoc submission, b) the job name
the original job stream and its alias are assigned new already exists, and c) an alias has not been supplied.
internal IDs which make them unique, making the alias The program uses the "docommand" string of the job
available for use for the same or another job stream. as the alias.
The following is an example: This means that if the program has already created
1. You submit job streams "JS-1" and "JS-2". The plan an alias for a job with a given "docommand" string,
now contains the following items, identified it cannot create an alias for any job that has the same
uniquely by their job stream internal IDs: "docommand" string. The job cannot be submitted
because the alias is a duplicate.
v Job stream name=WS-1#JS-1 Job stream internal
ID=058HNKHGRD8378
The following is an example of the latter situation: The
v Job stream name=WS-1#JS-2 Job stream internal jobs "Job-1" and "Job-2"already exist in the plan in the
ID=058HNKYIJG8945 same job stream for workstation "WS-1". You submit
2. You then submit job stream "JS-1" with the alias "Job-1" again as an ad-hoc job without an alias and
"myalias". The plan now contains the following with a "docommand "of "runjob27.exe". The program
items, identified uniquely by their job stream generates the alias from the docommand resulting in
internal IDs: the following job in the plan: Job name=WS-
v Job stream name=WS-1#JS-1 Job stream internal 1#0AAAAAAAAAAAAABG.RUNJOB27
ID=058HNKHGRD8378
You then submit "Job-2" again as an ad-hoc job without
v Job stream name=WS-1#JS-2 Job stream internal
an alias. The program wants to generate the same job
ID=058HNKYIJG8945
name, but cannot, because to do would create a
v Job stream name=WS-1#myalias Job stream duplicate alias. This message is issued.
internal ID=myalias
System action: The submit operation is not
3. You then try and submit job stream "JS-2" with the
performed.
alias "myalias". The plan already has a job stream

138 IBM Tivoli Workload Scheduler: Messages


Operator response: Choose a different specific alias
and resubmit the job.

Chapter 2. Message help 139


AWSBIP004E

Connector messages - BIP


This section lists error and warning messages that could be issued by the connector
component.

The message component code is BIP and the old message set code is 223 in the
″maestro″ message catalog.

AWSBIP004E An incorrect filter was encountered for


the object type object_type in method
method_name
Explanation: This message is issued by the Tivoli
Workload Scheduler Connector upon encountering one
of the following conditions:
v There is a product level mismatch between the Job
Scheduling Console and the Connector.
v An incorrect field was sent by the Job Scheduling
Console on a particular user action.
System action: The connector might stop, depending
on the circumstances.
Operator response: Verify that compatible Job
Scheduling Console, Tivoli Workload Scheduler
Connector, and Tivoli Workload Scheduler versions are
installed. If this is not the problem, contact IBM
Support.

140 IBM Tivoli Workload Scheduler: Messages


AWSBIS002E • AWSBIS009E

Customize messages - BIS


This section lists error and warning messages that could be issued by the customize
component.

Note: This component is no longer used, but the messages have been maintained
for backwards compatibility.

The message component code is BIS and the old message set code is 226 in the
″maestro″ message catalog.
Explanation: Customize is attempting to customize a
AWSBIS002E An internal error has occurred.
Tivoli Workload Scheduler configuration file, but the
Customize failed to run the following
file does not exist in the <TWS_home>/config directory.
UNIX command during the installation:
"command" A possible reason is that the Tivoli Workload Scheduler
Correct the problem and rerun tar file was corrupted while being copied to the
customize. workstation, or an error occurred during the unpacking
of the file.
Explanation: The command can be any of the
following: file_name can be any of the following:
v chgrp v jobmanrc
v chmod v JnextPlan
v chown v loadbal
v filepriv (UnixWare only) v localopts
v mkdir v NetConf
v mv v ntmulti
v rm v ntsingle
v Security
Customize issues this message in any of the following
v Sfinal
circumstances:
v StartUp
v It is unable to set permissions, ownership or group
of the Tivoli Workload Scheduler files. v unixlocl
v It could not create one or more directories. v unixrsh
v It could not delete or rename one or more files. v unixrsh.wrp

System action: Customize stops. The installation is not These files must all be in the <TWS_home>/config
completed. directory before running customize.
Operator response: Determine why the system System action: Customize stops. The installation is not
command specified in command failed and rerun completed.
customize.
Operator response: Check that all the configuration
Capturing the output from the customize command files listed above exist in the <TWS_home>/config
will help you to determine the error. Do the following: directory, and are legible. If any files are missing or
1. Run this command: script -a <file_name> where corrupted, delete the <TWS_home> directory and all its
<file_name> is the fully qualified path and file name contents and restart the installation process described
of the file where you want to capture the customize in the Planning and Installation Guide.
output (for example, /tmp/custOut.txt).
See also: The Planning and Installation Guide for details
2. Re-issue the customize command with all the of the installation process.
arguments used before.
3. When customize fails, issue the exit command to
close the output file. AWSBIS009E Customize could not create a symbolic
link to the following program: program.
4. Open the file and read the output from customize.
Explanation: Customize could not create a symbolic
link for one or more of the following Tivoli Workload
AWSBIS003E The following Tivoli Workload Scheduler programs from the directory: <TWS_home>/bin
Scheduler configuration file does not to the directory: <TWS_home>/../bin:
exist: file_name.
v datecalc

Chapter 2. Message help 141


AWSBIS010E • AWSBIS014E

v jobstdl 4. Restart the installation.


v maestro
v mat AWSBIS013E The user ID cannot be found in
v mbatch /etc/passwd and Yellow Pages (NIS).
Either it is not installed or it is not
v morestdl
accessible from the PATH system
v parms variable.

program is one or more of the programs listed above. Explanation: The Yellow Pages is a centralized
database of files including the passwd, group, and other
System action: Customize stops. The installation has system files. In a networked environment, these files
completed some steps but Tivoli Workload Scheduler is are centralized on a NIS server which makes them
not usable. available to all the machines on the network, for ease of
maintenance. Users can also have the same password
Operator response: Determine the reason why
across the network.
customize could not create a symbolic link, using the
tools of the operating system. Customize could not find the Tivoli Workload
Scheduler user’s login ID in the file /etc/passwd. It
When you have resolved the problem, delete all files in
then tried to look up the user ID in Yellow Pages, but
the product directory and restart the installation.
Yellow Pages was not installed or accessible on the
system.
AWSBIS010E Customize could not create a symbolic
The user ID must be in either /etc/passwd or Yellow
link to the following program, because a
Pages.
link already exists: program.
System action: Customize stops. The installation is
Explanation: Customize could not create a symbolic
not completed.
link for one or more of the following Tivoli Workload
Scheduler programs from the directory: <TWS_home>/bin Operator response: Define the Tivoli Workload
to the directory: <TWS_home>/../bin: Scheduler user in the /etc/passwd file, or in Yellow
v datecalc Pages.
v jobstdl If it is defined in Yellow Pages, ensure that the
v maestro directory where the Yellow Pages executable program is
stored is included in the PATH system variable.
v mat
v mbatch Rerun customize.
v morestdl
v parms AWSBIS014E The following user ID cannot be found
in either /etc/passwd or the Yellow
program is one or more of the programs listed above. Pages: user_name.
Explanation: The Yellow Pages is a centralized
This probably indicates that links made for a previous database of files including the passwd, group, and other
version of Tivoli Workload Scheduler were not deleted system files. In a networked environment, these files
when the old version was uninstalled or upgraded. are centralized on a NIS server which makes them
System action: Customize stops. The installation has available to all the machines on the network, for ease of
completed some steps, but Tivoli Workload Scheduler is maintenance. Users can have the same password across
not usable. the network.

Operator response: Use the following procedure: Customize could not find the Tivoli Workload
Scheduler user’s login ID either in the file /etc/passwd
1. Use operating system tools to determine which or in the Yellow Pages.
links exist.
2. Use the following commands to remove the existing The user ID must be in either /etc/passwd or Yellow
links: Pages.
"rm <TWS_home>/usr/bin/mat" System action: Customize stops. The installation is
"rm <TWS_home>/usr/bin/mbatch" not completed.
"rm <TWS_home>/usr/bin/datecalc"
"rm <TWS_home>/usr/bin/maestro" Operator response: Define the Tivoli Workload
"rm <TWS_home>/usr/bin/morestdl" Scheduler user in the /etc/passwd file, or in Yellow
"rm <TWS_home>/usr/bin/jobstdl" Pages.
"rm <TWS_home>/usr/bin/parms"
3. Delete all files in the product directory.

142 IBM Tivoli Workload Scheduler: Messages


AWSBIS015E • AWSBIS026E

AWSBIS015E The user running customize is not AWSBIS021E An error occurred running one of the
logged in as "root". commands required for the installation.
Determine which command had failed
Explanation: See message text.
by examining the error messages issued
System action: Customize cannot start. previous to this one. Correct the
problem and resubmit the command.
Operator response: Log off and log in again as "root"
and run customize again. Explanation: See message text.
System action: Customize stops. The installation is
AWSBIS016E Customize cannot use the chown not completed.
command.
Operator response: Determine which command failed
Explanation: The chown command was either not by examining the error messages issued previous to
found following the PATH environment variable or this one. Correct the problem and resubmit the
/etc/chown did not have "execute" permission. command.

System action: Customize stops. The installation is


not completed. AWSBIS024E Customize has been launched with the
’"-m <module_name>" option incorrectly
Operator response: Determine what has caused the specified more than once.
error and either add the directory that contains the
chown command to the PATH environment variable or Explanation: See message text.
ensure that the user running customize has "execute"
System action: Customize does not start.
permission for the command.
Operator response: Rerun Customize, supplying the
Rerun customize.
"-m <module_name>" option only once.
See also: The Planning and Installation Guide for details
AWSBIS017E The following user ID, for which you
of the syntax of customize.
want to install Tivoli Workload
Scheduler, does not exist or does not
belong to any group: user_name. AWSBIS025E Customize has been issued with the
following incorrect option: "option".
Explanation: user_name is the missing user ID.
Explanation: See message text.
System action: Customize stops. The installation is
not completed. option is the name of the incorrect option.
Operator response: Verify that the intended Tivoli System action: Customize does not start.
Workload Scheduler user ID has been added to the
Operator response: Run customize -U to see the valid
/etc/passwdfile, and the /etc/group or to their
command line options, or see the Planning and
equivalents in Yellow Pages (NIS).
Installation Guide.
Verify that the groups command runs correctly on the
See also: The Planning and Installation Guide for details
intended Tivoli Workload Scheduler user ID.
of the syntax of customize.
Rerun customize.
AWSBIS026E The Tivoli Workload Scheduler home
AWSBIS020E The supplied Tivoli Workload directory does not exist.
Scheduler home directory does not exist.
Explanation: Either you have supplied the wrong
Explanation: Either you have supplied the wrong directory to Customize, or you have not created the
directory to Customize, or you have not created the directory.
directory.
System action: Customize stops. The installation is
System action: Customize stops. The installation is not completed.
not completed.
Operator response: Depending on the reason for the
Operator response: Depending on the reason for the error, either rerun Customize, specifying the correct
error, either rerun Customize, specifying the correct directory, or create the Tivoli Workload Scheduler home
directory, or create the Tivoli Workload Scheduler home directory and extract the tar file into it before rerunning
directory and extract the tar file into it before rerunning Customize.
Customize.

Chapter 2. Message help 143


AWSBIS033E • AWSBIS047E

updating an installation. The -noexp option can only be


AWSBIS033E An error occurred while trying to
specified with the -new option when running a new
extract Tivoli Workload Scheduler from
installation of Tivoli Workload Scheduler.
the following tar file: tar_file_name.
System action: Customize stops. The installation is
Explanation: The problem might be caused by the file
not completed.
not being present or because of lack of disk space to
unpack it. Operator response: If this is an update, rerun
customize without the -noexp option.
tar_file_name is the name of the tar file.
See also: The Planning and Installation Guide for details
System action: Customize stops. The installation is
of the syntax of customize.
not completed.
Operator response: Check that the file exists at the
AWSBIS045E There is a syntax error in the
location you specified and that there is sufficient disk
customize options: the -uname option is
space available to extract it in the file set where you
not followed by a user ID, or the
want to install Tivoli Workload Scheduler. If there is
supplied user ID commences with a
insufficient space, create some and rerun customize, or
hyphen.
rerun customize, changing the options to install Tivoli
Workload Scheduler in a different file set with sufficient Explanation: A user ID must be supplied with the
space. -uname option. If the user ID that you tried to use
commences with a hyphen "-", chose a different user ID
that does not commence with a hyphen, or should
AWSBIS034E Customize encountered an error while
change the user ID so that it does not commence with a
installing Tivoli Workload Scheduler.
hyphen.
Determine the details of the error by
examining the error messages issued System action: Customize stops. The installation is
previous to this one. Correct the not completed.
problem and rerun customize.
Operator response: Rerun customize, specifying a
Explanation: See message. valid user ID after the -uname option, that does not
commence with a hyphen.
System action: Customize stops. The installation is
not completed. See also: The Planning and Installation Guide for details
of the syntax of customize.
Operator response: Determine the details of the error
by examining the error messages issued previous to
this one. Correct the problem and rerun customize. AWSBIS046E There is a syntax error in the
customize options: either the -update
and -new options have both been
AWSBIS042E Customize failed to decompress the
specified, or one of them has been
following tar file: tar_file_name.
specified more than once.
Explanation: The problem might be caused by the file
Explanation: See message.
not being present or because of lack of disk space to
decompress it. System action: Customize stops. The installation is
not completed.
tar_file_name is the name of the tar file.
Operator response: Rerun customize specifying either
System action: Customize stops. The installation is
the -new or the -update option only once.
not completed.
See also: The Planning and Installation Guide for details
Operator response: Check that the file exists at the
of the syntax of customize.
location you specified and that there is sufficient disk
space available to decompress it in the file set where
you want to install Tivoli Workload Scheduler. If there AWSBIS047E There is a syntax error in the
is insufficient space, create some and rerun customize, customize options: the -thiscpu option
or rerun customize, changing the options to install cannot be used with the -update option.
Tivoli Workload Scheduler in a different file set with
sufficient space. Explanation: You specified the -thiscpu option with the
-update option. The -thiscpu option can only be used
during a new installation (with the -new option) to
AWSBIS044E There is a syntax error in the specify the name of the Tivoli Workload Scheduler
customize options: -noexp should be workstation for that installation.
specified only with a -new install
System action: Customize stops. The installation is
Explanation: You specified the -noexp option when not completed.

144 IBM Tivoli Workload Scheduler: Messages


AWSBIS048E • AWSBIS052E

Operator response: If you are updating an installation,


AWSBIS050E There is a syntax error in the
rerun customize without the -thiscpu option.
customize options: you are running a
If you are running a fresh installation, specify the -new fresh installation (with the -new option)
option, without the -thiscpu option. but have not supplied either the -master
<workstation_name> option or the
See also: The Planning and Installation Guide for details -thiscpu <workstation_name> option,
of the syntax of customize. which are both mandatory for a fresh
installation.
AWSBIS048E There is a syntax error in the Explanation: See message.
customize options: the -thiscpu option is
not followed by a workstation name, or System action: Customize stops. The installation is
the supplied workstation name not completed.
commences with a hyphen.
Operator response: If you intended to update an
Explanation: A workstation name must be supplied existing installation, you must rerun customize using
with the -thiscpu option. If the workstation name that the -update option, but without the -master or the
you tried to use commences with a hyphen "-", chose a -thiscpu options.
different workstation name that does not commence
If you intended to run a fresh installation, specify the
with a hyphen, or should change the workstation name
-new option with the -master <workstation_name> and
so that it does not commence with a hyphen.
-thiscpu <workstation_name> options.
System action: Customize stops. The installation is
See also: The Planning and Installation Guide for details
not completed.
of the syntax of customize.
Operator response: Rerun customize, specifying a
valid workstation name after the -thiscpu option, that
AWSBIS051E There is a syntax error in the
does not commence with a hyphen.
customize options: the -master option is
See also: The Planning and Installation Guide for details not followed by a workstation name, or
of the syntax of customize. the supplied workstation name
commences with a hyphen.

AWSBIS049E There is a syntax error in the Explanation: A workstation name must be supplied
customize options: the -master with the -master option. If the workstation name that
<workstation_name> option can only be you tried to use commences with a hyphen "-", chose a
specified with -new option. different workstation name that does not commence
with a hyphen, or should change the workstation name
Explanation: You specified the -master so that it does not commence with a hyphen.
<workstation_name> option (which identifies to which
master domain manager you want the workstation System action: Customize stops. The installation is
where you are conducting the installation to belong) not completed.
while running an update installation (with the -update
Operator response: Rerun customize, specifying a
option).
valid workstation name after the -master option, that
System action: Customize stops. The installation is does not commence with a hyphen.
not completed.
See also: The Planning and Installation Guide for details
Operator response: If you are updating an installation, of the syntax of customize.
rerun customize without the -master <workstation_name>
option.
AWSBIS052E There is a syntax error in the
If you are updating an installation, and you want at the customize options: the -netman option is
same time to change the master domain manager for not followed by a directory name, or the
this workstation, you must first upgrade the supplied directory name commences
installation, and then change the master domain with a hyphen.
manager.
Explanation: A directory name must be supplied with
If you intended to run a fresh installation, specify the the -netman option. If the directory name that you tried
-new option, with the -master <workstation_name> to use commences with a hyphen "-", chose a different
option. directory name that does not commence with a hyphen,
or should change the directory name so that it does not
See also: The Planning and Installation Guide for details commence with a hyphen.
of the syntax of customize.
System action: Customize stops. The installation is
not completed.

Chapter 2. Message help 145


AWSBIS054E • AWSBIS060E

Operator response: Rerun customize, specifying a System action: Customize stops. The installation is
valid directory name after the -netman option, that does not completed.
not commence with a hyphen.
Operator response: If you intended to update an
See also: The Planning and Installation Guide for details existing installation, you must rerun customize using
of the syntax of customize. the -update option, but without the -master or the
-thiscpu options.
AWSBIS054E There is a syntax error in the If you intended to run a fresh installation, specify the
customize options: the -company option -new option with the -master <workstation_name> and
is not followed by a company name, or -thiscpu <workstation_name> options.
the supplied company name commences
See also: The Planning and Installation Guide for details
with a hyphen.
of the syntax of customize.
Explanation: A company name must be supplied with
the -company option. If the company name that you
AWSBIS059E Customize failed to decompress the
tried to use commences with a hyphen "-", chose a
following tar file: tar_file_name.
different company name that does not commence with
a hyphen, or should change the company name so that Explanation: The problem might be caused by the file
it does not commence with a hyphen. not being present or because of lack of disk space to
decompress it.
System action: Customize stops. The installation is
not completed. tar_file_name is the name of the tar file.
Operator response: Rerun customize, specifying a System action: Customize stops. The installation is
valid company name after the -company option, that not completed.
does not commence with a hyphen.
Operator response: Check that the file exists at the
See also: The Planning and Installation Guide for details location you specified and that there is sufficient disk
of the syntax of customize. space available to decompress it in the file set where
you want to install Tivoli Workload Scheduler. If there
is insufficient space, create some and rerun customize,
AWSBIS055E There is a syntax error in the
or rerun customize, changing the options to install
customize options: the -execpath option
Tivoli Workload Scheduler in a different file set with
is not followed by a path name, or the
sufficient space.
supplied path name commences with a
hyphen.
AWSBIS060E The following components directory
Explanation: A path name must be supplied with the
identified in the
-execpath option. If the path name that you tried to use
UNISON_COMPONENT_FILE variable
commences with a hyphen "-", chose a different path
is not a directory, or does not exist:
name that does not commence with a hyphen, or
directory_name.
should change the path name so that it does not
commence with a hyphen. Explanation: Customize found that the
UNISON_COMPONENT_FILE variable is set, but that
System action: Customize stops. The installation is
the path name it contains is incorrect, because the
not completed.
directory component of the pathname is not a directory
Operator response: Rerun customize, specifying a or does not exist.
valid path name after the -execpath option, that does not
directory_name is the name of the directory that is
commence with a hyphen.
incorrect or does not exist.
See also: The Planning and Installation Guide for details
System action: Customize stops. The installation is
of the syntax of customize.
not completed.
Operator response: Set the
AWSBIS058E There is a syntax error in the
UNISON_COMPONENT_FILE variable correctly, and
customize options: you are running a
export it, and then rerun customize. Alternatively,
fresh installation (with the -new option)
delete the variable and rerun customize, which will use
but have not supplied either the -master
the default value documented in the Planning and
<workstation_name> option or the
Installation Guide .
-thiscpu <workstation_name> option,
which are both mandatory for a fresh See also: The Planning and Installation Guide for details
installation. of how to use customize.
Explanation: See message.

146 IBM Tivoli Workload Scheduler: Messages


AWSBIS062E • AWSBIS502E

be a problem with file space or access permissions.


AWSBIS062E An entry was found in the components
file for the specified group, but it Operator response: Check the file system of the
contained incorrect data. <TWS_home> directory to ensure that there is sufficient
space, and that the user has write permission. If the
Explanation: See message.
problem persists, contact IBM Software Support for
System action: Customize stops. The installation is assistance.
not completed.
Operator response: Check the entry in the AWSBIS350W The application server is not running.
components file under the specified group, and verify
Explanation: The application server must be running
that it is correct. Rerun customize.
for you to run JnextPlan.
System action: The script CheckPrerequisites stops.
AWSBIS063E More than one entry was found in the
You cannot run JnextPlan.
components file either for the following
specified location: "directory_name" or the Operator response: To start the application server,
following group: "group_name". rerun CheckPrerequisites adding the option -start.
Explanation: See message.
AWSBIS502E "at": You are not authorized to use the
directory_name is the name of the Tivoli Workload
"at" command.
Scheduler home directory that has more than one entry
in the file. group_name is the name of the group that has Explanation: See message.
more that one entry in the file.
System action: The operation is not performed.
System action: Customize stops. The installation is
not completed. Operator response: Contact the Tivoli Workload
Scheduler administrator to obtain the required
Operator response: Check the Tivoli Workload authorization.
Scheduler entries in the components file, and ensure
that the locations and groups are not repeated.

AWSBIS065W You are trying to install Tivoli


Workload Scheduler in the following
location: "directory_name" under the
following group: "group_name". However,
there is already an instance installed in
that location and group.
Explanation: See message.
directory_name is the name of the directory that already
holds a Tivoli Workload Scheduler installation.
group_name is the name of the group under which a
Tivoli Workload Scheduler installation already exists.
System action: Customize stops. The installation is
not completed.
Operator response: Rerun customize, selecting a
different location or a different group for the Tivoli
Workload Scheduler installation, or both.

AWSBIS072E An error occurred while creating or


updating the components file.
Explanation: After Tivoli Workload Scheduler is
installed successfully, customize runs the ucomp
program to update the components file with the
location and group of the Tivoli Workload Scheduler
installation. If the components file does not exist,
customize creates it. This message indicates that
customize encountered an error during this process
while creating or updating the components file. It could

Chapter 2. Message help 147


AWSBIY001W

Demo scripts messages - BIY


This section lists error and warning Demo scripts messages that could be issued.

The message component code is BIY and the old message set code is 232 in the
″maestro″ message catalog.

AWSBIY001W Running the sample database setup


deletes
all job streams and jobs with the prefix
"SMPL" from the database.
Explanation: The sample database contains a set of
scheduling objects to be used in the tutorial. These
objects are all identified by the presence in the object
name of the prefix "SMPL". When you install the
database, it automatically deletes any previous objects
with the same prefix that it finds. This allows you to
easily replace the database after you have used the
tutorial and modified the objects (provided that you
did not modify the prefix).
System action: The sample database installation waits
for your response.
Operator response: Answer "y" or "n" at the prompt.

148 IBM Tivoli Workload Scheduler: Messages


AWSBJG001E • AWSBJG009E

Router messages - BJG


This section lists router error and warning messages that could be issued.

The message component code is BJG and the old message set code is 240 in the
″maestro″ message catalog.

AWSBJG001E Router cannot initialize the AWSBJG006E Router cannot perform the data
communication or set the connection translation between network format and
type and file descriptor for the host format required for SSL
connected socket to make an SSL communication. (ntoh). The following
connection to conman. The following error message is given: error_message
error message is given: error_message
Explanation: error_message either identifies the record
Explanation: error_message is the operating system that could not be translated or gives more information
error message text. about the error.
System action: Router stops and the operation fails. System action: Router stops and the operation fails.
Operator response: Check that the network is working Operator response: This is an internal error. Contact
correctly. Check that SSL is configured correctly. If you IBM Software Support for assistance.
have corrected the error, use the workstation stop and
start commands to restart router.
AWSBJG007E Router cannot send router packets on
See also: See the chapter on setting security in the the network. The following error
Planning and Installation Guide for more information message is given: error_message
about SSL.
Explanation: error_message either identifies the record
that could not be sent or gives more information about
AWSBJG002E Router is unable to create the stdlist the error.
file.
System action: Router stops and the operation fails.
Explanation: See message.
Operator response: Check that the network is working
System action: Router stops and the operation fails. correctly. If you have corrected the error, use the
workstation stop and start commands to restart router.
Operator response: Check the file system of the
<TWS_home> directory to ensure that there is sufficient If the problem persists, contact IBM Software Support.
space, and that the user has write permission. If you
have corrected the error, use the workstation stop and
AWSBJG008E Router cannot receive router packets
start commands to restart router.
from the network. The following error
If the problem persists, contact IBM Software Support message is given: error_message
for assistance.
Explanation: error_message either identifies the record
that could not be received or gives more information
AWSBJG005E Router has been invoked with an about the error.
incorrect number of arguments.
System action: Router stops and the operation fails.
Explanation: If you have invoked router manually,
Operator response: Check that the network is working
you have not supplied the correct number of
correctly. If you have corrected the error, use the
arguments.
workstation stop and start commands to restart router.
If router has been invoked by a Tivoli Workload
If the problem persists, contact IBM Software Support.
Scheduler process, this is an internal error.
System action: Router does not start.
AWSBJG009E Router ran out of memory allocating
Operator response: If you have invoked router memory for internal data structures
manually, check the syntax by issuing the command (comarea).
with just the "-u" argument (router -u). Retry the
Explanation: See message.
operation.
System action: Router stops and the operation is not
If router has been invoked by a Tivoli Workload
performed.
Scheduler process, contact IBM Software Support for
assistance. Operator response: Check the following:

Chapter 2. Message help 149


AWSBJG011E • AWSBJG017E

1. Verify if the workstation has enough memory


AWSBJG015E The following error occurred opening
available. Information about the memory
the configuration file "file_name":
requirements of Tivoli Workload Scheduler is
error_message.
provided in the Release Notes. If not, you might need
to increase the memory of the workstation or make Explanation: See message.
changes in memory management and paging to
System action: Router stops and the operation is not
make more memory available to router. Use the
performed.
workstation stop and start commands to restart
router. Operator response: Verify whether the configuration
2. If the workstation memory is adequate, try closing file exists and has read permission for the <TWS_user>.
all the applications that you do not need, and then
use the workstation stop and start commands to AWSBJG016E An error occurred reading the
restart router. configuration file "file_name":
3. If the problem persists, reboot the workstation, and error_message.
then use the workstation start command to restart
router. Explanation: See message.
4. If the problem persists, contact IBM Software System action: Router stops and the operation is not
Support for assistance. performed.
See also: The Release Notes for details of memory Operator response: Verify whether the configuration
requirements. file exists and has read permission for the <TWS_user>.

AWSBJG011E Scribner, called by router, cannot read AWSBJG017E An error occurred while closing the
the standard list file (stdlist) for the configuration file "file_name":
following job: error_message.
workstation_name.job_stream_name:
Explanation: See message.
job_name
System action: Router stops and the operation is not
Explanation: workstation_name, job_stream_name, and
performed.
job_name identify the job for which the standard list
could not be read. Operator response: Contact IBM Software Support for
assistance.
System action: Router stops and the operation is not
performed.
Operator response: Verify if the standard list file
exists and has read permission for the <TWS_user>.
Check if there are any network problems that might
prevent scribner from accessing the workstation where
the job was running.
If you have solved the problem, use the workstation
stop and start commands to restart router.

AWSBJG012E Router cannot open or read the


Symphony file.
Explanation: See message.
System action: Router stops and the operation is not
performed.
Operator response: Verify if the Symphony file exists
and has read permission for the <TWS_user>.
If you have solved the problem, use the workstation
stop and start commands to restart router.

150 IBM Tivoli Workload Scheduler: Messages


AWSBJG001E • AWSBJG009E

Migration messages - BJH


This section lists error and warning migration messages that could be issued.

The message component code is BJH and the old message set code is 241 in the
″maestro″ message catalog.

AWSBJG001E Router cannot initialize the AWSBJG006E Router cannot perform the data
communication or set the connection translation between network format and
type and file descriptor for the host format required for SSL
connected socket to make an SSL communication. (ntoh). The following
connection to conman. The following error message is given: error_message
error message is given: error_message
Explanation: error_message either identifies the record
Explanation: error_message is the operating system that could not be translated or gives more information
error message text. about the error.
System action: Router stops and the operation fails. System action: Router stops and the operation fails.
Operator response: Check that the network is working Operator response: This is an internal error. Contact
correctly. Check that SSL is configured correctly. If you IBM Software Support for assistance.
have corrected the error, use the workstation stop and
start commands to restart router.
AWSBJG007E Router cannot send router packets on
See also: See the chapter on setting security in the the network. The following error
Planning and Installation Guide for more information message is given: error_message
about SSL.
Explanation: error_message either identifies the record
that could not be sent or gives more information about
AWSBJG002E Router is unable to create the stdlist the error.
file.
System action: Router stops and the operation fails.
Explanation: See message.
Operator response: Check that the network is working
System action: Router stops and the operation fails. correctly. If you have corrected the error, use the
workstation stop and start commands to restart router.
Operator response: Check the file system of the
<TWS_home> directory to ensure that there is sufficient If the problem persists, contact IBM Software Support.
space, and that the user has write permission. If you
have corrected the error, use the workstation stop and
AWSBJG008E Router cannot receive router packets
start commands to restart router.
from the network. The following error
If the problem persists, contact IBM Software Support message is given: error_message
for assistance.
Explanation: error_message either identifies the record
that could not be received or gives more information
AWSBJG005E Router has been invoked with an about the error.
incorrect number of arguments.
System action: Router stops and the operation fails.
Explanation: If you have invoked router manually,
Operator response: Check that the network is working
you have not supplied the correct number of
correctly. If you have corrected the error, use the
arguments.
workstation stop and start commands to restart router.
If router has been invoked by a Tivoli Workload
If the problem persists, contact IBM Software Support.
Scheduler process, this is an internal error.
System action: Router does not start.
AWSBJG009E Router ran out of memory allocating
Operator response: If you have invoked router memory for internal data structures
manually, check the syntax by issuing the command (comarea).
with just the "-u" argument (router -u). Retry the
Explanation: See message.
operation.
System action: Router stops and the operation is not
If router has been invoked by a Tivoli Workload
performed.
Scheduler process, contact IBM Software Support for
assistance. Operator response: Check the following:

Chapter 2. Message help 151


AWSBJG011E • AWSBJG017E

1. Verify if the workstation has enough memory


AWSBJG015E The following error occurred opening
available. Information about the memory
the configuration file "file_name":
requirements of Tivoli Workload Scheduler is
error_message.
provided in the Release Notes. If not, you might need
to increase the memory of the workstation or make Explanation: See message.
changes in memory management and paging to
System action: Router stops and the operation is not
make more memory available to router. Use the
performed.
workstation stop and start commands to restart
router. Operator response: Verify whether the configuration
2. If the workstation memory is adequate, try closing file exists and has read permission for the <TWS_user>.
all the applications that you do not need, and then
use the workstation stop and start commands to AWSBJG016E An error occurred reading the
restart router. configuration file "file_name":
3. If the problem persists, reboot the workstation, and error_message.
then use the workstation start command to restart
router. Explanation: See message.
4. If the problem persists, contact IBM Software System action: Router stops and the operation is not
Support for assistance. performed.
See also: The Release Notes for details of memory Operator response: Verify whether the configuration
requirements. file exists and has read permission for the <TWS_user>.

AWSBJG011E Scribner, called by router, cannot read AWSBJG017E An error occurred while closing the
the standard list file (stdlist) for the configuration file "file_name":
following job: error_message.
workstation_name.job_stream_name:
Explanation: See message.
job_name
System action: Router stops and the operation is not
Explanation: workstation_name, job_stream_name, and
performed.
job_name identify the job for which the standard list
could not be read. Operator response: Contact IBM Software Support for
assistance.
System action: Router stops and the operation is not
performed.
Operator response: Verify if the standard list file
exists and has read permission for the <TWS_user>.
Check if there are any network problems that might
prevent scribner from accessing the workstation where
the job was running.
If you have solved the problem, use the workstation
stop and start commands to restart router.

AWSBJG012E Router cannot open or read the


Symphony file.
Explanation: See message.
System action: Router stops and the operation is not
performed.
Operator response: Verify if the Symphony file exists
and has read permission for the <TWS_user>.
If you have solved the problem, use the workstation
stop and start commands to restart router.

152 IBM Tivoli Workload Scheduler: Messages


AWSBWX002E • AWSBWX007W

Dataxtract messages - BWX


This section lists error and warning messages that could be issued by dataxtract.

The message component code is BWX.


v That there is sufficient disk space to write the file
AWSBWX002E An error has occurred opening the
file "file_name" for writing.
Resolve the problem and rerun the operation.
Explanation: See message.
file_name is the file that cannot be opened. AWSBWX005E An error has occurred renaming the
file "file_name" in "file_name_renamed".
System action: The action stops.
Explanation: See message.
Operator response: Check the following:
v That the file exists file_name is the file that cannot be renamed.
file_name_renamed is the file renamed.
v That the file is in the correct directory
v That the file has read permission System action: The action stops.
v That there is sufficient disk space to open and read a Operator response: Check the following:
file v That the file exists
v That there are sufficient file descriptors available to v That the file is in the correct directory
open a file.
v That the file has write permission
Correct any errors that you find, and perform the v That there is sufficient disk space to write the file
action again.
Resolve the problem and rerun the operation.
AWSBWX003E An error has occurred opening the
file "file_name" for reading. AWSBWX006W An error occurred while creating the
directory "directory". The book file is
Explanation: See message. created in the default directory
file_name is the file that cannot be opened. "default_directory".

System action: The action stops. Explanation: See message.

Operator response: Check the following: directory is the directory that cannot be created.
default_directory is the default directory where the book
v That the file exists
file will be created.
v That the file is in the correct directory
System action: The file is saved in the indicated
v That the file has read permission
default directory.
v That there is sufficient disk space to open and read a
file Operator response: If the creation of the book file in
the default directory is acceptable, no action is
v That there are sufficient file descriptors available to
required.
open a file.
Otherwise, check the following:
Correct any errors that you find, and perform the v That the indicated directory name and path is valid
action again.
v That there is sufficient disk space to create the
directory
AWSBWX004E An error has occurred writing the file v That the user performing the operation has write
"file_name". access to the directory path
Explanation: See message.
Correct any error that you find and repeat the
file_name is the file that cannot be written. operation.
System action: The action stops.
Operator response: Check the following: AWSBWX007W An error occurred opening the file
"file_name" for writing. The book file is
v That the file exists
created in the default directory
v That the file is in the correct directory "default_directory".
v That the file has write permission
Explanation: See message.

Chapter 2. Message help 153


file_name is the file that cannot be opened.
default_directory is the default directory where the book
file will be created.
System action: The file is saved in the default
directory.
Operator response: If the creation of the book file in
the default directory is acceptable, no action is
required.
Otherwise, check the following:
v That the specified directory name and path is valid
v That there is sufficient disk space to create the
directory
v That the user performing the operation has write
access to the directory path

Correct any error that you find and repeat the


operation.

154 IBM Tivoli Workload Scheduler: Messages


AWKCAL001E • AWKCAL008E

Calendar - CAL
This section lists error and warning messages that could be issued by the Calendar
functions.

The message component code is CAL.


Explanation: The format of the string containing the
AWKCAL001E The specified start date and time
list of dates provided in input to the calendar
startDateTime is greater than the end date
constructor is incorrect or does not comply to the
and timeendDateTime.
yyyymmdd-hh:mm, [yyyymmdd-hh:mm] syntax.
Explanation: You asked to calculate the list of dates
System action: The Calendar object is not created.
matched by this calendar in a specified interval, but the
specified start date and time of this interval is greater Operator response: Review the string and ensure that
than the end date and time. it complies with the syntax specified in the message
explanation.
System action: The list of matching dates is not
returned.
AWKCAL006E Cannot specify the starting hour in a
Operator response: Specify the correct values for the
recurring rule of the following type:
start and end date and time.
type.
Explanation: You specified a starting hour in a
AWKCAL002E The specified start date and time
recurring calendar rule that does not support this
startDateTime is greater than the end date
feature, for example, in an hourly rule.
and timeendDateTime.
System action: The recurring rule is not created
Explanation: The start date and time you have
specified for the time interval during which a calendar Operator response: Use the setStartDateTime() method
is valid is greater than the corresponding end date and of the rule or of the entire Calendar to specify the hour
time. and minutes from which an hourly rule must start.
System action: The Calendar object is not created.
AWKCAL007E Cannot specify a weekday in a
Operator response: Specify the correct values for the
recurring rule of the following type:
calendar validity interval start and end date and time.
type.
Explanation: You specified a weekday (for example,
AWKCAL003E At least one start date and time must
Monday, Friday) in a recurring calendar rule that does
be specified for the calendar or the
not support weekdays, for example, in a
recursion rule. Rule inclusionRule.
monthly-by-date or in a daily or yearly rule.
Explanation: When you define a recursion rule, you
System action: The recurring rule is not created
must specify a start date and time, either at the rule
level or at the calendar level. Operator response: Do not specify a weekday when
defining a recurring rule of the following types: daily,
System action: The Calendar object is not created.
monthly by date or yearly.
Operator response: Specify the start date and time
either at rule or calendar level.
AWKCAL008E Cannot specify a weekday with an
offset in a recurring rule of the
AWKCAL004E The format of the crontab string is following type: type.
incorrect: Message_exception.
Explanation: You specified a weekday offset (for
Explanation: The format of the crontab string example, 3nd Monday, or 2nd-last Friday) in a
provided in input to the calendar constructor is recurring calendar rule that does not support weekdays
incorrect or does not comply with the crontab syntax offsets, for example, in a daily, weekly, or yearly rule.
rules.
System action: The recurring rule is not created
System action: The Calendar object is not created.
Operator response: Do not specify a weekday offset
Operator response: Review the crontab string and when defining a weekly rule (for example, every 3
ensure that it complies with a valid crontab rule. weeks), a daily rule (for example, every 4 days), or a
yearly rule (for example, every year).
AWKCAL005E The string containing the list of dates
is incorrectMessage_exception.

Chapter 2. Message help 155


AWKCAL009E • AWKCAL018E

AWKCAL009E Cannot specify a day of the month in AWKCAL018E The specified crontab string is
a recurring rule of the following type: incorrect because it contains too many
type. tokens: crontab_string.
Explanation: You specified a day of the month (for Explanation: The format of the crontab string
example, 2, 15, 19, 27) in a recurring calendar rule that provided in input to the calendar constructor is
does not support month days, for example, in a daily, incorrect because it contains too many tokens. You
weekly, or monthly-by-weekday rule. cannot concatenate crontab strings.
System action: The recurring rule is not created System action: The Calendar object is not created.
Operator response: Do not specify a month day when Operator response: Review the crontab string and
defining a weekly rule (for example, every 3 weeks), a ensure that it complies with a valid crontab rule.
daily rule (for example, every 4 days), or a
monthly-by-day rule (for example, every 3 months on
the 2nd Monday of the month).

AWKCAL010E Cannot specify a month of the year in


a recurring rule of the following type:
type.
Explanation: You specified a month (for example,
February) in a recurring calendar rule that does not
allow you to specify the month, for example, a yearly
rule.
System action: The recurring rule is not created
Operator response: Do not specify months on a yearly
rule. To set the start date and time of the yearly rule,
set the start date and time either in the rule definition
or at the calendar level.

AWKCAL011E Cannot specify a day of the year in a


recurring rule of the following type:
type.
Explanation: You specified a day of the year (for
example, day 239) in a recurring calendar rule that
does not support days of the year, for example, a daily
or weekly or monthly rule.
System action: The recurring rule is not created
Operator response: Do not specify a year of the day
when defining a weekly rule (for example, every 3
weeks), a daily rule (for example, every 4 days), or a
monthly-by-day or by-date rule.

AWKCAL012E The recurring rule is incorrect: it


contains neither a start date and time
nor a specific hour-minute keyword.
Explanation: A recurring rule must contain at least a
start date and time value, or an hour and minute value.
System action: The recurring rule is not created
Operator response: Ensure that the recurring rule
contains at least a start date and time value, or an hour
and minute value.

156 IBM Tivoli Workload Scheduler: Messages


AWSCCM002W

CCMDB integration messages - CCM


This section lists error and warning messages that could be issued by the CCMDB
integration..

The message component code is CCM.

AWSCCM002W The workstation "workstation" has not


been added in the book file. Cannot
resolve the host name or host address.
Explanation: See message.
System action: The program continues and the book
file is created correctly.
Operator response: Check that the correct host name
or host address is specified in the workstation
definition available in the Tivoli Workload Scheduler
database.

Chapter 2. Message help 157


AWKCDM001W • AWKCDM011E

Change and configuration management database messages - CDM


This section lists error and warning change and configuration management database
messages that could be issued.

The message component code is CDM.


Explanation: See message text.
AWKCDM001W An error occurred while loading the
user configuration file "config_file". The System action: The operation is not performed.
following error was returned: "error".
The default values will be used. Operator response: Specify the required parameter.

Explanation: The configuration file cannot be read


from the Tivoli dynamic workload broker configuration AWKCDM007E The command failed because it
directory. included an unsupported parameter
"parameter".
System action: See message text.
Explanation: See message text.
Operator response: Check whether the configuration
file located in the Tivoli dynamic workload broker System action:
configuration directory is corrupted, locked, or missing. Operator response: Check the command syntax and
retry the operation.
AWKCDM002E An error occurred while getting the
configuration file "config_file". The AWKCDM008E The operation failed because the
following error was returned: "error". URL specified for the Tivoli dynamic
Explanation: The configuration file cannot be found in workload broker server URLis not
the Tivoli dynamic workload broker jar files. correct.

System action: Explanation: See message text.

Operator response: Check whether the jar files in the System action: See message text.
Tivoli dynamic workload broker installation directory Operator response: Correct the URL.
are corrupted or missing. If the problem persists,
contact IBM Software Support.
AWKCDM009E A problem occurred while contacting
the Tivoli dynamic workload broker
AWKCDM003E Unable to find the configuration file server. The Tivoli dynamic workload
"config_file" . broker service is not available.
Explanation: See message text. Explanation: See message text.
System action: None System action: See message text.
Operator response: Check whether the jar files in the Operator response: Check that the Tivoli dynamic
Tivoli dynamic workload broker installation directory workload broker server is up and running and that it
are corrupted or missing. If the problem persists, can be contacted.
contact IBM Software Support.

AWKCDM010E Unable to invoke Tivoli dynamic


AWKCDM005E An exception occurred on the workload broker Web Services because
CCMDB server. The following error was an incorrect parameter was specified.
returned: "error".
Explanation: See message text.
Explanation: See message text.
System action: The operation was not performed.
System action:
Operator response: Check the parameters and try
Operator response: Check that the Tivoli Change and again.
Configuration Management Database server is up and
running and that it can be contacted.
AWKCDM011E Unable to invoke Tivoli dynamic
workload broker Web Services.
AWKCDM006E The operation failed because the
required parameter "parameter" is Explanation: See message text.
missing. Include it in the command or System action: The operation was not performed.
in the configuration file.

158 IBM Tivoli Workload Scheduler: Messages


AWKCDM012E • AWKCDM014E

Operator response:

AWKCDM012E Unable to connect to the Tivoli


dynamic workload broker server. The
user credentials might be incorrect.
Explanation: See message text.
System action: The operation was not performed.
Operator response: Check the user name and
password and retry the operation.

AWKCDM013E The operation failed because the


user is not authorized to perform it.
Explanation: See message text.
System action: The operation was not performed.
Operator response: Log on with the required level of
authorization and retry the operation.

AWKCDM014E An unexpected error occurred.


Explanation: See message text.
System action: The operation is not performed.
Operator response: Check the trace file for more
information about the error.

Chapter 2. Message help 159


AWSCDW002E • AWSCDW011E

Clustering messages - CDW


This section lists error and warning messages that could be issued when using the
Windows® clustering facility.

The message component code is CDW.

AWSCDW002E The cluster service is installed and AWSCDW006E An error has occurred opening the
configured on the node "node_name", but cluster "cluster_name".
is not currently running.
Explanation: See message.
Explanation: See message.
cluster_name identifies the cluster that has been opened.
node_name identifies the node where the cluster service
System action: The program cannot proceed.
is installed and configured but not running.
Operator response: Check that the correct name has
System action: The program cannot proceed.
been used for the cluster. If not, retry the operation
Operator response: Start the cluster service and retry using the correct name. If the correct name has been
the installation of the Tivoli Workload Scheduler cluster used, this is an internal error; contact IBM Software
resource. Support for assistance.
See also: Readme for the fix in which the clustering
option was made available. AWSCDW007E The program cannot identify the
available nodes on the cluster.
AWSCDW003E The cluster service is not installed on Explanation: See message.
the node.
System action: The program cannot proceed.
Explanation: See message.
Operator response: Try to reinstall the Tivoli
System action: The program cannot proceed. Workload Scheduler cluster resource again. You can
optionally choose to specifically identify the hosts using
Operator response: Install and configure the cluster
the hosts parameter.
service on the node, start the cluster service, and retry
the installation of the Tivoli Workload Scheduler cluster See also: Readme for the fix in which the clustering
resource. option was made available.
See also: Readme for the fix in which the clustering
option was made available. AWSCDW010E The program cannot install the
remote service "service_name" on node :
"node_name".
AWSCDW004E The cluster service is installed on the
node but has not yet been configured. Explanation: See message.
Explanation: See message. service_name identifies the service which cannot be
installed.
System action: The program cannot proceed.
node_name identifies the node on which you are trying
Operator response: Configure the cluster service on
to install it.
the node, start the cluster service, and retry the
installation of the Tivoli Workload Scheduler cluster System action: The program cannot proceed.
resource.
Operator response: Do the following:
See also: Readme for the fix in which the clustering 1. Check that the user and password you are using are
option was made available. correct
2. Check the network connection
AWSCDW005E An internal error has occurred. The 3. Check if Service Manager is running on the remote
program cannot read the cluster host and close it if it is.
information.
Correct any errors and retry the remote installation.
Explanation: See message.
See also: Readme for the fix in which the clustering
System action: The program cannot proceed. option was made available.
Operator response: Contact IBM Software Support for
assistance. AWSCDW011E The program cannot save the registry
key on the node "node_name".

160 IBM Tivoli Workload Scheduler: Messages


AWSCDW013E • AWSCDW021E

Explanation: See message. The probable reason is that


AWSCDW017E The program cannot open the cluster
the network connection has broken before the registry
object "object_name".
could be updated.
Explanation: See message.
node_name identifies the node on which the installation
cannot save the registry key. object_name identifies the object that cannot be opened.
Probably an incorrect object name has been used.
System action: The program cannot proceed.
System action: The program cannot proceed.
Operator response: Check the network connection.
When you are sure that the network connection is Operator response: Retry the installation, specifying
working correctly, rerun the installation. valid values for the "group", "ip" , and "net"
parameters.
See also: Readme for the fix in which the clustering
option was made available. See also: Readme for the fix in which the clustering
option was made available.
AWSCDW013E The program cannot copy the file
"file_name" to "dest_name". AWSCDW018E The program cannot add the Tivoli
Workload Scheduler cluster resource to
Explanation: See message.
the group.
file_name is the file that the installation needs to copy.
Explanation: See message.
dest_name is the destination name for the copy that the
System action: The program cannot proceed.
program wants to use but cannot.
Operator response: Check in the log for the system
System action: The program cannot proceed.
error to understand why the cluster resource could not
Operator response: Check the following: be added to the group. Use the cluster documentation
v That the file exists and operating system documentation to resolve the
problem. Retry the installation, or use the option to add
v That the user running the program has read the resource manually.
permission for the file
v That the destination path exists See also: Readme for the fix in which the clustering
option was made available.
v That the user running the program has write
permission in the destination directory
v That there is sufficient space in the destination AWSCDW019E An internal error has occurred. The
directory fileset program cannot convert a string to or
from UNICODE characters.
Correct any error that you find and retry the operation.
Explanation: See message.
See also: Readme for the fix in which the clustering
option was made available. System action: The program cannot proceed.
Operator response: Contact IBM Software Support for
AWSCDW015E The program cannot register the assistance.
cluster dll, and so cannot install the
Tivoli Workload Scheduler resource. AWSCDW020E An internal error has occurred. The
Explanation: See message. program cannot locate the Windows
common directory.
System action: The program cannot proceed.
Explanation: See message.
Operator response: Check in the log for the system
error to understand why the dll could not be System action: The program cannot proceed.
registered. Use the cluster documentation and Operator response: Contact IBM Software Support for
operating system documentation to resolve the assistance.
problem. Then rerun the installation, or use the option
to add the dll manually.
AWSCDW021E The program cannot obtain the
See also: Readme for the fix in which the clustering <TWSHome> directory from the Tivoli
option was made available. Workload Scheduler Windows services.
Check that the values for the domain
and user parameters are valid.
Explanation: See message.
System action: The program cannot proceed.

Chapter 2. Message help 161


AWSCDW022W • AWSCDW028W

Operator response: Check that the values for the 2. Add the <TWSUser> to the local administrator group
domain and user parameters are valid. on all target hosts.
Check that the Tivoli Workload Scheduler services are Note: only modify the local security policy and the local
installed correctly by checking the Windows Services administrator group. The domain equivalents must be
Manager utility. The following services must be present: left unchanged.
v Tivoli Workload Scheduler (for TWSuser) See also: Readme for the fix in which the clustering
v Tivoli Netman (for TWSuser) option was made available.
v Tivoli Token Service (for TWSuser)
v Autotrace Runtime AWSCDW026W The program cannot remove the
v WebSphere Application Server Tivoli Workload Scheduler cluster
service on the node "host_name".
If any are missing, Tivoli Workload Scheduler must be
uninstalled and reinstalled. The cluster installation can Explanation: See message text.
then be repeated. host_name identifies the node from which the cluster
services cannot be removed.
If no services are missing, this is an internal error;
contact IBM Software Support for assistance. System action: The program proceeds.

See also: Readme for the fix in which the clustering Operator response: The Tivoli Workload Scheduler
option was made available. cluster service must be removed manually.
See also: Readme for the fix in which the clustering
AWSCDW022W The program cannot add the option was made available.
"key_name" key into the "localopts" file.
Add the key manually. AWSCDW027W The program cannot remove the
Explanation: See message. Tivoli Workload Scheduler registry key
on the node "host_name".
key_name identifies the key object that cannot be
added/changed. Explanation: See message text.

System action: The program proceeds. host_name identifies the node from which the registry
key cannot be removed.
Operator response: Add the clusterinstancename
option to the localopts file on the computer before System action: The program proceeds.
attempting to use the cluster service. The value of the Operator response: The Tivoli Workload Scheduler
option must be set to the Tivoli Workload Scheduler registry key must be removed manually.
cluster resource instance name.
See also: Readme for the fix in which the clustering
See also: Readme for the fix in which the clustering option was made available.
option was made available.

AWSCDW028W The program cannot check whether


AWSCDW023W The program cannot modify the the custom Tivoli Workload Scheduler
local security policy on the target host. cluster resource type is already installed.
Explanation: See message. Explanation: See message text.
System action: The program cannot proceed. System action: The program proceeds.
Operator response: Perform the following manually Operator response: Check whether the custom Tivoli
before attempting to use the cluster service: Workload Scheduler cluster resource type is already
1. Manually add the following user privileges to the installed. Attempt to determine why the program could
local security policy for the <TWSUser> in all target not check for its existence. Check that the user
hosts: performing the cluster installation has permission to
v Act as part of the operating system read the registry on the remote node. Correct any
errors you find and rerun the command.
v Increase quotas
v Log on as batch job See also: Readme for the fix in which the clustering
option was made available.
v Log on as a service
v Log on locally
v Replace a process level token

162 IBM Tivoli Workload Scheduler: Messages


AWSCDW029E • AWSCDW039W

See also: Readme for the fix in which the clustering


AWSCDW029E The program cannot determine the
option was made available.
Windows boot disk from the remote
registry on the node "host_name".
AWSCDW036W The program cannot delete the
Explanation: See message text.
temporary file "dll_temp_file_name".
host_name identifies the remote node where the
Explanation: See message text.
Windows boot disk cannot be determined.
dll_temp_file_name identifies the temporary file used in
System action: The program stops.
the remote cluster installation, that could not be
Operator response: Check the network connections. deleted.
Check that the user performing the cluster installation
System action: The program continues.
has permission to read the registry on the remote node.
Correct any errors you find and rerun the command. Operator response: Check whether the file exists. If it
does, delete it.
See also: Readme for the fix in which the clustering
option was made available. See also: Readme for the fix in which the clustering
option was made available.
AWSCDW031E The program cannot determine the
version of the custom Tivoli Workload AWSCDW037W The custom Tivoli Workload
Scheduler cluster resource type dll. Scheduler cluster resource type dll to be
installed is older than the dll currently
Explanation: See message text.
installed. Press "ESC" to exit from the
System action: The program stops. installation or any key to continue.
Note: during the upgrade the custom
Operator response: Check the network connections.
Tivoli Workload Scheduler cluster
Check that the user performing the cluster installation
resource might be restarted.
has permission to access the custom Tivoli Workload
Scheduler cluster resource type dll on the remote node. Explanation: The program has compared the versions
Check that the path to the dll indicated in the registry of the installed dll with the one to be installed, and has
is correct. Correct any errors you find and rerun the determined that the installed dll is newer. You are
command. offered the choice to continue or exit from the
installation. If you continue, the installation of an older
See also: Readme for the fix in which the clustering
dll might compromise the functioning of other
option was made available.
programs on the computer that use the dll.
System action: The program waits for your response.
AWSCDW034E The program cannot determine the
path to the custom Tivoli Workload Operator response: Press ESC to exit from the
Scheduler cluster resource type dll. installation or any key to continue.
Explanation: See message text. See also: Readme for the fix in which the clustering
option was made available.
System action: The program stops.
Operator response: Check the network connections.
AWSCDW039W The program cannot create the script
Check that the user performing the cluster installation
to start or stop the Tivoli Workload
has permission to access the custom Tivoli Workload
Scheduler custom cluster resource
Scheduler cluster resource type dll on the remote node.
instance.
Correct any errors you find and rerun the command.
Explanation: See message text.
See also: Readme for the fix in which the clustering
option was made available. System action: The program continues but the script
is not created.
AWSCDW035E The program cannot update the Operator response: Check that there is sufficient space
custom Tivoli Workload Scheduler in the <TWSHome> directory to create a file. Check
cluster resource type dll. that the user has the rights to create a file in that
directory.
Explanation: See message text.
After the installation has finished, create the file
System action: The program stops.
manually following the instructions in the readme.
Operator response: Update the dll using the Microsoft
See also: Readme for the fix in which the clustering
cluster command line.
option was made available.

Chapter 2. Message help 163


AWSCDW042E • AWSCDW049W

Operator response: Check the syntax of the command


AWSCDW042E The command-line parameter
by issuing it with just the "-u" parameter, or by looking
"parameter" is not correct.
in the documentation. Retry the command with the
Explanation: You have supplied an unrecognizable correct syntax.
command-line parameter.
System action: The program cannot proceed. AWSCDW047W The password cannot be validated.
Either you have specified an incorrect
Operator response: Check the syntax of the command
password or the program cannot
by issuing it with just the "-u" parameter, or by looking
validate it (probably because it does not
in the documentation. Retry the command with the
have the correct permission to do so).
correct syntax.
Explanation: The supplied password is either
incorrect, or cannot be validated. It is not critical to the
AWSCDW043E The context of the supplied
installation process, but is used by the process being
command line string
installed. The installation program might not have the
"command_line"indicates that a pair of
correct permissions to validate the password, in which
quotation symbols (’) is required.
case you can ignore this warning and continue the
However, the first of the pair is missing.
installation.
Explanation: See message.
System action: The program waits for you decide
System action: The program cannot proceed. what to do.

Operator response: Check the syntax of the command Operator response: Check that the password is
by issuing it with just the "-u" parameter, or by looking correctly specified according to the rules of the
in the documentation. Retry the command with the computer where it is to be used.
correct syntax. If the password is not correct, press ESC to exit from
the installation and specify a new password.
If you are certain that the password is correct, press
AWSCDW044E The context of the supplied any key to continue. Note that if you continue with an
command line string "command_line" incorrect password, the service will be installed on all
indicates that a pair of quotation nodes on the cluster with that incorrect password, and
symbols (’) is required. However, the you will have to change it on all of those nodes before
last of the pair is missing. the service can be made operational.
Explanation: See message.
System action: The program cannot proceed. AWSCDW048E You cannot install Tivoli Workload
Scheduler in this cluster environment.
Operator response: Check the syntax of the command The only supported environment is the
by issuing it with just the "-u" parameter, or by looking Microsoft Cluster service on Windows
in the documentation. Retry the command with the Server 2003.
correct syntax.
Explanation: You have tried to install Tivoli Workload
Scheduler on a cluster environment that is not
AWSCDW045E The command-line parameter supported.
"parameter" is mandatory.
System action: The installer stops.
Explanation: You have issued a command omitting
the indicated mandatory parameter. Operator response: Check the cluster environment
where you want to install Tivoli Workload Scheduler.
System action: The program cannot proceed. You might be able to upgrade it to the supported
Operator response: Check the syntax of the command environment.
by issuing it with just the "-u" parameter, or by looking
in the documentation. Retry the command with the AWSCDW049W The user "user_ID" was not found.
correct syntax. Press ESC to exit from the installation
or any key to continue.
AWSCDW046E The command-line parameter Explanation: The program is unable to find a user
"parameter" has been supplied with a with the name specified.
value "parameter_value" that is outside
the permitted range "range_value". System action: The program waits for you decide
what to do.
Explanation: See message.
Operator response: Verify that the user exists and that
System action: The program cannot proceed. the Windows Domain Controller is reachable. If the
problem can be resolved without stopping the

164 IBM Tivoli Workload Scheduler: Messages


AWSCDW050E • AWSCDW054E

installation, just press any key to continue. Otherwise,


AWSCDW054E The program cannot obtain the Tivoli
when you have corrected the error, retry the operation.
Workload Scheduler home directory
from the "cluster_resource_name" cluster
AWSCDW050E The operation cannot be completed resource.
because a Tivoli Workload Scheduler
Explanation: See message text.
cluster resource called
"cluster_resource_name" already exists, and cluster_resource_name identifies the name of the Tivoli
also points to this Tivoli Workload Workload Scheduler cluster resource.
Scheduler agent.
System action: The installer stops.
Explanation: You have tried to define a new cluster
Operator response: Check the system error message
resource that points to the same Tivoli Workload
that follows to understand why the program cannot
Scheduler agent of an existing cluster resource.
determine the home directory property. Use the cluster
cluster_resource_name identifies the name of the existing documentation and operating system documentation to
cluster resource that already points to this agent. resolve the problem. Retry the operation.
System action: The installer stops.
Operator response: Check the parameters of the
command to ensure that you have not made an error
with the resource name. Check whether the existing
cluster resource is correctly named. Resolve the
duplication and retry the command.

AWSCDW051E A cluster resource with the name


"cluster_resource_name" already exists.
Choose a different resource name.
Explanation: See message text.
cluster_resource_name identifies the name used to create
the new Tivoli Workload Scheduler cluster resource.
System action: The installer stops.
Operator response: Choose a different resource name
and retry the command.

AWSCDW052E The operation to rename the cluster


resource "current_cluster_resource_name" in
"new_cluster_resource_name" has failed.
Explanation: See message text.
current_cluster_resource_name identifies the name of the
existing Tivoli Workload Scheduler cluster resource to
rename.
new_cluster_resource_name identifies the selected new
name of the Tivoli Workload Scheduler cluster resource.
System action: The installer stops.
Operator response: Check the system error message
that follows to understand why the cluster resource
could not be renamed. Use the cluster documentation
and operating system documentation to resolve the
problem. Retry the operation.

Chapter 2. Message help 165


AWKCLI001E • AWKCLI042E

Command line messages - CLI


This section lists error and warning messages that could be generated by the
dynamic workload broker Command Line Interface.

The message component code is CLI.


Explanation: See message text.
AWKCLI001E An error occurred while getting the
configuration file "config_file". The System action: The operation is not performed.
following error was returned: "error".
Operator response: Check that the default
Explanation: See message text. configuration file is correct.
System action: The application will use the default
values. AWKCLI035E Unable to read configuration files.
Operator response: Check the configuration file path. Explanation: See message text.
System action: The operation is not performed.
AWKCLI013E The required variable "variable" is
missing from the configuration file. Operator response: Check that the configuration file is
correct.
Explanation: See message text.
System action: The operation is not performed. AWKCLI036E The command failed because the
variable "variable" is not present in the
Operator response: Define the variable in
configuration file.
configuration file.
Explanation: A required variable cannot be found in
the configuration file.
AWKCLI031E The command failed because of a
missing mandatory parameter System action: The operation is not performed.
"parameter".
Operator response: Set the variable in configuration
Explanation: See message text. file and try again.
System action: The operation is not performed.
AWKCLI040E The command failed because the
Operator response: Insert the missing parameter.
parameter "VALUE_0" is not specified as
a command parameter and the property
AWKCLI032E The command failed because of a "VALUE_1" is not present in the
missing value for a parameter: configuration file.
"parameter"
Explanation: See message text.
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Specify the required parameter.
Operator response: Insert the missing parameter
value.
AWKCLI041E The command failed because of a
missing parameter. One of the following
AWKCLI033W Unable to read the configuration file parameters is required: "parameter_1" ,
"file_name . The default configuration parameter_2 .
file will be used.
Explanation: See message text.
Explanation: The configuration file might be
System action: The operation is not performed.
corrupted or missing.
Operator response: Define the missing parameter.
System action: The operation continues using values
from the default file.
AWKCLI042E The command failed because the
Operator response: Check that the configuration file is
following mutually exclusive parameters
correct.
were both included. "parameter_1" ,
"parameter_2" .
AWKCLI034E Unable to read the default
Explanation: See message text.
configuration file.

166 IBM Tivoli Workload Scheduler: Messages


AWKCLI043E • AWKCLI054E

System action: The operation is not performed. Operator response: A valid Tivoli dynamic workload
broker server address must be specified in the
Operator response: Reissue the command specifying
configuration file.
only one of the parameters.

AWKCLI050E The Tivoli dynamic workload broker


AWKCLI043E The command failed because a
server address "address"is not in a correct
variable has an incorrect format:
format.
"VALUE_0".
Explanation: The Tivoli dynamic workload broker
Explanation: See message text.
server address found in the configuration file is not a
System action: The operation is not performed. valid address.

Operator response: Check the JSDL variable format. System action:


Operator response: Check the Tivoli dynamic
AWKCLI044E The command failed because neither workload broker server address format.
of the following affinity parameters was
specified: "parameter_1" , "parameter_2" .
AWKCLI051E An unexpected error occurred while
. One of the parameters must be
submitting the job.
specified.
Explanation: See message text.
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Check the log file for information
Operator response: Specify one of the affinity
about the cause of the error.
parameters.

AWKCLI052E Unable to find the JSDL file


AWKCLI045E The command failed because only one
"file_name".
of the following affinity parameters can
be specified: "parameter_1" , parameter_2 . Explanation: See message text.
Explanation: See message text. System action: The operation is not performed.
System action: The operation is not performed. Operator response: Check that the JSDL file is present
in the specified directory.
Operator response: Check the affinity parameters
specification.
AWKCLI053E The JSDL file format is not correct:
"VALUE_0" --- "VALUE_1".
AWKCLI046E The command failed because of an
incorrect affinity format: "VALUE_0". Explanation: The JSDL file is not well formed
according to the JSDL specification.
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Check the JSDL file format
Operator response: Check the affinity parameter
format.
AWKCLI054E Tivoli dynamic workload broker
server service is not available
AWKCLI047E The command failed because
parameter "parameter" is not applicable. Explanation: Possible causes are:
Explanation: See message text. v The server cannot be contacted, is not responding, or
is switched off.
System action: The operation is not performed.
v The service is already active or has been disabled.
Operator response: Correct the command and try
System action:
again.
Operator response: Check the status and the
accessibility of the Tivoli dynamic workload broker
AWKCLI049E Unable to find the address of a Tivoli
server.
dynamic workload broker server in the
configuration file.
Explanation: No Job Dispatcher is specified.
System action:

Chapter 2. Message help 167


AWKCLI055E • AWKCLI070E

Operator response: Correct the command and try


AWKCLI055E The operation failed because the input
again.
parameter is incorrect. "parameter"
Explanation: One of the parameters cannot be
AWKCLI065E The job definition file "file_name"
processed by the Tivoli dynamic workload broker
contains errors.
server
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: None.
Operator response: Check for errors in the job
definition file.
AWKCLI056E Tivoli dynamic workload broker
server - operation failed. VALUE_0
AWKCLI066E The job definition name "job_def"is not
Explanation: See message text.
correct.
System action: The operation is not performed.
Explanation: See message text.
Operator response: None.
System action: The operation is not performed.
Operator response: Check the job name.
AWKCLI057E An unexpected error occurred.
Explanation: See message text.
AWKCLI067E Unable to find the job definition
System action: The operation is not performed. "job_def" .
Operator response: Check the log file for more Explanation: See message text.
information about the error.
System action: The operation is not performed.
Operator response: Check whether the specified job
AWKCLI059E Unable to find job ID "jobID".
exists.
Explanation: See message text.
System action: The operation is not performed. AWKCLI068E The command failed because of an
incorrect query parameter.
Operator response: Check whether the specified job
ID exists. Explanation: See message text.
System action: The operation is not performed.
AWKCLI060E The operation failed because the
Operator response: Specify a supported parameter.
specified state is not a valid job state.
Explanation: See message text.
AWKCLI069E The specified job state "state"is not
System action: The operation is not performed. valid.
Operator response: Check whether the specified state Explanation: See message text.
is correct.
System action: The operation is not performed.
Operator response: Correct the specified job state.
AWKCLI061E The operation failed because job ID
"jobID"is not correct.
AWKCLI070E One of the selection criteria must be
Explanation: See message text.
specified.
System action: The operation is not performed.
Explanation: See message text.
Operator response: Check whether the specified job
System action: The operation is not performed.
ID is correct.
Operator response: Relaunch command specifying
one of the selection criteria as described in command
AWKCLI063E The operation failed because of an
usage.
incorrect parameter and value:
"parameter" , "value". This parameter does
not support wildcards.
Explanation: See message text.
System action: The operation is not performed.

168 IBM Tivoli Workload Scheduler: Messages


AWKCLI072E • AWKCLI102E

AWKCLI072E Unable to find job status "status". AWKCLI090E An unexpected error occurred. Unable
to contact the Tivoli dynamic workload
Explanation: You have specified an incorrect job
broker server.
status.
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Correct the job status and try
again. Operator response: Check whether the Tivoli dynamic
workload broker server is running and can be reached.
AWKCLI073E The command failed because the date
"date" is in an incorrect format. The AWKCLI098E The command failed because of a
valid format is "date_format" missing value for parameter "parameter" .
Explanation: See message text. Explanation: See message text.
System action: The operation is not performed. System action: The operation is not performed.
Operator response: Correct the date and try again. Operator response: Retry the command specifying the
missing value.
AWKCLI074E You have specified an incorrect date:
"date" AWKCLI099E The command failed because a
mandatory parameter "parameter" is
Explanation: See message text.
missing.
System action: The operation is not performed.
Explanation: See message text.
Operator response: Correct the date and try again.
System action: The operation is not performed.
Operator response: Retry the command specifying the
AWKCLI075E The date from "date_1"to "date_2" is not
missing parameter.
valid.
Explanation: See message text.
AWKCLI100E The command failed because the value
System action: The operation is not performed. specified for the offset parameter "offset"
is out of range. Specify a number
Operator response: Correct the dates and try again. between 0 and "Long_MAXVALUE".
Explanation: See message text.
AWKCLI087E Unable to find JSDL file "file_name" .
System action: The operation is not performed.
Explanation: See message text.
Operator response: See message text.
System action: The operation is not performed.
Operator response: Check the JSDL file path. AWKCLI101E The command failed because the value
specified for the sizePage parameter
AWKCLI088E "Unable to connect to the Tivoli "page_size" is out of range. Enter a valid
dynamic workload broker server.". number between 0 and
"Integer_MAXVALUE".
Explanation: See message text.
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Check whether the Tivoli dynamic
workload broker server is running and can be reached. Operator response: See message text.

AWKCLI089E Unexpected exception received while AWKCLI102E A database error occurred. The
submitting the job. internal error returned by the database
manager is: "db_error".
Explanation: See message text.
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Check the log file for more
information about the error. Operator response: Check the database status and
availability.

Chapter 2. Message help 169


AWKCLI105E • AWKCLI154E

AWKCLI105E The command failed because the AWKCLI130E You have specified an incorrect date:
format of the Resource Definition file is "date".
incorrect.
Explanation: See message text.
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Correct the date.
Operator response: Check the resource definition file.
AWKCLI132E The Job Dispatcher service is
AWKCLI109E Incorrect JSDL file format "VALUE_0" unavailable.
--- "VALUE_1".
Explanation: See message text.
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Check whether the Job Dispatcher
Operator response: Check the JSDL file. is running and can be reached.

AWKCLI110E The job ID "JobID" is not correct. AWKCLI134E The job ID "jobID" is incorrect.
Explanation: See message text. Explanation: See message text.
System action: The operation is not performed. System action: The operation is not performed.
Operator response: Correct the job ID. Operator response: Check the job ID and retry the
operation.
AWKCLI120E The command failed because of
incorrect input parameters "parameters" . AWKCLI135E The specified job state "state" is not
correct.
Explanation: See message text.
Explanation: See message text.
System action: The operation is not performed.
System action: The operation is not performed.
Operator response: Check the input parameters.
Operator response: Check the state value and the
allowed values.
AWKCLI121E "Resource Advisor - Operation failed.".
Explanation: See message text.
AWKCLI150E The job definition JOB_NAME cannot
System action: The operation is not performed. be updated. It is not present in the Job
Repository.
Operator response: Check the log files and retry the
operation. Explanation: See message text.
System action: The operation is not performed.
AWKCLI122E Job Dispatcher - Operation
Operator response: Check that the specified job
failed.VALUE_0.
definition name is correct.
Explanation: See message text.
System action: The operation is not performed. AWKCLI151E The "all_option" option cannot be used
with other query filter options.
Operator response: Check the log files and retry the
operation. Explanation: You can use this option on its own or
define a query using a combination of other options.
AWKCLI129E The specified date "date" is in an System action: The operation is not performed.
incorrect format. The valid format is
Operator response: Check the command usage.
"date_format"
.
AWKCLI154E The specified quantity
Explanation: See message text.
"RESOURCE_QUANTITY" is not an
System action: The operation is not performed. integer. You can specify an integer
within the 0 and 99999999 range.
Operator response: Correct the date format.
Explanation: See message text.

170 IBM Tivoli Workload Scheduler: Messages


AWKCLI155E • AWKCLI170E

System action: The operation is not performed.


Operator response: Specify an integer.

AWKCLI155E The specified quantity


"RESOURCE_QUANTITY_RANGE" is
outside the valid range. You can specify
an integer within the 0 and 99999999
range.
Explanation: See message text.
System action: The operation is not performed.
Operator response: Specify an integer within the 0
and 9999999 range.

AWKCLI156E The specified resource name


"RESOURCE_NAME" is not supported.
Explanation: See message text.
System action: The operation is not performed.
Operator response: Insert a valid resource name.

AWKCLI157E The specified resource type


"RESOURCE_TYPE" is not supported.
Explanation: See message text.
System action: The operation is not performed.
Operator response: Insert a valid resource type.

AWKCLI170E Rollback failed with database error:


"error".
Explanation: An error occurred when trying to
rollback a transaction.
Operator response: See message text.

Chapter 2. Message help 171


AWSDDW008E

Std utility messages - DDW


This section lists std utility error and warning messages that could be issued.

The message component code is DDW and the old message set code is 100 in the
″unison″ message catalog.

AWSDDW008E An I/O error occurred while


accessing a file. A memory dump has
been taken to aid IBM Software Support
with problem determination.
Explanation: See message.
System action: The program proceeds. The file is not
accessed.
Operator response: See the messages that follow this
one to understand why the file could not be accessed.
If you can fix the problem that these messages reveal,
stop the server, fix the problem, and then retry the
operation.
If you cannot fix this problem, or after trying to fix it
the problem persists, contact IBM Software Support
providing the following documentation:
v A tar file of the Tivoli Workload Scheduler work
directory (<TWS_home>)
v The memory dump.

172 IBM Tivoli Workload Scheduler: Messages


AWSDEB009E • AWSDEB017E

SSL messages - DEB


This section lists error and warning messages that could be issued when using SSL.

The message component code is DEB and the old message set code is 105 in the
″unison″ message catalog.
to wait for the DNS server to update its database with
AWSDEB009E Data transmission is not possible
the new or changed host name.
because the connection is broken. The
following gives more details of the If a different type of error is reported, attempt to
error: error_message. resolve it.
Explanation: See message. If the error has been resolved, retry the operation.
error_message describes the error and includes the
operating system error message. AWSDEB011E The socket descriptor is incorrect. The
following gives more details of the
System action: This message is generated by a library
error: error_message.
function that is called by more than one program. The
calling program decides how to process the error that Explanation: See message.
this message has revealed. Look in the log for other
messages following this one to see how Tivoli error_message describes the error and includes the
Workload Scheduler reacts. operating system error message.

Operator response: Use the ping command to check if System action: This message is generated by a library
the two workstations involved can connect to each function that is called by more than one program. The
other. calling program decides how to process the error that
this message has revealed. Look in the log for other
If not, resolve the network problem and restart the messages following this one to see how Tivoli
process that was trying to communicate. Workload Scheduler reacts.
If there is no network problem, and this is the first Operator response: Verify t