The DATAID specified on the BROWSE service has not been initialized using LMINIT.

An invalid combination of parameters was specified on the BROWSE service. MEMBER or DATAID cannot be used with DATASET. VOLUME or PASSWORD cannot be used with DATAID.

An error occurred opening the partitioned data set for input.

An I/O error occurred while reading the partitioned data set directory.

A quotation mark was found indicating the beginning of a quoted string but no matching quotation mark was found to indicate the end of the string.

There is insufficient virtual storage to read the entire data set into storage. Browse will continue, displaying as much of the data as will fit into virtual storage.

This is an informational message.

An I/O error, insufficient virtual storage to process the BLDL, or other problems were encountered processing a BLDL.

This is an informational message.

You entered something that is not a valid command for BROWSE.

An unexpected return code was received from module ISRCBR.

The partitioned data set directory has an incorrect blocksize.

The LOCATE command was entered with no parameter.

The LOCATE command was entered with an invalid parameter. A valid parameter is either a previously defined label or a relative line number. The maximum length of the parameter is 8 characters.

The LOCATE command was entered with a label that has not been defined.

The LOCATE command was entered with a label that is greater than 8 characters long.

This is an informational message.

This is an informational message.

This is an informational message.

The panel specified for use to display the data does not exist or is unusable.

You entered the FIND command with no character string to find.

The FIND command has an unrecognizable keyword parameter. You may have entered a FIND command with quotes that do not correctly delimit the string that you want to find and BROWSE is attempting to interpret the remainder of the string as a keyword.

This is an informational message.

The FIND command was entered followed by two or more words (strings of characters delimited by blanks) that are not recognized keywords of FIND. To find these words, you must enclose them in single quotation marks to indicate that they are a single string.

This is an informational message.

This is an informational message.

This is an informational message.

An I/O error occurred reading the first record of the data set.

There is insufficient virtual storage for BROWSE to continue processing.

The record format or LRECL of the data set you are browsing is not fixed 80. Only fixed 80 data sets can be processed by the SUBMIT command.

This is an informational message.

The data set that you are attempting to Browse or Edit has data that appears to be packed but is not in the format that is valid for ISPF packed data. The data set may be corrupted.

This is an informational message.

This is an informational message.

This is an informational message.

Your installation has indicated in the configuration table that the Browse SUBMIT command should be disabled.

The Browse SUBMIT command is not allowed if the member being browsed has been modified by another user since the start of the browse session.

Your installation has indicated in the configuration table that the View SUBMIT command should be disabled.

This is an informational message.

The FIND string must be less than or equal to 40 characters in length.

The FIND string cannot be a null string.

The value entered is invalid for P'xxx' is invalid as a picture string.

A string of characters was entered that must be enclosed in single quotation marks to specify it as a string to be found.

Two mutually exclusive keywords were entered.

The string that was entered to be found is longer than the LRECL of the data set or will not fit between the columns specified.

The find of non EBCDIC strings is restricted to character finds.

More than two numbers were entered as part of a FIND command. Only two numbers (left and right bounds) are allowed as parameters for the FIND command.

The left boundary used in the FIND command cannot exceed the record length (LRECL) of the data set.

The boundary parameters of the FIND command must be specified with the left boundary first and the left boundary must be smaller than the right boundary.

The number of records in the data set extends past the limit currently supported by Browse. Any data beyond this point will not be displayed.

A character string must be entered as a parameter to the FIND command.

A hex string entered as a parameter to the FIND command must have an even number of digits.

No occurrence of the FIND string was found within the boundaries specified on the FIND command.

Only hex digits (0-9, A-F) are valid when specifying a hex FIND string (x'nnnn').

No occurrence of the FIND string was found from the point of the beginning of the search to the beginning of the data.

No occurrence of the FIND string was found from the point of the beginning of the search to the end of the data.

An I/O error occurred while reading data to process the FIND command.

An I/O error occurred while reading data to process the BROWSE command.

ISPF was unable to obtain storage for the STAE macro. Storage subpool 0 is full.

ISPF requires a member name that consists of alphanumeric characters with the first character being alpha.

Member names cannot be greater than 8 characters in length.

Sequential data sets do not contain members.

Recursive BROWSE is not allowed when browsing the ISPF log data set.

YES and NO are the only valid entries for mixed mode.

The format name entered contains invalid characters. Format names must be alphanumeric with the first character alpha.

Too many parameters or an invalid parameter was entered.

The number of records in the data set extends past the limit currently supported by Browse. Any further instances of the search string past this point will not be located or displayed.

No occurrence of the FIND string was found within the boundaries specified on the FIND command. The number of records in the data set extends past the limit currently supported by Browse. Any further instances of the search string past this point will not be located or displayed.

No occurrence of the FIND string was found from the point of the beginning of the search to the end of the data. The number of records in the data set extends past the limit currently supported by Browse. Any further instances of the search string past this point will not be located or displayed.

Too many parameters were entered for the command.

An invalid parameter was entered for this command.

The parameters entered were inconsistent or conflicting.

The "character" parameter of the DISPLAY command can only be one character in length.

For the first format the DISPLAY command accepts parameters of only a single character (the character for non-displayable codes) and CC or NOCC to designate whether or not to show carriage control characters. For the second format the DISPLAY command accepts parameters of CCSID and a number, LINE and 1 or 2 numbers, and COLS and 1 or 2 numbers in where CCSID, LINE and COLS may be specified in any order. Also CCSID and the following number may be replaced by one of the acronyms UTF8, UTF16, UTF32, UCS2, ASCII, USASCII, EBCDIC or UNICODE. At least the CCSID and a number or a valid acronym must be provided.

The DISPLAY command accepts parameters of only a single character (the character for non-displayable codes) and CC or NOCC to designate whether or not to show carriage control characters. You must enter at least one parameter.

An error prevented freeing the allocation for the data set being browsed. This data set may still be allocated to your user ID. The allocation will be freed when you log off.

