z/os mvs system messages, vol 7 (ieb-iee) - ibm.com · vi z/os mvs system messages, v ol 7...

z/OS

MVS System Messages Volume 7 (IEB -IEE)Version 2 Release 3

SA38-0674-30

IBM

NoteBefore using this information and the product it supports, read the information in Notices on page 847.

This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modificationsuntil otherwise indicated in new editions.

Last updated: September 25, 2018

Copyright IBM Corporation 1988, 2017.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this document . . . . . . . . . vWho uses MVS System Message information . . . viHow to use message information . . . . . . . viWhere to find more information . . . . . . . vi

Where to find the most current messageinformation . . . . . . . . . . . . . vii

How to send your comments to IBM . . ixIf you have a technical problem. . . . . . . . ix

Summary of changes. . . . . . . . . xiSummary of changes for z/OS MVS SystemMessages, Vol 7 (IEB-IEE) for z/OS Version 2Release 3 . . . . . . . . . . . . . . . xi

Message changes for z/OS MVS SystemMessages, Vol 7 (IEB-IEE) . . . . . . . . . xi

Summary of message changes for z/OS MVSSystem Messages, Vol 7 (IEB-IEE) for Version 2Release 2 (V2R2) and its updates . . . . . . . xiiiSummary of message changes for z/OS MVSSystem Messages, Vol 7 (IEB-IEE) for Version 2Release 1, as updated February 2015 . . . . . . xivSummary of changes for z/OS Version 2 Release 1(V2R1) as updated March 2014 . . . . . . . . xvz/OS Version 2 Release 1 summary of changes . . xv

Chapter 1. IEB messages . . . . . . . 1

Chapter 2. IEC messages . . . . . . 171

Chapter 3. IEC0H messages . . . . . 449

Chapter 4. IEE messages (IEE012A -IEE195I) . . . . . . . . . . . . . . 451

Chapter 5. IEE messages (IEE200I -IEE399I) . . . . . . . . . . . . . . 567



Chapter 8. IEE messages (IEE902I -IEE994E) . . . . . . . . . . . . . 809

Chapter 9. Messages with subchannelset identifiers . . . . . . . . . . . 841

Appendix. Accessibility . . . . . . . 843Accessibility features . . . . . . . . . . . 843Consult assistive technologies . . . . . . . . 843Keyboard navigation of the user interface . . . . 843Dotted decimal syntax diagrams . . . . . . . 843

Notices . . . . . . . . . . . . . . 847Terms and conditions for product documentation 849IBM Online Privacy Statement. . . . . . . . 850Policy for unsupported hardware. . . . . . . 850Minimum supported hardware . . . . . . . 850Trademarks . . . . . . . . . . . . . . 851

Copyright IBM Corp. 1988, 2017 iii

iv z/OS MVS System Messages, Vol 7 (IEB-IEE)

About this document

MVS System Messages primarily describe messages that are issued to the systemoperator at the system console and system messages that are logged. The followingmessages are included:v Operator messages that are issued by the BCP and DFSMS.v Log messages that are issued by the BCP and DFSMS.v Some SYSOUT messages that are issued by the BCP and DFSMS. SYSOUT

messages are issued by utilities that normally run in batch, such as SPZAP.v Batch job messages that are issued by the BCP. Messages that are issued by JES2

or JES3 for batch jobs are in the JES messages documents.

Usually, messages that are issued at interactive terminals (like TSO/E and CICS

terminals) are documented by the specific elements and products that supportthose terminals.

The titles of the MVS System Messages indicate the range of message prefixes inthe documents:v z/OS MVS System Messages, Vol 1 (ABA-AOM)v z/OS MVS System Messages, Vol 2 (ARC-ASA)v z/OS MVS System Messages, Vol 3 (ASB-BPX)v z/OS MVS System Messages, Vol 4 (CBD-DMO)v z/OS MVS System Messages, Vol 5 (EDG-GFS)v z/OS MVS System Messages, Vol 6 (GOS-IEA)v z/OS MVS System Messages, Vol 7 (IEB-IEE)v z/OS MVS System Messages, Vol 8 (IEF-IGD)v z/OS MVS System Messages, Vol 9 (IGF-IWM)v z/OS MVS System Messages, Vol 10 (IXC-IZP)

Some of the other types of message information include the following titles.v z/OS MVS Dump Output Messagesv z/OS MVS System Codesv z/OS and z/VM HCD Messagesv z/OS JES3 Messagesv z/OS TSO/E Messagesv z/OS UNIX System Services Messages and Codes

For a list of message information that is sorted by message prefix, see theIntroduction section in z/OS MVS System Messages, Vol 1 (ABA-AOM).

This information also contains the routing and descriptor codes that IBM assignsto the messages that z/OS components, subsystems, and products issue. Routingand descriptor codes are specified by the ROUTCDE and DESC keywordparameters on WTO and WTOR macros, which are the primary methods thatprograms use to issue messages. The routing code identifies where a message isdisplayed. The descriptor code identifies the significance of the message and thecolor of the message on operator consoles with color.

Copyright IBM Corp. 1988, 2017 v

Who uses MVS System Message informationMVS System Messages are for programmers who receive messages from the system.Usually, these people are system operators, system programmers, and applicationprogrammers who do any of the following tasks.v Initialize the operating system and its subsystems.v Monitor system activity.v Keep the system correctly running.v Diagnose and correct system problems.v Diagnose and correct errors in problem programs.

How to use message informationThe system messages contain descriptions of messages. For details about z/OSmessage formats, prefix by component, descriptions, and more see theIntroduction section in z/OS MVS System Messages, Vol 1 (ABA-AOM).

Where to find more informationThis information explains how z/OS references information in other documentsand on the web.

When possible, this information uses cross-document links that go directly to thetopic in reference using shortened versions of the document title. For completetitles and order numbers of the documents for all products that are part of z/OS,see z/OS Information Roadmap.

To find the complete z/OS library, including the IBM Knowledge Center for z/OS,see the following resources.

z/OS Internet library (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary)IBM Knowledge Center (www.ibm.com/support/knowledgecenter/SSLTBW/welcome)

Many message descriptions refer to the following terms. You need to consult thereference listed below for more information:v Data areas and control blocks: See z/OS MVS Data Areas in the z/OS Internet

