z/os: z/os language environment runtime messages

z/OS2.5

Language EnvironmentRuntime Messages

IBM

SA38-0686-50

Note

Before using this information and the product it supports, read the information in “Notices” on page797.

This edition applies to Version 2 Release 5 of z/OS® (5650-ZOS) and to all subsequent releases and modifications untilotherwise indicated in new editions.

Last updated: 2021-09-30© Copyright International Business Machines Corporation 1995, 2021.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

Tables................................................................................................................... v

About this document............................................................................................vii

How to send your comments to IBM.......................................................................ix

Summary of changes.............................................................................................xi

Chapter 1. Language Environment runtime messages............................................. 1

Chapter 2. C prelinker and C object library utility messages................................ 163

Chapter 3. C Utility messages.............................................................................173

Chapter 4. XL C/C++ runtime messages.............................................................. 195

Chapter 5. Fortran runtime messages.................................................................271

Chapter 6. PL/I runtime messages..................................................................... 399

Chapter 7. COBOL runtime messages..................................................................509

Chapter 8. Language Environment abend codes.................................................. 579

Chapter 9. Language Environment errno2 values................................................ 597

Chapter 10. SPC messages, abend and reason codes.......................................... 775

Chapter 11. Return codes to CICS...................................................................... 781

Appendix A. Accessibility...................................................................................793

Notices..............................................................................................................797

Index................................................................................................................ 801

iii

Tables

1. Basic Set of Qualifying Data for I/O Conditions....................................................................................... 272

2. Structure of file qualifying data that is not blank..................................................................................... 272

3. Structure of the code that references files by ddname........................................................................... 273

4. Names of resume actions......................................................................................................................... 273

5. File Organization and Conflicting Attributes.............................................................................................421

6. Operations and Conflicting File Organizations......................................................................................... 485

v

About this document

This document contains reference information that is intended to help you understand runtime messages,codes, and errno2 values that produced by the IBM® z/OS Language Environment® runtime, and to takeappropriate action. This information also explains message formats, conventions, and where to findadditional information.

Who should read this documentThis document is intended for anyone using z/OS Language Environment who wants descriptiveexplanations, system actions, and suggested responses to issued run-time messages, codes, and errno2values. A general knowledge of the z/OS Language Environment is useful for implementing recommendedresponses.

z/OS informationThis information explains how z/OS references information in other documents and on the web.

When possible, this information uses cross document links that go directly to the topic in reference usingshortened versions of the document title. For complete titles and order numbers of the documents for allproducts that are part of z/OS, see z/OS Information Roadmap.

To find the complete z/OS library, go to IBM Documentation (www.ibm.com/docs/en/zos).

© Copyright IBM Corp. 1995, 2021 vii

https://www.ibm.com/docs/en/zos

viii z/OS: z/OS Language Environment Runtime Messages

How to send your comments to IBM

We invite you to submit comments about the z/OS product documentation. Your valuable feedback helpsto ensure accurate and high-quality information.

Important: If your comment regards a technical question or problem, see instead “If you have a technicalproblem” on page ix.

Submit your feedback by using the appropriate method for your type of comment or question:Feedback on z/OS function

If your comment or question is about z/OS itself, submit a request through the IBM RFE Community(www.ibm.com/developerworks/rfe/).

Feedback on IBM Documentation functionIf your comment or question is about the IBM Documentation functionality, for example searchcapabilities or how to arrange the browser view, send a detailed email to IBM Documentation Supportat [email protected].

Feedback on the z/OS product documentation and contentIf your comment is about the information that is provided in the z/OS product documentation library,send a detailed email to [email protected]. We welcome any feedback that you have, includingcomments on the clarity, accuracy, or completeness of the information.

To help us better process your submission, include the following information:

• Your name, company/university/institution name, and email address• The following deliverable title and order number: z/OS Language Environment Runtime Messages,

SA38-0686-50• The section title of the specific information to which your comment relates• The text of your comment.

When you send comments to IBM, you grant IBM a nonexclusive authority to use or distribute thecomments in any way appropriate without incurring any obligation to you.

IBM or any other organizations use the personal information that you supply to contact you only about theissues that you submit.

If you have a technical problemIf you have a technical problem or question, do not use the feedback methods that are provided forsending documentation comments. Instead, take one or more of the following actions:

• Go to the IBM Support Portal (support.ibm.com).• Contact your IBM service representative.• Call IBM technical support.

© Copyright IBM Corp. 1995, 2021 ix

http://www.ibm.com/developerworks/rfe/

http://www.ibm.com/developerworks/rfe/

mailto:[email protected]

mailto:[email protected]

http://support.ibm.com

x z/OS: z/OS Language Environment Runtime Messages

Summary of changes

This information includes terminology, maintenance, and editorial changes. Technical changes oradditions to the text and illustrations for the current edition are indicated by a vertical line to the leftof the change.

Note: IBM z/OS policy for the integration of service information into the z/OS product documentationlibrary is documented on the z/OS Internet Library under IBM z/OS Product DocumentationUpdate Policy (www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/ibm-zos-doc-update-policy?OpenDocument).

Summary of message changes for Language Environment in z/OSVersion 2 Release 5 (V2R5) and its updates

The following messages are new, changed, or no longer issued for Language Environment in z/OS V2R5and its updates.

New messagesThe following messages are new.

CEE3935I

Changed messagesThe following messages are changed.

IBM0236IBM0598

Deleted messagesLanguage Environment no longer issues the following messages.

None.

New abend codesThe following abend codes are new.

X’400’ (1024)X’404’ (1028)

Changed abend codesThe following abend codes are changed.

U4093 (X'FFD')

New errno valuesThe following errno values are new.

C4030020C4030021C112001F

© Copyright IBM Corp. 1995, 2021 xi

https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/ibm-zos-doc-update-policy?OpenDocument




The following messages are new, changed, or no longer issued for Language Environment in z/OS V2R4and its updates.


IGZ0342W (APAR PH26783)IGZ0350S (APAR PH15921)IGZ0351S (APAR PH15921)IGZ0352S (APAR PH15921)IGZ0353S (APAR PH15921)IGZ0354S (APAR PH15921)IGZ0355S (APAR PH15921)IGZ0356I (APAR PH15921)IGZ0372S (APAR PH31133)IGZ0373S (APAR PH31133)IGZ0374S (APAR PH31133)IGZ0375S (APAR PH31133)IGZ0376S (APAR PH31133)

Changed messagesThe following messages have changed.

CEE3754SIGZ0064SIBM0225SIBM0236SIGZ0153SIGZ0339W


None.

New abend codesThe following abend codes are new.

X’400’ (1024) (APAR PH28966)X’404’ (1028) (APAR PH28966)

Changed abend codesThe following abend codes are changed.

U4093 (X'FFD') (APAR PH28966)

New errno valuesThe following errno values are new.

xii z/OS: z/OS Language Environment Runtime Messages

C4030020 (APAR PH28966)C4030021 (APAR PH28966)C112001F (APAR PH28966)


The following messages are new, changed, or no longer issued for Language Environment in z/OS V2R3and its updates. For more information, see z/OS Language Environment Runtime Messages.

The most recent updates are listed at the top of the section.


C03E0005C03E0011C0460037C0460051C04A001EC04A0031C066000AC066000BC066000CC0660012C1180046C1180047C1180048C1180049C118004AC118004BC118004CC118004EC118007DC1180085C1180086C1180087C1180088C1180089C118008AC118008BC118008CC118008DC118008EC11800A8C11800A9C9170002C917000BC932000EC9320022C9320023C9330071

Summary of changes xiii

C9340057C9340058C9340059C934005AC934005BC935002CC9360040C936007DC9360092C9360093C9360101C942000BC9420016CEE3252ECEE3257ECEE3258ECEE3259ECEE3600SCEE3880ICF060003CF06000BIBM0430SIBM0431SIBM0432SIBM0433SIBM0434SIBM0435SIBM0436SIBM0660SIBM0710SIBM0711SIBM0712SIBM0713SIBM0714SIBM0715SIBM0716SIBM0717SIBM0718SIBM0719SIBM0720SIBM0721SIBM0723SIBM0725SIBM0726SIBM0727SIBM0728SIBM0729SIBM0730SIBM0731SIBM0732SIBM0733S

xiv z/OS: z/OS Language Environment Runtime Messages

IBM0734SIBM0735SIBM0736SIBM0737SIBM0738SIBM0739SIBM0740SIGZ0277WIGZ0278SIGZ0279WIGZ0304WIGZ0305WIGZ0306WIGZ0307WIGZ0308WIGZ0309WIGZ0310WIGZ0311WIGZ0312WIGZ0313WIGZ0314WIGZ0315WIGZ0316WIGZ0317SIGZ0318WIGZ0319W for APAR PI83544IGZ0320W for APAR PI83544IGZ0321I for APAR PI83544IGZ0322I for APAR PI83544IGZ0323I for APAR PI83544IGZ0324I for APAR PI83544IGZ0325I for APAR PI83544IGZ0326I for APAR PI83544IGZ0327I for APAR PI83544IGZ0328I for APAR PI83544IGZ0329I for APAR PI83544IGZ0330I for APAR PI83544IGZ0335W for APAR PI83544IGZ0336W for APAR PI83544IGZ0337W for APAR PI83544IGZ0338W for APAR PI83544IGZ0339W for APAR PI83544IGZ0340W for APAR PI83544IGZ0341W for APAR PI83544IGZ0345S for APAR PI97171IGZ0346S for APAR PI97171IGZ0347S for APAR PI97171IGZ0348S for APAR PH02099IGZ0349S for APAR PH02099IGZ9900I for APAR PI97171IGZ9901I for APAR PI97171

Summary of changes xv

IGZ9910W for APAR PI97171IGZ9911W for APAR PI97171IGZ9920E for APAR PI97171IGZ9921E for APAR PI97171IGZ9930S for APAR PI97171IGZ9931S for APAR PI97171IGZ9940C for APAR PI97171IGZ9941C for APAR PI97171

Changed messagesThe following messages have changed.

IBM0722SIBM0724SIGZ0265S for APAR PI97171IGZ0266S for APAR PI97171IGZ0278S for APAR PI97171IGZ0279W for APAR PI97171IGZ0304W for APAR PI97171IGZ0305W for APAR PI97171IGZ0306W for APAR PI97171IGZ0307W for APAR PI97171IGZ0308W for APAR PI97171IGZ0309W for APAR PI97171IGZ0310W for APAR PI97171IGZ0311W for APAR PI97171IGZ0312W for APAR PI97171IGZ0313W for APAR PI97171IGZ0314W for APAR PI97171

The following abends have changed: U4080 (X'FF0') and U4088 (X'FF8')


C9340034C934004C

xvi z/OS: z/OS Language Environment Runtime Messages

Chapter 1. Language Environment runtime messages

The messages in this topic pertain to Language Environment. Each message is followed by an explanationdescribing the condition that caused the message, a programmer response suggesting how you mightprevent the message from occurring again, and a system action indicating how the system responds to thecondition that caused the message.

The messages also contain a symbolic feedback code, which represents the first 8 bytes of a 12-bytecondition token. You can think of the symbolic feedback code as the nickname for a condition. Assuch, the symbolic feedback code can be used in user-written condition handlers to screen for a givencondition, even if it occurs at different locations in an application.

The messages in this topic contain alphabetic suffixes that have the following meaning:I

Informational messageW

Warning messageE

Error messageS

Severe error messageC

Critical error message

CEE0000I The service completedsuccessfully.

ExplanationThe service completed successfully.

System actionNone

Programmer responseNone

Symbolic Feedback CodeCEE000

CEE0102S An unrecognized condition tokenwas passed to routine and couldnot be used.

ExplanationThe condition token passed to routine contained fieldsthat were not within the range of accepted values.

System actionUnless the condition is handled, the default action is toterminate the enclave.

Programmer responseVerify that the condition token passed to routine doesnot contain invalid fields.


CEE0110S For data conversion fromcharacter form to internal floating-point form, an invalid characterwas specified in the inputcharacter string character_string.

System actionThe output value from the conversion routine isundefined.

Programmer responseEnsure the input character string specified forconversion contains only numerical characters. Signs,decimal points, commas, exponents are not allowed inthe string. If the feedback token was omitted on the

© Copyright IBM Corp. 1995, 2021 1

call to the conversion routine, then the condition issignaled. Otherwise, examine the feedback token uponreturn and take appropriate action.

Symbolic Feedback CodeCEE03E

CEE0111S For data conversion from internalfloating-point form to characterform, the number of fraction digitsspecified was either negative orgreater than the value specifiedfor the length of the characterstring.


Programmer responseEnsure the input value specified for fraction digits isnon-negative and less than the value specified for thelength of the character string. If the feedback tokenwas omitted on the call to the conversion routine,then the condition is signaled. Otherwise, examinethe feedback token upon return and take appropriateaction.

Symbolic Feedback CodeCEE03F

CEE0112S For data conversion from internalfloating-point form to characterform, the value specified for thelength of the output characterstring is outside the acceptablerange. The valid range for E-formatconversion is 1 to 35, and for F-format conversion is 2 to 36.


Programmer responseEnsure the input value specified for the length of theoutput character string is within limit. If the feedbacktoken was omitted on the call to the conversionroutine, then the condition is signaled. Otherwise,examine the feedback token upon return and takeappropriate action.

Symbolic Feedback CodeCEE03G

CEE0113S For data conversion fromcharacter form to internal floating-point form, the value specified forthe length of the input characterstring is outside the acceptablerange. The valid range is 1 to 35.


Programmer responseEnsure the input value specified for the length of theinput character string is within limit. If the feedbacktoken was omitted on the call to the conversionroutine, then the condition is signaled. Otherwise,examine the feedback token upon return and takeappropriate action.

Symbolic Feedback CodeCEE03H

CEE0198S The termination of a thread wassignaled due to an unhandledcondition.

ExplanationTermination imminent due to an unhandled conditionwas signaled or was the target of a promote.

System actionIf this condition is signaled, or is the target of apromote, and it remains unhandled at stack framezero, the thread will terminate without re-raising thiscondition. If this condition was signaled with CEESGLspecifying a feedback code, the feedback code isreturned to the caller of CEESGL and control isreturned to the next sequential instruction followingthe call to CEESGL.

Programmer responseCall CEEITOK from a user-written condition handler todetermine what condition was unhandled. With thatinformation, you can either recover appropriately orallow termination to continue.


2 z/OS: z/OS Language Environment Runtime Messages

CEE0199W The termination of a thread wassignaled due to a STOP statement.

ExplanationThe termination of a thread was signaled.

System actionThe thread is terminated in a normal manner.

Programmer responseNo response is required. A thread is terminatingnormally.


CEE0201I An unhandled condition wasreturned in a feedback code.

ExplanationNo language run-time component event handler orCEEHDL routine handled the condition.

System actionLanguage Environment returns to the point at whichthe original condition was signaled.

Programmer responseSee the original condition.


CEE0250S An unrecognized label variablewas detected. The stack frameaddress could not be associatedwith an active stack frame.

ExplanationA call to CEEGOTO was made with a bad label variable.The label variable should be a valid code point that issubject to a current save area.

System actionThe thread is terminated.

Programmer responseThe label variable applies to a program that is nolonger active, or the label variable was not initialized.Make sure that the program is active.

Symbolic Feedback CodeCEE07Q

CEE0252W CEEHDLU was unable to find therequested user-written conditionhandler routine.

ExplanationA call to CEEHDLU was made to unregister a user-written condition handler that was not registered.

System actionNo user-written condition handlers are removed.

Programmer responseEnsure that the user-written condition handler you aretrying to free is registered.

Symbolic Feedback CodeCEE07S

CEE0253W A user-written condition handlerwas unregistered. Additionalregistration remain in the queue.

ExplanationA call to CEEHDLU was made to unregister a user-written condition handler. The user-written conditionhandler had been registered a multiple number oftimes.

System actionThe first occurrence of the user-written conditionhandler is removed from the queue. Otherregistrations remain on the queue.

Programmer responseNo programmer action is required.

Symbolic Feedback CodeCEE07T

CEE0254W The first parameter passed toCEEMRCR was not 0 or 1.

Chapter 1. Language Environment runtime messages 3

ExplanationThe first parameter passed to CEEMRCR was neither 0nor 1.

System actionThe resume cursor is not moved.

Programmer responseChange the first parameter (type_of_move) passed toCEEMRCR to a valid value (0 or 1).

Symbolic Feedback CodeCEE07U

CEE0255S The first parameter passed toCEEMRCE was an unrecognizedlabel.

ExplanationA move resume cursor must be made to a valid labelpointed to by CEEMRCE.


Programmer responseChange the position parameter pointed to byCEEMRCE to a valid label.

Symbolic Feedback CodeCEE07V

CEE0256W The user-written condition handlerroutine specified was alreadyregistered for this stack frame. Itwas registered again.

ExplanationCEEHDLR provided for multiple registration of user-written condition handler routines but the registrationof the same routine again for the same stack frame isconsidered unusual.

System actionThe handler is registered.

Programmer responseNo response is required. This message is just awarning.


CEE0257S The routine specified contained aninvalid entry variable.

ExplanationCEEHDLR could not validate the entry variable passed.


Programmer responseBuild and pass CEEHDLR a valid entry variable.


CEE0259S A move to stack frame zero usingCEEMRCR was attempted from aMAIN routine.

ExplanationThe handler for the first stack frame beyond stackframe zero attempted to do a move of the resumecursor with type_of_move = 1. The resume cursor wasnot moved.

System actionThe resume cursor is not moved. The thread isterminated.

Programmer responseDo not attempt to move the resume cursor to the callerof the main routine. If you want to end the thread,signal Termination Imminent.


CEE0260S No condition was active when acall to a condition managementroutine was made. The requestedfunction was not performed.


ExplanationThe condition manager had no record of an activecondition.


Programmer responseNo response is required. Calls to these routines shouldonly be made within the handler routine.


CEE0264S An invalid request to resume acondition was detected.

ExplanationA user-written condition handler attempted to resumefor a condition for which resumption is not allowedunless the resume cursor is moved.

Note: CEE088 might not be handled and resumedwithout moving the resume cursor. If resumption isrequested without moving the resume cursor, theenvironment is terminated with ABEND 4091-12.

System actionThe resume request that triggered this condition isignored.

Programmer responseMove the resume cursor as part of handling thecondition.


CEE0277W CEEMRCR was called to performan unnecessary move.

ExplanationA user-written condition handler attempted to movethe resume cursor with type_of_move = 0 and with thehandle and resume cursors pointing to the same stackframe. The handle and resume cursor might point tothe same stack frame either because the handler is forthe incurring frame or because the resume cursor hasalready been moved to the frame being handled.

System actionNo action is taken by the Condition Manager. Theresume cursor is not moved.

Programmer responseNo response is necessary.

Symbolic Feedback CodeCEE08L

CEE0355C The user-written conditionhandler that was scheduledusing CEEHDLR returned anunrecognized result code.

ExplanationA user written condition handler passed an invalidresult code. A user-written condition handler haseither returned without setting a reason code variableto a valid response code or has moved the resumecursor that caused a return to condition managementwithout a valid response code being set.


Programmer responseSupply a valid result code.

Symbolic Feedback CodeCEE0B3

CEE0356C An internal condition handlerreturned an unrecognized resultcode.

ExplanationA language run-time component condition handlerpassed an invalid result code.


Programmer responseContact your service representative.

Symbolic Feedback CodeCEE0BA


CEE0374C CONDITION = condition-idTOKEN = condition-token WHILERUNNING PROGRAM program-name WHICH STARTS AT program-address AT THE TIME OFINTERRUPT PSW psw GPR 0-3gpr0 gpr1 gpr2 gpr3 GPR 4-7 gpr4gpr5 gpr6 gpr7 GPR 8-B gpr8 gpr9gprA gprB GPR C-F gprC gprD gprEgprF FLT 0-2 flt0 flt2 FLT 4-6 flt4flt6

ExplanationAn unrecoverable condition occurred while processinga previous condition. This message is issued with aWTO because Language Environment has encountereda critical error while handling a previous condition. TheCONDITION indicates the message representing thecondition being handled and the TOKEN is the threeword Language Environment Condition Token. Theprogram-name, program-address (starting address ofprogram), psw, and registers are for the conditionbeing handled when the unrecoverable conditionoccurred. If the CEE0374C message appears severaltimes in sequence, the conditions appear in orderof occurrence. Correcting the earliest condition mayallow the application to run successfully.

System actionThe thread is terminated abnormally.

Programmer responseAttempt to correct the original condition by looking upthe condition-token specified in the message.

Symbolic Feedback CodeCEE0BM

CEE0398W Resume with new input.

ExplanationThis condition was returned from a user-writtencondition handler to tell Language Environment toretry the operation with new input.

System actionLanguage Environment attempts to retry the operation.

Programmer responseNo programmer response is required.

Symbolic Feedback CodeCEE0CE

CEE0399W Resume with new output.

ExplanationThis condition was returned from a user-writtencondition handler to tell Language Environment toretry the operation with new output.

System actionLanguage Environment resumes execution with newoutput.


Symbolic Feedback CodeCEE0CF

CEE0400E An invalid action code action-codewas passed to routine routine-name.

ExplanationAn action code parameter passed to routine did notcontain a valid value.

System actionNo system action is performed. The output isundefined.

Programmer responseProvide a valid action code.

Symbolic Feedback CodeCEE0CG

CEE0401S An invalid case code case-codewas passed to routine routine-name.

ExplanationA case code parameter must be a 2-byte integer with avalue of 1 or 2.



Programmer responseProvide a valid case code.

Symbolic Feedback CodeCEE0CH

CEE0402S An invalid control code control-code was passed to routineroutine-name.

ExplanationA control code parameter must be a 2-byte integerwith a value of 0 or 1.

System actionNo system action is performed.

Programmer responseProvide a valid control code.

Symbolic Feedback CodeCEE0CI

CEE0403S An invalid severity code severity-code was passed to routineroutine-name.

ExplanationA severity code parameter must be a 2-byte integerwith a value between 0 and 4.


Programmer responseProvide a valid severity code.

Symbolic Feedback CodeCEE0CJ

CEE0404W Facility ID facility-id with non-alphanumeric characters waspassed to routine routine-name.

ExplanationA facility ID parameter was passed with characters notin the range of A-Z, a-z, 0-9.

System actionNo system action is performed. Processing continues.

Programmer responseVerify that the facility ID passed is the correct value.

Symbolic Feedback CodeCEE0CK

CEE0450S The message inserts for thecondition token with messagenumber message-number andfacility ID facility-id could not belocated.

ExplanationAn insert area for the given condition token did notexist. It possibly was never allocated, or was reused byanother condition.


Programmer responseVerify that the message-number and Facility-ID passedcontain the correct values. If so, verify that theprogram was run with the MSGQ option specifyinga large enough value to contain all the insert areasnecessary for this program to run.

Symbolic Feedback CodeCEE0E2

CEE0451S An invalid destination codedestination-code was passed toroutine routine-name.

ExplanationA destination code must be a 4-byte integer with avalue of 2.

System actionNo system action is performed. The message is notwritten.

Programmer responseProvide a valid destination code.



CEE0452S An invalid facility ID facility-id waspassed to routine routine-name.

ExplanationA facility id parameter must be a 3-alphanumericcharacter field.


Programmer responseProvide a facility id made up of 3-alphanumericcharacters that corresponds to a product recognizedby Language Environment. The IBM-supplied facilityids are IBM, CEE, IGZ, and EDC.


CEE0454S The message number message-number could not be found forfacility ID facility-id.

ExplanationThe message could not be located within the sourcemessage files for facility-id.


Programmer responseEnsure the message number is contained within thesource message file for facility-id.


CEE0455W The message with messagenumber message-number andfacility ID facility-id wastruncated.

ExplanationThe message could not fit within the message buffersupplied. Msg_index contains the index into themessage returned.

System actionThe index into the message is returned in msg_ptr.

Programmer responseSubsequent calls to CEEMGET with the previouslyreturned msg_index value will retrieve the remainderof the message.


CEE0457S The message file destinationddname could not be located.

ExplanationAn error was detected trying to access the givenmessage file ddname.


Programmer responseVerify that the file exists and is usable.


CEE0458S The message repository repository-name could not be located.

ExplanationThe file containing the table of message file namescould not be located. The name of the file wastxxxMSGT, where t was either the letter "I" for anIBM-assigned facility id, or "U" for a user-assignedfacility id. xxx was the facility id. MSGT was the letters"MSGT".



Programmer responseVerify that the table exists and is appropriately named.

Symbolic Feedback CodeCEE0EA

CEE0459S Not enough storage was availableto create a new instance specificinformation block.

ExplanationA new ISI could not be created because not enoughstorage was available.

System actionNo storage is allocated.

Programmer responseEnsure that the REGION size is sufficient to run theapplication. Verify that the storage sizes specified inthe HEAP run-time option is reasonable, given theregion size allocated to the application.

Symbolic Feedback CodeCEE0EB

CEE0460W Multiple instances of the conditiontoken with message numbermessage-number and facility IDfacility-id were detected.

ExplanationA message insert block for the given condition tokenalready existed. A new message insert block wascreated. The two were differentiated by the I_S_infofield in the condition token.

System actionA call to CEEMSG or CEEMGET will format the messageassociated with the instance of the message insertblock indicated by the I_S_info field of the conditiontoken.

Programmer responseNo response is required.

Symbolic Feedback CodeCEE0EC

CEE0461S The maximum number of uniquemessage insert blocks wasreached. This condition token hadits I_S_info field set to 1.

ExplanationThe maximum number of 2,147,483,647 uniquemessage insert blocks was reached. The conditiontoken passed had its I_S_info field set to 1.

System actionThe I_S_info field in the condition token is set to 1.


Symbolic Feedback CodeCEE0ED

CEE0462S Instance specific information forthe condition token with messagenumber message-number andfacility ID facility-id could not befound.

ExplanationThe ISI associated with the condition token was notlocated. It possibly was reused by another condition ifthe number specified in the MSGQ run-time option wasexceeded.


Programmer responseSpecify a MSGQ run-time option that is sufficient tocontain all the active ISIs.

Symbolic Feedback CodeCEE0EE

CEE0463S The maximum size for an insertdata item was exceeded.

ExplanationThe maximum size of 254 for the length of an insertdata item was exceeded.


System actionNo system action is performed. The insert is notcreated.

Programmer responseMake the insert 254 characters or less. If this is notpossible, divide the insert into 2 or more inserts.

Symbolic Feedback CodeCEE0EF

CEE0464S Instance-specific information forthe condition token with messagenumber message-number andfacility ID facility-id did not exist.

ExplanationNo ISI was associated with the condition token. It ismost likely that the information was never created.


Programmer responseIf this condition was returned by a LanguageEnvironment service, contact your servicerepresentative. Otherwise, make sure that the correctI_S_info was identified.

Symbolic Feedback CodeCEE0EG

CEE0502S The operational descriptor forthe argument list was missing inroutine routine-name.

ExplanationThe high order bit of register 1 was off or the constantX'81C3C501' was missing from the storage locationimmediately preceding the argument list.



Symbolic Feedback CodeCEE0FM

CEE0553S An internal error was detectedin creating the inserts for acondition.

ExplanationAn invalid insert number was passed to the routine toformat inserts.



Symbolic Feedback CodeCEE0H9

CEE0554W A value outside the range of 0through 999,999 was supplied.However, the value was still usedas the enclave return code.

ExplanationLanguage Environment prefers the user to set theenclave return code to a value of 0 through 999,999.

System actionThe value will still be used as the enclave return code.

Programmer responseIf possible, change the return code to be within therange of 0 through 999,999.

Symbolic Feedback CodeCEE0HA

CEE0802C Heap storage control informationwas damaged.

ExplanationInternal control information saved in header recordswithin the heap was damaged.

System actionNo storage is allocated. A severity 4 condition issignaled and the application is terminated.


Programmer responseEnsure that your program does not write data to anarea larger than the original allocation. For example,allocating a 100 byte area and then writing 120 bytesto this area could cause damage to a storage header.

Symbolic Feedback CodeCEE0P2

CEE0803S The heap identifier in a get storagerequest or a discard heap requestwas unrecognized.

ExplanationThe heap identifier supplied in a call to CEEGTST orCEEDSHP did not match any known heap identifier,or the heap had already been discarded by a call toCEEDSHP (discard heap) before the request.

System actionNo storage is allocated. The value of the addressparameter is undefined.

Programmer responseFor get heap storage requests, ensure that the value inthe heap identifier parameter is either 0, indicating thedefault heap, or an identifier returned by the CEECRHP(create heap) service. For all other requests, ensurethat the heap is not discarded before the request.


CEE0804S The initial size value supplied ina create heap (CEECRHP) requestwas invalid.

ExplanationThe initial size value supplied to CEECRHP was anegative number.

System actionNo heap is created. The value of the heap identifier isundefined.

Programmer responseEnsure that the value in the initial size parameteris either 0, indicating same as the initial heap, or apositive integer.


CEE0805S The increment size value suppliedin a create heap (CEECRHP)request was invalid.

ExplanationThe increment size value supplied to CEECRHP was anegative number.


Programmer responseEnsure that the value in the increment size parameteris either 0, indicating same as the initial heap, or apositive integer.


CEE0806S The options value supplied in acreate heap (CEECRHP) requestwas unrecognized.

ExplanationThe value of the options parameter supplied toCEECRHP was not recognized.


Programmer responseEnsure that the value in the options parameter iseither 0, indicating same as the initial heap, or one ofthe supported options values documented in the z/OSLanguage Environment Programming Guide.


CEE0807S An input supplied to a create userheap request (CEEVUHCR) was notvalid.


ExplanationThe value of an input parameter supplied toCEEVUHCR was not correct.

System actionNo heap is created. The value of the heap token isundefined.

Programmer responseEnsure that all of the input parameters have beenproperly specified on the call to CEEVUHCR.


CEE0808S Storage size in a get storagerequest (CEEGTST) or a reallocaterequest (CEECZST) was not apositive number.

ExplanationThe size parameter supplied in a get storage requestcall to CEEGTST or a reallocate call to CEECZST wasless than or equal to 0.


Programmer responseEnsure that the size parameter is a positive integerrepresenting the number of bytes of storage to beobtained.


CEE0809S The maximum number of heapswas reached.

ExplanationThe maximum number of heaps had already beencreated.


Programmer responseModify the program to discard unneeded heaps beforeattempting to create a new heap or restructure theapplication so that it requires fewer heaps.


CEE0810S The storage address in a freestorage (CEEFRST) request wasnot recognized, or heap storage(CEECZST) control informationwas damaged.

ExplanationThe address parameter supplied in a call to CEEFRSTor CEECZST did not contain the starting address ofa currently allocated area in the heap. Either thesupplied address was invalid, or the area had beenfreed previously.

System actionNo storage is freed. The address parameter is leftunchanged so that its value can be examined.

Programmer responseEnsure that the address parameter contains a valuereturned by a call to CEEGTST or CEECZST. Ensurethat the storage area to be freed has not been freedpreviously.

Symbolic Feedback CodeCEE0PA

CEE0812S An invalid attempt to discard theinitial heap was made.

ExplanationThe heap identifier supplied in a discard heap requestwas zero (indicating the initial heap) but the initialheap could not be discarded.

System actionNo storage is freed. The value of the heap identifierremains unchanged.

Programmer responseEnsure that the heap identifier supplied in the discardheap call is an identifier returned by the create heap(CEECRHP) service.


Symbolic Feedback CodeCEE0PC

CEE0813S Insufficient storage was availableto satisfy a get storage (CEECZST)request.

ExplanationThere was not enough free storage available to satisfya get storage call to CEEGTST or reallocate request callto CEECZST.


Programmer responseEnsure that the REGION size is sufficient to run theapplication. Ensure that the size parameter in the getstorage request is not an unusually large number.Verify that the storage sizes specified in the HEAPand STACK run-time options are reasonable, given theregion size allocated to the application. Verify that youare using storage options that get your storage fromabove the line, if you can, since you can run out ofstorage below the line much more easily.

Symbolic Feedback CodeCEE0PD

CEE0814S Insufficient storage was availableto extend the stack.

ExplanationDuring prologue processing, a new stack frame couldnot be obtained because there was not enough freestorage available.

System actionA SIGSEGV signal is raised. If the process is blockingor ignoring this signal, or is catching it but has notspecified that the catcher function should run onan alternate stack, the signal will be unblocked andits action set to default (i.e., terminate the process)before the signal is raised.

Programmer responseEnsure that the REGION size is sufficient to run theapplication.

If this is an AMODE 64 application:

• Ensure that the maximum stack size sub-option ofthe STACK64 run-time option is large enough tomeet the user stack requirements of the application.If this is a pthread, and THREADSTACK64(ON) hasbeen specified, then ensure that the maximumstack size sub-option of the THREADSTACK64 run-time option is large enough to meet the pthread'sstack requirements. See z/OS Language EnvironmentProgramming Reference for more information aboutthe STACK64 run-time and THREADSTACK64 option.

• Ensure that the MEMLIMIT setting for the applicationis large enough to meet the overall storagerequirements of the application. See z/OS MVSProgramming: Extended Addressability Guide formore information about MEMLIMIT.

Symbolic Feedback CodeCEE0PE

CEE0815E The stack soft limit set by the__set_stack_softlimit() functionhas been exceeded.

ExplanationDuring prologue processing the stack soft limit setby the __set_stack_softlimit() function has beenexceeded.

System actionA SIGSEGV signal with a si_code of _SEGV_SOFTLIMITis delivered to the thread where the soft limit wasexceeded.

Programmer responseThe soft limit can be increased or decreased by usingthe __set_stack_softlimit() function if desired.

Symbolic Feedback CodeCEE0PF

CEE1000S Language Environment internalabend. ABCODE = abcode REASON= rsncode

ExplanationThis message was issued to the operators consolein CICS® to indicate that Language Environment hadabended, with the abend code and reason code asspecified in the message.


System actionThe transaction is terminated abnormally with theabend code stated in this message.

Programmer responseRefer to the Language Environment Abend Codes topicin this information for details on the cause of theabend.

Symbolic Feedback CodeCEE0V8

CEE1001E A cross program branching wasattempted as a result of a CICSHANDLE command with the LABELoptions. This was not supportedby the language used by programprogram-name.

ExplanationThe HLL did not support transferring control tospecified LABEL.


Programmer responseThis is a language-specific restriction. See z/OSLanguage Environment Programming Guide forinformation on EXEC CICS.


CEE2001E For an exponentiation operation(R**S) where R and S are realvalues, R was less than zero inmath routine routine-name.

ExplanationInvalid arguments were specified to the scalar mathroutine.

System actionThe output value from the math routine is undefined.

Programmer responseEnsure the arguments are valid to the math routine.You might want to register a user handler that will gain

control if this condition is signaled (if the feedbacktoken was omitted on the call to the math routine, thenthe condition is signaled). If you specify the feedbacktoken on the call to the math routine, examine thefeedback token upon return from the math routine andtake appropriate action.

Symbolic Feedback CodeCEE1UH

CEE2002E The argument value was too closeto one of the singularities (plus orminus pi/2, plus or minus 3pi/2,for the tangent; or plus or minuspi, plus or minus 2pi, for thecotangent) in math routine routine-name.



Programmer responseEnsure the arguments are valid to the math routine.You might want to register a user handler that will gaincontrol if this condition is signaled (if the feedbacktoken was omitted on the call to the math routine, thenthe condition is signaled). If you specify the feedbacktoken on the call to the math routine, examine thefeedback token upon return from the math routine andtake appropriate action.

Symbolic Feedback CodeCEE1UI

CEE2003E For an exponentiation operation(I**J) where I and J are integers,I was equal to zero and J wasless than or equal to zero in mathroutine routine-name.





Symbolic Feedback CodeCEE1UJ

CEE2004E For an exponentiation operation(R**I) where R is real and I is aninteger, R was equal to zero and Iwas less than or equal to zero inmath routine routine-name.




Symbolic Feedback CodeCEE1UK

CEE2005E The value of the argument wasoutside the valid range range inmath routine routine-name.




Symbolic Feedback CodeCEE1UL

CEE2006E For an exponentiation operation(R**S) where R and S are realvalues, R was equal to zero and Swas less than or equal to zero inmath routine routine-name.




Symbolic Feedback CodeCEE1UM

CEE2007E The exponent exceeded limit inmath routine routine-name.





Symbolic Feedback CodeCEE1UN

CEE2008E For an exponentiation operation(Z**P) where the complex baseZ equals zero, the real part ofthe complex exponent P, or theinteger exponent P was less thanor equal to zero in math routineroutine-name.




Symbolic Feedback CodeCEE1UO

CEE2009E The value of the real part of theargument was greater than limit inmath routine routine-name.




Symbolic Feedback CodeCEE1UP

CEE2010E The argument was less than limitin math routine routine-name.

ExplanationInvalid arguments were specified to the scalar mathroutine, or a hardware square root exception occurredoutside of a math routine.

System actionThe output value from the math routine or square rootinstruction is undefined.

Programmer responseEnsure the arguments are valid to the math routine orthe input is valid for the square root instruction. Youmight want to register a user handler that will gaincontrol if this condition is signaled (if the feedbacktoken was omitted on the call to the math routine, thenthe condition is signaled. For square root exceptions,the condition is always signaled.) If you specify thefeedback token on the call to the math routine,examine the feedback token upon return from themath routine and take appropriate action.

Symbolic Feedback CodeCEE1UQ

CEE2011E The argument was greater thanlimit in math routine routine-name.





Symbolic Feedback CodeCEE1UR

CEE2012E The argument was less than orequal to limit in math routineroutine-name.




Symbolic Feedback CodeCEE1US

CEE2013E The absolute value of theimaginary part of the argumentwas greater than limit in mathroutine routine-name.




Symbolic Feedback CodeCEE1UT

CEE2014E Both arguments were equal tolimit in math routine routine-name.




Symbolic Feedback CodeCEE1UU

CEE2015E The absolute value of theimaginary part of the argumentwas greater than or equal to limitin math routine routine-name.





Symbolic Feedback CodeCEE1UV

CEE2016E The absolute value of theargument was greater than limit inmath routine routine-name.





CEE2017E The absolute value of theargument was greater than orequal to limit in math routineroutine-name.





CEE2018E The real and imaginary parts ofthe argument were equal to limitin math routine routine-name.





CEE2019E The absolute value of the real partof the argument was greater thanor equal to limit in math routineroutine-name.






CEE2020E For an exponentiation operation(R**S) where R and S are realvalues, either R is equal to zeroand S is negative, or R is negativeand S is not an integer whoseabsolute value is less than orequal to limit in math routineroutine-name.





CEE2021E For an exponentiation operation(X**Y), the argument combinationof Y*log2(X) generated a numbergreater than or equal to limit inmath routine routine-name.





CEE2022E The value of the argument wasplus or minus limit in math routineroutine-name.





CEE2024E An overflow has occurred in mathroutine routine-name.

ExplanationAn overflow had occurred in calculating the results inthe scalar math routine.



Programmer responseEnsure the input arguments are valid to the mathroutine. You might want to register a user handlerthat will gain control if this condition is signaled (ifthe feedback token was omitted on the call to themath routine, then the condition is signaled). If youspecify the feedback token on the call to the mathroutine, examine the feedback token upon return fromthe math routine and take appropriate action.


CEE2025W An underflow has occurred inmath routine routine-name.

ExplanationAn underflow had occurred in calculating the results inthe scalar math routine.




CEE2028E The value of the second argumentwas outside the valid range rangein math routine routine-name.



Programmer responseEnsure the arguments are valid to the math routine.You might want to register a user handler that will gain

control if this condition is signaled (if the feedbacktoken was omitted on the call to the math routine, thenthe condition is signaled). If you specify the feedbacktoken on the call to the math routine, examine thefeedback token upon return from the math routine andtake appropriate action.

Symbolic Feedback CodeCEE1VC

CEE2029E The value of the argument wasequal to limit in math routineroutine-name.

ExplanationInvalid input arguments were specified to the scalarmath routine.



Symbolic Feedback CodeCEE1VD

CEE2030E The value of the second argumentwas equal to limit in math routineroutine-name.



Programmer responseEnsure the input arguments are valid to the mathroutine. You might want to register a user handlerthat will gain control if this condition is signaled (ifthe feedback token was omitted on the call to themath routine, then the condition is signaled). If you


specify the feedback token on the call to the mathroutine, examine the feedback token upon return fromthe math routine and take appropriate action.

Symbolic Feedback CodeCEE1VE

CEE2031E The value of the argument wasa non-positive whole number inmath routine routine-name.




Symbolic Feedback CodeCEE1VF

CEE2040E The value of the third argumentwas outside the valid range rangein math routine routine-name.



Programmer responseEnsure the input arguments are valid to the mathroutine. You may want to register a user handler thatwill gain control if this condition is signaled (if thefeedback token was omitted on the call to the mathroutine, then the condition is signaled). If you specifythe feedback token on the call to the math routine,examine the feedback token upon return from themath routine and take appropriate action.

Symbolic Feedback CodeCEE1VO

CEE2041E The absolute value of the secondargument was greater than eitherthe value of the third argumentor the number of bits in the firstargument in math routine routine-name.




Symbolic Feedback CodeCEE1VP

CEE2042E The sum of the second and thethird arguments was greater thanthe number of bits in the firstargument in math routine routine-name.



Programmer responseEnsure the input arguments are valid to the mathroutine. You may want to register a user handler thatwill gain control if this condition is signaled (if thefeedback token was omitted on the call to the mathroutine, then the condition is signaled). If you specifythe feedback token on the call to the math routine,


examine the feedback token upon return from themath routine and take appropriate action.

Symbolic Feedback CodeCEE1VQ

CEE2043E The value of the second or thirdargument was less than 0 in mathroutine routine-name.




Symbolic Feedback CodeCEE1VR

CEE2050S The length of the first argumentwas less than 0 or greater than32767 in routine routine-name.

ExplanationInvalid length of input argument was specified.

System actionThe output value is undefined.

Programmer responseEnsure the length of input argument is valid.


CEE2051S The length of the second argumentwas less than 0 or greater than32767 in routine routine-name.

ExplanationInvalid length of input argument was specified.


Programmer responseEnsure the length of input argument is valid.


CEE2052S The length of the result was lessthan 0 or greater than 32767 inroutine routine-name.

ExplanationInvalid length of result was specified.


Programmer responseEnsure the length of result is valid.


CEE2053S The value of the second argumentwas not positive in routine routine-name.

ExplanationInvalid input argument was specified.


Programmer responseEnsure the input argument is valid.


CEE2502S The UTC/GMT was not availablefrom the system.


ExplanationA call to CEEUTC or CEEGMT failed because thesystem clock was in an invalid state. The current timecould not be determined.

System actionAll output values are set to 0.

Programmer responseNotify systems support personnel that the systemclock is in an invalid state.


CEE2503S The offset from UTC/GMT to localtime was not available from thesystem.

ExplanationA call to CEEGMTO failed because either (1) thecurrent operating system could not be determined, or(2) the time zone field in the operating system controlblock appears to contain invalid data.


Programmer responseNotify systems support personnel that the local timeoffset stored in the operating system appears tocontain invalid data.


CEE2505S The input_seconds value in a callto CEEDATM or CEESECI was notwithin the supported range.

ExplanationThe input_seconds value passed in a call toCEEDATM or CEESECI was not a floating-point numberbetween 86,400.0 and 265,621,679,999.999. Theinput parameter should represent the number ofseconds elapsed since 00:00:00 on 14 October 1582,with 00:00:00.000 15 October 1582 being the firstsupported time/date, and 23:59:59.999 31 December9999 being the last supported time/date.

System actionFor CEEDATM, the output value is set to blanks. ForCEESECI, all output parameters are set to 0.

Programmer responseVerify that input parameter contains a floating-pointvalue between 86,400.0 and 265,621,679,999.999.


CEE2506S An era (<JJJJ>, <CCCC> or<CCCCCCCC>) was used in apicture string passed to CEEDATM,but the input number-of-secondsvalue was not within thesupported range. The era could notbe determined.

ExplanationIn a CEEDATM call, the picture string indicated that theinput value was to be converted to an era; however,the input value that was specified lies outside therange of supported eras.

System actionThe output value is set to blanks.

Programmer responseVerify that the input value contains a valid number-of-seconds value within the range of supported eras.


CEE2507S Insufficient data was passed toCEEDAYS or CEESECS. The Lilianvalue was not calculated.

ExplanationThe picture string passed in a CEEDAYS or CEESECScall did not contain enough information. For example,it is an error to use the picture string MM/DD (monthand day only) in a call to CEEDAYS or CEESECS,because the year value is missing. The minimuminformation required to calculate a Lilian value is either(1) month, day and year, or (2) year and Julian day.

System actionThe output value is set to 0.


Programmer responseVerify that the picture string specified in a call toCEEDAYS or CEESECS specifies, as a minimum, thelocation in the input string of either (1) the year,month, and day, or (2) the year and Julian day.


CEE2508S The date value passed to CEEDAYSor CEESECS was invalid.

ExplanationIn a CEEDAYS or CEESECS call, the value in the DDor DDD field was not valid for the given year and/ormonth. For example, MM/DD/YY with 02/29/90, orYYYY.DDD with 1990.366 are invalid because 1990 isnot a leap year. This code can also be returned for anynonexistent date value such as June 31st or January 0.


Programmer responseVerify that the format of the input data matchesthe picture string specification and that input datacontains a valid date.


CEE2509S The era passed to CEEDAYS orCEESECS was not recognized.

ExplanationThe value in the era field passed in a call to CEEDAYSor CEESECS did not contain a supported era name.


Programmer responseVerify that the format of the input data matches thepicture string specification and that the spelling ofthe era name is correct. Note that the era namemust be a proper DBCS string, that is, the '<' positionmust contain a shift-out character (X'0E') and the '>'position must contain a shift-in character (X'0F').


CEE2510S The hours value in a call toCEEISEC or CEESECS was notrecognized.

Explanation(1) In a CEEISEC call, the hours parameter did notcontain a number between 0 and 23, or (2) in aCEESECS call, the value in the HH (hours) field didnot contain a number between 0 and 23, or the AP(a.m./p.m.) field was present and the HH field did notcontain a number between 1 and 12.


Programmer responseFor CEEISEC, verify that the hours parameter containsan integer between 0 and 23. For CEESECS, verify thatthe format of the input data matches the picture stringspecification, and that the hours field contains a valuebetween 0 and 23, (or 1 and 12 if the AP field is used).


CEE2511S The day parameter passed in aCEEISEC call was invalid for yearand month specified.

ExplanationThe day parameter passed in a CEEISEC call didnot contain a valid day number. The combination ofyear, month, and day formed an invalid date value.Examples: year=1990, month=2, day=29; or month=6,day=31; or day=0.


Programmer responseVerify that the day parameter contains an integerbetween 1 and 31, and that the combination of year,month, and day represents a valid date.



CEE2512S The Lilian date value passed in acall to CEEDATE or CEEDYWK wasnot within the supported range.

ExplanationThe Lilian day number passed in a call to CEEDATEor CEEDYWK was not a number between 1 and3,074,324.


Programmer responseVerify that the input parameter contains an integerbetween 1 and 3,074,324.


CEE2513S The input date passed in aCEEISEC, CEEDAYS, or CEESECScall was not within the supportedrange.

ExplanationThe input date passed in a CEEISEC, CEEDAYS, orCEESECS call was earlier than 15 October 1582, orlater than 31 December 9999.


Programmer responseFor CEEISEC, verify that the year, month, and dayparameters form a date greater than or equal to 15October 1582. For CEEDAYS and CEESECS, verify thatthe format of the input date matches the picture stringspecification, and that the input date is within thesupported range.

Symbolic Feedback CodeCEE2EH

CEE2514S The year value passed in aCEEISEC call was not within thesupported range.

ExplanationThe year parameter passed in a CEEISEC call did notcontain a number between 1582 and 9999.


Programmer responseVerify that the year parameter contains valid data,and that the year parameter includes the century. Forexample, you must specify the year as 1990, not as90.

Symbolic Feedback CodeCEE2EI

CEE2515S The milliseconds value in aCEEISEC call was not recognized.

ExplanationIn a CEEISEC call, the milliseconds parameter(input_milliseconds) did not contain a numberbetween 0 and 999.


Programmer responseVerify that the milliseconds parameter contains aninteger between 0 and 999.

Symbolic Feedback CodeCEE2EJ

CEE2516S The minutes value in a CEEISECcall was not recognized.

Explanation(1) In a CEEISEC call, the minutes parameter(input_minutes) did not contain a number between 0and 59, or (2) in a CEESECS call, the value in the MI(minutes) field did not contain a number between 0and 59.


Programmer responseFor CEEISEC, verify that the minutes parameter(input_minutes) contains an integer between 0 and 59.For CEESECS, verify that the format of the input datamatches the picture string specification, and that theminutes field contains a number between 0 and 59.


Symbolic Feedback CodeCEE2EK

CEE2517S The month value in a CEEISEC callwas not recognized.

Explanation(1) In a CEEISEC call, the month parameter(input_month) did not contain a number between 1and 12, or (2) in a CEEDAYS or CEESECS call, the valuein the MM field did not contain a number between 1and 12, or the value in the MMM, MMMM, etc. field didnot contain a correctly spelled month name or monthabbreviation in the currently active National Language.


Programmer responseFor CEEISEC, verify that the month parameter(input_month) contains an integer between 1 and 12.For CEEDAYS and CEESECS, verify that the format ofthe input data matches the picture string specification.For the MM field, verify that the input value is between1 and 12. For spelled-out month names (MMM,MMMM, etc.), verify that the spelling or abbreviationof the month name is correct in the currently activeNational Language.

Symbolic Feedback CodeCEE2EL

CEE2518S An invalid picture string wasspecified in a call to a date/timeservice.

ExplanationThe picture string supplied in a call to one of thedate/time services was invalid. Only one era characterstring can be specified. The picture string containedan invalid DBCS string or contains more than one eradescriptor.


Programmer responseVerify that the picture string contains valid data. Onlyone era character string can be specified. If the picturestring contains the X'0E' (shift-out) character, thisindicates the presence of DBCS data. Therefore, (1)

the DBCS data must be terminated by a X'0F' (shift-in) character, (2) there must be an even number ofcharacters between the shift-out and shift-in, and (3)these characters must all be valid DBCS characters.

Symbolic Feedback CodeCEE2EM

CEE2519S The seconds value in a CEEISECcall was not recognized.

Explanation(1) In a CEEISEC call, the seconds parameter(input_seconds) did not contain a number between 0and 59, or (2) in a CEESECS call, the value in the SS(seconds) field did not contain a number between 0and 59.


Programmer responseFor CEEISEC, verify that the seconds parameter(input_seconds) contains an integer between 0 and 59.For CEESECS, verify that the format of the input datamatches the picture string specification, and that theseconds field contains a number between 0 and 59.

Symbolic Feedback CodeCEE2EN

CEE2520S CEEDAYS detected non-numericdata in a numeric field, or the datestring did not match the picturestring.

ExplanationThe input value passed in a CEEDAYS call did notappear to be in the format described by the picturespecification. For example, non-numeric charactersappear where only numeric characters are expected.


Programmer responseVerify that the format of the input data matches thepicture string specification and that numeric fieldscontain only numeric data.


Symbolic Feedback CodeCEE2EO

CEE2521S The Japanese (<JJJJ>) or Chinese(<CCCC>) year-within-Era valuepassed to CEEDAYS or CEESECSwas zero.

ExplanationIn a CEEDAYS or CEESECS call, if the YY or ZYY picturetoken was specified, and if the picture string containedone of the era tokens such as <CCCC> or <JJJJ>, thenthe year value must be greater than or equal to 1. Inthis context, the YY or ZYY field means year within Era.


Programmer responseVerify that the format of the input data matches thepicture string specification and that the input data isvalid.

Symbolic Feedback CodeCEE2EP

CEE2522S An era (<JJJJ>, <CCCC> or<CCCCCCCC>) was used in apicture string passed to CEEDATE,but the Lilian date value was notwithin the supported range. Theera could not be determined.

ExplanationIn a CEEDATE call, the picture string indicated that theLilian date was to be converted to an era, but the Liliandate lies outside the range of supported eras.


Programmer responseVerify that the input value contains a valid Lilian daynumber within the range of supported eras.

Symbolic Feedback CodeCEE2EQ

CEE2523W The system time was not availablewhen CEERAN0 was called. A seed

value of 1 was used to generate arandom number and a new seedvalue.

ExplanationA seed value of 0 was specified in a CEERAN0 call,indicating that the current system time should be usedas a seed value. Because the system time was notavailable, a seed value of 1 was used to generate anew seed value.

System actionA seed value of 1 is assumed. CEERAN0 returns both arandom number and a new seed value.

Programmer responseIf seed=1 is acceptable, no action is required.Otherwise, code an appropriate non-zero seed, or referto message CEE2502.

Symbolic Feedback CodeCEE2ER

CEE2524S An invalid seed value was passedto CEERAN0. The random numberwas set to -1.

ExplanationCEERAN0 was called with a seed value that was out ofrange.

System actionThe random number output was set to -1, and theseed value input was not changed.

Programmer responseCode a seed value between 0 and 2147483646,inclusive, for the CEERAN0 call.

Symbolic Feedback CodeCEE2ES

CEE2525S CEESECS detected non-numericdata in a numeric field, or thetimestamp string did not matchthe picture string.

ExplanationThe input value passed in a CEESECS call did notappear to be in the format described by the picture


specification. For example, non-numeric charactersappear where only numeric characters are expected,or the a.m./p.m. field did not contain the strings AM orPM.


Programmer responseVerify that the format of the input data matches thepicture string specification and that numeric fieldscontain only numeric data.

Symbolic Feedback CodeCEE2ET

CEE2526E The date string returned byCEEDATE was truncated.

ExplanationIn a CEEDATE call, the output string was not largeenough to contain the formatted date value.

System actionThe output value is truncated to the length of theoutput parameter.

Programmer responseVerify that the output string variable is large enoughto contain the entire formatted date. Ensure that theoutput parameter is at least as long as the picturestring parameter.

Symbolic Feedback CodeCEE2EU

CEE2527E The timestamp string returned byCEEDATM was truncated.

ExplanationIn a CEEDATM call, the output string was not largeenough to contain the formatted timestamp value.

System actionThe output value is truncated to the length of theoutput parameter.

Programmer responseVerify that the output string variable is large enoughto contain the entire formatted timestamp. Ensure thatthe output parameter is at least as long as the picturestring parameter.

Symbolic Feedback CodeCEE2EV

CEE2529S A debug tool has terminated theenclave.

ExplanationThe debug tool terminated the enclave at the user'srequest. Under VM, abend code 4094, reason codeX'28' is issued. Under MVS™, return code 3000 isissued.

System actionThe enclave is terminated.

Programmer responseNo programmer response is necessary.

Symbolic Feedback CodeCEE2F1

CEE2530S A debug tool was not available.

ExplanationEither the debug environment was corrupted or couldnot load the debug event handler.


Programmer responseMake sure the debug tool is installed with the loadablename CEEEVDBG.


CEE2531S The local time was not availablefrom the system.


ExplanationA call to CEELOCT failed because the system clockwas in an invalid state. The current time could not bedetermined.


Programmer responseNotify systems support personnel that the systemclock is in an invalid state.


CEE2533S The value passed to CEESCEN wasnot between 0 and 100.

ExplanationThe century_start value passed in a CEESCEN call wasnot between 0 and 100, inclusive.

System actionThe 100-year window assumed for all 2-digit years isunchanged.

Programmer responseEnsure that the input parameter is within range.


CEE2534W Insufficient field width wasspecified for a month or weekdayname in a call to CEEDATE orCEEDATM. Output set to blanks.

ExplanationThe CEEDATE or CEEDATM callable services issuedthis message whenever: (1) the picture stringcontained MMM, MMMMMZ, WWW, Wwww, etc.,requesting a spelled out month name or weekdayname, (2) the national language currently in effect wasa DBCS (Double Byte Character Set) language suchas NATLANG(JPN), and (3) the month name currentlybeing formatted contained more characters than canfit in the indicated field.

System actionThe month name and weekday name fields that areof insufficient width are set to blanks. The rest of theoutput string is unaffected. Processing continues.

Programmer responseIncrease the field width to contain the longestmonth or weekday name being formatted, includingtwo bytes for the SO/SI characters. For Japanese,eight characters are sufficient (3 DBCS + SO/SI), soone should specify MMMMMMMM or MMMMMMMZ,WWWWWWWW or WWWWWWWWZ in the picturestring.


CEE2535S Profiler loaded, Debug Toolunavailable.

ExplanationProfiler and Debug Tool cannot run concurrently.


Programmer responseTo dynamically invoke Debug Tool, set PROFILE run-time option OFF.


CEE2600I Success with zero result.

ExplanationThe floating-point input value was a true zero, and thecaller is to provide the appropriate formatting.

System actionProgram continues.




CEE2601I Success with positive result.

ExplanationThe conversion has been completed successfully, andthe result is strictly greater than zero.




CEE2602I Success with negative result.

ExplanationThe conversion has been completed successfully, andthe result is strictly less than zero.




CEE2603I Success with plus-rounded-to-zero result.

ExplanationThe conversion has been completed successfully, andthe result contains a zero result that was created by astrictly positive input value that rounded to zero.



Symbolic Feedback CodeCEE2HB

CEE2604I Success with minus-rounded-to-zero result.

ExplanationThe conversion has been completed successfully, andthe result contains a zero result that was created by astrictly negative input value that rounded to zero.



Symbolic Feedback CodeCEE2HC

CEE2606E Result overflows output field.

ExplanationThe floating-point input value is too large or the outputcharacter string is too small to contain the fixed-pointrepresentation of the input argument.

System actionThe result value is undefined.

Programmer responseEnsure the input floating-point value is properlyspecified and the length of the output character stringis big enough to contain the fixed-point representationof the input argument.

Symbolic Feedback CodeCEE2HE

CEE2607E Result has underflowed.

ExplanationThe conversion would have resulted in a numbersmaller than the underflow threshold for the floatingpoint representation.

System actionA true floating point zero result has been returned.


Programmer responseEnsure the input character value to be convertedis specified correctly. If the feedback token wasomitted on the call to the conversion routine, thenthe condition is signaled. Otherwise, examine thefeedback token upon return and take appropriateaction.

Symbolic Feedback CodeCEE2HF

CEE2608E Result has overflowed.

ExplanationThe conversion would have resulted in a number largerthan the overflow threshold for the floating pointrepresentation.

System actionThe maximum positive floating point magnitude hasbeen returned.

Programmer responseEnsure the input character value to be convertedis specified correctly. If the feedback token wasomitted on the call to the conversion routine, thenthe condition is signaled. Otherwise, examine thefeedback token upon return and take appropriateaction.

Symbolic Feedback CodeCEE2HG

CEE2701S An invalid category parameter waspassed to a locale function.

ExplanationAn invalid category parameter was passedto a locale function. Valid categories are:LC_ALL, LC_COLLATE, LC_CTYPE, LC_MESSAGES,LC_MONETARY, LC_NUMERIC, and LC_TIME.


Programmer responseSupply a valid category to the function.

Symbolic Feedback CodeCEE2KD

CEE2702S An invalid locale name parameterwas passed to a locale function.

ExplanationAn invalid locale name parameter was passed to alocale function. Locale name must be one providedwith the product or constructed using the LOCALEDEFutility.


Programmer responseSupply a valid locale name to the function.

Symbolic Feedback CodeCEE2KE

CEE2999C An internal logic error wasdetected in a date/time routine.

ExplanationAn internal logic error was detected in one of the date/time services. Internal date/time control blocks mighthave been damaged.

System actionThe requested action is not completed. Theapplication is terminated.

Programmer responseVerify that the program doesn't inadvertently overlayareas of storage reserved for library use.

Symbolic Feedback CodeCEE2TN

CEE3098S The user routine traceback couldnot be completed.

ExplanationThe user routine traceback could not be completeddue to an error detected in tracing back through theDSA chain.


System actionThe user routine traceback is not completed.

Programmer responseAttempt to perform problem determination throughthe use of a dump.


CEE3100E The title or option string passedwas longer than 120 bytes.

ExplanationThe maximum character string length for a dump islarger than allowed.

System actionThe title string is truncated to 120 bytes.

Programmer responseSpecify a string with 120 characters or less.


CEE3101E The title or option string passedto CEE3DMP is longer than 132bytes.

ExplanationThe maximum character string length for a dump titleis 132 bytes.

System actionThe title string is truncated to 132 bytes.

Programmer responseSpecify a dump title string with 132 characters or less.


CEE3102E Invalid CEE3DMP options orsuboptions were found andignored.

ExplanationInvalid options or suboptions were found in theoptions parameter to CEE3DMP.

System actionThe invalid options or suboptions are ignored, validoptions and suboptions are processed, and a dump isperformed.

Programmer responseCheck the options string passed to CEE3DMP. Makesure it has correct syntax and values for optionsand suboptions as specified in the z/OS LanguageEnvironment Programming Reference. Also, make surethe options string is 255 characters long.


CEE3103S An error occurred in writingmessages to the dump file.

ExplanationAn error occurred in trying to write information to thedump file, whose file name was specified with theFNAME option to CEE3DMP. The default file name wasCEEDUMP, or CESE transient data queue under CICS.

System actionDump processing is terminated at the point where thefile error is detected.

Programmer responseMake sure the file name is correct as specified in theoptions to CEE3DMP. Also, make sure there is enoughroom in the file to contain the dump.


CEE3104S Information could not besuccessfully extracted for thisDSA.

ExplanationSome information associated with the DSA or savearea passed to CEETRCB could not be determined.


System actionAll information that could be extracted is returned byCEETRCB. Any information that could not be extractedis zero or blank (depending on parameter type).

Programmer responseIf no information could be extracted by CEETRCB, it islikely that the DSAPTR parameter does not point to anactual DSA or save area.


CEE3105S The language dump exit wasunsuccessful.

ExplanationA language component of Language Environmentreturned this condition to the common component ofLanguage Environment when an error had occurred inthe language component's dump event handler thatwas not covered in the conditions returned by thedump CWI services.

System actionThe common component of Language Environmentignores this condition and continues dump processing.

Programmer responseNot applicable. This is an internal condition withinLanguage Environment, and is never seen by theapplication programmer.


CEE3106S An invalid parameter value wasspecified in a call to the CEEVDMPCWI service.

ExplanationThe CEEVDMP CWI service was called with an invalidvalue for one of the parameters.

System actionThe CEEVDMP service returns to the caller withoutadding any information to the dump.

Programmer responseCheck to make sure the parameters on the call toCEEVDMP are correct. In particular, check the lengthsof the strings passed as parameters.


CEE3107E The CEEHDMP or CEEBDMP CWIservice encountered inaccessiblestorage during dump processing.

ExplanationThe CEEHDMP CWI service encountered inaccessiblestorage while dumping a storage area, or theCEEBDMP CWI service encountered inaccessiblestorage while dumping a control block.

System actionThe message Inaccessible storage is printed inthe dump at the point of the encounter. The storageor control block dumping terminates, and CEEHDMP orCEEBDMP returns to the calling routine.

Programmer responseMake sure the address and length of the storage areaare correct for CEEHDMP. Make sure the address andoffset are correct for CEEBDMP, and that CEEBDMP isdumping the control block with a correct mapping forthe control block.


CEE3108E An invalid option, suboption, ordelimiter was found in the dumpoption string.

ExplanationAn invalid option, suboption, or delimiter was found inthe dump option string.

System actionNo system action is taken.

Programmer responseCorrect the error location as indicated in the positionparameter.



CEE3110E The cmd parameter is not a validcommand for __le_traceback().

ExplanationThe cmd parameter was not a valid command for__le__traceback(). No processing was performed.

System actionThe request has failed. The application continues torun.

Programmer responseProvide a valid cmd parameter. Refer to the descriptionof __le_traceback() in z/OS XL C/C++ Runtime LibraryReference for a list of valid commands.


CEE3111I CEEDUMP was defined as adummy data set. No LanguageEnvironment dump processingwas performed.

ExplanationThis message is issued when a Language Environmentdump report DD name is defined to DUMMY in a jobstep and CEE3DMP is called with a NULL feedbacktoken code (fc).

System actionNo Language Environment dump processing isperformed.

Programmer responseVerify if a CEEDUMP DD card should be defined toanother data set.


CEE3186E A field type parameter of theCEEBDMP CWI service containedan invalid value.

ExplanationThe field_ids, field_length, or field_types parameter ofthe CEEBDMP CWI service contained an invalid value.

System actionCEEBDMP returns to its caller. Information might havebeen written to the dump.

Programmer responseCheck to make sure the mapping of the control blockspecified to CEEBDMP through these three parametersis correct.

Symbolic Feedback CodeCEE33I

CEE3191E An attempt was made toinitialize an AMODE24 applicationwithout using the ALL31(OFF) andSTACK(,,BELOW) run-time options.

ExplanationDuring initialization it was detected that a programbegan in AMODE 24, yet the options required forcompletely safe execution in AMODE 24 were not fullyspecified.

System actionProgram initialization continues.

Programmer responseSpecify run-time options ALL31(OFF) andSTACK(,,BELOW) for AMODE 24 operation.

Symbolic Feedback CodeCEE33N

CEE3192C The Language Environment anchorsupport was not installed or wasnot supported on the operatingsystem.

ExplanationThe Language Environment anchor was the addressof the Language Environment main control block,the CAA. The underlying operating system mustprovide the Language Environment anchor support forLanguage Environment to get its main control block,the CAA. Because the anchor was not installed, theapplication was not able to run properly.


System actionThe application is terminated.

Programmer responseReport the error to your systems programmer. Checkwhether Language Environment anchor support isinstalled properly on the underlying operating system.

Symbolic Feedback CodeCEE33O

CEE3193I The invocation commandparameter string contained anunmatched quote character.

ExplanationThe invocation command parameter string contained abeginning quote (either single quote or double quote)but a matching end quote was not found.

System actionThe entire string is treated as user parameters.

Programmer responseCorrect the string.

Symbolic Feedback CodeCEE33P

CEE3194E An attempt was made to initializean AMODE24 program when theXPLINK(ON) run-time option wasin effect. AMODE24 programsare not supported in an XPLINKenvironment.

ExplanationDuring initialization it was detected that a programbegan in AMODE 24 and the XPLINK(ON) run-timeoption was in effect. The XPLINK(ON) run-time optionmay be in effect because it was specified or becauseXPLINK-compiled routines were found in the initialprogram of the application.


Programmer responseIf the application does not invoke any XPLINK-compiled routines, specify run-time optionsXPLINK(OFF), ALL31(OFF) and STACK(,,BELOW) forAMODE 24 operation. Otherwise, the application mustbe modified to eliminate either the AMODE24 routinesor the XPLINK routines.


CEE3195W The SNAP dump file could not beopened.

ExplanationThe SNAP dump file could not be opened.

System actionNo SNAP dump was taken.

Programmer responseIf a SNAP dump was desired, determine the reason thefile could not be opened and correct the problem.

Symbolic Feedback CodeCEE33R

CEE3196W The id number was not in theallowed range.

ExplanationThe id number was not in the required range of 0 to255.

System actionThe id number MOD 256 was used.

Programmer responseThis is an internal problem. Contact your servicerepresentative.


CEE3197W An invalid value for reserved waspassed.


ExplanationAn invalid value for the reserved parameter waspassed to the SNAP dump service.

System actionThe invalid value is ignored.



CEE3198S A SNAP dump was requested onan unsupported system.

ExplanationThe SNAP dump service was called to produce a SNAPdump on an unsupported system.

System actionThe SNAP dump was not produced.



CEE3199S An error was returned from theSNAP system function.

ExplanationThe SNAP dump service was called. It invoked theSNAP system service that failed.

System actionThe SNAP dump was not produced.



CEE3200S The system detected a programinterruption.

ExplanationThe Language Environment routine that processesprogram interruptions received a program interruptioncode.


Programmer responseObtain a CEEDUMP. The interruption code will bedisplayed in the Condition Information for ActiveRoutines section of the CEEDUMP. See a Principles ofOperation manual for a full list of interruption codes.


CEE3201S The system detected an operationexception (System CompletionCode=0C1).

ExplanationThe program attempted to execute an instruction withan invalid operation code. The operation code may beunassigned or the instruction with that operation codecannot be installed on this platform. See a Principlesof Operation manual for a full list of operationexceptions.


Programmer responseExamine the contents of registers 14 and 15. Ifregister 15 has a value of 0, then the cause wasprobably a routine didn't exist and a branch was madeto location 0. This would indicate a link-edit failure.Examine the contents of register 14 to determine thepoint at which the branch was made. Also examinethe linkage editor map for any unresolved referencesreported by the linkage editor.

Another possible cause is a routine branched to someunintended location, such as a conflict in addressingmode between the calling and the called routine, orany other program error that branched to the wronglocation.



CEE3202S The system detected a privileged-operation exception (SystemCompletion Code=0C2).

ExplanationAttempted to execute a privileged operation codewhile the machine was in a problem state. Seea Principles of Operation manual for a full list ofprivileged-operation exceptions.


Programmer responseExamine the contents of registers 14 and 15. Ifregister 15 has a value of 0, then the probable causeis that a routine doesn't exist and a branch was madeto location 0. This would indicate a link-edit failure.Examine the contents of register 14 to determine thepoint at which the branch was made. Also examinethe linkage editor map for any unresolved referencesreported by the linkage editor.

Another possible cause is a routine branched to someunintended location, such as a conflict in addressingmode between the calling and the called routine, orany other program error that branched to the wronglocation.


CEE3203S The system detected an executeexception (System CompletionCode=0C3).

ExplanationYour program attempted to execute an EXECUTEinstruction where the target of the first EXECUTEinstruction was another EXECUTE instruction. See aPrinciples of Operation manual for a full list of executeexceptions.


Programmer responseCheck your application for errors in the EXECUTEinstructions. See a Principles of Operation manual for afull list of execute exceptions.


CEE3204S The system detected a protectionexception (System CompletionCode=0C4).

ExplanationYour program attempted to access a storage locationto which it was not authorized.


Programmer responseCheck your application for these common errors:

• Using the wrong AMODE to reference storage• Trying to use a pointer that has not been set• Trying to store data into storage reserved for the

system• Using an invalid index to an array

See a Principles of Operation manual for a full list ofprotection exceptions.


CEE3205S The system detected anaddressing exception (SystemCompletion Code=0C5).

ExplanationYour program attempted to reference a main-storagelocation that was not available in the configuration.See a Principles of Operation manual for a full list ofaddressing exceptions.


Programmer responseCheck your application for these common errors:

• Using the wrong AMODE to reference storage


• Trying to use a pointer that has not been set• Trying to store data into storage reserved for the

system• Using an invalid index to an array

See a Principles of Operation manual for a full list ofaddressing exceptions.


CEE3206S The system detected aspecification exception (SystemCompletion Code=0C6).

ExplanationYour program attempted an invalid operation suchas incorrect use of registers. The register used foran operation was invalid. Examples include using anodd register number when an even register numberwas required, using a bad number for floating pointregisters, or having data that was not correctly aligned.


Programmer responseIf the program is being produced by a compiler, thenyou might be able to specify a different optimizationlevel to by-pass the problem. See a Principles ofOperation manual for a full list of specificationexceptions.


CEE3207S The system detected a dataexception (System CompletionCode=0C7).

ExplanationYour program attempted to use a decimal instructionincorrectly. See a Principles of Operation manual for afull list of data exceptions.


Programmer responseCheck the variables associated with the failingstatement to make sure that they have been initializedcorrectly.


CEE3208S The system detected a fixed-point overflow exception (SystemCompletion Code=0C8).

ExplanationYour program attempted to use signed binaryarithmetic or signed left-shift operations and anoverflow occurred. See a Principles of Operationmanual for a full list of fixed-point overflow exceptions.


Programmer responseYou can use a condition handling routine to correct thedata values and resume the application.


CEE3209S The system detected a fixed-point divide exception (SystemCompletion Code=0C9).

ExplanationYour program attempted to perform a signed binarydivision and the divisor is zero. See a Principles ofOperation manual for a full list of fixed-point divideexceptions.





CEE3210S The system detected a decimal-overflow exception (SystemCompletion Code=0CA).

ExplanationYour program attempted to perform a mathematicaloperation and one or more nonzero digits were lostbecause the destination field in a decimal operationwas too short to contain the results. See a Principlesof Operation manual for a full list of decimal-overflowexceptions.



Symbolic Feedback CodeCEE34A

CEE3211S The system detected adecimal-divide exception (SystemCompletion Code=0CB).

ExplanationYour program attempted to perform a mathematicaloperation where, in decimal division, the divisor is zeroor the quotient exceeds the specified data-field size.See a Principles of Operation manual for a full list ofdecimal-divide exceptions.



Symbolic Feedback CodeCEE34B

CEE3212S The system detected an exponent-overflow exception (SystemCompletion Code=0CC).

ExplanationYour program attempted a floating-point operation andthe result characteristic exceeded 127 and the result

fraction was not zero. See a Principles of Operationmanual for a full list of exponent-overflow exceptions.



Symbolic Feedback CodeCEE34C

CEE3213S The system detected an exponent-underflow exception (SystemCompletion Code=0CD).

ExplanationYour program attempted a floating-point operationand the result characteristic is less than zero andthe result fraction was not zero. See a Principles ofOperation manual for a full list of exponent-underflowexceptions.



Symbolic Feedback CodeCEE34D

CEE3214S The system detected asignificance exception (SystemCompletion Code=0CE).

ExplanationYour program attempted a floating-point addition orsubtraction and the resulting fraction was zero. Seea Principles of Operation manual for a full list ofsignificance exceptions.





CEE3215S The system detected a floating-point divide exception (SystemCompletion Code=0CF).

ExplanationYour program attempted a do a floating-point divideand the divisor had a zero fraction. See a Principles ofOperation manual for a full list of floating-point divideexceptions.




CEE3216S The system detected an IEEEinexact exception. The result wastruncated.

ExplanationAn IEEE-inexact condition is recognized when therounded result of an operation differs in value from theintermediate result computed as if exponent range andprecision were unbounded.

System actionThe thread or the process is terminated.



CEE3217S The system detected an IEEEinexact exception. The result wasincremented.

ExplanationAn IEEE-inexact condition is recognized when therounded result of an operation differs in value from theintermediate result computed as if exponent range andprecision were unbounded.

System actionThe thread or the process is terminated.



CEE3218S The system detected an IEEEexponent-underflow exception.

ExplanationAn IEEE-underflow condition is recognized when theexponent of the exact result of an operation would beless than the minimum exponent of the target format.




CEE3219S The system detected an IEEEexponent-underflow exception.The result was inexact andtruncated.





Symbolic Feedback CodeCEE34J

CEE3220S The system detected an IEEEexponent-underflow exception.The result was inexact andincremented.




Symbolic Feedback CodeCEE34K

CEE3221S The system detected an IEEEexponent-overflow exception.

ExplanationAn IEEE-overflow condition is recognized when theexponent of the rounded result of an operation wouldbe greater than the maximum exponent of the targetformat if the exponent range were unbounded.




CEE3222S The system detected an IEEEexponent-overflow exception. Theresult was inexact and truncated.




Symbolic Feedback CodeCEE34M

CEE3223S The system detected an IEEEexponent-overflow exception.The result was inexact andincremented.


System actionThe process is terminated.



CEE3224S The system detected an IEEEdivision—by—zero exception.

ExplanationAn IEEE-division—by—zero condition is recognizedwhen in BFP division the divisor is zero and thedividend is a finite nonzero number.





CEE3225S The system detected an IEEEinvalid operation exception.

ExplanationAn IEEE-invalid-operation condition is recognizedwhen any of the following occur:

1. An SNaN is encountered in any arithmetic orcomparison operation.

2. A QNaN is encountered in a comparison byCOMPARE AND SIGNAL.

3. A difference is undefined (addition of infinities ofopposite sign, or subtraction of infinities of likesign).

4. A product is undefined (zero times infinity).5. A quotient is undefined (DIVIDE instruction with

both operands zero or both operands infinity).6. A remainder is undefined (DIVIDE TO INTEGER

with a dividend of infinity or a divisor of zero).7. A square root is undefined (negative nonzero

operand).




CEE3226S An IEEE inexact exception wasreported.

ExplanationIEEE interruption simulation (IIS) event instructionswere used to report an IEEE inexact exception.Floating point software might detect that a roundedresult of an operation differed in value from theresult that could have been computed if precision andexponent range were unbounded.

System actionThe thread/process is terminated.

Programmer responseYou can use a condition handling routine to recoverfrom the error and resume the application.


CEE3227S An IEEE underflow exception wasreported.

ExplanationIEEE interruption simulation (IIS) event instructionswere used to report an IEEE underflow exception.Floating point software might detect that the exactresult of an operation was nonzero and less inmagnitude than the smallest normal number in thetarget format, but the result could still be representedexactly.


Programmer responseUse a condition handling routine to recover the errorand resume the application.


CEE3228S An IEEE underflow and inexactexception was reported.

ExplanationIEEE interruption simulation (IIS) event instructionswere used to report an IEEE underflow and inexactexception. Floating point software might detect thatthe exact result of an operation was nonzero and lessin magnitude than the smallest normal number in thetarget format, and the result could not be representedexactly.





CEE3229S An IEEE overflow exception wasreported.

ExplanationIEEE interruption simulation (IIS) event instructionswere used to report an IEEE overflow exception.Floating point software might detect that the roundedresult of an operation was larger in magnitude thanthe largest finite number in the target format, but thescaled result could still be represented exactly.




CEE3230E Vector unnormalized operandexception occurred.

ExplanationThe parameters to the vector instruction were floating-point numbers that are unnormalized.

System actionThe user program is terminated unless the condition ishandled.

Programmer responseThe data to be processed by the vector instructionsmust be normalized before it is to be handled in avector instruction. Normalize the input value by addingfloating-point zero (0.0) to the qdata item.


CEE3231S An IEEE overflow and inexactexception was reported.

ExplanationIEEE interruption simulation (IIS) event instructionswere used to report an IEEE overflow and inexactexception. Floating point software might detect thatthe rounded result of an operation was larger inmagnitude than the largest finite number in the targetformat, and the scaled result could not be representedexactly.




CEE3232S An IEEE division-by-zeroexception was reported.

ExplanationIEEE interruption simulation (IIS) event instructionswere used to report an IEEE division-by-zeroexception. Floating point software might detect thata finite non-zero floating point number was divided byzero.




CEE3233S An IEEE invalid-operationexception was reported.

ExplanationIEEE interruption simulation (IIS) event instructionswere used to report an IEEE invalid-operationexception. Floating point software might detect one ofthe following situations:

• A NaN was encountered.


• The result of an arithmetic operation was undefined(zero divided by zero, for example).

• The result of a QUANTIZE, REROUND, conversion, orother operations was undefined.




CEE3234S The system detected a Compareand Trap data exception.

ExplanationA Compare and Trap instruction (such as CRT, CGRT,CGFRT, CIT, CGIT, CLRT, CLGRT, CLGFRT, CLFIT, CLGIT)in your program generated a data exception.


Programmer responseUse a condition handling routine to correct theproblem and resume the application.


CEE3235S The system detected a vector-processing exception (SystemCompletion Code=0E0).

ExplanationYour application attempted to use a vector instructionincorrectly. See a principles of operations manual for afull list of vector-processing exceptions.


Programmer responseCheck and correct the usage of vector type data in theapplication.


CEE3236S The system detected a vector-processing exception of IEEEinvalid operation.

ExplanationA vector-processing condition of IEEE-invalid-operation is recognized when any of the followingoccur:

• An SNaN is encountered in any arithmetic orcomparison operation.

• A QNaN is encountered in a comparison by VECTORFP COMPARE AND SIGNAL SCALAR.

• A difference is undefined (addition of infinities ofopposite sign, or subtraction of infinities of like sign).

• A product is undefined (zero times infinity).• A quotient is undefined (VECTOR FP DIVIDE

instruction with both operands zero or bothoperands infinity).

• A square root is undefined (negative nonzerooperand).




CEE3237S The system detected a vector-processing exception of IEEEdivision-by-zero.

ExplanationA vector-processing condition of IEEE-division-by-zerois recognized when in BFP division the divisor is zeroand the dividend is a finite nonzero number.





CEE3238S The system detected a vector-processing exception of IEEEexponent-overflow.

ExplanationA vector-processing condition of IEEE-overflow isrecognized when the exponent of the rounded resultof an operation would be greater than the maximumexponent of the target format, if the exponent rangewere unbounded.




CEE3239S The system detected a vector-processing exception of IEEEexponent-overflow.

ExplanationA vector-processing condition of IEEE-underflow isrecognized when the exponent of the exact result of anoperation would be less than the minimum exponentof the target format.




CEE3240S The system detected a vector-processing exception of IEEEinexact.

ExplanationA vector-processing condition of IEEE-inexact isrecognized when the rounded result of an operationdiffered in value from the result that could havebeen computed if precision and exponent range wereunbounded.




CEE3250C The system or user abend abend-code was issued.

ExplanationA system or user abend has occurred.

System actionThe program is terminated abnormally.

Programmer responseLook in the messages and codes or system codesmanual for the particular platform to resolve thesystem-described problem.


CEE3251I An ATTENTION conditionoccurred.

ExplanationAn ATTENTION condition was signaled after pollingcode was invoked.

System actionThe program is resumed after the point where thecondition was signaled.

Programmer responseDo whatever is appropriate for the user to do, after theuser hits the "attention" key.



CEE3252E An attempt to call __CEEYSORTwas made from within a DFSORTexit routine.

ExplanationOnly one sort can be active at a time. A program calledduring the execution of SORT must have attempted toinvoke sort again.

System actionThe request was unsuccessful. A feedback is returned.If no feedback is requested and the raised condition isunhandled, the enclave terminates.

Programmer responseDo not attempt a sort from within a sort exit.

Problem determinationCEE35K

CEE3253C A critical condition occurredduring the sort operation.

ExplanationAn unrecoverable error prevented SORT fromcompleting.


Programmer responseTake the appropriate action defined by the SORTmessages.


CEE3254C An incorrect DFSORT Plist waspassed to CEE3SRT.

ExplanationThe parameter list for CEE3SRT must be the 31 bit listspecified by DFSORT.


Programmer responseCorrect the parameter list for CEE3SRT.


CEE3255C An attempt to call CEE3SRT wasmade from within a DFSORT exitroutine.

ExplanationOnly one sort can be active at a time. A program calledduring the execution of SORT must have attempted toinvoke sort again.


Programmer responseDo not attempt a sort from within a sort exit.


CEE3257E The version field does not containa supported value.

ExplanationThe __CEEYSORT service was called with a sort_plistthat did not contain a supported value in the__sort_version field. Currently the only valid value forthe __sort_version field is 1.


Programmer responseMake sure that the version field contains a supportedvalue.

Problem determinationCEE35P

CEE3258E The DFSORT E15 and E32 userexits are mutually exclusive.


ExplanationThe __CEEYSORT service was called with a sort_plistthat contained a non-zero value for both the__sort_e15 and __sort_e32 fields. One of these fieldsmust be zero.


Programmer responseMake sure that one of the fields is zero.

Problem determinationCEE35Q

CEE3259E Invoking DFSORT is not supportedwhen the POSIX(ON) runtimeoption is in effect.

ExplanationThe __CEEYSORT service was called when thePOSIX(ON) runtime option was in effect.


Programmer responseSpecify the POSIX(OFF) runtime option.

Problem determinationCEE35R

CEE3260W No condition was active when acall to a condition managementroutine was made.

ExplanationThe condition manager had no record of an activecondition.


Programmer responseNo response is required. Calls to conditionmanagement routines should only be made within thehandler routine.


CEE3261W service-name is not supported.

ExplanationThe service was no longer supported. It was providedfor migration and compatibility with previous releasesof Language Environment.

System actionThe service did not take any action.

Programmer responseMigrate an application to a supported function.


CEE3262W An invalid condition token waspassed. The condition token didnot represent an active condition.

ExplanationThe condition token passed to CEE3CIB did notrepresent a condition that is currently active.


Programmer responseNo programmer response required.


CEE3263C The condition handler's conditioninformation block was damaged.The requested function was notperformed.

ExplanationThe condition manager did not have a valid CIB chain.


System actionThe requested function is not performed.

Programmer responseThis is an internal problem. Contact you servicerepresentative.


CEE3264S No machine state block found inassociation with the current stackframe.

ExplanationYour program has not established a valid machinestate block (via CEE3SRP) associated with the currentstack frame.


Programmer responseMake sure CEE3SRP is issued before calling CEE3GMB.


CEE3292W The language run-time componentid was already registered. Noaction was taken.

ExplanationThe CEE3DHDL CWI was invoked previously with thesame language run-time component id.

System actionIf this condition is not handled, execution continues atthe instruction after the CEE3DHDL invocation.



CEE3293C The Language Environment wascorrupted. The save area chainwas broken.

ExplanationThe save area chain was not intact.

System actionThe function was not completed, and did not schedulethe routine.

Programmer responseLanguage Environment always expects the save areato be valid, and usually abends when it is not. Ensurethat the save chain is valid.


CEE3294E The cancel request could not beperformed, since the routine wasnot previously scheduled.

ExplanationA request was made to cancel a routine, but thatroutine could not be found on the active chain. Theroutine that was requested to cancel either was neverscheduled or was previously deleted.

System actionNo routine is released.

Programmer responseEnsure that routines are scheduled via CEEHDLRbefore an attempt is made to delete them.


CEE3295E The condition string fromCEE3SPM did not contain all ofthe settings, because the returnedstring was truncated.

ExplanationThe QUERY option of the CEE3SPM service needed alarger character string to represent the conditions.

System actionSome items might have been filled in.


Programmer responseTry increasing the character string length.


CEE3296E Some of the data in the conditionstring from CEE3SPM could not berecognized.

ExplanationThe data encountered in the string could not beinterpreted.

System actionOnly conditions that could be recognized were set.

Programmer responseCorrect the character representation for thecondition(s) and ensure that the string is padded withblanks.


CEE3297E The service completedsuccessfully for recognizedcondition(s), unsuccessfullyfor unrecognized (invalid)condition(s).

ExplanationThe data encountered in the string could not beinterpreted.

System actionOnly conditions that could be recognized were set.

Programmer responseCorrect the character representation for theconditions.


CEE3298E CEE3SPM attempted to PUSHsettings onto a full stack.

ExplanationThere was not enough storage for the CEE3SPM PUSHservice to save all of the conditions.

System actionNo settings were changed.

Programmer responseIncrease the size of the storage.


CEE3299E CEE3SPM attempted to POPsettings off an empty stack.

ExplanationA call to CEE3SPM was made to POP the stack. Therewere no elements on the stack to POP.

System actionNo settings are changed.

Programmer responseEnsure that something is on the stack before youattempt to POP it.


CEE3300E The action parameter in CEE3SPMwas not one of the digits 1 to 5.

ExplanationA call to CEE3SPM was made with an invalid action.

System actionNo settings were changed.

Programmer responseUse an action value parameter between 1 and 5 wheninvoking CEE3SPM.


CEE3301E The first parameter was not one ofthe digits expected.


ExplanationA call was made to a condition managementsubroutine that did not have a valid parameter for theaction parameter.


Programmer responseThis is an internal error. The internal routine was calledwith an improper parameter. Contact your servicerepresentative.


CEE3303E The callable service was passedreserved arguments that were notset to zero.

ExplanationThe reserved arguments passed to the callable serviceroutine must be set to zero.

System actionThe request was unsuccessful and a symbolicfeedback code was returned. If a symbolic feedbackcode was not requested and the raised condition wasnot handled, the enclave terminates.

Programmer responseVerify the reserved arguments passed to the callableservice routine are set to zero.


CEE3350S Unable to find the event handler.

ExplanationAn internal error occurred when LanguageEnvironment attempted to load a required languagerun-time component module.




CEE3351S Unable to properly initialize theevent handler.

ExplanationAn internal error occurred when LanguageEnvironment attempted to initialize a requiredlanguage run-time component module.




CEE3352E The enclave terminated with anon-zero return code.

ExplanationAn internal error occurred while attempting toterminate an enclave.




CEE3353S The parameter manipulationservice was called, but notduring the create enclave event,or not by a language run-timecomponent corresponding to theMAIN program.


ExplanationThe parameter manipulation service was used duringenclave initialization by the language in which the mainprogram was written. It was used in an illegal manner.

System actionThe requested parameter manipulation is notperformed and the main parameter list might not becorrect.



CEE3354S The parameter list manipulationservice was called in a CICSenvironment.

ExplanationThe parameter manipulation service was used duringenclave initialization by the language in which the mainprogram was written. It cannot be used in a CICSenvironment.

System actionThe requested parameter manipulation is notperformed and the main parameter list might not becorrect.



CEE3355S A language run-time componentinitialization has failed.

ExplanationAn internal error occurred while attempting toestablish a minimum environment for a language run-time component.




CEE3356S The rc_modifier must be in therange of 1 through 4. The returncode modifier was not changed.

ExplanationThe rc_modifier was not in the range of 1 through 4.The return code modifier that was first established bythe enclave termination services or by the conditionhandling was kept.


Programmer responseProvide a valid rc_modifier.


CEE3357S The service was invoked outside ofthe language run-time componentenclave termination. No actionwas taken.

ExplanationCEESRCM was to be called during the language run-time component enclave termination. It was invokedoutside of the language run-time component enclavetermination.


Programmer responseEnsure that the routine is called during the enclavetermination.



CEE3358E The service was invoked outside ofthe member enclave initialization.No action was taken.

ExplanationThis CWI service can only be invoked from withinmember language enclave initialization.

System actionThe service returns, without performing the function ofthe service.

Programmer responseMove the use of this service to within enclaveinitialization event handling, or, determine the properevent to be using at the point where you are trying toinvoke this event.


CEE3359E The module or language list is notsupported in this environment.

ExplanationThe module or language list is not supported in thisenvironment.

System actionThe function is not performed.

Programmer responseUse a supported module or language list for thisservice when running on this version of the operatingsystem.


CEE3360S The stack frame was not found onthe call chain.

ExplanationThe stack frame parameter passed to the CEE3SMSCWI did not point to a valid stack frame on the callchain.

System actionThe CEE3SMS CWI returns without allocating amachine state control block.



CEE3361W A nested enclave completed withan unhandled condition of severitytwo or greater.

ExplanationIf a nested enclave is created due to an SVC-assistedlinkage (LINK on VM or MVS, CMSCALL on VM),and it subsequently abends or program checks, or itsoftware-signals a condition of severity two or greater,then condition token CEE391 was signaled in thecreator of the nested enclave.

System actionIf the signal of the CEE391 condition is not handled,execution continues at the instruction after the LINK orCMSCALL.

Programmer responseCheck condition token CEE391.


CEE3362S No main or fetchable procedure orfunction was present within theload module.

ExplanationThe load module contained neither a main procedure/function nor a fetchable procedure/function.


Programmer responseCorrect the load module.



CEE3363S A second main procedure orfunction was entered withoutcrossing a nested enclaveboundary.

ExplanationA direct call was made to a main procedure. Theprogram should have been loaded and/or calledusing a defined language construct like fetch() orsystem().


Programmer responseCorrect the load module.


CEE3364W The enclave name was truncatedby the enclave naming serviceduring initialization.

ExplanationThe enclave naming service was used by the languagein which the main program was written during enclaveinitialization. It was passed a name longer than 32characters.

System actionThe truncated name is used as the enclave name.



CEE3365S The enclave naming servicewas called, but not duringenclave initialization, or not bya language run-time componentcorresponding to the MAINprogram.

ExplanationThe enclave naming service was used by the languagein which the main program was written during enclaveinitialization. It was used in an illegal manner.




CEE3367E An attempt was made to createa nested enclave for a 31-bitprogram module_name found inAMODE 64 environment.

ExplanationOnly AMODE 64 programs are supported in nestedenclaves under the AMODE 64 environment.

System actionNone.

Programmer responseDo not attempt to create a nested enclave foran AMODE 31 program under the AMODE 64environment. Instead, recompile the target program ofthe nested enclave for the 64-bit environment.


CEE3370W The program invocation namecould not be found, and thereturned name was blank.

ExplanationCEEBGIN could not determine the name under whichthe program was invoked.





CEE3380W The target load module wasnot recognized by LanguageEnvironment.

ExplanationThe language list could not be returned because thetarget load module was not recognized. A value of zerowas returned.

System actionProcessing continues. No system action is performed.



CEE3400W The condition name was notrecognized and the value of thecondition token was undefined.

ExplanationCEEQFBC was passed a condition name that couldnot be translated into a corresponding LanguageEnvironment condition token.



Symbolic Feedback CodeCEE3A8

CEE3401W The condition token was notrecognized and the value of thecondition name was undefined.

ExplanationCEEBFBC was passed a condition token that could notbe translated into a corresponding condition name.



Symbolic Feedback CodeCEE3A9

CEE3402E The condition token passed wasinvalid and the value of thecondition name was undefined.

ExplanationCEEBFBC was passed a condition token that wasdetermined to be invalid and could not to be translatedinto a corresponding condition name.



Symbolic Feedback CodeCEE3AA

CEE3403E The input parameter func_code isincorrect.

ExplanationThe input for the parameter func_code was notrecognized.

System actionThe requested function was not performed.

Programmer responseUse a valid function code in the parameter list.

Symbolic Feedback CodeCEE3AB

CEE3404I The service routine with specifiedwork area has already beenenabled.


ExplanationThe requested service routine with a specified workarea was already successfully enabled.


Programmer responseNone. The service routine with the specified work areawas already enabled.

Symbolic Feedback CodeCEE3AC

CEE3405I The service routine with specifiedwork area does not exist or hasalready been disabled.

ExplanationThe requested service routine with a specified workarea was already disabled or was never enabled.


Programmer responseIf a service routine with a specific work area wasalready disabled or was never enabled, do not disableit. Instead, do not take any action.

Symbolic Feedback CodeCEE3AD

CEE3406S The service failed to allocatestorage.

ExplanationCEERCB_ZGETST or CEEVGTST failed when allocatingstorage.


Programmer responseIf necessary, increase the region size and retry therequest. If you need more information, contact yourservice representative.

Symbolic Feedback CodeCEE3AE

CEE3407S The service failed to free storage.

ExplanationCEERCB_ZFREEST or CEEVFRST failed when freeingstorage.



Symbolic Feedback CodeCEE3AF

CEE3408E The maximum number of uniquepairs of service routines withspecified work areas has beenreached.

ExplanationThe maximum number of supported unique pairs ofservice routines with specified work areas is 20 overa region lifetime, including both enabled and disabledroutines.


Programmer responseTry to reduce the number of service routines withspecified work areas.

Symbolic Feedback CodeCEE3AG

CEE3424S CEE3SMO was called from outsidea user-written condition handler.

ExplanationCEE3SMO can only be called from within a user-written condition handler.



Programmer responseOnly code calls to CEE3SMO from within user-writtencondition handlers.


CEE3425S Severity 0 or 1 condition wassignaled with CEESGLN.

ExplanationThe caller of CEESGLN signaled a severity 0 or 1condition; however, resumption is never allowed for acondition signaled from CEESGLN.

System actionThe condition is changed to CEE3B1 and, if unhandled,the enclave is terminated.

Programmer responseDo not signal severity 0 and 1 conditions fromCEESGLN. Use CEESGL when signaling a severity 0 and1 conditions.


CEE3426S There was an invalid request tofix-up and resume a condition.

ExplanationThere was a request to fix-up and resume from a user-written condition handler and either (1) the resumecursor was moved, or (2) the condition was signaledfrom CEESGLN or from CEESGL without a feedbackcode. The resume cursor can not be moved by a user-written condition handler if fix-up and resume behavioris desired. Conditions signaled from CEESGLN orfrom CEESGL without a feedback code can not beresumed without moving the resume cursor. Theoriginal condition is indicated in the next message inthe message file.

System actionThe condition is promoted to CEE3B2 and, ifunhandled, the enclave is terminated.

Programmer responseA user-written condition handler must move theresume cursor and return a result code of 10 (Resume)

in order to resume a condition signaled by CEESGLN orby CEESGL without a feedback code.


CEE3427S A user-written condition handlerpromoted a condition signaled byCEESGLN to severity 0 or 1.

ExplanationThe condition handling mechanism allows conditionhandlers to promote their current condition and thenhandle new ones. If a severity 2 or above conditionsignaled by CEESGLN was promoted to a 0 or 1condition, the purpose of CEESGLN would be violated- programs can never resume following a call toCEESGLN. (Language Environment allows severity 0or 1 conditions to resume.) Note that the originalcondition is indicated in the next message in themessage file.

System actionThe condition is promoted to CEE3B3 and if unhandledthe enclave is terminated.

Programmer responseUser-written condition handlers must not promoteconditions that are not allowed to resume to severity 0or 1.


CEE3428S Condition signaled by CEESGLNis not enabled by a language run-time component.

ExplanationSome conditions are disabled by a language run-time component. For example Fixed Point Overflowconditions in COBOL are ignored and the applicationis resumed. Such a condition must not be signaled byCEESGLN. Note that the original condition is indicatedin the next message in the message file.

System actionThe condition is promoted to CEE3B4 and if unhandledthe enclave is terminated.


Programmer responseDo not use CEESGLN to signal a condition from alanguage that does not enable the condition.


CEE3429S Move resume cursor relative isnot permitted in a user-writtencondition handler registered withthe USRHDLR run-time option.

ExplanationYou can register a user-written condition handler atstack frame 0 with the USRHDLR run-time option. Themove resume cursor relative (CEEMRCR) service wasnot permitted at stack frame 0.


Programmer responseRemove all references to CEEMRCR in user-writtencondition handlers registered with the USRHDLR run-time option.


CEE3449S An internal message services erroroccurred during termination.

ExplanationA message service was called to perform a serviceduring termination, but the service could not becompleted because certain resources were no longeravailable.



Symbolic Feedback CodeCEE3BP

CEE3450E Only one language was on thestack when a POP request wasmade to CEE3LNG. The currentlanguage was returned in thedesired language parameter.

ExplanationCEE3LNG cannot POP since the resulting stack wasempty.

System actionThe current language is returned in thedesired_language parameter and the stack remainsunchanged.


Symbolic Feedback CodeCEE3BQ

CEE3451S The desired language desired-language for the PUSH or SETfunction for CEE3LNG was invalid.No operation was performed.

ExplanationThe desired_language parameter was not a valid 3-character national language id.


Programmer responseProvide a valid desired_language parameter. A listof the valid national languages is provided in z/OSLanguage Environment Programming Reference.

Symbolic Feedback CodeCEE3BR

CEE3452S The function function specified forCEE3LNG was not recognized. Nooperation was performed.

ExplanationThe function parameter must be a fullword binary 1, 2,3, or 4.



Programmer responseProvide a fullword binary 1, 2, 3, or 4 in the functionparameter.

Symbolic Feedback CodeCEE3BS

CEE3454S The function requested inCEE3LNG failed because at leastone of the high-level languages didnot accept the change from thefunction.

ExplanationAn internal error prevented the requested change frombeing made.



Symbolic Feedback CodeCEE3BU

CEE3455E Only one country code was on thestack when a POP request wasmade to CEE3CTY. The currentcountry code was returned in thecountry code parameter.

ExplanationCEE3CTY cannot POP the stack since the resultingstack was empty.

System actionThe current country code is returned in thecountry_code parameter and the stack remainsunchanged.


Symbolic Feedback CodeCEE3BV

CEE3456S The country code country-codefor the PUSH or SET functionfor CEE3CTY was invalid. Nooperation was performed.

ExplanationThe country_code parameter was not a valid 2-character country code.


Programmer responseProvide a valid country_code parameter. A list of thevalid country codes is provided in z/OS LanguageEnvironment Programming Reference.

Symbolic Feedback CodeCEE3C0

CEE3457S The function function specified forCEE3CTY was not recognized. Nooperation was performed.

ExplanationThe function parameter must be a fullword binary 1, 2,3, or 4.


Programmer responseProvide a fullword binary 1, 2, 3, or 4 in the functionparameter.


CEE3458E The country code country_codewas invalid for CEE3MC2.The default currency symbolcurrency_symbol was returned. Nointernational currency symbol wasreturned.


ExplanationThe country_code parameter was not a valid 2-character country code. The default currency symbolwas returned. No international currency symbol wasreturned.

System actionThe default currency symbol is returned. Nointernational currency symbol is returned.

Programmer responseProvide a valid country_code parameter. A list of thevalid country codes is provided in the z/OS LanguageEnvironment Programming Reference.


CEE3459S The function requested inCEE3CTY failed because at leastone of the high-level languages didnot accept the change from thefunction.

ExplanationThe function requested failed because one of the high-level languages did not accept the change.


Programmer responseAn internal error prevented the requested change frombeing made. Contact your service representative.


CEE3460E The decimal separator'decimal_separator' was truncatedand was not defined in CEE3MDS.

ExplanationThe decimal_separator parameter must be a 2-character field. The resulting decimal separator mightnot be valid. The decimal separator was left-justifiedand padded on the right with a blank if necessary.

System actionThe decimal separator is truncated and placed into thegiven parameter.

Programmer responseProvide a 2-character decimal_separator parameter.


CEE3461E The country code country_codewas invalid for CEE3MDS.The default decimal separator'decimal_separator' was returned.

ExplanationThe country_code parameter was not a valid 2-character country code. The default decimal separatorwas returned.

System actionThe default decimal separator is returned.



CEE3462E The currency symbol'currency_symbol' was truncatedand was not defined in CEE3MCS.

ExplanationThe currency_symbol parameter must be a 2-characterfield. The resulting currency symbol might not be valid.The currency symbol was left-justified and padded onthe right with a blank if necessary.

System actionThe currency symbol is truncated and placed into thegiven parameter.

Programmer responseProvide a 2-character currency_symbol parameter.



CEE3463E The country code country_codewas invalid for CEE3MCS.The default currency symbol'currency_symbol' was returned.

ExplanationThe country_code parameter was not a valid 2-character country code. The default currency symbolwas returned.

System actionThe default currency symbol is returned.



CEE3464E The thousands separator'thousands_separator' wastruncated and was not defined inCEE3MTS.

ExplanationThe thousands_separator parameter must be a 2-character field. The resulting thousands separatormight not be valid. The thousands separator wasleft-justified and padded on the right with a blank ifnecessary.

System actionThe thousands separator is truncated and placed intothe given parameter.

Programmer responseProvide a 2-character thousands_separator parameter.


CEE3465E The country code country_codewas invalid for CEE3MTS.The default thousands

separator 'thousands_separator'was returned.

ExplanationThe country_code parameter was not a valid 2-character country code. The default thousandsseparator was returned.

System actionThe default thousands separator is returned.



CEE3466E The date picture stringdate_pic_string was truncated andwas not defined in CEEFMDA.

ExplanationThe date_pic_string parameter must be an 80-character field. The resulting date_pic_string mightnot be valid. The date_pic_string was left-justified andpadded on the right with a blank if necessary.

System actionThe date_pic_string is truncated and placed into thegiven parameter.

Programmer responseProvide an 80-character date_pic_string parameter.

Symbolic Feedback CodeCEE3CA

CEE3467E The country code country_codewas invalid for CEEFMDA. Thedefault date picture stringdate_pic_string was returned.

ExplanationThe country_code parameter was not a valid 2-character country code. The default date picture stringwas returned.


System actionThe default date picture string is returned.


Symbolic Feedback CodeCEE3CB

CEE3468E The time picture stringtime_pic_string was truncated andwas not defined in CEEFMTM.

ExplanationThe time_pic_string parameter must be an 80-character field. The resulting time_pic_string mightnot be valid. The time_pic_string was left-justified andpadded on the right with a blank if necessary.

System actionThe time_pic_string is truncated and placed into thegiven parameter.

Programmer responseProvide an 80-character time_pic_string parameter.

Symbolic Feedback CodeCEE3CC

CEE3469E The country code country_codewas invalid for CEEFMTM. Thedefault time picture stringtime_pic_string was returned.

ExplanationThe country_code parameter was not a valid 2-character country code. The default time picture stringwas returned.

System actionThe default time picture string is returned.


Symbolic Feedback CodeCEE3CD

CEE3470E The date and time stringdatetime_str was truncated andwas not defined in CEEFMDT.

ExplanationThe datetime_str parameter must be an 80-characterfield. The resulting datetime_str might not be valid. Thedatetime_str was left-justified and padded on the rightwith a blank if necessary.

System actionThe datetime_str is truncated and placed into the givenparameter.

Programmer responseProvide an 80-character datetime_str parameter.

Symbolic Feedback CodeCEE3CE

CEE3471E The country code country_codewas invalid for CEEFMDT. Thedefault date and time picturestring datetime_str was returned.

ExplanationThe country_code parameter was not a valid 2-character country code. The default date and timestring was returned.

System actionThe default date and time string is returned.


Symbolic Feedback CodeCEE3CF

CEE3472S An internal message services erroroccurred while getting storage forthe message inserts.


ExplanationInsufficient heap storage was available to completemessage services.

System actionNo message insert area is created.

Programmer responseIf possible, free unneeded heap storage or contactyour service representative.

Symbolic Feedback CodeCEE3CG

CEE3473S An internal message services erroroccurred while processing theinserts for this message.

ExplanationCorrupted storage was encountered when attemptingto initialize a message insert block.



Symbolic Feedback CodeCEE3CH

CEE3475S An internal message services erroroccurred while freeing the insertarea.

ExplanationCorrupted storage was encountered when attemptingto free a message insert block.



Symbolic Feedback CodeCEE3CJ

CEE3476S An internal message services erroroccurred while freeing storage forthe message inserts.

ExplanationMessage services detected a heap storage freeingfailure.



Symbolic Feedback CodeCEE3CK

CEE3480S An internal message services erroroccurred while processing theinserts for a message.

ExplanationMessage services detected an insert error whileformatting a message.



Symbolic Feedback CodeCEE3CO


ExplanationCorrupted storage was encountered when attemptingto process a message insert block.




Symbolic Feedback CodeCEE3CP


ExplanationAn invalid insert was encountered when attempting toprocess a message insert block.



Symbolic Feedback CodeCEE3CQ

CEE3484E A message could not bewritten to ddname because themessage length of message_lengthexceeded the allowable maximumof max-message-length.

ExplanationThe message could not be written to ddname data setbecause message services will not process a messagewhose length is greater than max-message-length.

System actionThe message is not written.

Programmer responseReduce the size of the message or divide it intosections of acceptable length.

Symbolic Feedback CodeCEE3CS

CEE3485S An internal message serviceserror occurred while locatingthe message number within amessage file.

ExplanationThe message library for the given message numberwas located and loaded, but the message numbercould not be found within the library.

System actionThe given message library is loaded, but no otheraction is performed.


Symbolic Feedback CodeCEE3CT

CEE3486S An internal message serviceserror occurred while formatting amessage.

ExplanationCorrupted storage was encountered when attemptingto process a message insert block.



Symbolic Feedback CodeCEE3CU

CEE3487S An internal message serviceserror occurred while locatinga message number within theranges specified in the repository.

ExplanationThe message number could not be found within theranges in the message_library_table.




Symbolic Feedback CodeCEE3CV


ExplanationAn invalid internal message buffer length was detectedwhile formatting a message.



Symbolic Feedback CodeCEE3D0

CEE3489S An internal message services erroroccurred while getting storagenecessary to format a message.

ExplanationNo heap storage was available to get storage neededto complete the formatting of a message.




CEE3490S An internal message services erroroccurred while attempting to writea message.

ExplanationThe given ddname or destination was not valid or wasnot available.




CEE3491S An internal message services erroroccurred while getting storage.

ExplanationNo heap storage was available to get storage neededto write out a message.




CEE3492S An internal message services erroroccurred while attempting to writea message.

ExplanationAn error was detected while trying to OPEN, WRITE, orCLOSE a given ddname or destination.





CEE3493W An internal message services erroroccurred while attempting to closethe message file.

ExplanationLanguage Environment could not close the specifiedddname, because Language Environment either didnot own it, or the file was not currently open.




CEE3494S An internal message services erroroccurred while attempting to closethe message file.

ExplanationAn error was detected while trying to CLOSE the givenddname.





ExplanationAn error preventing the completion of messageformatting was detected.




CEE3496I An internal message serviceserror occurred while formatting amessage.

ExplanationAn internal error was detected while locating theinserts for a message.




CEE3497E The message file was discoveredto have an insufficient LRECL oftoo-small.

ExplanationThe message file cannot have an LRECL less than14. This was to allow for the message number and 4characters of text per line.

System actionThe message file LRECL is forced to the default LRECLvalue.

Programmer responseSpecify an LRECL of 14 or greater.


CEE3498I The message file was alreadyopen.


ExplanationA request to open the message file via CEEOPMF couldnot be completed because it was already open.



Symbolic Feedback CodeCEE3DA

CEE3499E The message file was unable to beopened.

ExplanationA request to open the message file via CEEOPMF couldnot be completed.


Programmer responseEnsure that the ddname to used for the message file isa valid name, and the data set is usable.

Symbolic Feedback CodeCEE3DB

CEE3500S Not enough storage was availableto load module-name.

ExplanationNot enough storage was available to load therequested module into virtual memory.

System actionModule is not loaded. The application might abend.

If this was a C dllload() or dlopen() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, wereavailable through the _EDC_DLL_DIAG environmentvariable.

If this was an explicit C dlopen() request, thiserror could also be returned to the caller through asubsequent call to the C dlerror() function.

If this was a DLL load or open request, a CEEDLLF DLLfailure control block was populated with further DLLerror diagnostics.

Programmer responseEnsure that the region size is sufficient to run theapplication. If necessary, delete the modules thatthe application does not need or delete free unusedstorage, and retry the load request. The module namespecified in the message might be truncated fordisplay purposes.

Symbolic Feedback CodeCEE3DC

CEE3501S The module module-name was notfound.

ExplanationThe system could not find the load module whosename was specified on the parameter list to theLanguage Environment load service, in the indicatedlibrary (job library or link library).





Programmer responseMake sure the requesting program name was notincorrectly modified. Make sure that the indicatedlibrary is correct in the job step. Correct the error,and execute the job step again. The module namespecified in the message might be truncated fordisplay purposes.


Symbolic Feedback CodeCEE3DD

CEE3502S The module name module-namewas too long.

ExplanationThe module name length was greater than the namelength supported by the underlying operating system.

System actionName length is truncated to the name lengthsupported by the underlying operating system. Therequested module might or might not be loaded.




Programmer responseCorrect the module name length and execute the jobstep again. The module name specified in the messagewas truncated for display purposes.

Symbolic Feedback CodeCEE3DE

CEE3503S The load request for modulemodule-name was unsuccessful.

ExplanationThe system could not load the load module.

System actionModule was not loaded. The application might abend.

If this was a C dllload() or dlopen() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message wass sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,

and turning off _EDC_DLL_DIAG diagnostics, wereavailable through the _EDC_DLL_DIAG environmentvariable.



Programmer responseCheck the original abend from the operating systemand refer to the underlying operating system messagemanual for explanation and programer's response.The module name specified in the message might betruncated for display purposes.

Symbolic Feedback CodeCEE3DF

CEE3504S The delete request for modulemodule-name was unsuccessful.

ExplanationThe load module might already have been deleted orwas never loaded.


Programmer responseMake sure the requesting module name is notincorrectly modified.

Symbolic Feedback CodeCEE3DG

CEE3505S The library vector table (LIBVEC)descriptor module module-namecould not be loaded.

ExplanationDuring LIBVEC initialization the library vector tabledescriptor module could not be found.

System actionLIBVEC initialization is not performed.


Programmer responseMake sure you passed the name of the libraryvector table (LIBVEC) descriptor rather than the entryaddress. Make sure the name was not incorrectlymodified and the indicated library (job library or linklibrary) is correct.

Symbolic Feedback CodeCEE3DH

CEE3506S The library packaged subroutinemodule module-name could not beloaded.

ExplanationThe system could not find the load module whosename was specified in the library vector table (LIBVEC)descriptor module in the indicated library (job libraryor link library).

System actionModule is not loaded and LIBVEC initialization is notperformed.

Programmer responseMake sure the requesting program name was notincorrectly modified. Make sure that the indicatedlibrary is correct in the job step. Correct the error, andexecute the job step again.

Symbolic Feedback CodeCEE3DI

CEE3507S Not enough storage was availablefor the library vector table(LIBVEC) table-name.

ExplanationInsufficient storage was available to build the LIBVEC.

System actionNo storage is allocated for the LIBVEC. LIBVECinitialization did not complete.

Programmer responseIf necessary, free available storage and retry LIBVECinitialization.

Symbolic Feedback CodeCEE3DJ

CEE3508S The number of library packagedsubroutines specified in thedescriptor module module-nameexceeded the maximum of 256library packages. No librarypackages were loaded.

ExplanationThe maximum number of library packages supportedis 256.

System actionLIBVEC initialization did not complete.

Programmer responseRepackage the library routines so that the numberof library packages does not exceed the maximumsupported.

Symbolic Feedback CodeCEE3DK

CEE3509S The number of library vector slotsspecified in the descriptor modulemodule-name either exceeded1024 or was less than 1.

ExplanationA minimum of 1 library routine entry name wasrequired to build the library vector table. A maximumof 1024 library routines entry names is allowed in aLIBVEC.

System actionLIBVEC initialization did not complete.

Programmer responseIf library vector slots exceed the maximum, you mighthave to build more than one LIBVEC.

Symbolic Feedback CodeCEE3DL

CEE3510S The module module-name is amember of the library packagedsubroutine module-name andcould not be deleted.


ExplanationLibrary package subroutines are not allowed to bedeleted.

System actionModule not deleted.

Programmer responseCorrect your program so that it does not request alibrary package subroutine be deleted.

Symbolic Feedback CodeCEE3DM

CEE3511S The function code function-codewas invalid.

ExplanationValid functions codes for the verify library vectorsubroutine are delete and load.


Programmer responseMake sure the function code passed to the verifylibrary vector subroutine is delete/load. Correct theprogram and execute job step again.

Symbolic Feedback CodeCEE3DN

CEE3512S An z/OS UNIX file system load ofmodule module-name failed. Thesystem return code was return-code; the reason code was reason-code.

ExplanationThe callable service BPX1LOD failed while attemptingto load module module-name from the z/OS UNIX filesystem. The system return and reason codes werereturned.





Programmer responseSee z/OS UNIX System Services Messages and Codesfor the appropriate action to take for this return codeand reason code. Consult with your system supportpersonnel if necessary. The module name specifiedin the message may have been truncated for displaypurposes.

Symbolic Feedback CodeCEE3DO

CEE3513S The library vector table (LIBVEC)table-name could not beterminated.

ExplanationLIBVEC termination failed due to an inability to deletelibrary subroutines or free the storage obtained for theLIBVEC.

System actionLIBVEC termination did not complete.


Symbolic Feedback CodeCEE3DP

CEE3514C An internal error, UnknownOperating System, was detected.

ExplanationThe underlying operating system was unsupported inLanguage Environment.



Programmer responseLanguage Environment runs under the control of, orin conjunction with, the following operating systems/subsystems: MVS/ESA, CICS/ESA, IMS/ESA®, Db2®,SQL/DS, DFSORT, ISPF, and TSO/E.

Symbolic Feedback CodeCEE3DQ

CEE3515I No modules were loaded.

ExplanationNo application load modules have been loaded viaLanguage Environment load service in the currentapplication.



Symbolic Feedback CodeCEE3DR

CEE3517S The dynamic allocation of themsgfile was not successful. Thereason code was reason-code.

ExplanationLanguage Environment attempted to dynamicallyallocate a ddname for the msgfile. However, theallocation was not successful.


Programmer responseUse the error reason code to determine why thedynalloc service did not complete successfully.

Symbolic Feedback CodeCEE3DT

CEE3518S The module module-name was notfound in an authorized library

ExplanationAn authorized program requested the load of a modulethat could not be found in an authorized library orconcatenation of libraries.


If this was a C dllload() or dlopen() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and the turning off _EDC_DLL_DIAG diagnostics, wereavailable through the _EDC_DLL_DIAG environmentvariable.



Programmer responseIf the requested module can not be found, makesure the module exists in a system or user-definedauthorized library. Correct the error, and run the jobstep again. The module name specified in the messagemight be truncated for display purposes.

Symbolic Feedback CodeCEE3DU

CEE3519S The version specified in theCEEFTCH control block passedto the CEEFETCH macro is notsupported.

ExplanationThe version specified in the CEEFTCH control blockpassed to the CEEFETCH macro is not supported.



Programmer responseSee the CEEFTCH section in the z/OS LanguageEnvironment Programming Guide for supportedversions of the CEEFTCH control block.

Symbolic Feedback CodeCEE3DV

CEE3530S The service was invoked for a loadmodule.

ExplanationThe CEEPPOS service was invoked for a load module.Only program objects are supported. No action wastaken.

System actionUnless the condition is handled the default action is toterminate the enclave.



CEE3531S The entry point was notrecognized by LanguageEnvironment.

ExplanationThe CEEPPOS service was invoked and LanguageEnvironment was not able to recognize the entry pointstyle. Only Language Environment enabled entry pointstyles are supported for program objects. No actionwas taken.




CEE3532S The requested class does not existin the program object.

ExplanationThe CEEPPOS service was invoked. If this is anOBTAIN for class C_WSA then this indicates thatthe program object does not have writable static. Ifthis is a LOCATE for class C_@@DLLI, C_@@STINITor C_@@PPA2 then this indicates that the programobject does not contain the class. No action was taken.




CEE3533S The service invoked a systemfunction which was unsuccessful.The system return code wasreturn_code and the system reasoncode was reason_code.

ExplanationThe CEEPPOS service invoked program managementsystem service for a program object. The systemreturn code and reason code were returned.




CEE3534S The requested function is notsupported.

ExplanationThe CEEPPOS service was invoked with a function thatis not recognized. No action was taken.





CEE3535S The requested class_name is notsupported, or a required inputvalue for the specified class_namewas not correctly specified.

ExplanationThe CEEPPOS service was invoked with class_namethat is not recognized, or the required input for thefunction with class_name CEE_ALL is incorrect. Noaction was taken.


Programmer responseIf your application is involving CEEPPOS, then checkthat the class_name specified is correct for thefunction being used. If you are using a function thataccepts the class_name CEE_ALL, make sure youspecify the class_address and class_size correctly.Otherwise, contact your service representative.


CEE3536S Not enough storage was availablefor the WSA.

ExplanationThe CEEPPOS service was invoked to OBTAIN the WSAand storage was not available to load the WSA intovirtual memory. No action was taken.




CEE3537S The request to release the WSAwas unsuccessful.

ExplanationThe CEEPPOS service was invoked to RELEASE theWSA and the system could not release the WSAbecause the class_address was not valid.



Symbolic Feedback CodeCEE3EH

CEE3538S The request to refresh the WSAwas unsuccessful.

ExplanationThe CEEPPOS service was invoked to REFRESH theWSA and the system could not refresh the WSAbecause the class_address was not valid.



Symbolic Feedback CodeCEE3EI

CEE3539S The load request for programobject module-name wasunsuccessful for the current levelof CICS.

ExplanationThe load request for module, module-name resulted inloading a program object. The load service does notsupport loading a program object for the current levelof CICS.


System actionThe module is not loaded. Unless the condition ishandled, the default action is to terminate the enclave.

Programmer responseRebuild the module using the Language EnvironmentPrelinker Utility and reexecute.

Symbolic Feedback CodeCEE3EJ

CEE3540S The load request for programobject module-name wasunsuccessful.

ExplanationThe load request for module, module-name resulted inloading a program object. The load service does notsupport loading a program object.

System actionThe module is not loaded. Unless the condition ishandled, the default action is to terminate the enclave.

Programmer responseRebuild the module using the Language EnvironmentPrelinker Utility and reexecute.

Symbolic Feedback CodeCEE3EK

CEE3541S A Writeable Static Area (WSA)associated with the entry pointwas not found.

ExplanationThe CEEPFWSA service was invoked and LanguageEnvironment was not able to find an executablemodule containing the specified entry point. A searchis made of the executable module containing main (ifpresent), any fetched, dynamically-called, PIPI-loadedmodules, CEEFETCHed modules and any loaded DLLs.


Programmer responseVerify that the entry point passed to CEEPFWSA isa valid C/370 or Language Environment style entrypoint contained within a currently loaded executablemodule. Contact your service representative.

Symbolic Feedback CodeCEE3EL

CEE3542S Unable to find a valid Entry Pointor PPA1 or PPA2 for this DSA.

ExplanationDSA pointer, DSA format and Entry Point address arethe required parameters for the CEEYEPAF callableservice. They have to be passed to the CEEYEPAF CWI.PPA1 and PPA2 pointers are optional parameters.But if the PPA2 pointer is passed to the CEEYEPAFCWI, then the PPA1 pointer has to be passed to theCEEYEPAF CWI as well.

System actionThe request was unsuccessful. The address of theEntry Point or PPA1 or PPA2 is not established.

Programmer responsePass the correct parameters to the CEEYEPAF callableservice. PPA1 pointer has to be passed to theCEEYEPAF CWI, if PPA2 pointer is passed to it.

Symbolic Feedback CodeCEE3EM

CEE3543E Requested optional field not foundin the passed PPA1.

ExplanationThe optional field parameter passed to the CEEYPPAFcallable service doesn't exist in the passed PPA1structure.

System actionThe request was unsuccessful. The address of theoptional field is evaluated to 0.

Programmer responsePass the correct optional name parameter to theCEEYPPAF CWI.


Symbolic Feedback CodeCEE3EN

CEE3544E Optional field requested is notvalid ( 1 - 9 ).

ExplanationThe valid value for the optional field parameter passedto the CEEYPPAF callable service is from number 1 tonumber 9.

System actionThe request was unsuccessful. The address of theoptional field is evaluated to 0.

Programmer responsePass the valid number as the optional field parameterto the CEEYPPAF callable service.

Symbolic Feedback CodeCEE3EO

CEE3545E Unable to verify the passed PPA1as valid for XPLINK.

ExplanationThe PPA1 parameter passed to the CEEYPPAF callableservice is not a valid XPLINK PPA1.

System actionThe request was unsuccessful. The address of theoptional field is not established.

Programmer responsePass the XPLINK PPA1 parameter to the CEEYPPAFcallable service.

Symbolic Feedback CodeCEE3EP

CEE3546E An error occurred whileattempting to find the previousDSA.

ExplanationA program check occurred in the unwind process.


Programmer responseMake sure the input DSA is valid. Verify the DSA formatis correct.

Symbolic Feedback CodeCEE3EQ

CEE3547E The DSA physical callee wasrequested and the physical calleeformat was not.

ExplanationCallable service CEEYDSAF requires the physical calleeformat when the physical callee parameter is passed.


Programmer responseMake sure the physical callee format is passed ifphysical callee is requested.

Symbolic Feedback CodeCEE3ER

CEE3548E The callable service was passed aDSA format of -1 and was unableto determine the format of thepassed DSA.

ExplanationUnable to determine whether the DSA is up or downformat.

System actionThe callable service will return feedback. If feedbackis not requested, a severity 1 condition will beraised. If the condition remains unhandled, processingcontinues.

Programmer responseVerify the DSA is valid.


Symbolic Feedback CodeCEE3ES

CEE3549S The service was invoked fora program object that containssome combination XPLINK andNOXPLINK-compiled parts.

ExplanationA Language Environment service found a programobject that contains a combination of AMODE 64,XPLINK, and NOXPLINK-compiled parts. You cannotmix any combination of AMODE 64, XPLINK andNOXPLINK-compiled parts in the same programobject.

System actionIf the Language Environment service that detectedthe condition was passed a feedback code parameter,then the feedback code representing this message isreturned. Otherwise the enclave is terminated.

Programmer responseRebind the program object after recompiling the partsso that they are all compiled either AMODE 64, XPLINKor NOXPLINK. Alternatively, you can split the programobject into separate DLLs, one containing AMODE 64compiled parts, one containing XPLINK-compiled partsand the other containing NOXPLINK compiled parts.Then each of these DLLs would be bound with theDLL side deck of the other. Refer to z/OS XL C/C++Programming Guide for more details on DLLs.

Symbolic Feedback CodeCEE3ET

CEE3550S DLL dll-name does not contain aCEESTART CSECT.

ExplanationThe application is attempting to load DLL dll-nameimplicitly or explicitly, but the CEESTART CSECTcannot be located within it.

System actionIf this was an implicit DLL reference, the condition issignaled. If the condition is not handled, the defaultaction is to terminate the enclave.

If this was an explicit DLL Load (CEEPLDE) or DLL Open(CEEPOPDL) request, the feedback code is returned tothe caller.



A CEEDLLF DLL failure control block was populatedwith further DLL error diagnostics.

Programmer responseMake sure that when you generate the DLL, it containsa CEESTART CSECT.

Symbolic Feedback CodeCEE3EU

CEE3551S DLL dll-name does not contain anyC functions.

ExplanationDLL dll-name does not contain any C functions.

System actionThe condition is signaled. If the condition is nothandled, the default action is to terminate the enclave.

If the _EDC_DLL_DIAG environment variable is not setto QUIET, the error message is sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, areavailable through the _EDC_DLL_DIAG environmentvariable.

A CEEDLLF DLL failure control block is populated withfurther DLL error diagnostics.

Programmer responseMake sure that you are loading the correct module,and that the DLL is built correctly.

Symbolic Feedback CodeCEE3EV

CEE3552S DLL dll-name does not export anyvariables or functions.


ExplanationDLL dll-name does not export any variables orfunctions. Either the definition side-deck supplied toyour application is incorrect, or the DLL is generatedincorrectly.




Programmer responseEnsure that the DLL was built properly.

1. Specify #pragma export in your source or compilewith EXPORTALL compiler option.

2. Compile with DLL, RENT, and LONGNAME compileroptions.

3. Ensure that the DLL was built properly.


CEE3553S DLL dll-name is part of a circularlist.

ExplanationA deadlock condition was discovered while processinga DLL load request for DLL dll-name. The deadlockcondition exists because the DLLs that are beingloaded depend on each other. The following situationillustrates a deadlock condition. DLL A has staticconstructors that require objects from DLL B. DLL Bhas static constructors that require objects from DLLA. When DLL A is loaded, its static constructors requireobjects from DLL B. This forces DLL B to be loaded,requiring objects from DLL A. Since the loading of DLLA has not completed, a deadlock condition exists.


Programmer responseRemove the circular list dependency from the DLLs.


CEE3554S There is not enough storage toload DLL dll-name.

ExplanationThere is insufficient storage to satisfy the DLL Load orDLL Open request for DLL dll-name..






Programmer responseIncrease the region size.


CEE3555S A call was made from aNOXPLINK-compiled applicationto an XPLINK-compiled exportedfunction in DLL dll-name and theXPLINK(ON) runtime option wasnot specified.

ExplanationDuring Language Environment initialization, XPLINKresources need to be allocated if any XPLINK-


compiled functions are going to be called during theexecution of the application. Language Environmenttries to detect this by inspecting the attributes ofthe initial program. If the initial program consistsof NOXPLINK-compiled functions that may at somepoint call an XPLINK-compiled function, then theXPLINK(ON) runtime option must be used to indicateto Language Environment initialization that XPLINKresources should be allocated.






Programmer responseSpecify the XPLINK(ON) runtime option.


CEE3556S An internal error was detected, noWSA could be found associatedwith entry point entry-pt.

ExplanationThis is an internal error. Language Environment couldnot find the WSA associated with the caller of a DLLfunction (the entry point in the message is the addressof the caller).




CEE3557S An internal error was detected byLanguage Environment during DLLload.

ExplanationThis is an internal error. Language Environmentcould not complete DLL load processing because anunexpected condition was encountered in the formatof either the DLL or the DLL application.




CEE3558S DLL dll-name does not export anyvariables.

ExplanationThe application made an implicit reference to DLL dll-name. During the load of the DLL, it was determinedthat the application references external variables fromthe DLL. However, the DLL that was loaded does notcontain any exported variables.





Programmer responseEnsure that the DLL indicated in the job library or linklibrary is the correct version, and that it contains theexternal variable.


CEE3559S External variable variable-namewas not found in DLL dll-name.

ExplanationThe application is attempting to refer to externalvariable, variable-name. However, this variable is notdefined in DLL, dll-name.

System actionThe condition is signaled. If the condition is nothandled the default action is to terminate the enclave.





CEE3560S DLL dll-name does not export anyfunctions.

ExplanationThe application made an implicit reference to DLL, dll-name. During the load of the DLL it was determinedthat the application references functions from the DLL.However, the DLL that was loaded does not containany exported functions.




Programmer responseEnsure that the DLL indicated in the job library or linklibrary is the correct version, and that it contains theexternal function.


CEE3561S External function function-namewas not found in DLL dll-name.

ExplanationThe application is attempting to refer to an externalfunction, function-name that is not defined in the DLL,dll-name.






CEE3562S There is not enough storage toobtain a function pointer forexternal function function-name inDLL dll-name.


ExplanationThere is insufficient heap storage to satisfy a QueryDLL Function request for function function-name inDLL dll-name.

System actionIf this was an explicit DLL Query Function (CEEPQDF)request, the feedback code is returned to the caller.

If this was a C dllqueryfn() or dlsym() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, wereavailable through the _EDC_DLL_DIAG environmentvariable.

If this was an explicit C dlsym() request, this errorcould also be returned to the caller through asubsequent call to the C dlerror() function.



Symbolic Feedback CodeCEE3FA

CEE3563S Attempted to load DLL dll-namewhile running C++ destructors.

ExplanationThe application is attempting to load DLL dll-namewhile running C++ destructors.

System actionIf this was an implicit DLL reference, the condition issignaled. If the condition was not handled, the defaultaction is to terminate the enclave.


If this was a C dllload() or dlopen() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and the turning off _EDC_DLL_DIAG diagnostics, wereavailable through the _EDC_DLL_DIAG environmentvariable.



Programmer responseMake sure that you are not referring to DLL variables orfunctions from your C++ destructors.

Symbolic Feedback CodeCEE3FB

CEE3564S DLL constructors or destructorsdid not complete, so DLL dll-namecannot be used.

ExplanationDLL dll-name, which was being loaded or deleted,was in the process of running static constructors ordestructors. However, the process did not complete(probably because the thread was abnormallyterminated). The DLL is left in an indeterminatestate. This error was detected by a thread that wasattempting to load or delete the same DLL, andwas waiting for the constructors or destructors tocomplete.


If this was a C dllload(), dlopen(), dllqueryfn(),dllqueryvar(), dlsym(), dllfree(), or dlclose() requestand the _EDC_DLL_DIAG environment variablewas not set to QUIET, the error message wassent to the Language Environment message file.Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, were available throughthe _EDC_DLL_DIAG environment variable.

If this was an explicit C dlopen(), dlsym(), or dlclose()request, this error could also be returned to the callerthrough a subsequent call to the C dlerror() function.


Programmer responseDetermine the cause of the incomplete constructor ordestructor process. Ensure that the constructors ordestructors are not the cause of the thread terminationthat lead to this condition.


Symbolic Feedback CodeCEE3FC

CEE3565I The input dll-token was NULL.

ExplanationThe dll-token supplied to the DLL Free request is notvalid.

System actionThe request is ignored.

If this was a C dllfree() or dlclose() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, wereavailable through the _EDC_DLL_DIAG environmentvariable.

If this was an explicit C dlclose() request, thiserror could also be returned to the caller through asubsequent call to the C dlerror() function.


Programmer responseYou must request a DLL Load or call the C dlopen()function to initialize a dll-token properly beforeattempting to delete a DLL.

Symbolic Feedback CodeCEE3FD

CEE3566I There are no DLLs to delete.

ExplanationAn attempt was made to delete a DLL, but no DLLs areloaded, or the dll-token passed is inactive.





Programmer response.Ensure that the DLL Free or C dlclose() request isinvoked after the DLL Load or C dlopen() request,respectively, has completed successfully, and that youhave no extra DLL Free or C dlclose() requests usingthis dll-token in your application.

Symbolic Feedback CodeCEE3FE

CEE3567I A logical delete was performed forDLL dll-name , but the DLL was notphysically deleted.

ExplanationThe DLL Free or C dlclose() request completedsuccessfully. DLL dll-name is not physically deletedbecause either there was an implicit DLL Loadperformed against this DLL by the application, ormultiple DLL Load or C dlopen() requests were madefor the DLL.

System actionExecution continues.




Programmer responseIf the DLL was loaded implicitly by referring toan external variable or an external function, it willbe physically deleted by Language Environment atenclave termination. Otherwise, to free or close theDLL, issue a DLL Free or C dlclose() request using theproper dll-token.


Symbolic Feedback CodeCEE3FF

CEE3568I No DLL could be found whichmatched the input dll-token.

ExplanationThe dll-token supplied to the DLL Free or C dlclose()request could not be matched to a DLL loaded by thisapplication.





Programmer responseEnsure that the dll-token supplied to the DLL Free or Cdlclose() request is the same as the one returned fromthe DLL Load or C dlopen() request, respectively, andthat it has not been overwritten.

Symbolic Feedback CodeCEE3FG

CEE3569E The DLL function was not allowedbecause destructors are runningfor the DLL.

ExplanationA DLL Free, Query Variable, Query Function, Cdlclose(), or C dlsym() request was made for a DLL thatis currently running destructors. Since destructors arerunning, the DLL is about to be freed. Further functionrequests using this DLL are not allowed.

System actionIf this was an explicit DLL Free (CEEPFDE), QueryVariable (CEEPQDV), Query Function (CEEPQDF), Close

(CEEPCLDL), or Symbol (CEEPSYDL) request, thefeedback code was returned to the caller.

If this was a C dllqueryfn(), dllqueryvar(), dlsym(),dllfree(), or dlclose() request and the _EDC_DLL_DIAGenvironment variable was not set to QUIET, the errormessage was sent to the Language Environmentmessage file. Other DLL diagnostic options, such asissuing ctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, were available throughthe _EDC_DLL_DIAG environment variable.

If this was an explicit C dlclose() or dlsym() request,this error could also be returned to the caller through asubsequent call to the C dlerror() function.


Programmer responseDo not issue DLL function requests from one threadwhile the DLL is being freed from another thread.

Symbolic Feedback CodeCEE3FH

CEE3570S DLL name dll-name was not valid.

ExplanationEither the DLL name provided as input was null, or thelength of the DLL name was negative.

System actionIf this was an implicit DLL reference, the condition issignaled. If the condition is not handled, the defaultaction is to terminate the enclave. If this was anexplicit DLL Load (CEEPLDE) or DLL Open (CEEPOPDL)request, the feedback code is returned to the caller.





Programmer responseIf this was an implicit DLL reference, make sure thatthe DLL was built correctly. If this was an explicit DLLLoad or C dlopen() request, verify that the DLL namewas specified correctly.

Symbolic Feedback CodeCEE3FI

CEE3571S Storage for writeable static wasnot available for DLL dll-name.

ExplanationNot enough storage was available for allocation ofwriteable static for DLL dll-name.

System actionThe request is ignored. The load module is deletedfrom storage.




Programmer responseEnsure that the REGION size is sufficient to run theapplication. Verify that the storage sizes specified inthe HEAP and STACK run-time options are reasonable,given the region size allocated to the application.Verify that you are using storage options that get yourstorage from above the line, if you can, since you canrun out of storage below the line much more easily.

Symbolic Feedback CodeCEE3FJ

CEE3572I The input dll-token was notavailable for use.

ExplanationThe dll-token supplied to a DLL Query Function, DLLQuery Variable, or C dlsym() request could not be usedbecause one of the following was true:

• the dll-token was null• the dll-token was not valid• the dll-token had been marked inactive as a result of

an explicit DLL Free or C dlclose() request.


If this was a C dllqueryfn(), dllqueryvar(), ordlsym() request and the _EDC_DLL_DIAG environmentvariable was not set to QUIET, the error messagewas sent to the Language Environment messagefile. Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, were available throughthe _EDC_DLL_DIAG environment variable.



Programmer responseEnsure that the proper dll-token is supplied to theDLL request, and that the subject DLL is not freedprematurely.

Symbolic Feedback CodeCEE3FK

CEE3573I Dll dll-name does not export anyfunctions.

ExplanationAn attempt was made to query an external function,but DLL dll-name does not contain any exportedfunctions.


If this was a C dllqueryfn() or dlsym() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, were


available through the _EDC_DLL_DIAG environmentvariable.




Symbolic Feedback CodeCEE3FL

CEE3574I External function function-namewas not found in DLL dll-name.

ExplanationAn attempt was made to query an external function,but function function-name was not found in theexport section of the DLL dll-name.





Programmer responseEnsure that the function name specified on theDLL Query Function request is correct, that the DLLindicated in the job library or link library is the correctversion, and that it contains the external function.

Symbolic Feedback CodeCEE3FM

CEE3575I DLL dll-name does not export anyvariables.

ExplanationAn attempt was made to query an external variable,but DLL dll-name does not contain any exportedvariables.


If this was a C dllqueryvar() or dlsym() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, wereavailable through the _EDC_DLL_DIAG environmentvariable.




Symbolic Feedback CodeCEE3FN

CEE3576I External variable variable-namewas not found in DLL dll-name.

ExplanationAn attempt was made to query an external variable,but variable-name was not found in the export sectionof DLL dll-name.






Programmer responseEnsure that the variable name specified on theDLL Query Variable request is correct, that the DLLindicated in the job library or link library is the correctversion, and that it contains the external variable.

Symbolic Feedback CodeCEE3FO

CEE3577I The external function was notfound in DLL dll-name.

ExplanationAn attempt was made to query an external function inDLL dll-name, but either the function name was null, orthe length of the function name was negative.





Programmer responseEnsure that the function name and length are specifiedcorrectly on the DLL Query Function request.

Symbolic Feedback CodeCEE3FP

CEE3578I The external variable was notfound in DLL dll-name.

ExplanationAn attempt was made to query an external variable inDLL dll-name, but either the variable name was null, orthe length of the variable name was negative.





Programmer responseEnsure that the variable name and length are specifiedcorrectly on the DLL Query Variable request.

Symbolic Feedback CodeCEE3FQ

CEE3579S Attempted to delete DLL dll-namewhile running C++ destructors.

ExplanationThe application is attempting to delete DLL dll-namewhile running C++ destructors.

System actionThe feedback code is returned to the caller.

If this was an explicit DLL Free (CEEPFDE) or DLL Close(CEEPCLDL) request, the feedback code is returned tothe caller.





Programmer responseMake sure that you are not deleting this DLL from yourC++ destructors.

Symbolic Feedback CodeCEE3FR

CEE3580S External variable variable-namewas not found in DLL dll-name.

ExplanationAn attempt was made to reference an externalvariable, but variable-name is not supported as anexported variable from DLL dll-name.




Programmer responseVerify that the side deck representing the DLL iscorrect. Since the DLL does not export this variable,it should not be present in the side deck. Contact thesupplier of the DLL.

Symbolic Feedback CodeCEE3FS

CEE3581S An internal error was detected byLanguage Environment during theload of DLL dll-name.

ExplanationThis is an internal error. Language Environmentcould not complete DLL load processing because an

unexpected condition was encountered in the formatof either the DLL or the DLL application.




If this was an implicit DLL load, or an explicit DLLLoad or Open, a CEEDLLF DLL failure control block waspopulated with further DLL error diagnostics.


Symbolic Feedback CodeCEE3FT

CEE3582S An attempt was made to load anew module containing XPLINK-compiled functions and theXPLINK(ON) runtime option wasnot specified.

ExplanationDuring Language Environment initialization, XPLINKresources need to be allocated if any XPLINK-compiled functions are going to be called during theexecution of the application. Language Environmenttries to detect this by inspecting the attributes ofthe initial program. If the initial program consistsof NOXPLINK-compiled functions that may at somepoint call an XPLINK-compiled function, then theXPLINK(ON) runtime option must be used to indicateto Language Environment initialization that XPLINKresources should be allocated.

System actionIf no feedback code was provided, the condition issignaled. If the condition is not handled, the defaultaction is to terminate the enclave.


If a feedback code was provided, the feedback code isreturned to the caller.


Symbolic Feedback CodeCEE3FU

CEE3583S The transition from standardLanguage Environment linkageconventions to XPLINK linkageconventions could not beperformed. The transition routineCEEVROND could not locate theinformation required to performthe transition or the informationwas not valid.

ExplanationCEEVROND gains control before the routine actuallybeing called. It uses information from the PPA1 of thecalled routine to perform parameter list and returnvalue mapping between the two linkage conventions.On input, it expects register 0 to be the address ofa function descriptor for a routine with an LanguageEnvironment conforming XPLINK entry point.


Programmer responseDepending on the TERMTHDACT run-time option, aCEEDUMP may be available for additional diagnosis.Use the traceback information in the CEEDUMP todetermine the two routines involved.

Symbolic Feedback CodeCEE3FV

CEE3584E The transition from standardLanguage Environment linkageconventions to XPLINK linkageconventions could not beperformed. The transition routineCEEVROND could not determinethe length of the parameter listbeing passed to the called routine.

ExplanationCEEVROND gains control before the routine actuallybeing called. It uses information from the PPA1 of thecalled routine to perform parameter list and returnvalue mapping between the two linkage conventions.The PPA1 indicated that the called routine expects avariable length parameter list. The parameter list wasnot located within a stack frame where its length couldnot be approximated.


Programmer responseDepending on the TERMTHDACT run-time option, aCEEDUMP may be available for additional diagnosis.Use the traceback information in the CEEDUMP todetermine the two routines involved.

Symbolic Feedback CodeCEE3G0

CEE3585E The transition from XPLINKlinkage conventions to LanguageEnvironment standard linkageconventions could not beperformed. The transition routineCEEVRONU could not locate theinformation required to performthe transition or the informationwas not valid.

ExplanationCEEVRONU gains control before the routine actuallybeing called. It uses information from the PPA1 ofthe called routine and from the return address of thecalling routine to perform parameter list and returnvalue mapping between the two linkage conventions.On input, it expects register 5 to be the addressof a function descriptor for or the entry point of aNOXPLINK-compiled routine. This routine must havean Language Environment conforming entry point.


Programmer responseDepending on the TERMTHDACT run-time option, aCEEDUMP may be available for additional diagnosis.


Use the traceback information in the CEEDUMP todetermine the two routines involved.


CEE3586S An attempt was made to resolveDLL references from a NORENTcompiled program that was loadedinto read only storage.

ExplanationWhen a program makes an implicit reference to a DLL,that reference is resolved at run-time by LanguageEnvironment. When the program is non-reentrant ornaturally-reentrant (i.e. NORENT compiled), it doesn'thave a writeable static area (WSA) so the referenceresides within the executable program itself. Thisrequires that the program be loaded into read-writestorage, which is normally the case. However, if theprogram resides in LPA, or was link-edited with theRENT option, then it may get loaded into read-onlystorage.

Note that NOXPLINK compiled programs that callC RTL functions have those calls resolved staticallyvia stubs in the SCEELKED data set, and thereforeprograms that call just C RTL (and other non-DLL)functions and are compiled NOXPLINK would neversee this message.

XPLINK compiled programs have their C RTLreferences resolved dynamically through the C RTLside deck (CELHS003 in SCEELIB), and as suchXPLINK compiled programs call the C RTL using DLLcall mechanisms.




Programmer responseThe traceback in the CEEDUMP will show the loadof a program in process. Ensure that this programresides in read-write storage. This can be done by link-

editing the program NORENT, or STEPLIBing to it inan unauthorized data set. Do not put the program intoLPA.

Optionally, the program can be compiled and link-edited with the RENT option to provide constructedreentrancy, and all writeable references will reside inWSA.


CEE3587S A call was made to a function inthe AMODE 31 DLL dll-name froman AMODE 64 caller.

ExplanationThere is no support for mixing 31-bit Addressing Mode(AMODE 31) and 64-bit Addressing Mode (AMODE 64)applications across DLL calls.






Programmer responseMake sure that the AMODE of the calling functionmatches the AMODE of the DLL. You may need toverify with the DLL provider that they support runningin the AMODE you are calling from, and that you areusing the correct DLL.

If the DLL provider does not provide this DLL builtAMODE 64, then you will not be able to use it unlessyou rebuild your application as AMODE 31.


If the DLL provider does support this DLL in bothAMODE 31 and AMODE 64, they would ship twocopies of the same DLL which are built with differentAMODEs. They would ship them using one of thefollowing techniques:

• Ship two DLLs with different names. In this case youwill need to make sure your application referencesthe correct DLL name for the AMODE in which you'rerunning, either explicitly on the dllload() or dlopen()call, or implicitly by choosing the correct side deck atlinkedit time.

• Ship two DLLs with the same name but installed indifferent paths or data sets. In this case you willneed to specify the correct DLL location at run-timeusing either the LIBPATH environment variable orSTEPLIB, respectively.


CEE3588S A call was made to a function inthe AMODE 64 DLL dll-name froman AMODE 31 caller.

ExplanationThere is no support for mixing 31-bit Addressing Mode(AMODE 31) and 64-bit Addressing Mode (AMODE 64)applications across DLL calls.






Programmer responseMake sure that the AMODE of the calling functionmatches the AMODE of the DLL. You may need toverify with the DLL provider that they support runningin the AMODE you are calling from, and that you areusing the correct DLL.

If the DLL provider does not provide this DLL builtAMODE 31, then you will not be able to use it unlessyou rebuild your application as AMODE 64.

If the DLL provider does support this DLL in bothAMODE 31 and AMODE 64, they would ship twocopies of the same DLL which are built with differentAMODEs. They would ship them using one of thefollowing techniques:

• Ship two DLLs with different names. In this case youwill need to make sure your application referencesthe correct DLL name for the AMODE in which you'rerunning, either explicitly on the dllload() or dlopen()call, or implicitly by choosing the correct side deck atlinkedit time.

• Ship two DLLs with the same name but installed indifferent paths or data sets. In this case you willneed to specify the correct DLL location at run-timeusing either the LIBPATH environment variable orSTEPLIB, respectively.


CEE3589S The service was invoked for aprogram object that contains WSAlocated above the 2GB bar andbelow the bar.

ExplanationA Language Environmentservice found a programobject that contains a WSA located above and belowthe 2GB bar. You cannot mix any WSA above andbelow the bar parts in the same program object.

System actionIf the Language Environment service that detectedthe condition was passed a feedback code parameter,then the feedback code representing this message isreturned. Otherwise the enclave is terminated.

Programmer responseRebind the program object after recompiling the partsso that they are all compiled either above the bar orbelow the bar.



CEE3590I Input dll-token not permitted forthis DLL function.

ExplanationThe DLL handle supplied to this DLL function call couldnot be matched to a DLL handle returned from aprevious C dlopen() request.

System actionIf this was a C dlclose() or dlsym() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, wereavailable through the _EDC_DLL_DIAG environmentvariable.

If this was a C dlclose() or dlsym() request, thiserror could also be returned to the caller through asubsequent C dlerror() request.


Programmer responseEnsure that the DLL handle supplied to a C dlclose()or dlsym() request is the same as one returned froma dlopen() request. You cannot share a DLL handlebetween the older explicit DLL services (dllload,dllqueryvar, dllqueryfn, dllfree) and the newer services(dlopen, dlsym, dlclose).


CEE3591I DLL dll-name does not export anysymbols.

ExplanationAn attempt was made to locate an external DLLsymbol, but DLL dll-name does not contain anyexported symbols.

System actionIf this was a C dlsym() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,


If this was a C dlsym() request, this error could also bereturned to the caller through a subsequent call to theC dlerror() function.


Programmer responseThe request is ignored. Ensure that the DLL indicatedin the job library or link library is the correct version,and that it contains the external symbol.


CEE3592I The external symbol was not foundin DLL dll-name.

ExplanationAn attempt was made to locate an external symbol inDLL dll-name, but either the symbol name was null, orthe length of the symbol name was negative.

System actionIf the _EDC_DLL_DIAG environment variable is not setto QUIET, the error message is sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, areavailable through the _EDC_DLL_DIAG environmentvariable.

This error can also be returned to the caller through asubsequent call to the C dlerror() function.


Programmer responseThe request is ignored. Ensure that the symbol nameand length are specified correctly on the C dlsym()request.


CEE3593I External symbol symbol-name wasnot found in DLL dll-name


ExplanationAn attempt was made to locate an external symbol,but symbol-name was not found in the export sectionof DLL dll-name, or any of its dependent DLLs thatwere also loaded at the time of the C dlopen() request.

System actionIf this was a C dlsym() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, wereavailable through the _EDC_DLL_DIAG environmentvariable.



Programmer responseThe request is ignored. Ensure that the symbol namespecified on the C dlsym() request is correct, thatthe DLL indicated in the job library or link library isthe correct version, and that it contains the externalvariable. If the symbol is expected to be found in oneof the dependent DLLs, then you may need to makethe C dlopen() request with the RTLD_NOW flag toensure all dependent DLLs are preloaded and availablefor subsequent C dlsym() requests.


CEE3594I External symbol symbol-name wasnot found as a result of a search ofthe global symbol object.

ExplanationAn attempt was made to locate an external symbol inthe global symbol object, but symbol-name was notfound in the export section of any of the "non-LOCAL"DLLs currently loaded.

System actionIf this was a C dlsym() request and the_EDC_DLL_DIAG environment variable was not set toQUIET, the error message was sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,




Programmer responseThe request is ignored. Ensure that the symbol namespecified on the C dlsym() request is correct, and thatthe DLL that is expected to contain the symbol wasopened at least once with the RTLD_GLOBAL flag.

Symbolic Feedback CodeCEE3GA

CEE3595S DLL dll-name does not contain aCELQSTRT CSECT.

ExplanationThe application is attempting to load DLL dll-nameimplicitly or explicitly, but the CELQSTRT CSECTcannot be located within it.


If this was an explicit DLL Load (dllload()) or DLL Open(dlopen()) request, the feedback code is returned tothe caller.




Programmer responseMake sure that when you generate the DLL, it containsa CELQSTRT CSECT.


Symbolic Feedback CodeCEE3GB

CEE3596S An MVS load of module module-name failed. The system abendcode was abend-code the reasoncode was reason-code.

ExplanationAn attempt to load module module-name from MVSfailed. The system abend and reason codes werereturned.

System actionUnless the condition is handled, the default actionis to terminate the enclave. If this was a Cdllload() or dlopen() request and the _EDC_DLL_DIAGenvironment variable is not set to QUIET, theerror message is sent to the Language Environmentmessage file. Other DLL diagnostic options, such asissuing ctrace(), signaling a condition, and the abilityto turn off _EDC_DLL_DIAG diagnostics, are availablethrough the _EDC_DLL_DIAG environment variable.

If this was an explicit C dlopen() request, this error canalso be returned to the caller through a subsequentcall to the C dlerror() function.

If this was a DLL load or open request, a CEEDLLF DLLfailure control block is populated with further DLL errordiagnostics.

Programmer responseSee z/OS MVS System Codes for the appropriate actionto take for this abend code and reason code. Consultwith your system support personnel if necessary.

CEE3600S A function or variable reference tomember-language runtime libraryDLL can not be resolved.

ExplanationLanguage Environment can not resolve an applicationroutine's reference to a runtime library's DLL. Theruntime library may not be initialized.

System actionThe enclave is terminated.

Programmer responseEnsure that the referencing routine is written in asupported member language, and that referenced

member language's runtime library DLLs are in yourprogram search order.

Symbolic Feedback CodeCEE3GG

CEE3601I The string 'string' was found wherea delimiter was expected followinga quoted suboption for the run-time option option.

ExplanationA quoted suboption must be followed by either acomma, right parenthesis, or space.

System actionThe characters following suboption up to the nextcomma, space, or parenthesis are ignored.

Programmer responseCorrect the run-time options string.

Symbolic Feedback CodeCEE3GH

CEE3602I An end quote delimiter did notoccur before the end of the run-time option string.

ExplanationQuotes, either single or double, must be in pairs.

System actionThe end quote is assumed.


Symbolic Feedback CodeCEE3GI

CEE3603I The character 'character' is not avalid run-time option delimiter.

ExplanationOptions must be separated by either a space or acomma.


System actioncharacter is ignored.


Symbolic Feedback CodeCEE3GJ

CEE3604I The character 'character' is not avalid suboption delimiter for run-time options.

ExplanationSuboptions must be separated by a comma.

System actionThe separator is assumed to be a comma.


Symbolic Feedback CodeCEE3GK

CEE3605I The string 'string' was found wherea delimiter was expected followingthe suboptions for the run-timeoption option.

ExplanationSuboptions that are enclosed within parentheses mustbe followed by either a space or a comma.

System actionThe characters following the right parenthesis up tothe next comma or space are ignored.


Symbolic Feedback CodeCEE3GL

CEE3606I The string 'string' was too long andwas ignored.

ExplanationThe maximum string length for an option or suboptionwas exceeded.

System actionstring is ignored.


Symbolic Feedback CodeCEE3GM

CEE3607I The end of the suboption string didnot contain a right parenthesis.

ExplanationA left parenthesis did not have a matching rightparenthesis.

System actionThe right parenthesis is assumed.


Symbolic Feedback CodeCEE3GN

CEE3608I The following messages pertain tothe invocation command run-timeoptions.

ExplanationThe messages after this one up to the next messageof this type with a different source, pertain to theinvocation command.



Symbolic Feedback CodeCEE3GO


CEE3609I The run-time option option is notsupported.

Explanationoption was an option from a previous release that wasnot supported or mapped by Language Environment.

System actionoption is ignored.

Programmer responseConsult the appropriate migration guide for a list ofoptions supported for the language. Correct the run-time options string.

Symbolic Feedback CodeCEE3GP

CEE3610I The run-time option old-option wasmapped to the run-time option le-option.

Explanationold-option was an option from a previous releasethat was supported by Language Environment forcompatibility.

System actionold-option is mapped to le-option.

Programmer responseConsult the appropriate migration guide for a list ofoptions supported for the language. Change the run-time options string to use the le-option instead.

Symbolic Feedback CodeCEE3GQ

CEE3611I The run-time option option wasan invalid run-time option or isnot supported in this release ofLanguage Environment.

Explanationoption was not a valid option. Either the option isnot valid for this release of Language Environment, orwas recognized by Language Environment for previousrelease language campatibility.

System actionThe option option is ignored.

Programmer responseConsult z/OS Language Environment ProgrammingReference or the appropriate migration guide for alist of options supported on the release of LanguageEnvironment being used. Change the run-time optionsstring, or execute this application on a level ofLanguage Environment that supports this option.

Symbolic Feedback CodeCEE3GR

CEE3612I Too many suboptions werespecified for the run-time optionoption.

ExplanationThe number of suboptions specified for optionexceeded that defined for the option.

System actionThe extra suboptions are ignored.

Programmer responseA list of valid run-time options is provided inz/OS Language Environment Programming Reference.Correct the run-time options string.

Symbolic Feedback CodeCEE3GS

CEE3613I The run-time option old-optionappeared in the options string.

Explanationold-option (SPIE, NOSPIE, STAE, or NOSTAE) was anoption from a previous release that was supported byLanguage Environment for compatibility, but ignored ifTRAP was specified. See z/OS Language EnvironmentProgramming Reference for the interactions betweenTRAP and SPIE, NOSPIE, STAE, or NOSTAE.

System actionold-option is ignored if TRAP is specified, otherwise itis mapped to TRAP.


Programmer responseChange the run-time options string to use the TRAPoption instead of SPIE, NOSPIE, STAE, or NOSTAE.

Symbolic Feedback CodeCEE3GT

CEE3614I An invalid character occurred inthe numeric string 'string' of therun-time option option.

Explanationstring did not contain all decimal numeric characters.

System actionThe string is ignored.

Programmer responseCorrect the run-time options string to contain allnumeric characters.

Symbolic Feedback CodeCEE3GU

CEE3616I The string 'string' was not a validor supported suboption of the run-time option option in this release.

Explanationstring was not in the set of recognized values or notsupported in this release of Language Environment.

System actionThe suboption is ignored.

Programmer responseConsult z/OS Language Environment ProgrammingReference or the appropriate migration guide for alist of suboptions for option option supported onthe release of Language Environment being used.Change the invalid suboption string for the run-timeoption option or execute this application on a level ofLanguage Environment that supports this suboption.Remove the invalid suboption string from the run-time.


CEE3617I The number number of the run-time option option exceeded

the range of -2147483648 to2147483647.

Explanationnumber exceeded the range of -2147483648 to2147483647.

System actionThe number is ignored.

Programmer responseCorrect the run-time options string to be within theacceptable range of -2147483647 to 2147483647.


CEE3618I The run-time option option wasnot valid from the invocationcommand.

Explanationoption was not valid from the invocation command.


Programmer responseRemove the option run-time option from the invocationcommand.


CEE3619I The value value was not a validMSGQ number.

Explanationvalue must be greater than zero.

System actionvalue is ignored.

Programmer responseCorrect the value in the run-time options string to begreater than zero.



CEE3620I The following messages pertain tothe assembler user exit run-timeoptions.

ExplanationThe messages after this one up to the next messageof this type with a different source pertain to theassembler user exit.




CEE3621I The run-time option option was notvalid from the assembler user exit.

Explanationoption was not valid from the assembler user exit.


Programmer responseRemove the option from the run-time options specifiedin the assembler user exit.


CEE3622I The STORAGE option quotedsuboption string 'string' was notone character long.

ExplanationThe only acceptable length for STORAGE suboptionswithin quotes is one.


Programmer responseCorrect the STORAGE run-time option quotedsuboption string to be one character long.


CEE3623I The UPSI option suboption string'string' was not eight characterslong.

ExplanationThe only acceptable length for the UPSI suboption iseight.


Programmer responseCorrect the UPSI run-time option suboption string tobe eight characters long.


CEE3624I One or more error messagespertaining to the run-timeoptions included in the invocationcommand were lost.

ExplanationThe run-time options error table (ROET) overflowed.

System actionThe errors that are detected after the table overflowedare discarded.

Programmer responseCorrect the reported errors so the discarded errors fitinto the error table.


CEE3625I One or more error messagespertaining to the run-time optionsreturned by the assembler userexit were lost.






CEE3626I One or more error messagespertaining to the run-time optionscontained within the programmerdefaults were lost.





CEE3627I The following messages pertain tothe programmer default run-timeoptions.

ExplanationThe messages after this one up to the next messageof this type with a different source, pertain to theprogrammer default options.



Symbolic Feedback CodeCEE3HB

CEE3628I The run-time option option wasnot valid from the programmerdefaults.

Explanationoption was not valid from the programmer defaults.

System actionThe option is ignored.

Programmer responseCorrect the run-time options string by removing theoption run-time option.

Symbolic Feedback CodeCEE3HC

CEE3629I The run-time option old-option waspartially mapped to the run-timeoption le-option.

Explanationold-option was an old language option that was beingsupported by Language Environment for compatibility.The user should use the Language Environment optionle-option instead.

System actionold-option is partially mapped to its LanguageEnvironment equivalent.

Programmer responseChange the run-time options string to use theLanguage Environment option instead.

Symbolic Feedback CodeCEE3HD

CEE3630I One or more settings of the run-time options STAE or SPIE wereignored.

ExplanationSTAE, SPIE, NOSTAE, and NOSPIE (options froma previous release) were ignored when the TRAPoption was specified. See z/OS Language Environment


Programming Reference for the interactions betweenTRAP and SPIE, NOSPIE, STAE, or NOSTAE.

System actionSTAE, SPIE, NOSTAE, or NOSPIE are ignored.

Programmer responseRemove the STAE, SPIE, NOSTAE, or NOSPIE run-timeoptions if the TRAP run-time option is specified.

Symbolic Feedback CodeCEE3HE

CEE3631I One or more settings of the run-time options STAE or SPIE weremapped to TRAP.

ExplanationSTAE, SPIE, NOSTAE, and NOSPIE are optionsfrom a previous release that are supported byLanguage Environment for compatibility. See z/OSLanguage Environment Programming Reference for theinteractions between TRAP and SPIE, NOSPIE, STAE,or NOSTAE.

System actionSTAE, SPIE, NOSTAE, or NOSPIE are mapped to TRAP.

Programmer responseChange the run-time options string to use the TRAPoption instead of SPIE, STAE, NOSPIE, or NOSTAE.

Symbolic Feedback CodeCEE3HF

CEE3632I POSIX(ON) run-time optionspecified and the UNIX SystemServices feature is not available onthe underlying operating system.

ExplanationThe POSIX(ON) option was specified but the UNIXSystem Services feature was not available on theunderlying operating system.

System actionPOSIX(ON) is ignored.

Programmer responseCheck with your system programmer to ensure thatUNIX System Services feature is available. Removethe POSIX(ON) run-time option if the UNIX SystemServices feature is not available.

Symbolic Feedback CodeCEE3HG

CEE3633W The total length of the combinedENVAR strings exceeded 250characters.

ExplanationThe total length of the combined ENVAR stringsexceeded the maximum limit of 250 characters.

System actionThe ENVAR string is ignored.

Programmer responseReduce the total length of the ENVAR strings to lessthan the 250 character maximum.

Symbolic Feedback CodeCEE3HH

CEE3634I The number number of the run-time option option exceeded therange of -32768 to 32767.

Explanationnumber exceeded the range of -32768 to 32767.


Programmer responseCorrect the run-time options string to be within therange of -32768 to 32767.

Symbolic Feedback CodeCEE3HI

CEE3635I The string string was not a validRECFM suboption specification forrun-time option MSGFILE.


Explanationstring for RECFM suboption must be one of thefollowing: F, FA, FB, FBA, FBS, FBSA, U, UA, V, VA, VB,or VBA.

System actionstring is ignored.

Programmer responseSpecify a valid RECFM suboption string of F, FA, FB,FBA, FBS, FBSA, U, UA, V, VA, VB, or VBA.

Symbolic Feedback CodeCEE3HJ

CEE3636I The value value exceeded themaximum allowable LRECL orBLKSIZE of 32760 bytes.

Explanationvalue cannot be greater than 32760.

System actionvalue is ignored.

Programmer responseCorrect the LRECL or BLKSIZE suboption value to beless than or equal to 32760 bytes.

Symbolic Feedback CodeCEE3HK

CEE3637I The number number specified inthe suboption suboption of therun-time option option is not avalid hexadecimal number in therange 0 to FFFFFFFF.

ExplanationAn invalid hexadecimal numeral was specified or therange of the number exceeds 0 to FFFFFFFF.


Programmer responseCorrect the run-time options string to be a validhexadecimal number in the range of 0 to FFFFFFFF.

Symbolic Feedback CodeCEE3HL

CEE3638I The table size of size, specifiedin the TRACE run-time option,exceeds the maximum allowedvalue of 16777215.

Explanationsize exceeded the maximum allowed value of16777215.

System actionThe size is ignored.

Programmer responseCorrect the TRACE run-time options to not exceed themaximum of 16777215.

Symbolic Feedback CodeCEE3HM

CEE3639I The ID suboption suboption ofthe TRACE run-time option mustconsist of the keyword 'ID'followed by a one or two digitnumber in the range 0 to number

ExplanationThe format of the ID suboption of the TRACE run-timeoption is IDxx=nnnnnnnn where xx is a one or two digitdecimal number with no blanks between it and eitherthe ID or the equal-sign.


Programmer responseCorrect the ID suboption of the TRACE run-time optionto be the correct format where xx is a one or two digitdecimal number with no blanks between it and eitherthe ID or the equal-sign.

Symbolic Feedback CodeCEE3HN

CEE3640W Multithreading function is beingused in your application but theUNIX System Services feature is


not available on the underlyingoperating system.

ExplanationMultithreading function is being used in yourapplication and that function is not supported. Theunderlying operating system must have the UNIXSystem Services feature installed and active when yourun this application.


Programmer responseIf your application uses multithreading ensure thatthe underlying operating system has the UNIX SystemServices option installed and that it is active when yourapplication is running.

Symbolic Feedback CodeCEE3HO

CEE3641I The number of the run-time optionoption exceeded the range of 0 to2147483647.

Explanationnumber exceeded the range of 0 to 2147483647.


Programmer responseCorrect the run-time option string to be within therange of 0 to 2147483647.

Symbolic Feedback CodeCEE3HP

CEE3642I The cell pool size number of therun-time option option is not valid.

Explanationnumber is either not a multiple of 8 or not in the rangefrom 8 to 2048.


Programmer responseCorrect the run-time options string so that the numberis in the range from 8 to 2048.

Symbolic Feedback CodeCEE3HQ

CEE3643I The cell pool percentage numberof the run-time option optionexceeded the range of 1 to 90.

Explanationnumber exceeded the range of 1 to 90.



Symbolic Feedback CodeCEE3HR

CEE3644I TEST option negates PROFILEoption setting.

ExplanationThe TEST and PROFILE run-time options cannot beactive at the same time. If TEST and PROFILE ON arespecified together, Language Environment will not loadthe profiler tool.

System actionThe PROFILE option is ignored.

Programmer responseTo specify a PROFILE option, ensure the NOTEST run-time option is specified for your application or as yoursystem default. The NOTEST option should be firstwhen specifying NOTEST and PROFILE together via acompiler #pragma runopts directive or on applicationinvocation.

Symbolic Feedback CodeCEE3HS

CEE3645I Profiler not loaded; moduleprofiler-name not accessible.


ExplanationThe PROFILE ON run-time option has been specifiedbut Language Environment has not loaded the profilertool.

System actionThe PROFILE option is ignored.

Programmer responseEnsure that the profile module CEEEVPRF exists andis accessible to Language Environment. When callingthe profiler application, Language Environment mustbe able to locate and access the CEEEVPRF module.

Symbolic Feedback CodeCEE3HT

CEE3646I The following messages pertainto the region default run-timeoptions.

ExplanationThe messages after this one, and up to the nextmessage of this type with a different source, pertainto the region default options.



Symbolic Feedback CodeCEE3HU

CEE3647I The region default for the run-time option option could not beoverridden.

Explanationoption was defined as non-overrideable at regioninitialization time.


Programmer responseCorrect the run-time options to not specify this option.

Symbolic Feedback CodeCEE3HV

CEE3648S POSIX(ON) run-time option in anested enclave enclave-name isnot supported.

ExplanationIn Language Environment, a process can have onlyone enclave that is running with POSIX(ON), and thatenclave must be the first enclave. All nested enclavesmust be running with POSIX(OFF).

System actionThe application will be terminated.

Programmer responseSpecify the POSIX(ON) run-time option for only thefirst enclave. Make sure all nested enclaves specifyPOSIX(OFF).

Symbolic Feedback CodeCEE3I0

CEE3649W The parameter string returnedfrom CEE3PRM exceeded themaximum length of 80 bytes andwas truncated.

ExplanationThe user parameters exceed 80 characters. The first80 bytes are returned and the remainder of the userparameters are truncated.

System actionThe user parameter string is truncated to 80 bytes.The truncated value is returned to the caller in thecharacter string parameter.

Programmer responseReduce the user parameter string to less than 80bytes.


CEE3700I The storage and options reportheading replaced a previousheading.


ExplanationThe specified report heading has replaced a headingset by an earlier call to CEERPTH.

System actionThe report heading is replaced by the new heading.

Programmer responseNone required.

Symbolic Feedback CodeCEE3JK

CEE3701W Heap damage found by HEAPCHKrun-time option.

ExplanationThis is a title message for the heap check section ofthe message file.


Programmer responseView the messages following this one to see wheredamage was found.

Symbolic Feedback CodeCEE3JL

CEE3702S Program terminating due to heapdamage.

ExplanationThis is the last message in the heap check section ofthe message file.


Programmer responseThe message file will contain the address, expectedand actual data for each damaged area found.

Symbolic Feedback CodeCEE3JM

CEE3703I In controlblock Control Block, thefieldname is damaged.

ExplanationA Language Environment control block controlblockhas damage in the fieldname area.


Programmer responseThe message following this one in the message filewill identify the address of the damage and theexpected data. If you did not use the HEAPCHK run-time option, re-run the application with HEAPCHK(ON)to help locate the cause of the problem. If you usedthe HEAPCHK run-time option and are unable tolocate the cause of the problem, contact your servicerepresentative.

Symbolic Feedback CodeCEE3JN

CEE3704I Expected data at addressaddress:data.

ExplanationProvides the address address and expected data datawhen heap damage is found.


Programmer responseThe data area following this message provides theactual data found at the damaged location.

Symbolic Feedback CodeCEE3JO

CEE3705I Pointer at address should point toa valid controlblock.

ExplanationThe pointer at location address should point toa Language Environment control block with acontrolblock eye catcher.




Symbolic Feedback CodeCEE3JP

CEE3706I The contents of the free treenode at address1 in the heapsegment beginning at address2 donot match the STORAGE run-timeoption heap_free_value.

ExplanationThe contents of storage at address1 should matchthe heap_free_value specified with the STORAGE run-time option. The first 16 bytes at address1 provideheader information and are not expected to match theheap_free_value.



Symbolic Feedback CodeCEE3JQ

CEE3707I branch pointer is bad in the freetree at address1 in the heapsegment beginning at address2.

ExplanationThe pointer to the branch branch of the free tree nodeat address address1 does not point to another freetree node.



Symbolic Feedback CodeCEE3JR

CEE3708I branch length is bad in the freetree at address1 in the heapsegment beginning at address2.

ExplanationThe length of the branch branch of the free tree nodeat address address1 is damaged.



Symbolic Feedback CodeCEE3JS

CEE3709I Either the branch pointer or lengthis damaged in the free tree ataddress1 in the heap segmentbeginning at address2.

ExplanationThe pointer to the branch branch of the free tree nodeat address address1 plus it's length does not match aheap storage element.



Symbolic Feedback CodeCEE3JT

CEE3710I Heap element at address isdamaged; expected data isword1:word2.

ExplanationThe header of the heap storage element at addressdoes not match the expected data word1 and word2.




Symbolic Feedback CodeCEE3JU

CEE3711I Processing of the HEAPCHK run-time option has been terminateddue to a previous error. Heapsare no longer being checked fordamage.

ExplanationA message preceding this one in the message file willprovide the actual error which caused the HEAPCHKprocessing to be terminated.


Programmer responseLocate the message that describes the actual errorand take appropriate action to correct the problem.If you are unable to locate the cause of the problem,contact your service representative.

Symbolic Feedback CodeCEE3JV

CEE3712I The number number of the run-time option option must end withan M to indicate the number ofMegs of storage.

ExplanationThe number number of the run-time option optiondoes not end in M.

System actionThe number is ignored

Programmer responseCorrect the run-time options string so that the valueends with M.

Symbolic Feedback CodeCEE3K0

CEE3713I The cell pool count number of therun-time option option must be atleast 4.

ExplanationThe cell pool count number of the run-time optionoption was less than 4.


Programmer responseCorrect the run-time options string so that the numberis more than 4.


CEE3714I The heap pool contains a cell to befreed at address but it has alreadybeen freed.

ExplanationThe cell at address is being freed twice by theapplication.


Programmer responseReview the heap pool trace data for the heap pool tolearn the application offset that is freeing this cell.


CEE3715W The parameter string returnedfrom CEE3PR2 was truncated dueto insufficient storage space forthe string provided by the caller.

ExplanationThe user parameters exceeded the space provided bythe caller and the remainder of the user parametersare truncated.


System actionThe user parameter string is truncated to the length ofthe space provided by the caller.

Programmer responseIncrease the storage space to the length returned bythe service.


CEE3716I The heap check zone following thestorage at address stg-address forlength stg-length has been overlaidat address overlay-address. Eachbyte in the zone from zone-low-address to zone-high-addressshould contain the value X'zone-value'.

ExplanationThe HEAPZONES runtime option detected an overlayat overlay-address. Each byte from zone-low-addressto, but not including, zone-high-address should containzone-value.


Programmer responseThe data area following this message provides theactual data found at the damaged location. In additionto the storage around overlay-address, the start andend of both the allocated storage and the heap checkzone are shown.


CEE3717I Control information in a heapcheck zone has been damaged.The value at address overlay-address should be greater thanlow-address and less than or equalto high-address.

ExplanationThe HEAPZONES runtime option detected an overlayat overlay-address. The allocated heap storage startsat low-address. The requested size was less than orequal to high-address minus low-address.




CEE3728S The use of a function, which isnot supported by this releaseof Language Environment wasdetected

ExplanationThe application has exploited a new function notavailable on this release of Language Environment.


Programmer responseRemove the usage of the unsupported function fromthe application or execute this application on arelease of Language Environment that supports thisfunction. Depending on the TERMTHDACT run-timeoption, a CEEDUMP may be available for additionaldiagnosis. One can use the traceback informationin the CEEDUMP to locate the specific LanguageEnvironment function used, that caused this message.

Symbolic Feedback CodeCEE3KG

CEE3730I One or more error messagespertaining to the system run-timeoptions were lost.





Symbolic Feedback CodeCEE3KI

CEE3731I The following messages pertainto the system default run-timeoptions in the groupname in origin.

ExplanationThe messages after this one up to the next messageof this type with a different source, pertain to thesystem default options. These defaults are found inoptions group groupname in origin, where origin can bea SETCEE command, a Parmlib member used at IPLor with a SET CEE command, or a Parmlib memberused with an invocation of the Language EnvironmentParmlib checker.

System actionNone

Programmer responseCorrect the options in the Parmlib member or SETCEEcommand.

Symbolic Feedback CodeCEE3KJ

CEE3732I An end of comment delimiter ismissing on line line of parmlibmember membername.

ExplanationLine number line in the parmlib member membernameis missing an ending delimiter for a comment. Allcomments must end on the same line on which theybegin.

System actionNone.

Programmer responseCorrect the options in the Parmlib member.

Symbolic Feedback CodeCEE3KK

CEE3733I The eof for parmlib membermembername was reached beforefinding a closing option group

delimiter for the options groupgroupname.

ExplanationThe delimiter that ends option group groupname ismissing. Each group must begin and end with aparenthesis.

System actionNone

Programmer responseCorrect the Parmlib member.

Symbolic Feedback CodeCEE3KL

CEE3734I The EOF for parmlib membermembername was reached beforefinding a closing quote delimiterfor the options group groupname.

ExplanationEach quoted string must end with a quote characterthat matches the one used to start the string.

System actionNone


Symbolic Feedback CodeCEE3KM

CEE3735I Text on line line starting atcolumn column is outside of anoptions group in parmlib membermembername.

ExplanationAll text must be in a comment or an options group.

System actionNone

Programmer responseCorrect the options in the Parmlib member.


Symbolic Feedback CodeCEE3KN

CEE3736I Error code code on linenumber line of parmlib membermembername.

ExplanationAn I/O error occurred while reading the parmlibmember.

System actionNone.


Symbolic Feedback CodeCEE3KO

CEE3737I Contents of parmlib membermembername.

ExplanationThis is the heading of the listing of the contents ofa parmlib member specified by CEE= at IPL. One ormore lines may follow with the contents of the parmlibmember.

System actionNone


Symbolic Feedback CodeCEE3KP

CEE3738I A CEE= parmlib member was notfound or is in error.

Explanationz/OS CEE parmlib parsing has encountered a syntaxerror in one of the specified parmlib members or thespecified parmlib member does not exist. Once thesystem has completed it's IPL, check the hardcopy logfor the errors.

System actionThe system prompts for a new CEE= parmlibspecification.


Symbolic Feedback CodeCEE3KQ

CEE3739I Language Environmentinitialization complete.

ExplanationLanguage Environment has completed the reading andprocessing of parmlib members.

System actionThe processing of parmlib members has completed.


Symbolic Feedback CodeCEE3KR

CEE3740I The following messages pertainto the system default run-timeoptions.

ExplanationThe messages after this one up to the next message ofthis type with a different source, pertain to the systemdefault options.

System actionThe processing of parmlib members has completed.


Symbolic Feedback CodeCEE3KS

CEE3741I The run-time option option wasnot valid from the system defaultoptions.


Explanationoption was not valid from the System Default options.


Programmer responseRemove the option run-time option from the Parmlibmember or from the SET CEE command.

Symbolic Feedback CodeCEE3KT

CEE3742I The SET CEE command hascompleted.

ExplanationThe SET CEE command has completed processing theparmlib members. Errors might have been reportedwhile parsing the run-time options in the members.

System actionThe run-time options in the Parmlib member specifiedwith the SET CEE command have been saved.


Symbolic Feedback CodeCEE3KU

CEE3743I The SETCEE command hascompleted.

ExplanationThe SETCEE command has completed processing therun-time options. Errors might have been reportedwhile parsing the run-time options specified with theSETCEE command.

System actionThe run-time options specified with the SETCEEcommand have been saved.


Symbolic Feedback CodeCEE3KV

CEE3744I hh.mm.ss DISPLAYCEE=(members)or NO MEMBERS SPECIFIED

ExplanationThe following material is part of the message text:hh.mm.ss

The time in hours (00--23), minutes (00--59), andseconds (00--59) for the DISPLAY CEE command.

CEE=(members)The parmlib member name list specified on theSET CEE command or in the IEASYS member usedat IPL.

NO MEMBERS SPECIFIEDDisplayed when there have been no CEEPRMmembers.

System actionNone


Symbolic Feedback CodeCEE3L0

CEE3745I hh.mm.ss DISPLAYgroupnameCEE=(members) or NO MEMBERSSPECIFIEDtext

ExplanationThe following material is part of the message text:hh.mm.ss

The time in hours (00 - 23), minutes (00 - 59), andseconds (00 - 59) for the DISPLAY CEE command.

groupnameEither the name of the group (CEECOPT, CEEDOPT,or CELQDOPT) for the options listed in the textportion of this message or the name of thekeyword (CEEROPT or CELQROPT) whose valuesare listed in the text portion of this message.

CEE=(members)The parmlib member name list specified on theSET CEE command or in the IEASYS member usedat IPL.

NO MEMBERS SPECIFIEDDisplayed when there have been no CEEPRMmembers.


textIf groupname is CEECOPT, CEEDOPT or CELQDOPT,then a list of the run-time options specified usingthe CEEPRMxx or the SETCEE command will bedisplayed. One or more of these formats will bedisplayed:

PARMLIB(CEEPRMxx) option(value)CEEPRMxx Non-overrideable option(value)SETCEE COMMAND option(value)SETCEE Non-overrideable option(value)

System actionNone



CEE3746I No option group groupname exists.

ExplanationThe group name groupname requested on theDISPLAY CEE or SETCEE command is invalid.

System actionNone

Programmer responseReissue the command with a valid group name.


CEE3748I The keyword keyword found insource is not valid.

ExplanationThe keyword is either not valid or is not supported inthis release of Language Environment.

System actionNone

Programmer responseReissue the command with a valid keyword.


CEE3749I The value specified for keywordkeyword found in source is notvalid.

ExplanationThe value specified is either not valid or is notsupported in this release of Language Environment.

System actionNone

Programmer response: Reissue the command with a valid value in keyword.


CEE3751I The alternative heap managerdoes not support XPLINK.

ExplanationThe user or application attempted to use analternative heap manager for an XPLINK application,but alternative heap manager indicated that it does notsupport the XPLINK environment.

System actionThe alternative heap manager is ignored. Processingcontinues with the normal heap manager.

Programmer responseSelect an alternative heap manager that supportsXPLINK, or do not use one. Contact the owner of thealternative heap manager if necessary.


CEE3752I The alternative heap manager didnot supply all of the replacementroutine addresses.

ExplanationA NULL or incorrect value for one of the replacementroutines was set by the alternative heap manager.


System actionThe alternative heap manager is ignored. Processingcontinues with the normal heap manager.

Programmer responseContact the owner of the alternative heap manager.


CEE3753I The input symbol can not be foundin the current job step.

ExplanationThe JCL symbol that was requested can not be foundin the current job step.

System actionThe function has not been performed.

Programmer responseCheck the JCL to ensure that an EXPORT was donefor the requested symbol and that the symbol wasSET after being exported. And make sure that theJCL symbol name follows the JCL symbol namingconventions.


CEE3754S Incorrect parameters detected.

ExplanationIf this message was returned by CEEGTJS or__le_ceegtjs(), one or more of the following may betrue:

• The function_code is not valid.• A wild card character ('*' or '?') was found in the

input symbol_name.• The output parameter symbol_value or value_length

is not valid. An addressing exception occurred whilestoring the symbol value or value length into thesefields. Make sure the symbol_value is a valid 255-byte fixed-length string.

If the message was returned by CEERCDM or_le_record_dump(), one or more of the following maybe true:

• The function_code is not valid.

• The function_code is 1, and the length of thecharacter string in the input information is either notpositive or is greater than 44.

If the message was returned by CEESECS, one of thefollowing may be true:

• An input date outside the specified Era was used inthe call.

If this message was returned by CEEUSGD or__le_ceeusgd(), one or more of the following may betrue:

• The function_code is not valid.• Prtoken (or prtoken64) and product_owner

cannot be specified simultaneously when requestis deregister, functionbegin, functiondata orfunctionend.


Programmer responseCorrect the parameter and try again.

Symbolic Feedback CodeCEE3LA

CEE3755I Suboption position-number of theHEAPCHK runtime option is notvalid. Pool pool-number is notactive.

ExplanationThe pool number is bigger than the number of activeheap pools.

System actionThe heap pool tracing is not activated.

Programmer responseCheck the HEAPCHK, HEAPPOOLS, HEAPPOOLS64runtime options.

Symbolic Feedback CodeCEE3LB

CEE3760E The Language EnvironmentParmlib checker could notprocess the specified membermembername.


ExplanationThe specified CEEPRMxx member did not exist or themembername did not contain valid characters.

System actionParmlib checker ends.

Programmer responseMake sure the suffix of CEEPRMxx member isalphanumeric. See z/OS Language EnvironmentCustomization for further details for creating themember.

Symbolic Feedback CodeCEE3LG

CEE3761I The following messages pertainto the call to the LanguageEnvironment Parmlib checker.

ExplanationThe Language Environment Parmlib checker wascalled to syntax check the one or more members. Themessages after this one report one or more errorsfound in the members.

System actionNone


Symbolic Feedback CodeCEE3LH

CEE3762I The Language EnvironmentParmlib checker has completed.

ExplanationThe Language Environment Parmlib checker hascompleted processing one or more members. Errorsmay have been reported while parsing the run-timeoptions in one or more members.

System actionNone


Symbolic Feedback CodeCEE3LI

CEE3765I The delimiter delimiter is notallowed from the current source.

ExplanationThe delimiter found is only valid when processing aCEEPRMxx parmlib member or a SETCEE command.The delimiter found can be one of the following:

• When specifying an OVR or NONOVR attribute:

=(( or ((

• When specifying an OVR or NONOVR attribute withthe NOAUTOTASK run-time option:

=( or (



Symbolic Feedback CodeCEE3LL

CEE3766I A required delimiter delimiter wasnot found.

ExplanationA required delimiter was not found. One of thefollowing occurred:

• An equal sign (=) was specified after a run-timeoption without two opening parenthesis. Blanks arenot allowed within an =(( delimiter.

• A comma was missing after the closing parenthesisof the suboptions.

• A closing parenthesis was missing after the OVR orNONOVR attribute.

• A SETCEE command did not include the requireddelimiter.

System actionThe system continues processing.


Programmer responseCorrect the run-time options string or the SETCEEcommand syntax.

Symbolic Feedback CodeCEE3LM

CEE3767I The required OVR or NONOVRattribute was not found.

ExplanationAn "=(( " or "((" delimiter was found, but therequired OVR or NONOVR attribute was not found.



Symbolic Feedback CodeCEE3LN

CEE3768I The system default for the run-time option option could not beoverridden.

ExplanationThe specified run-time option, option, was definedas nonoverrideable in the system default run-timeoptions. This was either with a CEEPRMxx member orthe SETCEE command.


Programmer responseCorrect the run-time options to not specify this option.

Symbolic Feedback CodeCEE3LO

CEE3769I The run-time option ENVAR cannotbe marked as nonoverrideable.

ExplanationENVAR was specified with the NONOVR attribute in aCEEPRMxx member or on a SETCEE command. ENVARcannot be marked as nonoverrideable.

System actionNONOVR has been forced to be OVR.


Symbolic Feedback CodeCEE3LP

CEE3770I A required sub-option was notspecified.

ExplanationAn "=(( " or "((" delimiter was found but a requiredsuboption was not specified. The run-time optionsAIXBLD, DEBUG, FILEHIST, INQPCOPN, OCSTATUS,PC, RTEREUS, and SIMVRD require an ON or OFFsuboption to be specified when using the "=(( "or "((" delimiter. For more information, see z/OSLanguage Environment Customization.

System actionThe option is ignored and the system continuesprocessing.


Symbolic Feedback CodeCEE3LQ

CEE3771I The value of the suboptionsuboption of the HEAPZONESruntime option was not in the validrange.

ExplanationThe value of the suboption suboption was not inthe valid range. See z/OS Language EnvironmentProgramming Reference for information about a validrange value.

System actionThe value is ignored. The default value is used.

Programmer responseChange the value of the suboption suboption to be inthe valid range.


Symbolic Feedback CodeCEE3LR

CEE3772I HEAP location set to BELOW forcesHEAPPOOLS to be set OFF.

ExplanationThe HEAP runtime option must be set to ANYWHEREfor HEAPPOOLS to be active.

System actionHEAPPOOLS is set to OFF.

Programmer responseChange HEAP to ANYWHERE before settingHEAPPOOLS to ON or ALIGN.

Symbolic Feedback CodeCEE3LS

CEE3775W A conflict was detected betweenthe TERMTHDACT suboptionCICSDDS and level. TheTERMTHDACT level setting hasbeen set to TRACE.

ExplanationThe thread termination dump output level settingconflicts with the destination setting of CICSDDS. Alevel of TRACE or less must be used with CICSDDS.

System actionThe level setting was reset to TRACE.

Programmer responseChange the value of the detail level to TRACE or less.

Symbolic Feedback CodeCEE3LV

CEE3781I The value of the reg_stor_amountsub-option of the TERMTHDACToption was not in the valid range0–256.

ExplanationThe value of the reg_stor_amount sub-option was nota member in the range of 0 - 256.

System actionThe value is ignored. The default value of 96 is used.

Programmer responseChange the value of the reg_stor_amount suboption tobe in the valid range 0 - 256.

Symbolic Feedback CodeCEE3M5

CEE3782E The value of the REGSTOR optionof CEE3DMP was not in the validrange 0–256.

ExplanationThe value of the REGSTOR option of CEE3DMP was nota number in the range of 0–256.

System actionThe value is ignored. The default value of 96 is used.

Programmer responseChange the value of the REGSTOR option to be in thevalid range 0–256.


CEE3783I The page_len suboption of theCEEDUMP run-time option is notvalid.

ExplanationThe page_len suboption supplied for the CEEDUMPrun-time option is not valid. Page_len must adhere tothe following rules:

• It must be a 1 to 9 digit decimal whole number.• The value must be either 0 or greater than 9.

System actionThe suboption value is ignored. Processing continues.

Programmer responseVerify that page_len complies with the previous rules.



CEE3784I The input string string is not avalid SYSOUT class.

ExplanationAn invalid sysout class was encountered duringCEEDUMP run-time options parsing.

The sysout class provided must adhere to thefollowing rules:

• It must be one character long.• The class can equal "A" through "Z", "0" through "9"

or "*" as JCL rules allowed.• The class can not be specified in quotation marks.

System actionThe suboption value is ignored. Option processingstops.

Programmer responseVerify that the sysout class complies with the previousrules.


CEE3785I The dynamical allocation of aCEEDUMP DD statement using thespecified sysout class has failed.

ExplanationThe CEEDUMP run-time option specified the use ofa sysout class for defining a CEEDUMP DD card.However, the dynamic allocation of the CEEDUMP dataset failed during the use of the given sysout class<class>. A new CEEDUMP data set was allocated toSYSOUT=* instead.

System actionA CEEDUMP data set is allocated to SYSOUT=*.

Programmer responseVerify that the sysout class specified in the CEEDUMPrun-time option is a valid class in your installation.


CEE3786I The input string string is not avalid sysout form-name.

ExplanationAn invalid form-name was encountered duringCEEDUMP run-time options parsing. The form-name provided must consist of one through fouralphanumeric or national (#,@,$) characters accordingto JCL rules.

System actionThe suboption value is ignored. Option processingstops.

Programmer responseVerify that the form-name specified is valid.

Symbolic Feedback CodeCEE3MA

CEE3787I The option run-time option didnot contain a required leftparenthesis.

ExplanationA required left parenthesis was not found whileprocessing a suboption of the above mentioned run-time option.

System actionThe run-time option string processed is ignored.Option processing stops.

Programmer responseCorrect the run-time option string.

Symbolic Feedback CodeCEE3MB

CEE3788I The cell-size suboption of therto-name run-time option wasspecified as a sublist. The sublistcontained a pool-count value but itdid not contain a cell-size value.

ExplanationWhen the cell-size suboption is specified as a sublist,both the cell-size value and pool-count value must bespecified.




Symbolic Feedback CodeCEE3MC

CEE3789I The cell-size suboption of therto-name run-time option wasspecified as a sublist. The sublistcontained a cell-size value but itdid not contain a pool-count value.

ExplanationWhen the cell-size suboption is specified as a sublist,both the cell-size value and pool-count value must bespecified.



Symbolic Feedback CodeCEE3MD

CEE3790I The CEEOPTS data set specifies anunsupported data set type.

ExplanationLanguage Environment was unable to read the data setspecified as the DD:CEEOPTS run-time options file dueto it being in an unsupported format.

System actionThe invalid DD:CEEOPTS dataset is ignored, theoptions specified within it are not read in, andexecution continues as normal.

Programmer responseMake sure that the dataset specified is in a supportedformat. Refer to the z/OS Language EnvironmentProgramming Guide for details on supported datasettypes.

Symbolic Feedback CodeCEE3ME

CEE3791I An I/O error occurred accessingthe CEEOPTS data set.

ExplanationLanguage Environment was unable to read the data setspecified as the DD:CEEOPTS run-time options file dueto a open/read error.

System actionThe invalid DD:CEEOPTS dataset is ignored, theoptions specified within it are not read in, andexecution continues as normal.

Programmer responseMake sure that the data set specified exists and theprogram has appropriate permissions to access it.

Symbolic Feedback CodeCEE3MF

CEE3792I The following messages pertain tothe CEEOPTS data set run-timeoptions.

ExplanationThe messages after this one up to the next messageof this type with a different source, pertain to theCEEOPTS data set.



Symbolic Feedback CodeCEE3MG

CEE3793I One or more error messagespertaining to the DD:CEEOPTSrun-time options were lost.





Symbolic Feedback CodeCEE3MH

CEE3794I The run-time option option wasnot valid from the DD:CEEOPTSdataset.

Explanationoption was not valid from the DD:CEEOPTS dataset.


Programmer responseRemove the option run-time option from theDD:CEEOPTS dataset.

Symbolic Feedback CodeCEE3MI

CEE3795I The dataset specified byDD:CEEOPTS contained more datathan is allowed. The data wastruncated starting on line line atcolumn column.

ExplanationThe dataset specified by DD:CEEOPTS containedgreater than 3072 bytes of data. LanguageEnvironment limits the amount of data within thisdataset to 3072 bytes. Data beyond this limit indicatedby line and column was truncated.

System actionThe excess data is truncated. The first 3072 bytes ofthe DD:CEEOPTS dataset are processed, and executioncontinues as normal.

Programmer responseMake sure that the dataset specified does not containmore than 3072 bytes of data (including blanks).Shorten the dataset and re-run application.

Symbolic Feedback CodeCEE3MJ

CEE3796I An attempt to dynamically takea dump was not successful. Theerror return code was return andthe reason code was reason.

ExplanationLanguage Environment invoked IEATDUMP todynamically allocate a dump data set. However, theallocation was not successful. Return and reasonare returned by the IEATDUMP system service orby RACF®. IEATDUMP or RACF might issue othermessages to the console or SYSLOG. See messageCEE3798I for the name of the data set.

System actionNo data set is allocated, no dump is created.

Programmer responseSee z/OS MVS Programming: Assembler ServicesReference IAR-XCT for information about IEATDUMPreturn and reason codes.

CEE3797I Language Environment hasdynamically created a dump.

ExplanationLanguage Environment was able to obtain a dump. Seemessage CEE3798I for the name of the data set.

System actionNone.

Programmer responseView the dump by using IPCS to determine the causeof the ABEND.

CEE3798I Attempting to take a dump forABEND abend_code to data set:dumpname

ExplanationLanguage Environment has determined that a dumpfor ABEND code abend_code needs to be created. Adata set dumpname will be allocated.

System actionNone


Programmer responseThis message should be followed by either CEE3797Ior CEE3796I.

CEE3799I The cell pool pool-count number ofthe run-time option option is notvalid.

ExplanationThe number value is not in the range from 1 to 255.

System actionBoth the cell-size and pool-count values for the cell-size suboption are ignored. Processing continues.


Symbolic Feedback CodeCEE3MN

CEE3800S The address passed to the stacksegment routine was not withinany Language Environment stacksegment.

ExplanationThe address passed to the stack segment routinewas not within any currently allocated LanguageEnvironment stack segment.

System actionThe bounds, segment type, and chain are undefined.

Programmer responseContact your service representative. This is an internalerror.

Symbolic Feedback CodeCEE3MO

CEE3817E The member event handler did notreturn a useable function pointer.

ExplanationThe member language which compiled the input loadmodule either does not support the CEEPGFD CWI, orencountered an unrecoverable error.

System actionCEEPGFD returns an unusable function pointer.

Programmer responseEnsure that the input load module is compiled from alanguage which supports the CEEPGFD CWI.

Symbolic Feedback CodeCEE3N9

CEE3818E The member event handlerencountered an error.

ExplanationThe member language which compiled the input loadmodule either does not support the CEEPRFD CWI, orencountered an unrecoverable error.

System actionNo function pointer is released.

Programmer responseEnsure that the input load module is compiled from alanguage which supports the CEEPRFD CWI, and thatthe function pointer is a valid pointer obtained fromthe CEEPGFD CWI.

Symbolic Feedback CodeCEE3NA

CEE3819I An invalid string string was foundin the run-time option ENVAR.

ExplanationThe string does not contain an equal sign. The inputbeginning at the string will be ignored.

System actionThe invalid ENVAR string is ignored.

Programmer responseENVAR strings must be in the form of 'name=value'.The string may be missing or have misplaced quotationmarks. You can specify multiple environmentvariables, separating the name=value pairs withcommas. Quotation marks are required whenspecifying multiple variables.


Symbolic Feedback CodeCEE3NB

CEE3821I The run-time option old-optionappeared in the options stringand is ignored when theTHREADSTACK option is specified.

Explanationold-option (NONIPTSTACK or NONONIPSTACK) is anoption from a previous release that is supported byLanguage Environment for compatibility, but ignored ifTHREADSTACK is specified.

System actionold-option is ignored if THREADSTACK is specified.

Programmer responseChange the run-time options string to use the newoption THREADSTACK instead of NONIPTSTACK orNONONIPTSTACK.

Symbolic Feedback CodeCEE3ND

CEE3825I The run-time optionNONONIPTSTACK orNONIPTSTACK appeared in theoptions string. NONONIPTSTACKor NONIPTSTACK were mapped toTHREADSTACK.

ExplanationNONIPTSTACK and NONONIPSTACK are options froma previous release that are supported by LanguageEnvironment for compatibility.

System actionNONONIPTSTACK or NONIPTSTACK is mapped toTHREADSTACK.

Programmer responseChange the run-time options string to use theTHREADSTACK option instead of NONONIPTSTACK orNONIPTSTACK.

Symbolic Feedback CodeCEE3NH

CEE3836I A statement number is notavailable for this DSA. DWARFdata in the load module iscorrupted.

ExplanationThis is an internal error. Language Environment couldnot determine a statement number from the loadmodule associated to this DSA. The required CompileDebug Architecture information found in this loadmodule is corrupted. This error can take place whenthe respective load module was originally produced asa UNIX file name but was then incorrectly copied to adata set (some contents of the load module have anASCII format). If this is the case, recompile the sourceassociated to the load module and use the c89 utility-o option to generate a load module in a data set, orcompile the source directly in a MVS environment.

System actionThe statement number for this DSA is not displayed inthe CEEDUMP. Processing continues.

Programmer responseIf the problem persists contact your systemrepresentative.

Symbolic Feedback CodeCEE3NS

CEE3837I Statement numbers are notavailable. The explicit DLL loadof DLL CDAEQED failed withfeedback code fc.

ExplanationThis is an internal error. Language Environment couldnot load to storage a CDA DLL required for obtainingstatement numbers. Refer to the CEEPLDE feedbackcode documentation for further information aboutthe cause of this failure. Verify SCEERUN2 memberCDAEQED is found in the system's search order.

System actionStatement numbers are not displayed in theCEEDUMP. Processing continues.



Symbolic Feedback CodeCEE3NT

CEE3838I Statement numbers are notavailable. The explicit DLL loadof DLL CDAEQDPI failed withfeedback code fc.

ExplanationThis is an internal error. Language Environment couldnot load to storage a CDA DLL required for obtainingstatement numbers. Refer to the CEEPLDE feedbackcode documentation for further information aboutthe cause of this failure. Verify SCEERUN2 memberCDAEQDPI is found in the system's search order.



Symbolic Feedback CodeCEE3NU

CEE3839I Statement numbers are notavailable. The explicit DLL loadof DLL CELQDSNF failed withfeedback code fc.

ExplanationThis is an internal error. Language Environment couldnot load to storage a DLL required for obtainingstatement numbers. Refer to the CEEPLDE feedbackcode documentation for further information aboutthe cause of this failure. Verify SCEERUN2 memberCELQDSNF is found in the system's search order.


Programmer responseNone.

Symbolic Feedback CodeCEE3NV

CEE3840I Statement numbers are notavailable. dllqueryfn() failed for afunction in the DLL CELQDSNF.

ExplanationThis is an internal error. Language Environment couldnot locate the function that determines the statementnumber.



Symbolic Feedback CodeCEE3O0

CEE3841I A statement number is notavailable for this DSA. An internalroutine failed with return code rcand reason code rs.

ExplanationThis is an internal error. Language Environment couldnot determine a statement number for this DSA.

System actionA statement number is not displayed in the CEEDUMP.Processing continues.



CEE3842I Additional Fully Qualified Nameinformation is suppressed.

ExplanationAdditional lines corresponding to other DSA entriesare not shown in the traceback report. Excludinginformation about the main entry for C/C++ programs,up to 51 lines can be dumped in the Fully QualifiedNames section of the traceback. Only complete entrieswill be output.


System actionSome entries are not displayed in the traceback'sFully Qualified Names section. CEEDUMP processingcontinues.



CEE3843I The program unit name is too longto be displayed. See the FullyQualified Names section for thecomplete name.

ExplanationA program unit name longer than 60 characters cannotbe displayed in the Condition Information sectionof the CEEDUMP. However, it is listed in the FullyQualified Names section of the traceback for the entryname shown above this message.

System actionProcessing continues.



CEE3845I CEEDUMP processing started.

ExplanationThis is a message that will be issued in the dumpreport after the header in page 1. If the LanguageEnvironment dump report successfully completes thenmessage CEE3846I will be issued at the end of thereport.

System actionLanguage Environment dump processing continues.



CEE3846I CEEDUMP processing completed.

ExplanationProcessing for the Language Environment dump reporthas completed.

System actionNone.



CEE3854I Additional Fully Qualified Nameinformation is suppressed.

ExplanationAdditional lines corresponding to other DSA entries arenot shown in the Fully Qualified Names section of thetraceback. Only up to 72 lines can be displayed in thissection. Only complete entries in the Fully QualifiedNames section are shown.

System actionSome entries are not displayed in the traceback's FullyQualified Names section. Language Environment dumpprocessing continues.


Symbolic Feedback CodeCEE3OE

CEE3858I Possible Bad Branch: Statement:statement num Offset: offset

ExplanationThis message is issued by a signaled condition orCEE3DMP to help determine the error location whenan exception occurs due to an invalid branch. If thismessage is issued by a signaled condition, then thismessage will be displayed along with the rest ofthe condition message. If it is displayed as part ofa CEEDUMP report, it will appear in the condition


information section for the active routine. If thestatement number is not available, then only the offsetwill be listed in this message. The message number isnot displayed along with the message text.


Programmer responseCheck the statement number or offset or bothprovided in this message for an invalid branch inyour routine. For further information on how to usea statement number, entry address or entry offsetto locate a problem in a routine, see z/OS LanguageEnvironment Debugging Guide.

Symbolic Feedback CodeCEE3OI

CEE3880I dump type has been suppressed -reason

ExplanationAn attempt was made to take a Language Environmentdump, but the dump was suppressed.

dump type is one of the following:

• CEEDUMP• TRANSACTION DUMP

reason is one of the following:

• USER IS NOT AUTHORIZED• PROGRAM IS RUNNING IN AN AUTHORIZED KEY• PROGRAM IS RUNNING WITH JSCBPASS ON

System actionThe dump is not taken. If dump processing occurredon behalf of an unhandled condition of severity 2or greater, the application is terminated. Otherwise,processing continues.

Programmer responseRefer to the reason in the message to determine theproper action:

• USER IS NOT AUTHORIZED: A user is runninga Language Environment application as a RACF-controlled program on a system where theIEAABD.DMPAUTH resource in the FACILITY classhas been defined, but the user has not beenpermitted access to this resource.

If this user must be able to obtain LanguageEnvironment dumps, ensure that the user has beenpermitted to the IEAABD.DMPAUTH resource in theFACILITY class.

• PROGRAM IS RUNNING IN AN AUTHORIZED KEY:A user is running an authorized key LanguageEnvironment application in a non-started taskaddress space but the user has not been permittedaccess to the IEAABD.DMPAKEY resource in theFACILITY class.

If this user must be able to obtain LanguageEnvironment dumps, ensure that the user has beenpermitted to the IEAABD.DMPAKEY resource in theFACILITY class.

• PROGRAM IS RUNNING WITH JSCBPASS ON: Auser is running a Language Environment applicationin a non-started task address space that has theJSCBPASS indicator on, including applications whosePPT entry specifies bypassing security protection.

For these applications, if a dump is neededimmediately and one is not produced, a SLIP trapcan be set to get an SVC dump. Ideally, theapplication should have its own strategy to providediagnostic data in cases of abnormal behavior.For instance, the application may use LanguageEnvironment condition handlers to produce an SVCdump or IEATDUMP for diagnostic purposes.

For more information on permitting users to theIEAABD.DMPAUTH and IEAABD.DMPAKEY resourcesin the FACILITY class, refer to the z/OS SecurityServer RACF Security Administrator's Guide.


CEE3900S The function code passed toCEE3USR was not 1 or 2.

ExplanationThe function_code specified in a CEE3USR call wasinvalid

System actionNeither SET nor QUERY is performed.

Programmer responseInvoke CEE3USR with function_code 1 (for SET) or 2(for QUERY).

Symbolic Feedback CodeCEE3PS


CEE3901S The field number passed toCEE3USR was not 1 or 2.

ExplanationThe field number specified in a CEE3USR call wasinvalid.

System actionNeither SET nor QUERY is performed.

Programmer responseInvoke CEE3USR with field_number 1 or 2.

Symbolic Feedback CodeCEE3PT

CEE3910S The CEECENQ function wasinvoked in a non CICSenvironment.

ExplanationThe CEECENQ function is only available when runningin a CICS environment. The issuing application mustbe running under the CICS subsystem in order to usethis function.



Symbolic Feedback CodeCEE3Q6

CEE3911S The CEECENQ function is notsupported at this level of CICS.

ExplanationThe CEECENQ function is only available when runningin a CICS environment. The issuing application mustbe running under a CICS level that supports thisfunction.


Programmer responseUpgrade to a supported CICS level. This is an internalerror.


CEE3912S The CEECENQ function has failedduring an EXEC CICS ADDRESSEIB command.

ExplanationThe CEECENQ function has failed while trying to obtaina CICS EIB address via an EXEC CICS ADDRESS EIBcommand.




CEE3913S The CEECENQ function has failedduring an EXEC CICS ENQcommand.

ExplanationThe CEECENQ function has failed while issuing anEXEC CICS ENQ command.




CEE3914I The CEECENQ function is unableto enqueue on the specifiedresource.


ExplanationThe CEECENQ function has received a response froman EXEC CICS ENQ command indicating that theresource is unavailable.


Programmer responseThe resource is not available at this time.

Symbolic Feedback CodeCEE3QA

CEE3915S The CEECDEQ function is notsupported at this level of CICS.

ExplanationThe CEECDEQ function is only available when runningin a CICS environment. The issuing application mustbe running under a CICS level that supports thisfunction.


Programmer responseUpgrade to a supported CICS level. This is an internalerror.

Symbolic Feedback CodeCEE3QB

CEE3916S The CEECDEQ function has failedduring an EXEC CICS ADDRESSEIB command.

ExplanationThe CEECDEQ function has failed while trying to obtaina CICS EIB address via an EXEC CICS ADDRESS EIBcommand.



Symbolic Feedback CodeCEE3QC

CEE3917S The CEECDEQ function has failedduring an EXEC CICS DEQcommand.

ExplanationThe CEECDEQ function has failed while issuing anEXEC CICS DEQ command.



Symbolic Feedback CodeCEE3QD

CEE3918I The CEECDEQ function is unableto dequeue using the specifiedduration value.

ExplanationThe CEECDEQ function has been invoked with aduration period that does not match the durationperiod that was specified on the correspondingenqueue for the named resource.



Symbolic Feedback CodeCEE3QE

CEE3919S The CEECDEQ function wasinvoked in a non CICSenvironment.

ExplanationThe CEECDEQ function is only available when runningin a CICS environment. The issuing application mustbe running under the CICS subsystem in order to usethis function.




Symbolic Feedback CodeCEE3QF

CEE3930W The input value input_value ina call to the callable servicecallable_service_name was notwithin the valid range.

ExplanationThe input value specified lies outside the valid range.

System actionThe request is ignored. Processing continues.

Programmer responseCheck the documentation to determine the range ofvalues.

Symbolic Feedback CodeCEE3QQ

CEE3931W CEEDLYM was invoked in a CICSenvironment.

ExplanationThe CEEDLYM callable service cannot be used in aCICS environment.



Symbolic Feedback CodeCEE3QR

CEE3932W The system service system_servicefailed with return code return_codeand reason code reason_code.

ExplanationThe call to the system service failed. The return codeand reason code (if the service provided a reasoncode) were returned.


Programmer responseCheck the documentation for the system service todetermine the appropriate action to take for this returncode and reason code. Consult with your systemsupport personnel if necessary.

Symbolic Feedback CodeCEE3QS

CEE3935I The STDENV data set specifies anunsupported data set type.

ExplanationLanguage Environment was unable to read the dataset specified as the DD:STDENV due to it being in anunsupported format.

System actionThe invalid DD:STDENV dataset is ignored, theenvironment variables specified within it are not readin, and execution continues as normal.

Programmer responseMake sure that the specified dataset is in a supportedformat.

Symbolic Feedback CodeCEE3QV

CEE4001S General Failure: Service could notbe completed.

ExplanationAn error was encountered attempting to complete aC/370 locale function.




Symbolic Feedback CodeCEE3T1

CEE4015S Input Error: The number ofcharacters to be transformed mustbe greater than zero.

ExplanationAn error was encountered attempting to complete aC/370 locale function. The CEESTXF callable servicewas called with a number parameter that was non-positive.


Programmer responseMake sure the parameter is positive.

Symbolic Feedback CodeCEE3TF

CEE4086S Input Error: The number ofcharacters to be formatted mustbe greater than zero.

ExplanationAn error was encountered attempting to completea C/370 locale function. The CEEFMON or CEEFTDScallable service was called with a maxsize parameterthat was non-positive.


Programmer responseMake sure the parameter is positive.

Symbolic Feedback CodeCEE3VM

CEE4087S Input Error: The version_infocontrol block contains a numberthat is not valid.

ExplanationAn error was encountered attempting to completea C/370 locale function. The CEELCNV or CEEQDTCcallable service was called with a parameter thatpointed to a an invalid version number.


Programmer responseMake sure the parameter points to a version_infocontrol block that contains a correct version number.

Symbolic Feedback CodeCEE3VN

CEE5001S POSIX function was not available.POSIX(ON) run-time option mustbe in effect and UNIX SystemServices started.

ExplanationThe requested POSIX service failed because thePOSIX(ON) run-time option was not in effect and/orUNIX System Services were not started.


Programmer responseSpecify the POSIX(ON) run-time option and/or contactyour system programmer to start the UNIX SystemServices.

Symbolic Feedback CodeCEE4S9

CEE5002S POSIX function was not available.UNIX System Services were notstarted.

ExplanationThe requested POSIX service failed because the UNIXSystem Services were not started.



Programmer responseContact your system programmer to start the UNIXSystem Services.

Symbolic Feedback CodeCEE4SA

CEE5101C During initialization, the callableservice BPX1MSS failed. Thesystem return code wasreturn_code; the reason code wasreason_code. The application willbe terminated.

ExplanationThe callable service BPX1MSS failed with return codereturn_code and reason code reason_code.


Programmer responseSee z/OS UNIX System Services Programming:Assembler Callable Services Reference for theappropriate action to take for this return code andreason code. Consult with your z/OS UNIX SystemServices (z/OS UNIX) support personnel if necessary.One possibility is the application was not authorizedto use z/OS UNIX. If this is true, contact your systemadministrator to have the ID registered with z/OS UNIXto use these services.

Symbolic Feedback CodeCEE4VD

CEE5102E A request to dump process andenclave information could not beguaranteed to be consistent due tosystem constraints.

ExplanationA call to dump services was made in a multithreadenvironment, but the QUIESCE_FREEZE feature of thecallable service BPX1PTQ was not available on therelease that was running.

System actionA dump is taken with unpredictable results.

Programmer responseCheck that the level of UNIX System Services youare running supports the QUIESCE_FREEZE feature ofthe UNIX System Services callable service BPX1PTQ.QUIESCE_FREEZE is an UNIX System Services Release2 feature.

Symbolic Feedback CodeCEE4VE

CEE5103W The dump service was busy.

ExplanationA call to dump services was made in a multithreadenvironment while another thread had requested thatall threads be frozen.

System actionNo dump is taken. The thread is not terminated.

Programmer responseTo dump your active thread, put the call to the dumpservice in a loop that iterates until the dump issuccessful. However, dump information for your threadmight already be in the dump report due to anotherthread requesting a dump of all threads in the process.

Symbolic Feedback CodeCEE4VF

CEE5104S The callable service BPX1PTQfailed. The system return code wasreturn_code, the reason code wasreason_code.

ExplanationThe callable service, BPX1PTQ, is called by LanguageEnvironment to freeze and unfreeze threads. If thisservice fails, Language Environment will return thereturn_code and reason_code.


Programmer responseLook up the return code and reason code in z/OS UNIXSystem Services Programming: Assembler CallableServices Reference and take the appropriate action.It is possible that the service failed due to thefact that another thread had already given a freeze


request. Consult with your system support personnel ifnecessary.

Symbolic Feedback CodeCEE4VG

CEE5105S A call was made tocallable_service_name without thethread being frozen.

ExplanationA call was made to the CWI callable_service_namewith a caaptr parameter which pointed to a CAApointer of a thread that was not frozen.


Programmer responseConsult with your system support personnel.

Symbolic Feedback CodeCEE4VH

CEE5106S A call was made tocallable_service_name with aninvalid caaptr parameter.

ExplanationA call was made to the CWI callable_service_namewith a caaptr parameter which didn't point to a validCAA.


Programmer responseConsult with your system support personnel.

Symbolic Feedback CodeCEE4VI

CEE5151S The POSIX fork() function couldnot operate on the LanguageEnvironment member ID numbermember_id.

ExplanationThe Language Environment member cannot be theobject of a fork() or vfork() function. This messageis issued from within a single-thread environment.In a multithread environment, message CEE5154S isissued.


Programmer responseMake sure that the member can be the object of afork() or vfork() function before issuing the function.


CEE5152S The callable service BPX1FRKfor the fork function wasunsuccessful. The system returncode was return_code, the reasoncode was reason_code.

ExplanationThe callable service BPX1FRK for the fork() or vfork()function failed. The system return code and reasoncode were returned. The return_code and reason_codefields are decimal numbers.


Programmer responseSee z/OS UNIX System Services Programming:Assembler Callable Services Reference for theappropriate action to take for this return code andreason code. Consult with your system supportpersonnel if necessary.


CEE5154S The requested fork() service failedbecause it was invoked from amultithread environment.


ExplanationThe vfork() and exec() services can be invoked onlyfrom within a single-thread environment. The fork()service is not permitted from within a multithreadenvironment where the application contains a highlevel language other than C/C++. A multithreadfork() is not allowed in a Language Environmentpreinitialization (CEEPIPI) environment.


Programmer responseTry the requested service in a single-threadenvironment, use supported high level languages,and/or avoid using fork() in a multithread CEEPIPIenvironment.


CEE5155S The callable service BPX1SPNfor the spawn function wasunsuccessful. The system returncode was return_code, the reasoncode was reason_code.

ExplanationThe callable service BPX1SPN for the spawn() orspawnp() function failed. The system return codeand reason code were returned. The return_code andreason_code fields are decimal numbers.




CEE5161S The callable service BPX1EXC forthe exec() family function wasunsuccessful. The system return

code was return_code, the reasoncode was reason_code.

ExplanationThe callable service BPX1EXC for the exec() familyfunction failed. The system return code and reasoncode were returned.




CEE5162S The environment variable,_CEE_RUNOPTS, was too long.

ExplanationDuring exec() processing, Language Environmentpropagated run-time options from the program issuingthe exec() by concatenating all run-time optionsthat were specified on invocation of this programwith those specified in the environment variable_CEE_RUNOPTS. The size of the work area used toperform this concatenation was insufficient.

System actionexec() family function failed.

Programmer responseVerify that the value of the _CEE_RUNOPTSenvironment variable does not contain superfluousblanks or invalid run-time options.


CEE5176S There was insufficient storage toprocess an environment variable.


ExplanationThe environment variable processing service wascalled, however, there was insufficient system storageavailable to process the request.


Programmer responseAdditional system storage is required before moreenvironment variables can be processed. Either freesome heap storage or rerun the application with alarger region size.


CEE5177S A bad input character wasdetected for the environmentvariable name.

ExplanationThe environment variable processing service wascalled, however, the name specified contained aninvalid "=" character.


Programmer responseCorrect the environment variable name and retry.


CEE5178S The environment variable anchoror array contained an invalidaddress.

ExplanationThe environment variable processing service wascalled, however, an invalid anchor or array address wasencountered.


Programmer responseFor C/C++ programmers: If **environ is used to setor clear an environment variable, make sure that theaddress is correct.


CEE5179S A parameter to the environmentvariable processing routinecontained an invalid value.

ExplanationThe environment variable processing service wascalled, however, one of the parameters specifiedcontained an invalid value. For instance, the namelength or value length was negative, or the functioncode was invalid.


Programmer responseCorrect the parameter and retry.


CEE5180I The specified environmentvariable name already exists.

ExplanationAn attempt was made to set an environment variablewhose name already exists, but overwrite was notspecified.

System actionThe original variable is not modified.

Programmer responseIf you want to modify the variable, specify functioncode 5.


CEE5201S The signal SIGFPE was received.


ExplanationA signal indicating an erroneous arithmetic operationwas raised.

System actionIf the signal is unhandled, the default action is toterminate the POSIX process and produce a tracebackor dump, depending on how the TERMTHDACT run-time option is set. The return code is set to 3000 andthe signal number for the process termination is set to8.



CEE5202S The signal SIGILL was received.

ExplanationA signal indicating an invalid hardware instruction wasraised.




CEE5203S The signal SIGSEGV was received.

ExplanationA signal indicating an invalid memory reference wasraised.

System actionIf the signal is unhandled, the default action is toterminate the POSIX process and produce a tracebackor dump, depending on how the TERMTHDACT run-time option is set. The return code is set to 3000 and

the signal number for the process termination is set to11.



CEE5204S The signal SIGABND was received.

ExplanationA signal indicating a user or system initiated abendwas raised.




CEE5205S The signal SIGTERM was received.

ExplanationA signal indicating a termination signal was raised.




CEE5206S The signal SIGINT was received.


ExplanationA signal indicating an interruptive attention signal wasraised.




CEE5207E The signal SIGABRT was received.

ExplanationA signal indicating an abnormal termination signal wasraised.

System actionIf the signal is unhandled, the default action is toterminate the enclave with a return code of 2000 andthe signal number for the process termination is set to3.



CEE5208S The signal SIGUSR1 was received.

ExplanationA signal indicating an application-defined signal 1 wasraised.

System actionIf the signal is unhandled, the default action is toterminate the enclave with a return code of 3000 andthe signal number for the process termination is set to16.



CEE5209S The signal SIGUSR2 was received.

ExplanationA signal indicating an application-defined signal 2 wasraised.




CEE5210S The signal SIGHUP was received.

ExplanationA signal indicating a hangup on the controlling terminalor the termination of the controlling process wasraised.




CEE5211S The signal SIGSTOP was received.


ExplanationA signal indicating a 'STOP' was raised. This signalcannot be caught or ignored.

System actionThe process is stopped.



CEE5212C The signal SIGKILL was received.

ExplanationA signal indicating a termination signal was raised.This signal cannot be caught or ignored.

System actionThe system abnormally terminates the process.



CEE5213S The signal SIGPIPE was received.

ExplanationA signal indicating a write to a pipe with no readerswas raised.




CEE5214S The signal SIGALRM was received.

ExplanationA signal was raised, indicating a timeout conditionsuch as initiated by the alarm() function.




CEE5215W The signal SIGCONT was received.

ExplanationA signal indicating a 'continue if stopped' signal wasraised.

System actionIf the default action is SIG_DFL, all stopped threads inthe process are continued.



CEE5216W The signal SIGCHLD was received.

ExplanationA signal indicating a terminated child process orstopped condition was raised.





CEE5217S The signal SIGTTIN was received.

ExplanationA signal was raised, indicating a read from a controlterminal attempted by a language run-time componentof a background process group condition.

System actionIf the default action is SIG_DFL, all threads in theprocess are stopped.



CEE5218S The signal SIGTTOU was received.

ExplanationA signal was raised, indicating a write to a controlterminal attempted by a language run-time componentof a background process group condition.




CEE5219W The signal SIGIO was received.

ExplanationA signal indicating the completion of an input or outputoperation was raised.




CEE5220S The signal SIGQUIT was received.

ExplanationA signal indicating an interruptive terminal signalrequesting the process termination was raised.

System actionIf the signal is unhandled, the default action is toterminate the enclave with a return code of 3000 andthe signal number for the process termination set to24.



CEE5221S The signal SIGTSTP was received.

ExplanationA signal was raised, indicating an interruptive stopsignal by a language run-time component of abackground process group condition.




CEE5222S The signal SIGTRAP was received.

ExplanationA signal indicating a trap condition was raised.

System actionIf the signal is unhandled, the default action is toterminate the enclave with a return code of 3000 andthe signal number for the process termination set to26.




CEE5223W The signal SIGIOERR wasreceived.

ExplanationA signal indicating an I/O error was raised.


Programmer responseSee z/OS XL C/C++ Programming Guide for informationon SIGIOERR and how to respond to this error.


CEE5224W The signal SIGDCE was received.

ExplanationDCE has been removed, as of z/OS V1R13. In previousz/OS releases, the SIGDCE signal was generatedas a result of a MODIFY DCEKERN,DEBUG pid=command. This command communicates to a DCE-enabled process that DCE runtime debug messagesshould be enabled. If the target process is not a DCEprocess, the target process does not know how tohandle SIGDCE.

System actionNo system action taken.



CEE5225S The signal SIGPOLL was received.

ExplanationThis signal indicates that a pollable event hasoccurred. If the signal is unhandled, the followingdefault action will be applied: The program (enclave)

is terminated and a traceback or dump is issueddepending on the TERMTHDACT run-time option. Thereturn code is set to 3000 and the signal number forthe process termination is set to 5.




CEE5226W The signal SIGURG was received.

ExplanationThis signal indicates that high bandwidth data isavailable at a socket.




CEE5227S The signal SIGBUS was received.

ExplanationThis signal indicates that a bus error has occurred. Ifthe signal is unhandled, the following default actionwill be applied: The program (enclave) is terminatedand a traceback or dump is issued depending onthe TERMTHDACT run-time option. The return codeis set to 3000 and the signal number for the processtermination is set to 10.



Symbolic Feedback CodeCEE53B


CEE5228S The signal SIGSYS was received.

ExplanationThis signal indicates that a bad system call wasdetected. If the signal is unhandled, the followingdefault action will be applied: The program (enclave)is terminated and a traceback or dump is issueddepending on the TERMTHDACT run-time option. Thereturn code is set to 3000 and the signal number forthe process termination is set to 12.



Symbolic Feedback CodeCEE53C

CEE5229W The signal SIGWINCH wasreceived.

ExplanationThis signal indicates that the window size haschanged.



Symbolic Feedback CodeCEE53D

CEE5230S The signal SIGXCPU was received.

ExplanationThis signal indicates that the CPU time limit has beenexceeded. If the signal is unhandled, the followingdefault action will be applied: The program (enclave)is terminated and a traceback or dump is issueddepending on the TERMTHDACT run-time option. Thereturn code is set to 3000 and the signal number forthe process termination is set to 29.




CEE5231S The signal SIGXFSZ was received.

ExplanationThis signal indicates that the file size limit has beenexceeded. If the signal is unhandled, the followingdefault action will be applied: The program (enclave)is terminated and a traceback or dump is issueddepending on the TERMTHDACT run-time option. Thereturn code is set to 3000 and the signal number forthe process termination is set to 30.




CEE5232S The signal SIGVTALRM wasreceived.

ExplanationThis signal indicates that a virtual timer has expired.If the signal is unhandled, the following default actionwill be applied: The program (enclave) is terminatedand a traceback or dump is issued depending onthe TERMTHDACT run-time option. The return codeis set to 3000 and the signal number for the processtermination is set to 31.




CEE5233S The signal SIGPROF was received.


ExplanationThis signal indicates that a profiling timer has expired.If the signal is unhandled, the following default actionwill be applied: The program (enclave) is terminatedand a traceback or dump is issued depending onthe TERMTHDACT run-time option. The return codeis set to 3000 and the signal number for the processtermination is set to 32.




CEE5234I The signal SIGDUMP was received.

ExplanationA signal indicating a dump signal was raised. Thissignal cannot be caught or ignored.

System actionThe system will obtain a user address space dump.



CEE5235I The signal SIGDANGER wasreceived.

ExplanationA signal indicating OMVS subsystem shutdown inprogress was received.




CEE5236I The signal SIGTHSTOP wasreceived.

ExplanationA signal indicating that a thread should be stoppedwas raised. This signal cannot be caught or ignored.

System actionThe specified thread will be stopped.



CEE5237I The signal SIGTHCONT wasreceived.

ExplanationA signal indicating a thread should be resumed wasraised. This signal cannot be caught or ignored.

System actionThe specified thread will be resumed.



CEE5238I The signal SIGTRACE wasreceived.

ExplanationA signal indicating a trace signal was raised. This signalcannot be caught or ignored.

System actionThe system toggles the UNIX System Services syscalltrace for the process or process group.




CEE5301S An invalid message number wasreceived by the internal signalhandling routine.

ExplanationThe message number specified in the condition tokenpassed to CEEOKILL was invalid. Only those messagenumbers that correspond to valid POSIX signals (5201through 5224) are allowed.




CEE5302S A signal could not be raised dueto a system-detected error, withreturn code error-code and reasoncode reason-code.

ExplanationThe Language Environment library routine calledthe callable services BPX1KIL (for kill or raise)or BPX1PTK (all others including pthread_kill andCEESGL) and the call was not successful. The systemreturn code and reason code were returned. The error-code is a decimal number, and the reason-code ishexadecimal.




CEE5401S The function code func_code toCEEMPMSG was invalid.

ExplanationA call to CEEMPMSG, the message handler, had aninvalid function code.


Programmer responseReport the error to your system support personnel.


CEE5402I The callable service BPX1OPN,when invoked to open themessage file, was unsuccessful.The system return code wasposix_rc, the reason code wasposix_rsn.

ExplanationThe callable service BPX1OPN, when invoked to openthe message file, failed. The system return codeand reason code were returned. The posix_rc andposix_rsn fields are decimal numbers.




CEE5403I The callable service BPX1WRT,when invoked to write to themessage file, was unsuccessful.The system return code wasposix_rc; the reason code wasposix_rsn.


ExplanationThe callable service BPX1WRT, when invoked to writeto the message file, failed. The system return codeand reason code were returned. The posix_rc andposix_rsn fields are decimal numbers.




CEE5404I The callable service BPX1CLO,when invoked to close themessage file, was unsuccessful.The system return code wasposix_rc; the reason code wasposix_rsn.

ExplanationThe callable service BPX1CLO, when invoked to closethe message file, failed. The system return codeand reason code were returned. The posix_rc andposix_rsn fields are decimal numbers.




CEE5405I The callable service BPX1GCW,when invoked to determine thecurrent working directory, wasunsuccessful. The system returncode was posix_rc; the reasoncode was posix_rsn.

ExplanationThe callable service BPX1GCW, when invoked todetermine the current working directory, failed. Thesystem return code and reason code were returned.The posix_rc and posix_rsn fields are decimalnumbers.

System actionNo Language Environment dump taken.

Programmer responseSee z/OS UNIX System Services Programming:Assembler Callable Services Reference for theappropriate action to take for this return code andreason code.


CEE5526S There was not enough storage tocreate the new key.

ExplanationThere was not enough storage to create the new key.Keys are allocated in heap storage.


Programmer responseIncrease the storage allocation available to theexecution of the program by either freeing some heapstorage or rerunning the application with a largerregion size.

Symbolic Feedback CodeCEE5CM

CEE5527S The key namespace wasexhausted.

ExplanationThe maximum number of keys allowed have beencreated.



Programmer responseUse the sysconf() function to determine themaximum number of keys that can be created withinan enclave. Do not exceed this limit.

Symbolic Feedback CodeCEE5CN

CEE5528S Termination was in progress. Keycreates were not allowed.

ExplanationKey creates (CEEOPKC) calls were not allowed duringthread termination after all destructor routines havebeen executed.



Symbolic Feedback CodeCEE5CO

CEE5529S There was no storage to bind valueto the key.

ExplanationThere was not enough storage available in the addressspace to acquire sufficient heap storage to satisfy theCEEOPSS call.


Programmer responseEither free some heap storage or rerun the applicationwith a larger region size.

Symbolic Feedback CodeCEE5CP

CEE5530S The specified key ID was invalid.

ExplanationThe key identifier passed on the call to internalservices CEEOPSS or CEEOPGS did not refer to a validkey.


Programmer responseBefore setting or getting the value associated witha key, the key must be created using the internalCEEOPKC service.

Symbolic Feedback CodeCEE5CQ

CEE5531S The key set was not allowed.

ExplanationKey set operation (CEEOPSS) calls were not allowedduring thread termination after all destructor routineshad been executed.



Symbolic Feedback CodeCEE5CR

CEE5532S The key get was not allowed.

ExplanationKey gets (CEEOPGS) calls were not allowed duringthread termination after all destructor routines hadbeen executed.




Symbolic Feedback CodeCEE5CS

CEE5533S An invalid key pointer was passedin key create operation.

ExplanationThe pointer to the storage location for which the newlycreated key was to be placed was invalid.

System actionThe key create is not performed.


Symbolic Feedback CodeCEE5CT

CEE5551S The array entry described by theslot parameter was already set.

ExplanationConditional invocation of CEEOSETE internal servicefailed because the array entry described by theslot parameter was already set. The slot parameterdescribed an array entry that was already in use. Theentry can be set by using UNCONDITIONAL form ofthis CWI.

System actionThe entry is not set.


Symbolic Feedback CodeCEE5DF

CEE5552S The array entry described by theslot parameter was invalid or wasreserved.

ExplanationInvocation of the CEESETE internal service failedbecause the array entry described by the slotparameter was invalid or was reserved. The slotparameter described an array entry that wasunavailable for use. The value of slot was invalid.


Programmer responseChoose a value for slot that is not reserved.

Symbolic Feedback CodeCEE5DG

CEE5553S The callable service BPX1IPT (runa program on the IPT task) wasunsuccessful. The system returncode was return_code; the reasoncode was reason_code.

ExplanationThe callable service BPX1IPT (run a program on theIPT task) failed. The system return code and reasoncode were returned. The return_code and reason_codefields are decimal numbers.



Symbolic Feedback CodeCEE5DH

CEE5601S The attributes object parameterdid not contain a valid initializedattributes object (POSIX PTAT).

ExplanationEach routine for which the thread attributes objectwas a parameter checks certain fields in that objectto verify that they contain valid values. If any of thefields that were checked by the routine contained aninvalid value, this condition was raised.



Programmer responseModify the calling program to pass a valid parameterobject.


CEE5602S The detachstate parameter did notcontain a valid value.

ExplanationThe detachstate parameter must be a fullwordcontaining binary 0 for undetached or 1 for detached.


Programmer responseModify the calling program to pass a valid parametervalue.


CEE5603S The threadweight parameter didnot contain a valid value.

ExplanationThe threadweight parameter must be a fullwordcontaining binary 0 for heavy-weight, or 1 for medium-weight.




CEE5604S A new thread could not be createddue to a system-detected error,with error code error-code andreason code reason-code.

ExplanationThe Language Environment library routine called UNIXSystem Services and failed. The error code and reasoncode were returned. The error-code and reason-codefields are decimal numbers.


Programmer responseSee z/OS UNIX System Services Programming:Assembler Callable Services Reference or z/VM:OpenExtensions Callable Services Reference for theappropriate action to take for this error code andreason code. Consult with your system supportpersonnel if necessary.


CEE5605S A new thread could not be createddue to an insufficient storagecondition.

ExplanationStorage resource was insufficient for a new thread tobe created.


Programmer responseUse a larger region size or release some heap storage,and retry the application.


CEE5606S The callable service BPX1PTJfailed due to an invalid threadID on a join request. The systemreturn code was return_code; thereason code was reason_code.

ExplanationThe callable service BPX1PTJ was called by theLanguage Environment internal join service CEEOPJto wait for a thread to terminate. However, BPX1PTJ


returned without waiting because the ID of the targetthread specified on the join request was invalid.The return_code and reason_code fields are decimalnumbers.


Programmer responseSee z/OS UNIX System Services Programming:Assembler Callable Services Reference or z/VM:OpenExtensions Callable Services Reference for theappropriate action to take for this return code andreason code. Consult with your system supportpersonnel if necessary.


CEE5607S The callable service BPX1PTJfailed due to an invalid threadID on a join request. The systemreturn code was return_code; thereason code was reason_code.

ExplanationThe callable service BPX1PTJ was called by theLanguage Environment internal join service CEEOPJto wait for a thread to terminate. However, BPX1PTJreturned without waiting because the ID of the targetthread specified on the join request was the sameas the ID of the calling thread that would result in adeadlock condition. The return_code and reason_codefields are decimal numbers.




CEE5608S The callable service BPX1PTJfailed during a thread join request.The system return code wasreturn_code; the reason code wasreason_code.

ExplanationThe callable service BPX1PTJ was called by theLanguage Environment internal join service CEEOPJto wait for a thread to terminate. However, BPX1PTJreturned without waiting. The return_code andreason_code fields are decimal numbers.




CEE5609S The callable service BPX1PTJfailed during a thread join request.The system return code wasreturn_code; the reason code wasreason_code.

ExplanationThe callable service BPX1PTJ was called by theLanguage Environment internal join service CEEOPJto wait for a thread to terminate. However, BPX1PTJreturned without waiting indicating the target threadwas not in an undetached state and could not bejoined. The return_code and reason_code fields aredecimal numbers.


Programmer responseSee z/OS UNIX System Services Programming:Assembler Callable Services Reference or z/VM:OpenExtensions Callable Services Reference for the


appropriate action to take for this return code andreason code. Consult with your system supportpersonnel if necessary.


CEE5612S The stacksize parameter did notcontain a valid value.

ExplanationThe stacksize parameter must be a fullword containinga binary number that is greater than or equal to zero.If positive, it specifies the number of bytes to be usedfor the stack. If 0, it specifies that 1/2 of all availablestorage should be used for the stack.



Symbolic Feedback CodeCEE5FC

CEE5613S The synctype parameter did notcontain a valid value.

ExplanationThe synctype parameter must be a fullword containingbinary 0 for synchronous.



Symbolic Feedback CodeCEE5FD

CEE5626S There was insufficient storage forcleanup push operation.

ExplanationThe internal service CEEOPCPU failed while tryingto acquire heap storage for the cleanup routineregistration.


Programmer responseEither free some heap storage or rerun the applicationwith a larger region size.

Symbolic Feedback CodeCEE5FQ

CEE5627S Cleanup push was not allowedduring thread termination.

ExplanationCleanup routine push operations (CEEOPCPU) werenot allowed during thread termination after all cleanuproutines have been executed.



Symbolic Feedback CodeCEE5FR

CEE5628S The cleanup pop was not allowedduring thread termination.

ExplanationCleanup routine pop operations (CEEOPCPO) were notallowed during thread termination after all cleanuproutines have been executed.




Symbolic Feedback CodeCEE5FS

CEE5629S The cleanup stack was empty.

ExplanationThe internal service CEEOPCPO failed because therewere no cleanup routines available. The cleanup stackwas empty.



Symbolic Feedback CodeCEE5FT

CEE5651S The oncecontrol parameter did notcontain a valid value.

ExplanationThe oncecontrol parameter must be a fullwordcontaining binary 0 for initial value, or one of theother defined but not externalized values set by thepthread_once routine.


Programmer responseModify the calling program to pass a valid parametervalue. oncecontrol should be initialized by the caller toPTHREAD_ONCE_INIT(0). After initialization, it shouldnot be modified directly but only by calling thepthread_once routine. It should not be tested directlyby the caller, but only implicitly by calling thepthread_once routine.

Symbolic Feedback CodeCEE5GJ

CEE5701S The mutex object was notinitialized.

ExplanationThe mutex-related service that was invoked requiresthe mutex object specified as a parameter beinitialized.


Programmer responseUse the internal service CEEOPMI to initialize themutex object before invoking the service that failed.


CEE5702S The mutex was already owned.

ExplanationA thread invoked the mutex lock internal serviceCEEOPML specifying a nonrecursive mutex that hadalready been locked by the thread. Only a mutex thathad been given the attribute RECURSIVE can be lockedmultiple times by the same thread.




CEE5703S An addressing exception occurredreferencing a mutex object ormutex attribute object.

ExplanationThe address of a mutex object or mutex attributeobject passed as an parameter on a mutex relatedservice call was invalid. An addressing exceptionprogram interrupt occurred when the called servicereferenced this address.



Programmer responseSpecify the correct mutex object or mutex attributeobject when passing parameters to the mutex-relatedservice call.


CEE5704C An addressing exception occurredreferencing system storageallocated for mutexes.

ExplanationAn addressing exception program interrupt occurredwhen a mutex-related service referenced systemstorage allocated for mutexes.


Programmer responseMake sure that the application has not written oversystem storage before issuing the service call.


CEE5705S A mutex object has been changedsince it was initialized.

ExplanationThe mutex destroy internal service CEEOPMD detectedthat a mutex object (specified as a parameter)had changed since it was initialized by the mutexinitialization internal service CEEOPMI. The mutexwas destroyed, but internal service CEEOPMD did notalter the storage associated with the mutex object.However, if internal service CEEOPMI was invoked, thestorage was altered.


Programmer responseMake sure the application is not incorrectly reusingstorage associated with the mutex object afterinitializing it.


CEE5706S The mutex was not owned bythread.

ExplanationA thread called the mutex unlock internal serviceCEEOPMU to unlock the mutex but the mutex was notowned by the thread. A thread acquired a mutex withthe mutex lock internal service CEEOPML or mutextrylock internal service CEEOPMT and was said to ownthe lock.


Programmer responseStructure the application so that the thread that locksthe mutex also unlocks the mutex.

Symbolic Feedback CodeCEE5IA

CEE5707I The mutex was busy.

ExplanationThe mutex trylock internal service CEEOPMT wasinvoked to lock a nonrecursive mutex that was alreadylocked.



Symbolic Feedback CodeCEE5IB

CEE5708S The mutex object was alreadyinitialized.

ExplanationThe mutex initialization internal service CEEOPMI wascalled to initialize a mutex object that had alreadybeen initialized.


System actionThe request is rejected.

Programmer responseCall the mutex destroy internal service CEEOPMD todestroy an initialized mutex object before initializing itagain.

Symbolic Feedback CodeCEE5IC

CEE5709S The mutex attribute object wasnot initialized.

ExplanationThe mutex attribute-related services required that themutex attribute object specified as an parameter beinitialized.


Programmer responseUse internal service CEEOPXI to initialize the mutexattribute object before invoking the service that failed.

Symbolic Feedback CodeCEE5ID

CEE5710S There was insufficient storage toinitialize a mutex object.

ExplanationThe mutex initialization internal service CEEOPMI wascalled to initialize a mutex object. However, there wasinsufficient system storage available.


Programmer responseGet additional system storage before initializing moremutex objects.

Symbolic Feedback CodeCEE5IE

CEE5711S A mutex attribute object has beenchanged since it was initialized.

ExplanationThe mutex attribute destroy internal service CEEOPXDdetected that a mutex attribute object specified as aparameter was changed since it was initialized by themutex attribute initialization internal service CEEOPXI.The mutex attribute object was destroyed, but internalservice CEEOPXD did not alter the storage associatedwith the mutex attribute object. However, if internalservice CEEOPXI was invoked, the storage was altered.


Programmer responseMake sure the application is not incorrectly reusingstorage associated with the mutex attribute objectafter initializing it.

Symbolic Feedback CodeCEE5IF

CEE5712S The mutex attribute object wasalready initialized.

ExplanationThe mutex attribute initialization internal serviceCEEOPXI was called to initialize a mutex attributeobject that had already been initialized.


Programmer responseCall the mutex attribute destroy internal serviceCEEOPXD to destroy an initialized mutex attributeobject before initialized it again.

Symbolic Feedback CodeCEE5IG

CEE5713S There was insufficient storage toinitialize a mutex attribute object.


ExplanationThe mutex attribute initialization internal serviceCEEOPXI was called to initialize a mutex attributeobject. However, there was insufficient system storageavailable.


Programmer responseAcquire additional system storage before initializingmore mutex attribute objects.

Symbolic Feedback CodeCEE5IH

CEE5714S The mutex was busy.

ExplanationThe mutex destroy internal service CEEOPMD wasinvoked to destroy a mutex that was in use. A mutexthat was locked or associated with a condition wait ortimed wait cannot be destroyed.


Programmer responseVerify that your applications owns the mutex beforecalling CEEOPMD to destroy the mutex.

Symbolic Feedback CodeCEE5II

CEE5715S An addressing exception occurredwhile referencing attribute kindstorage.

ExplanationThe address where to return attribute kind thatwas passed as an parameter on a getkind_npservice request, was invalid. An addressing exceptionoccurred when the getkind_np service CEEOPXattempted to store the attribute kind value at thisaddress.


Programmer responseSpecify the correct attribute kind address parameteron the getkind_np service call.

Symbolic Feedback CodeCEE5IJ

CEE5716C System mutex storage could notbe freed.

ExplanationThe destroy mutex internal service CEEOPMD wasunable to free storage allocated for a mutex by themutex initialization service CEEOPMI.

System actionThread is terminated.

Programmer responseCheck if the application might have written oversystem storage. Report this problem to the storageadministrator.

Symbolic Feedback CodeCEE5IK

CEE5717C System mutex attribute storagecould not be freed.

ExplanationThe destroy mutex attribute internal service CEEOPXDwas unable to free storage allocated for a mutexattribute by the mutex attribute initialization serviceCEEOPXI.


Programmer responseCheck if the application might have written oversystem storage. Report this problem to the systemadministrator.

Symbolic Feedback CodeCEE5IL

CEE5718C There was invalid mutex attributestorage.


ExplanationThe mutex attribute getkind_np internal serviceCEEOPXG found an invalid value in system storage formutex attributes.



Symbolic Feedback CodeCEE5IM

CEE5719S There was an invalid attributevalue.

ExplanationThe attribute kind parameter in a call to internalservice CEEOPXS specified an invalid attribute kindvalue. Valid values for setkind_np are NONRECURSIVE(0), RECURSIVE (1), NONRECURSIVE + NODEBUG (2),and RECURSIVE + NODEBUG (3).


Programmer responseSpecify a correct attribute kind value.

Symbolic Feedback CodeCEE5IN

CEE5720C A thread waiting for a mutex wasforced to terminate.

ExplanationAn event, such as the initial thread terminating, forcedall threads to terminate including threads waiting for amutex.


Programmer responseCheck that all threads exit correctly.

Symbolic Feedback CodeCEE5IO

CEE5721C There was insufficient resource toinitialize another mutex.

ExplanationThe mutex init internal service, CEEOPMI, was invokedto initialize a mutex, but not enough resource wasavailable to initialize another mutex.



Symbolic Feedback CodeCEE5IP

CEE5722I There was insufficient privilege toinitialize the mutex.

ExplanationThe mutex init internal service, CEEOPMI, was invokedto initialize a mutex, but not enough resource wasavailable to initialize another mutex.



Symbolic Feedback CodeCEE5IP

CEE5724I There was insufficient resource toobtain the mutex.

ExplanationThe mutex lock or trylock internal services CEEOPMLor CEEOPMT was invoked to lock a recursive mutex,but not enough resource was available to obtain thisrecursive mutex another time.




Symbolic Feedback CodeCEE5IS

CEE5726S The condition object was notinitialized.

ExplanationThe condition-related service required that thecondition object (specified as an parameter) beinitialized.


Programmer responseUse internal service CEEOPCI to initialize the conditionobject before invoking the service that failed.

Symbolic Feedback CodeCEE5IU

CEE5727S The condition signal service(CEEOPCS) failed due to a systemdetected error with error codereturn-code and reason codereason-code.

ExplanationOne of the following:

• The condition signal internal service CEEOPCS calledthe callable service BPX1CPO to signal anotherthread waiting on the condition. BPX1CPO returnedan unexpected error code and reason code.

• The condition signal internal service (CEEOPCS) orthe condition broadcast internal service (CEEOPCB)called the IEAVRLS service to signal another threadwaiting on the condition. IEAVRLS returned anunexpected return code. In the message, the reasoncode field is always zero when IEAVRLS is used.


Programmer responseReport this failure to your system administrator.

Symbolic Feedback CodeCEE5IV

CEE5728C An addressing exception occurredreferencing system storage relatedto conditions variables.

ExplanationAn addressing exception program interrupt occurredwhen a condition variable related service referencedsystem storage allocated for a condition variable.

System actionThe thread on which the addressing exceptionoccurred is terminated.


Symbolic Feedback CodeCEE5J0

CEE5729S The mutex specified on a conditionwait or timed wait request was arecursive mutex. The request wasrejected.

ExplanationThe condition wait internal service CEEOPCW andcondition timed wait internal service CEEOPCT did notaccept a request since the mutex associated with therequest was recursive.


Programmer responseDo not specify a mutex with the recursive attribute ona condition wait or timed wait request.



CEE5730S The mutex specified on a conditionwait or timed wait requestwas a different mutex than theone already associated with thecondition variable. The requestwas rejected.

ExplanationDifferent threads called the condition wait internalservice CEEOPCW or condition timed wait internalservice CEEOPCT and specified the same conditionobject but different mutexes on the requests.


Programmer responseMake sure that all threads waiting on a particularcondition variable specify the same mutex in theircondition wait or timed wait requests.


CEE5731S The condition wait service ortimed wait service failed due to asystem detected error with errorcode return-code and reason codereason-code.

ExplanationThe condition wait internal service CEEOPCW or timedwait internal service CEEOPCT called the callableservice BPX1CSE to set up for a condition wait.BPX1CSE returned an unexpected error code andreason code.




CEE5732S The condition wait service faileddue to a system detected errorwith error code return-code andreason code reason-code.

ExplanationThe condition wait internal service CEEOPCW calledthe callable service BPX1CWA to block a thread.BPX1CWA returned an unexpected error code andreason code.




CEE5733S The value specified for numberof seconds to wait was invalid.The condition wait request wasrejected.

ExplanationThe value for number of seconds to wait that waspassed to the condition timed wait internal serviceCEEOPCT must be a non-negative number of secondssince midnight, January 1, 1970. This value cannotexceed 2,147,483,647 seconds.


Programmer responseTime to wait should be specified as current calendarin seconds since midnight, January 1, 1970. Be surethe service you are using to get current calendar timereturns seconds since midnight, January 1, 1970, orthat your program is correctly converting the valueobtained.


CEE5734S The value specified for number ofnanoseconds to wait was invalid.


The condition wait request wasrejected.

ExplanationThe value for number of nanoseconds to wait that waspassed to the condition timed wait internal serviceCEEOPCT must be a non-negative number that doesnot exceed 1,000,000,000 (1,000 million).


Programmer responseBe sure to initialize the nanosecond parameter to avalue in the range 0 to 1,000,000,000 before invokingthe condition wait service.


CEE5735S The value for current calendartime was invalid. The conditionwait request was rejected.

ExplanationThe system time of day (TOD) clock was not properlyinitialized or had overflowed. The value for currentcalendar time returned to the condition timed waitinternal service CEEOPCT by the store clock (STCK)instruction was invalid.

System actionThe condition wait is rejected.

Programmer responseReport this problem to your system administrator.


CEE5736I The time to wait specified on acondition timed wait request haselapsed.

ExplanationCurrent® calendar time in seconds since midnight,January 1, 1970, was equal to or greater than the timeto wait. The time to wait was specified to the conditiontimed wait internal service CEEOPCT in seconds plus

nanoseconds. Internal service CEEOPCT returned toallow the thread to continue processing.


Programmer responseBe sure you are specifying seconds to wait as currentcalendar time in seconds since midnight, January 1,1970, plus some additional number of seconds.


CEE5737S The condition timed wait servicefailed due to a system error witherror code return-code and reasoncode reason-code.

ExplanationThe condition timed wait internal service CEEOPCTcalled the callable service CPX1CTW to block a thread.CPX1CTW returned an unexpected error code andreason code.




CEE5738S The condition attribute object wasalready initialized.

ExplanationThe condition attribute initialization internal serviceCEEOPDI was called to initialize a condition attributeobject that had already been initialized.


Programmer responseCall the condition attribute destroy internal serviceCEEOPDD to destroy an initialized condition attribute


object before calling internal service CEEOPDI toinitializing it.

Symbolic Feedback CodeCEE5JA

CEE5739S There was insufficient storageto initialize a condition attributeobject.

ExplanationThe condition attribute initialization internal serviceCEEOPDI was called to initialize a condition attributeobject. However, there was insufficient system storageavailable to do so.


Programmer responseAdditional system storage is required beforeattempting to initialize more condition attributeobjects.

Symbolic Feedback CodeCEE5JB

CEE5740S An addressing exception occurredreferencing condition object orcondition attribute object.

ExplanationThe address of a condition object or conditionattribute object passed as an parameter on a conditionvariable related service call was invalid. An addressingexception program interrupt occurred when the calledservice referenced this address.


Programmer responseMake sure the application correctly specifies thecondition object or condition attribute objectparameter in the service call.

Symbolic Feedback CodeCEE5JC

CEE5741C The system condition attributestorage could not be freed.

ExplanationThe destroy condition attribute internal serviceCEEOPDD was unable to free storage allocatedfor a condition attribute by the condition attributeinitialization internal service CEEOPDI.


Programmer responseCheck if the application might have written oversystem storage. Report this problem to your systemadministrator.

Symbolic Feedback CodeCEE5JD

CEE5742S The condition object was alreadyinitialized.

ExplanationThe condition initialization internal service CEEOPCIwas called to initialize a condition object that hadalready been initialized.


Programmer responseCall the condition destroy internal service CEEOPCDto destroy an initialized condition object beforeinitializing it again.

Symbolic Feedback CodeCEE5JE

CEE5743S The condition attribute object wasnot initialized.

ExplanationAn uninitialized condition attribute object wasspecified as an parameter on a call to the conditioninitialization internal service CEEOPCI.



Programmer responseCall internal service CEEOPDI to initialize the conditionattribute object before invoking internal serviceCEEOPCI.

Symbolic Feedback CodeCEE5JF

CEE5744S There was insufficient storage toinitialize a condition object.

ExplanationThe condition initialization internal service CEEOPCIwas called to initialize a condition object. However,there was insufficient system storage available to doso.


Programmer responseGet additional system storage before initializing morecondition objects.

Symbolic Feedback CodeCEE5JG

CEE5745C The system condition variablestorage could not be freed.

ExplanationThe destroy condition internal service CEEOPCD wasunable to free storage allocated for a conditionvariable by the condition initialization internal serviceCEEOPCI.



Symbolic Feedback CodeCEE5JH

CEE5746S A condition attribute object hadbeen changed since it wasinitialized.

ExplanationThe condition attribute destroy internal serviceCEEOPDD detected that a condition attribute object(specified as a parameter) had changed since itwas initialized by the condition attribute initializationinternal service CEEOPDI. The condition attributeobject was destroyed, but internal service CEEOPDDdid not alter the storage associated with the conditionattribute object. However, if internal service CEEOPDIwas invoked, the storage was altered.


Programmer responseCheck that the application is correctly reusing storageassociated with the condition attribute object afterinitializing it.

Symbolic Feedback CodeCEE5JI

CEE5747S The condition variable was busy.

ExplanationThe condition destroy internal service CEEOPDD wasinvoked to destroy a condition variable that was in use.A condition variable that was in use by one or morethreads for a condition wait or timed wait cannot bedestroyed.


Programmer responseRetry the request or determine why the conditionvariable is in use.

Symbolic Feedback CodeCEE5JJ

CEE5748S A condition object had beenchanged since it was initialized.


ExplanationThe condition destroy service CEEOPCD detected thata condition object (specified as a parameter) waschanged since it was initialized by the conditioninitialization internal service CEEOPCI. The conditionvariable was destroyed, but internal service CEEOPDDdid not alter the storage associated with the conditionobject. However, if internal service CEEOPCI wasinvoked, the storage was altered.


Programmer responseCheck that the application is correctly reusing storageassociated with the condition object after initializing it.

Symbolic Feedback CodeCEE5JK

CEE5749S An invalid attribute kind value waspassed.

ExplanationThe attribute kind parameter setkind_np that waspassed to internal service CEEOPDS specified aninvalid value. Valid values for setkind_np areNODEBUG (2).


Programmer responseSpecify a valid attribute kind value.

Symbolic Feedback CodeCEE5JL

CEE5750S An addressing exception occurredreferencing attribute kind storage.

ExplanationThe address where to return attribute kind thatwas passed as a parameter on a getkind_npservice request, was invalid. An addressing exceptionoccurred when the internal service CEEOPDGattempted to store the attribute kind value at thisaddress.


Programmer responseCheck that the application is correctly specifying theattribute kind address parameter on the getkind_npservice call.

Symbolic Feedback CodeCEE5JM

CEE5751C Invalid condition attribute storagedetected.

ExplanationInternal service CEEOPDG found an invalid value insystem storage for condition attribute getkind_np.



Symbolic Feedback CodeCEE5JN

CEE5761C Latch services were notavailable. The application will beterminated.

ExplanationA Language Environment function invoked internalLanguage Environment latch services when theseservices were not available. Latch services areinitialized only when the POSIX(ON) run-time optionwas in effect.


Programmer responseReport problem to your system administrator.



CEE5762C The latch was already owned. Theapplication will be terminated.

ExplanationA Language Environment function invoked internalLanguage Environment latch services to request alatch. The thread from which the request was madealready holds the latch.




CEE5763C The latch was not owned. Theapplication will be terminated.

ExplanationA Language Environment function invoked internalLanguage Environment latch services to release alatch. The thread from which the request was madedid not hold the latch.




CEE5764S The lock object was not initialized.

ExplanationThe mutex or read-write lock related service thatwas invoked requires the lock object specified as aparameter be initialized.


Programmer responseUse the internal service CEEOPMI to initialize themutex or read-write lock object before invoking theservice that failed.


CEE5765S The read-write lock was alreadyheld for writing.

ExplanationA thread invoked the read-write rdlock internal serviceCEEOPRL specifying a read-write lock that had alreadybeen locked by the thread for writing. A read-writelock can only be locked for reading multiple times bythe same thread.




CEE5766S An addressing exception occurredreferencing a lock object or lockattribute object.

ExplanationThe address of a mutex or read-write lock object, ormutex or read-write lock attribute object passed as aparameter on a lock related service call was invalid.An addressing exception program interrupt occurredwhen the called service referenced this address.


Programmer responseSpecify the correct lock object or lock attribute objectwhen passing parameters to the lock related servicecall.



CEE5767S An addressing exception occurredreferencing system storageallocated for locks.

ExplanationAn addressing exception program interrupt occurredwhen a mutex or read-write lock-related servicereferenced system storage allocated for locks.




CEE5768S A lock object has been changedsince it was initialized.

ExplanationThe mutex or read-write lock destroy internal serviceCEEOPMD detected that a lock object (specified asa parameter) had changed since it was initialized bythe lock initialization internal service CEEOPMI. Thelock was destroyed, but internal service CEEOPMD didnot alter the storage associated with the read-writelock object. However, if internal service CEEOPMI wasinvoked, the storage was altered.


Programmer responseMake sure the application is not incorrectly reusingstorage associated with the read-write lock objectafter initializing it.


CEE5769S The read-write lock was not heldby thread.

ExplanationA thread called the read-write lock unlock internalservice CEEOPRU to unlock the read-write lock but the

read-write lock was not held by the thread. A threadacquired a read-write lock with one of the followingread-write lock internal services:

• rdlock internal service CEEOPRL• tryrdlock internal service CEEOPRT• wrlock internal service CEEOPWL• trywrlock internal service CEEOPWT

and was said to have held the lock.


Programmer responseStructure the application so that the thread that locksthe read lock also unlocks the read lock.


CEE5770S The read-write lock was alreadyheld.

ExplanationA thread invoked the read-write wrlock internalservice CEEOPWL specifying a read-write lock that hadalready been locked by the thread. A read-write lockcan only be locked for reading multiple times by thesame thread.


Programmer responseStructure the application so that the thread that locksthe read-write lock also unlocks the read-write lock.

Symbolic Feedback CodeCEE5KA

CEE5771S The read-write lock was alreadyinitialized.

ExplanationThe read-write lock initialization internal serviceCEEOPMI was called to initialize a read-write lockobject that had already been initialized.



Programmer responseCall the real-write lock destroy internal serviceCEEOPMD to destroy an initialized read-write lockobject before initializing it again.

Symbolic Feedback CodeCEE5KC

CEE5772S The lock attribute object was notinitialized.

ExplanationThe mutex or read-write lock attribute related servicesrequired that the lock attribute object specified as aparameter be initialized.


Programmer responseUse internal service CEEOPXI to initialize the mutexor read-write lock attribute object before invoking theservice that failed.

Symbolic Feedback CodeCEE5KC

CEE5773S There was insufficient storage toinitialize a read-write lock object.

ExplanationThe read-write lock initialization internal serviceCEEOPMI was called to initialize a read-write lockobject. However, there was insufficient system storageavailable.


Programmer responseGet additional system storage before initializing moreread-write lock objects.

Symbolic Feedback CodeCEE5KD

CEE5774S A read-write lock attribute objecthas been changed since it wasinitialized.

ExplanationThe read-write lock attribute destroy internal service,CEEOPXD, detected that a read-write lock attributeobject specified as a parameter was changed sinceit was initialized by the read-write lock attributeinitialization internal service, CEEOPXI. The read-writelock attribute object was destroyed, but internalservice, CEEOPXD, did not alter the storage associatedwith the read-write lock attribute object. However, ifinternal service, CEEOPXI, was invoked, the storagewas altered.


Programmer responseMake sure the application is not incorrectly reusingstorage associated with the read-write lock attributeobject after initializing it.

Symbolic Feedback CodeCEE5KE

CEE5775S The read-write lock attributeobject was already initialized.

ExplanationThe read-write lock attribute initialization internalservice, CEEOPXI, was called to initialize a read-writelock attribute object that had already been initialized.


Programmer responseCall the read-write lock attribute destroy internalservice, CEEOPXD, to destroy an initialized read-writelock attribute object before initializing it again.

Symbolic Feedback CodeCEE5KF

CEE5776S There was insufficient storageto initialize a read-write lockattribute object.


ExplanationThe read-write lock attribute initialization internalservice, CEEOPXI, was called to initialize a read-writelock attribute object, however, there was insufficientsystem storage available.


Programmer responseAcquire additional system storage before initializingmore read-write lock attribute objects.

Symbolic Feedback CodeCEE5KG

CEE5777S The lock was busy.

ExplanationThe mutex or read-write lock destroy internal serviceCEEOPMD was invoked to destroy a lock that was inuse. A mutex or read-write lock that is locked, or amutex that is associated with a condition wait or timedwait, cannot be destroyed.


Programmer responseVerify that no other thread holds the lock beforecalling CEEOPMD to destroy the lock.

Symbolic Feedback CodeCEE5KH

CEE5778S An addressing exception occurredwhile referencing attribute returnstorage.

ExplanationThe address where to return attribute information thatwas passed as a parameter on a call to the mutex andread-write lock attribute internal service, CEEOPXG,was invalid. An addressing exception occurred whenthe CEEOPXG internal service attempted to store theattribute value at this return address.


Programmer responseSpecify the correct attribute return address parameteron the CEEOPXG internal service call.

Symbolic Feedback CodeCEE5KI

CEE5779S System lock storage could not befreed.

ExplanationThe destroy mutex and read-write lock internalservice, CEEOPMD, was unable to free storageallocated for a mutex or read-write lock by the lockinitialization service, CEEOPMI.



Symbolic Feedback CodeCEE5KJ

CEE5780S System lock attribute storagecould not be freed.

ExplanationThe destroy lock attribute internal service, CEEOPXD,was unable to free storage allocated for a mutexor read-write lock attribute by the lock attributeinitialization service, CEEOPXI.




Symbolic Feedback CodeCEE5KK

CEE5781S There was invalid lock attributestorage.

ExplanationThe mutex and read-write lock attribute internalservice, CEEOPXG, found an invalid value in systemstorage for lock attributes of the specified type.



Symbolic Feedback CodeCEE5KL

CEE5782S There was an invalid lock attributevalue.

ExplanationThe attribute parameter in a call to internal service,CEEOPXS, specified an invalid attribute value for lockattributes of the specified type. Valid values for typesetkind_np or settype are:

• NONRECURSIVE + DEBUG + ERRORCHECK (0)• RECURSIVE + DEBUG + ERRORCHECK (1)• NONRECURSIVE + NODEBUG + ERRORCHECK (2)• RECURSIVE + NODEBUG + ERRORCHECK (3)• NONRECURSIVE + DEBUG + NOERRORCHECK (4)• RECURSIVE + DEBUG + NOERRORCHECK (5)• NONRECURSIVE + NODEBUG + NOERRORCHECK (6)• RECURSIVE + NODEBUG + NOERRORCHECK (7)

Valid values for type setpshared are:

• PRIVATE (0)• SHARED (8)

System actionUnless the condition is handled, the default action it toterminate the enclave.

Programmer responseSpecify a correct attribute value.

Symbolic Feedback CodeCEE5KM

CEE5783C A thread waiting for a read-writelock was forced to terminate.

ExplanationAn event, such as the initial thread terminating, forcedall threads to terminate including threads waiting for aread-write lock.


Programmer responseCheck that all threads exit correctly.

Symbolic Feedback CodeCEE5KN

CEE5784I There was insufficient resource toinitialize another read-write lock.

ExplanationThe read-write lock init internal service, CEEOPMI, wasinvoked to initialize a read-write lock, but not enoughresource was available to initialize another read-writelock.



Symbolic Feedback CodeCEE5KO

CEE5785I There as insufficient privilege toinitialize the read-write lock.

ExplanationThe read-write lock init internal service, CEEOPMI, wasinvoked to initialize a read-write lock, but not enoughprivilege was available to initialize the read-write lock.




Symbolic Feedback CodeCEE5KP

CEE5786S The z/OS UNIX callable service,BPX1SLK, failed during sharedlock processing. The system returncode was return_code, the reasoncode was reason_code. X'00'

ExplanationThe z/OS UNIX callable service, BPX1SLK, was calledby a Language Environment internal service forshared mutex or read-write lock processing. BPX1SLKreturned without performing the specified shared lockprocessing (initialize, lock, unlock, or destroy).


Programmer responseSee z/OS UNIX System Services Programming:Assembler Callable Services Reference for theappropriate action to take for this return code andreason code. Consult with your z/OS UNIX systemsupport personnel if necessary.

Symbolic Feedback CodeCEE5KQ

CEE5787I There as insufficient resource toobtain the read-write lock.

ExplanationThe read-write lock rdlock or tryrdlock internalservices, CEEOPRL, or CEEOPRT was invoked to lock aread-write lock, but not enough resource was availableto obtain this read-write lock another time for read.



Symbolic Feedback CodeCEE5KR

CEE5788I The read-write lock was busy.

ExplanationThe read-write lock tryrdlock internal service,CEEOPRT, was invoked to lock a read-write lock forread that was already locked for write or had anoutstanding write lock request.



Symbolic Feedback CodeCEE5KS

CEE5789I The read-write lock was busy.

ExplanationThe read-write lock trywrlock internal service,CEEOPWT, was invoked to lock a read-write lock forwrite that was already locked for read or write.



Symbolic Feedback CodeCEE5KT

CEE5790S There was insufficient storage tolock a read-write lock object.

ExplanationA thread attempted to lock a read-write lock by callingone of the following read-write lock internal services:

• rdlock internal service, CEEOPRL• tryrdlock internal service, CEEOPRT


• wrlock internal service, CEEOPWL• trywrlock internal service, CEEOPWT

However, there was insufficient system storageavailable.


Programmer responseAcquire additional system storage before attemptingto lock more read-write lock objects.

Symbolic Feedback CodeCEE5KU

CEE5791C System read-write lock storagecould not be freed.

ExplanationThe read-write lock unlock internal service, CEEOPRUwas unable to free storage allocated for a read-writelock by one of the following read-write lock internalservices:

• rdlock internal service, CEEOPRL• tryrdlock internal service, CEEOPRT• wrlock internal service, CEEOPWL• trywrlock internal service, CEEOPWT



Symbolic Feedback CodeCEE5KV

CEE5792I There was insufficient resource toinitialize another condition object.

ExplanationThe condition object init internal service CEEOPCI wasinvoked to initialize a condition object, but not enoughresource was available to initialize another conditionobject.




CEE5793I There was insufficient privilege toinitialize the condition object.

ExplanationThe condition object init internal service CEEOPCI wasinvoked to initialize a condition object, but not enoughprivilege was available to initialize the conditionobject.




CEE5794S The condition attribute object wasnot initialized.

ExplanationThe condition wait related services required that thecondition attribute object specified as a parameter beinitialized.


Programmer responseUse internal service CEEOPDI to initialize the conditionattribute object before invoking the service that failed.


CEE5795S The callable service BPX1SMCfailed during shared conditionvariable processing. The system


return code was return_code thereason code was reason_code.

ExplanationThe callable service BPX1SMC was called by aLanguage Environment internal service for sharedcondition variable processing. BPX1SMC returnedwithout performing the specified shared conditionvariable processing (initialize, wait, signal, or destroy).




CEE5796S The callable service BPX1SMCfailed during shared lockprocessing. The system returncode was return_code the reasoncode was reason_code.

ExplanationThe callable service BPX1SMC was called by aLanguage Environment internal service for sharedmutex lock processing. BPX1SMC returned withoutperforming the specified shared lock processing(initialize, lock, unlock, or destroy).


Programmer responseUse internal service CEEOPDI to initialize the conditionattribute object before invoking the service that failed.


CEEH001I Language Environment controlblocks are unavailable.

ExplanationThe check could not execute.


Programmer responseContact your IBM Support Center.

Symbolic Feedback CodeN/A

CEEH002I Health check received an unknownentry code of hex from IBM HealthChecker for z/OS.

ExplanationThis is an internal error.




CEEH010I Language Environment Parmlib isin use. The check ran successfullyand found no exceptions.

ExplanationLanguage Environment Parmlib support is in use.


Programmer responseN/A


CEEH011I The following Options Groups arein use: <comma separated list ofOptions Groups>


ExplanationAll enabled Language Environment Parmlib OptionsGroups are listed.


Programmer responseN/A



Chapter 2. C prelinker and C object library utilitymessages

This topic provides message information for the prelinker and object library utilities.

A return code is generated to indicate the degree of prelinking success. The return codes are as follows:0

No error detected; processing completed; successful execution anticipated.4

Possible error (warning) detected; processing completed; successful execution probable.8

Error detected; processing might have been completed; successful execution impossible.12

Severe error detected; processing terminated abnormally; successful execution impossible.

The messages issued by the prelinker and object library utility have the following format:

EDCnnnns text <&s>

nnnnError message number

sError severityI


Warning messageE

Error messageS

Severe error message&s

Substitution variable, such as &1

Note: For C messages less than 4000, see z/OS XL C/C++ Compiler and Runtime Migration Guide for theApplication Programmer.

EDC4000S Unable to open &1.

ExplanationAn error was encountered during a file open.

System actionProcessing terminates.

Programmer responseMake sure that the named file has the proper DCBrequirements (for example, RECFM, BLKSIZE, LRECL).

EDC4001S Unable to read &1.

ExplanationAn error was encountered during a file read.


Programmer responseMake sure that the named file has the proper DCBrequirements (for example, RECFM, BLKSIZE, LRECL).


If the file has been corrupted recreate it, thenrecompile and run the new file.

EDC4002S Unable to write to &1.

ExplanationAn error was encountered during a file write.


Programmer responseMake sure that the named file has the proper DCBrequirements (for example, RECFM, BLKSIZE, LRECL).Also make sure that sufficient write space is available.

Programmer responseEnsure that sufficient disk space is available.

EDC4004W Invalid options: &1.

ExplanationThe listed prelinker options were invalid.

System actionThe invalid prelinker options are ignored andprocessing continues.

Programmer responseEnter the list of valid options.

EDC4005E No input decks were specified.

ExplanationNo input decks were specified for the prelink.

System actionThe prelinker will process nothing.

Programmer responseInput at least one deck.

EDC4006S Object deck was missing TXTcards.

ExplanationA corrupted input deck was encountered during theprelink.


Programmer responseRecompile the source routine and run it again. If theproblem persists, call your IBM service representative.

EDC4007S Object deck had multipleinitialized CSECTs.




EDC4008S Invalid initialization deck (RLDsspan cards).




EDC4009S Invalid initialization deck (RLDsand TXTs not in sync).





EDC4010W A zero length static object wasfound in assembler deck.

ExplanationA zero length static object was encountered in anassembler deck.

System actionIncorrect or undefined execution could result.

Programmer responseRedefine the object with the appropriate size.

EDC4011E Unresolved writable staticreferences were detected.

ExplanationUndefined writable static objects were encountered atprelink termination.

System actionPrelinker produces object module with unresolvedwritable static references. Use of this object modulecould result in incorrect or undefined execution.

Programmer responsePrelink with the MAP option to find the objects inquestion and include these objects with the prelinkstep.

EDC4012E No input decks were found.

ExplanationInput decks were not found for the prelink.

System actionThe prelinker will process nothing.

EDC4013I No map displayed as no writablestatic was found.

ExplanationNo writable static objects were found during theprelink.

System actionIf MAP option is specified, no static map is producedbecause no writable static objects were found.

EDC4014E Undefined writable static objectswere detected:

ExplanationThe listed writable static objects were undefined atprelink termination.

System actionIncorrect or undefined execution could result.

Programmer responseInclude these objects during the prelink.

EDC4015W Unresolved references weredetected:

ExplanationThe listed objects were unresolved at prelinktermination. Unresolved C library objects are notrequired for the prelink step, but should be resolvedduring the link-edit step. Unresolved writable staticobjects or unresolved objects referring to writablestatic objects are required for prelink.

System actionPrelinker only resolves writable static objects orunresolved objects referring to writable static objects.

Programmer responseTo correct the latter, include these objects during theprelink.

EDC4016W Duplicate objects were detected.

ExplanationThe listed objects were defined multiple times.

System actionIncorrect execution could occur unless the objects aredefined consistently.

Programmer responseDefine the objects consistently.

EDC4017W Duplicate object &1 was definedwith different sizes.

Chapter 2. C prelinker and C object library utility messages 165

ExplanationAn object had been defined multiple times withdifferent sizes. The larger of the different sizes wastaken. Incorrect execution could occur unless theobject is defined consistently.

System actionThe largest size is used.

Programmer responseDefine the object consistently.

EDC4018E No member name specified andNAME card not found.

ExplanationFor the ADD function, you must specify a membername, or a NAME card indicating the member namemust be present in the object module.


Programmer responseRepeat the step specifying an appropriate membername.

EDC4019S Invalid or missing XSD cards.

ExplanationA corrupted input deck was encountered duringprocessing.


Programmer responseRecompile your source routine and repeat the step.If the problem persists, call your IBM servicerepresentative.

EDC4020W Continuation card missing for &1control card.

ExplanationA control card of type &1 was encountered with thecontinuation column set, but there was no next card orthe next card was not a valid continuation card.

System actionThe card is ignored and processing continues.

Programmer responseAdd the appropriate continuation card or setcontinuation column 72 to blank if no continuationcard is required.

EDC4021W Invalid syntax specified on &1control card.

ExplanationA control card with invalid syntax was encounteredduring processing.

System actionIf the card was an INCLUDE card, the card isprocessed up to the syntax error and the remainderof the card is ignored. If the card was not an INCLUDEcard, the card is ignored. In either case, processingcontinues.

Programmer responseIf the card is required, correct the syntax errors andrepeat the step. If the card is not required, the warningmessage can be removed by deleting the invalid card.

EDC4022W More than one &1 card found in&2.

ExplanationMore than one control card of type &1 wasencountered during the processing of &2.

System actionIf the card is a NAME card and this was encounteredduring the prelink step, the last NAME card is used andprocessing continues.

If the card is a NAME card and this was encounteredduring the C370LIB ADD or GEN steps, all NAME cardsfor &2 are ignored and processing continues.

Programmer responseNo recovery is necessary unless the incorrect card waschosen or incorrect processing was performed. In thiscase, remove the offending card and repeat the step.

EDC4023W Continuation cards not allowed for&1 card. Card ignored.


ExplanationA control card of type &1 was found to be expecting acontinuation card. Information for a card of this typemust be specified on one card.


Programmer responseCorrect the card if necessary, set continuation column72 to blank, and repeat the step.

EDC4024W RENAME card cannot be used forshort name &1.

ExplanationA RENAME card was encountered that attempted torename a short name to another name. RENAME cardsare valid only for long names for which there is nocorresponding short name.


Programmer responseThe warning message can be removed by deleting theinvalid RENAME card.

EDC4025W Multiple RENAME cards found for&1. First valid one taken.

ExplanationMore than one RENAME card was encountered for thename &1.

System actionThe first RENAME card with a valid output name ischosen.

Programmer responseThe prelinker map shows which output name waschosen. If this was not the intended name, remove theduplicate RENAME card(s) and repeat the step.

EDC4026W May not RENAME long name &1 toanother long name &2.

ExplanationA RENAME card had been encountered that attemptedto rename a long name to another long name.


Programmer responseThe prelinker map shows which output name waschosen. If this was not the intended name, replacethe invalid RENAME card with a valid output nameand repeat the step. To remove the warning message,delete the invalid RENAME card.

EDC4027W May not RENAME defined longname &1 to defined name &2.

ExplanationA RENAME card had been encountered that attemptedto rename the defined long name &1 to anotherdefined name &2.


Programmer responseThe prelinker map shows which output name waschosen. If this was not the intended name, replacethe invalid RENAME card with a valid output nameand repeat the step. To remove the warning message,delete the invalid RENAME card.

EDC4028W RENAME card of &1 to &2 ignoredsince &2 is target of anotherRENAME.

ExplanationMultiple RENAME cards had been encounteredattempting to rename two different names the samename &2.

System actionThe first valid RENAME card for &2 is chosen.

Programmer responseThe prelinker map shows which name was renamedto &2. If the output name for &2 was not theintended name, change the name and repeat the step.To remove the warning message, delete the extraRENAME card(s).

EDC4029W &1 and &2 mapped to same name(&3) due to UPCASE option.


ExplanationA name (&1) that was made uppercase because of theUPCASE option collided with the output name (&3) ofanother name (&2).

System actionBoth names (&1 and &2) are mapped to &3.

Programmer responseIf both names (&1 and &2) correspond to the sameobject the warning can be ignored. If the names do notcorrespond to the same object or if the warning is tobe removed, do one of the following:

• Use a RENAME card to rename one of the names tosomething other than &3.

• Change one of the names in the source routine.• Use #pragma map in the source routine on one of

the names.• Do not run the step with the UPCASE option.

EDC4030E Missing command operands.

ExplanationOne or more operands were missing on the invocationof object library utility command.


Programmer responseAdd the proper operands and repeat the step.

EDC4031W File &1 not found.

ExplanationThe specified file could not be located to perform thecommand.

System actionIf possible, processing continues ignoring theparticular file.

Programmer responseTry the command again, specifying the appropriate file.

EDC4032E Error with &1 command. Returncode=&2.

ExplanationIn order to perform the library command, the systemcommand &1 was issued and resulted in a return codeof &2.


Programmer responseDiagnose the problem using the return code and anymessages generated.

EDC4033E Invalid C370LIB-directoryencountered in library &1.

ExplanationAn invalid or corrupted C370LIB-directory had beenencountered.


Programmer responseUse the C370LIB DIR command to recreate theC370LIB-directory and repeat the step.

EDC4034E Library &1 did not contain aC370LIB-directory.

ExplanationThe library &1 did not contain a C370LIB-directorynecessary to perform the command.


Programmer responseThe library was not created with the C370LIBcommand. Use the C370LIB DIR command to createthe C370LIB-directory and repeat the step.

EDC4035W Member &1 not found in library&2.

ExplanationThe specified member &1 was not found in the library.



Programmer responseUse the C370LIB MAP command to display the namesof library members.

EDC4036E Invalid command operands: &1.

ExplanationInvalid operands were specified on the invocation ofthis command.


Programmer responseSpecify the correct operands and repeat the step.

EDC4037E File &1 had invalid format.

ExplanationThe specified file, &1, did not have the proper format.The file should be fixed-format with a record length of80.

System actionThe file is ignored and processing continues.

Programmer responseCorrect the file or file specification and repeat the step.

EDC4038E Library &1 not found.

ExplanationThe library, &1, could not be found to perform thecommand.


Programmer responseTry the command again, specifying the correct library.

EDC4039E Library &1 had invalid format.

ExplanationThe specified library, &1, did not have the properformat. The library must contain object modules asmembers and be fixed-format with a record length of80.


Programmer responseCorrect the library or library specification and repeatthe step.

EDC4042S Virtual storage exceeded.

ExplanationThe utility ran out of memory. This sometimeshappens with large files or routines with largefunctions. Very large routines limit the optimizationthat can be done.


Programmer responseDivide the file into several smaller sections or shortenthe function.

EDC4043E Invalid symbol table encounteredin archive library &1.

ExplanationThe archive library from the MVS system had invalidinformation in its symbol table.

System actionThe invalid archive library is ignored and processingcontinues.

Programmer responseRebuild the archive library.

EDC4044E Archive library &1 did not containa symbol table.

ExplanationThe symbol table for the archive library from the MVSsystem could not be found.




EDC4045E Archive library &1 not found.

ExplanationThe archive library could not be found.


Programmer responseTry the command again specifying the appropriate file.

EDC4046E Archive library &1 had invalidformat.

ExplanationThe file was found but did not have the correctinformation to be recognized as an archive library.



EDC4048W Card &1 of &2 is invalid.

ExplanationThe card shown is not valid.

Programmer responsePrelink the DLL and generate a new, uncorrupteddefinition side-deck.

EDC4049E Unresolved references could notbe imported.

ExplanationThe same symbol was referenced in both DLL andnon-DLL code. The DLL reference could have beensatisfied by an IMPORT control statement which wasprocessed, but the non-DLL reference could not.

Programmer responseYou must either supply a definition for the referencedsymbol during the prelink step or recompile thecode containing the non-DLL reference with the DLLcompiler option so that it becomes a DLL reference.

EDC4050W Card &1 of &2 is not thecontinuation of an IMPORT controlstatement.

ExplanationThe object deck of IMPORT control statements iscorrupted.

Programmer responsePrelink the exporting DLL again to generate a newobject deck of control statements or get a new copyfrom the DLL provider.

EDC4051W Duplicate IMPORT definitions aredetected.

ExplanationA name referenced in DLL code was not defined withinthe application but more than one IMPORT controlstatement was seen with that symbol name. The firstone seen by the prelinker was used.

Programmer responseCheck the Import Symbol Map section of the PrelinkerMap to see if you are importing the symbol from thecorrect DLL. If not, change the input order of theIMPORT control statements.

EDC4052W Module name &1 chosenfor generated IMPORT controlstatements.

ExplanationThe prelinker has assigned the default nameTEMPNAME to the module in the Definition Side-Deck.

Programmer responseInclude a NAME control statement in the prelinkerinput or specify the output object module of theprelinker to be a PDS member so that the prelinkerwill use that as the module name in generated IMPORTcontrol statements.

EDC4057E Truncated duplicate #pragmamapped objects are detected.

ExplanationThe prelinker has detected duplicate names whichwere longer than 8 characters in length but have been#pragma mapped and truncated; therefore, cannot berenamed by the prelinker. The duplicate names could


have also been mapped for other reasons such as aCSECT compiler option or a #pragma csect statement.

Programmer responseModify the duplicate names listed in the message toavoid the conflict.

EDC4058E Truncated duplicate #pragmamapped objects are detected.

ExplanationThe prelinker has detected duplicate names whichwere longer than 8 characters in length but have been

#pragma mapped and truncated; therefore, cannot berenamed by the prelinker. The duplicate names couldhave also been mapped for other reasons such as aCSECT compiler option or a #pragma csect statement.

Programmer responseEnsure the MAP option is in effect. The truncated#pragma mapped duplicates will be listed in theprelinker MAP if the MAP option is in effect. Once thetruncated #pragma mapped duplicates are identified,modify the duplicate names to avoid the conflict.

Severe error messagesThe following error messages are produced by the prelinker or the Object Library Utility if the message fileis itself invalid.

EDC0090 Unable to open message file &1.

EDC0091 Invalid offset table in message file&1.

EDC0092 Message component &1 is notfound.

EDC0093 Message file &1 corrupted.

EDC0094 Integrity check failure on msg &1.

EDC0095 Bad substitution number inmessage &1.

EDC0096 Virtual storage exceeded.


Chapter 3. C Utility messages

This topic provides message and code information for the localedef utility, the iconv utility, and thegenxlt utility. See z/OS XL C/C++ Messages for messages for the DSECT and CXXFILT utilities.

localedef messagesThis topic contains the localedef return codes and messages. The localedef utility returns thefollowing return codes:0

No errors were detected and the locales were generated successfully.4

Warning messages were issued and the locales were generated successfully, or error messages wereissued but the BLDERR option was specified.

4Warning or errors were detected and the locale was not generated.

The messages issued by the localedef utility have the following format.

EDCnnnn ss text <%n$x>


ssError severity10

Warning message30

Error message40

Severe error%n$x

Substitution variable%

The start of the substitution variablen

The number that represents the line position of the variable$

A delimiterx

The kind of variable (d=decimal, c=character, s=string)

Warning messages will be issued when the FLAG(E) option is not specified. The default FLAG(W), willproduce warnings. When warning messages (severity of 10) are issued, the minimum return code from thelocaledef utility is 4.

When error messages (severity of 30) are issued, the locale is built only if the BLDERR option is specified.The default is NOBLDERR. If BLDERR is specified, the return code would be set to a minimum of 4. Iferror messages are issued and NOBLDERR was specified (or by default), the return code will be set to aminimum of 8.


When severe error messages (severity of 40) are issued, the locale is not built and the return code fromthe localedef utility is 12.

EDC4100 40 The symbol '%1$s'is not thecorrect type.

ExplanationThis message is issued while processing a localedefinition file containing a reference to a symbolthat does not have expected type. This error occurscommonly when the LC_CTYPE keywords are usedas character references in any locale definition filecategory.

System actionThe locale has not been created.

Programmer responseUse a symbolic name instead of a character reference.

EDC4101 40 Could not open '%1$s' for read.

ExplanationThis message is issued if the open for read failed forany file required by the localedef utility.


Programmer responseVerify the file name is correct and the file/data setexists.

EDC4102 40 Internal error in file %1$s on line%2$d.

ExplanationAn internal error had occurred in the localedefutility.


Programmer responseExamine the locale definition and charmap files forpossible errors. Report error to IBM.

EDC4103 40 Syntax Error: expected %1$darguments and received %2$darguments.

ExplanationThis message is issued in the locale definition filewhen a keyword was expecting a fixed number ofarguments and not enough arguments were supplied.


Programmer responseAdd the missing arguments to the keyword in thelocale definition file.

EDC4104 40 Illegal limit in range specification.

ExplanationAn error had occurred in a range in the LC_CTYPEcategory of the locale definition file. The locale wasnot created.


Programmer responseExamine the locale definition file for possible errors.

EDC4105 40 Memory allocation failure on line%1$d in module %2$s.

ExplanationThe localedef utility was unable to allocate memory.


Programmer responseUnder MVS and TSO, increase region size and rerunthe localedef utility. Under CMS, increase the virtualmachine size and rerun the localedef utility.

EDC4106 40 Could not open file '%1$s' forwrite.

ExplanationThis message is issued if the open for write failedwhen the localedef utility attempted to generatethe C program. The file name passed to fopen() isincluded in the message.



Programmer responseUnder CMS, verify the A-Disk exists and is in WRITEmode.

EDC4107 40 The '%1$s' character is longerthan <mb_cur_max>.

ExplanationThe length of value assigned to the specified symbolin the charmap file must not be bigger than the valueassigned to mb_cur_max. mb_cur_max defaults to 1and can only have the values 1 or 4 for EBCDIClocales and 1, 2 or 3 for ASCII locales. If multibytecharacters are required then the value of mb_cur_maxmust also include the shift_in and shift_out characterseven though the shift_in and shift_out characters arenot entered into the charmap file as part of a characterdefinition.


Programmer responseIncrease the size of mb_cur_max or remove the extrabyte in multibyte sequence assigned to the symbolspecified.

EDC4108 10 The '%1$s' symbolic name wasundefined and has been ignored.

ExplanationThe specified symbolic name used in the localedefinition file was not defined in the charmap file.When a symbolic name that is not defined is used inthe LC_CTYPE or LC_COLLATE categories, the warningis issued.

System actionThe character has been ignored and the locale hasbeen created.

Programmer responseDefine the specified symbol name in the charmap file.

EDC4109 40 The '%1$s' symbolic name wasundefined.

ExplanationThe specified symbolic name used in the localedefinition file was not defined in the charmap file.When a symbolic name that is not defined is used incategories other than LC_CTYPE or LC_COLLATE, anerror message is issued.


Programmer responseDefine the specified symbol name in the charmap file.

EDC4110 40 The start of the range, '%1$s',must be numerically less than theend of the range, '%2$s'.

ExplanationIn the collation section of the locale definition file,the start range codepoint specified must be less thanthe end range codepoint specified. These codepointswere assigned values in the charmap file where thecodepoints can be assigned in any order.


Programmer responseChange the collation range codepoints in the localedefinition file so that the start of the range is less thanthe end of the range.

EDC4111 40 The symbol range containing%1$s and %2$s was incorrectlyformatted.

ExplanationThe symbolic names used in range definition inthe charmap file should consist of zero or morenonnumeric characters, followed by an integer formedby one or more decimal digits. The characterspreceding the integer should be identical in the twosymbolic names, and the integer formed by the digitsin the second name should be equal to or greater thanthe integer formed by the digits in the first name.This is interpreted as a series of symbolic namesformed from the common part and each of the integersbetween the first and second integer, inclusive.

In the following example, the first line is valid as bothnames have the same prefix, followed by four digits,

Chapter 3. C Utility messages 175

whereas the second example has a different prefix forthe first and second name, and is invalid.

<ab0101>...<ab0120> \x42\xc1<abc0101>...<ab0120> \x42\xc1


Programmer responseCheck the specified symbolic names to ensurecompliance to the above rules.

EDC4112 40 Illegal character reference orescape sequence in '%1$s'.

ExplanationA character reference or escape sequence had beendefined that was not legal.


Programmer responseMake the character reference or escape sequencelegal.

EDC4113 30 The symbolic name '%1$s', hadalready been specified.

ExplanationThe specified symbolic name in the charmap file hadalready been specified. A symbolic name should onlybe defined once.


Programmer responseRemove the duplicate symbolic name from thecharmap file.

EDC4114 10 There are characters in thecodeset which were unspecified inthe collation order.

ExplanationThere were characters defined in the charmap filethat were not used in the collation category of thelocale definition file. The locale was still created. The

characters were added at the end of the collationsequence.

System actionThe locale has been created and the characters wereadded at the end of the collation sequence.

Programmer responseIf required, add the missing characters from thecharmap file to the collation category of the localedefinition file.

EDC4115 30 Illegal decimal constant '%1$s'.

ExplanationThe decimal constant of type '\dnnn' specified in thecharmap file was greater than decimal 255.


Programmer responseChange the decimal constant in the charmap file to avalue less than or equal to 255.

EDC4116 30 Illegal octal constant '%1$s'.

ExplanationThe octal constant of type '\nnn' specified in thecharmap file was greater than octal 377.


Programmer responseChange the octal constant in the charmap file to avalue less than or equal to octal 377.

EDC4117 30 Illegal hexadecimal constant'%1$s'.

ExplanationThe hexadecimal constant of type '\xnn' specified inthe charmap file was greater than hexadecimal FF.



Programmer responseChange the hexadecimal constant in the charmap fileto a value less than or equal to hexadecimal FF.

EDC4118 30 Missing closing quote in string'%1$s'.

ExplanationThe string specified had a opening double quote but noclosing double quote. The closing quote will be added.

System actionThe locale has not been created. If BLDERR option isspecified, the characters between the opening doublequote and the end of line character will be used.

Programmer responseAdd the closing double quote after the string.

EDC4119 30 Illegal character, '%1$c', in inputfile.

ExplanationAn illegal character had been found in the charmap orlocale definition file.

System actionThe locale has not been created. If BLDERR option isspecified, the character is ignored.

Programmer responseRemove the character.

EDC4120 30 The character for '%1$s'statement is missing. Statement isignored.

ExplanationWhen defining the escape character or commentcharacter in the charmap or locale definition file, acharacter was not supplied.

System actionThe statement was ignored and the escape characteror comment character was not changed. The localehas not been created. If BLDERR option is specified,the default comment or escape character is used.

Programmer responseInsert a character to be defined as the escapecharacter or comment character in the charmap orlocale definition file.

EDC4121 30 '%1$c' is not a POSIX PortableCharacter. Character is ignored.

ExplanationWhen defining escape_char or comment_char in thecharmap or locale definition file, the character wasless than space.

System actionThe statement was ignored and the escape characteror comment character was not changed. The localehas not been created. If BLDERR option is specified,the default comment or escape character is used.

Programmer responseDefine the escape_char or comment_char in thecharmap or locale definition file with a charactergreater than space.

EDC4122 30 The character symbol '%1$s' ismissing the closing '>'. The '>' isadded.

ExplanationThe character symbol specified had a less than signat the beginning of the symbol but no closing greaterthan sign. The symbol was accepted.

System actionThe locale has not been created. If BLDERR option isspecified, the characters between the open '<' and theend of line character is used.

Programmer responseAdd the greater than sign after the symbol.

EDC4123 30 Unrecognized keyword, '%1$s',statement is ignored.

ExplanationWhen a dot is not used in a string or as part asof an ellipses (…), the keyword is unrecognized, thestatement is ignored.



Programmer responseRemove the dot that is part of the unrecognizedkeyword or add the missing dots to make up ellipses(…).

EDC4124 40 The encoding specified for the'%1$s' character is unsupported.

ExplanationThe multibyte character was not valid, contains ashift out without a corresponding shift in or a shift incharacter without a corresponding shift out. The localewas not created.


Programmer responseIf the string contains unmatched shift in or shift outcharacters, remove them.

EDC4125 30 The character, '%1$s', hasalready been assigned a weight.Specification is ignored.

ExplanationThe specified character or symbolic name in thecollation category of the locale definition file, hadalready been defined.

System actionThe locale has not been created. If BLDERR option isspecified, the second definition is ignored.

Programmer responseRemove the duplicate character or symbolic name forthe collation category.

EDC4126 30 A character in range'%1$s...%2$s' already had acollation weight. Range is ignored.

ExplanationA character or symbolic name in the specified range inthe collation category of the locale definition file, hadalready been defined in the collation category.

System actionThe locale has not been created. If BLDERR option isspecified, the second definition is ignored.

Programmer responseRemove the duplicate character or adjust the range soas not to cover duplicate characters.

EDC4127 10 No toupper section defined for thislocale source file.

ExplanationThe toupper keyword in the LC_CTYPE category in thelocale definition file was not specified. The lowercasecharacter 'a' to 'z' are mapped to the characters 'A' to'Z'.

System actionThe locale has been created.

Programmer responseAdd the lowercase characters 'a' to 'z' and 'A' to 'Z' tothe toupper section of the LC_CTYPE category in thelocale definition file.

EDC4128 10 The use of the '...' keywordassumed that the codeset wascontiguous between the two rangeendpoints specified.

ExplanationThis warning is always produced when ellipses (…)are used in defining collation sequences in the localedefinition file because the locale may not be portablewhenever ellipses are used.

System actionThe locale is still created.

Programmer responseInstead of using ellipses, insert all the symbol namesbetween the two range endpoints.

EDC4129 30 The symbolic name, '%1$s',referenced had not yet beenspecified in the collation order.


ExplanationCollation weights in the locale definition file must usesymbolic names that have already been specified inthe collation order.

System actionThe locale has not been created. If BLDERR option isspecified, the unspecified reference to the symbolicname is ignored.

Programmer responseRemove the reference to the symbolic name from thecollation weights that have not yet been specified inthe collation order.

EDC4130 30 Error in file %1$s, on line %2$d, atcharacter %3$d.

ExplanationAn error had occurred in the charmap or localedefinition file on the line number supplied and atthe character position supplied. The line numberand character position in the message indicates theposition within the file when the error was detected.This may be after the line containing the error.

Programmer responseSee the message EDC4131 10 for more information.

EDC4131 10 Warning in file %1$s, on line%2$d, at character %3$d.

ExplanationA warning message had been produced for the linenumber supplied, at the character position supplied inthe charmap or locale definition file name supplied.The line number and character position in the messageindicates the position within the file when the errorwas detected. This may be after the line containing theerror.

Programmer responseSee the message EDC4132 30 for more information.

EDC4132 30 Syntax error in file %1$s, on line%2$d, at character %3$d.

ExplanationA syntax error had been found in the charmap orlocal definition file name supplied, on the line numbersupplied and at the character position supplied. The

line number and character position in the messageindicates the position within the file when the errorwas detected. This may be after the line containing theerror.

Programmer responseChange the line in the charmap or locale definition fileto conform to the POSIX standard format.

EDC4133 40 Specific collation weightassignment was not valid whenno sort keywords have beenspecified.

ExplanationThe number of sort rules, such as forward,backward, no-substitute or position, specified after theorder_start keyword must be greater than or equal tothe number of weights assigned to any one characterin the collation category of the locale definition file.When no sort rules are specified, one forward sort ruleis assumed.


Programmer responseAdd additional sort rules to the order_start keyword.

EDC4134 10 The <mb_cur_min> keyword mustbe defined as 1, you have definedit as %1$d. Value is ignored.

ExplanationThe <mb_cur_min> keyword in the charmap file canonly be set to 1.

System actionThe Value was ignored and the locale has beencreated.

Programmer responseChange the value of the <mb_cur_min> keyword in thecharmap file to 1.

EDC4135 30 The <code_set_name> mustcontain only characters from thePOSIX portable character set,'%1$s' is not valid.


ExplanationThe <code_set_name> in the charmap file must onlyuse graph characters. It must contain only charactersfrom the portable character set. The character %1$s isnot valid.

System actionThe locale has not been created. If BLDERR option isspecified, the <code_set_name> is used anyway.

Programmer responseRemove the character from the <code_set_name> inthe charmap file that is not in the portable characterset.

EDC4136 30 The collation directives forwardand backward are mutuallyexclusive.

ExplanationEach sort rules of the order_start keyword of thecollation category in the locale definition file canconsist of one or more sort rules separated bycommas. The sort rules forward and backward, cannotbe used at the same time.


Programmer responseSpecify only forward or backward but not both.

EDC4137 30 Received too many arguments,expected %1$d.

ExplanationThis message is issued in the locale definition filewhen a keyword is expecting a fixed number ofarguments and too many arguments are supplied.

System actionThe locale has not been created. If BLDERR option isspecified, the extra arguments are ignored.

Programmer responseRemove the unnecessary argument in the localedefinition file.

EDC4138 30 The %1$s category had alreadybeen defined.

ExplanationThe specified category in the locale definition fileshould only be defined once.

System actionThe locale has not been created. If BLDERR optionis specified, the second definition of the duplicatecategory is ignored.

Programmer responseRemove the specified duplicate category.

EDC4139 10 The %1$s category was empty.

ExplanationThe specified category in the locale definition file didnot contain any keywords.


Programmer responseRemove the empty category or add keywords to thespecified category.

EDC4140 30 Unrecognized category %1$s wasnot processed by localedef.

ExplanationUser defined categories in the locale definitionfile were not supported. That is, categories thatare not LC_CTYPE, LC_COLLATE, LC_MONETARY,LC_NUMERIC, LC_TIME, LC_MESSAGES, LC_SYNTAX orLC_TOD were not processed by the localedef utility.

System actionThe locale has not been created. If BLDERR option isspecified, the unsupported categories are ignored.

Programmer responseRemove the unrecognized category from the localedefinition file.

EDC4141 10 The POSIX defined categoriesmust appear before anyunrecognized categories.

ExplanationUser defined categories in the locale definitionfile must appear after the POSIX defined


categories LC_CTYPE, LC_COLLATE, LC_MONETARY,LC_NUMERIC, LC_TIME, LC_MESSAGES, LC_SYNTAXand LC_TOD.


Programmer responseMove the unrecognized category to the end of localedefinition file.

EDC4142 30 The file code for the digit %1$swas not one greater than the filecode for %2$s.

ExplanationThe values assigned to the digit symbolic names<zero> to <nine> in the charmap file must be insequence and be contiguous.


Programmer responseChange the value assigned to the specified digitsymbolic name in the charmap file so that it is onegreater than the value assigned to the preceding digitsymbolic name.

EDC4143 30 The process code for the digit%1$s is not one greater than theprocess code for %2$s.

ExplanationThe wide character values assigned to the digitsymbolic names <zero> to <nine> in the charmap filemust be in sequence and be contiguous.

System actionThe locale has not been created. If BLDERR option isspecified, the values are forced to be used.

Programmer responseChange the wide character value assigned to thespecified digit symbolic name in the charmap file sothat it is one greater than the wide character valueassigned to the preceding digit symbolic name.

EDC4144 30 The symbol %1$s has alreadybeen defined. Ignoring definitionas a collating-symbol.

ExplanationThe collation symbol must be a symbolic name,enclosed between angle brackets (< and >), andshould not duplicate any symbolic name in thecharmap file or any other name defined in the collationdefinition.

System actionThe locale has not been created. If BLDERR optionis specified, the definition as a collating-symbol isignored.

Programmer responseUse another symbolic name for the collating symbol.

EDC4145 10 Locale did not conform to POSIXspecifications for the LC_CTYPE'%1$s' keyword.

ExplanationThe specified keyword in the LC_CTYPE category inthe locale definition contained characters that conflictwith the POSIX definition of the category. This may becaused by the following:

• The upper keyword contained characters from thecntrl, digit, punct or space keywords.

• The lower keyword contained characters from thecntrl, digit, punct or space keywords.

• The alpha keyword contained characters from thecntrl, digit, punct or space keywords.

• The space keyword contained characters from thedigit, upper, lower, alpha or xdigit keywords.

• The cntrl keyword contained characters from thedigit, upper, lower, alpha, graph, punct, print or xdigitkeywords.

• The punct keyword contained characters from thedigit, upper, lower, alpha, cntrl, space or xdigitkeywords.

• The graph keyword contained characters from thecntrl keyword.

• The print keyword contained characters from thecntrl keyword.


Programmer responseRemove the character from the specified keywordthat conflicts with characters from one of the otherkeywords.


EDC4146 10 Locale did not specify theminimum required for theLC_CTYPE '%1$s' keyword. Settingto POSIX defined defaults.

ExplanationThe specified keyword in the LC_CTYPE category inthe locale definition file did not contain the minimumcharacters required by the keyword. The minimumrequirements for the keywords are as follows:

• The upper keyword does not contain the requiredcharacters 'A' to 'Z'.

• The lower keyword does not contain the requiredcharacters 'a' to 'z'.

• The digit keyword does not contain the requireddigits 0 through 9.

• The xdigit keyword does not contain the requireddigits 0 through 9,the uppercase letters 'A' through'F' and the lowercase letters 'a' through 'f'.

• The space keyword does not contain the requiredcharacters space, form feed, newline, carriagereturn, horizontal tab and vertical tab.

• The blank keyword does not contain the requiredcharacters space and tab.


Programmer responseSpecify the minimum requirements for the specifiedkeyword.

EDC4147 10 Locale did not specify only '0', '1', -'2', '3', '4', '5', '6', '7', '8', and '9' forLC_CTYPE digit keyword.

ExplanationThe digit keyword in the LC_CTYPE category in thelocale definition file can only contain the charactersrequired, '0' to '9'.

System actionThe locale will still be created.

Programmer responseRemove the character outside the '0' to '9' range in thedigit keyword.

EDC4148 10 Locale did not specify only '0', '1','2', '3', '4', '5', '6', '7', '8', '9', 'a'

through 'f', and 'A' through 'F' forLC_CTYPE xdigit keyword.

ExplanationThe xdigit keyword in the LC_CTYPE category in thelocale definition file can only contain the charactersrequired, '0' to '9' and 'A' to 'F' or 'a' to 'f'. The localewill still be created.

System actionThe locale will still be created.

Programmer responseRemove the character outside the range '0' to '9' and'A' to 'F' or 'a' to 'f' to the xdigit keyword.

EDC4149 30 The number of operands toLC_COLLATE order exceededCOLL_WEIGHTS_MAX.

ExplanationThe number of sort rules, such as forward,backward, no-substitute or position, specifiedafter the order_start keyword must not exceedCOLL_WEIGHTS_MAX in the collation category of thelocale definition file.

System actionThe locale has not been created. If BLDERR option isspecified, the extra operands are ignored.

Programmer responseReduce the number of sort rules to the order_startkeyword.

EDC4150 30 Both '%1$s' and '%2$s' symbolsmust be characters and notcollation symbols or elements.

ExplanationWhen defining ranges using ellipses (…) in thecollation category of the locale definition file, theendpoints of the range must be characters or symbolicnames defined in the charmap file. They should notbe collating-symbol operands or collating-elementoperands.

System actionThe locale has not been created. If the BLDERR optionis specified, the defined ranges will not be used.


Programmer responseUse different characters for the range endpoints.

EDC4151 10 Option %1$s is not valid and wasignored.

ExplanationThe option specified in the message is not a validlocaledef utility option or a valid option has beenspecified with an invalid value.

System actionThe specified option was ignored and the locale hasbeen created.

Programmer responseRerun the localedef utility with the correct option.

EDC4152 10 No matching right parenthesis for%1$s option.

ExplanationThe option specified had a sub option beginning with aleft parenthesis but no right parenthesis was present.The option and suboption were accepted and thelocale was still produced.

System actionThe option and sub option has been accepted and thelocale was still produced.

Programmer responseAdd the right parenthesis after the sub option.

EDC4153 10 Required symbolic name %1$s notdefined in the charmap file.

ExplanationThe symbolic name specified is not defined in thecharmap file and must be specified.

System actionThe locale has been produced.

Programmer responseDefine the missing symbol name in the charmap file.

EDC4154 30 Keyword 'copy' cannot be nested.

ExplanationA locale category specifies the copy keyword, and thelocale from which the category is being copied fromalso includes copy keyword for the same category.

System actionThe locale has not been created. If BLDERR option isspecified, the default is used for the category.

Programmer responseChange the name of the existing locale to be copied tothe name specified in existing locale copy keyword.

EDC4155 30 'copy' keyword category '%1$s'not found.

ExplanationThe specified category cannot be found in the localedefinition file that was included using the copykeyword. The category is not copied.

System actionThe category is not copied and the locale has not beencreated.

Programmer responseChange the name of the existing locale to be copied oradd the specified category to the locale definition file.

EDC4156 30 LC_SYNTAX '%1$s' character canonly be a punctuation character.

ExplanationThe specified character defined in the LC_SYNTAXcategory of the locale definition file, must be apunctuation character. The character was ignored.


Programmer responseOnly use punctuation characters as LC_SYNTAXcharacters.

EDC4157 10 LC_SYNTAX '%1$s' character canonly have a length of 1. Ignoringadditional characters.


ExplanationThe specified character defined in the LC_SYNTAXcategory of the locale definition file contained morethan one character, or specified a multibyte character.The LC_SYNTAX characters must only be single-bytecharacters.

System actionThe locale is created ignoring additional characters.

Programmer responseOnly use single-byte characters as LC_SYNTAXcharacters.

EDC4158 10 LC_SYNTAX '%1$s' charactercould not be found in the charmapfile. Assigned code page %2$ssymbol is '%3$s'.

ExplanationThe LC_SYNTAX category was omitted, or thecharacter was omitted from the LC_SYNTAX category,and the localedef utility attempted to assign thedefault value. The specified symbolic name was notfound in the charmap file, and the character has beenassigned the code point value from the IBM-1047code page.

System actionThe local is still created.

Programmer responseSpecify the character in the LC_SYNTAX category thatexists in charmap file, or change the charmap file toinclude the specified symbolic name.

EDC4159 30 Duplicate characters for '%1$s'and '%2$s' found in LC_SYNTAX.

ExplanationThe specified characters from the LC_SYNTAXcategory have the same code points assigned.

System actionThe locale has not been build.

Programmer responseChange the characters to specify different code pointsfor each of the LC_SYNTAX characters.

EDC4160 10 The '%1$s' keyword is notsupported and was ignored.

ExplanationThe specified keyword is not defined in the POSIXstandard.

System actionThe undefined keyword is ignored and locale has beencreated.

Programmer responseRemove the specified keyword.

EDC4161 10 The <mb_cur_max> keyword mustbe defined as 1 or 4, you havedefined it as %1$d. Value isignored.

ExplanationThe <mb_cur_max> keyword can have the value of 1for single-byte characters only, or 4 to support DBCScharacters. Values of other than 1 or 4 are ignored.

System actionThe value is ignored and locale has been created. IfBLDERR option is specified, the value of 1 is used.

Programmer responseSpecify <mb_cur_max> as either 1 or 4.

EDC4162 30 Both <shift_in> and <shift_out>must be specified or neitherspecified.

ExplanationEither the <shift_in> keyword or the <shift_out>keyword have been specified, but not both.


Programmer responseSpecify either both or neither <shift_in> and<shift_out>.

EDC4163 30 You have exceeded the maximumnumber of alternate strings foralt_digits.


ExplanationUp to 100 alternate strings can be specified for thealt_digits keyword for the values from zero to 99.

System actionThe locale has not been created. If BLDERR option isspecified, the extra strings are ignored.

Programmer responseRemove the extra alternate strings.

EDC4164 30 The grouping string '%1$s' isinvalid.

ExplanationThe string specified for the LC_NUMERIC groupingkeyword or LC_MONETARY mon_grouping keyword isnot in the correct format. The string should consistof numbers in the range -1 and 254 separated bysemicolons.


Programmer responseCorrect the grouping or mon_grouping string to be inthe correct format.

EDC4165 10 The grouping string '%1$s' isinvalid and had been truncated to'%2$s'.

ExplanationThe string specified for the LC_NUMERIC groupingkeyword or LC_MONETARY mon_grouping keyword isnot in the correct format. The string should consistof numbers in the range -1 and 254 separated bysemicolons, with no other numbers or semicolonsfollowing the -1.

System actionThe characters following the -1 were ignored and thelocale has been created.

Programmer responseRemove the characters from the grouping ormon_grouping string following the -1.

EDC4166 30 The value '%1$d' for '%2$s' isinvalid.

ExplanationThe value %1$d specified is not a value for thespecified keyword. For example, the day is not valid forthe specified month, or the month is not in the rangefrom 1 to 12.

System actionThe locale has not been created. If BLDERR option isspecified, localdef assign 0 to value '%1$d'.

Programmer responseCorrect the value for the specified keyword to bewithin the correct range for that keyword.

EDC4167 30 '%1$s' specified with no '%2$s'.

ExplanationThe keyword specified can only be specified if theother keyword is also specified. Either both or neithershould be specified.


Programmer responseEither remove the first keyword specified, or add theother required keyword.

EDC4168 10 'daylight_name' must be specifiedif Daylight Saving Timeinformation is to be used by themktime and localtime functions.

ExplanationKeywords had been specified in the LC_TOD category,but the 'daylight_time' keyword had not beenspecified. The other keywords will be ignored.

System actionThe locale has been build.

Programmer responseRemove the other keywords from the LC_TODcategory, or add the 'daylight_time' keyword.

EDC4169 30 One-to-many mappings cannotbe specified against a collating-symbol, collating-element or theUNDEFINED symbol.


ExplanationA one-to-many mapping has been specified in theLC_COLLATE category against a collating-symbol,collating-element or the UNDEFINED symbol. Forexample, all of the following would cause this errormessage:

collating-symbol <HIGH>collating-element <ch> from "<c><h>"<HIGH> "<A>"<ch> "<B>"UNDEFINED "<C>"

System actionThe locale has not been build.

Programmer responseRemove the one-to-many mapping from the collating-symbol, collating-element or the UNDEFINED symbol.

EDC4170 40 Write failed while writing to file%1$s.

ExplanationThe write failed to the specified file.


Programmer responseLook for a basic problem, such as insufficient diskspace or lack of access to the file. If you are stillunable to determine the cause of the write failure,contact your system programmer.

EDC4171 30 The process code of the firstcharacter of the collating-elementwas greater than the maximumprocess code.

ExplanationThe wchar_t value for the first character in a collating-element was greater than the largest characterspecified in the charmap file. This may occur if thecharmap file specifies <mb_cur_max> of 4, but didnot specify the DBCS characters, and the collating-element begins with a DBCS character.


Programmer responseEither use a charmap file that specifies <mb_cur_max>of 1, or change the collating-element to not start witha DBCS character.

EDC4172 30 Consecutive ellipses collatingelements are not allowed.

ExplanationConsecutive ellipses cannot occur in a rangespecification.


Programmer responseRemove one of the ellipses.

EDC4173 30 The grouping integer %1$s isinvalid.

ExplanationThe grouping integer must be >= -1 and <255.


Programmer responseCorrect the grouping integer value.

EDC4174 10 The grouping integer list is invalidand has been truncated after -1.

ExplanationNo grouping integers can follow -1.

System actionThe grouping integers following -1 were ignored andthe locale has been created.

Programmer responseCorrect the grouping integer list.

EDC4175 40 Missing output locale name.

ExplanationThe name of the file in which localedef creates thelocale object was not specified when localedef wasinvoked.



Programmer responseSpecify the name of the file in which the locale objectis to be created.

EDC4176 40 Could not create a temporary file.

ExplanationThe temporary file for locale generation could not becreated.


Programmer responseEnsure that there are sufficient system resources togenerate the temporary file and contact your systemprogrammer.

EDC4177 40 You have specified differentnames for the same character'%1$d'.

ExplanationThis message is produced when the option -w isspecified and more than one symbolic name wasassigned to the same character.

System actionThe value was accepted and the locale has beencreated.

Programmer responseIf multiple symbolic names for the same characterare intended, then no action is required; otherwise, anunintended duplicate exists and should be corrected.

EDC4178 30 Character for escape_charstatement missing. Statementignored.

ExplanationThe escape_char statement must be followed by agraphic character that is not a space.

System actionThe statement has been ignored and the escapecharacter set to default. The locale has been created.

Programmer responseAdd a character after the escape_char statement.

EDC4179 30 Character for comment_charstatement missing. Statementignored.

ExplanationThe comment_char statement must be followed by agraphic character that is not a space.

System actionThe statement has been ignored and commentcharacter set to default. The locale has been created.

Programmer responseAdd a character after the comment_char statement.

EDC4200 40 usage: localedef [-c][-w][-A][-X][-fcharmap][-i locsrc][-L binder opts][-m methfile] locname

ExplanationFollow the usage information on how to correctlyinvoke localedef.

System actionThe locale has not been generated.

Programmer responseCorrect the invocation syntax.

EDC4201 40 The compile was unsuccessful.Required header files localdef.hand lc_core.h may be the wrongversion or may be missing.

ExplanationThe compile or link of the temporary method file wasunsuccessful.


Programmer responseEnsure that the C compiler and the binder are correctlyinstalled and functional.

EDC4202 40 The methods for mbtowc,mbstowcs, wctomb, wcstombs,


mblen, wcwidth, wcswidth mustbe specified in the <methodfile>.

ExplanationThe listed methods are mandatory and must bespecified in the method file.


Programmer responseAdd missing methods and rebuild the locale.

EDC4203 40 Locale can not mix private methodtable methods and global methodtable methods.

ExplanationUse either private method table methods or globalmethod table methods.


Programmer responseChange the method file to contain only methods fromthe method table of the same type.

EDC4204 40 Unable to exec /bin/sh to processintermediate files.

ExplanationThis is a system problem.


Programmer responseContact your system programmer.

EDC4206 40 Missing end of symbol in string'%1$s'.

ExplanationThe symbol is missing end of symbol character '>'.


Programmer responseCorrect the symbol specification and rebuild thelocale.

EDC4207 30 The symbolic name '%1$s' is notdefined in the character map.

ExplanationThe reported symbol name was not defined in thecharacter map.

System actionThe locale generation will continue.

Programmer responseEnsure that the proper character map is used.

EDC4208 40 Unable to load locale '%1$s' forcopy directive.

ExplanationThe locale named in the copy directive of the localesource could not be loaded.


Programmer responseEnsure that the locale name is correct and representsa full or relative path name.

EDC4209 40 Locale name longer thanPATH_MAX (%1$d).

ExplanationThe locale name that appears in a copy directive islonger than the maximum path length indicated.


Programmer responseRename the locale or put it in a directory structurewith a smaller depth.

EDC4210 30 '%1$s' was not declared in acharclass statement.


ExplanationThe character class listed in the message was foundin the locale specification but was not declared in acharclass statement.

System actionThe value was added to the character class table, andthe locale has been created.

Programmer responseEnsure that the character class is spelled correctly andrebuild the locale. If the character class was correctlyspelled, add it to the charclass statement.

EDC4211 30 Collating symbols such as %1$scan not have explicit weights.Specification ignored.

ExplanationCollating symbols cannot be assigned explicit weights.Their weights are derived from the relative positionthey occupy in the locale specification.

System actionThe value assigned to the collating symbol wasignored, and the locale has been created.

Programmer responseRemove the weight assignment from the affectedcollating symbol.

EDC4212 30 Ellipsis on the right hand sidemay only be used with ellipsis orUNDEFINED symbols on the lefthand side.

ExplanationAn ellipsis was used to assign a collation weight to acharacter but this is not allowed.

System actionThe value was ignored, and the locale has beencreated.

Programmer responseUse the correct weight assignment syntax.

EDC4213 30 Ellipsis may not be used as oneof the characters in a one-to-manymapping.

ExplanationEllipsis was used in a one to many mapping but this isnot allowed.


Programmer responseUse the correct one to many mapping syntax.

EDC4214 40 Stack overflow error.

ExplanationThe stack used for symbols and semantic elementswas exhausted.


Programmer responseContact your IBM representative.

EDC4215 40 Required symbol name %1$s notdefined in character map file.

ExplanationThe listed name was used in the locale specificationbut was not defined in the character map file.


Programmer responseEnsure that the correct character map file is used.

EDC4216 30 The symbol %1$s is too long. Itwill be truncated to %2$d bytes.

ExplanationThe symbol name is longer than the maximum namelength supported.

System actionThe name was truncated, and the locale has beencreated.


Programmer responseUse a shorter symbol name.

EDC4217 30 The symbol '%1$s' character isundefined. This character alongwith any range statements it maybe in will be ignored.

ExplanationThe symbolic name for a character was not defined inthe character map file.


Programmer responseEnsure that the correct character map file is used.

EDC4218 30 More weights were definedfor character %1$s than werespecified with the order_startkeyword.

ExplanationThe character listed in the message was assignedmore weights than the order_start keyword indicates.

System actionThe extra weights were ignored and the locale hasbeen created.

Programmer responseUse the correct number of weights in line with whatwas specified in the order_start keyword.

iconv utility messagesThis topic contains the iconv return codes and messages. The iconv utility returns the following returncodes:0

No errors were detected and the file was successfully converted from the input codeset to the outputcodeset.

4The specified conversions are not supported, the given input file cannot be read, or there is a usage-syntax error.

8An unusable character was encountered in the input file.

>8A severe error occurred.

The messages issued by the iconv utility have the following format:

EDCnnnn s text <%n$x>


sError severity10

Warning message30

Error message%n$x

Substitution variable%

The start of the substitution variable


nThe number that represents the line position of the variable

$A delimiter

xThe kind of variable (d=decimal, c=character, s=string)


ExplanationThe option specified in the message is not a validiconv utility message, or a valid option had beenspecified with an invalid value.

System actionThe specified option has been ignored.

Programmer responseRerun the iconv utility, specifying the correct option.

EDC4152 10 No matching right parenthesis for%1$s option.

ExplanationThe option specified had a suboption beginning with aleft parenthesis, but no right parenthesis was present.

System actionThe option has been accepted as entered.

Programmer responseAdd the right parenthesis.

EDC4180 30 FROMCODE option had not beenspecified.

ExplanationThe FROMCODE option is required, but had not beenspecified.

System actionThe file has not been converted.

Programmer responseRerun the iconv utility, specifying the FROMCODEoption.

EDC4181 30 TOCODE option has not beenspecified.

ExplanationThe TOCODE option is required, but has not beenspecified.


Programmer responseRerun the iconv utility, specifying the TOCODE option.

EDC4182 30 Cannot open converter from %1$sto %2$s.

ExplanationThe iconv utility could not locate the conversion from%1$s to %2$s.


Programmer responseCheck the %1$s and %2$s specified to ensure theyare correct.

EDC4183 30 Cannot open input file.

ExplanationThe iconv utility could not open the input file.


Programmer responseVerify that the correct file name has been specifiedand rerun the iconv utility.

EDC4184 30 Cannot open output file.

ExplanationThe iconv utility could not open the output file.



Programmer responseCorrect the cause of the error and rerun the iconvutility.

EDC4185 30 Invalid character found.

ExplanationAn invalid character was detected in the input file andcould not be converted.

System actionThe file is converted up to the record in error.

Programmer responseCorrect the invalid character in the input file, or specifya different FROMCODE and TOCODE.

EDC4186 30 Truncated character found.

ExplanationThe end of the file has been reached, and a truncatedmultibyte character was detected.

System actionThe last character has not been converted.

Programmer responseCorrect the invalid character in the input file, or specifya different FROMCODE and TOCODE.

EDC4187 30 Unable to allocate enoughmemory.

ExplanationThe iconv utility could not allocate buffers for usewhen converting the file.


Programmer responseRerun the iconv utility with more memory.

EDC4188 30 I/O error on file filename.

ExplanationAn input or output error was detected with thefilename.

This message is issued if the record format of theoutput file was fixed and the output records did nothave the same length as the output file, or if the recordformat of the output file was variable and the outputrecords were longer than the maximum record length.


Programmer responseCorrect the cause of the input/output error and rerunthe iconv utility.

EDC4189 30 Unable to fetch messages fileEDCIMSGE.

ExplanationThe iconv utility could not fetch the message fileEDCIMSGE.


Programmer responseEnsure that the iconv utility has sufficient storageto run. Under CMS, ensure that the GLOBAL LOADLIBcommand has been issued. Under MVS and TSO,ensure that the correct libraries are specified on theSTEPLIB DD statement.

EDC4199 30 Output record size %d too small.

ExplanationThe output record length of %d supplied for the iconvutility is too small to hold a converted input line.


Programmer responseCheck the output record length to be sure that itis large enough to hold the longest input recordconverted.


genxlt utility messagesThe messages issued by the genxlt utility have the following format:

EDCxxxx nn text <%n$x>

xxxxError message number.

nnError severity.10

Warning message.30

Error message.%n$x

Substitution variable .%

The start of the substitution variable.n

The number that represents the line position of the variable.$

A delimiterx

The kind of variable (d=decimal, s=string).


ExplanationThe option specified in the message is not a validgenxlt utility message, or a valid option had beenspecified with an invalid value.

System actionThe specified option is ignored.

Programmer responseRerun the genxlt utility, specifying the correct option.

EDC4190 30 Unable to open data file.

ExplanationThe genxlt utility could not open the input file.

System actionThe conversion table has not been built.

Programmer responseCheck that the correct file name has been specifiedand rerun the genxlt utility.

EDC4191 30 Unable to open target file.

ExplanationThe genxlt utility could not open the output file.


Programmer responseCorrect the cause of the error, and rerun the genxltutility.

EDC4192 30 There was no assignment for index%1$d.

ExplanationThe character %1$d had not been assigned acharacter to which it must be converted.



Programmer responseUpdate the input file to specify a conversion value forthe character specified.

EDC4193 30 Unable to write for target file.

ExplanationAn output error was detected with the output file.

Programmer responseCorrect the cause of the output error and rerun thegenxlt utility.

EDC4194 30 Invalid format at line %1$d.

ExplanationThe line %1$d is not valid. The conversion table hasnot been built.


Programmer responseCorrect the line in error and rerun the genxlt utility.

EDC4195 30 Unable to fetch messages fileEDCGMSGE.

ExplanationThe genxlt utility could not fetch the message fileEDCGMSGE.


Programmer responseEnsure that the genxlt utility has sufficient storageto run. Under CMS, ensure that the GLOBAL LOADLIBcommand has been issued. Under MVS and TSO,ensure that the correct libraries are specified on theSTEPLIB DD statement.


Chapter 4. XL C/C++ runtime messages

The following runtime messages pertain to C/C++ that have an EDC prefix. For information on themessages from the C/C++ legacy class libraries, which have a prefix of CLB, refer to z/OS XL C/C++Messages. Each message is followed by an explanation describing the condition that caused the message,a programmer response suggesting how you might prevent the message from occurring again, and asystem action indicating how the system responds to the condition that caused the message.

The messages contain a symbolic feedback code, which represents the first 8 bytes of a 12-byte conditiontoken. You can think of the symbolic feedback code as the nickname for a condition. As such, the symbolicfeedback code can be used in user-written condition handlers to screen for a given condition, even if itoccurs at different locations in an application. The messages in this topic also contain alphabetic suffixesthat have the following meaning:I


Warning messageE

Error messageS



EDC5000I No error occurred.

ExplanationThe value of errno is zero.

System actionNone.


Symbolic Feedback CodeEDC4S8

EDC5001I A domain error occurred.

ExplanationAn input argument to one of the math functionswas outside the domain over which the mathematicalfunction is defined.

System actionThe math function fails.

Programmer responseRefer to z/OS XL C/C++ Runtime Library Reference forthe math functions that produced this error.

Symbolic Feedback CodeEDC4S9

EDC5002I A range error occurred.

ExplanationThe result of the math function could not berepresented as a double value, or a buffer provided bythe user was not large enough to contain a function’soutput.

System actionThe function fails or returns partial results.

Programmer responseRefer to z/OS XL C/C++ Runtime Library Reference forthe function that produced this error.

Symbolic Feedback CodeEDC4SA


EDC5003I Truncation of a record occurredduring an I/O operation.

ExplanationTruncation occurred because: 1) the specified recordlength on the write operation was larger than therecord buffer size; 2) an attempt to extend the recordbuffer for a CMS variable length file failed whichcaused record truncation; or 3) the record read in waslarger than the record buffer size.

System actionThe return value depends on the operation attempted.In all cases, the buffer will be read or written up to thepoint where truncation occurred.

Programmer responseFor a text stream, place the newline character earlierin the record to shorten the record size. For a fileopened for record I/O, specify a smaller number ofbytes for fread(), fwrite(), or fupdate().

Symbolic Feedback CodeEDC4SB

EDC5004I The size of the specified recordwas too small.

ExplanationThe record length was too small because the specifiedrecord size for an fwrite() or fupdate() functionwas smaller than the minimum record length allowedfor the file.

System actionIn all cases, the write or update operation fails.

Programmer responseIncrease the size or count parameter on thefwrite() or fupdate() function.

Symbolic Feedback CodeEDC4SC

EDC5005I A write operation may notimmediately follow a readoperation.

ExplanationIf the last operation on a non-VSAM file opened forrecord I/O was a read, a write operation may notdirectly follow.

System actionThe write operation fails.

Programmer responseInvoke fflush(), rewind(), fseek(), orfsetpos() between the read and write operations onthe file stream.

Symbolic Feedback CodeEDC4SD

EDC5006I A read operation may notimmediately follow a writeoperation.

ExplanationIf the last operation on a file was a write, a readoperation may not directly follow.

System actionThe read operation fails.

Programmer responseInvoke fflush(), rewind(), fseek(), orfsetpos() between the write and read operations onthe file stream.

Symbolic Feedback CodeEDC4SE

EDC5007I The I/O buffer could not beallocated.

ExplanationMemory was not available for the allocation of variousbuffers when invoking any of the I/O functions.

System actionThe I/O function returns NULL or EOF.

Programmer responseRun the program in a larger region.


Symbolic Feedback CodeEDC4SF

EDC5008I The LRECL or BLKSIZE exceededthe maximum allowable value.

ExplanationOn CMS, the resultant CMS LRECL was greater than65535. On MVS, the specified LRECL or BLKSIZE wasgreater than 32760.

System actionThe fopen()/freopen() function returns NULL.

Programmer responseChange the open attributes specified to be within thevalid limits.

Symbolic Feedback CodeEDC4SG

EDC5009I An I/O operation was attemptedusing an invalid FILE pointer.

ExplanationThe FILE pointer that was input to the I/O functionwas not an active FILE pointer created by fopen()/freopen().

System actionThe specified I/O operation fails.

Programmer responseEnsure that the FILE pointer was created by fopen()/freopen(), and that no I/O operation is attemptedafter fclose().

Symbolic Feedback CodeEDC4SH

EDC5010I A read operation was attemptedon a file that was not opened forreading.

ExplanationWhen a read operation (for example, fgetc(),fread() ) is invoked, the file specified must beopened in a mode that supports reading.


Programmer responseOpen the file with a mode that supports reading. Thefollowing modes do NOT support reading: 'w', 'wb', 'a',or 'ab'.

Symbolic Feedback CodeEDC4SI

EDC5011I The number of ungetc() push-back characters has exceeded themaximum allowed.

ExplanationAn ungetc() was attempted but could not behonored because there were already pushed-backcharacters waiting to be read, and the numberof pushed-back characters already equaled themaximum allowed.

System actionThe ungetc() function returns EOF.

Programmer responseEither read a pushed-back character, or reposition thefile before attempting to push back another character.

Symbolic Feedback CodeEDC4SJ

EDC5012I File positioning is not allowed forthis data set.

ExplanationAn attempt was made to either acquire the file positionor reposition the file using an I/O function that is notsupported by the file.

System actionThe function fails.

Programmer responseFor non-VSAM files, do not open the file with theNOSEEK option. For VSAM PATH data sets, positionthe FILE pointer to the beginning of the data set, ordo not issue the ftell() or fseek() functions. Ifthe data set resides on a device that does not support

Chapter 4. XL C/C++ runtime messages 197

repositioning, either move the data set or do not usethe positioning functions.

Symbolic Feedback CodeEDC4SK

EDC5013I No hiperspace blocks are availablefor expansion.

ExplanationA hiperspace has been filled to its maximum allowedsize. An attempt has been made to add more data tothe hiperspace.


Programmer responseCheck with your system programmer to see if there iscurrently a shortage of resources for hiperspaces.

Symbolic Feedback CodeEDC4SL

EDC5014I An attempt was made to acquire aposition that is before the start ofthe file.

ExplanationThe ftell() and fgetpos() functions cannot returna file position when characters are pushed back usingungetc() at the start of the file. This is because theresultant position ends up being before the start of thefile, and this is not a valid position.

System actionFunction ftell() or fgetpos() fails.

Programmer responseDo not call ftell() or fgetpos() if you push backcharacters before the start of the file, unless you eitherread them or discard them using a reposition first.

Symbolic Feedback CodeEDC4SM

EDC5015I The file position value was beyondthe limits that ftell() can representin a long integer value.

ExplanationThe current position lies outside the bounds that canbe represented by the ftell() encoding scheme.For fixed format binary streams, this is a file positionbeyond relative byte number 2147483647. For otherfiles, the limit is based on the relative block or recordnumber. For CMS files with LRECL between 32KB and64KB, this limit is 65536 records. For all other files,the maximum depends on the block size. Smallerblock sizes allow more records to be encoded. Themaximum is at least 131072 records.

System actionThe ftell() function fails (return -1 (EOF)).

Programmer responseThe fgetpos() function can be used to reportfile positions that ftell() cannot. The fsetpos()function must then be used to perform therepositioning at a later time.

Symbolic Feedback CodeEDC4SN

EDC5016I Byte I/O was attempted on a filethat was opened for record I/O.

ExplanationOne of the byte I/O functions was invoked with a filethat was opened using 'type=record'.

System actionThe requested function fails.

Programmer responseOnly the fread(), fwrite(), and fupdate()functions may be used to read, write, or update a fileopened for record I/O.

Symbolic Feedback CodeEDC4SO

EDC5017I A write operation was attemptedon a file that was not opened forwriting.

ExplanationWhen a write operation (for example, fputc(),fwrite() ) is invoked, the file specified must havebeen opened for writing.



Programmer responseOpen the file with a mode that supports writing. Thefollowing modes do not support writing: 'r', 'rb'.

Symbolic Feedback CodeEDC4SP

EDC5018I An ungetc() function call cannotimmediately follow a writeoperation.

ExplanationA reposition function or flush must occur between awrite operation and ungetc().

System actionThe ungetc() function returns EOF.

Programmer responseInvoke either fflush(), rewind(), fseek(), orfsetpos() before calling ungetc().

Symbolic Feedback CodeEDC4SQ

EDC5019I An unrecoverable error haspermanently marked the file inerror.

ExplanationA previous I/O operation has failed such that thecurrent file pointer is no longer valid. Only thefclose() and freopen() functions are permitted.

System actionThe operation fails.

Programmer responseCheck the return codes of previous I/O operations, orset up a SIGIOERR handler to determine the source ofthe error. When you have determined which C functionhas generated the error, issue perror() to get theoriginal error message.

Symbolic Feedback CodeEDC4SR

EDC5020I An attempt to allocate memoryin the Language Environment hasfailed.

ExplanationThe attempt of Language Environment attempt toobtain memory in order to satisfy the current libraryrequest has failed.


Programmer responseRun the program in a larger region, or usethe HEAP(,,FREE) run-time option instead of theHEAP(,,KEEP) option.

Symbolic Feedback CodeEDC4SS

EDC5021I The file attributes for open createan invalid combination.

ExplanationAn invalid combination was caused by merging thecharacteristics specified on the fopen()/freopen()call, the ddname declaration, or the existing fileattributes.


Programmer responseAdjust the LRECL and BLKSIZE parameters on thefopen()/freopen() call, or adjust the attributesspecified with the ddname so a valid combination willbe created. See z/OS XL C/C++ Programming Guide fordetails on attribute merging and valid combinations.

Symbolic Feedback CodeEDC4ST

EDC5022I An error occurred while generatinga temporary name.


ExplanationThe tmpnam() function was called to generate atemporary file name. However, a name, which didnot already exist, could not be generated within themaximum number of attempts.

System actionThe tmpnam() function fails and returns NULL.

Programmer responseVerify that the time() and clock() functions areworking correctly on your system. If so, try erasingall unused files that were created by the tmpnam()function, and retry the function. Contact your IBMSupport Center if error still occurs.

Symbolic Feedback CodeEDC4SU

EDC5023I An attempt to back up position hasfailed.

ExplanationOne or more ungetc() calls are outstanding when anfgetpos() or ftell() is called such that the fileposition is really in the previous physical block. Anattempt by the Language Environment to back up thefile to acquire the position has failed.

System actionThe ftell()/fgetpos() function fails.

Programmer responseCheck the __amrc structure for more information.See z/OS XL C/C++ Programming Guide for moreinformation on the __amrc structure.

Symbolic Feedback CodeEDC4SV

EDC5024I An attempt was made to closea file that had been opened onanother thread.

ExplanationA file that was opened on one thread was closed onanother.

System actionThe close operation fails.

Programmer responseAll files must be closed on the same thread on whichthey were opened.

Symbolic Feedback CodeEDC4T0

EDC5025I An I/O function was invoked whena read was pending for a file thathad been intercepted.

ExplanationA file that was intercepted under the debugging toolwas expecting input when an I/O function for that filewas invoked from the debugging session.

System actionThe I/O function fails.

Programmer responseDo not recursively invoke library I/O functions whena read is pending. Supply the expected data and theninvoke the I/O function.


EDC5026I An error occurred when expandinghiperspace.

ExplanationAn error occurred trying to expand a hiperspace tomore than its current size, but less than equal to itsmaximum allowable size.


Programmer responseCheck the __amrc structure for the return code fromHSPSERV. See z/OS XL C/C++ Programming Guide formore information on the __amrc structure.



EDC5027I The position specified to fseek()was invalid.

ExplanationOne of the following occurred: 1) a whence valueother than SEEK_SET, SEEK_CUR, or SEEK_END wasspecified; 2) the specified position was before the startof the stream; or 3) the specified position was beyondthe end of the stream and the stream was not a binaryfile.

System actionThe fseek() function fails.

Programmer responseCorrect the offset/whence parameters on thefseek() function to be a valid position, or open thefile in binary mode if the user wants file positionsbeyond EOF to result in null extension to the file.


EDC5028I A previous I/O error has markedthe stream invalid for further I/Oprocessing.

ExplanationA serious error has occurred in a previous I/Ooperation such that further I/O cannot be continued.The routine that caused the original error had set errnopreviously, but it will have changed because of thiserrno value. The clearerr() function will not clearthis type of error.

System actionThe current I/O operation fails.

Programmer responseCheck the return code values of previous I/Ooperations to detect which operation originated thesystem I/O failure and get the errno value. Use thislist to find a prescribed action, or attempt a rewind()or fsetpos() to clear the internal error marker andreestablish the file position.


EDC5029I An unrecognized signal value waspassed to the signal() or raise()function.

ExplanationThe signal value passed into the signal() orraise() function was not one of the valid signals asdefined in signal.h.

System actionThe signal() or raise() function returns SIG_ERR.

Programmer responsePass either SIGIOERR, SIGFPE, SIGSEGV, SIGILL,SIGABRT, SIGTERM, SIGINT, SIGTERM, SIGUSR1,SIGUSR2, or SIGABND to the signal() or raise()function.


EDC5030I An invalid argument was passed.

ExplanationThe setenv() function has been called with a '=' signin the environment variable name. This is an invalidargument.

System actionThe setenv() function fails.

Programmer responseRemove the '=' sign from the environment variablename.


EDC5031I An attempt was made to closea stream not belonging to thecurrent main program.

ExplanationThe user has passed a file pointer across a system callboundary and has attempted to close or reopen the filein the child program.

System actionThe fclose()/freopen() function fails.


Programmer responseThe program is invalid and must be changed. Thesuggested change is to close the file in the parentprogram before the system() call. The file can thenbe reopened in the child program, if required. Uponreturning to the parent program, the file can again bereopened.


EDC5032I An error was detected in theinput string passed to the system()function.

ExplanationWhen the system() function was invoked and 'PGM='was specified for an MVS-style parameter list, eitherthe 'PARM=' string was not specified or invalidcharacters were found on the 'PARM=' string.

System actionThe system() function fails.

Programmer responseCorrect the parameter string passed to the system()function, or use a VM-style parameter list.


EDC5033I An attempt was made to extend anon-extendable file.

ExplanationWhile updating a partitioned data set member or aconcatenated dataset, an attempt was made to extendthe file.

System actionThe I/O write operation fails.

Programmer responseIf extension is required to a member, open the oldmember in read mode and copy the contents to a newmember that is opened for write. Because the newmember is opened in write mode, it can be extended.Close both the old and new members, and then deletethe old member with the remove() function. Renamethe new member using the rename() function so that

it appears to be the old member, now extended. Youcannot extend the concatenation for a concatenateddata set.


EDC5034I An unsupported buffering modewas specified for the setvbuf()function.

ExplanationThe buffer type specified as a parameter for thesetvbuf() function was unsupported, or a buffermode other than line buffered (_IOLBF) was specifiedfor a terminal device type.

System actionThe setvbuf() function fails.

Programmer responseSpecify one of the following supported buffer types:_IOFBF (full buffering) or _IOLBF (line buffering).

Symbolic Feedback CodeEDC4TA

EDC5035I An attempt was made to changethe buffering mode after anoperation on a file.

ExplanationA call was made to the setvbuf() function after thefile had been read or written.

System actionThe setvbuf() function returns EOF.

Programmer responseUse the setvbuf() function to set the buffering modebefore any read or write I/O operations are done.

Symbolic Feedback CodeEDC4TB

EDC5036I The specification of a member isinvalid.


ExplanationOn a remove() or rename() function call, a memberhas been specified for a file that does not havemembers, or a member has been specified for onename of a rename() function call, but not for thesecond name.

System actionThe remove()/rename() function fails.

Programmer responseIf the file does not have members, remove themember specification. If this is a rename() call andonly one name specifies a member, either remove themember specification or add a member specificationto the second name.

Symbolic Feedback CodeEDC4TC

EDC5037I The specified ddname was notfound.

ExplanationA ddname was specified for a file name parameter,but the ddname was not defined. The functionsthat support ddnames as file names are fopen(),freopen(), and remove().


Programmer responseSee z/OS XL C/C++ Programming Guide for detailson how to define a ddname in the environmentssupported. See z/OS XL C/C++ Runtime LibraryReference for the math functions.

Symbolic Feedback CodeEDC4TD

EDC5038I An error occurred when thesystem flushed terminal outputbefore retrieving terminal input.

ExplanationWhen a terminal read cannot get any data from thebuffer and must perform a system terminal read, allterminal output data not yet flushed to the system

must be output. While writing the unflushed terminaloutput data, an error occurred.

System actionThe terminal input operation fails.

Programmer responseChange the code so all terminal output is completedand flushed to the terminal before the terminal inputoperation. Check all return codes to find out if anyoutput operation gets an error; then check the errnovalue for further information regarding any errorsencountered.

Symbolic Feedback CodeEDC4TE

EDC5039I A writable CMS minidisk could notbe found to hold the output filespecified.

ExplanationAn attempt has been made to open a CMS minidiskfile for 'write' or 'append', but there is no CMS minidiskaccessed 'r/w' to write the output file.

System actionThe fopen()/freopen() function fails.

Programmer responseAccess a CMS minidisk in 'r/w' mode.

Symbolic Feedback CodeEDC4TF

EDC5040I An attempt was made to open aflat file as a PDS.

ExplanationWhen a memory file is created without members, itsname cannot be used with a member specified.


Programmer responseEither specify a memory file that already hasmembers, or remove the flat memory file before


specifying the open with the member specified andopen the file for 'write'.

Symbolic Feedback CodeEDC4TG

EDC5041I An error was detected at thesystem level when opening a file.

ExplanationA system level error was detected.


Programmer responseLook in the __amrc structure for further detailsregarding the error. See z/OS XL C/C++ ProgrammingGuide for more information on the __amrc structure.Or check the MVS job log for an error message.

Symbolic Feedback CodeEDC4TH

EDC5042I A special internally-generatedmemory file name was specifiedfor opening, but a memory filewith this name does not exist.

ExplanationA name was specified of the form: '((x))', where 'x'is a decimal number, but the name did not matchan existing memory file. A name of this format maynot be used to create a memory file. The name isgenerated internally by C/MVS when a user opensa memory file with a name of '*' for output. C/MVSgenerates the name so that the user can acquireit using the fldata() function and then can read,update, append, or remove the memory file.


Programmer responseIf using memory files created with a name of '*', issuefldata() to acquire the correct name. If the namewas properly acquired using fldata(), make sure ithas not been closed and removed before opening thegenerated name.

Symbolic Feedback CodeEDC4TI

EDC5043I An attempt was made to open anon-memory file as a memory file.

ExplanationAn open for read has specified 'type=memory', but thefile is not a memory file.


Programmer responseRemove the 'type=memory' specification on thefopen()/freopen().

Symbolic Feedback CodeEDC4TJ

EDC5044I An error occurred whenattempting to erase a CMS file.

ExplanationWhen the remove() function was invoked, either theCMS file was not found to be erased, or an erroroccurred when the system attempted to erase the file.

System actionThe remove() function fails.

Programmer responseEnsure that the file name specified to the remove()function exists and is on a disk accessed for write.

Symbolic Feedback CodeEDC4TK

EDC5045I The operation attempted could notbe performed because the file wasopen.

ExplanationAn attempt was made to remove or rename a file thatwas still open, or an attempt was made to open a filefor output or append that was already open.


System actionThe remove(), rename(), fopen(), or freopen()function fails.

Programmer responseThe remove() function can only be invoked with filesthat have been closed. The fopen() function cannotopen a memory or disk file for write/update/append ifthe file is already opened. A memory file opened witha member specified will prevent the name from beingused without a member, and vice-versa. For example,it is not possible to have memory files: 'a.b' and 'a.b(c)'opened at the same time. In either case, the originalopen file must be closed.

Symbolic Feedback CodeEDC4TL

EDC5046I The file could not be deleted.

ExplanationThe remove() function could not remove the filespecified on MVS.


Programmer responseVerify that the file name specified to the remove()function is erasable.

Symbolic Feedback CodeEDC4TM

EDC5047I An invalid file name was specifiedas a function parameter.

ExplanationThe name specified to the remove(), rename(),fopen(), or freopen() functions was invalid. Thename is either not valid for the system (MVS, CMS), isnot a valid memory file name, or is a '*' or GDG data setname specified to the rename() function.

System actionThe invoked function fails.

Programmer responseSpecify a valid file name according to the system,or to the memory file name rules to the remove(),rename(), fopen(), and freopen() functions.

Symbolic Feedback CodeEDC4TN

EDC5048I A Language Environment internalroutine has failed unexpectedly.

ExplanationAn internal call to a Language Environment internalroutine has failed, but the failure is not anticipated,and recovery is not possible.

System actionCurrent library function using an internal routine fails.


Symbolic Feedback CodeEDC4TO

EDC5049I The specified file name could notbe located.

ExplanationWhen the rename() function was invoked, the old filename could not be found or the new file name couldnot be allocated or, when the fopen()/freopen()function was invoked, the specified file name openedfor read could not be found.

System actionThe fopen(), freopen(), or rename() functionfails.

Programmer responseVerify that the specified file exists.

Symbolic Feedback CodeEDC4TP

EDC5051I An error occurred when renaminga file.


ExplanationA rename error has occurred.

System actionThe rename() function fails.

Programmer responseFor disk files, ensure that the old file name exists.For memory files, ensure that different names arespecified to the rename() function and that PDS-stylenaming conventions are used consistently for old andnew names. For MVS, check the __amrc for furtherdetails.

Symbolic Feedback CodeEDC4TR

EDC5052S The application is running withAMODE=24 while the run-timelibrary was installed above theline.

ExplanationThe application which is accessing the run-timelibrary is running with AMODE=24. But the run-timelibrary was installed above the 16MB line, which theapplication cannot address.

System actionApplication is terminated with 3000 abend.

Programmer responseEnsure the AMODE of the application matches that ofthe run-time library. Language Environment no longersupports C applications in AMODE=24. Relink theapplication to have AMODE=31.

Symbolic Feedback CodeEDC4TS

EDC5053S The Language Environment run-time library load module EDCZ24could not be loaded.

ExplanationAn error has occurred when Language Environmenttried to load the run-time library load module EDCZ24.

System actionThe program ends and a traceback or dump is issued,depending on the TERMTHDACT run-time option. Areturn code of 3000 is returned.

Programmer responseCheck the data sets in the go steplib for the job toensure that EDCZ24 is available. (For example, checkSCEERUN.)

Symbolic Feedback CodeEDC4TT

EDC5054I An attempt to override thedisposition was ignored. The filemay still be removed.

ExplanationThe remove() function attempted to delete the dataset by using a disposition of DELETE. The data setwould not allow an override of the disposition.

System actionThe remove() function fails, but the data set mayhave been removed if the original allocation specifiedDELETE as the normal disposition.

Programmer responseChange the disposition on the original allocation, orremove the data set outside of your C program.

Symbolic Feedback CodeEDC4TU

EDC5055I An error occurred trying to removethe file before its expiration date.

ExplanationWhen the remove() function attempted to erasethe file, an error was returned indicating that theexpiration date had not yet occurred.


Programmer responseChange the expiration date of the data set.


Symbolic Feedback CodeEDC4TV

EDC5057I The open mode string was invalid.

ExplanationThe mode string passed to the fopen()/freopen()function was found to have invalid keywords,combinations, or characters. For example, if you areopening a ddname, be sure the DISP= specified on theDD statement is compatible with the open mode youspecified.


Programmer responseCorrect the mode string and reissue the fopen()/freopen().

Symbolic Feedback CodeEDC4U1

EDC5059I An attempt to reposition a VSAMfile failed.

ExplanationWhen the flocate() function was invoked, thereposition was not successful, or rewind() could notposition to the beginning of the file.

System actionThe flocate() function fails. The rewind() functiondoes not reposition to the start of the data set.

Programmer responseFor flocate(), verify that the attributes of the VSAMfile match the type of repositioning being attempted.For a rewind() error, check the __amrc structure.See z/OS XL C/C++ Programming Guide for moreinformation on the __amrc structure.


EDC5060I An invalid file position was passedto the fsetpos() function.

ExplanationWhen fsetpos() was invoked, the fpos_t structurepassed did not represent a valid position in the currentfile.

System actionThe fsetpos() function fails.

Programmer responseVerify that the fpos_t structure set by fgetpos() isa valid file position before calling fsetpos(). Alsoverify that the file has not changed between the timeof the fgetpos() and fsetpos().


EDC5061I An error occurred whenattempting to define a file to thesystem.

ExplanationThe fopen()/freopen() function or the remove()function could not successfully allocate or FILEDEF thespecified file.

System actionThe fopen(), freopen(), or remove() functionfails.



EDC5063I An error was detected in aninternal control block.

ExplanationOne of the internal I/O control blocks was corruptedand is causing unexpected behavior.

System actionThe I/O operation fails and the stream is marked asinvalid for further I/O.


Programmer responseEnsure that the application program is not overwritingstorage. If the error cannot be located, contact theIBM Support Center.


EDC5065I A write system error wasdetected.

ExplanationA system level write error has occurred.




EDC5066I A read system error was detected.

ExplanationA system level read error has occurred.



Symbolic Feedback CodeEDC4UA

EDC5067I An attempt was made to open anonexistent file for read.

ExplanationThe fopen()/freopen() function was invoked forread, but the file specified did not exist, or the dataset name '*' was attempted to be opened for read inMVS batch.


Programmer responseEnsure that the file to be opened for read exists, orthat the interactive terminal is not being opened forread in MVS batch.

Symbolic Feedback CodeEDC4UB

EDC5072I An attempt was made to opena KSDS or Path VSAM data setwithout specifying record I/O.

ExplanationKey Sequenced VSAM data sets and Path VSAM datasets may not be opened as streams for writing. OnlyEntry Sequenced VSAM data sets and Relative RecordVSAM data sets may be opened this way.


Programmer responseChange the type string parameter on the fopen()function to include 'type=record'.

Symbolic Feedback CodeEDC4UG

EDC5073I The maximum number of attemptsto obtain temporary names wasexceeded.

ExplanationThe tmpnam() function was invoked more than themaximum number of times allowed.

System actionThe tmpnam() function returns NULL and does notgenerate any more unique names.

Programmer responseThe programmer should alter the application tominimize the number of calls to tmpnam(). Thesystem can only ensure that TMP_MAX calls will work.


Symbolic Feedback CodeEDC4UH

EDC5074I The open parameters weremissing the 'type=record'specifier.

ExplanationThe open type keyword parameter 'acc=' is not validunless 'type=record' is also specified.


Programmer responseSpecify 'type=record' on the fopen()/freopen()statement.

Symbolic Feedback CodeEDC4UI

EDC5076I An fread() was not performedbefore calling the fdelrec() orfupdate() functions.

ExplanationThe fdelrec() and fupdate() functions may not beinvoked without first calling the fread() function.

System actionThe fdelrec() and fupdate() functions fail.

Programmer responseInvoke the fread() function directly before thesefunctions.

Symbolic Feedback CodeEDC4UK

EDC5077I An error occurred trying to erase aVSAM record.

ExplanationThe fdelrec() function could not successfully erasethe last record read from the specified VSAM file.

System actionThe fdelrec() function fails.

Programmer responseExamine the values of __amrc__code__feedback__rcand __amrc__code__feedback__fdbk immediatelyafter receiving this errno. Look up the __rc and __fdbkvalues in a VSAM Macro Reference manual, suchas MVS/ESA VSAM Administration: Macro InstructionReference. __rc corresponds to the register 15 value,__fdbk corresponds to the Reason Code. See z/OS XLC/C++ Programming Guide for more information on the__amrc structure.

Symbolic Feedback CodeEDC4UL

EDC5078I The requested operation is validonly for VSAM data sets.

ExplanationThe fdelrec(), flocate() and fupdate()functions may only be invoked with VSAM data sets.

System actionThe fdelrec(), flocate() and fupdate()functions fail.

Programmer responseUse the fseek()/ftell() or fgetpos()/fsetpos() functions for positioning within a non-VSAM file. To update, use fread()/fwrite() or thebyte I/O functions instead of fupdate().

Symbolic Feedback CodeEDC4UM

EDC5079I The file was not opened with a'type=record' specification.

ExplanationThe fdelrec() and fupdate() functions are notvalid for VSAM data sets opened as streams.

System actionThe fdelrec() and fupdate() functions failed.

Programmer responseChange the fopen() type parameter string to include'type=record'.


Symbolic Feedback CodeEDC4UN

EDC5080I An invalid option was passed tothe flocate() function.

ExplanationOne of the supplied parameters, options or key to theflocate() function contained an invalid value.

System actionThe flocate() function fails.

Programmer responseUse one of the following as the optionsparameter: __KEY_FIRST, __KEY_LAST, __KEY_EQ,__KEY_EQ_BWD, __KEY_GE, __RBA_EQ or__RBA_EQ_BWD, as defined in stdio.h.

If using either __RBA_EQ or __RBA_EQ_BWD, ensurethat the key parameter is a multiple of the LRECL.

Symbolic Feedback CodeEDC4UO

EDC5083I An error occurred attempting toload a module into storage.

ExplanationThe library has attempted to dynamically load amodule and a failure resulted. This is usually as aresult of a system() call.

System actionThe called library function fails.

Programmer responseVerify that the specified program/command has beenmade accessible for loading. You may also need toadjust your region size. For MVS batch, check the joblog for messages which will help to pinpoint the nameof the module.

Symbolic Feedback CodeEDC4UR

EDC5084I The program was not run becauseof redirection errors on thecommand line.

ExplanationAn error was detected when the input string tomain() was being parsed. One of the following mayhave occurred: 1) the file name specified with theredirection symbols could not be opened (for read,write, or append); 2) the file name specified with thewrite redirection symbol was already opened; or 3)the same redirection symbol was specified more thanonce in the command string.

System actionThis errno is used internally to generate the redirectionerror message. The program is terminated or thesystem() call returns the failure and does not invokethe second program.

Programmer responseCorrect the input string passed to main and if thesystem() call is being used to invoke another Cmain() program, the files that are still open in the firstprogram will be considered open when the redirectionstatements are being verified.

Symbolic Feedback CodeEDC4US

EDC5086I An unsupported open mode wasspecified for a PDS member.

ExplanationThe fopen()/freopen() function was incorrectlyinvoked specifying write-update, append, or append-update for a PDS member.


Programmer responseOpen a PDS member with open modes: read, read-update, or write.

Symbolic Feedback CodeEDC4UU

EDC5087I The specified file characteristicsdid not match those of the existingfile.


ExplanationThe fopen()/freopen() was attempting to performan open that used an existing data set, but foundthat the specified attributes did not match the existingfile attributes; specifically, LRECL, BLKSIZE, or recordformat.


Programmer responseVerify that the attributes of the physical file are asexpected by the application program.

Symbolic Feedback CodeEDC4UV

EDC5088I An invalid open mode wasspecified for the current device.

ExplanationThe following open modes and device types are invalidcombinations: 1) opening the interactive terminal forupdate; 2) reading a display or printer; 2) writing to acharacter reader; 3) updating a magnetic tape device;4) opening SYSIN or SYSOUT for 'append' or 'update';5) opening SYSIN for anything except 'read'; or 6)opening SYSOUT 'read'.


Programmer responseCorrect the open mode on the fopen()/freopen()call and/or verify the that the current device type iswhat is expected.

Symbolic Feedback CodeEDC4V0

EDC5089I Open mode is invalid for a SYSINor SYSOUT data set.

ExplanationOne of the following was attempted: 1) opening a JCLinstream data set for 'update', 'write', or 'append'; 2)opening a SYSOUT data set for 'read' or 'update'.


Programmer responseCorrect the open mode on the fopen()/freopen()call.


EDC5091I The requested function could notbe performed because a systemutility failed.

ExplanationA system level utility used by the library unexpectedlyreturned a failure code.


Programmer responseCheck the __amrc structure and z/OS XL C/C++Programming Guide for further details.


EDC5092I An I/O abend was trapped.

ExplanationAn I/O abend has occurred during an I/O operation(open, read, write, position, or close) and has beentrapped. Recovery was attempted.

System actionThe I/O operation fails. The stream is marked in errorand all further I/O operations on this stream fail.

Programmer responseCheck the __amrc structure defined in z/OS XL C/C++Programming Guide for an explanation of the fields.


EDC5093I An unsupported I/O operation hasbeen attempted.


ExplanationThe following unsupported I/O operation has beenattempted by the application program:

• An attempt was made to open a large formatsequential data set for read with repositioning(seek), while the data set was already opened forwrite without repositioning (noseek). This action isprevented because the writer can extend the dataset beyond the point where the reader is allowed toread (65535 tracks). A possible solution is to openfor read without repositioning (noseek).

System actionThe function call fails.

Programmer responseChange the application program to avoid using theunsupported I/O operation.


EDC5094I An attempt was made to pushback the EOF character usingungetc().

ExplanationThe ungetc() function may not be invoked with theEOF character.

System actionThe ungetc() function fails.

Programmer responseDo not call ungetc() with EOF.


EDC5095I The requested CMS minidisk wasnot accessed.

ExplanationThe fopen()/freopen() function could not open theCMS file specified because the specified minidisk wasnot accessed.


Programmer responseAccess the correct disk when attempting to open a file.


EDC5098I An invalid RECFM was specifiedwhen opening a PDS member.

ExplanationThe resultant record format for the open function isinvalid. Under CMS, record formats containing ASAcharacters or machine characters are invalid for PDSmembers, as well as files with the spanned attribute.Under MVS, spanned record formats are not valid.


Programmer responseIssue the fopen()/freopen() function with validattributes, or verify the attributes specified when theddname is defined.

Symbolic Feedback CodeEDC4VA

EDC5099I The function specified is notsupported under CICS.

ExplanationThe function specified is not supported under CICS.

System actionThe specified function fails.

Programmer responseRefer to z/OS XL C/C++ Programming Guide for moreinformation on running with C/MVS under CICS.

Symbolic Feedback CodeEDC4VB

EDC5100I An attempt was made to performdisk file I/O under CICS.

ExplanationThe fopen(), freopen(), rename() and remove()functions only support memory files. The standard


streams must be memory files or use the specifiedqueues.

System actionThe fopen(), freopen(), rename(), and remove()functions fail, and all writes to stdout/stderr fail.

Programmer responseOnly invoke fopen(), freopen(), rename() orremove() with memory files when running underCICS.

Symbolic Feedback CodeEDC4VC

EDC5101I The transient data queue was notenabled for the standard streams.

ExplanationAn attempt was made to write to stdout or stderr,when running under CICS, when the requestedtransient data queue was not enabled.

System actionThe write I/O operation fails.

Programmer responseEnsure that the DFHDCT macro has been assembledand defined correctly in the start-up CICS JCL. Thesystems programmer will know the name, type ofqueue, and associated ddnames at your installation.

Symbolic Feedback CodeEDC4VD

EDC5102I The transient data queue was notopened for the standard streams.

ExplanationWhen the first I/O operation was requested for stdoutor stderr when running under CICS, the Transient DataQueue inquiry indicated that the requested TD queuewas not opened.


Programmer responseVerify that the start-up CICS JCL opened the specifiedTD queues correctly.

Symbolic Feedback CodeEDC4VE

EDC5103I An attempt was made to mapremote queues to the standardstreams under CICS.

ExplanationWhen the first I/O operation was requested for stdoutor stderr when running under CICS, the Transient DataQueue inquiry indicated that the requested queue wasa REMOTE queue.


Programmer responseCorrect the start-up JCL to specify (using theDFHDCT macro) the standard stream queues to beEXTRAPARTITION, INTRAPARTITION, or INDIRECT.

Symbolic Feedback CodeEDC4VF

EDC5106I An error occurred creating ahiperspace memory file.

ExplanationAn error has occurred while trying to create ahiperspace for a 'type=memory(hiperspace)' file. Theerror may result from a shortage of resources.

System actionThe fopen()/freopen() or other I/O operation fails.

Programmer responseCheck with your system programmer if hiperspacefacilities are available at your installation, and ifavailable, if there is currently a shortage of resourcesfor hiperspaces.

Symbolic Feedback CodeEDC4VI

EDC5107I An error occurred writing to ahiperspace memory file.


ExplanationAn error occurred when writing to a hiperspacememory file. The return code from the HSPSERV macrowas greater than 4.


Programmer responseCheck the __amrc structure for the return codefrom HSPSERV. Refer to z/OS MVS Programming:Assembler Services Reference ABE-HSP for moreinformation regarding the return code. See z/OS XLC/C++ Programming Guide for more information on the__amrc structure.

Symbolic Feedback CodeEDC4VJ

EDC5108I An error occurred reading from ahiperspace memory file.

ExplanationAn error occurred when reading from a hiperspacememory file. The return code from the HSPSERV macrowas greater than 4.

System actionThe read I/O operation fails.

Programmer responseCheck the __amrc structure for the return codefrom HSPSERV. Refer to z/OS MVS Programming:Assembler Services Reference ABE-HSP for moreinformation regarding the return code. See z/OS XLC/C++ Programming Guide for more information on the__amrc structure.

Symbolic Feedback CodeEDC4VK

EDC5111I Permission denied.

ExplanationAn attempt was made to access a file in a way thatviolates its file access permissions. This message isequivalent to the POSIX.1 EACCES errno.

System actionThe access request is denied. The applicationcontinues to run.

Programmer responseThe specific reason for the access denial depends onthe function being attempted. Refer to z/OS XL C/C++ Runtime Library Reference for the function beingattempted for the specific reason for failure.

Symbolic Feedback CodeEDC4VN

EDC5112I Resource temporarily unavailable.

ExplanationA (temporary) condition has occurred which makesthe resource unavailable. Later calls may completenormally. This message is equivalent to the POSIX.1EAGAIN errno.


Programmer responseThe reason for the resource being unavailable dependson the function being attempted. Refer to z/OS XLC/C++ Runtime Library Reference for the function beingattempted for the specific reason for failure.

Symbolic Feedback CodeEDC4VO

EDC5113I Bad file descriptor.

ExplanationThe file descriptor used referred to a file which wasnot open or was out of range, or a read request wasmade to a file that was only open for writing, or awrite request was made to a file that was open onlyfor reading. This message is equivalent to the POSIX.1EBADF errno.



Programmer responseRefer to z/OS XL C/C++ Runtime Library Reference forthe function being attempted for the specific reasonfor failure.

Symbolic Feedback CodeEDC4VP

EDC5114I Resource busy.

ExplanationAn attempt was made to use a system resourcethat was not available because it was being used byanother process or thread in a manner that wouldhave conflicted with the request being made by thisprocess/thread. This message is equivalent to thePOSIX.1 EBUSY errno.



Symbolic Feedback CodeEDC4VQ

EDC5115I No child processes.

ExplanationA wait() or waitpid() function was executed bya process that had no existing or unwaited-for childprocesses. This message is equivalent to the POSIX.1ECHILD errno.


Programmer responseEnsure that a child process exists.

Symbolic Feedback CodeEDC4VR

EDC5116I Resource deadlock avoided.

ExplanationAn attempt was made to lock a system resourcethat would have resulted in a deadlock situation. Thismessage is equivalent to the POSIX.1 EDEADLK errno.


Programmer responseRefer to z/OS XL C/C++ Programming Guide for thefunction being attempted for the specific reason forfailure.

Symbolic Feedback CodeEDC4VS

EDC5117I File exists.

ExplanationAn inappropriate action was requested for an existingfile. For instance, a mkdir() is attempted for a filethat already exists. This message is equivalent to thePOSIX.1 EEXIST errno.



Symbolic Feedback CodeEDC4VT

EDC5118I Incorrect address.

ExplanationThe system detected an invalid address when using anargument of a call. Note that not all functions detectthis error. This message is equivalent to the POSIX.1EFAULT errno.



Programmer responseRefer to z/OS XL C/C++ Runtime Library Reference forthe function being attempted for the specific reasonfor failure. This failure is usually caused by an invalidargument address.

Symbolic Feedback CodeEDC4VU

EDC5119I File too large.

ExplanationThe size of a file would exceed the maximum allowed.The maximum file size allowed for z/OS UNIX filesystem files is 2 gigabytes. This message is equivalentto the POSIX.1 EFBIG errno.


Programmer responseEnsure that enough space is available in the file.

Symbolic Feedback CodeEDC4VV

EDC5120I Interrupted function call.

ExplanationAn asynchronous signal was caught by the (POSIX)process during the execution of an interruptiblefunction, and the signal handler (or default action)resulted in a normal return. This resulted in theinterrupted function returning this error condition. Thismessage is equivalent to the POSIX.1 EINTR errno.

System actionThe request fails. The application continues to run.

Programmer responseRefer to z/OS XL C/C++ Runtime Library Reference forthe function being attempted for possible side effectsfrom the function being interrupted.

Symbolic Feedback CodeEDC500

EDC5121I Invalid argument.

ExplanationAn argument supplied was invalid. This message isequivalent to the POSIX.1 EINVAL errno.




EDC5122I Input/output error.

ExplanationAn input or output error occurred. This message isequivalent to the POSIX.1 EIO errno.




EDC5123I Is a directory.

ExplanationThe program attempted to write to a file descriptorthat is a directory. This message is equivalent to thePOSIX.1 EISDIR errno.


Programmer responseEnsure that the file being written to is not a directory.



EDC5124I Too many open files.

ExplanationAn attempt was made to open more than themaximum number of file descriptors allowed for this(POSIX) process. This message is equivalent to thePOSIX.1 EMFILE errno.


Programmer responseThe maximum number of files allowed per (POSIX)process is controlled by the OPEN_MAX run-timeinvariant, which can be determined during programexecution using the sysconf() function.


EDC5125I Too many links.

ExplanationAn attempt was made to have the link count of afile exceed the maximum value allowed. For instance,this can occur while using the link() or rename()functions. This message is equivalent to the POSIX.1EMLINK errno.


Programmer responseThe maximum number of links for a file is establishedby the LINK_MAX pathname variable value, andwhich can be determined at execution time using thepathconf() function.


EDC5126I Filename too long.

ExplanationThe size of a pathname string exceeded the maximumallowed, or a pathname component was longerthan the maximum allowed and no truncation is in

effect. This message is equivalent to the POSIX.1ENAMETOOLONG errno.


If this is a DLL failure, and the _EDC_DLL_DIAGenvironment variable is not set to QUIET,a corresponding CEE3597I message is issuedto the Language Environment message file.Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.

If this is a DLL failure, a CEEDLLF DLL failure controlblock is populated with further DLL error diagnostics.

Programmer responseThe maximum allowable pathname is controlledby the PATH_MAX pathname variable value, whichcan be determined at execution time using thepathconf() function. The maximum allowable filename is controlled by the NAME_MAX pathnamevariable value, which can be determined at executiontime using the pathconf() function. Truncationof the pathname component is not allowed if the_POSIX_NO_TRUNC execution time symbolic is set.This can be determined by using the pathconf()function.


EDC5127I Too many open files in system.

ExplanationThe system reached its predefined limit for files openat one time. This message is equivalent to the POSIX.1ENFILE errno.


Programmer responseThe request may succeed later if fewer files are in use.


EDC5128I No such device.


ExplanationThe function being attempted is not allowed by thespecified device. For instance, the program attemptedto read from a printer. This message is equivalent tothe POSIX.1 ENODEV errno.




EDC5129I No such file or directory.

ExplanationA name in the pathname does not exist, or thepathname is an empty string. This message isequivalent to the POSIX.1 ENOENT errno.


Programmer responseEnsure the pathname for the object being accessedis correct. Refer to z/OS XL C/C++ Runtime LibraryReference for the function being attempted, for thespecific reason for failure.


EDC5130I Exec format error.

ExplanationA request was made to execute a file that was notin a format that may be executed (however, the filedoes have the appropriate permissions). This messageis equivalent to the POSIX.1 ENOEXEC errno.



Symbolic Feedback CodeEDC50A

EDC5131I No locks available.

ExplanationNo file and/or record locks are available. The systemlimit has been reached. This message is equivalent tothe POSIX.1 ENOLCK errno.



Symbolic Feedback CodeEDC50B

EDC5132I Not enough memory.

ExplanationThere is not enough memory space available to createthe new object. This message is equivalent to thePOSIX.1 ENOMEM errno.



Symbolic Feedback CodeEDC50C

EDC5133I No space left on device.

ExplanationDuring a write() function to a file, there was no freespace left in the z/OS UNIX file system. This error may


also occur when extending a directory. This message isequivalent to the POSIX.1 ENOSPC errno.


Programmer responseAllocate additional space for the file system. Referto z/OS XL C/C++ Runtime Library Reference for thefunction being attempted for the specific reason forfailure.

Symbolic Feedback CodeEDC50D

EDC5134I Function not implemented.

ExplanationThe function to be executed has not beenimplemented. This message is equivalent to thePOSIX.1 ENOSYS errno.


Programmer responseThe function may not be used by the applicationprogram.

Symbolic Feedback CodeEDC50E

EDC5135I Not a directory.

ExplanationA component in a pathname or directory specifiedan object that was not a directory. This message isequivalent to the POSIX.1 ENOTDIR errno.



Symbolic Feedback CodeEDC50F

EDC5136I Directory not empty.

ExplanationA directory that was expected to be empty wasnot. This message is equivalent to the POSIX.1ENOTEMPTY errno.



Symbolic Feedback CodeEDC50G

EDC5137I Inappropriate I/O controloperation.

ExplanationA control function was attempted for a file or a specialfile for which the operation was inappropriate. Forinstance, the file is not a terminal. This message isequivalent to the POSIX.1 ENOTTY errno.



Symbolic Feedback CodeEDC50H

EDC5138I No such device or address.

ExplanationInput or output on a special file referred to a devicethat did not exist, or made a request beyond the limitsof the device. For instance, I/O was sent to a tape drivethat is not online. This message is equivalent to thePOSIX.1 ENXIO errno.




Symbolic Feedback CodeEDC50I

EDC5139I Operation not permitted.

ExplanationAn attempt was made to perform an operation limitedto processes with appropriate privileges, or to theowner of a file or other resource. This message isequivalent to the POSIX.1 EPERM errno.



Symbolic Feedback CodeEDC50J

EDC5140I Broken pipe.

ExplanationA write was attempted on a pipe or FIFO for whichthere was no process to read the data. This message isequivalent to the POSIX.1 EPIPE errno.



Symbolic Feedback CodeEDC50K

EDC5141I Read-only file system.

ExplanationAn attempt was made to modify a file or directoryon a file system that was read-only. This message isequivalent to the POSIX.1 EROFS errno.



Symbolic Feedback CodeEDC50L

EDC5142I Invalid seek.

ExplanationA seek function was issued on a pipe or FIFO. It isinvalid to do a positioning operation on a pipe or FIFO.This message is equivalent to the POSIX.1 ESPIPEerrno.


Programmer responseDo not attempt a seek function on a device that cannotseek.

Symbolic Feedback CodeEDC50M

EDC5143I No such process.

ExplanationThe process ID does not correspond to an existingprocess. The UID or userid is not defined, or theOMVS segment is not setup correctly. This error mayalso apply to the process group ID. This message isequivalent to the POSIX.1 ESRCH errno.




Symbolic Feedback CodeEDC50N

EDC5144I Improper link.

ExplanationA link to a file on another file system was attempted.This message is equivalent to the POSIX.1 EXDEVerrno.


Programmer responseFiles may be linked only within the same file system.Refer to z/OS XL C/C++ Runtime Library Reference forthe function being attempted for the specific reasonfor failure.

Symbolic Feedback CodeEDC50O

EDC5145I Arg list too long.

ExplanationThe sum of the number of bytes for the new processimage's argument list and the environment list wasgreater than the system limit.


Programmer responseThe system limit is defined by the ARG_MAX run-timeinvariant value, and can be determined at executiontime using the sysconf() function. Refer to z/OS XLC/C++ Runtime Library Reference for the function beingattempted for the specific reason for failure.

Symbolic Feedback CodeEDC50P

EDC5146I Too many levels of symbolic links.

ExplanationOnly POSIX_SYMLOOP symlinks are allowed duringpathname resolution. This message is equivalent tothe POSIX.1 ELOOP errno. POSIX_SYMLOOP is aninvariant variable.


Programmer responseVerify that the specified pathname can be resolved,and that no loop exists (of a symbolic link referringto itself). Refer to z/OS XL C/C++ Runtime LibraryReference for the function being attempted for thespecific reason for failure.

Symbolic Feedback CodeEDC50Q

EDC5147I Illegal byte sequence.

ExplanationThe string contains an illegal sequence of bytes. Forexample, an unmatched shift out / shift in conditionexists. This message is equivalent to the z/OS UNIXSystem Services errno, EILSEQ.



Symbolic Feedback CodeEDC50R

EDC5149I Value Overflow Error.

ExplanationA value is too large to be stored in the data type.



Programmer responseRework the program to reissue the request using alarger data type. For example, if working with largefiles, rework the program using the _LARGE_FILESfeature. This message is equivalent to the errno,EOVERFLOW.

Symbolic Feedback CodeEDC50T

EDC5150I UNIX System Services is notactive.

ExplanationThe function being requested cannot be performedbecause the UNIX System Services kernel is not active.This message is equivalent to the EMVSNOTUP errno.


Programmer responseHave the operator start UNIX System Services (STARTOMVS).

Symbolic Feedback CodeEDC50U

EDC5151I Dynamic allocation error.

ExplanationA z/OS UNIX file system or a VM/ESA Byte File System(BFS) could not be mounted during dynamic allocation.The dynamic allocation reason code returned in errno2is documented in z/OS MVS Programming: AuthorizedAssembler Services Guide or VM/ESA ApplicationDevelopment Guide: Authorized Assembler LanguagePrograms. This message is equivalent to the errno,EMVSDYNALC.


Programmer responseHave the system programmer correct the allocation ofthe z/OS UNIX file system data set or VM/ESA BFS.

Symbolic Feedback CodeEDC50V

EDC5152I Common VTOC access facility(CVAF) error.

ExplanationThe mount of a z/OS UNIX file system failed. TheCVAF reason code is returned in errno2. See z/OSDFSMSdfp Diagnosis for an explanation. This messageis equivalent to the z/OS UNIX System Services errno,EMVSCVAF.


Programmer responseHave the system programmer correct the allocation ofthe z/OS UNIX file system.


EDC5153I Catalog obtain error.

ExplanationThe mount of a z/OS UNIX file system failed. Thecatalog return code and reason code are returned inerrno2. The third byte of errno2 is the catalog returncode. The fourth (last) byte of errno2 is the catalogreason code. See message IDC3009I in z/OS MVSSystem Messages, Vol 6 (GOS-IEA) for an explanation.This message is equivalent to the z/OS UNIX SystemServices errno, EMVSCATLG.


Programmer responseHave the system programmer correct the allocation ofthe z/OS UNIX file system.


EDC5156I Process initialization error.

ExplanationA process initialization error has occurred. A furtherexplanation can be found in z/OS UNIX System ServicesProgramming: Assembler Callable Services Referenceor z/VM®: OpenExtensions Callable Services Reference.


System actionProcess does not start.

Programmer responseUse the function errno2() to retrieve the value ofthe UNIX System Services kernel reason code todetermine further information from z/OS UNIX SystemServices Programming: Assembler Callable ServicesReference or z/VM: OpenExtensions Callable ServicesReference.


EDC5157I An internal error has occurred.

ExplanationThis message is equivalent to the z/OS UNIX SystemServices errno, EMVSERR or ECMSERR.

System actionA system dump is taken of the error and MVS or VMattempts to continue.

Programmer responseReport this problem to your system programmer.


EDC5158I Bad parameters were passed tothe service.

ExplanationAn incorrect parameter was passed to z/OS UNIX.This message is equivalent to the z/OS UNIX SystemServices errno, EMVSPARMERR.




EDC5159I The Physical File Systemencountered a permanent fileerror.

ExplanationThis message is equivalent to the z/OS UNIX SystemServices errno, EMVSPFSFILERR or ECMSPFSFILE.




EDC5160I Bad character in environmentvariable name.

ExplanationAn invalid character was found in the 'name' or 'value'string specified on a getenv() or setenv() function.This message is equivalent to the z/OS UNIX SystemServices errno, EMVSBADCHAR.




EDC5162I The Physical File Systemencountered a system error.

ExplanationThis message is equivalent to the z/OS UNIX SystemServices errno, EMVSPFSPERMERR or ECMSPFSPERM.





EDC5163I SAF/RACF extract error.

ExplanationAn authorization failure occurred when attempting theservice. This message is equivalent to the z/OS UNIXSystem Services errno, EMVSSAFEXTRERR.




EDC5164I SAF/RACF error.

ExplanationAn internal SAF/RACF error occurred. This message isequivalent to the z/OS UNIX System Services errno,EMVSSAF2ERR.




EDC5165I System TOD clock not set.

ExplanationThe system time of day (TOD) clock is in error,stopped, or in a non-operational state. This messageis equivalent to the z/OS UNIX System Services errno,EMVSTODNOTSET.




EDC5166I Access mode argument onfunction call conflicts withPATHOPTS parameter on JCL DDstatement.

ExplanationAn open or reopen was issued to a DD whichspecified PATHOPTS. The PATHOPTS specified on theDD conflict with those specified in the function call.This message is equivalent to the z/OS UNIX SystemServices errno, EMVSPATHOPTS.


Programmer responseCorrect either the open/reopen call or the PATHOPTSspecified on the DD being opened.


EDC5167I Access to the UNIX SystemServices version of the C RTL isdenied.

ExplanationAn attempt was made to issue an Open C libraryfunction that has a dependency on UNIX SystemServices and the subsystem was not available or at theincorrect release level. This message is equivalent tothe errno, EMVSNORTL.


Programmer responseYou need to either install the correct level of thesubsystem or modify your program to not issue thefunction or conditionally issue the function.



EDC5168I Password has expired.

ExplanationThe verification request has failed because thepassword or password phrase has expired. Thismessage is equivalent to the z/OS UNIX SystemServices errno, EMVSEXPIRE.


Programmer responseChange the password or the password phrase.


EDC5169I Password is invalid.

ExplanationThe verification or change password or passwordphrase request has failed because the suppliedpassword or password phrase is invalid. This messageis equivalent to the z/OS UNIX System Services errno,EMVSPASSWORD.


Programmer responseCorrect the supplied password or password phrase,and retry the request.


EDC5170I An error was encountered withWLM.

ExplanationA WLM error was detected.


Programmer responseReport the failure to your local administrator for theWLM function. Try the application again when theproblem has been corrected.


EDC5171I An error was encountered withCPL.

ExplanationA CPL error was detected.


Programmer responseReport the failure to your local administrator for theCPL function. Try the application again when theproblem has been corrected.


EDC5172I An error was encounteredwith Application ResponseMeasurement (ARM) component.

ExplanationAn Application Response Measurement (ARM) errorwas detected.


Programmer responseThe return value of the failed service contains thedetailed error code. Try again, when the problem hasbeen corrected.


EDC5200I The application contains aLanguage Environment memberlanguage that cannot tolerate afork().


ExplanationAn application that uses the fork() or vfork()functions cannot use other Language Environmentmember languages that do not support fork() orvfork().

System actionThe fork() function is not performed.

Programmer responseRestructure your application so that it containsonly high level languages that support fork() orvfork(). C/C++, COBOL, and PL/I tolerate fork()and vfork(), but FORTRAN does not. This messagecan only be issued from within a single-threadenvironment. In a multithread environment, messageEDC5232I is issued.


EDC5201I The Language Environmentmessage file was not found in thehierarchical file system.

ExplanationFor Language Environment messaging to workcorrectly in a child process, the Language Environmentmessage file must reside in the hierarchical filesystem.


Programmer responseDefine your message file as a hierarchical file.


EDC5202E DLL facilities are not supportedunder SPC environment.

ExplanationAn SPC application is attempting to use DLL callableservices, or the SPC application is compiled with DLLcompiler options.

System actionThe request is not completed.

Programmer responseMake sure that dllload(), dllqueryvar(),dllqueryfn(), and dllfree() functions are notinvoked from your application, or your application isnot compiled with the DLL compile-time option.


EDC5203E DLL facilities are not supportedunder POSIX environment.

ExplanationA POSIX application is attempting to use DLL callableservices, or the POSIX application is compiled with theDLL compiler option.

System actionThe request is not completed.

Programmer responseMake sure that dllload(), dllqueryvar(),dllqueryfn(), and dllfree() functions are notinvoked from your application, or your application isnot compiled with the DLL compiler-time option.


EDC5204E Not enough storage to load DLLmodule.

ExplanationNot enough storage was available to load therequested DLL load module into virtual storage. If thiswas an implicit load request, this message is precededby message EDC6063I that identifies the DLL loadmodule name.

System actionThe DLL module is not loaded. If the _EDC_DLL_DIAGenvironment variable is not set to QUIET, acorresponding CEE3500S or CEE3554S messageis issued to the Language Environment messagefile. Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off


_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.


Programmer responseEnsure that the REGION size is large enough to run theapplication. If necessary, delete modules not currentlyneeded by the application, or free unused storage, andretry the load request.


EDC5205S DLL module not found.

ExplanationThe system could not find the DLL load modulename specified on the parameter list to LanguageEnvironment load service, in either the job libraryor link library. If this was an implicit load request,this message is preceded by message EDC6063I thatidentifies the DLL load module name.

System actionDLL module is not loaded.

If the _EDC_DLL_DIAG environment variable is notset to QUIET (and not set to MSG for CEE3501S),a corresponding CEE3501S or CEE3570S messageis issued to the Language Environment messagefile. Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.


Programmer responseEnsure that the requested DLL name was correctlymodified. Make sure that the job step indicates thecorrect library. Correct the error and run the job stepagain.


EDC5206S DLL module name too long.

ExplanationThe module name length is greater than the namelength supported by the underlying operating system.If this was an implicit load request, this message ispreceded by message EDC6063I that identifies theDLL load module name.

System actionThe name length is truncated to the name lengthsupported by the underlying operating system. Therequested module may or may not be loaded.

If the _EDC_DLL_DIAG environment variable is notset to QUIET, a corresponding CEE3502S messageis issued to the Language Environment messagefile. Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.


Programmer responseCorrect the module name length and run the job again.

Symbolic Feedback CodeEDC52M

EDC5207S Load request for DLL load moduleunsuccessful.

ExplanationThe system cannot load the DLL load module. If thiswas an implicit load request, this message is precededby message EDC6063I that identifies the DLL loadmodule name.

System actionThe DLL module is not loaded. The application mayabend.

If the _EDC_DLL_DIAG environment variable isnot set to QUIET, a corresponding message isissued to the Language Environment message file.Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.



Programmer responseCheck the original abend from the operating system,and refer to the underlying operating system messagemanual for explanation and programmer's action.

Symbolic Feedback CodeEDC52N

EDC5208I dllHandle supplied to thedllqueryvar() function is notavailable for use.

ExplanationThe dllHandle supplied to the dllqueryvar() callis inactive, because the DLL is logically freed by asuccessful call to dllfree().


If the _EDC_DLL_DIAG environment variable is notset to QUIET, a corresponding CEE3572I messageis issued to the Language Environment messagefile. Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.

Programmer responseEnsure that the proper dllHandle is supplied to thedllqueryvar() service, or that the subject DLL is notfreed prematurely.


EDC5209I No variables exported from thisdllHandle.

ExplanationAttempting to query an external variable, but the DLLdoes not contain any imported variables.


If the _EDC_DLL_DIAG environment variable is notset to QUIET, an error corresponding message isalso issued to the Language Environment messagefile. Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off

_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.


Programmer responseEnsure that the DLL load module indicated in the joblibrary or link library is the correct version, and that itcontains the external variable.


EDC5210I Requested variable not found inthis DLL.

ExplanationAttempting to query an external variable, but thevariable name is not found in the export section of theDLL.


If the _EDC_DLL_DIAG environment variable is notset to QUIET, a corresponding CEE3576I or CEE3578Imessage is issued to the Language Environmentmessage file. Other DLL diagnostic options, such asissuing ctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.


Programmer responseEnsure that the variable name specified on thedllqueryvar() function call is correct, or that theDLL load module indicated in the job library or linklibrary is the correct version, and that it contains theexternal variable.


EDC5211I DLL load module does not containa writeable static area.

ExplanationDLL load module that you loaded does not contain anywriteable static.


System actionThe request is ignored. Load module is deleted fromstorage.

Programmer responseEnsure that the load module name specified is correct,or that the DLL load module indicated in the job libraryor link library is the correct version. Also check that theDLL load module was built properly.

1. Specify #pragma export in your source, or compilewith EXPORTALL compiler option.


3. Prelink.


EDC5212I dllHandle supplied to dllqueryfn()function is not available for use.

ExplanationThe dllHandle supplied to dllqueryfn() call isinactive because the DLL is logically freed as a result ofa successful call to the dllfree() function.


If the _EDC_DLL_DIAG environment variable isnot set to QUIET, an error message is alsoissued to the Language Environment message file.Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and the turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.

Programmer responseEnsure that the proper dllHandle is supplied to thedllqueryfn() function, or that the subject DLL is notfreed prematurely.

Symbolic Feedback CodeEDC52S

EDC5213I No functions exported from thisdllHandle.

ExplanationAttempting to query an external function, but the DLLdoes not contain any imported functions.




Programmer responseEnsure that the DLL load module indicated in the joblibrary or link library is the correct version, and that itcontains the external function.


EDC5214I Requested function not found inthis DLL.

ExplanationAttempting to query an external function, but thefunction name is not found in the export section of theDLL.


If the _EDC_DLL_DIAG environment variable is notset to QUIET, a corresponding CEE3574I or CEE3577Imessage is issued to the Language Environmentmessage file. Other DLL diagnostic options, such asissuing ctrace(), signaling a condition, and the turningoff _EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.


Programmer responseEnsure that the function name specified ondllqueryfn() is correct, or that the DLL load moduleindicated in the job library or link library is the correctversion, and that it contains the external function.



EDC5215I Not enough storage available forwriteable static.

ExplanationNot enough heap storage was available for allocationof writeable static for the DLL load module.

System actionThe request is ignored. Load module is deleted fromstorage.

Programmer responseIncrease heap size or free unused heap storage.


EDC5216I dllHandle supplied is NULL.

ExplanationThe dllHandle supplied to the dllfree call is invalid.


If the _EDC_DLL_DIAG environment variable is not setto QUIET, a message is also issued to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, areavailable through the _EDC_DLL_DIAG environmentvariable.

Programmer responseYou must call the dllload service to initialize adllHandle properly before attempting to free a DLL.


EDC5217I No DLLs to be freed.

ExplanationAttempting to free a DLL, but all DLLs are freedalready, or the dllHandle passed is inactive.




Programmer responseEnsure that dllfree() is invoked after the call todllload() is completed successfully, or that youhave no extra calls to dllfree() with this dllHandlein your application.


EDC5218I Logical delete performed, but theDLL is not physically deleted.

ExplanationThe dllfree() function completed successfully. TheDLL is not physically deleted because either thereis an implicit dllload performed against this DLL bythe application, or multiple calls were made to thedllload() service.




Programmer responseIf the DLL was loaded implicitly by referring toan external variable or an external function, it willbe physically deleted by the run-time library atenclave termination. Otherwise, to free the DLL, invokedllfree() with the proper dllHandle.



EDC5220I Invalid dllHandle.

ExplanationThe dllHandle supplied to the dllfree call could not bematched to a DLL loaded by this application.




Programmer responseEnsure that the dllHandle supplied to dllfree()is the same as the one returned from dllload()accidentally, and that it has not been overwritten.


EDC5221S Load request for DLL notsupported while running C++destructors.

ExplanationThe application is attempting to load a DLL explicitlywhile running C++ destructors.

System actionThe request is ignored. Execution continues but resultsare unpredictable.



Programmer responseMake sure that you are not invoking dllload() fromyour C++ destructors.


EDC5222S IOStreams do not support RecordMode I/O.

ExplanationThe application is attempting to initialize an IOStreamsobject to perform Record Mode I/O. Record Mode I/Ois not supported in IOStreams objects.

System actionThe attempt to initialize the object fails. Executioncontinues.

Programmer responseRemove the "type=record" specification from theconstructor or open() function call.


EDC5223S Too many characters.

ExplanationThe application called the form() function with aformat specifier string that caused form() to writepast the end of the format buffer. form() is providedin stream.h for compatibility.

System actionExecution ends.

Programmer responseSplit the call to form() into two or more calls.


EDC5224S Singularity: log((0,0))

ExplanationThe application is attempting to take the log of (0.0,0.0).


System actionExecution ends.

Programmer responseCorrect the value passed to log() and resubmit.


EDC5225E DLL function is not allowedbecause destructors are runningfor the DLL.

ExplanationA dllfree(), dllqueryvar(), or dllqueryfn() function wasinvoked for a DLL that is currently running destructors.Since destructors are running the DLL is about to befreed. Further function requests using this DLL are notallowed.

System actionThe request failed. Application execution continues.The dllfree() function returns a value of 7. Thedllqueryvar() and dllqueryfn() functions return a nullpointer.

If the _EDC_DLL_DIAG environment variable is notset to QUIET, a corresponding CEE3569E messageis issued to the Language Environment messagefile. Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.


Programmer responseDo not issue DLL function requests from one threadwhile the DLL is being freed from another thread.


EDC5226S A load of DLL from the z/OS UNIXfile system failed.

ExplanationA load attempt for a DLL in the z/OS UNIX filesystem failed. If this was an implicit load request,this message is preceded by message EDC6063I thatidentifies the DLL load module name.

System actionIf the DLL was explicitly loaded using the dllload()function, the request fails and the DLL is not loaded. Ifthe DLL was implicitly loaded by reference to a variableor function contained in it, the application is ends withreturn code 3000.

Programmer responseVerify that the DLL is available in the z/OS UNIX filesystem and that the application has access to the file.


EDC5227I Buffer is not long enough tocontain a path definition.

ExplanationThe request for a path definition for the specifiedddname cannot be satisfied because the path namelength of the path associated with this ddname isgreater than the specified buffer length.


Programmer responseSpecify a larger buffer.


EDC5228I The file referred to is an externallink.

ExplanationAn I/O operation cannot be satisfied because the filereferred to is an external link.


Programmer responseRefer to z/OS UNIX System Services User's Guide forinformation on how to perform I/O operations onexternal links.



EDC5229I No path definition for ddname ineffect.

ExplanationThe request to obtain the path definition for thespecified ddname cannot be satisfied because noOPENVM PATHDEF CREATE command was issued toassociate a BFS path definition with this ddname.


Programmer responseIssue OPENVM PATHDEF CREATE command toassociate this ddname with a path name definition.


EDC5230I ESM error.

ExplanationAn internal External Security Manager (ESM) erroroccurred. This message is equivalent to the z/OS UNIXSystem Services errno ECMSESMERR.

System actionMessages are displayed on the file pool serveroperator console indicating the error and VMprocessing continues.



EDC5231I CP or the external securitymanager had an error.

ExplanationAn error occurred in CP or the external securitymanager. This message is equivalent to the z/OS UNIXSystem Services errno ECPERR.

System actionNone.

Programmer responseTry the command again. If the problem persists, reportit to your system programmer.


EDC5232I The function failed because itwas invoked from a multithreadenvironment.

ExplanationAn application may not use the exec() or vfork()functions from within a multithread environment. Thefork() function is not permitted within a multithreadenvironment where the application contains a highlevel language other than C/C++. COBOL and PL/Itolerate fork() in a single-thread environment, butnot in a multithread environment. A multithreadfork() is not allowed in a Language Environmentpreinitialization (CEEPIPI) environment.


Programmer responseRestructure your application so that it is notmultithreaded, remove the call to the function, usesupported high level languages, and/or avoid using thefunction in a multithread CEEPIPI environment.


EDC5233S The linkage of the specified localedoesn't match the current run-time environment.

ExplanationThe application attempted to change the current localebut the linkage attributes for the requested localedo not match the linkage attributes of the run-timeenvironment.

This can happen when an application compiled withthe NOXPLINK option runs with the XPLINK(OFF) run-time option but supplies the fully qualified locale pathname for an XPLINK locale. XPLINK locales stored in


the z/OS UNIX file system have a ".xplink" suffix. Theyare usable only when the XPLINK(ON) run-time optionis in effect. This can also happen when an applicationcompiled with the XPLINK option supplies the fullyqualified locale path name for a non-XPLINK locale.

System actionThis can happen when an application compiled withthe NOXPLINK option runs with the XPLINK(OFF) run-time option but supplies the fully qualified locale pathname for an XPLINK locale. XPLINK locales stored inthe z/OS UNIX file system have a ".xplink" suffix. Theyare usable only when the XPLINK(ON) run-time optionis in effect. This can also happen when an applicationcompiled with the XPLINK option supplies the fullyqualified locale path name for a non-XPLINK locale.

Programmer responseThis can happen when an application compiled withthe NOXPLINK option runs with the XPLINK(OFF) run-time option but supplies the fully qualified locale pathname for an XPLINK locale. XPLINK locales stored inthe z/OS UNIX file system have a ".xplink" suffix. Theyare usable only when the XPLINK(ON) run-time optionis in effect. This can also happen when an applicationcompiled with the XPLINK option supplies the fullyqualified locale path name for a non-XPLINK locale.

EDC5234S The DLL cannot be loaded becauseit does not contain a CEESTARTCSECT.

ExplanationAn AMODE 31 application is attempting an explicitload of a DLL that does not contain a CEESTART CSECT.If this is an AMODE 64 application, the DLL mustcontain a CELQSTRT CSECT.

System actionThe function is not performed. If the _EDC_DLL_DIAGenvironment variable is not set to QUIET, acorresponding CEE3550S or CEE3595S messageis issued to the Language Environment messagefile. Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable. A CEEDLLFDLL failure control block is also populated with moreDLL error diagnostics.

Programmer responseMake sure that when you generate the DLL for whichthe dllload() service is failing, it contains theappropriate CEESTART or CELQSTRT CSECT.

EDC5235S The fetched executable does notcontain a fetchable entry point.

ExplanationSpecifically, one or more of the following errors mighthave occurred:

• The application is attempting to fetch() anexecutable that has been compiled with the XPLINKoption but does not have a fetchable entry point.

• The application is attempting to fetch() a non-XPLINK executable that has CEESTART as the entrypoint, but does not contain a fetchable entry point.


Programmer responseFetched XPLINK executables, as well as non-XPLINKexecutables that have CEESTART as the entry point,must have a fetchable entry point specified using the#pragma linkage(..., fetchable) directive.

EDC5236S The fetched executable wascompiled XPLINK but the XPLINKenvironment is not active.

ExplanationThe application is attempting to fetch() anexecutable that has been compiled with the XPLINKoption but the current run-time environment does notsupport XPLINK executables.


Programmer responseXPLINK executables that are to be fetched musthave the XPLINK C run-time environment active.This can be achieved by specifying the XPLINK(ON)run-time option. Another alternative is to compileyour main program with the XPLINK compiler option.If main() is compiled XPLINK then the XPLINK Crun-time environment will be active by default, andyou may also have the added benefit of enhancedperformance. For more information on XPLINK, referto z/OS Language Environment Programming Guide


EDC5237S The DLL was not found in anauthorized library.

ExplanationThe application is authorized and is attempting toexplicitly load a DLL, but that DLL could not be found inan authorized library or concatenation of libraries.

System actionThe function is not performed. If the _EDC_DLL_DIAGenvironment variable is not set to QUIET,a corresponding CEE3518S message is issuedto the Language Environment message file.Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable. A CEEDLLFDLL failure control block is also populated with furtherDLL error diagnostics.

Programmer responseMake sure the module exists in a system or user-defined authorized library. Correct the error, and runthe application again.

EDC5238E Not enough storage to fetchmodule.

ExplanationNot enough storage was available to fetch therequested load module into virtual storage.

System actionThe module is not fetched.

Programmer responseEnsure that the REGION size is large enough to run theapplication. If necessary, delete modules not currentlyneeded by the application, or free unused storage, andretry the fetch function.

EDC5239S Fetched module not found.

ExplanationThe system could not find the load module namespecified to the fetch function in either the job libraryor link library.

System actionThe module is not fetched.

Programmer responseEnsure that the requested fetch name was correctlyspecified. Make sure that the job step indicates thecorrect library. Correct the error and run the job stepagain.

EDC5240S Fetched module name too long.

ExplanationThe length of the name specified on the fetch()function is greater than the name length supported bythe underlying operating system.

System actionThe name length is truncated to the name lengthsupported by the underlying operating system. Therequested module may or may not be loaded.

Programmer responseCorrect the module name length and run the job again.

EDC5241S Load request for fetch load moduleunsuccessful.

ExplanationThe system cannot load the load module specified onthe fetch() function.

System actionThe fetched module is not loaded. The application mayabend.

Programmer responseCheck the original abend from the operating system,and refer to the underlying operating system messagemanual for explanation and programmer's action.

EDC5242S The fetched module was not foundin an authorized library.

ExplanationThe application is authorized and is attempting tofetch a module, but that module could not be foundin an authorized library or concatenation of libraries.



Programmer responseMake sure the module exists in a system or user-defined authorized library. Correct the error, and runthe application again.

EDC5244I The program, module or DLL is notsupported in this environment.

ExplanationThe program, module or DLL specified on the functioncall contains one or more languages that are notsupported on this version of the operating system.


If this is a C dllload() request, and the_EDC_DLL_DIAG environment variable is not set toQUIET, an error message is sent to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,and turning off _EDC_DLL_DIAG diagnostics, areavailable through the _EDC_DLL_DIAG environmentvariable.

If this is a C dllload() request, a CEEDLLF DLL failurecontrol block is populated with further DLL errordiagnostics.

Programmer responseUse a supported program, module or DLL for thisfunction when running on this version of the operatingsystem.

EDC5245I Data is not valid.

ExplanationThe parameter is not the correct size or containsan incorrect value. For the Enterprise IdentityMapping services, the EIM return code structuredoes not meet the minimum size requirement. SeeEIM_RC_MIN_SIZE in <eim.h> for the minimum size.


Programmer responseCorrect the parameter and try the service again.

EDC5246I Unknown system state.

ExplanationA program exception occurred or an unexpectederror was detected by an underlying service. EIMapplications may receive this errno when an LDAPservice returns an unexpected error or a problem wasdetected in the value of an EIM attribute.


Programmer responseCorrect the problem and try the service again.Applications using Enterprise Identity Mapping willreceive an informative error string to aid withdiagnosing the problem.

EDC5247I Operation not supported.

ExplanationThe requested operation is not supported on z/OS.


Programmer responseReplace the operation with support that is available onz/OS.

EDC5248I The object name specified is notcorrect

ExplanationThe name specified is not valid. EIM applicationsreceive this errno when the domain, registry, oridentifier name is not valid or the caller does nothave enough permissions to perform the requestedfunctions.


Programmer responseVerify the name exists in the EIM domain and thatthe caller has the necessary permissions to access thespecified LDAP data.

EDC5249I The function is not allowed.


ExplanationThe requested function could not be performedbecause the data has not been properly removed. AnEIM application receives this errno when it attemptsto remove a system registry when it has an applicationregistry or when it attempts to remove a domain whenthe domain is not empty.


Programmer responseIdentify the functions that must be performed beforeretrying the service again. EIM applications mustremove the application registry before attempting toremove a system registry and empty the domainof identifiers and associations before attempting todelete a domain.

EDC5250I The utmpx database formatcannot be read.

ExplanationThe requested function was not able to determine therecord format in use by the UTMPX database. UTMPXinterfaces depend on the version indicator in the firstrecord of the UTMPX file.


Programmer responseThe version member of the first record in the UTMPXfile contains invalid data. Check for other applicationsthat write to the UTMPX database but that do not usepututxline() to manage the write().

EDC5251I Input dllHandle not permitted forthis DLL function.

ExplanationThe dllHandle supplied to this DLL function call couldnot be matched to a dllHandle returned from dllload().


If the _EDC_DLL_DIAG environment variable is notset to QUIET, an error is issued to the LanguageEnvironment message file. Other DLL diagnosticoptions, such as issuing ctrace(), signaling a condition,

and turning off _EDC_DLL_DIAG diagnostics, areavailable through the _EDC_DLL_DIAG environmentvariable.


Programmer responseEnsure that the dllHandle supplied to dllfree(),dllqueryfn(), or dllqueryvar() is the same asthe one returned from dllload(). Make sure that thedllHandle was not returned from from dlopen().

EDC5252S A call was made from aNOXPLINK-compiled applicationto an XPLINK-compiled exportedfunction in DLL and theXPLINK(ON) runtime option wasnot specified.

ExplanationDuring Language Environment initialization, XPLINKresources need to be allocated if any XPLINK-compiled functions are going to be called during theexecution of the application. Language Environmenttries to detect this by inspecting the attributes ofthe initial program. If the initial program consistsof NOXPLINK-compiled functions that may at somepoint call an XPLINK-compiled function, then theXPLINK(ON) runtime option must be used to indicateto Language Environment initialization that XPLINKresources should be allocated.

System actionIf this was an implicit DLL reference, the condition issignaled. If the condition is not handled, the defaultaction is to terminate the enclave. If this was anexplicit DLL Load (CEEPLDE) or DLL Open (CEEPOPDL)request, the feedback code is returned to the caller.If this was an explicit C dlopen() request, this error isreturned to the caller through a subsequent call to theC dlerror() function.





EDC5253S An AMODE64 application isattempting to load an AMODE31DLL load module.

ExplanationAn application with AMODE=64 is attempting to loada DLL load module link-edited as an AMODE=31 loadmodule.

System actionDLL module is not loaded. The invoked function fails.



Programmer responseEnsure that the AMODE of the application and theAMODE of the DLL load module are the same. Re-linkyour DLL load module to have AMODE=64.

EDC5254S An AMODE31 application isattempting to load an AMODE64DLL load module.


System actionDLL module is not loaded. The invoked function fails.




EDC5255S An AMODE31 application isattempting to fetch() an AMODE64executable.

ExplanationAn application with AMODE=31 is attempting to fetchan executable link-edited as an AMODE=64 programobject.

System actionFetched executable is not loaded. The fetch() functionfails.

Programmer responseOnly applications that have been linked AMODE=64can fetch an executable that is AMODE=64. Re-linkeither your application or your fetched executable tohave the correct matching AMODE.

EDC5256S An AMODE64 application isattempting to fetch() an AMODE31executable.

ExplanationAn application with AMODE=64 is attempting to fetchan executable link-edited as an AMODE=31 programobject.

System actionFetched executable is not loaded. The fetch() functionfails.

Programmer responseOnly applications that have been linked AMODE=31can fetch an executable that is AMODE=31. Re-linkeither your application or your fetched executable tohave the correct matching AMODE.

EDC5257I Function cannot be called in thechild process of a fork() from amultithreaded process until exec()is called.

ExplanationOnly async-safe functions are supported in thisenvironment.



Programmer responseRestructure your application so that it is notmultithreaded at the time of the fork(), or only useasync-safe functions in the child process up untilexec() is called. Refer to the z/OS XL C/C++ RuntimeLibrary Reference for the list of async-safe functions.


EDC5258I A CUN_RS_NO_UNI_ENV error wasissued by Unicode Services.

ExplanationAn iconv() function received a CUN_RS_NO_UNI_ENVerror from z/OS Unicode Services.

Programmer responseRefer to Support for z/OS Unicode: z/OS UnicodeServices documentation for user action.

EDC5259I A CUN_RS_NO_CONVERSION errorwas issued by Unicode Services.

ExplanationAn iconv() function received aCUN_RS_NO_CONVERSION error from z/OS UnicodeServices.


EDC5260I A CUN_RS_TABLE_NOT_ALIGNEDerror was issued by UnicodeServices.

ExplanationAn iconv() function received aCUN_RS_TABLE_NOT_ALIGNED error from z/OSUnicode Services.


EDC5261S There is not enough storage toobtain a DLL function or variablepointer.

ExplanationThere is insufficient heap storage to satisfy a dlsym(),dllqueryfn(), or dllqueryvar() request.


If the _EDC_DLL_DIAG environment variable isnot set to QUIET, a corresponding message isissued to the Language Environment message file.Other DLL diagnostic options, such as issuingctrace(), signaling a condition, and turning off_EDC_DLL_DIAG diagnostics, are available throughthe _EDC_DLL_DIAG environment variable.



EDC5262I An iconv() function encountered anunexpected error while using z/OSUnicode Services.

ExplanationAn iconv() function encountered an unexpected errorwhile using z/OS Unicode Services.

Programmer responseRefer to message EDC6258 for additional information.

EDC5263I Byte I/O was attempted on a filethat was opened for blocked I/O.

ExplanationOne of the byte I/O functions was invoked with a filethat was opened using ’type=blocked’.


Programmer responseOnly the fread() and fwrite() functions may beused to read or write a file opened for blocked I/O.



EDC5264I Truncation of a block occurredduring an I/O operation.

ExplanationTruncation occurred because the specified blocklength on the write operation was larger than the blockbuffer size.

System actionThe return value depends on the operation attempted.In all cases, the buffer will be written up to the pointwhere truncation occurred.

Programmer responseFor a file opened for blocked I/O, specify a smallernumber of bytes for fwrite().


EDC6000E The raise() function was issued forthe signal SIGFPE.

ExplanationThe program has invoked the raise() function withthe SIGFPE signal specified and the default actionspecified.

System actionThe program is terminated and a traceback or dumpis issued, depending on the TERMTHDACT run-timeoption. A return code of 3000(MVS) or 3000000(VM) isreturned.


Symbolic Feedback CodeEDC5RG

EDC6001E The raise() function was issued forthe signal SIGILL.

ExplanationThe program has invoked the raise() function withthe SIGILL signal specified and the default actionspecified.

System actionThe program is terminated and a traceback or dumpis issued, depending on the TERMTHDACT run-timeoption. A return code of 3000(MVS) or 3000000(VM) isreturned.


Symbolic Feedback CodeEDC5RH

EDC6002E The raise() function was issued forthe signal SIGSEGV.

ExplanationThe program has invoked the raise() function withthe SIGSEGV signal specified and the default actionspecified.

System actionThe program will be terminated and a tracebackor dump is issued, depending on the TERMTHDACTrun-time option. A return code of 3000(MVS) or3000000(VM) is returned.


Symbolic Feedback CodeEDC5RI

EDC6003E The raise() function was issued forthe signal SIGABND.

ExplanationThe program has invoked the raise() function withthe SIGABND signal specified and the default actionspecified.




Symbolic Feedback CodeEDC5RJ

EDC6004E The raise() function was issued forthe signal SIGTERM.

ExplanationThe program has invoked the raise() function withthe SIGTERM signal specified and the default actionspecified.



Symbolic Feedback CodeEDC5RK

EDC6005E The raise() function was issued forthe signal SIGINT.

ExplanationThe program has invoked the raise() function withthe SIGINT signal specified and the default actionspecified.



Symbolic Feedback CodeEDC5RL

EDC6006E The raise() function was issued forthe signal SIGABRT.

ExplanationThe program has invoked the raise() function withthe SIGABRT signal specified and the default actionspecified.



Symbolic Feedback CodeEDC5RM

EDC6007E The raise() function was issued forthe signal SIGUSR1.

ExplanationThe program has invoked the raise() function withthe SIGUSR1 signal specified and the default actionspecified.



Symbolic Feedback CodeEDC5RN

EDC6008E The raise() function was issued forthe signal SIGUSR2.

ExplanationThe program has invoked the raise() function withthe SIGUSR2 signal specified and the default actionspecified.




Symbolic Feedback CodeEDC5RO

EDC6009E The raise() function was issued forthe signal SIGIOERR.

ExplanationThe program has invoked the raise() function withthe SIGIOERR signal specified and the default actionspecified.



Symbolic Feedback CodeEDC5RP

EDC6010E An object was thrown which wasnot caught by any catch clauses.

ExplanationAn object was thrown for which no catch clausesexist to catch it.

System actionThe program ends abnormally.


Symbolic Feedback CodeEDC5RQ

EDC6052S An AMODE 24 application isattempting to load an AMODE 31DLL load module.


System actionThe application ends with return code 3000.

Programmer responseEnsure that the AMODE of the application matchesthat of the run-time library. Language Environment nolonger supports C applications in AMODE=24. Relinkthe application to have AMODE=31.


EDC6053S An AMODE 31 application isattempting to load an AMODE 24DLL load module.

ExplanationAn application with AMODE=31 is attempting to loada DLL load module link-edited as a load module withAMODE=24.

System actionApplication is terminated with return code 3000.



EDC6054S External variable is not found inDLL load module.

ExplanationThe application is attempting to refer to an externalvariable that is not defined in the DLL load module.


Programmer responseEnsure that the DLL load module indicated in the joblibrary or link library is the correct version, and that itcontains the external variable.



EDC6055S External function is not found inDLL load module.

ExplanationThe application is attempting to refer to an externalfunction that is not defined in the DLL load module.


Programmer responseEnsure that the DLL load module indicated in the joblibrary or link library is the correct version, and that itcontains the external function.


EDC6056S Attempting to load a DLL whilerunning C++ destructors.

ExplanationThe application is attempting to load a DLL implicitlywhile running C++ destructors.


Programmer responseMake sure that you are not referring to variables orfunctions implicitly from your C++ destructors.


EDC6057S A DLL load module that youare attempting to load does notcontain a CEESTART csect.

ExplanationThe application is attempting to load a DLL loadmodule implicitly or explicitly, but the CEESTART csectcannot be located within it.


Programmer responseMake sure that when you generate the DLL loadmodule, it contains a CEESTART csect.


EDC6058S There is not enough heap storageto load DLL.

ExplanationThere is insufficient heap storage to satisfy DLL loadrequest.


Programmer responseIncrease the allocation of your application heapstorage by using the heap run-time option.


EDC6059S The DLL that you have loadeddoes not export any variables orfunctions.

ExplanationA DLL was loaded successfully, but the DLL does notexport any variables or functions. Either the definitionside-deck supplied to your application is incorrect, orthe DLL load module is generated incorrectly.


Programmer responseEnsure that the DLL load module was built properly.

1. Specify #pragma export in your source or compilewith EXPORTALL compiler option.


3. Prelink.



EDC6060S The DLL that you are attemptingto load does not contain any Cfunctions.

ExplanationA DLL was loaded successfully, but the load moduledoes not contain any C functions.


Programmer responseMake sure that you are loading the correct loadmodule, and that the DLL load module is builtcorrectly.


EDC6061S You are attempting to load DLLsthat are in a circular list.

ExplanationThe run-time library discovered a deadlock conditionwhile processing a DLL load request. The deadlockcondition exists because the DLLs that are beingloaded depend on each other. The following situationillustrates a deadlock condition. DLL A has staticconstructors that require objects from DLL B. DLL Bhas static constructors that require objects from DLLA. When DLL A is loaded, its static constructors requireobjects from DLL B. This forces DLL B to be loaded,requiring objects from DLL A. Since the loading of DLLA has not completed, a deadlock condition exists.


Programmer responseRemove the circular list dependency from the DLLs.


EDC6062S DLL constructors or destructorsdid not complete, so DLL cannot beused.

ExplanationA DLL being loaded or freed was in the process ofrunning static constructors or destructors but theprocess did not complete (probably because thethread was abnormally terminated). The DLL is leftin an indeterminate state. Another thread that waswaiting for the constructors or destructors to completewhile attempting a load or free of the same DLLdetected this error.


Programmer responseDetermine the cause of the incomplete constructor ordestructor process. Ensure that the constructors ordestructors are not the cause of the thread terminationthat lead to this condition.


EDC6063I DLL name is dll_name.

ExplanationThis message accompanies other DLL load errormessages (for example EDC5205S). It identifies thename of the DLL for which the load failed.

System actionNone.

Programmer responseRefer to the accompanying DLL error message.


EDC6064I Not enough storage was availableto use MEMCHECK vendor heapmanager.

ExplanationThe MEMCHECK vendor heap manager was loaded butthere is insufficient storage to manage this trace anddiagnostic tool.

System actionNone.


Programmer responseIf possible, free unneeded heap storage or Increasethe size of the storage.

EDC6200E An invalid argument list wasspecified.

ExplanationThe parameter list specified to DLLRNAME is invalid.See z/OS XL C/C++ User's Guide for proper syntax.

System actionDLLRNAME: fails with return code 8.

Programmer responseEnsure that:

1. At least 1 input module or DLL is specified.2. The syntax of the parameters matches listed syntax

for environment.3. Valid options are specified correctly.


EDC6201S A failure occurred accessing @1.

ExplanationAn unexpected error occurred when DLLRNAMEaccessed an input file.

System actionDLLRNAME prints out a perror() message thenterminates with rc=16.

Programmer responseLook up subsequent error message and performProgrammer Response if possible (for example, filenot found error might mean to fix input file name).Otherwise, report the problem to your IBM SupportCenter.


EDC6202S A DLL named " @1 " is alreadyimported.

ExplanationA DLLRNAME operation has found that an old DLLname to be renamed is being renamed to a new namethat is already imported in the current module beingprocessed.

System actionDLLRNAME fails with rc=12.

Programmer responseUser has specified DLL to rename, but the new namechosen matches a DLL in the import list.


EDC6203E A DLL name was specified morethan once for a rename.

ExplanationOn a DLLRNAME, user has specified a DLL nametwice in the "oldname=newname" list. Examples are:(A=B,A=C or A=C,B=C or A=B,B=C or A=B,C=A or A=A).


Programmer responseFix the argument list. A DLL cannot appear twice in theargument list.


EDC6204E No argument list was provided.

ExplanationUser did not provide any argument list.


Programmer responseAn argument list must be provided (for example,through SYSIN or standard streams redirection).



EDC6251C The library functionsetjmp(), _setjmp(), sigsetjmp(),getcontext(), or swapcontext()failed when it tried to use thepassed in jmp_buf, sigjmp_buf orucontext_t area.

ExplanationThe library function failed when it tried to initialize thepassed-in buffer. A program check occurred, perhapsbecause the address of the passed-in buffer was notcorrect.

System actionThe application ends.

Programmer responseMake sure that the address of the bufferpassed into setjmp(), _setjmp(), sigsetjmp(),getcontext(), or swapcontext() is correct.

EDC6252C The library function longjmp(),_longjmp(), siglongjmp(),setcontext(), or swapcontext()failed when it tried to use thepassed in jmp_buf, sigjmp_buf orucontext_t area.

ExplanationThe library function failed when it tried to use thethe passed-in buffer. Either the data in the buffer wasincorrect, or a program check occurred because theaddress of the passed-in buffer was not correct.

Programmer responseMake sure that the address of the bufferpassed into setjmp(), _setjmp(), sigsetjmp(),setcontext(), or swapcontext() is correct.Make sure that the buffer has been initializedby setjmp(), _setjmp(), sigsetjmp(), orgetcontext() before it is passed to longjmp(),_longjmp(), siglongjmp(), or setcontext(), orswapcontext().

EDC6253S An error occurred attempting toretrieve the C++ state variablestable from the PPA1.

ExplanationAn invalid C++ PPA1 state variables locator wasdetected.


EDC6254S ASCII applications require aPOSIX(ON) environment. Changeenvironment to POSIX(ON).

ExplanationASCII C-RTL support does not support a POSIX(OFF)environment.

Programmer responseChange environment to POSIX(ON).

EDC6255S ASCII/EBCDIC mode changefailed.

ExplanationASCII/EBCDIC mode change failed. An internal erroroccurred.


EDC6256S ASCII initialization failed.

ExplanationInsufficient memory available.

Programmer responseIncrease the amount of storage available to theapplication.

EDC6257C There is a socket problem, syslogdmay need to be restarted. Until thecondition is resolved, all messageswill be lost.

Explanationsyslog() has not been able to send a message forat least seven minutes. There is a problem with thesocket, syslogd() likely needs to be restarted.

Programmer responseRestart syslogd().


EDC6258I An iconv() function encounteredan unexpected error while usingUnicode Conversion Services. Areturn code of <return code>and reason code of <reasoncode> were returned from UnicodeServices.

ExplanationAn iconv() function encountered an unexpected errorwhile using Unicode Services.

Programmer responseRefer to Support for Unicode: Unicode Services foruser action.

EDC6259S This function is not supportedrunning on hardware that does nothave the Decimal Floating PointFacility installed.

ExplanationThe invoked Decimal Floating Point function cannot beused unless the hardware has the Decimal FloatingPoint Facility installed.

System actionIf unhandled, the enclave is terminated.

Programmer responseBefore using this function, make sure that thehardware has the Decimal Floating Point Facilityinstalled.


EDC7000C Signal delivery has failed becausethe service BPX1SIA failed.

ExplanationThe callable service, BPX1SIA (sigaction()),unexpectedly returned a failure code. This service wasinvoked by the library during delivery of a signal to auser catcher function.



Symbolic Feedback CodeEDC6QO

EDC7001C Signal delivery has failed becausethe service BPX1SPM failed.

ExplanationThe callable service BPX1SPM (sigprocmask())unexpectedly returned a failure code. This service wasinvoked by the library during delivery of a signal to auser catcher function.



Symbolic Feedback CodeEDC6QP

EDC7002C Signal delivery has failed becausethe MVS service CSRL16J failed.

ExplanationThe MVS callable service CSRL16J unexpectedlyreturned a failure code. This service was invoked bythe library following the return from a user signalcatcher function.



Symbolic Feedback CodeEDC6QQ

EDC7003C Invalid signal received fromthe z/OS UNIX System Serviceskernel.

ExplanationThe library has been interrupted by the z/OS UNIXSystem Services kernel to perform default signal


processing. However, the signal was not one of thesupported types (SIGHUP, SIGINT, SIGABRT, SIGILL,SIGFPE, SIGSEGV, SIGPIPE, SIGALRM, SIGTERM,SIGUSR1, SIGUSR2, SIGABND, SIGQUIT, or SIGTRAP).



Symbolic Feedback CodeEDC6QR

EDC7004C The library function sigsetjmp()or siglongjmp() failed because theservice BPX1SPM failed.

ExplanationThe callable service BPX1SPM (sigprocmask())unexpectedly returned a failure code. The library wasattempting to save or restore the signal mask as partof the sigsetjmp() or siglongjmp() functions.



Symbolic Feedback CodeEDC6QS

EDC7005E The getopt() function detectedan invalid option characteroption_char when it was invokedfrom program program_name.

ExplanationThe getopt() function detected that an optioncharacter that was parsed was not one of therecognized set of specified option characters.

System actionThe getopt() function returns the character in error.The application continues to run.

Programmer responseRespecify a recognized option character.

Symbolic Feedback CodeEDC6QT

EDC7006E The getopt() function detected anoption character option_char thatis missing an argument whenit was invoked from programprogram_name.

ExplanationThe getopt() function encountered an optioncharacter that required an option-argument, but theoption-argument was not found.

System actionThe getopt() function returns the character in error.The application continues to run.

Programmer responseRespecify the option character with an option-argument.

Symbolic Feedback CodeEDC6QU

EDC7007C No memory available for therandom() function family internalstructure.

ExplanationThe initialization routine for the random() functionfamily was unable to allocate memory for the internalstructure used by the functions.


Programmer responseReduce memory use and try again.

Symbolic Feedback CodeEDC6QV

EDC7008E No previous regular expression.

ExplanationThe re_comp() function was invoked with either anull pointer argument or a null regular expression, anda compiled regular expression does not currently exist.


System actionThe re_comp() function returns with a pointer to thiserror message. The application continues to run.

Programmer responseInvoke the re_comp() with a valid regular expression.

Symbolic Feedback CodeEDC6R0

EDC7009E Regular expression too long.

ExplanationThe input regular expression for the re_comp()function is too long. The compiled regular expressioncannot fit in the internal work buffer, which is oflimited size.


Programmer responseInvoke the re_comp() with a shorter regularexpression.


EDC7010E paren_pair imbalance.

ExplanationThe re_comp() function detected an error in the inputregular expression. The character sequences $ (leftparenthesis) were found without a matching $ (rightparenthesis), or vice versa.


Programmer responseCorrect the regular expression pattern and retry there_comp().


EDC7011E brace_pair imbalance.

ExplanationThe re_comp() function detected an error in the inputregular expression. The character sequences \{ (leftbrace) were found without a matching \} (right brace),or vice versa.




EDC7012E square_bracket imbalance.

ExplanationThe re_comp() function detected an error in the inputregular expression. The left square bracket [ was foundwithout a matching right square bracket ].




EDC7013E Too many paren_pair pairs.

ExplanationThe re_comp() function detected an error in the inputregular expression. Too many  sub-expression pairswere specified. Up to nine such  pairs are allowed.





EDC7014E Incorrect range values inbrace_pair.

ExplanationThe re_comp() function detected an error in the inputregular expression. The repetition interval specifiedwithin the \{m,n\} is incorrect. Specifically, one or moreof the following errors may have occurred:

• One or more numbers within the \{\} are too large.They must be less than 256.

• Bad numbers (for example, non-numeric values) areused as range values.

• More than two numbers are given within the \{\}.• First number exceeds the second number within the

\{\}.




EDC7015E Back-reference number inbackslash digit incorrect.

ExplanationThe re_comp() function detected an error in the inputregular expression. The back-reference number, digit,in \digit is incorrect. This value must be between 1 and9 (inclusive), and must correspond to one of the earlierbracketed sub-expressions (that is, sub-expressionsenclosed in ). The expression is invalid if less thandigit sub-expressions precede the \digit. For example,if five bracketed sub-expressions are defined in theregular expression, then it is valid to refer to them byspecifying from \1 to \5. However, it is incorrect tospecify \6, \7, \8, or \9.




EDC7016E Incorrect endpoint in rangeexpression.

ExplanationThe re_comp() function detected an error in the inputregular expression. The ending range point in a rangeexpression must collate equal to or higher than thestarting range point. For example, it is an error tospecify [d-a].




EDC7022I USERID:

ExplanationA userid was not specified, while executing the REXECcommand. If a userid was specified, it was notfound to be valid at the host, when searching the$HOME/.netrc file. A userid must be input at theinvocation of this message.

System actionSystem waits for user input of userid.

Symbolic Feedback CodeEDC6RE

EDC7023I PASSWORD:


ExplanationA password was not specified, while executing theREXEC command. If a password was specified, it wasnot found to be valid at the host, when searching the$HOME/.netrc file. A password must be input at theinvocation of this message.

System actionSystem waits for user input.

Symbolic Feedback CodeEDC6RF

EDC7024I $HOME/.netrc file cannot beopened.

ExplanationThe open of the $HOME/.netrc file failed for a reasonother than ENOENT.

System actionThe system continues, asking the user to enter theuser ID and password.

Symbolic Feedback CodeEDC6RG

EDC7025I fstat() failed on $HOME/.netrc file.

ExplanationAn fstat() was performed on the $HOME/.netrc file,and had an unsuccessful return code.

System actionThe system stops trying to find the user ID andpassword through the $HOME/.netrc file. The usermust enter them instead.

Symbolic Feedback CodeEDC6RH

EDC7026I $HOME/.netrc file is not in thecorrect mode.

ExplanationIf the $HOME/.netrc file contains a login password,the file's permissions must be set to 600 (read andwrite by owner only). The system detected that the$HOME/.netrc file was not set to 600.

System actionThe system asks the user to enter the user ID andpassword.

Symbolic Feedback CodeEDC6RI

EDC7027I Remove password or correct$HOME/.netrc mode.

ExplanationThis message follows EDC7026 and advises the userhow to correct the problem with the $HOME/.netrc file.

System actionThe system asks the user to enter a user ID andpassword.

Symbolic Feedback CodeEDC6RJ

EDC7028I Unknown $HOME/.netrc option.

ExplanationThe system has successfully examined the$HOME/.netrc file for the user ID. However, the restof the $HOME/.netrc file is in a syntax that the systemcannot understand.

System actionThe system stops trying to find the password in the$HOME/.netrc file. The user must then enter it instead.

Symbolic Feedback CodeEDC6RK

EDC7100E errval : error unknown

ExplanationAn unrecognized XTI error value was passed to t_erroror t_strerror.

System actionPass a valid XTI error value to the function.


EDC7101I incorrect addr format


ExplanationA transport address was passed to an XTI functionwhich had an invalid format.

System actionThe function fails. A correct address should be passedto the function.


EDC7102I incorrect option format

ExplanationAn option buffer was passed to an XTI function whichhad inconsistent length indication or contained aninvalid option value.

System actionThe function fails. An option buffer with valid formatshould be passed to the function.


EDC7103I incorrect permissions

ExplanationAn XTI caller tried to change a transport option forwhich they lacked privilege.

System actionThe function fails. The caller should not attempt tochange the option while operating without adequateprivilege.


EDC7104I illegal transport fd

ExplanationThe descriptor did not refer to a valid XTI transportendpoint.

System actionThe function fails. Pass a descriptor referring to a validtransport endpoint.


EDC7105I couldn't allocate addr

ExplanationThe XTI transport provider couldn't allocate atransport address.

System actionThe function fails. Reattempt when addresses areavailable.


EDC7106I out of state

ExplanationA transport endpoint was not in a valid state for thefunction to be performed.

System actionThe function fails. Manipulate the endpoint to bring itinto the correct state before reattempting.


EDC7107I bad call sequence number

ExplanationAn invalid sequence number was specified in at_accept call.

System actionThe function fails. Specify a valid sequence number.


EDC7108I system error

ExplanationA system error occurred during the execution of an XTIfunction.


System actionThe function fails. Correct the underlying problem.


EDC7109I event requires attention

ExplanationAn event on an XTI endpoint requires attention.

System actionThe function fails. Call t_look to process the event.


EDC7110I illegal amount of data

ExplanationAn invalid amount of user data was passed to an XTIfunction.

System actionThe function fails. Correct the amount of data passed.


EDC7111I buffer not large enough

ExplanationThe buffer provided to return a value from an XTIfunction was not large enough.

System actionThe function fails. Pass a larger return buffer.


EDC7112I flow control

ExplanationO_NONBLOCK was set in a call to an XTI function tosend data, but the transport flow control mechanismprevented the transport provider from accepting anydata at this time.

System actionThe function fails. Call the function again when theflow control condition no longer exists.


EDC7113I no data

ExplanationAn XTI function to accept a connection or receive datawas called with O_NONBLOCK set on the endpoint,and no connection/data was pending.

System actionThe function fails. Retry.


EDC7114I discon_ind not found on queue

ExplanationNo disconnect indication was found on the specifiedXTI endpoint.



EDC7115I unitdata error not found

ExplanationNo unitdata error was found on the specified XTIendpoint.



EDC7116I bad flags

ExplanationAn invalid flags value was passed to t_optmgmt.


System actionThe function fails. Retry with a valid flags value.


EDC7117I no ord rel found on queue

ExplanationNo orderly release indication was found on thespecified XTI endpoint.



EDC7118I primitive/action not supported

ExplanationAn operation unsupported by the underlying transportprovider was requested.



EDC7119I state is in process of changing

ExplanationAn operation was requested on an XTI endpoint whosestate was in the process of changing.



EDC7120I unsupported struct-typerequested

ExplanationAllocation of an unsupported XTI structure type wasrequested from t_alloc.

System actionThe function fails. Pass a correct structure type.


EDC7121I invalid transport provider name

ExplanationAn invalid transport provider name was specified whenattempting to open an XTI endpoint.

System actionThe function fails. Specify a valid transport provider.


EDC7122I qlen is zero

ExplanationAn attempt was made to listen on an XTI endpointwhose connection queue length is zero.

System actionThe function fails. Specify an endpoint with a non-zeroqueue length.


EDC7123I address in use

ExplanationAn attempt was made to bind to a transport addresswhich is already in use.

System actionThe function fails. Specify an address which isavailable.


EDC7124I outstanding connectionindications


ExplanationThe XTI endpoint specified for both fd and resfd in acall to t_accept has outstanding connect requests.

System actionThe function fails. Specify an endpoint with nooutstanding connect requests.


EDC7125I transport provider mismatch

ExplanationThe listening and responding endpoints in a t_acceptcall do not refer to the same transport provider.

System actionThe function fails. Specify two endpoints which bothrefer to the same transport provider.


EDC7126I resfd specified to accept w/qlen>0

ExplanationThe XTI endpoint specified as resfd to t_accept is apassive endpoint.

System actionThe function fails. Specify an endpoint with zero queuelength.


EDC7127I resfd not bound to same addr as fd

ExplanationThe responding endpoint in a call to t_accept is notbound to the same address as the listening endpoint.

System actionThe function fails. Specify two endpoints both boundto the same address.


EDC7128I incoming connection queue full

ExplanationThe connection queue of the endpoint specified in acall to t_listen is full.

System actionThe function fails. Accept pending connections on theendpoint and retry.


EDC7129I XTI protocol error

ExplanationA communication problem has been detected betweenXTI and the transport provider to which an endpointrefers.

System actionThe function fails. Refer to diagnostic procedures forthe transport provider.


EDC8000I A bad socket-call constant wasfound in the IUCV header.

ExplanationA problem has occurred between MVS or VM andTCP/IP.


Programmer responseRecord this error and report the failure using your localprocedure to report failures to the IBM Service supportcontact.

Symbolic Feedback CodeEDC7Q0


EDC8001I An error was found in the IUCVheader.

ExplanationAn error was found in the IUCV header, such as a badlength.




EDC8002I A socket descriptor is out of range.

ExplanationA socket number assigned by client interface code (forsocket() and accept()) is out of range.




EDC8003I A socket descriptor is in use.

ExplanationA socket number assigned by client interface code isalready in use.




EDC8004I Request failed because of an IUCVerror.

ExplanationThe request failed because of IUCV error. This error isgenerated by the client stub code.




EDC8005I Offload box error.

ExplanationA problem has occurred between MVS and TCP/IP.




EDC8006I Offload box restarted.






EDC8007I Offload box down.





EDC8008I Already a conflicting calloutstanding on socket.





EDC8009I Request cancelled using aSOCKcallCANCEL request.





EDC8011I A name of a PFS was specifiedthat either is not configured or isnot a Sockets PFS.




Symbolic Feedback CodeEDC7QB

EDC8100I Block device required.

ExplanationA non-block file was specified when a block device isrequired.


Programmer responseProceed with cleanup of the application resources,and then close the socket. When the socket has beenfreed, the application may begin the process again.


EDC8101I Text file busy.


ExplanationAn attempt is made to run a pure-procedure programthat is currently open for writing or reading. It alsooccurs when an attempt is made to open for writing, orto remove, a pure-procedure program or shared librarywhile that program or library is being run.


Programmer responseProceed with cleanup of the application resources;then close the socket. When the socket has beenfreed, the application may begin the process again.


EDC8102I Operation would block.

ExplanationAn operation on a socket marked as non-blocking hasencountered a situation, such as no data available,that otherwise would have caused the function tosuspend execution.




EDC8103I Operation now in progress.

ExplanationThe socket was marked O_NDELAY or O_NONBLOCKusing fcntl(), and the connection cannot beimmediately established.




EDC8104I Connection already in progress.

ExplanationA connection or disconnection request is already inprogress for the specified socket.




EDC8105I Socket operation on non-socket.

ExplanationThe file descriptor does not refer to a socket.


Programmer responseReport the failure to your local administrator for theTCP/IP function. Try the application again when theproblem has been corrected.


EDC8106I Destination address required.

ExplanationThe socket operation failed because a destinationaddress was not provided. No bind address wasestablished.





EDC8107I Message too long.

ExplanationThe socket data transfer failed because the messageexceeded the size limits. A message sent on atransport provider was longer than an internalmessage buffer or some other network limit.




EDC8108I Protocol wrong type for socket.

ExplanationEither the two sockets to be connected are not of thesame type, or the protocol used does not support thistype of socket.




EDC8109I Protocol not available.

ExplanationThe protocol option specified to setsockopt() is notsupported by this implementation.




EDC8110I Protocol not supported.

ExplanationThis protocol is not supported by the address family, orthe protocol is not supported by this implementation.




EDC8111I Socket type not supported.

ExplanationThe type of socket specified is not supported. Do notuse this type of socket in your program.





EDC8112I Operation not supported onsocket.

ExplanationThis socket, with its particular type, domain, andprotocol, does not allow the requested operation.



Symbolic Feedback CodeEDC7TG

EDC8113I Protocol family not supported.

ExplanationThe socket protocol specified is not supported. Do notuse this protocol in your program.



Symbolic Feedback CodeEDC7TH

EDC8114I Address family not supported.

ExplanationThis implementation does not support the specifiedaddress family, or the specified address is not valid forthe address family of the specified socket.



Symbolic Feedback CodeEDC7TI

EDC8115I Address already in use.

ExplanationA bind or connect operation was attempted using asocket name that is already in use.


Programmer responseReport the failure to your local administrator for theTCP/IP function. Try the application again when theproblem has been corrected

Symbolic Feedback CodeEDC7TJ

EDC8116I Address not available.

ExplanationThe requested socket address is not available to thismachine. Either an incorrect socket address was used,or there is a problem at the remote node where thesocket address should be.



Symbolic Feedback CodeEDC7TK

EDC8117I Network is down.


ExplanationA socket operation failed because the network is notavailable. The local interface to use or reach thedestination is not available.


Programmer responseProceed with cleanup of the application resources andthen close the socket. When the socket has beenfreed, the application may begin the process again.

Symbolic Feedback CodeEDC7TL

EDC8118I Network is unreachable.

ExplanationA socket operation failed because the destination isat a remote node that cannot be reached over thenetwork. No route to the network exists.



Symbolic Feedback CodeEDC7TM

EDC8119I Network dropped connection onreset.

ExplanationThe host to which the socket was connected wentdown. The connection can be reestablished after theremote node is restarted.



Symbolic Feedback CodeEDC7TN

EDC8120I Connection ended abnormally.

ExplanationThe connection between a socket and a remote nodewas terminated at the local node, the remote node, orthe network level.



Symbolic Feedback CodeEDC7TO

EDC8121I Connection reset.

ExplanationThe connection was forcibly closed by the peer. Thiserrno can be set because of an error, or because of aconnection that was closed.


Programmer responseProceed with cleanup of the application resources andthen close the socket. When the socket has beenfreed, the application may begin the process again.

Symbolic Feedback CodeEDC7TP

EDC8122I No buffer space available.

ExplanationNot enough buffer space is available in the system toperform the requested socket operation.




Symbolic Feedback CodeEDC7TQ

EDC8123I Socket already connected.

ExplanationA connect operation was attempted on a socket that isalready connected.



Symbolic Feedback CodeEDC7TR

EDC8124I Socket not connected.

ExplanationA socket operation, other than a connect, wasattempted on a socket that is not currently connected,or a send operation that does not require a connectionwas attempted without a destination address.



Symbolic Feedback CodeEDC7TS

EDC8125I Can't send after socket shutdown.

ExplanationAn attempt was made to send data after a socket wasshut down.



Symbolic Feedback CodeEDC7TT

EDC8126I Too many references; can't splice.

ExplanationToo many references have been specified.



Symbolic Feedback CodeEDC7TU

EDC8127I Connection timed out.

ExplanationA remote socket did not respond within the timeoutperiod set by the protocol of the socket on thisnode. If the connection timed out during execution ofthe function that reported this error (as opposed totiming out before the function being called), results areunpredictable.




Symbolic Feedback CodeEDC7TV

EDC8128I Connection refused.

ExplanationA remote node refused to allow the attempted connectoperation. The attempt to connect to a socket wasrefused because there was no process listening,or because the queue of connection requests wasfull and the underlying protocol does not supportretransmissions.




EDC8129I Host is not available.

ExplanationA socket operation failed because the remote nodespecified is not available.




EDC8130I Host cannot be reached.

ExplanationA socket operation failed because no route to theremote node was available because of an incorrectaddress, an incorrect routing table, or networkhardware problems.




EDC8131I Too many processes.

ExplanationThe system process limit has been exceeded.




EDC8132I Too many users.

ExplanationThe maximum number of users has been reached.




EDC8133I Disk quota exceeded.


ExplanationA write to an ordinary file, the creation of a directory orsymbolic link, or the creation of a directory entry failedbecause the user's quota of disk blocks is exhausted.




EDC8134I Stale file handle.

ExplanationThe current directory, the root directory, or a filedescriptor to a file refers to a file that is no longeraccessible. This error may be caused by the local orremote file system being unmounted, or by a remotefile server disabling currently open file handles forimplementation-defined reasons.


Programmer responseReport the failure to your local administrator. Trythe application again when the problem has beencorrected.


EDC8136I File is not a STREAM.

ExplanationA STREAM operation was attempted on a filedescriptor which was not associated with a STREAM.


Programmer responseReport the failure to your local administrator.


EDC8137I STREAMS ioctl() timeout.

ExplanationThe timer set for a STREAMS ioctl() call hasexpired. The cause of this error is device-specificand indicates either a hardware or software failure,or a timeout value that is too short for the specificoperation. The status of the ioctl() operation isunpredictable.




EDC8138I No STREAMS resources.

ExplanationInsufficient STREAMS memory resources are availableto perform a STREAMS-related function. This is atemporary condition; recovery is possible if otherprocesses release resources.



Symbolic Feedback CodeEDC7UA

EDC8139I The message identified by set_idand msg_id is not in the messagecatalog.

ExplanationThis message is equivalent to the ENOMSG errno.




Symbolic Feedback CodeEDC7UB

EDC8140I Bad message.

ExplanationDuring a read(), getmsg(), or ioctl() I_RECVFDrequest to a STREAMS device, a message arrived atthe head of the STREAMS that is inappropriate for thefunction receiving the message:

• read() — The message waiting to be read on aSTREAMS is not a data message.

• getmsg() — A file descriptor was received insteadof a control message.

• ioctl() — Control or data information was receivedinstead of a file descriptor when I_RECVFD wasspecified.



Symbolic Feedback CodeEDC7UC

EDC8141I Identifier removed.

ExplanationReturned during interprocess communication if anidentifier has been removed from the system.



Symbolic Feedback CodeEDC7UD

EDC8144I The link has been severed.

ExplanationThis error may be reported by a function that refersto a remote file, when the communications link tothe server for that resource has been lost, any filedescriptor associated with this remote file should notbe used for future I/O.



Symbolic Feedback CodeEDC7UG

EDC8148I Protocol error.

ExplanationA protocol error occurred. This error is device-specific,but is usually not caused by a hardware failure.



Symbolic Feedback CodeEDC7UK

EDC8149I Multihop not allowed.


ExplanationFor a function that has a pathname as oneof its arguments, resolution of that pathnamerequires multihop access to a remote resource, andmultihop access is not supported by the underlyingimplementation.



Symbolic Feedback CodeEDC7UL

EDC8152I The asynchronous I/O request hasbeen canceled.

ExplanationAn asynchronous operation was in blocking state andhas been canceled with aio_cancel().

System actionThe asynchronous I/O request fails with ECANCELED.

Programmer responseAvoid using aio_cancel() to allow operations to wait orcomplete.

EDC8159I Function call was interruptedbefore any data was received.

ExplanationAn asynchronous signal was caught by the (POSIX)process during the execution of an interruptiblefunction, and the signal handler (or default action)resulted in a normal return. This caused theinterrupted function to return this errno. The signalarrived after the socket connection was establishedbut before any data was received over the connection.

System actionThe request fails and no data is returned. The socketconnection is established. The application continues torun.

Programmer responseSee z/OS XL C/C++ Runtime Library Reference forinformation about possible side effects of interruptingthe function.

Symbolic Feedback CodeEDC7UV

EDC8160I Socket reuse is not supported.

ExplanationAn attempt was made to reuse the specified socket forthis function. Reuse of this socket by this function isnot allowed.

System actionThe socket is not reused. Refer to the z/OS XL C/C++ Runtime Library Reference for more information onhow each function reacts to this error. The applicationcontinues to run.

Programmer responseSee z/OS XL C/C++ Runtime Library Reference for thefunction being attempted for the specific reason forfailure, and for any side effects from the function.


EDC8161I The file system cannot currentlybe moved.

ExplanationThe function call is attempting to move a file systemwhich currently cannot be moved. This occurs in a USSsysplex environment. One reason is that an applicationhas issued byte range locks for one or more files in thefile system. The move cannot succeed until the filesare closed and/or the byte range locks are released.

System actionThe file system is not moved.

Programmer responseEnsure the program has no byte range locksoutstanding. It may also be necessary to close anyopen files which had byte range locks. If that doesnot help, ask the system programmer to use the FBPXOINIT,FILESYS…, console command to determinethe state of the file system and to perform file system


diagnosis. All applications which hold byte range locksmay also need to be determined.

EDC9500I An unknown error occurred.

ExplanationFunction getaddrinfo() or getnameinfo() failed.The reason is unknown.

System actionThe gai_strerror() function returns this messagewhen it is given an error code that is not oneof the documented return values from either thegetaddrinfo() or getnameinfo() function.

Programmer responseReport the problem to your system administrator.

EDC9501I The name does not resolve for thesupplied parameters.

ExplanationFunction getaddrinfo() or getnameinfo() failed.For getnameinfo(), flag NI_NAMEREQD is set andthe host's name cannot be located, or both node andservice names were null. For getaddrinfo(), bothnodename and servname were null.

System actionThe getaddrinfo() or getnameinfo() function fails. Thevalue EAI_NONAME is returned.

Programmer responseFor getaddrinfo(), correct the function call tosupply either or both the nodename and servnameparameters. For getnameinfo(), either the node orservice name supplied cannot be located and shouldbe verified for a correct name.

EDC9502I The name or address could notbe resolved at this time. Futureattempts may succeed.

ExplanationFunction getaddrinfo() or getnameinfo() failed.The host address specified for getnameinfo() or thehost name specified for getaddrinfo() could not beresolved in the configured time interval or the systemresolver address space has not been started.

System actionThe getaddrinfo() or getnameinfo() function fails. Thevalue EAI_AGAIN is returned.

Programmer responseRetry your request at a later time.

EDC9503I A non-recoverable error occurredwhen attempting to resolve thename or address.

ExplanationFunction getaddrinfo() or getnameinfo() failed.The host address specified for getnameinfo() or thehost name specified for getaddrinfo() could not beresolved.

System actionThe getaddrinfo() or getnameinfo() function fails. Thevalue EAI_FAIL is returned.


EDC9504I An argument buffer overflowed.

ExplanationFunction getnameinfo() failed. The buffer pointed to bythe node or service argument for getnameinfo() wastoo small.

System actionThe getnameinfo() function fails. The valueEAI_OVERFLOW is returned.

Programmer responseCorrect the size of the argument buffer.

EDC9505I The address family was notrecognized or the address lengthwas invalid for the specifiedfamily.

ExplanationFunction getaddrinfo() or getnameinfo() failed.The address family information was incorrect.

System actionThe getaddrinfo() or getnameinfo() function fails. Thevalue EAI_FAMILY is returned.


Programmer responseConsult the z/OS XL C/C++ Runtime Library Referencefor the valid address families allowed and correct theapplication to use a supported address family and itscorrect length.

EDC9506I There was a memory allocationfailure.

ExplanationFunction getaddrinfo() or getnameinfo() failed.The service was unable to obtain the memorynecessary to build the return information.

System actionThe getaddrinfo() or getnameinfo() functionfails. The value EAI_MEMORY is returned.


EDC9507I The flags parameter had an invalidvalue.

ExplanationFunction getaddrinfo() or getnameinfo() failed.For the getaddrinfo() function, the ai_flagsmember of the hints structure specified an invalidcombination of flags. For the getnameinfo()function, the flags parameter specified an invalidcombination of flags.

System actionThe getaddrinfo() or getnameinfo() functionfails. The value EAI_BADFLAGS is returned.

Programmer responseConsult the z/OS XL C/C++ Runtime Library Referencefor the valid flags allowed and correct the applicationto use a proper combination of flags.

EDC9508I The service passed was notrecognized for the specified sockettype.

ExplanationFunction getaddrinfo() failed. The servnameparameter specified on getaddrinfo() does notsupport ai_socktype member specified in the hintsparameter.

System actionThe getaddrinfo() function fails. The valueEAI_SERVICE is returned.

Programmer responseCorrect the servname parameter or the ai_socktypevalue. If these are correct, then contact your systemadministrator.

EDC9509I The intended socket type was notrecognized.

ExplanationFunction getaddrinfo() fails. The getaddrinfo()function does not support the socket type specified inthe ai_socktype member of the hints parameter.

System actionThe getaddrinfo() function fails. The valueEAI_SOCKTYPE is returned.

Programmer responseCorrect the ai_socktype value. If it is correct, thencontact your system administrator.

EDC9510I A system error occurred. The errorcode can be found in errno.

ExplanationFunction getaddrinfo() or getnameinfo() failed.The request failed because of a system error.

System actionThe getaddrinfo() or getnameinfo() functionfails. The value EAI_SYSTEM is returned.

Programmer responseRetrieve the errno value and use the information itsupplies to correct the problem.

EDC9511I The extended flags parameter hadan invalid value.

ExplanationFunction getaddrinfo() failed. The ai_eflags memberof the hints structure specified a combination of flagsthat is not valid.


System actionThe getaddrinfo() function fails. The valueEAI_BADEXTFLAGS is returned.

Programmer responseRefer to z/OS XL C/C++ Runtime Library Reference forthe valid flags allowed and correct the application touse a proper combination of flags.


Chapter 5. Fortran runtime messages

This topic shows the ranges of Fortran message numbers by message type, and explains qualifying data,permissible resume actions, and locator-text in the Fortran messages. Finally, the list of the Fortranmessages is given.

Fortran runtime message number rangesComponent or Language Element Range of Message Numbers

(Reserved) 0000–0099

Service Subroutines 0100–0299

Common Blocks 0300–0339

Operator Messages 0340–0344


Run-time Environment 0401–0499

Implicit Routines 0500–0599

Intrinsic Functions 0600–0699


I/O 1000–1999

Input Conversion 1000–1019

Sequential I/O 1020–1069

Direct I/O 1070–1099

Keyed I/O 1100–1179

Formatted I/O 1180–1199

Unformatted I/O 1200–1209

List Directed I/O 1210–1219

Namelist I/O 1220–1249

Striped I/O 1250–1269

Asynchronous I/O 1270–1329

VSAM I/O 1330–1339

INQUIRE 1340–1359

CLOSE semantics 1360–1379

OPEN / DEFINE FILE semantics 1380–1449


System-detected errors 1500–1549

Command / Macro / Service failure 1550–1599

File Disconnection 1900–1909

End of Data 1910–1914

Invalid unit 1915–1919

Miscellaneous 1920–1999

Multitasking Facility (MTF) 2000–2099

AUTOTASK 2000–2029

AUTOTASK DD Statement 2030–2039

Function invalid 2040–2049


Component or Language Element Range of Message Numbers


Vector 2100–2119

Run-Time Options 2120–2129


Separation Tool 2200–2249

Static Debug 2250–2279



Qualifying dataMany of the messages listed have a section called Qualifying Data, which describes qualifying data(q_data) associated with the condition. Qualifying data (or q_data) consists of variables that containinformation about the occurrence of a particular condition, such as the input values to the service thatdetected the condition. This information is useful for a condition handler to determine what correctiveactions to take.

Many of the conditions have q_data descriptors (indicated by data type Q_DATA_DESC) as part of theirqualifying data. A q_data descriptor indicates the data type and length of the immediately followingelement of qualifying data.

The first qualifying data for any condition is parm-count, the total number of elements of qualifying dataincluding parm-count itself, associated with that condition token.

For I/O errors, the first four qualifying data are defined as shown in Table 1 on page 272.

Table 1. Basic Set of Qualifying Data for I/O Conditions

No. Name Input/ Output Type Value

1 parm-count Input INTEGER*4 The total number of elements of qualifying data includingthis one. If there is no additional qualifying data beyondthe basic set shown here, then this value is 4. Otherwise,it includes the first four shown here plus whateveradditional qualifying data is applicable to the condition.

2 statement Input CHARACTER*12 The name of the I/O statement being processed.

3 unit Input INTEGER*4 -1, if the I/O statement is directed to an internalfile. Otherwise, the unit number specified on the I/Ostatement.

4 file Input CHARACTER*62 Blank, if the I/O statement refers to an internal file orif the name of the file is not provided as part of themessage text for this condition.

Otherwise, a structure that gives the name of theexternal file to which the I/O statement refers (see Table2 on page 272).

When the file qualifying data is not blank, it gives the file name of the file involved in the I/O statement,and has the following format:

Table 2. Structure of file qualifying data that is not blank

Position Length Contents

1 8 The ddname for the file.

9 1 A code that indicates if the file is identified in the Fortran program by its ddname or by its dataset name. A value of blank indicates that the file is referred to through its ddname. Any non-blankcharacter indicates that it is referred to by its data set name (see Table 3 on page 273).

For z/OS, position 9 of the file qualifying data has the following structure when it does not contain blanks.


Table 3. Structure of the code that references files by ddname

Position Length Contents

9 44 Data set name

53 8 PDS member name (or blank if not a PDS)

61 2 Not used

For more information on qualifying data, see z/OS Language Environment Programming Guide.

Permissible resume actionsMany of the messages listed have a section called Permissible Resume Actions describing which resumeactions a user condition handler can request when the resume cursor has not been moved.

Table 4 on page 273 shows the names (that is, the two-character codes) of the resume actions. It alsocontains a description of the values that the user condition handler must set for the indicated parametersto request that resume action. (result_code and new_condition are defined in z/OS Language EnvironmentProgramming Guide.)

Table 4. Names of resume actions

Name Corresponding Resume Action result_code Parameter new_condition Parameter

RN Resume without moving the resume cursor 10 —

RI Resume with new input value 60 CEE0CE

RO Resume with new output value 60 CEE0CF

If a user condition handler requests a resume action that is not listed as one of the permissible resumeactions for the condition being processed, either the condition CEE088 (invalid request for the resumeaction) or the condition CEE087 (invalid request for the fix-up and resume action) is signaled. If a usercondition handler attempts to resume without moving the resume cursor for the condition CEE088 orCEE087, the condition is percolated to the next condition handler to avoid a program loop.

Regardless of what is listed for a message under Permissible Resume Actions, you can always move theresume cursor by invoking the callable service CEEMRCE and then requesting the resume action. In thiscase, the only actions that are taken are those described under System Action; none of those listed underPermissible Resume Actions is taken.

Name Resume Action result_code Parameter new_condition Parameter

— Resume after moving the resume cursor 10 —

locator-text in the runtime message textsIn many message texts for conditions involving I/O statements, locator-text is shown as part of themessage text. This locator-text identifies the Fortran statement for which the error was detected and canbe one of the following:

• The statement statement for unit unit-number, which was connected to file-name, failed.• The statement statement for an internal file failed.• An error occurred during enclave termination.• The statement statement for unit unit-number failed.• The INQUIRE statement failed.

Chapter 5. Fortran runtime messages 273

List of runtime messagesThe messages listed pertain to Fortran. Messages are followed by an explanation describing the conditionthat caused the message (except for those messages for which the message text is self-explanatory), aprogrammer response suggesting how you might prevent the message from occurring again, and a systemaction indicating how the system responds to the condition that caused the message.


Some messages also contain qualifying data and permissible resume actions, as discussed in “Qualifyingdata” on page 272, and “Permissible resume actions” on page 273, respectively. The VS FORTRANVersion 2 error number is shown for those messages that existed in VS FORTRAN Version 2.

These messages also contain alphabetic suffixes that have the following meaning:I


Warning messageE

Error messageS



FOR0096W The symbol table in storage wascorrupted and couldn't be used toproduce a dump.

ExplanationDuring the printing of a dump, a Language Environmentroutine detected an inconsistency in a symbol table,which contains information about the type andlocation of the variables in a Fortran program unit.Most likely the symbol table in virtual storage wasoverlaid by some routine (but not necessarily by theroutine with the overlaid symbol table).

System actionThe dump or the remainder of the dump for thisprogram unit is not created.

Programmer responseDetermine and correct the cause of the overlaidsymbol table. In Fortran program units, this is oftencaused by:

• Using subscripts that reference virtual storageoutside the declared bounds of an array.

• Referring to variables that are in EQUIVALENCEstatements when the variables are declared tooverlay too much storage.

• Referring to storage that's addressed through apointer whose value isn't properly established.

• In a CALL statement or function reference, providingactual arguments that are not consistent with thedummy arguments declared in the subprogram. Theactual arguments could be of the wrong type, rank,or have the wrong array bounds. There could be anincorrect number of actual arguments.

Symbolic Feedback CodeFOR0096

FOR0100S The DIV callable service service-name for the dynamic commonblock common-name failed. Amacro-name macro instructionhad a system completion (abend)code of abend-code, and areason code of reason-code. Seekassistance from your LanguageEnvironment support personnel.VS FORTRAN Version Error 2Number: AFB143I-1

ExplanationThe DIV callable service service-name failed becausethe macro instruction macro-name, which was usedinternally by Language Environment, failed. The


system completion (abend) codes and reason codesare described in z/OS MVS Programming: AssemblerServices Reference ABE-HSP.

System actionThe condition is signaled. If the condition isunhandled, the application is terminated.

Qualifying Data: None

Permissible Resume Actions:

Name Action Taken after Resumption

RN The service is not completed, a return code of 128 is set,and execution resumes.

Programmer responseRefer to the one of the publications listed under“Explanation” for the cause of the error. You mightrequire the assistance of your Language Environmentsupport personnel to resolve many of these errors.


FOR0101S The DIV callable service service-name failed for the dynamiccommon block common-name. Amacro-name macro instruction hada return code of return-code, and areason code of reason-code. Seekassistance from your LanguageEnvironment support personnel.VS FORTRAN Version Error 2Number: AFB143I-2

ExplanationThe DIV callable service service-name failed becausethe macro instruction macro-name, which was usedinternally by Language Environment, failed. The returncodes and reason codes are described in z/OS MVSProgramming: Assembler Services Reference ABE-HSP.






Programmer responseRefer to the one of the publications listed under“Explanation” for the cause of the error. You mightrequire the assistance of your Language Environmentsupport personnel to resolve many of these errors.


FOR0102S The DIV callable service service-name failed. The return code wasreturn-code. VS FORTRAN VersionError 2 Number: AFB144I-1,AFB144I-2

ExplanationThe DIV callable service service-name failed becauseof one of the errors in the table, which is identifiedby the return code return-code. The argumentsmentioned in the explanations are those described forthe DIV callable services in VS FORTRAN Version 2Language and Library Reference.

Return

Code

Explanation

8 The value of the dyncom argument wasn't the name of adynamic common block.

12 The value of the type argument was neither DDNAME,DSNAME, nor DSN.

16 If the value of the type argument was DSNAME or DSN,the value of the access argument was neither READnor READWRITE. If the value of the type argument wasDDNAME, the value of the access argument was neitherREAD, READWRITE, nor blank.

20 The value of the access argument was READ, but the dataobject was empty.

24 The object specified by the divobj argument was alreadyassociated with a dynamic common block or an object IDthrough a different ddname.

28 The ddname or data set name given as the divobjargument did not refer to a VSAM linear data set.

32 The value supplied for divobj argument was not a validddname or data set name (as determined by the value ofthe type argument).

36 The value of the divobj argument conflicted with the valueof the type argument. For example, this return code couldindicate that the type argument had a value of DDNAME,and the divobj had a value that could only be a data setname rather than a ddname.

40 The data set that had the name given as the value of thedivobj argument and that should have been a VSAM lineardata set could not be dynamically allocated, possiblybecause it didn't exist.


Return

Code

Explanation

44 The dynamic common block whose name was given asthe value of the dyncom argument was already associatedwith another data object through a the use of the DIVINFor DIVVWV callable service.

48 The argument list passed to the DIV callable service wasinvalid for one or more of these reasons:

• Call was made from a program compiled by the VSFORTRAN Version 1 or the VS FORTRAN Version 2compiler with the the LANGLVL(66) compiler option.

• Call was made from a program compiled by the VSFORTRAN Version 1 compiler at a level before Release3.

• Call was made from a program compiled by theFORTRAN IV H Extended or the FORTRAN IV G1compiler.

• Incorrect number of arguments was provided.• One or more of the arguments wasn't of the type

required by the callable service.• Call was made from an assembler language program,

and the arguments were not provided in the formrequired when there are character arguments.

52 The value of the mapnum argument implied a range inthe data object that overlaps a range that was alreadymapped.

56 The value of the obj-id argument did not have anassociation with any data object.

60 The value of the offset argument was negative.

64 The dynamic common block whose name was given as thevalue of the dyncom argument was not associated withany data object.

68 The DIVSAV callable service was invoked, but the dataobject associated with the dynamic common whose namewas given as the value of the dyncom argument was notaccessed using a value of READWRITE for the accessargument.

72 The value of the mapnum argument was zero or negative.

76 The DIV callable service was called from within an MTFparallel subroutine.

System actionThe service is not completed, and the condition issignaled. If the condition is unhandled, the applicationis terminated.

Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 3

2 subroutine- name

Input CHARACTER*8 Name of the DIVsubroutine

No.

Name Input/Output

Data Type andLength

Value

3 return-code

Input INTEGER*4 Return code fromthe Fortran DIVsubroutine.



RN The service is not completed, a return code of return codeis set, and execution resumes.

Programmer responseBased on the return code identified by return-code,take the action indicated. The arguments mentionedare those described for the DIV callable services in VSFORTRAN Version 2 Language and Library Reference.

Return

Code

Explanation

8 Specify the name of the common block as one of thesuboptions of the DC compiler option.

12 Change the value of the type argument to DDNAME,DSNAME, or DSN depending on whether a ddname or adata set name is given as the value of the divobj argument.(Lowercase characters are allowed.)

16 Change the value of the access argument to READ orREADWRITE. (Lowercase characters are allowed.)

20 Ensure that name given as the divobj argument refersto the data object (VSAM linear data set) that wasintended, or change the value of the access argument toREADWRITE.

24 Remove this call to the DIVINF or DIVINV callable serviceif an existing association can be used. Alternatively,terminate the existing association using the DIVTRF orDIVTRV callable service before calling DIVINF or DIVINV.

28 Ensure that the ddname or the data set name given as thedivobj argument refers to a VSAM linear data set.

32 Ensure that the value of the divobj argument is a validddname or a data set name that refers to a VSAM lineardata set. Also ensure that it is correctly specified as eithera ddname or a data set name in the type argument.

36 If the type argument has a value of DDNAME, then ensurethat a ddname referring to a VSAM linear data set is givenas the value of the divobj argument. If the type has a valueof DSNAME or DSN, then ensure that a data set name ofa VSAM linear data set is given as the value of the divobjargument. Change either or both of these arguments tomake them consistent.

40 Ensure that the data set name refers to a VSAM linear dataset, which can be created using Access Method Services.


Return

Code

Explanation

44 Make one or more of these changes:

• Remove the call to the DIVINF or DIVVWV if an existingassociation can be used.

• Use a different dynamic common block name.• First terminate the existing association using the

DIVTRF or DIVTRV callable service.

48 If the calling program is written in Fortran, compile itwith the VS FORTRAN Version 2 compiler, and do notspecify the LANGLVL(66) compiler option. If it is writtenin assembler language, use the Fortran conventionsfor argument lists with character arguments. Theseconventions are described in the topic “Passing CharacterArguments Using the Standard Linkage Convention” inAppendix B of VS FORTRAN Version 2 Programming Guidefor CMS and MVS.

52 Use a different value for the mapnum argument to avoidoverlapping an existing mapping of the data object. Usethe DIVCML callable service if necessary to determine thelength of the dynamic common blocks so that overlappingmappings can be avoided.

56 Ensure that the value of the obj-id argument is the sameas what was returned by a previous call to the DIVINVcallable service. Also ensure that the previous call to theDIVINV callable service completely successfully. If it'spossible that a user-written condition handler requestedthat execution resume in the event of an error, thenprovide logic to handle the nonzero return code.

60 Provide a value for the offset argument that is not lessthan 0.

64 Ensure that the name given as the value of the dyncomargument has been associated with a data object usingthe DIVINF callable service. Also ensure that the previouscall to the DIVINF callable service completely successfullyby checking the return code if it's possible that a user-written condition handler requested that resumption ofexecution occur.

68 If the changes made in the dynamic common block are tobe saved in the data object, then ensure that the value ofthe access argument in the call to the DIVINF or DIVINVcallable service is READWRITE. If the changes are not tobe saved, then remove the call to the DIVSAV callableservice.

72 Provide a positive value for the mapnum argument. Alsosee the actions for return code 52.

76 Restructure the application so that there are no callsto the data-in-virtual callable service in MTF parallelsubroutines. However, these services can be used in themain task program, and the SHRCOM callable servicecan be used to allow sharing of the dynamic commonblocks among the main task program and the parallelsubroutines.


FOR0103W The DIV callable service service-name completed successfully,but the dynamic common block

common-name had a length oflength, which was not a multiple of4096.

System actionThe service is completed and execution resumes.


Permissable Resume Actions:


RN The service is not completed, a return code of 4 is set, andexecution resumes.

Programmer responseIf dynamic common block common-name will bemodified and the changes saved in the data objector if you want to avoid the signaling of this condition,change the declarations of the variables in common-name such that the length of this common blockbecomes an exact multiple of 4096 (4096, 8192,12288, and so on). Otherwise, you can ignore thiscondition.


FOR0104S The DIV callable service service-name failed. It was called withno argument list. VS FORTRANVersion Error 2 Number: AFB154I






Programmer responseProvide the arguments that are required for theservice-name callable service. The data-in-virtualcallable services are described in detail in VSFORTRAN Version 2 Language and Library Reference.



FOR0105S The DIV callable service service-name failed. It was called with anincorrect number of arguments. VSFORTRAN Version Error 2 Number:AFB154I





RN The service is ignored, a return code of 48 is set, andexecution resumes.



FOR0106S The DIV callable service service-name failed. It was called withan argument list in an incorrectformat. This probably occurredbecause a required characterargument was not provided. VSFORTRAN Version Error 2 Number:AFB154I

ExplanationThe argument list provided to the service-namecallable service wasn't in the internally-generatedform produced by the Fortran compiler when there arecharacter arguments. This could have occurred for oneor more of these reasons:

• The call was made from a program compiled by theVS FORTRAN Version 1 or the VS FORTRAN Version 2compiler with the the LANGLVL(66) compiler option.

• The call was made from a program compiled by theVS FORTRAN Version 1 compiler at a level beforeRelease 3.

• The call was made from a program compiled by theFORTRAN IV H Extended or the FORTRAN IV G1compiler.

• An incorrect number of arguments was provided.

• One or more of the arguments wasn't of the typerequired by the callable service.

• The call was made from an assembler languageprogram, and the arguments were not providedin the form required when there are characterarguments.





RN The service is ignored, a return code of 48 is set, andexecution resumes.


If the program is written in Fortran, compile it with theVS FORTRAN Version 2 compiler, and do not specifythe LANGLVL(66) compiler option. If it is writtenin assembler language, use the Fortran conventionsfor argument lists with character arguments. Theseconventions are described in the topic “PassingCharacter Arguments Using the Standard LinkageConvention” in Appendix B of VS FORTRAN Version 2Programming Guide for CMS and MVS.


FOR0120S The FILEINF callable servicefailed. It was called with anargument list in an incorrectformat. VS FORTRAN Version Error2 Number: AFB096I-1

ExplanationThe argument list provided in the call to the FILEINFcallable service was incorrect in one of these ways:

• There was no argument list.• The argument list had an even number of arguments.• The argument list wasn't in the internally-generated

form produced by the Fortran compiler when thereare character arguments. This could have occurredfor one or more of these reasons:


– One or more of the keyword arguments (CYL,RECFM, and so on) weren't provided as characterexpressions.

– The call was made from a program compiled bythe VS FORTRAN Version 1 or the VS FORTRANVersion 2 compiler with the the LANGLVL(66)compiler option.

– The call was made from a program compiled bythe VS FORTRAN Version 1 compiler at a levelbefore Release 3.

– The call was made from a program compiled bythe FORTRAN IV H Extended or the FORTRAN IVG1 compiler.

– The call was made from an assembler languageprogram, and the arguments were not providedin the form required when there are characterarguments.

System actionThe condition is signaled. If the condition isunhandled, the application is terminated. However,if the RN action listed under “Permissible ResumeActions” is taken to resume execution following thecall, then the file information provided is ignored,and error FOR1926 is detected during execution of asubsequent OPEN or INQUIRE statement. Detectionof error FOR1926 can be suppressed if, following thefailing call to the FILEINF callable service, another callis made either with no arguments or with argumentsthat don't cause another error to be detected.




RN The service is ignored, and execution resumes. Refer to“System Action” regarding the detection of error FOR1926following this resumption.

Programmer responseBe sure that the argument list contains an oddnumber of arguments and that the even-numberedarguments are character expressions whose values arethe permissible keyword arguments.


Refer to “System Action” regarding the detection oferror FOR1926 on a subsequent OPEN or CLOSEstatement.


FOR0121S The FILEINF callable servicefailed. The argument in positionposition of the argument list wasnot one of the character valuesthat the FILEINF callable serviceunderstands as an argument. VSFORTRAN Version Error 2 Number:AFB096I-2

ExplanationPosition position of the argument list for the FILEINFcallable service was not a character expression whosevalue was one of the permissible keyword arguments.These permissible keyword arguments are values suchas RECFM, CYL, and so on.






Programmer responseCorrect the argument list by coding the first argumentas an integer variable and the remaining pairsof arguments as one of the permissible keywordarguments followed by its value. The keywordarguments are listed in the description of the FILEINFcallable service in VS FORTRAN Version 2 Languageand Library Reference.

Be sure that each keyword argument is coded as acharacter expression. Remember that if a character


constant is used, the keyword argument, such asRECFM, must be enclosed in quotes or apostrophes.



FOR0122S The FILEINF callable servicefailed. An incorrect value wasprovided for the actual argumentimmediately following the actualargument with the value ofkeyword. VS FORTRAN VersionError 2 Number: AFB096I-3






Programmer responseChange the argument list by providing a value that'sallowed to follow and correspond to the keywordargument keyword. The permissible values are shownin the description of the FILEINF callable service in VSFORTRAN Version 2 Language and Library Reference.

If the value is of character type, such as FB, and it iscoded as a character constant, be sure to enclose thevalue in quotes or apostrophes.



FOR0123S The FILEINF callable servicefailed. VSAM record level sharing(RLS) was specified, but executionwas on a system without bothMVS/ESA SP Version 5 Release 2or later and DFSMS/MVS Version 1Release 3 or later.






Programmer responseEnsure that the Fortran application that connects aVSAM file using RLS mode is run on MVS/SP Version 5Release 2 or later and DFSMS/MVS Version 1 Release3 or later. If these levels aren't available, then youcan't use RLS mode. In this case, remove the RLSkeyword argument and its corresponding value fromthe argument list for the FILEINF callable service.



FOR0130S The ARGSTR callable servicefailed. It was called with anargument list in an incorrectformat.

ExplanationThe argument list provided in the call to the ARGSTRcallable service was incorrect in one of these ways:

• There was no argument list.


• The argument list had other than two arguments.• The argument list wasn't in the internally-generated

form produced by the Fortran compiler when thereare character arguments. This could have occurredbecause:

– The first argument was not of character type.– The call was made from a program compiled by

the VS FORTRAN Version 1 or the VS FORTRANVersion 2 compiler with the the LANGLVL(66)compiler option.




System actionThe service is ignored, and the condition is signaled.If the condition is unhandled, the application isterminated.




RN The service is ignored, and execution resumes.

Programmer responseBe sure that the argument list contains two arguments,the first of which is a character variable and thesecond of which is an integer variable of length 4.



FOR0300S One program unit specifiedcommon block common-name in aDC compiler option, but another

program unit did not specify itin a DC compiler option. VSFORTRAN Version Error 2 Number:AFB158I-2


Qualifying Data:

No. Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 commonname

Input CHARACTER*31 Name ofcommon block



RN common-name is not made available to one or moreprogram units and execution continues. The resultsof execution are unpredictable if data in the dynamiccommon block is subsequently referenced.

Programmer responseIf you want common-name to be a dynamic commonblock, compile all program units that refer to it usinga DC compiler option that has as a suboption eithercommon-name or an asterisk. If you want common-name to be a static common block, do not compileany program units that refer to it using a DC compileroption that has as a suboption either common-nameor an asterisk unless common-name is used as asuboption of the SC compiler option.


FOR0301S The common block common-nameof length length could notbe created because there wasinsufficient virtual storage. VSFORTRAN Version Error 2 Number:AFB156I


Qualifying Data:


No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 3

2 common-name

Input CHARACTER*31 Name of commonblock.

3 length Input/Output

INTEGER*4 Length of commonblock.



RN The service is not completed, a return code of return codeis set, and execution resumes.

RI An attempt is made to acquire virtual storage for thecommon block. common-name using the length providedin length. If this is successful, execution continues butthe results of execution are unpredictable if data in thedynamic common block beyond the length provided aslength is referenced.

Programmer responseRun your application in a larger region. You can changethe region size with the REGION parameter on theEXEC statement in your JCL.

If the application allows it, you could also recompileall program units that refer to common block common-name with declarations that result in a smaller lengthfor this or for other common blocks.

If there are allocatable arrays that are allocated butnot currently in use, then deallocate them to makemore storage available.

If one of your routines is running in 24-bit addressingmode, remember that dynamic common blocksacquired for it are created in virtual storage below16 Mb, where storage is limited. However, when theroutine is running in 31-bit addressing mode, dynamiccommon blocks acquired for it are created in virtualstorage above 16 Mb, where there is normally muchmore storage available. Therefore, if your applicationis running in 24-bit addressing mode and if it couldrun in 31-bit addressing mode instead, then makingthis change could alleviate this storage constraint. Butbefore link editing the application with the AMODE=31option, you should be sure that there aren't anyprogram units, such as those compiled with theFORTRAN IV H Extended compiler, that aren't capableof running in 31-bit addressing mode.


FOR0302S Common block common-name wasdefined with a length of length1,but it was defined with a length

of length2 in a program unitthat was invoked earlier. VSFORTRAN Version Error 2 Number:AFB158I-1


Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 4

2 common-name

Input CHARACTER*31 Name of commonblock

3 length-1 Input INTEGER*4 Length of commonblock, as definedin program unit 1.

4 length-2 Input INTEGER*4 Length of commonblock, as definedin program unit 2.



RN common-name is not made available to one or moreprogram units and execution continues. The resultsof execution are unpredictable if data in the dynamiccommon block is subsequently referenced.

Programmer responseIn all program units that refer to the common blockcommon-name ensure that the declarations of thecommon block are such that the length of the commonblock is the same.


FOR0303S The common block callableservice service-name failed. Itwas called with an argumentlist in an incorrect format. VSFORTRAN Version Error 2 Number:AFB920I-2, AFB157I-3

ExplanationThe argument list provided in the call to the service-name callable service was incorrect in one of theseways:

• There was no argument list.


• The argument list had the wrong number ofarguments.

• The argument list wasn't in the internally-generatedform produced by the Fortran compiler when thereare character arguments. This could have occurredfor one or more of these reasons:

– The common block name wasn't provided as acharacter expression.

– The call was made from a program compiled bythe VS FORTRAN Version 1 or the VS FORTRANVersion 2 compiler with the the LANGLVL(66)compiler option.




System actionThe service is ignored, and the condition is signaled.If the condition is unhandled, the application isterminated.

Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 service-name

Input CHARACTER*8 Name of commonblock callableservice that wascalled.




Programmer responseBe sure that the argument list contains the numberof arguments required by service-name and that theyare of the correct type. In particular, if the commonblock name is coded as a character constant, be sureto enclose the value in quotes or apostrophes.

If the program is written in Fortran, compile it with theVS FORTRAN Version 2 compiler, and do not specifythe LANGLVL(66) compiler option. If it is writtenin assembler language, use the Fortran conventions

for argument lists with character arguments. Theseconventions are described in the topic “PassingCharacter Arguments Using the Standard LinkageConvention” in Appendix B of VS FORTRAN Version 2Programming Guide for CMS and MVS.


FOR0304S The common block callableservice service-name failed. Thecommon block name had anincorrect format. The invalidname was 'common-name'. VSFORTRAN Version Error 2 Number:AFB157I-2

ExplanationThe name of the dynamic common block provided tothe service-name was not a valid name because iteither:

• Began with a blank or was all blank,• Was longer than 31 characters, or• Contained an imbedded blank


Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 3

2 service-name

Input CHARACTER*8 Name of commonblock callableservice that wascalled.

3 common-name

Input CHARACTER*31 Common blockname (or the first31 characters ofthe name) thatwas provided forservice-name.





Programmer responseBe sure the character expression for the dynamiccommon block name passed to service-name is a validFortran name. In particular, it must:

• Be left-adjusted with trailing blanks,• Begin with a letter, underscore ( _ ), or dollar sign

( $ ),• Contain only alphameric characters, that is, letters,

digits, underscores ( _ ), or dollar signs ( $ ),• Contain at least 1 but no more than 31 nonblank

characters, and• Have no imbedded blanks.

If the common block name is coded as a characterconstant, be sure to enclose the value in quotes orapostrophes.

If the program is written in Fortran, compile it with theVS FORTRAN Version 2 compiler, and do not specifythe LANGLVL(66) compiler option. If it is writtenin assembler language, use the Fortran conventionsfor argument lists with character arguments. Theseconventions are described in the section “PassingCharacter Arguments Using the Standard LinkageConvention” in Appendix B of VS FORTRAN Version 2Programming Guide for CMS and MVS.


FOR0310S The ALLOCATE statement couldnot be completed. Theobject object_name of lengthobject_length could not be createdbecause there was insufficientvirtual storage.

System actionIf the STAT specifier is not present on the ALLOCATEstatement, the condition is signaled. If the condition isunhandled, the application is terminated.

Qualifying Data:


Data Type andLength

Value

1 parm-count

Input INTEGER*4 3

2 object-name

Input CHARACTER*250 Name ofobject specifiedin ALLOCATEstatement.

3 object-length

Input INTEGER*4 Length ofobject specifiedin ALLOCATEstatement.



RN The current operation is ignored. The remainder of theallocation is processed and execution continues.

Programmer responseRun your application in a larger region. You can changethe region size with the REGION parameter on theEXEC statement in your JCL.

If the application allows it, you could also reduce thesize of the allocatable array so that it doesn't requireas much storage.

If there are other allocatable arrays that are allocatedbut not currently in use, then deallocate them to makemore storage available.

If there are common blocks or other large storageareas that could be reduced in size, then doing socould make more storage available.

If a routine is running in 24-bit addressing mode,remember that allocatable arrays acquired for itare created in virtual storage below 16 Mb, wherestorage is limited. However, when the routine isrunning in 31-bit addressing mode, allocatable arraysacquired for it are created in virtual storage above16 Mb, where there is normally much more storageavailable. Therefore, if your application is running in24-bit addressing mode and if it could run in 31-bitaddressing mode instead, then making this changecould alleviate this storage constraint. But before linkediting the application with the AMODE=31 option,you should be sure that there aren't any programunits, such as those compiled with the FORTRAN IVH Extended compiler, that aren't capable of running in31-bit addressing mode.


FOR0311S The ALLOCATE statement couldnot be completed. Theobject object_name was alreadyallocated.

System actionIf the STAT specifier is not present on the ALLOCATEstatement, the condition is signaled. If the condition isunhandled, the application is terminated.

Qualifying Data:


No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 object-name

Input CHARACTER*250 Name ofobject specifiedin ALLOCATEsubroutine.



RN The current operation is ignored. The remainder of theallocation list is processed and execution continues.

Programmer responseCorrect the logic of your program so that the sameallocatable array isn't allocated again until its firstoccurrence is deallocated.


FOR0312S The DEALLOCATE statement couldnot be completed. The objectobject_name was not allocated.

System actionIf the STAT specifier is not present on the DEALLOCATEstatement, the condition is signaled. If the condition isunhandled, the application is terminated.

Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 object-name

Input CHARACTER*250 Name of objectspecified inDEALLOCATEstatement.



RN The current operation is ignored. The remainder of thedeallocation list is processed and execution continues.

Programmer responseCorrect the logic of your program so that you don'tdeallocate an array isn't allocated.


FOR0340A PAUSE message VS FORTRANVersion Error 2 Number: AFB001I

ExplanationA PAUSE statement has been executed from a Fortranroutine. The message text message is whateverinformation was provided by the programmer with thePAUSE statement.

System actionExecution of the program waits for a response, whichcan be any character. After the response is entered,execution of the program continues with the statementfollowing the PAUSE statement.


Permissible Resume Actions: None

Programmer responseFollow the instructions given by message or by theperson who submitted the job for execution. Theseinstructions should indicate the action to be taken.

To resume execution, provide any single character asa response to the outstanding console message aftertaking the actions requested.


FOR0341I STOP message VS FORTRANVersion Error 2 Number: AFB002I

ExplanationA STOP statement has been executed from a Fortranroutine. The message text message is whateverinformation was provided by the programmer with theSTOP statement.

System actionThe termination imminent condition is signaled. If thecondition is unhandled, the application is terminated.





FOR0400S A Fortran main program wasexecuted from within anenclave that had already startedexecuting. VS FORTRAN VersionError 2 Number: AFB905I




Programmer responseIf you intended to call a Fortran subroutine rather thana main program, then code a SUBROUTINE statementas the first statement of that called routine.

If you want to call a main program, which will be in anew enclave, do this in one of these two ways:

• Invoke an assembler language program that uses aLINK macro instruction to pass control to the mainprogram and implicitly create a new enclave.

• Invoke the callable service CEE3CRE, which createsa new enclave and passes control to the mainprogram.

In both cases, the main program that is specified mustbe in a separate load module.


FOR0401S The execution of program unitprogram-unit failed at ISNstatement-number because anerror was detected by the compilerat that statement. VS FORTRANVersion Error 2 Number: AFB230I




Programmer responseRefer to the printed output of the compilation ofprogram unit program-unit to determine the error thatoccurred at ISN statement-number. Correct the error,then compile, link edit, and execute the job again.


FOR0402S program-name2, which has oneor more dummy arguments ofcharacter type with an assumedlength, was called by program-name1 with an argument list thatdidn't provide the lengths of thecharacter arguments. VS FORTRANVersion Error 2 Number: AFB153I

ExplanationThe subprogram program-name2 had a dummyargument of character type with an assumed length,that is, for which the current length needs to beprovided by the calling routine. However, the argumentlist provided by program unit program-name1 wasn't inthe internally-generated form produced by the Fortrancompiler when there are character arguments. Thiscould have occurred because:

• A dummy argument in program-name2 wasinadvertently coded as a character dummy argumentwith an assumed length, as in this example:

CHARACTER*(*) INPUT_ARG

• program-name1 did not provide one or more of thecharacter arguments that were required by program-name2.

• program-name1 was compiled by the VS FORTRANVersion 1 or the VS FORTRAN Version 2 compilerwith the the LANGLVL(66) compiler option.

• program-name1 was compiled by the VS FORTRANVersion 1 compiler at a level before Release 3.

• program-name1 was compiled by the FORTRAN IV HExtended or the FORTRAN IV G1 compiler.

• program-name1 was an assembler languageprogram, and the arguments were not providedin the form required when there are characterarguments.




Programmer responseBe sure that the argument list provided by program-name1 contains the number of arguments required byprogram-name2 and that they are of the correct type.


If a character argument is coded as a characterconstant, be sure to enclose the value in quotes orapostrophes.

If program-name1 is written in Fortran, compile itwith the VS FORTRAN Version 2 compiler, and do notspecify the LANGLVL(66) compiler option.

If program-name1 is written in assembler language,use the Fortran conventions for argument lists withcharacter arguments. These conventions are describedin the topic “Passing Character Arguments Using theStandard Linkage Convention” in Appendix B of VSFORTRAN Version 2 Programming Guide for CMS andMVS.

If program-name1 is neither a Fortran nor anassembler language program, the required argumentlist cannot be generated. In this case, changeprogram-name2 so the character data in the dummyargument list is of fixed, rather than of assumed,length.


FOR0404C The LIBPACK (composite module)module-name1 was at releaselevel module-level1, but theLIBPACK module-name2 was atrelease level module-level2. VSFORTRAN Version Error 2 Number:AFB142I




Programmer responseIf your JCL specifies the correct LanguageEnvironment library for execution, then this is likely tobe a problem either with the installation of LanguageEnvironment or with the availability of the library. Referthe problem to your Language Environment supportpersonnel.


FOR0405C module-name was not a validLIBPACK (composite module). VSFORTRAN Version Error 2 Number:AFB145I




Programmer responseIf your JCL specifies the correct LanguageEnvironment library for execution, then this is likely tobe a problem either with the installation of LanguageEnvironment or with the availability of the library. Referthe problem to your Language Environment supportpersonnel.


FOR0406C The shareable load modulemodule-name was loaded at anaddress above 16 Mb by thenonshareable part of program unitprogram-unit, which was runningin 24-bit addressing mode. VSFORTRAN Version Error 2 Number:AFB146I

ExplanationProgram unit program-unit was compiled with theRENT compiler option and was separated into itsnonshareable and shareable parts. The nonshareablepart was entered in 24-bit addressing mode but wasunable to pass control to its shareable part becausethe shareable part was loaded above 16 Mb.




Programmer responseEither:

• Run the program in 31-bit addressing mode by linkediting the nonshareable parts with AMODE=31 as alinkage editor parameter. This can be done only if theload module has no routines, such as those compiledwith the FORTRAN IV H Extended compiler, that arenot capable of executing in 31-bit addressing mode.

• Link edit the shareable load module usingAMODE=24 as a linkage editor parameter.



FOR0407C The shareable load modulemodule-name that was loaded bythe nonshareable part of programunit program-unit had an incorrectformat. VS FORTRAN Version Error2 Number: AFB147I

ExplanationProgram unit program-unit was compiled with theRENT compiler option and was separated into itsnonshareable and shareable parts. During execution,the program's nonshareable part loaded a load modulethat was supposed to contain the program's shareablepart. However, the load module was not in theexpected format.




Programmer responseUse the Fortran reentrant program separation tool toseparate the shareable and nonshareable parts of theprogram that was compiled with the RENT compileroption. (This tool is invoked by the use of the catalogedprocedures AFHWRL and AFHWRLG.) Then ensure thatduring the execution of the program, the load modulecontaining the shareable part is available either in alibrary referenced by a STEPLIB DD statement or in alink pack area.


FOR0409C The shareable load modulemodule-name that was loaded bythe nonshareable part of programunit nonshareable-part-name hada timestamp of timestamp1 inthe shareable part of programunit shareable-part-name. Thistimestamp differed from thetimestamp of timestamp2 in thenonshareable part of programunit nonshareable-part-name. VSFORTRAN Version Error 2 Number:AFB149I

ExplanationProgram unit program-unit was compiled with theRENT compiler option and was separated into itsnonshareable and shareable parts. During execution,the program's nonshareable part loaded a load modulethat was supposed to contain the program's shareablepart. However, the load module contained a copy ofthe code that was compiled at a different time thanthe nonshareable part. The parts are assumed to beincompatible.




Programmer responseUse the Fortran reentrant program separation tool toseparate the shareable and nonshareable parts of theprogram that was compiled with the RENT compileroption. (This tool is invoked by the use of the catalogedprocedures AFHWRL and AFHWRLG.) Then ensure thatduring the execution of the program, the load modulecontaining the shareable part is available either in alibrary referenced by a STEPLIB DD statement or in alink pack area. Also ensure that some previous copyisn't accessible so that only the corresponding copyof the shareable part load module is available to theexecuting program.


FOR0410C A Fortran subprogram was calledbefore the Fortran run-timeenvironment was initialized. VSFORTRAN Version Error 2 Number:AFB932I

ExplanationLanguage Environment did not become aware of theexistence of a Fortran subprogram in the applicationbefore the invocation of that subprogram. Usually,the presence of a Fortran routine in the applicationis detected either at the time a main program isstarted or at the time a subsequent load module isdynamically loaded using various languages' dynamiccall facilities. However, because Fortran compiled codedoesn't conform to the current Language Environmentlinkage conventions, sometimes a Fortran subprogram


isn't detected, especially if it doesn't require the use ofan run-time library services such as Input/Output.




Programmer responseEnsure that there is a main program (not necessarilywritten in Fortran) in the application and that it isexecuted before any Fortran subprograms. If this wasalready the case, then provide the following linkageeditor control statement in the input that link edits themain program:

INCLUDE SYSLIB(CEESG007)


FOR0411C VS FORTRAN Version 2 error error-number was detected by LanguageEnvironment.

ExplanationThe obsolete VS FORTRAN Version 2 error conditionwith error number error-number was detected. This inan internal error in the Fortran portion of LanguageEnvironment.




Programmer responseContact the people who provide system support atyour installation for Language Environment.


FOR0414C The shareable load modulemodule-name, which was loadedby the nonshareable part ofprogram unit program-unit, didnot contain the shareable

part shareable-part-name. VSFORTRAN Version Error 2 Number:AFB148I

ExplanationProgram unit program-unit was compiled with theRENT compiler option and was separated into itsnonshareable and shareable parts. During execution,the program's nonshareable part loaded a load modulethat was supposed to contain the program's shareablepart. However, the load module did not contain theexpected shareable part.




Programmer responseUse the Fortran reentrant program separation tool toseparate the shareable and nonshareable parts of theprogram that was compiled with the RENT compileroption. (This tool is invoked by the use of the catalogedprocedures AFHWRL and AFHWRLG.) Then ensure thatduring the execution of the program, the load modulecontaining the shareable part is available either in alibrary referenced by a STEPLIB DD statement or in alink pack area. Also ensure that some previous copyisn't accessible.


FOR0415C The shareable load modulemodule-name that was loaded bythe nonshareable part of programunit program-unit did not containthe shareable part shareable-part-name at a storage locationaccessible to the program. VSFORTRAN Version Error 2 Number:AFB148I

ExplanationProgram unit program-unit was compiled with theRENT compiler option and was separated into itsnonshareable and shareable parts. During execution,the program's nonshareable part loaded a load modulethat was supposed to contain the program's shareablepart. However, not all of that load module was loadedso that it could be used.





Programmer responseUse the Fortran reentrant program separation tool toseparate the shareable and nonshareable parts of theprogram that was compiled with the RENT compileroption. (This tool is invoked by the use of the catalogedprocedures AFHWRL and AFHWRLG.) Then ensure thatduring the execution of the program, the load modulecontaining the shareable part is available either in alibrary referenced by a STEPLIB DD statement or in alink pack area.


FOR0416S The program unit program-unitcalled the subprogram routine-name with the array array-name(array-bounds) having a dimensionwith the lower bound greater thanthe upper bound. VS FORTRANVersion Error 2 Number: AFB257I





RN Execution continues, but invalid results are probable ifa reference is made to the array whose dimensions arewrong.

Programmer responseEnsure that the declarations of the array and of thedimension arguments are consistent in program-unitand in routine-name. Also ensure that the values ofthe bounds that are provided as actual arguments forthe call do not make the lower bound greater than theupper bound for any dimension of the array.


FOR0417S The program unit program-unitcalled the subprogram routine-name with the array locatedat address array-address, offsetarray-offset, and array boundsarray-bounds. The array boundshad a dimension with the lowerbound greater than the upperbound. VS FORTRAN Version Error2 Number: AFB257I





RN Execution continues, but invalid results are probable ifa reference is made to the array whose dimensions arewrong.

Programmer responseEnsure that the declarations of the array and of thedimension arguments are consistent in program-unitand in routine-name. Also ensure that the values ofthe bounds that are provided as actual arguments forthe call do not make the lower bound greater than theupper bound for any dimension of the array.


FOR0500S A relational expression usingcharacter values with therelational operator relational-operator could not be evaluated.Character value operand-numberhad a length of operand-length,which was not between 1 and32767, inclusive. VS FORTRANVersion Error 2 Number: AFB193I


Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2


No.

Name Input/Output

Data Type andLength

Value

2 operator-name

Input CHARACTER*2 Name of therelational operator



RN The comparison is not performed, and executioncontinues.

Programmer responseEnsure that the length of the character value is neitherless than 1 nor greater than 32767. Examine anyvariables that define a character substring to be surethat they don't have values that result in an invalidlength.


FOR0501S The assignment of the charactervalue could not be performed. Thestorage area that was being copiedoverlapped with the storage areato which that data was to becopied. VS FORTRAN Version Error2 Number: AFB195I





RN The character assignment is not performed, and executioncontinues.

Programmer responseExamine any variables that define a charactersubstring to be sure that they don't have values thatresult in an excessive character length or overlappingsubstrings. Also look at EQUIVALENCE statements toensure that the character variables in question don'toverlap.


FOR0502S The assignment of the charactervalue could not be performed.

The length of the storage area towhich the data was to be copiedwas not between 1 and 32767,inclusive. VS FORTRAN VersionError 2 Number: AFB196I








FOR0503S The assignment of the charactervalue could not be performed. Thelength of the storage area fromwhich the data was to be copiedwas not between 1 and 32767,inclusive. VS FORTRAN VersionError 2 Number: AFB197I









FOR0504S The concatenation of charactervalues could not be performed.The length of one of the valueswas not between 1 and 32767,inclusive. VS FORTRAN VersionError 2 Number: AFB199I





RN The character concatenation is not performed, andexecution continues.

Programmer responseEnsure that the lengths of the character values are notless than 1 and not greater than 32767. Examine anyvariables that define a character substring to be surethat they do not have values that result in an invalidlength.


FOR0601S The funcname function could notbe evaluated. The value of theargument was not between 0and limit, inclusive. VS FORTRANVersion Error 2 Number: AFB258I


No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 function Input CHARACTER*8 funcname



RN The CHAR or ACHAR function is ignored, and executioncontinues.

Programmer responseEnsure that the argument to the ACHAR function in notless than 0 nor greater than 127 or that the argumentto the CHAR function in not less than 0 nor greaterthan 255. The values of 127 and 255 are the greatestvalues in the ASCII and EBCDIC collating sequences,respectively.


FOR0602S The INDEX function could notbe evaluated. Argument numberargument-number had a length ofargument-length, which was notbetween 1 and 32767, inclusive.VS FORTRAN Version Error 2Number: AFB259I


Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 function Input CHARACTER*8 INDEX



RN The INDEX function is ignored, and execution continues.

Programmer responseEnsure that the length of the character value inargument argument-number is neither less than 1 norgreater than 32767. Examine any variables that definea character substring to be sure that they don't havevalues that result in an invalid length.


FOR0603S The lexical relational functioncould not be evaluated. Argumentnumber argument-number had alength of argument-length, whichwas not between 1 and 32767,inclusive. VS FORTRAN VersionError 2 Number: AFB191I



Qualifying Data: None.



RN The lexical compare is ignored, and execution continues.

Programmer responseEnsure that the length of the character value inargument argument-number for the the LGE, LGT, LLE,or LLT function is neither less than 1 nor greater than32767. Examine any variables that define a charactersubstring to be sure that they don't have values thatresult in an invalid length.


FOR0610S The value of argument numberargno for the the MVBITSsubroutine was not between 0and limit, inclusive. VS FORTRANVersion Error 2 Number: AFB159I


Qualifying Data: None.



RN The lexical compare is ignored, and execution continues.

Programmer responseFor argument argno provide a value that is between 0and limit.


FOR0611S The sum of the values of argumentnumbers argno1 and argno2for the MVBITS subroutine wasgreater than the number of bits inthe first argument. VS FORTRANVersion Error 2 Number: AFB176I


Qualifying Data:


Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 function Input CHARACTER*8 MVBITS



RN The MVBITS subroutine is ignored, and executioncontinues.

Programmer responseAdjust the values of arguments argno1 and argno2 sothat the specified string of bits doesn't extend beyondthe end of the integer.


FOR0612S The funcname function couldnot be evaluated. The valueof argument number argno wasnot between lowlimit and hilimit,inclusive. VS FORTRAN VersionError 2 Number: AFB159I


Qualifying Data:


Data Type and Length Value

1 parm-count

Input INTEGER*4 2

2 function Input CHARACTER*8 funcname



RN The bit manipulation function is ignored, and executioncontinues.


Programmer responseFor the function funcname, ensure that the valueprovided for argument argno is in the range of lowlimitthrough hilimit.


FOR0613S The IBITS function could not beevaluated. The sum of the secondand the third arguments wasgreater than the number of bits inthe first argument. VS FORTRANVersion Error 2 Number: AFB159I


Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 function Input CHARACTER*8 IBITS



RN The IBITS function is ignored, and execution continues.

Programmer responseFor the IBITS function, adjust the values of arguments2 and 3 so that the specified string of bits doesn'textend beyond the end of the integer.


FOR0614S The IBITS function could not beevaluated. The value of the secondor third argument was less than0. VS FORTRAN Version Error 2Number: AFB159I


Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 function Input CHARACTER*8 IBITS



RN The IBITS function is ignored, and execution resumes.

Programmer responseFor the IBITS function, adjust the values of arguments2 and 3 so that they are nonnegative integer valuesthat indicate the starting bit number (relative to 0) andthe number of bits to be extracted.


FOR0650S The callable service service-namefailed. Qualifying datum numberindex was specified as the secondargument, but that qualifyingdatum was not available for thecondition.

ExplanationEither QDFETCH or QDSTORE was called to obtain orupdate an element of qualifying data, but index, whichspecifies the ordinal number of the qualifying datumto be referenced, was either less than 1 or greaterthan the total number of elements of qualifying dataassociated with this instance of the condition.






Programmer responseEnsure that the second argument is a positive integerwhose value is the ordinal number of an element ofqualifying data.



FOR0651S The callable service service-namefailed. The first argument, thecondition token, was not acharacter variable or arrayelement of length 12.

ExplanationEither the first argument was not a character variableor character array element of length 12 or theargument list wasn't in the internally-generated formproduced by the Fortran compiler when there arecharacter arguments. The latter could have occurredbecause:

• The call was made from a program compiled by theVS FORTRAN Version 1 or the VS FORTRAN Version 2compiler with the the LANGLVL(66) compiler option.

• The call was made from a program compiled by theVS FORTRAN Version 1 compiler at a level beforeRelease 3.

• The call was made from a program compiled by theFORTRAN IV H Extended or the FORTRAN IV G1compiler.

• The call was made from an assembler languageprogram, and the arguments were not providedin the form required when there are characterarguments.





RN The service is ignored, and execution continues.

Programmer responseBe sure that the argument list contains the number ofarguments required by service-name and that they areof the correct type. In particular, ensure that the firstargument is a condition token whose declaration is acharacter variable or character array element of length12.

If the program is written in Fortran, compile it with theVS FORTRAN Version 2 compiler, and do not specifythe LANGLVL(66) compiler option. If it is writtenin assembler language, use the Fortran conventionsfor argument lists with character arguments. These

conventions are described in the topic “PassingCharacter Arguments Using the Standard LinkageConvention” in Appendix B of VS FORTRAN Version 2Programming Guide for CMS and MVS.


FOR1000S locator-text The formatted inputdata input-field had a value thatwas outside the range of valuesthat could be contained withinthe integer item in the input itemlist. VS FORTRAN Version 2 ErrorNumber: AFB206I

Explanationinput-field is a character string that was interpreted asan integer value; an integer variable or array elementthat was given in the input item list of a READstatement was supposed to become defined with thisvalue. However, the value of input-field was outsidethe acceptable range. These are the ranges of integervalues corresponding to integer data items of differentlengths:

Data Type Max. Positive Value Max. Negative Value

INTEGER*1

127 (27 -1) -128 (-27 )

INTEGER*2

32767 (215-1) -32768 (-215)

INTEGER*4

2147483647 (231-1) -2147483648 (-231)

INTEGER*8

9223372036854775807 (263-1)

-9223372036854775808 (-263)

locator-text gives more information about the locationof the error, and can be one of the following:

• The READ statement for an internal file failed.• The READ statement for unit unit-number which was

connected to file-name failed.

System actionThe input item being processed and the remainder ofthe items in the input item list become undefined. Ifneither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. If thecondition is unhandled, the application is terminated.


No.

Name Input/

Output

Data Type andLength

Value

5 input-field-desc

Input Q_DATA_DESC The q_datadescriptor for input-field. It contains thedata type and thelength of input-field.

6 subroutine- name

Input CHARACTER*n Formatted inputdata; that is, thecharacter stringthat is beinginterpreted asan integer value.Length n is partof input_field-descand has a maximumpossible value of255.

7 record-desc

Input Q_DATA_DESC The q_datadescriptor forrecord. It containsthe data type andthe length of record.

7 record-desc


8 record Input CHARACTER*n Formatted inputrecord thatcontained thecharacter stringbeing interpreted asan integer value.Length n, whichincludes only thedata portion of therecord, is part ofrecord-desc.

9 result-desc

Input Q_DATA_DESC The q_datadescriptor forresult. It containsthe data type andthe length of result.

10

result output INTEGER*n New output value,where n, the length,is part of result-desc and could be1, 2, 4, or 8.


R0 The input item receives the value placed in result,execution continues, and the remainder of the input itemlist is processed.

Programmer responseEnsure that the following are true:

• The edit descriptor specifies the correct field width.

• The value specified by input-field is within therequired range for the integer variable size.

• input-field doesn't have any imbedded or trailingblanks that are incorrectly treated as zeros, thuschanging the intended magnitude of the number.Blanks are treated as zeros in these cases:

– The BLANK specifier is given on the OPENstatement with value of ZERO.

– The BZ edit descriptor is included in the formatspecification.

– There is no OPEN statement, and there is no BNedit descriptor in the format specification.


FOR1001E locator-text The length of therecord to be written exceededthe maximum data length, data-length, allowed for records inthe file. VS FORTRAN Version 2Error Number: AFB164I, AFB201I(format 1), AFB201I (format 2),AFB204I, AFB212I, AFB213I

ExplanationBased on the type of formatting described by the FMTspecifier (or by its absence) on the WRITE or REWRITEstatement, one of the following exceeded data-length,which is the smaller of either the maximum lengthof the data that can fit in a record in the file or thevalue given in the RECL specifier, if any, on the OPENstatement:

• For output using a format specification:

– The length of the record described by the outputitem list and the format specification.

• For list-directed output or namelist output:

– For an output item of neither character type norcomplex type, the formatted length of the item.

– For an output item of complex type, the formattedlength of the real or the imaginary part.

The formatted lengths of the output from list-directed formatting for the various data typesis listed in “WRITE Statement — List-DirectedI/O to External Devices” in VS FORTRAN Version2 Language and Library Reference. For namelistformatting, the lengths of the data are the same.

• For unformatted output:

– The total length of all the items in the output itemlist.


The maximum length of a record that can be writtenon a particular file depends on the values of certainspecifiers given on the OPEN statement and onvarious file characteristics managed by the underlyingoperating system's access methods. Length is takenfrom one or more of the following:

• Files connected for sequential access:

– Non-VSAM files

- From the LRECL value given in the DD statementor ALLOCATE command (when dynamic fileallocation is not involved).

- From the LRECL value given in the invocation ofthe FILEINF callable service (when dynamic fileallocation is involved).

- For a DASD or labeled tape file for which thedata set existed previously, from the LRECLvalue given when the file was either allocatedor created.

- From the default LRECL value specified for theunit in the Unit Attribute Table either as shippedby IBM or as customized for the installation.

- From the LRECL value derived from theRECFM and BLKSIZE values when there is aconflict among these three parameters. Refer to“Considerations for Specifying RECFM, LRECL,and BLKSIZE” in Chapter 12, or in VS FortranVersion 2 Programming Guide for CMS and MVS.

When the record format is one of the variable-length formats: (variable (V), variable blocked(VB), variable spanned (VS), or variable blockedspanned (VBS), the maximum length of the datathat can be written is four bytes less than theLRECL value.

– VSAM files

- From the maximum record length given asthe second sub-parameter of the RECORDSIZEparameter of the Access Method ServicesDEFINE command that was used to define thecluster.

• Files connected for direct access:

– From the value given by the RECL specifier on theOPEN statement.

In certain cases, this value must be consistentwith the record length specified previously:

- VSAM files (RRDSs):

With the maximum record length given asthe second sub-parameter of the RECORDSIZEparameter of the Access Method ServicesDEFINE command that was used to define thecluster.

- Non-VSAM files that existed previously and arenot being reformatted:

With the record length given in the RECLspecifier on the OPEN statement that was usedto create the file.

An existing file connected for direct access is notreformatted unless one or more of the following istrue:

- WRITE is given as the value of the ACTIONspecifier on the OPEN statement.

- NEW is given as the value of the STATUSspecifier on the OPEN statement.

- No records have been written into the filepreviously.

• Files connected for keyed access:

From the maximum record length given asthe second sub-parameter of the RECORDSIZEparameter of the Access Method Services DEFINEcommand that was used to define the cluster.

• Internal files:

From the length of the record or records thatcomprise the internal file. This is the length of thecharacter variable, of the character substring, orof the character array element that comprises theinternal file. For an internal file that is a characterarray, this is the length of the correspondingcharacter array element.


• The WRITE statement for an internal file failed.• The statement statement for unit unit-number which

was connected to file-name, failed.

System actionIf either the ERR or the IOSTAT specifier is presenton the I/O statement, then before control returns tothe program, the record described for the action RN iswritten.

If neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. If thecondition either is unhandled or is handled by movingthe resume cursor and resuming, then the recorddescribed for the action RN is written. If the conditionis unhandled, the enclave stops executing after therecord has been written.

Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of READ,and parm_count has a value of 10. In addition, thereare these qualifying data:



Data Type and Length Value

5 access Input CHARACTER*10 For an external file, thevalue SEQUENTIAL,DIRECT, or KEYED,depending on if thefile is connectedfor sequential, direct,or keyed access,respectively. For aninternal file, thisqualifying datumcontains the valueSEQUENTIAL.

6 fmt-type Input CHARACTER*8 One of the followingvalues to indicate thetype of formattingindicated by theFMT specifier (orits absence) on theWRITE or REWRITEstatement:

• blanks:Unformatted

• FORMAT: Formatspecification

• *: List-directedformatting

• NAMELIST:Namelist formatting

7 data_len Input INTEGER*4 Maximum length ofthe data that canbe written into therecords in the fileduring this connection.If this length iscontrolled by a RECLspecifier on theOPEN statement, thisqualifying datum hasthat value given bythat RECL specifier.Otherwise, this is themaximum amount ofdata that can bewritten in the recordsin the file. Whenthe record format isone of the variable-length formats, thatis, variable (V),variable blocked (VB),variable spanned (VS),or variable blockedspanned (VBS), thelength given here isthe LRECL value less4 (unless the RECLspecifier had a smallervalue).


RN A record is written, but its length does not exceed themaximum length allowed for the file, and no additionalrecord is written. Formatted and unformatted output arehandled slightly differently:

Formatted output:

For a data item of other than character type thatdoesn't fit in the record, that data item is ignored,that is, none of it is placed in the record. (If therecords are of fixed-length format, blanks fill the rest


of the record. Otherwise, no additional charactersare added to the record.) The rest of the output itemlist and the rest of the format specification, if any, areignored.For a data item of character type, including acharacter constant in the format specification, thatdoesn't fit in the record, as much of the item as canfit is placed in the record. The rest of this item, therest of the output item list, and the rest of the formatspecification, if any, are ignored.

Unformatted output:

As much of the data from the output item list as canfit is placed in the record. This includes the data itemthat would overflow the record; as much of it as canfit is placed in the record. The rest of this item andthe rest of the output item list are ignored.

In either case, execution then continues.

RF This action depends on several factors:

• The type of formatting, if any, specified in the WRITEor REWRITE statement,

• if the file is connected for sequential, direct, or keyedaccess

• The record format.

For output using a format specification:

• Files connected for sequential access: For aformatted data item of other than character typethat doesn't fit in the record, none of it is placedin the record from which it would overflow. (If therecords are of fixed-length format, blanks fill the restof the record. Otherwise, no additional characters areadded to the record.) The entire formatted data itemis placed into the next record beginning at characterposition 1. Should the maximum length record be tooshort to hold this data item, as much of the data ascan fit is placed in this next record, and the rest of thedata is lost. No error is detected for this loss of data.

For a data item of character type (including acharacter constant in the format specification) thatdoesn't fit in the record, as much of the item as can fitis placed in this record, and the remainder continuesinto the next record or records for as many records asit takes to hold the entire item.

After the formatted data item is placed in the nextrecord, normal processing of the rest of the formatspecification and the output item list continues. Thissame condition could be detected again for the sameWRITE or REWRITE statement.

• Files connected for direct access: The action is thesame as for sequential access. When applied to directaccess, the term next record refers to the record withthe next higher record number.

• Files connected for keyed access: This action is thesame as RN.



RF(cont.)

For list-directed and namelist output:

• For the formatted data item (or the real or imaginarypart of an item of complex type) that's longer than therecord, none of the data is placed in the record. (If therecords are of fixed-length format, blanks fill the restof the record. Otherwise, no additional characters areadded to the record.) The rest of the output item list isignored.

For data of character type, this error is not detected.Such data is automatically spanned across recordswithout this being considered an error.

For unformatted output:

• Files connected for sequential access: For non-VSAM files that have a record format of variablespanned (VS) or variable blocked spanned (VBS), arecord of the size required by the output item listis written. This is just as though the LRECL valuespecified an unlimited record length. Such recordsgenerally cannot be read using languages other thanFortran because the lengths of records in the fileexceed the LRECL value associated with the file.

For other files connected for sequential access, thisaction is the same as RN. .

• Files connected for direct access: As much of thedata from the output item list as can fit is placed inthe record. This includes the data item that wouldoverflow the record; as much of it as can fit is placedin the record. The rest of this item plus the remainingdata items in the output item list are written into asmany records as necessary to hold the data. Eachsuccessive record is written as the record with thenext higher record number.

• Files connected for keyed access: This action is thesame as RN.

Programmer responseEnsure that the length of the record described orimplied by the output item list and the formatidentifier, if any, is no longer than the maximum lengthrecord that can be written to the file. Either the lengthof the record to be written or the maximum recordlength allowed for the file must be changed to correctthe condition or conditions described in “Explanation.”If the length of the record being written isn't what youintended, then you might have to change:

• The type of formatting indicated by FMT specifier(or its absence) in the I/O statement. For example,perhaps you intended to write the file using aformat specification rather than using list-directedformatting.

• The format specification. This can include errorsin the edit descriptors, field widths, repetitionfactors, nesting levels, Hollerith constants (H editdescriptor), and character constants.

• The output item list. There could be errors in thenumber of items in the list, in the data types and

lengths of individual items, and in the specificationof implied DOs in the output item list.

If the length of the record is what you intended, thenthe maximum record length allowed for the file mustbe increased. If you are creating a new file, you mighthave to change:

• The record length given in the RECL specifier of theOPEN statement

• The LRECL parameter on a DD statement or a TSOALLOCATE command (when dynamic file allocationis not involved) or the LRECL parameter for theFILEINF callable service (when dynamic allocationis involved)

For record formats of variable spanned or variableblocked spanned, you can make the record lengthlarger than the block size. You can also define therecord to be of unlimited length in one of these ways:

– When dynamic file allocation is not involved,provide a value of X for the LRECL parameter ofa DD statement or a TSO ALLOCATE command.

– When dynamic file allocation is involved, providea value of -1 for LRECL in the arguments for theFILEINF callable service.

For any of the variable-length record formats, thatis, for variable (V), variable blocked (VB), variablespanned (VS), or variable blocked spanned (VBS),the length given as LRECL includes a 4-byte recorddescriptor word. Therefore, the LRECL value must befour bytes larger than the largest amount of data thatyou want to write in a single record.

• The RECFM and BLKSIZE parameters on a DDstatement or a TSO ALLOCATE command whendynamic file allocation is not involved or asparameters for the FILEINF callable service whendynamic file allocation is involved. Note thatwhen not all of the RECFM, LRECL, and BLKSIZEparameters have been specified for a particularprogram, the defaults in the Unit Attribute Tableare applied for the omitted ones. Sometimes thiscauses inconsistencies among the parameters; thisis resolved as described in “Considerations forSpecifying RECFM, LRECL, and BLKSIZE” in Chapter12, or in VS Fortran Version 2 Programming Guide forCMS and MVS.

• The use of a particular device or file itself if thedevice or file isn't capable of accepting a largeenough record

• The maximum record length given as the secondsub-parameter of the RECORDSIZE parameter onthe DEFINE command that defined a VSAM cluster

If you are writing on an existing file whose previouscontents you want to retain, then you generally cannotincrease the record length without recreating the file.


The person at your installation who gives systemsupport for Language Environment can change yourinstallation's default values for record format, recordlength, and block size for various units. This is doneby customizing the the Unit Attribute Table. As part ofthis process, the SFLRECL or SULRECL parameters onthe AFHODCBM macro instructions can specify largerdefault values for formatted or unformatted I/O. Eachunit (other than the error message unit) can be givendifferent default values.


FOR1002E locator-text An input item requireddata from beyond the end ofthe data that was available ina record. The length of theavailable data was data-length. VSFORTRAN Version 2 Error Number:AFB164I, AFB201I (format 1),AFB201I (format 2), AFB204I,AFB212I, AFB213I

ExplanationIn a READ statement, one or more of the input itemsin the input item list required that data be transferredfrom beyond position data-length of the record. data-length is the smaller of either the value given in theRECL specifier, if any, on the OPEN statement or thelength of the record available from the underlyingsystem access methods. This latter length is limitedby the value of the LRECL parameter, if any, in the filedefinition if this LRECL value is less than the actuallength of the previously written record. The specificerror that is detected differs based on these factors:

• The type of formatting described by the FMTspecifier (or by its absence) on the READ statement

• The record format (the RECFM value) for the file• The value given in the PAD specifier, if any, on the

OPEN statement• The value of the RECPAD run-time option

These are the specific errors that this conditionrepresents:

• For input using a format specification:

– Both of the items (1 and 2) were true:

1. Either of these two conditions occurred:

- An input item referred to a field that startedbeyond position data-length in the record.

- An input item with a corresponding editdescriptor of A referred to a field that

extended beyond position data-length in therecord.

Note that because the T edit descriptor couldhave been used to specify the position at whichdata transfer was to begin, this condition doesnot necessarily imply that just the input itemsalong with their corresponding repeatable editdescriptors represented more data than therecord contained.

2. Either of these two conditions applied:

- The OPEN statement had a PAD specifierwhose value was NO.

- There was no PAD specifier on the OPENstatement (or there was no OPEN statementbecause the file is a preconnected file or aninternal file). In addition, one of these casesapplied:

• The RECPAD(NONE) run-time option was ineffect.

• The RECPAD(VAR) run-time option was ineffect and the file was an external filethat was a non-VSAM file with a recordformat (that is, the RECFM value that wasapplied to the file) of either fixed (F) orfixed blocked (FB).

• The RECPAD(VAR) run-time option was ineffect and the file was an external filethat was a VSAM relative record data set(RRDS).

• For unformatted input:

– All three of the items were true:

1. The total length of the items in the input itemlist exceeded the number of bytes of data(data-length) available from the record.

2. The NUM specifier was not given in the READstatement.

3. If the unit was connected for direct access, theOPEN statement rather than the DEFINE FILEstatement from the FORTRAN 66 languagestandard was used to connect the file.

• For list-directed input:

– Both of the items were true:

1. There were no characters other than blanks inthe record that corresponded to one or moreinput items.

2. The record format (that is, the RECFM valuethat was applied to the file) was either variablespanned (VS) or variable blocked spanned(VBS).





System actionIf either the ERR or the IOSTAT specifier is presenton the READ statement, then before control returns tothe program, the RN action described at" PermissibleResume Actions" is taken.

If neither the ERR nor the IOSTAT specifier is presenton the READ statement, the condition is signaled. Ifthe condition either is unhandled or is handled bymoving the resume cursor and resuming, then the RNaction described at " Permissible Resume Actions" istaken. If the condition is unhandled, execution of theenclave terminates.

Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within the basic set, statement has a value of READ,and parm_count has a value of 7. In addition, there arethese qualifying sets:

No.

Name Input/Output

Data Type andLength

Value

5 access Input CHARACTER*10 For an externalfile, the valueSEQUENTIAL,DIRECT, orKEYEDdepending on ifthe file isconnected forsequential,direct, or keyedaccess,respectively. Foran internal file,this qualifyingdatum containsthe valueSEQUENTIAL.

6 fmt-type

Input CHARACTER*8 One of thefollowing valuesto indicate thetype offormattingindicated by theFMT specifier (orits absence) onthe READstatement:

• blanks:Unformatted

• FORMAT:Formatspecification

• *: List-directedformatting

7 data-length

Input INTEGER*4 Maximum lengthof data available

No.

Name Input/Output

Data Type andLength

Value

to be read. If theOPEN statementhad a RECLspecifier, thendata-length couldbe less than whatis reflected inrecord-desc.

8 record-desc

Input Q_DATA_DESC The q_datadescriptor forrecord. Itcontains the datatype and thelength of record.

9 record Input CHARACTER*n For a formattedREAD statementor for anunformattedREAD statementdirected to a filewith other thanspanned records(VS or VBS), thewhole inputrecord.

For anunformattedREAD statementthat read from arecord that spansmore than oneblock, only thesingle recordsegment thatincludes positiondata-length ofthe record.

Length n, whichincludes only thedata portion ofthe record, is partof record-desc.



RN Formatted and unformatted input are handled slightlydifferently:

Formatted input:

• The input item that required data from beyond theend of the record as well as any remaining inputitems, if any, are not modified. The remainder of theformat specification, if any, is ignored.

Unformatted input:

• All of the data from the record is transferred to theitems in the input item list. This includes the item forwhich there was not enough data in the record; asmuch of it as is available is transferred to the item.


The rest of this item and the remaining input items, ifany, are not modified.

In both cases, the file is positioned to the end of therecord that was read (that is, to the end of the recordthat was too short).


RF If the READ statement is for unformatted I/O and it refersto a unit that is connected for direct access, then datafrom as many of the succeeding records as necessary istransferred to the input items, and the file is positionedto the end of the last record from which data wastransferred. (This action is similar to the semantics of theFORTRAN 66 standard except that there is no associatedvariable.) For other READ statements, this action is thesame as RN.

Programmer responseIf you want to read an existing record, change one ormore of the following:

• The type of formatting indicated by FMT specifier(or its absence) in the I/O statement. For example,you might have to read the record with list-directedformatting rather than with a format specificationin order to be consistent with the structure of theexisting record.

• The format specification. This could include errors inthe edit descriptors field widths, repetition factors,and nesting levels.

• The input item list. There could be errors in thenumber of items in the list, in the data types andlengths of individual items, and in the specificationof implied DOs in the input item list.

• The value given for the RECL specifier on the theOPEN statement. If this value is limiting the availableamount of data to less than what the record actuallycontains, you should increase it to allow additionaldata to be read.

• The NUM specifier for an unformatted READstatement. When there is a NUM specifier on anunformatted READ statement, encountering a recordthat is shorter than the total length of all of the inputitems does not cause this error to be detected. Inthis case:

1. All of the data from the record is transferred tothe input items. This includes the data item forwhich there was not enough data in the record;as much of it as is available is transferred to theitem.

2. The rest of this input item and the remaininginput items, if any, are not modified.

3. The variable or array element num given in theNUM=num specifier becomes defined with the

number of bytes of data that were transferred tothe input items.

• The position of the file. Perhaps previous I/Ostatements (READ, WRITE, BACKSPACE, REWIND,and so on) caused the file to be positioned to arecord other than the one you intended to read.

• Blank padding, which can be used when your READstatement has a format specification. When it isused, records are treated as though they wereextended with a sufficient number of blanks tosupply data for all of the input items. Blank paddingis in effect either when the OPEN statement has aPAD specifier that has a value of YES or when thereis no PAD specifier when certain sub-options of theRECPAD run-time option are in effect.

The following RECPAD run-time option values causeblank padding to be in effect:RECPAD(VAR)

Any of the following:

– An external file that is a non-VSAM file with arecord format (the RECFM value) of other thanfixed (F) or fixed blocked (FB)

– An external file that is a VSAM entry-sequenced data set (ESDS) or key-sequenceddata set (KSDS)

– An internal file

Note that for an external file connected fordirect access, a non-VSAM file must have arecord format of fixed, and a VSAM file mustbe an RRDS; therefore, the run-time optionRECPAD(VAR) won't alleviate the problem for afile connected for direct access.

RECPAD(ALL)Any file (internal or external; VSAM of any type;non-VSAM with any record format)

When blank padding is used to treat a record asthough it were extended with blanks, the values thatwould be provided for the input items that wouldotherwise have caused this error to be detected areas follows:

– For a field that corresponded to an edit descriptorof A and that would have extended beyond thenumber of characters available from the record,the portion of the field in the record would beextended with blanks and transferred to the inputitem.

– For a field that corresponded to an edit descriptorof A and that would have started beyond thenumber of characters available from the record,the input item becomes defined with a value ofblanks.


– For a field that corresponded to an edit descriptorof L and that would have started beyond thenumber of characters available from the record,the input item becomes defined with a value offalse.

– For a field that corresponded to one of thenumeric edit descriptors and that would havestarted beyond the number of characters availablefrom the record, the input item becomes definedwith a value of zero.

Note that because a run-time option controls thisextension of records with blanks, the appropriateaction is taken for all records and files to which itapplies.

If the existing record of the file doesn't have the lengthor structure that you intended, you might have torecreate the file after correcting either the programthat originally wrote the file or the file definitionsthat were in effect when the file was created. Thereis more detailed information on this subject in the“Programmer Response” topic for condition FOR1001.


FOR1003S locator-text A character thatwasn't numeric was found in theformatted input data where anumeric character was expected.The input field was 'input-field'. VSFORTRAN Version 2 Error Number:AFB215I

ExplanationFor a READ statement, input-field is a character stringthat was interpreted as an integer, real or complexvalue either because the input item in the input itemlist was an integer, real or complex data type, orbecause the format specification had an I, E, F, Q or Dedit descriptor. input-field contained characters otherthan 0 through 9 where only these characters wereallowed.

When the input is interpreted as a complex value,the expected format of input-field depends on if aformat specification is used. If a format specificationis used, two Fortran real numbers are used to describea complex number: one describing the real part of thecomplex number, the other describing the imaginarypart of the complex number. For list-directed ornamelist, input-field should have the form of a complexconstant. Note, however, that for list-directed ornamelist input, condition FOR1006 could be detectedin some cases for complex input.




System actionThe input item being processed, and the remainder ofthe items in the input item list are undefined. If neitherthe ERR nor the IOSTAT specifier is present on the I/Ostatement, the condition is signaled. If the condition isunhandled, the application is terminated.

Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of READ,and parm-count has a value of 8. In addition, there arethese qualifying data:

No.

Name Input/Output

Data Type andLength

Value

5 input-field-desc

Input Q_DATA_DESC The q_datadescriptor forinput-field. Itcontains the datatype and thelength of input-field.

6 input-field

Input/Output

CHARACTER*n Formatted inputdata; that is, thecharacter stringthat is beinginterpreted aseither an integer,real, or complexvalue. The lengthn is part of input-field-desc andhas a maximumpossible value of255.

7 index Input INTEGER*4 Index in input_field of thecharacter in error.

8 record_desc

Input Q_DATA_DESC The q_datadescriptor forrecord. It containsthe data typeand the length ofrecord.

9 record Input CHARACTER*n Formatted inputrecord thatcontained thecharacter stringbeing interpretedas a numericvalue. The lengthn, which includesonly the dataportion of therecord, is part ofrecord-desc.


No.

Name Input/Output

Data Type andLength

Value

10 result-desc

Input Q_DATA_DESC The q_datadescriptor forresult. It containsthe data typeand the length ofresult.

11 result Output See result_desc. Result value thatis used whenthe release_optionaction isrequested by theuser conditionhandler. The datatype can be aninteger with alength of 1, 2, 4,or 8, or it canbe real with alength of 4, 8, or16. When a formatspecification isused, the realor imaginary partof a numberis supplied asqualifying data asa real number ofhalf the length.



RI Character string that is in input-field (whose lengthis part of input-field-desc) is converted to a valuethat has the data type specified by result-desc andthe data type specified by result-desc, and the inputitem becomes defined with this value. Executioncontinues, and the remainder of the input item listis processed.

release-option

Input item, or the real or imaginary part of acomplex input item, becomes defined with the valueresult.


• input-field contains formatted data that can beconverted to the expected data type (refer to VSFORTRAN Version 2 Language and Library Referencefor the form that integer, real and complex constantscan have),

• The edit descriptor does not indicate numeric inputwhere other input should be indicated,



FOR1004S locator-text A character thatwasn't a hexadecimal characterwas found in the formattedinput data where a hexadecimalcharacter was expected. The inputfield was 'input-field'. VS FORTRANVersion 2 Error Number: AFB225I

ExplanationFor a READ statement, input-field is a characterstring that was interpreted as hexadecimal databecause there was a Z edit descriptor in theformat specification. Hexadecimal data consists of thecharacters 0 through 9 and A through F, but input-fieldcontained other characters.






No.

Name Input/Output

Data Type andLength

Value

5 input-field-desc

Input Q_DATA_DESC The q_datadescriptor forinput-field. Itcontains the datatype and the lengthof input-field.

6 input-field

Input/Output

CHARACTER*n Formatted inputdata, that is, thecharacter stringthat is beinginterpreted as ahexadecimal value.The length n ispart of input-field-desc and has amaximum possiblevalue of 255.



No.

Name Input/Output

Data Type andLength

Value

8 record-desc


9 record Input CHARACTER*n Formatted inputrecord thatcontained thecharacter stringbeing interpretedas a numericvalue. The lengthn, which includesonly the dataportion of therecord, is part ofrecord-desc.

10 result-desc


11 result Output Q_DATA_DESC Result value thatis used whenthe release_optionaction is requestedby the usercondition handler.



RI The character string that is in input-field whoselength is part of input-field-desc) is converted toa hexadecimal value, and the input item becomesdefined with this value. Execution continues, and thremainder of the input list is processed.

release-option

The input item becomes defined with the valueresult.


• input-field contains formatted data that can beconverted to hexadecimal data,

• The edit descriptor does not indicate hexadecimalinput where other input should be indicated.



FOR1005S locator-text The formatted inputdata input-field was outside therange of values that could becontained within the real or

complex input item. VS FORTRANVersion 2 Error Number: AFB226I

ExplanationFor a READ statement, input-field is a character stringthat was interpreted either as the value of a realnumber or as the value of the real or the imaginarypart of a complex number. This value exceeded thepermissible range for a floating-point number. Thelargest magnitude is approximately 7.2E+75, and thesmallest magnitude is approximately 5.4E-79.

The locator-text gives more information about thelocation of the error, and can be one of the following:

• The READ statement for an internal file failed.• The READ statement for unit unit-number, which was

connected to file-name, failed.



No.

Name Input/Outpu

t

Data Type andLength

Value

5 input-field-desc


6 input-field

Input CHARACTER*n Formatted inputdata, that is, thecharacter stringthat is beinginterpreted as aa real value oras the real orimaginary part ofa complex value.The length nis part of input-field-desc andhas a maximumpossible value of255.


No.

Name Input/Outpu

t

Data Type andLength

Value

7 return-desc

Input Q_DATA_DESC The q_datadescriptor forrecord; containsthe data typeand the length ofrecord.

9 record_desc


9 result output REAL*n New output value,where n, thelength is partof result-desc ancould be 4, 8, or16.



release-option

Input item becomes defined with the value in result.Execution continues, and the remainder of the inputitem list is processed.


• The formatted data in input-field is within therequired range for a real number,

• input-field does not contain trailing blanks if eitherthe BLANK specifier is given on the OPEN statementwith value of ZERO or the BZ edit descriptor isincluded on the format specification.


FOR1006S locator-text For list-directed input,the variable was of complex type,but the formatted input data wasnot in the correct format for acomplex constant. The formattedinput data was input-field. VSFORTRAN Version 2 Error Number:AFB238I

ExplanationFor a READ statement, input-field is a portion of thecharacter string that was interpreted as a complexconstant for list-directed input, and can be either thereal part, the imaginary part, or both. input-field eithercontained embedded blanks in the real part or the

imaginary part of the complex number, did not containa comma as a separator between the real part and theimaginary part, or was not enclosed in parentheses. Or,the end of the record occurred other than between thereal part and the comma or between the comma andthe imaginary part.





Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of READ,and parm_count has a value of 8. In addition, there arethese qualifying data:


Data Type andLength

Value

5 input-field-desc


5 input-field

Input CHARACTER*n Formatted inputdata, that is,a part of thecharacter stringthat is beinginterpreted as acomplex number.It can be eitherthe real part, theimaginary part, orboth. The lengthn is part of input-field-desc andhas a maximumpossible value of255.

7 return-desc




Data Type andLength

Value

8 record Input CHARACTER*n Formatted inputrecord thatcontained thecharacter stringbeing interpretedas a complexnumber. Thelength n, whichincludes only thedata portion of therecord, is part ofrecord-desc.


RN Current operation is ignored. The remainder of thedeallocation list is processed and execution continues.



RN Execution continues, and the remainder of the input itemlist is ignored.

Programmer responseEnsure that input-field contains no embedded blanksin the real part or the imaginary part of the complexnumber, contains a comma as a separator, is enclosedby a left and a right parenthesis, and, if the thecomplex number does not fit into one record, that theend of the record occurs between the real part and thecomma or between the comma and the imaginary part.


FOR1007S locator-text The input item was oftype character, but the formattedinput data did not begin withan apostrophe or with a quote.The input field was input-field. VSFORTRAN Version 2 Error Number:AFB238I

ExplanationFor a READ statement, input-field is a character stringthat was interpreted as a character constant forlist-directed input. input-field did not begin with anapostrophe or with a quote.




System actionThe input item being processed and the remainder ofthe input items in the input item list are undefined.If neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. If thecondition is unhandled, the application is terminated.


No.

Name Input/Output

Data Type andLength

Value

5 input-field-desc

Input Q_DATA_DESC The q_datadescriptor forinput-field;contains the datatype and the lengthof input-field.

6 input-field

Input CHARACTER*n Formatted inputdata; that is, thecharacter stringthat is beinginterpreted as acharacter value.The length n ispart of input-field-desc and has amaximum possiblevalue of 255.

7 record-desc


8 record Input CHARACTER*n Formatted inputrecord thatcontained thecharacter stringbeing interpretedas a charactervalue. The lengthn, which includesonly the dataportion of therecord, is part ofrecord-desc.


RN The remainder of the input items in the input item list areignored, and execution continues.

Programmer responseEnsure that input-field is delimited by apostrophes orquotes, and that the beginning and ending delimitersare the same.



FOR1009S locator-text The list-directed inputdata did not have a valueseparator following the endingdelimiter. The input data endedwith input-field. VS FORTRANVersion 2 Error Number: AFB238I

ExplanationFor a READ statement, input-field is a character stringthat was interpreted as a character constant (delimitedby apostrophes or quotes) or a complex constant(delimited by parentheses) for list-directed input.input-field was not followed by a value separator,where a value separator can be either a comma ( , ), ablank, or a slash ( / ).




System actionThe input item being processed and the remainder ofthe items in the input item list are undefined. If neitherthe ERR nor the IOSTAT specifier is present on the I/Ostatement, the condition is signaled. If the condition isunhandled, the application is terminated.


No.

Name Input/Outpu

t

Data Type andLength

Value

5 input-field- desc


6 input-field Input CHARACTER*n Formatted inputdata; that is, thecharacter stringthat is beinginterpreted eitheras a charactervalue or as acomplex number.The length nis part of input-

No.

Name Input/Outpu

t

Data Type andLength

Value

field-desc andhas a maximumpossible value of255.

7 record-desc


8 record Input CHARACTER*n Formattedinput recordthat containedthe characterconstant with nodelimiter. Thelength n, whichincludes only thedata portion of therecord, is part ofrecord-desc.


RN The remainder of the input item list is ignored, andexecution continues.

Programmer responseEnsure that input-field is followed by a value separator.


FOR1010S locator-text A character thatwasn't a binary character wasfound in the formatted input datawhere a binary character wasexpected. The input field was'input-field'.

ExplanationFor a READ statement, input-field is a character stringthat was interpreted as binary data because there wasa B edit descriptor in the format specification. Binarydata consists of the characters 0 and 1, but input-fieldcontained other characters.







No.

Name Input/Outpu

t

Data Type andLength

Value

5 input-field-desc


6 input-field

Input/Output

CHARACTER*n Formatted inputdata; that is, thecharacter stringthat is beinginterpreted asa binary value.The length nis part of input-field-desc andhas a maximumpossible value of255.

7 index Input INTEGER*4 The index ininput_ field of thecharacter in error.

8 record-desc


9 record Input CHARACTER*n Formatted inputrecord thatcontained thecharacter stringbeing interpretedas a binary value.The length n,which includesonly the dataportion of therecord, is part ofrecord-desc.

10 result-desc


No.

Name Input/Outpu

t

Data Type andLength

Value

11 result output See result-desc Result value thatis used when therelease_optionaction isrequested by theuser conditionhandler.



RI Character string that is in input-field (whose lengthis part of input-field-desc) is converted to a binaryvalue, and the input item becomes defined with thisvalue. Execution continues, and the remainder of theinput item list is processed.

release-option

Input item becomes defined with the value result.


• input-field contains formatted data that can beconverted to binary data,

• The edit descriptor does not indicate binary inputwhere other input should be indicated,



FOR1011S locator-text A character thatwasn't an octal character wasfound in the formatted input datawhere an octal character wasexpected. The input field was'input-field'.

ExplanationFor a READ statement, input-field is a character stringthat was interpreted as octal data because there wasan O edit descriptor in the format specification. Octaldata consists of the characters 0 through 7, but input-field contained other characters.







No.

Name Input/Output

Data Type andLength

Value

5 input-field-desc


6 input-field

Input/Output

CHARACTER*n Formatted inputdata, that is, thecharacter stringthat is beinginterpreted asan octal value.The length nis part of input-field-desc andhas a maximumpossible value of255.


8 record-desc


9 record Input CHARACTER*n Formatted inputrecord thatcontained thecharacter stringbeing interpretedas an octal value.The length n,which includesonly the dataportion of therecord, is part ofrecord-desc.

10 result-desc


11 result Output See result-desc Result value thatis used when the

No.

Name Input/Output

Data Type andLength

Value

release_optionaction isrequested by theuser conditionhandler.


RI Character string that is in input-field (whose lengthis part of input-field-desc) is converted to a binaryvalue, and the input item becomes defined with thisvalue. Execution continues, and the remainder ofthe input item list is processed.

release-option

Input item becomes defined with the value result.


• input-field contains formatted data that can beconverted to octal data,

• The edit descriptor does not indicate octal inputwhere other input should be indicated.



FOR1020S The statement statement forsequential access for unit unit-number, which was connected tofile-name, failed. The file had beenconnected for access access. VSFORTRAN Version 2 Error Number:AFB163I, AFB231I (format 1)

System actionIf neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. If thecondition is unhandled, the application is terminated.

Qualifying Data: Only the basic set of four qualifyingdata for I/O conditions as shown in Table 1 on page272. Within this basic set, parm_count has a value of 4.



Programmer responseEnsure that you use only the I/O statements that areconsistent with the access mode in use for the fileconnection. For example, if you intend to use directaccess, then don't use the file positioning statements


(BACKSPACE, ENDFILE, REWIND). Instead, use onlyREAD or WRITE statements with a REC specifier; thevalue given for the REC specifier is the number of therecord that you want to read or write.

If you want to read the file sequentially, then you mustconnect the file for sequential access by executing anOPEN statement in which the access specifier has avalue of SEQUENTIAL (or in which the access specifieris omitted). If the file was already connected for directaccess and you want to process it with sequentialaccess, then you must execute a CLOSE statementbefore the OPEN statement.


FOR1022S The statement statement for unitunit-number, which was connectedto file-name, failed. The filewas already positioned afterthe endfile record. VS FORTRANVersion 2 Error Number: AFB101I,AFB218I (format 8)

ExplanationThe file was positioned after the endfile record eitherbecause the end-of-file condition was just detected fora READ statement or because you just executed anENDFILE statement. Your statement statement impliedthe use of a subsequent subfile, but your file did nothave multiple subfiles because it was a dynamicallyallocated scratch file, a named file, or a striped file.




RN The I/O operation is ignored, and execution continues.

Programmer responseDo not try to read or write records beyond theendfile record for the files that don't support multiplesubfiles. The only files that can have multiple subfilesare unnamed files that are neither striped files nordynamically allocated.

Check the logic of your program to ensure that youhaven't inadvertently executed a READ or WRITE

statement either after reaching the end of the file orafter executing an ENDFILE statement. Use the ENDspecifier, if necessary, to detect the end of the file.

If you want to extend an existing file after readingthrough the data records and detecting the end ofthe file, you can do so by executing a BACKSPACEstatement (which positions the file just beyond thelast data record and just before the endfile record)followed by WRITE statements.


FOR1023S The statement statement for unitunit, which was connected to file-name, failed. The file definitionstatement referred to a file on adevice or with a file organizationfor which the statement statementis not supported. VS FORTRANVersion 2 Error Number: AFB095I(format 1), AFB166

ExplanationYour program executed a statement statement, but thefile to which the unit is connected doesn't support thisstatement. For example, the following statements areinconsistent with the types of files indicated:BACKSPACE

PrinterBACKSPACE

Striped fileENDFILE

PDS memberREWIND

Language Environment message file





Programmer responseEither


• Change the logic of your program to avoid the use ofthe prohibited I/O statements for the file that you'reusing, or

• Change the file definition (DD statement, ALLOCATEcommand) to refer to a different type of file, andmaintain the data in that other type of file.


FOR1024S The BACKSPACE statement forunit unit-number, which wasconnected to file-name, failed. Thefile definition statement refersto a PDS member and theprevious statement was a WRITEstatement. VS FORTRAN Version 2Error Number: AFB095I (format 2)


Qualifying Data: Only the basic set of four qualifyingdata for I/O conditions as shown in Table 1 on page272. Within this basic set, statement has a value ofBACKSPACE, and parm_count has a value of 4.



Programmer responseBecause the sequence of a WRITE statement followedby a BACKSPACE statement isn't allowed for a file thatis a PDS member, make or both of these changes:

• Modify the program so it doesn't use this sequenceof statements.



FOR1025S The BACKSPACE statement forunit unit-number, which wasconnected to file-name, failed. Thefile definition statement referredto a PDS member, and BUFNOhad a value greater than 1. VSFORTRAN Version 2 Error Number:AFB095I (format 2)


Qualifying Data: Only the basic set of four qualifyingdata for I/O conditions as shown in Table 1 on page272. Within this basic set, statement has a value ofBACKSPACE, and parm_count has a value of 4.



Programmer responseBecause the BACKSPACE statement isn't allowed witha file that is a PDS member and that is processedwith more than one buffer, make one or more of thesechanges:

• Modify the program so it does not use a BACKSPACEstatement.


• Change the file definition statement either byremoving the BUFNO parameter that has a valuegreater than 1 or by providing a BUFNO=1parameter.

• For a dynamically allocated file that has anassociated call to the FILEINF callable service, eitherremove the BUFNO parameter that has a valuegreater than 1 or provide a a BUFNO parameter withan associated value of 1.


FOR1026S The statement statement forunit unit-number, which wasconnected to file-name, failed.The file definition statementreferred to a PDS member,and statement statement nor aREWIND statement. VS FORTRANVersion 2 Error Number: AFB123I(format 6), AFB123I (format 7)

ExplanationThe sequence of I/O statements that was executed fora file that was a PDS member caused a change eitherfrom input to output processing or from output to inputprocessing without an intervening REWIND statement.






Programmer responseChange the logic of the program to avoid switchingbetween input and output processing.

If you must do both input and output processing onthe file, either

• Insert an intervening REWIND statement (or aCLOSE followed by an OPEN statement) between thetwo types of processing if the logic of the programand the desired file positioning allows it, or



FOR1027S The READ statement for unit unit-number, which was connectedto file-name, failed. The filedefinition statement referred toa system output (sysout) dataset. VS FORTRAN Version 2 ErrorNumber: AFB218I (format 3)


Qualifying Data: Only the basic set of four qualifyingdata for I/O conditions as shown in Table 1 on page272. Within this basic set, statement has a value ofREAD, and parm_count has a value of 4.



Programmer responseIf the file is supposed to be a system output dataset (SYSOUT parameter on the DD statement), thenchange the logic of your program so that you don'texecute a READ statement for a unit that's connectedto this file.

If the file should be another type, then change thefile definition (DD statement, ALLOCATE command) torefer to the file that you intend to use.


FOR1028S The statement statement forunit unit-number, failed. The filewas already positioned after theendfile record of the 999th subfile,which is the last subfile allowed.

ExplanationYour program has already processed 999 subfilesand is trying to position itself into the next one;however, 999 is the maximum number of subfiles thatcan be handled. Note that each subsequent subfileis referenced when you execute a READ, WRITE,or ENDFILE statement either after the end-of-filecondition was just detected for a READ statement orafter you just executed an ENDFILE statement.

System actionThe file is closed. If neither the ERR nor theIOSTAT specifier is present on the I/O statement, thecondition is signaled. If the condition is unhandled, theapplication is terminated.

Qualifying Data: Only the basic set of four qualifyingdata for I/O conditions as shown in Table 1 on page272. Within this basic set, and parm_count has a valueof 4.



Programmer responseEnsure that your program doesn't inadvertentlyexecute a READ, WRITE, or ENDFILE statement forthe same unit either after reaching the end of thefile or after executing an ENDFILE statement. Use theEND specifier, if necessary, on the READ statement todetect the end of the file.

If you want to extend an existing file after readingthrough the data records and detecting the end of


the file, you can do so by executing a BACKSPACEstatement (which positions the file just beyond thelast data record and just before the endfile record)followed by WRITE statements


FOR1070S The direct access statementstatement for unit unit-number,which was connected to file-name, failed. The REC specifierhad a value of record-number,which either was not positiveor exceeded num-records, thenumber of records in the file. VSFORTRAN Version 2 Error Number:AFB232I

System actionIf neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled.

Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, parm_count has a value of 6. Inaddition, there are these qualifying data:


Data Type andLength

Value

5 record-number

Input INTEGER*4 Invalid recordnumber that wasgiven in the RECspecifier.

6 num-records

Input INTEGER*4 Number of recordsfor which there isspace within thefile.



RN The remainder of the input item is ignored, and executioncontinues.

Programmer responseEnsure that the REC specifier on the direct accessREAD or WRITE statement has a value that is neitherless than 1 or greater than the number of records inthe file.

If you're sure that the file contains the correct numberof records, then just correct the logic of your programto provide the correct value for the REC specifier.

If you expect the file to contain more records than itdoes, then you'll have to delete the existing file and

create it again to give it additional space. In this case,the term delete means that the data set's disk spacemust be released and the data set allocated again.Note that unless the file is dynamically allocated,neither of the following release the data set's existingspace on the disk volume:

• A CLOSE statement with a STATUS specifier value ofDELETE or

• An OPEN statement with a STATUS specifier value ofREPLACE.

However, if the file is dynamically allocated, you canuse these forms of the OPEN and CLOSE statements torelease the space from within your Fortran program.

For a non-VSAM file, you should indicate the amount ofspace in the file by one of the following:

• In MVS JCL: the SPACE parameter on the DDstatement

• In the TSO ALLOCATE command: the SPACE operandalong with the BLOCK, TRACKS, or CYLINDERSoperand

• In the FILEINF argument list for a dynamicallyallocated file: the CYL, TRK, or MAXREC keywordargument

For a VSAM relative record data set (RRDS), youshould indicate the amount of space on the AccessMethod Services DEFINE CLUSTER command with theCYLINDERS, RECORDS, or TRACKS parameter.

When the new file is first connected with a FortranOPEN statement whose ACCESS specifier has a valueof DIRECT, it is automatically formatted with as manyrecords as will fit in the space allocated to the dataset. (However, when the DEFINE FILE statement fromthe FORTRAN 66 language standard is used, onlythe number of records specified in that statement isformatted.)

Alternatively, you can format a newly created file byusing sequential access rather than direct access. Inthis case, simply write as many records as the file issupposed to to hold, then close the file, and reconnectit for direct access. Remember that a file connected fordirect access must have a record format that indicatesfixed-length unblocked records and a record lengththat is the same as the value of the RECL specifieron the OPEN statement that's used to connect the filefor direct access. Therefore, if you're using sequentialaccess to format the file, ensure that the record formatand record length are correctly specified in the DDstatement, in the TSO ALLOCATE command, or in thethe arguments for the FILEINF callable service.



FOR1071S The direct access statementstatement for unit unit-number,which was connected to file-name, failed. The file had beenconnected for access access. VSFORTRAN Version 2 Error Number:AFB235I

ExplanationYour program executed a statement statement witha REC specifier, which indicates direct access, butthe file was connected for access rather than directaccess.


Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, parm_count has a value of 4.



Programmer responseEnsure that you use only the I/O statements thatare consistent with the access mode in use for thefile connection. For example, if you intend to usesequential access, then don't use READ or WRITEstatements with a REC specifier because these applyonly to direct access.

If you want to read the file using direct access, thenconnect the file by executing an OPEN statement inwhich the access specifier has a value of DIRECT.(In a program that uses the FORTRAN 66 languagestandard, the DEFINE FILE statement has a functionsimilar to the OPEN statement.)


FOR1072S The direct access READ statementfor unit unit-number, which wasconnected to file-name, failed.The file was empty. VS FORTRANVersion 2 Error Number: AFB236I(format 1)


Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of READ,and parm_count has a value of 4.



Programmer responseEnsure that whatever program created the file actuallywrote records into the file. The three most commonways of writing these records are:

• Using the OPEN statement with a value of DIRECTfor the ACCESS specifier when the file doesn't yetexist. If the OPEN statement does not have either:

– A STATUS specifier with a value of OLD, or– An ACTION specifier with a value of READ.

then during execution of the OPEN statement thefile should be formatted automatically with as manyrecords as it can hold.

• Using sequential access to write the records. Inthis case, simply write as many records as the fileis supposed to to hold, then close the file, andreconnect it for direct access. Remember that afile connected for direct access must have a recordformat that indicates fixed-length unblocked recordsand a record length that is the same as the valueof the RECL specifier on the OPEN statement that'sused to connect the file for direct access. Therefore,if you're using sequential access to format the file,ensure that the record format and record length arecorrectly specified in the DD statement, in the TSOALLOCATE command, or in the the arguments for theFILEINF callable service.

• Using a utility program or a program written in someother language. If the file is to be used with directaccess by a Fortran, it must have a record formatthat indicates fixed-length unblocked records and arecord length that is the same as the value of theRECL specifier on the Fortran OPEN statement thatwill be used to connect the file for direct access.


FOR1100S The REWRITE statement for unitunit-number, which was connected


to file-name, failed. The key ofreference had a value of new-rec-key (X'new-rec-key-hex'), whichwas different from orig-rec-key(X'orig-rec-key-hex'), the value ofthat key in the record that wasread. The key of reference had aKEYID value of keyid. VS FORTRANVersion 2 Error Number: AFB139I

ExplanationYou read a record and, in trying to rewrite it, provideda record in your output item with a key of referencewhose value differed from that in the original record.You cannot use the REWRITE statement to replace arecord if you change the value of the key of reference.

The term key of reference means the key (that is,certain positions within the record) that was used forthe sequential or direct retrieval of the record that wasread. The term keyid means the relative position of thestart-end pair for this key within the start-end pairslisted in the KEYS specifier on the OPEN statement.


Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page272. Within this basic set, statement has a valueof REWRITE, and parm_count has a value of 6. Inaddition, there are these qualifying data:

No.

Name Input/

Output

Data Type andLength

Value

5 record-desc


6 record Input CHARACTER*n The record. Thelength n is part ofrecord-desc.



Programmer responseIf you intended to replace an existing record ratherthan to write one with a modified key value, ensurethat:

• The value of the key in the output item list is thesame as what was just read and that it is in thecorrect position in the record,

• The output item list contains all the fields of therecord to be rewritten, and

• Any changes in the order or length of various fieldsin the record have not caused the value of the keyof reference within the record to be shifted from itsoriginal position.

If you want to replace the record with one havinga different key value, use the DELETE statement todelete the record that was read, and then

• If there isn't already a record in the file with thedifferent key value, then use the WRITE statement,rather than the REWRITE statement, to add therecord with a new key value.

• If there is already a record in the file with thedifferent key value, then use the READ statementto read that record, and then use the REWRITEstatement to replace that record.

If you want to add a new record with a key value thatdoesn't already exist in the file, then use the WRITEstatement to add it.


FOR1102S The WRITE statement for unit unit-number, which was connected tofile-name, failed. Records werebeing loaded into the file, and theprimary key had a value of new-key (X'new-key-hex'), which wasnot greater than prev-key (X'prev-key-hex'), the value of the primarykey in the previous record. VSFORTRAN Version 2 Error Number:AFB140I

ExplanationBecause the OPEN statement for this file connectionhad a value of WRITE for the ACTION specifier, the filewas connected for use in loading records in order ofascending primary key value. You attempted to loada record in which the value of the primary key wasnot greater than the value of the primary key in theprevious record. The term primary key refers to themain key for the VSAM key-sequenced data set as itwas declared in the Access Method Services DEFINECLUSTER command.



Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of WRITE,and parm_count has a value of 6. In addition, there arethese qualifying data:


Data Type andLength

Value

5 record-desc





Programmer responseEnsure that your output item list has the primary keyat its proper position within the record being written. Ifyou're not sure where this key is located in the record,use the Access Method Services LISTCAT commandto find out. Then change your output item list (andthe KEYS specifier, if present, on the OPEN statement)so that it is consistent with the primary key positionknown to VSAM. On the other hand, if the output ofthe LISTCAT command shows the key in a differentposition than you intended, then delete and redefinethe file with the Access Method Services DELETE andDEFINE CLUSTER commands.

Change the logic of your program or the order of therecords being loaded so that the records are presentedin increasing sequence of their primary key values.

If you cannot present the records in increasing keysequence, then on the OPEN statement change thevalue of the ACTION specifier to READWRITE. Thisallows records to be added to the file without regardfor the order of their keys.


FOR1103S The statement statement for unitunit-number, which was connectedto file-name, failed. The previous

I/O statement for this unitresulted in a condition that causedthe loss of position in the file. VSFORTRAN Version 2 Error Number:AFB123I (format 1), AFB123I(format 2), AFB123I (format 3),AFB123I (format 4), AFB123I(format 5)

ExplanationThe statement statement was not allowed for either orboth of these reasons:

• It depended on a previous statement to establish orretain a position (or record pointer) within the file.

• The execution of a previous statement caused theloss of position in the file. This file position couldhave been lost because of any of a number ofconditions:

– Record-not-found condition– Duplicate-key condition– End-of-file condition– Any error condition

You can neither read records sequentially nor use aBACKSPACE statement until you have reestablishedfile position. In addition, you cannot use a DELETE,or REWRITE statement except immediately aftersuccessfully reading a record.





Programmer responseEnsure that a BACKSPACE statement or a sequentialretrieval READ statement isn't executed until aposition has been established within the file. Thisposition can be established by a successfully executedOPEN, REWIND, or direct retrieval READ statement.

Ensure that a DELETE or REWRITE statement isn'texecuted unless a record has just been read.



FOR1104S The READ statement for unit unit-number, which was connectedto file-name, failed. The KEYIDspecifier had a value of keyid,which conflicted with num-keys,the number of keys specified inthe KEYS specifier on the OPENstatement. VS FORTRAN Version 2Error Number: AFB124I

ExplanationThe value of the KEYID specifier on the OPENstatement is either less than 1 or greater than thenumber of start-end pairs in the KEYS specifier.Therefore, no pair (and hence no key) can beassociated with the value of the KEYID specifier.

This conflict can arise even if no KEYS specifier iscoded: a default of one key is assumed, so if keyid hasa value greater than 1, an error is detected.





Programmer responseIf the KEYS specifier on the OPEN statementaccurately indicates the keys that you want to use,then change the value of the KEYID specifier so that itis a positive integer that is no larger than the numberof start-end pairs in the KEYS specifier. Its valueshould be the ordinal number of the start-end pair forthe key that you want to use.

If you intended to have additional keys available foruse, then specify their starting and ending recordpositions as start-end pairs in the KEYS specifieron the OPEN statement. In addition, provide thefile definitions (DD statements or TSO ALLOCATEcommands) to refer VSAM paths for the additionalkeys.


FOR1106S The READ statement for unit unit-number, which was connected tofile-name, failed. The argument tobe used in searching for a key hada length of arg-length, which wasgreater than key-length, the lengthof the key on which the search isbeing made. The KEYID value waskeyid. VS FORTRAN Version 2 ErrorNumber: AFB125I

ExplanationThe argument to be used in searching for a key wasgiven in the KEY, KEYGE, or KEYGT specifier of a READstatement. However, the length of this argument isgreater than the length of the key of reference.

The term key of reference means the key (that is,certain positions within the record) that was used forthe direct retrieval of the record that was to be read.The key of reference is indicated by the keyid, whichis the relative position of the start-end pair for this keywithin the start-end pairs listed in the KEYS specifieron the OPEN statement. The key of reference can beestablished through the KEYID specifier on a directretrieval READ statement and remains in effect until itis changed in another direct retrieval READ statement.The keyid value is 1 if it has not been specified sincethe file was connected.



No.

Name Input/Output

Data Type andLength

Value

5 key-desc

Input Q_DATA_DESC The q_datadescriptor for key.It contains the datatype and the lengthof key.


No.

Name Input/Output

Data Type andLength

Value

6 key Input See key-desc Value of the keyargument. The datatype can be integerof length 1, 2, 4,or 8, or it can becharacter with anypositive length notexceeding 255.

7 keyid Input INTEGER*4 Value of the KEYIDspecifier.



Programmer responseProvide a search argument in the KEY, KEYGE, orKEYGT specifier whose length does not exceed thatof the key of reference. If you want to search with adifferent key of reference, then for the KEYID specifierspecify the ordinal number of the desired key's start-end pair in the KEYS specifier on the OPEN statement.


FOR1107S No record with the specified keycould be found for the keyedaccess READ statement for unitunit-number, which was connectedto file-name. The key specifier hada value of value (X'hex-value'). TheKEYID value was keyid (start:end).VS FORTRAN Version 2 ErrorNumber: AFB126I

ExplanationFor the key of reference there was no record in the filemeeting the search criterion indicated by the searchargument in the KEY, KEYGE, or KEYGT specifier on theREAD statement. This is the record not found conditionand might not be an error.

The term key of reference means the key (that is,certain positions within the record) that was used forthe direct retrieval of the record that was to be read.The key of reference is indicated by the keyid, whichis the relative position of the start-end pair for this keywithin the start-end pairs listed in the KEYS specifieron the OPEN statement. The key of reference can beestablished through the KEYID specifier on a directretrieval READ statement and remains in effect until itis changed in another direct retrieval READ statement.

The KEYID value is 1 if it has not been specified sincethe file was connected.

System actionIf the IOSTAT=ios specifier is present on the READstatement, ios becomes defined either with the value1107 if ios is an integer variable or with the conditiontoken for FOR1107 if ios is a character variable oflength 12.

If the NOTFOUND=nfd specifier is present on theREAD statement, control passes to the label nfd. Ifthe NOTFOUND specifier is not present on the READstatement but the ERR=err specifier is present, controlpasses to the label err.

If neither the ERR, the NOTFOUND, nor the IOSTATspecifier is present on the READ statement, thecondition is signaled. If the condition is unhandled, theapplication is terminated.


No. Name Input/Outpu

t

Data Type andLength

Value

5 key-desc Input Q_DATA_DESC The q_datadescriptor for key.It contains thedata type and thelength of key.

6 key Input See key-desc Value of the keyargument. Thedata type can beinteger of length1, 2, 4, or 8,or it can becharacter with anypositive length notexceeding 255.

7 keyid Input INTEGER*4 Value of the KEYIDspecifier.



Programmer responseEnsure that the KEYID value on this or an a previouslyexecuted READ statement represents the desired keyof reference.

Check the value of the KEY, KEYGE, or KEYGT specifierto ensure that it provides the desired search argument.


Check the program and the data that was used tocreate the file to ensure that the expected records areactually in the file.

If you want your program to get control in the eventof a record not found condition, then on the READstatement add a NOTFOUND specifier with the labelof the statement to be given control should the recordnot found condition occur.


FOR1112S The statement statement for unitunit-number, which was connectedto file-name, failed. The recordbeing written had a length oflength, which was too short tocontain all the keys. VS FORTRANVersion 2 Error Number: AFB129I(format 1), AFB129I (format 2)

ExplanationThe record described by the output item list on thestatement statement wasn't long enough to containall of the keys that were defined for the file throughAccess Method Services. The record being writtenmust be long enough to contain all of these keys evenif one or more of the keys wasn't listed as a start-endpair in the KEYS specifier of the OPEN statement.


Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, parm_count has a value of 6. Inaddition, there are these qualifying data:

No. Name Input/Outpu

t

Data Type andLength

Value

5 record-desc


6 record Input CHARACTER*n The record. Thelength n is part ofrecord_desc.



Programmer responseEnsure that the output item list defines a recordlong enough to contain all of the keys made knownto VSAM through the DEFINE CLUSTER, DEFINEALTERNATE INDEX, and DEFINE PATH commands forAccess Method Services. Use the LISTCAT command ifnecessary to determine the position of these keys.

Remember that with a REWRITE statement the outputitem list must provide output items that describe thewhole record rather than just the portions that are tobe rewritten.


FOR1113S The statement statement for unitunit-number, which was connectedto file-name, failed. The file hadbeen connected for access access,and the statement statement wasof a form that applies to keyedaccess. VS FORTRAN Version 2Error Number: AFB127I, AFB128I

ExplanationOne of the following specifiers was given on thestatement statement:

• KEY• KEYGE• KEYGT• NOTFOUND• DUPKEY• KEYID

These specifiers are applicable only to files connectedfor keyed access, but the file connection was foraccess access.






Programmer responseIf your file is a VSAM key-sequenced data set (KSDS),then provide a value of KEYED for the ACCESS specifieron the OPEN statement. This will allow you to use I/Ostatements that apply to keyed access.

If your file is not a VSAM KSDS, then you cannot usekeyed access nor can you use I/O statements thatapply only to keyed access. In this case, you have twochoices:

• Change the logic of your program to use only thestatements that apply to sequential or direct access.

• Define or redefine the file using Access MethodServices to make it a VSAM KSDS. Then you canconnect the file for keyed access and use any of theI/O statements that apply to keyed access.

Do not confuse sequential or direct access withsequential or direct retrieval statements. Sequentialand direct access are indicated by the ACCESSspecifier on the OPEN statement. Sequential anddirect retrieval statements are forms of the READstatement that can be used when the file is connectedfor keyed access, that is, when the ACCESS specifieron the OPEN statement has a value of KEYED.


FOR1114S The WRITE statement for unitunit-number, which was connectedto file-name, failed. A key valuewithin the record to be writtenwas a duplicate of a key in arecord already in the file. Thekey of reference had a positionof start : end in the record, ahexadecimal value of value, anda KEYID of keyid. VS FORTRANVersion 2 Error Number: AFB135I

ExplanationA WRITE statement that was used with a file thatwas connected for keyed access provided in its outputitem list a record with a key whose value was thesame as one that was already in the file. The duplicatekey value was either for the primary key, which neverallows duplicate key values, or for an alternate-indexkey that does not allow duplicate values because itwas defined to be unique through the Access MethodServices DEFINE ALTERNATEINDEX command. Thekey whose value is duplicated is not necessarily thekey of reference, which is indicated in the messagetext, and it isn't even necessarily among the keys listedin the KEYS specifier of the OPEN statement for the

file. However, the key is one that was defined using theAccess Method Services DEFINE CLUSTER or DEFINEALTERNATE INDEX command.

This is the duplicate key condition and might not be anerror.

(The term key of reference means the key (that is,certain positions within the record) that is currentlyin use for reading and writing records. The key ofreference is indicated by the keyid, which is therelative position of the start-end pair for this keywithin the start-end pairs listed in the KEYS specifieron the OPEN statement. The key of reference can beestablished through the KEYID specifier on a directretrieval READ statement and remains in effect until itis changed in another direct retrieval READ statement.The keyid value is 1 if it has not been specified sincethe file was connected.)

System actionIf the IOSTAT=ios specifier is present on the I/Ostatement, ios becomes defined either with the value1114 if ios is an integer variable or with the conditiontoken for FOR1114 if ios is a character variable oflength 12.

If the DUPKEY=dky specifier is present on the I/Ostatement, control passes to the label dky. If theDUPKEY specifier is not present on the I/O statementbut the ERR=err specifier is present, control passes tothe label err.

If neither ERR, the DUPKEY, nor the IOSTAT specifieris present on the I/O statement, the condition issignaled. If the condition is unhandled, the applicationis terminated.

Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of WRITE,and parm_count has a value of 6. In addition, there arethese qualifying data:

No.

Name Input/Output

Data Type andLength

Value

5 record-desc






Programmer responseEnsure that the output item list defines a record suchthat no key positions have values that are the same asvalues that are already in the file. This applies both tothe primary key and to all alternate index keys whosevalues are supposed to be unique. Carefully check therecord to be sure that it is in the intended format.

Remember that the key whose value has beenduplicated in your record might not be one thatyour program uses. You'll have to check all of thekeys made known to VSAM through the DEFINECLUSTER, DEFINE ALTERNATE INDEX, and DEFINEPATH commands for Access Method Services. Usethe LISTCAT command if necessary to determine theposition of these keys.

If you want your program to get control in the eventof a duplicate key condition, then on the WRITE orREWRITE statement add a DUPKEY specifier with thelabel of the statement to be given control should theduplicate key condition occur.


FOR1180S The formatted statementstatement for unit unit-number,which was connected to file-name,failed. The file was connectedfor unformatted I/O. VS FORTRANVersion 2 Error Number: AFB174I

ExplanationA formatted statement statement was executed for aunit that was connected for unformatted Input/Outputoperations.

A formatted I/O statement is a PRINT statement, or itis identified by the presence of an FMT specifier in theI/O statement's control list as follows:

• The presence of a FMT specifier with the FMTkeyword. For example:

READ (FMT=*, UNIT=8) AREAD (8, FMT=10) A

• The absence of the UNIT keyword in the unitspecifier and the presence of an immediatelyfollowing specifier that has no keyword. Forexample:

READ (8, NL1) AREAD (8, *) A

The file was connected for unformatted Input/Outputoperations because either:

• A value of UNFORMATTED was given for the FORMspecifier on the OPEN statement,

• The FORM specifier was omitted from the OPENstatement for a file that was connected for direct orkeyed access, or

• The first I/O statement that was executed fora preconnected file was an unformatted I/Ostatement, that is, an I/O statement with no FMTspecifier.






Programmer responseDetermine if you want to perform formatted orunformatted Input/Output operations on the file. Ifyou want to use unformatted I/O statements, removeor change the formatted I/O statements.

If you want to use formatted I/O statements, then:

• For an OPEN statement that connects a file forsequential access, either omit the FORM specifier orprovide one with a value of FORMATTED.

• For an OPEN statement that connects a file for director keyed access, provide a FORM specifier with avalue of FORMATTED.

• Do not execute an unformatted I/O statement for theunit.


FOR1181S locator-text A format specificationcontained an invalid editdescriptor of code. VS FORTRANVersion 2 Error Number: AFB211I

ExplanationA format specification referenced by the I/O statementcontained an edit descriptor (sometimes called aformat code) that was



• The statement statement for an internal file failed.• The statement statement for unit unit-number, which


System actionThe input or output item being processed and theremainder of the items in the Input/Output itemlist are undefined. If neither the ERR nor theIOSTAT specifier is present on the I/O statement, thecondition is signaled. If the condition is unhandled, theapplication is terminated.



RN The invalid edit descriptor is treated as the end of theformat specification, and execution continues.

Programmer responseIf the FMT specifier on the I/O statement referredto the format specification in a variable (rather thanas a constant or as a label of a FORMAT statement),ensure that the format specification was constructedaccording to the same rules that apply for a FORMATstatement. In particular, it must start with a leftparenthesis, end with a right parenthesis, have noimbedded blanks except within a pair of quotes orapostrophes, and use only the edit descriptors that areallowed by the Fortran language.

Ensure that the logic of your program didn'tinadvertently overlay storage such as by referring toarray elements outside the declared bounds of thearray.


FOR1182S locator-text A format specificationcontained more than 51 nestedparenthesis groups. VS FORTRANVersion 2 Error Number: AFB160I




RN The parenthesis group is ignored, and executioncontinues. The results are unpredictable.

Programmer responseIn your format specification, do not use more than 51levels of nesting for parenthesis groups.


FOR1183S locator-text The format specifieron the I/O statement did notrefer to a FORMAT statement. VSFORTRAN Version 2 Error Number:AFB211I

System actionThe input or output item being processed and theremainder of the items in the Input/Output itemlist are undefined. If neither the ERR nor theIOSTAT specifier is present on the I/O statement, thecondition is signaled. If the condition is unhandled, theapplication is terminated.



RN The format field is treated as an end of format, andexecution continues.

Programmer responseEnsure that the format specifier refers to a correctlystructured format specification. Either provide thelabel of a FORMAT statement or character expressionwhose value is a format specification.

Ensure that the logic of your program didn'tinadvertently overlay storage such as by referring toarray elements outside the declared bounds of thearray.


FOR1200S The unformatted statementstatement for unit unit-number,which was connected to file-name,failed. The file was connectedfor formatted I/O. VS FORTRANVersion 2 Error Number: AFB173I


ExplanationAn unformatted statement statement was executed fora unit that was connected for formatted Input/ Outputoperations.

An unformatted I/O statement is recognized by theabsence of an FMT specifier. For example, these areunformatted I/O statements:

WRITE (10) A, BREAD (7, END=88) A, B

These are formatted I/O statements:

WRITE (FMT=*, UNIT=8) AWRITE (8, FMT=*) AREAD (8, NL1) AREAD (8, *, END=77) APRINT 10, A, B, C

The file was connected for formatted Input/ Outputoperations because either:

• A value of FORMATTED was given for the FORMspecifier on the OPEN statement,

• The FORM specifier was omitted from the OPENstatement for a file that was connected forsequential access, or

• The first I/O statement that was executed for apreconnected file was a formatted I/O statement,that is, an I/O statement with an FMT specifier.



Name Action Taken sfter Resumption


Programmer responseDetermine if you want to perform formatted orunformatted Input/ Output operations on the file. Ifyou want to use formatted I/O statements, remove orchange the unformatted I/O statements.

If you want to use unformatted I/O statements, then:

• For an OPEN statement that connects a file forsequential access, provide a FORM specifier with avalue of UNFORMATTED.

• For an OPEN statement that connects a file for director keyed access, either omit the FORM specifier orprovide one with a value of UNFORMATTED.

• Do not execute a formatted I/O statement for theunit.


FOR1201S The unformatted READ statementfor unit unit-number, which wasconnected to file-name, failed. Thefile definition statement referredto an ASCII tape. VS FORTRANVersion 2 Error Number: AFB214I

ExplanationAn unformatted READ statement referred to a unitthat was connected to a file whose DCB informationindicated variable-length ASCII tape records. TheseASCII tape records are indicated by a RECFM value ofD.





Programmer responseIf you have an ASCII tape to be read, then change yourprogram to use formatted rather than unformattedREAD statements.

If your input file is not an ASCII tape, then ensure thatyou provide DCB information that does not include avalue of D for the RECFM parameter.


FOR1210S locator-text There was an invalidrepeat specification in a recordbeing read with list-directedformatting. VS FORTRAN Version 2Error Number: AFB227I


ExplanationAn input field in a record that was read with a list-directed READ statement had the form n*value, wheren, which is the repeat specification, should be aninteger constant and value should be the value to beassigned to n successive variables or array elementsin the input item list. However, there was an error inthe format of n*value. Possible errors might includean incorrect integer value for the repeat specification,a second asterisk, or an invalid value following theasterisk.







Data Type andLength

Value

5 record-desc

Input Q_DATA_DESC The q_datadescriptor forrecord; containsthe data type andthe length ofrecord.

6 record Input CHARACTER*n Formatted inputrecord thatcontained theinvalid repeatspecification.The length n,which includesonly the dataportion of therecord, is part ofrecord-desc.


Data Type andLength

Value

1 parm-count

Input INTEGER*4 3

2 subroutine- name

Input CHARACTER*8 Name of DIVsubroutine


Data Type andLength

Value

3 return-code

Input INTEGER*4 Return codefrom FortranDIV subroutine




RN The I/O operation is not completed, and executioncontinues.

Programmer responseIn the record to be read, ensure that the repeatspecification and the constant following the asteriskare coded in the correct format.


FOR1220S locator-text In the namelist groupgroup-name in a namelist inputfile, a variable name or arrayname exceeded 31 characters inlength. The first 31 characterswere object-name. VS FORTRANVersion 2 Error Number: AFB221I




Data Type andLength

Value

5 group-name

Input CHARACTER*31 The namelistgroup name inthe namelistinput file.

6 object-name-desc

Input Q_DATA_DESC Theq_data_descriptor for object-name.It contains thedata type and thelength of object-name.



Data Type andLength

Value

7 object-name

Input CHARACTER*n Variable nameor array namethat was toolong in group-name in thenamelist inputfile. The length nis part of object-name-desc andhas a maximumpossible value of255.

8 record-desc

Input Q_DATA_DESC The q_datadescriptor forrecord. Itcontains the datatype and thelength of record.

9 record Input CHARACTER*n Formatted inputrecord thatcontained thename that wastoo long. Thelength n, whichincludes only thedata portion ofthe record, is partof record-desc.



Programmer responseEnsure that the variable names in the namelistgroup in the namelist input file are all listed in thecorresponding NAMELIST statement in the programand that the delimiters, such commas, equal signs,and quotes, are used as required.


FOR1221S locator-text In the namelist groupgroup-name in a namelist inputfile, the variable name or arrayname object-name was not in thenamelist group in the NAMELISTstatement. VS FORTRAN Version 2Error Number: AFB222I



No.

Name Input/Output

Data Type andLength

Value

5 group-name

Input CHARACTER*31 The namelist groupname in thenamelist input file.

6 object-name

Input CHARACTER*31 Variable nameor array namethat was notin group-namein the NAMELISTstatement.

7 record-desc


8 record Input CHARACTER*n Formatted inputrecord thatcontained thename that was notin the namelistgroup. The lengthn, which includesonly the dataportion of therecord, is part ofrecord-desc.

Name Action Taken After Resumption




FOR1222S locator-text In the namelist groupgroup-name in a namelist inputfile, there was a syntax errorinvolving the name object-name orits value. VS FORTRAN Version 2Error Number: AFB223I


System actionThe variable being processed and the remainder ofthe variables given in the namelist input file becomeundefined. If neither the ERR nor the IOSTAT specifieris present on the I/O statement, the condition issignaled. If the condition is unhandled, the applicationis terminated.



Data Type andLength

Value

5 group-name-desc

Input Q_DATA_DESC The q_datadescriptor forgroup-name. Itcontains the datatype and the lengthof group-name.

6 group-name

Input CHARACTER*n The namelist groupname in thenamelist input file.The length nis part of group-name-desc andhas a maximumpossible value of250.

7 object-name-desc

Input Q_DATA_DESC The q_datadescriptor forobject-name. Itcontains the datatype and the lengthof object-name.

8 object-name

Input CHARACTER*n Variable name orarray name thathad an incorrectvalue or syntaxin group-name inthe namelist inputfile. The length nis part of object-name-desc andhas a maximumpossible value of250.

9 record-desc


10 record Input CHARACTER*n Formatted inputrecord thatcontained thename that hadan incorrect valueor syntax. Thelength n, whichincludes only thedata portion of the


Data Type andLength

Value

record, is part ofrecord-desc.





FOR1223S locator-text In the namelist groupgroup-name in a namelist inputfile, a subscript for array object-name had the value subsc-val,which was not within the boundsfor that array. VS FORTRANVersion 2 Error Number: AFB224I



No.

Name Input/Output

Data Type andLength

Value

5 group-name


6 object-name

Input CHARACTER*31 Name of thearray that had anincorrect subscriptvalue in group-name in thenamelist input file.

7 record-desc



No.

Name Input/Output

Data Type andLength

Value

8 record Input CHARACTER*n Formatted inputrecord thatcontained thename of thearray that had anincorrect subscriptvalue. The lengthn, which includesonly the dataportion of therecord, is part ofrecord-desc.


RN The I/O operation is not complete, and executioncontinues.

Programmer responseEnsure that the subscript has a value that lies withinthe bounds of the array object-name. Either correct thesubscript or change the declaration of the array in theprogram.


FOR1224S locator-text In the namelist groupgroup-name in a namelist inputfile, object-name had a subscriptbut was not an array. VS FORTRANVersion 2 Error Number: AFB224I



No.

Name Input/Output

Data Type andLength

Value

5 group-name


6 object-name

Input CHARACTER*31 Name of thevariable that hada subscript ingroup-name in thenamelist input file.

7 record-desc

Input Q_DATA_DESC The q_datadescriptor forrecord. It contains

No.

Name Input/Output

Data Type andLength

Value

the data typeand the length ofrecord.

8 record Input CHARACTER*n Formatted inputrecord thatcontained thename of thevariable that hada subscript. Thelength n, whichincludes only thedata portion of therecord, is part ofrecord-desc.



Programmer responseCorrect the inconsistency between the use of object-name with a subscript in the namelist input file andthe declaration of object-name in the Fortran programas a scalar variable. Either remove the subscript inthe namelist input file or correct the declaration in theprogram.


FOR1225W locator-text In a namelist inputfile, a namelist group nameor variable name exceeded max-length characters in length. Thefirst max-length characters werename. VS FORTRAN Version 2 ErrorNumber: AFB221I

System actionIf neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. If thecondition is unhandled, execution continues, and thename name is ignored.




Data Type andLength

Value

5 group-name-desc

Input Q_DATA_DESC The q_datadescriptor forgroup_name. Itcontains the datatype and thelength of group-name.

6 group-name

Input CHARACTER*n The namelistgroup name thatwas too longin group-name inthe namelist inputfile. The length nis part of group-name-desc andhas a maximumpossible value of255.

7 record-desc


8 record Input CHARACTER*n Formatted inputrecord thatcontained thename that wastoo long. Thelength n, whichincludes only thedata portion of therecord, is part ofrecord-desc.



Programmer responseEnsure that the namelist input file is coded inthe correct format with the information beginningin column 2 or later in the records. Check foran ampersand preceding the namelist group namewith no intervening spaces, and check for missingdelimiters, such as commas, quotes, or apostrophes.


FOR1226S locator-text There was an errorin the specification of a namein a name-value pair within thenamelist group group-name in thenamelist input file. (Description ofthe error that was detected.) VSFORTRAN Version 2 Error Number:AFB222I

ExplanationThe namelist group group-name in the namelist inputfile had an error involving one of the variable namesgiven in what should be a name-value pair. Thedetailed description of the error is in the message text.







Data Type andLength

Value

5 group-name-desc

Input Q_DATA_DESC Theq_data_descriptor for group-name.It contains thedata type and thelength of group-name.

6 group-name

Input CHARACTER*n The namelistgroup name thatcontained thevariable that wascoded in error.The length nis part of group-name-desc andhas a maximumpossible value of255.

7 record-desc




Data Type andLength

Value

8 record Input CHARACTER*n Formatted inputrecord thatcontained thename that wastoo long. Thelength n whichincludes only thedata portion ofthe record, is partof record_desc.



Programmer responseCorrect the incorrectly coded variable name in thenamelist input file or provide any missing delimiters.


FOR1227S locator-text Within the namelistgroup group-name in the namelistinput file the variable var-namewas not followed by an equalsign. VS FORTRAN Version 2 ErrorNumber: AFB222I

ExplanationThe namelist group group-name in the namelist inputfile contained the variable name var-name. However,this name was not immediately followed by the equalsign ( = ), which should separate the name and a value.





Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of READ,

and parm_count has a value of 10. In addition, thereare these qualifying data:

No.

Name Input/Output

Data Type andLength

Value

5 group-name-desc


6 group-name

Input CHARACTER*n The namelistgroup name thatcontained thevariable that wasn'tfollowed by anequal sign. Thelength n is part ofgroup-name-descand has a maximumpossible value of255.

7 var-name-desc

Input Q_DATA_DESC The q_datadescriptor for var-name. It containsthe data type andthe length of var-name.

8 var-name Input CHARACTER*n Name of thevariable that wasn'tfollowed by anequal sign. Thelength n, whichis part of var-name-desc, has amaximum possiblevalue of 255 evenif the variable nameis actually longer.

9 record-desc


10 record Input CHARACTER*n Formatted inputrecord thatcontained thename that wasn'tfollowed by anequal sign. Thelength n, whichincludes only thedata portion of therecord, is part ofrecord-desc.




Programmer responseCode the name-value pair in the form of the variablename followed by an equal sign followed by a value orvalues.


FOR1228S locator-text Within the namelistgroup group-name in the namelistinput file there were too manyvalues given for the variable var-name. VS FORTRAN Version 2 ErrorNumber: AFB222I

ExplanationThe namelist group group-name in the namelist inputfile contained the variable name var-name followed byan the equal sign ( = ), which separates the name andthe values. However, following that equal sign therewere more values than there were intrinsic data itemscomprising the variable. There were either:

• more values than there were elements in an arrayvariable,

• more values than there were intrinsic data itemswithin a variable of derived type, or

• more than one value for a scalar variable of anintrinsic data type.






No.

Name Input/Output

Data Type andLength

Value

5 group-name-desc

Input Q_DATA_DESC The q_datadescriptor forgroup-name. It

No.

Name Input/Output

Data Type andLength

Value

contains the datatype and the lengthof group-name.

6 group-name

Input CHARACTER*n The namelistgroup name thatcontained thevariable that hadtoo many values.The length nis part of group-name-desc andhas a maximumpossible value of255.

7 var-name-desc

Input Q_DATA_DESC The q_datadescriptor for var-name. It containsthe data type andthe length of var-name.

8 var-name

Input CHARACTER*n Name of thevariable that hadtoo many values.The length n, whichis part of var-name-desc, has amaximum possiblevalue of 255 even ifthe variable name isactually longer.

9 record-desc


10 record Input CHARACTER*n Formatted inputrecord thatcontained the valuethat exceededthe number ofallowable ones. Thelength n, whichincludes only thedata portion of therecord, is part ofrecord-desc.



Programmer responseCode the name-value pair in the form of the variablename followed by an equal sign followed by nomore values than comprise the variable. For example,a scalar variable of an intrinsic data type cannothave more than one value. If an assumed-shapeor deferred-shape array is involved, ensure that thenumber of values doesn't exceed the number ofelements represented by the current shape of the


array. If a variable of derived type is involved, ensurethat there aren't more values than there are intrinsicdata items within the derived type, and ensure that thevalues are of the proper type to correspond with theintrinsic data items.

If you intended for the extraneous value to beinterpreted as the next variable name rather than asa value, then code this variable name followed by anequal sign followed by this variable's value or values.


FOR1229S locator-text Within the namelistgroup group-name in the namelistinput file the character not-name-char was found instead of thebeginning of a variable name.

ExplanationIn the namelist group group-name in the namelistinput file, there wasn't a variable name at a placewhere a variable name should have been. Instead,there was the character not-name-char, which cannotbegin a variable name. This could have occurred atthe beginning of the namelist group. Alternatively,following some other variable and its values therecould have been some string of characters that wasn'trecognized either as a value or as another variablename.






No.

Name Input/Output

Data Type andLength

Value

5 group-name-desc


6 group-name

Input CHARACTER*n The namelist groupname that wastoo long in group-name in thenamelist input file.The length nis part of group-name-desc andhas a maximumpossible value of255.

7 record-desc


8 record Input CHARACTER*n Formatted inputrecord thatcontained thestring of charactersthat was expectedto be a variablename but wasn't inthe correct formatfor a name. Thelength n, whichincludes only thedata portion of therecord, is part ofrecord-desc.



Programmer responseCode the name-value pairs in the form of the variablename followed by an equal sign followed by no morevalues than comprise the variable. Be sure that eachvariable name is the name of a variable given forthe namelist group in the NAMELIST statement in theFortran program. Also be sure that the value or valuesare coded as literal constants rather than as namedconstants.


FOR1230S locator-text In the namelist groupgroup-name in a namelist inputfile, the value for the variableobject-name was not in the form


of a complex constant even thoughthe variable was of complex type.The formatted input data wasinput-field.

ExplanationFor a READ statement, input-field is a portion of thecharacter string that is being interpreted as a complexconstant for namelist input, and can be either thereal part, the imaginary part, or both. input-field eithercontained embedded blanks in the real part or theimaginary part of the complex number, did not containa comma as a separator between the real part and theimaginary part, or was not enclosed in parentheses.






No.

Name Input/Output

Data Type andLength

Value

5 group-name-desc

Input Q_DATA_DESC The q_datadescriptor forgroup_name. Itcontains the datatype and thelength of group-name.

6 group-name

Input CHARACTER*n The namelist groupname in thenamelist input file.The length nis part of group-name-desc.

7 object-name-desc

Input Q_DATA_DESC The q_datadescriptor forobject_name. Itcontains the datatype and thelength of group-name.

No.

Name Input/Output

Data Type andLength

Value

8 object-name

Input CHARACTER*n Name of thecomplex variablethat has anincorrect valuein group-name inthe namelist inputfile. The length nis part of object-name-desc.

9 record-desc


10 record Input CHARACTER*n Formatted inputrecord thatcontained thename of thearray that had anincorrect subscriptvalue. The lengthn, which includesonly the dataportion of therecord, is part ofrecord-desc.



Programmer responseEnsure that input-field contains no embedded blanksin the real part or the imaginary part of the complexnumber, contains a comma as a separator, is enclosedby a left and a right parenthesis, and, if the complexnumber does not fit into one record, that the end of therecord occurs between the real part and the comma orbetween the comma and the imaginary part.


FOR1231S locator-text In the namelist groupgroup-name in a namelist inputfile, the value for the variableobject-name was not a delimitedcharacter constant even thoughthe variable was of character type.The formatted input data wasinput-field.

ExplanationFor a READ statement, input-field is a portion of thecharacter string that is being interpreted as a character


constant for namelist input. It was not delimited byapostrophes ( ' ) or by quotes ( " ) as required fornamelist input.






No.

Name Input/Output

Data Type andLength

Value

5 group-name-desc

Input Q_DATA_DESC The q_datadescriptor forgroup-name. Itcontains the datatype and thelength of group-name.

6 group-name


7 object-name-desc

Input Q_DATA_DESC The q_datadescriptor forobject-name. Itcontains the datatype and thelength of object-name.

8 object-name

Input CHARACTER*n Name of thecharacter variablethat has a valuethat was notproperly delimitedin group-name inthe namelist inputfile. The length nis part of object-name-desc.

9 record-desc

Input Q_DATA_DESC The q_datadescriptor forrecord. It containsthe data type

No.

Name Input/Output

Data Type andLength

Value

and the length ofrecord.

10 record Input CHARACTER*n Formatted inputrecord thatcontained thevalue that was notproperly delimited.The length n,which includesonly the dataportion of therecord, is part ofrecord-desc.



Programmer responseEnsure that the character constant used as the valuefor the variable is delimited either by apostrophes ( ' )or by quotes ( " ).


FOR1232S locator-text In the namelist groupgroup-name in a namelist inputfile, the variable object-name wasa delimited character constantfor which there was no endingdelimiter. The character constantcontained or began with thecharacters input-field.

ExplanationFor a READ statement, input-field is a portion of thecharacter string that is being interpreted as a characterconstant for namelist input. It had a starting delimiterof either an apostrophe or a quote, but there wascorresponding ending delimiter before the end of thefile.




System actionThe variable being processed becomes undefined. Ifneither the ERR nor the IOSTAT specifier is present


on the I/O statement, the condition is signaled. If thecondition is unhandled, the application is terminated.


No.

Name Input/Output

Data Type andLength

Value

5 group-name-desc


6 group-name


7 object-name-desc


8 object-name

Input CHARACTER*n The name of thecharacter variablethat has a valuethat did not havean ending delimiterin group-name inthe namelist inputfile. The length nis part of object-name-desc.

9 record-desc


10 record Input CHARACTER*n Formatted inputrecord thatcontained thevalue that didnot have anending delimiter.The length n, whichincludes only thedata portion of therecord, is part ofrecord-desc.



Programmer responseEnsure that the character constant used as the valuefor the variable is delimited either by apostrophes( ' ) or by quotes ( " ). Both the starting and endingdelimiter must both be apostrophes or both be quotes.

Check for a doubled occurrence of the delimiterthat started the character constant. Such a doubleddelimiter is not interpreted as the ending delimiterbut rather as one occurrence of that delimiter as acharacter within the character constant. In this case,a single occurrence of the delimiter must follow toindicate the end of the character constant.


FOR1233S locator-text In the namelist groupgroup-name in a namelist inputfile, the variable object-name wasa delimited character constantwhose length, length, exceededmax-char-length, the maximumlength allowed for a characterconstant. The character constantbegan with the characters input-field.

ExplanationFor a READ statement, input-field is a portion ofthe character string that is being interpreted as acharacter constant for namelist input. This length ofthis constant, not counting the starting and endingdelimiters, was length, but this was longer than max-char-length, the product-imposed maximum lengthof a character constant that can be interpreted asnamelist input.





Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of READ,


and parm_count has a value of 10. In addition, thereare these qualifying data:

No.

Name Input/Output

Data Type andLength

Value

5 group-name-desc


6 group-name


7 object-name-desc


8 object-name

Input CHARACTER*n The name of thecharacter variablethat has a valuethat was too longin group-name inthe namelist inputfile. The length nis part of object-name-desc.

9 record-desc


10 record Input CHARACTER*n Formatted inputrecord thatcontained thevalue that wastoo long. Thelength n, whichincludes only thedata portion of therecord, is part ofrecord-desc.



Programmer responseEnsure that the character constant used as the valuefor the variable is delimited either by apostrophes( ' ) or by quotes ( " ). Both the starting and endingdelimiter must both be apostrophes or both be quotes.

Check for a doubled occurrence of the delimiterthat started the character constant. Such a doubleddelimiter is not interpreted as the ending delimiter

but rather as one occurrence of that delimiter as acharacter within the character constant. In this case,a single occurrence of the delimiter must follow toindicate the end of the character constant.


FOR1250S locator-text The file definitions forthe stripes of file-name did notdefine consistent characteristicsfor all the stripes. VS FORTRANVersion 2 Error Number: AFB092I

ExplanationA striped file, that is, one with ddnames of theform FTnnP001, FTnnP002, and so on, had differentcharacteristics given in its file definitions (DDstatements or ALLOCATE commands) or data setlabels for the different stripes. One or more of thefollowing parameters had different values among thestripes:

• RECFM• LRECL• BLKSIZE• BUFOFF• IN or OUT (fourth subparameter of the LABEL

parameter)• DISP




System actionIf the error occurred during the execution of an OPENstatement, the unit is not connected to a file. If neitherthe ERR nor the IOSTAT specifier is present on the I/Ostatement, the condition is signaled. If the condition isunhandled, the application is terminated.





Programmer responseEnsure that the file definitions for all of the stripeshave identical values for the parameters listed in“Explanation.” If an existing data set was used, be surethat the whatever was in the existing data set labeldoesn't cause this conflict; override such a conflictingvalue if necessary.


FOR1251S locator-text The file definitionstatements for the stripes of file-name had inconsistent ddnamesor data set names. VS FORTRANVersion 2 Error Number: AFB093I

ExplanationA striped file, that is, one with ddnames of the formFTnnP001, FTnnP002, and so on, had inconsistentddnames and data set names in one or more of its filedefinitions (DD statements or ALLOCATE commands).The inconsistency could be one of the following:

• A file definition for ddname FTnnPmmm did not referto a data set name that ends in the form xxxPyyy,where xxx is the number of stripes and yyy is aparticular stripe number.

• A file definition for ddname FTnnPmmm did refer toa data set name that ends in the form xxxPyyy, andeither:

– The stripe numbers mmm and yyy did not match,– The portion of the data set name other than the

stripe number, that is, other than the yyy, differedfrom that for other stripes, or

– The stripe number yyy and the maximum stripenumber xxx did not have the same number ofdigits.


• The statement statement for unit-number failed.• The INQUIRE statement failed.


Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.

Within this basic set, parm_count has a value of 4. Inaddition, there are these qualifying data:



Programmer responseAssuming that there are xxx stripes, ensure that:

• There are xxx file definitions and that thefile definitions have the ddnames FTnnP001,FTnnP002, ... FTnnPsss, where nn is the two-digitunit number and sss is the three-digit representationof the number of stripes (xxx),

• In the file definition with the ddname FTnnPmmm,the final characters of the end of the data set nameare xxxPyyy, where yyy is the stripe number, that is,yyy has the same numeric value as mmm,

• The number of digits in xxx is the same as thenumber of digits in each yyy, and

• All the data set names are identical except for thetrailing mmm.

Here is an example of DD statements for a striped filewith six stripes:

//FT10P001 DD DSN=MYNAME.MYFILE.ABC6P1,DISP=OLD//FT10P002 DD DSN=MYNAME.MYFILE.ABC6P2,DISP=OLD//FT10P003 DD DSN=MYNAME.MYFILE.ABC6P3,DISP=OLD//FT10P004 DD DSN=MYNAME.MYFILE.ABC6P4,DISP=OLD//FT10P005 DD DSN=MYNAME.MYFILE.ABC6P5,DISP=OLD//FT10P006 DD DSN=MYNAME.MYFILE.ABC6P6,DISP=OLD


FOR1252S locator-text A file definitionstatement for one of the stripes offile-name referred to a file type ordevice type that cannot be usedfor a striped file. VS FORTRANVersion 2 Error Number: AFB094I

ExplanationA file definition (DD statement or ALLOCATEcommand) for a striped file referred to a file on adevice that was neither a tape nor a non-VSAM diskfile other than a PDS member.


• The statement statement for unit-number failed.• The INQUIRE statement failed.






Programmer responseEnsure that for each of the stripes of a striped file thefile definition refers either to a tape or to a non-VSAMdisk file other than a PDS member.


FOR1270S The WAIT statement for unit unit-number, which was connected tofile-name, failed. There was nocorresponding READ or WRITEstatement. VS FORTRAN Version 2Error Number: AFB287I


Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of WAIT,and parm_count has a value of 4.


RN The WAIT statement is ignored, and execution continues.

Programmer responseEnsure that the program executes a WAIT statementonly after a corresponding asynchronous READ orWRITE statement.


FOR1271S The asynchronous statementstatement for unit unit-number,which was connected to file-name, failed. In the file

definition statement, the BLKSIZEparameter either was omitted orhad a value of 0. VS FORTRANVersion 2 Error Number: AFB239I





Programmer responseEnsure that for a new file the block size (BLKSIZEparameter in the DD statement or ALLOCATEcommand) has a nonzero value.


FOR1272S The asynchronous statementstatement for unit unit-number,which was connected to file-name,failed. The last array element inthe input item list had a lowersubscript value than the first. VSFORTRAN Version 2 Error Number:AFB228I





Programmer responseEnsure that the starting and ending elements in theinput/output item list are specified with the lower-valued subscript first. If the subscripts involve anvariable, ensure that the variables are set to theirintended values.



FOR1273S The asynchronous statementstatement for unit unit-number,which was connected to file-name,failed. The previous I/O statementfor this unit was neither a REWINDnor another asynchronous I/Ostatement. VS FORTRAN Version 2Error Number: AFB286I





Programmer responseIf you want to switch back and forth betweenasynchronous I/O statements and the sequential I/Ostatement defined by the Fortran language standard,then you must execute a REWIND statement eachtime you switch between the two. (Of course you canalso execute a CLOSE statement followed by an OPENstatement.) While positioned within a file, you cannotswitch between the two forms of I/O statements.If executing the REWIND statement doesn't providethe file positioning that your program requires, thenchange the program so that either asynchronous I/Ostatements or standard sequential I/O statements areused exclusively.


FOR1274S The statement statement, whichwas not of the asynchronous form,for unit unit-number, which wasconnected to file-name, failed.The previous asynchronous I/Ostatement was not followed by aREWIND statement. VS FORTRANVersion 2 Error Number: AFB286I





Programmer responseIf you want to switch back and forth betweenasynchronous I/O statements and the sequential I/Ostatements defined by the Fortran language standard,then execute a REWIND statement each time youswitch between the two. (Alternatively, you couldexecute a CLOSE statement followed by an OPENstatement.) While positioned within a file, you cannotswitch between the two forms of I/O statements.If executing the REWIND statement doesn't providethe file positioning that your program requires, thenchange the program so that either asynchronous I/Ostatements or standard sequential I/O statements areused exclusively.


FOR1275S There was no corresponding WAITstatement for an asynchronousstatement statement that wasexecuted for unit unit-number,which was connected to file-name.VS FORTRAN Version 2 ErrorNumber: AFB288I




RN Execution continues with an implied WAIT.

Programmer responseEnsure that the Fortran program executes a WAITstatement after each asynchronous READ or WRITEstatement.


FOR1276S The asynchronous statementstatement for unit unit-number,


which was connected to file-name, failed. The file definitionstatement referred to a file typeor device type that cannot beused for asynchronous I/O. VSFORTRAN Version 2 Error Number:AFB090I (format 2), AFB194I(format 1)

ExplanationAn asynchronous statement statement was executedfor unit unit, and one of the following was true:

• The file definition (DD statement or ALLOCATEstatement) for the ddname FTnnF001 referred to afile that was neither a tape nor an non-VSAM disk fileother than a PDS member.

• There was a file definition with the ddnameFTnnP001.




Programmer responseIf you want to use asynchronous I/O, then provide afile definition that refers to either a tape nor an non-VSAM disk file other than a PDS member. Also, do notprovide a file definition with the ddname FTnnP001because asynchronous I/O cannot be performed onstriped files.

If you didn't intend to use an asynchronous I/Ostatement, which is identified by the ID specifier, thencorrect your program so that you don't use one for aunit that's connected to one of the prohibited file ordevice types.


FOR1277S The asynchronous statementstatement for unit unit-number,which was connected to file-name,failed. The unit was being used asone of the Fortran standard I/Ounits. VS FORTRAN Version 2 ErrorNumber: AFB192I

ExplanationThe asynchronous statement referred to a unitthat was either the standard input unit, the errormessage unit, the print unit (which could be thesame as the error message unit), or the punch unit.These unit numbers are specified by the RDRUNIT,ERRUNIT, PRTUNIT, and PUNUNIT run-time options,respectively.





Programmer responseIf you want to use asynchronous I/O, do one of thefollowing:

• Change the unit number in your asynchronous I/Ostatements to refer to some unit other than one ofthe prohibited units listed under “Explanation.”

• Change the value of one or more of the RDRUNIT,ERRUNIT, PRTUNIT, or PUNUNIT run-time options sothat one of them refers to the unit that you wantto use for asynchronous I/O, ensuring, of course,that you don't create a conflict with some other unitthat's used by your program.

If you didn't intend to use asynchronous I/O, thenchange the form of the I/O statement by removingthe ID specifier and making whatever other changesare needed. Note that unformatted I/O statements aresimilar in function to asynchronous I/O statements.


FOR1278S The asynchronous statementstatement for unit unit-number,which was connected to file-name,failed. The program was executedon other than an MVS system. VSFORTRAN Version 2 Error Number:AFB161I






Programmer responseIf you didn't intend to use asynchronous I/O, thenchange the form of the I/O statement by removingthe ID specifier and making whatever other changesare needed. Note that unformatted I/O statements aresimilar in function to asynchronous I/O statements.

If the performance requirements of your program aresuch that asynchronous I/O is needed, then you'll haveto run the program on MVS.


FOR1279S The asynchronous statementstatement for unit unit-number,which was connected to file-name,failed. The I/O subtask terminatedabnormally with the systemcompletion code completion-code.VS FORTRAN Version 2 ErrorNumber: AFB205I

ExplanationMuch of the processing for an asynchronous I/Ostatement is done in an MVS subtask so that itsprocessing can overlap that of your program. Theasynchronous I/O subtask terminated abnormally witha system completion (abend) code of completion-code.





Programmer responseEnsure that the file definition (DD statement orALLOCATE command) for the file you are using iscoded correctly.

Ensure that your program uses the correct sequenceof asynchronous READ, WRITE, and WAIT statementswith no intervening I/O statements of the standardsequential form unless a REWIND statement is used toseparate the uses of the two forms.

For the meaning of completion-code, and for possiblecorrective actions, refer to z/OS DFSMS MacroInstructions for Data Sets.

FOR1280S The asynchronous statementstatement for unit unit-number,which was connected to file-name,failed. The record format wasother than variable spanned. VSFORTRAN Version 2 Error Number:AFB214I (format 2)




RN The READ statement is ignored, and execution continues.

RF For an input operation, the READ statement is notcompleted and execution continues. For an outputoperation, VS is assumed, and execution continues.

Programmer responseEnsure that the file definition (DD statement orALLOCATE command) for the file indicates a RECFMvalue of VS.

If you're reading an existing file that has some arecord format of other than variable spanned, thenyou can't use asynchronous I/O statements to readit. In this case, either change your program to usethe standard sequential I/O statements, or recreatethe file so that it has variable spanned records.If you choose to recreate the file using a Fortranprogram, you can produce variable spanned recordswith either asynchronous I/O statements or withstandard unformatted I/O statements. Ensure thatwhen you recreate the file, the file definition has aRECFM value of VS.


FOR1281S The asynchronous statementstatement for unit unit-number,which was connected to file-name,


failed. The program resides inauthorized library. VS FORTRANVersion 2 Error Number: AFB952I(format 8)

ExplanationYour program was link edited with an AC option thatprovided an authorization code of other than 0, andyour program was in an authorized library. In addition,your program used an asynchronous I/O statement,but this is inconsistent with executing in an authorizedstate because of the internal implementation ofasynchronous I/O.

Language Environment does not support executionof Fortran programs running in an authorized state.Running such programs, while not diagnosed in allcases, causes a system integrity exposure.





Programmer responseLink edit your program without the AC option so that itdoes not run in an authorized state.


FOR1330S The statement statement forunit unit-number failed. The filedefinition statement for file-namereferred to a VSAM file, but thefile had not been connected to theunit with an OPEN statement. VSFORTRAN Version 2 Error Number:AFB168I





Programmer responseIf you intend to process a VSAM file, ensure thatyour program executes an OPEN statement before anyother I/O statements.

If you don't intend to process a VSAM file, change thefile definition (DD statement or ALLOCATE command)to refer to some other file.


FOR1331S The WRITE statement forsequential access for unit unit-number, which was connectedto file-name, failed. The filewas a VSAM RRDS that alreadycontained records. VS FORTRANVersion 2 Error Number: AFB162I





Programmer responseEnsure that you don't use the sequential access formof the WRITE statement for a VSAM relative recorddata set (RRDS) if the data set already containsrecords.

If you want to replace individual records, use a valueof DIRECT for the ACCESS specifier on the OPENstatement, and use the direct access form of theWRITE statement, that is, with a REC specifier whosevalue indicates the specific record to be written.

If you want to extend the file at the end or rewritethe file sequentially from somewhere other than theend, the file can't be a VSAM RRDS, so change the filedefinition (DD statement or ALLOCATE command) torefer to a non-VSAM file.



FOR1340S The INQUIRE statement failed.The FILE specifier had a value ofblanks, but the UNIT specifier wasnot given. VS FORTRAN Version 2Error Number: AFB106I


Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 4

2 statement

Input CHARACTER*12 INQUIRE

3 unit Input INTEGER*4 Undefined

4 file Input CHARACTER*62 Undefined



Programmer responseCorrect your program to use of the four acceptableforms of the INQUIRE statement:INQUIRE by file

No UNIT specifier; FILE specifier with a value thatis either a data set name preceded by a slash( / ) or a ddname other than one of the defaultddnames such as FTnnF001

INQUIRE by unitUNIT specifier; no FILE specifier

INQUIRE by unnamed file, format 1UNIT specifier; FILE specifier with a value ofblanks

INQUIRE by unnamed file, format 2No UNIT specifier; FILE specifier with a value thatis one of the defaults ddnames such as FTnnF001


FOR1341S The INQUIRE statement failed.The FILE specifier had a value offile-name, which, because it wasother than all blanks, conflicted

with the presence of the UNITspecifier. VS FORTRAN Version 2Error Number: AFB109I


Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page272. Within this basic set, statement has a value ofINQUIRE, and parm_count has a value of 4.









FOR1342S The INQUIRE statement failed.The FILE specifier had a value offile-name, which was not in thecorrect format for a file name. VSFORTRAN Version 2 Error Number:AFB180I (format 1)


Qualifying Data:


No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 4

2 statement

Input CHARACTER*12 INQUIRE


4 file Input CHARACTER*62 Name of fileto whichthe INQUIREstatement wasdirected.









FOR1360E On the CLOSE statement for unitunit-number, which was connectedto file-name, the STATUS specifierhad a value of KEEP, butthe STATUS specifier on theOPEN statement had a value ofSCRATCH. VS FORTRAN Version 2Error Number: AFB171I

System actionThe file is closed as though STATUS='DELETE' hadbeen specified. If neither the ERR nor the IOSTATspecifier is present on the I/O statement, thecondition is signaled. If the condition is unhandled, theapplication is terminated.

Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of CLOSE,and parm_count has a value of 4.


RN Execution continues.

Programmer responseEither change the OPEN statement so that its STATUSspecifier has a value of other than SCRATCH, or changethe CLOSE statement so that its STATUS specifier iseither omitted or has a value of DELETE. In the lattercase, the scratch file will be deleted.


FOR1361E On the CLOSE statement for unitunit-number, the STATUS specifierhad a value of status, which wasother than KEEP or DELETE. VSFORTRAN Version 2 Error Number:AFB186I

System actionThe file is closed as though STATUS='KEEP' had beenspecified. If neither the ERR nor the IOSTAT specifieris present on the I/O statement, the condition issignaled. If the condition is unhandled, the applicationis terminated.

Qualifying Data: The basic set of four qualifying datafor I/O conditions as shown in Table 1 on page 272.Within this basic set, statement has a value of CLOSE,and parm_count has a value of 4.


RN Execution continues.

Programmer responseCorrect the value of the STATUS specifier on the CLOSEstatement so that it has a value of either KEEP orDELETE. You can also omit the STATUS specifier inwhich case the default value is:

• DELETE if the OPEN statement had a STATUSspecifier with a value of SCRATCH, or

• KEEP if the OPEN statement either had no STATUSspecifier or a STATUS specifier with a value of otherthan SCRATCH.



FOR1380S The OPEN statement could notconnect unit unit-number to file-name. The STATUS specifier hada value of status, which wasother than NEW, OLD, REPLACE,SCRATCH, or UNKNOWN. VSFortran Version 2 Error Number:AFB251I

System actionIf the unit is other than the error message unit, the unitis no longer connected to a file. If neither the ERR northe IOSTAT specifier is present on the I/O statement,the condition is signaled. If the condition is unhandled,the application is terminated.




RN The OPEN statement is not completed, and executioncontinues.

Programmer responseBased on whether the file you're connecting exists ornot, change the value of the STATUS specifier on theOPEN statement to NEW, OLD, REPLACE, SCRATCH,or UNKNOWN. If you code the value as a characterconstant, enclose the value in quotes or apostrophes.

For the error message unit, either omit the STATUSspecifier, or provide a value of UNKNOWN.


FOR1381S The OPEN statement for unit unit-number failed. The FILE specifierhad a value of ddname, which isa ddname reserved for unnamedfiles. VS Fortran Version 2 ErrorNumber: AFB107I

System actionIf the unit is other than the error message unit, the unitis no longer connected to a file. If neither the ERR northe IOSTAT specifier is present on the I/O statement,

the condition is signaled. If the condition is unhandled,the application is terminated.





Programmer responseIf you want to connect the unit to an unnamed file, thatis, to a file with a ddname of FTnnFmmm, FTnnKmm,FTERRsss, or FTPRTsss, then omit the FILE specifierfrom the OPEN statement. A file definition (DDstatement or ALLOCATE command) for that ddnamewould still be required, however.

If you want to refer to a named file, then for the FILEspecifier provide a value than isn't one of the ddnamesthat are used for unnamed files.


FOR1382S The OPEN statement could notconnect unit unit-number to file-name. The ACTION specifier hada value of action, which wasother than READ, WRITE, orREADWRITE. VS Fortran Version 2Error Number: AFB136I





RN The OPEN statement is not completed, andexecution continues.


Programmer responseDepending on whether you intend to use only inputstatements, only output statements, or both, changethe value of the ACTION specifier on the OPENstatement to READ, WRITE, or READWRITE. If youcode the value as a character constant, enclose thevalue in quotes or apostrophes.


FOR1383S The OPEN statement for unit unit-number failed. The FILE specifierhad a value of file-name, whichwas not in the correct format fora file name.

ExplanationVS Fortran Version 2 Error Number: AFB180I (format2)






Programmer responseCorrect the value of the FILE specifier. If you'reproviding a ddname, ensure that it consists of nomore than eight characters, all of which must bealphanumeric, and that its first character is alphabetic.

If you're providing a data set name, code the value ofthe FILE specifier as a slash (/) followed by the dataset name. The data set name, which can be followedby a member name surrounded by parentheses, mustbe in the format required by the DSNAME parameterof a DD statement as described in z/OS DFSMS MacroInstructions for Data Sets.


FOR1384S The OPEN statement could notconnect unit unit-number to file-name. The ACCESS specifier hada value of access, which wasother than SEQUENTIAL, DIRECT,or KEYED.

ExplanationVS Fortran Version 2 Error Number: AFB182I






Programmer responseDepending on the type of I/O statements that youwant to use for the file that you're connecting, changethe value of the ACCESS specifier on the OPENstatement to SEQUENTIAL, DIRECT, or KEYED. If youcode the value as a character constant, enclose thevalue in quotes or apostrophes.


FOR1385S The OPEN statement could notconnect unit unit-number to file-name. The BLANK specifier had avalue of blank, which was otherthan ZERO or NULL.








Programmer responseDepending on whether you want blanks in input fieldsthat are read with formatted READ statements tobe interpreted as zeros or nulls, change the valueof the BLANK specifier on the OPEN statement toZERO or NULL, respectively. If you code the value asa character constant, enclose the value in quotes orapostrophes.

If you omit the FILE specifier from the OPENstatement, a value of NULL is assumed.


FOR1386S The OPEN statement could notconnect unit unit-number tofile-name. The FORM specifierhad a value of format, whichwas other than FORMATTED orUNFORMATTED.







Programmer responseDepending on whether you intend to use formattedor unformatted input/output statements for the file,change the value of the FORM specifier on theOPEN statement to FORMATTED or UNFORMATTED,respectively. If you code the value as a characterconstant, enclose the value in quotes or apostrophes.


FOR1387S The OPEN statement could notconnect unit unit-number to file-name. The CHAR specifier had avalue of char, which was otherthan DBCS or NODBCS. FortranVersion 2 Error Number: AFB104I






Programmer responseDepending on whether your input file contains double-byte characters that are to be read with a formattedREAD statement, change the value of the CHARspecifier on the OPEN statement to DBCS or NODBCS.If you code the value as a character constant, enclosethe value in quotes or apostrophes.


FOR1389S The OPEN statement could notconnect unit unit-number to file-name. The RECL specifier had a


value of recl, which was not withinthe range 1 to 32760, inclusive.Fortran Version 2 Error Number:AFB233I



No.

Name Input/Output

Data Type andLength

Value

5 record-length

Input/Output

INTEGER*4 Value of the RECLspecifier on theOPEN statement.



RN The OPEN statement is not completed, and executioncontinues. The remainder of the deallocation list isprocessed and execution continues.

RI The value placed in record_length is used as the new valuefor the RECL specifier, and execution continues.

Programmer responseEnsure that the value of the RECL specifier on theOPEN statement is an integer that is neither less than1 nor greater than 32760. In addition, ensure thatthis value is the same as the value that's associatedwith the file through one or more of the following, asapplicable:

• The label of an existing data set• The LRECL parameter of the DD statement or

ALLOCATE command• The LRECL value given in an invocation of the

FILEINF callable service• The record length given in the RECORDSIZE

parameter of the Access Method Services DEFINEcommand that was used to define the VSAM cluster.


FOR1390S The OPEN statement could notconnect unit unit-number to file-name. The SMSVSAM server wasnot available.

ExplanationVSAM record level sharing was requested for thefile either because of the RLS parameter on the DDstatement or ALLOCATE command or because of theRLS argument in the call to the FILEINF callableservice. Record level sharing could not be providedbecause the SMSVSAM server was not available.

System actionThe unit is no longer connected to a file. If neitherthe ERR nor the IOSTAT specifier is present on the I/Ostatement, the condition is signaled. If the condition isunhandled, the application is terminated.





Programmer responseIf VSAM record level sharing isn't required, then don'trequest it in the DD statement, in the ALLOCATEcommand, or in the call to the FILEINF callableservice. Otherwise, correct the situation that causedthe SMSVSAM server not to be available.

If you cannot resolve the problem, seek assistancefrom your Language Environment support personnel.


FOR1393S locator-text The VSAM macro-namemacro instruction executed forfile-name had a return code ofreturn-code and an error codeof X' hex-code ' (decimal-code).The SMSVSAM server was notavailable.

ExplanationIn support of the Fortran I/O statement indicated bythe message text, Language Environment executeda VSAM macro-name macro instruction. DFSMS/MVSdetected the error indicated by the return code return-code and the error code with a hexadecimal value ofhex-code (decimal value of decimal-code). This errorcode indicates that VSAM record level sharing couldn'tbe provided because the SMSVSAM server was not


available. (VSAM record level sharing was requestedfor the file either because of the RLS parameter on theDD statement or ALLOCATE command or because ofthe RLS argument in the call to the FILEINF callableservice.)






Programmer responseFor the meaning of return code return-code and errorcode hex-code (or decimal-code), refer to z/OS DFSMSMacro Instructions for Data Sets.

If VSAM record level sharing isn't required, then don'trequest it in the DD statement, in the ALLOCATEcommand, or in the call to the FILEINF callableservice. Otherwise, correct the situation that causedthe SMSVSAM server not to be available.

If you are unable to resolve the problem, seekassistance from your Language Environment supportpersonnel.


FOR1394S The OPEN statement could notconnect unit unit-number, theerror message unit, to file-name.The FILE specifier had a value thatstarted with a slash (/).

ExplanationOn the OPEN statement the UNIT specifier had a valuethat was the error message unit number, and the FILEspecifier had a value with a leading slash ( / ). Theleading slash indicated dynamic file allocation, that is,that a data set name rather than a ddname was given.






Programmer responseDynamic allocation cannot be done from a Fortranprogram for a file that's being connected to the errormessage unit. Therefore, take one of these actions:

• Provide a file definition (DD statement or ALLOCATEcommand) for the file, and use its ddname without aslash as the value of the FILE specifier on the OPENstatement.

• Connect that file to a unit other than the errormessage unit by changing the unit identifier.

• Remove the slash from the value of the FILEspecifier if an intended ddname followed the slash.


FOR1395S The OPEN statement could notconnect unit unit-number to file-name. The ACCESS specifier hada value of KEYED, and the FILEspecifier had a value that startedwith a slash (/). Fortran Version 2Error Number: AFB102I

ExplanationThe OPEN statement had a value for the ACCESSspecifier that indicated keyed access and a value forthe FILE specifier with a leading slash ( / ). The leadingslash indicated dynamic file allocation, that is, that adata set name rather than a ddname was given.







Programmer responseDynamic allocation cannot be done from a Fortranprogram for a file that's being connected for keyedaccess. If you intend to use keyed access becausethe file is a VSAM key-sequenced data set, take on ofthese actions:

• Provide a file definition (DD statement or ALLOCATEcommand) for the file, and use its ddname without aslash as the value of the FILE specifier on the OPENstatement.

• Remove the slash from the value of the FILEspecifier if an intended ddname followed the slash.

If the file isn't a VSAM key-sequenced data set, thenchange the value of the ACCESS specifier to eitherSEQUENTIAL or DIRECT.


FOR1396S The OPEN statement could notconnect unit unit-number to file-name. The STATUS specifier had avalue of NEW, but the file alreadyexisted. Fortran Version 2 ErrorNumber: AFB108I (format 1)

ExplanationThe OCSTATUS run-time option was in effect, andthe STATUS specifier on the OPEN statement had avalue of NEW, but the file already existed accordingto the Fortran definitions of file existence. Thesedefinitions are explained in VS FORTRAN Version 2Programming Guide for CMS and MVS in the chapter“What Determines File Existence” and generally reflectthe operating system view of file existence; however,there are a few differences. For example, using a DDstatement or ALLOCATE command to allocate spacefor a file on a disk volume does not mean that thefile exists from the Fortran point of view. Such a filedoesn't exist until an OPEN or WRITE statement for ithas been used in a Fortran program or until it has hadrecords written into it by some non-Fortran program orutility.






Programmer responseThe changes that you must make depend on how youintend to processed the file in your program.

If you want to read an existing file, then change thevalue of the STATUS specifier to OLD.

If you want to read or update an existing file beingconnected for direct or keyed access, then change thevalue of the STATUS specifier to OLD.

If you want to extend an existing file being connectedfor sequential access, then change the value of theSTATUS specifier to OLD, and take one of theseactions:

• Provide the DISP=MOD parameter on the DDstatement, the MOD parameter in the ALLOCATEcommand, or a value of MOD for the DISP argumentin the invocation of the FILEINF callable service.

• Provide a value of APPEND for the POSITIONspecifier.

If you want to replace all of the records in an existingfile being connected for sequential access, then makeone of these changes:

• Provide a value of OLD for the STATUS specifierand do not provide either the DISP=MOD parameteron the DD statement, the MOD parameter on theALLOCATE command, nor a value of MOD for theDISP argument in the invocation of the FILEINFcallable service, or

• Provide a value of REPLACE for the STATUS specifier.In this case, if the disk file is dynamically allocated,the original space, if any, is released, and new spaceis allocated.

If you want to replace all of the records in an existingfile, being connected for direct or keyed access, thenprovide a value of REPLACE for the STATUS specifier.In this case, if the disk file is dynamically allocated,


the original space, if any, is released, and new space isallocated.

If you want to create and write to a new file in yourprogram, then the STATUS specifier value of NEW iscorrect. Ensure that all of the following are true:

• The file definition (DD statement or ALLOCATEcommand) or the data set name given in the FILEspecifier on the OPEN statement refers to the filethat you intended.

• No other unit is connected to the same file andhas updated it before this OPEN statement wasexecuted.

• The file does not exist according to the Fortranrules of file existence. (For example, under certaincircumstances, a file that is present on a disk volumebut contains no data can still exist according to thisdefinition.)

If the file does exist according to the Fortran definitionof file existence, but you still want the STATUSspecifier value to be NEW, then use the NOOCSTATUSrun-time option. However, consider the following:

• Because file existence is not checked, the STATUSspecifier value of NEW takes precedence, meaningthat any records already in the file could beoverwritten.

• This run-time option causes file existence checkingto be bypassed for all OPEN statements.


FOR1397S The OPEN statement could notconnect unit unit-number to file-name. The STATUS specifier hada value of NEW, but the filedefinition referred to a file ordevice that was restricted toinput only. Fortran Version 2 ErrorNumber: AFB108I (format 2)

ExplanationThe STATUS specifier had a value of NEW, whichimplied that a file was to be created. However, thefile definition (DD statement or ALLOCATE command)or the data set name given in the FILE specifier onthe OPEN statement referred to a file or device thatdoesn't allow output operations. Examples of suchfiles include:

• An in-stream data set (DD *)• A data set whose DD statement specifies

LABEL=(,,,IN)

• A file for which the system's access control facility(such as RACF) prevents you from updating the dataset.






Programmer responseIf you want to read from a file or a device that doesn'tpermit output, either omit the STATUS specifier orprovide a value of OLD or UNKNOWN for the STATUSspecifier. Ensure that the file really exists and that youcan read from it.

If you want to create a new file and write records on it,then the STATUS specifier value of NEW is correct. Inthis case, change either of the following, as applicable,to refer to a file or device on which you can writerecords:

• The file definition (DD statement or ALLOCATEcommand)

• For a dynamically allocated data, the data set namethat follows the slash ( / ) in the FILE specifier.

Do not refer to a data set such as an in-stream dataset (DD *), a data set for which you do not have RACFauthority to update, or a data set whose DD statementhas a LABEL=(,,,IN) parameter.


FOR1398S The OPEN statement could notconnect unit unit-number to file-name. The STATUS specifier hada value of OLD, but the file didnot exist. Fortran Version 2 ErrorNumber: AFB108I (format 3)


ExplanationThe OCSTATUS run-time option was in effect, andthe STATUS specifier on the OPEN statement hada value of OLD, but the file didn't exist accordingto the Fortran definitions of file existence. Thesedefinitions are explained in VS FORTRAN Version 2Programming Guide for CMS and MVS in the chapter“What Determines File Existence” and generally reflectthe operating system view of file existence; however,there are a few differences. For example, using a DDstatement or ALLOCATE command to allocate spacefor a file on a disk volume does not mean that thefile exists from the Fortran point of view. Such a filedoesn't exist until an OPEN or WRITE statement forit has been used in a Fortran program or until it hashad records written into it by a non-Fortran program orutility.






Programmer responseIf you want to create a new file and write records on it,then change the value of the STATUS specifier to NEW,REPLACE, or UNKNOWN.

If you want to read from or write to an existing file,then the STATUS specifier value of OLD is correct.Ensure that all of the following are true:


• No other unit has been connected to the same fileand has caused the file to be deleted before thisOPEN statement was executed.

• The file exists according to the Fortran rulesof file existence. (For example, under certaincircumstances, a file that is present on a disk volume

but contains no data doesn't exist according to thisdefinition.)

If the file doesn't exist according to the Fortrandefinition of file existence, but you still want theSTATUS specifier value to be OLD, then use theNOOCSTATUS run-time option. However, consider thefollowing:

• Because file existence is not checked, the STATUSspecifier value of OLD will take precedence, meaningthat there must be records in the file if you want toread them.

• This run-time option causes file existence checkingto be bypassed for all OPEN statements.


FOR1399S The OPEN statement could notconnect unit unit-number to file-name. The ACTION specifier hada value of READ, but the file didnot exist. Fortran Version 2 ErrorNumber: AFB108I (format 4)

ExplanationThe ACTION specifier on the OPEN statement hada value of READ, but the file didn't exist accordingto the Fortran definitions of file existence. Thesedefinitions are explained in VS FORTRAN Version 2Programming Guide for CMS and MVS in the chapter“What Determines File Existence” and generally reflectthe operating system view of file existence; however,there are a few differences. For example, using a DDstatement or ALLOCATE command to allocate spacefor a file on a disk volume does not mean that thefile exists from the Fortran point of view. Such a filedoesn't exist until an OPEN or WRITE statement for ithas been used in a Fortran program or until it has hadrecords written into it by some non-Fortran program orutility.







Programmer responseIf you want to write records on the file, then eitheromit the ACTION specifier, or change the value of theACTION specifier to WRITE or READWRITE.

If you want to just read from an existing file, then theACTION specifier value of READ is correct. Ensure thatall of the following are true:



• The file exists according to the Fortran rulesof file existence. (For example, under certaincircumstances, a file that is present on a disk volumebut contains no data doesn't exist according to thisdefinition.)

If the file doesn't exist according to the Fortrandefinition of file existence, but you still want to readfrom the file, then omit the ACTION specifier to avoiddetecting this error. In this case, ensure that the filehas records that can be read.


FOR1400S The OPEN statement could notconnect unit unit-number to file-name. The ACTION specifier hada value of READ, but the filedefinition referred to a file ordevice that was restricted tooutput only. Fortran Version 2Error Number: AFB108I (format 5)

ExplanationThe ACTION specifier had a value of READ, whichimplied that only input processing would be performedon the file. However, the file definition (DD statementor ALLOCATE command) or the data set name givenin the FILE specifier on the OPEN statement referredto a file or device that allows only output operations.Examples of such files include:

• A system output data set (SYSOUT parameter on theDD statement)

• A data set whose DD statement specifiesLABEL=(,,,OUT)






Programmer responseEnsure that the value of the ACTION specifier isconsistent with the capabilities of the file or devicereferenced by the file definition (DD statement orALLOCATE command) or by the data set name given inthe FILE specifier on the OPEN statement. You mighthave to change either the ACTION specifier, the filedefinition, or the data set name.

If you want to write on a file or device that allows onlyoutput, either omit the ACTION specifier or provide avalue of WRITE for the action specifier.

If you want to read from a file, then change the filedefinition (DD statement or ALLOCATE command) orthe data set name given in the FILE specifier on theOPEN statement to refer to a file or device from whichyou can read records. Ensure that the file exists or thatare records to be read.

If you want to read to and write from the file, thenensure that the file or device allows you to performboth input and output. In this case, either omit theACTION specifier, or provide a value of READWRITE forthe ACTION specifier.


FOR1401S The OPEN statement could notconnect unit unit-number to file-name. The ACTION specifier hada value of action, but the filedefinition referred to a file ordevice that was restricted toinput only. Fortran Version 2 ErrorNumber: AFB108I (format 6)


ExplanationThe ACTION specifier had a value of action, whichimplied that output statements, such WRITE orENDFILE, would to be executed. However, the filedefinition (DD statement or ALLOCATE command) orthe data set name given in the FILE specifier onthe OPEN statement referred to a file or device thatdoesn't allow output operations. Examples of suchfiles include:


LABEL=(,,,IN)• A file for which the system's access control facility

(such as RACF) prevents you from updating the dataset.






Programmer responseEnsure that the value of the ACTION specifier isconsistent with the capabilities of the file or devicereferenced by the file definition (DD statement orALLOCATE command) or by the data set name given inthe FILE specifier on the OPEN statement. You mighthave to change either the ACTION specifier, the filedefinition, or the data set name.

If you want to read from a file or a device that doesn'tpermit output, either omit the ACTION specifier orprovide a value of READ for the STATUS specifier.Ensure that the file really exists and that you can readfrom it.

If you want to create a new file and write recordson it, then provide a value of WRITE for the ACTIONspecifier. In this case, ensure that either of thefollowing, as applicable, refers to a file or device onwhich you can write records:

• The file definition (DD statement or ALLOCATEcommand)

• For a dynamically allocated data, the data set namethat follows the slash (/) in the FILE specifier

If you want to read to and write from the file, thenensure that the file or device allows you to performboth input and output. In this case, either omit theACTION specifier, or provide a value of READWRITE forthe ACTION specifier.

If you provide a value of WRITE or READWRITE forthe ACTION specifier, don't refer to a data set suchas an in-stream data set (DD *), a data set for whichyou don't have RACF authority to update, or a data setwhose DD statement has a LABEL=(,,,IN) parameter.


FOR1402S The OPEN statement could notconnect unit unit-number to file-name. The ACTION specifier,which had a value of READ,conflicted with the STATUSspecifier, which had a value ofstatus. Fortran Version 2 ErrorNumber: AFB108I (format 8)

ExplanationThe ACTION specifier on the OPEN statement had avalue of READ, which implied that you would readfrom but not write to a file which should alreadyexist. However, the value of status for the STATUSimplied that a new file was to be created. This wasinconsistent because you can't read from a newlycreated file until records have been written on it.







Programmer responseIf you want to read from an existing file withoutwriting on it, then the value of READ for the ACTIONspecifier is correct. Either omit the STATUS specifier, orprovide a value of OLD or UNKNOWN for the STATUSspecifier. Ensure that the file definition (DD statementor ALLOCATE command) or the data set name given inthe FILE specifier on the OPEN statement refers to afile that exists so that you can read from it.

If you want to write records on the file, change thevalue of the ACTION specifier to WRITE, or, if you wantto both write to and read from the file, either changethe value of the ACTION specifier to READWRITE oromit the ACTION specifier. For the STATUS specifier,use a value of NEW if you want to create a file thatdoesn't already exist, a value of REPLACE if you wantto create a new file replacing the existing one if italready exists, or a value of OLD if you want to usean existing file even if you want to rewrite it. Omittingthe STATUS specifier or providing value of UNKNOWNis the equivalent of NEW if the file doesn't exist or ofOLD if it does exist.


FOR1403S The OPEN statement could notconnect unit unit-number to file-name. The file did not exist, andthe file definition referred to a fileor device that was restricted toinput only. Fortran Version 2 ErrorNumber: AFB108I (format 9)

ExplanationThe file definition (DD statement or ALLOCATEcommand) or the data set name given in the FILEspecifier on the OPEN statement referred to a file ordevice that doesn't allow output operations. Examplesof such files include:

• A data set whose DD statement specifiesLABEL=(,,,IN)

• A file for which the system's access control facility(such as RACF) prevents you from updating the dataset.

However, the file didn't exist according to the Fortrandefinitions of file existence; this precludes anymeaningful access to the file.

The Fortran definitions of file existence are explainedin VS FORTRAN Version 2 Programming Guide forCMS and MVS in the chapter “What Determines FileExistence” and generally reflect the operating systemview of file existence; however, there are a few

differences. For example, using a DD statement orALLOCATE command to allocate space for a file on adisk volume does not mean that the file exists from theFortran point of view. Such a file doesn't exist until anOPEN or WRITE statement for it has been used in aFortran program or until it has had records written intoit by some non-Fortran program or utility.






Programmer responseIf you want to create a new file, ensure that the filedefinition (DD statement or ALLOCATE command) orthe data set name given in the FILE specifier on theOPEN statement refers to a file or device that allowsyou to perform output operations.

If you want to read from an existing file, ensure that allof the following are true:



• The file exists according to the Fortran rulesof file existence. (For example, under certaincircumstances, a file that is present on a disk volumebut contains no data doesn't exist according to thisdefinition.)


FOR1404S The OPEN statement could notconnect unit unit-number to file-name. The ACCESS specifier hada value of DIRECT, and the file


already existed, but the file wasempty. Fortran Version 2 ErrorNumber: AFB108I (format 10)

ExplanationThe file that was to be connected for direct accessexisted before the execution of the OPEN statement.However, there were no records in the file, and such afile can't be used for direct access. The fact that thefile seemed to exist is based on one of the following:

• The file was previously connected for sequentialaccess within the same executable program andwas closed without any records having beenwritten. Unless the STATUS specifier on that CLOSEstatement had a value of DELETE, such a file is seenas an existing file according to the Fortran definitionsof file existence, which are explained in VS FORTRANVersion 2 Programming Guide for CMS and MVS in thechapter “What Determines File Existence.”

• The file was dynamically allocated, that is, the FILEspecifier had a data set name preceded by a slash(/), and before execution of the OPEN statement thedata set existed on the disk volume but contained norecords.

• The NOOCSTATUS run-time option was in effect, thefile didn't contain any records, and the file had notbeen used previously within the same executableprogram.






Programmer responseIf you want to connect an existing file for direct access,ensure that all of the following are true:


• The file contains at least one record.• The program that created the file successfully closed

it.• The file contains unblocked fixed-length records,

that is, the RECFM value is F.

If you want to create a new file, then change the valueof the STATUS specifier to NEW or SCRATCH.

If the file might have existed before the executionof the OPEN statement and if you want to replacewhatever might have been in that file, then take oneof these actions, as applicable:

• If the file is a named file, provide a value of REPLACEfor the STATUS specifier.

• If the file was used earlier in a Fortran program,provide a value of DELETE for the STATUS specifieron the CLOSE statement for that previous use of thefile.

FOR1405S The OPEN statement could notconnect unit unit-number to file-name. The ACTION specifier,which had a value of WRITE,conflicted with the KEYS specifier,which listed more than one key.Fortran Version 2 Error Number:AFB121I

ExplanationA value of WRITE was provided for the ACTIONspecifier on an an OPEN statement that specifiedkeyed access; this implied that records were to beloaded into the file using the file's primary key.However, the KEYS specifier listed more than onestart-end pair, and this is not permitted when loadingrecords into the file.







Programmer responseIf you want to load records into the file with recordsthat are presented in increasing sequence of theprimary key, then either remove the KEYS specifieror specify only the start-end pair that represents theprimary key for the file. Ensure that the file definition(DD statement or ALLOCATE command) refers to thebase cluster of the VSAM key-sequenced data setrather than to a path that corresponds to one of thealternate index keys.

If you want to process a file that is not empty,change the value of the ACTION specifier to READ orREADWRITE.


FOR1406S The OPEN statement could notconnect unit unit-number to file-name. The KEYS specifier wasgiven, but the ACCESS specifierdid not have a value of KEYED.Fortran Version 2 Error Number:AFB137I






Programmer responseIf you were connecting a VSAM key-sequenced dataset (KSDS), then change the value of the ACCESSspecifier to KEYED. Otherwise, remove the KEYSspecifier from the OPEN statement, and ensurethat the ACCESS specifier has a value of eitherSEQUENTIAL or DIRECT, as appropriate to your use ofthe file. If you code the value of the ACCESS specifieras a character constant, enclose the value in quotes orapostrophes.


FOR1407S The OPEN statement could notconnect unit unit-number to file-name. The ACCESS specifier had avalue of KEYED, and the ACTIONspecifier had a value of READ, butthe file was empty. Fortran Version2 Error Number: AFB138I






Programmer responseEnsure that the VSAM key-sequenced data set (KSDS)that you want to process is referenced by the filedefinition (DD statement or ALLOCATE command).

If you want to read from a file that has records, then:

• If the file referenced by the file definition is a basecluster, that is, the file with the primary key, thenensure that is was successfully loaded with records,either in a Fortran program or by a program writtenin some other language.

• If the file referenced by the file definition is a pathfor an alternate index, then ensure that the AccessMethod Services BLDINDEX command successfullybuilt the alternate index after the base cluster wasloaded.

If you want to start with an empty file and addrecords to it in other than ascending sequence of theprimary key, then change the value of the ACCESSspecifier to READWRITE. In this case the OPENstatement processing simulates the loading of the fileand deletes all loaded records; then VSAM no longerconsiders the file to be empty.

If you want to load records into an empty file in thefastest way, follow these steps:


1. On the file definition (DD statement or ALLOCATEcommand), provide the data set name of the file'sbase cluster, that is, of the file with the primary key.

2. Execute an OPEN statement with a value of WRITEfor the ACTION specifier and a value of KEYEDfor the ACCESS specifier; either omit the KEYSspecifier or provide a KEYS specifier with a singlestart-end pair that represents the position in therecord of the file's primary key.

3. Execute at least one WRITE statement to writethe records; ensure that you write the records inascending sequence of the primary key.

4. Execute a CLOSE statement.

After these steps, the file is available to be connectedusing an ACTION specifier of either READ orREADWRITE.

If you omit the DELIM specifier, then for list-directedformatting the character values are written withoutdelimiters, and for namelist formatting the charactervalues are surrounded by apostrophes.


FOR1432S The OPEN statement could notconnect unit unit-number to file-name. The DELIM specifier wasgiven, but the file was to beconnected for unformatted input/output.






Programmer responseMake one of these changes in the OPEN statement:

• If you want to use formatted input/outputstatements, then:

– For sequential access either omit the FORMspecifier, or change the value of the FORMspecifier to FORMATTED.

– For direct or keyed access, provide a valueFORMATTED of the FORM specifier.

• If you want to use unformatted input/outputstatements, then remove the DELIM specifier.


FOR1433S The OPEN statement could notconnect unit unit-number to file-name. The POSITION specifier hada value of APPEND, but the filedefinition referred to a file or adevice for which positioning to theend is not allowed.

ExplanationThe POSITION specifier had a value of APPEND onan OPEN statement for a file that resides on a devicethat does not honor positioning commands in a waythat would permit positioning the file to its terminalpoint. Most tape and disk files support positioningcommands, whereas the following do not:

• In-stream data sets (DD *)• System output data sets (SYSOUT parameter on the

DD statement)• Terminals• Card readers• Printers• Card punches







Programmer responseEnsure that the file definition (DD statement orALLOCATE command) or the data set name given inthe FILE specifier on the OPEN statement refers to thefile that you intended.

If the logic of your program requires that the file bepositioned at its terminal point when it is connected,change the file definition or the data set name givenin the FILE specifier to refer to a file or a device thatsupports this type of positioning. If the positioning tothe terminal point is not required, either remove thePOSITION specifier on the OPEN statement or changeits value to ASIS or REWIND.


FOR1434S The OPEN statement could notconnect unit unit-number to file-name. The file definition referredto a member of a partitioned dataset (PDS), the POSITION specifierhad a value of APPEND, and theACTION specifier didn't have avalue of READ.

ExplanationThe file definition (DD statement or ALLOCATEcommand) or the data set name given in the FILEspecifier on the OPEN statement referred to a memberof a partitioned data set (PDS). The OPEN statementhad a POSITION specifier with a value of APPEND,which indicates that the file should be positioned to itsendfile record. However, because the ACTION specifierwas either omitted or was coded with a value of otherthan READ, writing of records onto the file is implied.It is not possible to write records onto the end of anexisting member of a PDS.






Programmer responseEnsure that the file definition or FILE specifier on theOPEN statement refers to the file that you intended.

If you want to write a new or replacement member of aPDS, then remove the POSITION specifier and providea value of WRITE for the ACTION specifier.

If you want to read an existing member of a PDS fromthe beginning, provide a value of READ for the ACTIONspecifier and either remove the POSITION specifier orprovide a value of REWIND for it.

If you want to read an existing member of a PDS afterfirst positioning the file to the end (so that you canexecute BACKSPACE statements, for example), thenthe value of APPEND for the POSITION specifier iscorrect. In this case, provide a value of READ for theACTION specifier.


FOR1435S The OPEN statement could notconnect unit unit-number to file-name. The file definition referredto a concatenation of data sets,and the POSITION specifier had avalue of APPEND.

ExplanationThe file definition (DD statement or ALLOCATEcommand) referred to a concatenation of data sets,that is, to a sequence data sets that was to beprocessed as though it consisted of a continuoussequence of records in a single file. The POSITIONspecifier on the OPEN statement had a value ofAPPEND, which implied that this file was to bepositioned at its terminal point. Such positioningcannot be done for a file that is a concatenation of datasets.







Programmer responseEnsure that the file definition refers to the file that youintended.

If the file that you want to process is a concatenationof data sets, either remove the POSITION specifier onthe OPEN statement or change its value to REWINDor ASIS. You won't be able to position this file to itsterminal point.

If the logic of your program requires that the file bepositioned at its terminal point when it is connected,change the file definition to refer to a file or a devicethat supports this type of positioning.


FOR1436S The OPEN statement could notconnect unit unit-number to file-name. The file definition referredto a concatenation of data sets,and the STATUS specifier had avalue of REPLACE.

ExplanationThe file definition (DD statement or ALLOCATEcommand) referred to a concatenation of data sets,that is, to a sequence data sets that was to beprocessed as though it consisted of a continuoussequence of records in a single file. The STATUSspecifier on the OPEN statement had a value ofREPLACE, which implied that this file was to bedeleted and recreated. This deletion and recreationcannot be done for a file that is a concatenation of datasets.







If the file that you want to process is a concatenationof data sets, either remove the STATUS specifier onthe OPEN statement or change its value to OLD orUNKNOWN. You won't be able to delete the existingfile.

If the logic of your program requires that the file bedeleted and recreated, change the file definition torefer to a file or a device that supports file deletion.


FOR1437S The OPEN statement could notconnect unit unit-number to file-name. The file definitions referredto a striped file, and the POSITIONspecifier had a value of APPEND.

ExplanationThe file definitions (DD statements or ALLOCATEcommands) referred to a striped file, that is, to a filewith ddnames of the form FTnnPmmm, where nn isthe unit number and mmm is the stripe number. ThePOSITION specifier on the OPEN statement had avalue of APPEND, which implied that this file was tobe positioned at its terminal point. Such positioningcannot be done for a striped file.








If the file that you want to process is a striped file,either remove the POSITION specifier on the OPENstatement or change its value to REWIND or ASIS. Youwon't be able to position this file to its terminal point.

If the logic of your program requires that the file bepositioned at its terminal point when it is connected,change the ddname on the file definition to the formFTnnF001. Ensure that the file or a device referencedby the file definition is one that supports this type ofpositioning.


FOR1438S The OPEN statement could notconnect unit unit-number to file-name. The RECL specifier had avalue of recl-val, which is smallerthan the minimum length, high-key-pos, needed to contain all ofthe file's keys.


Qualifying Data: Only the basic set of four qualifyingdata for I/O conditions as shown in Table 1 on page272. Within this basic set, statement has a value ofOPEN, and parm_count has a value of 6.

No.

Name Input/Output

Data Type andLength

Value

5 recl-val Input INTEGER*4 Value from the RECLspecifier in the OPENstatement.

6 high-key-pos

Input INTEGER*4 Minimum record sizeneeded to include allthe keys specified inthe KEYS specifier.




Programmer responseEither remove the RECL specifier from the OPENstatement or increase its value so that it is large

enough to contain all record positions of each of thekeys listed as start-end pairs in the KEYS specifier onthe OPEN statement.

If you don't need to refer to certain of the keys, thendon't list the unneeded ones as start-end pairs in theKEYS specifier.


FOR1439S The OPEN statement for unitunit-number, which was alreadyconnected to file file-name, failed.The POSITION specifier had avalue of position, which was otherthan ASIS.

ExplanationThe OPEN statement referred to a unit that wasalready connected to a file. Because the FILE specifierwas either omitted or had a value that was same asthe name of the file to which the unit was alreadyconnected, the OPEN statement did not cause thefile to be disconnected and opened again; instead,the OPEN statement applied to the already existingconnection. In addition, the POSITION specifier onthe OPEN statement had a value of either REWINDor APPEND. This is not allowed because only theBLANK, CHAR, DELIM, and PAD specifiers can changethe properties of the connection when the OPENstatement refers to an existing connection between aunit and a file.






Programmer responseEnsure that both the OPEN statement and anypreviously executed I/O statements refer to the unitnumber that you intend.


If you want to retain the existing connection betweenthe unit and the file, then either remove the POSITIONspecifier from the OPEN statement or change the valueof the POSITION specifier to ASIS.

If you want to use the OPEN statement to establisha new connection between the unit and the file, thentake one of the following actions to disconnect the unitfrom the file to which it's already connected and toconnect the unit to a different file:

• Execute a CLOSE statement followed by anotherOPEN statement.

• For a named file only, execute an OPEN statementwith a FILE specifier whose value is different fromthe name of the file to which the unit is alreadyconnected. This has the effect of executing a CLOSEstatement with no STATUS specifier followed by theOPEN statement.

For either of these two cases, all specifiers coded onthe OPEN statement and the default values for allomitted specifiers provide the properties of the newconnection between the unit and the file.


FOR1440S The OPEN statement could notconnect unit unit-number to file-name. The STATUS specifier hada value of SCRATCH, but the filedefinition referred to a file ordevice that is restricted to inputonly.

ExplanationThe STATUS specifier had a value of SCRATCH, whichimplied that a temporary file was to be created andthat output statements, such WRITE or ENDFILE,would be executed. However, the file definition (DDstatement or ALLOCATE command) or the data setname given in the FILE specifier on the OPENstatement referred to a file or device that doesn't allowoutput operations. Examples of such files include:



(such as RACF) prevents you from updating the dataset

System actionThe unit is no longer connected to a file. If neitherthe ERR nor the IOSTAT specifier is present on the I/O

statement, the condition is signaled. If the condition isunhandled, the application is terminated.





Programmer responseEnsure that the value of the STATUS specifier isconsistent with the capabilities of the file or devicereferenced by the file definition (DD statement orALLOCATE command) or by the data set name given inthe FILE specifier on the OPEN statement. You mighthave to change either the STATUS specifier, the filedefinition, or the data set name.

If you want to read from a file or a device that doesn'tpermit output, either remove the STATUS specifier orchange its value to OLD. Ensure that the file reallyexists and that you can read from it.

If you want to create a temporary file and writerecords on it, then the value of SCRATCH for theSTATUS specifier is correct. In this case, ensure thatthe file definition refers to a file or device on whichyou can write records. Note that when the STATUSspecifier has a value of SCRATCH, you must omit theFILE specifier.

If you want to create a new file that is other than atemporary file, either remove the STATUS specifier orchange its value to NEW or REPLACE. The value ofREPLACE allows you to create a new file if it doesn'talready exist or to delete an existing one and create anew one.

If you want to overwrite the records in an existingfile, either remove the STATUS specifier or change itsvalue to OLD. Unless you specify either a value ofAPPEND for the POSITION specifier, the DISP=MODparameter in the DD statement, or the MOD specifierin the ALLOCATE command, the file will be positionedto the beginning and the first WRITE statement willoverwrite any existing records.

In any of the cases for which a file is to be created orrecords are to be written, ensure that the file definitionrefers to a file or device on which you can writerecords. For example, don't refer to a data set suchas an in-stream data set (DD *), a data set for whichyou don't have RACF authority to update, or a data setwhose DD statement has a LABEL=(,,,IN) parameter.



FOR1441S The OPEN statement could notconnect unit unit-number to file-name. The STATUS specifier had avalue of SCRATCH, but the ACTIONspecifier had a value of READ

ExplanationThe STATUS specifier had a value of SCRATCH, whichimplied that a temporary file was to be created andthat output statements, such WRITE or ENDFILE,would be executed. However, the ACTION specifierhad a value of READ, which implied that that no outputstatements would be executed.






Programmer responseEnsure that the value of the STATUS specifier isconsistent with the value of the ACTION specifier andwith the capabilities of the file or device referencedby the file definition (DD statement or ALLOCATEcommand) or by the data set name given in the FILEspecifier on the OPEN statement. You might haveto change either the STATUS specifier, the ACTIONspecifier, the file definition, or the data set name.

If you just want to read from a file, then the value ofREAD for the ACTION specifier is correct. In this case,either remove the STATUS specifier or change its valueto OLD. Ensure that the file really exists and that youcan read from it.

If you want to create a temporary file and writerecords on it, then the value of SCRATCH for theSTATUS specifier is correct. In this case, eitherremove the ACTION specifier or change its value toREADWRITE. Also ensure that the file definition refersto a file or device on which you can write records.

Note that when the STATUS specifier has a value ofSCRATCH, you must omit the FILE specifier.


FOR1500S locator-text System-messageFortran Version 2 Error Number:AFB225I (format 1), AFB225I(format 2)

ExplanationAn I/O error was detected by one of the underlyingoperating system's access methods; the error isdescribed by System-message. Examples of causesinclude these situations:

• A permanent I/O error was encountered.• The length of the data to be read or written was

inconsistent with the block size specified in the filedefinition (DD statement or ALLOCATE command)or in the call to the FILEINF callable service for adynamically allocated file.

• The length of the data to be read or written wasinconsistent with the capabilities of the I/O device.

• The physical end of a tape was encountered whilereading or writing a record.

• A storage medium error occurred on either tape ordisk.


• The statement statement for unit unit-number failed.• The INQUIRE statement failed.• An error occurred during enclave termination.

System actionIf the error occurred during the execution of an OPENstatement, the unit is no longer connected to a file.If neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. If thecondition is unhandled, the application is terminated.






Programmer responseExamine the description of the error described bySystem-message, and try to determine and fix thecause of the error. Check the possibilities listedunder “Explanation.” If you are unable to resolvethe problem, seek assistance from your LanguageEnvironment support personnel.


FOR1502S locator-text The volume volser didnot have enough space availableto create the new data set data-set-name. Fortran Version 2 ErrorNumber: AFB103I (format 1)

ExplanationThe data set data-set-name was to be created usingdynamic file allocation. (Dynamic allocation occurredeither because data-set-name was given in the FILEspecifier on the OPEN statement or because a value ofSCRATCH was given in the STATUS specifier and therewas no corresponding file definition, that is, no DDstatement or ALLOCATE command.) The volume serialnumber volser was given as a value for the VOLSER orVOLSERS argument on the immediately preceding callto the FILEINF callable service, and this disk volumedidn't have the amount of space either indicated bythe CYL, TRK, MAXBLK, or MAXREC argument on theFILEINF call.

locator-text gives more information about the locationof the error, and can be one of the following, wherestatement is the OPEN statement:

• The statement statement for unit unit-number failed.• The INQUIRE statement failed.






Programmer responseTake one or more of these actions:

• If amount of space indicated by the CYL, TRK,MAXBLK, or MAXREC argument on the call to theFILEINF callable service is larger than you need,reduce the value.

• Use a volume other than volser if you know of onethat might have more space.

• Remove the VOLSER or VOLSERS argument on thecall to the FILEINF callable service so that space canbe found on any available disk volume.


FOR1503S locator-text The data set data-set-name had been allocated toanother job and was not available.Fortran Version 2 Error Number:AFB103I (format 2), AFB103I(format 3)

ExplanationThe data set data-set-name was to be connected usingdynamic file allocation. (Dynamic allocation occurredeither because data-set-name was given in the FILEspecifier on the OPEN statement or because a valueof SCRATCH was given in the STATUS specifier andthere was no corresponding file definition, that is, noDD statement or ALLOCATE command.) However, youruse of the data set was denied because one or both ofthese conditions existed:

• Another job had exclusive use of data-set-name.• Another job was using data-set-name but your job

wanted exclusive use of it.

The job, either your job or the other job, that requestedexclusive use of the data set did so in one or more ofthese ways:

• In the immediately preceding call to the FILEINFcallable service, the DISP argument had a value ofNEW, OLD, or MOD.

• On the DD statement the DISP parameter had avalue of NEW, OLD, or MOD.

• The ALLOCATE command had a NEW, OLD, or MODparameter. For a non-VSAM data set or for a VSAMdata set when VSAM record level sharing was notused (that is, there was no RLS parameter on theDD statement, on the ALLOCATE command, or onthe call to FILEINF), either of the following impliedexclusive use of the data set:


• On the OPEN statement the STATUS specifier had avalue of NEW.

• On the OPEN statement the ACTION specifier waseither omitted or had a value of READWRITE orWRITE.








Programmer responseIf you can run the conflicting jobs, or at least theportions of them that use the data set data-set-name,at different times, then schedule the jobs accordingly.

If you must run the conflicting jobs at the same timeand if both need the data set at the same time, thenchange either or both jobs so that they request shareduse of the data set. To do this, take one or more of thefollowing actions, as applicable, in both jobs:

• Change the value of the DISP argument for theFILEINF callable service to SHR.

• Change the value of the DISP parameter on the DDstatement to SHR.

• Remove the NEW, OLD, or MOD parameter on theALLOCATE command and replace it with SHR. Fora non-VSAM data set or for a VSAM data set whenVSAM record level sharing is not used:

• Change the value of the STATUS specifier on theOPEN statement to OLD.

• Change the value of the ACTION specifier on theOPEN statement to READ.

Note that except when VSAM record level sharing isused, the changes listed don't allow a file to be creatednor do they allow either job to update the file.


FOR1504S locator-text The volume volser,which should have contained thedata set data-set-name, could notbe found. Fortran Version 2 ErrorNumber: AFB103I (format 4)

ExplanationThe data set data-set-name was to be connected usingdynamic file allocation. (Dynamic allocation occurredeither because data-set-name was given in the FILEspecifier on the OPEN statement.) The volume serialnumber volser was given as a value for the VOLSER orVOLSERS argument on the immediately preceding callto the FILEINF callable service, but this disk volumewasn't available.








Programmer responseEnsure that volume serial number given as the valueof the VOLSER or VOLSERS argument on the call tothe FILEINF callable service is one that resides on thedevice given by the DEVICE argument.

If the data set is cataloged, you don't need to specifythe volume serial number, so remove the VOLSER orVOLSERS argument.



FOR1505S locator-text An incorrect devicename, dev-name, was specifiedfor the data set data-set-name.Fortran Version 2 Error Number:AFB103I (format 5)

ExplanationThe data set data-set-name was to be connected usingdynamic file allocation. (Dynamic allocation occurredeither because data-set-name was given in the FILEspecifier on the OPEN statement or because a value ofSCRATCH was given in the STATUS specifier and therewas no corresponding file definition, that is, no DDstatement or ALLOCATE command.) The device namedev-name was given either as the value for the DEVICEargument on the immediately preceding call to theFILEINF callable service or as the default value thatwas established during the installation of LanguageEnvironment. However, this device name wasn't knownon your system.








Programmer responseEnsure that the value given for the DEVICE argumentin the call to the FILEINF callable service is a validdevice on your system. If you didn't provide theDEVICE argument, then dev-name was the defaultvalue assigned during the installation of LanguageEnvironment. In this latter case or if you areunable to resolve the problem, seek assistance fromyour Language Environment support personnel todetermine the device names that can be used at yoursite.

You can code the device name in the same three waysthat you can code this same information in the UNITparameter on the DD statement:

• A three-character hexadecimal number of thedevice. For example, 130.

• The generic name of the device that identifies adevice by machine type and model. For example,3380.

• A group name, which identifies a group of devices bya symbolic name. For example, SYSDA.


FOR1506S locator-text The volume did nothave enough space for thedirectory for the data set data-set-name. Fortran Version 2 ErrorNumber: AFB103I (format 6)

ExplanationThe data set data-set-name was to be created usingdynamic file allocation. (Dynamic allocation occurredbecause data-set-name was given in the FILE specifieron the OPEN statement.) The data set was to be apartitioned data set (PDS) and the number of directoryblocks was given as the value of the DIR argumenton the immediately preceding call to the FILEINFcallable service. However, the number of directoryblocks was so large that there wasn't enough spacefor the whole directory on the volume given by theVOLSER or VOLSERS argument, if any, on the FILEINFcall.










• If the number of directory blocks indicated by theDIR argument on the call to the FILEINF callableservice is larger than you need, reduce the value.

• On the VOLSER or VOLSERS argument on the callto FILEINF, specify a volume that might have morespace.


FOR1507S locator-text The space requestedfor the directory was greater thanthe amount of primary spacerequested for the data set data-set-name. Fortran Version 2 ErrorNumber: AFB103I (format 7)

ExplanationThe data set data-set-name was to be created usingdynamic file allocation. (Dynamic allocation occurredbecause data-set-name was given in the FILE specifieron the OPEN statement.) The data set was to be apartitioned data set (PDS) and the number of 256-byte directory blocks was given as the value of theDIR argument on the immediately preceding call tothe FILEINF callable service. However, the number ofdirectory blocks was so large that it wouldn't fit intothe amount of disk space indicated by the CYL, TRK,MAXBLK, or MAXREC argument on the call to FILEINF.



where statement is the OPEN statement.







• If the number of directory blocks indicated by theDIR argument on the call to the FILEINF callableservice is larger than you need, reduce the value.

• Increase the amount of disk space indicated by theCYL, TRK, MAXBLK, or MAXREC argument on the callto FILEINF. Ensure that you have available to you adisk volume with enough space to allocate a data setof this size.


FOR1508S locator-text A required catalog wasnot available for the data set data-set-name. Fortran Version 2 ErrorNumber: AFB103I (format 8)

ExplanationThe data set data-set-name was to be referencedusing dynamic file allocation. (Dynamic allocationoccurred because data-set-name was given in the FILEspecifier on the OPEN statement.) However, a catalogin which the data set was supposed to be catalogedwasn't available.








Programmer responseIf the data set was created using Access MethodServices and if the CATALOG parameter was usedon the DEFINE command. then supply a JOBCAT


or STEPCAT DD statement that refers to that samecatalog.

In this doesn't resolve the problem, seek assistancefrom your Language Environment support personnel.


FOR1509S locator-text The catalog did nothave enough space to add an entryfor the data set data-set-name.Fortran Version 2 Error Number:AFB103I (format 9)

ExplanationThe data set data-set-name was to be created usingdynamic file allocation. (Dynamic allocation occurredbecause data-set-name was given in the FILE specifieron the OPEN statement.) However, there wasn'tenough space available in a catalog for the new dataset to be cataloged.



where statement is the OPEN statement.






Programmer responseSeek assistance from your Language Environmentsupport personnel.


FOR1510S locator-text The data set data-set-name could not be dynamicallyallocated because the limit hadbeen reached for the number ofdynamically allocated files thatcould be in use at the same time.Fortran Version 2 Error Number:AFB169I (format 2)

ExplanationThe data set data-set-name was to be referencedusing dynamic file allocation. (Dynamic allocationoccurred either because data-set-name was given inthe FILE specifier on the OPEN statement or becausea value of SCRATCH was given in the STATUS specifierand there was no corresponding file definition, that is,no DD statement or ALLOCATE command.) All possibleddnames that can be used for dynamic allocated fileswere in use, so no more files could be dynamicallyallocated.








Programmer responseReduce the number of dynamically allocated files.

If you've happened to use ddnames of either of theseforms:

• sDFnnnnn• DFsnnnnn

where s is @, #, or $, and nnnnn is in the rangefrom 00000 to 99999, then don't use these asddnames of your own because they are what Language


Environment uses internally for dynamically allocatedfiles.


FOR1511S locator-text A permanent I/O errorwas detected while searchingthe partitioned data set (PDS)directory for file-name. FortranVersion 2 Error Number: AFB219I(format 11)






Programmer responseEnsure that the following are true:

• The data set was a PDS.• The data set name wasn't used without a member

name for input/output operations. Violating thisrestriction might have caused the directory to beoverwritten.

• There weren't two different members in the data setbeing used for output operations at the same time.


FOR1550S locator-text The SVC 99 functionexecuted for the data set data-set-name had a return codeof return-code and an errorreason code of reason-code.System-message Seek assistancefrom your Language Environmentsupport personnel. Fortran Version2 Error Number: AFB103I (format10)

ExplanationThe data set data-set-name was to be referencedusing dynamic file allocation. (Dynamic allocationoccurred either because data-set-name was given inthe FILE specifier on the OPEN statement or becausea value of SCRATCH was given in the STATUS specifierand there was no corresponding file definition, thatis, no DD statement or ALLOCATE command.) Theinternally executed SVC 99 service, which performsthe dynamic allocation, detected the error reflected byreturn code return-code and error reason code reason-code. It also provided System-message to explain theerror.








Programmer responseFor the meaning of return code return-code and errorreason code reason-code, refer to z/OS DFSMS MacroInstructions for Data Sets.



FOR1551W locator-text The SVC 99 functionexecuted for the data set data-set-name was successful, butan unusual condition occurred.The information reason code wasinformation-code. System-message


Fortran Version 2 Error Number:AFB103I (format 10)

ExplanationThe data set data-set-name was to be referencedusing dynamic file allocation. (Dynamic allocationoccurred either because data-set-name was givenin the FILE specifier on the OPEN statement orbecause a value of SCRATCH was given in theSTATUS specifier and there was no correspondingfile definition, that is, no DD statement or ALLOCATEcommand.) The internally executed SVC 99 service,which performs the dynamic allocation, detectedan exceptional situation (not necessarily an error)reflected by information code information-code. It alsoprovided System-message to explain the situation.



System actionThe file is allocated or deallocated, and executioncontinues.



RN Execution resumes.

Programmer responseFor the meaning of information code information-code,refer to z/OS DFSMS Macro Instructions for Data Sets.



FOR1552C The SVC 99 function executedfor the file file-name duringenclave initialization had a returncode of return-code and anerror reason code of reason-code.System-message Seek assistancefrom your Language Environmentsupport personnel. Fortran Version2 Error Number: AFB936I (format2)

ExplanationDynamic allocation occurred for the print unit, filename file-name, because there was no correspondingfile definition, that is, no DD statement or ALLOCATEcommand. The internally executed SVC 99 service,which performs the dynamic allocation, detected theerror reflected by return code return-code and errorreason code reason-code. It also provided System-message to explain the error.

System actionThe condition is signaled, and execution of the enclaveterminates.






FOR1553C The SVC 99 function executedfor the file file-name duringenclave termination had a returncode of return-code and anerror reason code of reason-code.System-message Seek assistancefrom your Language Environmentsupport personnel. Fortran Version2 Error Number: AFB936I (format3)

ExplanationDynamic allocation had occurred earlier for the printunit, file name file-name, because there was nocorresponding file definition, that is, no DD statementor ALLOCATE command. Then during termination,the deallocation of this file occurred. The internallyexecuted SVC 99 service, which performs the dynamicallocation, detected the error reflected by return codereturn-code and error reason code reason-code. It alsoprovided System-message to explain the error.


System actionThe condition is signaled, and execution of the enclaveterminates.






FOR1554S locator-text The macro-namemacro instruction executed forfile-name had a return code ofreturn-code and a reason codeof reason-code. Seek assistancefrom your Language Environmentsupport personnel. Fortran Version2 Error Number: AFB091I,AFB225I (format 5), AFB219I(format 9)

ExplanationIn support of the Fortran I/O statement indicatedby the message text, Language Environmentexecuted a non-VSAM macro-name macro instruction.DFSMS/MVS detected the error indicated by returncode return-code and reason code reason-code.








Programmer responseFor the meaning of return code return-code andreason code reason-code, refer to z/OS DFSMS MacroInstructions for Data Sets. If you are unable to resolvethe problem, seek assistance from your LanguageEnvironment support personnel.


FOR1557S locator-text The VSAM macro-namemacro instruction executed forfile-name had a return codeof return-code. Seek assistancefrom your Language Environmentsupport personnel. Fortran Version2 Error Number: AFB111I (format4), AFB130I, AFB167I

ExplanationIn support of the Fortran I/O statement indicated bythe message text, Language Environment executeda VSAM macro-name macro instruction. DFSMS/MVSdetected the error indicated by return code return-code.



System actionIf the error occurred during enclave termination orfrom a CLOSE statement, the file is disconnected, butnot deleted (as though the STATUS specifier had beencoded with a value of KEEP). If the error occurredduring the execution of an OPEN statement, the unitis no longer connected to a file.

If neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. If thecondition is unhandled, the application is terminated.






Programmer responseFor the meaning of return code return-code refer toz/OS DFSMS Macro Instructions for Data Sets. If youare unable to resolve the problem, seek assistancefrom your Language Environment support personnel.


FOR1558S locator-text The VSAM macro-namemacro instruction executed forfile-name had a return code ofreturn-code and an error code ofX'hex-code' (decimal-code). Seekassistance from your LanguageEnvironment support personnel.Fortran Version 2 Error Number:AFB111I (format 4), AFB130I,AFB167I

ExplanationIn support of the Fortran I/O statement indicated bythe message text, Language Environment executeda VSAM macro-name macro instruction. DFSMS/MVSdetected the error indicated by the return code return-code and the error code with a hexadecimal value ofhex-code (decimal value of decimal-code).









Programmer responseFor the meaning of return code return-code and errorcode hex-code (or decimal-code), refer to z/OS DFSMSMacro Instructions for Data Sets. If you are unableto resolve the problem, seek assistance from yourLanguage Environment support personnel.


FOR1559S locator-text There was a systemcompletion code of completion-code involving file file-name. Seekassistance from your LanguageEnvironment support personnel.Fortran Version 2 Error Number:AFB111I (format 1), AFB225I(format 4)

ExplanationIn support of the Fortran I/O statement indicated bythe message text, Language Environment executed adata management macro instruction such as OPEN,READ, WRITE, or CHECK. Either MVS or DFSMS/MVSdetected the error indicated by the system completion(abend) code completion-code.










Programmer responseEnsure that the file definition (DD statement orALLOCATE command) for the file you are using iscoded correctly. If the the program uses dynamicallocation for the file, ensure that both the dataset name given in the FILE specifier on the OPENstatement and the arguments on call to the FILEINFcallable service are coded correctly.

For the meaning of completion-code and for possiblecorrective actions, refer to z/OS DFSMS MacroInstructions for Data Sets.


FOR1560S locator-text There was a systemcompletion code of completion-code and a reason code of reason-code involving file file-name. Seekassistance from your LanguageEnvironment support personnel.Fortran Version 2 Error Number:AFB111I (format 1), AFB225I(format 4), AFB219I (format 10)

ExplanationIn support of the Fortran I/O statement indicated bythe message text, Language Environment executed adata management macro instruction such as OPEN,READ, WRITE, or CHECK. Either MVS or DFSMS/MVSdetected the error indicated by system completion(abend) code completion-code and reason codereason-code.










For the meaning of system completion codecompletion-code and reason code reason-code, and forpossible corrective actions, refer to z/OS DFSMS MacroInstructions for Data Sets.


FOR1563S The statement statement for unitunit-number, which was connectedto file-name, failed. A block thatwas read had an unexpectedlength. Fortran Version 2 ErrorNumber: AFB091I

ExplanationIn a record of the file being read, there were one mormore of the following inconsistencies:

• The record format was either V, VS, D, VB, VBS,or DB, and the block descriptor did not match theactual block size.

• The record format was either V, VS, D, VB, VBS, orDB, and the record descriptor implied that the recordextended past the end of the block.

• The record format was VBS, and a record descriptorvalue was too small; that is, it implied no data but itwas not a valid VBS null segment.

• The record format was D, and the actual block sizedid not exceed the specified block size.

• The record format was FB with a block preface, andthe actual block size did not exceed the specifiedblock preface size.


• The record format was FB, and the last recordextended beyond the end of the block.

(The record format refers to the RECFM value that isprovided either in the file definition (DD statement orALLOCATE command) or in the label of an existing file.)






Programmer responseEnsure that the file definition (DD statement orALLOCATE command) for the file you are using iscoded correctly in the following ways:

• The file definition refers to the data set that you wantto process.

• The RECFM value, if any, indicates the same recordformat that was specified when the file was created.

• The LRECL value, if any, indicates the same recordlength that was specified when the file was created.

• The BLKSIZE value, if any, indicates the same blocklength that was specified when the file was created.

Ensure that the file was closed successfully when itwas created. If it wasn't, then the file must be createdagain because the last block might not have beenwritten correctly.


FOR1570S locator-text The file definition withthe ddname ddname was missing.Fortran Version 2 Error Number:AFB219I (format 1), AFB219I(format 7)

ExplanationThere was no file definition (DD statement orALLOCATE command) with the ddname implied by theI/O statement.








Programmer responseDetermine the ddname implied by the I/O statement,and provide a DD statement or ALLOCATE commandwith this ddname.

If the file is an unnamed file, then the ddname takesthe form FTnnF001 for sequential and direct accessfiles and the form FTnnKmm for keyed access files,where nn is the unit number. A file is an unnamed filein either of these cases:

• The OPEN statement that connects the unit and thefile has no FILE specifier.

• The unit is seen as preconnected to a file becausea sequential I/O statement is executed for the unitbefore an OPEN statement.

If the file is a named file, then the ddname hasthe value given for the FILE specifier on the OPENstatement.

If you want to refer to the file through dynamicallocation, then ensure that there is an OPENstatement with a FILE specifier whose value consistsof a slash ( / ) followed by the data set name. In thiscase, no file definition is needed.

If the OPEN statement has no FILE specifier and youwant that OPEN statement to refer to an existingconnection between the unit and a file, then ensurethat the unit is already connected to a file beforethe OPEN statement is executed. (Failure to observethis restriction could cause the OPEN statement to beinterpreted as referring to an unnamed file.)



FOR1571S locator-text The OPEN macroinstruction executed for file-namehad a system completion code ofcompletion-code and a reason codeof reason-code. Seek assistancefrom your Language Environmentsupport personnel. Fortran Version2 Error Number: AFB219I (format1)

ExplanationIn support of the Fortran I/O statement indicated bythe message text, Language Environment executed anOPEN macro instruction. Either MVS or DFSMS/MVSdetected the error indicated by system completion(abend) code completion-code and reason codereason-code.









For the meaning of system completion codecompletion-code and reason code reason-code, and for

possible corrective actions, refer to z/OS DFSMS MacroInstructions for Data Sets.


FOR1900E locator-text The file file-namewas to be deleted, but the filedefinition referred to a file ordevice for which file deletion wasnot possible. Fortran Version 2Error Number: AFB105I, AFB111I(format 2)

ExplanationOne of the following implied that the file deletion wasto occur:

• The CLOSE statement had a STATUS specifier with avalue of DELETE.

• The CLOSE statement referred to a unit for whichthe corresponding OPEN statement had a STATUSspecifier with a value of SCRATCH.

• During enclave termination, a unit was stillconnected to a file for which the correspondingOPEN statement had a STATUS specifier with a valueof SCRATCH.

In addition, the OCSTATUS run-time option was ineffect, and the file had a characteristic, such as oneof the following, that precluded file deletion:

• VSAM data set that is not empty and that is notreusable

• Unlabeled tape data set• In-stream (DD *) data set• Sysout data set• Terminal• Unit record input data set• Unit record output data set• Subsystem file• Concatenation of multiple data sets• Keyed file with an alternate index• LABEL=(,,,IN) parameter on the DD statement• IN parameter on the ALLOCATE command• Multiple sub-files• Connected with an OPEN statement that had an

ACTION specifier with a value of READ


• The statement statement for unit unit-number failed.


• The INQUIRE statement failed.• An error occurred during enclave termination.

System actionThe file is disconnected, but not deleted (as thoughthe STATUS specifier on the CLOSE statement hadbeen coded with a value of KEEP). If neither theERR nor the IOSTAT specifier is present on the I/Ostatement, the condition is signaled. If the condition isunhandled, the application is terminated.




RN The file is closed but not deleted, and executioncontinues.

Programmer responseIf file deletion is required so that further use of thefile isn't possible, then change one or more of thefollowing to avoid referring to a file with any of thecharacteristics listed under “Explanation”:

• The value of the ACTION specifier on the OPENstatement to either WRITE or READWRITE

• The value of the FILE specifier on the OPENstatement to refer to some other ddname

• The value of the FILE specifier on the OPENstatement to refer to some other data set name

• The value of the UNIT specifier on the OPENstatement to refer to some other Fortran unitnumber

• The DD statement parameters such as the referenceto a particular device or data set

• The ALLOCATE command parameters such as thereference to a particular device or data set

• The reusability attribute of a VSAM data set in theAccess Method Services DEFINE CLUSTER command

• The combination of DD statements or ALLOCATEcommand parameters that concatenate multipledata sets under a single ddname

If file deletion isn't required, then either use theNOOCSTATUS run-time option, or modify the programin one or more of the following ways so that filedeletion won't occur:

• On the OPEN statement, either omit the STATUSspecifier or provide a value other than SCRATCH.

• On the CLOSE statement, either omit the STATUSspecifier or provide a value other than DELETE.


FOR1910S locator-text The end of the file wasreached. Fortran Version 2 ErrorNumber: AFB200I, AFB217I

ExplanationThe execution of the READ statement requested thata record be read even though the file was alreadypositioned beyond the last data record in the file.

This is the end-of-file condition and might not be anerror.

For a READ statement that specified namelistformatting, this also could have occurred for thefollowing reason: For the namelist group name givenin the FMT specifier on the READ statement, therewas no corresponding namelist group in the inputfile at a point beyond where the file was alreadypositioned. Some syntax error within the input file,such as a missing &END delimiter or a missing quote orapostrophe delimiter, might have caused the namelistgroup to treated as part of some other construct andthus appear as though it wasn't in the input file.




where statement is READ.

System actionIf the IOSTAT=ios specifier is present on the READstatement, ios becomes defined either with the value-1 if ios is an integer variable or with the conditiontoken for FOR1910 if ios is a character variable oflength 12. If the END=stl specifier is present on theREAD statement, control passes to the label stl. Ifneither the END nor the IOSTAT specifier is present onthe READ statement, the condition is signaled. If thecondition is unhandled, the application is terminated.







RF If the error occurred on a READ statement for sequentialaccess to an unnamed file that is neither VSAM norstriped, the data set sequence number is increased by1 and the next subfile is read; otherwise, executioncontinues.

Programmer responseEnsure that the READ statement refers to the unitthat you intended, that the unit is connected to thefile that you intended, and that the file definition(DD statement or ALLOCATE command) or the dataset name given in the FILE specifier on the OPENstatement refers to the file that you intended. Alsoensure that the file was created successfully, eitherin a program or by some manual process such as aneditor.

If the file is the one you want to read, modify theprogram to detect the end of the file in one of theseways:

• Use the END specifier on the READ statement so thatyour program can gain control at some specific labelwhen the end-of-file condition occurs.

• Use the IOSTAT specifier on the READ statementso that upon completion of the READ statementyour program can determine whether the end-of-filecondition occurred. A value of -1 in the variable givenin the IOSTAT specifier indicates that the end-of-filecondition occurred.

• If you know the number of records in the file beforereading them, maintain a count of the number ofrecords read so that your program doesn't attempt toread beyond the last data record.

If your program uses statements that position thefile, ensure that the logic of the program and thecontents of the file don't cause the file to beinadvertently positioned to the wrong place. Thefollowing statements affect the position within the file:

• ENDFILE• BACKSPACE• REWIND• OPEN with a POSITION specifier that has a value of

APPEND• READ statement, even with no input item list• READ statement with a format specification that has

a slash (/) edit descriptor• WRITE, which for sequential access causes the

record that's written to become the last record in thefile

In addition, if the DD statement has the DISP=MODparameter or the ALLOCATE command has the MOD

parameter, the file is positioned beyond the last datarecord when it's first connected.

If namelist formatting is requested on the READstatement because the FMT specifier refers to thea namelist group name declared in a NAMELISTstatement, ensure that the namelist group indicatedby the FMT specifier is actually in the file at some pointbeyond the current position. (There's no attempt toread through the entire file to find the namelist group;the search is only from the current file position.) Inthe file, identify the namelist group with an ampersand( & ) followed by the namelist group namewith no intervening blanks. Ensure that the ampersandbegins in position 2 or later, and that all positionspreceding the ampersand in the record are blank.

In a namelist input file, ensure that all namelistgroups, especially any that precede the one referencedby the failing READ statement, are coded in the correctformat. Remember that all information must start noearlier than position 2 of the records. Pay attention toall delimiters, such as commas, equal signs, quotes,and apostrophes, to ensure that they are used asrequired. Also ensure that each namelist group isended by the characters &END.


FOR1915S The OPEN statement for unit unit-number failed. The FILE specifierwas not given, and the unitnumber was greater than 99, themaximum unit number allowed forunnamed files. Fortran Version 2Error Number: AFB175I

System actionIf neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. If thecondition is unhandled, the application is terminated.The statement is ignored, and processing continues.

Qualifying Data: Only the basic set of four qualifyingdata for I/O conditions as shown in Table 1 on page272. Within this basic set, file has a value of blanks,and parm_count has a value of 4.





Programmer responseIf you want to connect an unnamed file, ensure thatthe value given for the the unit number does notexceed the smaller of either 99 or the highest unitnumber allowed at your site.

If you want to connect a named file, add a FILEspecifier to the OPEN statement and provide either addname or a data set name, the latter preceded by aslash ( / ).

If you want the OPEN statement to refer to an existingconnection between a unit and a file (so that you canuse one or more of the BLANK, CHAR, DELIM, and PADspecifiers to change the properties of the connection),then ensure that the unit is connected to a file beforeexecuting the OPEN statement.


FOR1916S The statement statement forunit unit-number failed. The unitnumber was either less than 0or greater than max-unit-num, thehighest unit number allowed atyour installation. Fortran Version 2Error Number: AFB220I

System actionIf neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. If thecondition is unhandled, the application is terminated.The statement is ignored, and execution continues.

Qualifying Data: Only the basic set of four qualifyingdata for I/O conditions as shown in Table 1 on page272. Within this basic set, file has a set of blanks, andparm_count has a value of 5. In addition, there arethese qualifying data:

No.

Name Input/Output

Data Type andLength

Value

5 max-unit-name

Input INTEGER*4 Highest unit numberallowed at yourinstallation.




Programmer responseEnsure that the unit number given on the statementstatement is a positive number that doesn't exceed

max-unit-num, which was established during theinstallation or customization of Language Environmentas the highest unit number available at your site.

The defaults provided by IBM have 99 as the highestunit number. However, this can be changed byupdating the UNTABLE parameter of the AFHOUTCMmacro instruction in the module AFHOUTAG. Formore information, refer to z/OS Language EnvironmentCustomization.


FOR1917S The statement statement could notbe executed for unit unit-number.The unit was not connected toa file. Fortran Version 2 ErrorNumber: AFB110I






Programmer responseEnsure that the statement statement refers to the unitthat you intended.

Check the logic of your program to ensure that the unitunit-number is connected to a file before executing thestatement statement. Here are some items to examineor correct:

• Determine whether some error occurred. An errordetected for an OPEN statement, for example,usually causes the unit to be disconnected from thefile. If such an error occurred, correct the problem.

• Ensure that a CLOSE statement did not disconnectthe unit from the file. If it did, then either executean OPEN statement to reconnect the unit to a file ordon't execute the CLOSE statement.

• If you want to use a preconnected file, that is, onethat can be read or written without first executingan OPEN statement, then ensure that there's a filedefinition (DD statement or ALLOCATE command)


with a ddname FTnnF001, where nn is the two-digitunit number.

• If you want to use a unit number greater than 99,then use an OPEN statement to connect a named fileto the unit. To connect a named file, provide the FILEspecifier on the OPEN statement.

It's possible for the statement statement used forsequential access to automatically reconnect a unitto an unnamed file. To do this, ensure that theseconditions are met:

• The unit number doesn't exceed 99.• There's a file definition with the ddname FTnnF001,

where nn is the two-digit unit number. This is the fileto which the unit will be reconnected.

• The NOOCSTATUS run-time option is in effect.


FOR1920S The statement statement for unitunit-number, which was connectedto file-name, failed. The filedefinition referred to a file ordevice that was restricted toinput only. Fortran Version 2 ErrorNumber: AFB108I (format 7)

ExplanationThe statement is an output statement, but the filedefinition (DD statement or ALLOCATE command) orthe data set name given in the FILE specifier onthe OPEN statement referred to a file or device thatdoesn't allow output operations. Examples of suchfiles include:



(such as RACF) prevents you from updating the dataset






Programmer responseEnsure that I/O statement to be executed is consistentwith the capabilities of the file or device referencedby the file definition (DD statement or ALLOCATEcommand) or by the data set name given in the FILEspecifier on the OPEN statement. You might have tochange either the file definition, the data set name, orthe I/O statements used to process the file.

If you want to perform output operations on a file,don't refer to an input-only data set such as an in-stream data set (DD *), a data set for which you don'thave RACF authority to update, or a data set whose DDstatement has a LABEL=(,,,IN) parameter.


FOR1921S The statement statement for unitunit-number, which was connectedto file-name, failed. Execution ofthis statement was inconsistentwith the ACTION specifier on theOPEN statement, which had avalue of action. Fortran Version 2Error Number: AFB122I






Programmer responseEither change the value of the ACTION specifier on theOPEN statement that connected the unit to the file,or change the logic of your program so that you don'texecute a statement that isn't allowed by the valuethat you provide for the ACTION specifier. Also ensurethat the ACCESS specifier has a value that indicatesthe type of file access that you want to use. Here are


the permissible statements based on the values of theACTION specifier and of the ACCESS specifier:

ACTIONSpecifier

ACCESSSpecifier

Permissible Input/OutputStatements

READ SEQUENTIALKEYED

READ, BACKSPACE, REWIND,CLOSE with STATUS='KEEP'

READ DIRECT READ, CLOSE with STATUS='KEEP'

READWRITE SEQUENTIAL READ, BACKSPACE, REWIND,WRITE, ENDFILE, CLOSE withSTATUS='KEEP'

READWRITE DIRECT READ, WRITE, CLOSE with anySTATUS value

READWRITE KEYED READ, BACKSPACE, REWIND,WRITE, REWRITE, DELETE, CLOSEwith any STATUS value

WRITE SEQUENTIAL WRITE, ENDFILE, CLOSE with anySTATUS value

WRITE DIRECT WRITE, CLOSE with any STATUSvalue

WRITE KEYED WRITE, CLOSE withSTATUS='KEEP'


FOR1922S The statement statement for unitunit-number, which was connectedto file-name, failed. The file wasnot usable because a permanentI/O error was detected FortranVersion 2 Error Number: AFB152I






Programmer responseDetermine the cause of the error on some previous I/Ostatement that was executed for this unit, and correctthe problem.

To continue using a file connected for sequentialaccess after an error has occurred, execute a REWINDstatement.

To use the same unit or file through a newlyestablished file connection, execute a CLOSEstatement followed by an OPEN statement.


FOR1923S The statement statement for unitunit-number, which was connectedto file-name, failed. An implied DOin the input or output item listinconsistently specified the initial,terminal, and increment values.The initial value was initial-value; the terminal value wasterminal-value, and the incrementvalue was increment-value. FortranVersion 2 Error Number: AFB203I

ExplanationIn the input or output item list of a READ or WRITEstatement there was an implied DO, such as thefollowing:

( A(I), I = initial-value, terminal-value, increment-value)

For one of the levels of nesting in the implied DO,the combination of initial-value, terminal-value, andincrement-value was incorrect in one of these ways:

• increment-value = 0• terminal-value &lt initial-value and increment-value

> 0• terminal-value > initial-value and increment-value <

0






Programmer responseEnsure that the combination of the initial value,terminal value, and increment value in the implied DO


doesn't have any of the inconsistencies listed under“Explanation” for any level of nesting.


FOR1924S The statement statement for unitunit-number failed. The statementwas executed from within an MTFparallel subroutine and referred toan unnamed file. Fortran Version 2Error Number: AFB923I

System actionIf neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition is signaled. Ifthe condition is unhandled either in the parallelsubroutine or in the main task program, the applicationis terminated.





Programmer responseChange the MTF parallel subroutine so that theI/O statements refer only to named rather than tounnamed files. A file is an unnamed file in either ofthese cases:

• The OPEN statement that connects the unit and thefile has no FILE specifier.

• The unit is seen as preconnected to a file becausea sequential I/O statement is executed for the unitbefore an OPEN statement. (Except for the standardinput unit, the error message unit, and the printunit, preconnected files don't exist in an MTF parallelsubroutine.)

A file is a named file if the OPEN statement thatconnects the unit and the file has a FILE specifier.Therefore, in the parallel subroutine include the FILEspecifier on each OPEN statement that's used toconnect a unit to a file.

If the OPEN statement has no FILE specifier and youwant that OPEN statement to refer to an existingconnection between the unit and a file, then ensurethat the unit is already connected to a file beforethe OPEN statement is executed. (Failure to observe

this restriction could cause the OPEN statement to beinterpreted as referring to an unnamed file.)


FOR1925S The statement statement forunit unit-number, which was theerror message unit, failed. Thestatement or the form of thestatement that was used is notpermitted for the error messageunit. Fortran Version 2 ErrorNumber: AFB234I

ExplanationThe statement statement referred to the error messageunit and therefore to the Language Environmentmessage file, but was other than one of the followingstatements that is allowed to refer explicitly to theerror message unit:

• OPEN statement• INQUIRE statement• CLOSE statement• WRITE statement for sequential access and

formatted I/O

The following statements refer to the print unit. Theyare allowed to refer implicitly to the error message unitwhen the error message unit and the print unit are thesame unit:

• PRINT statement• WRITE statement that has * as the unit identifier






Programmer responseChange the program so that if you refer to the errormessage unit you use only the statements or forms


of statements listed under “Explanation.” For example,do not use these statements:

• WRITE statement for direct access (REC specifier)• WRITE statement for keyed access (KEY specifier)• WRITE statement for asynchronous I/O (ID specifier)• WRITE statement for unformatted I/O (no formatspecifier)

• ENDFILE statement• REWIND statement• BACKSPACE statement• DELETE statement• REWRITE statement

If you need to use any of the prohibited statementsor forms of statements, change the unit specifier torefer to some unit other than the error message unit. Ifyou need only the BACKSPACE, REWIND, or ENDFILEstatements in conjunction with output that's directedto the print unit (rather than explicitly to the errormessage unit), then take both of the following actions:

• Use the ERRUNIT and PRTUNIT run-time options todefine the error message unit and the print unit asdifferent units.

• On the BACKSPACE, REWIND, or ENDFILEstatement, provide a unit number that is the sameas what you've used as the value of the PRTUNITrun-time option.


FOR1926S locator-text The file name was file-name. The immediately previousinvocation of the FILEINF callableservice failed. Fortran Version 2Error Number: AFB219I (format 9)






Programmer responseDetermine the cause of the error that caused theprevious call to the FILEINF callable service to fail;then correct the problem.

If the call to the FILEINF callable service doesn't needto be used for the OPEN or INQUIRE statement, thenremove the call.


FOR1927S An I/O statement was executed,but some other I/O statement hadnot yet completed. Fortran Version2 Error Number: AFB904I

ExplanationThere was a recursive call to the Fortran input/outputlibrary routines that are part of Language Environment.Here are some situations that could have caused therecursive call:

• Within the input item list on a READ statementthere was a reference to a user-written function thatperforms some other I/O operation. To illustrate thissituation, here is an example of a READ statementwith a function reference:

READ (8) I, A(INXFUNC(I))

This is an example of the referenced functionsubprogram with a PRINT statement whoseexecution causes error FOR1927 to be detected:

FUNCTION INXFUNC ( X )INTEGER*4 INXFUNCINTEGER*4 XIF ( X .GT. 4 ) THEN PRINT *, ’INCORRECT SUBSCRIPT VALUE. ASSUMING 1.’ INXFUNC = 1ELSE INXFUNC = XENDIFEND

• As a result of some error that was detected duringthe execution of a Fortran I/O statement, thefollowing occurred:

1. The condition representing the error wassignaled.

2. Assuming that a user-written condition handlerhad been registered before the I/O statementwas executed, the condition handler was entered.This condition handler included a Fortransubprogram.

3. The Fortran subprogram executed a PRINTstatement to report the error.

The condition handling was considered to be asubordinate part of the original failing I/O statement.


Therefore, execution of the PRINT statement in thecondition handler caused the prohibited recursiveentry into the input/output library and thus causederror FOR1927 to be detected.

System actionThe ERR and IOSTAT specifiers are not honored. Thecondition is signaled. If the condition is unhandled, theapplication is terminated.

Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 4

2 statement

Input CHARACTER*12 Name of the I/Ostatement beingprocessed


4 file Input CHARACTER*62 Undefined


Programmer responseRestructure the program to avoid the recursive entryinto the Fortran input/output library.


FOR1928S During execution of an I/Ostatement that had an IOSTATspecifier, a condition occurredfrom the internal use of someLanguage Environment callableservice.

ExplanationSome unusual condition occurred during the executionof an I/O statement that had an IOSTAT=ios specifier,where ios was an INTEGER*4 variable. This conditionwasn't one that was detected by the Fortran libraryportion of Language Environment but rather by oneof the internally used routines that are part ofLanguage Environment. Because the IOSTAT specifierwas present, this condition was not signaled. Instead,a value of 1928 was returned in ios.

(If ios had been a character variable of length 12,the condition token reflecting the condition that wasdetected would have been returned. If the IOSTATspecifier had not been present, that condition wouldhave been signaled.)

System actionIf the IOSTAT=ios specifier is present on the I/Ostatement, and if ios is an integer variable, the value1928 is returned in ios. If ios is a character variable oflength 12, the condition token that reflects the errorthat was detected by the internally executed callableservice is returned in ios.

If neither the ERR nor the IOSTAT specifier is presenton the I/O statement, the condition detected by theinternally executed callable service is signaled. If thecondition is unhandled, the application is terminated.



Programmer responseIf there isn't some obvious problem involving eitherthe I/O statement, the file definition (DD statement orALLOCATE command), or the virtual storage availableto the application, remove (at least temporarily) theIOSTAT specifier. Then the condition reflecting theproblem that was detected will be signaled.


FOR1929S The statement statement for unitunit-number, which was connectedto file-name, failed. The ADVANCEspecifier had a value of advance,which was other than YES or NO.






Programmer responseBased on whether you want to use advancing ornonadvancing input/output, change the value of theADVANCE specifier on the statement statement to YESor NO. If you code the value as a character constant,enclose the value in quotes or apostrophes.



FOR1930S The statement statement for unitunit-number, which was connectedto file-name, failed. The EORspecifier was provided on aformatted READ statement thatdid not have an ADVANCE specifierwith the value NO.






Programmer responseIf you want to use the advancing READ statement,that is, the conventional form of the READ statement,remove the EOR specifier from the READ statement.Also remove the SIZE specifier if it is present.

If you want to use nonadvancing input/output, thenon the READ statement provide an ADVANCE specifierwith a value of NO. If you code the value as a characterconstant, enclose the value in quotes or apostrophes.


FOR1931S The statement statement for unitunit-number, which was connectedto file-name, failed. The SIZEspecifier was provided on aformatted READ statement thatdid not have an ADVANCE specifierwith the value NO.






Programmer responseIf you want to use the advancing READ statement,that is, the conventional form of the READ statement,remove the SIZE specifier from the READ statement.Also remove the EOR specifier if it is present.

If you want to use nonadvancing input/output, thenon the READ statement provide an ADVANCE specifierwith a value of NO. If you code the value as a characterconstant, enclose the value in quotes or apostrophes.


FOR2000C The MTF parallel subroutine loadmodule module-name, the nameof which was specified in theAUTOTASK run-time option, didnot exist in the load libraryspecified by the AUTOTASKfile definition statement. VSFORTRAN Version 2 Error Number:AFB919I-1

System actionThe condition is signaled, and the application isterminated.



Programmer responseEnsure that your multitasking facility (MTF) parallelsubroutine load module was link-edited as a memberof the partitioned data set referenced by the filedefinition (DD statement or ALLOCATE command) withthe ddname of AUTOTASK. Use the name of thismember in the AUTOTASK run-time option, whichmust be in the following format:

AUTOTASK(loadmod,numtasks)

loadmodName of the parallel subroutine load module;that is, the name of the member in the data setreferenced by the file definition with the ddnameAUTOTASK.

numtasksNumber of tasks to be created by MTF.



FOR2001C The PDS member member-name,the name of which was specifiedin the AUTOTASK run-time optionas the name of the MTF parallelsubroutine load module, wasnot a valid load module. VSFORTRAN Version 2 Error Number:AFB919I-2




Programmer responseEnsure that your multitasking facility (MTF) parallelsubroutine load module was link-edited as a memberof the partitioned data set referenced by the filedefinition (DD statement or ALLOCATE command) withthe ddname of AUTOTASK. Use the name of thismember in the AUTOTASK run-time option, whichmust be in the following format:





FOR2003C The MTF parallel subroutine loadmodule module-name, the nameof which was specified in theAUTOTASK run-time option, hadthe not-editable linkage editorattribute. VS FORTRAN Version 2Error Number: AFB919I-3




Programmer responseEnsure that your multitasking facility (MTF) parallelsubroutine load module was link-edited as a memberof the partitioned data set referenced by the filedefinition (DD statement or ALLOCATE command) withthe ddname of AUTOTASK. Also ensure that there wereno failures during the link-editing process.


FOR2004C The MTF parallel subroutine loadmodule module-name, the nameof which was specified in theAUTOTASK run-time option, didnot contain the entry pointVFEIS#. VS FORTRAN Version 2Error Number: AFB919I-4




Programmer responseEnsure that your multitasking facility (MTF) parallelsubroutine load module was link-edited as a memberof the partitioned data set referenced by the filedefinition (DD statement or ALLOCATE command)with the ddname of AUTOTASK. Also ensure thatthe module VFEIS# was included during the link-editprocess. As an example of how to link-edit yourparallel subroutine load module, assume that:

• You've compiled your parallel subroutine, and it's inthe temporary data set &&LOADSET.

• You want the load module to be given the membername SUB001, and you want it placed in the loadload with the data set name MY.SUB.LOAD.

Then, you would code the following job step to link-edit your parallel subroutine load module:

//LINKPS EXEC CEEWCL,PGMLIB='MY.SUB.LOAD',GOPGM=SUB001//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)// DD * INCLUDE SYSLIB(VFEIS#) ENTRY VFEIS#/*



FOR2005C The MTF parallel subroutineload module module-name, thename of which was specified inthe AUTOTASK run-time option,contained VFEIS#, but VFEIS#was not the entry point of the loadmodule. VS FORTRAN Version 2Error Number: AFB919I-5




Programmer responseEnsure that your multitasking facility (MTF) parallelsubroutine load module was link-edited as a memberof the partitioned data set referenced by the filedefinition (DD statement or ALLOCATE command) withthe ddname of AUTOTASK. Also ensure that the yourparallel subroutine is a subroutine subprogram, orpossibly more than one subroutine subprogram, andthat there is no main program.

As an example of how to link-edit your parallelsubroutine load module, assume that:

• You've compiled your parallel subroutine, and it's inthe temporary data set &&LOADSET.

• You want the load module to be given the membername SUB001, and you want it placed in the loadload with the data set name MY.SUB.LOAD.

Then you would code the following job step to link-edityour parallel subroutine load module:

//LINKPS EXEC CEEWCL,PGMLIB='MY.SUB.LOAD',GOPGM=SUB001//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)// DD * INCLUDE SYSLIB(VFEIS#) ENTRY VFEIS#/*


FOR2030C The AUTOTASK file definitionstatement was missing. VSFORTRAN Version 2 Error Number:AFB925I-1




Programmer responseEnsure that your multitasking facility (MTF) parallelsubroutine load module was link-edited as a memberof a partitioned data set. Do not use a partitioneddata set extended (PDSE). Provide a file definition (DDstatement or ALLOCATE command) with the ddnameof AUTOTASK; in this file definition, refer to the dataset into which you link-edited your parallel subroutineload module.


FOR2031C The AUTOTASK file definitionstatement did not specify a loadlibrary. VS FORTRAN Version 2Error Number: AFB925I-2




Programmer responseEnsure that your multitasking facility (MTF) parallelsubroutine load module was link-edited as a memberof a partitioned data set. Do not use a partitioneddata set extended (PDSE). In the file definition (DDstatement or ALLOCATE command) with the ddnameof AUTOTASK, refer to the data set into which youlink-edited your parallel subroutine load module.


FOR2032C The OPEN macro instructionexecuted for the load library thatwas specified by the AUTOTASKfile definition statement andthat should contain the MTFparallel subroutine load modulehad a system completion codeof completion-code and a reasoncode of reason-code. Seekassistance from your LanguageEnvironment support personnel.VS FORTRAN Version 2 ErrorNumber: AFB925I-1


ExplanationDuring the initialization of the Fortran multitaskingfacility (MTF), Language Environment executed anOPEN macro instruction that referred to the filedefinition (DD statement or ALLOCATE command) witha ddname of AUTOTASK. (This is the file definition thatis supposed to refer to the partitioned data set (PDS)into which was link-edited the parallel subroutine loadmodule with the name given in the AUTOTASK run-time option.) Either MVS or DFSMS/MVS detected theerror indicated by system completion (abend) codecompletion-code and reason code reason-code.




Programmer responseEnsure that the file definition with the ddnameAUTOTASK is coded correctly and that it refers to thePDS (not PDSE) into which was link-edited the parallelsubroutine load module with the name given in theAUTOTASK run-time option.

For the meaning of system completion codecompletion-code and reason code reason-code, and forpossible corrective actions, refer to z/OS MVS SystemCodes.


FOR2040S The MTF callable service service-name failed. The service wascalled from an MTF parallelsubroutine. VS FORTRAN Version2 Error Number: AFB920I-1,AFB157I-1

ExplanationThe multitasking facility (MTF) callable service service-name was called from a parallel subroutine. However,this service is restricted to use in the main taskprogram.


Qualifying Data:


Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 service-name

Input CHARACTER*6 Name of the MTFcallable service




Programmer responseRemove the call to service-name from the parallelsubroutine, and, if necessary, place the call in the maintask program instead.


FOR2041S The MTF callable service service-name failed. The service wascalled with an argument listin an incorrect format. VSFORTRAN Version 2 Error Number:AFB920I-2, AFB157I-3

ExplanationThe argument list provided in the call to the service-name callable service was incorrect in one of theseways:

• There was no argument list when one was required.• The argument list had an incorrect number of

arguments.• For either the DSPTCH or SHRCOM callable service,

the argument list wasn't in the internally-generatedform produced by the Fortran compiler when thereare character arguments. This could have occurredbecause:

– The first argument was not of character type.– The call was made from a program compiled by

the VS FORTRAN Version 1 or the VS FORTRANVersion 2 compiler with the the LANGLVL(66)compiler option.






Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 service-name





Programmer responseEnsure that the argument list contains the requirednumber of arguments and that the arguments are ofthe required type. For further information, refer to thechapter “Multitasking Facility (MTF) Subroutines” in VSFORTRAN Version 2 Language and Library Reference.

For either the DSPTCH or SHRCOM callable service,follow these rules: If the program is written inFortran, compile it with the VS FORTRAN Version2 compiler, and do not specify the LANGLVL(66)compiler option. If it is written in assembler language,use the Fortran conventions for argument lists withcharacter arguments. These conventions are describedin the section “Passing Character Arguments Using theStandard Linkage Convention” in Appendix B of VSFORTRAN Version 2 Programming Guide for CMS andMVS.


FOR2042S The MTF callable service service-name failed. The multitaskingfacility was not active. VSFORTRAN Version 2 Error Number:AFB920I-3


Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 2

2 service-name



Programmer responseIf you intend to use the Fortran multitasking facility(MTF), then do the following to make MTF active forthe application:

1. Link-edit your parallel subroutine load module as amember of a partitioned data set.

2. Provide a file definition (DD statement or ALLOCATEcommand) with the ddname of AUTOTASK. Referthis file definition to the data set into which youlink-edited your parallel subroutine load module.

3. Provide the AUTOTASK run-time option in thefollowing format:


loadmodNname of the parallel subroutine load module;that is, the name of the member in the dataset referenced by the file definition with theddname AUTOTASK.


If you didn't intend to use MTF, then make one of thesechanges:

• If the call to service-name was meant to referto one of your own routines rather than to theMTF callable service, then during the link-editingof your application, ensure that your own routineis included in the load module. Do this either byusing the linkage editor INCLUDE statement or byconcatenating the library containing your routineahead of the Language Environment product libraryin the SYSLIB DD statement.

• If the call to service-name was coded to use the MTFcallable service, then remove the call because youcan't use this callable service unless MTF is activefor the application (as discussed earlier).


FOR2044S The MTF callable service SHRCOMfailed. The dynamic common block


common-name was not declared inany program unit that was invokedin the main task program. VSFORTRAN Version 2 Error Number:AFB099I


Qualifying Data:

No.

Name Input/Output

Data Type andLength

Value

1 parm-count

Input INTEGER*4 3

2 service-name

Input CHARACTER*6 SHRCOM

3 common-name

Input CHARACTER*31 Name of dynamiccommon block





Programmer responseEnsure that common block name, common-name,given as the argument for the SHRCOM callable serviceis the name that you intended. If you code the nameas a character constant, enclose the name in quotes orapostrophes.

Also ensure that at least one program unit that wasentered before the SHRCOM callable service wasinvoked has a declaration of the common block as adynamic common block. (Declaring it in the programunit that invokes the SHRCOM callable service meetsthis requirement.) Specify the common block as adynamic common block by supplying its name as asuboption of the DC compile-time option.


FOR2056S MTF subtask subtask-numberabnormally terminated duringexecution of parallel subroutinesubroutine-name. The systemcompletion code was system-completion-code, and the reasoncode was reason-code. VSFORTRAN Version 2 Error Number:AFB922I-2

ExplanationAt the time that a call was made to one of multitaskingfacility (MTF) callable services SYNCRO, DSPTCH, orSHRCOM, Language Environment detected that theparallel subroutine subroutine-name in MTF subtasksubtask-number had ended unexpectedly because ofthe abnormal termination indicated by the systemcompletion code completion-code and reason codereason-code. The message describing this abnormaltermination is in the message file for the subtask.This message file is the one referenced by the filedefinition (DD statement or ALLOCATE command) withthe ddname FTERRsss, where sss is the three-digitrepresentation of subtask-number.

System actionThe condition FOR2056 is signaled in the main taskprogram. If the condition is unhandled, the applicationis terminated.



Programmer responseFor the meaning of system completion codecompletion-code and reason code reason-code, and forpossible corrective actions, refer to z/OS MVS SystemCodes.


FOR2057S MTF subtask subtask-numberabnormally terminated duringexecution of parallel subroutinesubroutine-name. The usercompletion code was user-completion-code, and the reasoncode was reason-code. VSFORTRAN Version 2 Error Number:AFB922I-2

ExplanationAt the time that a call was made to one of multitaskingfacility (MTF) callable services SYNCRO, DSPTCH, orSHRCOM, Language Environment detected that theparallel subroutine subroutine-name in MTF subtasksubtask-number had ended unexpectedly becauseof the abnormal termination indicated by the usercompletion code completion-code and reason codereason-code. If the parallel subroutine wrote anyoutput on the message file before terminating, thatoutput is in the message file for the subtask. This


message file is the one referenced by the filedefinition (DD statement or ALLOCATE command) withthe ddname FTERRsss, where sss is the three-digitrepresentation of subtask-number.

The abnormal termination was requested by executingan assembler language ABEND macro instruction orby calling one of the CEE3ABD, SYSABN, or SYSABDcallable services, among others. The exact meaning ofthe user completion code completion-code and reasoncode reason-code depends on the application thatrequested the abnormal termination. Some form ofinformation about the meaning of these codes shouldbe available to users of that application.




Programmer responseCorrect the problem indicated by the user completioncode completion-code and reason code reason-code.


FOR2058S MTF subtask subtask-numberterminated during executionof MTF parallel subroutinesubroutine-name because of anunhandled condition of severityseverity. VS FORTRAN Version 2Error Number: AFB922I-2

ExplanationAt the time that a call was made to one of multitaskingfacility (MTF) callable services SYNCRO, DSPTCH, orSHRCOM, Language Environment detected that theparallel subroutine subroutine-name in MTF subtasksubtask-number had ended unexpectedly becauseof an unhandled condition of severity severity. Themessage describing this condition is in the messagefile for the subtask. This message file is the onereferenced by the file definition (DD statement orALLOCATE command) with the ddname FTERRsss,where sss is the three-digit representation of subtask-number.




Programmer responseCorrect the problem indicated by the unhandledcondition.


FOR2059S A CSECT with the name CEEUOPTwas present in the MTF parallelsubroutine load module.




Programmer responseLink-edit the parallel subroutine load module withoutthe CSECT with the name CEEUOPT.

If you want to provide run-time options that are link-edited with the application, then link-edit the CSECTwith the name CEEUOPT into the main task loadmodule. The run-time options that you specify in thismanner or in any other manner will apply in the maintask program and in all parallel subroutines.


FOR2060S The MTF callable service DSPTCHcould not be completed. The firstargument to the DSPTCH callableservice specified that subroutine-name was to be invoked asa parallel subroutine, but theparallel subroutine load moduledid not contain a subroutine withthe specified name. VS FORTRANVersion 2 Error Number: AFB921I



Qualifying Data:


Data Type andLength

Value

1 parm-count

Input INTEGER*4 3

2 service-name

Input CHARACTER*6 DSPTCH

3 subroutine- name

Input CHARACTER*8 Name ofMTF parallelsubroutine


Programmer responseEnsure that the parallel subroutine name, subroutine-name, given as the first argument for the DSPTCHcallable service is the name that you intended. If youcode the name as a character constant, enclose thename in quotes or apostrophes. Do not provide a namethat exceeds eight characters in length.

Ensure that the parallel subroutine subroutine-nameis link-edited into your multitasking facility (MTF)parallel subroutine load module. Also ensure thatthis load module is link-edited as a member of thepartitioned data set referenced by the file definition(DD statement or ALLOCATE command) with theddname of AUTOTASK. Use the name of this memberin the AUTOTASK run-time option, which must be inthe following format:





FOR2062C During MTF initialization, themacro-name macro instruction hada return code of return-code. Seekassistance from your LanguageEnvironment support personnel.VS FORTRAN Version 2 ErrorNumber: AFB924I

ExplanationDuring the initialization of the Fortran multitaskingfacility (MTF), Language Environment executed amacro-name macro instruction. Either MVS orDFSMS/MVS detected the error indicated by returncode return-code.




Programmer responseFor the meaning of return code return-code, andfor possible corrective actions, refer to one of thefollowing:

• z/OS MVS System Codes• z/OS DFSMS Macro Instructions for Data Sets



FOR2063C During MTF initialization, themacro-name macro instruction hada return code of return-code and areason code of reason-code. Seekassistance from your LanguageEnvironment support personnel.VS FORTRAN Version 2 ErrorNumber: AFB925I

ExplanationDuring the initialization of the Fortran multitaskingfacility (MTF), Language Environment executed amacro-name macro instruction. Either MVS orDFSMS/MVS detected the error indicated by returncode return-code and reason code reason-code.





Programmer responseFor the meaning of return code return-code and reasoncode reason-code, and for possible corrective actions,refer to one of the following:

• z/OS MVS System Codes• z/OS DFSMS Macro Instructions for Data Sets



FOR2064S The MTF callable service DSPTCHcould not be completed. The MTFmain task program was operatingin 31-bit addressing mode, but theparallel subroutine load modulehad the linkage editor attributethat indicated 24-bit addressingmode. VS FORTRAN Version 2Error Number: AFB927I


Qualifying Data:


Data Type andLength

Value

1 parm-count

Input INTEGER*4 3

2 service-name

Input CHARACTER*6 DSPTCH

3 subroutine- name

Input CHARACTER*8 Name of MTFparallel subroutine


Programmer responseDetermine whether any routine in the parallelsubroutine load module must execute in 24-bitaddressing mode or why the linkage editor gave it theattribute indicating that it must. For example, codecompiled by the FORTRAN IV H Extended compilermust run in 24-bit addressing mode; therefore, if theparallel subroutine load module contains such code,then this attribute is correct.

If a routine in the parallel subroutine load modulemust execute in 24-bit addressing mode, then ensurethat the main task program is running in 24-bit

addressing mode at the time that it calls the DSPTCHcallable service. Do this in one of these ways:

• When you link-edit the main task program, providethe AMODE=24 and RMODE=24 linkage editor options.This causes the main task program to be invoked in24-bit addressing mode and to reside below 16 Mb.

• If a portion of the main task program must runin 31-bit addressing mode, then use an assemblerlanguage routine to switch into 24-bit addressingmode at some point before calling the DSPTCHcallable service. (Also switch back into 31-bitaddressing mode as necessary.) Remember that inorder to switch successfully into 24-bit addressingmode, the load module must reside below 16 Mb. Toensure that the load module is loaded below 16 Mb,provide the RMODE=24 linkage editor option.

If you are sure that no routine in the parallelsubroutine load module must be invoked in 24-bitaddressing mode, then when you link-edit this loadmodule, provide the AMODE=31 linkage editor option.

In addition, if the parallel subroutine load module canreside above 16 Mb, then also provide the RMODE=ANYlinkage editor option.


FOR2065C The MTF main task programload module was created withLanguage Environment, but theMTF parallel subroutine loadmodule was created with VSFORTRAN. VS FORTRAN Version 2Error Number: AFB928I




Programmer responseLink-edit parallel subroutine load module usingLanguage Environment. This is required because yourmain task program was link-edited using LanguageEnvironment.

If, when you link-edit your parallel subroutine loadmodule, you want to use your executable load module(rather than the original object modules) as inputto the linkage editor, then remember to replace theVS FORTRAN library modules that are in that load


module. For information on how to do this, refer toz/OS Language Environment Programming Reference.


FOR2067S The MTF main task programterminated while subtask subtask-number was still executing parallelsubroutine subroutine-name. VSFORTRAN Version 2 Error Number:AFB930I




Programmer responseEnsure that before the main task program ends itinvokes the SYNCRO callable service to wait for thecompletion of the parallel subroutines.


FOR2068C MTF internal error error-numberwas detected. Seek assistancefrom your Language Environmentsupport personnel. VS FORTRANVersion 2 Error Number: AFB931I




Programmer responseBecause this error is not likely to be caused byyour application, seek assistance from your LanguageEnvironment support personnel.


FOR2069C MTF subtask subtask-numberfailed during initialization. VS

FORTRAN Version 2 Error Number:AFB922I-1

ExplanationDuring the initialization of the Fortran multitaskingfacility (MTF) by Language Environment, subtasksubtask-number couldn't be started successfully. Themessage describing this situation is in the messagefile for the subtask. This message file is the onereferenced by the file definition (DD statement orALLOCATE command) with the ddname FTERRsss,where sss is the three-digit representation of subtask-number.




Programmer responseCorrect the problem indicated in the message file forsubtask subtask-number.


FOR2070I MTF subtask subtask-numberabnormally terminated duringexecution of parallel subroutinesubroutine-name. The systemcompletion code was system-completion-code, and the reasoncode was reason-code. VSFORTRAN Version 2 Error Number:AFB922I-2

ExplanationThe parallel subroutine subroutine-name in MTFsubtask subtask-number ended unexpectedly becauseof the abnormal termination indicated by the systemcompletion code completion-code and reason codereason-code. The message describing this abnormaltermination is in the message file for the subtask.This message file is the one referenced by the filedefinition (DD statement or ALLOCATE command) withthe ddname FTERRsss, where sss is the three-digitrepresentation of subtask-number.


System actionThe condition FOR2070 is signaled in the main taskprogram during termination of the application.



Programmer responseFor the meaning of system completion codecompletion-code and reason code reason-code, and forpossible corrective actions, refer to z/OS MVS SystemCodes.


FOR2071I MTF subtask subtask-numberended during execution of MTFparallel subroutine subroutine-name because a statementthat requested an immediatetermination was executed. Thesubtask return code was return-code. VS FORTRAN Version 2 ErrorNumber: AFB922I-3

ExplanationThe parallel subroutine subroutine-name in MTFsubtask subtask-number ended because of a requestto explicitly terminate the application with return codereturn-code. Examples of such requests include theexecution either of a STOP statement or of a call to theEXIT or SYSRCX callable service.




Programmer responseCorrect the problem indicated either by return codereturn-code or by any other messages the parallelsubroutine wrote.


FOR2072I MTF subtask subtask-numberterminated during executionof MTF parallel subroutine

subroutine-name because of anunhandled condition of severityseverity. VS FORTRAN Version 2Error Number: AFB922I-2

ExplanationThe parallel subroutine subroutine-name in MTFsubtask subtask-number ended unexpectedly becauseof an unhandled condition of severity severity. Themessage describing this condition is in the messagefile for the subtask. This message file is the onereferenced by the file definition (DD statement orALLOCATE command) with the ddname FTERRsss,where sss is the three-digit representation of subtask-number.




Programmer responseCorrect the problem indicated by the unhandledcondition.


FOR2073I MTF subtask subtask-numberabnormally terminated duringexecution of parallel subroutinesubroutine-name. The usercompletion code was user-completion-code, and the reasoncode was reason-code. VSFORTRAN Version 2 Error Number:AFB922I-2

ExplanationThe parallel subroutine subroutine-name in MTFsubtask subtask-number ended unexpectedly becauseof the abnormal termination indicated by the usercompletion code completion-code and reason codereason-code. If the parallel subroutine wrote anyoutput on the message file before terminating, thatoutput is in the message file for the subtask. Thismessage file is the one referenced by the filedefinition (DD statement or ALLOCATE command) withthe ddname FTERRsss, where sss is the three-digitrepresentation of subtask-number.


The abnormal termination was requested by executingan assembler language ABEND macro instruction orby calling one of the CEE3ABD, SYSABN, or SYSABDcallable services, among others. The exact meaning ofthe user completion code completion-code and reasoncode reason-code depends on the application thatrequested the abnormal termination. Some form ofinformation about the meaning of these codes shouldbe available to users of that application.




Programmer responseCorrect the problem indicated by the user completioncode completion-code and reason code reason-code.


FOR2101S Based on the value given for theSIZE suboption of the VECTORcompile-time option, the programunit was compiled so that it couldrun only on a machine with asection size of comp-section-size.However, execution was on amachine with a section size ofmach-section-size. VS FORTRANVersion 2 Error Number: AFB934I

ExplanationWhen the program unit was compiled, the VECTORcompile-time option had one of these forms:VECTOR( … SIZE(LOCAL) … )

In this case, the machine on which the programunit was compiled had a section size of comp-section-size, and the compiler produced code thatcould be run only on a machine with this samesection size.

VECTOR( … SIZE(comp-section-size) …)In this case, the compiler was directed to producecode that could be run only on a machine with asection size of comp-section-size.

In either case, because the compiled code wascapable of running only on a machine with a sectionsize of comp-section-size, it couldn't be run on themachine that had a section size of mach-section-size.




Programmer responseIf you want the compiled code to be able on runon machines with various section sizes, then compilethe program with the following VECTOR compile-timeoption, which has the IBM-supplied default for theSIZE suboption:

VECTOR( … SIZE(ANY) … )

When the SIZE(ANY) suboption is used, the codesequences are not as efficient as they would be if thecode were targeted only for machines with a specificsection size.

If you can ensure that the compiled code will be runonly on a machine with the a section size of mach-section-size, and if you want the code to be optimizedfor machines with that section size, then compilethe program with the following VECTOR compile-timeoption:

VECTOR (… SIZE(mach-section-size) …)

If you can ensure that the compiled code will be runonly on a machine with the same section size as thaton which it is compiled, and if you want the codeto be optimized for machines with that section size,then compile the program with the following VECTORcompile-time option:

VECTOR( … SIZE(LOCAL) … )


FOR2102S An internal table used to controlthe allocation of vector spill areaswas corrupted and couldn't beused. VS FORTRAN Version 2 ErrorNumber: AFB935I

ExplanationAt entry to a program unit that was compiled with theVECTOR compile-time option, a Language Environmentroutine detected an inconsistency in a table thatwas supposed to control allocation of storage forvector spill areas, which are areas used to store thecontents of vector registers. Most likely the table invirtual storage was overlaid by some routine (but not


necessarily by the routine containing the table thatwas destroyed).




Programmer responseDetermine and correct the cause of the overlaid table.In Fortran program units, this is often caused by:

• Using subscripts that reference virtual storageoutside the declared bounds of an array

• Referring to variables that are in EQUIVALENCEstatements when the variables are declared tooverlay too much storage

• Referring to storage that's addressed through apointer whose value isn't properly established

• In a CALL statement or function reference, providingactual arguments that are not consistent with thedummy arguments declared in the subprogram. Theactual arguments could be of the wrong type, rank,or have the wrong array bounds. There could be anincorrect number of actual arguments


FOR2121C A suboption of the AUTOTASKrun-time option was missing. VSFORTRAN Version 2 Error Number:AFB917I-1




Programmer responseIf you want to use the Fortran multitasking facility(MTF), provide the AUTOTASK run-time option in thefollowing format:


loadmodName of the parallel subroutine load module;that is, the name of the member in the data set

referenced by the file definition with the ddnameAUTOTASK.


If you did not intend to use MTF, then eitherremove the AUTOTASK run-time option or specify theNOAUTOTASK run-time option.


FOR2130C A construct of the parallelfeature of VS FORTRAN Version 2could not be completed. Parallelprograms cannot be executedusing Language Environment.

ExplanationThe program was compiled with VS FORTRAN Version2 Release 5 or 6 and was considered to be a parallelprogram for one or more of these reasons:

• The program contained parallel language constructs.• The program invoked one of the parallel callable

services (PEORIG, PEPOST, PEWAIT, PETERM,PLCOND, PLFREE, PLLOCK, PLORIG, or PLTERM).

• The program was compiled with the PARALLELcompile-time option.

You cannot run a parallel program if it has been link-edited with Language Environment.




Programmer responseIf you want to link-edit and run the program withLanguage Environment, then compile it without thePARALLEL compile-time option, and remove theparallel language constructs and any calls to theparallel callable services.

If you want to continue to run the program as a parallelprogram, then link-edit it with the VS FORTRANVersion 2 Release 6 library. In this case, don't codeanything in the program (including in any relatedsubprograms) that makes use of any of the LanguageEnvironment features that aren't in VS FORTRANVersion 2 Release 6. You can then run the program


either with the VS FORTRAN Version 2 Release 6library or with Language Environment.


FOR2131S The program program-name wascompiled by VS FORTRAN Version2 compiler with the EC option,which is not supported byLanguage Environment.

ExplanationThe program was compiled with VS FORTRAN Version2 Release 5 or 6 with the EC compile-time option.This option specified that certain common blocks werebe treated as extended common blocks and that theirvirtual storage was to be allocated in data spaces. Youcannot run such a program if it has been link-editedwith Language Environment.




Programmer responseIf you want to link-edit and run the program withLanguage Environment, then compile it without theEC compile-time option. Specify the common blocksas dynamic common blocks by giving their names assuboptions of the DC compile-time option. However,unless you can reduce the size of the extendedcommon blocks, this approach won't work if theprogram and the common blocks won't fit in theprimary address space.

If you want to continue to run the program withextended common blocks, then link-edit it with theVS FORTRAN Version 2 Release 6 library. In thiscase, don't code anything in the program (includingin any related subprograms) that makes use of anyof the Language Environment features that aren't inVS FORTRAN Version 2 Release 6. You can then runthe program either with the VS FORTRAN Version 2Release 6 library or with Language Environment.


FOR2132S An invalid argument was providedto an INTEGER*8 simulation

routine. VS FORTRAN Version 2Error Number: AFB177I

ExplanationAn INTEGER*8 simulation routine was implicitlyreferenced by the compiled code because of the use ofan integer variable of length 8. One of the argumentsto this routine had an unexpected value. Most likelythe argument or argument list in virtual storage wasoverlaid by some routine (but not necessarily by theroutine containing the argument that was destroyed).




Programmer responseDetermine and correct the cause of the overlaidargument. In Fortran program units, this is oftencaused by:



• Referring to storage that's addressed through apointer whose value is not properly established




FOR2133S A program interruption occurredduring the simulation of anINTEGER*8 instruction. VSFORTRAN Version 2 Error Number:AFB178I


ExplanationAn INTEGER*8 simulation routine in the Fortranlibrary portion of Language Environment was implicitlyreferenced by the compiled code because of the use ofan integer variable of length 8. During the executionof this simulation routine, a program interruptionoccurred.




Programmer responseExamine the operands involved in any use of integervariables of length 8, and correct any errors that youfind. Here are some errors that might have caused theprogram interruption:



• Referring to storage that's addressed through apointer whose value isn't properly established





Chapter 6. PL/I runtime messages

The messages in this topic pertain to PL/I. Each message is followed by an explanation describingthe condition that caused the message, a programmer response suggesting how you might prevent themessage from occurring again, and a system action indicating how the system responds to the conditionthat caused the message.


The messages in this topic contain alphabetic suffixes that have the following meaning:I


Warning messageE

Error messageS



IBM0004S The program terminated with usercode= user-code

ExplanationThe program terminated with a user code.

System actionThe ERROR condition is raised.

Programmer responseCheck your program documentation or the programsource to determine the reason the code was issued.

Symbolic Feedback CodeIBM004

IBM0005S The number of files, CONTROLLEDvariables, or fetched proceduresexceeded the limit.

ExplanationThe total length of the pseudoregister vector for theprogram was more than 4096 bytes. Four bytes areused for each file constant, controlled variable, andfetched procedure.


Programmer responseModify the program so the pseudoregister vector doesnot exceed 4096 bytes by reducing the number of filesor controlled variables used or by restructuring theprogram into several external procedures.


IBM0006S The program could not beexecuted because it did not havea main procedure.

ExplanationThere are two possible causes for this error:

• An attempt was made to run a program whichcontained one or more external PL/I procedures.None of the procedures had the MAIN or FETCHABLEoption in the PROCEDURE statement.

• An attempt was made to FETCH a load modulewith entry PLISTART or CEESTART which containedone or more external PL/I procedures. None of the


procedures had the MAIN or FETCHABLE option inthe PROCEDURE statement.


Programmer responseEnsure that the first external PL/I procedure to beinvoked has the MAIN or FETCHABLE option in thePROCEDURE statement. When fetching a load module,follow the instructions on "Link-Editing Fetchable LoadModules" in z/OS Language Environment ProgrammingGuide.


IBM0010W An invalid length or address wasfound in the PLICALLB argumentlist for ISA, HEAP, or TASKHEAPstorage. The length or address wasignored.

ExplanationIf the length or address of ISA, HEAP, or TASKHEAPstorage is provided, it must be valid and for the lengthit must be a multiple of 8 bytes and for the address itmust be on a double-word boundary.


Programmer responseCheck the provided length and/or address to makesure it is valid and follows the rules.

Symbolic Feedback CodeIBM00A

IBM0011W The ISA or HEAP storage providedin the PLICALLB argument list wasabove the 16M line but the BELOWsuboption of the STACK or HEAPrun-time option was in effect. Theprovided storage was ignored.

ExplanationThe location of the user-provided ISA or HEAP storageconflicts with the location in effect in the STACK orHEAP run-time option. The provided storage is ignoredbut the provided length is still used.


Programmer responseMake sure the location of the provided ISA or HEAPstorage agrees with the location in the STACK or HEAPrun-time option.

Symbolic Feedback CodeIBM00B

IBM0020S ONCODE=600. The CONVERSIONcondition was raised by a SIGNALstatement.

ExplanationThe program contained a SIGNAL statement to raisethe CONVERSION condition for which there was noassociated ON-unit.


Programmer responseEither remove the SIGNAL statement or includean ON-unit for the CONVERSION condition in theprogram.

Symbolic Feedback CodeIBM00K

IBM0021S ONCODE=601. The CONVERSIONcondition was raised because ofunknown source attributes oninput.

ExplanationThe CONVERSION condition was raised within a GETLIST or GET DATA statement with the FILE option. Theattributes of the source data could not be determined.

Consider the following example, where the inputstream contained 'PIG'C, 'DOG'.

DCL (A,B) CHAR(14);GET LIST(A,B);

The condition will be raised when the first item isencountered. The value for ONSOURCE would be:"'PIG'C", and value of ONCHAR would be: "C". TheONCODE associated with this message is 601.



Programmer responseInclude a suitable ON-unit in the program to monitorerrors in the input data revealed by the CONVERSIONcondition. Use the ONSOURCE and ONCHAR built-infunctions to identify the error and the ONSOURCEand ONCHAR pseudovariables to assign a valid valueso the program can continue processing. Also, checkthe input data for correctness before rerunning theprogram.

Symbolic Feedback CodeIBM00L

IBM0022S ONCODE=602. The CONVERSIONcondition was raised becauseof unknown source attributeson input after the TRANSMITcondition was detected.

ExplanationThe CONVERSION condition was raised after an errorcaused the TRANSMIT condition to be raised. Foran example of the conversion error, refer to theexplanation given for message IBM0021. The ONCODEassociated with this message is 602.


Programmer responseCorrect the transmit error. If the conversion errorrecurs after correcting the transmit error, refer to thesteps for conversion errors in message IBM0021.

Symbolic Feedback CodeIBM00M

IBM0023S ONCODE=oncode-value TheCONVERSION condition wasraised because of unknown sourceattributes.

ExplanationThe CONVERSION condition was raised within a GETLIST STRING or GET DATA STRING statement. Foran example of the conversion error, refer to theexplanation for message IBM0021.


Programmer responseFollow the steps given for conversion errors inmessage IBM0021.

Symbolic Feedback CodeIBM00N

IBM0024S ONCODE=oncode-value TheCONVERSION condition wasraised because a conversion erroroccurred using F-format on input.

ExplanationAn invalid character was detected in an F-format inputfield. The ONCODEs associated with this message are:

• 603 - GET STRING statement• 604 - GET FILE statement


Programmer responseInclude a suitable ON-unit in the program to monitorerrors in the input data that are revealed by theCONVERSION condition. Use the ONSOURCE andONCHAR built-in functions to identify the error and theONSOURCE and ONCHAR pseudovariables to assigna valid numeric value so the program can continueprocessing. Also, ensure all input is in the correctformat before running the program.

Symbolic Feedback CodeIBM00O

IBM0025S ONCODE=605. The CONVERSIONcondition was raised becausea conversion error occurredusing F-format on input afterthe TRANSMIT condition wasdetected.

ExplanationAn invalid character was detected in an F-format inputfield. A transmission error also occurred and maybe the cause of the conversion error. The ONCODEassociated with this message is 605.

Chapter 6. PL/I runtime messages 401


Programmer responseCorrect the transmit error. If the conversion errorrecurs after correcting the transmit error, refer to thesteps given for message IBM0024.

Symbolic Feedback CodeIBM00P

IBM0027S ONCODE=oncode-value TheCONVERSION condition wasraised because a conversion erroroccurred using E-format on input.

ExplanationAn invalid character was detected in an E-format inputfield. The ONCODEs associated with this message are:



Programmer responseRefer to the steps for conversion errors in messageIBM0024. Use the ONSOURCE and ONCHAR built-infunctions to identify the error, and the ONSOURCE andONCHAR pseudovariables to assign a valid value sothe program can continue processing.

Symbolic Feedback CodeIBM00R

IBM0028S ONCODE=608. The CONVERSIONcondition was raised becausea conversion error occurredusing E-format on input afterthe TRANSMIT condition wasdetected.

ExplanationAn invalid character was detected in an E-format inputfield. A transmission error also occurred and maybe the cause of the conversion error. The ONCODEassociated with this message is 608.


Programmer responseCorrect the transmission error. If the conversion errorrecurs after correcting the transmission error, refer tothe steps for message IBM0024.

Symbolic Feedback CodeIBM00S

IBM0029S ONCODE=oncode-value TheCONVERSION condition wasraised because a conversion erroroccurred using B-format on input.

ExplanationAn invalid character was detected in a B-format inputfield. The ONCODEs associated with this message are:



Programmer responseInclude a suitable ON-unit in the program to monitorerrors in the input data that are revealed by theCONVERSION condition. Use the ONSOURCE andONCHAR built-in functions to identify the error and theONSOURCE and ONCHAR pseudovariables to assigna valid bit character so the program can continueprocessing. Also, ensure all input is in the correctformat before running the program.

Symbolic Feedback CodeIBM00T

IBM0031S ONCODE=611. The CONVERSIONcondition was raised becausea conversion error occurredusing B-format on input afterthe TRANSMIT condition wasdetected.

ExplanationAn invalid character was detected in a B-format inputfield. A transmission error also occurred and maybe the cause of the conversion error. The ONCODEassociated with this message is 611.




Symbolic Feedback CodeIBM00V

IBM0032S ONCODE=612. The CONVERSIONcondition was raised because aconversion error occurred whenconverting a character string to anarithmetic value.

ExplanationAn invalid character was detected in a character stringthat was being converted to an arithmetic data type.The ONCODE associated with this message is 612.


Programmer responseIf the error is in the conversion of a PL/I sourceprogram constant or in the conversion of a characterstring created while the program is running, correctthe source program. Recompile and rerun theprogram. Use the ONSOURCE and ONCHAR built-infunctions to identify the error, and the ONSOURCE andONCHAR pseudovariables to assign a valid value sothe program can continue processing.


IBM0033S ONCODE=613. The CONVERSIONcondition was raised because aconversion error occurred whenconverting character to arithmeticon input or output.

ExplanationA character which is invalid for conversion to anarithmetic form was detected in one of the following:

• An arithmetic constant in a list-directed or data-directed item.

• A character constant being converted to anarithmetic form in a list-directed or data-directeditem.

• An A-format input field being converted to anarithmetic form.

The ONCODE associated with this message is 613.


Programmer responseRefer to the steps for message IBM0024.


IBM0034S ONCODE=614. The CONVERSIONcondition was raised because aconversion error occurred whenconverting from character on inputafter the TRANSMIT condition wasdetected.

ExplanationA character is invalid for conversion to an arithmeticform was detected in one of the following:

• An arithmetic constant in a list-directed or data-directed input item.

• A character constant being converted to anarithmetic form in a list-directed or data directedinput item.

• An A-format input field being converted to anarithmetic form.

A transmission error also occurred and may be thecause of the conversion error. The ONCODE associatedwith this message is 614.





IBM0035S ONCODE=615. The CONVERSIONcondition was raised because aconversion error occurred whenconverting from character to bit.

ExplanationAn invalid character was detected in a character stringthat was being converted to a bit string. The ONCODEassociated with this message is 615.


Programmer responseIf the error is in the conversion of a program constantor in the conversion of a character string created whilethe program is running, correct the source program.Recompile and rerun the program. Use the ONSOURCEand ONCHAR built-in functions to identify the error,and the ONSOURCE and ONCHAR pseudovariablesto assign a valid value so the program can continueprocessing.


IBM0036S ONCODE=616. The CONVERSIONcondition was raised because aconversion error occurred whenconverting character to bit oninput or output.

ExplanationA character other than 0 or 1 appeared in one of thefollowing:

• A bit constant in a list-directed or data-directed item• A character constant being converted to bit form in a

list-directed or data-directed item• An A-format input field being converted to bit form• A B-format input field (excluding any leading or

trailing blanks)





IBM0037S ONCODE=617. The CONVERSIONcondition was raised becausea conversion error occurredwhen converting character to biton input after the TRANSMITcondition was detected.

ExplanationA character other than 0 or 1 appeared in one of thefollowing:

• A bit constant in a list-directed or data-directedinput item

• A character constant being converted to bit form in alist-directed or data-directed input item

• An A-format input field being converted to bit form• A B-format input field (excluding any leading or

trailing blanks)

A transmission error also occurred and may havecaused the conversion error. The ONCODE associatedwith this message is 617.




IBM0038S ONCODE=618. The CONVERSIONcondition was raised because aconversion error occurred whenconverting to a PICTURE characterstring.

ExplanationA character that did not match the picturespecification was detected in a conversion to aPICTURE character string. The ONCODE associatedwith this message is 618.



Programmer responseEnsure the character string to be converted to aPICTURE character string matches the picture stringspecification. If necessary, use the ONSOURCE andONCHAR built-in functions to identify the error andthe ONSOURCE and ONCHAR pseudovariables toreplace an erroneous character with a valid conversioncharacter.


IBM0039S ONCODE=619. The CONVERSIONcondition was raised because aconversion error occurred whenconverting to a PICTURE characterstring on input or output.

ExplanationA character that did not match the picturespecification was detected in a STREAM-oriented itemthat required conversion to a PICTURE characterstring. The ONCODE associated with this message is619.


Programmer responseEither ensure all input data to the program is inthe correct format or refer to the steps for messageIBM0038. These steps ensure the program hasadequate error recovery facilities to process anyinvalid data found in its input and continue processing.


IBM0040S ONCODE=620. The CONVERSIONcondition was raised becausea conversion error occurredwhen converting to a PICTUREcharacter string on input afterthe TRANSMIT condition wasdetected.

ExplanationA character that did not match the picturespecification was detected in a STREAM-oriented inputitem that required conversion to a PICTURE characterstring. A transmission error also occurred and may

be the source of the conversion error. The ONCODEassociated with this message is 620.




IBM0042S ONCODE=oncode-value TheCONVERSION condition wasraised because a conversion erroroccurred when converting fromPICTURE format on input.

ExplanationAn edit-directed PICTURE format input item containeda character that did not match the picturespecification. The ONCODEs associated with thismessage are:



Programmer responseEither ensure all input data to the program is in thecorrect format before running the program or usethe program to check the data. If necessary, usethe ONSOURCE and ONCHAR built-in functions toidentify the error and the ONSOURCE and ONCHARpseudovariables to replace an erroneous characterwith a character valid for conversion.


IBM0043S ONCODE=623. The CONVERSIONcondition was raised because aconversion error occurred whenconverting from a PICTURE formaton input after the TRANSMITcondition was detected.


ExplanationAn invalid character was detected in a PICTURE formatinput field. A transmission error also occurred andmay be the cause of conversion error. The ONCODEassociated with this message is 623.


Programmer responseCorrect the transmission error.

Programmer responseIf the conversion error recurs after correcting thetransmission error, refer to the steps for messageIBM0042.


IBM0045S ONCODE=625. The CONVERSIONcondition was raised because aconversion error occurred whenconverting from PICTURE formaton input.

ExplanationAn invalid character was detected in a PICTURE formatinput item. The ONCODE associated with this messageis 625.


Programmer responseEither ensure all input data to the program is in thecorrect format before running the program or usethe program to check the data. If necessary, usethe ONSOURCE and ONCHAR built-in functions toidentify the error and the ONSOURCE and ONCHARpseudovariables to replace an erroneous characterwith a valid conversion character.

Symbolic Feedback CodeIBM01D

IBM0046S ONCODE=626. The CONVERSIONcondition was raised because aconversion error occurred whenconverting from PICTURE format

on input after the TRANSMITcondition was detected.

ExplanationAn invalid character was detected in a PICTURE formatinput item. A transmission error also occurred and maybe the cause of the conversion error. The ONCODEassociated with this message is 626.



Symbolic Feedback CodeIBM01E

IBM0047S ONCODE=627. The CONVERSIONcondition was raised because agraphic or mixed character stringwas encountered in a non-graphicenvironment.

ExplanationA graphic ('G') or mixed ('M') string was used as a datavalue in the expression for the STRING option of a GETstatement. The ONCODE associated with this messageis 627.


Programmer responseRemove the graphic or mixed string from theexpression.

Symbolic Feedback CodeIBM01F

IBM0048S ONCODE=628. The CONVERSIONcondition was raised because agraphic or mixed character stringwas encountered in a non-graphicenvironment on input.


ExplanationA graphic ('G') or mixed ('M') string was detected inan input file that was not declared with the GRAPHICoption in the ENVIRONMENT attribute. The ONCODEassociated with this message is 628.


Programmer responseSpecify the GRAPHIC option for a file that containsgraphic or mixed character strings.

Symbolic Feedback CodeIBM01G

IBM0049S ONCODE=629. The CONVERSIONcondition was raised becausea graphic or mixed characterstring was encountered in a non-graphic environment on inputafter the TRANSMIT condition wasdetected.

ExplanationThe CONVERSION condition was raised after an errorcaused the TRANSMIT condition to be raised. Foran example of the conversion error, refer to theexplanation for message IBM0048. The ONCODEassociated with this message is 629.



Symbolic Feedback CodeIBM01H

IBM0053S ONCODE=633 The CONVERSIONcondition was raised because aninvalid character was detected inan X, BX, or GX string constant.

ExplanationA character other than a hexadecimal character wasdetected. Only hexadecimal characters (0-9,a-f,A-F)

are allowed in X, BX, and GX string constants. TheONCODE associated with this message is 633.


Programmer responseInclude a suitable ON-unit in the program to monitorerrors in the input data that are revealed by theCONVERSION condition. Use the ONSOURCE andONCHAR built-in functions to identify the error and theONSOURCE and ONCHAR pseudovariables to assigna valid hexadecimal character so the program cancontinue processing. Also ensure all input is in thecorrect format before executing the program.


IBM0054S ONCODE=634 The CONVERSIONcondition was raised because aninvalid character was detected inan X, BX, or GX string constant oninput.

ExplanationA character other than a hexadecimal character wasdetected. Only hexadecimal characters (0-9,a-f,A-F)are allowed in X, BX, and GX string constants. TheONCODE associated with this message is 634.


Programmer responseInclude a suitable ON-unit in the program to monitorerrors in the input data that are revealed by theCONVERSION condition. Use the ONSOURCE andONCHAR built-in functions to identify the error and theONSOURCE and ONCHAR pseudovariables to assigna valid hexadecimal character so the program cancontinue processing. Also, ensure all input is in thecorrect format before executing the program.


IBM0055S ONCODE=635 The CONVERSIONcondition was raised because aninvalid character was detected inan X, BX, or GX string constant


on input after the TRANSMITcondition was detected.

ExplanationA character other than a hexadecimal character wasdetected. Only hexadecimal characters (0-9,a-f,A-F)are allowed in X, BX, and GX string constants. Atransmission error also occurred and may be thesource of the conversion error.




IBM0056S ONCODE=636 The CONVERSIONcondition was raised because agraphic string contained an invalidcharacter.

ExplanationThis condition was raised by the GRAPHIC built-infunction. The source was a graphic (DBCS) string and ashift character was detected in it.


Programmer responseRemove the shift characters from the graphic (DBCS)string. ONSOURCE and ONCHAR pseudovariablescannot be used to assign a new value to the string.ERROR is raised if retry is attempted.


IBM0059S ONCODE=639 The CONVERSIONcondition was raised because amixed character string containedan invalid character.

ExplanationThis condition was raised by the GRAPHIC built-in function. One of the following rules for mixedconstants was broken:

• SBCS portions of the constant cannot contain a shift-in.

• Neither byte of a DBCS character can contain a shiftcode.

Note: In mixed character strings, a shift-in followinga DBCS character or following a shift-out causes atransition to single-byte mode. It is impossible for thefirst byte of a DBCS character in a mixed characterstring to contain a shift-in.


Programmer responseEnsure mixed character strings contain balanced,unnested shift-out/shift-in pairs. The MPSTR built-infunction can be used to check shift-out/shift-in pairs.ONSOURCE and ONCHAR pseudovariables cannot beused to assign a new value to the string. ERROR israised if retry is attempted.


IBM0060S ONCODE=667. The CONVERSIONcondition was raised becausethere was no SBCS equivalentin the GRAPHIC conversion tocharacter.

ExplanationThis condition is raised during an attempt to converta GRAPHIC string, containing ASCII DBCS characters,that represents a character value. The string containeda DBCS character for which there is no equivalentSBCS character. The ONCODE associated with thismessage is 667.


Programmer responseModify your program to ensure such strings containonly valid ASCII DBCS characters. Use the ONSOURCEpseudovariable to assign a valid GRAPHIC string to the


ONSOURCE built-in function to allow the conversion tobe retried.


IBM0061S ONCODE=668. The CONVERSIONcondition was raised becausethere was no SBCS equivalentin the GRAPHIC conversion tocharacter on input.

ExplanationThis condition is raised during an attempt to converta GRAPHIC string in an input file, containing ASCIIDBCS character, that represents a character value. Thestring contained a DBCS character for which there is noequivalent SBCS character. The ONCODE associatedwith this message is 668.


Programmer responseModify your program to ensure such strings containonly valid ASCII DBCS characters. Use the ONSOURCEpseudovariable to assign a valid GRAPHIC string to theONSOURCE built-in function to allow the conversion tobe retried.


IBM0062S ONCODE=669. The CONVERSIONcondition was raised becausethere was no SBCS equivalentin the GRAPHIC conversionto character on input afterthe TRANSMIT condition wasdetected.

ExplanationThe CONVERSION condition was raised after an errorcaused the TRANSMIT condition to be raised. For anexample of the conversion error, see the explanationgiven for message IBM0061. The ONCODE associatedwith this message is 669.


Programmer responseIf the conversion error recurs after eliminating thetransmission error, take the steps given for messageIBM0061.

Symbolic Feedback CodeIBM01U

IBM0092I PL/I PLIDUMP was called withTraceback (T) option.

ExplanationPLIDUMP was called with the T option.




IBM0100W ONCODE=oncode-value The NAMEcondition was raised by a SIGNALstatement (FILE= or ONFILE= file-name).

ExplanationThe program contained a SIGNAL statement to raisethe NAME condition for which there was no associatedON-unit. The ONCODE associated with this message is10.

System actionExecution continues with the next sequentialstatement.

Programmer responseEither remove the SIGNAL statement or include anON-unit for the NAME condition in the program.


IBM0101W ONCODE=oncode-value The NAMEcondition was raised becausean invalid element-variable in aSTREAM item was encountered


during a GET FILE DATA statement(FILE= or ONFILE= file-name).

ExplanationOne of the following conditions was detected:

• An identifier in the input stream had no counterpartin the data list of the GET statement, or the GETstatement had no data list and an unknown identifierwas encountered in the stream.

• Invalid blank characters were found within anidentifier in the input stream.

• The name field or part of a qualified name wasomitted.

• There were more than 256 characters in a fully-qualified name.

• Blanks were found within an array subscript otherthan between the optional sign and the decimaldigits.

• An array subscript was missing or indicated toomany dimensions.

• A value in a subscript was not a decimal digit.• The subscript was beyond the declared range of

subscripts for a particular array.• The left-parenthesis was missing after the name of

an array.• A character other than "=" or a blank was found after

a right-parenthesis that delimits an array subscript inthe input stream.

• The end-of-file or a nonblank delimiter was foundbefore "=" in an item in the input stream.

System actionThe incorrect data field is ignored and execution of theGET statement continues.

Programmer responseUse the DATAFIELD built-in function in a NAME ON-unit to obtain the invalid data item.


IBM0120S ONCODE=oncode-value TheRECORD condition was raised bya SIGNAL statement. (FILE= orONFILE= file-name).

ExplanationThe program contained a SIGNAL statement toraise the RECORD condition for which there was noassociated ON-unit.


Programmer responseSupply an ON-unit for the RECORD condition orremove the SIGNAL statement.


IBM0121S ONCODE=oncode-value TheRECORD condition was raisedbecause the length of the recordvariable was less than the recordlength (FILE= or ONFILE= file-name).

ExplanationThis message was produced for records that werelonger than the associated PL/I variable.

1. For a READ statement, the record was truncated tothe length of the variable in the INTO option.

2. For a LOCATE statement (F-format records only), abuffer was not allocated.

3. For a WRITE statement (F-format records only),the record was transmitted with the appropriatenumber of padding bytes added to equal the lengthof the record on the data set. The contents of thepadding bytes were undefined.

4. For a REWRITE statement, the record was replacedby the shorter record with the appropriate numberof padding bytes added to equal the length of therecord on the data set. The contents of the paddingbytes were undefined.


Programmer responseEither supply an ON-unit for the RECORD conditionso the program can continue running, or modify theprogram to make the length of the record variablethe same as the length of the records on the dataset. Refer to the language reference manual for this


compiler for details of how such records are handledwhen the RECORD condition is raised.


IBM0122S ONCODE=oncode-value TheRECORD condition was raisedbecause the length of the recordvariable was greater than therecord length (FILE= or ONFILE=file-name).

ExplanationThis message was produced for records that wereshorter than the associated PL/I variable.

1. For the READ statement using F-format recordsand a fixed-length variable in the INTO option, theexcess bytes in the variable were undefined.

2. For a LOCATE statement, where the maximumlength of the records was less than the length ofthe PL/I variable, the buffer was not allocated.

3. For a WRITE statement, the variable in the FROMoption was longer than the maximum length of therecords, and was truncated to the maximum recordlength.

4. For a REWRITE statement, the variable in the FROMoption was longer than the record it was to replace,and was truncated to the length of this record.


Programmer responseEither supply an ON-unit for the RECORD conditionso the program can continue running, or modify theprogram to make the length of the record variablethe same as the length of the records on the dataset. Refer to the language reference manual for thiscompiler for details of how such records are handledwhen the RECORD condition is raised.

Symbolic Feedback CodeIBM03Q

IBM0123S ONCODE=oncode-value TheRECORD condition was raisedbecause the WRITE or LOCATEvariable had a zero length (FILE=or ONFILE= file-name).

ExplanationA WRITE or REWRITE statement attempted to transmita record variable of zero length, or a LOCATEstatement attempted to obtain buffer space for a zerolength record variable.


Programmer responseEnsure the varying-length string used as a recordvariable is not a null string when the WRITE, REWRITEor LOCATE statement is run.


IBM0124S ONCODE=24 The RECORDcondition was raised because azero length record was read froma Regional data set (FILE= orONFILE= file-name).

ExplanationA record of zero length was read from a REGIONALdata set associated with a DIRECT file. A zero-lengthrecord on a direct-access device indicates the end ofthe data set. However, this message is generated onlyif the data set was created incorrectly. The ONCODEassociated with this message is 24.


Programmer responseEnsure the data set is created correctly as a regionaldata set. If necessary, recreate the data set andensure the record is accessed with a valid key.


IBM0125S ONCODE=oncode-value TheRECORD condition was raisedbecause a WRITE or LOCATEarea was too short to containthe embedded string (FILE= orONFILE=file-name).


ExplanationA record variable was too short to contain the data setembedded key. Either a WRITE or REWRITE statementattempted to transmit the record variable or a LOCATEstatement attempted to allocate buffer space for therecord variable. For a WRITE or REWRITE statement,no transmission takes place. For a LOCATE statement,a buffer is not allocated.


Programmer responseEnsure the record variable is long enough to containthe data set embedded key and the key is valid.


IBM0140S ONCODE=40. The TRANSMITcondition was raised by a SIGNALstatement (FILE= or ONFILE= file-name).

ExplanationThe program contained a SIGNAL statement to raisethe TRANSMIT condition for which there was noassociated ON-unit. The ONCODE associated with thismessage is 40.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the TRANSMIT condition in the program.

Symbolic Feedback CodeIBM04C

IBM0141S ONCODE=oncode-value TheTRANSMIT condition was raisedbecause of an uncorrectable errorin output (FILE= or ONFILE=file-name).

ExplanationData management routines detected an uncorrectableerror while transmitting output data between mainstorage and an external storage device. The condition

was raised on the completion of a WRITE, REWRITEor LOCATE statement. For BUFFERED files, thiscondition can be raised only after executing severalI/O statements following the processing of an OUTPUTfile. The outfile can not be associated with a unitrecord device. Processing of an UPDATE file cancontinue. For INDEXED data sets, the condition canoccur while searching through the indexes or tracingan overflow record. The ONCODEs associated with thismessage are:

• 41 output data set• 42 input data set


Programmer responseIf the error recurs, obtain a dump of the input/output buffer areas by using PLIDUMP in a TRANSMITON-unit. Refer to z/OS Language EnvironmentProgramming Guide for details of PLIDUMP. Theresultant output, together with all relevant listings anddata sets, should be preserved for later study by IBM.


IBM0142S ONCODE=42. The TRANSMITcondition was raised because of anuncorrectable error in input (FILE=or ONFILE= file-name).

ExplanationData management routines detected an uncorrectableerror while transmitting input data between mainstorage and an external storage device. If the blockcontains VS-format records, the error is raised onceonly for the block. Otherwise, the condition is raisedon the completion of a READ or REWRITE statementfor each record in the block that contains the errorand for every item transmitted by GET statementsfrom a block that contains the error. The contentsof the record or data item are undefined. However,processing of subsequent records in the input file canbe continued. For INDEXED data sets, the conditioncan be raised while searching the indexes or tracingan overflow record. The ONCODE associated with thismessage is 42.



Programmer responseIf the error recurs, obtain a dump of the input/outputbuffers by using PLIDUMP in a TRANSMIT ON-unit.Refer to z/OS Language Environment ProgrammingGuide for details of PLIDUMP. Save the PLIDUMPoutput and all relevant listings and data sets for laterstudy by IBM.


IBM0143S ONCODE=oncode-value TheTRANSMIT condition was raisedbecause of unreadable OMR data(FILE= or ONFILE= file-name).

ExplanationOne or more OMR columns contained a marginal mark,weak mark or poor erasure that could not be read.The condition is raised on completion of the READoperation for the information. An X'3F' character issubstituted for unreadable characters, and also put inthe last byte of the record. The ONCODE associatedwith this message is 42.


Programmer responseReplace the information that caused the TRANSMITcondition to be raised. Ensure the data on theinformation is readable by the OMR.


IBM0144S ONCODE=oncode-value TheTRANSMIT condition was raisedbecause of a write error in theindex set (FILE= or ONFILE=file-name).

ExplanationData management detected a physical error whileattempting to write on the index set of a VSAM KSDS.The condition is raised on the completion of a WRITE,REWRITE, LOCATE or DELETE statement. No furtherprocessing of an OUTPUT file can occur. Processing ofan UPDATE file can continue. The ONCODE associatedwith this message is 43.


Programmer responseCheck the DASD on which the data set is being writtenfor errors.


IBM0145S ONCODE=oncode-value TheTRANSMIT condition was raisedbecause of a read error in theindex set (FILE= or ONFILE=file-name).

ExplanationData management detected a physical error whileattempting to read from the index set of a VSAM KSDS.The condition is raised on the completion of a READ,WRITE, REWRITE, LOCATE or DELETE statement. Nofurther processing of an OUTPUT file can occur.Processing of an UPDATE file can continue. If the erroroccurs on a READ statement, no data is transferredto the record variable. For sequential access, dataset positioning can be lost, causing a subsequentREAD without KEY to raise ERROR. Refer to messageIBM0831 for information on sequential access errors.The ONCODE associated with this message is 44.


Programmer responseCheck the DASD on which the data set resides forerrors. If more research is required, consult with thesystem programmer.


IBM0146S ONCODE=oncode-value TheTRANSMIT condition was raisedbecause of a write error in thesequence set (FILE= or ONFILE=file-name).

ExplanationData management detected a physical error whileattempting to write on the sequence set of a VSAMKSDS. The condition is raised on the completion of


a WRITE, REWRITE, LOCATE or DELETE statement.No further processing of an OUTPUT file can occur.Processing of an UPDATE file can continue. TheONCODE associated with this message is 45.


Programmer responseCheck the DASD on which the data set is being writtenfor error. Also, consult with the system programmer.

Symbolic Feedback CodeIBM04I

IBM0147S ONCODE=oncode-value TheTRANSMIT condition was raisedbecause of a read error in thesequence set (FILE= or ONFILE=file-name).

ExplanationData management detected a physical error whileattempting to read from the sequence set of a VSAMKSDS. The condition is raised on the completionof a READ, WRITE, REWRITE, LOCATE or DELETEstatement. No further processing of an OUTPUT filecan occur. Processing of an UPDATE file can continue.If the error occurs on a READ statement, no datais transferred to the record variable. For sequentialaccess, data set positioning can be lost, causing asubsequent READ without KEY to raise ERROR. Referto message IBM0831 for sequential access errors. TheONCODE associated with this message is 46.


Programmer responseCheck the DASD on which the data set resides forerrors. Also, consult with the system programmer.

Symbolic Feedback CodeIBM04J

IBM0160S ONCODE=oncode-value The KEYcondition was raised by a SIGNALstatement (FILE= or ONFILE= file-name).

ExplanationThe program contained a SIGNAL statement to raisethe KEY condition for which there was no associatedON-unit. The ONCODE associated with this message is50.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the KEY condition in the program.


IBM0161S ONCODE=oncode-value The KEYcondition was raised because thespecified key could not be found(FILE= or ONFILE= file-name).

ExplanationA READ, REWRITE or DELETE statement specified arecorded key which could not be found on the data set.In the case of an INDEXED data set, the key in errorwas either higher than the highest level index or therecord was not in the prime area or the overflow areasof the data set. In the case of a DIRECT file associatedwith a data set with REGIONAL organization, the keyin error was not in the specified region or within thesearch limit defined by the LIMCT subparameter ofthe DCB parameter. The ONCODE associated with thismessage is 51.


Programmer responseDetermine why the key was incorrect and modify theprogram or the data set to correct the error. Use ofthe ONKEY built-in function in a KEY ON-unit will aid indetermining the value of the erroneous key.


IBM0162S ONCODE=oncode-value The KEYcondition was raised because thespecified key was already in usein data set (FILE= or ONFILE= file-name).


ExplanationIn the case of data set with INDEXED organization, anattempt was made to transmit a keyed record to a dataset that already held a record with the same key. In thecase of a data set with REGIONAL(1) or REGIONAL(2)organization that was being created sequentially, anattempt was made to transmit a record to a region thatalready contains a record. The ONCODE associatedwith this message is 52.


Programmer responseEither check the validity of the data that is beingprocessed before running the program or use theprogram to check the data. Use of the ONKEY built-infunction in a KEY ON-unit can aid in identifying anerroneous key, correcting it, and allowing processing tocontinue normally.


IBM0163S ONCODE=oncode-value The KEYcondition was raised because thespecified key was less than thevalue of the previous key (FILE= orONFILE= file-name).

ExplanationA key with a value that was less than the value ofthe preceding key was detected during the creation orextension of an INDEXED or REGIONAL SEQUENTIALdata set. The ONCODE associated with this message is53.


Programmer responseEnsure the records written onto an INDEXED orREGIONAL data set that is being created or extendedare in the correct ascending key sequence order. Also,use a KEY ON-unit to comment on the error and, wherepossible, allow processing to continue normally.


IBM0164S ONCODE=oncode-value The KEYcondition was raised becausethe specified key could not beconverted to valid data (FILE= orONFILE= file-name).

ExplanationA WRITE, READ, REWRITE, DELETE or LOCATEstatement for a REGIONAL data set specified a keywith a invalid character-string value. Invalid valuesconsist entirely of blanks, contain characters otherthan 0-9, or a have blank as part of the region number.The ONCODE associated with this message is 54.


Programmer responseEnsure the key is in the correct format. If necessary,use the ONKEY built-in function in a KEY ON-unit toidentify the erroneous key. The ON-unit can be usedto report any such errors and allow processing tocontinue. Records associated with the erroneous keyscan be transmitted in a subsequent run if the keyshave been corrected.


IBM0165S ONCODE=oncode-value The KEYcondition was raised because thespecified key was invalid (FILE= orONFILE= file-name).

ExplanationFor an INDEXED data set, either the KEY or theKEYFROM expression was a null string or an attemptwas made to rewrite a record with the embedded keyof the replacement record not equal to the recordto be overwritten. For a REGIONAL data set, the keyspecified was a null string or a string commencingwith '11111111'B. The ONCODE associated with thismessage is 55.





IBM0166S ONCODE=oncode-value The KEYcondition was raised because thekey specifies a position outsidethe Regional data set (FILE= orONFILE= file-name).

ExplanationA WRITE, READ, REWRITE or DELETE statementspecified a key whose relative record or track valueexceeded the number of records or tracks respectivelyfor the REGIONAL data set. The ONCODE associatedwith this message is 56.




IBM0167S ONCODE=oncode-value The KEYcondition was raised becausespace was not available to add akeyed record (FILE= or ONFILE=file-name).

ExplanationFor a SEQUENTIAL file associated with an INDEXEDdata set, an attempt was made to write or locate arecord during the creation or extension of such a dataset when the space allocated to the data set was full.For a DIRECT file associated with an INDEXED dataset, space in overflow areas was unable to accept theoverflow record. This was caused by the insertion ofa new record by a WRITE statement. For a DIRECTfile associated with a REGIONAL data set, space wasunavailable to add the record in the specified limitof search as specified in the LIMCT subparameterof the DCB parameter. Note that the data set is notnecessarily full. The ONCODE associated with thismessage is 57.


Programmer responseUse the ONKEY built-in function to identify the keyvalue that caused the error. If the key is in error,correct it and continue the job from the point reachedwhen the error occurred. If the key is correct, organizethe data set so the rejected record can be accessed.


IBM0168S ONCODE=oncode-value The KEYcondition was raised because theKEYFROM value was outside theKEYRANGE(s) defined for the dataset (FILE= or ONFILE= file-name).

ExplanationA WRITE or LOCATE statement specified a key witha value outside the key ranges defined for the dataset (VSAM KSDS). The ONCODE associated with thismessage is 58.


Programmer responseUse the ONKEY built-in function to identify the keyvalue that caused the error and correct the program.


IBM0180S ONCODE=oncode-value TheENDFILE condition was raised bya SIGNAL statement (FILE= orONFILE= file-name).

ExplanationThe program contained a SIGNAL statement to raisethe ENDFILE condition for which there was noassociated ON-unit. The ONCODE associated with thismessage is 70.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the ENDFILE condition in the program.



IBM0181S ONCODE=oncode-value TheENDFILE condition was raised(FILE= or ONFILE= file-name).

ExplanationThe end of an input file was detected. The ONCODEassociated with this message is 70.


Programmer responseInclude an ON-unit for the ENDFILE condition for eachinput file in the program to handle the end-of-fileprocessing.


IBM0182S ONCODE=oncode-value TheENDFILE condition was raisedbecause an end-of-file waspreviously encountered in STREAMinput (FILE= or ONFILE= file-name).

ExplanationThe ENDFILE condition was raised when the file markwas encountered but an attempt was made to readbeyond the end of the file. Either an ENDFILE ON-unitwas run and an attempt was made to read the file orthe end-of-file mark was encountered between itemsin the data list of the current GET statement. TheONCODE associated with this message is 70.


Programmer responseIf the program contains an ENDFILE ON-unit, ensurethe program does not attempt to read the file afterthe ENDFILE condition is raised. If the error occurredwhile a GET statement with two or more items in thedata list is running, ensure the GET statement cancomplete by providing sufficient data items before theend-of-file mark is encountered.


IBM0190W The ENDPAGE condition wasraised by a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement toraise the ENDPAGE condition. The message for thiscondition is never issued by PL/I.

System actionNone.



IBM0191W The ENDPAGE condition wasraised.

ExplanationA PUT statement resulted in an attempt to start a newline beyond the limit specified for the current page.The message for this condition is never issued by PL/I.

System actionNone.



IBM0195W The PENDING condition wasraised by a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement toraise the PENDING condition. The message for thiscondition is never issued by PL/I.

System actionNone.




IBM0196W The PENDING condition wasraised.

ExplanationAn attempt was made to read a record fora TRANSIENT INPUT file that was temporarilyunavailable. The message for this condition is neverissued by PL/I.

System actionNone.



IBM0200S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised by a SIGNAL statement(FILE= or ONFILE= file-name).

ExplanationThe program contained a SIGNAL statement to raisethe UNDEFINEDFILE condition for which there was noassociated ON-unit. The ONCODE associated with thismessage is 80.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the UNDEFINEDFILE condition in theprogram.


IBM0201S ONCODE=81 The UNDEFINEDFILEcondition was raised because ofconflicting DECLARE and OPEN

attributes (FILE= or ONFILE= file-name).

ExplanationAn attribute in an OPEN statement conflictedwith an attribute in a DECLARE statement. Theattributes may have been written explicitly or impliedby other attributes. For example, DIRECT impliesKEYED. Also, some RECORD input/output statementsimply file attributes in an implicit OPEN statement.For example, LOCATE implies RECORD OUTPUTBUFFERED SEQUENTIAL. Conflicting attributes are:BACKWARDS

STREAM, OUTPUT/UPDATE, DIRECT, KEYED,EXCLUSIVE, PRINT, TRANSIENT

BUFFEREDSTREAM, UNBUFFERED, PRINT

DIRECTSTREAM, SEQUENTIAL, BACKWARDS, PRINT,TRANSIENT

EXCLUSIVESTREAM, INPUT/OUTPUT, SEQUENTIAL,BACKWARDS, PRINT, TRANSIENT

INPUTOUTPUT/UPDATE, EXCLUSIVE, PRINT

KEYEDSTREAM, BACKWARDS, PRINT

OUTPUTINPUT/UPDATE, EXCLUSIVE, BACKWARDS

PRINTRECORD, INPUT/UPDATE, DIRECT/SEQUENTIAL,BUFFERED/UNBUFFERED, KEYED, EXCLUSIVE,BACKWARDS, TRANSIENT

RECORDSTREAM, PRINT

SEQUENTIALSTREAM, DIRECT, EXCLUSIVE, PRINT, TRANSIENT

STREAMRECORD, UPDATE, DIRECT/SEQUENTIAL,BUFFERED/UNBUFFERED, KEYED, EXCLUSIVE,BACKWARDS, TRANSIENT

TRANSIENTSTREAM, UPDATE, DIRECT/SEQUENTIAL,EXCLUSIVE, BACKWARDS, PRINT

UNBUFFEREDSTREAM, BUFFERED, PRINT

UPDATESTREAM, INPUT/OUTPUT, BACKWARDS, PRINT,TRANSIENT



Programmer responseEnsure the attributes specified on the DECLAREstatement are compatible with the attributes specifiedon the OPEN statement.


IBM0202S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the device typeconflicted with file attributes(FILE= or ONFILE= file-name).

ExplanationA conflict between the device type and the fileattributes was detected. For example, a file with theUPDATE attribute cannot be associated with a papertape reader, a printer, or a magnetic-tape device. TheONCODE associated with this message is 82.


Programmer responseEnsure the device type and the file attributes arecompatible.


IBM0203S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the BLOCKSIZEwas not specified (FILE= orONFILE= file-name).

ExplanationThe blocksize for an output file was not specified. Foran output file, the blocksize must be specified in eitherthe ENVIRONMENT attribute or in the DCB parameterof the DD statement or CMS FILEDEF. The ONCODEassociated with this message is 83.


Programmer responseFor output files, ensure the block size is specified. Forinput files, ensure the block size is valid.


IBM0204S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because a DD statementor CMS FILEDEF was not used in(FILE= or ONFILE=file-name).

ExplanationThe job stream for a file did not contain either a DDstatement or a CMS FILEDEF. The job stream mustcontain a DD statement or a CMS FILEDEF with addname that is either the name of the file (if theTITLE option is not specified) or the name providedby the TITLE option. The ONCODE associated with thismessage is 84.


Programmer responseSpecify a DD statement or CMS FILEDEF to associatethe file with a physical data set.


IBM0205S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because of an I/O error -the Regional data set could not beformatted (FILE= or ONFILE=file-name).

ExplanationAn I/O error prevented the data set from beingformatted correctly. When a REGIONAL data set isopened for direct output, data management routinesformat the data set into specified regions by writingdummy or control records into the data set.

TF: PROC;OPEN FILE(F) DIRECT OUTPUT;END;




Programmer responseIf the problem recurs, have the direct access device orstorage medium checked by a customer engineer.


IBM0206S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because a LINESIZE orPAGESIZE argument was outsidethe defined limits (FILE= orONFILE= file-name).

ExplanationThe implementation-defined maximum or minimumfor the LINESIZE option of the ENVIRONMENTattribute was exceeded. For F-format and U-formatrecords, the maximum is 32,759. For V-formatrecords, the maximum is 32,751. When usingMSGFILE(SYSPRINT), the maximum is 255. Theminimum for V- and F-format records is 1. Theminimum for V- format PRINT files is 9. The minimumfor V-format non-PRINT files is 10. The ONCODEassociated with this message is 86.


Programmer responseEnsure the argument to the LINESIZE option is withinthe prescribed limits. If the argument is a variable,verify it is a FIXED BINARY (31,0) STATIC variable thatwas correctly initialized before the file was opened.


IBM0207S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the key length wasnot specified (FILE= or ONFILE=file-name).

ExplanationA key length was not specified in either theENVIRONMENT attribute or the DCB parameter of theassociated DD statement.


Programmer responseSpecify the key length and rerun the program.


IBM0208S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the wrongBLOCKSIZE or record length wasspecified (FILE= or ONFILE= file-name).


1. Block size was less than record length.2. For FB-format records, block size was not a

multiple of record length.3. For VS-format and VBS-format consecutive files:

• LRECL=X was specified but RECSIZE was notspecified or was invalid in the ENVIRONMENTattribute.

• The file was opened for update with a specifiedlogical record size exceeding 32,756.

4. For VS-format REGIONAL(3) files, logical recordsize was greater than block size minus four.

5. FUNC=EO was specified with a record length notequal to 80 or FUNC=CO was specified with arecord size not equal to 160.

6. Column binary was specified with a record lengthnot equal to 160 on an output file.

7. FUNC=I (punch interpret) was specified with arecord length not equal to 80 (or 81 if controlcharacters are in use).



Programmer responseThe numbered responses below apply to thecorrespondingly numbered explanations above:

1. Check the block size and record length specifiedin the BLKSIZE and RECSIZE options of


the ENVIRONMENT attribute. If LINESIZE wasspecified, ensure it is compatible with BLKSIZE.

2. If the argument of either option is a variable, ensureit is FIXED BINARY(31,0) STATIC and has beeninitialized.

3. To correct this error:

a. Specify a record size in the ENVIRONMENTattribute or correct its value.

b. Specify a record size less than 32,757.4. Specify a record size less than or equal to the block

size minus four.5. If FUNC=EO is specified, ensure the record length

is 80. If FUNC=CO is specified, ensure the recordlength is 160.

6. Ensure the record length is 160 when columnbinary is specified.

7. If FUNC=I is specified, ensure the record length is80.


IBM0209S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because of conflictingattributes and file organizationspecifications (FILE= or ONFILE=file-name).

ExplanationThe file organization conflicted with one or moreexplicit or implicit file attributes. Refer to the tablebelow for a list of possible conflicts.

Table 5. File Organization and Conflicting Attributes

Organization Conflicting Attributes

CONSECUTIVE DIRECT, EXCLUSIVE, KEYED,TRANSIENT

INDEXED STREAM, TRANSIENT, DIRECTOUTPUT, OUTPUT without KEYED

REGIONAL STREAM, TRANSIENT, OUTPUTwithout KEYED

TP Non-TRANSIENT

VSAM STREAM, TRANSIENT, BACKWARDS,DIRECT OUTPUT, OUTPUT withoutKEYED(KSDS), KEYED(ESDS),DIRECT(ESDS), REUSE for other thanOUTPUT file, DIRECT with NON-UNIQUE INDEXES

None KEYED, TRANSIENT



Programmer responseEnsure the file attributes are compatible with the fileorganization.


IBM0210S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the recordformat was invalid for this fileorganization (FILE= or ONFILE=file-name).

ExplanationThe following combinations of file organization andrecord format are valid:Organization

Record FormatCONSECUTIVE BUFFERED

AllCONSECUTIVE UNBUFFERED

F, FS, V, D, UHFS

F, FB with FILEDATA=TEXT or FILEDATA=BINARYV, VB with FILEDATA=TEXT

INDEXEDF, FB, V, VB

REGIONAL(1)F

REGIONAL(2)F

REGIONAL(3)F, V, VS, U

TP(M), TP(R)None



Programmer responseChange the file declaration so the record format iscompatible with the file organization.



IBM0211S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the record formatwas not specified (FILE= orONFILE= file-name).

ExplanationThe record format was not specified. A record formatmust be supplied for a file with the RECORD attributein either the ENVIRONMENT attribute or in the dataset label. The ONCODE associated with this message is83.


Programmer responseModify the program to include the record format forthe file.


IBM0212S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the KEYLENGTHwas negative or greater than 255(FILE= or ONFILE= file-name).

ExplanationThe KEYLENGTH option of the ENVIRONMENTattribute for this file had an invalid key length greaterthan 255 or less than zero.


Programmer responseCheck the argument of the KEYLENGTH option toensure it is either a constant or a variable with theattributes FIXED BINARY (31,0) STATIC and valuebetween zero and 255 when the file is opened. If theargument is a variable, ensure it is correctly initialized.


IBM0213S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because an invalid KEYLOCvalue was detected (FILE= orONFILE=file-name).


1. The offset of the key within a record was invalid.The sum of the KEYLOC value and the key lengthwas greater than the record length.

2. For blocked ISAM files, either KEYLOC was notspecified or KEYLOC(0) was specified. Both areinvalid.


Programmer responseThe two numbered responses below apply to thenumbered explanations above.

1. Check the value of the argument to the KEYLOCoption. If the argument is a variable, check that it isFIXED BINARY (31,0) STATIC and that it has beencorrectly initialized.

2. Specify a KEYLOC value that is greater than zero.


IBM0214S ONCODE=oncode-value. TheUNDEFINEDFILE condition wasraised because of conflicting orinvalid environment options FILE=or ONFILE=file-name).

ExplanationThere were conflicting environment options.


Programmer responseEnsure all environment options for the file arecompatible. If there are invalid environment optionsspecified, remove or correct them.



IBM0215S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because an invalid BUFOFFvalue was detected (FILE= orONFILE= file-name). ASCII inputdata set are in the range 0 thru 99.


Programmer responseEnsure the value specified in the BUFOFF option iswithin the range of valid values. If the argument is avariable, also ensure if is correctly initialized.


IBM0219S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the MODE orFUNC option conflicts with the fileattribute (FILE= or ONFILE= file-name).

ExplanationThe MODE or FUNC DCB subparameter conflicted witha file attribute. Refer to z/OS Language EnvironmentProgramming Guide for details of possible conflicts.


Programmer responseRemove the conflicting file attribute, or replace it withone that is compatible with the MODE or FUNC optionvalues. For more information on the MODE and FUNCsubparameters of the DCB parameter, refer to z/OSMVS JCL User's Guide.


IBM0220S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the MODE or FUNCoption conflicted with the recordformat (FILE= or ONFILE= file-name).

ExplanationOMR or RCE files, IBM 3525 print files, and IBM 3525associated files can be F-format only. The ONCODEassociated with this message is 88.


Programmer responseEnsure the MODE or FUNC option value is compatiblewith the record format of the file. For more informationon the MODE and FUNC subparameters of the DCBparameter, refer to the z/OS MVS JCL User's Guide


IBM0221S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the device typeconflicted with the MODE option(FILE= or ONFILE= file-name).

ExplanationOMR can be used only on an IBM 3505 and RCE onan IBM 3525 device. The ONCODE associated with thismessage is 88.


Programmer responseEnsure the device type and the MODE option value iscompatible.


IBM0222S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the TOTAL option isinvalid with an OMR or associatedfile (FILE= or ONFILE= file-name).

ExplanationEither the OMR (MODE=EO or MODE=CO) wasspecified on a file with the TOTAL option, or a deviceassociation was specified on a file with the TOTALoption. The ONCODE associated with this message is88.



Programmer responseEither remove the TOTAL option or modify the MODEoption so it is compatible with a file with the TOTALoption.


IBM0223S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because of a conflictbetween the MODE and FUNCoptions (FILE= or ONFILE= file-name).

ExplanationRefer to z/OS Language Environment ProgrammingGuide for details of possible conflicts. The ONCODEassociated with this message is 88.


Programmer responseEnsure the values specified for the MODE and FUNCoptions are compatible. For more information, refer toz/OS MVS JCL User's Guide.


IBM0225S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the value of theENV option conflicted with theactual data set value (FILE= orONFILE= file-name).

ExplanationFor VSAM data sets, the values of KEYLOC,KEYLENGTH and RECSIZE are specified when the dataset is defined. If values are specified on any filedeclarations, they must match the defined values.

For non-VSAM data sets, the attributes specifiedin the environment option (such as RECSIZE andBLOCKSIZE) must match those of the actual physicaldata set.



Programmer responseFor VSAM data sets, ensure the values of KEYLOC,KEYLENGTH and RECSIZE specified in the programmatch the defined values. For non-VSAM data sets,ensure the specified values in the environment optionmatch those of the actual physical data set.


IBM0226S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the NCP or STRNOvalue was not 1 (FILE= or ONFILE=file-name).

ExplanationEither an NCP value greater than one was specifiedin the ENV attribute or a STRNO value greater thanone was specified in the AMP parameter in theDD statement. For VSAM files, only one outstandingoperation is allowed. An operation with the EVENToption must be processed before another operation isstarted.


Programmer responseEnsure the NCP or STRNO value for a VSAM file is oneif the EVENT option is involved, or modify the programto use operations without the EVENT option to allowconcurrent operations on the data set.


IBM0227S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the TOTAL option isinvalid for ESDS (FILE= or ONFILE=file-name).

ExplanationThe specification of TOTAL can cause the compilerto generate in-line code for I/O statements for


CONSECUTIVE files. If the data set to be accessed isa VSAM Entry Sequenced Data set (ESDS) this code isinvalid. The ONCODE associated with this message is91.


Programmer responseRemove the TOTAL option from the file declaration.


IBM0228S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the password wasinvalid or was not specified (FILE=or ONFILE= file-name).

ExplanationFor VSAM data sets defined with a password, ENV(PASSWORD) and the password must be specified inthe file declaration. If the password is incorrect or isnot specified, a number of attempts will be given tospecify the correct password. The number of retriesallowed is specified when the data set is defined. Ifthese attempts fail, UNDEFINEDFILE is raised.

Note: If the Authorized Program Facility (APF) is beingused, the load module must be authorized.



Programmer responseModify the program to include the ENV (PASSWORD)option and the correct password in the file declaration.


IBM0229S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because an entry was notin the VSAM catalog for data set(FILE= or ONFILE= file-name).

ExplanationThe ENV(VSAM) was specified for a file, but the dataset was not converted from ISAM to VSAM. Beforeusing a VSAM data set, a catalog entry must becreated and space allocated for the data set usingthe access method services DEFINE command. Thecatalog containing the data set must be specified ina JOBCAT or STEPCAT DD statement (unless it is themaster catalog). The ONCODE associated with thismessage is 92.


Programmer responseEnsure the data set is catalogued and the right catalogis accessed. Also, ensure the data set is a valid VSAMdata set.


IBM0230S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because of an I/O errorreading the catalog or the volumelabel (FILE= or ONFILE= file-name).

ExplanationAn I/O error prevented the reading of a VSAM catalogor a volume label. The ONCODE associated with thismessage is 92.


Programmer responseConsult with the system programmer.


IBM0231S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because a timestampmismatch was detected (FILE= orONFILE= file-name).


ExplanationFor VSAM data sets, the index and data can beupdated separately and the time of the latest updateof each is recorded. If these times do not match,the integrity of the data is uncertain and an OPENerror will occur. Similarly, the timestamp in the dataset catalog record might not match the timestampon the volume containing the data set. This indicatesthe extent information in the catalog record mightnot agree with the extents indicated in the VTOCfor the volume. Message IEC161 is displayed on theoperator's console and will provide more detail. TheONCODE associated with this message is 92.


Programmer responseResubmit the job. If the error recurs after resubmittingthe job, use PLIDUMP to obtain a storage dump andsave all the relevant information for study by IBM.


IBM0232S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the requested dataset was not available (FILE= orONFILE= file-name).

ExplanationThe data set to be accessed either does not exist orwas already being used by another program and couldnot be shared. Refer to z/OS Language EnvironmentProgramming Guide for further information.


Programmer responseRefer to z/OS Language Environment ProgrammingGuide for more information on sharing data sets.


IBM0233S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the data set was

not properly closed (FILE= orONFILE= file-name).

ExplanationThe last time the data set was opened the closeoperation failed, leaving the data set in an unusablestate. The ONCODE associated with this message is92.


Programmer responseUse the access method services VERIFY command torestore the data set to a usable state. Refer to theMVS/DFP Access Method Services manual for details.


IBM0234S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the data set wasnever loaded (FILE= or ONFILE=file-name).

ExplanationA file can not be opened for INPUT or UPDATE toaccess a VSAM data set until one or more records havebeen loaded into the data set using a SEQUENTIALOUTPUT file. Once records are loaded into the dataset, records can be added using a DIRECT UPDATE fileeven after all records have been deleted from the dataset. The ONCODE associated with this message is 82.


Programmer responseLoad the empty data set first. Then proceed withfurther update/input/delete activity.


IBM0235S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because of an unidentifiederror during VSAM open(FILE= or ONFILE= file-name).Subcode1=sc1 Subcode2=sc2


ExplanationThe VSAM routines detected an error duringthe open process which PL/I did not recognize.Subcode1 and Subcode2 provide detailed VSAMdiagnostic information. See message IBM0811S foran explanation of these fields. VSAM message IEC161will also be displayed on the operator's console andwill provide more detail.


Programmer responseUse the VSAM diagnostic messages to correct thecause of the error and resubmit the program.


IBM0236S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the operatingsystem was unable to OPEN thefile Subcode1= sc1 Subcode2=sc2(FILE= or ONFILE= file-name).

ExplanationThe operating system or access method encounteredan error during the open process. Subcode1 indicateswhy the file could not be opened. Subcode2, if notzero, indicates the return code ( in hexadecimal ) givenby the operating system or access method. Subcode2information is mainly used by IBM support whendiagnosing problems. The meaning of the Subcode1values are as follows:

• 50 - A non-existent ISAM file is being opened forinput.

• 51 - An unexpected error occurred when openingan ISAM file. Subcode2 gives the return code fromISAM.

• 52, 53 - An unexpected error occurred when openinga native or REGIONAL(1) file.

• 54 - A non-existent BTRIEVE file is being opened forinput.

• 55 - An unexpected error occurred when opening aBTRIEVE file. Subcode2 gives the return code fromBTRIEVE.

• 56 - An unexpected error occurred when opening aDDM file.

• 57,58 - An unexpected error occurred when openinga DDM sequential, DDM relative or DDM indexed file.Subcode2 gives the return code from DDM.

• 59 - An attempt was made to open a file that wasalready open.

• 60 - A file of invalid type is being opened. Anexample of this is opening a VSAM file under UNIXSystem Services. VSAM files are not supported underUNIX System Services.

• 66 - Open of a VSAM file failed. Subcode2 gives thefeedback code.

• 125 - A parsing error occurred during processing ofthe DD(ddname(membername)) TITLE option.

• 126 - The DD(ddname(membername)) TITLE optionis only supported in 64-bit mode.



Programmer responseFor Subcodes 50 and 54, ensure the input file exists.For Subcode 60, ensure the file being opened has a filetype that is supported by the operating system underwhich the program is being run. For Subcode 125,check the syntax of the DD(ddname(membername))TITLE option.For all the other subcodes, call IBMSupport for assistance.


IBM0241S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the REUSE optionwas specified for a non-reusabledata set (FILE= or ONFILE= file-name).

ExplanationThe ENVIRONMENT option REUSE can only bespecified with VSAM data sets which have beendefined as reusable during their creation by accessmethod services. The ONCODE associated with thismessage is 94.



Programmer responseRemove the REUSE option.


IBM0242S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the alternate indexpath was empty (FILE= or ONFILE=file-name).

ExplanationAn alternate index can be emptied by having all of itspointers deleted. An empty alternate index cannot beopened. The ONCODE associated with this message is95.


Programmer responseEnsure the index is defined before it is built and theright alternate index is used.


IBM0243S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because an attempt toposition the file at the last recordfailed (FILE= or ONFILE= file-name). Subcode1= sc1 Subcode2=sc2

ExplanationWhen the ENVIRONMENT option BKWD is specifiedfor a file open, the file must be positioned at the lastrecord. If an attempt to position at the last record fails,the file is closed and the UNDEFINEDFILE conditionis raised with this message. Subcode1 and Subcode2provide detailed VSAM diagnostic information. Seemessage IBM0811S for an explanation of thesefields. This message is also issued if the data setonly consists of deleted records. For this case, thesubcodes are zero.


Programmer responseUse the VSAM diagnostic information to correct thecause of the error and resubmit the program.


IBM0250S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because the data set orpath was not found (FILE= file-name).

ExplanationThe specified data set or path name could not befound during dynamic allocation processing for the file.The ONCODE associated with this message is 110.


Programmer responseCorrect the name of the data set or path.

Symbolic Feedback CodeIBM07Q

IBM0251S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because an invalid keywordkeyword was found at positionposition in environment variableenvironment-variable (FILE= file-name).

ExplanationAn invalid keyword was encountered in theenvironment variable string during dynamic allocationprocessing for the file. The ONCODE associated withthis message is 111.


Programmer responseRemove or correct the invalid keyword from theenvironment variable. Ensure that the DSN or PATHkeyword is specified first in the environment variable.



IBM0252S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because keyword keyword1was found at position position inenvironment variable environment-variable and is mutually exclusivewith keyword keyword2 (FILE=file-name).

ExplanationConflicting keywords were detected during dynamicallocation processing for the file. The ONCODEassociated with this message is 112.


Programmer responseRemove one of the conflicting keywords from theenvironment variable.


IBM0253S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because an invalid delimiterwas found at position position inenvironment variable environment-variable (FILE= file-name).

ExplanationA bad delimiter was detected during dynamicallocation processing for the file. The ONCODEassociated with this message is 113.


Programmer responseCorrect the identified delimiter in the environmentvariable.


IBM0255S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because temporary data setnames cannot be used for dynamicallocation in environment variableenvironment-variable (FILE= file-name).

ExplanationThe DSN parameter of the environment variablespecified a temporary data set name, which isnot supported for dynamic allocation. The ONCODEassociated with this message is 115.


Programmer responseChange the DSN parameter in the specifiedenvironment variable to specify a permanent data setname.


IBM0256S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because an absolute pathname was not specified inenvironment variable environment-variable (FILE= file-name).

ExplanationThe PATH parameter of the environment variable didnot specify an absolute path name. Only absolute pathnames are supported. The ONCODE associated withthis message is 116.


Programmer responseChange the PATH parameter in the specifiedenvironment variable to specify an absolute pathname.


IBM0257S ONCODE= oncode-value TheUNDEFINEDFILE condition was


raised because the environmentvariable environment-variablecontains an invalid data set name(FILE= file-name).

ExplanationThe data set name specified in the DSN keyword ofthe environment variable was invalid. The ONCODEassociated with this message is 117.


Programmer responseCorrect the data set name in the DSN keyword of theenvironment variable.


IBM0258S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because the environmentvariable environment-variablecontains an invalid member name(FILE= file-name).

ExplanationThe member name specified in the DSN keyword ofthe environment variable was invalid. The ONCODEassociated with this message is 118.


Programmer responseCorrect the member name in the DSN keyword of theenvironment variable.


IBM0259S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because the environmentvariable environment-variablecontains an invalid path name(FILE= file-name).

ExplanationThe path name specified in the PATH keyword ofthe environment variable was invalid. The ONCODEassociated with this message is 119.


Programmer responseCorrect the path name in the PATH keyword of theenvironment variable.


IBM0260S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because of an incorrectenvironment variable (FILE= orONFILE= file-name).

ExplanationEither the DD environment variable defining thecharacteristics of the data set or the name in the TITLEoption of the OPEN statement was entered incorrectly,contained an invalid option, or was too long. TheONCODE associated with this message is 96.


Programmer responseCorrect the SET DD command (OS/2 and Windows),the export DD command (AIX® and UNIX SystemServices), or the filespec in the TITLE option of theOPEN statement and then rerun your program.


IBM0265S ONCODE=oncode-value. TheUNDEFINEDFILE condition wasraised because the file couldnot be opened Subcode1= sc1Subcode2=sc2 (FILE= or ONFILE=file-name).

ExplanationThe file could not be opened. Subcode1 indicates whythe file could not be opened and Subcode2, if not zero,


indicates the return code ( in hexadecimal ) given bythe operating system or DDM. Subcode2 informationis mainly used by IBM support when diagnosingproblems. The meaning of the Subcode1 values are asfollows:

Subcode 1

value

Meaning

1, 2 No RECCOUNT or RECSIZE values weregiven via the ENVIRONMENT option or theset DD or export DD environment variable.

3 A positioning error occurred for asequential output file.

4 TYPE(FIXED) was specified for a nativefile, but the file size was not a multiple ofRECSIZE.

5, 13 A positioning error occurred for aregional(1) file.

6 - 12 A positioning error occurred for an outputfile.

21 - 23 AMTHD(DDM) was specified on theDD environment variable but the DDMloadable component (DUBRUN andDUBLDM on OS/2, or PLI_DDM on AIX)could not be found or could not beaccessed on the system.

24 Incorrect extended attribute existed on aDDM file.

25 The ORGANIZATION option of theENVIRONMENT attribute conflicted withthe type of data set (DDM or native).

26 Conflicts exist with the way the file is beingused.

27 A composite key was detected witha keyed-opening. Composite keys areacceptable only for non-keyed openings.

28 - 30 A new DDM file could not be created.

31 A positioning error occurred for a DDM file.

35 AMTHD(BTRIEVE) was specified on theDD environment variable but the BTRIEVEloadable component (BTRCALLS) could notbe found or could not be accessed on thesystem.

36 Unexpected error occurred when openinga BTRIEVE file.

37 A new BTRIEVE file could not be created.

Subcode 1

value

Meaning

38 A positioning error occurred for a BTRIEVEfile.

40 AMTHD(ISAM) was specified on theDD environment variable but theISAM non-multithreading loadablecomponents(IBMOS20F and IBMOS20Gon OS/2, or IBMWS20F and IBMWS20Gon Windows) or the ISAM multithreadingloadable components(IBMOM20F andIBMOM20G on OS/2, or IBMWM20F andIBMWM20G on Windows) could not befound or could not be accessed on thesystem.

41 Unexpected error occurred when openingan ISAM file.

42 A new ISAM file could not be created.

43 A positioning error occurred for an ISAMfile.

62 Query for file information failed for a VSAMfile under MVS batch.

63 A non-VSAM file is being opened as aVSAM file under MVS batch.

64 A VSAM file is being opened with an invalidtype (that is, the file is not a KSDS, ESDS,or RRDS file).

65 A VSAM file is being opened in a non-MVSbatch environment. VSAM files are onlysupported under MVS batch.

67 A VSAM file is being opened as a non-VSAM file under MVS batch.

68 An invalid VSAM file is opened.

69 Query for file information failed for a nativefile under MVS batch.

70 Positioning for a VSAM file failed.



Programmer responseRe-issue the DD environment variable and use theinformation to correct the program.



IBM0269S ONCODE=oncode-value. TheUNDEFINEDFILE condition wasraised because the file functionconflicted with the DDM dataset definition (FILE= or ONFILE=file_name).

ExplanationA conflict existed between the I/O functions intendedfor the file and the functions allowed on the data set.One of the following was detected when attempting toopen a file to be accessed by the DDM access method:

• The file was being opened for INPUT but the data setwas not get capable

• The file was being opened for UPDATE, but the dataset was not insert capable, get capable, modifycapable, or delete capable

• The file was being opened for OUTPUT, but the dataset was not insert capable


Programmer responseEnsure the correct data set is being referenced andthe data set is re-created with an appropriate set ofcapabilities.


IBM0270S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because the dynamicallocation failed for ddnameddname Error code = error-codeReason code = reason-code Errorinfo = error-info Return code =dynalloc-rc (FILE= file-name).

ExplanationAn error occurred during the dynamic allocation phasefor the file associated with the ddname. The ONCODEassociated with this message is 120.


Programmer responseSee the JOBLOG output for any additional messagesfrom data management explaining the error. Foradditional information about the error codes, see thetopic about interpreting DYNALLOC return codes inz/OS MVS Programming: Authorized Assembler ServicesGuide.


IBM0271S ONCODE= oncode-value TheUNDEFINEDFILE condition wasraised because the dynamicdeallocation failed for ddnameddname Error code = error-codeReason code = reason-code Errorinfo = error-info Return code =dynalloc-rc (FILE= file-name).

ExplanationAn error occurred while attempting to dynamicallydeallocate the file associated with the ddname. TheONCODE associated with this message is 121.




IBM0280S The ERROR condition was raisedby a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe ERROR condition.



Programmer responseEither remove the SIGNAL statement or include anON-unit for the ERROR condition in the program thattransfers control out of the ON-unit with a GO TOstatement.


IBM0281S A prior condition was promoted tothe ERROR condition.

ExplanationThis condition was raised by PL/I because the implicitaction occurred for a PL/I condition that includesraising the ERROR condition as part of its implicitaction.

The message for this condition is never issued, but itcan appear in a dump. Note that the message for theprior condition was issued.


Programmer responseInvestigate the prior condition that led to the ERRORcondition. Remove the cause of that condition, orinclude an ON-unit for that condition or an ON-unit forthe ERROR condition.


IBM0290S ONCODE=oncode-value. TheCONVERSION condition wasraised because a conversion fromPICTURE format contained aninvalid character.

ExplanationAn invalid character was detected in a picture stringthat was being converted to an arithmetic data type.


Programmer responseIf the error is in the conversion of a PL/I sourceprogram constant or in the conversion of a picturecharacter string while the program is running, correct

the source program, recompile it, and rerun theprogram.


IBM0291S ONCODE=oncode-value. TheCONVERSION condition wasraised because a conversion fromPICTURE format contained aninvalid character on input oroutput.

ExplanationA picture character which was invalid for conversionto an arithmetic form was detected in one of thefollowing:

• An arithmetic constant in a list-directed or data-directed item

• A picture character constant being converted to anarithmetic form in a list-directed or data-directeditem

• A PICTURE format input field being converted to anarithmetic form


Programmer responseInclude a suitable ON-unit in the program to monitorerrors in the input data that are revealed by theCONVERSION condition. Use the ONSOURCE andONCHAR built-in functions to identify the error, andthe ONSOURCE and ONCHAR pseudovariables toassign a valid numeric value so the program cancontinue running normally. Otherwise, ensure all inputis in the correct format before running the program.


IBM0292S ONCODE=oncode-value. TheCONVERSION condition wasraised because a conversionfrom PICTURE format containedan invalid character on inputor output after the TRANSMITcondition was detected.


ExplanationA picture character which was invalid for conversionto an arithmetic form was detected in one of thefollowing:

• An arithmetic constant in a list-directed or data-directed item

• A picture character constant being converted to anarithmetic form in a list-directed or data-directeditem

• A PICTURE format input field being converted to anarithmetic form

A transmission error also occurred and may havecaused the conversion error.


Programmer responseCorrect the transmission error. If the conversion errorrecurs after the transmission error is corrected, referto the steps for message IBM0291.


IBM0300S ONCODE=320 The ZERODIVIDEcondition was raised by a SIGNALstatement.

ExplanationThe program contained a SIGNAL statement to raisethe ZERODIVIDE condition for which there was noassociated ON-unit.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the ZERODIVIDE condition in the program.


IBM0301S ONCODE=oncode-value TheZERODIVIDE condition was raised.

ExplanationThe program attempted to execute a statement inwhich a value of zero was used as the divisor in adivision operation. Alternatively, an overflow occurredduring a convert to binary operation.


Programmer responseEither check the data that could produce a zero divisor(or overflow, if doing a convert to binary operation)before running the program or include an ON-unit forthe ZERODIVIDE condition in the program.


IBM0320W ONCODE=oncode-value TheUNDERFLOW condition was raisedby a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe UNDERFLOW condition for which there was noassociated ON-unit. The ONCODE associated with thismessage is 330.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the UNDERFLOW condition in the program.

Symbolic Feedback CodeIBM0A0

IBM0321W ONCODE=oncode-value TheUNDERFLOW condition was raised.

ExplanationThe magnitude of a floating-point number was smallerthan the allowed minimum.

System actionExecution continues from the point at which thecondition was raised.


Programmer responseEither modify the program so that the magnitude ofthe floating-point number is higher than the minimumallowed, or include an ON-unit for the UNDERFLOWcondition in the program.

Symbolic Feedback CodeIBM0A1

IBM0330W The ATTENTION condition wasraised by a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe ATTENTION condition. The message for thiscondition is never issued by PL/I.

System actionNone.


Symbolic Feedback CodeIBM0AA

IBM0340S ONCODE=oncode-value The SIZEcondition was raised by a SIGNALstatement.

ExplanationThe program contained a SIGNAL statement to raisethe SIZE condition for which there was no associatedON-unit. The ONCODE associated with this message is340.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the SIZE condition in the program.

Symbolic Feedback CodeIBM0AK

IBM0341S ONCODE=oncode-value The SIZEcondition was raised in an I/Ostatement.

ExplanationThe high-order (leftmost) significant binary or decimaldigits were lost in an input/output operation wherethe size of the value being transmitted exceededthe declared (or default) size of the data item. TheONCODE associated with this message is 341.


Programmer responseEither modify the program so that the data item islarge enough for the value being transmitted or includean ON-unit for the SIZE condition in the program.

Symbolic Feedback CodeIBM0AL

IBM0342S ONCODE=oncode-value The SIZEcondition was raised.

ExplanationThe high-order (leftmost) significant binary or decimaldigits were lost in an assignment to a variable ortemporary variable where the size of the value beingassigned exceeded the declared (or default) size of thedata item. The ONCODE associated with this messageis 341.


Programmer responseEither modify the program so that the data item islarge enough for the value being assigned to it orinclude an ON-unit for the SIZE condition to allowprocessing to continue when the SIZE condition israised.

Symbolic Feedback CodeIBM0AM

IBM0360W ONCODE=oncode-value TheSTRINGRANGE condition wasraised by a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe STRINGRANGE condition for which there was no


associated ON-unit. The ONCODE associated with thismessage is 350.


Programmer responseEither remove the SIGNAL statement or includean ON-unit for the STRINGRANGE condition in theprogram.

Symbolic Feedback CodeIBM0B8

IBM0361W ONCODE=oncode-value TheSTRINGRANGE condition wasraised.

ExplanationIn the expression SUBSTR(S,I,J), the substringrepresented by starting position I for a length of J doesnot lie wholly within the string S.

System actionExecution continues with a revised SUBSTR reference.Refer to the Language Reference Manual for detailsregarding the value of the revised SUBSTR reference.

Programmer responseEnsure that the values used for I and J are neither lessthan nor greater than the length of S.

Symbolic Feedback CodeIBM0B9

IBM0365W The FINISH condition was raisedby a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe FINISH condition. The message for this conditionis never issued by PL/I.

System actionNone.


Symbolic Feedback CodeIBM0BD

IBM0366S The FINISH condition was raisedduring a STOP statement.

ExplanationThe program contained a STOP statement whichcaused the FINISH condition to be raised. Themessage for this condition is never issued by PL/I.

System actionNone.


Symbolic Feedback CodeIBM0BE

IBM0367S The FINISH condition was raisedby a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raiseduring an EXIT statement which caused the FINISHcondition to be raised. The message for this conditionis never issued by PL/I.

System actionNone.


Symbolic Feedback CodeIBM0BF

IBM0368W The FINISH condition was raiseddue to a RETURN or ENDstatement in the main procedure.

ExplanationThe program completed normally, and as a result theFINISH condition was raised. The message for thiscondition is never issued by PL/I.

System actionNone.



Symbolic Feedback CodeIBM0BG

IBM0369S The FINISH condition was raisedafter the ERROR condition.

ExplanationThe FINISH condition was raised as the normal returnaction or implicit action for the ERROR condition. Themessage for this condition is never issued by PL/I.

System actionNone.


Symbolic Feedback CodeIBM0BH

IBM0380S ONCODE=oncode-value The AREAcondition was raised by a SIGNALstatement.

ExplanationThe program contained a SIGNAL statement to raisethe AREA condition for which there was no associatedON-unit. The ONCODE associated with this message is362.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the AREA condition in the program.

Symbolic Feedback CodeIBM0BS

IBM0381S ONCODE=oncode-value The AREAcondition was raised because thetarget area was too small for theAREA assignment.

ExplanationIn an assignment of an area variable, the currentextent of the area on the right-hand side of theassignment statement was greater than the size ofthe area to which it was to be assigned. The ONCODEassociated with this message is 361.


Programmer responseModify the program to ensure that the target area islarge enough to contain the source area.

Symbolic Feedback CodeIBM0BT

IBM0382S ONCODE=oncode-value The AREAcondition was raised because ofinsufficient contiguous space inthe area for allocation.

ExplanationInsufficient space was available in the specified areafor the allocation. The ONCODE associated with thismessage is 360.


Programmer responseProvide an ON-unit to allow the allocation to be triedagain. If necessary, change the value of the pointerqualifying the reference to the inadequate area so thatit points to another area in which the allocation can betried again.

Symbolic Feedback CodeIBM0BU

IBM0400W ONCODE=oncode-value TheCONDITION condition was raisedby a SIGNAL statement andthe condition condition-name wassignaled.

ExplanationThe program contained a SIGNAL statement to raisethe CONDITION condition for which there was no


associated ON-unit. The ONCODE associated with thismessage is 500.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the CONDITION condition in the program.

Symbolic Feedback CodeIBM0CG

IBM0420S ONCODE=oncode-value TheSUBSCRIPTRANGE condition wasraised by a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe SUBSCRIPTRANGE condition for which there wasno associated ON-unit. The ONCODE associated withthis message is 520.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the SUBSCRIPTRANGE condition in theprogram.

Symbolic Feedback CodeIBM0D4

IBM0421S ONCODE=oncode-value. TheSUBSCRIPTRANGE condition wasraised.

ExplanationAn array subscript exceeded the declared bound forthe array.


Programmer responseIn order to ensure that the program can continueprocessing after encountering a subscript range error,

include an ON-unit for this condition which runsa GOTO statement to the appropriate place in theprogram. Also, recompile the program. Normal returnfrom a SUBSCRIPTRANGE ON-unit will produce thismessage and raise the error condition. Note thatarray handling operations are made slower whenSUBSCRIPTRANGE is enabled.

Symbolic Feedback CodeIBM0D5

IBM0430S ONCODE=oncode-value. TheASSERTION condition was raisedby a SIGNAL statment.

ExplanationThe program contained a SIGNAL statement to raisethe ASSERTION condition for which there was noassociated ON-unit.



Programmer responseModify your program to use the built-in functioncorrectly.

Symbolic Feedback CodeIBM0DE

IBM0431S ONCODE=oncode-value. AnASSERT statement failed.

ExplanationAn ASSERT TRUE or ASSERT FALSE statement failed.



Programmer responseModify the program to ensure that the conditiondoes not recur or provide an ON-unit to handle thecondition.

Symbolic Feedback CodeIBM0DF


IBM0432S ONCODE=oncode-value. AnASSERT statement failed with texttext-insert .

ExplanationAn ASSERT TRUE or ASSERT FALSE statement failed.




Symbolic Feedback CodeIBM0DG

IBM0433S ONCODE=oncode-value. AnASSERT UNREACHABLE statementfailed.

ExplanationAn ASSERT UNREACHABLE statement failed.




Symbolic Feedback CodeIBM0DH

IBM0434S ONCODE=oncode-value. AnASSERT UNREACHABLE statementfailed with text text-insert.

ExplanationAn ASSERT UNREACHABLE statement failed.




Symbolic Feedback CodeIBM0DI

IBM0435S ONCODE=oncode-value. AnASSERT COMPARE statementfailed.

ExplanationAn ASSERT COMPARE statement failed.




Symbolic Feedback CodeIBM0DJ

IBM0436S ONCODE=oncode-value. AnASSERT COMPARE statementfailed with text text-insert.

ExplanationAn ASSERT COMPARE statement failed.





Symbolic Feedback CodeIBM0DK

IBM0440W ONCODE=oncode-value TheSTRINGSIZE condition was raisedby a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe STRINGSIZE condition for which there was noassociated ON-unit. The ONCODE associated with thismessage is 150.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the STRINGSIZE condition in the program.

Symbolic Feedback CodeIBM0DO

IBM0441W ONCODE=oncode-value TheSTRINGSIZE condition was raised.

ExplanationA string was assigned to a shorter string, causingright-hand characters or bits in the source string to betruncated.


Programmer responseDetermine whether or not truncation of the right-handcharacters or bits in the source string is correct. Usean ON-unit to record the relevant data or modifythe program as required. Note that string-handlingoperations are made slower when STRINGSIZE isenabled.

Symbolic Feedback CodeIBM0DP

IBM0442W ONCODE=151 The STRINGSIZEcondition was raised. Thecondition was detected during

a mixed character stringassignment.

ExplanationThis condition was raised by one of the CHAR,GRAPHIC, or MPSTR built-in functions. The target wasnot long enough to contain the result. This targetcan be the actual target or a temporary target thatis created by the program. This condition may haveoccurred also due to a mixed character assignmentwith STRINGSIZE enabled and CHARGRAPHIC ineffect for the procedure or block. An MPSTR call isgenerated in this case.


Programmer responseDetermine whether or not truncation of right-handcharacters in the result is correct. Use an ON-unit torecord the relevant data or modify the program asrequired.

Symbolic Feedback CodeIBM0DQ

IBM0450S ONCODE=oncode-value TheSTORAGE condition was raised bya SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe STORAGE condition for which there was noassociated ON-unit.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the STORAGE condition in the program.

Symbolic Feedback CodeIBM0E2

IBM0451S ONCODE=oncode-value TheSTORAGE condition was raised.


ExplanationThere was insufficient storage available to satisfy arequest for additional storage. For a storage allocationfor a BASED variable, the variable was not allocatedand its associated pointer will be undefined. For astorage allocation for a CONTROLLED variable, thecontrolled variable's generation was not allocated.A reference to the controlled variable will result inthe access of a previous generation of the controlledvariable (if any).


Programmer responseAttempt to free the allocated storage through a FREEstatement or within an ON-unit, or provide necessarysteps in the ON-unit to terminate the program withoutlosing pertinent information.

Symbolic Feedback CodeIBM0E3

IBM0460S ONCODE=oncode-value. TheOVERFLOW was raised by aSIGNAL statement.

ExplanationThe OVERFLOW condition was raised by a SIGNALstatement. :xpl.The program contained a SIGNALstatement to raise the OVERFLOW condition forwhich there was no associated ON-unit. The ONCODEassociated with this message is 300.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the OVERFLOW condition in the program.

Symbolic Feedback CodeIBM0EC

IBM0461S ONCODE=oncode-value TheOVERFLOW condition was raised.

ExplanationThe magnitude of a floating-point number exceededthe allowed maximum.



Symbolic Feedback CodeIBM0ED

IBM0470S ONCODE=oncode-value TheINVALIDOP condition was raisedby a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe INVALIDOP condition for which there was noassociated ON-unit.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the INVALIDOP condition in the program.

Symbolic Feedback CodeIBM0EM

IBM0472S ONCODE=oncode-value. TheINVALIDOP condition was raised.

ExplanationOne of the following types of floating point processorexceptions occurred:

• Invalid floating point operation exceptions, includingthe following:

– Subtraction of two infinities– Multiplication of infinity by 0– Division of two infinities– Division of zero by zero

• Floating point processor stack overflow exception• Floating point processor stack underflow exception• Denormalized operand exception• Precision exception


• Other nonspecific floating point processorexceptions

Continuing execution after an INVALIDOP condition,with or without an INVALIDOP ON-unit, can result infurther conditions being raised and termination of theprogram. Generally, the program should be fixed toprevent INVALIDOP conditions from occurring becausethe occurrence of the INVALIDOP condition indicatesthe program has fatal or near-fatal errors.


Programmer responseEither check the data or sequence of floatingpoint instructions which could cause the INVALIDOPcondition before running the program or insert anINVALIDOP ON-unit to handle the condition wheneverit arises.

Symbolic Feedback CodeIBM0EO

IBM0480S ONCODE=oncode-value TheFIXEDOVERFLOW condition wasraised by a SIGNAL statement.

ExplanationThe program contained a SIGNAL statement to raisethe FIXEDOVERFLOW condition for which there was noassociated ON-unit. The ONCODE associated with thismessage is 310.


Programmer responseEither remove the SIGNAL statement or include anON-unit for the FIXEDOVERFLOW condition in theprogram.

Symbolic Feedback CodeIBM0F0

IBM0482S ONCODE=oncode-value TheFIXEDOVERFLOW condition wasraised.

ExplanationThe length of the result of a fixed-point arithmeticoperation exceeded the allowed maximum.



Symbolic Feedback CodeIBM0F2

IBM0501S ONCODE=oncode-value.Greenwich Mean Time was notavailable for the RANDOM built-infunction.

ExplanationGreenwich Mean Time was not set on the system. TheONCODE associated with this message is 2101.


Programmer responseGreenwich Mean Time needs to be set on the system.Use the OS/2 API DosSetDateTime service to setthe time. Refer to the OS/2 Control ProgrammingReference for details.

Symbolic Feedback CodeIBM0FL

IBM0502S ONCODE=oncode-value. An invalidseed value was detected in theRANDOM built-in function.

ExplanationThe input seed value was not within the valid rangeof 0 to 2,147,483,646. The random number was setto —1. The ONCODE associated with this message is2102.



Programmer responseCorrect the seed value to be within the supportedrange.

Symbolic Feedback CodeIBM0FM

IBM0503S ONCODE=oncode-value. Local timewas unavailable.

ExplanationThe system clock was not set. The ONCODE associatedwith this message is 2103.


Programmer responseSet the system clock using the appropriate OS/2commands or use a program that uses the OS/2 APIDosSetDateTime service. Refer to the OS/2 ControlProgramming Reference for details.

Symbolic Feedback CodeIBM0FN

IBM0504S ONCODE=oncode-value The valueof Y in SECSTODATE(X,Y),DAYS(X,Y), DAYSTODATE(X,Y), orDATETIME(Y) contained an invalidPICTURE.

ExplanationThe character string representing the desired formatfor the output datetime stamp contained an invalidpicture string. The ONCODE associated with thismessage is 2104.


Programmer responseCorrect the format.

Symbolic Feedback CodeIBM0FO

IBM0505S ONCODE=oncode-value X inDAYS(X,(Y)) contained an invalidday value.

ExplanationThe supplied value for the day parameter was notwithin the valid range of 15 October 1582 to 31December 9999. The ONCODE associated with thismessage is 2105.


Programmer responseCorrect the value for the day parameter to be withinthe supported range.

Symbolic Feedback CodeIBM0FP

IBM0506S ONCODE=oncode-value X inDAYS(X,(Y)) contained an invalidmonth value.

ExplanationThe supplied value for the month parameter was notwithin the valid range of October 1582 to December9999. The ONCODE associated with this message is2106.


Programmer responseCorrect the value for the month parameter to be withinthe supported range.

Symbolic Feedback CodeIBMOFQ

IBM0507S ONCODE=oncode-value X inDAYS(X,(Y)) contained an invalidyear value.

ExplanationThe supplied value for the year parameter was notwithin the valid range of 1582 to 9999. The ONCODEassociated with this message is 2107.



Programmer responseCorrect the value for the year parameter to be withinthe supported range.

Symbolic Feedback CodeIBMOFR

IBM0508S ONCODE=oncode-value X inDAYSTODATE(X,(Y)) was outsidethe supported range.

ExplanationX represents the number of days since 15 October1582. The valid range is from 1 to 3,074,324. TheONCODE associated with this message is 2108.


Programmer responseCorrect the value for X to be within the supportedrange.

Symbolic Feedback CodeIBMOFS

IBM0509S ONCODE=oncode-value. X inSECSTODATE(X,(Y)) was outsidethe supported range.

ExplanationX represents the number of seconds elapsed since00:00:00 on 14 October 1582, with 00:00:00.00015 October 1582 being the first supported date/time,and 23:59:59.999 31 December 9999 being the lastsupported date/time. The valid range is from 86,400 to265,621,679,999.999. The ONCODE associated withthis message is 2109.


Programmer responseCorrect the value for X to be within the supportedrange.

Symbolic Feedback CodeIBM0FT

IBM0510S ONCODE=oncode-value. X inDAYSTODATE(X,Y) could not beconverted to a valid Era.

ExplanationAn Era was used in the picture string X specified inthe DAYSTODATE reference, but X was outside thesupported range of Eras. The ONCODE associated withthis message is 2110.


Programmer responseEnsure X contains a valid Lilian day number within therange of supported Eras.

Symbolic Feedback CodeIBM0FU

IBM0511S ONCODE=oncode-value. The offsetfrom Greenwich Mean Time wasunavailable.

ExplanationThe difference between the current local time andthe Greenwich Mean Time was not available from thesystem. The ONCODE associated with this message is2111.


Programmer responseEnsure that both the Greenwich Mean Time and thelocal time are set on the system. Use the OS/2 APIDosSetDateTime service to set the time. Refer to theOS/2 Control Programming Reference for details.

Symbolic Feedback CodeIBM0FV

IBM0512S ONCODE=oncode-value X inSECS(X,Y) or DAYS(X,Y) wasoutside the supported range.

ExplanationThe input date supplied was earlier than 15 October1582 or later than 31 December 9999. The ONCODEassociated with this message is 2112.



Programmer responseCorrect the input date to be within the supportedrange.

Symbolic Feedback CodeIBM0G0

IBM0513S ONCODE=oncode-value X inSECS(X,Y) contained an invalidseconds value.

ExplanationThe supplied value for the seconds parameter wasnot within the valid range of 0 to 59. The ONCODEassociated with this message is 2113.


Programmer responseCorrect the value for the seconds parameter to bewithin the supported range.


IBM0514S ONCODE=oncode-value X inSECS(X,Y) contained an invalidminutes value.

ExplanationThe supplied value for the minutes parameter wasnot within the valid range of 0 to 59. The ONCODEassociated with this message is 2114.


Programmer responseCorrect the value for the minutes parameter to bewithin the supported range.


IBM0515S ONCODE=oncode-value X inSECS(X,Y) contained an invalidhour value.

ExplanationThe valid range for the hour parameter is 0 to 23. Ifthe "AP" field is present, the valid range is 0 to 12. TheONCODE associated with this message is 2115.


Programmer responseCorrect the value for the hour parameter to be withinthe supported range.


IBM0516S ONCODE=oncode-value X inDAYS(X,Y)did not match thepicture specification.

ExplanationThe value of X did not match the format describedby the picture specification. For example, non-numericcharacters appear where only numeric characters areexpected. The ONCODE associated with this messageis 2116.


Programmer responseVerify the format of the input data matches the picturestring specification.

Symbolic Feedback CodeIBMOG4

IBM0517S ONCODE=oncode-value X inSECS(X,Y) did not match thepicture specification.

ExplanationThe value of X did not match the format describedby the picture specification. For example, non-numericcharacters appear where only numeric characters areexpected. The ONCODE associated with this messageis 2117.



Programmer responseVerify the format of the input data matches the picturestring specification.


IBM0518S ONCODE=oncode-value Thedate string returned byDAYSTODATE(X,Y) was truncated.

ExplanationThe output string was not large enough to contain theformatted date value. The ONCODE associated withthis message is 2118.


Programmer responseEnsure the output string is large enough to contain theentire formatted date.

Symbolic Feedback CodeIBMOG6

IBM0519S ONCODE=oncode-value Thetimestamp string returned byDATETIME(X) or SECSTODATE(X,Y)was truncated.

ExplanationThe output string was not large enough to contain theformatted data value. The ONCODE associated withthis message is 2119.


Programmer responseEnsure the output string is large enough to contain theentire formatted date.


IBM0520S ONCODE=oncode-value X inSECSTODATE(X,Y) or DATETIME(X)contained an invalid number-of-seconds value.

ExplanationAn Era was used in the picture string X specified inthe SECSTODATE reference, but X was outside thesupported range of Eras. The ONCODE associated withthis message is 2120.


Programmer responseEnsure X contains a valid number-of-seconds valuewithin the range of supported Eras.


IBM0521S ONCODE=oncode-valueInsufficient data was passed tothe DAYS or SECS built-in function.

ExplanationThe picture string passed to the DAYS or SECSbuilt-in function did not contain enough information.The minimum information required is either month,day, and year, or year and Julian day. The ONCODEassociated with this message is 2121.


Programmer responseEnsure the input data contains, as a minimum, theyear, month, and day, or the year and Julian day.


IBM0522S ONCODE=oncode-value X inSECS(X,Y) or DAYS(X,Y) containedan invalid Era name.

ExplanationX did not contain a supported Japanese or Republicof China Era name. The ONCODE associated with thismessage is 2122.



Programmer responseEnsure X is a valid DBCS string.

Symbolic Feedback CodeIBM0GA

IBM0523S ONCODE=oncode-value SystemError getting local time for theTIMESTAMP built-in function

ExplanationError getting local time from the system clock. TheONCODE associated with this message is 2123.


Programmer responseVerify that the TOD clock is initialized correctly andretry the request. Refer to the z/OS MVS Programming:Assembler Services Reference IAR-XCT for the returncode of the TIME macro. Check with your systemprogrammer if the problem persists.

Symbolic Feedback CodeIBM0GB

IBM0531S ONCODE=oncode-value Operationexception.

ExplanationA programmer-related hardware error was detected.The ONCODE associated with this message is 8091.


Programmer responseIt is possible that an error in the program hascaused part of the instructions that can be run tobe overwritten by data. Other possible causes of anoperation exception might be an attempt to invokean external procedure or other routine that wasnot incorporated into the running program by thelinkage editor, or running a branch instruction that isincorrect because a control block had previously been

overwritten. Consequently, it is advisable to check thelinkage editor diagnostics to ensure that all requestedexternal procedures and subroutines have in fact beenincorporated into the running program, and that anyoverlay phases do not overwrite any phases that arestill active.

Symbolic Feedback CodeIBM0GJ

IBM0532S ONCODE=oncode-value Privilegedoperation exception



Programmer responseIf the error is not in a non-PL/I routine included in therunning program, the PL/I program should be checkedfor an error that could cause the instructions that runto be overwritten by data that matches a privilegedoperation.

Symbolic Feedback CodeIBM0GK

IBM0533S ONCODE=oncode-value EXECUTEexception



Programmer responseIf the error is not in a non-PL/I routine included in therunning program, the PL/I program should be checkedfor an error that could cause the running instructionto be overwritten by data that matches the operationcode for the EXECUTE instruction on.

Symbolic Feedback CodeIBM0GL


IBM0534S ONCODE=oncode-value Protectionexception



Programmer responseIf the error is not in a non-PL/I routine included in therunning program, the PL/I program should be checkedfor an error that could cause the address used by thestore instruction to be corrupted.

Symbolic Feedback CodeIBM0GM

IBM0535S ONCODE=oncode-value Addressingexception



Programmer responseIf the error is not in a non-PL/I routine included inthe running program, the PL/I program should bechecked for an error that could cause the address tobe corrupted.

Symbolic Feedback CodeIBM0GN

IBM0536S ONCODE=oncode-valueSpecification exception



Programmer responseIf the error is not in a non-PL/I routine included inthe running program, the PL/I program should bechecked for an error that could cause the operand tobe corrupted by overwriting control blocks or sectionsof running code.

Symbolic Feedback CodeIBM0GO

IBM0537S ONCODE=oncode-value Dataexception



Programmer responseThe PL/I program should be checked for an error suchas an operation on a FIXED DECIMAL data item beforeit has been initialized, or an error which could causethe data item to be overwritten.

Symbolic Feedback CodeIBM0GP

IBM0541S ONCODE=oncode-value X inASIN(X) or ACOS(X) was invalid


• ABS(X) was greater than one.

The ONCODEs associated with this message are:

• For real short floating-point arguments:1518

Argument greater than one• For real long floating-point arguments:

1519Argument greater than one

• For real extended floating-point arguments:1520

Argument greater than one



Programmer responseEnsure X is a real expression where ABS(X) is less thanor equal to one.

Symbolic Feedback CodeIBM0GT

IBM0542S ONCODE=oncode-value X inATAN(X) or ATAND(X) was invalid.


• The real and imaginary parts of X were equal to (0,+1i) or (0, –1i).


• For complex short floating-point arguments:1558

Argument equal to (0,+1i) or (0,-1i)• For complex long floating-point arguments:

1559Argument equal to (0,+1i) or (0,-1i)

• For complex extended floating-point arguments:1564

Argument equal to (0,+1i) or (0,-1i)


Programmer responseIf X is complex, ensure X is not equal to +1i or –1i.

Symbolic Feedback CodeIBM0GU

IBM0543S ONCODE=oncode-value X inATANH(X) was invalid

ExplanationOne of the following conditions occurred::

• ABS(X) was greater than one.



Argument greater than one• For real long floating-point arguments:

1515Argument greater than one


Argument greater than one


Programmer responseIf X is real, ensure ABS(X) is less than one. If X iscomplex, ensure X is not equal to +1i or —1i.

Symbolic Feedback CodeIBM0GV

IBM0544S ONCODE=oncode-value X inSIN(X), COS(X), SIND(X) orCOSD(X) was invalid.

ExplanationOne of the following conditions occurred:

• ABS(X) was greater than or equal to K, whereK=2**63 for short and long floating-point values, andK=2**64 for extended floating-point values.

• The absolute value of the real part of X was greaterthan or equal to K, where K=2**63 for complexshort and long floating-point values, and K=2**64 forcomplex extended floating-point values.

• An overflow occurred because the absolute value ofthe imaginary part of X was greater than K, where Kis as follows:

– 89.76 for complex short floating-point arguments– 710.82 for complex long floating-point arguments– 11357.56 for complex extended floating-point

arguments• An overflow occurred because the absolute value of

the imaginary part of X was greater than I but lessthan J, and the absolute value of the real part wasout of range. The values for I and J are as follows:

– I = 89.41 and J = 89.76 for complex shortfloating-point arguments

– I = 710.47 and J = 710.82 for complex longfloating-point arguments

– I = 11357.21 and J = 11357.56 for complexextended floating-point arguments


• For real short floating-point arguments:


1506Argument greater than or equal to limit

2425Argument equal to plus or minus limit


Absolute value of the real part of argumentgreater than or equal to limit

• For real long floating-point arguments:1507

Argument greater than or equal to limit2426

Argument equal to plus or minus limit• For complex long floating-point arguments:

1530Absolute value of the real part of argumentgreater than or equal to limit


Argument greater than or equal to limit• For complex extended floating-point arguments:

1531Absolute value of the real part of argumentgreater than or equal to limit


Programmer responseEnsure X is valid.

Symbolic Feedback CodeIBM0H0

IBM0545S ONCODE=oncode-value X inSINH(X) or COSH(X) was invalid.


• The absolute value of the imaginary part of X wasgreater than or equal to K, where K=2**63 forcomplex short and long floating-point values, andK=2**64 for complex extended floating-point values.

• ABS(X) was greater than 89.41 for X represented asa short floating-point value.

• ABS(X) was greater than or equal to K, whereK=710.47 for long floating-point values andK=11357.22 for extended floating-point values.

• An overflow occurred because the absolute value ofthe real part of X was greater than K, where K is asfollows:


arguments• An overflow occurred because the absolute value of

the real part of X was greater than I but less than J,and the absolute value of the imaginary part was outof range. The values for I and J are as follows:






Absolute value of argument greater than limit• For complex short floating-point arguments:

1914Absolute value of the imaginary part of argumentgreater than or equal to limit


Absolute value of argument greater than or equalto limit

• For complex long floating-point arguments:1915

Absolute value of the imaginary part of argumentgreater than or equal to limit









IBM0547S ONCODE=oncode-value X in TAN(X)or TAND(X) was invalid.


• ABS(X) was greater than or equal to K, whereK=2**63 for short and long floating-point values, andK=2**64 for extended floating-point values.

• The absolute value of the real part of X was greaterthan or equal to K, where K=2**63 for complexshort and long floating-point values, and K=2**64 forcomplex extended floating-point values.

















IBM0548S ONCODE=oncode-value X inTANH(X) was invalid.


• The absolute value of the imaginary part of X wasgreater than or equal to K, where K=2**63 forcomplex short and long floating-point values, andK=2**64 for complex extended floating-point values.

• An overflow occurred because the absolute value ofthe real part of X was greater than 11357.56.

• An overflow occurred because the absolute value ofthe real part of X was greater than 11357.21 butless than 11357.56, and the absolute value of theimaginary part was out of range.











IBM0549S ONCODE=oncode-value X in ERF(X)was invalid.

ExplanationX was not a valid number.



2177Real short floating-point arguments

2178Real long floating-point arguments

2179Real extended floating-point arguments




IBM0550S ONCODE=oncode-value X in EXP(X)was invalid.


• X was less than K, where K is as follows:

– –87.33 for short floating-point arguments– –708.39 for long floating-point arguments– –11355.13 for extended floating-point arguments

• The absolute value of the imaginary part of Xwas greater than or equal to K, where K=2**63for complex short and long floating-point values,and K=2**64 for complex extended floating-pointvalues. :li.An overflow occurred because the realpart of X was greater than K, where K is as follows:


arguments• An overflow occurred because the real part of X was

greater than I but less than J, and the imaginarypart was out of range. The values for I and J are asfollows:




• X was greater than or equal to K, where K is asfollows:

– 88.73 for short floating-point arguments

– 709.79 for long floating-point arguments– 11356.53 for extended floating-point arguments



Argument less than limit1611

Argument greater than or equal to limit• For complex short floating-point arguments:




Argument greater than or equal to limit• For complex long floating-point arguments:




Argument greater than or equal to limit• For complex extended floating-point arguments:





IBM0551S ONCODE=oncode-value X inGAMMA(X) or LOGGAMMA(X) wasinvalid.


• X was less than K, where K is as follows:


– for the built-in function GAMMA:– 35.04 for short floating-point arguments– 171.62 for long floating-point arguments– 1755.54 for extended floating-point arguments– for the built-in function LOGGAMMA:– 4.085E+36 for short floating-point arguments– 2.559E+305 for long floating-point arguments– 1.048E+4928 for extended floating-point

arguments• For GAMMA(X), X was less than or equal to zero.• For LOGGAMMA(X), X was less than zero.• For GAMMA(X), the calculated result was greater

in magnitude than the largest finite numberrepresentable in the result data type.



Argument greater than limit2165

Argument less than or equal to zero• For real long floating-point arguments:

1572Argument greater than limit

2166Argument less than or equal to zero


Argument greater than limit2164

Argument less than zero2167

Argument equal to zero2403

Argument less than or equal to minus zero2404

Argument equal to zero


Programmer responseIf X is numeric, ensure X is greater than zero.


IBM0552S ONCODE=oncode-value X inLOG(X), LOG10(X) or LOG2(X) wasinvalid.


• X was less than or equal to zero.• A floating point division by zero occurred because X

was equal to (0,0i).




Argument equal to plur or minus zero• For complex short floating-point arguments:

2413X equal to (0,0i)



Argument equal to plus or minus zero• For complex long floating-point arguments:

2414X equal to (0,0i)


Programmer responseIf X is real, ensure X is greater than zero. If X iscomplex, ensure X is not equal to 0 + 0i.


IBM0553S ONCODE=oncode-value TheERFC(X) was invalid.


• X was greater than K, where K is as follows:

– 9.19 for short floating-point arguments– 26.54 for long floating-point arguments– 106.53 for extended floating-point arguments




Argument greater than limit• For real long floating-point arguments:

2172Argument greater than limit


Argument greater than limit


Programmer responseEnsure X is greater than zero.


IBM0554S ONCODE=oncode-value X inSQRT(X) was invalid.


• X was less than zero• X was equal to minus zero.




Argument equal to limit• For real long floating-point arguments:

1501Argument less than zero

1962Argument equal to limit


Programmer responseEnsure X is greater than zero.

Symbolic Feedback CodeIBM0HA

IBM0555S ONCODE=oncode-value X inABS(X) was invalid.

ExplanationThe calculated result was greater in magnitude thanthe largest finite number representable in the resultdata type.

The ONCODEs associated with this message are 2504,2505, 2506.



Symbolic Feedback CodeIBM0HB

IBM0560S ONCODE=oncode-value The EVENTvariable, as argument to theCOMPLETION pseudovariable, wasalready in use with file file-name.

ExplanationThe event variable used in this statement was alreadyactive and associated with an input/output operationon the named file. The ONCODE associated with thismessage is 3904.


Programmer responseModify the program so that the COMPLETIONpseudovariable refers to the event variable when it isinactive.

Symbolic Feedback CodeIBM0HG

IBM0561S ONCODE=oncode-value The TASKvariable was already in use withentry entry-name.


ExplanationThe task variable specified in a CALL statement isalready associated with an active task. The namedentry denotes the entry point of the task with whichthe variable is associated. The ONCODE associatedwith this message is 3901.


Programmer responseModify the program so that the task variable isuniquely associated with each task in the application.

Symbolic Feedback CodeIBM0HH

IBM0562S ONCODE=oncode-value The EVENTvariable, as argument to theCOMPLETION pseudovariable, wasalready in use with a DISPLAYstatement.

ExplanationThe event variable used in this statement was alreadyactive and associated with a DISPLAY statement.



Programmer responseModify the program so that the COMPLETIONpseudovariable refers to the event variable when it isinactive.

Symbolic Feedback CodeIBM0HI

IBM0563S ONCODE=oncode-value The EVENTvariable was already in use withfile file-name.

ExplanationThe event variable used in this statement was alreadyactive and associated with another input/outputoperation on the named file. The ONCODE associatedwith this message is 3907.


Programmer responseModify the program so that the input/output operationrefers to another event variable, or include a WAITstatement to prevent the statement from running untilthe active event is complete.

Symbolic Feedback CodeIBM0HJ

IBM0564S ONCODE=oncode-value The EVENTvariable being assigned wasalready in use with file file-name.

ExplanationAn attempt was made to assign a value to an eventvariable while it was still associated with an input/output operation.

DCL X FILE RECORD INPUT UNBUFFEREDENV(BLKSIZE(80) RECSIZE(80) F);DCL Y CHAR(80);DCL (Z,Z1) EVENT;READ FILE(X) INTO(Y) EVENT(Z);Z = Z1;



Programmer responseModify the program so that the event variable used asthe target in the assignment, or as the argument of theCOMPLETION pseudovariable, is not the same eventvariable associated with an input/output operation.Alternatively, include a WAIT statement to preventthis statement from running until the active event iscomplete.

Symbolic Feedback CodeIBM0HK

IBM0566S ONCODE=oncode-value The taskwas not created because the totalnumber of active tasks wouldexceed the allowable limit.

ExplanationThe request to create a task was not honoredbecause otherwise the total number of concurrently


active tasks would exceed the limit set either bythe PLITASKCOUNT run-time option or the underlyingUNIX System Services installation default for themaximum number of threads.



Programmer responseIncrease the number of tasks allowed to be activeconcurrently or modify the program so that theexisting number of tasks is not exceeded.

Symbolic Feedback CodeIBM0HM

IBM0567S ONCODE=oncode-value A WAIToccurred in the ON-unit for theI/O event required for the currenttask.

ExplanationA WAIT statement specified an event variable. Thecompletion of the event caused entry to an ON-unitfor an I/O condition which contained another WAITstatement for the same event variable as in the originalWAIT statement.

DCL F FILERECORD OUTPUT UNBUFFEREDENV(BLKSIZE(80) RECSIZE(80) F);ON RECORD(F) BEGIN;WAIT(E);END;WRITE FILE(F) FROM (X) EVENT(E);WAIT(E); (this statement raises therecord condition)



Programmer responseRemove the WAIT statement from the ON-unit for theinput/output condition.

Symbolic Feedback CodeIBM0HN

IBM0568S ONCODE=oncode-value Theassigned EVENT variable was

already in use with a DISPLAYstatement.

ExplanationThe event variable specified as the argument of theCOMPLETION built-in function, or used as the targetin an assignment, was still associated with a DISPLAYstatement.

DCL A CHAR,COMPLETION BUILTIN;DISPLAY('MESSAGE TO OPERATOR')REPLY(A) EVENT(E);COMPLETION(E)='1'B;

ONCODEs associated with this message are:

• 3904—event variable as argument to theCOMPLETION built-in function

• 3907—event variable is active


Programmer responseModify the program so that the event variable usedas the target in the assignment or as the argumentof the COMPLETION pseudovariable is not the sameevent variable associated with the DISPLAY statement.Or include a WAIT statement to prevent this statementfrom running until the active event is complete.

Symbolic Feedback CodeIBM0HO

IBM0569S ONCODE=oncode-value Theassigned EVENT variable wasalready active and was used withentry entry-name.

ExplanationAn active event variable was specified as the target ofan event variable assignment.

DCL (E,E1) EVENT;CALL P EVENT(E);E=E1;P: PROC;END;


• 3906 - event assignment• 3907 - event variable is active



Programmer responseEither use another inactive event variable, or includea WAIT statement to ensure that this statement is notrun until the active event is complete.

Symbolic Feedback CodeIBM0HP

IBM0570S ONCODE=oncode-value The EVENTvariable was active and was usedwith entry entry-name.

ExplanationAn active event variable was specified in the EVENToption of an input/output statement.



Programmer responseEither insert a WAIT statement to ensure the event inquestion is inactive when this statement is run, or ifthe statement can be run correctly before the currentlyactive event is complete, use another inactive eventvariable.

Symbolic Feedback CodeIBM0HQ

IBM0571S ONCODE=oncode-value The EVENTvariable was already used with aDISPLAY statement.

ExplanationThe event variable specified in the statement wasalready associated with a DISPLAY statement. TheONCODE associated with this message is 3907.


Programmer responseEither use a different event variable or insert a WAITstatement so that the DISPLAY statement is completebefore this statement is run.

Symbolic Feedback CodeIBM0HR

IBM0572S ONCODE=oncode-value A CALLstatement with the TASK, EVENT,or PRIORITY option was found in aPUT FILE (SYSPRINT) statement.

ExplanationA tasking CALL statement is not allowed from a PUTFILE (SYSPRINT) statement because no programsin the attempted new task via the tasking CALLstatement can produce output on SYSPRINT while aPUT statement is running, and task interlock is likely tooccur.

DCL X FIXED BIN(15);PUT LIST(F(X));F: PROC(X);CALL E TASK;X=5;RETURN (X);END F;E: PROC;END E;



Programmer responseRemove the tasking CALL statement from the PUT FILE(SYSPRINT) statement.

Symbolic Feedback CodeIBM0HS

IBM0573S ONCODE=oncode-value The EVENTvariable, as argument to theCOMPLETION pseudovariable, wasalready used with entry entry-name.

ExplanationAn active event variable was used as theargument to the COMPLETION pseudovariable. Eventvariables used as arguments to the COMPLETIONpseudovariable must be inactive.




Programmer responseEither use a different event variable for theCOMPLETION pseudovariable, or modify the programso that the COMPLETION pseudovariable refers to theevent variable when it is inactive.

Symbolic Feedback CodeIBM0HT

IBM0575S ONCODE=oncode-value An attemptwas made to invoke a Fortranor COBOL program while anotheractive task had invoked a programof the same language.

ExplanationIf a Fortran or COBOL program has been invoked in atask, a program of the same language can not executein any other task until the task used to invoke theFortran or COBOL program terminates. The ONCODEassociated with this message is 3914.


Programmer responseMake sure all Fortran or COBOL programs are invokedin one task or control the invocation sequence in sucha way that the second Fortran or COBOL programinvoked from a task waits until another task whichhas already invoked a program of the same languageterminates.

Symbolic Feedback CodeIBM0HV

IBM0576S ONCODE=oncode-value An attemptto use a CALL statement withthe TASK, EVENT, or PRIORITYoption was found in a non-taskingenvironment.

ExplanationAn attempt was made to create a task when theapplication was not linked with the multitaskinglibrary. The ONCODE associated with this message is3915.


Programmer responseRemove the tasking option from the CALL statement,or if this is a multitasking application, relink it with themultitasking library.

Symbolic Feedback CodeIBM0I0

IBM0577I A PL/I multitasking applicationwas found under CICS, IMS, Db2,CMS, pre-initialized environment,or a nested enclave.

ExplanationPL/I Multitasking Facility is not supported under CICS,IMS, Db2, CMS, pre-initialized environment (bothLanguage Environment-defined and PL/I-defined pre-initialized environment), and a nested enclave.

System actionThe application is terminated with the 4093-12Abend.

Programmer responseDo not use the PL/I Multitasking Facility in the aboveenvironment, or run the multitasking application underz/OS.


IBM0579I ONCODE=oncode-value Thecallable service BPX1SYC forthe installation default of themaximum number of threads wasunsuccessful. The system returncode was return_code; the reasoncode was reason_code.

ExplanationThe callable service BPX1SYC used to query theinstallation default of the maximum number of threadsfailed. The system return code and reason code werereturned.

System actionThe application is abnormally terminated with4093-152 Abend.


Programmer responseLook up the return code and reason code inz/OS UNIX System Services Programming: AssemblerCallable Services Reference, and take the appropriateaction. Consult with your system support personnel ifnecessary.


IBM0580S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because an attemptwas made to OPEN theMSGFILE(SYSPRINT) file after asubtask had been created.

ExplanationWhen the MSGFILE(SYSPRINT) run-time option isspecified, you must ensure that the standardSYSPRINT file is opened in the major PL/I task beforeany subtask is ever created.



Programmer responseEnsure that the above rule has not been violated.One method is to add an OPEN statement for theSYSPRINT file at the start of the major PL/I task beforean subtasks are created.


IBM0581I The POSIX(ON) run-time optionwas in effect for a PL/Imultitasking application.

ExplanationThe POSIX(ON) run-time option is not supported for aPL/I multitasking application.

System actionThe application is terminated with the 4093-52Abend.

Programmer responseSpecify the POSIX(OFF) run-time option for a PL/Imultitasking environment.


IBM0583S ONCODE=oncode-value Thecallable service BPX1MPI(mvspauseinit) was unsuccessful.The return code was return_codeand the reason code wasreason_code.

ExplanationThe callable service BPX1MPI (mvspauseinit) wascalled to initialize a wait for a PL/I WAIT or DISPLAYstatement for a PL/I multi-tasking program. Thisservice failed with the return code and reason codeshown in the message text.





IBM0584S ONCODE=oncode-value Thecallable service BPX1MP(mvspause) was unsuccessful. Thereturn code was return_code andthe reason code was reason_code.

ExplanationThe callable service BPX1MP (mvspause) was called toperform a wait for a PL/I WAIT or DISPLAY statementfor a PL/I multi-tasking program. This service failedwith the return code and reason code shown in themessage text.




Programmer responseLook up the return code and reason code in thez/OS UNIX System Services Programming: AssemblerCallable Services Reference and take the appropriateaction. Consult with your system support personnel ifnecessary.


IBM0585S ONCODE=oncode-value Thecallable service BPX1PTB forcancelling a PL/I subtask wasunsuccessful. The system returncode was return_code, the reasoncode was reason_code.

ExplanationThe callable service BPX1PTB used to cancel aPL/I subtask during abnormal termination failed. Thesystem return code and reason code were returned.





IBM0586S ONCODE=oncode-value Thecallable service BPX1ENV forsupporting PL/I EXCLUSIVE fileswas unsuccessful. The systemreturn code was return_code, thereason code was reason_code.

ExplanationThe callable service BPX1ENV used to support thePL/I EXCLUSIVE files failed. The system return codeand reason code were returned.




Symbolic Feedback CodeIBM0IA

IBM0590S ONCODE=oncode-value Thefetchable procedure with entryentry-name could not be found.

ExplanationThe libraries available when the program was run didnot contain a member with a name or alias matchingthat used in the FETCH statement. The ONCODEassociated with this message is 9250.


Programmer responseEnsure that the load module that is to be fetchedis accessible at run-time, and that it is stored withthe same name or alias as that used in the FETCHstatement.

Symbolic Feedback CodeIBM0IE

IBM0591S ONCODE=oncode-value There wasa permanent I/O error whilefetching procedure with entryentry-name.

ExplanationA permanent I/O error occurred while trying to loadthe module named in the FETCH statement. TheONCODE associated with this message is 9251.



Programmer responseEnsure that the required load module has beenincorporated into the appropriate library with properdata set/file attributes, and then rerun the job. Ifthe problem recurs, inform your installation systemprogrammer, who will take the appropriate action.

Symbolic Feedback CodeIBM0IF

IBM0592S ONCODE=oncode-value FETCH/RELEASE is not supported in CMS.

ExplanationAn attempt was made to FETCH or RELEASE anotherprogram from a PL/I module that was linked with PL/IVersion 2 Release 3 or earlier. The FETCH/RELEASEfacility under CMS is only available with LanguageEnvironment PL/I. The ERROR condition has beenraised. The ONCODE associated with this message is9252.


Programmer responseRemove the FETCH or RELEASE statement from theapplication and use the CALL statement instead. Orrelink the program with Language Environment PL/I.

Symbolic Feedback CodeIBM0IG

IBM0593W ONCODE=oncode-value The CALLPLITEST statement failed becausethe NOTEST compiler option wasin effect.

ExplanationAn attempt was made to execute a CALL PLITESTstatement in a program that was compiled with theNOTEST option. The debugger can not be invokedwhen the NOTEST compiler option is in effect.

System actionProcessing continues with the next sequentialstatement. The debugger is not invoked.

Programmer responseRe-compile the program with the TEST option, orremove the CALL PLITEST statement(s) from theprogram.

Symbolic Feedback CodeIBM0IH

IBM0594S ONCODE=oncode-value UnderCICS, an attempt was made toFETCH a main procedure from aPL/I routine.

ExplanationUnder CICS, using FETCH to dynamically load a PL/Imain procedure from a PL/I routine is not supported.The ONCODE associated with this message is 9254.


Programmer responseRemove the FETCH statement and use the EXEC CICSLINK command to create a nested enclave.

Symbolic Feedback CodeIBM0II

IBM0595S ONCODE=9255 An attempt wasmade to release a load modulecontaining non-PL/I high levellanguage programs.

ExplanationA load module containing non-PL/I high level languageprograms, such as C, COBOL, or FORTRAN, couldnot be released by a PL/I RELEASE statement. Theload module will be released automatically during theenclave termination. A load module containing PL/Iprograms and/or Assembler programs only can bereleased by a PL/I RELEASE statement.



Programmer responseRemove the RELEASE statement from the program asthe load module will be released automatically duringthe enclave termination.


Symbolic Feedback CodeIBM0IJ

IBM0596S ONCODE=9256 The fetchableprocedure could not be released.

ExplanationEither the routine was not previously fetched, or thefetched part containing the routine was no longerin use but could not be released. The ONCODEassociated with this message is 9256.


Programmer responseEnsure the name used in the RELEASE statementis correct, and that the routine has been previouslyfetched. Also, ensure the fetched part containing theroutine to be released is accessible at run-time.

Symbolic Feedback CodeIBM0IK

IBM0597S ONCODE=oncode-value Asubroutine load module using thePLICALLA entry point was fetched.

ExplanationThe PLICALLA entry point can only be used for aload module with a PL/I main routine. The ONCODEassociated with this message is 9257.


Programmer responseEither Specify OPTIONS(MAIN) and recompile or don'tuse the PLICALLA entry point.

Symbolic Feedback CodeIBM0IL

IBM0598S ONCODE=oncode-value The FETCHstatement did not conform toRENT/NORENT guidelines.

ExplanationThe use of FETCH entails certain rules that needto be followed. Specifically, there are guidelines

pertaining to combining RENT and NORENT routines,or PL/I and non-PL/I routines, or both. Refer tothe "Enterprise PL/I for z/OS Programming Guide" atIBM Enterprise PL/I for z/OS library (www.ibm.com/support/docview.wss?uid=swg27036735) for detailspertaining to guidelines related to the abovecombinations.



Programmer responseEnsure that the fetching and fetched routines satisfythe guidelines as documented in the manual.

Symbolic Feedback CodeIBM0IM

IBM0600S ONCODE=oncode-value An E-format specification containedincorrect values in fields W, D, andS.

ExplanationAn edit-directed input/output operation for an E-format item was specified incorrectly. The ONCODEassociated with this message is 3000.


Programmer responseCorrect the E-format item according to the languagerules.

Symbolic Feedback CodeIBM0IO

IBM0601S ONCODE=oncode-value The valueof a W field in an F-formatspecification was too small.

ExplanationAn edit-directed input/output operation for an F-format item was specified with a W-specification thatwas too small to allow room for the decimal-pointwhen the number of fractional digits was specified aszero. The ONCODE associated with this message is3001.


http://www.ibm.com/support/docview.wss?uid=swg27036735



Programmer responseCorrect the F-format item according to the languagerules.

Symbolic Feedback CodeIBM0IP

IBM0602I ONCODE=ONCODE-VALUE Dataconversion from source-ccsid totarget-ccsid was unsuccessful. Thereturn code from the conversionservice was return-code and thereason code was reason-code.

ExplanationFor z/OS, the data conversion for the CCSID pair failedas indicated by the return code and the reason codefrom the Unicode Conversion Service CUNLCNV.

The return code and the reason code values forconversion services are described in z/OS UnicodeServices User's Guide and Reference.

For AIX, the data conversion for the CCSID pair failedas indicated by the return code. The return code valuesare the error numbers described in the errno.hinclude file, which can be found under /usr/includeof your AIX installation. The reason code is PL/I forAIX-specific, and it assists IBM Service in determiningthe source of the message.



Programmer responseFor z/OS, follow the programmer responses indicatedfor specific return and reason codes in z/OS UnicodeServices User's Guide and Reference.

For AIX, correct the error based on the return codemessage text. More information about the returncodes can be found in the AIX manuals.

IBM0603S ONCODE=ONCODE-VALUE Therewas not enough room for theshift-in character after the call toUnicode Conversion Services

ExplanationThe Unicode Conversion Services was called to convertcharacters from a Unicode CCSID to an EBCDIC MBCSCCSID. After the conversion was complete there wasno room left in the target buffer for the closing shift-incharacter.



Programmer responseRetry the conversion after increasing the target bufferto accommodate the closing shift-in character.

IBM0604S ONCODE=oncode-value An invalidassignment was made to apictured character string.

ExplanationAn attempt was made to assign an invalid data itemto a pictured string. A data item which is not acharacter string cannot be assigned to a picturedcharacter string because it does not match thedeclared characteristics of the pictured target variable.The ONCODE associated with this message is 3006.


Programmer responseAlter the characteristics either of the source variableor of the target variable so the data item assignment ispossible.

Symbolic Feedback CodeIBM0IS

IBM0611S ONCODE=oncode-value The F-factor in the PICTUREspecification was outside therange of -128 to 127.

ExplanationThe picture character F specifies a picture scalingfactor for fixed-point decimal numbers. The numberof digits following the V picture character minus theinteger specified with F was required to be between-128 and 127.




Programmer responseCorrect the integer specified with the picture scalingfactor F.

Symbolic Feedback CodeIBM0J3

IBM0612S ONCODE=oncode-value ThePICTURE specification containedan invalid character.

ExplanationThe PICTURE specification can contain only A X 9 forcharacter data and only 9 V Z * , . / B S + - $ CR DBY K E F &lt > for numeric data. The charactersbetween the insertion characters &lt > are notaffected by this rule.



Programmer responseEnsure the PICTURE specification contains valid data.


IBM0613S ONCODE=oncode-value An invalidcharacter(s) appeared in the Fscaling factor.

ExplanationThe picture character F specifies a picture scalingfactor for fixed-point decimal numbers. The format isF(#) where # can be any signed integer between -128and 127 inclusively.



Programmer responseEnsure the value specified for the scaling factor is avalid fixed-point decimal number that is within thesupported range.


IBM0614S ONCODE=oncode-value An invalidcharacter PICTURE specificationwas used.

ExplanationThe PICTURE specification can contain only A X 9 forcharacter data. Other characters are not permitted.



Programmer responseEnsure the PICTURE specification contains valid data.


IBM0615S ONCODE=oncode-value An invalidprecision value was specified.The length was correctedautomatically.

ExplanationThe number of digits for the precision field withina numeric data PICTURE specification must bebetween one and fifteen digits. The invalid precisionspecification is corrected automatically.



Programmer responseEnsure the value specified for the precision is withinthe supported range.



IBM0616S ONCODE=oncode-value Thecharacters T, I or R appearedtoo often in the PICTUREspecification.

ExplanationT, I, R are the overpunch characters in a PICTUREspecification. Only one overpunch character canappear in the specification for a fixed point number. Afloating-point specification can contain two overpunchcharacters, one in the mantissa field and one in theexponent field.



Programmer responseEnsure the above restrictions are followed.


IBM0617S ONCODE=oncode-value Theprecision in the numeric PICTUREspecification was less than 1.

ExplanationThe number of digits for the precision field within anumeric data PICTURE specification must be betweenone and fifteen digits.



Programmer responseCheck the precision and modify the programaccordingly.


IBM0618S ONCODE=oncode-value Theprecision in the fixed decimalPICTURE specification exceededthe limit.

ExplanationThe precision in the fixed decimal PICTUREspecification must not exceed the specified value inthe LIMITS compiler option. The default maximum is15.



Programmer responseUse the LIMITS compiler option to specify a maximumvalue of 29 or 31.

Symbolic Feedback CodeIBM0JA

IBM0619S ONCODE=oncode-value The valuespecified for the precision inthe float decimal PICTUREspecification exceeded the limit.

ExplanationThe precision in the float decimal PICTUREspecification is limited by the hardware to 18 digits.



Programmer responseCheck and correct the precision.

Symbolic Feedback CodeIBM0JB

IBM0620S ONCODE=oncode-value ThePICTURE specification did notcontain picture characters forcharacter or numeric data.

ExplanationThe PICTURE specification must contain picturecharacters for either character or numeric data.




Programmer responseCheck the PICTURE specification string.

Symbolic Feedback CodeIBM0JC

IBM0621S ONCODE=oncode-value Theexponent in the float PICTUREspecification exceeded the 4-digitlimit.

ExplanationThe number of digits in the exponent of the floatdecimal PICTURE specification is limited to 4 digits.



Programmer responseEnsure that the exponent does not exceed 4 digits.

Symbolic Feedback CodeIBM0JD

IBM0622S ONCODE=oncode-value Theexponent in the float PICTUREspecification was missing.

ExplanationThe exponent in the float decimal PICTUREspecification was missing. A value must be entered,even if it is zero.



Programmer responseEnter the missing exponent value.

Symbolic Feedback CodeIBM0JE

IBM0623S ONCODE=oncode-value Theexponent in the PICTUREspecification contained a Vcharacter.

ExplanationThe character V was specified in the PICTUREspecification. The character V specifies an implicitdecimal point and is not permitted in the exponentfield.



Programmer responseRemove the character V from the exponent field.

Symbolic Feedback CodeIBM0JF

IBM0624S ONCODE=oncode-value The floatPICTURE specification containedinvalid characters CR, DB or F.

ExplanationThe float PICTURE specification contained invalidcharacters CR, DB or F. Credit (CR), Debit (DB), andScale Factor (F) are only allowed in the fixed PICTUREspecification.



Programmer responseRemove the invalid characters from the float PICTUREspecification.

Symbolic Feedback CodeIBM0JG

IBM0625S ONCODE=oncode-valueThePICTURE specification exceededthe limit. Excessive characterswere truncated on the right.

ExplanationThe compiler restricts the length of the PICTUREspecification to:

• Fixed Decimal: 254• Float Decimal: 253• Character Data: 511




Programmer responseCorrect the PICTURE specification length.

Symbolic Feedback CodeIBM0JH

IBM0626S ONCODE=oncode-value ThePICTURE specification containedan invalid delimiter.

ExplanationThe floating insertion string is delimited by &lt >characters. The string can contain any character withthe exception of the delimiters themselves. To includethe characters &lt and > in the floating insertionstring, angle brackets must be used in an "escaped"format. &lt&lt denotes character < in the floatinginsertion string. <> denotes character > in the floatinginsertion string. The leading < and ending > charactersare delimiters.

<aaa<<bbb<>ccc> denotes the FIS aaa<bbb>ccc



Programmer responseCorrect the floating insertion string.

Symbolic Feedback CodeIBM0JI

IBM0630S ONCODE=3009 A mixed characterstring ended incorrectly.

ExplanationA mixed character string contained a shift-outcharacter but did not contain a matching shift-incharacter.


Programmer responseEnsure that mixed character strings contain unnestedpairs of shift-out/shift-in characters.

Symbolic Feedback CodeIBM0JM

IBM0631S ONCODE=3010 A mixed characterstring contained an invalidcharacter.

ExplanationOne of the following rules for mixed constants wasbroken:

• SBCS portions of the constant cannot contain a shift-in

• DBCS portions of the constant cannot contain a shift-out (Either byte of a DBCS character cannot contain ashift-out.)

• The second byte of a DBCS character cannot containa shift-in


Programmer responseEnsure the mixed character string contains balanced,unnested pairs of shift-out/shift-in characters.

Symbolic Feedback CodeIBM0JN

IBM0632S ONCODE=3011 An invalid functionstring was specified for the MPSTRbuilt-in function.

ExplanationFor the MPSTR built-in function, a function string isinvalid if it is null, contains only blanks, or containscharacters other than 'V', 'v', 'S', 's', or a blank.


Programmer responseEnsure the function string is valid.


Symbolic Feedback CodeIBM0JO

IBM0633S ONCODE=3012 A retry wasattempted after a graphicconversion error.

ExplanationThe use of the ONSOURCE or ONCHAR pseudovariableto attempt a conversion retry for a graphic (DBCS)conversion error is not allowed.


Programmer responseRemove the retry attempt from your program.

Symbolic Feedback CodeIBM0JP

IBM0634S ONCODE=3013 An invalidgraphic variable assignment wasattempted.

ExplanationA graphic (DBCS) target of length greater than 16,383was encountered. This target could have been anactual target or a temporary target created by theprogram. This condition was raised by the GRAPHICbuilt-in function. The maximum length of a graphic(DBCS) string is 16,383 characters (32,766 bytes).


Programmer responseEnsure that graphic (DBCS) strings are less than themaximum allowed length of 16,383.

Symbolic Feedback CodeIBM0JQ

IBM0635S ONCODE=3014 An invalid use of ashift code occurred.

ExplanationThere are two possible errors:

• The STREAM input record could not be scanned dueto an unmatched or nested shift code.

• A graphic (DBCS) constant in STREAM inputcontained a shift code or used shift codesimproperly.


Programmer responseVerify that shift code pairs are matched and unnested,continuation rules are followed, and graphic (DBCS)constants are in one of the allowable forms.

Symbolic Feedback CodeIBM0JR

IBM0636S ONCODE=3015 An invalid numberof digits was used in a X or GXconstant.

ExplanationX constants must be specified in pairs. GX constantsmust be specified in groups of four.


Programmer responseChange the STREAM input data so that all X constantsare specified in pairs and all GX constants arespecified in groups of four.

Symbolic Feedback CodeIBM0JS

IBM0637S ONCODE=3016 A double-bytecharacter was used incorrectly.

ExplanationA non-EBCDIC double-byte character was usedincorrectly. These characters are only valid in DBCSnames, graphic (DBCS) constants, and mixed characterconstants.



Programmer responseVerify that a bit, character or hexadecimal constantdoes not contain a non-EBCDIC double-byte character,or that such a character is not present outside aconstant unless it is part of a name for a GET DATAstatement.

Symbolic Feedback CodeIBM0JT

IBM0638S ONCODE=oncode-value A STREAMoutput record could not be writtencorrectly.

ExplanationA record could not be written out because therewas not enough room for a valid DBCS continuationsequence. As a consequence, the record cannotbe read correctly as STREAM input. The ONCODEassociated with this message is 3017.


Programmer responseDefine the STREAM I/O data set to contain V- or U-type record formats.

Symbolic Feedback CodeIBM0JU

IBM0640S ONCODE=oncode-value InvalidUTF-8 data was detected.

ExplanationAn attempt was made to scan a UTF-8 string, but abyte was found that is not part of any UTF-8 character.The first byte in a UTF-8 character must be either lessthan '80'x or else greater than 'c1'x but less than 'f5'x.



Programmer responseCorrect the invalid data.

Symbolic Feedback CodeIBM0K0

IBM0641S ONCODE=oncode-value An invalidbyte 2 in a UTF-8 characterdetected.

ExplanationAn attempt was made to scan a UTF-8 string, but thesecond byte in a UTF-8 character was invalid. In UTF-8characters that span 2 bytes, the second byte mustnot be less then '80'x nor greater than 'bf'x. In UTF-8characters that span 3 bytes or 4 bytes, the secondbyte range is determined by the first byte. See z/OS XLC/C++ Language Reference for more details.





IBM0642S ONCODE=oncode-value An invalidbyte 3 in a UTF-8 character wasdetected.

ExplanationAn attempt was made to scan a UTF-8 string, but thethird byte in a UTF-8 character was invalid. In UTF-8characters that span 3 bytes or 4 bytes, the third bytemust not be less then '80'x nor greater than 'bf'x.





IBM0643S ONCODE=oncode-value An invalidbyte 4 in a UTF-8 character wasdetected.


ExplanationAn attempt was made to scan a UTF-8 string, but thefourth byte in a UTF-8 character was invalid. In UTF-8characters that span 4 bytes, the fourth byte must notbe less then '80'x nor greater than 'bf'x.





IBM0644S ONCODE=oncode-value Anincomplete UTF-8 character wasdetected.

ExplanationAn attempt was made to scan a UTF-8 string, but thestring ended with an incomplete UTF-8 character.





IBM0645S ONCODE=oncode-value InvalidUTF-16 data was detected.

ExplanationAn attempt was made to scan a UTF-16 string, buta widechar was found that indicated it was part ofa surrogate pair. The second widechar in that pairwas invalid since it did not have a value of at least'dc00'wx.





IBM0646S ONCODE=oncode-value Anincomplete UTF-16 character wasdetected.

ExplanationAn attempt was made to scan a UTF-16 string, but thestring ended with an incomplete UTF-16 character.





IBM0647S ONCODE=oncode-value USUBSTRreference is invalid.

ExplanationIn a USUBSTR(x,i,j) reference, i must be positive,j must be nonnegative and the sum of i + j - 1must be less than or equal to ULENGTH(x).





IBM0650S ONCODE=3799 The source was notmodified in the CONVERSION ON-unit. Retry was not attempted.


ExplanationThe CONVERSION condition was raised by thepresence of an invalid character in the string to beconverted. The character was not corrected in an ON-unit using the ONCHAR or ONSOURCE pseudovariable.


Programmer responseUse either the ONCHAR or the ONSOURCEpseudovariable in the CONVERSION ON-unit to assigna valid character to replace the invalid character in thesource string.

Symbolic Feedback CodeIBM0KA

IBM0660S ONCODE=oncode-value The valueof Y in GETSYSWORD(Y) is invalid.

ExplanationThe argument passed to the GETSYSWORD built-infunction is incorrect. Refer to the Enterprise PL/I forz/OS Language Reference for details of the argument.



Programmer responseModify your program to use the built-in functioncorrectly.

Symbolic Feedback CodeIBM0KK

IBM0670S ONCODE=oncode-value X was lessthan 0 in SQRT(X).

ExplanationThe built-in function SQRT was invoked with anargument that is less than zero. ONCODEs associatedwith this message are:

• 1500 Short floating-point argument• 1501 Long floating-point argument• 1502 Extended floating-point argument


Programmer responseModify the program so that the argument of the SQRTbuilt-in function is never less than zero.

Symbolic Feedback CodeIBM0KU

IBM0671S ONCODE=oncode-value X was lessthan or equal to 0 in LOG(X),LOG2(X) or LOG10(X).

ExplanationOne of the built-in functions LOG, LOG2, or LOG10 wasinvoked with an argument less than or equal to zero.The invocation may have been direct or as part of theevaluation of an exponentiation calculation. ONCODEsassociated with this message are:

• 1503 Extended floating-point argument• 1504 Short floating-point argument• 1505 Long floating-point argument


Programmer responseIf the invocation is direct, modify the program sothat the argument of the LOG, LOG2, or LOG10 built-in function is greater than zero. If the invocation ispart of an exponentiation calculation, ensure that theargument is greater than zero.

Symbolic Feedback CodeIBM0KV

IBM0672S ONCODE=oncode-value ABS(X)was too large in SIN(X), COS(X),SIND(X), COSD(X), TAN(X) orTAND(X).

ExplanationThe error occurred during one of the following:

• The evaluation of SIN, SIND, COS, COSD, TAN, orTAND when invoked implicitly

• The evaluation of TAN, when invoked during theevaluation of TAN or TANH with a complex argument


• The evaluation of SIN or COS, when invoked duringthe evaluation of EXP, SIN, SINH, COS, COSH, TAN,or TANH with a complex argument

• The evaluation of a general exponentiation functionwith complex arguments

The argument passed to TAN, TAND, SIN, SIND, COS,or COSD exceeded the limit specified below.

Floating-Point Precision Limit

Binary p = 21

Decimal p = 6

x<(2**18)*K

where K = pi for x in radians(SIN, COS, or TAN)

Binary 21 < p = 53

Decimal 6 < p = 16

x<(2**50)*K

where K = 180 for x in degrees(SIND, COSD, TAND)

Binary 53 < p = 109

Decimal 6 < p = 33

x<(2**100)*K/pi


• 1506 Short floating-point argument involving SIN,COS, SIND or COSD

• 1507 Long floating-point argument involving SIN,COS, SIND or COSD

• 1508 Short floating-point argument involving TAN orTAND

• 1509 Long floating-point argument involving TAN orTAND

• 1517 Extended floating-point argument involvingSIN, COS, SIND or COSD

• 1522 Extended floating-point argument involvingTAN or TAND


Programmer responseEnsure that X does not violate the limits as describedabove. If X is an expression, simplify X for easierproblem diagnosis.

Symbolic Feedback CodeIBM0L0

IBM0674S ONCODE=oncode-value Both Xand Y were 0 in ATAN(Y,X) orATAND(Y,X).

ExplanationTwo arguments, both of value zero, were given forthe ATAN or ATAND built-in function. ATAN or ATANDwas invoked either directly with a real argument orindirectly in the evaluation of the LOG built-in functionwith a complex argument. ONCODEs associated withthis message are:

• 1510 Short floating-point arguments• 1511 Long floating-point arguments• 1521 Extended floating-point arguments


Programmer responseChange the arguments of ATAN or ATAND to nonzerovalues.


IBM0675S ONCODE=oncode-value ABS(X)was greater than or equal to 1 inATANH(X).

ExplanationThe ATANH built-in function had a floating-pointargument with an absolute value that equaled orexceeded 1. ONCODEs associated with this messageare:



Programmer responseModify the ATANH built-in function so that theabsolute value of a floating-point assignment does notequal or exceed 1.


IBM0676S ONCODE=oncode-value ABS(X)was greater than 1 in ASIN(X) orACOS(X).


ExplanationThe absolute value of the floating-point argumentof the ASIN or ACOS built-in function exceeded 1.ONCODEs associated with this message are:



Programmer responseModify the program so that the ASIN or ACOS built-in function is never invoked with a floating-pointargument whose absolute value exceeds 1.


IBM0682S ONCODE=oncode-value X inEXPONENT(X) was invalid.


• For X**Y where X and Y are integers, X was equal tozero and Y was less than or equal to zero.

• For X**Y where X is a real value and Y is an integer,X was equal to zero and Y was less than or equal tozero.

• For X**Y where X and Y are integers, X was not equalto plus or minus one and Y was less than zero.

• For X**Y where X and Y are complex values, X was(0,0i) and Y was less than or equal to zero.

• For X**Y where X and Y are complex values, Xexceeded the limit K, where K=2**63 for complexshort and long arguments, and K=2**55 for complexextended arguments.

• For X**Y where X and Y are complex values, X wasequal to (0,0i).

• For X**Y where X and Y are real values, X was equalto zero and Y was not an integer-float greater thanzero.

• For X**Y where X and Y are real values, X was lessthan zero and Y was not an integer-float.


• For integer base and integer exponent1673

X equal to zero and Y less than or equal to zero

1674X not equal to plus or minus one and less thanzero

• For real short floating-point base with integerexponent1550

X equal to zero and Y less than or equal to zero• For real long floating-point base with integer

exponent1551

X equal to zero and Y less than or equal to zero• For real extended floating-point base with integer

exponent1560

X equal to zero and Y less than or equal to zero• For complex short floating-point base with integer

exponent1554

X equal to (0,0i) and Y less than or equal to zero• For complex long floating-point base with integer

exponent1555

X equal to (0,0i) and Y less than or equal to zero• For complex extended floating-point base with

integer exponent1562

X equal to (0,0i) and Y less than or equal to zero• For real short floating-point base with real short

floating-point exponent1552

X equal to zero and Y not a positive integer-float,or X less than zero and Y not an integer-float

1729X equal to (0,0i) and Y less than or equal to zero

• For real long floating-point base with real longfloating-point exponent1553


1730X equal to (0,0i) and Y less than or equal to zero

• For real extended floating-point base with realextended floating-point exponent1561


• For complex short floating-point base with complexshort floating-point exponent


1556Argument equal to (0,0i)

1754Argument exceeded limit

• For complex long floating-point base with complexlong floating-point exponent1557

Argument equal to (0,0i)1755

Argument exceeded limit• For complex extended floating-point base with

complex extended floating-point exponent1563

Argument equal to (0,0i)1756

Argument exceeded limit


Programmer responseEnsure X is a valid floating-point number.

Symbolic Feedback CodeIBM0LA

IBM0683S ONCODE=oncode-value X or Y inATAN(X,Y) or ATAND(X,Y) wasinvalid.


• X and Y were invalid.



Both arguments were invalid• For real long floating-point arguments:

1511Both arguments were invalid


Both arguments were invalid


Programmer responseEnsure X and Y are both real values and that Y is notequal to zero.

Symbolic Feedback CodeIBM0LB

IBM0700S ONCODE=oncode-value An attemptto assign data to an unallocatedCONTROLLED variable occurredduring GET DATA for file file-name.

ExplanationA CONTROLLED variable in the stream was accessedby a GET FILE DATA statement, but there was nocurrent allocation for the variable.

DCL X CONTROLLED FIXED BIN;GET DATA(X);

(Input stream containsX=5,.....)



Programmer responseEither remove the data item from the input stream orinsert an ALLOCATE statement for the variable beforethe GET FILE DATA statement.

Symbolic Feedback CodeIBM0LS

IBM0701S ONCODE=oncode-value An attemptto assign data to an unallocatedCONTROLLED variable occurred ona GET DATA statement.

ExplanationA CONTROLLED variable in the stream was accessedby a GET FILE DATA statement, but there was nocurrent allocation for the variable.

DCL STR CHAR(4) INIT('X=5'),X CONTROLLED FIXED BIN;GET STRING(STR) DATA(X);




Programmer responseEither remove the data item from the string or insertan ALLOCATE statement for the variable before theGET STRING DATA statement.

Symbolic Feedback CodeIBM0LT

IBM0702S ONCODE=oncode-value An attemptto to output an unallocatedCONTROLLED variable occurred ona PUT DATA statement.

ExplanationA CONTROLLED variable was being output to a file by aPUT FILE DATA statement, but there was no currentallocation for the variable. The ONCODE associatedwith this message is 4002.


Programmer responseInsert an ALLOCATE statement for the variable beforethe PUT FILE DATA statement.

Symbolic Feedback CodeIBM0LU

IBM0703S ONCODE=oncode-valueAn attemptto assign from an unallocatedCONTROLLED variable occurred ona PUT DATA statement with theSTRING option.

ExplanationA CONTROLLED variable was being accessed by a PUTSTRING DATA statement, but there was no currentallocation for the variable. The ONCODE associatedwith this message is 4003.


Programmer responseEnsure the CONTROLLED variable is allocated andinitialized before the PUT DATA statement.

Symbolic Feedback CodeIBM0LV

IBM0710S ONCODE=oncode-value Too manydigits specified in JSON floating-point number.

ExplanationFloating-point numbers in JSON text are limited to34 digits excluding those in the exponent field. TheONCODE associated with this message is 5050.


Programmer responseEnsure the floating-point numbers in the JSON text donot exceed 34 digits.

Symbolic Feedback CodeIBM0M6

IBM0711S ONCODE=oncode-value Too manydigits specified in JSON fixed-point number.

ExplanationFixed-point numbers in JSON text are limited to 31digits. The ONCODE associated with this message is5051.


Programmer responseEnsure the fixed-point numbers in the JSON text donot exceed 31 digits.


IBM0712S ONCODE=oncode-value Invalidvalue type in JSON text.

ExplanationWhen performing an assignment while parsing JSONtext, the source value must start with one of thecharacters forming the start of a JSON string, a JSONnumber, or one of the JSON keywords null, true, or


false. The ONCODE associated with this message is5052.


Programmer responseEnsure the JSON text starts with a valid value type.


IBM0713S ONCODE=oncode-value Conversionfrom UTF-8 to character failed.

ExplanationWhen performing an assignment while parsing JSONtext, if the source value is a JSON string and thetarget is not WIDECHAR, then every UTF-8 characterin the source string must have a match in the targetcodepage (as defined by the CODEPAGE when it wascompiled). The ONCODE associated with this messageis 5053.


Programmer responseEnsure the JSON text being assigned to a non-WIDECHAR target contains UTF-8 characters that havea match in the target codepage.


IBM0714S ONCODE=oncode-value Source inJSON assignment to BIT is invalid.

ExplanationWhen performing an assignment while parsing JSONtext, if the source value is a JSON string and the targetis BIT, the source string must consist entirely of 0'sand 1's. The ONCODE associated with this message is5054.


Programmer responseEnsure the JSON text being assigned to a BIT targetconsists entirely of 0's and 1's.

Symbolic Feedback CodeIBM0MA

IBM0715S ONCODE=oncode-value Conversionfrom UTF-8 to UTF-16 failed.

ExplanationWhen performing an assignment while parsing JSONtext, if the source value is a JSON string and thetarget is WIDECHAR, the source string must consist ofno more than 16383 UTF-8 characters. The ONCODEassociated with this message is 5055.


Programmer responseEnsure the JSON text being assigned to a WIDECHARtarget does not exceed 16383 UTF-8 characters.

Symbolic Feedback CodeIBM0MB

IBM0716S ONCODE=oncode-value String inJSON text is too long.

ExplanationThe number of bytes in a JSON string must be nogreater than 3*32767. The ONCODE associated withthis message is 5056.


Programmer responseEnsure the length of the JSON string does not exceed3*32767.

Symbolic Feedback CodeIBM0MC

IBM0717S ONCODE=oncode-value Charactersafter \u are not valid hexadecimaldigits.


ExplanationIn JSON text, the 4 characters after \u must be validhexadecimal digits. The ONCODE associated with thismessage is 5057.


Programmer responseEnsure the 4 characters after \u are valid hexadecimaldigits.

Symbolic Feedback CodeIBM0MD

IBM0718S ONCODE=oncode-valueHexadecimal characters specify aninvalid UTF surrogate pair.

ExplanationIn a JSON text, hexadecimal characters must specifyvalid UTF-8 data. This means that if \uxxxx specifiesa value between d800 and dbff, then it must beimmediately followed by \uyyyy where yyyy specifiesa value between dc00 and dfff. Conversely, if \uxxxxspecifies a value between dc00 and dfff, it musthave been immdiately preceded by \uyyyy where yyyyspecifies a value between d800 and dbff. The ONCODEassociated with this message is 5058.


Programmer responseEnsure the hexadecimal characters in the JSON textspecify valid UTF-8 data.

Symbolic Feedback CodeIBM0ME

IBM0719S ONCODE=oncode-value Invalidescape character in JSON text.

ExplanationIn JSON text, the only valid characters after theescape symbol (\) are the characters double quotationmark ("), backslash (\), forward slash (/), u, b, f, n, r,and t, and the first 4 of these are valid only insidestrings. The ONCODE associated with this message is5059.


Programmer responseEnsure the JSON text contains valid characters afterthe escape symbol.

Symbolic Feedback CodeIBM0MF

IBM0720S ONCODE=oncode-value Only validvalue starting with t in JSON textis true.

ExplanationIn JSON text, the only time a value starting with theletter t can appear is when it is the start of the wordtrue. Any other string starting with the letter t must beenclosed in quotes. The ONCODE associated with thismessage is 5060.


Programmer responseEnsure the t in the JSON text is the start of the wordtrue. Otherwise, enclose the string in quotes.

Symbolic Feedback CodeIBM0MG

IBM0721S ONCODE=oncode-value Only validvalue starting with f in JSON textis false.

ExplanationIn JSON text, the only time a value starting with theletter f can appear is when it is the start of the wordfalse. Any other string starting with the letter f must beenclosed in quotes. The ONCODE associated with thismessage is 5061.


Programmer responseEnsure the f in the JSON text is the start of the wordfalse. Otherwise, enclose the string in quotes.


Symbolic Feedback CodeIBM0MH

IBM0722S ONCODE=oncode-value Only validvalue starting with n in JSON textis null.

ExplanationIn JSON text, the only time a value starting with theletter n can appear is when it is the start of the wordnull. Any other string starting with the letter n must beenclosed in quotes.



Programmer responseEnsure the n in the JSON text is the start of the wordnull.

Otherwise, enclose the string in quotation marks.

Symbolic Feedback CodeIBM0MI

IBM0723S ONCODE=oncode-value JSON textends prematurely.

ExplanationAll JSON text must have enough characters to becomplete. This means, for example, if the text has adouble quotation mark (") to open a string, then itmust have a closing double quotation mark (") or, forexample, that if the text contains 3.14E, then it musthave at least one more character (that specifies theexponent).



Programmer responseEnsure the JSON text is complete and that there arematching delimiters if these are used.

Symbolic Feedback CodeIBM0MJ

IBM0724S ONCODE=oncode-value Numberdoes not conform to the rules ofJSON syntax.

ExplanationAny number specified in JSON text must conform tothe rules of JSON syntax. This means, for example,that it cannot start with a plus-sign and that if its firstdigit is a 0, then any other digits must come after adecimal point.



Programmer responseEnsure the number specified in the JSON textconforms to the JSON syntax rules.

Symbolic Feedback CodeIBM0MK

IBM0725S ONCODE=oncode-value Name inJSON source does not match thatin the target.

ExplanationWhile parsing JSON text for an assignment, the namein any name-value pair must match the name in thecorresponding target reference.



Programmer responseEnsure the names specified in the JSON source andtarget match.

Symbolic Feedback CodeIBM0ML

IBM0726S ONCODE=oncode-value The JSONvalues true and false may beassigned only to NONVARYINGBIT.


ExplanationWhen performing an assignment while parsing JSONtext, if the source value is the keyword true or false,then the target must have the attributes NONVARYINGBIT.



Programmer responseEnsure the target for the JSON values true and false isa nonvarying bit string.

Symbolic Feedback CodeIBM0MM

IBM0727S ONCODE=oncode-value JSON textcontains invalid UTF-8 characters.

ExplanationAll JSON text must consist of valid UTF-8 characters.



Programmer responseEnsure the JSON text contains valid UTF-8 characters.

Symbolic Feedback CodeIBM0MN

IBM0728S ONCODE=oncode-value Objectsand arrays in the JSON text arenested too deeply.

ExplanationObjects and arrays must be nested no more than 100-fold.



Programmer responseEnsure the nesting level for objects and arrays in theJSON text does not exceed 100.

Symbolic Feedback CodeIBM0MO

IBM0729S ONCODE=oncode-value Nextsignificant character in the JSONtext should be an opening bracket,hex 5B (in UTF-8).

ExplanationWhile parsing JSON text to assign to an array, thecorresponding JSON text must start with an openingbracket, [.



Programmer responseEnsure the JSON text that is to be assigned to an arraystarts with an opening bracket, [.

Symbolic Feedback CodeIBM0MP

IBM0730S ONCODE=oncode-value Nextsignificant character in the JSONtext should be a closing bracket,hex 5D (in UTF-8).

ExplanationWhile parsing JSON text to assign to an array, thecorresponding JSON text must end with a closingbracket, ].



Programmer responseEnsure the JSON text that is to be assigned to an arrayhas a closing bracket, ].

Symbolic Feedback CodeIBM0MQ


IBM0731S ONCODE=oncode-value Nextsignificant character in the JSONtext should be an opening brace,hex 7B (in UTF-8).

ExplanationWhile parsing JSON text to assign to a structure, thecorresponding JSON text must start with an openingbrace, {.



Programmer responseEnsure the JSON text that is to be assigned to astructure has an opening brace, {.

Symbolic Feedback CodeIBM0MR

IBM0732S ONCODE=oncode-value Nextsignificant character in the JSONtext should be a closing brace, hex7D (in UTF-8).

ExplanationWhile parsing JSON text to assign to a structure, thecorresponding JSON text must end with a closingbrace, }.



Programmer responseEnsure the JSON text that is to be assigned to astructure has a closing brace, }.

Symbolic Feedback CodeIBM0MS

IBM0733S ONCODE=oncode-value Nextsignificant character in the JSONtext should be a comma (,).

ExplanationWhile parsing JSON text to assign to a subsequentelement of a structure or array, the correspondingJSON text must have a comma (,).



Programmer responseEnsure the JSON text that is to be assigned toa subsequent element of a structure or array isdelimited by a comma (,).

Symbolic Feedback CodeIBM0MT

IBM0734S ONCODE=oncode-value Nextsignificant character in the JSONtext should be a double quotationmark (").

ExplanationWhile parsing JSON text for an object member, thestart of the member must be a name enclosed indouble quotation marks (").



Programmer responseEnsure the JSON text for the name of an objectmember is enclosed in double quotation marks (").

Symbolic Feedback CodeIBM0MU

IBM0735S ONCODE=oncode-value Nextsignificant character in the JSONtext should be a colon (:).

ExplanationAfter a name in a name-value pair in an object, thenext significant character must be a colon (:).




Programmer responseEnsure the name in a name-value pair in an object isfollowed by a colon (:).

Symbolic Feedback CodeIBM0MV

IBM0736S ONCODE=oncode-value Nextsignificant character in the JSONtext should be the start of a JSONvalue.

ExplanationA JSON value must start with an opening brace, {,opening bracket, [, or the start of a JSON string, aJSON number, or one of the JSON keywords null,true, or false.



Programmer responseEnsure the JSON text starts with a valid JSON value.

Symbolic Feedback CodeIBM0N0

IBM0737S ONCODE=oncode-value Nextsignificant character in the JSONtext should be a closing bracket,hex 5D (in UTF-8), or the start of aJSON value.

ExplanationAfter an opening bracket, [, to open an array, the nextsignificant character must be either the start of a JSONvalue or a closing bracket, ], to close the array.



Programmer responseEnsure the next significant character following anopening bracket, [, to an array is either the start of aJSON value or a closing bracket, ].


IBM0738S ONCODE=oncode-value Nextsignificant character in the JSONtext should be a double quotationmark (") or a closing brace, hex 7D(in UTF-8).

ExplanationAfter an opening brace, {, to open an object, thenext significant character must be either a doublequotation mark (") to start a name-value pair or aclosing brace, }, to close the object.



Programmer responseEnsure the next significant character following anopening brace, {, is either a starting double quotationmark (") for a name-value pair or a closing brace, }.


IBM0739S ONCODE=oncode-value Nextsignificant character in the JSONtext should be a comma (,) or aclosing bracket, hex 5D (in UTF-8).

ExplanationAfter an array element, the next significant charactermust be either a comma (,) to continue the array or aclosing bracket, ], to close it.




Programmer responseEnsure the next significant character following an arrayelement is either a continuing comma (,) for the arrayor a closing bracket, ].


IBM0740S ONCODE=oncode-value Nextsignificant character in the JSONtext should be a comma (,) or aclosing brace, hex 7D (in UTF-8).

ExplanationAfter an object member, the next significant charactermust be either a comma (,) to continue the object or aclosing brace, }, to close it.



Programmer responseEnsure the next significant character following anobject member is either a continuing comma (,) for theobject or a closing brace, }.


IBM0750S ONCODE=oncode-value A GOTO toan invalid block was attempted.

ExplanationA GOTO statement that transfers control to a labelvariable was invalid. The possible causes are:

• The generation of the block that was active whenthe label variable was assigned was no longer activewhen the GOTO statement was run.

• The label variable was uninitialized.• The element of the label array, to which control is to

be transferred, does not exist in the program.• An attempt has been made to transfer control to a

block that is not within the scope of this task.

DCL L LABEL;BEGIN;A: L = A;END;GOTO L;



Programmer responseModify the program so that the GOTO statementtransfers control to a label in an active block.

Symbolic Feedback CodeIBM0NE

IBM0751S ONCODE=oncode-value A GOTOwas attempted to an element ofa label constant array, but thesubscripts for the element werenot those of any label in that array.

ExplanationThe subscripts of an element in a GOTO statementmust match the label in the specified array. This erroroccurs in the following code if n is 1, 3, 5 or 7:

dcl n fixedbin;

.

.

.

goto x(n);

.

.

.

x(0):

.

.

.

x(2):

.

.

.

x(4):

.

.

.

x(6):

.

.

.

x(8):

Note: This error will not occur if n is less than thelower bound for x or greater than the upper bound.




Programmer responseCorrect your program.

Symbolic Feedback CodeIBM0NF

IBM0752S ONCODE=oncode-value A RETURNwithout an expression wasattempted from a procedure thathad been entered at an ENTRYthat specified the RETURNSattribute.

ExplanationA procedure can contain ENTRYs some of which havethe RETURNS attribute and some of which do not, butif it is entered at an ENTRY that has the RETURNSattribute, it must be exited with a RETURN statementthat specifies a return value.




Symbolic Feedback CodeIBM0NG

IBM0753S ONCODE=oncode-value A RETURNwithout an expression wasattempted from a procedure thathad been entered at an ENTRYthat does not specify the RETURNSattribute.

ExplanationA procedure can contain ENTRYs some of which havethe RETURNS attribute and some of which do not, butif it is entered at an ENTRY that has the RETURNSattribute, it must be exited with a RETURN statementthat does not specify a return value.




Symbolic Feedback CodeIBM0NH

IBM0780S ONCODE=oncode-value No WHENclauses were satisfied and noOTHERWISE clause was available.

ExplanationNo WHEN clauses of a SELECT statement wereselected and no OTHERWISE clause was present. TheONCODE associated with this message is 3.


Programmer responseAdd an OTHERWISE clause to the SELECT group.

Symbolic Feedback CodeIBM0OC

IBM0802S ONCODE=oncode-value TheGET/PUT STRING exceeded thesource string size.

ExplanationFor input, a GET statement attempted to access datathat exceeded the length of the source string. Foroutput, a PUT statement attempted to assign data thatexceeded the target string. The ONCODE associatedwith this message is 1002.


Programmer responseFor input, either extend the length attribute of thesource string, or correct the data so that the lengthdoes not exceed the declared length of the sourcestring. For output, either extend the length attributeof the target string, or correct the data so that thelength does not exceed the declared length of thetarget string.


Symbolic Feedback CodeIBM0P2

IBM0803S ONCODE=oncode-value A priorcondition on file file-nameprevented further output.

ExplanationA PL/I WRITE, LOCATE, or PUT statement was issuedfor a file to which a previous attempt to transmit arecord caused the TRANSMIT condition to be raisedimmediately. If the EVENT option was specified to bestacked until the event was waited on, the data setwas not a unit-record device and no further processingof the file was possible. The ONCODE associated withthis message is 1003.


Programmer responseCorrect the error that caused the TRANSMIT conditionto be raised and rerun the program.


IBM0804S ONCODE=oncode-value The PRINToption/format item was used withnon-PRINT file file-name.

ExplanationAn attempt was made to use one of the options PAGEor LINE for a file that was not a print file. The ONCODEassociated with this message is 1004.


Programmer responseEither remove the PRINT option/format item from thenon-print file, or specify the PRINT option for the printfile.


IBM0805S ONCODE=oncode-value A DISPLAYwith REPLY option had a zero-length string.

ExplanationThe current length of the character string to bedisplayed, or the maximum length of the characterstring to which the reply was assigned, was zero. TheONCODE associated with this message is 1005.


Programmer responseChange length of the character string to be displayed,or to which the reply is to be assigned, to greater thanzero.


IBM0807S ONCODE=oncode-value TheREWRITE or DELETE on filefile-name occurred without apreceding READ SET or READINTO statement.

ExplanationA REWRITE or DELETE statement without the KEYoption was run. The last input/output operation on thefile was not a READ statement with the SET or INTOoption or was a READ statement with the IGNOREoption. The ONCODE associated with this message is1007.


Programmer responseModify the program so that the REWRITE or DELETEstatement is either preceded by a READ statement or,in the case of a REWRITE statement, replaced by aWRITE statement, according to the requirements ofthe program. A preceding READ statement with theIGNORE option will also cause the message to beissued.


IBM0808S ONCODE=oncode-value An invalidelement was present in the stringfor a GET STRING DATA statement.


ExplanationThe identifier in the string named in the STRING optionof a GET STRING DATA statement did not matchthe identifier in the data specification. Note that theDATAFIELD built-in function does not return a value inthis case. The ONCODE associated with this messageis 1008.


Programmer responseModify the program so that the string contains theidentifier in the data specification.


IBM0809S ONCODE=oncode-value An invalidfile operation was attempted onfile file-name.

ExplanationAn attempt was made to perform an invalid operationon a file. For example, it is not possible to run aREWRITE statement on a STREAM file, read an outputfile, or write an input file. Refer to the table below for alist of operations and conflicting file organizations.

Table 6. Operations and Conflicting File Organizations

Statement/Option File Organization

Any record I/Ostatement

STREAM

Any stream I/Ostatement

RECORD

READ OUTPUT

READ SET UNBUFFERED

READ EVENT UNBUFFERED

READ KEY REGIONAL SEQUENTIAL orCONSECUTIVE

READ IGNORE DIRECT

READ NOLOCK SEQUENTIAL or INPUT

WRITE INPUT SEQUENTIAL UPDATE,INDEXED DIRECT NOWRITE,REGIONAL (not KEYED)

WRITE EVENT BUFFERED

REWRITE INPUT or OUTPUT

Table 6. Operations and Conflicting File Organizations(continued)

Statement/Option File Organization

REWRITE (withoutFROM)

UNBUFFERED or DIRECT

REWRITE KEY SEQUENTIAL

REWRITE EVENT BUFFERED

LOCATE INPUT or UPDATE,UNBUFFERED, DIRECT

LOCATE KEYFROM INDEXED or REGIONAL(without KEYED)

DELETE INPUT or OUTPUT,CONSECUTIVE, REGIONALSEQUENTIAL, RKP=0 (blockedrecords), OPTCD=L notspecified

DELETE KEY SEQUENTIAL

UNLOCK INPUT or OUTPUT,SEQUENTIAL

GET OUTPUT

PUT INPUT



Programmer responseEnsure the file declaration and the input/outputstatements for the named file are compatible.


IBM0810S ONCODE=oncode-value A built-in function or pseudovariablereferenced an unopened fileor referenced a file with acontradicting attribute.

ExplanationAn I/O built-in function or pseudovariable referenceda file that was not opened or referenced a filewith an attribute that contradicted the function orpseudovariable. The functions/pseudovariables are :

• PAGENO - file not open or does not have the PRINTattribute

• SAMEKEY - file does not have the RECORD attribute


• ENDFILE - file not open• FILEREAD - file not open or is not a TYPE(U) file• FILEWRITE - file not open or is not a TYPE(U) file• FILESEEK - file not open or is not a TYPE(U) file• FILETELL - file not open or is not a TYPE(U) file• FILEDDTEST - file not open or:

– AMTHD - file not a native file– BKWD - file not a record file– DESCENDKEY - file not a record file– GENKEY - file not a record file– PRINT - file not a stream output file

• FILEDDINT - file not open or:

– BUFSIZE - file not a native file– DELAY - file not a DDM, BTRIEVE or ISAM file– RETRY - file not a DDM, BTRIEVE or ISAM file– FILESIZE - file not a native file– KEYLEN - file not an indexed or a relative keyed

file– KEYLOC - file not an indexed or a relative keyed

file• FILEDDWORD - file not open or:

– TYPEF - file not a native file



Programmer responseCorrect your program to use the built-in function orpseudovariable correctly.

Symbolic Feedback CodeIBM0PA

IBM0811S ONCODE=oncode-value An I/Oerror occurred. Subcode1= sc1Subcode2= sc2

ExplanationThe data management routines detected an errorduring an input/output operation, which PL/I did notrecognize. Subcode1 and Subcode2 provide VSAMdiagnostic information; otherwise, they contain zeros.See the VSAM Macro Instruction manual for adescription of the errors. Subcode1 indicates the I/Ofunction involved:

• 0 - I/O function not identified• 1 - GET• 2 - PUT• 3 - CHECK• 4 - POINT• 5 - ENDREQ• 6 - ERASE• 64 - OPEN• 130 - GENCB of ACB• 131 - GENCB of RPL• 138 - SHOWCB of ACB• 142 - TESTCB of ACB• 146 - SHOWCB of block lengths

Subcode2 consists of 8 hexadecimal digits (xxxxyyyy).The meaning of Subcode2 varies depending on thePL/I product used.

For MVS and VM, the value of subcode1 determinesthe type of VSAM return code information provided.

• Subcode1 0: VSAM return code information is notprovided.

• Subcode1 1-63: VSAM Request Parameter ListFeedback Word (RPLFDBWD) = xxxxyyyy.

• Subcode1 64: Open register 15 = xxxx. Open reasoncode = yyyy.

• Subcode1 128-192: Register 15 = xxxx. Register 0 =yyyy.

For Enterprise PL/I for z/OS, Subcode2 gives thefollowing information:

• Register 15 = xxxx. Reason code = yyyy.

Note that PL/I terminology translates to VSAM termsas follows:

• PL/I UPDATE OPEN is equivalent to VSAM IN andOUT OPEN.

• PL/I OUTPUT OPEN is equivalent to VSAM OUTOPEN, but only inserts or additions are allowed.

• PL/I READ results in VSAM POINT to key, if specified,followed by VSAM GET.

• PL/I WRITE or LOCATE results in VSAM PUT NUP. ForPL/I LOCATE, the associated VSAM PUT NUP occurson the next PL/I I/O request.

• PL/I REWRITE results in implied read, if needed,followed by VSAM PUT UPD.

• PL/I DELETE results in implied read, if needed,followed by VSAM ERASE.

• PL/I WAIT EVENT I/O results in VSAM CHECK.





Symbolic Feedback CodeIBM0PB

IBM0812S ONCODE=oncode-value A READSET or READ INTO statement didnot precede a REWRITE request.

ExplanationA REWRITE statement with the INTO or SET option ranwithout a preceding READ statement. The ONCODEassociated with this message is 1012.


Programmer responseModify the program so that the REWRITE statement iseither preceded by a READ statement or replaced by aWRITE statement.

Symbolic Feedback CodeIBM0PC

IBM0813S ONCODE=oncode-value The lastREAD statement before thelast REWRITE or DELETE wasincomplete.

ExplanationAn attempt was made to run a REWRITE or DELETEstatement before a preceding READ statement (withthe EVENT option) for a file that had completed. TheONCODE associated with this message is 1013.


Programmer responseInsert a WAIT statement for the given event variableinto the flow of control between the REWRITE orDELETE and READ statements. The REWRITE or

DELETE statement should run after completion of theREAD statement.

Symbolic Feedback CodeIBM0PD

IBM0814S ONCODE=oncode-value Excessiveincomplete I/O operationsoccurred for file file-name.

ExplanationAn attempt was made to initiate an input/outputoperation beyond the limit imposed by the NCP(number of channel programs) subparameter of theDCB parameter or option of the ENVIRONMENTattribute. For a file with the attributes SEQUENTIALand UNBUFFERED, the default for NCP is one. Thelimit, for VSAM files, is specified either by the NCPoption of the ENVIRONMENT attribute or by theSTRNC sub-parameter of the AMP parameter in theDD statement. The limit is one for both SEQUENTIALand DIRECT UNBUFFERED files except when using theISAM compatibility interface. The ONCODE associatedwith this message is 1014.


Programmer responseModify the program so that the input/output operationis not initiated until an incomplete input/outputoperation completes.

Symbolic Feedback CodeIBM0PE

IBM0816S ONCODE=oncode-value Theimplicit OPEN was unsuccessfulfor file file-name.

ExplanationAn error occurred during the implicit opening of afile. The UNDEFINEDFILE condition was raised anda normal return was made from the associated ON-unit, but the file was still unopened. The ONCODEassociated with this message is 1016.



Programmer responseEnsure that the file has been completely and correctlydeclared, and that the input/output statement thatimplicitly opens the file is not in conflict with the filedeclaration.

Symbolic Feedback CodeIBM0PG

IBM0818S ONCODE=oncode-value Anunexpected end of file/string wasdetected in the STREAM input.

ExplanationThe end of the file was detected before the completionof a GET FILE statement. The ONCODE associated withthis message is 1018.


Programmer responseFor edit-directed input, ensure that the last item ofdata in the stream has the same number of charactersas specified in the associated format item. If theerror occurs while an X-format is running, ensure thatthe same number of characters to be skipped arepresent before the last data item in the stream. Forlist-directed and data-directed input, ensure the lastitem of data in the data set that precedes the end-of-file character is terminated by a quote character for astring or a 'B' character for a bit-string.

Symbolic Feedback CodeIBM0PI

IBM0819S ONCODE=oncode-value An attemptwas made to close a file in thewrong task.

ExplanationA file can only be closed by the task that opened it.



Programmer responseChange your program to insure the close is issued inthe same task that opened the file.

Symbolic Feedback CodeIBM0PJ

IBM0820S ONCODE=oncode-value An attemptwas made to access a lockedrecord.

ExplanationIn an exclusive environment, an attempt was made toread, rewrite, or delete a record when either the recordor the data set was locked by another file in this task.The ONCODE associated with this message is 1021.


Programmer responseEnsure that all files accessing the data set have theEXCLUSIVE attribute. If a READ statement is involved,specify the NOLOCK option to suppress the lockingmechanism.

Symbolic Feedback CodeIBM0PK

IBM0821S ONCODE=oncode-value An I/Ostatement occurred before a WAITstatement completed a previousREAD.

ExplanationWhile an indexed sequential file was open for directupdating, an input/output statement was attemptedbefore the completion of a previous READ statementwith the EVENT option. The ONCODE associated withthis message is 1020.


Programmer responseInclude a WAIT statement so that the erroneous input/output statement cannot be run until the completion ofthe previous READ statement with the EVENT option.

Symbolic Feedback CodeIBM0PL

IBM0822S ONCODE=oncode-valueInsufficient space was available


for a record in the sequentialoutput data set.

ExplanationThe space allocated for the sequential output data setwas full. The ONCODE associated with this message is1040.


Programmer responseIncrease the size of the data set, or check the logic ofthe application for possible looping.

Symbolic Feedback CodeIBM0PM

IBM0823S ONCODE=oncode-value An invalidcontrol format item was detectedduring a GET/PUT STRING.

ExplanationAn invalid control format item (PAGE, LINE, SKIP, orCOL) was detected in a remote format list for a GET orPUT STRING statement.

DCL(A,B) CHAR(10),C CHAR(80);F: FORMAT(A(10), SKIP,A(10));A='FRED'; B='HARRY';PUT STRING(C) EDIT(A,B) (R(F));



Programmer responseModify the source program so that GET or PUT STRINGstatements do not use the control format items PAGE,LINE, SKIP or COL.

Symbolic Feedback CodeIBM0PN

IBM0824S ONCODE=oncode-value Recordswere still locked in a subtaskwhile attempting to closeEXCLUSIVE file file-name.

ExplanationWhen an EXCLUSIVE file is closed by a task, no recordsshould be locked by any subtasks.

ONCODE associated with this message is 1023.


Programmer responseChange your program to insure that the subtasks freeany record locks before the file is closed.

Symbolic Feedback CodeIBM0PO

IBM0825S ONCODE=oncode-value The EVENTvariable was already used.

ExplanationAn input/output statement with an EVENT option wasattempted while a previous input/output statementwith an EVENT option that used the same eventvariable was still incomplete. The ONCODE associatedwith this message is 1015.


Programmer responseEither change the event variable used in the secondEVENT option or insert a WAIT statement for the eventvariable between the two input/output statements.

Symbolic Feedback CodeIBM0PP

IBM0826S ONCODE=oncode-value The EVENTvariable was already used with aDISPLAY statement.

ExplanationAn input/output statement with an EVENT option wasattempted while a previous DISPLAY statement withan EVENT option that used the same event variablewas still incomplete.




Programmer responseEither change the event variable used in the secondEVENT option or insert a WAIT statement for theevent variable between the DISPLAY statement andthe input/output statement.

Symbolic Feedback CodeIBM0PQ

IBM0827S ONCODE=oncode-value The EVENTvariable was already active andwas used with entry entry-name.

ExplanationAn event variable that was already used in the EVENToption in a CALL statement was still active whenused again in the EVENT option of an input/outputstatement.



Programmer responseEither use a different event variable or insert a WAITstatement so that the input/output statement is notrun until the event variable becomes inactive.

Symbolic Feedback CodeIBM0PR

IBM0828S ONCODE=oncode-value Anincorrect sequence of I/Ooperations was performed on anassociated file.

ExplanationOperations on a set of associated files were not carriedout in the correct sequence, as follows:

1. Appropriate I/O operations were not carried outin the sequence Read-Punch-Print. Only the Printoperation can be omitted or repeated.

2. An attempt was made to print more than themaximum number of lines on a card, using a printfile that was associated with a read or punch file.



Programmer responseEnsure that the above rules have not been violated.

Symbolic Feedback CodeIBM0PS

IBM0829S ONCODE=oncode-valueInsufficient virtual storage wasavailable to VSAM.

ExplanationDuring an OPEN/CLOSE or any other operation ona VSAM data set, insufficient storage was availablefor workspace and control blocks. The ONCODEassociated with this message is 1025.


Programmer responseIncrease the REGION size for the VSAM application.

Symbolic Feedback CodeIBM0PT

IBM0830S ONCODE=oncode-value An I/Oerror occurred during a CLOSEoperation.

ExplanationAn I/O error occurred while a VSAM close routinewas either reading or writing a catalog record, orcompleting an outstanding I/O request.



Programmer responseIf the problem is related to an insufficient amountof virtual storage available to VSAM, try running thejob with a larger REGION size. The access methodservices VERIFY command can be used to obtainmore information pertaining to the error. Refer to theMVS/DFP Access Method Services manual for details.


Symbolic Feedback CodeIBM0PU

IBM0831S ONCODE=oncode-value A positionwas not established for asequential READ statement.

ExplanationA READ statement without the KEY option wasattempted on a VSAM data set. This occurred aftersequential positioning was lost as the result ofa previous error during sequential processing (forexample, read error on index set or failure to positionto next highest key after a "key not found" condition).The ONCODE associated with this message is 1026.


Programmer responseUse the KEYTO option of the READ statement toobtain the keys of records read. Use this informationto reposition a file for subsequent retrieval whenpositioning is lost.

Symbolic Feedback CodeIBM0PV

IBM0832S ONCODE=oncode-valueInsufficient space was availablefor VSAM file file-name.

ExplanationVSAM was unable to allocate additional DASD spacefor the data set (ESDS or KSDS). This condition wasraised during an attempt to write or locate a recordduring the sequential creation or extension of a dataset and the space allocated to the data set was full.For a KSDS, the condition may have occurred whenthe associated PL/I file was opened for update and anattempt was made to write new records to the file or toincrease the size of existing records using the WRITEand REWRITE statements respectively. An attempt toincrease the size of a data set while processing withSHROPT=4 and DISP=SHR may also have raised thiscondition. The ONCODE associated with this messageis 1022.


Programmer responseUse the access method services ALTER commandto extend a data set provided secondary allocationwas specified during data set definition. Refer to theMVS/DFP Access Method Services manual for details.

Symbolic Feedback CodeIBM0Q0

IBM0833S ONCODE=oncode-value Arequested record was held inexclusive control.

ExplanationThe VSAM data set control interval containing therequested record was in the process of being updatedby another file which used the same DD statement.The ONCODE associated with this message is 1027.


Programmer responseRetry the update after completion of the other file'sdata transmission, or avoid having two files associatedwith the same data set at one time.


IBM0834S ONCODE=oncode-value Therequested record was stored on anon-mounted volume.

ExplanationThe requested record was stored on a non-mountedvolume of a VSAM data set spanning several volumes.The ONCODE associated with this message is 1028.


Programmer responseEnsure that all volumes on which a VSAM data setresides are accessible at the time the application isrun.



IBM0835S ONCODE=oncode-value An attemptto position the file for a sequentialREAD failed. Subcode1= sc1Subcode2= sc2

ExplanationAn attempt to reposition to the next highest key forsubsequent sequential retrieval, after the 'key notfound' condition, failed. If file processing is continued,the next I/O statement should specify the KEY optionto effect positioning. Otherwise message IBM0831may result. Subcode1 and Subcode2 provide detailedVSAM diagnostic information. See message IBM0811Sfor an explanation of these fields.



Programmer responseUse the VSAM diagnostic information to correctthe cause of the error and resubmit the program.Alternatively, use the KEYTO option of the READstatement to obtain the keys of the records read, sothat you can reposition the file yourself for sequentialretrieval.


IBM0836S ONCODE=oncode-value Thenumber of concurrent operationson a data set exceeded STRNO.

ExplanationSeveral files accessed a VSAM data set by means ofthe same DD statement (that is, using the same title).The STRNO subparameter of the DD statement thatspecified the total number of operations on all filesthat can be active at the same time was less thanthe number of concurrent operations. The ONCODEassociated with this message is 1014.


Programmer responseEnsure the concurrent operations are valid. Or, modifythe STRNO parameter to reflect the correct numberof allowed concurrent operations. A read-rewrite pairof operations on a sequential file counts as one

operation. For example, if three sequential files are toupdate the same data set at the same time, 'STRNO=3'should be specified in the DD statement.


IBM0837S ONCODE=oncode-value An erroroccurred during an index upgrade.Subcode1= sc1 Subcode2= sc2

ExplanationA change to a base cluster could not be reflectedin one of the indexes of the cluster's upgradeset. Subcode1 and Subcode2 provide detailed VSAMdiagnostic information. See message IBM0811S for anexplanation of these fields.



Programmer responseRun the job with a larger REGION size. The problemmight be related to an insufficient amount of virtualstorage available to VSAM.


IBM0838S Incorrect record length or recordlength not sufficient contain newalternate index key pointer.

ExplanationThe record length specified was 0 or larger than themaximum or not equal to the slot size for a fixed-length RRDS. This message will also be issued whenthe RECORDSIZE specified for a VSAM alternate indexdefined with NONUNIQUEKEY is not large enough tohold all the base cluster key pointers for a given non-unique alternate key. This message can also be issuedif the number of alternate index pointers exceeded32767, the maximum number allowed in an alternateindex for any given key.

AThe ONCODE associated with this message is 1030.



Programmer responseMake sure the RECLEN specified is not 0 or notlarger than the maximum allowed. For fixed-lengthRRDS, RECLEN must be equal to the slot size. For non-unique alternate indices, each alternate index recordcontains pointers to all the records that have theassociated alternate index key. As a result, the indexrecord can be quite large. Make sure the RECORDSIZEspecified during the creation of the alternate indexis large enough. If the number of alternate indexpointers exceed the allowed maximum of 32767, thena different alternate key would need to be used. Referto the appropriate VSAM manual for more informationregarding the use of alternate index paths.


IBM0839S ONCODE=oncode-value An invalidalternate index pointer was used.

ExplanationA pointer in the alternate index was invalid. This mayhave been caused by incorrect use of the alternateindex as a Key Sequenced Data Set (KSDS).



Programmer responseRefer to z/OS Language Environment ProgrammingGuide regarding a general description on the use ofalternate index. For more information, refer to z/OSLanguage Environment Programming Guide.


IBM0840S ONCODE=oncode-value An invalidsequential WRITE was attempted.

ExplanationA WRITE statement on a file associated with a RelativeRecord Data Set (RRDS) did not specify a relativerecord number. This resulted in an attempt to writein a slot already containing a record. The ONCODEassociated with this message is 1031.


Programmer responseModify the WRITE statement to include a relativerecord number (or key) by specifying the KEYFROMoption. If a relative record number is used, ensurethe record number is valid. For error diagnosis, theKEYTO option can be used to obtain the number ofthe key for each record written if previous sequentialWRITE statements did not have the KEYFROM optionspecified.


IBM0841S ONCODE=oncode-value A data set,open for output, used all availablespace.

ExplanationNo more space on the disk.



Programmer responseIncrease the size of the data set or check the logic ofthe program for possible looping.


IBM0842S ONCODE=oncode-value An attemptwas made to write a recordcontaining record delimiter.

ExplanationAn attempt was made to write a record containing arecord delimiter (line feed character or carriage controland line feed character combination) to a native dataset with the type(lf) or type(crlf) option applied.

System actionThe record is not transmitted to the data set.


Programmer responseEither change your program to let PL/I write thedelimiter or use the type(fixed) option.

Symbolic Feedback CodeIBM0QA

IBM0843S ONCODE=oncode-value A record inthe data set was not properlydelimited.

ExplanationWhile reading a native data set with TYPE(CRLF)applied, a record delimiter (carriage control and linefeed character combination) was not found before thenumber of bytes specified by RECSIZE were read.


System actionThe record is not assigned to the record variable.

Programmer responseIncrease the value of RECSIZE appropriately and re-run your program.

Symbolic Feedback CodeIBM0QB

IBM0850S ONCODE=oncode-value Theaggregate length exceeded thelimit of 2**24 bytes.

ExplanationThe length of the structure or array to be mappedwas greater than 2²4, thus exceeding thelimits of addressability. The program was compiledwith CMPAT(V1). The ONCODE associated with thismessage is 3800.


Programmer responseReduce the size of the array or structure to a sizethat can be accommodated within the main storageavailable. If a variable is used to specify the dimensionor length, check that it has been correctly initializedbefore the storage is allocated to the aggregate. Or,compile the program with the CMPAT(V2) option.

Symbolic Feedback CodeIBM0QI

IBM0851S ONCODE=oncode-value The arraystructure element could not bemapped.

ExplanationThe program was compiled with CMPAT(V1). Either theprogram contained a structure with:

• An adjustable element and an array element withextents that cause the relative virtual origin toexceed 2³²-1.

• A structure with an adjustable element and an arraywith a lower bound greater than the upper bound.

DCL 1 A CTL,2 B CHAR(N),2 C (15000:15001, 15000:15001,15000:15001) CHAR(32700);N=2;ALLOCATE A;



Programmer responseIf possible, compile the program with the CMPAT(V2)option. If recompiling is not possible:

• Ensure aggregates with array elements remainwithin the limit of addressability (2³²-1), or

• Ensure the lower bound is not greater than the upperbound.

Symbolic Feedback CodeIBM0QJ

IBM0852S ONCODE=oncode-value Themapping of an aggregate to aCOBOL form failed.

ExplanationAn attempt was made to pass to or obtain froma COBOL program a structure with more thanthree dimensions. The ONCODE associated with thismessage is 3808.



Programmer responseEnsure PL/I aggregates that are passed to or fromCOBOL programs are within the limits describedabove.

Symbolic Feedback CodeIBM0QK

IBM0854S ONCODE=oncode-value Themaximum depth of iterationexceeded the limits during anarray initialization.

ExplanationThe depth of iteration within the initial attribute on anAUTOMATIC array exceeded 12.



Programmer responseChange the depth of iteration to less than 12.

Symbolic Feedback CodeIBM0QM

IBM0855S ONCODE=3809 The length of adata aggregate exceeded themaximum limit.

ExplanationThe length of the structure to be mapped was greaterthan the allowable limit. Structures that do not containany unaligned bit elements have a maximum size of2**31-1 bytes. Structures with one or more unalignedbit elements have a maximum size of 2**28-1 bytes.


Programmer responseReduce the size of the structure to less than themaximum allowed. If a variable is used to specify thedimension or length of an element, ensure the variableis correctly initialized before the storage is allocated tothe aggregate.

Symbolic Feedback CodeIBM0QN

IBM0856S ONCODE=3810 An extent of anarray exceeded the maximumlimit.

ExplanationDuring structure mapping, an array with an extentgreater than the allowed maximum was encountered.The largest allowable extent (upper bound minuslower bound) of any dimension in an array is 2**31-1.


Programmer responseReduce the extent of the array to less than themaximum allowed. If a variable is used to specify abound, ensure the variable is correctly initialized.

Symbolic Feedback CodeIBM0QO

IBM0860S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because the VSAM serverwas not available to performthe OPEN (FILE= or ONFILE= file-name).

ExplanationVSAM Record Level Sharing (RLS) is supported bya VSAM server address space and data space. TheVSAM server has failed and is unavailable for PL/I tocomplete the open function.



Programmer responseWhen the VSAM server becomes available, resubmitthe program. See the VSAM publications for additionalinformation.

Symbolic Feedback CodeIBM0QS


IBM0861S ONCODE=oncode-value TheUNDEFINEDFILE condition wasraised because an attempt toposition the file at the first recordfailed FILE= or ONFILE= file-name).Subcode1=sc1 Subcode2=sc2

ExplanationFor SEQUENTIAL INPUT or UPDATE, the file mustbe positioned at the first record. If an attempt toposition at the first record fails, the file is closedand the UNDEFINEDFILE condition is raised with thismessage. Subcode1 and Subcode2 provide detailedVSAM diagnostic information. See message IBM0811Sfor an explanation of these fields.




Symbolic Feedback CodeIBM0QT

IBM0862S ONCODE=oncode-value The VSAMserver was not available toexecute a VSAM I/O request

ExplanationVSAM Record Level Sharing (RLS) is supported bya VSAM server address space and data space. TheVSAM server has failed and is unavailable to performVSAM I/O requests. The failing file must be CLOSEd,if an attempt is made to reopen the file and continueprocessing.



Programmer responseWhen the VSAM server becomes available, resubmitthe program. See z/OS Language EnvironmentProgramming Guide for additional information.

Symbolic Feedback CodeIBM0QU

IBM0863S ONCODE=oncode-value A deadlockwas detected while attempting tolock a record.

ExplanationThe program has attempted to lock a record usingVSAM Record Level Sharing (RLS). However, VSAM RLSprocessing has detected that a deadlock conditionexists within its sysplex-wide set of lock ownersand lock waiters. This program has been selected toreceive the deadlock error so that the deadlock can bebroken.



Programmer responseThis program was found to be in deadlock withother programs. The system programmer will haveSMSVSAM diagnostic tools and diagnostic informationis available from CICS to determine what programsencountered the deadlock. The action for this erroris to avoid running the same mix of programs. Theprogram may also attempt to retry the PL/I requestwhich encountered the deadlock error some numberof times. However, depending of the mix of programs,this may or may not be successful.

Symbolic Feedback CodeIBM0QV

IBM0865S ONCODE=oncode-value A retainedlock reject has occurred whileattempting to lock a record.

ExplanationThis program has attempted to lock a record usingVSAM Record Level Sharing (RLS). However, VSAM RLShas rejected this request for the lock because of itsretained lock status. That is, the lock is held by a failedCICS and until that CICS restarts and completes itsbackout of the record, the record is not available.




Programmer responseThis error can occur on a READ statement for a fileopened for INPUT when RLS=CR is used, but not ifRLS=NRI is used. For sequential read, the programmay wish to proceed to read the next available record.Or, the program can be resubmitted when the CICSrestart is complete. See z/OS Language EnvironmentProgramming Guide for additional information aboutthis failure.


IBM0870S ONCODE=oncode-value The OS/VSCOBOL program is not supportedfor interlanguage communicationin Language Environment.

ExplanationThe OS/VS COBOL program is not supportedfor interlanguage communication in LanguageEnvironment.



Programmer responseCompile the OS/VS COBOL program with IBM SAA AD/Cycle COBOL/370 or do not run the application withLanguage Environment.

Symbolic Feedback CodeIBM0R6

IBM0880S ONCODE=oncode-value A programcheck occurred in the SORT/MERGE program.

ExplanationAn error occurred while the SORT/MERGE program wasrunning after it was invoked from a PL/I program byuse of the PL/I SORT interface facilities. As a result,the SORT program was unable to continue and controlwas passed to the PL/I error-handler. The ONCODEassociated with this message is 9200.


Programmer responseBecause the problem occurred while the SORT/MERGEprogram was running, refer to the appropriate SORT/MERGE program manual for an explanation of anySORT program messages and any other informationthat might be necessary to correct the error.

Symbolic Feedback CodeIBM0RG

IBM0882S ONCODE=oncode-value The stringRECORD TYPE was missing inthe second argument of the callPLISRTx statement.

ExplanationThe RECORD TYPE string must be given in the RECORDstatement for calls to PLISRTx. It is used to specify thetype of records in the file.



Programmer responseEnsure the RECORD TYPE is coded correctly in theRECORD statement and rerun the application.

Symbolic Feedback CodeIBM0RI

IBM0883S ONCODE=oncode-value Incorrectrecord type was specified inthe second argument of the callPLISRTx statement.

ExplanationThe RECORD TYPE in the RECORD statement ofPLISRTx takes F for fixed length and V for varyinglength EBCDIC. Characters other than F and V areinvalid.



Programmer responseCode the correct record type in the RECORD statementand rerun the application.


Symbolic Feedback CodeIBM0RJ

IBM0884S ONCODE=oncode-value TheLENGTH= was not specified inthe second argument of the callPLISRTx statement.

ExplanationThe LENGTH specifier must be given for calls toPLISRTB, and PLISRTD. Use this specifier to indicatethe length of the record to be sorted.



Programmer responseEnsure the LENGTH specifier is coded in the RECORDstatement and rerun the application.

Symbolic Feedback CodeIBM0RK

IBM0885S ONCODE=oncode-value The lengthspecified in the LENGTH=parameter in the second argumentof the call PLISRTx statement wasnot numeric.

ExplanationThe length coded for LENGTH= in the RECORDstatement of the PLISRTx call must be numerical.



Programmer responseEnsure numerical data is coded for LENGTH= in theRECORD statement and rerun the application.

Symbolic Feedback CodeIBM0RL

IBM0886S ONCODE=oncode-value Incorrectreturn code rc received from user'sE15 or E35 handling routine.

ExplanationThe allowed return code from the E15 input handlingroutine are 8, 12, and 16. The allowed return codefrom the E35 output handling routine are 4 and 16.



Programmer responseEnsure the return code returned by the PLIRETC built-in function is correct and rerun the application.

Symbolic Feedback CodeIBM0RM

IBM0887S ONCODE=oncode-value dfsortfailed with a return code of rc.

ExplanationThe sort program returns an unsuccessful return code.For the explanation of the return code, refer to themessage in the JES log.



Programmer responseCorrect the program based on the information fromthe return code and the message and rerun theapplication.

Symbolic Feedback CodeIBM0RN

IBM0888S ONCODE=oncode-value PLISRTxnot supported in environmentsother than ADMVS.

ExplanationThe PL/I program calling the PLISRTx function musthave the ADMVS running.




Programmer responseTake out the PLISRTx call and rerun the application.

Symbolic Feedback CodeIBM0RO

IBM0889S ONCODE=oncode-value Fetch ofSMARTSort failed.

ExplanationFetch of the SMARTSort library failed.



Programmer responseTake out the PLISRTx call and rerun the application.

Symbolic Feedback CodeIBM0RO

IBM0890S ONCODE=oncode-value DD for sortinput data set is missing or invalid.

ExplanationThe DD statement for the SORT input data set ismissing.



IBM0891S ONCODE=oncode-value DD for sortoutput data set is missing orinvalid.

ExplanationThe DD statement for the SORT output data set ismissing.



IBM0892S ONCODE=oncode-value DD for sortdata set must specify a LENGTH orLRECL.

ExplanationThe DD statement for the SORT data set is missing aLENGTH or LRECL specification.



IBM0893S ONCODE=oncode-value DD for sortdata set must specify a TYPE.

ExplanationFetch of the SMARTSort library failed.



IBM0894S ONCODE=oncode-value The stringSORT FIELDS was missingin the first argument of the callPLISRTx statement.

ExplanationThe SORT FIELDS string must be given in the SORTstatement for calls to PLISRTx. It is used to specifywhat fields determine the sort.



Programmer responseEnsure the SORT FIELDS is coded correctly in theSORT statement and rerun the application.

IBM0895S ONCODE=oncode-value SORTFIELDS specifies too many sortfields.

ExplanationThe ONCODE associated with this message is 9215.


IBM0896S ONCODE=oncode-value SORTFIELDS contains invalid startand/or length fields.




IBM0897S ONCODE=oncode-value The SORTFIELDS specifies an invalid form.



IBM0898S ONCODE=oncode-value The SORTFIELDS specifies an invalidsequence.



IBM0900S ONCODE=oncode-value The WAITstatement would cause apermanent wait. The program hasbeen terminated.

ExplanationA WAIT statement that could never have beencompleted was encountered.

COMPLETION (E1) = '0'B;WAIT(E1);

The event E1 is inactive and incomplete.



Programmer responseModify the program so that the WAIT statement cannever wait for an inactive or incomplete event.

Symbolic Feedback CodeIBM0S4

IBM0913S ONCODE=oncode-value An erroroccurred on a FREE statement.

ExplanationPL/I storage management detected an error during theprocessing of either a FREE statement or the PLIFREEbuilt-in function.



Programmer responseEnsure the variable specified on the FREE statement isa controlled variable that has been allocated. Anothersuggestion is to acquire a storage report to check onthe program's use of storage. A PLIDUMP should beobtained for later study by IBM.

Symbolic Feedback CodeIBM0SH

IBM0914S ONCODE=oncode-value Anabnormal termination hasoccurred in a linked PL/I programwhile running a CICS transaction.

ExplanationA PL/I program called through EXEC LINK or EXECXCTL terminated abnormally.



Programmer responseExamine the linked PL/I program unit and correct theerror that caused error.

Symbolic Feedback CodeIBM0SI

IBM0915S ONCODE=oncode-value An internalerror occurred in PL/I library.

ExplanationAn error occurred within the PL/I library. The ONCODEassociated with this message is 1104.



Programmer responseA PLIDUMP should be obtained for later study by IBM.

Symbolic Feedback CodeIBM0SJ

IBM0916S ONCODE=oncode-value An objectwindow was unable to be created.

ExplanationThe Presentation Manager returned an error when anattempt was made to create an object window duringthe execution of a DISPLAY statement or I/O to aPresentation Manager Terminal (PMT).



Programmer responseThe problem may be that too many windows havebeen created. Reduce the number of windows and re-run your program.

Symbolic Feedback CodeIBM0SK

IBM0917S ONCODE=oncode-value An internalerror occurred in PL/I storagemanagement.

ExplanationThere was either a problem freeing storage, orinsufficient space available to satisfy a storageallocation request within PL/I storage management.The ONCODE associated with the storage allocationrequest is 1106. The ONCODE associated with thestorage free processing is 1107.


Programmer responseAcquire a storage report to check on the program's useof storage. A PLIDUMP should be obtained for laterstudy by IBM.

Symbolic Feedback CodeIBM0SL

IBM0924W Closing a file in the ON-unitcaused errors in this statement.

ExplanationAn ON-unit for an I/O condition was entered and thefile associated with the ON-unit was closed in the ON-unit. A GOTO statement should have been used to exitfrom the ON-unit. The result of a normal return froman ON-unit is undefined.


Programmer responseUse a GOTO statement to exit from the ON-unit, orclose the file outside of the ON-unit.

Symbolic Feedback CodeIBM0SS

IBM0925W The PLIRETC value was reduced to999.

ExplanationThe value passed to the PLIRETC built-in procedurewas greater than 999. 999 is the maximum alloweduser value.

System actionProcessing continues with the next sequentialstatement.

Programmer responseEnsure all PLIRETC values are below 999.

Symbolic Feedback CodeIBM0ST

IBM0926S The CHECKPOINT/RESTARTfacility is not supported in a CMSenvironment.

ExplanationAn attempt was made to call the CHECKPOINT/RESTART facility from PL/I. CHECKPOINT/RESTART isnot supported under CMS. The ERROR condition wasraised.



Programmer responseRemove the call to the CHECKPOINT/RESTART facility.If this facility needs to be used, run the applicationunder OS/390®.

Symbolic Feedback CodeIBM0SU

IBM0930S ONCODE=oncode-value An attemptwas made to call a Checkout-compiled program in LanguageEnvironment.

ExplanationCheckout-compiled programs are not supported inLanguage Environment.



Programmer responseRemove the call to the Checkout-compiled program.

Symbolic Feedback CodeIBM0T2

IBM0950S ONCODE=oncode-value A systemerror occurred in PL/Imultithreading support for theWAIT statement.

ExplanationAn uninitialized task variable may have been specifiedin the THREAD option. Another reason why an errormay have occurred in WAIT is that the operatingsystem may have run out of resources to satisfy therequest or may have timed out.



Programmer responseEnsure that the tasking variable has been initialized toa valid value. The ATTACH statement with the THREADoption must be used to give a tasking variable astarting value. Ensure that there are enough resourcesfor the operating system to acquire.

Symbolic Feedback CodeIBM0TM

IBM0951S ONCODE=oncode-value A systemerror occurred in PL/Imultithreading support for theDETACH statement.

ExplanationAn uninitialized task variable may have been specifiedin the THREAD option.



Programmer responseEnsure that the tasking variable has been initialized toa valid value. The ATTACH statement with the THREADoption must be used to give a tasking variable astarting value.

Symbolic Feedback CodeIBM0TN

IBM0952S ONCODE=oncode-value A systemerror occurred in PL/Imultithreading support for theATTACH statement.

ExplanationThe operating system may have run out of resources(not enough memory, too many handles) to satisfy therequest.



Programmer responseEnsure that there are enough resources for theoperating system to acquire.


Symbolic Feedback CodeIBM0TO

IBM0953S ONCODE=oncode-value A systemerror occurred in PL/Imultithreading support for theSTOP statement.

ExplanationAn uninitialized task variable may have been specifiedin the THREAD option.



Programmer responseEnsure that the tasking variable has been initialized toa valid value. The ATTACH statement with the THREADoption must be used to give a tasking variable astarting value.

Symbolic Feedback CodeIBM0TP

IBM0954S Nested condition limit has beenexceeded.

ExplanationToo many conditions have been raised whileprocessing other conditions.


Programmer responseThe most common cause of this message is when theERROR condition is raised from within and ERROR on-unit and the ERROR on-unit does not use ON ERRORSYSTEM to specify implicit action be taken for nestedERROR conditions.

Symbolic Feedback CodeIBM0TQ

IBM0955S ONCODE= oncode-value Asystem error occurred inPL/I. Multithreading support forthe ATTACH statement was

issued under the POSIX(OFF)environment.

ExplanationAn attempt was made to ATTACH a thread under thePOSIX(OFF) environment.



Programmer responseEnsure that the POSIX(ON) run-time option isspecified for the Multithreading application.

Symbolic Feedback CodeIBM0TR

IBM0960S XML to language structureconversion could not completein procedure PROCEDURE-NAMEbecause an error return codeof RETURN-CODE was receivedfrom the PLISAX FUNCTION-SUFFIX built-in function. The erroroccurred at element ELEMENT-NAME with the character contentCONTENT-CONTEXT.

ExplanationXML to language structure conversion makes use ofthe PL/I PLISAXx built-in function. The return codeprovided is from the PL/I PLISAXx built in function asdescribed in the Enterprise PL/I for z/OS ProgrammingGuide.

System actionThe converter will either signal a LanguageEnvironment condition or, if the optional feedbackcode argument is provided, a condition tokenrepresenting the condition will be placed in theargument.

Programmer responseUse the return code to determine the error and correctthe input XML message.

Symbolic Feedback CodeIBM0U0


IBM0961S XML to language structureconversion could not completein procedure PROCEDURE-NAMEbecause the valid range of arepeating group or repeating dataitem was exceeded. The erroroccurred at element ELEMENT-NAME

ExplanationXML to language structure conversion encounterserrors that are distinct from PLISAXA/B errors.


Programmer responseCorrect the input XML message. Check that the inputXML document has the correct number of occurrencesof all entries that repeat.


IBM0962S XML to language structureconversion could not completein procedure PROCEDURE-NAMEbecause no element names in theXML document were recognized bythe converter.



Programmer responseSupply the correct XML message corresponding to thisconverter.


IBM0963S XML to language structureconversion could not completein procedure PROCEDURE-NAMEbecause the character contentfor element ELEMENT-NAMEwas longer than the element'smaximum of LIMIT characters.



Programmer responseCorrect the input XML message.


IBM0964S XML to language structureconversion could not completein procedure PROCEDURE-NAMEbecause conversion of thecharacter content of an elementthat is mapped as numericfailed. The error occurred atelement ELEMENT-NAME with thecharacter content CHARACTER-CONTENT.




Programmer responseCorrect the input XML message and try again. Checkthat the character content represents a numericquantity that is both valid and compatible with thetarget language structure member.


IBM0965S XML to language structureconversion could not completein procedure PROCEDURE-NAMEbecause the size of the inputXML message was INPUT-LENcharacters, which exceeds themaximum of MAXIMUM charactersfor this converter.

ExplanationXML to language structure conversion supports parsingXML messages whose length falls within certaincompiler limits.


Programmer responseCorrect the input XML message or define an auxiliarylanguage structure or structures to process the XML insegments.


IBM0966S XML to language structureconversion could not completein procedure PROCEDURE-NAMEbecause the character content forelement ELEMENT-NAME had alength equal to or greater thanINPUT-LENGTH characters whichwas too long for the converter toprocess.

ExplanationThe XML converter maintains a buffer for charactercontent whose size is equal to that of the largest

character member in the language structure or 128,whichever is larger.


Programmer responseCorrect the input XML message. Check for anyexcessive whitespace in the element content.


IBM0967S Language structure to XMLconversion could not completein procedure PROCEDURE-NAMEbecause the maximum outputmessage size of SIZE characterswas exceeded while creating theoutbound XML document.

ExplanationLanguage structure to XML conversion supportsgeneration of XML messages whose length fallswithin certain compiler limits. Whitespace suppressionand entity reference expansion is performed duringcreation of the XML document. Entity referenceexpansion increases the size of a message in relationto the number of special characters in the sourcelanguage structure that need to be represented as oneof the five predefined entity references in XML.


Programmer responseAvoid the use of the five predefined entities in XMLwhen populating the language structure or define anauxiliary language structure or structures to generatethe output XML in segments.



IBM0968S The XML Conversion couldnot complete in procedurePROCEDURE-NAME because anon-zero return code was receivedfrom the Unicode ConversionService CUNLCNV while convertingfrom CCSID SOURCE-CCSID toCCSID TARGET-CCSID.

ExplanationXML Conversion uses PL/I built-in support forUNICODE when the input XML or output XML isencoded in either UTF-16 or UTF-8.


Programmer responseCheck that z/OS Support for UNICODE is properlyinstalled and that the conversion attempted by XMLConversion is supported by the current conversionimage.


IBM0969S Language structure to XMLconversion could not completein procedure PROCEDURE-NAMEbecause the content ofnon-numeric member MEMBER-NAME of language structureSTRUCTURE-NAME containedcharacters that are not legal in anXML document.

ExplanationCertain language structure members permit storageof characters that are not legal in an XML document.The permitted characters are defined by the XMLspecification at W3C (www.w3.org).


Programmer responseEnsure that the language structure member is properlyinitialized and does not contain any characters that areillegal in XML before attempting conversion.


IBM0970S Language structure to XMLconversion could not completein procedure PROCEDURE-NAMEbecause the content of numericmember MEMBER-NAME oflanguage structure STRUCTURE-NAME is invalid.

ExplanationLanguage structure to XML conversion has determinedthat the contents of the storage occupied by a numericdata structure member is invalid for the type.


Programmer responseEnsure that the numeric data structure member isproperly initialized following the semantics of thelanguage.

Symbolic Feedback CodeIBM0UA

IBM0971S XML to language structureconversion could not completein procedure PROCEDURE-NAMEbecause the maximum XMLelement nesting depth wasexceeded. The error occurredat element ELEMENT-NAME withcharacter content CHARACTER-CONTENT.

ExplanationXML to language structure conversion maintains aninternal stack which represents the full qualificationof the current element being processed in the XMLdocument. If extraneous XML elements not describedin the XML schema to which the converter is bound


http://www.w3.org

are present in the XML document, they may exceed themaximum supported element depth.


Programmer responseEither supply XML documents to the converter thatvalidate against the bound XML schema or remove theextraneous element that causes the failure from theinput XML document.

Symbolic Feedback CodeIBM0UB

IBM0972S XML conversion could notcomplete in procedurePROCEDURE-NAME because anattempt to register an exceptionhandler failed with LanguageEnvironment error LE-ERROR.

ExplanationThe converter uses Language Environment callableservices to handle errors that may occur duringconversion. An attempt by the converter to register aLanguage Environment condition handler failed.


Programmer responseEnsure that Language Environment is configuredproperly and that no conditions exist in the chainof execution leading up to the converter that wouldprevent proper operation.

Symbolic Feedback CodeIBM0UC

IBM0973S XML conversion could notcomplete in procedurePROCEDURE-NAME because anattempt to unregister an exception

handler failed with LanguageEnvironment error LE-ERROR.

ExplanationThe converter uses Language Environment callableservices to handle errors that may occur duringconversion. An attempt by the converter to register aLanguage Environment condition handler failed.



Symbolic Feedback CodeIBM0UD

IBM0974S XML conversion could notcomplete in procedurePROCEDURE-NAME because theaddress of one or more parameterswas not valid.

ExplanationThe converter detected that one or more of theparameters that were passed to its main entry pointdo not have valid storage addresses to which theconverter could refer and obtain the value.


Programmer responseEnsure that each parameter passed to the converterhas a valid storage address unless a particularparameter can be null as defined by the convertercall interface. For example, a null message addresspassed to the outbound converter will be interpreted


as a request for the maximum outbound message sizeto be returned instead of performing a conversion.

Symbolic Feedback CodeIBM0UE

IBM0975S XML to language structureconversion could not completein procedure PROCEDURE-NAMEbecause a response code ofRESPONSE-CODE with reasoncode REASON-CODE was receivedfrom the bidirectional dataconversion module MODULE-NAME while processing elementELEMENT-NAME.

ExplanationXML to language structure conversion makes useof an external module to handle bidirectional dataconversions.


Programmer responseRefer to the bidirectional data conversion moduledocumentation for explanations of return codes.

Symbolic Feedback CodeIBM0UF

IBM0976S Language structure to XMLconversion could not completein procedure PROCEDURE-NAMEbecause a response code ofRESPONSE-CODE with reasoncode REASON-CODE was receivedfrom the bidirectional dataconversion MODULE-NAME whileprocessing member MEMBER-NAME of language structureSTRUCTURE-NAME.

ExplanationLanguage structure to XML conversion makes useof an external module to handle bidirectional dataconversions.



Symbolic Feedback CodeIBM0UG

IBM0977S Language structure to XMLconversion could not completein procedure PROCEDURE-NAMEbecause the length prefix in thelanguage structure STRUCTURE-NAME specified a length ofSPECIFIED-LENGTH bytes, whichis less than the structure'sminimum length of MINIMUM-LENGTH bytes.

ExplanationLanguage Structure to XML conversion detected thatthe length prefix of a language structure specified alength that is less than the minimum length of thestructure. The minimum length of a language structureis computed as the sum of the bytes consumed by allsubordinate fields.


Programmer responseCorrectly set the two-byte length prefix of eachlanguage structure in the language structure buffer.

Symbolic Feedback CodeIBM0UH


Chapter 7. COBOL runtime messages

Each COBOL runtime message is followed by an explanation that describes the condition causing themessages. A programmer response suggests how you might prevent the message from occurring againand a system action indicates how the system responds to the condition that caused the message areincluded.

The messages also contain a symbolic feedback code that represents the first 8 bytes of a 12-bytecondition token. You can think of the symbolic feedback code as the nickname for a condition. Assuch, the symbolic feedback code can be used in user-written condition handlers to screen for a givencondition, even if it occurs at different locations in an application.

The messages contain alphabetic suffixes that have the following meaning:I

Informational message.W

Warning message.E

Error message.S

Severe error message.C

Critical error message.

IGZ0002S debugging-information

ExplanationA SYNAD error has occurred on a QSAM file. The textwas supplied by the system SYNADAF routine. Sincethe debugging information supplied in this message issystem specific, the message format differs betweenCMS and MVS environments. The message issuedunder MVS consists of the following:

IGZ0002S job name, step name, unit address, device type, ddname, operation attempted, error description, actual track address and block number, access method.

The message issued under CMS is as follows:

IGZ0002S 120S operation type ERROR nnn ON ddname,

Definitions requiring further explanation for the abovemessage formats are:120S

is the CMS message number for SYNAD errorsoperation type

INPUT or OUTPUTdevice type

UR for unit record device

TAMagnetic tape device

DADirect access device

nnnis the associated error code

ddnameis the DDNAME of the related file

operation attemptedactual operation

System actionThe application was terminated.

Programmer responseFor more information regarding the CMS messagenumber 120S and related error codes, see z/VMCMS and REXX/VM Messages and Codes or z/VM CPMessages and Codes. For information on the MVS textof this SYNADAF message, see z/OS DFSMS MacroInstructions for Data Sets, and z/OS DFSMS Using DataSets.

Symbolic Feedback CodeIGZ002


IGZ0003W A logic error occurred for file file-name in program program-name atrelative location relative-location.

ExplanationThis error is usually caused by an I/O operationrequest that is not valid for the file—for example, aWRITE into a file opened for INPUT, or a START to aVSAM ESDS.

A file status clause was specified or an errordeclarative statement was active for the file.

System actionNo system action was taken.

Programmer responseCheck the operation request and modify the program.


IGZ0005S OS/VS COBOL programs in theapplication were found in multipleenclaves.

ExplanationOS/VS COBOL programs are restricted to one enclavewithin an application.


Programmer responseModify the application so that the OS/VS COBOLprograms appear in one enclave only.


IGZ0006S The reference to table table-nameby verb number verb-number online line-number addressed anarea outside the region of thetable.

ExplanationWhen the SSRANGE option is in effect, this messageis issued to indicate that a fixed-length table has beensubscripted in a way that exceeds the defined size of

the table, or, for variable-length tables, the maximumsize of the table.

The range check was performed on the compositeof the subscripts and resulted in an address outsidethe region of the table. For variable-length tables,the address is outside the region of the table definedwhen all OCCURS DEPENDING ON objects are at theirmaximum values; the ODO object's current value isnot considered. The check was not performed onindividual subscripts.


Programmer responseEnsure that the value of literal subscripts and/orthe value of variable subscripts as evaluated at run-time do not exceed the subscripted dimensions forsubscripted data in the failing statement.


IGZ0007S The size of variable lengthgroup group-name exceeded themaximum defined length of thegroup at the time of reference byverb number verb-number on lineline-number.

ExplanationWhen the SSRANGE option is in effect, this messageis issued to indicate that a variable-length groupgenerated by OCCURS DEPENDING ON has a lengththat is less than zero, or is greater than the limitsdefined in the OCCURS DEPENDING ON clauses. Therange check was performed on the composite lengthof the group, and not on the individual OCCURSDEPENDING ON objects.


Programmer responseEnsure that OCCURS DEPENDING ON objects asevaluated at run-time do not exceed the maximumnumber of occurrences of the dimension for tableswithin the referenced group item.



IGZ0009C A delete of module module-namewas unsuccessful.

ExplanationAn attempt to delete a module failed.


Programmer responseSee your IBM service representative.


IGZ0011C module-name was not aproper module for this systemenvironment.

ExplanationA library subroutine that is system sensitive isinappropriate for the current system environment. Forexample, an OS environment specific module has beenloaded under CICS. The likely causes are:

• Improper concatenation sequence of partitioneddata sets that contain the subroutine library, eitherduring run-time or during link-edit of the COBPAC.

• An attempt to use a function unsupported on thecurrent system (for example, ACCEPT on CICS).


Programmer responseCheck for the conditions stated above, and modify theenvironment or the application as needed.

Symbolic Feedback CodeIGZ00B

IGZ0012S There was an invalid attempt toend a sort or merge.

ExplanationA sort or merge initiated by a COBOL program was inprogress and one of the following was attempted:

1. A STOP RUN was issued.

2. A GOBACK or an EXIT PROGRAM was issuedwithin the input procedure or the output procedureof the COBOL program that initiated the sort ormerge. Note that the GOBACK and EXIT PROGRAMstatements are allowed in a program called by aninput procedure or an output procedure.

3. A user handler associated with the programthat initiated the sort or merge moved thecondition handler resume cursor and resumed theapplication.


Programmer responseChange the application so that it does not use one ofthe above methods to end the sort or merge.

Symbolic Feedback CodeIGZ00C

IGZ0013S An error return code return-codecame from a CICS commandCICS-command issued by librarysubroutine library-subroutine.

ExplanationAn error was encountered when a run-time routineissued a CICS command. The error return code isfrom the field EIBRESP in the CICS EIB. For moreinformation about the values for the field EIBRESP, seethe CICS/ESA Application Programmer's Reference ,SC33-0676.


Programmer responseModify your application as required.

Symbolic Feedback CodeIGZ00D

IGZ0014W module-name is no longersupported. Its content wasignored.

ExplanationThis message is issued when the run-time detects thatIGZETUN or IGZEOPT is linked with the application.

Chapter 7. COBOL runtime messages 511

IGZETUN and IGZEOPT are ignored when runningwith Language Environment. CEEUOPT may be usedin place of IGZETUN and IGZEOPT.


Programmer responseRemove the explicit INCLUDE of IGZEOPT or IGZETUNduring the link-edit step.

Symbolic Feedback CodeIGZ00E

IGZ0015S A recursive call was attempted toa program that was already active.The program name is program-name.

ExplanationAn illegal recursive entry to an active programis detected. For example, Program A has CALLedProgram B, and Program B is CALLing Program A.


Programmer responseRemove the recursive call to program-name orspecify the IS RECURSIVE phrase on the PROGRAM-ID statement for the recursively CALLed program.Additionally, if the recursive program is calleddynamically, link-edit it with REUS.

Symbolic Feedback CodeIGZ00F

IGZ0016W Program program-name could notbe deactivated by non-return exitof a routine. Subsequent reentry isnot supported.

ExplanationA COBOL program cannot normally be recursivelyentered. When non-return style procedure collapseprocessing is being performed for a COBOL program,an attempt is made to reset the program to a statewhere it can be recursively entered. This is notsupported for certain combinations of function usedwithin the program. After this message is issued, any

attempt to reenter the program will result in messageIGZ0015S and termination of the enclave.


Programmer responseDo not reenter the program or modify the program toallow it to be successfully reset.

Symbolic Feedback CodeIGZ00G

IGZ0017S The open of DISPLAY orACCEPT file with environmentname environment-name wasunsuccessful.

ExplanationAn error occurred while opening the DISPLAY/ACCEPTfile.


Programmer responseCheck to make sure a ddname has been defined forthe file.

Symbolic Feedback CodeIGZ00H

IGZ0018S On CICS, an attempt was madeto run a COBOL program which isnot reentrant. The program nameis program-name.

ExplanationCOBOL programs running on CICS must be reentrant.


Programmer responseIn order to make a COBOL program reentrant, compilethe COBOL program with the RENT compile-timeoption.


Symbolic Feedback CodeIGZ00I

IGZ0019W A FUNCTION result used asa DELIMITED BY operand islarger than the UNSTRING objectin program program-name atdisplacement displacement. TheDELIMITED BY phrase is ignored.

ExplanationA FUNCTION used as a DELIMITED BY operand waslarger than the UNSTRING object.


Programmer responseCheck the FUNCTION arguments to ensure that theyare not larger than the UNSTRING object.

Symbolic Feedback CodeIGZ00J

IGZ0020S A logic error occurred. NeitherFILE STATUS nor a declarativewas specified for file file-namein program program-name atrelative location relative-location.The status code was status-code.

ExplanationThis error is an I/O error, usually caused by anoperation request that is not valid for the file, forexample, a WRITE into a file opened for INPUT, ora START to a VSAM ESDS. No file status clause wasspecified, and no error declarative was in effect.


Programmer responseCheck operation request for the file.

Symbolic Feedback CodeIGZ00K

IGZ0021C macro-name was unsuccessful forfile file-name.

ExplanationThe execution of an ENDREQ, GENCB, MODCB,SHOWCB, or TESTCB macro failed. This is the resultof system or VSAM problems.



Symbolic Feedback CodeIGZ00L

IGZ0022W File file-name in program program-name will return the maximumrecord length when read.

ExplanationA VSAM RRDS with a varying record length has beenopened for input. The maximum record length will bereturned.



Symbolic Feedback CodeIGZ00M

IGZ0023S The dynamic allocation of filefile-name was unsuccessful. Thereturn code was return-code. Thereason code was reason-code.

ExplanationAn attempt to dynamically allocate a file usingDYNALLOC failed, resulting in the indicated return andreason codes.


Programmer responseReview the job stream or filedef to see if anyDDNAMES are missing or misspelled. If you can


not find any errors, resubmit the job with theCBLQDA(OFF) run-time option and check for anyaccess method messages.

Symbolic Feedback CodeIGZ00N

IGZ0024S An invalid separate sign characterwas detected in program-name atdisplacement displacement.

ExplanationAn operation was attempted on data defined with aseparate sign. The value in the sign position was not aplus (+) or a minus (-).


Programmer responseThis error might have occurred because of aREDEFINES clause involving the sign position or agroup move involving the sign position, or the positionwas never initialized. Check for these cases. Thecompiler formatting option TEST(), or equivalent, alongwith the ABTERMENC() run-time option, can be usedto generate a formatted dump of the user data. Thisdump can then be used to identify the unacceptabledata item contents.

Symbolic Feedback CodeIGZ00O

IGZ0026W The SORT-RETURN special registerwas never referenced, but thecurrent content indicated the sortor merge operation in programprogram-name on line numberline-number was unsuccessful.

ExplanationThe COBOL source does not contain any references tothe sort-return register. The compiler generates a testafter each sort or merge verb. A nonzero return codehas been passed back to the program by Sort/Merge.


Programmer responseDetermine why the Sort/Merge was unsuccessful andfix the problem. Possible reasons why the Sort/Mergewas unsuccessful include:

• There was an error detected by DFSORT. See theDFSORT messages for the reason for the error.

• The SORT-RETURN special register was set to a non-zero value by the application program while in aninput procedure or an output procedure.

Symbolic Feedback CodeIGZ00Q

IGZ0027W The sort control file could not beopened.

ExplanationAn attempt to open the sort control file has failed.Possible reasons for the open failure include:

• A ddname for the sort control file was not provided.• The IGZSRTCD ddname was provided, but the file

associated with the ddname could not be found.

When the sort control file cannot be opened, user-supplied sort control cards will not be passed to Sort/Merge.

The sort control file is optional. On MVS, if you didnot provide a ddname for the sort control file (the sortcontrol file name is IGZSRTCD unless it is overriddenby changing the value of the SORT-CONTROL specialregister) you will also get this message: IEC130I'IGZSRTCD DD STATEMENT MISSING'. This messageis informational only.


Programmer responseIf you want to pass in sort control cards from the sortcontrol file, verify that the ddname is specified and thefile is available.

Symbolic Feedback CodeIGZ00R

IGZ0028S An I/O error occurred in sortcontrol file file-name.


ExplanationAn I/O error was encountered while trying to read thesort control file. Some or all of the user-supplied sortcontrol cards will not be passed to Sort/Merge.


Programmer responseFor more information, look at the previous systemmessage you received relating to this I/O error.

Symbolic Feedback CodeIGZ00S

IGZ0029S Argument-1 for function function-name in program program-nameat line line-number was less thanzero.

ExplanationAn illegal value for argument-1 was used.


Programmer responseEnsure that argument-1 is greater than or equal tozero.

Symbolic Feedback CodeIGZ00T

IGZ0030S Argument-2 for function function-name in program program at lineline-number was not a positiveinteger.

ExplanationAn illegal value for argument-2 was used.


Programmer responseEnsure that argument-2 is a positive integer.

Symbolic Feedback CodeIGZ00U

IGZ0031S A restart was not possible sincethe checkpoint record record-namewas taken while a sort or mergewas in progress.

ExplanationAn attempt was made to use the restart facility ofcheckpoint/restart to resume execution of a job froma checkpoint taken by a COBOL program because ofa rerun clause during a Sort/Merge operation. Onlycheckpoints taken by the sort product can be used torestart from a point within the Sort/Merge operation.The checkpoint record cannot be used for restart.


Programmer responseUse a different checkpoint record. If no othercheckpoint records exist, the job cannot be restarted.

Symbolic Feedback CodeIGZ00V

IGZ0032S A CANCEL was attempted onactive program program-name.

ExplanationAn attempt was made to cancel an active program. Forexample, program A called program B; program B istrying to cancel program A.


Programmer responseRemove the failing CANCEL statement. In orderto locate the failing CANCEL statement, rerun theapplication with TERMTHDACT(TRACE) or (ABEND).Review the traceback information to identify theprogram that issued the CANCEL.


IGZ0033S An attempt was made to passa parameter address above 16


megabytes to AMODE(24) programprogram-name.

ExplanationAn attempt was made to pass a parameter locatedabove the 16-megabyte storage line to a program inAMODE(24). The called program will not be able toaddress the parameter.


Programmer responseIf the calling program is compiled with the RENToption, the DATA(24) option may be used in the callingprogram to make sure that its data is located instorage accessible to an AMODE(24) program. If thecalling program is compiled with the NORENT option,the RMODE(24) option may be used in the callingprogram to make sure that its data is located instorage accessible to an AMODE(24) program. Verifythat no linkedit, binder or genmod overrides areresponsible for this error.


IGZ0034W The file with system-name system-name could not be extended.Secondary extents were notspecified or were not available.The last WRITE was at offset offsetin program program-name.

ExplanationThere is insufficient space available for an output file.There is no invalid key clause, file status, or user errordeclarative. This corresponds to the MVS X37 ABEND.


Programmer responseCheck the file attributes and if necessary, reallocatethe file. Also check data set allocations.


IGZ0035S There was an unsuccessful OPENor CLOSE of file file-name in

program program-name at relativelocation location. Neither FILESTATUS nor an ERROR declarativewere specified. The status codewas status-code.

ExplanationAn error has occurred while opening or closing thenamed file. No file status or user error declarative wasspecified.


Programmer responseCheck to make sure there is a ddname defined for theindicated file.


IGZ0036W Truncation of high order digitpositions occurred in programprogram-name on line numberline-number.

ExplanationThe generated code has truncated an intermediateresult (that is, temporary storage used during anarithmetic calculation) to 30 digits; some of thetruncated digits were not 0.


Programmer responseSee COBOL for OS/390 & VM Programming Guideor COBOL for MVS & VM Programming Guide for adescription of intermediate results.


IGZ0037S The flow of control in programprogram-name proceeded beyondthe last line of the program.


ExplanationThe program did not have a terminator (STOP,GOBACK, or EXIT), and control fell through the lastinstruction.


Programmer responseCheck the logic of the program. Sometimes this erroroccurs because of one of the following logic errors:

• The last paragraph in the program was onlysupposed to receive control as the result of aPERFORM statement, but due to a logic error it wasbranched to by a GO TO statement.

• The last paragraph in the program was executed asthe result of a "fall-through" path, and there was nostatement at the end of the paragraph to end theprogram.


IGZ0038S A reference modification lengthvalue of reference-modification-value on line line-number whichwas not equal to 1 was found ina reference to data item data-itemwhich was passed by value.

ExplanationThe length value in a reference modificationspecification was not equal to 1. The length value mustbe equal to 1.


Programmer responseCheck the indicated line number in the program toensure that any reference modified length values are(or will resolve to) 1.


IGZ0039S An invalid overpunched signwas detected in program program-name on line line-number.

ExplanationAn operation was attempted on data defined with anoverpunched sign. The value in the sign was not valid.


Programmer responseThis error might have occurred because of aREDEFINES clause involving the sign position or agroup move involving the sign position, or the positionwas never initialized. Check for the above cases.


IGZ0040S An invalid separate sign wasdetected in program program-name on line line-number.

ExplanationAn operation was attempted on data defined with aseparate sign. The value in the sign position was not aplus (+) or a minus (-).


Programmer responseThis error might have occurred because of aREDEFINES clause involving the sign position or agroup move involving the sign position, or the positionwas never initialized. Check for the above cases.


IGZ0041W The warning message limitwas exceeded. Further warningmessages were suppressed.

ExplanationThe limit on warning messages is 256. This constrainton the number of warning messages prevents alooping program from flooding the system buffers.



Programmer responseCorrect the situations causing the warning messagesor correct the looping problem.


IGZ0042C There was an attempt to use theIGZBRDGE macro, but the callingprogram was not COBOL.

ExplanationA non-COBOL program attempted to call a COBOLprogram using the IGZBRDGE interface. COBOL/370could not find a COBOL environment.


Programmer responseDo not call an entry point specified via the IGZBRDGEmacro from a non-COBOL program.

Symbolic Feedback CodeIGZ01A

IGZ0044S There was an attempt to callthe COBOL main program program-name that was not in initial state.

ExplanationYou will receive this message if you attempt to entera NONREENTRANT COBOL/370, VS COBOL II, COBOLfor MVS & VM, or COBOL for OS/390 & VM mainprogram more than once. This is a nonstandard entryattempt.


Programmer responseModify the application so that the non-reentrantCOBOL main program won't be called more than once.


IGZ0045S Unable to invoke method method-name on line number line numberin COBOL program program-name.

ExplanationThe specific method is not supported for the class ofthe current object reference.


Programmer responseCheck the indicated line number in the program toensure that the class of the current object referencesupports the method being invoked.


IGZ0046W The value specified in the programfor the special-register specialregister was overridden by thecorresponding value in the sortcontrol file.

ExplanationA nondefault value for the SORT special registerspecified in the message was used in a program, buta value in the SORT control file which corresponds tothat SORT special register was found. The value in theSORT control file was used, and the value in the SORTspecial register was ignored.


Programmer responseSee COBOL for OS/390 & VM Programming Guideor COBOL for MVS & VM Programming Guide for adescription of SORT special registers and the SORTcontrol file.


IGZ0047S Unable to invoke method method-name on line number line numberin COBOL class class-name.

ExplanationThe specific method is not supported for the class ofthe current object reference.



Programmer responseCheck the indicated line number in the class to ensurethat the class of the current object reference supportsthe method being invoked.


IGZ0048W A negative base was raisedto a fractional power inan exponentiation expressionin program program-name atdisplacement displacement. Theabsolute value of the base wasused.

ExplanationA negative number raised to a fractional poweroccurred in a library routine. The value of a negativenumber raised to a fractional power is undefined inCOBOL. If a SIZE ERROR clause had appeared on thestatement in question, the SIZE ERROR imperativewould have been used. However, no SIZE ERRORclause was present, so the absolute value of the basewas used in the exponentiation.


Programmer responseEnsure that the program variables in the failingstatement have been set correctly.


IGZ0049W A zero base was raisedto a zero power in anexponentiation expression inprogram program-name atdisplacement displacement. Theresult was set to one.

ExplanationThe value of zero raised to the power zero occurred ina library routine. The value of zero raised to the powerzero is undefined in COBOL. If a SIZE ERROR clausehad appeared on the statement in question, the SIZE

ERROR imperative would have been used. However, noSIZE ERROR clause was present, so the value returnedwas one.




IGZ0050S A zero base was raisedto a negative power inan exponentiation expressionin program program-name atdisplacement displacement.

ExplanationThe value of zero raised to a negative power occurredin a library routine. The value of zero raised to anegative number is not defined. If a SIZE ERRORclause had appeared on the statement in question,the SIZE ERROR imperative would have been used.However, no SIZE ERROR clause was present.




IGZ0051S An invalid EBCDIC digit stringwas detected on conversion tofloating point in program-name atdisplacement displacement.

ExplanationThe input to the conversion routine contained invalidEBCDIC data.





IGZ0052C An internal error or invalidparameters were detected in thefloating point conversion routinecalled from program-name atdisplacement displacement.

ExplanationNone




IGZ0053S An overflow occurred onconversion to floating point inprogram-name at displacementdisplacement.

ExplanationA number was generated in the program that is toolarge to be represented in floating point.


Programmer responseYou need to modify the program appropriately to avoidan overflow.


IGZ0054W An overflow occurred onconversion from floating point tofixed point in program-name atdisplacement displacement. Theresult was truncated.

ExplanationThe result of a conversion to fixed point from floatingpoint contains more digits than will fit in the fixed pointreceiver. The high order digits were truncated.


Programmer responseNo action is necessary, although you may want tomodify the program to avoid an overflow.


IGZ0055W An underflow occurred onconversion to floating point inprogram-name at displacementdisplacement. The result was setto zero.

ExplanationOn conversion to floating point, the negative exponentexceeded the limit of the hardware. The floating pointvalue was set to zero.


Programmer responseNo action is necessary, although you may want tomodify the program to avoid an underflow.


IGZ0056W One or more files were not closedby program program-name beforeprogram termination.

ExplanationThe specified program has finished but has not closedall of the files it opened. COBOL attempts to clean upstorage and closes any open files.



Programmer responseCheck that all files are closed before the programterminates.


IGZ0057S There was an attempt to initializea reusable environment throughILBOSTP0, but either the enclavewas not the first enclave or COBOLwas not the main program of thealready established enclave.

ExplanationA request to establish a reusable environment throughILBOSTP0 can only occur at the beginning of theapplication. Examples when this error can occur:

• PL/I program calls ASSEMBLE program which callsILBOSTP0.

• Language Environment enabled ASSEMBLERprogram calls ILBOSTP0.


Programmer responseOnly invoke ILBOSTP0 before calling any programwithin the application that brings up LanguageEnvironment.

Symbolic Feedback CodeIGZ01P

IGZ0058S Exponent overflow occurredin program program-name atdisplacement displacement.

ExplanationFloating point exponent overflow occurred in a libraryroutine.




IGZ0059W An exponent with more than ninedigits was truncated in programprogram-name at displacementdisplacement.

ExplanationExponents in fixed point exponentiations may notcontain more than nine digits. The exponent wastruncated back to nine digits; some of the truncateddigits were not 0.


Programmer responseNo action is necessary, although you may want toadjust the exponent in the failing statement.


IGZ0060W Truncation of high order digitpositions occurred in programprogram-name at displacementdisplacement.

ExplanationCode in a library routine has truncated an intermediateresult (that is, temporary storage used during anarithmetic calculation) back to 30 digits; some of thetruncated digits were not 0.


Programmer responseSee COBOL for OS/390 & VM Programming Guideor COBOL for MVS & VM Programming Guide for adescription of intermediate results.


IGZ0061S Division by zero occurredin program program-name atdisplacement displacement.


ExplanationDivision by zero occurred in a library routine. Divisionby zero is not defined. If a SIZE ERROR clause hadappeared on the statement in question, the SIZEERROR imperative would have been used. However, noSIZE ERROR clause was present.




IGZ0063S An invalid sign was detected ina numeric edited sending fieldin program-name on line numberline-number.

ExplanationAn attempt has been made to move a signed numericedited field to a signed numeric or numeric editedreceiving field in a MOVE statement. However, the signposition in the sending field contained a character thatwas not a valid sign character for the correspondingPICTURE.




IGZ0064S A recursive call to active programprogram-name in compilation unitcompilation-unit was attempted.

ExplanationCOBOL does not allow reinvocation of an internalprogram which has begun execution, but has not yetterminated. For example, if internal programs A and Bare siblings of a containing program, and A calls B andB calls A, this message will be issued.


Programmer responseExamine your program to eliminate calls to activeinternal programs or specify the IS RECURSIVE phraseon the PROGRAM-ID statement for the recursivelyCALLed program.


IGZ0065S A CANCEL of active programprogram-name in compilation unitcompilation-unit was attempted.

ExplanationAn attempt was made to cancel an active internalprogram. For example, if internal programs A and Bare siblings in a containing program and A calls B andB cancels A, this message will be issued.


Programmer responseExamine your program to eliminate cancellation ofactive internal programs.


IGZ0066S The length of external data recorddata-record in program program-name did not match the existinglength of the record.

ExplanationWhile processing External data records during programinitialization, it was determined that an External datarecord was previously defined in another program inthe run-unit, and the length of the record as specifiedin the current program was not the same as thepreviously defined length.



Programmer responseExamine the current file and ensure the External datarecords are specified correctly.


IGZ0067S The NOEQUALS keyword inthe sort control file file-nameconflicted with the specificationsof the DUPLICATES phrase on theSORT statement.

ExplanationA sort control file with an OPTION card specifyingthe NOEQUALS keyword was used for a SORT whichhad the DUPLICATES IN ORDER phrase specified.The NOEQUALS keyword and the DUPLICATES phraseconflict.


Programmer responseEither remove the NOEQUALS keyword from the sortcontrol file or remove the DUPLICATES IN ORDERphrase from the SORT statement.


IGZ0068W Duplicate characters wereignored in an INSPECTCONVERTING statement inprogram program-name atdisplacement displacement.

ExplanationThe same character appeared more than once inthe identifier that contained the characters to beconverted in an INSPECT CONVERTING statement.The first occurrence of the character, and thecorresponding character in the replacement field, areused, and subsequent occurrences are not used.


Programmer responseDuplicate characters in the indicated INSPECTstatement may be deleted; programmer action is notrequired.


IGZ0069S On VM, file file-name in programprogram-name attempted to useVSAM in XA or ESA mode. UsingVSAM while in XA or ESA mode isnot supported under the installedlevel of VM. The program wasterminated.

ExplanationVSAM can only operate in S/370 mode virtualmachines on VM/SP XA and VM/ESA Release 1 ESAfeature. The job was cancelled. Only on VM/ESARelease 1.1 (CMS8), and higher releases, can VSAMand VS COBOL II be used in XA-mode and XC-modevirtual machines.


Programmer responseSee your systems programmer for assistance.


IGZ0070S The FILEDEF command "FILEDEFddname DISK FILE ddname A4"was unsuccessful.

ExplanationAn attempt at dynamic allocation for CMS file ddnameusing the FILEDEF command has failed.





IGZ0071S ALL subscripted table reference totable table-name by verb numberverb-number on line line-numberhad an ALL subscript specifiedfor an OCCURS DEPENDING ONdimension, and the object was lessthan or equal to 0.

ExplanationWhen the SSRANGE option is in effect, this messageis issued to indicate that there are 0 occurrences ofdimension subscripted by ALL.

The check is performed against the current value ofthe OCCURS DEPENDING ON OBJECT.


Programmer responseEnsure that ODO object(s) of ALL-subscripteddimensions of any subscripted items in the indicatedstatement are positive.


IGZ0072S A reference modification startposition value of reference-modification-value on line line-number referenced an area outsidethe region of data item data-item.

ExplanationThe value of the starting position in a referencemodification specification was less than 1, or wasgreater than the current length of the data item thatwas being reference modified. The starting positionvalue must be a positive integer less than or equalto the number of characters in the reference modifieddata item.


Programmer responseCheck the value of the starting position in thereference modification specification.


IGZ0073S A non-positive referencemodification length value ofreference-modification-value online line-number was found in areference to data item data-item.

ExplanationThe length value in a reference modificationspecification was less than or equal to 0. The lengthvalue must be a positive integer.


Programmer responseCheck the indicated line number in the program toensure that any reference modified length values are(or will resolve to) positive integers.


IGZ0074S A reference modification startposition value of reference-modification-value and lengthvalue of length on line line-numbercaused reference to be madebeyond the rightmost character ofdata item data-item.

ExplanationThe starting position and length value in a referencemodification specification combine to address an areabeyond the end of the reference modified data item.The sum of the starting position and length valueminus one must be less than or equal to the number ofcharacters in the reference modified data item.


Programmer responseCheck the indicated line number in the program toensure that any reference modified start and lengthvalues are set such that a reference is not madebeyond the rightmost character of the data item.



IGZ0075S Inconsistencies were foundin EXTERNAL file file-namein program program-name.The following file attributesdid not match those ofthe established external file:attribute-1 attribute-2 attribute-3attribute-4 attribute-5 attribute-6attribute-7

ExplanationOne or more attributes of an external file did not matchbetween two programs that defined it.


Programmer responseCorrect the external file. For a summary of fileattributes which must match between definitions ofthe same external file, see IBM COBOL LanguageReference


IGZ0076W The number of charactersin the INSPECT REPLACINGCHARACTERS BY data-namein program program-name atdisplacement displacement wasnot equal to one. The firstcharacter was used.

ExplanationA data item which appears in a CHARACTERS phrasewithin a REPLACING phrase in an INSPECT statementmust be defined as being one character in length.Because of a reference modification specification forthis data item, the resultant length value was not equalto one. The length value is assumed to be one.


Programmer responseYou may correct the reference modificationspecifications in the failing INSPECT statement toensure that the reference modification length is (or willresolve to) 1; programmer action is not required.


IGZ0077W The lengths of the data-itemitems in program program-name atdisplacement displacement werenot equal. The shorter length wasused.

ExplanationThe two data items which appear in a REPLACING orCONVERTING phrase in an INSPECT statement musthave equal lengths, except when the second suchitem is a figurative constant. Because of the referencemodification for one or both of these data items, theresultant length values were not equal. The shorterlength value is applied to both items, and executionproceeds.


Programmer responseYou may adjust the operands of unequal length in thefailing INSPECT statement; programmer action is notrequired.


IGZ0078S ALL subscripted table reference totable table-name by verb numberverb-number on line line-numberwill exceed the upper bound of thetable.

ExplanationWhen the SSRANGE option is in effect, this messageis issued to indicate that a multi-dimension table withALL specified as one or more of the subscripts willresult in a reference beyond the upper limit of thetable.

The range check was performed on the compositeof the subscripts and the maximum occurrences forthe ALL subscripted dimensions. For variable-lengthtables the address is outside the region of the tabledefined when all OCCURS DEPENDING ON objects areat their maximum values; the ODO object's currentvalue is not considered. The check was not performedon individual subscripts.



Programmer responseEnsure that OCCURS DEPENDING ON objects asevaluated at run-time do not exceed the maximumnumber of occurrences of the dimension for tableitems referenced in the failing statement.


IGZ0079S On CICS, program-lang programprogram-name attempted to callOS/VS COBOL program program-name.

ExplanationOn CICS, a COBOL/370, VS COBOL II, COBOL forMVS & VM, or COBOL for OS/390 & VM programattempted to call an OS/VS COBOL program with theCALL statement. Using the CALL statement to performcalls between the following are not not supported onCICS:

• COBOL for OS/390 & VM programs and OS/VSCOBOL programs

• COBOL for MVS & VM programs and OS/VS COBOLprograms

• COBOL/370 programs and OS/VS COBOL programs• VS COBOL II programs and OS/VS COBOL programs


Programmer responseIf you need to invoke an OS/VS COBOL program froma COBOL/370, VS COBOL II, COBOL for MVS & VM,or COBOL for OS/390 & VM program use EXEC CICSLINK.


IGZ0080S A dynamic call to module-namefailed because the program entryname program-name does notmatch.

ExplanationIf a program compiled withthe PGMNAME(LONGUPPER) or thePGMNAME(LONGMIXED) option is dynamically called,the program name must be identical to the name ofthe module that contains it. If an alternate entry nameis called, the entry name must be identical to theALIAS name representing that entry point. Note thatthe program entry name can not exceed 8 bytes andmust be entirely upper-case.


Programmer responseThe name of the program failing the dynamic callmust be modified to comply with the rules statedabove. Otherwise, only static calls to the program arepermitted.


IGZ0096C A load of module module-namewas unsuccessful.

ExplanationAn attempt to load a module failed. The module wasnot available or a system load failure occurred.




IGZ0097S Argument-1 for function function-name in program program-nameat displacement displacementcontained no digits.

ExplanationArgument-1 for the indicated function must contain atleast 1 digit.



Programmer responseAdjust the number of digits in Argument-1 in the failingstatement.


IGZ0098C The message text for messagemessage-number was inaccessibleto IGZCWTO.

ExplanationThe message text module used by IGZCWTO didnot contain message text for the indicated messagenumber.




IGZ0099C Internal error error-code wasdetected in module module-name.

ExplanationAn unrecoverable error was detected in run-timemodule module-name.

When the module name in the message is IGZCXCC,the error-code indicates the error as described below:

Error-codeDescription

1The COBOL environment is not initialized. TheCOBOL environment must be initialized beforecalling IGZCXCC.

2An invalid function code was passed to IGZCXCC.

3An invalid name length was passed to IGZCXCC.

4IGZCXCC detected that a nested enclave should becreated.

5IGZCXCC cannot be called when running on CICS.

When the module name in the message is IGZCLNC,IGZCLNK, or IGZCFCC, the error-code indicates theerror as described below:


9IGZCXCC is being used and an invalid cancel wasattempted.

When the module name in the message is IGZEINI,the error-code indicates the error as described below:


101There was an attempt to initialize a VS COBOL II orOS/VS COBOL program as a subprogram before themain program has run.

102An OS/VS COBOL program is being initialized butthe TGT address was not passed.

When the module name in the message is IGZCII1, theerror-code indicates the error as described below:Error-code

DescriptionNOTMAIN1

Subprogram initialization occurred when mainprogram initialization was expected.

MAINCLASCOBOL class initialization occurred when mainprogram initialization was expected.

INVSTRC1Invalid threading status.

INVST001Invalid program initialization state.



PGMIIP01Program initialization occurred when anotherprogram was in the process of being initialized.

When the module name in the message is IGZCII2, theerror-code indicates the error as described below: :Error-code

DescriptionINVSIG01

During class initialization, the initialization in-progress count is negative.


INVSIG02During program initialization, the initialization in-progress count is not one.

INVSIG03During program initialization, the initialization in-progress count is not zero.





IGZ0100S Argument-1 for function functionin program program atdisplacement displacement wasless than or equal to -1.

ExplanationAn illegal value was used for Argument-1.


Programmer responseEnsure that argument-1 is greater than -1.


IGZ0108S The cancel of program program-name failed because the moduleload point address was notprovided when the program wasloaded.

ExplanationIn a Language Environment/370 preinitializedenvironment users may specify their own load serviceroutine. If this routine fails to provide the module loadpoint address as an output parameter when loadinga COBOL program, that program can not be cancelledusing COBOL'S CANCEL statement.


Programmer responseModify the user load service to provide the moduleload point address.


IGZ0151S Argument-1 for function function-name in program program-nameat displacement displacementcontained more than 18 digits.

ExplanationThe total number of digits in argument-1 of theindicated function exceeded 18 digits.


Programmer responseAdjust the number of digits in argument-1 in the failingstatement.


IGZ0152S Invalid character character wasfound in column column-number inargument-1 for function function-name in program program-name at displacement program-displacement.

ExplanationA non-digit character other than a decimal point,comma, space or sign (+,-,CR,DB) was found inargument-1 for NUMVAL/NUMVAL-C function.


Programmer responseCorrect argument-1 for NUMVAL or NUMVAL-C in theindicated statement.



IGZ0153S Program program-name wascompiled with a level of thecompiler that requires serviceto be installed on z/OS or onthe COBOL runtime component ofLanguage Environment, or both.Contact COBOL support for furtherassistance.

ExplanationAn attempt was made to run a program that wascompiled with a release or service level of the compilerthat requires maintenance to be installed on z/OSor on the COBOL runtime component of LanguageEnvironment, or both, but that maintenance has notbeen installed.


Programmer responseContact your system programmer to ensure thatthe corresponding COBOL runtime componentof Language Environment maintenance and z/OSmaintenance was installed as was indicated in therecent COBOL compiler version or maintenance thatwas installed. Contact COBOL support for furtherassistance.


IGZ0154S A procedure pointer was set tonested program nested-program-name in program program-name atdisplacement displacement.

ExplanationProcedure pointers can not be set to a nestedprogram.


Programmer responseMake sure that the procedure program is set to anexternal program.


IGZ0155S Invalid character character wasfound in column column-number inargument-2 for function function-name in program program-name at displacement program-displacement.

ExplanationIllegal character was found in argument-2 forNUMVAL-C function.


Programmer responseCheck that the function argument does follow thesyntax rules.


IGZ0156S Argument-1 for function function-name in program program-nameat line line-number was less thanzero or greater than 28.

ExplanationInput argument to function FACTORIAL is greater than28 or less than 0.


Programmer responseCheck that the function argument is only one bytelong.


IGZ0157S The length of Argument-1 forfunction function-name in programprogram-name at line line-numberwas not equal to 1.

ExplanationThe length of input argument to ORD function is not 1.



Programmer responseCheck that the function argument is only one bytelong.


IGZ0158S The length of Argument-1 forfunction function-name in programprogram-name at displacementdisplacement was zero.

ExplanationThe length of the argument of the REVERSE, theUPPER-CASE or the LOWER-CASE function is zero.


Programmer responseMake sure that the length of the argument is greaterthan zero.


IGZ0159S Argument-1 for function function-name in program program-name atline line-number was less than 1 orgreater than 3067671.

ExplanationThe input argument to DATE-OF-INTEGER or DAY-OF-INTEGER function is less than 1 or greater than3067671.


Programmer responseCheck that the function argument is in the valid range.


IGZ0160S Argument-1 for function function-name in program program-nameat line line-number was lessthan 16010101 or greater than99991231.

ExplanationThe input argument to function INTEGER-OF-DATE isless than 16010101 or greater than 99991231.




IGZ0161S Argument-1 for function function-name in program program-nameat line line-number was less than1601001 or greater than 9999365.

ExplanationThe input argument to function INTEGER-OF-DAY isless than 1601001 or greater than 9999365.




IGZ0162S Argument-1 for function function-name in program program-nameat line line-number was less than1 or greater than the number ofpositions in the program collatingsequence.

ExplanationThe input argument to function CHAR is less than1 or greater than the highest ordinal position in theprogram collating sequence.





IGZ0163S Argument-1 for function function-name in program program-nameat line line-number was less thanzero.

ExplanationThe input argument to function RANDOM is less than0.


Programmer responseCorrect the argument for function RANDOM in thefailing statement.


IGZ0164C module-name was unable to getHEAP storage.

ExplanationThe request made to obtain heap storage failed.




IGZ0165S A reference modification startposition value of start-position-value on line line referenced anarea outside the region of thefunction result of function-result.

ExplanationThe value of the starting position in a referencemodification specification was less than 1, or wasgreater than the current length of the function resultthat was being reference modified. The startingposition value must be a positive integer less than orequal to the number of characters in the referencemodified function result.


Programmer responseCheck the value of the starting position in thereference modification specification and the length ofthe actual function result.


IGZ0166S A non-positive referencemodification length value of lengthon line line-number was found in areference to the function result offunction-result.

ExplanationThe length value in a reference modificationspecification for a function result was less than orequal to 0. The length value must be a positive integer.


Programmer responseCheck the length value and make appropriatecorrection.


IGZ0167S A reference modification startposition value of start-position andlength value of length on lineline-number caused reference tobe made beyond the rightmostcharacter of the function result offunction-result.


ExplanationThe starting position and length value in a referencemodification specification combine to address an areabeyond the end of the reference modified functionresult. The sum of the starting position and lengthvalue minus one must be less than or equal tothe number of characters in the reference modifiedfunction result.


Programmer responseCheck the length of the reference modificationspecification against the actual length of the functionresult and make appropriate corrections.


IGZ0168S The creation of a second enclavewithin a reusable environmentwas attempted. The first programof the second enclave wasprogram-name.

ExplanationReusable environment support is limited to a singleenclave. The enclave must be the first enclave.


Programmer responseModify the application so that it can run within asingle enclave with the COBOL reusable environment.If the program name printed is "????????" then the firstprogram of the second enclave is not COBOL.


IGZ0169W External data data-record wasallocated within the 31-bitaddress range. The calledprogram program-name containeda definition for this external data,and it was compiled with theDATA(24) option.

ExplanationExternal data was allocated ANYWHERE within the 31-bit addressing range by a program. But a subsequentlycalled program containing a definition for that sameexternal data was compiled with the DATA(24) option.This was discovered while processing external datarecords during program initialization.


Programmer responseRe-compile program with the DATA(31) option ifappropriate. If the external data needs to be allocatedbelow 16M, then the FIRST program in the rununitthat contains a definition of the external data must becompiled with the DATA(24) option.


IGZ0170S One or more files were not closedby NORENT program program-name and the program cannot befound in storage.

ExplanationThe specified NORENT program has not closed all ofthe files it opened and the program cannot be found instorage. COBOL is unable to close the files because therequired control blocks which reside in the programare no longer available. Unpredictable results willoccur when the system attempts to close the files. Thiserror can occur if the application has an assemblerprogram that loads and deletes the specified NORENTprogram.


Programmer responseEnsure that all files are closed by the NORENTprogram.


IGZ0171S An attempt was made byprogram program-name to openVSAM variable-length relativerecord file file-name but the file


was not defined to VSAM asRRDS. The COBOL variable-lengthrelative record data set simulationprovided by SIMVRD is no longersupported.

ExplanationThe SIMVRD run-time option can no longer be usedto provide simulation of VSAM variable-length RRDS inprograms compiled with Enterprise COBOL V4R1 andlater.


Programmer responseChange the file to a VSAM variable-length RRDS fileand use native VSAM support for variable-length RRDSdata sets.


IGZ0172W RTEREUS was specified, butignored. A reusable run-timeenvironment was not establishedbecause the first program in theapplication was not COBOL.

ExplanationA reusable environment can be established only whenthe main program of the first enclave is COBOL.


Programmer responseEnsure that RTEREUS is off. The performance benefitsof using RTEREUS are available without the run-timeoption when the application is running under LanguageEnvironment.


IGZ0173S There was an invalid attempt tostart a sort or merge.

ExplanationA sort or merge initiated by a COBOL program wasalready in progress when another sort or merge wasattempted by another COBOL program. Only one sortor merge can be active at a time.


Programmer responseChange the application so that it does not initiateanother sort or merge from within the COBOL sortexists.


IGZ0174S A dynamic call to module-namefailed because the load module isa DLL.

ExplanationA COBOL dynamic call cannot be made to a loadmodule that is a DLL. A load module that is a DLLcontains one or more of the following:

• A COBOL for OS/390 & VM program compiled withthe DLL option and the EXPORTALL option.

• A C routine compiled with the DLL option thatexports functions or variables.

• A C++ routine that exports functions or variables.


Programmer responseChange the dynamically called load module so thatit does not contain routines that export functionsor variables. If the load module contains COBOL forOS/390 & VM programs compiled with the DLL andthe EXPORTALL options, recompile the programs withNOEXPORTALL.


IGZ0175S A dynamic call to module-namefailed because the entry point is aCOBOL program compiled with theDLL compiler option.


ExplanationA COBOL dynamic call cannot be made to a COBOL forOS/390 & VM program that is compiled with the DLLcompiler option.


Programmer responseCompile the COBOL for OS/390 & VM program with theNODLL compiler option.


IGZ0176S A call from a COBOL programcompiled with the DLL compileroption failed because the programprogram-name was previouslydynamically called by a COBOLprogram compiled without the DLLcompiler option.

ExplanationWhen dynamically calling a COBOL program, insurethat the DLL compiler option is consistent betweencalling and called programs.


Programmer responseCompile both the calling and called COBOL for OS/390& VM programs with either the DLL or the NODLLcompiler option.


IGZ0177S A CANCEL of DLL program-name isnot allowed.

ExplanationThe program was called with a CALL identifierstatement from a COBOL program compiled with theDLL option. This caused the called program to beidentified as a DLL. A DLL cannot be cancelled.


Programmer responseDo not request that a DLL be cancelled.


IGZ0178S An attempt to find programprogram-name in DLL module-name was unsuccessful.

ExplanationAn error during the load of a DLL or during a queryDLL function request prevented an entry point addressfrom being returned.


Programmer responseSee the corresponding CEEnnnnI message foradditional information and the details of the problem.If the CEEnnnn message is not found in the MSGFILEinsure that the runtime option INFOMSGFILTER is OFF.


IGZ0179S A dynamic call to module-namefailed because the load modulecontains one or more routines withXPLINK linkage.

ExplanationA COBOL dynamic call cannot be made to a loadmodule that contains routines with XPLINK linkage.


Programmer responseChange the dynamically called load module so that itdoes not contain routines that use XPLINK linkage.



IGZ0180S An attempt was made to run aVS COBOL II or OS/VS COBOLprogram in a OS/390 UNIXprocess. The program name isprogram-name.

ExplanationVS COBOL II and OS/VS COBOL programs cannot berun in a z/OS UNIX process.


Programmer responseCompile the program with COBOL for MVS & VM orCOBOL for OS/390 & VM.


IGZ0181S An attempt was made to runa COBOL program that is notreentrant in a OS/390 UNIXprocess. The program name isprogram-name.

ExplanationCOBOL programs running in a z/OS UNIX process mustbe reentrant.


Programmer responseIn order to make a COBOL program reentrant, compilethe COBOL program with the RENT compile-timeoption.


IGZ0182W A fork() is not allowed when aCOBOL reusable environment isactive.

ExplanationA COBOL reusable environment is active and the fork()function was called. A COBOL reusable environment isestablished by doing one of the following:

• Using the RTEREUS run-time option• Calling ILBOSTP0• Calling IGZERRE


Programmer responseChange the application so that a COBOL reusableenvironment is not used.


IGZ0183W A fork() is not allowed whenan OS/VS COBOL program or aVS COBOL II program is in theenvironment.

ExplanationAt least one OS/VS COBOL program or VS COBOL IIprogram is in the environment and the fork() functionwas called.


Programmer responseCompile all OS/VS COBOL programs and the VS COBOLII programs with COBOL for MVS & VM or COBOL forOS/390 & VM.


IGZ0184W A fork() is not allowed when a sortor merge is in progress.

ExplanationA SORT or MERGE statement is in progress and thefork() function was called.


Programmer responseChange the application to call fork() when sort ormerge is not active.



IGZ0185W A fork() is not allowed when adeclarative in a COBOL program isactive.

ExplanationA declarative in a COBOL program is active and thefork() function was called.


Programmer responseChange the application to call fork() when a declarativeis not active.


IGZ0186S An attempt was made to run aVS COBOL II program with therun-time option XPLINK(ON). Theprogram name is program-name.

ExplanationRun-time option XPLINK(OFF) must be specified to runVS COBOL II programs.


Programmer responseSet the XPLINK run-time option to OFF and removeany load modules from the application that useXPLINK linkage, or compile the COBOL program withCOBOL for MVS & VM or COBOL for OS/390 & VM.


IGZ0187S There was an attempt toestablish a COBOL reusableenvironment with the run-timeoption XPLINK(ON).

ExplanationA COBOL reusable environment cannot be establishedwhen the XPLINK(ON) run-time option is specified. A

COBOL reusable environment is established by doingone of the following:



Programmer responseSet the XPLINK run-time option to OFF and removeany load modules from the application that useXPLINK linkage, or do not use a COBOL reusableenvironment.


IGZ0188S Value string is invalidfor environment variable_IGZ_SYSOUT.

ExplanationAllowable values for environment variable_IGZ_SYSOUT are "stdout" or "stderr". Value can beany combination of upper and lower case and must notcontain leading or trailing spaces.


Programmer responseChange value to be either "stdout" or "stderr".


IGZ0189S Program program-name cannotbe run in this operating systemenvironment.

ExplanationThe program contains features that are not supportedin this operating system environment. For example,when running on CMS, the following features are notsupported:

• programs compiled with the DLL compiler option• programs compiled with the ARITH(EXTEND)

compiler option


• programs compiled with Enterprise COBOL for z/OSand OS/390 V3R1 and later


Programmer responseModify the program to use supported features for theenvironment or run the program in the appropriateenvironment.


IGZ0190S There was an attempt to parse anXML document with an ENCODINGphrase that specified an invalidCCSID.

ExplanationThe CCSID value must be a positive integer between 1and 65,535 inclusive.


Programmer responseCorrect the ENCODING phrase of the XML PARSEstatement.


IGZ0191S There was an attempt to parsean XML document in a nationaldata item but with an ENCODINGphrase that specified a CCSIDother than 1200.

ExplanationThe CCSID value for parsing a national document mustbe 1200.




IGZ0192S There was an attempt to parse anXML document in an alphanumericdata item but with an ENCODINGphrase that specified CCSID 1200.

ExplanationThe CCSID value for parsing an alphanumericdocument must be 1208 (Unicode UTF-8), one ofthe supported EBCDIC CCSIDs, or, if the RETURNINGNATIONAL phrase was specified, any CCSID that canbe converted to CCSID 1200 (national).




IGZ0193W Search argument argument-number in the WHEN phrase ofthe SEARCH ALL statement inprogram program-name on linenumber line-number was a signeditem with a negative value. Thecorresponding table key wasan unsigned item, and so theargument could never match thekey in any of the table entries.

ExplanationThe SEARCH ALL statement specified a searchargument that was a signed item with a negative sign.The table key was an unsigned numeric item, and sothe comparison of the argument and the keys wouldalways be unequal. Hence the SEARCH ALL statementcould never succeed in locating a matching table entry.


Programmer responseEnsure that the search argument is correctly initializedbefore issuing the SEARCH ALL statement. For anunsigned table key, a numeric argument must either


be unsigned or have a positive sign for the searchstatement to have a possibility of successfully finding amatching table entry.


IGZ0194W Search argument argument-number in the WHEN phrase ofthe SEARCH ALL statement inprogram program-name on linenumber line-number was longerthan the corresponding key. Theexcess digit or character positionsof the argument were not zerosor spaces respectively, and so theargument could never match thekey in any of the table entries.

ExplanationThe SEARCH ALL statement specified a searchargument that was longer than the table key, andsince the excess digits or characters were not zeros orspaces respectively, the comparison of the argumentand the keys would always be unequal. Hencethe SEARCH ALL statement could never succeed inlocating a matching table entry.


Programmer responseInitialize the excess argument positions to zeros orblanks as appropriate before issuing the SEARCH ALLstatement. Alternatively, use a MOVE statement tomove the argument to a shorter temporary variable totruncate the excess argument positions, then use thattemporary variable as the SEARCH ALL argument.


IGZ0195S A SORT or MERGE statement wasattempted when running in anOS/390 UNIX process.

ExplanationSORT and MERGE statements are not supported whenrunning in a z/OS UNIX process.


Programmer responseRemove the SORT or MERGE statements from theapplication or run the program in a z/OS environment.


IGZ0196S Argument-1 for function function-name in program program-nameat displacement displacementcontained more than 31 digits.

ExplanationThe total number of digits in argument-1 of theindicated function exceeded 31 digits.


Programmer responseAdjust the number of digits in argument-1 in the failingstatement.


IGZ0197S There was an unsuccessful READor WRITE of file file-name inprogram program-name at relativelocation location Neither FILESTATUS nor an ERROR declarativewere specified. The file statuscode was status-code. The BPXreturn code was return-code. TheBPX reason code was reason-code.

ExplanationAn error has occurred while reading or writing thenamed file. No file status or user error declarative wasspecified.


Programmer responseFor additional information on the return-codeand reason-code, see z/OS UNIX System ServicesProgramming: Assembler Callable Services Reference,SC23-3020, topics for read (BPX1RED) and write(BPX1WRT).



IGZ0198W File file-name in program program-name had a block size of block-size which exceeds the maximumsupported block size.

ExplanationThe program file description specified a block sizethat exceeds the maximum supported block size. TheOPEN statement failed.

System actionIf a file status or error declarative was specified forthe file, no system action is performed. If neither a filestatus nor an error declarative was specified for thefile, the program is terminated and message IGZ0035Sis generated.

Programmer responseEnsure that the block size specified in the BLOCKCONTAINS clause is supported for the file, for thedevice that the dataset resides on and for theoperating system level being used.


IGZ0199S An attempt was made to run aCOBOL program that was compiledwith the SEPARATE suboption ofthe TEST compiler option. Thisis not supported with this levelof Language Environment or thislevel of Debug Tool. The programname is program-name.

ExplanationCOBOL programs running with TEST(,,SEPARATE) mustrun on levels of Language Environment and Debug Toolthat support it. This error can occur with any of thefollowing:

• running with a level of Language Environment thatdoes not support the SEPARATE suboption

• running with a level of Language Environment thatcould support the SEPARATE suboption but does nothave current maintenance applied

• running with a level of Debug Tool that could supportthe SEPARATE suboption but does not have currentmaintenance applied


Programmer responseRun the program under levels of LanguageEnvironment and Debug Tool that support programscompiled with TEST(,,SEPARATE) or recompile theCOBOL program without the SEPARATE suboption ofthe TEST compiler option.


IGZ0200W A file attribute mismatch wasdetected. File file-name inprogram program-name wasdefined as a physical sequentialfile and the file specified in theASSIGN clause was a VSAM dataset.

ExplanationThe program file description specified that the file wasa physical sequential file and the data set associatedwith the ASSIGN clause was found to be a VSAM file.The OPEN statement failed.

System actionIf a file status was specified, no system action isperformed. If a file status field was not specified,the program is terminated and message IGZ0035S isgenerated.

Programmer responseCheck that the file description and the DD parameterassociated with the ASSIGN clause are for the correctdata set.


IGZ0201W A file attribute mismatch wasdetected. File file-name inprogram program-name had arecord length of record-length-1and the file specified in theASSIGN clause had a recordlength of record-length-2.


ExplanationThe program file description specified a record lengththat did not match the record length of the dataset associated with the ASSIGN clause. The OPENstatement failed.


Programmer responseFor Format-V and Format-S files the maximum recordlength specified in your program must be exactly 4bytes smaller than the length attribute of the dataset. For Format-F files, the record length specified inyour program must exactly match the length attributeof the data set. For Format-U files, the maximumrecord length specified in your program must exactlymatch the length attribute of the data set. If yourfile is a printer file, the compiler may add one byteto the file description for carriage control character,depending on the ADV compiler option and the COBOLstatements used in your program. In which case, theadded byte must be included in the data set lengthattribute. For VSAM files, the record length must notbe greater than the maximum length attribute of thedata set. For VSAM simulated RRDS (SIMVRD run-timeoption) the record length specified in the ASSIGNclause is incremented by 4 bytes before comparisonwith the length attribute of the data set.


IGZ0202W A file attribute mismatch wasdetected. File file-name inprogram program-name specifiedASCII data and the file specified inthe ASSIGN clause did not containthe ASCII data attribute.

ExplanationThe CODE-SET clause was specified in the programfile description and the data set associated with theASSIGN clause did not contain ASCII data. The OPENstatement failed.

System actionIf a file status was specified, no system action isperformed. If a file status field was not specified,

the program is terminated and message IGZ0035S isgenerated.

Programmer responseCheck that the data set associated with the ASSIGNclause is the correct one, and if it is, check the data setfor the ASCII attribute.


IGZ0203W A file attribute mismatch wasdetected. File file-name inprogram program-name specifiednon-ASCII data and the filespecified in the ASSIGN clausecontained the ASCII dataattribute.

ExplanationThe data set associated with the ASSIGN clausecontained ASCII type data and the file description inthe program did not contain ASCII data. The OPENstatement failed.


Programmer responseCheck that the data set associated with the ASSIGNclause is the correct one, and if it is, check the data setfor the ASCII attribute.


IGZ0204W A file attribute mismatch wasdetected. File file-name inprogram program-name wasdefined as RECORDING MODErecording-mode and the filespecified in the ASSIGN clause didnot contain the same attribute.

ExplanationThe RECORDING MODE specified in the program filedescription did not match the data control block fieldsof the data set associated with the ASSIGN clause. TheOPEN statement failed.



Programmer responseCheck the data control block fields of the actual dataset to verify that the RECORDING MODE matches. Themost common cause of this error is conflicting fixedand variable record length data set attributes.


IGZ0205W An OPEN failure occurred forfile file-name in program program-name because the SMSVSAMserver was not available. The filewas closed.

ExplanationCOBOL encountered a SMSVSAM server not availableerror return while performing OPEN, I/O, or controlblock testing of a VSAM data set in RLS mode. For thiserror condition VSAM requires that the file be closed,opened, and positioned before resubmitting requests.Look for possible VSAM error messages in the job log.


Programmer responseCOBOL only performs a close of the file. Resolve theSMSVSAM server not available condition and resubmitthe run or remove the RLS keyword specification fromthe DD statement.


IGZ0206W The AIXBLD run-time optionwas invalid for file file-name inprogram program-name becausethe file was opened in RLS mode.The file was closed.

ExplanationThe AIXBLD option is only supported for VSAM datasets opened without RLS mode. VSAM data setsopened in RLS mode can be empty, but upgrades

to empty paths are not supported. The alternateindex path must be built before using RLS mode. Thealternate index was not built and the file was closed.


Programmer responseIf AIXBLD option is required, remove the RLS keywordspecification from the DD statement for this file andresubmit the run.


IGZ0207W The SIMVRD run-time optionwas invalid for file file-name inprogram program-name becausethe file was opened in RLS mode.The file was closed.

ExplanationThe SIMVRD option is not supported for VSAM datasets in RLS mode. The file was closed.


Programmer responseIf SIMVRD option is required, remove the RLS keywordspecification from the DD statement for this file andresubmit the run.


IGZ0210S There was an attempt to run anOS/VS COBOL program program-name in a non-initial thread.

ExplanationOS/VS COBOL programs can only run in the initialthread. For example, OS/VS COBOL programs can notrun in a subtask created by a PL/I CALL statement withthe TASK, EVENT, or PRIORITY option.



Programmer responseCompile the COBOL program with the COBOL for MVS& VM or COBOL for OS/390 & VM compiler.


IGZ0215S Argument —1 for function function-name in program program-name atline line-number was less than 0 orgreater than 99.



Programmer responseEnsure that argument-1 is greater than, or equal to 0,and less than 100.












IGZ0218S The sum of the year at thetime of execution and the valueof argument —2 was less than1700 or greater than 10000 forfunction function-name in programprogram-name at line line-number.



Programmer responseEnsure that the sum of the year at the time ofexecution and the value of argument-2 is less than1700 or greater than 10000.


IGZ0219S The base year for programprogram-name was outside thevalid range of current yearminus 99 through 1999. Thesliding window value window-value resulted in a base year ofbase-year.

ExplanationThe current year was outside the 100-year fixedwindow specified by the YEARWINDOW compileroption value.

For example, if a COBOL program is compiled withYEARWINDOW(1920), the 100-year window for theprogram is 1920 and 2019. When the program is run


in the year 2020, this error message would occur sincethe current year is not within the 100-year window.


Programmer responseExamine the application design to determine if itwill support a change to the YEARWINDOW optionvalue. If the application can run with a change tothe YEARWINDOW option value, then compile theprogram with an appropriate YEARWINDOW optionvalue. If the application cannot run with a change tothe YEARWINDOW option value, then convert all datefields to expanded dates and compile the programwith NODATEPROC.


IGZ0220S The current year was outsidethe 100-year window, year-startthrough year-end for programprogram.

ExplanationThe current year was outside the 100-year fixedwindow specified by the YEARWINDOW compileroption value.

For example, if a COBOL program is compiled withYEARWINDOW(1920), the 100-year window for theprogram is 1920 through 2019. When the programis run in the year 2020, this error message wouldoccur since the current year is not within the 100 yearwindow.


Programmer responseExamine the application design to determine if itwill support a change to the YEARWINDOW optionvalue. If the application can run with a change tothe YEARWINDOW option value, then compile theprogram with an appropriate YEARWINDOW optionvalue. If the application cannot run with a change tothe YEARWINDOW option value, then convert all datefields to expanded dates and compile the programwith NODATEPROC.


IGZ0221W The Y2PAST= y2past-value SORToption (from the YEARWINDOWcompiler option) was overriddenby the Y2PAST value in the sortcontrol file.

ExplanationA windowed date field was specified as a KEY in aSORT or MERGE, which resulted in the YEARWINDOWcompiler option being converted into a SORT optionY2PAST value, but Y2PAST was also specified in thesort control file.

The value in the sort control file was used, and theY2PAST value from the program was ignored.


Programmer responseSee Enterprise COBOL for z/OS library (www.ibm.com/support/docview.wss?uid=swg27036733)for adescription of using windowed date fields with SORTand MERGE.


IGZ0222S No significant digits remainin a fixed-point exponentiationoperation in program program atdisplacement displacement dueto excessive decimal positionsspecified in the operands orreceivers.

ExplanationA fixed-point exponentiation operation that specifiesa negative exponent could not be completed becauseall significant digits were lost after the operands werescaled. This condition is caused by excessive decimalpositions being specified in the operands or receiversof the expression.





Programmer responseSimplify the arithmetic expression, specifying lessdecimal positions in the operands.

Do not use exponentiation of a base having 31 decimalpositions, using a negative integral exponent. Rather,use an exponentiation specifying a positive exponentfollowed by an explicit division operation.

Alternatively, use a floating-point expression. To dothis, specify at least one floating-point operand orreceiver.


IGZ0223S Argument-1 for function function-name in program program-nameat line line-number was less thanzero or greater than 29.

ExplanationInput argument to function FACTORIAL is greater than29 or less than 0.




IGZ0224S There was an attempt to runCOBOL programs in more thanone thread and all of the COBOLprograms were not enabled formultithreading. The error wasdetected when attempting to runCOBOL program program-name.

ExplanationThere was an attempt to run COBOL programs thatare not enabled for multithreading in more than onethread. In order to run COBOL programs in morethan one thread, all of the COBOL programs in theapplication must be compiled with the EnterpriseCOBOL compiler using the THREAD compiler option.

COBOL programs compiled with the followingcompilers can only run in one thread at a time:

• Enterprise COBOL with the NOTHREAD compileroption

• COBOL for OS/390 & VM• COBOL for MVS & VM• COBOL/370• VS COBOL II• OS/VS COBOL

This condition can occur when PL/I multitasking isused or when POSIX(ON) is in effect.

If PL/I multitasking is used, here are examples thatcan cause this condition:

• If an Enterprise COBOL program compiled withoutthe THREAD compiler option or a COBOL for OS/390& VM program has been invoked in the main task,then any attempts to invoke a COBOL program ina subtask created by a PL/I statement with theTASK, EVENT or the PRIORITY option will cause thiscondition to be signaled.

• If an Enterprise COBOL program compiled withoutthe THREAD compiler option or a COBOL for OS/390& VM program has been invoked in a subtask, thenany attempts to invoke a COBOL program in anyother task will cause this condition to be signaleduntil the subtask is terminated.

If POSIX(ON) is in effect, here are examples that cancause this condition:

• If an Enterprise COBOL program compiled withoutthe THREAD compiler option or a COBOL for OS/390& VM program has been invoked in the initial thread,then any attempts to invoke a COBOL program ina non-initial thread will cause this condition to besignaled.

• If an Enterprise COBOL program compiled withoutthe THREAD compiler option or a COBOL for OS/390& VM program has been invoked in a non-initialthread, then any attempts to invoke a COBOLprogram in another thread will cause this conditionto be signaled until the non-initial thread in which aCOBOL program was invoked is terminated.


Programmer responseCompile all the COBOL programs with the EnterpriseCOBOL using the THREAD compiler option.



IGZ0225S There was an attempt to run thethread enabled COBOL programprogram-name in a COBOLreusable environment.

ExplanationEnterprise COBOL programs compiled with theTHREAD compiler option cannot run in a COBOLreusable environment.

A COBOL reusable environment is established by doingone of the following:



Programmer responseIf you want to continue to run with the COBOLreusable environment, compile the COBOL programwith the NOTHREAD compiler option. If youwant to run COBOL programs compiled with theTHREAD option in a preinitialized environment, usethe Language Environment preinitialization supportprovided by CEEPIPI.


IGZ0226S On CICS, an attempt was madeto run a COBOL program thatcontains object-oriented syntax.The program name is program-name.

ExplanationCOBOL programs running on CICS cannot contain anyobject-oriented syntax.


Programmer responseChange the COBOL program so that it does not containobject-oriented class definitions, INVOKE statements,or references to the JNIEnvPtr special register.


IGZ0227S There was an invalid attempt toend an XML PARSE statement.

ExplanationAn XML PARSE statement initiated by a COBOLprogram was in progress and one of the following wasattempted:

1. A GOBACK or an EXIT PROGRAM was issued withinthe COBOL program that initiated the XML PARSE.

2. A user handler associated with the programthat initiated the XML PARSE moved thecondition handler resume cursor and resumed theapplication.


Programmer responseChange the application so that it does not use one ofthe above methods to end the XML PARSE statement.


IGZ0228S There was an invalid attempt tostart an XML PARSE statement.

ExplanationAn XML PARSE statement initiated by a COBOLprogram was already in progress when another XMLPARSE statement was attempted by the same COBOLprogram. Only one XML PARSE statement can beactive in a given invocation of a COBOL program.


Programmer responseChange the application so that it does not initiateanother XML PARSE statement from within the sameCOBOL program.


IGZ0229S Argument–2 for function function-name in program program-name at


line line-number was less than 1 orgreater than 65535.

ExplanationArgument-2, the CODEPAGE, for the indicated functionwas not within the range of 1 thru 65535.


Programmer responseEnsure the argument-2 for the indicated function iswithin the valid range of 1 thru 65535.

Symbolic Feedback CodeIGC075

IGZ0230S The processing procedure for anXML PARSE statement set XML-CODE to an unsupported value ofxml-code-value for XML event xml-event.

ExplanationThe XMLPARSE(XMLSS) compiler option was in effect.For the END-OF-INPUT XML event, XML-CODE can beset to a value of -1, zero or 1. For all other XML events,only -1 and zero are supported.


Programmer responseCorrect the statements that set the value of the XML-CODE special register.


IGZ0251W An invalid keyword keywordwas found at position positionin environment variable env-varwhile processing file file-name inprogram program-name.

ExplanationWhile processing the allocation of the file, thespecified keyword was encountered at the indicatedposition. The keyword was not allowed in the

environment variable. The OPEN statement failed withfile status 98.


Programmer responseRemove the identified keyword from the environmentvariable. Also, make sure that all keywords are inuppercase. Additionally, for QSAM and VSAM files,make sure that the DSN or PATH keyword is specifiedfirst in the environment variable. For line sequentialfiles, make sure that the PATH keyword is the onlykeyword specified in the environment variable.


IGZ0252W An invalid delimiter was found atposition position in environmentvariable env-var while processingfile file-name in program program-name.

ExplanationWhile processing the allocation of the file, thedelimiter at the indicated position was invalid in thecontext used in the environment variable. The OPENstatement failed with file status 98.


Programmer responseCorrect the identified delimiter in the environmentvariable.


IGZ0253W Keyword keyword1 was found atposition position in environmentvariable env-var while processingfile file-name in program program-


name and is mutually exclusivewith keyword keyword2.

ExplanationWhile processing the allocation of the file, keyword1was found at the indicated position in the environmentvariable but cannot be specified with keyword2 whichwas found earlier. The OPEN statement failed with filestatus 98.


Programmer responseRemove either keyword1 or keyword2 from theenvironment variable.


IGZ0254W Environment variable env-var isnull or only contains blanks forfile file-name in program program-name.

ExplanationThe contents of the environment variable that wasused for the allocation of the file were null or onlycontained blanks. The file cannot be allocated. TheOPEN statement failed with file status 98.


Programmer responseFor QSAM and VSAM files, make sure that the ddnameis properly defined for the file by specifying a ddnamefor the file setting an environment variable with thesame name as the ddname to identify the file. Forline sequential files, make sure that the file is properlydefined by setting an environment variable with thesame name as the file name to identify the file usingan absolute pathname.


IGZ0255W Dynamic allocation failed forddname ddname while processingfile file-name in program program-name. The return code from thedynamic allocation was return-code, error code error-code, reasoncode reason-code, and informationcode information-code.

ExplanationA error occurred issuing the dynamic allocation for theddname. The OPEN statement failed with file status98.




IGZ0256W Dynamic deallocation failed forddname ddname while processingfile file-name in program program-name. The return code from thedynamic deallocation was return-code, error code error-code, reasoncode reason-code, and informationcode information-code.

ExplanationAn error occurred issuing the dynamic deallocationfor the ddname. The CLOSE statement failed with filestatus 98.

System actionIf a file status or error declarative was specified forthe file, no system action is performed. If neither a file


status nor an error declarative was specified for thefile, the program is terminated and message IGZ0035Sis generated.



IGZ0257W The environment variable env-varfor file file-name in programprogram-name contains an invaliddataset name value.

ExplanationWhile processing the allocation of the file, the datasetname specified in the DSN keyword of the environmentvariable was invalid. The OPEN statement failed withfile status 98.


Programmer responseCorrect the dataset name in the DSN keyword of theenvironment variable.


IGZ0258W The environment variable env-varfor file file-name in programprogram-name contains an invalidmember name value.

ExplanationWhile processing the allocation of the file, the membername specified in the DSN keyword of the environmentvariable was invalid. The OPEN statement failed withfile status 98.


Programmer responseCorrect the member name in the DSN keyword of theenvironment variable.


IGZ0259W The environment variable env-varfor file file-name in programprogram-name contains an invalidpath name value.

ExplanationWhile processing the allocation of the file, thepath name specified in the PATH keyword of theenvironment variable was invalid. The OPEN statementfailed with file status 98.


Programmer responseCorrect the path name in the PATH keyword of theenvironment variable.


IGZ0260W Temporary dataset names cannotbe used for dynamic allocation inenvironment variable env-var forfile file-name in program program-name.

ExplanationThe contents of the environment variable that wasused for the allocation of the file specified atemporary dataset name in the DSN parameter.Temporary dataset names are not supported for


dynamic allocation. The OPEN statement failed withfile status 98.


Programmer responseChange the DSN parameter in the specifiedenvironment variable to specify a permanent datasetname.


IGZ0261W An absolute pathname was notspecified in environment variableenv-var for file file-name inprogram program-name.

ExplanationThe contents of the environment variable that wasused for the allocation of the file did not specifyan absolute pathname in the PATH parameter.Only absolute pathnames are supported. The OPENstatement failed with file status 98.


Programmer responseChange the PATH parameter in the specifiedenvironment variable to specify an absolute pathname.


IGZ0262S C-Runtime-message

ExplanationAn error occurred while attempting to retrieve theoptimized schema. The message provides details.


Programmer responseCorrect the indicated error. For more informationregarding the message, see z/OS LanguageEnvironment Runtime Messages.


IGZ0263I The previous condition has alsooccurred in program prograrm-name on line(s): line-numbers.

ExplanationSee the explanation for the previous message fordetails.


Programmer responseSee the user response for the previous message fordetails.


IGZ0264S There was an attempt to runboth OS/VS COBOL and EnterpriseCOBOL V5 programs in the sameenclave.

ExplanationOS/VS COBOL programs can not be run in the sameenclave where Enterprise COBOL V5 programs are alsorunning.


Programmer responseCompile the OS/VS COBOL program with an EnterpriseCOBOL compiler.



IGZ0265S Argument-1 for function function-name in program program-nameat displacement displacement wasnot a valid UTF-8 string.

ExplanationArgument-1 is not a valid UTF-8 string.


Programmer responseEnsure that argument-1 is a valid UTF-8 string.


IGZ0266S Argument-2 and argument-3 forfunction USUBSTR in programprogram-name at displacementdisplacement was not a validcombination for substring of aUTF-8 string.

ExplanationThe values for argument-2 and argument-3 forfunction USUBSTR were invalid.


Programmer responseEnsure that argument-2 and argument-3 are validfor UTF-8 substring. Argument-2 must be an integergreater than zero. Argument-3 must be an integergreater than or equal to zero. (Argument-2 +argument-3 - 1) must be less than or equal toULENGTH(argument-1).


IGZ0268W An invocation was made of OS/VSCOBOL program program-name.

ExplanationAn invocation of an OS/VS COBOL program wasmade. OS/VS COBOL programs cannot interoperatewith Enterprise COBOL V5 programs. In addition, IBMmay remove support for OS/VS COBOL programs from

Language Environment in the future. Therefore, usersneed to know if they are using OS/VS COBOL programsand what the program names are.


Programmer responseRecompile the OS/VS COBOL program with a newercompiler.


IGZ0269W program-lang version program-version program program-namemade a call to OS/VS COBOLprogram program-name.

ExplanationA COBOL program made a call to an OS/VS COBOLprogram with the CALL statement. Using the CALLstatement to perform calls between Enterprise COBOLV5 programs and OS/VS COBOL programs is notsupported. In addition, IBM may remove support forOS/VS COBOL programs from Language Environmentin the future, so users need to know if they are usingOS/VS COBOL programs and what the program namesare.

An OS/VS COBOL program can also be called byan ASSEMBLER program using the IGZCXCC routine.In this case, the actual name of the ASSEMBLERprogram, as well as the program version information,will not be available as part of the message.


Programmer responseRecompile the OS/VS COBOL program with a newercompiler.


IGZ0270S In a multithreaded environment,COBOL program program-namewas called during conditionhandling and the program cannotbe initialized.


ExplanationIn a multithreaded environment, COBOL programscannot be called as a condition handler for conditionsraised while performing COBOL program initialization.


Programmer responseUse a condition handler written in assembler or Cto handle conditions raised during COBOL programinitialization.


IGZ0271S There was an attempt to initializeCOBOL in a nested enclave whenthe initial enclave is multithreadedor multitasking. The first programof the nested enclave wasprogram-name.

ExplanationA COBOL program cannot run in a nested enclavewhen the initial enclave is multithreaded ormultitasking.


Programmer responseChange the application so that the COBOL programis not running in a nested enclave or do not usemultithreading or multitasking when using COBOLprograms in nested enclaves. If the program nameprinted is "????????", then the first program of thenested enclave is not COBOL.


IGZ0272S Data conversion from CCSIDCCSID1 to CCSID2 wasunsuccessful. The return codefrom the Unicode ConversionService CUNLCNV was return-codeand the reason code was reason-code.

ExplanationThe data conversion for the CCSID pair failed asindicated by the return code and the reason code. Thereturn code and the reason code values for conversionservices are described in z/OS Unicode Services User'sGuide and Reference.


Programmer responseFollow the programmer responses indicated forspecific return and reason codes in z/OS UnicodeServices User's Guide and Reference.


IGZ0273S A GOBACK, EXIT PROGRAM, orSTOP RUN was attempted whilean EXCEPTION/ERROR declarativewas in control for a QSAM ABEND.The declarative in control is inprogram program-name for filefile-name.

ExplanationA GOBACK, EXIT PROGRAM, or STOP RUN statementcannot be used while an EXCEPTION/ERRORdeclarative is in control due to a QSAM ABEND for aREAD, REWRITE, or WRITE statement. When a QSAMabend occurs during a READ, WRITE, or REWRITE, thefile status code can be file status 34 or file status 90.

System actionThe application is terminated with ABEND 4043.

Programmer responseChange the program to not use a GOBACK, EXITPROGRAM, or STOP RUN statement when theEXCEPTION/ERROR declarative is in control.


IGZ0274S A GOBACK, EXIT PROGRAM, orSTOP RUN was attempted while aLABEL declarative was in control.The declarative in control is inprogram program-name for filefile-name.


ExplanationA GOBACK, EXIT PROGRAM, or STOP RUN statementcannot be used while a LABEL declarative is in control.

System actionThe application is terminated with ABEND 4043.

Programmer responseChange the program to not use a GOBACK, EXITPROGRAM, or STOP RUN statement when the LABELdeclarative is active.


IGZ0275S The contents of data item data-name at the time of referenceby verb number verb-numberon line line-number failed theNUMERIC class test generated bythe ZONECHECK compiler option.

ExplanationWhen the ZONECHECK(ABD) compiler option is ineffect, this message is issued to indicate that a zoneddecimal (numeric USAGE DISPLAY) data item hadinvalid contents at runtime.

The compiler generated a NUMERIC class test, andthis data item tested as not numeric.


Programmer responseEnsure that the source of the data for this data item iscorrect, and that the data has not been corrupted byother statements.


IGZ0276W The contents of data item data-name at the time of referenceby verb number verb-numberon line line-number failed theNUMERIC class test generated bythe ZONECHECK compiler option.

ExplanationWhen the ZONECHECK(MSG) compiler option is ineffect, this message is issued to indicate that a zoneddecimal (numeric USAGE DISPLAY) data item hadinvalid contents at runtime.





IGZ0277W The value data-item-value of dataitem data-name at the time ofreference by verb number verb-number on line line-number inprogram program-name failed theNUMERIC class test generated bythe ZONECHECK compiler option.

ExplanationWhen the ZONECHECK(MSG) compiler option is ineffect, this message is issued to indicate that a zoneddecimal (numeric USAGE DISPLAY) data item hadinvalid contents at runtime.





IGZ0278S The contents of data item data-name at the time of referenceby statement number verb-numberon line line-number failed the


NUMERIC class test or containeda value larger than the PICTUREclause as detected by theNUMCHECK compiler option.

ExplanationWhen the NUMCHECK(ZON,ABD) compiler option is ineffect, or the NUMCHECK(PAC,ABD) compiler optionis in effect, this message is issued to indicate that azoned decimal (numeric USAGE DISPLAY) or PACKED-DECIMAL data item had invalid contents at runtime.

The compiler generated a NUMERIC class test, andthis data item tested as not numeric. For PACKED-DECIMAL data items that have an even number ofdigits, the unused bits were also checked for zeros.




IGZ0279W The value data-item-value of dataitem data-name at the time ofreference by statement numberverb-number on line line-numberin program program-name failedthe NUMERIC class test orcontained a value larger than thePICTURE clause as detected bythe NUMCHECK compiler option.

ExplanationWhen the NUMCHECK(ZON,MSG) compiler option is ineffect, or the NUMCHECK(PAC,MSG) compiler optionis in effect, this message is issued to indicate that azoned decimal (numeric USAGE DISPLAY) or PACKED-DECIMAL data item had invalid contents at runtime.

The compiler generated a NUMERIC class test, andthis data item tested as not numeric. For PACKED-DECIMAL data items that have an even number ofdigits, the unused bits were also checked for zeros.




IGZ0280S XML to data structure conversioncould not complete in programPROGRAM-NAME because an errorreturn code of RETURN-CODE wasreceived from the XML PARSEstatement. The error occurred atelement ELEMENT-NAME with thecharacter content CHARACTER-CONTENT.

ExplanationXML to language structure conversion uses the COBOLXML PARSE statement. When the XMLPARSE(COMPAT)compiler option is in effect, the return code is providedfrom the XML PARSE statement and is described inthe Enterprise COBOL Programming Guide. When theXMLPARSE(XMLSS) compiler option is in effect, thereturn code is provided from the z/OS XML SystemServices Parser and is described in the XML SystemServices User's Guide and Reference.


Programmer responseUse the return code to determine the error and correctthe input XML message.


IGZ0281S XML to language structureconversion could not complete inprogram PROGRAM-NAME becausethe valid range of a repeatinggroup or repeating data item wasexceeded. The error occurred atelement ELEMENT-NAME.


ExplanationXML to language structure conversion encounterserrors while transforming an XML message to alanguage structure. These errors are distinct from XMLPARSE errors.


Programmer responseCorrect the input XML message. Ensure that themessage is valid according to the XML Schema uponwhich the XML to language structure converter isbased.


IGZ0282S XML to language structureconversion could not complete inprogram PROGRAM-NAME becausenone of the elements in the inputXML document matched a mappedelement in the XML Schema uponwhich the XML converter is based.





IGZ0283S XML to language structureconversion could not complete inprogram PROGRAM-NAME becausethe character content for elementELEMENT-NAME was longer thanthe element's maximum of LIMITcharacters.





IGZ0284S XML to language structureconversion could not complete inprogram PROGRAM-NAME becauseconversion of the charactercontent of an element thatis mapped as numeric failed.The error occurred at elementELEMENT-NAME with the charactercontent CHARACTER-CONTENT.






IGZ0285S XML to language structureconversion could not completein program PROGRAM-NAMEbecause the length of the inputXML document is INPUTLENcharacters, which exceedsthe maximum of MAXIUMUMcharacters for this converter.

ExplanationXML to language structure conversion imposes a limiton the length of XML documents that can be convertedinto language structures. The maximum length in bytesof the input XML document is 16MB when version 3of Enterprise COBOL for z/OS is used and 32MB whenversion 4 of Enterprise COBOL for z/OS is used.


Programmer responseCheck that the input XML message conforms to theXML Schema upon which it is based. Check anywhitespace outside of element content has beentrimmed.


IGZ0286S XML to language structureconversion could not complete inprogram PROGRAM-NAME becausethe content for element ELEMENT-NAME had a length greater thanor equal to INPUTLEN characterswhich was too long for theconverter to process.

ExplanationXML to language structure conversion maintains abuffer for character content that has a maximum sizeequal to 10 times the size of the largest item in thetarget language structure. The content of an elementwas longer than expected.




IGZ0287S Language structure to XMLconversion could not complete inprogram PROGRAM-NAME becausethe maximum output messagelength of LENGTH characters wasexceeded while generating theXML document.

ExplanationLanguage structure to XML conversion performswhitespace suppression and entity referenceexpansion while generating the XML document. Entityreference expansion increases the length of datawhich is included as element content causing it togrow up to 6 times the original length of the data (thelongest predefined entity is 6 characters long).


Programmer responseEnsure that the language structure has not changedsince the Language structure to XML converter hasbeen generated. Regenerate the XML converter ifchanges have been made to the language structure.



IGZ0288S XML conversion could notcomplete in program PROGRAM-NAME because a non-zeroreturn code was received fromthe Unicode Conversion ServiceCUNLCNV while converting fromCCSID SOURCE-CCSID to CCSIDTARGET-CCSID.

ExplanationXML Conversion converts XML and language data toand from Unicode during parsing and generation ofXML, if XML is expected to be exchanged in Unicode.


Programmer responseCheck that conversion services is properly installed,and ensure that the conversion attempted by the XMLConverter is supported by the systems installation ofconversion services.


IGZ0289S Language structure to XMLconversion could not completein program PROGRAM-NAMEbecause the content of non-numeric member MEMBER-NAMEof language structure STRUCTURE-NAME contained characters thatare not legal in an XML document.

ExplanationCertain data structure members permit storage ofcharacters that are not legal in an XML document.The permitted characters are defined by the XMLspecification at W3C (www.w3.org).

System actionThe converter will either signal a LanguageEnvironment condition or, if the optional feedbackcode argument is provided, a condition token

representing the condition will be placed in theargument.

Programmer responseEnsure that the language structure member is properlyinitialized and does not contain any characters that areillegal in XML before attempting conversion.


IGZ0290S Language structure to XMLconversion could not complete inprogram PROGRAM-NAME becausethe content of numeric memberMEMBER-NAME of languagestructure STRUCTURE-NAME isinvalid.

ExplanationLanguage structure to XML conversion has determinedthat the contents of the storage occupied by a numericlanguage structure member are invalid for the type.


Programmer responseEnsure that the numeric language structure member isproperly initialized according to COBOL semantics.


IGZ0291S XML to language structureconversion could not complete inprogram PROGRAM-NAME becausethe maximum XML elementnesting depth was exceeded.The error occurred at elementELEMENT-NAME with charactercontent CHARACTER-CONTENT.

ExplanationThe language structure to XML converter maintains aninternal stack which represents the full qualificationof the current element being processed in the XMLdocument. If extraneous XML elements that are not


http://www.w3.org

described in the XML schema to which the converteris bound are present in the XML document, they willexceed the maximum supported element depth.


Programmer responseEither supply XML documents to the converter thatvalidate against the bound XML schema or remove theextraneous element that causes the failure from theinput XML document.


IGZ0292S XML conversion could notcomplete in program PROGRAM-NAME because an attempt toregister an exception handlerfailed with Language Environmenterror LE-ERROR.

ExplanationXML conversion uses Language Environment callableservices to register a user-written handler to handleerrors that occur during conversion. An attempt toregister such a handler failed.




IGZ0293S XML conversion could notcomplete in program PROGRAM-NAME because an attempt to

unregister an exception handlerfailed with Language Environmenterror LE-ERROR.

ExplanationXML conversion uses Language Environment callableservices to register a user-written handler to handleerrors that occur during conversion. An attempt tounregister such a handler failed.




IGZ0294S XML conversion could notcomplete in program PROGRAM-NAME because the address of oneor more required parameters tothe main entry point did not havevalid addresses.

ExplanationEnsure that each parameter passed to the XMLconverter has a valid non-null storage address unlessa particular parameter can be null as defined by theconverter call interface. For example, passing a nulladdress for the XML buffer address to the languagestructure to XML converter will cause the required sizeof the XML buffer to be returned instead of performingXML conversion.



Programmer responseEnsure that each parameter passed to the converterhas a valid storage address unless a particularparameter can be null as defined by the convertercall interface. For example, a null message addresspassed to the outbound converter will be interpretedas a request for the maximum outbound message sizeto be returned instead of performing a conversion.


IGZ0295S XML to language structureconversion could not complete inprogram PROGRAM-NAME becausea response code of RESPONSE-CODE with reason code REASON-CODE was received from thebidirectional data conversionmodule MODULE-NAME whileprocessing the XML elementELEMENT-NAME.

ExplanationXML to language structure conversion uses an externalmodule to handle bidirectional data conversions.




IGZ0296S Language structure to XMLconversion could not completein program PROGRAM-NAMEbecause a return code of RETURN-CODE with reason code REASON-CODE was received from thebidirectional data conversionmodule MODULE-NAME whileprocessing member MEMBER-NAME of language structureSTRUCTURE-NAME.

ExplanationLanguage structure to XML conversion uses anexternal module to handle bidirectional dataconversions.




IGZ0297S XML to language structureconversion could not completein program PROGRAM-NAMEbecause the content for attributeATTRIBUTE-NAME had a lengthgreater than or equal to INPUTLENcharacters, which was too long forthe converter to process.

ExplanationXML to language structure conversion maintains abuffer for accumulating the contents of XML attributes.The maximum size of the buffer is based on attributeand namespace declarations in the XML Schema.


Programmer responseCorrect the XML instance document such that itconforms to the inbound XML Schema.

IGZ0298S XML to language structureconversion could not complete inprogram PROGRAM-NAME becausethe target namespace of elementELEMENT-NAME was NAMESPACE-ACTUAL which is inconsistent with


the expected target namespace ofNAMESPACE-EXPECTED.

ExplanationXML to language structure conversion can optionallyvalidate the namespace name of XML elements.


Programmer responseCorrect the XML instance document such that theXML elements have namespace names consistent withthose specified in the XML Schema.

IGZ0299S XML to language structureconversion could not complete inprogram PROGRAM-NAME becausethe minimum count of languagestructure STRUCT-NAME was notmet.

ExplanationXML to language structure conversion detected thatthe count of a language structure does not meet theminimum count that was specified when the converterwas generated.

System actionThe converter will signal a Language Environmentcondition. But if the optional feedback code argumentis provided, a condition token representing thecondition will be placed in the argument.

Programmer responseCorrect the XML document or replace the converterwith one having a different minimum count for thelanguage structure.

IGZ0300S XML to language structureconversion could not complete inprogram PROGRAM-NAME becausethe maximum count of languagestructure STRUCT-NAME wasexceeded.

ExplanationXML to language structure conversion detected thatthe count of a language structure exceeds themaximum that was specified when the XML converterwas generated.


Programmer responseCorrect the XML document or replace the XMLconverter with one having a higher maximum.

IGZ0301S Language structure to XMLconversion could not complete inprogram PROGRAM-NAME becausethe total count of languagestructure instances received wasACTUAL-COUNT which is less thanthe minimum of MINIMUM-COUNTinstances required by the messagelayout.

ExplanationLanguage structure to XML conversion detected thatthe language structure buffer it received containedfewer language structure instances in total than isrequired by the message layout.


Programmer responseCorrect the language structure buffer so that eachlanguage structure occurs at least as many times asis required per the message layout.

IGZ0302S Language structure to XMLconversion could not complete inprogram program-name becausethe length prefix of languagestructure struct-name specified alength of specified-length bytes,which is less than the structure'sminimum length of minimum-length bytes.


ExplanationLanguage structure to XML conversion detected thatthe length prefix of a language structure specified alength that is less than the minimum length of thestructure. The minimum length of a language structureis computed as the sum of the bytes consumed by allsubordinate fields. In the case of fields that specifyOCCURS DEPENDING ON, the minimum number ofoccurrences is assumed.


Programmer responseCorrectly set the two-byte length prefix of eachlanguage structure in the language structure buffer.


IGZ0303S Language structure to XMLconversion could not complete inprogram program-name becausethe total count of languagestructure instances received wasactual-count which is greater thanthe maximum of maximum-countinstances allowed by the messagelayout.

ExplanationLanguage structure to XML conversion detected thatthe language structure buffer it received containedmore language structure instances in total than isallowed by the message layout.


Programmer responseCorrect the language structure buffer so that itcontains no more than the maximum number ofinstances of each language structure in the messagelayout.


IGZ0304W The reference to table table-nameby verb number verb-numberon line line-number in programprogram-name addressed an areaoutside the region of the table.

ExplanationWhen the SSRANGE option is in effect, this messageis issued to indicate that a fixed-length table has beensubscripted in a way that exceeds the defined size ofthe table, or, for variable-length tables, the maximumsize of the table.

The range check was performed on the compositeof the subscripts and resulted in an address outsidethe region of the table. For variable-length tables,the address is outside the region of the table definedwhen all OCCURS DEPENDING ON objects are at theirmaximum values; the ODO object's current value isnot considered. The check was not performed onindividual subscripts.


Programmer responseEnsure that the value of literal subscripts or the valueof variable subscripts, or both, as evaluated at run-time do not exceed the subscripted dimensions forsubscripted data in the failing statement.


IGZ0305W The size of variable lengthgroup group-name exceeded themaximum defined length of thegroup at the time of reference byverb number verb-number on lineline-number in program program-name.

ExplanationWhen the SSRANGE option is in effect, this messageis issued to indicate that a variable-length groupgenerated by OCCURS DEPENDING ON has a lengththat is less than zero, or is greater than the limitsdefined in the OCCURS DEPENDING ON clauses.


The range check was performed on the compositelength of the group, and not on the individual OCCURSDEPENDING ON objects.


Programmer responseEnsure that OCCURS DEPENDING ON objects asevaluated at run-time do not exceed the maximumnumber of occurrences of the dimension for tableswithin the referenced group item.


IGZ0306W A reference modification lengthvalue of reference-modification-value on line line-number inprogram program-name which wasnot equal to 1 was found in areference to data item data-itemwhich was passed by value.

ExplanationThe length value in a reference modificationspecification was not equal to 1. The length value mustbe equal to 1.


Programmer responseCheck the indicated line number in the program toensure that any reference modified length values are(or will resolve to) 1.


IGZ0307W ALL subscripted table referenceto table table-name by verbnumber verb-number on line line-number in program program-namehad an ALL subscript specifiedfor an OCCURS DEPENDING ONdimension, and the object was lessthan or equal to 0.

ExplanationWhen the SSRANGE option is in effect, this messageis issued to indicate that there are 0 occurrences ofdimension subscripted by ALL.

The check is performed against the current value ofthe OCCURS DEPENDING ON OBJECT.


Programmer responseEnsure that ODO object(s) of ALL-subscripteddimensions of any subscripted items in the indicatedstatement are positive.


IGZ0308W A reference modification startposition value of reference-modification-value on line line-number in program program-namereferenced an area outside theregion of data item data-item.

ExplanationThe value of the starting position in a referencemodification specification was less than 1, or wasgreater than the current length of the data item thatwas being reference modified. The starting positionvalue must be a positive integer less than or equalto the number of characters in the reference modifieddata item.


Programmer responseCheck the value of the starting position in thereference modification specification.


IGZ0309W A non-positive referencemodification length value ofreference-modification-value online line-number in programprogram-name was found in areference to data item data-item.


ExplanationThe length value in a reference modificationspecification was less than or equal to 0. The lengthvalue must be a positive integer.


Programmer responseCheck the indicated line number in the program toensure that any reference modified length values are(or will resolve to) positive integers.


IGZ0310W A reference modification startposition value of reference-modification-value and lengthvalue of length on line line-numberin program program-name causedreference to be made beyond therightmost character of data itemdata-item.

ExplanationThe starting position and length value in a referencemodification specification combine to address an areabeyond the end of the reference modified data item.The sum of the starting position and length valueminus one must be less than or equal to the number ofcharacters in the reference modified data item.


Programmer responseCheck the indicated line number in the program toensure that any reference modified start and lengthvalues are set such that a reference is not madebeyond the rightmost character of the data item.


IGZ0311W ALL subscripted table reference totable table-name by verb numberverb-number on line line-numberin program program-name willexceed the upper bound of thetable.

ExplanationWhen the SSRANGE option is in effect, this message isissued to indicate that a multidimension table with ALLspecified as one or more of the subscripts will result ina reference beyond the upper limit of the table.

The range check was performed on the compositeof the subscripts and the maximum occurrences forthe ALL subscripted dimensions. For variable-lengthtables, the address is outside the region of the tabledefined when all OCCURS DEPENDING ON objects areat their maximum values; the ODO object's currentvalue is not considered. The check was not performedon individual subscripts.


Programmer responseEnsure that OCCURS DEPENDING ON objects asevaluated at run-time do not exceed the maximumnumber of occurrences of the dimension for tableitems referenced in the failing statement.


IGZ0312W A reference modification startposition value of start-position-value on line line in programprogram-name referenced an areaoutside the region of the functionresult of function-result.

ExplanationThe value of the starting position in a referencemodification specification was less than 1, or wasgreater than the current length of the function resultthat was being reference modified. The startingposition value must be a positive integer less than orequal to the number of characters in the referencemodified function result.


Programmer responseCheck the value of the starting position in thereference modification specification and the length ofthe actual function result.



IGZ0313W A non-positive referencemodification length value of lengthon line line-number in programprogram-name was found in areference to the function result offunction-result.

ExplanationThe length value in a reference modificationspecification for a function result was less than orequal to 0. The length value must be a positive integer.


Programmer responseCheck the length value and make appropriatecorrection.


IGZ0314W A reference modification startposition value of start-position andlength value of length on lineline-number in program program-name caused reference to be madebeyond the rightmost characterof the function result of function-result.

ExplanationThe starting position and length value in a referencemodification specification combine to address an areabeyond the end of the reference modified functionresult. The sum of the starting position and lengthvalue minus one must be less than or equal tothe number of characters in the reference modifiedfunction result.


Programmer responseCheck the length of the reference modificationspecification against the actual length of the functionresult and make appropriate corrections.


IGZ0315S The contents of data item data-name at the time of referenceby statement number verb-numberon line line-number was invalid.The value exceeded the numberof digits in the data definition,and failed the SIZE ERROR testgenerated by the NUMCHECK(BIN)compiler option.

ExplanationWhen the NUMCHECK(BIN,ABD) compiler option is ineffect, this message is issued to indicate that a binarydata item had invalid data contents at runtime.

The compiler generated a SIZE ERROR test, and thisdata item contained a value that exceeded the size ofthe data item according to the PICTURE clause in itsdata definition.


Programmer responseEnsure that the source of the data for this data item iscorrect, and that the data item has not been corruptedby other statements.


IGZ0316W The value data-item-value of dataitem data-name at the time ofreference by statement numberverb-number on line line-numberin program program-name wasinvalid. The value exceeded thenumber of digits in the datadefinition, and failed the SIZEERROR test generated by theNUMCHECK(BIN) compiler option.

ExplanationWhen the NUMCHECK(BIN,MSG)) compiler option is ineffect, this message is issued to indicate that a binarydata item had invalid data contents at runtime.

The compiler generated a SIZE ERROR test, and thisdata item contained a value that exceeded the size ofthe data item according to the PICTURE clause in itsdata definition.



Programmer responseEnsure that the source of the data for this data item iscorrect, and that the data item has not been corruptedby other statements.


IGZ0317S The CALL statement on line line-number in program program-namecaused corruption of data beyondthe end of the section-nameSECTION.

ExplanationA subprogram modified data beyond the end of thesection that contained the argument passed to thatsubprogram.


Programmer responseChange the definition of the arguments in the callingprogram, or the definition of the parameters in thecalled subprogram, so that they match, per the rulesin the COBOL Language Reference Manual, as follows:The description of the data items in the called programmust describe the same number of character positionsas the description of the corresponding data items inthe calling program.


IGZ0318W The CALL statement on line line-number in program program-namecaused corruption of data beyondthe end of the section-nameSECTION.

ExplanationA subprogram modified data beyond the end of thesection that contained the argument passed to thatsubprogram.


Programmer responseChange the definition of the arguments in the callingprogram, or the definition of the parameters in thecalled subprogram, so that they match, per the rulesin the COBOL Language Reference Manual, as follows:The description of the data items in the called programmust describe the same number of character positionsas the description of the corresponding data items inthe calling program.


IGZ0319W The COBOL runtime option option-name specified in IGZUOPT is inconflict with option option-name;option option-name is ignored.

ExplanationThe COBOL runtime options specified in IGZUOPT arein conflict.


Programmer responseCorrect the conflicting options.


IGZ0320W The COBOL runtime option option-name specified in IGZUOPT isinvalid. It is ignored.

ExplanationThe COBOL runtime option specified in IGZUOPT isinvalid.


Programmer responseCorrect the option.


Symbolic Feedback CodeIGZ0A0

IGZ0321I During execution of the JSONPARSE statement on line line-number of program program-name,no JSON name/value pair matcheddata item data-name, which wasthus not modified.

ExplanationAfter processing any NAME phrase literals, the givenCOBOL data item had no matching JSON name/valuepair. A match occurs when the JSON name (Unicode)and COBOL data name (EBCDIC) have an equivalentmeaning at the same level ("qualification") betweenthe JSON text and COBOL structure.

• The JSON parser continued and set the specialregister JSON-STATUS to 1, a non-exceptioncondition.

• This runtime message is issued only when the WITHDETAIL phrase is specified.


Programmer responseIf the referenced data-name should be modified bythe JSON PARSE statement, modify the JSON text orCOBOL data name or structure. If the referenced data-name does not need to be modified, then the messagecan be ignored.


IGZ0322I During execution of the JSONPARSE statement on line line-number of program program-name,no data item matched JSON nameJSON-name at offset offset.

ExplanationAfter processing any NAME phrase literals, the givenJSON name had no matching COBOL data item.A match occurs when the JSON name (Unicode)and COBOL data name (EBCDIC) have an equivalentmeaning at the same level ("qualification") betweenthe JSON text and COBOL structure.

• The JSON parser continued and set the specialregister JSON-STATUS to 2, a non-exception

condition. The offset refers to the byte offset of theJSON name from the beginning of the JSON text.



Programmer responseIf the data associated with the named JSON value/pairis not important, then the message can be ignored oryou could remove the JSON name/value pair from theJSON text. If the data associated with named JSONvalue/pair is important, use the NAME phrase to matchthe data-name to the JSON name, or create a newCOBOL data item whose name is the same as theJSON name.


IGZ0323I During execution of the JSONPARSE statement on line line-number of program program-name,a duplicate JSON name/value pairat offset matched data item data-name. The duplicate value wasaccepted.

ExplanationMore than one JSON name/value pair matched thegiven COBOL data item. The JSON values wereidentical, therefore the first assigned value wasretained.

• The JSON parser continued and set the specialregister JSON-STATUS to 4, a non-exceptioncondition. The offset refers to the byte offset of theJSON name from the beginning of the JSON text.



Programmer responseIgnore the message if the data in the COBOL group isOK, or remove the duplicate JSON name/value pairsfrom the JSON text.



IGZ0324I During execution of the JSONPARSE statement on line line-number of program program-name,JSON array with name JSON-nameat offset offset had fewer elementsthan the matching table itemdata-name. The additional tableelements were not modified.

ExplanationThe given JSON array had fewer values than thematching COBOL table item, therefore the additionalelements in the COBOL table item were not modified.




Programmer responseIf it is OK that all elements of the COBOL table are notmodified, then ignore the message. If it is not OK, thenmodify the number of values in the JSON array, or thenumber of occurrences of the matching COBOL tableitem.


IGZ0325I During execution of the JSONPARSE statement on line line-number of program program-name,JSON array with name JSON-nameat offset offset had more valuesthan the matching table item data-name. The additional values wereignored.

ExplanationThe given JSON array had more elements than thematching COBOL table item, therefore the additionalvalues in the JSON array were ignored.


condition. The offset refers to the byte offset of theJSON name from the beginning of the JSON text.



Programmer responseIf the data that was not stored in the COBOL group wasnot important, you could ignore the message or modifythe number of values in the JSON array. If the datathat was not stored was important, then modify thenumber of occurrences in the matching COBOL tableitem.


IGZ0326I During execution of the JSONPARSE statement on line line-number of program program-name,data item data-name was notchanged because the value of theJSON name/value pair at offsetoffset was the special value null.

ExplanationThe value of the COBOL data item was not changedbecause the JSON value null was interpreted as aninstruction to skip the assignment.

• The JSON parser continued and set the specialregister JSON-STATUS to 32, a non-exceptioncondition. The offset refers to the byte offset of theJSON value from the beginning of the JSON text.



Programmer responseIf the COBOL data item was to be modified, thenchange the null value of the pair from the JSON text.If it is OK that the COBOL data item was not modified,then ignore the message or remove the name/valuepair with the null value from the JSON text.



IGZ0327I During execution of the JSONPARSE statement on line line-number of program program-name,JSON array with name JSON-nameat offset offset included one ormore null values. Correspondingelements in the matching tableitem data-name were not changed.

ExplanationThe given JSON array had one or more null values.The corresponding elements in its matching COBOLtable item were not changed because the JSON valuenull was interpreted as an instruction to skip theassignment.




Programmer responseIf all occurrences of the table were to be modified,then change the JSON text to not have null values. Ifit is OK that not all occurrences were modified, thenignore the message or modify the number of valuesin the JSON array and the maximum occurrence of itsmatching COBOL table item.


IGZ0328I During execution of the JSONPARSE statement on line line-number of program program-name,assignment of the value of theJSON name/value pair at offsetoffset to data item data-nameresulted in loss of significance("SIZE ERROR").

ExplanationThe given JSON value was either string consistingof only decimal digits or number, and did not fit inits matching COBOL data item. The JSON value wastruncated during the assignment.


condition. The offset refers to the byte offset of theJSON value from the beginning of the JSON text.



Programmer responseModify the JSON value or COBOL data item to ensurethat they fit.


IGZ0329I During execution of the JSONPARSE statement on line line-number of program program-name,assignment of the value of theJSON name/value pair at offsetoffset to data item data-nameresulted in a loss of information.

ExplanationThe given JSON value was a string consisting of atleast one non-decimal digit and did not fit in itsmatching COBOL data item. The JSON value wastruncated during the assignment.




Programmer responseModify the JSON value or COBOL data item to ensurethat they fit.


IGZ0330I During execution of the JSONPARSE statement on line line-number of program program-name,the value of JSON name/valuepair with name JSON-name atoffset offset resulted in one


or more substitution characterswhen translated from Unicodeto the CCSID specified by theCODEPAGE compiler option. Thetranslated value was assigned todata-item data-name.

ExplanationThe given JSON value was translated from Unicode tothe CCSID before assigning it to its matching COBOLdata item. During the translation, one or more ofsubstitution character (X'3F') was substituted for theuntranslatable characters.




Programmer responseModify the value of the JSON name/pair to ensureit contains only characters translatable to the CCSIDspecified by the CODEPAGE compiler option.

Symbolic Feedback CodeIGZ0AA

IGZ0335W During execution of the JSONPARSE statement on line line-number of program program-name,the JSON text in data-name wasfound to be invalid. At offsetoffset , JSON-token was found, butone of JSON-tokens was expected.

ExplanationThe JSON-token from the JSON text was invalid andwas expected to be one or more of the followingJSON-tokens:JSON-token

DescriptionLEFT CURLY BRACKET or RIGHT CURLY BRACKET

The character at the offset was expected to be aleft or right curly bracket ({ or }).

LEFT QUOTATION MARK or RIGHT QUOTATIONMARK

The character at the offset was expected to be aleft or right quotation mark (").

JSON VALUEThe JSON text at the offset was expected to be abeginning of one of JSON values (string, number,object, array, true, false, or null).

COMMAThe character at the offset was expected to be acomma (,).

RIGHT SQUARE BRACKETThe character at the offset was expected to be aright square bracket (]).

COLONThe character at the offset JSON text wasexpected to be a colon (:).

LOWERCASE U or CONTROL CHARACTERThe character at the offset was preceded by abackslash (\) and was expected to be a lowercasecharacter u (u) or one of control characters (", \, /,b, f, n, r, t, or x).

NON-CONTROL CHARACTERS (Unicode U+0000 -U+001F)

The character at the offset was one of controlcharacters (Unicode U+0000 - U+001F) and wasexpected to be escaped.

HEXADECIMAL DIGITThe character at the offset was preceded bya backslash and a character u (\u), and wasexpected to be one of hexadecimal digits (0-9, a-f,A-F).

DECIMAL DIGITThe character at the offset was part of JSONnumber, therefore was expected to be one ofdecimal digits (0-9).

VALID UTF SEQUENCESThe character at the offset JSON text wasexpected to be part of well-formed UTF bytesequences. See the byte validity for UTF data inthe COBOL Language Reference Manual.

NON-LOW SURROGATEThe character at the offset was expected to be anon-low surrogate because no high surrogate wasproceeded.

LOW SURROGATEThe character at the offset was expected to bea low surrogate because a high surrogate wasproceeded.

• The JSON parser stopped and set the specialregister JSON-CODE to 100, an exception condition.The offset refers to the byte offset of the JSON-token from the beginning of the JSON text.




Programmer responseModify the contents of the JSON text appropriately.

Symbolic Feedback CodeIGZ0AF

IGZ0336W During execution of the JSONPARSE statement on line line-number of program program-name,the JSON text in data-name wasfound to be invalid. The JSON textwas zero-length, or consisted onlyof whitespace.

ExplanationThe JSON text being parsed was empty or hadcontents consisting of only white spaces. Anacceptable JSON white space is one of space (UnicodeU+0020), horizontal tab (Unicode U+0009), linefeed/new line (Unicode U+000A), or carriage return(Unicode U+000D).

• The JSON parser stopped and set the specialregister JSON-CODE to 101, an exception condition.



Programmer responseModify the JSON stream to contain only valid non-whitespace JSON text.

Symbolic Feedback CodeIGZ0AG

IGZ0337W During execution of the JSONPARSE statement on line line-number of program program-name,the JSON text in data-name wasfound to be invalid. Superfluouscharacters text were foundfollowing the closing brace of theoutermost JSON object.

ExplanationThe JSON text was valid and complete. The outermostclosing brace (}) was followed by one or more non-white space characters. An acceptable JSON whitespace is one of space (Unicode U+0020), horizontaltab (Unicode U+0009), line feed/new line (UnicodeU+000A), or carriage return (Unicode U+000D).




Programmer responseRemove the non-space characters following theoutermost closing brace (}) from the JSON text.

Symbolic Feedback CodeIGZ0AH

IGZ0338W During execution of the JSONPARSE statement on line line-number of program program-name,JSON name/value pair at offsetoffset was a duplicate match todata item data-name, but witha value different from the first(leftmost) matching name/valuepair. The value from the firstmatching JSON name/value pairwas retained.

ExplanationMore than one JSON name/value pair matched thegiven COBOL data item. The JSON values werenot identical, therefore the first assigned value wasretained.

• The JSON parser stopped and set the specialregister JSON-CODE to 103, an exception condition.The offset refers to the byte offset of the JSON namefrom the beginning of the JSON text.




Programmer responseRetain only the one desired matching JSON name/value pair in the JSON text.

Symbolic Feedback CodeIGZ0AI

IGZ0339W During execution of the JSONPARSE statement on line line-number of program program-name,the value of JSON name/valuepair with name JSON-name atoffset offset was found to beincompatible with the matchingdata item.

ExplanationThe given JSON name found its matching COBOL dataitem and its value was one of the following:

1. The JSON value was one of string, number, true,or false, but its matching COBOL data item was agroup.

2. The JSON value was an array, but its matchingCOBOL data item was not a table.

3. The JSON value and its matching COBOL data itemresulted in an invalid move, per the JSON PARSErules in the COBOL Language Reference Manual.

4. The JSON value was neither true nor false, butits matching COBOL data item was specified ona 'CONVERTING BOOLEAN' phrase of the JSONPARSE statement.

• The JSON parser stopped and set the specialregister JSON-CODE to 104, an exception condition.The offset refers to the byte offset of the JSON valuefrom the beginning of the JSON text.



Programmer responseModify the JSON text or COBOL data item or structure.

Symbolic Feedback CodeIGZ0AJ

IGZ0340W During execution of the JSONPARSE statement on line line-number of program program-name,the value of JSON name/value pair

with name JSON-name at offsetoffset was found to be one of thespecial values true or false.

ExplanationThe given JSON value was true or false. The specialvalues true and false are not supported.




Programmer responseRemove the JSON name/value pairs that have thespecial values true or false.

Symbolic Feedback CodeIGZ0AK

IGZ0341W During execution of the JSONPARSE statement on line line-number of program program-name,no JSON name/value pair matchedany data item in the receiver.The receiver data-name was notmodified.

ExplanationThere was no match between the JSON text andCOBOL data item. A match occurs when the JSONname (Unicode) and COBOL data name (EBCDIC)have an equivalent meaning at the same level("qualification") between the JSON text and COBOLstructure.





Programmer responseModify the JSON text, COBOL data name or structure,or use the NAME phrase, to ensure that the namesmatch.

Symbolic Feedback CodeIGZ0AL

IGZ0342W During execution of the JSONPARSE statement on line line-number of program program-name,the value of JSON name/value pairwith name JSON-name at offsetoffset was found to be one of thespecial values true or false. But,the matching COBOL data itemdata-name is not specified on a'CONVERTING BOOLEAN' phraseof the JSON PARSE statement.

ExplanationThe given JSON value was true or false. The valuewas not assigned to the COBOL data item data-name because the data item was not specified on a'CONVERTING BOOLEAN' phrase of the JSON PARSEstatement.




Programmer responseSpecify the data item on a 'CONVERTING BOOLEAN'phrase in the JSON PARSE statement.

Symbolic Feedback CodeIGZ0AM

IGZ0345S Argument-1 for function function-name in program program-nameat displacement displacement wasnot a valid UTF-16 string.

ExplanationArgument-1 is not a valid UTF-16 string.


Programmer responseEnsure that argument-1 is a valid UTF-16 string.

Symbolic Feedback CodeIGZ0AP

IGZ0346S Argument-2 and argument-3 forfunction USUBSTR in programprogram-name at displacementdisplacement was not a validcombination for substring of aUTF-16 string.

ExplanationThe values for argument-2 and argument-3 forfunction USUBSTR were invalid.


Programmer responseEnsure that argument-2 and argument-3 are validfor UTF-16 substring. Argument-2 must be aninteger greater than zero. Argument-3 must be aninteger greater than or equal to zero. (Argument-2+ argument-3 - 1) must be less than or equal toULENGTH(argument-1).

Symbolic Feedback CodeIGZ0AQ

IGZ0347S The stack frame at address stack-address of program program-namein the call chain was invalid.

ExplanationThe stack frame of a COBOL program has beenfound to be corrupted. If the program name canbe determined, it is shown in the message. If thecorruption is extensive and the program name cannotbe determined, it is be shown as "???????".



Programmer responseCorruption was likely to happen at some point beforethe current execution location. Identify and correct thecorruption.

Symbolic Feedback CodeIGZ0AR

IGZ0348S Argument-1 for function function-name in program program-name at displacement program-displacement had a length thatwas not a multiple of multiple-sizebytes.

ExplanationInput argument to the specified function was expectedto have a length that is a multiple of the specifiednumber of bytes.


Programmer responseIdentify the data with the incorrect length and correctit.

Symbolic Feedback CodeIGZ0AS

IGZ0349S The mantissa in argument-1 forfunction function-name in programprogram-name at displacementprogram-displacement containedmore than 16 digits.

ExplanationThe total number of digits in the mantissa of thefloating point number in argument-1 of the indicatedfunction exceeded 16 digits.


Programmer responseAdjust the number of digits in the mantissa inargument-1 in the failing statement.

Symbolic Feedback CodeIGZ0AT

IGZ0350S Program program-name atdisplacement displacement wasunable to get storage- lengthbytes of storage-type storage fromLanguage Environment.

ExplanationThe request made to obtain heap storage for COBOLWORKING-STORAGE failed from program program-name.


Programmer responseIncrease your region size for running this programor contact your system programmer to ensure thatthe size of the required storage does not exceed themaximum limit set on the system.

Symbolic Feedback CodeIGZ0AU

IGZ0351S An attempt was made to run aCOBOL program with LanguageEnvironment that requires a higherlevel of z/OS Version minimum-version Release minimum-release.

ExplanationA COBOL program was executed on a level ofLanguage Environment that was too low. The COBOLprogram must run with Language Environment whichrequires z/OS Version minimum-version Releaseminimum-release or greater.


Programmer responseRun the program with the supported LanguageEnvironment Version and Release.

Symbolic Feedback CodeIGZ0AV


IGZ0352S A dynamic call to program-object-name failed because the calledsubprogram is not an AMODE 64program.

ExplanationA dynamic call was made from an AMODE 64 COBOLprogram to an AMODE 24 or AMODE 31 program.Only dynamic calls from AMODE 64 COBOL programsto Language Environment-conforming AMODE 64programs are allowed.


Programmer responseChange the called subprogram to a LanguageEnvironment-conforming AMODE 64 program.

Symbolic Feedback CodeIGZ0B0

IGZ0353S A dynamic call to program-object-name failed because the calledsubprogram is not a LanguageEnvironment-conforming AMODE64 program.

ExplanationA dynamic call was made from an AMODE 64 COBOLprogram to an AMODE 64 program that was notLanguage Environment-conforming. The main entrypoint for a Language Environment-conforming AMODE64 program must be CELQSTRT.


Programmer responseChange the called program object to a LanguageEnvironment- conforming AMODE 64 program. If theCOBOL program was bound with assembler programs,the ENTRY binder control statement CELQSTRT may beneeded to identify it as the primary entry point. Thiserror may also occur if some assembler CSECT hasbeen mistakenly identified as the primary entry point.


IGZ0354S A dynamic call to program-object-name failed because the calledsubprogram is not fetchable.

ExplanationA dynamic call was made from an AMODE 64COBOL program to an AMODE 64 C/C++, PL/I orassembler program that was not fetchable. Eitheruse the #pragma linkage directive (C/C++) or theFETCHABLE option (PL/I), or bind with the CELQFMANLE CSECT (assembler) when building the subprogram.This error may also occur if an AMODE 64 programis incorrectly bound with other AMODE 31 or non-Language Environment assembler programs.


Programmer responseChange the called program object to be a LanguageEnvironment- conforming fetchable program.


IGZ0355S Program program-name wasoptimized with a level of theAutomatic Binary Optimizer thatrequires service to be installed onLanguage Environment.

ExplanationAn attempt was made to run a program that wasoptimized with a release or service level of theAutomatic Binary Optimizer that requires maintenanceto be installed on Language Environment, but thatmaintenance has not been installed.


Programmer responseContact your system programmer to ensure that thecorresponding Language Environment maintenancewas installed as was indicated in the recent AutomaticBinary Optimizer version or maintenance that wasinstalled.



IGZ0356I The run-time option option-namewas an invalid COBOL run-timeoption. The option was ignored.

Explanationoption-name was not a valid COBOL run-time option,or was not supported with the combination ofcompilation options that were in effect. The latter mayoccur if LP(64) is used, for example.

System actionThe option option-name is ignored.

Programmer responseCheck and correct the run-time option string.


IGZ0372S Argument argument-number forfunction function-name in programprogram-name on line numberline-number was less than 1 orgreater than 3067671.

ExplanationThe integer date specified must be greater than orequal to 1 which represents a starting date of January1, 1601 and less than or equal to 3,067,671 whichrepresents an end date of December 31, 9999.


Programmer responseCorrect the integer date value in the indicatedstatement.

Symbolic Feedback CodeIGZ0BK

IGZ0373S Argument argument-number forfunction function-name in programprogram-name on line numberline-number was less than 0 orgreater than or equal to 86400.

ExplanationThe standard numeric time specified must be greaterthan or equal to 0 which represents 0 seconds past

midnight at 00:00:00 and less than 86400 whichrepresents the end of day at 23:59:59.


Programmer responseCorrect the standard numeric time value in theindicated statement.

Symbolic Feedback CodeIGZ0BL

IGZ0374S Argument argument-number forfunction function-name in programprogram-name on line numberline-number was less than -1439or greater than 1439.

ExplanationThe magnitude of the offset from UTC (expressed inminutes) specified must be greater than or equal to0 which represents no offset from UTC time and lessthan or equal to 1439 which represents 23 hours and59 minutes offset from UTC time.


Programmer responseCorrect the magnitude of the offset from UTC(expressed in minutes) in the indicated statement.

Symbolic Feedback CodeIGZ0BM

IGZ0375S The contents of the time orthe combined date and timein argument content-argument-number for function function-namein program program-name was notvalid according to the specifiedtime format or combined date andtime format found in argumentformat-argument-number.

ExplanationIf a time format is specified, the contents of thefollowing argument shall be a time in that format. Ifa combined date and time format is specified, the


contents of the following argument shall be a time inthat format.


Programmer responseCorrect the contents of the time or the combined dateand time.

Symbolic Feedback CodeIGZ0BN

IGZ0376S The contents of the date orthe combined date and timein argument content-argument-number for function function-namein program program-name was notvalid according to the specifieddate format or combined date andtime format found in argumentformat-argument-number.

ExplanationIf a date format is specified, the contents of thefollowing argument shall be a date in that format. Ifa combined date and time format is specified, thecontents of the following argument shall be a time inthat format.


Programmer responseCorrect the contents of the date or the combined dateand time.

Symbolic Feedback CodeIGZ0BO

IGZ9900I Message message-number ismissing.

ExplanationThe currently installed COBOL runtime library doesn'thave this message. When the PTF containing thismessage is installed, it will display normally.


Programmer responseLook up the message number in the documentation tounderstand the reason of the original message.

Updates to the book z/OS Language EnvironmentRuntime Messages might be delayed. Search forwebpage 'COBOL Message 2005368' at ibm.com.This is an online documentation with title 'New Run-Time Messages for Enterprise COBOL V5 and Above',containing updated COBOL Runtime messages.

Symbolic Feedback CodeIGZ9LC

IGZ9901I Message message-number ismissing. The following are theinserts: insert-1, insert-2, insert-3,insert-4, insert-5, insert-6,insert-7,insert-8.



Programmer responseLook up the message number in the documentationand use the provided inserts to understand the reasonof the original message.


Symbolic Feedback CodeIGZ9LD

IGZ9910W Message message-number ismissing.






Symbolic Feedback CodeIGZ9LM

IGZ9911W Message message-number ismissing. The following are theinserts: insert-1, insert-2, insert-3,insert-4, insert-5, insert-6,insert-7,insert-8.





Symbolic Feedback CodeIGZ9LN

IGZ9920E Message message-number ismissing.





Symbolic Feedback CodeIGZ9M0

IGZ9921E Message message-number ismissing. The following are theinserts: insert-1, insert-2, insert-3,insert-4, insert-5, insert-6,insert-7,insert-8.





Symbolic Feedback CodeIGZ9M1


IGZ9930S Message message-number ismissing.





Symbolic Feedback CodeIGZ9MA

IGZ9931S Message message-number ismissing. The following are theinserts: insert-1, insert-2, insert-3,insert-4, insert-5, insert-6,insert-7,insert-8.





Symbolic Feedback CodeIGZ9MB

IGZ9940C Message message-number ismissing.





Symbolic Feedback CodeIGZ9MK

IGZ9941C Message message-number ismissing. The following are theinserts: insert-1, insert-2, insert-3,insert-4, insert-5, insert-6,insert-7,insert-8.




Updates to the book z/OS Language EnvironmentRuntime Messages might be delayed. Search forwebpage 'COBOL Message 2005368' at ibm.com.This is an online documentation with title 'New Run-


Time Messages for Enterprise COBOL V5 and Above',containing updated COBOL Runtime messages.

Symbolic Feedback CodeIGZ9ML


Chapter 8. Language Environment abend codes

This topic lists the Language Environment abend codes with descriptions and programmer responses.The hexadecimal equivalent of the abend code is shown in parentheses. Reason codes are shown inhexadecimal with the decimal equivalent in parentheses.

UXXXX (≤4000)

ExplanationThe assembler user exit could have forced an abendfor an unhandled condition. These are user-specifiedabend codes.

System actionTask terminated.

Programmer responseCheck the Language Environment message file formessage output. This will tell you what the originalabend was.

U4012 (X'FAC') Not enough main storageavailable.

ExplanationInsufficient storage was available. Possible reasoncodes are:

Reason codeExplanation

X'7009' (28681)A call to malloc() failed. Storage for environmentvariables could not be obtained.

X'7014' (28692)A call to malloc() failed.

X'7015' (28693)A call to malloc() within __Throw() failed.

X'7016' (28694)Storage could not be allocated for I/O trace table.

X'7017' (28695)Storage could not be allocated for I/O trace filename.

X'70C1' (28865)Insufficient storage was available to allocate thewriteable static area (WSA) and parameter list.

System actionThe routine terminates.

Programmer responseRun the program in a larger region.

U4034 (X'FC2')

ExplanationLanguage Environment condition handling wasbypassed. This could result from an error conditionbeing raised while Language Environment wasdormant.


Programmer responseFollow appropriate problem determinationprocedures.

U4036 (X'FC4')

ExplanationA program check occurred and Language Environmentdetermined that it could not turn the program checkinto a condition.Reason code

ExplanationX'01' (1)

A program check was detected when LanguageEnvironment condition handling was disabled. Onecause for this abend is a program check during anInformation Management System (IMS) call suchas CEETDLI. The address of the EPIE is loadedinto register 2 before the abend is issued. Anothercause for this abend is a program check during aSORT or MERGE that has been initiated by a SORTor MERGE statement in an OS/VS COBOL program.

X'02' (2)A program check was detected and LanguageEnvironment could not determine if the programcheck occurred in the current enclave. The addressof the EPIE is loaded into register 2 before theabend is issued.


X'03' (3)A program check was detected and the LanguageEnvironment runtime option for the enclave isTRAP(OFF). The address of the EPIE is loaded intoregister 2 before the abend is issued.

X'04' (4)A program check was detected and the LanguageEnvironment runtime option for the enclaveis TRAP(OFF) or TRAP(ON,NOSPIE). LanguageEnvironment expected to recover from thisprogram check but was unable to do so. Theaddress of the ESPIE is not loaded into register 2for this case.

X'05' (5)A program check occurred due to a branch intounbacked storage, when the current XPLINK stacksegment was almost full, and the TRAP(ON,SPIE)option was in effect. If the XPLINK stack were notalmost full or TRAP(ON,NOSPIE) were in effect,normal CEE3204 condition handling would haveoccurred for this program check.

X'06' (6)The Language Environment ESPIE exit routine forAMODE 24 or 31 applications received control for aprogram check that occurred while the addressingmode was 64-bit. The address of the EPIE isloaded into register 2 before the abend is issued.

X'07' (7)The Language Environment ESPIE routine wasentered to handle a program interrupt whenLanguage Environment expected the ESTAEroutine to be entered to handle it instead. Theaddress of the EPIE is loaded into register 2 priorto the abend being issued.


Programmer responseFor reason codes 1–3:

• Use the contents of register 2 at the abend to findthe EPIE. The EPIE is a system control block that hasthe value of the registers and the PSW at the timeof the program check. The values in the EPIE can beused to start the problem determination process.

For reason code 4:

• This may be a secondary error. Check any messagesor CEEDUMPs to diagnose the original error. Ifthis program check is the only error then run theprogram with the runtime option TRAP(ON) (orTRAP(ON,SPIE)) to diagnose the original programcheck.

The SPIE has many formats:Offset

Content 0

Eyecatcher: EPIE 8

Value of register 0 C

Value of register 110



Value of register 41C












PSW bits 0–314C

PSW bits 32–6350

Program interruption information:

• ILC (Instruction Length Code)• Interruption code

54Translation exception address if interruption codeis a page fault interrupt code

U4038 (X'FC6')


ExplanationLanguage Environment has encountered a software-raised or user-raised unhandled condition of severity2 or greater and will terminate. If the TERMTHDACTruntime option is set appropriately, a LanguageEnvironment dump (CEEDUMP) will be generated,however, no system dump will be generated for thisabend.

System actionEnclave terminated.

Programmer responseExamine the resulting Language Environment dump(CEEDUMP), if available, or the Language Environmentmessage file to help determine the cause of theunhandled condition. See z/OS Language EnvironmentDebugging Guide for information on collecting andusing Language Environment dumps. See z/OSLanguage Environment Programming Reference fordetails on the TERMTHDACT runtime option.

U4039 (X'FC7')

ExplanationThe U4039 has been issued because the user has setthe TERMTHDACT runtime option to request a systemdump be generated when an unhandled conditionof severity 2 or greater has been encountered, andLanguage Environment will terminate. Note that for asystem dump to be collected you must either use theDYNDUMP runtime option or allocate the appropriatedump DD. See z/OS Language Environment DebuggingGuide for information on collecting system dumps.

System actionLanguage Environment continues with termination.

Programmer responseExamine the resulting Language Environment dump(CEEDUMP) or system dump to help determine thecause of the unhandled condition. See z/OS LanguageEnvironment Debugging Guide for information oncollecting and using Language environment dumpsand system dumps. See z/OS Language EnvironmentProgramming Reference for details on the DYNDUMPand TERMTHDACT runtime options.

U4041 (X'FC9')

ExplanationLanguage Environment message processing tried toissue a dynamic allocation for a data set. The returncode used by the ABEND macro is the same returncode from SVC 99. For an explanation of SVC 99, seez/OS TSO/E Programming Services.


Programmer responseFollow appropriate problem determinationprocedures.

U4042 (X'FCA')

ExplanationUser heap damage was found.Reason code


The error was detected in the heap by theHEAPCHK runtime option.

X'01' (1)The error detected is in a heap pool.

X'02' (2)The error detected is in a heap pool.

X'03' (3)An overlay of a heap check zone was detectedby the HEAPZONES runtime option. The outputrequested was ABEND. The address of the overlayis loaded into register 3 before the abend is issued.

System actionThe routine terminates.

Programmer responseExamine the Language Environment message file,looking for messages that identify where the damageis located.

U4043 (X'FCB')

ExplanationLanguage Environment detected an unrecoverableerror running a COBOL program. Before this abend isissued, Language Environment writes an IGZ messageto the message file with the details of the errorcondition.

Chapter 8. Language Environment abend codes 581


Programmer responseRead the IGZ message in the Language Environmentmessage file to determine the error.

U4080 (X'FF0')

ExplanationThis completion code was issued for one of thefollowing reasons:

1. An error occurred, but the usual error messagecould not be displayed. This error occurred earlyduring initialization or late in termination, whenLanguage Environment could not display themessage. This ABEND is issued from CEEMMSG orCEEKMSG.

2. An error occurred while writing to the LanguageEnvironment message file. This could be a normalmessage file write, or it could be during output ofthe Options Report or Storage Report. This ABENDis issued from CEEMOUTM. Register 9 contains theerrno2 value associated with the write failure.

The reason code associated with the completion codeidentifies the message that could not be displayed oridentifies a write failure. Note that message inserts arenot available.


CEEnnnnnCorresponds to message number CEEnnnnX (X = I,W, E, S, C.)

EDCnnnnnCorresponds to message number EDCnnnnX (X = I,W, E, S, C)

AAAnnnnnUsed for non-CEEnnnnX and non-EDCnnnnXmessages. The Facility ID is not displayed in theABEND reason code, but nnnnn is the messagenumber. This prefix is used for messages normallyissued through CEEMMSG.

BBBnnnnnUsed for non-CEEnnnnX and non-EDCnnnnXmessages. The Facility ID is not displayed in theABEND reason code, but nnnnn is the messagenumber. This prefix is used for messages normallyissued through CEEKMSG.

CEE03492A possible cause is that the standard streamfile descriptors not being made available to anexec()ed application during initialization. If the

standard stream file descriptors are not available,the C stderr stream (file descriptor 2) is effectivelykilled during application startup. If the applicationdoes not redirect stderr, then the first attempt towrite a message or output the first line of eitherthe Options Report or Storage Report will result inan fflush or fwrite failure.

Another possible cause is that the C stderr datasetwas opened prior to a fork() being issued. SinceMVS datasets cannot be propagated to the newforked process, the C stderr stream is effectivelymarked as invalid during fork processing. Afterthis, the first attempt by the child to write amessage or output the first line of either theOptions Report or Storage Report will result in anwrite failure to stderr.

CCCnnnnnUsed for non-CEEnnnnX and non-EDCnnnnXmessages. The Facility ID is not displayed in theABEND rea-son code, but 'nnnnn' is the messagenumber. This prefix is used for messages normallyissued through CEEHSGL.

For more information about the error condition forCEEnnnnX and EDCnnnnX messages, find the messagenumber in one of the message topics in this document.

System actionSee the indicated message for the appropriate systemaction.

Programmer responseCheck if one of the possible causes for the reason codemight be the problem, otherwise see the indicatedmessage for the appropriate programmer response.

U4082 (X'FF2')

ExplanationA second malfunction occurred while handling acondition.Reason code


A second malfunction occurred while trying toinitialize a second math save area.

X'02' (2)A condition was raised before the point where asecond condition could be recorded.

X'03' (3)A condition was raised while LanguageEnvironment was processing a current conditionunder CICS.



Programmer responseThis condition can be fixed by correcting the initialcondition.

U4083 (X'FF3')

ExplanationThe back chain was found in error. The reason codedescribes the most likely cause of the abend.Reason code


A save area loop exists. The save area points toitself or another save area incorrectly points to ahigher save area.

X'02' (2)Traversal of the back chain resulted in a programcheck.

X'03' (3)Under normal conditions, all save area chainsshould end with a save area pointed to byCEECAADDSA. In this case, the save area chainterminated with a back chain pointer of 0.

X'04' (4)Under normal conditions, all save areas arepresumed to be word-aligned. Either a linkagestack has been encountered with the characterstring of "F1SA' (X'C6F1E2C1') in a backwardpointer field of the save area chain, or a misaligned(non-word) boundary save area is in the chain.Examine the save area chain to determine whichis the case.

X'05' (5)A condition was raised before the allocation ofthe main stack frame, or after the main routineterminated.

X'06' (6)The dsa format was not set to up or down.

X'07' (7)The save area chain cannot be reached or is non-existent. The pointer referencing the back chain isset to 0 (register 13).

X'08' (8)A save area on the chain points to itself.

X'09' (9)Under normal conditions, all XPLINK save areasare presumed to be quad-word-aligned (thestarting address must end in 0. Either a linkagestack has been encountered with the character

string of FISA (X'C6F1E2C1' in a backward pointerfield of the save area chain, or a misaligned (non-quad-word) boundary XPLINK save area is in thechain. Examine the save area chain to determinewhich is the case.

X'0F' (15)The save area chain is not intact.

X'10' (16)A save area loop has been detected duringcondition processing.

X'11' (17)During pthread_exit() processing, LanguageEnvironment encountered a save area chain thatterminated with a stack frame pointer of 0.

X'12' (18)The General Purpose Register fix-up routinedetected a save area corruption.

X'13' (19)The module delete service has detected a savearea loop.

X'14' (20)The module load service has detected a save arealoop.

X'15' (21)The AMODE31 dynamic dump routine hasdetected a save area loop.

X'16' (22)The AMODE64 dynamic dump routine hasdetected a save area loop.


Programmer responseFor applications that generate their own save areas,ensure the save areas are chained together correctly;all save areas must be addressable in AMODE(31).It may be helpful to generate a system dumpof the original error by using runtime optionsTERMTHDACT(UAIMM) and TRAP(ON,NOSPIE).

For other types of applications, a storage overlayproblem has probably occurred.

U4084 (X'FF4')

ExplanationThread terminated abnormally.Reason code

Explanation


X'01' (1)A shared resource associated with a memberlibrary-held mutex might have been corrupted.

X'02' (2)Mutex prematurely released

X'03' (3)Infinite loop detected while handlingpthread_cond_timedwait()

X'04' (4)A pause element associated with this thread couldnot be deallocated. Register 3, at the time of theABEND, contains the return code from IEAVDPE orIEA4DPE.

X'05' (5)A PAUSE request (IEAVPSE orIEA4PSE) failed during conditionvariable processing (pthread_cond_wait() orpthread_cond_timedwait()). Register 3, at the timeof the ABEND, contains the return code fromIEAVPSE or IEA4PSE.

X'06' (6)A call to IEAVRPI or IEA4RPI failed withan unexpected return code during conditionvariable processing (pthread_cond_wait() orpthread_cond_timedwait()). Register 3, at the timeof the ABEND, contains the return code fromIEAVRPI or IEA4RPI.

X'07' (7)A call to IEAVRPI or IEA4RPI returned anunexpected pause element state during conditionvariable processing (pthread_cond_timedwait() orpthread_cond_timedwait()). Register 3, at the timeof the ABEND, contains the pause element statefrom IEAVRPI or IEA4RPI.



U4085 (X'FF5')

ExplanationThe GOTO routine encountered an error.Reason code


GOTO is already active.

X'02' (2)The address of the stack frame could not be foundon the save area chain, and no feedback code wasprovided.


Programmer responseEnsure the save areas are active.

U4086 (X'FF6')

ExplanationA library routine could not be loaded.Reason code


Not enough storage to load module.X'02' (2)

Module not found.X'03' (3)

Module not loaded.

System actionProcess terminated.

Programmer responseCorrect the system installation error.

U4087 (X'FF7')

ExplanationA recursive error was detected. A condition was raised,causing the number of nested conditions to exceed thelimit set by the DEPTHCONDLMT option. The reasoncode indicates which subcomponent or process wasactive when the exception was detected.Reason code


Language Environment condition manager was incontrol at the time of the condition.

X'01'(1)While enabling the language specific conditionhandlers a subsequent condition was raised.

X'02' (2)A user handler routine (CEEHDLR) was processinga condition when a subsequent condition wasraised.


X'03' (3)A language-specific condition handler wasprocessing a condition when a subsequentcondition was raised.

X'04' (4)During the Language Environment conditionmanager’s processing of the stack frame thatprecedes the stack frame for the first routine, asubsequent condition was raised.

X'05' (5)While a language-specific event handling wasbeing processed, a subsequent condition wasraised.

X'06' (6)A malfunction occurred while the Debug Tool wasin control.

X'07' (7)While Language Environment was trying to outputa message, a subsequent condition was raised.

X'08' (8)While attempting to output a dump, a subsequentcondition was raised.

X'0A' (10)An abnormal termination exit was in controland Language Environment detected one of thefollowing:

• A program check• An ABEND• A call to CEESGL to signal a condition• Invalid DCT under CICS


Programmer responseIn the case of CEEHDLR routine, recursion canoccur when you use the DEPTHCONDLMT runtimeoption. It may be helpful to generate a systemdump of the original error by using runtime optionsTERMTHDACT(UAIMM) and TRAP(ON,NOSPIE).

For reason code 10, determine the error in theabnormal termination exit.

U4088 (X'FF8')

ExplanationA storage condition occurred during the processingof a storage condition. The reason code indicates therequest type.Reason code

Explanation

X'5B' (91)Stack pointer corrupted at location 1.

X'5C' (92)Stack pointer corrupted at location 2.

X'5D' (93)Stack pointer corrupted at location 3.

X'5E' (94)Stack pointer corrupted at location 4.

X'5F' (95)Stack pointer corrupted at location 5.

X'60' (96)Stack guard field has been modified unexpectedly;stack frame may be corrupted.

X'61' (97)DSA not found in stack

X'62' (98)Previous NAB not in stack

X'63' (99)Stack segment owning the next-available-byte(NAB) could not be found or a DSA backchainpointer did not contain a valid 31-bit addressableaddress. A storage overlay problem has probablyoccurred.DSA backchain pointers must containvalid addresses that can be accessed as is whilein 31-bit addressing mode. For instance, a 24-bitaddress that was obtained by using the BAL orBALR assembler instruction will contain the ILC,CC, and Program Mask in the uppermost byte ofthis address, thus making it an invalid address in31-bit mode.

X'64'–X'6C' (10x)First free storage request terminated with returncode x.

X'6E'–X'74' (110 – 116)Debug Tool storage manager control blockscorrupted.

X'75' (117)During a stack overflow on the Down stack, thestack pointer (register 4) was not within thecurrent Down stack segment.

X'76' (118)The system service IARVSERV was invokedwith the CHANGEACCESS,TARGET_ VIEW=HIDDENoptions to create a guard page for a Down stacksegment. The service returned a nonzero returncode. The reason code returned by the IARVSERVservice is loaded into register 3 before the abend isissued.

X'77' (119)During a stack overflow on the Down stack, theentry point of the routine that caused the overflowcould not be found or a program check occurred


while attempting to access data from the routine'sentry point or PPAs.

X'78' (120)The Get Next Available Byte service (CEEVGTUN)was invoked when the stack direction was down.

X'79' (121)The storage size requested on a stack overflow isinvalid (for example negative or too big).

X'7A' (122)An invalid stack segment was detected duringstack increment processing.

X'7B' (123)An invalid stack segment header was detectedduring stack increment processing.

X'C8'–X'D8' (20x)Second free storage request terminated withreturn code x.

X'12C' (300)A call to CEEVFSTR failed

X'190' (400)There is not enough storage to initialize theMEMCHECK vhm tool.

X'191' (401)There is no more storage to keep the MEMCHECKvhm tool working.

X'3E8'–X'3F8' (100x)Get storage request for stack storage terminatedwith return code x. A reserve stack segmentwas not available or the reserve stack segmentwas already in use, so the out of storagecondition CEE0PD (message CEE0813S) could notbe signalled.

X'400' (1024)An out-of-storage condition has occurred with noreserve stack allocated.

X'800' (2048)An internal service was invoked to change theactive stack to the alternate signal stack. Theservice returned a nonzero return code.

X'801' (2049)The active stack was the alternate signal stack ora user context stack. While changing the activestack, one of the following occurred:

• The system service IARV64 wasinvoked with the REQUEST=CHANGEGUARD,CONVERT=FROMGUARD options to remove theguard page from the alternate signal stack ora user context stack. The service returned anonzero return code.

• An internal service was invoked to change theactive stack. The service returned a nonzeroreturn code.

X'802' (2050)Automatic expansion of the user stack failed.Either MEMLIMIT was exceeded or storage for awork area could not be obtained.

X'803' (2051)The reserve stack is full. Automatic expansion isnot available for this stack.

X'804' (2052)The alternate signal stack or a user context stacksupplied by the application is full. Automaticexpansion is not available for these stacks.

X'805' (2053)An internal service was invoked to change theactive stack to the reserve stack. The servicereturned a nonzero return code.

X'806' (2054)The active stack was the reserve stack. An internalservice was invoked to change the active stack.The service returned a nonzero return code.

X'807' (2055)Automatic expansion of the user stack failed. Thestack has already been expanded to its maximumsize.

X'808' (2056)The system service IARV64 was invoked with theREQUEST=CHANGEGUARD, CONVERT=TOGUARDoptions to create a guard page for the alternatesignal stack or a user context stack. The servicereturned a nonzero return code.

X'809' (2057)An application-managed stack supplied by theapplication is full. Automatic expansion is notavailable for these stacks.

X'80A' (2058)The system service IARV64 was invoked with theREQUEST=CHANGEGUARD, CONVERT=TOGUARDoptions to create a guard page for a user contextstack. The service returned a nonzero return code.

X'80B' (2059)The system service IARV64 wasinvoked with the REQUEST=CHANGEGUARD,CONVERT=FROMGUARD options to remove theguard page from a user context stack. The servicereturned a nonzero return code.

X'80C' (2060)An internal service was invoked to change theactive stack. The service returned a nonzero returncode.

X'BB8'–X'BC8' (300x)Get storage request for stack storage terminatedwith return code x. The out of storage conditionCEE0PD (message CEE0813S) has already beensignalled to allow user condition handlers to freestorage.


nnnCritical condition nnn was signaled, but CEESGLreturned control to the signaller. The signaller doesnot support a retry of the operation, so the moduleterminated.


Programmer responseFor reason codes 91–20x, probable internalmalfunction or storage corruption. For reason code 96,check if the program has any stack buffer overflowissues. For code 1001 or 1004, increase the regionsize or check for infinite recursion. For reason code1024, increase the region size or request a reservestack. Use the STORAGE runtime option to get moreinformation about the environment leading up to theout-of-storage condition or allow a user handler to getcontrol and respond to the condition.

U4089 (X'FF9')

ExplanationDuring attention processing, a request to end the taskwas made.Reason code


A debugging tool was asked to interrupt the codesequence and process the CEE3250 condition.

System actionProcess terminated.

Programmer responseContinue debugging the application using a debuggingtool.

U4091 (X'FFB')

ExplanationAn unexpected condition occurred during the runningof Language Environment condition management.Reason code


A GOTO was made by an enablement routine.

X'02' (2)Invalid return code from a language-specificevent handler was received during enablementprocessing.

X'03' (3)Language Environment condition managementdetected an implicit movement of the resumecursor. Either a GOTO or move resume cursorshould have been used for resumption in adifferent stack frame.

X'04' (4)Invalid return code from a language-specific eventhandler was received.

X'05' (5)A program check was detected while LanguageEnvironment condition manager was in control.

X'06' (6)A request to resume the application was notaccepted. The Language Environment conditionmanager does not accept resumption requestswith conditions, such as abends.

X'07' (7)Invalid return code from a language-specificevent handler was received during stack frameprocessing.

X'08' (8)CEESGL callable service was attempting to signala new condition. A control information block couldnot be allocated for that condition.

X'09' (9)The CEEHDLR routine returned with an invalidfeedback code.

X'0A' (10)The Language Environment library was unable tofind a free control information block for a newcondition. This is a critical error.

X'0B' (11)The error count specified in the ERRCOUNTruntime option has been exceeded.

X'0C' (12)Language Environment signaled a condition thatcould not be resumed. After a resume tookplace, Language Environment again attempted toterminate by signaling an imminent termination.Another resume was attempted and caused anabend.

X'0D' (13)An invalid return code from the Debug Tool wasreceived.

X'0E' (14)An invalid attempt to populate an ISI withqualifying data was detected.


X'0F' (15)A condition token other than CEE000 was returnedfrom a member event handler. The feedback tokenresulted from a new condition being raised.

X'10' (16)A request to extend stack storage could not behonored. A fixed-size stack might currently be inuse.

X'11' (17)A request for library stack storage could not becompleted.

X'12' (18)Stack storage was requested when storagemanagement services were not available.

X'13' (19)A request to extend stack storage could not behonored.

X'14' (20)After being informed of a new condition, thecondition handler indicated an unrecoverable error.

X'15' (21)The maximum depth of condition nesting specifiedin the DEPTHCONDLMT runtime option wasexceeded.

X'16' (22)The resume point was invalid.

X'17' (23)BXITA requested ABEND.

X'18' (24)ABEND without LIBVEC layer.

X'19' (25)A CIBH pointer was expected in HCOM_CIBH=0,but the field contained 0.

X'1A' (26)A PCQ pointer was expected in HCOM_PCQ=0, butthe field contained 0.

X'1B' (27)No matching PCIBH was found because therewas a logic error or the Language Environment iscorrupted.

X'1C' (28)No storage was available for PCIBH.

X'1D' (29)No storage was available for QDATA.

X'1E' (30)No storage was available for SigRetData.

X'1F' (31)An internal call to the MVS function BPX1SPM wasnot successful.

X'20' (32)An internal call to the MVS function BPX1PTR wasnot successful.

X'21' (33)An internal call to the MVS function BPX1SPB wasnot successful.

X'22' (34)CSRL16J tried unsuccessfully to return to theinterrupt point for the signal delivery.

X'23' (35)There was a logic error in Sig safing or theLanguage Environment is corrupted.

X'24' (36)There was an internal logic error or the LanguageEnvironment is corrupted.

X'25' (37)The alternate signal stack supplied by theapplication is full. Automatic expansion is notavailable for alternal signal stacks.

X'26' (38)CEERSN_EMTYCIBH. No Language Environmentcondition information block (CIB) was found to bein use.

X'28' (40)CEERSN_NOCIBH. The chain of LanguageEnvironment condition information blocks (CIB) isempty.

X'29' (41)The BPX1SIA callable service failed whenLanguage Environment was trying to generate asignal.

X'2A' (42)An Internal error occurred in LanguageEnvironment condition management when theOS/390 CSRL16J service failed to resume theinterrupted program. The return code fromCSRL16J is loaded into register 8 at the time theABEND is declared. See z/OS MVS Programming:Assembler Services Reference ABE-HSP for adescription of these return codes.

X'2B' (43)An Internal error occurred in LanguageEnvironment condition management when theRP instruction failed to resume the interruptedprogram.

X'2C' (44)The DBX user (or other user of BPX1PTR orPTRACE) tried to resume the application after aprogram check using an invalid value in register 4or 13. When altering the resume registers after aprogram check using DBX, make sure that register4 or 13 points to a valid stack frame for the currentthread.

X'2D' (45)An Internal error occurred in LanguageEnvironment condition management when trying


to resume an application with an unknown DSAaddress in register 4 or 13.

X'2E' (46)An internal error occurred in LanguageEnvironment when the ESTAE service was unableto establish the ESTAE routine required by theQuick Freeze Exit Routine. The return code fromESTAE (in register 15) is loaded into register 8 atthe time the ABEND is declared, and the reasoncode from ESTAE (in register 10) is loaded intoregister 9. See z/OS MVS Programming: AssemblerServices Reference ABE-HSP for a description ofthese return codes.

X'2F' (47)ESTAE 0 MACRO failed in CEEOPQEX

X'30' (48)HCOM_SAVED_REG14 was 0 when CEEOSIGR gotcontrol

X'31' (49)HCOM_SAVED_REG7 was 0 when CEEOSIGX/Y gotcontrol

X'32' (50)HCOM_SAVED_REG7 was 0 when CEEOSIGZ gotcontrol

X'35' (53)An internal call to the MVS function BPX1SPMwas not successful. BPX1SPM failed because itwas called on the wrong RB (request block) orin the wrong RB state. This error can happenif the Language Environment ESPIE routine getscontrol after a program check occurs on a differentRB than Language Environment is using (forexample, an application does a LINK SVC toanother program that then takes a program check).Applications that can program check or ABEND onnon-Language Environment RBs need to establishtheir own ESPIE/ESTAE to make sure the LanguageEnvironment ESPIE or ESTAE do not get control onan unexpected RB.

X'37' (55)A program check occurred while accessing thefield pointed to by the CEECAA_SAVSTACK_ASYNCfield in the CAA (or the CEELCA_SAVSTACK_ASYNCfield in the LCA for AMODE 64 applications).

X'38' (56)A reserve stack is required.

X'39' (57)An error occurred during the handling phase ofthe condition manager. Language Environment wasunable to fetch the load module that runs C++destructors. This error may occur if there is ashortage of available storage.


Programmer responseIf this abend was caused by a user-written conditionhandler, check the return codes provided to LanguageEnvironment condition manager.

Another source of this problem can be the use ofCEEMRCR with a type_of_move '1' done for acondition handler that is invoked for another conditionhandler.

U4092 (X'FFC')

ExplanationESPIE or ESTAE issued this abend because controlstorage was overlaid. Language Environment conditionmanager could not proceed.Reason code


SPIE/ESPIE routine was detected.X'01' (1)

STAE/ESTAE routine was detected.X'02' (2)

An CAA overlay was detected in a CICS interfaceroutine.

X'03' (3)An EICB overlay was detected in a CICS interfaceroutine.

X'04' (4)An EDB overlay was detected in a CICS interfaceroutine.


Programmer responseDetermine why storage was overlaid.

U4093 (X'FFD')

ExplanationErrors were detected during initialization.


X'04' (4)Storage management could not properly allocatethe initial storage area.


X'08' (8)Language Environment control blocks could not beset up properly.

X'0C' (12)System not supported.

X'10' (16)The application's parameter list could not beprocessed correctly. The parameter list might beinvalid.

X'14' (20)Hardware not supported.

X'18' (24)An error occurred when attempting to process theoptions specified in the application.

X'1C' (28)Stack management could not allocate stack and/orheap storage. Ensure that the REGION size issufficient to run the application. Verify that thestorage sizes specified in the HEAP, ANYHEAP,BELOWHEAP, STACK, LIBSTACK and STORAGEruntime options are reasonable, given the regionsize allocated to the application.

X'20' (32)Program management could not find a module thatwas to be loaded.

X'24' (36)During processing of the DD:CEEOPTS runtimeoptions file, below the line storage could not beallocated. Ensure that the REGION size is sufficientto run the application.

X'28' (40)Program management could not be initializedproperly. Possible reasons are:

• The module CEEPLPKA could not be loaded.• The ALL31(OFF) runtime option is in effect and

below the line storage for library vector tablescould not be allocated.

X'2C' (44)The Language Environment math library could notbe initialized properly.

X'30' (48)Condition management could not be initializedproperly.

X'34' (52)A language-specific event handler returned toinitialization with a feedback code, causingimmediate termination.

X'38' (56)Vector initialization did not succeed.

X'3C' (60)The initial fixed-size stack overflowed.

X'40' (64)Process level ran out of storage.

X'44' (68)Enclave level ran out of storage.

X'48' (72)Thread level ran out of storage.

X'4C' (76)CAA pointer became corrupted.

X'50' (80)PCB pointer became corrupted.

X'54' (84)Assembler user exit malfunctioned.

X'58' (88)Get heap malfunctioned during initialization.

X'5C' (92)Anchor setup malfunctioned.

X'60' (96)The PLIST runtime option conflicts with theoperating system type.

X'64' (100)The Language Environment anchor support wasunavailable.

X'6C' (108)The routine was compiled with an unsupportedrelease of a compiler.

X'70' (112)A load module did not contain a main procedure/function and was invoked without LanguageEnvironment having been previously initialized.

X'74' (116)The primary entry point routine of the root loadmodule was found with Language EnvironmentV1R2 CEESTART, but the rest of the routines inthe load module were not linked with LanguageEnvironment V1R2 (or later) library.

X'7C' (124)An unsupported parameter style was detected.

X'80' (128)Too many files, fetched procedures, controlledvariables in a PL/I routine, or assembler use ofexternal dummy sections caused the total lengthof the PRV to exceed the maximum limit of 4096bytes.

X'84' (132)Library routines required for CICS support arenot defined in the CICS CSD. See z/OS LanguageEnvironment Customization for the library routinesrequired for CICS support. If running a PL/Iapplication with the shared library, see PL/I forMVS & VM Compiler and Run-Time Migration Guidefor instructions on enabling shared library supportunder Language Environment.


X'88' (136)Reinitialization feature is not supported in PL/I-defined preinitialization support.

X'8C' (140)MVS has not installed an anchor pointer; therefore,no anchor support is available.

X'90' (144)The POSIX(ON) runtime option was specified orthe application requires threading services, butLanguage Environment was unable to register itssignal interface routine (SIR). The callable serviceBPX1MSS failed. The reason code from BPX1MSSis loaded into register 3 before the abend is issued.

X'94' (148)A language-specific event handler returned tothread initialization with a return code, causingimmediate termination.

X'98' (152)A bad return code was received from the memberthread initialization exit, causing immediatetermination.

X'A0' (160)Re-entry at the top of an existing LanguageEnvironment runtime environment from a non-Language Environment-conforming driver wasattempted at a different link level than that ineffect when the Language Environment runtimeenvironment was first created. The link level isthe count of LINK or CMSCALL SVCs active withinthe task. Following is an example of when this canhappen:

1. An assembler program calls IGZERRE with theinitialization call.

2. The assembler program calls a COBOL programusing LOAD and BALR.

3. The assembler program calls a COBOL programusing a LINK SVC. When the LINK SVC isperformed on the COBOL program, abendU4093 is issued.

This reason code will also be issued:

• When the RTEREUS runtime option, or callsto ILBOSTP0 or IGZERRE, are used in anIMS message processing region and all of theprograms that receive control from IMS are notpreloaded.

• When using the NORTEREUS runtime optionwithout removing all non-reentrant or non-reusable modules from the preload list and anySTEPLIB.

X'A4' (164)The service routine vector address was nonzerowhen using request modifier value 4 in theExtended Parameter List (EPL) for the INIT

function of the Pre-Init Compatibility Interface(PICI). This is not supported.

X'A8' (168)Pre-Init Compatibility Interface (PICI) initializationwas attempted while a Unix System Servicesmedium weight process was in effect. This is notsupported.

X'AC' (172)POSIX(ON) runtime option in a nested enclave isnot supported.

X'B1' (177)An attempt was made to run an XPLINKapplication under LRR when an XPLINK applicationis not permitted. Set the XPLINK keyword of theCEELRR macro to YES when initializing the LRRenvironment.

X'B2' (178)An attempt was made to run a non-XPLINKapplication with the XPLINK(ON) run time optionspecified under LRR when an XPLINK applicationis not permitted. Set the XPLINK keyword of theCEELRR macro to YES when initializing the LRRenvironment.

X'B8' (184)An XPLINK application cannot be started whileSORT is active. There is no support for SORT in anXPLINK environment.

X'BC' (188)An XPLINK application cannot be started whilePIPI is active. There is no support for PIPI in anXPLINK environment.

X'C0' (192)An XPLINK application cannot be started whileCICS is active. There is no support for CICS in anXPLINK environment.

X'C4' (196)An XPLINK application cannot be started in anested child enclave whose parent enclave is anon-XPLINK environment.

X'C8' (200)The entry point of the XPLINK-compiled implicitcaller of a DLL function could not be found. This isan internal error.

X'CC' (204)The Writeable Static Area (WSA) of the XPLINK-compiled implicit caller of a DLL function could notbe found. This is an internal error.

X'D0' (208)There was an internal error in the format of theImport Export Table (IET) of the XPLINK-compiledimplicit caller of a DLL function.


X'D4' (212)Storage management could not properly allocatean initial below storage area after ALL31(ON) wasassumed.

X'D8' (216)Storage management could not properly allocatethe dummy library stack when PL/I was added toan enclave.

X'E0' (224)The application main routine is XPLINK or theXPLINK(ON) runtime option was specified whilerunning on VM. XPLINK is not supported on VM.

X'E4' (228)Language Environment detected that the LibraryRoutine Retention (LRR) control block eye-catcher was damaged during initialization of theenvironment.

X'E8' (232)Language Environment was unable to obtainstorage for the heap pools trace table. This storageis obtained when the HEAPCHK(ON) runtimeoption in effect and suboption pool_call_level isgreater than zero. The failure is most likely dueto there being insufficient available storage inthe address space. Ensure that the REGION (andMEMLIMIT for AMODE 64 environment) size(s) aresufficient to run the application.

X'EC' (236)Allocation of a thread-specific data controlblock (enclave level) failed, causing immediatetermination.

X'F0' (240)Allocation of a thread-specific data controlblock (thread level) failed, causing immediatetermination.

X'F4' (244)The CEEBXITA user exit was not found.

X'F8' (248)Language Environment has detected a mismatchof runtime modules. Check to ensure that runtimemodules CEEBINIT, CEEPIPI, CEEBPICI, andCEEPLPKA are at the same release level.

X'FC' (252)A POSIX(ON) program was called undera preinitialization environment created byCEEPIPI(init_main_dp).

X'200' (512)Language Environment was unable to obtain thelibrary storage (control blocks) during initializationof the AMODE 64 runtime environment. Ensurethat the MEMLIMIT size is sufficient to run theapplication.

X'204' (516)Language Environment detected a re-initializationrequest while the AMODE 64 environment wasalready initialized. This failure is most likely dueto a request to create a nested enclave (main tomain). Nested enclaves are not supported in theAMODE 64 environment.

X'208' (520)The length of the parameter list passed to theAMODE 64 application exceeded the maximumallowable size of 64K.

X'20C' (524)Language Environment was unable to obtainstorage for the extended parameter list. When thelength of the parameter list exceeds 256 bytes, aseparate storage request is needed. The failure ismost likely due to there being insufficient availablestorage in the address space. Ensure that theMEMLIMIT size is sufficient to run the application.

X'210' (528)Language Environment was unable to obtain initialstack and heap for the AMODE 64 environment.The failure is most likely due to there beinginsufficient available storage in the address space.Ensure that the MEMLIMIT size is sufficient to runthe application.

X'214' (532)Language Environment failed unexpectedly.Possible problems include returning from AMODE64 environment termination and failure to setthe active CEELAA address in the PSA whenpreinitialized environments are used.

X'218' (536)Language Environment initialization was requestedfor an AMODE 64 application that does not containa main. Specifically, the CELQMAIN CSECT is notpresent in the program object or the CELQMAINCSECT does not point to the main routine (theaddress of the main is zero). One possible causeis that the user attempted to invoke a DLL orfetchable routine as a main.

X'21C' (540)Load of the AMODE 64 Language Environmentlibrary CELQLIB failed. One possible cause is thatthe SCEERUN2 data set was not in the programsearch order.

X'220' (544)Language Environment was unable to performinitialization for a pthread.

X'224' (548)The 64-bit virtual limit (MEMLIMIT) was 0. Thissetting prevents the initialization and executionof an AMODE 64 application under LanguageEnvironment since storage above 2GB cannot beallocated. SMFPRMxx parameter MEMLIMIT, JCL


JOB statement keyword MEMLIMIT, and JCL EXECstatement MEMLIMIT keyword are some of themechanisms for setting the amount of 64-bitvirtual storage that can be allocated in the addressspace. See z/OS MVS Programming: ExtendedAddressability Guide for more information onsetting MEMLIMIT and how the system determineswhat value to use.

X'228' (552)Language Environment initialization failedattempting to parse PLIST(HOST) style inputarguments.

X'22C' (556)Language Environment was unable to obtainstorage for a copy of the _CEE_HEAP_MANAGERenvironment variable while initializing the AMODE64 environment that is to be run with CELQMCHK,or other vendor heap manager, in control. Ensurethat the MEMLIMIT size is sufficient to run theapplication.

X'230' (560)Language Environment was unable to obtainstorage for a copy of the storage managementroutine address while initializing the AMODE 64environment that is to be run with CELQMCHK,or other vendor heap manager, in control. Ensurethat the MEMLIMIT size is sufficient to run theapplication.

X'234' (564)Language Environment was unable to obtainthe 31-bit addressable storage needed duringinitialization of the AMODE 64 environment. Thisstorage is used during initialization and later duringexecution for low-level I/O operations. Ensure thatthe REGION size is sufficient to run the application.

X'3E8'–X'4E7' (1000–1255)Unable to load event handler for a high-levellanguage. The last 3 digits of the decimal reasoncode indicate the facility ID of the component thatdid not load correctly.

The name of the event handler for which the loadwas attempted is constructed as follows:

• CEEEVxxx for non-XPLINK event handlers.• CELHVxxx for XPLINK event handlers.

In both cases, xxx is the 3 digits described above.

For example, CEEEV003 is the non-XPLINK C/C++event handle, and CELHV003 is the XPLINK C/C++event handler. If either of these cannot be loaded,the reason code will be X'3EB' (1003).

The load may have failed because the correctdata set containing the event handler wasnot found in the search concatenation. Forexample, CELHV003 is contained in the Language

Environment SCEERUN2 data set, which typicallyis part of your STEPLIB or LINKLST.

For CICS applications, make sure you have addedthe Language Environment program resourcedefinitions for CICS using the CEECCSD memberin the Language Environment SCEESAMP data set.

For more information on setting up LanguageEnvironment, see z/OS Language EnvironmentCustomization.

X'500' (1280)When a 31-bit program that specified thePOSIX(ON) runtime option was calling a 64-bitprogram, Language Environment was unable toinitialize a 64-bit environment and reenable the31-bit signal interface routine (SIR). The callableservice BPX1MSS failed. The reason code fromBPX1MSS is loaded into register 3 before theabend is issued.

X'7D0' (2000)For a Fortran application, a call to CEEARLU thatthe Language Environment CAA does not exist.


Programmer responseCorrect any specific conditions described in theexplanation of the reason code that was issued. Checkthe JOBLOG for any messages issued before theabend.

U4094 (X'FFE')

ExplanationAn abend was issued during termination, when errorswere detected.Reason code


An invalid parameter to termination services wasdiscovered.

X'08' (8)A language-specific event handler returned aninvalid return code.

X'0C' (12)A language-specific event handler returned totermination with a return code, causing immediatetermination.

X'10' (16)Condition management could not properlyterminate.


X'14' (20)Program management could not properlyterminate.

X'18' (24)Storage management could not properly free stackand/or heap storage. This might be due to writingbeyond storage.

X'1C' (28)Storage management could not properly free theinitial storage allocation.

X'20' (32)The user stack was unable to be collapsed usingGOTO.

X'24' (36)The fixed-size termination stack overflowed.

X'28' (40)An unhandled condition of severity 2 or greateroccurred in a created enclave with TRAP(OFF) setin the creating enclave. Under CMS, this abend isissued when a severity 2 or greater condition isunhandled in a nested enclave, or a debugging toolhas terminated the enclave at the user's request.

In addition to TRAP(OFF), this abend can alsoresult when a parent enclave save area chaincannot be located, even though two enclavesexisted, thus causing an attempt to propagate thefailing condition. When the parent enclave receivedcontrol, the save area chain was not intact, and theABEND was percolated.

An example of this is a COBOL program that isinvoked without a LINK SVC and with a reusableruntime environment. On return from the COBOLprogram, the Language Environment enclave stillexists, because of the reusable environment. Whena second COBOL program is invoked by a LINKSVC, any Language Environment attempt to createa second enclave does not succeed. In an attemptto propagate this error condition to the parentenclave, Language Environment issues an abend.When the first enclave is not in the currentsave area chain, Language Environment percolatesthis abend. See z/OS Language EnvironmentProgramming Guide for information about nestedenclaves.

X'2C' (44)Termination requested during termination.

X'30' (48)Condition management for MVS could not properlyterminate.

X'34' (52)The MVS environment could not properlyterminate.

X'38' (56)A language-specific event handler returned tothread termination with a return code, causingimmediate termination.

X'3C' (60)An internal logic error occurred during recursivetermination handling.

X'40' (64)An internal logic error occurred during forcedthread termination handling.

X'44' (68)An internal logic error occurred becausetermination was not expected.

X'48' (72)During termination, library latches were being heldand could not be released, causing immediatetermination.

X'4C' (76)Library latch services have received anunrecognized latch request, causing immediatetermination.

X'4E' (78)A language-specific event handler returned tothread termination with a return code, causingimmediate termination.

X'54' (84)Storage management could not properly free thedummy library stack that was added when PL/Iwas active in an enclave.

X'58' (88)This error occurred when attempting to usemalloc(), free(), calloc(), or realloc()after vendor heap manager (VHM) terminated forthe enclave and heap manager is active. This maybe an IBM problem. Contact IBM support.

X'5C' (92)Abend when heap latch locked. A 04E ABEND codeoccurred while a Language Environment heap latchwas held. The code that was holding the latch wasunexpectedly interrupted by this asynchronousabend, and the Language Environment heap isin an unknown state. The 04E ABEND probablyoccurred because of problems on some other taskor in some other address space. Determine theunderlying problem that caused the other taskor address space to send the 04E ABEND tothis thread. Language Environment terminates withan abend immediately with 4094-96 to preventother problems that would occur if recovery wasstarted with the Language Environment heap in anunknown state

X'60' (96)04E abend and latch was locked. An 04E ABENDcode occurred while a Language Environment


library latch was held. The code that washolding the latch was unexpectedly interruptedby this asynchronous abend, and some LanguageEnvironment resource protected by the latch isin an unknown state. The 04E ABEND probablyoccurred because of problems on some other taskor in some other address space. Determine theunderlying problem that caused the other taskor address space to send the 04E abend to thisthread. Language Environment terminates with anabend immediately with 4094-96 to prevent otherproblems that would occur if recovery was startedwith the Language Environment resource is in anunknown state

X'64' (100)Access failure occurred when attempting tocleanup mutexes on behalf of the application attermination. Please make sure all mutexes aredestroyed before application termination. Or makesure all mutexes are valid, and have valid storagebacking at termination.

X'68' (104)Access failure occurred when attempting tocleanup mutexes on behalf of the application attermination. Please make sure all mutexes aredestroyed before application termination. Or makesure all mutexes are valid, and have valid storagebacking at termination.

X'6C' (108)The application was waiting on a mutex thatappeared to be locked after all other threads hadended. This wait would hang indefinitely, so it wasconverted to an abend to avoid the hang. In mostsituations, the thread that originally held the mutexended abruptly with a 422 abend, and the mutexwas not cleaned up. This abend can be ignoredsince one or more other threads in the applicationhas already been ended with a 422 abend.

X'70' (112)The application was waiting on a LanguageEnvironment fast latch that appeared to be lockedafter all other threads had ended. This wait wouldhang indefinitely, so it was converted to an abendto avoid the hang. In most situations, the threadthat originally held the fast latch ended abruptlywith a 422 abend, and the fast latch was notcleaned up. This abend can be ignored since one ormore other threads in the application has alreadyended with a 422 abend.

X'74'(116)A library mutex was being held when anasynchronous abend or unhandled conditioncaused termination. The mutex was marked asreleased prematurely and any attempt to lock themutex caused termination to be entered again.

After several attempts to terminate, this abend isissued to prevent an infinite loop.

X'84' (132)During pthread_mutex_lock() processing,the application was waiting on a LanguageEnvironment fast latch that appeared to be lockedafter all other threads had ended. This wait wouldhang indefinitely, so it was converted to an abendto avoid the hang. In most situations, the threadthat originally held the fast latch ended abruptlywith a 422 abend, and the fast latch was notcleaned up. This abend can be ignored since one ormore other threads in the application has alreadyended with a 422 abend.

X'88' (136)A 04E abend was issued because of a problemwith another task or another address space whileLanguage Environment was holding or waiting for alibrary latch. Language Environment is terminatedimmediately with a 4094 abend, reason codeX'88', to prevent additional errors that mightoccur if recovery is attempted with the LanguageEnvironment resource in an unknown state.To correct this error, determine the underlyingproblem that caused the other task or otheraddress space to issue the 04E abend to theLanguage Environment thread.

X'8C' (140)The application was waiting on a LanguageEnvironment latch that appeared to be locked afterall other threads had ended. This wait would hangindefinitely, so it was converted to an abend toavoid the hang. In most situations, the thread thatoriginally held the latch ended abruptly with a 422abend, and the latch was not cleaned up. Thisabend can be ignored since one or more otherthreads in the application has already ended with a422 abend. The address of the latch is loaded intoregister 3 before the abend is issued.

X'90' (144)Resource Recovery Services was not able toprocess the request from Language Environment tobackout in-flight units of recovery for threads thatare being processed during quiesce term.

X'200' (512)An error occurred while releasing storage attermination of an AMODE 64 application. Capture asystem dump of the failure.

X'204' (516)An error occurred while terminating the C runtimelibrary of an AMODE 64 application. Capture asystem dump of the failure.


X'208' (520)An error occurred while terminating the C runtimelibrary of an AMODE 64 application. Capture asystem dump of the failure.

X'20C' (524)An error occurred while deleting the LanguageEnvironment ESPIE, ESTAE, or both whenterminating an AMODE 64 application. Capture asystem dump of the failure.

X'210' (528)An error occurred while deleting the debuggerwhen terminating an AMODE 64 application.Capture a system dump of the failure.

X'214' (532)An error occurred while deleting the profiler whenterminating an AMODE 64 application. Capture asystem dump of the failure.

X'218' (536)An error occurred during termination of an AMODE64 application. Capture a system dump of thefailure.

X’400’ (1024)Termination due to unhandled condition occurredin secondary Language Environment in AMODE 31and AMODE 64 interoperating programs.

X’404’ (1028)An error occurred during termination of thesecondary Language Environment in AMODE 31and AMODE 64 interoperating programs.


Programmer responseSee system programmer.

U4095 (X'FFF')

ExplanationAn abend was issued as a response to the fatalreturn code of a Language Environment-conforminglanguage.Reason code

Explanation<X'12C' (< 300)

The reason code is set to the LanguageEnvironment-conforming language ID.

X'12C' (300)The condition was provoked from a user handlerattention routine.

X'12D' (301)The condition was provoked from a user handlerroutine.


Programmer responseSee system programmer.


Chapter 9. Language Environment errno2 values

This section contains information about Language Environment errno2 values. You can also receive thisinformation by using the Language Environment edcmtext utility, which is similar to the bpxmtext utility.For more information about these utilities, see z/OS Language Environment Debugging Guide and z/OSUNIX System Services Command Reference, respectively.

C0010001

ExplanationThe stream pointer passed to the fwide() function isnull and posix is enabled.

Programmer responsePass a non null stream pointer to fwide().

Symbolic Feedback CodeJrEdcFwidEbadf01

C0010002

ExplanationThe stream pointer passed to the fwide() function isnot a valid file pointer and posix is enabled.

Programmer responsePass a valid file pointer to fwide().


C0010003

ExplanationThe stream passed to the fwide() function does nothave a valid orientation.

Programmer responsePass a stream to fwide() with a valid orientation.


C001000C

ExplanationThe stream passed to the fwide() function has eitherbeen opened as type=record or type=blocked or refersto a VSAM data set or a CICS transient data queue.

Programmer responsePass a valid stream to fwide().

Symbolic Feedback CodeJrEdcFwidEinval01

C0010015

ExplanationThe stream pointer passed to the fwide() function isnull and posix is not enabled.


Symbolic Feedback CodeJrEdcFwidEnotopen01

C0010016

ExplanationThe stream pointer passed to the fwide() function isnull and posix is not enabled.


Symbolic Feedback CodeJrEdcFwidEnotopen02

C0010021

ExplanationThe fwide() function was called on a thread other thanthe one that opened the stream.


Programmer responseUse the proper thread to access the stream or do notuse the samethread keyword on the open.

Symbolic Feedback CodeJrEdcFwidEwrongthd01

C0010022

ExplanationThe fwide_unlocked() function was called on a threadother than the one that opened the stream.


Symbolic Feedback CodeJrEdcFwidEwrongthd02

C004000E

ExplanationThe stream pointer passed to fldata() is not a valid filepointer and posix is enabled.

Programmer responsePass a valid stream pointer to fldata().

Symbolic Feedback CodeJrEdc1fldEbadf01

C004000F

ExplanationThe file passed to the function fldata() does not have afile category and posix is enabled.

Programmer responsePass a file to fldata() with a file category.

Symbolic Feedback CodeJrEdc1fldEbadf02

C0040018

ExplanationCould not allocate enough memory to hold the data setname in function fldata() and posix is enabled.

Programmer responseFree up more resources for fldata() to run successfully.

Symbolic Feedback CodeJrEdc1fldEnomem01

C0040021

ExplanationCould not allocate enough memory to hold the data setname in function fldata() and posix is not enabled.

Programmer responseFree up more resources for fldata() to run successfully.

Symbolic Feedback CodeJrEdc1fldEnomemory01

C004002A

ExplanationThe stream pointer passed to fldata() is not a valid filepointer and posix is not enabled.

Programmer responsePass a valid stream pointer to fldata().

Symbolic Feedback CodeJrEdc1fldEnotopen01

C004002B

ExplanationThe file passed to the function fldata() does not have afile category and posix is not enabled.

Programmer responsePass a file to fldata() with a file category.

Symbolic Feedback CodeJrEdc1fldEnotopen02

C0040031


ExplanationThe __fldata_a() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdc1fldEwrongthd01

C0040032

ExplanationThe __fldtata_unlocked_a() function was called on athread other than the one that opened the stream.



C0040033

ExplanationThe fldata() function was called on a thread other thanthe one that opened the stream.



C0040034

ExplanationThe fldtata_unlocked() function was called on a threadother than the one that opened the stream.



C0090030

ExplanationThe mode argument passed to fopen() or freopen()specified type=blocked, but the open file is a UNIX filewhich is not support with the type=blocked keyword.

Programmer responseCorrect the mode argument. UNIX files do not supportthe type=blocked open mode. Remove type=blockedkeyword.

Symbolic Feedback CodeJrEdc1ohfEbadmode01

C00B0001

ExplanationThe specified record format is not compatible with theexisting record format. This failure occurred trying toopen an existing OS file for write.

Programmer responseCorrect the mode argument.

Symbolic Feedback CodeJrEdc1opsEexisting01

C00B0002

ExplanationThe existing PDS(E), lrecl, and blksize were specified,but the specified lrecl or blksize is not compatible withthe existing lrecl or blksize. This failure occurred tryingto open an existing PDS or PDSE for write.

Programmer responseCorrect the mode argument. For a PDS, the lrecl andblksize must be the same. For a PDSE, the lrecl mustbe the same, but the blksize may be different.


C00B0003

Chapter 9. Language Environment errno2 values 599

ExplanationA member of a partitioned data set is being openedfor write. The lrecl or blksize specified do not matchthat of the existing data set. An exception would bea specified blksize of 0. This failure occurred trying toopen an existing OS file for write.

Programmer responseCorrect the mode argument. Attributes specified for apartitioned data set must match those of the existingdata set, even when opening a member in write mode.


C00B0004

ExplanationA member of a partitioned data set is being opened forwrite. The blksize specified does not match that of theexisting data set. An exception would be a specifiedblksize of 0. This failure occurred trying to open anexisting OS file for write.

Programmer responseCorrect the mode argument. Attributes specified for apartitioned data set must match those of the existingdata set, even when opening a member in write mode.


C00B0005

ExplanationAn existing PDS(E) directory is being opened for read.The mode argument passed to fopen() or freopen()specified a record format that does not match theexisting data set. The specified record format mustmatch either the record format in the DCB or therecord format in the DSCB.

Programmer responseCorrect the application.


C00B0006

ExplanationAn existing OS data set is being opened for reador append. The mode argument passed to fopen()or freopen() specified a record format that does notmatch the existing data set. The specified recordformat must match the record format in the DCB.



C00B0007

ExplanationAn existing OS data set is being opened for read orappend. The record format is fixed and blocked. Theeffective blksize is not a multiple of lrecl.



C00B0008

ExplanationAn existing OS data set is being opened for read orappend. The record format is fixed and not blocked.The effective lrecl does not match blksize.



C00B0009

ExplanationAn existing OS data set is being opened for reador append. The record format is variable and notspanned. The effective lrecl is larger than blksize - 4.




C00B000A

ExplanationAn existing OS data set is being opened for reador append. The record format is variable. The modeargument passed to fopen() or freopen() specifiedlrecl=X. The mode argument specified update orappend. The logical record length in the DCB is notLRECLX.



C00B000B

ExplanationAn existing PDS(E) directory is being opened for read.The record format is undefined. The mode argumentpassed to fopen() or freopen() specified a blksize thatdoes not match the existing data set. The specifiedblksize must match either the blksize in the DCB or theblksize in the DSCB.



C00B000C

ExplanationAn existing OS data set is being opened for read orappend. The record format is undefined. The modeargument passed to fopen() or freopen() specified ablksize that does not match the existing data set.



C00B0021

ExplanationThe mode argument passed to fopen() or freopen() didnot begin with r, w, or a.

Programmer responseCorrect the mode argument. The first keyword of themode argument must be the open mode. Ensure theopen mode is specified first and begins with r, w, or a.

Symbolic Feedback CodeJrEdc1opsEinval01

C00B0022

ExplanationThe mode argument passed to fopen() or freopen()contained more information than just the open mode,but did not use a comma to separate the additionalkeywords.

Programmer responseCorrect the mode argument. White-space charactersare not permitted within the open mode. The't' specification is not allowed for POSIX(OFF)applications. Separate the open mode from theremaining keywords with a comma. Note that it couldbe possible that the open mode itself is not correct.


C00B0023

ExplanationThe mode argument passed to fopen() or freopen()contained one or more syntax errors.



C00B0051

ExplanationThe filename argument passed to fopen() or freopen()specified '*' as the first character of the filename, indicating to open a terminal file or sysoutdata set. The program is not running in an


interactive environment, meaning not under TSO inthe foreground. This implies a sysout data set is tobe opened. An out of memory error occurred trying toallocate a DCB.

Programmer responseTry making more below-the-line storage available tothe program. If that does not work, contact IBMsupport.

Symbolic Feedback CodeJrEdc1opsEnomemory01

C00B0052

ExplanationThe filename argument passed to fopen() or freopen()specified '*' as the first character of the filename, indicating to open a terminal file or sysoutdata set. The program is not running in aninteractive environment, meaning not under TSO inthe foreground. This implies a sysout data set is tobe opened. An out of memory error occurred tryingto allocate a thread specific below-the-line I/O workarea.



C00B0053

ExplanationAn out of memory error occurred trying to allocate afile specific below-the-line control block for a terminalfile.



C00B0054

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The ddname does notexist on the open file chain. We have to allocate aDCB in order to read the JFCB. An out of memory erroroccurred trying to allocate a DCB.



C00B0055

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The ddname does notexist on the open file chain. We have to allocate athread specific below-the-line I/O work area to readthe JFCB. An out of memory error occurred tryingto allocate a thread specific below-the-line I/O workarea.



C00B0056

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. We have to allocate aDCB in order to read the JFCB. An out of memory erroroccurred trying to allocate a DCB.




C00B0057

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. We have to allocate athread specific below-the-line I/O work area to readthe JFCB. An out of memory error occurred tryingto allocate a thread specific below-the-line I/O workarea.



C00B0058

ExplanationAn out of memory error occurred trying to allocate aDCB.



C00B0059

ExplanationAn out of memory error occurred trying to allocate athread specific below-the-line I/O work area.



C00B005A

ExplanationAllocation of a memory file control block failed.

Programmer responseTry to make more storage available to the program. Ifthat does not work, contact IBM support.


C00B005B

ExplanationAllocation of a memory file control block failed.



C00B005C

ExplanationAllocation of a hiperspace memory file control blockfailed.



C00B005D





C00B005E




C00B005F




C00B0061




C00B0062

ExplanationAn out of memory error occurred trying to allocate theOS I/O control block.



C00B0063

ExplanationAn out of memory error occurred trying to allocate aDCBE.



C00B0064

ExplanationAn out of memory error occurred.



C00B0065

ExplanationAn out of memory error occurred.



C00B0066

ExplanationAn out of memory error occurred trying to allocate aJFCB.




C00B0067

ExplanationAn out of memory error occurred trying to allocate theOS I/O control block extension.

Programmer responseTry making more storage available to the program. Ifthat does not work, contact IBM support.


C00B0068

ExplanationAn out of memory error occurred trying to allocate aDCB.



C00B0069

ExplanationAn out of memory error occurred trying to allocate aDCBE.

Programmer responseTry making more storage available to the program. Ifthat does not work, contact IBM support.


C00B00A1

ExplanationThe program called freopen() with an empty filenamestring. The mode argument specified a write or appendmode. The mode argument specified type=memoryor type=memory(hiperspace). The file being reopenedalready exists on the open file chain, however it is nota memory file. You cannot request to reopen a file as amemory file in write or append mode if the file is not amemory file.


Symbolic Feedback CodeJrEdc1opsEnotmemory01

C00B00A2

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a memory file with a membername. A file of the same name does exist, but it is nota memory file.



C00B00A3

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a memory file with a membername. A file with the same base name (a parent) doesexist, but it is not a memory file.



C00B00A4

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a memory file. A file with thesame name already exists, but it is not a memory file.




C00B00A5

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a hiperspace memory file. A filewith the same name already exists, but it is not ahiperspace memory file.



C00B0101

ExplanationThe mode argument passed to fopen() or freopen()specified type=record, but the open mode did notspecify binary.

Programmer responseCorrect the mode argument. Record I/O requires abinary open mode. Either remove type=record orspecify a binary open mode.

Symbolic Feedback CodeJrEdc1opsEbadmode01

C00B0102

ExplanationThe mode argument passed to fopen() or freopen()specified both recfm=+ and append mode. This is not avalid combination.



C00B0103

ExplanationThe program called freopen() with an empty filenamestring. The mode argument specified type=memory.The name of the file being reopened begins with '*',which is not possible for a memory file. You cannotspecify type=memory when reopening a file that is nota memory file.



C00B0104

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname(member) syntax that referred toa DASD data set, but the mode argument specifiedappend or write/update. It is not valid to open a PDS orPDSE member in append or write/update mode. Thisfailure occurred trying to open a DASD data set.

Programmer responseCorrect the filename or mode argument.


C00B0105

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax that referred to a tapedata set, but the data set spans more than one volumeand the mode argument specifies append. This failureoccurred trying to open a tape data set.



C00B0106

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax that referred to a


concatenation, but the mode argument did not specifyread. A concatenation can only be opened in readmode.



C00B0107

ExplanationThe filename argument passed to fopen() or freopen()specified dsname(member) syntax, but the modeargument specified append or write/update, orspecified a fixed standard record format.

Programmer responseCorrect the mode argument. A PDS or PDSE data setcannot be opened in a, ab, a+, a+b, w+, w+b, or wb+. Astandard fixed record format cannot be specified for aPDS or PDSE member.


C00B0108

ExplanationThe filename argument passed to fopen() or freopen()specified an existing memory file name, but the modeargument specified type=record.

Programmer responseCorrect the mode argument. Existing memory file I/Ocannot be specified with type=record. To open anexisting memory file, type=memory must be specified.


C00B0109

ExplanationThe existing PDS(E) member was specified, but theopen mode specified append or write/update or themode argument specified a standard fixed recordformat.

Programmer responseCorrect the mode argument. A PDS(E) member cannotbe opened in a, ab, a+, a+b, w+, w+b, or wb+. Astandard fixed record format cannot be specified fora PDS(E) member.


C00B010A

ExplanationThe record format is specified as fixed, but the lreclwas less than 1 or greater than 32760 or the blksizewas less than 0 or greater than 32760. The failureoccurred trying to open an existing OS file for write.



C00B010B

ExplanationThe record format indicates non-spanned variable, butthe lrecl is greater than 32760 or equal to X. Thisfailure occurred trying to open an existing OS file forwrite.



C00B010C

ExplanationThe record format indicates variable, but the lrecl orblksize is not valid. This failure occurred trying to openan existing OS file for write.

Programmer responseCorrect the mode argument. The lrecl for a variablerecord format data set must be at least 4 or equal toX. The blksize must be at least 8 or 0 and no morethan 32760. The value lrecl=X is sometimes used forspanned data sets.



C00B010D

ExplanationThe record format is undefined. The specified lrecl orblksize was larger than the maximum value of 32760.



C00B010E

ExplanationAn existing OS data set is being opened for read orappend. The record format is fixed. The effective lreclor blksize are out of range.



C00B010F

ExplanationAn existing OS data set is being opened for read orappend. The record format is variable. The effectivelrecl or blksize are out of generic range.



C00B0110

ExplanationAn existing OS data set is being opened for reador append. The record format is variable and notspanned. The effective lrecl is out of range.



C00B0111

ExplanationAn existing OS data set is being opened for read orappend. The record format is undefined. The effectivelrecl or blksize is out of range.



C00B0112

ExplanationAn existing OS data set is being opened for read orappend. The record format is undefined. The effectivelrecl is greater than the effective blksize.



C00B0113

ExplanationA new OS data set is about to be opened. The effectiverecord format is fixed (not blocked). The modeargument passed to fopen() or freopen() specified anlrecl but no blksize. The specified lrecl is out of range.



C00B0114


ExplanationA new OS data set is about to be opened. The effectiverecord format is fixed (including blocked). The modeargument passed to fopen() or freopen() specified ablksize but no lrecl. The specified blksize is out ofrange.



C00B0115

ExplanationA new OS data set is about to be opened. The effectiverecord format is fixed (not blocked). The modeargument passed to fopen() or freopen() specified bothlrecl and blksize. The specified lrecl is out of range.



C00B0116

ExplanationA new OS data set is about to be opened. The effectiverecord format is fixed blocked. The mode argumentpassed to fopen() or freopen() specified an lrecl. Thespecified lrecl is out of range.



C00B0117

ExplanationA new OS data set is about to be opened. The effectiverecord format is fixed blocked. The mode argumentpassed to fopen() or freopen() specified both lrecl andblksize. The specified lrecl is out of range.



C00B0118

ExplanationA new OS data set is about to be opened. Theeffective record format is variable (including blocked).The mode argument passed to fopen() or freopen()specified an lrecl. The specified lrecl is out of range.



C00B0119

ExplanationA new OS data set is about to be opened. Theeffective record format is variable (including blocked).The mode argument passed to fopen() or freopen()specified a blksize The specified blksize is out of range.



C00B011A

ExplanationA new OS data set is about to be opened. Theeffective record format is variable (including blocked).The mode argument passed to fopen() or freopen()specified lrecl=X and blksize, but the record formatdoes not indicate spanned.




C00B011B

ExplanationA new OS data set is about to be opened. Theeffective record format is variable (including blocked).The mode argument passed to fopen() or freopen()specified lrecl=X and blksize. The specified blksize isout of range.



C00B011C

ExplanationA new OS data set is about to be opened. Theeffective record format is variable (including blocked).The mode argument passed to fopen() or freopen()specified an lrecl and blksize=0. The specified lrecl isout of range.



C00B011D

ExplanationA new OS data set is about to be opened. Theeffective record format is variable (including blocked).The mode argument passed to fopen() or freopen()specified an lrecl and blksize. The specified lrecl orblksize is out of range.



C00B011E

ExplanationA new OS data set is about to be opened. The effectiverecord format is undefined. The mode argumentpassed to fopen() or freopen() specified an lrecl. Thespecified lrecl is out of range.



C00B011F

ExplanationA new OS data set is about to be opened. The effectiverecord format is undefined. The mode argumentpassed to fopen() or freopen() specified a blksize. Thespecified blksize is out of range.



C00B0120

ExplanationA new OS data set is about to be opened. The effectiverecord format is undefined. The mode argumentpassed to fopen() or freopen() specified both lrecl andblksize. The specified lrecl or blksize is out of range.



C00B0121

ExplanationThe mode argument passed to fopen() or freopen()specified type=blocked, but the open mode did notspecify binary.


Programmer responseCorrect the mode argument. Blocked I/O requires abinary open mode. Either remove type=blocked orspecify a binary open mode.


C00B0122

ExplanationThe mode argument passed to fopen() or freopen()specified type=blocked and noseek, but type=blockedkeyword is not suported.

Programmer responseCorrect the mode argument. Either removetype=blocked or remove noseek. noseek.


C00B0123

ExplanationThe mode argument passed to fopen() or freopen()specified type=blocked, but the open file is a terminalI/O file which does not support type=blocked keyword.

Programmer responseCorrect the mode argument. Terminal I/O doesnot support type=blocked open mode. Removetype=blocked keyword.


C00B0124

ExplanationThe mode argument passed to fopen() or freopen()specified type=blocked, but the open file is a memoryfiles which does not support type=blocked keyword.

Programmer responseCorrect the mode argument. Memory files donot support type=blocked open mode. Removetype=blocked keyword.


C00B0125

ExplanationThe mode argument passed to fopen() or freopen()specified type=blocked, but the open file is a VSAMdata set which does not support type=blockedkeyword.

Programmer responseCorrect the mode argument. VSAM data sets donot support type=blocked open mode. Removetype=blocked keyword.


C00B0161

ExplanationAn ABEND occurred trying to OPEN an OS data set foroutput.

Programmer responseFailure information was recorded in the AMRCstructure. Use the information there to determine thecause of the failure. Check the JOBLOG for additionalmessages.

Symbolic Feedback CodeJrEdc1opsEabend01

C00B0162

ExplanationAn ABEND occurred trying to OPEN an OS data set.



C00B0163


ExplanationAn ABEND occurred trying to OPEN an OS data set forextend.



C00B0164

ExplanationAn ABEND occurred trying to OPEN an OS data set foroutput.



C00B0165

ExplanationAn ABEND occurred trying to OPEN an OS data set.



C00B01A1

ExplanationA failure occurred trying to OPEN an OS data set foroutput.


Symbolic Feedback CodeJrEdc1opsEopenfail01

C00B01A2

ExplanationA failure occurred trying to OPEN an OS data set.



C00B01A3

ExplanationA failure occurred trying to OPEN an OS data set forextend.



C00B01A4

ExplanationA failure occurred trying to OPEN an OS data set foroutput.




C00B01A5

ExplanationA failure occurred trying to OPEN an OS data set.



C00B0201

ExplanationThe mode argument passed to fopen() or freopen()specified a fixed record format, lrecl, and blksize, butthe blksize was not a multiple of lrecl. This failureoccurred trying to open a terminal file.


Symbolic Feedback CodeJrEdc1opsEbadattr01

C00B0202

ExplanationThe mode argument passed to fopen() or freopen()specified a fixed non-blocked record format, lrecl, andblksize, but the blksize was not equal to lrecl. Thisfailure occurred trying to open a terminal file.



C00B0203

ExplanationThe mode argument passed to fopen() or freopen()specified a variable record format and lrecl, but thelrecl was less than 4. The first 4 bytes of a variablelength record contains either the RDW or SDW, andtherefore requires a minimum length of 4. This failureoccurred trying to open a terminal file.



C00B0204

ExplanationThe mode argument passed to fopen() or freopen()specified a variable record format, lrecl, and blksize,but the blksize was not at least 4 bytes larger than thelrecl. The first 4 bytes of a variable block contains theBDW, and therefore requires a minimum size of lrecl +4. This failure occurred trying to open a terminal file.



C00B0205

ExplanationThe mode argument passed to fopen() or freopen()specified a variable record format and blksize, but theblksize was less than 8. The first 8 bytes of a variableblock contain the 4 byte BDW followed by a 4 byteRDW or SDW, and therefore requires a minimum sizeof 8. This failure occurred trying to open a terminal file.



C00B0206


ExplanationThe mode argument passed to fopen() or freopen()specified an undefined blocked record format. This isnot a valid combination. This failure occurred trying toopen a terminal file.

Programmer responseCorrect the mode argument. Valid attributes foran undefined-format terminal file are recfm=U,recfm=UA, or recfm=UM.


C00B0207

ExplanationThe mode argument passed to fopen() or freopen()specified an undefined record format, lrecl, andblksize, but the blksize was not larger or equal to thelrecl. This failure occurred trying to open a terminalfile.



C00B0208

ExplanationThe record format is specified as fixed blocked, but theblksize was not 0 and was not a multiple of lrecl. Thisfailure occurred trying to open an existing OS file forwrite.



C00B0209

ExplanationThe record format is specified as fixed non-blocked,but the blksize was not 0 and was not equal to lrecl.This failure occurred trying to open an existing OS filefor write.



C00B020A

ExplanationThe record format indicates non-spanned variable, butthe lrecl is greater than the blksize - 4 (and blksize isnot 0). This failure occurred trying to open an existingOS file for write.



C00B020B

ExplanationThe record format is undefined. Blocked was specified,but is not permitted for undefined format data sets.



C00B020C

ExplanationThe record format is undefined. The specified lreclis larger than the specified blksize (when blksize notspecified as 0).



C00B020D


ExplanationAn existing OS data set is being opened for reador append. The mode argument passed to fopen()or freopen() specified recfm=A, but the attributes ofthe existing data set do not include recfm=A. Theattributes must be consistent.



C00B020E

ExplanationAn existing OS data set is being opened for read orappend. The record format is undefined. The effectiverecord format indicates blocked which is not valid forundefined record format data sets.



C00B020F

ExplanationAn existing OS data set is being opened for read orappend. The device type is DASD. The effective blksizeis 0. This is not valid.



C00B0210

ExplanationA new OS data set is about to be opened. The effectiverecord format is fixed (not blocked). The modeargument passed to fopen() or freopen() specified bothlrecl and blksize. The blksize is not zero and does notmatch lrecl.



C00B0211

ExplanationA new OS data set is about to be opened. The effectiverecord format is fixed blocked. The mode argumentpassed to fopen() or freopen() specified both lrecl andblksize. The blksize is not zero and not a multiple oflrecl.



C00B0212

ExplanationA new OS data set is about to be opened. Theeffective record format is variable (including blocked).The mode argument passed to fopen() or freopen()specified lrecl=X, but the record format does notindicate spanned.



C00B0213

ExplanationA new OS data set is about to be opened. Theeffective record format is variable (including blocked).The mode argument passed to fopen() or freopen()specified an lrecl and blksize. The specified lrecl + 4is greater than blksize and the record format does notindicate spanned.




C00B0214

ExplanationA new OS data set is about to be opened. The effectiverecord format is undefined. The mode argumentpassed to fopen() or freopen() specified both lrecl andblksize. The specified blksize is not zero and less thanthe lrecl.



C00B0281

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname(member) syntax where the firstcharacter of the member name indicated a relativename for a Generation Data Group (GDG), but at leastone other character in the relative name is not valid.

Programmer responseCorrect the relative name in the filename argument.The relative name must be +number, -number, or 0.

Symbolic Feedback CodeJrEdc1opsEbadfilename01

C00B0282

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname(member) syntax, but at least onecharacter in the member name is not valid.

Programmer responseCorrect the member name in the filename argument.Characters must be alphanumeric or national. TheX'C0' character is also allowed after the first character.


C00B0283

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The device type checkindicated a DASD data set. The data set organizationindicated a partitioned data set. The mode argumentspecified write, append, or update mode, but nomember name was provided. You cannot open thedirectory for a partitioned data set in any mode, exceptread.



C00B0284

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname(member) syntax, but the JFCBfor the ddname also specifies a member name. This isa conflict, except when the JFCB refers to a relativegeneration of a Generation Data Group (GDG).



C00B0285

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname(member) syntax where the firstcharacter of the member name indicated a relativename for a Generation Data Group (GDG), but at leastone other character in the relative name is not valid.This failure occurred trying to open a DASD data set.

Programmer responseCorrect the relative name in the filename argument.The relative name must be +number, -number, or 0.


C00B0286


ExplanationThe filename argument passed to fopen() or freopen()specified dsname syntax, but one of the qualifiers wasless than 1 or greater than 8 characters in length.



C00B0287

ExplanationThe filename argument passed to fopen() or freopen()specified dsname syntax, but there was at least onecharacter in the data set name that is not valid.



C00B0288

ExplanationThe filename argument passed to fopen() or freopen()specified dsname(member) syntax. The first characterof the member name was '+', '-', or a digit. Thisindicates a relative generation. However, at least oneother character in the member name was not a digit,and therefore not valid.



C00B0289

ExplanationThe filename argument passed to fopen() or freopen()specified dsname(member) syntax. The first characterof the member name was not '+', '-', or a digit.This indicates a regular member name. However, atleast one other character in the member name wasnot alphanumeric, a national character, or X'C0', andtherefore not valid.



C00B028A

ExplanationThe filename argument passed to fopen() or freopen()specified dsname(member) syntax. The first characterof the member name was '+', '-', or a digit. Thisindicates a relative generation. However, at least oneother character in the member name was not a digit,and therefore not valid.



C00B028B

ExplanationThe filename argument passed to fopen() or freopen()specified dsname(member) syntax. The first characterof the member name was not '+', '-', or a digit.This indicates a regular member name. However, atleast one other character in the member name wasnot alphanumeric, a national character, or X'C0', andtherefore not valid.



C00B028C

ExplanationThe filename argument passed to fopen() or freopen()specified a partitioned data set without a membername. The mode argument specified write, append, orupdate. You cannot open the directory for a partitioneddata set in any mode, except read.




C00B028D

ExplanationThe filename argument passed to fopen() or freopen()specified dsname syntax. Allocation of a ddname forthe dsname was attempted, but SVC 99 failed.

Programmer responseFailure information returned from SVC 99 wasrecorded in the AMRC structure. Use the informationthere to determine the cause of the failure. ContactIBM support if you cannot solve the problem.


C00B028E

ExplanationThe filename argument passed to fopen() or freopen()was not valid. This failure is specific to the first passname parsing when it is known the filename cannot bea UNIX file.



C00B028F

ExplanationThe filename argument passed to fopen() or freopen()specified a PDS(member), but there is a sequentialdata set already created with the same PDS name.

Programmer responseCorrect the filename. A sequential data set cannotcontains a member.


C00B0302

ExplanationAn attempt was made to open a multivolume orpotential multivolume data set for read when thedata set is already open for write, append, or update.Simultaneous readers (files that can support sharingby a writer and one or more readers) are not supportedfor multivolume data sets.

Programmer responseChange the application.

Symbolic Feedback CodeJrEdc1opsEnocando02

C00B0303

ExplanationThe sequential dataset attempting to be opened has anon-zero key length, and is not supported.

Programmer responseTry to copy the dataset to a new one without a keylength (can verify with an IEHLIST). Otherwise thistype of dataset is not supported.

Symbolic Feedback CodeJrEdc1opsEnocando03

C00B0351

ExplanationThe filename argument passed to fopen() or freopen()specified '*' as the file name, but the mode argumentspecified update. This failure occurred trying to open aterminal file.

Programmer responseCorrect the mode argument. Terminal files cannot beopened in update mode.

Symbolic Feedback CodeJrEdc1opsEdevmode01

C00B0352

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax that referred to a tapedata set, but the mode argument specified update.This failure occurred trying to open a tape data set.


Programmer responseCorrect the mode argument. A tape data set cannot beopened in update mode.


C00B0353

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The mode argumentspecified write, append, or update. The device typecheck indicated a device that can only be opened forread.



C00B0354

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The mode argumentspecified read or update. The device type checkindicated a device that can only be opened for writeor append.



C00B0355




C00B0356

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The mode argumentspecified write, append, or update. The device typecheck indicated a device that can only be opened forread.



C00B0357




C00B0381

ExplanationThe filename argument passed to fopen() or freopen()specified '*' as the first character of the filename, indicating to open a terminal file or sysoutdata set. The program is not running in aninteractive environment, meaning not under TSO in theforeground. This implies a sysout data set is to beopened. The mode argument specified update modewhich is not allowed for a sysout data set.

Programmer responseCorrect the application so that it does not attempt toopen a sysout data set for update.


Symbolic Feedback CodeJrEdc1opsEsysinout01

C00B0382

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The JFCB indicates aSYSIN or SYSOUT data set. The mode argumentspecified update, but that is not allowed for thesetypes of data sets.



C00B0383

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The JFCB indicates aSYSIN or SYSOUT data set. The mode argument didnot specify read as required for a SYSIN data set.



C00B0384

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The JFCB indicates aSYSIN or SYSOUT data set. SVC 99 identified theddname as a SYSIN data set. The mode argument didnot specify read as required for a SYSIN data set.



C00B0385

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The JFCB indicates aSYSIN or SYSOUT data set. SVC 99 identified theddname as a SYSOUT data set. The mode argumentspecified read, but that is not allowed for a SYSOUTdata set.



C00B03B1

ExplanationThe filename argument passed to fopen() or freopen()specified '*' as the first character of the filename, indicating to open a terminal file or sysoutdata set. The program is not running in aninteractive environment, meaning not under TSO in theforeground. This implies a sysout data set is to beopened. The mode argument specified a read modewhich is not allowed for a sysout data set.

Programmer responseCorrect the application so that it does not attempt toopen a sysout data set for read.

Symbolic Feedback CodeJrEdc1opsEnofile01

C00B03B2

ExplanationThe program called freopen() with an empty filenamestring. The mode argument specified a read mode.The mode argument specified type=memory ortype=memory(hiperspace). The name of the file beingreopened begins with DD: and already exists on theopen file chain, however it is not a memory file. Youcannot request to reopen a file as a memory file inread mode if the file is not a memory file.




C00B03B3

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The mode argumentspecified a read mode. The mode argument specifiedtype=memory or type=memory(hiperspace). The filedoes not exist. You cannot open a memory file for readthat does not exist.



C00B03B4

ExplanationThe program called freopen() with an empty filenamestring. The mode argument specified a read mode.The mode argument specified type=memory ortype=memory(hiperspace). The file being reopenedalready exists on the open file chain, however it is nota memory file. You cannot request to reopen a file asa memory file in read mode if the file is not a memoryfile.



C00B03B5

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a memory file to be openedin read mode, but the file does not exist. This couldbe either a sequential memory file or a non-existentmember of a partitioned memory file.



C00B03B6

ExplanationThe specified member was not found in the partitioneddata set.



C00B0401

ExplanationThe filename argument passed to fopen() or freopen()specified '*' as the first character of the filename, indicating to open a terminal file or sysoutdata set. The program is not running in aninteractive environment, meaning not under TSO in theforeground. This implies a sysout data set is to beopened. A failure occurred trying to allocate the sysoutdata set.

Programmer responseFailure information returned from SVC 99 wasrecorded in the AMRC structure. Use the informationthere to determine the cause of the failure.

Symbolic Feedback CodeJrEdc1opsEfiledef01

C00B0402

ExplanationThe filename argument passed to fopen() or freopen()specified dsname syntax. The mode argumentspecified write or append. The data set does not exist.Allocation of a new data set was attempted, but failed.



C00B0403


ExplanationThe filename argument passed to fopen() or freopen()specified dsname syntax. Allocation of a ddname forthe dsname was attempted, but failed.



C00B0441

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a memory file. The modeargument specifies write, append, or update. It wasfound that the memory file is already open. You cannotopen a memory file for write if it is already open.


Symbolic Feedback CodeJrEdc1opsEisopen01

C00B0442

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a hiperspace memory file. Themode argument specified read update mode. A filewith the same name already exists. It was foundthat the hiperspace memory file is already open. Youcannot open a hiperspace memory file for read updateif the hiperspace memory file is already open.



C00B0443

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a hiperspace memory file. The

mode argument specified write, append, or updatemode. A file with the same name already exists. Itwas found that the hiperspace memory file is alreadyopen. You cannot open a hiperspace memory file forwrite, append, or update if the hiperspace memory fileis already open.



C00B0444

ExplanationThe application requested to open a file for write, butthe file is already open.



C00B0445

ExplanationThe application requested to open a file for write. Thesame base file name (a parent) is already open and isthe directory of a partitioned data set or is a memberof a regular partitioned data set that is opened forwrite. You cannot open multiple members of a regularpartitioned data set for write.



C00B0446

ExplanationThe application requested to open a file for append orupdate, but the same file is already open.




C00B0447

ExplanationThe application requested to open a file for appendor update. The same base file name (a parent) isalready open and the base file is not a PDSE and nota member of a partitioned data set. You cannot opena file for append or update if there already exists anopen file with the same base name unless it is a PDSEor member of a partitioned data set.



C00B0448

ExplanationA new OS data set is about to be opened. The is anexisting match on the open file chain. This is not a validsituation.

Programmer responseContact IBM support.


C00B0481

ExplanationThe filename argument passed to fopen() or freopen()specified '*' as the first character of the filename, indicating to open a terminal file or sysoutdata set. The program is not running in aninteractive environment, meaning not under TSO inthe foreground. This implies a sysout data set is tobe opened. A failure occurred trying to read the JFCBassociated with the sysout data set.

Programmer responseFailure information returned from RDJFCB wasrecorded in the AMRC structure. Use the informationthere to determine the cause of the failure.

Symbolic Feedback CodeJrEdc1opsEutility01

C00B0482

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. An error occurred tryingto obtain device type information. The DEVTYPE macrofailed with return code greater than 4.

Programmer responseFailure information returned from DEVTYPE wasrecorded in the AMRC structure. Use the informationthere to determine the cause of the failure.


C00B0483

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. An error occurred tryingto read the JFCB. The RDJFCB macro failed.



C00B0484

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The device type checkindicated a DASD data set. The JFCB did notcontain information about the data set organization.A failure occurred using the OBTAIN macro to retrieveinformation about the data set.

Programmer responseFailure information returned from OBTAIN wasrecorded in the AMRC structure. Use the informationthere to determine the cause of the failure.



C00B0485

ExplanationThe filename argument passed to fopen() or freopen()specified dsname syntax. We have successfullyallocated a ddname for the dsname. An error occurredtrying to obtain device type information. The DEVTYPEmacro failed.

Programmer responseFailure information returned from DEVTYPE wasrecorded in the AMRC structure. Use the informationthere to determine the cause of the failure.


C00B0486

ExplanationAn error occurred trying to read the JFCB. The RDJFCBmacro failed.



C00B0487

ExplanationA failure occurred using the OBTAIN macro to retrieveinformation about the data set.

Programmer responseFailure information returned from OBTAIN wasrecorded in the AMRC structure. Use the informationthere to determine the cause of the failure.


C00B04B1

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The ddname does notexist on the open file chain. The JFCB specified PATH=indicating a UNIX file. A failure occurred trying toacquire further details about the allocation.


Symbolic Feedback CodeJrEdc1opsEnoent01

C00B04B2

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. The JFCB specifiedPATH= indicating a UNIX file. A failure occurred tryingto acquire further details about the allocation.



C00B04B3

ExplanationThe filename argument passed to fopen() or freopen()was NULL or the filename argument passed to fopen()was an empty string. This failure is specific to thePOSIX(ON) environment.



C00B0501

ExplanationCreation of the hiperspace failed.

Programmer responseCheck the AMRC for failure information. Contact IBMsupport if unable to solve the problem.


Symbolic Feedback CodeJrEdc1opsEhspcreate01

C00B0502

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a hiperspace memory file. Themode argument specified write mode. A hiperspacefile with the same name already exists, so it mustbe deleted and recreated. Deletion of the existinghiperspace failed.



C00B0503

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a hiperspace memory file. Themode argument specified write mode. A hiperspacefile with the same name already exists, so it must bedeleted and recreated. Recreation of the hiperspacefailed.



C00B0541

ExplanationThe lrecl specified for a terminal file opened for readexceeded the maximum value of 32767.


Symbolic Feedback CodeJrEdc1opsEmaxattr01

C00B0542

ExplanationThe lrecl specified for a terminal file opened for writeexceeded the maximum value of 32766.


Symbolic Feedback CodeJrEdc1opsEmaxattr02

C00B0581

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a memory file with a membername. A file with the same base name (a parent) doesexist and is a memory file, but it is not partitioned.

Programmer responseCorrect the application. You cannot use the samename for both sequential and partitioned memoryfiles.

Symbolic Feedback CodeJrEdc1opsEflatfile01

C00B0582

ExplanationThe filename and mode arguments passed to fopen()or freopen() specified a memory file without membername. A file with the same base name exists, but alsohas a member specified.

Programmer responseCorrect the application. You cannot use the samename for both sequential and partitioned memoryfiles.

Symbolic Feedback CodeJrEdc1opsEflatfile02

C00B05B1

ExplanationThe filename argument passed to fopen() or freopen()specified dd:ddname syntax. An error occurred tryingto obtain device type information. The DEVTYPE macrofailed with return code 4 indicating the ddname doesnot exist.



Symbolic Feedback CodeJrEdc1opsEddname01

C00B0601

ExplanationAn unexpected failure occurred checking the recordformat associated with an fopen() or freopen(). Thisfailure occurred trying to open a terminal file.


Symbolic Feedback CodeJrEdc1opsEbadcb01

C00B0641

ExplanationThe filename argument passed to fopen() or freopen()specified dsname syntax. The mode argumentspecified read. Allocation of a ddname for the dsnamewas attempted, but SVC 99 failed with error code0x1708. The data set name could not be located. Youcannot use read mode for a data set that does notexist.


Symbolic Feedback CodeJrEdc1opsElocate01

C00B0681

ExplanationThe filename argument passed to fopen() specifiedsyntax ((x)), where x is an unsigned integer, indicatinga generated memory file name or perhaps a UNIX file.The application is either running POSIX(OFF) or thefilename was prefixed with exactly two '/' characters,indicating that the file is not a UNIX file. The file namedoes not exist on the file chain, meaning that thereis no such memory file. You cannot open a memoryfile using a generated memory file name when thememory file does not exist.


Symbolic Feedback CodeJrEdc1opsEnotempmem01

C00B06B1

ExplanationThe filename argument passed to fopen() or freopen()exceeded the maximum length of 1024 characters.This failure is specific to the POSIX(ON) environment.


Symbolic Feedback CodeJrEdc1opsEnametoolong01

C00C0001

ExplanationAn I/O abend was trapped trying to position a streamto its prior location after a reopen of the read/updateDCB was needed to update the last known TTR(file position) and block number for a stream thathad been simultaneously been open for read with astream that was just closed. The READ macro failed.The SIGIOERR is raised (if needed). The stream isprevented from further I/O.

Programmer responseCheck the AMRC for details of the abend. In theSIGIOERR handler, the AMRC2 can be checked to findthe stream that incurred the error.

Symbolic Feedback CodeJrEdc1oscEabend01

C00C0002

ExplanationAn I/O abend was trapped closing the read/updateDCB associated with the stream being closed. TheCLOSE macro failed. The SIGIOERR is raised (ifneeded).

Programmer responseCheck the AMRC for details of the abend.



C00C0003

ExplanationAn I/O abend was trapped closing the write DCBassociated with the stream being closed. The CLOSEmacro failed. The SIGIOERR is raised (if needed).



C00C0004

ExplanationAn I/O abend was trapped closing the write DCBassociated with the stream being closed. The CLOSEmacro failed. The SIGIOERR is raised (if needed).



C00C000A

ExplanationAn internal error occurred trying to allocate memoryneeded to replace a member of a partitioned data set.

Programmer responseContact your IBM support representative.

Symbolic Feedback CodeJrEdc1oscEnomemory01

C00C0013

ExplanationAn error occurred trying to position a stream toits prior location after a reopen of the read/updateDCB was needed to update the last known TTR (fileposition) and block number for a stream that hadbeen simultaneously been open for read with a stream

that was just closed. The READ macro failed. TheSIGIOERR is raised (if needed). Further reads areprevented until a reopen and reposition.

Programmer responseCheck the AMRC for details of the error. In theSIGIOERR handler, the AMRC2 can be checked to findthe stream that incurred the error.

Symbolic Feedback CodeJrEdc1oscErderror01

C00C001C

ExplanationAn error occurred replacing a member of a partitioneddata set. The STOW macro failed. The SIGIOERR israised (if needed).

Programmer responseCheck the AMRC for details of the error.

Symbolic Feedback CodeJrEdc1oscEutility01

C00C001D

ExplanationAn error occurred closing the read/update DCBassociated with the stream being closed. The CLOSEmacro failed. The SIGIOERR is raised (if needed).



C00C001E

ExplanationAn error occurred closing the write DCB associatedwith the stream being closed. The CLOSE macro failed.The SIGIOERR is raised (if needed).




C00C001F

ExplanationAn error occurred trying to update the last knownTTR (file position) and block number for a streamthat had simultaneously been open for read with astream that was just closed. The NOTE macro failed.The SIGIOERR is raised (if needed). Further reads areprevented until a reopen and reposition.

Programmer responseCheck the AMRC for details of the error. In theSIGIOERR handler, the AMRC2 can be checked to findthe stream that incurred the error.


C00C0020

ExplanationAn error occurred closing the read/update DCBassociated with the stream being closed. The CLOSEmacro failed. The SIGIOERR is raised (if needed).



C00C0029

ExplanationA request was made to close a stream associated withan MVS data set on a thread different than the oneon which it was opened. TCB affinity rules require theopen and close to be on the same thread.

Programmer responseClose the stream associated with an MVS data set onthe same thread on which it was opened.

Symbolic Feedback CodeJrEdc1oscEwrongthd01

C0120001

ExplanationThe name specified to the remove() function was notvalid.

Programmer responseCorrect the name and try again.

Symbolic Feedback CodeJrEdc1rmvEbadfilename01

C012000A

ExplanationAn error occurred trying to remove an MVS data set.


Symbolic Feedback CodeJrEdc1rmvEexpdate01

C012000B



Symbolic Feedback CodeJrEdc1rmvEexpdate02

C0120014

ExplanationThe name specified to the remove() function indicateda temporary memory file, but the memory file is open.An open memory file cannot be removed.

Programmer responseCorrect the name or close the memory file and tryagain.

Symbolic Feedback CodeJrEdc1rmvEisopen01

C0120015


ExplanationThe name specified to the remove() function indicateda file that is currently open. An open file cannot beremoved.

Programmer responseCorrect the name or close the file and try again.


C0120016




C0120017




C0120018




C0120019




C012001A




C012001B




C012001C





C012001D




C012001E




C012001F

ExplanationThe name specified to the remove() function indicateda partitioned memory file (without a memberspecified). This indicates a desire to remove all of themembers of the memory file. However, at least one ofthe members is open. You cannot delete a partitionedmemory file that has one or more members currentlyopen.

Programmer responseCorrect the name or close the open member(s) and tryagain.


C0120028

ExplanationA request was made to remove a non-memory fileunder CICS. This is not supported.


Symbolic Feedback CodeJrEdc1rmvEkio01

C0120029

ExplanationA request was made to remove a non-memory fileunder CICS. This is not supported.


Symbolic Feedback CodeJrEdc1rmvEkio02

C0120032

ExplanationThe name specified to the remove() function indicateda temporary memory file, but the name could not befound on the open file chain.


Symbolic Feedback CodeJrEdc1rmvElocate01

C012003B

ExplanationThe name specified to the remove() function used thedd:ddname(member) syntax. A memory file was foundthat matches the dd:ddname, but there is no suchmember.



Symbolic Feedback CodeJrEdc1rmvEmbrinval01

C012003C

ExplanationThe name specified to the remove() function used thedd:ddname syntax without a member specified, butthe ddname allocation that was found does include amember. This remove is not allowed.

Programmer responseCorrect the name or allocation and try again.


C012003D

ExplanationThe name specified to the remove() function used thedsn(member) syntax. A memory file was found thatmatches the dsn, but there is no such member.



C012003E

ExplanationThe name specified to the remove() function indicateda member of a memory file, but no such member wasfound.



C0120047

ExplanationThe name specified to the Enhanced ASCII remove()function was too long.


Symbolic Feedback CodeJrEdc1rmvEnametoolong01

C0120050

ExplanationThe name specified to the remove() function used thedd:ddname syntax that matched an existing ddnameallocation with the PATH= specification, but an erroroccurred trying to acquire the path name.


Symbolic Feedback CodeJrEdc1rmvEnoent01

C0120051

ExplanationThe name specified to the remove() function used thedd:ddname syntax that matched an existing ddnameallocation with the PATH= specification, but an erroroccurred trying to acquire the path name.



C0120052

ExplanationThe name specified to the remove() function was notvalid.



C0120053


ExplanationThe name specified to the remove() function waseither a NULL pointer or a pointer to a NULL string.



C012005C

ExplanationAn internal error occurred trying to allocate memoryneeded to remove a file.


Symbolic Feedback CodeJrEdc1rmvEnomem01

C0120065



Symbolic Feedback CodeJrEdc1rmvEnomemory01

C0120066




C0120067




C0120068




C0120069




C012006A




C012006B





C012006C




C012006D




C0120076

ExplanationAn error occurred trying to open the DCB in order todelete the member of a partitioned data set. The OPENmacro failed.


Symbolic Feedback CodeJrEdc1rmvEopenfail01

C012007F



Symbolic Feedback CodeJrEdc1rmvEoverride01

C0120080



Symbolic Feedback CodeJrEdc1rmvEoverride02

C0120089



Symbolic Feedback CodeJrEdc1rmvEremove01

C012008A




C012008B





C012008C




C012008D




C012008E

ExplanationAn error occurred trying to remove an archived dataset. The ARCHDEL macro failed.



C0120097

ExplanationAn internal utility failed trying to collect informationabout a file being removed. The RDJFCB macro failed.


Symbolic Feedback CodeJrEdc1rmvEutility01

C0120098

ExplanationAn internal utility failed trying to collect informationabout a file being removed. The DEVTYPE macrofailed.



C0120099

ExplanationAn error occurred allocating a ddname needed in orderto remove a member of a partitioned data set.



C012009A

ExplanationAn error occurred trying to delete a member of apartitioned data set. The STOW macro failed.



C0130001

ExplanationThe oldname specified to the rename() function wasnot valid.


Programmer responseCorrect the oldname and try again.

Symbolic Feedback CodeJrEdc1rnmEbadfilename01

C0130002

ExplanationThe newname specified to the rename() function wasnot valid.

Programmer responseCorrect the newname and try again.


C0130003

ExplanationThe newname specified to the rename() function wasnot valid.



C0130004

ExplanationA request was made to rename a member in onepartitioned data set to a member of a differentpartitioned data set. This is not allowed.

Programmer responseCorrect the oldname or newname and try again.


C0130005

ExplanationA request was made to rename to or from a ddname.This is not allowed.



C013000E

ExplanationThe newname specified to the rename() functionindicated a temporary memory file, but one alreadyexists with that name.


Symbolic Feedback CodeJrEdc1rnmEexist01

C013000F

ExplanationA rename was requested for a temporary memoryfile, but the newname is not consistent with that ofa temporary memory file. This is not allowed.



C0130010

ExplanationA request was made to rename a file to a namethat already exists on the open file chain. This is notallowed.

Programmer responseCorrect the newname or close the open file and tryagain.


C0130019


ExplanationA rename was requested for POSIX name to a non-POSIX name or vice versa. This is not allowed.


Symbolic Feedback CodeJrEdc1rnmEinval01

C0130022

ExplanationThe oldname specified to the rename() functionindicated a file that is currently open. An open filecannot be renamed.

Programmer responseCorrect the oldname or close the file and try again.

Symbolic Feedback CodeJrEdc1rnmEisopen01

C0130023

ExplanationThe newname specified to the rename() functionindicated a file that is currently open.



C0130024

ExplanationThe oldname specified to the rename() functionindicated a memory file. At least one child memoryfile exists with same name that is open. You cannotrename a memory file if it has at least one child that isopen.

Programmer responseCorrect the oldname or close the children and tryagain.


C0130025

ExplanationThe oldname specified to the rename() functionindicated a file that is currently open. An open filecannot be renamed.

Programmer responseCorrect the oldname or close the file and try again.


C013002E

ExplanationA request was made to rename a non-memory fileunder CICS. This is not supported.


Symbolic Feedback CodeJrEdc1rnmEkio01

C0130037

ExplanationThe oldname specified to the rename() functionindicated a temporary memory file, but no memory filewith that name could be found.


Symbolic Feedback CodeJrEdc1rnmElocate01

C0130040

ExplanationA rename was requested using a member specificationas part of the oldname, but no member was specifiedas part of the newname. This is not allowed.



Symbolic Feedback CodeJrEdc1rnmEmbrinval01

C0130041

ExplanationThe oldname specified to the rename() functionindicated a member of a memory file, but no suchmember was found.


Symbolic Feedback CodeJrEdc1rnmEmbrinval02

C013004A

ExplanationThe oldname specified to the Enhanced ASCIIrename() function was too long.


Symbolic Feedback CodeJrEdc1rnmEnametoolong01

C013004B

ExplanationThe newname specified to the Enhanced ASCIIrename() function was too long.


Symbolic Feedback CodeJrEdc1rnmEnametoolong02

C0130054

ExplanationAn internal error occurred trying to allocate memoryneeded to rename a file.


Symbolic Feedback CodeJrEdc1rnmEnomemory01

C0130055




C0130056




C0130057




C0130058





C0130061

ExplanationAn error occurred trying to open the DCB in order torename a member of a partitioned data set. The OPENmacro failed.


Symbolic Feedback CodeJrEdc1rnmEopenfail01

C013006A

ExplanationAn error occurred trying to rename an MVS data set.


Symbolic Feedback CodeJrEdc1rnmErename01

C0130073

ExplanationAn error occurred allocating a ddname needed in orderto rename a member of a partitioned data set.


Symbolic Feedback CodeJrEdc1rnmEutility01

C0130074

ExplanationAn error occurred trying to rename a member of apartitioned data set. The STOW macro failed.


Symbolic Feedback CodeJrEdc1rnmEutility02

C01D0031

ExplanationThe fdelrec() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcDlrcEwrongthd01

C01D0032

ExplanationThe fdelrec_unlocked() function was called on a threadother than the one that opened the stream.


Symbolic Feedback CodeJrEdcDlrcEwrongthd02

C01E0060

ExplanationBlocked I/O does not support ungetc() function.

Programmer responseDon't use ungetc() on blocked I/O or use binary I/O.

Symbolic Feedback CodeJrEdcEpegEblkio01

C01F0010

ExplanationThe clearerr() function was called on a thread otherthan the one that opened the stream.



Symbolic Feedback CodeJrEdcFlgsEwrongthd01

C01F0011

ExplanationThe clearerr_unlocked() function was called on athread other than the one that opened the stream.



C01F0012

ExplanationThe feof() function was called on a thread other thanthe one that opened the stream.



C01F0013

ExplanationThe feof_unlocked() function was called on a threadother than the one that opened the stream.



C01F0014

ExplanationThe ferror() function was called on a thread other thanthe one that opened the stream.



C01F0015

ExplanationThe ferror_unlocked() function was called on a threadother than the one that opened the stream.



C0200010

ExplanationThe fflush_unlocked() function was called on a threadother than the one that opened the stream.


Symbolic Feedback CodeJrEdcFlshEwrongthd01

C0200011

ExplanationThe fflush() function was called on a thread other thanthe one that opened the stream.



Symbolic Feedback CodeJrEdcFlshEwrongthd02

C0210020

ExplanationThe fgetc() function was called on a thread other thanthe one that opened the stream.


Symbolic Feedback CodeJrEdcGetcEwrongthd01

C0210021

ExplanationThe fgetc_unlocked() function was called on a threadother than the one that opened the stream.



C0210022

ExplanationThe getc() function was called on a thread other thanthe one that opened the stream.



C0210023

ExplanationThe getc_unlocked() function was called on a threadother than the one that opened the stream.



C0210024

ExplanationThe getchar() function was called on a thread otherthan the one that opened the stream.



C0210025

ExplanationThe getchar_unlocked() function was called on athread other than the one that opened the stream.



C0220030

ExplanationThe __fgets_a() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcGetsEwrongthd01

C0220031


ExplanationThe fgets() function was called on a thread other thanthe one that opened the stream.



C0220032

ExplanationThe __fgets_unlocked_a() function was called on athread other than the one that opened the stream.



C0220033

ExplanationThe fgets_unlocked() function was called on a threadother than the one that opened the stream.



C0220034

ExplanationThe __gets_a() function was called on a thread otherthan the one that opened the stream.



C0220035

ExplanationThe gets() function was called on a thread other thanthe one that opened the stream.



C0220036

ExplanationThe __gets_unlocked_a() function was called on athread other than the one that opened the stream.



C0220037

ExplanationThe gets_unlocked() function was called on a threadother than the one that opened the stream.



C023000C

ExplanationThe ftell() function was called to get the current fileposition. The offset exceeds the maximum value thatcan be returned. The offset maximum is LONG_MAX.


Programmer responseUse the large files version of ftello() or the fgetpos()function to report positions beyond LONG_MAX.

Symbolic Feedback CodeJrEdcGposEftell01

C0230010

ExplanationThe ftell() function was called to get the current fileposition. The offset exceeds the maximum value thatcan be returned. The offset maximum is LONG_MAX.

Programmer responseUse the large files version of ftello() or the fgetpos()function to report positions beyond LONG_MAX.


C0230011

ExplanationThe ftell() function was called to get the current fileposition using encoded offsets. The offset exceeds themaximum value that can be returned.

Programmer responseUse the large files version of ftello() to report positionsbeyond the maximum.


C023002D

ExplanationThe current file position cannot be correctlyrepresented in a long int type. The value is eithergreater than or equal to 4GB-1, or greater than orequal to 2GB-1 when in the middle of a DBCS string.

Programmer responseIf possible, use the large files version of the ftello().function.

Symbolic Feedback CodeJrEdcGposEoverflow02

C0230030

ExplanationThe ftell() function was called on a thread other thanthe one that opened the stream.


Symbolic Feedback CodeJrEdcGposEwrongthd01

C0230031

ExplanationThe ftell_unlocked() function was called on a threadother than the one that opened the stream.



C0230032

ExplanationThe ftello() function was called on a thread other thanthe one that opened the stream.



C0230033

ExplanationThe ftello_unlocked() function was called on a threadother than the one that opened the stream.




C0230034

ExplanationThe ftello_o() function was called on a thread otherthan the one that opened the stream.



C0230035

ExplanationThe ftello_unlocked_o() function was called on athread other than the one that opened the stream.



C0230036

ExplanationThe fgetpos() function was called on a thread otherthan the one that opened the stream.



C0230037

ExplanationThe fgetpos_unlocked() function was called on athread other than the one that opened the stream.



C0250030

ExplanationThe flocate() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcLoctEwrongthd01

C0250031

ExplanationThe flocate_unlocked() function was called on a threadother than the one that opened the stream.


Symbolic Feedback CodeJrEdcLoctEwrongthd02

C0300001

ExplanationAn internal error occurred trying to allocate memoryneeded when passing a standard stream across theANSI system call.


Symbolic Feedback CodeJrEdcNoskEnomemory01

C030000A


ExplanationA request was made to reposition a file opened noseekthat was either not a rewind() call or the file isopened for output. A file opened noseek can only berepositioned using rewind() and if it is also opened forjust reading. The __last_op field in the AMRC is set to__NOSEEK_REWIND. The SIGIOERR is raised (if notset to ignore).


Symbolic Feedback CodeJrEdcNoskEnoseek01

C030000B

ExplanationA request was made to reposition a file opened noseekthat was either not a rewind() call or the file isopened for output. A file opened noseek can only berepositioned using rewind() and if it is also opened forjust reading. The __last_op field in the AMRC is set to__NOSEEK_REWIND. The SIGIOERR is raised (if notset to ignore).


Symbolic Feedback CodeJrEdcNoskEnoseek02

C0300014

ExplanationAn error occurred reopening the read/update DCBduring a rewind of a file opened noseek. The OPENmacro failed. The SIGIOERR is raised (if not set toignore). Further I/O is prevented on the stream.

Programmer responseCheck the AMRC for details of the error. You shouldclose the stream.

Symbolic Feedback CodeJrEdcNoskEopenfail01

C030001D

ExplanationAn error occurred closing the read/update DCB duringa rewind of a file opened noseek. The CLOSE macrofailed. The SIGIOERR is raised (if not set to ignore).


Symbolic Feedback CodeJrEdcNoskEutility01

C0300026

ExplanationAn I/O abend was trapped closing the read/updateDCB during a rewind of a file opened noseek. TheCLOSE macro failed. The SIGIOERR is raised (if not setto ignore).


Symbolic Feedback CodeJrEdcNoskEabend01

C0320001

ExplanationAn internal error occurred trying to allocate the read/update DCB for a stream. Further I/O is prevented onthe stream.


Symbolic Feedback CodeJrEdcOpruEnomemory01

C0320002

ExplanationAn internal error occurred trying to allocate the read/update DCBE for a stream. Further I/O is prevented onthe stream.



Symbolic Feedback CodeJrEdcOpruEnomemory02

C032000B

ExplanationAn error occurred opening the read/update DCB duringa reopen of the read/update DCB for a stream. TheOPEN macro failed. The SIGIOERR is raised (if not setto ignore). Further I/O is prevented on the stream.


Symbolic Feedback CodeJrEdcOpruEopenfail01

C032000C

ExplanationAn error occurred positioning to the member of apartitioned data set during a reopen of the read/update DCB for a stream. The BLDL / FIND macrosequence failed. The SIGIOERR is raised (if not set toignore). Further I/O is prevented on the stream.


Symbolic Feedback CodeJrEdcOpruEopenfail02

C0320015

ExplanationAn error occurred closing the read/update DCB duringa reopen of the read/update DCB. The CLOSE macrofailed. The SIGIOERR is raised (if not set to ignore).


Symbolic Feedback CodeJrEdcOpruEutility01

C032001E

ExplanationAn I/O abend was trapped closing the read/updateDCB during a reopen of the read/update DCB. TheCLOSE macro failed. The SIGIOERR is raised (if not setto ignore).


Symbolic Feedback CodeJrEdcOpruEabend01

C0350001

ExplanationThe low-level READ function ABENDed. The SIGIO israised (if needed) and the stream is prevented fromfurther use. This failure occurred while reading to EOFin order to get the stream position.

Programmer responseCheck the AMRC for details of the ABEND.

Symbolic Feedback CodeJrEdcOsntEabend01

C0350005

ExplanationThe low-level READ function failed. The SIGIO israised (if needed) and the stream is prevented fromfurther use. This failure occurred while reading to EOFin order to get the stream position.


Symbolic Feedback CodeJrEdcOsntErderror01

C0360001

ExplanationThe low-level READ function ABENDed. The SIGIO israised (if needed) and the stream is prevented fromfurther use. This failure occurred while positioning toEOF in preparation for a relative reposition backwards.There had been a prior jump to EOF without actuallymoving the file pointer.



Symbolic Feedback CodeJrEdcOsrbEabend01

C0360002

ExplanationThe low-level READ function ABENDed. The SIGIO israised (if needed) and the stream is prevented fromfurther use. This failure occurred reading the previousblock during a relative reposition backwards.


Symbolic Feedback CodeJrEdcOsrbEabend02

C0360005

ExplanationAn internal error occurred trying to allocate memoryfor a JFCB.


Symbolic Feedback CodeJrEdcOsrbEnomemory01

C0360009

ExplanationA relative reposition is being attempted, but there is anoutstanding read error.

Programmer responseA direct reposition or rewind must be done to clear theprevious read error.

Symbolic Feedback CodeJrEdcOsrbEpreverr01

C036000D

ExplanationThe low-level READ function failed. The SIGIO israised (if needed). The stream is prevented fromfurther READ attempts. This failure occurred whilepositioning to EOF in preparation for a relativereposition backwards. There had been a prior jump toEOF without actually moving the file pointer.


Symbolic Feedback CodeJrEdcOsrbErderror01

C036000E

ExplanationThe low-level READ function failed. The SIGIO israised (if needed). The stream is prevented fromfurther READ attempts. This failure occurred whilereading all blocks on the previous volume in order tofind the previous block.



C036000F

ExplanationThe low-level READ function failed. The SIGIO israised (if needed). The stream is prevented fromfurther READ attempts. This failure occurred readingthe previous block during a relative repositionbackwards.



C0360015

ExplanationAn internal error occurred trying to read the previousblock during a relative reposition backwards.



Symbolic Feedback CodeJrEdcOsrbEreadback01

C0360016

ExplanationAn internal error occurred trying to read the previousblock during a relative reposition backwards.


Symbolic Feedback CodeJrEdcOsrbEreadback02

C0360019

ExplanationAn error occurred using a system utility.

Programmer responseCheck the AMRC for details of the failure.

Symbolic Feedback CodeJrEdcOsrbEutility01

C036001A




C036001B




C036001C




C036001D




C036001E




C036001F





C0370001

ExplanationThe low-level READ function ABENDed. The SIGIO israised (if needed) and the stream is prevented fromfurther use. This failure occurred while reading thenext block.


Symbolic Feedback CodeJrEdcOsrdEabend01

C0370005

ExplanationA read of the next block is being attempted, but thereis an outstanding read error. This failure occurredwhile reading the next block.

Programmer responseA direct reposition or rewind must be done to clear theprevious read error.

Symbolic Feedback CodeJrEdcOsrdEpreverr01

C0370009

ExplanationThe low-level READ function failed. The SIGIO israised (if needed). The stream is prevented fromfurther READ attempts. This failure occurred whilereading the next block.


Symbolic Feedback CodeJrEdcOsrdErderror01

C0380001

ExplanationThe low-level READ function ABENDed. The SIGIO israised (if needed) and the stream is prevented fromfurther use. This failure occurred while rewinding thefile.


Symbolic Feedback CodeJrEdcOsrwEabend01

C0380005

ExplanationThe low-level READ function failed. The SIGIO israised (if needed). The stream is prevented fromfurther READ attempts. This failure occurred whilerewinding the file.


Symbolic Feedback CodeJrEdcOsrwErderror01

C0390001

ExplanationThe low-level READ function ABENDed. The SIGIOis raised (if needed) and the stream is preventedfrom further use. This failure occurred during direct orrelative block seeking.


Symbolic Feedback CodeJrEdcOsskEabend01

C0390002

ExplanationThe low-level READ function ABENDed. The SIGIO israised (if needed) and the stream is prevented fromfurther use. This failure occurred during byte seeking.


Symbolic Feedback CodeJrEdcOsskEabend02

C0390005


ExplanationThe low-level READ function failed. The SIGIO israised (if needed). The stream is prevented fromfurther READ attempts. This failure occurred duringdirect or relative block seeking.


Symbolic Feedback CodeJrEdcOsskErderror01

C0390006

ExplanationThe low-level READ function failed. The SIGIO israised (if needed). The stream is prevented fromfurther READ attempts. This failure occurred duringbyte seeking.


Symbolic Feedback CodeJrEdcOsskErderror02

C03C0006

ExplanationThe input position is format TTTR and using largeblock tokens, but the current file stream is not.


Symbolic Feedback CodeJrEdcP030Ebadfpos06

C03C0032

ExplanationThe ftello() function was called to get the currentfile position for a fixed binary os data set. The offsetexceeds the maximum value that can be returned. Theoffset limit is LONGLONG_MAX.


Symbolic Feedback CodeJrEdcP030Eftell01

C03D0016




C03E0005

ExplanationAn error occurred in QSAM TRUNC during a flush of abuffer.


Symbolic Feedback CodeJrEdcP039Ewrerror05

C03E0011

ExplanationAn I/O abend was trapped on QSAM TRUNC during aflush of a buffer.


Symbolic Feedback CodeJrEdcP039Eabend01

C03F0006





C03F0034

ExplanationThe ftello() function was called to get the current fileposition for an undefined binary os data set. The offsetexceeds the maximum value that can be returned. Theoffset limit is LONGLONG_MAX.



C03F0035

ExplanationThe ftell() or ftello() function was called to get thecurrent file position for an undefined binary os dataset. The block number portion of the encoded offsetexceeds the maximum number of blocks that can berepresented. The block limit is INT_MAX.



C0400007




C0400031

ExplanationThe ftello() function was called to get the current fileposition for a fixed non-ASA text os data set. The

number of blocks represented in the offset exceedsthe limit supported by the run-time. The limit is 2 GBblocks.



C0410007




C0410031

ExplanationThe ftello() function was called to get the current fileposition for a fixed ASA text os data set. The numberof blocks represented in the offset exceeds the limitsupported by the run-time. The limit is 2 GB blocks.



C0420009




C0420030


ExplanationThe ftello() function was called to get the current fileposition for a variable non-ASA text os data set. Thenumber of blocks represented in the offset exceedsthe limit supported by the run-time. The limit is 2 GBblocks.



C0430012




C043003D

ExplanationThe ftello() function was called to get the currentfile position for a variable ASA text os data set. Thenumber of blocks represented in the offset exceedsthe limit supported by the run-time. The limit is 2 GBblocks.



C044002A




C0440033




C0450006




C0450037

ExplanationThe ftello() function was called to get the currentfile position for an undefined non-ASA text os dataset. The number of blocks represented in the offsetexceeds the limit supported by the run-time. The limitis 2 GB blocks.



C0460037





C0460051




C0470012




C0470040

ExplanationThe ftello() function was called to get the current fileposition for an undefined ASA text os data set. Thenumber of blocks represented in the offset exceedsthe limit supported by the run-time. The limit is 2 GBblocks.



C0480006




C048002A

ExplanationThe ftello() function was called to get the current fileposition for a fixed format OS file under record I/O. Therecord offset exceeds the maximum value that can bereturned. The record offset limit is LONGLONG_MAX.



C0490005




C04A001E





C04A0031




C04B0005




C04B000D

ExplanationAttempting to seek to past the EOF is not permitted.

Programmer responseCorrect the application to assure the requestedposition is not beyond the EOF.

Symbolic Feedback CodeJrEdcP084Ebadseek02

C04B0014

ExplanationThe fseek() or fseeko() function was called to relativelyreposition with an offset greater than 2 GB in anundefined OS data set using record I/O. Undefinedrecord I/O treats each block as a record. The run-time supports data sets up to 2 GB blocks in size.Repositioning beyond 2 GB blocks is unsupported.



C04B0024

ExplanationThe ftello() function was called to get the currentfile position for an undefined format OS file underrecord I/O. The record offset exceeds the maximumvalue that can be returned. The record offset limit isLONGLONG_MAX.



C04B0076

ExplanationPDS(E) member opened for rb+ mode orconcantenated data set cannot be extended.

Programmer responseCorrect the application. For PDS(E) member, it onlycan be extended under wb or wb+ mode. Forconcantenated data set, it can't be extended.

Symbolic Feedback CodeJrEdcP084Eextend01

C050008C

ExplanationAn unexpected failure occurred while calling ftell()on a VSAM KSDS data set opened for SEEK withtype=record.

Programmer responseInformation about the failure was recorded inthe AMRC structure. Use the information there todetermine the cause of the failure.

Symbolic Feedback CodeJrEdcP096Evsampos08

C0510065


ExplanationAn unexpected failure occurred while calling fsetpos()on a VSAM RRDS data set opened for SEEK with openmode binary.

Programmer responseInformation about the failure was recorded inthe AMRC structure. Use the information there todetermine the cause of the failure.

Symbolic Feedback CodeJrEdcP098Erderror20

C0560020

ExplanationThe __fputc_a() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcPutcEwrongthd01

C0560021

ExplanationThe fputc() function was called on a thread other thanthe one that opened the stream.



C0560022

ExplanationThe __fputc_unlocked_a() function was called on athread other than the one that opened the stream.



C0560023

ExplanationThe fputc_unlocked() function was called on a threadother than the one that opened the stream.



C0560024

ExplanationThe __putc_a() function was called on a thread otherthan the one that opened the stream.



C0560025

ExplanationThe putc() function was called on a thread other thanthe one that opened the stream.



C0560026

ExplanationThe putc_unlocked_a() function was called on a threadother than the one that opened the stream.




C0560027

ExplanationThe putc_unlocked() function was called on a threadother than the one that opened the stream.



C0560028

ExplanationThe __putchar_a() function was called on a threadother than the one that opened the stream.



C0560029

ExplanationThe putchar() function was called on a thread otherthan the one that opened the stream.



C056002A

ExplanationThe __putchar_unlocked_a() function was called on athread other than the one that opened the stream.



C056002B

ExplanationThe putchar_unlocked() function was called on athread other than the one that opened the stream.



C057002A

ExplanationThe __fputs_a() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcPutsEwrongthd01

C057002B

ExplanationThe fputs() function was called on a thread other thanthe one that opened the stream.




C057002C

ExplanationThe __fputs_unlocked_a() function was called on athread other than the one that opened the stream.



C057002D

ExplanationThe fputs_unlocked() function was called on a threadother than the one that opened the stream.



C057002E

ExplanationThe __puts_a() function was called on a thread otherthan the one that opened the stream.



C057002F

ExplanationThe puts() function was called on a thread other thanthe one that opened the stream.



C0570030

ExplanationThe __puts_unlocked_a() function was called on athread other than the one that opened the stream.



C0570031

ExplanationThe puts_unlocked() function was called on a threadother than the one that opened the stream.



C0590020

ExplanationThe __fread_a() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcReadEwrongthd01

C0590021


ExplanationThe fread() function was called on a thread other thanthe one that opened the stream.



C0590022

ExplanationThe __fread_unlocked_a() function was called on athread other than the one that opened the stream.



C0590023

ExplanationThe fread_unlocked() function was called on a threadother than the one that opened the stream.



C05B0045

ExplanationThe new file position cannot be correctly representedin a long int type.

Programmer responseIf possible, use the large files version of the fseeko()function.

Symbolic Feedback CodeJrEdcRposEoverflow01

C05B0046

ExplanationThe new file position cannot be correctly representedin an off_t type.

Programmer responseIf possible, use the large files version of the fseeko()function.

Symbolic Feedback CodeJrEdcRposEoverflow02

C05B0050

ExplanationThe fseek() function was called on a thread other thanthe one that opened the stream.


Symbolic Feedback CodeJrEdcRposEwrongthd02

C05B0051

ExplanationThe fseek_unlocked() function was called on a threadother than the one that opened the stream.



C05B0052

ExplanationThe fseeko() function was called on a thread otherthan the one that opened the stream.




C05B0053

ExplanationThe fseeko_unlocked() function was called on a threadother than the one that opened the stream.



C05B0054

ExplanationThe fseeko_o() function was called on a thread otherthan the one that opened the stream.



C05B0055

ExplanationThe fseeko_unlocked_o() function was called on athread other than the one that opened the stream.



C05B0056

ExplanationThe fsetpos() function was called on a thread otherthan the one that opened the stream.



C05B0057

ExplanationThe fsetpos_unlocked() function was called on athread other than the one that opened the stream.



C05B0058

ExplanationThe rewind() function was called on a thread otherthan the one that opened the stream.



C05B0059

ExplanationThe rewind_unlocked() function was called on a threadother than the one that opened the stream.




C05C001E

ExplanationBlocked I/O only supports full buffering mode.

Programmer responseChange buffering mode to _IOFBF.

Symbolic Feedback CodeJrEdcStbfEbufmode11

C060002A

ExplanationThe ungetc() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcUngtEwrongthd01

C060002B

ExplanationThe ungetc_unlocked() function was called on a threadother than the one that opened the stream.


Symbolic Feedback CodeJrEdcUngtEwrongthd02

C0610020

ExplanationThe fupdate() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcUpdtEwrongthd01

C0610021

ExplanationThe fupdate() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcUpdtEwrongthd02

C0620020

ExplanationThe __fgetwc_a() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcWgetEwrongthd01

C0620021

ExplanationThe __fgetwc_unlocked_a() function was called on athread other than the one that opened the stream.



C0620022


ExplanationThe fgetwc() function was called on a thread otherthan the one that opened the stream.



C0620023

ExplanationThe fgetwc_unlocked() function was called on a threadother than the one that opened the stream.



C0620024

ExplanationThe __getwc_a() function was called on a thread otherthan the one that opened the stream.



C0620025

ExplanationThe getwc() function was called on a thread other thanthe one that opened the stream.



C0620026

ExplanationThe __getwc_unlocked_a() function was called on athread other than the one that opened the stream.



C0620027

ExplanationThe getwc_unlocked() function was called on a threadother than the one that opened the stream.



C0620028

ExplanationThe __getwchar_a() function was called on a threadother than the one that opened the stream.



C0620029

ExplanationThe getwchar() function was called on a thread otherthan the one that opened the stream.




C062002A

ExplanationThe __getwchar_unlocked_a() function was called on athread other than the one that opened the stream.



C062002B

ExplanationThe getwchar_unlocked() function was called on athread other than the one that opened the stream.



C062002C

ExplanationThe __fgetws_a() function was called on a thread otherthan the one that opened the stream.



C062002D

ExplanationThe fgetws() function was called on a thread otherthan the one that opened the stream.



C062002E

ExplanationThe __fgetws_unlocked_a() function was called on athread other than the one that opened the stream.



C062002F

ExplanationThe fgetws_unlocked() function was called on a threadother than the one that opened the stream.



C0620030

ExplanationThe ungetwc() function was called on a thread otherthan the one that opened the stream.




C0620031

ExplanationThe ungetwc_unlocked() function was called on athread other than the one that opened the stream.



C0620032

ExplanationThe __ungetwc_a() function was called on a threadother than the one that opened the stream.



C0620033

ExplanationThe __ungetwc_unlocked_a() function was called on athread other than the one that opened the stream.



C0630010

ExplanationThe __fputwc_a() function was called on a threadother than the one that opened the stream.


Symbolic Feedback CodeJrEdcWputEwrongthd01

C0630011

ExplanationThe fputwc() function was called on a thread otherthan the one that opened the stream.



C0630012

ExplanationThe __fputwc_unlocked_a() function was called on athread other than the one that opened the stream.



C0630013

ExplanationThe fputwc_unlocked() function was called on a threadother than the one that opened the stream.



C0630014


ExplanationThe __putwc_a() function was called on a thread otherthan the one that opened the stream.



C0630015

ExplanationThe putwc() function was called on a thread other thanthe one that opened the stream.



C0630016

ExplanationThe __putwc_unlocked_a() function was called on athread other than the one that opened the stream.



C0630017

ExplanationThe putwc_unlocked() function was called on a threadother than the one that opened the stream.



C0630018

ExplanationThe __putwchar_a() function was called on a threadother than the one that opened the stream.



C0630019

ExplanationThe putwchar() function was called on a thread otherthan the one that opened the stream.



C063001A

ExplanationThe __putwchar_unlocked_a() function was called ona thread other than the one that opened the stream.



C063001B

ExplanationThe putwchar_unlocked() function was called on athread other than the one that opened the stream.




C063001C

ExplanationThe __fputws_a() function was called on a threadother than the one that opened the stream.



C063001D

ExplanationThe fputws() function was called on a thread otherthan the one that opened the stream.



C063001E

ExplanationThe __fputws_unlocked_a() function was called on athread other than the one that opened the stream.



C063001F

ExplanationThe fputws_unlocked() function was called on a threadother than the one that opened the stream.



C0640020

ExplanationThe __fwrite_a() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcWritEwrongthd01

C0640021

ExplanationThe fwrite() function was called on a thread other thanthe one that opened the stream.



C0640022

ExplanationThe __fwrite_unlocked_a() function was called on athread other than the one that opened the stream.




C0640023

ExplanationThe fwrite_unlocked() function was called on a threadother than the one that opened the stream.



C066000A

ExplanationThe DIR pointer argument of __readdir2_64() is NULL.

Programmer responseCorrect the DIR pointer argument.

Symbolic Feedback CodeJrEdcDir_Ebadf10

C066000B

ExplanationDIR stream passed to __readdir2_64() is notallocated.



C066000C

ExplanationDirectory stream passed to __readdir2_64() is notvalid.



C0660012

ExplanationIn __readdir2_64(), extracted dir entry isn't valid.

Programmer responseCheck the directory passed to __readdir2_64().

Symbolic Feedback CodeJrEdcDir_Eio02

C068000A

ExplanationThe fileno() function was called on a thread other thanthe one that opened the stream.


Symbolic Feedback CodeJrEdcFlnoEwrongthd01

C068000B

ExplanationThe fileno_unlocked() function was called on a threadother than the one that opened the stream.


Symbolic Feedback CodeJrEdcFlnoEwrongthd02

C069000A

ExplanationThe flockfile() function was called on a thread otherthan the one that opened the stream.



Symbolic Feedback CodeJrEdcFlokEwrongthd01

C069000B

ExplanationThe ftrylockfile() function was called on a thread otherthan the one that opened the stream.



C069000C

ExplanationThe funlockfile() function was called on a thread otherthan the one that opened the stream.



C0700001

ExplanationStorage could not be allocated for I/O trace table.

Programmer responseIncrease the storage available to the anywhere heap.

Symbolic Feedback CodeJrEdcIotrEnomemory01

C0700002

ExplanationStorage could not be allocated for I/O tracing.



C0700003




C0700004




C0700005




C0700006





C0700007




C0700008

ExplanationStorage could not be allocated for I/O trace file name.



C0700009

ExplanationStorage could not be allocated for I/O trace file name.



C0700011

ExplanationI/O trace initialization attempted by invalid function.


Symbolic Feedback CodeJrEdcIotrEinval01

C0710001

ExplanationThe stream pointer passed to the __fbufsize() functionis not a valid file pointer with POSIX(ON).

Programmer responsePass a valid file pointer to __fbufsize().

Symbolic Feedback CodeJrEdcFioeEbadf01

C0710002

ExplanationThe stream pointer passed to the __flbf() function isnot a valid file pointer with POSIX(ON).

Programmer responsePass a valid file pointer to __flbf().


C0710003

ExplanationThe stream pointer passed to the __fpending() or__fpending_unlocked() function is not a valid filepointer with POSIX(ON).

Programmer responsePass a valid file pointer to __fpending() or__fpending_unlocked().


C0710004

ExplanationThe stream pointer passed to the __freadable()function is not a valid file pointer with POSIX(ON).

Programmer responsePass a valid file pointer to __freadable().



C0710005

ExplanationThe stream pointer passed to the __freadahead() or__freadahead_unlocked() function is not a valid filepointer with POSIX(ON).

Programmer responsePass a valid file pointer to __freadahead() or__freadahead_unlocked().


C0710006

ExplanationThe stream pointer passed to the __freading() or__freading_unlocked() function is not a valid filepointer with POSIX(ON).

Programmer responsePass a valid file pointer to __freading() or__freading_unlocked().


C0710007

ExplanationThe stream pointer passed to the __fwritable()function is not a valid file pointer with POSIX(ON).

Programmer responsePass a valid file pointer to __fwritable().


C0710008

ExplanationThe stream pointer passed to the __fwriting() or__fwriting_unlocked() function is not a valid filepointer with POSIX(ON).

Programmer responsePass a valid file pointer to __fwriting() or__fwriting_unlocked().


C0710009

ExplanationThe stream pointer passed to the __fpurge() functionis not a valid file pointer with POSIX(ON).

Programmer responseMake sure the stream pointer is valid.


C071000A

ExplanationThe stream pointer passed to __fsetlocking() is notvalid with POSIX(ON).

Programmer responsePass a valid stream pointer to __fsetlocking().


C071000B

ExplanationThe stream pointer passed to the __fseterr() functionis not a valid file pointer with POSIX(ON).



C0710011

ExplanationThe stream pointer passed to the __fbufsize() functionis not a valid file pointer with POSIX(OFF).


Programmer responsePass a valid file pointer to __fbufsize().

Symbolic Feedback CodeJrEdcFioeEnotopen01

C0710012

ExplanationThe stream pointer passed to the __flbf() function isnot a valid file pointer with POSIX(OFF).

Programmer responsePass a valid file pointer to __flbf().


C0710013

ExplanationThe stream pointer passed to the __fpending() or__fpending_unlocked() is not a valid file pointer withPOSIX(OFF).

Programmer responsePass a valid file pointer to __fpending() or__fpending_unlocked().


C0710014

ExplanationThe stream pointer passed to the __freadable()function is not a valid file pointer and posix is notenabled.

Programmer responsePass a valid file pointer to __freadable().


C0710015

ExplanationThe stream pointer passed to the __freadahead() or__freadahead_unlocked() is not a valid file pointer withPOSIX(OFF).

Programmer responsePass a valid file pointer to __freadahead() or__freadahead_unlocked().


C0710016

ExplanationThe stream pointer passed to the __freading() or__freading_unlocked() is not a valid file pointer withPOSIX(OFF).

Programmer responsePass a valid file pointer to __freading() or__freading_unlocked().


C0710017

ExplanationThe stream pointer passed to the __fwritable()function is not a valid file pointer with POSIX(OFF).

Programmer responsePass a valid file pointer to __fwritable().


C0710018

ExplanationThe stream pointer passed to the __fwriting() or__fwriting_unlocked() is not a valid file pointer withPOSIX(OFF).

Programmer responsePass a valid file pointer to __fwriting() or__fwriting_unlocked().



C0710019

ExplanationThe stream pointer passed to the __fpurge() functionis not a valid file pointer with POSIX(OFF).



C071001A

ExplanationThe stream pointer passed to __fsetlocking() is notvalid with POSIX(OFF).

Programmer responsePass a valid stream pointer to __fsetlocking().


C071001B

ExplanationThe stream pointer passed to the __fseterr() functionis not a valid file pointer with POSIX(OFF).



C0710021

ExplanationThe stream pointer passed to the __freadahead()or __freadahead_unlocked() function is not currentlyreading.

Programmer responseA reading operation must be performed prior tocalling __freadahead() or __freadahead_unlocked orthe stream must be opened for read only.

Symbolic Feedback CodeJrEdcFioeEnotread01

C071002A

ExplanationThe stream pointer passed to the __fpending()or __fpending_unlocked() function is not currentlywriting.

Programmer responseA writing operation must be performed prior to calling__fpending() or __fpending_unlocked or the streammust be opened for write or append only.

Symbolic Feedback CodeJrEdcFioeEnotwrite01

C0710031

ExplanationThe __fpending() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcFioeEwrongthd01

C0710032

ExplanationThe __fpending_unlocked() function was called on athread other than the one that opened the stream.




C0710033

ExplanationThe __freadahead() function was called on a threadother than the one that opened the stream.



C0710034

ExplanationThe __freadahead_unlocked() function was called on athread other than the one that opened the stream.



C0710035

ExplanationThe __freading() function was called on a thread otherthan the one that opened the stream.



C0710036

ExplanationThe __freading_unlocked() function was called on athread other than the one that opened the stream.



C0710037

ExplanationThe __fwriting() function was called on a thread otherthan the one that opened the stream.



C0710038

ExplanationThe __fwriting_unlocked() function was called on athread other than the one that opened the stream.



C0710039

ExplanationThe __fpurge() function was called on a thread otherthan the one that opened the stream.



C071003A

ExplanationThe __fpurge_unlocked() function was called on athread other than the one that opened the stream.




C071003B

ExplanationThe __fsetlocking() function was called on a threadother than the one that opened the stream.



C0710041

ExplanationThe type parameter passed to __fsetlocking() is notvalid.

Programmer responsePass a valid type parameter as defined in stdio_ext.h to__fsetlocking().

Symbolic Feedback CodeJrEdcFioeEinval01

C0710051

ExplanationA stream was passed to the __fpurge() function that isnot supported by the function. __fpurge() only allowsthe purging of UNIX files.

Programmer responseCorrect the application so that it does not attempt touse __fpurge() on streams that are not UNIX files.

Symbolic Feedback CodeJrEdcFioeEnocando01

C0710052

ExplanationAn invalid Record Descriptor Word (RDW) wasencountered while processing a variable-format dataset during an __freadahead() call.

Programmer responseValidate record data in the data set is accurate.

Symbolic Feedback CodeJrEdcFioeEnocando02

C0710061

ExplanationThe file is open with type=record and an attempt wasmade to get the number of bytes or wide characterspending to be written using __fpending(). Byte I/O isnot allowed on files open type=record.

Programmer responseRemove type=record from the fopen() mode argumentand use byte I/O functions to write the file if you desirethe number of bytes or wide characters pending to bewritten.

Symbolic Feedback CodeJrEdcFioeErecio01

C0710062

ExplanationThe file is open with type=record and an attempt wasmade to get the number of bytes or wide charactersleft to read from the buffer using __freadahead(). ByteI/O is not allowed on files open type=record.

Programmer responseRemove type=record from the fopen() mode argumentand use byte I/O functions to read the file if you desirethe number of bytes or wide characters to be read.

Symbolic Feedback CodeJrEdcFioeErecio02

C0710071

ExplanationThe file is open with type=blocked and an attempt wasmade to get the number of bytes or wide characters


pending to be written using __fpending(). Byte I/O isnot allowed on files open type=blocked.

Programmer responseRemove type=blocked from the fopen() modeargument and use byte I/O functions to write the fileif you desire the number of bytes or wide characterspending to be written.

Symbolic Feedback CodeJrEdcFioeEblkio01

C0710072

ExplanationThe file is open with type=blocked and an attempt wasmade to get the number of bytes or wide charactersleft to read from the buffer using __freadahead(). ByteI/O is not allowed on files open type=blocked.

Programmer responseRemove type=blocked from the fopen() modeargument and use byte I/O functions to read the fileif you desire the number of bytes or wide characters tobe read.

Symbolic Feedback CodeJrEdcFioeEblkio02

C0720001

ExplanationThe request size is not a multiple of one record length.

Programmer responseCorrect the size specified, change to a size of multipleof one record length.

Symbolic Feedback CodeJrEdcP131Ebadarg01

C072000A

ExplanationByte I/O is not allowed for blocked I/O files.

Programmer responseuse fread() to read a blocked I/O file.

Symbolic Feedback CodeJrEdcP131Eblkio01

C072000B


Programmer responseuse fwrite() to write a blocked I/O file.


C072000C


Programmer responseuse fread() to read a blocked I/O file.


C072000D


Programmer responseuse fwrite() to write a blocked I/O file.


C0720016

ExplanationThe capacity specified to write is more than a wholeblock, data was truncated.

Programmer responseCorrect the size specified, change to a size no morethan blksize.


Symbolic Feedback CodeJrEdcP131Etruncblk01

C0720017

ExplanationThe capacity specified to write is more than a wholeblock, data was truncated.

Programmer responseCorrect the size specified, change to a size no morethan blksize.

Symbolic Feedback CodeJrEdcP131Etruncblk02

C0720020

ExplanationThe ftello() function was called to get the currentfile position for an OS file under blocked I/O. Theblock offset exceeds the maximum value that can bereturned. The block offset limit is LONGLONG_MAX.



C0720029

ExplanationA request was made to reposition a file while seekingnot allowed. A file opened noseek can only berepositioned using rewind().

Programmer responseCorrect the application to assure reposition isrequested only when seeking is allowed.

Symbolic Feedback CodeJrEdcP131Enoseek01

C0720032

ExplanationThe input position is not correct

Programmer responseCorrect the application to assure that a valid position isspecified.


C0720033




C0720034

ExplanationThe input position is not correct.

Programmer responseCorrect the application to assure that a valid position isspecified.


C072003F

ExplanationThe fseek() or fseeko() function was called to relativelyreposition with an offset greater than LONG_MAXin an OS data set using blocked I/O. The run-time supports data sets up to LONG_MAX blocksin size. Repositioning beyond LONG_MAX blocks isunsupported.

Programmer responseCorrect the application to assure the relative offset isnot greater than LONG_MAX.


C0720040


ExplanationAttempting to seek to before the first block is notpermitted.

Programmer responseCorrect the application to assure the requestedposition is not before the BOF.


C0720041




C0720042


Programmer responseCorrect the application to assure the requestedposition is not before BOF.


C0720043


Programmer responseCorrect the application to assure the requestedposition is not beyond EOF.


C0720044


Programmer responseCorrect the application to assure the requestedposition is not before the BOF.


C0720045

ExplanationInput Whence to fseek() is not correct.

Programmer responseCorrect the application to specify a valid Whence


C0720046




C0720050


Programmer responseCorrect the application to assure the requestedposition is not before BOF.


Symbolic Feedback CodeJrEdcP131Ebeforebof01

C0720059

ExplanationCurrent block position is not available


Symbolic Feedback CodeJrEdcP131Eutility01

C0720060

ExplanationPDS member cannot be extended if opened for update.

Programmer responseCorrect the application. Only write mode is supportedto extend a PDS member.

Symbolic Feedback CodeJrEdcP131Eextend01

C112000C

ExplanationThe thread argument to pthread_create() was NULL.

Programmer responseCorrect the thread argument.

Symbolic Feedback CodeJrEdcPc__Einval01

C1120015

ExplanationThe pthread_create() function was called in the childof a multithread fork(). This is not supported.


Symbolic Feedback CodeJrEdcPc__Elemultithreadfork01

C1180045

ExplanationThe mutex is not owned by the calling thread.

Programmer response

Symbolic Feedback CodeJrEdcXfr3Einval22

C1180046

ExplanationArgument abstime is null

Programmer response


C1180047


Programmer response


C1180048

ExplanationAddress exception while reference cond arugment

Programmer response


C1180049

ExplanationInvalid mutex object


Programmer response


C118004A

ExplanationArgument tv_sec not invlid

Programmer response


C118004B

ExplanationArgument tv_nsec not invalid

Programmer response


C118004C

ExplanationAnother mutex has been associated with this condobject

Programmer response


C118004D


Programmer response


C118004E

ExplanationMutex not initialized

Programmer response


C118006C

ExplanationInsufficient memory exists to associate the threadspecific data with the key.

Programmer response


C118007D

ExplanationArgument cond not initialized

Programmer response


C1180081

ExplanationLength of applid exceeds the maximum lengthallowed.

Programmer responseProvide correct applid.


C1180082

ExplanationLength of password exceeds the maximum lengthallowed.


Programmer responseProvide correct password.


C1180083

ExplanationLength of userid exceeds the maximum lengthallowed.

Programmer responseProvide correct userid.


C1180084

ExplanationLength of applid exceeds the maximum lengthallowed.

Programmer responseProvide correct applid.


C1180085

Explanationargument abstime is null

Programmer response


C1180086


Programmer response


C1180087

ExplanationArgument cond not initialized

Programmer response


C1180088

ExplanationAddress exception while reference cond argument

Programmer response


C1180089

ExplanationInvalid Mutex Object

Programmer response


C118008A

ExplanationArgument tv_sec is not valid

Programmer response


C118008B

ExplanationArgument tv_nsec is not valid


Programmer response


C118008C

ExplanationAnother mutex has been associated with this condobject

Programmer response


C118008D


Programmer response


C118008E

ExplanationMutex not initialized

Programmer response


C1180099

ExplanationUnable to allocate storage for fork handler list.

Programmer response

Symbolic Feedback CodeJrEdcXfr3Enomem10

C118009A

ExplanationUnable to allocate storage for fork handler list.

Programmer response

Symbolic Feedback CodeJrEdcXfr3Enomem11

C11800A8

ExplanationTime out

Programmer response

Symbolic Feedback CodeJrEdcXfr3Etimedout01

C11800A9

ExplanationTime out

Programmer response

Symbolic Feedback CodeJrEdcXfr3Etimedout02

C20F000B

ExplanationThe conversion was unable to allocate layout buffersfor the Bidi shaping transformation.


Symbolic Feedback CodeJrEdcWcstEnomem01

C20F000C





C20F000D




C20F000E




C20F0014




C2100001

ExplanationLocale name ending in .xplink requested. InAMODE64, applications must use AMODE64 locales.

Programmer responseRefer to the XL C/C++ Programming Guide for anexplanation of locale naming conventions.

Symbolic Feedback CodeJrEdcStlcHEinval01

C2100002

ExplanationLocale name ending in .lp64 requested. AMODE64locales are only supported in AMODE64 environments.



C2100003

ExplanationLocale name ending in .xplink requested. InAMODE64, applications must use AMODE64 locales.



C2100004

ExplanationLocale name ending in .lp64 requested. AMODE64locales are only supported in AMODE64 environments.



C2290001


ExplanationThe input pointer to the number of seconds since theEpoch is either missing or points to a negative value.

Programmer responseGive gmtime() a valid pointer as input.

Symbolic Feedback CodeJrEdcGmtmEoverflow01

C2290002

ExplanationThe input number of seconds represents a date thatconverts to a year greater than 9999.

Programmer responseCheck the input value passed to gmtime().


C2290003


Programmer responseGive localtime() a valid pointer as input.


C2290004

ExplanationThe difference between the number of seconds andthe time zone offset is not representable in a tmstructure

Programmer responseCorrect the value pointed to as input to localtime().


C2290005

ExplanationThe input arg to localtime() points to a number ofseconds that converts to a year greater than 9999.



C2290006




C2290007

ExplanationThe adjusted local time cannot be represented in atime_t.



C2290008




C2290009



Programmer responseGive localtime64() a valid pointer as input.


C229000A

ExplanationThe difference between the number of seconds andthe time zone offset is not representable in a tmstructure

Programmer responseCorrect the value pointed to as input to localtime64().


C229000B

ExplanationThe input arg to localtime64() points to a number ofseconds that converts to a year greater than 9999.



C229000C




C229000D

ExplanationThe adjusted local time cannot be represented in atime64_t.



C229000E




C229000F


Programmer responseGive gmtime64() a valid pointer as input.


C2290010

ExplanationThe input number of seconds represents a date thatconverts to a year greater than 9999.

Programmer responseCheck the input value passed to gmtime64().


C22C0005


ExplanationAn invalid conversion descriptor was used

Programmer responseCorrect the conversion descriptor and try again.

Symbolic Feedback CodeJrEdcIcntEbadf05

C22C0006

ExplanationAn invalid conversion handle was used.

Programmer responseCorrect the conversion handle and try again.


C22C0007

ExplanationThe storage trying to be free()'ed is NULL.

Programmer responseFix the conversion handle and try again.


C22C0008




C22C0009


Programmer responseFix the conversion descriptor and try again.


C22C001C

ExplanationThe from CCSID cannot be determined.

Programmer responseThe from converter name is invalid. Fix it and try again.

Symbolic Feedback CodeJrEdcIcntEinval16

C22C001D

ExplanationThe to CCSID cannot be determined.

Programmer responseThe to converter name is invalid. Fix it and try again.


C22C001E

ExplanationEither Unicode Services does not support conversionbetween the specified character sets or elsethe Unicode Services environment is not properlyconfigured.

Programmer responseRefer to the Unicode Services User's Guide andReference (SA22-7649) to make sure that theconversion is supported and that the Unicode Servicesdata sets are installed and catalogued correctly.


C22C001F


ExplanationAn invalid outbuf pointer or pointer to outbuf wasused.

Programmer responseCorrect the pointer and try again.


C22C0030

Explanationmalloc() failed.

Programmer responseFree up system memory.

Symbolic Feedback CodeJrEdcIcntEnomem04

C22C0031




C22C0032




C22C0040

ExplanationThe convert to characters will not fit in the outbuf.

Programmer responseIncrease the size of the outbuf and try again.

Symbolic Feedback CodeJrEdcIcntE2big01

C2340001

ExplanationThe year is less than 1969 or greater than 2037.

Programmer responseAdjust the year in the input tm structure.

Symbolic Feedback CodeJrEdcMktmEoverflow01

C2340002

ExplanationThe computed year is greater than 9999.



C2340003




C2340004





C2340005

ExplanationThe date computed from the broken-down timeinput to the mktime() function exceeds year 2037(AMODE31) or 9999 (AMODE64).

Programmer responseAdjust the values in the input tm structure.


C2340006

ExplanationThe year is less than 1969 or greater than 9999.



C2340007




C2340008




C2340009




C234000A

ExplanationThe date computed from the broken-down time inputto the mktime64() function exceeds year 9999.

Programmer responseAdjust the values in the input tm structure.


C2410001

ExplanationXPLINK locales are only supported in xplinkenvironments.


Symbolic Feedback CodeJrEdcStclEinval01

C2410002

ExplanationAMODE64 locales are only supported in AMODE64environments.



Symbolic Feedback CodeJrEdcStclEinval02

C2430001

ExplanationThe system time of day (TOD) clock is in error,stoppped, or in a non-operational state. The time()function fails and processing continues.


Symbolic Feedback CodeJrEdcTimeEmvstodnotset01

C2430002

ExplanationThe system time of day (TOD) clock is in error,stoppped, or in a non-operational state. The time()function fails and processing continues.



C2430003

ExplanationThe system time of day (TOD) clock is in error,stoppped, or in a non-operational state. The time64()function fails and processing continues.



C2430004

ExplanationThe system time of day (TOD) clock is in error,stoppped, or in a non-operational state. The time64()function fails and processing continues.



C25F0001

ExplanationA conversion was attempted using a non-supportedccsid.

Programmer responseCorrect the ccsid and try again.

Symbolic Feedback CodeJrEdcCdpgEbadf01

C25F000A

ExplanationAn unexpected error was encountered from UnicodeServices.

Programmer responseA return and reason code will be issued.

Symbolic Feedback CodeJrEdcCdpgEcunerr01

C25F0013

ExplanationUnicode Services issued a CUN_RS_NO_CONVERSIONerror.

Programmer responseRefer to Unicode Services pub for action.

Symbolic Feedback CodeJrEdcCdpgEcunnoconv01

C25F001C

ExplanationA CUN_RS_NO_UNI_ENV error was issued by UnicodeServices.



Symbolic Feedback CodeJrEdcCdpgEcunnoenv01

C25F0025

ExplanationUnicode Services issued aCUN_RS_TABLE_NOT_ALIGNED error.


Symbolic Feedback CodeJrEdcCdpgEcunnotaligned01

C25F002E

ExplanationAn invalid character was encountered in the inputbuffer.

Programmer responseCorrect the character in the input buffer.

Symbolic Feedback CodeJrEdcCdpgEilseq01

C25F0037

Explanationmalloc failed.


Symbolic Feedback CodeJrEdcCdpgEnomemory01

C25F0038

Explanationmalloc failed.


Symbolic Feedback CodeJrEdcCdpgEnomemory02

C25F0040

ExplanationThe size of the output buffer is to small.

Programmer responseIncrease the size of the output buffer.

Symbolic Feedback CodeJrEdcCdpgE2big01

C25F0041




C25F0042




C25F0048

ExplanationAn incomplete character was encountered in inputbuffer.

Programmer responseCorrect the character in the input buffer.


Symbolic Feedback CodeJrEdcCdpgEinval01

C2600001

ExplanationAn invalid conversion descriptor was used

Programmer responseCorrect the conversion descriptor and try again.

Symbolic Feedback CodeJrEdcZzzzEbadf01

C2600002

ExplanationAn invalid conversion handle was used.

Programmer responseCorrect the conversion handle and try again.


C2600003




C2600004




C2600005


Programmer responseFix the conversion descriptor and try again.


C260000E

ExplanationAn invalid outbuf pointer or pointer to outbuf wasused.

Programmer responseCorrect the pointer and try again.

Symbolic Feedback CodeJrEdcZzzzEinval01

C260000F

ExplanationThe from CCSID cannot be determined.

Programmer responseThe from converter name is invalid. Fix it and try again.


C2600010

ExplanationThe to CCSID cannot be determined.

Programmer responseThe to converter name is invalid. Fix it and try again.


C2600011


ExplanationConversion to/from the character sets specified is notsupported.

Programmer responseUse a supported to/from character set and try again.


C260001A



Symbolic Feedback CodeJrEdcZzzzEnomem01

C260001B




C260001C




C2600025

ExplanationThe convert to characters will not fit in the outbuf.

Programmer responseIncrease the size of the outbuf and try again.

Symbolic Feedback CodeJrEdcZzzzE2big01

C3030001

ExplanationThe output value exponent caused overflow.

Programmer responseSpecify corect exponent for input values.

Symbolic Feedback CodeJrEdc0sclErange01

C3030002

ExplanationThe output values caused underflow.

Programmer responseSpecify correct input values.


C3030003




C3030004





C3030005




C3030006




C3031001

ExplanationThe input value of log10() was negative, a domain errorhappened.

Programmer responseTo avoid this error, specify a reasonable input value.

Symbolic Feedback CodeJrEdcflg1Edom01

C303100A

ExplanationThe input value of log10() was equal to 0.0, a poleerror happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a positive double type number.

Symbolic Feedback CodeJrEdcflg1Erange01

C30A0001

ExplanationThe input value of log2l() was less than 0.0, a domainerror happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a positive long double number.

Symbolic Feedback CodeJrEdcLlg2Edom01

C30A000A

ExplanationThe input value of log2l() was equal to 0.0, a pole errorhappened.


Symbolic Feedback CodeJrEdcLlg2Erange01

C3101001

ExplanationThe result overflowed.

Programmer responseChange the value of x or n.

Symbolic Feedback CodeJrEdcSsbnErange01

C3101002


Programmer responseChange the value of x or n


Symbolic Feedback CodeJrEdcSsbnErange02

C3110001

ExplanationInput Decimal Floating Point argument was too large

Programmer responseMake sure the input argument is within range for thisfunction

Symbolic Feedback CodeJrEdc0expErange01

C3110002

ExplanationInput Decimal Floating Point argument was too small



C3110003




C3110004




C3110005




C3110006




C3110007




C3110008





C3120001

ExplanationThe Decimal Floating Point aggument is not valid.

Programmer responseMake sure the input argument is valid for this function.

Symbolic Feedback CodeJrEdc0logEdom01

C3120002




C3120003




C3131001

ExplanationThe input value of log1p() function was out ofreasonable input range, a domain error happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a double number that greater than-1.0.

Symbolic Feedback CodeJrEdcfl1pEdom01

C313100A

ExplanationThe input value of log1p() was equal to -1.0, a poleerror happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a double number that greater than-1.0.

Symbolic Feedback CodeJrEdcfl1pErange01

C3200001

ExplanationThe input parameter is out of range.

Programmer responseSpecify a correct input parameter value.

Symbolic Feedback CodeJrEdc0achEdom01

C3200002




C3200003





C3231001

ExplanationThe first input value of pow() was less than 0.0,while the second one was non-integer, a domain errorhappened.

Programmer responseSpecify reasonable input values.

Symbolic Feedback CodeJrEdcfpowEdom01

C323100A

ExplanationThe first argument of pow() was equal to 0.0, while thesecond one was less than 0.0, a pole error happened.


Symbolic Feedback CodeJrEdcfpowErange01

C323100B

ExplanationThe result of pow() causes an overflow, a range errorhappened.



C323100C




C323100D




C32A0001

ExplanationThe input value of log1pl() was less than -1.0, adomain error happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a long double number that greaterthan -1.0.

Symbolic Feedback CodeJrEdcLlgpEdom01

C32A000A

ExplanationThe input value of log1pl() was equal to -1.0, a poleerror happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a long double number that greaterthan -1.0.

Symbolic Feedback CodeJrEdcLlgpErange01

C3300001




Symbolic Feedback CodeJrEdc0acsEdom01

C3300002




C3300003




C3330001



Symbolic Feedback CodeJrEdc0sinEdom01

C3330002




C3330003




C3330004




C3330005




C3330006





C33A0002

ExplanationThe input value of logl() was less than 0.0, a domainerror happened.


Symbolic Feedback CodeJrEdcLlogEdom02

C33A000A

ExplanationThe input value specified for x for the logl() functionwas zero.

Programmer responseSpecify a correct input value.

Symbolic Feedback CodeJrEdcLlogErange01

C3410001



Symbolic Feedback CodeJrEdc0fmdEdom01

C3410002




C3410003




C3410004




C3410005




C3410006




C3430001




Symbolic Feedback CodeJrEdc0snhErange01

C3430002




C3430003




C3430004




C3430005




C3430006




C34A0001

ExplanationRange error in llround funct, argument is too big.

Programmer response

Symbolic Feedback CodeJrEdcLlrdErange01

C34A0002

ExplanationRange error in llroundl funct, argument is too small.

Programmer response


C34A0003

ExplanationRange error in llroundl funct, argument is too big.

Programmer response


C34A0004


ExplanationRange error in llroundf, argument is too big.

Programmer response


C3500001



Symbolic Feedback CodeJrEdc0asnEdom01

C3500002




C3500003




C3600001



Symbolic Feedback CodeJrEdc0at2Edom01

C3600002




C3600003




C3630001

ExplanationInput Decimal Floating Point argument was negative

Programmer responseMake sure the input argument is a non-negativeDecimal Floating Point number

Symbolic Feedback CodeJrEdc0sqtEdom01

C3630002





C3630003




C3650001

ExplanationThe number passed to exp2() is greater than themaximum allowed.

Programmer responsePass in a number in range.

Symbolic Feedback CodeJrEdcExp2Erange01

C3650002

ExplanationThe number passed to exp2() is less than the minimumallowed.


Symbolic Feedback CodeJrEdcExp2Erange02

C3730001



Symbolic Feedback CodeJrEdc0tanEdom01

C3730002




C3730003




C3750001

ExplanationThe result of atan2f() causes an underflow, a rangeerror happened.


Symbolic Feedback CodeJrEdcF2d_Erange01

C3750002

ExplanationThe result of coshf() causes an overflow, a range errorhappened.




C3750003

ExplanationThe result of expf() causes an overflow, a range errorhappened.



C3750004

ExplanationThe result of expf() causes an underflow, a range errorhappened.



C3750005

ExplanationThe result of ldexpf() causes an overflow, a range errorhappened.



C3750006

ExplanationThe result of ldexpf() causes an underflow, a rangeerror happened.



C3750007

ExplanationThe result of powf() causes an overflow, a range errorhappened.



C3750008

ExplanationThe result of powf() causes an underflow, a range errorhappened.



C3750009

ExplanationThe result of sinhf() causes an overflow, a range errorhappened.



C375000A

ExplanationThe result of sinhf() causes an overflow, a range errorhappened.




C375000B

ExplanationThe result of sinhf() causes an underflow, a range errorhappened.



C375000C

ExplanationThe result of tanf() causes an overflow, a range errorhappened.



C375000D

ExplanationThe result of tanf() causes an overflow, a range errorhappened.



C375000E

ExplanationThe result of tanf() causes an underflow, a range errorhappened.



C375000F

ExplanationThe result of cotanf() causes an overflow, a range errorhappened.



C3750010

ExplanationThe result of exp2f() causes an overflow, a range errorhappened.



C3750011

ExplanationThe result of exp2f() causes an underflow, a rangeerror happened.



C3750012

ExplanationThe result of expm1f() causes an overflow, a rangeerror happened.




C3750013

ExplanationThe result of hypotf() causes an overflow, a range errorhappened.



C3750014

ExplanationThe result of lgammaf() causes an overflow, a rangeerror happened.



C3750015

ExplanationThe result of tgammaf() causes an overflow, a rangeerror happened.



C3750016

ExplanationThe input value specified for x for the logf() functionwas zero.



C3750017

ExplanationThe input value of log10f() was equal to 0.0, a poleerror happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a positive float type number.


C3750018

ExplanationThe input value of log1pf() was equal to -1.0, a poleerror happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a float number that greater than -1.0.


C3810001



Symbolic Feedback CodeJrEdc0gmaEdom01

C3810002





C3810003




C3810004




C3810005




C3810006




C381000F



Symbolic Feedback CodeJrEdc0gmaErange01

C3810010




C3810011




C3810012





C3810013




C3810014




C3810015




C3810016




C3810017




C3810018




C3810019




C381001A




C38F0001

ExplanationThe value of x = 0.


Programmer responseAdjust the value of x.

Symbolic Feedback CodeJrEdcSilbEdom01

C38F0002

ExplanationThe value of x is INF or NaN.

Programmer responseAdjust the value of x.

Symbolic Feedback CodeJrEdcSilbEdom02

C3910001



Symbolic Feedback CodeJrEdc0hypErange01

C3910002




C3910003




C3910004




C3910005




C3920001

ExplanationThe input value specified for x was zero.


Symbolic Feedback CodeJrEdc0nxaErange01

C3920002

ExplanationThe input values in a call to nextafterd32() causedoverflow.

Programmer responseSpecify correct input values



C3920003

ExplanationThe input values in a call to nextafterd32() causedunderflow.



C3920004




C3920005




C3920006




C3920007




C3920008




C3920009




C395000D

ExplanationThe rounding mode specified in envp is not valid.

Programmer responseCheck the specified rounding mode.

Symbolic Feedback CodeJrEdcFenvEinval13

C395000E


ExplanationThe specified rounding mode is not valid.



C395000F

ExplanationThe rounding mode specified in envp is not valid.



C3950018

ExplanationThe rounding mode stored in the FPC register is notthe same that the one specified by the user.


Symbolic Feedback CodeJrEdcFenvEmvserr01

C3950019




C3950020




C39A0001

ExplanationThe input value of log2()/log2f() was less than 0.0, adomain error happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a positive double/float number.

Symbolic Feedback CodeJrEdcLog2Edom01

C39A000A

ExplanationThe input value of log2()/log2f() was equal to 0.0, apole error happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a positive double/float number.

Symbolic Feedback CodeJrEdcLog2Erange01

C3A00001



Symbolic Feedback CodeJrEdc0cosEdom01

C3A00002





C3A00003




C3A00004




C3A00005




C3A00006




C3A10001

ExplanationThe input value specified is not a number.


Symbolic Feedback CodeJrEdc0ilbEdom01

C3A10002

ExplanationThe input value specified is infinity.



C3A10003

ExplanationThe input value specified zero.



C3A10004





C3A10005




C3A10006




C3A10007




C3A10008




C3A10009




C3A30001



Symbolic Feedback CodeJrEdc0xp2Erange01

C3A30002




C3A30003




C3A30004





C3A30005




C3A30006




C3A30007




C3A30008




C3A30009




C3A60001

ExplanationThe number passed to llround() is not in the validrange.


Symbolic Feedback CodeJrEdcHlrdErange01

C3A60002

ExplanationThe number passed to llroundl() is less than theminimum value allowed.



C3A60003

ExplanationThe number passed to llroundl() is greater than themaximum value allowed.




C3A60004

ExplanationThe number passed to llroundl() is greater than themaximum value allowed.



C3A60005

ExplanationThe number passed to llroundf() is less than theminimum value allowed.



C3B10001



Symbolic Feedback CodeJrEdc0l1pEdom01

C3B10002




C3B10003




C3B30001

ExplanationInput Decimal Floating Point value was not valid

Programmer responseMake sure to use the proper input values

Symbolic Feedback CodeJrEdc0xpyEdom01

C3B30002




C3B30003





C3B3000C



Symbolic Feedback CodeJrEdc0xpyErange01

C3B3000D




C3B3000E

ExplanationInput Decimal Floating Point caused overflow orunderflow



C3B3000F




C3B30010




C3B30011




C3B30012




C3B30013





C3B30014




C3B90001

ExplanationDomain error in fmodl() function: Division by 0 isundef.

Programmer response

Symbolic Feedback CodeJrEdcLfmdEdom01

C3B90002

ExplanationDomain error in fmodl() function: Division by 0 isundef.

Programmer response

Symbolic Feedback CodeJrEdcLfmdEdom02

C3C00001



Symbolic Feedback CodeJrEdc0cshErange01

C3C00002




C3C00003




C3C00004




C3C00005




C3C00006





C3C10001

ExplanationThe Decimal Floating Point input argument was notvalid.


Symbolic Feedback CodeJrEdc0lg1Edom01

C3C10002




C3C10003




C3C20001



Symbolic Feedback CodeJrEdc0remEdom01

C3C20002




C3C20003




C3C20004




C3C20005





C3C20006




C3CA0001

ExplanationThe first input value of powl() was less than 0.0,while the second one was non-integer, a domain errorhappened.


Symbolic Feedback CodeJrEdcLpowEdom01

C3CA000A

ExplanationThe result of powl() causes an overflow, a range errorhappened.


Symbolic Feedback CodeJrEdcLpowErange01

C3CA000B

ExplanationThe result of powl() causes an underflow, a range errorhappened.



C3CA000C




C3CA000D




C3CA000E




C3CA000F





C3CA0010

ExplanationThe first argument of powl() was equal to 0.0, whilethe second one was less than 0.0, a pole errorhappened.



C3D00001

ExplanationThe result of a call to fdim32() is out of the range.

Programmer responseCorrect the input values in this call.

Symbolic Feedback CodeJrEdc0dimErange01

C3D00002




C3D00003




C3D10001




C3D10002




C3D10003




C3D20001




Symbolic Feedback CodeJrEdc0rmqEdom01

C3D20002




C3D20003




C3D20004




C3D20005




C3D20006




C3E00001



Symbolic Feedback CodeJrEdc0em1Erange01

C3E00002




C3E00004




C3E00006





C3E10001



Symbolic Feedback CodeJrEdc0lgbEdom01

C3E10002




C3E10003




C3E21001



Symbolic Feedback CodeJrEdc0qxpEdom01

C3E21002




C3E21003




C3E21004




C3E21005





C3E21006




C3F00001



Symbolic Feedback CodeJrEdc0ercErange01

C3F00002




C3F00003




C3F00004




C3F10001



Symbolic Feedback CodeJrEdc0lgmErange01

C3F10002




C3F10003




C3F10004





C3F10005




C3F10006




C3F10007




C3F21001

ExplanationThe input value specified for x for the log() functionwas zero.


Symbolic Feedback CodeJrEdcflogErange01

C3F90001

ExplanationThe input value of log10l() function was out ofreasonable input range, a domain error happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a positive long double type number.

Symbolic Feedback CodeJrEdcLlg1Edom01

C3F9000B

ExplanationThe input value of log10l() was equal to 0.0, a poleerror happened.

Programmer responseTo avoid this error, specify a reasonable input valuewhich should be a positive long double type number.

Symbolic Feedback CodeJrEdcLlg1Erange01

C3FF0001


Programmer responseChange the values of x or y.

Symbolic Feedback CodeJrEdcSnxaErange01

C4030020

ExplanationAn error was detected during a call to dlopen() - a64-bit caller tried to load a 31-bit dll.


Programmer responseSee feedback code CEE3G4 (message CEE3588S) formore information.

Symbolic Feedback CodeJrEdcDlopDlmode6401

C4030021

ExplanationAn error was detected during a call to dlopen() - a31-bit caller tried to load a 64-bit dll.

Programmer responseSee feedback code CEE3G4 (message CEE3588S) formore information.

Symbolic Feedback CodeJrEdcDlopDlmode6401

C112001F

ExplanationMultithread is not supported when 31/64interoperability.

Programmer responseDo not use multithreading in this scenario.

Symbolic Feedback CodeJrEdcPc__Eagain01

C4070001

ExplanationAn error was detected during a call to fetch().

Programmer responseThe errno decimal value is adjusted by +100000.Subtract 100000 to find the CEE messagenumber that is associated with the failure. SeeLanguage Environment Run-Time Messages for moreinformation. Contact IBM if you are not able to resolvethe problem.

Symbolic Feedback CodeJrEdcFtchE__lemap01

C407000A

ExplanationThe program called release(). The fetch pointer passedas the argument was NULL.

Programmer responseCorrect the argument.

Symbolic Feedback CodeJrEdcFtchEinval01

C407000B

ExplanationThe program called release(). The fetch pointer passedas the argument was not valid.

Programmer responseCorrect the argument. Ensure that the fetch pointer isactive and valid. If you cannot correct the problem,contact your service representative, as this may be aninternal error.


C407000C

ExplanationThe program called release(). The fetch pointer passedas the argument was not valid. The fetch pointer refersto an internal control structure whose address was notfound.



C407000D

ExplanationThe program called release(). The fetch pointer passedas the argument was not valid. The fetch pointer refersto an internal control structure whose address wasfound, but is marked not active.




C4070020

ExplanationStorage could not be obtained during a call to fetch().

Programmer responseEnsure sufficient storage is available or contact yourservice representative.

Symbolic Feedback CodeJrEdcFtchEnomem02

C4070021




C4070022




C4070023




C4070024

ExplanationStorage could not be obtained during a call torelease().



C4070025

ExplanationStorage could not be obtained during a call tofetchep().



C4070026





C4070027




C4070028




C4070031

ExplanationThe program called fetch() to load a module. Theapplication is not running in an XPLINK environment,but attempted to fetch an XPLINK program object. Thisis not allowed.

Programmer responseEither run under XPLINK(ON) or change theapplication so that it does not fetch an XPLINKprogram object.

Symbolic Feedback CodeJrEdcFtchFbadxplink01

C4070032

ExplanationThe program called fetch() to load a module. Theapplication is not running in an XPLINK environment,but attempted to fetch a program object containing a

combination of XPLINK and non-XPLINK code. This isnot allowed.

Programmer responseCorrect the application. You cannot mix XPLINK andnon-XPLINK in the same program object.

Symbolic Feedback CodeJrEdcFtchFbadxplink02

C407003B

ExplanationThe program called fetch() to load a module. The loadfailed.

Programmer responseCheck the JOBLOG for additional messages. Checkthe original abend from the operating system andrefer to the underlying operating system messagemanual for explanation and programmer response.The module name specified in the message may havebeen truncated for display purposes. See messagesEDC5241S and CEE3503S for more information.

Symbolic Feedback CodeJrEdcFtchFcfailed01

C4070044

ExplanationThe program called fetch() to load a module. Themodule was not found.

Programmer responseMake sure the program is loading the correct module.Make sure the proper libraries are available to theprogram. See messages EDC5239S and CEE3501S formore information.

Symbolic Feedback CodeJrEdcFtchFcmodnf01

C407004D

ExplanationThe program called fetch() to load a module. Themodule name is too long.


Programmer responseCorrect the module name length. See messagesEDC5240S and CEE3502S for more information.

Symbolic Feedback CodeJrEdcFtchFcmodtl01

C4070056

ExplanationThe program called fetch() to load a module. Anauthorized program requested the load of a modulethat could not be found in an authorized library orconcatenation of libraries.

Programmer responseMake sure the module exists in a system or user-defined authorized library. See messages EDC5242Sand CEE3518S for more information.

Symbolic Feedback CodeJrEdcFtchFcnoauthlib01

C407005F

ExplanationThe program called fetch() to load a module.Insufficient virtual memory was available.

Programmer responseEnsure that the region size is sufficient to run theapplication. See messages EDC5238E and CEE3500Sfor more information.

Symbolic Feedback CodeJrEdcFtchFcnostg01

C4070068

ExplanationThe program called fetch() to load a module. Theapplication is running AMODE 64 but attempted toload a module that is not AMODE 64. This is notallowed.


Symbolic Feedback CodeJrEdcFtchFetcmode3101

C4070071

ExplanationThe program called fetch() to load a module. Theapplication is running AMODE 31 but attempted toload a module that is AMODE 64. This is not allowed.


Symbolic Feedback CodeJrEdcFtchFetcmode6401

C407007A

ExplanationThe program called fetch() to load a module. Thefetched executable has CEESTART as the entry point,but does not contain a fetchable entry point. It couldbe that a "main" is being used as the target of thefetch() function, which is not allowed.

Programmer responseCorrect the application. Do not use a "main" as thetarget of the fetch(). For a C executable that is not a"main" and has CEESTART as the entry point, declarethe routine as fetchable by specifying the #pragmalinkage(...,fetchable) directive in the source code. Fornon-C languages, be sure to follow the proper ruleswhen building an executable that will be the target offetch().

Symbolic Feedback CodeJrEdcFtchFnoceefmain01

C407007B

ExplanationThe program called fetch() to load a module. Thefetched executable is XPLINK, but does not haveCEESTART as the entry point. This is not allowed.

Programmer responseCorrect the application. An XPLINK C executablethat is to be the target of fetch() must haveCEESTART as the entry point and have the fetchable


entry point defined by specifying the #pragmalinkage(...,fetchable) directive in the source code.

Symbolic Feedback CodeJrEdcFtchFnoceefmain02

C40B000A

ExplanationThe Language Environment service called to load theDLL failed.

Programmer responseA CEEDLLF DLL failure control block is populated withfurther DLL error diagnostics. If the _EDC_DLL_DIAGenvironment variable is not set to QUIET, theerror message is sent to the Language Environmentmessage file. Other DLL diagnostic options, such asissuing ctrace(), signaling a condition, and the abilityto turn off _EDC_DLL_DIAG diagnostics, are availablethrough the _EDC_DLL_DIAG environment variable.

Symbolic Feedback CodeJrEdcDldeDlfailed01

C40B000B

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE378 (messageCEE3304E).

Programmer responseSee feedback code CEE378 for more information.


C40B000C

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE3DF (messageCEE3503S).

Programmer responseSee feedback code CEE3DF for more information.


C40B000D

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE3F0 (messageCEE3552S).

Programmer responseSee feedback code CEE3F0 for more information.


C40B0013

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE3G3 (messageCEE3587S).

Programmer responseSee feedback code CEE3G3 for more information.

Symbolic Feedback CodeJrEdcDldeDlmode3101

C40B001C

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE3G4 (messageCEE3588S).

Programmer responseSee feedback code CEE3G4 for more information.

Symbolic Feedback CodeJrEdcDldeDlmode6401

C40B0025

ExplanationThe Language Environment service called to load theDLL failed with feedback code CEE3DD (messageCEE3501S).


Programmer responseSee feedback code CEE3DD for more information.

Symbolic Feedback CodeJrEdcDldeDlmodnf01

C40B0026

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE3FI (messageCEE3570S).

Programmer responseSee feedback code CEE3FI for more information.

Symbolic Feedback CodeJrEdcDldeDlmodnf02

C40B002F

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE3DE (messageCEE3502S).

Programmer responseSee feedback code CEE3DE for more information.

Symbolic Feedback CodeJrEdcDldeDlmodtl01

C40B0038

ExplanationThe Language Environment service called to load theDLL failed with feedback code CEE3DU (messageCEE3518S).

Programmer responseSee feedback code CEE3DU for more information.

Symbolic Feedback CodeJrEdcDldeDlnoauthlib01

C40B0041

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE3DC (messageCEE3500S).

Programmer responseSee feedback code CEE3DC for more information.

Symbolic Feedback CodeJrEdcDldeDlnostg01

C40B0042




C40B0043

ExplanationNot enough storage was available to allocate a bufferto contain the DLL name translated from ASCII toEBCDIC.

Programmer responseEnsure that the REGION size is large enough to run theapplication. If necessary, delete modules not currentlyneeded by the application, or free unused storage, andretry the load request.


C40B004B




Symbolic Feedback CodeJrEdcDldeDlnoxplopt01

C40B0054

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE3FB (messageCEE3563S).

Programmer responseSee feedback code CEE3FB for more information.

Symbolic Feedback CodeJrEdcDldeDloadns01

C40B005D

ExplanationThe Language Environment service called to loadthe DLL failed with feedback code CEE3EU (messageCEE3550S).

Programmer responseSee feedback code CEE3EU for more information.

Symbolic Feedback CodeJrEdcDldeDnoceestart01

C40B005E

ExplanationThe Language Environment service called to load theDLL failed with feedback code CEE3GB (messageCEE3595S).

Programmer responseSee feedback code CEE3GB for more information.

Symbolic Feedback CodeJrEdcDldeDnoceestart02

C40B0066

ExplanationDLL facilities are not supported under SPCenvironment.

Programmer responseMake sure that dllload(), dllqueryvar(), dllqueryfn(),and dllfree() functions are not invoked from yourapplication.

Symbolic Feedback CodeJrEdcDldeDnotspc01

C40B0078

ExplanationThe size of the DLL name string exceeded themaximum allowed.

Programmer responseVerify that the DLL name was specified correctly.

Symbolic Feedback CodeJrEdcDldeEnametoolong01

C413001A

ExplanationThe execle() function failed because it was invokedfrom a multithread environment.


Symbolic Feedback CodeJrEdcExecElemultithread01

C413001B

ExplanationThe execv() function failed because it was invokedfrom a multithread environment.



C413001C


ExplanationThe execve() function failed because it was invokedfrom a multithread environment.



C4130025

ExplanationThe pathname argument passed to __execl() exceededthe maximum length of 1024 characters.


Symbolic Feedback CodeJrEdcExecEnametoolong01

C4130026

ExplanationThe path argument passed to __execle() exceeded themaximum length of 1024 characters.



C4130027

ExplanationThe file parameter passed to __execlp() is greater thanthe allowed maximum of 1024.



C4130028

ExplanationThe path parameter passed to __execv() is greaterthan the allowed maximum of 1024.



C4130029

ExplanationThe pathname argument passed to __execve()exceeded the maximum length of 1024 characters.



C413002A

ExplanationThe file parameter passed to __execlp() is greater thanthe allowed maximum of 1024.



C413002B

ExplanationThe path parameter passed to __spawn() is greaterthan the allowed maximum of 1024.



C413002C


ExplanationThe path parameter passed to __spawnp() is greaterthan the allowed maximum of 1024.



C413002D

ExplanationThe path parameter passed to ____spawn2() is greaterthan the allowed maximum of 1024.



C413002E

ExplanationThe path argument passed to ____spawnp2()exceeded the maximum length of 1024 characters.



C4130037

ExplanationThe file parameter passed to function execlp() is NULL.


Symbolic Feedback CodeJrEdcExecEnoent01

C4130038

ExplanationThe file parameter passed to function __execve() isNULL.



C4130039

ExplanationThe file parameter passed to function execvp() isNULL.



C413003A

ExplanationThe file parameter passed to function __execvp() isNULL.



C413003B

ExplanationThe file parameter passed to function __spawn() isNULL.



C413003C


ExplanationThe file parameter passed to function spawnp() isNULL.



C413003D

ExplanationThe path parameter passed to function __spawnp() isNULL.



C413003E

ExplanationThe path parameter passed to function ____spawn2()is NULL.



C413003F

ExplanationThe file parameter passed to function __spawnp2() isNULL.



C4130040

ExplanationThe path parameter passed to function____spawnp2() is NULL.



C4130056

ExplanationIn execle(), the total size of the argumentsand environment variables exceeds 4096 and_SC_ARG_MAX.


Symbolic Feedback CodeJrEdcExecE2big01

C4130058

ExplanationIn execv(), the total size of the argumentsand environment variables exceeds 4096 and_SC_ARG_MAX.



C4130059

ExplanationIn execve(), the total size of the argumentsand environment variables exceeds 4096 and_SC_ARG_MAX.




C413005B

ExplanationIn spawn(), the total size of the argumentsand environment variables exceeds 4096 and_SC_ARG_MAX.



C413005D

ExplanationIn __spawn2(), the total size of the argumentsand environment variables exceeds 4096 and_SC_ARG_MAX.



C4170004

ExplanationThe system() function was attempted while runningunder CICS. This is not supported.

Programmer responseNo action can be taken. The function is not supported.

Symbolic Feedback CodeJrEdcSys_Ecics01

C4170006

ExplanationThe string argument passed to system() started with"PGM=" indicating an MVS program name. There wereat least 6 more characters following the programname, but the first 6 were not ",PARM=" as requiredby the syntax.

Programmer responseCorrect the string argument. When specifying an MVSprogram with parameters, the required syntax is:"PGM=program-name,PARM='program-parameters'"Note that the program-name must be a valid MVSprogram name.

Symbolic Feedback CodeJrEdcSys_Esystem01

C4170007

ExplanationThe string argument passed to system() started with"PGM=" indicating an MVS program name. Therewas at least 1 additional character, but less than 6,following the program name. This does not allow forthe ",PARM=" syntax for specifying parameters.

Programmer responseCorrect the string argument. When specifying an MVSprogram with parameters, the required syntax is:"PGM=program-name,PARM='program-parameters'"Note that the program-name must be a valid MVSprogram name.


C4170008

ExplanationThe string argument passed to system() startedwith "PGM=" indicating an MVS program name andcontained a ",PARM=" parameter string. A syntax errorwas found while parsing the program parameters.

Programmer responseCorrect the program parameters.


C417000C

ExplanationAn internal error occurred trying to allocate memoryfor the parameter list needed to process a system()call.



Symbolic Feedback CodeJrEdcSys_Enomemory01

C417000D




C417000E




C417000F




C4170010

ExplanationAn internal error occurred trying to allocate memoryfor the working storage and command to call _systso().

Programmer responseIncrease the storage available below the bar.


C4170020

ExplanationDuring a system() call, an error occurred trying togive control to the target program. For an AMODE 64application, a message was written to the C stderrstream, otherwise a message was written to theLanguage Environment Message File.

Programmer responseRefer to the message that was written for moreinformation on the cause of the failure.

Symbolic Feedback CodeJrEdcSys_Eload01

C507000F

ExplanationAn error occurred in CEEVCZST other than out ofmemory.

Programmer responseDetermine the CEE message from errno to investigatethe cause of the failure.

Symbolic Feedback CodeJrEdcAlocE__lemap01

C5100001

ExplanationThe minimum required __mopl_s size has not beenprovided.

Programmer responseChange the caller of __moservices() to provide storagefor the __mopl_s structure that is at least the size ofthe structure.


Symbolic Feedback CodeJrEdcVmosEinval01

C5100002

ExplanationA __mopl_s structure has not been provided.

Programmer responseChange the caller of __moservices() to provide a__mopl_s structure.


C5100003

ExplanationA moorigin field has not been provided.

Programmer responseChange the caller of __moservices() to provide amoorigin.


C5100004

ExplanationThe input dump priority was not with the valid range.

Programmer responseMake sure that the __moservices() caller is settinga dump priority within the range of 1 to 99 in the__mopldumppriority field of the __mopl_s structure.


C5100005

ExplanationThe size of the requested memory object has not beenprovided.

Programmer responseMake sure that the __moservices() caller is providing amemory object size within field __moplrequestsize ofthe __mopl_s structure.


C5100006

ExplanationA moorigin field has not been provided.

Programmer responseChange the caller of __moservices() to provide amoorigin.


C5100007

ExplanationThe memory object origin address is not above the bar.

Programmer responseMake sure that the caller of __moservices() isproviding a valid memory object origin.


C5100008

ExplanationThe memory object origin address is not a multiple of amegabyte.

Programmer responseMake sure that the caller of __moservices() isproviding a valid memory object origin.


C5100009


ExplanationThe minimum required __mopl_s size has not beenprovided.

Programmer responseChange the caller of __moservices() to provide storageor the __mopl_s structure that is at least the size ofthe structure.


C510000A

ExplanationA __mopl_s structure has not been provided.

Programmer responseChange the caller of __moservices() to provide a_mopl_s structure.


C510000B

ExplanationThe input dump priority was not with the valid range.

Programmer responseMake sure that the __moservices() caller is settinga dump priority within the range of 1 to 99 in the__mopldumppriority field of the __mopl_s structure.


C510000C

ExplanationRequested memory object service not supported.

Programmer responseMake sure that the caller of __moservices() isproviding a valid request type.


C510000D

ExplanationThe caller has requested more than one page framesize in the __mopl_s structure at the same time.

Programmer responseMake sure that only one of the pageframe size flags, __MOPL_PAGEFRAMESIZE1MEG,__MOPL_PAGEFRAMESIZEMAX,__MOPL_PAGEFRAMESIZE_PAGEABLE1MEG,__MOPL_PAGEFRAMESIZE_2G has been set in the__mopl_s structure.


C5100015

ExplanationThe call to the system component of LanguageEnvironment was not successful.

Programmer responseExamine the __mopl_iarv64_rc and__mopl_iarv64_rsn fields in the __mopl_s structure todetermine if the call to IARV64 failed.

Symbolic Feedback CodeJrEdcVmosEmvserr01

C5100016

ExplanationThe call to the system component of LanguageEnvironment was not successful.

Programmer responseExamine the __mopl_iarv64_rc and__mopl_iarv64_rsn fields in the __mopl_s structure todetermine if the call to IARV64 failed.


C5100017


Explanation__MO_SHMDUMPRIORITY cannot be requested in SRBor cross-memory mode.

Programmer responseEnsure the caller of __moservices() is running in non-cross memory task mode.


C5100018

ExplanationThe current PSW key does not match the key of theTHLI control block.

Programmer responseMake sure that the caller of __moservices() is runningwith a PSW key that matches that of the THLI.


C5100019

ExplanationThe call to the Preinit GETSTORE service routine wasnot successful.

Programmer responseExamine any diagnostic data the GETSTORE serviceroutine may have provided to determine the reason itfailed.


C510001A

ExplanationThe call to the Preinit FREESTORE service routine wasnot successful.

Programmer responseExamine any diagnostic data the FREESTORE serviceroutine may have provided to determine the reason itfailed.


C6030001

ExplanationThe __perror_a() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcPerrEwrongthd01

C6030002

ExplanationThe perror() function was called on a thread other thanthe one that opened the stream.



C6030003

ExplanationThe __perror_unlocked_a() function was called on athread other than the one that opened the stream.



C6030004

ExplanationThe perror_unlocked() function was called on a threadother than the one that opened the stream.




C8030001

ExplanationThe vfscanf() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcVscnEwrongthd01

C8030002

ExplanationThe vfscanf_unlocked() function was called on a threadother than the one that opened the stream.



C8030003

ExplanationThe vscanf() function was called on a thread other thanthe one that opened the stream.



C8030004

ExplanationThe vscanf_unlocked() function was called on a threadother than the one that opened the stream.



C8040001

ExplanationThe vfwscanf() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcVwscEwrongthd01

C8040002

ExplanationThe vfwscanf_unlocked() function was called on athread other than the one that opened the stream.



C8040003

ExplanationThe vwscanf() function was called on a thread otherthan the one that opened the stream.




C8040004

ExplanationThe vwscanf_unlocked() function was called on athread other than the one that opened the stream.



C8060001

ExplanationThe vfscanf2() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcXvscEwrongthd01

C8060002

ExplanationThe vfscanf2_unlocked() function was called on athread other than the one that opened the stream.



C8060003

ExplanationThe vscanf2() function was called on a thread otherthan the one that opened the stream.



C8060004

ExplanationThe vscanf2_unlocked() function was called on athread other than the one that opened the stream.



C8070001

ExplanationThe vfwscanf2() function was called on a thread otherthan the one that opened the stream.


Symbolic Feedback CodeJrEdcXvwsEwrongthd01

C8070002

ExplanationThe vfwscanf2_unlocked() function was called on athread other than the one that opened the stream.


Symbolic Feedback CodeJrEdcXvwsEwrongthd02

C8070003


z/os: z/os language environment runtime messages

Documents