The DISPLAY command accepts parameters of only a single character (the character for non-displayable codes) and CC or NOCC to designate whether or not to show carriage control characters. You must enter at least one parameter.

The DISPLAY command was used to specify that some of the data needs to be converted, but MVS™ was unable to convert some of the data specified. The return and reason codes are documented in Support for Unicode : Using Conversion Services Appendix D

MVS Conversion Services needs to be configured for the CCSIDS involved using search technique ER in order for the conversion to be done. Refer to Support for Unicode : Using Conversion Services, topic 3.

The user has used the DISPLAY command to specify that some of the data shown on the screen was stored in a different CCSID and requiring conversion prior to display.

MVS Conversion Services needs to be configured for the CCSIDS involved using search technique ER in order for the conversion to be done. Refer to Support for Unicode : Using Conversion Services, topic 3.

The DISPLAY command is rejected because the terminal has not provided character set information to ISPF.

The command routine used by your dialog does not support BROWSE as a command.

The data set selected for browsing has an unsupported record format. You cannot browse this data set.

The data set selected for browsing has a record length greater than 32 760. You cannot browse this data set.

The data set you are attempting to BROWSE contains no data.

An unexpected return code was received from ISRCBR or from a dialog supplied routine.

The BRIF service does not allow the use of a member name.

A return code 20 was received from ISRCBR or a dialog supplied routine.

Browse does not handle packed multivolume data sets.

When not enough storage is available to edit or view a data set, browse is automatically substituted. Data was browsed successfully.

When not enough storage is available to edit or view a data set, browse is automatically substituted. Data was not browsed successfully.

A second ISPF session may not be started while an ISPF session is active.

A TSO command is required as input on the TSO COMMAND PROCESSOR panel.

It is invalid to specify TSO without following it with a valid TSO command.

Commands containing the ISPF NONDISPL keyword cannot be executed from option 6.

The command passed to ISRCINVC is not BROWSE, EDIT, or VIEW.

This is an informational message.

The data set name parameter exceeds 44 characters.

The member name parameter embedded within the data set name exceeds 8 characters.

This is an informational message.

This is an informational message.

The parameter passed to ISRCPREC is not EDIT or VIEW.

This is an informational message.

This is an informational message.

An invalid INTENS value has been entered.

An invalid COLOR has been entered.

An invalid HILITE has been entered.

The user attempted to select a choice that is unavailable.

This is an informational message. The shared personal list was not found in library ISPTLIB. Referral list will default to user profile data set.

This is an informational message.

An invalid command was entered for this function.

There is no reference list active for this user.

This is an informational message. Personal list was updated successfully with the most recent Reference List entry.

A data set was specified that did not both start and end with an apostrophe.

When specifying a data set and member, the member name must be 1 to 8 characters in length, and must be contained within parentheses. For example:

'USER1.PRIVATE.SOURCE(MEMBER1)'

An MVS data set name uses periods to separate its qualifiers, but it cannot start or end with a period.

A Reflist data set entry was selected, but the entry does not contain a data set name.

The Reflist library entry was selected, but the entry does not contain either a Project, Group, or Type.

The PDF Alternate Dialog processor (ISRALTDI) detected an invalid input parameter.

The PDF Alternate Dialog Processor was invoked specifying panels aaaaaaaa and bbbbbbbb as the primary and secondary panels to be used, but neither panel could be found in the ISPPLIB concatenation.

The PDF Alternate Dialog Processor was invoked specifying that alternate panel aaaaaaaa was to be used, but the panel could not be found in the ISPPLIB concatenation.

The PDF Alternate Dialog processor detected a loop in the display of input panel aaaaaaaa, and stopped after 120 calls to the ISPF DISPLAY service. The panel may be forcing non-display mode by having .RESP=ENTER coded in its )INIT section.

PDF received a return code of aaaa from the LOCATE macro.

The PDF Data Set List utility could not get an exclusive ENQ on the target data set for the SAVE command (userid.list-id.DATASETS) because you are currently using it.

The PDF SVC99 interface module (ISRSVCBD) was invoked with an invalid DAIR request code of aaaa.

PDF attempted to allocate a data set to ddname aaaaaaaa, but the ddname was already allocated.

The data set being moved/copied to could not be allocated like the data set being moved/copied from.

The COMPARE command was entered in the editor but both the file being edited and the data set or member it is being compared to are empty or they have no data to be used for the comparison after filtering is completed. The input filtering is defined by the panel which is displayed when the COMPARE command is entered without any operands.

PDF received a return code 4, error code X'1708'from SVC 99 indicating that the data set aaa(44) specified does not exist.

PDF received a return code 4, error code X'4704'from SVC 99 indicating that the data set aaa(44). specified for creation already exists.

A valid volume serial has not been entered.

PDF received a return code 4, error code X'5708'from SVC 99 indicating that a return code 8 was received from the CATALOG macro during processing of data set aaa(44).

PDF received a return code 4, error code X'0420'from SVC 99 indicating that the data you are trying to process is currently open by you or another user.

PDF received a return code 4, error code X'021C'from SVC 99 indicating that the unit name specified (aaaaaaaa) is not defined to your MVS system.

There is an error in obtaining the data set volume that was entered. The volume entered was not mounted, the device table was not found, the device table was empty or the UCB for the volume could not be found.

The data set specified as input to a PDF function or service resides on TAPE, not on DASD. PDF does not support the processing of TAPE data sets.

PDF received an SVC 99 return code/error code combination for which there is no specific PDF message. Entering the HELP command when this message is displayed will provide a tutorial panel with the error messages generated by the system, as well as the SVC 99 return code, error code, and information code.

This is an informational message.

PDF received a return code 12 or 16 from the LOCATE macro, indicating a problem with the index or generation data group specified (aaa(44)).

PDF received a return code 20 from the LOCATE macro indicating the data set name specified (aaa(44)) was syntactically incorrect.

