AionDS Messages and Codes Guide

Messages and Codes 

PLATINUM technology, inc. 

555 Twin Dolphin Drive, Suite 400 

Redwood City, CA 94065 

DC0431 (415) 591-8200

................................................................................................................................. 

Title and publication number 


DC0431 

................................................................................................................................. 

Product version 

This manual accompanies the 7.0 Release of AionDS. 

................................................................................................................................. 

Copyright information 

© 1991-1996 by PLATINUM technology, inc. All rights reserved. 

................................................................................................................................. 

Notices 

No part of this document may be reproduced in any form or by any means, electronic, 

mechanical, photocopying, recording, or otherwise, without the express permission of 

PLATINUM technology, inc. 

RESTRICTED RIGHTS LEGEND. Use, duplication, or disclosure by the U.S. 

Government is subject to restrictions as set forth in a contract with PLATINUM technology, 

inc. (formerly Trinzic Inc., formerly Aion Corporation/AICorp, Inc.) and, if applicable, 

subpar. (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 

252.227-7013 or subpars. (c)(1) and (2) of the Commercial Computer Software - Restricted 

Rights clause at 48 CFR 52.227-19, as applicable. The contractor/manufacturer is 

PLATINUM technology, inc., 555 Twin Dolphin Drive, Suite 400, Redwood City, CA 

94065. 

Additional copies of this document can be ordered from PLATINUM technology, inc. Contact 

PLATINUM technology, inc. for prices on bulk orders and fees for reproduction licenses. 

................................................................................................................................. 

Trademarks 

AION, Forest & Trees, and KBMS are registered trademarks, and InfoHub, 

InfoPump, and INTELLECT are trademarks of PLATINUM technology, inc. 

All other products or other names referenced are the trademarks, registered trademarks, or 

products of the respective manufacturers. 

................................................................................................................................. 

Acknowledgements 

Writer: Michele Gustafson 

Assisted by: Scott Asire, Michael Campbell, Wynne Stepp

Preface How to Use This Manual 

Table of Contents 

Chapter 1 AionDS Runtime Errors 

Overview ..................................................................................................................... 1-2 

Table of error messages.............................................................................................. 1-4 

Table for converting error codes ................................................................................ 1-37 

AionDS runtime errors ............................................................................................... 1-47 

Chapter 2 Transaction Driver Messages 

CICS transaction driver messages............................................................................... 2-2 

Post Version 6.00-style messages (MSG600=NO).......................................... 2-3 

Version 6.0-style messages (MSG600=YES) ................................................ 2-11 

IMS and TSO transaction driver messages................................................................2-16 

Chapter 3 CICS/VS Exception Conditions 

CICS/VS exception conditions ..................................................................................... 3-2 

Chapter 4 DB/DC Program Interface Return Codes 

ADSMSW (Message switching function)...................................................................... 4-2 

ADSULINK (User link facility)....................................................................................... 4-4 

ADSPSB (Schedule a new PSB - AionDS/CICS only).................................................. 4-6 

ADSMOD (Schedule a new IMS Mod Name - AionDS/IMS only) ................................. 4-8 

Chapter 5 MAES Error Codes 

MAES-specific codes................................................................................................... 5-2 

Return codes .................................................................................................. 5-4 

Request codes................................................................................................ 5-8 

Status Codes .................................................................................................. 5-9 

Table of Contents iii

Chapter 6 MAESLOG Messages 

iv AionDS Messages and Codes 

MAESLOG messages ................................................................................................. 6-2 

Chapter 7 AionDS Fatal System Errors 

Overview ..................................................................................................................... 7-2 

Fatal system errors...................................................................................................... 7-4 

Chapter 8 AionDS System Log 

Examining the system log............................................................................................ 8-2 

Timestamp messages..................................................................................... 8-4 

Execution messages....................................................................................... 8-5 

Consultation messages................................................................................... 8-7 

Database messages ....................................................................................... 8-8 

QSAM and Local VSAM Messages .................................................... 8-8 

Remote VSAM Messages................................................................. 8-10 

SQL Messages................................................................................. 8-12 

DL/I Messages .................................................................................8-13 

Miscellaneous messages .............................................................................. 8-14

How to Use This Manual 

.........................................................................................................................................................................................................˝.......................................... 

What this manual is 

about 

Use the AionDS Messages and Codes manual to assist in debugging 

knowledge-based applications developed with the Aion Development System 

(AionDS). This manual describes AionDS runtime errors, API errors, 

transaction driver messages, CICS/VS exception conditions, DB/DC 

program interface return codes, MAES error codes, MAESLOG messages, 

AionDS fatal system errors, and the format of the AionDS system log. 

.........................................................................................................................................................................................................˝.......................................... 

How to find 

information 

This manual is organized as follows: 

Chapter Contents 

Chapter 1 describes AionDS, HPO, ADSAPI, AAPI/CICS, and AAPI/IMS 

errors that are issued while running a knowledge base 

Chapter 2 describes the messages that are issued by the AionDS/CICS and 

AionDS/IMS transaction drivers 

Chapter 3 describes the EIB codes returned from EXEC CICS calls issued by 

the AionDS/CICS transaction driver 

Chapter 4 describes the codes returned from the ADSMSW, ADSULINK, 

ADSPSB, and ADSMOD program interface routines 

Chapter 5 describes the AionES Control Block (AESCB) AESRCODE return 

codes and the MAES-specific codes 

Chapter 6 describes the messages that are written to the MAESLOG 

Chapter 7 describes the most common fatal system errors that can be reported 

by AionDS and HPO while running a knowledge base 

Chapter 8 describes the format of the AionDS system log 

How to Use This Manual v

.........................................................................................................................................................................................................˝.......................................... 

For more 

information 

vi AionDS Messages and Codes 

To develop knowledge base applications in AionDS, you should also have the 

following AionDS manuals: 

General Reference 

Language Reference 

I/O Reference 


User’s Guide (Character-Based) 

Installation and Operation Guide for your platform 

Application Programming Interface Guide for your platform 

............................................................................................................................................................................. 

GUI applications 

If you are building a knowledge base with a graphical user interface, you 

should also have the following AionDS manuals: 

Building GUI Applications: Reference 

Building GUI Applications: Tutorial 

User’s Guide 

............................................................................................................................................................................. 

TP monitor options 

In addition, if you are running one of the AionDS teleprocessing (TP) 

monitor options for AionDS/MVS (AionDS/CICS and AionDS/IMS), see 

the corresponding Installation and Operation Guide: 

AionDS/CICS Option Installation and Operation Guide 

AionDS/IMS Option Installation and Operation Guide 

Note: If you are running one of the AionDS teleprocessing (TP) monitor 

options for AionDS/MVS (AionDS/CICS or AionDS/IMS), you must set up 

the Aion Multitasking Monitor (MAES) to run, monitor and manage 

multiple AionDS consultations simultaneously as subtasks under MAES. For 

more information about setting up MAES, see Aion Multitasking Monitor 

(MAES) Installation and Operation Guide.

............................................................................................................................................................................. 

Communicating with external programs 

For information about using external programs to communicate with 

AionDS/MVS or call AionDS/MVS from external programs, see 

AionDS/MVS Application Programming Interface Guide. For information 

about using external programs to communicate with or call one of the 

AionDS TP monitor options for MVS, see AionDS/CICS Option Installation 

and Operation Guide for AionDS/CICS or AionDS/IMS Option Installation 

and Operation Guide for AionDS/IMS. 

............................................................................................................................................................................. 

HPO 

For information about installing, operating, and troubleshooting HPO, see 

Aion HPO/MVS Installation and Operation Guide. 

............................................................................................................................................................................. 

Application Testing Facility 

For information about installing and operating the Application Testing 

Facility/MVS (ATF/MVS), see Aion Application Testing Facility. 

.........................................................................................................................................................................................................˝.......................................... 

Aion® product 

abbreviations 

The AionDS documentation set uses the following abbreviations for Aion® 

products: 

Aion® product Abbreviation 

Aion® Development System AionDS 

Aion® Execution System AionES 

Component Aion® Execution System CAES 

Multitasking Aion® Execution System MAES 

Aion® Development System Application 

Programming Interface 

ADSAPI 

continued 

How to Use This Manual vii

viii AionDS Messages and Codes 

continued 

Aion® product Abbreviation 

Aion® High Performance Option HPO 

Aion® Cooperative Processing Option CPO 

Callable Aion® Building System CABS 

Aion® Code Integration Option CIO 

.........................................................................................................................................................................................................˝.......................................... 

Conventions 

The AionDS documentation set uses the following conventions. 

............................................................................................................................................................................. 

Typeface 

The AionDS documentation set uses these typeface conventions: 

Style of type What it represents 

Boldface new term and its definition 

Italic ■ manual titles 

■ syntax variables 

■ emphasis 

■ foreign language phrases 

Monospace ■ code examples 

■ prompts and messages 

■ examples of user input (in procedures, for example)

............................................................................................................................................................................. 

Icons 

The AionDS documentation set uses these icons: 

Symbol Meaning 

Alternative: identifies an alternative to the previous procedure 

(choice is usually a matter of personal preference; 

neither offers a distinct advantage) 

Caution: helps you avoid mistakes that can produce 

unexpected or undesirable results (runtime errors 

and losing work, for example) 

Exception: indicates an exception to common functionality 

or behavior 

For more information: identifies additional sources of information on a 

particular topic 

Important: stresses a point that can help you achieve greater 

success with the AionDS product 

Reminder: reminds you in passing of an important aspect 

that was discussed previously 

Tip: suggests a technique that can result in more 

efficient use of the system 

identifies a one-step procedure 

How to Use This Manual ix

x AionDS Messages and Codes 

............................................................................................................................................................................. 

Syntax 

The following conventions are used to define the AionDS syntax and 

command formats in this manual. 

■ You must type letters that are capitalized. You do not have to capitalize 

these letters. Lowercase letters are optional. If a command or syntax 

statement contains both capitalized and lowercase letters, you can type 

only the capitalized letters: 

RUn 

For the above command, you can type the following letters: 

ru 

run 

You cannot type the following letter: 

r 

Important: For AionDS running on UNIX platforms, AionDS 

commands are not case sensitive. However, file names that exist in 

UNIX (for example, knowledge base names) must be typed in uppercase 

and lowercase exactly as displayed in UNIX. 

■ Italics indicate a response that you must specify: 

RUn kb_name 

The expected response for an italicized word is indicated below the 

command or syntax statement. 

■ Brackets indicate an option: 

ASORT (expr [ON key]) 

The ON key phrase is optional. 

■ A bar indicates a choice: 

List-objects [State st_name | Vocabulary vocab_nm] 

In this case, you can type either the State choice or the Vocabulary 

choice. 

■ Braces indicate a required choice: 

List-objects {State st_name | Vocabulary vocab_nm} 

You must type a State choice or a Vocabulary choice.

■ You must use other characters, such as parentheses and angle brackets, 

exactly as specified: 

EOF (fparam) 

The parentheses are required. 

■ An ellipsis (...) indicates that you can repeat a choice: 

param IS FROM (stexpr, stexpr, [, stexpr ...]) 

You can repeat “, stexpr” as many times as you want. 

How to Use This Manual xi

xii AionDS Messages and Codes

Chapter 1 

AionDS Runtime Errors 

.........................................................................................................................................................................................................˝.......................................... 

Introduction 

This chapter describes runtime errors that are reported when you run an 

AionDS or HPO knowledge-based application. AionDS runtime errors 

consist of an error code and an error message. 

.........................................................................................................................................................................................................˝.......................................... 

In this chapter 

Topic Page 

Overview 1-2 

Table of error messages 1-4 

Table for converting error codes 1-37 

AionDS runtime errors 1-47 

AionDS Runtime Errors 1-1

Overview 

Overview 

.........................................................................................................................................................................................................˝.......................................... 

Runtime errors occur 

1-2 AionDS Messages and Codes 

Most runtime errors occur because of an error in the knowledge base logic. 

In this situation, the following occurs: 

1 The error code is stored in the AionDS predefined parameter 

AES_ERRORNUM. 

2 The error message is stored in the AionDS predefined parameter 

AES_ERRORMSG. 

3 The error message is written to the AionDS system log and consultation 

trace. 

4 If the predefined parameter AES_ABORT is set to TRUE, a 

Consultation Error screen is displayed showing the error message. If 

AES_ABORT is set to FALSE, the Consultation Error screen is not 

displayed, allowing the application to interpret and process the error. 

For more information: See the “Predefined parameters” subsection of 

“Error Handling Parameters” in Chapter 10 of the AionDS General Reference 

manual for more information about AES_ERRORNUM, 

AES_ERRORMSG and AES_ABORT. 

Other runtime errors occur prior to the consultation being started, such as 

the knowledge base not being found, or in response to user actions that do 

not violate the knowledge base logic, such as pressing an invalid function key. 

In these situations, the error message is displayed by default in the message 

window if the window exists on the screen. 

You can set the ERROR-MESSAGE profile option to have AionDS display, 

or not display, the error code in addition to the error message text. 

For more information: See the AionDS User’s Guide or User’s Guide 

(Character-Based) for more information about the ERROR-MESSAGE 

profile option.

Overview 

.........................................................................................................................................................................................................˝.......................................... 

Error message 

variables 

Some error messages in this manual include the variables %1, %2, or %3. 

When AionDS displays an error message, it substitutes appropriate values for 

these variables. For example, in the following error message AionDS 

substitutes the knowledge base name and version in the place of the variables: 

%1 %2 v%3 cannot be loaded; saved form is incompatible 

.........................................................................................................................................................................................................˝.......................................... 


This chapter is divided into the following sections: 

■ The first section provides a table of error messages, alphabetized by the 

error message text. Use this table to look up the error code when the 

ERROR-MESSAGE profile option is set to TEXT. 

■ For some error messages, the error code stored in the 

AES_ERRORNUM parameter is not the same as the error code 

displayed on the screen or in the AionDS system log, when the ERROR- 

MESSAGE profile option is set to ON or CODE. The second section 

explains the two numbering schemes and provides a table to convert error 

codes from one scheme to another. 

■ The third section explains the AionDS runtime errors that can occur on 

all platforms, and offers suggested responses to them. The errors are 

listed by error code in ascending order. 

Some error messages in this manual include the variables %1, %2, or %3. 

When AionDS displays an error message, it substitutes appropriate values for 

these variables. For example, in the following error message AionDS 

substitutes the knowledge base name and version in the place of the variables: 

%1 %2 v%3 cannot be loaded; saved form is incompatible 


Table of error messages 


.........................................................................................................................................................................................................˝.......................................... 

Overview 


By default, AionDS does not include the error code in the error message text 

when displaying runtime errors or writing them to the AionDS system log. 

The error code is only included when the ERROR-MESSAGE profile option 

is set to ON or CODE. 

If the ERROR-MESSAGE profile option is set to TEXT, use the following 

table to determine the error code based on the error message text. After 

determining the error code, look for the explanation of the error later in this 

chapter. 

This table includes runtime error messages that are issued by AionDS, HPO, 

ADSAPI, AAPI/CICS and AAPI/IMS. Error messages issued by the 

AionDS/CICS and AionDS/IMS transaction drivers, as well as MAES, are 

not included in this table. 

For more information: See “How to Use This Manual” for information 

about where to find these messages. 

The following table shows the AionDS runtime error messages in alphabetical 

order. 

Message Code 

‘+’ expected (row %1/col %2) 50115 

‘=‘ or ‘is’ expected (row %1/col %2) 50114 

“%1” expected 13513 

%1%2 v%3 cannot be loaded; saved form is incompatible 28808 

%1%2 v%3 has invalid header format 23312 

%1-PROGRAM requested application termination 4883 

%1-PROGRAM requested consultation error processing 4884 

%1: Cannot import slot into external class 13216 

%2: Inherited properties will affect a hidden or read-only object - %1 13214


%Currentclass unexpected 22604 

%is, % and %current are prohibited when method is invoked on a class 22553 

-- Errors are in file 51156 

A SQL database connection cannot be established 20410 

Access denied 21308 

Access Method not supported by current environment 32806 

ADSAPI error: Buffer too small 19302 

ADSAPI error: Chained request errors 19303 

ADSAPI error: Driver buffer too small 19230 

ADSAPI error: FPL not supported 19354 

ADSAPI error: FPL parameter not found 19305 

ADSAPI error: Instance not found 19308 

ADSAPI error: Invalid delivery class 19236 

ADSAPI error: Invalid info level 19304 

ADSAPI error: Invalid item width 19313 

ADSAPI error: Invalid message 19237 

ADSAPI error: Invalid object name 19317 

ADSAPI error: Invalid object property 19311 

ADSAPI error: Invalid object range 19300 

ADSAPI error: Invalid object type 19307 

ADSAPI error: Invalid option flags 19235 

ADSAPI error: Invalid program specification 19234 

ADSAPI error: Invalid request 19301 

ADSAPI error: Invalid slot index 19312 

ADSAPI error: Invalid string width 19314 

ADSAPI error: MAES not active 19350 




ADSAPI error: MAES not connected 19351 

ADSAPI error: No more instance values 19310 

ADSAPI error: Object not found 19316 

ADSAPI error: Object pended 19319 

ADSAPI error: Parent not found 19315 

ADSAPI error: Parent not in scope 19318 

ADSAPI error: Session abend 19353 

ADSAPI error: Session not freed 19352 

ADSAPI error: Too many instance names 19309 

ADSAPI error: Unexpected response 19233 

ADSAPI is in an uninitialized state 19204 

ADSAPI receive timed out 19211 

ADSAPI server has died 19223 

ADSAPI server not responding 19203 

ADSAPI session name already in use 19201 

ADSAPI session not found 19202 

ADSAPI subsession has already been claimed 19220 

ADSAPI subsession not found 19218 

Aion Database Interface for DBC/1012 not installed 20416 

AION views are not supported for importing 37378 

All SQL cursors are currently in use 20403 

All SQL statements need a database connection before they can proceed 37360 

Ambiguous keyword 13503 

API subsystem received unexpected OS return code 19299 

Argument %1 to Window or DDE function is missing or unknown 1501 

Argument to AES function missing or unknown 950


Argument to CM function is missing or unknown 1346 

Argument to LN function is less than or equal to zero 2105 

Argument to SQRT function is negative 2104 

Argument to TRUNC or ROUND function is too large 2106 

ASCIIEBCDIC translation failure 20582 

ASCIIEBCDIC translation table load failure 20583 

ASK-PROGRAM (group) processing did not complete 5003 

ASK-PROGRAM processing did not complete 5000 

Assignment inconsistent with existing constraint 1004 

At least two files must be selected for comparison 28635 

Attempt to add duplicate key 32532 

Attempt to change prime key or key of reference 20345 

Attempted to delete a static instance 1341 

Attempted to use invalid date or time value 970 

Backup dataset is not allocated 26399 

Bad alpha input 16022 

Bad alphanumeric input 16023 

Bad argument passed to the INDEX function 1366 

Bad argument passed to the READSTR or WRITESTR function 1368 

Bad argument passed to the SET function 1365 

Bad boolean value format 20112 

Bad character input 16024 

Bad date format 20109 

Bad day input 16014 

Bad decimal input 16028 

Bad digit input 16027 




Bad full (4 char) year input 16010 

Bad hour input (1, 12) 16016 

Bad hour input (1, 24) 16017 

Bad hundredth second input 16020 

Bad integer format 20110 

Bad integer size 20123 

Bad minute input 16018 

Bad number input 16026 

Bad numeric input 16025 

Bad numeric month input 16012 

Bad ordinal input 16015 

Bad packed-decimal format 20105 

Bad real number format 20111 

Bad record format; field data truncated 32730 

Bad second input 16019 

Bad separator 16009 

Bad sign input 16029 

Bad textual month input 16013 

Bad time format 20108 

Bad time input (am, pm) 16021 

Bad year input 16011 

Bad zoned-decimal format 20106 

Bottom Margin is less than 0 22561 

Browse field is not defined 26332 

Buffer is too large for ADSAPI transfer 19213 

BYTES clause not found (row %1/col %2) 50031


Can’t load A7CABS.DLL 51100 

Cannot append to specified dataset 21309 

Cannot automatically invoke method with input/output parms or return 

value 

1343 

Cannot create %1%2 v%3; may already exist 28851 

Cannot create Slot in external class; try subclassing 12235 

Cannot delete given file specification 21312 

Cannot index on a memo field (row %1/col %2) 50108 

Cannot open DesktopWindow; existing DesktopWindow has open child 

windows 

Cannot send AssignAnswer when window is attached to a non-answer 

property 

1423 

51845 

Cannot specify member; filename is already allocated to a member 21323 

Certainty out of legal range (-1.0



Column is too wide 22575 

Column name not found or invalid 50303 

Comma must be used to separate option keywords 2903 

Command not allowed in a &TBL command 22572 

Command not allowed in the title of a table 22578 

Communications Client rejected APPC startup 20549 

Connection to host system is not active 20506 

Context too large; recompile using /o switch, with a higher 

argument 

51003 

Contradictory options specified 2906 

Could not optimize KB 51033 

CPO communication error occurred as a result of a previous error 20507 

CREATE function not valid for WINLIB instances; use CreateObject 

instead 

2778 

Cursor is not inside a printable window 26371 

Data Integrity Check failed 32804 

Data lengths are inconsistent 1213 

Data lengths are inconsistent with label lengths 1205 

Data transfer error 46763 

Data type not supported on this ODBC Data Source 50312 

Database file not found or invalid 32801 

Dataset has unsupported organization 21326 

Dataset is already cataloged 21339 

Dataset is in use 21315 

Dataset is not open 20200 

Dataset member not found 21304 

Dataset member not found or other error occurred during OPEN 21338


Dataset not cataloged 21303 

Dataset not open for adding records 20307 

Dataset not open for reading records 20304 

Dataset not open for updating records 20306 

Dataset not open for writing records 20305 

Dataset primary allocation full and no secondary space was requested 21318 

Dataset record length inconsistent with type definition 20301 

Dataset space is exhausted and cannot be extended 21317 

DB2 subsystem name missing or greater than 4 characters 20413 

dBASE CLOSEFILE failed 32702 

dBASE DELETEREC failed 32711 

dBASE GETREC attempted at end-of-file 32714 

dBASE OPENFILE failed 32703 

dBASE PUTREC failed 32712 

dBASE record does not exist 32732 

dBASE SELECT failed 32706 

DBC/1012 tdpid greater than 4 characters 20415 

DBC/1012 tdpid greater than 8 characters 20415 

DBMS function aborted; Class already in process 1367 

DDE - Delete Link failed 1432 

DDE - Paste Link failed 1431 

DELETE function not valid for WINLIB instance; use DeleteObject 

instead 

3359 

Delete system function only valid when sourcing a Class 26375 

Difference between Right and Left Margins is too large (more than 510) 22511 

Disk full 21318 

Disk is read-only 21315 




Disk not accessed 21330 

Display field out-of-bounds 2016 

Display terminal does not support graphics 1211 

Division by zero 2100 

DL/I DELETE request failed 20392 

DL/I GET request failed 20390 

DL/I PUT request failed 20391 

DL/I request failed - DL/I database not open 20395 

DL/I request failed - DL/I function unscheduled 20377 

DL/I request failed - DL/I language conflict 20373 

DL/I request failed - DL/I scheduling conflict 20387 

DL/I request failed - DL/I task not authorized 20388 

DL/I request failed - DL/I UIBDLTR unknown 20379 

DL/I request failed - DL/I UIBFCTR unknown 20378 

DL/I request failed - DL/I unscheduled termination 20376 

DL/I request failed - invalid PSB 20398 

DL/I request failed - invalid PSB address 20386 

DL/I request failed - invalid request 20399 

DL/I request failed - number of SSA’s exceeds 16 20394 

DL/I request failed - PSB already scheduled 20389 

DL/I request failed - PSB initialization failed 20374 

DL/I request failed - PSB not authorized 20375 

DL/I request failed - unknown database name 20393 

Drive is not ready 21310 

Dynamic dataset allocation error 21306 

Dynamic dataset allocation failed (SVC reason code = ‘%5’) 21319


Element with certainty 1.0 will be the only entry in the set 26343 

Empty list/set is not valid here 26367 

Empty string is not valid here 26366 

Environment variable AIONHPO is not set up 51008 

Error during file close 21333 

Error during I/O operation on External Data file 12001 

Error during I/O to report output file 22528 

Error during read from file 21335 

Error during write to file 21334 

Error occurred executing %1-PROGRAM user exit 4886 

Error occurred processing remote report 22699 

Error occurred starting program 46703 

Error opening file %1; file not found 51841 

Error opening graphical object - %1 1418 

Error passing parameters into the state 1001 

Error returning parameters from the state 1002 

Error: DDE Library not found 3361 

Error: Window Library not found 3357 

Executing %1-PROGRAM user exit 4885 

EXITSTATE used outside of agenda; use /e command-line switch 51001 

EXITSTATE used outside of agenda; use EXIT option with KBOPT 51001 

Expected instance reference: class_name(instance_name) (row %1/col %2) 12017 

Explanation is not enabled; trace-level must be greater than zero 26333 

External program abended 46783 

External program LOAD failed 46781 

Extraneous input 13504 




Fetching data to invalid file parameter, make sure cursor is opened 37355 

FIELD clause not found (row %1/col %2) 50033 

Field name expected (row %1/col %2) 50107 

File already exists 21339 

File is not open 20200 

File is not open and/or unenabled 20368 

File is read-only 21309 

File locking violation 21318 

File must be a database file, not an index or memo file 32737 

File not found 20300 




File not open 21302 

File not open for adding records 20307 

File not open for reading records 20304 

File not open for updating records 20306 

File not open for writing records 20305 

File not opened for reading 32736 

File opened for reading only 32739 

File record length inconsistent with type definition 20301 

File size exceeds 64K limit for TextWindow 51843 

File truncated 2006 

Fixed Parameter List (FPL) does not exist 19212 

Fixed size must be 2 or 4 20126 

Fixed-point overflows 20101


Forwardchain request ignored; Forward Chainer in progress 1373 

FPL contains invalid PDB 46761 

FPL input/output error 46762 

FPL parameter missing 46760 

GETREC called at end-of-file 20307 

GETREC called at end-of-file 20308 

GETREC open mode must be UPDATE 32710 

GRAPH-PROGRAM processing did not complete 5002 

Graphic display not available for %1 (%2) 5006 

Graphical object does not exist - %1 1416 

Graphical object is not compatible format or is corrupt - %1 1417 

Graphics adapter incompatible with GRAPHICS-DRIVER table 1216 

Graphics library (ADSGM6.DLL) not found on LIBPATH 1218 

Graphics subsystem received unexpected OS return code 1220 

GRAPHICS-DRIVER table not found or invalid 1210 

Group Processing not available for %1 (%2) 5007 

Header too long 1206 

I/O error occurred opening PRINT-FILE 5008 

I/O error writing PRINT-FILE 5009 

I/O operation invalid; GETREC-UPDATE returned EOF 20385 

I/O operation not supported by access method 20311 

I/O operation not supported for this dataset type 20310 

I/O operation not supported for this dataset type 20312 

I/O operation not supported for this file type 20312 

I/O privilege not configured (add IOPL=YES to CONFIG.SYS) 1219 

Illegal assignment 1000 




Illegal assignment: types incompatible 1371 

Illegal attempt to access private method 22602 

Illegal attempt to access private slot 22601 

Illegal character; ampersand(&) is not allowed 1409 

Illegal comparison - types are not compatible 1362 

Illegal operation for TextWindow with TWS_LABEL or 

TWS_READONLY style 

1401 

Illegal operation for TextWindow with TWS_LABEL style 1402 

Illegal operation; can’t explicitly close a graphical object 1421 

Illegal operation; can’t explicitly open a graphical object 1420 

Illegal operation; can’t use SetText on a window with WS_TSL style 1410 

Illegal operation; cannot change parent of app window or modal dialog - %1 1428 

Illegal operation; cannot Close a DesktopWindow instance 1422 

Illegal operation; child window equals or is an ancestor of parent window - 

%1 

1425 

Illegal operation; object is not open - %1 1408 

Illegal operation; object is open - %1 1407 

Illegal operation; OpenApp may not be sent to dialogs 1435 

Illegal operation; specified parent window cannot have children - %1 1424 

Illegal operation; specified window may not be a child of the desktop - %1 1427 

Illegal operation; the desktop is not a valid parent for controls 1403 

Illegal operation; toolbars may only contain tools 1433 

Illegal operation; tools may only be placed in toolbars 1434 

Illegal operation; window cannot be set to unknown 51844 

Import is only valid for the knowledge base owner 13215 

Incompatible ADSAPI.DLL and ADSAPI.EXE (version mismatch) 19229 

Incorrect data format encountered in External Data file 1012


Incorrect key length 20314 

Incorrect key location 20313 

Incorrect password; access to knowledge base denied 28807 

Incorrect password; try again 28617 

Index file not found or invalid 32802 

Index key does not exist 32734 

Index table name invalid (row %1/col %2) 50305 

Inherited child object’s authorization restricted by parent’s authorization 13424 

Inherited properties will affect a hidden or read-only object 12241 

Initialization of Database failed after DLL is loaded 37356 

Input data is inconsistent with the specified mask 16001 

Input is too long 16002 

Instance does not exist 22542 

Instance is static; cannot be deleted 26394 

Insufficient disk space 21303 

Insufficient disk space for copy of knowledge base 28855 

Integer overflow (value cannot be represented by an integer) 2201 

Internal ADSAPI error: Invalid channel id 19227 

Internal ADSAPI error: Invalid flags parameter 19208 

Internal ADSAPI error: Invalid netpath 19209 

Internal ADSAPI error: Invalid parameter 19226 

Internal ADSAPI error: Invalid parameter value 19225 

Internal ADSAPI error: Invalid server command 19200 

Internal ADSAPI error: Invalid session handle 19224 

Internal ADSAPI error: Invalid subrequest index 19215 

Internal ADSAPI error: Request canceled 19228 




Internal ADSAPI error: Request is gone 19216 

Internal ADSAPI error: Segment is not shareable 19214 

Internal ADSAPI error: Session is not a child 19210 

Internal stack overflow; check application for recursive logic 1370 

Invalid add to processed list/set ignored 1334 

Invalid ADSAPI Parameter Descriptor Block 19206 

Invalid ADSAPI session handle 19205 

Invalid ADSAPI string parameter length 19207 

Invalid amount of x-Data parameters 33235 

Invalid argument (must be a full parameter reference) 1336 

Invalid argument (must be a VCC parameter) 1337 

Invalid argument passed to the BIN function 1008 

Invalid argument passed to the DATE function 1017 

Invalid argument passed to the HEX function 1007 

Invalid argument passed to the NUM function 1005 

Invalid argument passed to the TIME function 1018 

Invalid attempt to add elements to a list/set 951 

Invalid block size; must be a multiple of 80 34334 

Invalid boolean value 28826 

Invalid character specification 34318 

Invalid class; use “A” to “Z”, “0” to “9”, or “*” 34332 

Invalid color passed to CM Color function 1350 

Invalid command mode; valid values are “MENU” and “COMMAND” 34304 

Invalid compatibility mode; valid values are "OS" and "PC" 34305 

Invalid create; instance name already exists 1342 

Invalid cursor position for EXECUTE key 26320


Invalid cursor position for EXPLAIN 26369 

Invalid cursor position for selection 42660 

Invalid data type (row %1/col %2) 50037 

Invalid database name (0 or greater than 8 characters) 20381 

Invalid dataset specification 21305 

Invalid dataset type/organization 20310 

Invalid date format 26340 

Invalid date mask 34312 

Invalid dBASE version; "III" and "IV" are valid 34321 

Invalid DD Name 46471 

Invalid device model; use 0, 1, 2, 3, 4, or 5 34331 

Invalid device type 34317 

Invalid EXE format - program not runnable by this operating system 21319 

Invalid field for MARK key 26318 

Invalid field for Select function; must be a menu 26374 

Invalid field name (row %1/col %2) 50105 

Invalid field or variable name 20203 

Invalid field specified for keyed selection 20201 

Invalid field type (row %1/col %2) 50106 

Invalid file parameter or class in SQL string 20470 

Invalid file specification 21305 

Invalid file specification 26393 

Invalid filemode 21331 

Invalid function key pressed 14202 

Invalid function passed to CM System function 1349 

Invalid generic key length 20315 




Invalid I/O operation; GETREC returned EOF 50706 

Invalid instance or list index in SQL string 20467 

Invalid instance reference; method was sent to a class 1217 

Invalid integer format 26338 

Invalid KB version specification 51153 

Invalid KB version specification 51153 

Invalid key specifications 50306 

Invalid Knowledge Base ID 51155 

Invalid knowledge base name; exceeds 8 characters 28804 

Invalid knowledge base name; invalid character 28803 

Invalid knowledge base version 28802 

Invalid LIBCALL token list 46722 

Invalid logical record length 21337 

Invalid message mode; "ON", "OFF", "CODE", and "TEXT" are valid 34315 

Invalid name string (row %1/col %2) 50035 

Invalid number 13509 

Invalid number 34301 

Invalid numeric format 26339 

Invalid object (host variable) in SQL string 20461 

Invalid object base type in SQL string 20464 

Invalid object ID 51154 

Invalid object type MESSAGE, PARAMETER, or SLOT expected (row 

%1/col %2) 

2779 

Invalid object_pointer value 58110 

Invalid OPENFILE option string 20302 

Invalid OPENFILE request; duplicate record name specified 50709 

Invalid option for WIN_statement (row %1/col %2) 2794


Invalid or missing WINLIB; file not found 28859 

Invalid path specification (row %1/col %2) 50113 

Invalid Pie Labels; labels list empty or invalid 33237 

Invalid placement of Thousands-Separator 540 

Invalid pointer value 1345 

Invalid pointer value 22600 

Invalid program exit options 46720 

Invalid PUTREC mode given 32713 

Invalid record field or slot in SQL string 20463 

Invalid record I/O get mode given 50703 

Invalid record I/O open mode given 20303 

Invalid record I/O open mode given 32705 

Invalid record I/O option string given 20302 



Invalid record number 20346 

Invalid record number 32533 

Invalid record selection string given 32707 

Invalid remote SQL interface; valid values are "IBM" and "DB2" 20419 

Invalid row for selection 26322 

Invalid row or column value passed to CM SetCursor function 1351 

Invalid screen attribute setting; use "G", "C", "H", or "X" 34330 

Invalid segment name (0 or greater than 8 characters) 20380 

Invalid selection character 26328 

Invalid slot instance integer value 13499 

Invalid SQL interface; valid values are "DB2", "Oracle" and "DBC/1012" 20412 




Invalid SQL interface; valid values are "IBM", "Oracle", "Sybase", and 

"ODBC" 

20412 

Invalid SQL interface; valid values are "Oracle" and "Sybase" 20412 

Invalid SQL interface; valid values are "SQL/DS", "Oracle" and 

"DBC/1012" 

20412 

Invalid statement; use Send Up instead (row %1/col%2) 2795 

Invalid stored answer file format 692 

Invalid swapper threshold 34316 

Invalid switch value; valid values are "ON" and "OFF" 34303 

Invalid time format 26341 

Invalid time mask 34313 

Invalid trace level; value must be between 0 and 3 34306 

Invalid trace level; value must be between 0 and 4 34306 

Invalid user interface; valid values are "GRAPHICAL" and 

"CHARACTER" 

34322 

Invalid value 34302 

Invalid value-can-change setting; "TRUE", "FALSE" and "TRUE/ASK" 

are valid 

34319 

Invalid variable record length; not within AionDS record length 20204 

Invalid window handle passed to CM Function 1364 

Invalid window size/position passed to CM function 1347 

Invalid window type passed to CM function 1352 

Invalid window type passed to CM GetWindow function 1348 

Invalid x-Data; ranges overlap 33234 

Invalid yes/no value 26337 

It is not possible to read from specified dataset type 21310 

It is not possible to read from specified file type 21310 

It is not possible to write to specified dataset type 21311


It is not possible to write to specified file type 21311 

KB property is read only 28824 

Key fields must be of the same type (row %1/col %2) 50109 

Knowledge base %1%2 v%3 is in use 28854 

Knowledge base %1%2 v%3 not found 28850 

Knowledge base (ENQ) failure 21350 

Knowledge base end-access (DEQ) failure 21352 

Knowledge base string file mode switch failed 28810 

Left hand side of power (**) function must be positive 2107 

Left Margin is greater than Right Margin 1115 

Left Margin is less than 1 22505 

Legend length inconsistent with number of data elements 33236 

Length of set or list is inconsistent with size constraint 26327 

Length of string exceeds size constraint 26326 

LINK to external program failed 46782 

List index is out-of-bounds 1006 

List index out-of-bounds 20468 

List truncated 20114 

Load module library could not be opened 46780 

Local ADSAPI receiver died 19219 

LU6.2 session error - Invalid local LU name 20563 

LU6.2 session error - Invalid LOGON MODE 20562 

LU6.2 session error - Invalid system name 20561 

LU6.2 session error - Null message returned 20515 

LU6.2 session error - RECEIVE failed 20548 

LU6.2 session error - SEND failed 20547 




LU6.2 session error - session ALLOCATION failed 20546 

LU6.2 session error - unexpected message type 20503 

LU6.2 session error - unexpected request type 20504 

Maximum Scale Value too small 1214 

Member not found 21304 

Member specification not allowed 20300 

Memo length cannot exceed 32K bytes 32743 

Menu item parent must be StandardWindow or MenuItem 51851 

Menu item parent must have the MIS_SUBMENU style 51852 

Menu items with the MIS_SUBMENU style cannot have a shortcut key 51854 

Message display not available for %1 (%2) 5005 

Message or block too long; truncated 1116 

Method must be sent to an instance 1502 

Minimum Scale Value too large 1215 

Missing command or argument 13501 

Missing data elements 1204 

Missing option keyword 2904 

Monitor processing suppressed 4881 

Must be an instance of class DialogBox (or subclass) 2702 

Must specify a knowledge base name 28801 

Must specify member of the partitioned dataset 21325 

NAME clause not found (row %1/col %2) 50034 

Negative value in stacked or surface graph 33232 

Negative values not supported for Scroll Bar ranges 1429 

New constraint inconsistent with existing constraint 1003 

No command line associated with the current display 26378


No current instance for slot or method, or non-unique instance name 22592 

No date mask is specified 16003 

No Explain text available 51846 

No explain window associated with current object 26370 

No further information is available 26330 

No input window associated with the current display 26396 

No knowledge bases found - %1 28853 

No matching objects 26364 

No objects window associated with the current display 26397 

No options window associated with the current display 26379 

No parent ADSAPI session found 19221 

No questions have been answered 26329 

No questions which have been answered are allowed to be backed up to 26398 

No space in partitioned dataset directory 21327 

No time mask is specified 16004 

Non-unique instance name used in TSL 22593 

Non-zero process completion code 4813 

None found 51111 

Not supported 51158 

Number of SQL arguments is inconsistent with the SQL request 20460 

Number of SQL columns returned do not match the columns for the 

parameter 

37366 

Number of SQL columns selected not compatible with target parameter 20404 

Object %1 is unprocessed 51109 

Object not a list/set or class in SQL string 20466 

Object not a record or instance in SQL string 20465 

Object not in ADSAPI shared heap 19222 




Object reference expected: type(contextname(objectname)) (row %1/col 

%2) 

12019 

Object referenced in CM function is non-simple and can’t be sourced 1359 

Object_pointer out of scope 58111 

Objects are from two different KBs 51157 

Only one item may be selected 26368 

Open failed for report output file 1117 

OpenApp may not be sent while an Application Window or Modal Dialog 

is open 

1406 

Operation attempted on an unprepeared SQL Cursor 37367 

Operation attempted on an unopened SQL cursor 20402 

Option supported only for currently sourced objects 42512 

Overlapping fields (row %1/col %2) 50039 

Packed size exceeds 16 20124 

Packed size too small 20104 

Parameter list inconsistent with LIBCALL token list 46721 

Parent context must be visible for import 13212 

Parent file variable is not open 20202 

Partial match on index key 32733 

Passed ‘%’ to function when already past the last element of list, set or 22510 

Passwords are write only 28825 

Path not found 21306 

Pointer type mismatch (row %1/col %2) 12018 

Positive integer expected (row %1/col %2) 50032 

Precision is negative 20122 

Problem advancing record pointer 32715 

Problem occurred updating %1 32805


Problem reading from memo file 32742 

Problem writing to memo file 32731 

Procedural Interface not supported 37364 

Process %1 %2; boolean expected 4805 

Process %1 %2; integer expected 4804 

Process %1 %2; parameter missing or value unknown 4802 

Process %1 %2; string expected 4801 

Process %1 %2; string too long 4803 

Process aborted due to hard error 21314 

Process aborted due to trap fault 21315 

Process killed 21316 

Profile string must have the form " = " 34308 

Profile string truncated 34307 

PUTREC data argument is unknown 980 

QSAM I/O operation failed 20320 

QSAM record length modification not allowed for UPDATE 20317 

Real number has too many digits; use exponential notation (%param:width) 22576 

Real number overflow (number cannot be represented by AionDS) 2101 

Real size must be 4 or 8 20127 

Record is locked by another process 32510 

Record length exceeds data length 20120 

Record must first be retrieved for UPDATE 20308 



Recursive call to an independent state 14108 

Referenced object is unknown or invalid 13481 




Referenced object is unknown, private or invalid 1344 

Remote Connect/KB control parameter has incorrect type definition 4830 

Remote MRO file requires specific VSAM type 20370 

Remote process object not supported 20512 

Remote VSAM CLOSE request failed 20351 

Remote VSAM ERASE request failed 20354 

Remote VSAM GET request failed 20352 

Remote VSAM GET returned DUPKEY condition 20359 

Remote VSAM OPEN request failed 20350 

Remote VSAM PUT request failed 20353 

Remote VSAM SELECT request failed 20355 

Remote VSAM UNLOCK request failed 20369 

Requested object is not explainable 42515 

Requested space not available 21337 

Required Window or DDE slot value is unknown - %1 1503 

Rerun file not found 28821 

Retrieved record with incorrect record length 20301 

Retry access? 32526 

Right Margin is larger than Line Length 22559 

Right Margin is larger than window width 22563 

RKB error - Bad HPO name 20511 

RKB error - Error starting remote knowledge base 20509 

RKB error - Remote consultation start failed 20508 

RKB error - Remote KB attempted to display a user message 20516 

RKB error - Unexpected error terminating remote consultation 20510 

SAESGET - unexpected VTAM link protocol error 20504


SAESGET VTAM link protocol error - unexpected message type. 20503 

SAESGET VTAM link receive failed 20502 

SAESSEND VTAM link send failed 20501 

Saved form of %1%2 v%3 not found 28805 

Screen/instance is only valid if all slots are specialized 42859 

Segment not found (row %1/col %2) 50030 

Segment not open for retrieving records 20382 

Segment not open for updating records 20383 

Segment not open for writing records 20384 

SELECT function argument is unknown 981 

SELECT key value argument is unknown 982 

Select mode cannot be LASTREC or BACKWARD 32740 

Selection criteria must be established for SQL cursor 20401 

Send Up may not be used in a title or footer 22591 

Set can only have one element when certainty 1.0 exists 26336 

Set may not have duplicate elements 26335 

SetText illegal on a graphic pushbutton 1411 

Severe Error -- Attempt to Continue? 7305 

Sharing violation: file already in use 21311 

Sharing violation: file already in use 32717 

Sharing violation: record already in use 32716 

SHOW-PROGRAM processing did not complete 5001 

Size is zero or negative 20121 

Size of SQL data returned exceeds AionDS limit 20411 

Skipped unspecializing object because information would be lost 12254 

Sorted-export and 600-export are incompatible flags 34323 




Specified dataset cannot be deleted 21312 

Specified dataset is not allocated 21314 

Specified dataset is not partitioned 21324 

Specified filename has not been FILEDEF’d 21314 

Specify space as (,(,,)) 34333 

SQL “close cursor” failed 37379 

SQL “describe cursor” failed 37375 

SQL “prepare cursor” failed 37365 

SQL "fetch" attempted at end-of-file 20400 

SQL "fetch" operation failed 20408 

SQL "open cursor" failed 20406 

SQL "request" operation failed 20409 

SQL "select" operation failed 20407 

SQL access string is inconsistent with SQL interface 20414 

SQL column type does not match a slot/record-member type 37368 

SQL data is invalid %1 20432 

SQL data type is incompatible with target parameter %1 20431 

SQL database name missing or too long 20413 

SQL Disconnect failed 37373 

SQL Feature is not supported 37370 

SQL string is unknown 983 

SQL Transaction (Commit or Rollback) failed 37374 

SQL/DS database machine name greater than 8 characters 20413 

SQL: unexpected sqlcode from %1: %2 37377 

START clause not found (row %1/col %2) 50038 

State with invalid objects was entered 1011


Static instance does not exist 20469 

String not found 2001 

String truncated 20100 

Subheader too long 1207 

Sum of data elements in Pie Graph equals 0 33238 

SYSLIN dataset disposition must be new or old 51096 

Table not found or invalid 50301 

Target ADSAPI session is dead 19217 

Temporary restriction: cannot SetParent of an open StandardWindow 1499 

Textual field truncated 20107 

The data does not match the input mask 26373 

The DLL is in an unrecognizable format 37358 

The implementation of AionDS being executed does not support graphs 33239 

The knowledge base contains invalid objects 51005 

The knowledge base contains more than 65536 models 51053 

The knowledge base contains more than 65536 symbols 51050 

The names of the knowledge base symbols total more than 1,703,910 bytes 51051 

The OTHERSOURCES command is not valid here 42511 

The property %1 can’t be represented as boolean 51106 

The property %1 can’t be represented as integer 51107 

The property %1 can’t be represented as real 51108 

The property can’t be represented in this type 51110 

The requested I/O operation requires a key 20366 

The SELECT format used is valid only for READ mode 20365 

The SQL Cursor Interface is not supported 37363 

The SQL Data Dictionary Interface is not supported 37362 




The SQL Standard Interface is not supported 37361 

The SQL Syntax Interface is not supported 37371 

The table’s title takes more lines than are available per page 22581 

The WHAT command is not valid here 42510 

There are no parameters or slots available for the WHAT command 42519 

There are no parameters or slots available for the WHY command 42518 

This command not allowed inside a title or footer 22536 

This will terminate your application program 28829 

Too few elements to graph 1202 

Too many elements to graph 1203 

Too many files on disk 21317 

Too many open files (increase FILES parameter in CONFIG.SYS) 21307 

Too many option keywords specified 2905 

Too many unique string constants in a context 51004 

Top Margin + Bottom Margin is greater than or equal to Page Length 22562 

Top Margin is less than 0 22560 

Total # of columns are greater than 64K 37376 

Trace is not enabled 51842 

Trace is not enabled or an output error occurred 26334 

TYPE clause not found (row %1/col %2) 50036 

Unable to add element to list/set (row %1/col %2) 12011 

Unable to assign value to parameter or instance slot (row %1/col %2) 12012 

Unable to backup 26331 

Unable to complete the agenda; it references an unprocessed parameter 1019 

Unable to create database: path not found or file already exists 50103 

Unable to create definition - table or columns not found 50304


Unable to create index: path not found or file already exists 50104 

Unable to create the save file 51052 

Unable to evaluate entry conditions 1016 

Unable to gain access to the clipboard 2015 

Unable to get procedure address for LIBCALL 46724 

Unable to load ADSAPI server 19203 

Unable to load ADSAPI.DLL (may be missing or incorrect version) 19298 

Unable to load dynamic link library for LIBCALL 46723 

Unable to load local static SQL access module 37380 

Unable to load remote static SQL access module 37381 

Unable to load support library for dBASE (ADSDB4DB.DLL) 32741 

Unable to load support library for IBM Database Manager 20415 

Unable to load support library for IBM Database Manager 37350 

Unable to load support library for Informix Server 37347 

Unable to load support library for Microsoft ODBC 37352 

Unable to load support library for Microsoft SQL Server 6.0 37346 

Unable to load support library for Microsoft/Sybase SQL Server 20418 

Unable to load support library for Microsoft/Sybase SQL Server 37349 

Unable to load support library for Oracle 20416 

Unable to load support library for Oracle 37351 

Unable to load support library for remote functions (MAES.DLL) 20581 

Unable to load support library for VAX Rdb/VMS 20417 

Unable to load support module for dBASE (ADSDB4DB.EXE) 32744 

Unable to load VSAM data using key; KSDS or ESDS path expected 32808 

Unable to lock foreground screen 1221 

Unable to open database file 50101 




Unable to open file 21332 

Unable to open index file 50102 

Unable to open/read rerun file 28822 

Unable to open/read rerun file 28822 

Unable to PUT integer 20113 

Unable to PUT real in 4 bytes 20102 

Unable to resolve all the function addresses in the DLL 37357 

Unable to set User-password; Owner-password does not exist 28630 

Unable to update all the modified instances 32803 

Unable to update instance using VSAM access method; no key field 

specified 

32809 

Unable to update instance; record not found 32810 

Unable to update new instances using QSAM access method 32807 

Unbalanced string delimiter 13514 

Unexpected C/370 runtime error occurred (return code = ‘%4’) 21300 

Unexpected CMS file processing error (completion code ‘%5’) 21328 

Unexpected OS return code 21300 

Unexpected symbol; ‘(‘ expected (row %1/col %2) 12008 

Unexpected symbol; ‘)’ expected (row %1/col %2) 12010 

Unexpected symbol; ‘,’ expected (row %1/col %2) 12009 

Unexpected symbol; boolean expected (row %1/col %2) 12004 

Unexpected symbol; certainty expected (row %1/col %2) 12007 

Unexpected symbol; date expected (row %1/col %2) 12013 

Unexpected symbol; end of input expected (row %1/col %2) 12015 

Unexpected symbol; integer expected (row %1/col %2) 12005 

Unexpected symbol; number expected (row %1/col %2) 12002 

Unexpected symbol; string expected (row %1/col %2) 12003


Unexpected symbol; time expected (row %1/col %2) 12006 

Unexpected VSAM MODRPL request failure 20336 

Unknown argument to ADS function: %1 1372 

Unknown Database found 37359 

Unknown field type 51105 

Unknown identifier in SQL string 20462 

UNKNOWN is not valid here 26321 

Unknown KB property 51104 

Unknown keyboard function 34310 

Unknown object type 51103 

Unknown option keyword 2902 

Unknown or invalid instance name used 1339 

Unknown profile keyword 34309 

Unknown property 51101 

Unknown SQL interface encountered 37372 

Unknown SQL type cannot be mapped 37369 

Unknown, invalid or private slot referenced 1340 

Unmatched delimiter 2014 

Unrecognized keyword 13502 

Unrecognized or unsupported KDL statement; import KB with High- 

Performance ON 

51002 

Unsupported process routine 4810 

Unsupported radix specified in call to STR function 953 

User exit requested percolation 4880 

User exit requested percolation 5010 

User Function is invalid 1338 




User interface is GRAPHICAL, but KB doesn’t include WINLIB; re-import 

KB 

1404 

User interface must be GRAPHICAL to issue graphical calls 1405 

User is not authorized to define datasets 21320 

User sourcing not available for %1 (%2) 5004 

Value not encodable by STR function 954 

View not found or invalid 50302 

VSAM CLOSE request failed 20331 

VSAM ERASE request failed 20334 

VSAM GET request failed 20332 

VSAM not positioned for I/O operation 20344 

VSAM OPEN request failed 20330 

VSAM POINT request failed 20335 

VSAM PUT request failed 20333 

VTAM error occurred processing a report 20500 

Window Library slots cannot be modified directly, use Library Methods 3358 

Window text too long 2003 

Windowing system return code - unable to set the parent of %1 1426 

X-Data not allowed in multiple element, side by side bar chart 33233 

X-size too small 1200 

Y-size too small 1201 

Zoned size exceeds 65512 20125 

Zoned size too small 20103

Table for converting error codes 


.........................................................................................................................................................................................................˝.......................................... 

Overview 

When the ERROR-MESSAGE profile option is set to ON or CODE, 

AionDS includes the error code in the error message text. The error code is 

actually the number of the message in the AionDS system message file. In 

most cases, the message number serves as the error code that is reported to the 

application through the AES_ERRORNUM parameter. 

For some runtime errors; however, the error code stored in 

AES_ERRORNUM is not the same as the number of the message in the 

system message file. Over time, the message number of some messages have 

changed. To provide upward compatibility for applications that are trapping 

and processing these errors using AES_ERRORNUM, AionDS converts the 

message numbers to the documented error codes. 

The explanations in this manual are based on the error codes stored in 

AES_ERRORNUM. If you specify the ERROR-MESSAGE profile option 

as ON or CODE, you can determine whether the error code included in the 

message text is the documented error code using either of the following 

methods: 

■ Using the message text, determine the error code from the table in the 

previous section. 

■ Using the table shown below, check to see if the code included in the 

message text (MSG) is different from the actual documented error code 

(ERR). 

MSG code ERR 

code 

Message 

1301 950 Argument to AES function missing or unknown 

1302 951 Invalid attempt to add elements to a list/set 

1303 954 Value not encodable by STR function 

1304 953 Unsupported radix specified in call to STR function 

1305 960 Certainty out of legal range (-1.0



1306 970 Attempted to use invalid date or time value 

1307 980 PUTREC data argument is unknown 

1308 981 SELECT function argument is unknown 

1309 982 SELECT key value argument is unknown 

1310 1000 Illegal assignment 

1313 1003 New constraint inconsistent with existing constraint 

1314 1004 Assignment inconsistent with existing constraint 

1315 1005 Invalid argument passed to the NUM function 

1316 1006 List index is out-of-bounds 

1317 1007 Invalid argument passed to the HEX function 

1318 1008 Invalid argument passed to the BIN function 

1319 1010 Circular reasoning was detected 

1322 1017 Invalid argument passed to the DATE function 

1323 1018 Invalid argument passed to the TIME function 

1325 2100 Division by zero 

1326 2101 Real number overflow (number cannot be represented by 

AionDS) 

1327 2104 Argument to SQRT function is negative 

1328 2105 Argument to LN function is less than or equal to zero 

1329 2106 Argument to TRUNC or ROUND function is too large 

1330 2107 Left hand side of power (**) function must be positive 

1331 2201 Integer overflow (value cannot be represented by an integer) 

9601 692 Invalid stored answer file format 

12014 1012 Incorrect data format encountered in External Data file 

14101 1011 State with invalid objects was entered 

14102 1016 Unable to evaluate entry conditions


14103 1019 Unable to complete the agenda; it references an unprocessed 

parameter 

14104 1001 Error passing parameters into the state 

14105 1002 Error returning parameters from the state 

22516 1115 Left Margin is greater than Right Margin 

22518 1116 Message or block too long; truncated 

22520 1117 Open failed for report output file 

28852 28808 %1%2 v%3 cannot be loaded; saved form is incompatible 

32500 20300 Member specification not allowed (MVS/VM) 

32501 20300 File not found (PC/WIN/OS2/PM/SUN/AIX) 

32501 20301 Dataset record length inconsistent with type definition (MVS) 

32501 20301 File record length inconsistent with type definition (VM) 

32502 20301 Retrieved record with incorrect record length 

(PC/WIN/OS2/PM/SUN/AIX) 

32502 20302 Invalid record I/O option string given (MVS/VM) 

32503 20302 Invalid record I/O option string given 


32503 20303 Invalid record I/O open mode given (MVS/VM) 

32504 20303 Invalid record I/O open mode given 


32504 20304 Dataset not open for reading records (MVS) 

32504 20304 File not open for reading records (VM) 

32505 20304 File not open for reading records(PC/WIN/OS2/PM/SUN/AIX) 

32505 20305 Dataset not open for writing records (MVS) 

32505 20305 File not open for writing records (VM) 

32506 20305 File not open for writing records (PC/WIN/OS2/PM/SUN/AIX) 

32506 20306 File not open for updating records (MVS) 

32506 20306 File not open for updating records (VM) 




32507 20306 File not open for updating 

records(PC/WIN/OS2/PM/SUN/AIX) 

32507 20307 Dataset not open for adding records (MVS) 

32507 20307 File not open for adding records (VM) 

32508 20307 GETREC called at end-of-file(PC/WIN/OS2/PM/SUN/AIX) 

32508 20308 GETREC called at end-of-file (MVS/VM) 

32509 20308 Record must first be retrieved for 

UPDATE(PC/WIN/OS2/PM/SUN/AIX) 

32509 20309 Record must first be retrieved for UPDATE (MVS/VM) 

32510 20310 Invalid dataset type/organization 

32512 20312 I/O Operation not supported for this dataset type (MVS) 

32512 20312 I/O Operation not supported for this file type (VM) 

32517 20317 QSAM record length modification not allowed for UPDATE 

32520 20320 QSAM I/O operation failed 

32530 20330 VSAM OPEN request failed 

32531 20331 VSAM CLOSE request failed 

32532 20332 VSAM GET request failed 

32533 20333 VSAM PUT request failed 

32534 20334 VSAM ERASE request failed 

32535 20335 VSAM POINT request failed 

32536 20336 Unexpected VSAM MODRPL request failure 

32544 20344 VSAM not positioned for I/O operation 

32545 20345 Attempt to change prime key or key of reference 

32546 20346 Invalid record number 

32550 20350 Remote VSAM OPEN request failed 

32551 20351 Remote VSAM CLOSE request failed 

32552 20352 Remote VSAM GET request failed

32553 20353 Remote VSAM PUT request failed 

32554 20354 Remote VSAM ERASE request failed 


32555 20355 Remote VSAM SELECT request failed 

32556 20356 Remote VSAM GET request failed 

32565 20365 The SELECT format used is valid only for READ mode 

32566 20366 The requested I/O operation requires a key 

32568 20368 File is not open and/or unenabled 

32569 20369 Remote VSAM UNLOCK request failed 

32570 20370 Remote MRO file requires specific VSAM type 

32601 20100 String truncated 

32602 20101 Fixed-point overflows 

32603 20102 Unable to PUT real in 4 bytes 

32604 20103 Zoned size too small 

32605 20104 Packed size too small 

32606 20105 Bad packed-decimal format 

32607 20106 Bad zoned-decimal format 

32608 20107 Textual field truncated 

32609 20108 Bad time format 

32610 20109 Bad date format 

32611 20110 Bad integer format 

32612 20111 Bad real number format 

32613 20112 Bad boolean value format 

32614 20113 Unable to PUT integer 

32615 20114 List truncated 

32620 20120 Record length exceeds data length 

32621 20121 Size is zero or negative 




32622 20122 Precision is negative 

32623 20123 Bad integer size 

32624 20124 Packed size exceeds 16 

32625 20125 Zoned size exceeds 65512 

32626 20126 Fixed size must be 2 or 4 

32627 20127 Real size must be 4 or 8 

33201 1200 X-size too small 

33202 1201 Y-size too small 

33203 1202 Too few elements to graph 

33204 1203 Too many elements to graph 

33205 1204 Missing data elements 

33206 1205 Data lengths are inconsistent with label lengths 

33207 1210 GRAPHICS-DRIVER table not found or invalid (PC/OS2) 

33207 1206 Header too long (MVS/VM) 

33208 1216 Graphics adapter incompatible with GRAPHICS-DRIVER 

table (PC/OS2) 

33208 1207 Subheader too long (MVS/VM) 

33210 1213 Data lengths are inconsistent 

33211 1214 Maximum Scale Value too small 

33212 1215 Minimum Scale Value too large 

33213 1217 Invalid instance reference; method was sent to a class 

33214 1218 Graphics library (ADSGM6.DLL) not found on LIBPATH 

(OS2) 

33214 1211 Display terminal does not support graphics (MVS/VM) 

33215 1219 I/O privilege not configured (add IOPL=YES to CONFIG.SYS) 

33216 1220 Graphics subsystem received unexpected OS return code 

33217 1221 Unable to lock foreground screen


34701 20200 File is not open (PC/WIN/OS2/PM/SUN/AIX/VM) 

34701 20200 Dataset is not open (MVS) 

34702 20302 Invalid OPENFILE option string 

34703 20311 I/O operation not supported by access method 

34704 20203 Invalid field or variable name 

34705 20201 Invalid field specified for keyed selection 

34706 20202 Parent file variable is not open 

34707 20204 Invalid variable record length; not within AionDS record length 

35500 20380 Invalid segment name (0 or greater than 8 characters) 

35501 20381 Invalid database name (0 or greater than 8 characters) 

35502 20382 Segment not open for retrieving records 

35503 20383 Segment not open for updating records 

35504 20384 Segment not open for writing records 

35505 20385 I/O operation invalid; GETREC-UPDATE returned EOF 

35506 20390 DL/I GET request failed 

35507 20391 DL/I PUT request failed 

35508 20392 DL/I DELETE request failed 

35509 20393 DL/I request failed - unknown database name 

35510 20394 DL/I request failed - number of SSA’s exceeds 16 

35511 20395 DL/I request failed - DL/I database not open 

35512 20396 CICS/VS could not access database (not in FCT or unopened) 

35513 20397 CICS/VS rejected request - DL/I is not active 

35514 20504 SAESGET - unexpected VTAM link protocol error 

35515 20398 DL/I request failed - invalid PSB 

35516 20399 DL/I request failed - invalid request 

35517 20386 DL/I request failed - invalid PSB address 




35518 20387 DL/I request failed - DL/I scheduling conflict 

35519 20388 DL/I request failed - DL/I task not authorized 

35520 20389 DL/I request failed - PSB already scheduled 

35521 20373 DL/I request failed - DL/I language conflict 

35522 20374 DL/I request failed - PSB initialization failed 

35523 20375 DL/I request failed - PSB not authorized 

35524 20376 DL/I request failed - DL/I unscheduled termination 

35525 20377 DL/I request failed - DL/I function unscheduled 

35526 20378 DL/I request failed - DL/I UIBFCTR unknown 

35527 20379 DL/I request failed - DL/I UIBDLTR unknown 

37301 20460 Number of SQL arguments is inconsistent with the SQL 

request 

37302 20461 Invalid object (host variable) in SQL string 

37303 20462 Unknown identifier in SQL string 

37304 20463 Invalid record field or slot in SQL string 

37305 20464 Invalid object base type in SQL string 

37306 20465 Object not a record or instance in SQL string 

37307 20466 Object not a list/set or class in SQL string 

37308 20467 Invalid instance or list index in SQL string 

37309 20468 List index out-of-bounds 

37310 983 SQL string is unknown 

37311 20469 Static instance does not exist 

37312 20470 Invalid file parameter or class in SQL string 

37320 20431 SQL data type is incompatible with target parameter %1 

37321 20432 SQL data is invalid %1 

37322 20400 SQL "fetch" attempted at end-of-file 

37323 20401 Selection criteria must be established for SQL cursor


37324 20402 Operation attempted on an unopened SQL cursor 

37325 20403 All SQL cursors are currently in use 

37326 20404 Number of SQL columns selected not compatible with target 

parameter 

37328 20406 SQL "open cursor" failed 

37329 20407 SQL "select" operation failed 

37330 20408 SQL "fetch" operation failed 

37331 20409 SQL "request" operation failed 

37332 20410 A SQL database connection cannot be established 

37340 20411 Size of SQL data returned exceeds AionDS limit 

37343 20412 Invalid SQL interface; valid values are "IBM", "Oracle", 

"Sybase", and "ODBC" (PC/WIN/OS2/PM) 

37343 20412 Invalid SQL interface; valid values are "DB2", "Oracle" and 

"DBC/1012" (MVS) 

37343 20412 Invalid SQL interface; valid values are "SQL/DS", "Oracle" and 

"DBC/1012" (VM) 

37343 20412 Invalid SQL interface; valid values are "Oracle" and "Sybase" 

(SUN/AIX) 

37344 20413 SQL database name missing or too long 


37344 20413 DB2 subsystem name missing or greater than 4 characters 

(MVS) 

37344 20413 SQL/DS database machine name greater than 8 characters 

(VM) 

37345 20414 SQL access string is inconsistent with SQL interface 

37346 20415 DBC/1012 tdpid greater than 4 characters (MVS) 

37346 20415 DBC/1012 tdpid greater than 8 characters (VM) 

37347 20416 Aion Database Interface for DBC/1012 not installed (MVS) 




37347 20419 Invalid remote SQL interface; valid values are "IBM" and 

"DB2" (WIN/OS2/PM) 

37348 20417 Unable to load support library for VAX Rdb/VMS 

37349 20418 Unable to load support library for Microsoft/Sybase SQL Server 

37350 20415 Unable to load support library for IBM Database Manager 

37351 20416 Unable to load support library for Oracle 

46441 20311 I/O operation not supported by access method 

46442 20310 I/O operation not supported for this dataset type 

46443 20313 Incorrect key location 

46444 20314 Incorrect key length 

46445 20315 Invalid generic key length 

46450 20350 Remote VSAM OPEN request failed 

46451 20351 Remote VSAM CLOSE request failed 

46452 20352 Remote VSAM GET request failed 

46453 20353 Remote VSAM PUT request failed 

46454 20354 Remote VSAM ERASE request failed 

46455 20355 Remote VSAM SELECT request failed 

46456 20359 Remote VSAM GET returned DUPKEY condition 

46465 20365 The SELECT format used is valid only for READ mode 

46466 20366 The requested I/O operation requires a key 

46468 20368 File is not open and/or unenabled 

46469 20369 Remote VSAM UNLOCK request failed 

46470 20370 Remote MRO file requires specific VSAM type

AionDS runtime errors 


.........................................................................................................................................................................................................˝.......................................... 

Overview 

This section explains the runtime error messages that are issued by AionDS, 

HPO, ADSAPI, AAPI/CICS and AAPI/IMS. Error messages issued by the 

AionDS/CICS and AionDS/IMS transaction drivers, as well as MAES, are 

not included in this chapter. 

For more information: See “How to Use This Manual” for information 

about where to find these messages. 

The errors are listed by error code in ascending order. For more information 

about determining the correct error code, see the previous section. 

In IMS, some error codes may include a 2-digit prefix. This prefix is a 

VTAM error code described in the section “IMS and TSO transaction driver 

messages” in Chapter 2. 

Caution: Some message codes use the same number as another message’s 

error code. This can cause confusion if you look for the message under the 

message code instead of the error code. If the message description seems 

inappropriate for your situation, check the numbers in the section “Table for 

converting error codes” on page 1-37. 

.........................................................................................................................................................................................................˝.......................................... 

540 

Invalid placement of Thousands-Separator 

This is a data validation error. The user entered a numeric value incorrectly. 

For example: 12,00 should be 1,200. 

.........................................................................................................................................................................................................˝.......................................... 

692 

Invalid stored answer file format 

The format of the file is incorrect. AionDS does not run the consultation. 

Check the specified file to make sure that it’s an AionDS stored answer file. 



.........................................................................................................................................................................................................˝.......................................... 

950 


Argument to AES function missing or unknown 

One of the arguments to the AES function is missing or unknown. If the 

user chooses to abort, the consultation is terminated immediately. If the user 

does not choose to abort, the AES statement is skipped and AionDS 

continues executing the KDL property. 

Note: If the knowledge base has been optimized using HPO, this error is not 

reported and the AES function is not executed. 

.........................................................................................................................................................................................................˝.......................................... 

951 

Invalid attempt to add elements to a list/set 

An attempt was made to add elements to a set or list that was already marked 

processed. For instance, a value was assigned in the parameter’s Facts 

property and an external process attempted to add values. 

.........................................................................................................................................................................................................˝.......................................... 

953 

Unsupported radix specified in call to STR function 

The base (radix) for the string is not 10, 16, or 2. These are the only valid 

bases. Check the arguments to the function. 

If the user chooses to abort, the consultation is terminated immediately. If 

the user does not choose to abort, AionDS continues executing the KDL 

property using the value UNKNOWN for the STR function. 

.........................................................................................................................................................................................................˝.......................................... 

954 

Value not encodable by STR function 

Either the data to encode is too large or the width is too small. Check the 

arguments to the STR function. 

.........................................................................................................................................................................................................˝.......................................... 

960 

Certainty out of legal range (-1.0




property using the value UNKNOWN for the CF function. 

.........................................................................................................................................................................................................˝.......................................... 

970 

Attempted to use invalid date or time value 

Dates and time values entered must be valid. The months must be one of the 

twelve months; days can only be from 1 to 31; years must be within the range 

of 1900 -1999. 

Time values must be from 0 - 24 in AM/PM or 24 hour format. For 

example, 2500 hrs or 34:00 PM are not valid times. 


reported and the illegal assignment is allowed. 

.........................................................................................................................................................................................................˝.......................................... 

980 

PUTREC data argument is unknown 

The record parameter is undefined in a KDL PUTREC statement. 


reported and the PUTREC statement is not executed. 

.........................................................................................................................................................................................................˝.......................................... 

981 

SELECT function argument is unknown 

The record number parameter in the KDL SELECT statement does not 

evaluate to a valid record number. 


reported and the SELECT statement is not executed. 

.........................................................................................................................................................................................................˝.......................................... 

982 

SELECT key value argument is unknown 

The parameter used as a key value is UNKNOWN. Check the use of the 

parameter. 



.........................................................................................................................................................................................................˝.......................................... 

983 


SQL string is unknown 

The first argument to the KDL SQL statement contains a parameter that is 

UNKNOWN. Check the use of the parameter. 

.........................................................................................................................................................................................................˝.......................................... 

1000 

Illegal assignment 

At edit time, this error is reported when the user tries to use the “(*)” syntax 

to assign to all elements of a list; for example, 

(*) is 'red' 

At runtime, this error can occur under the following circumstances: 

■ when an invalid assignment is made to a list element, such as assigning a 

value to list element that is not defined within a function; for example, 

list_pa(j) is 5 /*illegal when j is unknown*/ 

■ when an assignment is made to a file parameter and the file is not open; 

for example, 

file_pa->.field is 10 /*fails if file_pa is not open*/ 


reported and the assignment is ignored. 

.........................................................................................................................................................................................................˝.......................................... 

1001 

Error passing parameters into the state 

When passing parameters into a state, AionDS performs an assignment of the 

arguments to the state’s input parameters. This error is reported if the 

assignment cannot be performed because the input parameter already has a 

value (in the Facts property), or because of a type inconsistency. 

The assignment is ignored. If the input parameter already has a value, the 

value is unchanged. If the input parameter does not have a value, its value 

remains UNKNOWN. All other parameter passing is completed normally. 

Be sure the input parameter and the argument are of the same type (and not 

just compatible ones). For instance, making one of them an integer and the


other a positive integer (“>0”) is acceptable for the type checker, but it will 

produce problems if the argument evaluates to a negative integer. Avoid 

giving a value in the Facts property of the input parameter unless the 

parameter is a Value Can Change parameter. 


reported and the assignment is allowed. 

.........................................................................................................................................................................................................˝.......................................... 

1002 

Error returning parameters from the state 

When returning parameters from a state, AionDS performs an assignment of 

the state’s output parameters to the proper argument parameters. This error 

is reported if the assignment cannot be performed because the proper 

argument already has a value, or because of a type inconsistency. 

The assignment is ignored. If the argument parameter already has a value, 

the value is unchanged. If the argument parameter does not have a value, its 

value remains UNKNOWN. All other parameter passing is completed 

normally. 

Be sure the output parameter and the argument are of the same type (and not 

just compatible ones). For instance, making one of them an integer and the 

other a positive integer (“>0”) is acceptable for the type checker, but it will 

produce problems if the output parameter evaluates to a negative integer. 

The argument parameter should not have a value before the STATE step 

unless it is a Value Can Change parameter. 


reported and the assignment is allowed. 

.........................................................................................................................................................................................................˝.......................................... 

1003 

New constraint inconsistent with existing constraint 

A constraint operation is not consistent with the previous constraints on the 

parameter (for example, constraining a positive integer to be a negative 

value). 

The constraint operation is ignored. 



.........................................................................................................................................................................................................˝.......................................... 

1004 


Assignment inconsistent with existing constraint 

An attempt was made to assign to a parameter a value outside of its type 

constraint. For example, a negative value was assigned to a parameter of type 

positive integer. 

Cause 1: An attempt was made to assign a new value to a processed nonvalue-can-change 

parameter. 

Cause 2: The rule base is inconsistent: two rules that assign different values 

to a parameter have fired. The problem can be fixed by setting the 

parameter’s Value Can Change property to TRUE. Be sure that this solution 

is compatible with the knowledge base logic. 

The assignment is ignored. 

Note: If the knowledge base has been optimized using HPO, this error is 

generally not detected. However, during user sourcing, the Consultation 

Monitor will detect this error. 

.........................................................................................................................................................................................................˝.......................................... 

1005 

Invalid argument passed to the NUM function 

The argument to the KDL NUM function was not a valid string 

representation of a number. 



property using the value UNKNOWN for the NUM function. 

.........................................................................................................................................................................................................˝.......................................... 

1006 

List index is out-of-bounds 

In a list(index) type of reference, the value of index was greater than the 

length of list or less than 1. 



property using the value UNKNOWN for the index.



reported and the results are unpredictable. 

.........................................................................................................................................................................................................˝.......................................... 

1007 

Invalid argument passed to the HEX function 

The argument to the KDL HEX function is not a valid hexadecimal number. 

Check the number that you are using. 



property using the value UNKNOWN for the HEX function. 

.........................................................................................................................................................................................................˝.......................................... 

1008 

Invalid argument passed to the BIN function 

The argument to the BIN function is not a valid binary number. Check the 

number you are using. 



property using the value UNKNOWN for the BIN function. 

.........................................................................................................................................................................................................˝.......................................... 

1010 

Circular reasoning was detected 

While sourcing a parameter, AionDS found that the parameter required its 

own value to complete its sourcing. For example, the following rule 

combination can cause circular reasoning when sourcing the parameter a or 

b: 

if b then a ... if a then b ... 

The parameter causing the problem is removed from the goal list by setting it 

to processed; this avoids an infinite loop. 

Set the Value Can Change property of the parameter being sourced to 

TRUE. Make sure that this solution is consistent with the knowledge base 

logic. 



.........................................................................................................................................................................................................˝.......................................... 

1011 


State with invalid objects was entered 

A state with one or more invalid objects was encountered. The state is not 

executed. 

Edit the state in question and fix all of the invalid objects. Using the 

Outliner can help you identify all of the states that have invalid objects. 

.........................................................................................................................................................................................................˝.......................................... 

1012 

Incorrect data format encountered in External Data file 

While executing a READ DATA process, the contents of the file could not be 

read into the output parameters. This can occur because of an incorrect 

format or an inconsistency between the output parameter and the data value. 

Assignment of values to the output parameters is stopped. For example, if 

the format for the third output parameter is wrong, the first and second 

parameters are assigned values. The third and subsequent parameters are not 

assigned values. 

.........................................................................................................................................................................................................˝.......................................... 

1016 

Unable to evaluate entry conditions 

An unprocessed parameter was encountered while evaluating the entry 

conditions of a state. This most commonly occurs when information needed 

to evaluate the Entry Conditions property is located in a state that has not 

been evaluated yet. 

The state is not executed. Explicitly list all substates in the order they must 

be evaluated for proper operation. 

.........................................................................................................................................................................................................˝.......................................... 

1017 

Invalid argument passed to the DATE function 

The format of the argument for a KDL DATE function is not a valid format. 



property using the value UNKNOWN for the DATE function.


.........................................................................................................................................................................................................˝.......................................... 

1018 

Invalid argument passed to the TIME function 

The format of the argument for a KDL TIME function is not a valid format. 



property using the value UNKNOWN for the TIME function. 

.........................................................................................................................................................................................................˝.......................................... 

1019 

Unable to complete the agenda; it references an unprocessed parameter 

A parameter referenced in the agenda cannot be processed, so AionDS is 

unable to complete the agenda. 

.........................................................................................................................................................................................................˝.......................................... 

1115 

Left Margin is greater than Right Margin 

There is no room for text on the line because the specified left margin is to 

the right of the right margin. Check the use of &LM, &RM, &LI, and 

&RI. In reports, also check the Left Margin and Right Margin properties. 

.........................................................................................................................................................................................................˝.......................................... 

1116 

Message or block too long; truncated 

The TSL text is longer than the maximum size of 65,512 characters. This 

limit applies to messages and to blocks of text (marked with the &BLK 

command) within reports. The text is shown up to the point at which it was 

truncated. 

In a report, this error might be due to a &BLK+ command that does not 

have a corresponding &BLK- command. 

The size of a message is calculated by multiplying the number of lines times 

the width of the window in which the message is shown. Note that the size 

of a message cannot be computed before runtime because of indirect 

substitution. 



.........................................................................................................................................................................................................˝.......................................... 

1117 


Open failed for report output file 

The file for the report could not be created or opened. Any restriction on 

creating or opening a file for read/write will cause this error (for example, the 

file is write-protected, etc.) 

The report is not written. 

.........................................................................................................................................................................................................˝.......................................... 

1200 

X-size too small 

The horizontal resolution of the graph is too small. 

.........................................................................................................................................................................................................˝.......................................... 

1201 

Y-size too small 

The vertical resolution of the graph is too small. 

.........................................................................................................................................................................................................˝.......................................... 

1202 

Too few elements to graph 

The number of elements in one of the list parameters specified in the Data 

Values property of a line graph is less than 2. 

The graph is not displayed. 

.........................................................................................................................................................................................................˝.......................................... 

1203 

Too many elements to graph 

The number of elements to be graphed (in a line or bar graph) exceeds system 

limitations. The maximum number of elements that can be graphed depends 

on a number of variables: the graphics board resolution, the presence of a y- 

Title, and the number of elements in the list parameter specified in the 

graph’s Label Values property.



If the number of elements in any list parameter specified in the graph’s Data 

Values property and the number of elements in the list parameter specified in 

the graph’s Label Values property have a one-to-one ratio, change the ratio by 

increasing the number of lines/bars per label. 

.........................................................................................................................................................................................................˝.......................................... 

1204 

Missing data elements 

One of the list parameters specified in the graph’s Data Values property is an 

empty list or is unknown. 


.........................................................................................................................................................................................................˝.......................................... 

1205 

Data lengths are inconsistent with label lengths 

When drawing a bar or line graph, the number of elements in the list 

parameter specified in the graph’s Label Values property must evenly divide 

the number of elements in each list parameter specified in the graph’s Data 

Values property. 

When drawing a pie chart graph, the number of elements in the list 

parameter specified in the graph’s Label Values property must be equal to the 

number of elements in each list parameter specified in the graph’s Data 

Values property. 


.........................................................................................................................................................................................................˝.......................................... 

1206 

Header too long 

The Heading property of the Graph object is too long to be displayed. 

Reduce the length of the Heading. 



.........................................................................................................................................................................................................˝.......................................... 

1207 


Subheader too long 

The Sub-Heading property of the Graph object is too long to be displayed. 

Reduce the length of the Sub-Heading. 


.........................................................................................................................................................................................................˝.......................................... 

1210 

GRAPHICS-DRIVER table not found or invalid 

The graph driver is not in a directory in the Aion path, the DPATH, or the 

current directory. Check the name and location of the graph driver file. 

.........................................................................................................................................................................................................˝.......................................... 

1211 

Display terminal does not support graphics 

An attempt was made to display a graph on a terminal device that does not 

support graphics. 


.........................................................................................................................................................................................................˝.......................................... 

1213 

Data lengths are inconsistent 

When drawing a bar or line graph, the number of elements in each list 

parameter specified in the graph’s Data Values property must be the same as 

in the other parameters specified in the property. 


.........................................................................................................................................................................................................˝.......................................... 

1214 

Maximum Scale Value too small 

A data value is larger than the maximum scale value. Check the data values 

and the scale that you are using. 

The graph is not displayed.


.........................................................................................................................................................................................................˝.......................................... 

1215 

Minimum Scale Value too large 

A data value is less than the minimum scale value. Check the data values and 

the scale that you are using. 


.........................................................................................................................................................................................................˝.......................................... 

1216 

Graphics adapter incompatible with GRAPHICS-DRIVER table 

AionDS is unable to display a graph because the value of the GRAPHICS- 

DRIVER profile option does not match the type of graphics board in the 

computer. Check the graphics driver and set the profile option accordingly. 


(Character-Based) for an explanation of the possible values for the 

GRAPHICS-DRIVER profile option. 

.........................................................................................................................................................................................................˝.......................................... 

1217 

Invalid instance reference; method was sent to a class 

AionDS does not allow a generic reference to a slot or method in a method 

sent to a class. 

.........................................................................................................................................................................................................˝.......................................... 

1218 

Graphics library (ADSGM6.DLL) not found on LIBPATH 

Make sure that ADSGM6.DLL is included on the LIBPATH specified in the 

CONFIG.SYS file. 

.........................................................................................................................................................................................................˝.......................................... 

1219 

I/O privilege not configured (add IOPL=YES to CONFIG.SYS) 

Check that the statement IOPL=YES is present in your CONFIG.SYS file. 



.........................................................................................................................................................................................................˝.......................................... 

1220 


Graphics subsystem received unexpected OS return code 

AionDS is unable to display a graph because of an unexpected signal from the 

operating system. Check that the driver and the DLL are correctly located. 

If they are in the proper directories, contact PLATINUM Technical Support 

for AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

1221 

Unable to lock foreground screen 

Graphics require the foreground screen. AionDS must not be running in the 

background when an attempt is made to display a graph. 

.........................................................................................................................................................................................................˝.......................................... 

1320 

Class with invalid objects was entered 

AionDS is unable to ask slot values for the class because the class contains 

invalid objects. 

.........................................................................................................................................................................................................˝.......................................... 

1334 

Invalid add to processed list/set ignored 

AionDS is unable to add a value to the list or set because the parameter or 

slot has been processed and its Value Can Change property is FALSE. Check 

the logic to see why a rule or function tries to add a value after the parameter 

or slot is processed. 

.........................................................................................................................................................................................................˝.......................................... 

1336 

Invalid argument (must be a full parameter reference) 

Check to see if the field of a record was specified instead of the entire 

parameter. 

.........................................................................................................................................................................................................˝.......................................... 

1337 

Invalid argument (must be a VCC parameter) 

Check to see if the parameter specified in the argument has the Value Can 

Change property set to TRUE.


.........................................................................................................................................................................................................˝.......................................... 

1338 

User Function is invalid 

A call to an invalid function was detected. 

.........................................................................................................................................................................................................˝.......................................... 

1339 

Unknown or invalid instance name used 

The referenced instance is UNKNOWN or invalid. Check if the correct 

instance reference was specified. 



.........................................................................................................................................................................................................˝.......................................... 

1340 

Unknown, invalid or private slot referenced 

The referenced slot is UNKNOWN. Check if the correct slot reference was 

specified. 

.........................................................................................................................................................................................................˝.......................................... 

1341 

Attempted to delete a static instance 

Only dynamic instances can be deleted during runtime. 

.........................................................................................................................................................................................................˝.......................................... 

1342 

Invalid create; instance name already exists 

The instance specified in the create statement already exists. Change the 

name of the instance specified. 

.........................................................................................................................................................................................................˝.......................................... 

1343 

Cannot automatically invoke method with input/output parms or return 

value 

AionDS cannot automatically invoke a method if that method is a state or 

function with input or output parameters, or a return value. 



.........................................................................................................................................................................................................˝.......................................... 

1344 


Referenced object is unknown, private or invalid 

AionDS is unable to execute a method because it is invalid, private, or 

UNKNOWN. 

.........................................................................................................................................................................................................˝.......................................... 

1345 

Invalid pointer value 

AionDS is unable to dereference an instance pointer or delete an instance 

because the pointer does not point to a valid instance. Check whether the 

value of the pointer is UNKNOWN or the instance has been deleted. 



.........................................................................................................................................................................................................˝.......................................... 

1346 

Argument to CM function is missing or unknown 

The CM statement contains an argument whose value is UNKNOWN. 

Check that you have included all the necessary arguments and check the 

argument values. 

.........................................................................................................................................................................................................˝.......................................... 

1347 

Invalid window size/position passed to CM function 

The CM SETDIMENSIONS statement contains a value that is not within 

the appropriate range. For example, negative values for the width are invalid. 

.........................................................................................................................................................................................................˝.......................................... 

1348 

Invalid window type passed to CM GetWindow function 

The window type specified in the CM GETWINDOW statement is not a 

valid window type. 

For more information: See Chapter 4 of the AionDS Language Reference 

manual for a list of valid window types.


.........................................................................................................................................................................................................˝.......................................... 

1349 

Invalid function passed to CM System function 

The function specified in the CM SYSTEM statement is not a legal function 

name. 


manual for a list of valid functions. 

.........................................................................................................................................................................................................˝.......................................... 

1350 

Invalid color passed to CM Color function 

The color specified in the CM COLOR statement is not a legal color name. 


manual for a list of valid colors. 

.........................................................................................................................................................................................................˝.......................................... 

1351 

Invalid row or column value passed to CM SetCursor function 

The row or column specified in the CM SETCURSOR statement is outside 

of the appropriate range. The row value must be greater than zero. The 

column value must be greater than zero and less than the width of the 

window. 

.........................................................................................................................................................................................................˝.......................................... 

1352 

Invalid window type passed to CM function 

The window type specified in the CM statement is not a valid window type. 


manual for a list of valid window types. 

.........................................................................................................................................................................................................˝.......................................... 

1353 

CM function aborted; Consultation Monitor not active 

AionDS is unable to execute a CM statement because there is no current 

screen. This error occurs whenever a CM statement is used before the first 

screen is displayed or after one screen is finished and before the next screen is 

presented. 



.........................................................................................................................................................................................................˝.......................................... 

1359 


Object referenced in CM function is non-simple and can’t be sourced 

AionDS cannot execute a CM statement for the specified object because the 

object is too complex to be displayed on a single screen. The most complex 

object AionDS can display is a list of records in which all fields have basic 

data types. 

.........................................................................................................................................................................................................˝.......................................... 

1360 

Class must have an attached display to be sourced 

AionDS is unable to source values for the class because the class has no 

attached display. 

.........................................................................................................................................................................................................˝.......................................... 

1361 

Class contains list or set slots; may not be sourced 

AionDS cannot execute a CM or ASK statement for the specified class 

because the class is too complex to be displayed on a single screen. The most 

complex class that AionDS can display is one in which all slots have basic 

data types. 

.........................................................................................................................................................................................................˝.......................................... 

1362 

Illegal comparison - types are not compatible 

AionDS is unable to compare the values of an instance with those of an 

instance of another class. The comparison fails because there is a slot in one 

class that has the same position as a slot in the other class, but the type 

definition for these slots is different. For example, this error occurs if the 

third slot of one class has a different type than the third slot of the other class. 

.........................................................................................................................................................................................................˝.......................................... 

1363 

Class may not be loaded at this time; FLUSH required 

AionDS is unable to execute the DBMS(LOAD) statement because instances 

are already loaded in memory. The instances in memory may have been 

loaded as a result of a DBMS(LOAD) statement, or they may have been 

loaded automatically. This error can also occur if AionDS has created 

instances, and executed a DBMS(UPDATE) statement.


To correct this situation, execute the DBMS(FLUSH) statement before 

loading instances. 

.........................................................................................................................................................................................................˝.......................................... 

1364 

Invalid window handle passed to CM Function 

AionDS is unable to execute the CM statement because there is no window 

on the current screen with the specified handle. Check that the integer for 

the window handle is not hard-coded and that the variable that holds the 

handle is updated correctly. You can use CM GETCURSOR, CM 

GETWINDOW, or CM GETWINDOWLIST to get valid window handles. 

.........................................................................................................................................................................................................˝.......................................... 

1365 

Bad argument passed to the SET function 

The referenced slot is UNKNOWN. Check if the correct pointer and slot 

reference were specified. 

.........................................................................................................................................................................................................˝.......................................... 

1366 

Bad argument passed to the INDEX function 

The KDL INDEX statement specifies a non-existent index, such as zero. 

.........................................................................................................................................................................................................˝.......................................... 

1367 

DBMS function aborted; Class already in process 

AionDS is unable to execute a DBMS statement because it is already in the 

process of loading or updating the database. This can be due to a 

WHENLOADED demon that tries to execute a DBMS statement. 

.........................................................................................................................................................................................................˝.......................................... 

1368 

Bad argument passed to the READSTR or WRITESTR function 

One of the arguments to a READSTR or WRITESTR function was 

UNKNOWN or constant. An attempt was made to coerce an UNKNOWN 

or constant value into or out of the buffer. 

The statement is skipped. 



.........................................................................................................................................................................................................˝.......................................... 

1369 


Class does not contain any slots; may not be sourced 

An attempt was made to invoke the Consultation Monitor using a CM 

POPUP, CM ADD or ASK statement with a class that has no slots. The 

statement is skipped. 

.........................................................................................................................................................................................................˝.......................................... 

1370 

Internal stack overflow; check application for recursive logic 

The application exceeded the stack limitation of your computer. This 

problem typically occurs when user written functions get caught in an infinite 

loop. However, in very complex or vary large applications it is possible that 

the knowledge base complexity exceeds the facilities of your computer’s 

operating system. 

The consultation should be aborted; but if it isn’t, the KDL that caused the 

error (whether in a function or rule) is skipped entirely. 

.........................................................................................................................................................................................................˝.......................................... 

1371 

Illegal assignment: types incompatible 

AionDS cannot execute the assignment because the object types do not 

match. 

.........................................................................................................................................................................................................˝.......................................... 

1372 

Unknown argument to ADS function: %1 

The value of the specified argument is unknown. Verify that the argument 

was declared properly. 

.........................................................................................................................................................................................................˝.......................................... 

1373 

Forwardchain request ignored; Forward Chainer in progress 

The FORWARDCHAIN statement was ignored because the 

ForwardChainer was invoked earlier.


.........................................................................................................................................................................................................˝.......................................... 

1401 

Illegal operation for TextWindow with TWS_LABEL or 

TWS_READONLY style 

The operation is not valid for instances of TextWindow that have the Label 

or Readonly style. 

For more information: See the TextWindow chapter of the AionDS 

Building Graphical Applications: Reference for more information. 

.........................................................................................................................................................................................................˝.......................................... 

1402 

Illegal operation for TextWindow with TWS_LABEL style 

The operation is not valid for instances of TextWindow that have the Label 

style. 

For more information: See the TextWindow chapter of the AionDS 

Building Graphical Applications: Reference for more information. 

.........................................................................................................................................................................................................˝.......................................... 

1403 

Illegal operation; the desktop is not a valid parent for controls 

An instance of Desktop window can only have instances of StandardWindow 

as ChildWindows. A control can only have instances of StandardWindow, 

GroupBox or BitmapWindow as the ParentWindow. 

.........................................................................................................................................................................................................˝.......................................... 

1404 

User interface is GRAPHICAL, but KB doesn’t include WINLIB; reimport 

KB 

The USER-INTERFACE profile option setting does not match the 

knowledge base structure. Either set the USER-INTERFACE profile option 

to CHARACTER, or re-import the knowledge base so that the graphical 

window library is included. 

.........................................................................................................................................................................................................˝.......................................... 

1405 

User interface must be GRAPHICAL to issue graphical calls 

The knowledge base cannot execute graphical methods unless the USER- 

INTERFACE profile option is set to GRAPHICAL. 



.........................................................................................................................................................................................................˝.......................................... 

1406 


OpenApp may not be sent while an Application Window or Modal 

Dialog is open 

The OpenApp method cannot be sent if either a DialogBox, opened using 

the OpenModal method, or a StandardWindow, opened using the OpenApp 

method, is still open. 

.........................................................................................................................................................................................................˝.......................................... 

1407 

Illegal operation; object is open - %1 

The operation cannot be performed on a window instance that is currently 

open. 

.........................................................................................................................................................................................................˝.......................................... 

1408 

Illegal operation; object is not open - %1 

The operation cannot be performed on a window instance that is currently 

closed. 

.........................................................................................................................................................................................................˝.......................................... 

1409 

Illegal character; ampersand(&) is not allowed 

The ampersand (‘&’) character is not a valid character as input to the SetText 

method. 

.........................................................................................................................................................................................................˝.......................................... 

1410 

Illegal operation; can’t use SetText on a window with WS_TSL style 

The text of a TSL TextWindow cannot be dynamically modified. 

.........................................................................................................................................................................................................˝.......................................... 

1411 

SetText illegal on a graphic pushbutton 

AionDS supports only bitmaps for pushbuttons. Using text on pushbuttons 

is not supported.


.........................................................................................................................................................................................................˝.......................................... 

1416 

Graphical object does not exist - %1 

The file specified in the SourceFile or FileName slot of a graphical object 

cannot be found. Make sure the file exists in the search path. 

For more information: See the Installation and Operation Guide for your 

environment for information on the search path AionDS uses when looking 

for files. 

.........................................................................................................................................................................................................˝.......................................... 

1417 

Graphical object is not compatible format or is corrupt - %1 

The file specified in the SourceFile or FileName slot of a graphical object is 

either corrupt or is not in the correct format for the current operating system. 

Make sure you are pointing to the correct file, and that it is in the right 

format. 

.........................................................................................................................................................................................................˝.......................................... 

1418 

Error opening graphical object - %1 

There was an error opening the file specified in the SourceFile or FileName 

slot of a graphical object. Most likely either the file is corrupt or the system is 

running low on memory or graphical resources. Make sure you are pointing 

to the correct file, that it is in the right format, and that you have enough 

memory and resources to load the graphical object. 

.........................................................................................................................................................................................................˝.......................................... 

1420 

Illegal operation; can’t explicitly open a graphical object 

The Open method was sent to a graphical object (an instance of the Bitmap, 

Icon, or MousePointer class). There is no need to do this; graphical objects 

are opened and closed automatically by the system as needed. 

(The Open and Close methods are in the graphical object classes because they 

are inherited from the WindowObject class. However, they are never used). 



.........................................................................................................................................................................................................˝.......................................... 

1421 


Illegal operation; can’t explicitly close a graphical object 

The Close method was sent to a graphical object (a Bitmap, Icon, or 

MousePointer instance). There is no need to do this; graphical objects are 

opened and closed automatically by the system as needed. 

(The Open and Close methods are in the graphical object classes because they 

are inherited from the WindowObject class. However, they are never used). 

.........................................................................................................................................................................................................˝.......................................... 

1422 

Illegal operation; cannot Close a DesktopWindow instance 

The Close method was sent to an instance of DesktopWindow or one of its 

subclasses. This is not allowed, since there must always be a valid desktop 

open. 

If you want to change the desktop to a new desktop instance, simply send 

Open to the new instance. The old desktop instance will be closed 

automatically. 

.........................................................................................................................................................................................................˝.......................................... 

1423 

Cannot open DesktopWindow; existing DesktopWindow has open child 

windows 

The Open method was sent to an instance of DesktopWindow or one of its 

subclasses, but there are open windows still on the screen. You must close all 

windows that are owned by the knowledge base before opening a new 

desktop. 

.........................................................................................................................................................................................................˝.......................................... 

1424 

Illegal operation; specified parent window cannot have children - %1 

The SetParentWindow method’s argument (the new parent) belongs to a 

class which does not allow child windows. For example, a PushButton may 

not have children. Make sure the argument points to the correct instance.


.........................................................................................................................................................................................................˝.......................................... 

1425 

Illegal operation; child window equals or is an ancestor of parent window 

- %1 

The SetParentWindow method has been sent to an instance which either (a) 

is the same as the instance specified in the argument list, or (b) is an ancestor 

of the instance specified in the argument list. This is not allowed because a 

window may not be a child of itself or one of its children. 

.........................................................................................................................................................................................................˝.......................................... 

1426 

Windowing system return code - unable to set the parent of %1 

The arguments to the SetParentWindow method appear to be correct, but the 

operating system returned an error code when AionDS tried to set the 

window’s parent. Check the argument and the current instance to make sure 

they are valid, and make sure you are not out of memory or resources. 

.........................................................................................................................................................................................................˝.......................................... 

1427 

Illegal operation; specified window may not be a child of the desktop - 

%1 

The argument passed to the SetParentWindow method points to the desktop 

instance, but the method has been sent to an instance which may not legally 

be placed on the desktop. For example, a PushButton may not be on the 

desktop. Only instances of the StandardWindow class and its subclasses may 

be placed on the desktop. 

.........................................................................................................................................................................................................˝.......................................... 

1428 

Illegal operation; cannot change parent of app window or modal dialog - 

%1 

The SetParentWindow method has been sent to a window which was opened 

with the OpenApp or OpenModal statement. This is not allowed because it 

would put the windowing system in an unstable state. If you want to change 

the parent of the app window or a modal dialog, you must close the window 

or dialog before sending SetParentWindow. 



.........................................................................................................................................................................................................˝.......................................... 

1429 


Negative values not supported for Scroll Bar ranges 

The Open or SetScrollData method has been sent to a scroll bar using a 

negative value for either the Minimum or Maximum of the scroll range. This 

is not allowed by the windowing system. 

If you want to represent negative values using a scroll bar, you can set its 

scroll range to a positive range and then adjust the position internally when 

the WhichChosen method is sent to the scroll bar. 

.........................................................................................................................................................................................................˝.......................................... 

1431 

DDE - Paste Link failed 

Your attempt to paste a link into a DDELink instance failed. 

.........................................................................................................................................................................................................˝.......................................... 

1432 

DDE - Delete Link failed 

Your attempt to delete a link from a DDELink instance failed. 

.........................................................................................................................................................................................................˝.......................................... 

1433 

Illegal operation; toolbars may only contain tools 

You attempted to add an object other than a tool to a toolbar. Only tools are 

allowed in a toolbar. 

.........................................................................................................................................................................................................˝.......................................... 

1434 

Illegal operation; tools may only be placed in toolbars 

You attempted to place a tool somewhere other than a toolbar. Tools may 

only be placed in toolbars. To continue using the tool, place it in a toolbar. 

.........................................................................................................................................................................................................˝.......................................... 

1435 

Illegal operation; OpenApp may not be sent to dialogs 

You attempted to send OpenApp to a DialogBox class. OpenApp can be 

used to open the first standard window in an application, which cannot be a 

dialog box.


.........................................................................................................................................................................................................˝.......................................... 

1499 

Temporary restriction: cannot SetParent of an open StandardWindow 

In Windows, you cannot set the parent of an open standard window or dialog 

box. To use SetParent Window on a standard window or dialog box, make 

sure the window is closed first. 

.........................................................................................................................................................................................................˝.......................................... 

1501 

Argument %1 to Window or DDE function is missing or unknown 

The nth argument to the WIN_ keyword or DDE_ is either missing or 

UNKNOWN. Check the AionDS consultation trace or run the knowledge 

base with the debugger enabled to determine which method requires the 

argument and modify the knowledge base accordingly. 

Note: The arguments to the WIN_ keyword or DDE_ are not necessarily in 

the same order as the arguments to the method that executed it. 

.........................................................................................................................................................................................................˝.......................................... 

1502 

Method must be sent to an instance 

This graphical method cannot be sent to a class. It must be sent to an 

instance of the class. 

.........................................................................................................................................................................................................˝.......................................... 

1503 

Required Window or DDE slot value is unknown - %1 

The system needs the value of the named slot to process the graphical or 

DDE method. Check the AionDS consultation trace or run the knowledge 

base with the debugger enabled to diagnose the problem further. 

.........................................................................................................................................................................................................˝.......................................... 

2001 

String not found 

AionDS cannot find the target string during a search. 



.........................................................................................................................................................................................................˝.......................................... 

2003 


Window text too long 

The contents of the window exceed the system limit (65512 characters). If 

possible, the contents of the window should be split up and displayed in more 

than one window. 

.........................................................................................................................................................................................................˝.......................................... 

2006 

File truncated 

The file browser could not display the entire file because its contents exceed 

system limits. 

.........................................................................................................................................................................................................˝.......................................... 

2014 

Unmatched delimiter 

The user typed an ending parenthesis or square bracket, but a beginning 

parenthesis or square bracket was not found. 

.........................................................................................................................................................................................................˝.......................................... 

2015 

Unable to gain access to the clipboard 

The system clipboard is locked by another application causing AionDS to be 

unable to cut, copy or paste text. Close the application that has locked the 

clipboard, or take action to make it release the clipboard. 

.........................................................................................................................................................................................................˝.......................................... 

2016 

Display field out-of-bounds 

This warning message is written to the AionDS system log when the display 

management system in unable to display a field. The invalid field is not 

displayed. 

This condition will happen if the row, column, height or width of the field to 

be displayed is inconsistent with the display device. For example, an attempt 

is made to display a field beginning on row 35, but the display device only 

supports 24 lines. The row, column, height and width are included in the 

message that is written to the AionDS system log.


.........................................................................................................................................................................................................˝.......................................... 

2100 

Division by zero 

The mathematical operation being performed failed because an invalid value 

was detected. 



property using the value UNKNOWN for the division function. 

Caution: If the knowledge base has been optimized using HPO, this error 

is not detected and the results are unpredictable. 

.........................................................................................................................................................................................................˝.......................................... 

2101 

Real number overflow (number cannot be represented by AionDS) 

The number is too large. 



.........................................................................................................................................................................................................˝.......................................... 

2104 

Argument to SQRT function is negative 


was detected. 



property using the value UNKNOWN for the SQRT function. 



.........................................................................................................................................................................................................˝.......................................... 

2105 

Argument to LN function is less than or equal to zero 


was detected. 






property using the value UNKNOWN for the LN function. 



.........................................................................................................................................................................................................˝.......................................... 

2106 

Argument to TRUNC or ROUND function is too large 

The TRUNC or the ROUND function was called with a number larger than 

2,147,483,647 or smaller than -2,147,483,648. 



property using the value UNKNOWN for the TRUNC or ROUND 

function. 



.........................................................................................................................................................................................................˝.......................................... 

2107 

Left hand side of power (**) function must be positive 

The number that you want to raise to a power with the ** exponentiation 

operator must be positive. Check the KDL statement that caused the error. 



property using the value UNKNOWN for the ** function. 

.........................................................................................................................................................................................................˝.......................................... 

2201 

Integer overflow (value cannot be represented by an integer) 

The absolute value of an integer exceeds 2,147,483,647. 

The execution of the current KDL statement is terminated. The impact of 

this action depends on the situation at the time. If a Facts, Default, or Rule 

Definition property is being executed, it is terminated at the point of the 

error and excluded from further consideration. If an Entry Conditions or


Execution Conditions property is being executed, it is treated as if it 

evaluated to FALSE. 

If possible, change the type of the parameter to real. 



.........................................................................................................................................................................................................˝.......................................... 

2702 

Must be an instance of class DialogBox (or subclass) 

The specified instance is not an instance of the DialogBox class or of a 

subclass of DialogBox. When the Display property points to an instance, the 

instance must be in one of these classes so the system can open the window 

modally at runtime. 

Change the text of the Display property to point to such an instance, or move 

the specified instance to a subclass of DialogBox. 

.........................................................................................................................................................................................................˝.......................................... 

2778 

CREATE function not valid for WINLIB instances; use CreateObject 

instead 

AionDS has encountered a statement that tries to directly create a dynamic 

instance in the WindowObject class or any of its subclasses (the WinLib class 

hierarchy). 

Instead of using the CREATE function to create such an instance, send the 

CreateObject method to the class. This will perform the additional 

operations required for instances in the WinLib hierarchy. 

.........................................................................................................................................................................................................˝.......................................... 

2779 

Invalid object type; MESSAGE, PARAMETER, or SLOT expected (row 

%1/col %2) 

The attached object is not one of the allowable object types. Change the 

attached object to a message, parameter, or slot. 



.........................................................................................................................................................................................................˝.......................................... 

2794 


Invalid option for WIN_ statement (row %1/col %2) 

The win_ statement is a keyword reserved for use in predefined objects in the 

WinLib and cannot be used in knowledge bases. 

Most likely, you have specialized a method and copied the default code down 

from the same method in the parent class. Instead, you should use the 

SEND UP statement to execute the default code in the parent class. 

.........................................................................................................................................................................................................˝.......................................... 

2795 

Invalid statement; use Send Up instead (row %1/col %2) 

The win_ statement is a keyword reserved for use in predefined objects in the 

WinLib and cannot be used in knowledge bases. 

Most likely, you have specialized a method and copied the default code down 

from the same method in the parent class. Instead, you should use the 

SEND UP statement to execute the default code in the parent class. 

.........................................................................................................................................................................................................˝.......................................... 

2902 

Unknown option keyword 

The option specified is unknown or unsupported for the current function. 

This error typically occurs for record I/O functions (for example GETREC 

and PUTREC). 

.........................................................................................................................................................................................................˝.......................................... 

2903 

Comma must be used to separate option keywords 

There was a syntax error in specifying the list of options to the current KDL 

function. Typically this error is reported at edit-time, but it may be reported 

at runtime for certain record I/O functions. 

.........................................................................................................................................................................................................˝.......................................... 

2904 

Missing option keyword 

No options were specified for a KDL statement that required options. 

Typically this error is reported at edit time, but it may be reported at runtime 

for certain record I/O functions.


.........................................................................................................................................................................................................˝.......................................... 

2905 

Too many option keywords specified 

The number of options specified for the KDL statement exceeded the 

maximum number of options allowed. Typically this error is reported at edit 

time, but it may be reported at runtime for certain record I/O functions. 

.........................................................................................................................................................................................................˝.......................................... 

2906 

Contradictory options specified 

Two options were specified that are contradictory. Typically this error is 

reported at edit time, but it may be reported at runtime for certain record I/O 

functions. 

.........................................................................................................................................................................................................˝.......................................... 

3357 

Error: Window Library not found 

The knowledge base does not include the Window Library. This library, 

found in the WINLIB.1 knowledge base, must be included in the knowledge 

base. Use File.Libraries to add the knowledge base. 

.........................................................................................................................................................................................................˝.......................................... 

3358 

Window Library slots cannot be modified directly, use Library Methods 

AionDS has encountered a statement that tries to directly set the value of a 

slot imported from the Window Library (WinLib). Such statements are not 

allowed. 

To correct the problem, send the appropriate method to the instance that 

owns the slot instead of attempting to modify its slots directly. 

For example, if the statement in error is: 

textwindow1.Text = 'Name:' 

You correct this statement as follows: 

textwindow1.SetText('Name:') 



.........................................................................................................................................................................................................˝.......................................... 

3359 


DELETE function not valid for WINLIB instance; use DeleteObject 

instead 

AionDS has encountered a statement that tries to delete a dynamic instance 

directly in the WindowObject class or any of its subclasses (the WinLib class 

hierarchy). 

Instead of using the DELETE function to delete such an instance, send the 

DeleteObject method to the instance you want to delete. This will perform 

the additional operations required for instances in the WinLib hierarchy. 

.........................................................................................................................................................................................................˝.......................................... 

3361 

Error: DDE Library not found 

The DDE library cannot be found. Make sure the User-Interface setting is 

GRAPHICAL. You may need to import your application again. 

.........................................................................................................................................................................................................˝.......................................... 

4801 

Process %1 %2; string expected 

The data type of an input parameter or output parameter to a process does 

not match the definition of the process object. For example, the READ 

DATA process routine expects a string parameter as the first input parameter 

to the process. 

.........................................................................................................................................................................................................˝.......................................... 

4802 

Process %1 %2; parameter missing or value unknown 

The process object does not have all the required arguments or one of the 

mandatory arguments to the process is UNKNOWN. At runtime this error 

is typically reported when the value to a required input parameter is 

UNKNOWN. 

.........................................................................................................................................................................................................˝.......................................... 

4803 

Process %1 %2; string too long 

The value of an input parameter or output parameter to a process exceeds the 

maximum length allowed. Typically this error occurs if an input parameter 

that is used as a filename (for example, the first input parameter to the READ 

DATA process routine) exceeds the maximum possible length for a filename.


.........................................................................................................................................................................................................˝.......................................... 

4804 

Process %1 %2; integer expected 


not match the definition of the process object. For example, this error occurs 

if an integer parameter is expected and a non-integer parameter is specified. 

.........................................................................................................................................................................................................˝.......................................... 

4805 

Process %1 %2; boolean expected 


not match the definition of the process object. For example, this error occurs 

if a boolean parameter is expected and a non-boolean parameter is specified. 

.........................................................................................................................................................................................................˝.......................................... 

4810 

Unsupported process routine 

AionDS does not support the process routine specified. 

.........................................................................................................................................................................................................˝.......................................... 

4813 

Non-zero process completion code 

The completion code of a process routine was non-zero, but there was no 

output parameter in which to store the value. 

.........................................................................................................................................................................................................˝.......................................... 

4830 

Remote Connect/KB control parameter has incorrect type definition 

The type definition of the control parameter used for the REMOTE KB 

process routine is incorrect. 

.........................................................................................................................................................................................................˝.......................................... 

4880 

User exit requested percolation 

The external program called through API requested an error to be reported to 

the user. This message is written to the AionDS system log. 



.........................................................................................................................................................................................................˝.......................................... 

4881 


Monitor processing suppressed 

The requested user exit program (ASK, SHOW, GRAPH, PASSWORD, 

DISPLAY) is specified as NULL in the profile. Therefore, user sourcing and 

display are suppressed. This message is written to the AionDS system log. 

.........................................................................................................................................................................................................˝.......................................... 

4883 

%1-PROGRAM requested application termination 

The external program called through API requested the application to be 

terminated. 

.........................................................................................................................................................................................................˝.......................................... 

4884 

%1-PROGRAM requested consultation error processing 

The external program called through API requested a consultation error to be 

reported to the user. This message is written to the AionDS system log. 

.........................................................................................................................................................................................................˝.......................................... 

4885 

Executing %1-PROGRAM user exit 

This informational message is written to the AionDS system log before a user 

exit program is executed. 

.........................................................................................................................................................................................................˝.......................................... 

4886 

Error occurred executing %1-PROGRAM user exit 

A severe error occurred while AionDS was attempting to execute a user exit 

program (ASK-, SHOW-, GRAPH-, PASSWORD-, DISPLAY- 

PROGRAM). 

.........................................................................................................................................................................................................˝.......................................... 

5000 

ASK-PROGRAM processing did not complete 

The system is unable to successfully complete an ASK-PROGRAM user exit. 

Additional error information may be available in the AionDS system log.


.........................................................................................................................................................................................................˝.......................................... 

5001 

SHOW-PROGRAM processing did not complete 

The system is unable to successfully complete a SHOW-PROGRAM user 

exit. Additional error information may be available in the AionDS system 

log. 

.........................................................................................................................................................................................................˝.......................................... 

5002 

GRAPH-PROGRAM processing did not complete 

The system is unable to successfully complete a GRAPH-PROGRAM user 

exit. Additional error information may be available in the AionDS system 

log. 

.........................................................................................................................................................................................................˝.......................................... 

5003 

ASK-PROGRAM (group) processing did not complete 

The system is unable to successfully complete an ASK-PROGRAM user exit 

when sourcing a group. Additional error information may be available in the 

AionDS system log. 

.........................................................................................................................................................................................................˝.......................................... 

5004 

User sourcing not available for %1 (%2) 

AionDS is attempting to ask a parameter or slot in a component (CAES) 

knowledge base. Because there is no user interface available, the user’s answer 

is assumed to be unknown. 

.........................................................................................................................................................................................................˝.......................................... 

5005 

Message display not available for %1 (%2) 

AionDS is attempting to display a message in a component (CAES) 

knowledge base. Because there is no user interface available, the message 

should be written to the PRINT-FILE specified in the profile. 

.........................................................................................................................................................................................................˝.......................................... 

5006 

Graphic display not available for %1 (%2) 

AionDS is attempting to display a graph in a component (CAES) knowledge 

base. Because there is no user interface available, the graph is not displayed. 



.........................................................................................................................................................................................................˝.......................................... 

5007 


Group Processing not available for %1 (%2) 

AionDS is attempting to display a group in a component (CAES) knowledge 

base. Because there is no user interface available, the group message should 

be written to the PRINT-FILE specified in the profile and the group 

parameters/slots should be assumed to be unknown. 

.........................................................................................................................................................................................................˝.......................................... 

5008 

I/O error occurred opening PRINT-FILE 

The system encountered an operating system error while attempting to open 

the file specified in the PRINT-FILE profile option. Check the profile to 

make sure that the filename is valid and that there is enough disk space. 

.........................................................................................................................................................................................................˝.......................................... 

5009 

I/O error writing PRINT-FILE 

The system encountered an operating system error while attempting to write 

the file specified in the PRINT-FILE profile option. Check the system to 

make sure that there is enough disk space. 

.........................................................................................................................................................................................................˝.......................................... 

5010 

User exit requested percolation 

The user exit program (for example, ASK-PROGRAM or SHOW- 

PROGRAM) requested an error to be reported to the user. This message is 

written to the AionDS system log. 

.........................................................................................................................................................................................................˝.......................................... 

7305 

Severe Error -- Attempt to Continue? 

The system detected a severe internal consistency error. It is usually possible 

for the system to recover from this problem and to continue. 

At runtime the recommended action is to respond NO. The application 

developer should be contacted and the error should be reported.


At edit time the recommended action is to respond YES (continue). The 

application developer should attempt to export the application as soon as 

possible. If the export is successful, a fresh import should be done. If this 

problem re-occurs, a full copy of the application should be made and 

PLATINUM Technical Support for AionDS should be contacted. 

.........................................................................................................................................................................................................˝.......................................... 

12001 

Error during I/O operation on External Data file 

An I/O error occurred executing the READ DATA or WRITE DATA 

process routine. Check the system to make sure that there is enough disk 

space. 

.........................................................................................................................................................................................................˝.......................................... 

12002 

Unexpected symbol; number expected (row %1/col %2) 

The READ DATA process routine was expecting a numeric value. Check 

the format of the specified input file. 

.........................................................................................................................................................................................................˝.......................................... 

12003 

Unexpected symbol; string expected (row %1/col %2) 

The READ DATA process routine was expecting a string value. Check the 

format of the specified input file. 

.........................................................................................................................................................................................................˝.......................................... 

12004 

Unexpected symbol; boolean expected (row %1/col %2) 

The READ DATA process routine was expecting a boolean value. Check the 


.........................................................................................................................................................................................................˝.......................................... 

12005 

Unexpected symbol; integer expected (row %1/col %2) 

The READ DATA process routine was expecting an integer value. Check 




.........................................................................................................................................................................................................˝.......................................... 

12006 


Unexpected symbol; time expected (row %1/col %2) 

The READ DATA process routine was expecting a time value. Check the 


.........................................................................................................................................................................................................˝.......................................... 

12007 

Unexpected symbol; certainty expected (row %1/col %2) 

The READ DATA process routine was expecting a certainty value. Check 


.........................................................................................................................................................................................................˝.......................................... 

12008 

Unexpected symbol; ‘(‘ expected (row %1/col %2) 

The READ DATA process routine was expecting a ‘(‘ character. Check the 


.........................................................................................................................................................................................................˝.......................................... 

12009 

Unexpected symbol; ‘,’ expected (row %1/col %2) 

The READ DATA process routine was expecting a ‘,’ character. Check the 


.........................................................................................................................................................................................................˝.......................................... 

12010 

Unexpected symbol; ‘)’ expected (row %1/col %2) 

The READ DATA process routine was expecting a ‘)’ character. Check the 


.........................................................................................................................................................................................................˝.......................................... 

12011 

Unable to add element to list/set (row %1/col %2) 

The element specified is already present in the set and cannot be added. 

.........................................................................................................................................................................................................˝.......................................... 

12012 

Unable to assign value to parameter or instance slot (row %1/col %2) 

AionDS was unable to assign a value to the parameter or instance slot.


.........................................................................................................................................................................................................˝.......................................... 

12013 

Unexpected symbol; date expected (row %1/col %2) 

The READ DATA process routine was expecting a date value. Check the 


.........................................................................................................................................................................................................˝.......................................... 

12015 

Unexpected symbol; end of input expected (row %1/col %2) 

The READ DATA process routine was expecting the end of input character. 

Check the format of the specified input file. 

.........................................................................................................................................................................................................˝.......................................... 

12017 

Expected instance reference: class_name(instance_name) (row %1/col 

%2) 

The instance reference received (located on the row and column indicated) 

was in an unexpected format. The syntax for referencing an instance is 

class_name(instance_name). Verify that your instance reference matches this 

pattern. 

.........................................................................................................................................................................................................˝.......................................... 

12018 

Pointer type mismatch (row %1/col %2) 

The pointer type (located on the row and column indicated) does not match 

the type it references. Verify that the types for the pointer and the referenced 

item are the same. 

.........................................................................................................................................................................................................˝.......................................... 

12019 

Object reference expected: type(contextname(objectname)) (row %1/col 

%2) 

AionDS is expecting a reference to an object, using the object_pointer syntax. 

The object_pointer syntax is 

type(contextname(objectname)) 

For example, 

Parameter(Main(NumEmployees)) 



.........................................................................................................................................................................................................˝.......................................... 

12235 


Cannot create Slot in external class; try subclassing 

AionDS does not allow you to create slots in external classes (classes that are 

defined in libraries, such as WinLib). 

Instead of creating a slot in a predefined class, try creating a subclass of the 

predefined class. Then create a local slot in the subclass. 

.........................................................................................................................................................................................................˝.......................................... 

12241 

Inherited properties will affect a hidden or read-only subject 

AionDS will not allow the operation you have specified (for example, create 

or rename) because it would result in the slot or method having properties 

that are inherited by a hidden or read-only object in a subclass. Hidden and 

read-only objects cannot be modified directly or indirectly. 

.........................................................................................................................................................................................................˝.......................................... 

12254 

Skipped unspecializing object because information would be lost 

An object remained specialized because unspecializing it would cause 

information to be lost. For example, if the object has a specialized property, 

unspecializing the object would cause that property to revert to the value in 

its superclass. 

This message can be ignored. It is a warning to let you know that an object 

remained specialized. 

.........................................................................................................................................................................................................˝.......................................... 

13212 

Parent context must be visible for import 

In order to import an object, the state, class, or vocabulary into which it is 

being imported must not be hidden. Specify another parent that is visible. 

.........................................................................................................................................................................................................˝.......................................... 

13214 

%2: Inherited properties will affect a hidden or read-only object - %1 

AionDS will not allow the specified slot or method to be imported because it 

would result in the object having properties that are inherited by a hidden or 

read-only object in a subclass. Since hidden and read-only objects cannot be 

modified, either directly or indirectly, this operation is not allowed.


.........................................................................................................................................................................................................˝.......................................... 

13215 

Import is only valid for the knowledge base owner 

You cannot import a knowledge base unless you know the owner password. 

.........................................................................................................................................................................................................˝.......................................... 

13216 

%1: Cannot import slot into external class 

AionDS does not allow you to import slots in external classes (library classes). 

Instead of importing a slot in a predefined class, try creating a subclass of the 

predefined class. Then import a local slot into the subclass. 

.........................................................................................................................................................................................................˝.......................................... 

13424 

Inherited child object’s authorization restricted by parent’s authorization 

The authorization status of a child method or slot is inherited from the 

parent child or slot and cannot be changed. For example, if the parent 

method or slot is authorized as read-only, the child method or slot cannot be 

authorized as hidden or read-only. 

.........................................................................................................................................................................................................˝.......................................... 

13481 

Referenced object is unknown or invalid 

The system referenced an object that was invalid. This can happen in several 

ways. The most common cause is sending a message whose attached object is 

invalid. The solution is to edit the knowledge base and fix the invalid object. 

.........................................................................................................................................................................................................˝.......................................... 

13499 

Invalid slot instance integer value 

The value specified is not a valid value to the slot instance. Check the value. 

.........................................................................................................................................................................................................˝.......................................... 

13501 

Missing command or argument 

The syntax of the command requires additional arguments. Check the syntax 

for the desired command. 



.........................................................................................................................................................................................................˝.......................................... 

13502 


Unrecognized keyword 

The command issued is not valid or is misspelled. Check the syntax for the 

desired command. 

.........................................................................................................................................................................................................˝.......................................... 

13503 

Ambiguous keyword 

Not enough of the command was specified to disambiguate it from other 

valid commands. For example, this error occurs when E is specified and 

EDIT and EXPORT are both valid. 

.........................................................................................................................................................................................................˝.......................................... 

13504 

Extraneous input 

The user specified extra input that is not part of recognized command. 

.........................................................................................................................................................................................................˝.......................................... 

13509 

Invalid number 

The number specified for the command is invalid. For example, the number 

1000 is invalid for the version number. 

.........................................................................................................................................................................................................˝.......................................... 

13513 

“%1” expected 

The system expected the user to enter the command token displayed. For 

example, if you type ED in the Main monitor, the system responds 

with KNOWLEDGE BASE NAME EXPECTED. 

.........................................................................................................................................................................................................˝.......................................... 

13514 

Unbalanced string delimiter 

The string argument specified to the command does not have an ending 

quote mark. 

.........................................................................................................................................................................................................˝.......................................... 

14108 

Recursive call to an independent state 

AionDS is unable to invoke a state because the state has already been invoked 

and has not finished executing. States cannot be invoked recursively.


.........................................................................................................................................................................................................˝.......................................... 

14202 

Invalid function key pressed 

The function key pressed is not currently valid. Press F1 for help or check the 

AionDS User’s Guide (Character-Based) for a list of the currently valid 

function keys. 

.........................................................................................................................................................................................................˝.......................................... 

16001 

Input data is inconsistent with the specified mask 

The user typed either a null value or a value which does not match the mask 

associated with the parameter or slot being asked. 

.........................................................................................................................................................................................................˝.......................................... 

16002 

Input is too long 

AionDS is unable to accept the user-supplied value because it contains more 

characters than are specified in the mask for this value. 

.........................................................................................................................................................................................................˝.......................................... 

16003 

No date mask is specified 

The user-specified value does not match the default mask provided by 

AionDS. No other mask is specified in either the type definition, profile, or 

message file. 

.........................................................................................................................................................................................................˝.......................................... 

16004 

No time mask is specified 

The user-specified value does not match the default mask provided by 

AionDS. No other mask is specified in either the type definition, profile, or 

message file. 

.........................................................................................................................................................................................................˝.......................................... 

16009 

Bad separator 

The user-specified value does not correctly include a fixed character that is 

specified in the mask for this value. 



.........................................................................................................................................................................................................˝.......................................... 

16010 


Bad full (4 char) year input 

The user-specified year does not contain four digits or contains characters 

other than digits. 

.........................................................................................................................................................................................................˝.......................................... 

16011 

Bad year input 

The user-specified year does not conform to the mask specification. 

.........................................................................................................................................................................................................˝.......................................... 

16012 

Bad numeric month input 

The user-specified month does not conform to the mask specification. The 

value must be an integer less than or equal to 12. 

.........................................................................................................................................................................................................˝.......................................... 

16013 

Bad textual month input 

The user-specified month does not conform to the mask specification. The 

mask specifies either that the value be a three-letter abbreviation of the month 

name or that the value be the complete month name. 

.........................................................................................................................................................................................................˝.......................................... 

16014 

Bad day input 

The user-specified day does not conform to the mask. The value must be a 

positive integer less than or equal to 31. 

.........................................................................................................................................................................................................˝.......................................... 

16015 

Bad ordinal input 

The user-specified value does not conform to the mask. The value must 

contain the appropriate abbreviation ST, ND, RD, or TH to indicate an 

order. For example, 2ND signifies “second.” 

.........................................................................................................................................................................................................˝.......................................... 

16016 

Bad hour input (1, 12) 

The user-specified hour does not conform to the mask. The value must be a 

positive integer less than or equal to 12.


.........................................................................................................................................................................................................˝.......................................... 

16017 

Bad hour input (1, 24) 

The user-specified day does not conform to the mask. The value must be a 

non-negative integer less than or equal to 23. 

.........................................................................................................................................................................................................˝.......................................... 

16018 

Bad minute input 

The user-specified time does not conform to the mask. The minutes value 

must be a non-negative integer less than or equal to 59. 

.........................................................................................................................................................................................................˝.......................................... 

16019 

Bad second input 

The user-specified time does not conform to the mask. The seconds value 

must be a non-negative integer less than or equal to 59. 

.........................................................................................................................................................................................................˝.......................................... 

16020 

Bad hundredth second input 

The user-specified time does not conform to the mask. The hundredths of a 

second value must be a non-negative integer less than or equal to 99. 

.........................................................................................................................................................................................................˝.......................................... 

16021 

Bad time input (am, pm) 

The user-specified time does not conform to the mask. The time must 

include a designation of AM or PM. 

.........................................................................................................................................................................................................˝.......................................... 

16022 

Bad alpha input 

The user-specified value contains a non-alphabetic character where a letter is 

required. 

.........................................................................................................................................................................................................˝.......................................... 

16023 

Bad alphanumeric input 

The user-specified value contains a non-alphanumeric character where a letter 

or a number is required. 



.........................................................................................................................................................................................................˝.......................................... 

16024 


Bad character input 

The user-specified value does not contain as many characters as are required 

by the mask. 

.........................................................................................................................................................................................................˝.......................................... 

16025 

Bad numeric input 

The user-specified value contains a non-numeric character where a number is 

required. 

.........................................................................................................................................................................................................˝.......................................... 

16026 

Bad number input 

The user-specified value contains one or more non-numeric characters where 

one or more numbers are required. 

.........................................................................................................................................................................................................˝.......................................... 

16027 

Bad digit input 

The user-specified value contains a non-numeric character where a number is 

required. 

.........................................................................................................................................................................................................˝.......................................... 

16028 

Bad decimal input 

The user-specified value does not contain a decimal point, and a decimal 

point is required by the mask. 

.........................................................................................................................................................................................................˝.......................................... 

16029 

Bad sign input 

The user-specified value does not contain a plus sign (+) or a minus sign (-). 

The mask requires that one of these characters be present.


.........................................................................................................................................................................................................˝.......................................... 

19200 

Internal ADSAPI error: Invalid server command 

ADSAPI error code: ADSERR_INVALID_SERVER_COMMAND 

This is an internal error condition. An invalid message was passed to the 

ADSAPI server. Ensure that the ADSAPI link library and ADSAPI server are 

from the same version of AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

19201 

ADSAPI session name already in use 

ADSAPI error code: ADSERR_DUPLICATE_SESSION_NAME 

The name passed to ADSINITINTERFACE is already in use by another 

program. 

.........................................................................................................................................................................................................˝.......................................... 

19202 

ADSAPI session not found 

ADSAPI error code: ADSERR_SESSION_NOT_FOUND 

The specified session name was not found among the active ADSAPI clients. 

.........................................................................................................................................................................................................˝.......................................... 

19203 

ADSAPI server not responding (PC/WIN/OS2/PM/SUN/AIX) 

ADSAPI error code: ADSERR_SERVER_NOT_RESPONDING 

An ADSAPI server process is active, but did not respond to a call by the 

ADSAPI. The server may be hung. 

.........................................................................................................................................................................................................˝.......................................... 

19203 

Unable to load ADSAPI server (MVS/VM) 

ADSAPI error code: ADSERR_SERVER_NOT_RESPONDING 

AionDS was not able to load the ADSAPI server. Check that the ADSAPI 

load module exists and is available to AionDS. 



.........................................................................................................................................................................................................˝.......................................... 

19204 


ADSAPI is in an uninitialized state 

ADSAPI error code: ADSERR_API_NOT_INITED 

ADSAPI has not been initialized for this process, or initialization of the 

ADSAPI server failed. This error may be returned from an ADSAPI call if 

the ADSAPI server has recently shut down. Calling ADSINITINTERFACE will 

reinitialize ADSAPI. 

.........................................................................................................................................................................................................˝.......................................... 

19205 

Invalid ADSAPI session handle 

ADSAPI error code: ADSERR_INVALID_HANDLE 

The ADSAPI client handle supplied on an ADSAPI call is invalid. This error 

may occur if the ADSAPI server has been restarted. 

Reminder: In IMS, the error format is 19205-xx where xx is a 2-digit code 

described in the section “IMS and TSO transaction driver messages” in 

Chapter 2. 

.........................................................................................................................................................................................................˝.......................................... 

19206 

Invalid ADSAPI Parameter Descriptor Block 

ADSAPI error code: ADSERR_INVALID_PDB 

An invalid entry was discovered in the Parameter Descriptor Block. 

.........................................................................................................................................................................................................˝.......................................... 

19207 

Invalid ADSAPI string parameter length 

ADSAPI error code: ADSERR_INVALID_STRING_LENGTH 

A string argument passed to an ADSAPI function is too long or too short.


.........................................................................................................................................................................................................˝.......................................... 

19208 

Internal ADSAPI error: Invalid flags parameter 

ADSAPI error code: ADSERR_INVALID_FLAGS 

The flags argument passed to ADSSTARTSESSION is invalid. 

.........................................................................................................................................................................................................˝.......................................... 

19209 

Internal ADSAPI error: Invalid netpath 

ADSAPI error code: ADSERR_INVALID_NETPATH 

The current ADSAPI version does not support the network path argument to 

ADSSTARTSESSION. 

.........................................................................................................................................................................................................˝.......................................... 

19210 

Internal ADSAPI error: Session is not a child 

ADSAPI error code: ADSERR_NOT_CHILD_SESSION 

The ADSAPI session handle passed to ADSWAITSESSION does not belong to 

a session with a child process. 

.........................................................................................................................................................................................................˝.......................................... 

19211 

ADSAPI receive timed out 

ADSAPI error code: ADSERR_RECEIVE_TIMED_OUT 

The ADSAPI server did not respond to a call in time. The server or the 

target ADSAPI client may be hung. 

.........................................................................................................................................................................................................˝.......................................... 

19212 

Fixed Parameter List (FPL) does not exist 

ADSAPI error code: ADSERR_FPL_NOT_FOUND 

A Fixed Parameter List (FPL) was not supplied when the current process was 

started by ADSSTARTSESSION. 



.........................................................................................................................................................................................................˝.......................................... 

19213 


Buffer is too large for ADSAPI transfer 

ADSAPI error code: ADSERR_BUFFER_TOO_LARGE 

The data transfer buffer requirement is too large. 

.........................................................................................................................................................................................................˝.......................................... 

19214 

Internal ADSAPI error: Segment is not shareable 

ADSAPI error code: ADSERR_INVALID_SHARED_MEMORY 

An incorrect data pointer was provided on a call. 

.........................................................................................................................................................................................................˝.......................................... 

19215 

Internal ADSAPI error: Invalid subrequest index 

ADSAPI error code: ADSERR_INVALID_SUBREQUEST_NUM 

This is an internal error condition. 

.........................................................................................................................................................................................................˝.......................................... 

19216 

Internal ADSAPI error: Request is gone 

ADSAPI error code: ADSERR_REQUEST_NOT_FOUND 

This is an internal error condition. A data request has been completed by 

AionDS, but the request has disappeared from the ADSAPI data buffers. 

This error may occur if the requester is killed before an ADSAPI data request 

completes execution. 

.........................................................................................................................................................................................................˝.......................................... 

19217 

Target ADSAPI session is dead 

ADSAPI error code: ADSERR_REQUEST_DEST_DEAD 

The target of an ADSAPI data request is no longer active. For example, an 

ADSSENDMESSAGE request was issued by the knowledge base, but the 

partner session had terminated.




Chapter 2. 

.........................................................................................................................................................................................................˝.......................................... 

19218 

ADSAPI subsession not found 

ADSAPI error code: ADSERR_SUBSESSION_NOT_FOUND 


.........................................................................................................................................................................................................˝.......................................... 

19219 

Local ADSAPI receiver died 

ADSAPI error code: ADSERR_RECEIVER_DIED 


.........................................................................................................................................................................................................˝.......................................... 

19220 

ADSAPI subsession has already been claimed 

ADSAPI error code: ADSERR_SUBSESS_ALREADY_CLAIMED 

The default parent/child session has already been established. This occurs if 

an ADSAPI call is made before establishing the session with 

ADSINITINTERFACE. 



Chapter 2. 

.........................................................................................................................................................................................................˝.......................................... 

19221 

No parent ADSAPI session found 

ADSAPI error code: ADSERR_NO_PARENT_SESSION 

The current process is not a child created by ADSSTARTSESSION; 

ADSAPI_ATTACH_PARENT is not appropriate for this program. 



.........................................................................................................................................................................................................˝.......................................... 

19222 


Object not in ADSAPI shared heap 

ADSAPI error code: ADSERR_NOT_IN_HEAP 


.........................................................................................................................................................................................................˝.......................................... 

19223 

ADSAPI server has died 

ADSAPI error code: ADSERR_SERVER_DIED 

This is an internal error condition. The ADSAPI server is no longer active 

because it was killed or encountered a fatal error. The next 

ADSINITINTERFACE will restart the server. 

.........................................................................................................................................................................................................˝.......................................... 

19224 

Internal ADSAPI error: Invalid session handle 

ADSAPI error code: ADSERR_INVALID_SESSION_HANDLE 

An incorrect session handle was supplied as an argument. 

.........................................................................................................................................................................................................˝.......................................... 

19225 

Internal ADSAPI error: Invalid parameter value 

ADSAPI error code: ADSERR_INVALID_VALUE 

An invalid parameter value was supplied to ADSSETINTERFACE. 

.........................................................................................................................................................................................................˝.......................................... 

19226 

Internal ADSAPI error: Invalid parameter 

ADSAPI error code: ADSERR_INVALID_PARM 

An invalid function block size or function type was detected by the 

ADSSETINTERFACE call.


.........................................................................................................................................................................................................˝.......................................... 

19227 

Internal ADSAPI error: Invalid channel id 

ADSAPI error code: ADSERR_INVALID_CHANNEL 

The inbound or outbound channel specified by the session handle is invalid 

or has been closed. This error can be returned when the session partner 

terminates and no ADSGETMESSAGE is outstanding on the session. 

.........................................................................................................................................................................................................˝.......................................... 

19228 

Internal ADSAPI error: Request canceled 

ADSAPI error code: ADSERR_REQUEST_CANCELLED 

An API request to transfer data was canceled during execution because one of 

the API partners had broken the connection. 

.........................................................................................................................................................................................................˝.......................................... 

19229 

Incompatible ADSAPI.DLL and ADSAPI.EXE (version mismatch) 

ADSAPI error code: ADSERR_VERSION_MISMATCH 

The dynamic link library, ADSAPI.DLL, and server, ADSAPI.EXE, are not 

the same version. Check your LIBPATH and PATH. 

.........................................................................................................................................................................................................˝.......................................... 

19230 

ADSAPI error: Driver buffer too small 

ADSAPI error code: ADSERR_DRIVER_BUFFER_TOO_SMALL 

The buffer allocated by the DOS ADSAPI driver ADSAPI.EXE is too small 

to hold the ADSAPI request and user-defined buffer. 

.........................................................................................................................................................................................................˝.......................................... 

19233 

ADSAPI error: Unexpected response 

ADSAPI error code: ADSERR_UNEXPECTED_RESPONSE 

This error indicates a protocol error between the knowledge base, executing 

under MAES, and the program executing under CICS, IMS, TSO or Batch. 

This error can be returned by several AAPI functions. For example, during a 




call to ADSSENDMESSAGE to suspend the knowledge base, if AAPI does not 

receive a corresponding suspend OK message in reply to the 

ADSSENDMESSAGE, the ADSERR_UNEXPECTED_RESPONSE code is 

returned to the caller. 

.........................................................................................................................................................................................................˝.......................................... 

19234 

ADSAPI error: Invalid program specification 

ADSAPI error code: ADSERR_INVALID_PGM_SPEC 

This error code is returned by the ADSSTARTSESSION (ADSISE) function if 

the pPgmSpec parameter contains a non-null string. This error code is only 

returned if the program is being executed under IMS, TSO or Batch. The 

pPgmSpec parameter is not valid with AAPI/CICS because the pPgmArgs 

parameter of the ADSSTARTSESSION function contains the name of the 

knowledge base to be invoked. 

.........................................................................................................................................................................................................˝.......................................... 

19235 

ADSAPI error: Invalid option flags 

ADSAPI error code: ADSERR_INVALID_OPTION_FLAGS 

This error code can be returned by ADSSENDMESSAGE (ADSSME), 

ADSSETPARAMVALUES (ADSSPV), ADSSETCLASSVALUES (ADSSCV), 

ADSGETCLASSVALUES (ADSGCV) and ADSGETPARAMVALUES 

(ADSGPV) if the flag parameter on the function call does not match one of 

the valid flags for that function as documented in the AionDS/MVS 

Application Programming Interface Guide. 

Note: This error code is only returned if the program is executing under 

IMS, TSO or Batch. 

.........................................................................................................................................................................................................˝.......................................... 

19236 

ADSAPI error: Invalid delivery class 

ADSAPI error code: ADSERR_INVALID_DELIVERY_CLASS 

This error code can be returned by the ADSSENDMESSAGE (ADSSME) 

function if the delivery class coded on the parameter list to 

ADSSENDMESSAGE does not equal 1.


.........................................................................................................................................................................................................˝.......................................... 

19237 

ADSAPI error: Invalid message 

ADSAPI error code: ADSERR_INVALID_MESSAGE 

This error code can be returned by the ADSSENDMESSAGE (ADSSME) 

function if the message ID coded on the parameter list to 

ADSSENDMESSAGE does not equal one of the following: 

ADSMSG_EXT 100 

ADSMSG_RESUME 101 

ADSMSG_SUSPEND 102 

.........................................................................................................................................................................................................˝.......................................... 

19298 

Unable to load ADSAPI.DLL (may be missing or incorrect version) 

ADSAPI error code: NONE 

AionDS is unable to load the ADSAPI dynamic link library. This can be due 

to the following reasons: 

■ AionDS could not locate the library in a directory specified by the 

LIBPATH statement in CONFIG.SYS. 

■ An I/O error occurred during the load. 

■ The library is for a previous version of AionDS. 

Check that the correct ADSAPI.DLL resides in a directory specified in the 

LIBPATH. 

.........................................................................................................................................................................................................˝.......................................... 

19299 

API subsystem received unexpected OS return code 

ADSAPI error code: NONE 

An unexpected system error occurred while processing an ADSAPI request. 

The error code can be displayed in the AionDS system log using the /D1 

command line switch. Contact PLATINUM Technical Support for AionDS 

for further assistance. 



.........................................................................................................................................................................................................˝.......................................... 

19300 


ADSAPI error: Invalid object range 

ADSAPI error code: ADSERR_INVALID_OBJECT_RANGE 

The specified objects were not found on the appropriate process parameter 

list. 

.........................................................................................................................................................................................................˝.......................................... 

19301 

ADSAPI error: Invalid request 

ADSAPI error code: ADSERR_INVALID_REQUEST 


.........................................................................................................................................................................................................˝.......................................... 

19302 

ADSAPI error: Buffer too small 

ADSAPI error code: ADSERR_BUFFER_TOO_SMALL 

The buffer argument passed to an ADSAPI call is too small to contain the 

requested data. 



Chapter 2. 

.........................................................................................................................................................................................................˝.......................................... 

19303 

ADSAPI error: Chained request errors 

ADSAPI error code: ADSERR_CHAINED_REQUEST_ERRORS 


.........................................................................................................................................................................................................˝.......................................... 

19304 

ADSAPI error: Invalid info level 

ADSAPI error code: ADSERR_INVALID_INFO_LEVEL 

The information level argument is invalid or not supported for the target 

object type.


.........................................................................................................................................................................................................˝.......................................... 

19305 

ADSAPI error: FPL parameter not found 

ADSAPI error code: ADSERR_FPL_PARM_MISSING 


.........................................................................................................................................................................................................˝.......................................... 

19307 

ADSAPI error: Invalid object type 

ADSAPI error code: ADSERR_INVALID_OBJECT_TYPE 

The requested operation cannot be performed for the target object type. 

.........................................................................................................................................................................................................˝.......................................... 

19308 

ADSAPI error: Instance not found 

ADSAPI error code: ADSERR_INST_NOT_FOUND 

The specified instance name does not match any existing instances of the 

target class. 

.........................................................................................................................................................................................................˝.......................................... 

19309 

ADSAPI error: Too many instance names 

ADSAPI error code: ADSERR_TOO_MANY_INST_NAME 

More instance names than instance values were provided to 

ADSSETCLASSVALUES. 

.........................................................................................................................................................................................................˝.......................................... 

19310 

ADSAPI error: No more instance values 

ADSAPI error code: ADSERR_NO_MORE_INST 

All instance values have been retrieved. 



.........................................................................................................................................................................................................˝.......................................... 

19311 


ADSAPI error: Invalid object property 

ADSAPI error code: ADSERR_INVALID_PROPERTY 

The specified object property does not exist for this object. 

.........................................................................................................................................................................................................˝.......................................... 

19312 

ADSAPI error: Invalid slot index 

ADSAPI error code: ADSERR_INVALID_SLOT_INDEX 

The specified slot does not exist in the object. 

.........................................................................................................................................................................................................˝.......................................... 

19313 

ADSAPI error: Invalid item width 

ADSAPI error code: ADSERR_INVALID_ITEM_WIDTH 

The specified item width is not large enough to contain the fixed-size portion 

of the constraint information. 

.........................................................................................................................................................................................................˝.......................................... 

19314 

ADSAPI error: Invalid string width 

ADSAPI error code: ADSERR_INVALID_STRING_WIDTH 

The specified string width is invalid. 

.........................................................................................................................................................................................................˝.......................................... 

19315 

ADSAPI error: Parent not found 

ADSAPI error code: ADSERR_PARENT_NOT_FOUND 

The specified parent (context name) does not exist in the knowledge base. 

.........................................................................................................................................................................................................˝.......................................... 

19316 

ADSAPI error: Object not found 

ADSAPI error code: ADSERR_OBJECT_NOT_FOUND 

The specified object does not exist in the knowledge base.


.........................................................................................................................................................................................................˝.......................................... 

19317 

ADSAPI error: Invalid object name 

ADSAPI error code: ADSERR_INVALID_OBJECT_NAME 

The object name has an invalid syntax. See the ADSINITOBJECTLIST 

function description for the required syntax. 

.........................................................................................................................................................................................................˝.......................................... 

19318 

ADSAPI error: Parent not in scope 

ADSAPI error code: ADSERR_PARENT_NOT_INSCOPE 

The specified parent context is not accessible from the current location in the 

knowledge base. 

.........................................................................................................................................................................................................˝.......................................... 

19319 

ADSAPI error: Object pended 

ADSAPI error code: ADSERR_OBJECT_PENDED 

Sourcing was requested (SOURCEALL) but could not be completed because 

an out-of-scope source was encountered. 

.........................................................................................................................................................................................................˝.......................................... 

19350 

ADSAPI error: MAES not active 

ADSAPI error code: ADSERR_MAES_NOT_ACTIVE 

This error code is returned by the ADSINITINTERFACE (ADSIAP) function if 

the application program is unable to allocate a session to the MAES region 

specified in the client name passed to ADSINITINTERFACE. This error code 

is only returned by AAPI/CICS executing in the CICS region. 

.........................................................................................................................................................................................................˝.......................................... 

19351 

ADSAPI error: MAES not connected 

ADSAPI error code: ADSERR_MAES_NOT_CONNECTED 

This error code is returned by the ADSINITINTERFACE (ADSIAP) function if 

the application program is unable to connect a session to the MAES region 




specified in the client name passed to ADSINITINTERFACE. This error code 

is only returned by AAPI/CICS executing in the CICS region. 

.........................................................................................................................................................................................................˝.......................................... 

19352 

ADSAPI error: Session not freed 

ADSAPI error code: ADSERR_SESSION_NOT_FREED 

This error code is returned by the ADSTERMINTERFACE (ADSTAP) function 

if the application program is unable to free the LU6.2 session prior to 

termination of the CICS transaction. This error code is only returned by 

AAPI/CICS executing in the CICS region. 

.........................................................................................................................................................................................................˝.......................................... 

19353 

ADSAPI error: Session abend 

ADSAPI error code: ADSERR_SESSION_ABEND 

This error code indicates that the knowledge base abended because of a 

protocol error, an application coding error, or some other fatal system error 

that precludes it from continuing. This error can be returned by many 

AAPI/CICS functions, and is only returned by AAPI/CICS executing in the 

CICS region. 

.........................................................................................................................................................................................................˝.......................................... 

19354 

ADSAPI error: FPL not supported 

ADSAPI error code: ADSERR_FPL_NOT_SUPPORTED 

This error code is returned by the ADSSTARTSESSION (ADSISE) function if 

the FPL parameter coded on the parameter list is not zero. FPL processing is 

not supported by AAPI/CICS and AAPI/IMS. The ADSSETPARAMVALUES 

and ADSSETCLASSVALUES functions must be used to pass data to the 


.........................................................................................................................................................................................................˝.......................................... 

20100 

String truncated 

The string is too large for the field. It is truncated from the right to fit. 

Check the AionDS system log for more information about the error. Check 

the length of the string.


.........................................................................................................................................................................................................˝.......................................... 

20101 

Fixed-point overflows 

The real number is too large to store in fixed-point notation. Check the 

AionDS system log for more information about the error. Zero is stored into 

the field. 

.........................................................................................................................................................................................................˝.......................................... 

20102 

Unable to PUT real in 4 bytes 

The number is too large to fit in four bytes. Check the AionDS system log 

for more information about the error. Zero is stored into the field. 

.........................................................................................................................................................................................................˝.......................................... 

20103 

Zoned size too small 

The size specified for a real number is not sufficient to be stored in zoned 

format. Check the AionDS system log for more information about the error. 

Zero is stored into the field. 

.........................................................................................................................................................................................................˝.......................................... 

20104 

Packed size too small 

The size specified for a real number is not sufficient to store in packed format. 

Check the AionDS system log for more information about the error. Zero is 

stored into the field. 

.........................................................................................................................................................................................................˝.......................................... 

20105 

Bad packed-decimal format 

Cannot interpret field as a packed real number. Check the AionDS system 

log for more information about the error. The field is retrieved as zero. 

.........................................................................................................................................................................................................˝.......................................... 

20106 

Bad zoned-decimal format 

Cannot interpret field as a zoned real number. Check the AionDS system log 

for more information about the error. The field is retrieved as zero. 



.........................................................................................................................................................................................................˝.......................................... 

20107 


Textual field truncated 

Cannot store field in its textual format in the allotted space within a record. 

Check the AionDS system log for more information about the error. The 

field is truncated from its right side to fit within the file. 

.........................................................................................................................................................................................................˝.......................................... 

20108 

Bad time format 

The textual format of a time value is invalid. Check the AionDS system log 

for more information about the error. The field is retrieved as unknown. 

.........................................................................................................................................................................................................˝.......................................... 

20109 

Bad date format 

The textual format of a date value is invalid. Check the AionDS system log 

for more information about the error. The field is retrieved as unknown. 

.........................................................................................................................................................................................................˝.......................................... 

20110 

Bad integer format 

A textual field cannot be interpreted as an integer. Check the AionDS system 

log for more information about the error. The field is retrieved as unknown. 

.........................................................................................................................................................................................................˝.......................................... 

20111 

Bad real number format 

A textual field cannot be interpreted as a real number. Check the AionDS 

system log for more information about the error. The field is retrieved as 

unknown. 

.........................................................................................................................................................................................................˝.......................................... 

20112 

Bad boolean value format 

A textual field cannot be interpreted as a boolean. Check the AionDS system 

log for more information about the error. The field is retrieved as unknown. 

.........................................................................................................................................................................................................˝.......................................... 

20113 

Unable to PUT integer 

An integer is too large to be written in the size specified.


.........................................................................................................................................................................................................˝.......................................... 

20114 

List truncated 

The list size is too small to accept the number of elements in the record. 

Increase the size of the list parameter to accept all of the elements. 

.........................................................................................................................................................................................................˝.......................................... 

20120 

Record length exceeds data length 

The record length is different than the record definition requires. Check that 

the file was created with the same record definition. 

.........................................................................................................................................................................................................˝.......................................... 

20121 

Size is zero or negative 

A field is specified with an invalid length, such as a negative number of bytes 

or zero bytes. Check the AionDS system log for more information about the 

error. 

.........................................................................................................................................................................................................˝.......................................... 

20122 

Precision is negative 

A negative precision is specified. It must be zero or positive. Check the 

AionDS system log for more information about the error. 

.........................................................................................................................................................................................................˝.......................................... 

20123 

Bad integer size 

An integer is specified with an invalid length. An integer must be either one, 

two, or four bytes. Check the AionDS system log for more information 

about the error. 

.........................................................................................................................................................................................................˝.......................................... 

20124 

Packed size exceeds 16 

A record definition specifies more than 16 bytes for a packed real number. 


the record definition. 



.........................................................................................................................................................................................................˝.......................................... 

20125 


Zoned size exceeds 65512 

A record definition specifies more than 65,512 bytes for a zoned real number. 


the record definition. 

.........................................................................................................................................................................................................˝.......................................... 

20126 

Fixed size must be 2 or 4 

A record definition specifies a fixed real number with an invalid size. Check 

the AionDS system log for more information about the error. Check the 

record definition. A fixed real number must be either 2 or 4 bytes. 

.........................................................................................................................................................................................................˝.......................................... 

20127 

Real size must be 4 or 8 

A record definition specifies a real number with an invalid size. Check the 

AionDS system log for more information about the error. Check the record 

definition. A real number must be either 4 or 8 bytes. 

.........................................................................................................................................................................................................˝.......................................... 

20200 

20200 

File is not open (PC/WIN/OS2/PM/SUN/AIX/VM) 

Dataset is not open (MVS) 

The file is not open for I/O operations. Check that an OPENFILE 

statement has been executed. 

.........................................................................................................................................................................................................˝.......................................... 

20201 

Invalid field specified for keyed selection 

The AionDS record field specified for a VSAM keyed select is invalid. Check 

the use of the SELECT statement. 

.........................................................................................................................................................................................................˝.......................................... 

20202 

Parent file variable is not open 

An OPENFILE on a DL/I segment failed because the parent segment (file 

variable) has not been opened. Check that an OPENFILE statement on the 

parent segment is executed before an OPENFILE on the child segment.


.........................................................................................................................................................................................................˝.......................................... 

20203 

Invalid field or variable name 

The DL/I select field value is unknown. 

.........................................................................................................................................................................................................˝.......................................... 

20204 

Invalid variable record length; not within AionDS record length 

The variable record length specified for the KDL PUTREC statement is 

invalid because it exceeds the AionDS record length. The AionDS record 

length is computed according to the record definition in the base type of the 

file parameter. 

.........................................................................................................................................................................................................˝.......................................... 

20300 

File not found (PC/WIN/OS2/PM/SUN/AIX) 

The requested record I/O processing cannot be performed because the file 

cannot be found. Check for a valid path and filename. 

.........................................................................................................................................................................................................˝.......................................... 

20300 

Member specification not allowed (MVS/VM) 

A member of a partitioned dataset cannot be used for the requested record 

I/O processing. 

.........................................................................................................................................................................................................˝.......................................... 

20301 

Retrieved record with incorrect record length 


The length of the record retrieved is smaller than the associated AionDS 

record definition. Check that the record definition correctly matches the 

external data format. 

.........................................................................................................................................................................................................˝.......................................... 

20301 

20301 

Dataset record length inconsistent with type definition (MVS) 

File record length inconsistent with type definition (VM) 

The record length of the file is smaller than the associated AionDS record 

definition. Check that the record definition correctly matches the external 

data format. 



.........................................................................................................................................................................................................˝.......................................... 

20302 


Invalid record I/O option string given 

An invalid option was passed to an I/O function. Check the function syntax 

for the access method you are using. 

.........................................................................................................................................................................................................˝.......................................... 

20302 

Invalid OPENFILE option string 

An invalid option was passed to the OPENFILE function. Check the 

OPENFILE function syntax for the access method you are using. 

.........................................................................................................................................................................................................˝.......................................... 

20303 

Invalid record I/O open mode given 

An invalid open mode was specified in an OPENFILE statement. Check the 


.........................................................................................................................................................................................................˝.......................................... 

20304 

20304 

File not open for reading records (PC/WIN/OS2/PM/SUN/AIX/VM) 

Dataset not open for reading records (MVS) 

A GETREC cannot be performed on the file because it has not been opened 

with the correct mode. Check the open mode specified in the OPENFILE 

statement. 

.........................................................................................................................................................................................................˝.......................................... 

20305 

20305 

File not open for writing records (PC/WIN/OS2/PM/SUN/AIX/VM) 

Dataset not open for writing records (MVS) 

A PUTREC cannot be performed on the file because it has not been opened 

with the correct mode. Check the open mode specified in the OPENFILE 

statement.


.........................................................................................................................................................................................................˝.......................................... 

20306 

20306 

File not open for updating records (PC/WIN/OS2/PM/SUN/AIX/VM) 

Dataset not open for updating records (MVS) 

A PUTREC UPDATE cannot be performed on the file. Check that the file 

was opened with UPDATE specified as the open mode. 

.........................................................................................................................................................................................................˝.......................................... 

20307 

20307 

20307 

GETREC called at end-of-file (PC/WIN/OS2/PM/SUN/AIX) 

Dataset not open for adding records (MVS) 

File not open for adding records (VM) 

A PUTREC ADD cannot be performed on the dataset. Check the open 

mode specified in the OPENFILE statement. 

.........................................................................................................................................................................................................˝.......................................... 

20308 

Record must first be retrieved for UPDATE 


.........................................................................................................................................................................................................˝.......................................... 

20308 

GETREC called at end-of-file (MVS/VM) 

An attempt was made to read past the end of the file. 

.........................................................................................................................................................................................................˝.......................................... 

20309 

Record must first be retrieved for UPDATE (MVS/VM) 

A PUTREC UPDATE was attempted on a record that was not retrieved for 

update. Check the open mode specified in the OPENFILE statement. 

.........................................................................................................................................................................................................˝.......................................... 

20310 

20310 

I/O operation not supported for this dataset type 

Invalid dataset type/organization 

The dataset organization in an OPENFILE statement is not supported, or the 

access method does not match the access method specified in the file type 

object. 



.........................................................................................................................................................................................................˝.......................................... 

20311 


I/O operation not supported by access method 

AionDS is unable to access the database or file because the knowledge base 

uses an access method that is not available in the operating environment. 

.........................................................................................................................................................................................................˝.......................................... 

20312 

20312 

I/O operation not supported for this dataset type (MVS) 

I/O operation not supported for this file type (VM) 

Using VSAM, the I/O operation is not supported for the file type (KSDS, 

ESDS, or RRDS). 

.........................................................................................................................................................................................................˝.......................................... 

20313 

Incorrect key location 

Using VSAM, the location of the key is inconsistent with the associated 

AionDS record definition. Check the record definition and the key 

specification. 

.........................................................................................................................................................................................................˝.......................................... 

20314 

Incorrect key length 

Using VSAM, the length of the key is inconsistent with the associated 

AionDS record definition. 

.........................................................................................................................................................................................................˝.......................................... 

20315 

Invalid generic key length 

Using VSAM, the key length specified in the SELECT statement is 

inconsistent with dataset the key. Check that the length specified does not 

exceed the length of the dataset key. 

.........................................................................................................................................................................................................˝.......................................... 

20317 

QSAM record length modification not allowed for UPDATE 

A PUTREC UPDATE was attempted on a variable length QSAM record, 

but the length of the data does not match the length of the record retrieved.


.........................................................................................................................................................................................................˝.......................................... 

20320 

QSAM I/O operation failed 

An I/O operation using QSAM failed. Use the FILESTATUS option to get 

further information regarding the QSAM error. 

.........................................................................................................................................................................................................˝.......................................... 

20330 

VSAM OPEN request failed 

An OPENFILE using VSAM failed. Check the AionDS system log for 

further information about the error. 

.........................................................................................................................................................................................................˝.......................................... 

20331 

VSAM CLOSE request failed 

A CLOSEFILE using VSAM failed. Check the AionDS system log for 


.........................................................................................................................................................................................................˝.......................................... 

20332 

VSAM GET request failed 

A GETREC using VSAM failed. Check the AionDS system log for further 

information about the error. 

.........................................................................................................................................................................................................˝.......................................... 

20333 

VSAM PUT request failed 

A PUTREC using VSAM failed. Check the AionDS system log for further 


.........................................................................................................................................................................................................˝.......................................... 

20334 

VSAM ERASE request failed 

A DELETEREC using VSAM failed. Check the AionDS system log for 


.........................................................................................................................................................................................................˝.......................................... 

20335 

VSAM POINT request failed 

A SELECT using VSAM failed. Check the AionDS system log for further 




.........................................................................................................................................................................................................˝.......................................... 

20336 


Unexpected VSAM MODRPL request failure 

At attempt to modify the request parameter list (RPL) to change VSAM 

processing information was not successful. 

.........................................................................................................................................................................................................˝.......................................... 

20344 

VSAM not positioned for I/O operation 

The VSAM file is currently not positioned for the I/O operation. Check the 

usage of the operation under VSAM. You must use a SELECT statement 

that establishes positioning before you can perform the operation. 

.........................................................................................................................................................................................................˝.......................................... 

20345 

Attempt to change prime key or key of reference 

An attempt was made to change the prime key for a VSAM dataset. 

.........................................................................................................................................................................................................˝.......................................... 

20346 

Invalid record number 

The KDL SELECT statement specifies an invalid record number. Check 

that the record number is greater than zero. 

.........................................................................................................................................................................................................˝.......................................... 

20350 

Remote VSAM OPEN request failed 

An OPENFILE using remote VSAM failed. Check the AionDS system log 

for further information about the error. 

.........................................................................................................................................................................................................˝.......................................... 

20351 

Remote VSAM CLOSE request failed 

A CLOSEFILE using remote VSAM failed. Check the AionDS system log 


.........................................................................................................................................................................................................˝.......................................... 

20352 

Remote VSAM GET request failed 

A GETREC using remote VSAM failed. Check the AionDS system log for 

further information about the error.


.........................................................................................................................................................................................................˝.......................................... 

20353 

Remote VSAM PUT request failed 

A PUTREC using remote VSAM failed. Check the AionDS system log for 


.........................................................................................................................................................................................................˝.......................................... 

20354 

Remote VSAM ERASE request failed 

A DELETEREC using remote VSAM failed. Check the AionDS system log 


.........................................................................................................................................................................................................˝.......................................... 

20355 

Remote VSAM SELECT request failed 

A SELECT using remote VSAM failed. Check the AionDS system log for 


.........................................................................................................................................................................................................˝.......................................... 

20359 

Remote VSAM GET returned DUPKEY condition 

A GETREC using remote VSAM returned a DUPKEY condition. Check the 

AionDS system log for further information about the error. 

.........................................................................................................................................................................................................˝.......................................... 

20365 

The SELECT format used is valid only for READ mode 

AionDS cannot execute the SELECT statement because it contains an 

inappropriate option. Because the dataset is not open for reading records, the 

following options cannot be used: BACKWARD, FORWARD, FIRSTREC, 

and LASTREC. 

.........................................................................................................................................................................................................˝.......................................... 

20366 

The requested I/O operation requires a key 

AionDS is unable to perform a PUTREC ADD, using remote VSAM, on a 

dataset that is opened for UPDATE because positioning was not established 

prior to the request. Use a SELECT statement to establish position in the 

dataset before issuing the PUTREC ADD. 




This error is reported if: 

■ the dataset is an RRDS 

■ the dataset is a KSDS or an ESDS path residing in a separate File 

Owning Region, and the key position is not specified in the FCT 

.........................................................................................................................................................................................................˝.......................................... 

20368 

File is not open and/or unenabled 

AionDS is unable to open the dataset. Use the CEMT INQUIRE 

DATASET command to attempt to open the file. 

.........................................................................................................................................................................................................˝.......................................... 

20369 

Remote VSAM UNLOCK request failed 

An attempt to unlock a VSAM file defined to a CICS system has failed. 

.........................................................................................................................................................................................................˝.......................................... 

20370 

Remote MRO file requires specific VSAM type 

An attempt was made to access a file defined to a CICS region other than 

where the AAES transaction driver resides, but the AionDS file parameter did 

not specify the VSAM organization of the file (KSDS, RRDS, or ESDS). 

.........................................................................................................................................................................................................˝.......................................... 

20373 

DL/I request failed - DL/I language conflict 

CICS/VS rejected a DL/I request because of a conflict between the language 

being used and what was specified in the PSB. 

.........................................................................................................................................................................................................˝.......................................... 

20374 

DL/I request failed - PSB initialization failed 

The transaction driver attempted to schedule the PSB but the request failed 

when CICS/VS could not initialize the PSB. See the CICS/VS console log to 

determine the specific error CICS/VS encountered.


.........................................................................................................................................................................................................˝.......................................... 

20375 

DL/I request failed - PSB not authorized 

CICS/VS rejected a DL/I request because the program was not authorized to 

issue that specific request. For example, if the transaction driver issued an 

ISRT request yet the PSB only authorized the program to retrieve segments, 

this error would be reported. 

.........................................................................................................................................................................................................˝.......................................... 

20376 

DL/I request failed - DL/I unscheduled termination 

A DL/I request was rejected due to an unscheduled termination. 

.........................................................................................................................................................................................................˝.......................................... 

20377 

DL/I request failed - DL/I function unscheduled 

A DL/I request was rejected and the function unscheduled. 

.........................................................................................................................................................................................................˝.......................................... 

20378 

DL/I request failed - DL/I UIBFCTR unknown 

CICS/VS returned a DL/I status condition that the transaction driver could 

not interpret. This condition normally represents a program error. The code 

was returned in UIBFCTR. 

.........................................................................................................................................................................................................˝.......................................... 

20379 

DL/I request failed - DL/I UIBDLTR unknown 



was returned in UIBDLTR. 

.........................................................................................................................................................................................................˝.......................................... 

20380 

Invalid segment name (0 or greater than 8 characters) 

A segment name must be a valid DL/I segment name. It must be between 1 

and 8 characters, inclusive. 



.........................................................................................................................................................................................................˝.......................................... 

20381 


Invalid database name (0 or greater than 8 characters) 

A database name must be a valid DL/I database name. It must be between 1 

and 8 characters, inclusive. 

.........................................................................................................................................................................................................˝.......................................... 

20382 

Segment not open for retrieving records 

You must execute the OPENFILE statement using the READ or UPDATE 

option before you can retrieve a segment. 

.........................................................................................................................................................................................................˝.......................................... 

20383 

Segment not open for updating records 

You must execute the OPENFILE statement using the UPDATE option 

before you can replace a segment. 

.........................................................................................................................................................................................................˝.......................................... 

20384 

Segment not open for writing records 

You must execute the OPENFILE statement using the WRITE or APPEND 

options before you can insert a segment. 

.........................................................................................................................................................................................................˝.......................................... 

20385 

I/O operation invalid; GETREC-UPDATE returned EOF 

An attempt was made to execute a PUTREC or DELETEREC statement on 

a record after the GETREC operation failed. 

.........................................................................................................................................................................................................˝.......................................... 

20386 

DL/I request failed - invalid PSB address 

A DL/I request was issued to CICS/VS but the address of the passed PCB 

was invalid. This condition represents an internal logic error in the 

transaction driver. 

.........................................................................................................................................................................................................˝.......................................... 

20387 

DL/I request failed - DL/I scheduling conflict 

The DL/I request was rejected due to a scheduling conflict. See the CICS/VS 

console log to determine the cause of the error.


.........................................................................................................................................................................................................˝.......................................... 

20388 

DL/I request failed - DL/I task not authorized 

The DL/I request was rejected when CICS/VS determined that the 

transaction had not been properly authorized to use that function. 

.........................................................................................................................................................................................................˝.......................................... 

20389 

DL/I request failed - PSB already scheduled 

Due to an internal error, the transaction driver attempted to schedule a PSB a 

second time. 

.........................................................................................................................................................................................................˝.......................................... 

20390 

DL/I GET request failed 

AionDS executed a DL/I GU, GN, GHU, or GHN request that resulted in 

an error. Use DBINFO to determine the PCB status or check the AionDS 

system log. 

.........................................................................................................................................................................................................˝.......................................... 

20391 

DL/I PUT request failed 

AionDS executed a DL/I REPT or ISRT request that resulted in an error. 

Use DBINFO to determine the PCB status or check the AionDS system log. 

.........................................................................................................................................................................................................˝.......................................... 

20392 

DL/I DELETE request failed 

AionDS executed a DL/I DLET request that resulted in an error. Use 

DBINFO to determine the PCB status or check the AionDS system log. 

.........................................................................................................................................................................................................˝.......................................... 

20393 

DL/I request failed - unknown database name 

AionDS cannot locate the database. Check the database name. 

.........................................................................................................................................................................................................˝.......................................... 

20394 

DL/I request failed - number of SSA’s exceeds 16 

More than 16 segment search arguments are specified. You can specify a 

maximum of 16 segment search arguments. 



.........................................................................................................................................................................................................˝.......................................... 

20395 


DL/I request failed - DL/I database not open 

CICS/VS rejected a DL/I request because the database was not open. The 

CICS/VS console log should indicate why the database was not opened when 

CICS/VS was initialized. 

.........................................................................................................................................................................................................˝.......................................... 

20396 

CICS/VS could not access database (not in FCT or unopened) 

The DL/I request was rejected when CICS/VS either could not find the 

database name in the FCT, or the database was not open (as reflected in the 

FCT) or an invalid argument was passed to DL/I. 

.........................................................................................................................................................................................................˝.......................................... 

20397 

CICS/VS rejected request - DL/I is not active 

CICS/VS rejected a DL/I request because DL/I was not active. 

.........................................................................................................................................................................................................˝.......................................... 

20398 

DL/I request failed - invalid PSB 

The transaction driver attempted to allocate the PSB but instead was rejected 

when CICS/VS could not find the named PSB. 

.........................................................................................................................................................................................................˝.......................................... 

20399 

DL/I request failed - invalid request 

A DL/I call was required but CICS/VS discovered an error before passing 

control to DL/I. The UIBFCTR field has been set to X'08' by CICS/VS. See 

“DL/I Interface Response Codes” in the CICS Application Programmer’s 

Reference Manual (Command Level). 

.........................................................................................................................................................................................................˝.......................................... 

20400 

SQL “fetch” attempted at end-of-file 

An attempt was made to execute a GETREC statement after the EOF 

statement returned TRUE.


.........................................................................................................................................................................................................˝.......................................... 

20401 

Selection criteria must be established for SQL cursor 

An SQL statement using a SELECT must be executed before executing the 

OPENFILE statement. 

.........................................................................................................................................................................................................˝.......................................... 

20402 

Operation attempted on an unopened SQL cursor 

You must execute an OPENFILE statement before you can execute a 

statement such as GETREC. 

.........................................................................................................................................................................................................˝.......................................... 

20403 

All SQL cursors are currently in use 

You must execute a CLOSEFILE statement on an SQL file parameter before 

you can execute another OPENFILE statement. 

.........................................................................................................................................................................................................˝.......................................... 

20404 

Number of SQL columns selected not compatible with target parameter 

Check the number of columns used in your SQL statement. You must have 

the same number of columns as basic data type parameters in the target 

parameter. 

.........................................................................................................................................................................................................˝.......................................... 

20406 

SQL “open cursor" failed 

Check the format of your OPENFILE statement. Check the AionDS system 

log for more information. 

.........................................................................................................................................................................................................˝.......................................... 

20407 

SQL “select” operation failed 

AionDS could not execute an SQL SELECT statement. Check the AionDS 

system log for more information. 

.........................................................................................................................................................................................................˝.......................................... 

20408 

SQL “fetch” operation failed 

AionDS could not retrieve a record using GETREC. Check the AionDS 

system log for more information. 



.........................................................................................................................................................................................................˝.......................................... 

20409 


SQL “request” operation failed 

AionDS could not execute a non-SELECT statement using SQL. Check the 

AionDS system log for more information. 

.........................................................................................................................................................................................................˝.......................................... 

20410 

A SQL database connection cannot be established 

AionDS cannot connect to the SQL database. Check the AionDS system log 

for more information. Check with your system manager to make sure you 

have the proper database authorizations. 

.........................................................................................................................................................................................................˝.......................................... 

20411 

Size of SQL data returned exceeds AionDS limit 

The amount of data being returned from the SQL SELECT statement 

exceeds the AionDS data buffer limit. 

.........................................................................................................................................................................................................˝.......................................... 

20412 

20412 

20412 

20412 

Invalid SQL interface; valid values are “IBM”, “Oracle”, “Sybase”, and 

“ODBC” (PC/WIN/OS2/PM) 

Invalid SQL interface; valid values are “DB2”, “Oracle”, and 

“DBC/1012” (MVS) 

Invalid SQL interface; valid values are “SQL/DS”, “Oracle”, and 

“DBC/1012” (VM) 

Invalid SQL interface; valid values are “Oracle” and “Sybase” (SUN/AIX) 

The value of the SQL-INTERFACE profile option, or the first argument of a 

KDL SQLCONNECT statement, is not valid for the operating environment. 

.........................................................................................................................................................................................................˝.......................................... 

20413 

SQL database name missing or too long (PC/WIN/OS2/PM/SUN/AIX) 

The value of the SQL-DATABASE profile option, or the second argument of 

a KDL SQLCONNECT statement, is missing or too long.


.........................................................................................................................................................................................................˝.......................................... 

20413 

DB2 subsystem name missing or greater than 4 characters (MVS) 

AionDS was not able to establish a connection to DB2 because the subsystem 

name specified in the SQL-DATABASE profile option, or the second 

argument of a KDL SQLCONNECT statement, is missing or is too long. 

.........................................................................................................................................................................................................˝.......................................... 

20413 

SQL/DS database machine name greater than 8 characters (VM) 

AionDS was not able to establish a connection to SQL/DS because the 

database machine name specified in the SQL-DATABASE profile option, or 

the second argument of a KDL SQLCONNECT statement, is missing or is 

too long. 

.........................................................................................................................................................................................................˝.......................................... 

20414 

SQL access string is inconsistent with SQL interface 

The value of the SQL-ACCESS-STRING profile option, or the third 

argument of a KDL SQLCONNECT statement, is incorrect for the specified 

SQL interface. 

.........................................................................................................................................................................................................˝.......................................... 

20415 

Unable to load support library for IBM Database Manager (OS2/PM) 

AionDS was not able to connect to IBM Database Manager because the 

AionDS database interface is not installed or the files cannot be found. 

Check that the files are present and accessible to AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

20415 

20415 

DBC/1012 tdpid greater than 4 characters (MVS) 

DBC/1012 tdpid greater than 8 characters (VM) 

AionDS was not able to access the DBC/1012 because the Teradata Director 

Program ID is too long. 



.........................................................................................................................................................................................................˝.......................................... 

20416 


Unable to load support library for Oracle (PC/WIN/OS2/PM/SUN/AIX) 

AionDS was not able to connect to Oracle because the AionDS database 

interface is not installed or the files cannot be found. Check that the files are 

present and accessible to AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

20416 

Aion Database Interface for DBC/1012 not installed (MVS/VM) 

An attempt was made to execute an I/O function using the DBC/1012 access 

method, but the Aion Database Interface for DBC/1012 is not installed. 

.........................................................................................................................................................................................................˝.......................................... 

20417 

Unable to load support library for VAX Rdb/VMS 

AionDS was not able to connect to Rdb/VMS because the AionDS database 

interface is not installed or the files cannot be found. Check that the files are 

present and accessible to AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

20418 

Unable to load support library for Microsoft/Sybase SQL Server 

AionDS was not able to connect to Microsoft or Sybase SQL Server because 

the AionDS database interface is not installed or the files cannot be found. 


.........................................................................................................................................................................................................˝.......................................... 

20419 

Invalid remote SQL interface; valid values are “IBM” and “DB2” 

(WIN/OS2/PM) 

The value of the SQL-INTERFACE profile option, or the first argument of a 

KDL SQLCONNECT statement, must be IBM or DB2 to connect with 

DB2 using the Cooperative Processing Option (CPO). 

.........................................................................................................................................................................................................˝.......................................... 

20431 

SQL data type is incompatible with target parameter %1 

The data types of the SQL table columns must match the data types of fields 

in the target parameter.


.........................................................................................................................................................................................................˝.......................................... 

20432 

SQL data is invalid %1 

The returned SQL data cannot be interpreted. 

.........................................................................................................................................................................................................˝.......................................... 

20460 

Number of SQL arguments is inconsistent with the SQL request 

You can use a minimum of two parameters and a maximum of three 

parameters for SQL statements that issue a SELECT statement. Otherwise 

the minimum and maximum parameters are one and two, respectively. 

.........................................................................................................................................................................................................˝.......................................... 

20461 

Invalid object (host variable) in SQL string 

An object in the SQL statement is invalid. Check that the knowledge base 

does not contain invalid objects. 

.........................................................................................................................................................................................................˝.......................................... 

20462 

Unknown identifier in SQL string 

A parameter in the SQL statement does not exist. 

If this error occurs in an optimized knowledge base, it is probably due to 

using an input argument, output argument, or local variable as a host 

variable in an SQL statement in a function. HPO does not support using 

these types of variables as host variables. 

For more information: See the HPO Installation and Operation Guide for 

your environment. 

.........................................................................................................................................................................................................˝.......................................... 

20463 

Invalid record field or slot in SQL string 

An attempt was made to use a non-record object or slot as a record object. 

Check your SQL statement. 



.........................................................................................................................................................................................................˝.......................................... 

20464 


Invalid object base type in SQL string 

You may only use basic data types in parameters that are part of the SQL 

statement. 

.........................................................................................................................................................................................................˝.......................................... 

20465 

Object not a record or instance in SQL string 

An attempt was made to use a non-record parameter or instance as a record. 

Check your SQL statement. 

.........................................................................................................................................................................................................˝.......................................... 

20466 

Object not a list/set or class in SQL string 

An attempt was made to use an index on a parameter or class that is not a set 

or list. Check your SQL statement. 

.........................................................................................................................................................................................................˝.......................................... 

20467 

Invalid instance or list index in SQL string 

The list index or instance index for an AionDS parameter must be an integer 

literal or an integer parameter. Check your SQL statement. 

.........................................................................................................................................................................................................˝.......................................... 

20468 

List index out-of-bounds 

An attempt was made to use an element in a list beyond the last element that 

exists. Check your SQL statement. 

.........................................................................................................................................................................................................˝.......................................... 

20469 

Static instance does not exist 

The static instance referenced does not exist. Check your SQL statement. 

.........................................................................................................................................................................................................˝.......................................... 

20470 

Invalid file parameter or class in SQL string 

AionDS is unable to execute the SQL statement because the statement 

contains an invalid pointer reference. The characters ->, preceded by the 

name of a class or the name of a parameter whose type is FILE, dereference a 

pointer.


AionDS supports embedded AionDS parameters in SQL strings. For 

example: 

SQL('select * from tbl1 where coll = :pa_table' into pa_list) 

selects all data from tbl1 where col1 is equal to the value in the AionDS 

parameter pa_table and places the result into the AionDS parameter 

pa_list. In this scenario, pa_table is a simple parameter. 

However, AionDS supports record fields from file pointers as well as slots 

from class as host parameters. For example: 

SQL('select * from tbl1 where col1 = :pa_fileptr->.field' 

into pa_list) 

SQL('select * from tbl1 where col1 = :pa_classptr->.slot' 

into pa_list) 

selects all data from tbl1 where col1 is equal to the value of the AionDS 

field pa_fileptr->.field or whose name is in the slot pa_classptr- 

>.slot into the AionDS parameter pa_list. 

This error displays if a pointer is not fully deferenced into a field or a slot, as 

in the following incorrect syntax: 

SQL('select * from tbl1 where col1 = :pa_fileptr->' into 

pa_list) 

SQL('select * from tbl1 where col1 =:pa_classptr->' into 

pa_list) 

.........................................................................................................................................................................................................˝.......................................... 

20500 

VTAM error occurred processing a report 

An error occurred writing a TSL report under CICS, or IMS. 

.........................................................................................................................................................................................................˝.......................................... 

20501 

SAESSEND VTAM link send failed 

During SEND processing, an error occurred that prevented SAES from 

sending a message to its session partner. 



.........................................................................................................................................................................................................˝.......................................... 

20502 


SAESGET VTAM link receive failed 

During GET processing, an error occurred that prevented SAES from 

receiving a message from its session partner. 

.........................................................................................................................................................................................................˝.......................................... 

20503 

SAESGET VTAM link protocol error - unexpected message type (MVS) 

Within SAES and the Transaction Drivers, messages and message types are 

expected in certain sequences. This error message indicates that a message 

was received by SAES properly but the subtype of the message was not what 

was anticipated. 

.........................................................................................................................................................................................................˝.......................................... 

20503 

LU6.2 session error - unexpected message type (WIN/OS2/PM) 

A message was passed between AionDS/Win, AionDS/OS2 or AionDS/PM 

and the IMS data server, the CICS data server, or the MAES region that is 

unrecognizable. This is usually caused by a remote knowledge base 

attempting to display a message, report, or screen. 

.........................................................................................................................................................................................................˝.......................................... 

20504 

SAESGET - unexpected VTAM link protocol error (MVS) 

Before SAES can send a message to its session partner, both partners must be 

ready for the send to take place. The transaction driver will send a change 

direction to indicate that it is ready to receive a message from SAES. SAES 

must receive this change direction before it can send. This error is issued if 

the change direction is not received by SAES prior to SAES attempting to 

send a message to its session partner. 

.........................................................................................................................................................................................................˝.......................................... 

20504 

LU6.2 session error - unexpected request type (WIN/OS2/PM) 

AionDS/Win, AionDS/OS2 or AionDS/PM sent an unknown request type 

to a data server or to MAES. The data server or MAES is the recipient of the 

request type and did not recognize it as a valid request. A frequent cause is 

requesting VSAM data access from the IMS data server or any other illegal 

data access.


.........................................................................................................................................................................................................˝.......................................... 

20506 

Connection to host system is not active 

No communication with the host has been established. Ensure that the 

Communication Manager or DCA Select APPC has been successfully started. 

Check the AionDS system log and consultation trace for other errors that 

may have occurred. 

.........................................................................................................................................................................................................˝.......................................... 

20507 

CPO communication error occurred as a result of a previous error 

CPO communication errors occurred previous to the current request. Check 

the AionDS system log and consultation trace for previous CPO 

communications messages. 

.........................................................................................................................................................................................................˝.......................................... 

20508 

RKB error - Remote consultation start failed 

The remote MAES system was unable to start a consultation to run the 

requested knowledge base. A possible cause is that the MAES MAXTASK 

value has been reached. Check the MAESLOG of the remote MAES system 

for more information, or run the MONITOR knowledge base on the remote 

MAES system to identify how many tasks are active. 

.........................................................................................................................................................................................................˝.......................................... 

20509 

RKB error - Error starting remote knowledge base 

The remote MAES system was unable to start the requested knowledge base. 

The probable causes are an old version of the knowledge base, the knowledge 

base is corrupt, or the remote MAES system cannot find the knowledge base. 

Verify that the knowledge base exists in the same environment as the remote 

MAES system. Check the MAESLOG and the AionDS system log in the 

remote MAES system for other possible errors. 



.........................................................................................................................................................................................................˝.......................................... 

20510 


RKB error - Unexpected error terminating remote consultation 

An error was encountered by CPO in terminating the conversation with the 

remote data server or remote MAES. Check the MAESLOG for any 

problems with the termination of the consultation. Check the MVS Console 

Log for any VTAM error messages. If the remote data server is CICS, check 

the CICS log for related error messages. 

.........................................................................................................................................................................................................˝.......................................... 

20511 

RKB error - Bad HPO name 

The remote MAES system was unable to find the HPO knowledge base 

specified. Check that the name specified for the REMOTE KB process 

object is a load module in a library included in the STEPLIB DD of the 

remote MAES system. 

.........................................................................................................................................................................................................˝.......................................... 

20512 

Remote process object not supported 

The AionDS remote process routines REMOTE CONNECT and 

REMOTE KB require the Cooperative Processing Option (CPO) which is 

not installed. 

.........................................................................................................................................................................................................˝.......................................... 

20515 

LU6.2 session error - Null message returned 

An empty message was received from the remote system. 

.........................................................................................................................................................................................................˝.......................................... 

20516 

RKB error - Remote KB attempted to display a user message 

The remote knowledge base attempted to display a message. This is not 

allowed with CPO processing. Remove the display or the condition which 

caused the display in the remote knowledge base. To discover what caused 

this condition, check the AionDS system log and consultation trace of the 

remote MAES system.


.........................................................................................................................................................................................................˝.......................................... 

20546 

LU6.2 session error - session ALLOCATION failed 

CPO was unable to allocate a session with the host. Check that the 

configuration file has been set up with the suggested parameters. Also, check 

the SNA profile and the PARTNER LU profile for the partner you are 

attempting to access and the transmission profile. This error can also occur if 

you attempt to use DL/I or DB2 and it has not been activated in the remote 

system. 

.........................................................................................................................................................................................................˝.......................................... 

20547 

LU6.2 session error - SEND failed 

CPO was unable to send a message or request through VTAM to the remote 

system. Check that the remote system is still active and functioning. Check 

the MVS console or Netview for VTAM error conditions. 

.........................................................................................................................................................................................................˝.......................................... 

20548 

LU6.2 session error - RECEIVE failed 

Communication with the host abnormally terminated while CPO was 

waiting for a response. Check that the host system is active, that the remote 

system is active and is not in a loop. 

.........................................................................................................................................................................................................˝.......................................... 

20549 

Communications Client rejected APPC startup 

See your vendor’s communication client documentation. 

.........................................................................................................................................................................................................˝.......................................... 

20561 

LU6.2 session error - Invalid system name 

The system name specified in the input record passed by a REMOTE 

CONNECT or REMOTE KB process object referred to an invalid name. 

Check the Communications Client Configuration file for valid names. 



.........................................................................................................................................................................................................˝.......................................... 

20562 


LU6.2 session error - Invalid LOGON MODE 

The LOGON MODE specified in the input record passed to a REMOTE 

CONNECT or REMOTE KB process object does not match the 

Communications Client profile for the LOGON MODE specified for the 

system name. 

.........................................................................................................................................................................................................˝.......................................... 

20563 

LU6.2 session error - Invalid local LU name 

The LU ALIAS specified in the input record passed to a REMOTE 

CONNECT or REMOTE KB process object does not match the 

Communications Client profile for the LU ALIAS specified for that system 

name. 

.........................................................................................................................................................................................................˝.......................................... 

20581 

Unable to load support library for remote functions (MAES.DLL) 

The AionDS CPO support library MAES.DLL or one of the libraries it 

depends on (APPC.DLL or ACSSVC.DLL) could not be loaded. 

Under OS/2, the support libraries must be available in a directory referenced 

by the LIBPATH statement in the CONFIG.SYS file. 

Under Windows, the support libraries must be available in one of the 

following locations: 

1 the current directory 

2 the Windows directory (i.e. C:\WINDOWS) 

3 the Windows system directory (i.e. C:\WINDOWS\SYSTEM) 

4 the directory containing the currently executing copy of ADSW.EXE 

5 one of the directories referenced by the PATH environment variable 

(usually defined in the AUTOEXEC.BAT file)


.........................................................................................................................................................................................................˝.......................................... 

20582 

ASCIIEBCDIC translation failure 

This error normally occurs when the communications client software cannot 

load the Type-G Translation Table. Refer to the CPO Installation 

documentation for the proper installation of this file. 

.........................................................................................................................................................................................................˝.......................................... 

20583 

ASCIIEBCDIC translation table load failure 

The Type-G translation table could not be loaded by the communications 

driver. Refer to the CPO Installation documentation for instructions about 

installing this file. 

.........................................................................................................................................................................................................˝.......................................... 

21300 

Unexpected OS return code (PC/WIN/OS2/PM/SUN/AIX) 

AionDS received an unexpected return code from the operating system. 

Check the integrity of your I/O system. 

.........................................................................................................................................................................................................˝.......................................... 

21300 

Unexpected C/370 runtime error occurred (return code = ‘%4’) (MVS) 

AionDS/MVS received an unexpected return code from the IBM C/370 

runtime library. Record the return code and contact PLATINUM Technical 

Support for AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

21301 

File not found 

An internal error that occurs when a file needed by AionDS cannot be found. 

This error should never be reported to the user, because all file errors are 

trapped and reported in other ways. 

.........................................................................................................................................................................................................˝.......................................... 

21302 

File not open 

The system attempted to operate on a file that was not currently open. 



.........................................................................................................................................................................................................˝.......................................... 

21303 


Insufficient disk space (PC/WIN/OS2/PM/SUN/AIX) 

While attempting to write to disk, AionDS encountered an insufficient disk 

space error from the operating system. 

.........................................................................................................................................................................................................˝.......................................... 

21303 

Dataset not cataloged (MVS) 

The specified file does not exist or is not cataloged. 

.........................................................................................................................................................................................................˝.......................................... 

21303 

File not found (VM) 

The specified file does not exist or cannot be found. 

.........................................................................................................................................................................................................˝.......................................... 

21304 

Dataset member not found (MVS) 

The specified member of a partitioned dataset was not found. 

.........................................................................................................................................................................................................˝.......................................... 

21304 

Member not found (VM) 

The specified library member was not found. 

.........................................................................................................................................................................................................˝.......................................... 

21305 

21305 

Invalid file specification (PC/WIN/OS2/PM/SUN/AIX/VM) 

Invalid dataset specification (MVS) 

The file specification is invalid. Refer to the Installation and Operation Guide 

for your environment for more information about specifying filenames. 

.........................................................................................................................................................................................................˝.......................................... 

21306 

Path not found (PC/WIN/OS2/PM/SUN/AIX) 

An invalid path was specified for a data file. Specify a valid path name and 

retry.


.........................................................................................................................................................................................................˝.......................................... 

21306 

Dynamic dataset allocation error (MVS) 

A data definition (DD) name could not be allocated to a dataset. Check the 

values of the STORAGE-UNIT, SCRATCH-UNIT, and VOLUME- 

SERIAL profile options. 

.........................................................................................................................................................................................................˝.......................................... 

21307 

Too many open files (increase FILES parameter in CONFIG.SYS) 

The operating system reported that too many files were open when AionDS 

attempted to open a new file. Check the application to make sure that it is 

not accidentally leaving files open. If possible, increase the FILES parameter 

in the CONFIG.SYS file. 

.........................................................................................................................................................................................................˝.......................................... 

21308 

Access denied 

An attempt was made to open a file, but access was denied by the operating 

system. 

.........................................................................................................................................................................................................˝.......................................... 

21309 

File is read-only (PC/WIN/OS2/PM/SUN/AIX) 

AionDS attempted to write to a file that is marked read-only. Check the 

filename and file privileges to ensure that the correct file is specified. 

.........................................................................................................................................................................................................˝.......................................... 

21309 

Cannot append to specified dataset (MVS) 

An attempt was made to append to a member of a partitioned dataset. 

.........................................................................................................................................................................................................˝.......................................... 

21310 

Drive is not ready (PC/WIN/OS2/PM/SUN/AIX) 

AionDS attempted to write to a disk drive that was not ready. Correct the 

problem and retry the operation. Check to make sure the diskette is in the 

disk drive. 



.........................................................................................................................................................................................................˝.......................................... 

21310 

21310 


It is not possible to read from specified dataset type (MVS) 

It is not possible to read from specified file type (VM) 

AionDS is not able to open the specified file for input. Check that the 

operating environment supports reading from the type of file specified. 

.........................................................................................................................................................................................................˝.......................................... 

21311 

Sharing violation: file already in use (PC/WIN/OS2/PM/SUN/AIX) 

The operating system reported a sharing violation when AionDS attempted 

to access a file. 

.........................................................................................................................................................................................................˝.......................................... 

21311 

21311 

It is not possible to write to specified dataset type (MVS) 

It is not possible to write to specified file type (VM) 

AionDS is not able to open the specified file for output. Check that the 

operating environment supports writing to the type of file specified. 

.........................................................................................................................................................................................................˝.......................................... 

21312 

21312 

Specified dataset cannot be deleted (MVS) 

Cannot delete given file specification (VM) 

AionDS is not able to delete the specified file. Check that the operating 

environment supports deleting the type of file specified. 

.........................................................................................................................................................................................................˝.......................................... 

21314 

Process aborted due to hard error 

An external process abended with an operating system error (called through 

API).


.........................................................................................................................................................................................................˝.......................................... 

21314 

21314 

Specified dataset is not allocated (MVS) 

Specified filename has not been FILEDEF’d (VM) 

AionDS is not able to open the file specified. The file specification identifies 

a data definition (DD) name that is not defined to the operating 

environment. 

.........................................................................................................................................................................................................˝.......................................... 

21315 

Process aborted due to trap fault (PC/WIN/OS2/PM) 

An external process abended with a trap fault. Typically this is a general 

protection exception, TRAP 13. 

.........................................................................................................................................................................................................˝.......................................... 

21315 

Dataset is in use (MVS) 

AionDS is not able to access the dataset because it is currently in use. This 

error will most likely occur when AionDS detects a System Completion Code 

20C or 210. 

.........................................................................................................................................................................................................˝.......................................... 

21315 

Disk is read-only (VM) 

AionDS is not able to open the CMS file for output because the file resides 

on a minidisk that is linked in read-only mode. 

.........................................................................................................................................................................................................˝.......................................... 

21316 

Process killed 

The external process called through API was killed from an external source. 

For example, the user could kill the process by pressing CTRL+BREAK or the 

operating system could terminate the process. 



.........................................................................................................................................................................................................˝.......................................... 

21317 


Dataset space is exhausted and cannot be extended (MVS) 

AionDS is not able to save a dataset or a member of a partitioned dataset 

because the dataset space is exhausted and cannot be extended. This error 

may occur when the volume on which the dataset resides is full. This error 

will most likely occur when AionDS detects a System Completion Code B37 

or E37. 

.........................................................................................................................................................................................................˝.......................................... 

21317 

Too many files on disk (VM) 

AionDS is not able to save a file because there are too many files on the 

minidisk. 

.........................................................................................................................................................................................................˝.......................................... 

21318 

File locking violation (PC/WIN/OS2/PM/SUN/AIX) 

The operating system reported a locking violation when AionDS attempted 

to access a file. This typically means the file is in use by another user. 

.........................................................................................................................................................................................................˝.......................................... 

21318 

Dataset primary allocation full and no secondary space was requested 

(MVS) 


because the primary allocation has been exhausted and no secondary 

allocation was specified for the dataset. This error will most likely occur 

when AionDS detects a System Completion Code D37. 

.........................................................................................................................................................................................................˝.......................................... 

21318 

Disk full (VM) 

AionDS is not able to save a file because the minidisk is full.


.........................................................................................................................................................................................................˝.......................................... 

21319 

Invalid EXE format - program not runnable by this operating system 

(WIN) 

The operating system reported that an external program is not runnable. 

Check to make sure the program is valid and, if necessary, re-install or rebuild 

the program. 

.........................................................................................................................................................................................................˝.......................................... 

21319 

Dynamic dataset allocation failed (SVC reason code = ‘%5’) (MVS) 

An unexpected dataset allocation failure occurred. Check the SVC reason 

code to try and determine the problem. 

.........................................................................................................................................................................................................˝.......................................... 

21320 

Bad argument passed to the DLL (PC/WIN/OS2/PM) 

The DLL received a bad argument from AionDS. For example, this might 

occur when performing a LIBCALL process or calling an external library 

function. 

.........................................................................................................................................................................................................˝.......................................... 

21320 

User is not authorized to define datasets (MVS/VM) 

AionDS is unable to dynamically create a dataset because the user does not 

have the authorization. This error will most likely occur when AionDS 

detects a System Completion Code 47AC. 

.........................................................................................................................................................................................................˝.......................................... 

21323 

Cannot specify member; filename is already allocated to a member 


a data definition (DD) name and a member name, but the DD name is 

already allocated to a member. 

.........................................................................................................................................................................................................˝.......................................... 

21324 

Specified dataset is not partitioned 


a partitioned dataset, but the dataset is physical sequential. This error will 

most likely occur when AionDS detects a System Completion Code 330. 



.........................................................................................................................................................................................................˝.......................................... 

21325 


Must specify member of the partitioned dataset 

AionDS is not able to allocate the file specified. The file specification 

identifies a physical sequential dataset, but the dataset is partitioned. 

.........................................................................................................................................................................................................˝.......................................... 

21326 

Dataset has unsupported organization 

AionDS is not able to allocate the file specified, because the dataset 

organization is not supported. A partitioned or physical sequential dataset 

must be specified. 

.........................................................................................................................................................................................................˝.......................................... 

21327 

No space in partitioned dataset directory 

AionDS is not able to save a member of a partitioned dataset because the 

directory space has been exhausted. Check the number of directory blocks 

that are allocated for the PDS. 

.........................................................................................................................................................................................................˝.......................................... 

21328 

Unexpected CMS file processing error (completion code ‘%5’) 

An unexpected CMS file processing error occurred. 

.........................................................................................................................................................................................................˝.......................................... 

21330 

Disk not accessed 

AionDS is not able to find a CMS file because the minidisk is not accessed. 

.........................................................................................................................................................................................................˝.......................................... 

21331 

Invalid filemode 

An invalid CMS filemode was specified. Check the file specification. 

.........................................................................................................................................................................................................˝.......................................... 

21332 

Unable to open file 

An unexpected CMS file processing error occurred opening a file.


.........................................................................................................................................................................................................˝.......................................... 

21333 

Error during file close 

An unexpected CMS file processing error occurred closing a file. 

.........................................................................................................................................................................................................˝.......................................... 

21334 

Error during write to file 

An unexpected CMS file processing error occurred writing to a file. 

.........................................................................................................................................................................................................˝.......................................... 

21335 

Error during read from file 

An unexpected CMS file processing error occurred reading from a file. 

.........................................................................................................................................................................................................˝.......................................... 

21337 

Requested space not available (MVS) 


because the volume on which the dataset resides is full. This error will most 

likely occur when AionDS detects a System Completion Code 4714. 

.........................................................................................................................................................................................................˝.......................................... 

21337 

Invalid logical record length (VM) 

AionDS is not able to access the CMS file because the logical record length is 

invalid. 

.........................................................................................................................................................................................................˝.......................................... 

21338 

Dataset member not found or other error occurred during OPEN 

AionDS is not able to open a member of a partitioned dataset. This error will 

most likely occur when AionDS detects a System Completion Code 013. 

.........................................................................................................................................................................................................˝.......................................... 

21339 

Dataset is already cataloged (MVS) 

AionDS is not able to catalog the file with the specified name because it is 

already cataloged. 



.........................................................................................................................................................................................................˝.......................................... 

21339 


File already exists (VM) 

AionDS is not able to create the file with the specified name because it 

already exists. 

.........................................................................................................................................................................................................˝.......................................... 

21350 

Knowledge base (ENQ) failure 

An unexpected ENQ failure occurred accessing the knowledge base 

partitioned dataset. 

.........................................................................................................................................................................................................˝.......................................... 

21352 

Knowledge base end-access (DEQ) failure 

An unexpected DEQ failure occurred releasing the knowledge base 

partitioned dataset. 

.........................................................................................................................................................................................................˝.......................................... 

22505 

Left Margin is less than 1 

A TSL command has set the left margin to less than the leftmost position. 

Check any &LM and &LI commands in the text. If this error is issued for a 

report, check the Left Margin property of the report object. 

.........................................................................................................................................................................................................˝.......................................... 

22510 

Passed ‘%’ to function when already past the last element of list, set or 

class 

AionDS is unable to execute a function because there are not enough 

argument values available. When you execute a function for each value in a 

list or set, or for each instance in a group of instances, you must make sure 

that there are enough elements or instances for each time the function 

executes. 

For example, if a function takes two elements of a list as arguments each time 

it executes, the number of elements in the list must be divisible by two. If the 

list contains an odd number of elements, the function will be unable to 

execute for the final element.


.........................................................................................................................................................................................................˝.......................................... 

22511 

Difference between Right and Left Margins is too large (more than 510) 

The specified line width is larger than the limit within AionDS. The 

maximum number of characters allowed in a line is 511. 

Check the Left Margin and Right Margin properties and the use of &LM, 

&RM, &LI, and &RI. The difference between the right and left margin 

values must be less than or equal to 510. 

.........................................................................................................................................................................................................˝.......................................... 

22528 

Error during I/O to report output file 

AionDS is unable to write or close the output file. Any restriction on writing 

or closing a file for read/write will cause this error (for example, disk full). 

.........................................................................................................................................................................................................˝.......................................... 

22536 

This command not allowed inside a title or footer 

Certain TSL commands, such as &TITLE, &FOOTER, &PG, and so on, 

are not allowed inside a report title or footer. 

.........................................................................................................................................................................................................˝.......................................... 

22542 

Instance does not exist 

The instance referenced within the TSL text does not exist. 

.........................................................................................................................................................................................................˝.......................................... 

22553 

%is, % and %current are prohibited when method is invoked on a class 

AionDS cannot perform the specified action because %, %IS, and 

%CURRENT refer to the current instance and there is no current instance. 

The message was sent to a class rather than an instance, so no instance has 

been identified as the current instance. 

.........................................................................................................................................................................................................˝.......................................... 

22559 

Right Margin is larger than Line Length 

In a report, the right margin can be no greater than the line length. Check 

the Right Margin and Line Length properties and uses of the &RM and &RI 

commands. 



.........................................................................................................................................................................................................˝.......................................... 

22560 


Top Margin is less than 0 

The specified top margin is above the top of the page. Check the Top 

Margin property and uses of the &TM command. 

.........................................................................................................................................................................................................˝.......................................... 

22561 

Bottom Margin is less than 0 

The specified bottom margin is below the bottom of the page. Check the 

Bottom Margin property and uses of the &BM command. 

.........................................................................................................................................................................................................˝.......................................... 

22562 

Top Margin + Bottom Margin is greater than or equal to Page Length 

The specifications of the top and bottom margin allow no room for text. 

Check the Top Margin, Bottom Margin, and Page Length properties and 

uses of the &TM and &BM commands. 

.........................................................................................................................................................................................................˝.......................................... 

22563 

Right Margin is larger than window width 

The right margin can be no greater than the width of the window. Check 

uses of the &RM and &RI commands. 

.........................................................................................................................................................................................................˝.......................................... 

22572 

Command not allowed in a &TBL command 

There is a command used in the &TBL command that is not allowed. Check 

the &TBL command and any messages that are included in the table by 

means of the &MSG command or message passing, such as with the 

&SEND command. 

.........................................................................................................................................................................................................˝.......................................... 

22575 

Column is too wide 

There is column text in a table that exceeds the line length (in a report) or the 

window width (in other objects). Check the data for the table and other text 

that appears in the table.


.........................................................................................................................................................................................................˝.......................................... 

22576 

Real number has too many digits; use exponential notation 

(%param:width) 

AionDS cannot substitute a real number value because the number has too 

many digits in the specified format (%param:width:precision). To correct 

this, use the %param:width format. The number will then appear in 

exponential notation. 

.........................................................................................................................................................................................................˝.......................................... 

22578 

Command not allowed in the title of a table 

There is a command used in the title specification of the &TBL command 

that is not allowed. Check the title and any messages that are included in the 

title by means of the &MSG command or message passing, such as with the 

&SEND command. 

.........................................................................................................................................................................................................˝.......................................... 

22581 

The table’s title takes more lines than are available per page 

The longest column title takes more lines than are available on a page. The 

available lines per page are calculated by subtracting the top margin and the 

bottom margin from the page length. 

Check the title and any messages that are included in the title by means of 

the &MSG command or message passing, such as with the &SEND 

command. 

Also check the Top Margin, Bottom Margin, and Page Length properties and 

uses of the &TM and &BM commands. 

.........................................................................................................................................................................................................˝.......................................... 

22591 

Send Up may not be used in a title or footer 

The &SEND(... UP) or %UP statement is not allowed in a report’s title or 

footer. Change the text to a regular SEND or another statement. 



.........................................................................................................................................................................................................˝.......................................... 

22592 


No current instance for slot or method, or non-unique instance name 

AionDS cannot perform an action on the specified instance. This error can 

occur under two types of circumstances: 

■ The statement refers to a slot of the current instance or sends a message 

to the current instance but the message has been sent to a class rather 

than an instance, so there is no current instance. 

■ The statement refers to a static instance by name, but at the time the 

statement is executed there is more than one instance with the specified 

name. To eliminate the error, change the instance reference from 

%instance_name to %classref(%instance_name). 

.........................................................................................................................................................................................................˝.......................................... 

22593 

Non-unique instance name used in TSL 

AionDS cannot perform an action on the specified instance. The statement 

refers to a static instance by name, but at the time the statement is executed 

there is more than one instance with the specified name. To eliminate the 

error, change the instance reference from %instance_name to 

%classref(%instance_name). 

.........................................................................................................................................................................................................˝.......................................... 

22600 

Invalid pointer value 

AionDS cannot perform an action on the specified instance because the 

pointer is invalid. Check whether the instance has been deleted. 

.........................................................................................................................................................................................................˝.......................................... 

22601 

Illegal attempt to access private slot 

AionDS cannot access the slot at this point in the consultation because the 

slot is not in the current context and the Public property of the slot is FALSE. 

Private slots are only accessible from within the parent class or a class below 

the parent in the hierarchy.


.........................................................................................................................................................................................................˝.......................................... 

22602 

Illegal attempt to access private method 

AionDS cannot access the method at this point in the consultation because 

the method is not in the current context and the Public property of the 

method is FALSE. Private methods are only accessible from within the 

parent class or a class below the parent in the hierarchy. 

.........................................................................................................................................................................................................˝.......................................... 

22604 

%Currentclass unexpected 

%CURRENTCLASS was used in a TSL property when there was no current 

class. 

Make sure there is a current class whenever using the %CURRENTCLASS 

substitution in TSL. 

.........................................................................................................................................................................................................˝.......................................... 

22699 

Error occurred processing remote report 

An error occurred terminating a report that was being written to a remote 

device. Check the AionDS system log for more information. 

The printer is probably not properly defined in your CICS or IMS system. 

.........................................................................................................................................................................................................˝.......................................... 

23312 

%1%2 v%3 has invalid header format 

The format of the knowledge base header file for this knowledge base is 

invalid. Check that the proper directory is specified and that the knowledge 

base has been upgraded to the appropriate version of AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

26318 

Invalid field for MARK key 

AionDS cannot execute the MARK function because the cursor is not 

positioned in a menu or window in which this function is available. 

Reposition the cursor to an appropriate location before pressing the MARK 

key again. 



.........................................................................................................................................................................................................˝.......................................... 

26320 


Invalid cursor position for EXECUTE key 

AionDS cannot perform the EXECUTE function because the cursor is not 

positioned in a window in which this function is available. Keys that perform 

this function (such as the FILE, ENTER, or UNKNOWN keys) are only 

available in windows owned by a message, slot, or parameter. 

.........................................................................................................................................................................................................˝.......................................... 

26321 

UNKNOWN is not valid here 

AionDS cannot accept UNKNOWN as a valid response for this parameter or 

slot. 

.........................................................................................................................................................................................................˝.......................................... 

26322 

Invalid row for selection 

AionDS cannot perform a selection because the cursor is not positioned in an 

appropriate location in the menu. Reposition the cursor to a line in the 

menu that contains a response before pressing the key again. 

.........................................................................................................................................................................................................˝.......................................... 

26323 

Certainty value not found 

You have entered a value without specifying the certainty factor. Enter the 

certainty factor. 

.........................................................................................................................................................................................................˝.......................................... 

26324 

Certainty value out of legal range 

You have entered a certainty factor that is less than -1 or greater than 1. 

Reenter the certainty factor. 

.........................................................................................................................................................................................................˝.......................................... 

26325 

Certainty value format is invalid 

The certainty factor is invalid. You must specify a real number between -1 

and 1, inclusive. The format allows a sign, digits, and one decimal point.


.........................................................................................................................................................................................................˝.......................................... 

26326 

Length of string exceeds size constraint 

The TDL for the string specifies CHECKLENGTH and the maximum size. 

You have attempted to enter a string whose length exceeds the applicationdefined 

limit. 

.........................................................................................................................................................................................................˝.......................................... 

26327 

Length of set or list is inconsistent with size constraint 

The TDL for the list or set specifies CHECKLENGTH and the maximum 

number of elements. You have attempted to enter more elements than the 

application has defined to allow. 

.........................................................................................................................................................................................................˝.......................................... 

26328 

Invalid selection character 

You are using characters in a Selection Input window that do not match the 

characters in the SELECT-INPUT profile option. Either change the profile 

or use the correct characters. 

.........................................................................................................................................................................................................˝.......................................... 

26329 

No questions have been answered 

You have attempted to back up or restart the consultation before the display 

of a message or graph and before any user sourcing has occurred. The 

consultation has not established a point at which to back up or restart. 

Continue the consultation. 

.........................................................................................................................................................................................................˝.......................................... 

26330 

No further information is available 

You have issued the EXPLAIN command for an object that does not contain 

any explanation. Continue the consultation. 

.........................................................................................................................................................................................................˝.......................................... 

26331 

Unable to backup 

You have issued the BACKUP command when the BACKUP-ENABLE 

profile option is set to NO. Change the profile option and execute the 

consultation again. 



.........................................................................................................................................................................................................˝.......................................... 

26332 


Browse field is not defined 

You have issued the TRACE command from a screen that does not contain a 

Browse window. The window is required to display the contents of the trace 

file. 

.........................................................................................................................................................................................................˝.......................................... 

26333 

Explanation is not enabled; trace-level must be greater than zero 

You have issued an Explanation facility command, such as HOW, WHAT, 

or WHY when the TRACE-LEVEL profile option is set to 0. Change the 

profile option to 1, or greater. 

.........................................................................................................................................................................................................˝.......................................... 

26334 

Trace is not enabled or an output error occurred 

AionDS cannot open the trace file. Check that the TRACE-LEVEL profile 

option is not set to 0. 

.........................................................................................................................................................................................................˝.......................................... 

26335 

Set may not have duplicate elements 

You cannot enter this value because an element with the same value already 

exists in the set. Enter a different value. 

.........................................................................................................................................................................................................˝.......................................... 

26336 

Set can only have one element when certainty 1.0 exists 

You cannot enter another value into the certainty set because the certainty set 

already contains a value with a certainty factor of 1.0. 

.........................................................................................................................................................................................................˝.......................................... 

26337 

Invalid yes/no value 

The value entered for “yes” or “no” is invalid. Enter the correct value. 

.........................................................................................................................................................................................................˝.......................................... 

26338 

Invalid integer format 

The value entered for an integer contains characters other than the digits 0 to 

9, inclusive. Enter the correct value.


.........................................................................................................................................................................................................˝.......................................... 

26339 

Invalid numeric format 

The value entered for a number contains characters other than a plus or 

minus sign, a single decimal point, or the digits 0 to 9, inclusive. Enter the 

correct value. 

.........................................................................................................................................................................................................˝.......................................... 

26340 

Invalid date format 

The value entered for a date is not in the correct format, or is for a date 

before January 1, 1900. Enter the correct value. 

.........................................................................................................................................................................................................˝.......................................... 

26341 

Invalid time format 

The value entered for a time is not in the correct format, or exceeds 

23:59:59.99 hours. Enter the correct value. 

.........................................................................................................................................................................................................˝.......................................... 

26343 

Element with certainty 1.0 will be the only entry in the set 

You have entered a value in a certainty set with a certainty factor that 

prohibits additional entries. 

.........................................................................................................................................................................................................˝.......................................... 

26364 

No matching objects 

You have attempted to issue an Explanation facility command, such as 

HOW, WHY, or WHAT, when there are no objects that can be explained. 

The cursor might not be in any window. Check that the cursor is in a 

window before issuing the command or pressing the function key that 

invokes the Explanation facility command. 

.........................................................................................................................................................................................................˝.......................................... 

26366 

Empty string is not valid here 

The TDL for the string includes the NOEMPTY attribute. You must enter a 

value or UNKNOWN. 



.........................................................................................................................................................................................................˝.......................................... 

26367 


Empty list/set is not valid here 

The TDL for a list or set includes the NOEMPTY attribute. You must enter 

at least one value or UNKNOWN. 

.........................................................................................................................................................................................................˝.......................................... 

26368 

Only one item may be selected 

You have attempted to select more than one item from a list. Choose the 

correct item. 

.........................................................................................................................................................................................................˝.......................................... 

26369 

Invalid cursor position for EXPLAIN 

You have issued the EXPLAIN command outside of any of the windows 

displayed on the screen. Move the cursor into a window and reissue the 

command. 

.........................................................................................................................................................................................................˝.......................................... 

26370 

No explain window associated with current object 

You have issued an EXPLAIN command from a Display object that does not 

have an Explain window. Either disallow the EXPLAIN command from the 

Display object or create an Explain window. 

.........................................................................................................................................................................................................˝.......................................... 

26371 

Cursor is not inside a printable window 

You have issued a PRINTWINDOW command while the cursor is outside 

of a printable window. Move the cursor into a printable window and reissue 

the command. 

.........................................................................................................................................................................................................˝.......................................... 

26373 

The data does not match the input mask 

You attempted to enter a value that does not match the mask. Correct the 

entry.


.........................................................................................................................................................................................................˝.......................................... 

26374 

Invalid field for Select function; must be a menu 

You have issued a SELECT command when the cursor is not in a Selection 

Input window. Move the cursor and reissue the command. 

.........................................................................................................................................................................................................˝.......................................... 

26375 

Delete system function only valid when sourcing a Class 

AionDS was not sourcing a class when you pressed a function key that is 

bound to the DELETE system function. Perform a different operation. 

.........................................................................................................................................................................................................˝.......................................... 

26378 

No command line associated with the current display 

You attempted to issue a command from the command line in a Display 

object that does not have a Command-line window defined. Either disallow 

commands from this Display object or add the window. 

.........................................................................................................................................................................................................˝.......................................... 

26379 

No options window associated with the current display 

You attempted to issue an OPTIONS command from a Display object that 

does not have an Options window defined. Either disallow the OPTIONS 

command from this Display object or add the window. 

.........................................................................................................................................................................................................˝.......................................... 

26393 

Invalid file specification 

The filename specified for a PRINTWINDOW command is invalid. Check 

that the name follows the file naming conventions for the operating system 

you are using and reissue the command. 

.........................................................................................................................................................................................................˝.......................................... 

26394 

Instance is static; cannot be deleted 

You pressed a function key assigned to the DELETE system function while 

the cursor was on a static instance. You can only delete dynamic instances. 

Choose a different instance. 



.........................................................................................................................................................................................................˝.......................................... 

26396 


No input window associated with the current display 

You attempted to issue a STORE or PRINTWINDOW command from a 

Display object that does not have an Input window defined. The Input 

window is used to receive the filename. Either disallow these commands 

from the Display object or add the window. 

.........................................................................................................................................................................................................˝.......................................... 

26397 

No objects window associated with the current display 

You attempted to issue a backup or restart command from a Display object 

that does not have an Objects window defined. The Objects window is used 

to display the objects from which you can make your selection. Either 

disallow these commands from the Display object or add the window. 

.........................................................................................................................................................................................................˝.......................................... 

26398 

No questions which have been answered are allowed to be backed up to 

You issued the BACKUP command before executing or sourcing an object 

for which backing up is allowed. If you want to back up to an object, you 

must specify TRUE in the Backup property for the object. 

.........................................................................................................................................................................................................˝.......................................... 

26399 

Backup dataset is not allocated 

AionDS could not execute the Consultation Monitor Backup command 

because the backup dataset could not be allocated. Check the value of the 

SCRATCH-UNIT profile option. 

.........................................................................................................................................................................................................˝.......................................... 

28617 

Incorrect password; try again 

The knowledge base is protected by a different password. Try again. 

.........................................................................................................................................................................................................˝.......................................... 

28630 

Unable to set User-password; Owner-password does not exist 

To use the Authorization feature, you must first set up an owner password for 

the knowledge base.


.........................................................................................................................................................................................................˝.......................................... 

28635 

At least two files must be selected for comparison 

You attempted to run a comparison with fewer than two files. Select two or 

more files and retry the comparison. 

.........................................................................................................................................................................................................˝.......................................... 

28801 

Must specify a knowledge base name 

You attempted to execute a knowledge base without specifying the name. 

Try again. 

.........................................................................................................................................................................................................˝.......................................... 

28802 

Invalid knowledge base version 

The knowledge base version is incorrect or the version cannot be found. 

Check that you are using the correct version of the knowledge base and try 

again. 

.........................................................................................................................................................................................................˝.......................................... 

28803 

Invalid knowledge base name; invalid character 

The knowledge base name must conform to the file naming conventions of 

the operating system. You have specified a name that contains a character 

that cannot be used as part of a filename for this operating system. Check the 

name and try again. 

.........................................................................................................................................................................................................˝.......................................... 

28804 

Invalid knowledge base name; exceeds 8 characters 

The knowledge base name must conform to the file naming conventions of 

the operating system. The operating system does not allow filenames to 

exceed eight characters, excluding a version number suffix. Check the name 

and try again. 

.........................................................................................................................................................................................................˝.......................................... 

28805 

Saved form of %1%2 v%3 not found 

The knowledge base directory does not contain the “save format” files. 

Import the knowledge base and try again. 



.........................................................................................................................................................................................................˝.......................................... 

28807 


Incorrect password; access to knowledge base denied 

You have entered a password three times and failed. You cannot use AionDS 

until you exit and restart. Check with the knowledge base administrator for 

the password. 

.........................................................................................................................................................................................................˝.......................................... 

28808 

%1%2 v%3 cannot be loaded; saved form is incompatible 

The knowledge base is for an incompatible version of AionDS. You must 

import the knowledge base before you can access it. You may have to run a 

PLATINUM-supplied upgrade program before the knowledge base is usable. 

.........................................................................................................................................................................................................˝.......................................... 

28810 

Knowledge base string file mode switch failed 

An internal error occurred that is most likely related to a failure of the 

operating system, especially in a network environment. Contact your system 

manager. If the problem persists, contact PLATINUM Technical Support 


.........................................................................................................................................................................................................˝.......................................... 

28821 

Rerun file not found 

The rerun file specified in the STORE-FILE profile option cannot be found. 

Check whether the rerun file is missing, named incorrectly, or corrupted. If 

the file is specified incorrectly, change the profile option to designate the 

correct file. 

.........................................................................................................................................................................................................˝.......................................... 

28822 

Unable to open/read rerun file 

The rerun file does not exist, cannot be found, or is protected. Check that 

you specified the filename and location correctly. Contact your system 

manager for further advice. 

.........................................................................................................................................................................................................˝.......................................... 

28824 

KB property is read only 

You attempted to modify a knowledge base property that is read-only.


.........................................................................................................................................................................................................˝.......................................... 

28825 

Passwords are write only 

You cannot read a password entry. Password are write-only. 

.........................................................................................................................................................................................................˝.......................................... 

28826 

Invalid boolean value 

You attempted to specify an invalid Boolean value. Make sure the value 

designated for the Boolean is either TRUE or FALSE. 

.........................................................................................................................................................................................................˝.......................................... 

28829 

This will terminate your application program. 

The end-user chose the Close item from the system menu of the main 

application window. Press ‘OK’ to quit the program or ‘Cancel’ to continue. 

.........................................................................................................................................................................................................˝.......................................... 

28850 

Knowledge base %1%2 v%3 not found 

The knowledge base does not exist in the directory specified. Check the 

directory and the filename and try again. 

.........................................................................................................................................................................................................˝.......................................... 

28851 

Cannot create %1%2 v%3; may already exist 

The specified knowledge base cannot be created. This version may already 

exist. 

.........................................................................................................................................................................................................˝.......................................... 

28853 

No knowledge bases found - %1 

You attempted to access a knowledge base that could not be found. No 

knowledge bases were found in the specified directory. 

.........................................................................................................................................................................................................˝.......................................... 

28854 

Knowledge base %1%2 v%3 is in use 

The knowledge base is being used by another copy of AionDS. Contact your 

system manager. 



.........................................................................................................................................................................................................˝.......................................... 

28855 


Insufficient disk space for copy of knowledge base 

The copy of the specified knowledge base cannot be created because there is 

insufficient diskspace. Increase available disk space and try again. 

.........................................................................................................................................................................................................˝.......................................... 

28859 

Invalid or missing WINLIB; file not found 

The AION path is invalid or missing. The WINLIB.1 directory, which 

contains the predefined graphical window library, must be on the AION 

path. 

.........................................................................................................................................................................................................˝.......................................... 

32510 

Record is locked by another process 

AionDS is unable to perform the GETREC operation because the record is 

locked by another process. The other process has access to the record because 

the knowledge base opened the file with the SHARE option to the 

OPENFILE statement. 

To correct this situation, either free the record from the other program and 

retry the GETREC operation, or use the OPENFILE statement without the 

SHARE option. 

.........................................................................................................................................................................................................˝.......................................... 

32526 

Retry access? 

AionDS is unable to perform the GETREC operation because the record is 

locked by another process. Answer YES if you want AionDS to try and access 

the record again, or NO if you want AionDS to continue without the record. 

AionDS only presents this message when the OPENFILE or the GETREC 

statement contains the RETRY option. You can avoid this prompt by 

removing the RETRY option from these statements. In this case, if AionDS 

is unable to access a record, it does not display the prompt and does not 

attempt to access the record again.


.........................................................................................................................................................................................................˝.......................................... 

32532 

Attempt to add duplicate key 

This is an internal error condition. If you receive this error, contact 

PLATINUM Technical Support for AionDS. 

Caution: This error code number is the same as a message code number 

for another error. The messages are listed by the error code number. Refer to 

the section “Table for converting error codes” on page 1-37 for more 

information. 

.........................................................................................................................................................................................................˝.......................................... 

32533 

Invalid record number 

The KDL SELECT statement specifies an invalid record number. Check 

that the record number is greater than zero. 

.........................................................................................................................................................................................................˝.......................................... 

32702 

dBASE CLOSEFILE failed 

AionDS is unable to close the database file. Check whether the data in the 

file is corrupted. 

.........................................................................................................................................................................................................˝.......................................... 

32703 

dBASE OPENFILE failed 

AionDS is unable to open the database or index file. Check that the 

database, index, and associated memo file are present. This error can also be 

due to an attempt to open an index file without first opening the database 

file. 

.........................................................................................................................................................................................................˝.......................................... 

32704 


The OPENFILE statement contains an option other than TRAP. This 

statement requires that either no option or the TRAP option be specified. 



.........................................................................................................................................................................................................˝.......................................... 

32705 


Invalid record I/O open mode given 

An invalid open mode was specified in an OPENFILE statement. Check the 


.........................................................................................................................................................................................................˝.......................................... 

32706 

dBASE SELECT failed 

AionDS is unable to perform the SELECT operation. If the SELECT 

statement contains a key value, the index file must be open before the 

SELECT can be performed. This error could also be due to a corrupted 

index file. 

.........................................................................................................................................................................................................˝.......................................... 

32707 

Invalid record selection string given 

The SELECT statement contains a selection string other than FIRSTREC, 

LASTREC, FORWARD, or BACKWARD. This statement must contain 

either FIRSTREC, LASTREC, FORWARD, or BACKWARD, or no 

selection string. 

.........................................................................................................................................................................................................˝.......................................... 

32710 

GETREC open mode must be UPDATE 

The GETREC statement contains a mode other than UPDATE. This 

statement must contain either UPDATE or no mode specification. 

.........................................................................................................................................................................................................˝.......................................... 

32711 

dBASE DELETEREC failed 

AionDS is unable to perform the DELETEREC operation. This error can 

occur if the record does not exist or if the database file is corrupted. 

.........................................................................................................................................................................................................˝.......................................... 

32712 

dBASE PUTREC failed 

AionDS is unable to update the database. Check for a missing or incorrectlynamed 

memo file, an incorrect index file, or a full disk.


.........................................................................................................................................................................................................˝.......................................... 

32713 

Invalid PUTREC mode given 

The PUTREC statement specifies an incorrect mode. The valid modes are 

ADD and UPDATE. You cannot specify ADD for a read-only file and you 

cannot specify UPDATE for a file that was opened for append only. 

.........................................................................................................................................................................................................˝.......................................... 

32714 

dBASE GETREC attempted at end-of-file 

An attempt was made to read past the end of the file. 

.........................................................................................................................................................................................................˝.......................................... 

32715 

Problem advancing record pointer 

AionDS cannot get the next record because the database is corrupted in some 

way. 

.........................................................................................................................................................................................................˝.......................................... 

32716 

Sharing violation: record already in use 

AionDS was unable to retrieve a dBASE record because it is currently locked 

by another process. 

.........................................................................................................................................................................................................˝.......................................... 

32717 

Sharing violation: file already in use 

AionDS was unable to open a database or index file because it is currently in 

use by another process. 

.........................................................................................................................................................................................................˝.......................................... 

32730 

Bad record format; field data truncated 

The record length is different than what the record definition requires. 

Check that the file was created with the same record definition. 

.........................................................................................................................................................................................................˝.......................................... 

32731 

Problem writing to memo file 

AionDS is unable to write to a memo file. Check whether the memo file is 

missing, named incorrectly, or corrupted. 



.........................................................................................................................................................................................................˝.......................................... 

32732 


dBASE record does not exist 

AionDS tried to select a record that is not in the database. Either the record 

has been deleted from the database or the specified record number is greater 

than the total number of records in the file. 

.........................................................................................................................................................................................................˝.......................................... 

32733 

Partial match on index key 

A SELECT statement contains a key that can be found in the database, but 

the value in the database has more characters than the key in the SELECT 

statement. 

For example, this error would occur if the SELECT statement specified the 

key JOHN and the database contained the key JOHNSON. 

.........................................................................................................................................................................................................˝.......................................... 

32734 

Index key does not exist 

No record in the database matches the key specified in the SELECT 

statement. 

.........................................................................................................................................................................................................˝.......................................... 

32735 

File not found 

AionDS is unable to find the file specified in the OPENFILE statement. 

Check whether the file is present in the appropriate location and named 

correctly. 

.........................................................................................................................................................................................................˝.......................................... 

32736 

File not opened for reading 

AionDS is unable to read from the file because it was opened for append 

only. 

.........................................................................................................................................................................................................˝.......................................... 

32737 

File must be a database file, not an index or memo file 

AionDS attempted to execute a record I/O statement (for example, 

GETREC, PUTREC, or DELETEREC) on an index or memo file.


.........................................................................................................................................................................................................˝.......................................... 

32738 

Record must first be retrieved for UPDATE 

AionDS is unable to perform a PUTREC operation with the UPDATE 

option because the record does not have update access. You must use 

GETREC with the UPDATE option before using PUTREC with the 

UPDATE option. 

.........................................................................................................................................................................................................˝.......................................... 

32739 

File opened for reading only 

AionDS is unable to write data to the database with a PUTREC statement 

because the database file is only open with read access. 

.........................................................................................................................................................................................................˝.......................................... 

32740 

Select mode cannot be LASTREC or BACKWARD 

AionDS is unable to perform a PUTREC operation while processing a file in 

a backward direction. To correct this, use a SELECT statement specifying 

FIRSTREC or FORWARD before the PUTREC statement. 

.........................................................................................................................................................................................................˝.......................................... 

32741 

Unable to load support library for dBASE (ADSDB4DB.DLL) 

To perform dBASE operations under OS/2, the ADSDB4DB.DLL file must 

exist in a directory specified in the LIBPATH environment variable. 

.........................................................................................................................................................................................................˝.......................................... 

32742 

Problem reading from memo file 

AionDS is unable to read from a memo file. Check whether the memo file is 

missing, named incorrectly, or corrupted. Also, check whether the DBASE- 

VERSION profile option is consistent with the memo file type. For a memo 

file created with dBASE III, this option must have the value III, and for 

dBASE IV, the value must be IV. 




If you are running AionDS under DOS, verify that a CONFIG.AIA file has 

been set up with the HIGHKERNEL YES option. This option must be 

specified in order to read memo files. 

For more information: See the AionDS Installation and Operation 

Guide for information. 

.........................................................................................................................................................................................................˝.......................................... 

32743 

Memo length cannot exceed 32K bytes 

AionDS is unable to write to a memo file because the memo is larger than 32 

KB (32,768 bytes). 

.........................................................................................................................................................................................................˝.......................................... 

32744 

Unable to load support module for dBASE (%1DB4.DLL) 

where 

%1 version information 

To perform dBASE operations under DOS, %1DB4.DLL must exist in a 

directory specified in the AION environment variable. 

.........................................................................................................................................................................................................˝.......................................... 

32801 

Database file not found or invalid 

AionDS is unable to load or update a class with information from the 

database because it cannot locate the database file. Check that the database 

file is present and accessible. 

.........................................................................................................................................................................................................˝.......................................... 

32802 

Index file not found or invalid 


database because it cannot locate the index file. Check that the index file is 

present and accessible.


.........................................................................................................................................................................................................˝.......................................... 

32803 

Unable to update all the modified instances 

AionDS cannot complete execution of the DBMS(UPDATE) statement 

because it encountered a database error for one or more instances. The 

instances that were not updated are reported in the AionDS consultation 

trace, under error 32805. 

.........................................................................................................................................................................................................˝.......................................... 

32804 

Data Integrity Check failed 

AionDS did not update an instance in the database because the current data 

for the instance on disk is not the same as when it was first read into AionDS. 

AionDS checked the data because the Data Integrity Check property in the 

access method is TRUE. 

.........................................................................................................................................................................................................˝.......................................... 

32805 

Problem occurred updating %1 

AionDS is unable to execute the DBMS(UPDATE) statement for this 

instance. The error message displayed immediately after this message, in the 

AionDS consultation trace, identifies the specific problem. 

.........................................................................................................................................................................................................˝.......................................... 

32806 

Access Method not supported by current environment 

AionDS is unable to access the database or file because the knowledge base 

uses an access method that is not available in the operating environment. 

.........................................................................................................................................................................................................˝.......................................... 

32807 

Unable to update new instances using QSAM access method 

Dynamically created instances cannot be updated using the QSAM access 

method with ADI. Only instances that are loaded may be updated using 

QSAM. 



.........................................................................................................................................................................................................˝.......................................... 

32808 


Unable to load VSAM data using key; KSDS or ESDS path expected 

AionDS was not able to load VSAM data using ADI because the Key Field or 

Alternate Key Field property of the Access Method was specified, but the 

dataset type is not a KSDS or an ESDS path. 

.........................................................................................................................................................................................................˝.......................................... 

32809 

Unable to update instance using VSAM access method; no key field 

specified 

AionDS was not able to update VSAM data using ADI because the dataset 

type is a KSDS or an ESDS path, but the Key Field property of the Access 

Method was not specified. 

.........................................................................................................................................................................................................˝.......................................... 

32810 

Unable to update instance; record not found 

AionDS was not able to update VSAM data using ADI because the record 

could not be found. Check the Selection Criteria property of the Access 

Method. 

.........................................................................................................................................................................................................˝.......................................... 

33232 

Negative value in stacked or surface graph 

AionDS is unable to display negative data values in graphs specified as 

STACKED or SURFACE. Examine the AionDS consultation trace and 

modify the knowledge base so that the graph contains no negative values. 

.........................................................................................................................................................................................................˝.......................................... 

33233 

X-Data not allowed in multiple element, side by side bar chart 

AionDS is unable to display a graph because the specified type of graph does 

not support x-data values. To correct this, modify the graph specification in 

the knowledge base.


.........................................................................................................................................................................................................˝.......................................... 

33234 

Invalid x-Data; ranges overlap 

AionDS is unable to display a graph because the width of the bars is 

incorrectly specified. Modify the x-Data values of the graph so that the bars 

do not overlap. 

.........................................................................................................................................................................................................˝.......................................... 

33235 

Invalid amount of x-Data parameters 

AionDS is unable to display a graph because the number of parameters listed 

in the x-Data Values property is inappropriate to the type of graph. For a pie 

chart, the x-Data Values property must be empty. For a line graph, this 

property can be empty or can contain one parameter name. For a bar chart, 

this property can be empty or can contain two parameter names. 

.........................................................................................................................................................................................................˝.......................................... 

33236 

Legend length inconsistent with number of data elements 

AionDS is unable to display a graph because the number of data elements 

does not equal the number of elements in the list of legend values. Modify 

the knowledge base so that the parameter or slot that contains legend values 

receives the appropriate number of elements. 

.........................................................................................................................................................................................................˝.......................................... 

33237 

Invalid Pie Labels; labels list empty or invalid 

AionDS is unable to display a graph because the list containing label values is 

either empty or contains an inappropriate number of elements. This list must 

contain one label for each slice of the pie chart. Modify the knowledge base 

so that the slot or parameter identified in the Label Values property of the 

graph receives the appropriate number of elements. 

.........................................................................................................................................................................................................˝.......................................... 

33238 

Sum of data elements in Pie Graph equals 0 

AionDS is unable to display a Pie graph because the sum of the data elements 

totals 0. Check the Data Values property of the graph object. 



.........................................................................................................................................................................................................˝.......................................... 

33239 


The implementation of AionDS being executed does not support graphs 

An attempt was made to display a graph using an AionDS implementation 

that does not support business graphics. 

.........................................................................................................................................................................................................˝.......................................... 

34301 

Invalid number 

You attempted to set a profile option with an invalid numeric entry. Change 

the AES PROFILE statement. This error can also occur on invocation of 

AionDS if the profile is incorrect. 

.........................................................................................................................................................................................................˝.......................................... 

34302 

Invalid value 

You attempted to set a profile option with an invalid value. Change the AES 

PROFILE statement. This error can also occur on invocation of AionDS if 

the profile is incorrect. 

.........................................................................................................................................................................................................˝.......................................... 

34303 

Invalid switch value; valid values are “ON” and “OFF” 

You attempted to set a profile option with an invalid value. Change the AES 



.........................................................................................................................................................................................................˝.......................................... 

34304 

Invalid command mode; valid values are “MENU” and “COMMAND” 

You attempted to set the COMMAND-PREFERENCE profile option to an 

invalid value. Change the AES PROFILE statement. This error can also 

occur on invocation of AionDS if the profile is incorrect. 

.........................................................................................................................................................................................................˝.......................................... 

34305 

Invalid compatibility mode; valid values are “OS” and “PC” 

You attempted to set the COMPATIBILITY profile option to an invalid 

value. Change the AES PROFILE statement. This error can also occur on 

invocation of AionDS if the profile is incorrect.


.........................................................................................................................................................................................................˝.......................................... 

34306 

34306 

Invalid trace level; value must be between 0 and 4 


Invalid trace level; value must be between 0 and 3 (MVS/VM) 

You attempted to set the TRACE-LEVEL profile option to an invalid value. 

Change the AES PROFILE statement. This error can also occur on 

invocation of AionDS if the profile is incorrect. 

.........................................................................................................................................................................................................˝.......................................... 

34307 

Profile string truncated 

You attempted to set a profile command with a string that is too long. 



.........................................................................................................................................................................................................˝.......................................... 

34308 

Profile string must have the form “ = ” 

A line in a profile file is incorrect. This error can occur on invocation of 

AionDS or whenever a profile is read from disk. 

.........................................................................................................................................................................................................˝.......................................... 

34309 

Unknown profile keyword 

The profile option you attempted to set is invalid or does not exist. Change 

the AES PROFILE statement. This error can also occur on invocation of 

AionDS if the profile is incorrect. 


(Character-Based) for a list of valid profile options. 



.........................................................................................................................................................................................................˝.......................................... 

34310 


Unknown keyboard function 

The key you attempted to assign in the profile is invalid. Change the AES 




(Character-Based) for a list of valid key assignments. 

.........................................................................................................................................................................................................˝.......................................... 

34312 

Invalid date mask 

The value for the DATE-MASK profile option is invalid. Change the AES 




manual for valid masks. 

.........................................................................................................................................................................................................˝.......................................... 

34313 

Invalid time mask 

The value for the TIME-MASK profile option is invalid. Change the AES 




manual for valid masks. 

.........................................................................................................................................................................................................˝.......................................... 

34315 

Invalid message mode; “ON”, “OFF”, “CODE”, and “TEXT” are valid 

You attempted to set the ERROR-MESSAGE profile option to an invalid 


invocation of AionDS if the profile is incorrect.


.........................................................................................................................................................................................................˝.......................................... 

34316 

Invalid swapper threshold 

You attempted to set the SWAPPER-THRESHOLD profile option to an 

invalid value. The value specifies the number of kilobytes of memory to 

reserve, or 0 to reserve all available memory. Change the AES PROFILE 

statement. This error can also occur on invocation of AionDS if the profile is 

incorrect. 

.........................................................................................................................................................................................................˝.......................................... 

34317 

Invalid device type 

You attempted to set the DEVICE-TYPE profile option to an invalid value. 




(Character-Based) for a list of valid device types 

.........................................................................................................................................................................................................˝.......................................... 

34318 

Invalid character specification 

You attempted to specify a multi-character value to the DECIMAL- 

SEPARATOR or THOUSANDS-SEPARATOR profile option. Only one 

character is allowed. Change the AES PROFILE statement. This error can 

also occur on invocation of AionDS if the profile is incorrect. 

.........................................................................................................................................................................................................˝.......................................... 

34319 

Invalid value-can-change setting; “TRUE”, “FALSE” and “TRUE/ASK” 

are valid 

You attempted to set the VALUE-CAN-CHANGE profile option to an 

invalid value. Change the AES PROFILE statement. This error can also 

occur on invocation of AionDS if the profile is incorrect. 

.........................................................................................................................................................................................................˝.......................................... 

34321 

Invalid dBASE version: “III” and “IV” are valid 

You attempted to set the DBASE-VERSION profile option to an invalid 






AionDS supports dBASE III, III+, and IV. You must specify which version 

for AionDS to be compatible with. Set the DBASE-VERSION profile 

option to “III” for dBASE III and III+, or “IV” for dBASE IV. 

.........................................................................................................................................................................................................˝.......................................... 

34322 

Invalid user interface; valid values are “GRAPHICAL” and 

“CHARACTER” 

You attempted to set the USER-INTERFACE profile option to an invalid 



.........................................................................................................................................................................................................˝.......................................... 

34323 

Sorted-export and 600-export are incompatible flags 

The sorted-export and 600-export flags cannot both be set to ON. This is 

because Version 6.00 did not support the sorted-export format. 

.........................................................................................................................................................................................................˝.......................................... 

34330 

Invalid screen attribute setting; use “G”, “C”, “H”, or “X” 

The value of the SCREEN-INFO profile option is invalid. Change the AES 



For more information: Refer to the AionDS User’s Guide or User’s Guide 

(Character-Based) for more information about this profile option. 

.........................................................................................................................................................................................................˝.......................................... 

34331 

Invalid device model; use 0, 1, 2, 3, 4, or 5 

The value of the SCREEN-INFO profile option is invalid. Change the AES 




(Character-Based) for more information about this profile option.


.........................................................................................................................................................................................................˝.......................................... 

34332 

Invalid class; use “A” to “Z”, “0” to “9”, or “*” 

The value of the SYSOUT-CLASS profile option is invalid. Change the AES 





.........................................................................................................................................................................................................˝.......................................... 

34333 

Specify space as (,(,,)) 

The value of the KB-SPACE or TEXT-SPACE profile option is invalid. 





.........................................................................................................................................................................................................˝.......................................... 

34334 

Invalid block size; must be a multiple of 80 

The value of the BLOCK-SIZE profile option is invalid. Change the AES 





.........................................................................................................................................................................................................˝.......................................... 

37346 

Unable to load support library for Microsoft SQL Server 6.0 

AionDS was not able to connect to Microsoft SQL Server because the 

AionDS database interface is not installed or the files cannot be found. 




.........................................................................................................................................................................................................˝.......................................... 

37347 


Unable to load support library for Informix Server 

AionDS was not able to connect to Informix Server because the AionDS 

database interface is not installed or the files cannot be found. Check that the 

files are present and accessible to AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

37349 

Unable to load support library for Microsoft/Sybase SQL server 

This error occurs if you set SQL-INTERFACE=SYBASE in the profile, but 

you don’t have the Aion Database Interface for Sybase installed. Install the 

Aion Database Interface for SQL Server. 

.........................................................................................................................................................................................................˝.......................................... 

37350 

Unable to load support library for IBM Database Manager 

This error occurs if you set SQL-INTERFACE=IBM in the profile, but you 

don’t have the Aion Database Interface for DB2/2 installed. Install the Aion 

Database Interface for DB2/2. 

.........................................................................................................................................................................................................˝.......................................... 

37351 

Unable to load support library for Oracle 

This error occurs if you set SQL-INTERFACE=ORACLE in the profile, but 

you don’t have the Aion Database Interface for Oracle installed. Install the 

Aion Database Interface for Oracle. 

.........................................................................................................................................................................................................˝.......................................... 

37352 

Unable to load support library for DB2/6000 (UNIX) 

This error occurs if you set SQL-INTERFACE=DB2/6000 in the profile but 

you don’t have the Aion Database Interface for DB2/6000 installed. Install 

the Aion Database Interface for DB2/6000.


.........................................................................................................................................................................................................˝.......................................... 

37352 

Unable to load support library for Microsoft ODBC 

(PC/WIN/OS2/PM/MVS/VM) 

This error occurs if you set SQL-INTERFACE=ODBC in the profile but 

you don’t have the AionDS ODBC (Open Database Connectivity) Support 

option installed. Install the Aion Database Interface for ODBC. 

.........................................................................................................................................................................................................˝.......................................... 

37355 

Fetching data to invalid file parameter, make sure cursor is opened 

This error occurs when an “open cursor” function failed or was not executed, 

but the operation ws continued with a fetch. A successful “open cursor” 

must precede a fetch. 

You must issue the OPENFILE(FILEREC) KDL before you can use the 

GETREC(FILEREC) command. 

.........................................................................................................................................................................................................˝.......................................... 

37356 

Initialization of Database failed after DLL is loaded 

The DLL caused the database to be unable to initialize. Try to reinitialize the 

database. 

.........................................................................................................................................................................................................˝.......................................... 

37357 

Unable to resolve all the function addresses in the DLL 

An error occurs while evaluation function addresses in the DLL. 

.........................................................................................................................................................................................................˝.......................................... 

37358 

The DLL is in an unrecognizable format 

The DLL may have been transferred with the format set incorrectly. Reinstall 

the DLL. 

.........................................................................................................................................................................................................˝.......................................... 

37359 

Unknown Database found 

This error occurs if the SQL-INTERFACE profile option is not set to a 

supported relational database management system for the platform you are 

using. Specify DB2 or ORACLE in the SQL-INTERFACE profile option. 



.........................................................................................................................................................................................................˝.......................................... 

37360 


All SQL statements need a database connection before they can proceed 

This error occurs if you have not included an explicit SQL connection 

statement and the implicit connection is invalid. 

To establish an SQL connection, AionDS first uses the PDI SQL statement 

or ADI connect information. If the PDI SQL statement or ADI connect 

information is invalid, AionDS uses the implicit connection information. If 

you have not included the correct profile options in the profile, you cannot 

implicitly connect to a database. 

To resolve the error, complete one of the following actions: 

■ In PDI, include a valid SQL CONNECT statement. 

■ In ADI, include a valid access-string or table name Access Method 

monitor option. 

■ Make sure that the SQL-ACCESS-STRING, SQL-CONNECT, and 

SQL-DATABASE profile options are valid. 

.........................................................................................................................................................................................................˝.......................................... 

37361 

The SQL Standard Interface is not supported 

This error occurs when the database accessed is not supported for the AionDS 

platform you are using. 

.........................................................................................................................................................................................................˝.......................................... 

37362 

The SQL Data Dictionary Interface is not supported 

This error occurs when you attempt to import an external data structure 

using an access method that doesn’t have Data Dictionary support. 

.........................................................................................................................................................................................................˝.......................................... 

37363 

The SQL Cursor Interface is not supported 

This error occurs when an open, fetch, or close cursor operation is not 

supported.


.........................................................................................................................................................................................................˝.......................................... 

37364 

Procedural Interface is not supported 

This error occurs when you try to execute the SQL procedure using the 

specific SQL API. 

.........................................................................................................................................................................................................˝.......................................... 

37365 

SQL “prepare cursor” failed 

This error occurs when there is an invalid column or table name. Examine 

the ADSLOG to find the invalid column or table name and correct it. 

.........................................................................................................................................................................................................˝.......................................... 

37366 

Number of SQL columns returned do not match the columns for the 

parameter 

This error occurs when there are more columns selected than corresponding 

slots specified for the class. 

Examine the ADSLOG to find the class in which there are fewer slots than 

columns in the table. Create the same number of corresponding slots as 

columns in the table. 

.........................................................................................................................................................................................................˝.......................................... 

37367 

Operation attempted on an unprepared SQL Cursor 

This error occurs if you continued the operation after a “prepare cursor” 

failed. For example, an OPENFILE must be executed before a GETREC is 

executed. Since the “prepare cursor” action failed, an OPENFILE was not 

executed and the subsequent GETREC failed. 

Do not continue the operation after a “prepare cursor” error (error message 

37365) occurs. Examine the ADSLOG to find the invalid column or table 

name and correct it. 



.........................................................................................................................................................................................................˝.......................................... 

37368 


SQL column type does not match a slot/record-member type 

This error occurs when the AionDS data type does not match the SQL data 

type. For example, a slot type is defined with a data type of INT and the 

corresponding SQL column has a data type of REAL. Match the AionDS 

data type with the corresponding SQL data type. 

.........................................................................................................................................................................................................˝.......................................... 

37369 

Unknown SQL type cannot be mapped 

This error occurs when an SQL data type does not have a corresponding data 

type in AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

37370 

SQL Feature is not supported 

This error occurs if you are attempting to execute a commit or rollback 

against a table that is accessed remotely. 

To resolve the error, complete one of the following actions: 

■ Delete the commit or rollback attempt from the knowledge base. 

■ Access the table locally. 

.........................................................................................................................................................................................................˝.......................................... 

37371 

The SQL Syntax Interface is not supported 

This error occurs when DB2 or Oracle attempts to modify an SQL statement 

that couldn’t find the interface to support it. This error should not occur. 

.........................................................................................................................................................................................................˝.......................................... 

37372 

Unknown SQL interface encountered 

This error occurs if invalid data was returned to AionDS. This error should 

not occur.


.........................................................................................................................................................................................................˝.......................................... 

37373 

SQL Disconnect failed 

This error occurs when a disconnect request was unsuccessful; for example, a 

connection might not have been established. Examine the ADSLOG for 

other messages that might help to resolve the problem. 

.........................................................................................................................................................................................................˝.......................................... 

37374 

SQL (Commit or Rollback) failed 

This error occurs when a DBMS (‘COMMIT, ...) or a DBMS 

(ROLLBACK, ...) failed for a locally accessed table. This error might occur 

when the database terminates in the middle of the commit or rollback or if 

the database is locked in update mode. See your database administrator. 

.........................................................................................................................................................................................................˝.......................................... 

37375 

SQL “describe cursor” failed 

This error occurs only in Oracle when the prepare phase of the SELECT 

statement fails. Make sure that the SELECT statement is valid. 

.........................................................................................................................................................................................................˝.......................................... 

37376 

Total # of columns are greater than 64K (WIN) 

This error occurs when the total number of bytes for all column names in a 

table exceeds 64 KB. Reduce the number of bytes for all column names in 

the table to 64 KB or less. 

.........................................................................................................................................................................................................˝.......................................... 

37377 

SQL: unexpected sqlcode from %1: %2 

This error occurs when an error occurs that returns an SQL subsystem error 

code. 

%1 SQL function such as FETCH 

%2 SQLCODE value 

Examine the ADSLOG and identify the error. 



.........................................................................................................................................................................................................˝.......................................... 

37378 


AION views are not supported for importing 

AionDS does not allow you to import views because it cannot guarantee the 

view will be valid against the database. 

.........................................................................................................................................................................................................˝.......................................... 

37379 

SQL “close cursor” failed 

This error might occur if the close cursor function attempted to close an 

invalid cursor or a cursor that wasn’t open. 

To find out more information about why the “close cursor” function failed, 

use the DBINFO KDL statement to retrieve the SQL database error code 

and error message. 

For more information: See the AionDS I/O Reference for more 

information about DBINFO. 

.........................................................................................................................................................................................................˝.......................................... 

37380 

Unable to load local static SQL access module (MVS) 

This error occurs when an HPO knowledge base attempted to execute a local, 

static SQL request but the static SQL access module was not in ADSLIB or 

STEPLIB of the region. 

.........................................................................................................................................................................................................˝.......................................... 

37381 

Unable to load remote static SQL access module (MVS) 

This error occurs when an HPO knowledge base attempted to execute a 

remote, static SQL request but the static SQL access module was not in 

DFHRPL or STEPLIB of the IMS region. 

.........................................................................................................................................................................................................˝.......................................... 

42510 

The WHAT command is not valid here 

The WHAT command is not available within the What monitor or the 

Other Sources monitor. Within the Explanation facility, the WHAT 

command is only valid from the How and Why monitors.


.........................................................................................................................................................................................................˝.......................................... 

42511 

The OTHERSOURCES command is not valid here 

The OTHERSOURCES command is not available in this context. This 

command is only available within the How and Why monitors. 

.........................................................................................................................................................................................................˝.......................................... 

42512 

Option supported only for currently sourced objects 

AionDS is unable to execute the WHAT or WHY command because there is 

no slot or parameter currently being sourced. 

.........................................................................................................................................................................................................˝.......................................... 

42515 

Requested object is not explainable 

AionDS is unable to provide an explanation for the current parameter or slot 

because its Explainable property contains the value NEVER. 

.........................................................................................................................................................................................................˝.......................................... 

42518 

There are no parameters or slots available for the WHY command 

AionDS is unable to process the WHY command because there are no 

parameters or slots for which the WHY command may be issued. 

.........................................................................................................................................................................................................˝.......................................... 

42519 

There are no parameters or slots available for the WHAT command 

AionDS is unable to process the WHAT command because there are no 

parameters or slots for which the WHAT command may be issued. 

.........................................................................................................................................................................................................˝.......................................... 

42660 

Invalid cursor position for selection 

No object was selected from the Intermediate Explanation monitor because 

the cursor is not positioned properly. Position the cursor on one of the 

choices and press ENTER to make a selection. 



.........................................................................................................................................................................................................˝.......................................... 

42859 


Screen/instance is only valid if all slots are specialized 

To issue the SCREEN/INSTANCE command, you must first specialize all 

slots in the current class. To do this, use the SPECIALIZE command in the 

character-based editing system, or use the Object.Specialize command in the 

graphical editing system. 

.........................................................................................................................................................................................................˝.......................................... 

46471 

Invalid DD Name 

The DD Name specified is invalid. A DD Name can be no longer than 8 

characters. 

.........................................................................................................................................................................................................˝.......................................... 

46703 

Error occurred starting program 

ADSAPI is unable to execute the desired program. The AionDS system log 

contains error codes that might assist in diagnosis. 

Check that the files ADSAPI.EXE and ADSAPI.DLL are located in the 

directory specified in the Application Programming Interface Guide for your 

environment. Verify that the target program is also available for execution. 

.........................................................................................................................................................................................................˝.......................................... 

46720 

Invalid program exit options 

The program exit options specified in the program string are invalid. The 

options must be separated by commas and must follow the program name. 

For more information: See Appendix D of the Application Programming 

Interface Guide for the list of options available in your environment. 

.........................................................................................................................................................................................................˝.......................................... 

46721 

Parameter list inconsistent with LIBCALL token list 

The process parameter lists do not contain the number of parameters 

necessary to construct the LIBCALL parameter list. Check the LIBCALL 

parameter token list and process parameter lists for agreement.


.........................................................................................................................................................................................................˝.......................................... 

46722 

Invalid LIBCALL token list 

The LIBCALL parameter token list is not in the correct format. 

For more information: Consult the Application Programming Interface 

Guide for the required format. 

.........................................................................................................................................................................................................˝.......................................... 

46723 

Unable to load dynamic link library for LIBCALL 

AionDS is unable to load the DLL specified for the LIBCALL. Check that 

the correct name is specified in the program string. Also check that the 

appropriate library is available in a directory specified in the LIBPATH 

statement of the CONFIG.SYS file. 

.........................................................................................................................................................................................................˝.......................................... 

46724 

Unable to get procedure address for LIBCALL 

AionDS cannot locate the specified procedure in the target library. Verify 

that AionDS is using the correct procedure name. Also verify that the ordinal 

name (#nnnn) is used where required (some libraries do not export procedure 

names - for example DOSCALLS). 

.........................................................................................................................................................................................................˝.......................................... 

46760 

FPL input/output error 

An error occurred while retrieving the Fixed Parameter List. The AionDS 

system log contains additional error information. 

.........................................................................................................................................................................................................˝.......................................... 

46761 

FPL contains invalid PDB 

The format of the Fixed Parameter List passed to the knowledge base is 

incorrect. Check that the FPL is being correctly constructed and passed to 

the knowledge base. 



.........................................................................................................................................................................................................˝.......................................... 

46762 


FPL parameter missing 

The input/output parameter lists in the knowledge base are inconsistent with 

the Fixed Parameter List that was passed to the knowledge base. 

.........................................................................................................................................................................................................˝.......................................... 

46763 

Data transfer error 

A data conversion error occurred during transfer of data to or from the 

knowledge base. Check the data types, sizes, and attributes for consistency 

between the knowledge base and external programs. 

.........................................................................................................................................................................................................˝.......................................... 

46780 

Load module library could not be opened 

The program string specified a library from which to load the external 

program, but the library could not be opened. 

.........................................................................................................................................................................................................˝.......................................... 

46781 

External program LOAD failed 

The load module specified in the program string could not be loaded. See the 

AionDS system log for additional information. 

.........................................................................................................................................................................................................˝.......................................... 

46782 

LINK to external program failed 

The load module specified in the program string could not be linked to and 

executed. See the AionDS system log for additional information. 

.........................................................................................................................................................................................................˝.......................................... 

46783 

External program abended 

An abend condition was detected during execution of the external program. 

Additional information is available in the AionDS system log. 

.........................................................................................................................................................................................................˝.......................................... 

50030 

Segment not found (row %1/col %2) 

For more information: See Chapter 6, “DL/I Data Access,” in the 

AionDS I/O Reference for more information on DL/I-specific issues.


.........................................................................................................................................................................................................˝.......................................... 

50031 

BYTES clause not found (row %1/col %2) 


AionDS I/O Reference for more information on DL/I-specific issues. 

.........................................................................................................................................................................................................˝.......................................... 

50032 

Positive integer expected (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50033 

FIELD clause not found (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50034 

NAME clause not found (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50035 

Invalid name string (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50036 

TYPE clause not found (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50037 

Invalid data type (row %1/col %2) 





.........................................................................................................................................................................................................˝.......................................... 

50038 


START clause not found (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50039 

Overlapping fields (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50101 

Unable to open database file 

The specified database file cannot be opened. Check whether the database 

file is missing, named incorrectly, or corrupted. 

For more information: See Chapter 2, “dBASE Data Access,” in the 

AionDS I/O Reference for further information on dBASE IV-specific issues. 

.........................................................................................................................................................................................................˝.......................................... 

50102 

Unable to open index file 

The specified index file cannot be opened. Check whether the index file is 

missing, named incorrectly, or corrupted. 



.........................................................................................................................................................................................................˝.......................................... 

50103 

Unable to create database: path not found or file already exists 

The attempt to create a database was unsuccessful because the specified path 

is invalid or the file already exists. Check the path to verify that it exists and 

is accessible. If the file already exists, specify a different filename. 


AionDS I/O Reference for further information on dBASE IV-specific issues.


.........................................................................................................................................................................................................˝.......................................... 

50104 

Unable to create index: path not found or file already exists 

The attempt to create an index was unsuccessful because the specified path is 

invalid or the file already exists. Check the path to verify that it exists and is 

accessible. If the file already exists, specify a different filename. 



.........................................................................................................................................................................................................˝.......................................... 

50105 

Invalid field name (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50106 

Invalid field type (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50107 

Field name expected (row %1/col %2) 



.........................................................................................................................................................................................................˝.......................................... 

50108 

Cannot index on a memo field (row %1/col %2) 

Illegal operation at the location specified. The operation expected a unique 

value. 





.........................................................................................................................................................................................................˝.......................................... 

50109 


Key fields must be of the same type (row %1/col %2) 

Invalid key specification. Closed parentheses were expected. 



.........................................................................................................................................................................................................˝.......................................... 

50113 

Invalid path specification (row %1/col %2) 

An invalid path was specified at row %1/col %2. Specify a valid path name 

and retry. 



.........................................................................................................................................................................................................˝.......................................... 

50114 

‘=’ or ‘is’ expected (row %1/col %2) 

AionDS has received a bad key specification. 



.........................................................................................................................................................................................................˝.......................................... 

50115 

‘+’ expected (row %1/col %2) 

AionDS has received a bad key specification. 



.........................................................................................................................................................................................................˝.......................................... 

50301 

Table not found or invalid 


database because it cannot locate the table. Check that the table is present 

and accessible.


.........................................................................................................................................................................................................˝.......................................... 

50302 

View not found or invalid 


database because it cannot locate the database view. Check that the database 

view is present and accessible. 

.........................................................................................................................................................................................................˝.......................................... 

50303 

Column name not found or invalid 


database because it cannot locate the database column. Check that the 

database column is present and accessible. 

.........................................................................................................................................................................................................˝.......................................... 

50304 

Unable to create definition - table or columns not found 

AionDS is unable to create a definition with information from the database 

because it cannot locate the database table or column. Check that the 

database table or column is present and accessible. 

.........................................................................................................................................................................................................˝.......................................... 

50305 

Index table name invalid (row %1/col %2) 


database because it cannot locate the index table name. Check that the index 

table name is present and accessible. 

.........................................................................................................................................................................................................˝.......................................... 

50306 

Invalid key specifications 

Key specification string is in the wrong format. Check your documentation 

for the correct format. 

.........................................................................................................................................................................................................˝.......................................... 

50312 

Data type not supported on this ODBC Data Source 

The ODBC Data Source does not support one or more of the data types that 

are being exported. 



.........................................................................................................................................................................................................˝.......................................... 

50702 



An invalid option was passed to an I/O function. Check the function syntax. 

.........................................................................................................................................................................................................˝.......................................... 

50703 

Invalid record I/O get mode given 

An invalid get mode was specified in a GETREC statement. Check the 

syntax for GETREC. 

.........................................................................................................................................................................................................˝.......................................... 

50706 

Invalid I/O operation; GETREC returned EOF 

An attempt was made to execute an I/O function after the EOF function 

returned an end-of-file condition. 

.........................................................................................................................................................................................................˝.......................................... 

50709 

Invalid OPENFILE request; duplicate record name specified 

A duplicate record name was specified in an OPENFILE statement. AionDS 

already has a file parameter open for that record name. 

.........................................................................................................................................................................................................˝.......................................... 

51001 

EXITSTATE used outside of agenda; use /e command-line switch 


A KDL property that is not a state’s agenda contains the EXITSTATE 

statement. 

You must pass the /E switch to HPO or HPOOPT. Because this switch 

results in slightly larger and slower code, you should avoid using it if possible. 

Instead make sure you use EXITSTATE in agendas only.


.........................................................................................................................................................................................................˝.......................................... 

51001 

EXITSTATE used outside of agenda; use EXIT option with KBOPT 

(MVS/VM) 

A KDL property that is not a state’s agenda contains the EXITSTATE 

statement. 

You must assign the value of EXIT to the execution symbolic parameter P in 

the KBOPT or KBOPT1 JCL. Because this switch results in slightly larger 

and slower code, you should avoid using it if possible. Instead make sure that 

you use EXITSTATE in agendas only. 

.........................................................................................................................................................................................................˝.......................................... 

51002 

Unrecognized or unsupported KDL statement; import KB with High- 

Performance ON 

The knowledge base contains a statement that HPO does not support. All 

such statements are listed in Chapter 2 of the HPO Installation and Operation 

Guide for your environment. 

Before optimizing a knowledge base, you should always set the HIGH- 

PERFORMANCE profile option to ON and import the knowledge base. 

This will tell you if there are any statements in the knowledge base that HPO 

does not support. 

.........................................................................................................................................................................................................˝.......................................... 

51003 

Context too large; recompile using /o switch, with a higher 

argument 

A state or class contains more KDL than the Optimizer can compile. Try 

rerunning the HPO Optimizer using the /O switch. Give a higher argument 

to /O than the default. 

.........................................................................................................................................................................................................˝.......................................... 

51004 

Too many unique string constants in a context 

A state or class contains too many unique string constants. Try breaking up 

the state or class into two or more states or classes. 



.........................................................................................................................................................................................................˝.......................................... 

51005 


The knowledge base contains invalid objects 

Make sure the entire knowledge base has no invalid objects before attempting 

to optimize it. 

.........................................................................................................................................................................................................˝.......................................... 

51008 

Environment variable AIONHPO is not set up 

The AIONHPO environment variable must be set up before attempting to 

run the High Performance Option to optimize a knowledge base. 

For more information: See the HPO Installation and Operation Guide for 

information on how to set this variable in your environment. 

.........................................................................................................................................................................................................˝.......................................... 

51033 

Could not optimize KB 

An error occurred during optimization. This message is always preceded by a 

message telling what error occurred. 

.........................................................................................................................................................................................................˝.......................................... 

51050 

The knowledge base contains more than 65536 symbols 

HPO can only optimize a knowledge base which has 65536 or fewer entries 

in the symbol table. The number of entries in the symbol table depends on 

the number and type of objects in the knowledge base. 

Break up the knowledge base into two or more separate knowledge bases 

which use the AES CHAIN statement to call each other. 

.........................................................................................................................................................................................................˝.......................................... 

51051 

The names of the knowledge base symbols total more than 1,703,910 

bytes 

HPO can only optimize a knowledge base which has 1,703,910 or fewer total 

bytes in the names of all the symbols. 

Shorten the names of some of the objects in your knowledge base, or break 

up the knowledge base into two or more separate knowledge bases which use 

the AES CHAIN statement to call each other.


.........................................................................................................................................................................................................˝.......................................... 

51052 

Unable to create the save file 

The HPO Optimizer was unable to create the save file in the optimized 

knowledge base directory. Check to make sure your disk is not full. 

.........................................................................................................................................................................................................˝.......................................... 

51053 

The knowledge base contains more than 65536 models 

HPO can only optimize a knowledge base which has 65536 or fewer models. 

The number of models depends on the number of parameters (especially 

record parameters), slots and classes in the knowledge base. 

Break up the knowledge base into two or more separate knowledge bases 

which use the AES CHAIN statement to call each other. 

.........................................................................................................................................................................................................˝.......................................... 

51096 

SYSLIN dataset disposition must be new or old 

.........................................................................................................................................................................................................˝.......................................... 

51100 

Can’t load A7BCABS.DLL 

Cannot load the DLL for the Callable Aion Building System (CABS). It may 

not be installed. 

.........................................................................................................................................................................................................˝.......................................... 

51101 

Unknown property 

This property is not a valid CABS property. 

For more information: See the CABS Reference for information on valid 

CABS properties. 

.........................................................................................................................................................................................................˝.......................................... 

51103 

Unknown object type 

This object type is not valid for CABS. 


CABS objects. 



.........................................................................................................................................................................................................˝.......................................... 

51104 


Unknown KB property 

This knowledge base property is not valid for CABS. 


CABS knowledge base properties. 

.........................................................................................................................................................................................................˝.......................................... 

51105 

Unknown field type 

This field type is unknown for CABS. 

.........................................................................................................................................................................................................˝.......................................... 

51106 

The property %1 can’t be represented as boolean 

The specified property cannot be represented as Boolean in CABS. Modify 

the property appropriately. 

.........................................................................................................................................................................................................˝.......................................... 

51107 

The property %1 can’t be represented as integer 

The specified property cannot be represented as an integer in CABS. Modify 

the property appropriately. 

.........................................................................................................................................................................................................˝.......................................... 

51108 

The property %1 can’t be represented as real 

The specified property cannot be represented as real in CABS. Modify the 

property appropriately. 

.........................................................................................................................................................................................................˝.......................................... 

51109 

Object %1 is unprocessed 

The specified property has not been parsed in CABS. The object may have 

been modified without being parsed using KbParse. 

.........................................................................................................................................................................................................˝.......................................... 

51110 

The property can’t be represented in this type 

The specified property cannot be represented as the current type in CABS. 

Modify the property appropriately.


.........................................................................................................................................................................................................˝.......................................... 

51111 

None found 

The specified CABS object cannot be found. Specify a different object and 

try again. 

.........................................................................................................................................................................................................˝.......................................... 

51153 

Invalid KB version specification 

The version number specified is not valid. Knowledge base version must be 

from 0.00 to 9.99. 

.........................................................................................................................................................................................................˝.......................................... 

51154 

Invalid object ID 

This object ID is invalid for the knowledge base or object specified. Verify 

you have specified the appropriate object ID for the CABS function. 

.........................................................................................................................................................................................................˝.......................................... 

51155 

Invalid Knowledge Base ID 

This knowledge base ID (KB ID) is invalid for the knowledge base or object 

specified. Verify you have specified the appropriate KB ID for the CABS 

function. 

.........................................................................................................................................................................................................˝.......................................... 

51156 

-- Errors are in file 

You are attempting to import or open a CABS file containing errors. Check 

the trace file to determine the what the errors are. 

.........................................................................................................................................................................................................˝.......................................... 

51157 

Objects are from two different KBs 

The object IDs specified for this CABS function are from two different 

knowledge bases. The operation cannot be performed. 

.........................................................................................................................................................................................................˝.......................................... 

51158 

Not supported 

You attempted to use a CABS function that is not supported. 



.........................................................................................................................................................................................................˝.......................................... 

51159 


The property can’t be represented as boolean 

This property cannot be represented as Boolean in CABS. Modify the 


.........................................................................................................................................................................................................˝.......................................... 

51160 

The property can’t be represented as real 

This property cannot be represented as real in CABS. Modify the property 

appropriately. 

.........................................................................................................................................................................................................˝.......................................... 

51161 

The property is unparsed 

You attempted to access a property that has not been parsed in CABS. The 

object may have been modified without being parsed using KbParse. 

.........................................................................................................................................................................................................˝.......................................... 

51162 

The property can’t be represented as an object 

This property cannot be represented as an object in CABS. Modify the 


.........................................................................................................................................................................................................˝.......................................... 

51190 

Insufficient memory allocated to return desired information 

The CABS information requested is to large for the allocated buffer. 

Determine the approximate size of the information to be retrieved and 

reallocate a memory buffer for the information. 

.........................................................................................................................................................................................................˝.......................................... 

51841 

Error opening file %1; file not found 

The system could not find the specified file. Check to verify that the name is 

correct and that the file is in the specified directory. 

.........................................................................................................................................................................................................˝.......................................... 

51842 

Trace is not enabled 

The trace level must be set to 2 (two) or greater in order for the Trace 

method to bring up a trace dialog. Set the trace level to two or greater.


.........................................................................................................................................................................................................˝.......................................... 

51843 

File size exceeds 64K limit for TextWindow 

On Windows, the file size for TextWindow is limited 64 KB. This file 

exceeds the 64 KB limit. Reduce the size of the TextWindow. 

.........................................................................................................................................................................................................˝.......................................... 

51844 

Illegal operation; window cannot be set unknown 

Some window objects cannot be set to unknown. For these types of 

windows, using the System menu item Unknown option will cause this 

message. 

.........................................................................................................................................................................................................˝.......................................... 

51845 

Cannot send AssignAnswer when window is attached to a non-answer 

property 

The knowledge base attempted to send the AssignAnswer method to a 

window that does not have an answer property. Check the property type for 

the window in question, and attach the window to an answer property. 

.........................................................................................................................................................................................................˝.......................................... 

51846 

No Explain text available 

There is no explain text available for the attached object. Check to see that 

explain text is valid for the attached object, and that the explain property is 

set. 

.........................................................................................................................................................................................................˝.......................................... 

51851 

Menu item parent must be StandardWindow or MenuItem 

The system is attempting to create a menu item whose parent is not a valid 

StandardWindow, DialogBox, or MenuItem instance. Check the KDL for a 

Class(MenuItem).CreateObject call that specifies a parent that does not 

fit the above conditions. 



.........................................................................................................................................................................................................˝.......................................... 

51852 


Menu item parent must have the MIS_SUBMENU style 

An attempt has been made to create a menu item whose parent menu item 

does not have the MIS_SUBMENU style. Check the KDL for a 

Class(MenuItem).CreateObject call for which this is the case and either 

specify a different parent menu or add the MIS_SUBMENU style to the 

specified parent menu instance. 

.........................................................................................................................................................................................................˝.......................................... 

51853 

Child menu items cannot have the MIS_MENUBAR style 

The system is attempting to create a menu item with the MIS_MENUBAR 

style as a child to another menu item. Check the KDL for a 

Class(MenuItem).CreateObject call for which this is the case and either 

remove the MIS_MENUBAR style from the menu item, or specify a valid 

StandardWindow or DialogBox instance as the parent instance for the menu 

item. 

.........................................................................................................................................................................................................˝.......................................... 

51854 

Menu items with the MIS_SUBMENU style cannot have a shortcut key 

An attempt has been made to create a menu item with the MIS_SUBMENU 

style, which indicates that the menu item is to be a parent to another menu 

item. Parent menu items may not have shortcut keys assigned to them. 

Check the KDL for the offending Class(MenuItem).CreateObject call 

and remove the shortcut key specification. 

.........................................................................................................................................................................................................˝.......................................... 

58110 

Invalid object_pointer value 

The object_pointer does not point to a valid object. It may have pointed to a 

dynamic instance that has been deleted. 

.........................................................................................................................................................................................................˝.......................................... 

58111 

Object_pointer out of scope 

Either a window instance or a DDE instance referenced an object that is no 

longer in scope. Move the object into scope or remove the reference to 

correct this error.

Chapter 2 

Transaction Driver Messages 

.........................................................................................................................................................................................................˝.......................................... 

Introduction 

This chapter describes the messages issued by the transaction drivers provided 

with AionDS/CICS and AionDS/IMS. This chapter is divided into the 

following sections: 

■ CICS Transaction Driver Messages 

■ IMS and TSO Transaction Driver Messages 

Messages formatted by the AionDS transaction drivers are presented to the 

user on the terminal, or through an error message field passed to one of the 

FPL interface modules. Messages can be informational or indications of 

severe problems in the execution of your knowledge base. Messages that are 

not informational include a header indicating the type of error that occurred 

and the error number. 

The following sections identify and describe these messages. 

.........................................................................................................................................................................................................˝.......................................... 


Topic Page 

CICS transaction driver messages 2-2 

IMS and TSO transaction driver messages 2-16 

Transaction Driver Messages 2-1

CICS transaction driver messages 


.........................................................................................................................................................................................................˝.......................................... 

Overview 


The AionDS/CICS transaction driver supports two message formats. The 

format of the message issued is controlled by the MSG600 parameter in the 

AAESVARS program. By default, the MSG600 parameter is set to NO. 

For more information: See the AionDS/CICS Option Installation and 

Operation Guide for information about setting the MSG600 parameter.

Post Version 6.00-style messages (MSG600=NO) 


.........................................................................................................................................................................................................˝.......................................... 

Overview 

When the MSG600 parameter is set to NO, the transaction driver issues 

messages to the end user using a format that provides more descriptive 

information than Version 6.0. The Version 6.3 message format is described 

as follows: 

where 

xxxx - component - text 

xxxx 4-character, site-defined transaction code associated with the 

AionDS/CICS transaction driver 

component one of the following: 

MAES ERROR for errors occurring with MAES 

TD ERROR for errors occurring with the transaction 

driver 

FPL ERROR for errors occurring with FPL 

text descriptive text explaining the error condition 

The Version 6.3-style CICS transaction driver messages are listed below in 

numeric order. 

.........................................................................................................................................................................................................˝.......................................... 

xxxx - MAES ERROR 

(64) 

CONSULTATION STOPPED DUE TO INTERNAL ERROR 

The consultation abnormally ended with an internal error rather than a 

system or user abend. Refer to the AionDS system log for information about 

the abnormal termination. 



.........................................................................................................................................................................................................˝.......................................... 


(68) 


UNKNOWN MESSAGE TYPE RECEIVED - mmmm uuuu 

The transaction driver received a message from MAES or the consultation but 

could not recognize the request. The major (mmmm) and minor (uuuu) 

codes are printed. Report this error to PLATINUM Technical Support for 

AionDS. 

.........................................................................................................................................................................................................˝.......................................... 


(84) 

NODE ssss IS NOT ACTIVE. CONSULTATION CANNOT 

CONTINUE 

The transaction driver tried to continue a consultation on the ssss MAES 

node. However, CICS is unable to allocate an LU6.2 session. 

.........................................................................................................................................................................................................˝.......................................... 


(302) 

CONSULTATION ABENDED WITH ccccc CODE: uuuuu 

The consultation abended with a major code of ccccc and a minor code of 

uuuuu. 

.........................................................................................................................................................................................................˝.......................................... 

xxxx - TD ERROR 

(309) 

CONSULTATION LOST. POSSIBLE TIMEOUT. 

The user has replied to a screen or 3270 display but when the transaction 

driver attempted to reconnect to the consultation, it was no longer available. 

The probable cause is that the consultation timed out between the display of 

the screen to the user and the reply. 

.........................................................................................................................................................................................................˝.......................................... 


(310) 

MAX TASKS REACHED ON NODE: ssss 

The transaction driver attempted to start a consultation on the MAES system 

known as ssss. However, ssss did not have the resources to run the 

consultation. This generally means that the MAXTASKS runtime parameter 

for that MAES system is too low.


.........................................................................................................................................................................................................˝.......................................... 


(316) 

REQUEST ABORTED. ssss IS SHUTTING DOWN 

During a consultation, the MAES system called ssss was shut down. All active 

consultations were terminated. 

.........................................................................................................................................................................................................˝.......................................... 


(354) 

UNEXPECTED MESSAGE TYPE - mmmm, SUBCODE - uuuu 

The transaction driver received a message from MAES but the message type 

was inconsistent with the current state of the transaction driver. Report the 

message and circumstances that caused the message to PLATINUM 

Technical Support for AionDS. 

.........................................................................................................................................................................................................˝.......................................... 


(361) 

VALUE FOR ssssssss IS GREATER THAN 8 BYTES 

The length of the node name, or other specified value ssssssss, is greater than 

the maximum (8 bytes). 

.........................................................................................................................................................................................................˝.......................................... 

xxxx - FPL ERROR 

(362) 

INPUT PARM SIZE EXCEEDS THE TOTAL ALLOWED (nnnnn 

BYTES) 

The input parameter on an FPL request was too big. The maximum size of 

the parameter is nnnnn bytes. Either the parameter is too big or the PDB is 

incorrectly formatted. 

.........................................................................................................................................................................................................˝.......................................... 


(363) 

OUTPUT PARM SIZE EXCEEDS THE TOTAL ALLOWED (nnnnn 

BYTES) 

The output parameter on an FPL request was too big. The maximum size of 

the parameter is nnnnn bytes. Either the parameter is too big or the PDB is 

incorrectly formatted. 



.........................................................................................................................................................................................................˝.......................................... 


(368) 


PGM pppppppp NOT FOUND DURING ADSMSW. CHECK FOR 

pppppppp IN PPT 

The application was unable to switch to program pppppppp under CICS. 

Check that the program has a PPT entry and that the program actually exists 

in the load libraries. 

.........................................................................................................................................................................................................˝.......................................... 


(373) 

PGM pppppppp NOT FOUND DURING ADSULINK. CHECK FOR 

pppppppp IN PPT 

The application attempted to run program pppppppp under CICS, but the 

EXEC CICS LINK failed. Be sure that the program has a PPT entry and 

that the program actually exists in the load libraries. 

.........................................................................................................................................................................................................˝.......................................... 


(392) 

SADS, SAES, OR HPO KB QUIESCED - NO NEW USERS ALLOWED. 

A request to attach another subtask for the program SADS, SAES, or an 

HPO KB has failed because the program in question has been quiesced 

through the MONITOR knowledge base. No new users will be allowed in 

until all active users have finished and the program is reactivated. Contact 

your AionDS system administrator to resolve this error. 

.........................................................................................................................................................................................................˝.......................................... 


(811) 

AAES AND vvvv VERSIONS DO NOT MATCH 

MAES compared its version number to the version number of the transaction 

driver and found that they were not equal. This may represent a problem 

that would prevent the consultation from running successfully. 

.........................................................................................................................................................................................................˝.......................................... 


(913) 

COMMAND LINE LENGTH EXCEEDS 80 BYTES ON XCTL TO 

AAES 

The command line cannot be greater than 80 bytes.


.........................................................................................................................................................................................................˝.......................................... 


(3167) 

NO MAES RESOURCES AVAILABLE 

The transaction driver attempted to begin a consultation. There are multiple 

MAES addresses spaces potentially available but the transaction driver cannot 

find one with sufficient capacity to run this new consultation. 

.........................................................................................................................................................................................................˝.......................................... 


(6000) 

CMD LINE + INPUT PARMS (nnnnn) > EIBCALEN (vvvvv) 

The length of the command line plus input parameters nnnnn provided to 

AAES on an XCTL is greater than the value in the EIB (vvvvv). The 

application program that transferred control to AAES should be corrected. 

.........................................................................................................................................................................................................˝.......................................... 


(6001) 

CMD LINE + INPUT PARMS EXCEEDS 32K LIMIT 

The size of the command line plus the size of the input parameters exceeds 32 

KB. Correct the calling program. 

.........................................................................................................................................................................................................˝.......................................... 


(6002) 

AN “EXEC CICS ssssssss” FAILED WITH COND: cccccccc AT LABEL 

llllllll 

A CICS request ssssssss, issued by the transaction driver, failed because of 

cccccccc. This is an abnormal situation. Report this error to PLATINUM 


.........................................................................................................................................................................................................˝.......................................... 


(6005) 

A PROTOCOL VIOLATION HAS OCCURRED: ssssssss 

A communication protocol error occurred. Report this error to PLATINUM 


.........................................................................................................................................................................................................˝.......................................... 


(6006) 

COMMAND LINE LENGTH


.........................................................................................................................................................................................................˝.......................................... 


(6007) 


UNABLE TO RECEIVE TERMINAL DATA. CONSULTATION 

ABORTED 

The transaction driver attempted a CICS RECEIVE on the user’s terminal, 

but the RECEIVE failed. Your CICS systems programmer should use the 

CICS log to determine the error and make the necessary corrections. 

.........................................................................................................................................................................................................˝.......................................... 


(6008) 

NO SESSIONS AVAILABLE TO MAKE A CICS CONNECTION TO 

nnnn 

The transaction driver tried to allocate a session to nnnn but found that no 

sessions were available. For maximum efficiency, you should have enough 

LU6.2 sessions allocated to CICS (connecting to nnnn) to satisfy the 

maximum number of concurrent users. 

.........................................................................................................................................................................................................˝.......................................... 


(6009) 

NODE nnnn HAS DIED. UNABLE TO RESUME YOUR 

CONSULTATION 

The MAES node nnnn is no longer active. Your consultation cannot 

continue. This error is caused by too many users on node nnnn. If this error 

persists after restarting the consultation, try increasing the value of MAXSESS 

in the DFHTCT. 

The syntax for MAXSESS is: 

where 

MAXSESS=(N,Q) 

N maximum number of sessions in the group 

Q maximum number of sessions that are to be supported as contention 

winners. The value specified for Q must not be greater than the 

number specified for N.


Note: The failed node may show active in CICS and VTAM. 

For more information: See Chapter 2 of the CICS Installation and 

Operation Guide for more information. 

.........................................................................................................................................................................................................˝.......................................... 


(6010) 

A CICS ABEND HAS OCCURRED AT LABEL llllllll, ABEND CODE 

aaaa 

If the abend cannot be resolved by your CICS systems programmer, contact 


.........................................................................................................................................................................................................˝.......................................... 


(6011) 

VALUE FOR “:MAES=” IS GREATER THAN 4 BYTES 

The target MAES node name is limited to 4 bytes. 

.........................................................................................................................................................................................................˝.......................................... 


(6012) 

nnnn IS AN INVALID PDB TYPE 

A type of parameter descriptor block contained in the fixed parameter list 

passed to the transaction driver is invalid. Correct the PDB structure and rerun 

the application. 

.........................................................................................................................................................................................................˝.......................................... 


(6013) 

PDB COUNT INCONSISTENT WITH NUMBER OF PARMS PASSED 

The size of the PDB defines the number of parameters represented. The size 

of the PDB is larger than the number of valid parameters. 

.........................................................................................................................................................................................................˝.......................................... 


(6014) 

NO KNOWLEDGE BASE NAME LENGTH SPECIFIED IN PDB 

The size of the knowledge base name parameter was zero. 



.........................................................................................................................................................................................................˝.......................................... 


(6015) 


THE PDBS AND INPUT PARM DATA EXCEEDS MAXIMUM 

(nnnnn) 

The total size of the PDB and the input parameter is limited to nnnnn bytes. 

Either the total of the two is too large or the size of the PDB or input 

parameter (as specified in the PCB) is incorrect. 

.........................................................................................................................................................................................................˝.......................................... 

(no transaction code 

or component) 

CONSULTATION WITH AIONDS/CICS ENDED. SESSION RUN ON 

NODE: ssssssss 

The consultation ended normally and was run on MAES node ssssssss. This is 

an informational message.

Version 6.0-style messages (MSG600=YES) 


.........................................................................................................................................................................................................˝.......................................... 

Overview 

When the MSG600 parameter is set to YES, the transaction driver displays 

messages on the user’s terminal using the format provided in Version 6.0. It 

is recommended that you set MSG600=NO unless you have an unknown 

message handler exit routine that expects error messages to be formatted as 

they were in Version 6.0. The Version 6.0 message format is described as 

follows: 

msg_no routine label text 

msg_no 2-digit message number 

routine name of the routine generating the message (1 to 8 

characters) 

label name of the routine in the transaction driver that 

created the error message (1 to 8 characters) 

text variable error message text 

The Version 6.0-style CICS transaction driver messages are listed below in 

numeric order. 

.........................................................................................................................................................................................................˝.......................................... 

01 

xxxxxxxx xxxxxxxx COMMAND cccccccc FAILED - CONDITION 

yyyyyyyy 

where 

cccccccc CICS command that failed 

yyyyyyyy error condition 

This message is created when a CICS command error condition is detected. 



.........................................................................................................................................................................................................˝.......................................... 

02 


xxxxxxxx xxxxxxxx PROTOCOL VIOLATION HAS OCCURRED: 

pppppppppppppppppppp 

where 

pppppppppppppppppppp explanation of the protocol error 

The transaction driver will intercept CICS-detected LU6.2 protocol errors 

and display this message. A protocol error is typically due to the 

unanticipated failure of the partner session, although it could reflect an error 

in coding on one side or the other. 

.........................................................................................................................................................................................................˝.......................................... 

03 

xxxxxxxx xxxxxxxx AN ABEND HAS OCCURRED, ABCODE: 

cccccccccccccccccccc 

where 

cccccccccccccccccccc explanation of the abend 

If the user does not supply an abend handler routine, the transaction driver 

will intercept the CICS abend and display this message. 

.........................................................................................................................................................................................................˝.......................................... 

04 

xxxxxxxx xxxxxxxx XCTL WITH BAD COMMAREA LENGTH OR 

CMDLINE LENGTH 

If the consultation has tried to perform a switch to another CICS transaction 

and the XCTL fails, this message is issued. In general, this should be viewed 

as a transaction driver error and reported to PLATINUM Technical Support 


.........................................................................................................................................................................................................˝.......................................... 

05 

xxxxxxxx xxxxxxxx INVALID MAES OPTION -- CONSULTATION 

CANNOT CONTINUE 

The user tried to use the MAES= option on the command line and the 

requested name is greater than 8 characters.


.........................................................................................................................................................................................................˝.......................................... 

06 

xxxxxxxx xxxxxxxx CONSULTATION WITH mmmm HAS ENDED 

SUCCESSFULLY 

where 

mmmm the SYSIDNT of the MAES region 

When the consultation completes, this message confirms that it ended 

successfully. 

.........................................................................................................................................................................................................˝.......................................... 

07 

xxxxxxxx xxxxxxxx UNEXPECTED MESSAGE RECEIVED. TYPE: ttttt, 

SUBTYPE: sssss 

where 

ttttt the numeric ‘type’ of the message for diagnostic purposes 

sssss the numeric ‘subtype’ of the message for diagnostic purposes 

During the exchange of messages between the transaction driver and MAES, 

errors in the consultation can cause the messages to become unsynchronized. 

The transaction driver will recognize messages that are out of sequence and 

present this message. The consultation will not continue. You should first 

determine if the consultation performed properly by looking at the AionDS 

system log and system trace. Otherwise, report the problem to PLATINUM 


For more information: Consult “MAES-specific codes” in Chapter 5 for a 

description of these codes. 

.........................................................................................................................................................................................................˝.......................................... 

08 

xxxxxxxx xxxxxxxx SUBTASK ABEND IN MAES. wwwwww ABEND 

CODE ccccc 

A consultation abend has been detected. 




wwwwww either SYSTEM or USER, depending on the type of 

abend 

ccccc the abend code (in decimal). If the abend is a 

SYSTEM abend, this number should be converted 

to hexadecimal to determine the true abend 

condition. 

For more information: If the abend is a user abend, consult “MAESspecific 

codes” in Chapter 5 or consult Chapter 7. 

.........................................................................................................................................................................................................˝.......................................... 

09 

xxxxxxxx xxxxxxxx ZERO COMMAND LINE LENGTH DETECTED 

DURING FPL PROCESS 

A user transaction switched to AAES but the command line length was zero. 

This is invalid since the command line must contain the knowledge base 

name. 

.........................................................................................................................................................................................................˝.......................................... 

10 

xxxxxxxx xxxxxxxx NUMBER OF PDBS DOES NOT MATCH 

NUMBER OF INPUT PARMS 

On a CICS LINK to AAESFPL, the Fixed Parameter List PDB is 

inconsistent with the number of input parameters. Correct the calling 

program. 

.........................................................................................................................................................................................................˝.......................................... 

11 

xxxxxxxx xxxxxxxx UNKNOWN PDB TYPE DETECTED DURING FPL 

PROCESS 

The PDB contains 2-byte binary fields representing the type and length of 

each parameter. AAESFPL has detected a parameter type code that is invalid. 

Correct the calling program. 

.........................................................................................................................................................................................................˝.......................................... 

12 

xxxxxxxx xxxxxxxx NOT ENOUGH SPACE FOR OUTPUT DATA 

During FPL processing, data received from the inference engine is larger than 

the output area provided by the caller. Correct either the calling program or 

the knowledge base to make the data definitions consistent.


.........................................................................................................................................................................................................˝.......................................... 

13 

xxxxxxxx xxxxxxxx INVALID IDENTIFIER GIVEN FOR MAES, 

CONID, OR USERID 

During FPL processing, one of the three identifiers is found to be invalid. 

Correct the calling program. 

.........................................................................................................................................................................................................˝.......................................... 

14 

xxxxxxxx xxxxxxxx INPUT DATA TOO LARGE - MAXIMUM IS 21000 

BYTES 

The amount of data passed to the inference engine during FPL processing is 

limited by the size of the message VTAM will accept as well as overhead 

associated with the process. Correct the calling program. 

.........................................................................................................................................................................................................˝.......................................... 

15 

xxxxxxxx xxxxxxxx OUTPUT DATA TOO LARGE - MAXIMUM IS 

21000 BYTES 

The amount of data passed by the inference engine to the calling program 

during FPL processing is limited by the size of the message VTAM will accept 

as well as overhead associated with the process. Correct the calling program. 


IMS and TSO transaction driver messages 


.........................................................................................................................................................................................................˝.......................................... 

Overview 


This section lists the messages that are issued by the AionDS/IMS transaction 

driver, the TSO transaction driver, or both. The message format is described 

as follows: 

where 

tt Error nnnn: text 

tt one of the following: 

MS for errors occurring with MAES 

IM for errors occurring with IMS 

LR for errors occurring with VTAM 

TY for miscellaneous errors occurring with the 

transaction driver 

nnnn error number 

text descriptive text explaining the error condition 

The IMS and TSO transaction driver messages are listed below in numeric 

order. The header (tt Error) has been omitted for brevity. 

.........................................................................................................................................................................................................˝.......................................... 

(No error number) 

Development session ended 

The AionDS/IMS transaction driver displays this message at the end of a 

development session. This is informational only. 

.........................................................................................................................................................................................................˝.......................................... 


Consultation with xxxxxxxx ended 

The AionDS/IMS transaction driver displays this message at the end of 

consultation xxxxxxxx. This is informational only.


.........................................................................................................................................................................................................˝.......................................... 


Execution of xxxxxxxx complete 

The optimized knowledge base xxxxxxxx has finished executing. This is 

informational only. 

.........................................................................................................................................................................................................˝.......................................... 


Actions : nnn, seconds : ssss, average : aaaa 

where 

nnn indicates the total number of session terminal inputs 

ssss indicates the CPU time consumed by the transaction driver 

aaaa indicates the average CPU time consumed for each input 

The AionDS/IMS transaction driver displays this message at the end of each 

consultation or development session. This is informational only. 

.........................................................................................................................................................................................................˝.......................................... 


Session run on node xxxxxxxx 

The consultation was executed on the MAES region whose VTAM node 

name is xxxxxxxx. This is informational only. 

.........................................................................................................................................................................................................˝.......................................... 


Please press PA1 to continue 

When switching from the conversational transaction driver to a nonconversational 

transaction, IMS requires an intervening message. The 

transaction driver sends out this message, asking the user to press PA1 which 

will cause the first message from the target transaction to be displayed. 

.........................................................................................................................................................................................................˝.......................................... 

12 

Record from MAES is too large for the I/O area 

The message sent from MAES or SAES was larger than the user area 

provided. This error typically occurs when a user-written program attempts 

to drive the link and the AESIOLEN field is not set properly. 



.........................................................................................................................................................................................................˝.......................................... 

16 


Not enough storage to allocate I/O area for message 

The IMS and TSO transaction drivers buffer the entire message from MAES 

or SAES. If the original buffer is too small and not enough memory exists to 

allocate a new buffer, then the message is not transmitted and the AionDS 

transaction driver issues this error. If this error occurs, increase the region 

size of the of the MPR or TSO address space where the AionDS transaction 

driver resides. 

.........................................................................................................................................................................................................˝.......................................... 

20 

VTAM session is inactive 

The VTAM session to MAES was not active when AionDS tried to receive or 

send a message to MAES. Either the session was not properly opened 

through the program IAESSTIN or the session has been terminated. 

.........................................................................................................................................................................................................˝.......................................... 

24 

Negative length specified on a SEND 

The maximum length for any single message is 32,767 bytes. The 

AESMLEN field contains a value that is greater than the maximum, which 

appears as a negative number to the transaction. 

.........................................................................................................................................................................................................˝.......................................... 

28 

Data request error 

If you receive this error, report it to PLATINUM Technical Support for 


.........................................................................................................................................................................................................˝.......................................... 

32 

LU name was all blanks for an ACB OPEN 

The VTAM logical unit name of the AionDS transaction driver consisted of 

all blanks when IAESSTIN was called. This message indicates a problem 

with the IAESLUNM list of logical units.


.........................................................................................................................................................................................................˝.......................................... 

36 

The VTAM ACB on node xxxxxxx failed to OPEN properly (rr/cc) 

An error occurred trying to open the VTAM ACB on MAES node xxxxxxxx. 

The message includes the OPEN return code in register 15 (rr) as well as the 

ACB error code (cc). 

For more information: Refer to the IBM VTAM Programming manual for 

more information on the codes. 

.........................................................................................................................................................................................................˝.......................................... 

36 

The VTAM ACB failed to open properly (88/0) 

1 When the system programmer defined the transaction in the IMS 

generation, the transaction could have been made eligible for processing 

in two message process regions at the same time. Under normal 

circumstances, the transaction can only be processed by a single message 

processing region at any one time. 

The AionDS/IMS transaction driver uses the transaction name as the 

node name when opening the VTAM ACB. If two message regions try 

to process transactions from the same queue, the first one gets use of the 

node name and the second one fails and writes this error message. 

2 The message processing region can terminate without closing the ACB. 

Typically, this error is the result of an error with the transaction driver. 

The message processing region is left in a state where the ACB is still 

open and associated with that message processing region. The node 

name cannot be used in other regions or in that same message processing 

region. 

To alleviate this problem, you can stop the message processing region and 

then restart it. You can vary the VTAM node OFFLINE and then vary it 

back ONLINE from the VTAM operator’s console. 

.........................................................................................................................................................................................................˝.......................................... 

36 

The VTAM ACB failed to open properly (90/0) 

This error can be caused by running a consultation under IMS where the 

IMS transaction code has not been established as a VTAM node name. The 

AionDS/IMS transaction driver uses the transaction code as the application 

name in the VTAM ACB. 



.........................................................................................................................................................................................................˝.......................................... 

40 


OPNDST failed on node xxxxxxxx with RTNCD = rr and FDBK = ff 

The OPNDST VTAM function failed during the initialization of the session 

with MAES. The message includes the return code from the RPL (rr) and 

the code in the RPLFDBK2 field (ff). 

.........................................................................................................................................................................................................˝.......................................... 

44 

ACB not OPEN when terminating the session 

The ACB was not open when IAESTERM was called. Either the ACB was 

not opened by the AionDS transaction driver, or the session terminated and 

AionDS did not detect and handle the termination properly. 

.........................................................................................................................................................................................................˝.......................................... 

48 

CLSDST failed 

IAESTERM issues this message and other diagnostic information when a 

CLSDST fails. 

.........................................................................................................................................................................................................˝.......................................... 

52 

SEND failed 

IAESTERM and IAESSEND issue this message and other diagnostic 

information when a SEND fails. 

.........................................................................................................................................................................................................˝.......................................... 

56 

RECEIVE failed 

IAESTERM and IAESGET issue this message and other diagnostic 

information when a RECEIVE fails. 

.........................................................................................................................................................................................................˝.......................................... 

60 

Subroutine failed to complete its processing 

This informational message is preceded by other messages which identify the 

reason why the subroutine failed to complete.


.........................................................................................................................................................................................................˝.......................................... 

64 

Consultation stopped due to internal error 

Failure of an internal component has caused the transaction driver to 

terminate. Look for error messages in the JES job log and report the problem 

to PLATINUM Technical Support for AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

68 

Unknown message type received - mm rr 

An unrecognized message was received. The AionDS/IMS transaction driver 

expects a header at the beginning of each message. The header contains 

values which identify the data that follows. The message includes the value 

found the AESMTYPE field (mm), and the value found in the AESMREQ 

field (rr). The value in the AESMTYPE field was not recognized by the 


.........................................................................................................................................................................................................˝.......................................... 

72 

VTAM error encountered - RTNCD = rrr and FDBK = fff 

The message includes the return code (rrr) and the feedback information (fff) 

from the VTAM RPL. 

.........................................................................................................................................................................................................˝.......................................... 

76 

LU name for VTAM missing from PDBs 

This internal error message is issued by ADSFPL when an application 

program attempts to invoke a MAES-resident knowledge base without 

passing in a parameter descriptor block containing the VTAM node name. 

.........................................................................................................................................................................................................˝.......................................... 

84 

Node xxxxxxxx is inactive. Consultation cannot continue 

A consultation attempted to resume, but the MAES node that was processing 

that consultation is no longer active. 

.........................................................................................................................................................................................................˝.......................................... 

88 

No node name available for the transaction driver 

The VTAM node names to be used by ADSFPL were unavailable or not 

defined. The request by the user application program failed. 



.........................................................................................................................................................................................................˝.......................................... 

302 


Consultation abend : sssss code ccc 

SAES, SADS, or an optimized knowledge base terminated abnormally. The 

value sssss specifies either SYSTEM or USER. The value ccc is the abend 

code. 


description of the abend codes. 

.........................................................................................................................................................................................................˝.......................................... 

309 

Consultation lost. Possible timeout. 

The transaction driver is trying to resume a suspended consultation but 

MAES indicates the consultation cannot be found. This situation can 

happen under the following conditions: 

1 The consultation has timed out. 

2 A terminal database managed by the non-conversational transaction 

driver is corrupted. 

3 MAES has been recycled during the time the user received the last display 

and entered the response. 

.........................................................................................................................................................................................................˝.......................................... 

310 

Maximum tasks allocated to xxxxxxxx 

A consultation is being started against a specific MAES (node name 

xxxxxxxx). However, the number of active consultations is currently at the 

limit set by the MAES runtime parameter MAXTASKS. 

.........................................................................................................................................................................................................˝.......................................... 

311 

Unexpected subcode ss for mm message 

The message type mm is either not supported or not valid for subtype ss. For 

example, a VSAM data request is valid for CICS but not IMS. IMS rejects 

the request.


.........................................................................................................................................................................................................˝.......................................... 

333 

Cannot find the PCB for the report 

An attempt was made to route a report remotely under IMS, yet there was 

either no ALTPCB, or the CHNG call to the ALTPCB failed. 

.........................................................................................................................................................................................................˝.......................................... 

354 

Unexpected message type - mm, subcode - rr 

The AionDS/IMS transaction driver expects some messages to occur in a 

specific sequence. This message indicates that an unexpected message type 

(mm) subtype (rr), was received. Typically, this message indicates a 

synchronization problem between the knowledge base and the session partner. 


description of these codes. 

.........................................................................................................................................................................................................˝.......................................... 

361 

Value for xxxxxxxx is greater than 8 bytes 

The value xxxxxxxx is the name of the field passed to ADSFPL that is in error. 

For example, the length of the VTAM logical unit names cannot be greater 

than 8 bytes. 

.........................................................................................................................................................................................................˝.......................................... 

362 

User input data of nn bytes exceeds yy maximum 

The AionDS/IMS transaction driver has a limit on the amount of data that 

can be passed to the inference engine using ADSFPL. The limit is yy and the 

number of bytes provided to ADSFPL was nn. 

.........................................................................................................................................................................................................˝.......................................... 

363 

User output data of nn bytes exceeds yy maximum 

The AionDS/IMS transaction driver has a limit on the amount of data that 

can be received from the inference engine using ADSFPL. The limit is yy and 

the number of bytes in the output area provided to ADSFPL was nn. 



.........................................................................................................................................................................................................˝.......................................... 

365 


MAES address space is unavailable 

An attempt to BIND with a specific MAES address space failed. The MAES 

address space has not been started. 

.........................................................................................................................................................................................................˝.......................................... 

392 

Program quiesced on node xxxxxxxx, no new users allowed 

A request to attach another subtask for the program SADS, SAES, or an 

optimized knowledge base has failed because the program in question has 

been quiesced through the MONITOR KB. No new users will be allowed in 

until all active users have finished and the program is reactivated. Contact 

your AionDS system administrator to resolve this error. 

.........................................................................................................................................................................................................˝.......................................... 

811 

Driver and xxxxxxxx versions do not match 

The version of MAES (node name xxxxxxxx) and the transaction driver are 

incompatible. 

.........................................................................................................................................................................................................˝.......................................... 

900 

Node xxxxxxxx is invalid for LU6.2 connection 

VTAM node xxxxxxxx is unknown to VTAM. This is produced by the 

IMS/CPO server program. 

.........................................................................................................................................................................................................˝.......................................... 

902 

Node xxxxxxxx is not an LU6.2 node 

Node xxxxxxxx is one of the possible OS/2 or other communication partners 

for IMS/CPO. However, the VTAM protocol used during the BIND 

process was not LU6.2. The attempt to BIND failed. 

.........................................................................................................................................................................................................˝.......................................... 

903 

No sessions available for LU6.2 node xxxxxxxx 

The IMS/CPO function attempted to communicate with BAES or MAES. 

However, not enough parallel sessions have been defined.


.........................................................................................................................................................................................................˝.......................................... 

904 

Node xxxxxxxx is inactive 

The IMS/CPO function attempted to BIND to the node xxxxxxxx. 

However, the node is not active. 

.........................................................................................................................................................................................................˝.......................................... 

905 

No sessions for node xxxxxxxx bound 

An LU6.2 connection between IMS/CPO and MAES (for remote knowledge 

base) or BAES (for the DL/I data server) failed because no sessions were 

bound between MAES and the PC. Typically, this indicates a problem in the 

connection definition on the PC or at the VTAM level. 

.........................................................................................................................................................................................................˝.......................................... 

906 

CID for node xxxxxxxx is invalid 

An active session between IMS/CPO and xxxxxxxx failed causing an invalid 

conversation ID condition. Typically this will happen if xxxxxxxx is stopped 

while still processing messages with IMS/CPO. 

.........................................................................................................................................................................................................˝.......................................... 

907 

Attempted to free an unowned session for node xxxxxxxx 

An internal error caused the IMS/CPO function to attempt a release of a 

VTAM session owned by the VTAM partner. This error should be reported 

to PLATINUM Technical Support for AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

908 

Free session for node xxxxxxxx invalid - bad owner 

An attempt to free a VTAM session failed. This is an internal error and 

should be reported to PLATINUM Technical Support for AionDS. 



.........................................................................................................................................................................................................˝.......................................... 

916 


COMMREC parameter missing for REMOTE KB request 

A remote knowledge base request was detected but the COMMREC 

parameter was missing. The COMMREC parameter describes the MAES 

node that contains the remote knowledge base and the name of the remote 


For more information: See the AionDS/IMS Installation and Operation 

Guide for more information on remote knowledge bases. 

.........................................................................................................................................................................................................˝.......................................... 

3150 

Knowledge base name is missing 

You entered the transaction code and did not specify a knowledge base name 

or the RUNADS ($ADS) string for a development session. 

.........................................................................................................................................................................................................˝.......................................... 

3151 

Request was rejected by the user edit routine 

A user-written input edit routine rejected the input message. You can 

override this default message in the input edit routine. 

.........................................................................................................................................................................................................˝.......................................... 

3155 

Unable to get the SPA - status xx 

The conversational version of the AionDS/IMS transaction driver 

encountered an error when it tried to retrieve the SPA. The value xx indicates 

the PCBSTATUS code. 

.........................................................................................................................................................................................................˝.......................................... 

3156 

SA error - suspend failed - code ccc 

The AionDS/IMS transaction driver attempted to suspend the consultation 

but the suspend failed with code ccc. The consultation is terminated. 

.........................................................................................................................................................................................................˝.......................................... 

3157 

PCB status xx encountered in module mmmmmmmm 

An unexpected PCB status code xx was encountered while module 

mmmmmmmm was executing.


.........................................................................................................................................................................................................˝.......................................... 

3158 

Report to xxxxxxxx failed - no PCB available 

A report was formatted and targeted for the xxxxxxxx logical terminal but 

could not be sent because no alternate I/O PCB or modifiable PCB for the 

xxxxxxxx logical terminal was found. 

.........................................................................................................................................................................................................˝.......................................... 

3159 

xxxx call failed with status ss 

Call xxxx failed with PCB status code ss. This error can occur when you edit 

PCBs for logical terminal output. 

.........................................................................................................................................................................................................˝.......................................... 

3160 

xxxxxxxx is an unknown destination for output 

Output targeted for the xxxxxxxx logical terminal could not be sent because 

no alternate I/O PCB or modifiable PCB could be found. 

.........................................................................................................................................................................................................˝.......................................... 

3161 

No program was specified for $EXE option 

The user attempted to execute an optimized knowledge base using $EXE 

KBNAME but neglected to specify KBNAME. 

.........................................................................................................................................................................................................˝.......................................... 

3162 

The program specified for $EXE was more than 8 bytes 

The length of an optimized knowledge base name cannot exceed 8 bytes. 

.........................................................................................................................................................................................................˝.......................................... 

3165 

Unable to allocate nnn bytes of memory 

The transaction driver attempted to acquire nnn bytes of memory but was 

unsuccessful. Increase the region size for the message processing region and 

try the request again. 



.........................................................................................................................................................................................................˝.......................................... 

3167 


No MAES resources available to run a consultation 

A new consultation was being initialized but either the potential MAES server 

regions were not started, or the number of consultations active in the MAES 

regions had already reached the limit set by the MAES runtime parameter 

MAXTASKS. 

.........................................................................................................................................................................................................˝.......................................... 

3168 

Unable to get the message - status xx 

The transaction driver’s attempt to retrieve a message from the message queue 

failed with the DL/I status code of xx. 

.........................................................................................................................................................................................................˝.......................................... 

4000 

SPA length invalid - check definition in IAESTABL 

The conversational transaction driver read in the SPA and discovered that the 

length of the SPA is less than the combination of the expected length (50 

bytes) and the SPA offset (defined in IAESTABL). 

.........................................................................................................................................................................................................˝.......................................... 

4001 

Invalid data in the start message. Consult ADSILOG 

This error can occur during the consultation of a non-conversational KB. 

When the user presses ENTER on the last screen of a timed-out consultation, 

the non-conversational transaction driver attempts to start a new 

consultation. It gives the 3270 data from the screen as the knowledge base 

name because it can’t find a SPA in MAES that corresponds with this 

terminal. The 3270 data is invalid as a knowledge base name. The 

ADSILOG shows what the non-conversational transaction driver was trying 

to formulate as a start message. 

.........................................................................................................................................................................................................˝.......................................... 

6009 

Node xxxxxxxx has died. Unable to resume your consultation 

MAES node xxxxxxxx is no longer active. Your consultation cannot continue. 

This error could result from MAES being canceled.


.........................................................................................................................................................................................................˝.......................................... 

6016 

Fatal error - SPA does not exist 

A message switch was attempted from the non-conversational transaction 

driver (AIONNC) where the user specified “txnid TRANSFER SPA” yet the 

transaction specified (txnid) is non-conversational. 

.........................................................................................................................................................................................................˝.......................................... 

6017 

‘I=’override greater than 8 bytes 

An attempt to override the IPPCB-USERIDE using the :I command line 

option failed due to an excessive number of characters. User IDs are limited 

to 8 characters. 



2-30 AionDS Messages and Codes

Chapter 3 

CICS/VS Exception Conditions 

.........................................................................................................................................................................................................˝.......................................... 

Introduction 

This chapter describes the EIB codes returned from EXEC CICS calls issued 

by the AionDS/CICS transaction driver. 

The following codes are returned by CICS as the result of an EXEC CICS 

command issued by the AionDS/CICS transaction driver. The codes are 

returned to the knowledge base and included as part of the error message 

written to the AionDS system log. In addition, certain codes can appear in 

error messages displayed by the transaction driver on the terminal. 

For example, if a remote VSAM select fails, the following message might be 

written to the AionDS system log: 

ADS32599 W Select TAEKEY2 INVREQ 12-1103,710 

1103 is the CICS return code that was passed back from the AionDS/CICS 


.........................................................................................................................................................................................................˝.......................................... 


Topic Page 

CICS/VS exception conditions 3-2 

CICS/VS Exception Conditions 3-1

CICS/VS exception conditions 


.........................................................................................................................................................................................................˝.......................................... 

Overview 


The following EIB codes can be returned from EXEC CICS calls issued by 

the AionDS/CICS transaction driver. 

.........................................................................................................................................................................................................˝.......................................... 

1100 

PGMIDERR condition detected. 

See the IBM CICS Application Programmer’s Reference Manual. 

.........................................................................................................................................................................................................˝.......................................... 

1102 

CBIDERR condition detected. 

See the IBM CICS Application Programmer’s Reference Manual for 

information on terminal control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1103 

INVREQ condition detected. 

See the IBM CICS Application Programmer’s Reference Manual. 

.........................................................................................................................................................................................................˝.......................................... 

1104 

INBFMH condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1105 

NOTALLOC condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1106 

LENGERR condition detected. 

See the IBM CICS Application Programmer’s Reference Manual.


.........................................................................................................................................................................................................˝.......................................... 

1107 

SESSIONERR condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1108 

SIGNAL condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1109 

SYSIDERR condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1110 

SESSBUSY condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1111 

SYSBUSY condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1112 

“link out of service”. 


information on “Link Out of Service.” 

.........................................................................................................................................................................................................˝.......................................... 

1113 

Name Unknown to CICS/VS. 


information on “Name Unknown to CICS/VS.” 



.........................................................................................................................................................................................................˝.......................................... 

1114 


DSIDERR condition detected. 


information on file control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1115 

ILLOGIC condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1116 

NOTOPEN condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1117 

DISABLED condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1118 

ENDFILE condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1119 

IOERR condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1120 

NOTFND condition detected. 


information on file control exceptional conditions.


.........................................................................................................................................................................................................˝.......................................... 

1121 

DUPREC condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1122 

NOSPACE condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1123 

DUPKEY condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1124 

ISCINVREQ condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1125 

NOTAUTH condition detected. 



.........................................................................................................................................................................................................˝.......................................... 

1126 


information on ITEMERR and temporary storage exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1127 


information on QIDERR and temporary storage exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1128 


information on RETPAGE and BMS exceptional conditions. 



.........................................................................................................................................................................................................˝.......................................... 

1129 



information on MAPFAIL and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1130 


information on INVMPSC and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1131 


information on INVERRTERM and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1132 


information on RTESOME and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1133 


information on RTEFAIL and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1134 


information on WRBRK and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1135 


information on RDATT and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1136 


information on PARTNFAIL and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1137 


information on INVPARTN and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1138 


information on INVPARTNSET and BMS exceptional conditions.


.........................................................................................................................................................................................................˝.......................................... 

1139 


information on INVLDC and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1140 


information on UNEXPIN and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1141 


information on IGREQCD and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1142 


information on TSOIOERR and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1143 


information on OVERFLOW and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1144 


information on EOC and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1145 


information on IGREQID and BMS exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1146 


information on TRANSIDERR and interval control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1147 


information on TERMIDERR and interval control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1148 


information on INVTSREQ and interval control exceptional conditions. 



.........................................................................................................................................................................................................˝.......................................... 

1149 



information on EXPIRED and interval control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1150 


information on ENDDEFERR and interval control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1151 


information on QZERO and transient data control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1152 


information on QBUSY and transient data control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1153 


information on ENQBUSY and task control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1154 


information on ROLLEDBACK and sync point exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1155 


information on NOSTG and storage control exceptional conditions. 

.........................................................................................................................................................................................................˝.......................................... 

1156 


information on EXEC interface command and response codes. 

.........................................................................................................................................................................................................˝.......................................... 

1157 


information on EXEC interface command and response codes. 

.........................................................................................................................................................................................................˝.......................................... 

1158 


information on TERMERR and terminal control exceptional conditions.


.........................................................................................................................................................................................................˝.......................................... 

1206 

Invalid “file command code”. 

An invalid or unsupported file command request was received by the 

transaction driver. This error should be reported to PLATINUM Technical 


.........................................................................................................................................................................................................˝.......................................... 

1207 

Invalid length on a variable length parameter. 

A request prepared by SAES or an external routine contained a parameter 

with an invalid length. Some messages passed to the transaction driver 

contain a number of parameters in the message text. Each of these 

parameters is of the general form: 

where 

length parm_flag data 

length 2-byte length field 

parm_flag one-byte parameter flag 

data data associated with the parameter 

This error is issued if the length is zero, the length is negative, or the length is 

greater than the remainder of the message. 

.........................................................................................................................................................................................................˝.......................................... 

1208 

Too many parameters in the request. 

Given the general format of some requests as shown in message 1207, if the 

transaction driver processes the message and finds the information needed to 

complete the request before processing all the parameters in the message, it 

assumes that the message is improperly coded and produces status 1208. 

This condition can happen if SAES or a user external routine erroneously 

duplicates parameters in the message or includes information not needed for 

the request type. 



.........................................................................................................................................................................................................˝.......................................... 

1209 


Set error. 

MAES manages messages as a series of elements in a set. The transaction 

driver detected an invalid set sequence. For example, a middle-in-set was 

received following a last-in-set. This message reflects a program problem 

either in MAES/SAES or in a user-written external routine. Activate the 

MAESLOG and recreate the condition. The output of the MAESLOG will 

be used by PLATINUM Technical Support for AionDS to isolate the 

problem. 

.........................................................................................................................................................................................................˝.......................................... 

1210 

Record ID missing from a data request. 

The VSAM file request type requires a key, relative byte address, or relative 

record number. None of these were supplied. This is typically an application 

program error. 

.........................................................................................................................................................................................................˝.......................................... 

1211 


information on INVALID TERMINAL IDENTIFIER and route list format. 

.........................................................................................................................................................................................................˝.......................................... 

1212 


information on TERMINAL NOT SUPPORTED UNDER BMS and route 

list format. 

.........................................................................................................................................................................................................˝.......................................... 

1213 


information on OPERATOR NOT SIGNED ON and route list format. 

.........................................................................................................................................................................................................˝.......................................... 

1214 


information on OPERATOR SIGNED ON UNSUPPORTED 

TERMINAL and route list format. 

.........................................................................................................................................................................................................˝.......................................... 

1215 


information on INVALID LCD MNEMONICS and route list format.


.........................................................................................................................................................................................................˝.......................................... 

1300 

DL/I database not open. 

CICS/VS rejected a DL/I request because the database was not open. The 

CICS/VS console log should indicate why the database was not opened when 

CICS/VS was initialized. 

.........................................................................................................................................................................................................˝.......................................... 

1301 

Invalid DL/I call. 

A DL/I call was required but CICS/VS discovered an error before passing 

control to DL/I. The UIBFCTR field has been set to X'08' by CICS/VS. 

For more information: See the IBM CICS Application Programmer’s 

Reference Manual for information on DL/I interface response codes. 

.........................................................................................................................................................................................................˝.......................................... 

1302 

PCB address is invalid. 

A DL/I request was issued to CICS/VS but the address of the passed PCB 

was invalid. This condition represents an internal logic error in the 


.........................................................................................................................................................................................................˝.......................................... 

1304 

Scheduling conflict. 

The DL/I request was rejected due to a scheduling conflict. See the CICS/VS 

console log to determine the cause of the error. 

.........................................................................................................................................................................................................˝.......................................... 

1305 

Request for an invalid database. 

The DL/I request was rejected when CICS/VS could not find the database 

name in the FCT or the database was unopened as reflected in the FCT or an 

invalid argument was passed to DL/I. 

.........................................................................................................................................................................................................˝.......................................... 

1306 

PSB not found. 

The transaction driver attempted to allocate the PSB but instead was rejected 

when CICS/VS could not find the named PSB. 



.........................................................................................................................................................................................................˝.......................................... 

1307 


Transaction unauthorized. 

The DL/I request was rejected when CICS/VS determined that the 

transaction had not been properly authorized to use that function. 

.........................................................................................................................................................................................................˝.......................................... 

1308 

PSB already scheduled. 

Due to an internal error, the transaction driver attempted to schedule a PSB a 

second time. 

.........................................................................................................................................................................................................˝.......................................... 

1309 

Language conflict. 

CICS/VS rejected a DL/I request because of a conflict between the language 

being used and what was specified in the PSB. 

.........................................................................................................................................................................................................˝.......................................... 

1310 

PSB initialization failed. 

The transaction driver attempted to schedule the PSB but the request failed 

when CICS/VS could not initialize the PSB. See the CICS/VS console log to 

determine the specific error CICS/VS encountered. 

.........................................................................................................................................................................................................˝.......................................... 

1311 

PSB not authorized. 

CICS/VS rejected a DL/I request because the program was not authorized to 

issue that specific request. For example, if the transaction driver issued an 

ISRT request yet the PSB only authorized the program to retrieve segments, 

error 1311 would be reported. 

.........................................................................................................................................................................................................˝.......................................... 

1312 

Unscheduled termination. 

A DL/I request was rejected due to an unscheduled termination. 

.........................................................................................................................................................................................................˝.......................................... 

1313 

Function unscheduled. 

A DL/I request was rejected and the function unscheduled.


.........................................................................................................................................................................................................˝.......................................... 

1314 

DL/I not active. 

CICS/VS rejected a DL/I request because DL/I was not active. 

.........................................................................................................................................................................................................˝.......................................... 

1315 

Unrecognized DL/I status code. 



was returned in UIBFCTR. 

.........................................................................................................................................................................................................˝.......................................... 

1316 

Unrecognized DL/I status code. 



was returned in UIBDLTR. 

.........................................................................................................................................................................................................˝.......................................... 

1317 

Search for data segment. 

The transaction driver sets this internal status condition when it needs the 

data segment in the message to satisfy the user request. It will not appear as a 

message or an error condition. 

.........................................................................................................................................................................................................˝.......................................... 

1318 

Data segment not provided. 

To satisfy an ISRT, DLET, or REPL DL/I request, the SAES program or the 

user-written external routine must pass or return the segment in question. 

The transaction driver could not find the segment in the message requesting 

the insert, delete, or replace. 



3-14 AionDS Messages and Codes

Chapter 4 

DB/DC Program Interface Return 

Codes 

.........................................................................................................................................................................................................˝.......................................... 

Introduction 

This chapter describes the codes returned from the following DB/DC 

Program Interface Routines: 

AionDSMSW (Message Switching Function) 

AionDSULINK (User Link Facility) 

AionDSPSB (Schedule a New PSB - AionDS/CICS only) 

AionDSMOD (Schedule a New IMS Mod Name - AionDS/IMS 

only) 

Note: If the return code from the specified program interface routine is not 

listed below, then some type of general MAES error occurred. See “MAESspecific 

codes” in Chapter 5 for a listing of MAES-specific codes. 

.........................................................................................................................................................................................................˝.......................................... 


Topic Page 

ADSMSW (Message switching function) 4-2 

ADSULINK (User link facility) 4-4 

ADSPSB (Schedule a new PSB - AionDS/CICS only) 4-6 

ADSMOD (Schedule a new IMS Mod Name - AionDS/IMS only) 4-8 

DB/DC Program Interface Return Codes 4-1

ADSMSW (Message switching function) 


.........................................................................................................................................................................................................˝.......................................... 

Introduction 


The codes described below can be returned by the ADSMSW Program 

Interface Routine. 

.........................................................................................................................................................................................................˝.......................................... 

354 

Unexpected message type. 


was inconsistent with the current state of the transaction driver. Contact 


.........................................................................................................................................................................................................˝.......................................... 

368 

Invalid program or queue name in the command string. 

(CICS) 

The message switch failed because the CICS program or transient data queue 

was not found. Correct the name in the command string. 

.........................................................................................................................................................................................................˝.......................................... 

368 

Invalid transaction name in the command string. (IMS) 

One of the following conditions was encountered: 

■ The PSB did not have an alternate I/O PCB for the target transaction. 

■ The PSB did not have a modifiable PCB. 

■ The change call (CHNG) to the modifiable PCB failed. 

Correct the PSB to either provide an alternate I/O PCB for the target 

transaction, or add a modifiable PCB that the IMS transaction driver can use. 

If either of those PCBs exist, be sure that the name of the transaction in the 

knowledge base is correct. 

.........................................................................................................................................................................................................˝.......................................... 

1001 

The command string is empty. 

Correct the command string in the AionDS Process object that called 

ADSMSW.


.........................................................................................................................................................................................................˝.......................................... 

1002 

Unrecognized keyword in command string. 

Check the MAESLOG for the keyword that ADSMSW did not recognize. 

Correct the command string in the AionDS Process object that called 

ADSMSW. 

.........................................................................................................................................................................................................˝.......................................... 

1003 

Output parameter found where none required. 

Correct the AionDS Process object that called ADSMSW. ADSMSW does 

not expect any data to be returned from the target application or program. 

.........................................................................................................................................................................................................˝.......................................... 

1020 

Message switch attempted from AionDS. 

A message switch cannot be performed during execution under a 

development session (AionDS). Only AionES and optimized knowledge 

bases are enabled to perform message switches. 


ADSULINK (User link facility) 


.........................................................................................................................................................................................................˝.......................................... 

Introduction 


The codes described below can be returned by the ADSULINK Program 


.........................................................................................................................................................................................................˝.......................................... 

354 

Unexpected message type. 


was inconsistent with the current state of the transaction driver. Contact 


.........................................................................................................................................................................................................˝.......................................... 

369 

Program name greater than 8 bytes. 

Correct the name of the target CICS program or IMS transaction. 

.........................................................................................................................................................................................................˝.......................................... 

370 

More than 1 input parameter found. 

ADSULINK supports a single input parameter to be sent to the target CICS 

program or IMS transaction. 

Correct the Process object. There can only be three input parameters: 

■ the program name 

■ the command line 

■ an optional data parameter to be sent to the target CICS program or IMS 

transaction


.........................................................................................................................................................................................................˝.......................................... 

371 

More than 1 output parameter found. 

ADSULINK supports a single output parameter to be set by the target CICS 

program or IMS transaction. 

Correct the Process object. There can only be two output parameters: 

■ the return code 

■ an optional data parameter to be set by the target CICS program or IMS 

transaction 

.........................................................................................................................................................................................................˝.......................................... 

372 

No program name. 

ADSULINK was unable to locate a target CICS program name or IMS 

transaction name in the command string. Correct the command string. 

.........................................................................................................................................................................................................˝.......................................... 

373 

Program not found. 

ADSULINK attempted to invoke a CICS program or an IMS transaction, 

but the program or transaction did not exist. 


ADSPSB (Schedule a new PSB - AionDS/CICS only) 


.........................................................................................................................................................................................................˝.......................................... 

Introduction 


The codes described below can be returned by the ADSPSB Program 


.........................................................................................................................................................................................................˝.......................................... 

0 

The new PSB was scheduled successfully. 

.........................................................................................................................................................................................................˝.......................................... 

200 

The VTAM send failed to send the PSB request to the AionDS/CICS 


.........................................................................................................................................................................................................˝.......................................... 

300 

The VTAM get failed to receive a confirmation from the AionDS/CICS 

transaction driver that the new PSB had been scheduled. 

.........................................................................................................................................................................................................˝.......................................... 

1300 

DL/I database not open. The CICS/VS console log should indicate why the 

database was not opened when CICS/VS was initialized. 

.........................................................................................................................................................................................................˝.......................................... 

1301 

Invalid DL/I call. 

.........................................................................................................................................................................................................˝.......................................... 

1304 

Scheduling conflict. See the CICS/VS console log to determine the cause of 

the error. 

.........................................................................................................................................................................................................˝.......................................... 

1306 

PSB not found. The PSB was not defined to CICS/VS. 

.........................................................................................................................................................................................................˝.......................................... 

1307 

Transaction unauthorized. CICS/VS determined that the transaction had 

not been properly authorized to use that function. 

.........................................................................................................................................................................................................˝.......................................... 

1308 

PSB already scheduled. A request was made to schedule a PSB a second time.


.........................................................................................................................................................................................................˝.......................................... 

1310 

PSB initialization failed. See the CICS/VS console log to determine the 

specific error CICS/VS encountered. 

.........................................................................................................................................................................................................˝.......................................... 

1314 

DL/I not active. CICS/VS rejected the request because DL/I was not active. 


ADSMOD (Schedule a new IMS Mod Name - AionDS/IMS only) 

ADSMOD (Schedule a new IMS Mod Name - AionDS/IMS 

only) 

.........................................................................................................................................................................................................˝.......................................... 

Introduction 


The codes described below can be returned by the ADSMOD Program 


In addition, a variety of codes could be returned if the VTAM connection 

fails between MAES and the IMS region. 

For more information: See Chapter 5 for a complete list of possible error 

codes. 

.........................................................................................................................................................................................................˝.......................................... 

0 

The new mod name was scheduled successfully. 

.........................................................................................................................................................................................................˝.......................................... 

1001 

No input parameters to ADSMOD. The mod name must be specified in the 

command line of the RUN PROGRAM Process object that invokes 

ADSMOD.

Chapter 5 

MAES Error Codes 

.........................................................................................................................................................................................................˝.......................................... 

Introduction 

This chapter describes communication codes and error codes used by MAES 

when communicating with a partner logical unit. These return codes can be 

displayed in a variety of places. Typically, they appear in transaction driver 

messages displayed on the terminal as the result of a communication or 

protocol error between the transaction driver and MAES. 

.........................................................................................................................................................................................................˝.......................................... 


Topic Page 

MAES-specific codes 5-2 

MAES Error Codes 5-1

MAES-specific codes 


.........................................................................................................................................................................................................˝.......................................... 

Overview 


The following codes are used by MAES and the transaction drivers to build 

communication messages. In addition, error codes that can be set as the 

result of communication, protocol, database, or application errors are 

contained here. The MAESERRC member of the MACLIB database, 

provided on the AionDS/CICS and AionDS/IMS distribution tapes, contains 

this information in machine-readable form. 

These error codes can be displayed on the user’s terminal as part of 

transaction driver error messages, in the AionDS system log as part of error 

and remote database messages, and in the MAESLOG to document message 

traffic flow between the partner logical unit and MAES. 

.........................................................................................................................................................................................................˝.......................................... 

100 

User input message sent to MASES. This message is probably displayed 

because of a protocol error or possibly an invalid message switch from a user 

program to the transaction driver. The following codes are the type of user 

input message sent to MAES: 

Code number Description 

102 User 3270 Data Stream. The input is the input form an 

AionDS screen. 

103 User Field-by-Field. This input is in the form of an FPL 

.........................................................................................................................................................................................................˝.......................................... 

200 

Screen output message. This is displayed when a screen is sent to the 

transaction driver out of sequence. For example, you start an embedded 

knowledge base by calling AAESFPL and the knowledge base sends a screen 

(abort of user sourcing screen). Since screens are not allowed in embedded 

processing, this error code can be displayed. The following codes are the type 

of screen output message:


202 3270 Data Stream. Normal AionDS screen. 

206 ADSMSW requested a message switch. 


207 Field-by-field unblocked message. The output parameters 

for an FPL are being sent back. 

208 The knowledge base called ADSMOD to set a new IMS 

MODNAME for the next report to use. 

.........................................................................................................................................................................................................˝.......................................... 

300 

A status message was received. The following codes are the type of the status 

messages: 


308 Consultation end request. The knowledge base stopped 

unexpectedly. 

309 Timeout on the MAES side. Avoid timing out by 

increasing the TIME MAESPARM. 

310 Maxtask limit reached in MAES. 

350 Generic failure in the message protocols. 



Return codes 

.........................................................................................................................................................................................................˝.......................................... 

Return codes from 

ADSULINK 


Return Code Description 

369 Program name > 8 bytes 

370 More than 1 input found 

371 More than 1 output found 

372 No program name 

373 Program not found on user link 

374 Send response to TD 

375 Bad DB2 commit 

376 No CID during bind processing 

377 Failed program security check (the request was rejected by 

the program specified in the PGMSEC MAES parameter) 

378 MAES node not found 

379 Bad PCB change request 

380 Unused 

381 Receive attempted while in send mode 

382 Send attempted while in receive mode 

383 Did not receive expected change 

384 No input parameter specified 

385 Send attempted before going through the whole of the 

receive buffer 

386 Tried to send FMH5 in middle of RU 

387 No LUs available for the TD 

388 Session was lost (line is out) 

continued

continued 

Return Code Description 

389 Send attempted between brackets 

398 DB2 cols > than request 


399 Duplicate consultation direction (essentially same as 382) 

400 Data request message type 

401 DL/I database SSAS 

402 CICS VSAM request 

403 DB2 request 

404 User-program request 

406 Schedule a new PSB (CICS) 

450 SQL connect request 

460 Schedule a KB specified PSB 

499 'Other' data request type 

500 Data message block 

501 DL/I database segments 

502 CICS VSAM records 

503 DB2 data 

504 User-program response 

580 X-memory bind information 

598 Parameter data between TD and MAES 

599 'Other' data types 

600 Report message block 

700 User-defined message type 



.........................................................................................................................................................................................................˝.......................................... 


AAESVSAM 


The following return codes from AAESVSAM are printed in the ADSLOG. 

Return code Description 

1206 Invalid VSAM file request 

1207 Invalid input parameter length 

1208 Too many input parameters 

1210 No VSAM record ID 

1219 No key specified (a zero length key) 

1220 Invalid input data flag 

1221 Invalid input data 

1222 Input keys conflict 

.........................................................................................................................................................................................................˝.......................................... 


AAESDLI 

The following return codes from AAESDLI are printed in the ADSLOG. 


1300 DL/1 not open 

1301 DL/1 invalid request 

1302 DL/1 invalid PCB address 

1304 DL/1 scheduling conflict 

1306 DL/1 PSB not found 

1307 DL/1 task not authorized 

1308 DL/1 PSB already scheduled 

1309 DL/1 language conflict 

1310 DL/1 PSB initialization failed 

1311 DL/1 PSB not authorized 

1312 DL/1 terminal unscheduled 

continued

continued 


1313 DL/1 function unscheduled 

1314 DL/1 not active 

1315 DL/1 UIBFCTR unknown 

1316 DL/1 UIBDLTR unknown 

1317 DL/1 data found 

1318 DL/1 data not found 




Request codes 

.........................................................................................................................................................................................................˝.......................................... 

CICS/VSAM request 

codes 


The following CICS/VSAM request codes are printed in the ADSLOG 

(MVSAMOPN in MAESMSG1). These codes are helpful in determining 

which remote VSAM request received an error. 

Request code Description 

700 Read only 

701 Read with update 

702 Write/Add 

703 Rewrite 

704 Delete 

705 Unlock 

706 Start browse 

707 Read next 

708 Read previous 

709 Reset browse 

710 End browse 

711 Get file characteristics

Status Codes 


.........................................................................................................................................................................................................˝.......................................... 

Status codes from the 

failure of the CICS 

command 

The status codes are displayed in the ADSLOG as the result of the failure of a 

remote request to process. For example: 

ADS32599 W Unlock TAE100P NOTOPEN,12-1116,705 

The following codes are the result of file control exceptions. You can find 

these codes in the CICS/MVS Application Programmer’s Reference. 

Label Code number 

#INVREQ 1103 

#LENGERR 1106 

#SYSIDER 1109 

#DSIDERR 1114 

#ILLOGIC 1115 

#NOTOPEN 1116 

#DISABLE 1117 

#ENDFILE 1118 

#IOERR 1119 

#NOTFND 1120 

#DUPREC 1121 

#NOSPACE 1122 

#DUPKEY 1123 

#ISCINVR 1124 

#NOTAUTH 1125 




You can find these codes in the CICS/MVS Application Programmer’s 

Reference. These codes are not limited to file control exceptions. 

Label Code number 

#PGMIDER 1100 

#ITEMERR 1126 

#TRIDERR 1146 

#TERMID 1147

Chapter 6 

MAESLOG Messages 

.........................................................................................................................................................................................................˝.......................................... 

Introduction 

The MAES component of Multitasking AionES creates an output log called 

MAESLOG. The MAESLOG can contain as much, or as little, information 

as desired by changing the values for the MAESLOG= execution parameter. 

The MAESLOG is designed to track the message traffic between MAES and 

the transaction drivers as well as the status of the consultations within the 

system. 

.........................................................................................................................................................................................................˝.......................................... 


Topic Page 

MAESLOG messages 6-2 

MAESLOG Message 6-1

MAESLOG messages 


.........................................................................................................................................................................................................˝.......................................... 

Syntax 


The MAESLOG messages (or log messages) have the following format: 

where 

-- version -- prog date time ---msg_txt 

[opt_info] 

version current version and module level of MAES 

prog name of the program that created the log message 

date date the program was assembled 

msg_no unique log message number 

time time of day and date when the log message was created 

msg_text optional text message 

opt_info specifically labeled control blocks used by the system 

(such as RPL or ALOG), or a hexadecimal dump of 

information needed for debugging 

Log messages from 1 to 9999 are informational only. Log messages 10000 

and higher indicate error conditions that require corrective action.


The following list shows the type of information that each log message, 

within the specified log message range, contains: 

Log Message Numbers Type of Information 

1000 - 1999 Task Management 

2000 - 2999 VTAM Management 

3000 - 3999 Control Block Dump 

4000 - 4999 Startup and Termination 

5000 - 5999 Partner Management 

11000 - 11999 Task Management 

12000 - 12999 VTAM Management 

13000 - 13999 Control Block Dump 

14000 - 14999 Startup and Termination 

15000 - 15999 Partner Management 

The MAESLOG messages are listed below in ascending numerical order. 

.........................................................................................................................................................................................................˝.......................................... 

1000 

MAESBFPL 

The transaction driver passed data to the inference engine in the form of a 

Fixed Parameter List (FPL). This does not mean that the transaction driver 

sent any data using FPL. Instead, the normal method of passing data to the 

attached subtask is in the FPL format. The transaction driver sends data to 

the inference engine prior to the starting of a new consultation. In the FPL 

format is the command line which is passed to the inference engine. This can 

be used to verify that the correct knowledge base is being started. 

.........................................................................................................................................................................................................˝.......................................... 

1001 

MAESETXR 

This log message is issued when a subtask ends normally. 

MAESLOG Messages 6-3


.........................................................................................................................................................................................................˝.......................................... 

1002 


MAESNCON 

This log message is issued when a consultation is being initialized and the 

program being attached is not SAES or SADS -- that is, the program being 

attached is an optimized knowledge base. An optimized knowledge base is 

run as its own program and is not interpreted under SAES and SADS. The 

name of the program being attached is printed as part of the log message. 

.........................................................................................................................................................................................................˝.......................................... 

1003 

MAESNCON 

This log message is issued immediately after the ATTACH SVC is issued. 

The command line passed to the subtask is printed as part of the log message. 

.........................................................................................................................................................................................................˝.......................................... 

1004 

MAESNCON 

This log message indicates that a consultation is being resumed. This log 

message is issued immediately after POSTing the subtask. The consultations 

are managed using WAIT/POST logic. 

.........................................................................................................................................................................................................˝.......................................... 

1005 

MAESSETX 

The statistics function ended normally and the MAESSTAT dataset was 

closed without any errors. 

.........................................................................................................................................................................................................˝.......................................... 

1008 

MAESITAR 

The timing analysis function ended after an error occurred while writing to 

the output dataset. 

.........................................................................................................................................................................................................˝.......................................... 

1500 

SAESGET 

The text, “MASTER POSTED,” means that MAES posted the daughter task 

with an error code. Typically, this is done at shutdown when MAES cleans 

up the current consultations.


.........................................................................................................................................................................................................˝.......................................... 

1501 

SAESGET 

A transaction driver sent the CONSULTATION STOP message to force the 

consultation to end. This can occur when the transaction driver has 

problems communicating with the DB/DC environment. The error detected 

in the transaction driver is propagated back to the consultation, causing an 

abnormal termination. 

.........................................................................................................................................................................................................˝.......................................... 

1502 

SAESGET 

When the transaction driver is about to send the next prompt or display to 

the user, the transaction driver tells the consultation under MAES to enter a 

wait state. This log message is issued prior to the subtask relinquishing 

control to MAES. 

.........................................................................................................................................................................................................˝.......................................... 

1503 

SAESGET 

RWAIT POSTED is issued under the following conditions: 

■ The transaction driver is resuming a suspended consultation. 

■ The amount of time that the consultation was waiting for the transaction 

driver to resume processing was greater than that specified on the TIME= 

execute parameter. 

■ MAES posted the suspended consultation to force termination due to a 

normal shutdown or abnormal conditions which are signaled by other 

MAESLOG messages. 

.........................................................................................................................................................................................................˝.......................................... 

1504 

SAESSEND 

This log message is produced when MAES posts the consultation. Typically, 

the consultation terminates normally. 



.........................................................................................................................................................................................................˝.......................................... 

1505 


SAESSTIN 

When this log message is issued at consultation initialization, it indicates that 

SAES, SADS, or an optimized knowledge base was entered properly. If this 

log message is not issued, the system configuration has significant problems. 

.........................................................................................................................................................................................................˝.......................................... 

1506 

SAESPGOT 

Paging was forced for this consultation, overriding normal demand paging. 

.........................................................................................................................................................................................................˝.......................................... 

2000 

MAES 

This log message is issued just prior to the VTAM OPEN call which MAES 

uses to establish a connection to VTAM for subsequent activities. Any errors 

in the OPEN call are detected after this log message is issued. 

.........................................................................................................................................................................................................˝.......................................... 

2001 

MAESCICS 

MAESCICS processes service manager data messages. This status message 

traces the request unit received on an LU6.2 service manager session. 

.........................................................................................................................................................................................................˝.......................................... 

2002 

MAESCICS 

This log message notes that a VTAM LUSTAT protocol message was 

received on an LU6.2 service manager session. 

.........................................................................................................................................................................................................˝.......................................... 

2003 

MAESCICS 

This log message shows an LU6.2 change number of sessions protocol 

message that was received on the service manager session.


.........................................................................................................................................................................................................˝.......................................... 

2004 

MAESCICS 

This log message displays a response to a LU6.2 exchange log names protocol 

message only if the Exchange Log Names (XLN) message sent from the 

session partner was sent on the service manager session. 

.........................................................................................................................................................................................................˝.......................................... 

2005 

MAESCNOS 

A change number of sessions (CNOS) was sent to the session partner. The 

message is either an initiated CNOS by MAES or a reply to the CNOS 

received by MAES. 

.........................................................................................................................................................................................................˝.......................................... 

2006 

MAESCSUB 

During deactivation of an APPC partner session, MAES cleans up internal 

control blocks used to manage the traffic sessions. This log message indicates 

that the cleanup routine was entered. 

.........................................................................................................................................................................................................˝.......................................... 

2007 

MAESETXR 

This log message indicates that MAESETSR determined that the RPL is still 

in use. MAESETSR cancels the VTAM RPL request and reuses the RPL. 

When MAESETSR terminates a subtask, MAESETSR uses the VTAM RPL 

that belongs to that subtask. If the subtask ended abnormally, the RPL 

might already be in use for traffic between the subtask and the transaction 

driver. 

.........................................................................................................................................................................................................˝.......................................... 

2008 

MAESLUNM 

This log message contains the text of any error condition found in 

MAESLUNM. 



.........................................................................................................................................................................................................˝.......................................... 

2009 


MAESLGON 

MAES received a LOGON request. This log message is issued at entry to 

MAESLGON, but before MAES determines if the request is from a valid 

session partner. 

.........................................................................................................................................................................................................˝.......................................... 

2010 

MAESLGON 

In response to a LOGON request, MAES issues a VTAM OPNDST call to 

the requester. This MAESLOG message shows the VTAM RPL and node 

initialization block (NIB) used for the successful OPNDST. 

.........................................................................................................................................................................................................˝.......................................... 

2011 

MAESLUNM 

The value specified for WIN was not a valid number. 

.........................................................................................................................................................................................................˝.......................................... 

2012 

MAESLUNM 

The value specified for MAX was not a valid number. 

.........................................................................................................................................................................................................˝.......................................... 

2013 

MAESNSEX 

In certain VTAM error situations (typically when a session is being unbound) 

the network services exit is given control. This log message reflects that fact 

and also logs the header information which is used to determine the reason 

for the error condition. 

.........................................................................................................................................................................................................˝.......................................... 

2014 

MAESRCVE 

After an outstanding VTAM RECEIVE call is completed, another RECEIVE 

call is issued. This log message indicates that the RECEIVE call can be 

completed with a message from any session bound to MAES which is not 

already in a specific mode with another MAES component.


.........................................................................................................................................................................................................˝.......................................... 

2015 

MAESLUNM 

The value specified for RU was not a valid number. 

.........................................................................................................................................................................................................˝.......................................... 

2016 

MAESLUNM 

The value of RU is either less than 256 or not a power of 2 (256, 512, 1024, 

and so on). 

.........................................................................................................................................................................................................˝.......................................... 

2017 

MAESSBND 

MAESSBND constructs the request unit for binding to another session. This 

log message shows the contents of the BIND image. 

.........................................................................................................................................................................................................˝.......................................... 

2018 

MAESSCIP 

A VTAM SCIP exit is given control. This log message indicates that one of 

the following conditions occurred: 

■ Request Recovery (RQR VTAM message) 

■ Set and TEST Sequence Numbers (STSN VTAM message) 

■ bind request 

■ session unbind 

■ clear 

MAESSCIP determines which condition occurred and acts accordingly. 

.........................................................................................................................................................................................................˝.......................................... 

2019 

MAESSCIP 

The MAES SCIP exit receives an UNBIND request. The reason code for the 

UNBIND request is logged with this log message. Typically, an UNBIND 

request occurs when the partner session terminates. 



.........................................................................................................................................................................................................˝.......................................... 

2020 


MAESSECS 

The SCIP VTAM exit routine received a BIND request. These requests are 

routed to MAESSECS. This log message contains the BIND parameters. 

.........................................................................................................................................................................................................˝.......................................... 

2021 

MAESSECS 

If a BIND request is accepted, MAES issues an OPNSEC call. This log 

message indicates that the OPNSEC call was issued. MAES checks to make 

sure that the OPNSEC call was successful. 

.........................................................................................................................................................................................................˝.......................................... 

2022 

MAESSERV 

Either the MONITOR knowledge base or MAES shutdown processing 

initiated a service request. This log message indicates that an active service 

manager session is being unbound by doing a VTAM CLSDST on the 

session. The session is owned by MAES. 

.........................................................................................................................................................................................................˝.......................................... 

2023 

MAESSERV 

As a result of a MONITOR request or shutdown processing, MAES 

terminates a traffic session with a session partner in a parallel sessions 

connection. This log message indicates that MAES issues a VTAM 

TERMSESS on the session. 

.........................................................................................................................................................................................................˝.......................................... 

2024 

MAESSERV 

As a result of a MONITOR request or shutdown processing, MAES 

terminates a service manager session with a session partner in a parallel 

sessions connection. This log message indicates that MAES issues a VTAM 

TERMSESS on the session. The session partner owns the session.


.........................................................................................................................................................................................................˝.......................................... 

2025 

MAESSMGE 

This log message records data received on a service manager session which is 

connected to a session partner in a parallel sessions connection. This MAES 

owns the session and, typically, reflects responses to MAES-initiated actions 

such as an exchange of log names (XLN). 

.........................................................................................................................................................................................................˝.......................................... 

2026 

MAESSMGE 

A message was received from a session response that required a VTAM 

response. This log message records that a response was sent. 

.........................................................................................................................................................................................................˝.......................................... 

2027 

MAESSMGE 

In response to a change number of sessions (CNOS) request sent on the 

service manager session owned by this MAES, the session partner sends the 

negotiated reply. MAES accepts the reply and logs the CNOS reply. 

.........................................................................................................................................................................................................˝.......................................... 

2028 

MAESSMGR 

When a MAES binds with a session partner in a parallel sessions connection, 

MAES binds a service manager session consistent with LU6.2 protocol. This 

log message is issued after the OPNDST call is executed and before the 

return code is examined. 

.........................................................................................................................................................................................................˝.......................................... 

2029 

MAESSUBS 

Prior to acquiring (OPNDST) a subsession with a session partner in a parallel 

sessions connection, MAESSUBS logs the VTAM node initialization block 

(NIB) for informational purposes. 



.........................................................................................................................................................................................................˝.......................................... 

2030 


MAESSYNA 

A VTAM error occurred. However, the error code indicates that the request 

can be retried. This log message is issued immediately before the retry 

attempt. 

.........................................................................................................................................................................................................˝.......................................... 

2031 

MAESRECP 

This log message is issued when MAESWALL is posted from its wait state 

because MAES received a VTAM LU6.2 LUSTAT message. The VTAM 

LU6.2 LUSTAT message is written to MAESLOG, and then MAES waits for 

more data. 

.........................................................................................................................................................................................................˝.......................................... 

2032 

MAESRECP 

MAES received a message that required a VTAM response. The point at 

which the message was received does not affect any current consultations. 

MAESERR is called to send the response. 

.........................................................................................................................................................................................................˝.......................................... 

2033 

MAESRECP 

MAES received a data message. This log message records the VTAM RPL as 

well as the content of the request unit. 

.........................................................................................................................................................................................................˝.......................................... 

2034 

MAESXLN 

MAES originates an exchange log names (XLN) request on the MAES-owned 

service manager session. This is a normal part of LU6.2 protocol. 

.........................................................................................................................................................................................................˝.......................................... 

2035 

MAESXLN 

MAES received an exchange log names (XLN) request from a session partner 

in a parallel sessions connection. Typically, this request requires a VTAM 

response. This log message records that MAES is responding to an XLN 

initiated by the session partner.


.........................................................................................................................................................................................................˝.......................................... 

2036 

MAESXLN 

This log message is issued after an exchange log names request was sent 

successfully to a partner session. 

.........................................................................................................................................................................................................˝.......................................... 

2038 

MAESAUTO 

MAES is not connected to VTAM, so a request for automatic acquisition of a 

session partner was cancelled. 

.........................................................................................................................................................................................................˝.......................................... 

2111 

MAESLUS 

This log message indicates that MAES is sending a VTAM protocol message 

(LUSTAT) which verifies that a session has been properly established and sets 

the traffic direction. In the current implementation, the message is not a 

proper LUSTAT. Instead, the message is a zero length data message with the 

appropriate protocol switches set. 

.........................................................................................................................................................................................................˝.......................................... 

2112 

MAESLUS 

This log message is issued after control is returned to MAES following a 

SEND of a LUSTAT message. 

.........................................................................................................................................................................................................˝.......................................... 

2116 

MAESRRN 

MAESSRN responds to an FMH7 from a session partner in a parallel sessions 

connection. An FMH7 typically indicates an abend condition which requires 

a response. MAESSRN sends the response. 

.........................................................................................................................................................................................................˝.......................................... 

2125 

MAESSMGE 

MAES attempted to use a service manager session, but the service manager 

session had already been unbound. 



.........................................................................................................................................................................................................˝.......................................... 

2135 


MAESRECP 

This log message shows the user’s input message and the VTAM RPL. 

.........................................................................................................................................................................................................˝.......................................... 

2208 

MAESETXR 

This log message indicates a change in the VTAM RPL status for a 

terminating consultation. If the associated transaction driver is an LU6.2 

(with parallel sessions) partner, the RPL associated with the terminating 

subtask is reset from SPECIFIC to ANY mode. 

.........................................................................................................................................................................................................˝.......................................... 

2500 

SAESGET 

If the consultation is waiting for data from the transaction driver, this log 

message is issued. This log message is issued just after a VTAM RECEIVE 

request is issued but before the WAIT is issued. 

.........................................................................................................................................................................................................˝.......................................... 

2501 

SAESGET 

This log message is issued when a message is received from the transaction 

driver. The VTAM request unit is recorded in MAESLOG. 

.........................................................................................................................................................................................................˝.......................................... 

2502 

SAESSEND 

This log message shows the contents of the VTAM RPL request prior to the 

actual VTAM SEND. This log message verifies the VTAM protocol of the 

outgoing request unit. 

.........................................................................................................................................................................................................˝.......................................... 

2503 

SAESSEND 

This log message shows the request unit that was sent as well as the contents 

of the VTAM RPL and the AionDS AESCB. At this point, VTAM accepted 

the message, and as long as no error indicators are in the RPL, the request 

unit was sent to the session partner.


.........................................................................................................................................................................................................˝.......................................... 

2504 

SAESSEND 

This log message confirms that VTAM returned control to the SAESSEND 

program, and that the message was accepted without errors. 

.........................................................................................................................................................................................................˝.......................................... 

2505 

SAES62 

An LU6.2 CONNECT request was issued for a secondary LU6.2 session. 

.........................................................................................................................................................................................................˝.......................................... 

2506 

SAES62 

The VTAM FMH5 request unit is logged prior to sending it through a 

secondary LU6.2 session. 

.........................................................................................................................................................................................................˝.......................................... 

2507 

SAES62 

An LU6.2 SEND request was issued for a secondary LU6.2 session. 

.........................................................................................................................................................................................................˝.......................................... 

2508 

SAES62 

An LU6.2 RECEIVE or WAIT request was issued for a secondary LU6.2 

session. 

.........................................................................................................................................................................................................˝.......................................... 

2509 

SAES62 

An LU6.2 FREE request was issued for a secondary LU6.2 session. 

.........................................................................................................................................................................................................˝.......................................... 

2510 

SAESGET 

This log message shows the entire input message from the transaction driver. 



.........................................................................................................................................................................................................˝.......................................... 

2512 


SAESGET 

A conditional end bracket (CEB) was received from the transaction driver. 

The VTAM session was reset. 

.........................................................................................................................................................................................................˝.......................................... 

3000 

MAESNCON 

This log message is issued immediately after log message 1004. This log 

message is a dump of internal control blocks which PLATINUM Technical 

Support for AionDS can use for debugging task management errors. 

.........................................................................................................................................................................................................˝.......................................... 

3002 

MAESWALL 

The control blocks were dumped after MAESLOG message 4023. Log 

message 4023 is still issued, but the control blocks are not recorded. 

.........................................................................................................................................................................................................˝.......................................... 

3003 

MAESWALL 

The control blocks were dumped after MAESLOG message 4033. Log 

message 4033 is still issued, but the control blocks are not recorded. 

.........................................................................................................................................................................................................˝.......................................... 

3501 

SAES62 

The AESCB control block is dumped after a VTAM SEND request was 

issued on a secondary LU6.2 session. 

.........................................................................................................................................................................................................˝.......................................... 

3502 

SAES62 

The AESCB control block is dumped after a VTAM RECEIVE request was 

issued on a secondary LU6.2 session. 

.........................................................................................................................................................................................................˝.......................................... 

3503 

SAES62 

The AESCB control block is dumped after a LU6.2 RECEIVE or WAIT 

request was issued on a secondary LU6.2 session.


.........................................................................................................................................................................................................˝.......................................... 

3510 

SAESSEND 

This log message shows the output message (in hexadecimal) to the user. 

.........................................................................................................................................................................................................˝.......................................... 

4000 

MAESINIT 

This log message indicates that MAES is active. This log message includes 

the version number of MAES. 

.........................................................................................................................................................................................................˝.......................................... 

4001 

MAES 

MAES attempts to open the MAESPARM DD statement. MAESPARM is 

associated with a partitioned dataset containing execution parameter 

information. If no MAESPARM DD statement exists, all execution 

parameters are either in the EXEC statement or are dynamically entered using 

the operator MODIFY command. 

.........................................................................................................................................................................................................˝.......................................... 

4002 

MAES 

This log message indicates that MAES accepts BIND requests from any 

partner sessions. This log message is issued after the VTAM SET LOGON 

request has completed, but before MAES initializes its ESPIE and ESTAE. 

.........................................................................................................................................................................................................˝.......................................... 

4003 

MAESAALG 

This log message records the building of each ALOG control block. As part 

of the initialization process for MAES, a new control block is built for each 

potential session partner. 

.........................................................................................................................................................................................................˝.......................................... 

4004 

MAESACCT 

MAES opened the MAESACCT dataset successfully which activates normal 

MAES accounting. 



.........................................................................................................................................................................................................˝.......................................... 

4005 


MAESALRU 

This log message records request unit memory allocation and request unit 

size. As part of the initialization process, MAES allocates memory for request 

units. 

.........................................................................................................................................................................................................˝.......................................... 

4006 

MAESAUTO 

As part of startup or by virtue of a MONITOR request to acquire a partner, 

MAES automatically acquires sessions with a session partner. This log 

message is issued immediately after the VTAM REQSESS request. 

.........................................................................................................................................................................................................˝.......................................... 

4007 

MAESBECB 

This log message is issued after storage was allocated for the list of event 

control blocks (ECBs). MAES maintains a list of ECBs. 

.........................................................................................................................................................................................................˝.......................................... 

4008 

MAESBRPL 

During initialization, MAES constructs VTAM control blocks for all 

potential consultations. This log message indicates that the VTAM RPL 

request was built. 

.........................................................................................................................................................................................................˝.......................................... 

4009 

MAESDBUG 

During initialization, MAES attempts to load the MAESDBUG program 

which represents an optimized version of a PLATINUM-supplied knowledge 

base (debug knowledge base) to analyze problems. This log message indicates 

that the module was found and that the debug knowledge base was activated.


.........................................................................................................................................................................................................˝.......................................... 

4011 

MAESLOGM 

MAES can dynamically link to certain external programs (such as the debug 

knowledge base). The external programs can add log messages to the 

MAESLOG dataset under this ID. These log messages can be informational 

or reflect error conditions. For example, execution parameter processing 

errors are recorded in MAESLOG. MAESPARM and PMEMBER 

processing messages are also associated with log message 4011. 

.........................................................................................................................................................................................................˝.......................................... 

4012 

MAESLUNM 

This log message indicates that the MAESLUNM analysis function was 

entered. 

.........................................................................................................................................................................................................˝.......................................... 

4013 

MAESLUNM 

This log message is issued when a parsing error is found in the MAESLUNM 

entry. This log message describes the problem. Correct the error and 

resubmit the MAES JCL. 

.........................................................................................................................................................................................................˝.......................................... 

4014 

MAESLUNM 

This log message shows the record read from the MAESLUNM file before 

any processing is done. 

.........................................................................................................................................................................................................˝.......................................... 

4015 

MAESPARM 

This log message has no text. This log message precedes the remaining log 

messages that are issued when the execute parameters are parsed and 

analyzed. 

.........................................................................................................................................................................................................˝.......................................... 

4016 

MAESPRLD 

This log message indicates that the preload function was invoked. 



.........................................................................................................................................................................................................˝.......................................... 

4017 


MAESPRLD 

This log message shows name of the program that was successfully loaded 

prior to running any consultations. 

.........................................................................................................................................................................................................˝.......................................... 

4018 

MAESPRLD 

This log message indicates that the MAESPRLD DD statement is missing or 

the dataset is empty. 

.........................................................................................................................................................................................................˝.......................................... 

4019 

MAESSECS 

If a service manager session with the session partner was bound, MAES 

initiates a VTAM RECEIVE request to ensure that any messages sent by the 

session partner are processed. 

.........................................................................................................................................................................................................˝.......................................... 

4020 

MAESSERV 

Certain functions within the system must be performed under control of the 

MAES task as a means of enforcing serialization. This log message indicates 

that a system service request was received from a subtask. The nature of the 

request is explained in subsequent log messages. 

.........................................................................................................................................................................................................˝.......................................... 

4021 

MAESSHUT 

During shutdown, this log message is the last to appear in MAESLOG. 

.........................................................................................................................................................................................................˝.......................................... 

4022 

MAESSHUT 

MAES can recover from abends within the MAES task. The MAES end of 

task exit routine handles subtask abends. ESPIE and ESTAE routines handle 

MAES abends. If MAESSHUT gains control due to an abnormal condition, 

it tolerates a certain number of abends before terminating MAES. If that 

limit is not exceeded, MAESSHUT returns control to the mainline of MAES.


Since this error represents an abend within the MAES task, review the 

problem and submit your findings to PLATINUM Technical Support for 

AionDS for resolution, where appropriate. 

.........................................................................................................................................................................................................˝.......................................... 

4023 

MAESWALL 

This log message indicates that the MAES mother task (represented by the 

MAES program) entered a wait state. This is normal and indicates that no 

VTAM activity exists, or the active consultations are running or waiting for 

input. 

.........................................................................................................................................................................................................˝.......................................... 

4024 

MAESWALL 

During MAES processing, the ECB list that MAES uses needs to be rebuilt 

periodically. For example, the ECB list needs to be rebuilt when a new 

session partner is bound and MAES needs to wait on the new session 

partner’s VTAM session. At that point, the executing program (actually a 

VTAM exit routine) posts the main task out of the wait state so it can rebuild 

the ECB list. 

.........................................................................................................................................................................................................˝.......................................... 

4025 

MAESWALL 

This log message is issued when an internal service request is made. MAES 

responds to a number of asynchronous service requests which can be external 

or internal. When a service request must be performed by the mother task, 

an internal service request is initiated. Usually, the MONITOR knowledge 

base initiates an internal service request. For example, a service request to 

acquire a session partner must be done by the mother task, so an internal 

service request is issued. 

.........................................................................................................................................................................................................˝.......................................... 

4026 

MAESRCVE 

This log message indicates that a message was received from the session 

partner without any error condition set. 



.........................................................................................................................................................................................................˝.......................................... 

4027 


MAESRECP 

VTAM has a protocol message that is called a CHASE. MAESWALL is 

designed to respond to a VTAM CHASE. This log message indicates that 

MAESWALL received a CHASE and is ready to respond. 

.........................................................................................................................................................................................................˝.......................................... 

4028 

MAESRECP 

Certain LU6.2 messages carry a VTAM format header (FMH). This log 

message indicates that MAES recognized the FMH presence and deleted it, 

leaving only the application information. 

.........................................................................................................................................................................................................˝.......................................... 

4029 

MAESRECP 

Part of the LU6.2 protocol involves a data message that is used to carry 

switches which control session ownership. This log message indicates that 

the data message was received and is only used to manage internal state 

conditions. 

.........................................................................................................................................................................................................˝.......................................... 

4030 

MAESWALL 

MAES terminates if the Write to Operator with Reply (WTOR) was 

answered properly. This log message indicates that the WTOR was 

answered, but the answer was not verified. 

.........................................................................................................................................................................................................˝.......................................... 

4031 

MAESOPER 

MAES responds to an operator STOP command (STOP jobname). This log 

message indicates that an operator STOP command was recognized. MAES 

terminates.


.........................................................................................................................................................................................................˝.......................................... 

4032 

MAESWALL 

MAES responds to an operator MODIFY command (MODIFY 

jobname,parameters). This log message indicates that an operator MODIFY 

command was recognized. MAES passes the parameter information to 

MAESPARM for processing and continues. 

.........................................................................................................................................................................................................˝.......................................... 

4033 

MAESWALL 

MAES waits on certain events to complete. One event is a consultation being 

suspended. In this case, the VTAM session is released back to the pool and 

MAES is posted, indicating that the subtask is suspended. 

.........................................................................................................................................................................................................˝.......................................... 

4035 

MAESINIT 

This log message is issued when MAES runs as an authorized program. 

Authorized path VTAM is used for all synchronous VTAM requests. 

.........................................................................................................................................................................................................˝.......................................... 

4036 

MAESINIT 

This log message is issued after the ADSPI module is loaded and called. 

.........................................................................................................................................................................................................˝.......................................... 

4037 

MAESPGSI 

This log message contains messages issued by the PLATINUM-supplied 

program security initialization module (MAESPGSI). 

.........................................................................................................................................................................................................˝.......................................... 

4038 

MAESINIT 

This log message displays the return code when the program security 

initialization program has been linked. 

.........................................................................................................................................................................................................˝.......................................... 

4039 

MAESISTT 

Statistics gathering is enabled. 



.........................................................................................................................................................................................................˝.......................................... 

4040 


MAESISTT 

The statistics gathering function is disabled. The DD statement for 

MAESSTAT was not found. 

.........................................................................................................................................................................................................˝.......................................... 

4041 

MAESSWAP 

This log message is issued during startup when the MAES address space is 

swappable. The MAES address space should be non-swappable otherwise 

adequate performance will not be assured. This message also prints out the 

default user ID which is used for RACF and DB2 authorization checking. 

.........................................................................................................................................................................................................˝.......................................... 

4042 

MAESINIT 

The SAESEP interface module loaded successfully. 

.........................................................................................................................................................................................................˝.......................................... 

4043 

MAESINIT 

The MAESHPO dataset was opened successfully. 

.........................................................................................................................................................................................................˝.......................................... 

4044 

MAESINIT 

The MAESHPO DD statement is missing. 

.........................................................................................................................................................................................................˝.......................................... 

4047 

MAESITAR 

The timing analysis function was started. 

.........................................................................................................................................................................................................˝.......................................... 

4048 

MAESITAR 

The timing analysis function was not started. The output dataset (the 

MAESMTARR DD statement) could not be opened.


.........................................................................................................................................................................................................˝.......................................... 

4050 

MAESINIT 

The SESSLOG dataset was opened successfully. The MONITOR knowledge 

base can capture message activity. 

.........................................................................................................................................................................................................˝.......................................... 

4051 

MAESINIT 

The SESSLOG dataset could not be opened. The MONITOR knowledge 

base cannot capture message activity. 

.........................................................................................................................................................................................................˝.......................................... 

4070 

MAESERR 

This log message shows the last message that the consultation sent to the 


.........................................................................................................................................................................................................˝.......................................... 

4089 

MAESOPER 

The MAESXSUB load module could not be brought into memory. The 

MAESLOG dataset cannot be used. 

.........................................................................................................................................................................................................˝.......................................... 

4098 

MAESINIT 

The MAESXSUB load module could not be brought into memory. The 

MAESLOG dataset cannot be used. 

.........................................................................................................................................................................................................˝.......................................... 

4118 

MAESRECP 

MAESRECF was called and returned a non-zero value in register 15. 

.........................................................................................................................................................................................................˝.......................................... 

4129 

MAESRECP 

A VTAM message with a length equal to zero was received and ignored. 



.........................................................................................................................................................................................................˝.......................................... 

4141 


MAESSWAP 

The MAES address space is non-swappable. 

.........................................................................................................................................................................................................˝.......................................... 

4142 

MAESPRLD 

The optimized module is eligible for forced paging. 

.........................................................................................................................................................................................................˝.......................................... 

4409 

SAESTERM 

This log message shows user output data in hexadecimal form. 

.........................................................................................................................................................................................................˝.......................................... 

4410 

SAESTERM 

This log message shows the MST (an internal control block) of the ending 

consultation. 

.........................................................................................................................................................................................................˝.......................................... 

4500 

SAESSTIN 

This log message is issued each time a consultation is initialized. This log 

message contains version, modification, and date information that can be 

used to verify the SAES or SADS level that you are running. 

.........................................................................................................................................................................................................˝.......................................... 

4503 

SAESRUID 

This log message shows the PDBs (Parameter Descriptor Blocks) of the input 

Fixed Parameter List. 

.........................................................................................................................................................................................................˝.......................................... 

4504 

SAESRUID 

This log message records the parameter list specifying where input and output 

data is to be placed. PLATINUM Technical Support for AionDS can use 

this information for debugging.


.........................................................................................................................................................................................................˝.......................................... 

4505 

SAESRUID 

This log message records the input data area for FPL data. 

.........................................................................................................................................................................................................˝.......................................... 

4506 

SAESRUID 

This log message indicates that all of the information contained in the last 

request unit was received from the transaction driver during FPL input 

retrieval. 

.........................................................................................................................................................................................................˝.......................................... 

4507 

SAESRUID 

This log message indicates that the transaction driver is not sending any FPL 

input data. However, there might be FPL output data. 

.........................................................................................................................................................................................................˝.......................................... 

4508 

SAESSTAT 

As part of normal protocol, SAES/SADS sends status messages to the 

transaction driver. This log message indicates that the subroutine is about to 

send the status message. 

.........................................................................................................................................................................................................˝.......................................... 

4509 

SAESTERM 

As part of FPL processing, output data is returned to the transaction driver at 

knowledge base termination. This log message contains the data that is to be 

returned to the session partner. 

.........................................................................................................................................................................................................˝.......................................... 

4510 

SAES62 

As part of the underlying secondary LU6.2 session support for remote 

knowledge bases, this log message is issued to indicate that a VTAM 

RECEIVE request is about to be issued. 



.........................................................................................................................................................................................................˝.......................................... 

4900 


MAESXMCH 

During shutdown, MAESXMCH found that there are still active cross 

memory services sessions. 

.........................................................................................................................................................................................................˝.......................................... 

5000 

MAESLGON 

If a potential session partner attempts to logon to MAES, MAESLGN is 

given control. If appropriate, MAES attempts an OPNDST request. This 

log message indicates that the session partner is valid and the OPNDST 

request is about to be issued. 

.........................................................................................................................................................................................................˝.......................................... 

5002 

MAESSECS 

MAESSECS is a subroutine of the VTAM SCIP exit coded into MAES. 

When MAESSECS receives a BIND request, the requestor’s LU name is 

matched against the LU names specified in the MAESLUNM file. This log 

message indicates that the session is from an IMS-type partner (no parallel 

session support) and that MAES is about to send an OPNSEC request to the 

requestor. 

.........................................................................................................................................................................................................˝.......................................... 

5003 

MAESSECS 

MAESSECS is a VTAM SCIP exit subroutine which handles BIND requests. 

In this case, a BIND request was received from a session partner that is 

defined as supporting parallel sessions (APPC). Also, the mode name is 

SNASVCMG. These two conditions indicate that the requestor is 

attempting to bind its service manager session with MAES. 

MAES is about to issue the VTAM OPNSEC request to complete the bind.


.........................................................................................................................................................................................................˝.......................................... 

5004 

MAESSERV 

MAES received a request to deactivate a session partner. That means 

breaking any sessions bound with that session partner and marking it as 

unavailable to accept BIND requests. The request was either from the 

MONITOR knowledge base or a result of normal shutdown. 

.........................................................................................................................................................................................................˝.......................................... 

5005 

MAESSERV 

As part of session partner deactivation, MAES (where the session partner 

supports parallel sessions) unbinds (using a CLSDST call) the MAES-owned, 

service manager session. This log message records this event. 

.........................................................................................................................................................................................................˝.......................................... 

5006 

MAESSERV 

MAES received a request from the MONITOR knowledge base to activate 

an inactive session partner. Unless a session partner is active, BIND requests 

are rejected. 

.........................................................................................................................................................................................................˝.......................................... 

5007 

MAESSERV 

MAES received a request from the MONITOR to acquire sessions with the 

session partner. This is applicable only to session partners that support 

acquisition by MAES. This results in binding VTAM sessions with the 

session partner. 

.........................................................................................................................................................................................................˝.......................................... 

5008 

MAESSERV 

As part of remote knowledge base processing, mainframe-to-mainframe, 

traffic sessions to the session partner are allocated from the pool of sessions 

owned by this MAES. This log message records that a request for a session 

was received. 



.........................................................................................................................................................................................................˝.......................................... 

5009 


MAESSMGR 

As part of the LU6.2 protocol in which parallel sessions are involved, each 

side of the connection owns a service manager session. This log message 

indicates that MAES is about to issue an OPNDST to establish a service 

manager session with XXXXXXX. 

.........................................................................................................................................................................................................˝.......................................... 

5010 

MAESSTAB 

Sessions are bound with a session partner that was previously bound with 

MAES. This log message indicates that an internal control block is freed 

prior to allocating a new one. 

.........................................................................................................................................................................................................˝.......................................... 

5011 

MAESSTAB 

Sessions are bound with a session partner in a parallel sessions connection. 

This log message indicates that internal control blocks are allocated to 

support the traffic sessions. 

.........................................................................................................................................................................................................˝.......................................... 

5012 

MAESSUBS 

As part of the process to establish traffic sessions with a session partner in a 

parallel sessions connection, MAES initiates BIND requests to the traffic 

sessions MAES will own. This log message indicates that an attempt to bind 

a traffic session using an OPNDST call was made. 

.........................................................................................................................................................................................................˝.......................................... 

5013 

MAESSUBS 

This log message is issued after MAES completed acquiring all the traffic 

sessions it should own for a particular session partner.


.........................................................................................................................................................................................................˝.......................................... 

5014 

MAESSERV 

The datasets associated with the MAESHPO DD statement can be closed 

and reopened using the MONITOR knowledge base. This log message is 

issued if the action is successful. 

.........................................................................................................................................................................................................˝.......................................... 

5015 

MAESSERV 

The MONITOR knowledge base can be used to suspend scheduling of an 

optimized knowledge base. This log message indicates which knowledge base 

is being quiesced. 

.........................................................................................................................................................................................................˝.......................................... 

5016 

MAESQPGM 

An internal queue of optimized knowledge bases, which are preloaded, 

quiesced, or newcopied, is built. After MAES initialization, this log message 

is issued when a MONITOR knowledge base action causes a new program 

queue control block to be built. 

.........................................................................................................................................................................................................˝.......................................... 

5017 

MAESSERV 

This log message indicates that a previously quiesced, optimized knowledge 

base is being activated and made available for scheduling. 

.........................................................................................................................................................................................................˝.......................................... 

5018 

MAESSQ 

This log message is issued when a user of the MONITOR knowledge base 

requested that an optimized knowledge base be refreshed (commonly called 

NEWCOPY). The storage shown in this log message is the name of the 

optimized knowledge base being reloaded. 



.........................................................................................................................................................................................................˝.......................................... 

5019 


MAESSERV 

The MONITOR knowledge base can be used to change the dispatching 

priority of an optimized knowledge base’s future schedulings. This log 

message indicates the name of the optimized knowledge base and its new 

priority. 

.........................................................................................................................................................................................................˝.......................................... 

5023 

MAESSERV 

The MONITOR knowledge base is preloading a program. 

.........................................................................................................................................................................................................˝.......................................... 

5106 

MAESSERV 

This log message is issued when the MONITOR knowledge base is 

activating a session partner. 

.........................................................................................................................................................................................................˝.......................................... 

5111 

MAESSTAB 

As a result of a change number of sessions (CNOS), a new subsession table 

has been allocated. 

.........................................................................................................................................................................................................˝.......................................... 

6000 

MAESMALL 

This log message indicates that the cross memory services environment was 

created under MAES. 

.........................................................................................................................................................................................................˝.......................................... 

6001 

XAESNCON 

A cross memory bind was received from and accepted by a transaction driver 

and accepted. 

.........................................................................................................................................................................................................˝.......................................... 

6002 

XAESNCON 

MAES received a cross memory message. The cross memory message is a 

control message rather than a traffic message for the consultation.


.........................................................................................................................................................................................................˝.......................................... 

6003 

SAESXMSE 

A cross memory message is about to be transferred to the transaction driver. 

.........................................................................................................................................................................................................˝.......................................... 

6004 

XAESCLEN 

A cross memory session is being terminated. 

.........................................................................................................................................................................................................˝.......................................... 

6005 

SAESXMGE 

A cross memory message is about to be retrieved from the transaction driver. 

.........................................................................................................................................................................................................˝.......................................... 

6007 

XAESNCON 

This log message indicates that a protocol message was sent after a cross 

memory bind. 

.........................................................................................................................................................................................................˝.......................................... 

6008 

XAESERN 

A cross memory status message is about to be sent to the transaction driver. 

.........................................................................................................................................................................................................˝.......................................... 

6009 

XAESNCON 

A cross memory event completed successfully. 

.........................................................................................................................................................................................................˝.......................................... 

6010 

SAESXMSE 

A cross memory send completed successfully. 

.........................................................................................................................................................................................................˝.......................................... 

6011 

MAESMALL 

To assist in debugging, this log message traces the PLATINUM-written 

SVC. 



.........................................................................................................................................................................................................˝.......................................... 

6016 


XAESNCON 

This log message shows the transaction driver version. 

.........................................................................................................................................................................................................˝.......................................... 

6017 

XAESNCON 

The transaction driver version does not match the MAES version. The 

consultation request is rejected. 

.........................................................................................................................................................................................................˝.......................................... 

7010 

SAESAPI 

This log message shows the contents of the buffer that the asynchronous API 

uses when a message is sent to the client. 

.........................................................................................................................................................................................................˝.......................................... 

7020 

SAESAPI 

This log message indicates that the asynchronous API requests a message 

from the API client. 

.........................................................................................................................................................................................................˝.......................................... 

7030 

SAESAPI 

This log message contains the return code from an API request. 

.........................................................................................................................................................................................................˝.......................................... 

7040 

SAESAPI 

This log message contains the asynchronous API message received from the 

client.


.........................................................................................................................................................................................................˝.......................................... 

11000 

MAESBFPL 

When a consultation is initialized, storage is allocated to hold the parameter 

list this is passed to the subtask. This includes any FPL information and the 

command line. If the MAES region is too small, there might not be enough 

storage available for the parameter list. This log message records the problem 

before returning an error code to the caller. The consultation request is 

rejected. 

Increase the MAES region size when not enough storage is available for the 

parameter list. 

.........................................................................................................................................................................................................˝.......................................... 

11001 

MAESETXR 

When a consultation terminates, the address of the terminating task control 

block (TCB) is used as an argument into a chain of internal control blocks. 

If none of the control blocks has a matching TCB address, this log message is 

issued. 

If this occurs, MAES has an internal error. This error should be reported to 

PLATINUM Technical Support for AionDS. Although the subtask 

terminates normally, the terminal that was running the consultation will 

probably hang. MAESETXR needs to locate the control block in order to 

properly terminate the connection with the corresponding transaction driver. 

Moreover, the subtask that dynamically allocated the datasets did not 

properly free the datasets. The datasets remain allocated. 

.........................................................................................................................................................................................................˝.......................................... 

11002 

MAESETXR 

The MAES end-of-task exit routine detects consultation abends. System and 

user abends are formatted into a message indicating the nature of the abend. 

For user abends, the decimal abend code typically matches a message number 

in the consultation’s AionDS system log. Typically, user abends result from 

consultation errors. You will probably need an AionDS system log to resolve 

user abends. 




For system abends, you need to convert the decimal abend code into a 

hexadecimal number to analyze the problem. For instance, a protection 

exception appears as system abend 0196 in this log message, but is normally 

traced as system abend OC4 (in hexadecimal). To resolve system abends you 

need to allocate a SYSUDUMP DD statement to the MAES job. 

.........................................................................................................................................................................................................˝.......................................... 

11003 

MAESNCON 

This log message indicates that an existing consultation was terminated in 

order to start a new consultation. MAES uses a combination of the session 

partner’s LU name (for parallel session connections) and the user’s terminal 

name to identify a consultation. Under certain abnormal situations, even 

though an existing consultation was suspended, the transaction driver 

attempts to initialize a new consultation with the same identifier (LU name 

and terminal name). MAES automatically terminates the old consultation 

before initializing the new consultation. 

.........................................................................................................................................................................................................˝.......................................... 

11004 

MAESNCON 

This log message is issued when the maximum number of consultations that 

can run concurrently is exceeded. The MAXTASKS execution parameter sets 

the maximum number of consultations that can run concurrently. 

In the MAXTASKS execution parameter, increase the maximum number of 

consultations that can run concurrently. You might also need to increase the 

amount of memory available to MAES. 

.........................................................................................................................................................................................................˝.......................................... 

11005 

MAESNCON 

This log message is issued when MAES receives a consultation resume request 

and the consultation is not active. This log message includes the consultation 

identifier (typically the terminal ID). This condition can occur if the 

consultation timed out or was otherwise terminated while the end user was 

answering a prompt. MAESNCON manages resuming current consultations 

or starting new consultations.


.........................................................................................................................................................................................................˝.......................................... 

11006 

MAESSHUT 

As part of shutdown processing, MAES abnormally terminates any 

consultations that are in process. This log message identifies each 

consultation that terminated. Each consultation is identified by its 

consultation ID. 

.........................................................................................................................................................................................................˝.......................................... 

11007 

MAESRECP 

MAES was posted from its WAIT state. MAESWALL receives a message 

associated with a specific consultation, but MAESWALL cannot locate the 

consultation’s internal control block. This error should be reported to 


.........................................................................................................................................................................................................˝.......................................... 

11008 

MAESRECP 

This log message indicates that the consultation associated with the session 

receiving the bracket initiate stop (BIS) was posted to terminate. The VTAM 

protocol BIS message indicates that the receiver is to shutdown any activities 

on that session. 

.........................................................................................................................................................................................................˝.......................................... 

11009 

MAESSETX 

This log message shows the abend code for the statistics routine that has 

abended. 

.........................................................................................................................................................................................................˝.......................................... 

11010 

MAESITAR 

This log message contains abend information for the error that occurred 

while writing to the timing analysis dataset. Timing analysis ends. 



.........................................................................................................................................................................................................˝.......................................... 

11500 


SAESGET 

This log message is issued when the consultation was in a WAIT state longer 

than the limit specified in the TIME= execution parameter. The consultation 

abnormally terminates. 

.........................................................................................................................................................................................................˝.......................................... 

11501 

SAESSEND 

MAES posted the subtask with a code indicating that the consultation should 

be shut down. Two conditions can cause this to occur: 

■ A consultation cancellation request was received from the MONITOR 


■ A new consultation is being started with the same ID as the current one. 

.........................................................................................................................................................................................................˝.......................................... 

11502 

SAESSEND 

MAES can post SAESSEND when normal shutdown is in progress. This log 

message indicates that a consultation was in progress when normal shutdown 

began. Other log messages that indicate the cause of the shutdown are 

issued. 

.........................................................................................................................................................................................................˝.......................................... 

11503 

SAESSEND 

This log message indicates that MAES posted the subtask, but the subtask 

could not recognize the code it was given. MAES can post SAESSEND for 

consultation cancellation and system shutdown. 

.........................................................................................................................................................................................................˝.......................................... 

11504 

SAESSTIN 

This log message indicates that the consultation used too much CPU time to 

reply to the user’s last input. The consultation abends with user abend 4000.


.........................................................................................................................................................................................................˝.......................................... 

11505 

SAESSTOP 

This log message indicates a logical error in the consultation that can be 

resolved using other messages in MAESLOG. While processing a 

consultation, the low-level VTAM routines within SAES or SADS either 

timed out or has received a stop consultation message from the transaction 

driver. After this log message is written, SAES abends. 

.........................................................................................................................................................................................................˝.......................................... 

12000 

MAES 

MAES attempts to establish a connection to VTAM by opening an Access 

Method Control Block (ACB) using the nodename provided in the 

NODENAME execute parameter. If the OPEN request fails, MAES formats 

the VTAM error code. The error code can be located in the IBM VTAM 

Programming manual. If the debug knowledge base is available, more 

detailed information about the error and a suggested resolution to the 

problem is written to the MAESLOG. 

.........................................................................................................................................................................................................˝.......................................... 

12001 

MAES 

After opening its VTAM ACB, MAES enables itself to accept BIND requests. 

If the VTAM request (SETLOGON) fails, MAES logs the error code and 

terminate. If the debug knowledge base is available, more detailed 

information is written to the MAESLOG. 

.........................................................................................................................................................................................................˝.......................................... 

12002 

MAESAUTO 

MAES had an error issuing the VTAM REQSESS request when MAES 

attempted to automatically bind with a potential session partner. 

MAESSYNA logs more information. 



.........................................................................................................................................................................................................˝.......................................... 

12003 


MAESBRPL 

When setting up potential consultation subtasks, MAES uses VTAM services 

to generate control blocks. This log message occurs when the NIBGEN fails. 

The error code is included in the log message, and can be used in conjunction 

with the IBM VTAM Programming manual to help resolve the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12004 

MAESBRPL 

When setting up potential consultation subtasks, MAES generates control 

blocks using VTAM services. This log message occurs when the RPLGEN 

fails. The error code is included in this log message and can be used in 

conjunction with the IBM VTAM Programming manual to help resolve the 

problem. 

.........................................................................................................................................................................................................˝.......................................... 

12005 

MAESCICS 

The MAESCICS routine asynchronously processes traffic from a parallelsessions-connected 

partner’s service manager session. An error condition was 

detected after the VTAM RECEIVE and the VTAM CHECK request were 

completed. This situation can occur when the session partner abnormally 

terminates or is cancelled without cleaning up properly. If this is not the 

case, report the problem to PLATINUM Technical Support for AionDS 

along with the MAESLOG. A log message from MAESSYNA further 

analyzes the error. 

.........................................................................................................................................................................................................˝.......................................... 

12006 

MAESCICS 

MAES attempts to respond to an exchange log names request from a session 

partner in a parallel sessions connection. However, VTAM detected an error. 

This message is accompanied by a log message from MAESSYNA which 

further analyzes the problem.


.........................................................................................................................................................................................................˝.......................................... 

12007 

MAESCNOS 

MAES either initiates or responds to a session partner’s change number of 

sessions request. 

VTAM detects an error on the request. A log message from MAESSYNA, 

which precedes this log message, further analyzes the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12008 

MAESERR 

MAES attempts to send a status message to the transaction driver. VTAM 

detects an error. A log message from MAESSYNA, which precedes this log 

message, further analyzes the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12009 

MAESLGON 

MAESLGON issues an OPNDST call in response to a CINIT from a 

potential session partner. VTAM detects an error condition. A log message 

from MAESSYNA, which precedes this log message, further analyzes the 

problem. 

.........................................................................................................................................................................................................˝.......................................... 

12010 

MAESLUS 

MAES attempts to send a VTAM LUSTAT message to a session partner. 

VTAM detects an error condition. A log message from MAESSYNA, which 

precedes this log message, further analyzes the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12011 

MAESNSEX 

When the VTAM network services exit gets control, a header code is used to 

determine the service that is required. This message formats the header code 

for debugging purposes. 



.........................................................................................................................................................................................................˝.......................................... 

12013 


MAESRCVE 

MAESRCVE issued a VTAM RECEIVE request against a session and the 

request failed. A log message from MAESSYNA, which precedes this log 

message, further analyzes the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12014 

MAESRCV1 

MAES issued a VTAM RECEIVE request against its service manager session. 

VTAM detected an error condition. A log message from MAESSYNA, which 

precedes this log message, further analyzes the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12015 

MAESSCIP 

The VTAM SCIP exit handles a set of conditions such as BIND and 

UNBIND. This log message indicates that the MAESSCIP program could 

not determine what action was requested. Report this situation to 

PLATINUM Technical Support for AionDS. Include a copy of the 

MAESLOG in your report. 

.........................................................................................................................................................................................................˝.......................................... 

12016 

MAESSECS 

MAES issues an OPNSEC request in response to a session partner’s 

OPNDST request. If the VTAM request fails, this message is issued as an 

analysis by MAESSYNA. The error should be reported to PLATINUM 


.........................................................................................................................................................................................................˝.......................................... 

12017 

MAESSECS 

After MAES receives a BIND request, it verifies the following: 

■ The LU name is in the MAESLUNM dataset. 

■ The potential session partner supports multiple request unit output.


■ The node is active (has not been deactivated using the MONITOR 

knowledge base). 

■ The log mode name is present in the BIND parameters. 

If any of these conditions is not valid, MAES issues a SESSIONC request to 

rejects the BIND request. 

.........................................................................................................................................................................................................˝.......................................... 

12018 

MAESSMGE 

A VTAM RECEIVE request issued against the MAES service manager 

session that is bound with a session partner, was posted with an error code. A 

log message from MAESSYNA, which precedes this log message, has more 

information about the error condition. 

.........................................................................................................................................................................................................˝.......................................... 

12019 

MAESSMGR 

MAES attempts to bind a service manager session with a session partner 

(XXXXXXXXX). The OPNDST request fails. Preceding log messages from 

MAESSYNA provides a further analysis of the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12020 

MAESSUBS 

MAES attempts to acquire a traffic session. The OPNDST request fails. 

Preceding log messages from MAESSYNA further analyze the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12021 

MAESSYNA 

MAESSYNA manages cancellation of outstanding VTAM requests. If MAES 

is waiting to receive a message from its session partner, and the session 

partner is cancelled or terminates without replying, VTAM automatically 

posts the outstanding RECEIVE request with an error condition. This log 

message notes that a RECEIVE request was cancelled. This is typical for 

sessions with a single session connection, but is not typical for sessions with a 

parallel session connection. 



.........................................................................................................................................................................................................˝.......................................... 

12022 


MAESSYNA 

All VTAM request errors, other than OPEN and CLOSE requests, force the 

SYNAD exit to be executed. MAES logs the return code and feedback 

information in the VTAM RPL with this message. If the debug knowledge 

base is active, more detailed information is written to MAESLOG which can 

help in analyzing the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12023 

MAESSYNA 

Certain VTAM errors can be retried. If the MAES VTAM SYNAD exit 

determines that a retry is appropriate, a VTAM EXECRPL is executed. This 

message indicates that the request was rejected. The RPL is logged so that 

PLATINUM Technical Support for AionDS can debug the problem. 

.........................................................................................................................................................................................................˝.......................................... 

12024 

MAESRECP 

MAES received a reached recovery node (RRN) VTAM protocol message 

from the session partner. MAES calls MAESRRN to respond appropriately. 

.........................................................................................................................................................................................................˝.......................................... 

12025 

MAESXLN 

By returning its own XLN message, MAES responds to an exchange log 

names (XLN) request from a session partner. If the VTAM request fails, 

MAESSYNA issues an error message. The code that issued the SEND 

request issues this log message. 

.........................................................................................................................................................................................................˝.......................................... 

12026 

MAESSECS 

MAES received a BIND request, but the name of the logical unit attempting 

the BIND was not found in the MAESLUNM dataset. Determine if the 

attempt to bind was valid. If the BIND request was valid, correct the 

MAESLUNM dataset before resubmitting the request to MAES. You can 

also add a new potential partner session using the MONITOR knowledge 

base if you are unable to terminate MAES to make the correction.


.........................................................................................................................................................................................................˝.......................................... 

12118 

MAESSECS 

The session control blocks are dumped after a BIND fails. A log message 

header (with the same log message number) separates each session control 

block dump. 

.........................................................................................................................................................................................................˝.......................................... 

12140 

MAESERR 

A format header type 7 (FMH7) was sent to the transaction driver. 

.........................................................................................................................................................................................................˝.......................................... 

12145 

MAESERR 

A status message was sent to the transaction driver. This log message contains 

the status message in hexadecimal form. 

.........................................................................................................................................................................................................˝.......................................... 

12240 

MAESRCV1 

A VTAM RECEIVE call was made to a service manager session. 

.........................................................................................................................................................................................................˝.......................................... 

12250 

MAESRESP 

A VTAM response was sent to the transaction driver. 

.........................................................................................................................................................................................................˝.......................................... 

12500 

SAESGET 

This log message is issued when a VTAM protocol message SEND fails. For 

instance, SAESGET detects a VTAM SHUTD request and attempts to 

respond. If the response fails, log message 12500 is issued. 



.........................................................................................................................................................................................................˝.......................................... 

12501 


SAESRUID 

This log message is issued when the low-level VTAM routines detect an error. 

Analyze the error situation using the log message that SAESGET writes to the 

MAESLOG prior to this log message. If a true VTAM error occurred (not a 

logical error managing the message), MAESSYNA writes a log message to the 

MAESLOG. 

.........................................................................................................................................................................................................˝.......................................... 

12502 

SAESRUID 

When the low-level VTAM receive routine is called, the expected size of the 

user input data is passed. This log message indicates that the request unit size 

received by SAESGET was greater than the size that SAESRUID expected. 

This is a programming error in either ADSFPL, AAESFPL or DCFPL. The 

amount of data actually sent must be the same amount that SAESRUID 

expects. 

.........................................................................................................................................................................................................˝.......................................... 

12620 

SAESSEND 

The calling function attempted to receive a message. However, the session 

was in SEND mode, so the request was rejected with an error. 

.........................................................................................................................................................................................................˝.......................................... 

13000 

MAESNCON 

When MAES is unable to resume a consultation because the consultation ID 

cannot be found, AionDS control blocks are printed. PLATINUM Technical 

Support for AionDS can use these AionDS control blocks to debug the 

problem. 

.........................................................................................................................................................................................................˝.......................................... 

13001 

MAESNCON 

When MAES terminates an existing consultation because a second 

consultation start request was received, AionDS control blocks are printed. 

PLATINUM Technical Support for AionDS can use these AionDS control 

blocks to further analyze the problem.


.........................................................................................................................................................................................................˝.......................................... 

13002 

MAESSCIP 

If MAES cannot locate the conversation ID (CID) in its internal control 

blocks (log message 15001), MAES logs the control blocks that can be used 

to analyze the problem. 

.........................................................................................................................................................................................................˝.......................................... 

14001 

MAES 

As part of MAES initialization, an MVS ESTAE function is executed to trap 

abends in the MAES task. If the ESTAE fails, this log message is issued and 

MAES terminates. Contact PLATINUM Technical Support for AionDS and 

have both the MAESLOG and the MVS job log for MVS available. 

.........................................................................................................................................................................................................˝.......................................... 

14002 

MAESDBUG 

When starting the debug knowledge base, MAES issues an MVS IDENTIFY 

to make entry points within the load module known to the operating system. 

If the IDENTIFY fails, certain operations of the MONITOR knowledge base 

will not work. Report this problem to PLATINUM Technical Support for 

AionDS and have the MAESLOG and the MVS job log available. 

.........................................................................................................................................................................................................˝.......................................... 

14003 

MAESDBUG 

If the execution parameters indicate that the debug knowledge base is to be 

loaded, MAES attempts to bring in the debug knowledge base using the 

MVS LOAD function. If the load fails, MAES continues. Examine the 

MVS job log to determine the specific error. Usually, the problem is that 

neither the JOBLIB nor STEPLIB concatenations contain the MAESDBUG 

load module. Correct the problem before running MAES again. 



.........................................................................................................................................................................................................˝.......................................... 

14006 


MAESETXR 

When a consultation terminates, MAESETXR attempts to deallocate any 

datasets that might have been allocated by the subtask, but not deallocated by 

the inference engine. These datasets have a consultation-unique identifier 

(Annn) prefixed to the DD name. If the deallocation fails, this error message 

is issued with the DD name that MAESETXR failed to process. 

If a deallocation failure occurs, it can interfere with subsequent consultations 

because the consultation-unique identifier is reusable. The reason for the 

deallocation failure is found in the operating system job log for MAES. The 

deallocation failure is listed as a standard MVS error message. Examine the 

MVS error message and correct the error condition before trying to run 

MAES again. 

.........................................................................................................................................................................................................˝.......................................... 

14007 

MAESLUNM 

This log message indicates that the DD statement for MAESLUNM was 

missing from the JCL stream. MAES requires all potential session partners to 

be identified before any sessions are established. The dataset associated with 

the MAESLUNM DD statement is scanned to identify potential session 

partners. Correct the error and resubmit the MAES JCL. 

.........................................................................................................................................................................................................˝.......................................... 

14008 

MAESLUNM 

MAESLUNM found the ACQUIRE keyword, but the argument is neither 

YES nor NO. The correct form is ACQUIRE(YES) or ACQUIRE(NO). 

Correct the MAESLUNM dataset and resubmit the MAES JCL. 

.........................................................................................................................................................................................................˝.......................................... 

14009 

MAESLUNM 

MAESLUNM found the TYPE keyword, but the argument is not a valid 

selection such as CICS or IMS. Review the MAESLUNM dataset in 

conjunction with this guidebook and correct any errors before resubmitting 

the MAES JCL.


.........................................................................................................................................................................................................˝.......................................... 

14010 

MAESLUNM 

Either the WIN or the MAX keyword was specified, but the TYPE keyword 

indicates the potential session partner is not an LU6.2 interface with parallel 

session support. For instance, WIN or MAX is invalid if TYPE(IMS) was 

specified. Correct the MAESLUNM dataset and resubmit the MAES JCL. 

.........................................................................................................................................................................................................˝.......................................... 

14011 

MAESLUNM 

A potential session partner is being defined, but MAX was not specified for 

the WIN keyword. MAES needs to know the maximum number of traffic 

sessions that are supported so that it can maintain the appropriate number of 

internal control blocks. Correct the MAESLUNM dataset and resubmit the 

MAES JCL. 

.........................................................................................................................................................................................................˝.......................................... 

14012 

MAESLUNM 

In processing an MAESLUNM specification for a session partner where 

MAES owns some of the traffic sessions, it was determined that the value 

from WIN exceeded the maximum number of traffic sessions as specified by 

MAX. Correct the problem and resubmit the MAES JCL. 

.........................................................................................................................................................................................................˝.......................................... 

14013 

MAESLUNM 

MAES processed the MAESLUNMdataset. The MAESLUNM dataset was 

either empty or all the entries had an associated error. In either case, correct 

the problems and resubmit the MAES JCL. 

.........................................................................................................................................................................................................˝.......................................... 

14014 

MAESPARM 

When execute parameter information is received, MAESPARM dynamically 

links to the MAESPC module which is used to parse the information. 

However, an error occurred while attempting to LINK to MAESPC. This 

log message is recorded and MAES terminates. Examine the MVS job log for 

the MAES job with the error messages which can be used to solve the 

problem. Usually, the problem is that the module is not in the STEPLIB or 




JOBLIB concatenations; however, other problems might be noted in the job 

log. 

.........................................................................................................................................................................................................˝.......................................... 

14015 

MAESPARM 

MAESPARM recognizes the SEC= execute parameter and attempts to load 

the indicated security program. The LOAD fails and MAES terminates. Use 

the MVS job log for the MAES job to solve the problem. In the MVS job 

log, find the MVS error messages which can be used to determine the 

problem with the security program load. 

.........................................................................................................................................................................................................˝.......................................... 

14016 

MAESPRLD 

MAES attempts to preload a program specified in the MAESPRLD dataset. 

However, the program could not be loaded. The MVS code (such as 806) is 

included in this log message. The MVS code is consistent with the MVS 

abend codes in the MVS messages and codes documentation. 

.........................................................................................................................................................................................................˝.......................................... 

14017 

MAESPRLD 

An error occurred in the MAESPRLD data stream. A program name is 

improperly delimited and is greater than 8 bytes. The first 8 bytes of the 

program are included in this log message. Correct the MAESPRLD data 

stream and resubmit the MAES JCL. 

.........................................................................................................................................................................................................˝.......................................... 

14018 

MAESSERV 

A service request was made, but the internal function code was not 

recognized. This error represents either mismatched levels between MAES 

and the MONITOR knowledge base, or a programming error. Verify that 

MAES and MONITOR are at the correct levels. If they are at the correct 

levels, report the error to PLATINUM Technical Support for AionDS and 

submit a copy of the MAESLOG.


.........................................................................................................................................................................................................˝.......................................... 

14019 

MAESSHUT 

If MAES intercepts an abend or program interrupt, it logs the error 

condition. If the debug knowledge base is available, more information is 

included in this log message. 

.........................................................................................................................................................................................................˝.......................................... 

14022 

MAESRECP 

MAES supports a fixed number of concurrent consultations (as specified in 

the MAXTASKS= execution parameter). This log message is issued if a start 

consultation request is received when the maximum number of consultations 

is already active. 

.........................................................................................................................................................................................................˝.......................................... 

14023 

MAESINIT 

MAES attempts to initialize the API, but the ADSAPI module could not be 

executed. Although MAES continues processing, any programs attempting 

to use API fail. Correct the problem by insuring that the library containing 

ADSAPI is included in the STEPLIB or JOBLIB concatenation. 

.........................................................................................................................................................................................................˝.......................................... 

14024 

MAESINIT 

The first program, INITPRGM, of the PGMSEC execution parameter could 

not be executed. Make sure the program is executable and is included in a 

STEPLIB or JOBLIB library. 

.........................................................................................................................................................................................................˝.......................................... 

14025 

MAESINIT 

The second program, CHECKPRGM, of the PGMSEC execution parameter 

could not be executed. Make sure the program is executable and is included 

in a STEPLIB or JOBLIB library. 



.........................................................................................................................................................................................................˝.......................................... 

14026 


MAESINIT 

The SAESEP version does not match the MAES version. Processing 

continues. 

.........................................................................................................................................................................................................˝.......................................... 

14500 

SAESLOGM 

Certain external programs that the inference engine calls as functions (remote 

KB, message switching, etc.) add log messages to the MAESLOG. All these 

log messages appear under this log message ID. Typically, they reflect errors 

in processing. The knowledge base receives a return code from the process 

object. The return code and log message in the MAESLOG can help you 

solve the problem. 

.........................................................................................................................................................................................................˝.......................................... 

14504 

SAESSTIN 

The checking program, CHECKPRGM, returned a non-zero value in register 

15. The user is probably not authorized. The consultation abends with user 

abend 377. 

.........................................................................................................................................................................................................˝.......................................... 

14502 

SAESRUID 

SAES expects FPL data to be provided by a screen input message type with a 

subtype of field-by-field. SAES received a screen input message type, but it 

was not field-by-field data. This log message can be caused by either 

programming errors in ADSFPL, AAESFPL or DCFPL, or inconsistent levels 

between these two programs and MAES. 

.........................................................................................................................................................................................................˝.......................................... 

14503 

SAESRUID 

SAES attempts to allocate enough storage to accommodate the FPL input and 

output data. Not enough memory is available to complete the request. If 

increasing the REGION parameter on the EXEC statement does not 

eliminate the problem, it could be the result of a programming error. In this 

case, report the problem to PLATINUM Technical Support for AionDS and 

submit the MAESLOG showing all the data traffic.


.........................................................................................................................................................................................................˝.......................................... 

15000 

MAESLGON 

A VTAM BIND request was received, but the requestor’s name was not 

found in the internal control blocks formatted from the MAESLUNM file. If 

the requestor is valid, the MAESLUNM dataset must be upgraded to include 

the new session partner. 

.........................................................................................................................................................................................................˝.......................................... 

15001 

MAESSCIP 

This log message is produced when the VTAM SCIP exit gets control on an 

UNBIND request. MAES uses the VTAM conversation ID (CID) as an 

argument into internal control blocks. If the session was cleaned up before, it 

produces this log message. Typically, this is not an error situation. 

.........................................................................................................................................................................................................˝.......................................... 

15002 

MAESSERV 

Using a MONITOR knowledge base function, a user requested that a 

partner session be terminated. This log message indicates that the LU name 

could not be found in internal control blocks. This represents a 

programming error and should be reported to PLATINUM Technical 


.........................................................................................................................................................................................................˝.......................................... 

15003 

MAESSERV 


partner session be activated. This log message indicates that the LU name 






.........................................................................................................................................................................................................˝.......................................... 

15004 


MAESSERV 


partner session be acquired. This log message indicates that the LU name 




.........................................................................................................................................................................................................˝.......................................... 

15005 

MAESSUBS 

As MAES binds traffic sessions with its session partner, the session 

information is stored in an internal control block. This log message is issued 

when more sessions need to be bound, but no more control blocks are 

available. This is an error condition and should be reported to PLATINUM 

Technical Support for AionDS. Also submit the MAESLOG. 

.........................................................................................................................................................................................................˝.......................................... 

15006 

MAESSERV 

Using the MONITOR knowledge base, a user attempted to close and reopen 

the datasets associated with the MAESHPO DD statement. However, the 

DD statement was missing from the MAES start-up JCL and the request was 

rejected. 

.........................................................................................................................................................................................................˝.......................................... 

15007 

MAESSQ 

The user attempted to reload a preloaded program using the MONITOR 

knowledge base and the request failed. The JES log for the MAES job 

contains the error information generated by MVS. 

.........................................................................................................................................................................................................˝.......................................... 

15008 

MAESPRLD 

A statement in the dataset associated with the MAESPRLD DD statement is 

incorrect. MAES found a specification with an opening parenthesis but 

without a closing parenthesis. MAES assumes you have tried to use multiple 

statements for a single preload specification. This is not valid.


.........................................................................................................................................................................................................˝.......................................... 

15009 

MAESPRLD 

While verifying the statements in the dataset associated with the 

MAESPRLD DD statement, a priority specification was found that was not 

numeric. There can be no imbedded blanks, special characters, or sign 

information in a priority specification. 

.........................................................................................................................................................................................................˝.......................................... 

15010 

MAESPRLD 

A priority for a preloaded, optimized knowledge base cannot have a length 

greater than 3 bytes. The appropriate values are from 1 to 16, inclusive. 

.........................................................................................................................................................................................................˝.......................................... 

15011 

MAESPRLD 

The priority assigned to an optimized program was greater than 16. 

.........................................................................................................................................................................................................˝.......................................... 

16000 

MAESAALG 

This log message indicates that an error occurred while establishing a Cross 

Memory Services session. 

.........................................................................................................................................................................................................˝.......................................... 

16001 

XAESNCON 

A cross memory bind was rejected because an earlier VTAM connection had 

been established to the same node name. This can occur for one of the 

following reasons: 

■ MAES and the transacton driver are not at the same version level. 

■ Another consultation is running that has locked the LU name with which 

you are trying to BIND. 

■ There is a problem with the cross memory SVC installation. 



.........................................................................................................................................................................................................˝.......................................... 

16002 


XAESNCON 

After an XMS bind was successful, the transaction driver sent a message to 

MAES that was either invalid or out of sequence. Send the MAESLOG and 

any other supporting documentation to PLATINUM Technical Support for 


.........................................................................................................................................................................................................˝.......................................... 

16003 

MAESSECS 

See log message 16001. This is the reverse of the situation in which an XMS 

session was established and a transaction driver attempts to establish a VTAM 

session. 

.........................................................................................................................................................................................................˝.......................................... 

16004 

SAESXMGE 

MAES posted the consultation with a stop request. This typically happens 

during shutdown or in a situation in which a new consultation is to be 

started from the same terminal. 

.........................................................................................................................................................................................................˝.......................................... 

16005 

SAESXMSE 

An XMS SEND request completed, but the transaction driver indicated that 

there was an error. This should be reported with the MAESLOG to 


.........................................................................................................................................................................................................˝.......................................... 

16006 

XAESNCON 

After an XMS bind is received, MAES attempts to establish an ENQ for the 

transaction driver. The ENQ failed. Send the MAESLOG and other 

supporting material to PLATINUM Technical Support for AionDS. 

.........................................................................................................................................................................................................˝.......................................... 

16007 

SAESXMSE 

An attempt was made to send a message to the transaction driver. However, 

the transaction driver either failed or a protocol error occurred.


.........................................................................................................................................................................................................˝.......................................... 

16008 

XAESNCON 

While trying to complete a sequence of protocol messages, the cross memory 

connection to a transaction driver failed. Typically, this occurs when the 

transaction driver abends. 

.........................................................................................................................................................................................................˝.......................................... 

16105 

SAESXMSE 

A cross memory services SEND failed. 

.........................................................................................................................................................................................................˝.......................................... 

16107 

SAESXMGE 

A cross memory services GET failed. 

.........................................................................................................................................................................................................˝.......................................... 

17000 

SAESAPI 

An initialize API request was received from the transaction driver but the 

request failed. Diagnostic information is printed. 

.........................................................................................................................................................................................................˝.......................................... 

17001 

SAESAPI 

A request to initialize a session with the API was received but the request 

failed. Diagnostic information is printed. 



.........................................................................................................................................................................................................˝.......................................... 

19001 


XAESBRPL 

A node initialization block (NIB) could not be built. MAES terminates. 

.........................................................................................................................................................................................................˝.......................................... 

19002 

XAESBRPL 

A request parameter list (RPL) could not be built. MAES terminates.

Chapter 7 

AionDS Fatal System Errors 

.........................................................................................................................................................................................................˝.......................................... 

Introduction 

If a fatal system error occurs, look up the error number in this chapter to see 

if there is an immediate solution to the problem. If no solution is given for 

the error, or you are unable to correct the problem, contact PLATINUM 


.........................................................................................................................................................................................................˝.......................................... 


Topic Page 

Overview 7-2 

Fatal system errors 7-4 

AionDS Fatal System Errors 7-1

Overview 

Overview 

.........................................................................................................................................................................................................˝.......................................... 

Fatal system errors 


A fatal system error occurs when AionDS detects an internal inconsistency or 

operating condition that requires the development or execution system to be 

shut down. The error is displayed on the user’s terminal, and is also written 

to the AionDS system log. Some common causes of fatal system errors are: 

■ A bug in the AionDS product which, upon detection, jeopardizes the 

integrity of the application being developed or executed. 

■ A bug in the application, such as a knowledge base logic error or an API 

data transfer error, which, upon detection, jeopardizes the integrity of the 

application execution. 

■ An operating system error, which, upon detection, jeopardizes the 

integrity of the application being developed or executed. For example, a 

memory allocation request is made to the operating system, but there is 

not enough memory available to satisfy the request. 

.........................................................................................................................................................................................................˝.......................................... 

Fatal system error 

processing 

Fatal system errors can occur at edit time and runtime. AionDS performs the 

following actions when a fatal system error is detected: 

1 The fatal system error is displayed on the user’s terminal. 

2 The AionDS consultation trace is flushed and closed. 

3 The AionDS system log is flushed and closed. 

4 If a local SQL database connection exists, a ROLLBACK request is 

issued to cancel any uncommitted database changes. 

5 A call is made to the operating system to terminate the development or 

execution system.

Overview 

Only at edit time can the integrity of a knowledge base be jeopardized. To 

ensure against loss of changes and knowledge base corruption, the application 

developer should periodically export the knowledge base during the 

development cycle. 


(Character-Based) for more information about the AUTO-EXPORT profile 

option. 




.........................................................................................................................................................................................................˝.......................................... 

Overview 


This section documents the fatal system errors and, where possible, offers 

suggested responses. Fatal system errors are formatted as follows: 

where 

system: Internal Error error, subcode 

system name of the AionDS system that detected the fatal 

system error 

error fatal system error 

subcode related subcode that can assist the PLATINUM 

Technical Support for AionDS and Development staff 

in diagnosing the problem 

.........................................................................................................................................................................................................˝.......................................... 

Example 

Here is an example of a fatal system error: 

AionDS/OS2: Internal Error 23600,101 

The fatal system errors are listed below in numerical order. 

.........................................................................................................................................................................................................˝.......................................... 

100 to 199 

An internal error was detected in the character string processing package. 

.........................................................................................................................................................................................................˝.......................................... 

1000 to 1099 

An internal error was detected by the display management system. 

.........................................................................................................................................................................................................˝.......................................... 

1300 to 1399 

An internal error was detected while executing a KDL statement. 

.........................................................................................................................................................................................................˝.......................................... 

1600 to 1699 

An inconsistency was detected in the knowledge base.


............................................................................................................................................................................. 

1601 

If the fatal error is 1601, AionDS displays the following message at edit-time: 

Severe Error -- Attempt to Continue? 

Answer YES and immediately export the knowledge base. You should be able 

to import the knowledge base and continue without having lost any of your 

changes. If you cannot continue, do not export the knowledge base again. 

Contact PLATINUM Technical Support for AionDS. 

At runtime, the 1601 error causes AionDS to terminate execution of the 

knowledge base because it is corrupted. In this case, you should restart 

AionDS and attempt to export and import the knowledge base before you 

continue. If you cannot continue, do not export the knowledge base again. 

Contact PLATINUM Technical Support for AionDS. 

............................................................................................................................................................................. 

1605 

If the error number is 1605, you can export the knowledge base and import it 

again. 

............................................................................................................................................................................. 

Other 1600 errors 

If the error number is not 1601 or 1605, you should import the knowledge 

base and resume work from that point. If you do not have a recent export 

file, you can attempt to load the knowledge base without error checking. 

For more information: See your Installation and Operation Guide for 

information about using command line switches to modify startup options. 

During the knowledge base development cycle, you should periodically export 

the knowledge base. 



option. 



.........................................................................................................................................................................................................˝.......................................... 

2100 to 2199 


An internal error was detected by the parameter object handler. 

.........................................................................................................................................................................................................˝.......................................... 

2400 to 2499 

An internal error was detected in a knowledge base object. 

.........................................................................................................................................................................................................˝.......................................... 

2500 to 2599 

An internal error was detected by the memory manager. 

.........................................................................................................................................................................................................˝.......................................... 

2701 

An internal error was detected while parsing an object and adding it to the 

symbol table. 

.........................................................................................................................................................................................................˝.......................................... 

3000 to 3099 

An internal error was detected by the KDL parser. 

.........................................................................................................................................................................................................˝.......................................... 

3100 to 3199 

An internal error was detected by the TDL parser. 

.........................................................................................................................................................................................................˝.......................................... 

3200 to 3299 

An internal error was detected in the numeric constraint processor. 

.........................................................................................................................................................................................................˝.......................................... 

3300 to 3399 

An internal error was detected during the type checking phase of the KDL 

parser. 

.........................................................................................................................................................................................................˝.......................................... 

3400 to 3499 

An internal error was detected in the window system. 

.........................................................................................................................................................................................................˝.......................................... 

3500 to 3699 

A file system error was detected. 

.........................................................................................................................................................................................................˝.......................................... 

3800 to 3899 

An internal error was detected in the Consultation monitor. 

.........................................................................................................................................................................................................˝.......................................... 

4100 

Internal runtime error. 

............................................................................................................................................................................. 

4185 

A status code of 4185 indicates that the runtime stack overflowed. This can 

occur if many nested rules are forward chained.


.........................................................................................................................................................................................................˝.......................................... 

5200 to 5299 

An internal error was detected by the window system. 

.........................................................................................................................................................................................................˝.......................................... 

6600 to 6699 

An internal error was detected in the structure of the state hierarchy. 

.........................................................................................................................................................................................................˝.......................................... 

7000 to 7099 

An error was detected by the type object handler. 

.........................................................................................................................................................................................................˝.......................................... 

7100 to 7199 


.........................................................................................................................................................................................................˝.......................................... 

7302 

An error was detected while reading the internal format of the knowledge 

base. 

The knowledge base is corrupted. You must import the knowledge base and 

resume work from that point. If the knowledge base resides on MVS, 

compress the knowledge base partitioned dataset and make sure that the space 

and directory block allocations are adequate. 

If you do not have a recent export file, you can attempt to load the knowledge 

base without error checking. 

For more information: See your Installation and Operation Guide for 

information about using command line switches to modify startup options. 

During the knowledge base development cycle, you should periodically export 

the KB. 



option. 

.........................................................................................................................................................................................................˝.......................................... 

7700 to 7799 

An internal error occurred in the AionDS virtual memory manager. Try 

increasing the amount of memory available to AionDS if possible. 

.........................................................................................................................................................................................................˝.......................................... 

8200 to 8299 

An internal error was detected in the Main monitor. 



.........................................................................................................................................................................................................˝.......................................... 

8300 to 8399 



.........................................................................................................................................................................................................˝.......................................... 

8600 to 8699 

An internal error was detected in the window system. 

.........................................................................................................................................................................................................˝.......................................... 

10900 to 10999 

An internal error was detected while executing a KDL numeric statement. 

.........................................................................................................................................................................................................˝.......................................... 

11000 to 11099 

An internal error was detected while executing a KDL statement on a record. 

.........................................................................................................................................................................................................˝.......................................... 

11100 to 11199 

An internal error was detected while executing a KDL string statement. 

.........................................................................................................................................................................................................˝.......................................... 

11200 to 11299 

An internal error was detected while executing a KDL list or set processing 

statement. 

.........................................................................................................................................................................................................˝.......................................... 

11500 to 11599 

An internal error was detected while executing a KDL constraint processing 

statement. 

.........................................................................................................................................................................................................˝.......................................... 

12201 

An internal error was detected while copying an object. 

.........................................................................................................................................................................................................˝.......................................... 

13500 to 13599 

An internal error occurred in the command processor. 

.........................................................................................................................................................................................................˝.......................................... 

14100 

An internal error was detected sourcing a TSL property. 

.........................................................................................................................................................................................................˝.......................................... 

14300 to 14399 

An internal error was detected in the AionDS debugger. 

.........................................................................................................................................................................................................˝.......................................... 

17300 to 17399 

An internal error was detected while executing a KDL time or date statement. 

.........................................................................................................................................................................................................˝.......................................... 

20000 

An internal error occurred while deallocating a parameter model.


.........................................................................................................................................................................................................˝.......................................... 

20001 

The knowledge base exceeded the maximum number of parameter models. 

You can usually correct this error by exporting the knowledge base and 

importing it again. 

.........................................................................................................................................................................................................˝.......................................... 

21000 to 21099 

An internal error occurred reading or writing text to or from disk. 

.........................................................................................................................................................................................................˝.......................................... 

21200 to 21299 

An internal error occurred in the object property manager. 

.........................................................................................................................................................................................................˝.......................................... 

22200 to 22099 

An internal error occurred substituting data values into a TSL property. 

.........................................................................................................................................................................................................˝.......................................... 

22300 to 22399 

An internal error occurred processing a TSL command. 

.........................................................................................................................................................................................................˝.......................................... 

22400 to 22499 

An internal error occurred formatting a TSL property. 

.........................................................................................................................................................................................................˝.......................................... 

22500 to 22599 

An internal error occurred formatting a TSL property. 

.........................................................................................................................................................................................................˝.......................................... 

23600 to 23699 

An internal error occurred while processing the system screen definitions. 

This can occur if the AionDS screen table is not properly generated. 

For more information: See Appendix B of the AionDS General Reference 

for the screen file format. 

.........................................................................................................................................................................................................˝.......................................... 

29000 to 29099 

An internal error was detected in the file browser. 

.........................................................................................................................................................................................................˝.......................................... 

32500 to 32599 

An internal error occurred executing a remote VSAM request. 

.........................................................................................................................................................................................................˝.......................................... 

33700 

An internal error was detected while calling a user defined function. 

.........................................................................................................................................................................................................˝.......................................... 

34300 to 34399 

An internal error was detected during the processing of a profile. 



.........................................................................................................................................................................................................˝.......................................... 

42599 


An internal error was detected in the explanation system while processing an 

OTHER SOURCES command. 

.........................................................................................................................................................................................................˝.......................................... 

43100 to 43199 

An internal error occurred during TSL processing. 

.........................................................................................................................................................................................................˝.......................................... 

43201 

An internal error occurred processing a class hierarchy. 

.........................................................................................................................................................................................................˝.......................................... 

46077 

An internal error occurred loading or executing the MAES accounting 

program. Increase the MAES task memory and/or region size and try the 

operation again. 

.........................................................................................................................................................................................................˝.......................................... 

57100 

Internal AionDS error. Inserting a byte into a string failed. 

.........................................................................................................................................................................................................˝.......................................... 

57101 

Internal AionDS error. Internal padding blanks or 0s to the right of a string 

failed. 

.........................................................................................................................................................................................................˝.......................................... 

57102 

Internal AionDS error. This error is caused by one of the following 

conditions: 

■ A string copy or string concatenation failed. 

■ During a knowledge base utility operation, the AION or DPATH 

environment variables are greater than 256 characters. 

.........................................................................................................................................................................................................˝.......................................... 

57103 to 57199 

An internal error was detected in the character string processing package.

Chapter 8 

AionDS System Log 

.........................................................................................................................................................................................................˝.......................................... 

Introduction 

The AionDS system log contains information that relates to timing and 

conditions that occur during a development or execution session, including 

informational messages and error messages. This chapter discusses how to 

examine the system log by describing the format and content of the most 

common log messages. 

For more information: Refer to your Installation and Operation Guide for 

more information about enabling the AionDS system log. 

.........................................................................................................................................................................................................˝.......................................... 


Topic Page 

Examining the system log 8-2 

AionDS System Log 8-1

Examining the system log 


.........................................................................................................................................................................................................˝.......................................... 

Overview 


The AionDS system log is an historical account of what happened during a 

development or execution session. AionDS writes messages to the system log 

in chronological order. The system log may be used in conjunction with the 

consultation trace to determine what happened during a knowledge base 

consultation. It may also be used to assist in debugging knowledge base logic 

errors as well as AionDS fatal system errors. 

Each message in the system log has the following format: 

where 

ADS##### sev message 

##### unique number that identifies the AionDS subsystem from 

which the message was issued 

sev severity of the message (see “Severity level” below) 

message system log message. Generally one of the following 

message types can appear in the system log: 

timestamp The first and last line of the system log is a 

timestamp containing product and version 

information. 

execution These messages reflect the amount of time 

taken to load, execute and clear a 


consultation These messages contain information about 

knowledge base logic errors that occur 

during a consultation.


database These messages contain information about 

accessing QSAM, VSAM, SQL, and DL/I 

data. 

miscellaneous These messages contain information about 

the operating environment, and vary with 

each AionDS-supported platform. 

These message types are discussed in the following sections. 

.........................................................................................................................................................................................................˝.......................................... 

Severity level 

In addition to identifying the type of message, the severity also determines the 

default return code that AionDS gives to the operating system upon 

termination. 

Use the AES(EXITCODE) KDL statement to override the default return 

code. 


for information about the AES statement. 

The relationship between the severity and the return code is as follows: 

Severity code Description Return code 

I informational 0 

W warning 4 

E error 8 

S severe error 12 

U unrecoverable error 16 



Timestamp messages 

.........................................................................................................................................................................................................˝.......................................... 

Overview 


The first and last line of the system log is a timestamp containing product 

and version information. The timestamp message has the following format: 

where 

ADS##### I system version date time cputime 

##### value is 00000 for the beginning timestamp, and 00001 for 

the ending timestamp 

system name of the AionDS system that generated the log, such as 

AIONDS/MVS 

version version of the AionDS system that generated the log, such 

as 7.00 

date date on which the system log started or ended 

time time at which the system log started or ended 

cputime total AionDS execution time (reported in seconds) 

.........................................................................................................................................................................................................˝.......................................... 

Examples 

Here are two examples of timestamp messages: 

ADS00000 I AionDS/MVS 6.50 6-Sep-94 2:37pm 0.213 

ADS00001 I AionDS/MVS 6.50 6-Sep-94 2:38pm 0.900

Execution messages 


.........................................................................................................................................................................................................˝.......................................... 

Overview 

Execution messages reflect the amount of time taken to load, execute and 

clear a knowledge base. Execution messages have the following format: 

where 

ADS##### I operation {symbols | context | kbname} 

(cputime [,objects]) 



operation operation that was performed 

context name of the context (state, class or vocabulary) on which 

the operation was performed 

kbname name of the knowledge base on which the operation was 

performed 

cputime total time taken to perform the operation (reported in 

milliseconds) 

objects number of objects in the context 

.........................................................................................................................................................................................................˝.......................................... 

Example 

The following example shows a sample system log for the execution of a 

knowledge base called SYS630. 

ADS00000 I AionDS/PM 6.30 6-Sep-93 5:53pm 1 

ADS07302 I Loaded symbols (156,68) 

ADS07304 I Loaded SYS630 0.01 (156) 

ADS07303 I Loaded context Main (187,33) 

ADS07303 I Loaded context system (125,35) 

ADS04809 I Executed process sysinfo (281) 

ADS14107 I Executed state Main (2313) 

ADS02434 I Cleared SYS630 0.01 (31,68) 

ADS00001 I AionDS/PM 6.30 6-Sep-93 5:53pm 13 




The times displayed are cumulative. For example, the 2.313 seconds it takes 

to execute state Main, includes the cumulative time, beginning with the 

message “Loaded Context Main.” In addition, the 2.313 seconds includes 

the .281 seconds to execute the SYSINFO process. 

The system log records elapsed time and includes the time for user responses. 

If you want to isolate the time required to execute specific KDL statements, 

use the CPU TIME process object. 

For more information: See Chapter 11 of the AionDS General Reference 

for information about the CPU TIME process object.

Consultation messages 


.........................................................................................................................................................................................................˝.......................................... 

Overview 

Consultation errors that occur during knowledge base execution are written 

to the AionDS system log. Consultation error messages have the following 

format: 

where 

ADS##### E (errnum) errmsg 



errnum consultation error number that was stored in the 

AES_ERRORNUM parameter 

errmsg consultation error message that was stored in the 

AES_ERRORMSG parameter 

For more information: For more information about the 

AES_ERRORNUM and AES_ERRORMSG predefined parameters, see 

Chapter 10 of the AionDS General Reference. 

.........................................................................................................................................................................................................˝.......................................... 

Examples 

Here are two examples of consultation error messages: 

ADS14101 E (1000) Illegal assignment 

ADS14101 E (1204) Missing data elements 



Database messages 

.........................................................................................................................................................................................................˝.......................................... 

Overview 

QSAM and Local VSAM Messages 


When a knowledge base accesses data using the QSAM, VSAM, SQL or 

DL/I access methods, AionDS writes special messages to the system log when 

an error occurs. The format and content of these messages is described 

below. 

.........................................................................................................................................................................................................˝.......................................... 

Overview 

If you use the QSAM or local VSAM access methods on the mainframe, the 

system log contains a special message whenever an I/O error occurs. The 

format of this message is as follows: 

where 

ADS##### sev access,op,ddname,dsname,return-reason info 



sev message severity 

access access method type 

op I/O operation that was being performed 

ddname DD name 

dsname dataset name 

return return code 

reason reason code 

info info code


.........................................................................................................................................................................................................˝.......................................... 

Example 

For example, a VSAM error can cause the following message to appear in the 

system log: 

ADS32599 E VSAM,Open,ADS$0004,VN3871.RR.VSAMDATA,008-118 

0 

You interpret the message as follows: 

Access method: VSAM 

I/O operation: Openfile 

DD name: ADS$0004 

Dataset name: VN3871.RR.VSAMDATA 

Return code: 008 

Reason code: 118 

Info code: 0 



Remote VSAM Messages 

.........................................................................................................................................................................................................˝.......................................... 

Overview 


If you use the remote VSAM access method, the system log contains a special 

message whenever an I/O error occurs. The format of this message is as 

follows: 

where 

ADS##### sev op ddname errtyp,return-reason,info 




op I/O operation that was being performed 

ddname DD name 

errtype error type 

return return code 

reason reason code 

For more information: See Chapter 3 for more 

information about the reason code. 

info info code 

For more information: See “MAES-specific codes” in 

Chapter 5 for more information about the info code.


.........................................................................................................................................................................................................˝.......................................... 

Example 

For example, a remote VSAM error can cause the following message to appear 

in the system log: 

ADS32599 W Unlock TAE100P DSIDERR,12-1114,705 

You interpret the message as follows: 

I/O operation: Unlock 

DD name: TAE100P 

Error Type: DSIDERR 

Return code: 12 

Reason code: 1114 

Info code: 705 



SQL Messages 

.........................................................................................................................................................................................................˝.......................................... 

Overview 


After each SQL call, AionDS writes information to the system log. The log 

entry consists of the statement that AionDS passed to the SQL database and 

an optional error code if an error occurred. The format of the log entry is as 

follows: 

where 

ADS##### sev [(sql_code)] SQL: sql_stmt 




sql_code value of SQLCODE in SQLCA 

sql_stmt SQL statement 

.........................................................................................................................................................................................................˝.......................................... 

Examples 

Here is an example of an SQL error message: 

ADS37303 I SQL: select * from c3871dp.cars 

ADS37303 E SQL: (-128) update flight set cost = 100000 

where 

ADS37303 E cost = 0 

In the second example, the actual SQL statement could be the following: 

sql ('update flight set cost = :n_cost where cost = 

:unk_cost') 

The values of N_COST and UNK_COST are substituted for the parameters 

when AionDS executes the statement.

DL/I Messages 


After each DL/I call, AionDS writes information to the system log. The 

format of the log entry is as follows: 

where 

ADS##### sev 

call_type,segment,dbname,dli_request,rc='pcb_status' 




call_type AionDS-defined call type 

segment segment name 

dbname database name 

dli_request DL/I function code 

pcb_status PCB status code returned by the call 

.........................................................................................................................................................................................................˝.......................................... 

Example 

The following line shows a sample entry in the log: 

ADS35000 I DL/I: Get,SKILLS,EMPDB,GN,rc=' ' 

The request is a GET that operates on the SKILLS segment of the EMPDB 

database. AionDS executed a GN function. The return code of two blanks 

indicates that the call completed successfully. 



Miscellaneous messages 

.........................................................................................................................................................................................................˝.......................................... 

Overview 


AionDS writes miscellaneous messages to the system log containing 

information about the operating environment. The format and content of 

these messages varies across AionDS-supported platforms. 

For example, at the end of a system log on the mainframe, AionDS reports 

the following information: 

I/O Records This is the number of records read or written while loading 

the knowledge base, reading the system tables, writing the 

trace and log files, and so on. It does not include I/O 

performed as part of the consultation. 

Total Storage This is the approximate amount of total storage allocated 

during the development or execution session. 

Peak Storage This is the approximate largest amount of storage that was 

allocated at one point during the development or execution 

session.

AionDS 


DC0431 

 

 

PLATINUM technology Technical Documentation 

PLATINUM technology, Inc. 

555 Twin Dolphin Drive, Suite 400 

Redwood City, CA 94065 

Hotline: 800/833-PLAT 

FAX: 415/594-8645 

Dear Customer: Your comments on PLATINUM technology Technical Documentation are highly valued. If you 

have any problem or suggestion about this manual or the online help, please use this form to communicate with us. 

Alternatively, you may call the PLATINUM technology Hotline to report documentation problems or provide 

comments. 

Describe Problem or Suggestion: _________________________________________________________________ 

____________________________________________________________________________________________ 

____________________________________________________________________________________________ 

Page Number:_______________ Manual Title and ID (if different from above): ____________________________ 

(Optional) Your name: __________________________________ Phone No: ______________________________ 

Company: ___________________________________________________________________________________ 

Please take a moment to complete this Quick Survey. For the following statements, indicate the extent of agreement 

you have with the statement by circling the number that best reflects your opinion. 

“This manual is useful, clear, and covers the appropriate material.” 

Strongly 

Disagree 1 2 3 4 5 

Strongly 

Agree 

“The product's Online Help was concise and easily navigated.” 

Strongly 


Strongly 

Agree 

“The quality of the written documentation is superior to similar products.” 

Strongly 


Strongly 

Agree 

“The overall product documentation meets or exceeds our expectations.” 

Strongly 


Strongly 

Agree

AionDS Messages and Codes Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?