ESQ143 Messages And Codes

Transcription

Adabas SQL ServerMessages and Codes Manual

Manual Order Number: ESQ143-060ALLThis document applies to Adabas SQL Server Version 1.4.3 and to all subsequent releases.Specifications contained herein are subject to change and these changes will be reported in subsequentrelease notes or new editions.Readers’ comments are welcomed. Comments may be addressed to the Documentation Department at theaddress on the back cover or to the following e-mail address:Documentation@softwareag.comE July 1999, Software AGAll rights reservedPrinted in the Federal Republic of GermanySoftware AG and/or all Software AG products are either trademarks or registered trademarks of Software AG.Other products and company names mentioned herein may be the trademarks of their respective owners.

TABLE OF CONTENTSPREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11. ADABAS SQL SERVER MAINFRAME CODES . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Abend Codes — Mainframe Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Console Messages — Mainframe Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5BS 2000 — Multi/Single-Session Driver Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62. ADABAS SQL SERVER ERROR MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11I

II

PREFACEThis manual consists of two chapters: one describing mainframe codes and one describingplatform-independent error messages.The message numbers of system messages issued by Adabas SQL Server begin with the initials“ESQ”. The possible error numbers range from 1000 to 9999.This manual contains the following types of messages:ESQ1000 – ESQ1999Serious system errors, i.e., initialization problemsESQ2000 – ESQ2999Host-language-specific scanner errorsESQ3000 – ESQ3255Original Adabas errors encountered during SQL statementexecution. (See the Adabas Messages and Codes Manual)ESQ4000 – ESQ4999SQL statement compilation errorsESQ6000 – ESQ6999Miscellaneous database access errorsESQ8000 – ESQ8999Runtime system/statement execution errorsESQ9000 – ESQ9255Original Adabas errors encountered during an Adabas call.(See the Adabas Messages and Codes Manual)ESQ9500 – ESQ9999Buffer manager errors, etc.Compilation Error ClassificationErrors occuring during compilation can have one of the following error classes:WarningDuring compilation of a statement a situation was detectedwhich although not wrong, needs to be brought to the attentionof the user.SyntaxA syntactical error was detected during the compilation of astatement.SemanticA semantical error was detected during the compilation of astatement.FatalA serious error, which prematurely terminates the compilationprocess, was detected during the compilation of a statement.1

2

1ADABAS SQL SERVER MAINFRAME CODESThis chapter describes various types of messages and codes occuring on mainframe platforms only.Abend Codes — Mainframe PlatformsThese abnormal termination codes result from fatal internal errors and require the immediateattention of the Software AG support specialists.The following ABEND codes can occur in either the mainframe client or Server Session.ABENDCICSDescriptionAEY9ESQ Environment is not initialised– Use the CICS Transaction ESQI to initialize the ESQ EnvironmentELADCannot load CICS ADALNK– Check the ADALINK (.) definitionin the VO Parameter module(VOPRM)ESTWTWA address is not acessible on ADABAS call– Check the TWA size of the ESQ CICS client transaction: ensure that it isat least 32 bytes in size.E100SQLIOR call function code not recognized– Fatal internal error, contact Software AG SupportVOANCannot link CICS ADALNK– Check as ELAD above, and that the ADALINK is accessible using theEXEC CICS LINK commandVONMCannot load ESQLNKCI– Ensure that the ESQLNKCI is declared in the PPT and that the ESQ LoadLibrary is accessible using the EXEC CICS LINK and that the ESQLNKCI has beencopied, as described in the installation step D.3778Not enough storage space available to start the C-environment in the module:L UMAIN – C environment createL UATEX – C “ATEXIT” routine buildL UEXLK – C “ATEXIT” routine buildL URETR – retry on longjump998E998Installation step B.7 has not been completed successfully1201E201VOPRM not found. Terminating abnormally U1201– Ensure that the library/sublibrary containing the VOPRM module is defined in the relevant JCL3