PDF received a return code 8 from the LOCATE macro indicating the data set specified was not found in the catalog.

PDF received a nonzero return code when attempting to uncatalog a data set (aaa(44)) during a data set deletion request.

PDF received a return code 4, error code X'4714'from SVC 99 indicating that there is insufficient space for the data set specified (aaa(44)) on the volume selected by the system.

The member specified is being updated by you on another logical screen or by another user.

PDF received a return code 8 from the OBTAIN macro, indicating that data set aaa(44) does not exist on volume bbbbbb.

PDF received a return code 4, error code X'020C'or X'0210'from SVC 99 indicating data set aaa(44) is currently allocated to another job or user and is, therefore, unavailable to satisfy your request.

PDF received a return code 4, error code X'4708'(return code 8 from DADSM allocate) indicating that the volume table of contents for volume aaaaaa is full; therefore, the entry needed to satisfy your request cannot be added.

PDF received a return code 4, error code X'4714'(return code 20 from DADSM allocate) indicating that volume aaaaaa does not have sufficient space available to satisfy your create request for data set bbb(44).

PDF received a return code 4, error code X'020C'or X'0210'from SVC 99 indicating data set aaa(44) is currently allocated to another job or user and is, therefore, unavailable to satisfy your request.

Someone (you or another user) is using the data set specified as the target data set in a MOVE, COPY, CREATE, or REPLACE command.

The only valid values for the EXDATE parameter of LMDDISP are YES or NO.

The only valid values for the REFLIST parameter of LMDDISP are YES or NO.

Parameters were entered on the UNDO edit primary command. The UNDO command does not accept any parameters.

The UNDO command was issued while there were pending line commands. The UNDO command cannot proceed because it is unclear exactly what is to be undone.

The UNDO command was issued while there were changes in the data area that the editor has not yet processed. The UNDO command cannot proceed because it is unclear exactly what is to be undone.

The UNDO command is not available because you do not have Edit Recovery turned on and your site has not installed the storage recovery function.

This is an informational message. Either no changes have been made to the data since the beginning of the session or since the data was last saved, or all of the changes have already been undone.

The UNDO function is not available because Edit Recovery has been suspended.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

A save-as list name already exists as a current list.

The currently displayed list is not permanent until a save action is performed.

This is an informational message.

This is an informational message.

An error was encountered while saving a personal data set list. Contact IBM service.

A choice was selected that does not contain a data set entry.

Multiple lists were selected by the user.

A list that is active cannot be deleted.

This is an informational message. A save action has been completed successfully.

An invalid primary command/action was detected.

This message is self explanatory.

The NRETRIEV command was entered but the current library reference list contains no entries. The ISPF library names on the panel were not changed.

The NRETRIEV command was used to retrieve a data set name, workstation file name, or data set name level and either the current personal data set list is empty, or NRETRIEV verification is enabled and none of the data sets in the list exist. For data set list name levels, this message may be shown if all of the entries in the personal data set list are determined to be workstation file names. NRETRIEV verification is not used for the data set list utility (data set name levels), but work station file names are not retrieved to the data set list entry panel.

The NRETRIEV command retrieved a library name from the personal library list named aaaaaaaa.. If you want to use a different personal list, use the REFOPEND command and open the personal list which you would like the NRETRIEV command to use when retrieving library names.

The NRETRIEV command retrieved a data set name from the personal data set list named aaaaaaaa.. If you want to use a different personal list, use the REFOPEND command and open the personal list which you would like the NRETRIEV command to use when retrieving data set names.

This message is self explanatory.

This is an informational message.

This is an informational message.

This is an informational message.

The tables used for ISPF reference lists could not be created or opened when ISPF was started. One of the tables may be damaged. The table names are ISRPLIST and ISRLLIST. To determine which table is corrupted, rename each table individually and restart ISPF. When a table is deleted, ISPF will recreate it when ISPF is started.

This message is self explanatory.

The pathname for a z/OS® UNIX file or directory was selected from the list but the panel to which the pathname will be returned does not support the processing of z/OS UNIX files or directories.

The personal data set list name specified with the UDLIST command was not found in the personal data set list table ISRPLIST.

The UDLIST action has completed successfully.

The UDLIST action has completed successfully.

This is an informational message. Personal list was updated successfully with the pathname for the selected file or directory.

The profile name entered is not a valid data set group name.

Your system programmer has disabled the View function through the ISPF Configuration table.

You have typed an invalid hex character into the hex portion of the edit session display.

This message is self-explanatory.

This message is self-explanatory.

You are in text entry mode. You may type text without regard to end of line considerations. Press enter to return to normal edit mode.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message.

The member the user is trying to create already exists in the TO library.

An I/O error was encountered during a move operation. The FROM member was not deleted.

The FROM member was not deleted. MOVE will not delete the FROM member unless it is the first library in the concatenation.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message. Data saved from the EDIF session.

This is an informational message. The requested MOVE or COPY action was completed successfully.

AUTOSAVE mode has been turned to AUTOSAVE OFF PROMPT.

WARNING: A member has been created in the first library in the ISPF library concatenation that has the same name as a member in one of the other groups in the concatenation. The data in the members is NOT necessarily the same.

This message is self explanatory.

In order to write out data, PDF edit attempted to issue a RESERVE on a volume that already had a RESERVE issued against it.

This is an informational message.

The MASK and TABS lines together are longer than the record length of the recovery file.

At least one data line is too large to save in the recovery file.

The ISPF editor only supports data lengths from 1 to 32 760 for fixed length data sets (Record format F or FB) and from 1 to 32 756 for variable length data sets (Record format V or VB) inclusive.

This is an informational message. A USER_STATE edit macro command was issued but the combined length of the TABS and MASK lines is too large to save so they have been truncated.

SUBMIT processing ended abnormally.

The temporary control file used to contain the submit job could not be allocated.