library (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary) or IBM Knowledge Center (www.ibm.com/support/knowledgecenter/SSLTBW/welcome).

v Dumps: For examples of ABEND, stand-alone, and SVC dumps and how to readthem, see z/OS MVS Diagnosis: Tools and Service Aids. For examples of componentoutput from dumps and how to read and request it, see z/OS MVS Diagnosis:Reference.

v Identification of a component, subsystem, or product: See the z/OS MVSDiagnosis: Reference to identify the component, subsystem, or product from thename of an IBM module or for a macro. The module prefix and macro tablesgive the program identifier to be used in a PIDS symptom in a search argument.

v System completion and wait state codes: See z/OS MVS System Codes.v Logrec data set error records: For the formatted records, see z/OS MVS

Diagnosis: Reference.

vi z/OS MVS System Messages, Vol 7 (IEB-IEE)

http://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcomehttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcomehttp://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcomehttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcome

v Trace output: For the formats and the meaning of the information in thegeneralized trace facility (GTF) trace, instruction address trace, master trace,system trace, and component trace, see z/OS MVS Diagnosis: Tools and ServiceAids.

v Hardware: Use the appropriate Principles of Operation document for the hardwareyou have installed.

Where to find the most current message informationThe MVS System Messages documents are cumulative. As messages are added tothe system, they are added to the documents. Similarly, when messages arechanged on the system, they are changed in the documents. However, when amessage is deleted from the system (no longer issued), the message is not deletedfrom the document. You can always look in the most recent message informationfor the descriptions of all system messages.

To find the most current edition of a message or document, see the followingresources.

z/OS Internet library (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary)IBM Knowledge Center (www.ibm.com/support/knowledgecenter/SSLTBW/welcome)

About this document vii

http://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcomehttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcome

viii z/OS MVS System Messages, Vol 7 (IEB-IEE)

How to send your comments to IBM

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

Important: If your comment regards a technical question or problem, see insteadIf you have a technical problem.

Submit your feedback by using the appropriate method for your type of commentor question:

Feedback on z/OS functionIf your comment or question is about z/OS itself, submit a request throughthe IBM RFE Community (www.ibm.com/developerworks/rfe/).

Feedback on IBM Knowledge Center functionIf your comment or question is about the IBM Knowledge Centerfunctionality, for example search capabilities or how to arrange the browserview, send a detailed email to IBM Knowledge Center Support [email protected].