1Adabas SQL Server Messages and Codes ManualABENDCICSDescription1202E202C stack overflow1203E203Error in PLUTO return (on prolog)1204E204Error in PLUTO return (on epilog) or bad target for LONGJMP12061224On server initialization, the ’threadsize’ provided is less than 64 KBE224123412994Attempt to issue LONGJMP under CICS or an environment where it isforbiddenA time arithmetic function has resulted in a GMT time difference callE299VOINIT failed. Terminating abnormally U1299– Fatal internal error, contact Software AG Support

Adabas SQL Server Mainframe Codes1Console Messages — Mainframe PlatformsSome Adabas SQL Server error messages may be accompanied by console messages which aredesribed here. For example:ESQ8516TUPLE MANAGER BUFFER SORT:vo execute file sort r eturned –nnThe above mainframe message is often issued together with the following console message:VO BMxx EBP ERROR – nnwhere xx is the module issuing the message:IN –OP –RD –WR –DE –InitializationFile OpenFile ReadFile WriteFile Purge1234567891011121314152050file not allocatedblock not allocatedno more file to allocateno more blocks to allocatenot enougn space in the temporary areaerror on opening the fileerror on closing the fileerror on reading the fileerror on writing the filefile link name (DDNAME) for workfile is missingworkfile is too smallworkfile is in useworkfile is not activeinvalid requestinvalid user IDinternal errorlock has been donewhere nn is a VO �–––5

1Adabas SQL Server Messages and Codes ManualSubcodeAction6Declare editor workfile10Check for missing file allocation statementEDITWORK (MVS and VSE)EDRWRK01 (BS2000)2,4,9Editor workfile is too small for the sort of join operation to be performed. Check the sizeand enlarge it accordingly.BS 2000 — Multi/Single-Session Driver Response CodesThe following response codes are issued by the multi/single-session driver (ESQMSRTN),which is a part of the Adabas SQL BS2000 Interface:6ESQ8734MSDRV: RESPONSE – msdriv-responseESQ8735MSDRV: RESPONSE – msdriv-response; SUBCODE subcodeWhere:msdriv responsesubcodeis the response-code returned from the module ESQMSDRVis the BS2000 macro response code.

Adabas SQL Server Mainframe Codes1The following table lists the response codes returned by ESQMSDRV (MSDRIV-Macro),provides a brief explanation and a reference to where more detailed information about thecorresponding BS2000 macro response codes may be found. Another table informing about theprobable cause of the subcode may be found later in this ÁÁÁÁÁÁÁÁÁÁCode / TextSubcodeExplanation01 TIMEOUT/ASYNCHR.–––Time Out During AsynchronousWrite02 SOLSIG/ASYNCHR.–––03 RDTFT/ROLLFILEDMS-CodeInvalid File Link/Attributes (ESQROLL)04 FSTAT/ROLLFILEDMS-Code.(1)Invalid File Link/Attributes (ESQROLL)05 ENASIMacro Rsp (2)06 ENQARMacro Rsp (2)07 ENAMPMacro Rsp (2)08 REQMPMacro Rsp (2)09 REQM/CLIENT-SLOTMacro Rsp (2)Insufficient Storage Resouces10 REQM/ASYNCHR.Macro Rsp (2)Insufficient Storage Resouces11 CCT LOCKED–––12 CCT FULL–––13 ENAEIMacro Rsp (2)14 ENACOMacro Rsp (2)15 OPEN/ROLLFILEFCB-Code (3)Invalid File Link/Attributes(ESQROLL)16 WRITE/ROLLFILEFCB-Code (3)Invalid File Link/Attributes(ESQROLL)17 WRITE/ASYNCHR.FCB-Code (3)Invalid File Link/Attributes(ESQROLL)18 WRITE/SYNCHR.FCB-Code (3)Invalid File Link/Attributes(ESQROLL)19 ADR.APPL.SYSTEM–––Required Module Missing(ESQMSSRV)7