An I/O error was encountered while writing to the temporary control data set.

This is an informational message. The temporary JCL data set was empty.

This message is self explanatory.

The left bound entered was invalid. A valid left boundary is usually 1, 7, or 9 depending on the type of sequence numbering in effect and the record format of the data set being edited.

The right bound entered was invalid.

The data entered into the number field is ignored.

The data entered outside the record field is ignored.

An undefined label was used.

An incomplete block command was found.

aaaaaaaa is not a valid line command.

A number was found with the aaaaaaaa line command.

The aaaaaaaa line command entered is not valid on the line where it was entered.

The aaaaaaaa line command conflicts with the bbbbbbbb range specification for the CREATE/REPLACE macro command.

The aaaaaaaa line command is within the range of the bbbbbbbb line command.

Both of the edit aaaaaaaa and bbbbbbbb line commands require a destination command. They cannot be used simultaneously.

The aaaaaaaa command conflicts with the bbbbbbbb line command.

Two destination line commands have been specified.

The aaaaaaaa line command is within the range of the bbbbbbbb line command.

A TE line command was issued along with another line command, such as Dn. The number of lines affected by the second line command overlapped the text entry area.

A C, CC, M, or MM line command was entered without a destination (A, B, or O) line command or a CREATE or REPLACE primary command.

An A or B destination line command was entered without a corresponding MOVE/COPY line or primary command.

The requested data shift was not completed.

Text entry was begun (that is, a TE line command was issued), but one half of a block command (such as CC) was entered while the TE was in effect.

An O destination line command was entered without a corresponding MOVE/COPY line command.

A CREATE or REPLACE command was entered with no MOVE/COPY line command(s) or label range.

A pair of block line commands that allow numbers (such as '))n') was entered with different numbers modifying each member of the pair.

While in Edit, a CREATE command was issued. The target data set indicated on panel ISRECRA1 was a sequential data set. The target data set for a CREATE must be a PDS or a PDSE. If the target data set is intended to be sequential, Replace must be used instead.

Someone (you or another user) is using the data set specified as the target data set in a MOVE, COPY, CREATE, or REPLACE command.

An end quotation mark is missing at the end of the string.

Too many parameters were entered for the LOCATE primary command.

This is an informational message. The line was not located.

The relative line number specified for the LOCATE macro command must be a number with 6 digits or fewer.

The LOCATE command is expecting a parameter.

The line number specified for the LOCATE primary command must be a number with 8 digits or fewer.

An invalid parameter was specified for the LOCATE command.

The COBOL line number specified for the LOCATE primary command must be a number with 6 digits or fewer.

The TF line command requires more storage than is currently available.

This is an informational message.

The macro name aaaaaaaa specified in the DEFINE primary command was not found.

The command name aaaaaaaa specified in the DEFINE primary command is not a valid edit command.

Too many parameters are specified for the SCAN macro command.

An invalid parameter is specified for the SCAN macro command.

Inconsistent parameters are specified for the SCAN macro command.

An invalid parameter is specified for the SCAN macro command.

Destination for the MOVE or COPY command is missing.

Initial or recovery macro aaaaaaaa could not be executed because it does not exist.

An internal error has occurred in the ESTAE macro during the SUBMIT command.

The END command was invoked with too many parameters.

This message is self explanatory.

This message is self explanatory.

A non-blank character(s) was found in the overlay lines. The MOVE operation was changed to COPY so that the source line would not be deleted.

A non-blank character(s) was found in the overlay lines. The MOVE operation was changed to COPY so that the source lines would not be deleted.

Data outside the bounds was found in the move lines. The MOVE operation was changed to COPY so that the source line would not be deleted.

Data outside the bounds was found in the lines to be moved. The MOVE operation was changed to COPY so that the source lines would not be deleted.

There were more lines to be copied than lines to be overlaid. Extra lines were ignored.

There were more lines to be moved than lines to be overlaid. Extra lines were ignored.

This is an informational message.

This is an informational message.

The member name aaaaaaaa specified is not valid for partitioned data sets.

The member name aaaaaaaa specified is not valid for workstation edit.

The data set specified is being updated by another user or by you on another logical screen. Enter HELP for a list of users using the data set.

A severe error has occurred.

The member specified is being updated by you on another logical screen or by another user. Enter HELP for a list of users using the member.

The volume serial is only allowed along with a data set name in the Other data set name field.

There was an error in processing the edit recovery table. The edit recovery table may be corrupted.

A recovery file from an old release of PDF cannot be processed.

A severe internal error has occurred.

A severe internal error has occurred. An unexpected return code from VDEFINE service has been received by ISREDS.

Directory block size exceeding 256 bytes is not supported. The data set may be corrupted.

A severe internal error has occurred. An unexpected return code from the display service has been received.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

The user pressed a function key defined as RFIND before entering a FIND command.

This message is self explanatory.

This is an informational message. A FIND ALL command was issued with columns specified. This message tells the user how many occurrences of the string were found.

This is an informational message. This message tells the user the string was found.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

The attempt to allocate the backup data set aaaaaaaa was unsuccessful. The data set may have been deleted, or the volume on which it resides may be offline. Another user may have an exclusive enqueue on the data set.

An attempt to open backup data set aaaaaaaa was unsuccessful.

An unrecoverable error occurred while reading backup data set aaaaaaaa.

The attempt to allocate the target data set aaaaaaaa was unsuccessful. The data set may have been deleted, or the volume on which it resides may be offline. Another user may have an exclusive enqueue on the data set.

The attributes (LRECL, record format, and so on) of the target and backup data sets are not the same. It is probable that the target data set has been deleted or renamed and reallocated using different attributes.

An expected return code was received from module ISREBP.

The EDIT or VIEW service was requested using a data ID but the data ID was not previously defined using LMINIT.

The data set that you are attempting to Edit or View has attributes that are not supported by ISPF.

An attempt to open the edit or view target data set was unsuccessful.

