App Builder Messages PDF

BluePhoenix AppBuilder 2.1.0.
Messages Reference Guide

BluePhoenix AppBuilder 2.1.0.
Document Title
April, 2003
Corporate Headquarters
BluePhoenix Solutions
Vlierwerf 7B
4704 SB Roosendaal
The Netherlands
+31 (0) 165 399 401
+31 (0) 165 396 308 fax
USA Headquarters
BluePhoenix Solutions USA, Inc.
8000 Regency Parkway
Cary, NC 27511
United States
+1 919.380.5100
+1 919.380.5111 fax
www.bluephoenixsolutions.com
1992-2003 BluePhoenix Solutions

All rights reserved.
BluePhoenix is a trademark of BluePhoenix Solutions. All other product and company names
mentioned herein are for identification purposes only and are the property of, and may be trademarks
of, their respective owners.
Portions of this product may be covered by U.S. Patent Numbers 5,495,222 and 5,495,610 and various
other non-U.S. patents.
The software supplied with this document is the property of BluePhoenix Solutions, and is furnished
under a license agreement. Neither the software nor this document may be copied or transferred by any
means, electronic or mechanical, except as provided in the licensing agreement.
BluePhoenix Solutions has made every effort to ensure that the information contained in this document
is accurate; however, there are no representations or warranties regarding this information, including
warranties of merchantability or fitness for a particular purpose. BluePhoenix Solutions assumes no
responsibility for errors or omissions that may occur in this document. The information in this
document is subject to change without prior notice and does not represent a commitment by
BluePhoenix Solutions or its representatives.
TABLE OF
CONTENTS
Table of Contents
AppBuilder 2.1.0 Messages Reference Guide
1 Rules Language Preparation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Rules Preparation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
2 Execution Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Rules Execution Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Application Execution Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
3 Communications Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

General Communications Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Java Communications Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Interpreting Third-party Error Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Handling Unresolved UNIX Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
4 Enterprise Development Messages (Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Enterprise Development Messages - Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
5 Enterprise Development Messages (Part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Enterprise Development Messages (Part 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
6 Enterprise Execution Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Enterprise Execution Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
7 Enterprise Messages by CICS Abend Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Enterprise Messages by Abend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
8 Trace File Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Trace File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Sample 1: A Successful Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Sample 2: An Unsuccessful Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Index ....................................................................................... i
AppBuilder 2.1.0 Messages Reference Guide i

ii AppBuilder 2.1.0 Messages Reference Guide
CHAPTER
1 RULES LANGUAGE PREPARATION

MESSAGES
When you are preparing a Rules Language rule or an application with rules, you may encounter Rules
Preparation Messages. Generally, the messages that appear are caused by improper Rules Language
syntax and are displayed during code generation. For details on the Rules Language syntax, refer to the
Rules Language Reference Guide.
Each of the Rules Preparation Messages begins with a number and a letter: S, W, or I. The letter indicates
the severity of the message:
S indicates a severe error that prevents preparation of a rule. You must fix a severe error before
continuing.
W indicates a warning and flags a potential problem, but does not prevent preparation. You may
proceed with caution.
I indicates an informational message about your preparation. It does not affect preparation in any
way.
In the tables listing the messages, the number is the message identifier. The messages are listed in
numerical order. Many messages contain placeholders, such as Item1. When one of these messages
appears, the placeholder is replaced by the name of an object, file, or another entity that is causing the
error.
Rules Preparation Messages

Table 1-1 lists the rules preparation messages.
Table 1-1 Rules Preparation Messages

Message
ID Message Text Message Description
00000-I Error in bindfile at line number Item1. There is an error in the bind file at the line number of Item1.
00001-I ERROR Item1 in line Item2. There is an error Item1 in line Item2.
00002-I WARNING Item1 in line Item2. There is an warning Item1 in line Item2.
00003-I INFO Item1 in line Item2. There is information Item1 in line Item2.
00004-I INVALID Item1 in line Item2. There is an invalid Item1 in line Item2.
00005-I ERROR Item1 in line Item2 near Item3. There is an error Item1 in line Item2 near Item3.
AppBuilder 2.1.0 Messages Reference Guide 1-1

Rules Preparation Messages 00006-I
Table 1-1 Rules Preparation Messages (Continued)

Message
WARNING Item1 in line Item2 near
00006-I There is an warning Item1 in line Item2 near Item3.
Item3.
00007-I INFO Item1 in line Item2 near Item3. There is information Item1 in line Item2 near Item3.
00008-I INVALID Item1 in line Item2 near Item3. There is an invalid Item1 in line Item2 near Item3.
The system does not understand something in the
A general syntax error has been indicated line. Make sure that you have spelled everything
00100-S
encountered. correctly and that you are referencing the entitys name.
Check for proper syntax.
This rule has too many error and/or
There are too many messages. Correct all the known errors
00101-S warning messages. No more
and prepare the rule again.
messages will be shown.
The rule is a PCCICS rule: it can be prepared either for the
CICS (mainframe online) or for the PC (workstation)
This rule has been especially prepared
execution environments. The message appears if such a
00368-I for T3270. Windows C code is being
rule is prepared for the workstation. See USE statements in
generated.
the Rules Language Reference Guide for further
clarification.
00888-S Invalid procedure. There was an invalid procedure.
The system was unable to open the rule file of Item1.
Check your hierarchy and Rules Language code. Prepare it
00919-S Unable to open rule file Item1.
again. If you get this message again, contact the System
Administrator.
The system was unable to open the merge listing file of
Unable to open merge listing file Item1.Check your hierarchy and Rules Language code.
00921-S
Item1. Prepare it again. If you get this message again, contact the
System Administrator.
The merge option was disabled. Check your hierarchy and
00922-S Merge option disabled. Rules Language code. Prepare it again. If you get this
message again, contact the System Administrator.
The system was unable to open the listing file of Item1.
00923-S Unable to open listing file Item1.
Administrator.
The system was unable to open the bind file of Item1.
00924-S Unable to open bind file Item1.
Administrator.
The system was unable to open the generated code file of
Unable to open generated code file Item1. Check your hierarchy and Rules Language code.
00925-S
The system was unable to open the augmented bind file of
Unable to open augmented bind file Item1. Check your hierarchy and Rules Language code.
00926-S
The file has ended unexpectedly. The end marker came
Encountered unexpected End-of-File
10109-I directly after the token. Review the code again. If not
pattern.
corrected, this error may lead to upload problems.
These two items occur a different number of times. This
may lead to errors. For instance, mapping data from a
"Item1" and"Item2" occur a different
10260-W source view that occurs more times than the target view
number of times.
may result in lost data. See VIEW in the Rules Language
Reference Guide for further clarification.
1-2 Rules Language Preparation Messages

10261-W Rules Preparation Messages

Message
Line will exceed maximum line length
The line exceeds the maximum line length on the host. The
of Item1 on mainframe. This could be
message is not repeated even if other lines exceed the
due to added Shift-Out Shift-In
10261-W limit. To determine which other lines exceed the limit,
characters. CAUTION: This is the only
correct the indicated line and then prepare the rule again.
time this message occurs, even if
Repeat this cycle until this message does not appear.
more lines exceed correct length.
Numeric item Item1 may not be Some data types are incompatible, and data cannot be
10302-S
mapped to character item Item2. mapped from one to another.
Character item Item1 may not be Some data types are incompatible, and data cannot be
10303-S
mapped to numeric item Item2. mapped from one to another. .
Item1 may not be mapped to the Some data types are incompatible, and data cannot be
10310-S
PICTURE var Item2. mapped from one to another.
Item1 occurs both as source and as
10320-W You are mapping data from an entity to itself.
target.
indicated line. Make sure that you have spelled everything
10889-S This MAP statement has syntax errors.
correctly and that you are referencing the entitys name.
Check for proper syntax.
View Item1 may not be mapped to field The source and destination data types are incompatible,
10991-S
Item2. and data cannot be mapped from one to another.
Field or literal Item1 may not be The source and destination data types are incompatible,
10992-S
mapped to view Item2. and data cannot be mapped from one to another.
Item1 does not represent an unsigned The source and destination data types are incompatible,
10994-S
integer. It may not be mapped to Item2. and data cannot be mapped from one to another.
Item1 can assume a longer value than In your MAP statement, one of the data items may assume
10995-W Item2. Truncation or overflow may a value larger than the other data item. This may lead to
occur. truncation or overflow at run time.
The source and destination data types are incompatible,
10996-S TEXT may not be mapped to IMAGE
and data cannot be mapped from one to another.
The source and destination data types are incompatible,
10998-S IMAGE may not be mapped to TEXT
and data cannot be mapped from one to another.
Item1 is a numeric field. It may not be Item1 is a numeric field. It may not be used in an OVERLAY
11366-S
used in an OVERLAY statement. statement.
Item1 is a signed or non-integer
Item1 is a signed or non-integer PICTURE field. It may not
11377-W PICTURE field. It may not be used in
be used in an OVERLAY statement.
an OVERLAY statement.
You can overlay a view to a field, a view to a view, or a field
Neither of the OVERLAY parameters, or constant to a view. Make sure that you have spelled
11401-S
Item1 nor Item2, are views. everything correctly and that you are referencing the
entitys name.
Resource error: Item1 file Item2 not
13001-S If you get this message, contact the System Administrator.
found.
Internal error: Not enough memory to
allocate data.
Internal error: Internal table Item1
overflow.
Resource error: Bad Item1 table
format in file Item2.
Error in configuration file item1. Line:
Item2.
Error in configuration file Item1. Line
with Item2 not found.

Rules Preparation Messages 13007-S

Message
Internal error: Attempt to allocate
block of size zero (0).
Resource error: Cannot create a file
13008-S Item1. There may not be enough disk If you get this message, contact the System Administrator.
space.
Resource error: Rule file name is not
specified.
Resource error: Error writing to file
13010-S Item1. There may not be enough disk If you get this message, contact the System Administrator.
space.
Resource error: Error in parameters:
Item1.
Resource error: Error in parameters.
Unknown generator type: item1.
13013-S Too many flags, flag is too long, or If you get this message, contact the System Administrator.
flag length=0: Item1.
Unknown option: Item1.
Unknown symbol: Item1.
13016-S Two source file names: Item1 and If you get this message, contact the System Administrator.
item2.
Resource error: Unable to open error
file Item1.
Configuration file Item1 contains a file
name that is too long: Item2.
A file name is too long in the
command line: Item1.
13020-I NO ERRORS DETECTED. No errors detected.
13021-I ONE (1) ERROR DETECTED. One error detected.
13022-I ITEM1 ERRORS DETECTED. Item1 errors detected.
13023-I NO WARNINGS GENERATED. No warnings generated.
13024-I ONE (1) WARNING GENERATED. One warning generated.
13025-I ITEM1 WARNINGS GENERATED. Item1 warnings generated.
Resource error: File Item1 not copied
13026-W If you get this message, contact the System Administrator.
into Item2.
Resource error: File Item1 not
renamed in Item2.
External interface file is not created or
13028-W External interface file is not created or one contains errors.
one contains errors.
Hierarchy does not contain a MAIN See the Developing Applications Guide for further
13029-S
rule. clarification.
The value Item1 under one of the code generation keys in
13030-S Error in registry setting:"Item1" the registry is not valid. If you get this message, contact the
Error in parameters. Closing symbol The pragma must be specified as -yp[PRAGMA ....] If you
13031-S
for the pragma Item1 is missing. get this message, contact the System Administrator.

13032-S Rules Preparation Messages

Message
The configuration file, registry, or command line contains
Too many pragmas in the parameters.
too many pragmas. Solution: Move some of the pragmas to
13032-S Maximum allowed number of pragmas
the rule code. If you get this message, contact the System
is Item1.
Administrator.
Resource error: Item1 by writing table
in file Item2 at line Item3.
This error occurs because a view short name is equal to a
BINDFILE: Ambiguous reference to
13106-S set short name or two different (by mode) views have the
Name Item1 at line Item2.
same name or a view has a subview with the same name.
BINDFILE: Multiple declaration input
or output view.
BINDFILE: The word Item1 is used for
the name of a rule.
BINDFILE: Unable to find declaration
of view Item1.
BINDFILE: Expected section body at
The Universal Section for that entity is not correctly
line Item1 for Universal section
13110-S generated. If you get this message, contact the System
declaration that was mentioned in
Administrator.
previous line.
BINDFILE: Unexpected format type in In Rules Language, there is no such data type for view or
13111-S
view or field section at line Item1. field.
The type of RULE does not correspond to any possible rule
BINDFILE: Invalid type of Rule in bind
13112-S type in Rules Language. If you get this message, contact
file.
the System Administrator.
BINDFILE: Entity "Item1" specified in The entity is present in the hierarchy but does not have
13113-S preparation scope of another entity Universal Section. If you get this message, contact the
does not exist in preparing bindfile. System Administrator.
13114-S BINDFILE: Expected SubRule. If you get this message, contact the System Administrator.
BINDFILE: Unexpected length for
integer or smallint in bind file.
The bind file has ended unexpectedly. The end marker
BINDFILE: Unexpected end of bind file
13116-S came directly after the token. If you get this message,
at line number Item1.
contact the System Administrator.
BINDFILE: Expected Universal section The bind file is not correctly generated. If you get this
13117-S
at line number Item1. message, contact the System Administrator.
BINDFILE: Unexpected type of section Encountered unexpected type in Context Section. If you get
13118-S
at line Item1. this message, contact the System Administrator.
The incorrect format of a bind file. The bind file does not
BINDFILE: In this version, only Rules
contain an entity that can be prepared; the first entity must
13119-S and Reports may be used as preparing
be Rule Section or Report Section or you could get an error.
objects.
If you get this message, contact the System Administrator.
BINDFILE: Expected start section in The first entity in the bind file must be a Start Section. If you
13120-S
bind file at line Item1. get this message, contact the System Administrator.
BINDFILE: Different view names in The view name in Universal Section and the name of 01-
13121-S bind file at line Item1 for $$VIEW and level view are different. If you get this message, contact the
01-level view. System Administrator.
BINDFILE: Expected universal section
for view at line number Item1.
BINDFILE: Expected EOF section or
The incorrect format of bind file. If you get this message,
13123-S encountered unexpected type of
section at line number Item1.
13124-S BINDFILE: Expected end of bind file. If you get this message, contact the System Administrator.


Message
BINDFILE: Unexpected field format in The representation of picture format is invalid. If you get
13125-S
bind file. this message, contact the System Administrator.
BINDFILE: Expected Component
Section at line Item1.
BINDFILE: Expected window section
at line item1.
BINDFILE: Unexpected set format in The designated set is not allowed. If you get this message,
13128-S
Set Section. contact the System Administrator.
BINDFILE: Expected View or Field
Section at line Item1.
BINDFILE: Ambiguous reference to The short names were not correctly generated. If you get
13130-W
Name "Item1" at line Item2. this message, contact the System Administrator.
PANELFILE: Unexpected character at The panel file is not correctly generated. If you get this
13131-W
line Item1. message, contact the System Administrator.
PANELFILE: Unexpected token at line The panel file is not correctly generated. If you get this
13132-W
Item1. message, contact the System Administrator.
PANELFILE: Unexpected end of file at The panel file is not correctly generated. If you get this
13133-W
line Item1. message, contact the System Administrator.
PANELFILE: Invalid integer at line The panel file is not correctly generated. If you get this
13134-W
The panel file is not correctly generated. If you get this
13135-W PANELFILE: Invalid float at line Item1.
message, contact the System Administrator.
PANELFILE: Invalid Boolean at line The panel file is not correctly generated. If you get this
13136-W
PANELFILE: Invalid string at line The panel file is not correctly generated. If you get this
13137-W
PANELFILE: Invalid symbol at line The panel file is not correctly generated. If you get this
13138-W
PANELFILE: Panel file "Item1"not The panel file has not been found. If you get this message,
13139-W
found. contact the System Administrator.
BINDFILE: Type of value Item1 is not
compatible with type of Item2 of set The type of value is not compatible with the type of set; the
13140-W
Item3 at line Item4. Set element set element is ignored.
ignored.
PANELFILE: The same HPSID Item1 is There are two or more objects in the panel file with the
13141-W
used for several different objects. same System ID.
There is an event in the bind file that has neither a Trigger
BINDFILE: Incorrect event section at
13142-S nor an Action attribute. If you get this message contact the
line number Item1.
BINDFILE: Invalid View Hierarchy at
line number Item1.
BINDFILE: Set symbol Item1 redefines
13145-W other set symbol at line Item2. The set If you get this message, contact the System Administrator.
symbol is ignored.
The symbol long name is the same as a Rules Language
BINDFILE: Set symbol Item1 at line
reserved keyword. Change the symbol name if you need to
13146-W Item2 redefines one of the standard
use it in your rule. Refer to the Rules Language Reference
words in Rules Language.
Guide for a list of reserved words.
BINDFILE: Set symbol Item1 at line
Item2 redefines one of the identifiers
declared earlier. The set symbol is
ignored.


Message
BINDFILE: Set symbol Item1 in set
13148-W Item2 redefines other set symbol. Change name of one.
These elements have different values.
BINDFILE: Line Item1. The item
There are two items with the same long name in preparing
13150-W "Item2" redefines other item. The item
bind file.
is ignored.
BINDFILE: Non-character field VALUE
initialization at line Item1. It can be The CHAR value initialization is not for character fields. It
13153-S
used only with Report Writer and can be used only in Report Writer mode.
character fields.
BINDFILE: The VALUE initialization
The CHAR value initialization number is too large. It can be
13154-S value at line Item1 is too large. It can
used only in Report Writer mode.
only be used with Report Writer.
BINDFILE: The VALUE initialization
The CHAR value initialization string's length is too large. It
13155-S string at line Item1 is too large. It can
can be used only in Report Writer mode.
only be used with Report Writer.
BINDFILE: Invalid long name of The long name for this specified entity is invalid. If you get
13156-W
variable "Item1." this message, contact the System Administrator.
BINDFILE: "Item1"- Unrecognized
The system encountered an unrecognized platform. If you
13157-S execution environment in Rule
get this message, contact the System Administrator.
Section.
BINDFILE: Item1 at line Item2 is
13158-W invalid. It can only be used with Report This feature can be used only with Report Writer.
Writer.
BINDFILE: Format string Item1 at line
13159-W Item2 is invalid. It can only be used This feature can be used only with Report Writer.
with Report Writer.
BINDFILE: Processing Report Bindfile
13160-S is allowed only in Report Writer. This feature can be used only with Report Writer.
Processing failed.
BINDFILE: The Short Name Item1 is The short name of any entity is a reserved word. Change
13161-W
the same as the reserved word. the short name of this entity.
The generated format of the bind file is no longer
BINDFILE: In the Bindfile Section
13162-W supported. If you get this message contact the System
Item2, Item1 has invalid format.
Administrator.
Entity declaration has not been specified in any preparation
BINDFILE: Unexpected Section Type
13163-S scope. If you get this message, contact the System
"Item2" at line "Item1".
Administrator.
BINDFILE: Expression "Item2" is not For section report, any number of qualifiers were used. If
13164-W
supported at line Item1. you get this message, contact the System Administrator.
BINDFILE: Incorrect redefine
The field could not redefine view. If you get this message,
13165-S relationship at line Item2. Field Item1
cannot redefine view.
BINDFILE: The long name "Item1" at
The long name of the entity is the same as the name of
line Item2 is the same as the name of
13166-W standard method or procedure. Change the long name to
the standard METHOD or
be unique.
PROCEDURE.
BINDFILE: Name "Item1" at line Item2 The long name of the entity is the same as the name of
13167-W was used twice in the rule hierarchy another one in the rule hierarchy. Change the long name to
for entities of different types. be unique.
The word (as a rule, a long or short name) is reserved in the
The word Item1 used as Item2 is
13168-W Rules Language. Change the word used as Item2 to be
reserved in the Rules Language.
unique.

Rules Preparation Messages 13169-W

Message
BINDFILE: The set Item1has no
13169-W The set has no elements. All set elements were ignored.
elements; it will be ignored.
BINDFILE: Item1 view of Item2 and A rule cannot have a work view and the same input or
13170-S
work view are the same. output view. Change the name of the work view.
BINDFILE: Item1 view is both work Item1 cannot be a work view and a global view. Remove
13171-S
view and global view. one of these views from the rule hierarchy.
BINDFILE: Value Item1 of set element
Value literal of set element is too large. Change the value of
13172-W Item2 is too large. Value will be
set element.
truncated.
BINDFILE: View item1 at line Item2
redefines another view. Its property The Occurs time of redefining views must be equal to zero.
13174-W
value of Occurs times will be Change the occurs time of view to zero.
ignored.
The VARCHAR field has to have a length field with the
BINDFILE: Length field Item1 of
name equal to "long name of varchar" + "_LEN". This string
VARCHAR field at line Item2 is
13175-S may be greater than 34, so it cannot be recognized.
missing. The name of the VARCHAR
Change the long name of VARCHAR and contact system
field is probably too long.
support.
BINDFILE: The size of one of the
redefining subviews of view Item1 is The size of a redefined subview is greater than the size of a
13176-W greater than the size of the primary based view, which could lead to runtime errors. Change the
view. This could cause errors at structure of based view or redefined view.
runtime.
BINDFILE: View Item1 redefines more
13177-W Change the structure of the based view.
than one view.
BINDFILE: File "Item1" have no input
13178-W Attach an input view to the file hierarchy.
view.
BINDFILE: Object for window not
13179-S Try to prepare it again.
found.
There are two or more objects in the panel file with the
PANELFILE: Object's HPSID "Item1" same system identifier (HPSID). There is an identifier with
13180-W
could not be used in the rule. the same long name as the object's system identifier.
Change the system identifier of the object.
BINDFILE: Invalid long name of The long name for this specified entity is invalid. If you get
13183-W
symbol "Item1" in set "Item2". this message, contact your System Administrator.
Expression after WHILE symbol is not valid. See DO
13200-S WHILE expression must be Boolean. statements in the Rules Language Reference Guide for
further clarification.
Occurrence of symbol Item2 in this context is not valid. See
Item2 "Item1" unexpected in this
13201-S declaration of corresponding statement in the Rules
context.
Language Reference Guide for further clarification.
Invalid exponentiation in (Item1) ** Item2 is expression of DECIMAL type. See Operators in the
13202-W
(Item2). Rules Language Reference Guide for further clarification.
The prefix of the method call is typed object reference, but
Objects class with CLSid Item1 not
13203-S objects class with CLSid Item1 is not defined in the
defined.
interface file.
The value of object scope that is indicated by object
Invalid value of the object scope. Set
13204-W declaration in DCL statement must be RULE,
RULE scope.
PROCESS, and APPLICATION.
In DCL statement identifier Item1 is declared as a
13205-W Local procedure Item1 is not defined.
procedure, but this procedure definition is missing.
13206-S Item1 was expected. Item1 is expected in this context.


Message
You may have skipped the statements list after procedure
header, after the ELSE symbol, or after the logical
13207-S Statements list was expected. expression in conditional statement. See the declaration of
the corresponding statement in the Rules Language
IF symbol should be followed by boolean expression. See
13208-S Condition was expected. IF Statements in the Rules Language Reference Guide for
CASE symbol and expression should be followed by
13209-S CASE list was expected. alternatives list. See CASEOF statements in the Rules
Character literal is not ended. Character literal must be
13210-S Apostrophe not closed.
ended with an apostrophe or quote character.
PERFORM symbol should be followed by procedure name
13211-S Procedure name was expected.
(identifier).
Identifier Item1 is not declared as an event for class Item2;
Item1 is not declared as an Event of
13212-S therefore, Item1 cannot be used as the declaration or
class Item2.
definition of the event handler after the FOR symbol.
EVENT symbol should be followed by one or more event
13213-S Event name list was expected. names. See Post Event statements in the Rules Language
EVENT symbol should be followed by one or more event
13214-S Item1 is not an EVENT name. names. See Post Event statements in the Rules Language
Rule Item1 should not be followed by packed parameters
RULE Item1 does not have an input list because rule Item1 is defined as rule without input view.
13215-S
view. See USE statements in the Rules Language Reference
Guide for further clarification.
If one operand of the compare operation is view, then
View cannot contain Item1 because it
13216-S another must be view as well. See Expressions in the Rules
is Item2.
13217-S Operand Item1 cannot be VIEW. For views, entities are only allowed to compare operations.
Logical operation has operand of invalid type. See
13218-S Operand Item1 must be BOOLEAN. conditions in the Rules Language Reference Guide for
If a rule or a component is used as a MAP source, then it
13219-S Item1 must have an output view. must have output view. Your rule or component Item1 is
defined as a rule without an output view.
Event handler Item1 (for event Item2) The parameters number of event handler Item1 is different
13220-S has invalid parameters number; it from parameters number of corresponding event Item2.
must be equal to Item3. Parameters number of event Item2 is equal to Item3.
Statement Item1 must not be used in Some statements, such as procedure declaration and
13221-S
procedure body. return, cannot be used in the procedure body.
EVENT POST should be followed by one or more event
names. Item1 is not TRIGGER name. See Post Event
13222-S Event Item1 is non-Trigger.
statements in the Rules Language Reference Guide for
13223-S Invalid type of Print operand. PRINT operand may be numeric or character expression.
You cannot map object reference Either both objects references have no type or they are
13224-S
Item1 to object reference Item2. pointers to objects of different classes.
The construct 'Item1 ()', where Item1 is an object identifier,
The object Item1 has no default
13225-S means the call of the method which is the default method
method.
for object Item1 is not defined.


Message
The type of Object Item1 is not The prefix of the method call, object reference Item1, has
13226-S
defined. no type.
If a rule contains an SQL ASIS statement then it must be
defined as a SQLCA view . See File Access statements in
13227-S View SQLCA is not defined.
clarification.
Platform Item1 of calling rule Item2 is
See USE statements in the Rules Language Reference
13228-S not compatible with platform Item3 of
receiving rule Item4.
Platform Item1 of calling rule Item2 is
13229-S not compatible with platform Item3 of
receiving component Item4.
The SQL ASIS statement is empty and contains no
embedded SQL commands. See File Access statements in
13231-W Empty SQL ASIS statement.
clarification.
The declaration of Item1 as an OBJECT is not found.
Check the following: There is an OLE control in the
repository that has the same name as the type of Item1,
There is a control with a system identifier (HPSID) of Item1
13232-S Item1 is not declared as an Object.
defined in your window, If there is a warning with number
13028 in your preparation results, there is a problem with
the OLE controls in your repository. If you get this message,
Error handler Item1 should not have This local procedure is defined as an error handler and
13233-S
parameters. cannot have parameters.
Item1 is not a valid System ID. Either you did not define
The character literal Item1 is not an
13234-S OBJECT with the System ID on your window, or there is an
object identification string.
error in compiling the object definition file.
If one operand of an operation is DBCS string then another
13235-S The operand Item1 must be DBCS. must have DBCS data type as well. See Expressions in the
Rules Language Reference Guide for further clarification.
If one operand of an operation is MIXED string then another
must have MIXED data type as well. See Expressions in
13236-S The operand "Item1" must be MIXED.
clarification.
13237-S Duplicated object Item1. The object with System ID Item1 is defined more than once.
The map source Item1 has the VOID
13238-S The map source must have a type other than VOID.
type.
The operation operand must have a different type than
13239-S The item Item1 has the VOID type.
VOID.
The method Item1 returns a value which has a different
The return value of method Item1 is
13240-S type than object reference, therefore it cannot be used in
not object reference.
this context.
The class Item1 of Item2 Item3 is not The object type must be defined in the window that belongs
13241-S
defined. to the rule or in the repository.
The object type must be defined in the window that belongs
13242-S The class Item1 is not defined.
to the rule, or it must be in the repository.
The class Item1 is defined more than
13243-S Class item1 is defined in two different subsystems.
once.
13244-S Unknown information after Item1.
indicated line.
13245-S Unexpected end of file. Unexpected end of file.


Message
This information is specified before an error message
13246-S Operand "Item1" has type "Item2".
associated with operations that have invalid operands.
Operation "Item1" has not been
See Expressions in the Rules Language Reference Guide
13247-S defined for operands of type "Item2"
for further clarification.
and "Item3".
Operation "Item1" has not been See Expressions in the Rules Language Reference Guide
13248-S
defined for operand of type "Item2". for further clarification.
See Data Types in the Rules Language Reference Guide
13249-S DEC field length cannot exceed Item1.
Invalid format in PICTURE clause: V See Data Types in the Rules Language Reference Guide
13250-S
must be preceded by an S. for further clarification.
Invalid format in PICTURE clause. See Data Types in the
13251-S 9 expected.
Empty statements list in procedure
13252-W Empty statements list in procedure Item1.
Item1.
Invalid report section encountered for See Converse statements in the Rules Language
13253-S
this CONVERSE REPORT statement. Reference Guide for further clarification.
Procedure Item1 must have the
13254-S You passed invalid type parameters to the procedure Item1.
following parameter(s): Item2.
The call of this method cannot be used
13255-S There is a problem with the OLE controls in your repository.
as a map destination.
You used as a map destination a property whose status is
The ReadOnly variable cannot be used
13256-S ReadOnly. There is a problem with the OLE controls in your
as a map destination.
repository.
The component Item1 should not be followed by a packed
parameters list, because component Item1 is defined as a
There is no input view for component
13257-S component without an input view. See USE statements in
Item1.
clarification.
The local procedure Item1 cannot be The event handler parameter types must be compatible
13258-S
event handler for event Item2. with parameter types of the corresponding event.
13259-S Item1 is not declared as a VIEW. Before BASED, the declared can be only a view name.
Pointer declarer may not be used in You may declare POINTER name only for the COBOL
13260-S
this environment. environment by use of the Report Writer.
Based declarer may not be used in You may declare BASED name only for the COBOL
13261-S
this environment. environment by use of the Report Writer.
See Numeric Values in the Rules Language Reference
13262-S Hexadecimal literal Item1 is not valid.
See Character Literals, Hexadecimal, and Octal Notation
Escape sequence is out of range for
13263-W (Character Value data type) in the Rules Language
representation.
13264-W Escape character Item1 is not valid. (Character Value data type) in the Rules Language
Escape character Item1 is not valid for
13265-S (Character Value data type) in the Rules Language
Cobol generation.
Item1 is an event handler and cannot The event handler is prohibited from being called in the
13266-S
be called in the rule. rule.
Generic CONVERSE REPORT is only See Converse statements in the Rules Language
13267-S supported in the MAINFRAME Reference Guide for further clarification on converse
environment. statement syntax in the mainframe environment.


Message
Item1 must be a character value. See Data Items in the
13268-S Expression Item1 is too complex.
You used a CONVERSE REPORT statement, but view
13269-S View RPTCA is not defined.
RPTCA is not defined.
Your rule contains a call of Item1, but the declaration
13270-S Procedure Item1 is not defined.
procedure of Item1 is missing.
Method Item1 is not defined for class Your rule contains a call of method Item1, but the
13271-S
Item2. declaration method Item1 is missing in class Item2.
See File Access statements in the Rules Language
13272-S Previous SQL block was not closed.
Either you specified an invalid declarer by formal parameter
The type of the formal parameter Item1
13273-S Item1 declaration or you specified a view declarer but did
of procedure Item2 is not declared.
not define parameter.
Identifier Item1 is not defined in the In the DCL statement of procedure Item2, the declaration of
13274-S
procedure Item2. identifier Item1 is not found.
13275-S Identifier Item1 is not defined. The declaration of identifier Item1 is not found.
The PROC RETURN statement has not found a parameter
13276-W Missing Item1 procedure return value.
that returns the procedure result.
The procedure Item1 declared to The PROC RETURN statement has a parameter but
13277-S
return void cannot return a value. procedure Item1 declared to return void.
The PROC RETURN statement parameter has an
"Item1" does not fit into the range-- expression that can assume a value larger than the data
13278-S
overflow will occur at runtime. item which must return the procedure. This will lead to
overflow at runtime.
The type of Item1 actually returned is The PROC RETURN statement parameter has a type that
13279-S incompatible with the declared type of is incompatible with the declared type of the procedures
the procedures return value. return value.
Identifier Item1 has one of following
Identifier Item1is defined as more than one entity, none of
13280-S types Item2 and cannot be used in this
which can be used in this context.
context.
Identifier Item1 has type Item2 and Identifier Item1 is defined as the name of an entity of type
13281-S
cannot be used in this context. Item2, and it cannot be used in this context.
This identifier is declared, but not as a view; therefore, it
Identifier Item1 is not defined as a
13282-S cannot be used after of-symbol. See View statements in the
view.
Data Item1 of Item2 type is In your case statement, one of the selectors is a constant of
13283-W inconsistent with that of CASEOF Item1 type, but CASEOF variable Item2 has type which is
variable Item3. inconsistent with Item1.
In your case statement, the selector Item1 is an integer
Data Item1 does not fit into the range
13284-W constant that is too long, and the CASEOF variable has
of Item2.
smallint or integer type.
No code will be generated for this All CASE clause items are incompatible with the CASEOF
13285-W
CASE clause. variable.
The field name item1 after CASEOF variable has the type
The field name item1 has the invalid Item2 which is invalid for CASEOF field names. See
13286-S
type Item2. CASEOF in the Rules Language Reference Guide for
The loop control variable must have See DO statements in the Rules Language Reference
13287-S
numeric type. Guide for further clarification.


Message
You must use conditional statements in the following form:
IF <condition>
ELSE <statement>
ENDIF
Item1 of IF statement contains no
13288-W or
statements.
IF <condition>
ENDIF
See IF statements in the Rules Language Reference Guide
Item1 declared in the DCL statement as a procedure but
13289-S The procedure Item1 has no definition. not defined in its body; therefore, you cannot use the call of
Item1.
Item1 is the main rule and cannot be
13290-S Use of main rule is prohibited.
used in this context.
Construction Item1 cannot be used as See DO statements in the Rules Language Reference
13291-S
loop index. Guide for further clarification.
The host variable has not been defined. See File Access
13292-S Invalid host variable Item1. statements in the Rules Language Reference Guide for
further clarification regarding the SQL ASIS statement.
Error in RETURN PROC statement.
Error in RETURN PROC statement. Character data cannot
13293-S Character data cannot be used in the
be used in the statement.
statement.
A PROC RETURN statement parameter is an expression
Item1 assumes a longer value than
that may assume a value larger than the data item which
13294-W returned with this procedure.
must return the procedure. This may lead to truncation at
Truncation may occur.
runtime.
A PROC RETURN statement parameter is an expression
"Item1" does not fit into the range-- that may assume a value larger than the data item which
13295-W
overflow may occur at runtime. must return the procedure. This may lead to truncation at
runtime.
The value Item1 may be negative while
The value Item1 may be negative while the procedure
13296-W the procedure returns an unsigned
returns an unsigned picture.
picture.
PROC RETURN statement is not PROC RETURN statement is not allowed out of the
13297S
allowed out of the procedures scope. procedures scope.
13298-W DCL statement is empty. There are no declarations within the DCL statement.
View Item1 cannot be mapped to view The views types are incompatible and cannot be mapped
13301-S
Item2. from one to the other.
Aggregate Item1 cannot be mapped to In the MAP statement, when you have an aggregate as
13302-S
the view Item2 because it is multiply. source, the destination must be a non-array view.
Aggregate Item1 cannot be mapped to
13303-S An aggregate can be mapped only to a view.
the field Item2.
Empty aggregate cannot be mapped to In the MAP statement, you cannot have an empty
13304-S
Item1. aggregate as a source.
Item1 cannot be mapped to Item2. The The result of LOC function is char(8) and must be mapped
13314-S
result of this function is CHAR (8). to char(8).
"Item1" assumes a longer value than Item1 assumes a longer value than Item2. Item1 may be
13315-W
"Item2". Truncation may occur. truncated.
In a constant expression that is a part of an arithmetic
Integer part of intermediate result
13316-W formula with variables and integer, part of the expressions
contains more than 31 digits.
result contains more than 31 digits.
Integer part of result contains more The result of a constant expression should fit into the range
13317-S
than 31 digits. of the destination.


Message
View Item1 cannot be mapped to field
13318-S View Item1 cannot be mapped to field data item Item2.
data item Item2.
Aggregate cannot be mapped to the
In your MAP statement with an aggregate as a source, the
13321-S view Item1, since aggregate contains
aggregate contains more fields than the target view.
more fields than target view.
The return value of method Item1 is
13322-W The return value of the method call is not used.
not used.
13323-S Invalid exponentiation in Item1. The power of the exponentiation is not integer.
Item1 Item2 cannot be mapped to
13350-S Item1 Item2 cannot be mapped to Item3 Item4.
Item3 Item4.
Parameter of PRINT must be variable The parameter of PRINT must be a variable or a constant
13450-S
or constant. expression.
13460-W Condition at line Item1 is always true. Condition Item1 is always true
13461-W Condition at line Item1 is always false. Condition Item1 is always false
Value of Item1 parameter must not be
In method of object ARRAY, the index must not be less than
13462-S less than one (1) because it is an index
one (1).
of ARRAY.
Literal "Item1" is longer than "Item2". As the length of one operand of a condition is less than that
13463-S
They will never coincide. of another, the condition will always be true or false.
As the length of one operand of a condition may be less
The literal "Item1" can be longer than
13464-W than that of another, the condition may always be true or
"Item2".
false.
The interface file contains the definition of class Item1 more
13501-S The class Item1 is duplicated.
than once.
The interface file contains the definition of standard
13503-S The procedure Item1 is duplicated.
procedure Item1 more than once.
The method Item1 of class Item2 is The interface file contains the definition of method Item1
13504-S
duplicated. more than once.
The property Item1 of class Item2 is The interface file contains the definition of property Item1
13505-S
duplicated. more than once.
DEC must be followed by length and
In this context, the decimal type must be fully specifiedit
13506-W scale. Set default length value to Item1
must specify length and scale.
and default scale value to Item2.
Item1 must be followed by length. In this context, the CHAR (VARCHAR, DBCS, MIXED) type
13507-W
Length is set to Item2. must be fully specifiedit must specify length.
The interface file contains the definition of property which
13514-W The property cannot have void type.
has a void type. This definition is ignored.
PIC must be followed by pattern. Set
In this context, the picture type must be fully specifiedit
13515-W length value item1 and scale value
must have a pattern.
Item2.
Unexpected symbol Item1. Expected
13516-S In this context, symbol Item1 cannot be used.
Item2.
Property definitions can use modificators RO/RW and
The modificator Item1 is invalid in this BYREF/BYVALUE. Method's parameter definitions can use
13517-W
context; it is ignored. modificator BYREF/BYVALUE. Only case modificators can
be used.
13518-S CLSID must be ended with quote. The interface file is erroneous.
The interface file contains the default method definition for
13519-W Duplicated default method.
the same class more than once.
13520-S Unexpected Item1. In this context, symbol Item1 cannot be used.


Message
13521-W Item1 cannot be class name. Using the reserved word Item1 as a class name is invalid.
This information is specified before an error message
13601-I Operand "Item1" is aggregate.
associated with operations that have invalid operands.
Local procedure Item1 call or method Item1call is used in a
13602-W The value of Item1 is not used.
non-expression, but Item1 is defined as returning a value.
See Data Types in the Rules Language Reference Guide
13603-S Invalid format in PICTURE clause.
The standard function Item1 call or variable Item1 is used in
13604-S The value of Item1 must be used.
a non-expression.
See Statements in the Rules Language Reference Guide
13605-S Type declarer was waited.
The value Item1 of type Item2 may not Some data types are incompatible, and data cannot be
13606-S
be mapped to item Item3 of type Item4. mapped from one to another.
In your MAP statement, one of the data items may assume
The value Item1 may not be mapped to
13607-S a value larger than the other data item. This may lead to
item Item2: overflow will occur.
truncation or overflow at run time.
The method Item1 is not defined in the
13608-S The method Item1 is not defined in the class Item2.
class Item2.
The overlay source cannot be the aggregate. The overlay
The construction Item1 cannot be
13609-S destination can be only those constructions that can be
Item2 in an Overlay statement.
mapped to the destination.
In this context, lexema Item1 is expected. See syntax rules
13610-W Expected Item1.
in the Rules Language Reference Guide.
For class (or object) Item1 more than one error handler is
13611-S Duplicated error handler for Item1.
defined.
13612-S Duplicated default error handler. There is more than one default error handler is defined.
The procedure Item1 is declared to return a value, but its
13613-W Procedure Item1: no return value.
body does not contain a PROC RETURN statement.
Construct Item1 may not be Item2
13614-S Construct Item1 may not be Item2 statement operand.
statement operand.
Procedure Item1 with Item2 An invalid number of actual parameters for local procedure
13615-S
parameters not defined. Item1 is specified.
Method Item1 with Item2 parameters An invalid number of actual parameters for method Item1 is
13616-S
not defined in class Item3. specified.
The constructions HIGH_VALUES, LOW_VALUES and
Construction Item1 is not allowed as a
13617-S aggregate cannot be the actual parameter of the standard
parameter of standard function Item2.
function.
Type of Item2 actual parameter
incompatible with type of An invalid type of actual parameter of local procedure call is
13618-S
corresponding formal parameter of specified.
procedure Item1.
Parameter number Item3 in the
method Item1 of class Item2 has The actual parameter of method call's type is incompatible
13619-S
incorrect type. It must have type with the specified type of corresponding formal parameter.
Item4.
Item1 cannot be a source in Overlay
Item1 cannot be a source in Overlay statement. Only view
13620-S statement. Only view or character field
or character field can be used as a source.
can be used as a source.
Item2 is an explanation of reason why Item1 cannot be
Item1 cannot be used in LIKE clause
13621-S used in LIKE clause. See Statements in the Rules
because it is Item2.


Message
Construction Item1 cannot be used as destination. See
Construction Item1 cannot be used as
13622-S Assignment Statements in the Rules Language Reference
destination.
In the formal parameters list, Item1 is declared as a view. In
Invalid redefinition of the formal
13623-S the DCL statement, it must be defined as a view that
parameter Item1.
contains fields only.
Construction Item1 cannot be used in See Statements in the Rules Language Reference Guide
13624-S
the event handler body. for further clarification.
Different result types of event handler The event handler result type must be compatible with the
13625-S
Item1 and event method Item2. result type of the corresponding event.
This message appears when the user tries to use an
Unable to distinguish between HPSIDs
13626-S identifier that is case insensitive and equal to more than
Item1 and Item2.
one object system identifier (HPSID).
The system identifier (HPSID) cannot be used in the rule as
An alias was defined for HPSID Item1.
13627-S an identifier since an alias is declared for that system
Use this alias instead of the HPSID.
identifier (HPSID).
HPSID "Item1" was used for two There is more than one object with the same system
13628-S different objects. An alias for such an identifier (HPSID), so you cannot use that system identifier
HPSID cannot be declared. (HPSID) in the rule or declare an alias for it.
The value of Item1 is incorrect for The view occurrence value exceeds 2147483647, which is
13629-S
OCCURS clause. the size limit, or the value equals zero.
Two entities with equal names exist. This message is
The local procedure with identifier generated when: The procedure and the view have
13630-W
Item1 redefines Item2. coinciding names, The number of procedure parameters is
equal dimension of view (field), The procedure return value.
generated when: Both procedures have coinciding names,
The local procedure with identifier
13631-S The number of their parameters is equal, The
Item1 redefines another procedure.
corresponding parameters of procedures have coerced
types.
The map source Item1 has type Item2. This error message is generated when the map destination
13632-S Only values of the type Item4 may be is the method or the property of some class and it has
mapped to Item3. incompatible type.
The handler Item1 redefines the This error message is generated when Item1 and Item2 are
13633-S
handler Item2. the names of the handlers.
The identifier Item1 was declared as
13634-S The identifier Item1 cannot be used as the operand.
item2 and cannot be the operand.
The object identifier cannot be An object identifier can be declared in the rule only. See
13635-S declared in the local procedure Statements in the Rules Language Reference Guide for
declarative statement. further clarification.
Incorrect parameter number Item1 in A very complicated expression is being passed as an actual
13636-S
the method Item2 of class Item3. parameter.
Qualifying redefining views against their parent view is a
The OF clause Item 1 of Item2 is deprecated feature which will not port to the mainframe.
13637-W invalid because view Item3 redefines This is likely to be an error in a future release. See the
view Item4. Rules Language Reference Guide, Redefining Views, for
illustrations of the correct syntax.
Default error handler Item1 is not The default error handler is declared in the declarative
13638-W
defined. section, but its body is not defined.
Error handler Item1 on item2 Item3 is The error handler is declared in the declarative section, but
13639-W
not defined. its body is not defined.
Event handler Item1 for Item2 Item3 The event handler is declared in the declarative section, but
13640-W
Item4 is not defined. its body is not defined.


Message
Item1 is declared neither as an object, Item1 is expected to be an object, an object reference, or a
13641-S
an object reference, nor a view. view.
Construction item1 cannot be used as
You cannot use the constructions of the kind Item1 to
13642-S an object name. An identifier was
denote an object.
expected.
Item1 cannot be mapped to Item2. Item1 must be mapped
Construction Item1 is very complexed
13643-S to some variable, and then the variable must be mapped to
to be mapped to Item2.
Item2.
An object of subsystem Item1 cannot
13644-S be locally declared using a DCL
statement.
Host variable item1 must not have See Statements in the Rules Language Reference Guide
13645-S
subscripts. for further clarification.
Item1 cannot be a source in a MAP or Use cannot use Item1 as a source in MAP or OVERLAY
13646-S
OVERLAY statement. statements.
Item1 cannot be an operand of INSET Value Item1 has a type which is incompatible with the type
13647-S
operation because set has type Item2. of the set.
The declaration and the definition of
The declaration of the procedure must correspond with its
13648-S the local procedure Item1 defines
definition.
different types for the return value.
Local procedure cannot return value A local procedure cannot be defined to return a value of the
13649-S
of type Item1. type Item1.
Procedure Item1 is defined as error
The same local procedure cannot be used as both an event
13650-S and as event handler. This is not
and an error handler.
allowed.
Statement Item1 is not allowed within Statements of the type Item1 are not allowed in the bodies
13651-S
handler procedure. of event handlers.
When identifiers without declared local parameters are
The declaration of local procedure
13652-W used in a rule, the identifier is recognized as a local
Item1 added.
procedure identifier.
13653-S Error reading input stream. Error reading input stream.
Procedure definition cannot be used
Procedure definition cannot be used in the IF statement,
13654-S in the IF statement, DO statement or
DO statement or CASE statement.
CASE statement.
Duplicate use of CASE constant
13655-W Duplicate use of CASE constant.
"Item1".
The construction Item1 cannot be
used in the current context because a The construction cannot be used in the current context
13656-S valid entry of identifier Item2 which because a valid entry of identifier which gets the value of a
gets the value of Item3 type does not type that does not exist.
exist.
The operands of the operation Item1 The operands of the operation Item1 have incompatible
13657-W
have incompatible types. types.
There is a possible problem with the rule's execution
Control is passed from Item1
13658-W environment. See USE statements in the Rules Language
environment to Item2 rule Item3.
Control is passed from Item1 There is a possible problem with the component's
13659-W environment to Item2 component execution environment. See USE statements in the Rules
Item3. Language Reference Guide for further clarification.
The rule has the wrong execution environment. See USE
Rule Item1 is targeted for the Item2-
13660-S statements in the Rules Language Reference Guide for
environment.


Message
The component has the wrong execution environment. See
Component Item1 is targeted for the
13661-S USE statements in the Rules Language Reference Guide
Item2-environment.
Item Item1 cannot be a destination in
overlay statement. Only view or See OVERLAY statements in the Rules Language
13662-S
character field could be used as a Reference Guide for further clarification.
destination.
That is a deprecated feature which will See File Access statements in the Rules Language
13663-W
not port to the mainframe. Reference Guide for further clarification.
The formal parameter Item1 declared The appointment field is not accessible because the formal
13664-W as a view which contains field with the parameter declared as a view which contains field with the
same name. same name.
13665-W Index of view cannot be empty. Index of view cannot be empty.
The procedure parameter cannot be
13666-S The procedure parameter cannot be omitted.
omitted.
Parameter number Item3 in the The actual parameter of method call's cannot be omitted
13667-S method Item1 of class Item2 cannot be because the corresponding formal parameter is not
omitted. optional.
13668-S Item1 is not listener. The event handler is defined with an invalid listener.
The map source Item1 has type Item2 This warning is generated when the source and destination
13669-W and cannot be mapped to item Item3 of MAP statement have incompatible types. This could
of the type Item4. cause errors at runtime.
The class Item1 cannot be loaded. The
13670-W This message can appear when class is not accessible.
nontyped object reference created.
You can call the static method when you will use the class
13671-S Item1 is not class alias.
alias only.
You cannot call the nonstatic method when you use class
13672-S The method Item1 is not static.
alias.
Item1 is not a keyword that can be The keyword can not be disabled. See the Rules Language
13673-W
disabled. Reference Guide for further clarification.
The keyword is already disabled. See the Rules Language
13674-W Keyword Item1 is already disabled.
The keyword is not disabled. See the Rules Language
13675-W Keyword Item1 is not disabled.
Construct Item1 is very complex to be The construction HIGH_VALUES and LOW_VALUES
13676-S
operand of operation Item2. cannot be operands.
There is no identifier Item1 declaration
See MAP statements in the Rules Language Reference
13677-S that could be assigned to the Item2 of
type Item3.
This is invalid that both operands of
See Conditions in the Rules Language Reference Guide for
13678-S Item1 operation are HIGH_VALUES or/
and LOW_VALUES.
The rule object cannot be created
The rule object cannot be created because the rule and the
13679-W because the rule and the window have
window have the same name.
the same name.
The identifier Item1 is not event
13680-S The identifier is not event handler identifier.
handler identifier.
The event handler Item1 defines no
13681-S The event handler defines no listener.
listener.
The identification of event handler At least two events with the same name exist. For such
13682-S
Item1 is impossible. events defined event handlers with the same name Item1.


Message
The identifier Item1 is not defined as The identifier Item1 is not defined as event handler for
13683-S
event handler for object Item2. object Item2.
Item1 and Item2 define handlers for
13684-S Item1 and Item2 define handlers for the same event.
the same event.
13685-S The object type declaration is invalid. The object type declaration is invalid.
Only object reference can be used as
13686-S Only object reference can be used as formal parameter.
formal parameter.
You cannot use any statement outside You cannot use any statement outside local procedure
13687-S
local procedure body. body.
The expression Item1 is very complex. The expression Item1 is very complex. Only variable can be
13688-S
Only variable can be used here. used here.
The event Item1 has not method to
13689-S The event Item1 has not method to register listener.
register listener.
The event Item1 has no method to
13690-W The event Item1 has no method to unregister listener.
unregister listener.
The procedure Item1 defined as event
The procedure Item1 defined as event handler for event
13691-W handler for event Item2 and object
Item2 and object Item3 twice.
Item3 twice.
The procedures Item1 and Item2
defined as event handlers for the The procedures Item1 and Item2 defined as event handlers
13692-W
same event Item3 and for the same for the same event Item3 and for the same object Item4.
object Item4.
The local variable Item1 redefines a generated when the procedure and the view have
13693-W
local procedure. coinciding names, the number of procedure parameters is
equal dimension of view (field), the procedure return value.
The class with class identifier Item1
13694-S The class with class identifier Item1 does not exist.
does not exist.
You cannot assign an aggregate to You cannot assign an aggregate to Item1 because it is
13695-S
Item1 because it is nontyped view. nontyped view.
An aggregate cannot be actual
parameter of procedure Item1 because An aggregate cannot be actual parameter of procedure
13696-S
formal parameter Item2 is nontyped Item1 because formal parameter Item2 is nontyped view.
view.
You cannot use Item1 as operand
You cannot use Item1 as operand NEW clause because it
13697-S NEW clause because it defines
defines abstract class or interface.
abstract class or interface.
Property Item1 cannot be used in a You can solve this problem by renaming the case sensitive
rule because several properties with property name using appropriate pragma. See PRAGMA
13698-S
the same case insensitive name are clause in the Rules Language Reference Guide for further
defined in the class Item2. clarification.
Property Item1 is not defined in the
13699-S Property Item1 is not defined in the class Item2.
class Item2.
The name Item1 used as property alias
The name Item1 used as property alias redefines some
13700-W redefines some property of class
property of class Item2 or an alias.
Item2 or an alias.
Pragma Item1 can be used while Java is generated only.
13701-S Pragma Item1 cannot be used. See PRAGMA clause in the Rules Language Reference
See PRAGMA clause in the Rules Language Reference
13702-S Invalid pragma.


Message
Invalid keyword in pragma. Only Item1 See PRAGMA clause in the Rules Language Reference
13703-S
allowed here. Guide for further clarification.
Event handler cannot be defined for
13704-S Event handler cannot be defined for non-typed pointer.
non-typed pointer.
"Item1" is not declared as an Event of Item1 is not declared as an Event of class Item2 with
13705-S
class Item2 with listener Item3. listener Item3.
It is Item2. The entity of type Item3 has There are several entities that have the same name and
13706-S
been chosen. can be MAP/CLEAR/OVERLAY destination.
13707-W Class name Item1 is not unique. The several classes with name Item1 are defined.
The corresponding cursor fields are
13708-W The corresponding cursor fields are different.
different.
More than one cursor declared in SQL ASIS clause. See
More than one cursor declared in SQL File Access statements in the Rules Language Reference
13709-S
ASIS clause. Guide for further clarification regarding the SQL ASIS
statement.
13710-S Cursor Item1 declared repeatedly. Cursor Item1 declared repeatedly.
Object Item1 redefines Item2 and Object with name Item1 created for rule to access to
13711-W
cannot be used in the rule. methods of class "com.level8.hps.HpsRule".
Occurrence view Item1 cannot be local Occurrence view Item1 cannot be local procedure formal
13712-S
procedure formal parameter. parameter.
13713-S Item1 is not final static property. Item1 is not final static property.
Item1 value(s) will not be compared Item1 value(s) will not be compared with other case
13714-W
with other case selectors. selectors.
Item1 is non-typed object pointer and Item1 is non-typed object pointer and cannot be used in this
13715-S
cannot be used in this context. context.
The identifier cannot start with
13716-S The identifier cannot start with underscore symbol.
underscore symbol.
The cursor Item1 has no fields. Empty The cursor Item1 has no fields. Empty cursor is not
13717-S
cursor is not allowed. allowed.
The parameter Item1 has unsuitable See the Rules Language Reference Guide for further
13718-S
type. clarification.
The parameters Item2 and Item3
See the Rules Language Reference Guide for further
13719-S of standard function Item1 are
clarification.
non-compatibles.
The identifier Item1 is neither a view nor an object;
Identifier Item1 is not defined neither
13723-S therefore, the dot symbol cannot follow it. See the Rules
as a view nor as an object.
Only LOOKUP or ERROR set can be Only a LOOKUP or an ERROR set can be the first
13726-S
first parameter of this function. parameter of this function.
Function Item1 with such parameters
The function Item1 with such parameters is not supported
13727-S is not supported for this target
for this target platform.
platform.
13728-S Variable Item1 has nonpositive index. The variable Item1 has a non-positive index.
17354-S The destination is not valid. The destination is not valid.
Invalid operands in expression with See Date and Time functions in the Rules Language
18600-S
DATE type. Reference Guide for further clarification.
Invalid operands in expression with See Date and Time functions in the Rules Language
18601-S
TIME type. Reference Guide for further clarification.
Result of expression with DATE type See Date and Time functions in the Rules Language
18602-W
operands will be numeric. Reference Guide for further clarification.


Message
Result of expression with TIME type See Date and Time functions in the Rules Language
18603-W
operands will be numeric. Reference Guide for further clarification.
Error in MAP statement. Only DATE See Date and Time functions in the Rules Language
18604-S
can be used in the statement. Reference Guide for further clarification.
Error in MAP statement. Only TIME See Date and Time functions in the Rules Language
18605-S
can be used in the statement. Reference Guide for further clarification.
Error in MAP statement. Invalid See Date and Time functions in the Rules Language
18609-S
datatype used along with TIMESTAMP. Reference Guide for further clarification.
Illegal datatype in a conditional See Date and Time functions in the Rules Language
18612-S
expression with DATE. Reference Guide for further clarification.
Illegal datatype in a conditional See Date and Time functions in the Rules Language
18613-S
expression with TIME. Reference Guide for further clarification.
Only TIMESTAMP can be used in a
See Date and Time functions in the Rules Language
18614-S conditional expression with
TIMESTAMP.
This version of Rules Language does Your version of the system environment does not support
18620-S
not support Item1. the listed item.
See CASEOF statements in the Rules Language
20356-W CASE block contains no statements.
DOWHILE block contains no See DO statements in the Rules Language Reference
20357-W
statements. Guide for further clarification.
DOFROMTOBYINDEX block See DO statements in the Rules Language Reference
20361-W
contains no statements. Guide for further clarification.
The entire RULE block contains no See Statements in the Rules Language Reference Guide
20367-W
statements. for further clarification.
Data Item1 of Item2 type is
21062-S inconsistent with type of CASEOF
variable Item3.
21355-S Duplicate use of CASE constant Item1.
CASEOF is not followed by a variable See CASEOF statements in the Rules Language
21519-S
name. Reference Guide for further clarification.
A DO statement with neither of FROM,
See DO statements in the Rules Language Reference
22162-S TO, BY, or INDEX requires a WHILE
clause.
Wrong RULE environment for the USE RULEINIT
Item1 may not be initialized because
23937-S statement. See USE statements in the Rules Language
of incompatible environments.
Rule Item1 requires a package name
30141-S since it is used in a USE RULE
statement with no INSTANCE clause.
DETACH option may be used only if
30145-S both calling and called rules are PC
rules.
This rule has the wrong execution environment. See USE
Rule Item1 is targeted for the Item2
30864-S statements in the Rules Language Reference Guide for
environment.
USE COMPONENT/MODULE is not See USE statements in the Rules Language Reference
30892-S
followed by a component ID. Guide for further clarification.
30893-S USE RULE is not followed by a rule ID.


Message
Recursive rule calling is not See USE statements in the Rules Language Reference
30894-S
supported. Guide for further clarification.
INSTANCE option may be used only if See USE statements in the Rules Language Reference
31145-S
the PC rule calls LDPFUN rule. Guide for further clarification.
You cannot have a CONVERSE WINDOW statement in a
"Item1" is not supported in the rule whose execution environment is CICS. If you want to
32557-S COBOL environment unless the rule is make the rule a 3270 Converse rule, change the execution
T3270. environment to PCCICS. Refer to the MVS Environment
Guide for further information.
See CONVERSE statements in the Rules Language
32895-S PRINTER name expected.
The subheader level is unusual: It
evaluates to Item1, but it should be > See CONVERSE statements in the Rules Language
32997-W
or = zero and less than Item2 (number Reference Guide for further clarification.
of regular sections for this report).
The expression Item1 must have one of the following
34581-S Item1 must be numeric.
numeric types: integer, smallint, decimal, or picture.
50204-S "Item1" must not have subscripts.
50241-S This subscript contains a syntax error.
Invalid Format in PICTURE clause: See Data Types in the Rules Language Reference Guide
50928-S
Only one S allowed. for further clarification.
Invalid Format in PICTURE clause: See Data Types in the Rules Language Reference Guide
50929-S
Only one V allowed. for further clarification.
DEC must be followed by a DEC See Statements in the Rules Language Reference Guide
50966-S
clause! for further clarification.
50968-S Name expected after LIKE.
50972-S CONTAINS list expected.
50973-S CONTAINS expected.
This item in a declaration has already been defined
50974-S Item1 may not be redefined.
elsewhere.
See Numeric Data Types in the Rules Language Reference
50976-S DEC field length must be at least 1!
50978-S DEC field scale must not be negative!
50979-S DEC field scale cannot exceed length!
Declared size of Item1 is invalid for a
CHAR.
Declared size of Item1 is invalid for a
VARCHAR.
Before you can use a data item (variable or constant) in the
50982-S Item1 is not defined. Rules Language code, it must either be part of the rules
hierarchy or declared locally using the DCL statement.
See Numeric D statements in the Rules Language
50985-S Length or scale values are invalid.


Message
50986-S Picture expected.
Unknown error during macro See Macros in the Rules Language Reference Guide for
52800-S
processing. further clarification.
Internal error during macro See Macros in the Rules Language Reference Guide for
52801-S
processing: Item1. further clarification.
A comma used to separate any two operands in a macro
A comma must immediately follow
statement must immediately follow the first operand with no
52802-W operand "Item1" with no intervening
intervening spaces. See Macros in the Rules Language
spaces.
Quoted string must be finished with right quote characters.
Closing quote was not found for the
52810-S See Macros in the Rules Language Reference Guide for
string started at line Item1.
Unexpected end of file found by the macro preprocessor in
the argument list. It is possible that the list is not closed.
52811-S End of File in argument list.
See Macros in the Rules Language Reference Guide for
Exceeded recursive limit of Item1; use See Macros in the Rules Language Reference Guide for
52812-S
-L<N> to change it. further clarification.
Missing right parenthesis in See Arithmetic Macros in the Rules Language Reference
52813-S
evaluation: Item1. Guide for further clarification.
Invalid expression in evaluation: See Arithmetic Macros in the Rules Language Reference
52814-S
Item1. Guide for further clarification.
52815-W Invalid input in evaluation: Item1.
52816-W Excess input in evaluation: Item1.
Dividing by zero is forbidden. See Arithmetic Macros in the
52817-S Divide by zero in evaluation: Item1.
See Arithmetic Macros in the Rules Language Reference
52818-S Module by zero in evaluation: Item1.
Macro expansion exceeds maximum See Macros in the Rules Language Reference Guide for
52819-S
allowed recursion level. further clarification.
Too few arguments in macro function See Macros in the Rules Language Reference Guide for
52821-W
Item1. further clarification.
Excess arguments in macro function See Macros in the Rules Language Reference Guide for
52822-W
Item1 ignored. further clarification.
Non-numeric argument in macro See Macros in the Rules Language Reference Guide for
52823-S
function Item1. further clarification.
52824-W Undefined name Item1.
52825-W Undefined macro Item1.
The radix must be from 2 to 36 See Arithmetic Macros in the Rules Language Reference
52826-S
inclusive. Guide for further clarification.
52827-W Negative width for evaluation.
52828-W Non-numeric argument to Item1.
52830-W Debug mode--bad debug flags: Item1.

Rules Preparation Messages 52831-W

Message
\\0 will disappear; use \\& as a See Macros in the Rules Language Reference Guide for
52831-W
replacement. further clarification.
Invalid regular expression: Item1 : See Macros in the Rules Language Reference Guide for
52840-W
Item2. further clarification.
Error matching regular expression See Macros in the Rules Language Reference Guide for
52841-W
\Item1\. further clarification.
52850-S Undiverting stream.
Unclosed argument list in macro See Macros in the Rules Language Reference Guide for
52860-S
function Item1. further clarification.
52861-W Unexpected end of file. Unexpected end of file found by the macro preprocessor.
Macro definition is ignored because See Macros in the Rules Language Reference Guide for
52870-S
no macro name is specified. further clarification.
Make sure that this file exists and you have permission to
52900-W Cannot open Item1 with errno=Item2.
open it.
Cannot set error file Item1 with
52901-W Cannot set error file Item1 with errno=Item2.
errno=Item2.
Error copying inserted file with
52902-S Error copying inserted file with errno=Item1.
errno=Item1.
Error reading inserted file with
52903-S Error reading inserted file with errno=Item1.
errno=Item1.
52910-S Unable to open input file Item1. Unable to open input file Item1.
52911-S Unable to open listing file Item1. Unable to open listing file Item1.
52912-S Unable to open output file Item1. Unable to open output file Item1.
52913-S Unable to open bind file Item1. Unable to open bind file Item1.
Error writing to output stream on the See Macros in the Rules Language Reference Guide for
52914-S
macro expansion step. further clarification.
52915-S Error writing to file "Item1". Error writing to file.
Error reading from input stream on the See Macros in the Rules Language Reference Guide for
52916-S
macro expansion step. further clarification.
The macro name must be specified in the first parameter of
Macro definition is ignored because
52920-S function CG_DEFINE. See Macros in the Rules Language
no macro name is specified.
The macro name must be specified in the first parameter of
Macro undefinition is ignored because
52921-S function CG_UNDEFINE. See Macros in the Rules
no macro name is specified.
Macro expansion string is not
52922-S specified. Macro definition for "Item1"
is ignored.
The first symbol in a macro name may be any letter or the
The first symbol in macro name
52923-S underscore (_) character. See Macros in the Rules
"Item1" is invalid.
The macro name may be any sequence of letters, digits
The macro name "Item1" contains and the underscore (_) character, where the first character
52924-S
invalid symbols. is not a digit. Blanks are not permitted. See Macros in the
Macro name "Item1" cannot be See Macros in the Rules Language Reference Guide for
52926-S
defined recursively. further clarification.


Message
Quote strings should never start with a letter or underscore
Quote string "Item1" starts with a
52927-S (_) character. See Macros in the Rules Language
letter or underscore.
Quote string "Item1" contains invalid See Macros in the Rules Language Reference Guide for
52928-S
symbols. further clarification.
The name of a macro must be specified in functions
CG_DEFINE, CG_UNDEFINE, and so on. See Macros in
52929-S Macro name must be specified.
clarification.
The radix must be from 2 to 36 inclusive. See Arithmetic
52940-S The radix is less 2. Macros in the Rules Language Reference Guide for further
clarification.
The radix must be from 2 to 36 inclusive. See Arithmetic
52941-S The radix is greater 36. Macros in the Rules Language Reference Guide for further
clarification.
The symbol Item1 is prohibited for See Arithmetic Macros in the Rules Language Reference
52942-S
numbers with radix Item2. Guide for further clarification.
52950-S Unexpected statement "Item1".
CG_IF, CG_IFDEFINED and CG_IFNOTDEFINED
Statement "Item1" is not closed with statements must be closed with CG_ENDIF. See Macros in
52951-S
"CG_ENDIF". the Rules Language Reference Guide for further
clarification.
CG_IF, CG_IFDEFINED and CG_IFNOTDEFINED
CG_IF... statement is not closed with statements must be closed with CG_ENDIF. See Macros in
52952-S
"CG_ENDIF". the Rules Language Reference Guide for further
clarification.
Unexpected statement "Item1" after See the chapter on Macros in the Rules Language
52953-S
"Item2". Reference Guide for further clarification.
Macro was defined as "Item2". Macro
preprocessor uses case-sensitive See the chapter on Macros in the Rules Language
52954-W
comparison if the translation flag Reference Guide for further clarification.
MEXCI is not set.
Value "Item1" is not listed in the
52960-S Check the 'MacroDomains' section of the INI file.
domain for macro "Item2".
Macro "Item1" must be defined
52961-S because it is specified in the Check the 'MacroDomains' section of the INI file.
'MacroDomains' section.
Macro "Item1" cannot be undefined
52962-S because it is specified in the Check the 'MacroDomains' section of the INI file.
'MacroDomains' section.
Flag MMBDEF was specified that means all macros must
52965-S Macro "Item1" is not defined.
be defined before using.
The rule translation is finished by The rule translation is stopped by user request. See Macros
52990-W CG_CGEXIT statement with return in the Rules Language Reference Guide for further
code Item1 clarification.
60051-S FROM expression must be numeric.
60052-S TO expression must be numeric.
60053-S BY expression must be numeric.
Guide for further clarification..


Message
Variable "Item1" must have Item2 See View data type in the Rules Language Reference
60211-S
subscript(s). Guide for further clarification.
The subscript "Item1" exceeds its See View data type in the Rules Language Reference
60220-S
legal maximum value "Item2." Guide for further clarification about subscripts.
See View data type in the Rules Language Reference
60221-S The subscript "Item1" is less than 1.
Guide for further clarification about subscripts.
Before you can use a data item (variable or constant) in
Rules Language code, it must either be part of the rules
60322-S "Item1" is not declared as a variable. hierarchy or declared locally using the DCL statement. See
Variable Data Items in the Rules Language Reference
A reference to a set symbol is incorrect. When more than
one entity with the same name exists, you must properly
Ambiguous reference to set symbol qualify the entity by referring to its ancestors. Your
60327-S
"Item1." qualification is either incomplete or is referring to the wrong
ancestors. See Variable Data Items in the Rules Language
When more than one entity with the same name exists, you
must properly qualify the entity by referring to its ancestors.
Variable "Item1" contains an invalid
60398-S Your qualification is either incomplete or is referring to the
parent-child qualification.
wrong ancestors. See Variable Data Items in the Rules
When more than one entity with the same name exists, you
must properly qualify the entity by referring to its ancestors.
Ambiguous reference to entity named
60399-S Your qualification is either incomplete or is referring to the
"Item1".
wrong ancestors. See Variable Data Items in the Rules
The input view (or part thereof) Item1 The rule should modify its own input view. See the
60420-W
should not be modified. Developing Applications Guide for further clarification.
Make sure that you have spelled everything correctly, that
you are referencing the entitys name, and that set or set
"Item1" is not declared as a set or
61323-S symbol exists in your hierarchy. See Symbol data type in
symbol.
clarification.
Make sure that a set name follows the INSET operation,
61551-S "INSET" is not followed by a set name.
and that it is spelled correctly.
See Character Value data type in the Rules Language
62375-S Character literal "Item1" is too long.
See Numeric data type in the Rules Language Reference
62376-S Integer literal "Item1" is too long.
See Numeric data type in the Rules Language Reference
62378-S Decimal literal "Item1" is too long.
To use this data item in this statement and in this manner,
Data item "Item1" must be of type
63045-S the item must be of type CHAR. See Data Items in the
character.
The keyword WINDOW is not followed
63895-S by a window ID with the correct
Reference Guide for further clarification..
syntax.
The keyword REPORT is not followed See CONVERSE statements in the Rules Language
63896-S
by a report ID with the correct syntax. Reference Guide for further clarification..
The keyword SECTION is not followed See CONVERSE statements i then Rules Language
63897-S
by a section ID with the correct syntax. Reference Guide for further clarification.


Message
Division by zero in expression. Divisor
A number divided by zero is undefined. Check for proper
64156-S begins in line Item1 and ends in line
syntax.
Item2 position Item3.
Item2 is an expression of DECIMAL type. See Operators in
Invalid exponentiation in (Item1) **
64158-S the Rules Language Reference Guide for further
(Item2).
clarification.
"Item1" does not fit into the range of
You are attempting to map a source expression into an
64329-S "Item2." Overflow will occur at
incompatible target.
runtime.
64330-W "Item2." The source may be negative
while the target may not be.
64359-W "Item2." Overflow may occur at
runtime.
See File Access statements in the Rules Language
80021-S This rule contains SQL statements. Reference Guide for further clarification regarding the SQL
ASIS statement.
The word Item1 is reserved for HPS
85801-W The word Item1 is reserved for Rules Language.
Rules Language.
85933-S Please contact product support. Contact product support.
Subsequent portions of this rule are Break the statement into several statements and prepare
86959-S
not scanned for errors. the rule again.
There is an invalid character (for example, a nonprintable
98516-S Invalid character in position Item1. character) in the rule source code. Check your code and
prepare the rule again.
In this particular statement, the listed operand must be
99046-S The operand "Item1" must be numeric.
numeric.
You should not use Item1 in this See the Rules Language Reference Guide for further
99940-S
version of Rules Language. clarification.
View Item1 exceeds the size of 32K. This may cause
99950-W The view item1 exceeds 32K.
possible errors on some platforms.
The total size of variables locally declared in the rule
99951-W The LOCAL VARS exceeds 32K. exceeds 32K. This may cause may possible errors on some
platforms.
The view being returned by Item1 The procedure returns a view which is incompatible with the
99960-S
cannot be assigned to Item2. view it should be mapped to.
The actual parameter Item1 of Item2 is The user passes the view as an actual parameter of
99961-S
incompatible with formal parameter. incompatible type.
An aggregate has a structure which is incompatible with the
Trying to compare an aggregate with view it has to be compared with. For example, the
99962-S
an incompatible view. aggregate cannot be mapped to the view of the same
structure it is compared with.
The view actually returned is The view being used in PROC RETURN statement is
99963-S incompatible with the declared type of incompatible with the declared formal result of the
the procedures return value. procedure.
Output view Item1 of the rule being Output view of the rule being called is incompatible with the
99964-S
called cannot be mapped to Item2. destination view of the map statement.
The identifier with short name equal to
99980-S The panel file object is linked with not defined variable.
"Item1" not found
The object with HPSID equal to
99981-S Panel file is corrupt or you could not use object of this type.
"Item1" was not defined


Message
Set with implementation name equal
99982-S to "Item1" not found in the rule Window uses set that is not defined.
hierarchy.

CHAPTER
2 EXECUTION MESSAGES
Error messages that appear during application run-time are described in the sections that follow:
Rules Execution Messages
Application Execution Messages
Rules Execution Messages

Rules Execution Messages may occur when running an application that was created with Rules Language
rules. Some error codes are returned by the HPSError function in AppBuilder. The corresponding text
strings are returned by the HPSErrorMessage function. Refer to the Rules Language Reference Guide
for more information on Rules Language and related issues.
Table 2-1 lists the rules execution messages in the order of the message identifier.
Table 2-1 Rules Execution Messages
Message Identifier Message Text

Internal error in runtime(1)
1
This error should never occur. If it does, contact Customer Support.
2 Using wrong object type as array
3 Not enough memory to create array
4 Method not implemented to access array
5 Used parameter type is not supported for this method
6 Index either less than 0, or greater than upper bound of array
7 Wrong parameter number for this method
8
9 Not enough memory to allocate array element
10 This element type is not supported
11 Access to an un-allocated element
12
13 Too many nested procedure calls
14 Could not allocate enough memory
15 Not enough memory to allocate array element
16
17 Object method returned wrong value
18 Error in generated PCC file

Application Execution Messages 19
Table 2-1 Rules Execution Messages (Continued)

19 Division by zero
20 Numeric overflow
21 Operand of numeric operation is incorrect
22 Source of map statement is incorrect
23 Source doesnt fit into the range of destination
Application Execution Messages

You may also encounter Application Execution Messages when running an application.
The three-letter prefix determines whether it is a component (Cmp) or rules (Rul) message.
Each of the Application Messages begins with a letter: s, w, i, or e after the number. The letter indicates
the severity of the message:
s indicates a severe error that prevents execution of a rule. You must fix a severe error before
continuing.
w indicates a warning and flags a potential problem, but does not prevent execution. You may
proceed with caution.
i indicates an informational message about execution. It does not affect execution in any way.
e indicates an error.
The messages in Table 2-2 list application execution messages alphabetically and numerically by message
identifier.
Table 2-2 Application Execution Messages
Message ID Message Text Message Description

Input field WINDOW_LONG_NAME of The window on which the specified component should
Cmp101w system component ComponentName is execute has not been specified. This field is mandatory
required. in order for the component to execute.
The GUI help file which should be used has not been
Input field HELP_FILE_NAME of system
Cmp102w specified. This field is mandatory in order for the
component ComponentName is required.
component to execute.
Input field HPS_BITMAP_NAME of The bitmap file which should be used has not been
Cmp103w system component ComponentName is specified. This field is mandatory in order for the
required. component to execute.
Input field WINDOW_LONG_NAME of The window on which the specified component should
The GUI help file which should be used has not been
Cmp102w specified. This field is mandatory in order for the
Input field HPS_BITMAP_NAME of The bitmap file which should be used has not been
Cmp103w system component ComponentName is specified. This field is mandatory in order for the
required. component to execute.
The GUI help keyword which should be used has not
Input field HELP_KEYWORD of system
Cmp104w been specified. This field is mandatory in order for the
2-2 Execution Messages

Cmp105w Application Execution Messages
Table 2-2 Application Execution Messages (Continued)

The system ID (HPSID) of the object on which the
Input field HPS_ITEM_ID of system specified component should execute has not been
Cmp105w
component ComponentName is required. specified. This field is mandatory in order for the
Input field MESSAGE_SET_NAME of The set which should be used has not been specified.
Cmp106w system component ComponentName is This field is mandatory in order for the component to
required. execute.
The text on the push button on which the specified
Input field PUSH_TEXT of system
Cmp107w component should execute has not been specified. This
field is mandatory in order for the component to execute.
The name of the event which should be posted has not
Input field EVENT_NAME of system
Cmp108w been specified. This field is mandatory in order for the
The rule calling the component must be in a sub-process
System component ComponentName in order for this component to be used. There must be a
Cmp111w
failed. A parent rule does not exist. root process in this rule hierarchy from which Use Rule
Detach is executed.
The view on which the specified component should
Input field VIEW_LONG_NAME of
Cmp112w execute has not been specified. This field is mandatory
system ComponentName is required.
in order for the component to execute.
Input field FIELD_LONG_NAME of The field on which the specified component should
The destination (rule name) to which events should be
Input field EVENT_DEST of system
Cmp114w posted has not been specified. This field is mandatory in
order for the component to execute.
The system ID (HPSID) of the object or the multicolumn
list box column is incorrect. Compare the IDs being used
Input field HPS_ITEM_ID or
in the component to the IDs defined in Window Painter.
HPS_LISTBOX_CELL_ID of system
Also, if changes have been made to the IDs in Window
Cmp201w component ComponentName contains
Painter, then the window must be prepared again. Verify
invalid value. HPS_ITEM_ID: HPS ID
that the component is being used on an object that it
HPS_LISTBOX_CELL_ID: Cell ID
supports (for example, HPS_SET_SELECTED_FIELDS
applies only to list boxes and multicolumn list boxes).
The field or view specified is incorrect. Compare the field
and view names being used in the component to those
defined in Window Painter. Also, if changes have been
made to the names in Window Painter, then the window
must be prepared again.
Input field FIELD_LONG_NAME or
Verify that the component is being used on an object
VIEW_LONG_NAME of system
that it supports (for example, SET_FIELD_MESSAGE
applies only to edit fields and combo boxes).
invalid value. FIELD_LONG_NAME:
If the component uses the input field FIELD_MODE,
Field VIEW_LONG_NAME: View
verify that the FIELD_MODE is being set to a value that
is valid for the object. A multicolumn list box column can
be either visible/enabled (FIELD_MODE=2) or visible/
disabled (FIELD_MODE=1) but not invisible
(FIELD_MODE=0).
Input field NUMBER_OF_RECORDS of
system component ComponentName
Cmp203w Number of records must be greater than or equal to 0.
contains invalid value Number of
Records.
The field occurrence specified is not valid. This field can
Input field FIELD_OCCUR of system
contain the value -1 (first selected), 0 (next selected), or
a possible occurrence number. It can not contain a value
invalid value FieldOccurrence.
less than -1.
Input field VIEW_LONG_NAME of
The view specified either does not exist or is not an
Cmp205w system component ComponentName
occurring view.
contains invalid value View.

Application Execution Messages Cmp206w

Input field MENU_NAME or An invalid menu or pulldown name has been entered.
PULLDOWN_NAME of system Either the name does not exist or the names have not
Cmp206w component ComponentName contains been entered correctly for the component. See the
invalid value. MENU_NAME: Menu System Components manual for details on correct
PULLDOWN_NAME: Pulldown usage.
Input field PUSH_TEXT of system
The push button text which is specified does not match
the text of a push button on the window.
invalid value Push Text.
The system ID (HPSID) of the multicolumn list box
column is incorrect. Compare the ID being used in the
component to the ID defined in Window Painter. Also, if
changes have been made to the ID in Window Painter,
then the window must be prepared again.
Verify that the component is being used on an object
Input field HPS_LISTBOX_CELL_ID of that it supports (for example,
Cmp208w system component ComponentName HPS_SET_SELECTED_FIELDS applies only to list
contains invalid value Cell ID. boxes and multicolumn list boxes).
Also, if the component uses the input field
FIELD_MODE, verify that the FIELD_MODE is being set
to a value that is valid for the object. A multicolumn list
box column can be either visible/enabled
(FIELD_MODE=2) or visible/disabled
(FIELD_MODE=1), but not invisible(FIELD_MODE=0).
The system ID (HPSID) of the object is incorrect.
Compare the ID being used in the component to the ID
defined in Window Painter. Also, if changes have been
Input field HPS_ITEM_ID of system made to the ID in Window Painter, then the window must
Cmp209w component ComponentName contains be prepared again.
invalid value HPS ID. Verify that the component is being used on an object
that it supports (for example,
SET_MENU_MODE_BY_ID applies only to menu
items).
Input field POPTYPE of system
The poptype must be 1 (absolute), 2 (relative to
window), or 3 (relative to client area).
invalid value Poptype.
Input field NUMBER_OF_SECONDS of
The seconds specified must be between 0 and 65525,
inclusive.
contains invalid value Seconds.
Input field HPS_ACTIVE_STATE of
Cmp212w system component ComponentName The active state must either be 0 (inactive) or 1 (active).
contains invalid value State.
Input field HPS_WINDOW_STATE of
The window state must be 0 (minimized), 1 (maximized),
or 2 (normal).
contains invalid value State.
Input field FIELD_MODE of system
The field mode must be 0 (invisible), 1 (visible/disabled),
or 2 (visible/enabled).
invalid value Mode.
Input field PUSH_MODE of system
The push mode must be 0 (invisible), 1 (visible/
disabled), or 2 (visible/enabled).
invalid value Mode.
Input field ATTR_COLOR of system
Cmp216w component ComponentName contains The color must be between 0 and 9, inclusive.
invalid value Color.
Input field PUSH_ATTR of system The attribute must be 0 (background), 1 (text), 2
Cmp217w component ComponentName contains (border), 10 (reset background), 11 (reset text), or 12
invalid value Attr. (reset border).
Input field FIELD_ATTR of system The attribute must be 0 (background), 1 (text), 2
Cmp218w component ComponentName contains (border), 10 (reset background), 11 (reset text), or 12
invalid value Attr. (reset border).

Cmp219w Application Execution Messages

Input field HPS_MITEM_ATTRIBUTE of
The menu attribute must either be 0 (enable) or 1
(check).
contains invalid value Attr.
Input field HPS_MITEM_STATE of
Cmp220w system component ComponentName The menu state must either be 0 (off) or 1 (on).
contains invalid value Menu State.
For value sets, the text code must match a value
Input field TEXT_CODE of system
attached to the set in the hierarchy. For error sets, the
text code must match the encoding value of an item for
invalid value Text Code.
which default text has been created.
The name of the set is not valid. Verify that the set which
is created in Development Workbench has prepared
Input field MESSAGE_SET_NAME of
successfully. A set with this name and the extension
.REF (for value sets) or .SET (for error sets) should exist
contains invalid file name Set.
in the path specified by REF_DIR in the AE Runtime
section of the hps.ini file.
Input field TITLE_LENGTH of system
The title length specified must be between 0 and 50,
inclusive.
invalid value Length.
The name of the help file is not valid. Verify that
GUI_HELP_DIR is set in the AE Runtime section of the
hps.ini file and that the help file exists in the path
specified by the GUI_HELP_DIR. Also verify that the file
invalid file name File Name.
is a valid help file for the environment in which it is being
accessed.
Input field LISTBOX_OCCUR of system
The list box occurrence must be greater than or equal to
0.
invalid value List Box Occurrence.
Input field EVENT_VIEW of system View does not exist. The view specified does not exist in
Cmp226w component ComponentName contains the hierarchy. Verify that the view exists in the hierarchy
invalid value View. as a work view under the parent rule and the child rule.
Input field EVENT_VIEW of system Local views are not allowed. The view specified is a
Cmp227w component ComponentName contains local view. Local views can not be used for posting
invalid value View. events.
Either the event destination or the event qualifier
contains an invalid value. Verify that EVENT_DEST
contains the rule name that should receive the event and
that the rule is indeed a child rule. (The rule is executed
with Use Rule Detach.)
Input field EVENT_DEST or
Check the rule name in the component with the rule
EVENT_QUALIFIER of system
name defined in the hierarchy. If the rule name has
component ComponentName contains
Cmp228w changed ensure that the rule and its calling rule have
invalid value.
been prepared again.
EVENT_DEST: Destination
If an event is being posted to an instance rule, the
EVENT_QUALIFIER: Qualifier
EVENT_QUALIFIER must contain the name of the
instance. The instance name is the name following Use
Rule Detach instance InstanceName. If an event is
being posted to a child rule, the EVENT_QUALIFIER
should be not be populated.
Input field BACK_BUFFER of system
Cmp229w component ComponentName contains The back buffer must be greater than or equal to 0.
invalid value Buffer.
Input field VIRTUAL_SIZE of system
Cmp230w component ComponentName contains The virtual size must be greater than or equal to 0.
invalid value Virtual Size.
Component Manager error: Cannot An error with the component has occurred. There is a
Cmp233w locate view View for system component problem either with the component in the repository or
ComponentName. with the installed version of AppBuilder.

Application Execution Messages Cmp234w

An error with the component has occurred. There is a
Component Manager error: View qualifier
Cmp234w problem either with the component in the repository or
Qualifier is not valid.
with the installed version of AppBuilder.
Input field Color of system component
The color specified must be between 0 and 255,
Cmp235w ComponentName contains invalid value
inclusive.
Color Value.
The name of the bitmap file is not valid. Verify that
BITMAP_DIR is set in the AE Runtime section of the
Input field HPS_BITMAP_NAME of hps.ini file and that the bitmap file exists in the path
Cmp236w system component ComponentName specified by the BITMAP_DIR. Also verify that the
contains invalid value File Name. bitmap is a valid bitmap for the environment from which
it is being accessed. If possible, a system bitmap editor
can be used to verify this.
Rul101i Loading database, please wait. Status message. A database is currently being loaded.
NetEssential initialization failed. Error = See AppBuilder communications documentation, such
Rul102e
Return Code Error Information. as the Configuring Communications Guide.
Database initialization failed. Error = See AppBuilder communications documentation, such
Rul103e
Return Code Error Information. as the Configuring Communications Guide.
Rule failed. NetEssential Error Message See AppBuilder communications documentation, such
Rul104e
= Error Information. as the Configuring Communications Guide.
Database initialization failed for See AppBuilder communications documentation, such
Rul105e
DatabaseName. as the Configuring Communications Guide.
There is a problem with the RuleView DLL. Check to
Rul106s RuleView cannot be executed. ensure that this DLL resides in the path where
AppBuilder is installed.
Select Yes to use RuleView, the runtime debugger, to
step through the application and debug problems. If you
select No, RuleView can still be started at any time by
Rul107q Do you wish to start RuleView? pressing Alt+Pause. To prevent this dialog from being
displayed, set HPSRT_DEBUG_START in the AE
Runtime section of the hps.ini file to FALSE. If you do
so, pressing Alt+Pause during execution has no effect.
See AppBuilder communications documentation, such
Rul108e Error closing NetEssential.
as the Configuring Communications Guide.
There is a mismatch in the size of the rules view.
Attempt to prepare the rule again. If the view is a view
View ViewName size mismatch: Size and
Rul109e from the default repository, there is a problem either with
Size.
the view in the repository or with the installed version of
AppBuilder.
A RuleView debugging session has already been
started, either by setting HPSRT_DEBUG_START to
TRUE, setting HPSRT_DEBUG_START to QUERY, and
Rul110i RuleView is already executing!
responding Yes to the resulting dialog, or by a previous
selection of the Alt+Pause key combination. The
currently active RuleView session should be used.
The ID of the rule does not match the ID embedded in
Rul111e Rule system ID mismatch: ID and ID. the rule DLL. It is possible that the rule did not
successfully prepare. Attempt to prepare the rule again.
Either the process is being aborted or there is an option
to abort or continue the process. The rule may not have
Cannot load rule RuleName. Aborting
successfully prepared. Attempt to prepare the rule
process.
again. If the rule prepares successfully, then verify that
Rul112e Cannot load rule RuleName. Abort this
the value in the hps.ini file is being set. Also verify that
process?
the rule exists in the path specified by the
(The specified rule cannot be loaded.)
RULE_DLL_DIR or RULE_DLL_DIR_SRV setting in the
AE Runtime section of the hps.ini file.

Rul113e Application Execution Messages

The specified component cannot be loaded and the
process is being aborted. The user component may not
have successfully prepared. Attempt to prepare the
Cannot load user component
Rul113e component again. If the component prepares
ComponentName. Aborting process.
successfully, verify that the component exists in the path
specified by the UCOMP_DIR setting in the AE Runtime
The system component has not been implemented in
System component ComponentName not
Rul114e the installed version of AppBuilder and cannot be
implemented.
executed.
Rul115e Error closing database.
The component that the currently executing rule is trying
to execute has an unrecognized environment. Check the
Unrecognized type Type for component
Rul116e Execution Environment setting in the Properties dialog
ComponentName.
for the component from the Hierarchy window of the
Construction Workbench.
The rule that the currently executing rule is trying to
execute has an unrecognized environment. It is possible
Unknown type Type for rule RuleName. to abort the process or to continue executing. Check the
Rul117e
Abort this process? Execution Environment setting in the Properties dialog
for the rule from the Hierarchy window of the
Construction Workbench.
The window specified cannot be loaded. It is possible to
abort the process or to continue to execute. The window
may not successfully have prepared. Attempt to prepare
Cannot load window WindowName. Abort
Rul118e the window again. Verify that a window with the name
this process?
specified in the error dialog exists in the path specified in
the PANEL_DIR setting in the AE Runtime section of the
hps.ini file.
The specified view cannot be found in the rule. It is
View ViewName cannot be found in rule possible that changes have been made in the hierarchy
Rul119e
RuleName. and some of the rules have not been prepared again.
Prepare the rule and the calling rule.
Root rule RuleName is requesting an Attempt to prepare the rule again and verify that the rule
Rul120e
input view. Aborting process. prepares successfully.
Rule RuleName is defined with no output There may be a problem with the installed version of
Rul121s
view. Aborting process. AppBuilder.
There is a mismatch between the size of the rules input
view and the size of the input view the calling rule
Input view mismatch in rule RuleName.
expects the rule to have. It is possible changes have
Rul122e Expected: Length. Actual: Length. You
been made in the hierarchy and some of the rules have
may need to reprepare rules.
not been prepared again. Prepare all rules which contain
this view and all calling rules.
Rule RuleName is defined with no input There may be a problem with the installed version of
Rul123s
view. Aborting process. AppBuilder.
There is a mismatch between the size of the rules
output view and the size of the output view the calling
Output view mismatch in rule RuleName.
rule expects the rule to have. Changes may have been
Rul124e Expected: Length. Actual: Length. You
made in the hierarchy and some of the rules have not
may need to reprepare rules.
been prepared again. Prepare all rules which contain
this view and all calling rules.
Error getting NetEssential Status View
Rul125e information. Error = Return Code Error
Information.
Rule RuleName called unsupported The macro specified is not supported in the version of
Rul126e
macro MacroName. AppBuilder that is executing.

Application Execution Messages Rul128e

Rule RuleName: view ViewName length
There is a mismatch in the size of the rules view.
Rul128e mismatch. Codegen= Length; Resource=
Attempt to prepare the rule again.
Length.
An attempt has been made to detach more
Only Number levels of subprocesses are
Rul129w subprocesses than are allowed. From a root rule only
supported.
number levels of subprocesses can be detached.
Could not find view ViewName in rule The specified view cannot be found in the rule. Attempt
Rul131e
RuleName at index Index. to prepare the rule.
Could not extract view ViewName from The specified view cannot be found in the rule. Attempt
Rul132e
rule RuleName at ordinal Ordinal. to prepare the rule again.
View ViewName cannot be located for The view to which an event is being posted cannot be
Rul133e the event posting view. The data will be located. Verify that the view name is a work view of both
discarded. the parent and child rule.
The file specified in the LANGUAGE setting in the AE
Runtime section of the hps.ini file cannot be loaded.
Rul134s Failed to load language file FileName.
Check to be sure this DLL resides in the path where
AppBuilder is installed.
The codepage of the language DLL (the language DLL
is specified in the LANGUAGE setting in the AE Runtime
section of the hps.ini file) must be the same as the
Codepage conflict: codepage set in the NLS section of the hps.ini file. Verify
Rul135e HPS.INI: CodePage that the NLS setting is the same as the number given in
Language file: CodePage. the LANGUAGE setting (that is, a setting of
Codepage_OS2=437 in the NLS section would match
with a language setting of ENU437 or ENG437 but not
with ENU1004).
Cannot load DLLname.dll. Return code: The specified DLL cannot be loaded. Refer to the error
Rul136s
(Return Code) Error Information. information for more details as to the cause of the error.
Cannot find function FunctionName in
The DLL specified is in error. Refer to the error
Rul137s DLLnamethat is.dll. Return code: (Return
information for more details as to the cause of the error.
Code) Error Information.
The specified rule cannot be loaded. If the path given is
incorrect, correct the RULE_DLL_DIR and
RULE_DLL_DIR_SRV settings in the AE Runtime
section of the hps.ini file. If the path given does not
indicate a drive letter or the drive letter is incorrect, verify
Rule cannot be loaded from Path.
Rul138e that the value in the hps.ini file is being set correctly. If
Rule cannot be loaded from Path or Path.
the rule DLL specified in the path does not exist, it needs
to be successfully prepared in Preparation Workbench. If
the rule DLL specified in the path does exist, there may
be a problem with the RULE_COMP_OPTS setting
specified in AP section of the hps.ini file.
There may be a problem with the installed version of
Rul139s Could not get address for Rule.
AppBuilder.
The rule cannot be loaded. See the return code given
and verify that the rule is successfully prepared. It is
possible that the rule did not successfully prepare.
Rule RuleName cannot be loaded. Attempt to prepare the rule again. If the rule prepares
Rul140e
Return code = Return Code. successfully verify that the hps.ini file is being set. Also
verify that the rule exists in the path specified by the
RULE_DLL_DIR or RULE_DLL_DIR_SRV setting in the
AE Runtime section of hps.ini file.
There is a conflict between the codepage of the rule and
Codepage conflict: the codepage specified in the NLS section of the hps.ini
Rul141e Rule = CodePage; file. The codepage on the machine where the rule is
HPS.INI = CodePage. prepared must match the codepage set in the NLS

Rul142e Application Execution Messages

Registering event failed.\nError = Return See AppBuilder communications documentation, such
Rul142e
Code. as the Configuring Communications Guide.
Deregistering event failed.\nError = See AppBuilder communications documentation, such
Rul143e
Return Code. as the Configuring Communications Guide.
Posting the event failed.\nError = Return See AppBuilder communications documentation, such
Rul144e
Code. as the Configuring Communications Guide.
Cannot receive the event.\nError = See AppBuilder communications documentation, such
Rul145e
Return Code. as the Configuring Communications Guide.
Rul146e Unknown NetEssential error ErrorType.
An attempt is being made to shut down a process while
detached processes are displaying error messages.
Rul147e Please clear all error messages.
First dismiss all other error messages. Then clear this
error message and the process shuts down.

Application Execution Messages An attempt is being made to shut down a process while de-

CHAPTER
3 COMMUNICATIONS MESSAGES
Error messages related to internal communications are termed General Communications Messages. The
following topics describe the messages and descriptions for general and Java-related messages.
General Communications Messages
Java Communications Messages
For an explanation of error numbers from third-party software, refer to the resources listed in
Interpreting Third-party Error Numbers.
For a sample trace file, see Chapter 8, Trace File Example.
Table 3-1 lists the types of messages from AppBuilder communications.

Table 3-1 Communications Message Types
Message Description
EXTERNAL Results from a problem with a third-party product. Contact your System Administrator.
Results from a problem that is internal to the product. Contact your System
INTERNAL Administrator to obtain the latest fix software.
USER Results from a problem at your site or the system implementation.
INFO There is no error but the message contains information of interest.
General Communications Messages

Table 3-2 lists general AppBuilder communications messages. They are listed numerically by message
identifier.
Note For Java applications, see Java Communications Messages.
Table 3-2 General Communications Messages

INFO 1. No Error.
The application has invoked the AppBuilder communications
function that will ultimately give control to the specified service. The
INFO 2. Entered Routine %s. message appears only if the debug level is 2. The System
Administrator sets the debug level in the DNA.INI file, TRACING
section, DEBUGLVL variable.

General Communications Messages INFO 3.
Table 3-2 General Communications Messages (Continued)

The specified service has given control back to AppBuilder
communications after a Remote Procedure Call. The message
INFO 3. Exiting Routine %s. appears only if the debug level is 2. The System Administrator sets
the debug level in the DNA.INI file, TRACING section, DEBUGLVL
variable.
The client application tried to do a data-communications task
without including the address of a valid client context. Review the
use of the third parameter in the function dna_InitClient and ensure
USER 4. No Client Context Found.
that the client application is making proper use of the address,
which needs to be included in subsequent calls. For dna_InitClient
usage, refer to the Application Programming Interface.
The system failed to allocate memory for the named data structure.
EXTERNAL 5. Error Allocating %s.
Contact the System Administrator.
The second parameter in the client application function
No Service was Specified dna_ServiceRequest or dna_BoundServiceRequest did not point to
USER 6.
in the Service Request. a valid string. For service request usage, refer to Application
Programming Interface.
The system is unable to access the DLL specific to a protocol. The
message suggests that the protocol string is invalid; the protocol-
configuration file (dnaproto.conf in the UNIX environments,
dnaproto.cfg in Windows) is missing or incorrect; or the referenced
Error Getting Protocol DLL is missing or corrupted. First, determine whether the protocol
USER 7. Information for Service = string is valid. If the string is invalid, correct the string in the source
%s, Protocol = %s. of routing information. Otherwise, check the DNA.INI file, DNA
section, PROTOCOLS variable to ensure that the system is trying
to access the correct protocol-configuration file, and check your
system configuration to ensure that the system has access to the
protocol-specific DLL.
Error Reading [%s], %s The specified variable is not found in the DNA.INI file. Add the
USER 8. from the NetEssential variable in the DNA.INI file. The messages first variable identifies
initialization file. the relevant section of that file.
Error Opening File %s for The specified file is missing or corrupted. The platform-specific
USER 9. Mode = %s, system error system error usually explains the problem. If necessary, contact the
= %d. System Administrator.
Error Allocating Protocol The system failed to allocate memory required by a protocol.
EXTERNAL 10.
Space for Protocol = %s. Contact the System Administrator.
An application tried to access a service that is either Absent from
the route table or Present only in data-dependent entries, where
the input is such that none of those entries is invoked. You can
code the application to invoke a local program whenever that error
occurs. If the error occurs unexpectedly, perform these checks: If
No Routing Information the DNA.INI file, ROUTING section, NAME_SERVICE variable
USER 11.
Found for Service %s. equals ROUTE_TABLE or SERVICE_MANAGER, ensure that the
route table or Service Manager, respectively, has routing
information for the service named in the message. If the variable
equals DNAINI, ensure that such information is in the DNA.INI file,
ROUTING section, DEFAULT_HOST_NAME,
DEFAULT_PROTOCOL, and so forth variables.
The named protocol could not be referenced because either the
system configuration does not point to the library, in which case you
Error Loading Protocol =
USER 12. or the System Administrator should change the configuration, or
%s.
the library is corrupted, or the system cannot allocate space in
memory. For the last two cases, contact the System Administrator.
The named library could not be referenced because: The system
configuration does not point to the library, in which case you or the
USER 13. Error Loading Library %s. System Administrator should change the configuration. The library
is corrupted. The system cannot allocate space in memory. For the
last two cases, contact the System Administrator.
3-2 Communications Messages

USER 14. General Communications Messages

Error Resolving Entry Point The specified library is not compiled properly or the specified
USER 14.
%s for Library %s function is not exported. Recompile the library.
Internal AppBuilder communications error. The named protocol did
not correctly handle the tasks associated with a commit or abort.
Error Closing Protocol =
INTERNAL 15. For further details, check the protocol-specific messages that
%s.
precede this message in the error log, and contact Customer
Support.
Error Invoking Protocol Internal AppBuilder communications error. For further details,
INTERNAL 16. Function = %d in Protocol = check the protocol-specific messages that precede this message in
%s. the error log, and contact Customer Support.
Internal AppBuilder communications error. For further details,
INTERNAL 17. Error On Start Transaction. check the protocol-specific messages that precede this message in
the error log, and contact Customer Support.
Error On Commit
INTERNAL 18. check the protocol-specific messages that precede this message in
Transaction.
Error On Abort
Transaction.
The second parameter in the client application function
dna_GetError is NULL. Allocate a variable and pass its address.
USER 20. Null Error Code Received.
For dna_GetError usage, refer to Application Programming
Interface .
Error Initializing the
Protocol = %s.
Error Getting Service Internal AppBuilder communications error. For further details,
INTERNAL 22. Information for Service = check the protocol-specific messages that precede this message in
%s Over Protocol %s. the error log, and contact Customer Support.
Error Invoking Start Service
Event.
Error on Service Request
for Service %s.
The values of the DNA.INI file, ROUTING section,
Error Negative DNA Retry DNA_NO_OF_RETRIES and DNA_RETRY_INTERVAL variables
USER 25.
Number/Interval Value. were not greater than or equal to 0. If the data is correct, ensure
that the path to DNAINI is set in the execution environment.
Error Local Commit after
RPC failed.
Error Local Abort after RPC
failed.
The value of the DNA.INI file, DNA section,
Invalid Logical Unit of Work LOG_UNIT_OF_WORK variable is not 52LOCAL, LOCAL, or
USER 28.
Value = %s. REMOTE. If the data is correct, ensure that the path to DNAINI is
set in the execution environment.
Error Loading The system configuration is not pointing to the library; or the DLL is
USER 29.
Authentication Library. missing, corrupted, or improperly prepared.
Error Loading Authorization The system configuration is not pointing to the library; or the DLL is
USER 30.
Library. missing, corrupted, or improperly prepared.
Error Loading RPC End The system configuration is not pointing to the library; or the DLL is
USER 31.
Exit Library. missing, corrupted, or improperly prepared.

General Communications Messages USER 32.

Error Getting User Login The System Administrator-defined authentication exit failed.
USER 32.
Name. Review the DLL source to determine why.
Error Received from User The System Administrator-defined authorization exit failed. Review
USER 33.
Authorization Exit. the DLL source to determine why.
Error Received from User The System Administrator-defined RPC end-exit failed. Review the
USER 34.
RPC End Exit. DLL source to determine why.
Error NULL CallRuleId for
USER 35. No longer in use.
Status View.
Error Loading Encryption The encryption library is corrupted. Reprepare that library as per
USER 36.
Library. documented instructions.
Error Received from User The System Administrator-defined encryption exit failed. Review
USER 37.
Encryption Exit. the DLL source to determine why.
Internal AppBuilder communications error. An error occurred at
Error %s, Event = %s,
event registration or deregistration. For further details, refer to the
INTERNAL 38. Type = %s, Subsystem =
messages that precede this message in the error log, and contact
%s with Service Agent.
Customer Support.
Internal AppBuilder communications error. For further details, refer
Error Posting Event to
INTERNAL 39. to the messages that precede this message in the error log, and
Service Agent.
contact Customer Support.
Error Getting Dispatch
Library Name for Event = Check the <SUBSYSTEM_NAME> variable in the DNA.INI file.
USER 40.
%s and Subsystem = Note that the value is case-sensitive.
%s.
The system may have failed to free memory allocated for the login
Error Received from
structure. The problem occurred during the second call to the
USER 41. Authentication Cleanup
authentication exit, at execution of the function dna_CloseClient.
Function.
Error Invoking End Rule
Event.
No routing information is found for the specified service. The
Service Manager Returned Service Manager may lack the routing information, or did not pass it
USER 43. NO Binding for Service = to a service agent, or the passed information is corrupted. Check
%s. the information in the service controller, and retransfer the routing
information to the local service agent.
Error Making Service Call
%s Over Protocol %s.
Error Passing NULL login The second parameter in a dna_SetLoginInfo call is NULL, but
USER 45. struct to must point to an allocated structure of type dna_LoginStruct.
dna_SetLoginInfo(). Change the code.
The gateway has an authentication exit. The security data elicited
by that exit is in all cases ignored, and data elicited by the clients
Gateway Uses Login Info
authentication exit, if any, is used instead. The user should prevent
USER 46. from Clients Authentication
the gateways direct use of an authentication exit by leaving the
Exit.
DNA.INI file, DNA_EXITS section, DNA_AUTHENT_EXIT variable
empty.
Data_Info_t alignment
failure.
An Encina server encountered a function that it cannot resolve
routed locally to %s when
USER 48. locally. Check that the service is in the routing table. For Encina
it is not available locally.
server usage, refer to Supporting DCE and Encina.


An Encina client stub DLL failed. The service is not offered by the
USER 49. service %s not found. requested server. For Encina server usage, refer to Supporting
DCE and Encina.
Too many servers are involved in the transaction. Restructure the
maximum handle count
USER 50. application to invoke fewer services per transaction by breaking up
exceeded.
the logical units of work into smaller ones.
The Encina client is unable to bind to the server specified in the
Encina mond handle fetch route table. Verify that the server is running. For further details,
USER 51.
fails with %d: %s. check the error code in the Encina mon_status.h file. For Encina
The Encina server is down or disabled. For further details, check
Encina PA handle fetch
EXTERNAL 52. the error code in Encinas mon_status.h file. If necessary, contact
fails with %d: %s.
DCE RPC binding cleanup Encina client failure. The code is from DCE. contact Customer
EXTERNAL 53.
fails with %d. Support.
An Encina client is unable to set its security level. Ensure that the
DCE RPC binding auth
EXTERNAL 54. UNIX environment variable ENCINA_PRINCIPAL is set correctly. If
fails with %d.
necessary, contact the System Administrator.
Encina server initialization failure. Check the error code in the
Encina scheduling policy
EXTERNAL 55. Encina mon_status.h file and, if necessary, contact Customer
fcn failed, stat = %d.
Support.
Encina server failed to Encina mon_status.h file and, if necessary, contact Customer
USER 56.
advertise %s stat = %d. Support. For Encina server usage, refer to Supporting DCE and
Encina .
Encina failed to make
Encina mon_status.h file and, if necessary, contact Customer
USER 57. server recoverable, stat =
Support. For Encina server usage, refer to Supporting DCE and
%d.
Encina .
Encina could not open the resource manager associated with the
server. Check the error code in the Encina mon_status.h file.
Encina server failed to init
Ensure that the database XA product has been installed and
USER 58. resource manager, stat =
enabled, that the database is set up, and that the open information
%d.
string in the vtpm.conf file is set up correctly. For Encina server
usage, refer to Supporting DCE and Encina.
failed to find machine Encina client failure. Check the TP_llcode in /usr/include/errno.h
EXTERNAL 59. name, TP_error = %d, and, if necessary, contact Customer Support. TP_error is an
TP_llcode = %d. internal AppBuilder communications code.
Tuxedo client initialization failed. For the meaning of the TP_llcode,
Tuxedo client init failed,
look up the equivalent value for the variable tperror in the Tuxedo
EXTERNAL 60. TP_error = %d, TP_llcode
documentation. TP_error is an internal AppBuilder communications
= %d.
code.
Encina environment:
cell='%s', prin='%s'.
Encina client init failed: Encina client failure. Check the TP_llcode in the Encina
EXTERNAL 62. TP_error = %d TP_llcode = mon_status.h file and, if necessary, contact Customer Support.
%d. encina error msg: %s. TP_error is an internal AppBuilder communications code.
Encina security default Encina client failure. Check the ll code in the Encina mon_status.h
EXTERNAL 63. function failed: er = %d, ll = file and, if necessary, contact Customer Support. The first number
%d. (er) is an internal AppBuilder communications code.
Tuxedo transaction start failed. For the meaning of the TP_llcode,
Tuxedo transaction begin:
look up the equivalent value for the variable tperror in the Tuxedo
EXTERNAL 64. TP_error=%d,
documentation. TP_error is an internal AppBuilder communications
TP_llcode=%d.
code.

General Communications Messages EXTERNAL 65.

Encina transaction begin:
Encina transaction start failed. Check the TP_llcode in the Encina
TP_error=%d,
EXTERNAL 65. mon_status.h file and, if necessary, contact Customer Support.
TP_llcode=%d. encina
TP_error is an internal AppBuilder communications code.
error msg: %s.
Encina transaction commit failed. For the meaning of the
Tuxedo transaction
TP_llcode, look up the equivalent value for the variable tperror in
commit: TP_error=%d,
EXTERNAL 66. the Tuxedo documentation. TP_error is an internal AppBuilder
TP_llcode=%d. tuxedo
communications code. For further details, check the messages that
error msg: %s.
precede this message in the error log.
Encina transaction commit:
Encina transaction commit failed. Check the TP_llcode in the
TP_error=%d,
EXTERNAL 67. Encina mon_status.h file and, if necessary, contact Customer
TP_llcode=%d. encina
Support. TP_error is an internal AppBuilder communications code.
error msg: %s.
Encina transaction abort failed. For the meaning of the TP_llcode,
Tuxedo transaction look up the equivalent value for the variable tperror in the Tuxedo
EXTERNAL 68. rollback: TP_error=%d, documentation. TP_error is an internal AppBuilder communications
TP_llcode=%d. code. For further details, check the messages that precede this
message in the error log.
Encina transaction Encina transaction abort failed. Check the TP_llcode in the Encina
EXTERNAL 69. rollback: TP_error=%d, mon_status.h file and, if necessary, contact Customer Support.
TP_llcode=%d. TP_error is an internal AppBuilder communications code.
Internal AppBuilder communications error. Encina failed to perform
an RPC because no transaction existed. Ensure that dna_StartTxn
RPC attempted w/ no txn: is called successfully. TP_error is an internal AppBuilder
INTERNAL 70.
TP_error=%d. communications code. For further details, refer to the messages
that precede this message in the error log, and contact Customer
Support.
shadowed to disparate Shadowing is enabled when route table entries for the same
USER 71. protocols: TP_error=%d, service have the same priority. The protocol for all such entries is
TP_llcode=%d. vtrpc. Fix the route table.
Internal AppBuilder communications error. The first call in a
First of shadowed RPCs: shadowed transactional RPC failed. Ensure that routes for the
INTERNAL 72. TP_error=%d, shadowed calls are correct. For further details, refer to the
TP_llcode=%d. messages that precede this message in the error log, and contact
Customer Support.
A second or subsequent call in a shadowed transactional RPC
Second or later shadowed
failed. Ensure that routes for the shadowed calls are correct. If the
EXTERNAL 73. RPC: TP_error=%d,
problem persists, retain the error log and contact Customer
TP_llcode=%d.
Support.
Protocol library received
invalid instruction.
Internal AppBuilder communications error. Client initialization failed
Error in DNA initialization at at VTPM layer. For further details, refer to the messages that
INTERNAL 75.
VTPM level. precede this message in the error log, and contact Customer
Support.
Internal AppBuilder communications error. Start transaction failed
Error in DNA transaction at VTPM layer. For further details, refer to the messages that
INTERNAL 76.
start at VTPM level. precede this message in the error log, and contact Customer
Support.
Error Allocating client info The client machine failed to allocate memory. Contact the System
EXTERNAL 77.
for server '%s'. Administrator.
No Client Initialization was
Done.

INTERNAL 79. General Communications Messages

Internal AppBuilder communications error. Could not obtain server
Error Getting Server Info information from the DCE SERVER_CLIENTS file. For further
INTERNAL 79.
for server '%s'. details, refer to the messages that precede this message in the
error log, and contact Customer Support.
The call to the Encina client stub DLL failed. Ensure that the
Error Invoking Rule %s on
USER 80. service in question is available to the server. For Encina server
Server '%s'.
The AppBuilder communications client is unable to load the Encina
Error Loading Server Client client stub DLL or is unable to set up a binding to the Encina server
USER 81.
%s. in question. The Encina server may be down. For Encina server
The AppBuilder communications client is unable to load the Encina
Error Loading Server client stub DLL or is unable to set up a binding to the Encina server
USER 82.
Clients for server %s. in question. The Encina server may be down. For Encina server
Internal AppBuilder communications error. The AppBuilder
communications client failed to obtain an interface specification for
Error Getting if-spec for
INTERNAL 83. the client being called. For further details, refer to the messages
server %s.
Support.
The AppBuilder communications client failed to obtain service
Error Getting Rule Info for information from the Encina client stub DLL. Ensure that the
USER 84.
Rule %s. service requested is actually offered by the server. For Encina
Encina shadowing is attempted with a binding in which not all
No Server Found with protocols are vtrpc. The service is routed to both vtrpc and non-
USER 85. Protocol vtrpc for service= vtrpc servers. Fix the route table so that, if one of several shadow
%s. routes specifies vtrpc, all do. For Encina server usage, refer to
Supporting DCE and Encina.
Error Initializing PA Handle Encina RPC handle setup failed. Ensure that the Encina server is
EXTERNAL 86.
for server: '%s'. up.
Internal AppBuilder communications error. The error occurred
during Encina processing of an RPC call. Check the error code in
Transactional RPC error:
INTERNAL 87. the Encina mon_status.h file. For further details, refer to the
%d.
Customer Support.
Internal AppBuilder communications error. The error occurred
during Encina processing of an RPC call. The message variable
may be as follows: ENC_tip_0011: tran_Comm SendingRequest
Transactional RPC error:
INTERNAL 88. failed. If so, ensure that the transaction time-out value in
%s.
dna_StartTxn is sufficient. For further details, refer to the messages
Support.
Error on getting DCE RPC
Encina RPC handle setup failed. Ensure that the Encina server is
EXTERNAL 89. handle from Encina PA
running.
handle: %s.
Error on query the Encina RPC handle setup failed. Ensure that the Encina server is
EXTERNAL 90.
application server principal. running.
Internal AppBuilder communications error. VTPM client initialization
Error in DNA-to-VTPM
INTERNAL 91. failed. For further details, refer to the messages that precede this
Initialization.
message in the error log, and contact Customer Support.
Internal AppBuilder communications error. VTPM start transaction
Start Transaction.
Internal AppBuilder communications error. VTPM abort transaction
Abort Transaction.

General Communications Messages INTERNAL 94.

Internal AppBuilder communications error. VTPM commit
Error in DNA-to-VTPM transaction failed. For further details, refer to the messages that
INTERNAL 94.
Commit Transaction. precede this message in the error log, and contact Customer
Support.
The DCE SERVER_CLIENTS file did not include an entry for the
No RPC Stub DLL for
USER 95. specified server id. Add the entry. For DCE server usage, refer to
Serverid: '%s'.
An invalid network protocol is specified internally. Contact the
USER 96. %d: Unknown protocol.
An incorrect destination is specified in the route table. If, for
example, TCP/IP is in use, the host name is unknown: check the
USER 97. %s: Unknown host or LU.
TCP/IP hosts file. If LU6.2 is in use, the specified LU profile name
or alias is invalid.
%s: Unknown service or The specified port name is not found. Check the TCP/IP services
USER 98.
TP profile. file to ensure that the specified port name is listed there.
For forking servers using TCP/IP, refer to the protocol
Error preparing to listen to documentation for information on the error number. This message
USER 99.
network, errno=%d. indicates that the protocol cannot bind to a port, perhaps because
the port is already in use.
The error message includes the remote host name and a protocol-
specific error number. The remote machine may be down, or the
Error establishing
remote program may not be responding. If LU6.2 is in use, ensure
USER 100. conversation with %s,
that the LU6.2 configuration and mode profile are the same for both
errno=%d.
client and host. It is also possible that the communication may have
encountered a security restriction.
The error message includes a protocol-specific error number. If
TCP/IP is in use, the protocol may have failed to get a local socket,
EXTERNAL Error getting channel
as happens if the system file table is full. If LU6.2 is in use, the SNA
101. descriptor, errno=%d.
subsystem may not be running or, in AIX, an invalid LU profile
name may have been specified.
EXTERNAL Error getting channel
The error message includes a CPI-C error number.
102. descriptor, cmret=%d.
The message includes an error code specific to LU6.2. The host
EXTERNAL Error changing to receive
program died or a network problem occurred. If necessary, contact
103. state, errno=%d.
The message includes a protocol-specific error number. The host
EXTERNAL
Read error, errno=%d. program died or a network problem occurred. If necessary, contact
104.
EXTERNAL A blocking read returned 0,
105. errno = %d.
EXTERNAL
Write error, errno=%d. program died or a network problem occurred. If necessary, contact
106.
Error performing The message includes an LU6.2-specific error number. The host
EXTERNAL
REQUEST to SEND, program died or a network problem occurred. If necessary, contact
107.
errno=%d. the System Administrator.
This message occurs only if LU6.2 is in use. The message includes
EXTERNAL Error deallocating LU a protocol-specific error number. The host program died or a
108. conversation, errno=%d. network problem occurred. If necessary, contact the System
Administrator.
This message occurs only if TCP/IP is in use. The message
EXTERNAL Error closing network includes a protocol-specific error number. The host program died or
109. connection, errno=%d. a network problem occurred. If necessary, contact the System
Administrator.

EXTERNAL 110. General Communications Messages

EXTERNAL Error freeing memory, The message includes a platform-specific error number. If
110. errno=%d. necessary, contact the System Administrator.
EXTERNAL Error waiting on network The message includes a protocol-specific error number. If
111. channel, errno=%d. necessary, contact the System Administrator.
INTERNAL 112. Invalid argument passed. to the messages that precede this message in the error log, and
Internal AppBuilder communications error. The message includes
Error getting TP invocation an LU6.2 error number. For further details, refer to the messages
INTERNAL 113.
parameters, errno=%d. that precede this message in the error log, and contact Customer
Support.
No TP invocation
parameters received.
Invalid TP invocation
parameters.
EXTERNAL Error accepting new TCPIP The message includes a TCP/IP error number. Contact the System
116. connection, errno=%d. Administrator.
EXTERNAL Error trying to flush network A network write error has occurred. For further details, check the
117. data representation data. messages that precede this message in the error log.
A program did not receive data expected from the client or server
EXTERNAL Error trying to read data
with which it communicates. Check the error log of the remote
118. from the network.
client or server.
Invalid operation for Internal AppBuilder communications error. For further details, refer
INTERNAL 119. network data to the messages that precede this message in the error log, and
representation. contact Customer Support.
Error trying to set remote The message includes an LU6.2 error number. An incorrect partner
USER 120.
LU name, SNA error is %d. LU alias or connection profile is specified.
Error trying to set remote The message includes a CPI-C error number. An incorrect TP
USER 121.
TP name, SNA error is %d. name may have been specified.
The message includes a CPI-C error number. The remote machine
Error trying to allocate may be down or the remote program may not be operating. If LU6.2
USER 122. conversation, SNA error is is in use, ensure that the LU6.2 configuration and mode profile are
%d. the same for both client and host. It is also possible that the
communication may have encountered a security restriction.
The message includes a CPI-C error number.The host program
EXTERNAL Error trying to read data,
died or a network problem occurred. If necessary, contact the
123. SNA error is %d.
For forking servers using TCP/IP, this message indicates that the
protocol could not bind to a port, perhaps because the port is in use
Could not register TP
USER 124. or invalid. For LU6.2 on AIX, this message indicates that the
name.
protocol could not register the TP name on which the server is
listening, perhaps because the TP name is in use or invalid.
This message appears only if the TCP/IP autostart server is in use.
Error trying to get peer
USER 125. The server is not started correctly. Alternatively, the TCP/IP hosts
socket information.
file may not match the remote machine.
INTERNAL Error setting non-blocking I/
to the messages that precede this message in the error log, and
126. O.
The message includes a Named Pipes error number. The
Error creating Named Pipe, configuration of Named Pipes on a server machine is incorrect,
USER 127.
errno = %d. perhaps because a name is already in use. Contact the System
Administrator.


The message includes a Named Pipes error number. The
Error opening pipe to %s, configuration of Named Pipes on a Windows client workstation is
USER 128.
errno = %d. incorrect, or the server is not running, or a network problem
occurred. If necessary, contact the System Administrator.
INTERNAL Error setting i/o mode %X,
129. errno = %d.
The message includes a file name and a platform-specific error
EXTERNAL Error getting file status for
message. The file does not exist or is corrupted. Contact the
130. %s, errno = %d.
EXTERNAL Error reading from file %s, The message includes a file name and a platform-specific error
131. errno = %d. message. The file is corrupted.
EXTERNAL Error writing to file %s, The message includes a file name and a platform-specific error
132. errno = %d. message. Disk space is unavailable or the file is corrupted.
INTERNAL Invalid Data Presentation
133. type %d.
Listening on %d channels
INFO 134. with timeout of %ld sec %ld An informational message indicating a forking servers status.
usec.
Listening on %d channels
INFO 135. An informational message indicating a forking servers status.
with no timeout.
TCP/IP channel %d has an An informational message indicating that the forking server has
INFO 136.
event. received a client request.
LU6.2 channel %d has an An informational message indicating that the forking server has
INFO 137.
event. received a client request.
Accepted connection from A TCP/IP server-specific informational message indicating the hex
INFO 138.
host ip# %#lX. IP address from the remote client that requested a service.
Accepted connection from An LU6.2 server-specific information message indicating the client
INFO 139.
host LU %s. LU name.
EXTERNAL Could not enter the SEND LU6.2 returned an error, perhaps because the remote program died
140. state. or the network failed. Contact the System Administrator.
An informational message indicating the number of bytes that
INFO 141. We read %d bytes of data.
AppBuilder communications read from the network.
An informational message indicating the number of bytes that
INFO 142. We wrote %d bytes of data.
AppBuilder communications wrote to the network.
EXTERNAL Error reading/writing file For further details, check the platform-specific messages that
143. size. precede this message in the error log.
The message includes an LU6.2 error number. Either the remote
EXTERNAL Error sending confirm
program has failed or the problem is internal to AppBuilder
144. request, errno = %d.
communications. In the latter case, contact Customer Support.
The message includes an LU6.2 error number. Either the remote
EXTERNAL Error sending confirmed
program has failed or the problem is internal to AppBuilder
145. ACK, errno = %d.
communications. In the latter case, contact Customer Support.
INTERNAL
Bad confirm type %d. to the messages that precede this message in the error log, and
146.
INTERNAL Failure to set SYNC LEVEL an LU6.2 error number. For further details, refer to the messages
147. to %ld, errno = %ld. that precede this message in the error log, and contact Customer
Support.


INTERNAL Failure to check confirm an LU6.2 error number. For further details, refer to the messages
148. status. that precede this message in the error log, and contact Customer
Support.
Failure to set PREP to RCV
INTERNAL an LU6.2 error number. For further details, refer to the messages
TYPE to %ld,
149. that precede this message in the error log, and contact Customer
errno = %ld.
Support.
The message includes an LU6.2 error number. The DNA.INI file,
Could not set mode name LU6.2 section, MODE_NAME variable may not have been set, or
USER 150.
to %s, errno = %d. may have been set incorrectly. If the value is correct, make sure the
path to DNA.INI is set in the execution environment.
INFO 151. Using local LU name %s. An informational message.
INFO 152. Using mode name %s. An informational message.
INTERNAL Failure to set deallocate an LU6.2 error number. For further details, refer to the messages
153. type to %ld, errno = %ld. that precede this message in the error log, and contact Customer
Support.
EXTERNAL Error reading/writing file
Disk space is unavailable, or the file being transferred is corrupted.
154. line term format.
INTERNAL Text line termination format An informational message referring to the end-of-line characteristic
155. received is %d. of the file being transferred.
INTERNAL Transferring file %s of size
An informational message.
156. %d.
EXTERNAL Error blocking new signals, The message includes a UNIX error number. Contact the System
157. errno = %d. Administrator.
EXTERNAL Error restoring old signal The message includes a UNIX error number. Contact the System
158. mask, errno = %d. Administrator.
The message includes an LU2 error number. Possible problems
EXTERNAL Failure to connect session,
include an LU2 configuration error, a bad session name, a session
159. error = %d.
that is already in use, or a bad MFLOGON.SCR file.
The message includes an LU2 error number. Possible problems
EXTERNAL include a bad login ID, a bad password, an LU2 configuration error,
Login failure.
160. a bad session name, a session that is already in use, or a bad
MFLOGON.SCR file.
The message includes an LU2 error number. The mainframe is not
EXTERNAL Error trying to send
responding. Try again. If the problem persists, contact the System
161. keystroke, error = %d.
Administrator.
EXTERNAL Error disconnecting The message includes an LU2 error number. Contact the System
162. session, error = %d. Administrator.
EXTERNAL Error resetting session, The message includes an LU2 error number. Contact the System
163. error = %d. Administrator.
The message includes a TPS/3270 error number and an AIX error
EXTERNAL TPS/3270 LU Start Error.
number. Either the LU2 configuration is wrong or the SNA
164. e32rc = %d, sysrc = %d.
subsystem is not running.
INTERNAL Failure trying to set session an LU6.2 error number. For further details, refer to the messages
165. parameters, error = %d. that precede this message in the error log, and contact Customer
Support.
EXTERNAL Error while waiting for host responding. Try again. If the problem persists, contact the System
166. status, error = %d. Administrator. The problem may be internal to AppBuilder
communications.


Error starting host
EXTERNAL responding. Try again. If the problem persists, contact the System
notification for LU2, error =
167. Administrator. The problem may be internal to AppBuilder
%d.
communications.
Could not find string %s in The message includes an LU2 error number. A string specified in a
USER 168.
PS. return code is %d. COMPARE statement in an LU2 logon script is not found.
A program did not receive data expected from the client or server
EXTERNAL Insufficient data read from with which it communicates. Check the error log of the remote
169. the network. client or server. For data transmission, refer to Application
USER 170. Logoff failure. There may have been a problem in an LU2 logoff script.
Error opening AIX code
The message includes an AIX error number. AIX lacked the files
USER 171. page conversion routine,
necessary for multiple-language support. Review the installation.
errno = %d.
Error performing AIX code The message includes an AIX error number. A buffer overflow
EXTERNAL
page conversion, errno = occurred, or a character could not be converted from one code
172.
%d. page to the other. If necessary, contact Customer Support.
Internal AppBuilder communications error. AppBuilder
INTERNAL No valid DBCS/Mixed communications does not support the source or destination code
174. conversion routine. page. For further details, refer to the messages that precede this
The value of the DNA.INI file, NLS section, LOCAL_CODEPAGE
Local code page variable is not set to a valid code page. If the required data is in
USER 175.
undefined. place, make sure the path to DNA.INI is set in the execution
environment.
INTERNAL Bad internal code page
176. number, %d.
EXTERNAL Error loading dynamically - The specified DLL could not be loaded. For further details, refer to
177. %s. the messages that follow this one in the error log.
The Service Agent could not determine the numeric ID of a routing
could not read id from file, or event record. The specified file may have been corrupted.
USER 178.
line %d = %s. Remove the file and retransfer it in the service controller. If the
problem persists, contact the System Administrator.
A service agent normally deletes an old route or event file before
replacing that file with a newer version. In this case, the deletion
EXTERNAL failed. Delete that file, as well as the file identified in the DNA.INI
could not unlink %s file.
179. file, SMA section, TEMP_FILE variable. Then retransfer the new
version of the file in the service controller. If the problem persists,
A service agent is unable to update the route or event file because
the attempted renaming of the temp file failed. Delete the route or
EXTERNAL could not rename %s to event file, as well as the file identified in the DNA.INI file, SMA
180. %s. section, TEMP_FILE variable. Then retransfer the new version of
the route or event file in the service controller. If the problem
persists, contact the System Administrator.
Failure to attach to service-agent shared memory. Check the
EXTERNAL attaching to SVM shared segment whose key corresponds to the value in the DNA.INI file,
181. memory. SMA section, IPC_KEY variable. Make sure that segment
permissions (IPCS) are correct.
Internal AppBuilder communications error. Failure of write-wait on
INTERNAL write-waiting on SVM service-agent shared memory. For further details, refer to the
182. shared memory. messages that precede this message in the error log, and contact
Customer Support.


Internal AppBuilder communications error. Failure of read-wait on
INTERNAL read-waiting on SVM service-agent shared memory. For further details, refer to the
183. shared memory. messages that precede this message in the error log, and contact
Customer Support.
Internal AppBuilder communications error. Service-agent shared
INTERNAL memory overflow. For further details, refer to the messages that
id %ld too big.
184. precede this message in the error log, and contact Customer
Support.
Internal AppBuilder communications error. Failure to release
INTERNAL write-signaling on SVM service-agent shared memory after write. For further details, refer
185. shared memory. to the messages that precede this message in the error log, and
Internal AppBuilder communications error. Failure to release
INTERNAL read-signaling on SVM service-agent shared memory after read. For further details, refer
186. shared memory. to the messages that precede this message in the error log, and
Internal AppBuilder communications error. Shared memory pointed
to by the DNA.INI file, SMA section, IPC_KEY variable is absent
and cannot be allocated. System limits for IPC on the machine may
INTERNAL
in shmget, errno = %d. have been exceeded. Check the specified error number in the /usr/
187.
include/sys/errno.h file or its equivalent. For further details, refer to
the messages that precede this message in the error log, and
Internal AppBuilder communications error. A shared memory attach
(shmat) system call failed. Check the segment whose key
corresponds to the value in the DNA.INI file, SMA section,
INTERNAL IPC_KEY variable and make sure that the service agent has
in shmat, errno = %d.
188. permission to read from and write to that segment. Check the
specified error number in the /usr/include/sys/errno.h file or its
equivalent. For further details, refer to the messages that precede
this message in the error log, and contact Customer Support.
Internal AppBuilder communications error. Could not detach from
service-agent shared memory. Future attempts to attach may fail,
INTERNAL
in shmdt, errno = %d. and freeing that memory may be impossible. For further details,
189.
refer to the messages that precede this message in the error log,
and contact Customer Support.
Internal AppBuilder communications error. Could not access
semaphore pointed to by the DNA.INI file, SMA section, IPC_KEY
INTERNAL variable. System limits for IPC resources on the machine may have
in semget, errno = %d.
190. been exceeded. Ensure that semaphores are enabled on your
system. For further details, refer to the messages that precede this
Internal AppBuilder communications error. Failure in operation on
read semaphore for service agent. Check the specified error
INTERNAL in semctl, errno = %d, on
number in the /usr/include/sys/errno.h file or its equivalent. For
191. read semaphore.
further details, refer to the messages that precede this message in
lock semaphore for service agent. Check the specified error
INTERNAL in semctl, errno = %d, on
number in the /usr/include/sys/errno.h file or its equivalent. For
192. lock semaphore.
INTERNAL in semop, errno = %d, lock semaphore for service agent. For further details, refer to the
193. waiting on lock semaphore. messages that precede this message in the error log, and contact
Customer Support.


INTERNAL in semop, errno = %d, lock semaphore. For further details, refer to the messages that
194. signalling lock semaphore. precede this message in the error log, and contact Customer
Support.
INTERNAL in semop, errno = %d, wait read semaphore. For further details, refer to the messages that
195. read = 0. precede this message in the error log, and contact Customer
Support.
Internal AppBuilder communications error.Failure in operation on
INTERNAL in semop, errno = %d, read semaphore. For further details, refer to the messages that
196. increment read. precede this message in the error log, and contact Customer
Support.
Internal AppBuilder communications error.Failure in operation on
INTERNAL in semop, errno = %d, read semaphore. For further details, refer to the messages that
197. decrement read. precede this message in the error log, and contact Customer
Support.
Internal AppBuilder communications error. Shared memory
INTERNAL adding ID = %d. ID number
overflow. For further details, refer to the messages that precede
198. is too large.
Internal AppBuilder communications error. Failure in semaphore
INTERNAL locking the semaphore.
operation. For further details, refer to the messages that precede
199. Return Code = %d.
getting the shared memory Internal AppBuilder communications error. Shared memory failure.
INTERNAL
segment. Return Code = For further details, refer to the messages that precede this
200.
%d. message in the error log, and contact Customer Support.
freeing the shared memory Internal AppBuilder communications error. Shared memory failure.
INTERNAL
segment. Return Code = For further details, refer to the messages that precede this
201.
%d. message in the error log, and contact Customer Support.
Internal AppBuilder communications error. Semaphore failure. For
INTERNAL unlocking the semaphore.
202. Return Code = %d.
Internal AppBuilder communications error. Shared memory is
pushing information to the
INTERNAL unable to receive an action record. For further details, refer to the
Action Table. Return Code
203. messages that precede this message in the error log, and contact
= %d.
Customer Support.
INTERNAL unable to receive a machine record. For further details, refer to the
MACHINE Table. Return
Code= %d.
Customer Support.
INTERNAL unable to receive a cell record. For further details, refer to the
CELL Table. Return Code=
%d.
Customer Support.
INTERNAL unable to receive a machine-cell membership record. For further
MINC Table. Return Code=
206. details, refer to the messages that precede this message in the
%d.
INTERNAL unable to receive a cell-cell membership record. For further details,
CINC Table. Return Code=
207. refer to the messages that precede this message in the error log,
%d.
INTERNAL unable to receive an event record. For further details, refer to the
EVENT Table. Return
Code= %d.
Customer Support.


INTERNAL unable to receive a trigger record. For further details, refer to the
TRIGGER Table. Return
Code= %d.
Customer Support.
INTERNAL unable to receive a routing-table record. For further details, refer to
ROUTES Table. Return
210. the messages that precede this message in the error log, and
Code= %d.
deleting global event
unable to receive an event record. For further details, refer to the
INTERNAL 211. information. Return Code=
%d.
Customer Support.
INTERNAL Getting Input and Control
212. Info.
INTERNAL Breaking Control and Data
213. Info.
Getting Host Name for The DNA.INI file, SMA section, SMA_HOST_NAME variable is not
USER 214.
SMA. set or is set incorrectly.
Internal AppBuilder communications error. The applications call to
INTERNAL dna_InitClient failed. For further details, refer to the messages that
Initializing Client.
215. precede this message in the error log, and contact Customer
Support.
A service agent tried and failed to post an event. For further details,
INTERNAL
Doing Post Bound Event. refer to the messages that precede this message in the error log,
216.
Internal AppBuilder communications error. An error occurred during
INTERNAL a call to dna_BoundServiceRequest. For further details, refer to the
Getting SMA bindings.
Customer Support.
The system is unable to get the information necessary to route data
to the parent of a service agent. Ensure that valid values were
specified for the DNA.INI file, SMA section,
USER 218. Getting Parent Binding.
SMA_SMSA_CODEPAGE, SMA_SMSA_NAME,
SMA_SMSA_PRIORITY, SMA_SMSA_PROTOCOL, and
SMA_SMSA_SERVERID variables.
Internal AppBuilder communications error. An error occurred in
INTERNAL Setting Cookie Into Client relation to a gateway. For further details, refer to the messages that
219. Cntxt. precede this message in the error log, and contact Customer
Support.
Internal AppBuilder communications error. An error occurred in
INTERNAL Setting Login Info Into relation to a gateway. For further details, refer to the messages that
220. Client Cntxt. precede this message in the error log, and contact Customer
Support.
Internal AppBuilder communications error. Reduce the number of
Event Data=%d Larger
INTERNAL bytes in an applications event data. For further details, refer to the
Than System Allowed
Limit=%d.
Customer Support.
Internal AppBuilder communications error. Error in the Service
Manager setup. Ensure that this machine has been assigned to a
INTERNAL Error Getting Values for
cell and that the information has been pushed to this machine. For
222. SMA and SMASUBCELL.


Internal AppBuilder communications error. Close client applications
and ask the System Administrator to restart AppBuilder
INTERNAL DNA Detects a Null Shared
communications agents and the service executive. For further
223. Memory Handle.
details, refer to the messages that precede this message in the
Internal AppBuilder communications error. The application tried to:
Receive an event without having registered it, or Deregister a non-
INTERNAL
No Events Registered. existent event. If registering all relevant events fails to solve the
224.
problem, refer to the messages that precede this message in the
Internal AppBuilder communications error. Client applications have
registered more events than the system can support. Deregister
INTERNAL
No Free Events Found. events that are no longer of interest. For further details, refer to the
225.
Customer Support.
Internal AppBuilder communications error. Receipt of this message
suggests that the error catalog is corrupted, since events need not
INTERNAL Null Event Information
be associated with event information. For further details, refer to
226. Received.
the messages that precede this message in the error log, and
Internal AppBuilder communications error. An application asked to
INTERNAL Event To Be Deleted Not deregister an event that is not in use. For further details, refer to the
227. Found. messages that precede this message in the error log, and contact
Customer Support.
Internal AppBuilder communications error. Problem in memory
INTERNAL No Free Postings allocation. Ensure that all outstanding events have been received.
228. Available. For further details, refer to the messages that precede this
Internal AppBuilder communications error. Memory has been
INTERNAL Failure During Deleting corrupted. Reboot the system. For further details, refer to the
229. Mapping Entry. messages that precede this message in the error log, and contact
Customer Support.
INTERNAL corrupted. Reboot the system. For further details, refer to the
No Event Data Found.
Customer Support.
INTERNAL corrupted. Reboot the system. For further details, refer to the
No Postings Found.
Customer Support.
INTERNAL Nothing Preceding for
232. Posted Event Id = %ld.
INTERNAL No More Map Entries corrupted. Reboot the system. For further details, refer to the
233. Available. messages that precede this message in the error log, and contact
Customer Support.
INTERNAL No Data Entry Found for
234. Event.
INTERNAL
Init DCE Client. to the messages that precede this message in the error log, and
235.
INTERNAL
Close DCE Client. to the messages that precede this message in the error log, and
236.


INTERNAL
DCE Abort Transaction. to the messages that precede this message in the error log, and
237.
INTERNAL
DCE Commit Transaction. to the messages that precede this message in the error log, and
238.
Invalid DCE Service Name: In a service request, the service name is NULL or empty. Fix the
USER 239.
%s. code.
INTERNAL Failure in DCE ServerInfo
240. Cache Init.
241. Cache Insertion.
242. Cache Update.
INTERNAL DCE RPC Failure for
243. Service: DCE_START.
INTERNAL DCE RPC Failure for
244. Service: %s.
The DCE SERVER_CLIENTS file did not include an entry for the
DCE Client Stub DLL for
USER 245. specified serverid. Add the entry. For DCE server usage, refer to
Serverid: %s Not Found.
The DCE client stub DLL is missing or corrupted. Reprepare the
Loading DCE Client Stub
USER 246. DLL per the DCE documentation. For DCE server usage, refer to
DLL: %s.
Internal AppBuilder communications error. Reprepare the DCE
INTERNAL Getting DCE Server
client stub. For further details, refer to the messages that precede
247. Interface.
EXTERNAL Locking An Instance for
All DCE servers of the specified name are busy.
248. Serverid: %s.
Internal AppBuilder communications error. The DCE client could
INTERNAL Release Instance for not release its DCE server process for use by other clients. For
249. Serverid: %s. further details, refer to the messages that precede this message in
INTERNAL Getting DCE Remote
250. Server Handle: %s.
EXTERNAL rpc_server_register_if For further details, check the error number in the DCE
251. failed with %d. documentation.
EXTERNAL rpc_server_use_all_protse For further details, check the error number in the DCE
252. gs failed with %d. documentation.
EXTERNAL rpc_server_inq_bindings For further details, check the error number in the DCE
EXTERNAL rpc_binding_export failed For further details, check the error number in the DCE
254. with %d. documentation.
EXTERNAL rpc_binding_vector_free For further details, check the error number in the DCE
EXTERNAL rpc_ep_unregister failed For further details, check the error number in the DCE


EXTERNAL rpc_ep_register failed with For further details, check the error number in the DCE
257. %d. documentation.
EXTERNAL rpc_server_listen failed For further details, check the error number in the DCE
EXTERNAL rpc_mgmt_stop_server_list For further details, check the error number in the DCE
259. ening failed with %d. documentation.
EXTERNAL Could not start transaction, For further details, check the error number in the SQL
260. sqlcode = %d. documentation.
EXTERNAL Could not commit For further details, check the error number in the SQL
261. transaction, sqlcode = %d. documentation.
EXTERNAL Could not abort For further details, check the error number in the SQL
262. transaction, sqlcode = %d. documentation.
EXTERNAL Could not connect to For further details, check the error number in the SQL
263. database, sqlcode = %d. documentation.
EXTERNAL Could not set consistency For further details, check the error number in the SQL
264. level, sqlcode = %d. documentation.
INTERNAL Error trying to send
265. preamble.
INTERNAL Error trying to read
266. preamble.
A service executive or service manager requires one of these
Invalid data source "%s" values for the DNA.INI file, SMX section, DATASOURCE variable:
USER 267.
specified. FILE, SHMEM, or DATABASE. Ensure that the appropriate value is
specified.
In relation to a combined service manager and service agent
Local database specified,
(SMSA), the DNA.INI file, SMX section, DATASOURCE variable is
USER 268. but not supported by
set to DATABASE. SMSAs rely on information in shared memory or
software.
a file, so DATABASE is not a valid option.
Internal AppBuilder communications error. The Service Executive
INTERNAL SMX select failed for cells, is unable to obtain cell information. For further details, refer to the
269. sqlcode = %d. messages that precede this message in the error log, and contact
Customer Support.
Spawning a connection- An informational message indicating that an AppBuilder
INFO 270.
oriented server process. communications server has spawned a child process.
Usage %s (if using db --- -
u<dbname> -i<db isolation
An informational message indicating the AppBuilder
INFO 271. mode c/m/r/d>) (-f
communications server startup syntax.
(forking) or (-d -p <tcp/lu62/
npipe> - autostart) ).
If %s is a gateway - add -g
An informational message indicating the AppBuilder
INFO 272. and remove the db-related
communications server startup syntax.
options.
INTERNAL Error in reading result on
273. abort.
The message includes a protocol-specific alias for an endpoint; for
EXTERNAL Abort failed for channel %s example, a TCP/IP service, a Named Pipes pipe name, or an
274. - sqlcode = %ld. LU6.2 TP name. For further information, look up the sqlcode that is
in the message.
INTERNAL
Error in sending the data. to the messages that precede this message in the error log, and
275.


INTERNAL Error in initializing client
276. structures in conn.
INTERNAL shutdown - Error in reading
277. result on commit.
The message includes a protocol-specific alias for an endpoint; for
shutdown - Commit failed
EXTERNAL example, a TCP/IP service, a Named Pipes pipe name, or an
for channel %s; sqlcode =
278. LU6.2 TP name. For further details, look up the sqlcode that is in
%ld.
the message.
INTERNAL shutdown - error in closing
279. channel %s.
INTERNAL
Error in reading the cookie. to the messages that precede this message in the error log, and
280.
INTERNAL init_channel_info returned
281. NULL.
INTERNAL Client - could not open a
282. channel ptr.
INTERNAL failure in reading the
283. cookie.
INTERNAL Child %d- Error in
284. shutdown after commit.
INTERNAL unable to invoke the server
285. DLL.
INTERNAL Failure in sending the
286. output data.
server shutdown - error, Internal AppBuilder communications error. For further details, refer
INTERNAL
could not find the database to the messages that precede this message in the error log, and
287.
shutdown function. contact Customer Support.
Internal AppBuilder communications error. The server is unable to
Could not get dll load the specified service. Ensure that the service is prepared per
INTERNAL
information from the entry instructions in Application Programming Interface. For further
288.
point - service %s. details, refer to the messages that precede this message in the
Internal AppBuilder communications error.The message includes a
INTERNAL Could not initialize the net protocol-specific error code. For further details, refer to the
289. layer, net error = %d. messages that precede this message in the error log, and contact
Customer Support.
INTERNAL server main - Error - failure
290. in initializing structures.
INTERNAL failed to open any channels
291. - exiting.
The system failed to fork a child process from a forking server. The
EXTERNAL Parent server process -
problem may involve the process table. Contact the System
292. Error on fork.
Administrator.


INTERNAL Error in closing channel
293. %d.
Error in opening file (read- Internal AppBuilder communications error. For further details, refer
INTERNAL
only) %s for reading to the messages that precede this message in the error log, and
294.
channel names. contact Customer Support.
Internal AppBuilder communications error. The message arose on
INTERNAL The servers cookie
the client side of a data communication. Review the servers error
295. indicates an error - %d.
log, and contact Customer Support.
INTERNAL
Error in writing the cookie. to the messages that precede this message in the error log, and
296.
INTERNAL Error - must never reach
297. here if using MFLU62/LU2.
Although TCP has been Internal AppBuilder communications error. For further details, refer
INTERNAL
requested, this code was to the messages that precede this message in the error log, and
298.
not compiled for TCP. contact Customer Support.
INTERNAL failed to resolve symbol
299. after loading %s.
INTERNAL
close failed for channel %s. to the messages that precede this message in the error log, and
300.
The server-authentication DLL is missing or corrupted, or the
customized server-authentication routine returned an error. If the
server authentication error. DLL is missing or corrupted, error-log messages preceding this
USER 301.
user_name - %s. message indicate that the problem occurred at load time. If such
messages are present, reprepare the DLL. Otherwise, check the
DLL source to determine the reason for failure.
The server-authorization DLL is missing or corrupted, or the server-
authorization routine returned an error. If the DLL is missing or
server authorization error.
corrupted, error-log messages preceding this message indicate
USER 302. user_name - %s, service -
that the problem occurred at load time. If such messages are
%s.
present, reprepare the DLL. Otherwise, check the DLL source to
determine the reason for failure.
INTERNAL Bound Service Request for
303. rule %s failed.
Internal AppBuilder communications error. A System error occurred
INTERNAL Could not invoke rule %s, during execution of the specified rule. For further details, refer to
304. bad rule type %d. the messages that precede this message in the error log, and
INTERNAL Could not resolve address as a result of a problem with rule preparation. For further details,
305. for view name %s. refer to the messages that precede this message in the error log,
INTERNAL Unable to get the view info as a result of a problem with rule preparation. For further details,
306. map for rule %s. refer to the messages that precede this message in the error log,
INTERNAL
The data %s is NULL. to the messages that precede this message in the error log, and
307.


The command line arguments used to invoke the server (startup
Invalid command-line server) were incorrect. It is invalid to start the AppBuilder
USER 308. parameters - cannot communications server as a multithreading server in the current
specify multithreading. environment. If a forking server is required, change the command
line options to include -f.
INTERNAL
The cookie is NULL. to the messages that precede this message in the error log, and
309.
EXTERNAL CICS service %s abended
Check the CICS abend code.
310. - abend code = %s.
invalid opcode for value
%s.
A forking server is unable to open any of the channels specified for
it in the DNA.INI file, DNA_SERVER section, LU_NAMES,
forking/multi-threading
NPIPE_NAMES, or TCPIP_SERVICES variable. Make sure you
USER 312. server - no channels to
assigned values to the variables that are pertinent to this server. If
open - exiting.
the problem persists, contact the System Administrator or the
Customer Service.
forking server - call to
EXTERNAL For further details, check the error number in the operating system
library routine %s failed -
313. documentation.
errno = %d.
A forking server is unable to open any of the channels specified for
it in the DNA.INI file, DNA_SERVER section, LU_NAMES,
Could not open channel NPIPE_NAMES, or TCPIP_SERVICES variable. Make sure: You
USER 314. %s, protocol %s - will not assigned values to the variables that are pertinent to this server.
listen on it. Other servers or gateways are not also listening on the channels. If
the problem persists, contact the System Administrator or the
Customer Service.
Internal AppBuilder communications error. The specified DLL is
missing or corrupted. If the file is an exit DLL, ensure that the exit-
INTERNAL hps_load returned error on specific variable in the DNA.INI file, DNA_EXITS section is set
315. loading %s. correctly and that the DLL is prepared correctly. If the DLL is an
AppBuilder communications system file or if the problem persists,
contact the System Administrator or the Customer Service.
INTERNAL Call to commit on the cics
to the messages that follow this message in the error log, and
316. server failed.
INTERNAL Call to abort on the cics
to the messages that follow this message in the error log, and
317. server failed.
INTERNAL
The call context is null. to the messages that follow this message in the error log, and
318.
INTERNAL Sending a client request -
319. could not send the cookie.
Sending a client request - Internal AppBuilder communications error. For further details, refer
INTERNAL
could not send the header to the messages that precede this message in the error log, and
320.
and data. contact Customer Support.
INTERNAL Sending a view - could not
321. send the cookie.
INTERNAL Could not flush the buffer
322. after a service request.


INTERNAL Could not flush the buffer
323. during a shutdown.
Server - invalid command
USER 324. The server startup command syntax is incorrect.
line options.
Internal AppBuilder communications error. If the preceding
Error in reading/
INTERNAL messages in the error log refer to a customized data type, check
marshalling view data from
325. the descriptions associated with those messages. Otherwise,
the network.
INTERNAL Abort request from a
326. gateway failed.
gateway abort - could not Internal AppBuilder communications error. For further details, refer
INTERNAL
send the output to the to the messages that precede this message in the error log, and
327.
client. contact Customer Support.
Error in receiving the Internal AppBuilder communications error. For further details, refer
INTERNAL
control information of the to the messages that precede this message in the error log, and
328.
view. contact Customer Support.
INTERNAL Error in sending the control
329. information of the view.
call to the local cics server
EXTERNAL Check the CICS error code. If necessary, contact Customer
for service name %s -
330. Support.
retcode = %d.
Although a gateway service
USER 331. has been requested, this is A server is not configured as a gateway.
not a gateway.
INTERNAL Error - the call via a
332. gateway failed.
INTERNAL Could not initialize the
333. output view.
INTERNAL Could not initialize the
334. output sub-view.
No view initialization Internal AppBuilder communications error. For further details, refer
INTERNAL
information found - type = to the messages that precede this message in the error log, and
335.
%s. contact Customer Support.
Error invoking output Internal AppBuilder communications error. For further details, refer
INTERNAL
initialization function for to the messages that precede this message in the error log, and
336.
type = %s. contact Customer Support.
INTERNAL failure in dna/hps
337. initialization.
INTERNAL failure in executing service
338. %s.
INTERNAL
failure in using service %s. to the messages that precede this message in the error log, and
339.
INTERNAL
abort failed. to the messages that precede this message in the error log, and
340.


INTERNAL
commit failed. to the messages that precede this message in the error log, and
341.
INTERNAL
gateway - shutdown failed. to the messages that precede this message in the error log, and
342.
Internal AppBuilder communications error. Do the following: Ensure
that the DNA.INI file, ROUTING section, NAME_SERVICE variable
specifies the source of routing information. Depending on the value
of ROUTING section, NAME_SERVICE variable, check the data
stored in the Service Manager or the value of the DNA.INI file,
INTERNAL Error in getting protocol
ROUTING section, DNA_DCENS_DIR, ROUTETBL, or
343. information for service %s.
DEFAULT_PROTOCOL variable. Review the source of routing
information to ensure that the service specified in the error
message is associated with a valid protocol. For further details,
refer to the messages that precede this message in the error log,
Internal AppBuilder communications error. The implementation file
Error in getting the identified in the DNA.INI file, DNA_SERVER section,
INTERNAL
implementation name for IMPNAME_FILE variable must include an entry for the specified
344.
service %s. service. For further details, refer to the messages that precede this
INTERNAL Error in sending the header
345. and view data.
INTERNAL Gateway could not commit
346. on servers.
Server - Could not send the Internal AppBuilder communications error. For further details, refer
INTERNAL
output after performing the to the messages that precede this message in the error log, and
347.
commit. contact Customer Support.
INTERNAL Abort - could not receive
348. data.
Internal AppBuilder communications error. Ensure that your
INTERNAL Could not re-start database exits and overall database installation are correct. For
349. transaction after a commit. further details, refer to the messages that precede this message in
INTERNAL Could not re-start database exits and overall database installation are correct. For
350. transaction after an abort. further details, refer to the messages that precede this message in
Server - Could not send the Internal AppBuilder communications error. For further details, refer
INTERNAL
output after performing an to the messages that precede this message in the error log, and
351.
abort. contact Customer Support.
INTERNAL Could not find input control
352. information for service %s.
INTERNAL Abort - error in sending
353. output.
EXTERNAL runtime library call %s Check the system-specific error code. If necessary, contact the
354. failed - system error = %s. System Administrator.
INTERNAL Call to the conn section for
355. service %s failed.


INTERNAL Call to the conn section to
356. initialize failed.
INTERNAL Call to the conn section to
357. close failed.
INTERNAL Call to the conn section to database exits and overall database installation are correct. For
358. commit failed. further details, refer to the messages that precede this message in
INTERNAL Call to the conn section to database exits and overall database installation are correct. For
359. abort failed. further details, refer to the messages that precede this message in
Client couldnt fill the net
INTERNAL context - channel %s,
360. protocol %s, serverid %s,
code page %s, priority %d.
INTERNAL Server couldnt fill the net
361. context.
INTERNAL Could not flush the channel
362. %s.
INTERNAL Could not get the control
363. address for view %s.
INTERNAL Failure in initializing the
364. dna client context.
Error in filling the user- Internal AppBuilder communications error. For further details, refer
INTERNAL
specified information for to the messages that precede this message in the error log, and
365.
CICS. contact Customer Support.
INTERNAL Error in getting the dna
366. client context.
Gateway - Could not route Internal AppBuilder communications error. For further details, refer
INTERNAL
and send the request to an to the messages that precede this message in the error log, and
367.
application server. contact Customer Support.
Internal AppBuilder communications error. Ensure that your server-
INTERNAL Gateway - Call to commit side database exits and overall database installation are correct.
368. the client failed. For further details, refer to the messages that precede this
Internal AppBuilder communications error. Ensure that your server-
INTERNAL Call to abort the client side database exits and overall database installation are correct.
369. failed. For further details, refer to the messages that precede this
INTERNAL Gateway - Call to close the
370. client failed.
Gateway - Could not get Internal AppBuilder communications error. For further details, refer
INTERNAL
service info from dna for to the messages that precede this message in the error log, and
371.
service %s. contact Customer Support.
Could not determine Internal AppBuilder communications error. For further details, refer
INTERNAL
whether to allocate space to the messages that precede this message in the error log, and
372.
for output data. contact Customer Support.


INTERNAL
Gateway - Client call failed. to the messages that precede this message in the error log, and
373.
Error in reading/ Internal AppBuilder communications error. For further details, refer
INTERNAL
marshalling header data to the messages that precede this message in the error log, and
374.
from the network. contact Customer Support.
Error in writing/marshalling Internal AppBuilder communications error. For further details, refer
INTERNAL
header data from the to the messages that precede this message in the error log, and
375.
network. contact Customer Support.
Forking server - the parent Internal AppBuilder communications error. For further details, refer
INTERNAL
failed to clean up after the to the messages that precede this message in the error log, and
376.
childs execution. contact Customer Support.
Internal AppBuilder communications error. Review the DNA.INI file,
DNA_SERVER section, LU_NAMES, NPIPE_NAMES, or
Server - failed to get
INTERNAL TCPIP_SERVICES variable to ensure that they identify the correct
information about channels
377. channels. Make sure the channels are identified to your protocol.
- protocol %s.
For further details, refer to the messages that precede this
INTERNAL Failure in writing control
378. information.
INTERNAL Failure in reading control
379. information.
INTERNAL Error in sending a self-
380. describing view.
INTERNAL Error in reading a self-
381. describing view.
INTERNAL Error in finding the number
382. of control elements.
INTERNAL Failure in reading the
383. control header.
INTERNAL Failure in writing the control
384. header.
INTERNAL CICS call for service %s
385. failed.
INTERNAL Server commit - could not
386. read data.
INTERNAL Error - could not initialize
387. tracing - exiting.
USER 388. %s Bad command line
The server startup command syntax is incorrect.
parameter for option %s.
EXTERNAL The server couldnt The server returned an error message to the client. For further
389. connect to the database. details, refer to the messages in the servers error log.
The server couldnt
EXTERNAL The server returned an error message to the client. For further
disconnect from the
390. details, refer to the messages in the servers error log.
database.


EXTERNAL The server couldnt start The server returned an error message to the client. For further
391. the transaction. details, refer to the messages in the servers error log.
EXTERNAL The server couldnt commit The server returned an error message to the client. For further
EXTERNAL The server couldnt abort The server returned an error message to the client. For further
Internal AppBuilder communications error. The server returned an
INTERNAL
Server - invalid commit. error message to the client. For further details, refer to the
394.
messages in the servers error log, and contact Customer Support.
INTERNAL
Server - invalid abort. error message to the client. For further details, refer to the
395.
INTERNAL
Server - load rule failed. error message to the client. For further details, refer to the
396.
INTERNAL
Server - function call failed. error message to the client. For further details, refer to the
397.
INTERNAL The server couldnt restart
error message to the client. For further details, refer to the
398. the transaction.
INTERNAL The server couldnt
399. initialize the gateway.
INTERNAL The server couldnt
400. shutdown the gateway.
INTERNAL The server couldnt commit
401. the gateway.
INTERNAL The server couldnt abort
402. the gateway.
INTERNAL Server - Invalid comms
403. protocol.
INTERNAL Server - dna/db
404. initialization failed.
INTERNAL This server is not a
405. gateway.
There is a problem in a server authentication exit. The server
server authentication
USER 406. returned an error message to the client. For further details, refer to
failure
the messages in the servers error log.
There is a problem in a server authorization exit.The server
USER 407. server authorization failure. returned an error message to the client. For further details, refer to
the messages in the servers error log.
INTERNAL
Server - CICS call failed. error message to the client. For further details, refer to the
408.
INTERNAL Server - CICS commit
409. failed.


INTERNAL
Server - CICS abort failed. error message to the client. For further details, refer to the
410.
Server failed initializing the
INTERNAL 411. error message to the client. For further details, refer to the
output view.
EXTERNAL Server unable to invoke The server returned an error message to the client. For further
412. requested service. details, refer to the messages in the servers error log.
INTERNAL Server detected invalid
413. RPC type.
The EXEC CICS command failed with the specified RESP and
RESP2 response codes from CICS. If the CICS command is a
EXEC CICS %s failed with VERIFY, then the response values are the return code and reason
EXTERNAL
response values %d and code returned by the security package (RACF, ACF2 etc). Note that
414.
%d. these may both be zero, indicating that CICS has raised a
NOTAUTH condition. Refer to the CICS/ESA Users Handbook for
an explanation of the CICS response codes.
The time-out period specified in your LU2 logon script has expired.
EXTERNAL Timeout while waiting for
Make sure the WAITSTRING verb has been used correctly in the
415. string "%s" in LOGIN script.
script.
EXTERNAL DCE name service XOM
Ensure that the DCE CDS server starts correctly.
416. error# %d has occurred.
EXTERNAL DCE name service XDS
417. %s returned error %d.
DCE name service XDS
EXTERNAL
%s failed for unknown Ensure that the DCE CDS server starts correctly.
418.
reason.
EXTERNAL DCE name service
419. ds_initialize() failed.
DCE name service:
EXTERNAL
malformed service entry Ensure that the DCE CDS server starts correctly.
420.
attribute.
INTERNAL Not a valid DCE name
421. service request.
The DNA.INI file, ROUTING section, DNA_DCENS_DIR variable
Invalid DCE directory entry
USER 422. did not specify the full path of the DCE Name Service Directory. For
name format: %s.
DCE server usage, refer to Supporting DCE and Encina.
The DCE login as cell administrator (cell_admin) or (for AppBuilder)
No required dce_login
USER 423. as system administrator (hps) is not performed. For DCE server
performed.
EXTERNAL DCE name service error
424. read: %s.
Incorrect [ROUTING] The DNA.INI file, ROUTING section, NAME_SERVICE variable is
USER 425.
NAME_SERVICE value. not set or is set incorrectly.
INTERNAL A Null Pointer Sent to
to the messages in the servers error log, and contact Customer
426. Receive Context Pointer.
Support.
Error trying to allocate
EXTERNAL The system failed to allocate memory. Contact the System
memory, system error =
427. Administrator.
%d.


The client-side authentication exit did not elicit a user ID expected
Userid token was in logon
by an LU2 logon script. Perhaps the exit is not being invoked or is
USER 428. script, but no userid was
not storing the user ID. Make sure the DNA.INI file, DNA_EXITS
passed in the call context.
section, DNA_AUTHENT_EXIT variable is set correctly.
The client-side authentication exit did not elicit a password
Password token was in
expected by an LU2 logon script. Perhaps the exit is not being
logon script, but no
USER 429. invoked or is not storing the user ID. Make sure the DNA.INI file,
password was passed in
DNA_EXITS section, DNA_AUTHENT_EXIT variable is set
the call context.
correctly.
INTERNAL could not convert to an
For future use.
430. array.
EXTERNAL runtime library call %s
Run-time problem. Check the system-specific error code.
431. failed - system error = %d.
Could not get the name of
INTERNAL
the static servers template For future use.
432.
file.
INTERNAL Couldnt generate code for
For future use.
433. the static server.
INTERNAL
The file name is NULL. For future use.
434.
INTERNAL
The file pointer is NULL. For future use.
435.
INTERNAL Error in writing copyright
For future use.
436. information into the file.
INTERNAL Error in generating header
For future use.
437. information.
INTERNAL Error in generating
For future use.
438. component information.
INTERNAL could not generate code for
For future use.
439. rule insertion.
INTERNAL could not generate code for
For future use.
440. component insertion.
Could not generate code
INTERNAL
for internal mapping For future use.
441.
structures.
INTERNAL Could not generate code
For future use.
442. for internal macros.
INTERNAL Could not generate code
For future use.
443. for internal data definitions.
EXTERNAL
Can not Get Time. For future use.
444.
INTERNAL Error in inserting info about
For future use.
445. rule/component %s.
Server - failure to get rule
INTERNAL
and component For future use.
446.
information.
Usage - %s -l<listfile>
containing rule and
USER 447. component names For future use.
(absolute path) > -o<output
file - absolute>.
Internal AppBuilder communications error. Refer to the messages
INTERNAL Server unable to get data
448. for output.
Support.


INTERNAL Client was unable to
449. refresh the channel.
Support.
The conn layer was not Internal AppBuilder communications error. Refer to the messages
INTERNAL
initialized - cannot shut the that precede this message in the error log, and contact Customer
450.
servers in HPS 52 fashion. Support.
INTERNAL Error in calling the atomic
451. abort/shutdown.
Support.
INTERNAL Error in calling the atomic
452. commit/shutdown.
Support.
INTERNAL Invalid shutdown
453. semantics requested.
Support.
INTERNAL
Failure in shutting down. that precede this message in the error log, and contact Customer
454.
Support.
The value specified in the DNA.INI file, DNA section,
CLIENT_DNARPC_TIMEOUT variable or DNA_SERVER section,
Timed out waiting on
SERVER_DNARPC_TIMEOUT variable has been exceeded. A
EXTERNAL channel.
related client or server process may have failed. Check the client
455. System return code is = %
log if the current log is for the server. Check the server log if the
d.
current log is for a client. Check both client and server logs if the
current log is for a gateway.
EXTERNAL DCE Function %s Return
Refer to the DCE documentation for details.
456. Error: %s.
Conversion from code
USER 457. page %s to %s is not Ensure that the code pages listed in DNA.INI are valid.
supported.
Unable to determine cursor
EXTERNAL Restart the emulator session. Contact the System Administrator if
location in the 3270
458. the problem persists.
emulator, error = %d.
Unable to set the cursor
EXTERNAL location Restart the emulator session. Contact the System Administrator if
459. in the 3270 emulator, error the problem persists.
= %d.
460. Error: %s.
461. Error: %s.
User ID ------------------------
DNA Shows the current value of the status view loginName field.
> %s
WorkStation ID -------------->
DNA Shows the current value of the status view workstation field.
%s
Transaction ID ---------------
DNA Shows the current value of the status view dnaTranId field.
> %lu
Calling Rule System ID ----
DNA Shows the current value of the status view CallingRuleId field.
> %s
Target Rule System ID ---> Shows the current value of the status view targetServiceName
DNA
%s field.
Target Machine -------------- Shows the current value of the status view targetServiceName
DNA
> %s field.

General Communications Messages DNA

Target Server -------------->
DNA Shows the current value of the status view targetServerId field.
%s
Target Protocol ---------------
DNA Shows the current value of the status view targetProtocol field.
> %s
Type of Error --------------->
DNA Shows the current value of the status view dnaErrorCode field.
%ld
Error Code ------------------>
DNA Shows the current value of the status view dnaErrorCode field.
%ld
Protocol Error Code ----->
DNA Shows the current value of the status view protocolErrorCode field.
%ld
Input Data Length ---------->
DNA Shows the number of bytes in the last-used input view.
%ld
Output Data Length --------
DNA Shows the number of bytes in the last-used output view.
> %ld
Shows the last-used input data, as per settings in the DNA.INI file,
DNA Input Data ----------------> TRACING section, DEBUGLVL, DUMPDATA, and
DUMP_INPUT_SIZE variables.
Shows the last-used input data, as per settings in the DNA.INI file,
DNA Output Data --------------> TRACING section, DEBUGLVL, DUMPDATA, and
DUMP_OUTPUT_SIZE variables.
The message includes LU6.2 error and sub-error numbers. The
Error trying to allocate
remote machine may be down or the remote program may not be
conversation with LU %s,
USER 475. operating. Ensure that the LU6.2 configuration and mode profile
TP %s, error = %d,
are the same for both client and host. It is also possible that the
suberror = %d.
communication may have encountered a security restriction.
Error changing to receive The message includes error codes specific to LU6.2. The host
EXTERNAL
state, program died or a network problem occurred. If necessary, contact
476.
error = %d, suberror = %d. the System Administrator.
The message includes protocol-specific error numbers. The host
EXTERNAL Read error, error = %d,
477. suberror = %d.
Error deallocating LU The message includes error codes specific to LU6.2. The host
EXTERNAL
conversation, error = %d, program died or a network problem occurred. If necessary, contact
478.
suberror = %d. the System Administrator.
The message includes protocol-specific error numbers. The host
EXTERNAL Write error, error = %d,
479. suberror = %d.
Error disconnecting from
EXTERNAL The error includes LU6.2 error messages. If necessary, contact the
the SNA subsystem, error
480. System Administrator.
= %d.
Error connecting to the The error includes LU6.2 error messages. LU6.2 may not be
EXTERNAL
SNA subsystem, error = operational. If necessary, contact the System Administrator to
481.
%d. ensure that the system is running and is configured properly.
INTERNAL
Error generating file name. that precede this message in the error log, and contact Customer
482.
Support.
Inspect the Data_Info_t structure for each data item of type
EXTERNAL Generated file name too
MBINARY or MTEXT and ensure that the value in the
483. long for view.
Data_Occurrence field is 256.
INTERNAL
Error flushing input data. that precede this message in the error log, and contact Customer
484.
Support.
EXTERNAL IMS call %s failed with Look up the specified status code in the IMS/ESA messages and
485. status code %c%c. codes manual. If necessary, contact Customer Support.


EXTERNAL IMS fetches service Ensure that the specified service program is present and is
486. program %s failed. correctly compiled. Recompilation may be necessary.
EXTERNAL IMS opens service program
No longer in use.
487. language table failed.
EXTERNAL The dce name service The entry that associates a service route with a dcet server is
488. entry name is invalid. incorrect. Review the DCE CDS name space.
INTERNAL Error in getting the dce
489. interface specification.
Support.
INTERNAL The channel passed in is
490. NULL.
Support.
INTERNAL The transport data is
491. NULL.
Support.
EXTERNAL The dce rpc failed, error Refer to the DCE documentation for the specified DCE RPC error
492. code = %ld. number.
EXTERNAL The dce rpc failed, error Refer to Encina documentation for the specified DCE RPC error
493. code = %ld. number.
Cannot refresh from Internal AppBuilder communications error. Refer to the messages
INTERNAL
channel if using protocol that precede this message in the error log, and contact Customer
494.
%d. Support.
INTERNAL The DCE rpc binding
495. handle is NULL.
Support.
EXTERNAL Encina function %s failed:
Refer to the Encina system documentation for details.
496. %s.
EXTERNAL
%s. For future use.
497.
Start dcet_master server Informational message indicating how many instances of the dcet
INFO 498.
with instances: %d. server started as a result of your invoking boot_dcet_server.
Lock a dcet server. Informational message indicating that the specified dcet server
INFO 499.
instance id: %d. instance is in use.
Release a dcet server. Informational message indicating that the specified dcet server is
INFO 500.
instance id: %d. available.
Invoke boot_dcet_server with more instances or wait until
EXTERNAL Unable to lock a server
AppBuilder communications has released a locked server. For
501. instance.
details on server invocation, refer to Supporting DCE and Encina.
You tried to start a dcet server as a forking server, rather than
Forking servers not
USER 502. invoking boot_dcet_server. For DCE server usage, refer to
supported for protocol dcet.
You tried to start a dcet server as a multithreading server, rather
Multithreading servers not
USER 503. than invoking boot_dcet_server. For DCE server usage, refer to
supported for protocol dcet.
Server name must be
You invoked boot_dcet_server incorrectly. For DCE server usage,
USER 504. specified for DCE RPC
refer to Supporting DCE and Encina.
servers.
Server instance must be
You invoked boot_dcet_server incorrectly. For DCE server usage,
USER 505. specified for DCE RPC
refer to Supporting DCE and Encina.
server.
DCE not installed or not DCE and dcet are not supported in the release of AppBuilder
USER 506.
supported. communications installed on the machine.


INTERNAL
Failed to start transaction. that precede this message in the error log, and contact Customer
507.
Support.
INTERNAL Failed to open a network
508. channel.
Support.
INTERNAL Failed to set network
509. parameters.
Support.
INTERNAL
Callrule failed. that precede this message in the error log, and contact Customer
510.
Support.
Failed to close network
INTERNAL 511. that precede this message in the error log, and contact Customer
channel.
Support.
Entered routine
Informational message indicating the command-line switches with
INFO 512. server_Init(%d, ('%s', '%s',
which the enct server is started.
'%s', '%s'...)).
INFO %d - Entered routine
Informational message indicating the command-line switches with
INFO 513. server_Init(%d, ('%s', '%s',
which the Encina server is started.
'%s', '%s'...)).
serverid: '%s', rmname: Informational message indicating the values set in enct.conf for an
INFO 514.
'%s', dbname: '%s' enct server.
Spawning a server Informational message indicating that the AppBuilder
INFO 515.
connection thread. communications server has spawned a thread.
Invalid option %ld read for Internal AppBuilder communications error. For further details, refer
INTERNAL
exchanging control to the messages that precede this message in the error log, and
516.
information. contact Customer Support.
INTERNAL Failure in writing control
517. information type.
Failure in converting to Internal AppBuilder communications error. For further details, refer
INTERNAL
optimized control to the messages that precede this message in the error log, and
518.
Failure in converting to the Internal AppBuilder communications error. For further details, refer
INTERNAL
unoptimized control to the messages that precede this message in the error log, and
519.
A system call was Informational message indicating that the AppBuilder
INFO 520. interrupted, but the server communications server has recovered from a UNIX system-call
will continue. error mentioned in a previous message.
INTERNAL Failed to save client
521. binding.
INTERNAL Failed to %s the debug
522. data.
INTERNAL Failed to get the client code
523. page.
INTERNAL DNA Post Event %s For
524. Rule %s Failed.


Internal AppBuilder communications error. In AppBuilder, a server
Server Doesnt Support
INTERNAL cannot register, deregister, or receive an event. For further details,
Event Type Other Than
525. refer to the messages that precede this message in the error log,
Post Event.
INTERNAL Failed to initialize rule for
526. debug.
Debug can not be set for a
USER 527. For future use.
non-HPS rule.
Internal AppBuilder communications error. Each Windows or
Windows NT application must include the dna_SaveWinHandle
and dna_SaveCntxt calls. Ensure that your application does so.
Error Setting the Timer.
INTERNAL The number of running applications that use timers may exceed the
Window Handle = %d.
528. number supported by Windows or Windows NT. In that case, close
TimerID = %d.
other applications that use timers and start the application that
failed. For further details, refer to the messages that precede this
INTERNAL
The server context is null. to the messages that precede this message in the error log, and
529.
INTERNAL Error in updating the
530. storage structure.
INTERNAL server main - failure in
531. initializing static server.
EXTERNAL Port Detach Failed. Error
532. Code = %d.
EXTERNAL Port Attach Failed. Error
533. Code = %d.
EXTERNAL Message Open Failed.
534. Error Code = %d.
EXTERNAL Send Message Failed.
EXTERNAL Receive Message Failed.
Received Message Length
EXTERNAL
(%d) Is Less Than Contact the System Administrator.
537.
Expected (%d).
Invalid value %s for DNA
USER 538. Initialization File variable The value of the specified DNA.INI variable is not valid.
%s from section %s.
Invalid environment for
USER 539. MVS_SERVICE_TYPE=H No longer in use.
PS.
Service name not found in
EXTERNAL
table, Service name is Contact the System Administrator.
540.
used as PSB.
PSB name not found in
EXTERNAL
table, Service name is Contact the System Administrator.
541.
used as PSB.
EXTERNAL
IMS APSB call failed. Contact the System Administrator.
542.
EXTERNAL
IMS DPSB call failed. Contact the System Administrator.
543.


EXTERNAL
Win Sleep Failed. Contact the System Administrator.
544.
EXTERNAL Gateway timed out in
545. receiving reply from server.
EXTERNAL The onc rpc failed, error
546. code = %ld.
INTERNAL Error in initializing the
547. server context.
INTERNAL Error in getting a dna call
548. context.
contact Customer Support
INTERNAL The protocol-specific
549. context is NULL.
EXTERNAL CICS COMMAREA
550. required but not available.
Cannot pass more than
EXTERNAL
24K bytes on CICS START Contact the System Administrator.
551.
- %d requested.
INFO 552. No Trigger File Found. Informational message indicating that the trigger file is not found.
INTERNAL
Can not open events file. to the messages that precede this message in the error log, and
553.
INTERNAL No Actions Specified for
554. event %s.
Maximum simultaneous
side reactions exceeded for Informational message indicating that the maximum simultaneous
INFO 555.
the rule %s. Further side reactions were exceeded for the specified rule.
actions ignored.
Maximum event stacks
reached for the rule %s. Informational message indicating that the maximum event stacks
INFO 556.
Further Invocations were reached for the specified rule.
Ignored.
HPS Commarea is required
EXTERNAL
but the commarea pointer Contact the System Administrator.
557.
is NULL.
DIV service %s failed with
EXTERNAL
return code %x and reason Contact the System Administrator.
558.
code %x.
EXTERNAL
%s for DIV service failed. Contact the System Administrator.
559.
EXTERNAL
%s a DIV service failed. Contact the System Administrator.
560.
INTERNAL Can't find lib handle for
561. specified protocol: %s.
This is an application Informational message indicating that the server is an application
INFO 562.
server. server.
INFO 563. This is a gateway. Informational message indicating that the server is a gateway.
Executing Version 1
Informational message indicating that a version 1 component is
INFO 564. Component. Previous
being executed.
Errmessage ignored.


Security daemon failed to The local security daemon is not running or is experiencing a
USER 565.
set %s. problem. Check that the daemon is running.
Security daemon failed to The local security daemon is not running or is experiencing a
USER 566.
get %s. problem. Check that the daemon is running.
Client does not have The local security daemon is not running or is experiencing a
USER 567.
security on. problem. Check that the daemon is running.
Invalid keyword %s for
USER 568. script line beginning with An LU2 logon or logoff script used an invalid keyword.
%s.
Missing label %s specified
USER 569. A label is missing in a GOTO statement in an LU2 logon script.
in GOTO statement.
Support for protocol, %s, is
unavailable. Ensure that The specified protocol is not available. Check that the protocol
USER 570.
the correct library is library is installed correctly.
installed.
Error setting channel
EXTERNAL
option, %d. System error is Contact the System Administrator.
571.
%d.
Client version more
advanced than server Informational message indicating that the client version is more
INFO 572.
version. Requesting advanced than the server.
resend.
Client version %d more
advanced than server Informational message indicating that the client version is more
INFO 573.
version %d. Requesting advanced than the server.
resend.
Trying to send too much
The application exceeded the limit for data that can be transmitted
USER 574. data over LU2. Please use
over LU2.
a different protocol.
Failed in performing
USER 575. The DCE login information is incorrect or missing.
dce_login.
Existing DCE login expired:
USER 576. The DCE login information has expired.
%s.
Error getting DCE login
USER 577. The DCE login information is missing.
context.
Need to do dce_login at
USER 578. runtime, but we got empty The DCE login information is incorrect or missing.
DCE principal or password.
USAGE: %s -o<a/d> -
USER 579. The DNASACLT startup command syntax is incorrect.
d<dnaini path>.
Attempt to set DNAINI
EXTERNAL
environment variable to %s Contact the System Administrator.
580.
with PUTENV failed.
%s - program exit code =
INFO 581. Informational message indicating the program exit code.
%d.
Service program %s failed
getting [SMA] The DNA.INI file, SMA section, SMA_SUBCELL_TABLE variable is
USER 582.
SMA_SUBCELL_TABLE not set or is set incorrectly.
from dnaini.
Service program %s
attempted to ADD host
USER 583. You attempted to add a host that is already in the subcell table.
which already exists in
subcell table.


Service program %s
attempted to DELETE host
USER 584. You attempted to delete a host that is not in the subcell table.
which does not exist in
subcell table.
585. Service program %s
INTERNAL to the messages that precede this message in the error log, and
returned internal error %d.
This is an application
INFO 586. server - %s failed. Calling Informational message.
%s.
This is a gateway server -
INFO 587. Informational message.
%s failed, calling %s.
Receive Null View There is a problem in a control-structure array of type Data_Info_t.
USER 588.
Descriptor. For Data_Info_t usage, refer to Application Programming Interface.
The receiving program expected a view different from the view that
USER 589. Rule - View Size Mismatch. is sent. For data transmission, refer to Application Programming
Interface.
Rule Input View Size The receiving program expected an input view different from the
USER 590. Mismatch. Expected size: view that is sent. For data transmission, refer to Application
%ld, But given size: %ld. Programming Interface.
Rule Output View Size The receiving program expected an output view different from the
USER 591. Mismatch. Expected size: view that is sent. For data transmission, refer to Application
%ld, But given size: %ld. Programming Interface.
An invalid data type is specified in a control-structure array of type
USER 592. Error Data Info Type: %d. Data_Info_t. For Data_Info_t usage, refer to Application
An invalid data type is specified in a control-structure array of type
Error: Invalid Data Type
USER 593. Data_Info_t. For Data_Info_t usage, refer to Application
Detected.
EXTERNAL Invalid DNA Stratus
546. Request: %d.
EXTERNAL Unspecified Stratus Queue
547. Link Directory.
Error: Posting of event
The specified event is not posted. For global eventing usage, refer
USER 594. (name: %s, subsys: %s) to
to Application Programming Interface .
process (id: %d) failed.
Because of event post
failure, we deregistered Internal AppBuilder communications error. For further details, refer
INTERNAL
local event name: %s, type: to the messages that precede this message in the error log, and
595.
%s, subsys: %s, machine: contact Customer Support.
%s, procID: %d.
Because of event post to
INTERNAL subcell :%s failed, we
596. deregistered event name:
%s, type: %s, subsys: %s.
The local eventing agent is not available. For details on the error
EXTERNAL Error Posting Message to
code, review the documentation for the appropriate environment:
597. SVM Daemon. errorid: %d.
Presentation Manager or Windows.
EXTERNAL Not able to find SVM One of the processes associated with the local eventing agent is
598. Daemon Window. killed. Restart the agent.
Shared Memory Allocation The operating system failed to allocate memory for a specific
EXTERNAL
for sending message to message. Close any unnecessary processes and restart your
599.
svmd failed. application.
EXTERNAL The specified function failed. Consult the IMS system
%s failed on IMS.
600. documentation.


%d - MQSeries function %s
EXTERNAL
failed with completion code
601.
%d and reason code %d.
EXTERNAL %d - Invalid Implicit Event
602. View Choice: %s.
EXTERNAL %d - Invalid Implicit Event
603. Attribute: %s.
%d - Server error in
INTERNAL reading service header -
604. local C version = %lu,
remote C version = %lu.
%d - Invalid Offset
EXTERNAL Description: %s During
605. Data Dependent Routing or
Triggering.
%d - sender version 0x%x
INTERNAL
is higher than receiver
606.
version 0x%x.
INTERNAL %d - Net/security
607. initialization failure.
INTERNAL %d - Net/security data
608. manipulation failure.
%d - receiver version 0x%x
INFO 609. is higher than sender
version 0x%x.
EXTERNAL %d - Unable to enter
610. message critical section.
EXTERNAL %d - Unable to exit
611. message critical section.
EXTERNAL %d - Unable to notify the
612. Messaging Agent.
EXTERNAL %d - Unable to notify
613. messaging client of results.
EXTERNAL %d - Unable to wait for the
614. Messaging Agent.
%d - Unable to wait for
EXTERNAL
notification from messaging
615.
clients.
EXTERNAL %d - The Messaging Agent
616. is too busy.
INTERNAL %d - An invalid message
617. packet was referenced.
INTERNAL %d - An invalid message
618. request was referenced.
EXTERNAL %d - An invalid or stale
619. connection id was used.
INTERNAL %d - An unexpected packet
620. type was detected.
INTERNAL %d - An unexpected packet
621. version was detected.
%d - Unable to create
EXTERNAL
primary shared memory
622.
block.


%d - Unable to gain access
EXTERNAL
to primary shared memory
623.
block.
%d - Unable to create
EXTERNAL
messaging semaphore
624.
resources.
%d - Unable to gain access
EXTERNAL
to messaging semaphore
625.
resources.
%d - Unable to initialize
INTERNAL
memory managers for
626.
messaging.
INTERNAL %d - Unable to send
627. message remotely.
INTERNAL %d - No remote message
628. binding provided.
INTERNAL %d - No return message
629. binding provided.
%d - An unexpected
INTERNAL
messaging error has
630.
occurred.
INTERNAL %d - An invalid messaging
631. error code was reported.
%d - Problem Tracking:
INTERNAL [%s Location = %s, Code =
632. %d, Context = %ld, Line =
%d]
%d - Remote net version
INFO 633. 0x%x does not match local
version 0x%x.
%d - No Routing
USER 634. Information Found for
message target "%s".
%d - No Routing
USER 635. Information Found for
message source "%s".
%d - Client - will re-do
INFO 636.
exchange.
%d - Error trying to
EXTERNAL
allocate memory for %s,
637.
system error = %d.
EXTERNAL %d - Host %s not in
638. hierarchy.
%d - Invalid
dna_RequestService()
EXTERNAL Option Combination.
639. ONEWAY and DYNAMIC
and STATIC options are
mutually exclusive.
INTERNAL %d - One or more input
640. pointers are NULL.
INTERNAL %d - One or more input
641. arguments are invalid.


INTERNAL %d - An invalid request is
642. encountered.
EXTERNAL %d - Can't fork a child
643. process, errno: %d.
EXTERNAL %d - Can't create a pair of
644. sockets, errno: %d.
%d - Can't send a
EXTERNAL
message, system errno is
645.
%d.
%d - Can't receive a
EXTERNAL
message, system errno is
646.
%d.
EXTERNAL %d - Can't wait for a
647. socket, system errno is %d.
EXTERNAL %d - Can't read from a
EXTERNAL %d - Can't write to a
INTERNAL %d - Can't call a rule,
650. system errno is %d.
INTERNAL %d - List is corrupted,
651. system errno id %d.
%d - Entered Routine
INFO 652. dna_BoundServiceReques
t - Service %s.
%d - One or more options
USER 653.
are invalid.
%d - One or more input
USER 654.
pointers are NULL
%d - Unable to send
USER 655.
message.
%d - Invalid messaging
USER 656.
protocol.
%d - Unable to receive
USER 657.
message.
EXTERNAL
Network Input Line Trace:
658.
EXTERNAL
Network Output Line Trace:
659.
%d - Error on fork() after
EXTERNAL
%d number of retries.
660.
errno: %d.
%d -
SMA_POST_START...subc
INFO 661. ell:
%s, event name:%s,
type:%s, subsys:%s.
%d - Security API
EXTERNAL
initialization failure - error
662.
code = %d
EXTERNAL %d - Security API close
663. failure - error code = %d


EXTERNAL %d - Security API encode
EXTERNAL %d - Security API decode
%d - Error - requested to
INTERNAL decode %ld bytes but,
666. obtained %ld bytes from
the user exit.
%d - Server using a
security cookie obtained
INFO 667.
from local client
authentication exit.
INTERNAL %d - Sending Shutdown
668. Signal: %d Failed.
INTERNAL %d - Server Shutdown
669. Initiated.
INTERNAL %d - NetEssential system
670. is unable to proceed.
%d - Unable to register an
USER 671.
event.
%d - Unable to deregister
USER 672.
an event.
%d - Error Attaching to
USER 673.
Shared Memory.
EXTERNAL %d - Error Receiving
674. Event.
%d - Error Receiving Event
USER 675. Because No Registration
Found.
%d - The remote LU
rejected the allocation
request because the
USER 676.
access security information
(provided by the local
system) is invalid.
%d - Temporarily no
available server instances.
USER 677. Please reconfigure the total
number of instances in
DNA.INI.
%d - Registration from %s
USER 678.
is not in subcell table.
INTERNAL %d - %s Process %d Got A
679. Signal %d. %s
%d - Accepted connection
INFO 680.
from host ip# %s.
%d - System memory
usage exceeded %d
EXTERNAL
percent. Please free up
681.
memory before trying to
send messages.
%d - Using default value
USER 682.
"%d" for "[%s]", "%s".


%d - Error Loading
USER 683.
Performance Exit Library.
%d - Error Invoking
USER 684.
Performance Exit Library.
%d - Client specified
Logical Unit of Work Value
is invalid, must use
USER 685. 52LOCAL or
NONCONVERSATIONAL
for mainframe
communications.
%d - The maximum
USER 686. number of Registrations
has been reached.
%d - Local Event
Registration failed. Check
USER 687.
the Service Agent trace file
for more information.
EXTERNAL %d - Hostmon Initialization
688. Failed.
EXTERNAL %d - Hostmon Connect
689. failed.
EXTERNAL %d - Hostmon ShutDown
690. failed.
EXTERNAL %d - Call to create_window
691. failed.
%d -
INTERNAL
GET_TEXT_MESSAGE:
692.
Set %s not found
%d -
INTERNAL GET_TEXT_MESSAGE:
693. Message %d not found in
set %s
%d -
INTERNAL
GET_TEXT_MESSAGE:
694.
Set %s corrupt or invalid
%d - Invalid performance
USER 695. marshalling version
specified - "%s"
%d - View size limit
USER 696. exceeded for version 1 of
performance marshalling
where <qname> is the name of the MQ Series queue on which the
AB-MQ process started, MQ Listener is operating.
INFO 901.
Input-Queue is <qname>. This message informs the name of the MQ Series queue that the
MQ Listener is reading input messages from.
This message indicates if the MQ Listener will continue, waiting for
DNA_- AB-MQ process is a new message, or if it is ending. Once it ends, the next incoming
INFO 902.
{continuing|ending}. message will cause the CICS trigger monitor to (re-)invoke the MQ
Listener.

General Communications Messages INFO 903

This message indicates that the MQ Listener is committing the
updates, or if it cannot due to errors then it is rolling back the
AB-MQ is updates. If rolling back, there will be previously issued error
INFO 903 {committing|rolling back} messages indicating the failure. Note that committing does not
MQSeries operations. imply success. A commit is issued after forwarding messages from
the input-queue to the dead-letter queue - when the MQ Listener is
configured to use a dead-letter-queue.
where <tran> is the name of the CICS transaction.
AB-MQ is starting
INFO 904 This messages informs the name of the CICS transaction that the
transaction <tran>.
Listener will invoke to process the message. Typically this is PCIO.
where <qname> is the name of the MQ Series queue on which the
AB-MQ has [not] forwarded MQ Listener is operating.
message to This message informs if the MQ message was forwarded to the
INFO 905
{Process|DeadLetter}- Process queue or, in the case of errors, whether the MQ message
Queue <qname>. was forwarded to the Dead-Letter queue or not (based on DNA.INI
settings).
AB-MQ has deleted where <qname> is the name of the MQ Series queue on which the
message from MQ Listener is operating.
INFO 906
{Input|Process|DeadLetter} This message informs that the MQ Listener deleted a message
-Queue <qname>. from the specified queue.
where <userid> is the name of the userid and <rulename> is the
AB-MQ decrypted User-ID
name of the rule.
INFO 907 is <userid>, Rule is
This message informs the decrypted values of the user-ID and the
<rulename>.
rule name that the MQ Listener will use.
where <errcode> is the error code , <qname> is the name of the
MQ Series queue that the MQ Listener is operating on, and
AB-MQ sent error
<qmgr> is the name of the MQ Series Queue Manager.
(<errcode>) message to
INFO 908 This message indicates that the MQ Listener has successfully sent
client, Queue is <qname>,
an error notification message back to the client. The message was
QueueManager is <qmgr>.
sent to the queue manager and queue specified in the above
message.
INFO 909 AB-MQ No Error. F.F.U.
INFO 910 AB-MQ No Error. F.F.U.
This message indicates that the MQ Listener received an
AB-MQ cannot process encrypted/compressed message, but encryption/compression is
INTERNAL 911 message: Encryption is not not supported. As the encryption/compression is done by user-
supported/enabled. modules, the user needs to relink the MQ Listener with the
appropriate user objects with the dna_Buf*() functions.
where <id> is the ID parameter and <MQMSG> is the expected
AB-MQ Parameter Error -
parameter ID
INTERNAL 912 Invalid MQ ID: <id>,
This message indicates an internal error, as the expected protocol
expected <MQMSG>.
ID for MQ messages is MQMSG.
AB-MQ Parameter Error - where <msgid> is the MQ message ID.
INTERNAL 913 Invalid MQ MessageID: This message indicates an internal error in which an invalid MQ
<msgid>. Message ID was used as a parameter.
AB-MQ Parameter Error -
where <len> is the message length.
Invalid MQ message
INTERNAL 914 This message indicates an internal error in which a length field
length: <len>, expected a
parameter is invalid.
positive number.
INTERNAL 915 AB-MQ No Error. F.F.U.

EXTERNAL 920 Java Communications Messages

where <maxsock> is the maximum socket limit as specified in the
Reached Max-Socket
CICS TCP configuration record (EZAC).
EXTERNAL (<maxsock>) connections.
This message indicates that the TCP Listener has reached the
920 New connection requests
maximum socket limit as specified in the CICS TCP configuration
processing suspended.
record. The Listener will stop processing new connection requests.
<maxsock> is the maximum socket limit as specified in the CICS
No longer Max-Socket
TCP configuration record (EZAC).
EXTERNAL (<maxsock>) connections.
This message indicates that the TCP Listener is no longer at the
921 New connection requests
maximum socket limit as specified in the CICS TCP configuration
processing resumed.
record. The Listener will now process new connection requests.
where <func> is the failing function name and <errno> is the error
Network error:
code (errno) .
EXTERNAL Socket API call <func>
This is specific to TCP/IP. This message indicates that an
922. returned error code
unexpected error code <errno> was returned by the socket API
<errno>.
function <func>.
where <errno> is the error code (errno).
EXTERNAL Error attempting to GIVE This is specific to TCP/IP. This message indicates that an error
923. socket, errno = <errno> occurred while the Listener attempted to pass the socket to the
child server (PCIO).
where <socket> is the socket descriptor number and <errno> is the
Error attempting to TAKE error code (errno).
EXTERNAL
given socket <socket>, This is specific to TCP/IP. This message indicates that an error
924.
errno = <errno>. occurred while the child server attempted to take the socket passed
by the Listener.
where:
<prog> is the name of the WLM De/Registration program
(EZACIC12)
WLM De/Registration <rc-ch> is the error code in character format
EXTERNAL
(<prog>) returned error <rc-int> is the error code in integer format
925.
code '<rc-ch>' (<rc-int>) Currently this is specific to TCP/IP, but may be applicable to other
protocols in the future. This message indicates that the WLM De/
Registration program (EZACIC12) returned an unexpected return
code. It is displayed in character and integer format.
Java Communications Messages

Table 3-3 lists Java communications messages in numerical order
Table 3-3 Java Communications Messages

1000-1999 System error messages
1001 I/O Exception in flushing the output stream - " +
1001-1019 Buffer stream error messages
1002 I/O Exception in trying to read from input stream - " +
1003 No more data left to read in the input stream"
1004 Incomplete buffer, alignment data not found"
1005 Size mismatch in sending TEXT data"
1006 I/O Exception in reading TEXT data - "
1007 I/O Exception in reading BINARY data - "
1008 Unsupported terminal character in the TEXT data input"
1009 Size mismatch in sending BINARY data"

Java Communications Messages 1010
Table 3-3 Java Communications Messages (Continued)

1010 I/O Exception in writing TEXT data - "
1011 I/O Exception in writing BINARY data - "
1020-1029 Configuration error messages
1021 I/O Exception in reading config file -
1022 Security Exception in reading configuration information -
1023 I/O Exception in JSocket init Transport -
1024 Security Exception in JSocket init Transport -
1025 Security Exception in resolving the host IP address -
1026 Unable to find/load class -
1027 Unable to create an instance of class -
1028 Error connecting to URL: -
1030 Version mismatch on the response
1030-1039 Errors from server related messages
1031 Consistency check: Length mismatch on the response
1032 Consistency check: Checksum mismatch on the response
1033 NetEssential Error from Server: + m_ackErr;
1034 Error from Server (Web service) in XML:
1040 HpsDataException
1099 System exceptions
1100 Invalid error code
1100-1199 Internal or programming error messages
1101 Trying to flush a invalid output stream"
1102 Trying to read from an invalid input stream"
1103 Not enough space to write alignment bytes"
1104 Length mismatch in character encoding: " + enc
1105 Unsupported Encoding Exception: "
1107 Internal Error in send: object and dit(MVIEW) does not match"
1108 Internal Error in send: object length and dit occurrence does not match"
1109 unmatching array length and MIVEW occurrence! "
1110 Internal Error in recv: dit and decimal data does not match"
1111 Internal Error in recv: dit and primitive type does not match"
1121 No Such Method Exception in reading config sections - "
1122 Exception in Method reading config section - " + x.getMessage()
1123 Illegal Access Exception in reading config sections - "
1124 Bad Iterator, unable to fallback from the check point"
1125 Invalid Cookie type"
1126 Internal Error: Session is still active"
1127 Trying to inactivate a inactive Session"
1199 Internal or programming errors
1200-1299 User, settings, or usage error messages
1201 Error Opening TEXT data file: " + dataFile.getAbsolutePath() + " for Reading"
1201-1219 User errors
1202 Error in opening BINARY file: " + dataFile.getAbsolutePath() + " for Reading"

1203 Java Communications Messages

1203 Incomplete BINARY data file, unable to read"
1204 Error in getting method names in View.java - "
1205 Illegal Access Exception in getting a view child - "
1206 Exception in view.getField - " + x.getMessage()
1207 Illegal Access Exception in setting the field value - "
1208 Exception in field.setField - " + x.getMessage()
1209 NULL Reference during
1210 Invalid child view/field size
1211 Not an AppBuilder data object
1220-1229 Configuration file related messages
1221 Unable to connect to : " + fullPath.toString()
1222 Invalid URL for the Configuration file: " + fullPath
1223 Unable to read the configuration from : " + resURL.toString()
1224 Unable to locate the configuration jar file: " + cfgPath
1225 Invalid jar file name: <null>"
1226 cfgFile + " does not exist in the jar: " + inFile.getName()
1227 Unable to locate the configuration file: " + fullPath
1228 Error in reading the configuration(appbuildercom.ini) data stream: " + path
1240-1259 Configuration entries related messages
1241 Invalid NAME_SERVICE in configuration, has to be DNAINI or ROUTETBL"
1242 invalid LOG_UNIT_OF_WORK entry in configuration"
1243 invalid DEFAULT_PROTOCAL entry" // FIX ME IIOP
1244 Unsupported NetEssential code page: " + id
1245 Unable to create an instance of NetEClientExit class " + value
1246 Class Not Found Exception in loading NeteClientExit - "
1247 Illegal Access Exception in NeteClientExit - "
1248 invalid PROTOCAL entry in route table: " + tempStr
1249 Router file name is not set"
1250 Error in getting the router info's input stream: " + path
1251 I/O Exception in reading route information - "
1252 Unable to locate the route information for Service: " + svcName
1253 Java Character Encoding not defined for code page: " + serverCP
1260s, 1360s Session related messages
1261 self-reference detected in parameters."
Default session could be used only for Non-Conversational mode; create a
1262
Session object to make service request"
1264 Unknown host: " + m_currRoute.getHost()
1270s, 1370s Overlay related messages
1271 Error creating a trace file in the local cache: "
1271-1274 Trace file related messages
1272 Error in opening trace file: "
1273 Security exception when trying to read system property
1275 Input data size too big for the byte buffer, truncating...

Interpreting Third-party Error Numbers 1299

1299 User, settings, or usage error
1300-1399 Information messages
1363 Client side validation failed for this request"
1365 Unsupported protocol: {0}
1366 Exhausted all possible routes, unable to connect for Service: {0}
1376 Output view too small for the byte buffer, truncating...
1377 Overlay supported only for AppBuilder applications
1399 Information
Interpreting Third-party Error Numbers

In some cases, the messages identify an error number from a third-party compiler, protocol, or
operating system. Among the documents that contain information on third-party error numbers are:
For LU6.2, the IBM Systems Application Architecture Common Programming Interface
Communications Reference.
For LU2, the IBM Communications Manager/2 EHLAPPI Programming Reference.
For TCP/IP on OS/2, the IBM Transmission Control Protocol/Internet Protocol Version 2.0 for OS/2:
Programmers Reference.
For UNIX environments, the system-specific Programmers Reference Manual, Section 2.
Handling Unresolved UNIX Symbols

AppBuilder communications error reporting varies across UNIX platforms when a library does not
export a symbol that a service DLL needs:
On the server side, an AppBuilder communications error message is reported on AIX only. The text of
the message is:
DNA_EXTERNAL 177. Error loading dynamically - file %s. Exec format error.
The unresolved symbol is not identified.
On SunOS and HP-UX, no AppBuilder communications error message is reported; the unresolved
symbol is reported and identified on stderr only.
On the client side, for all UNIX platforms, the communications error message reads:
Network read error due to severed connection.

CHAPTER
4 ENTERPRISE DEVELOPMENT
MESSAGES (PART 1)
This section lists messages you may encounter when developing an application in an enterprise
(mainframe) environment.
Note In this document, enterprise and mainframe are used interchangeably.
Enterprise Development Messages - Part 1

Table 4-1 lists enterprise development messages from DB2000E to HLM1. Messages from HMR001E to
XWU012I are listed in Chapter 5, Enterprise Development Messages (Part 2).
Table 4-1 Enterprise Development Messages - DB2000E through HLM1
Code Text Description and Recommended Action

Review the other messages that are displayed with this message. Review the SQL
code and determine the best course of action depending on the severity of the SQL
An error has occurred attempting to code, your system configuration and the resources specified in the messages.
DB2000E
access DB2 data. Contact your AppBuilder System Administrator if you feel that the AppBuilder
repository application is in question. Retry the operation later if the resource
specified is temporarily unavailable.
Review the other messages that are displayed with this message. Review the SQL
code and determine the best course of action depending on the severity of the SQL
code, your system configuration and the resources specified in the messages.
DB2001E Invalid SQL code returned
Contact your AppBuilder System Administrator if you feel that the AppBuilder
repository application is in question. Retry the operation later if the resource
specified is temporarily unavailable.
Error deleting CRC value in table. An error occurred while attempting to delete the CRC value in a table. Review and
DB2002E
SQL code: %1 correct the delete request.
An error occurred while attempting to delete from the specified table. Review and
DB2003E Error Deleting from %1 table.
correct the delete request.
An error occurred while attempting to select from the specified table. Review and
DB2004E Error Selecting from %1 table.
correct the select request.
An error occurred while attempting to insert into the specified table. Review and
DB2005E Error Inserting into %1 table.
correct the insert request.
An error occurred while attempting to update the specified table. Review and
DB2006E Error Updating %1 table.
correct the update request.
A DB2 COMMIT error occurred during program execution. Review and correct the
DB2007E DB2 COMMIT error occurred
DB2 COMMIT request.
A DB2 ROLLBACK error occurred in the execution of the program. Review and
DB2008E DB2 ROLLBACK error occurred
correct the DB2 ROLLBACK request.
DB2 ERROR, The program will be
DB2009E Review and correct the DB2 error.
terminated

Enterprise Development Messages - Part 1 GA0001I
Table 4-1 Enterprise Development Messages - DB2000E through HLM1 (Continued)

This message indicates the processing options that were selected. The following
GA0001I Processing Options selected:
messages list those options.
GA0002I User Id . . . . . . . . . . . . : %1 The specified user ID is a selected processing option.
GA0003I Entity Type . . . . . . . . . . : %1 The specified entity type is a selected processing option.
GA0004I Migration Id . . . . . . . . . : %1 The specified migration ID is a selected processing option.
GA0005I Migration Name . . . . . . . . : %1 The specified migration long name is a selected processing option.
GA0006I Version . . . . . . . . . . . . : %1 The specified version is a selected processing option.
Unable to delete any data which
The attempt to delete data from the specified table for the indicated migration is not
GA0007E may exist in table %1
successful. Review and correct your request for the deletion from the table.
for Migration %2 .
Unable to insert %1 %2 for The attempt to insert the specified data for the indicated migration is not successful.
GA0008E
Migration %2. Review and correct the migration attempt as appropriate.
The attempt to retrieve the specified module is unsuccessful. Review and correct
GA0009E Unable to retrieve module %1.
the retrieve module request.
Unable to retrieve long name for %1 The long name for the specified entity could not be retrieved. Review and correct
GA0011E
%2. the retrieve request.
The cursor for the specified table is not defined. Review and correct the table
GA0012E Unable to define cursor for table %1.
specification and/or cursor definition.
An error occurred when attempting to open the cursor for the specified table.
GA0013E Unable to open cursor for table %1.
Review and correct the open cursor for table request.
Unable to retrieve entities marked
The attempt to retrieve entities marked for rebuild is unsuccessful for the specified
GA0014E for rebuild for Migration %1, version
migration and version. Review and correct the retrieve entity rebuild request.
%2.
No entities marked for rebuild for The request to rebuild for the specified migration cannot be completed because no
GA0015I
Migration %1, version %2. entities were marked. Select the entity to be rebuilt, and repeat the command.
An error occurred when attempting to close a cursor for the specified table.
GA0016E Unable to close cursor for table %1.
Examine and correct the request to close the cursor for the table.
Unable to retrieve hierarchy for
The entity hierarchy marked for rebuild cannot be retrieved. Review the specified
GA0017E entities marked for rebuild, reason
return code and correct the request.
code %1.
Program to determine the scope of In determining the scope of the rebuild if the specified migration is imported, the
GA0018I rebuild, if Migration %1 is imported, program analyzing the process received the indicated return code. Evaluate the
ended with return code %2. return code, and adjust the import process.
Unable to determine which entities
A roll-up analysis failure prevented determining which entities were marked for
GA0019E are marked for rebuild due to failure
rebuild. Examine the return code and correct the failure.
in roll-up analysis, reason code %1.
An invalid action is detected when the first item is passed to the second item.
GA0020E Invalid action - %1 passed to %2.
Review the action, and correct the failure.
Analyze Entities and Relations for
GA0024I The Analyze job for the specified migration began at the specified time.
%1(%2), Version %3 started at %4.
The Analyze job for the specified migration completed successfully at the specified
GA0025I %1(%2), Version %3 ended
time.
successfully at %4.
GA0026I %1(%2), Version %3 ended with The Analyze job for the specified migration completed at the specified time.
errors at %4.
Delete Relations for %1(%2),
GA0027I The Delete Relations job for the specified migration began at the specified time.
Version %3 started at %4.
The Delete Relations job for the specified migration completed successfully at the
GA0028I Version %3 ended successfully at
specified time.
%4.
Delete Relations for %1(%2), The Delete Relations job for the specified migration completed with errors at the
GA0029I
Version %3 ended with errors at %4. specified time.
4-2 Enterprise Development Messages (Part 1)

GA0030I Enterprise Development Messages - Part 1

Collision found on %1 having A collision is detected on the specified item, which has the indicated long name.
GA0030I
Longname %2. Review and correct any error with the named items designated.
Collision found on %1 having A collision is detected on the specified item with the indicated system ID. Review
GA0031I
System ID %2. and correct any error with the named items designated.
The specified delete relations operation is terminated as shown. No relations were
GA0032I Version %3 ended at %4. There
found that could be checked.
were no relations to check.
Object %1, MigUid %2, is not
Because the object encountered is not defined for the platform, it is discarded.
GA0033E defined on platform %3. It will be
Review and ascertain your need and use for the object.
discarded.
Parent of migration is not in Because the parent of migration is not located in the migration, the relation is
GA0036E
Migration. Relation discarded. discarded. Review and correct the migration relationships.
Child of migration is not in Migration. Because the child of migration is not located in the migration, the relation is
GA0037E
Relation discarded. discarded. Review and correct the migration relationships.
GA0038I Project . . . . . . . . . . . . : %1 This information message identifies the project.
Analyze Collisions for %1 (%2) The collision-detection portion of the Analyze process for migration started at the
GA0039I
Version: %3 started at %4. specified time.
Analyze Collisions for %1 (%2)
The collision-detection portion of the Analyze process for migration ended at the
GA0040I Version: %3 ended successfully, no
specified time, with no collisions found.
collisions were found, at %4.
Analyze Collisions for %1(%2)
The collision-detection portion of the Analyze process for migration ended at the
GA0041I Version: %3 ended with errors at
specified time, with errors. See additional messages.
%4.
Analyze Collisions for %1 (%2) The collision-detection portion of the Analyze process for migration ended at the
GA0042I Version: %3 ended successfully, specified time. If the use of duplicate names is acceptable, continue; otherwise,
however collision was found change the names of the system IDs.
Rebuild Detector for %1 (%2),
GA0043I
version %3 started at %4 %5.
GA0044I version %3 ended successfully at
%4 %5.
GA0045I version %3 ended with errors at %4
%5.
Analyze is detecting invalid
condition of delete for Entity %1.
GA0046E The Migration files are missing an
entry for this item. Processing will
terminate.
Rebuild Detector found invalid
GA0047E object type. The object type %1 is
non-preparable.
Entity %1 %2(%3) has changed and
GA0048I
needs to be prepared.
Entity %1 %2(%3) needs to be
GA0049I prepared, because one of its
children has changed.
Data record is missing from the %1
GA0050E file. Logkey pointer of INMIG file
record is %2.
Invalid data format from the %1
GA0051E file.logkey pointer of record in INMIG
file is %2.

Enterprise Development Messages - Part 1 GA0052E

Invalid data format from %1 file.
GA0052E Logkey pointer of record in INMIG
file is %2.
Unable to get confirmation The expected confirmation message, message ID, and message text were not
GCCF00E
message, message ID %1 received.
Unable to Fetch Variable %1. RC =
GCFV00E The attempt to fetch the specified REXX variable is unsuccessful.
%2.
GCL000I Clean-up program started at %1 %2. The migration clean-up program started at the specified time.
Clean-up program ended The migration clean-up program ended at the specified time after cleaning up the
GCL001I
successfully at %1 %2. selected processes.
GCL002I Clean-up program failed at %1 %2. The migration clean-up program failed. Check the errors and restart that program.
Unable to Set Variable %1 with An error occurred when attempting to set the specified REXX variable with the
GCSV00E
value %2. RC = %3. indicated value. Correct the set variable request.
Object %1 is NOT defined in The requested object is not defined in the specified release. Review and correct the
GC0002E
Release %2 request.
Model/Release %1 is NOT The specified model and release of the System are not supported in this
GC0003E
supported environment. Review and correct the references to the correct specification.
Property %1 is NOT supported for The specified property is not available for the specified object in this release of the
GC0004W
Object %2 in Release %3 System. Correct your request.
Unable to fetch program %1 for The attempt to fetch the specified data-dictionary program for this release of the
GC0005E
Release %2. System is unsuccessful. Review and correct the fetch request.
EOF on file %1 while reading An EOF is received while reading the header of the specified file. Review and
GC0006E
header correct the file header read request.
Error on file %1 while reading An error occurred while reading the header of the specified file. Review and correct
GC0007E
header. the file header read request.
Logical key pointer %1, not found in The specified logical key pointer is not located on the file. Verify the file and pointer
GC0008E
file. to be read.
Requested data length to be read is
An attempt to read data is unsuccessful because the data length is greater than the
GC0009E too large. Requested size %1
maximum size. Review and correct the file read request.
Maximum Size %2.
EOF on file %1 when trying to read An attempt to read a specific amount of data is unsuccessful because an EOF is
GC0010E
%2 bytes encountered. Review and correct the file read request.
Error on file %1 when trying to read An attempt to read a specific amount of data is unsuccessful because an error is
GC0011E
%2 bytes encountered. Review and correct the file read request.
Error on file %1 when trying to write An error is detected on the specified file when attempting to write the indicated
GC0012E
%2 record record. Review and correct the file write request.
Error on file %1 when trying to write An attempt to write a record is unsuccessful because an error is detected on the file.
GC0013E
record Review and correct the file write request.
CRUD processing ended with error
The CRUD request is unsuccessful and returned the specified return code. Review
GC0014E return code %1, when performing
and the correct the error reported.
the %2 action for systemid %33
PSB source is present in Migration, A mismatch is detected: a PSB (program specification block) source is present in
GC0015W although IMS is not installed on migration, but IMS is not installed on this repository. Review and reconcile the
repository. inconsistent parts of this request.
Source object is not found in source The source object is missing from the source version of the migration. Review and
GC0016E
version (V: %1) of Migration. supply the missing source object.
Text object is not found in source The text object is missing from the source version of the migration. Review and
GC0017E
version (V: %1) of Migration. supply the missing text object.
Keyword object is not found in The keyword object is missing from the source version of the migration. Review and
GC0018E
source version (V: %1) of Migration. supply the missing keyword object.
EOF on file %1 when trying to read An unexpected EOF is detected on the specified file while attempting to read the
GC0019E
next record. next record. Examine and correct the file read operation.

GC0020E Enterprise Development Messages - Part 1

Error on file %1 when trying to read An error occurred on the specified file while trying to read the next record. Examine
GC0020E
next record. the error and correct the file read request.
EOF on file %1 when trying to read An unexpected EOF is encountered on the specified file while trying to read the file
GC0021E
file header. header. Examine and correct the file read request.
Error on file %1 when trying to read An unexpected error is detected on the specified file when trying to read the file
GC0022E
file header. header. Examine and correct the file read request.
Error reading Row Header An unexpected error is detected on the specified file when trying to read the row
GC0023E
information on file %1. header. Examine and correct the file read request.
An error is detected in parsing an INMIG record. Review and correct the INMIG
GC0024E Error occurred parsing Inmig record
record.
An error occurred while parsing a row record. Review and correct the row record
GC0025E Error parsing row record.
request.
An error occurred while parsing an entity logical key record. Review and correct the
GC0026E Error parsing Ent LogKey record.
logical key record.
An error occurred while parsing an relationship logical key record. Review and
GC0027E Error parsing Rel LogKey record.
correct the record.
Error occurred when executing pgm
GC0029E An internal error occurred. Contact your local System Administrator.
hmpbndx.
An internal error occurred. The action to be processed is invalid. Contact your local
GC0030E Invalid action - %1 passed to %2.
Definition for entity type %1 is not An internal error occurred. The explode program cannot locate the entity type.
GC0031E
found. Contact your local System Administrator.
An internal error occurred. The CRC control value does not exist for the specified
GC0032E CRC value missing for %1.
object. Contact your local System Administrator.
Drawing file is longer than expected.
Expected length %1, length returned
GC0033E An internal error occurred. Contact your local System Administrator.
from Source Text Keyword CRUD
%2.
Update of %1 object, systemid %2,
GC0034I An internal error occurred. Contact your local System Administrator.
ended at %3 - Return Code = %4.
The text associated with migration could not be processed. If no text exists for this
Error processing MIGRTN text for
GC0035E systemid, contact the objects owner. A negative return code is a DB2 error code
systemid: %1. Return Code = %2.
that reflects a problem in accessing the repository; check the IBM documentation.
Collisions found in migration, and
your configuration considers
A collision is found during Analyze. You must respond to the messages in the
GC0036E collision an error. Check message
message file before processing can continue.
file for objects where collisions are
found.
Error trying to add text object to An error occurred when trying to add text to the repository. Contact your local
GC0037E
version %1. System Administrator.
Error trying to add source object to An error occurred when trying to add source to the repository. Contact your local
GC0038E
Error trying to add keyword object to An error occurred when trying to add keywords to the repository. Contact your local
GC0039E
Error trying to add reltext object to An error occurred when trying to add relations text to the repository. Contact your
GC0040E
version %1. local System Administrator.
Error trying to add binary source An error occurred when trying to add binary source to the repository. Contact your
GC0041E
object to version %1. local System Administrator.
Error during CRUD operation, An internal error occurred when trying to create, read, update, or delete a record.
GC0042E
Return Code = %1 Contact your local System Administrator.
Error invoking REXX CRUD for %1 An internal error occurred when trying to access information from the REXX
GC0043E
%2 Return Code= %3. variable pool for the specified object. Contact your local System Administrator.

Enterprise Development Messages - Part 1 GC0044E

ERROR - when deleting from %1
GC0044E A DB2 error occurred when trying to delete rows from the specified table.
table.
Format error on audit block of file An audit-block eyecatcher is not found during processing of the audit record. This
GC0045E
%1, beginning eyecatcher not found usually indicates that the data file is incorrect.
Format error on audit block of file An audit-block eyecatcher is not found during processing of the audit record. This
GC0046E
%1, terminal eyecatcher not found usually indicates that the data file is incorrect.
Invalid MetaType, SOURCE, TEXT,
GC0047E KEYWRD was expected. %1 found
in %2.
GC0048E Record:%1
GC0049E Reason:%1
GC0050E Error deleting record from file %1
Error processing %1 file, searching
GC0051E
for MetaId: %2, found MetaId: %3.
Error on file DETAIL when trying to
GC0052E
write record.
GC0053R Open ERROR
GC0054R Write ERROR
GC0055R Close ERROR
GC1001E Invalid number of input parameters
Error in generating Migration entity
GC1002E
system id
Error in creating Migration entity,
GC1003E
system id %2
Error trying to get seeds for
GC1004E migration (OPEN):systemid %1,
process id %2
GC1005E migration (FETCH): system id %1
process if %2
GC1006E migration (CLOSE): system id %1
process if %2
Error in creating Migration
GC1007E Relation,ParentSystemid %1
ChildSystemid %2
Error in deleting migration seeds,
GC1008E
systemid %1
GC1009E Error in setting RQST variable
GC1010E Error in opening file, DD name %1
Error in writing RMIRQST file,error
GC1011E
no %1
Error in opening file, DD name %1
GC1012E
memname %2 errorno %3
Error in updating Job_status table,
GC1013E
process id %1
GC1020E Socket Error Accept : errmsg %1
GC1021E Socket Error Receive : errmsg %1
Error in allocating input buffer, size
GC1022E
%1
GC1023E Socket error Send : errmsg %1

GC1024E Enterprise Development Messages - Part 1

Error in creating migration seeds,
GC1024E
process id %1
Error in commiting database,
GC1025E
process id %1
GC1026E Error in allocating Query Buffer
Error in selecting job status detail,
GC1027E
process id %1
GC1028E Error in allocating Job status buffer
Error trying to get result files
GC1029E
(OPEN):,process id %1
GC1030E
(FETCH):,process id %1
GC1031E
(CLOSE):,process id %1
GC1032E Socket error Socket : errmsg %1
GC1033E Socket error Bind : errmsg %1
GC1034E Socket error Listen : errmsg %1
Error in Dynamic allocaion
GC1035E initialization, errcode %1 infocode
%2
Error in Dynamic allocaion INTRDR,
GC1036E
errcode %1 infocode %2
GC1037E Error trying to get process id
Error in creating job status, process
GC1038E
id
GC1039E Usage: %1 port
GC1040R Communication_OK
GC1041R Login_Failed
GC1042R Login_Successful
GC1043R Error_in_Submitting_Upload
GC1044R Error_in_getting_jobstatus
GC1045R Error_in_Submitting_Download
GC1046R Row does not exist
User_does_not_have_access_to_th
GC1047R
e_version
GC1048R Error_in_querying_objects
GC1049R Unknown_operation
GC1050R Invalid_version
GC1051R Repository_does_not_exist
GC1052R Authorization_error_project_version
GC1053R Job_status_not_found
GC1054R Invalid_Entity_type
GC1055R Invalid_scope_type
GC1060E Error on %1 for Call Attach Facility
DB2 found FORCE,ABTERM, shut
GC1061E
down for CAF action %1.
Found a mismatch between DB2
GC1062W
and CAF release levels.

Enterprise Development Messages - Part 1 GC1063E

Found unexpected error on CAF
GC1063E
action %1.
GC1064E DB2 is unavailable.
Warning: DB2 connection failure.
GC1065E Cause unknown. SqlCode %1 on
CAF action %2.
An unknown service has been
GC1066E
returned for CAF action %1.
CAF found user error on CAF action
GC1067E
%1. See DSNTRACE dataset.
CAF system error on CAF action
GC1068E
%1. See DSNTRACE dataset.
GC1069E %1 %2
Error in Allocating % data set,retcc
GC1070E
%2
GC1071E Allocation_error
User %1 does not have access to
GC1072E
the project %2 & version %3
GC1073R Archetype_Model_is_not_supported
GC1074R Security_Model_is_not_supported
GC1075R Error_in_opening_db2_connection
GC1076E Invalid number of bytes received
Error in connecting to db2
GC1077E
subsystem %1
Error in Opening Db2 connection,
GC1078E
subsystem %1 plan %2
GC1079E Error in Closing Db2 connection
GC1080E Error in fetching load module %1
GC1081R DB2_error._Check_mainframe_log
GC1082E DB2 error occurred. Error code : %1
Error in initializing REXX ini
GC1083E
variables
Error in getting Control number:
GC1084E Control name %1 ess if
%2
Error in updating Control number:
GC1085E Control name %1,control no %2
ess if %2
GC1086R Server tables are already Created.
Server has SHUTDOWN
GC1087W
successfully.
Migration cleanup utility, version %1
GC1100I
started at %2
GC1101I
ended successfully at %2
GC1102I
failed at %2
Total number of migration entities
GC1103I
processed : %1
GC1104I Migration creation start date : %1

GC1105I Enterprise Development Messages - Part 1

GC1105I Migration creation end date : %1
GC1106I Migration partial long name : %1
Processed Migration Entity
GC1107I
(longname) : %1
Entity Type %1, %2 is missing from The specified entity type (%1) and name (%2) were not found in the DB2 table.
GE0000E
the %3 Table. Correct the problem.
No Seeds to process for Migration No seeds to process were found in a migration attempt. Review and correct the
GE0001E
%1. missing seeds for this migration.
There are no preparable objects
You have requested the export of preparable objects configured for the PC, but no
GE0002E configured for the PC platform in
such objects exist.
Rebuild Package %1(%2).
Error code - %1 returned from The CRUD routine detected a problem and returned the specified error code.
GE0003E
CRUD routine. Review the error and correct the operation.
An error occurred when a specified relation is missing from the indicated table.
GE0004E CRC value missing for %1.
Review and correct the missing relation.
%1 for %2 has 0 data length. %3 will The specified item has a data length of zero. Consequently, the export cannot
GE0005E
not be Exported. continue. Review and correct the data length and the request for export.
Attempt to explode using an invalid An attempt to explode failed because of the specified invalid scope. Review and
GE0006E
scope. Scope=%1. correct the scope specified.
Attribute section is too long to be The query entered on selective export is too complicated to be processed. Simplify
GE0007E
processed by Selective Export. the query by removing the number of attributes.
Export has resulted in zero objects No rows resulted from export. Review the export criterion and resubmit the export
GE0008E
for %1 processing. job.
Ensure the relation exists in the repository. The message includes a DB2 return
GE0009E Error trying to export %1. RC=%2.
code, as described in IBM documentation.
The specified object cannot be exported because the DB2 data row for that object is
GE0010E DB2 Data Row not found for %1. missing. Export is terminated. To correct the error, add the object back to the
repository.
Export %1 %2 (%3), Version %4 The specified Export migration job for the designated version began at the indicated
GE0021I
started at %5. time.
Export %1 %2 (%3), Version %4 The specified Export migration job for the designated version ended successfully at
GE0022I
ended successfully at %5. the indicated time.
Export %1 %2 (%3), Version %4
GE0023I The Export job for the designated entity ended with errors at the indicated time.
ended with errors at %5.
This error occurred either because of contention on the database management
system or because of an error in the repository. In the former case, wait until the
Error trying to retrieve child entity for
GE0024E other user is no longer accessing the entity. In the latter case, check the relations
relation %1. RC = %2.
and ensure that the child exists in the repository. A negative return code is a DB2
error, as described in IBM documentation.
GE0025I User supplied input parameters.
GE0026I Entity Type . . . . . . . . . . . . .:%1.
GE0027I Entity's Name . . . . . . . . . . . .:%1.
GE0028I Entity's System ID . . . . . . . . . .:%1.
GE0029I Source Version . . . . . . . . . . . .:%1.
GE0030I Target Version . . . . . . . . . . . .:%1.
GE0031I User ID . . . . . . . . . . . . . . .:%1.
GE0032I Project . . . . . . . . . . . . . . .:%1.
GE0033I Method ID . . . . . . . . . . . . . .:%1.
GE0034I Process Text . . . . . . . . . . . . .:%1.
GE0035I Process Source . . . . . . . . . . . .:%1.

Enterprise Development Messages - Part 1 GE0036I

GE0036I Process Keywords . . . . . . . . . . .:%1.
GE0037I Selective Export . . . . . . . . . . .:%1.
Migration Release Level . . . . . .
GE0038I
.:%1.
GE0039I Fastpath Migration . . . . . . . . . .:%1.
GE0040I Data Set Prefix . . . . . . . . . . .:%1.
%1 for Relation %2 Parent:%3 (%4)
GE0041E Child:%5 (%6) has zero data length.
%7 will not be exported.
ERROR - When getting count
GE0042E
Migration Seeds.
GE0043I Global Migration Options.
GE0044I Repository Name . . . . . . . . . . .:%1.
GE0045I Results to File . . . . . . . . . . .:%1.
GE0046I Count Report . . . . . . . . . . . . .:%1.
GE0047I Detail Report . . . . . . . . . . . .:%1.
GE0048I %1 is not found in Repository.
Object %1 %2 (%3) has been The specified object cannot be imported because it is changed since the Analyze
GI0001E changed since Analyze. It will not step. Review the object status, and verify which operation needs to be performed.
be imported. Analyze assigns import values; if you change the object, you must reanalyze.
The specified relation cannot be imported because it has changed since the
Relation %1 %2 %3 %4 %5 (%6) Analyze step. The error message includes (in order) the parent type, parent id,
GI0002E has been changed since Analyze. It relation type, child name, and child type. Analyze assigns import values; if you
will not be imported. change the object, you must re-run Analyze. Review the relation status and verify
which operation needs to be performed.
Error Importing %1 %2 (with An error occurred attempting to import a specified item with the short name
GI0003E
shortname %3). indicated. Review and correct the import request.
Unable to import %1 for %2, the An error occurred attempting to import a specified item. Review and correct the
GI0004I
object has a length of zero. import request.
Import migration for %1(%2),
GI0005I Import migration began.
GL0006I Version %3 ended successfully at Import migration ended successfully.
%4.
GL0007I Import migration ended with errors.
Version %3 ended with errors at %4.
Error setting Import status in
GI0008E subroutine %1. Processing is An internal error occurred. Contact your local System Administrator.
terminated.
Error setting Import status for %1
GI0009E Object Type:%2. Processing is An internal error occurred. Contact your local System Administrator.
terminated.
Keyword data for %1 has a length of
%2, which is longer than the
GI0010E An internal error occurred. Contact your local System Administrator.
maximum allowable length for the
Main Frame Repository.
Error in trying to skip keywords for
GI0011E An internal error occurred during import. Contact your local System Administrator.
%1. Processing is terminated.
There are no parts (DB2 row, Text,
GI0012E Source, Keywords) to be imported
for %1.

GI0013E Enterprise Development Messages - Part 1

Relation create failed because child
GI0013E entity was not exported due to
selective export criterion.
Source Repository cannot be found,
GI0015E and user has requested Import
without files.
Relation create failed because
GI0016E parent entity was not exported due
to selective export criterion
Unable to obtain %1 for Target An error occurred attempting to obtain the specified value for the target relation
GL0000E
relation record. record. Review and correct the request.
Property %1 did NOT exist for object
During migration from another platform or release, a default value is being assigned
GL0001W %2 in source repository release %3
for an object property that is not present in the target environment.
and is being defaulted to %4.
Migration has root Migration is not The current migration release does not support migration that has migration as the
GL0002E
supported in Release %1. root entity. Remove the root entity from the migration list.
Error occurred when retrieving value The program cannot get the default properties from the target repository. Contact
GL0003E
from the Target Repository. your System Administrator.
Error occurred: INMIG File doesn't An error occurred attempting to use the INMIG file having no data records.
GL0020E
have any data records. Reevaluate and correct the file request.
Analyze Load Migration for %1(%2),
GL0021I The process to analyze the specified load migration started at the designated time.
Analyze Load Migration for %1(%2),
The process to analyze the specified load migration ended successfully at the
GL0022I Version %3 ended successfully at
designated time.
%4.
Analyze Load Migration for %1(%2), The process to analyze the specified load migration ended with errors at the
GL0023I
Version %3 ended with errors at %4. designated time.
CSD level of Migration files is
different from Repository. CRC
GL0024I
values for Entities and Relations will
be recalculated.
Migration files are coming from a
Repository having different Release
level than the Target Repository.
GL0025I Level of Migration files: %1 Level of
Target Repository %2. This will
result in a recalculation of CRC
values.
Data record length of %1 in
GL0026E Migration file %2 does not match the
expected length of %3.
Loading incorrect value for data field
GL0027E %1 in Migration file %2. Data record
is: %3.
The specified method type is not recognized. Review and correct the method type
GR0001E Unrecognized method type %1.
request.
Rebuild Analyze was run
successfully by %1 on %2 at %3. The attempt to run the rebuild analyze step is successful, and no exceptional
GR0002I
NO exceptional processes were processes were found.
found.
Rebuild Package %1, Version %2
The specified rebuild package had no seeds. You must use the ADDR HIRISE
GR0003E has no seeds. Use ADDR HIRISE
method to provide the seeds.
method to add seeds.
The specified rebuild package improperly seeded. You must use the ADDR HIRISE
GR0004E has not been seeded correctly. Use
method to correct the seeding.
ADDR HIRISE method to correct it.

Enterprise Development Messages - Part 1 GR0005I

Rebuild Analyze for Rebuild
Package %1, Version %2 is The rebuild analyze program is presently running for the identified rebuild package.
GR0005I
currently running. It was started by The message description also shows where and when the process is started.
%3 on %4 at %5.
Rebuild Analyze for Rebuild
The attempt to start the rebuild analyze program for the specified rebuild package is
Package %1, Version %2 cannot be
GR0006I unsuccessful. Consequently, one of the phases following it is started. Review and
initiated. One of the phases
correct the rebuild package before starting the Rebuild Analyze again.
following it has been initiated.
Rebuild Analyze was run The rebuild analyze program for the specified rebuild package executed
GR0007I successfully by %1 on %2 at %3. successfully. But exceptional processes were found. Review and analyze the
Exceptional processes were found. rebuild analyze process to determine if the results are acceptable.
entity has not been defined The identified rebuild package is not defined successfully. Use the ADDR HIRISE
GR0008E
successfully. Use ADDR HIRISE method to correct the definition of the rebuild package.
method to correct it.
ERROR - when committing changes An error is detected when attempting to commit changes to status for the specified
GR0009E to status for Rebuild Package %1, rebuild package. Review and correct the rebuild package before committing
Version %2. changes to status again.
ERROR - Rebuild Package has An invalid status error is detected when examining the rebuild package. The current
GR0010E
invalid status. Current status is %1. status is shown. Review and correct the invalid rebuild package status.
ERROR - Rebuild Analyze has not An error is detected as a result of the rebuild analyze process not being properly
GR0011E
been initiated properly. initiated. Review and correct the rebuild analyze process.
ERROR - Rebuild Prepare has not An error is detected as a result of the rebuild prepare process not being properly
GR0012E
been initiated properly. initiated. Review and correct the rebuild prepare process.
Rebuild Prepare for Rebuild
Package %1 Version %2 finished The rebuild prepare for the specified rebuild package completed successfully. Also
GR0013I
successfully. It was submitted by %3 noted is information regarding when and by whom it is submitted.
on %4 at %5.
Package %1 Version %2 is currently The rebuild prepare for the specified rebuild package is now running. Also noted is
GR0014I
running. It was started by %3 on %4 information regarding when and by whom it is submitted.
at %5.
The rebuild prepare for the specified rebuild package is not started. Also the rebuild
Package %1 Version %2 cannot be
GR0015E analyze process has not ended successfully. Review and correct the rebuild
initiated. Rebuild Analyze has not
processes.
finished successfully.
Package %1 Version %2 cannot be The rebuild prepare for the specified rebuild package is not started. Also one the
GR0016E
initiated. One of the phases phases following it is started. Review and correct the rebuild processes as required.
following it has been initiated.
ERROR - when selecting objects for An error is detected while selecting objects for a prepare. Review and correct the
GR0017E
prepare. objects being prepared.
ERROR - when getting count of An error is detected while attempting to count the number of failed prepares.
GR0018E
failed prepares. Review the request and request the count again.
ERROR - when getting status of An error is detected while attempting to get the status of the specified rebuild
GR0019E
Rebuild Package %1, Version %2. package. Review and correct the status request.
Verify successful. Status of Rebuild
The verify request is successful. The status of the specified rebuild package is now
GR0020I Package %1 Version %2 is Rebuild
Rebuild Seed Redefine Submitted.
Seed Refine Submitted.
Rebuild Analyze Submitted.
Analyze Submitted.
Rebuild Analyze Submitted.
Prepare Submitted.

GR0024I Enterprise Development Messages - Part 1

Rebuild Install Submitted.
Install Submitted.
Attempt was made to select objects The attempt to select objects for prepare in background is not allowed and,
GR0025E for prepare in background, which is therefore, unsuccessful. Review and correct your request to select objects for
not allowed. prepare.
Verify successful. Rebuild Seed
The verify request is successful. Now you can start the Rebuild Seed Redefine for
GR0026I Refine for Rebuild Package %1
the specified rebuild package.
Version %2 can be initiated.
Verify successful. Rebuild Analyze
The verify request is successful. Now you can start Rebuild Analyze for the
GR0027I for Rebuild Package %1 Version %2
specified rebuild package.
can be initiated.
Verify successful. Rebuild Prepare
The verify request is successful. Now you can start Rebuild Prepare for the
GR0029I for Rebuild Package %1 Version %2
specified rebuild package.
can be initiated.
Verify successful. Rebuild Install for
The verify request is successful. Now you can start Rebuild Install for the specified
GR0030I Rebuild Package %1 Version %2
rebuild package.
can be initiated.
Rebuild Package %1, Version %2 is The specified rebuild package is not defined. Review and verify the correct package
GR0031E
not defined. is identified.
ERROR - when getting count of An error occurred when attempting to count the prepares now in execution. Review
GR0033E
currently running prepares. and determine the validity of the request; correct and reissue the query.
ERROR - when getting count of An error occurred when attempting to count the prepares now remaining. Review
GR0034E
remaining prepares. and determine the validity of the request; correct and reissue the query.
The rebuild prepares that were requested previously have now completed. You can
GR0035I Rebuild prepares have finished.
now proceed to the next operation.
ERROR - when getting count of An error occurred when attempting to count the prepares that failed. Review and
GR0036E
failed prepares. determine the validity of the request; correct and reissue the query.
Updating status of Rebuild Package
%1 Version %2 to Rebuild Analyze The status of the specified rebuild package is changed to Rebuild Analyze
GR0037I
Successful with NO Exceptional Successful with no exceptions. You can now proceed to the next operation.
Processes.
The status of the specified rebuild package is changed to Rebuild Analyze
%1 Version %2 to Rebuild Analyze
GR0038I Successful with exceptions. Review and decide whether to proceed or to return and
Successful with Exceptional
reissue the earlier requests.
Processes.
The verify request is successful. Now the specified rebuild package is Rebuild Seed
GR0039I Package %1, Version %2 is Rebuild
Successful. You can now proceed to the next operation.
Seed Successful.
Verify failed. Current status of
The verify request is not successful. The message text declares the status of the
GR0040I Rebuild Package %1, Version %2 is
specified rebuild package. Review and respond to the current status.
%3.
Verify failed. Current status of
The verify request is not successful. The status of the specified rebuild package is
Rebuild Package %1, Version %2 is
GR0041I Rebuild Analyze Successful with exceptional processes. Review and correct the
Rebuild Analyze Successful with
current status and exceptions.
Exceptional Processes.
The status of the specified rebuild package is changed to Rebuild Analyze Seed
GR0042I %1 Version %2 to Rebuild Analyze
Refine Executing.
Seed Refine Executing.
An error is detected when a status update occurred. The specified rebuild package
is changed to Rebuild Analyze Seed Refine Failed.
Seed Refine Failed.
The status of the designated rebuild package is changed to Rebuild Analyze
GR0045I %1, Version %2 to Rebuild Analyze
Executing.
Executing.


An error is detected when a status update has occurred. The designated rebuild
package is changed to Rebuild Analyze Failed.
Failed.
The status of the specified rebuild package is changed to Rebuild Prepare
GR0047I %1 Version %2 to Rebuild Prepare
Executing.
Executing.
The status of the specified rebuild package is updated to Rebuild Prepare
Successful.
GR0049I %1 Version %2 to Rebuild Prepare The status of the designated rebuild package is updated to Rebuild Prepare Failed.
Failed.
The status of the designated rebuild package is updated to Rebuild Prepare
Incomplete.
Incomplete.
ERROR - when allocating temporary An error is detected attempting to allocate the designated temporary file. Review
GR0051E
file %1 and correct the request to allocate the temporary file.
ERROR - Rebuild Install cannot be
An error is detected from an earlier problem, consequently preventing you from
GR0052E initiated, because of previous
starting Rebuild Install. Examine and correct the earlier problem.
problem(s).
Rebuild Install for Rebuild Package
%1 Version %2 finished Rebuild Install for the specified rebuild package ended successfully. The message
GR0053I
successfully. It was submitted by %3 text also reports submission details.
on %4 at %5.
Rebuild Install for Rebuild Package
Rebuild Install for the specified rebuild package is now executing. The message text
GR0054I %1, Version %2 is currently running.
also reports submission details.
It was started by %3 on %4 at %5.
Verify failed. Rebuild Install can not
The verify process failed. Do not attempt to start the rebuild install process yet
GR0055I be initiated because not all phases
because not all the prior phases ended successfully.
prior to it have finished successfully.
Rebuild Install terminated upon Rebuild Install is terminated as the user had requested. You can proceed with your
GR0056E
user's request. next operation.
ERROR - Unsupported setting in The error of an unsupported setting in the INSTALL_TYPE variable is detected.
GR0057E
INSTALL_TYPE variable. Review and correct the setting in the variable.
Find Rebuild Bind for %1 (%2) %3 The message indicates (in order) the rebuild long name, rebuild system ID, rebuild
GR0058I
%4 Application %5 started at %6. type, and version.
Find Rebuild Bind for %1 (%2) %3
The message indicates (in order) the rebuild long name, rebuild system ID, rebuild
GR0059I %4 (Non-Configured Applications)
type, and version.
%5 started at %6.
Rebuild Seed Refine program
GR0060I The Rebuild Seed Define program began as reported in the message text.
started at %1 %2.
Rebuild Seed Refine program The Rebuild Seed Refine program ended successfully as reported in the message
GR0061I
ended successfully at %1 %2. text.
Rebuild Seed Refine program failed
GR0062I The Rebuild Seed Refine program failed as reported in the message text.
at %1 %2.
Rebuild Analyzer program started at
GR0063I The Rebuild Analyzer program began as reported in the message text.
%1 %2.
Rebuild Analyzer program ended
GR0064I The Rebuild Analyzer program ended successfully as reported in the message text.
successfully at %1 %2.
Rebuild Analyzer program failed at
GR0065I The Rebuild Analyzer program failed at the specified time.
%1 %2.
Rebuild Prepare-driver program
GR0066I The Rebuild Prepare-driver program began at the specified time.
started at %1 %2.


Rebuild Prepare-driver program The Rebuild Prepare-driver program ended successfully as reported in the
GR0067I
ended successfully at %1 %2. message text.
Rebuild Prepare-driver program
GR0068I The Rebuild Program-driver program failed as reported in the message text.
failed at %1 %2.
Rebuild Install-driver program
GR0069I The Rebuild Install-driver program began as reported in the message text.
started at %1 %2.
Rebuild Install-driver program ended The Rebuild Install-driver program ended successfully as reported in the message
GR0070I
successfully at %1 %2. text.
Rebuild Install-driver program failed
GR0071I The Rebuild Install-driver program failed at the specified time.
at %1 %2.
ERROR - when getting count of An error occurred when attempting to count the installs in execution. Review and
GR0072E
currently running installs. confirm the validity of the count request.
ERROR - when getting count of An error occurred when attempting to count the installs that remain. Review and
GR0073E
remaining installs. confirm the validity of the count request.
The rebuild installs that were requested previously have completed. You can now
GR0074I Rebuild installs have finished.
proceed to the next operation.
ERROR - when getting count of An error is detected when attempting to count the installs that failed. Review and
GR0075E
failed installs. confirm the validity of the count request.
The status of the designated rebuild package is updated to Rebuild Install
GR0076I %1 Version %2 to Rebuild Install
Executing. You can now proceed to the next operation.
Executing.
Successful.
Updating status of rebuild package
The status of the designated rebuild package is updated to Rebuild Install Failed.
GR0078I %1, version %2 to Rebuild Install
Review and correct the rebuild package request.
Failed.
Incomplete. Review and correct the rebuild package request.
Incomplete.
ERROR - Rebuild Install has not An error occurred while attempting to initiate the Rebuild Install process. Review
GR0080E
been initiated properly. and confirm the validity of the initiate request.
ERROR - when getting count of Top An error occurred while attempting to count the top and intermediate binds. Review
GR0081E
and Intermediate Binds. and confirm the validity of the count request.
Rebuild Clean-up program started at
GR0082I The clean-up program began running at the specified time.
%1 %2.
Rebuild Clean-up program ended
GR0083I The clean-up program ended successfully at the specified time.
Rebuild Clean-up program failed at
GR0084I Review the other messages.
%1 %2.
Static Link for %1 %2 %3
GR0085E Linkage began at the specified time.
Application %4 started at %5.
Static Link for %1 %2 %3 (Non-
GR0086E Configured Applications) started at Linkage began at the specified time.
%4.
Rebuild SCL program for %1
GR0087I The rebuild SCL program began running at the specified time.
version %2 started at %3.
GR0088I version %2 ended successfully at The rebuild SCL program ended without errors at the specified time.
%3.
version %2 failed at %3.

Enterprise Development Messages - Part 1 GR0090E

ERROR - Unable to retrieve user A call to a security module failed, probably because a user is not listed in a security
GR0090E authorization level. Reason code table or because a DB2 error occurred. Review the other messages and, if
%1. necessary, contact your DB2 administrator.
ERROR - Unable to retrieve
GR0091E An internal error. A repository entry is missing. Contact your System Administrator.
Significant Change Date for %1, %2.
Find Rebuild Static Link for %1 %2
GR0093I Linkage began at the specified time.
%3 Application %4 started at %5.
Find Rebuild Static Link %1 %2 %3
GR0094I (Non-Configured Applications) Linkage began at the specified time.
started at %4.
Rebuild Package does not need to
GR0095I As stated.
be Re-Prepared and Installed.
Rebuild Package does not need to
GR0096I be Re-Prepared, but it needs to be As stated.
Re-Installed.
GR0097I %4 Application %5 ended The bind completed at the specified time with no errors.
successfully at %6.
GR0098I %4 (Non-Configured Applications) The bind completed at the specified time with no errors.
ended successfully at %5.
Find Rebuild Static Link for %1 (%2)
GR0099I %3 %4 Application %5 ended Linkage ended at the specified time.
sucessfully at %6.
Find Rebuild Static Link %1 (%2)
%3 %4 (Non-Configured
GR0100I Linkage ended at the specified time.
Applications) ended successfully at
%5.
GR0101E Error Selecting from %1 table. Internal error. Contact your System Administrator.
ERROR - OS Type %1 is undefined.
GR0102E Translation OS Type to Platform Define the specified execution environment in the system initialization file (hps.ini).
could not be performed
Find Rebuild Static Link for %1 (%2)
GR0103I %3 %4 Application %5 ended with Review the other messages.
errors at %6.
Find Rebuild Static Link %1 (%2)
%3 %4 (Non-Configured
Applications) ended with errors at
%5.
GR0105I %4 Application %5 ended with Review the other messages.
errors at %6.
GR0106I %4 (Non-Configured Applications) Review the other messages.
ended with errors at %5.
The system dataset associated with the DD name INSTFILE is missing. Re-run the
ERROR - File Allocation file %1
GR0108E Analyze method. If the problem persists, contact your System Administrator, who
NOT found.
must call Customer Support.
Results for COPY VSAM records
The copying of VSAM records has started, part of the copy executable phase of the
GR0109E phase for Rebuild Package: %1,
rebuild install.
Version: %2, executed at %3 %4.
ERROR INI variable %1 is not
GR0110E initialized to one of the expected Review the documentation for the initialization file.
values.


All preparable objects in Rebuild
Package %1 have finished
GR0112I As stated.
successfully. Rebuild prepare will
not be submitted.
All Non-IMS VSAM records have
GR0113I As stated.
been copied successfully.
Error have been found during
copying of Non-IMS VSAM records.
Rebuild Report can not be initiated
now. Rebuild Analyze is currently in
GR0115E Wait for the Rebuild Analyze to end.
progress. It was initiated by %1 on
%2 at %3.
now. Rebuild Prepare is currently in
GR0116E Wait for the Rebuild Prepare to end.
%2 at %3.
now. Rebuild Install is currently in
GR0117E Wait for the Rebuild Install to end.
%2 at %3.
GR0118E now. Rebuild Package needs to be Run the ADDR method to do the seeding.
seeded first.
Rebuild Report program ended
GR0119I The program ended at the specified time.
Rebuild Report program failed at %1
%2.
Rebuild Report program initiated at
GR0121I The program began at the specified time.
%1 %2.
There are no rebuild actions
GR0122E Internal error. Contact your System Administrator.
associated with type: %1.
Review the DB2 messages. If the DB2 return code is 100. the configuration unit is
Can't get Long Name for Config Unit
GR0123E not available; you may need to re-enter the configuration unit. If the DB2 return
%1. Advice File will use systemid.
code is negative, contact your DB2 administrator.
Plan Bind has been requested.
Rebuild Package will perform Top
GR0124I As stated.
and Intermediate DB2 Plan bind(s)
when required.
Package Bind has been requested.
GR0125I Rebuild Package will perform DB2 As stated.
Package bind(s) when required.
GR0125I Perform Package Bind . . . . . :%1.
Endevor AVX flag is ON. Rebuild
GR0126I Prepare will prepare PC Rule(s) and
Component(s) for Endevor.
Running RINSTALL method in
GR0127E ENDEVOR environment is not
allowed.
ERROR - when writing to
GR0129E
DDNAME:%1. Error message - %2.
ERROR - when reading from %1.
GR0130E
%2.
ERROR - invalid DD Name %1
GR0131E
returned from HPIVSAM step.


HPIVSAM step ended with return
code of 8, however HMFIERR is
GR0132E
empty. Will fail all 'Copy IMS VSAM
record(s)' actions.
Rebuild Impact Report dataset can
GR0133I not be closed. It has not been
opened.
ERROR - Invalid platform when
GR0134E
fetching count of phases.
Method can not continue. This
GR0135I Rebuild Package does NOT contain
PC prepares.
Rebuild Package marked PC
GR0136E
entities for prepare only, but current
Rebuild Status is invalid.
Rebuild Package marked PC and
Mainframe entities for prepare. The
GR0137E
status of PC prepares can be
updated after successful end of
Rebuild Install.
Resetting rebuild prepare status to
GR0138I
Prepare Needed.
Error setting Install status in
GR0139I subroutine %1. Processing is
terminated.
GR0140I No static link analysis is needed.
Cycle Found in Hierarchy, Top Bind
GR0141I
Analysis will not be performed.
Copy VSAM for %1 %2 started at
GR0142I
%3 %4.
Copy VSAM for %1 %2 ended
GR0143I
sucessfully at %3 %4.
Copy VSAM for %1 %2 ended with
GR0144I
errors at %3 %4.
Install copy will be skipped for %1
GR0145I %2 (%3) because last prepare is
more recent.
GR0146I There are no rebuild copies needed.
Internal tables indicate that a more
recent method has occurred for %1
%2 (%3) for Methodid: %4. The
GR0147I
method timestamp will not be copied
to the Ent Method table for this
entity.
There are no Methods available for
GR0148I
Update on %1 platform.
Set Install Status for %1 %2 started
GR0149I
at %3 %4.
Set Install Status for %1 %2 ended
GR0150I
sucessfully.
Set Install Status for %1 %2 ended
GR0151I
with errors.
GR0160I Rebuild Analyze for RBDPKG Entity


GR0161I Exception Processing
Specify Rebuild Analyze option.
GR0162I
Then Press Enter.
GR0163I Rebuild Analyze option . . . .
GR0164I Inverse Processing
ERROR - when changing status of An error occurred while attempting to change the status of the specified rebuild
GR2001E Rebuild Package %1, Version %2 to package to Rebuild Seed Refine Successful. Review and confirm the validity of the
Rebuild Seed Refine Successful. change status request.
ERROR - when deleting leaf An error is detected when attempting to delete leaf processes in the specified
GR2002E processes in Rebuild Package %1, rebuild package. Review and confirm the validity of the delete leaf processes
Version %2. request.
ERROR - Rebuild Package %1,
An error occurred when the specified rebuild package either is not defined or had no
GR2005E Version %2 is not defined or has no
seeds. Review and correct the rebuild package or its preparation.
seeds.
WARNING - process %1 found in The specified process in the indicated migration is not a leaf process and is
GR2007I migration %2 is not a leaf process. It ignored. The process is a seed process to a rebuild package. Review and change
will be ignored. the process as appropriate.
ERROR - when allocating storage
An error is detected when attempting to allocate storage for the next node on the
GR2008E for the next node on the entity link
entity link list. Review and confirm the validity of the storage allocation request.
list.
ERROR - when verifying that An error is detected when attempting to verify that the specified rebuild-seed
GR2009E
process %1 is a leaf one. process is a leaf process. Review and confirm whether the leaf process exists.
ERROR - Rebuild Package is
seeded with Migration #1, but An error is detected when the specified migration is not found in the R_MGPRXX
GR2010E
migration table R_MGPRXX does table. Review and correct the status of the specified migration.
not contain any Processes.
ERROR - when updating seed An error is detected when attempting to update the specified seed process to be a
GR2011E
process %1 to be a leaf one. leaf process. Review and confirm the validity of the process updating request.
ERROR - when adding a leaf An error is detected when attempting to add the specified leaf process to the
GR2012E process %1 to Rebuild Package %2, identified rebuild package. Review and confirm the validity of the leaf adding
Version %3. request.
Rebuild Seed Refine can not An error is detected when attempting to perform the Rebuild Seed Refine process.
GR2014E continue because of previous That attempt cannot continue because of previous errors. Review and confirm the
error(s). validity of the request to rebuild seed redefine.
ERROR - when resetting leaf
An error is detected when attempting to reset leaf processes in the specified rebuild
GR2015E processes in Rebuild Package %1,
package. Review and confirm the validity of the leaf resetting request.
Version %2.
GR2018I Rollback is being performed. This notification confirms the Rollback process is now executing.
GR2019I Rollback successful. This notification confirms the Rollback process completed successfully.
This notification informs you that the Rollback process encountered errors. Review
GR2020I Rollback error occurred.
and determine the error and the corrective action needed.
An error is detected when attempting to find the specified entity type in the hash
ERROR - entity %1, type %2, could
GR2022E table. Review and confirm the validity of the request to locate the entity in the hash
not be found in hash table.
table.
Rebuild Analyze can not continue The Rebuild Analyze process could not continue because of encountered errors.
GR2023E
because of previous error(s). Review and validate the Rebuild Analyze request.
ERROR - Rebuild Package %1 An error is detected because the specified rebuild package has none of the required
GR2024E
Version %2 has no leaf processes. leaf processes. Review and validate the request for the rebuild package.
Rebuild Package %1 Version %2 An error is detected because the specified rebuild package had no entities marked
GR2025I
has no entities marked for prepare. for prepare. Review and validate the request for the rebuild package.
Rebuild Package %1 Version %2 To run Rebuild Analyze, you need to have defined a root entity. Do so and re-run
GR2026E
has NO Root Entities. the Rebuild Analyze.


ERROR - when selecting next An error is encountered in attempting to select the next prepare. Review and correct
GR5001E
prepare. the prepare request.
ERROR - when writing Profile
An error is detected when attempting to write a profile record of the RMI request file.
GR5002E record of RMI request file. Error
Review and correct the write RMI request.
message - %1.
ERROR - when writing FT request
An error is detected when attempting to write an FT record of the RMI request file.
GR5003E record of RMI request file. Error
Review and correct the write RMI request.
message - %1.
ERROR - when writing prepare An error is detected when attempting to write a prepare parameter record. Review
GR5004E
parm record. and correct the write request.
Preparable object %1, type %2 does An error is detected because the specified preparable object is not located. Review
GR5005E
not exist. and correct the request for the object.
ERROR - when updating status of An error is detected when attempting to update the status of the specified
GR5006E
preparable object %1, type %2. preparable object. Review and correct the preparable object request.
ERROR - when committing status of An error is detected when attempting to commit the status of the specified
GR5007E
preparable object %1, type %2. preparable object. Review and correct the preparable object request.
Changing status of Rebuild Package The status of the rebuild package is changed to Prepare Successful. This
GR5008I
to Prepare Successful. information message confirms the change of the rebuild packages status.
The status of the rebuild package is changed to Prepare Failed. This information
Changing status of Rebuild Package
GR5009I message confirms the change of status, allowing you to reexamine the rebuild
to Prepare Failed.
package.
Changing status of preparable
The status of the specified preparable object is changed to Prepare Successful.
GR5010I object %1, type %2, to Prepare
This information message confirms the change of the objects status.
Successful.
The status of the specified preparable object is changed to Prepare Successful.
This information message confirms the change of the objects status.
Submitted.
Changing status of preparable The status of the specified preparable object is changed to Prepare Failed. This
GR5012I object %1, type %2, to Prepare information message confirms the change of the objects status, allowing you to
Failed. reexamine the preparable object.
An error is detected when attempting to perform the rebuild prepare. That attempt
Rebuild Prepare can not continue
GR5013I cannot continue because of previous errors. Review and confirm the validity of the
because of previous error(s).
request to rebuild prepare.
Rebuild Prepare can not continue.
The rebuild prepare cannot continue because the number of prepares for the
GR5014E Total %1 prepares for phase %2
specified phase have failed. Review and correct the specified prepares.
(%3) have failed.
The status of the specified preparable object is changed to Prepare Executing. This
information message confirms the change of the objects status.
Executing.
Rebuild Prepare failed. Resetting An error occurred during the rebuild prepare, and consequently, the indicated
GR5016E remaining selected prepares to number of the prepares selected were reset to Prepare Required. Review and
Prepare Required. correct the rebuild prepare, and then reissue the prepare for all affected processes.
Rebuild Install failed. Will reset %1 An error occurred during the rebuild install, and consequently the indicated number
GR5017E remaining selected installs to Install of the installs selected were reset to Install Required. Review and correct the rebuild
Required. install, and then reissue the install for all affected processes.
ERROR - when fetching variable An error is detected when attempting to fetch the specified REXX variable. Review
GR9000E
%1, rc = %2. the return code, and correct the fetch before reissuing the command.
ERROR - when putting variable %1, An error is detected when attempting to put the specified REXX variable. Review
GR9001E
rc = %2. the return code and correct the put before reissuing the command.
ERROR - when getting DB2 An error is detected during an attempt to get a time stamp from DB2. Review and
GR9002E
timestamp. validate your request for getting the time stamp.
ERROR - explode was not initiated
GR9003E This message warns that the explode did not start, and it returns.
properly.

GR9004E Enterprise Development Messages - Part 1

ERROR - non-zero return code from An error is detected when the specified return code is received from EXPLINIT.
GR9004E
explinit, rc = %1. Review the code, and correct the command.
ERROR - non-zero return code from An error is detected when the specified return code is received from EXPLADDE.
GR9005E
expladde, rc = %1. Review the code, and correct the command.
ERROR - non-zero return code from An error is detected when the specified return code is received from EXPLODE.
GR9006E
explode, rc = %1. Review the code, and correct the command.
ERROR - definition for entity type An error is detected when the definition for the specified entity type is not found.
GR9007E
%1 is not found. Review the entity type definition, and correct the command.
An error is detected while attempting to open the specified cursor. Review and
GR9008E ERROR - when opening cursor %1.
correct the open request.
ERROR - when fetching for cursor An error is detected while attempting to fetch the specified cursor. Review and
GR9009E
%1. correct the fetch command.
An error is detected while attempting to close the specified cursor. Review and
GR9010E ERROR - when closing cursor %1.
correct the close command.
ERROR - when updating for cursor An error is detected while attempting to update the specified cursor. Review and
GR9011E
%1. correct the update command.
ERROR - %1 is not a preparable An error is detected because the specified entity is not preparable. Review and
GR9012E
entity. correct the request.
ERROR - entity type %1, name %2, An error is detected: the specified entity is not located. Review and reissue the
GR9013E
version %3 is not found. correct request.
ERROR - when closing data set. An error is detected when attempting to close a data set. Review and correct the
GR9014E
Error message - %1. close command.
ERROR - allocation for DSNAME = An error is detected because the specified entity is not located. Review and reissue
GR9015E
%1 failed with RC = %2. the correct request.
A storage allocation error is encountered. Review and evaluate the allocation
GR9016E ERROR - when allocating storage.
request.
ERROR - when fetching from %1 An error is detected when attempting to fetch from the specified table. Review and
GR9017E
table. correct the fetch command.
ERROR - when deleting from %1 An error is detected when attempting to delete from the specified table. Review and
GR9018E
table. correct the delete command.
ERROR - when inserting into %1 An error is detected when attempting to insert into the specified table. Review and
GR9019E
table. correct the insert command.
An error is detected when attempting to update the specified table. Review and
GR9020E ERROR - when updating %1 table.
correct the update command.
An error is detected when attempting to read the INI file. Review and evaluate the
GR9021E ERROR - when reading INI file.
attempt to read the INI file.
ERROR - Selection Panels could An error is detected: the selection panels cannot be displayed. Review and correct
GR9022E
not be displayed. the display request.
ERROR - Rebuild Prepare cannot
An error is detected because previous problems prevented the start of the rebuild
GR9024E be initiated, because of previous
prepare process. Review and evaluate the rebuild prepare request.
problem(s).
ERROR - when opening DDName
An error is detected when attempting to open a data set. Review and correct the
GR9025E %1, Member %2. Error message -
open request.
%3.
ERROR - invalid Rebuild Analyze An error is detected: the Rebuild Analyze phase is invalid. Review and validate the
GR9026E
phase. Rebuild Analyze phase request.
ERROR - Rebuild Prepare Status An error is detected: the Rebuild Prepare Status Reset finished unsuccessfully.
GR9027E
Reset has finished unsuccessfully. Review and correct that rebuild request.
Resetting prepare status of object in The prepare status of the object in the specified phase is being reset. The entity
GR9028I
phase %1, (%2). types are listed.
GR9029I Prepares were reset successfully. The attempt to reset the prepares is successful.
GR9030I NO prepares were found to be reset. The attempt to reset prepares failed because no prepares were found.


ERROR - Prepares are still in This message informs that a requested action cannot be performed now because
GR9031E progress. This action can not be prepares were in progress. Review the request, and wait for the completion of the
performed presently. present action.
Attempt was made to reset prepare
An attempt is requested to reset the prepare status of objects in background, and
GR9032E status of objects in background,
that action is not allowed. Review and correct the request.
which is not allowed.
ERROR - Prepare Status Reset
The attempt to perform an action cannot be honored because the prepares have not
GR9033E cannot be initiated. Rebuild
been started. Review the request, and ensure the completion of the present action.
Prepares have not been initiated.
ERROR - Prepare Status Reset
cannot be initiated. One of the An attempt to start the prepare status reset process failed. Another phase after it
GR9034E
phases following it has been started executing. Review and correct the prepare request.
initiated.
Rebuild Prepare Status Reset has This message notifies that the Rebuild Prepare Status Reset completed
GR9035I
finished successfully. successfully.
ERROR - Fetch for module %1 An error is detected: the attempt to fetch the specified module failed because the
GR9036E failed. Program was not found or program is not found or could not be loaded. Review and confirm the validity of the
could not be loaded. fetch request.
Rebuild Prepare Status Reset This message confirms that the Rebuild Prepare Status Reset is ended at the
GR9037E
terminated upon user's request. request of the user.
Skipping %1, %2, execution An error is detected because the mainframe batch (MVSBAT) execution
GR9038E environment: MVSBAT, because environment requires BATCH support to be installed. Review and correct the proper
BATCH AVX is not supported. environment for this request.
Skipping %1, %2, execution An error is detected because the mainframe (MVS) execution environment requires
GR9039E environment: MVS, because BATCH BATCH and CICS support to be installed. Review and correct the proper
and CICS AVXs are not supported. environment for this request.
Skipping %1, %2, execution
An error is detected because the MAINFRM and PCCICS execution environment
environment: MAINFRM or
GR9040E requires CICS support to be installed. Review and correct the proper environment
PCCICS, because CICS AVX is
for this request.
NOT supported.
Skipping %1, %2, execution An error is detected because the IMS and PCIMS execution environment requires
GR9041E environment: IMS or PCIMS, IMS support to be installed. Review and correct the proper environment for this
because IMS AVX is not supported. request.
ERROR - when committing current An error is detected when attempting to commit the current changes to DB2 tables.
GR9042E
changes to DB2 tables. Review and correct the commit current changes request.
ERROR - when updating status of An error is detected when attempting to update the status of the rebuild package.
GR9043E
Rebuild Package. Review and correct the update status request.
ERROR - Prepare platform %1 is An error is detected because the specified prepare platform is invalid. Review and
GR9044E
invalid correct the prepare request.
ERROR - when writing to Install File An error is detected when attempting to write to the Install File Allocation file.
GR9045E
Allocation file. Review and correct the commit current changes request.
ERROR - when getting count of An error is detected when attempting to count the install actions. Review and
GR9046E
install actions. correct the counting installs request.
Changing status of Install Action %1 This messages informs the status of the specified install action is changed to
GR9047I
to Successful. Successful.
Changing status of Install Action %1 This messages informs the status of the specified install action is changed to
GR9048I
to Initiated. Initiated.
Changing status of Install Action %1 This messages informs the status of the specified install action is changed to Failed.
GR9049I
to Failed. Review and correct the install action request.
Changing status of Install Action %1 This messages reports the status of the specified install action is changed to
GR9050I
to Executing. Executing.
ERROR - when updating status of An error is detected when attempting to update the status of Install Action. Review
GR9051E
Install Action. and correct the install action request.

GR9052E Enterprise Development Messages - Part 1

Resetting ALL remaining Selected This message reports that all of the remaining selected Install Actions were being
GR9052E
Install Actions reset.
Installation Problem. NO AVX are An installation problem occurred because no AVXs were installed. Review your
GR9053E
installed. installation and determine the updates your installation needs.
Installation Error. INI variable
REGIONS.CICSREG has to be An installation problem occurred because CICSREG is not defined. Review your
GR9054E
defined when CICS support is installation and determine the updates your installation needs.
installed.
REGIONS.IMSREG has to be An installation problem is detected because IMSREG is not defined. Review your
GR9055E
defined when IMS support is installation and determine the updates your installation needs.
installed.
REGIONS.BTCHREG has to be An installation problem is detected because BATCHREG is not defined. Review
GR9056E
defined when BATCH support is your installation and determine the updates your installation needs.
installed.
ERROR - when updating prepare An error is detected when attempting to update the prepare time. Review and
GR9057E
time. correct the update prepare time request.
Update Prepare Time for %1 %2
GR9058I The prepare time for the specified entity type and name is successful.
successfully.
ERROR - Rebuild Install Status An error occurred because the status reset for rebuild install failed. Review and
GR9059I
Reset has failed. correct the status reset request.
ERROR - Install Status Reset
An error occurred because Install Status Reset cannot be started. Review and
GR9060E cannot be initiated. Rebuild Installs
correct the Install Status Reset request.
have not been initiated.
Rebuild Install Status Reset has This message confirms the successful completion of the Rebuild Install Status
GR9061I
finished successfully. Reset for the request.
Changing status of Install Action %1 This message confirms that the status of the specified install action is now
GR9062I
to Required. Required.
Resetting install status of actions in This message reports the install status of the actions in the Copy Executables step
GR9063I
'Copy Executables' step. is reset.
Resetting install status of actions in This message reports the install status of the actions in the DB2 Bind Top Rules
GR9064I
'DB2 Bind Top Rules' step. step is reset.
Resetting install status of actions in
GR9065I This message reports the install status of the actions in the LU2 Install step is reset.
'LU2 Install' step.
Resetting install status of actions in This message reports the install status of the actions in the DB2 Bind Intermediate
GR9066I
'DB2 Bind Intermediate Rules' step. Rules step is reset.
GR9067I Installs were reset successfully This message confirms that all installs were completed and successfully reset.
GR9068I NO installs were found to be reset. This message informs that no install to be reset were found.
Attempt was made to reset install
GR9069E status of objects in background, To reset the install status of the objects, use the repository.
which is not allowed.
ERROR - Installs are still in
An error occurred attempting to perform this action due to installs in progress. Wait
GR9070E progress. This action can not be
for the completion of the present action.
performed presently.
ERROR - Unrecognized Rebuild
Install Action is found.
All preparable entities with Projects If you wish to prepare those entities, have your System Administrator change the
GR9072I
%1 will be skipped. values in the HPSINI Analyze section variables SKIP_SEER1 and SKIP_SEER2.
Running Rebuild Analyze for
GR9073I As stated.
SUPER PREPARE.
GR9074I Rebuild Seed Refine final statistics. Introduces the numbers that appear thereafter.


Total number of Rebuild Root
GR9075I As stated.
Entities Refined...%1.
Total number of Leaf Processes
GR9076I As stated.
added...%1.
Total number of Root Entities
GR9077I As stated.
marked as Leaf Processes...%1.
GR9078I Rebuild Analyze final statistics. Introduces the numbers that appear thereafter.
Total number of Rebuild Root
GR9079I As stated.
Entities...%1.
Total number of Non-Configured
GR9080I As stated.
Root Entities...%1.
Total number of Configured Root
GR9081I As stated.
Entities...%1.
Total number of entities marked for
GR9082I As stated.
prepare...%1.
Total number of Exceptional Top
GR9083I As stated.
Entities...%1.
GR9084I Clean-up is not required. As stated.
When updating status of action %1,
selection did not find any matches.
GR9086I Internal error. Contact the System Administrator.
Static Link step.
GR9087I Approve is not required. As stated.
Error occurred when getting
GR9088E Review the other messages.
Migration information.
User %1 is the Migration owner, and
GR9089I You lack the authority to perform this task. //??????? Yarik ?????//
can not approve it.
Migration Analyze has not finished
GR9090I successfully. Migration can not be Wait until Migration Analyze is complete.
approved.
Migration has been approved
GR9091I As stated.
successfully.
Error occurred when updating
GR9092E Review other messages.
migration status
Prepare time for Entity Type %1 and
GR9093I As stated.
Entity Name %2 was successful.
Rebuild Install Status Reset has
GR9094I Review other messages.
failed.
Migration has been already
GR9095I You need not run the Approve method against this migration.
approved.
Rebuild Detector program has
GR9096I Review other messages.
ended with error, rc=%1.
Skipping %1, %2, prepare
platform:Mainframe, because The AVX flags are not set properly in the initialization (INI) file. Contact your System
GR9097E
neither CICS and PCNV nor IMS Administrator.
and ICNV AVX flags are supported.
GR9098I No action necessary.
DB2 Package Bind step.
GR9099I Perform Process Prepare . . . :%1.
INI variable PROCESS52 is NOT
GR9100I set. Rebuild Analyze will not add
PROCESSES to rebuild tables.


GR9101I Processing Options selected:
Default values from INI file(s) for
GR9102I
SUPERPR:
GR9103I Prepare Phase . . . . . . . . :%1.
GR9104I Install Phase . . . . . . . . :%1.
GR9105I Number of active jobs . . . . :%1.
GR9106I Ignore failed prepares . . . . :%1.
GR9107I Continuous submission . . . . :%1.
Re-submit incomplete prepares.
GR9108I
:%1.
GR9109I Re-submit failed prepares . . :%1.
GR9110I DB2 Bind Intermediate Rules . :%1.
Endevor Status Update program
GR9111I
started on %1 at %2.
Endevor Status Update for %1
GR9112I %2(%3) ended successfully at %4
%5.
Endevor Status Update for %1
GR9113I
%2(%3) failed at %4 %5.
GR9114I Updating Static Link phase.
GR9115I Updating Copy Executables phase.
GR9116I Updating Top Bind phase.
GR9117I Updating Intermediate Bind phase.
GR9118I Updating LU2-Setup Install phase.
GR9119I Updating Endevor Install phase.
GR9120I Update successful.
NO actions were found for this
GR9121I
phase.
Unrecognized method id was
GR9122E passed to Endevor State Update
program.
GR9123I Updating Endevor Prepare actions.
GR9124I Entity Type . . . . . . . . . :%1.
GR9125I Entity's Name . . . . . . . . :%1.
GR9126I Entity's System ID . . . . . . :%1.
GR9127I Version . . . . . . . . . . . :%1.
GR9128I User ID . . . . . . . . . . . :%1.
GR9129I Project . . . . . . . . . . . :%1.
GR9130I Method ID . . . . . . . . . . :%1.
GR9131I Ignore failed installs . . . . :%1.
GR9132I Re-submit incomplete installs. :%1.
GR9133I Re-submit failed installs . . :%1.
GR9134I Original Method ID . . . . . . :%1.
GR9135I Re-generate LU2 control cards :%1.
GR9136I Re-generate Bind control cards :%1.
GR9137I Global processing options.


GR9138I Commit level . . . . . . . . . :%1.
GR9139I Endevor . . . . . . . . . . . :%1.
GR9140I Endevor Option . . . . . . . . :%1.
GR9141I Batch AVX . . . . . . . . . . :%1.
GR9142I CICS AVX . . . . . . . . . . :%1.
GR9143I PCNV AVX . . . . . . . . . . :%1.
GR9144I IMS AVX . . . . . . . . . . :%1.
GR9145I ICNV AVX . . . . . . . . . . :%1.
GR9146I Rebuild original seeds.
Rebuild original seeds for
GR9147I
Application Configuration %1.
GR9148I %1 %2(%3) requires refinement.
GR9149I %1 %2(%3).
GR9150I Rebuild refined seeds.
Rebuild refined seeds for
GR9151I
Rebuild Analyze with the Inverse
scope option previously ended
successfully. The Cleanup method
GR9152I
must be executed against the
Rebuild package prior to running
another Rebuild analyze.
GR9154I Rebuild Scope. . . . . . . . . :%1.
GR9156I Impact of Rebuild Analysis.
%1 %2(%3) needs to be prepared
GR9157I on %4. It was last prepared at %5,
and modified at %6.
GR9158I on %4. It has never been prepared
before.
on %4, because its prepare scope
GR9159I
changed. Entity that changed %5
%6(%7) was modified at %8.
GR9160I Rebuild Seed summary report.
Rebuild Seed summary report for
GR9161I
Rebuild refined seed %1 %2(%3)
GR9162I
has changed.
Rebuild exceptional Top Object %1
GR9163I
%2(%3).
GR9164I %1 %2(%3) needs to be prepared.
Source / Relations (RUNTDBG) .
GR9165I
:%1.
ERROR - when allocating one of the
INSTALL datasets identified in
GR9166E dataset: &dsname . Check
SYSTSPRT in your job output for
the specific dataset.


GR9167I on %4. Rebuild runs in SUPERPR
mode.
CICS Viewdef (RUNTDBVW) . . .
GR9168I
:%1.
GR9170I Process Prepare Collapse . . . :%1.
GR9171I HPS Release Level. . . . . . . :%1.
GR9172I Cycle found on relation %1.
Window %1(%2) can not be
GR9173E processed; it is not used by any
Rule.
Window %2(%1) can not be
GR9174I processed; it is not used by any
Rule.
The execution environment will be
GR9175I
defaulted to PC.
File definition is missing from
GR9176E
e_hpsfil table for Action Id %1.
Error during VSAM install of %1 %2
GR9177E
(%3) in ActionId %4.
GR9179I on %4, because %5 %6 is marked
for prepare.
GR9180E VSAM rc . . . . . . .:%1
GR9181E VSAM Reason Code. . .:%1
GR9182I on %4, since the layout of %5 %6
has changed.
ERROR - When opening cursor
GR9201R
DETAIL_RPRT
ERROR - When fetching for cursor
GR9202R
DETAIL_RPRT
ERROR - When closing cursor
GR9203R
DETAIL_RPRT
ERROR - When fetching from
GR9204R
E_CFGUNIT table.
GR9205R Execution Environment:%1,
Platform:%1,%2 Project:%3,
GR9206R
DBMS:%4.
GR9207R Config ID:%1, Config Name:%2
GR9208R Current Rebuild State:%1
Maintained by:%1, Maintain
GR9209R
Date:%2 %3
GR9210R - %1 Prepare
GR9211R - %1 Prepare Collapse
GR9212R - %1 ENDEVOR Prepare
GR9213R - %1 ENDEVOR Install
GR9214R Successful
GR9215R Incomplete
GR9216R Failed

Enterprise Development Messages - Part 1 GR9217R

GR9217R Executing
GR9218R Submitted
GR9219R Selected
GR9220R Needs
GR9221R ERROR
GR9222R Mainframe
GR9223R PC
GR9224R DETAIL
GR9225R COUNT
GR9226R Unrecognized Rebuild State
GR9227R Skipped
%1 %2(%3) has no significance
GR9300W
table row in version: %4.
Orphan %1 %2 has no E_%3 row in
GR9301W
Version: %4.
GR9302R Report Summary for Version: %1
GR9303R %1s Processed: %2
GR9304R Entities need to be prepared: %1
GR9305R Orphan relationships found: %1
GR9306R Missing Significance rows: %1
ERROR - Rebuild
GR9999E
UNSUCCESSFUL, %1
Error - SUPERC Utility processing An error occurred because processing the SUPERC utility ended with the specified
GT0000E
terminated with rc = %1. return code. Evaluate the return code and correct the problem.
Warning - Analyze has to be run
GT0001W A message of warning: you must run the Analyze process before Delta can execute.
before Delta can proceed.
Informational - Import is successful.
GT0002I This message informs that Import is successful, and Delta will not run.
Delta will not run.
Object in target repository has been This warning message appears when you are running the Delta method because
GT0005W
modified since the last Analyze. the target object has changed since the Analyze.
Object has been created in the
This warning messages appears when you are running the Delta method because
GT0006W target repository since the last
the object now exists in the target repository and is identical to the source object.
Analyze.
Object has been created in the
target repository since the last This warning messages appears when you are running the Delta method because
GT0007W
Analyze. It is now different from the the object now exists in the target repository and is different from the source object.
source repository.
Object has been deleted from the
GT0008W target repository since the last Object is deleted during execution of the Delta method.
Analyze.
GT0009W Error generating %d report. The specified report can not be produced. Review the other messages.
Source MF Code Page &CVALUE
The source mainframe code page does not match the target code page . Review
GUI000E does not match the target
and correct the code page specification.
&MVALUE.
Source PC Code Page %1 does not The source workstation code page does not match the target code page. Review
GUI001E
match the target %2. and correct the code page specification.
Source release %1 cannot be
GUI002E Review and correct the migration release specification.
migrated to target release %2.
Change processing option for %1 to This message notifies that you must match the specified processing option with the
GUI003W
match the %2. specified method.

GUI004E Enterprise Development Messages - Part 1

The migration cannot occur because the target repository is not set up to receive
GUI004E Invalid Source Repository %1. from the source. Ask your System Administrator to change the restriction on the
target repository.
An internal error occurred when trying to retrieve the data record from the specified
GUI005E Error Code %1 returned from %2.
program. Contact your System Administrator.
Error when writing to %1 file. RC =
GUI006E Ensure that the dataset associated with the DD name MIGCNTL is allocated.
%2.
Error Allocating PARMS file for %1.
GUI007E Ensure that the dataset associated with the DD name PARMS is allocated.
RC = %2.
Rebuild Processing cannot proceed
GUI008E Run the migration import job.
because Import hasn't been done.
Unable to obtain LOCK for Migration An error occurred when trying to lock the specified migration for processing.
GUI009E
Entity %1. Another user may have locked the same migration.
Rebuild Workbench is not installed,
GUI010E Export if a rebuild package cannot run. Install the Rebuild Workbench.
EXPORT will not run.
Rebuild Export will not run because
GUI011E Rbdpkg has not been successfully Export of a rebuild package can occur only after the rebuild package is successful.
analyzed.
Import cannot continue. Migration The approval process is enabled and the migration analyze has not been approved.
GUI012E
needs to be Approved. Approve the migration before trying to import the migration.
An error occurred when trying to update the migration-entity record. Review the
GUI013E Cannot update %1 record, RC = %2.
other messages.
The state of your Rebuild package is
GUI014E
not valid for this method.
COPYAPP &LIBNAME MEMBER
COPYAPP &LIBNAME MEMBER &IMPNAME NOT IN LOAD LIBRARY,
HAX001W &IMPNAME NOT IN LIBRARY,
REPREPARE.
CHECK IF OK OR REPREPARE.
COPYAPP &TYPE RECORD
COPYAPP &TYPE RECORD &IMPNAME IN &FILE FILE NOT FOUND,
HAX002W &IMPNAME IN &FILE FILE NOT
REPREPARE &TYPE.
FOUND, REPREPARE &TYPE.
COPYAPP ENTITY FILE DOES
HAX003E NOT EXIST, RERUN RUNTIME Always run export before running the COPYAPP method.
EXPORT METHOD.
COPYAPP EXTRACT PACKAGE COPYAPP EXTRACT PACKAGE SUBMITTED FOR %1. The job is submitted to
HAX004I
SUBMITTED FOR &OUTTYPE. extract the tape output data or the PC chopped 80 byte data.
COPYAPP EXTRACT PACKAGE
COPYAPP EXTRACT PACKAGE NOT SUBMITTED. JCL IN DATASET
HAX005W NOT SUBMITTED. JCL IN
&FTOUTFIL.
DATASET &FTOUTFIL.
COPYAPP CHECK RESULTS AND
HAX006I SUBMIT JCL EXTRACT COPYAPP CHECK RESULTS AND SUBMIT JCL EXTRACT %1 IF OK. As stated.
&FTOUTFIL IF OK.
COPYAPP FUNCTION
COPYAPP CHECK RESULTS AND SUBMIT JCL EXTRACT &FTOUTFIL IF OK.
HAX007E &FUNCTION FOR &NAME FAILED
As stated.
WITH RC=&RETCC.
COPYAPP ALLOCATE FOR FILE
COPYAPP CHECK RESULTS AND SUBMIT JCL EXTRACT &FTOUTFIL IF OK.
HAX008E &DDNAME DSN &DSN FAILED
COPYAPP CHECK RESULTS AND SUBMIT JCL EXTRACT %1 IF OK. As stated.
WITH RC=&RETCC.
COPYAPP EXPORT &NAME
HAX009I VERSION &VRSN STARTED AT COPYAPP EXPORT &NAME VERSION &VRSN STARTED AT &TIMESTAMP.
&TIMESTAMP.
VERSION &VRSN ENDED COPYAPP EXPORT &NAME VERSION &VRSN ENDED SUCCESSFULLY AT
HAX010I
SUCCESSFULLY AT &TIMESTAMP.
&TIMESTAMP.

Enterprise Development Messages - Part 1 HAX011I

COPYAPP EXPORT &NAME VERSION &VRSN ENDED WITH MESSAGES AT
HAX011I VERSION &VRSN ENDED WITH
&TIMESTAMP.
MESSAGES AT &TIMESTAMP.
COPYAPP EXPORT WILL NOT
COPYAPP EXPORT WILL NOT RUN RBDPKG HAS NOT BEEN SUCCESSFULLY
HAX012E RUN RBDPKG HAS NOT BEEN
EXPORTED.
SUCCESSFULLY EXPORTED.
Runtime data for Sets and 3270
HAX013W Converse Windows missing from
%1
Runtime data missing for %1 %2
HAX014W with implementation name %3 from
DD:%4
HAXPRST - Update object
HAX015I
preparation timestamp started.
HAX016I preparation timestamp ended
successfully.
HAX017W preparation timestamp ended with
warnings.
HAX018W preparation timestamp ended with
errors.
COPYAPP &RECTYPE RECORD
&IMPNAME NOT FOUND IN &FILE
HAX019W
FILE, RE-PREPARE PARENT
RULE(S).
COPYAPP &RECTYPE RECORD
&IMPNAME NOT FOUND IN &FILE
HAX020W
FILE, RE-PREPARE FRONTIER
RULE.
HC0000I Successful CRUD operation. Successful CRUD operation. No action required.
This relationship already exists. Message occurs when you try adding a relationship
HC0803E This relationship already exists. between two relationships or when you try adding a preexisting relationship; in
either case, do not repeat the attempt.
A DB2 805 error occurred. Contact your System Administrator. In the system, there
HC0805E A DB2 805 error occurred.
is a DBRM timestamp problem or a DB2 package is missing from a collection.
A DB2 904 error occurred. Unavailable Resource. If a resource time-out is
A DB2 904 error occurred.
HC0904E suspected, retry the operation later; the system may be transferring data from tape
Unavailable Resource.
to disk. If the problem persists, contact your System Administrator.
A DB2 911 error occurred. A DB2 911 error occurred. Resource deadlock occurred. Retry the operation. If the
HC0911E
Resource deadlock occurred. problem persists, contact your System Administrator.
HC0997E CCNVT Internal Error occurred. CCNVT Internal Error occurred. Contact your System Administrator.
Error locking relation. Object already Error locking relation. Object already in requested state. Object is already locked
HC1001E
in requested state. and can not be reset to the same lock level. No action required.
Cannot perform the action since the present lock status of the object conflicts with
Your action conflicts with the current
HC1002E your action. In other words, you cannot unlock an object that is not locked or
lock status of the object.
update/ delete an object which is being updated. Retry again at a later time.
Mismatch of Entity's original and Mismatch of Entity's original and current change number. An update has occurred
HC1003E
current change number since you accessed the entity. Cancel your changes and retry the operation.
Mismatch of Relation's original and current change number. An update has
Mismatch of Relation's original and
HC1004E occurred since you accessed the relation. Cancel your changes and retry the
current change number
operation.

HC1006E Enterprise Development Messages - Part 1

Security authorization level error or User request unauthorized. You lack the
Security authorization level error or
HC1006E necessary security clearance to perform the operation. Contact your System
User request unauthorized.
Administrator.
The CRUD entity or relation code is The CRUD entity or relation code is not in the required range. Internal error. Contact
HC1008E
not in the required range. the System Administrator.
The CRUD driver operation code is The CRUD driver operation code is not valid. Internal error. Contact the System
HC1009E
not valid. Administrator.
Error Message Set Style must be of Error Message Set Style must be of type Integer or Small Integer. Correct the
HC1018E
type Integer or Small Integer. domain of your set type and retry the operation.
Embedded blanks not allowed. The displayed property cannot have embedded
HC1021E Embedded blanks not allowed.
blanks Remove them and retry the operation.
Name cannot contain non alpha/ Name cannot contain non alpha/numeric characters. Remove the invalid characters
HC1022E
numeric characters. and retry the operation.
The field contains an invalid first The field contains an invalid first character. Remove the invalid character and retry
HC1023E
character. the operation.
Small Integer and Integer length
Small Integer and Integer length must be 15 for Set Style Error Message. Correct
HC1024E must be 15 for Set Style Error
the domain of your set type and retry the operation.
Message.
Length of Decimal data type must Length of Decimal data type must be between 1 and 31. Correct the data type or
HC1026E
be between 1 and 31. length and retry the operation.
Field scale must be between 0 and Field scale must be between 0 and length of field. Correct the field scale and retry
HC1027E
length of field. the operation.
Range of Minimum Value must be Range of Minimum Value must be less than range of Maximum Value. Correct the
HC1028E
less than range of Maximum Value. ranges and retry the operation.
Length of Integer data type must be Length of integer data type must be 31 and small integer must be 15. Correct the
HC1029E
31 and Smallint must be 15. data type or length and retry the operation.
Picture data type must have a Picture data type must have a picture storage format. Correct the data type or
HC1030E
picture storage format. length and retry the operation.
Picture storage value has invalid Picture storage value has invalid character or format. Correct the value and retry the
HC1031E
character or format. operation.
Length of character data type Length of character data type cannot exceed 4000. Set field length within the
HC1032E
cannot exceed 4000. required range and retry the operation.
Length of VARCHAR data type must Length of VARCHAR data type must not exceed 4000. Set field length within the
HC1034E
not exceed 4000. required range and retry the operation.
Picture display format contains Picture display format contains invalid characters. Make the print display format
HC1035E
invalid characters. conform with standard COBOL formatting and retry the operation.
HC1041E Error during TSO library cleanup. Error during TSO library cleanup. Contact the System Administrator.
Length of character/mixed data type Length of character/mixed data type must be between 1 and 30. Correct the data
HC1045E
must be between 1 and 30. type or length and retry the operation.
Set scale must be between 1 and Set scale must be between 1 and length of Set. Correct the domain of your set type
HC1046E
length of Set. and retry the operation.
The entity or relation code is out of The entity or relation code is out of range. Internal error. Contact the System
HC1053E
range. Administrator.
HC1059E Internal Locking error occurred. Internal Locking error occurred. Internal error. Contact the System Administrator.
The entity query direction is invalid. Internal error. Contact the System
HC1070E The entity query direction is invalid.
Administrator.
HC1071E The commit flag is invalid. The commit flag is invalid. Internal error. Contact the System Administrator.
HC1072E The relation query mode is invalid. The relation query mode is invalid. Internal error. Contact the System Administrator.
The CRUD operation code is not The CRUD operation code is not valid. Internal error. Contact the System
HC1120E
valid. Administrator.
A Relation CRUD entity type is not A Relation CRUD entity type is not valid. Internal error. Contact your System
HC1121E
valid. Administrator.

Enterprise Development Messages - Part 1 HC1129E

System Id of this entity already System Id of this entity already exists. A user-defined object already exists in the
HC1129E
exists. enterprise repository. Review the actions that created this object.
The long name of this entity already The long name of this entity already exists. Determine if you want to create a new
HC1130E
exists. object or use
Parent of relation cannot be found. The parent object of a relationship object cannot
HC1131E Parent of relation cannot be found. be found in the enterprise repository. Review your actions and, if appropriate, create
the parent object.
Child of relation cannot be found. The child object of a relationship object cannot be
HC1132E Child of relation cannot be found. found in the enterprise repository. Review your actions and, if appropriate, create
the child object.
Copybook not found, or error found
HC1133E NEW
in Copybook Generation.
HC1138E PC Copybook Extension is Missing PC Copybook Extension is Missing Add the extension and retry the operation.
PC Copybook Extension can be 13 PC Copybook Extension can be 13 SBCS characters. Use valid characters and
HC1139E
SBCS characters. retry the operation.
Copybook extension must be in
Copybook extension must be in SBCS alphanumeric/national characters. Use valid
HC1140E SBCS alphanumeric/national
characters and retry the operation.
characters.
Copybook Name must be in SBCS Copybook Name must be in SBCS alphanumeric/national characters. Use valid
HC1141E
alphameric/national characters. characters and retry the operation.
Copybook Name can be 18 SBCS Copybook Name can be 18 SBCS characters long. Use valid characters and retry
HC1142E
characters long. the operation.
Copybook Name can be 18 SBCS
Copybook Name can be 18 SBCS characters, Extension can be 13 SBCS
HC1143E characters, Extension can be 13
characters. Use valid characters and retry the operation.
SBCS characters.
Creator Id in implementation name
Creator ID in implementation name must be in SBCS alphanumeric characters.
HC1146E must be in SBCS alphameric
Create the property using valid characters and retry the operation.
characters.
Creator Id in implementation name
Creator Id in implementation name cannot exceed 8 SBCS alphameric characters.
HC1147E cannot exceed 8 SBCS alphameric
Use valid characters and retry the operation.
characters.
Implementation name must not
Implementation name must not exceed 18 SBCS characters or 8 DBCS characters.
HC1148E exceed 18 SBCS characters or 8
Use valid characters and retry the operation.
DBCS characters.
Implementation name may not have Implementation name may not have double apostrophe(s). Use valid characters
HC1149E
double apostrophe(s). and retry the operation.
Length of Mixed data type cannot Length of Mixed data type cannot exceed 5000. Use valid characters and retry the
HC1150E
exceed 5000. operation.
Length of DBCS data cannot exceed 2000. Use valid characters and retry the
Length of DBCS data cannot exceed operation. HC1152E Length of DBCS data type must be between 1 and 15. Length
HC1151E
2000. of DBCS data type must be between 1 and 15. Use valid characters and retry the
operation.
HC1155E Short name generation failed. Short name generation failed. Internal error. Contact your System Administrator.
Cannot create project type SDS or Cannot create project type SDS or SEC, they are reserved project ids. Use another
HC1170E
SEC, they are reserved project ids. project ID and retry the operation.
File implementation name not legal File implementation name not legal for DB2 table name. Use a valid DB2 table
HC1172E
for DB2 table name. name and retry the operation.
Column Length must be greater Column Length must be greater than zero. Correct the property and retry the
HC1175E
than zero. operation.
Page Size must be greater than Page Size must be greater than zero and less than 501. Correct the page size and
HC1176E
zero and less than 501 retry the operation.
Line Size must be greater than zero Line Size must be greater than zero and less than 1000. Correct the line size and
HC1177E
and less than 1000. retry the operation.


Top Margin cannot exceed Page Top Margin cannot exceed Page Size. Correct the margin or page size and retry
HC1178E
Size. the operation.
Left Margin cannot exceed Line Left Margin cannot exceed Line Size. Correct the margin or line size and retry the
HC1179E
Size. operation.
Invalid value for X Resolution. Invalid value for X Resolution. (Range must be 1 4000). Correct the property and
HC1180E
(Range must be 1 4000) retry the operation.
Range must be between 1 4000 for Invalid value for Y Resolution. (Range must be 1 4000). Correct the property and
HC1181E
Y Resolution. retry the operation.
The implementation name of this entity already exists. You are using an
The implementation name of this
HC1184E implementation name that is not unique. Review the existing implementation name
entity already exists.
and respond as appropriate.
The user ID of this entity already
HC1185E The user ID of this entity already exists. Enter a unique ID.
exists.
The project ID of this entity already The project ID of this entity already exists. Enter a unique ID or review the object
HC1186E
exists. being edited or entered.
HC1190E Error deleting text. Error deleting text. Internal error. Contact your System Administrator.
HC1191E Error deleting keywords. Error deleting keywords. Internal error. Contact your System Administrator.
HC1192E Error deleting source. Error deleting source. Internal error. Contact your System Administrator.
HC1193E Error updating entity CRC table. Error updating entity CRC table. Internal error. Contact your System Administrator.
Error updating relation CRC table. Internal error. Contact your System
HC1194E Error updating relation CRC table.
Administrator.
Error updating relation. This relation Error updating relation. This relation is not found. Internal error. Contact your
HC1195E
was not found. System Administrator.
Error locking Parent entity of relation. Parent cannot be found. When a relationship
Error locking Parent entity of
HC1196E is locked, the parent is locked Review the ID that is locked and ask the owner to
relation. Parent cannot be found.
release it.
Error locking Child entity of relation. Error locking Child entity of relation. Child cannot be found. Review the ID that is
HC1197E
Child cannot be found. locked and ask the owner to release it.
Error locking relation for update. Review the descriptions for the accompanying
HC1198E Error locking relation for update.
messages.
Invalid Scope. An invalid entity or relationship object is entered. Correct the data
HC1200E Invalid Scope.
and retry the operation. See the System list of proper scope types.
Invalid Method Name for Scope. The method entered does not exist for this object
HC1201E Invalid Method Name for Scope.
type. See the System administrative guide for a list of method names and scopes.
Use Access Profile option only
applicable when Project is of type Invalid Method Name for Scope. The method entered does not exist for this object
HC1202E
model. Invalid Method Name for type. See the System administrative guide for a list of method names and scopes.
Scope.
Unable to retrieve entity deletion Unable to retrieve entity deletion hierarchy. Internal error. Contact your System
HC1210E
hierarchy. Administrator.
Unable to delete object hierarchy
due to error in deletion of
Unable to delete object hierarchy due to error in deletion of %1 %2 for the following
HC1211E &CRUDERR.ENTITY_TYPE
reason: Review the messages that follow.
&CRUDERR.ENTITY_NAME for the
following reason:
Average length should be within the Average length should be within the range of the field length. Change the property
HC1220E
range of the field length. and retry the operation.
Maximum value length should be Maximum value length should be within the range of the field length. Change the
HC1221E
within the range of the field length. property and retry the operation.
Minimum value length should be Minimum value length should be within the range of the field length. Change the
HC1222E
within the range of the field length. property and retry the operation.
Drawings can only be migrated Drawings can only be migrated using the Drawing scope type. The scope type is
HC7040E
using the Drawing scope type. wrong. Check your migration definition in the repository.

Enterprise Development Messages - Part 1 HC7041E

NonDrawings can not be migrated NonDrawings can not be migrated using the Drawing scope type. The scope type is
HC7041E
using the Drawing scope type. wrong. Check your migration definition in the repository.
NonPreparable objects can not be
NonPreparable objects can not be migrated using the Prepare scope type. The
HC7042E migrated using the Prepare scope
scope type is wrong. Check your migration definition in the repository.
type.
Scope type of Prepare Hierarchy is
HC7043E NEW
not supported in this release.
Windows can only be migrated
Windows can only be migrated using the Entity or Prepare Hierarchy scope type.
HC7044E using the Entity or Prepare
The scope type is wrong. Check your migration definition in the repository.
Hierarchy scope type.
Rebuild Package cannot be deleted
Rebuild Package cannot be deleted because the Rebuild state indicates processing
because the Rebuild state indicates
is not complete. To reset state, execute Cleanup method before deleting the entity.
HC7050E processing is not complete. To reset
You can not delete the Rebuild Package while you are working on it. To delete it, run
state, execute Cleanup method
the Cleanup and DE methods.
before deleting the entity.
A root entity can not be added while A root entity can not be added while the rebuild is in progress. To add the root entity,
HC7051E
the rebuild is in progress. run the Cleanup and ADDR methods.
A root entity can not be deleted A root entity can not be deleted while the rebuild is in progress. To delete the root
HC7052E
while the rebuild is in progress. entity, run the Cleanup and DR methods.
A root entity can not be updated A root entity can not be updated while the rebuild is in progress. To update the root
HC7053E
while the rebuild is in progress. entity, run the Cleanup and MR methods.
The application configuration is not The application configuration is not defined. Before using an application
HC7054E
defined. configuration, define it in the repository.
Only an exceptional process can be
HC7055E NEW
changed to a root object.
The migration object cannot be
deleted because the Migration state The migration object cannot be deleted because the Migration state indicates the
indicates the method is not method is not complete. To reset state, run the Cleanup method before deleting the
HC7056E
complete. To reset state, run the entity. You can not delete the migration object while you are working on it. To delete
Cleanup method before deleting the it, run the Cleanup and DE methods.
entity.
Your system options (INI variables) Your system options (INI variables) prohibit deletion of this entity. Contact your
HC7057E prohibit deletion of this entity. Please System Administrator. The System Administrator needs to set the appropriate flags
contact your System Administrator. in the INI file.
HC7058E Object has not been deleted. Object has not been deleted. Review the other messages.
The rule is already related to a
HC8031E The rule is already related to a process. A rule may be related to only one process.
process.
This rule is already attached to a This rule is already attached to a window. A rule may be attached to only one
HC8033E
window. window.
HC8034E This relationship already exists. This relationship already exists. As stated.
HC8035E This relationship already exists. This relationship already exists. As stated.
A Process can only be defined by a
A Process can only be defined by a single Rule. This Process is already defined.
HC8036E single Rule. This Process is already
As stated.
defined.
B2 error opening table DB2 error opening table R_WNDWNC. Internal error. Contact your System
HC8090E
R_WNDWNC. Administrator.
DB2 error, unable to delete row from DB2 error, unable to delete row from table R_WNDWNC. Internal error. Contact
HC8091E
table R_WNDWNC. your System Administrator.
DB2 error opening table DB2 error opening table R_WNCPNL. Internal error. Contact your System
HC8092E
R_WNCPNL. Administrator.
DB2 error, unable to delete row from DB2 error, unable to delete row from table R_WNCPNL. Internal error. Contact your
HC8093E
table R_WNCPNL System Administrator.
DB2 error, unable to delete row from DB2 error, unable to delete row from table E_PANEL. Internal error. Contact your
HC8094E
table E_PANEL. System Administrator.


DB2 error, unable to delete row from DB2 error, unable to delete row from table E_HELP. Internal error. Contact your
HC8095E
table E_HELP. System Administrator.
DB2 error opening table DB2 error opening table R_WNCHLP. Internal error. Contact your System
HC8096E
R_WNCHLP. Administrator.
DB2 error, unable to delete row from DB2 error, unable to delete row from table R_WNCHLP. Internal error. Contact your
HC8097E
table R_WNCHLP. System Administrator.
The field: %1 contains an invalid The field: %1 contains an invalid character for object: %2. Revise the objects
HC9100E
character for object: %2. property and retry the operation.
The field: %1 has an invalid first The field: %1 has an invalid first character for object: %2. Revise the objects
HC9200E
character for object: %2. property and retry the operation.
The field: %1 contains embedded The field: %1 contains embedded blanks for object: %2. Revise the objects
HC9300E
blanks for object: %2. property and retry the operation.
The field: %1 has an invalid domain The field: %1 has an invalid domain for object: %2. Revise the objects property and
HC9700E
for object: %2. retry the operation.
The field: %1 contains a nonnumeric The field: %1 contains a nonnumeric value for object: %2. Revise the objects
HC9800E
value for object: %2. property and retry the operation.
The field: %1 is blank but is required The field: %1 is blank but is required for object: %2. Revise the objects property
HC9900E
for object: %2. and retry the operation.
This can be a symptom of the following:-
- The requested rule does not exist in the CICS region.
- The 'vidtext' file is closed so the System cannot identify or find the rule.
- Garbage is passed with the transaction id.
HPS cannot locate the requested If a transaction is invoked (either directly or by another process) any extra data
HLM1
rule. passed is treated as a rule name and the System tries to find the rule in the vidtext
file. This can occur if a user enters TRIDxxxx instead of TRID or if bad data is
passed by the calling (MQ) process. If this is a case of MQ passing something funny
with the tran-id of the rule, then it may be possible to get around by explicity passing
the correct rule name.
Note Continued in the following section.

Enterprise Development Messages - Part 1 Continued in the following section.

CHAPTER
5 ENTERPRISE DEVELOPMENT
MESSAGES (PART 2)
This section completes the list of messages you may encounter when developing an application in an
enterprise (mainframe) environment. It lists messages from HMR001E to XWU012I. For messages from
DB2000E to HLM1, refer to Chapter 4, Enterprise Development Messages (Part 1).
Note For SVC Messages, refer to the IBM MVS/Extended Architecture System Programming Library: System
Macros and Facilities manual. These codes are specified in the SVC 99 Error Reason Codes sections.
Enterprise Development Messages (Part 2)

Table 5-1 completes the list of enterprise development messages from Chapter 4, Enterprise
Development Messages (Part 1).
Table 5-1 Enterprise Development Messages - HMR001E to XWU012I

The relation type is not found in user method exit. The variable
Relation type &RQST.ENTITY_TYPE not found in user
HMR001E &RQST.ENTITY_TYPE contains the relation type. Contact your
method exit
The entity type is not found in the user method exit. The
variable &RQST.ENTITY_TYPE contains the entity type. Entity
Entity type &RQST.ENTITY_TYPE not found in user type %1 not found in user method exit. The specified REXX
HMU001E
method exit EXEC is not in the EXEC libraries. Either System has not
provided the EXEC or a user has placed it in another data set.
Contact your System Administrator.
The operation completed successfully. The process completed
HM0000I No Errors
with no detected errors.
A DB2 error occurred while reading the specified table. Review
DB2 error reading %1 An error was encountered when
HM0001E and correct the operation. If the problem persists then contact
reading the specified DB2 table.
your DB2 administrator.
An error is encountered reading the specified file. Review any
return codes associated with this file. Correct any common
HM0003E Error reading file %1 problems associated with the file specified. Retry the
operation. If the problem persists then contact your System
Administrator.
An error is detected when opening the specified DD statement.
This message may be followed by other messages specifying
HM0004E Error opening DD statement %1 the cause of the error condition. Review and correct the JCL or
allocation statements causing the error. If the condition
persists then contact your System Administrator.
A System that is specified does not exist in the message file.
HM0005E missing or invalid: &MESSAGE_NUMBER Contact your System Administrator with the contents of the
message.

Enterprise Development Messages (Part 2) HM0006E
Table 5-1 Enterprise Development Messages - HMR001E to XWU012I (Continued)

An error is encountered opening the specified file. Review the
message or messages for common file errors. Correct these
HM0006E Error opening file %1
errors if possible. Retry the operation. If the problem persists
then contact your System Administrator.
The specified REXX variable is not found. Review and correct
HM0008E Undefined rexx variable %1
the variable.
An error occurred writing to the specified file. An I/O error
occurred attempting to write the specified file. Review any
HM0009E Error writing %1 file additional messages that are displayed. Correct the problem if
possible and retry the operation. If the problem persists then
contact your System Administrator.
An internal error has occurred in the System software. Contact
HM0011E %1 %2 does not exist
your System Administrator with the contents of the message.
HM0012E Variable %1 invalid or not found
An operation has exhausted all available system memory. 1.
Retry the operation again. System resources may have been
heavily used during the first execution. Attempt execution
during off peak system times if possible. 2. Allocate more
memory to the specific operation. If the operation is a batch
operation then retry the operation by increasing the region
HM0013E Out of memory in module %1
allocated to the batch operation by specifying a REGION
statement on the job card. If the operation is a online operation
then have your systems personnel allocate more memory to
your session. 3. Reduce the scope of the operation. Certain
memory requirements can be reduced by limiting the scope of
data that the operation will access.
An error occurred during a file positioning operation. Contact
HM0014E Error restoring file position for file %1
HM0015E Internal Error
A file input/output error has occurred. Review this message
and any other additional messages that may exist. Correct the
HM0016E File I/O error occurred, File=&RQST.FILE
problem if possible and retry the operation. If the problem
Onsource=&RQST.ONSOURCE, Onchar=&RQST.ONCHAR
The message contains abend information and will be displayed
HM0017E Oncode=&RQST.ONCODE, Onloc=,&RQST.ONLOC,
with other messages. Contact your System Administrator with
the contents of this message.
A file open error has occurred. Review the error and any
additional messages that may appear. Attempt to correct the
HM0018E File open error occurred, File=&RQST.FILE
problem if possible and retry the operation. If the problem
An error occurred while saving the position of the specified file.
Review any other messages that may appear with this
HM0019E Error saving file position for file %1
message and attempt to correct the problem. If the problem
An internal error is detected during processing. Contact your
HM0020E Illegal record length
System Administrator with the contents of this error.
An internal error is detected during processing. An unexpected
HM0021I End of file occurred on read EOF error is encountered while performing a file read. Contact
your System Administrator with the contents of this message.
A file read error occurred. The error number is displayed.
HM0022E File read error occurred. Msg: %1 Contact your System Administrator with the contents of this
message.
The audit properties were not valid for this object. Contact your
HM0023E Invalid audit data
System Administrator with the contents of this message.

HM0024E Enterprise Development Messages (Part 2)

The audit information is missing for the specified
HM0024E Invalid audit information in field %1 property.Contact your System Administrator with the contents
of this message.
An internal error is detected by the system software. Contact
HM0025E Invalid control block data in field %1
The specified rule has not been prepared successfully prior to
Rule %1 has not been prepared. RBD requires a
HM0026E executing the RBD method. Prepare the rule successfully using
successful rule prepare.
the PR method and then reissue the RBD method.
The entity with the system ID of &ERROR.ENTITY_ID does not
The entity with the system ID of &ERROR.ENTITY_ID
HM0027E exist. The entity with the specified system ID can not be found.
does not exist.
Review and correct the request for this system ID.
The entity with the specified long name does not exist in the
The entity with the long name of &ERROR.ENTITY_ID
HM0028E repository. The entity with the specified long name can not be
does not exist.
found. Review and correct the request for this long name.
An error is encountered while closing the specified file. Contact
HM0029E Error closing file %1
An error is encountered while executing the specified method.
Review any other additional messages that were displayed
HM0030E %1 method has failed due to an error
with this message. Correct any problems and retry the
operation.
An error is detected in module HMCCFGI and the specified
HM0031E %1 failed due to an error in module HMCCFGIAction
method failed. Review and correct the specified item.
The specified method must have a plan name on the
%1 requires plan name on the R_CUECXX relationship
HM0032E (Configuration Unit Encapsulates Entity) R_CUECXX
Action
relationship. Review and correct the plan name.
The specified method must have COLLECTION_ID values on
%1 requires COLLECTION_ID values on the the Configuration Unit Encapsulates Entity) R_CUECXX or
HM0033E
R_CUECXX or E_CFGUNIT tableAction (Configuration Unit Entity) E_CFGUNIT table. Review and
correct the required method values.
%1 requires plan name on the E_CFGUNIT The specified method requires plan name on the E_CFGUNIT
HM0034E
relationshipAction relationship. Review and correct the plan name.
The Activate method is a required operation before you can
ACTIVATE method is a prerequisite operation to
HM0035E use the specified method. Review and employ the Activate
%1Action
method appropriately.
A Collection ID is required when the DB2.PCKG INI variable =
'P' or 'V'. Your repository has package binding enabled and a
collection id is not available for binding. Contact your System
A Collection ID is required when binding your
HM0036E Administrator and have them review the DB2 INI file settings
applications using packages.
for this repository and version. A detailed description of DB2
considerations can be found in chapter 20 in The MVS
Environment.
The specified tailor file name cannot be filed. Review and
HM0037E Cannot file tailor filename %1.Action
correct the use of the specified file.
The file specified does not contain any data. The action
specified has been cancelled. The file or the contents may
HM0038E The file is empty and the action is unavailable
have been previously deleted. Retry the operation necessary
to populate the file and retry your action.
The file specified may be a secure file or is no longer available
HM0039E The file cannot be deleted to your system. Retry the deletion. If the problem persists then
The execution environment for the specified entity and system
%1 %2 has an invalid execution environment for this
HM0040E Id is invalid for this method. Review and invoke a consistent
method.Action
execution environment.

Enterprise Development Messages (Part 2) HM0042I

There are not any result files available for processing. The
anticipated results for the specified item is not found. This may
HM0042I There are no results for &RQST.Y_LNAME
be due to the fact that the item has no results or the result file
may no longer be available on your system.
The file name associated with the DD name HMFPRNT cannot
HM0043E Cannot open output printer file be opened. The attempt to open the printer file is unsuccessful.
Review and correct the output printer name or allocation.
The specified window is not prepared. The TS method
HM0050E Window %1 has not been prepared. requires a successful Window prepare. Prepare the specified
Window method and retry the TS method.
The keyword search failed because an illegal token starting
Illegal token starting with character &TOKEN in keyword
HM0051E with the specified character is in the keyword search text.
search text.
Review and correct the illegal token in the keyword search text.
One of the single quotes in the keyword search text does not
have a matching single quote. Review the search text and
HM0052E Mismatched single quote in keyword search text.
correct the search text so that it contains a even number of
single quotes. Retry the search operation again.
There is a odd number of parenthesis in the keyword search
HM0053E Mismatched parentheses in keyword search text. text. Review the search text, and correct the parenthesis so
that a even number of parenthesis exist. Retry the operation.
An error occurred in the keyword search program that is
described by the specified DB2 return code. Review the
keyword search text for invalid syntax. The keyword search
An error occurred in the keyword search program.
HM0054E facility uses a DB2 Like clause to perform the keyword search.
Return code = &RETCC.
The return code will represent the DB2 SQL return code in the
DB2 Messages and Codes manual. Review the query and
correct the syntax. Retry the keyword search again.
The search string contains invalid characters within the search
text.The keyword search program failed because of an illegal
HM0055E Illegal token or statement in keyword search text.
token or statement. Review and correct the error in the
keyword search text.
The attempt to match rows with specified pattern is
HM0056E The search pattern specified did not match any data. unsuccessful. Review and correct the search criteria specified
and retry the request.
An attempt to browse the source is unsuccessful. Review and
HM0057E Unable to browse source Action
correct the request to browse.
Package Binds are unsupported when the INI variables
DB2.PCKG is set to 'P' and the DB2.PKLIST INI variable is set
HM0059E Explicit package binds are not supported
to 'E'. Contact your System Administrator and have them
correct the bind INI file settings.:
HM0060E Keyword Search ResultsAction MATCHING SEARCH ITEMS: AS STATED.
To Browse Keywords, select one or more objects. Then press
To browse keywords, select one or more objects. Then ENTER. This informational message teaches how to use
HM0061I
press ENTER. browse. To browse keywords, first select some object(s), and
then press the Enter key.
The partitioned data set could not be opened properly.Review
the allocations specified for the partitioned data set. If the data
Specified partitioned data set could not be opened for
HM0068E set is temporarily unavailable then retry the operation at a later
output
point in time. If the problem persists then contact your System
Administrator.
The specified data set has a requirement of an eight byte
logical record length and the data set does not conform to this
HM0069E Logical record length of data set must be eighty bytes requirement. Contact your System Administrator to change the
allocation for the data set to have a logical record length of
eighty bytes.


The record format of the data set must be fixed (F) or fixed
block (FB) during allocation. Contract your System
HM0070E Record format of data set must be fixed or fixed block Administrator with the contents of this message. The specified
data set must be allocated as a fixed format data set. Once the
file has been allocated properly then retry the operation.
The specified PDS member already exists in the library. You
Member already exists, specify new name or YES to the can overwrite this member by specifying yes to the replace
HM0071W
Replace option. option. Determine whether or not to overwrite the specified
member and continue.
The data set specified does not exist in the library. Determine if
the data set should have existed prior to this operation. If so,
HM0072E Specified partitioned data set does not exist. then determine if the data set is temporarily unavailable on this
system. Retry the operation at a later time. If the problem
exists then contact your System Administrator.
A fully qualified partitioned data set name must have matching
HM0073E Unbalanced quotes in partitioned data set name.
quotes. Correct the quotes and retry the operation.
An error is found in the syntax of the partitioned data set name.
HM0074E Error in specifying partitioned data set member name. Ensure that the name conforms with MVS naming conventions.
Correct the problem and retry the operation.
The DB2.PCKG variable for this repository is set to package
binds. The component rebind method does not support the
Package Binds are unsupported for this method. Use binding of packages for components. Use the BINDPKG
HM0075E
the BINDPKG method to rebind the package method to rebind the package associated with this component.
Have your System Administrator review the INI settings for this
repository if you believe that this message is in error.
The DB2 package bind requires a collection ID value. Contact
HM0076E A Collection ID is required for DB2 rules. your System Administrator and have them review the DB2 INI
file settings for this repository.
Exit the SRCH method. Please report the DB2 error to Exit the SRCH method. Report the DB2 error to your System
HM0090I
your System Administrator. Administrator.
The Collapse option is only valid for Rules with the specified
The Collapse option is only valid for Rules with an
HM0091E execution environment. Correct the execution environment or
execution environment of %1
remove the collapse request and retry the operation.
The Collapse option is only valid for Rules with an execution
HM0093E Invalid entity type specified: %1 environment of %1. The Collapse option is only valid for Rules
with an execution environment of %1.
The version specified %1 is not defined in the repository. Enter
HM0094E Invalid Version Specified: %1
a valid version.
The Collapse option is only valid for Rules with an execution
HM0095E The name value: %RQST.NAME exceeds 26 bytes
environment of %1
The Entity type is unsupported for this method. An error
HM0100E Unsupported Entity type occurred: The entity type is invalid. Review and correct the
entity type.
The limitation of only one IN/INOUT view is exceeded. Review
HM0101E Only one IN/INOUT View is allowed
and correct the number of IN/INOUT views.
Only one OUT/INOUT View is allowed per an application
hierarchy. The limitation of only one OUT/INOUT view is
HM0102E Only one OUT/INOUT View is allowed
exceeded. Review and correct the number of OUT/INOUT
views.
An error occurred when reviewing the entity. This section
HM0103E Duplicate Section duplicated an existing section. Review and correct the
duplication.
There are no fields defined for a view. The
There are no fields defined for VIEW: &RQST.VIEW_LNAME is substituted by the Views Long name.
HM0104E
&RQST.VIEW_LNAME An error occurred when the specified view is found having no
defined fields. Review and correct the missing fields.


The member receiving the error is displayed in the %2 variable.
HM0105E Cannot open file for DD: %1, Member %2 An error is detected when attempting to open a file for the
specified DD and member. Review and correct the statement.
EVENT has no views (must be coded as INOUT) An error
HM0106E EVENT has no views (must be coded as INOUT) occurred because an Event without a view must be coded as
INOUT. Correct the code for Event.
The requested entity is not found. The
&ERROR.ENTITY_TYPE variable is substituted with the
&ERROR.ENTITY_TYPE &ERROR.ENTITY_ID Not Entities entity type. The &ERROR.ENTITY_ID variable is
HM0107E
Found substituted with the Entities System ID. An error is detected
when the specified Entity Type and ID is not found. Review and
correct the missing entity.
The variable &RQST.LNAME is the long name of the rule. The
The rule &RQST.LNAME is invalid for a DB2 Bind. No hierarchy is searched but no additional DB2 rules were found.
HM0108E
rules in the rules hierarchy are marked as DB2. Either change the hierarchy to include DB2 or remove the DB2
code from the prepared entity.
The length specified for a rule defined as Varchar exceeds the
maximum length of 26 bytes. The variable
&RQST.FIELD_LNAME The calculated length for
HM0109E &RQST.FIELD_LNAME is the long name of the field. Change
Description of a VARCHAR field exceeds 26 bytes.
the length of the Varchar field to be less than or equal to 26
bytes.
A parameter error occurred: There is either an invalid
HM0110E Invalid number of Parameters or Invalid Parameter parameter or invalid number of them. Review and correct the
parameters.
Encountered a problem with an Empty PDS. An error is
HM0111E Encountered a problem with an Empty PDS detected when a PDS member list is executing. Review and
correct the PDS member list operation.
An attempt is made to access a view that doesn't exist. The
&VIEWID variable displays the view system ID. Review the
HM0112E VIEW &VIEWID does not exist application to insure the specified view is valid. You may have a
dangling relationship to a view that is removed from the
repository. Correct the relationship or view entity.
Encountered an error in the FT generation of the requested
HM0113E Encountered an FT error
method. Internal FT error. Contact your System Administrator.
This method is only applicable to objects preparable on the
Mainframe. The value 'ReBind DB2 Plans' is displayed in the
variable RQST.METHOD_ID. The entity that you are
&RQST.METHOD_TEXT is only applicable to objects
HM0114E performing the method on must have DB2 usage in its
preparable on the mainframe platform.
hierarchy. The entity must have a valid execution environment
on the mainframe. Review and correct the entity or entities
hierarchy.
The parameter %1 is replaced by the Entity type. An Error is
HM0115E Source code is missing for this &ERROR.ENTITY_TYPE detected in the specified entity: Its source code is not found.
Review and correct the missing source code problem.
The language of the sub Component must match the language
of the parent component. The value of the %1 variable is the
Component &SUBCOMP Language does not match the sub Components System ID. The value of the %2 variable is
HM0116E
Parent Component &PARCOMP the parent components System ID. The specified component
language and the specified parent component did not match.
Review and correct the inconsistency.
Components marked as Subroutines cannot be prepared. The
Component &RQST.LNAME is marked as a %1 parameter is replaced by the Components system ID. If the
HM0117E
SUBROUTINE and cannot be prepared. component is not a subroutine, maintain the entity and modify
the subroutine indicator.
Requested method will not be available until General
Requested method will not be available until General Availability. The method employed is not supported in this level
HM0118I
Availability. of code. Use the method when you have applied the General
Availability version.

HM0119I Enterprise Development Messages (Part 2)

Requested method is designated for future use. The method
HM0119I Requested method is designated for future use.
employed is not supported in this level of code.
Support for execution environment is not installed. The variable
Support for execution environment &RQST.EXEC_ENVIRON is replaced by the entitys execution
HM0120E
&RQST.EXEC_ENVIRON is not installed. environment. The specified execution environment does not
have support installed. Contact your System Administrator.
Support for execution environment CICS or IMS is not installed.
Support for execution environment CICS or IMS is not
HM0121E Execution environment CICS or IMS is not installed. Contact
installed.
your System Administrator.
Invalid Operating System on Machine Entity for the activated
Invalid Operating System on Machine for the activated
HM0122E Configuration Unit. Modify the machine type on the relationship
Configuration Unit.
from the Configuration Unit to the Machine entity.
This method is not supported for components used as
&RQST.METHOD_TEXT is not supported for subroutines. The %1 parameter is the Method that is executed.
HM0123E
component subroutines. Reinstall method does not support the preparation of
component subroutines.
Source code is missing the entity. The &ENTITY parameter is
Error in Creating Source code for ENTITY:%1 the entity type. The &SYSTEM parameter is the system ID. The
HM0124W
SYSTEMID:%2 VERSION:%3 &VERSION parameter is the Version. Add Source code for the
Entity.
This method is only applicable for CICS components. LU2
&RQST.METHOD_TEXT is only applicable for CICS
HM0125E installation is only relevant for components with a valid
components.
mainframe execution environment.
This method is only supported when the System CICS
&RQST.METHOD_TEXT is only supported when the autoinstall feature is activated. The value of the %1 variable is
HM0126E
System CICS autoinstall feature is activated. the method executed. Ask your System Administrator to install
the feature.
This method is only applicable to reports preparable on the
&RQST.METHOD_TEXT is only applicable to reports Mainframe platform. The %1 parameter is replaced by the
HM0127E
preparable on the Mainframe platform. method Id. This method is only supported for reports with a
valid mainframe execution environment.
Support for Report Writer is not installed. Ask your System
HM0128E Support for Report Writer is not installed.
Administrator to install the Report Writer AVX.
Source code is missing for the Entity. The &ENTITY parameter
Source code is missing for &ERROR.ENTITY_TYPE is the entity type. The &SYSTEM parameter is the system ID.
HM0129E
&RQST.SYSTEMID Run the source method or download it to the PC and enter it
there for the affected entity.
Override Values taken for RQST.BINDPARM is
Override Value taken for &RQST.BINDPARM is
HM0130I &RQST.BINDVAL. The &RQST.BINDPARM parameter is the
&RQST.BINDVAL
NEW
A configuration unit requires a relationship to a machine entity.
A Machine object must be associated to the activated
HM0131E Create a relationship to an activated configuration unit by
Configuration Unit.
issuing an ADDR or ASSIGNCU method.
A configuration unit requires a relationship to a machine entity.
HM0132E Member already exists in the DB2 table Create a relationship to an activated configuration unit by
The &error.table parameter is the name of the internal table. A
Internal error, table &error.table exceeds &error.entries configuration unit requires a relationship to a machine entity.
HM0133E
entries. Create a relationship to an activated configuration unit by
The language of the mainframe component is not valid for
mainframe preparation. The value of the &RQST.LANGUAGE
The Language &RQST.LANGUAGE of Component variable is the components source language. The value of the
HM0134E &RQST.LNAME is unsupported on the Mainframe &RQST.LNAME is the long name of the component. If the
platform. component requires mainframe preparation, change the
Language of the component to one supported on the
mainframe.


&RQST.METHOD not available when the Configuration This method is not available when the Configuration Indicator
HM0140I Indicator is off. Please see your Repository System is off. The &RQST.METHOD parameter is the method ID.
Administrator. Contact your Repository System Administrator.
&RQST.METHOD not available when the Package This method is not available when the package indicator is off.
HM0145E Indicator is off. Please see your Repository System The &RQST.METHOD parameter is the method ID. Contact
Administrator. your Repository System Administrator.
The method is processed successfully. The %1 parameter is
the method name. The %2 parameter is the entitys long name.
HM0150I %1 for %2 V: &RQST.VERSION processed
The &RQST.VERSION variable is the Version. The method is
processed successfully.
%1 for %2 V: %3 ended with Errors. The given entity for this
HM0151E %1 for %2 V: &RQST.VERSION ended with Errors
version ended with Errors
The user cancelled the method for the entity. The %1
parameter is the method name. The %2 parameter is the
HM0152I %1 for %2 V: &RQST.VERSION was Cancelled
entitys long name. The &RQST.VERSION variable is the
Version. Reissue the method if necessary.
The method is processed successfully. The %1 parameter is
&RQST.METHOD for &RQST.ENTITY_ID V: the method name. The %2 parameter is the entitys long name.
HM0153I
&RQST.VERSION processed The &RQST.VERSION variable is the Version. The method is
processed successfully.
The method ended with Errors. The %1 parameter is the
&RQST.METHOD for &RQST.ENTITY_ID V: method name. The %2 parameter is the entitys long name.
HM0154E
&RQST.VERSION ended with Errors The &RQST.VERSION variable is the Version. Review and
correct the errors. Execute the method again if necessary.
The requested method is cancelled. The %1 parameter is the
method name. The %2 parameter is the entitys long name.
&RQST.METHOD for &RQST.ENTITY_ID V:
HM0155I The &RQST.VERSION variable is the Version. The user
&RQST.VERSION was Cancelled
cancelled the method for the entity. Execute the method again
if necessary.
The method is processed. The %1 parameter is the method
HM0156I %1 processed name. This informational message confirms that the specified
method finished processing.
The method ended with Errors. The %1 parameter is the
HM0157E %1 ended with Errors method name. Review and correct the errors. Execute the
method again if necessary.
The method is cancelled. The %1 parameter is the method
name. Processing for the specified method is cancelled.
HM0158I %1 was Cancelled
Review why the method is cancelled and resubmit if
necessary.: HM0169I
Browse is in effect because a security or locking check error
Browse of data displayed due to security or locking occurred. This entity may be locked by another user or you
HM0170I
constraints may not have the proper authorization to access this object.
Contact project administrator to determine your level of access.
Missing Database Directory Path for the activated Issue the ME method and add a valid DBRM library name in
HM0171E
Configuration Unit. the database directory field for the activated configuration unit.
The Database entity is missing its Implementation name.
HM0172E IMP_NAME Missing for DATABASE entity.
Correct the IMP_NAME field on the DATABASE entity.
A Database object must be associated to the activated
A Database object must be associated to the activated
HM0173E Configuration Unit. To correct this error, you must associate the
Configuration Unit.
Database object to the activated Configuration Unit.
The variable &RQST.CFGDSPL is the configuration units
HM0174I Configuration Unit Name.. : &RQST.CFGDSPL name. If the value is incorrect, see your Repository System
Administrator.
The variable &RQST.MACDSPL is the Machine entitys name.
HM0175I Machine Name....... : &RQST.MACDSPL If the value is incorrect, see your Repository System
Administrator.


The variable &RQST.DATDSPL is the Database entitys name.
HM0176I Database Name....... : &RQST.DATDSPL If the value is incorrect, see your Repository System
Administrator.
The variable &RQST.SVRDSPL is the Servers name. If the
HM0177I Server Name........ : &RQST.SVRDSPL
value is incorrect, see your Repository System Administrator.
The INI file defined by the Machine implementation name is not
INI file for Machine implementation name &RGNINI1 is defined. The &RGNINI1 variable is the name of the Region INI
HM0178E
not defined. file. Contact the System Administrator to create the INI file for
the Machine implementation name.
Machine Implementation Name : &RQST.MACINAMHM0180I
The variable &RQST.MACINAM is the Machines Machine OS Type...... : &RQST.MACOSTY The variable
HM0179I
implementation name. &RQST.MACOSTY is the Machines OS Type. If the value is
incorrect, see your Repository System Administrator.
The variable &RQST.CFGDSPL is the Database entities
HM0181I Database Implementation Name: &RQST.DATINAM Implementation name. If the value is incorrect, see your
Repository System Administrator.
The variable &RQST.DATDTYP is the Database entitys type. If
HM0182I Database Type....... : &RQST.DATDTYP the value is incorrect, see your Repository System
Administrator.
HM0183I Database Directory Path.. : This text contains the string 'Database Directory Path'.
HM0184I Application Configuration: This message contains the text 'Application Configuration'
DB2 Options: This message contains the text 'DB2
HM0185I NEW
Options:'
This message contains the text: 'Bind Mode......... : N (Plan,
HM0186I Bind Mode......... : N (Plan, DBRM Member list)
DBRM Member list)'
The variable &RQST.DB2COLL is the DB2 Collection ID. If the
HM0187I Collection Id....... : &RQST.DB2COLL
The variable &RQST.DB2OWNR is the DB2 Owner ID. If the
HM0188I Owner Id......... : &RQST.DB2OWNR
The variable &RQST.DB2QUAL is the DB2 Qualifier ID. If the
HM0189I Qualifier Id....... : &RQST.DB2QUAL
The variable &RQST.USECFGU determines whether Config
HM0190I Use Configuration Unit.. : &RQST.USECFGU Units are supported in the repository version. If the value is
incorrect, see your Repository System Administrator.
This message displays the following text: 'Database Type....... :
HM0191I Database Type....... : DB2 DB2' If the value is incorrect, see your Repository System
Administrator.
This message displays the following text: 'Machine OS
HM0192I Machine OS Type...... : CICS/MVS Type...... : CICS/MVS' If the value is incorrect, see your
HM0193I Machine OS Type...... : MVS Batch Type...... : MVS Batch' If the value is incorrect, see your
HM0194I Machine OS Type...... : IMS Type...... : IMS' If the value is incorrect, see your Repository
The variable &RQST.ENTITY_TYPE is the Entity type. If the
HM0195I &RQST.ENTITY_TYPE Prepare Processing Options
The variable &RQST.DATDIRY is the DBRM library used
HM0196I &RQST.DATDIRY during the DB2 bind operations. If the value is incorrect, see
your Repository System Administrator.
This message displays the following text: 'Bind Mode......... :
HM0197I Bind Mode......... : P (Package, Project Mode) P (Package, Project Parameters)' If the value is incorrect, see


This message displays the following text: 'Bind Mode......... :
HM0198I Bind Mode......... : V (Package, Version Mode) V (Package, Version Parameters)' If the value is incorrect, see
This message displays the following text: 'Installed Products:' If
HM0199I Installed Products: the value is incorrect, see your Repository System
Administrator.
The version of the entity or relation is not found, Review and
HM0200E Version of entity or relation is missing
correct the missing version.
The %1 parameter contains the internal entity or relation code.
The specified entity or relation code is not found. Review and
HM0201E Entity or relation code %1 does not exist
correct the nonexistent code or contact your System
Administrator.
No Window Content exists for the Window. The variable
&RQST.LNAME contains the Windows long name. The
HM0202E No Window Content exists for Window &RQST.LNAME
specified window had no content. Review and correct the
window contents.
The entitys file type on the mainframe must be DB2. The %1
HM0203E File &RQST.LNAME has invalid file type, must be DB2 parameter contains the file long name. The file type of specified
item is invalid. Review and correct the file type to be DB2.
The 3270 Converse is not installed. Ask your System
HM0204E 3270 Converse not installed.
Administrator to install the 3270 Converse AVX.
No DATA View is defined for the File. The variable
&RQST.LNAME contains the Files long name. The specified
HM0205E No DATA View is defined for FILE &RQST.LNAME
file had no defined data view. Review and correct the data view
definition for the file.
Multiple DATA views exist for the File. The variable
&RQST.LNAME contains the Files long name. The specified
HM0206E Multiple DATA views exist for FILE &RQST.LNAME
file had more than one defined data view. Review and correct
the data view definition for the file.
The 3270 Converse load process failed. This is not an error if
the set being prepared doesn't require 3270 converse. The
The 3270 Converse load failed, the return code is
HM0207W variable &RQST.RETCC is a System program return code.
&RQST.RETCC
Otherwise, review the Batch prepare job results or contact your
The files Implementation name is missing or invalid. The %1
Implementation name for file &RQST.LNAME is missing parameter contains the File entitys name. The specified file
HM0208E
or invalid has an implementation name that is either missing or invalid.
Review and correct the implementation name for the file.
The Source code for the Component is missing. The variable
HM0210E Source code for Component &RQST.LNAME &RQST.LNAME is the Components long name. Create source
code for the Component.
Components can not be submitted using Project SEER2. Only
HM0211E Components can not be submitted using Project SEER2
a System Administrator can prepare using project SEER2.
No 3270 Window Content is found for the Window. The
variable &E_WINDOW.LNAME is the Windows long name. The
No 3270 Window Content found for Window
HM0212E specified window did not have a 3270 WINCON. Download the
&E_WINDOW.LNAME
window, create the panel on the Development Workbench, and
upload the window to the mainframe.
The 3270 Converse product is not installed. The variable
3270 Converse not installed. Cannot prepare WINDOW
HM0213E &RQST.LNAME is the Windows long name. See your System
&RQST.LNAME
Administrator to install the 3270 Converse AVX.
A PDS data set is missing. The Entity cannot be prepared. The
Missing &LIBPDS library. Cannot prepare variable &RQST.Y_ENTITY_TYPE is the entity type. The
HM0214E
&RQST.Y_ENTITY_TYPE variable &LIBPDS is a Partitioned data set name. See your
System Administrator to allocate the PDS.


The generation of the System bind file failed. The variable
&RQST.Y_ENTITY_TYPE is the entity type. The variable
Bind file for &RQST.Y_ENTITY_TYPE &RQST.LNAME
HM0215E &RQST.LNAME is the entitys long name. The Bind file for the
is not generated.
specified entity type was not generated. Review and correct
the entity type and its required Bind file.
The load of the window prepare HELP text failed. The variable
Load of Help for &RQST.Y_ENTITY_TYPE &RQST.LNAME is the entitys long name. A window prepare
HM0216E
&RQST.LNAME failed. error. The PNV is not found. You may have to upload your
Window to the mainframe. Otherwise, contact your System
Administrator.
The load of the window prepare PNV file failed. The variable
Load of PNV for &RQST.Y_ENTITY_TYPE &RQST.LNAME is the entitys long name. A window prepare
HM0217W
&RQST.LNAME failed. error. The PNV is not found. You may have to upload your
Window to the mainframe. Otherwise, contact your System
Administrator.
User only allowed BROWSE authorization on this object. See
HM0218W User only allowed BROWSE authorization on this object. your System Administrator if you require administrative access
other than browse.
Error trying to Lock object requested. Lock attempt failed. A
Error trying to Lock object requested. Lock attempt
HM0219E lock failure occurred when attempting to lock a required object.
failed.
Review and correct the lock request.
Error trying to Unlock the object. Invalid authorization. An
invalid authorization failure is detected when the user
HM0220E Error trying to Unlock the object. Invalid authorization.
attempted to unlock an object. Review and correct the unlock
request.
Error trying to Unlock the object. Unlock failure occurred. An
HM0221E Error trying to Unlock the object. Unlock failure occurred. unlock failure is detected when the user attempted to unlock an
object. Review and correct the unlock request.
User not authorized to perform request. Changing to Browse
User not authorized to perform request. Changing to
HM0222W mode. See your System Administrator if you need
Browse mode.
administrative access other than browse.
The object is currently locked by another user. Your access is
HM0223W Object currently locked. Changing to Browse mode. being changed to browse. Contact your System Administrator if
you are unable to resolve your locking conflict.
No HELP or PANEL member found for Window Content. The
variable &RQST.TYPE is either HELP or PANEL. The variable
No &RQST.TYPE found for Window Content
HM0224E &RQST.WINCON is the Window Contents name. Download the
&RQST.WINCON
A DB2 error occurred during processing. The &RQST.WINCON
variable is the Window Content name. The &table is the DB2
DB2 error on table &table processing Window Content table that the error occurred against. Review the RES files of
HM0225E
for &RQST.WIN CON the entity to diagnose the DB2 error. Confirm that your window
content is complete. If necessary, contact your System
Administrator.
A DB2 error occurred processing the Window Content of the
Window. The &E_WINDOW.LNAME is the windows long
DB2 error processing Window Content for Window name. Review the RES files of the entity to diagnose the DB2
HM0226E
&E_WINDOW.LNAME error. The window content may be missing. If necessary,
download the window, create the content on the Development
Workbench, and upload the window to the mainframe.
No HELP or PANEL member found for Window Content. The
variable &RQST.TYPE is either HELP or PANEL The variable
No &RQST.TYPE found for Window Content
HM0227E &RQST.WINCON is the Window Contents name. Download the
&RQST.WINCON


3270 Converse not installed. Cannot prepare SET: Cannot prepare the specified SET. Ask your System
HM0228E
%1.Action Administrator to install the 3270 Converse AVX.
Rebind job for Component has been submitted
HM0230I Rebind job for Component has been submitted successfully
successfully retcc.
The Component entity is locked by another user. Determine
HM0231E Component is locked why the entity is locked. If you need the entity unlocked, see
You can invoke Rebind for mainframe components only.
HM0232E Rebind may be invoked only for Mainframe Components
Review and correct the use of Rebind.
ReBind DB2 Plans may be invoked only for Mainframe
Components that use DB2. If the Component is required to
Rebind DB2 Plans may be invoked only for Mainframe
HM0233E have DB2 processing you must review its hierarchy. The
Components that use DB2.
Component must have a child relationship to a rule that has
DB2 in its hierarchy.
Rebind method has failed due to an error. Review your
HM0234E Rebind method has failed due to an error Component entity RES files to diagnose the problem. If you
receive DB2 errors, see your System Administrator.
The parent rules are missing, so the rule may be a PC rule.
HM0235E There are no parent rules found. Rule may be PC rule.
Review and correct the rule if appropriate.
No parent rules are eligible for Rebind. If a rule and or
HM0236E No parent rules are eligible for Rebind. component in the hierarchy is DB2 it must be marked as DB2.
Change the DB2 usage to DB2 if necessary.
Submit command is invalid since no selections have
HM0237E The Submit command is invalid when selections are not made.
been made.
The text message follows: '* Rebind Statements Built.' This
HM0238I * Rebind Statements Built. informational message confirms the Rebuild statements were
successfully constructed.
No DBRMs found for any Entities within the hierarchy. You may
HM0240E No DBRM's found for any Entities within the hierarchy need to prepare rules and/or components in the application
hierarchy.
The plan ID for the rule is missing. Reprepare the rule to The plan identifier for the rule is missing from the E_RULE
HM0241E
generate another plan id. table. Prepare the rule to generate a DB2 plan name.
Errors occurred in HMCALCAT, see output message file Error in HMCALCAT program. Review your Res files. If the
HM0242E
for details error persists, contact your System Administrator.
The HMCRXM program has failed due to an error. Review your
HM0243E RB method has failed due to an error Res files. If the error persists, contact your System
Administrator.
Configuration error: The specified maximum transaction id
Configuration error: The specified maximum TRANID exceeds the calculated maximum transaction id for the
HM0244W (%1) exceeds the calculated maximum TRANID (%2) for specified region. Review the region bit table settings. The
region %3 estimated maximum bit setting may have been exceeded.
Report the error to the System Administrator.
There are no transaction codes defined for the specified
region. The %1 parameter is the Region Name. The CICS,
Batch or IMS region for this version has not been configured
with a transaction bit table. All processing regions must have a
HM0245E There are no transaction codes defined for region %1.
transaction range configured by the System Administrator.
Notify your local administrator and request a transaction bit
table be configured in the CM_TRAN table for the region and
version that you are using.
Keyword Data cannot be longer than 240 characters. Review
HM0246W Keyword Data cannot be longer than 240 characters and reduce the length of Keyword data to less than or equal to
240 bytes.
Keyword Data too long. An error occurred while processing the
HM0247W The keywords for this object exceed 255 bytes. keywords. Review the keywords for this object and reduce the
size. Keywords cannot exceed 255 bytes in length.

HM0248W Enterprise Development Messages (Part 2)

An ISPF table display error has occurred. The variable
&RQST.TABLE is an internal ISPF table used during method
Table display error, Table name=&RQST.TABLE,
HM0248W processing. The variable &RQST.TBDISPRC is the return code
RC=&RQST.TBDISPRC
received from ISPF table display processing. Report the error
to your System Administrator.
A Transaction is not created for the specified region. The %1
parameter is the name of the Region. The CICS, Batch or IMS
region for this version has not been configured with a
transaction bit table. All processing regions must have a
HM0249E A Transaction was not created for region %1
transaction range configured by the System Administrator.
Notify your local administrator and request a transaction bit
table be configured in the CM_TRAN table for the region and
version that you are using.
The activated configuration ID is specified. The variable
HM0251E The activated configuration ID is &HIRISE.CONFIGID &HIRISE.CONFIGID is the active configuration unit ID. This
message identifies the activated configuration ID.
The method selected failed. Review and assess the impact on
HM0252E This method failed due to an error.Action
your current activity.
No text exists to Browse for this entity. Enter text on the entity
HM0256I No text exists to Browse for this entity
using the TXE method.
No source exists to Browse for this entity. Enter source using
HM0257I No source exists to Browse for this entity
the S method.
No keywords exist to Browse for this entity. No keywords exist
HM0258I No keywords exist to Browse for this entity
to BROWSE for this entity. As stated.
No text exists to Browse for this relation. Enter Text on a
HM0259I No text exists to Browse for this relation
relation using the TXR method.
Keyword Search method failed due to an error Review the
HM0260E Keyword Search method failed due to an error syntax requirements for a Keyword Search and reissue the
method. If the problems persist see your System Administrator
Source/Text/Keywords method ended with errors. Review the
syntax requirements for the method and reissue the method. If
HM0261E Source/Text/Keywords method ended with errors
the problems persist see your System Administrator and
correct the reported method failure.
User modifications to object have been Saved. This
HM0262I User modifications to object have been Saved informational message confirms that the user modifications to
the object have been saved.
System ID of this entity already exists. Enter another System ID of this entity already exists. Review the IDs and
HM0263E
and save. create a unique ID.
The Name of this entity already exists. Enter another The Name of this entity already exists. Review the system
HM0264E
and save. names and create a unique name.
Parent of relation can not be found. Choose another. The parent of the relation is missing. You must choose another
HM0265E
Then press Save. and then save it.
Child of relation cannot be found. Choose another. Child of relation cannot be found. Choose another child relation
HM0266E
Then press Save. and then save it.
DBMS Usage must be DB2. If the entity contains SQL
HM0272E DBMS Usage must be DB2. statements, use the ME method to change the DBMS
ATTRIBUTE TO 'DB2'.
INI Line number in the specified INI file may be invalid. The
parameter %1 is the line number of the invalid INI statement.
HM0273W INI Line number %1 in file %2 may be invalid The parameter %2 is the name of the INI file. Correct the
syntax error or invalid domain. Contact your System
Administrator for assistance.
INI Line number in the specified INI file may be invalid. The INI
HM0274E INI Line number %1 in file %2 is invalid line number may have a syntax error or invalid domain.
Contact your System Administrator for assistance.


INI Line number in the specified INI file may be invalid. The
parameter %1 is the line number of the invalid INI statement.
HM0275I INI Variable %1 was found to be invalid The parameter %2 is the name of the INI file. Correct the
syntax error or invalid domain. Contact your System
Administrator for assistance.
This message is for informational use. The %1 parameter is a
HM0276I Checking for %1
text string. This message is for informational use only.
This message is for informational use. The %1 parameter is a
HM0277I Current Value is %1
text string. This message is for informational use only.
No transaction codes exist within the transaction range of the
activated configuration unit for the specified region. Contact
No transaction codes exist within the transaction range
HM0278E your System Administrator for the valid ranges. Then run the
of the activated configuration unit for region %1.
ME method on the configuration unit entity and modify the MIN
TRANID or MAX TRANID values.
This message is for informational use. The %1 is the value of
HM0279I INI Value %1
the INI variable. This message is for informational use only.
The INI variable will not be validated. The %1 parameter
HM0280W Ini variable will not be validated: %1 contains the name of the INI variable. Contact your System
Administrator if you feel this INI variable should be validated.
The %1 parameter contains the key of the VSAM record. INI
A VSAM file error occurred. The record keyed by %1 Value %1. Review the RES files for entity prepare. If you are
HM0281W
could not be found. unable to resolve the problem, contact your System
Administrator.
A VSAM file error occurred. The record keyed by %1 could not
be read. The %1 parameter contains the key of the VSAM
HM0282W INIDFT VSAM file error, cannot read record %1 record. Review the RES files for entity prepare. If you are
unable to resolve the problem, contact your System
Administrator.
Source/Text/Keywords method ended with errors. Review the
DB2 database error occurred, Check HMLOG for Error
HM0283E syntax requirements for the method and correct the error.
code.
Contact your System Administrator if the problem persists.
The specified Configuration Unit has more than one server.
HM0300E Configuration Unit %1 has more than one server The %1 parameter is the Configuration Unit ID. Delete the
relationship to one of the servers.
The specified Configuration Unit has more than one database.
HM0301E Configuration Unit %1 has more than one database The %1 parameter is the Configuration Unit ID. Delete the
relationship to one of the databases.
The specified Configuration Unit has more than one machine.
HM0302E Configuration Unit %1 has more than one machine The %1 parameter is the Configuration Unit ID. Delete the
relationship to one of the machines.
The specified Configuration Unit is missing a server. The %1
parameter is the Configuration Unit ID. If necessary, Create a
HM0303E Configuration Unit %1 is missing a server.
server entity, and add a relationship from the Configuration unit
to the Server entity.
The object selected for preparation is not encapsulated by the
configuration unit. The %1 parameter is the System ID of the
Preparable object %1 %2 is not encapsulated by the encapsulated entity. The %2 parameter is the Entity type of the
HM0304E
configuration unit %3 encapsulated entity. The %3 parameter is the Configuration
Unit ID. Add a relationship from the Configuration Unit to the
Entity.
The specified Application Configuration was not found. The %1
parameter contains the Application Configuration ID. Create
HM0305E Application Configuration %1 was not found
the Application Configuration entity. If the problem persists,


The specified Application Configuration does not have any
configuration units. The %1 parameter contains the Application
Application Configuration %1 does not have any
HM0306E Configuration ID. Create a Configuration Entity and add a
configuration units
relationship from the Application Configuration Entity to the
Configuration Unit.
Configuration verification completed with errors. Validate that
the Configuration unit has the required relationships to a
HM0307E Configuration verification completed with errors
database, machine, and server entity. Review and correct the
application configuration.
Configuration verification completed successfully. The
HM0308I Configuration verification completed successfully
verification of application configuration completed without error.
The Preparable object is not encapsulated by the configuration
unit within the Application's Configuration Unit. The %1
Preparable object %1 is not encapsulated by the parameter contains the Preparable entities System ID. If the
HM0309E configuration unit within the Application's Configuration object is required by the configuration unit, add a relationship
Unit using the ADDE or ASSIGNCU method from the configuration
unit to the object. Review and correct the preparable unit
encapsulation.
Error attempting to allocate memory. Review the RES and
HMLOG files to determine where the memory allocation failure
HM0310E Error attempting to allocate memory
occurred. If you are unable to resolve the problem contact your
Configuration Unit=%1, server=%2, database=%3, and
machine=%4 The %1 parameter contains the Configuration
Configuration Unit=%1, server=%2, database=%3, and Unit ID. The %2 parameter contains the Server ID. The %3
HM0311I
machine=%4 parameter contains the Database ID. The %4 parameter
contains the Machine ID. This message displays the mandated
components of your Configuration Unit hierarchy.
The specified Configuration Unit is missing a database. The
HM0312E Configuration Unit %1 is missing a database. %1 parameter contains the Database ID. Review and add a
relationship to a database entity.
The specified Configuration Unit is missing a machine. The %1
HM0313E Configuration Unit %1 is missing a machine. parameter contains the Machine ID. Review and add a
relationship to a machine entity.
The specified method must have a collection ID on the
(Configuration Unit Encapsulates Entity) relationship. The
&RQST.METHOD_ID method requires collection ID on
HM0330E &RQST.METHOD_ID variable contains the requested method
the R_CUECXX relation
ID. Review and add the collection ID to the (Configuration Unit
Encapsulates Entity) relationship.
The variable &RQST.INSTBTCH contains the status of the
Batch AVX installation in the Repository. This text message
HM0331I Batch........... : &RQST.INSTBTCH
displays the status of the Batch AVX installation in the
Repository.
The variable &RQST.INSTCICS contains the status of the
CICS AVX installation in the Repository. This text message
HM0332I CICS........... : &RQST.INSTCICS
displays the status of the CICS AVX installation in the
Repository.
The variable &RQST.INSTIMS contains the status of the IMS
HM0333I IMS............ : &RQST.INSTIMS AVX installation in the Repository. This text message displays
the status of the IMS AVX installation in the Repository.
The variable &RQST.INSTENVR contains the status of the
HM0334I Endevor.......... : &RQST.INSTENVR Endevor system in the Repository. This text message displays
the status of the Endevor system in the Repository.
The variable &RQST.DB2SUBID contains the name of the DB2
Subsystem used during the requested entity prepare. This text
HM0335I Application Subsystem Id. : &RQST.DB2SUBID
message displays the name of the DB2 subsystem used during
the entity prepare.


This message displays the status of the Collapse option in the
repository. The variable &PREPARE.COLLAPSE contains the
HM0336I Installed Collapse Value. : &PREPARE.COLLAPSE
status of the Collapse option in the repository. This message is
for informational purposes only.
This message displays the users Collapse selection for the
entity prepare. The variable &RQST.COLLAPSE contains the
HM0337I Users Collapse Option... : &RQST.COLLAPSE
users Collapse selection. This message is for informational
purposes only.
This text message contains the following string: 'Repository
HM0338I Repository Collapse Enablement: Collapse Enablement:' This message is for informational
purposes only.
This text message contains the following string: 'Collapse Rule
HM0340I Collapse Rule Hierarchy........ Hierarchy........' This message is for informational purposes
only.
This text message contains the following string: 'Preparation
HM0341I Preparation Options.......... Options..........' This message is for informational purposes
only.
This text message contains the following string: 'Full prepare
HM0342I Full prepare Process
Process' This message is for informational purposes only.
This text message contains the following string: 'Rule Hierarchy
HM0343I Rule Hierarchy and Source
and Source' This message is for informational purposes only.
This text message contains the following string: 'Evaluate Rule
HM0344I Evaluate Rule Source only
Source only' This message is for informational purposes only.
The COLLAPSR and EXPANDR methods are only available for
The %1 method is only valid for rules with an execution rules with an execution environment of MVSBAT. The %1
HM0345I
environment of MVSBAT parameter contains the Method ID. If applicable change the
execution environment of the entity to MVSBAT.
Source code is missing for the entity. The variable
&RQST.SYSTEMID contains the entities system ID. The
Error in Creating Source code for ENTITY:
variable &RQST.VERSION contains the entities version.
HM0346W &RQST.ENTITY_TYPE SYSTEMID: &R
Review your HMLOG and HMMSG files for assistance in
QST.SYSTEMID VERSION: &RQST.VERSION
troubleshooting this problem. Contact your System
Administrator if the problem persists..
There are no results available for
&RQST.SYSTEMIDHM0401E Rule Bind ended with Errors,
HM0400I There are no results available for &RQST.SYSTEMID use RES action to view messages. Rule Bind ended with
Errors, use the RES action to view messages. Review the
results in the RES file to determine the bind error.
Verify ended with errors, A DB2 Rollback is issued. The verify
HM0402I Verify ended with errors, A DB2 Rollback was issued. process ended with errors; consequently, a DB2 rollback is
issued.
HM0403I Verify ended with no errors The verify process ended without error.
The long name specified for the rule is not found in the
repository. The specified rule long name is either misspelled or
HM0405E Rule &RQST.Y_LNAME not found
missing from the repository. Review and correct the long
name.
Rule &RQST.Y_LNAME being processed
HM0406I Rule &RQST.Y_LNAME being processed. Rule %1 The specified rule is currently being processed.
being processed
The entity specified in the Rule Source does not exist in the
&ERROR.ENTITY_TYPE &ERROR.ENTITY_ID in Rule Repository. %1 %2 in Rule Source not found in repository. The
HM0407E
Source not found in Repository specified error entity in rule source is not in the repository.
Review and correct the error entity name.
&ERROR.ENTITY_TYPE &ERROR.ENTITY_ID for
The specified View has no Field relations. Review and correct
HM0408E &ERROR.ENTITY_TYP2 &ERROR.ENTITY_ID has no
the missing relationships.
field relations


&ERROR.ENTITY_TYPE&ERROR.ENTITY_ID has The specified entity has multiple INPUT/OUTPUT views.
HM0409E
multiple INPUT/ OUTPUT views Review and correct the duplicate views.
Relationship for The relationship for the specified entity is removed. Use the
HM0410W &ERROR.ENTITY_TYPE&ERROR.ENTITY_ID was ADDR method if the relationship between the two entities is
removed required.
Relationship for The relationship for the specified entity is added. A successful
HM0411W &ERROR.ENTITY_TYPE&ERROR.ENTITY_ID was relationship has been established between the specified
added entities.
Rule has multiple window converses. The rule specified has a
HM0412W Rule has multiple window converses relationship to multiple windows. Remove a relationship to one
of the windows.
The number of rules exceed the maximum allowed for the
The number of rules exceed the maximum allowed for verification method. The evaluation has stopped. Because the
HM0413E
the verification method. The evaluation has stopped. maximum is exceeded, further evaluation is discontinued.
Review and correct the verification request.
&ERROR.ENTITY_TYPE&ERROR.ENTITY_ID does The selected entity does not exist. If the entity is required, use
HM0414W
not exist the ADDE method to add the entity to the repository.
Messages were issued by the LEXICAL Analysis Program, Use
Messages were issued by the LEXICAL Analysis RES to view the results. This message alerts you that the
HM0498I
Program, Use RES to view the results Lexical Analysis Program has issued messages, which you can
view with RES.
Additional information to a previous or upcoming message.
Additional information from the program such as data records
HM0499I &ERROR.MESSAGE
or fields used as supplemental information to a previous or
upcoming message.
Missing input file PDS member. This message alerts you that
HM0500E Missing input file PDS member an expected input file PDS member is missing. Review and
correct the missing file.
Missing output file PDS member. This message alerts you that
HM0501E Missing output file PDS member an expected output file PDS member is missing. Review and
correct the missing file.
Unterminated statement. The statement is diagnosed as not
terminated by a '>' symbol. Review the associated
informational messages to determine the line number and
HM0502E Unterminated statement
skeleton in question. A file tailoring statement may span many
lines, but is terminated by a single '>' symbol. The symbol
must be the last character in the skeleton.
Illegal starting char in the specified variable. The specified
starting character in the identified variable is illegal. File
HM0503E Illegal starting char %1 in variable %2
tailoring variables cannot start with numerics. Review and
correct the illegal character.
The variable name specified is greater than thirty two
The variable name starting with %1 is greater than %2 characters long. The specified variable name is invalid
HM0504E
characters long because it is greater than thirty two characters. Review and
correct the length of the specified variable name.
Invalid size specified for variable definition. Internal error.
HM0505E Invalid size of %1 specified for variable %2 definition
Unterminated single quote. Analysis revealed a mismatch of
HM0506E Unterminated single quote single quotes. Review and correct the single quote so that they
match up.
Unterminated double quote. Analysis revealed a mismatch of
HM0507E Unterminated double quote double quotes. Review and correct the double quote so that
they match up.


Appending to a PDS member is not allowed. Review the
skeleton logic and correct the problem. All OUTFs specified
during a file tailoring are 'remembered'. If multiple OUTFs are
HM0508E Cannot append to an existing PDS member targeted to the same file name, then that file will be appended
to. Since PDS members cannot be appended to, the error
message is displayed. Sequential files can be appended to
during processing.
The DOT statement did not have the required matching /DOT
DOT statement does not have a matching /DOT in file in the specified file. Review the skeleton name specified and
HM0509E
%1 the line number specified. Correct the problem and retry the
operation.
The IF statement did not have the required matching /IF in the
HM0510E IF statement does not have a matching /IF in file %1 specified file. Review the skeleton name specified and the line
number specified. Correct the problem and retry the operation.
The value for the specified variable is missing. Review and
HM0511E A value for variable %1 could not be found
provide a value for the specified variable.
This information message specifies a skeleton file name and
HM0512I File: %1 Line: %2 line number. It is displayed during error messages to assist in
diagnosing skeleton syntax errors.
This informational message is displayed during error handling.
HM0513I Statement: %1 This informational message is displayed during error handling
to assist in skeleton syntax error messages.
An ELSE statement exists without the required IF. An error in
the skeleton logic is found. Review the IF, ELSE and /IF
HM0514E ELSE without IF
statements within the specified skeleton. Correct the problem
and retry the operation.
/IF without IF in the specified file. The /IF statement appears
HM0515E /IF without IF in file %1 without an IF in the specified file. Review and correct the IF
usage.
The /WHILE statement appears without an WHILE in the
HM0516E /WHILE without WHILE in file %1
specified file. Review and correct the WHILE usage.
Invalid integer value. The specified integer value is invalid.
HM0517E Invalid integer value %1
Review and correct the integer value.
The MSG statement is incomplete. It does not contain any.
HM0518E MSG statement does not have any message
Review and correct the message statement.
IM statement is missing the input file name. The IM statement
HM0519E IM statement is missing the input file name is incomplete. It did not contain an input file name. Review and
correct the statement.
The SET statement is incomplete. It did not contain the target
HM0520E SET statement is missing the target variable name
variable name. Review and correct the SET statement.
An illegal expression is detected. Review the expression in
HM0521E Illegal expression
context, and make the necessary correction.
An illegal arithmetic expression is detected. Review the
HM0522E Illegal arithmetic expression
expression in context, and make the necessary correction.
An illegal boolean expression is detected. Review the
HM0523E Illegal boolean expression
expression in context, and make the necessary correction.
The type and value for the specified variable were different.
HM0524E Variable %1 type and value are different
Review and correct the conflict.
Mismatched parenthesis. The set of parentheses is
HM0525E Mismatched parenthesis
mismatched. Review and correct the mismatch.
HM0526E Illegal character %1 in expression Illegal character in expression.
The SQL statement did not have a database name. Review
HM0527E SQL statement is missing database name
and correct the SQL statement.
The SQL statement did not have an SQL query. Review and
HM0528E SQL statement is missing SQL query
correct the SQL statement.


The DOT did not have an array name or a database name.
HM0529E DOT missing array or database name
Review and correct the DOT statement.
DOT array name %1 is longer than %2 characters. The
specified DOT array name had more than the designated
HM0530E DOT array name %1 is longer than %2 characters
number of characters. Review and correct the array name
length.
The specified DOT database name had more than the
HM0531E DOT database name %1 is longer than %2 characters designated number of characters. Review and correct the
database name length.
Using a Break statement outside of a loop is illegal. Review
HM0532E BREAK illegal outside of a loop
and correct the Break statement.
/DOT encountered without a starting DOT. A /DOT without a
HM0533E /DOT encountered without a starting DOT starting DOT statement is detected. Review and correct the
DOT statement.
The OUTF statement did not have an output file name. Review
HM0534E OUTF missing output file name
and correct the OUTF statement.
The fill character is detected to be illegal. Review and correct
HM0535E Illegal fill character
the fill character.
The strip character is detected to be illegal. Review and
HM0536E Illegal strip character
correct the strip character.
The number of formatting arguments is found to be illegal.
HM0537E Illegal number of formatting arguments
Review and correct the number of formatting arguments.
The equality operator is detected to be illegal. Review and
HM0538E Illegal equality operator
correct the equality operator.
Illegal numeric to non numeric comparison. The
HM0539E Illegal numeric to non numeric comparison numeric-to-nonnumeric comparison is illegal. Review and
correct the comparison.
Illegal conditional operator. The conditional operator is
HM0540E Illegal conditional operator detected to be illegal. Review and correct the conditional
operator.
The boolean operator is detected to be illegal. Review and
HM0541E Illegal boolean operator
correct the boolean operator.
The DOT statement is found to be recursive. Review and
HM0542E RECURSIVE DOT STATEMENT
correct the DOT statement.
The specified array is undefined. Review and correct the array
HM0543E Array %1 has not been defined
definition.
Format starting position of %1 is greater than variable Format starting position of %1 is greater than variable length of
HM0544E
length of %2. %2. Internal error. Contact your System Administrator.
An error occurred when attempting to divide by zero. Review
HM0545E Divide by zero
and correct the division.
The specified operator is invalid. Review and correct the
HM0546E Invalid operator %1
operator.
The equality expression is illegal. Review and correct the
HM0547E Illegal equality expression
equality expression.
HM0548I Using default value for variable %1 Using default value for assigned value.
An attempt to change databases is invalid. Review and correct
HM0549E Cannot change databases
the request to change databases.
DOT statements cannot be nested more than eight An attempt to nest DOT statements deeper than eight levels is
HM0550E
levels deep. invalid. Review and correct the nesting of DOT statements.
SQL statement cannot return more than one row of data. An
HM0551E SQL statement cannot return more than one row of data attempt to nest DOT statements deeper than eight levels is
invalid. Review and correct the nesting of DOT statements.


SQL statement cannot exceed more than 1024 bytes Shorten
HM0552E SQL statement cannot exceed more than 1024 bytes
the SQL statement.
The value to be set to a rexx variable must be character.
HM0553E The value to be set to a rexx variable must be character
Convert the expression being assigned to the variable.
The rexx variable could not be created. Internal error. Contact
HM0554E The rexx variable could not be created
The left-hand expression in the INI statement is missing.
HM0555E INIT missing a lvalue
Correct the statement and retry the operation.
Target of assignment is a defined variable whose size is too
Target of assignment is a defined variable whose size is small for the source value. Target of assignment is a defined
HM0556E
too small for the source value. variable whose size is too small for the source value. Internal
error. Contact your System Administrator.
The dataset &DSNCHK.DSNN has an invalid
HM0557E &DSNCHK.ATTRB of ( &DSNCHK.ACTUAL ) ; the valid The data-set contains an invalid value.
value is ( &DSNCHK.VLD ).
HM0558E The dataset &DSNCHK.DSNN does not exist. The specified data set does not exist.
Error reading ddname ( %1 ). RC: %2. Error reading the
HM0559E Error reading ddname ( DDNLIST ). RC: retcc
specified ddname. Review and correct the method invoked.
Attempting to Explode failed, with the specified return code.
HM0570E Error occurred during Explode, RC=%1
Review and correct the Explode request.
This method is only available through Rebuild. This method is
HM0575E This method is only available through Rebuild. available only through the rebuild process. Review and correct
the method invoked.
Configuration processing has been Deactivated. Review and
HM0576I Configuration processing has been Deactivated.
correct the method invoked.
Error occurred while editing Partitioned Data Set Error occurred while editing Partitioned Data Set member.
HM0600E
member. Review and correct the erroneous edit.
The control cards cannot be copied to a PDS member while the
PDS member in use, unable to copy control cards to
HM0601E member is in use. Review the availability of the PDS member,
PDS member.
and correct the timing and content of the attempted copy.
HM0617E Invalid set length for data type Correct the data type or set length and retry the operation.
Set length must be 15 for small integer and 31 for integer.
HM0619E Set length must be 15 for small integer and 31 for integer
Correct the data type or set length and retry the operation.
No versions were set up for this repository. Contact your
HM0700E No rows found in VERSION DB2 table.
System Administrator and review the installation.
An error occurred while trying to retrieve data from the DB2
VERSION table. Review additional messages in the data set
HM0701E Unable to retrieve data from DB2 VERSION table.
defined for DD HMFLOG to determine the cause of the error
and contact your System Administrator.
An error occurred while trying to save Text for the specified
object type and object name. Review additional messages in
HM0702E Insert of Text for %1 %2 failed.
the data set defined for DD HMFLOG to determine the cause of
the error and contact your System Administrator.
CONVERSION RESULTS FOR ENTITY TEXT FROM
HM0703I Report title for conversion of Text in the listed version.
VERSION: %1
%1 Entities had text rows in the T_ENT table for version The number of Entities listed had text rows in the T_ENT table
HM0705I
%2. for the listed version.
Inserted text into the E_TEXT table for %1 entities in Text is inserted in the E_TEXT table for the number of entities
HM0706I
version %2. listed in the version listed.
Text conversion failed for the listed number of entities during
HM0707I %1 Entities had the text conversion FAIL during this run. this run. Review additional messages in the data set defined for
DD HMFLOG to determine the cause of the error.
CONVERSION RESULTS FOR RELATION TEXT
HM0708I Report title for conversion of Text in the listed version.
FROM VERSION: %1


%1 Relations had text rows in the T_REL table for The number of Relations listed had text rows in the T_REL
HM0710I
version %2. table for the listed version.
Inserted text in the R_TEXT table for %1 relations in Text is inserted in the R_TEXT table for the number of relations
HM0711I
version %2. listed, in the version listed.
Text conversion failed for the listed number of Relations during
%1 Relations had the text conversion FAIL during this
HM0712I this run. Review additional messages in the data set defined for
run.
DD HMFLOG to determine the cause of the error.
HM0713I SOURCE CONVERSION RESULTS Report title for conversion of Source.
HM0715I PDS contains %1 members. Partitioned data set contains the listed number of members.
HM0716I Converted source for %1 members. Converted source for the number of members listed.
HM0717I Skipped source for %1 members. Did not convert source for the number of members listed.
CONVERSION RESULTS FOR ENTITY KEYWORDS
HM0718I Report title for conversion of Keywords in the listed version.
FROM VERSION: %1
Processed %1 rows from old Keyword table in version: Processed the number of rows listed from a prior version of the
HM0720I
%2 System Keyword table in the listed version.
Inserted %1 rows into the new Keyword table for Inserted the number of rows listed into the current System
HM0721I
version: %2 Keyword table for the listed version.
The number of rows listed were not converted into the new
HM0722I %1 rows were NOT converted into the new table.
table format.
Summary of Entity CRC Verification for Version: %1 and
HM0723I Entity CRC report title for the listed version and System model.
Model: %2
%1 Total entries exist in the CRC_ENTITY table for The number listed is the total number of entities with CRC
HM0725I
Version: %2 values in the CRC_ENTITY table for the listed version.
The listed number of CRC entries do not have any
corresponding objects in the various DB2 tables. Review
%1 Entries were missing corresponding objects in the
HM0726I additional messages in the data set defined for DD HMFLOG to
DB2 table
determine if these entries should be removed from the CRC
table(s) or the objects recreated in the appropriate DB2 tables.
The number of entries listed had DB2 errors during processing.
HM0727I %1 Entries had errors occur during processing Review messages in the data set defined for the DD HMFLOG
and SYSPRINT.
The listed object exists in the CRC_ENTITY table but not in the
corresponding DB2 object table (e.g. E_RULE). Determine if
HM0728E (MISSING) Entity Type:%1 MetaId:%2 SystemId:%3
the object must be removed from the CRC table or recreated in
the appropriate DB2 table.
The entity type listed is not defined within the System.
Determine if the object must be removed from the CRC table or
HM0729E (UNKNOWN) Entity Type:%1 SystemId:%2 MetaId:%3
recreated in an existing DB2 table. You should only recreate
the object if you know what the correct type is.
A DB2 error occurred while processing this object. Review
HM0730E (DB2 ERROR) Entity Type:%1 SystemId:%2 MetaId:%3 additional messages in the data set defined for the DD
HMFLOG and SYSPRINT.
An error occurred while processing this object. The return
HM0731E (BAD RC) Entity Type:%1 SystemId:%2 MetaId:%3 code from the processing is not accounted for. Review
messages in the data set defined for DD HMFLOG.
HM0732I Verifying Entity CRC's for Version: %1 and Model: %2 Report title for the specified version and model.
An object exists for each Entity CRC in the CRC_ENTITY
HM0734I There are no missing Entity CRCs to report
table.
The Meta ID listed in not defined within the System. Contact
HM0735E (UNKNOWN) Entity Type:%1 MetaId:%2 SystemId:%3
HM0736I Verifying Relation CRC's for Version: %1 and Model: %2 Report title for specified version and the System Model.


A CRC value exists for the listed Relation but there is no
corresponding relation entry in the DB2 relation table (e.g.
(MISSING) Y Ent:%1 X Ent:%2 YId:%3 XId:%4 RelId:%5
HM0738E R_RULRUL). Determine if the relation should be removed from
MetaId:%6 SepId:%7
the CRC_RELATION table or if the relation must be recreated
in the corresponding relation table.
(UNKNOWN) Y Ent:%1 X Ent:%2 YId:%3 XId:%4 The listed Relation is not defined within the System. Determine
HM0739E
RelId:%5 MetaId:%6 SepId:%7 if the Relation in the CRC_RELATION table must be deleted.
The Meta Id listed in not defined within the System. Contact
HM0740E (UNKNOWN) MetaId:%1 RelId:%2
A DB2 error occurred while processing the listed relation.
(DB2 ERROR) Y Ent:%1 X Ent:%2 YId:%3 XId:%4
HM0741E Review additional messages in the data set defined for the DD
RelId:%5 MetaId:%6 SepId:%7
An error occurred while processing this relation. The return
(BAD RC) Y Ent:%1 X Ent:%2 YId:%3 XId:%4 RelId:%5
HM0742I code from the processing is not accounted for. Review
MetaId:%6 SepId:%7
messages in the data set defined for the DD HMFLOG.
For every relation CRC value there is a corresponding relation
HM0743I There are no missing Relation CRCs to report.
in the relation table.
Summary of Relation CRC Verification for Version: %1
HM0744I Report title for specified version and the System model.
and Model: %2
%1 Total entries exist in the CRC_RELATION table for The number of entries listed exist in the CRC_RELATION table
HM0746I
Version %2. for the specified version.
HM0748I **** Starting CRC Report Program %1 Starting the listed report program.
HM0749I **** Ending CRC Report Program %1 Ending the listed report program.
There are no CRCs for this model in the specified version. If
HM0750E No CRC objects for this Model found in Version: %1 objects exist in this model, run the CRC Synchronization
method to generate CRCs for this model.
Cumulative Summary for all Versions and Models
HM0751I Report title.
processed
HM0753I %1 Total entries exist in the CRC_ENTITY table. The number of entries listed, exist in the CRC_ENTITY table.
The number of entries listed did not have corresponding
%1 Entries were missing corresponding objects in the
HM0754I objects in the DB2 table. Determine if the CRC values should
DB2 table.
be removed or the objects recreated.
The listed number of entries had DB2 errors during processing.
HM0755I %1 Entries had errors occur during processing. Review additional messages in the data set defined for DD
HM0756I %1 Total entries exist in the CRC_RELATION table. The listed number of entries exist in the CRC_ENTITY table.
HM0757I **** Starting CRC Syncronization Program %1 Starting the listed program.
HM0758I **** Ending CRC Syncronization Program %1 Ending the listed program.
The number of entries listed exist in the CRC_RELATION
HM0759I %1 Total entries exist in the CRC_RELATION table.
table.
**** Starting CRC Report Program with Delete Option
HM0760I Starting specified report program.
%1
**** Ending CRC Report Program with Delete Option
HM0761I Ending specified program.
%1
The specified entity exists in the CRC_ENTITY table but it does
(DELETEDMISSING) Entity Type:%1 MetaId:%2
HM0762E not exist in the corresponding DB2 table (e.g E_RULE). This
SystemId:%3
object has been deleted.
Id:%7. The specified Relation exists in the CRC_RELATION
(DELETEDMISSING) Y Ent:%1 X Ent:%2 YId:%3
HM0763E table but it does not exist in the corresponding relation table
XId:%4 RelId:%5 MetaId:%6 Sep
(e.g. R_RULRUL). It has been deleted.
(DELETEDUNKNOWN) Entity Type:%1 MetaId:%2 The Meta Id specified is invalid and has been deleted from the
HM0764E
SystemId:%3 CRC_ENTITY table.


The Meta Id specified is invalid and has been deleted from the
HM0765E (DELETEDUNKNOWN) MetaId:%1 RelId:%2
CRC_RELATION table.
Add a ENQ name to the statement and retry the operation. If
HM0800E ENQ statement missing ENQ name
the system persists, contact your System Administrator.
ENQ statement name must be no more than 24 characters
ENQ statement name must be no more than 24
HM0801E long. Shorten the name and retry the operation. If the system
characters long
persists, contact your System Administrator.
No output file available for output. A CLOSE statement has
been executed and data is pending for output. Since the
CLOSE is not followed by a OUTF statement this output data
HM0802E No output file available for output
cannot be written and will be lost. The CLOSE file should be
followed immediately by a OUTF statement or remove the
source of the output from the ft skeleton.
An error is found in the corresponding table for the object type
being processed before this error message. Check the object
** Error found in the corresponding table for this object type's corresponding DB2 table and fix the error. Check the
HM0803E
type Meta_id column in the corresponding DB2 table being
processed. If the problem persists, contact your System
Administrator.
No Text data copied. You do not have authorization to
HM0851W
create it.
No Keywords data copied. You do not have authorization
HM0852W
to create it.
No Source data copied. You do not have authorization to
HM0853W
create it.
HM0900L Entity Attributes
HM0901L Audit Attributes
HM0902L Entity Source Code
HM0903L View Source
HM0904L Text
HM0905L Keywords
HM0906L Softcopy
HM0907L Hardcopy
HM0908L Current Object
HM0909L Object Hierarchy
HM0910L Object Parts to Process . . . . . . . . .
Type 's' to select an option or type a space to deselect.
HM0911L
Then press ENTER.
HM0913L HPS Reporting Facility
HM0914L Database . . . . . . . . . . . . . . . .
HM0915L Tablespace . . . . . . . . . . . . . . .
HM0916L Create Foreign Key Index . . . . . . . .
HM0917L Storage Media . . . . . . . . . . . . .
HM0918L Storage Name . . . . . . . . . . . . . .
HM0919L Primary Quantity . . . . . . . . . . . .
HM0920L Secondary Quantity . . . . . . . . . . .
HM0921L Data Set Name . . . . . . . .
HM0922L Replace above member . . . . . . . . . .
HM0923L VCAT

Enterprise Development Messages (Part 2) HM0924L

HM0924L Storage Group
HM0925L DB2 Information:
HM0926L Storage Information:
HM0927L Output Partitioned Dataset Name:
HM0928L Yes
HM0929L No
HM0930L Generate DB2 DDL
Generic message used to display C runtime errors, etc.
HM1000I %1
Information is self-contained in the message.
Message displays generic warning. Information is self-
HM1001W %1
contained in the message.
STK object type is not defined within the System. Correct
HM1002E %1
object type before proceeding further.
An error occurred while retrieving the hierarchy of the listed
Explode Error occurred for seed: Entity Type: %1
HM1003E object. The return code is listed. Review messages in the data
System ID: %2. Explode rc: %3.
set defined for DD HMFLOG and SYSPRINT.
A DB2 error occurred while trying to retrieve the seed objects of
HM1004E Error trying to get seeds for migration: %1 the migration. Review messages in the data set defined for DD
HMFLOG to determine the cause of the error.
The aggregation for the specified type, type CD, and
Invalid aggregation for Type:%1 Typecd:%2
HM1005E aggregation number is invalid. Review and correct the
Aggnum:%3Action
aggregation request.
There is no Source or Text for the listed object. Determine if
HM1006W No SOURCE or TEXT data found for %1 %2
Source or Text is required before proceeding further.
An EOF occurred before completing the read of an anticipated
HM1007W EOF occurred on fread for file %1Action
file. Review and correct the file read procedure.
Generate Migration Package for %1; V:%2; started at
HM1008I Report title for the listed migration, version and time.
%3
There is no Text for the listed relation. Determine if there
HM1009W No TEXT data found for Relation %1
should be text for this object before proceeding further.
The record length specified in the STK control block exceeds
Incoming record length to insert exceeds the maximum 3200 characters. The maximum length acceptable is 3200
HM1010E
of 3200 characters characters. Review and correct the data so that the length is in
the acceptable range.
For records which are not null-terminated, the maximum record
If record is not \n terminated then maximum record size
HM1011E size cannot exceed 3199 characters. Review and correct the
of data allowed is 3199
data in the record before proceeding.
A DB2 error occurred while deleting existing data, so that new
HM1012E Error on Delete attempt before update. data could not be inserted. Review messages in the data set
defined for DD HMFLOG to determine the cause of the error.
The maximum size of the Keyword data cannot exceed 240
HM1013E Keyword Data cannot be longer than 240 characters. characters. Review and correct the keyword data before
proceeding further.
The specified STK file length is used to read the file. But, upon
EOF occurred before number of bytes passed in file
HM1014E attempting to read it, the file is empty. Review and correct the
length was actually read.
file length.
A DB2 error occurred when attempting to open the listed
HM1015E ERROR when opening cursor %1. cursor. Review messages in the data set defined for DD
HMFMSG and HMFLOG to determine the cause of the error.
A DB2 error occurred when attempting to retrieve data using
the listed cursor. Review messages in the data set defined for
HM1016E ERROR when fetching for cursor %1.
DD HMFLOG and HMFMSG to determine the cause of the
error.


CRC GENERATION RESULTS FOR OBJECT: %1
HM1020I Report title for listed object and version.
VERSION: %2
HM1022I %1 members exist for this object type. The number of members listed exist for this object type.
HM1023I Generated CRC's for %1 member(s). CRC values were generated for the listed number of members.
HM1024I No DB2 rows found for object type: %1 and version: %2 There are no DB2 rows for the listed object type and version.
A DB2 error occurred while attempting to retrieve data for the
listed object and version. Review messages in data set defined
HM1025E Error Fetching DB2 data for: %1 Version: %2
for DD HMFLOG and HMFMSG to determine the cause of the
error.
The INI variable in @USRENVn indicates that the The INI variable in @USRENVn indicates that the System
HM1026E
System Security product is set to N (No). Security product is set to N (No).
The INI variable indicates whether the System Security product
HM1026I PRODUCT.SECM is set to %1
is installed or not.
The INI variable in @USRENVn indicates that the The INI variable in @USRENVn indicates that the System
HM1027E
System Archetyp product is set to N (No). Archetyp product is set to N (No).
The INI variable indicates whether the System Archetype
HM1027I PRODUCT.ARCH is set to %1
product is installed or not.
The minimum and maximum values defined for the retrieval of
HM1028E Invalid MIN/MAX value for MNEBCRD/MXEBCRD dynamically fetched DB2 Entity CRUD modules are incorrect.
HM1029E Invalid MIN/MAX value for MNEBISP/MXEBISP dynamically fetched ISPF Entity CRUD modules are incorrect.
HM1030E Invalid MIN/MAX value for MNRBISP/MXRBISP dynamically fetched ISPF Relation CRUD modules are
incorrect. Contact your System Administrator.
HM1031E Invalid MIN/MAX value for MNRBCRD/MXRBCRD dynamically fetched Relation CRUD modules are incorrect.
The listed object type is not defined within the System
HM1032E Object Type %1 is invalid.
repository. Enter a valid object type.
HM1040I Options selected for CRC Synchronization: Report title.
HM1041I Synchronize CRC for Object... : &OBJTYPE CRC synchronization requested for listed object type.
HM1042I Synchronize CRC for...... : All Entities CRC synchronization requested for all entity types.
HM1043I Synchronize CRC for...... : All Relationships CRC synchronization requested for all relationships.
CRC synchronization requested for all entities and
HM1044I Synchronize CRC for...... : All Entities and Relationships
relationships.
CRC synchronization requested for objects in the listed
HM1045I Objects in Version....... : &ENTVER
version.
CRC synchronization requested for objects in all versions of
HM1046I Objects in........... : All Versions
the System repository.
DB2 updates will be saved after the listed number of objects
HM1047I CRC Commit Count........ : &COMITCNT
have been processed.
HM1048I Repository options: Report title.
The listed variable indicates whether the System Security
HM1049I PRODUCT.SECM.......... : &PRODUCT.SECM
The listed variable indicates whether the System Archetype
HM1050I PRODUCT.ARCH.......... : &PRODUCT.ARCH
HM1051I Options selected for CRC Reporting: Report title.
HM1052I Report on CRC's for...... : All Entities CRC report is for all entities.
HM1053I Report on CRC's for...... : All Relationships CRC report is for all relationships.


HM1054I Report on CRC's for...... : All Entities and Relationships CRC report is for all entities and relationships.
HM1055I Objects in Version....... : &OBJVER Report is for the objects in the listed version.
There are no fields defined for VIEW: %1. An error occurred
There are no fields defined for VIEW:
HM1104W when the specified view is found having no defined fields.
&RQST.VIEW_LNAME
Review and correct the missing fields.
Rule: %1 is invalid for a DB2 Bind. No Rules in the Rules
hierarchy are marked as DB2. The hierarchy is searched but
&RQST.FIELD_LNAME The calculated length for
HM1109W no additional DB2 rules were found. Either change the
Description of a VARC HAR field exceeds 26 bytes.
hierarchy to include DB2 or remove the DB2 code from the
prepared entity.
A system error occurred trying to retrieve a REXX variable.
HM2001E Unable to retrieve variable %1 from the REXX pool. Contact your System Administrator with the contents of this
message.
HM2002I %1 default value set to %2. The specified default value has been set. No action needed.
A DB2 error has occurred. The attempt to declare a cursor for
HM2003E Unable to declare cursor for table %1. the specified table is unsuccessful. Retry the operation. If the
error persists, contact your System Administrator.
The open cursor DB2 operation failed. The attempt to open a
cursor for the specified table is unsuccessful. Retry the
HM2004E Unable to open cursor for table %1.
operation. If the error persists, contact your System
Administrator.
A system error occurred while processing lock information. The
Unable to retrieve lock information for %1 %2 in version attempt to retrieve lock information for the specified item and
HM2005E
%3. version is unsuccessful. Retry the operation. If the error
A system error occurred while processing a lock request. Retry
HM2006E Unable to retrieve current request number. the operation. If the error persists, contact your System
Administrator with the contents of this message.
A system level error occurred in processing a lock request.
HM2007E Unable to save lock request in table %1. Retry the operation. If the error persists, contact your System
Administrator.
A escalate lock request failed for the specified object. The
attempt to escalate a waiting lock request for the specified item
Unable to escalate waiting lock request for %1 %2 in
HM2008E and version failed. This may be due to high system usage.
version %3.
Retry the operation. If the error persists, contact your System
Administrator.
The deletion of a waiting lock request failed for the specified
Unable to delete waiting lock request for %1 %2 in
HM2009E object. Retry the operation. If the error persists, contact your
version %3.
A system level error occurred in processing a lock request.
HM2010E Unsupported table function %1 for table %2.
A locking conflict has occurred during processing. The request
HM2011E Request for %1 conflicts with current mode. for the specified item and the current mode are in conflict.
Review and eliminate the request and mode conflict.
The user's request cannot be performed due to his
authorization level. Ask the System Administrator to check your
HM2012E User's authorization level is invalid for this request user authorization level for this project and this version. Also
review the action requested to make sure that the proper object
is specified.
A system level error has occurred. Retry the operation. If the
HM2013E Unable to put data record for %1 %2 into REXX pool.
A system level error occurred in processing a lock request. Ask
Unable to retrieve user authorization level for %1.
HM2014E your System Administrator to review your authorization level for
Security return code %2.
this project and version.
%1 %2 is in %3 mode. This informational message indicates
HM2015E %1 %2 is in %3 mode.Action
the specified item is in the indicated mode.


User not authorized to place %1 %2 in %3 mode. The attempt
to place the specified item in the indicated mode failed because
the user does not have sufficient authority. Review your
HM2016E User not authorized to place %1 %2 in %3 mode.
authorization level and the action requested. Contact your
System Administrator if an authorization level change is
needed.
A system level error occurred during a lock request. Retry the
HM2017E A system error occurred during environment initialization operation. If the error persists, contact your System
Administrator.
A system level error occurred while processing a lock request.
System error occurred while retrieving user authorization
HM2018E Retry the operation. If the error persists, contact your System
level
Administrator.:
%1 %2 placed in %3 mode. This informational message
HM2019I %1 %2 placed in %3 mode.Action reports the specified item is placed successfully in the indicated
mode.
A system level occurred while processing a lock request. Retry
HM2020E System error occurred while retrieving lock information the operation. If the error persists, contact your System
Administrator.
HM2021E A system level occurred while adding a request the operation. If the error persists, contact your System
Administrator.
HM2022E A system error occurred while updating the request the operation. If the error persists, contact your System
Administrator.
HM2023E A system level error occurred while releasing a lock the operation. If the error persists, contact your System
Administrator.
The request violates the authorization that your id has within
the System repository. Your authorization level is insufficient for
HM2024E You are not authorized to perform this request.
this action. Contact your System Administrator to request
changes in authorization levels.
The object cannot be placed in the requested state because it
HM2025E This object is already in the requested lock state
is already in that state. No action needed.
The lock status of the object cannot be changed to what you
The lock request conflicts with the current lock status of are requesting since your request conflicts with the current lock
HM2026E
the object. status of the object. Review your request or the previous state
of this object.
The object has been updated by someone else since you
This object has been updated since you obtained access
HM2027E obtained access to the object. Review and correct your
to the object.
request.
A system level error occurred while reading a INI file. Retry the
HM2028E Error occurred reading the INI file. operation. If the error persists, contact your System
Administrator.
The PREPARE.COLLAPSE INI variable in the @USRENV INI
The %1 method is only supported when the COLLAPSE
HM2029E file must be set TO 'Y'. Review this repositories INI Collapse
INI variable is turned on.
settings with your Repository System Administrator.
The object has been previously locked by another user.
The object is already locked by User ID
HM2030E Another user holds a lock on the object you are trying to lock.
&HMCLKCK.YLOCKID
Retry your action later or have that user free the existing lock.
HM2031I &RQST.ENTITY_TYPE &RQST.LNAME is not locked.
&RQST.ENTITY_TYPE &RQST.LNAME is placed in
HM2032I
&HCLKCK.YELKDESC mode by &HCLKCK.YLOCKID


Program to retrieve object hierarchy for configuration unit
assignment ended with return code %1. Program to retrieve
object hierarchy for configuration unit assignment ended with
Program to retrieve object hierarchy for configuration
HM2100I return code %1. An error occurred attempting to retrieve the
unit assignment ended with return code %1.
object hierarchy for the configuration unit assignment. The
return code is shown. Review and correct the retrieve object
hierarchy request.
Unable to retrieve object hierarchy, reason code %1. Retry the
HM2101E Unable to retrieve object hierarchy, reason code %1. operation. If the error persists, contact your System
Administrator.
Unable to retrieve data attributes for Configuration Unit %1.
Unable to retrieve data attributes for Configuration Unit The attempt to retrieve data attributes for the specified
HM2102E
&RQST.CONFIGID. configuration unit failed. Retry the operation. If the error
ACTIVATE a configuration unit before issuing this action. Issue
the ACTIVATE method on a specific configuration unit prior to
HM2103E ACTIVATE a configuration unit before issuing this action. issuing this method. This method requires that a configuration
unit be active for correct processing. Contact your development
leader for the proper configuration unit to activate.
The request to obtain an object hierarchy list failed because the
object specified does not have any child objects. Review the
HM2104E Object hierarchy list is empty.
object specified, and review the hierarchy of objects attached
to this object.
The request to obtain an object hierarchy list for relationships
HM2105E Object hierarchy list for relationships is empty. failed because the list is empty. Review the object specified
and the hierarchy attached to this object.
The attempt for a configuration unit assignment failed because
HM2106E No objects selected for configuration unit assignment. no objects were selected. Review and correct the configuration
unit assignment request.
Unable to assign configuration unit %1 to %2 %3 in version
Unable to assign configuration unit %1 to %2 %3 in %4, reason code %5. The attempt to assign the specified
HM2107E
version %4, reason code %5. configuration unit and version failed. Retry the operation. If the
The program to assign a configuration unit failed with the
Program to assign configuration unit ended with return
HM2108E indicated return code. Retry the operation. If the error persists,
code %1.
Unable to retrieve data attributes for %1 %2. Retry the
Unable to retrieve data attributes for &COSDESC operation. If the error persists, contact your System
HM2200E
&COSLNAME. Administrator. Note any other error messages that appear with
this message.
The specified new owner does not have any authorization in
the specified project. Review and reconcile the request
HM2201E New Owner %1 is not assigned to project %2.
involving the owner and project. Contact your System
Administrator if an authorization change is required.
The attempt to retrieve data attributes for the specified item
Unable to retrieve data attributes for %1 %2 in version
HM2202E and version failed. Retry the operation. If the error persists,
%3, Reason Code %4.
Unable to change ownership of %1 %2 in version %3, reason
code %4. The attempt to change ownership of the specified
Unable to change ownership of %1 %2 in version %3,
HM2203E item and version failed. Retry the operation. If the error
reason code %4.
persists, contact your System Administrator. Note any other
messages that appear with this message.
Action not available for object %1. The attempted action for the
HM2204E Action not available for object &COSDESC. specified object is not available. Review and correct the action
request.
The attempt to fetch the cursor for the specified table failed.
HM2205E Unable to fetch cursor for table %1. Retry the operation. If the error persists, contact your System
Administrator.


Unable to define %1 %2 for static linkage in version %3, reason
code %4. Message appears when the user tries to define a
relationship between an object and a static configuration unit.
Review all the error messages presented and take the
Unable to define %1 %2 for %3 in version %4, reason
HM2301E appropriate course of action. If the error is a 1196, this
code %5.
indicates that the configuration unit named
STATIC_LINK_DEFAULT is not present. Verify that the System
default repository has been imported into this version of the
repository
Program to establish static linkage ended with return code %1.
Program to establish static linkage ended with return
HM2302E This is the results of establishing static linkage. If the return
code %1.
code is not zero, review the other messages.
Unable to define %1 %2 for dynamic linkage in version %3,
reason code %4. Message appears when the user tries to
Unable to define %1 %2 for dynamic linkage in version
HM2303E define a relationship between an object and a dynamic
%3, reason code %4.
configuration unit. Retry the operation. If the problem persists,
Program to establish dynamic linkage ended with return code
Program to establish dynamic linkage ended with return %1. Program to establish dynamic linkage ended with return
HM2304E
code %1. code %1. If the return code is greater than zero, review the
other messages.
The %1 method is only valid for Rules with an execution The method stated is only supported for rules with an execution
HM2305E
environment of MVSBAT. environment of MVSBAT.
HM2306I %1 %2 in version %3 is already defined for %4 The method stated has already been successfully executed.
%1 %2 in version %3 is already defined for static linkage. You
%1 %2 in version %3 is already defined for Rule
HM2307I tried to establish a static linkage relationship that already
collapse.
exists.
%1 %2 in version %3 is already defined for static linkage. You
HM2308I %1 %2 in version %3 is already defined for Rule expand. tried to establish a static linkage relationship that already
exists.
The %1 method requires a Configuration Unit named
HM2309E Create a Configuration Unit with the name COLLAPSE.
COLLAPSE.
Value for %1 is undefined. The stated initialization variable is
HM2401E Value for &BPL.INIVAR is undefined.
not defined.Contact your System Administrator.
Program to define collection ids by Project ended with return
Program to define collection ids by Project ended with
HM2402E code %1. If the return code is greater than zero, see other
return code %1.
messages.
BindPlan action only applicable when DB2 packages are BindPlan action only applicable when DB2 packages are used.
HM2403E
used. BindPlan action only applicable when DB2 packages are used.
The region id is a required parameter. Enter a valid region id
HM2501E Enter Region Id.
for the CICS or IMS region to be updated.
Enter Version. The version is a required parameter. Enter the
HM2502E Enter Version.
version to be updated.
The minimum transaction id is a required parameter. Enter the
HM2503E Enter Minimum Transaction. first transaction id to be available for transaction assignment
during preparation.
The maximum transaction id is a required parameter. Enter the
HM2504E Enter Maximum Transaction. last transaction id to be available for transaction assignment
during preparation for this region.
The region type is a required parameter. Enter the region type
HM2505E Enter Region Type. for this region. The available types are 'C' for CICS, 'I' for IMS
and 'B' for batch.
The minimum and maximum transaction ranges must contain
Number of characters for minimum and maximum
HM2506E the same number of characters. Correct the problem and retry
transactions must be equal.
the operation.


Enter alphanumeric characters for the transaction range. The
transaction range must contain alphanumeric characters.
HM2507E Enter alphanumeric characters for the transaction range.
Remove the non-alphanumeric characters and retry the
operation.
Character C is reserved for CICS transactions. Reenter The character 'C' is reserved for CICS transactions. Specify a
HM2508E
transaction range. valid character and retry the operation.
The value of minimum transaction exceeds value of maximum
Value of minimum transaction exceeds value of transaction. The minimum transaction must be smaller than the
HM2509E
maximum transaction. maximum transaction specified. Correct the problem and retry
the operation.
The transaction table cannot be updated due to a DB2 error.
Unable to define transactions for region due to DB2 Review any other messages that are displayed with this
HM2510E
error. message. Correct the problem and retry the operation. If the
problem persists then contact your System Administrator.
The minimum transaction already exists for this region. Review
HM2511E Minimum transaction already exists.
the region definition and correct the range if necessary.
The maximum transaction already exists for this region.
HM2512E Maximum transaction already exists. Review the transaction definitions for this region and correct
the range if necessary.
The specified transaction range conflicts with a previously
New transaction range overlaps previously defined
HM2513E defined range. Review the range of transactions specified to
range.
this region and correct the problem if necessary.
%1 default value set to %2. The specified default value is set to
HM2601I No access rights defined for user %1 Id %2
the indicated value. Review and verify the value is acceptable.
This download request or a previous one has read to the end of
the file. A request to download failed because it reached EOF.
Retry the operation, if the problem persists then contact your
This download request or a previous one has read to the System Administrator. Your administrator should review the
HM3004E
end of the file. allocations of the download files to ensure that proper space
has been allocated to the DD names of DOWNTXT,
DOWNKWD and DOWNSRC. These files are allocated in the
HMFMAIN EXEC in the BASEQUAL Clist library.
Error parsing drawing and creating list of tokens, possibly due
to invalid token length. An error occurred when attempting to
Error parsing drawing and creating list of tokens,
HM3014E parse a drawing and to create a list of tokens. The problem can
possibly due to an invalid token length.
result from an invalid token length. Contact your System
Administrator.
The Drawing may have become corrupted. An error occurred
when attempting to parse a drawing and to create a list of
Error parsing drawing and creating list of tokens. tokens. Because the drawing may be corrupted, you should
HM3015E
Drawing may have become corrupted. review the drawing with the owner of the drawing to determine
the validity of the drawing. If the drawing looks fine then
An error was encountered while attempting free the An error is encountered while attempting free the drawing
HM3016E
drawing mainframe token mainframe token. Contact your System Administrator.
The entity or relation code is too high or too low. Contact your
HM3053E The entity or relation code is too high or too low.
The data set to be associated could not be allocated. The
attempt to allocate a data set to be associated failed. Your
administrator should review the allocations of the download
HM3055E The data set to be associated could not be allocated. files to ensure that proper space has been allocated to the DD
names of DOWNTXT, DOWNKWD and DOWNSRC. These
files are allocated in the HMFMAIN EXEC in the BASEQUAL
Clist library.


The data set to be associated could not be opened. Your
administrator should review the allocations of the download
files to ensure that proper space has been allocated to the DD
HM3056E The data set to be associated could not be opened.
names of DOWNTXT, DOWNKWD and DOWNSRC. These
files are allocated in the HMFMAIN EXEC in the BASEQUAL
Clist library.
The data set to be associated could not be deallocated. The
HM3057E The data set to be associated could not be deallocated. attempt to deallocate a data set to be associated failed. Review
and correct the deallocate data set request.
The attempt to allocate a drawing or scope file to be refreshed
The drawing or scope file to be refreshed could not be
HM3065E failed. Review and correct the allocate the drawing or scope file
allocated.
to be refreshed request.
The attempt to allocate the batch CRUD reply file failed.
HM3067E The batch CRUD reply file could not be allocated.
Review and correct the allocate reply file request.
The attempt to open a drawing or scope file to be refreshed
HM3068E failed. Review and correct the open file to be refreshed
opened.
request.
The attempt to open a batch CRUD request file failed. Review
HM3069E The batch CRUD request file could not be opened.
and correct the open batch CRUD request file request.
Processing is stopped because records were not in the refresh
No records in the refresh scoping file, processing
HM3073E scoping file. Review and correct the processing involved with
terminated.
the refresh scoping file.
No explode record found in refresh scoping file, processing
No explode record found in refresh scoping file, terminated. Processing is stopped because no explode record
HM3074E
processing terminated. existed in refresh scoping file. Review and correct the missing
explode record in the refresh scoping file.
The refresh scoping file contains an explode record only, Processing the refresh scoping file uncovered an error;
HM3075E
no scope records. although an explode record exists, there are no scope records.
The refresh scoping file contains a record with an invalid code
The refresh scoping file contains a record with an invalid
HM3076E in positions 14. Internal system error. Contact your System
code (cc 14)
Administrator.
Invalid request arguments to association driver. Internal system
HM3077E Invalid request arguments to association driver.
The attempt to process the association file failed due to an I/O
HM3079E I/O error encountered while processing association file.
error. Review and correct the association file processing.
The header record on the input scope file is not found. OR The
The header record on the input scope file was not found.
HM3085E first re. Internal system error. Contact your System
OR The first re
Administrator.
Attempting to open the batch CRUD file failed. Review and
HM3086E The batch CRUD reply file could not be opened.
correct the open batch CRUD file request.
The attempt to deallocate a drawing or scope file to be
HM3089E refreshed failed. Review and correct the deallocate the
deallocated.
drawing or scope file to be refreshed request.
The attempt to deallocate the CRUD request file failed. Review
HM3090E The CRUD request file could not be deallocated.
and correct the deallocate CRUD request file request.
The attempt to deallocate the CRUD reply file failed. Review
HM3091E The CRUD reply file could not be deallocated.
and correct the deallocate CRUD reply file request.
An error occurred attempting to write a buffer for the drawing
An error was encountered writing a buffer for the
HM3094E file to be refreshed. Review and correct the write buffer
drawing file to be refreshed.
request.
The buffer for the drawing file to be refreshed could not The attempt to close the buffer for the drawing file to be
HM3095E
be closed. refreshed failed. Review and correct the close buffer request.
The attempt to delete the CRUD reply file failed. Review and
HM3096E The CRUD reply file could not be deleted.
correct the delete CRUD reply file request.


The attempt to start another download failed because of the
There are too many file transfers in progress to start
HM3098E number of file transfers now in progress. Review and, if
another download.
appropriate, reissue the download later.
The attempt to allocate the file to be downloaded failed.
HM3099E The file to be downloaded could not be allocated.
Review and correct the allocate file request.
The download request failed because it did not specify the
The download request did not specify the DDNAME of
HM3101E DDNAME of an active file transfer. Review and correct the
an active file transfer.
download request.
HM3102E The downloaded data set could not be deallocated. The attempt to deallocate the downloaded data set failed.
The delete request failed because a fully qualified MVS data
The delete request did not specify a fully qualified MVS
HM3103E set name is not specified. Review and correct the delete
data set name.
request.
The data set specified in the request could not be The attempt to delete the data set specified in the request
HM3104E
deleted. failed. Review and correct the delete data set request.
The attempt to start another upload failed because of the
There are too many file transfers in progress to start
HM3105E number of file transfers now in progress. Review and, if
another upload.
appropriate, reissue the upload later.
HM3106E The file to be uploaded could not be allocated. The attempt to allocate the file to be uploaded failed.
The attempt to open the file to be uploaded failed. Review and
HM3107E The file to be uploaded could not be opened.
correct the open file request.
The upload request failed because it did not specify the
The upload request did not specify the DDNAME of an
HM3108E DDNAME of an active file transfer. Review and correct the
active file transfer.
upload request.
The record condition was raised while processing a file A DDNAME error occurred while downloading the file. Review
HM3110E
transfer request. the HMFLOG and SYSPRINT files.
The transmit condition was raised while processing a file A file transmission error occurred. Review the HMFLOG and
HM3111E
transfer request. SYSPRINT files.
The file transfer request failed because it did not specify the
A file transfer request has not specified the next
HM3112E next sequential block. Review and correct the file transfer
sequential block.
request.
The attempt to perform execute package in batch mode failed
Attempt to execute package in batch mode when batch
HM3169E because the batch is already active. Review and correct the
already active.
execute package request.
An error is detected in HPSSINK. Contact your System
HM3500E Error from HPSSINK.
Administrator.
The @USRENV INI file indicates that the CICS/IMS product is
not installed for the version you are using. Contact your System
HM4000E CICS/IMS is not installed for the option selected. Administrator to determine: 1. If the INI variable
PRODUCT.CICS must be set to Y 2. or, if the CICS/IMS
product must be installed by the Administrator.
You must enter a value in the indicated field before proceeding
HM5000W Enter a value in this field. Then press Enter.
further. Enter a value.
This message is intended for internal use only. This message is
HM8890I Performance Message: %1 %2 %3 used by the AppBuilder logging routines used for general
performance tuning internally.
This message will appear in the results file for any prepare
(FLUSHED) The Previous step did not run because of
HM8891I method. It is informational in only indicating at a glance that a
prior condition codes or program ABEND
job step did not run.
(NOTRUN) The Previous step did not run. This message will
appear in the results file for any prepare method. It is
HM8892I (NOTRUN) The previous step did NOT run.
informational in only indicating at a glance that a job step did
not run.
HM8894I Summary Status for JOB: %1 Summary Status for JOB: %1
HM8899I VSAM Error, VSAM return code = %1, reason code =%2 VSAM Error, VSAM return code = %1, reason code =%2


Errors occurred during processing. See preceding messages
HM9900E Program terminated due to Errors.
to determine cause of program termination.
An incorrect value is specified for the keyword. Review and
HM9901E Invalid Parameter specified for Keyword: %1
correct the value before continuing.
This informational message confirms the specified job name
HM9902I JOBNAME:%1 JOBNUM:%2 submitted
and job number is submitted.
HM9903I Step: %1 Result: %2 Condition Code: %3 Step: %1 Result: %2 Condition Code: %3
%D %T Job started for &RQST.ENTITY_TYPE This informational message confirms the job started for the
HM9905I
&RQST.LNAME (&RQST.SYSTEMID ) entity type and system ID.
%D %T Job Completed for &RQST.ENTITY_TYPE This informational message confirms the job completed for the
HM9906I
&RQST.LNAME entity type and system ID.
Job to perform specified action on entity name abended. The
HM9907E &RQST.METHOD_ID &RQST.LNAME Job ABENDed. specified job has abnormally terminated. Review the job
output to determine the cause of the error.
&RQST.METHOD_ID &RQST.LNAME Job completed
HM9908I Job completed successfully for action issued on entity name.
successfully.
Action for entity name ended with errors. The specified job has
&RQST.METHOD_ID &RQST.LNAME Ended with
HM9909E completed with errors. Review the job output to determine the
errors.
cause of errors.
<generic message line> A generic message used to display
direct output from a program. This message usually follows
HM9916I %1 another message determined by the program. This message
will contain additional messages or output data to support the
previous message.
%1 %2, Ended with return code %3, reason code %4. Review
HM9920E %1 %2, Ended with return code %3, reason code %4
preceding messages to determine the cause of the error.
Reason code 40, PROGRAM/CLIST/REXX EXEC was
HM9921E Contact your System Administrator.
not Found
JOBNAME:%1 JOBNUM:%2 for &RQST.ENTITY_TYPE
HM9922I
&RQST.LNAME (&RQST.SYSTEMID )
HM9930I %1
HM9931I %1 %2
HM9932I %1 %2 %3
HM9933I %1 %2 %3 %4
HM9934I %1 %2 %3 %4 %5
HM9935I %1 %2 %3 %4 %5 %6
HM9936I %1 %2 %3 %4 %5 %6 %7
HM9937I %1 %2 %3 %4 %5 %6 %7 %8
HM9938I %1 %2 %3 %4 %5 %6 %7 %8 %9
HM9940I &rqst.msg1
HM9941I &RQST.MSG1 &RQST.MSG2
HM9942I &RQST.MSG1 &RQST.MSG2 &RQST.MSG3
&RQST.MSG1 &RQST.MSG2 &RQST.MSG3
HM9943I
&RQST.MSG4
HM9944I
&RQST.MSG4 &RQST.MSG5
HM9945I
&RQST.MSG7


&RQST.MSG7 &RQST.MSG8
TSO LINK Return code &HMPCOPY.RETCC Reason
HM9977I code: &HMPCOPY.REASON ABEND CODE:
&HMPCOPY.ABCODE
Correct the control statements in the EXEC and retry the
HM9978I Allocation SYNTAX Error.
operation.
HM9979I Allocation SYNTAX Error, FILEID: %1
operation.
HM9980I Cannot Delete file/ File may not exist
operation.
Review preceding and subsequent messages to determine the
HM9981W Cannot Delete file. Filename is missing.
cause of the warning.
File Id is missing a value for DISP or SYSOUT keyword.
HM9982E Fileid %1 requires the DISP or SYSOUT parameter.
Correct this before proceeding.
HM9983E Cannot Delete file %1 based on its Usage Code %2 Review the error code in IBM C/370 Programming Guide.
Review preceding and subsequent messages to determine the
HM9984W File %1 not found.
cause of the warning.
The attempt to release the specified module failed. Restart
HM9986E Cannot release module: %1 repository. If error occurs repeatedly, contact your System
Administrator.
Review preceding and subsequent messages, a default value
HM9987W Variable %1 is missing.
may have been assigned to the missing variable.
An error is detected with the HMCWINI.CNT variable, which is
HM9988E HMCWINI.CNT variable missing or invalid.
missing or invalid. Review and correct the variable.
The attempt to fetch the specified module failed. Restart
HM9989E Cannot fetch module: %1 repository. If error occurs repeatedly, contact your System
Administrator.
The attempt to read the INI file(s) failed because the REXX
Cannot perform READ INI, DDName REXX variable not
HM9990E variable DDNAME is omitted. Review and correct the omitted
specified.
variable.
Cannot perform READ INI. Open error on Control An open error occurred while attempting to read the INI file. If
HM9991E
Record file. error occurs repeatedly, contact your System Administrator.
An error is detected with the DDNAME or DSNAME: it is either
HM9992E DDNAME or DSNAME may be missing or invalid. missing or invalid. Review and correct the missing or invalid
data.
Unable to deallocate file for DDNAME, DSNAME, and member.
Free Error, DDNAME: %1, DSNAME: %2, MEMBER:
HM9993E Review preceding and subsequent messages to determine
%3
cause of error.
DDNAME: %1, DSNAME: %2, MEMBER: %3 DISP: %4
HM9994I
DDNAME: %1, DSNAME: %2, MEMBER: %3 DISP: %4
A system allocation error is detected with the specified error
HM9995E Allocation error, Error code: %1, Reason code: %2
code and reason code.
The attempt to format the specified message failed. Contact
HM9996E Cannot format message : %1
The attempt to locate the specified message failed. Contact
HM9997E Cannot locate message : %1


The attempt to open the specified VSAM message file failed.
HM9998E Cannot open VSAM message file DD:%1 Retry operation, if error persists, contact your System
Administrator.
Cannot open Output message file DD:%1. The attempt to open
HM9999E Cannot open Output message file DD:%1 the specified output message file failed. Retry operation, if
error persists contact your System Administrator.
PDF000E An ISPF Error has occurred Review and correct the ISPF usage.
An error is detected: the specified function had the identified
PDF001E Function: %1, Return code: %2
return code. Review and correct the function requested.
Rebuild JOB for Rule submitted. This informational message
RBLD00I Rebuild JOB for Rule submitted.
confirms that a Rebuild Job is submitted for the rule.
The attempt to relink failed due to the error found in module
RBLD03I Unable to Relink due to an error in module HMCXRLE
HMCXRLE. Review and correct the error in the module.
No DBRM's found for Components and Rules, unable to No DBRM's found for Components and Rules, unable to
RBLD05E
Rebind. Rebind.
No Plan has been assigned to this rule, please prepare No Plan has been assigned to this rule, prepare rule before
RBLD07E
rule before Rebinding. Rebinding.
The attempt to rebuild the rule failed because no rebuild
RBLD08I No Rebuild options selected, rule not rebuilt.
options were selected. Review and correct the rebuild request.
This informational message confirms that a Reinstall Job is
RBLD09I Reinstall Job for Rule submitted.
submitted for the rule.
This informational message informs that you must prepare the
RBLD10I Rule selected must be prepared before being reinstalled.
selected rule before reinstalling it.
Invalid execution environment, only CICS rules may be The attempt to build the execution environment failed because
RBLD11I
reinstalled. it is invalid. Only the CICS rules can be reinstalled.
The attempt to open the specified file failed. Review and
RM0001E Unable to open file %1
correct the open file request.
The attempt to perform remote initiation failed because the
Method %1 must be enabled for remote initiation.
RM0002E specified method must be enabled first. Review and enable the
Request cancelled.
method request.
The remote method initiation completed with the indicated
RM0003I Remote Method Initiation ended with return code %1. return code. Review and correct any failure the return code
indicates.
The attempt to write to the specified file for DD failed. Review
RM0004E Unable to write to file for DD: %1.
and correct the write request.
This informational message informs the specified default value
RM0005I %1 default value set to %2.
is set to the indicated value.
An error is detected: the input request file allocated to the
RM0006E Input request file allocated to DD: %1 is empty.
indicated DD is empty. Review and correct the empty condition.
The attempt to read the specified file for DD failed. Review and
RM0007E Unable to read file for DD: %1.
correct the read file request.
Records in file for DD: %1 are not in correct sequence. The user profile record must precede the request record(s). An
RM0008E The user profile record must precede the request incorrect sequence error is detected in the file for the precedes
record(s). the request record(s).
This informational message reports that no request is found for
RM0009E No request found for user %1.
the specified user. Review and correct the user request,
An error occurred because the specified predecessor job does
Predecessor Job %1 %2 does not exist. Method request
RM0010E not exist. The method request is terminated. Review and
terminated.
correct the missing retrieve status request.
The attempt to retrieve status of the specified predecessor job
Unable to retrieve status of Predecessor Job %1 %2.
RM0011E failed. The method request is terminated. Review and correct
Method request terminated.
the retrieve status request.

Enterprise Development Messages (Part 2) RM0012E

The attempt to generate the JCL member name failed. Review
RM0012E Unable to generate JCL member name.
and correct the generate request.
The attempt to retrieve the Rep ID to generate the JCL
Unable to retrieve RepId to generate JCL member
RM0013E member name failed. Review the indicated return code and
name, rc: %1.
correct the retrieve Rep ID request.
Unable to update control number. Current member %1 Unable to update control number. Current member %1 may be
RM0014W
may be replaced by next method request. replaced by next method request.RM0014
An error occurred attempting to save the schedule request
Unable to save scheduled request issued in repository issued in the specified repository, version, and method for the
RM0015E
%1 version %2 method %3 for entity %4 %5. designated entity. Review and correct the save scheduled
request.
An error occurred attempting to save the schedule request
Unable to save scheduled request issued in repository
issued in the specified repository, version, and method for the
RM0016E %1 version %2 method %3 for relationship between %4
designated relationship. Review and correct the save
%5 and %6 %7.
scheduled request.
The attempt to add status for the specified job failed. Review
RM0017E Unable to add status for job %1 %2.
and correct the add status request.
RM0018I Job submitted. This informational message confirms the job is submitted.
Job is currently executing. This informational message
RM0019I Job is currently executing.
confirms the job is now running.
RM0020I Job completed. This informational message confirms the job has completed.
RM0021E Unable to update status for job %1 %2. Review and correct the update status request.
RM0022E Unable to fetch %1 module %2. Review and correct the fetch module request.
%1 module %2 for %3 %4 terminated with return code Review the return code, and correct the module termination
RM0023E
%5. failure
RM0024E %1 %2 for %3 %4 terminated with return code %5. Review the return code, and correct the termination failure.
The attempt to retrieve JCL job card information failed. The
Unable to retrieve JCL job card information return code
RM0025E request is terminated with the indicated return code. Review
%1. Request terminated.
and correct the retrieve JCL job card information request.
The attempt to define the specified variable for file tailoring
Unable to define variable %1 for file tailoring. Request
RM0026E failed. Review and correct the define variable for file tailoring
terminated.
request.
The attempt to retrieve the specified variable from the REXX
RM0027E Unable to retrieve variable %1 from the REXX pool. pool failed. Review and correct the retrieve variable from the
REXX pool request.
This informational message reports that repository is disabled.
RM0028E Repository currently disabled. All requests terminated. All current requests are terminated. Review those cancelled
requests, and reissue them later.
This informational message reports the specified repository
Repository version %1 currently disabled. All requests
RM0029E version is disabled. All current requests are terminated. Review
terminated.
those cancelled requests, and reissue them later.
A security check error is detected: the specified object is
RM0030E Security Check failed. Object %1 locked.
locked. Review and resolve the lock violation.
A security check error occurred when the specified user is not
Security Check failed. User %1 not authorized to access
RM0031E authorized to access the indicated item. Review and resolve
%2.
the authorization violation.
A security check error occurred when the specified user is not
Security Check failed. User %1 not authorized to
RM0032E authorized to execute the indicated method. Review and
execute method %2.
resolve the authorization violation.
The attempt to load the security table failed. Review and
RM0033E Unable to load security table.
correct the load security table request.
The attempt to put a data record for the specified item into the
Unable to put data record for %1 %2 into REXX pool.
RM0034E REXX pool failed Review the request termination, and correct
Request terminated.
the put data record request.

RM0035E Enterprise Development Messages (Part 2)

The attempt to retrieve the specified variable from the REXX
Unable to retrieve variable %1 from the REXX pool.
RM0035E pool failed. Review the request termination, and correct the
Request terminated.
retrieve variable request.
The attempt to put method parameters into the REXX pool
Unable to put method parameters into REXX pool.
RM0036E failed. Review the request termination, and correct the put
Request terminated.
method parameters request.
The attempt to generate JCL for the specified method failed.
JCL for method %1 on %2 %3 cannot be generated. The failure happened while file tailoring the indicated skeleton.
RM0037E
Error occurred during file tailoring of skeleton %4. Review and correct the generate JCL and file tailoring
requests.
The attempt to retrieve attributes of the specified method failed.
RM0038E Unable to retrieve attributes of method %1.
Review and correct the retrieve attributes request.
The attempt to put a data record for the specified relation failed,
Unable to put data record for relation %1 between %2
RM0039E and the request is terminated. Review and correct the put
%3 and %4 %5. Request terminated.
record request.
Security check failed. User %1 not authorized to project
RM0040E Security check failed. User %1 not authorized to project %2.
%2.
%1 module %2 for relation between %3 %4 and %5 %6 %1 module %2 for relation between %3 %4 and %5 %6
RM0041E
terminated with return code %7. terminated with return code %7.
%1 %2 for relation between %3 %4 and %5 %6 %1 %2 for relation between %3 %4 and %5 %6 terminated
RM0042E
terminated with return code %7. with return code %7.
JCL for method %1 on relation %2 between %3 %4 and JCL for method %1 on relation %2 between %3 %4 and %5 %6
RM0043E %5 %6 cannot be generated. Error occurred during file cannot be generated. Error occurred during file tailoring of
tailoring of skeleton %7. skeleton %7.
Unknown return code, possible security error (ACF2
SVFFFFE For more information, see page 5-1.
Violation).
Request for exclusive use of a shared data set cannot be
SV020CE For more information, see page 5-1.
honored.
SV0204E Real storage unavailable.Message Description For more information, see page 5-1.
SV0208E Reserved.Message Description For more information, see page 5-1.
Unit name specified is undefined. For more information, see
SV021CE Unit name specified is undefined.Message Description
page 5-1.
Requested dataset unavailable. The dataset is allocated
SV0210E to another job and its usage attribute conflicts with this For more information, see page 5-1.
request.
The unit specified in the allocation request is not available at
this time. This may be caused by an invalid unit specification
or the unit is offline. Verify that the specified unit is correct. If
Unit(s) not available; or, if allocating an internal reader,
SV0214E not, check the INI configurations values for
all defined internal readers are already allocated.
TUNITVOL,VUNITVOL,PUNITVOL in @HPSENV to ensure
they are correct. Correct the error condition and retry. For
more information, see page 5-1.
The volume specified in the allocation request is not available
at this time. This may be caused by an invalid volume
specification or it is offline or the user does not have the
Specified volume or an acceptable volume is not
authorization to mount the specified volume. Verify that the
SV0218E mounted, and user does not have volume mounting
specified volume is correct. If not, check the INI configurations
authorization
values for TUNITVOL, VUNITVOL, PUNITVOL in @HPSENV
to ensure they are correct. Correct the error condition and
retry. For more information, see page 5-1.
The volume specified in the allocation request is mounted on
an eligible permanently resident or reserved unit. Verify that
Volume mounted on ineligible permanently resident or the specified volume is correct. If not, check the INI
SV022CE
reserved unit. configurations values for TUNITVOL, VUNITVOL, PUNITVOL
in @HPSENV to ensure they are correct. Correct the error
condition and retry. For more information, see page 5-1.

Enterprise Development Messages (Part 2) SV0220E

authorization to mount the specified volume. Verify that the
SV0220E Requested volume not available.
specified volume is correct. If not, check the INI configurations
to ensure they are correct. Correct the error condition and
Eligible device types do not contain enough units. Verify that
the specified volume is correct. If not, check the INI
SV0224E Eligible device types do not contain enough units. configurations values for TUNITVOL, VUNITVOL, PUNITVOL
authorization to mount the specified volume or the specified
SV0228E Specified volume or unit in use by system. volume is in use. Verify verify that the specified volume is
correct. If not, check the INI configurations values for
TUNITVOL, VUNITVOL, PUNITVOL in @HPSENV to ensure
they are correct. Correct the error condition and retry. For
more information, see page 5-1.
The catalog required in the allocation request is not available at
this time. This may be caused by an invalid dataset
Required catalog not mounted, and user does not have specification or the user does not have the authorization to
SV023CE
volume mounting authorization. mount the necessary volume for the catalog. Verify that the
specified dataset is correct. Correct the error condition and
authorization to mount the specified volume or the specified
Permanently resident or reserved volume on required
SV0230E volume is in use. Verify that the specified volume is correct. If
unit.
not, check the INI configurations values for TUNITVOL,
VUNITVOL, PUNITVOL in @HPSENV to ensure they are
correct. Correct the error condition and retry. For more
information, see page 5-1.
More than one device required for a request specifying a
SV0234E For more information, see page 5-1.
specific unit.
SV0238E Space unavailable in task input output table (TIOT). For more information, see page 5-1.
Operating system managed resource was unavailable to Check to see if the resource is available. If not, correct the
SV024CE
the subsystem. condition and retry. For more information, see page 5-1.
SV0240E Requested device is a console. For more information, see page 5-1.
SV0244E Telecommunication device not accessible. For more information, see page 5-1.
SV0248E MSS virtual volume cannot be mounted. For more information, see page 5-1.
Requested device is boxed and cannot be accessed, as
SV025CE -
a result of an I/O error condition or the operator issuing a For more information, see page 5-1.
1-
VARY X, OFFLINE, FORCE command.
SV0250E Subsystem resource not available. For more information, see page 5-1.
The TIOT resource is currently unavailable and the user
requested conditional ENQ on the resource.
There was not a sufficient number of nonrestricted units
to satisfy the request, or JES3 selected a JES3managed
restricted unit to satisfy the request. Restricted units are
described in SPL: System Generation Reference.

SV0260E Enterprise Development Messages (Part 2)

or it is offline or the user does not have the authorization to
mount the specified unit or the specified unit is in use. Verify
SV0260E Unit does not meet specified status requirements.
that the specified unit is correct. If not, check the INI
configurations values for TUNITVOL, VUNITVOL, PUNITVOL
or it is offline or the user does not have the authorization to
mount the specified unit or the specified unit is in use. Verify
SV0264E Invalid request due to current unit status.
that the specified unit is correct. If not, check the INI
configurations values for TUNITVOL, VUNITVOL, PUNITVOL
this time. The message indicates that the tape unit may be
SV0268E Tape device is broken.
broken. Correct the error condition and retry. For more
One or more parameters specified in the allocation request are
not valid. Check the INI configurations values for TUNITVOL,
SV03A0E Subsystem detected an invalid parameter. VUNITVOL, PUNITVOL in @HPSENV to ensure they are
correct. Correct the error condition and retry. For more
Unable to protect data set/volume because of conflicting
SV03A4E For more information, see page 5-1.
keyword specification.
SV033CE Reserved. For more information, see page 5-1.
SV0340E Reserved. For more information, see page 5-1.
A locate error occurred accessing the dataset specified in the
message HM9994I, which contains the DDNAME and dataset
name in question. This dataset is expected to be available.
SV035CE Invalid PARM specified in text unit.
Check to ensure no errors were encountered during the
allocation of the specified file. For more information, see
page 5-1.
Overriding disposition of DELETE invalid for data set
allocated as SHR.
The parameter list specified in the allocation request is not
valid. Review the message for the erroneous parameter and
correct. Check the clist invocation and/or the INI configurations
SV036CE Invalid parameter list format. to ensure they are correct. Correct the error condition and retry.
Refer to the IBM MVS/Extended Architecture System
Programming Library: System Macros and Facilities manual for
more information. These codes are specified in the SVC 99
Error Reason Codes sections.
SV0360E Invalid KEY specified in text unit. For more information, see page 5-1.
JOBLIB/STEPLIB/JOBCAT/STEPCAT specified as
ddname, or associated with specified dsname.
SV0368E Authorized function requested by unauthorized user. For more information, see page 5-1.
SV037CE Invalid LEN specified in text unit. For more information, see page 5-1.

Enterprise Development Messages (Part 2) SV0370E

SV0374E Invalid # specified in text unit. Invalid # specified in text unit.
SV0378E Duplicate KEY specified in text unit. For more information, see page 5-1.
SV038CE Duplicate ddnames specified. For more information, see page 5-1.
Mutually exclusive KEY specified. Two keys that cannot
be used together were used in the request.
Mutually inclusive KEY not specified. One key was
used; two should have been used.
SV0388E Required key not specified. For more information, see page 5-1.
SV039CE Device type and volume are incompatible. For more information, see page 5-1.
GDG group name specified with relative generation
number exceeds 35 characters.
SV0394E Status and relative generation number are incompatible. For more information, see page 5-1.
Volume sequence number exceeds the number of
volumes.
SV04ACE Subsystem is not operational. For more information, see page 5-1.
SV04A0E Specified MSVGP name not defined. For more information, see page 5-1.
SV04A4E Subsystem request in error. For more information, see page 5-1.
Subsystem does not support allocation via key
SV04A8E For more information, see page 5-1.
DALSSNM.
SV04BCE MSS volume select error. For more information, see page 5-1.
SV04B0E Subsystem does not exist. For more information, see page 5-1.
Protect request not processed; RACF not in system or
SV04B4E For more information, see page 5-1.
not active.
SV04B8E MSS not initialized for allocation. For more information, see page 5-1.
SV04CCE Invalid reference to an OUTPUT JCL statement. For more information, see page 5-1.
SV04C0E Protect request failed; user not defined to RACF. For more information, see page 5-1.
The last request was for a VOL=REF to a dsname or
DCB=dsname that exceeded the maximum allowable
SV04C4E dsname referbacks. A maximum of 972 backward For more information, see page 5-1.
references are allowed if the data set names are 44
characters in length.
A non-zero return code was set in register 15 from either
common allocation or JFCB housekeeping; however, the
SV04C8E SIOT reason code (SIOTRSNC) was not set. This For more information, see page 5-1.
problem might result from installation modification of the
eligible device table (EDT).
SV0410E Specified ddname unavailable. For more information, see page 5-1.
Specified ddname or dsname associated with an open
data set.
SV0424E Deconcatenation would result in duplicate ddnames. For more information, see page 5-1.

SV0428E Enterprise Development Messages (Part 2)

The system could not deallocate enough of the
SV043CE resources being held in anticipation of reuse to meet the For more information, see page 5-1.
control limit.
DDname specified in ddname allocation request is
SV0434E associated with a convertible or non-permanently For more information, see page 5-1.
allocated resource.
SV0438E Specified ddname not found. For more information, see page 5-1.
Request was made for a data set that has a disposition
SV044CE of delete; this request cannot be honored because the For more information, see page 5-1.
data set may be deleted at any time.
SV0440E Specified dsname not found. For more information, see page 5-1.
Relative entry number specified in information retrieval
request not found.
Request for new data set failed; the data set already
exists.
Specified dsname to be deallocated is a member of a
SV045C E For more information, see page 5-1.
permanently-concatenated group.
Request would cause the limit of 1635 concurrent
allocations to be exceeded.
SV0454E DD name in DCB reference not found. For more information, see page 5-1.
Dsname in DCB reference or volume reference is a
GDG group name.
SV046CE Remote work station not defined to job entry subsystem. For more information, see page 5-1.
Specified dsname or member to be deallocated is not
associated with specified ddname.
SV0464E Specified dsname to be deallocated is a private catalog. For more information, see page 5-1.
SV0468E Error while allocating or opening a private catalog. For more information, see page 5-1.
SV047CE Unable to establish ESTAE environment. For more information, see page 5-1.
SV0470E User unauthorized for subsystem request. For more information, see page 5-1.
SV0474E Error while attempting to select optimum device. For more information, see page 5-1.
SV0478E Unable to process job entry subsystem request. For more information, see page 5-1.
SV048CE GDG pattern DSCB not found. For more information, see page 5-1.
The number of units needed to satisfy the request
exceeds the limit.
SV0484E Request denied by operator. For more information, see page 5-1.
SV0488E GDG pattern DSCB not mounted. For more information, see page 5-1.
SV049CE MSS virtual volume no defined. For more information, see page 5-1.
SV0490E Error changing allocation assignments. For more information, see page 5-1.
SV0494E Error processing OS CVOL. For more information, see page 5-1.
SV0498E MSS virtual volume not accessible. For more information, see page 5-1.
SV17FFE Locate error. For more information, see page 5-1.
SV1708E Locate error. For more information, see page 5-1.
SV1718E Locate error. For more information, see page 5-1.
SV172CE Locate error. For more information, see page 5-1.
SV47FFE DADSM allocate error. For more information, see page 5-1.
SV57FFE CATALOG error. For more information, see page 5-1.

Enterprise Development Messages (Part 2) SV67FFE

SV67FFE OBTAIN error. For more information, see page 5-1.
SV7700E Subsystem error. For more information, see page 5-1.
A Subsystem interface system error occurred while
processing key DALSSNM
SV8700E Scheduler JCL Facility (SJF) error. For more information, see page 5-1.
SV8704E Scheduler JCL Facility access function error. For more information, see page 5-1.
SV8708E Mutual exclusive checker error. For more information, see page 5-1.
SV970CE Severe SMS VTOC error. For more information, see page 5-1.
SV9700E Severe SMS IDAX error. For more information, see page 5-1.
SV9704E Severe SMS CATALOG error. For more information, see page 5-1.
SV9708E Severe SMS VOLREF error. For more information, see page 5-1.
SV9710E Severe SMS DISP error. For more information, see page 5-1.
SV9714E Severe SMS COPY SWB error. For more information, see page 5-1.
SV9728E System error while allocating a device. For more information, see page 5-1.
XWU010I Extended Where Used Options See other messages.
Confirm that Printer Destination is Correct. Then Press
XWU011I
ENTER.
XWU012I Printer . . . . . . .

CHAPTER
6 ENTERPRISE EXECUTION MESSAGES
This section lists execution (run-time) messages you may encounter when you run an application in an
enterprise environment.
Enterprise Execution Messages

Table 6-1 lists the enterprise application execution messages.
Table 6-1 Enterprise Execution Messages
Code Text Description

Informational message that accompanies other error
messages. PROGRAM = The eight-character name of the
PROGRAM= XXXXXXXX DATE=
HPS0000I program that issued this message
MM/DD/YY TIME= HH:MM:SS
DATE = current date
TIME = current time
A call is made to the error message handler, but the error
UNKNOWN CONDITION message key passed does not match any of the error
HPS0001I DETECTED IN PROGRAM messages in the current error messages database.
XXXXXXXX XXXXXXXX specifies the name of the program that issued
the call.Contact your System Administrator.
HPS0002I TRANSACTION COMPLETED The transaction has finished processing.
A message prompting for the input of one of the displayed
HPS0003I ENTER SELECTION
selections.
A message that indicates that a new copy of the specified
HPS0034I NEW COPY FORCED program is forced by reducing the program use count to zero
prior to issuing the new copy request.
HPS0035I TRANSACTION COMPLETE The transaction has finished processing.
A message that indicates that the program specified for the
HPS0036I PROGRAM IS RESIDENT new copy request is resident and in use.Wait until the
program is no longer resident and retry the new copy request.
HPS/CICS SECURITY HAS BEEN
HPS0037I System security has been activated for this CICS region.
ACTIVATED.
HPS/CICS SECURITY HAS BEEN
HPS0038I System security has been deactivated for this CICS region.
DEACTIVATED.
TOP OF PULL-DOWN
HPS0200W There are no more pull-down selections to be displayed.
SELECTIONS

Enterprise Execution Messages HPS0201W
Table 6-1 Enterprise Execution Messages (Continued)

BOTTOM OF PULL-DOWN
HPS0201W There are no more pull-down selections to be displayed.
SELECTIONS
HPS0202W TOP OF TEXT There is no more text to be displayed.
HPS0203W BOTTOM OF TEXT There is no more text to be displayed.
HPS0204W TOP OF DATA There is no more data to be displayed.
HPS0205W BOTTOM OF DATA There is no more data to be displayed.
HPS0206W TOP OF LIST There are no more list items to be displayed.
HPS0207W BOTTOM OF LIST There are no more list items to be displayed.
HELP FOR THIS PANEL IS NOT Help text for the panel requested cannot be found. Check to
HPS0208W
AVAILABLE see if the help text for the panel has been created.
HELP FOR THIS FIELD IS NOT Help text for the field requested cannot be found. Check to
HPS0209W
AVAILABLE see if the help text for the field has been created.
HELP FOR HELP TEXT IS NOT Help for help text requested cannot be found. Check to see if
HPS0210W
AVAILABLE the help for help text has been created.
HELP FOR THIS LISTBOX IS NOT Help for this list box cannot be found. Check to see if the help
HPS0211W
AVAILABLE text has been defined.
Warning message indicating that the System security feature
is not currently active. This message occurs when requesting
HPS0212W HPS SECURITY NOT ACTIVE security information and System security is not
active.Activate System security or disable the display of
warning messages.
An invalid selection is selected. Select a highlighted
HPS0400E REENTER SELECTION
selection.
UNAVAILABLE PROCESS
An unavailable process is selected. Select a highlighted
HPS0401E SELECTED; REENTER
process.
SELECTION
HPS0402E INVALID FUNCTION REQUEST An invalid selection is selected. Select a valid selection.
Input is not allowed when this key has been pressed. Either
INPUT NOT ALLOWED. ERASE OR
HPS0403E enter data and press a different key or enter no data and
ENTER ANOTHER KEY
press the chosen key.
The function key pressed has no defined function. Choose
HPS0404E FUNCTION KEY NOT DEFINED
another function key.
Some input is required when this key is pressed. Enter the
HPS0405E INPUT REQUIRED
required data.
Input fields have failed basic, range, or cycle edit checks.
HPS0406E HIGHLIGHTED FIELDS IN ERROR Failing fields are highlighted. Correct the input and
re-execute.
Input is not allowed in this field (may not be on the currently
HPS0407E INPUT NOT ALLOWED active panel). Retry the function key or refresh the screen
and retry the key.
Transaction is not initiated from a terminal. System software
TERMINAL IS REQUIRED FOR does not support this transaction. Initiate the transaction from
HPS0408E
THIS TRANSACTION a terminal. If you initiated this transaction from a terminal,
FUNCTION KEY IS NOT
HPS0409E The module does not support the function key requested.
AVAILABLE
You requested a function that requires System security to be
HPS0412E HPS SECURITY NOT ACTIVE active, but System security is not active. Activate System
security and retry the function.
The System table specified has not been loaded. XXXXXXXX
FAILURE TO LOAD HPS TABLE
HPS0416E specifies the name of the table that has not been loaded.
XXXXXXXX
Verify that CICS tables are specified properly and retry.
6-2 Enterprise Execution Messages

HPS0420E Enterprise Execution Messages

The System table that is required does not have any entries.
HPS0420E HPS TABLE IS EMPTY XXXXXXXX
XXXXXXXX specifies the name of the empty table.
A System module executed a CICS command that raised an
EXEC CICS COMMAND ERROR
HPS0421E error condition. XXXXYY specifies that code (XXXX=EIBFN
CODE=XXXXYY
YY=EIBRESP). Contact your System Administrator.
The program specified in the new copy request is currently in
HPS0431E CURRENT PROGRAM IS IN USE use. Wait until the program is no longer in use before retrying
the new copy request.
Invalid input is entered for the transaction request. Check the
HPS0432E INVALID INPUT, PLEASE REENTER
documentation for the correct transaction input.
The program specified for the new copy request is not found
in the CICS program processing table. Check the rule or
component results to determine whether the entity
preparation is successful. If not, correct the problems
specified in the results and submit the preparation again. If
PROGRAM NOT FOUND IN THE the preparation is successful, try to reinstall the rule or
HPS0433E
PPT component. If the reinstall fails, check with the CICS systems
programmer to verify whether the program processing table
entry exists in a CICS install group that is not installed. If it
does, have the CICS system programmer install the group. If
it does not, have the CICS system programmer add the
program to the CICS program processing table.
INVALID TERMINAL SPECIFIED, A request to initiate a transaction came from an invalid
HPS0434E TRANS WILL BE INITIATED device. System software attempts to initiate the transaction
WITHOUT A TERM unattached to a terminal.Contact your System Administrator.
A new copy of the program specified in the new copy request
could not be found.Check the rule or component preparation
results to verify the entity preparation is successful. If the
preparation is not successful, correct the errors specified in
CANNOT FIND NEW COPY OF the results and prepare the entity again. If the prepare is
HPS0437E
LOAD MODULE successful, check the target CICS load library to verify that
the library has not run out of disk space or directory space. If
it has, the CICS load library must be reallocated. If the CICS
load library has extended to another extent, the CICS region
must be restarted in order to access the new extent.
The user has left the terminal inactive beyond the time-out
HPS0438E TRANSACTION TIMEOUT
limit.
The RuleView transaction has abended unexpectedly, retain
HPS0439E TRLS TRANSACTION ABENDED all dumps and note the conditions which lead up to the
abend.
NO DISK SPACE IS AVAILABLE
HPS0440E No disk space available to add addition records to file.
FOR THE RECORD ADDITION
LENGTH IS GREATER THAN MAX
Length of record to be added to file is longer than maximum
HPS0441E LENGTH SPECIFIED IN THE VSAM
allowed.
CLUSTER
HPS0442E DUPLICATE RECORD FOUND Record to be added to file already exists.
THERE IS MORE THAN ONE
HPS0443E Duplicate record key exists for multiple records.
RECORD WITH THE SAME KEY
THE RECORD SPECIFIED IS NOT
HPS0444E Record does not exist in file.
FOUND
ENTRY PASSED CONTAINS LOW- Async information returned from TRSA or HSA contains low
HPS0445E
VALUES values.
REWRITE COMMAND ISSUED
Attempting to update the file without issuing a read with
HPS0446E WITHOUT A READ WITH UPDATE
update option first.
OPTION

Enterprise Execution Messages HPS0447E

THE RULE CANNOT BE FOUND IN
HPS0447E Broadcast ID table does not have a record of the target rule.
THE BROADCAST ID TABLE
THE NAMED TERMINAL OR
HPS0448E NETNAME COULD NOT BE The terminal ID or netname is no longer active.
LOCATED
THE NETNAME RETURNED DOES
The netname in the TRSA does not match the netname in the
HPS0449E NOT MATCH THE NETNAME IN
TCT for the terminal ID being inquired.
THE TCT
TERMINAL STORAGE AREA NOT
HPS0450E TRSA (Terminal Storage Area) does not exist.
AVAILABLE
HPS0451E TERMINAL IS OUT OF SERVICE Terminal is out of service.
NETNAME FROM LOGICAL INPUT Netname from input logical header is not the same as the
HPS0452E HEADER DOES NOT MATCH THE netname returned from the terminal control table for the
TCT ENTRY terminal ID.
HPS0453E QUEUE IS EMPTY Temporary storage queue is empty.
HPS0454E QUEUE CANNOT BE FOUND Temporary storage queue not found.
Abend code: H0CEA System module executed a CICS
command that raised an error condition. XXXXYY specifies
EXEC CICS COMMAND ERROR the code (XXXX=EIBFN YY=EIBRESP).The task abnormally
HPS0600S
CODE=XXXXYY terminated with a transaction dump. Use the dump to
determine why the failure occurred, or keep the dump and
EXEC CICS READ FAILURE Abend code: H0RE System CICS internal logic error. The
HPS0601S RECORD task abnormally terminated with a transaction dump. Keep
KEY=XXXXXXXXXXXXXXXXXXXX the dump and contact your System Administrator.
Abend code: H002System internal logic error. XXXXXXXX
NO COMMAREA PASSED TO specifies the name of the program that issued the call.Keep a
HPS0602S
PROGRAM XXXXXXXX note of the conditions that lead to the error message. Keep all
transaction dumps and contact your System Administrator.
Abend code: H003System internal logic error. XXXXXXXX
COMMAREA PASSED TO
specifies the name of the program that issued the call.Keep a
HPS0603S PROGRAM XXXXXXXX TOO
note of the conditions that lead to the error message. Keep all
SHORT
Abend code: H004Lack of sufficient system storage to satisfy
GETMAIN FAILED DUE TO LACK the GETMAIN request. XXXXXXXX specifies the name of the
HPS0604S OF SYSTEM STORAGE IN program that issued the GETMAIN.Keep a note of the
PROGRAM XXXXXXXX conditions that lead to the error message. Keep all
Abend code: H005CICS file is disabled at the time System
FILE XXXXXXXX DISABLED ON
CICS attempted to access it. XXXXXXXX specifies the file
HPS0605S REQUEST FROM PROGRAM
name. YYYYYYYY specifies the name of the program that
YYYYYYYY
tried to access the file.Try to enable the file using CEMT.
Abend code: H006.CICS file is not open at the time System
FILE XXXXXXXX NOT OPEN ON
CICS tried to access it. XXXXXXXX specifies the file name.
YYYYYYYY specifies the name of the program that tried to
YYYYYYYY
access the file.Try to open the file using CEMT.
Abend code: H007File could not be found at the time System
FILE XXXXXXXX NOT FOUND ON
attempted to access it. XXXXXXXX specifies the file name.
YYYYYYYY
access the file.Define the file properly.
Abend code: H008The System CICS user is not authorized
FILE XXXXXXXX NOT access to the file. XXXXXXXX specifies the file name.
HPS0608S AUTHORIZED ON REQUEST YYYYYYYY specifies the name of the program that tried to
FROM PROGRAM YYYYYYYY access the file.Grant proper access to the user ID attempting
the transaction.

HPS0609S Enterprise Execution Messages

Abend code: H009A file I/O error is detected during a read
I/O ERROR READING FROM FILE
operation. XXXXXXXX specifies the file name. YYYYYYYY
HPS0609S XXXXXXX FROM PROGRAM
will be replaced by the name of the program that tried to
YYYYYYYY
access the file.Correct the I/O error.
Abend code: H010Problems were detected when trying to
UNABLE TO READ FROM FILE
access the named file. XXXXXXXX specifies the file name.
HPS0610S XXXXXXXX FROM PROGRAM
YYYYYYYY
access the file.Try to correct the problem in the file.
Abend code: H011The program (YYYYYYYY) is unable to
link to the program (XXXXXXXX). XXXXXXXX specifies the
LINK TO PROGRAM XXXXXXXX
HPS0611S name of the program we tried to link to. YYYYYYYY specifies
FAILED IN PROGRAM YYYYYYYY
the name of the program that issued the link request. Make
sure all programs are defined correctly.
Abend code: H012The program (YYYYYYYY) is unable to
UNABLE TO LOAD PROGRAM load the program (XXXXXXXX). XXXXXXXX specifies the
HPS0612S XXXXXXXX IN PROGRAM name of the program we tried to load. YYYYYYYY specifies
YYYYYYYY the name of the program that issued the load request.Make
sure all programs are defined correctly.
Abend code: H013An attempt to initialize a work area for
converse failed. XXXXXXXX specifies the name of the
CVW INITIALIZATION FAILED IN
HPS0613S program that issued the call to 3270 Converse to initialize a
PROGRAM XXXXXXXX
work area.Save all dumps and contact your System
Administrator.
Abend code: H014An attempt to start a specified transaction
ATTEMPT TO START failed. XXXX specifies the name of the transaction.Make sure
HPS0614S
TRANSACTION XXXX FAILED the specified transaction is properly defined.Make sure the
load module is properly defined.
Abend code: H016A transaction is requested to start from an
INVALID TERMINAL SPECIFIED, invalid terminal ID. System software tries to initiate the
HPS0616S TRANS WILL BE INITIATED transaction unattached to a terminal. If this fails, the
WITHOUT A TERM transaction abends.Save all dumps and contact your System
Administrator.
INVALID HPS FUNCTION Abend code: H017An internal System request is invalid.Save
HPS0617S
SPECIFIED all dumps and contact your System Administrator.
Abend code: H018The execution environment specified for
INVALID EXECUTION the rule is invalid.Check the rule to make sure the execution
HPS0618S
ENVIRONMENT environment is valid. If so, save all dumps and contact your
Abend code: H019An internal error is detected with 3270
NON ZERO RETURN CODE FROM
HPS0619S Converse.Save all dumps and contact your System
HPS CONVERSE
Administrator.
Abend code: H020An error occurred in CICS post-cancel
ERROR OCCURRED DURING
HPS0620S processing internal to System software.Save all dumps and
POST-CANCEL PROCESSING
Abend code: H021An error occurred trying to issue a send or
TERMINAL ERROR ON SEND/
HPS0621S a receive from the terminal device.Save all dumps and
RECEIVE
Abend code: H022An error occurred when an internal
System process issued a read from the specified temporary
ERROR ON READQ TS FROM storage queue. XXXXXXXX specifies the name of the
HPS0622S
QUEUE XXXXXXXX temporary storage queue that System software tried to read
from.Check the status of the specified temporary storage
queue, and then contact your System Administrator.

Enterprise Execution Messages HPS0623S

Abend code: H023An error occurred when an internal
System process issued a write from the specified temporary
ERROR ON WRITEQ TS FROM storage queue. XXXXXXXX specifies the name of the
HPS0623S
QUEUE XXXXXXXX temporary storage queue that System software tried to write
to.Check the status of the specified temporary storage
queue, and then contact your System Administrator.
Abend code: H024 An error occurred when an internal
System process tried to access the 3270 Converse global
area. Verify that the HPEGAPA load module that consists of
UNABLE TO LOCATE THE
HPS0624S the System global parameters is not corrupted. Verify that the
CONVERSE GLOBAL AREA
HPECVGP CSECT is included in the HPEGAPA load
module. Save all dumps and contact your System
Administrator.
Abend code: H0IR An invalid request condition is raised
INVALID REQUEST ERROR
when executing the CICS command XXXXXXXXXX.
HPS0625S OCCURRED FOR CICS COMMAND
XXXXXXXXXX specifies the command. Save all dumps and
XXXXXXXXXX
Abend code: H0LE An invalid length condition is raised when
INVALID LENGTH ERROR
executing the CICS command XXXXXXXXXX.
XXXXXXXXXX specifies the command. Save all dumps and
XXXXXXXXXX
Abend code: H0NU An authorization error condition is raised
when executing the CICS command XXXXXXXXXX.
AUTHORIZATION ERROR
XXXXXXXXXX specifies the command. Check external
security audit logs for the resource that is accessed. Grant
XXXXXXXXXX
the appropriate security access, if possible. Save all dumps
An invalid FREEMAIN we issued within The System
INVALID FREEMAIN OCCURRED
HPS0628S XXXXXXXX will be replaced by the name of the program
IN PROGRAM XXXXXXXX
which issued the invalid FREEMAIN. ABEND H028
An attempt to initiate a System rule through RuleView failed.
HPS0629S RULE NOT FOUND: XXXXXXXX
ABEND H029
HPS0630S QUEUE NOT AVAILABLE Temporary storage queue is not available. ABEND H030
Temporary storage queue is being used by another task.
HPS0631S QUEUE IS BUSY
ABEND H031.
An attempt to delete a record failed. FFFFFFFF will be
I/O ERROR DELETING FROM FILE
replaced by the name of the file we are trying to delete from.
HPS0634S FFFFFFFF FROM PROGRAM
PPPPPPPP will be replaced by the name of the program
PPPPPPPP
which tried to delete the record. ABEND H034
An attempt to write a record failed. FFFFFFFF will be
I/O ERROR WRITING TO FILE
replaced by the name of the file we are trying to write to.
HPS0635S FFFFFFFF FROM PROGRAM
PPPPPPPP will be replaced by the name of the program
PPPPPPPP
which tried to write the record. ABEND H035
ASYNC-SUPPORT-ACTIVE FLAG Async flag to indicate async is active has not been set.
HPS0636S
NOT SET ABEND H036
INVALID CARRIAGE CNTL The carriage control used to control printing is not valid.
HPS0637S
CHARACTER ABEND H037
HPS0638S PRINTER OUT OF SERVICE Printer is out of service. ABEND H038
TRANSACTION XXXX ABENDED, An AppBuilder rule has abended in the CICS environment.
HPS0639S
HIT CLEAR SCREEN ABEND H039
Internal System error. Keep all dumps, note the conditions
ERROR CALLING SYSTEM
which led to the abend, and call Customer Technical Support.
HPS0650S STORAGE MANAGER
XXXXXXXXXXXXXXXXXXXX will be replaced by System
XXXXXXXXXXXXXXXXXXX
internal diagnostics. ABEND H050


ERROR CALLING HPS STORAGE
which lead up to the abend, and call Customer Service.
HPS0651S MANAGER
XXXXXXXXXXXXXXXXXXXX will be replaced by System
XXXXXXXXXXXXXXXXXXXX
internal diagnostics. ABEND H051
AN ABEND HAS OCCURRED AND
An AppBuilder rule has abended in the IMS environment.
HPS0654S TRANSACTION HAS BEEN
ABEND H054
TERMINATED
Abend code: H0ID You tried to invoke a System transaction
INVALID DEVICE TYPE
HPS0700S on a terminal device System software does not support. The
DEVICE=XXXX
terminal must be a 3270-type device.
Abend code: H0IS System software does not support the
INVALID SCREEN SIZE
HPS0701S screen size definition for the device. The screen size for the
HEIGHT=XX WIDTH=XXX
terminal must be specified as 24 x 80.
Abend code: H1MB A user tried to build a menu bar screen
that contained more than the screen height minus 11 lines of
menu bar selections. Example: a screen size 24 by 80 cannot
HPS1601S MENU-BAR BUILD OVERFLOW
have more than 13 lines of menu bar selections. A menu bar
screen must contain less than the screen height minus 11
lines of menu bar selections.
Abend code: H1ST A System users process exceeded 18
menu bar levels. Note: A menu bar level is each menu bar
HPS1602S MENU-BAR STACK OVERFLOW that is displayed within a specific process that is selected
from the first menu bar screen. A process cannot exceed 18
menu bar levels.
Abend code: H1MA A System user tried to build a menu bar
MENU-BAR BUILD VIEW ARRAY
HPS1603S that contained more than 38 menu bar selections. A screen
OVERFLOW
must contain less than 38 menu bar selections.
Abend code: H1PA A System user tried to build a pull-down
POP-UP BUILD VIEW ARRAY (pop-up) menu that contained more than 99 pull-down
HPS1604S
OVERFLOW (pop-up) selections. A pull-down (pop-up) menu must contain
less than 99 pull-down (pop-up) selections.
Abend code: H1FA A System user tried to build a function
FUNCTION MENU VIEW ARRAY menu (the master menu) that contained more than 99
HPS1607S
OVERFLOW selections. A function menu must contain less than 99
selections.
A System module is not invoked from a valid source.
XXXXXXXX specifies the name of the program that issued
this message. The task abnormally terminated with a
HPS1660S INVALID ENTRY INTO XXXXXXXX
transaction dump. Use the dump to determine how the
program is invoked or keep the dump and contact your
Abend code: H1CM An invalid COMMAREA is passed to an
INVALID COMMAREA IN internal System module. XXXXXXXX specifies the name of
HPS1661S
XXXXXXXX the program that issued this message. Keep all dumps and
The System log options transaction is entered without a
PROPER OPTIONS ARE ON, OFF, specified option. This is an informational message to prompt
HPS2000I
NOLOG, NOSEND AND NOCONV the user for a valid option. Re-enter the transaction with valid
option.
A match is not found for the input field name, view name, and
SEARCH CRITERIA FAILED FOR
HPS2200W occurrence number. XXXXXXXX specifies the name of the
COMPONENT XXXXXXXX
component that is invoked at the time the error occurred.
The named component is not given a valid color code on
INVALID COLOR CODE IN input. XXXXXXXX specifies the name of the component that
HPS2201W
COMPONENT XXXXXXXX is invoked at the time the error occurred. Change the input
color code to a valid color code.

Enterprise Execution Messages HPS2202W

WRONG CURSOR POSITION, The cursor is not within a field on the screen when the
HPS2202W CURSOR MUST BE UNDER A CGETFLD component is called. Place the cursor in a field on
FIELD the screen and reissue the call to CGETFLD.
The component CGETFLD is called, but none of the fields
NONE OF THE FIELDS SELECTED
HPS2203W selected meet the input search criteria of field name, view
MEET THE SEARCH CRITERIA
name, and occurrence number.
The CGETALT component is called, but none of the changed
NONE OF THE FIELDS ALTERED
HPS2204W fields meet the input selection criteria of field name, view
MEET THE SELECTION CRITERIA
name, and occurrence number.
The panel name passed to the named component does not
match the name of the panel currently conversed.
NO MATCHING PANEL NAME
XXXXXXXX specifies the name of the component that is
HPS2205W WHILE RUNNING COMPONENT
invoked at the time the error occurred. Change the input
XXXXXXXX
panel name to match the name of the panel currently being
conversed.
The view name passed to the named component does not
match any of the view names in the current panel.
NO MATCHING VIEW NAME WHILE
XXXXXXXX will be replaced by the name of the component
HPS2206W RUNNING COMPONENT
that is invoked at the time the error occurred. Change the
XXXXXXXX
input view name to match one of the views in the current
panel.
The small integer passed as input for the elevator position in
the named component is not a valid elevator position.
ELEVATOR POSITION XXXXXX
XXXXXX will be replaced by the input elevator position which
HPS2207W NOT VALID IN COMPONENT
is not valid. YYYYYYYY will be replaced by the name of the
YYYYYYYY
Change the input elevator position.
A list box operation is attempted on a panel that does not
NO LISTBOX IN CURRENT VIEW,
contain a list box. XXXXXXXX will be replaced by the name
HPS2208W ERROR IN COMPONENT
of the component that is invoked at the time the error
XXXXXXXX
occurred. Do not call the named component for this panel.
The occurrence number passed on input to the named
component is not a valid occurrence number. XXXXXX
OCCURRENCE NUMBER XXXXXX
specifies the occurrence number that is passed to the named
HPS2209W INVALID IN COMPONENT
component. YYYYYYYY specifies the name of the
YYYYYYYY
Change the occurrence number to a valid number.
The input operation specified for the named component is not
INVALID OPERATION SPECIFIED valid. XXXXXXXX specifies the name of the component that
HPS2210W
IN COMPONENT XXXXXXXX is invoked at the time the error occurred. Change the input
operation and call the component again.
The input picture string is invalid. XXXXXXXX specifies the
INVALID PICTURE FIELD GIVEN name of the component that is invoked at the time the error
HPS2211W ON INPUT TO COMPONENT occurred. Check the System documentation for valid picture
XXXXXXXX strings with 3270 Converse. Correct the picture string and try
again.
The set name given on input to the specified component does
INVALID NAME OF SET GIVEN ON
not exist. XXXXXXXX specifies the name of the component
HPS2212W INPUT TO COMPONENT
that is invoked at the time the error occurred. Correct the set
XXXXXXXX
name.
The System internal representation of the list box is invalid.
CONVERSE LISTBOX ERROR IN XXXXXXXX specifies the name of the component that is
HPS2213W
PROGRAM XXXXXXXX invoked at the time the error occurred. Contact your System
Administrator.
You have run out of the static storage reserved for
UNABLE TO MODIFY STRING DUE
dynamically modifying picture strings. You are advised to limit
HPS2215W TO LACK OF STORAGE IN
your use of such storage. The problem will be resolved when
XXXXXXXXX
the System Rule is re-initiated.

HPS2215W Enterprise Execution Messages

An attempt is made to modify a picture string, but not enough
UNABLE TO MODIFY STRING DUE
internal System storage is available. XXXXXXXX specifies
HPS2215W TO LACK OF STORAGE IN
the name of the component that is invoked at the time the
XXXXXXXX
error occurred. Contact your System Administrator.
An attempt is made to change a non-numeric picture string.
ONLY NUMERIC PICTURE
The System component CPICSIZ changes only numeric
HPS2216W STRINGS MAY BE MODIFIED BY
picture strings. Do not try to change a non-numeric picture
COMPONENT CPICSIZ
string.
CURSOR POSITION MUST BE Repeated call to system component Get_Selected_Field
HPS2217W
CHANGED ON REPEATED CALL without a change in the position of the cursor.
The text code passed to CFLDMSG or CPNLMSG does not
TEXT CODE NOT FOUND IN match any of the text codes in the specified set. XXXXXXXX
HPS2400E SPECIFIED TABLE IN specifies the name of the component that is invoked at the
COMPONENT XXXXXXXX time the error occurred. Correct the text code or add the text
code to the set.
The position requested for the pop-up item is outside the
available screen area. XXXXXXXX specifies the name of the
INVALID SET POPUP POSITION
HPS2401E component that is invoked at the time the error occurred.
POSITION REQUEST XXXXXXXX
Correct the pop-up position request so it is within the
available screen area.
The System global area HPSCGAP cannot be located. This
HPS24202
UNABLE TO MODIFY HPSCGAP is a System system error, possibly an installation error.
E
INVALID FIELD/VIEW NAME XXXXXXX specifies the name of the component that is
HPS2403E PASSED TO COMPONENT invoked at the time the error occurred. Correct name of field
XXXXXXXX or view and try again.
HPS2404E NO SETS IN RULE SET TABLE,E
SET ,I,8,X, NOT FOUND IN RULE
HPS2405E
SET TABLE* ,E
HPS2406E UNABLE TO LOAD SET ,I,8,E
INVALID SET LOOKUP FUNCTION
HPS2407E
CODE ,A,E
SOURCE VALUE ,I,10,X, FOR SET
HPS2408E
,I,8,X, * NOT FOUND,E
SET LANGUAGE ,I,3,X, NOT
HPS2409E
FOUND IN SET,I* ,8,E
Abend code: H200 The input view passed to the named
component is too small. XXXXXXXX specifies the name of
INPUT VIEW TOO SMALL FOR
HPS2600S the component that is invoked at the time the error occurred.
COMPONENT XXXXXXXX
Save all transaction dumps and contact your System
Administrator.
Abend code: H201 The output view passed to the named
component is too small. XXXXXXXX specifies the name of
OUTPUT VIEW TOO SMALL FOR
HPS2601S the component that is invoked at the time the error occurred.
COMPONENT XXXXXXXX
Save all transaction dumps and contact your System
Administrator.
Abend code: H202 System internal logic error. XXXXXXXX
INVALID ADDRESS FOR HPS
specifies the name of the component that is invoked at the
HPS2602S GLOBAL PARAMETERS IN
time the error occurred. Save all transaction dumps and
COMPONENT XXXXXXXX
INVALID ADDRESS FOR
HPS2603S CONVERSE GLOBAL AREA IN
COMPONENT XXXXXXXX


INVALID ADDRESS FOR
HPS2604S CONVERSE PARAMETER LIST IN
COMPONENT XXXXXXXX
INVALID ADDRESS FOR CVW IN specifies the name of the component that is invoked at the
HPS2605S
COMPONENT XXXXXXXX time the error occurred. Save all transaction dumps and
INVALID ADDRESS FOR
HPS2606S COMPONENT COMMAREA
XXXXXXXX
INVALID ADDRESS FOR specifies the name of the component that is invoked at the
HPS2607S
COMPONENT VIEW XXXXXXXX time the error occurred. Save all transaction dumps and
INVALID ADDRESS FOR
Abend code: H208 System internal logic error. Save all
HPS2608S TERMINAL RELATED STORAGE
AREA
Requested component cannot be executed. XXXXXXXX will
COMPONENT NOT AVAILABLE
HPS2609S be replaced by the system ID of the component which failed.
XXXXXXXX
ABEND H209
The key pressed caused 3270 Converse to take no action
possibly because the action requested is not valid for the
HPS3000I NO ACTION PERFORMED
panel. For example, the menu key has been pressed but
there are no application menu bars to display for this panel.
Abend code: quit (possibly) The Quit key has been pressed.
This message requests confirmation since an abend results
HIT QUIT AGAIN TO QUIT OR from the Quit action and the dialog will terminate. If the
HPS3001I
CLEAR TO CONTINUE intention is to quit (abend) the transaction, press quit again. If
the Quit key is pressed in error, press the Clear key to
redisplay the window and to return to the dialog.
The Prompt key is pressed but the cursor is not positioned on
FIELD NOT FOUND, IS NOT A
HPS3200W a field defined as a cycle field. Reposition the cursor to select
CYCLE FIELD OR IS DISABLED
the correct field and press Prompt again.
A nested (pop-up) window has been displayed, by the use of
a USE RULE xxx NEST statement where rule xxx
converses a window, and the parent rule (or any direct
ancestor) did not also converse a window. Subsequent
NESTED CONVERSE WITH NO
processing may not perform as planned. For example, the
HPS3201W HIGHER LEVEL, WINDOW
Clear key will redisplay only the pop-up window (as there is
RESULTS UNPREDICTABLE
no parent), and any reconverse of a previous window
displays it anew. Check the structure and logic of the rules
within the process being used to verify that they are coded as
intended.
NO MORE HELP TEXT PANELS TO There are no more help text panels to display. Return to the
HPS3400E
BE DISPLAYED previous panel.
HPS3401E HELP IS UNAVAILABLE There is no help text to display. Return to the previous panel.
Abend code: H301 An attribute record is not found in the
3270 Converse file. Verify that the installation of 3270
HPS3601S ATTRIBUTE RECORD NOT FOUND Converse is completed correctly. Verify that the converse
area in the System global area program contains the correct
record signature. Contact your System Administrator.
ATTRIBUTE NAME DOES NOT Abend code: H302 The panel attribute record is not found.
HPS3602S
MATCH Verify that the window preparation is completed successfully.


Abend code: H305 An invalid function request has been
BRANCH CODE NOT DIVISIBLE BY
HPS3605S passed to 3270 Converse. Contact your System
4
Administrator.
Abend code: H307 An incorrect control record is retrieved for
CONTROL NAME DOES NOT
HPS3607S the specified window. Verify that the window preparation
MATCH
completed successfully.
Abend code: H308 The control record for the specified
window is not found in the 3270 Converse file. Verify that the
file is allocated and open. Verify that the installation of 3270
HPS3608S CONTROL RECORD NOT FOUND
Converse is completed correctly. Verify that the converse
area in the System global area program contains the correct
record signature. Contact your System Administrator.
Abend code: H312 A previous bad return code from 3270
INVALID RETURN CODE ON LAST
HPS3612S Converse is not reported by the calling rule. Contact your
CONVERSE
Abend code: H313 An integer (or short int) field does not
FIELD:XXXX INTERNAL LENGTH IS have the correct field length. XXXX specifies the NETLIST
HPS3613S
NOT 2 OR 4 entry number. Verify that the window preparation completed
successfully. Contact your System Administrator.
Abend code: H314 The NETLIST records for the specified
HPS3614S NETLIST RECORD NOT FOUND window were not found in the 3270 Converse file. Verify that
the window preparation completed successfully.
Abend code: H315 Data is entered into an undefined field.
ENTRY FIELD NOT FOUND IN The panel data may be corrupted. Verify that the window
HPS3615S
NETLIST preparation completed successfully. Contact your System
Administrator.
Abend code: H316 An incorrect NETLIST record is retrieved
NETLIST NAME DOES NOT
HPS3616S for the specified window. Verify that the window preparation
MATCH
Abend code: H317 The record containing the window literal
HPS3617S PANEL RECORD NOT FOUND text is not found in the 3270 Converse file. Verify that the
window preparation completed successfully.
The panel record for the specified window is not found in the
HPS3618S PANEL NAME DOES NOT MATCH 3270 Converse file. Verify that the window preparation
STASH PORTION OF CVW <
Abend code: H319 Internal 3270 Converse storage error.
HPS3619S LENGTH RESERVED BY
CONVERSE
START BUFFER CODE NOT Abend code: H320 An invalid data stream is received from
HPS3620S
FOUND CICS. Contact your System Administrator.
Abend code: H322 Data is entered into a text (literal) field.
HPS3622S INPUT FIELD IS TEXT The text field has become unprotected or the screen has
become corrupted. Contact your System Administrator.
Abend code: H323 The field type is not a valid System type
FIELD:XXXX, TYPE IS NOT 1, 2, 3, (CHAR or integer). Your data might be corrupted. XXXX
HPS3623S
4, 5, 7 specifies the NETLIST entry number. Contact your System
Administrator.
Abend code: H324 The panel data contains invalid
characters. XXXX specifies the NETLIST entry number.
HPS3624S FIELD:XXXX IS NON-DISPLAYABLE
Verify that window fields have not been set to non-character
values. Contact your System Administrator.
Abend code: H325 An internal 3270 Converse error that
HPS3625S ENTRY MADE IN VIEW FIELD
indicates corrupt data. Contact your System Administrator.
Abend code: H326 An internal 3270 Converse error. A
HPS3626S VIEW NOT FOUND IN NETLIST required view is not found. Contact your System
Administrator.


Abend code: H327 3270 Converse initialization failed. This
message should never occur as specific conditions are
HPS3627S ERROR IN INIT ONLY CALL
covered by other messages. If it does, contact your System
Administrator.
Abend code: H328 A field in the window has an invalid length.
3270 Converse data may have been corrupted. XXXX
NETLIST FIELD:XXXX LENGTH < =
HPS3628S specifies the NETLIST entry number. Verify that the window
0
preparation completed successfully. Contact your System
Administrator.
Abend code: H330 3270 Converse did not receive a valid
NO PARM LIST PASSED IN parameter list. Verify that the installation of System software
HPS3630S
HPSCVPLA is completed successfully. Contact your System
Administrator.
Abend code: H331 The function record associated with a
FUNCTION CODE RECORD NOT
HPS3631S window is not found. Verify that the window preparation
FOUND
TRASH PORTION OF CVW <
Abend code: H332 An internal 3270 Converse storage error.
HPS3632S LENGTH RESERVED BY
CONVERSE
Abend code: H334 The address of the window input view is
invalid. Verify that the window preparation completed
HPS3634S INPUT VIEW ADDRESS = ZERO
successfully. Verify that the installation of System software is
completed successfully. Contact your System Administrator.
Abend code: H335 The address of the window output view is
invalid. Verify that the window preparation is completed
HPS3635S OUTPUT VIEW ADDRESS = ZERO
successfully. Verify that the installation of System software is
completed successfully. Contact your System Administrator.
Abend code: H336 An invalid function request is passed to
FUNCTION NUMBER REQUESTED 3270 Converse. Verify that the installation of System software
HPS3636S
TOO HIGH is completed successfully. Contact your System
Administrator.
Abend code: H338 3270 Converse data may be corrupted.
FIRST NETLIST ENTRY NOT
HPS3638S Verify that the window preparation is completed successfully.
PANEL DESCRIPTOR
Abend code: H340 The window data containing picture,
PIC - RANGE RECORD NOT range and cycle information is not found in the 3270
HPS3640S
FOUND Converse file. Verify that the window preparation completed
successfully. Contact your local System administrator.
Abend code: H341 An invalid screen address is generated
(XXXXX specifies the address). Ensure that the panel
SBA ADDRESS XXXXX EXCEEDS definition does not define a field that uses the last character
HPS3641S
MAXIMUM position on the bottom row of the screen. Ensure that a
pop-up item has not been moved to make part of the panel
appear off the screen area.
Abend code: H342 An invalid screen address is generated.
HPS3642S SBA ADDRESS LESS THAN 0
Abend code: H344 A packed decimal field has been defined
FIELD:XXXX PACKED DECIMAL
with an invalid length. XXXX specifies the NETLIST entry
HPS3644S LENGTH EXCEEDS MAXIMUM OF
number. Check the definition of the window fields and that the
8
window preparation completed successfully.
Abend code: H345 Data for the support of long names for the
window could not be found in the 3270 Converse file. Verify
LONG NAME RECORD NOT
HPS3645S that the window preparation completed successfully. Verify
FOUND
that the installation of System software completed
successfully.


Abend code: H346 Invalid data for the support of long names
for the window is found in the 3270 Converse file. Verify that
HPS3646S LONG NAME DOES NOT MATCH
the window preparation completed successfully. Verify that
the installation of System software completed successfully.
Abend code: H3CA HPSCNVH is not invoked by HPSCNVA
or there is an internal logic error in HPSCNVA. The task
INVALID COMMAREA ADDRESS
HPS3647S abnormally terminated with a transaction dump. Use the
FOR HPSCNVH
dump to determine how HPSCNVH is invoked, or keep the
dump and contact your System Administrator.
Abend code: H3GA Internal logic error. The task abnormally
INVALID HPSCGAP ADDRESS IN
HPS3648S terminated with a transaction dump. Keep the dump and
HPSCNVH
Abend code: H3ST Panel help or field help exceeds 18 levels
HPS3649S HELP STACK OVERFLOW (panels). You cannot build help panels for a field or a panel
that exceeds 18 levels (panels).
Abend code: H3HA A System user tried to build a help
HELP BUILD VIEW ARRAY
HPS3650S pop-up panel that contained more than 50 help text lines. A
OVERFLOW
help pop-up panel must contain less than 50 help text lines.
Abend code: H351 The in-out view data area is too small to
contain the data specified in the in-out view definition. Check
that the view definition has not been changed between the
HPS3651S INOUT VIEW LENGTH TOO SMALL
window and rule preparations, and prepare both again if
necessary. Contact your System Administrator if the problem
persists or is with a system panel.
Abend code: H352. Processing for an application menu bar
has encountered an unrecoverable situation. The return and
APPLICATION MENU BAR ERROR,
reason codes specify the error condition. Make note of the
HPS3652S RETURN CODE XXXXX REASON
return code and reason code and whether the error is
XXXXX
associated with a menu bar or a pull-down menu from a
menu bar. Then contact your System Administrator.
Abend code: H353 The System communication area and
NO TRSA ADDRESS PASSED TO
HPS3653S other important data areas have not been initialized correctly.
CONVERSE
Abend code: H354 Converse 3270 checks that the data in the
VSAM file is at a supported level for the version installed. An
error has been found when accessing the record with key
XXXXXXXXXXX; the level found on the record is YY. Ensure
UNSUPPORTED FILE LEVEL. that the correct version of 3270 Converse is running. Ensure
HPS3654S KEY=XXXXXXXXXXXXXXXX that any file conversion programs supplied with this release of
LEVEL=YY 3270 Converse have run successfully. Ensure that you have
prepared again any windows the conversion program
reported as not converted. Prepare the window again. If the
problem persists, print all records for the window specified
using IDCAMS and contact your System Administrator.
Abend code: H355 3270 Converse has been asked to write to
a terminal type that is unsupported. XXXXX specifies the
internal type number in the message. If the problem is
UNSUPPORTED TERMINAL TYPE. caused by a workstation-initiated host rule conversing a
HPS3655S
TYPE=XXXX window (type=64), revise the code of the host rule to remove
any 3270 Converse statements and prepare the rule again.
Otherwise, note the terminal type and contact your System
Administrator.
Abend code: H356 The address of the System global area
INVALID GLOBAL AREA ADDRESS
HPS3656S program could not be found. Contact your System
IN THE HPS COMMAREA
Administrator.


Abend code: H357. The address of the constants area could
not be found; this program contains addresses of data 3270
INVALID CONSTANTS AREA Converse requires. Check that the installation of 3270
HPS3657S
ADDRESS IN THE GLOBAL AREA. Converse completed correctly. In particular, check that the
constants area program, HPECNGP, is link-edited with the
global area program, HPEGAPA.
Abend code: H358 The address of the text strings 3270
Converse requires could not be found in the constants area.
INVALID TEXT STRINGS ADDRESS Check that the installation of 3270 Converse completed
HPS3658S
IN THE CONSTANTS AREA correctly. In particular, check that the text string and translate
tables program, HPECV66, is link-edited with the global area
program, HPEGAPA.
OVERFLOW OF THE INTERNAL
which lead up to the abend, and call Customer Service.
HPS3659S DATA STORE. CURRENT SIZE =
XXXXX will be replaced by an internal diagnostic code.
XXXXX
ABEND H359
INVALID INTERNAL FUNCTION which lead up to the abend, and call Customer Service.
HPS3660S
NUMBER = XXXXX XXXXX will be replaced by an internal diagnostic code.
ABEND H360
HPS4000I RULE TEST COMPLETE Indicates that the rule test facility has completed.
HPS4002I PANEL TEST COMPLETE Indicates that the panel test facility has completed.
HPS4003I TRLE PROCESSING COMPLETE Indicates that the rule test facility has completed.
XXXXXXXX HAS BEEN SETUP
Indicates that System in-core tables have been successfully
HPS4004I SUCCESSFULLY WITH TRANSID
updated to set rule XXXXXXXX with TRANSID YYYY.
YYYY
TRANSID EXIT ACTIVATED AND Indicates that the System DFHZCP exit that sets transaction
HPS4005I
STARTED IDs has been successfully activated.
An invalid rule name is passed to System software. Ensure
that the correct rule name is supplied. Prepare the rule again
HPS4400E RULENAME MISMATCH ERROR
and check that all response codes are normal. Contact your
The data passed from the workstation to the host is not
INPUT BLOCK NUMBER
HPS4401E blocked in proper sequential order. This is an internal System
SEQUENCE ERROR
Input or output data length the workstation specified does not
INVALID INPUT/OUTPUT DATA
HPS4402E match the data that is received or sent. Contact your System
LENGTH
Administrator.
The control header passed from the workstation to the host is
INVALID INPUT CONTROL
HPS4403E invalid. This is an internal System error. Contact your System
HEADER ERROR
Administrator.
The view is not found in the System view definition VSAM file.
VIEW RECORD NOT FOUND Make sure System view definition VSAM file is opened and
HPS4404E
ERROR enabled. Prepare the rule that is failing again; ensure all
return codes are normal. Contact your System Administrator.
The input data length does not match the input view length.
This is usually because the view has changed but the rule
INPUT DATA LENGTH DOES NOT
HPS4405E has not been prepared again. Prepare the rule that is failing
MATCH VIEW LENGTH
again and ensure that all return codes are normal. Contact
The System VSAM file is either not open or disabled. Make
VSAM FILE NOT OPEN. RETRY
HPS4406E sure that the System VSAM file is opened and enabled.
REQUEST
ERROR-TABLE CANNOT BE The HPSTBLE1 or HPSTBLE2 in-core table could not be
HPS4407E
FOUND addressed. Contact your System Administrator.

HPS4408E Enterprise Execution Messages

The HPSTBLE2 in-core table is full. Restart the CICS region
ERROR-HPSTBLE2 IS FULL, THE
HPS4408E to build a new HPSTBLE1 table and to refresh the
RULE CANNOT BE SETUP
HPSTBLE2 table.
The input to the UTBL transaction is invalid. The input should
INVALID INPUT-RULE AND/OR be in the form: UTBL, XXXX,YYYYYYYY where XXXX
HPS4409E TRANSID HAS NOT BEEN specifies the TRANSID and YYYYYYYY is the rule name.
ENTERED Input the UTBL transaction again, using the correct
parameters.
System in-core tables could not be loaded. Verify that the
HPS4410E UNABLE TO LOAD TABLES System tables exist, are defined to CICS, and are enabled for
processing.
The HPSGAPA or HPSCGAP global parameter table could
not be loaded. Verify that the HPSCGAP table or the
HPS4411E UNABLE TO LOAD GLOBALS
HPEGAPA table exists, is defined, and enabled for
processing.
The DFHZCP HZCATT exit could not be activated. Have the
HPS4412E UNABLE TO ACTIVATE EXIT CICS systems programmer manually activate the HZCATT
exit using the CECI transaction.
The DFHZCP HZCATT exit could not be started. Have the
HPS4413E UNABLE TO START EXIT CICS systems programmer manually start the HZCATT exit
using the CECI transaction.
The HPSENAEP program could not extract the global work
UNABLE TO PERFORM EXTRACT area address for the DFHZCP HZCATT exit. Check with the
HPS4414E
FOR GWA ADDRESS CICS systems programmer to verify that CICS exits are
activated.
Check with the CICS systems programmer to verify that CICS
HPS4415E GWA LENGTH NOT AS DEFINED
exits are activated.
INVALID INPUT/OUTPUT VIEW An invalid view name is passed to the application interface
HPS4416E
NAME module HPECAPI.
INPUT VIEW NAME OF TARGET
The input view name of the target rule does not match the
HPS4417E RULE DOES NOT MATCH THE
input view name of the calling rule for async.
CALLING RULE
Abend code: H402 The input or output data length is too
large. The maximum data length is 32,255 bytes. Adjust the
INVALID INPUT/OUTPUT DATA
HPS4602S input or output view data length to less than the maximum.
LENGTH ERROR
Prepare all rules that use this view, and ensure that all return
codes are normal.
Abend code: H406 The output data length does not match
the output view length. This is usually because the view has
OUTPUT DATA LENGTH DOES
HPS4606S changed but the rule has not been prepared again. Prepare
NOT MATCH VIEW LENGTH
the rule that is failing, and ensure that all return codes are
normal. Contact your System Administrator.
Abend code: H407 An error occurred when using the CEMT
HPS4607S INQ/SET INTERFACE ERROR command level interface. Save all dumps and contact your
Abend code: H408 An invalid System CICS global parameter
HPSGLBL CONFIGURATION
HPS4608S table is found at the specified address. Save all dumps and
ERROR
Abend code: H409 A TCTUA is not allocated while the
System Environment is running in a development
HPS4609S TCTUA ALLOCATION ERROR
environment. This is an internal System error. Contact your
Abend code: H410 A TWA is not addressable while TWA
HPS4610S TWA ALLOCATION ERROR length from the CICS assign is greater than zero. Save all
dumps and contact your System Administrator.


INPUT CONVERSION BUFFER Abend code: H411 The storage allocated for input view data
HPS4611S OVERFLOW. CONVERSION conversion has been exceeded. Save all dumps and contact
ABORTED your System Administrator.
OUTPUT CONVERSION BUFFER Abend code: H412 The storage allocated for output view data
HPS4612S OVERFLOW. CONVERSION conversion has been exceeded. Save all dumps and contact
ABORTED your System Administrator.
Abend code: H413 Non-numeric data in the output view is
encountered when numeric data is expected. Verify that the
NON NUMERIC DATA ON OUTPUT.
HPS4613S data placed in the output view matches the data types the
NUMERIC DATA EXPECTED
view definition specifies. Contact your System Administrator
for further assistance.
Abend code: H414 The output view is defined with a real
OUTPUT VIEW CONTAINS A REAL
number that is a data type that the output conversion
HPS4614S NUMBER. CONVERSION NOT
program does not support. Remove or redefine the real
DETERMINED
number field.
OUTPUT VIEW CONTAINS A BIT Abend code: H415 The output view is defined with a bit string
HPS4615S STRING. CONVERSION NOT that is a data type the output conversion program does not
DETERMINED support. Remove or redefine the bit string field.
Abend code: H416 Non-numeric data in the input view is
NON NUMERIC DATA RECEIVED. encountered when numeric data is expected. Verify that the
HPS4616S
NUMERIC DATA EXPECTED data placed in the input view matches the data types the view
definition specifies. Contact your System Administrator.
INPUT VIEW CONTAINS A REAL Abend code: H417 The input view is defined with a real
HPS4617S NUMBER. CONVERSION NOT number that is a data type the input conversion program does
DETERMINED not support. Remove or redefine the real number field.
INPUT VIEW CONTAINS A BIT Abend code: H418 The input view is defined with a bit string
HPS4618S STRING. CONVERSION NOT that is a data type the input conversion program does not
DETERMINED support. Remove or redefine the bit string field.
Abend code: H419 An error is encountered when System
TEMP STORAGE READ ERROR
software issued a read from temporary storage during
HPS4619S DURING POST-CANCEL
post-cancel processing. Save all dumps and contact your
PROCESSING
UNABLE TO ISSUE CANCEL Abend code: H420 An error is encountered when System
HPS4620S DURING POST-CANCEL software issued a cancel during post-cancel processing.
PROCESSING Save all dumps and contact your System Administrator.
Abend code: H421 An error is encountered when System
TEMP STORAGE WRITE ERROR
software issued a temporary storage write during post-cancel
HPS4621S DURING POST-CANCEL
processing. Save the dump and contact your System
PROCESSING
Administrator.
Abend code: H422 The specified rule abended with the
specified abend code. Look in the CICS manuals to
RULE XXXXXXXX ABENDED WITH determine the reason for the abend. XXXXXXXX specifies
HPS4622S
YYYY ABEND CODE the name of the rule that abended. YYYY specifies CICS
abend code that the rule abended with. Contact your System
Administrator.
Abend code: H423 The specified rule returned an undefined
ERROR EXPERIENCED WHILE
HPS4623S error return code. XXXXXXXX specifies the name of the rule
EXECUTING RULE XXXXXXXX
in error. Contact your System Administrator.
Abend code: H424 The specified rule requested a service
that has not been installed (such as 3270 Converse).
HPS4624S INSTALLATION ERROR Remove the requested service from the rule source or
contact your System Administrator to install the desired
service.
Abend code: H425 No address to the System task or terminal
NO ADDRESS TO HPSTRSA IN related storage area is found in the AppBuilder system
HPS4625S
HPSCOMM COMMAREA. Save all dumps and contact your System
Administrator.


Abend code: H426 No address to the System terminal control
NO ADDRESS TO HPSTCTUA IN
HPS4626S table user area is found in the System COMMAREA. Save all
HPSCOMM
dumps and contact your System Administrator.
The version indicator within the mainframe to workstation
communications is not valid. Check that the proper version of
INVALID TRANSACTION VERSION:
HPS4627S AppBuilder has been installed on both the mainframe and on
XXXX
the workstation. XXXX will be replaced by the transaction
version that is not valid. ABEND H427
The format indicator within the mainframe to workstation
communications is not valid. Check that the proper version of
UNSUPPORTED TRANSACTION
HPS4628S ApPBuilder has been installed on both the mainframe and on
FORMAT: X
the workstation. X will be replaced by the transaction format
that is not valid. ABEND H428
The view format of the rule on the mainframe does not match
CALCULATED CHECKSUM DOES the view format of the rule on the workstation.
HPS4629S NOT MATCH TRANSACTION Re-synchronize the mainframe and the workstation System
CHECKSUM Rule and prepare the System Rule on both platforms again.
ABEND H429
The transaction type indicator within the mainframe to
workstation communications is not valid. Check that the
HPS4630S proper version of System has been installed on both the
TYPE: X
mainframe and on the workstation. X will be replaced by the
transaction type that is not valid. ABEND H430
The name of the System Rule passed during the mainframe
INVALID USER TRANSACTION
HPS4631S to workstation communications is not in a valid format. Call
FORMAT
Customer Service. ABEND H431.
A transaction code only is entered to initiate an System Rule,
TRANSACTION CODE TO RULE but the transaction code is not in the System Rule lookup
HPS4632S
LOOKUP FAILED table. Insert the System Rule into the System
Transaction-Rule Lookup Table. ABEND H432
The workstation is running in a code page that is not currently
HPS4633S INVALID CODE PAGE supported on the mainframe. Check your System mainframe
installation. ABEND H433
The async sub function must be either a 1 or 0. Anything else
HPS4634S ASYNC SUB FUNCTION IS BLANK
is not valid. ABEND H434
ADDRESS TO ENUMERATED
The address that points to the area to hold the async
HPS4635S OBJECTS AREA FOR ASYNC IS
information is blank. ABEND H435
BLANK
HPS5000I SIGNON COMPLETE Indicates that sign-on is complete.
HPS5001I SIGNOFF COMPLETE Indicates that sign-off is complete.
An error is encountered trying to read from the database.
HPS5400E SQL ERROR
You have not signed on to the external security system. Sign
HPS5401E USER HAS NOT SIGNED ON
on to the external security system.
USER IS NOT AUTHORIZED FOR You are not allowed access to the System environment.
HPS5402E
HPS Contact the data security administrator to acquire access.
The current terminal is not allowed access to the System
TERMINAL IS NOT AUTHORIZED
HPS5403E Environment. Try from another terminal or allow this terminal
FOR HPS
access to the System Environment.
USER/TERMINAL COMBINATION You are not allowed access to this terminal. Try another
HPS5404E
IS NOT AUTHORIZED FOR HPS terminal or obtain access to this terminal.
TERMINAL IS NOT ALLOWED FOR This terminal is not allowed access at this time of day. Try
HPS5405E
THIS TIME OF DAY again some other time or allow access to this terminal.


The maximum number of users has already logged on to the
INCORE HPS LOGON TABLE IS
HPS5406E System Environment. Try signing on to the System
FULL, TRY LATER
Environment later, after some users have signed off.
General access is denied. Further access is denied. Contact
HPS5408E ACCESS DENIED
the data security administrator for access authority.
General function denied. Further user access is denied.
HPS5409E FUNCTION DENIED
Contact the data security administrator for access authority.
HPS5410E GETMAIN FAILED Internal GETMAIN error. Contact your System Administrator.
Internal CICS READ error. Contact your local System
HPS5411E BAD RC FROM CICS READ
Administrator.
COUNTERS IN VIDTEXT Internal VIDTEXT file error. Contact your local System
HPS5412E
CORRUPTED Administrator.
Internal VIDTEXT file error. Contact your local System
HPS5413E AN ITEM IN VIDTEXT IS BLANK
Administrator.
There is no menu generated for any group you selecting
NO MENU DATA FOR THE when signing on, so no menu can be downloaded to the
HPS5414E
GROUPS client. Ask your security administrator to generate menus for
the groups that you belong to.
TOO MANY ITEMS, TOO SMALL
HPS5415E Internal work area error. Contact your System Administrator.
WORK AREA
INVALID START_ITEM IN INPUT
HPS5416E Internal parameter error. Contact your System Administrator.
VIEW
# OF GROUPS INVALID IN INPUT
VIEW
A GROUP IN INPUT VIEW IS
BLANK
Authorization information cannot be downloaded to the client
NO AUTHORIZATION DATA FOR
HPS5419E because it is not defined in the repository. Ask your security
THE GROUPS
administrator to define authorization data.
EXTERNAL SECURITY SIGNON Sign-on failed, possibly because of an incorrect password.
HPS5420E
FAILED Try to sign-on again or contact your security administrator.
HPS5421E PASSWORD EXPIRED Your password expired. Create a new one online.
Your login ID has been suspended, sign-on failed. Contact
HPS5422E LOGINID SUSPENDED
your security administrator.
The format of your new password is invalid. Correct the
HPS5423E INVALID PASSWORD FORMAT
problem and sign-on again.
The in-core rule table cannot be loaded, possibly because
HPS5424E RULE TABLE LOAD FAILURE some loadlibs were not defined in the SYSLIB. Contact your
security administrator or system programmer.
Abend code: HXSE The System external security interface
HPS5600S SECURITY SIGNON EXIT ABEND program abended. Save all dumps and contact your System
Administrator.
INCORRECT SYNCHRONIZATION An invalid synchronization level is requested by the session
HPS6500S LEVEL SPECIFIED FOR THE partner during LU6.2 communications. Contact Customer
CONVERSATION Technical Support. ABEND H650
CONFIRMATION WAS NOT
During LU6.2 communications, the session partner did not
HPS6501S REQUESTED BY THE SESSION
issue a confirm after sending the data packet. ABEND H651.
PARTNER
FREE SESSION WAS REQUESTED The session partner issued an unexpected free session.
HPS6502S
BY THE SESSION PARTNER ABEND H652
ISSUE ERROR CONDITION WAS
The session partner experienced an unexpected error.
HPS6503S RAISED BY THE SESSION
ABEND H653
PARTNER


An error is detected during the confirmation of a send/receive
EIB ERROR CONDITION WAS SET
HPS6504S data packet in a LU6.2 communications protocol. ABEND
BY CICS
H654
A NOTALLOC error condition is raised during LU6.2
NOT ALLOCATED ERROR
communications between the mainframe and workstation.
HPS6505S CONDITION WAS RAISED FOR
XXXXXXXXXX will be replaced by the CICS command which
CICS COMMAND XXXXXXXXXX
caused the NOTALLOC error condition. ABEND H655
A TERMERR error condition is raised during LU6.2
TERMINAL ERROR CONDITION
communications between the mainframe and workstation.
HPS6506S WAS RAISED FOR CICS
XXXXXXXXXX will be replaced by the CICS command which
COMMAND XXXXXXXXXX
caused the TERMERR error condition. ABEND H656
XXXXXXXX HAS BEEN SETUP
HPS7004I SUCCESSFULLY WITH TRANSID The specified rule has been assigned a transaction ID.
YYYYYY
TERMINAL USER EXIT DFSCMTR0
The terminal exit routine has successfully reset the
HPS7039I HAS REFRESHED RULE/TRAN
transaction tables.
TABLES
TERMINAL USER EXIT DFSCMTR0
HPS7040I The terminal exit routine has successfully set the debug flags.
DEBUG FLAGS HAVE BEEN SET
RULE/TRANSACTION
The data in the transaction tables has been written to the
HPS7041I RELATIONSHIP TABLES HAVE
syslog.
BEEN DUMPED
TERMINAL USER EXIT DEBUG The terminal exit routine debug flags have been successfully
HPS7042I
FLAGS HAVE BEEN REMOVED removed.
TERMINAL USER EXIT
The terminal exit routine transaction trace has been
HPS7043I TRANSACTION TRACE HAS BEEN
successfully set.
SET
INVALID DEBUG COMBINATION The terminal exit routine contains an invalid debug
HPS7044I
FOR TERM USER EXIT DFSCMTR0 combination.
HPS/IMS REG XXXXXXXX FOR
HPS7045I RULE XXXXXXXX HAS BEEN The rules processing region has been successfully started.
STARTED
HPS/IMS BATCH RULE XXXXXXXX
HPS7046I The rule has finished processing.
HAS COMPLETED
HPS/IMS REG XXXXXXXX FOR
HPS7047I RULE XXXXXXXX HAS BEEN The rules processing region has been successfully stopped.
STOPPED
HPS BMP PGM XXXXXXXX FOR
HPS7213W RULE XXXXXXXX ALREADY UP, The rules region is already running and so is not started.
REG NOT STARTED
ERROR-HPSTBLE2 IS FULL. RULE
The transaction table is full. The rules transaction ID has not
HPS7408E XXXXXXXX TRAN XXXXXXXX NOT
been set.
SET
IMS RETURN CODE XX FOR
An invalid IMS return code is issued for the FUNCTION
HPS7448E FUNCTION TYPE XXXX ON PCB
TYPE call.
XXXXXXXX
IMS(AIB) RETURN CODE XXXX
An invalid IMS return code is issued for the AIB FUNCTION
HPS7449E FOR FUNCTION TYPE XXXX ON
TYPE call.
PCB XXXXXXXX
A DATABASE IN THE PSB IS
HPS7450E One of these listed databases cannot be found.
UNAVAILABLE
IMS RETURN CODE XX FOR FUNC
Run Control has received a bad return code from an IMS
HPS7451E TYPE XXXX COMMAND
command call.
XXXXXXXXXXXXXXXXXXXXXX


HPS/IMS TXN XXXXXXXX FOR
The rules transaction is currently stopped from a previous
HPS7452E RULE XXXXXXXX STOPPED,
error. Restart transaction and program.
UNABLE TO START REG
SQL ERROR CODE XXXX FOR
HPS7453E An SQL error is encountered in the table.
TABLE XXXXXXXX
HPS/IMS RULE XXXXXXXX
HPS7454E PROGRAM XXXXXXXX NOT The rule has not been properly defined to IMS.
DEFINED TO IMS
RULNAME FILE DOES NOT
HPS7455E The rules name is not in the RULNAME file.
CONTAIN A RULE NAME

CHAPTER
7 ENTERPRISE MESSAGES BY CICS

ABEND CODE
This section describes the CICS abend code execution messages you may encounter when running an
application in an enterprise environment.
Enterprise Messages by Abend

Table 7-1 the enterprise application execution (run-time) messages arranged by CICS abend code.
Table 7-1 CICS Abend Execution Messages
CICS Abend Code Text Description

System internal logic error. XXXXXXXX
specifies the name of the program that
NO COMMAREA PASSED TO issued the call.Keep a note of the
H002 HPS0602S
PROGRAM XXXXXXXX conditions that lead to the error message.
Keep all transaction dumps and contact
specifies the name of the program that
COMMAREA PASSED TO
issued the call.Keep a note of the
H003 HPS0603S PROGRAM XXXXXXXX TOO
conditions that lead to the error message.
SHORT
Lack of sufficient system storage to satisfy
the GETMAIN request. XXXXXXXX
GETMAIN FAILED DUE TO LACK specifies the name of the program that
H004 HPS0604S OF SYSTEM STORAGE IN issued the GETMAIN.Keep a note of the
PROGRAM XXXXXXXX conditions that lead to the error message.
CICS file is disabled at the time System
CICS attempted to access it. XXXXXXXX
FILE XXXXXXXX DISABLED ON
specifies the file name. YYYYYYYY
H005 HPS0605S REQUEST FROM PROGRAM
specifies the name of the program that tried
YYYYYYYY
to access the file.Try to enable the file
using CEMT.

Enterprise Messages by Abend H006
Table 7-1 CICS Abend Execution Messages (Continued)

CICS file is not open at the time System
CICS tried to access it. XXXXXXXX
FILE XXXXXXXX NOT OPEN ON
H006 HPS0606S REQUEST FROM PROGRAM
YYYYYYYY
to access the file.Try to open the file using
CEMT.
File could not be found at the time System
FILE XXXXXXXX NOT FOUND ON attempted to access it. XXXXXXXX
H007 HPS0607S REQUEST FROM PROGRAM specifies the file name. YYYYYYYY
YYYYYYYY specifies the name of the program that tried
to access the file.Define the file properly.
The System CICS user is not authorized
access to the file. XXXXXXXX specifies the
FILE XXXXXXXX NOT
file name. YYYYYYYY specifies the name
H008 HPS0608S AUTHORIZED ON REQUEST
of the program that tried to access the
FROM PROGRAM YYYYYYYY
file.Grant proper access to the user ID
attempting the transaction.
A file I/O error is detected during a read
I/O ERROR READING FROM FILE operation. XXXXXXXX specifies the file
H009 HPS0609S XXXXXXX FROM PROGRAM name. YYYYYYYY will be replaced by the
YYYYYYYY name of the program that tried to access
the file.Correct the I/O error.
Problems were detected when trying to
access the named file. XXXXXXXX
UNABLE TO READ FROM FILE
H010 HPS0610S XXXXXXXX FROM PROGRAM
YYYYYYYY
to access the file.Try to correct the problem
in the file.
The program (YYYYYYYY) is unable to link
to the program (XXXXXXXX). XXXXXXXX
specifies the name of the program we tried
LINK TO PROGRAM XXXXXXXX
H011 HPS0611S to link to. YYYYYYYY specifies the name
FAILED IN PROGRAM YYYYYYYY
of the program that issued the link request.
Make sure all programs are defined
correctly.
The program (YYYYYYYY) is unable to
load the program (XXXXXXXX).
UNABLE TO LOAD PROGRAM XXXXXXXX specifies the name of the
H012 HPS0612S XXXXXXXX IN PROGRAM program we tried to load. YYYYYYYY
YYYYYYYY specifies the name of the program that
issued the load request.Make sure all
programs are defined correctly.
An attempt to initialize a work area for
converse failed. XXXXXXXX specifies the
CVW INITIALIZATION FAILED IN name of the program that issued the call to
H013 HPS0613S
PROGRAM XXXXXXXX 3270 Converse to initialize a work
area.Save all dumps and contact your
An attempt to start a specified transaction
failed. XXXX specifies the name of the
ATTEMPT TO START
H014 HPS0614S transaction.Make sure the specified
TRANSACTION XXXX FAILED
transaction is properly defined.Make sure
the load module is properly defined.
A transaction is requested to start from an
invalid terminal ID. System software tries to
INVALID TERMINAL SPECIFIED,
initiate the transaction unattached to a
H016 HPS0616S TRANS WILL BE INITIATED
terminal. If this fails, the transaction
WITHOUT A TERM
abends.Save all dumps and contact your
7-2 Enterprise Messages by CICS Abend Code

H017 Enterprise Messages by Abend

An internal System request is invalid.Save
INVALID HPS FUNCTION
H017 HPS0617S all dumps and contact your System
SPECIFIED
Administrator.
The execution environment specified for
the rule is invalid.Check the rule to make
INVALID EXECUTION
H018 HPS0618S sure the execution environment is valid. If
ENVIRONMENT
so, save all dumps and contact your
An internal error is detected with 3270
NON ZERO RETURN CODE
H019 HPS0619S Converse.Save all dumps and contact your
FROM HPS CONVERSE
An error occurred in CICS post-cancel
ERROR OCCURRED DURING processing internal to System
H020 HPS0620S
POST-CANCEL PROCESSING software.Save all dumps and contact your
An error occurred trying to issue a send or
TERMINAL ERROR ON SEND/ a receive from the terminal device.Save all
H021 HPS0621S
RECEIVE dumps and contact your System
Administrator.
An error occurred when an internal System
process issued a read from the specified
temporary storage queue. XXXXXXXX
ERROR ON READQ TS FROM specifies the name of the temporary
H022 HPS0622S
QUEUE XXXXXXXX storage queue that System software tried
to read from.Check the status of the
specified temporary storage queue, and
then contact your System Administrator.
process issued a write from the specified
temporary storage queue. XXXXXXXX
ERROR ON WRITEQ TS FROM specifies the name of the temporary
H023 HPS0623S
QUEUE XXXXXXXX storage queue that System software tried
to write to.Check the status of the specified
temporary storage queue, and then contact
process tried to access the 3270 Converse
global area. Verify that the HPEGAPA load
UNABLE TO LOCATE THE module that consists of the System global
H024 HPS0624S
CONVERSE GLOBAL AREA parameters is not corrupted. Verify that the
HPECVGP CSECT is included in the
HPEGAPA load module. Save all dumps
An invalid FREEMAIN we issued within
INVALID FREEMAIN OCCURRED The System XXXXXXXX will be replaced
H028 HPS0628S
IN PROGRAM XXXXXXXX by the name of the program which issued
the invalid FREEMAIN.
An attempt to initiate a System rule through
H029 HPS0629S RULE NOT FOUND: XXXXXXXX
RuleView failed.
H030 HPS0630S QUEUE NOT AVAILABLE Temporary storage queue is not available.
Temporary storage queue is being used by
H031 HPS0631S QUEUE IS BUSY
another task.
An attempt to delete a record failed.
FFFFFFFF will be replaced by the name of
I/O ERROR DELETING FROM
the file we are trying to delete from.
H031 HPS0634S FILE FFFFFFFF FROM
PPPPPPPP will be replaced by the name
PROGRAM PPPPPPPP
of the program which tried to delete the
record.


An attempt to write a record failed.
FFFFFFFF will be replaced by the name of
I/O ERROR WRITING TO FILE
the file we are trying to write to.
H035 HPS0635S FFFFFFFF FROM PROGRAM
PPPPPPPP will be replaced by the name
PPPPPPPP
of the program which tried to write the
record.
ASYNC-SUPPORT-ACTIVE FLAG Async flag to indicate async is active has
H036 HPS0636S
NOT SET not been set.
INVALID CARRIAGE CNTL The carriage control used to control printing
H037 HPS0637S
CHARACTER is not valid.
H038 HPS0638S PRINTER OUT OF SERVICE Printer is out of service.
TRANSACTION XXXX ABENDED, An AppBuilder rule has abended in the
H039 HPS0639S
HIT CLEAR SCREEN CICS environment.
Internal System error. Keep all dumps, note
ERROR CALLING SYSTEM the conditions which led to the abend, and
H050 HPS0650S STORAGE MANAGER call Customer Technical Support.
XXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXX will be
replaced by System internal diagnostics.
ERROR CALLING HPS STORAGE the conditions which lead up to the abend,
H051 HPS0651S MANAGER and call Customer Service.
XXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXX will be
replaced by System internal diagnostics.
AN ABEND HAS OCCURRED AND
An AppBuilder rule has abended in the IMS
H054 HPS0654S TRANSACTION HAS BEEN
environment.
TERMINATED
System module executed a CICS
command that raised an error condition.
XXXXYY specifies the code (XXXX=EIBFN
EXEC CICS COMMAND ERROR YY=EIBRESP).The task abnormally
H0CEA HPS0600S
CODE=XXXXYY terminated with a transaction dump. Use
the dump to determine why the failure
occurred, or keep the dump and contact
You tried to invoke a System transaction on
INVALID DEVICE TYPE a terminal device System software does
H0ID HPS0700S
DEVICE=XXXX not support. The terminal must be a
3270type device.
An invalid request condition is raised when
INVALID REQUEST ERROR executing the CICS command
H0IR HPS0625S OCCURRED FOR CICS XXXXXXXXXX. XXXXXXXXXX specifies
COMMAND XXXXXXXXXX the command. Save all dumps and contact
System software does not support the
INVALID SCREEN SIZE screen size definition for the device. The
H0IS HPS0701S
HEIGHT=XX WIDTH=XXX screen size for the terminal must be
specified as 24 x 80.
An invalid length condition is raised when
INVALID LENGTH ERROR executing the CICS command
H0LE HPS0626S OCCURRED FOR CICS XXXXXXXXXX. XXXXXXXXXX specifies
COMMAND XXXXXXXXXX the command. Save all dumps and contact

H0NU Enterprise Messages by Abend

An authorization error condition is raised
when executing the CICS command
XXXXXXXXXX. XXXXXXXXXX specifies
AUTHORIZATION ERROR
the command. Check external security
H0NU HPS0627S OCCURRED FOR CICS
audit logs for the resource that is accessed.
COMMAND XXXXXXXXXX
Grant the appropriate security access, if
possible. Save all dumps and contact your
EXEC CICS READ FAILURE System CICS internal logic error. The task
RECORD abnormally terminated with a transaction
H0RE HPS0601S
KEY=XXXXXXXXXXXXXXXXXXX dump. Keep the dump and contact your
X System Administrator.
An invalid COMMAREA is passed to an
internal System module. XXXXXXXX
INVALID COMMAREA IN
H1CM HPS1661S specifies the name of the program that
XXXXXXXX
issued this message. Keep all dumps and
A System user tried to build a function
FUNCTION MENU VIEW ARRAY menu (the master menu) that contained
H1FA HPS1607S
OVERFLOW more than 99 selections. A function menu
must contain less than 99 selections.
A System user tried to build a menu bar
MENU-BAR BUILD VIEW ARRAY that contained more than 38 menu bar
H1MA HPS1603S
OVERFLOW selections. A screen must contain less than
38 menu bar selections.
A user tried to build a menu bar screen that
contained more than the screen height
minus 11 lines of menu bar selections.
Example: a screen size 24 by 80 cannot
H1MB HPS1601S MENU-BAR BUILD OVERFLOW
have more than 13 lines of menu bar
selections. A menu bar screen must
contain less than the screen height minus
11 lines of menu bar selections.
A System user tried to build a pull-down
(pop-up) menu that contained more than 99
POP-UP BUILD VIEW ARRAY
H1PA HPS1604S pull-down (pop-up) selections. A pull-down
OVERFLOW
(pop-up) menu must contain less than 99
pull-down (pop-up) selections.
A System users process exceeded 18
menu bar levels. Note: A menu bar level is
each menu bar that is displayed within a
H1ST HPS1602S MENU-BAR STACK OVERFLOW
specific process that is selected from the
first menu bar screen. A process cannot
exceed 18 menu bar levels.
The input view passed to the named
component is too small. XXXXXXXX
INPUT VIEW TOO SMALL FOR specifies the name of the component that is
H200 HPS2600S
COMPONENT XXXXXXXX invoked at the time the error occurred.
Save all transaction dumps and contact
The output view passed to the named
component is too small. XXXXXXXX
OUTPUT VIEW TOO SMALL FOR specifies the name of the component that is
H201 HPS2601S
COMPONENT XXXXXXXX invoked at the time the error occurred.


INVALID ADDRESS FOR HPS specifies the name of the component that is
H202 HPS2602S GLOBAL PARAMETERS IN invoked at the time the error occurred.
COMPONENT XXXXXXXX Save all transaction dumps and contact
INVALID ADDRESS FOR specifies the name of the component that is
H203 HPS2603S CONVERSE GLOBAL AREA IN invoked at the time the error occurred.
H204 HPS2604S CONVERSE PARAMETER LIST IN invoked at the time the error occurred.
specifies the name of the component that is
INVALID ADDRESS FOR CVW IN
H205 HPS2605S invoked at the time the error occurred.
COMPONENT XXXXXXXX
H206 HPS2606S COMPONENT COMMAREA invoked at the time the error occurred.
XXXXXXXX Save all transaction dumps and contact
specifies the name of the component that is
INVALID ADDRESS FOR
H207 HPS2607S invoked at the time the error occurred.
COMPONENT VIEW XXXXXXXX
INVALID ADDRESS FOR System internal logic error. Save all
H208 HPS2608S TERMINAL RELATED STORAGE transaction dumps and contact your
AREA System Administrator.
Requested component cannot be
COMPONENT NOT AVAILABLE executed. XXXXXXXX will be replaced by
H209 HPS2609S
XXXXXXXX the system ID of the component which
failed.
An attribute record is not found in the 3270
Converse file. Verify that the installation of
3270 Converse is completed correctly.
ATTRIBUTE RECORD NOT
H301 HPS3601S Verify that the converse area in the System
FOUND
global area program contains the correct
record signature. Contact your System
Administrator.
The panel attribute record is not found.
ATTRIBUTE NAME DOES NOT
H302 HPS3602S Verify that the window preparation is
MATCH
An invalid function request has been
BRANCH CODE NOT DIVISIBLE
H305 HPS3605S passed to 3270 Converse. Contact your
BY 4
An incorrect control record is retrieved for
CONTROL NAME DOES NOT the specified window. Verify that the
H307 HPS3607S
MATCH window preparation completed
successfully.


The control record for the specified window
is not found in the 3270 Converse file.
Verify that the file is allocated and open.
Verify that the installation of 3270 Converse
H308 HPS3608S CONTROL RECORD NOT FOUND is completed correctly. Verify that the
converse area in the System global area
program contains the correct record
signature. Contact your System
Administrator.
A previous bad return code from 3270
INVALID RETURN CODE ON
H312 HPS3612S Converse is not reported by the calling rule.
LAST CONVERSE
An integer (or short int) field does not have
the correct field length. XXXX specifies the
FIELD:XXXX INTERNAL LENGTH NETLIST entry number. Verify that the
H313 HPS3613S
IS NOT 2 OR 4 window preparation completed
successfully. Contact your System
Administrator.
The NETLIST records for the specified
window were not found in the 3270
H314 HPS3614S NETLIST RECORD NOT FOUND
Converse file. Verify that the window
preparation completed successfully.
Data is entered into an undefined field.
The panel data may be corrupted. Verify
ENTRY FIELD NOT FOUND IN
H315 HPS3615S that the window preparation completed
NETLIST
Administrator.
An incorrect NETLIST record is retrieved
NETLIST NAME DOES NOT for the specified window. Verify that the
H316 HPS3616S
MATCH window preparation completed
successfully.
The record containing the window literal
text is not found in the 3270 Converse file.
H317 HPS3617S PANEL RECORD NOT FOUND
Verify that the window preparation
STASH PORTION OF CVW <
Internal 3270 Converse storage error.
H319 HPS3619S LENGTH RESERVED BY
CONVERSE
START BUFFER CODE NOT An invalid data stream is received from
H320 HPS3620S
FOUND CICS. Contact your System Administrator.
Data is entered into a text (literal) field. The
text field has become unprotected or the
H322 HPS3622S INPUT FIELD IS TEXT
screen has become corrupted. Contact
The field type is not a valid System type
(CHAR or integer). Your data might be
FIELD:XXXX, TYPE IS NOT 1, 2, 3,
H323 HPS3623S corrupted. XXXX specifies the NETLIST
4, 5, 7
entry number. Contact your System
Administrator.
The panel data contains invalid characters.
XXXX specifies the NETLIST entry
FIELD:XXXX IS NON-
H324 HPS3624S number. Verify that window fields have not
DISPLAYABLE
been set to non-character values. Contact
An internal 3270 Converse error that
H325 HPS3625S ENTRY MADE IN VIEW FIELD indicates corrupt data. Contact your


An internal 3270 Converse error. A
H326 HPS3626S VIEW NOT FOUND IN NETLIST required view is not found. Contact your
3270 Converse initialization failed. This
message should never occur as specific
H327 HPS3627S ERROR IN INIT ONLY CALL conditions are covered by other messages.
If it does, contact your System
Administrator.
A field in the window has an invalid length.
3270 Converse data may have been
NETLIST FIELD:XXXX LENGTH < corrupted. XXXX specifies the NETLIST
H328 HPS3628S
=0 entry number. Verify that the window
3270 Converse did not receive a valid
NO PARM LIST PASSED IN parameter list. Verify that the installation of
H330 HPS3630S
HPSCVPLA System software is completed successfully.
The function record associated with a
FUNCTION CODE RECORD NOT
H331 HPS3631S window is not found. Verify that the window
FOUND
TRASH PORTION OF CVW <
An internal 3270 Converse storage error.
H332 HPS3632S LENGTH RESERVED BY
CONVERSE
The address of the window input view is
invalid. Verify that the window preparation
completed successfully. Verify that the
H334 HPS3634S INPUT VIEW ADDRESS = ZERO
installation of System software is
completed successfully. Contact your
The address of the window output view is
invalid. Verify that the window preparation
OUTPUT VIEW ADDRESS = is completed successfully. Verify that the
H335 HPS3635S
ZERO installation of System software is
completed successfully. Contact your
An invalid function request is passed to
3270 Converse. Verify that the installation
FUNCTION NUMBER
H336 HPS3636S of System software is completed
REQUESTED TOO HIGH
Administrator.
3270 Converse data may be corrupted.
FIRST NETLIST ENTRY NOT Verify that the window preparation is
H338 HPS3638S
PANEL DESCRIPTOR completed successfully. Contact your
The window data containing picture, range
and cycle information is not found in the
PIC - RANGE RECORD NOT
H340 HPS3640S 3270 Converse file. Verify that the window
FOUND
Contact your local System administrator.
An invalid screen address is generated
(XXXXX specifies the address). Ensure
that the panel definition does not define a
SBA ADDRESS XXXXX EXCEEDS field that uses the last character position on
H341 HPS3641S
MAXIMUM the bottom row of the screen. Ensure that a
popup item has not been moved to make
part of the panel appear off the screen
area.


An invalid screen address is generated.
H342 HPS3642S SBA ADDRESS LESS THAN 0
A packed decimal field has been defined
with an invalid length. XXXX specifies the
FIELD:XXXX PACKED DECIMAL
NETLIST entry number. Check the
H344 HPS3644S LENGTH EXCEEDS MAXIMUM OF
definition of the window fields and that the
8
window preparation completed
successfully.
Data for the support of long names for the
window could not be found in the 3270
LONG NAME RECORD NOT Converse file. Verify that the window
H345 HPS3645S
FOUND preparation completed successfully. Verify
that the installation of System software
Invalid data for the support of long names
for the window is found in the 3270
Converse file. Verify that the window
H346 HPS3646S LONG NAME DOES NOT MATCH
preparation completed successfully. Verify
that the installation of System software
The in-out view data area is too small to
contain the data specified in the in-out view
definition. Check that the view definition
INOUT VIEW LENGTH TOO has not been changed between the window
H351 HPS3651S
SMALL and rule preparations, and prepare both
again if necessary. Contact your System
Administrator if the problem persists or is
with a system panel.
Processing for an application menu bar has
encountered an unrecoverable situation.
The return and reason codes specify the
APPLICATION MENU BAR
error condition. Make note of the return
H352 HPS3652S ERROR, RETURN CODE XXXXX
code and reason code and whether the
REASON XXXXX
error is associated with a menu bar or a
pull-down menu from a menu bar. Then
The System communication area and other
NO TRSA ADDRESS PASSED TO important data areas have not been
H353 HPS3653S
CONVERSE initialized correctly. Contact your System
Administrator.
Converse 3270 checks that the data in the
VSAM file is at a supported level for the
version installed. An error has been found
when accessing the record with key
XXXXXXXXXXX; the level found on the
record is YY. Ensure that the correct
version of 3270 Converse is running.
UNSUPPORTED FILE LEVEL.
Ensure that any file conversion programs
H354 HPS3654S KEY=XXXXXXXXXXXXXXXX
supplied with this release of 3270
LEVEL=YY
Converse have run successfully. Ensure
that you have prepared again any windows
the conversion program reported as not
converted. Prepare the window again. If the
problem persists, print all records for the
window specified using IDCAMS and


3270 Converse has been asked to write to
a terminal type that is unsupported. XXXXX
specifies the internal type number in the
message. If the problem is caused by a
UNSUPPORTED TERMINAL workstation-initiated host rule conversing a
H355 HPS3655S
TYPE. TYPE=XXXX window (type=64), revise the code of the
host rule to remove any 3270 Converse
statements and prepare the rule again.
Otherwise, note the terminal type and
INVALID GLOBAL AREA The address of the System global area
H356 HPS3656S ADDRESS IN THE HPS program could not be found. Contact your
COMMAREA System Administrator.
The address of the constants area could
not be found; this program contains
addresses of data 3270 Converse requires.
INVALID CONSTANTS AREA
Check that the installation of 3270
H357 HPS3657S ADDRESS IN THE GLOBAL
Converse completed correctly. In particular,
AREA.
check that the constants area program,
HPECNGP, is link-edited with the global
area program, HPEGAPA.
The address of the text strings 3270
Converse requires could not be found in
the constants area. Check that the
INVALID TEXT STRINGS
installation of 3270 Converse completed
H358 HPS3658S ADDRESS IN THE CONSTANTS
correctly. In particular, check that the text
AREA
string and translate tables program,
HPECV66, is link-edited with the global
area program, HPEGAPA.
OVERFLOW OF THE INTERNAL
the conditions which lead up to the abend,
H359 HPS3659S DATA STORE. CURRENT SIZE =
and call Customer Service. XXXXX will be
XXXXX
replaced by an internal diagnostic code.
INVALID INTERNAL FUNCTION the conditions which lead up to the abend,
H360 HPS3660S
NUMBER = XXXXX and call Customer Service. XXXXX will be
replaced by an internal diagnostic code.
HPSCNVH is not invoked by HPSCNVA or
there is an internal logic error in HPSCNVA.
The task abnormally terminated with a
INVALID COMMAREA ADDRESS
H3CA HPS3647S transaction dump. Use the dump to
FOR HPSCNVH
determine how HPSCNVH is invoked, or
keep the dump and contact your System
Administrator.
Internal logic error. The task abnormally
INVALID HPSCGAP ADDRESS IN terminated with a transaction dump. Keep
H3GA HPS3648S
HPSCNVH the dump and contact your System
Administrator.
A System user tried to build a help popup
HELP BUILD VIEW ARRAY panel that contained more than 50 help text
H3HA HPS3650S
OVERFLOW lines. A help popup panel must contain less
than 50 help text lines.
Panel help or field help exceeds 18 levels
(panels). You cannot build help panels for a
H3ST HPS3649S HELP STACK OVERFLOW
field or a panel that exceeds 18 levels
(panels).


The input or output data length is too large.
The maximum data length is 32,255 bytes.
INVALID INPUT/OUTPUT DATA Adjust the input or output view data length
H402 HPS4602S
LENGTH ERROR to less than the maximum. Prepare all rules
that use this view, and ensure that all return
codes are normal.
The output data length does not match the
output view length. This is usually because
the view has changed but the rule has not
OUTPUT DATA LENGTH DOES
H406 HPS4606S been prepared again. Prepare the rule that
NOT MATCH VIEW LENGTH
is failing, and ensure that all return codes
are normal. Contact your System
Administrator.
An error occurred when using the CEMT
H407 HPS4607S INQ/SET INTERFACE ERROR command level interface. Save all dumps
An invalid System CICS global parameter
HPSGLBL CONFIGURATION table is found at the specified address.
H408 HPS4608S
ERROR Save all dumps and contact your System
Administrator.
A TCTUA is not allocated while the System
Environment is running in a development
H409 HPS4609S TCTUA ALLOCATION ERROR
environment. This is an internal System
A TWA is not addressable while TWA
length from the CICS assign is greater than
H410 HPS4610S TWA ALLOCATION ERROR
zero. Save all dumps and contact your
The storage allocated for input view data
INPUT CONVERSION BUFFER
conversion has been exceeded. Save all
H411 HPS4611S OVERFLOW. CONVERSION
dumps and contact your System
ABORTED
Administrator.
The storage allocated for output view data
OUTPUT CONVERSION BUFFER
conversion has been exceeded. Save all
H412 HPS4612S OVERFLOW. CONVERSION
ABORTED
Administrator.
Nonnumeric data in the output view is
encountered when numeric data is
NON NUMERIC DATA ON expected. Verify that the data placed in the
H413 HPS4613S OUTPUT. NUMERIC DATA output view matches the data types the
EXPECTED view definition specifies. Contact your
System Administrator for further
assistance.
The output view is defined with a real
OUTPUT VIEW CONTAINS A
number that is a data type that the output
H414 HPS4614S REAL NUMBER. CONVERSION
conversion program does not support.
NOT DETERMINED
Remove or redefine the real number field.
The output view is defined with a bit string
OUTPUT VIEW CONTAINS A BIT
that is a data type the output conversion
H415 HPS4615S STRING. CONVERSION NOT
program does not support. Remove or
DETERMINED
redefine the bit string field.
Nonnumeric data in the input view is
encountered when numeric data is
NON NUMERIC DATA RECEIVED. expected. Verify that the data placed in the
H416 HPS4616S
NUMERIC DATA EXPECTED input view matches the data types the view
definition specifies. Contact your System
Administrator.


The input view is defined with a real
INPUT VIEW CONTAINS A REAL
number that is a data type the input
H417 HPS4617S NUMBER. CONVERSION NOT
conversion program does not support.
DETERMINED
Remove or redefine the real number field.
The input view is defined with a bit string
INPUT VIEW CONTAINS A BIT
that is a data type the input conversion
H418 HPS4618S STRING. CONVERSION NOT
program does not support. Remove or
DETERMINED
redefine the bit string field.
An error is encountered when System
TEMP STORAGE READ ERROR software issued a read from temporary
H419 HPS4619S DURING POST-CANCEL storage during post-cancel processing.
PROCESSING Save all dumps and contact your System
Administrator.
UNABLE TO ISSUE CANCEL
software issued a cancel during
H420 HPS4620S DURING POST-CANCEL
post-cancel processing. Save all dumps
PROCESSING
TEMP STORAGE WRITE ERROR software issued a temporary storage write
H421 HPS4621S DURING POST-CANCEL during post-cancel processing. Save the
PROCESSING dump and contact your System
Administrator.
The specified rule abended with the
specified abend code. Look in the CICS
manuals to determine the reason for the
RULE XXXXXXXX ABENDED
H422 HPS4622S abend. XXXXXXXX specifies the name of
WITH YYYY ABEND CODE
the rule that abended. YYYY specifies
CICS abend code that the rule abended
with. Contact your System Administrator.
The specified rule returned an undefined
ERROR EXPERIENCED WHILE error return code. XXXXXXXX specifies the
H423 HPS4623S
EXECUTING RULE XXXXXXXX name of the rule in error. Contact your
The specified rule requested a service that
has not been installed (such as 3270
Converse). Remove the requested service
H424 HPS4624S INSTALLATION ERROR
from the rule source or contact your
System Administrator to install the desired
service.
No address to the System task or terminal
related storage area is found in the
NO ADDRESS TO HPSTRSA IN
H425 HPS4625S AppBuilder system COMMAREA. Save all
HPSCOMM
Administrator.
No address to the System terminal control
NO ADDRESS TO HPSTCTUA IN table user area is found in the System
H426 HPS4626S
HPSCOMM COMMAREA. Save all dumps and contact
The version indicator within the mainframe
to workstation communications is not valid.
Check that the proper version of
INVALID TRANSACTION
H427 HPS4627S AppBuilder has been installed on both the
VERSION: XXXX
mainframe and on the workstation. XXXX
will be replaced by the transaction version
that is not valid.


The format indicator within the mainframe
to workstation communications is not valid.
Check that the proper version of
H428 HPS4628S AppBuilder has been installed on both the
FORMAT: X
mainframe and on the workstation. X will
be replaced by the transaction format that
is not valid.
The view format of the rule on the
mainframe does not match the view format
CALCULATED CHECKSUM DOES
of the rule on the workstation.
H429 HPS4629S NOT MATCH TRANSACTION
Re-synchronize the mainframe and the
CHECKSUM
workstation System Rule and prepare the
System Rule on both platforms again.
The transaction type indicator within the
mainframe to workstation communications
is not valid. Check that the proper version
H430 HPS4630S of System has been installed on both the
TYPE: X
mainframe and on the workstation. X will
be replaced by the transaction type that is
not valid.
The name of the System Rule passed
INVALID USER TRANSACTION during the mainframe to workstation
H431 HPS4631S
FORMAT communications is not in a valid format.
Call Customer Service.
A transaction code only is entered to
initiate an System Rule, but the transaction
TRANSACTION CODE TO RULE
H432 HPS4632S code is not in the System Rule lookup
LOOKUP FAILED
table. Insert the System Rule into the
System Transaction Rule Lookup Table.
The workstation is running in a code page
that is not currently supported on the
H433 HPS4633S INVALID CODE PAGE
mainframe. Check your System mainframe
installation.
ASYNC SUB FUNCTION IS The async sub function must be either a 1
H434 HPS4634S
BLANK or 0. Anything else is not valid.
ADDRESS TO ENUMERATED
The address that points to the area to hold
H435 HPS4635S OBJECTS AREA FOR ASYNC IS
the async information is blank.
BLANK
An invalid synchronization level is
INCORRECT SYNCHRONIZATION
requested by the session partner during
H650 HPS6500S LEVEL SPECIFIED FOR THE
LU6.2 communications. Contact Customer
CONVERSATION
Technical Support.
CONFIRMATION WAS NOT During LU6.2 communications, the session
H651 HPS6501S REQUESTED BY THE SESSION partner did not issue a confirm after
PARTNER sending the data packet.
FREE SESSION WAS
The session partner issued an unexpected
H652 HPS6502S REQUESTED BY THE SESSION
free session.
PARTNER
ISSUE ERROR CONDITION WAS
The session partner experienced an
H653 HPS6503S RAISED BY THE SESSION
unexpected error.
PARTNER
An error is detected during the confirmation
EIB ERROR CONDITION WAS
H654 HPS6504S of a send/receive data packet in a LU6.2
SET BY CICS
communications protocol.


A NOTALLOC error condition is raised
during LU6.2 communications between the
NOT ALLOCATED ERROR
mainframe and workstation.
H655 HPS6505S CONDITION WAS RAISED FOR
XXXXXXXXXX will be replaced by the
CICS COMMAND XXXXXXXXXX
CICS command which caused the
NOTALLOC error condition.
A TERMERR error condition is raised
during LU6.2 communications between the
TERMINAL ERROR CONDITION
mainframe and workstation.
H656 HPS6506S WAS RAISED FOR CICS
XXXXXXXXXX will be replaced by the
COMMAND XXXXXXXXXX
CICS command which caused the
TERMERR error condition.

CHAPTER
8 TRACE FILE EXAMPLE
AppBuilder writes information in the DNA.INI file about programs that are executing to the file
specified in the [TRACING] TRCFILE variable. Variables in the [TRACING] section let you control the
type of information logged. This section describes the format of the trace file for full tracing, that is,
when the [TRACING] DEBUGLVL variable is set to ERRORS_AND_TRACES (or 3). Trace output for
the mainframe goes to C/370 standard output.
This topic includes:

Trace File Format a description of the trace file entries
Sample 1: A Successful Call a sample trace file for a successful API call
Sample 2: An Unsuccessful Call a sample trace file for an unsuccessful API call
Trace File Format

For successful calls, AppBuilder logs when the call started and stopped executing; input/output view
lengths, if the call processes input or output; and a hex dump, if a network call was made in the course of
processing. For unsuccessful calls, it also logs errors and status view data. On the client side, for calls to
dna_ServiceRequest or dna_DynamicRequest, AppBuilder communications logs when the bound
versions of these functions started and stopped executing; the bound versions are used internally.
Entry Format
The entry format is as follows with each field described in:
DNA 2 INFO Entered Routine dna_InitClient.
96-06-25 15:01:35.687 add PID= 10741 426:267:2
Table 8-1 Entry Format Contents
Field Number Contents Description

Message ID. This field contains the product code, optional message number, and message
1 category. For example, in DNA 2 INFO, DNA refers to the product (AppBuilder communications),
2 is the message number, and INFO is the message category.
2 Message text, input/output view length, or status view item.
3 Date.
4 Time.
Client ID. On the client side, this field contains the character string given in the first argument to
5
dna_InitClient. On the server side, this field contains the name of the server, consrv.exe.
6 Process ID or thread ID.
7 For internal use.

Sample 1: A Successful Call For internal use.
Status View Entries

Status view entries correspond to items in the AppBuilder communications status view and have the
form:
DNA --- DEBUG : DNA - Target Server -----------> dnamsg
96-06-25 15:00:28.904 add PID= 10733
The fields are the same as those described above, except that Field 2 describes the target server item in
the status view. The type definition of the status view appears in dna.h. Items in the status view are as
follows:
User ID (equivalent to loginName given in authentication exit)
Workstation ID (equivalent to DNA.INI [DNA] Workstation_ID)
Transaction ID (system-generated)
Name (or system ID) of service to be invoked (possibly specified in source of routing information)
Host name of target machine (specified in source of routing information)
Server ID of target server (specified in source of routing information)
Protocol (specified in source of routing information)
Type of error (repeated from error message)
Error code (repeated from error message)
Protocol error code
Where to Locate Error Messages for Asynchronous Programs

Global eventing and non-connection-oriented messaging are asynchronous programming techniques;
they do not provide robust reporting of errors accessing remote hosts. If, for example, your program
references a binding to a nonexistent host, you are not notified of the failure in the sending programs
trace file, only in the local AppBuilder communications agents trace file. For messaging, you can have
the receiving program send an autoreply with no data to acknowledge message receipt. If you do not
receive acknowledgment, you know that some kind of error occurred.
Sample 1: A Successful Call

On the client side, a trace of a successful API call will look like this when
[TRACING] DEBUGLVL is set to 3:
DNA 2 INFO Entered Routine
dna_InitClient.
96-06-05 10:15:21.088 add PID= 16601 426:267:2
DNA 3 INFO Exiting Routine
dna_InitClient.
96-06-05 10:15:21.093 add PID= 16601 426:495:2
96-06-25 15:01:35.687 add PID= 10741 426:267:2
DNA 3 INFO Exiting Routine dna_InitClient.
96-06-25 15:01:35.692 add PID= 10741 426:495:2
DNA 2 INFO Entered Routine dna_StartTxn.
96-06-25 15:01:35.704 add PID= 10741 426:1464:2
8-2 Trace File Example

For internal use. Sample 1: A Successful Call
DNA 3 INFO Exiting Routine dna_StartTxn.

96-06-25 15:01:35.705 add PID= 10741 426:1505:2
DNA 2 INFO Entered Routine dna_ServiceRequest.
96-06-25 15:01:35.718 add PID= 10741 426:731:2
DNA 2 INFO Entered Routine dna_BoundServiceRequest - Service ADD.
96-06-25 15:01:35.719 add PID= 10741 426:545:2
DNA --- DEBUG : DNA - Input Data Length --------> 4
96-06-25 15:01:35.721 add PID= 10741
DNA --- DEBUG : DNA - Input Data --------------->
96-06-25 15:01:35.721 add PID= 10741
0000 00010003 *.... *
DNA --- DEBUG : DNA - Network Output Line Trace:
96-06-25 15:01:35.903 add PID= 10741
0000 646E616D 73672020 20303030 30303030 30303434 *dnamsg 00000000044*
0014 444E4143 4F4D4D53 41444420 20202020 00080001 *DNACOMMSADD ....*
0028 5D5E1D69 00010001 000000E8 20222006 00000000 *]^.i........ " .....*
003C 00000180 00000000 00000000 00000000 00000000 *....................*
0050 00000000 00000000 00000000 00000000 00000000 *....................*
0064 61646400 00000000 00000000 00000000 00000000 *add.................*
0078 00000000 00000000 00000000 00000000 00000000 *....................*
008C 00000001 00000000 00000181 00000000 41444400 *................ADD.*
00A0 00000000 00000000 00000000 00000000 00000000 *....................*
00B4 00000000 00000000 00000000 00000000 00000002 *....................*
00C8 00000003 00000004 00010001 00000000 00000002 *....................*
00DC 00030001 00010000 00000002 00030001 00010000 *....................*
00F0 00000001 00000003 00000002 00000002 00000002 *....................*
0104 00010001 00000000 00000002 00030001 00010000 *....................*
DNA --- DEBUG : DNA - Network Input Line Trace:
96-06-25 15:01:36.082 add PID= 10741
0000 00010001 *.... *
DNA --- DEBUG : DNA - Network Input Line Trace:
96-06-25 15:01:36.084 add PID= 10741
0000 00000020 3AFEA8A9 00000000 00000181 00000000 *... :...............*
0014 40008F70 7AFE265C 00000004 *@..pz.&\.... *
DNA 3 INFO Exiting Routine dna_BoundServiceRequest.
96-06-25 15:01:36.089 add PID= 10741 426:581:0
DNA 3 INFO Exiting Routine dna_ServiceRequest.
96-06-25 15:01:36.089 add PID= 10741 426:787:0
DNA 2 INFO Entered Routine dna_CommitTxn.
96-06-25 15:01:36.119 add PID= 10741 426:1533:0
DNA 3 INFO Exiting Routine dna_CommitTxn.
96-06-25 15:01:36.120 add PID= 10741 426:1574:0
DNA 2 INFO Entered Routine dna_CloseClient.
96-06-25 15:01:36.133 add PID= 10741 426:1327:0
DNA 3 INFO Exiting Routine dna_CloseClient.
96-06-25 15:01:36.134 add PID= 10741 426:1429:0

Sample 2: An Unsuccessful Call For internal use.
Sample 2: An Unsuccessful Call

On the client side, a trace of an unsuccessful API call will look like this when
[TRACING] DEBUGLVL is set to 3:
96-06-25 15:00:28.627 add PID= 10733 426:267:2
DNA 3 INFO Exiting Routine dna_InitClient.
96-06-25 15:00:28.634 add PID= 10733 426:495:2
DNA 2 INFO Entered Routine dna_StartTxn.
96-06-25 15:00:28.667 add PID= 10733 426:1464:2
DNA 3 INFO Exiting Routine dna_StartTxn.
96-06-25 15:00:28.668 add PID= 10733 426:1505:2
DNA 2 INFO Entered Routine dna_ServiceRequest.
96-06-25 15:00:28.682 add PID= 10733 426:731:2
DNA 2 INFO Entered Routine dna_BoundServiceRequest - Service ADD.
96-06-25 15:00:28.684 add PID= 10733 426:545:2
DNA --- DEBUG : DNA - Input Data Length --------> 4
96-06-25 15:00:28.694 add PID= 10733
DNA --- DEBUG : DNA - Input Data --------------->
96-06-25 15:00:28.712 add PID= 10733
0000 00010003 *.... *DNA
100 USER Error establishing conversation with hope, errno = 146.
96-06-25 15:00:28.881 add PID= 10733 181:821:146
DNA 282 INTERNAL Client - could not open a channel ptr.
96-06-25 15:00:28.884 add PID= 10733 264:2184:146
DNA 44 INTERNAL Error Making Service Call "ADD" Over Protocol "tcpip".
96-06-25 15:00:28.897 add PID= 10733 131:1277:146
DNA --- DEBUG : DNA - Output Data Length -------> 0
96-06-25 15:00:28.898 add PID= 10733
DNA --- DEBUG : DNA - User Id ------------------>
96-06-25 15:00:28.899 add PID= 10733
DNA --- DEBUG : DNA - WorkStation Id ----------->
96-06-25 15:00:28.899 add PID= 10733
DNA --- DEBUG : DNA - Transaction Id -----------> 2505573269
96-06-25 15:00:28.902 add PID= 10733
DNA --- DEBUG : DNA - Calling Rule System Id --->
96-06-25 15:00:28.902 add PID= 10733
DNA --- DEBUG : DNA - Target Rule System Id ----> ADD
96-06-25 15:00:28.903 add PID= 10733
DNA --- DEBUG : DNA - Target Machine -----------> hope
96-06-25 15:00:28.903 add PID= 10733
DNA --- DEBUG : DNA - Target Server -----------> dnamsg
96-06-25 15:00:28.904 add PID= 10733
DNA --- DEBUG : DNA - Target Protocol ----------> tcpip
96-06-25 15:00:28.904 add PID= 10733
DNA --- DEBUG : DNA - Type Of Error -----------> 100
96-06-25 15:00:28.905 add PID= 10733
DNA --- DEBUG : DNA - Error Code ---------------> 100
96-06-25 15:00:28.905 add PID= 10733
DNA --- DEBUG : DNA - Protocol Error Code ------> 146
96-06-25 15:00:28.906 add PID= 10733
DNA 3 INFO Exiting Routine dna_BoundServiceRequest.
96-06-25 15:00:28.906 add PID= 10733 426:581:146
DNA 24 INTERNAL Error On Service Request for Service "ADD".
96-06-25 15:00:28.907 add PID= 10733 426:773:146

For internal use. Sample 2: An Unsuccessful Call
DNA 3 INFO Exiting Routine dna_ServiceRequest.

96-06-25 15:00:28.907 add PID= 10733 426:787:146

Sample 2: An Unsuccessful Call For internal use.

Index
INDEX
A E
abend code, messages organized by 7-1 e, indicates execution error 2-2
Abort Transaction, Error on 3-3 encryption exit, error received from 3-4
Analyze job 4-2 encryption library, error loading 3-4
ancestors 1-26 end rule event, error invoking 3-4
application execution messages 2-2 Entered Routine 3-1
authentication library, error loading 3-3 entry format for status view 8-2
authorization library, error loading 3-3 Entry Point, Error Resolving 3-3
autostart server 3-9 Error Allocating 3-2
Error Allocating Protocol Space 3-2
Error Closing Protocol 3-3
B Error code in status view 8-2
binding for service, none 3-4 Error Getting Protocol Information 3-2
Error Getting Service Information 3-3
error indication 2-2
C Error Initializing the Protocol 3-3
case sensitive 1-19 Error Invoking End Rule Event 3-4
CICS abend code, messages organized by 7-1 Error Invoking Protocol Function 3-3
Cmp, component prefix 2-2 Error Invoking Start Service Event 3-3
code generation messages 1-1 Error Loading Encryption Library 3-4
code pages 3-29 Error Loading Library 3-2
code, abend 7-1 Error Loading Protocol 3-2
combined service manager and service agent (SMSA) Error On Abort Transaction 3-3
3-18 Error On Commit Transaction 3-3
Commit Transaction, Error on 3-3 Error on Service Request 3-3
communications logs 8-1 Error On Start Transaction 3-3
communications message Error Opening File 3-2
external error 3-1 Error Reading variable 3-2
information 3-1 Error Received from User Encryption Exit 3-4
internal error 3-1 Error Resolving Entry Point 3-3
user error 3-1 error type in status view 8-2
compiler, third-party errors 3-46 execution messages (mainframe) 6-1, 7-1
exit usage 3-4, 3-20, 3-26, 3-28
D Exiting Routine 3-2
External communications error messages 3-1
DB2 rollback 4-1
EXTERNAL prefix 3-1
DEBUGLVL variable 8-1
dispatch library name, error getting 3-4
division by zero error 1-27 F
DNA Retry Number/Interval Value 3-3 failure in semaphore operation 3-14
dynamically loading file, error 3-46 forking server 3-21
AppBuilder 2.1.0 Messages Reference Guide i

G messages
application execution 2-2
gateway startup 3-22
development (host) 4-1, 5-1
execution (mainframe) 6-1, 7-1
H internal communications 3-1
Host name in status view 8-2 mainframe 4-1, 5-1
HPSError function 2-1 Rules code generation 1-1
HPSErrorMessage function 2-1 Rules preparation 1-1
rules preparation 1-1
run-time 2-2
I run-time (mainframe) 6-1, 7-1
i, indicates information about execution 2-2 multithreading server 3-21
I, indicates information about preparation 1-1
ID, see message identifier
identifier, message 1-1, 2-1, 2-2, 3-1
N
implementation file name 3-23 Name in status view 8-2
incompatible data types 1-3 Negative DNA Retry Number/Interval Value 3-3
INFO prefix 3-1 NetEssential initialization file 3-2
Information communications messages 3-1 No Client Context Found 3-2
information indication 2-2 No Routing Information 3-2
Internal communications error messages 3-1 No Service was Specified 3-2
internal communications messages 3-1 Non-IMS VSAM records 4-17
INTERNAL prefix 3-1 Null Error Code 3-3
Invalid Logical Unit of Work Value 3-3 Null Shared Memory Handle 3-16
Item1, placeholder 1-1
O
L object not found 1-10
Library, Error Loading 3-2 operating system
Loading Authentication Library 3-3 third-party errors 3-46
Loading Authorization Library 3-3
loading file dynamically, error 3-46 P
Loading RPC End Exit Library 3-3
Local Abort after RPC failed 3-3 PCCICS rule 1-2
Local Commit after RPC failed 3-3 preparation messages 1-1
LOG_UNIT_OF_WORK variable 3-3 protocol
Logical Unit of Work, Invalid 3-3 third-party errors 3-46
LU2 logoff script 3-12, 3-35 Protocol Function 3-3
LU2 logon script 3-12, 3-27, 3-35 Protocol in status view 8-2
protocol messages 3-1
Protocol, Error Closing 3-3
M Protocol, Error Initializing 3-3
macro definition 1-24
mainframe messages 4-1, 5-1 Q
maximum line length 1-3
quote string 1-25
message identifier 1-1, 2-1, 2-2, 3-1
message severity 1-1, 2-2
R
radix 1-23, 1-25
Index ii
Rebuild Package 4-13, 4-15, 4-19 trace file 8-1
Rebuild Report 4-17 entry format 8-1
route table 3-8 trace of a successful API call 8-2
routing information, none 3-4 trace output 8-1
RPC End Exit library, error loading 3-3 TRACING section 8-1
Rules code generation messages 1-1 Transaction ID in status view 8-2
rules error messages (preparation) 1-1 TRCFILE variable 8-1
run-time messages 2-2 trigger 3-34
Type of error in status view 8-2
S
s, indicates severe execution error 2-2 U
S, indicates severe preparation error 1-1 Unit of Work Value, Invalid Logical 3-3
sample trace of unsuccessful API call 8-4 UNIX
segment permissions 3-12 unresolved symbols 3-46
semaphore failure 3-14 unresolved symbols on UNIX 3-46
Server ID in status view 8-2 unsuccessful API call, sample trace 8-4
server startup 3-21, 3-22, 3-25 user authorization exit, error received from 3-4
server startup syntax 3-18 user communications error messages 3-1
Service Info, Error Getting 3-3 user encryption exit, error received from 3-4
Service Manager 3-4 User ID in status view 8-2
Service Request, Error on 3-3 user login name, error getting 3-4
severe execution error indication 2-2 USER prefix 3-1
severe preparation error indication 1-1 user RPC end exit, error received from 3-4
severity of message 2-2
severity of preparation message 1-1
shadowing 3-6 V
shared memory failure 3-14, 3-15, 3-16 VTPM layer 3-6
shared memory overflow 3-14
SMA section 3-15
SQL ASIS statement 1-10, 1-12, 1-13, 1-20, 1-27
W
Start Service Event, Error Invoking 3-3 w, indicates warning in execution 2-2
Start Transaction, Error on 3-3 W, indicates warning in preparation 1-1
startup server 3-21 warning indication 1-1, 2-2
status view entries 8-2 Workstation ID in status view 8-2
subcell table usage 3-35, 3-36
subsystem name, check 3-4
successful API call, sample trace 8-2
support code 3-29
symbol 1-25
syntax error 1-2, 1-3, 1-22, 1-26
system ID in status view 8-2
System security 6-1, 6-2
T
table-driven eventing 3-34
third-party error numbers 3-46
Index iii

App Builder Messages PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

App Builder Messages PDF

Transféré par

Droits d'auteur :

Formats disponibles

BluePhoenix AppBuilder 2.1.0.

Messages Reference Guide

1992-2003 BluePhoenix Solutions

AppBuilder 2.1.0 Messages Reference Guide

1 Rules Language Preparation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

2 Execution Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

3 Communications Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

4 Enterprise Development Messages (Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

5 Enterprise Development Messages (Part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

6 Enterprise Execution Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

7 Enterprise Messages by CICS Abend Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

8 Trace File Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

AppBuilder 2.1.0 Messages Reference Guide i

1 RULES LANGUAGE PREPARATION

AppBuilder 2.1.0 Messages Reference Guide

Rules Preparation Messages

Table 1-1 Rules Preparation Messages

AppBuilder 2.1.0 Messages Reference Guide 1-1

Table 1-1 Rules Preparation Messages (Continued)

1-2 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-3

Table 1-1 Rules Preparation Messages (Continued)

1-4 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-5

Table 1-1 Rules Preparation Messages (Continued)

1-6 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-7

Table 1-1 Rules Preparation Messages (Continued)

1-8 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-9

Table 1-1 Rules Preparation Messages (Continued)

1-10 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-11

Table 1-1 Rules Preparation Messages (Continued)

1-12 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-13

Table 1-1 Rules Preparation Messages (Continued)

1-14 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-15

Table 1-1 Rules Preparation Messages (Continued)

1-16 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-17

Table 1-1 Rules Preparation Messages (Continued)

1-18 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-19

Table 1-1 Rules Preparation Messages (Continued)

1-20 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-21

Table 1-1 Rules Preparation Messages (Continued)

1-22 Rules Language Preparation Messages

Table 1-1 Rules Preparation Messages (Continued)

AppBuilder 2.1.0 Messages Reference Guide 1-23

Table 1-1 Rules Preparation Messages (Continued)