Académique Documents
Professionnel Documents
Culture Documents
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
Table of Contents
Index ....................................................................................... i
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.
2 EXECUTION MESSAGES
Error messages that appear during application run-time are described in the sections that follow:
Rules Execution Messages
Application Execution Messages
Table 2-1 lists the rules execution messages in the order of the message identifier.
Table 2-1 Rules Execution Messages
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
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.
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.
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.
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.
4 ENTERPRISE DEVELOPMENT
MESSAGES (PART 1)
This section lists messages you may encounter when developing an application in an enterprise
(mainframe) environment.
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.
This section lists execution (run-time) messages you may encounter when you run an application in an
enterprise environment.
This section describes the CICS abend code execution messages you may encounter when running an
application in an enterprise environment.
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.
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
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
INDEX
AppBuilder 2.1.0 Messages Reference Guide
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
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