An unexpected return code was received from module ISREAL.

All variables must be from 1 to 8 characters long.

The value to the left of the = sign must be a variable.

You have specified an excess number of variable names to the left of an assignment statement.

The command specification is syntactically incorrect.

The command specification is syntactically incorrect. Labels must start with a period and be from 1 to 8 alphabetic characters in length, the first of which must not be Z.

The label specified in the command cannot be found.

All variable names must be 1 to 8 characters long.

The command requires that variables be enclosed in parentheses.

Variable names within a template must be enclosed in parentheses.

A template must be enclosed by less than (<) and greater than (>) signs.

A column number is needed to indicate where the variable or string is to be substituted.

The line indicated in the line pointer could not be found.

A variable name is needed between the parentheses.

Either a partial range was entered, or a range was entered with an invalid type of lines to reset.

The only valid parameters for the NOTE command are ON or OFF.

The NOTE command requires only one parameter. ON or OFF are the only valid parameters.

This assignment statement is a single value phrase.

This assignment statement requires a line pointer argument.

The string specified and the keyphrase are invalid in this SET assignment command.

The string specified and the keyphrase name are invalid in this GET assignment command.

This is an informational message. The command name specified in the message has been defined as not operational (NOP).

The equal sign is not valid in a command issued from the command line of an edit session. It is only valid in an edit macro.

In order to reset a range of lines, two pointers are required. Specify a line pointer for both the beginning line and the ending line.

Two keywords were specified for the LOCATE command where only one is valid. An example would be LOCATE FIRST LAST CMD.

Only use ranges with one of the reset keywords. Using a range for more than one keyword is invalid.

There are too many parameters specified for the edit command.

A quoted string that contains no characters was entered with a FIND command.

This is an informational message. Once you have defined a command as disabled, you cannot define the command as MACRO, ALIAS, or NOP.

This message is self explanatory.

The find previous string entered was not found in the range of lines specified.

The find string entered was not found in the range of lines specified.

This message is issued when you try to find a string in either excluded or non-excluded lines in an empty data set or member.

The find string was not found on any excluded or non-excluded lines between the specified labels.

The left boundary plus the size of the find string exceeds the record length.

This message is issued when a FIND, CHANGE, or SEEK command is used in an edit macro and the column range is greater than the last column of data.

The command called aaaaaaaa has been disabled by the DEFINE aaaaaaaa DISABLED command. Most likely this was done in order to prevent you from causing damage to some application data. You cannot enable the aaaaaaaa command.

A FIND command was entered using an asterisk ("*") as the first string operand (the FROM string), but no previous FIND, CHANGE, SEEK, or EXCLUDE command was issued during this edit session.

No excluded or unexcluded lines exist in the file for the FIND command to search.

An invalid character exists in a picture string specification on a FIND command. The character may be an unusual hexadecimal code such as X'01'if the command is issued from a macro.

The search string was not found by the FIND command on any excluded or non-excluded lines between columns ddddd and eeeee.

The search string was not found by the FIND command on any excluded or non-excluded lines, but part of the file has not been searched.

The search string was not found by the FIND PREVIOUS command on any excluded or non-excluded lines, but part of the file has not been searched.

A string was specified on a FIND command that would not fit between the specified boundary columns.

A hexadecimal string was specified on a FIND command that did not have an even number of hexadecimal digits (0-9, A-F).

A hexadecimal string was specified on a FIND command that contained an invalid hexadecimal digit.

There are no members in the PDS specified, so a member list cannot be displayed.

An I/O error occurred while reading the PDS directory to build a member list. The member list cannot be built.

There was an error opening the PDS directory.

To invoke the EDIT or VIEW service, you may specify either a data set name, DATAID, workstation file name, or z/OS UNIX file pathname. If a data set parameter is used, a member name can be specified in the data set name. If a DATAID is specified, the member parameter is used to specify a member name.

Valid options for the EDREC service are INIT, QUERY, PROCESS, CANCEL, and DEFER.

The EDREC service must be invoked with the QUERY option before being invoked with the CANCEL option.

There are no valid commands from this panel.

The EDIT or VIEW service was invoked without a data set, DATAID, workstation file, or z/OS UNIX file pathname parameter.

You may specify a volume for the EDIT or VIEW service only if you use the data set parameter. For a request with a DATAID, the volume is specified on the LMINIT service.

The CMD parameter is only valid with INIT; password and DATAID are only valid with PROCESS.

The valid parameters for the LINE_AFTER command are: the line pointer, the line type, the data for the line, or a label or pointer to a line to be placed after the line pointed to by the line pointer. If the data for a line is not in quotation marks, the data may be considered to be extra parameters.

This is an informational message. An incorrect line type may have been specified.

Either an extra parameter or an invalid parameter was specified for the LINE_AFTER command.

A line number or a label must be specified as the target for a LINE_AFTER command.

The LINE_AFTER command requires that data be specified for the for the line being added.

When the LINE keyword is used with the MASKLINE or TABSLINE command, a line pointer must follow the LINE keyword.

The line pointed to by the line pointer does not exist in the data.

The data pointer or length is invalid for the LINE, ADDLINE, MASKLINE, or TABSLINE command.

An error occurred while processing a variable in the assignment statement specified in the error message. One possible cause is that the variable is too small to hold the value. If the value being returned is a line number or column number and the variable is VDEFINEd in character format, it should be defined as 8 characters for line numbers and 5 characters for column numbers. The returned value is left padded with zeros. For compatibility with previous releases of ISPF, column number variables of 3 or 4 characters and line number variables of 6 or 7 characters are allowed in cases where no data loss will occur.

Inconsistent parameters were specified for the given commands.

The valid parameters for the LINE_BEFORE command are: the line pointer, the line type, the data for the line, or a label or pointer to a line to be placed after the line pointed to by the line pointer. If the data for a line is not in quotes, the data may be considered to be extra parameters.