Feedback on the z/OS product documentation and contentIf your comment is about the information that is provided in the z/OSproduct documentation library, send a detailed email [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 followinginformation:v Your name, company/university/institution name, and email addressv The following deliverable title and order number: z/OS MVS System

Messages, Vol 7 (IEB-IEE), SA38-0674-30v The section title of the specific information to which your comment

relatesv The text of your comment.

When you send comments to IBM, you grant IBM a nonexclusive right to use ordistribute the comments in any way appropriate without incurring any obligationto you.

IBM or any other organizations use the personal information that you supply tocontact you only about the issues that you submit.

If you have a technical problemIf you have a technical problem or question, do not use the feedback methods thatare provided for sending documentation comments. Instead, take one or more ofthe following actions:v Go to the IBM Support Portal (support.ibm.com).v Contact your IBM service representative.v Call IBM technical support.

Copyright IBM Corp. 1988, 2017 ix

http://www.ibm.com/developerworks/rfe/mailto:[email protected]:[email protected]://support.ibm.com

x z/OS MVS System Messages, Vol 7 (IEB-IEE)

Summary of changes

This information includes terminology, maintenance, and editorial changes.Technical changes or additions to the text and illustrations for the current editionare indicated by a vertical line to the left of the change.

Summary of changes for z/OS MVS System Messages, Vol 7 (IEB-IEE)for z/OS Version 2 Release 3

Message changes for z/OS MVS System Messages, Vol 7(IEB-IEE)

The following messages are new, changed, or no longer issued in V2R3.

New

The following messages are new.IEC359I (form 7 of 7)IEC816IIEE587I for APAR OA50653IEE763I

Changed

The following messages are changed.IEC036I for APAR OA55398IEC120AIEC121DIEC122DIEC123DIEC124DIEC125DIEC126IIEC127DIEC128DIEC129DIEC141IIEC143I for APAR OA52343IEC145IIEC150IIEC161IIEC161I (return code 240) for APAR OA53383IEC359IIEC380IIEC457IIEC459I

Copyright IBM Corp. 1988, 2017 xi

IEE115IIEE174IIEE174I (form 6 of 36) for APAR OA50189IEE174I (form 21 of 36) is merged into IEE174I (form 6 of 35) for APAROA50653IEE174I (form 22 of 36) and is renamed IEE174I (form 21 of 35) for APAROA50653IEE174I (form 23 of 36) and is renamed IEE174I (form 22 of 35) for APAROA50653IEE174I (form 24 of 36) and is renamed IEE174I (form 23 of 35) for APAROA50653IEE174I (form 25 of 36) and is renamed IEE174I (form 24 of 35) for APAROA50653IEE174I (form 26 of 36) and is renamed IEE174I (form 25 of 35) for APAROA50653IEE174I (form 27 of 36) and is renamed IEE174I (form 26 of 35) for APAROA50653IEE174I (form 28 of 36) and is renamed IEE174I (form 27 of 35) for APAROA50653IEE174I (form 29 of 36) and is renamed IEE174I (form 28 of 35) for APAROA50653IEE174I (form 30 of 36) and is renamed IEE174I (form 29 of 35) for APAROA50653IEE174I (form 31 of 36) and is renamed IEE174I (form 30 of 35) for APAROA50653IEE174I (form 32 of 36) and is renamed IEE174I (form 31 of 35) for APAROA50653IEE174I (form 33 of 36) and is renamed IEE174I (form 32 of 35) for APAROA50653IEE174I (form 34 of 36) and is renamed IEE174I (form 33 of 35) for APAROA50653IEE174I (form 35 of 36) and is renamed IEE174I (form 34 of 35) for APAROA50653IEE174I (form 36 of 36) and is renamed IEE174I (form 35 of 35) for APAROA50653IEE186IIEE187IIEE342IIEE457I for APAR OA50189IEE459I for APAR OA54279IEE584I for APAR OA51642 and APAR OA51289IEE586I for APAR OA51642IEE852IIEE979W for APAR OA52828

Deleted

The following messages are no longer issued.IEE114I

xii z/OS MVS System Messages, Vol 7 (IEB-IEE)

IEE115I

Summary of message changes for z/OS MVS System Messages, Vol 7(IEB-IEE) for Version 2 Release 2 (V2R2) and its updates

The following lists indicate the messages that are new, changed, or no longerissued in z/OS V2R2 and its updates. Messages that have been added, updated, orthat are no longer issued in an updated edition of V2R2 are identified by thequarter and year that the message was updated, in parentheses. For example,(4Q2015) indicates that a message was updated in the fourth quarter of 2015.

New

The following messages are new.IEC385S (Changed from IEC385W)IEC386S (Changed from IEC386W)IEC387S (Changed from IEC387W)IEE584I (2Q2016)IEE586I (2Q2016)

Changed

The following messages are changed.IEB311I (4Q2015)IEC027I (1Q2016)IEC030I (1Q2016)IEC031I (1Q2016)IEC032I (1Q2016)IEC036I (1Q2016)IEC104I (1Q2016)IEC130I (1Q2016)IEC142I (1Q2016)IEC143I (1Q2016)IEC161I (1Q2016)IEC190I (1Q2016)IEC205I (1Q2016)IEC353IIEC385S (Changed from IEC385W)IEC386S (Changed from IEC386W)IEC387S (Changed from IEC387W)IEC503IIEC613A (1Q2016)IEE080D (1Q2016)IEE062I (1Q2016)IEE174I (form 17 of 36) (3Q2016)IEE178IIEE256IIEE289I (1Q2016)

Summary of changes xiii

IEE459I (form 1 of 3) (2Q2016)IEE479W (1Q2016)IEE536I (1Q2016)IEE712I (1Q2016)IEE716I (4Q2015)IEE735IIEE836DIEE844W (1Q2016)IEE972I

Deleted

The following messages are no longer issued.IEE859I

Summary of message changes for z/OS MVS System Messages, Vol 7(IEB-IEE) for Version 2 Release 1, as updated February 2015

The following messages are new, changed, or no longer issued for z/OS MVSSystem Messages, Vol 7 (IEB-IEE) in the February 2015 update of z/OS V2R1. Formore information, see z/OS MVS System Messages, Vol 7 (IEB-IEE) .

New

The following messages are new.IEE506IIEE995IIEE996I

Changed

The following messages are changed.IEE075IIEE097IIEE174IIEE174I (form 2 of 36)IEE174I (form 6 of 36)IEE174I (form 17 of 36)IEE176IIEE239IIEE241IIEE247IIEE244DIEE459IIEE496IIEE559IIEE718IIEE772I

xiv z/OS MVS System Messages, Vol 7 (IEB-IEE)

Summary of changes for z/OS Version 2 Release 1 (V2R1) as updatedMarch 2014

The following changes are made for z/OS Version 2 Release 1 (V2R1) as updatedMarch 2014. In this revision, all technical changes for z/OS V2R1 are indicated bya vertical line to the left of the change.

Changed

The following messages are changed for zEDC compression (new reason codes):IEC036IIEC143IIEC214I

The following messages were updated for service:IEE399IIEE459I

z/OS Version 2 Release 1 summary of changesSee the Version 2 Release 1 (V2R1) versions of the following publications for allenhancements related to z/OS V2R1:v z/OS Migrationv z/OS Planning for Installationv z/OS Summary of Message and Interface Changesv z/OS Introduction and Release Guide

Summary of changes xv

xvi z/OS MVS System Messages, Vol 7 (IEB-IEE)

Chapter 1. IEB messages

IEBA01I IEBIMAGE UTILITY COMPLETE. RETURN CODE = return-code

Explanation: The utility has completed processing. The return code indicates the greatest severity of error found inany of the requested operations:

00 Successful completion, operation(s) performed as requested.

04 Operation(s) performed, investigate messages for exceptional circumstances.

08 Operation(s) not performed. Investigate messages.

12 Severe exception. Utility may end.

16 Catastrophic exception. Utility ended.

20 SYSPRINT data set could not be opened. Utility ended.

24 User parameter list incorrect. Utility ended.

In the message text:

return-codeThe return code.

System action: IEBIMAGE processing is ended.

System programmer response: If the error recurs and the program is not in error, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the SYSOUT output, thesource input for the job, and all printed output and output data sets related to the problem.

Programmer response: Examine the return code to determine the degree of successful processing. If the return codeis 08 or greater, the preceding messages must be investigated and resolved and the job rerun.

Source: DFSMSdfp

IEBA02I MEMBER (mem) {ADDED|REPLACED} IN DIRECTORY

Explanation: The specified member has been placed into the library and a directory entry added or replaced in thePDS directory.


mem The member name.

System action: The IEBIMAGE program continues processing the next control statement.

Source: DFSMSdfp

IEBA03I NO SPACE IN DIRECTORY.

Explanation: A STOW macro has been issued but all directory blocks for the data set specified by the SYSUT1 DDstatement have been used.

System action: The IEBIMAGE program continues processing the next control statement, but subsequent writing tothe library data set is inhibited.

System programmer response: If the error recurs and the program is not in error, look at the messages in the joblog for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact theIBM Support Center. Provide the JCL, the SYSOUT output, and the source input for the job.

Programmer response: Using utility programs such as IEBCOPY and IEHPROGM the data set may be recreated,allowing for more directory entries.

Source: DFSMSdfp

Copyright IBM Corp. 1988, 2017 1

IEBA04I PERMANENT I/O ERROR IN [DIRECTORY] devnum, devtyp, ddname, op, errdes, lastskad, accmeth

Explanation: During writing to the specified library an I/O error occurred.


devnum The device number.

devtyp The device type.

ddname The DDNAME specified.

op The operation.

errdes A description of the error.

lastskad The last seek address.

accmeth The access method.


System programmer response: If the error recurs and the program is not in error, look at the messages in the joblog for more information.

Programmer response: Rerun the job.

Source: DFSMSdfp

IEBA05I FCB SPECIFICATION BEYOND RANGE OF FORM.

Explanation: The keywords supplied on the FCB control statement have specified channel controls beyond the lastbyte of the FCB image.

System action: The IEBIMAGE program continues processing the next control statement, but writing to the librarydata set for the current operation is inhibited.


Programmer response: Correct the FCB control statement and rerun the job.

Source: DFSMSdfp

IEBA06I PARAMETERS SPECIFIED IN (LOC) KEYWORD RESULT IN X(FF), AN UNPRINTABLECHARACTER.

Explanation: During processing of a TABLE operation, the LOC keyword contained a parameter group in thefollowing specification (23, 3F, 03). The 3F index into WCGM 03 is specifically reserved to represent anunprintable character. The message does not inhibit the construction of the character arrangement table, but thischaracter will not be printed.



Programmer response: If an unprintable character is desired, specify only the character arrangement table location,that is (LOC=23). To specify a printable character the WCGM or the CGMID reference must be changed and the jobrerun.

Source: DFSMSdfp

IEBA04I IEBA06I

2 z/OS MVS System Messages, Vol 7 (IEB-IEE)

IEBA07I MODULE TOO LONG OR TOO SHORT

Explanation: An INCLUDE statement referenced a module that is too long or too short to be valid. If an FCBmodule is being built, the length field is too large for the virtual storage occupied by the module, or too small todescribe a valid FCB. Maximum size for COPYMOD is 8196 bytes, and for GRAPHIC is 64 segments. For FCB, theLPI keyword specifies lines beyond that specified by the SIZE keyword.



Programmer response: Respecify COPYMOD statements to optimize storage usage. If more than 64 segments areneeded for GRAPHIC, up to four GRAFMODS can be created and their names included into this appropriatecharacter arrangement table. For FCB, SIZE keyword determines maximum number of lines. Respecify the controlcards and rerun the job.

Source: DFSMSdfp

IEBA08I NO MEMBER NAME SPECIFIED.

Explanation: No NAME control statement or no name was specified on the NAME or INCLUDE statement.



Programmer response: Supply the missing 1- to 4-character name and rerun the job.

Source: DFSMSdfp

IEBA09I DUPLICATE MEMBER NAME FOR (mem), MEMBER NOT ADDED.

Explanation: A request was made to add a member to the specified library whose directory currently contains thename of a member equal to that of the name of the member to be added.





Programmer response: Change the name of the member to be added or if the member currently on the library is nolonger needed, specify the replace option (R) on the NAME control statement.

Source: DFSMSdfp

IEBA10I MEMBER (mem) NOT FOUND.

Explanation: While processing the utility control statements, the name specified could not be found on the librarydirectory. If this message precedes message IEBA42I, control card specifications are erroneous; otherwise it is anattention only message.




IEBA07I IEBA10I

Chapter 1. IEB messages 3


Programmer response: Ensure that the name specified is correct and resubmit the job if necessary.

Source: DFSMSdfp

IEBA11I FCB NOT MULTIPLE OF 1/2 INCH.

Explanation: The form length as described by the LPI keyword is not a multiple of one half inch. Any lines notspecified by the LPI keyword default to 6 LPI, up to the length of the form (as specified by the SIZE keyword).



Programmer response: Correct the LPI keyword specifications and rerun the job.

Source: DFSMSdfp

IEBA12I CONTINUATION INVALID.

Explanation: A control statement was found that is not in proper format for a continuation statement. Columns 1through 15 must be blank and the continuation information must start in column 16.



Programmer response: Change either the control statement that indicates continuation (it is non-blank in column72), or ensure that the subsequent control statement is specified properly.

Source: DFSMSdfp

IEBA13I PREVIOUS INCLUDE STATEMENT INVALID FOR THIS OPERATION, IT IS IGNORED.

Explanation: If an INCLUDE control statement precedes a FCB control statement or a print-only request, it isincorrect and is ignored. If multiple INCLUDE statements are present, only the last INCLUDE statement is used.



Programmer response: Remove unnecessary INCLUDE statements and rerun job, if necessary.

Source: DFSMSdfp

IEBA14I PARAMETER(S) INVALID FOR KEYWORD (keywd).

Explanation: Parameters for the indicated keyword have been incorrectly specified. There are too many characters,or too many parameters, or incorrect parameter specification. It may also mean that the number of lines described bythe LPI keyword exceeds the length of the form as described by LINES or SIZE.


keywd The specified keyword.


IEBA11I IEBA14I



Programmer response: Correct the parameter specifications and resubmit the job.

Source: DFSMSdfp

IEBA15I KEYWORD (keywd) INVALID FOR THIS OPERATION.

Explanation: The indicated keyword is not valid for the current operation.





Programmer response: Correct the control statement and resubmit the job.

Source: DFSMSdfp

IEBA16I OPERATION INVALID - op

Explanation: The indicated operation is incorrectly specified, is not in the proper sequence, or is missing a namestatement.


op The operation.



Programmer response: Correct the indicated control statement and rerun the job.

Source: DFSMSdfp

IEBA17I INVALID CONTROL CARD FORMAT.

Explanation: Either the control statement has an incorrect label, or it is a blank card image.




Source: DFSMSdfp

IEBA18I INVALID SEQUENCE FOR INITIAL COPY NUMBER, IN SEGMENT segnum.

Explanation: In an existing module that was either built or modified by other than the IEBIMAGE utility, theindicated segment has an initial copy member that is lower than the previous segment.


segnum The segment number.

IEBA15I IEBA18I




Programmer response: Using the INCLUDE with the DELSEG keyword, delete the appropriate segments.

Source: DFSMSdfp

IEBA19I DATA SET NOT FOUND, DSNAME = dsname

Explanation: The indicated data set could not be found during the issuance of an OPEN macro.


dsname The specified dsname.



Programmer response: Ensure that the DD statement is correctly specified. Rerun the job.

Source: DFSMSdfp

IEBA20I FAILURE DURING OPEN FOR DD = ddname

Explanation: The indicated DDNAME statement was incorrectly specified or not included in the JCL for this jobstep. If the DDNAME=SYSIN, the LRECL of the data set is probably not 80.



Programmer response: Correct the DD statement error and rerun the job. For SYSIN DD, also ensure that the dataset is allocated with LRECL=80.

Source: DFSMSdfp

IEBA21I INSUFFICIENT SPACE IN DATA SET - dsname

Explanation: The indicated data set is full. A D37 ABEND which has been suppressed by the utility has occurred.


dsname The specified dsname.


System programmer response: If the error recurs and the program is not in error, look at the messages in the joblog for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact theIBM Support Center. Provide the JCL, the SYSOUT output, the source input for the job, and all printed output andoutput data sets related to the problem.

Programmer response: Using utility programs such as IEBCOPY and IEHPROGM, the data set may be recreated,allowing for more space.

Source: DFSMSdfp

IEBA19I IEBA21I


IEBA22I INVALID CHARACTER IN CARD COLUMN number

Explanation: An unexpected character was encountered in the indicated column.


number The indicated column number.




Source: DFSMSdfp

IEBA23I DUPLICATE OR MUTUALLY EXCLUSIVE KEYWORD (keywd) FOR OPERATION.

Explanation: The indicated keyword has been specified more than once on this control statement, or conflicts withother keywords or with the operation.





Programmer response: Correct the control statement and rerun the job.

Source: DFSMSdfp

IEBA24I SEGMENT NUMBER (segnum) NONEXISTENT.

Explanation: The indicated segment number is greater than the number of segments in the module referenced.


segnum The indicated segment number.


System programmer response: Run the IEBIMAGE utility to print the applicable member. If the error recurs and theprogram is not in error, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBMSupport Center. Provide the SYSOUT output, the source input for the job, and all printed output and output data setsrelated to the problem.

Programmer response: Correct the segment number specification in the DELSEG or the REF keyword and rerun thejob.

Source: DFSMSdfp

IEBA25I INSUFFICIENT KEYWORD INFORMATION TO COMPLETE OPERATION.

Explanation: Necessary keywords have not been specified, preventing the requested operation from completingsuccessfully.


System programmer response: If the error recurs and the program is not in error, search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the SYSOUT output, the

IEBA22I IEBA25I


source input for the job, and all printed output and output data sets related to the problem.

Programmer response: Specify the necessary keywords and rerun the job.

Source: DFSMSdfp

IEBA26I INVALID USE OF DELIMITER IN KEYWORD (keywd).

Explanation: A comma or a parenthesis has been encountered on a control statement which does not have theproper relationship to other delimiters within the indicated keyword.






Source: DFSMSdfp

IEBA27I NO OPERATION DEFINED.

Explanation: A NAME control statement has been encountered that does not immediately follow an operationcontrol statement (that is, FCB, COPYMOD, CHARSET, TABLE, or GRAPHIC).



Programmer response: Correct the control statement sequence and rerun the job.

Source: DFSMSdfp

IEBA28I INVALID DATA SEQUENCE NUMBER.

Explanation: The sequence number on a data card (column 29 and 30) for a GRAPHIC or CHARSET operation isincorrect. The sequence number must be a 2-digit decimal number, between 1 and 24 (if the device being used is anIBM 3800 Model 1) or between 1 and 40 (if the device being used is an IBM 3800 Model 3 or Model 6).



Programmer response: Correct the sequence number and rerun the job.

Source: DFSMSdfp

IEBA29I MEMBER NAME OR REPLACE OPTION INVALID.

Explanation: The name specified exceeds four characters or the replace option (R) was incorrectly specified.



IEBA26I IEBA29I


Programmer response: Correct the error and rerun the job.

Source: DFSMSdfp

IEBA30I {GRAPHIC|CHARSET} DATA EXCEEDS RANGE OF PITCH IN SEGMENT segnum

Explanation: Data specified on the GRAPHIC or CHARSET data cards requires a character be built which has bitsoutside the allowable limits of the pitch specified in the ASSIGN keyword. In the formatted print of that characterthe erroneous bit(s) will be printed as a dollar sign ($).






Source: DFSMSdfp

IEBA31I NO VALID INPUT DATA FOR {GRAPHIC|CHARSET} ASSIGN.

Explanation: The GRAPHIC or CHARSET operation with an ASSIGN keyword is not followed by a data card whichhas the data SEQ= in column 25 through 28.



Programmer response: Supply appropriate data cards and rerun the job.

Source: DFSMSdfp

IEBA32I SIZE OF FORM IS nn.n INCHES (xxxx.xx MM).

Explanation: The FCB form size is printed as a number in inches and in millimeters (MM). This size was specifiedor defaulted with the SIZE parameter.


nn.n The size of the form in inches.

xxxx.xx The size of the form in millimeters.



Programmer response: None

Source: DFSMSdfp

IEBA33I SEGMENT segnum COPY copynum LINE linenum MAY CREATE A LINE OVERRUN CONDITION IFPREVIOUS LINE IS PRINTED AT {6|8|10|12} LINES PER INCH.

Explanation: The segment with segment number segno, in combination with all the previous segments, may cause aline overrun condition to occur when this copy modification module is used. If the message specifies 12 lines perinch, the segment can be printed at 6, 8, or (for 3800-3) 10 lines per inch. If the message specifies 10 lines per inch,

IEBA30I IEBA33I


the segment can be printed at 6 or 8 lines per inch. If the message specifies 8 lines per inch, the segment can beprinted only at 6 lines per inch.



copynumThe number of the copy in which the line overrun condition may occur.

linenum The line number in that copy.

The corresponding segment in the formatted listing is flagged with the designation NOTE (n). If n is 0 (for3800-3), 2, or 3, it indicates at least one overrun condition for 12, 8, or 6 lines per inch respectively. If n is 1, itindicates at least one overrun condition for 12 lines per inch (for 3800-1), or 10 lines per inch (for 3800-3).



Programmer response: Respecify COPYMOD statements such that each segment in combination with precedingsegments does not create a line overrun condition when the copy modification module is used. The OPTIONstatement with the OVERRUN parameter can be used to suppress this message.

Source: DFSMSdfp

IEBA34I CHARACTERS SPECIFIED IN TEXT KEYWORD RESULT IN HEXADECIMAL (FF).

Explanation: A specification in the TEXT keyword which results in a hexadecimal (FF) is incorrect. FF has beenreserved for use within copy modification text to denote a duplication factor.




Source: DFSMSdfp

IEBA35I UNBALANCED PARENTHESIS IN KEYWORD (keywd).

Explanation: The number of right parentheses does not equal the number of left parentheses in the indicatedkeyword.






Source: DFSMSdfp

IEBA34I IEBA35I


IEBA36I DUPLICATE CHANNEL SPECIFICATION FOR PRINT LINE prtlnnum

Explanation: More than one channel specification has been requested for the same print line (for example, CH1=10,CH2=10).


prtlnnumThe print line number specified.




Source: DFSMSdfp

IEBA37I REFERENCES TO NONEXISTENT CGMID WITHIN TABLE.

Explanation: One or more locations in the character arrangement table reference a CGMID that has not been definedin the trailer portion of the table.




Source: DFSMSdfp

IEBA38I TABLE REFERENCES NO PRINTABLE CHARACTERS.

Explanation: A character arrangement table has been constructed or modified such that the resulting table has all256 locations referencing the non-printable character (FF).




Source: DFSMSdfp

IEBA39I INVALID PARITY IN SEGMENT segnum

Explanation: In a graphic character modification module that was either created or modified by other than theIEBIMAGE utility, the indicated segment was found to have incorrect parity.





IEBA36I IEBA39I


Programmer response: Use SPZAP to correct the error, or rebuild the module using an INCLUDE control statementwith the DELSEG keyword, and a GRAPHIC or CHARSET control statement with the ASSIGN keyword andappropriate data cards.

Source: DFSMSdfp

IEBA40I INCONSISTENT PITCH WITHIN SEGMENT segnum

Explanation: In a graphic character modification module that was either created or modified by other than theIEBIMAGE utility, the indicated segment was found to have inconsistent pitch.





Programmer response: Use SPZAP to correct the error, or rebuild the modules using an INCLUDE control statementwith the DELSEG keyword, and a GRAPHIC or CHARSET control statement with the ASSIGN keyword and theappropriate data cards.

Source: DFSMSdfp

IEBA41I PREVIOUSLY USED {EBCDIC|WCGM} ASSIGNMENT IN SEGMENT segnum

Explanation: A segment was found to have an assignment value equal to that of one previously used in the module.This error does not prohibit completion of the operation. For GRAPHIC operations all segments are built, but onlythe last one will take effect should it be loaded into the printer. For CHARSET operations only the last of theduplicated assignments is built. All previous library character set segments are ignored.





Programmer response: For GRAPHIC operations the unwanted duplicate segments can be deleted by using anINCLUDE control statement with the DELSEG keyword. An assignment value can be changed by using theGRAPHIC control statement with the REF keyword to change the EBCDIC assignment value. For CHARSEToperations the INCLUDE control statement with the DELSEG keyword can be used to delete any unwantedsegments. An assignment value can be inserted by using the CHARSET control statement with the REF or ASSIGNkeywords.

Source: DFSMSdfp

IEBA42I MEMBER NOT ADDED TO LIBRARY, ERROR(S) LISTED.

Explanation: Errors previous to this statement have prevented the utility from updating the library with the modulespecified in the current operation.



Programmer response: Correct the errors and rerun the job.

Source: DFSMSdfp

IEBA40I IEBA42I


IEBA43I IN SEGMENT segnum, {COPY|LINE|TEXT} SPECIFICATION BEYOND RANGE OF MAXIMUMVALUE.

Explanation: One of the following values has been exceeded:

COPY - 256LINE - 133TEXT - 205

The IEBIMAGE utility does not allow number of copies, number of lines, or number of text characters per linespecifications to exceed certain values.

COPYThe number of the copy at which additional printing is to begin, plus the number of copies, cannot exceed256.

LINEThe number of the line at which additional printing is to begin, plus the number of lines, cannot exceed 133.The IEBIMAGE utility allows the sum to be 133, which is valid for a 3800 using International Standards Organization(ISO) paper sizes. If this value is greater than 120 for a 3800 that uses common-use paper sizes, the entry is neverused.

TEXTThe number of the character at which additional printing is to begin, plus the number of characters, cannotexceed 205.






Source: DFSMSdfp

IEBA44I SEQUENCE NUMBER INVALID OR PREVIOUSLY USED.

Explanation: A data card sequence number of less than 1, or one that has been used previously, has beenencountered.



Programmer response: Correct the data card and resubmit the job.

Source: DFSMSdfp

IEBA45I LIBRARY SPACE INCREASED TO nn EXTENTS.

Explanation: After updating the library specified by the SYSUT1 DD statement, it was found that the last recordwas written on a different extent than the previous update. The SYS1.IMAGELIB system data set can have up to 16extents.


nn The number of extents.


System programmer response: If the error recurs and the program is not in error, look at the messages in the job

IEBA43I IEBA45I


log for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact theIBM Support Center. Provide the SYSOUT output and all printed output and output data sets related to the problem.

Programmer response: Programs that have the library open while IEBIMAGE is processing may not be able toaccess new or updated members unless they close and reopen it.

Source: DFSMSdfp

IEBA46I REQUEST TO UPDATE LIBRARY DENIED, DSNAME = dsname.

Explanation: The OPEN macro has caused a message to be sent to the operator requesting an update to a librarywhose expiration has not been exceeded. The operator replied M, denying the request.


dsname The data set name.

System action: IEBIMAGE processing continues with the next control statement but updating of the library data setis inhibited.


Programmer response: Specify a different volume and/or obtain authorization to update the subject data set.

Source: DFSMSdfp

IEBA47I INSUFFICIENT VIRTUAL STORAGE TO PERFORM STOW FUNCTION.

Explanation: A STOW SVC was issued and its function was prohibited due to lack of virtual storage.



Programmer response: Rerun the job. The error may be a temporary one caused by fragmentation of virtual storage.

Source: DFSMSdfp

IEBA48I DUPLICATE TABLE REFERENCE FOR LOCATION (loc).

Explanation: Specification for the same location in a character arrangement table occurred more than once. Eachreference must be unique.


loc The indicated location.




Source: DFSMSdfp

IEBA49I NO CHANNEL 1 CODE HAS BEEN SPECIFIED.

Explanation: The FCB does not contain a channel 1 code. Be careful when using this FCB, because a skip commandwill cause a unit check at the printer if the FCB does not contain the required channel code.


IEBA46I IEBA49I



Source: DFSMSdfp

IEBA50I CLOC PARAMETER NOT SPECIFIED FOR REFERENCED GCM SEGMENT segnum

Explanation: When building a library character set using the REF keyword of the CHARSET operation, no characterlocation (CLOC) assignment was specified for the graphic character module (GCM).





Programmer response: Specify a WCGM location in the second parameter of the REF keyword for the CHARSEToperation. All library character set segments require a WCGM location assignment between 00-3F.

Source: DFSMSdfp

IEBA51I LIBRARY NOT UPDATED: MODULE CONTAINS NO DATA

Explanation: The module being created contains no data. This may have been caused by a DELSEG parameter onan INCLUDE statement which deleted all the segments of the module.




Source: DFSMSdfp

IEBA52I VALUE OF LINES CONTRADICTS VALUE OF SIZE

Explanation: When building an FCB module for the 3800, 3262 model 5, or 4248 printer, the specifications for theLPI, LINES, and SIZE parameters on the FCB statement were conflicting.



Programmer response: Respecify the FCB statement with complementary values for the LINES, SIZE, and LPIparameters. See the IEBIMAGE chapter in z/OS DFSMSdfp Utilities for the default value of each parameter.

Source: DFSMSdfp

IEB001I {SYSUT1|SYSUT2|SYSIN} NOT OPENED

Explanation: The SYSUT1, SYSUT2, or SYSIN data set, as indicated in the message text, could not be opened. Eitherthe DD statement defining the data set was not included in the input stream, or a DCB parameter for the data setwas incorrect.

System action: The job step is ended. The return code is 8.

IEBA50I IEB001I


System programmer response: If the error recurs and the program is not in error, look at the messages in the joblog for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact theIBM Support Center. Provide the JCL and all printed output and output data sets related to the problem.

Programmer response: Probable user error. Ensure that a DD statement for SYSUT1, SYSUT2, and SYSIN is includedin the input stream, and that the parameters on the DD statements are correct (particularly that the block sizespecification is a multiple of 80). Resubmit the job.

Source: DFSMSdfp

IEB008I INVALID NAME FIELD

Explanation: The name field is incorrect in the EDIT statement preceding this message. Possibly, the name fieldconsists of more than 8 characters or contains an incorrect character.

System action: Processing continues with the next EDIT statement. The return code is 4.


Programmer response: Probable user error. Correct the name field on the preceding statement. Resubmit the job toprocess either the entire input stream or the unedited portion of the input stream.

Source: DFSMSdfp

IEB009I INVALID STATEMENT SYNTAX

Explanation: The EDIT statement preceding this message is coded incorrectly.



Programmer response: Probable user error. Correct the preceding statement. Resubmit the job to process either theentire input stream or the unedited portion of the input stream.

Source: DFSMSdfp

IEB010I INVALID OPERATION CODE

Explanation: The preceding statement is not an EDIT utility control statement. Possibly, EDIT is misspelled.



Programmer response: Probable user error. Correct the operation on the preceding control statement to EDIT.Resubmit the job to process either the entire input stream or the unedited portion of the input stream.

Source: DFSMSdfp

IEB011I INVALID OPERAND

Explanation: The operand is incorrect in the EDIT statement preceding this message. Possibly, a parameter ismisspelled or incompatible parameters are specified.



Programmer response: Probable user error. Correct the operands on the preceding control statement. Resubmit the

IEB008I IEB011I


job to process either the entire input stream or the unedited portion of the input stream.

Source: DFSMSdfp

IEB014I INVALID DELIMITER

Explanation: A delimiter is incorrect in the EDIT statement preceding this message.



Programmer response: Correct the delimiters on the preceding control statement. Resubmit the job to process eitherthe entire input stream or the unedited portion of the input stream.

Source: DFSMSdfp

IEB020I INVALID CONTINUATION CARD

Explanation: The continuation does not begin at column 16 in the statement preceding this message.



Programmer response: Probable user error. Begin the continuation statement in column 16 or, if no continuation isdesired, correct the statement that indicated a continuation. Resubmit the job to process either the entire input streamor the unedited portion of the input stream.

Source: DFSMSdfp

IEB021I INVALID CHARACTER

Explanation: A character is incorrect in the EDIT statement preceding this message.



Programmer response: Probable user error. Correct the error in the control statement. Resubmit the job to processeither the entire input stream or the unedited portion of the input stream.

Source: DFSMSdfp

IEB022I JOB NAME NOT FOUND BEFORE END OF FILE

Explanation: Either no JOB statement was found in the input data set, or the specified job could not be found.



Programmer response: Probable user error. Insert the missing JOB statement into the input stream or correct thecontrol information on the associated EDIT statement. Resubmit the job.

Source: DFSMSdfp

IEB014I IEB022I


IEB023I sss STEP COULD NOT BE FOUND

Explanation: The step could not be found in the input data set. Possibly, the step name was misspelled.


sss The indicated step.



Programmer response: Probable user error. Insert the missing step into the input stream or correct the controlinformation on the associated EDIT statement. Resubmit the job to process either the entire input stream or theunedited portion of the input stream.

Source: DFSMSdfp

IEB024I high WAS HIGHEST SEVERITY CODE

Explanation: The return code was the highest return code generated during processing of the IEBEDIT program.


high The highest return code generated.


Programmer response: For other than successful job completion (severity code= 0), resubmit the job to processeither the entire input stream or the unedited portion of the input stream.

Source: DFSMSdfp

IEB027I I/O ERROR dsname, jjj, sss, ddd, devtyp, ddname, op, err, xxxx, acc

Explanation: A permanent input/output error occurred while processing on the device.

In the message text, the error analysis information provided by the SYNADAF data management macro issued by theSYNAD routine was:

dsnameData set name.

jjjJob name.

sssStep name.

dddDevice number of the device.

devtypDevice type.

ddnameData definition name.

op Operation attempted.

errError description.

xxxxLast seek address or block count.

IEB023I IEB027I


accAccess method.

System action: The program is ended. The return code is 8.


Programmer response: Correct the error condition indicated in the message text according to the error analysisinformation provided by the SYNADAF data management macro instruction. Resubmit the job.

Source: DFSMSdfp

IEB030I {SYSUT1|SYSIN} BLKSIZE INVALID

Explanation: The block size of the SYSUT1 or SYSIN data set, as indicated in the message text, is not a multiple of80 bytes.

System action: The program is ended. The return code is 8.


Programmer response: Probable user error. Correct the block size of the indicated data set and resubmit the job.

Source: DFSMSdfp

IEB032I SYSUT2 BLKSIZE INVALID - SYSUT1 ASSUMED

Explanation: The block size of the SYSUT2 data set is not a multiple of 80 bytes.

System action: The SYSUT1 block size attributes are assumed for the SYSUT2 data set. Processing continues. Thereturn code is 4.


Programmer response: Probable user error. If the block size for SYSUT1 is undesirable for SYSUT2, correct the blocksize for SYSUT2 and resubmit the job; otherwise, disregard this message.

Source: DFSMSdfp

IEB033I STATEMENT NOT PROCESSED EOF ON SYSUT1

Explanation: An end-of-file condition was encountered on the SYSUT1 data set. The preceding EDIT statement wasnot processed.



Programmer response: Probable user error. Restructure the EDIT statements if the edited output is not as desiredand resubmit the job; otherwise, disregard the unprocessed EDIT statements.

Source: DFSMSdfp

IEB034I STEPNAME REQUIRED WITH TYPE= {INCLUDE|EXCLUDE}

Explanation: No step name was specified with a TYPE=INCLUDE or TYPE=EXCLUDE operation, as indicated inthe message text.


System programmer response: If the error recurs and the program is not in error, look at the messages in the job

IEB030I IEB034I


log for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact theIBM Support Center. Provide the JCL and all printed output and output data sets related to the problem.

Programmer response: Probable user error. Correct the condition indicated in the message text. Resubmit the job toprocess either the entire input stream or the unedited portion of the input stream.

Source: DFSMSdfp

IEB100I I/O ERROR READING MEMBER memname

Explanation: An I/O error was encountered while reading the specified member. Message IEB139I, which givesdetailed information regarding the location of the error record, is always issued previous to this message.


memnameThe specified member name.

System action: The next COPY control statement is sought unless a data check occupies the key or data portion. Inthis case, the error is ignored and data is copied as it came into main storage. If the copy is performed, the returncode is 4; if not, the return code is 8.


Programmer response: Depending on the type of error, rerun the COPY operation with the data set in errorallocated:

v At a different physical location on the volume.v On a different device.v On a different channel.

If the error is on an input data set, it may be necessary to re-create the data set.

Source: DFSMSdfp

IEB101I I/O ERROR WRITING MEMBER DATA AT TTR=ttr [-DURING READ BACK CHECK]

Explanation: An I/O error occurred while copying member data to the output data set. The TTR of the record inerror relative to the beginning of the data set is given. The [ ] part of the message is only given if the error occurredduring a read back check.


ttr The logical disk address.

System action: If the error was encountered during read back check and involved a data check in key or data only,the error is ignored, and the return code is 4. Otherwise, the next COPY control statement is sought, and the returncode is 8.


Programmer response: Depending on the type of error, rerun the COPY operation with the data set in errorallocated:

v At a different physical location on the volume.v On a different device.v On a different channel.

Source: DFSMSdfp

Routing code: Note 11

Descriptor code: -

IEB100I IEB101I


IEB102I MEMBER member NOT {COPIED | LOADED | UNLOADED} DUE TO I/O ERROR

Explanation: An I/O error on the SYSUT3 work file has made processing of the member impossible. If ********replaces the member name in the above message, the error was found reading from SYSUT3.


member The name of the member.

The severity is 8.

System action: Processing continues with the next member to be copied.

System programmer response: Use the IEHLIST utility to investigate the output directory and determine whichmember(s) were not copied.

Programmer response: Retry the failing operation, and either:

v Remove the SYSUT3 DD statement and increase the work area size as previously indicated in previously messageIEB1051I.

v Use a different SYSUT3 data set. Place the SYSUT3 data set on a different physical location on the volume, on adifferent device, or on a different channel.

Source: Data Facility Product (DFP)


Descriptor code: -

IEB103I MEMBERS member THRU END OF DATASET ARE NOT ACCESSIBLE DUE TO I/O ERROR

Explanation: Due to an I/O error while updating the output data set's directory, members starting from the namedmember, member, through the end of the data set (in alphameric order) have become inaccessible.


member The name of the member.

The severity is 12.

System action: The operation is ended and the next control statement is sought.

System programmer response: Verify that the output data set directory is large enough. If the error recurs and theprogram is not in error, look at the messages in the job log for more information. Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the JCL and all printedoutput and output data sets related to the problem.

Programmer response: Retry the failing operation. Use a different output data set. Place the data set on a differentphysical location on the volume, on a different device, or on a different channel.


Routing code: 11

Descriptor code: 7

IEB104I INVALID COMMAND OR KEYWORD

Explanation: A command or keyword on the control statement just listed is misspelled or is incorrect for theIEBCOPY program.

The severity is 8.



Programmer response: Correct the control statement.

IEB102I IEB104I




Descriptor code: -

IEB105I PARAMETER INVALID

Explanation: A parameter on the control statement just listed is too long or contains an incorrect character.

The severity is 8.






Descriptor code: -

IEB106I UNEQUAL PARENTHESIS

Explanation: The statement just listed has an unbalanced number of parentheses.

The severity is 8.






Descriptor code: -

IEB107I INVALID CONTINUATION

Explanation: The control statement just listed is incorrect.

(1) Parameters may have ended with a comma (which implies continuation), but the continuation column (72) wasblank.

(2) An attempt may have been made to continue a statement from within a rename/replace specification withinnested parentheses. This is incorrect.

The severity is 8.






Descriptor code: -

IEB105I IEB107I


IEB108I MEMBER WITHOUT SELECT OR EXCLUDE

Explanation: A control statement containing a MEMBER= operand has been encountered. The operand can not beassociated with a previous SELECT or EXCLUDE statement. The control statements are out of order or a SELECT orEXCLUDE statement is missing.

The severity is 8.



Programmer response: Place each MEMBER= following a SELECT or EXCLUDE statement or MEMBER= operand.

Source: Data Facility Pro

z/os mvs system messages, vol 7 (ieb-iee) - ibm.com · vi z/os mvs system messages, v ol 7...

Documents