1Adabas SQL Server Messages and Codes ÁCode / TextSubcodeExplanation20 ROLLSLOT OVERFLOWSize in Bytes (4)Compressed Threadslot too large21 ADR.SLOT.INIT–––22 SESSION-MODE–––23 MSBUFF MISSING–––24 CMPT TOO LARGE–––25 CMPT ERRORCCUPERR (5)Internal Error26 ROLLFILE ROLLTSZ–––Invalid File Link/Attributes(ESQROLL)27 INCORRECT SLOT–––Internal Error28 INIT.ERRORINITERR (6)Internal Error29 CLIENT NOT FOUND–––Internal Error30 INVALID FUNCTION–––Internal Error31 INVALID SLOT ADR–––Invalid ADDR-Parameter(ESQMSDRV)Required Module Missing(ESQMSSRV)(1) DMS-System error codes. For details refer to BS2000 System Help or to the SiemensBenutzerhandbuch: BS2000 DVS Assembler-Schnittstelle.(2) BS2000 macro response codes. For details refer to the table below or to the SiemensBenutzerhandbuch: BS2000 Makroaufrufe an den Ablaufteil.(3) DMS-System error codes extracted from FCB. For details refer to BS2000 System Helpor to the Siemens Benutzerhandbuch: BS2000 DVS Assembler-Schnittstelle.(4) Size of the compressed threadslot, which exceeded the MSDRIV/ROLLTSZ-Parameter.(5) Internal error codes (CCUPPER-Macro).(6) Internal error codes (ESQMSINI).8

Adabas SQL Server Mainframe Codes1BS2000 Macro ResponsesThe following table provides an overview of the macro response codes, which occur most often.This infomation has been derived from the Siemens Benutzerhandbuch: BS2000 Makroaufrufean den �ÁÁÁÁÁÁÁÁMacroResponseProbable CauseENACOx10000004Possible parameter errorx18000004Maximum number of serialisation id’s have been exceededx10000004Possible parameter errorx18000004Maximum number of serialisation id’s have been exceededx04000004Common memory pool does not existx08000004Memory pool exists already (MODE NEW) Conflicting Parametersx14000004Not enough free space in the user’s address space Not enough free spacebelow 16MBx18000004Invalid addressparameter conflict (ADDR 16MB/LOC BELOW)overlapping common memory poolsx1C000004Possible parameter errorCommon Memory Pool Name invalidinvalid SCOPE-ParameterPARMOD 24 in combination with 31-bit address modex20000004Request can not be fulfilled at the moment,due to a temporary shortage of resources.x10000004Possible parameter errorx18000004Maximum number of serialisation id’s have been exceededx10000004Possible parameter errorx18000004Maximum number of serialisation id’s have been exceededx40000004Klasse-5-Speicher exhaustedx14000004Not enough memory to fulfill requestRESIDENT PAGES parameter in START-PROGRAMor LOAD-PROGRAM exceeded.x18000004Requested address is not within Common Memory PoolAddress is not aligned to a 4KB boundryENAEIENAMPENASIENQARREQMP9

1Adabas SQL Server Messages and Codes ÁÁÁÁÁMacroREQM10ResponseProbable Causex1C000004Possible parameter errorCommon Memory Pool Name invalidinvalid SCOPE-ParameterPARMOD 24 in combination with 31-bit address modex24000004READ-ONLY memory poolx04Not enough memory to fulfil requestnot enough free space in the Paging Areax0CPossible parameter errorpossible overlap with common memory pool

2ADABAS SQL SERVER ERROR MESSAGESThis chapter contains the Adabas SQL Server Error Messages in ascending order.11

2ADABAS SQL Server Messages and Codes �––––––––––––1301ATTEMPTED ADABAS CALL FAILED WITH RESPONSE –––––––––––Text:ATTEMPTED ADABAS CALL FAILED WITH RESPONSEExpl:DURING THE COMPILATION OF A STATEMENT A CALL TO THE ESQ DIRECTORYFAILED AND RETURNED THE GIVEN ADABAS ERROR CODE.Actn:REFER THE PROBLEM TO YOUR SYSTEM OURCE STATEMENT DIRECTORY OVERFLOW DETECTED DURING RCE STATEMENT DIRECTORY OVERFLOW DETECTED DURING COMPILATIONExpl:T

Messages and Codes Manual. Manual Order Number: ESQ143-060ALL This document applies to Adabas SQL Server Version 1.4.3 and to all subsequent releases. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Readers’ comments are welcomed. Comments may be addressed to the Documentation Department