This is an informational message. An incorrect line type may have been specified.

Either an extra parameter or an invalid parameter was specified for the LINE_BEFORE command.

A line number or a label must be specified as the target for a LINE_BEFORE command.

The LINE_BEFORE command requires that non-blank data be specified for the line being added.

The EXCLUDE command may contain 1 string, 1 direction keyword, and 1 type keyword.

Two directional or two type keywords were specified.

An invalid parameter has been entered for the EXCLUDE command. Check the parameters.

The EXCLUDE command contains more than one string. Put the string in quotes.

A string was not specified for the EXCLUDE command.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

A FROM string was entered for the CHANGE command but no TO string was entered.

The RCHANGE command can only be used after a CHANGE command has been entered or when a CHANGE command is on the command line.

The RCHANGE command has been used following a FIND command. Enter a CHANGE command with a TO string to use the RCHANGE command.

This message is self explanatory.

This message is self explanatory.

The COMPARE edit command was issued with the NEXT or SESSION keyword from an edit session which was initiated through the EDIF, VIIF or EDIREC service. The COMPARE command is not supported from this environment because the EDIF and VIIF interface edits data in storage, and the compare program requires a physical data set and a catalogued data set name.

This is an informational message.

This is an informational message.

When using the CHANGE edit command and specifying a special string (picture (p''), hex (x''), text (t'') or character (c'')) as the source (or 'from') string, the target (or 'to') string cannot be a text (t'') string of a different length. For example, the command

CHANGE P'##' T'ABCD'

is invalid because the target text string (T'ABCD') is not the same length as the source picture string.

When using the edit CHANGE command and specifying a picture (p'') string as both the source (or 'from') and target (or 'to') string, the two strings must be of the same length.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message.

A COMPARE edit primary command was entered which had too many parameters. The COMPARE command can specify a member name or NEXT when you are editing a partitioned data set, or a data set name. Additional parameters may be SYSIN, EXCLUDE, or SAVE.

This is an informational message.

This is an informational message.

This is an informational message.

An edit CHANGE command was entered that specified a left boundary within the range of the edit line numbers. A CHANGE command cannot be used to change the sequence numbers of a file. The minimum value that can be used as the left boundary is aaaaaaaa.

An edit CHANGE command was entered that specified a right boundary within the range of the edit line numbers. A CHANGE command cannot be used to change the sequence numbers of a file. The maximum value that can be used as the right boundary is aaaaaaaa.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message.

An invalid MASKLINE command was entered.

An invalid MASKLINE command was entered.

An invalid MASKLINE command was entered.

An invalid MASKLINE command was entered.

An invalid TABSLINE command was entered.

An invalid TABSLINE command was entered.

An invalid TABSLINE command was entered.

An invalid TABSLINE command was entered.

Some edit profile attributes can be forced to values by settings in the ISPF configuration table. These values include RECOVERY, the recovery warning message, PACK, STATS, and SETUNDO.

This is an informational message. The data set is sequential and has been created using the data that was specified.

An invalid INSERT command was entered.

An invalid INSERT command was entered.

An invalid INSERT command was entered.

An invalid INSERT command was entered.

An invalid INSERT command was entered.

An invalid TENTER command was entered.

An invalid TENTER command was entered.

An invalid TENTER command was entered.

An invalid TENTER command was entered.

An invalid TENTER command was entered.

An invalid SOURCE command was entered.

An invalid CHANGE command was entered.

An invalid SOURCE command was entered.

The command requires you to put single quotation marks around the characters to be displayed.

This is an informational message.

This is an informational message.

This is an informational message.

This is an informational message.

A command specifying an invalid left boundary has been entered.

A command with an invalid column range has been entered.

An edit FIND, CHANGE, SEEK, or EXCLUDE was attempted with a string longer than 256 characters. The maximum length for the strings on these commands is 256.

A CHANGE command was entered using an asterisk (*) as the first string operand (the FROM string), but no previous FIND, CHANGE, SEEK, or EXCLUDE command was issued during this edit session.

No excluded or unexcluded lines exist in the file for the change command to search.

An invalid character exists in a picture string specification on a CHANGE command. The character may be an unusual hexadecimal code such as X'01'if the command is issued from a macro.

The search string was not found by the CHANGE command on any excluded or non-excluded lines between columns ddddd and eeeee.

The search string was not found by the CHANGE command on any excluded or non-excluded lines, but part of the file has not been searched.

The search string was not found by the CHANGE PREVIOUS command on any excluded or non-excluded lines, but part of the file has not been searched.

A string was specified on a CHANGE command that would not fit between the specified boundary columns.

A hexadecimal string was specified on a CHANGE command that did not have an even number of hexadecimal digits (0-9, A-F).

A hexadecimal string was specified on a CHANGE command that contained an invalid hexadecimal digits.

An invalid MOVE command was entered.

An invalid MOVE command was entered.

An invalid MOVE command was entered.

An invalid LINENUM command was entered.

The command could not be executed because the line number entered is invalid.

An invalid LINENUM command was entered.

The member you are trying to edit is SCLM controlled.

The editor was unable to process a pending edit recovery because the format of the recovery data set is incorrect. The most likely explanation for this condition is that you are trying to process a recovery data set created during an edit session run on a previous release of ISPF.

The member you are trying to replace is SCLM controlled.

The failure can occur if the required conversion is not defined to MVS Conversion Services. MVS Conversion Services needs to be configured for the CCSIDS involved using search technique ER in order for the conversion to be done. Refer to Support for Unicode : Using Conversion Services, chapter 3.

An invalid CREATE command was entered.

An invalid CREATE command was entered.

An invalid CREATE command was entered.

An invalid LINE command was entered.

An invalid LINE command was entered.

An invalid LINE command was entered.

An invalid LINE command was entered.

An invalid LINE command was entered.

This message is self explanatory.

This message is self explanatory.

An invalid CHANGE command was entered.

