Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
ISRE600 z/OS ISPF Messages and Codes SC19-3622-00 |
|
ISRE600 Invalid bounds parameter - "aaaaaaaa"
is invalid as a parameter to the BOUNDS command. ExplanationThe value aaaaaaaa specified on the BOUNDS command is not a valid parameter. User responseEnsure that all parameters are valid when entering BOUNDS command. Information for the BOUNDS command can be obtained by using Help. ISRE601 Too many parameters - Left and right column numbers (or *)
are only valid BOUNDS command parms. ExplanationToo many parameters were specified on the BOUNDS command. The BOUNDS command should be entered with no parameters or 2 parameters. The 2 parameters are the left column number and the right column number. ISRE602 Invalid specification - Either specify both left and right
BOUNDS operands or specify neither. ExplanationOnly one parameter was specified on the BOUNDS command. The BOUNDS command requires either no parameters or 2 parameters. User responseSpecify no parameters on the BOUNDS command to use the default bounds, or specify both left and right columns. An "*" (asterisk) can be used as either the left or right column parameter, indicating that the current value for that bounds should be retained. ISRE603 Invalid left bound - Left bound was invalid as entered and
was reset to its default column. ExplanationThe left bound that was specified is either before the first data column or after the last data column. User responseSpecify a left bound that is within the data columns. ISRE604 Invalid right bound - Right bound was invalid as entered
and was reset to its default column. ExplanationThe right bound that was specified is either before the first data column or after the last data column. User responseSpecify a right bound that is within the data columns. ISRE605 Left bound exceeds right - Invalid for left bound specification
to exceed right bound specification. ExplanationThe first value specified, which is the left bound, is greater than the value specified for the right bound. The value specified for the left bound must be smaller than the value for the right bound. User responseSpecify a value for the left bound that is smaller than the value specified for the right bound. ISRE606 Both bounds invalid - Both bounds were invalid as entered
and were reset to their default columns. ExplanationThe left bound that was specified is either before the first data column or after the last data column and the right bound that was specified is either before the first data column or after the last data column. User responseSpecify bounds values within the data columns. ISRE607 Too many parameters - Invalid line number, column number,
label, or cursor command keyword. ExplanationToo many parameters were specified on the CURSOR command. This may be due to an invalid line number, column number, or label. User responseEnsure that the cursor command has the correct number of parameters. ISRE608 Invalid parameter - Invalid line number, column number, label,
or cursor command keyword. ExplanationA parameter specified on the CURSOR command is not valid. This may be due to an invalid line number, column number, or label. User responseEnsure that the line number and column number specified on the cursor command have valid values. ISRE609 Parameter unrecognized - Invalid line number, column number,
label, or cursor command keyword. ExplanationA parameter specified on the CURSOR command was not recognized as a valid parameter. This may be due to an invalid line number, column number, or label. User responseEnsure that the cursor command has the correct number of parameters and that they are all valid. ISRE610 Changes not saved - Changes to data are not saved within
View sessions. Use Create or Replace commands to save changes. ExplanationA SAVE or END command has been requested from within an edit macro running in VIEW. View does not save changes to data. User responseIn order to save the changes, use the primary CREATE or REPLACE command. Programmer responseIf your macro is designed to run from within View, and your macro makes data changes, use the cancel command to leave the view session. ISRE611 Cmd not valid for ascii - The TE (text entry) and TF (text
flow) commands are not supported when editing ascii data. ExplanationA TE or TF line command has been entered but the user is editing ascii data. User responseRemove the TE or TF line command. ISRE622 -CAUTION- Profile changed to NUMBER ON COB (from NUMBER ON
STD COB). ExplanationThis message is self explanatory. ISRE623 LRECL is not large enough for COBOL and standard numbers. ExplanationThis message is self explanatory. ISRE632 Changes are shown - The differences between the files are
now highlighted. This file was compared to 'aaaaaaaa'. ExplanationThe compare command completed successfully and the differences between the files are now highlighted. The file with which the edited data set was compared is shown in the long message (aaaaaaaa). User responseIf some differences are not shown, or you would like to modify the comparison methods, use the COMPARE command with no operands to change the comparison settings. ISRE633 Files are the same - This file was compared to 'aaa(56)'.
The compared files have no differences. ExplanationThe compare command completed successfully and no differences were found. The file with which the edited data set was compared is shown in the long message (aaa(56)). User responseIf some differences are not shown, or you would like to modify the comparison methods, use the COMPARE command with no operands to change the comparison settings. ISRE638 SuperC error - SuperC ended with a return code of aa. ExplanationThe SuperC compare program, which is used to compare the files specified with the COMPARE command, ended with a return code (aa), which indicates that the comparison failed. Possible reasons for the failure may include I/O errors, unsupported data set types, allocation errors or other failures. User responseUse the SuperC dialog in the utilities section to compare the files. If there is a failure there, you may be able to find the cause in the SuperC listing. ISRE639 Delta file error - An unrecognized control card was found
in the delta file. Use the SuperC dialog in the utilities section
to compare the files. ExplanationAn unrecognized control card was found in the delta file which was produced by SuperC during the comparison. This may result if the temporary delta file created by the editor was too small to hold all of the records written by SuperC, or it may be the result of a SuperC error. User responseUse the SuperC dialog in the utilities section to compare the files. ISRE644 Files Compared - No differences were found, but some differences
may exist which are not shown. Options were selected on the Edit
Compare Settings panel which may cause some data to be ignored during
the comparison. This file was compared to 'aaa(56)'. ExplanationThe COMPARE edit command detected no differences. However options were selected on the Edit Compare Settings Panel which filtered the input to the compare program. As a result, some differences may have been ignored during the compare and may not be highlighted in the editor. ISRE645 No matches - Files have been compared and they are completely
different. Edit has reset the display. ExplanationThis message is self explanatory. ISRE656 ASCII already set - The ASCII option was already set. ExplanationThis message is self explanatory. ISRE668 Changes are shown - The differences between the files are
now highlighted. This file was compared to 'aaaaaaaa'.
The SuperC listing is saved in data set 'bbbbbbbb'. ExplanationThe compare command completed successfully and the differences between the files are now highlighted. The file with which the edited data set was compared is shown in the long message (aaaaaaaa). The SuperC listing was saved in data set 'bbbbbbbb' as a result of the SAVE option being specified. User responseIf some differences are not shown, or you would like to modify the comparison methods, use the COMPARE command with no operands to change the comparison settings. ISRE669 Files are the same - This file was compared to 'aaa(56)'.
The compared files have no differences. The SuperC listing is saved
in data set 'bbbbbbbb'. ExplanationThe compare command completed successfully and no differences were found. The file with which the edited data set was compared is shown in the long message (aaa(56)). The SuperC listing was saved in data set 'bbbbbbbb' as a result of the SAVE option being specified. User responseIf some differences are not shown, or you would like to modify the comparison methods, use the COMPARE command with no operands to change the comparison settings. ISRE720 Too many parameters - You may specify a member name and AFTER
or BEFORE aaaaaaaa with MOVE command ExplanationToo many parameters are specified for the MOVE command. User responseRemove the invalid parameter. ISRE721 Invalid parameter - You may specify a member name and AFTER
or BEFORE followed by a aaaaaaaa. ExplanationAn invalid parameter was specified. User responseRemove the invalid parameter and try again. ISRE722 Destination is required - aaaaaaaa requires
AFTER/BEFORE lptr. Member name is also required. ExplanationThe destination parameter was omitted. User responseSpecify either AFTER or BEFORE and the member name. ISRE723 Member name is required - In a macro a member name, data
set name and member, sequential data set name, or z/OS UNIX file
pathname are required by aaaaaaaa command ExplanationThe member name was omitted. User responseSpecify a valid member name. ISRE724 Too many parameters - You may specify a member name, data
set name and member, sequential data set name, or z/OS UNIX file
pathname and aaaaaaaa range on a CREATE command. ExplanationToo many parameters were specified. User responseRemove the invalid parameter. ISRE725 Invalid parameter - You may specify a member name, data set
name and member, sequential data set name, or z/OS UNIX file
pathname and aaaaaaaa range on a CREATE command. ExplanationAn invalid parameter was specified. User responseRemove the invalid parameter and try the CREATE command again. ISRE726 -CAUTION- Profile changed to STATS ON (from STATS EXT) because ExplanationThis message is self explanatory. ISRE727 extended ISPF statistics do not exist for this member. ExplanationThis message is self explanatory. ISRE728 Too many parameters - You may specify a member name, data
set name and member, sequential data set name, or z/OS UNIX file
pathname and an aaaaaaaa range with REPLACE command ExplanationToo many parameters were specified for the REPLACE command. User responseRemove the excess parameters and try the operation again. ISRE729 Invalid parameter - You may specify a member name, a data
set name and member, sequential data set name, or z/OS UNIX file
pathname and an aaaaaaaa range with REPLACE command ExplanationAn invalid parameter was specified for the REPLACE command. User responseRemove the invalid parameter and try the command again. ISRE730 STAE macro error - Unable to obtain storage for STAE macro,
subpool 0 full. ExplanationThis is an informational message. ISRE731 Invalid block size - Specified data set has zero block size. ExplanationThe specified data set has a block size of zero; this is invalid. User responseEither choose a different data set or change the block size. ISRE732 BLDL error - I/O error, insufficient virtual storage, or
other BLDL error. ExplanationThis is an informational message. System programmer responseThis is a probable system failure. Isolate the reason for the failure. User responseRequest additional virtual storage. If the error recurs, contact your system programmer. ISRE733 I/O error during read - Unable to read data. ExplanationA failure occurred while attempting to read a data set. System programmer responseThis is probably a system error. Isolate the error, contact IBM® support. User responseContact your system programmer. ISRE734 Member not found - The requested member was not found in
the PDS directory(s). ExplanationThe member you specified was not found in the data set directory. User responseVerify that the member exists. ISRE735 Data set not partitioned - Member name specified, but the
data set is not a partitioned data set. ExplanationIf you specify a member name, the data set must be partitioned. User responseEither remove the member name or correct the data set name. ISRE736 Member list update error - Member name not added to member
list. An error occurred during update. ExplanationThe attempt to update the member list failed. System programmer responseThis is likely the result of a system failure. Isolate the cause of the failure. User responseContact your system programmer. ISRE737 Invalid member name - Member name aaaaaaaa not
valid for partitioned data sets. ExplanationAn invalid member name was entered. User responseCorrect the member name. ISRE738 Member aaaaaaaa created - aaaaaaaa was
added to bbbbbbbb ExplanationThis is an informational message. ISRE739 Too many parameters - Too many parameters were entered with
the scrolling command. ExplanationToo many parameters were entered for the SCROLL command. User responseRemove the invalid parameters. ISRE740 Command is not a macro - "aaaaaaaa" does
not contain an ISREDIT MACRO statement. ExplanationThe command you entered is not a valid edit macro. User responseDetermine the correct edit macro name. If the edit macro name is correct, contact the responsible programmer. Programmer responseVerify the macro name, add an ISREDIT MACRO statement to the macro. ISRE741 Command not executed - An ISREDIT MACRO statement must precede
any executable statements. ExplanationThe macro name you entered does not have the ISREDIT MACRO statement as the first executable instruction. User responseContact the responsible programmer. Programmer responseVerify that the first executable instruction in the macro is the ISREDIT MACRO instruction. ISRE742 System error, no SYSPROC - Command is invalid or a macro.
Macros require an allocated SYSPROC. ExplanationEither you entered an invalid command or you requested that a macro be run but did not first allocate a SYSPROC. User responseAllocate a SYSPROC and attempt the operation again or correct the command. ISRE743 Command name invalid - "aaaaaaaa" is an
invalid macro name; invalid SYSPROC member name. ExplanationEither you entered an invalid command or macro name. User responseCorrect the command or macro name. ISRE744 Error accessing macro - BLDL error accessing SYSPROC member
"aaaaaaaa". ExplanationA BLDL error was received when attempting to access the specified macro. System programmer responseIsolate the system failure. User responseContact your systems programmer. ISRE745 Invalid command name - "aaaaaaaa" is not
a valid edit command or macro name ExplanationAn invalid macro name or edit command was entered. User responseCorrect the command or macro name. ISRE746 No command name found - ISREDIT was not followed by a command
name ExplanationThe ISREDIT command was entered without the required command parameter. User responseReenter the ISREDIT command with the correct command name. ISRE747 Invalid macro command - Parameter found outside parentheses
and is not PROCESS/NOPROCESS. ExplanationPROCESS or NOPROCESS is probably misspelled. User responseCorrect the macro command. ISRE748 Parameters are invalid - The "aaaaaaaa"
macro command must be specified without parameters. ExplanationAdditional parameters were specified that are not allowed for this service. User responseRemove the invalid parameters. ISRE749 MACRO command is invalid - The MACRO command must be specified
only once in a macro. ExplanationThe macro that was specified has multiple MACRO statements. User responseContact the responsible programmer. Programmer responseCorrect the macro logic. ISRE750 No space in directory - PDS directory is full, allocate more
directory blocks. ExplanationThe data set you specified has no more directory space for entries. User responseReallocate the data set with additional directory entries. ISRE751 I/O error during STOW - Permanent I/O error occurred updating
directory block. ExplanationAn attempt to write directory information resulted in an error. System programmer responseThis likely is the result of a system failure. Isolate the cause for the STOW error. User responseContact your system programmer. ISRE752 I/O error during STOW - Permanent I/O error occurred writing
EOF mark after member. ExplanationAn attempt to write the end-of-file marker resulted in an error. System programmer responseThis likely is the result of a system failure. Isolate the cause of the error. User responseContact your system programmer. ISRE753 Truncation warning. The data you are editing is variable
length data with at least one record that ends with a blank. Saving
the data will result in removal of any trailing blanks from all records.
You can issue the PRESERVE ON command if you don't want the blanks
removed. ExplanationThe data being edited contains variable length records, and one or more of these records ends with a blank. If you use the Edit SAVE or END command to save the data, the editor will remove any trailing blanks from each record prior to writing the record. Blanks will be removed regardless of whether an individual record was modified during the edit session. Issuing the PRESERVE ON command will tell the editor not to strip the blanks off the records. ISRE754 I/O error during write - Unable to write data. ExplanationSTOW with replace failed. System programmer responseThis likely is the result of a system failure. Isolate the cause of the failure. User responseContact your system programmer. ISRE755 System abend 'aaaaaaaa' - Data was not
saved due to abend. Press Help key for further information. ExplanationThis is an informational message. User responseSee MVS Message Library: System Codes for an explanation of the abend code if the tutorial panel was not sufficient help. ISRE756 Invalid command - The only valid command is LOCATE (L). ExplanationAn invalid command was entered for this panel. User responseChange the command to LOCATE member or L member. ISRE757 Either the member name was not found in the PDS directory(s)
or the data set name is not cataloged. ExplanationThe member or data set requested for the copy could not be found. User responseChange the member name or data set name. ISRE758 Insufficient storage - Not enough storage is available to
update directory (using STOW). ExplanationSTOW failed due to insufficient virtual memory. System programmer responseIf this is a recurring error, verify that a system failure is not occurring. User responseTry this operation again later. If the error recurs, contact your systems programmer. ISRE759 aaaaaaaa input error - VPUT failed to
set variable bbbbbbbb to value cccccccc ExplanationAn ISPF internal VPUT failed to set variable bbbbbbbb in
an edit macro. Possible causes for this in a program macro are:
Additional possibilities, applicable
to all types of macros, are:
User responseContact the responsible programmer. Programmer responseCheck for the problems shown. If none of these problems exists, contact IBM service. ISRE760 Too many parameters - The member name is the only valid parameter
for the EDIT, VIEW, or BROWSE commands. ExplanationToo many parameters were specified for the EDIT, VIEW, or BROWSE commands. The EDIT, VIEW, and BROWSE commands allow only the member name as a parameter. User responseRemove the extraneous parameters and try the command again. ISRE761 Invalid parameter - Extraneous or invalid parameter was specified
for the EDIT, VIEW, or BROWSE command. ExplanationAn extra or invalid parameter was specified for the EDIT VIEW, or BROWSE command. The EDIT, VIEW, and BROWSE commands allow only the member name as a parameter. User responseRemove the invalid parameter and try the command again. ISRE762 Member/filename omitted - Required member/filename parameter
not specified for EDIT, VIEW, or BROWSE command. ExplanationThe member name or file name is required to use the EDIT, VIEW, or BROWSE command. User responseSpecify a member name or file name when using the EDIT, VIEW, or BROWSE command. ISRE763 Invalid member name - Member name "aaaaaaaa"
must be alphanumeric chars, starting with alpha. ExplanationThe member name is invalid for the EDIT, VIEW, or BROWSE command. User responseThe member name must contain alphanumeric characters beginning with an alphabetic character. Correct the member name and try the command again. ISRE764 Invalid member name - Member name "aaaaaaaa"
exceeds 8-character allowable length. ExplanationThe member name is invalid for the EDIT, VIEW, or BROWSE command. User responseThe member name may not exceed 8 characters. Correct the member name and try the command again. ISRE765 Member name not allowed - A member name cannot be specified
when editing, viewing, or browsing a sequential data set. ExplanationThe EDIT, VIEW, or BROWSE command cannot be invoked with a member name when a sequential data set is being edited, viewed, or browsed. User responseSpecify EDIT, VIEW, or BROWSE with no member name and try again. ISRE766 Variable process error - Error occurred processing a variable
in the EDIT or VIEW command. ExplanationA severe internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE767 EDIT or VIEW not allowed - Recursive entry to edit or view
is not allowed when recovery session is active. ExplanationThe EDIT and VIEW commands are not allowed because recovery is being processed on this screen. The recovery process needs to be completed before creation of a new recovery data set. User responseEnd edit or view recovery before using the EDIT or VIEW command. ISRE768 EDIT or VIEW table error - A table error was encountered
while processing EDIT or VIEW command. ExplanationA severe internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE769 Message line error - An error was encountered while trying
to format a message line. ExplanationThe message line could not be formatted. System programmer responseContact IBM support. User responseContact your system programmer. ISRE770 Too many parameters - The edit primary NOP command allows
no parameters. ExplanationParameters are not allowed for the edit primary NOP command. User responseRemove the parameters and try the command again. ISRE771 Too many parameters - The edit primary MACRO command allows
no parameters. ExplanationParameters are not allowed for the edit primary MACRO command. User responseRemove the parameters and try the command again. ISRE772 No parameters - The edit scrolling macro requires MAX/CSR/PAGE/HALF/DATA
or amount. ExplanationThe parameter for the macro was invalid. User responseValid parameters are MAX, CSR, PAGE, HALF, DATA, or the actual amount. ISRE773 Data panel error - A severe error occurred trying to process
data display panel through PQUERY. ExplanationAn internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE774 Storage allocation error - A severe error occurred trying
to GETMAIN storage for edit data display. ExplanationStorage could not be obtained to display the edit data. System programmer responseContact IBM support. User responseContact your system programmer. ISRE775 Severe display error - A severe error occurred in trying
to display the edit data ExplanationA severe error has occurred while trying to display the edit data. System programmer responseContact IBM support. User responseContact your system programmer. ISRE776 Invalid parameter - Extraneous or invalid parameter specified
with this command. ExplanationAn extraneous or invalid parameter was specified with this command. User responseRemove the extraneous parameter or correct the invalid parameter and try the command again. ISRE777 Error updating directory - STOW failed. Return code=aaaaaaaa Reason
code=bbbbbbbb (x'cccccccc'). ExplanationAn internal error has occurred. User responseContact the responsible programmer. Programmer responseIncrease the size of the directory. ISRE778 System abend 'aaaaaaaa' - An abend occurred
while attempting to save the data. The previous information in the
target sequential data set has been overwritten. The CANCEL command
will not restore the data in the data set. Press Help for further
information. ExplanationAn abend has occurred while attempting to save data. If the ABEND code specified was B37, D37, or E37, there is no space on the disk pack or there is no space in the data set to store the data. If an x37 ABEND occurred writing to a sequential data set, that data set has been overwritten. The CANCEL command will not restore the original contents. If UNDO is available, you may be able to undo all of your changes and SAVE the data set to restore its original contents. User responseFrom within the edit session (the edit data display
screen) you may:
ISRE779 Panel not found - The panel name specified in the PANEL field
for EDIT/VIEW could not be found. ExplanationThe EDIT service was invoked, passing the name of a panel to be used when displaying the edit data. The panel does not exist in the current ISPPLIB concatenation. User responseDetermine what data set the panel exists in, then modify your ISPF allocation CLIST or logon proc to contain that data set. ISRE780 Too many parameters - Do not specify parameters with the
RFIND command. ExplanationParameters were specified with the RFIND command, but parameters are not allowed. User responseRemove the parameters and try the command again. ISRE781 Too many parameters - Do not specify parameters with the
RCHANGE command. ExplanationParameters were specified with the RCHANGE command, but parameters are not allowed. User responseRemove the parameters and try the command again. ISRE782 Issue a change command - RCHANGE command works only after
a valid CHANGE command is issued. ExplanationThe RCHANGE command was issued, but no CHANGE command was issued previously. User responseIssue a CHANGE command before issuing the RCHANGE command. ISRE783 Issue a FIND command - RFIND command works only after a valid
FIND command is issued. ExplanationThe RFIND command was issued, but no FIND command was issued previously. User responseIssue a FIND command before issuing the RFIND command. ISRE784 Level out of range - The level parameter must be a positive
number from 0 to 255. ExplanationThe level parameter specified was not in the range 0 to 255. User responseEnter a value for the LEVEL parameter from 0 to 255 and try the command again. ISRE785 Invalid data sets - When comparing any data set to a one
which does not have a fixed record length, neither data set can have
a record length greater than 32756. ExplanationThe Edit Compare command does not allow comparisons of files when one or both of the files has a logical record length greater than 32756 and at least one of the files has a record format of variable(V) or unblocked(U). User responseIf you need to compare the files, use the SuperC utility to produce a listing instead of using the edit COMPARE command. ISRE786 -CAUTION- Profile changed to STATS EXT (from STATS OFF) because ExplanationThis message is self explanatory. ISRE787 extended ISPF statistics already exist for this member. ExplanationThis message is self explanatory. ISRE788 Member name required - Member name is required for this partitioned
data set. ExplanationAdd a member name to complete the specification of the partitioned data set indicated by the cursor. User responseSpecify the member name and retry. Browse the data set if you are uncertain which member is correct. ISRE789 Invalid data ID request - Only one data ID can be automatically
generated per edit recursion level. ExplanationThis message is self explanatory. ISRE790 Too many parameters - Too many parameters specified for the
LABEL command. ExplanationToo many parameters were specified for the LABEL command. User responseContact the responsible programmer. Programmer responseSpecify the correct number of parameters for the LABEL command. ISRE791 Invalid label name - 'aaaaaaaa' is an
invalid label name specified in the LABEL command. ExplanationThe label name is invalid. User responseContact the responsible programmer. Programmer responseSpecify a valid label name in the LABEL command. The label name must begin with a period followed by 1 to 8 alphabetic characters, the first of which must not be Z. ISRE792 No label found - No label is associated with the line specified
in the LABEL command. ExplanationThere is no label associated with the line specified in the LABEL command. User responseSpecify a label for the line. ISRE793 Invalid label name - Name started with reserved character
"Z" ExplanationThe label name started with the character Z, which is reserved for editor-defined labels. User responseContact the responsible programmer. Programmer responseSpecify a valid label name that does not start with Z. ISRE794 Label name missing - Required label name parm not correctly
specified for LABEL command. ExplanationThe label name is missing. User responseContact the responsible programmer. Programmer responseSpecify a label name for the LABEL command. ISRE795 Assignment command error - Assignment type (GET/SET) unrecognized
for LABEL command. ExplanationAn internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE796 Invalid line pointer - The line pointer specified for the
LABEL command does not exist. ExplanationThis is an informational message. The line number specified on the LABEL command does not exist. ISRE797 Required parm missing - Too few parameters were specified
for the LABEL command. ExplanationThere were too few parameters specified for the LABEL command. User responseContact the responsible programmer. Programmer responseSpecify all required parameters for the LABEL command. ISRE798 Invalid keyphrase - The LABEL command requires the keyphrase:
LABEL LINE-POINTER. ExplanationThe LABEL command must contain the phrase LABEL LINE-POINTER. User responseContact the responsible programmer. Programmer responseCorrect the LABEL command to contain the phrase LABEL LINE-POINTER. ISRE799 Invalid parameter - The optional level parameter of the LABEL
command must be numeric. ExplanationThe level parameter was not numeric. User responseContact the responsible programmer. Programmer responseSpecify a number from 0 to 255 for the level parameter. ISRE800 Edit profile unavailable - Edit profile table member 'aaaaaaaa'
could not be created or read. It may already be in use by you or
another user. Edit will run with a default profile. Changes made
to the edit profile will not be saved. ExplanationThe edit profile table could not be read or created. User responseExit the application and try again. If this message still appears, attempt to compress the profile data set, or delete the edit profile table. ISRE801 Edit table not open - Table 'aaaaaaaa'
is not open. Table service RC=bbbbbbbb. ExplanationThe edit profile table is not open. User responseExit the application and try again. If this message still appears, attempt to compress the profile data set, or delete the edit profile table. ISRE802 Invalid edit table - Table 'aaaaaaaa'
contains invalid variable(s). Table service RC=bbbbbbbb. ExplanationThe edit profile table contains invalid variables. User responseDelete the edit profile table from the profile data set. ISRE803 Edit profile error - Changes to any edit profile will not
be saved on disk this edit session. ExplanationThere was an error in the edit profile. Any changes to the edit profile will not be saved in this edit session. User responseExit the application and try again. If this message still appears, attempt to compress the profile data set, or delete the edit profile table. ISRE804 Invalid label - A label name assigned to level 0 has more
than 5 characters following the period. ExplanationA label name assigned to level 0 must have only 5 characters following the period. The label name being assigned has more than 5 characters. User responseContact the responsible programmer. Programmer responseCorrect the label statement to assign a label name of 5 characters or fewer following the period. ISRE805 Label not allowed - Label names can only be entered on data
lines. ExplanationA label name was entered on a line other than a data line. User responseEnter the label name on a data line. ISRE806 Member not allowed - Specifying a member is only allowed
for a partitioned data set. ExplanationA member name was specified for the CREATE, REPLACE, MOVE, or COPY command, but the data set is not partitioned, or a member name was specified for the SYSIN file for the COMPARE command when the data set is sequential. User responseSpecify the command without a member name. ISRE807 Error: File changed - This member has changed since the edit
session began. Save the data and reissue the COMPARE function. If
you do not want to save the data, use the CREATE or REPLACE command
to save it to a temporary location and use the COMPARE command while
editing that temporary file. ExplanationThe COMPARE service was issued in an edit session where the data was changed. The data in the edit session must exist on disk the same as it does in the edit session for the COMPARE command to function. Therefore, compare is only valid before the data is changed in the editor. User responseSave the data and reissue the COMPARE function. If you do not want to save the data, use the CREATE or REPLACE command to save it to a temporary location and use the COMPARE command while editing that temporary file. ISRE808 Parameters required - The COMPARE macro command requires
parameters. ExplanationThe COMPARE edit macro command was issued without parameters. In an edit macro, the COMPARE parameter requires parameters since edit macro commands do not display panels. User responseContact the author of the edit macro. Programmer responseChange the edit macro to include parameters on the COMPARE macro command. ISRE809 File allocation error - The temporary SuperC delta file could
not be allocated. ExplanationAn allocation error occurred creating the SuperC delta file. System programmer responseInsure that the PDFCUNIT field in the configuration table ISRCONFG points to a valid unit which can allocate a 50 track temporary data set. User responseContact the System Programmer ISRE810 Internal error - Contact your systems developer for the reason
for this error. ExplanationAn internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE811 Label missing - Two labels must be entered to indicate a
range for the 'aaaaaaaa' command. ExplanationTwo labels are required to indicate a range for this command. User responseSpecify two labels for the range and try the command again. ISRE812 Some lines not x'd - Line(s) were not excluded that contained
pending line command(s). ExplanationLines that contained pending line commands were not excluded. User responseExecute the line commands before excluding the lines. ISRE813 Open error - An error occurred while trying to open the PDS. ExplanationAn internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE814 I/O error - I/O error while trying to build the member list. ExplanationAn internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE815 All lines excluded - aaaaaaaa lines were
excluded ExplanationThis is an informational message. ISRE816 Range excluded - aaaaaaaa lines were excluded
in range bbbbbbbb to cccccccc. ExplanationThis is an informational message. ISRE817 No lines excluded - aaaaaaaa lines met
EXCLUDE criteria ExplanationThis is an informational message. ISRE818 BLDL error - I/O error, insufficient virtual storage, or
other BLDL error. ExplanationAn internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE819 No members in data set - The PDS specified contains no members. ExplanationThere are no members in the data set being accessed. User responseSpecify a data set that has members and try the command again. ISRE820 Too many parameters - ON/OFF are the only valid parameters
for the PACK command. ExplanationToo many parameters were specified for the PACK command. User responseSpecify ON or OFF as the parameter for the PACK command and try the command again. ISRE821 Inconsistent parameters - "aaaaaaaa" and
"bbbbbbbb" cannot both be entered with PACK command. ExplanationThe parameters entered for the PACK command are not consistent. User responseEnter either ON or OFF as the parameter for the PACK command and try the command again. ISRE822 Parameter unrecognized - ON/OFF are the only valid parameters
for the PACK command. ExplanationThe parameter specified for the PACK command is invalid. User responseSpecify either ON or OFF as the parameter for the PACK command and try the command again. ISRE823 Invalid parameter - ON/OFF are the only valid parameters
for the PACK command. ExplanationThe parameter specified for the PACK command is invalid. User responseSpecify either ON or OFF as the parameter for the PACK command and try the command again. ISRE824 Required parm missing - NOWARN parameter not accepted without
OFF keyword being specified. ExplanationThe OFF keyword must be specified with the NOWARN parameter. User responseSpecify the OFF keyword with the NOWARN parameter and try the command again. ISRE825 Assignment command error - Assignment type (GET/SET) not
recognized for the PACK command. ExplanationAn internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE826 Required parm missing - WARN parameter not accepted without
OFF keyword being specified. ExplanationThe OFF keyword must be specified with the WARN parameter. User responseSpecify the OFF keyword with the WARN parameter and try the command again. ISRE827 Inconsistent parameters - ON and PROMPT cannot both be specified
for the AUTOSAVE command. ExplanationThe parameters specified for the AUTOSAVE command were not consistent. User responseSpecify either ON or PROMPT as parameters for the AUTOSAVE command and try the command again. ISRE828 Required parm missing - NOPROMPT parameter not accepted without
OFF keyword being specified. ExplanationThe OFF keyword must be specified with the NOPROMPT parameter. User responseSpecify the OFF keyword with the NOPROMPT parameter and try the command again. ISRE829 Data not saved by END - AUTOSAVE OFF NOPROMPT: Data changes
not saved automatically by END command. ExplanationThis is an informational message. ISRE830 aaaaaaaa label invalid - Labels must be
alphabetic characters only. ExplanationThe label aaaaaaaa must be alphabetic characters only. User responseRespecify the label to contain only alphabetic characters. ISRE831 aaaaaaaa label invalid - Labels starting
with ".Z" are reserved for system use. ExplanationThe label name started with the character Z, which is reserved for editor-defined labels. User responseSpecify a valid label name that does not start with Z. ISRE832 aaaaaaaa name invalid - Command name is
greater than 6, the length of the line command area. ExplanationThe line command name used in the PROCESS macro command is greater than six characters. User responseContact the responsible programmer. Programmer responseCorrect the line command name used in the PROCESS macro command. ISRE833 Range name is missing - Process RANGE keyword requires one
line command name to be specified. ExplanationNo line command name was specified with the RANGE keyword in the PROCESS macro command. User responseContact the responsible programmer. Programmer responseSpecify a line command name for the RANGE keyword in the PROCESS macro command. ISRE834 Unrecognized parameter - PROCESS parm is not RANGE or DEST
keyword: PROCESS <DEST> <RANGE cmdname> ExplanationAn unrecognized parameter was entered for the PROCESS macro command. User responseContact the responsible programmer. Programmer responseCorrect the PROCESS macro command to use the RANGE and DEST keywords. ISRE835 Command on invalid line - Place aaaaaaaa line
command in command area associated with a data line. ExplanationThe command is on an invalid line. User responsePlace the line command in a command area that contains a data line. ISRE836 Invalid process request - End user input previously processed.
Specify NOPROCESS on macro command. ExplanationInput was previously processed. User responseContact the responsible programmer. Programmer responseSpecify NOPROCESS on the macro command before using the PROCESS macro command. ISRE837 Missing variable name - Information cannot be returned in
a variable: no variable name found. ExplanationNo variable name was specified in which to return information. User responseSupply a variable name with the command and try again. ISRE838 Member not replaced - The Replace command was not confirmed. ExplanationThe Confirm Replace panel was displayed at the user's request. The user chose not to Replace the member by entering the End command. ISRE839 Member not created - Member already existed. The Create
command was not confirmed. ExplanationThe Confirm Create panel was displayed at the user's request. The user chose not to replace the member by entering the END command. The Confirm Create panel is only displayed if there is a member in the lowest level library with the same name requested by the create command, and if confirm replace was chosen. ISRE840 Too many parameters - A version number is the only valid
parameter for the VERSION command. ExplanationThe VERSION command allows only a version number as a parameter. User responseSpecify only a version number for the VERSION command and try the command again. ISRE841 Parameter unrecognized - A version number is the only valid
parameter for the VERSION command. ExplanationThe parameter specified for the VERSION command is invalid. User responseSpecify a version number as a parameter for the VERSION command and try the command again. ISRE842 Invalid parameter - A version number is the only valid parameter
for the VERSION command. ExplanationThe parameter specified for the VERSION command is invalid. User responseSpecify a version number as the parameter for the VERSION command and try the command again. ISRE843 Required parm missing - A version number parameter is required
for the VERSION command. ExplanationThe version number parameter is required for the VERSION command. User responseSpecify a version number as the parameter for the VERSION command and try the command again. ISRE844 Invalid version number - The specified version number must
be in the range: 1-99. ExplanationThe version number specified for the VERSION command is invalid. User responseSpecify a version number from 1 to 99 for the VERSION command and try the command again. ISRE845 Assignment command error - Assignment type (GET/SET) is unrecognized
for the AUTOSAVE command. ExplanationAn internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRE846 Too many parameters - ON/OFF and PROMPT/NOPROMPT are the
only valid AUTOSAVE parameters. ExplanationToo many parameters were specified for the AUTOSAVE command. User responseSpecify ON or OFF and PROMPT or NOPROMPT for the AUTOSAVE command and try the command again. ISRE847 Inconsistent parameters - "aaaaaaaa" and
"bbbbbbbb" cannot both be specified on the AUTOSAVE
command. ExplanationInconsistent parameters were specified for the AUTOSAVE command. User responseSpecify one but not both of the inconsistent parameters for the AUTOSAVE command and try the command again. ISRE848 Parameter unrecognized - ON/OFF and PROMPT/NOPROMPT are the
only valid AUTOSAVE parameters. ExplanationThe parameter specified for the AUTOSAVE command is not valid. User responseSpecify ON/OFF and PROMPT/NOPROMPT for the AUTOSAVE command and try the command again. ISRE849 Invalid parameter - ON/OFF and PROMPT/NOPROMPT are the only
valid AUTOSAVE parameters. ExplanationThe parameter specified for the AUTOSAVE command is not valid. User responseSpecify ON or OFF and PROMPT or NOPROMPT for the AUTOSAVE command and try the command again. ISRE850 Too many parameters - A modification level number is the
only valid parm for the LEVEL command. ExplanationThe LEVEL command has too many parameters. Only one parameter in the range 0-99 is accepted. User responseIssue the LEVEL command with one parameter in the range 0-99. ISRE851 Invalid modlevel number - A valid specification for LEVEL
is in the range 0-99. ExplanationThe LEVEL command parameter is out of range. It must be in the range 0-99. User responseIssue the LEVEL command with one parameter in the range 0-99. ISRE852 Assignment command error - Assignment type (GET/SET) not
recognized for the LEVEL command. ExplanationThe setting of the modification level or the retrieval of the modification level for assignment to a variable failed. The LEVEL macro command may not have been properly used. User responseContact programmer of the dialog that uses the LEVEL macro command. Programmer responseCheck the syntax of the LEVEL macro command for errors. ISRE853 Invalid parameter - The only valid parameter for the LEVEL
command is a number (0-99). ExplanationThe LEVEL command parameter is invalid. It must be a number in the range 0-99. User responseIssue the LEVEL command with one parameter in the range 0-99. ISRE854 Required parm missing - The LEVEL command requires a numeric
parameter in the range 0-99.
ISRE855 Assignment command error - Assignment type (GET/SET) not
recognized for the VERSION command. ExplanationThe setting of the version number or the retrieval of the version number for assignment to a variable failed. The VERSION macro command may not have been properly used. User responseContact programmer of the dialog that uses the VERSION edit macro. Programmer responseCheck the syntax of the VERSION macro command for errors. ISRE856 Invalid macro command - CTL_LIBRARY is no longer a valid
Edit macro command with the removal of LMF. ExplanationThe Library Management Facility (LMF) has been removed from ISPF. The CTL_LIBRARY Edit macro command supported LMF and has been removed as well. ISRE858 Command not found - The aaaaaaaa program
macro could not be loaded. ExplanationThe load module was not found or the load module was marked not executable. System programmer responseThe load module may be in a library that is not concatenated in the user environment. In this case, the library concatenation for the user may need to be changed in order to find the appropriate library. User responseMake sure the load module name was spelled correctly. Contact the load module programmer if the load module name was spelled correctly. Programmer responseThe load module may need to be relinked if it was marked not executable. The load module may need to be added to the proper library if it was not located by the system. ISRE859 Data set not replaced - The Replace command was not confirmed. ExplanationThe Confirm Replace panel was displayed at the user's request. The user chose not to Replace the data set by entering the End command. ISRE860 Too many parameters - The only valid parameter for the IMACRO
command is a name or NONE. ExplanationMore than one parameter was entered for the IMACRO command. The only valid parameter for the IMACRO command is a name or NONE. User responseReissue the IMACRO command with a name or NONE as the only parameter. Programmer responseExamine the edit macro for an ISREDIT macro command that assigns too many parameters to IMACRO. ISRE861 Assignment command error - Assignment type (GET/SET) not
recognized for the IMACRO command. ExplanationAssignment type (GET/SET) was not recognized for an ISREDIT macro command. The value of IMACRO was being retrieved to a variable (GET) or being assigned a value (SET). System programmer responseExamine the invocation of the edit macro for a possible read (GET) or write (SET) error. User responseContact the responsible programmer. Programmer responseExamine the edit macro for an incorrect ISREDIT macro command that references IMACRO. ISRE862 Invalid parameter - The only valid parameter for the IMACRO
command is a name or NONE. ExplanationThis message is self explanatory. ISRE863 Required parm missing - The IMACRO command requires an initial
macro name as a parameter. ExplanationNo parameter was specified for a macro name. User responseReissue the IMACRO command with a macro name or NONE. Programmer responseExamine the edit macro for an ISREDIT macro command that is not assigning any parameter to IMACRO. ISRE864 Invalid macro name - "aaaaaaaa" specified
for the IMACRO command is an invalid macro name. ExplanationAn invalid macro name was specified. Valid parameters are a valid macro name or NONE. User responseReissue the IMACRO command with a valid macro name or NONE. Programmer responseExamine the edit macro for an ISREDIT macro command that assigns an invalid macro name to IMACRO. ISRE865 Invalid macro name - The length of name "aaaaaaaa"
specified for the IMACRO command is invalid. ExplanationThe number of characters in the macro name for the IMACRO command exceeds the maximum length for a name. User responseReissue the IMACRO command with a macro name of the appropriate length. Programmer responseExamine the edit macro for an ISREDIT macro command that is assigning a macro name of inappropriate length to IMACRO. ISRE866 Imacro name not accepted - A new IMACRO name will not be
accepted while the profile is locked. ExplanationIMACRO command is not permitted when the edit profile is locked. User responseUnlock the profile and issue the IMACRO command again. Contact the responsible programmer if the IMACRO command is in an edit macro and the profile will not unlock. Programmer responseExamine the edit macro. The profile must be unlocked in order to issue the IMACRO command successfully. ISRE867 SETUNDO unavailable - The SETUNDO command has not been enabled
by your system programmer. ExplanationThe SETUNDO command is only available if the function has been enabled by your system programmer. SETUNDO is enabled by way of the PDF configuration table. System programmer responseTo enable the SETUNDO command, change the value UNDOSIZE to a nonzero value in the PDF configuration table. User responseTurn Recovery on to enable UNDO support. ISRE868 Some data not processed - The files are different, but additional
differences may not be shown. Options were selected on the Edit Compare
Settings panel which may cause some data to be ignored during the
comparison. This file was compared to 'aaa(56)'. ExplanationThe COMPARE edit command detected differences.
However options were selected on the Edit Compare Settings Panel
which filtered the input to the compare program. As a result, some
differences may have been ignored during the compare and may not be
highlighted in the editor.
User responseNo action is required unless you are using the COMPARE command to merge changes from another file. If you are using the COMPARE command to merge changes from another file, you may want to deselect all of the "don't process" options on the Edit Compare Settings panel and run the COMPARE command again. To deselect the "don't process" options, type COMPARE with no parameters on the command line and press Enter. ISRE869 Data set not allocated - In a macro the target data set must
be allocated for the aaaaaaaa command ExplanationThe data set name specified is not allocated. User responseSpecify a data set that has been allocated. ISRE870 Too many parameters - The only valid parameter for the RMACRO
command is a name or NONE. ExplanationMore than one parameter was entered for the RMACRO command. The only valid parameter for the RMACRO command is a name or NONE. User responseReissue the RMACRO command with a name or NONE as the only parameter. Programmer responseExamine the edit macro for an ISREDIT macro command that assigns too many parameters to RMACRO. ISRE871 Assignment command error - Assignment type (GET/SET) not
recognized for the RMACRO command. ExplanationAssignment type (GET/SET) is not recognized for an ISREDIT macro command. The value of RMACRO is being retrieved to a variable (GET) or being assigned a value (SET). System programmer responseExamine the invocation of the edit macro for a possible read (GET) or write (SET) error. User responseContact the responsible programmer. Programmer responseExamine the edit macro for an incorrect ISREDIT macro command that references RMACRO. ISRE872 Invalid parameter - The only valid parameter for the RMACRO
command is a name or NONE. ExplanationThis message is self explanatory. ISRE873 Required parm missing - The RMACRO command requires a recovery
macro name as a parameter. ExplanationNo parameter is specified for a recovery macro name or NONE. User responseReissue the RMACRO command with a recovery macro name or NONE. Programmer responseExamine the edit macro for an ISREDIT macro command that is not assigning any parameter to RMACRO. ISRE874 Invalid macro name - "aaaaaaaa" specified
for the RMACRO command is an invalid macro name. ExplanationAn invalid macro name was specified. Valid parameters are either a valid macro name or NONE. User responseReissue the RMACRO command with a valid macro name or NONE. Programmer responseExamine the edit macro for an ISREDIT macro command that assigns an invalid macro name to RMACRO. ISRE875 Invalid macro name - The length of name "aaaaaaaa"
specified for the RMACRO command is invalid. ExplanationThe number of characters in the macro name for the RMACRO command exceeds the maximum length for a name. User responseReissue the RMACRO command with a macro name of the appropriate length. Programmer responseExamine the edit macro for an ISREDIT macro command that is assigning a macro name of inappropriate length to RMACRO. ISRE876 Too many parameters - You may specify one or two labels on
the FLIP command. ExplanationThe FLIP command was issued with more than two labels. User responseReissue the FLIP command with zero, one, or two labels. Programmer responseExamine the edit macro for a FLIP command with more than two labels. ISRE877 Invalid parameter - You may specify one or two labels on
the FLIP command. ExplanationThe FLIP command may be specified with zero, one, or two labels. One of the parameters specified with the FLIP command is not a valid label. User responseReissue the FLIP command with zero, one, or two valid labels. Programmer responseExamine the edit macro for a FLIP command with an invalid label. ISRE878 Member not moved - The Move command was not confirmed. ExplanationThe Confirm Move panel was displayed at the user's request. The user chose not to move the member by entering the END command. The Confirm Move panel is only displayed if there is a member in the lowest level library with the same name requested by the move command, and if confirm move was chosen. ISRE879 Data set not moved - The Move command was not confirmed. ExplanationThe Confirm Move panel was displayed at the user's request. The user chose not to move the data set by entering the END command. The Confirm Move panel is only displayed if confirm move was chosen. ISRE880 Model class error - Too many parameters entered. The correct
format is: MODEL CLASS NAME. ExplanationThe MODEL macro command was issued with too many parameters. The correct syntax is MODEL CLASS NAME. User responseReissue the MODEL command with the correct syntax. ISRE881 Member not found - Model member aaaaaaaa.
was not found in ISPSLIB skeleton library. ExplanationThe name of a member in a skeleton library was not found. The name may be misspelled or the member may not be present in the skeleton library. User responseContact the responsible programmer. Programmer responseCheck the panel member for a misspelled name and the skeleton library for a missing member. Problem determinationThe skeleton member name may be misspelled in the panel member or be missing from the skeleton library. ISRE882 Member selection failed - Error received during selection
panel process to determine a model. ExplanationThe MODEL command was issued with a member name for the message class. Since there is only one model for messages, the concatenation of the class and the specified member name resulted in the error. User responseReissue the MODEL command without specifying a member name. Programmer responseExamine the edit macro for a MODEL command that specifies a member name for the message class. ISRE883 I/O error reading member - Error received during read for
requested model. ExplanationAn I/O error was received during read for the requested model. System programmer responseExamine the model data set for corruption. Use data set recovery techniques if the model data set is not usable. User responseReissue the MODEL command. Contact the system programmer if the error persists. Problem determinationThe model data set may be corrupted. Use standard I/O error problem determination techniques. ISRE884 Model command pending - An A or B line command or a valid
label has not been specified. ExplanationA MODEL command was issued without specifying where to place the model. An A or B line command or a valid label has not been specified. User responseSpecify an A or B line command or a valid label. ISRE885 Model class changed - Model class is now set to "aaaaaaaa". ExplanationThis is an informational message indicating that the model class has been changed. This message may appear after issuing the MODEL CLASS command and selecting a different class. ISRE886 DVPUT returning error - DVPUT to set a variable for model
function fails. ExplanationAn ISPF system error, installation error, or unrecoverable I/O error has occurred. User responseContact your system programmer. ISRE887 DVDEF returning error - When defining variables for model
function fails. ExplanationAn ISPF system error, installation error, or unrecoverable I/O error has occurred. User responseContact your system programmer. ISRE888 DVGET returning error - Attempt to retrieve variable for
model function fails. ExplanationAn ISPF system error, installation error, or unrecoverable I/O error has occurred. User responseContact your system programmer. ISRE889 Invalid model class name - Name is too long; it may contain
a maximum of eight characters. ExplanationA model class name was entered that exceeds 8 characters in length. User responseReissue the MODEL command with a class name of the proper length. Programmer responseExamine the edit macro for "ISREDIT MODEL CLASS name" where "name" is greater than 8 characters in length. ISRE890 Probable macro loop - Macros are nested 255 levels deep.
Check recursive invocations. ExplanationEach macro operates on a separate level. A person at the keyboard always operates at level 0. Macros started by that person operate at level 1. Macros started by macros at level "n" will operate at level "n+1". The limit on the number of levels is 255. User responseContact the responsible programmer. Programmer responseChange the macro or macros to remove repetitive starts of the same macro. A design change is required if there are more than 254 macro starts. Problem determinationThis statement may be added to the macro
(or macros):
ISRE891 aaaaaaaa macro error - aaaaaaaa macro
set a return code of bbbbbbbb ExplanationThe EDIT macro set a return code greater than 11. Return codes greater than 11 are considered error codes. User responseDetermine the cause of the error. Contact the programmer if the error code should be less than 12. Programmer responseThe code may be changed if the return code should be less than 12. ISRE892 Macro command error - PROCESS/NOPROCESS keywords specified
more than once on macro command. ExplanationMultiple PROCESS/NOPROCESS keywords have been recognized on the macro command. User responseContact the responsible programmer. Programmer responseThe edit macro MACRO command must have only one PROCESS/NOPROCESS keyword. Change the MACRO command so that there is only one PROCESS/NOPROCESS keyword. Problem determinationMultiple PROCESS/NOPROCESS keywords are recognized when they are separated by a parameter string. Without a parameter string separation the first keyword will be used and the others will be ignored without an error message. ISRE893 Macro command error - No ending parenthesis found to delimit
macro parameters. ExplanationThe MACRO command parameters are not delimited by an ending parenthesis. User responseContact the responsible programmer. Programmer responseChange the MACRO command in the edit macro so the parameters have an ending parenthesis. ISRE894 aaaaaaaa macro error - Command as entered:
"bbbbbbbb". ExplanationA command in an edit macro ended in error. User responseExamine the parameters (if any) specified for the edit macro. Invalid parameters passed to commands in the edit macro may cause an error. Contact the edit macro programmer for additional assistance. Programmer responseA command in an edit macro ended in error. If the parameters passed to the command are correct then the problem may be with incorrect command syntax, execution of the wrong version of the command, or errors in the command itself. Problem determinationExamine the edit macro for incorrect parameters specified by the user, incorrect command specification in the edit macro, and incorrect version of the command to be executed. ISRE895 aaaaaaaa macro error - Command after an
END or CANCEL or a severe error was not executed. ExplanationAn ISREDIT or ISPEXEC statement follows and END, CANCEL or a severe error, and was not executed. User responseReissue the edit macro after removing the cause of the severe error. Contact the responsible programmer if there was no severe error. Programmer responseIn the situation of no severe error, the edit macro may be changed so that the macro exits after the END or CANCEL. ISRE896 Invalid define request - It is invalid to assign an alias
for a command/macro that is NOP'ed. ExplanationThe DEFINE command may be used to make a name inoperable (NOP). The DEFINE command may not be used to identify a name as an alias of a name that is inoperable (NOP). User responseThe DEFINE command may be used to make inoperable names operable through the use of RESET. The DEFINE command may then be used to assign an alias to an operable name. ISRE897 Model member missing - The model member desired must be specified
on the MODEL macro command. ExplanationThe MODEL macro command requires the name of the model to be copied. User responseContact the responsible programmer. Programmer responseThe edit macro may contain a MODEL macro command that does not specify the name of the model to be copied. The edit macro code may be changed so that the name of a model is specified as part of the MODEL macro command. Problem determinationExamine the edit macro for MODEL commands that do not specify the name of a model. ISRE898 Member not found - Model "aaaaaaaa" was
not found in ISPSLIB skeleton library. ExplanationThe name of the model specified on the MODEL macro command was not found in the ISPSLIB skeleton library. The model may be missing from the library or the model name may be misspelled. User responseContact the responsible programmer. Programmer responseThe edit macro may need to be corrected with a proper spelling of the model name, or the model may need to be added to the ISPSLIB skeleton library. Problem determinationExamine the edit macro for a misspelled model name. If the model name is spelled properly, then the model may need to be added to the ISPSLIB skeleton library. ISRE899 Class name not specified - The class name desired must be
specified on the MODEL macro command. ExplanationThe MODEL macro command class syntax requires specification of a class name. There was no class name specified. User responseContact the responsible programmer. Programmer responseThe edit macro may contain a MODEL command that does not specify a class name as per the macro command class name syntax. Change the macro so a class name is specified on the MODEL CLASS command. Problem determinationExamine the edit macro for a missing class name on the MODEL CLASS command. ISRE900 Invalid IMACRO name - Name must follow member name rules
or start with "!" followed by a valid name ExplanationThe IMACRO command saves the name of an initial macro in the current edit profile. A value of NONE specifies that no macro is to be run at the beginning of each edit session. The name must follow the rules for a member name or start with an exclamation mark ! followed by a valid name. User responseReissue the IMACRO command with NONE or a valid name. Contact the edit macro programmer if the IMACRO command is issued in an edit macro. Programmer responseExamine the edit macro for an IMACRO command with an invalid name. Replace the invalid name with a valid name. ISRE901 Severe error - Unexpected return code from the dialog supplied
read routine. ExplanationAn unexpected return code was received from the dialog supplied read routine. Expected return codes are 0, 8, 16, and 20. System programmer responseThe dialog supplied read routine should be examined for errors. There may be a problem with the data being read. User responseContact your system programmer. ISRE902 aaaaaaaa too large - Insufficient storage
to read in bbbbbbbb at this time. ExplanationAn out of storage situation has been detected. There is insufficient storage for a GETMAIN. System programmer responseExamine the data set or z/OS® UNIX file to see if it is too large for the user environment. A larger region size may solve the problem. User responseThe region size may need to be increased. Contact the system programmer if increased region size does not solve the problem, or if the region size is already at the maximum limit. ISRE903 I/O error reading data - I/O error occurred reading the edit
data. ExplanationAn I/O error with a return code of 16 was encountered. This is an ISPF system error, installation error, or unrecoverable I/O error. System programmer responseInvestigate the cause of the I/O error. User responseContact your system programmer. ISRE904 I/O error reading data - I/O error occurred reading the edit
data. Check data set block sizes. ExplanationAn error occurred while reading the edit data. System programmer responseInvestigate the cause of the I/O error. User responseContact your system programmer. Problem determinationThis should not be a packed data problem as errors from packed data result in a different message. The data set block sizes may be causing the error. ISRE905 Invalid EDIT/VIEW parm - Password is not allowed when DATAID
is specified. ExplanationA password and DATAID are present. A password is not allowed with a DATAID. User responseContact the programmer of the dialog that invokes the EDIT or VIEW service. Programmer responseCorrect the dialog so that a password is not present with a DATAID. ISRE906 Invalid EDIT/VIEW parm - Data set specified is sequential,
but member parm has been coded. ExplanationA member is specified for a sequential data set. This is not correct. User responseContact the programmer of the dialog that invokes the EDIT or VIEW service. Programmer responseCorrect the dialog so that a member is not specified with a sequential data set. ISRE907 EDREC service error - EDREC PROCESS, CANCEL or DEFER issued,
but Recovery is not pending. ExplanationThe dialog is attempting to issue an edit recovery PROCESS, CANCEL, or DEFER without first issuing a query. User responseContact the responsible programmer. Programmer responseThe dialog may be issuing two consecutive edit recovery PROCESS, CANCEL, or DEFER functions. Examine the dialog that invokes the edit service. The dialog code may need to be corrected. ISRE908 EDREC service error - EDREC QUERY or INIT is not allowed
because recovery is pending. ExplanationThe dialog is attempting to perform an edit recovery QUERY or INIT while a recovery is pending. User responseContact the responsible programmer. Programmer responseThe dialog may be issuing two consecutive edit recovery queries. Examine the dialog that invokes the edit service. The dialog code may need to be corrected. ISRE909 Invalid macro name - aaaaaaaa is not a
valid macro name. Must be 1-8 alphanumeric characters. ExplanationThis message is self explanatory. ISRE910 Too many parameters - Too many parameters specified for the
SEEK command. ExplanationThis message is self explanatory. ISRE911 Missing parameter - At least one variable name parameter
required for SEEK_COUNTS command. ExplanationThis message is self explanatory. ISRE912 Invalid specification - 'get' assignment type unrecognized
for the SEEK_COUNTS command. ExplanationThis message is self explanatory. ISRE913 Invalid DEFINE request - RESET was attempted for a name not
currently defined. ExplanationA DEFINE name RESET command was issued for an undefined name. User responseExamine the command syntax for a misspelled name or a name that is not defined. Contact the edit macro programmer if the DEFINE command is in an edit macro. Programmer responseExamine DEFINE name RESET commands for misspelled name or name not previously defined in the edit macro. ISRE914 Parameter not recognized - Check for misspelled keywords
or too many BOUNDS or RANGE parameters. ExplanationThe SEEK macro command in an edit macro was issued with a misspelled keyword or too many BOUNDS or RANGE parameters. User responseContact the responsible programmer. Programmer responseExamine the edit macro for a SEEK macro command that has a misspelled keyword or too many BOUNDS or RANGE parameters. The edit macro code may need to be corrected. Problem determinationCompare the SEEK macro command in the edit macro with the syntax of the SEEK macro command in ISPF Edit and Edit Macros . The keywords or bound and range parameters may be incorrect at run time. ISRE915 Missing parameter - At least one variable name parameter
required for SESSION command. ExplanationThe SESSION assignment statement is missing the required variable name used to return the requested data. User responseCorrect the SESSION assignment statement so that it includes the required variable name. ISRE916 Model data truncated - Model command has detected data in
the model which could not be inserted into the edit data because NUMBER
mode is on. ExplanationModel member contains data in the columns used by sequence numbers in the data currently being edited and number mode is ON. Model command is terminated at the point the problem occurs. System programmer responseEdit the model so that all data is no longer overlaid by sequence numbers. User responseUse NUM OFF command and retry the MODEL command or contact your system programmer if sequence numbers are required. ISRE917 Required string missing - The SEEK command requires specification
of a target string. ExplanationThe SEEK macro command in an edit macro was issued without a search string. User responseContact the responsible programmer. Programmer responseExamine the edit macro for a SEEK macro command that does not have a search string. The edit macro code may need to be corrected. Problem determinationCompare the SEEK macro command in the edit macro with the syntax of the SEEK macro command in ISPF Edit and Edit Macros . The search string for the SEEK command may be null at run time which may also be the cause of the error. ISRE918 Inconsistent parameters - 'aaaaaaaa' and
'bbbbbbbb' cannot both be specified for SEEK command. ExplanationThe SEEK macro command in an edit macro was issued with inconsistent parameters such as LAST and PREV. User responseContact the responsible programmer. Programmer responseExamine the edit macro for a SEEK macro command with inconsistent parameters. The edit macro code may need to be corrected. Problem determinationCompare the SEEK macro command in the edit macro with the syntax of the SEEK macro command in ISPF Edit and Edit Macros . ISRE919 Put string in quotes - Put quotes (' ') around the string
of characters to be displayed. ExplanationThis message is self explanatory. ISRE920 Missing parameter - Variable name parameter required for
BLKSIZE command. ExplanationThis message is self explanatory. ISRE921 Invalid specification - GET assignment type unrecognized
for the BLKSIZE command. ExplanationThis message is self explanatory. ISRE922 Missing parameter - Variable name parameter required for
DATASET command. ExplanationThis message is self explanatory. ISRE923 Invalid specification - GET assignment type unrecognized
for the DATASET command. ExplanationThis message is self explanatory. ISRE924 Label does not exist - The label was deleted before LOCATE
could be performed. ExplanationThis message is self explanatory. ISRE925 Too many parameters - Valid parameters for the SETUNDO command
are ON, OFF, STG, KEEP and REC. ExplanationThe SETUNDO command was entered with too many parameters. User responseReissue the SETUNDO command with a correct parameter. Contact the responsible programmer if the SETUNDO command is in an edit macro. Programmer responseExamine the edit macro for a SETUNDO command with too many parameters. The valid parameters are ON, OFF, STG, KEEP and REC. The edit macro code may require changes to the SETUNDO command invocation. ISRE926 Invalid parameter - ON, OFF, STG, KEEP and REC are the only
valid parameters for SETUNDO. ExplanationThis message is self explanatory. ISRE927 Inconsistent parameters - "aaaaaaaa" and
"bbbbbbbb" cannot both be entered with SETUNDO
command. ExplanationThis message is self explanatory. ISRE928 Parameter unrecognized - Valid parameters for the SETUNDO
command are ON, OFF, STG, KEEP and REC. ExplanationThe SETUNDO command was entered with a parameter that was not recognized. The parameter may be misspelled or invalid. User responseReissue the SETUNDO command with a correct parameter. Contact the edit macro programmer if the SETUNDO command is in an edit macro. Programmer responseExamine the edit macro for a SETUNDO command with an incorrect parameter. The valid parameters are ON, OFF, STG, KEEP and REC. The edit macro code may require changes to the SETUNDO command invocation. ISRE929 Invalid specification - GET assignment type unrecognized
for the SESSION command. ExplanationEither the SESSION assignment statement contains an invalid variable name or a parameter is missing. User responseVerify that the SESSION assignment statement contains no syntax errors or missing parameters. ISRE930 Invalid line number - The relative line number given to the
LINE_STATUS command is invalid. ExplanationThe edit macro command LINE_STATUS 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. Programmer responseCorrect the LINE_STATUS command using the
syntax
Also check to see that the line number you are passing exists in the file. You may want to use the LINENUM command to get the relative line number of the last line (.ZLAST). ISRE931 Invalid specification - GET assignment type unrecognized
for the LINE_STATUS command. ExplanationThe PDF editor encountered an edit macro statement involving the command LINE_STATUS, but the editor could not recognize the statement as a GET type request (a request for PDF to get the value for a current editor setting and place it into a dialog-specified variable). A GET type request is the only valid request type for the LINE_STATUS macro command. User responseContact the responsible programmer. Programmer responseChange the LINE_STATUS command to specify the proper parameters. Refer to ISPF Edit and Edit Macros for editor command syntax. ISRE932 Too many parameters - Too many parameters specified for LINE_STATUS
command. ExplanationThe edit macro command LINE_STATUS was issued with too many parameters. Programmer responseCorrect the LINE_STATUS command using the
syntax
ISRE933 Invalid parameter - Extraneous or invalid parameter was specified
for LINE_STATUS command. ExplanationThe edit macro command LINE_STATUS was issued with invalid parameters. Programmer responseCorrect the LINE_STATUS command using the
syntax
ISRE934 Required parm omitted - Required line number parm omitted
or invalid for the LINE_STATUS command. ExplanationThe edit macro command LINE_STATUS was issued without a line number parameter. Programmer responseCorrect the LINE_STATUS command using the
syntax
ISRE935 Data parm omitted - Required data parameter not specified
for LINE_STATUS command. ExplanationAn invalid LINE command was entered. User responseReview documentation for the LINE command in ISPF Edit and Edit Macros . Programmer responseCorrect the LINE_STATUS command using the
syntax
ISRE936 HILITE unavailable - The HILITE command is not available
in ascii or utf8 edit sessions. ExplanationThis is an informational message. ISRE938 Missing parameter - Variable name parameter required for
VOLUME command. ExplanationThe VOLUME assignment statement is missing the required variable name for the volume of the edit data set. User responseCorrect the VOLUME assignment statement so that it includes the required variable name for the volume of the current edit data set. ISRE939 Invalid specification - GET assignment type unrecognized
for the VOLUME command. ExplanationEither the VOLUME assignment statement contains an invalid variable name or a parameter is missing. User responseVerify that the VOLUME assignment statement contains no syntax errors or missing parameters. ISRE940 Dialog unavailable - The HILITE dialog cannot be started
from an edit macro. ExplanationThe edit command HILITE without operands was specified in an edit macro. The HILITE dialog is not available from edit macros. User responseSpecify at least one operand on the HILITE command in the edit macro. ISRE941 Invalid line number - The relative line number of a line
to be copied cannot be zero. ExplanationA relative line number for a copy operation was specified as zero. The relative line number must be one or greater. User responseRespecify the relative line number(s). ISRE942 HILITE unavailable - The HILITE command is not available
in mixed mode edit sessions. ExplanationThis is an informational message. ISRE943 Option unavailable - The only HILITE services available when
editing data sets with data lengths greater than 255 characters are
FIND and CURSOR. All language sensitive hilighting is disabled. ExplanationThis is an informational message. ISRE944 HILITE unavailable - The HILITE command is not available
when enhanced edit color is not enabled. Enhanced edit color is either
disabled in the PDF configuration table, or the edit panel in use
does not support enhanced edit color or you issued the HILITE disable
command. ExplanationEnhanced edit color is not available because it
is disabled for one of these reasons:
System programmer responseIf you decide to enable enhanced coloring, update the ISPF configuration table. See Planning and Customizing . User responseIf enhanced color is unavailable because the panel you are using is not enabled for it, change the edit panel you are using to enable it. The panel must have a dynamic area called ZDATA, a shadow variable called ZSHADOW, and special attributes in the )ATTR section. See the panel ISREDDE2 which is shipped with ISPF for an example. ISRE945 HILITE unavailable - The HILITE command is not available
when an edit format is used. ExplanationThis is an informational message. ISRE946 Parameters ignored - Enhanced coloring is now enabled. When
enhanced coloring is disabled and the HILITE command is entered with
the RESET, ON, or one of the LOGIC keywords, enhanced coloring is
enabled, but the parameters on the HILITE command are ignored. You
may need to enter the HILITE command again. ExplanationEnhanced coloring was changed from DISABLED to ON by using the HILITE command with the RESET, ON, LOGIC, IFLOGIC, or DOLOGIC keyword. The only effect of the command was to turn highlighting on. The parameters on the HILITE command were ignored and the specific HILITE settings which were in effect before enhanced coloring was disabled are restored. When HILITE is disabled, the editor does not have enough information to fully initialize the enhanced coloring environment. Therefore, it cannot process the parameters on the HILITE command. User responseIf you used any parameters on the HILITE command which change the way the data is highlighted, you may need to enter the HILITE command again. ISRE947 Invalid terminal - Enhanced coloring is not available on
this terminal because the terminal does not support extended highlighting. ExplanationThis is an informational message. ISRE948 HI DISABLE unavailable - Enhanced coloring cannot be disabled
with the current edit panel. Only panels ISREDDE2, ISREDDE3 and FLMEDDE
support the HILITE DISABLE command. ExplanationOnly panels ISREDDE2, ISREDDE3, and FLMEDDE support the HILITE DISABLE command. These are the default panels shipped with ISPF for option 2 and SCLM edit. Extended highlighting cannot be disabled when you are using customized (user) panels that support extended highlighting. ISRE949 HILITE unavailable - The HILITE command is not available
when the editor is used in GUI mode. ExplanationEdit highlighting is not available when you are using the Graphical User Interface (GUI) component of ISPF. ISRE950 Too many parameters - Too many parameters were specified
for "aaaaaaaa" command. ExplanationThis message is self explanatory. ISRE951 Invalid character string - The search string in an IGNORE
command cannot be a null ('') string. ExplanationThis message is self explanatory. ISRE952 Define is not allowed - 'aaaaaaaa' command
name has been disabled. ExplanationThis message is self explanatory. ISRE953 Put string in quotes - Put quotes (' ') around the string
of characters to be ignored. ExplanationThis message is self explanatory. ISRE954 * Top of range reached * - aaaaaaaa bbbbbbbb -
not found from cccccccc to dddddddd..
Press RFIND to continue ExplanationThis message is self explanatory. ISRE955 *** Bottom of range *** - aaaaaaaa bbbbbbbb -
not found from cccccccc to dddddddd..
Press RFIND to continue. ExplanationThis message is self explanatory. ISRE956 No lines searched - No aaaaaaaa lines
from bbbbbbbb-cccccccc were
found for the ignore command to search. ExplanationThis message is self explanatory. ISRE957 No aaaaaaaa bbbbbbbb ignored
- aaaaaaaa bbbbbbbb - not found
on any cccccccc lines from dddddddd to eeeeeeee ExplanationThis message is self explanatory. ISRE958 Invalid left boundary - aaaaaaaa(left
bound) + bbbbbbbb(string size) greater than cccccccc(LRECL) ExplanationThis message is self explanatory. ISRE959 Invalid column range - The aaaaaaaa column
range attempts a search beyond the last data column. ExplanationThis message is self explanatory. ISRE960 Disabled command - 'aaaaaaaa' command
name has been disabled. ExplanationThis message is self explanatory. ISRE961 Enter character string - A character string for ignore has
not been entered (so * is invalid). ExplanationThis message is self explanatory. ISRE962 No lines searched - No aaaaaaaa lines
were found for the ignore command to search. ExplanationThis message is self explanatory. ISRE963 Invalid character - Invalid special character for a picture
(P'xxx') string. ExplanationThis message is self explanatory. ISRE964 No aaaaaaaa bbbbbbbb found
- aaaaaaaa bbbbbbbb - not found
on any cccccccc lines (cols dddddddd to eeeeeeee). ExplanationThis message is self explanatory. ISRE965 *Bottom of data reached* - aaaaaaaa bbbbbbbb -
not found. Press RFIND key to continue from top. ExplanationThis message is self explanatory. ISRE966 * top of data reached * - aaaaaaaa bbbbbbbb -
not found. Press RFIND key to continue from bottom. ExplanationThis message is self explanatory. ISRE967 Invalid parameters - The string will not fit between the
specified columns. ExplanationThis message is self explanatory. ISRE968 Invalid hex string - The hex string must have an even number
of hex digits. ExplanationThis message is self explanatory. ISRE969 Invalid hex string - The hex string must contain only hex
digits (0-9,A-F). ExplanationThis message is self explanatory. ISRE970 Read-only member - You do not have update authority to the
PDSE you selected. Use the View function to access the member in
an editor environment. ExplanationYou do not have update authority to the PDSE you selected. Edit cannot be used to access the member. User responseUse the View function to access the member. ISRE971 Command not supported - aaaaaaaa command
not supported by the dialog supplied command routine. ExplanationThe Edit Interface (EDIF) service and View Interface (VIIF) service use a dialog-supplied command routine to process the MOVE, COPY, CREATE (EDIF only), REPLACE (EDIF only), EDIT (EDIF only) and VIEW (VIIF only) primary commands. The command routine considers the command you entered invalid and set the return code to 12. This message is issued as a default when one is not set by the routine. User responseEnter one of the commands supported by the dialog. Contact the responsible programmer for a list of supported commands. Programmer responseProvide the user with a list of supported commands, and update the command routine to set a more specific error message. ISRE972 Severe error - Severe error occurred in the dialog supplied
command routine. ExplanationA severe error occurred in the command routine specified on an Edit Interface (EDIF) service or View Interface (VIIF) service call made by the dialog. The routine set a return code of 20. This message is issued as the default when an error message was not set by the routine. User responseContact the responsible programmer. Programmer responseProvide the user with an explanation and response for the error condition, and update the command routine to set a more specific error message. ISRE973 Severe error - Unexpected return code from the dialog supplied
command routine. ExplanationThe command routine specified on an Edit Interface (EDIF) or View Interface (VIIF) service call made by the dialog set an unexpected return code. The supported return codes for the command routine are 0, 4, 12, and 20. User responseContact the responsible programmer. Programmer responseUpdate the command routine to use one of the supported return codes. Provide the user with an explanation and response to the error condition. ISRE974 Severe error - Severe error occurred in the dialog supplied
read routine. ExplanationA severe error occurred in the read routine specified on an Edit Interface (EDIF) or View Interface (VIIF) service call. A return code of 20 was passed back by the routine. This message is issued as the default because an error message was not set by the routine. User responseContact the responsible programmer. Programmer responseProvide the user with an explanation and response for the error condition, and update the read routine to set a more specific error message. ISRE975 HILITE unavailable - The HILITE command was issued from an
initial macro, but the edit panel being used does not support highlighting. ExplanationAn edit initial macro issued the HILITE command
to enable edit color highlighting, but the panel being used for edit
can not support edit highlighting for one of these reasons:
User responseIf edit highlighting is desired, refer to ISPF Planning and Customizing for an explanation of customizing edit panels. A set of ISPF edit panels are shipped that support highlighting and these panels may be used as the basis for modification. ISRE976 Severe error - Unexpected return code from the dialog supplied
write routine. ExplanationThe write routine specified on an Edit Interface (EDIF) service call made by the dialog set an unexpected return code. The supported return codes for the write routine are 0, 16, and 20. User responseContact the responsible programmer. Programmer responseUpdate the write routine so that it uses one of the supported return codes. Provide the user with an explanation and response to the error condition. ISRE977 Severe error - Severe error occurred in the dialog supplied
write routine. ExplanationA severe error occurred in the write routine specified on an Edit Interface (EDIF) service call. A return code of 20 was passed back by the routine. This message is issued as the default because an error message was not set by the routine. User responseContact the responsible programmer. Programmer responseProvide the user with an explanation and response for the error condition, and update the write routine to set a more specific error message. ISRE978 I/O error writing data - I/O error occurred writing the edit
data. ExplanationAn output error occurred in the write routine specified on an Edit Interface (EDIF) service call. A return code of 16 was set by the routine. This message is issued as the default because an error message was not set by the routine. User responseContact the responsible programmer. Programmer responseProvide the user with an explanation and response for the error condition, and update the write routine to set a more specific error message. ISRE979 Member name not allowed - A member name cannot be specified
when editing data with the EDIF or VIIF service. ExplanationThe dialog is using the Edit Interface (EDIF) or View Interface (VIIF) service to edit or view data. A member name cannot be specified when using the EDIT, VIEW, or BROWSE primary command from an EDIF or VIIF session. User responseReenter the EDIT, VIEW, or BROWSE command without specifying a member name. ISRE980 Invalid LOCATE range - Specify two valid aaaaaaaa.s
to indicate search range for LOCATE command. ExplanationTwo valid labels must be used to specify the range on the generic form of the LOCATE primary edit command. Either relative line numbers or labels may be used to specify the range on the generic form of the LOCATE Edit macro command. Either only one range parameter was specified, or one or both of the parameters entered were not valid labels or line numbers. User responseIf you are using the LOCATE primary command, reenter the command using two valid labels to define the group of lines to be searched. If you are using an Edit macro, contact the responsible programmer. Programmer responseUpdate the LOCATE macro command so that it uses either two valid labels or two valid line numbers to specify the range. ISRE981 Invalid line number - Line number aaaaaaaa does
not exist. Invalid range for LOCATE. ExplanationOne or both of the line numbers used to specify a range on the generic form of the LOCATE Edit macro command are invalid. User responseContact the responsible programmer. Programmer responseUpdate the LOCATE macro command in the Edit macro so that it uses two valid line numbers to specify the range of lines to be searched. ISRE982 Invalid LOCATE syntax - A range is only valid with a keyword:
X/ERR/CHG/SPECIAL/CMD/LABEL. ExplanationA range is only valid on the generic form of the LOCATE primary and macro commands. This command is used to locate a particular kind of line. A range was specified without specifying the kind of line to be searched for. User responseIf you are using the LOCATE primary command, reenter the command, specifying the kind of line to be located. If you are using an Edit macro, contact the responsible programmer. Programmer responseUpdate the LOCATE macro command so that it includes the kind of line to be located. ISRE983 No records to LOCATE - File is empty. LOCATE cannot position
display to a record in the file. ExplanationThis is an informational message. An attempt is being made to locate a line in an empty file. ISRE984 Command name missing - BUILTIN must be followed by a valid
edit command name. ExplanationThe BUILTIN command was entered without specifying the name of the command you wish to execute. User responseReenter the command with the Edit command name specified. ISRE985 Invalid line pointer - LPTR not numeric or label in syntax
"ISREDIT (varname) = aaaaaaaa LPTR". ExplanationAn assignment statement of the form shown requires that the line pointer be either a valid label or line number. The line pointer used was invalid. User responseContact the responsible programmer. Programmer responseUpdate the assignment statement in the Edit macro to specify a valid label or line number. ISRE986 Invalid line pointer - LPTR not numeric or label in syntax
"ISREDIT aaaaaaaa LPTR = value". ExplanationAn assignment statement of the form shown requires that the line pointer be either a valid label or line number. The line pointer used was invalid. User responseContact the responsible programmer. Programmer responseUpdate the assignment statement in the Edit macro to specify a valid label or line number. ISRE987 Macro/text mode invalid - Macros cannot be executed when
in text entry mode ExplanationAn Edit macro cannot be executed when you are in text entry mode. User responseComplete the text entry before invoking the macro. ISRE988 Command string too long - Exceeds maximum length of 512 bytes
after variable substitution. ExplanationAn Edit macro command resolved to more than 512 bytes after variable substitution. User responseContact the responsible programmer. Programmer responseRework the macro command so that it resolves to a length less than 512 bytes after variable substitution. ISRE989 Var substitution error - Severe error while resolving symbolic
variables in ISREDIT statement. ExplanationOne of the variables used in an Edit macro command cannot be resolved. User responseContact the responsible programmer. Programmer responseEnsure that values are being assigned correctly to all variables used in your Edit macro commands. ISRE990 -CAUTION- Profile changed to STATS OFF (from STATS ON) because ExplanationThis message is self explanatory. ISRE991 ISPF statistics cannot be collected for EDIF service data
sets. ExplanationThis message is self explanatory. ISRE992 -CAUTION- Profile changed to PACK OFF (from PACK ON) because ExplanationThis message is self explanatory. ISRE993 PACK ON is ignored by EDIF service. ExplanationThis message is self explanatory. ISRE994 Inconsistent parameters - Inconsistent keyword parameters
specified for the RESET command. ExplanationThis message is self explanatory. ISRE995 -CAUTION- Saving this member will invalidate the SCLM accounting ExplanationThis message is self explanatory. ISRE996 information. Refer to the edit tutorial for further details. ExplanationThis message is self explanatory. ISRE997 Invalid reg expression - The regular expression failed to
compile. ExplanationISPF invokes the C function REGCOMP to compile the regular expression. In this instance the compile failed. User responseChange the FIND command to specify a valid regular expression or a valid FIND string. ISRE998 SCLM warning - The member being edited may belong to an SCLM
controlled project. ExplanationThe member being edited may belong to an SCLM controlled project. If so, editing the member outside of SCLM will invalidate the member's accounting information. User responseVerify that the member does not belong to an SCLM controlled project before saving any changes. ISRE999 Refer to the ISPF edit tutorial for further details. ExplanationThis message is self explanatory. ISREI001 Missing record format - Specify the record format F or V
for EDIF. ExplanationThe required record format parameter for the EDIF is not specified. User responseContact the responsible programmer. Programmer responseSpecify either F or V for the record format parameter for the EDIF service. ISREI002 Missing record length - Specify a record length greater than
9 and less than 32761 for fixed record length data sets and less than
32757 for variable length data sets. ExplanationThe required record length parameter for the EDIF service is not specified. User responseContact the responsible programmer. Programmer responseSpecify a record length greater than 9 and less than 32761 for fixed record length data sets and less than 32757 for variable length data sets. ISREI003 Missing profile name - Specify the profile name for EDIF. ExplanationThe required profile name parameter for the EDIF service is not specified. User responseContact the responsible programmer. Programmer responseSpecify the profile name for the EDIF service. ISREI004 Invalid aaaaaaaa name - The name must
be 1 to 8 alphanumeric characters starting with an alphabetic character. ExplanationAn invalid format name is specified for the EDIF service. User responseContact the responsible programmer. Programmer responseSpecify a format name with 1 to 8 alphanumeric characters starting with an alphabetic character for the EDIF service. ISREI005 Invalid mixed mode - Specify either YES or NO for the mixed
mode parameter. ExplanationAn invalid mixed mode is specified for the EDIF service. User responseContact the responsible programmer. Programmer responseSpecify either YES or NO for the mixed mode parameter for the EDIF service. ISREI006 Invalid record format - Specify either F or V for the record
format parameter. ExplanationAn invalid record format is specified for the EDIF service. User responseContact the responsible programmer. Programmer responseSpecify either F or V for the record format parameter for the EDIF service. ISREI007 Invalid edit length - The value of data to be edited must
have a length between 10 and 32760. ExplanationAn invalid edit length is specified for the EDIF service. User responseContact the responsible programmer. Programmer responseSpecify the edit length with a value between 10 and 32760 for the EDIF service. ISREI008 aaaaaaaa name not allowed - aaaaaaaa name
not allowed when processing Edit Recovery. Explanationaaaaaaaa name is specified for the EDIF service. This is not allowed when processing Edit Recovery. User responseContact the responsible programmer. Programmer responseBlank out the aaaaaaaa name from the EDIREC service. ISREI009 Mixed mode not allowed - Mixed mode not allowed when processing
Edit Recovery. ExplanationMixed mode is specified for the EDIF service. This is not allowed when processing edit recovery. User responseContact the responsible programmer. Programmer responseBlank out mixed mode from the EDIREC service. ISREI010 Edit length not allowed - Data to be edited length not allowed
when processing Edit Recovery. ExplanationEdit length is specified for the EDIF service. This is not allowed when processing edit recovery. User responseContact the responsible programmer. Programmer responseBlank out the edit length from the EDIREC service. ISREI011 Invalid recovery option - Specify either YES or NO for the
recovery option. ExplanationAn invalid recovery option is specified for the EDIF service User responseContact the responsible programmer. Programmer responseSpecify either YES or NO for the recovery option. ISREI012 Invalid edit length - The edit length must be less than or
equal to the record length. ExplanationAn invalid edit length is specified for the EDIF service. User responseContact the responsible programmer. Programmer responseSpecify an edit length less than or equal to the record length. ISREI013 Conflicting options used - The edit length and the format
are mutually exclusive. ExplanationConflicting options are specified for the EDIF service. The edit length and the format cannot be used simultaneously. User responseContact the responsible programmer. Programmer responseBlank out one of the conflicting options. ISREI020 Invalid EDIREC option - Only one of these options is allowed
: QUERY, CANCEL, DEFER or INIT. ExplanationAn invalid option is specified for the EDIREC service. User responseContact the responsible programmer. Programmer responseSpecify one of the allowed options (QUERY, CANCEL, DEFER, or INIT) for the EDIREC service. ISREI021 Invalid EDIREC parameter - The COMMAND parameter may only
be specified with the INIT option. ExplanationAn invalid parameter is specified for the EDIREC service. The COMMAND parameter may only be specified with the INIT option. User responseContact the responsible programmer. Programmer responseEither correct the option to INIT or blank out the COMMAND parameter out. ISREI022 EDIREC service error - EDIREC CANCEL or DEFER issued, but
recovery is not pending. ExplanationThe CANCEL or DEFER option is specified for the EDIREC service, but recovery is not pending. User responseContact the responsible programmer. Programmer responseUse the QUERY option for the EDIREC service to scan the EDIF recovery table for an entry containing a recovery pending condition. ISREI023 EDIREC service error - EDIREC QUERY or INIT is not allowed
because recovery is pending. ExplanationThe QUERY or INIT option for the EDIREC service is not allowed when recovery is pending. User responseContact the responsible programmer. Programmer responseInvoke the EDIF service with recovery-request = YES to recover the data, or invoke the EDIREC service with the CANCEL or DEFER options to dispose of the pending recovery condition. ISREI024 Invalid CANCEL request - EDIREC CANCEL request issued before
query for recovery pending. ExplanationAn invalid CANCEL request is issued for the EDIREC service before the query for recovery pending. User responseContact the responsible programmer. Programmer responseUse the QUERY option for the EDIREC service before issuing a CANCEL request to scan the EDIF recovery table for an entry containing a recovery pending condition. ISREI025 Data in use - Data is being updated by another user or on
other logical screen. ExplanationThe data set requested is being updated by another user or by you on another logical screen. User responseCheck the data set name, find out if another user is using the data set, or release the data set on another logical screen. ISREI026 Recovery is not pending - The edit recovery cannot proceed
when recovery is not pending. ExplanationAn edit recovery is requested while recovery is not pending. User responseContact the responsible programmer. Programmer responseCorrect the recovery-request option for the EDIF service. ISREV000 Browse substituted - Browse was substituted for View or Edit,
since not enough storage was available. ExplanationThis is an informational message. There was not enough storage available for the VIEW or EDIT command to process correctly. Therefore Browse was substituted. ISREV001 Browse substituted - Browse was substituted for View or Edit,
since neither data sets with a record length less than 10 nor data
sets with RECFM=U can be Viewed or Edited. ExplanationThis is an informational message. You can only edit or view data that has certain record formats and record lengths. If Edit cannot process the data, Browse is substituted. ISREV002 Return ignored - The return command was preempted to allow
the View Warning panel to display. ExplanationThis is an informational message. Changes were made from within a view session. In order to inform users that the changes will not be saved, the RETURN command has been preempted. ISREV003 Browse substituted - Browse was substituted for View or Edit
because the amount of storage required to edit or view the data set
exceeded the maximum value allowed by your ISPF system configuration
or your editor settings (aaaaaaaa.Kb). You can
use the EDITSET command to change this limit. However, the limit
you set in the editor settings panel cannot be used to increase limits
set in the ISPF configuration table. ExplanationThe amount of storage required to read in the data to be edited or viewed exceeds the amount allowed by the ISPF configuration table or the editor settings. When the amount of storage needed to edit a data set exceeds the system defined limits, browse is substituted for edit or view. You can change your editor settings by using the EDITSET command from within an edit session. The value you set in the editor settings panel will not permit you to use more storage for edit or view than the ISPF configuration table allows. System programmer responseTo increase the amount of storage allowed for the initial loading of data into edit or view, modify the value of EDITSTOR in the ISPF configuration table. User responseIf you need to have this value increased, contact your system programmer. ISREV004 VSAM editor rc = aaaaaaaa. - A VSAM editor
ended with return code aaaaaaaa.. It was substituted
for Edit because of configuration table settings. ExplanationIf you try to edit a VSAM data set and a VSAM editor has been specified in the configuration table, the VSAM editor is automatically invoked by ISPF. ISREV005 VSAM browse rc = aaaaaaaa. - A VSAM browser
ended with return code aaaaaaaa.. It was substituted
for Browse because of configuration table settings. ExplanationIf you try to browse a VSAM data set and a VSAM browser has been specified in the configuration table, the VSAM browser is automatically invoked by ISPF. ISREV006 VSAM View rc = aaaaaaaa.. - A VSAM viewer
ended with return code aaaaaaaa.. It was substituted
for View because of configuration table settings. ExplanationIf you try to view a VSAM data set and a VSAM viewer has been specified in the configuration table, the VSAM viewer is automatically invoked by ISPF. ISREV007 VSAM rc = aaaaaaaa. - ISPF attempted
to invoke a VSAM processor on bbbbbbbb.. The VSAM
editor, viewer, or browser exited with return code aaaaaaaa.. ExplanationIf you try to edit, view, or browse a VSAM data set, ISPF looks at the configuration table to determine if there is a VSAM editor, viewer, or browser requested. If so, it is automatically invoked by ISPF. The return code variable is the value returned by the processor, or the return code for the select service. System programmer responseInstall the VSAM processor on your system, or change the configuration table values to correctly invoke the VSAM processor. ISREV008 VSAM processing unavail. - aaaaaaaa is
a VSAM data set. An attempt was made to invoke a VSAM editor, viewer,
or browser, but it is not allowed due to configuration table settings. ExplanationIf you try to edit, view, or browse a VSAM data set, ISPF looks at the configuration table to determine if the VSAM data set is allowed to be processed. System programmer responseDetermine if this user should be allowed to change this data set. If so, update the configuration table. ISREV009 Config. table error - The list of data sets to disallow
for VSAM processing has an invalid data set name pattern. ExplanationThe configuration table list of data set names has a data set name or pattern that is not allowed. Possible reasons are that the qualifier is more than 8 characters, the qualifier is less than 1 character, and there are invalid characters. System programmer responseUpdate the configuration table to have valid data set name or pattern. ISREV010 Session not canceled - The Cancel command was not confirmed. ExplanationThis is an informational message. The Confirm Cancel panel was displayed at the user's request. The user chose not to cancel the edit session by entering the END command. ISREV011 Data changes cannot be saved in a View session. Use Edit
if you want to be able to save your changes. Using the REPLACE command
to write data from a VIEW session can overwrite changes which were
made to the data set after the VIEW session began because VIEW does
not provide ENQ protection at the beginning of the VIEW session. ExplanationThis is an informational message. The user is in a View session but has changed data. The SAVE command is unavailable in View. If the changes are intended to be saved then Edit should be used. View does not ENQ the data set or member during the session. Therefore, the file may be changed by another user or on another split screen after the view session starts. If the data is saved using the REPLACE command from within VIEW, changes made to the data set after the VIEW session began will be overwritten. ISREV012 ISPF/VSAM error - The ISPF Configuration Table indicates
that VSAM data set restrictions are in place, but the ISPF VSAM Restriction
module (ISPCFIGV) could not be found. ExplanationWhen restricting VSAM processing through the ISPF Configuration Table, The ISPF Configuration Table Utility creates a load module called ISPCFIGV which contains the restriction information. The ISPF Configuration Table currently in use indicates that VSAM restrictions are present, but load module ISPCFIGV cannot be found. System programmer responseModule ISPCFIGV may not have been moved into a library in the ISPF search sequence, or may have been renamed or deleted. The module can be recreated if necessary through the ISPF Configuration Table utility and must be reside in a library in the ISPF search sequence. User responseContact your system programmer. ISREV013 View substituted - View was substituted for Edit, since the
file does not have permissions allowing you to update the file. ExplanationThe permissions defined for this z/OS UNIX file do not provide you with WRITE permission to the file. View has been substituted for Edit to allow you to look at the data in the file, but not modify it. ISRF000 aaaaaaaa - to bbbbbbbb..cccccccc..OBJ(dddddddd) ExplanationThis is an informational message. The short message identifies the foreground compiler language. The long message identifies the ISPF library member into which the compiled output object code is stored. ISRF001 aaaaaaaa - to bbbbbbbb..OBJ(cccccccc) ExplanationThis is an informational message. The short message identifies the foreground compiler language. The long message identifies the partitioned data set member into which the compiled output object code is stored. ISRF002 aaaaaaaa - to bbbbbbbb..OBJ ExplanationThis is an informational message. The short message identifies the foreground compiler language. The long message identifies the sequential data set into which the compiled output object code is stored. ISRF003 aaaaaaaa - of bbbbbbbb..cccccccc.(dddddddd) ExplanationThis is an informational message. The short message identifies a FORTRAN interactive debug session. The long message identifies the partitioned data set against which the FORTRAN interactive debug session is run. ISRF004 aaaaaaaa - of bbbbbbbb..cccccccc ExplanationThis is an informational message. The short message identifies a FORTRAN interactive debug session. The long message identifies the sequential data set against which the FORTRAN interactive debug session is run. ISRF005 aaaaaaaa - to bbbbbbbb..cccccccc..LOAD(dddddddd) ExplanationThis is an informational message. The short message identifies a foreground linkage edit or bind. The long message identifies the ISPF load library member into which the linkage editor or binder output is stored. ISRF006 aaaaaaaa - to bbbbbbbb..LOAD(cccccccc) ExplanationThis is an informational message. The short message identifies a foreground linkage edit or bind. The long message identifies the other partitioned load data set member into which the linkage editor or binder output is stored. ISRF007 aaaaaaaa - of bbbbbbbb..LOAD(cccccccc) ExplanationThis is an informational message. The short message identifies a COBOL interactive debug session. The long message identifies the partitioned data set against which the COBOL interactive debug session is run. ISRF009 aaaaaaaa - to bbbbbbbb ExplanationThis is an informational message. The short message identifies the foreground script language. The long message identifies the data set into which the scripted output is stored. ISRF010 VDEFINE error RC=aaaaaaaa - VDEFINE service
return code was aaaaaaaa. ExplanationA severe internal error has occurred. An unexpected return code was received from the VDEFINE service. System programmer responseContact IBM support. User responseContact your system programmer. ISRF011 DISPLAY severe error - DISPLAY service severe error occurred. ExplanationA severe internal error has occurred. An unexpected returned code was received from the DISPLAY service. System programmer responseContact IBM support. User responseContact your system programmer. ISRF012 Duplicate format "aaaaaaaa" - Format name
"aaaaaaaa" already exists. ExplanationThe format name specified, aaaaaaaa, already exists in the format table. User responseCorrect the format name. ISRF013 "aaaaaaaa" does not exist - Format name
"aaaaaaaa" does not exist. ExplanationThe format name specified, aaaaaaaa, does not exist in the format table. ISRF014 Table service error - Table service severe error occurred. ExplanationA severe internal error has occurred. An unexpected return code was received from a table service. System programmer responseContact IBM support. User responseContact your system programmer. ISRF015 TBDISPL error RC=aaaaaaaa - Table display
service return code was aaaaaaaa. ExplanationA severe internal error has occurred. An unexpected return code was received from the table display service. System programmer responseContact IBM support. User responseContact your system programmer. ISRF016 Need field definition - At least one field definition is
required. ExplanationAt least one field definition is required in a format definition. User responseEnter at least one field definition. ISRF017 Field overlap - A field is overlapped with other field. ExplanationOne field definition is overlapped with another field definition. User responseCorrect the overlapping field definition. ISRF018 Operation canceled - The requested function was canceled. ExplanationThis is an informational message. The requested function was canceled. ISRF019 Normal completion - Requested function successfully completed. ExplanationThis is an informational message. The requested function was completed successfully. ISRF020 Field length error - Zero length field is defined. ExplanationAn invalid field length of zero is specified. User responseSpecify a field length between 1 and 71. ISRF021 Odd length DBCS field - Odd length DBCS field is defined. ExplanationAn odd field length is specified. User responseSpecify an even number for the DBCS field length. ISRF022 Invalid command - aaaaaaaa is an invalid
command. ExplanationAn invalid format selection list command is entered. User responseCorrect the invalid format selection list command. ISRF023 Too many parameters - Too many parameters are specified in
the command area. ExplanationToo many parameters are specified in the command area. User responseBlank out the extra parameters. ISRF024 Invalid parameter - Invalid parameter is specified in the
command area. ExplanationAn invalid parameter is specified for the format selection list command. User responseCorrect the invalid parameter. ISRF025 "aaaaaaaa" does not exist - From format
name "aaaaaaaa" does not exist. ExplanationThe FROM format specified, aaaaaaaa, for the copy operation in the Format Specification utility does not exist. User responseCorrect the FROM format name. ISRF026 Format name missing - This command requires a format name. ExplanationThe FROM format name for the copy operation in the Format Specification utility is missing. ISRF027 Duplicate name - Same format in same TABLE(ISRFORM) is specified
for copy. ExplanationThe same format in the same format table is specified for copy. User responseCorrect the format names. ISRF028 "*" is invalid - "*" cannot be specified when the From table
is ISRFORM. ExplanationAn asterisk ("*") cannot be specified when the FROM table is ISRFORM. User responseSpecify a valid FROM format name, or specify a FROM table name other than ISRFORM. ISRF029 Duplicate format name - Format name specified already exists. ExplanationThe format name specified already exists. User responseCorrect the format name. ISRF030 RECFM must be fixed - Variable length records may not be
used for the formatted file. ExplanationVariable RECFM formatted data sets are not supported. User responseSpecify a fixed RECFM formatted data set or blank out the format name. ISRF031 No format table - Format table ISRFORM does not exist. ExplanationA format name is specified, but the format table does not exist. User responseUse the Format Specification utility (option 3.11) to add the new format. ISRF032 Format table is in use - Format table is in use by another
user or by you. ExplanationThe format table is in use by another user or by you on another logical screen. User responseFind out if another user is using the format table, or release the format table on another logical screen. ISRF033 Library is not allocated - The table library is not allocated. ExplanationThe table library for ISPF is not allocated. User responseRefer to the Program Directory for details on allocating the table library for ISPF. ISRF034 Table service error - Severe table service error occurred. ExplanationA severe table service error has occurred. The table data set may be corrupted. User responseContact the responsible programmer. Programmer responseCheck the integrity of the table data set. Reallocate or restore from a backup if the table data set is corrupted. Otherwise, contact IBM support. ISRF035 Format not found - The specified format does not exist. ExplanationThe specified format does not exist in the format table. User responseContact the responsible programmer. Programmer responseCorrect the spelling of the format name, or add the new format using the Format Specification utility (option 3.11). ISRF036 Invalid format - The maximum column position in format exceeds
record length. ExplanationThe maximum column position in the format exceeds the record length of the data set. User responseContact the responsible programmer. Programmer responseUse the Format Specification utility (option 3.11) to update the format so that the maximum column position in the format does not exceed the record length of the data set. ISRF037 LRECL limit exceeded - LRECL plus formatted attribute bytes
exceeds edit/browse lrecl limit. ExplanationThe record length of the data set plus the formatted attribute bytes exceeds the Edit or Browse record length limit. User responseContact the responsible programmer. Programmer responseDivide the format into two smaller formats and Edit or Browse the data set in two steps. ISRF038 No formats found - No format table entries were found to
process. ExplanationNo format table entries were found to process. User responseUse option A to add a new format. ISRF040 Table does not exist - From table "aaaaaaaa"
does not exist. ExplanationThe FROM table aaaaaaaa specified for the copy operation in the Format Specification utility does not exist. User responseCorrect the FROM table name. ISRF041 Table is in use - From table "aaaaaaaa"
is in use. ExplanationThe FROM table aaaaaaaa specified for the copy operation in the Format Specification utility is in use by another user or by you on another logical screen. User responseFind out if another user is using the table, or release the table on another logical screen. ISRF042 Table service error - Severe table service error occurred
with from table. ExplanationA severe table service error has occurred with the FROM table. The FROM table may be corrupted. User responseContact the responsible programmer. Programmer responseCheck the integrity of the FROM table. Reallocate or restore from a backup if the table is corrupted. Otherwise, contact IBM support. ISRF043 Invalid selection code - Valid codes are: S (select), U (update),
R (rename), or D (delete). ExplanationAn invalid selection code is specified. User responseEnter one of the valid selection codes (S, U, R, or D) for the format selection list. ISRF044 Invalid selection code - Valid code is: S (select). ExplanationAn invalid selection code is specified. User responseEnter the valid selection code (S) for the copy format selection list. ISRF900 Function ended RC=X'aaaa' - The selected
function completed with return code of X'aaaa.'. ExplanationThis is an informational message. The selected foreground function is complete with a return code of aaaa hex. ISRF901 ISRLEMX ended RC=aaaa - Member expansion
completed with return code of aaaa. ExplanationThe PDF Member Expansion routine (ISRLEMX) failed
with a return code of aaaa. The ISRLEMX return
codes are:
User responseRefer to z/OS ISPF Dialog Developer's Guide and Reference and ISPF Planning and Customizing for further information on the ISRLEMX routine. ISRF902 No list file found - Unable to locate list file for aaaaaaaa or
the file was empty. ExplanationThis is an informational message. The processing (indicated by variable aaaaaaaa) is complete, but the expected listing data set was not found. ISRF903 Invalid ZSEL variable - The ZSEL panel variable must start
with CMD or PGM. ExplanationThe PDF foreground processor (ISRFPR) is invoked passing the name of a panel to display. The )PROC section of this panel must set variable &ZSEL to an CMD(...) or PGM(...) string that PDF can pass to the ISPF SELECT service. A ZSEL string was encountered that does not start with CMD or PGM. User responseContact the responsible programmer. Programmer responseCorrect the ZSEL string and retry the function. ISRF904 Nonzero return code - The selected function terminated with
return code of X'aaaa.'. ExplanationThis is an informational message. The selected foreground function is complete with a return code of aaaa hex. If aaaa is X'63' this indicates a clist error, probably caused by entering an arithmetic operator (*, /, +, -, etc.) in one of the panel input fields. Any other return code is the return code returned by the selected language processor. ISRF905 Invalid organization - Only partitioned and physical sequential
data sets processed. ExplanationThe PDF foreground option was invoked specifying a data set that was other than partitioned or sequential. User responseChange the input data set to one that is partitioned or sequential and retry. ISRF906 Invalid organization - Only partitioned data sets processed. ExplanationThe PDF foreground Binder/Linkage Editor and VS COBOL II Interactive Debug options only support partitioned data sets as input. User responseChange the input data set to one that is partitioned and retry. ISRF907 Processor failed, RC=20 - The aaaaaaaa language
processor ended with a return code of 20, possibly indicating that
it could not be found by ISPF. ExplanationThe PDF foreground processor attempted to invoke the language processor you requested, but the ISPF SELECT service returned a return code 20. This could be a return code 20 from the processor, or it could be indicate that ISPF could not find the language processor. User responseVerify that your MVS™ search sequence includes the load module data set containing the processor requested is included, then retry the request. If the same message is returned, the language processor is returning the 20 and you should refer to the documentation supplied with that processor for problem determination. ISRF910 aaaaaaaa ExplanationThis message is self explanatory. ISRF911 Specify list ID - Specify a "list ID" for sequential file. ExplanationThe list ID, used as one of the qualifiers for the listing data set name, normally defaults to the name of the PDS member being processed. When a sequential data set is specified, no default name is used and the list ID must be specified. User responseSpecify a list ID and retry the function. ISRF912 Invalid ZSEL2 variable - The ZSEL2 panel variable must start
with CMD or PGM ExplanationThe PDF foreground processor (ISRFPR) is invoked passing the name of a panel to display. The )PROC section of this panel must set variable &ZSEL and may optionally set variable &ZSEL2 to an CMD(...) or PGM(...) string that PDF can pass to the ISPF SELECT service. A ZSEL2 string was encountered that did not start with CMD or PGM. User responseContact the responsible programmer. Programmer responseCorrect the ZSEL2 string and retry the function. ISRF914 BLDL error - I/O error, insufficient virtual storage or other
BLDL error ExplanationPDF received an error from the BLDL macro processing the data set specified for foreground processing. System programmer responseCheck your MVS console for messages caused by this error and refer to the System Messages and Codes for problem determination. If further assistance is needed, contact IBM support. User responseContact your system programmer. ISRF915 No members in data set - The PDS specified contains no members. ExplanationA member list was requested from the PDF foreground processor, but no members exist in the specified data set. User responseEither add the appropriate members to the data set you are using, or specify a different data set. ISRF916 I/O error - An I/O error occurred while reading the PDS directory. ExplanationPDF received a return code 8 from the BLDL macro while attempting to gather member statistics while building a foreground member list. User responseContact your system programmer. ISRF917 I/O error - An I/O error occurred during member list processing. ExplanationPDF member list routine received an I/O error while attempting to read the PDS directory of the data set specified for foreground processing. System programmer responseCheck your MVS console for messages caused by this error and refer to the System Messages and Codes for problem determination. If further assistance is needed, contact IBM support. User responseContact your system programmer. ISRF918 Member list error - Unexpected error from member list display
routine ExplanationThe PDF foreground processor (ISRFPR) received an unexpected return code from the PDF member list processor (ISRCML). System programmer responseCheck your MVS console for messages caused by this error and refer to the System Messages and Codes for problem determination. If further assistance is needed, contact IBM support. User responseContact your system programmer. ISRF919 Member not found - The requested member was not found in
the PDS directory(s). ExplanationThe member specified for foreground processing does not exist in the library specified. User responseCorrect the data set name and member name to specify an existing member and retry the function. ISRF920 Style deleted - Selected style(s) deleted from style table. ExplanationThis is an informational message. The selected style was deleted successfully from the Select Script/VS Formatting Style panel (panel ISRFP09T). ISRF921 Style table deleted - A new table will be created with the
next script invocation. ExplanationThis is an informational message. All styles were deleted from the existing style table, so the table was deleted. ISRF922 Bad directory - Directory block size exceeds maximum of 256. ExplanationThe PDF common member list routine detected a data set that had a directory block greater than 256 bytes, the maximum supported by PDF. User responseCopy the data into a new data set and retry the request. ISRF923 Function terminated - Processing was terminated by user request
(end). ExplanationThis is an informational message. The user entered the END command to terminate the current function. ISRF924 Select formatting style - Select a formatting style to process
script input. ExplanationEnter was pressed on the Select Script/VS Formatting Style panel (panel ISRFP09T) while a style was being selected. User responseSelect a style using the S line command, delete a style using the D line command, or enter the END command to exit without a selection. ISRF925 Invalid line command - Enter either S to select a style or
D to delete one. ExplanationA line command other than S or D was entered on the Select Script/VS Formatting Style panel (panel ISRFP09T). S and D are the only valid line commands. User responseSelect a style using the S line command, delete a style using the D line command, or enter the END command to exit without a selection. ISRF926 Select one style - Select only one style for the SCRIPT/VS
processor to use. ExplanationMultiple selections were made (using the S line command) on the Select Script/VS Formatting Style panel (panel ISRFP09T). Only one style may be selected from this panel. User responseRemove the extra selections and press Enter to continue the request, or enter the END command to exit without processing. ISRF927 Table not found - System style table 'aaaaaaaa.'
was not found. ExplanationThe PDF style table, used to hold the various default and user defined styles for processing script documents, could not be found in any of the data sets concatenated to ISPTLIB. System programmer responseCheck the user's ISPTLIB concatenation to see if it is complete. If not, make the necessary corrections to the logon proc or CLIST/REXX exec used. If the ISRSTLYE member cannot be located, a default copy of table ISRSTYLE can be found in the PDF product libraries shipped on the ISPF install tape. User responseCheck your ISPTLIB allocation to see if it is complete, or contact your system programmer for assistance. ISRF928 Internal dialog error - aaaaaaaa received
a return code of X'bbbb.'. ExplanationThe PDF Script/VS CLIST (CLIST ISRFC09) received a return code bbbb hex from an ISPEXEC aaaaaaaa service call. System programmer responseRefer to z/OS ISPF Services Guide for return code explanations. User responseContact your system programmer. ISRF929 Style table in use - Style table 'aaaaaaaa.'
is currently in use by another user. ExplanationPDF received a return code 12 from the TBOPEN service for table aaaaaaaa, indicating that the table is in use by you or another user. User responseWait until the table is free, then retry the request. ISRF930 Expand failed - Error during execution of member expansion,
return code aaaa. ExplanationA failure was encountered while an attempt was being made to unpack members that are packed. User responseRefer to ISPF User's Guide under "Member Expansion ISRLEMX Return Codes" for further information. ISRF931 Foreground - process - Member expansion error for aaaaaaaa file bbbbbbbb,
rc = cccccccc ExplanationThis message is self explanatory. ISRF932 Data not unpacked - Temporary data set cannot be generated
for packed data. ExplanationThis message is self explanatory. ISRF933 Processor error - The 'aaaaaaaa' language
processor could not be found. ExplanationThis message is self explanatory. ISRF934 Text not moved - "aaaaaaaa..bbbbbbbb..TEXT"
could not be accessed for text move. ExplanationThis message is self explanatory. ISRF935 No list file found - Unable to locate list file for member
parts list, or the file was empty. ExplanationThis is an informational message. The member parts list processor is complete, but the expected listing data set was not found for PDF to browse. ISRF936 DSN unavailable - DSN for input aaa(12) is
unavailable or does not exist. ExplanationThe aaa(12) data set specified on the Script/VS Options for Style: xxxxx (panel ISRFP09O) does not exist, or may be in use by another user. User responseIf the data set was specified incorrectly, correct the data set name and retry the function. If the name is correct, contact your system programmer of assistance. ISRF937 Additional lib error - The aaaaa of additional
library bbb(44) and the aaaaa of
the input library are incompatible. ExplanationPDF detected an inconsistency in either the RECFM or LRECL (indicated by aaaaa) of one of the additional input libraries specified when compared against your primary input library. User responseEnter a correct data set in the additional input library field and retry the function. ISRF938 Additional lib error - Additional library aaa(44) was
not found in catalog. ExplanationData set aaa(44), specified in the additional input libraries field, does not exist. User responseEither create the library, or specify an existing library and retry the request. ISRF939 Invalid data set name - The data set must be fully qualified
and enclosed in apostrophes. ExplanationA data set name was entered in the additional input libraries field that was not enclosed in apostrophes. User responseCorrect the data set name and retry the request. ISRF940 Additional lib error - Additional input library aaa(44) is
not partitioned. All libraries specified in the additional input
libraries fields must be partitioned. ExplanationData set aaa(44), specifies as one of the additional input libraries specified at the bottom of one of the compiler interface data entry panels is not partitioned. Only partitioned data sets may be specified in these fields. User responseSpecify a partitioned data set and retry the request. ISRG001 Invalid option number - Select an option and enter the option
number or code. ExplanationThis message is self explanatory. ISRG002 Enter project name - Project name is missing or invalid. ExplanationThe Project name field is blank or invalid in the ISPF library data set input fields. User responseA valid Project name must be entered for the
ISPF library. An ISPF library is a cataloged partitioned data set
with a three-level data set name in this format:
ISRG003 Enter group name - Group name is missing or invalid. ExplanationThe Project name field is blank or invalid in the ISPF library data set input fields User responseA valid Project name must be entered for the
ISPF library. An ISPF library is a cataloged partitioned data set
with a three-level data set name in this format:
ISRG004 Enter type qualifier - Type is missing or invalid. ExplanationThe Type name field is blank or invalid in the ISPF library data set input fields. User responseA valid Type name must be entered for the ISPF
library. An ISPF library is a cataloged partitioned data set with
a three-level data set name in this format:
ISRG005 Enter member name - The specified data set is partitioned.
A member name is required. ExplanationThis message is self explanatory. ISRG006 Enter volume serial - A volume serial is needed for this
operation. ExplanationThis message is self explanatory. ISRG007 Vol serial not allowed - Use "Other data set name" field
when specifying volume serial. ExplanationThe Volume Serial input field invalidly contains a value when not specifying Other Data Set Name field. User responseWhen using the ISPF Library input fields for entering the data set name, do not put any value in the Volume Serial input field. Only when using the Other Data Set Name input field can the Volume Serial input field contain a valid value. ISRG008 Invalid required parm - Select the required parameter from
the options shown. ExplanationThis message is self explanatory. ISRG009 Enter data set name - Use standard TSO format for data set
name. ExplanationThis message is self explanatory. ISRG010 Data set is open - Data set is currently being used by ISPF. ExplanationThe specified data set is open and currently being used by ISPF. User responseThis message is issued when one of the data sets LIST, LOG, TEMPLIST, TEMPCNTL, or EDIT RECOVERY is specified and ISPF is currently using the data set. The LOG and LIST data sets are controlled by the LOG and LIST commands. These two commands can keep the current data set and continue with a new data set so that keep data set can be used. The TEMPLIST, TEMPCNTL, and EDIT RECOVERY data sets need to be saved and closed in order to be used. ISRG011 Unsupported data type - HFS data sets are supported for data
set creation, data set information, data set rename and data set delete
only. ExplanationAn attempt was made to perform a PDF function other than data set creation, data set information, data set rename, or data set delete against an HFS data set. User responseUse a supported data set type. ISRG040 Invalid DSORG - Data set organization must be partitioned
or sequential. ExplanationThe data set organization was entered incorrectly. User responseCorrect the data set organization. ISRG044 Concatenation failed - Unable to concatenate the specified
libraries. ExplanationThe concatenation failed, ISPCDAIR did not return with RC=0. System programmer responseIf the user's action was correct, contact IBM support. User responseContact your system programmer. ISRG045 STAE macro error - Unable to obtain storage for STAE macro,
subpool 0 full. ExplanationStorage has been exhausted; there was a previous error that could have used all of the available storage. System programmer responseVerify that the task is not looping and that the storage is sufficient to execute the failing function. User responseVerify that your region size is large enough to run the task that just failed. If you still have a problem, contact the system programmer. ISRG070 OBTAIN failed - Unable to open data set. OBTAIN returned
nonzero return code. ExplanationThis message is self explanatory. ISRG071 Concatenation failed - Unable to concatenate the specified
libraries. ExplanationThe allocation of a concatenated set of libraries failed because the concatenation could not be completed. User responseVerify that the libraries to be concatenated can, in fact, be concatenated for allocation. Try using the TSO ALLOCATE command to perform the allocation and see if it produces messages. Also check for incompatible data set attributes among the data sets to be concatenated. ISRG072 Tape not supported - ISPF does not support data sets on tape. ExplanationAn allocation request was made for a data set which resides on tape. This action is not supported by ISPF. User responseCopy the data from the tape to a direct access storage device (DASD) and work with the data from the disk instead of the tape. ISRG073 Load failed - The attempt to load the installation allocation
exit failed. ExplanationThe allocation exit specified in the Configuration Table could not be loaded. User responseContact your system programmer. Programmer responseEnsure that the exit listed in the Configuration Table is available to the user, and that is not marked non-executable. ISRG074 Unknown return code - The installation allocation exit returned
an unknown return code of aaaaaaaa. ExplanationYour installation is using an allocation exit that is specified in the Configuration table. That exit returned a return code (aaaaaaaa) which is not defined to ISPF. There is probably an error in the exit. Programmer responseVerify that the exit is operating properly and ensure that the exit returns only return codes for which ISPF is prepared. ISRG075 Inconsistent block size - The first library must have the
largest block size. ExplanationThis message is self explanatory. ISRG076 Inconsistent record size - All libraries must have the same
record length. ExplanationAn attempt was made to concatenate data sets with different record lengths. This action is not supported by ISPF. User responseCheck to be sure that the correct data sets are being allocated and that the record lengths and record formats are the same for all of the data sets. You may need to reallocate the data sets or copy the contents to temporary data sets which you allocate instead. ISRG077 Inconsistent record type - All libraries must be the same
record type. ExplanationAn attempt was made to concatenate data sets with different record formats (fixed, variable, etc). This action is not supported by ISPF. User responseCheck to be sure that the correct data sets are being allocated and that the record lengths and record formats are the same for all of the data sets. You may need to reallocate the data sets or copy the contents to temporary data sets which you allocate instead. ISRG078 Inconsistent record size - The first library must have the
largest record length. ExplanationAn attempt was made to concatenate two data sets with variable record lengths where one data set has a larger record length than the first data set. This action is not supported by ISPF. User responseCheck to be sure that the correct data sets are being allocated and that the first data set has the largest record length among the data sets. You may need to reallocate the data sets or copy the contents to temporary data sets which you allocate instead. ISRG079 LOCATE failed - The LOCATE for 'aaaaaaaa'
failed, RC = bbbbbbbb. ExplanationA return code which ISPF does not recognize was
received from the LOCATE macro. The return code is specified in bbbbbbbb and
is NOT one of these:
User responseVerify that the data set exists and is located on the volume specified by the catalog. If it exists, there may be other problems with the system, volume, or catalog. Contact your system programmer. ISRG080 Inconsistent data sets - Data set organizations are not the
same. ExplanationAn attempt was made to concatenate data sets with different data set organizations. This action is not supported by ISPF. User responseCheck to be sure that the correct data sets are being allocated and that the data set organizations (sequential or partitioned) are the same for all of the data sets. You may need to reallocate the data sets or copy the contents to temporary data sets which you allocate instead. ISRG081 Data set not partitioned - Member name specified, but the
data set is not a partitioned data set. ExplanationA member name was specified with a data set which is not partitioned. User responseRemove the member name, or verify that the data set was correctly specified and correctly allocated. ISRG082 Data set not partitioned - Only partitioned data sets may
be concatenated. ExplanationAn attempt was made to concatenate data sets that are not partitioned. ISPF does not support concatenated sequential data sets. User responseCheck to be sure that the correct data sets are being allocated and that the data set organizations are all partitioned. ISRG083 Deconcatenation failed - Unable to deconcatenate the specified
libraries. ExplanationAn attempt was made to unallocate a set of concatenated libraries but the deconcatenate operation failed. User responseSince this is probably due to another allocation that uses the same ddname needed by the deconcatenation operation, you may need to use the TSO FREE command to free ddnames. If it does not matter if you have the data sets allocated, you may be able to ignore this message. However, if other users may need the data sets, it may be a good idea to free the data sets manually with the TSO FREE command, or to log off and back on. Problem determinationDetermine what activity has occurred between the allocation and freeing of the failing concatenation. It is possible that some other allocation attempt failed and did not free all of its allocations. These allocations may or may not have been done by ISPF. ISRG084 Reallocation failed - Reallocation failed for data set 'aaaaaaaa' ExplanationThe attempt to allocate a data set exclusively before deleting it failed. The data set may be in use by other users. User responseTry the operation again later. ISRG085 Deallocation failed - Deallocation failed for data set 'aaaaaaaa' ExplanationThe attempt to deallocate a data set in order to delete it failed. The data set may be in use by other users or by you. User responseUse the TSO FREE command to free all your allocations of the data set, and retry the operation. ISRG086 Delete data set failed - 'aaaaaaaa' is
in use, it cannot be deleted. ExplanationThe attempt to delete a data set failed. The data set may be in use by other users or by you, or you may not have authority to delete the data set. User responseUse the TSO FREE command to free all your allocations of the data set and retry the operation. If other users are not using the data set and you are authorized to delete the data set, contact your system programmer. ISRG087 Data set in use - The data set is currently in use by you. ExplanationAn operation on a data set failed because you are already allocated to the data set. User responseReturn to the primary option menu on all screens and retry the operation again. If that does not fix the problem, use the TSO FREE command to free the data set and retry the operation. ISRG088 DSN alloc check failed - Unable to check if data set is already
allocated. ExplanationAn internal error occurred. User responseLog off the system and log back on. Then retry the operation that failed. ISRG089 Multivolume data set - Data sets on multiple volumes are
not supported. ExplanationThis message is self explanatory. ISRG090 Invalid DSN - quotes - Data set name contains unbalanced
apostrophes. ExplanationThe data set name entered contains unbalanced apostrophes. User responseReenter the data set name with the correct apostrophes. ISRG091 Invalid DSN - length - Data set name must be 1-44 characters
in length counting prefix (if any). ExplanationThe data set name you entered had an invalid length. It must be no more than 44 characters including the TSO prefix, if used. User responseCheck the data set name, and reenter it correctly. ISRG092 Invalid member name - Member name must be 1-8 characters
and enclosed in parentheses. ExplanationThe member name that was entered was invalid. The member name must be 1 to 8 characters, enclosed in parentheses. User responseReenter the member name using the correct syntax. ISRG093 Invalid DSN - syntax - Embedded blanks, parentheses, or apostrophes
in data set name are invalid. ExplanationThe data set name that was entered contained blanks, apostrophes, or parentheses, which are invalid in a data set name. User responseReenter the data set name following the correct syntax. ISRG094 Data set not cataloged - Generation data set not found. Check
catalog of generation group. ExplanationThe data set specified was not found. User responseCheck the data set name entered. ISRG095 Inconsistent block size - The first library must have the
largest block size. ExplanationThe first library of the concatenation must have the largest block size of the libraries within the concatenation. System programmer responseUpdate the concatenation so that the largest block size data is first in the concatenation. ISRG096 Inconsistent record size - All libraries must have the same
record length. ExplanationAll libraries within a concatenation must have the same record length. System programmer responseUpdate the concatenation and library allocations to have consistent record lengths. ISRG097 Inconsistent record type - All libraries must be the same
record type. ExplanationAll libraries within a concatenation must be defined with the same record type. Programmer responseReview the libraries within the concatenation for the correct record type. ISRG098 Inconsistent record size - The first library must have the
largest record length. ExplanationThe first library within a concatenation must be defined with the largest record length. Programmer responseReview the libraries within the concatenation for the correct record length and concatenation sequence. ISRG099 Not generation data set - Data set is not a generation data
set. ExplanationThe data set specified is not a generation data set. Programmer responseCheck the specified data set name. ISRG100 Vol serial not allowed - Use "Other data set name" field
when specifying volume serial. ExplanationA volume serial was specified on a panel when the Project/Group/Type fields were used for the data set name. The volume serial may only be specified when you use the Other Data Set Name field for the data set. User responseIf you are trying to access a data set on a particular volume, type the data set name in the Other Data Set Name field and place the volume name in the Volume Serial field before pressing the Enter key. ISRG101 Load failed - The attempt to load the data set allocation
exit failed. ExplanationPDF attempted to load the allocation exit specified in the PDF configuration table but was unable to do so. The exit may not have been found, may have been non-executable, or you may not be authorized to load it. User responseEnsure that the allocation exit is correctly specified in the configuration table and is available and executable in your load libraries or system libraries before entering PDF. ISRG102 Load failed - The attempt to load the print utility exit
failed. ExplanationPDF attempted to load the print utility exit specified in the PDF configuration table but was unable to do so. The exit may not have been found, may have been non-executable, or you may not be authorized to load it. User responseEnsure that the print utility exit is correctly specified in the configuration table and is available and executable in your load libraries or system libraries before entering PDF. ISRG103 Load failed - The attempt to load the compress exit failed. ExplanationPDF attempted to load the compress exit specified in the PDF configuration table but was unable to do so. The exit may not have been found, may have been non-executable, or you may not be authorized to load it. User responseEnsure that the compress exit is correctly specified in the configuration table and is available and executable in your load libraries or system libraries before entering PDF. ISRG104 Load failed - The attempt to load the data set list exit
failed. ExplanationPDF attempted to load the data set list exit specified in the PDF configuration table but was unable to do so. The exit may not have been found, may have been non-executable, or you may not be authorized to load it. User responseEnsure that the data set list exit is correctly specified in the configuration table and is available and executable in your load libraries or system libraries before entering PDF. ISRG105 Load failed - The attempt to load the member list filter
exit failed. ExplanationPDF attempted to load the member list filter exit specified in the PDF configuration table but was unable to do so. The exit may not have been found, may have been non-executable, or you may not be authorized to load it. User responseEnsure that the member list filter exit is correctly specified in the configuration table and is available and executable in your load libraries or system libraries before entering PDF. ISRG106 Load failed - The attempt to load the data set name change
exit failed. ExplanationPDF attempted to load the data set name change exit specified in the PDF configuration table but was unable to do so. The exit may not have been found, may have been non-executable, or you may not be authorized to load it. User responseEnsure that the data set name change exit is correctly specified in the configuration table and is available and executable in your load libraries or system libraries before entering PDF. ISRG107 Load failed - The attempt to load the data set list line
command exit failed. ExplanationPDF attempted to load the data set list line command exit specified in the PDF configuration table but was unable to do so. The exit may not have been found, may have been non-executable, or you may not be authorized to load it. User responseEnsure that the data set list line command exit is correctly specified in the configuration table and is available and executable in your load libraries or system libraries before entering PDF. ISRG108 Load failed - The attempt to load the installation accounting
exit failed. ExplanationPDF attempted to load the installation accounting exit specified in the PDF configuration table but was unable to do so. The exit may not have been found, may have been non-executable, or you may not be authorized to load it. User responseEnsure that the installation accounting exit is correctly specified in the configuration table and is available and executable in your load libraries or system libraries before entering PDF. ISRH020 ISRCMD aaaaaaaa bbbbbbbb ExplanationThis message is self explanatory. ISRH021 ISRCMD aaaaaaaa ExplanationThis message is self explanatory. ISRI001 ISPF load error - The subroutine table for the PDF component
of ISPF could not be loaded, probably due to an installation error.
Please contact your system programmer. ExplanationISPF received an error attempting to load the Subroutine Table for the PDF component, load module ISRTSP. System programmer responseCheck the load library concatenation sequence (ISPLLIB, STEPLIB, and so forth) to ensure that the library containing ISRTSP is included. User responseContact your system programmer. ISRI003 Incorrect DM version - The PDF component of ISPF for z/OS 02.01.00 requires the DM component
of ISPF for z/OS 02.01.00,
probable installation error. Please contact your system programmer. ExplanationThe PDF component of ISPF for z/OS 02.01.00 was invoked with a version of ISPF that is not for z/OS 02.01.00. System programmer responseCheck the load library concatenation sequence (ISPLLIB, STEPLIB, and so forth) to ensure that the proper ISPF libraries for z/OS are specified. ISRJ001 aaaaaaaa - from bbb(56) ExplanationThis is an informational message. The message logged upon successful building of the job step to invoke the aaaaaaaa language processor against data set and member bbb(56). ISRJ002 aaaaaaaa - from bbb(44) ExplanationThis is an informational message. The message logged upon successful building of the job step to invoke the aaaaaaaa language processor against data set bbb(44). ISRJ003 aaaaaaaa - to bbbbbbbb..LOAD(cccccccc) ExplanationThis is an informational message. The message logged upon successful building of the job step to invoke the aaaaaaaa language processor, placing the output in data set bbbbbbbb.LOAD, member cccccccc. ISRJ004 Job step generated - aaaaaaaa -------
from bbb(56). ExplanationThis is an informational message. Indicates a JCL job step has been successfully generated for the aaaaaaaa language processor, using input from data set and member bbb(56). ISRJ005 Job step generated - aaaaaaaa -------
from bbbbbbbb. ExplanationThis is an informational message. Indicates a JCL job step has been successfully generated for the aaaaaaaa language processor, using input from data set bbbbbbbb. ISRJ006 Job step generated - aaaaaaaa -------
to bbbbbbbb..LOAD(cccccccc). ExplanationThis is an informational message. Indicates a JCL job step has been successfully generated for the aaaaaaaa language processor, sending output from data set and member bbbbbbbb.LOAD(cccccccc). ISRJ007 Job - aaaaaaaa - Canceled. ExplanationThis is an informational message. The user entered the CANCEL command on the Batch Termination panel to exit batch without submitting the generated JCL. ISRJ008 Job - aaaaaaaa - Submitted. ExplanationThis is an informational message. The user entered the END command on the Batch Termination panel to exit batch after submitting the generated JCL. ISRJ009 Submit job ERROR1 - Error submitting job from aaaaaaaa. ExplanationAn error occurred while attempting to use the TSO SUBMIT command to submit the generated JCL (allocated to ddname aaaaaaaa) for processing. User responseRegenerate the JCL and resubmit the job. If problems persist, contact your system programmer for assistance. ISRJ010 aaaaaaaa - from bbb(56) ExplanationThis is an informational message. This message is logged on the successful building of the job step to invoke the aaaaaaaa language processor against data set and member bbb(56). ISRJ011 aaaaaaaa - to bbbbbbbb..cccccccc..LOAD(dddddddd). ExplanationThis is an informational message. This message is logged on the successful building of the job step to invoke the aaaaaaaa language processor against ISPF library bbbbbbbb.cccccccc.LOAD(dddddddd). ISRJ012 Job step generated - aaaaaaaa -------
from bbb(56). ExplanationThis is an informational message. Indicates a JCL job step has been successfully generated for the aaaaaaaa language processor, using input from data set and member bbb(56). ISRJ013 Job step generated - aaaaaaaa -------
to bbbbbbbb..cccccccc..LOAD(dddddddd). ExplanationThis is an informational message. Indicates a JCL job step has been successfully generated for the aaaaaaaa language processor, sending output to the ISPF library and member bbbbbbbb.cccccccc.LOAD(dddddddd). ISRJ014 Enter option - Enter one of the listed options. ExplanationThe Enter key was pressed on either the Batch Selection panel (ISRJPA) or the Batch Termination panel (ISRJPB) without an option being selected. User responseSpecify the option desired on the command line and press Enter. ISRJ015 Invalid option - The option that was entered was not valid. ExplanationAn invalid option was entered on either the Batch Selection panel (ISRJPA) or the Batch Termination panel (ISRJPB). User responseSpecify a valid option and press Enter. ISRJ901 aaaaaaaa - bbbbbbbb. ExplanationThis message is self explanatory. ISRJ902 Skeleton not found - Skeleton "aaaaaaaa"
or imbedded skeletons in "aaaaaaaa" not found. ExplanationPDF issued an ISPEXEC FTINCL for skeleton aaaaaaaa, but received a nonzero return code, indicating the skeleton could not be found. User responseCheck your ISPSLIB concatenation to ensure the proper skeleton libraries are specified. After correcting your concatenation, retry the request. ISRJ903 Invalid ZSEL variable - The ZSEL panel variable must start
with CMD or PGM. ExplanationThe PDF batch processor (ISRJB2) is invoked, passing the name of a panel to display. The )PROC section of this panel must set variable &ZSEL to a CMD(...) or PGM(...) string that PDF can pass to the ISPF SELECT service. A ZSEL string was encountered that did not start with CMD or PGM. User responseContact the responsible programmer. Programmer responseCorrect the ZSEL string and retry the function. ISRJ904 BLDL error - I/O error, insufficient virtual storage or other
BLDL error ExplanationPDF received an error from the BLDL macro processing the data set specified for batch processing. System programmer responseCheck the MVS console for messages and refer to the appropriate IBM documentation for problem determination steps. User responseContact your system programmer for assistance in problem determination. ISRJ905 Invalid organization - Only partitioned and physical sequential
data sets processed. ExplanationThe PDF batch option was invoked, specifying a data set that was other than partitioned or sequential. User responseChange the input data set to one that is partitioned or sequential and retry. ISRJ906 Invalid organization - Only partitioned data sets processed. ExplanationThe PDF batch Binder/Linkage Editor option only supports partitioned data sets as input. User responseChange the input data set to one that is partitioned and retry. ISRJ907 Batch: aaaaaaaa ------------------------------------------------------- ExplanationThis message is self explanatory. ISRJ908 Job skeleton not found - Job skeleton file ISRJSJC not found. ExplanationPDF batch skeleton ISRJSJC, used to set up the job cards for batch job submission, could not be found in your ISPSLIB concatenation. User responseCheck your ISPSLIB concatenation to ensure the proper skeleton libraries are specified. After correcting your concatenation, retry the request. ISRJ909 File tailoring error - File tailoring is already in progress. ExplanationThe PDF batch option uses ISPF file tailoring to create its jobstream; therefore, it cannot be invoked when another file tailoring request is in progress. User responseFinish the in-process file tailoring request, then retry the batch request. ISRLA120 No unit description - Must specify the unit description for
the outlist data set.
ISRLA121 No block size - Must specify the block size for the outlist
data set.
ISRLA122 No logical record length - Must specify the logical record
length for the outlist data set.
ISRLA123 No lines per page - Must specify the lines per page for the
outlist data set.
ISRLA124 No primary/secondary - Must specify primary/secondary space
quantity for outlist data set.
ISRLA125 No primary space - Must specify primary space quantity for
partitioned outlist data set.
ISRLD000 Missing parameters - One or both of level and volume must
be specified for LMDINIT. ExplanationEither a data set name level or a volume or both must be specified for the data set list service. User responseCorrect the LMDINIT command. ISRLD001 Insufficient storage - Not enough main storage was available
to satisfy request for LMDINIT. ExplanationThere is not enough storage available to build the control block for processing LMDINIT. User responseIncrease your region size and retry the request. ISRLD002 Free storage failed - Free main storage request failed. ExplanationThe LMDINIT service was unable to free the storage used to build the control block. User responseContact your system programmer. ISRLD003 Invalid data set level - Data set level must not have quotes. ExplanationThe data set name level does not need to be included in quotes. User responseRemove the quotes from the data set name level. ISRLD004 Invalid DSname level - Two or more adjacent asterisks within
a DSname level qualifier is invalid. A single asterisk indicates
0 or more letters may occupy that position in the qualifier. ExplanationTwo or more adjacent asterisks means 0 or more qualifiers may occupy that position. This is invalid within a single qualifier. Double asterisks may be used as a qualifier with no other characters. User responseChange the adjacent asterisks to a single asterisk. ISRLD005 Invalid DSname level - In order to list catalog entries,
you must specify at least one partial qualifier. Any DSname level
that contains only asterisks is invalid. ExplanationIf you specify only asterisks for a DSNAME level, a search will be made of all the catalogs on the system. This is detrimental to performance, so at least one partial qualifier is required. User responsePartially qualify at least one dsname level qualifier. ISRLD006 Invalid data set level - Qualifiers cannot be longer than
8 characters. ExplanationThis is an informational message. ISRLD007 Invalid data set level - Qualifiers must be at least one
character long. ExplanationThis is an informational message. ISRLD008 Invalid data set level - A data set level cannot have more
than 8 qualifiers. ExplanationThis is an informational message. ISRLD009 Invalid data set level - The specified data set level is
invalid. ExplanationThis message is self explanatory. ISRLD010 Invalid option - Specify one of LIST, FREE, SAVE, SAVEC or
TOTALS. ExplanationValid options for the LMDLIST service are LIST, FREE, SAVE, SAVEC and TOTALS. User responseSpecify a valid option. ISRLD011 List ID not initialized - The list ID was not initialized
successfully by the LMDINIT service. ExplanationThe LMDINIT service failed. User responseContact the responsible programmer. Programmer responseCheck the parameters of the LMDINIT service. ISRLD012 Volume error - The volume specified for this list ID is invalid ExplanationAn invalid volume was specified for the LMDINIT command. User responseSpecify a valid volume. ISRLD013 No data set names found - No data set names were found to
satisfy the search argument(s). ExplanationThis is an informational message. ISRLD014 Cannot free list - No data set list has been built by the
LMDLIST service for this list ID ExplanationAn invalid dslist ID was specified for the LMDFREE command. User responseContact the responsible programmer. Programmer responseCheck the list ID specified for the LMDFREE command. ISRLD015 Cannot save list - A save cannot be performed when a list
already exists for a list ID ExplanationWhen a LMDLIST command has been issued with the LIST option, an LMDFREE must be issued before an LMDLIST with option SAVE is executed. User responseContact the responsible programmer. Programmer responseIssue an LMDFREE command for the list before using LMDLIST with the save option. ISRLD016 Data set not specified - The data set parameter is required
for the list option. ExplanationThe data set parameter is required for the list option to establish the position of the list. User responseSpecify a data set parameter. ISRLD017 Invalid STATS parameter - Specify either YES, NO or PRT. ExplanationThe only valid parameters for the STATS parameter of LMDLIST are YES, NO or PRT. User responseEnter YES or NO to have STATS saved in the function pool. Enter PRT to add the Total Tracks header line to the data set list printed to the ISPF List data set. ISRLD018 Invalid data set level - The DSname level cannot contain
embedded blanks. ExplanationBlanks are not allowed in the DSname level for the LMDINIT service. User responseRemove the blanks from the DSname level. ISRLD019 Invalid STATUS parameter - Specify either YES or NO. ExplanationThe only valid parameters for the STATUS parameter of LMDLIST are YES or NO. User responseEnter YES or NO to have a progress status panel displayed during data collection. ISRLD020 List ID not initialized - The list ID was not initialized
successfully by the LMDINIT service. ExplanationAn LMDFREE service was requested for a data set list ID that was not initialized by the LMDINIT service. Programmer responseInitialize the data set list ID before trying to free it. ISRLD030 Internal error - The LDB was not properly initialized. Contact
system programmer. ExplanationThe control block for this data set list has not been initialized. The control block is initialized by the LMDINIT service. Programmer responseUse the LMDINIT service to initialize the control block for the LMDDISP service. ISRLD031 Invalid VIEW value - Specify either VOLUME, SPACE, ATTRIB
or TOTAL. ExplanationWhen the VIEW parameter is specified for the LMDDISP service, the parameter must be VOLUME, SPACE, ATTRIB, or TOTAL. Any other specification for VIEW is invalid. Programmer responseSpecify a valid view parameter. ISRLD032 Invalid CONFIRM value - Specify either YES or NO. ExplanationFor the LMDDISP service, the only valid values for the CONFIRM parameter are YES or NO. Programmer responseUse YES or NO with the CONFIRM parameter. ISRLD033 Load failed for ISRUDL - The load of the data set list utility
load module (ISRUDL) failed. ExplanationThe LMDDISP service was unable to load module ISRUDL. System programmer responseCheck the load library concatenation sequence (ISPLLIB, STEPLIB, and so forth) to ensure that the library containing ISRUDL is included. User responseContact your system programmer. ISRLD034 Load failed for ISRUDA - The load of the Library Utility
load module (ISRUDA) failed. ExplanationThe MEMLIST service was unable to load module ISRUDA. System programmer responseCheck the load library concatenation sequence (ISPLLIB, STEPLIB, and so forth) to ensure that the library containing ISRUDA is included. User responseContact your system programmer. ISRLD035 Data set not partitioned - The MEMLIST service requires the
data set to be a partitioned data set. ExplanationThe data set is not partitioned; the MEMLIST service requires a partitioned data set. User responseContact your system programmer. ISRLD036 Invalid CONFIRM value - Specify either YES or NO. ExplanationFor the MEMLIST service, the only valid values for the CONFIRM parameter are YES or NO. Programmer responseUse YES or NO with the CONFIRM parameter. ISRLD037 Invalid CATALOG value - Specify either YES or NO. ExplanationFor the LMDDISP service, the only valid values for the CATALOG parameter are YES or NO. Programmer responseUse YES or NO with the CATALOG parameter. ISRLD038 Invalid TOTALS parameter - Specify either YES or NO. ExplanationThe only valid parameters for the TOTALS parameter of LMDDISP are YES or NO. User responseEnter YES or NO to have an additional header line with the total tracks of all data sets and the number of all data sets in the list displayed above the column description for the TOTAL and SPACE view. ISRLD039 Invalid STATUS parameter - Specify either YES or NO. ExplanationThe only valid parameters for the STATUS parameter of LMDDISP are YES or NO. User responseEnter YES or NO to have a progress status panel displayed during data collection. ISRLE000 Enter project name - Project name is missing or invalid. ExplanationEither no project name was entered on the Member Parts List panel or the project name entered was syntactically incorrect. User responseCorrect the project value and retry the request. ISRLE001 Enter group name - Group name is missing or invalid. ExplanationEither no group name was entered on the Member Parts List panel or the group name entered was syntactically incorrect. User responseCorrect the group value and retry the request. ISRLE002 Enter type qualifier - Type is missing or invalid. ExplanationEither no type name was entered on the Member Parts List panel or the type name entered was syntactically incorrect. User responseCorrect the type value and retry the request. ISRLE003 DSN required - Output data set name required for option 2. ExplanationWhen using Member Parts List option 2 (Write Member Parts Data Set), the output data set must be specified. User responseSpecify a data set name in the Output Data Set field and retry the request. ISRLE004 Invalid DSORG - Input data set must be partitioned. ExplanationInput to the Member Parts List function must be a partitioned data set or a concatenation of partitioned data sets. User responseCorrect the input data set name to specify one or more partitioned data sets, and retry the request. ISRLE005 Library allocation error - ISPF input library cannot be allocated
to the input ddname. ExplanationThe Member Parts List processor attempted to allocate the input data sets specified to ddname ISRLCODE. This allocation failed, must likely because the ddname is already in use. User responseFree ddname ISRLCODE and retry the request. ISRLE006 Output DSN error - The output data set could not be allocated. ExplanationThe Member Parts List processor could not successfully allocate the data set specified in the Output Data Set field. User responseThe data set may be in use by another user. Verify that the data set is available and usable, then retry the request. ISRLE007 Allocate temp DSN failed - A temporary output data set could
not be allocated. ExplanationMember Parts List attempted to create a temporary data set to hold the listing requested, but the allocation failed. User responseThere may be no available data set names for
Member Parts List to use, or an existing data set that Member Parts
List is trying to use may have incorrect characteristics. Delete
all existing data sets that follow the Member Parts List naming convention,
and retry the request. The data set names generated by Member Parts
List have one of these forms:
ISRLE009 Enter valid LANG value - Minimum valid values are: ASM, COB,
FOR/FTN, PAS, PL1/PLI, SCR. ExplanationThe value entered in the language field was not
valid. The supported values and languages are:
User responseEnter a valid language value, and retry the request. ISRLE010 No valid job card found - Enter a valid job card from option
5 (Batch). ExplanationThis message is self explanatory. ISRLE011 Skeleton not found - Skeleton aaaaaaaa not
found in ISPSLIB concatenation. ExplanationThis message is self explanatory. ISRLE012 Member name not allowed - A member name was specified for
a sequential data set. ExplanationThe data set specified in the Output Data Set field is a sequential data set, but a member name was specified. Member name is not valid for a sequential data set. User responseEither specify a sequential data set without a member name or specify a partitioned data set and member in the Output Data Set field, then retry the request. ISRLE013 Member name is required - A partitioned data set was specified
with no member name. ExplanationThe data set specified in the Output Data Set field is a partitioned data set, but no member name was specified. A member name is required for a partitioned data set. User responseEither specify a sequential data set without a member name, or specify a partitioned data set and member in the Output Data Set field, then retry the request. ISRLE014 Error: SPFnnn.OUTLIST - Please delete all unneeded SPFnnn.OUTLIST
data sets. ExplanationMember Parts List attempted to create a temporary data set to hold the listing requested, but could not find a name available to use for the temporary data set. User responseDelete all existing data sets that follow the
Member Parts List naming convention, and retry the request. The data
set names generated by Member Parts List have one of these forms:
ISRLE015 Invalid output data set - The output data set must be record
format fixed with record length >= 17. ExplanationThe Member Parts List output data set must have a record format for Fixed or Fixed-Blocked and a logical record length of 17. User responseReallocate the data set with the correct characteristics, then retry the request. ISRLE020 Enter project name - Project name is missing or invalid. ExplanationEither no project name was entered on the Member Parts List panel or the project name entered was syntactically incorrect. User responseCorrect the project value and retry the request. ISRLE021 Enter group name - Group name is missing or invalid. ExplanationEither no group name was entered on the Member Parts List panel or the group name entered was syntactically incorrect. User responseCorrect the group value and retry the request. ISRLE022 Enter type qualifier - Type is missing or invalid. ExplanationEither no type name was entered on the Member Parts List panel or the type name entered was syntactically incorrect. User responseCorrect the type value and retry the request. ISRLE023 Invalid DSORG - Data set organization must be partitioned
(PO). ExplanationInput to the Member Parts List function must either be a partitioned data set or a concatenation of partitioned data sets. User responseCorrect the input data set name to specify one or more partitioned data sets and retry the request. ISRLE024 Skeleton not found - Skeleton for aaaaaaaa not
found in skels data set. ExplanationA skeleton needed for batch processing (aaaaaaaa) could not be found by the ISPF file tailoring program. User responseVerify that the proper ISPF skeleton library is allocated to ddname ISPSLIB, then retry the request. ISRLE025 DSN required - Data set name is required for option 2. ExplanationWhen using Member Parts List option 2 (Write Member Parts Data Set), the output data set must be specified. User responseSpecify a data set name in the Output Data Set field and retry the request. ISRLE026 Member name not allowed - A member name was specified for
a sequential data set. ExplanationThe data set specified in the Output Data Set field is a sequential data set, but a member name was specified. Member name is not valid for a sequential data set. User responseEither specify a sequential data set without a member name or a partitioned data set and member in the Output Data Set field, then retry the request. ISRLE027 Member name is required - A partitioned data set was specified
with no member name. ExplanationThe data set specified in the Output Data Set field is a partitioned data set, but no member name was specified. A member name is required for a partitioned data set. User responseEither specify a sequential data set without a member name or a partitioned data set and member in the Output Data Set field, then retry the request. ISRLE029 Enter valid LANG value - Minimum valid values are: ASM, COB,
FOR/FTN, PAS, PL1/PLI, SCR. ExplanationThe value entered in the language field was not
valid. The supported values and languages are:
User responseEnter a valid language value and retry the request. ISRLI003 Region size too small - Insufficient virtual storage from
module 'aaaaaaaa'.
ISRLI006 Free main storage failed - Free main storage failed in module
'aaaaaaaa'.
ISRLI009 Close failed - Close failed in module'aaaaaaaa'.
ISRLO999 Licensed Materials - Property of IBM 5650-ZOS Copyright IBM Corp. 1980, 2013. US Government Users Restricted
Rights - Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp. ExplanationThis is an informational message. ISRLS000 No data set specified - Must specify either an ISPF library,
data set, or ddname for LMINIT. ExplanationThe LMINIT service was incorrectly invoked. Either a complete ISPF library name (Project, Group(s), and Type), a data set name, or a ddname must be specified. User responseContact the responsible programmer. Programmer responseIf you are using the ISPF library keywords, insure that the project, group, and type are all correctly specified. If you are using the data set or ddname keywords, insure that the values you are passing to the service are complete and correct. If you are using a compiled language, check to see that values shorter than the maximum possible length are terminated with at least one blank. ISRLS001 Incomplete specification - Must specify project, group1,
and type for an ISPF library. ExplanationThe LMINIT service was incorrectly invoked. An incomplete ISPF library name (Project, Group(s), and Type) was specified. User responseContact the responsible programmer. Programmer responseEnsure that the project, group, and type are all correctly specified. If you are using a compiled language, check to see that values shorter than the maximum possible length are terminated with at least one blank. ISRLS002 Invalid ENQ requirement - Specify either SHR, EXCLU, SHRW,
or MOD. ExplanationAn LMINIT service was issued with an invalid or missing value for the ENQ parameter. User responseContact the responsible programmer. Programmer responseEnsure that the LMINIT service specifies either SHR, EXCLU, SHRW, or MOD for the ENQ parameter. In compiled languages, it is a good idea to pad the SHR parameter with a blank. ISRLS003 Invalid data set org - Data set is not sequential or partitioned.
Not supported by ISPF. ExplanationAn LMINIT service was issued for a data set that has an organization not supported by ISPF. User responseSpecify another data set, or contact the responsible programmer. Programmer responseEnsure that the data sets used by your application are either sequential data sets or partitioned data sets. ISRLS004 Insufficient storage - Not enough main storage was available
to satisfy request. ExplanationAn LMINIT service was unable to obtain the storage it needed to complete. User responseTry to reduce the number of programs already running while this program is running. If that is not feasible, try logging on with a larger region size. ISRLS005 Free storage failed - Free main storage request failed. ExplanationStorage obtained by an ISPF service could not be freed. User responseContact the responsible programmer. Programmer responseEnsure that your program is not incorrectly freeing storage that it did not obtain. If this does not solve the problem, contact IBM support. ISRLS006 Invalid data set status - Only sequential data sets can be
allocated mod for LMINIT. ExplanationAn LMINIT service was issued to allocate a data set for disposition MOD but the data set is not sequential. User responseContact the responsible programmer. Programmer responseEnsure that the application is allocating only sequential data sets with disposition MOD. ISRLS007 Member name not allowed - Member name not allowed in the
specification of data set parameter. ExplanationAn LMINIT service was issued with the member name specified in the data set parameter. This is not supported by ISPF. User responseContact the responsible programmer. Programmer responseChange the application to specify only the data set name on the LMINIT service. Then use the LMMFIND service before the LMGET service, or use the MEMBER keyword of the EDIT or BROWSE services. ISRLS008 Member name not allowed - Ddname allocated to member of partitioned
data set is not allowed. ExplanationAn LMINIT service was issued to use a preallocated ddname that was allocated to a member of a partitioned data set. This is not supported. User responseContact the responsible programmer. Programmer responseIf you know the name of the data set and member to be allocated, use the LMINIT service in combination with other services to allocate the data set as a whole, then to access the member. ISRLS009 Invalid data set status - Only partitioned data sets can
be allocated shrw for LMINIT. ExplanationAn LMINIT service was issued to allocate a data set for disposition SHRW but the data set is not partitioned. User responseContact the responsible programmer. Programmer responseEnsure that the application is allocating only partitioned data sets with disposition SHRW. ISRLS010 Ddname not found - Ddname 'aaaaaaaa' not
found. ExplanationAn LMINIT by ddname was requested, but the ddname specified is not currently allocated. User responseContact the responsible programmer. Programmer responseIf the ddname specified is correct, use the TSO ALLOCATE command to allocate the correct data sets to that ddname. If the ddname specified is not correct, make the necessary corrections. ISRLS011 Invalid data set status - Data set is not allocated as NEW,
OLD, SHARED, or MOD. ExplanationAn LMINIT by ddname was requested, but the ddname was allocated with a status other than NEW, OLD, SHARED, OR MOD. User responseContact the responsible programmer. Programmer responseReallocate the ddname using a correct status value and retry the LMINIT request. ISRLS012 Invalid concatenation - More than 16 concatenated data sets
not supported by ISPF. ExplanationAn LMINIT by ddname was requested, but the ddname specified has more than 16 data sets allocated to it. PDF only supports up to 16 concatenated data sets. User responseContact the responsible programmer. Programmer responseReallocate the ddname using 16 or fewer data sets, and retry the LMINIT request. ISRLS013 Invalid data set - Multivolume data sets are not supported
by LMINIT by DDNAME. ExplanationAn LMINIT by ddname was requested, but the data set allocated to the specified ddname is a multivolume data set. User responseReallocate the ddname to a single volume data set, and retry the LMINIT request. ISRLS014 Invalid device - Data sets not on direct access device are
not supported by ISPF. ExplanationAn LMINIT by ddname was requested, but one of the data sets allocated to the specified ddname does not reside on a direct access device. ISPF and PDF only support direct access devices. User responseContact the responsible programmer. Programmer responseReallocate the ddname using data sets on direct access devices, and retry the LMINIT request. ISRLS015 Obtain failed - Unable to obtain data set organization. ExplanationAn LMINIT by ddname was requested, but a failure was encountered when issuing the OBTAIN macro to retrieve the data set characteristics. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS016 Inconsistent data sets - Data sets with inconsistent 'aaaaaaaa'
cannot be concatenated. ExplanationAn LMINIT by ddname was requested, but the data sets allocated to the specified ddname did not all have the same data set organization, record format, or record length (as indicated by aaaaaaaa). User responseContact the responsible programmer. Programmer responseReallocate the ddname using data sets with consistent attributes and retry the LMINIT request. ISRLS017 Data set not partitioned - Only partitioned data sets may
be concatenated under ISPF. ExplanationAn LMINIT by ddname was requested, but the specified ddname represented a concatenation of sequential data sets. PDF only supports concatenations of partitioned data sets. User responseContact the responsible programmer. Programmer responseReallocate the ddname using either one sequential data set or a concatenation of partitioned data sets, and retry the LMINIT request. ISRLS018 Missing 'aaaaaaaa' - Must specify DSORG,
RECFM, BLKSZ, LRECL for ddname allocated new. ExplanationAn LMINIT by ddname was requested for a ddname representing a data set with a disposition of NEW, but valid values had not been specified for one of more of these items: data set organization, record format, block size, or logical record length. User responseContact the responsible programmer. Programmer responseReallocate the ddname, specifying all the appropriate information, then retry the LMINIT request. ISRLS019 No directory blocks - Must specify number of directory blocks
for new partitioned data set. ExplanationAn LMINIT by ddname was requested for a ddname representing a partitioned data set with a disposition of NEW, but the value for directory blocks is zero. User responseContact the responsible programmer. Programmer responseReallocate the ddname, specifying a nonzero value for directory blocks, then retry the LMINIT request. ISRLS020 Data ID not found - Data ID 'aaaaaaaa'
not found. ExplanationThe data ID specified in the library access service request does not exist. A previous LMINIT service was not successfully issued before the current service request was made. User responseContact the responsible programmer. Programmer responseCheck the application to verify that the LMINIT service was issued and that it was successful. You may want to add logic to bypass subsequent service requests if the LMINIT fails. ISRLS021 No information available - No information available for field
'aaaaaaaa'. ExplanationThe LMQUERY service was issued for a data ID that was not allocated in a manner that LMQUERY supports. LMQUERY only supports the allocations made with the ISPF library qualifiers (Project, Group(s), and Type) on the LMINIT service. User responseContact the responsible programmer. Programmer responseEnsure that the LMQUERY service is only used for data IDs that are allocated using the Project, Groups, and Type fields on the LMINIT service. ISRLS022 Unexpected severe error - Severe error occurred trying to
free data ID. ExplanationAn internal error occurred while trying to free a control block called the LSB. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS023 Unrecoverable I/O error - An unrecoverable read I/O error
occurred while freeing data set. ExplanationAn unrecoverable I/O error occurred while trying to free a data set that was open for reading. User responseSince the data set may not be usable, you may need to obtain a backup copy of it. Try to use other programs to read the data set before replacing it with an older backup copy. ISRLS024 Unrecoverable I/O error - An unrecoverable write I/O error
occurred while freeing data set. ExplanationThis message is self explanatory. ISRLS025 Unrecoverable error - An unrecoverable error occurred while
freeing member list. ExplanationAn unrecoverable error occurred while freeing a member list during the execution of the LMFREE service. User responseContact the responsible programmer. Programmer responseBefore issuing the LMFREE service, issue the LMMLIST service with the free option. If this does not solve the problem, contact IBM support. ISRLS026 Unrecoverable error - An unrecoverable error occurred while
closing data set. ExplanationThis message is self explanatory. ISRLS027 Members not found - No members were found in the specified
data set. ExplanationThe LMPROM service was issued to promote members out of a data set that does not contain the members requested. User responseContact the responsible programmer. Programmer responseVerify that the members you want to promote exist in the data set from which you are promoting. ISRLS028 Members not found - No members were found in the data set
to match pattern 'aaaaaaaa'. ExplanationNo members were found in the data set to match pattern aaaaaaaa, which was supplied to the LMPROM service. User responseDepending on the application, this may not be a problem. However, if you supplied the pattern, check to see if the pattern specified was correct. Programmer responseVerify that the pattern specified on the LMPROM service was correct. If this situation does not signify an error the application user needs to be aware of, you may want to ensure that LMPROM return codes are appropriately handled. ISRLS029 Invalid disposition - An enqueue disposition of MOD is invalid
for standard format records. ExplanationYou cannot do an LMINIT with the ENQ(MOD) on data sets with a record format of FS or FBS. Writing to an FS or FBS data set using a disposition of MOD will corrupt the data set. User responseEither use a disposition of OLD, or copy the data into a record format F or FB data set and that process the data set MOD. ISRLS030 Invalid open option - 'aaaaaaaa' is an
invalid option. Specify either INPUT or OUTPUT. ExplanationAn LMOPEN service was invoked with an invalid parameter for the OPTION keyword. Programmer responseVerify that the OPTION value on the LMOPEN service is either INPUT or OUTPUT. The default is INPUT. ISRLS031 Data set already opened - The data set identified by data
ID 'aaaaaaaa' is already open. ExplanationAn LMOPEN service was invoked for a data ID that was already open. Programmer responseCheck to see if LMOPEN is being called twice without an intervening LMCLOSE or LMFREE. If this is not the error, check to see if the data ID is open on entry to your program (if it was supplied by another program). For example, the edit macro DATAID statement will return a data ID that is already open and should not be closed by an edit macro. ISRLS032 OUTPUT not allowed - OUTPUT option is not allowed with data
set allocated SHR. ExplanationAn LMOPEN service attempted to open a data set for output when the data set was allocated by LMINIT with ENQ(SHR). Programmer responseChange the LMINIT ENQ option to EXCLU or SHRW. ISRLS033 OUTPUT not allowed - OUTPUT option is not allowed with concatenated
data sets. ExplanationAn LMOPEN service attempted to open a data ID for output when the data ID was allocated to more than one data set. Concatenated libraries cannot be opened for output by the LMOPEN service. Programmer responseChange the logic of your program to create a separate data ID for the specific data set you need to write to, then use that data ID for writes. You may find the LMQUERY service helpful in this effort, or you may need to use another method (such as trapping the output of the TSO LISTALC STATUS command, or examining MVS control blocks) to determine the name of the data set to allocate. ISRLS034 Invalid data set status - Data set can only be allocated
shared, old, shared/write, mod, or new. ExplanationAn LMOPEN service was attempted for a data ID that had an invalid allocation status. Programmer responseVerify that the LMINIT service that created the data ID has an ENQ value of SHR, SHRW, EXCLU, or MOD. If it does, then an internal control block was altered. Check your program for incorrect storage references. If none are found, contact IBM support. ISRLS035 INPUT not allowed - Only OUTPUT option is allowed with data
set allocated MOD. ExplanationAn LMOPEN service attempted to open a data ID for input when the data ID was allocated with the LMINIT service with a ENQ value of MOD. Programmer responseChange the LMINIT service that created the data ID to specify an ENQ value of SHR, SHRW, or EXCLU. The MOD value should only be used for writing to the end of a sequential data set. ISRLS036 Operation not supported - Statistics reset on an alias of
a member of a PDSE is not supported. ExplanationThis message is self explanatory. ISRLS040 Invalid STATS option - Specify either YES or NO for the STATS
parameter for LMMFIND. ExplanationSTATS parameter must be YES or NO. System actionLMMFIND ends with a return code of 12. User responseContact the responsible programmer. Programmer responseSpecify the STATS parameter as YES if you want the LMMFIND service to return statistics. Otherwise, specify the STATS parameter as NO. ISRLS041 Data set not opened - LMMFIND service requires the previous
successful completion of LMOPEN. ExplanationNo LMOPEN was done prior to invoking LMMFIND. System actionLMMFIND ends with a return code of 12. User responseContact the responsible programmer. Programmer responseAdd an LMOPEN invocation for the data ID used in the LMMFIND service. ISRLS042 Data set not partitioned - The LMMFIND service only works
with partitioned data sets. ExplanationThe LMMFIND service is used to find a member of a partitioned data set. The data set represented by the given data ID is not partitioned. System actionLMMFIND ends with return code 12. User responseContact the responsible programmer. Programmer responseChange the DATAID parameter to the DATAID for the partitioned data set to find the member name. ISRLS043 Member not found - Specified member 'aaaaaaaa'
not found in data set(s). ExplanationThe given member was not found in the data set(s) specified by the given data ID. System actionLMMFIND ends with return code 8. User responseContact the responsible programmer. Programmer responseThe response depends upon the design of the dialog. This may be an expected response. ISRLS044 Severe error - Unexpected return code aaaaaaaa from
common data set BLDL routine ISPCDB. ExplanationAn unexpected error occurred during BLDL processing.
The return code may be one of these:
System actionLMMFIND ends with return code 20. System programmer responseRecover the data set, if necessary. User responseContact the responsible programmer. Programmer responseVerify the input parameters to LMMFIND. Try accessing the member through Browse (option 1) to verify that the member exists as expected in the data set(s). ISRLS045 Severe error - I/O error trying to close out on read. ExplanationThis is an informational message. System actionLMMFIND ends with return code 20. ISRLS046 Not open for input - LMMFIND service requires the data set
to be opened for input. ExplanationThe data ID for the LMMFIND service must be opened for input before invoking the LMMFIND service. System actionLMMFIND ends with return code 12. User responseContact the responsible programmer. Programmer responseChange the OPTION to INPUT on the LMOPEN service for the specified data ID. ISRLS047 I/O error finding member - A permanent I/O error was detected
when searching the directory. ExplanationBLDL ended with return code 8. System actionLMMFIND ends with return code 8. System programmer responseRecover the data set, if necessary. User responseContact the responsible programmer. Programmer responseVerify the input parameters to LMMFIND. Try accessing the member through Browse (option 1) to verify that the member exists as expected in the data set(s). ISRLS048 Insufficient storage - Insufficient virtual storage was available
to search the directory. ExplanationThere is not enough virtual storage for ISPF to be able to read the directory. User responseIncrease virtual storage. ISRLS051 Invalid EXT option - The EXT parameter value must be NO or
omitted. ExplanationThe System Programmer has not enabled the recording of extended statistics. System programmer responseModify the ISPF Configuration table to enable extended statistics. User responseContact your System Programmer. ISRLS052 Invalid EXT option - The EXT parameter value must be NO or
YES ExplanationThe value passed for the LM service parameter
EXT was invalid. The valid values are:
User responseCorrect the parameter value and reissue the service call ISRLS055 Invalid statistics value - Current number of records must
be a positive number greater than 0. ExplanationThe LMMSTATS current number of records parameter contains an invalid value. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the current number of records to be a positive integer greater than 0. ISRLS056 Invalid statistics value - Initial number of records must
be a positive number greater than 0. ExplanationThe LMMSTATS initial number of records parameter contains an invalid value. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the current number of records to be a positive integer greater than 0. ISRLS057 Invalid statistics value - Number of modified records must
be a positive number greater than 0. ExplanationThe LMMSTATS number of modified records parameter contains an invalid value. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the current number of records to be a positive integer greater than 0. ISRLS060 Invalid mode specified - Specify either MOVE, LOCATE, INVAR
OR MULTX for mode parameter. ExplanationThe valid modes for the LMGET service are:
System actionLMGET service ends with return code 12. User responseContact the responsible programmer. Programmer responseSpecify the MODE parameter as MOVE, LOCATE, INVAR or MULTX. ISRLS061 Data set not opened - Data set is not opened for LMGET service. ExplanationThe data set(s) represented by the DATAID parameter of LMGET must be open. System actionLMGET service ends with return code 12. User responseContact the responsible programmer. Programmer responseOpen the data set(s) for the data ID, using the LMOPEN service, before calling LMGET. ISRLS062 Find member not done - For partitioned data sets, LMGET requires
previous successful LMMFIND. ExplanationIn order for LMGET to process the correct member, the LMMFIND service must be invoked before the LMGET service. System actionLMGET service ends with return code 12. User responseContact the responsible programmer. Programmer responseFind the member to be read by calling the LMMFIND service before calling LMGET. ISRLS063 Null DATALOC variable - For MOVE mode, DATALOC variable must
contain a value. ExplanationFor the LMGET MOVE mode, the DATALOC variable must contain a binary virtual storage address where the data read by LMGET is to be stored. System actionLMGET service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the variable, specified by the DATALOC parameter, to an address to store the data read by LMGET. ISRLS064 Invalid DATALOC variable - For MOVE mode, DATALOC variable
must have a positive numeric value. ExplanationFor the LMGET MOVE mode, the value specified by the DATALOC variable must be a valid address. All of the characters must be numeric and have a positive value. System actionLMGET service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the DATALOC variable to a valid address. ISRLS065 DATALOC var out of range - For MOVE mode, DATALOC variable
must have value <= (2**31)-1. ExplanationFor the LMGET service, the DATALOC variable must have a value of at least 1 but less than 2 147 483 647. System actionLMGET service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the DATALOC variable to a valid address. ISRLS066 I/O error on read - I/O error encountered while reading data
set. ExplanationA severe error occurred while attempting to read the data set(s) represented by the DATAID parameter on the LMGET service. System actionLMGET service ends with return code 12. System programmer responseRecover data, if necessary. User responseContact the responsible programmer. Programmer responseBrowse the data set to verify that it is not damaged. ISRLS067 Invalid record length - Maximum record length must be >
0 and <= aaaaaaaa ExplanationFor LMGET, the MAXLEN parameter is negative or zero. For MODE(MULTX) MAXLEN must also be less than or equal to 31,998. In all other cases it should be less than or equal to 32,760. System actionLMGET service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the MAXLEN parameter to a valid data length. ISRLS068 Not opened for input - Data set must be opened for input
for LMGET service. ExplanationThe LMGET service requires that the data set(s) represented by the DATAID parameter be open for input. System actionLMGET service ends with return code 12. User responseContact the responsible programmer. Programmer responseOn the LMOPEN service for the specified data ID, specify the INPUT option. ISRLS070 Invalid mode specified - Specify either MOVE, INVAR or MULTX
for mode parameter. ExplanationThe valid modes for the LMPUT service are:
System actionLMPUT service ends with return code 12. User responseContact the responsible programmer. Programmer responseSpecify the MODE parameter as MOVE, INVAR or MULTX ISRLS071 Data set not opened - Data set is not opened for LMPUT service. ExplanationThe data set represented by the DATAID parameter of LMPUT must be open. System actionLMPUT service ends with return code 12. User responseContact the responsible programmer. Programmer responseOpen the data set for the DATAID using the LMOPEN service before calling LMPUT. ISRLS072 Not opened for output - Data set is not opened for output
for LMPUT service. ExplanationThe LMPUT service requires that the data set represented by the DATAID parameter be open for output. System actionLMPUT service ends with return code 12. User responseContact the responsible programmer. Programmer responseOn the LMOPEN service for the specified data ID, specify the OUTPUT option. ISRLS073 Null DATALOC variable - DATALOC variable must either be an
address or the data for LMPUT. ExplanationThis message is self explanatory. ISRLS074 Invalid DATALOC variable - For MOVE mode, DATALOC variable
must have a positive numeric value. ExplanationFor the LMPUT MOVE mode, the value specified by the DATALOC variable must be a valid address. All of the characters must be numeric, and must be a positive value. System actionLMPUT service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the DATALOC variable to a valid address. ISRLS075 DATALOC var out of range - For MOVE mode, DATALOC variable
must have value <= (2**31)-1. ExplanationFor the LMPUT service, the DATALOC variable must have a value of at least 1 but less than 2 147 483 647. System actionLMPUT service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the DATALOC variable to a valid address. ISRLS076 I/O error on write - I/O error encountered while writing
data set. ExplanationA severe error occurred while attempting to write to the data set represented by the DATAID parameter on the LMPUT service. System actionLMPUT service ends with return code 12. System programmer responseRecover data, if necessary. User responseContact the responsible programmer. Programmer responseBrowse the data set to verify that it is not damaged. ISRLS077 Invalid record length - Record length must be positive and
between 1 and (2**15)-1. ExplanationFor LMPUT, the DATALEN parameter must not be negative, zero, or greater than 32 767. System actionLMPUT service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the DATALEN parameter to a valid data length. ISRLS080 Invalid member name - Member name 'aaaaaaaa'
is invalid. ExplanationMember name parameter contains invalid characters. System actionService ends with return code 12. User responseContact the responsible programmer. Programmer responseEnter a valid member name in the member name parameter. ISRLS081 Invalid STATS parameter - STATS parameter is invalid. Specify
either YES or NO. ExplanationThe STATS parameter must be YES, NO, or blank. System actionService ends with return code 12. User responseContact the responsible programmer. Programmer responseEnter a valid STATS parameter. ISRLS082 Member already exists - Directory already contains the specified
member name. ExplanationEither the LMMADD service or the LMMREN service failed because a member with the requested name already exists in the library. System actionService ends with return code 4. User responseContact the responsible programmer. Programmer responseFor the LMMADD service, either:
ISRLS083 Member not found - The specified member name 'aaaaaaaa'
not found in the directory. ExplanationThe requested member does not exist for the LMMDEL or LMMREN service. System actionService ends with return code 8. User responseContact the responsible programmer. Programmer responseEnsure that the correct member name is requested. No action is usually necessary for LMMDEL. ISRLS084 Member added - Member added to the data set. It did not
previously exist. ExplanationThis is an informational message. The LMMREP service could not find a member to replace. The member is added to the data set. ISRLS085 Not partitioned data set - Data set must be partitioned for
LMMADD, LMMREP, LMMDEL or LMMREN. ExplanationThe LMMADD, LMMREP, LMMDEL, and LMMREN services all operate on members of partitioned data sets. System actionService ends with return code 8. User responseContact the responsible programmer. Programmer responseEither ensure that the data set for the requested data ID is partitioned, or use the appropriate service to operate on sequential data sets. For example, to rename an entire data set, use the LMRENAME service. ISRLS086 Data set is not open - The data set must be open for LMMADD,
LMMREP, LMMDEL or LMMREN. ExplanationThe data set represented by the requested data ID is not open. System actionService ends with return code 12. User responseContact the responsible programmer. Programmer responseUse the LMOPEN service to open the data set before calling LMMADD, LMMREP, LMMDEL, or LMMREN. ISRLS087 Data set not for output - Must open data set for output for
LMMADD, LMMREP, LMMDEL, or LMMREN. ExplanationThe data set represented by the requested data ID must be open for output. System actionService ends with return code 12. User responseContact the responsible programmer. Programmer responseUse the OUTPUT option of the LMOPEN service for the requested data ID. ISRLS088 No record is written - LMMADD and LMMREP requires previous
successful LMPUT service. ExplanationThe LMMADD and LMMREP services are designed to add or replace a member of a partitioned data set. The LMPUT service writes the records to be used by LMMADD and LMMREP. System actionService ends with return code 14. User responseContact the responsible programmer. Programmer responseUse the LMPUT service to write records to the member before calling the LMMADD or LMMREP service to create or replace the member. ISRLS089 I/O error - Unexpected write error encountered. ExplanationThis message is self explanatory. ISRLS090 No space in directory - No space left in the directory of
the data set. ExplanationThere is no space left in the directory for the LMMADD, LMMREN, or LMMREP service to add the member. System actionService ends with return code 20. User responseContact the responsible programmer. Programmer responseReallocate the data set with more directory blocks. ISRLS091 Permanent I/O error - A permanent input or output error is
detected. ExplanationSTOW ended with return code 16. System actionService ends with return code 20. System programmer responseRecover the data set, if necessary. User responseVerify that the data set is not damaged. ISRLS092 DCB not opened - The specified data control block is not
open or is open for input. ExplanationSTOW ended with return code 20. System actionService ends with return code 20. System programmer responseRecover the data set, if necessary. User responseVerify that the data set is not damaged. ISRLS093 Not enough storage - Insufficient virtual storage is available
to perform STOW function. ExplanationSTOW ended with return code 24. System actionService ends with return code 20. System programmer responseRecover the data set, if necessary. User responseVerify that the data set is not damaged. ISRLS094 Invalid new member name - New member name 'aaaaaaaa'
is invalid. ExplanationThe new member name parameter for the LMMREN service contains invalid characters. System actionLMMREN service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnter a new member name parameter with valid characters. ISRLS095 Variable not found - Variable not found for member statistic
'aaaaaaaa'. ExplanationVariable requested was not found in any of the ISPF variable pools. System actionService ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the variable name is typed correctly. ISRLS096 No member name - A non-blank member name must be supplied ExplanationThe requested service operates on member(s). No member specification was given. System actionService ends with return code 12. User responseSupply a member specification ISRLS097 Member list error - Error building member list. ExplanationAn error was encountered when building a member list. System actionService ends with return code 12. ISRLS100 Data set is not open - The data set identified by data ID
'aaaaaaaa' is not open. ExplanationThe LMCLOSE service requires that the data set or sets represented by the requested data id be opened by the LMOPEN service. System actionThe LMCLOSE service ends with return code 8. User responseContact the responsible programmer. Programmer responseIf no LMOPEN is required by the dialog, remove the LMCLOSE service from the dialog. ISRLS101 Close failed - Close failed for data set identified by DATAID
'aaaaaaaa'. ExplanationThis message is self explanatory. ISRLS102 Unrecoverable I/O error - An unrecoverable read I/O error
occurred while closing data set. ExplanationLMCLOSE failed attempting to close the read buffer. System actionThe LMCLOSE service ends with return code 20. System programmer responseRecover the data sets if necessary. User responseContact the responsible programmer. Programmer responseEnsure that the data set or sets represented by the requested data ID are not damaged. ISRLS103 Unrecoverable I/O error - An unrecoverable write I/O error
occurred while closing data set. ExplanationThis message is self explanatory. ISRLS104 Unrecoverable error - An unrecoverable error occurred while
freeing member list. ExplanationLMCLOSE encountered a severe error while attempting to free a member list. System actionThe LMCLOSE service ends with return code 20. System programmer responseRecover the data sets if necessary. User responseContact the responsible programmer. Programmer responseEnsure that the data set or sets represented by the requested data ID are not damaged. ISRLS110 I/O error - I/O error closing data set represented by data
ID 'aaaaaaaa'. ExplanationAn error occurred while attempting to close the data set. System actionService ends with return code 20. System programmer responseBack up the data sets if necessary. User responseVerify that the data set is not damaged. ISRLS111 I/O error - I/O error freeing data set represented by data
ID 'aaaaaaaa'. ExplanationAn error occurred attempting to free the data set, or attempting to free internal storage. System actionService ends with return code 20. System programmer responseBack up the data set if necessary. User responseVerify that the data set is not damaged. Try the function again. If problem persists, contact the system programmer. ISRLS112 Severe error - Directory block size exceeds maximum of 256. ExplanationThe PDF common member list routine detected a data set that had a directory block greater than 256 bytes, the maximum supported by PDF. System programmer responseReallocate or recover the data set as necessary. User responseContact your system programmer. ISRLS113 Can't save member list - The SAVE option is valid only when
no member list exists for the data ID. ExplanationThe LMMLIST service has already been invoked with the LIST option. The SAVE option cannot be used when there is already an active member list for a data ID. System actionLMMLIST ends with return code 8. User responseContact the responsible programmer. Programmer responseIf you need to write the member list to
a data set and process members within the member list, invoke the
LMMLIST service with the SAVE option either
ISRLS120 Invalid option - Specify either LIST, FREE, or SAVE. ExplanationThe Option parameter of the LMMLIST service must be LIST, FREE, SAVE, or blank. Blank defaults to LIST. System actionLMMLIST service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnter a valid value for the OPTION parameter. ISRLS121 Invalid STATS parameter - Specify either YES or NO. ExplanationThe STATS parameter of the LMMLIST service must be YES, NO, or blank. Blank defaults to NO. System actionService ends with return code 12. User responseContact the responsible programmer. Programmer responseEnter a valid value for the STATS parameter. ISRLS122 Data set not open - LMMLIST requires prior successful completion
of LMOPEN. ExplanationThe LMOPEN service must be invoked against the requested data ID before invoking the LMMLIST service. System actionLMMLIST service ends with return code 12. User responseContact the responsible programmer. Programmer responseUse the LMOPEN service to open the requested data ID, before calling the LMMLIST service. ISRLS123 Data set not partitioned - LMMLIST requires the data set
to be a partitioned data set. ExplanationThe LMMLIST service gets a list of members for partitioned data sets only. System actionLMMLIST service ends with return code 12. User responseContact the responsible programmer. Programmer responseUse the LMMLIST service on the correct partitioned data set. ISRLS124 Empty member list - There are no members in this data set. ExplanationThis is an informational message. LMMLIST service ends with return code 4. ISRLS125 End of member list - No more members in this data set. ExplanationThis is an informational message. LMMLIST service ends with return code 8. ISRLS126 No member list - Member list does not exist for this data
set. ExplanationThe LMMLIST service attempted to free a member list that does not exist. System actionLMMLIST service ends with return code 8. User responseContact the responsible programmer. Programmer responseVerify that you are attempting to FREE a member list that was previously built. ISRLS127 Severe error - Open error occurred while building member
list. ExplanationAn ABEND occurred during open processing. System actionLMMLIST service ends with return code 20. System programmer responseRecover the data sets, if necessary. User responseContact the responsible programmer. Programmer responseEnsure that the data set or sets represented by the requested data ID have not been damaged. ISRLS128 Severe error - I/O error occurred while building member list. ExplanationAn error occurred reading directory blocks. System actionLMMLIST service ends with return code 20. System programmer responseRecover the data sets, if necessary. User responseContact the responsible programmer. Programmer responseEnsure that the data set or sets represented by the requested data ID have not been damaged. ISRLS129 Severe error - BLDL error occurred while building member
list. ExplanationBLDL failed during member list processing. System actionLMMLIST service ends with return code 20. System programmer responseRecover the data sets, if necessary. User responseContact the responsible programmer. Programmer responseEnsure that the data set or sets represented by the requested data ID have not been damaged. ISRLS130 Free member list failed - Error occurred while freeing member
list. ExplanationAn error occurred while attempting to free storage for the member list. System actionLMMLIST service ends with return code 20. ISRLS131 Invalid member name - Member name "aaaaaaaa"
is invalid or has not been initialized to blanks. ExplanationThe MEMBER parameter of the LMMLIST service contains invalid characters. System actionThe LMMLIST service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the member name variable contains either blanks or a valid member name. ISRLS132 Member name too long - Member name must be 1 to 8 characters
long. ExplanationThe member name variable must be able to contain a value with a length of 8 characters. System actionThe LMMLIST service ends with return code 8. User responseContact the responsible programmer. Programmer responseIf you are using a program interface, declare the member name variable to be 8 characters long. If you are using a command interface, ensure that the member name variable contains 8 characters. Pad the member name with blanks if necessary. ISRLS133 Invalid statistics value - Version number must be a positive
number from 1 to 99. ExplanationThe LMMSTATS version number parameter contains an invalid value. System actionLMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the version number to be a positive integer between 1 and 99, inclusive. ISRLS134 Invalid statistics value - Modification level must be a positive
number from 0 to 99. ExplanationThe LMMSTATS modification level parameter contains an invalid value. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the modification level to be a positive integer between 0 and 99, inclusive. ISRLS135 Invalid statistics value - Current number of records must
be a positive number from 0 to 65535. ExplanationThe LMMSTATS current number of records parameter contains an invalid value. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the current number of records to be a positive integer between 0 and 65 535, inclusive. ISRLS136 Invalid statistics value - Initial number of records must
be a positive number from 0 to 65535. ExplanationThe LMMSTATS initial number of records parameter contains an invalid value. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the initial number of records to be a positive integer between 0 and 65 535, inclusive. ISRLS137 Invalid statistics value - Number of modified records must
be a positive number from 0 to 65535. ExplanationThe LMMSTATS number of modified records parameter contains an invalid value. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseSet the number of modified records to be a positive integer between 0 and 65 535, inclusive. ISRLS138 Invalid statistics value - Creation date or last modified
date 'aaaaaaaa' is out of range. ExplanationThe creation date does not exist. Either the month value is greater than 12, or the day value exceeds the number of days for the given month. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnter a valid creation date. ISRLS139 Invalid statistics value - Last modified time 'aaaaaaaa'
is out of range. ExplanationThe last modified time does not exist. Either the hours are not between 00 and 23 inclusive, or the minutes are not between 00 and 59 inclusive. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnter a valid creation date. ISRLS140 Missing ZLCDATE/ZLMDATE - Must specify creation date and
last update date for member statistics. ExplanationThe LMMSTATS service requires that the ZLCDATE and ZLMDATE variables be set to valid dates. These variables must be in an ISPF variable pool. System actionLMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the ZLCDATE and the ZLMDATE variables are in ISPF variable pool and contain valid dates. ISRLS141 Invalid statistics value - Version number (aaaaaaaa)
must be positive number from 1 to 99. ExplanationEither the version number value is too long, or it contains nonnumeric characters. System actionLMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the ZLVERS variable is in an ISPF variable pool and contains a valid version number. ISRLS142 Invalid statistics value - Modification level (aaaaaaaa)
must be positive number from 0 to 99. ExplanationEither the modification level value is too long, or it contains nonnumeric characters. System actionLMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the ZLMOD variable is in an ISPF variable pool and contains a valid version number. ISRLS143 Invalid date aaaaaaaa - Created and last
modified dates must be in format YY/MM/DD or YYYY/MM/DD. Use the
"CREATED" AND "MODDATE" parameter for YY/MM/DD format and the "CREATED4"
and "MODDATE4" parameter for YYYY/MM/DD format. ExplanationThe creation date or modification date passed to the LMMSTATS service was either of incorrect length or contained incorrect data. The date must be 8 characters if the 2 character year format is used (YY/MM/DD, for example) or 10 characters if the 4 character year format is used (YYYY/MM/DD, for example). System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the dates passed to LMMSTATS via the CREATED, CREATED4, MODDATE and MODDATE4 parameters are of correct length and contain valid dates. ISRLS144 Invalid date aaaaaaaa - Created and last
modified dates must be in format YY/MM/DD or YYYY/MM/DD. Use the
"ZLCDATE" and "ZLMDATE" dialog variables for YY/MM/DD format and the
"ZLC4DATE" and "ZLM4DATE" dialog variables for YYYY/MM/DD format. ExplanationThe creation date or modification date passed to an ISPF service via the ZLCDATE, ZLC4DATE, ZLMDATE or ZLM4DATE had either an incorrect length or contained incorrect data. The date must be 8 characters if the 2 character year format is used (YY/MM/DD, for example, via variable ZLMDATE or ZLMDATE) or 10 characters if the 4 character year format is used (YYYY/MM/DD, for example, via variable ZLC4DATE or ZLM4DATE). System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the dates passed to ISPF via the ZLCDATE, ZLC4DATE, ZLMDATE and ZLM4DATE variables are of correct length and contain valid dates. ISRLS145 Invalid statistics value - Last modified time (aaaaaaaa)
must be in format HH:MM or HH:MM:SS ExplanationEither the ZLMTIME value does not have 5 or 8 characters or does not have a colon (:) as the third character in the 5 character format and/or as the sixth character in the 8 character format. System actionLMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the ZLMTIME variable is in an ISPF variable pool and contains a valid time. ISRLS146 Invalid statistics value - Current number of records (aaaaaaaa)
must be positive number from 0 to 65535. ExplanationEither the ZLCNORC variable value is too long, or contains nonnumeric characters. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the ZLCNORC variable is in an ISPF variable pool and contains a valid number between 0 and 65 535. ISRLS147 Invalid statistics value - Initial number of records (aaaaaaaa)
must be positive number from 0 to 65535. ExplanationEither the ZLINORC variable value is too long, or contains nonnumeric characters. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the ZLINORC variable is in an ISPF variable pool and contains a valid number between 0 and 65 535. ISRLS148 Invalid statistics value - Number of modified records (aaaaaaaa)
must be positive number from 0 to 65535. ExplanationEither the ZLMNORC variable value is too long, or contains nonnumeric characters. System actionThe LMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the ZLMNORC variable is in an ISPF variable pool and contains a valid number between 0 and 65 535. ISRLS149 Invalid statistics value - User ID (aaaaaaaa)
must be 1 to 7 characters. ExplanationThe ZLUSER variable value contains 8 or more characters. System actionLMMSTATS service ends with return code 12. User responseContact the responsible programmer. Programmer responseEnsure that the ZLUSER variable is in an ISPF variable pool and contains a valid user ID. ISRLS160 Close data set failed - Close the control file unsuccessfully. ExplanationThe close of the control file failed. System programmer responseEnsure that the control file is not damaged and can be accessed from the system. User responseIf the problem persists, contact the system programmer. ISRLS161 Free storage failed - Free the storage of TFD for the control
file unsuccessfully. ExplanationThe storage for the TFD of the control file could not be freed. System programmer responseIf the problem persists, contact IBM support. User responseIf the problem persists, contact the system programmer. ISRLS162 Close data set failed - Close "from" data set failed. ExplanationThe close of the FROM data set was not successful. System programmer responseEnsure that the FROM data set is not damaged and can be accessed from the system. User responseIf the problem persists, contact the system programmer. ISRLS163 Free data set failed - Free "from" data set failed. ExplanationThe allocation of the FROM data set could not be completed successfully. System programmer responseEnsure that the FROM data set is not damaged and can be accessed from the system. User responseIf the problem persists, contact the system programmer. ISRLS170 Alias name not supported - LMERASE service does not support
erasing alias data sets. ExplanationThe name that was specified is an alias. LMERASE does not support alias names. System actionThe alias and data sets are not deleted. User responseUse the data set name instead of the alias name. ISRLS171 Data set not expired yet - The PURGE(YES) keyword must be
used to delete the data set. ExplanationThe data set has an expiration date that has not yet been reached. The PURGE(YES) keyword must be specified to delete this data set. System actionThe data set is not deleted. User responseSpecify the PURGE(YES) keyword to delete the data set. ISRLS172 Obtain macro failed - Obtain format 1 data set control block
failed. ExplanationLMERASE was not able to access the format 1 data set control block. System actionThe data set is not deleted. System programmer responseVerify that the device containing the data set is online and can be accessed. Verify that the catalog containing the data set is also available. User responseVerify that the data set name is valid and available. ISRLS173 Invalid PURGE value - The PURGE keyword must have a value
of YES or NO. ExplanationThe value specified for PURGE was not YES or NO. System actionThe data set is not deleted. User responseSpecify either YES or NO for the PURGE value, or allow the value to default. ISRLS174 Invalid parameter - You must specify either PROJECT/GROUP/TYPE
or DATASET for the LMERASE service. ExplanationWhen invoking the LMERASE service to delete a data set, you must specify either a three-level qualified data set via the PROJECT, GROUP, and TYPE parameters, or an MVS partitioned or sequential data set via the DATASET parameter. Neither was specified. System actionThe data set is not deleted. User responseSpecify either PROJECT/GROUP/TYPE or DATASET on the LMERASE call. ISRLS175 Invalid parameter - For the LMERASE service, If PROJECT is
specified, GROUP and TYPE must also be specified. ExplanationThe LMERASE service was invoked with the PROJECT parameter specified, but either the GROUP or TYPE parameter was missing. System actionThe data set is not deleted. User responseEither specify PROJECT, GROUP and TYPE, or use the DATASET parameters to specify the data set name. ISRLS176 Invalid statistics value - Last modified second (ZLMSEC)
must be a number between 0 and 59. ExplanationEither the ZLMSEC value is not numeric or it is out of range. System actionThe second value is not accepted. User responseContact the responsible programmer. Programmer responseEnsure that the ZLMSEC variable is in an ISPF variable pool and contains a valid value. ISRLS190 No new name specified - Must specify either NEWPROJ, NEWGROUP,
or NEWTYPE for LMRENAME. ExplanationA new name was not supplied for the LMRENAME command. One or more of these parameters must be supplied: NEWPROJ, NEWGROUP, NEWTYPE. System actionThe name of the data set is not changed. User responseSpecify at least one of the values used to form the new data set name. ISRLS191 Invalid new name - 'aaaaaaaa' specified
for 'bbbbbbbb' is an invalid name. ExplanationThe value aaaaaaaa for the bbbbbbbb parameter forms an invalid data set name. System actionThe data set is not renamed. User responseChange the value for the bbbbbbbb parameter to specify a value that will create a valid data set name. ISRLS192 New name same as old - New ISPF library name specified for
LMRENAME is the same as old name. ExplanationThe values specified for LMRENAME results in the new data set name being the same as the old data set name. System actionThe data set is not renamed. User responseIf the data set is to be renamed, specify values that will result in a name different from the original data set name. ISRLS193 Alias name not supported - LMRENAME does not support renaming
alias data sets. ExplanationThe data set name specified for renaming using LMRENAME must not be an alias. System actionThe data set is not renamed. User responseSpecify a non-alias data set name. ISRLS194 Catalog unavailable - Catalog does not exist, is not open,
or do not allocate bit is on. ExplanationLMRENAME could not get access to the catalog.
One of these conditions may exist:
System actionThe data set is not renamed. System programmer responseEnsure that the catalog for the data sets specified to the LMRENAME service exists, is open, and that the do not allocate bit is not set. User responseVerify that both data sets specified to the LMRENAME service can be accessed through the catalog. Notify the system programmer of any catalog problems. ISRLS195 Authorization failed - The user is not authorized to perform
the operation. ExplanationThe user is not authorized to update the catalog with a new data set name. System actionThe data set is not renamed. User responseVerify that you have authority to update the data set name in the catalog. Programmer responseEnsure that the user has authority to update the data set name in the catalog. ISRLS196 Name already catalogued - Entire or partial name already
catalogued. ExplanationThe new name for the data set already exists in the catalog. System actionThe data set is not renamed. User responseChange the parameters to the LMRENAME service to specify a new name that is unique. ISRLS197 Index does not exist - The index structure necessary to catalog
the data set does not exist. ExplanationThe needed index structure to catalog the new data set name does not exist. System actionThe data set is not renamed. System programmer responseEnsure that the index structure is set up for the catalog that will contain the new data set name. User responseContact the system programmer to check that the catalog for the new data set name is properly set up. ISRLS198 No space in catalog - There is insufficient space on the
catalog data set. ExplanationThere is not enough space in the catalog that would contain the new data set name to add it to the catalog. System actionThe data set is not renamed. System programmer responseEnsure that the catalog for the new data set name is large enough. User responseNotify the system programmer that the catalog does not have enough space. ISRLS199 Uncatalog error - Uncatalog failed for data set aaa(44). ExplanationThe old data set name aaa(44) could not be uncataloged because it could not be found in the catalog. System programmer responseEnsure that there are no problems with the catalog for the old data set name. User responseVerify that the old data set name was specified correctly. ISRLS200 Data set not catalogued - Catalog error, Rtn code=aaaaaaaa (dec),
r0=bbbbbbbb (hex), r1=cccccccc (hex). ExplanationAn error occurred while attempting to catalog or uncatalog a data set. System programmer responseEnsure that the catalogs for both the new and old data set names are available to users for both read and update accesses. User responseContact the system programmer. ISRLS201 DSCB not on VTOC - The VTOC does not contain the format-1
DSCB for data set to be renamed ExplanationThe format-1 DSCB for the old data set name could not be found in VTOC of the volume where the catalog indicated that the data set exists. System programmer responseVerify that the catalog information for the data set is correct, and that the VTOC for the volume containing the data set is correct. User responseNotify the system programmer. ISRLS202 Data set pswd protected - Rename failed. Data set is password
protected. ExplanationThe data set is password protected and cannot be renamed without the password. User responseUse option 3.2 or another utility that supports specifying the password of the old data set to rename the data set. ISRLS203 New name already exists - A data set with the new name already
exists on the volume. ExplanationA data set with the same name as the new data set name already exists on the same volume. The existing data set may be uncataloged. User responseEither remove the existing data set with the same name as the new data set name, or specify a different new name. ISRLS204 Permanent I/O error - Permanent I/O error, invalid format-1
DSCB found, or error from CVAF. ExplanationA permanent I/O error occurred when accessing the format-1 DSCB in the VTOC of the volume of the data set that is being renamed. System programmer responseCheck the volume for I/O errors. User responseNotify the system programmer. ISRLS205 Volume not mounted - Volume not mounted or no device available
to mount the volume. ExplanationThe volume that contains the data set being renamed is not mounted to the system. User responseMount the volume containing the data set. ISRLS206 Volume not mounted - The operator is unable to mount the
volume. ExplanationThe volume that contains the data set being renamed is not mounted to the system. The mount request failed. User responseContact the system operator to determine the reason that the volume could not be mounted. ISRLS207 Data set in use - Data set not renamed because it is being
used. ExplanationThe data set is currently allocated to a ddname. User responseEnsure that you do not have the data set allocated to a ddname and that other users are not using the data set. ISRLS208 Authorization failed - Data set is RACF protected. The user is not alter authorized. ExplanationThe user does not have sufficient authority to rename the data set. ALTER authority is required for data sets that are RACF® protected. User responseEnsure that you are given sufficient authority to rename the data set. Authority is required for both the old and new data set names. ISRLS209 Rename error - Rename error, Rtn code=aaaaaaaa (dec),
status code=bbbbbbbb (dec). ExplanationThe rename service failed with return code aaaaaaaa and status code bbbbbbbb. System programmer responseVerify that the catalog for the new and old data set names and the VTOC for the volume containing the data set can be read and updated. User responseContact the system programmer. ISRLS210 Device code not found - DEVTYPE macro failed. Return code
= aaaaaaaa. ExplanationThis message is self explanatory. ISRLS211 Invalid ISPF libraries - Concatenated libraries must have
same project and type values. ExplanationAll data sets in the ddname concatenation must have the same project (high level qualifier) and type (last qualifier). User responseEnsure that the data sets concatenated to the ddname all have the same project and type values. ISRLS212 Members not replaced - aaaaaaaa members
not replaced, bbbbbbbb members cccccccc. ExplanationMembers of the same name exist in the source and target data sets. The members with the same name as those in the target data set were not replaced since the REPLACE option was not specified. User responseEither specify the REPLACE option or specify a TOMEM name that does not match an existing member in the target data set. ISRLS213 'To' member in use - aaaaaaaa members
not bbbbbbbb, cccccccc members bbbbbbbb ExplanationTarget members of the copy or move were in use. User responseEnsure that you or another user are not editing or in some other way using the member that is the target of the operation. ISRLS214 'From' member in use - aaaaaaaa members
not bbbbbbbb, cccccccc members bbbbbbbb ExplanationMembers were not copied or moved since they were in use. User responseEnsure that the members in the FROM data set are not in use by edit or another utility. ISRLS291 Data set is a PDSE - A PDSE does not need to be compressed. ExplanationA compress was issued against a PDSE data set. PDSE data sets do not require a compress. User responseContact the responsible programmer. Programmer responseBefore issuing the LMCOMP service, determine if the data set is a PDSE. ISRLS300 Write failed with abend - Abend code of 'aaaaaaaa'
during write. See system message for details. ExplanationA data set full condition caused an abend. User responseThis message is most likely the result of a PDF service invocation. Contact the responsible programmer. Programmer responseDetermine the service call that was invoked when the abend occurred. Possible services are: LMPUT, LMCOPY, LMPROM, and LMACT. Check the data sets used by the service for space. Reallocate the data sets with more space, if possible. ISRLS301 Close failed with abend - Abend code of 'aaaaaaaa'
during close. See system message for details. ExplanationA data set close resulted in an abend. System programmer responseCheck the data set and packs. If you are unable to discern the reason for the close abend, contact IBM support. User responseThis error is most likely the result of an PDF service call that issued a close data set command. Contact the responsible programmer. Programmer responseDetermine the PDF service call that resulted in the abend. Check the data set. If you are unable to discover the reason for the close abend, contact your system programmer. ISRLS302 Unrecoverable I/O error - An unrecoverable I/O error was
detected during a write request. ExplanationAn I/O error occurred during a write to data set request. User responseIf this is as a result of a PDF service request, contact the responsible programmer. Programmer responseDetermine the PDF service and the data set(s) in use. Attempt to write to the data set without using the service. If you are able to do this, try the service again. If the failure recurs, contact IBM support. ISRLS303 STOW failed with abend - Abend code of 'aaaaaaaa'
during STOW. See system message for details. ExplanationA STOW procedure resulted in an abend. User responseFollow the recommendations in System Messages. ISRLS304 Write failed RECFM error - Invalid record format specified
for output data set. ExplanationA write to a data set failed because the output data set is of an invalid record format. User responseIf you can identify the output data set, reallocate it with an acceptable record format; otherwise, contact the responsible programmer. Programmer responseReallocate the data set with the correct record format. ISRLS305 Write failed on pack - Invalid to pack undefined records. ExplanationAn attempt was made to pack a data set that was allocated as a undefined record format. User responseIf this message is a result of a PDF service call, contact the responsible programmer. Programmer responseDetermine the record format of the data set before issuing the service call. ISRLS306 Write failed on pack - Records already in packed format. ExplanationThe data set is already packed. User responseIf this message is the result of a service call, contact the responsible programmer. Programmer responseEliminate unnecessary pack requests. ISRLS307 Started task ISPLOG fail - Previous write to started task's
ISPLOG failed. ExplanationThe started task attempted to write to the ISPLOG but could not. System programmer responseDetermine if the started task has authority to write to the ISPLOG data set. User responseContact the system programmer. ISRLS308 Started task ISPLOG fail - Write to started task isplog abended
with 'aaaaaaaa'. ExplanationAn abend occurred on the write to the started task's ISPLOG. User responseFollow the recommendations in System Messages. ISRLS309 Internal program error. - STAE failed during initialization
in module 'aaaaaaaa' ExplanationAn internal error occurred within an PDF module. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS310 IEBCOPY interface failed - The listing data set aaa(44) could
not be allocated, opened or written to. ExplanationThis is an informational message. ISRLS311 Data set not partitioned - Data set for the compress is not
a partitioned one. ExplanationThe compress command is allowed only for partitioned data sets. ISRLS312 Service not available - Authorized IEBCOPY service not available. ExplanationAn attempt to attach IEBCOPY resulted in failure. System programmer responseVerify that IEBCOPY exists and that the user has proper authority. User responseContact your system programmer. ISRLS313 Compress not done - Exit return code indicates data set not
eligible for compression. ExplanationYour site-developed compress exit determined the data set was not eligible for compression. User responseContact the responsible programmer. Programmer responseValidate the compress exit. ISRLS314 Reserve failed - Unable to reserve the DASD volume at this
time. ExplanationThis is an informational message. User responseTry this operation again at a later time. ISRLS315 Error on write - Error writing IEBCOPY control cards. ExplanationAn attempt at writing IEBCOPY control cards has failed. System programmer responseDetermine cause for IEBCOPY failure. User responseContact your system programmer. ISRLS316 Open error - Data set is already opened. It cannot be opened
during compression. ExplanationAnother task has opened the data set. User responseTry again later. ISRLS317 Invalid disposition - Data set must be allocated exclusively.
Use ENQ(EXCLU) in LMINIT service. ExplanationThe data set was not allocated exclusively as required by the LMINIT service. User responseContact the programmer responsible for coding the LMINIT service. Programmer responseValidate the program issuing the LMINIT service. ISRLS318 Data set unmovable - Unmovable data sets cannot be compressed.
Compress aborted. ExplanationCompress alters the location of members within PDS storage. Because your PDS is unmovable, the compression cannot take place. ISRLS319 Concatenation exists - Concatenated libraries are not allowed
with the LMCOMP service. ExplanationThis is an informational message. ISRLS320 Authorization failed - You are not authorized to use the
IEBCOPY service. ExplanationThis message is self-explanatory. System programmer responseGive the user the necessary authorization, if appropriate. User responseIf you feel you require authorization, contact your system programmer. ISRLS321 IEBCOPY interface failed - Control card data set could not
be allocated or opened. ExplanationISPF was unable to allocate or open the temporary data set that holds IEBCOPY control cards. System actionIf a system failure occurred, correct the failure. System programmer responseThis is most likely either an authorization failure or a system failure. Verify the user's authorization. Verify that a system failure did not occur. User responseReissue the compress or MOVE or COPY request. If the problem recurs, contact your system programmer. ISRLS322 LMCOMP recursion error - Error attempting to use LMCOMP in
a recursive fashion. ExplanationYour installation-defined compress user exit routine identified a recursion error. User responseContact the responsible programmer. Programmer responseVerify the compress exit logic. ISRLS323 Compress failed - ISPF was unable to compress specified data
set. ExplanationISPF received a nonzero return code from IEBCOPY when attempting to compress a data set through the LMCOMP service. User responseThe IEBCOPY messages were written to DDNAME ISPLSTx (where x is the logical screen number that the request was issued from) if the ISPLSTx DDNAMEs were preallocated before entering ISPF, or to a data set named 'user ID.SPFLISTx.CNTL'. Refer to these messages for details on the IEBCOPY failure. ISRLS324 Compress exit error - Unable to allocate data set while using
the compress exit. ExplanationYour installation-defined user exit issued a data set allocation error. User responseContact the responsible programmer. Programmer responseVerify the data set allocation logic in your compress exit. ISRLS325 Compress exit error - Data set specified not cataloged. ExplanationYour installation-defined compress exit indicated a data set catalog error. User responseContact the responsible programmer. Programmer responseVerify that all data sets used by the exit exist and are cataloged, if applicable. ISRLS326 Compress exit error - Error in compress exit, ISPF will attempt
to continue. ExplanationYour installation-defined compress exit issued an error. User responseContact the responsible programmer. Programmer responseDetermine the compress exit failure. ISRLS327 Compress exit error - Bad return from compress exit. Error
unknown. ExplanationYour installation-defined compress exit issued an unknown return code. User responseContact the responsible programmer. Programmer responseDetermine the reason for the failure. ISRLS328 Compress exit error - Unable to execute compress exit. ExplanationISPF was unable to execute your installation-defined compress exit. User responseContact the responsible programmer. Programmer responseVerify the user exit exists and can be accessed. ISRLS329 Severe error - Unable to continue LMCOMP service. Compress
aborted. ExplanationA severe error caused the compress to be aborted. System programmer responseThis is likely to be the result of a system failure. Isolate the cause of the error. User responseContact your system programmer. ISRLS330 IEBCOPY warning - IEBCOPY warning messages were issued and
previously displayed for member aaaaaaaa.. IEBCOPY
messages may be found in data set bbb(44).. If
you are running from a member list you can press Enter to process
any other selected members or enter END command to exit member list. ExplanationA return code 4 was returned from IEBCOPY during the Move or Copy operation. The IEBCOPY listing was previously displayed. System programmer responseCheck for a system failure, such as a faulty pack. User responseRefer to the IEBCOPY listing and documentation for assistance. ISRLS331 Directory error - Directory error on member 'aaaaaaaa'. ExplanationAn attempt to STOW the member failed. System programmer responseCheck for a system failure, such as a faulty pack. User responseContact your system programmer. ISRLS332 IEBCOPY failed - IEBCOPY failed during copy. The IEBCOPY
error listing was previously displayed and may be found in data set aaa(44).. ExplanationA return code 8 or greater was returned from IEBCOPY during the Move or Copy operation. The IEBCOPY listing was previously displayed and may be found in data set aaa(44).. User responseRefer to the IEBCOPY listing and documentation for assistance in debugging the error. ISRLS333 Directory full - Directory full; unable to STOW member 'aaaaaaaa'. ExplanationThe directory entries for the data set have been filled. User responseIf you are able:
ISRLS334 RECFM = U not supported - Undefined record formats are not
supported in the 'aaaaaaaa' service. ExplanationRecord format U (undefined) is not allowed for the aaaaaaaa. service. User responseDetermine the correct record format for this data set. ISRLS335 IEBCOPY failed - IEBCOPY failed during copy. An IEBCOPY
listing was created and is in data set aaa(44).. ExplanationA nonzero return code was returned from IEBCOPY during the Move or Copy operation. The IEBCOPY SYSPRINT listing can be found in data set aaa(44).. User responseRefer to the IEBCOPY listing and documentation for assistance in debugging the error. ISRLS336 Invalid parameters - The DELETE keyword must be specified
alone. ExplanationOnly the keyword DELETE is allowed. Programmer responseSpecify only the DELETE keyword. ISRLS337 Invalid open - Data set not opened for input. ExplanationThe data set was opened but not for input. Programmer responseIf the LMMOPEN service was used, verify that the data set was opened for input. ISRLS338 Data set not partitioned - Sequential data sets are not valid
with the LMMSTATS service. ExplanationThe LMMSTATS service requires that the data set be partitioned. User responseReallocate the data set as partitioned. ISRLS339 Compress failed - Compress done by the compress exit failed. ExplanationThe installation-written compress exit failed. System programmer responseVerify that no system failures occurred. User responseAttempt the compress again. If the failure recurs, contact your system programmer. ISRLS340 Invalid record format - An undefined record format can only
exist as a partitioned data set. ExplanationA record format of U is only valid for partitioned data sets. User responseVerify that the number of directory entries is greater than 0. ISRLS341 Open error - FROM sequential data sets cannot be open prior
to using LMMOVE. ExplanationThe FROM data set was opened prior to the LMMOVE service call. User responseContact the responsible programmer. Programmer responseVerify that a previous service did not leave the FROM data set open. ISRLS342 Data set open for output - "From" data set must be opened
for input. ExplanationThe FROM data set was opened for output instead of input. User responseContact the responsible programmer. Programmer responseCorrect the service call. ISRLS343 DISP=MOD invalid - Disposition of mod not allowed for packed
data sets. ExplanationPacked data sets are not allowed a disposition of MOD. User responseEither change the disposition or remove the pack request. ISRLS344 Pack failed - Specifying DISP=MOD is invalid if "to" data
set has packed data. ExplanationWhen using LMCOPY and LMMOVE services and appending data to a sequential data set by using a TO data set disposition of MOD, the target output data set cannot be an existing data set that contains packed data. User responseEither unpack the data in the target sequential data set, or specify a different target data set that is not packed. ISRLS345 Read error on get - Unable to read the first record from
the target sequential file. ExplanationWhen copying to a sequential data set, PDF reads the first record of that data set to see if it contains packed or unpacked data. PDF encountered an I/O error while attempting to read that first record and cannot continue your request. User responseContact your system programmer for assistance determining the cause of the I/O error. ISRLS348 Invalid record format - The "from" or "to" data set has RECFM
= U. They must both be U. ExplanationIf either the FROM or TO data set has a record format of U (undefined), then both data sets must have record format U. User responseReallocate one of the data sets or forgo the MOVE/COPY. ISRLS349 Pack error - Packing is not allowed with undefined record
formats. ExplanationA pack option cannot be requested for data sets whose record format is U (undefined). User responseRemove the pack request from the service. ISRLS351 Data set unmovable - Input data set cannot be moved. ExplanationUnable to move this data set. User responseCheck that the data set you are attempting to move is not the input data set. ISRLS352 Output blksize too small - Output data set block size must
be equal or greater than input. ExplanationA MOVE or COPY has been requested in which the TO data set has a smaller block size than the FROM data set. User responseReallocate the TO data set or choose another data set. ISRLS353 Invalid SCLM setting - The SCLM parameter value must be ON,
OFF or ASIS ExplanationThe value passed for the LMMSTATS parameter SCLM
was invalid. The valid values are:
User responseCorrect the parameter value and reissue the service call ISRLS354 'aaaaaaaa' terminated - 'aaaaaaaa'
has been terminated due to truncation continue processing. ExplanationSome records may be truncated in the TO data set due to block size incompatibility. User responseEither accept the truncation or cancel the action. ISRLS355 Member name is blank - Input member name must be specified
for partitioned data sets. ExplanationAn input data set member name must be specified. User responseSpecify the member to MOVE or COPY. ISRLS356 Member name is required - A new member name must be specified
when from data set is sequential and to data set is partitioned. ExplanationAn output member name for partitioned data sets must be specified. User responseSpecify the output member to MOVE or COPY. ISRLS357 Member name not allowed - Member name 'aaaaaaaa'
not allowed with a sequential file. ExplanationA sequential file does not contain members. User responseBlank out the member name. ISRLS358 Invalid data sets - Same data sets not allowed when processing
'aaaaaaaa' service. ExplanationThe TO and FROM data set names are identical. User responseCorrect one of the data set names. ISRLS359 Concatenation is invalid - The "to" data ID contains concatenated
libraries. This is not allowed. ExplanationConcatenated libraries are not allowed for the TO data set. User responseContact the responsible programmer. Programmer responseCorrect the concatenation error. ISRLS360 New output name required - TO data set name and FROM data
set name are the same. Enter a different TO data set name, or enter
a member name (the FROM member will be copied/moved and renamed to
the new member name). ExplanationThe TO data set name is the same as the FROM data set name or blank. User responseSpecify a TO data set name that is different from the FROM data set name. Or enter a member name (the member will be renamed). ISRLS361 Member not found - Member 'aaaaaaaa' not
found in specified input library. ExplanationThe member does not exist in the input library. User responseMake sure the specified member name is correct. ISRLS362 Open error - 'aaaaaaaa' service requires
the "to" data IDs not to be opened. ExplanationThe specified service requires that the TO data set be closed when the service is invoked. User responseContact the responsible programmer. Programmer responseIssue an LMFREE for the TO data ID before invoking the service. ISRLS363 Concatenation is invalid - Concatenated libraries are not
allowed with the 'aaaaaaaa' service. ExplanationThe specified service does not allow concatenated libraries. User responseSpecify a library that is not part of a concatenation. ISRLS364 Output name not allowed - Output name 'aaaaaaaa'
not allowed when using member lists. ExplanationThe TO member name is not allowed when using member lists. User responseRemove the TO member name. ISRLS365 I/O error or BLDL - I/O error or BLDL on member build. ExplanationA severe internal error has occurred. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS366 RECFM=U not supported - Undefined record formats are only
supported with INDEX parameter of the LMPRINT service. ExplanationRecord format U (undefined) can only be used with the INDEX parameter of the LMPRINT service. LMPRINT does not support printing individual load module members. User responseSpecify either the INDEX parameter, or a data set that is not record format U. ISRLS367 Invalid keyword - LMF is no longer supported in this release
of ISPF, the "LOCK" keyword is not valid. For ISPEXEC calls, remove
the LOCK keyword. For ISPLINK calls, pass a blank for the LOCK parameter
value. ExplanationA dialog invoked the LMCOPY, LMMFIND or EDIT service with the LOCK option specified indicating an LMF lock should be performed. LMF is no longer supported by ISPF. Programmer responseFor ISPEXEC calls, remove the LOCK keyword. For ISPLINK calls, pass a blank for the LOCK parameter value. ISRLS369 No members in data set - The partitioned data set specified
contains no members. ExplanationThere are no members in the partitioned data set. User responseSpecify a partitioned data set that contains members. ISRLS370 Seq. data set invalid - Use partitioned data set, if "from"
side has multiple members. ExplanationThe TO data set must be partitioned if the FROM data set has multiple members. User responseSpecify a partitioned data set for the TO data set. ISRLS371 Invalid format parameter - Format value 'aaaaaaaa'
is not valid. Specify YES, NO, or blank. ExplanationThe value specified for the FORMAT parameter is not valid. User responseSpecify YES, NO, or blank for the value of the FORMAT parameter. ISRLS372 Member name not allowed - Member name not allowed when processing
index print request. ExplanationDo not specify a member name when printing an index listing. User responseRemove the member name and retry. ISRLS373 Sequential not supported - Sequential data sets are not supported
with the index option. ExplanationThe index option does not support sequential data sets. User responseUse the index option with a partitioned data set. ISRLS374 Member name not allowed - A member name or pattern is invalid
with sequential data sets. ExplanationA member name or pattern cannot be specified for sequential data sets. User responseEither remove the member name or specify a partitioned data set. ISRLS375 Member must be specified - A member, pattern or * must be
specified with partitioned data sets. ExplanationA member name, pattern, or an asterisk must be specified if the data set is partitioned. User responseEither specify a member name, pattern, or an asterisk, or specify a sequential data set. ISRLS376 No members match pattern - Pattern 'aaaaaaaa'
contains no matching members. ExplanationThis is an informational message. ISRLS377 Print failed - Unable to write to the listing data set. ExplanationThe print failed because it was unable to write to the listing data set. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS378 Print failed - Unable to allocate listing data set. ExplanationThe print failed because the listing data set could not be allocated. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS379 Member(s) empty - 'aaaaaaaa' member(s)
processed contained no records. ExplanationThis is an informational message. ISRLS440 Data set is empty - Data set contains no records to print. ExplanationThe data set requested for printing contains no records. User responseSpecify a data set that contains records. ISRLS441 Data set(s) not open - A call to LMOPEN must be made before
LMMDISP can be invoked. ExplanationThis message is self explanatory. ISRLS442 Invalid data-id - No data set is associated with the specified
data-id. ExplanationThere is no data set associated with the specified data-id. User responseIssue an LMINIT and an LMOPEN to associate the data set with the data-id, and open the data set. ISRLS443 Severe error - The PDS directory block size exceeds a maximum
of 256. ExplanationA severe error occurred because the PDS directory block size is greater than 256. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS444 Data set not partitioned - LMMDISP requires the data set
to be a partitioned data set. ExplanationThe data set is not partitioned; LMMDISP requires a partitioned data set. User responseSpecify a partitioned data set. ISRLS445 Severe error - An open error occurred while building the
member list. ExplanationAn open error occurred while building the member list. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS446 Severe error - An I/O error occurred while building the member
list. ExplanationAn I/O error occurred while building the member list. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS447 Severe error - A BLDL error occurred while building the member
list. ExplanationA BLDL error occurred while building the member list. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS448 Severe error - A severe BLDL error occurred while getting
the next selection. ExplanationA severe BLDL error occurred while getting the next selection. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS449 Invalid in batch mode - The LMMDISP service may not be invoked
in batch mode. ExplanationThis message is self explanatory. ISRLS450 Severe error - A translation or truncation error occurred
while accessing dialog variables. ExplanationA translation or truncation error occurred while accessing dialog variables. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS451 Empty member list - The LMMDISP or MEMLIST service was called
using a data set or concatenation which contains no members. No member
list was displayed. ExplanationThe LMMDISP or MEMLIST service was called using a data-id which refers to an empty partitioned data set or a concatenation of empty partitioned data sets. The requested member list was not displayed. User responseSpecify a data set that contains members. ISRLS452 No member list - A member list does not exist for this data
set. ExplanationThe data set does not have a member list. User responseSpecify a data set that contains members. ISRLS453 End of selections - No more members were selected from this
member list. ExplanationThis is an informational message. ISRLS454 End of display - END or RETURN was entered to terminate the
member list display. ExplanationThis is an informational message. ISRLS455 Member exists - The specified member already exists in the
member list. ExplanationThis is an informational message. ISRLS456 Member not found - The specified member cannot be found in
the data set concatenation. ExplanationThe specified member cannot be found in the concatenation of data sets. User responseSpecify a member that exists in the data set concatenation. ISRLS457 No matches found - No members matched the specified pattern. ExplanationThis is an informational message. ISRLS460 Keyword missing - Keyword MEMBER is required for use with
option ADD|DELETE|PUT. ExplanationA member name must be specified with the ADD|DELETE|PUT option of the LMMDISP service. User responseSpecify a member name for the ADD|DELETE|PUT option of the LMMDISP service. ISRLS461 Keyword missing - Keyword MEMBER is required for use with
option PUT. ExplanationThis message is self explanatory. ISRLS462 Invalid OPTION value - The valid values for keyword OPTION
are DISPLAY, GET, ADD, PUT, DELETE and FREE. ExplanationAn invalid value was specified for the OPTION keyword of the LMMDISP service. User responseSpecify DISPLAY, GET, ADD, PUT, DELETE or FREE for the OPTION keyword. ISRLS463 Invalid panel width - The member list panel ZDATA area requires
a width of 80 characters. ExplanationThe ZDATA area of the member list panel must be 80 characters. User responseSpecify a member list panel with a ZDATA area that is 80 characters. ISRLS464 Invalid pattern - The member name pattern specified contains
invalid characters. ExplanationThis message is self explanatory. ISRLS465 Panel not found - Panel "aaaaaaaa" could
not be found. ExplanationThis message is self explanatory. ISRLS466 No ZDATA area - The member list display panel must contain
a ZDATA area. ExplanationThere is no ZDATA area specified on the member list display panel. User responseSpecify a member list display panel that contains a ZDATA area. ISRLS467 Invalid CURSOR value - The valid values for keyword CURSOR
are ZCMD, ZLLCMD, and ZLUDATA. ExplanationThe value specified for the CURSOR keyword of the LMMDISP service is invalid. User responseSpecify ZCMD, ZLLCMD, or ZLUDATA for the CURSOR keyword. ISRLS468 Invalid COMMANDS value - The valid values for keyword COMMANDS
are S and ANY. ExplanationThe value specified for the COMMANDS keyword of the LMMDISP service is invalid. User responseSpecify S or ANY for the COMMANDS keyword. ISRLS469 Invalid STATS value - The valid values for keyword STATS
are YES and NO. ExplanationThe value specified for the STATS keyword of the LMMDISP service is invalid. User responseSpecify YES or NO for the STATS keyword. ISRLS470 Invalid member list - You may not use a member list created
by LMMDISP with the LMMLIST service. ExplanationMember lists generated by LMMDISP cannot be used with LMMLIST. User responseFree the member list using OPTION(FREE) when switching between LMMLIST and LMMDISP with the same data-id. ISRLS471 Invalid member list - You may not use a member list created
by LMMLIST with the LMMDISP service. ExplanationMember lists generated by LMMLIST cannot be displayed by LMMDISP. User responseFree the member list using OPTION(FREE) when switching between LMMLIST and LMMDISP with the same data-id. ISRLS472 Data set not open - LMMDISP requires prior successful completion
of LMOPEN. ExplanationThe data set is not open. LMOPEN must be issued for the data set before calling the LMMDISP service. User responseCall the LMOPEN service for the data set before calling LMMDISP. ISRLS473 Invalid MEMBER name - The value for keyword MEMBER contains
invalid characters. ExplanationThere are invalid characters in the value specified for the MEMBER keyword. User responseSpecify a valid pattern for the member name. Asterisk and percent are allowed in the pattern. ISRLS474 Invalid PANEL name - The value for keyword PANEL contains
invalid characters. ExplanationThere are invalid characters in the value specified for the PANEL keyword. User responseCorrect the invalid characters. ISRLS475 Invalid FIELD value - The valid values for keyword FIELD
are 1 and 9. ExplanationThe value specified for the FIELD keyword is invalid. User responseSpecify either 1 or 9 for the FIELD keyword. ISRLS476 ZLLCMD value too long - The value for ZLLCMD must be one
character long if field(1) was used. ExplanationThis message is self explanatory. ISRLS477 PQUERY error - A PQUERY error occurred. Contact your system
programmer. ExplanationAn error occurred while using PQUERY. System programmer responseContact IBM support. User responseContact your system programmer. ISRLS478 Panel not found - The specified member list display panel
was not found. ExplanationThe specified member list display panel was not found. User responseSpecify a display panel that exists. ISRLS479 Invalid member name - The value for keyword TOP contains
invalid characters. ExplanationThe value specified for the TOP keyword is invalid. User responseCorrect the value specified for the TOP keyword. ISRLS480 Member not found - The specified member was not found in
the member list. ExplanationThe PUT option of LMMDISP attempted to store data for a member that was not found in the list. User responseContact the responsible programmer. Programmer responseCorrect the incorrect member name. ISRLS481 Member not found - The specified member was not found in
the member list. ExplanationThe DELETE option of LMMDISP attempted to delete a member that was not found in the list. User responseContact the responsible programmer. Programmer responseCorrect the incorrect member name. ISRLU110 Dynamic allocation error - Unavailable resource with error
code aaaaaaaa, press Help key for detail.
ISRLU111 Dynamic allocation error - Invalid parameter list with error
code aaaaaaaa, press Help key for detail.
ISRLU112 Dynamic allocation error - Environmental error with error
code aaaaaaaa, press Help key for detail.
ISRLU113 Dynamic allocation error - System routine error with error
code aaaaaaaa, press Help key for detail.
ISRLU114 No dynamic allocation - Installation validation routine deny
dynamic allocation/unallocation.
ISRLU115 Catalog error - Already cataloged, VSAM protected, or other
reason - aaaaaaaa
ISRM000 Specify name or pattern - Command requires a member name
or pattern be specified. ExplanationThe SELECT command requires that a member name or pattern be specified. User responseReenter the SELECT command with a member name or pattern, or choose another command. ISRM001 Member not found - The requested member was not found in
the PDS directory(s). ExplanationPDF was unable to locate the member specified. System programmer responsePDF received an RC=4 from a BLDL. Run the appropriate diagnostics against the PDS (or PDSE) directory to verify that the member does exist. If directory problems are found, contact IBM support for the DFP component. User responseCheck that the member name was spelled correctly. If the member is known to exist, contact your system programmer. ISRM002 Invalid member name - Member name specified contains invalid
characters. ExplanationOne or more invalid characters were entered in the member name. User responseCheck that the member name entered is a character string of up to 8 alphanumeric characters, the first of which is either alphabetic or $, #, or @. ISRM003 Invalid command - Valid member list commands are SELECT,
SORT, LOCATE, RESET, REFRESH, SAVE, MLC, CONFIRM, FIND and SRCHFOR. ExplanationA command other than SELECT, SORT, LOCATE, RESET, REFRESH, SAVE, MLC, CONFIRM, FIND or SRCHFOR was entered. User responseCheck the spelling of the command entered. Valid member list commands are SELECT, SORT, LOCATE, RESET, REFRESH, SAVE, MLC, CONFIRM, FIND and SRCHFOR. ISRM004 Invalid command - The only valid member list command is LOCATE
(L). ExplanationThis message is self explanatory. ISRM005 Specify member name - Command specified requires a member
name. ExplanationThis message is self explanatory. ISRM006 Member name too long - Member name must be less than or equal
to 8 characters. ExplanationA member name of more than 8 characters was entered. User responseVerify the member name entered and ensure it is less than or equal to 8 characters. ISRM007 Invalid select code - Use "S" to select or primary command
RESET to erase all line commands. ExplanationA line command other than S was entered on a BROWSE or EDIT member list. User responseMake sure that BROWSE or EDIT is where you want to be. If so, enter S next to the member(s) to be selected, or enter RESET to clear all line commands. ISRM008 Invalid panel width - ISRCML requires a panel that is 80
characters wide. ExplanationThe member list panel specified has a width of fewer than 80 characters. System programmer responseCheck user's //ISPPLIB concatenation and any LIBDEFs to any panel libraries to ensure that the correct panel is being picked up and that it has a width of 80 characters. User responseVerify that the member list panel being used has a width of 80 characters. ISRM009 Pattern too long - Pattern must be less than or equal to
8 characters. ExplanationThe pattern specified has more than 8 characters. User responseReduce the pattern specified to 8 or fewer characters. ISRM010 Invalid sort field - Valid sort fields are NAME, LIB, VV,
MM, CRE, CHA, SIZE, INIT, MOD and ID. ExplanationAn invalid sort field type was specified. User responseEnter one of valid listed sort fields. ISRM011 Invalid sort field - Valid sort fields are NAME, LIB, SIZE,
TTR, ALIAS, AC, AM, RM, ATTR and SSI. ExplanationAn invalid sort field type was specified. User responseEnter one of valid listed sort fields. ISRM012 List in sorted order - The member list is already sorted
in the specified order. ExplanationThis is an informational message. ISRM012B Invalid sort direction - The sort field direction must be
A (for ascending) or D (for descending). ExplanationThis is an informational message. ISRM013 Panel not found - The specified member list panel could not
be found. ExplanationThe panel specified for the LMMLIST service could not be found. System programmer responseVerify that the panel specified for the LMMLIST service exists in a library that is concatenated to ISPPLIB. ISRM014 Invalid PDS directory - The directory block size exceeds
a maximum of 256. ExplanationThe directory for the specified library exceeds the maximum of 256. System programmer responseAllocate a data set with a directory that is less than the maximum of 256. ISRM015 Member deleted - The member you selected has been deleted.
Please select again. ExplanationThe user has selected a new action for a member which has been deleted by a previous action. User responseNo further actions can be performed against a deleted member. ISRM016 Members deleted - The members you selected have been deleted.
Please select again. ExplanationYou have selected a new action for a group of members which has been deleted by a previous action. User responseNo further actions can be performed against a deleted member. ISRM017 Invalid pattern - The specified pattern contains invalid
characters. ExplanationAn invalid character was used as part of a pattern. User responseRefer to the ISPF User's Guide, under Using Member Selection Lists for an explanation of member pattern usage. ISRM018 No matches - The specified pattern produced no matching members. ExplanationThis is an informational message. ISRM019 Invalid select code - Use select code "s" to select a member. ExplanationA selection code other than S was entered. User responseThe member list for this function only supports the selection code of S. ISRM020 Invalid command syntax - The primary command you entered
contains invalid syntax. ExplanationA syntax error was detected for a primary member list command. User responseValid member list commands are SELECT, SORT, LOCATE, RESET, REFRESH, and SAVE. ISRM021 I/O error - An I/O error was encountered while saving the
member list. ExplanationAn I/O error was detected while writing the member list to the ISPF list data set. System programmer responseVerify that the ISPF list data set is allocated and functional. ISRM022 List saved - The member list was saved in the ISPF list data
set. ExplanationThis is an informational message. ISRM023 List saved - The member list was saved in 'aaaaaaaa'. ExplanationThis is an informational message. ISRM024 Authorization failed - You may not use this protected data
set. Open 913 abend. ExplanationYou do not have write authority to the list data set. Contact your system programmer. System programmer responseUpdate the user's authority level to the allocated list data set. ISRM025 Too many sort fields - You may specify up to two fields for
use with the SORT command. ExplanationToo many parms were entered for the SORT primary command. User responseEnter up to two sort fields on the SORT primary command. ISRM026 Enter "aaaaaaaa" string - The LOCATE command
requires you to enter a "aaaaaaaa" string. ExplanationThe LOCATE primary command was entered with no parameter. User responseEnter one parameter with the LOCATE primary command. ISRM027 Invalid list-id - "aaaaaaaa" contains
invalid characters. ExplanationThe supplied list-id is invalid. The list-id
is the third qualifier in the data set the member list is to be written
to. The format is as follows:
User responseEnter a valid data set qualifier. ISRM028 Invalid created date - "aaaaaaaa" is invalid
as a "Created" date. ExplanationThe member list has been sorted by date created and a locate command has been entered that is not a numeric value. User responseEnter a valid date. ISRM029 Invalid changed string - "aaaaaaaa" is
invalid as a "Changed" date/time ExplanationThe member list has been sorted by date changed and a locate command has been entered that is not a numeric value. User responseEnter a valid date/time ISRM030 I/O error - An I/O error occurred while processing the member
list SORT command. ExplanationAn I/O error was detected during BLDL processing against the member list data set. System programmer responseVerify that the data set is functional. User responseRetry the operation. ISRM031 BLDL error - A BLDL error occurred while processing the member
list SORT command. ExplanationA BLDL error was detected against the member list data set. System programmer responseVerify that the data set is functional. User responseRetry the operation. ISRM032 OPEN error - An OPEN error occurred while processing the
member list SORT command. ExplanationAn OPEN error was detected against the member list data set. System programmer responseVerify that the data set is functional. User responseRetry the operation. ISRM033 No members left - All members have been deleted from the
PDS(s). ExplanationThis is an informational message. All the current members of the PDS have been deleted by a previous action. ISRM034 LOCATE command invalid - The member list must be sorted again
before you can use the LOCATE command. ExplanationThis is an informational message. ISRM035 Invalid locate string - NX, DATA, OVLY, RU, RN, RF and TEST
are the valid LOCATE parameters when a member list is sorted by ATTRIBUTES. ExplanationThe valid LOCATE parameters are based upon the most recent sort command. When a member list is sorted by attributes, use one of the LOCATE parameters listed. ISRM036 Allocation error - An error occurred allocating 'aaaaaaaa'. ExplanationAn error was encountered in allocating the List data set while processing the SAVE primary command. System programmer responseVerify that the data set is functional. User responseContact your system programmer. ISRM037 Invalid sort field - Valid sort fields are NAME, LIB, VV,
MM, CHA, SIZE, INIT, MOD, CRE and ID. ExplanationAn invalid SORT primary command parameter was entered. User responseRetry the operation with a valid SORT parameter. ISRM038 Invalid sort field - Valid sort fields are NAME, LIB, ALIAS,
SIZE, TTR, AC, AM, RM, ATTR and SSI. ExplanationAn invalid SORT primary command parameter was entered. User responseRetry the operation with a valid SORT parameter. ISRM039 I/O error - An I/O error occurred while saving the member
list. ExplanationAn I/O was encountered while processing the SAVE primary command. System programmer responseVerify that the data set is functional. User responseRetry the operation. ISRM039A Confirm forced on - Confirm member delete is forced on for
default action Delete. ExplanationInformational only ISRM039B Initial edit macro set - An initial edit macro is defined
for actions Edit and View. Enter a "/" in the prompt field for Edit
or View Actions to display or change Edit/View entry fields. ExplanationInformational only ISRM040 Invalid data set name - The specified data set name contains
invalid syntax. ExplanationA data set qualifier syntax is invalid. User responseCorrect and reenter the data set name. ISRM041 Invalid sort field - Valid sort fields are NAME, VV, MM,
CRE, CHA, SIZE, INIT, MOD, and ID. ExplanationAn invalid SORT primary command parameter was entered. User responseRetry the operation with a valid SORT parameter. ISRM042 Invalid sort field - Valid sort fields are NAME, SIZE, TTR,
ALIAS, AC, AM, RM, ATTR and SSI. ExplanationAn invalid SORT primary command parameter was entered. User responseRetry the operation with a valid SORT parameter. ISRM043 Invalid sort field - Valid sort fields are NAME, VV, MM,
CHA, SIZE, INIT, MOD, CRE PROMPT and ID. ExplanationAn invalid SORT primary command parameter was entered. User responseRetry the operation with a valid SORT parameter. ISRM044 Invalid sort field - Valid sort fields are NAME, ALIAS, SIZE,
TTR, AC, AM, RM, ATTR and SSI. ExplanationAn invalid SORT primary command parameter was entered. User responseRetry the operation with a valid SORT parameter. ISRM045 No members selected - None of the members in the member list
matched the specified pattern. ExplanationThis is an informational message. ISRM046 Locate string too long - Locate string "aaaaaaaa"
must be less than or equal to bbbbbbbb characters. ExplanationThe LOCATE parameter contains too many characters. User responseRetry the operation with correct number of characters. ISRM047 Invalid LRECL - Data set logical record length must be greater
than or equal to 80. ExplanationThe list-id data set must have a LRECL that is equal to or greater than 80. User responseCorrect the list-id data set and retry the SAVE operation. ISRM048 Error freeing data set - Error freeing the list data set. ExplanationThe list data set encountered an error while processing a FREE command. System programmer responseVerify that the data set is functional. User responseContact your system programmer. ISRM049 Error closing data set - Error closing the data set in which
the member list was saved. ExplanationAn error was encountered while closing the list data set. System programmer responseVerify that the data set is functional. User responseContact your system programmer. ISRM050 List-id too long - The list-id must be less than or equal
to 8 characters in length. ExplanationThe SAVE member list primary command allows a list-id as a parameter. The list-id must have 8 or fewer characters. ISRM051 Invalid locate string - Enter numeric characters (0-9) for
locate string. ExplanationThe locate parameter must be a valid number, if the list is sorted by LIB, VV, or MM. User responseReissue the LOCATE command with a valid parameter. ISRM052 Invalid locate string - Enter hexadecimal characters (0-9,A-F)
for locate string. ExplanationThe locate parameter must be a valid hex number, if the list is sorted by SIZE, TTR, or AC. User responseReissue the LOCATE command with a valid parameter. ISRM053 "*" not supported. - The "*" pattern is not supported for
this action. ExplanationThis message is self-explanatory. ISRM054 Select code too long - Only 1 character select codes are
valid. ExplanationThe select primary command allows a member name and a select code as parameters. For normal member list panels, only 1 character select codes are valid. ISRM055 Date not numeric - Enter numeric characters for month, day,
and year. ExplanationThe LOCATE command requires that the month, day, and year be expressed as numbers. User responseReissue the LOCATE command with a valid parameter. ISRM056 Time not numeric - Enter numeric characters for hour, minute
and second. ExplanationThe LOCATE command requires that the hour, minute and second be expressed as numbers. User responseReissue the LOCATE command with a valid parameter. ISRM057 Locate string too long - Changed date must have a length
less than or equal to 8. ExplanationThe LOCATE command requires that the month, day, and year be two digit numbers, separated by one character. User responseReissue the LOCATE command with a valid parameter. ISRM058 Locate string too long - Changed time must have a length
less than or equal to 5. ExplanationThe LOCATE command requires that the hour and minute be two digit numbers, separated by one character. User responseReissue the LOCATE command with a valid parameter. ISRM059 Date incomplete - Enter complete date in format YY/MM/DD. ExplanationThe LOCATE command requires a fully specified date. User responseReissue the LOCATE command with a valid parameter. ISRM060 No aaaaaaaa bbb(44) found
- aaaaaaaa bbb(44) - not found
in specified field. ExplanationThis is an informational message. A FIND or RFIND command was entered to cause the member list processor to search the specified field in the member list for the specified target string. The search was completed, but the target string was not found. ISRM061 Enter character string - Enter the string of characters to
be found. ExplanationThe FIND command was entered on a member list, but no parameter was specified to indicate what the search target was. User responseSpecify a target string on the FIND command. ISRM062 FIND string too long - The FIND string cannot be longer than
20 characters. ExplanationThe FIND command searches for the specified target string within the specified field. Since the maximum length of a field in the member list is 20 characters, the target string may not exceed 20 characters. User responseRetry the command, entering a target string that is equal to or less than 20 characters in length. ISRM063 aaaa - bbbbbbbb ccc(20) - bbbbbbbb ccc(20) found
on aaaa line(s) ExplanationThis is an informational message. A FIND ALL command was entered on a member list, and the specified target string was successfully located. ISRM064 aaaaaaaa bbb(20) found
- Search for aaaaaaaa bbb(20) was
successful. ExplanationThis is an informational message. A FIND command was entered on a member list, and the string was successfully located. ISRM065 *Bottom of list reached* - aaaaaaaa bbb(20) not
found. Press the RFIND key to continue the search from the top of
the member list. ExplanationThis is an informational message. The member list FIND command searches from the top of the displayed data to the bottom of the list to find the target string. FIND has searched and reached the bottom of that list without finding the target string. Entering the RFIND command continues the search, starting from the top of the member list. ISRM066 * Top of list reached * - aaaaaaaa bbb(20) not
found. Press the RFIND key to continue the search from the bottom
of the member list. ExplanationThis is an informational message. When the PREV keyword is specified, the member list FIND command searches from the top of the displayed data to the top of the list to find the target string. FIND has searched and reached the top of that list without finding the target string. Entering the RFIND command continues the search, starting from the bottom of the member list. ISRM067 Invalid string type - Member list FIND command does not process
picture (P'...'), hex (X'...'), text (T'...') or char (C'...') strings. ExplanationThe member list FIND command does not support
all of the keywords supported by the editor FIND command. These are
not supported:
All FIND commands are treated as text strings (T'...'), meaning that strings are matched regardless of case. User responseRemove the unsupported keyword and reenter the command. ISRM068 Invalid keyword - The keywords 'aaaaaaaa'
and 'bbbbbbbb' cannot both be used. Delete one. ExplanationThe FIND command was entered, passing conflicting
keywords. Only one of these keywords may be specified. Two types
of keywords are supported by the FIND command: direction keywords
and type keywords. No more than one of each type of keyword may be
specified on the FIND command. The keywords are:
The defaults are NEXT and CHARS User responseCorrect the keywords specified and retry the command. ISRM069A Invalid find field - Valid find fields are NAME, ALIAS, SIZE,
TTR, AC, AM, RM, ATTR and SSI. ExplanationAn invalid find primary command parameter was entered. User responseRetry the operation with a valid find parameter. ISRM069B Invalid find field - Valid find fields are NAME, VV, MM,
CRE, CHA, SIZE, INIT, MOD, and ID. ExplanationAn invalid find primary command parameter was entered. User responseRetry the operation with a valid find parameter. ISRM070 SUPERC error - SUPERC error, return code = aaaaaaaa. ExplanationInformational ISRM071 String(s) found - String(s) found in the member list. ExplanationInformational ISRM072 String(s) not found - String(s) not found in any of the members
in the list. ExplanationThis is an informational message. A SRCHFOR command was entered to search all the members in the member list for the string(s). The search was completed, but the string was not found in any of the members. ISRM073 Inconsistent member list - SRCHFOR detected inconsistencies
in the member list. Try a REFRESH ExplanationThis is an informational message. A SRCHFOR command was entered to search all the members in the member list for the string(s). The search was completed, but the member list in storage did not match the member list on DASD and a REFRESH should be issued to resolve this. ISRM074 SuperC error - SUPERC error, return code = aaaaaaaa.
Enter HELP for more information. ExplanationThis is a warning message. ISRM075 SRCHFOR disallowed - Member list SRCHFOR relies on an ISPF
service that does not support a DDNAME concatenation containing uncataloged
data sets. The SRCHFOR command can be executed against each individual
data set member list within the concatenation. ExplanationSRCHFOR has detected that LMINIT has been issued against a DDNAME containing uncataloged data sets. ISPF does not support this. User responseProcess each data set individually ISRM080A Invalid field - Invalid member list field specified on Filter
command ExplanationInformational ISRM080B Unsupported field - Member list field aaaaaaaa is
not supported by the Filter command ExplanationInformational ISRM080C Invalid operator - Invalid operator specified on Filter command ExplanationInformational ISRM080D Unsupported operator - Operator aaaaaaaa is
not supported for bbbbbbbb ExplanationInformational ISRM080E Wrong no. parms - Specify FILTER or 'FILTER <field> <oper> <value>' ExplanationInformational ISRM080F Field Unavailable - Member list field aaaaaaaa is
not available on the current display ExplanationUsed to indicate that LIB selected when only single lib ISRM081A Invalid value - Invalid value aaaaaaaa specified
on Filter command ExplanationInformational ISRM082A Canceled - The Member List Filter command was canceled ExplanationInformational ISRM082B No matches - No members matched the Filter criteria ExplanationInformational ISRP000 There are no keywords defined for language aaaaaaa. ExplanationThis is an informational message. Language aaaaaaa has no keywords which the editor specifically highlights, so you cannot look at the keyword list. ISRP001 Settings for language aaaaaaa were reset
to their original values. ExplanationThis is an informational message. All of the settings for language aaaaaaa, including colors, highlighting, intensity, and special characters to highlight were reset to the values they had when the HILITE command was invoked. ISRP002 Settings for language aaaaaaa were reset
to their default values. ExplanationThis is an informational message. All of the settings for language aaaaaaa, including colors, highlighting, intensity, and special characters to highlight were set to the default values defined by ISPF. The default settings will be saved when you exit the HILITE dialog unless you make further changes or use the CANCEL command or pull-down choice. ISRP003 No changes were made to language aaaaaaa. ExplanationThis is an informational message. The language dialog for language aaaaaaa was exited without any changes. ISRP003A No changes were made to the FIND string color. ExplanationThis is an informational message. The FIND string color dialog was ended with the CANCEL command. No changes were made to the FIND string color. ISRP003B No changes were made to the Cursor phrase color. ExplanationThis is an informational message. The cursor phrase color dialog was ended with the CANCEL command. No changes were made to the cursor phrase color. ISRP003C No changes were made to the overtype color. ExplanationThis is an informational message. The overtype color dialog was ended with the CANCEL command. No changes were made to the overtype color. ISRP004 Values for language aaaaaaa were updated.
They will be saved when this application is ended. ExplanationThis is an informational message. The settings for language aaaaaaa, including colors, highlighting, intensity, and special characters to highlight were changed. The changes will be saved when you exit the HILITE dialog unless you make further changes or use the CANCEL command or pull-down choice. ISRP004A Values for the overtype color were updated. They will be
saved when this application is ended. ExplanationThis is an informational message. The settings for overtype color were changed and will be saved when you exit HILITE dialog unless you make further changes to the overtype color, or use the CANCEL command or pull-down choice. ISRP004B Values for the FIND string highlight color were updated.
They will be saved when this application is ended. ExplanationThis is an informational message. The settings for FIND string highlight color were changed and will be saved when you exit HILITE dialog unless you make further changes to the FIND string highlight color, or use the CANCEL command or pull-down choice. ISRP004C Values for the cursor phrase highlight color were updated.
They will be saved when this application is ended. ExplanationThis is an informational message. The settings for cursor phrase highlight color were changed and will be saved when you exit HILITE dialog unless you make further changes to the cursor phrase highlight color, or use the CANCEL command or pull-down choice. ISRP005 Color, symbol and margin settings have been saved in the aaaa application
profile. All other HILITE settings were saved in the edit profile. ExplanationThis is an informational message. The HILITE command was used to update the behavior of ISPF enhanced edit coloring. The color, symbol and margin settings for the languages have been saved in the current application profile (aaaa). Other settings which affect highlighting, such as ON, OFF, LOGIC, PAREN and the current language determination method were saved in the edit profile. ISRP006 All settings have been reset to their original values. ExplanationThis is an informational message. All enhanced edit coloring settings, including colors, highlighting, intensity, and special characters to highlight were reset to the values they had when the HILITE command was invoked. ISRP007 You must enter a valid color (RED, GREEN, BLUE, WHITE, YELLOW,
PINK, TURQ) or blank for the default color. ExplanationThis message is self explanatory. ISRP007A You must enter a valid highlight specification (NORMAL, REVERSE,
USCORE, BLINK) or blank for the normal highlighting. ExplanationThis message is self explanatory. ISRP007B You must enter a valid intensity specification (HIGH, or
LOW) or blank for the default intensity. ExplanationThis message is self explanatory. ISRP007C Invalid Margin - Specify either '*' or a valid numeric value ExplanationThis message is self explanatory. ISRP008 All settings have been set to the defaults. ExplanationThis is an informational message. All of the settings, including colors, highlighting, intensity, and special characters to highlight, were set to the default values defined by ISPF. The default settings will be saved when you exit the HILITE dialog unless you make further changes or use the CANCEL command or pull-down choice. ISRP009 Cancel requested. No changes were saved. ExplanationThis is an informational message. The HILITE command dialog was exited with the CANCEL command. No changes to the enhanced coloring settings were saved. ISRP009A The settings for ALL LANGUAGES were set. These changes will
be saved when this application is ended. Use Cancel to avoid saving
these changes. ExplanationThis is an informational message. The settings for all of the supported languages were changed. Cancel out of the HILITE dialog if you do not want to save the changes. ISRP010 MARGINS not allowed - The HILITE MARGINS parameter is not
supported for the current HILITE language. ExplanationThe HILITE command was specified with the MARGINS parameter. This parameter is only supported if the HILITE language is C, PL/I, or PL/X. User responseRemove the incorrect parameter and reissue the HILITE command. ISRP011 Invalid left margin - Specify a value for the left margin
in the range aaaaaaaa. to bbbbbbbb. ExplanationThe value specified for the left margin is out of range for the current HILITE language. User responseReissue the HILITE command with valid parameters. ISRP012 Invalid right margin - Value specified for the right margin
must be in the range aaaaaaaa. to bbbbbbbb. ExplanationThe value specified for the right margin is out of range for the current HILITE language. User responseReissue the HILITE command with valid parameters. ISRP013 Parameter conflict - "AUTO" and "MARGINS" parameters conflict.
Remove one. ExplanationThe language AUTO and MARGINS parameters conflict and can not be specified together on the HILITE command. User responseReissue the HILITE command with valid parameters. ISRP014 -CAUTION- All profile HILITE settings have been disabled.
HILITE is not ExplanationThis message is self explanatory. ISRP015 supported for edit from a web client. Use view for HILITE. ExplanationThis message is self explanatory. ISRP016 HILITE unavailable - The HILITE command is not available
for edit from a web client. Use View to invoke the HILITE command. ExplanationEdit highlighting is not available when using edit from a web client because the highlighting features cause problems when changing data. If you need to use the highlighting features display the data in View mode. ISRP020 EDIT RECOVERY OR UNDO FAILED. If you are currently in an
edit session, DO NOT SAVE THE DATA. Press HELP for more information
and instructions. (Error Cause: Error writing ignore record) ExplanationAn error occurred processing an edit recovery or undo request. This error indicates that the record of changes that is kept by PDF was corrupted. User responseIf you are in an edit session, do not save the data; it may have been corrupted. Since this problem may indicate that the recovery record may have been built incorrectly, you may want to save the recovery data set (if one exists), and contact IBM support. In addition, please write down everything you remember about the edit session that originally created the recovery file or that you were in when the UNDO failed. Useful information includes messages you saw, what types of commands and macros you used, and any unusual data or system conditions. ISRP021 INCOMPLETE RECOVERY OR UNDO If you are currently in an edit
session, DO NOT SAVE THE DATA WITHOUT CHECKING IT FIRST. This message
may not indicate a data loss error. Press HELP for more information
and instructions. (Error Cause: Invalid data or length in recovery
file or chain) ExplanationAn error occurred processing an edit recovery or undo request. This error indicates that the record of changes that is kept by PDF was corrupted. User responseIf you are in an edit session, do not save the data; it may have been corrupted. Since this problem may indicate that the recovery record may have been built incorrectly, you may want to save the recovery data set (if one exists), and contact IBM support. In addition, please write down everything you remember about the edit session that originally created the recovery file or that you were in when the UNDO failed. Useful information includes messages you saw, what types of commands and macros you used, and any unusual data or system conditions. ISRP022 EDIT RECOVERY OR UNDO FAILED. If you are currently in an
edit session, DO NOT SAVE THE DATA. Press HELP for more information
and instructions. (Error Cause: Error reading recovery file or chain) ExplanationAn error occurred processing an edit recovery or undo request. This error indicates that the record of changes which is kept by PDF was corrupted. User responseIf you are in an edit session, do not save the data; it may have been corrupted. Since this problem may indicate that the recovery record may have been built incorrectly, you may want to save the recovery data set (if one exists), and contact IBM support. In addition, please write down everything you remember about the edit session that originally created the recovery file or that you were in when the UNDO failed. Useful information includes messages you saw, what types of commands and macros you used, and any unusual data or system conditions. ISRP023 EDIT RECOVERY OR UNDO FAILED. If you are currently in an
edit session, DO NOT SAVE THE DATA. Press HELP for more information
and instructions. (Error Cause: Invalid verb in recovery file or
chain (case 1)) ExplanationAn error occurred processing an edit recovery or undo request. This error indicates that the record of changes which is kept by PDF was corrupted. User responseIf you are in an edit session, do not save the data; it may have been corrupted. Since this problem may indicate that the recovery record may have been built incorrectly, you may want to save the recovery data set (if one exists), and contact IBM support. In addition, please write down everything you remember about the edit session that originally created the recovery file or that you were in when the UNDO failed. Useful information includes messages you saw, what types of commands and macros you used, and any unusual data or system conditions. ISRP024 EDIT RECOVERY OR UNDO FAILED. If you are currently in an
edit session, DO NOT SAVE THE DATA. Press HELP for more information
and instructions. (Error Cause: Nonexistent record referenced in
recovery file or chain) ExplanationAn error occurred processing an edit recovery or undo request. This error indicates that the record of changes which is kept by PDF was corrupted. User responseIf you are in an edit session, do not save the data; it may have been corrupted. Since this problem may indicate that the recovery record may have been built incorrectly, you may want to save the recovery data set (if one exists), and contact IBM support. In addition, please write down everything you remember about the edit session that originally created the recovery file or that you were in when the UNDO failed. Useful information includes messages you saw, what types of commands and macros you used, and any unusual data or system conditions. ISRP025 EDIT RECOVERY OR UNDO FAILED. If you are currently in an
edit session, DO NOT SAVE THE DATA. Press HELP for more information
and instructions. (Error Cause: Invalid verb in recovery file or
chain (case 1)) ExplanationAn error occurred processing an edit recovery or undo request. This error indicates that the record of changes which is kept by PDF was corrupted. User responseIf you are in an edit session, do not save the data; it may have been corrupted. Since this problem may indicate that the recovery record may have been built incorrectly, you may want to save the recovery data set (if one exists), and contact IBM support. In addition, please write down everything you remember about the edit session that originally created the recovery file or that you were in when the UNDO failed. Useful information includes messages you saw, what types of commands and macros you used, and any unusual data or system conditions. ISRP026 EDIT RECOVERY OR UNDO FAILED. If you are currently in an
edit session, DO NOT SAVE THE DATA. Press HELP for more information
and instructions. (Error Cause: Invalid verb in recovery file or
chain (case 1)) ExplanationAn error occurred processing an edit recovery or undo request. This error indicates that the record of changes which is kept by PDF was corrupted. User responseIf you are in an edit session, do not save the data; it may have been corrupted. Since this problem may indicate that the recovery record may have been built incorrectly, you may want to save the recovery data set (if one exists), and contact IBM support. In addition, please write down everything you remember about the edit session that originally created the recovery file or that you were in when the UNDO failed. Useful information includes messages you saw, what types of commands and macros you used, and any unusual data or system conditions. ISRP100 No connection - This action requires a connection with the
workstation to be established. A workstation connection can be established
from ISPF Settings panel or enter WSCON from any command line. ExplanationNo connection to a workstation exists. The user must identify the workstation by specifying the GUI parameter on ISPSTART, by selecting the Workstation pull-down choice from ISPF Settings panel or entering WSCON from any command line. User responseStart a session with a workstation before performing this action. Programmer responseNone ISRP101 Configuration error - Distributed View/Edit is only valid
when Workstation Tool Integration is configured for the View/Edit
actions. Select the Workstation Tool Integration pull-down choice
from the Workstation action bar pull-down on the View/Edit Entry Panel
to configure the Workstation Tool Integration or enter the ISPF command
INT on the command line. ExplanationISPF Workstation Tool Integration not configured. The user must configure the Workstation Tool Integration by issuing the INT ISPF command or by selecting the Workstation Tool Integration pull-down choice from the Workstation action bar pull-down on the View/Edit Entry Panel to configure the Workstation Tool Integration. User responseIssue the INT ISPF command or select the Workstation Tool Integration pull-down choice from the Workstation action bar pull-down on the View/Edit Entry Panel to configure the Workstation Tool Integration. Programmer responseNone ISRP102 Invalid VIEW/EDIT parm - When workstation file parameter
is specified, do not code DATAID or member. ExplanationTo invoke the VIEW or EDIT service, you may specify either a data set name, DATAID or workstation file. When workstation file parameter is specified, do not code DATAID or member. User responseRemove the DATAID and member parameters. ISRP103 File unavailable - File transfer failed, the workstation
file could not be opened or the file does not exist. ExplanationThe requested workstation file could not be accessed
for one of these reasons:
ISRP104 Error writing file - File transfer failed. Error writing
workstation file: aaaaaaaa.. The workstation disk
drive is full or the subdirectories do not exist. Create the subdirectories
if they do not exist and try the action again. ExplanationError writing workstation file. Workstation disk drive is full or the subdirectories do not exist. User responseCheck the workstation disk drive and retry. ISRP105 File transfer failed - Error returned by FILEXFER service,
FILEXFER return code aaaaaaaa.. ExplanationThe FILEXFER service failed with a return code of aaaaaaaa.. Refer to the ISPF Services book for an explanation of the return code. ISRP106 Function not supported - Distributed Browse is not a supported
function. Try Distributed View. ExplanationDistributed Browse is not a supported function. User responseTry Distributed View. ISRP107 Conflicting options - View on Workstation and Browse Mode
options cannot be selected simultaneously. De-select one of the conflicting
options. ExplanationView on Workstation and Browse Mode options cannot be selected simultaneously. User responseDe-select one of the conflicting options. ISRP108 No file access - File transfer failed. File access on workstation
rejected by ISPF Client/Server.
ISRP109 File not saved - File not saved on workstation.
ISRP110 Default configuration - ISPF Workstation Tool Integration
was not configured for the View/Edit actions. Default configuration
will be used. You may modify or save the default configuration. ExplanationISPF Workstation Tool Integration was not configured for the View/Edit actions. Default configuration will be used. User responseModify or save the default configuration. Programmer responseNone ISRP111 Edit not confirmed - The edit session canceled at your request.
Member cannot be promoted with requested authcode. ExplanationEntering END or EXIT on the SCLM Edit Authcode Confirmation panel cancels the edit session. User responseIf you want to promote the member, try editing with a different authcode. If you need to change the authcode, use the SCLM library utility. ISRP112 WS command failed - Workstation command failed. Return code
= aaaaaaaa..
ISRP113 Error saving data set - File transfer failed. Error saving
the workstation work file: aaaaaaaa into host data
set: bbbbbbbb.. The host data set may be RACF protected. The workstation
work file is kept on the workstation. ExplanationError saving the workstation work file: aaaaaaaa into host data set: bbbbbbbb. The host data set may be RACF protected. User responseRequest RACF access to the data set and upload the workstation work file manually. ISRP114 Data set packed - File transfer does not support packed data
sets. Unpack the data set and try the action again.
ISRP115 File in use - The ISPF generated workstation work file name aaaaaaaa is
in use. Try the action again later.
ISRP116 Member aaaaaaaa viewed - Member aaaaaaaa in bbbbbbbb was
viewed in View mode. The workstation work file was saved in cccccccc..
ISRP117 Data set viewed - aaaaaaaa was viewed
in View mode. The workstation work file was saved in bbbbbbbb..
ISRP118 Member aaaaaaaa edited - Member aaaaaaaa in bbbbbbbb was
edited in modeless Edit mode. The workstation work file was saved
in cccccccc..
ISRP119 Data set edited - aaaaaaaa was edited
in modeless Edit mode. The workstation work file was saved in bbbbbbbb..
ISRP120 Command not started - ISPF was not able to start the command
at the workstation. ExplanationISPF was not able to start the command at the workstation. User responseMake sure you are able to start the workstation command in the workstation's native environment. Programmer responseNone ISRP121 Command not allowed - Remote execution of the workstation
command was not allowed by the workstation. ExplanationRemote execution of the workstation command was not allowed by the workstation. Programmer responseNone ISRP122 No ISPF statistics - aaaaaaaa was saved
in bbbbbbbb, but no space in PDS directory for
ISPF statistics. ExplanationThere is not sufficient directory space to create statistics. User responseRe-allocate the data set with additional directory blocks. Programmer responseNone ISRP123 Device not ready - The requested device is not ready or available.
Please verify that the device has the correct media and that it is
available or select a different device. ExplanationThe device that was requested is not ready, available or found. Please check the device that was requested. System programmer responseContact IBM support. User responseCheck the device and verify that it is available and working. If needed place the proper media in the device or select a different device. Programmer responseNone. ISRP124 Macro parameter error - The parameter specified by PARM keyword
of the aaaa service could not be resolved. Either
the variable name bbbbbbbb is invalid, or a VCOPY
for the variable failed. ExplanationThe variable specified in the PARM parameter of the EDIT, VIEW, EDIF or VIIF service could not be resolved. System programmer responseThe EDIT or VIEW session is not started. User responseContact the author of the program. Programmer responseCheck the program which invokes EDIT or VIEW to insure that the variable name is valid and that the variable does contain data. ISPF uses the VCOPY service to get the value of the variable, so you should be sure that the variable exists in the same application id as the one in which the EDIT or VIEW service is invoked. ISRP125 Build not allowed - An SCLM Workstation Build can not be
performed from the ISPF Java environment. ExplanationSCLM Workstation Build uses the ISPF FILEXFER and WSCMDV services. These services are not valid when used for a Workstation Build in the Java™ environment. System programmer responseContact IBM support. Programmer responseNone. ISRP126 Assignment command error - Assignment type (GET/SET) unrecognized
for the PRESERVE command. ExplanationA severe error (return code 20) has been received using the PRESERVE macro command. The assignment type used with the PRESERVE command is invalid. User responseCorrect the edit macro so that it uses the correct assignment type for the PRESERVE command. ISRP127 PASTE data truncated - The Paste operation was successfully
completed, but some data may have been truncated. The data that was
pasted into the current edit session was CUT from a data set with
a longer logical record length. Data past the end of the current
record length was not copied into this edit session. ExplanationThe data that was pasted into the current edit session was CUT from a data set with a longer logical record length. Some data may have been truncated during the PASTE operation. ISRP128 PARM without MACRO - The PARM value of the aaaa service
is not allowed without the MACRO parameter. ExplanationThe EDIT, VIEW, EDIF, or VIIF service was issued with a value for the initial macro parameters (PARM keyword) but without an initial macro specified. User responseContact programmer of the dialog that uses the specified service. Programmer responseCheck the syntax of the service call to insure that either an initial edit macro name is specified, or that the edit macro parameter value is blank. ISRP129 Parameter too long - The value of the variable used in the
PARM parameter for the aaaa service was greater
than 200 characters. ExplanationThe EDIT, VIEW, EDIF, or VIIF service was issued with a variable name containing the initial macro parameters (PARM keyword) but variable contained a value longer than 200 bytes. User responseContact programmer of the dialog that uses the specified service. Programmer responseCheck the variable specified to contain parameters to insure that the value does not exceed 200 characters. If you need to pass more information, use the VPUT service in the calling program to save values in the shared variable pool and the VGET service in the macro to retrieve those values. ISRP130 Insufficient storage - CUT failed because not enough virtual
storage was available for saving the records being cut. aaaaaaaa bytes
were required, but only bbbbbbbb bytes were available
in the requested clipboard. Clipboard cccccccc was
not changed. ExplanationThe ISPF editor reserves a certain amount of space to save CUT lines and the cut request would use more than that reserved amount of space. User responseReduce the number of lines being cut, use the REPLACE parameter or specify a different clipboard on the CUT request. Programmer responseNone ISRP131 aaaaaaaa lines cut to bbbbbbbb - aaaaaaaa lines
were saved in clipboard bbbbbbbb for later retrieval
by the paste command. ExplanationThe CUT command was successfully completed. The clipboard contains only the lines that were most recently cut. Programmer responseNone ISRP132 aaaaaaaa lines added to bbbbbbbb - aaaaaaaa lines
were saved in clipboard bbbbbbbb for later retrieval
by the paste command. These lines were added to lines that were already
saved by one or more CUT commands. ExplanationThe CUT command was successfully completed. The clipboard contains the lines that were most recently cut in addition to lines that were already in the clipboard. Programmer responseNone ISRP133 Use CUT before PASTE - No lines exist in the clipboard named aaaaaaaa or
the clipboard does not exist. The CUT command must be used before
the PASTE command. ExplanationA PASTE request was issued using the name of an empty or nonexistent clipboard. User responseUse the CUT DISPLAY command to see the names of existing clipboards. Insure that you are using a clipboard that has had data placed in it by a previous CUT command. Programmer responseNone ISRP134 Clipboard limit reached - The maximum number of clipboards
have been created. No new clipboards may be created. Use the CUT
DISPLAY command to see the names of existing clipboards. ExplanationUse the CUT DISPLAY command to see the names of existing clipboards. You may want to rename or reuse an existing clipboard. Programmer responseNone ISRP135 Invalid clipboard name - The clipboard name was greater than
eight characters long. Reenter the command using a different clipboard
name or use the CUT DISPLAY command to view existing clipboard names. ExplanationClipboard names are 1 to 8 characters long, contain alphanumeric characters and start with an alphabetic character. User responseReenter the command using a valid clipboard name. Programmer responseNone ISRP136 No Clipboards - No Clipboards are available to list by the
CUT DISPLAY command. ExplanationNo clipboards exist. This condition should only occur when your userid can not create data spaces. System actionCut/paste services are not available. Programmer responseNone ISRP137 No more clipboards - No clipboards are available to use.
Use the CUT DISPLAY command to display the available clipboard names. Programmer responseNone ISRP138 DISPLAY is invalid - DISPLAY is not a valid operand on the
CUT edit macro command. ExplanationThe edit macro form of the CUT command was specified incorrectly. User responseContact the author of the edit macro. Programmer responseChange the edit macro to remove the DISPLAY keyword of the CUT command. CUT DISPLAY is not supported from a macro. ISRP139 aaaaaaaa is empty - The requested clipboard
(aaaaaaaa) contains no lines to browse or edit. ExplanationA browse or edit request was made for a clipboard that has no lines. Only clipboards containing lines may be browsed or edited. User responseUse the CUT command to add lines to the clipboard. Programmer responseNone ISRP140 Invalid clipboard name - The clipboard name entered is not
a valid name. Clipboard names follow the same rules as PDS member
names within ISPF. ExplanationA CUT or PASTE command was entered with an invalid clipboard name. Clipboard names are 1 to 8 alphameric characters starting with a alphabetic character. User responseEnter the command with a valid clipboard name. Programmer responseNone ISRP141 aaaaaaaa exists - A clipboard named aaaaaaaa already
exists. Choose a different name. ExplanationWhen renaming a clipboard, the name of an existing clipboard was used. User responseChoose a different name for the clipboard or reenter the original name. Programmer responseNone ISRP142 Name change invalid - You may not change the name of the
ISPF default clipboard. ExplanationAn attempt was made to rename the ISPF default clipboard. This is not allowed because ISPF reserves the name DEFAULT for the first clipboard. User responseIf you need additional clipboards, use the CUT command to create them and specify the clipboard name on the CUT command. Programmer responseNone ISRP143 Invalid command - Valid commands are B (Browse), E (Edit),
C (Clear), D (Delete), R (Rename), and O (Toggle read only) ExplanationAn invalid letter or symbol was placed next to a clipboard name. Only the listed commands are valid. User responseEnter one of the listed commands. Programmer responseNone ISRP144 Invalid parameter - You must specify a aaaaaaaa range
on a bbbbbbbb command and you may also specify
a clipboard name and the REPLACE or APPEND keyword. ExplanationAn invalid parameter was specified on a CUT command. User responseRemove the invalid parameter and try the CUT command again. ISRP145 Invalid parameter - You must specify a aaaaaaaa destination
on a bbbbbbbb command using the BEFORE or AFTER
keyword. You may also specify a clipboard name and the DELETE or
KEEP keywords. ExplanationAn invalid parameter was specified on a PASTE command. User responseRemove the invalid parameter and try the PASTE command again. ISRP146 CUT/PASTE unavailable - ISPF could not create a data space
in which to keep information about the editor clipboards. CUT/PASTE
services are not available. R15= aaaaaaaa. R0= bbbbbbbb. ExplanationISPF uses z/OS data spaces to store information about editor clipboards and ISPF was unable to create the data space required. If this is the first invocation of CUT then the system may not allow you to create data spaces. System actionCUT/PASTE services are not allowed in the edit session. System programmer response
User responseRemove the invalid parameter and try the CUT or PASTE command again. ISRP147 aaaaaaaa lines pasted - aaaaaaaa lines
were moved or copied into this edit session from clipboard bbbbbbbb. ExplanationThe contents of clipboard bbbbbbbb were inserted into the current edit session. If the KEEP keyword was used on the PASTE command, the contents of the clipboard were not changed. Otherwise, the clipboard was emptied. ISRP148 aaaaaaaa is read-only - Clipboard aaaaaaaa can
not be changed using the CUT command because it was marked read-only
by using the 'O' line command on the CUT DISPLAY panel. If you want
to change this clipboard, use the 'O' line command in the CUT DISPLAY
entry panel to change the read-only status to read-write. ExplanationThe contents of clipboard aaaaaaaa were not changed. User responseIf you want to change this clipboard, use the 'O' line command in the CUT DISPLAY entry panel to change the read-only status to read-write. ISRP149 Delete not allowed - The default ISPF edit clipboard can
not be deleted. ExplanationThe default ISPF edit clipboard can not be deleted. User responseYou can clear the contents of the default clipboard using the C line command. ISRP150 Invalid Environment - ISREMSPY must be run as a TSO command
within an edit macro or from within an edit session. ExplanationThe ISREMSPY program must be invoked from within an edit session. ISRP151 Data View Reset - The data display and cursor location were
reset to reflect the current state of the editor. ExplanationThis message is self explanatory. ISRP152 This is not an edit or view session. This display is generated
by the ISREMSPY program. All commands except END, CANCEL, RESET and
FIND are ignored. Press END to return to the edit macro or edit session
which started ISREMSPY. ExplanationThis message is self explanatory. ISRP153 Status Line - Line aaaaaaaa of bbbbbbbb ExplanationThis message is self explanatory. ISRP154 String found - The FIND command found the string you were
searching for. ExplanationThis message is self explanatory. ISRP155 String not found - The FIND command did not find the string
you were searching for. The FIND command on ISREMSPY only searches
the first 256 characters on each line. Press RFIND to begin searching
from the beginning of the data. ExplanationThis message is self explanatory. ISRP156 Invalid clipboard name - The CUT command does not accept
K, KEEP, DEL or DELETE as a clipboard name because those are keywords
on the PASTE command. Choose a different clipboard name. ExplanationThis message is self explanatory. ISRP280 Too many parameters - ON/OFF are the only valid parameters
for the PRESERVE command. ExplanationThe PDF edit PRESERVE command was invoked with more than one parameter. Only one parameter (either ON or OFF) may be specified for the PRESERVE command. User responseChange the command to specify the proper parameters for the PRESERVE command and reissue the command or rerun the macro. Refer to ISPF Edit and Edit Macros for editor command syntax. If the macro was supplied by someone else, contact the writer for assistance in correcting the error. Programmer responseChange the macro to specify the proper parameter for the PRESERVE command. Refer to ISPF Edit and Edit Macros for editor command syntax. ISRP281 Invalid parameter - ON/OFF are the only valid parameters
for the PRESERVE command. ExplanationThe PDF edit PRESERVE command was invoked with a parameter other than ON or OFF. User responseChange the command to specify the proper parameters for the PRESERVE command and reissue the command or rerun the macro. Refer to ISPF Edit and Edit Macros for editor command syntax. If the macro was supplied by someone else, contact the writer for assistance in correcting the error. Programmer responseChange the macro to specify the proper parameter for the PRESERVE command. Refer to ISPF Edit and Edit Macros for editor command syntax. ISRP282 Inconsistent parameters - "aaaaaaaa" and
"bbbbbbbb" cannot both be entered with PRESERVE
command. ExplanationMutually exclusive parameters (aaaaaaaa and bbbbbbbb) were specified on invocation of the PRESERVE command. User responseChange the command to specify the proper parameters for the PRESERVE command and reissue the command or rerun the macro. Refer to ISPF Edit and Edit Macros for editor command syntax. If the macro was supplied by someone else, contact the writer for assistance in correcting the error. Programmer responseChange the macro to specify the proper parameter for the PRESERVE command. Refer to ISPF Edit and Edit Macros for editor command syntax. ISRP283 Too many parameters - Too many parameters specified for the
SAVE_LENGTH command. Is data quoted? ExplanationAn invalid SAVE_LENGTH command was entered. User responseReview documentation for the SAVE_LENGTH command in ISPF Edit and Edit Macros . ISRP284 Unrecognized parameter - Extraneous or invalid parameter
was specified for the SAVE_LENGTH command. ExplanationAn invalid SAVE_LENGTH command was entered. User responseReview documentation for the SAVE_LENGTH command in ISPF Edit and Edit Macros . ISRP285 Invalid parameter - Extraneous or invalid parameter was specified
for the PRESERVE command. ExplanationAn invalid PRESERVE command was entered. User responseReview documentation for the PRESERVE command in ISPF Edit and Edit Macros . ISRP286 Line pointer invalid - Required line pointer not correctly
specified for PRESERVE command ExplanationAn invalid PRESERVE command was entered. User responseReview documentation for the PRESERVE command in ISPF Edit and Edit Macros . ISRP287 Data parm omitted - Required data parameter not specified
for PRESERVE command. ExplanationAn invalid PRESERVE command was entered. User responseReview documentation for the PRESERVE command in ISPF Edit and Edit Macros . ISRP288 Assignment command error - Assignment type (GET/SET) unrecognized
for the SAVE_LENGTH command. ExplanationA severe error (return code 20) has been received using the SAVE_LENGTH macro command. The assignment type used with the command is invalid. User responseCorrect the edit macro so that it uses the correct assignment type for the SAVE_LENGTH command. ISRP289 Parameter unrecognized - ON/OFF are the only valid parameters
for the PRESERVE command. ExplanationThe PDF edit PRESERVE command was invoked with a parameter other than ON or OFF. User responseChange the command to specify the proper parameters for the PRESERVE command and reissue the command or rerun the macro. Refer to ISPF Edit and Edit Macros for editor command syntax. If the macro was supplied by someone else, contact the writer for assistance in correcting the error. Programmer responseChange the macro to specify the proper parameter for the PRESERVE command. Refer to ISPF Edit and Edit Macros for editor command syntax. ISRP300 Invalid table name - The QUERYENQ service requires a valid
table name matching ISPF naming conventions.
ISRP301 Table exists - QUERYENQ could not create table 'aaaaaaaa'
because it already exists.
ISRP302 Table in use - QUERYENQ could not create table 'aaaaaaaa'
because it is in use.
ISRP303 Table creation error - QUERYENQ could not create table 'aaaaaaaa'
due to a severe error.
ISRP304 Table creation error - QUERYENQ was unable to add a row to
table 'aaaaaaaa'.
ISRP305 Variable GET error - QUERYENQ was unable to read variable
'aaaaaaaa'.
ISRP306 No ENQs found - No ENQs were found that matched the criteria
passed in to the QUERYENQ service.
ISRP307 Service unavailable - The QUERYENQ service is not available
due to an installation restriction.
ISRP308 Invalid list-id - The parameter on the SAVE operand of the
QUERYENQ service specified an invalid data set name qualifier.
ISRP309 Open Error - The QUERYENQ service was unable to open the
save data set 'aaaaaaaa'.
ISRP309A Data Set Exists - The QUERYENQ service was unable to allocate
the SAVE data set because a data set of the same name ('aaaaaaaa')
already exists but is not a sequential, variable blocked data set
with a record length of bbbbbbbb..
ISRP309B Abend aaaaaaaa from QUERYENQ - The QUERYENQ
service ended with an abend code of aaaaaaaa..
ISRP309D Invalid XSYS keyword - The value of the XSYS parameter on
the QUERYENQ service must be XSYS or blank.
ISRP500 Record length too small - The file contains a record that
is larger than the specified record length aaaaaaaa.. ExplanationRecord length aaaaaaaa was specified to have the file records loaded into the editor as fixed-length records. However the editor found a record that was larger than aaaaaaaa bytes in length. User responseContact the responsible programmer. Programmer responseSpecify a larger record length. ISRP501 File replaced - aaaaaaaa replaced by specified
data. ExplanationThis is an informational message. The data in the z/OS UNIX file has been replaced by the data that was specified. ISRP502 File created - aaaaaaaa created with specified
data. ExplanationThis is an informational message. The z/OS UNIX file has been created using the data that was specified. ISRP503 File not replaced - The Replace command was not confirmed. ExplanationThis is an informational message. The Confirm Replace panel was displayed at the user's request. The user chose not to Replace the file by entering the End command. ISRP504 Edit - Create - aaaaaaaa - data set created. ExplanationThis is an informational message. ISRP505 Edit - Create - aaaaaaaa - file created. ExplanationThis is an informational message. ISRP506 CREATE not allowed - Cannot CREATE a z/OS UNIX file
set that already exists. REPLACE may be used. ExplanationWhile in Edit, a CREATE command was issued. The target specified was a z/OS UNIX file that exists. If the target z/OS UNIX file exists, REPLACE must be used instead. User responseUse REPLACE or specify another z/OS UNIX file. ISRP507 Enter file name - A directory list is not supported with
the aaaaaaaa command. ExplanationThis is an informational message. A directory list is not supported for this command. User responseInclude a file name with the specified directory path name ISRP508 File in use - z/OS UNIX file is being updated by you
or another user. Enter HELP for a list of users using the file. ExplanationThe z/OS UNIX file specified is being updated by another user or by you on another logical screen. Enter HELP for a list of users using the file. User responseFind out if the file is in use by another user, or release the file from another logical screen. ISRP509 Specified data in use - Specified data is being updated by
you or another user. Enter HELP for a list of users using the data. ExplanationSomeone (you or another user) is using the z/OS UNIX file specified as the target file in a MOVE, COPY, CREATE, or REPLACE command. User responseEither choose another file as the target or wait until the file is not being used by someone. ISRP510 File in use - The specified z/OS UNIX file is in use by another user,
try again later. ExplanationSomeone (you or another user) is using the z/OS UNIX file specified as the target data set in a MOVE, COPY, CREATE, or REPLACE command. User responseEither choose another file as the target or wait until the file is not being used by someone. Programmer responseSpecify a larger record length. ISRP511 Permission denied - You do not have the necessary permission
to search the z/OS UNIX directory or some component of the pathname
prefix. ExplanationThis is an informational message. The permissions defined for the z/OS UNIX directory do not allow you to search the directory or some component of the directory pathname. User responseContact the directory owner or the z/OS UNIX system administrator to see if the directory permissions can be altered to allow you to search the directory. ISRP512 Permission denied - You do not have the necessary permission
to read the z/OS UNIX file. ExplanationThis is an informational message. The permissions defined for the z/OS UNIX file do not allow you to read the file or search some component of the pathname prefix. User responseContact the file owner or the z/OS UNIX system administrator to see if the file permissions can be altered to allow you to read the file. ISRP513 Recovery failed - Unable to allocate target z/OS UNIX file aaaaaaaa. ExplanationThe attempt to allocate the target z/OS UNIX file &ZEPATH; was unsuccessful. The file may have been deleted, or another user may have an exclusive enqueue on the file. User responseIf another user has exclusive use of the file, try again later. ISRP514 File aaaaaaaa - File was aaaaaaaa..
File bbbbbbbb exists. ExplanationThis is an informational message. The data from a z/OS UNIX filet 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 file. ISRP515 File aaaaaaaa - File was aaaaaaaa..
File bbbbbbbb exists. ExplanationThis is an informational message. The z/OS UNIX file was copied or moved. The data in the file that the data was copied from still exists, or the file that the data was moved from no longer exists. ISRP516 Requested line(s) copied - Lines aaaaaaaa through bbbbbbbb of
file were copied. ExplanationThis is an informational message. The requested lines from the z/OS UNIX file were copied. ISRP517 File not moved - The Move command was not confirmed. ExplanationThe Confirm Move panel was displayed at the user's request. The user chose not to move the z/OS UNIX fie set by entering the END command. The Confirm Move panel is only displayed if confirm move was chosen. ISRP518 WS edit not supported - Editing of a z/OS UNIX file
using a workstation editor is not supported. ExplanationISPF does not provide support for the editing of z/OS UNIX files using a workstation editor. User responseDo not select the 'Edit on Workstation' option when editing a z/OS UNIX file. ISRP519 File not edited - The request to edit a z/OS UNIX file
with authorized extended attributes was not confirmed. ExplanationThe user requested to edit a z/OS UNIX file which has one or more authorized extended attributes set. Editing such a file can cause the authorized extended attributes to be reset. ISPF displayed a confirmation panel to allow the user to proceed with the edit or not. The user chose not to proceed. ISRP520 PACK is invalid - PACK mode cannot be turned on for a z/OS UNIX file. ExplanationPacked format data is not supported for z/OS UNIX files. User responseDo not issue the PACK ON command when editing a z/OS UNIX file. ISRP521 Record too large - The z/OS UNIX file contains a record with
a length greater than 32750. Records of this size are not supported
by the ISPF editor. ExplanationISPF found the z/OS UNIX file contained a record greater than 32750 bytes in length. This is larger than the record length supported by the ISPF editor for Unix files. User responseIf you want to look at the data in the file, use ISPF BROWSE and specify a appropriate record length. ISRP522 Invalid line command - The valid line commands for this directory
selection list are S (Select), B (Browse), and L (List subdirectory). ExplanationThe z/OS UNIX directory selection list displayed for the edit MOVE and COPY commands only supports the S (Select), B (Browse), and L (List subdirectory) line commands. User responseOnly use the S, B, or L line commands on this directory selection list. ISRP523 Invalid pathname - Using + (plus) to represent the current
directory pathname is only valid when currently processing a z/OS UNIX file. ExplanationYou can only specify a relative pathname with a primary command when you are currently editing, viewing, or browsing a z/OS UNIX file. User responseSpecify the absolute pathname for the z/OS UNIX file. ISRP524 No home directory - A call to BPX1GPN (getpwnam) failed to
resolve your home or initial working directory. ExplanationYou specified the ~ (tilde) character at the start of a pathname to represent you home or initial work directory. ISPF called BPX1GPN to obtain information about your user ID but it was unable to determine your working directory. User responseContact your security administrator to see if your user information is correctly recorded in the security database. ISRP525 Permission denied - You do not have the necessary permission
to remove the directory entry for the file being moved. ExplanationOne of these conditions exist:
User responseCheck with your z/OS UNIX system administrator to see if the file permissions can be altered to allow you to move the file. ISRP526 Permission denied - You do not have the necessary permission
to write to the file to be created or replaced. ExplanationThe permissions defined for the target file do not allow you to write data to the file. User responseContact the filw owner to see if the file permissions can be changed to allow you to write to the file. ISRP527 Invalid FILE parameter - The variable specified with the
FILE parameter was not found or is invalid. ExplanationEither the variable was not found, a value was not specified for the variable, the value was too large for a pathname, or the name of the variable is invalid. User responseSpecify the name of a variable containing a pathname with the PATH parameter. ISRP528 Load failed for ISRUUDL - The load of the z/OS UNIX directory
list utility load module (ISRUUDL) failed. ExplanationISPF was unable to load module ISRUUDL. User responseCheck the load library concatenation sequence (ISPLLIB, STEPLIB, and so forth) to ensure that the library containing ISRUUDL is included. ISRRS000 aaaaaaaa - bbbbbbbb -
Member or Member pattern - aaaaaaaa - bbbbbbbb. ExplanationThis is an informational message. The member or pattern named in the message was Browsed, Printed, Renamed, Deleted, Moved, Copied, Edited, Reset, Viewed, or a command executed as specified. ISRRS001 Action mismatch - 'aaaaaaaa' organization
must be partitioned to perform this action. ExplanationThe option or line command selected requires a partitioned data set. ISRRS002 Personal List not found - Personal list is not defined as
one of your personal data set lists. ExplanationInformational only. ISRRS003 Personal list not found - The Personal list was not found. ExplanationThe personal list name was not found in the list of personal lists. User responseRetry, with a different list name Programmer responsenone ISRRS004 Data Set - aaaaaaaa - Data set - 'bbbbbbbb'
- aaaaaaaa.
ISRRS005 No data sets matched - No data sets matched the entries in
the referral list.
ISRRS006 Workstation file aaaaaaaa - Workstation
file aaaaaaaa successfully. ExplanationInformational only ISRRS007 No default set - No default open action has been defined,
or open action requested from enhanced member list which does not
support action "OPEN". User responseSelect a default for the Open action on the workplace settings panel. ISRRS008 Open not supported - The Open action is not supported from
LIBRARY or DSLIST utility.
ISRRS009 List aaaaaaaa of bbbbbbbb -
List aaaaaaaa of bbbbbbbb
ISRS000 No differences found - Normal completion (RC=0). Files compare
equally. ExplanationThis is an informational message. No differences were found by SuperC. User responseSee the SuperC listing data set for further information. ISRS001 Differences found - Normal completion (RC=1). Files are
not the same. ExplanationThis is an informational message. Differences were found by SuperC. User responseSee the SuperC listing data set for the differences and further information. ISRS002 Invalid input detected - Abnormal completion (RC=4). See
listing for warning. ExplanationThis is a warning message. The compare was performed; however, erroneous or conflicting input options have been detected by SuperC and reported in the SuperC listing data set. User responseCheck the SuperC listing data set for explanations of the invalid input. The compare results may not be consistent with your expectations. ISRS003 Bad sequence numbers - Abnormal completion (RC=6). See listing
for warning. ExplanationThis is a warning message. The old data set (OLDDD) does not contain proper sequence numbers, or the sequence number intervals are not large enough to contain insert activity. This applies only to UPDCMS8 or UPDMVS8 process options. User responseVerify that the old data set name is correct. Verify that sequence numbers exist in the old data set; create them if necessary. The NUMBER ON command in EDIT may be used. Use the RENUM command in EDIT to expand the sequence number intervals if necessary. ISRS004 Old input file error - Abnormal completion (RC=8). See listing
for details. ExplanationThere is an error involving the old input data set (OLDDD) and the compare was not performed. For example, if you modified the JCL and inadvertently omitted the OLDDD allocation, SuperC would return code 8. This error is also received if the old data set fails to open, perhaps because of an I/O error. User responseCheck the SuperC listing data set for specific information describing the error. Correct the JCL and resubmit. ISRS005 Bad grouping - Abnormal completion (RC=12). See listing
for details. ExplanationThis message indicates inconsistent data set organizations. The new and old data sets are not both PDSs or sequential data sets. The compare was not run. User responseMixed compares of PDS to sequential data sets are not permitted. The dialog interface prevents this, but you may have incorrectly modified or submitted JCL that attempts to allocate OLDDD to a PDS and NEWDD to a sequential (or vice versa). Correct the allocations and retry. ISRS006 New input file error - Abnormal completion (RC=16). See
listing for details. ExplanationThere is an error involving the new input data set (NEWDD). The compare was not performed. For example, if you modified the JCL and inadvertently omitted the NEWDD allocation, SuperC would return code 16. This error is also received if the new data set fails to open, perhaps because of an I/O error. User responseCheck the SuperC listing data set for specific information describing the error. Correct the JCL and resubmit. ISRS007 Bad update data set - Abnormal completion (RC=20). See listing
for details. ExplanationThere has been an error involving the update output data set (DELDD). Typically, the cause is a space abend writing to the data set, although an I/O error is also possible. If you modified the JCL and inadvertently omitted the DELDD allocation, then SuperC would also return code 20. User responseCheck the SuperC listing data set for specific information describing the error. Correct the JCL and resubmit. If the problem is a space abend, delete the update data set and preallocate larger with option 3.2 or specify larger default allocation parameters using option 3.13.A.D. ISRS008 Listing file error - Abnormal completion (RC=24). Listing
empty/incomplete. ExplanationError occurred during open or while writing to the SuperC listing output data set (OUTDD). This error can also be returned due to a NEW or OLD input data set simultaneously being used as the listing data set. The listing data set may or may not contain further information. User responseVerify that the name of the listing data set is not the same as any of the input data sets. Delete the listing data set and retry. ISRS009 No data compared - Abnormal completion (RC=28). See listing
for details. ExplanationNo data was compared because the old and new data sets were empty, member names were invalid, or nothing was left to compare after input filtering (such as DPPLCMT on a data set containing only comments). If you attempted a search, strings were not found due to empty input data sets, or nothing was left to search after input filtering. User responseVerify that the correct old and new data sets were specified. Verify that the SELECT process statements designate members that exist in the input data sets. Modify the input filtering statements and options so that something is left to compare or search. ISRS010 Insufficient storage - Abnormal completion (RC=32). See
listing for error. ExplanationInsufficient storage is available for the SuperC program to run. The region size is either too small or storage is too fragmented. User responseConsider submitting the SuperC job to batch, specifying a REGION= keyword and sufficient storage on the job card for the job to run. If batch is unavailable, consult your system programmer for instructions on how to temporarily increase your available region size at session logon. ISRS011 No UPDATE option - UPD Display Output options inconsistent
with no update process selected. ExplanationThis message is self explanatory. ISRS012 Member list error - Member list not applicable. ExplanationThis message is self explanatory. ISRS013 No differences found - Normal completion (rc=0). Files compare
equally. ExplanationThis message is self explanatory. ISRS014 Differences found - Normal completion (rc=1). Files are
not the same. ExplanationThis message is self explanatory. ISRS015 No update file created - No differences found. No update
file created. ExplanationThis message is self explanatory. ISRS016 Display Output conflict - Display Output UPD specified with
no update process option. ExplanationSetting the Display Output field to UPD implies that you are creating an update data set as output from your compare job. SuperC has detected that you have neglected to supply a process option (such as UPDPDEL) that would result in an update data set. Consequently, the request to Browse or View the UPD output is an error. User responseEither supply an update process option using option P, or change your Display Output field to YES, NO, or COND instead of UPD. ISRS017 ***** SuperC aaaaaaaa compare invoked.
***** ExplanationThis is an informational message. The foreground SuperC compare is executing. The message specifies which type of compare it is (LINE, WORD, FILE, or BYTE). ISRS018 Append to PDS invalid - Data set organization and append
option conflict. ExplanationIt is not valid to attempt to append to a SuperC listing that is a member of a partitioned data set. This action is only valid for sequential data sets. SuperC only replaces the content of PDS members. It will not add to them. User responseVerify that the list data set is sequential, or remove the APNDLST process option from the input to SuperC. ISRS019 Bad ds organizations - Concatenated data sets must have consistent
DS organizations. ExplanationSuperC cannot search or compare a mixture of partitioned and sequential data sets. All data sets in the NEW and OLD concatenation must be of the same organization. MVS concatenation rules will not permit the allocation of a mixture. User responseVerify that all data sets within the NEW and OLD concatenation (DS1-DS4) are all sequential or all partitioned. This may be done using option 3.4 ATTRIB view and inspecting the DSORG field. All data sets need to be PS or PO, unmixed. ISRS020 Mutually exclusive - aaaaaaaa and bbbbbbbb are
mutually exclusive. ExplanationAn invalid combination of process options was specified. The two process options substituted into the message are an either/or pair and are not meaningful in conjunction. User responseRemove one (or both) of the mutually exclusive options. Consult the tutorials and documentation for detailed explanations of the meaning and usage of each option. ISRS021 Unrecognizable keyword - aaaaaaaa is an
unrecognizable process option. ExplanationThe process option substituted into your message is unknown to SuperC. User responseVerify that the option is spelled correctly. Use option P in 3.13 or 3.13.S to select available process options. Remove the invalid option from the PROCESS OPTION input field before SuperC will continue. Consult the tutorials and documentation for a list of valid process options, some options are only valid for certain compare types. ISRS022 Keyword conflict - aaaaaaaa is invalid
for bbbbbbbb compare type. ExplanationThe process option you are specifying is not applicable for the compare type you are requesting. User responseEither remove the invalid process option from process options field on the panel or change the compare type to one valid for the process option. Use option P for a selection list of valid options for the current compare type. ISRS023 Inconsistent keyword - APNDUPD without update options are
specified. ExplanationYou have specified the APNDUPD process option, implying you wish to append output to an update file. However, you have not specified an option that will cause update file output to be created. User responseEither add an update file creation option (such as UPDMVS8), remove the APNDUPD, or change it to APNDLST, if you want to append compare output to an existing SuperC listing. Option P may be used to get a selection list of process options. ISRS024 Return (aaaaaaaa) - No description of
return code value. ExplanationSuperC has returned an undefined return code. System programmer responseThis is a possible ISPF installation problem. Verify that ISRSUPC is at the correct release level and that no other level of release exists on your system. Have your user check the header in his SuperC output. It should contain the current release of ISPF installed on your system. If no mixed release or wrong version of SuperC is evident, contact IBM support. User responseThis is a SuperC programming error or possible installation problem. Please write down the return code captured in the short message field and contact your system programmer. ISRS025 DS organization mismatch - New/old data set organizations
are not compatible. ExplanationYou are attempting to compare one or more partitioned data sets to one or more sequential data sets. This is not supported by SuperC. SuperC requires that all data sets be of the same organization, either all partitioned or all sequential. A partitioned data set specified with a member name - PDS(MEMBER) - is treated as a sequential for purposes of this requirement. User responseCorrect the old and new data sets specified to comply with the data set organization matching rule. ISRS026 Too many process options - Unable to assemble all selected
options on panel line(s). ExplanationThe maximum number of process options that will fit on the 2 lines available for them has been exceeded. Those that will fit have been carried forward to the panel, but one or more specified in option P are missing. User responseEliminate any redundant, conflicting, or unnecessary process options. It may be possible to squeeze in a few more by using option B to submit a batch compare, editing the JCL, and adding them to the PARM string to SuperC. Be aware that MVS limits the overall length of the PARM string to 255. If this limit is exceeded, a JCL error occurs. ISRS027 Password not accepted - Password only valid when used with
"Other data set name". Cleared. ExplanationInput has been entered in the Password field, perhaps inadvertently. This is only accepted when the corresponding Data Set Name is filled in. Passwords are not accepted for the DS1-4 fields. SuperC has cleared the password field. User responseNo action is required unless you intend to compare a password protected data set, in which case you are restricted to using the Data Set Name field and Password field. ISRS028 Invalid option - Only "3.13.S " (SRCHFOR) and "3.13.A " (Activate/Create)
are valid. ExplanationYou have attempted to jump into option 3.13 (SuperCE) with an invalid option, =3.13.X, for example. User responseYou may jump directly into Searchfor or profile manager using =3.13.S or =3.13.A; otherwise, you must use =3.13 to jump to SuperCE. From there you may specify the individual option you want (for example, E), for editing statements data sets. ISRS029 No strings searched - Abnormal completion (RC=28). See listing
for details. ExplanationNo string search was attempted because the search data set or members were empty. This may have resulted from filtering. For example, DPLINE or DPPLCMT statements may have eliminated all candidate lines from the input. User responseSee the Searchfor listing data set for details. You may need to adjust input filtering statements to exclude fewer lines from the search set. Verify that the search data set is not empty. ISRS030 Required field - First concatenation or "Other data set name"
must be specified. ExplanationAt a minimum, either the DS1 field or the Other Data Set field must be filled in for the new and old (or search) data sets. If both are filled in, the Other Data Set field will be used. User responseFill in either required field and retry. ISRS032 Profile created - Profile DS 'aaaaaaaa'
is created. ExplanationThe profile data set or member named in the message, which did not previously exist, has been created for you. User responseUse the created profile in option 3.12 or option 3.13 to specify compare options. ISRS033 Profile activated - Profile DS 'aaaaaaaa'
is activated. ExplanationThe profile data set in the message has been read and its process and compare options written to the panel for your use. If the profile data set contains any process statements, it has replaced the Statements Dsn name on the panel. User responseThe compare options contained in the profile data set are now transferred to the panel. You may now specify the compare data sets and run the compare. ISRS034 ****** SuperC Search-for invoked. ****** ExplanationThe search is now in progress. Depending on the amount of input to be searched, this may take some time. Typically, the next thing you see is a browse session of a listing data set that contains the results of the search. If no strings are found, you receive only a message, but the listing data set has been created and may be browsed by you outside of the SuperC dialog. User responseConsider submitting a batch search to avoid tying up your session during lengthy searches. This may be done using either option 3.14 or 3.13.S.B. ISRS035 * Search-for invoked. String(s) used from statements data
set * ExplanationThe search is in progress. However, since SRCHFOR or SRCHFORC statements are specified in a statements data set, they are used to specify the strings to be searched instead of the strings specified on the panel. The strings in the statements data set override the strings on the panel. User responseNone, unless you wanted to use the panel strings, in which case blank out the Statements Dsn field, or remove the SRCHFOR statements from the statements data set. ISRS036 No strings found - Search-for completed with no strings found.
See listing for details. ExplanationThe search is complete with no strings found. There may be further information in the search listing data set, which may be browsed outside of Searchfor. Input filtering (DPLINE, for example) may have hidden strings that otherwise would be found. User responseIf this result is unexpected, consider editing the statements data set (if one was specified) and investigating the filtering options. Also browse the listing data set. ISRS037 Strings found - Search-for completed. Strings were found. ExplanationThis is an informational message. The search was completed successfully with strings found. Other possible outcomes are no strings found, no strings searched, or errors. ISRS038 Edit error - Severe error detected on call to editor. ExplanationThis message is self explanatory. ISRS039 Profile replaced - Profile DS 'aaaaaaaa'
is replaced. ExplanationThe profile data set or member named in the message has been replaced for you. It previously existed. User responseUse the profile in option 3.12 or option 3.13 to specify compare options. ISRS040 Profile not created - Invalid compare type: aaaaaaaa. ExplanationThe attempt to create a profile was not successful because the Compare Type field is invalid. Valid types are LINE, FILE, BYTE, and WORD. User responseCorrect the invalid compare type and retry. ISRS041 Profile not created - Invalid listing type: aaaaaaaa. ExplanationThe attempt to create a profile was not successful because the Listing Type field is invalid. Valid types are OVSUM, DELTA, CHNG, LONG, and NOLIST. User responseCorrect the invalid listing type and retry. ISRS042 Profile not created - aaaaaaaa and bbbbbbbb are
mutually exclusive. ExplanationThe attempt to create a profile was not successful because the two Process options named in the message are not valid in combination. User responseEliminate either (or both) of the process options and retry the operation. ISRS043 Profile not created - aaaaaaaa is an unrecognizable
process option. ExplanationThe attempt to create a profile was unsuccessful because the process option named in the message is not valid. User responseCorrect the spelling of the process option and retry. Use option P for a selection of process options. ISRS044 Profile not created - aaaaaaaa is invalid
for bbbbbbbb compare type. ExplanationThe attempt to create a profile was unsuccessful because the process option named in the message is not valid in combination with the specified compare type. User responseEliminate the offending process option or change the compare type and retry. Use option P for a selection of process options valid with the current compare type. ISRS045 Profile not created - APNDUPD without update options are
specified. ExplanationThe attempt to create a profile was unsuccessful because the APNDUPD process option implies that you are creating an update file but no UPD process option is specified. User responseSpecify a UPD process option to create an update file, or use APNDLST instead of APNDUPD to specify append to the listing data set. Retry. ISRS046 Profile not created - Invalid browse option: aaaaaaaa. ExplanationThe attempt to create a profile was unsuccessful because the Browse output field is invalid. Valid types are YES, NO, COND, and UPD. User responseCorrect the invalid browse output selection and retry. ISRS047 Statements DS saved - Edit session for process statements
DS is complete. changes saved. ExplanationThis is an informational message. This message confirms that you made changes to the statements data set using option E. These changes were saved in the data set or member. ISRS048 Job submitted - JCL generated and submitted to the job scheduler. ExplanationThis message confirms that your batch compare or search job was submitted. It is still possible that there may be JCL errors and the job will fail, but the process of creating and submitting the JCL succeeded. User responseMonitor the job for completion. You need not remain in the SuperC dialog. ISRS049 Listing not generated - Abnormal completion (RC=25). Existing
list DS attribute conflict. ExplanationThe listing data set was not allocated due to a conflict with the LRECL, RECFM, or DS organization. A listing may only be saved in a PDS with identical DS attributes (that is, LRECL or RECFM); an APNDLST may never be done to a PDS; and an APNDLST may only be made to a sequential DS with identical attributes. No output was generated. User responseUse a new name for the listing data set that is not the same as an existing data set, or delete the existing data set (if it is not one you want to keep) so that SuperC can reallocate it with the proper attributes. ISRS050 Listing data set full - Listing data set or volume is full.
Delete and preallocate larger using option 3.2 or delete and increase
default space parms using option 3.13.A.D ExplanationThe listing data set or the volume on which it resides is out of space and could not hold all the output that SuperC attempted to generate. User responseIf the data set is sequential, you may delete it and preallocate it larger using option 3.2, or use option 3.13.A.D to increase the default space allocation parameters. If the data set is partitioned, you may attempt to compress it using option 3.1. If the volume is out of space, you may need to consult your system programmer for advice on where to allocate the listing data set. ISRS051 Invalid profile - Profile contains an invalid compare type: aaaaaaaa. ExplanationThe profile data set or member contains the invalid compare type indicated in the message. This is most likely the result of a manual edit of the profile that has corrupted it. Profiles normally should be modified only using option 3.13.A CREATE profile. User responseYou may edit the profile and correct the invalid compare type in the first PROF PREFIX statement at line 1. The syntax is CTYP=FILE/LINE/WORD/BYTE. Alternatively, you may use the option 3.13.A CREATE function to replace the invalid profile with new values taken from the 3.13 panel. ISRS052 Invalid profile - Profile contains an invalid listing type: aaaaaaaa. ExplanationThe profile data set or member contains the invalid listing type indicated in the message. This is most likely the result of a manual edit of the profile that has corrupted it. Profiles normally should be modified only using option 3.13.A CREATE profile. User responseEdit the profile and correct the invalid listing type in the first PROF PREFIX statement at line 1. The syntax is LTYP=OVSUM/DELTA/CHNG/LONG/NOLIST. Alternatively, use the option 3.13.A CREATE function to replace the invalid profile with new values taken from the 3.13 panel. ISRS053 Invalid profile - Profile contains an invalid Display Output
parameter: aaaaaaaa. ExplanationThe profile data set or member contains the invalid Display Output parameter indicated in the message. This is most likely the result of a manual edit of the profile that has corrupted it. Profiles normally should be modified only using option 3.13.A CREATE profile. User responseEdit the profile and correct the invalid Display Output parameter in the first PROF PREFIX statement at line 1. The syntax is BRW=YES/NO/COND/UPD. Alternatively, use the option 3.13.A CREATE function to replace the invalid profile with new values taken from the 3.13 panel. ISRS054 Invalid profile - aaaaaaaa and bbbbbbbb are
mutually exclusive. ExplanationThe profile data set or member contains the invalid combination of process options indicated in the message. This is most likely the result of a manual edit of the profile that has corrupted it. Profiles normally should be modified only using the option 3.13.A CREATE profile. User responseEdit the profile and correct the PROF PREFIX statements at lines 2 and 3 by specifying a valid combination of process options. Alternatively, use the option 3.13.A CREATE function to replace the invalid profile with new values taken from the 3.13 panel. ISRS055 Invalid profile - aaaaaaaa is an unrecognizable
process option. ExplanationThe profile data set or member contains the invalid process option indicated in the message. This is most likely the result of a manual edit of the profile that has corrupted it. Profiles normally should be modified only using the option 3.13.A CREATE profile. User responseEdit the profile and correct the PROF PREFIX statements at lines 2 and 3 by specifying a valid combination of process options. Alternatively, use the option 3.13.A CREATE function to replace the invalid profile with new values taken from the 3.13 panel. ISRS056 Invalid profile - aaaaaaaa is invalid
for bbbbbbbb compare type. ExplanationThe profile data set or member contains the invalid process option and compare type combination indicated in the message. This is most likely the result of a manual edit of the profile that has corrupted it. Profiles normally should be modified only using option 3.13.A CREATE profile. User responseEdit the profile and correct the PROF PREFIX statements at lines 1, 2, and 3 by specifying a valid combination of process options and compare type. Alternatively, use the option 3.13.A CREATE function to replace the invalid profile with new values taken from the 3.13 panel. ISRS057 Invalid profile - APNDUPD without update options are specified. ExplanationThe profile data set or member contains the invalid combination indicated in the message. This is most likely the result of a manual edit of the profile that has corrupted it. Profiles normally should be modified only using the option 3.13.A CREATE profile. User responseEdit the profile and correct the invalid combination by specifying a valid update process option in the PROF PREFIX line 2. Alternatively, use the option 3.13.A CREATE function to replace the invalid profile with new values taken from the 3.13 panel. ISRS058 Invalid ds RECFM/LRECL - Profile and statements data sets
must be fixed 80. ExplanationVerify that the name of the data set that you are attempting to use for a SuperC profile data set is not mistyped. Alternatively, you may have created the data set yourself to be used as a SuperC profile but with an incorrect LRECL. User responseCheck the spelling of the data set name. If you are using option 3.13.A CREATE to create a data set for use as a SuperC profile data set, you may need to specify another name because the name you have chosen already exists. If you allocated the data set yourself, verify that the LRECL is FIXED 80. If it is not, correct it and retry. Always browse the data set to check the contents before deleting it. ISRS059 Invalid profile prefix - Profile prefix record is incorrect
or missing. ExplanationThe profile data set or member does not contain valid prefixes to the first 3 records. It is probable that a data set was specified that is not a SuperC profile. SuperC profiles contain .* PROF PREFIX in the first 14 positions of the first 3 records and are FIXED 80 LRECL. User responseVerify that the name of the data set is correct. Otherwise, you may need to edit the profile to correct the invalid prefix. Alternatively, use the option 3.13.A CREATE function to replace the invalid profile with new values taken from the 3.13 panel. Be certain this is data that does not need to be preserved. A backup copy might be a good idea. ISRS060 Error in SUBMIT - SUBMIT error. ExplanationThe TSO SUBMIT command returned a nonzero return code. The job was not submitted successfully. This is either an MVS system problem or an internal ISPF processing failure. System programmer responseISPF selects the TSO SUBMIT command passing a temporary data set. There may be information in the user's ISPF LOG data set or in the system log. Attempt to run the TSO SUBMIT command from option 6 to see if there is a TSO problem. If the SUBMIT only fails from within ISPF, contact IBM support. User responseSave or print the ISPF LOG data set for your system programmer. This may be done by temporarily exiting ISPF. Write down the circumstances of the failure and contact your system programmer. ISRS061 FTOPEN error - Error using FTOPEN. ExplanationThis is a probable ISPF internal processing failure. ISPF was unable to open a temporary data set for file tailoring the JCL statements to be submitted. System programmer responseAn ISPF FTOPEN TEMP call has failed. There may be information in the user's ISPF LOG data set or in the system log. If you are unable to resolve the problem, contact IBM support. User responseSave or print your ISPF LOG data set for your system programmer. This may be done by temporarily exiting ISPF. Write down the circumstances of the failure and contact your system programmer. ISRS062 File tailor failure - File include. ExplanationThis is a probable ISPF internal processing failure. ISPF was unable to file tailor JCL statements into the temporary data set to be submitted. System programmer responseAn ISPF FTINCL SKELNAME call has failed. There may be information in the user's ISPF LOG data set or in the system log. Make sure the ISPF SKELS data set (ISPSLIB) is properly allocated by the user's logon proc. If you are unable to resolve the problem, contact IBM support. User responseSave or print your ISPF LOG data set for your system programmer. This may be done by temporarily exiting ISPF. Write down the circumstances of the failure and contact your system programmer. ISRS063 File tailor failure - File close. ExplanationThis is a probable ISPF internal processing failure. The JCL to be submitted was not successfully generated. System programmer responseAn ISPF FTCLOSE call has failed. There may be information in the user's ISPF LOG data set or in the system log. If you are unable to resolve the problem, contact IBM support. User responseSave or print your ISPF LOG data set for your system programmer. This may be done by temporarily exiting ISPF. Write down the circumstances of the failure and contact your system programmer. ISRS064 Invalid search-string - Matching end quote around string
missing. ExplanationUnbalanced quotation marks were detected in the search string(s). If you are attempting to enter a DBCS string that contains a x'7D' as part of a DBCS pair you must use the Enhanced SearchFor option (option 3.15) specifying the MIXED process option. User responseCorrect and retry. Two consecutive quotation marks may be used to specify one searchable quotation mark. For example, DON''T is a correct specification to find the string don't. ISRS065 Invalid search-qualifier - Must be WORD, PREFIX, SUFFIX or
C (continued). ExplanationSuperC has detected an invalid operand outside of the search string itself. This may be because a quotation mark intended to be part of the search string has prematurely terminated the string. Data to the right of the quotation mark is treated as a search qualifier. User responseEnclose the entire string in single quotation marks and double any embedded data quotation marks. For example: 'DON''T RUN' Alternatively, correct the spelling of the search qualifier and retry. ISRS066 Search string required - The search string must be specified
or be in statements input. ExplanationNo search string was specified from option 3.13.S Search-For, either on the panel or in a statements data set. User responseEither specify one or more of the 5 search string fields on the panel (CAPS or ASIS fields), or specify one or more SRCHFOR statements in the statements data set. The statements data set specification will override the strings specified on the panel. ISRS067 Hex character not paired - The hex string has an uneven pair
of hex characters. ExplanationThe hexadecimal string you have specified is incorrect. There must be an even number of hexadecimal characters for a valid string. User responseCorrect the hexadecimal string and retry. For example: Use X'F0F0' Not X'F1F' ISRS068 Invalid hex string - The hex string has an invalid character
within the specified string ExplanationHexadecimal characters must be in the range 0-9 or A-F. User responseCorrect the hexadecimal string and retry. For example: Use X'F123' Not X'ZZZZ' ISRS069 Null string invalid - A null string is an unacceptable search
argument. ExplanationSuperC cannot search for a null string. One blank is the minimum valid string. User responseCorrect the search string and retry. For example: Use ' ' Not '' to search for one blank character on a line. ISRS070 No member in PDS - PDS has no members. Invalid selection
candidate. ExplanationThis message is self explanatory. ISRS071 LMMLIST error - Error return from LMMLIST is aaaaaaaa. ExplanationThis message is self explanatory. ISRS072 List canceled by user - User entered a CANCEL command during
member list processing. ExplanationThis message is self explanatory. ISRS073 Specify member name - Command specified requires a member
name. ExplanationThis message is self explanatory. ISRS074 Member name too long - Member name must be less than or equal
to 8 characters. ExplanationThis message is self explanatory. ISRS075 No members with pattern - The data set has no members with
pattern "aaaaaaaa". ExplanationThis message is self explanatory. ISRS076 Invalid command - Valid commands are LOCATE (L), CANCEL (C)
and ALL (A). ExplanationThis message is self explanatory. ISRS077 Selections canceled - User request cancellation of new process
option selections. ExplanationThis is an informational message. This message confirms that you have canceled out of the process option selection dialog. The options are not changed. ISRS078 Data set in use - The data set or member is in use by you
or another user. ExplanationThis message is self explanatory. ISRS079 Invalid embedded quote - A quote may be used as a delimiter
or specified as two quotes. ExplanationThe search string contains an ambiguous quotation mark. Quotation marks are used in pairs to delimit the beginning and end of the search string if it contains embedded blanks. They may also be used to specify a searchable quotation mark, in which case two consecutive quotation marks are understood to be one and are taken as data instead of as a delimiter. If you are attempting to enter a DBCS string that contains a x'7D' as part of a DBCS pair you must use the Enhanced SearchFor option (option 3.15) specifying the MIXED process option. User responseCorrect and retry. Two consecutive quotation marks may be used to specify one searchable quotation mark. For example: DON''T is the correct specification to find the string don't. ISRS080 Allocation error - Allocation error on "new" data set. ExplanationThe TSO allocation of the specified data set to the NEWDD DDNAME requested by SuperC was unsuccessful, an unexpected result. This is probably either a SuperC internal processing failure or an ISPF installation problem. It is also possible that the data set has been deleted or exclusively allocated by another job or user between the time SuperC checks for the availability of the data set and the time the allocation is attempted. System programmer responseDetermine whether the user is running the CLIST or PROGRAM interface to SuperC. User's option 3.13.A.D and the PDF configuration table will determine this. If the user is in CLIST mode, verify that the user is running an uncorrupted version of ISRSFORG (or ISRSSRCH) CLIST by checking his SYSPROC allocation. Mixed level of code is possible, and the user could be picking up an old copy of the CLIST. Also, be sure that you are at current maintenance levels. There have been problems in the past with allocations of exotic data sets (aliases, uncataloged data sets with same name as cataloged data sets). Try to recreate the problem yourself. There may be some reasonable and correctable explanation for why the allocation is failing. If not, contact IBM support. User responseRetry the process. The condition causing the failure may be transient and may have resolved. You may also receive a more helpful error message the second time, if, for example, the data set was deleted before the allocation could succeed. If the problem persists, write down the circumstances of the failure and contact your system programmer. The ISPF log may contain useful information and can be printed or saved by temporarily exiting ISPF. It may be useful for your system programmer to know whether you are running SuperC in CLIST or PROGRAM mode. This can be determined by going to option 3.13.A.D and checking whether "Invoke SuperC via program interface" is selected. ISRS081 Allocation error - Allocation error on "old" data set. ExplanationThe TSO allocation of the specified data set to the OLDD DDNAME requested by SuperC was unsuccessful, an unexpected result. See ISRS080. ISRS082 Allocation error - Allocation error on "listing" data set. ExplanationThe TSO allocation of the specified data set to the OUTDD DDNAME requested by SuperC was unsuccessful, an unexpected result. See ISRS080. ISRS083 Allocation error - Allocation error on "statements/profile"
data set. ExplanationThe TSO allocation of the specified data set to the SYSIN DDNAME requested by SuperC was unsuccessful, an unexpected result. See ISRS080. ISRS084 Allocation error - Allocation error on "member names" data
set. ExplanationThe TSO allocation of the specified data set to the SYSIN2 DDNAME requested by SuperC was unsuccessful, an unexpected result. See ISRS080. ISRS085 Allocation error - Allocation error on "update" data set. ExplanationThe TSO allocation of the specified data set to the DELDD DDNAME requested by SuperC was unsuccessful, an unexpected result. See ISRS080. ISRS086 Allocation error - Allocation error on "search" data set. ExplanationThe TSO allocation of the specified data set to the NEWDD DDNAME requested by SuperC was unsuccessful, an unexpected result. See ISRS080. ISRS087 aaaaaaaa - bbbbbbbb ExplanationThis message is self explanatory. ISRS088 Invalid member name - Member name not valid for a partitioned
data set. ExplanationOne or more invalid characters were entered in the member name. User responseCheck that the member name entered is a character string of up to 8 alphanumeric characters, the first of which is either alphabetic or $, #, or @. Alternatively, you may enter a pattern (example: ABC* for a list of all members starting with ABC) or no member name and select members from a list. ISRS089 Old-mem not found - The member "aaaaaaaa",
selected for the old data set, was not found. ExplanationA single member was selected from the selection list panel for the New DS Name partitioned data set and ended from the panel. SuperC attempted to compare this single member to a member of the same name in the Old DS Name partitioned data set, but the member did not exist. User responseCheck that the Old DS Name is specified correctly. If it is correct, consider specifying an alternative old DS member name in the OLDMEM field on the member selection list panel, and compare a member in the list to a member of a different name. ISRS090 Volume serials required - Both volume serials required for
different new/old data set with same name. ExplanationThis message is self explanatory. ISRS091 Too many operands - Only WORD, SUFFIX, or PREFIX and/or C
are allowed. ExplanationThe search argument specified is invalid because it contains more than the maximum of two keywords in addition to the search string. You may receive this message if you have neglected to enclose a search string of several words in quotation marks. Example: 'This is just a test' User responseCorrect the search string and retry the search. Note that WORD, SUFFIX, and PREFIX are mutually exclusive. Only one may be specified for each string. C (for continuation) may be used with or without the other three operands to indicate that 2 or more strings must be found on the same line to constitute a find. ISRS092 Incorrect operands used - "aaaaaaaa" and
"bbbbbbbb" are mutually exclusive or redundant. ExplanationWORD, PREFIX, and SUFFIX may not be used together to qualify the same search string, they must stand alone. WORD means delimited by blanks, PREFIX means starting a word, SUFFIX means ending a word. User responseCorrect the search string specification and retry the search. ISRS093 Concatenation disallowed - All data set logical record lengths
(LRECL) must be identical to concatenate. ExplanationAn attempt has been made to concatenate 2 or more data sets with different logical record lengths. This is not allowed by MVS. Possibly one of the data set names is misspelled, or you are inadvertently attempting to concatenate different types of data, such as source and listings. User responseCheck that the list of concatenated data sets is the one you need. Use option 3.2 or 3.4 data set information functions to find the LRECLs of the data sets. Correct and retry. ISRS094 Concatenation disallowed - All data set record formats (RECFM)
must be identical to concatenate. ExplanationYou have attempted to concatenate 2 or more data sets with different record formats, such as Fixed and Variable. This is not allowed by MVS. One of the data set names may be misspelled or you are inadvertently attempting to concatenate different types of data, such as source and listings. User responseCheck that the list of concatenated data sets is the one you need. Use option 3.2 or 3.4 data set information functions to find the RECFMs of the data sets. Correct and retry. ISRS095 Concatenation disallowed - Largest logical record length
(LRECL) must be first to concatenate. ExplanationFor RECFM Variable data sets, the largest LRECL must be the first in the concatenation, according to MVS rules. User responseReorder the data sets and retry the compare. Use the data set information function of options 3.2 or 3.4 to learn which data set has the largest LRECL. ISRS096 C invalid for string one - Continuation operand valid on
any or all subsequent search strings. ExplanationThe continuation operand (C) was specified on the first search string. This is not allowed. Continuation means that the string with the C, the continued string, must be found on the same line as the previous string to make a match. There is no previous string for string one. User responseRemove the continuation operand (C), from string one and put it on string 2 for continuation. Ensure that the search string is enclosed in quotes. The string (for example, Vitamin C) may have been interpreted as an invalid continuation attempt. Try 'Vitamin C' instead. ISRS097 Concatenation specified - Select options and press Enter
to display the concatenation panel. ExplanationThe user has requested either Extended SuperC or Extended SearchFor from the Workplace and has passed an ISPF library concatenation. The project, groups and type fields have been filled in on the concatenation panel. User responseEnter options and press Enter to get the concatenation panel. ISRS098 Volume specified - Select options and press Enter to display
the uncataloged data set panel. ExplanationThe user has requested either Extended SuperC or Extended SearchFor from the Workplace and has passed a volume field along with the Other Data Set. It is assumed that the data set is uncataloged. User responseEnter options and press Enter to get the uncataloged data set panel. ISRS099 Invalid command - Specify B, S, P, E or A for Batch, Srchfor,
Process options, Edit statements or Activate profiles, or use the
Options pulldown. ExplanationThese are the valid fast path commands for additional SuperC functions. ISRS100 Invalid command - Command "aaaaaaaa" is
undefined. ExplanationThis message is self explanatory. ISRS101 Vol serial not allowed - Use "Other data set name" field
when specifying volume serial. ExplanationA volume serial was specified on a panel when the Project/Group/Type fields were used for the data set name. The volume serial may only be specified when you use the Other Data Set Name field for the data set. User responseIf you are trying to access a data set on a particular volume, type the data set name in the Other Data Set Name field and place the volume name in the Volume Serial field before pressing the Enter key. ISRS102 Password not allowed - Password not allowed for batch job.
Use foreground mode. ExplanationThis message is self explanatory. ISRS103 Member name required - Member name is required for this partitioned
data set. ExplanationAdd a member name to complete the specification of the partitioned data set indicated by the cursor. User responseSpecify the member name and retry. Browse the data set if you are uncertain which member is correct. ISRS104 Enter "old" PDS name - Cannot compare "new" PDS to "old"
sequential data set or PDS member. ExplanationBecause the New data set is partitioned (contains members), the Old data set must also be partitioned. Valid combinations are PDS to PDS, Sequential to Sequential, PDS(member) to PDS(member), or Sequential to PDS(member). In other words, SuperC compares one to one or many to many, but not one to many. User responseSpecify a valid combination and retry. ISRS105 Enter "old" member name - Cannot compare "new" sequential
data set or PDS member to "old" PDS. ExplanationBecause the New data set is a sequential or a member of a PDS, the Old data set requires a member. Valid combinations are PDS to PDS, Sequential to Sequential, PDS(member) to PDS(member), or Sequential to PDS(member). In other words, SuperC compares one to one or many to many, but not one to many. User responseSpecify a valid combination and retry. ISRS106 Member name not allowed - Member name not allowed for sequential
data set. ExplanationThe sequential data set indicated by the cursor is incorrectly specified with a member name. Only partitioned data sets can accept member names. User responseRemove the member name and retry. ISRS107 TBCREATE failure - Creating the table of member selections
failed. ExplanationThis is an internal ISPF processing failure. System programmer responseThere may be information in the ISPF log that sheds light on this failure. Perhaps there is a problem with the user's ISPTABL or ISPTLIB allocation. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the failure and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS108 TBPUT failure - TBPUT or TBADD to table of member selections
failed. ExplanationThis is an internal ISPF processing failure. System programmer responseThere may be information in the ISPF log that sheds light on this failure. Perhaps there is a problem with the user's ISPTABL or ISPTLIB allocation. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the failure and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS109 LMMDISP(get) failure - Internal ISPF error processing member
list. ExplanationThis is an internal ISPF processing failure. System programmer responseThere may be information in the ISPF log that sheds light on this failure. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the failure and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS110 File tailor failure - File tailoring of member selections
failed. ExplanationThis is an internal ISPF processing error while attempting to file tailor statements into the SYSIN2 data set. System programmer responseThere may be information in the ISPF log that sheds light on this error. Perhaps there is a problem with the user's ISPTABL or ISPTLIB allocation. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the error and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS111 LMINIT failure - LMINIT of specified data set failed with
return code = aaaaaaaa. ExplanationThis is an internal ISPF processing error. System programmer responseThere may be information in the ISPF log that sheds light on this error. You might also try looking up the LMINIT return code in z/OS ISPF Services Guide . It is possible there is something wrong with the data set itself. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the error and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS112 LMMFIND failure - LMMFIND of specified data set failed with
return code = aaaaaaaa. ExplanationThis is an internal ISPF processing error. System programmer responseThere may be information in the ISPF log that sheds light on this error. You might also try looking up the LMMFIND return code in z/OS ISPF Services Guide . It is also possible there is something wrong with the data set itself. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the error and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS113 LMOPEN failure - LMOPEN of specified data set failed with
return code = aaaaaaaa. ExplanationThis is an internal ISPF processing error. System programmer responseThere may be information in the ISPF log that sheds light on this error. You might also try looking up the LMOPEN return code in z/OS ISPF Services Guide . It is also possible there is something wrong with the data set itself. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the error and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS114 LMCLOSE failure - LMCLOSE of specified data set failed with
return code = aaaaaaaa. ExplanationThis is an internal ISPF processing error. System programmer responseThere may be information in the ISPF log that sheds light on this error. You might also try looking up the LMCLOSE return code in z/OS ISPF Services Guide . It is also possible there is something wrong with the data set itself. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the error and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS115 LMFREE failure - LMFREE of specified data set failed with
return code = aaaaaaaa. ExplanationThis is an internal ISPF processing error. System programmer responseThere may be information in the ISPF log that sheds light on this error. You might also try looking up the LMFREE return code in z/OS ISPF Services Guide . It is also possible there is something wrong with the data set itself. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the error and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS116 LMMREP failure - LMMREP of specified data set failed with
return code = aaaaaaaa. ExplanationThis is an internal ISPF processing error. System programmer responseThere may be information in the ISPF log that sheds light on this error. You might also try looking up the LMMREP return code in z/OS ISPF Services Guide . It is also possible there is something wrong with the data set itself. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the error and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS117 LMMDISP failure - LMMDISP of member list failed with return
code = aaaaaaaa. ExplanationThis is an internal ISPF processing error. System programmer responseThere may be information in the ISPF log that sheds light on this error. You might also try looking up the LMMDISP return code in z/OS ISPF Services Guide. It is also possible there is something wrong with the data set itself. If you are unable to resolve the problem contact IBM support. User responseWrite down the circumstances of the error and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS118 Canceled - Member selection canceled at your request. ExplanationThis message is self explanatory. ISRS119 No members found - No members matched member list pattern
or "new" data set empty. ExplanationNo member selection list was created because no members matched the selection criteria established by the specified pattern. If no pattern was specified, the New data set is empty. User responseModify the pattern to include one or more members of the New data set if you want to select from a list. Blank for member pattern allows you to select from a list of all members. ISRS120 No members selected - End key was pressed with no members
selected. ExplanationThis message is self explanatory. ISRS121 LMMDISP(PUT) failure - Creating the table of member selections
failed. ExplanationThis is an internal ISPF processing error. System programmer responseThere may be information in the ISPF log that sheds light on this error. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the error and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRS122 Browse substituted - Browse has been substituted for View
because View has been disabled via the configuration table. ExplanationThis is an informational message. ISRS123 Invalid profile - Too many options - no room to insert sequence
option. ExplanationThe profile you are using contains so many options that there is no room to add the sequence number option (SEQ, NOSEQ, or COBOL) specified from the panel without exceeding the maximum string size for parameters passed to SuperC. User responseYou, or the creator of the profile, need to modify the profile to remove 1 or possibly 2 process options to free additional space. This may be done by using option 3.13.A ACTIVATE and CREATE functions. Consider specifying the sequence option in the profile so there is no need to override it in option 3.12. ISRS124 ******Search in progress****** ExplanationThis is an informational message. Your input has been validated successfully, and SuperC is invoked to process your search request. ISRS125 GDG-use Other DSN field - GDG data sets are permitted only
in the "Other data set name" field. ExplanationA Generation Data Group data set was entered in the Project-Group-Type fields. This is not supported. User responseUse the Data Set Name field for the GDG and retry. ISRS126 Error browsing listing - aaaaaaaa ExplanationThis is an ISPF internal processing error. System programmer responseThere may be information in the ISPF log data set. Try to browse the list data set outside of SuperC to determine if something is wrong with it. If you cannot resolve the problem, contact IBM support. User responseThis condition may be temporary. Retry. If the error persists, contact your system programmer. It may be helpful to save or print the ISPF log data set when you exit ISPF. ISRS127 Error updating profile - aaaaaaaa ExplanationThis is an ISPF internal processing error. System programmer responseThere may be information in the ISPF log data set. Try to edit and save the profile data set outside of SuperC to determine if something is wrong with it. If you cannot resolve the problem, contact IBM support. User responseThis condition may be temporary. Retry. If the failure persists, contact your system programmer. It may be helpful to save or print the ISPF log data set when you exit ISPF. ISRS128 Not all strings found - Search-for completed with FINDALL
specified and one or more strings not found. See listing for details. ExplanationThe search is complete with not all strings found. There may be further information in the search listing data set, which may be browsed outside of Searchfor. Because you specified FINDALL there may be some strings found, or Input filtering (DPLINE, for example) may have hidden strings that otherwise would be found. User responseIf this result is unexpected, consider editing the statements data set (if one was specified) and investigating the filtering options. Also browse the listing data set. Consider removing FINDALL if you wish the search to be satisfied with some but not all strings found. ISRS129 All strings found - Search-for completed. FINDALL was specified
and all strings were found. ExplanationThis is an informational message. The search was completed successfully with all strings found. Other possible outcomes are not all strings found, no strings searched, or errors. ISRS130 Invalid command - Specify B, P, or E for Batch, Process options,
or Edit statements, or use the Options pulldown. ExplanationThese are the valid fast path commands for additional SuperC functions. ISRS131 SuperC error - SUPERC error, return code = aaaaaaaa.
Enter HELP for more information. ExplanationThis is a warning message. ISRT000 No matching names - There were no data set names matching
the specified pattern (aaaaaaaa). ExplanationThis message is self explanatory. ISRT000A Quotes Required - AUTOTYPE can not process unquoted data
set names when you are running without a TSO prefix. To use AUTOTYPE
without a TSO PREFIX, use fully qualified data set names within single
quotes. ExplanationThis message is self explanatory. ISRT000B Member name not allowed - AUTOTYPE will not retrieve a member
name for this field because this field requires a data set name without
a member name. ExplanationThis message is self explanatory. ISRT000C Internal error - An internal error has occurred because too
many names are being returned by catalog search. This can happen when
a GDG name forms part of the pattern. Retry the AUTOTYPE request with
a different pattern. ExplanationThis message is self explanatory. ISRT001 Retrieved - The name aaaaaaaa was retrieved
using pattern "bbbbbbbb". ExplanationThis message is self explanatory. ISRT002 No more names - There were no additional data set names matching
the specified pattern (aaaaaaaa). ExplanationThis message is self explanatory. ISRT003 Invalid pattern - A pattern is not allowed in the data set
name when a member name or pattern is also present. ExplanationThis message is self explanatory. ISRT004 Authorization error - The data set could not be opened to
scan for members matching your specified pattern. An ABEND 913 occurred. ExplanationThis message is self explanatory. ISRT005 No members match - No member names match your specified pattern.
The data set may not contain members which match the pattern, or
an error occurred reading the directory. ExplanationThis message is self explanatory. ISRT006 Not partitioned - No member name was returned because the
data set is not partitioned. ExplanationThis message is self explanatory. ISRT007 Allocation failed - No member name was returned because the
data set could not be allocated. ExplanationThis message is self explanatory. ISRT008 Invalid Cursor position - The AUTOTYPE function requires
that the cursor be on an enabled library or data set name field.
ISRT009 Open failed - The AUTOTYPE function was not able to open
the data set in order to read the directory. ExplanationThis message is self explanatory. ISRU000 Invalid option - Select one of the listed options. ExplanationNo option was entered on the primary option panel. User responseSelect one of the options available on this panel. ISRU001 Data set not printed - Print control characters exist, press
Help for additional information. ExplanationThe data set being printed contains print control characters. User responseUse the Hardcopy Utility, option 3.6, to print the data set. ISRU002 Prompt not valid - Prompt is entered only for the rename,
move, copy, TSO command, WS command, edit, or view actions. ExplanationA Prompt is only allowed when the option entered supports a prompt. User responseClear the Newname field. ISRU003 Enter new member name - Rename member option specified for
member aaaaaaaa. ExplanationA new member name is required for the Rename option. User responseEnter a new name for the member being renamed. ISRU004 Invalid DSORG - 'aaaaaaaa' organization
must be partitioned. ExplanationThe option or line command selected requires a partitioned data set. User responseEnter a valid command for the data set selected. ISRU005 Invalid DSORG - 'aaaaaaaa' organization
must be partitioned or sequential. ExplanationData set with this DSORG cannot be printed. User responseSpecify a data set to be printed that is partitioned or sequential. ISRU006 Not real data set name - The selected option cannot process
an alias data set name. ExplanationRename and Delete are not allowed for alias names. User responseUse the real name to rename or delete a data set. ISRU007 Enter member name - The selected option requires a member
name. ExplanationCommands B, D, E, P, R, and V are member commands and require a member name. User responseEnter a member name. ISRU008 Pattern/name not allowed - The selected option applies to
the entire data set. ExplanationCommands C, I, L, S, and X apply to the whole data set and a member name is not required. User responseDo not use a pattern or a member name. ISRU009 SYSCTLG not allowed - aaaaaaaa not valid
for the selected option. ExplanationA CVOL catalog is not allowed for the option selected. User responseChange the data set name specified. ISRU010 Invalid data set name - Syntax error in data set name aaaaaaaa. ExplanationA valid TSO data set name qualifier begins with an alphabetic character (A-Z, $, @, or #). The remaining characters must be alphanumeric or a hyphen (-). User responseCorrect the data set name. ISRU011 Request failed - Catalog authorization failed for aaaaaaaa. ExplanationRACF authorization failed for cataloging or uncataloging the data set. User responseIf you need this particular data set cataloged or uncataloged, contact your systems programmer or RACF administrator for assistance. Programmer responseCatalog or uncatalog the data set as requested. ISRU012 Rename failed - Rename return code aaaaaaaa decimal,
status code bbbbbbbb decimal, diagnostic information cccccccc hex. ExplanationThe return code, status code and diagnostic information indicate that one of several errors occurred. For more information, check the DADSM RENAME return, status, and diagnostic information. ISRU013 Data set not on volume - aaaaaaaa not
on volume bbbbbbbb. ExplanationThe data set being renamed does not exist. User responseEnter a data set name that exists. ISRU014 Request failed - Data set is password protected or is of
unsupported organization. ExplanationThis message is self-explanatory. User responseEnter the data set password. ISRU015 New name already on vol - Volume aaaaaaaa contains
data set bbbbbbbb. ExplanationThe data set already exists on the volume. User responseChange the new data set name. ISRU016 Invalid record unit - Average record unit must be 'M', 'K',
'U', or blank. ExplanationWhen selecting space units of records, an allocation unit of M for megabytes, K for kilobytes, or U for bytes must be used. If a blank is entered the default is U for bytes. User responseEnter a valid average record unit. ISRU017 Vol aaaaaaaa not mounted - Contact computer
center if this volume is required. ExplanationThe data set specified is on a volume that is not currently mounted. User responseContact a computer operator to have the volume mounted. ISRU018 Rename data set failed - aaaaaaaa is open,
cannot be renamed. ExplanationThe data set cannot be renamed because it is currently open. User responseRename the data set after it has been closed. ISRU019 aaaaaaaa not allowed - aaaaaaaa only
allowed for first library of concatenation. ExplanationThe member must be in the first library of a concatenation for the Rename, Delete, Reset, Move, TSO Command, and WS command Member options. User responseEnter the library containing the member as the first library in the concatenation. ISRU020 Utility - Delete - 'aaaaaaaa' deleted
from volume bbbbbbbb. ExplanationThis is an informational message. This message is written to the ISPF log data set when a data set is successfully deleted. ISRU021 Data set deleted - 'aaaaaaaa' deleted
from volume bbbbbbbb. ExplanationThis is an informational message. This message is displayed when a data set is successfully deleted. ISRU022 The data set was successfully renamed and cataloged, but
the catalog entry for the old name could not be removed from the catalog.
The uncatalog return code was aaaaaaaa. Enter
the HELP command for further information. ExplanationA data set is renamed in a 3 step process:
PDF successfully cataloged the new data set name and successfully renamed the data set itself, but could not uncatalog the old data set name. The current status of your system: Catalog entries exist for both the old and new names, the data set itself has the new name. System programmer responseRemove the catalog entry. User responseContact your system programmer. ISRU023 Data set renamed - Oldname: 'aaaaaaaa',
newname: 'bbbbbbbb' ExplanationThis is an informational message. This message is displayed when a data set is successfully renamed. The message gives both the old and the new name of the data set. ISRU023A Data set renamed:WARNING - Dataset 'aaaaaaaa'
has been renamed to 'bbbbbbbb' on volume 'cccccccc'
and the catalog option has not been selected. Therefore the catalog
entry for 'aaaaaaaa' has not been deleted or altered. ExplanationThis is an informational message. This message is displayed when a data set is successfully renamed. The message gives both the old and the new name of the data set and volume information for rename of a non-SMS data set. The catalog option has not been used the user is warned that a catalog entry remains. ISRU024 Utility - Rename - Old name: 'aaaaaaaa' ExplanationThis is an informational message. This message is written to the ISPF log data set when a data set is successfully renamed. It contains the old name of the data set. ISRU025 New name: 'aaaaaaaa' ExplanationThis is an informational message. This message is written to the ISPF log data set when a data set is successfully renamed. It contains the new data set name. ISRU026 Member not printed - Unable to use aaaaaaaa ExplanationAn error occurred either allocating, opening, or writing to the SPF list data set. User responseCheck the characteristics of your list data set in using option 0. ISRU027 Member aaaaaaaa bbbbbbbb -
In data set 'cccccccc' ExplanationThis is an informational message. The member or pattern named in the message was Browsed, Printed, Renamed, Deleted, Moved, Copied, Edited, Reset, Viewed, or a command executed as specified. ISRU028 aaaaaaaa bbbbbbbb processed
- In data set 'cccccccc' ExplanationThis is an informational message. ISRU029 Data set deleted - Multivolume data set 'aaaaaaaa'
was deleted ExplanationA multiple volume data was deleted ISRU030 Invalid selection code - Valid codes: P (Print), D (Delete),
R (Rename), B (Browse), E (Edit), V (View), M (Move), C (Copy), G
(Reset), J (Submit), T (TSO Command), W (WS Command), S (Select -
If default select set), O (Open - If ISPF Workplace) or I (Info) ExplanationEither the member list command is not a valid PDF member list command or the command length is too long. User responseCorrect the command. ISRU031 Member not found - aaaaaaaa was not found
in the directory for bbbbbbbb. ExplanationThis message indicates that a member was not found by a BLDL command. The BLDL was issued by a member list command to Print, Rename, or Delete a member. User responseUse member list to determine what members are in the partitioned data set selected. ISRU032 Member not printed - aaaaaaaa invalid
for printing or could not be read. ExplanationThis message is issued as a result of a BLDL for an error other than member not found. This may be the result of an I/O error or a directory error. User responseContact your system programmer. ISRU033 Invalid member name - Member name aaaaaaaa not
valid for partitioned data sets. ExplanationThe new name selected for a Rename operation is not a valid member name. User responseSelect a valid member name. ISRU034 aaaaaaaa already exists - Invalid to rename
member to an existing name. ExplanationThe member name selected for this rename operation already exists in the directory for this data set. User responseSelect another member name for the Rename Member operation. ISRU035 Request failed - STOW aaaaaaaa error with
member bbbbbbbb. ExplanationA stow error occurred while trying to rename a member. The return code indicates an I/O or directory error. User responseContact your system programmer. ISRU036 Request failed - Unable to read member aaaaaaaa directory
entry or data. ExplanationA directory error occurred while trying to read the directory entry for the member named. User responseContact your system programmer. ISRU037 Utility - Rename - aaaaaaaa(bbbbbbbb)
renamed (cccccccc). ExplanationThis is an informational message. This message is recorded in the ISPF log and specifies the member renamed and the new name. ISRU037A Utility - Rename - Alias aaaaaaaa updated
to reference member bbbbbbbb.. ExplanationThis is an informational message. This message is recorded in the ISPF log and specifies the alias member name updated to reference a renamed member. ISRU038 Utility - Delete - aaaaaaaa(bbbbbbbb)
deleted. ExplanationThis is an informational message. This message is recorded in the ISPF log and specifies the member deleted. ISRU038A Utility - Delete - Alias aaaaaaaa deleted. ExplanationThis is an informational message. This message is recorded in the ISPF log and specifies the alias member is also deleted. ISRU038B Utility - Delete - All members deleted from aaaaaaaa.. ExplanationThis is an informational message. This message is recorded in the ISPF log and specifies that all members of the data set were deleted. ISRU039 Conflicting selections - Enhanced member list must be selected
when Display Edit/View panel is selected. ExplanationEnhanced member list must be selected for prompt Edit/View setting. User responseSelect enhanced member lists, or de-select prompt Edit/View settings. ISRU039A Partial list displayed - Referral library list contained
more than 30 data set entries. Only the first 30 entry matches are
shown. ExplanationReferral list DSLIST supports up to 30 data set name/filters. The referral library list contained greater then 30 data set entries. The first 30 entry matches are shown. User responseNone, informational only. ISRU040 Index printed - Index of aaaaaaaa placed
in bbbbbbbb. ExplanationThis is an informational message. ISRU041 Index not printed - Index of aaaaaaaa not
placed in bbbbbbbb. ExplanationError opening temporary data set or error writing line to ISPF list data set. ISRU042 Member is empty - aaaaaaaa contains no
records. ExplanationA PRINT command was issued for an empty member. ISRU043 Data set printed - Listing of aaaaaaaa placed
in bbbbbbbb. ExplanationThis is an informational message. ISRU044 Internal service failed - An internal service failed with
return code = aaaaaaaa decimal, reason code X'bbbbbbbb'.
ISPF may be unable to obtain information about an HFS file because
the HFS is not mounted on the current system or you do not have an
OMVS segment. ExplanationISPF invoked the a macro to retrieve the number of pages allocated, the number of pages used and the number of members for the data set specified. The internal service failed with the return code listed in the message. This message commonly occurs when the HFS is mounted on a different system than the one you are running on or when the user does not have an OMVS segment. System programmer responseDetermine the cause of the problem by referring to the appropriate DFSMS documentation and correct the problem. User responseContact your system programmer. ISRU045 Data set not printed - aaaaaaaa has invalid
RECFM/LRECL, index printed. ExplanationThe record format is spanned, or the LRECL is not between 0 and 300. The index is printed, but the data set could not be printed. User responseTo print the data set, reformat it with an LRECL of 300 or less. ISRU046 Data set not printed - aaaaaaaa is empty,
index printed. ExplanationThis is an informational message. This is an empty sequential data set, or a partitioned data set with no members. The index is printed but the data set is not printed. ISRU047 Data set not printed - aaaaaaaa had a
directory error, index printed. ExplanationAn error occurred while reading the directory or opening a data set. User responseContact your system programmer. ISRU048 Part of data set printed - aaaaaaaa partially
placed in bbbbbbbb. ExplanationThere was an error when printing the data set. Messages are in the list data set. User responseCheck the list data set to determine what the error was. ISRU049 OBTAIN failed - aaaaaaaa has unknown attributes,
OBTAIN RC = bbbbbbbb hex. ExplanationThe DSCBs for this data set could not be read. There is either an error in the VTOC or an I/O error occurred. Information about the data set could not be obtained. User responseContact your system programmer. ISRU050 Utility - Allocate - aaaaaaaa allocated
on volume bbbbbbbb. ExplanationThis is an informational message. This is a message written to the ISPF log data set. ISRU051 Data set allocated - aaaaaaaa allocated
on volume bbbbbbbb. ExplanationThis is an informational message. ISRU052 Print failed - Unable to write to the list data set. The
logical record length of the list data set must be greater than 8. ExplanationThis is an informational message. User responseIncrease the logical record length of the list data set. ISRU053 Invalid record format - The record format value is other
than F, V, U or D. ExplanationEither an invalid record format was entered on the "Allocate New Data Set" panel, or the record format field was left blank and the resulting data set was created with a record format other than F, V, U or D. User responseSpecify the record format you want on the "Allocate New Data Set" panel. ISRU054 Invalid record format - 'aaaaaaaa' conflicts
with another code. ExplanationTwo codes for the same attribute, such as Fixed and Variable, have been entered for the record format. User responseCorrect the record format. ISRU055 Invalid record format - Record format F, V, or U required. ExplanationThe record format must have a type of Fixed, Variable, or Undefined. User responseCorrect the record format. ISRU056 Invalid record length - Record length is inconsistent with
block size for this record format. ExplanationThe record length is greater than the block size or is inconsistent with the block size. For fixed records, the block size should be divisible by the record length. For variable records, the block size should be a multiple of the record length plus 4. User responseCorrect the record length or the block size. ISRU057 Numeric out of range - The number entered must be greater
than or equal to aaaaaaaa.' ExplanationThis message is self explanatory. ISRU058 Rename not allowed - Rename is not allowed for indirectly
cataloged data sets on SYSRES volumes. ExplanationRename of data sets on system residence volumes is not allowed as this might effect IPL. ISRU059 OBTAIN failed - aaaaaaaa has unknown attributes,
OBTAIN RC = bbbbbbbb hex. ExplanationInformation about the source data set could not be obtained in order to create the target data set. User responseIf you were editing a temporary data set and used the CREATE command to create a new data set, you cannot have the data set created using the characteristics of the source data set. ISRU060 Invalid combination - The input and output data sets cannot
be the same if the ISPF IEBCOPY interface is being used. ExplanationThe IEBCOPY interface used by ISPF to copy load modules does not support specifying the same data set as both input and output. User responseIf the function requested is Move, use option 3.1 to rename the member. If the function requested is Copy, the member must first be copied to a second library, then back to the first. ISRU061 Invalid combination - One data set has "undefined" record
format, and the other does not. ExplanationRecord format U data sets can only be moved or copied to another record format U data set. User responseSpecify two format U data sets. ISRU062 Invalid block sizes - "To" block size is less than "from"
block size with record format U. ExplanationFor format U data sets, the block size of the TO data set must be equal to or greater than the block size of the FROM data set. User responseSpecify a TO data set with a block size that is at least as large as the FROM data set. ISRU063 Invalid member name - Member name aaaaaaaa is
not valid. First character must be alpha or national. ExplanationValid member names consist of 1-8 alphanumeric characters (A-Z, #, $, @, 1-9). The first character must be alphabetic. User responseCorrect the member name. ISRU064 Invalid record format - Cannot move or copy record format
U sequential data sets. ExplanationThis is an informational message. Use a partitioned data set to copy format U records. ISRU065 Invalid specification - "From" and "to" data sets cannot
be the same for sequential data sets. ExplanationWhen copying from a sequential data set, a different data set must be the target of the COPY command. User responseSpecify a different data set for the COPY command. ISRU066 Invalid load module - Cannot move or copy "planned overlay"
load modules. ExplanationThis is an informational message. Load modules that were created for planned overlay may not be moved or copied. ISPF does not support moving or copying data with note lists. ISRU067 Invalid specification - "To" member cannot be specified if
"from" member is blank or *. ExplanationWhen a member list is requested, the TO member name should not be specified on the TO panel. The TO member name can be specified in the rename field on the member list. User responseErase the member name on the TO panel. ISRU068 Enter new member name - Member must be renamed when "from"
and "to" data sets are the same. ExplanationWhen copying a member of a PDS to the same PDS, a new member name must be specified. The member cannot be copied to itself. User responseSpecify a new member name. ISRU069 Enter new member name - "From" data set is sequential and
"to" is PDS. Enter "to" member name. ExplanationWhen copying a sequential data set to a PDS, a member name must be specified. User responseSpecify a member name for the TO data set. ISRU070 aaaaaaaa members bbbbbbbb -
to data set cccccccc ExplanationThis is an informational message. ISRU070A aaaaaaaa members bbbbbbbb - cccccccc primary
and dddddddd alias members bbbbbbbb to
data set eeeeeeee ExplanationThis is an informational message. ISRU071 Member aaaaaaaa bbbbbbbb -
to data set cccccccc ExplanationThis is an informational message. ISRU071A Member aaaaaaaa bbbbbbbb -
in data set cccccccc ExplanationThis is an informational message. ISRU071B Member aaaaaaaa bbbbbbbb -
Primary member cccccccc and dddddddd alias
members bbbbbbbb to data set eeeeeeee ExplanationThis is an informational message. ISRU071C Member aaaaaaaa bbbbbbbb -
Primary member cccccccc and dddddddd alias
members bbbbbbbb in data set eeeeeeee ExplanationThis is an informational message. ISRU072 Member aaaaaaaa bbbbbbbb -
to data set cccccccc(dddddddd) ExplanationThis is an informational message. ISRU072A Member aaaaaaaa bbbbbbbb -
in data set cccccccc ExplanationThis is an informational message. ISRU072B Member aaaaaaaa bbbbbbbb -
Primary member cccccccc and dddddddd alias
members bbbbbbbb to data set eeeeeeee.,
member aaaaaaaa renamed to ffffffff ExplanationThis is an informational message. ISRU072C Member aaaaaaaa bbbbbbbb -
Primary member cccccccc and dddddddd alias
members bbbbbbbb in data set eeeeeeee.,
member ffffffff renamed to aaaaaaaa ExplanationThis is an informational message. ISRU073 Data set aaaaaaaa - to data set bbbbbbbb ExplanationThis is an informational message. ISRU074 Data set aaaaaaaa - to data set bbbbbbbb(cccccccc) ExplanationThis is an informational message. ISRU075 Utility - Move/Copy - aaaaaaaa(bbbbbbbb) cccccccc ExplanationThis is an informational message written to ISPF log data set. ISRU076 Utility - Move/Copy - aaaaaaaa bbbbbbbb ExplanationThis is an informational message written to the ISPF log data set. ISRU077 to aaaaaaaa(bbbbbbbb) ExplanationThis is an informational message written to the ISPF log data set. ISRU078 to aaaaaaaa ExplanationThis is an informational message written to the ISPF log data set. ISRU079 Utility - Move/Copy - aaaaaaaa -- bbbbbbbb members cccccccc ExplanationThis is an informational message written to the ISPF log data set. ISRU080 Member not found - Member aaaaaaaa not
found in "from" data set. ExplanationThe member specified was not found in the input data set. User responseSpecify a member of the input data set. ISRU081 I/O error on BLDL - BLDL I/O error - member aaaaaaaa.
Move/Copy completed for bbbbbbbb members. ExplanationThe Move/Copy operation was completed for the number of members specified. An I/O error occurred on the BLDL for the member named. User responseContact your system programmer. ISRU082 I/O error during read - Unable to read member aaaaaaaa.
Move/Copy completed for bbbbbbbb members. ExplanationAn I/O error occurred reading the member named. The Move/Copy operation was completed for the number of members specified. User responseContact your system programmer. ISRU083 I/O error during write - Unable to write member aaaaaaaa.
Move/Copy completed for bbbbbbbb members. ExplanationThis is an informational message. An I/O error occurred while writing the member named. The Move/Copy operation was completed for the number of members specified. ISRU084 No space on directory - Unable to STOW member aaaaaaaa..
Move/Copy completed for bbbbbbbb members. ExplanationThis is an informational message. There is no space in the directory to stow the member named. The Move/Copy operation is complete for the number of members specified. ISRU085 I/O error on STOW - STOW I/O error - member aaaaaaaa.
Move/Copy completed for bbbbbbbb members. ExplanationThere was an I/O error when stowing the member named. The Move/Copy operation is complete for the number of members specified. ISRU086 STOW delete I/O error - Member aaaaaaaa not
deleted in "from" data set. bbbbbbbb members processed. ExplanationThis is an informational message. An I/O error occurred while attempting to delete the member named from the directory. The Move/Copy operation is complete for the number of members specified. ISRU087 STOW delete I/O error - Member aaaaaaaa not
deleted in "from" data set. Member copied, not moved. ExplanationThis is an informational message. The member specified could not be deleted from the directory of the FROM data set. The member has been copied but not deleted. ISRU088 Unable to print - "To" data set not printed, but Move/Copy
was successful. ExplanationThis is an informational message. ISRU089 aaaaaaaa not replaced - Member aaaaaaaa already
exists in the 'to' data set. ExplanationThe member specified already exists and you specified no replace. User responseSpecify a new member name or indicate that the member is to be replaced. ISRU090 Data set not printed - aaaaaaaa is an
empty sequential data set. ExplanationThis message is self explanatory. ISRU091 Enter Batch SYSOUT class - Batch SYSOUT class required for
this print operation. ExplanationThis message is self explanatory. ISRU092 Enter printer id/writer - Printer id or writer-name is required,
they are assigned by your installation. ExplanationThis message is self explanatory. ISRU093 Sent to local printer - aaaaaaaa directed
to local printer bbbbbbbbcccccccc. ExplanationThis is an informational message. The data set name specified was sent to the local printer specified. ISRU094 Utility - Hardcopy - aaaaaaaa directed
to local printer bbbbbbbbcccccccc. ExplanationThis is an informational message. This message is added to the ISPF log data set. ISRU095 Data set not printed. - aaaaaaaa not
printed. See the ISPF Messages and Codes or Help for ISPF Print RC
= bbbbbbbb. ExplanationPossible return codes are:
System programmer responseVerify that the local print function is set up correctly. User responseContact your system programmer. ISRU096 Duplicate specification - Specify Batch SYSOUT class or printer
id or writer-name. ExplanationThis message is self explanatory. ISRU097 Data set not cataloged - aaaaaaaa was
not cataloged on volume bbbbbbbb. ExplanationThis is an informational message. This message is issued when an uncatalog line command is issued against an uncataloged data set. ISRU098 Data set not allocated - NULLFILE is a reserved system name
and cannot be allocated. ExplanationNULLFILE is reserved by the system as a DUMMY data set name. It cannot be used for input or output. User responseSpecify a data set name other than NULLFILE. ISRU099 OBTAIN failed - aaaaaaaa has unknown attributes,
OBTAIN RC = bbbbbbbb hex. ExplanationAn attempt to read information about the data set to be printed was unsuccessful. The return code from the obtain macro is in the message. ISRU100 JCL generated - JCL to print aaaaaaaa bbbbbbbb placed
in cccccccc. ExplanationThis is an informational message. ISRU101 Error generating JCL - JCL to printaaaaaaaa bbbbbbbb not
placed in temp data set. ExplanationThe temporary data set used to build JCL could not be opened or closed. User responseDetermine why a temporary data set cannot be opened or closed. ISRU102 Unexpected return code - Return code "aaaaaaaa"
from the print utility exit. The data is kept. ExplanationThe print utility has returned a return code greater than 4 but not equal to 20. User responseDetermine why the print utility exit returned the return code, correct the problem, and resubmit the job. ISRU103 Job - aaaaaaaa - Printbbbbbbbb cccccccc on
SYSOUT class dddddddd. ExplanationThis is an informational message put in the log data set. ISRU104 "From" data set is empty - LMCOPY or LMMOVE service invoked
for empty "from" data set ExplanationThis is an informational message. ISRU105 Job - aaaaaaaa - Submitted ExplanationThis is an informational message put in the log data set. ISRU106 Cancel - aaaaaaaa - Canceled ExplanationThis is an informational message put in the log data set. ISRU107 Cancel - aaaaaaaa - Canceled because of
error in temp data set. ExplanationThis is an informational message put in the log data set. ISRU108 Sent to TSO/E ICF - aaaaaaaa printed via
TSO/E ICF printer support bbbbbbbb. ExplanationThis is an informational message. ISRU109 Utility - Hardcopy - aaaaaaaa printed
via TSO/E ICF printer support bbbbbbbb. ExplanationThis is an informational message put in the log data set. ISRU110 Invalid specification - "From" and "to" data sets cannot
be the same when all members specified. ExplanationThe TO and FROM data sets must be different if all the members are being copied. User responseChange the TO or FROM data set specification. ISRU111 I/O error on BLDL - I/O error on BLDL for member aaaaaaaa on
"to" data set. ExplanationBLDL macro has failed. Open failed, Obtain failed, or there is insufficient virtual storage for the BLDL. User responseIncrease virtual storage and retry. ISRU112 I/O error on BLDL - BLDL error on member aaaaaaaa on
"to" data set. bbbbbbbb members processed. ExplanationBLDL macro has failed. Open failed, Obtain failed, or there is insufficient virtual storage for the BLDL. User responseIncrease virtual storage and retry. ISRU113 Members not replaced - aaaaaaaa members
not replaced, bbbbbbbb members cccccccc. ExplanationThis is an informational message. User responseDetermine why the members were not replaced and retry. One possible explanation is that another user was accessing the member. ISRU114 to aaaaaaaa bbbbbbbb members
not replaced ExplanationThis is an informational message. User responseDetermine why the members were not replaced and retry. One possible explanation is that another user was accessing the member. ISRU115 aaaaaaaa not replaced - Like-named member
already exists in "to" data set. ExplanationThis is an informational message. ISRU116 I/O error on BLDL - BLDL I/O error member aaaaaaaa on
"to" data set. bbbbbbbb members complete. ExplanationBLDL macro has failed. Open failed, Obtain failed, or there is insufficient virtual storage for the BLDL. User responseIncrease virtual storage and retry. ISRU117 aaaaaaaa not bbbbbbbb -
Cannot find member cccccccc on "to" data set. ExplanationThis is an informational message. ISRU118 aaaaaaaa not bbbbbbbb -
Cannot find member cccccccc on "to" data set. dddddddd members
processed. ExplanationThis is an informational message. ISRU119 I/O error on BLDL - I/O error on BLDL for member aaaaaaaa on
"to" data set. ExplanationBLDL macro has failed. Open failed, Obtain failed, or there was insufficient virtual storage for the BLDL. User responseIncrease virtual storage and retry. ISRU120 aaaaaaaa members reset - Reset statistics
was completed successfully for aaaaaaaa members. ExplanationThis is an informational message. ISRU121 Member aaaaaaaa reset - Reset statistics
was completed successfully. ExplanationThis is an informational message. ISRU122 Member not found - Member aaaaaaaa not
found in data set. ExplanationThis is an informational message. ISRU123 I/O error during search - Directory error - member aaaaaaaa.
Reset completed for bbbbbbbb members. ExplanationBLDL macro has failed. Open failed, Obtain failed, or there is insufficient virtual storage for the BLDL. User responseIncrease virtual storage and retry. ISRU124 No space on directory - Unable to STOW member aaaaaaaa..
Reset completed for bbbbbbbb members. ExplanationStatistics could not be set because there is no space in the directory to store the statistics. User responseEither delete members from the data set to free space in the directory, or reallocate the data set with more directory blocks. ISRU125 I/O error during STOW - Directory error processing member aaaaaaaa,
data set may be out of space or directory blocks. Reset was completed
for bbbbbbbb members. ExplanationThe MVS STOW system macro has failed. System programmer responseThis is likely the result of an MVS system error. Correct the failure and retry. User responseContact your system programmer. ISRU126 I/O error during read - Unable to read member aaaaaaaa.
Reset completed for bbbbbbbb members. ExplanationThe MVS GET system macro has failed. System programmer responseThis is likely the result of an MVS system error. Correct failure and retry. User responseContact your system programmer. ISRU127 Statistics deleted - Delete statistics was completed successfully
for member aaaaaaaa. ExplanationThis is an informational message. ISRU128 Utility - Reset - aaaaaaaa(bbbbbbbb) ExplanationThis is an informational message put in the log data set. ISRU128A Utility - Reset - aaaaaaaa ExplanationThis is an informational message put in the log data set. ISRU129 Utility - Reset - aaaaaaaa ---- All members ExplanationThis is an informational message put in the log data set. ISRU129A Utility - Reset - aaaaaaaa ---- All members ExplanationThis is an informational message put in the log data set. ISRU130 Data set cataloged - 'aaaaaaaa' cataloged
on volume bbbbbbbb. ExplanationThis is an informational message. ISRU131 Utility - Catalog - 'aaaaaaaa' cataloged
on volume bbbbbbbb. ExplanationThis is an informational message. ISRU132 Data set uncataloged - 'aaaaaaaa' uncataloged. ExplanationThis is an informational message. ISRU133 Utility - Uncatalog - 'aaaaaaaa' uncataloged ExplanationThis is an informational message. ISRU134 Catalog unavailable - The volume containing the requested
catalog is not mounted. ExplanationThis message is self-explanatory. System programmer responseMount the volume. User responseHave your system programmer mount the volume. ISRU135 No space in system ctlg - Contact system PGMer, rtn code
= aaaaaaaa, r0 = bbbbbbbb, r1
= cccccccc (dec). ExplanationThere is no space in system volume to process request. User responseGive your system programmer the information in the message. ISRU136 Catalog request failed - Refer to MVS System Message IDC3009I for more information,
Return Code = aaaaaaaa, Reason Code = bbbbbbbb ExplanationA severe error has occurred while processing a catalog request. User responseGive your system programmer the information in the message. ISRU137 Request failed - Catalog return code = aaaaaaaa,
r0 = bbbbbbbb, r1 = cccccccc (dec). ExplanationA severe error has occurred while processing a catalog request. System programmer responseCorrect the catalog problem. User responseGive your system programmer the information in the message. ISRU138 Already cataloged - Entire or partial name cataloged, data
set 'aaaaaaaa'. ExplanationThis is an informational message. ISRU139 Data set not cataloged - 'aaaaaaaa' was
not found in catalog. ExplanationThis is an informational message. ISRU140 Compress successful - Compress listing is in 'aaaaaaaa' ExplanationThis is an informational message. ISRU141 Utility - Compress - 'aaaaaaaa' compressed ExplanationThis is an informational message. ISRU142 Statistics deleted - Delete statistics was completed successfully
for aaaaaaaa members. ExplanationThis is an informational message. ISRU143 Utility - Compress - 'aaaaaaaa' compress
failed, RC = bbbbbbbb hex ExplanationThis is an informational message put in the log data set. ISRU144 aaaa may be incomplete - ISPF does not
support copying aliases members to a PDSE load library. Your target
library is a PDSE load library and one or more of the members you
selected are aliases and have been marked with *ALIAS. These members
were not copied. ExplanationAlias members must be copied using the Binder or regenerated via the Binder. PDF cannot process the alias member. User responseUse the binder to process program object alias members. ISRU145 Incomplete aaaa - ISPF does not support
copying aliases members to a PDSE load library. Your target library
is a PDSE load library and one or more of the members you selected
are aliases. These members were not copied. ExplanationAlias members must be copied using the Binder or regenerated via the Binder. PDF cannot process the alias member. User responseUse the binder to process program object alias members. ISRU146 Member not aaaaa - ISPF does not support
copying aliases members to a PDSE load library. Your target library
is a PDSE load library and the member you selected is an alias. This
member was not copied. ExplanationAlias members must be copied using the Binder or regenerated via the Binder. PDF cannot process the alias member. User responseUse the binder to process program object alias members. ISRU147 Compress failed - Compress listing is in 'aaaaaaaa',
RC = bbbbbbbb hex. ExplanationThe compress has failed for one of these reasons:
ISRU148 Uncatalog failed - The uncatalog request finished with a
return code of 0, but the data set still exists in the catalog. ExplanationThe data set was not uncataloged, probably because is resides on a volume for which a CONVERTV was issued, but not successfully completed. PDF issued the uncatalog request, received a return code zero, but on further inspection discovered that the data set name still existed in the catalog. System programmer responseRefer to the appropriate DFP documentation for assistance in removing the catalog entry. User responseContact your system programmer for assistance in removing the data set from the datalog. ISRU149 Operation not supported - Statistics reset on an alias of
a member of a PDSE is not supported. ExplanationThis message is self explanatory. ISRU150 BLDL error - I/O error, insufficient virtual storage, or
other BLDL error. ExplanationEither there was not enough storage to process BLDL, or another BLDL error has occurred. User responseEither add more virtual storage, or correct the other BLDL error. ISRU151 I/O error during read - Unable to read data. ExplanationThe member is unreadable due to an I/O error. System programmer responseCorrect the I/O error. User responseRetry the operation. If the problem persists, contact your system programmer. ISRU152 Unable to copy data - Data contains user TTR, but is not
a load module. ISPF cannot copy. ExplanationISPF does not support the type of data being copied. User responseUse an alternate copy method, such as IEBCOPY. ISRU153 Print failed - Move/Copy operation encountered an error printing
one or more members. ExplanationThe Move/Copy operation could not print all of the successfully copied members to the print data set. This may be due to an out-of-space condition on the print data set. User responseReallocate the print data set with more space. ISRU154 Members may be copied - Only members from library aaaaaaaa will
be moved, all else will be copied. ExplanationThis is an informational message. ISRU155 Numeric out of range - The number entered is too large or
too small. ExplanationThis is an informational message. ISRU156 Invalid date - The date must be specified as one of the formats
listed. ExplanationThe date has been entered in an unsupported format. User responseEnter the date in a format that is supported. ISRU157 Invalid date - The specified expiration date has passed. ExplanationThe expiration date entered has already passed. User responseEnter a future date. ISRU158 Delete failed - The expiration date for this data set has
not passed. ExplanationThis data cannot be deleted until the expiration date has passed. User responseDelete the data after the expiration date. ISRU159 Invalid field - This field is valid for Copy only. ExplanationThis is an informational message. ISRU160 Invalid selection code - Valid options are: PK or PD. ExplanationOnly PK and PD are valid choices. User responseEnter either PK or PD. ISRU161 Empty member - Member aaaaaaaa is empty. ExplanationThis is an informational message. ISRU162 I/O error - Unable to read member aaaaaaaa. ExplanationThe member is unreadable due to an I/O error. System programmer responseFix the I/O error. User responseContact your system programmer. ISRU163 VSAM data set - VSAM data set organization is not supported
for this function. ExplanationYou cannot use the Rename, Catalog or Uncatalog functions of option 3.2 or option 3.4 against a VSAM data set. User responseUse IDCAMS to process the VSAM data set. ISRU164 Empty data set - Data set aaaaaaaa is
empty. ExplanationThis is an informational message. ISRU165 Invalid DSORG - Data set organization must be partitioned
or sequential. ExplanationThe data set organization must be partitioned or sequential to process the operation you have requested. User responseEnter a valid DSORG and retry the operation. ISRU166 Data set not partitioned - Member aaaaaaaa was
specified for data set bbbbbbbb. ExplanationThe requested operation requires a partitioned data set. User responseEnter a partitioned data set and retry the operation. ISRU167 Data set Open failed - Data set aaaaaaaa could
not be opened to check if member existed. ExplanationThe operation cannot continue because the data set could not be opened. User responseDetermine why Open was unsuccessful, correct the problem, and retry the operation. ISRU168 Member not found - Member aaaaaaaa was
not found in data set bbbbbbbb ExplanationThe member specified on the hardcopy Utility panel does not exist in the data set specified. User responseCorrect the data set and/or member and retry thr print request. ISRU169 Invalid disposition - A member cannot be deleted using this
function. ExplanationThe PD option cannot be used of the data to be printed is a member of a PDS. User responseUse the PK option to print the member. ISRU170 No data set names found - No data set names were found to
satisfy the search argument(s). ExplanationThis is an informational message. ISRU171 No data set names found - No data sets are cataloged that
start with 'aaaaaaaa'. ExplanationThis is an informational message. ISRU172 Dsname level error - Remove the quotes from the Dsname Level. ExplanationThe syntax of the Dsname Level is invalid. Quotation marks are not needed around the Dsname Level. User responseEnter a Dsname Level without quotation marks. ISRU172A Invalid DSN - quotes - Dsname level is missing within the
quotes. Specify a dsname level or remove the quotes to display a list
of personal data set lists. ExplanationThe syntax of the Dsname Level is invalid. A Dsname Level has to be specified within the quotation marks. User responseEnter a Dsname Level within the quotation marks ISRU172B Invalid DSN - quotes - Dsname level is missing within the
quotes. Specify a dsname level or remove the quotes and enter a volume. ExplanationThe syntax of the Dsname Level is invalid. A Dsname Level has to be specified within the quotation marks. Removing the quotes and entering a Volume serial will call up a list of all the data sets on the volume. User responseEnter a Dsname Level within the quotation marks or remove the quotes and enter a volume. ISRU173 Catalog search error - Locate return code for catalog search
was aaaaaaaa decimal. ExplanationA catalog error has occurred during a locate. System programmer responseCorrect the catalog error. User responseContact your system programmer. ISRU174 TBCREATE failure - Creating the table of data set names resulted
in return code aaaaaaaa. ExplanationA return code greater than 4 was received from the TBCREATE service. User responseThe error is probably due to the table being in use by another session. Free the table from that session and retry. ISRU175 Tbadd failure - Return code aaaaaaaa received
adding bbbbbbbb to table. ExplanationA return code greater than 8 was received from the TBADD or TBPUT service. System programmer responseContact IBM support. User responseLog off and retry. If the error recurs, contact your system programmer. ISRU176 Data set list saved - The listing of data sets was placed
in 'aaaaaaaa.' ExplanationThis is an informational message. ISRU177 VTOC information printed - The VTOC information for aaaaaaaa was
placed in the ISPF List data set. ExplanationThis is an informational message. ISRU178 Volume not mounted - Volume aaaaaaaa is
not mounted or is unavailable. ExplanationThe volume you are trying to access is not mounted. System programmer responseMount the volume. User responseContact your system programmer. ISRU179 Enter 2nd operand - A second operand is required for the
LOCATE command. ExplanationThe LOCATE command requires that a search string be entered. User responseReissue the command with a search string. ISRU180 Invalid LOCATE operand - Table is sorted by aaaaaaaa.
Operand is not a valid fixed value. ExplanationAn invalid LOCATE string was entered. User responseEnter a valid search string. ISRU181 LOCATE search error - Return code - aaaaaaaa -
received while searching table. ExplanationA return code greater than 8 was received from the TBSKIP service. System programmer responseContact IBM support. User responseLog off, log back on, and retry. If the error persists, contact the system programmer. ISRU182 Invalid command - The command entered is not valid for the
Data Set List Utility. ExplanationA command was entered that is not supported by the Data Set List. User responseEnter a valid data set list primary command: CONFIRM, FIND, LOCATE, SAVE, SHOWCMD, or SORT. ISRU183 TBDISPL error - Return code - aaaaaaaa -
received when displaying table. ExplanationThis message is self explanatory. ISRU184 Invalid selection code - 'aaaaaaaa' is
not a valid selection. ExplanationThis message is self explanatory. ISRU185 Incomplete string - Put a quote to indicate the end of the
string. ExplanationA quote was found to indicate the argument of the FIND command is a literal string, but no ending quote was found to mark the end of the string. User responseCorrect the FIND command string and retry. ISRU186 Invalid date - Specify a date in the format YYYY/MM/DD. ExplanationWhen the data set list is sorted by one of the date fields, the argument of the LOCATE command must be a valid date. User responseCorrect the invalid date format as instructed and retry the LOCATE command. ISRU187 Enter required field - Dsname level and/or volume must be
specified. ExplanationEither dsname level, volume or both must be specified when requesting a data set list. User responseSpecify a Dsname Level, a Volume serial, or both to indicate which data sets are to be included in the list. Entering a Volume serial with a blank Dsname level will call up a list of all the data sets on the volume. ISRU188 Duplicate data set name - Data set is cataloged on a volume
other than aaaaaaaa. ExplanationAn SMS data set with the same name is cataloged on another volume. Any attempt to allocate the uncataloged version of the data set will result in the SMS version of the data set being allocated. ISRU189 Edit not allowed - Edit recovery is pending, but not allowed
from this option. ExplanationThis message is self explanatory. ISRU190 aaaaaaaa VTOC printed - VTOC listing of
volume aaaaaaaa placed in bbbbbbbb. ExplanationThis is an informational message. ISRU191 VTOC listing not printed - VTOC listing of volume aaaaaaaa not
printed. Error in listing data set. ExplanationThis message is self explanatory. ISRU192 VTOC list not displayed - VTOC listing of volume aaaaaaaa not
displayed. Error in temp data set. ExplanationThis message is self explanatory. ISRU193 Vol aaaaaaaa not mounted - Volume must
be mounted to list the VTOC. ExplanationThe volume you are trying to get a VTOC list from is not mounted. System programmer responseMount the volume. User responseContact your system programmer. ISRU194 Compress not allowed - The specified library is a PDSE and
cannot be compressed. ExplanationThis is an informational message. ISRU195 VTOC error - OBTAIN return code = 'aaaaaaaa'. ExplanationAn error was encountered reading a format 4 DSCB. Problem determinationSee the appropriate DFP/DFSMS documentation for return code descriptions. ISRU196 Free space error - LSPACE return code = 'aaaaaaaa'
decimal. ExplanationAn error occurred when issuing the LSPACE macro to obtain VTOC free space information. Problem determinationSee the appropriate DFP/DFSMS documentation for return code descriptions. ISRU197 VTOC error - CVAF macro (SVC139) return code = 'aaaaaaaa'. ExplanationAn error occurred when issuing a CVAF macro to obtain VTOC or data set information. Problem determinationSee the appropriate dfSMS documentation for return code descriptions. ISRU198 Invalid order code - Valid codes are: A or P. ExplanationThis message is self explanatory. User responseEnter either A or P. ISRU199 Invalid record format - A record format of U is not valid
when creating a PDSE. ExplanationA record format of U is not supported when creating a PDSE. User responseEither enter a supported record format for a PDSE, or allocate as a PDS. ISRU200 Rename failed - RACF RC=8
for rename of aaaaaaaa. ExplanationRACF has returned a return code of 8 on a data set rename. User responseCheck your RACF authorization. Programmer responseCheck the RACF authorization for the data set. ISRU201 GDG base - There are no valid built-in selections for a GDG
base ExplanationAn attempt to use built-in functions on a GDG BASE is causing this error message. GDG Base entries are only entries in the catalog. System programmer responseVerify the user's action on the GDG Base to see what action the user was attempting. User responseContact your system programmer. ISRU202 Bad directory - Directory block size exceeds maximum of 256. ExplanationThis message is self explanatory. ISRU203 No member allowed - No member name or pattern allowed for
this built-in command. ExplanationA data set member name or pattern has been entered for a built-in command that does not support a data set member name or pattern. User responseRemove the data set member name or pattern, or check to see which built-in commands are valid for the data set member or pattern. ISRU204 Invalid line command - Valid line commands are B, D, E, P,
R, or a TSO command/CLIST. ExplanationAn invalid line command has been entered. User responseEnter one of these valid line commands: B, D, E, P, R, or a TSO command/CLIST. ISRU204A Block command invalid - An uneven number of block commands
was entered. ExplanationBlock commands can only be entered in pairs. Type a // at the start of a block of rows and another // at the end of the block of rows. Type the line command immeditately following the // either at the end or the beginning of the block. e.g. //e User responseMake sure that all block commands (//) are entered in pairs. ISRU204B Block command invalid - Line command missing. Specify a line
command immediately following the // either at the beginning or end
of the block. ExplanationType a // at the start of a block of rows and another // at the end of the block of rows. Type the line command immeditately following the // either at the end or the beginning of the block. e.g. //e User responseMake sure that a line command is specified either at the beginning or end of the block of rows. ISRU204C Block command invalid - Mismatching line commands specified.
A different line command was specified at the beginning and end of
the block. Block commands can not be nested. ExplanationType the line command immeditately following the // either at the end or the beginning of the block. e.g. //e Block commands can not be nested. User responseIf a line command is specified at the beginning and end of the block command, it has to be the same line command. ISRU204D Command conflict - A line command is within the range of
a block command. Correct the conflicting command. ExplanationLine commands can not be interleaved with block commands. Correct the conflicting command. Only one command can be applied to a dataset at any one time. User responseRemove the conflicting command. ISRU204E Block command invalid - A block command was entered on an
excluded line. Only NX/NXL/NXF commands are allowed on excluded lines.
To execute block commands for excluded lines, make sure the option
"Execute Block Commands for excluded Data Sets", is selected and the
excluded lines are in between the start and end of the block command. ExplanationBlock commands are only valid on unexcluded lines. To execute block commands for excluded lines, make sure the option "Execute Block Commands for excluded Data Sets", is selected and the excluded lines are in between the start and end of the block command. User responseMove the block command to an unexcluded line. ISRU205 Invalid data set name - Enter a quoted, fully qualified data
set name. ExplanationThe data set name is incorrect. User responseCorrect the data set name. ISRU206 Extraneous parameters - Extraneous parameters for built-in
command. ExplanationAn extraneous parameter has been entered for a built-in command. User responseRemove the extraneous parameter and reenter the built-in command. ISRU207 Invalid change - Data set name may not be changed for built-in
commands. ExplanationThe data set name cannot be changed for the built-in command. User responseDo not change the data set name for the built-in command. ISRU208 Command failed - Command 'aaaaaaaa' not
found, invalid, or issued return code 20. ExplanationThe command that was issued did not process. Either the command was not found, the command was invalid, or the command issued a return code of 20. User responseReenter a valid command. ISRU209 Command failed - Command 'aaaaaaaa' issued
return code bbbbbbbb. ExplanationThe command failed with the issued return code. User responseReenter a valid command. ISRU210 Data set is unmovable - Data set organization of "from" data
set indicates it is unmovable. ExplanationThe organization of the data set indicates that the data set cannot be moved. System programmer responseContact IBM support. User responseVerify that the data set organization indicates that it cannot be moved. Contact your system programmer. ISRU211 Invalid option specified - Select option 1 or 2. ExplanationThis message is self explanatory. ISRU212 No members in data set - The PDS specified contains no members. ExplanationThe specified partitioned data set contains no members. User responseVerify that this is the correct data set for the member you are trying to locate. Problem determinationThere are no members in the PDS. ISRU213 Severe error - Open, I/O, or BLDL error. ExplanationA severe error has occurred. Either an OPEN, I/O, or BLDL error has occurred on the data set. System programmer responseCheck the status of the data set that has caused this error. User responseContact the system programmer. ISRU214 Option not implemented - Try another option. ExplanationThe option entered is not available. User responseTry another option. ISRU215 No space in directory - PDS directory is full, allocate more
directory blocks. ExplanationThere is no more directory space for the partitioned data set. User responseThe PDS is out of directory space. More directory space needs to be allocated. Programmer responseAllocate more directory space. ISRU216 I/O error during STOW - Permanent I/O error occurred updating
directory block. ExplanationAn I/O error occurred during an attempt to update the directory block. System programmer responsePerform diagnostics on the data set that has failed. User responseContact your system programmer. ISRU217 Invalid select code - Type S for select or B for browse in
front of the member desired. ExplanationAn invalid selection code has been entered. Valid selections are S for Select or B for Browse. User responseEnter one of the valid selection codes. ISRU218 I/O error during read - Unable to read data. ExplanationAn I/O error occurred during READ. The data cannot be read. System programmer responsePerform diagnostics on the data set causing the error. User responseContact your system programmer. ISRU219 BLDL error - I/O error, insufficient virtual storage, or
other BLDL error. ExplanationA BLDL error occurred on the data set. System programmer responsePerform diagnostics on the data set causing the error. User responseContact your system programmer. ISRU220 Allocation failed - Allocation of print data set failed. ExplanationThe allocation of the Print temporary data set has failed. System programmer responseFind out why the temporary data set was not allocated. Make sure that the packs that the user has access to are not full and that a data set by the same name does not already exist. User responseContact your system programmer. Problem determinationThe data set that the output was allocated to may be full. ISRU221 No data to browse - Output command did not place any data
in print data set. ExplanationThis is an informational message. There is no data to browse in the print data set. ISRU222 No data to print - Output command did not place any data
in print data set. ExplanationThis is an informational message. There is no data in the data set to print. The output command did not place any data into the print data set. ISRU223 Utility - Outlist - Requeue issued job aaaaaaaa. ExplanationThis is an informational message. The OUTPUT command to requeue the requested job has been issued. ISRU224 Utility - Outlist - Delete issued job aaaaaaaa. ExplanationThis is an informational message. The job log has been deleted. ISRU225 Requeue issued - Output requeue attempted for job aaaaaaaa. ExplanationThis is an informational message. An attempt to requeue the job listed will be made. ISRU226 Delete issued - Output delete attempted for job aaaaaaaa. ExplanationThis is an informational message. An attempt to delete the job listed will be made. ISRU227 Print completed - Print function has completed ExplanationThis is an informational message. The requested print function has ended. ISRU228 Invalid class - Class must be alphanumeric (A-Z, 0-9). ExplanationThis is an informational message. An invalid class has been entered. The class must be either A-Z or 0-9. ISRU229 Member not found - Member "aaaaaaaa" not
found, only library 1 searched for MOVE service. ExplanationThe member was not found in the specified library. Only one library was entered. User responseCheck the data set concatenation to determine where the member is located. Programmer responseOnly one library member was entered. ISRU230 Vol serial not allowed - A volume serial is not allowed for
this operation. ExplanationThe volume serial is not allowed for this operation on an SMS managed data set that is accessed using a non-VTOC data set list. User responseAccess the data set using the data set list, and rerun the command. Problem determinationA command has been issued against an SMS data set that is not allowed. The data set was accessed using a non-VTOC data set list. ISRU231 Record size too small - These sizes are allowed: RECFM=F
10-32760, RECFM=V 14-32752. ExplanationThe logical record length is too small. The LRECL must be greater than or equal to 10 for fixed records and greater than or equal to 14 for variable records. User responseReblock the data set record size. Problem determinationCheck the data set LRECL. ISRU232 Vol serial not allowed - Use "Other data set name" field
when specifying volume serial. ExplanationThe Other Data Set Name field is used when the volume serial is specified. User responseEnter the Other Data Set Name. ISRU233 Invalid unit - Generic unit must be blank if volume serial
is specified. ExplanationGeneric Unit must be left blank when the volume serial is specified. User responseLeave Generic Unit blank. ISRU234 Insufficient storage - Not enough storage is available for
Browse to proceed. ExplanationThis message is self explanatory. ISRU235 Invalid required parm - Select the required parameter from
the options shown. ExplanationEnter one of the valid options listed to complete the command. User responseEnter a listed valid option. ISRU236 I/O error during write - Unable to write data. ExplanationAn error has occurred while writing data to a data set member. System programmer responseVerify that the failing data set is not corrupted and that the DASD is available. User responseCheck the data set to see if the data set is corrupted, and that the DASD is available. ISRU237 Enter member name - The specified data set is partitioned.
A member name is required. ExplanationThe data set that is specified is a partitioned data set. A partitioned data set requires a member name to continue. User responseEnter a member name. ISRU238 Option not implemented - Try another option. ExplanationThe requested option not available. User responseEnter an available option. ISRU239 Enter required field - User ID and/or new version number
must be specified with R option. ExplanationThe R option must be used with the user ID or NEW VERSION number or both. User responseUse the R option. ISRU240 Invalid SORT operand - 'aaaaaaaa' is not
a valid SORT operand. ExplanationAn invalid SORT operand has been entered. User responseCorrect the SORT operand and retry the command. Problem determinationVerify the sort operand. ISRU241 Too many sort fields - You may specify up to two fields for
use with the SORT command. ExplanationToo many SORT operands have been entered for the SORT command. A maximum of two operands can be entered per SORT command. User responseCorrect the number of SORT operands. ISRU242 SORT error - Error returned from table sort = aaaaaaaa. ExplanationThis message is self explanatory. Problem determinationA table sort error has occurred on an internal sort routine. ISRU243 Invalid operand - Valid CONFIRM operands are ON and OFF. ExplanationAn invalid CONFIRM operand was entered. The valid operands are ON and OFF. User responseUse a valid CONFIRM operand, either ON or OFF. ISRU244 Data set saved - The data set was saved. ExplanationThis is an informational message. ISRU245 Invalid command - Only ISPF system commands may be entered
on this panel. ExplanationAn invalid command was entered on the command line. User responseSpecify a valid command. Enter HELP when this message is displayed for command information. ISRU246 Invalid for load - Info is not valid for members of a load
module data set. ExplanationAn invalid command was entered on the command line. ISRU247 This list of data set names contains entries from a CVOL
catalog. The list exceeded the maximum number of names allowed in
the input area and may be incomplete. ExplanationA data set list did not build completely using the qualifiers entered. System programmer responseVerify that all DASD is operational and that valid qualifiers are being used. User responseVerify the qualifiers, then consult your system programmer. ISRU248 Incomplete list printed - The list of data set names exceeded
the allocated input area. ExplanationAn incomplete data set list was printed. User responseVerify the data set qualifiers. ISRU249 Error during list print - An error was encountered trying
to put list into the ISPF List data set. ExplanationAn error occurred while attempting to print to the ISPF list data set. User responseVerify that the ISPF list data set is available and is large enough to retain your data. Problem determinationCheck the ISPF list data set attributes. ISRU250 Four char. year invalid - The MVS system
must be MVS/XA, level MVS/SP 2.2.0 or higher. ExplanationThis MVS system is not a level that will support the 4 character year that has been entered. User responseEnter a valid date that is supported by this MVS system. ISRU251 Value too large - The maximum retention period allowed is
9999. ExplanationThe retention period that has been entered is greater than 9999. A retention period value must be less than or equal to 9999 days. User responseEnter a value for the retention period less than or equal to 9999 days. ISRU252 Invalid date - The date specified contains invalid values. ExplanationThe date that has been entered into the expiration date field has invalid values. These values could be an invalid day or month, or a character entered into the day, month, or year field. User responseCorrect the incorrect value that has been entered for the day, month, or year. ISRU253 Date not allowed - The date specified is only valid with
4 character year support. ExplanationThe date that was entered in Julian format is not supported on the level of MVS that is on your system. User responseCorrect the Julian date, or enter the date in character form using a 2 character year. ISRU254 Compress successful - The data set was successfully compressed
by the compress exit. ExplanationThis is an informational message. The data set that the compress was requested for has completed successfully. ISRU255 Compress failed - The compress done by the compress exit
failed. ExplanationThis message is self explanatory. ISRU256 Severe error - A severe error was returned by ISPF compress. ExplanationISPF ran a compress on a data set and a return code that was greater than or equal to 20 was returned. User responseSee what data set the compress was done against and check the data set characteristics to see if there is any problem with the data set. ISRU257 Data set not partitioned - The data set for compress must
be partitioned. ExplanationThe data set that the compress was issued against is not a partitioned data set, so the compress cannot be executed. To do a compress, the data set must be partitioned. User responseDo not compress data sets that are not partitioned. ISRU258 Member aaaaaaaa saved - bbbbbbbb was
edited and saved. ExplanationThis is an informational message. The data set listed was saved. ISRU259 Data set not deleted - Delete request for "aaaaaaaa"
was canceled by user. ExplanationThis is an informational message. The data set was not deleted. The confirmation of the data set delete was canceled. ISRU260 No information - Member has no statistics or directory entry
is not a valid ISPF directory. No further information is available. ExplanationThis message is self explanatory. ISRU261 Invalid operand - Valid SHOWCMD operands are ON and OFF. ExplanationAn invalid operand has been entered with the SHOWCMD command. Valid operands are ON and OFF. User responseEnter the SHOWCMD command with an ON or OFF operand. ISRU262 Panel not found - The specified data set list panel could
not be found. ExplanationThe data set list panel requested could not be found. System programmer responseCheck to see that the specified data set list panel exists and can be displayed. User responseContact your system programmer. ISRU263 Table processing error - An error occurred during control
table processing. ExplanationThere is a problem in creating the table needed to store the program state. System programmer responseCheck to see why the requested table was not created. User responseContact your system programmer. ISRU264 No previous command - The '=' command cannot be used until
a line command has been entered. ExplanationA previous line command has not been issued so the "=" command cannot be used. User responseEnter the line command you were attempting to retrieve. ISRU265 Data set does not exist - 'aaaaaaaa' was
deleted or uncataloged. ExplanationThe data set requested is not cataloged, not uncataloged, not a GDG, or on a tape. It does not exist. User responseCheck to see if the data set has been removed from the system. ISRU266 Member too long - A member name/pattern must be 8 or less
characters in length. ExplanationThe member name is greater than 8 characters. User responseEnter a valid member name or pattern that is 8 characters or fewer. ISRU267 Data set not found - "aaaaaaaa" not found
on volume bbbbbbbb. ExplanationThe requested data set is not on the specified volume. User responseEither enter the correct volume for the data set, or enter just the data set name. ISRU268 Command too long - Command expansion caused the command to
exceed 255 characters. ExplanationThe command that was entered exceeds the maximum length of 255 characters. User responseReenter the command with fewer than 255 characters. ISRU269 Invalid DSORG - Data set organization must be either partitioned
or sequential. ExplanationThis is an informational message. The data set organization is invalid. In order to execute a FREE command, the data set organization must be partitioned or sequential. ISRU270 Utility - Move/Copy - aaaaaaaa bbbbbbbb ExplanationThis is an informational message written to the ISPF log data set. ISRU271 to aaaaaaaa ExplanationThis is an informational message written to the ISPF log data set. ISRU272 UCBSCAN failure - The UCBSCAN service experienced a system
failure. ExplanationAn unexpected system failure occurred while requesting volume information. System programmer responsePossible causes for this failure are listed in the return code section for the UCBSCAN macro in the MVS Assembler Services Reference manual. User responseRetry the volume list, then consult your system programmer. ISRU273 Delete confirmation on - A confirmation panel will be displayed
for data set deletion requests. ExplanationThis is an informational message. Confirmation has been set to ON for data set deletion requests. A confirmation panel will be displayed for deletion requests unless confirmation is set to OFF. ISRU274 Delete confirmation off - Data set deletion requests will
not be confirmed. ExplanationThis is an informational message. Confirmation has been set to OFF for data set deletion request. A confirmation panel will not be displayed for a deletion request. Set Confirm ON to display the delete confirmation panel. ISRU275 Commands will be shown - Line commands will be displayed
before being processed. ExplanationThis is an informational message. SHOWCMD is set to ON so line commands will be displayed before being processed. Set SHOWCMD to OFF to if you do not want to see the line commands before they are processed. ISRU276 SHOWCMD off - Line commands will be processed immediately. ExplanationThis is an informational message. SHOWCMD is turned OFF so line commands will not be displayed before being processed. Issue the SHOWCMD ON command if you want to see line commands before they are processed. ISRU277 Numeric out of range - Partitioned data sets cannot have
a primary quantity of 0. ExplanationA value of 0 was entered into the Primary Quantity field, but the Primary Quantity field of a partitioned data set cannot be set to 0. User responseEnter a value greater than 0 in the Primary Quantity field. ISRU278 Numeric out of range - Primary quantity cannot be 0 when
secondary quantity is also 0. ExplanationThe Primary Quantity field and the Secondary Quantity field are both set to 0. The Primary Quantity field cannot be 0 if the Secondary Quantity field is 0. User responseChange either the Primary Quantity or the Secondary Quantity field to a value greater than 0. The Primary Quantity field cannot be set to 0 for a partitioned data set. ISRU279 Invalid combination - Partitioned data sets require a value >0
for directory blocks. ExplanationA value of 0 was entered for the number of directory blocks for a partitioned data set. User responseEnter a value greater than 0 for the number of directory blocks. ISRU280 Recovery processed - Pending recovery processed, canceled,
or deferred. ExplanationThis is an informational message. The pending error recovery has been processed. ISRU281 Job - aaaaaaaa - Submitted ExplanationThis is an informational message. The job has been submitted for processing. ISRU282 Listing deleted - aaaaaaaa has been deleted. ExplanationThis is an informational message. The listing file is deleted. ISRU283 Listing kept - aaaaaaaa has been kept. ExplanationThis is an informational message. The listing file is being kept. ISRU284 aaaaaaaa will be printed and bbbbbbbb by
job - cccccccc. ExplanationThis is an informational message. The listing file is being printed, and will be deleted when the print function is finished. ISRU285 Data set not opened - aaaaaaaa is a compressed
data set that has not been opened. The primary allocation is shown
in tracks. ExplanationThe data set that you have requested information on is a compressed data set that has not been opened. ISPF does not know the blocksize that will be used by DFSMS and therefore shows the primary quantity in tracks. ISRU286 Utility - Com print - SUBMIT failed - aaaaaaaa has
been kept ExplanationThe job that was submitted has not processed, but the list file will be kept. User responseCheck the job to determine what caused the error. ISRU287 Utility - Com print - aaaaaaaa directed
to local printer bbbbbbbb and cccccccc ExplanationThis is an informational message. The list file is directed to the specified local printer ID or writer. ISRU288 SMS not active - SMS is not active. Enhanced data set allocation
is unavailable. ExplanationSMS is not active on your MVS system. User responseUse the A fastpath command, or the space pull-down to allocate the data set as a non-SMS data set. Programmer responseInformational ISRU289 20 or more volumes - The information displayed is for the
first 20 volumes of this data set. If there are more than 20 volumes,
the information may be incorrect.
ISRU290 Data set not printed. - aaaaaaaa has
been kept. See the ISPF Messages and Codes or Help for Local Print
RC = bbbbbbbb. ExplanationThe attempt to print the data set on a local printer
was unsuccessful. The listing data set will be kept. Possible return
codes are:
System programmer responseVerify that the local print function is set up correctly. User responseContact your system programmer. ISRU291 Job skeleton not found - Job card skeleton "ISRSCHPJ" was
not found. ExplanationThe job card skeleton, ISRSCHPJ, cannot be found. System programmer responseVerify that you have the PDF skeletons in your system concatenations. User responseContact your system programmer. Problem determinationThe ISPF/PDF skeletons are not in your system concatenations. ISRU292 Enter option - Enter one of the listed options. ExplanationOne of the highlighted options displayed on this panel should be entered. User responseEnter one of the highlighted options. ISRU293 Data set not printed - An uncataloged data set cannot be
printed using option 3.6 with a print mode of LOCAL if there exists
a cataloged data set by the same name. ExplanationThe hardcopy utility cannot process an uncataloged data set if a cataloged data set by the same name exists on the system. User responseUse another method to print the data set. ISRU294 Unexpected return code - Return code "aaaaaaaa"
from the print utility exit. The listing is kept. ExplanationAn unexpected return code was received while attempting to exit from the print utility. The listing data set will be kept. System programmer responseCheck the print utility exit. User responseContact your system programmer. ISRU295 TSO/E ICF not installed - The TSO/E information center facility
(TSO/E ICF) is not installed. ExplanationThe TSO/E Information Center Facility is not installed on your system. System programmer responseVerify that the Information Center Facility (TSO/E ICF) is installed. User responseContact your system programmer. ISRU296 Print utility exit - The print utility exit produced a return
code of aaaaaaaa. ExplanationThis is an informational message. The print utility exit produced a return code that was received on the print utility exit. ISRU296A Data set disp modified - The print utility exit changed the
data set disposition. ExplanationThis is an informational message. The print utility exit has changed the variable which controls whether the data set is kept or deleted. ISRU297 Submit error - An error occurred while submitting JCL generated
by the print utility exit. ExplanationAn error occurred when the JCL generated by the print utility exit was submitted. User responseCheck the JCL for the error. ISRU298 Utility - TSO/E ICF - aaaaaaaa printed
by TSO/E ICF and bbbbbbbb. ExplanationThis is an informational message. The TSO/E Information Center Facility print was invoked to print the list file. ISRU299 Data set not renamed - The data set rename request was canceled
by the user ExplanationThis is an informational message. ISRU300 Job skeleton not found - Job card skeleton ISRCHCJB was not
found. ExplanationThis message is self explanatory. ISRU301 List data set not found - List data set aaa(44) cannot
be found. ExplanationThe list data set specified for printing (aaa(44)) does not exist; therefore, it cannot be printed. User responseRegenerate the listing and resubmit the print job. ISRU302 Exit submitted JCL - JCL generated by the print
exit was submitted. ExplanationThis is an informational message. The print utility exit successfully generated the JCL for the requested print operation. ISRU303 TSO/E ICF CLIST error - CLIST ICQCPC00 error. Contact your
system programmer. ExplanationThe CLIST used for processing ICF print requests (ICQCPC00) returned an error. System programmer responseRefer to the ICF documentation for problem determination. User responseContact your system programmer. ISRU304 TSO/E ICF msg not found - TSO/E ICF message variable not
found. Contact your system programmer. ExplanationTSO/E ICF encountered an error while processing the specified print request, but no message was found in ICF dialog variable QCPMSGID. System programmer responseRefer to the ICF documentation for problem determination. User responseContact your system programmer. ISRU305 Data set not deleted - Data set does not exist or not sufficient
authority ExplanationPDF received a return code 8 from the SCRATCH macro, indicating that the data set to be deleted either does not exist, or you do not have sufficient RACF authority to delete the data set. User responseVerify that the data set exists. If it does not, it has already been deleted and no further action is needed. If the data set does exist, you do not have sufficient RACF authority to delete it. In this case, either have the data set deleted by someone that does have sufficient RACF authority, or contact your RACF administrator to have your authority level changed. ISRU306 RECFM not supported - Standard records are not supported
for the FREE command. ExplanationThe PDF FREE command (the F line command from an option 3.4 data set list) is not supported for Fixed Standard record formats. User responseFind an alternate way to free the space in the data set. ISRU307 Rename failed. The data set could not be renamed, but the
catalog entry for the new name could not be removed from the catalog.
The uncatalog return code was aaaaaaaa. Enter
the Help command for further information. ExplanationWhen PDF renames a data set, a 3 step process is followed:
PDF successfully cataloged the new data set name, but could not rename the data set from the old name to the new name. PDF then attempted to uncatalog the new data set name to restore the system to its original state, but the uncatalog failed as well. Currently, catalog entries exist for both the old and new names, and the data set itself has the old name. System programmer responseRemove the catalog entry. User responseContact your system programmer. ISRU308 Data set not deleted - Data set was copied, but was not deleted
due to insufficient authority. ExplanationYou requested that the Move/Copy utility move a sequential data set. This involves 2 steps:
PDF was unable to delete the data set because you do not have sufficient access authority to request the delete. User responseHave your system programmer either grant you authority to delete the data set, or delete the data set for you. ISRU309 List records truncated - The records written to the ISPF
list data set by the data set list utility have a logical record length
of 121. To avoid truncation, use the ISPF parms option, list data
set characteristics, to change the record length to 121 or greater
for RECFM F or 125 or greater for RECFM V. ExplanationThis message is self explanatory. ISRU310 ------ I/O error on BLDL - BLDL I/O error - member aaaaaaaa.
Convert completed for bbbb members. ExplanationThis message is self explanatory. User responseContact your system programmer. ISRU311 -- I/O error during read - Unable to read member aaaaaaaa.
Convert completed for bbbb members. ExplanationThis message is self explanatory. User responseContact your system programmer. ISRU312 - I/O error during write - Unable to write member aaaaaaaa.
Convert completed for bbbb members. ExplanationThis message is self explanatory. User responseContact your system programmer. ISRU313 -- No space on directory - Unable to STOW member aaaaaaaa.
Convert completed for bbbb members. ExplanationThis message is self explanatory. User responseExpand the directory block size of the data set, and retry the request. ISRU314 ------ I/O error on STOW - STOW I/O error - member aaaaaaaa.
Convert completed for bbbb members. ExplanationThis message is self explanatory. User responseContact your system programmer. ISRU315 Convert - Menus/Msgs - aaa(44)(bbbbbbbb) cccccccc ExplanationThis message is self explanatory. ISRU316 Convert - Menus/Msgs - aaa(44) bbbbbbbb ExplanationThis message is self explanatory. ISRU317 to aaa(44)(bbbbbbbb) ExplanationThis message is self explanatory. ISRU318 to aaa(44) ExplanationThis message is self explanatory. ISRU319 Severe error in exit - Severe error in user exit. Compress
aborted. ExplanationAn unexpected return code was received from the compress exit, indicating a severe error has occurred. PDF will abort the compress request. System programmer responseRefer to ISPF Planning and Customizing for a discussion of the return codes expected from the compress exit, then modify the exit to return an appropriate return code. User responseContact the responsible programmer. ISRU320 Function not available - Requested function not provided.
Convert routine not available. ExplanationThis message is self explanatory. User responseContact your system programmer. ISRU321 aaaaaaaa not converted - Convert routine
returned with error indication. Member not converted. ExplanationThis message is self explanatory. User responseConvert the member by hand. ISRU322 Reset failed - Reset will not resequence packed data. ExplanationThe PDF reset utility cannot resequence data that is in packed format. User responseUse the edit RENUM command to resequence the data. ISRU323 ESTAE macro error - ESTAE macro failed with return code - aaaa ExplanationThe PDF Move/Copy processor (ISRUMCS) received a nonzero return code from the ESTAE macro. System programmer responseConsult the appropriate MVS documentation for problem determination. User responseContact your system programmer. ISRU324 System abend 'aaaa' - A system abend occurred.
Press Help key for further information. ExplanationThe PDF Move/Copy routine (ISRUMCS) received an abend aaaa when processing your request. System programmer responseConsult the appropriate MVS documentation for problem determination. User responseContact your system programmer. ISRU325 Reset failed - Member aaaaaaaa has packed
data. Reset completed for bbbb members. ExplanationThe PDF reset utility cannot process members that contain packed data; PDF will abort the reset request. bbbb members were successfully processed before the error was encountered. User responseIf the members need to be processed, use the PDF editor to unpack them. ISRU326 Insufficient work space - Work area exceeded. Press Help
key for additional information. ExplanationThis message is self explanatory. ISRU327 GETMAIN failed - Cannot GETMAIN enough work area to proceed. ExplanationPDF could not obtain the minimum size (64K) it needs to process a Data Set List utility request. User responseTry doing one of these:
ISRU328 GETMAIN failed - Unable to issue GETMAIN. ExplanationPDF received a return code greater than 4 from the GETMAIN macro while attempting to obtain a work area to process your Data Set List utility request. System programmer responseConsult the appropriate MVS documentation for problem determination. User responseContact your system programmer. ISRU329 Cannot pack data - ISPF will not pack data for RECFM=U. ExplanationISPF and PDF do not support packed data for record format U data sets. Only record formats F and V are supported. User responseEither move the data to a record format F/V data set and pack it, or leave the data unpacked. ISRU330 Invalid record format - S is not valid if data set organization
is partitioned. ExplanationPartitioned data sets with Fixed Standard or Variable Spanned record formats are not supported. User responseChoose another record format and retry the function. ISRU331 Invalid record format - U is not valid with B or S. ExplanationUndefined format records cannot be Blocked, Standard, or Spanned. User responseChoose another record format and retry the function. ISRU332 Numeric out of range - Record length of zero is valid only
if record format is U. ExplanationWhen allocating a data set using Fixed or Variable format records, a nonzero record length is required. A zero record length is only valid for Undefined format records. User responseSpecify a nonzero record length, or use record format U. ISRU333 aaaaaaaa - bbbbbbbb ExplanationThis message is self explanatory. ISRU334 Invalid disposition - Packing data is invalid if DISP=MOD
is specified. ExplanationWhen copying to a sequential data set with disposition MOD (which appends the copied data to the existing data in the data set), the data being copied cannot be packed. If the data being copied is packed, data will be created that ISPF cannot process. User responseEither use a disposition of OLD, or specify a pack option of NO to have ISPF unpack the data before writing it to the target data set. ISRU335 aaaaaaaa failed - Specifying DISP=MOD
is invalid if "to" data set has packed data. ExplanationWhen copying to a sequential data set that already contains packed data, you cannot specify a disposition of MOD (which appends the copied data to the existing data in the data set) because data will be created that ISPF cannot process. User responseEither use a disposition of OLD, or unpack the target sequential data set before attempting the COPY command. ISRU336 Unable to read data set - An error was encountered while
reading the "to" data set. ExplanationWhen copying to a sequential data set using a disposition of MOD, ISPF reads the first record of the target sequential to determine whether or not the data set contains packed data. An I/O error was encountered while attempting to read that first record. User responseContact your system programmer. ISRU337 Invalid combination - Copy request incomplete due to invalid
pack combination. When copying to a sequential data set with disposition
of mod and pack option of asis, you cannot copy both packed and unpacked
data, nor can you copy multiple packed members. aaaa members
were successfully copied during this operation. ExplanationOne of the two following conditions occurred during
an attempt to copy multiple members of a PDS (or concatenation of
PDSs) to a sequential data set, using a disposition of MOD:
Either of these cases results in data that cannot be processed by ISPF. User responseTo copy multiple PDS members to a sequential data with a disposition of MOD, all PDS members must either be unpacked or copied with a pack option of NO. In addition, the target sequential data set must either be empty or contain unpacked data. ISRU338 Invalid member name - The member name is invalid for a partitioned
data set. ExplanationA member name containing invalid characters was specified for processing. User responseCorrect the member name. A valid member name must be 1-8 characters in length, start with an alphabetic or special character, and contain only alphabetic, numeric, and special characters. ISRU339 "From" data set empty - Empty "from" PDS member or sequential
data set has been requested. ExplanationA request was made to copy from a PDS member or sequential data set that does not contain any data. User responseSpecify a member or data set that contains data. ISRU340 Error during list print - An error was encountered trying
to put list into 'aaa(44).' ExplanationISPF encountered an internal table services error while processing the SAVE command. System programmer responseContact IBM support. User responseContact your system programmer. ISRU341 List not printed - The list data set for the option 3.4 SAVE
command must be a sequential data set with logical record length greater
than or equal to 140 for RECFM F and greater than or equal to 144
for RECFM V. ExplanationThe option 3.4 SAVE command was issued, specifying a list-id to have the data set list information written to a data set named userid.list-id.DATASETS. If this data set already exists, it must be a sequential data set with logical record length greater than or equal to 140 for RECFM F and greater than or equal to 144 for RECFM V. User responseUse a different list-id to have ISPF write the data set list information to another data set, or delete and reallocate the existing data set to have the proper characteristics. ISRU342 Data set list printed - The listing of data sets was placed
in the ISPF list data set. ExplanationThis is an informational message. The option 3.4 SAVE command was successfully processed and the requested information has been written to the ISPF list data set. ISRU342A The listing of data sets was placed in the ISPF list data
set. Lines have been wrapped because the logical record length is
less than 121 for RECFM F or 125 for RECFM V. ExplanationThis is an informational message. The option 3.4 SAVE command was successfully processed and the requested information has been written to the ISPF list data set but has been wrapped. System programmer responseIncrease the value of the LIST_LOGICAL_RECORD_LENGTH configuration table keyword. User responseUse option 0 - List data set characteristics - to increase the logical record length. ISRU343 Invalid list-id - "aaaaaaaa" contains
invalid characters. ExplanationThe option 3.4 SAVE command was invoked with a list-id parameter, indicating that the data set list information should be written to a data set. The list-id parameter, used as the middle qualifier of the data set, did not conform to ISPF naming conventions. User responseCorrect the specified parameter and reenter the command. The parameter specified must be 1-8 characters in length; start with an alphabetic character, or @, #, or $; and all remaining characters must be alphabetic, numeric, or @, #, $, or X'CO'(right brace). ISRU344 List-id too long - The list-id must be less than or equal
to 8 characters in length. ExplanationThe option 3.4 SAVE command was invoked with a list-id parameter, indicating that the data set list information should be written to a data set. The list-id parameter, used as the middle qualifier of the data set, did not conform to ISPF naming conventions. User responseCorrect the specified parameter and reenter the command. The parameter specified must be 1-8 characters in length; start with an alphabetic character, @, #, or $; and all remaining characters must be alphabetic, numeric, @, #, $, or X'CO'(right brace). ISRU345 Free failed - aaaa failed for data set
'bbb(44)'. ExplanationISPF could not free the unused space for data set bbb(44) due to a failure in either the OPEN or RDJFCB macro (as indicated by aaaa). System programmer responseFollow normal problem determination procedures. User responseContact your system programmer. ISRU346 Utility - free - Any unused space freed for data set 'aaa(44)'. ExplanationThis is an informational message. The ISPF data set list FREE command has been completed successfully. ISRU347 Free completed - Any unused space freed for data set 'aaa(44)'.
Enter HELP for further information on when space may not be freed
from the data set. ExplanationThis is an informational message. The ISPF data set list FREE command has been completed successfully. ISRU347A Free completed for PDSE - Space freed past the last block
used for PDSE 'aaa(44)'. Enter HELP for further
information on when space may not be freed from the data set. Refer
to topic "Allocating Space for a PDSE" in the "DFSMS/MVS Using Data
Sets" as a guide to PDSE space usage. ExplanationThis is an informational message. The ISPF data set list FREE command has been completed successfully. ISRU348 Internal program error - ESTAE failed during initialization
in module ISRUAF. ExplanationISPF encountered an error from the ESTAE macro while processing the data set list FREE command. System programmer responseContact IBM support. User responseContact your system programmer. ISRU349 Free failed with abend - Abend code of 'aaaa'
during open. See system message for details. ExplanationISPF encountered an abend while processing the data set FREE command. System programmer responseContact IBM support. User responseContact your system programmer. ISRU350 Member not found - Member was not found in the from data
set(s). ExplanationThis message is self explanatory. ISRU351 Request failed - Unable to read member aaaaaaaa directory
entry or data. ExplanationThis message is self explanatory. ISRU352 aaaaaaaa issued - aaaaaaaa issued
for bbb(44) ExplanationThis is an informational message. The deletion of a migrated data set was requested. ISPF has issued the command specified in the configuration table to be used for deleting migrated data sets (aaaaaaaa). ISRU353 "From" data set in use - "From" data set is being updated
by you or another user. ExplanationA Move, Copy, Copy/Lock, or Promote request was issued, but the data set specified as the source of the operation is currently in use by you or another user. User responseIdentify the person using the data set and request that they release it, or try again later. ISRU354 "To" data set in use - "To" data set is being updated by
you or another user. ExplanationA Move, Copy, Copy/Lock, or Promote request was issued, but the data set specified as the target of the operation is currently in use by you or another user. User responseIdentify the person using the data set and request that they release it, or try again later. ISRU355 "From" member in use - "From" member is being updated by
you or another user. ExplanationA Move, Copy, Copy/Lock, or Promote request was issued, but one or more of the members specified as the source of the operation are currently in use by you or another user. User responseIdentify the person(s) using the member(s) and request that they release them, or try again later. ISRU356 "To" member in use - "To" member is being updated by you
or another user. ExplanationA Move, Copy, Copy/Lock, or Promote request was issued, but one or more of the members specified as the target of the operation are currently in use by you or another user. User responseIdentify the person(s) using the member(s) and request that they release them, or try again later. ISRU357 Data set not deleted - The data set was copied successfully
but could not be deleted, possibly due to an authorization failure. ExplanationThis message is self explanatory. ISRU358 aaaaaaaa failed - "From" record length
is greater than "to" block size for record format U. ExplanationWhen copying or moving members between 2 record format U libraries, the block size of the target library must be equal to or greater than that of the source data set. User responseReallocate the target library so that it has an appropriate block size, or copy the member to a different library. ISRU359 Incomplete list - Insufficient work space. Press Help key
for additional information. ExplanationThe work area required to process the current data set list request exceeds the area currently available. User responseTry doing one of these:
ISRU360 SCLM warning - The project being updated is an SCLM controlled
project. ExplanationThis is an informational message. ISPF has identified the data set you are processing as a possible SCLM-controlled library. If the library is indeed SCLM-controlled and you continue with the request, you will invalidate the SCLM accounting information stored in its VSAM database. This will not result in a loss of data, but will require you to use either the SCLM Migrate utility (option 10.3.3) or SCLM Edit (option 10.2) to correct the accounting information before building or promoting the member. ISRU361 No changes made - No updates have been made to the member
statistics. ExplanationThis is an informational message. The user responded that no updates should be done after being prompted with a warning that the library being processed may be an SCLM-controlled data set. ISRU362 Duplicate data set - Requested data set was allocated and
found to be cataloged on a volume other than aaaaaa.
The subsequent attempt to free the data set failed with SVC 99 error
code bbbb, information code cccc. ExplanationThe user specified a data set and volume combination, but SVC 99 allocated a data set by the same name on a different volume. This usually indicates that a data set with the same name as the data set requested by the user exists on an SMS controlled disk. To protect data set integrity, ISPF will not allow the request to be completed. However, when attempting to free the incorrect allocation, an SVC 99 error was encountered. SVC 99 returned an error code of bbbb, information code of cccc. User responseContact your system programmer. ISRU363 Recursion error - ISPF recursion error invoking the compress
function. ExplanationISPF does not support the recursive invocation
of functions that use file tailoring. An attempt was made to invoke
the ISPF compress function while another file tailoring function is
already active on a previous command nesting level. The other file
tailoring functions monitored for recursion are:
User responseComplete the previously nested file tailoring function, then retry the compress request. ISRU364 Unsupported data type - One or more PDSE load module libraries
have been detected in the input to the Move/Copy utility, the LMCOPY
service, or the LMMOVE service. Data sets of this type are not currently
supported by these ISPF functions. Press Help for more information. ExplanationThis message is self explanatory. ISRU365 Unsupported data type - aaaaaaaa is a
PDSE load module library. Data sets of this type are not supported
for the Move/Copy utility, LMCOPY service or LMMOVE service. ExplanationThis message is self explanatory. ISRU366 Delete not supported - "aaaaaaaa" is an
uncataloged SMS data set. The delete command is not supported for
an uncataloged SMS data set. ExplanationSMS data sets should always be cataloged. The scratch macro does not support uncataloged SMS data sets. User responseContact your system programmer. ISRU367 CAMLST Locate Error - The CAMLST locate for one or more data
sets returned by Catalog failed. The data set(s) are included in
the list with the volume left blank. ExplanationA catalog error occurred during a CAMLST locate. The data set name is listed without a volume. One reason for the failure may be an indirect volser being offline. User responseContact your system programmer. ISRU368 Catalog error - SVC 26 CAMLST locate RC = aaaaaaaa dec.,
reason code bbbbbbbb dec. ExplanationA catalog error occurred during a CAMLST locate. The return code and reason code are specified in the message. System message IDC3009I documents return and reason codes for the CAMLST macro. User responseContact your system programmer. ISRU369 Select options - Select the options needed for processing. ExplanationInformational message for SuperC and Search-For issued from the ISPF Workplace ISRU370 aaaa failed - aaaa failed
for member bbbbbbbb.. Failure in IEWBIND cccccccc,
return code dddd reason code eeee. ExplanationWhen processing a Move/Copy request for load data on a DFSMS 1.1 or later system, ISPF invokes the binder to do the actual copy. ISPF encountered an error during the cccccccc phase of the binder invocation. The following flow describes the binder calls made during a Move/Copy operation:
User responseRefer to the appropriate DFSMS documentation for an explanation of the return code and reason code from the binder, and follow the recommended diagnostic steps to correct the problem. ISRU371 Invalid input data - You cannot concatenate load and non-load
data sets for Move/Copy. ExplanationMove/Copy does not support concatenating load and non-load data sets as input. A load data set is defined
by ISPF as:
All other data is considered non-load. User responseCorrect the input data sets to specify either all load data, or all non-load data. ISRU372 Input/output mismatch - The input and output data sets for
Move/Copy must either be all load data sets, or all non-load data
sets. ExplanationThe user specified input and output data sets that do not agree. If the input is a load data setm the output must be as well. If the input is a non-load data set, the output must also be a non-load data set. A load data set is defined by
ISPF as:
All other data is considered non-load. User responseCorrect the input and output data sets to specify either all load data, or all non-load data. ISRU373 Incomplete aaaaaaaa - One or more aliases
were not bbbbbbbb to the output data set because
members by those names already existed in the target data set and
"Replace like-named members" was not selected.
ISRU374 Must be numeric. - The number of volumes must be a number
in the range of 1-20.
ISRU375 Dsname/volume modified. - The Data Set List Filter exit
generated a return code of 4 indicating that the Dsname Level and/or
the Volume Serial was modified. ExplanationThe Data Set List Filter exit specified in the ISPF Configuration Table returned a 4, indicating that it had modified either the Dsname Level or Volume Serial specified. The data set list presented was built using the modified data. ISRU376 List not displayed. - The Data Set List Filter exit generated
a return code other than 0 or 4 resulting in the data set list not
being displayed. ExplanationThe Data Set List Filter exit specified in the ISPF Configuration Table returned a code other than 0 or 4. This causes ISPF to stop building the data set list and redisplay the Data Set List Utility panel. ISRU377 Partial list displayed. - The Data Set List Filter exit
generated a return code of 4 for one or more data set names resulting
in the display of a partial data set list. ExplanationThe Data Set List Filter exit specified in the ISPF Configuration Table returned a code of 4 for one or more data sets. These data sets are not added to the list. ISRU378 Empty list. - The Data Set List Filter exit generated a
return code of 4 for all data set names, resulting in an empty data
set list. ExplanationThe Data Set List Filter exit specified in the ISPF Configuration Table returned a code of 4 for all of the data sets matching the Dsname Level and/or Volume Serial specified, resulting in no list to display. ISRU379 List terminated. - The Data Set List Filter exit generated
a return code other than 0 or 4, resulting in termination of the list
build process. ExplanationThe Data Set List Filter exit specified in the ISPF Configuration Table returned a code other than 0 or 4 for one of the data sets. This causes ISPF to stop building the data set list and to display the list as it currently exists. ISRU400 TBSKIP failure - Return code aaaa received
from TBSKIP command. ExplanationThe data set list processor encountered an internal error while invoking the TBSKIP service. System programmer responseContact IBM support. User responseContact your system programmer. ISRU401 TBPUT failure - Return code aaaa received
adding to data set name table. ExplanationThis message is self explanatory. ISRU402 TBTOP failure - Return code aaaa received
from TBTOP command. ExplanationThe data set list processor encountered an internal error while invoking the TBTOP service. System programmer responseContact IBM support. User responseContact your system programmer. ISRU403 TBEND failure - Attempted to free data set name table. Return
code=aaaa. ExplanationThe data set list processor encountered an internal error while invoking the TBEND service. System programmer responseContact IBM support. User responseContact your system programmer. ISRU404 No data set names found. There is a possibility of matching
entries that did not fit in the maximum allowed input area for CVOL
catalogs. ExplanationA data set list request was issued that required ISPF to search a CVOL catalog. Due to interface restrictions, ISPF may not be able to retrieve all the data sets in the CVOL. ISPF searched through the data sets that were retrieved, but found no data sets matching the dsname level specified. User responseISPF retrieves data sets by passing any fully specified qualifiers to the system to retrieve a set of data sets. It then scans this set for data sets matching any partial qualifiers that were specified. Passing a more specific name will cause the system to retrieve a smaller initial set of data sets, increasing the likelihood that all possible data sets will be scanned. For example, specify SYS1.XYZ.* instead of SYS1.XYZ*. This causes the system to retrieve only those data sets starting with SYS1.XYZ, rather than all data sets starting with SYS1. ISRU405 Uncatalog failed - The uncatalog request finished with a
return code of 0, but the data set still exists in the catalog. ExplanationA request was issued to uncatalog a data set that is SMS managed. PDF could not determine that the data set was SMS controlled, so the uncatalog request was issued. A return code 0 was received form the uncatalog, but upon further checking is was determined that the data set was still listed in the catalog. ISRU406 No aaaaaaaa bbb(44) found
- aaaaaaaa bbb(44) - not found
in any non X'ed data set names. ExplanationThis is an informational message. A FIND or RFIND command was entered to cause the data set li processor to search the entire data set list for the specified target string. The search was completed, but the target string was not found. ISRU407 No aaaaaaaa bbb(44) found
- aaaaaaaa bbb(44) - not found
in any data set names. ExplanationThis is an informational message. A FIND or RFIND command was entered to cause the data set list processor to search the entire data set list for the specified target string. The search was completed, but the target string was not found. ISRU408 Delete volume required. - The name of the volume that contains
the entry to be deleted is required for a DELETE NVR or DELETE VVR. ExplanationThe DELETE NVR or DELETE VVR function requires the name of the volume that contains the entry (NVR or VVR) to be deleted. User responseEnter the name of volume that contains the entry (NVR or VVR) to be deleted. Programmer responseNone. ISRU409 Volume not allowed. - Delete volume is allowed only for
DELETE NVR or DELETE VVR. ExplanationThe delete volume is used only for the DELETE NVR or DELETE VVR functions. It is not allowed for any other VSAM DELETE function. User responseBlank the delete volume field. Programmer responseNone. ISRU410 Enter character string - Enter the string of characters to
be found. ExplanationThe FIND command was entered on an option 3.4 data set list, but no parameter was specified to indicate what the search target was. User responseSpecify a target string on the FIND command. ISRU411 Invalid keyword - Check spelling of keywords used with the
FIND command. ExplanationThe FIND command was entered, passing a quoted string as the target string to find, but an additional parameter was specified that was not recognized at a valid FIND keyword. Valid keywords are: ALL, FIRST, LAST, NEXT, PREV, CHARS, PREFIX, SUFFIX, and WORD. User responseCorrect the specified keyword and retry the command. ISRU412 Put string in quotes - Put quotes (' ') around the string
of characters to be found. ExplanationThe FIND command was entered, passing multiple words as parameters that were not recognized as valid keywords. It is assumed that the words were intended to be an argument to the FIND command and, if so, must be enclosed in quotation marks. User responseAdd quotation marks around the string and retry the command. ISRU413 Invalid keyword - The keywords 'aaaaaaaa'
and 'bbbbbbbb' cannot both be used. Delete one. ExplanationThe FIND command was entered, passing conflicting
keywords. Only one of these keywords may be specified. Two types
of keywords are supported by the FIND command: direction keywords
and type keywords. No more than one of each type of keyword may be
specified on the FIND command. The keywords are:
The defaults are NEXT and CHARS User responseCorrect the keywords specified and retry the command. ISRU414 Enter character string - A character string for FIND has
not been entered (so * is invalid). ExplanationAn asterisk (*) used as the target string of the FIND command indicates that the previous target string should be reused. An asterisk was entered but no previously entered a valid target string was found, making the use of the asterisk invalid. User responseEnter a valid target string. Once a target string is entered, the asterisk may then be used on subsequent FIND commands. ISRU415 FIND string too long - The FIND string cannot be longer than
44 characters. ExplanationThe FIND command searches for the specified target string within the list of data set names. Since the maximum length of a data set in the list is 44 characters, the target string may not exceed 44 characters. User responseRetry the command, entering a target string that is equal to or less than 44 characters in length. ISRU416 Invalid character string - The FIND string cannot be a null
('') string. ExplanationThe FIND target string must be a minimum of 1 character in length. A target string of 0 characters was entered. User responseRetry the command, entering a target string that is equal to or greater than 1 character in length. ISRU417 Enter a FIND command - The RFIND key works only after a FIND
character string is entered. ExplanationThe RFIND command reissues the last FIND command that was entered. RFIND cannot be issued until at least one FIND command has been processed. User responseEnter a valid FIND command. Once entered, the RFIND command may be used to reissue the same FIND command. ISRU418 aaaa - bbbbbbbb ccc(44) - bbbbbbbb ccc(44) found
on aaaa line(s) ExplanationThis is an informational message. A FIND ALL command was entered on a data set list, and the specified target string was successfully located. ISRU419 aaaaaaaa bbb(44) found
- Search for aaaaaaaa bbb(44) was
successful. ExplanationThis is an informational message. A FIND command was entered on a data set list, and the string was successfully located. ISRU420 *Bottom of list reached* - aaaaaaaa bbb(44) not
found. Press the RFIND key to continue the search from the top for
the data set list. ExplanationThis is an informational message. The data set list FIND command searches from the top of the displayed data to the bottom of the list to find the target string. FIND has searched and reached the bottom of that list without finding the target string. Entering the RFIND command continues the search, starting from the top of the data set list. ISRU421 * Top of list reached * - aaaaaaaa bbb(44) not
found. Press the RFIND key to continue the search from the bottom
for the data set list. ExplanationThis is an informational message. When the PREV keyword is specified, the data set list FIND command searches from the top of the displayed data to the top of the list to find the target string. FIND has searched and reached the top of that list without finding the target string. Entering the RFIND command continues the search, starting from the bottom of the data set list. ISRU422 No aaaaaaaa bbb(44) found
- aaaaaaaa bbb(44) - not found
in any X'ed data set names. ExplanationThis is an informational message. A FIND or RFIND command was entered to cause the data set list processor to search the entire data set list for the specified target string. The search was completed, but the target string was not found. ISRU423 Invalid string type - Data set list FIND command does not
process picture (P'...'), hex (X'...'), text (T'...') or char (C'...')
strings. ExplanationThe data set list FIND command does not support
all of the keywords supported by the editor FIND command. These are
not supported:
All FIND commands are treated as text strings (T'...'), meaning that strings are matched regardless of case. User responseRemove the unsupported keyword and reenter the command. ISRU424 Data set list saved - The listing of data sets was placed
in the ISPF list data set. ExplanationThis is an informational message. The data set list SAVE command was entered without any parameters, indicating that the data set list information should be written to the ISPF list data set. The information has been successfully written. ISRU424A The listing of data sets was placed in the ISPF list data
set. Lines have been wrapped because the logical record length is
less than 121 for RECFM F or 125 for RECFM V. ExplanationThis is an informational message. The data set list SAVE command was entered without any parameters, indicating that the data set list information should be written to the ISPF list data set. The information has been successfully written but has been wrapped. System programmer responseIncrease the value of the LIST_LOGICAL_RECORD_LENGTH configuration table keyword. User responseUse option 0 - List data set characteristics - to increase the logical record length. ISRU425 Invalid line command - The data set list line command exit
has restricted the entered command. ExplanationThis is an informational message. A data set list line command exit is specified in the configuration table you are currently using. This exit has returned a return code indicating that the command entered is a restricted command and should not be executed. ISRU426 Severe error occurred - The data set list line command exit
issued a return code of 20. ExplanationA data set list line command exit is specified in the configuration table you are currently using. This exit has returned a return code of 20, indicating a severe error has been encountered. User responseContact the author of the exit for help in determining the cause of the error. ISRU427 Unknown return code - The data set list line command exit
issued a return code of aaaa. ExplanationA data set list line command exit is specified in the configuration table you are currently using. This exit has returned an unsupported return code of aaaa. Supported return codes from the exit are 0, 4, 8, and 20. User responseContact the author of the exit for help in determining the cause of the unsupported return code. ISRU428 LOCATE failed - The LOCATE for 'aaa(44)'
failed, RC = bbbb. ExplanationThe data set list processor issued a LOCATE macro to gather information on data set aaa(44), but the LOCATE failed with a return code of bbbb. User responseContact your system programmer. ISRU429 Incomplete VTOC list - Index entry not included because VTOC
entry does not exist. ExplanationAn entry was found in the VTOC index but the entry did not point to an actual DSCB, indicating that the data set does not actually exist on the volume. The name in the index has not been added to the data set list. System programmer responseCorrect the VTOC index. User responseContact your system programmer. ISRU430 Severe error - Severe error occurred in subsystem request
services. ExplanationISPF invoked the IEFSSREQ macro to determine whether the SMS subsystem is active on your system. The macro returned a return code of either 16 or 20, indicating that a severe error was encountered. User responseContact your system programmer. ISRU431 Invalid space units - Must be TRKS, BLKS, CYLS, KB, MB, BYTES
or RECORDS. ExplanationWhen creating a data set under ISPF option 3.2, the space to be allocated must be specified as Tracks, Blocks, Cylinders, Kilobytes, Megabytes, Bytes or Records. An unsupported value was entered. User responseCorrect the value for space units and retry the request. ISRU432 Invalid request - Managed data sets cannot be cataloged. ExplanationData sets managed by the SMS subsystem cannot be cataloged or uncataloged. User responseVerify that the data set name entered is correct. If not, correct it and retry the request. ISRU433 Invalid request - Managed data sets cannot be uncataloged. ExplanationData sets managed by the SMS subsystem cannot be cataloged or uncataloged. User responseVerify that the data set name entered is correct. If not, correct it and retry the request. ISRU434 VSAM data set alloc. - VSAM data set successfully allocated. ExplanationThis is an informational message. You requested that a VSAM data set be created by ISPF, and the data set was successfully created. ISRU435 Request failed - Allocation/deallocation request failed.
Press Help for more information. ExplanationISPF received an unexpected error from SVC 99 while trying to allocate or deallocate a data set. Any error messages generated by the system should have been written to the screen as TSO line messages. User responseIf you did not see any messages, use the TSO PROFILE WTPMSG command to ensure your ID is set up to receive "write to programmer" messages, then retry the request. Once you get the messages, follow normal debugging steps for those messages. ISRU436 Invalid DSN type - Enter LIBRARY for a PDSE, PDS for a PDS,
LARGE for large sequential or blank ExplanationThe only supported values for the Data Set Name
Type field are:
User responseCorrect the Data Set Name Type field and retry the command. ISRU437 Not all members aaaaaaaa - bbbb members
not aaaaaaaa, cccc members aaaaaaaa. ExplanationThis is an informational message. The Move/Copy request is completed, but not all the members were successfully processed. cccc indicates the number of members successfully processed, bbbb indicates the number of members that could not be processed. aaaaaaaa indicates whether this was a Move or Copy request. ISRU438 Action not selected - Select an action or remove default
(/). ExplanationThis message is self explanatory. ISRU439 Invalid DSN type - Enter LIBRARY for a PDSE, PDS for a pds,
HFS for hfs, LARGE for large sequential, EXTREQ for Extended Required,
EXTPREF for Extended Preferred or a blank. ExplanationThe only supported values for the Data Set Name
Type field are:
User responseCorrect the Data Set Name Type field and retry the command. ISRU440 VSAM Utility - Delete - An IDCAMS delete command has completed
with an RC=0. ExplanationThis is an informational message. ISRU441 IDCAMS delete completed - An IDCAMS delete command has completed
with an RC=0. ExplanationThis is an informational message. ISRU442 Enter a decimal percentage between 0 and 100. ExplanationThe CI-percent and CA-percent values must be a valid percentage between 0 and 100. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU443 Enter a decimal value between 1 and 32768. ExplanationThe control interval size must be a decimal number between 1 and 32768. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU444 Enter numeric characters (0-9). ExplanationThis message is self explanatory. ISRU445 Enter 1, 2, 3, or 4. ExplanationValid share options are 1, 2, 3 or 4 for Region, 3 or 4 for System. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU446 Enter decimal number between 1 and 16776704. ExplanationThe buffer space value must be a decimal number between 1 and 16776704. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU447 Enter a number between 3 and 255. ExplanationThe BUFND and BUFNI values must be a decimal number between 3 and 255. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU448 Enter a number between 2 and 255. ExplanationThe STRNO value must be a decimal number between 2 and 255. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU449 Enter one to six characters, beginning with a letter. ExplanationThis message is self explanatory. ISRU450 Enter one to eight characters. ExplanationThis message is self explanatory. ISRU451 Enter one to eight characters. ExplanationThis message is self explanatory. ISRU452 Enter one to eight characters. ExplanationThis message is self explanatory. ISRU453 Enter one to eight characters. ExplanationThis message is self explanatory. ISRU454 Enter one to eight characters. ExplanationThis message is self explanatory. ISRU455 Command canceled - Profile command has been canceled. ExplanationThis is an informational message. Changes made to the name of the profile data set have not been made because the CANCEL command was performed. ISRU456 Invalid Extended Attr - Enter NO or OPT or leave blank ExplanationThe only supported values for Extended Attribute
field:
User responseCorrect the Extended Attribute field and retry the command. ISRU457 Enter a number 1 to 9999. ExplanationThe file sequence field values must be a number between 1 and 9999. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU458 Member not found - The member you are trying to get does
not exist. ExplanationThe member cannot be retrieved because it does not exist. User responseEnter a member that exists, or enter a GET command with no parameters and a list of existing members will be displayed. ISRU459 List action de-selected - You have erased a list action.
Any actions on any other lists are ignored. ExplanationAn invalid list action was de-selected and an action was requested against a different list entry. Only one list may be processed at a time. System action/* OW14268 - ISPF V4.2 development APAR */ User responseSelect a new list action or enter a list action to perform. ISRU460 Data ignored - Erroneous data has been ignored. ExplanationThis is an informational message. There are more parameters entered than the command requires. The extra parameters will be ignored. ISRU461 Severe error - A severe error has occurred saving profile
member. ExplanationThe profile member could not be saved due to a system error. The most probable error is that the profile data set is full or has run out of directory blocks. User responseReallocate the profile data set with more space or directory blocks. ISRU462 Type mismatch - The request type of the member you are trying
to get does not match the request type being defined. ExplanationYou cannot get a member if the data in the member does not match the request being created. For example, if you are defining a cluster, the member you are getting must have been saved from a previous cluster define. ISRU463 Profile read error - A failure has occurred reading profile
member. ExplanationA LMGET call for data in the profile data set has failed. System programmer responseContact IBM support. User responseContact your system programmer. ISRU464 Allocate error - Unable to allocate the profile data set:
The data set must be a variable partitioned data set with an LRECL
of 203. ExplanationThe profile data set must be a variable partitioned data set with an LRECL of 203. User responseEnter an unallocated data set (PDF will allocate the data set) as the profile data set, or allocate a profile data set with the correct allocations. ISRU465 Enter a numeric value between '0' and '16777215'. ExplanationThe primary and secondary quantity values must between 1 and 16777215. ISRU466 Data saved - Data has been saved to profile. ExplanationThis is an informational message. ISRU467 Get error - There are no members in the profile data set
to get. ExplanationThis is an informational message. ISRU468 Enter a decimal percentage between 0 and 100. ExplanationThe values for the CI-percent and CA-percent must be a decimal percentage between 0 and 100. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU469 Enter a decimal value between 1 and 32768. ExplanationThe value for control interval size must be a decimal number between 1 and 32768. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU470 Enter numeric characters (0-9). ExplanationThis message is self explanatory. ISRU471 Enter 1, 2, 3, or 4. ExplanationValid Share Options for Region are 1, 2, 3 or 4. Refer to the appropriate IDCAMS documentation for specific information on this options. ISRU472 Enter 3 or 4 ExplanationValid Share Options for System are 3 or 4. Refer to the appropriate IDCAMS documentation for specific information on this options. ISRU473 Enter between 1 and 9999 days. ExplanationValid DAYS value is a decimal number of days between 1 and 9999. Refer to the appropriate IDCAMS documentation for specific information on this options. ISRU474 Enter decimal number between 1 and 16776704. ExplanationValid Buffer Space value is a decimal number between 1 and 16776704. Refer to the appropriate IDCAMS documentation for specific information on this options. ISRU475 Enter a year between 1993 and 2099. ExplanationThe year value of the Days To field must be between 1993 and 2099. Refer to the appropriate IDCAMS documentation for specific information on this options. ISRU476 Enter a day between 1 and 365. ExplanationThe day value of the Days To field must be between 1 and 365. Refer to the appropriate IDCAMS documentation for specific information on this options. ISRU477 Return Code 0 - The IDCAMS command processed for aaaaaaaa was
successful. ExplanationThis is an informational message. ISRU478 Enter one to eight characters. ExplanationThis message is self explanatory. ISRU479 Enter a decimal number between 1 and 255. ExplanationThe length value of the Keys field must be between 1 and 255. Refer to the appropriate IDCAMS documentation for specific information on this options. ISRU480 Enter one to eight characters. ExplanationThis message is self explanatory. ISRU481 Enter one to eight characters. ExplanationThis message is self explanatory. ISRU482 Enter one to six characters, beginning with a letter. ExplanationThis message is self-explanatory. ISRU483 Return Code 0 - aaaaaaaa was successfully
deleted. ExplanationThis is an informational message. ISRU484 The information request has been completed. ExplanationThis is an informational message. ISRU485 Days cannot be specified as both a for number of days and
a to date. ExplanationWhen specifying the Days option, you must specify either the retention period in days (the For value) or the ending data (the To value), but not both. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU486 IDCAMS has returned a nonzero return code. ExplanationThis is an informational message. User responseSee IDCAMS output for details. ISRU487 Request canceled - Process request has been canceled. ExplanationThis is an informational message. ISRU488 Enter YES if you would like to edit the command data set. ExplanationThis message is self explanatory. ISRU489 Enter Noerase or Erase. ExplanationValid values for this field are ERASE or NOERASE. Refer to the appropriate IDCAMS documentation for specific information on this options. ISRU490 Enter Noforce or Force. ExplanationValid values for this field are FORCE and NOFORCE. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU491 Enter Nopurge or Purge. ExplanationValid values for this field are PURGE and NOPURGE. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU492 Enter Norecovery or Recovery. ExplanationValid values for this field are RECOVERY and NORECOVERY. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU493 Enter Scratch or Noscratch. ExplanationValid values for this field are SCRATCH and NOSCRATCH. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU494 Enter Unordered or Ordered. ExplanationValid values for this field are ORDERED and UNORDERED. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU495 Enter Recovery or Speed. ExplanationValid values for this field are RECOVERY and SPEED. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU496 Enter Noreuse or Reuse. ExplanationValid values for this field are REUSE and NOREUSE. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU497 Enter Nonspanned or Spanned. ExplanationValid values for this field are SPANNED and NONSPANNED. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU498 Duplicate entry ignored. ExplanationAn attempt to add a duplicate ACL entry has been ignored. ISRU499A Enter ICFCATALOG, VSAMCATALOG or VOLCATALOG ExplanationValid values for this field are ICFCATALOG, VSAMCATALOG and VOLCATALOG. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU500 Enter Norecatalog or Recatalog. ExplanationValid values for this field are RECATALOG and NORECATALOG. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU501 Enter Indexed, Nonindexed, Linear, or Numbered. ExplanationValid values for this field are INDEXED, NONINDEXED, LINEAR and NUMBERED. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU502 Enter Noempty or Empty. ExplanationValid values for this field are EMPTY and NOEMPTY. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU503 Enter Noscratch or Scratch. ExplanationValid values for this field are SCRATCH and NOSCRATCH. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU504 Enter Noswap or Swap. ExplanationValid values for this field are SWAP and NOSWAP. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU505 Enter Nonuniquekey or Uniquekey. ExplanationValid values for this field are UNIQUEKEY and NOUNIQUEKEY. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU506 Enter Upgrade or Noupgrade. ExplanationValid values for this field are UPGRADE and NOUPGRADE. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU507 Enter Y, N, or leave blank. ExplanationThis message is self explanatory. ISRU508 Enter All, Allocation, History, Name, Volume or leave blank. ExplanationValid values for this field are ALL, ALLOCATION, HISTORY, NAME, VOLUME or blank. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU509 Enter Unlock or Lock. ExplanationValid values for this field are LOCK and UNLOCK. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU510 CVOL and VSAM catalogs are no longer supported. Matching
data sets cataloged in ICF catalogs are listed. ExplanationData sets in VSAM or CVOL catalogs can no longer be listed. Matching entries in ICF catalogs are listed. Programmer responseNone. ISRU511 No matching data sets were found in ICF catalogs. ExplanationCVOL and VSAM catalogs are no longer supported. Programmer responseChange the data set name level used. ISRU512 List may be incomplete. - Entries in catalogs that the user
has authority to are listed. There may be other entries that match
the data set name level that are in catalogs the user has no authority
to. ExplanationThe user does not have RACF or other authority to the master catalog and possibly some user catalogs. Data sets in catalogs that the user has authority to are listed. Programmer responseNone. ISRU513 Invalid volume name - A generic volume name is not allowed
when displaying VTOC information. ExplanationA generic volume name is only allowed when displaying a VTOC list. It is not allowed when displaying VTOC information. User responseEnter a volume name. Programmer responseNone. ISRU514 Enter one of the listed values. ExplanationThis is an ISPF-supplied message displayed as the result of a LIST,value1,value2,... verification failure. User responseEnter one of the listed values in the field pointed to by the cursor. Programmer responseNone. ISRU515 Enter required field at the cursor position. ExplanationThis is an ISPF-supplied message displayed as the result of a verification failure. User responseEnter the appropriate data into the field at the cursor position. Programmer responseNone. ISRU516 The choice selected is not valid for the request type selected. ExplanationThe VSAM Data Type selected is not valid for the Process Request entered. User responseCorrect either the VSAM Data Type or the Process Request, then retry the request. ISRU517 No data set names found - No data sets are cataloged that
match pattern 'aaaaaaaa'. ExplanationThe pattern entered for dsname level does not match any data sets in the catalog. User responseChange the dsname level. Programmer responseNone. ISRU518 No data set names found - There were no entries in catalogs
that the user has authority to that match the pattern 'aaaaaaaa'. ExplanationThis is an informational message. The user does not have RACF or other authority to the master catalog and possibly some user catalogs. There are no matching entries for the pattern in catalogs that the user has access to. Programmer responseNone. ISRU519 Invalid Dsname Level - In order to list catalog entries,
you must specify at least one partial qualifier. Any Dsname Level
that contains only asterisks is invalid. ExplanationIf you specify only asterisks for a dsname level, a search is made of all the catalogs on the system. This severely impairs performance, so at least one partial qualifier is required. User responsePartially qualify at least one dsname level qualifier. Programmer responseNone. ISRU520 Invalid Dsname Level - Two or more adjacent asterisks within
a Dsname Level qualifier is invalid. A single asterisk indicates
0 or more letters may occupy that position in the qualifier. ExplanationTwo or more adjacent asterisks means 0 or more qualifiers may occupy that position. This is invalid within a single qualifier. Double asterisks may be used as a qualifier with no other characters. User responseChange the adjacent asterisks to a single asterisk. Programmer responseNone. ISRU521 Invalid length qualifier - All Dsname Level qualifiers must
be 1 to 8 characters in length. ExplanationThere is a qualifier of 0 or more than 8 characters in the Dsname Level entered. User responseCorrect the Dsname Level qualifier. Programmer responseNone. Problem determinationVerify the Dsname levels, each must be 1 to 8 characters in length. ISRU522 Invalid VSAM delete - Delete is an invalid command for VSAM
data and index components. Delete is only allowed on the cluster
component. ExplanationIf you want to delete a VSAM data set, issue the delete command against the VSAM cluster. Programmer responseNone. ISRU523 Catalog search canceled - Enter a Dsname Level with a high
level qualifier other than '*' or '**'. ExplanationA high level qualifier of "*" (asterisk) or "**" (double asterisk) requires a search of all the catalogs on the system. This may require a great deal of time. You have chosen to cancel this search. Continue by entering another dsname level. User responseChange the Dsname Level. Programmer responseNone. Problem determinationChange the first level of the Dsname to some thing other than '**' or '*'. ISRU524 RDJFCB failed - The RDJFCB macro failed for data set 'aaa(44)'. ExplanationAn attempt to read the JFCB for the multivolume data set specified was not successful. User responseContact your system programmer. Programmer responseNone. Problem determinationVerify the sort operand. ISRU525 Data set aaaaaaaa - Data set 'bbb(44)' aaaaaaaa to
data set 'ccc(44)' ExplanationThis is an informational message. Programmer responseNone. ISRU526 Data set aaaaaaaa - Data set 'bbb(44)' aaaaaaaa to
data set 'ccc(56)'. ExplanationThis is an informational message. Programmer responseNone. ISRU527 Data set aaaaaaaa - Data set 'bbb(44)' aaaaaaaa to
library cccccccc. ExplanationThis is an informational message. Programmer responseNone. ISRU528 Catalog search error - DFSMSdfp Catalog Search returned these
details for a catalog search on aaaaaaaa: Return
code was bbbbbbbb (decimal); Reason code was cccccccc (decimal);
Module ID was dddddddd. (Note: Catalog Services
only returns a 2-byte module ID.) ExplanationThe catalog search to find the requested data set names failed. User responseRefer to the description of IDC3009I in z/OS MVS System Messages, Vol 6 (GOS-IEA) for more information about this error. Programmer responseNone. ISRU529 List may be incomplete. - Catalog search error. DFSMSdfp
Catalog Search returned these details for a catalog search on aaaaaaaa:
Return code was bbbbbbbb (decimal); Reason code
was cccccccc (decimal); Module ID was dddddddd.
(Note: Catalog Services only returns a 2-byte module ID.) ExplanationThe catalog search to find the requested data set names failed. User responseRefer to the description of IDC3009I in z/OS MVS System Messages, Vol 6 (GOS-IEA) for more information about this error. Programmer responseNone. ISRU530 Data retrieved - The GET command completed. Data from the
profile was retrieved and stored into the panel input fields. ExplanationThis is an informational message. ISRU531 Profile name set - The profile data set name has been set
and the data set was allocated if it did not previously exist. ExplanationThis is an informational message. ISRU532 Enter a decimal value between 0 and 32768. ExplanationValid values for the Length value of the Keys option are a decimal number between 0 and 32768. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU533 Enter a decimal value between 1 and 32768. ExplanationValid values for Average Record Size are a decimal number between 0 and 32768. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU534 Enter Unique or Suballocation ExplanationValid values for this field are UNIQUE and SUBALLOCATION. Refer to the appropriate IDCAMS documentation for specific information on these options. ISRU535 Member name not allowed - Use "NEW" member name field to
rename "TO" member. ExplanationA member name is not allowed as part of the TO data set name. User responseRemove member name from TO data set name. ISRU536 Settings saved - Workplace Settings have been saved to aaaaaaaa profile. ExplanationWorkplace settings were updated and saved to the ISPF profile. ISRU537 Settings canceled - Workplace settings canceled. ExplanationWorkplace settings were not updated or saved. ISRU538 DSLIST processed - DSLIST has been successfully processed. ExplanationThe DSLIST action has completed successfully. ISRU539 List no longer defined - The personal list selected has been
previously deleted by you or another user. Select another list. ExplanationThe DSLIST action has completed successfully. ISRU540 Enter Command name - Enter command name to invoke in the
Prompt action field.
ISRU541 Invalid Value - Enter a number from 1 to 8 for direct selection
of a library entry. Enter a "/" and press Enter to display Personal
list. Enter "DL" to display a DSLIST based on Library entries.
ISRU542 Invalid Value - Enter A (Save As), O (Open), D (Delete),
E (Edit), L (DSLIST) or / (Prompt).
ISRU543 Confirm delete aaaaaaaa - Confirm member
delete has been set to aaaaaaaa.
ISRU544 Action "=" invalid - The "=" (repeat) action is not valid
when used with the primary select command.
ISRU545 Welcome to the ISPF Workplace. Default view has been set
to Data Set. Enter Action "ListView" to change view to ISPF Library.
Default settings have been established for Applid 'aaaaaaaa'.
Select "Workplace Settings" from Option action bar to change Workplace
settings at any time.
ISRU546 Severe Exit Error - The member list line command exit issued
a return code of 20. ExplanationAccount member list user exit returned a RC=20. ISRU547 Unknown Exit Error - The member list line command exit issued
a unknown return code. ExplanationAccount member list user exit returned a RC that was not 0,8 or 20. ISRU548 Invalid Value - Enter a number from 1 to 30 to directly select
a data set entry. Enter a "/" and press Enter to display personal
list. Enter "DL" to display a DSLIST based on data set entries.
ISRU549 aaaaaaaa new append(s) - The currently
displayed DSLIST has been appended with aaaaaaaa additional
data set(s). ExplanationInformational only ISRU541A No new appends - No additional data sets were appended to
the DSLIST. ExplanationInformational only ISRU541B Entry not defined - The list entry selected is blank or entry
number is out of range. ExplanationInformational only ISRU550 Enter character string - Enter the string of characters to
be excluded. ExplanationThe EXCLUDE command was entered on an option 3.4 data set list, but no parameter was specified to indicate what the exclude target was. User responseSpecify a target string on the EXCLUDE command. ISRU551 Invalid keyword - Check spelling of keywords used with the
EXCLUDE command. ExplanationThe EXCLUDE command was entered, passing a quoted string as the target string to EXCLUDE, but an additional parameter was specified that was not recognized at a valid EXCLUDE keyword. Valid keywords are: ALL, FIRST, LAST, NEXT, PREV, CHARS, PREFIX, SUFFIX, and WORD. User responseCorrect the specified keyword and retry the command. ISRU552 Put string in quotes - Put quotes (' ') around the string
of characters to be excluded. ExplanationThe EXCLUDE command was entered, passing multiple words as parameters that were not recognized as valid keywords. It is assumed that the words were intended to be an argument to the EXCLUDE command and, if so, must be enclosed in quotation marks. User responseAdd quotation marks around the string and retry the command. ISRU553 Invalid keyword - The keywords 'aaaaaaaa'
and 'bbbbbbbb' cannot both be used. Delete one. ExplanationThe EXCLUDE command was entered, passing conflicting
keywords. Only one of these keywords may be specified. Two kinds
of keywords are supported by the EXCLUDE command: direction keywords
and type keywords. No more than one of each kind of keyword may be
specified on the EXCLUDE command. The keywords are:
The defaults are NEXT and CHARS User responseCorrect the keywords specified and retry the command. ISRU554 Enter character string - A character string for EXCLUDE has
not been entered and '*' is invalid until a character string is entered. ExplanationAn asterisk (*) used as the target string of the EXCLUDE command indicates that the previous target string should be reused. An asterisk was entered but no previously entered valid target string was found, making the use of the asterisk invalid. User responseEnter a valid target string. Once a target string is entered, the asterisk may then be used on subsequent EXCLUDE commands. ISRU555 EXCLUDE string too long - The EXCLUDE string cannot be longer
than 44 characters. ExplanationThe EXCLUDE command searches for the specified target string within the list of data set names. Since the maximum length of a data set in the list is 44 characters, the target string may not exceed 44 characters. User responseRetry the command, entering a target string that is equal to or less than 44 characters in length. ISRU556 Invalid character string - The EXCLUDE string cannot be a
null ('') string. ExplanationThe EXCLUDE target string must be a minimum of 1 character in length. A target string of 0 characters was entered. User responseRetry the command, entering a target string that is equal to or greater than 1 character in length. ISRU557 All data sets excluded - All data sets in the data set list
have been excluded. ExplanationThe command EXCLUDE ALL causes all data sets in the data set list A tarto be excluded. ISRU558 aaaa - bbbbbbbb ccc(44) - bbbbbbbb ccc(44) excluded
on aaaa line(s) ExplanationThis is an informational message. An EXCLUDE ALL command was entered on a data set list, and the specified target string was successfully located. ISRU559 aaaaaaaa bbb(44) excluded
- Search for aaaaaaaa bbb(44) was
successful. ExplanationThis is an informational message. An EXCLUDE command was entered on a data set list, and the string was successfully located. ISRU560 *Bottom of list reached* - aaaaaaaa bbb(44) not
found. Press the RFIND key to continue the search from the top of
the data set list. ExplanationThis is an informational message. The data set list EXCLUDE command searches from the top of the displayed data to the bottom of the list to find the target string. EXCLUDE has searched and reached the bottom of that list without finding the target string. Entering the RFIND command continues the search, starting from the top of the data set list. ISRU561 * Top of list reached * - aaaaaaaa bbb(44) not
found. Press the RFIND key to continue the search from the bottom
of the data set list. ExplanationThis is an informational message. When the PREV keyword is specified, the data set list EXCLUDE command searches from the top of the displayed data to the top of the list to find the target string. EXCLUDE has searched and reached the top of that list without finding the target string. Entering the RFIND command continues the search, starting from the bottom of the data set list. ISRU562 No aaaaaaaa bbb(44) found
- aaaaaaaa bbb(44) - not found
in any NON-X'ED data set names. ExplanationThis is an informational message. An EXCLUDE command was entered to cause the data set list processor to search the entire data set list for the specified target string. The search was completed, but the target string was not found in any unexcluded data set names. ISRU563 Invalid string type - Data set list EXCLUDE command does
not process picture (P'...'), hex (X'...'), text (T'...') or char
(C'...') strings. ExplanationThe data set list EXCLUDE command does not support
all of the keywords supported by the editor EXCLUDE command. The
following keywords are not supported:
All EXCLUDE commands are treated as text strings (T'...'), meaning that strings are matched regardless of case. User responseRemove the unsupported keyword and reenter the command. ISRU564 Invalid line command - The only line commands that are valid
on excluded lines are 'NX', 'NXF', and 'NXL'. ExplanationInformational User responseRemove the line command from the excluded line. ISRU565 - ExplanationThis message is for the ISPF Workplace scrollable section and contains a X'00' so no text will display with this message. ISRU566 Invalid parameter - Line command aaaaaaaa has
an invalid parameter specified. ExplanationThe exclude (X) and unexclude (NX, NXF, NXL) do not accept any parameters. User responseRemove the extra parameter or change the command. ISRU567 Invalid Library Action - The selected action is not valid
for ISPF Library view. Change View to "Data Set" to perform this
action.
ISRU568 Invalid Data Set Action - The selected action is not valid
for Data set view. Change View to "Library" to perform this action.
ISRU569 Volume not available - Volume 'aaaaaaaa'
not mounted or not authorized for your use. ExplanationPDF received one of the following return codes
while processing volume aaaaaaaa, indicating that
the volume specified is not available for your use:
User responseVerify that the correct data set name and volume were specified to PDF, and correct them if necessary. If the data specified looks correct, contact your system programmer. ISRU570 Workstation file saved - The workstation file has been successfully
saved. ExplanationInformational only. ISRU571 Data Set Saved - Data set - 'aaaaaaaa'
- Saved. ExplanationInformational only. The sequential data set was saved. ISRU572 aaaaaaaa members bbbbbbbb -
to data set cccccccc.. One or more members was
passed to the Binder for processing but was found not to be a load
module (Binder message IEW2522S). These members were successfully
copied using an alternate method. ExplanationISPF passes all members of a record format U PDS data set to the Binder for processing as a load module. If the Binder detects that the member is not a load module, it issues message IEW2522S and returns an error code of '83000523' to ISPF. ISPF will reprocess these members using a read-write loop and the IEW2522S message should be ignored. ISRU573 Some entries not used - One or more names in the specified
personal list could not be found. The data set list was built using
the entries that do match existing data sets. ExplanationOne or more of the data sets specified in the reference list passed to the DSLIST command do not exist and have therefore not been added to the data set list. ISRU574 Catalog error - Catalog/uncatalog request via SVC 26 failed,
return code = aaaaaaaa, reason code = bbbbbbbb,
module id = cccccccc. ExplanationThe catalog search to process the requested data set failed. User responseRefer to the appropriate dfSMS documentation for an explanation of the error. Programmer responseNone. ISRU575 RACF error - The data
set name is ineligible for RACF definition ExplanationAs the result of a DEFINE, IMPORT, or IMPORTRA command, VSAM attempted to define a RACF profile for the object. The profile could not be established because the user does not have sufficient authority for the specified data set characteristics User responseCheck your RACF authorization. Programmer responseCheck the installation security subsystem guidelines for defining a data set in the security subsystem. Modify the data set characteristics accordingly. ISRU576 to aaaaaaaa ExplanationThis is an informational message written to the ISPF log data set. ISRU578 Copy failed - Copied failed for member aaaaaaaa..
Members whose directory entries contain user TTRs cannot be copied
into a PDSE. Move/Copy completed for bbbbbbbb members. ExplanationYou attempted to copy a member that contained user TTRs into a PDSE data set. PDSE's do not support user-supplied TTRS in the user data field of the directory entry. ISRU579 Copy failed - Members whose directory entries contain user
TTRs cannot be copied into a PDSE. ExplanationYou attempted to copy a member that contained user TTRs into a PDSE data set. PDSE's do not support user-supplied TTRS in the user data field of the directory entry. ISRU580 IEBCOPY setup failed - The allocation of the IEBCOPY input
data sets failed. ExplanationThe allocation of the specified input libraries to separate DDNAMEs needed for invocation of IEBCOPY failed. System programmer responseContact IBM service for assistance User responseContact your system administrator for assistance ISRU581 IEBCOPY setup failed - The allocation of the IEBCOPY output
data sets failed. ExplanationThe allocation of the specified output library to a separate DDNAMES needed for invocation of IEBCOPY failed. System programmer responseContact IBM service for assistance User responseContact your system administrator for assistance ISRU582 aaaaaaaa members bbbbbbbb -
to data set cccccccc.. One or more members was
passed to the Binder for processing but was found not to be a load
module (Binder message IEW2522S). These members were successfully
copied using an alternate method. ExplanationISPF passes all members of a record format U PDS data set to the Binder for processing as a load module. If the Binder detects that the member is not a load module, it issues message IEW2522S and returns an error code of '83000523' to ISPF. ISPF will reprocess these members using a read-write loop and the IEW2522S message should be ignored. ISRU583 List incomplete - One or more names in the specified reflist
could not be found. ExplanationOne or more of the data sets specified in the reference list passed to the DSLIST command do not exist and have therefore not been added to the data set list. ISRU584 IEBCOPY interface failed - The Move/Copy processor could
not allocate the SYSPRINT data set needed for invocation of IEBCOPY. ExplanationThe Move/Copy processor allocates a data set named 'prefix.SPFnnn.IEBCOPY' to hold the IEBCOPY SYSPRINT output. ISPF will make 50 attempts to create a data set before failing. User responseDelete any unneeded 'zprefix.SPFnnn.IEBCOPY' data sets. Programmer responseNone. ISRU585 Catalog error - Generic Filter Locate (GFL) request via SVC
26 failed, return code = aaaaaaaa, reason code
= bbbbbbbb, module id = cccccccc. ExplanationThe catalog search to find the requested data set name failed. User responseRefer to the appropriate DFP documentation for an explanation of the error. Programmer responseNone. ISRU585A Catalog error - Generic Filter Locate (GFL) request via SVC
26 failed because a CVOL or VSAM catalog was processed. ExplanationThe catalog search to find the requested data set name failed. CVOL and VSAM catalogs are no longer supported. User responseCatalog the data set in an ICF catalog. Programmer responseNone. ISRU586 Mixed Copy - Copying a mixture of load and non-load data
sets to a PDSE data set is not supported. ExplanationThe Move/Copy request involves moving both load module members and non-load module members to the same PDSE. A PDSE cannot contain both load and non-load data. User responseDetermine which members are load and non-load and copy them to different libraries, or make your target data set a PDS. To find non-load members in a RECFM=U data set, bring up a member list, sort by SIZE and scroll to the bottom of the member list. Any members listed without statistics are not load modules. Programmer responseNone. ISRU587 Not found - Generic Filter Locate (GFL) request via SVC 26
failed to find the data set in the catalog. ExplanationThe catalog search did not find the requested data set name. User responseCheck that the data set is either cataloged in the master catalog or in a user catalog which is connected to the master catalog. Programmer responseNone. ISRU588 Copy failed - Copied failed for member aaaaaaaa..
Members whose directory entries contain user TTRs cannot be copied
into a PDSE. Move/Copy completed for bbbbbbbb members. ExplanationYou attempted to copy a member that contained user TTRs into a PDSE data set. PDSEs do not support user-supplied TTRS in the user data field of the directory entry. ISRU589 Copy failed - Members whose directory entries contain user
TTRs cannot be copied into a PDSE. ExplanationYou attempted to copy a member that contained user TTRs into a PDSE data set. PDSE's do not support user-supplied TTRS in the user data field of the directory entry. ISRU590 File not replaced - Workstation file aaaaaaaa already
exists and was not replaced. ExplanationA file transfer request was issued from ISPF option 3.7.4 with the REPLACE option not selected. The target workstation file already exists and is therefore not replaced. Select the "Replace existing member/file" choice to replace the workstation file. ISRU591 Member not replaced - Member aaaaaaaa already
exists and was not replaced. ExplanationA file transfer request was issued from ISPF option 3.7 with the REPLACE option not selected. The target data set member already exists and is therefore not replaced. Select the "Replace existing member/file" choice to replace the member. ISRU592 Data set not replaced - Sequential data set aaaaaaaa already
exists and was not replaced. ExplanationA file transfer request was issued from ISPF option 3.7 with the REPLACE option not selected. The target sequential data set already exists and is therefore not replaced. Select the "Replace existing member/file" choice to replace the data set. ISRU593 Invalid Dsname Level - The ISPF configuration table has been
set to disallow the use of wild cards in the high level qualifier. ExplanationThe ISPF configuration table has a selection field to disallow the ability to enter a wild card in the high level qualifier. The wild cards are "*" and "%". This field has been set to disallow the use of a wild card in the high level qualifier. System programmer responseRemove the ISPF configuration table selection that disallows the use of a high level qualifier in ISPF option 3.4. User responseSee you system programmer Programmer responseSee your system programmer ISRU594 Catalog error - Errors were returned from the search on one
or more catalogs. Enter HELP for a list of catalog(s), return code(s),
reason code(s), and module id(s). See message IDC3009I to interpret
these codes. ExplanationThe catalog search to find the requested data set names failed for one or more catalogs. User responseRefer to the appropriate dfSMS documentation for an explanation of the error, in particular message IDC3009I. Programmer responseNone. ISRU595 Member name invalid - A qualifier in parentheses may only
be specified as a GDG relative generation such as (0), (-1), or (+1). ExplanationThe data set list search is for data set names only; member names are not included. User responseCorrect the DSname level by specifying a GDG relative generation or a valid DSNAME level. Programmer responseNone. ISRU596 You have specified a volume serial for the data set you want
renamed. The data set is also cataloged on that volume. In addition
to renaming the data set, you should select the "Catalog the new data
set name" selection field if you want the data set cataloged. If
you do not, then the data set will be renamed and the catalog entry
for the old data set will be not deleted or altered. ExplanationFor non-managed data sets, if you enter the data set name in the OTHER DATA SET name field and the volume serial in the VOLUME SERIAL field, the new name will not be cataloged if the data set was not cataloged previously. If the data set is cataloged on the volume specified, you will be given a choice of whether or not to recatalog the data set. If you choose not to recatalog the old catalog is not deleted or altered. User responseSelect the "Catalog the new data set name" field if you want the data set cataloged. ISRU600 Enter member name - Enter member name or pattern to be searched
for in the partitioned data sets in the data set list. ExplanationThe data set list MEMBER command searches the partitioned data sets in the data set list for an occurrence of a member that matches the member name or the pattern entered with the MEMBER command. ISRU601 Invalid parameter - Only one member name or pattern, only
one limit ('x', 'ex' or 'nx') and only one recall parameter ('recall1'
or 'recall2') may be specified for the Member command. ExplanationThis is an informational message. More than one member name/pattern or more than one limit or more than one recall parameter was specified for the Member command. ISRU602 Member not found - Member aaaaaaaa - not
found in any NON-X'ED partitioned data set names. ExplanationThis is an informational message. A MEMBER command was entered to cause the data set list processor to search all the unexcluded partitioned data sets for the member name or pattern. The search was completed, but the member was not found in any unexcluded data set names. ISRU603 Member not found - Member aaaaaaaa - not
found in any X'ED partitioned data set names. ExplanationThis is an informational message. A MEMBER command was entered to cause the data set list processor to search all the excluded partitioned data sets for the member name or pattern. The search was completed, but the member was not found in any excluded data set names. ISRU604 Member(s) found - Member aaaaaaaa found
in bbbbbbbb data sets. ExplanationInformational ISRU605 Member not found - Member aaaaaaaa was
not found in any partitioned data set in the data set list. ExplanationInformational. ISRU606 Invalid member name - The member name or pattern must be
8 characters or less. ExplanationInformational. ISRU607 Member not found - Member aaaaaaaa not
found in any partitioned data sets. bbbbbbbb migrated
data sets were not searched. ExplanationThis is an informational message. A MEMBER command was entered to cause the data set list processor to search all the partitioned data sets for the member name or pattern. The search was completed, but the member was not found. Some migrated data sets were not searched. ISRU608 Member(s) found - Member aaaaaaaa found
in bbbbbbbb data sets. cccccccc migrated
data sets were not searched. ExplanationThis is an informational message. A MEMBER command was entered to cause the data set list processor to search all the partitioned data sets for the member name or pattern. The member or pattern was found in some of the data sets. Some migrated data sets were not searched. ISRU609 Put member in quotes - Put quotes (' ') around the member
name to be found. ExplanationThis is an informational message. More than one member name/pattern or more than one limit or more than one recall parameter was specified for the Member command. Please put the member name to be found in quotes. ISRU610 PDS List DS invalid - Partitioned list data set not allowed
for SRCHFOR command ExplanationSearches of multiple data sets must list results in a sequential data set. User responseSpecify a new or existing sequential ds and try again. ISRU611 Invalid parameter - Only one search string may be specified
on this panel. Enter SRCHFOR with no operands for other options. ExplanationThis is an informational message. Other parameters may be specified from a subsequent panel. Enter SRCHFOR alone or with one quoted search string. ISRU612 String(s) not found - String(s) not found in any of the aaaaaaaa unexcluded
data sets searched. bbbbbbbb migrated data sets
were not searched. cccccccc data sets were not
searched for other reasons. Details in dddddddd. ExplanationThis is an informational message. A SRCHFOR command was entered to cause the data set list processor to search all the unexcluded data sets for the string(s). The search was completed, but the string was not found in any unexcluded data set names. ISRU613 String(s) not found - String(s) not found in any of aaaaaaaa excluded
data sets searched. bbbbbbbb migrated data sets
were not searched. cccccccc data sets were not
searched for other reasons. Details in dddddddd. ExplanationThis is an informational message. A SRCHFOR command was entered to cause the data set list processor to search all the excluded data sets for the string(s). The search was completed, but the string was not found in any excluded data set names. ISRU614 String(s) found - String(s) found in aaaaaaaa of
the bbbbbbbb data sets searched. cccccccc migrated
data sets were not searched. dddddddd data sets
were not searched for other reasons. Details in eeeeeeee. ExplanationInformational ISRU615 String(s) not found - String(s) not found in any of the aaaaaaaa data
sets searched. bbbbbbbb migrated data sets were
not searched. cccccccc data sets were not searched
for other reasons. Details in dddddddd. ExplanationInformational. ISRU616 String(s) found - String(s) found in aaaaaaaa of
the bbbbbbbb excluded data sets searched. cccccccc migrated
data sets were not searched. dddddddd data sets
were not searched for other reasons. Details in eeeeeeee. ExplanationInformational ISRU617 String(s) found - String(s) found in aaaaaaaa of
the bbbbbbbb unexcluded data sets searched. cccccccc migrated
data sets were not searched. dddddddd data sets
were not searched for other reasons. Details in eeeeeeee. ExplanationInformational ISRU618 Search not run - Unable to acquire ISPF temporary data set
(DDNAME ISPCTLn). Possible installation error, or DD has been unexpectedly
freed or deleted. Log off, log on and retry. ExplanationSee the information about preallocating ISPF temporary data sets in Planning and Customizing. System programmer responseVerify ISPCTLn data sets are properly allocated. ISRU619 Table aaaaaaaa not found - Table aaaaaaaa was
not found in DD bbbbbbbb. ExplanationISPF was unable to find the table aaaaaaaa in the supplied table DD bbbbbbbb. User responseUse a tool such as ISRDDN to check if member aaaaaaaa exists in DD bbbbbbbb. ISRU620 Row already exists - Table aaaaaaaa already
contains a row with the specified key ExplanationA keyed table requires the rows to have unique key values. User responseSpecify a unique key value for the row being added. ISRU621 Table aaaaaaaa not found - Table aaaaaaaa was
not found in library bbbbbbbb. ExplanationISPF was unable to find the table aaaaaaaa in the supplied table data set bbbbbbbb. User responseCheck if member aaaaaaaa exists in bbbbbbbb. ISRU622 Invalid command - Valid member list commands are S (SELECT)
and L (LOCATE). ExplanationA command other than S (SELECT) or L (LOCATE) was entered. User responseCheck the command entered on the command line. ISRU623 Display length too short - The minimum display length is
7 characters. The display length is set to 7. ExplanationThe minimum length used to display the data for each column of the table is 7 characters. ISRU624 Changes canceled - Changes since the last SAVE were not applied
to table aaaaaaaa. ExplanationInformational ISRU625 Table saved - All the latest changes have been applied to
table aaaaaaaa. ExplanationInformational. ISRU626 Not in Edit - The aaaaaaaa command is
only valid for Edit. ExplanationInformational ISRU627 Not in Edit - E (Extension Variables) is the only line command
allowed in Browse. ExplanationInformational ISRU628 Table in use - Table aaaaaaaa is in use
by another user or on another logical screen. ExplanationThe ENQ at table open failed because the table is currently in use either by another user or by this user on another logical screen. User responseIf you have the table open on another logical screen either close the table or ensure it is opened on both logical screens in SHARE mode. ISRU629 aaaaaaaa not allocated - Table input library
DD aaaaaaaa is not allocated. ExplanationThe table input library DD was found not to be allocated to the user. User responseUse the TSO ISRDDN command to check if the DD is allocated. ISRU630 No table data sets - No table data sets (PDS/Es) were found
allocated to table library DD aaaaaaaa. ExplanationNo partitioned data sets were found allocated to the table library DD. User responseUse the TSO ISRDDN command to check that the data sets allocated to the table library DD are partitioned. ISRU631 aaaaaaaa already open - Table aaaaaaaa is
already open in bbbbbbbb mode in this logical screen.
Table is being processed in bbbbbbbb mode. ExplanationThe selected table aaaaaaaa was found to be already open in this logical screen. It can be processed in bbbbbbbb mode. User responseCheck whether it is acceptable to process the table in bbbbbbbb mode. ISRU632 aaaaaaaa sorted - Table aaaaaaaa has
been sorted as requested. ExplanationInformational ISRU633 aaaaaaaa not sorted - Table aaaaaaaa has
not been sorted because no sort fields were specified. ExplanationInformational ISRU634 No parameters specified - The FIND command requires specification
of a table variable name or column number and a target string. ExplanationThe syntax of the FIND command is "F varname charstring" or "F column_no charstring". User responseSupply the required parameters on the FIND command. ISRU635 Target string required - The FIND command requires specification
of a target string in addition to either a table variable name or
column number. ExplanationThe syntax of the FIND command is "F varname charstring" or "F column_no charstring". User responseSupply the required parameters on the FIND command. ISRU636 'aaaaaaaa' found - Search found 'aaaaaaaa'
in table variable 'bbbbbbbb' on line cccccccc ExplanationInformational ISRU637 'aaaaaaaa' not found - Search did not
find 'bbbbbbbb' in table variable 'cccccccc' ExplanationInformational ISRU638 aaaaaaaa not in table - The variable 'aaaaaaaa'
does not exist in table bbbbbbbb ExplanationThe variable name aaaaaaaa specified on the FIND command is not defined for table bbbbbbbb. User responseCheck the variable name specified on the FIND command. ISRU639 Invalid column number - The specified column number 'aaaaaaaa'
is not in the range 1 to bbbbbbbb ExplanationThe column number specified on the FIND command is outside the range of column numbers for this table. User responseCheck the column number specified on the FIND command. ISRU640 *Bottom of data reached* - 'aaaaaaaa'
- not found. Press RFIND key to continue from top. ExplanationInformational ISRU641 SAVE failed - SAVE failed - table input library DD aaaaaaaa not
allocated. ExplanationThe table input library DD was found not to be allocated when the SAVE function was performed. User responseUse the TSO ISRDDN command to check if the DD is allocated. ISRU642 SAVE failed - SAVE failed - no data sets allocated to the
input library DD aaaaaaaa. ExplanationThe table input library DD was found not to be allocated when the SAVE function was performed. User responseUse the TSO ISRDDN command to check the allocation for the table input library DD. ISRU643 aaaaaaaa failed - aaaaaaaa of
table export data set bbbbbbbb failed, RC = cccccccc ExplanationThe service invoked to display the table export data set bbbbbbbb failed with a return code of cccccccc. User responseCheck the ISPF Service Guide for the return codes from the service. ISRU644 SAVE canceled - SAVE command has been canceled, no table
data set was selected. ExplanationA table data set into which the table was to be saved was not selected from the list of data sets allocated to the table library DD. User responseTo save the table, select one of the data sets displayed in the list of data sets allocated to the table library DD. ISRU645 Invalid command - The command aaaaaaaa entered
is not valid for the Table Utility. ExplanationData was entered in the command line which was not recognized as one of the valid commands for the Table Utility. User responseEnter a valid command. Valid primary commands in the Table Utility are LEFT, RIGHT, CANCEL, SAVE, STRUCT, STATS, SORT, DUMP, FIND, and RFIND. ISRU646 Allocation failed - The request to allocate the table export
data set aaaaaaaa failed. Check the export data
set attributes defined on the panel display via the Options pulldown
menu. Press help for more information. ExplanationISPF received an unexpected error from SVC 99 while trying to allocate the data set. Any error messages generated by the system should have been written to the screen as TSO line messages. User responseIf you did not see any messages, use the TSO PROFILE WTPMSG command to ensure your ID is set up to receive "write to programmer" messages, then retry the request. Once you get the messages, follow normal debugging steps for those messages. ISRU647 Open failed - The OPEN issued for the table export data set aaaaaaaa failed. ExplanationUnable to open for output the table export data set. ISRU648 Note - aaaaaaaa is open in NOWRITE mode,
changes will not be saved ExplanationAny changes made cannot be stored in the sort information record for the table because the table is open in NOWRITE mode. User responseIf you want the sort changes saved, open the table in WRITE mode. ISRU649 Enter required field - Table data set or table DD must be
specified to display a table list. ExplanationTo display a list of tables a table data set or DD for allocated table data set must be supplied. User responseEnter a table data set name or table DD name. ISRU650 Invalid select code - Use "S" to select a table for processing. ExplanationA line command other than S was entered on the table list. User responseEnter S against the table you wish to BROWSE or EDIT. ISRU651 Invalid select code - Use "E" (Edit) or "B" (Browse) to process
the selected table. ExplanationA line command other than E or B was entered on the table list. User responseEnter E (Edit) or B (Browse) against the table you wish to process. ISRU652 aaaaaaaa created - Data was imported to
create table aaaaaaaa in library bbbbbbbb. ExplanationInformational ISRU653 Invalid import data set - The table import data set did not
contain heading records in the correct format used to determine the
keys and variables for the table. ExplanationThe first record in the import data set must contain the names of the table variables. The second record must underline the table variable names with either plus signs (+) or dashes (-). A name underlined with plus signs indicates a table key. User responseCheck whether the first two records in the import data set are in the correct format. ISRU654 I/O error reading file - Error occurred during read of the
import data set. ExplanationAn I/O error occurred while reading the import data set. System programmer responseExamine the import data set for corruption. Use data set recovery techniques if the import data set is not usable. User responseContact your system programmer if the error persists. Problem determinationThe import data set may be corrupted. Use standard I/O error problem determination techniques. ISRU655 Empty data set - The table import data set does not contain
any data. ExplanationNo records were found in the table import data set. User responseCheck you specified the correct table import data set. ISRU656 Import canceled - The import function was canceled because
it would cause existing table aaaaaaaa in output
library bbbbbbbb to be replaced using data from
the import data set. ExplanationInformational ISRU657 Export canceled - The export of the table data was canceled
because the output data set aaaaaaaa already exists. ExplanationInformational ISRU658 Table will be saved in originating data set aaaaaaaa. ExplanationInformational ISRU659 No extension variables - There are no extension variables
to view for the selected table row. ExplanationInformational ISRU660 Cannot process table - The table aaaaaaaa cannot
be processed by the ISPF Table Utility because it uses a table of
this name for internal processing. ExplanationThe ISPF Table Utility uses these tables for internal processing: ISRTBSTR, ISRTBTMP, ISRTBEXT, ISRTBMEM, ISRTBDSN, and ISRTMTMV. Attempting to use the ISPF Table Utility to process a table with one of these names would cause the utility to fail. User responseRename the table you wish to process. ISRU661 Variable not added - Variable names with a prefix of 'ZTD'
or 'ZTB' are reserved for internal use by the ISPF table processing
and the ISPF Table Utility. The utility cannot process user table
variables with a name beginning with either 'ZTD' or 'ZTB'. ExplanationThe table variables with names commencing with 'ZTD' or 'ZTB' could conflict with variables used internally by the ISPF Table Utility. Attempting to process these variable with the ISPF Table Utility could cause either the utility to fail or the table data to be corrupted. User responseUse another name for the extension variable. ISRU662 Invalid shift value - Valid values for left/right shift are
P, PAGE, M, MAX, or a numeric value. ExplanationThe shift field defines the default scroll amount for left and right scrolling. The valid values are P (or PAGE), M (or MAX), or a numeric value representing the number of columns to horizontally scroll. User responseSupply a valid shift value. ISRU663 Changes canceled - Changes since the last SAVE were not applied
to table aaaaaaaa because a table output data set
was not selected. ExplanationA table data set into which the table was to be saved was not selected from the list of data sets allocated to the table library DD. User responseTo save the table, select one of the data sets displayed in the list of data sets allocated to the table library DD. ISRU664 Command not recognized - "aaaaaaaa" is
not a valid line command. Specify a valid line command. Explanationaaaaaaaa is not a valid line command. User responseCorrect the aaaaaaaa line command. ISRU665 Invalid command - The command entered is not valid for this
Table Utility function. ExplanationA command was entered that is not supported by this Table Utility function. User responseEnter a valid command for this Table utility function. ISRU666 Duplicate key found - Adding a row to the table for import
data set record aaaaaaaa failed because a row with
the same key already exists. ExplanationISPF does not support duplicate keys in tables. The table was not created. User responseRemove records with duplicate keys from the import data set. ISRU667 The Table Utility received unexpected return code aaaaaaaa for
table service bbbbbbbb.. Table Utility processing
is terminated. ExplanationWhen processing an internal table service request, the ISPF Table Utility received an unexpected return code. The Table Utility processing is terminated. System programmer responseContact IBM support. User responseContact your systems programmer. ISRU668 Invalid Data Set - The specified export or import data set
must be a physical sequential (DSORG=PS) data set. ExplanationThe ISPF Table Utility export and import functions only support output to or input from physical sequential data sets. PDS/E members are not supported. User responseSpecify a physical sequential data set. ISRU669 Table aaaaaaaa is already open as SHARED
on another logical screen. The display shows the table data currently
loaded into virtual storage. ExplanationThis message is to warn the user that data displayed for the shared table was already loaded into virtual storage and was not obtained by reading the table member in the table data set. Also if the shared table is being edited, any changes made to the table data will not be saved to the table data set but will only be applied to the virtual storage copy of the table. User responseIf you need to browse or edit a version of a shared table that is already open and loaded into virtual storage, temporarily rename the table member so it does not match the open table. ISRU670 Tape not supported - The built-in command is not valid for
a tape data set. ExplanationAn attempt to use a built-in command on a TAPE data set is causing this error message. Tape data sets are not supported for this command. System programmer responseVerify the users action on the Tape data set to see what action the user was attempting. User responseContact your system programmer. ISRU671 Tape interface error - Error invoking command for TAPE data
set. Return Code = aaaaaaaa.. ExplanationAn unexpected error occurred calling the Tape/Removable Media interface for a TAPE data set. System programmer responseVerify the Tape/Removable media command as specified in the ISPF Configuration options. User responseContact your system programmer. ISRU672 Table saved - The temporary table has been successfully saved
in the specified data set and member. ExplanationThe temporary table created by the Table Utility for a table currently in use has been successfully saved in the data set and member specified by the user. User responseContact your system programmer. ISRU673 Processing a temporary copy of table aaaaaaaa ExplanationTable aaaaaaaa is currently in use and you selected to process a temporary copy of this table. User responseContact your system programmer. ISRU700 Unexpected error from aaaaaaaa; Error: bbbbbbbb Reason: cccccccc -
Press HELP for more details. ExplanationAn unexpected error was returned by a z/OS UNIX system service aaaaaaaa. Programmer responseRefer to the z/OS UNIX System Services Programming: Assembler Callable Services Reference and z/OS UNIX System Services Messages and Codes manuals for descriptions of the error and reason codes. ISRU701 Home directory displayed - A pathname was not specified on
the entry panel. The pathname has defaulted to your home directory. ExplanationIf a pathname is not specified on the entry panel, the directory list displayed defaults to your working directory. ISRU702 Time zone aaaaaaaa is used to calculate
the displayed date and time values. ExplanationThe time zone aaaaaaaa was obtained from the TZ environment variable. This time zone setting is used to calculate all displayed date and time values. ISRU703 Unable to determine the TZ environment variable setting due
to errors - Press HELP for more details. The GMT offset is used to
calculate all displayed date and time values. ExplanationThe z/OS UNIX Directory List Utility was unable to obtain the setting for the TZ (time zone) environment variable. The GMT offset defined for the operating system is used to calculate all displayed date and time values. ISRU704 Permission denied - You do not have the necessary permission
to aaaaaaaa the directory entry. ExplanationThe directory does not have the necessary read permission set. For the directory LIST function, the directory does not have the necessary read permission set. For the DELETE
function, one of these situations exist:
For the RENAME function, one
of these situations exist:
For the CREATE (new) function,
one of these situations exist:
User responseCheck with your z/OS UNIX system administrator to see if the directory or file permissions can be altered to allow you to remove the file. ISRU705 Directory not found - The specified directory was not found
in the file system. The pathname is aaaaaaaa bytes
long.
ISRU706 Not a directory - The target of the specified pathname is
not a directory or valid mask.
ISRU707 Cannot use z/OS UNIX - The user ID is not authorized
to use z/OS UNIX. ExplanationThe user ID has not been defined to the system security product as a z/OS UNIX user. User responseAsk your z/OS UNIX system administrator to define this user ID to the system security product as a z/OS UNIX user. ISRU708 TBCREATE failure - Creation of the table used to display
the z/OS UNIX Directory List column arrangement failed. ExplanationThis is an internal ISPF processing failure. System programmer responseThere may be information in the ISPF log that sheds light on this failure. Perhaps there is a problem with the user's ISPTABL or ISPTLIB allocation. If you are unable to resolve the problem, contact IBM support. User responseWrite down the circumstances of the failure and contact your system programmer. It may be helpful to print or save the ISPF log when you exit ISPF. ISRU709 Not a directory - The L line command can only be used against
a directory. ExplanationThe L (List Directory) line command is only valid when entered against a directory. ISRU710 Invalid file type - Edit or browse is only valid for regular
files and non-external symbolic links. ExplanationThe file you selected to edit or browse is not a regular file or non-external symbolic link. ISRU711 TBCREATE failure - Creating the table of entries for the z/OS UNIX directory
list resulted in return cod aaaaaaaa. ExplanationA return code greater than 4 was received from the TBCREATE service. User responseThe error is probably due to the table being in use by another session. Free the table from that session and retry. ISRU712 File created - The new file was successfully created in another
directory. ExplanationThe specified file was successfully created in a directory not currently displayed by the z/OS UNIX Directory List utility. ISRU713 Enter a pathname - A pathname was not specified and your
home directory could not be determined. ExplanationIf a pathname is not specified on the entry panel it defaults to your home directory. ISPF was unable to determine your home directory. command. User responseCheck if you have a home directory defined to z/OS UNIX. ISRU714 Invalid pathname - An absolute or relative pathname must
be specified. Absolute pathnames begin with '/'. Relative pathnames
begin with '.'.
ISRU715 File exists - The specified file already exists in the file
system. User responseChange the name of the file you are attempting to create. ISRU716 Not a directory - Either a node specified in the new pathname
is not a directory, or the file to be renamed is a directory and the
new file is not a directory. ExplanationEither a node within the new pathname is for a directory that does not exist or it refers to a file that is not a directory and the file to be renamed is a directory. User responseCorrect the new pathname to specify a directory that exists. ISRU717 File not found - The specified file or a directory in the
pathname was not found. The pathname is aaaaaaaa bytes
long. ExplanationThe pathname specified a file or directory that does not exist. User responseCorrect the pathname to specify an existing file or directory. ISRU718 Invalid command - The command entered is not valid for the z/OS UNIX Directory
List Utility. ExplanationA command was entered that is not supported by the z/OS UNIX Directory List Utility. User responseEnter a valid directory list primary command: EDIT, FIND/RFIND, LEFT/RIGHT, LOCATE, REFRESH, RESET, SAVE, or SORT. ISRU719 File not deleted - The delete request for the file was canceled
by the user. ExplanationThe file was not deleted. The confirmation of the file delete was canceled. ISRU720 OGET failed, rc=aaaaaaaa - The call to
OGET for the Copy command failed with return code aaaaaaaa.. ExplanationOGET experienced a problem processing the Copy command. Programmer responseCheck for error messages issued by OGET. If you did not receive any messages, ensure you have your TSO environment set up to receive write-to-programmer messages by issuing the command 'TSO PROFILE WTPMSG'. ISRU721 OPUT failed, rc=aaaaaaaa - The call to
OPUT for the Replace command failed with return code aaaaaaaa.. ExplanationOPUT experienced a problem processing the Replace command. Programmer responseCheck for error messages issued by OPUT. If you did not receive any messages, ensure you have your TSO environment set up to receive write-to-programmer messages by issuing the command 'TSO PROFILE WTPMSG'. ISRU722 Invalid Member Name - The member name specified is invalid
because it contains the pattern matching characters '*' or '%'. ExplanationA fully qualified member name must be specified. Member name pattern matching is not supported for this field. User responseRemove the pattern matching characters '*' or '%' from the member name. ISRU723 File not copied - The request to copy the file to an existing
target was canceled by the user. ExplanationThe file was not copied to the target. The confirmation of the file copy was canceled. ISRU724 No files to copy - The selected directory does not contain
any regular files eligible to be copied to the target data set. ExplanationWhen copying the contents of a directory to a partitioned data set, only regular files with filenames less than 9 characters in length and valid as member names are copied into the data set. The selected directory did not contain any such regular files. ISRU725 No files copied - No files were selected for copying on the
copy selection list display.
ISRU726 Copy selection canceled - The cancel command was entered
on the copy selection display. No files have been copied to the target
data set.
ISRU727 Target not found - The data set specified as the target for
the copy does not exists. ExplanationA catalog search failed to find the data set specified as the target for the copy. User responseCreate the specified data set or specify an existing data set. ISRU728 Data set not partitioned - The data set specified as the
target for the copy is not a partitioned data set. ExplanationA non-partitioned data set has been specified as the target for the directory copy. A partitioned data set must be specified. User responseSpecify a partitioned data set as the target for the directory copy. ISRU729 No members to copy - The specified partitioned data set does
not contain any members to be copied to the selected directory.
ISRU730 Directory list printed - The directory listing was written
to the ISPF list data set. ExplanationThis is an informational message. Option P on the z/OS UNIX Directory List Utility entry panel or the directory list SAVE primary command was successfully processed and the requested information has been written to the ISPF list data set. ISRU731 List-id too long - The list-id must be less than or equal
to 8 characters in length. ExplanationThe z/OS UNIX Directory List Utility SAVE command was invoked with a list-id parameter, indicating that the directory list information should be written to a data set. The list-id parameter, used as the middle qualifier of the data set, did not conform to ISPF naming conventions. User responseCorrect the specified parameter and reenter the command. The parameter specified must be 1-8 characters in length; start with an alphabetic character, @, #, or $; and all remaining characters must be alphabetic, numeric, @, #, $, or X'CO'(right brace). ISRU732 Invalid list-id - "aaaaaaaa" contains
invalid characters. ExplanationThe z/OS UNIX Directory List Utility SAVE command was invoked with a list-id parameter, indicating that the data set list information should be written to a data set. The list-id parameter, used as the middle qualifier of the data set, did not conform to ISPF naming conventions. User responseCorrect the specified parameter and reenter the command. The parameter specified must be 1-8 characters in length; start with an alphabetic character, or @, #, or $; and all remaining characters must be alphabetic, numeric, or @, #, $, or X'CO'(right brace). ISRU733 Data set in use - Data set is being updated by you. ExplanationThe z/OS UNIX Directory List Utility could not get an exclusive ENQ on the target data set for the SAVE command (userid.list-id.DIRLIST) because you are currently using it. User responseIf you are using the data set on another logical screen through a PDF function or local dialog, exit the function or dialog to free the data set. If you cannot determine why the data set is in use, exit and reenter ISPF and retry the function. If this doesn't work, log off, log back on, and retry. ISRU734 List not printed - The list data set for the z/OS UNIX Directory
List Utility SAVE command must be a sequential data set with logical
record length greater than or equal to 150 for RECFM F and greater
than or equal to 154 for RECFM V. ExplanationThe z/OS UNIX Directory List Utility SAVE command was invoked with a list-id parameter, indicating that the data set list information should be written to a data set named userid.list-id.DIRLIST. If this data set already exists, it must be a sequential data set with logical record length greater than or equal to 150 for RECFM F and greater than or equal to 154 for RECFM V. User responseUse a different list-id to have ISPF write the data set list information to another data set, or delete and reallocate the existing data set to have the proper characteristics. ISRU735 I/O error - An I/O error was encountered while saving the
directory list to data set aaaaaaaa.. ExplanationWhile processing the z/OS UNIX Directory List Utility SAVE command, an I/O error occurred writing a record to the requested data set aaaaaaaa.. System programmer responseVerify that the data set is functional. ISRU736 Directory list saved - The directory list has been successfully
written to data set aaaaaaaa.. ExplanationThis is an informational message. The z/OS UNIX Directory List Utility SAVE primary command was entered specifyinga list-id. The command was successfully processed and the requested information has been written to the data set aaaaaaaa.. ISRU737 Directory not deleted - The delete request for the directory
was not completed. A confirmation of a file or subdirectory delete
was cancel ed. ExplanationThe directory was not deleted. The user canceled out of a panel displayed to confirm the deletion of a file or subdirectory. ISRU738 Permission denied - You do not have the necessary permission
to remove the directory. Enter HELP to identify the directory that
could not be removed. ExplanationOne of these conditions exist:
User responseCheck with your z/OS UNIX system administrator to see if the directory permissions can be altered to allow you to remove the directory. ISRU739 Directory not empty - The directory could not be removed
because it still contains files and subdirectories. Enter HELP to
identify the directory that could not be removed. ExplanationISPF was unable to delete the files and subdirectories contained within the directory. The likely cause is that you do not have the necessary permission to work with this directory. User responseCheck with your z/OS UNIX system administrator to see if the directory permissions can be altered to allow you to delete contained files and subdirectories. ISRU740 Enter character string - Enter the string of characters to
be found. ExplanationThe FIND command was entered on a z/OS UNIX directory list, but no parameter was specified to indicate what the search target was. User responseSpecify a target string on the FIND command. ISRU741 Invalid string type - z/OS UNIX directory list FIND command
does not process picture (P'...'), hex (X'...'), text (T'...') or
char (C'...') strings. ExplanationThe z/OS UNIX directory list FIND command
does not support all of the keywords supported by the editor FIND
command. These are not supported:
User responseRemove the unsupported keyword and reenter the command. ISRU742 Put string in quotes - Put quotes (' ') around the string
of characters to be found. ExplanationThe FIND command was entered, passing multiple words as parameters that were not recognized as valid keywords. It is assumed that the words were intended to be an argument to the FIND command and, if so, must be enclosed in quotation marks. User responseAdd quotation marks around the string and retry the command. ISRU743 Invalid keyword - The keywords 'aaaaaaaa'
and 'bbbbbbbb' cannot both be used. Delete one. ExplanationThe FIND command was entered, passing conflicting
keywords. Only one of these keywords may be specified. Two types
of keywords are supported by the FIND command: direction keywords
and type keywords. No more than one of each type of keyword may be
specified on the FIND command. The keywords are:
The defaults are NEXT and CHARS User responseCorrect the keywords specified and retry the command. ISRU744 Invalid keyword - Check spelling of keywords used with the
FIND command. ExplanationThe FIND command was entered, passing a quoted string as the target string to find, but an additional parameter was specified that was not recognized at a valid FIND keyword. Valid keywords are: ALL, FIRST, LAST, NEXT, PREV, CHARS, PREFIX, SUFFIX, and WORD. User responseCorrect the specified keyword and retry the command. ISRU745 Put string in quotes - Put quotes (' ') around the string
of characters to be found. ExplanationThe FIND command was entered, passing multiple words as parameters that were not recognized as valid keywords. It is assumed that the words were intended to be an argument to the FIND command and, if so, must be enclosed in quotation marks. System programmer responseVerify that the data set is functional. User responseAdd quotation marks around the string and retry the command. ISRU746 Enter character string - A character string for FIND has
not been entered (so * is invalid). ExplanationAn asterisk (*) used as the target string of the FIND command indicates that the previous target string should be reused. An asterisk was entered but no previously entered a valid target string was found, making the use of the asterisk invalid. User responseEnter a valid target string. Once a target string is entered, the asterisk may then be used on subsequent FIND commands. ISRU747 FIND string too long - The FIND string cannot be longer than
44 characters. ExplanationThe FIND command searches for the specified target string within the list of filenames. Since the maximum length of a filename in the list is 255 characters, the target string may not exceed 255 characters. User responseRetry the command, entering a target string that is equal to or less than 255 characters in length. ISRU748 Invalid character string - The FIND string cannot be a null
('') string. ExplanationThe FIND target string must be a minimum of 1 character in length. A target string of 0 characters was entered. User responseRetry the command, entering a target string that is equal to or greater than 1 character in length. ISRU749 Enter a FIND command - The RFIND key works only after a FIND
character string is entered. ExplanationThe RFIND command reissues the last FIND command that was entered. RFIND cannot be issued until at least one FIND command has been processed. User responseEnter a valid FIND command. Once entered, the RFIND command may be used to reissue the same FIND command. ISRU750 TBSKIP failure - Return code aaaa received
from TBSKIP command. ExplanationThe z/OS UNIX directory list processor encountered an internal error while invoking the TBSKIP service. System programmer responseContact IBM support. ISRU751 Invalid LOCATE operand - Table is sorted by aaaaaaaa.
Operand is not a valid fixed value. ExplanationAn invalid LOCATE string was entered. User responseEnter a valid search string. ISRU752 LOCATE search error - Return code - aaaaaaaa -
received while searching table. ExplanationA return code greater than 8 was received from the TBSKIP service. User responseLog off, log back on, and retry. If the error persists, contact the system programmer. ISRU753 aaaa - bbb(255) - bbb(255) found
on aaaa line(s) ExplanationThis is an informational message. A FIND ALL command was entered on a data set list, and the specified target string was successfully located. ISRU754 aaa(255) found - Search for aaa(255) was
successful. ExplanationThis is an informational message. A FIND command was entered on a data set list, and the string was successfully located. User responseCorrect the specified keyword and retry the command. ISRU755 *Bottom of list reached* - aaa(255) not
found. Press the RFIND key to continue the search from the top for
the directory list. ExplanationThis is an informational message. The z/OS UNIX directory list FIND command searches from the top of the displayed data to the bottom of the list to find the target string. FIND has searched and reached the bottom of that list without finding the target string. Entering the RFIND command continues the search, starting from the top of the directory list. ISRU756 * Top of list reached * - aaa(255) not
found. Press the RFIND key to continue the search from the bottom
for the directory list. ExplanationThis is an informational message. When the PREV keyword is specified, the z/OS UNIX directory list FIND command searches from the top of the displayed data to the top of the list to find the target string. FIND has searched and reached the top of that list without finding the target string. Entering the RFIND command continues the search, starting from the bottom of the directory list. User responseEnter a valid target string. Once a target string is entered, the asterisk may then be used on subsequent FIND commands. ISRU757 No aaa(255) found - aaa(255) -
not found in any filenames. ExplanationThis is an informational message. A FIND or RFIND command was entered to cause the directory list processor to search the entire directory list for the specified target string. The search was completed, but the target string was not found. ISRU758 Mode fields changed - The requested modifications have been
made to the mode fields for the z/OS UNIX file.
ISRU759 Permission denied - You are not the owner of the file nor
do you have the privileges to change the mode fields. ExplanationYou are not permitted to change the mode fields for the file as you are not the owner of the file nor do you have the appropriate privileges. User responseRequest the owner of the file make the required changes to the mode fields or check with your z/OS UNIX system administrator to see if you can be granted the privileges required to update the mode fields. ISRU760 Extended attrs changed - The requested modifications have
been made to the extended attributes for the z/OS UNIX file.
ISRU761 Permission denied - You do not have the appropriate privileges
required to change the extended attributes for the file. ExplanationOne of these is true:
User responseCheck with the file owner or your z/OS UNIX system administrator to see if you can be granted the required privileges. ISRU762 Not a regular file - The MX (Modify Extended Attributes)
line command can only be used against a regular file. ExplanationThe MX (Modify Extended Attributes) line command is only valid when entered against a regular file. Extended attributes are only relevant for regular files. ISRU763 Invalid file type - The CO (Copy Out) and CI (Copy In) commands
are only valid for regular files and directories. ExplanationThe file you selected to copy out or in is not a regular file or directory. ISRU764 Invalid file type - The MM (Modify Mode) line command cannot
be entered against a symbolic link. ExplanationThe MM (Modify Mode) line command cannot be used to change the mode fields for a symbolic link. ISRU765 Command failed - Command 'aaaaaaaa' not
found, invalid, or issued return code 20. ExplanationThe command that was issued did not process. Either the command was not found, the command was invalid, or the command issued a return code of 20. User responseReenter a valid command. ISRU766 Command failed - Command 'aaaaaaaa' issued
return code bbbbbbbb. ExplanationThe command failed with the issued return code. User responseReenter a valid command. ISRU767 Invalid SORT operand - 'aaaaaaaa' is not
a valid SORT operand. ExplanationAn invalid SORT operand has been entered. User responseCorrect the SORT operand and retry the command. ISRU768 Too many sort fields - You may specify up to two fields for
use with the SORT command. ExplanationToo many SORT operands have been entered for the SORT command. A maximum of two operands can be entered per SORT command. User responseCorrect the number of SORT operands. ISRU769 SORT error - Error return from table sort = aaaaaaaa. ExplanationThis message is self explanatory. Problem determinationA table sort error has occurred on an internal sort routine. ISRU770 Source not found - The data set specified as the source for
the copy does not exists. ExplanationA catalog search failed to find the data set specified as the source for the copy. User responseEnsure you specify an existing partitioned data set. ISRU771 Not a regular file - The file specified as the target of
the copy exists but it is not a regular file. ExplanationWhen copying data from a regular file, the target can only be a sequential data set, a member of an existing partitioned data set, or a regular file. User responseEnsure you specify the pathname for a new or existing regular file. ISRU772 Incorrect file type - The new pathname specified is the pathname
for an existing file but it is a different file type to the file being
renamed. ExplanationA file can be renamed to the pathname of an existing file but that file must have the same file type as the file being renamed. User responseEnsure you specify either a unique pathname or the pathname of a file that is of the same file type as the file being renamed. ISRU773 Invalid record length - The record length specified with
the E (edit) or B (browse) line command is not a valid numeric value. ExplanationThe record length specified with the E (edit) or B (browse) line command must be a numeric value. For browse, it must be a value between 0 and 32760. For edit, it must be a value between 0 and 8192. User responseEnsure you specify a valid record length value with the edit or browse line command. ISRU774 Invalid scroll amount - Valid: M (MAX), P (PAGE), or a numeric
value for the number of columns to scroll. ExplanationAn invalid scroll amount has been specified. User responseEnter one of the valid responses listed in the Help message, either - M (MAX), P (PAGE), or a numeric value for the number of columns to scroll. ISRU775 Symbolic link loop - z/OS UNIX detected a loop while processing
symbolic links for the pathname. ExplanationA loop exists in symbolic links that were encountered during resolution of the Pathname. Problem determinationFollow the symbolic links for the Pathname to determine where the loop is defined. ISRU776 Pathname too long - Either the pathname is longer than 1023
characters, or a component of the pathname is longer than 255 characters. ExplanationThe specified pathname or a component of that pathname is too long and filename truncation is not supported. User responseCorrect the specified pathname. Problem determinationFollow the symbolic links for the Pathname to determine where the loop is defined. ISRU777 File system is read-only - An attempt was made to modify
a file on a file system that is read-only. ExplanationYou are attempting to modify a file in a file system that has been mounted in read-only mode. User responseCheck with the system programmer to determine why the file system is in read-only mode. Problem determinationFollow the symbolic links for the Pathname to determine where the loop is defined. ISRU778 Some component of the pathname is not a directory. ExplanationA component of the pathname specified identifies a file that is not a directory. User responseCorrect the pathname so it specifies the directory containing the file you want to process. Problem determinationFollow the symbolic links for the Pathname to determine where the loop is defined. ISRU779 Permission denied - You do not have the necessary permission
to process the z/OS UNIX file. ExplanationOne of these conditions may exist:
User responseCheck with the file owner or your z/OS UNIX system administrator to see if you can be granted permission to search the directory. Problem determinationFollow the symbolic links for the Pathname to determine where the loop is defined. ISRU780 Unable to initialize Language Environment. Dates
and times displayed in the directory list have been calculated using
the operating system GMT offset rather than using the setting for
the time zone environment variable. ExplanationISPF uses C functions to calculate the directory list data and time values based on the time zone environment variable setting. Initialization of Language Environment® and the C run-time failed so ISPF is unable to use these C functions. As an alternative, ISPF uses the operating system GMT offset to calculate the displayed dates and times. User responseTry to determine why the Language Environment and C run-time could not be initialized. Possible causes are: (1) The LE run-time library data set CEE.SCEERUN is not in STEPLIB or LNKLST. (2) Insufficient virtual storage to initialize LE and the C run-time. Check to see if the LE run-time library data set CEE.SCEERUN is in STEPLIB or LNKLST. If so, try logging on to TSO with a larger region size. ISRU781 Running shell command: aaaaaaaa. PID=bbbbbbbb. ExplanationThis message is displayed while waiting on the completion of a process executing a z/OS UNIX Directory List line command within the z/OS UNIX login shell. The message identifies the command and the Id of the z/OS UNIX process. ISRU782 Running direct command: aaaaaaaa. PID=bbbbbbbb. ExplanationThis message is displayed while waiting on the completion of a process executing a z/OS UNIX Directory List line command directly within z/OS UNIX. The message identifies the command and the Id of the z/OS UNIX process. ISRU783 File not found - The file specified to be run could not be
found. ExplanationOne or more components of the pathname for the file to be run were not found. User responseCorrect the pathname for the file to be run. ISRU784 Permission denied - You do not have the necessary permission
to run the specified file. ExplanationOne of these may be the cause:
User responseCheck with your z/OS UNIX system administrator to see if the directory or file permissions can be altered to allow you to run the file. ISRU785 Invalid file type - Running of z/OS UNIX commands, TSO commands, CLISTs,
and REXX execs is only supported against regular files and directories. ExplanationThe file you selected to run a command against is not a regular file or directory. User responseIssue the command against a regular file or directory. ISRU786 Enter 2nd operand - A second operand is required for the
LOCATE command. ExplanationThe LOCATE command requires that a search string be entered. User responseReissue the command with a search string. ISRU787 Not an executable file - The selected file is not in a format
that allows it to be executed. ExplanationThe selected file has execute permission, but it is not in the proper format to be a process image file. User responseReissue the command against an executable file. ISRU788 Cannot link to directory - A hard link cannot be created
to a directory. ExplanationAn attempt was made to create a hard link to directory. Hard links to directories are not supported. User responseSpecify the pathname for a file that is not a directory. ISRU789 Invalid new pathname - The new pathname is invalid because
the old pathname is in the prefix for the new pathname. ExplanationThe old pathname cannot be part of the prefix of the new pathname when renaming a file. User responseCorrect the new pathname so that it does not include the old pathname. ISRU790 UIDs changed - The real and effective UIDs have been changed. ExplanationThe request to change the real and effective UIDs was successful. ISRU791 Permission denied - You do not have the appropriate privileges
required to switch to this UID. ExplanationIf attempting to switch to superuser mode (UID 0) then you do not have permission to the BPX.SUPERUSER RACF facility class. User responseContact your security administrator to see if you can be granted permission to the BPX.SUPERUSER RACF facility class. ISRU792 Cannot resolve pathname - ISPF was unable to determine the
pathname for the currently listed directory. ExplanationA + (plus) was specified as the first character in a pathname to represent the pathname of the directory currently listed. ISPF was unable to obtain the pathname for the currently listed directory. ISRU793 Record length rejected - The file being browsed was created
with FILEDATA=RECORD so the record length provided by the user was
not used. ExplanationAttempting to browse a UNIX file created with FILEDATA=RECORD using a different record length would produce erroneous results, so ISPF does not permit a user specified record length. User responseRemove the record length from the BROWSE request. ISRU794 Record length rejected - The file being edited or viewed
was created with FILEDATA=RECORD so the record length provided by
the user was not used. ExplanationAttempting to edit or view a UNIX file created with FILEDATA=RECORD using a different record length would produce erroneous results, so ISPF does not permit a user specified record length. User responseRemove the record length from the EDIT or VIEW request. ISRU795 No files found - No files or directories were found using
the pattern entered. ExplanationISPF detected a valid Unix file pattern but did not find any files matching the pattern. User responseCorrect the pattern using valid Unix file name charcters as well as the glob characters ?, ., *, Ý and ¨. Additionally, check that you have read access to files or directories that match the pattern. ISRU799 File name aaaaaaaa was not found. Trying bbbbbbbb. ExplanationAn attempt to access the file failed. This could have been due to the command field being defined as CAPS(ON) resulting in conversion of the file name to uppercase. ISPF has tried to access the file again with the file name converted to lowercase. ISRU800 Unexpected error from call to aaaaaaaa in bbbbbbbb;
Error: cccccccc dddddddd Reason: eeeeeeee ffffffff ExplanationAn unexpected error was returned by a call to z/OS UNIX system service aaaaaaaa from ISPF module bbbbbbbb. Programmer responseRefer to the z/OS UNIX System Services Programming: Assembler Callable Services Reference and z/OS UNIX System Services Messages and Codes manuals for descriptions of the error and reason codes. ISRU801 Invalid PATH parameter - The variable specified with the
PATH parameter was not found or is invalid. ExplanationEither the variable was not found, a value was not specified for the variable, the value was too large for a pathname, or the name of the variable is invalid. Programmer responseSpecify the name of a variable containing a pathname with the PATH parameter. ISRU802 Invalid CONFIRM value - Specify either YES or NO. ExplanationFor the DIRLIST service, the only valid values for the CONFIRM parameter are YES or NO. Programmer responseUse YES or NO with the CONFIRM parameter. ISRU803 Invalid CONFDRD value - Specify either YES or NO. ExplanationFor the DIRLIST service, the only valid values for the CONFDRD parameter are YES or NO. Programmer responseUse YES or NO with the CONFDRD parameter. ISRU804 COLS values not paired - An odd number of values was specified
with the COLS parameter on a call to DIRLIST. A column/width pair
is not valid. ExplanationThe DIRLIST COLS parameter requires pairs of column and width values to be specified. An odd number of values was specified indicating a column/width pair was not specified correctly. Programmer responseSpecify a valid column name. ISRU805 Invalid column name - The column name aaaaaaaa specified
with the COLS parameter on the call to DIRLIST is not valid. ExplanationThe abbreviated column name values that can be specified with the DIRLIST COLS parameter are: TY, PE, AU, EX, FM, OW, GR, LI, SZ, MO, CH, AC, and CR. Programmer responseSpecify a valid column name. ISRU806 Invalid column width - The column width value aaaaaaaa is
not a numeric value. ExplanationA column width value specified with the DIRLIST COLS parameter is not numeric. Programmer responseSpecify a valid column name. ISRU807 Duplicate column - The abbreviated column name aaaaaaaa has
already been specified with the COLS parameter on the call to DIRLIST. ExplanationThe abbreviated column name aaaaaaaa is specified more than once with the DIRLIST COLS parameter. Programmer responseRemove the duplicated column names. ISRU808 Invalid FROM parameter - The variable specified with the
FROM parameter was not found or is invalid. ExplanationEither the variable was not found, a value was not specified for the variable, the value was too large for a filename, or the name of the variable is invalid. Programmer responseSpecify the name of a variable containing a filename with the FROM parameter or omit the parameter. ISRU810 Column width too large - The column width aaaaaaaa specified
with the COLS parameter on the call to DIRLIST is larger than the
maximum value bbbbbbbb allowed for column cccccccc. ExplanationThe column width specified is larger tha the maximum column width supported for this column. Programmer responseSpecify a column width that is not greater than the maximum supported value. ISRU811 Command name is invalid - The name 'aaaaaaaa'
specified as the line command processor with the LCMDS parameter on
the call to DIRLIST is not valid as a command name. ExplanationThe name specified is not valid for a command name. Valid command names have 8 characters or fewer, start with an alphabetic or national character, and may have alphabetic characters, national characters, or numeric digits after the first character. Programmer responseCorrect the line command processor name specified with the LCMDS parameter on the call to DIRLIST. ISRU812 Line command failed - Line command processor 'aaaaaaaa'
issued return code bbbbbbbb for line command cccccccc. ExplanationThe line command processor aaaaaaaa specified on the call to ISRLUDSP failed line command cccccccc with return code bbbbbbbb. Programmer responseCheck the logic for the line command processor to determine the reason the freturn code was set for the line command. ISRU813 Invalid FIXCOLS value - Specify either YES or NO. ExplanationFor the DIRLIST service, the only valid values for the FIXCOLS parameter are YES or NO. Programmer responseUse YES or NO with the FIXCOLS parameter. ISRU814 Columns are fixed - The column arrangement cannot be altered
for this directory list display. ExplanationThis directory list was invoked through a call to the DIRLIST service. The caller of DIRLIST specified a value of YES for the FIXCOLS parameter. This requests that the user be prevented from changing the column arrangement. ISRU815 Panel name is invalid - The name 'aaaaaaaa'
specified as the directory list panel with the PANEL parameter on
the call to DIRLIST is not valid as a panel name. ExplanationThe name specified is not valid for a panel name. Valid panel names have 8 characters or fewer, start with an alphabetic or national character, and may have alphabetic characters, national characters, or numeric digits after the first character. Programmer responseCorrect the directory list panel name specified with the PANEL parameter on the call to DIRLIST. ISRU820 Invalid file type - The MO (Modify Owner) line command cannot
be entered against a symbolic link. ExplanationThe MO (Modify Owner) line command cannot be used to change the owning user for a symbolic link. ISRU821 Invalid file type - The MG (Modify Group) line command cannot
be entered against a symbolic link. ExplanationThe MG (Modify Group) line command cannot be used to change the owning group for a symbolic link. ISRU822 Invalid UID - The owner UID specified is invalid or does
not exist. ExplanationThe value entered for the UID is not numeric, in the range 1 to 2147483647 or is not an existing UID. Programmer responseEnter the value of a valid UID. ISRU823 Permission denied - You do not have the necessary permission
to change the owner of the file. ExplanationTo change the UID of the file one of the following
must be true:
Programmer responseCheck with the z/OS UNIX system administrator to see if you can be given the authority to change the UID of the file. ISRU824 Invalid user ID - The user ID is not defined to use z/OS UNIX. ExplanationThe user ID specified has not be defined in your security data base to use z/OS UNIX. Programmer responseCheck with the z/OS UNIX system administrator to see if the user ID should be defined in your security data base to use z/OS UNIX. ISRU825 File owner changed - The owner UID for the file has been
successfully changed.
ISRU826 Invalid GID - The owner GID specified is invalid or does
not exist. ExplanationThe value entered for the GID is not numeric, in the range 1 to 2147483647 or is not an existing GID. Programmer responseEnter the value of a valid GID. ISRU827 Permission denied - You do not have the necessary permission
to change the owner of the file. ExplanationTo change the GID of the file one of the following
must be true:
If you are the owner of the file, you can change the group to your group or to any of your supplementary groups. Programmer responseCheck with the z/OS UNIX system administrator to see if you can be given the authority to change the GID of the file. ISRU828 Invalid group ID - The group ID is not defined to use z/OS UNIX. ExplanationThe group ID specified has not be defined in your security data base to use z/OS UNIX. Programmer responseCheck with the z/OS UNIX system administrator to see if the group ID should be defined in your security data base to use z/OS UNIX. ISRU829 Owning group changed - The owning group ID for the file has
been successfully changed.
ISRU830 Invalid file type - The MF (Modify Format) line command cannot
be entered against a symbolic link. ExplanationThe MF (Modify Format) line command cannot be used to change the format or file tag information for a symbolic link. ISRU831 Format changed - The file format and/or the file tag data
was successfully changed.
ISRU832 Permission denied - You do not have the necessary permission
to change the format or tag data for the file. ExplanationTo change the file format one of the following
must be true:
Programmer responseCheck with the z/OS UNIX system administrator to see if you can be given the authority to change the file format and/or tag information. ISRU833 Invalid file type - The UA (User Auditing) and AA (Auditor
Auditing) line commands cannot be entered against a symbolic link. ExplanationThe UA (User Auditing) and AA (Auditor Auditing) line commands cannot be used to change the user auditing and auditor auditing options for a symbolic link. ISRU834 Auditing changed - The user auditing settings for the file
were successfully changed.
ISRU835 Permission denied - You do not have the necessary permission
to change the user auditing settings for the file. ExplanationTo change the user auditing settings one of the
following must be true:
Programmer responseCheck with the z/OS UNIX system administrator to see if you can be given the authority to change the user auditing settings for the file. ISRU836 Auditing changed - The auditor auditing settings for the
file were successfully changed.
ISRU837 Permission denied - You do not have the necessary permission
to change the auditor auditing settings for the file. ExplanationTo change the auditor auditing settings you must be defined with AUDITOR authority in you security system. Programmer responseCheck with the z/OS UNIX system administrator to see if you can be given AUDITOR authority. ISRU838 Invalid file type - The FS (File System) line command is
not valid for a FIFO or character special file. ExplanationFile system information is not valid for FIFO and character special files. ISRV000 Invalid combination - You have selected Allocate Multiple
Volumes. The directory blocks field must be zero and the data set
name type must be blank to allocate a multivolume data set. Multivolume
data sets are sequential data sets. ExplanationThe directory blocks field must be 0 to allocate a multivolume data set. Multivolume data sets are sequential data sets. User responseEither change the directory block field to 0, the data set name type field to blank, or blank out the field to allocate multivolume data sets. ISRV001 Duplicate volumes - Duplicate volumes have been entered for
multivolume allocation. Correct or remove the duplicate volume. ExplanationAn attempt to allocate a multivolume data set has been made using the volume name of a volume that has been already entered. User responseCorrect or remove the duplicate volume name. ISRV002 More than 59 volumes - ISPF does not support multivolume
data sets with more than 59 volumes. Information is displayed about
the first 59 volumes. ExplanationThis is an informational message. The multivolume data set contains more than 59 volumes. ISPF supports up to 59 volumes for a multivolume data set. The information displayed is for the first 59 volumes. ISRV003 Invalid multivolume cmd - The data set that this command
has been issued against is a multivolume data set. The command is
invalid for multivolume data sets. ExplanationThis is an informational message. The data set that this command has been issued against is a multivolume data set. The command is invalid for multivolume data sets. ISRV004 Invalid multivolume cmd - The data set that this command
has been issued against is a multivolume data set. The command is
invalid for multivolume data sets that are displayed using a VTOC
list. ExplanationThe data set that this command has been issued against is a multivolume data set. The command is invalid for multivolume data sets that are displayed using a VTOC list. User responseRemove the volume name from the Volume Serial field and reissue the command. ISRV005 Invalid multivolume cmd - The data set that this command
has been issued against is a multiple volume data set. The command
is invalid for a multivolume data set using the volume serial. ExplanationThe data set that this command has been issued against is a multivolume data set. The command is invalid for multivolume data sets using the volume serial. User responseRemove the volume name from the Volume Serial field and reissue the command. ISRV006 Multivolume data set - The data set that is being edited
is a multivolume data set. Edit does not support the input of a volume
in the Volume Serial field for multivolume data sets. ExplanationThe data set that is being edited is a multivolume data set. Edit does not support the ability to edit data on one volume of a multivolume data set. User responseRemove the volume name from the Volume Serial field when you are attempting to edit a multivolume data set. ISRV007 Volume ignored - The data set that is being viewed is a multivolume
data set. The volume entered was ignored. All of the data set can
be viewed, not just one volume's data. If you wish to see the data
on one volume only, use browse instead of view. ExplanationFor a multivolume data set, view always allocates all volumes even when a specific volume is specified. The data presented begins with volume one. ISRV008 Volume ignored - This data set is an SMS managed multivolume
data set. The volume entered was ignored. You cannot allocate just
one volume of an SMS managed multivolume data set. The data displayed
begins with volume one. ExplanationFor an SMS managed multivolume data set, you cannot allocate just one volume's worth of data. The whole data set is allocated and the display begins with the data on volume one. ISRV009 More than 59 volumes - ISPF does not allow allocation of
a multivolume data set to more than 59 volumes. ExplanationThe maximum number allowed for the number of volumes is 59. ISRVI000 View length not allowed - View length not allowed when processing
View Recovery ExplanationView length is specified for the VIIF service. This is not allowed when processing view recovery. User responseContact the responsible programmer. Programmer responseBlank out the view length from the EDIREC service. ISRVI001 Missing record format - Specify the record format F or V
for VIIF. ExplanationThe required record format parameter for the VIIF service is not specified. User responseContact the responsible programmer. Programmer responseSpecify either F or V for the record format parameter for the VIIF service. ISRVI002 Missing record length - Specify a record length greater than
9 and less than 32761 for fixed record length data sets and less than
32757 for variable length data sets. ExplanationThe required record length parameter for the VIIF service is not specified. User responseContact the responsible programmer. Programmer responseSpecify a record length greater than 9 and less than 32761 for fixed record length data sets and less than 32757 for variable length data sets. ISRVI003 Missing profile name - Specify the profile name for VIIF. ExplanationThe required profile name parameter for the VIIF service is not specified. User responseContact the responsible programmer. Programmer responseSpecify the profile name for the VIIF service. ISRVI004 Invalid view length - The view length must be less than or
equal to the record length. ExplanationAn invalid view length is specified for the VIIF service. User responseContact the responsible programmer. Programmer responseSpecify an view length less than or equal to the record length. ISRVI005 Conflicting options used - The view length and the format
are mutually exclusive. ExplanationConflicting options are specified for the VIIF service. The view length and the format cannot be used simultaneously. User responseContact the responsible programmer. Programmer responseBlank out one of the conflicting options. ISRVI006 Recovery is not pending - The view recovery cannot proceed
when recovery is not pending. ExplanationA view recovery is requested while recovery is not pending User responseContact the responsible programmer. Programmer responseCorrect the recovery-request option for the VIIF service. ISRVI007 Invalid view length - The value of data to be viewed must
have a length between 10 and 32760. ExplanationAn invalid view length is specified for the VIIF service. User responseContact the responsible programmer. Programmer responseSpecify the view length with a value between 10 and 32760 for the VIIF service. ISRVI008 aaaaaaaa not allowed - aaaaaaaa name
not allowed when processing View Recovery. Explanationaaaaaaaa name is specified for the VIIF service. This is not allowed when processing View Recovery. User responseContact the responsible programmer. Programmer responseBlank out the aaaaaaaa name from the EDIREC service. ISRVI009 Mixed mode not allowed - Mixed mode not allowed when processing
View Recovery. ExplanationMixed mode is specified for the VIIF service. This is not allowed when processing view recovery. User responseContact the responsible programmer. Programmer responseBlank out mixed mode from the EDIREC service. ISRX000 Unknown return code - The installation accounting exit issued
a return code of aaaa. ExplanationThe only valid return code from the installation exit is 0. User responseContact the responsible programmer. Programmer responseCorrect the exit so that it returns a return code of 0. ISRYM012 Invalid class - Enter a valid class option. "aaaaaaaa"
is invalid ExplanationThe value entered on the model class panel or on the edit primary MODEL CLASS command is not a valid model class. User responseSpecify a valid model class and retry the request. ISRYM013 Invalid option - Enter a valid option. "aaaaaaaa"
is invalid ExplanationAn invalid model (aaaaaaaa) was requested on one of the PDF edit language model panels. User responseSpecify a valid model and press Enter. ISRZ000 aaaaaaaa - bbbbbbbb ExplanationThis is an informational message. This message may be used if an error is returned from a PDF edit macro command. ISRZ001 aaaaaaaa - bbbbbbbb ExplanationThis is an informational message. This message may be used if an error is returned from a PDF edit macro command. ISRZ002 aaaaaaaa - bbbbbbbb ExplanationThis is an informational message. This message may be used if an error is returned from a PDF dialog service. Variable &ZERRMSG indicates the message ID that is the source of the message text for ISRZ002. ISRZ003 aaaaaaaa - bbbbbbbb ExplanationThis is an informational message. This message may be used if an error is returned from a PDF dialog service. Variable &ZERRMSG will indicate the message id that is the source of the message text for ISRZ003. |
Copyright IBM Corporation 1990, 2014
|