An invalid CHANGE command was entered.

An invalid parameter has been entered.

In order for the command to run, the source and target character strings must be enclosed in single quotation marks.

An invalid CHANGE command was entered.

An invalid CHANGE command was entered.

An invalid command has been entered.

The command entered requires a label.

An invalid COPY command was entered.

This message is self explanatory.

This message is self explanatory.

This is an informational message. This message is sent to the user's log data set when the user presses Enter from panel ISREDM02 (the Edit Automatic Recovery panel) to continue editing the data set.

This message is self explanatory.

PDF was unable to open the recovery data set.

This informational message appears in the user's ISPF log data set when PDF is unable to open the recovery data set. Message ISRE304 will also appear on the user's terminal.

PDF was unable to process the recovery data set. Suspend code = X'02'

PDF was unable to write to the recovery data set. Suspend code = X'00'or X'03'.

This message is self explanatory.

An error occurred while trying to write to the recovery data set.

An edit macro command that cannot be used in an initial macro was used in an initial macro. Commands referencing display values (DISPLAY_COLS, DISPLAY_LINES, DOWN, LEFT, RIGHT, UP, LOCATE) are invalid in an initial macro because no data has been displayed.

This is an informational message. Not enough storage was available for the editor to save the current transaction in storage. The record of edit changes has been reset so that subsequent changes may be undone; however, changes made before this message is displayed cannot be undone.

There is not enough storage available for the editor to retain a complete original copy of the data set or member being edited. UNDO from storage is no longer available.

There is not enough storage available for the editor to retain a complete original copy of the data set or member being edited. UNDO from storage is not available. However, since recovery is active, UNDO will continue to be available from the recovery file.

There is not enough storage available for the editor to retain a complete original copy of the data set or member being edited. UNDO from storage is no longer available.

When displaying ASCII data, ISPF needs a codepage specification for the terminal. This information can be provided by the terminal or on the ISPSTART command. Otherwise ISPF will attempt to use a default.

The edit backup data set, also called the recovery file, has been allocated incorrectly and cannot be used for saving edit session changes. This may be due to an existing recovery data set which has incorrect attributes. In some cases, edit recovery will delete that data set, so turning recovery off and back on will fix this problem.

The editor has been forced to renumber a large number of records and the sequence numbers of successive records are so close that future changes may cause excessive renumbering of the data.

The UNDO command is not available because both SETUNDO STORAGE and RECOVERY are off or suspended.

A SHIFT edit macro command was issued with too many parameters. A maximum of 3 parameters is allowed: shift type, line pointer, and shift amount.

A SHIFT edit macro command was issued with at least one invalid parameter. The shift type and a line pointer must be specified. A shift amount is optional.

A SHIFT edit macro command was issued with at least one invalid parameter. The shift type and a line pointer must be specified. A shift amount is optional.

A SHIFT edit macro command was issued without a line pointer value. The shift type and a line pointer must be specified, a shift amount is optional.

A SHIFT edit macro command was issued without a shift type. The shift type, (, ), <, or >, and a line pointer must be specified; a shift amount is optional.

A SHIFT edit macro command was issued an invalid line pointer. The line pointer must be a valid, existing line number, or a valid, existing label.

As the SOURCE command is changing the view of the data, it is restricted from being entered at the same time as line commands.

The bbbbbbbb command has an operand that looks like a label, but either the label does not exist in the file, or it is syntactically incorrect.

An error has occurred due to an incorrectly defined internal PDF table.

An error has occurred due to an incorrectly defined internal PDF table.

An edit macro issued the USER_STATE command with too many parameters. The user state command allows only a variable name as a parameter.

An edit macro issued the USER_STATE command with an invalid parameter. The user state command allows only a variable name as a parameter.

This message is self explanatory.

An edit macro statement issued a USER_STATE = (var) assignment statement using a variable that contained invalid data. The variable must be set with data saved from a previous (var) = USER_STATE command.

This message is self explanatory.

An edit macro issued a USER_STATE command with an invalid parameter or invalid syntax.

An edit macro issued a USER_STATE command with no parameters. A variable name is required.

The SAVE and SYSIN operands of the COMPARE command may only be used when a compare data set or member name is also supplied on the COMPARE command. The SAVE operand saves the SuperC listing to a data set named prefix.ISPFEDIT.COMPARE.LIST. The SYSIN operand allows SuperC to obtain Process Statements from an existing allocation to DD name SYSIN. If SYSIN is not specified, the DD name SYSIN is freed before SuperC is invoked.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

This message is self explanatory.

Automatic codeset conversion is enabled for this file. Therefore low-level I/O handles conversion of the data between the file's tagged CCSID and EBCDIC. The data in the edit display area is in EBCDIC. The ISPF editor has not attempted to convert the data from ASCII to the CCSID of the terminal.

An EXCLUDE command was issued that had a null string as the string to be excluded.

The string to be excluded by an EXCLUDE command could not be determined from the command. This usually occurs when the string is a valid keyword on the command, or the string is a comma.

The string to be excluded by an EXCLUDE command was not found between the labels specified on the EXCLUDE command. The original EXCLUDE command specified that the search be from the bottom of the range to the top of the range. The top of the range was reached without finding the string.

The string to be excluded by an EXCLUDE command was not found between the labels specified on the EXCLUDE command. The original EXCLUDE command specified that the search be from the top of the range to the bottom of the range. The top of the range was reached without finding the string.

This message is self explanatory.

This message is self explanatory.

The left boundary plus the size of the exclude string exceeds the record length.

An EXCLUDE command in an edit macro attempted to find a string outside of the current data columns.

A FIND or EXCLUDE command was entered using an asterisk (*) as the first string operand (the FROM string), but no previous FIND, CHANGE, SEEK, or EXCLUDE command was issued during this edit session.

No excluded or unexcluded lines exist in the file for the FIND command to search.

An invalid character exists in a picture string specification on a FIND command. The character may be an unusual hex code such as X'01'if the command is issued from a macro.

The search string was not found by the FIND or EXCLUDE command on any excluded or non-excluded lines between columns ddddd and eeeee.

The search string was not found by the FIND or EXCLUDE command on any excluded or non-excluded lines, but part of the file has not been searched.

The search string was not found by the FIND PREVIOUS or EXCLUDE PREVIOUS command on any excluded or non-excluded lines, but part of the file has not been searched.

A string was specified on a FIND or EXCLUDE command that would not fit between the specified boundary columns.

A hexadecimal string was specified on a FIND or EXCLUDE command that did not have an even number of hexadecimal digits (0-9, A-F).

A hexadecimal string was specified on a FIND or EXCLUDE command that contained an invalid hexadecimal digits.

An ISREDIT TFLOW edit macro command was incorrectly issued from an edit macro. The TFLOW command allows only 2 parameters: a line pointer and a column number.

An ISREDIT TFLOW edit macro command was incorrectly issued from an edit macro. Possibly the line pointer was correctly specified, but the column number was invalid.

This message is self explanatory.

An ISREDIT TFLOW edit macro command was incorrectly issued from an edit macro. Most likely, the line pointer operand is invalid.

An ISREDIT TFLOW edit macro command was incorrectly issued from an edit macro. The line pointer references a line that does not exist in the edit data.

An ISREDIT TSPLIT edit macro command was incorrectly issued from an edit macro. The TSPLIT command allows only 2 parameters: a line pointer and a column number.

An ISREDIT TSPLIT edit macro command was incorrectly issued from an edit macro. The line pointer or column number is invalid.

An ISREDIT TSPLIT edit macro command was incorrectly issued from an edit macro. The line pointer refers to a line that is not in the edit data.

An ISREDIT TSPLIT edit macro command was incorrectly issued from an edit macro. Only one parameter was specified.

MVS Conversion Services has issued a non critical return code. The EDIT session has continued

The edit macro command XSTATUS was issued with too many parameters.

The edit macro command XSTATUS was issued with invalid parameters.

The edit macro command XSTATUS was issued without a line number parameter.

The edit macro command XSTATUS was issued without a status indicator.

The edit macro command XSTATUS was issued with an invalid line number. In this case, the line number is a type of line-pointer. The relative line number may not exist in the file.

An internal error occurred trying to free a data ID for edit macro execution.

The DISPLAY_LINES edit macro command was used in an initial macro. DISPLAY_LINES cannot be used until the data is actually displayed at least once, and, therefore, cannot be used in an initial macro.

An internal error occurred trying to create a data ID for edit macro execution.

The UP command was specified with too many parameters.

The UP command was specified with invalid parameters.

An invalid parameter was used with the UP command.

There were too many parameters specified for the RIGHT command.

Both parameters cannot be specified for the RIGHT command.

An incorrect parameter was specified for the RIGHT command.

Too many parameters were specified for the LEFT command.

Both parameters cannot be specified for the LEFT command.

A parameter was incorrect for the LEFT command.

Too many parameters were specified for the DOWN command.

Both parameters cannot be specified for the DOWN command.

An incorrect parameter was specified for the DOWN command.

The requested last line was not found for the extended copy command. The end-of-file was reached before the copy was completed.

A member list is not supported with the COPY command. A member name must be provided.

This is an informational message. The data from the member selected was copied. The member the data was copied from still exists.

This is an informational message. The data from a sequential data set was either copied or moved into the member of a partitioned data set. The data that was copied still exists, but the data that was moved no longer exists in the sequential data set.

This is an informational message. The data set was copied or moved. The data in the data set that the data was copied from still exists, or the data set that the data was moved from no longer exists.

Using the extended copy command and setting any of the line number parameters (First line, Last line or Number type) requires that all three parameters are set.

The number type entered is incorrect.

The value entered in the first line number field is greater than the value entered in the last line number field on the extended copy panel.

One of the values entered for the first line or last line number is not a positive decimal number greater than zero on the extended copy panel.

The first line number entered on the extended copy panel is not valid. The data set the data was to be copied from does not contain a record for that line. The end-of-file was reached in the from data set.

This is an informational message. The requested lines were copied.

This is an informational message. The requested lines were copied.

This is an informational message. The requested lines were copied.

This is an informational message. The requested lines were copied.

The range specified contained no lines for the COPY command.

This is an informational message. A member list is not supported for this command.

The member was not printed due to an error in opening the DCB for print.

This is an informational message. The data set is sequential and has been replaced by the data that was specified.

The data set file attributes have changed and no data has been saved.

The data set is still in use after the abend. To save the data, use the extended CREATE or REPLACE command to save the data into another data set. If you do not want to save the data, cancel the edit session.

The DATAID assignment statement is missing the required variable name for the data set currently allocated for editing.

The Member assignment statement is missing the required variable name for the member currently being edited.

The LRECL assignment statement is missing the required variable name for the maximum space in bytes available for data.

The FLOW_COUNTS assignment statement is missing a variable name for the most recently entered TFLOW command. At least one FLOW_COUNTS assignment statement variable must be coded.

The EXCLUDE_COUNTS assignment statement is missing a variable name for the most recently processed EXCLUDE command. At least one EXCLUDE_COUNTS assignment statement variable must be coded.

Either the DATAID assignment statement contains an invalid variable name or a parameter is missing.

Either the MEMBER assignment statement contains an invalid variable name or a parameter is missing.

Either the LRECL assignment statement contains an invalid variable name or a parameter is missing.

Either the FLOW_COUNTS assignment statement contains an invalid variable name or a parameter is missing.

Either the EXCLUDE_COUNTS assignment statement contains an invalid variable name or a parameter is missing.

The SORT command only allows X or NX to be specified. You cannot use both in the same command.

The SORT parameter that was entered is invalid.

Too many sort field parameters have been entered. SORT allows a maximum of five sort fields.