Professional Documents
Culture Documents
(ISPF) IBM
GC28-1326-04
Interactive System Productivity Facility (ISPF) IBM
GC28-1326-04
Note
Before using this document, read the general information under “Notices” on page 605.
If you would like a reply, be sure to include your name, address, telephone number, or FAX number.
Make sure to include the following in your comment or note:
Title and order number of this book
Page number or topic related to your comment
The ISPF development team maintains a site on the World-Wide Web. The URL for the site is:
http://www.software.ibm.com/ad/ispf
© Copyright International Business Machines Corporation 1980, 2000. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
What’s in the OS/390 V2R10.0 ISPF Return Codes from Terminating Dialogs . . . . 583
library? . . . . . . . . . . . . . . . v Return Codes from Termination Dialogs . . . 583
OS/390 V2R10.0 ISPF . . . . . . . . . . . v
Chapter 9. Diagnostic Tools and
Elements and Features in OS/390 . . . vii Information . . . . . . . . . . . . 585
ISPF Debug Tools . . . . . . . . . . . . 585
Preface . . . . . . . . . . . . . . . xi Diagnostic Information . . . . . . . . . . 585
Using the ENVIRON System Command . . . 586
About This Book . . . . . . . . . . . . . xi
ENVIRON Command Syntax and Parameter
Who Should Use This Book . . . . . . . . . xi
Descriptions . . . . . . . . . . . . . 586
How to Use This Book . . . . . . . . . . . xi
Abend Panels Provide Diagnostic Information 592
ISPF Statistics Entry in a PDS Directory . . . 595
Chapter 1. ISPF Messages . . . . . . . 1 Common Problems Using ISPF . . . . . . . 595
Messages . . . . . . . . . . . . . . 595
Chapter 2. PDF Messages . . . . . . 203 Unexpected Output . . . . . . . . . . 597
Abend Codes and Information . . . . . . . 597
Chapter 3. SCLM Messages . . . . . 435 Terminal I/O Error Codes . . . . . . . . . 599
Register Linkage Conventions . . . . . . . . 600
Obtaining Message IDs . . . . . . . . . . 601
Chapter 4. Macro Messages (MNOTEs) 535
Installation, Maintenance, and Migration
Diagnostics . . . . . . . . . . . . . . 602
Chapter 5. Library Management Common Installation and Maintenance
Facility (LMF) Messages. . . . . . . 549 Problems . . . . . . . . . . . . . . 602
Migration from Version 2 and Version 3 to
Chapter 6. SuperC Messages . . . . 569 Version 4.1 . . . . . . . . . . . . . 603
The licensed books that were declassified in OS/390 Version 2 Release 4 appear on
the OS/390 Online Library Collection, SK2T-6700.
The remaining licensed books for OS/390 Version 2 appear on the OS/390
Licensed Product Library, LK2T-2499, in unencrypted form.
For more information about the MSGID command, refer to ISPF User’s Guide
Within each chapter, the messages are organized first alphabetically and then
numerically.
v A message explanation that states the reason for the message. Error message
explanations describe probable causes of the errors; warning message
explanations give an explanation of the warnings given; information message
explanations give information about tasks ISPF is performing.
v A user response, which gives return codes, describes possible causes of
problems, and discusses how to correct the problems. No user action is
necessary for information messages and so no response is given.
v A second-level response that a programmer, system programmer, or project
administrator (in SCLM only) can use to correct the problems discussed in the
message explanation. When no second-level action is necessary, no response is
given.
ISPA331 APL2 workspace error - Function: list all ISPA336 Invalid variable name - aaaaaaaa is not a
variables, return code: aaaaaaaa. valid variable name for both ISPF and
APL2.
Explanation: An error in the list all variables function
caused a program failure. Explanation: The variable name is invalid.
User Response: Contact the responsible programmer. User Response: Contact the responsible programmer.
Programmer Response: Verify that the APL program Programmer Response: Correct the variable name.
is coded correctly for this function. If the list all
variables function is coded correctly, contact the system
programmer.
System Programmer Response: This is a possible
ISPA337 APL2 function limit - An ISPF service ISPC003 ISPCNT error: RC =aaaaaaaa - SPF parm
may retrieve up to 64k bytes of APL2 data must have the keyword TKV in the
workspace data. 3-5 or 4-6 position.
Explanation: Storage for the program has been Explanation: The specified member is not a valid
exhausted. PARMS data set if the keyword TKV is missing or not
in the correct location.
User Response: Contact the responsible programmer.
User Response: Verify that the specified member
Programmer Response: Correct the program to
exists in the SPF PARMS data set. Browse the specified
prevent the storage error.
member to see if the TKV keyword is missing or in the
wrong position. Refer to ISPF Planning and Customizing
ISPA400 ISPAPTT dialog error - No parameter for more information on the ISPCNT program.
input was passed.
Explanation: The parameter did not include all of the ISPC004 ISPCNT error: RC =aaaaaaaa - Open
necessary inputs. failure, allocate ISPPARM ddname to a
SPF parms member.
User Response: Contact the responsible programmer.
Explanation: The OPEN FAILURE is issued for not
Programmer Response: Correct the parameters for the having allocated the SPF PARMS data set to the
terminal type. ddname ISPPARM prior to invoking ISPCNT.
User Response: Allocate the fully-qualified SPF
ISPA401 ISPAPTT dialog error - Unexpected PARMS data set to the ddname ISPPARM. Refer to
return code aaaaaaaa from service ISPF Planning and Customizing for more information on
bbbbbbbb. the ISPCNT program.
Explanation: The APL program was unsuccessful.
User Response: Contact the responsible programmer. ISPC010 ISPC010W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. The ″cccccccc=dddddddd″
Programmer Response: The service shown above attribute specification is not valid when
failed with the return code shown above. Verify that the ″eeeeeeee″ conversion option has been
the above service is coded correctly. If it is correct, specified. ″cccccccc=dddddddd″ will not be
contact the system programmer. used.
System Programmer Response: This is a possible Explanation: The eeeeeeee conversion option is in
system or internal error. If you do not have mixed conflict with the use of attribute cccccccc specified for
levels of ISPF code, contact IBM support. value dddddddd. The cccccccc attribute specification is
ignored.
ISPC001 ISPCNT error: RC =aaaaaaaa - Open User Response: Change the attribute value or change
failure, member does not exist in data the conversion utility option.
set.
Explanation: The SPF PARMS member specified does ISPC011 ISPC011W: Warning. Line aaaaaaaa of file
not exist in the SPF PARMS data set ″bbbbbbbb″. Previous ″cccccccc″ tag
User Response: Verify that the spelling of the SPF attribute was missing or not valid.
PARMS member is correct. Ensure that the member ″dddddddd″ tag will be ignored.
exists in in the SPF PARMS data set allocated to Explanation: The previous tag cccccccc has a missing
ddname ISPPARM. Refer to ISPF Planning and or invalid attribute. The current dddddddd tag cannot be
Customizing for more information on the ISPCNT processed and will be ignored.
program.
User Response: Review the ISPDTLC log to determine
the problem with the cccccccc tag. Correct the problem
ISPC002 ISPCNT error: RC =aaaaaaaa - The input and rerun the conversion utility.
data set is a partitioned data set. Specify
a member name.
Explanation: An existing member of the SPF PARMS
partitioned data set must be specified.
User Response: Verify that the name of the SPF
PARMS data set is correct and that an existing member
is specified. Refer to ISPF Planning and Customizing for
more information on the ISPCNT program.
ISPC012 ISPC012W: Warning. Line aaaaaaaa of file ISPC015A ISPC015AW: Warning. Line aaaaaaaa of
″bbbbbbbb″. cccccccc attribute has already file ″bbbbbbbb″. The cccccccc attribute is
been defined for the dddddddd tag. not valid when the dddddddd attribute is
cccccccc = ″eeeeeeee″ will be ignored and also specified. cccccccc will not be used.
the first setting will be used.
Explanation: There is a conflict in the specification of
Explanation: The cccccccc attribute has been previously attributes cccccccc and dddddddd. The dddddddd attribute
defined on the current dddddddd tag. Duplicate attribute will be used. The cccccccc attribute is ignored.
specifications are ignored.
User Response: Remove the cccccccc attribute
User Response: Provide only 1 specification for specification from the DTL source file.
attribute cccccccc.
ISPC016 ISPC016E: Error. Line aaaaaaaa of file
ISPC013 ISPC013W: Warning. Line aaaaaaaa of file ″bbbbbbbb″. The cccccccc tag can only be
″bbbbbbbb″. The ″cccccccc=dddddddd″ coded within a text string. The previous
attribute is not defined for the ″eeeeeeee″ tag has not been properly closed.
tag and will be ignored.
Explanation: The cccccccc tag can be used only within
Explanation: The cccccccc attribute is not valid for the the text part of the tag syntax following the ’>’ close
eeeeeeee tag. tag delimiter.
User Response: Remove the cccccccc attribute User Response: Make sure that the previous tag has
specification from the DTL source file. been closed with the ″>″ tag delimiter. Correct the DTL
source and rerun the conversion utility.
ISPC013A ISPC013AW: Warning. Line aaaaaaaa of
file ″bbbbbbbb″. The ″cccccccc″ attribute is ISPC017 ISPC017W: Warning. Line aaaaaaaa of file
not defined for the ″dddddddd″ tag and ″bbbbbbbb″. The cccccccc=″dddddddd″
will be ignored. attribute value is not supported in the
conversion process. The default value
Explanation: The cccccccc attribute is not valid for the
″eeeeeeee″ will be used.
dddddddd tag.
Explanation: The invalid value dddddddd has been
User Response: Remove the cccccccc attribute
specified for the cccccccc attribute. The conversion
specification from the DTL source file.
utility will use the default value eeeeeeee.
User Response: Correct the DTL source and rerun the
ISPC014 ISPC014W: Warning. Line aaaaaaaa of file
conversion utility.
″bbbbbbbb″. cccccccc attribute has already
been defined for the dddddddd tag. This
duplicate attribute specification will be ISPC018 ISPC018E: Error. Line aaaaaaaa of file
ignored. ″bbbbbbbb″. A required tag was not coded
under the cccccccc tag. One of the
Explanation: The cccccccc attribute has been previously
following tags is required to be coded
defined on the current dddddddd tag. Duplicate attribute
under the cccccccc tag: ″dddddddd″.
specifications are ignored.
Explanation: The cccccccc tag requires the use of at
User Response: Provide only 1 specification for
least one of the nested tags dddddddd.
attribute cccccccc.
User Response: Correct the DTL source and rerun the
conversion utility.
ISPC015 ISPC015W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. The cccccccc attribute is not
valid when the dddddddd attribute is also ISPC019 ISPC019E: Error. Line aaaaaaaa of file
specified. cccccccc=eeeeeeee will not be ″bbbbbbbb″. Required cccccccc attribute
used. was not specified or was not valid on
the dddddddd tag.
Explanation: There is a conflict in the specification of
attributes cccccccc and dddddddd. The dddddddd attribute Explanation: The dddddddd tag requires the
will be used. The cccccccc attribute is ignored. specification of attribute cccccccc tags dddddddd.
User Response: Remove the cccccccc attribute User Response: Correct the DTL source and rerun the
specification from the DTL source file. conversion utility.
ISPC020 ISPC020W: Warning. ISPDTLC Release ISPC028 ISPC028I: aaaaaaaa message(s) have been
aaaaaaaa for bbbbbbbb is being run on suppressed.
ISPF Release cccccccc for dddddddd.
Explanation: This is an informational message.
Results are not predictable.
Explanation: This message is self-explanatory.
ISPC028A ISPC028AI: Total of aaaaaaaa message(s)
User Response: Review the file allocations to make have been suppressed.
sure that the ISPDTLC is being run from the SYSEXEC
Explanation: This is an informational message.
or SYSPROC data set for the correct ISPF release.
ISPC035 ISPC035W: Warning. Line aaaaaaaa of file ISPC041 ISPC041W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. No declaration found for ″bbbbbbbb″. cccccccc tag cannot be coded
ENTITY ″cccccccc″. The variable cannot after previously coded dddddddd tag.
be substituted. (ENTITY definitions are cccccccc and its nested tags will be
case sensitive. Verify that the ignored.
entity-name definition matches the
Explanation: A tag was found that is not allowed after
entity reference.)
the previously coded tag. The tag, and any tags nested
Explanation: Variable substitution cannot be within, are ignored during the continuation of the
completed for variable cccccccc. conversion.
User Response: If the entity is defined, make sure that Programmer Response: Verify the valid nesting
the entity-name reference is the same case as the entity conditions and update the DTL source file.
declaration. If the variable cccccccc is a run-time
substitution variable, the coding can be specified as
ISPC042 ISPC042E: Error. Line aaaaaaaa of file
″&S3.″ to avoid this message. Correct the DTL source
″bbbbbbbb″. Document type is unknown.
file and rerun the conversion utility.
Explanation: The document-type declaration
(DOCTYPE) was not found in the file to be converted.
ISPC036 ISPC036W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. During SOURCE tag Programmer Response: Update the DTL source file to
processing, no ENTITY declaration include the !DOCTYPE DM SYSTEM document-type
found for ″cccccccc″. The variable cannot declaration and reconvert the file.
be substituted. If ″cccccccc″ is a TSO
command or other panel logic value,
this message may be removed by coding ISPC043 ISPC043E: Error. Line aaaaaaaa of file
″%amp;dddddddd″. If ″cccccccc″ is a ″bbbbbbbb″. Multiple DOCTYPE records.
variable to be substituted, review the Explanation: More than one DOCTYPE record was
DTL source file. (ENTITY definitions found within a single GML source file.
are case sensitive. Verify that the
entity-name definition matches the Programmer Response: Update the DTL source file so
entity reference.) it contains a single DOCTYPE record.
ISPC050F Fixed length output panel libraries must ISPC053F Fixed length output list files must have
have a record length of 80, 132, or 160 a minimum record length of 80 bytes.
bytes.
Explanation: The record length of the specified list file
Explanation: The record length of the specified panel is not supported by ISPF.
library is not supported by ISPF.
User Response: Use a list file with a record length of
User Response: Use a panel library that has one of the 80.
specified record lengths.
ISPC053V Variable length output list files must
ISPC050V Variable length output panel libraries have a minimum record length of 84
should have a record length of 84, 136, bytes.
or 164 bytes. The minimum record
Explanation: The record length of the specified list file
length is 84 and the maximum is 164.
is not supported by ISPF.
Explanation: The record length of the specified panel
User Response: Use a list file with a record length of
library is not supported by ISPF.
84.
User Response: Use a panel library that has one of the
specified record lengths.
ISPC054F Fixed length output script files must
have a minimum record length of 80
ISPC051F Fixed length output message libraries bytes.
must have a minimum record length of
Explanation: The record length of the specified script
80 bytes.
file is not supported by ISPF.
Explanation: The record length of the specified
User Response: Use a script library with a record
message library is not supported by ISPF.
length of 80.
User Response: Use a message library with a record
length of 80.
ISPC054V Variable length output script files must
have a minimum record length of 84
ISPC051V Variable length output message libraries bytes.
must have a minimum record length of
Explanation: The record length of the specified script
84 bytes.
file is not supported by ISPF.
Explanation: The record length of the specified
User Response: Use a script library with a record
message library is not supported by ISPF.
length of 84.
User Response: Use a message library with a record
length of 84.
ISPC055 Tables files must have a record length of
80 bytes.
ISPC052F Fixed length output log files must have
Explanation: The record length of the specified tables
a minimum record length of 80 bytes.
file is not supported by ISPF.
Explanation: The record length of the specified log file
User Response: Use a tables library with a record
is not supported by ISPF.
length of 80.
User Response: Use a log file with a record length of
80.
ISPC059 Record format ″aaaaaaaa″ is not valid for
file ″bbbbbbbb″.
ISPC052V Variable length output log files must
Explanation: The record format of the specified file is
have a minimum record length of 84
not supported by ISPF.
bytes.
User Response: Table file format must be Fixed. DTL
Explanation: The record length of the specified log file
source, panels, messages, and script file format may be
is not supported by ISPF.
either Fixed or Variable. Log file and List file format
User Response: Use a log file with a record length of may be either Fixed or Variable, with or without print
84. control.
ISPC060 Press Enter to start conversion. | ISPC068C Only members from the first 16 data
| sets are included in this list. Select
Explanation: This message is self-explanatory.
| members to be converted. (Enter ″S *″ to
User Response: Press Enter to continue the conversion | select all members.)
process.
Explanation: Select members from the ISPF member
selection list by placing an asterisk (*) in front of each
ISPC061 Verify panel settings and press Enter to member to convert. If all the members are to be
start conversion. converted, enter ″S *″ on the command line and press
the Enter key.
Explanation: This message is self-explanatory.
User Response: Make appropriate selection of
User Response: Press Enter to continue the conversion members to be converted.
process.
ISPC073 Select option for KANA or NOKANA, ISPC079 Choose a language from the ISPF
but not both. supported languages. Use the Help
option for a list of languages.
Explanation: KANA and NOKANA are mutually
exclusive options, only one can be chosen. Explanation: The language specified is not one of the
valid ISPF supported languages. Valid languages are:
User Response: Select only one of the KANA or
English
NOKANA options and restart the conversion process.
German
Swiss German
ISPC074 Select option for Generate List file or Danish
Generate List file with substitution, but Spanish
not both. Portuguese
French
Explanation: Generate List file and Generate List file Italian
with substitution are mutually exclusive options, only Japanese
one can be chosen. Korean
User Response: Select option for Generate List file or Chinese (Simplified)
Generate List file with substitution, and restart the Chinese (Traditional)
conversion process. User Response: Specify a valid ISPF language and
restart the conversion process.
ISPC075 The aaaaaaaa language requires that the
DBCS option be selected. Either select ISPC081 Enter a valid DTL source library name.
the DBCS option or specify a non-DBCS
language. Explanation: The DTL source library name specified
was invalid. For example, the library name may not not
Explanation: The DBCS option is not selected but the conform to valid naming conventions, or unmatched
current language is a DBCS language. The language quotes were detected.
and DBCS option selection are in conflict.
User Response: Enter a valid DTL source library name
User Response: Either select the DBCS option or and restart the conversion process.
specify a non-DBCS language.
ISPC077 The KANA option is valid only with the ISPC083 Enter a valid output message library
JAPANESE language selection. name.
Explanation: KANA is only valid when the Explanation: The output message library name
JAPANESE language is used for the conversion. specified was invalid. For example, a library name may
User Response: Select the JAPANESE language, or not conform to valid naming conventions, or
deselect the KANA option, and restart the conversion unmatched quotes were detected.
process. User Response: Enter a valid output message library
name and restart the conversion process.
ISPC078 The DBCS option is valid only for
JAPANESE, CHINESES, CHINESET or ISPC084 Enter a valid output log file name.
KOREAN language selection.
Explanation: The output log file name specified was
Explanation: DBCS is only valid when the selected invalid. For example, a log file name may not conform
language used for the conversion is JAPANESE, to valid naming conventions, or unmatched quotes
CHINESES, CHINESET, or KOREAN. were detected.
User Response: Select one of the valid languages if User Response: Enter a valid output log file name and
the DBCS option is needed, or deselect the DBCS restart the conversion process.
option and restart the conversion process.
ISPC086 Enter a valid DTL source filename. ISPC100 ISPC100E: Error. Line aaaaaaaa of file
″bbbbbbbb″. The DBCS control byte ″SO″
Explanation: The DTL source member list can not be
has been detected in your source file,
displayed. This may occur when LMINIT or LMOPEN
but the DBCS option has not been
has not completed successfully.
specified. The conversion results are
User Response: Exit from the conversion utility. Enter unpredictable. The conversion utility
ISPDTLC and restart the conversion process. has automatically enabled the DBCS
option to allow formatting of your
source file to continue. Reconvert your
ISPC091 Enter a valid log file member name. source file specifying the DBCS option.
Explanation: The log file member name entered Explanation: The conversion utility encountered a
contains invalid characters, or does not conform to DBCS control shift-out byte when the DBCS option was
valid TSO member naming conventions. not specified for the conversion. The DBCS option has
User Response: Enter a valid member name for the been enabled at this point, but text formatting may be
log file. unpredictable.
User Response: Restart the conversion process with
ISPC092 Enter a valid output list file name. the DBCS option specified.
User Response: Enter a valid output list file name and Explanation: A DBCS shift-out byte was encountered
restart the conversion process. in the GML source file prior to a DBCS shift-in byte.
Programmer Response: Correct the GML source file to
ISPC093 Enter a valid list file member name. contain matched shift-in and shift-out bytes and restart
the conversion process.
Explanation: The list file member name entered
contains invalid characters, or does not conform to
valid TSO member naming conventions. ISPC102 ISPC102W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. At least 4 byte field widths
User Response: Enter a valid member name for the are required to format DBCS strings.
list file. There is not enough room to format the
″cccccccc″ on the dddddddd tag.
ISPC094 Enter a valid output SCRIPT library Explanation: The field width for the DBCS field must
name. be 4 bytes or greater to accomodate the
Explanation: The SCRIPT library name specified was shift-in/shift-out bytes along with the double-byte
invalid. For example, a library name may not conform character.
to valid naming conventions, or unmatched quotes Programmer Response: Update the GML source file to
were detected. allow at least 4 bytes for the field width and restart the
User Response: Enter a valid output SCRIPT library conversion process.
name and restart the conversion process.
ISPC103 ISPC103E: Error. Line aaaaaaaa of file
ISPC095 Enter a valid TABLES library name. ″bbbbbbbb″. Cannot end string without
DBCS SI byte.
Explanation: The TABLES library name specified was
invalid. For example, a library name may not conform Explanation: A string containing a DBCS shift-out
to valid naming conventions, or unmatched quotes byte ended before the matching DBCS shift-in byte was
were detected. found.
User Response: Enter a valid TABLES library name User Response: Check the GML source file and match
and restart the conversion process. DBCS shift-in and shift-out bytes, then restart the
conversion process.
ISPC104 ISPC104E: Error. Line aaaaaaaa of file ISPC109 ISPC109W: Warning. The use of the
″bbbbbbbb″. Cannot end DBCS string on ″aaaaaaaa″ language requires that the
odd byte boundary. DBCS option be specified for the
conversion. The conversion utility has
Explanation: A DBCS string was encountered with an
automatically enabled the DBCS option.
odd number of bytes, which is not acceptable for a
pure DBCS string. Explanation: This is an informational message. The
language specified for the conversion requires the
User Response: Update the GML source file for the
DBCS option. The DBCS option has been automatically
correct DBCS data and restart the conversion process.
enabled for the conversion.
ISPC121 ISPC121W: Warning. Line aaaaaaaa of file ISPC129A ISPC129AE: Error. Line aaaaaaaa of file
″bbbbbbbb″. Key Description exceeds ″bbbbbbbb″. Return code of ″12″
allowable length of cccccccc characters. (Attributes are not valid) from the
SELECT service attempting to create an
Explanation: The maximum key description allowed
ISPF Keylist.
by the Dialog Tag Language is 64. The first 8 bytes of
description are used by ISPF. Explanation: The keylist update program has detected
an invalid key attribute.
User Response: Reduce the length of the key
description to 64 for compatibility with OS/2 DM. User Response: Provide a valid value for the FKA
attribute of the KEYI tag.
ISPC123 ISPC123W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. Internal-command-name ISPC129B ISPC129BE: Error. Line aaaaaaaa of file
″cccccccc″ is not valid for the ″dddddddd″ ″bbbbbbbb″. Return code of ″16″ (Key
function key. defined is not valid) from the SELECT
service attempting to create an ISPF
Explanation: When the HELP command is specified in
Keylist.
a keylist, it must be assigned to the F1 or F13 key.
Explanation: The keylist update program has detected
When the EXIT command is specified in a keylist, it
an invalid key name.
must be assigned to the F3 or F15 key.
User Response: Provide a valid value for the KEY
When the CANCEL command is specified in a keylist,
attribute of the KEYI tag.
it must be assigned to the F12 or F24 key.
User Response: Use the appropriate key for the HELP,
ISPC129C ISPC129CE: Error. Line aaaaaaaa of file
EXIT, or CANCEL command.
″bbbbbbbb″. Return code of ″cccccccc″
(Severe Error) from the SELECT service
ISPC126 ISPC126W: Warning. Line aaaaaaaa of file attempting to create an ISPF Keylist.
″bbbbbbbb″. Duplicate ″cccccccc″ key was
Explanation: The keylist update program has detected
encountered and will be ignored.
a severe error while attempting to update the keylist.
Explanation: Only 1 definition of the cccccccc key is
User Response: If the error continues, contact your
allowed in each keylist.
system programmer.
User Response: Remove the duplicate definition for
System Programmer Response: If you are not running
the cccccccc key.
mixed levels of ISPF code, you may need to contact
IBM support.
ISPC127 ISPC127W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. The key value ″cccccccc″ is
ISPC129F ISPC129FE: Error. Line aaaaaaaa of file
not supported by the conversion utility
″bbbbbbbb″. Return code of ″32″ (Keylist
as a valid key assignment. Valid values
table open) from the SELECT service
are F1-F24 only.
attempting to create an ISPF Keylist.
Explanation: This message is self-explanatory. (The keylist update program received a
return code of ″12″ from the TBOPEN
User Response: Use a key value in the F1-F24 range. service.)
Explanation: The keylist update program received a
ISPC128 ISPC128E: Error. Line aaaaaaaa of file return code of 12 from the TBOPEN service. The keylist
″bbbbbbbb″. Key list Application ID update cannot be performed on the currently active
required. ″cccccccc″ must be specified as application ID.
an invocation option in order to write
″dddddddd″. User Response: ISPDTLC must be run with a different
application ID.
Explanation: No application ID is available to identify
the keylist.
User Response: Specify the application ID on the
invocation panel, or use the KEYLAPPL=xxxx keyword
from the invocation syntax to specify the application ID
for this keylist.
ISPC140 ISPC140W: The DBCS option is | ISPC150 ISPC150W: Warning. Line aaaaaaaa of file
required when KANA has been | ″bbbbbbbb″. When ″cccccccc″, ″dddddddd″
specified. The conversion utility has | on the eeeeeeee tag does not conform to
automatically enabled the DBCS option. | the CUA Architecture definition and
| will therefore not be CUA compliant.
Explanation: The KANA keyword has been specified
without specification of the DBCS option. DBCS is Explanation: This is an informational message.
required when processing with KANA. The conversion
utility has automatically enabled the DBCS option.
| ISPC151 ISPC151W: Warning. Line aaaaaaaa of file
User Response: If KANA is not to be used, restart the | ″bbbbbbbb″. The use of
conversion process without the KANA and DBCS | cccccccc=″dddddddd″ on the eeeeeeee tag
options. | does not conform to the CUA
| Architecture definition and will
| therefore not be CUA compliant.
ISPC141 ISPC141W: The JAPANESE language is
required when KANA has been Explanation: This is an informational message.
specified. The conversion utility has
automatically set the language to
ISPC201 ISPC201E: Error. Line aaaaaaaa of file
″JAPANESE″.
″bbbbbbbb″. No help panel title specified
Explanation: The KANA keyword has been specified after Help Tag.
without specification of the JAPANESE language. The
Explanation: A Help panel tag requires a panel title.
conversion utility requires the use of the JAPANESE
language when processing KANA. The conversion User Response: Update the DTL source file to add a
utility has automatically set the language specification panel title and rerun the conversion utility.
to JAPANESE.
User Response: If KANA is not to be used, restart the ISPC202 ISPC202W: Warning. Line aaaaaaaa of file
conversion process without the KANA and JAPANESE ″bbbbbbbb″. Panel title has been
options. truncated.
Explanation: The panel title is too long for the
ISPC142 ISPC142W: The DBCS option has been specified panel width.
specified, but either no language has
been specified or the language selected User Response: Reduce the length of the title text or
is not a DBCS language. The conversion increase the specified panel width, as appropriate.
utility has automatically set the
language to ″JAPANESE″. ISPC203 ISPC203W: Warning. Line aaaaaaaa of file
Explanation: The DBCS keyword has been specified. ″bbbbbbbb″. Panel title cannot be centered
However, either no language was selected, or the within the available panel width.
language specified does not support DBCS. The Explanation: This is an informational message.
conversion utility has automatically set the language
specification to JAPANESE.
ISPC205 ISPC205E: Error. Line aaaaaaaa of file
User Response: If DBCS is not to be used, restart the ″bbbbbbbb″. Unable to create any more
conversion process without the DBCS and JAPANESE cccccccc panels dynamically to simulate
options. scrolling. The maximum of 37 panels
has been exceeded.
ISPC149 ISPC149E: Error. Line aaaaaaaa of file Explanation: Help panel text has exceeded the
″bbbbbbbb″. Line contains DBCS data number of panels that can be created by the conversion
which is not valid. utility.
Explanation: Line contains DBCS data which is not User Response: Increase the width or depth (or both)
valid. Check for proper use of shift out and shift in of the help panels to allow more text on each panel,
control bytes, and make sure the DBCS data is an even convert the DTL source to generate a scrollable panel,
number of bytes. or divide the help text into multiple HELP tags.
User Response: Correct the DTL source file and rerun
the conversion process.
ISPC230 Enter the seven character FMID for the ISPC243 ISPC243W: Warning. Line aaaaaaaa of file
SMP/E USERMOD. ″bbbbbbbb″. Extraneous text ″cccccccc″
found during the format process of
Explanation: This is an informational message.
″dddddddd″ tag. Text is ignored.
Explanation: Text was present following the close tag
ISPC231 Enter DDDEF name - Enter the DDDEF
delimiter on the dddddddd tag. This tag does not allow a
name to be used as the SYSLIB for the
tag text field.
keyword source in the SMP/E
USERMOD. User Response: Remove the invalid text string.
Explanation: This is an informational message.
ISPC244 ISPC244W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. No text found during the
ISPC232 Enter DDDEF name - Enter the DDDEF
format process for the ″cccccccc″ tag.
name to be used as the SYSLIB for the
Panel formatting may be affected.
load modules in the SMP/E USERMOD.
Explanation: No text was provided for the cccccccc tag.
Explanation: This is an informational message.
This tag should have a text field for proper panel
formatting.
ISPC233 Enter DDDEF name - Enter the DDDEF
User Response: Place text between the cccccccc tag and
name to be used as the DISTLIB for the
the cccccccc end-tag.
keyword source in the SMP/E
USERMOD.
ISPC245 ISPC245W: Warning. Line aaaaaaaa of file
Explanation: This is an informational message.
″bbbbbbbb″. Panel width too small to
include LSTCOL DATAVAR=cccccccc..
ISPC234 Error Building USERMOD - An error cccccccc will not be written to the panel.
occured building the SMP/E
Explanation: There is insufficient room for the cccccccc
USERMOD. Correct errors reported and
table column.
retry the function.
User Response: Adjust table column width
Explanation: This is an informational message.
specifications.
ISPC249 ISPC249W: Warning. Line aaaaaaaa of file ISPC256 Conversion error — Conversion of
″bbbbbbbb″. LSTCOL tag assembler source file ″aaaaaaaa″ to
″column-heading″ extends beyond right keyword file ″bbbbbbbb″ failed.
panel boundary and will be truncated to
Explanation: An error was encountered converting the
″cccccccc″.
specified source file to the keyword file.
Explanation: This is an informational message.
User Response: Verify the input assembler file is an
ISPF configuration table assembler member (member
ISPC250 Keyword file saved — The updated ISPCNFIG from SAMPLIB).
keyword file was successfully saved to
″aaaaaaaa″ .
ISPC257 Member name not allowed — Member
Explanation: This is an informational message. name is not allowed on the load and
object data sets. Specify the member
name in the Configuration Member and
ISPC251 Keyword file verified — Keyword file
VSAM Member fields.
″aaaaaaaa″ was verified and is correct.
Explanation: A data set name string that included a
Explanation: This is an informational message.
member name was specified for either the ″Output
Configuration Table Load Module Data Set″ or ″ Object
ISPC252 Keyword file errors — Errors were data set″ field of the Build Configuration Table Load
found during verification of keyword Module panel. Member names for these data sets
file ″aaaaaaaa″ and were previously should be specified in the ″Configuration Member″ and
displayed. ″VSAM member″ fields if you wish to use names other
than the defaults of ISPCFIGU and ISPCFIGV.
Explanation: The keyword verification function found
errors in the keyword file being processed. A listing
showing the errors was previously displayed to the ISPC258 Assemble failed — The assemble of the
user. configuration table source failed, see
below for details.
User Response: Correct the errors in the keyword file
and reprocess it. Explanation: This is an informational message.
ISPC253 Load module built— The configuration ISPC259 Link Edit failed — The link edit of the
table load module and VSAM load configuration table failed, see below for
module were successfully saved to details.
″aaaaaaaa″ .
Explanation: This is an informational message.
Explanation: The specified keyword file contained
keywords for both the configuration table and the
ISPC260 Rename needed — The configuration
VSAM Edit/View/Browse support. Both load modules
load modules were successfully saved to
have been successfully built.
″aaaaaaaa″ , but using names ″bbbbbbbb″,
and ″cccccccc″. These members must be
ISPC254 Load module build error — An error named ISPCFIGU and ISPCFIGV to be
was encountered building load module used as ISPF configuration modules.
″aaaaaaaa″ from keyword file ″bbbbbbbb″.
Explanation: The configuration load module and
Explanation: An error was encountered converting the VSAM load module were successfully built using the
specified file to a load module. An assembler or link names specified in the ″Configuration member″ and
edit listing should have been displayed to indicate the ″VSAM member″ fields. These load module members
error. must be renamed to ISPCFIGU and ISPCFIGV and
placed in a load library accessible to ISPF for them to
User Response: If the error can be corrected by a be used by ISPF.
change to the keyword file, make the change and
reprocess. If the problem cannot be corrected, contact
your system programmer. ISPC261 Allocation error — An error was
encountered allocating Keyword data set
″aaaaaaaa″ .
ISPC255 Conversion successful —Conversion of
assembler file ″aaaaaaaa″ to keyword file Explanation: The TSO ALLOCATE command file
″bbbbbbbb″ was successful. failed when attempting to allocate the specified
keyword file to a DDNAME.
Explanation: This is an informational message.
ISPC276 Defaults loaded — Keyword file ISPC285 Invalid combination — At least one data
″aaaaaaaa″ was not found, default values set must be specified for each restriction
have been set for all configuration field selected.
options.
Explanation: Both a data set name or pattern and a
Explanation: This is an informational message. VSAM restriction field must be selected. It is not valid
to specify only one or the other.
ISPC277 Keyword file loaded — Defaults have
been initialized from keyword file ISPC286 Input file empty — The input data set
″aaaaaaaa″ . or member specified for conversion is
empty.
Explanation: This is an informational message.
Explanation: This is an informational message.
ISPC278 Block size value of aaaaaaaa is not a
multiple of bbbbbbbb . ISPC287 Invalid input file — The input file
specified is not an ISPF Configuration
Explanation: This is an informational message.
Table asssembler source module, no
ISRCONFG CSECT found.
ISPC279 Block size value of aaaaaaaa is not a
Explanation: The source file specified as input to the
multiple of record length value bbbbbbbb
Conversion option does not appear to be an ISPF
.
Configuraton Table assembler module. ISPF looks for
Explanation: This is an informational message. the string ’ISRCONFG CSECT’ on the first line not
containing an asterisk in column 1 and the string was
not found in the file specified.
ISPC280 Assemble failed — The assemble of the
configuration table VSAM module User Response: Specify the correct input file.
failed, see bolow for details.
Explanation: This is an informational message. ISPC290 GIMDTS error - An error was
encountered with GIMDTS converting
the keyword source file to the SMP/E
ISPC281 Link Edit failed — The link edit of the output data set. See the following
configuration table VSAM module GIMDTS listing.
failed, see below for details.
Explanation: When building the ISPF Configuration
Explanation: This is an informational message. table into an SMP/E USERMOD an error was
encountered with GIMDTS converting the keyword
ISPC282 Invalid data set name — The data set source file to the SMP/E output data set. See the
name specified is invalid. Enter the data generated GIMDTS listing for details.
set name and member for the keyword
file in the separate fields provided. ISPC291 IEBCOPY error - An error was
Explanation: The data set name entered is encountered with IEBCOPY unloading
syntactically incorrect. the load module aaaaaaaa. to a temporary
sequential file. See the following
User Response: Correct the data set name. IEBCOPY listing.
Explanation: When building the ISPF Configuration
ISPC284 Invalid data set name — Remove the table into an SMP/E USERMOD an error was
quotes from the data set name or pattern encountered with IEBCOPY unloading the load module
entered. for either the configuration table, module ISPCFIGU, or
Explanation: The specified name must be an unquoted the VSAM restrictions table, module ISPCFIGV to a
data set name or pattern. temporary sequential file. See the generated IEBCOPY
listing for details
User Response: Correct the data set name or pattern
entered.
ISPC292 GIMDTS error - An error was ISPC299 Enter a seven character identifier for the
encountered with GIMDTS converting SMP/E USERMOD.
the IEBCOPY unloaded load module
Explanation: This is an informational message.
aaaaaaaa. to the SMP/E output data set.
See the following GIMDTS listing.’
ISPC301 ISPC301W: Warning. Line aaaaaaaa of file
Explanation: When building the ISPF Configuration
″bbbbbbbb″. Duplicate MSG tag SUFFIX
table into an SMP/E USERMOD an error was
found. This MSG tag will be ignored.
encountered with GIMDTS converting the IEBCOPY
unloaded data set to the SMP/E output data set. See Explanation: Message SUFFIX must be unique for
the generated GIMDTS listing for details. each message within a MSGMBR.
User Response: Remove the duplicate suffix
ISPC293 EXECIO error - An error was specification and rerun the conversion utility.
encountered writing the USERMOD to
the output data set. Data set may be
full, compress the library and retry the ISPC302 ISPC302W: Warning. Line aaaaaaaa of file
function. ″bbbbbbbb″. Message text is longer than
cccccccc characters and will be truncated.
Explanation: When building the ISPF configuration
table into an SMP/E USERMOD an EXECIO error was Explanation: The message text provided exceeds the
encountered writing the USERMOD to the output data ISPF maximum message length.
set. User Response: Reduce the length of the message text
and rerun the conversion utility.
ISPC294 USERMOD built - The SMP/E
USERMOD was successfully saved to ISPC303 ISPC303W: Warning. Line aaaaaaaa of file
aaaaaaaa.. ″bbbbbbbb″. MSGMBR has no messages.
Explanation: The ISPF configuration table was No message file will be written.
successfully built into an SMP/E USERMOD. Explanation: No valid MSG tags were formatted
within the current MSGMBR tag.
ISPC295 Enter DDDEF name - Enter the DDDEF User Response: Correct reported problems or include
name to be used as the DISTLIB for the MSG tag(s) within the MSGMBR tag, as appropriate,
load modules in the SMP/E USERMOD. and rerun the conversion utility.
Explanation: This is an informational message.
ISPC304 ISPC304W: Warning. Line aaaaaaaa of file
ISPC296 Enter the seven character name of a ″bbbbbbbb″. MSG tag contains no text.
prior USERMOD to be superseded by Message cannot be created.
this SMP/E USERMOD. The fields must Explanation: MSG tag must include the message text.
be filled from top to bottom.
User Response: Add the required message text and
Explanation: This is an informational message. rerun the conversion utility.
ISPC297 Invalid data set name - The data set | ISPC305 ISPC305W: Warning. Line aaaaaaaa of file
name specified is invalid. The SMP/E | ″bbbbbbbb″. Conflict on VARSUB tag
data set name must not contain a | between attributes ″VAR″ and ″FIELD″.
member name. | ″FIELD″ cannot be specified if ″VAR″ is
Explanation: The data set name entered is | used. ″FIELD″ is ignored for this
syntactically incorrect. It must not contain a member | conversion.
name. | Explanation: DTL does not allow both VAR and
User Response: Correct the data set name. | FIELD attributes on the same VARSUB tag. FIELD is
| not supported by ISPF.
ISPC298 Incorrect attributes - The SMP/E data set | User Response: Remove the FIELD attribute and
must be a partitioned data set with a | rerun the conversion utility.
record length of 80 and a record format
of FB.
Explanation: This is an informational message.
ISPC307 ISPC307W: Warning. Line aaaaaaaa of file ISPC401 ISPC401W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. The SUFFIX value ″cccccccc″ ″bbbbbbbb″. The RUN option for the
is not valid because the resulting ACTION tag was specified without a
message number would be more than 8 command. The ACTION tag is ignored.
characters in length. This MSG tag will
Explanation: None.
be ignored.
User Response: Add a command name to the RUN
Explanation: A combination of a 7 character MSGMBR
attribute on the ACTION tag and rerun the conversion
name and a 2 character SUFFIX is invalid.
utility.
User Response: Change either the MSGMBR name or
the SUFFIX and rerun the conversion utility.
ISPC402 ISPC402W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. Internal-command-name
| ISPC309 ISPC309W: Warning. Line aaaaaaaa of file must be equal to the
| ″bbbbbbbb″. There is a conflict in the use external-command-name in order to
| of ″WIDTH=cccccccc″ on the MSGMBR allow command truncation when the T
| tag and ″FORMAT=ASIS″ on the MSG tag is used. There will be no minimum
| tag. The message may not display as command name in this command.
| intended.
Explanation: None.
| Explanation: This is an informational message.
User Response: Correct the DTL source so the
internal-command-name and external-command-name
ISPC310 ISPC310W: Warning. Line aaaaaaaa of file match, and rerun the conversion utility.
″bbbbbbbb″. The first line of the message
created by MSG tag formatting is longer
ISPC403 ISPC403W: Warning. Line aaaaaaaa of file
than 80 characters. Message cannot be
″bbbbbbbb″. Command table was not
created.
written because the required ″APPLID″
Explanation: A combination of short message and keyword was not specified.
message attributes for the first line of a message has
Explanation: None.
exceeded the width of the message file.
User Response: Specify the APPLID attribute on the
User Response: Remove the short message
CMDTBL tag
specification or reduce the length of variable names
used for message attributes HELP, MSGTYPE, and
LOCATION, as appropriate. ISPC404 ISPC404W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. An error occurred while
processing a command table. Processing
ISPC311 ISPC311W: Warning. Line aaaaaaaa of file
of command table has been cancelled
″bbbbbbbb″. NAME on MSGMBR tag is
after a return code of cccccccc from table
not valid. No message file will be
service ″dddddddd″.
written.
Explanation: None.
Explanation: The name provided does not follow the
ISPF message member name format. User Response: Refer to ISPF Services Guide for
explanations of table services return codes.
User Response: Change the name to match the ISPF
name format and rerun the conversion utility.
ISPC405 ISPC405E: Error. ISPF Command Table
was not created. An error occurred while
ISPC400 ISPC400W: Warning. Line aaaaaaaa of file
opening a command table. Refer to your
″bbbbbbbb″. External-command-name
ISPF documentation on TBOPEN for a
must be one word. It cannot contain any
Return Code of ″aaaaaaaa″.
blanks. The external-command-name is
ignored. Explanation: None.
Explanation: None. User Response: Refer to ISPF Services Guide for
explanations of table services return codes.
User Response: Enter a valid command name and
rerun the conversion utility.
ISPC406 ISPC406E: Error. ISPF Command Table ISPC410 ISPC410W: Warning. Line aaaaaaaa of file
was not created. Possible reasons may ″bbbbbbbb″. The ALIAS for command
be that the conversion tool was not run cccccccc was found after the command.
as a dialog on ISPF or ISPF was not The ALIAS entry must precede the
active. command it references. The ALIAS will
be unavailable to ISPF. Please update
Explanation: None.
your tag source file to move the ALIAS
User Response: Rerun the conversion utility from the before the referenced command.
ISPF command line.
Explanation: None.
User Response: Move the ALIAS reference in the DTL
ISPC407A ISPC407AE: Error. Line aaaaaaaa of file
source as indicated and rerun the conversion utility.
″bbbbbbbb″. Return code of ″16″
(ISPTABL file not allocated) from the
SELECT service attempting to create an ISPC411 ISPC411W: Warning. Line aaaaaaaa of file
ISPF Command Table. ″bbbbbbbb″. cccccccc is longer than
dddddddd characters, will be truncated.
Explanation: None.
Explanation: None.
User Response: Refer to ISPF Services Guide for
explanations of table services return codes. User Response: Adjust cccccccc to be equal to
dddddddd characters and rerun the conversion utility.
ISPC407B ISPC407BE: Error. Line aaaaaaaa of file
″bbbbbbbb″. Return code of ″cccccccc″ ISPC412 ISPC412W: Warning. Line aaaaaaaa of file
(Severe Error) from the SELECT service ″bbbbbbbb″. A LSTGRP heading must
attempting to create an ISPF Command include at least one field from the first
Table. model line to be displayed. This
heading cannot be formatted and is
Explanation: None.
being reset to blanks.
User Response: Refer to DM Guide and Reference for
Explanation: None.
explanations of table services return codes.
User Response: At least one LSTCOL tag from the
first model line should be included within the LSTGRP
ISPC408 ISPC408E: Error. Line aaaaaaaa of file
tag.
″bbbbbbbb″. The dynamic area identifier
″cccccccc″ is longer than the dddddddd
characters of dynamic area width. ISPC413 ISPC413W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. External command string
Explanation: None.
cannot be less than 2 characters in
User Response: Increase the width of the dynamic length and will be set to ″ ″.
area to at least the number of characters shown in the
Explanation: None.
area identifier.
User Response: Correct the command name to be a
minimum of 2 characters in length and rerun the
ISPC409 ISPC409E: Error. Line aaaaaaaa of file
conversion utility.
″bbbbbbbb″. The graphic area identifier
″cccccccc″ is longer than the dddddddd
characters of graphic area width. ISPC414 ISPC414W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. Only one keyword from the
Explanation: None.
following list can be specified on an
User Response: Increase the width of the graphic area ACTION tag: RUN, CLASS, SETVAR,
to at least the number of characters shown in the area TOGVAR.
identifier.
Explanation: None.
User Response: Correct the DTL source to specify
only one of the attributes listed and rerun the
conversion utility.
ISPC415 ISPC415W: Warning. Line aaaaaaaa of file ISPC421 ISPC421W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. ISPF will support a ″bbbbbbbb″. ″cccccccc″ exceeds the
Command Action up to 240 characters in maximum length of dddddddd text
length. The Command Action will be characters that can be placed on the
truncated. current panel command line. ″cccccccc″
will be truncated to fit on the command
Explanation: None.
line.
User Response: Correct the command action to the
Explanation: This message is self-explanatory.
stated length limit and rerun the conversion utility.
User Response: Shorten the command prompt text or
increase the panel width, as appropriate, and rerun the
ISPC416 ISPC416W: Warning. Line aaaaaaaa of file
conversion utility.
″bbbbbbbb″. ISPF does not support the
″ACTION=cccccccc″ coded on the
dddddddd tag. The Command Action will ISPC422 ISPC422W: Warning. Line aaaaaaaa of file
be set to ″NOP″. ″bbbbbbbb″. This panel contains a
)MODEL line generated by the LSTFLD
Explanation: None.
and LSTCOL tags but not a required
User Response: Replace the invalid action and rerun CMDAREA command line to
the conversion utility. accompany it. A command line is being
added to the panel.
ISPC417 ISPC417E: Error. Line aaaaaaaa of file Explanation: This message is self-explanatory.
″bbbbbbbb″. Additional parameters must
User Response: Provide a CMDAREA tag to eliminate
follow cccccccc and will affect
this message.
processing.
Explanation: None.
ISPC423 ISPC423W: Warning. Line aaaaaaaa of file
User Response: Add the additional command ″bbbbbbbb″. The requested SCROLL
parameters and rerun the conversion utility. amount field will not fit on the
command line for this panel. The
SCROLL amount field is ignored.
ISPC418 ISPC418W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. No parameters are valid Explanation: This message is self-explanatory.
following cccccccc..
User Response: Shorten the command prompt text or
Explanation: None. increase the panel width, as appropriate, and rerun the
conversion utility.
User Response: Remove the indicated invalid
parameters and rerun the conversion utility.
ISPC423A ISPC423AW: Warning. Line aaaaaaaa of
file ″bbbbbbbb″. The point-and-shoot text
ISPC419 ISPC419W: Warning. Line aaaaaaaa of file as specified by the PSBUTTON attribute
″bbbbbbbb″. No commands were specified will not fit on the command line for this
within the CMDTBL tag. No command panel. The point-and-shoot text is not
table will be written. added to the command line.
Explanation: None. Explanation: This message is self-explanatory.
User Response: Add the required CMD tag definitions User Response: Shorten the command prompt text,
and rerun the conversion utility. shorten the point-and-shoot text or increase the panel
width, as appropriate, and rerun the conversion utility.
ISPC420 ISPC420W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. A valid CMDACT ACTION
was not specified for cccccccc.
Explanation: This message is self-explanatory.
User Response: Provide a valid command action and
rerun the conversion utility.
ISPC424 ISPC424E: Error. Line aaaaaaaa of file ISPC431 ISPC431W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. An error occurred during the ″bbbbbbbb″. The default name ″ZCMD″
completion of processing for command was used to generate ″)INIT″ and
table ″cccccccc″. Processing of the ″)PROC″ section panel statements.
command table has been cancelled after These panel statements are not correct
a return code of dddddddd from ISPF because the CMDAREA tag name has
service ″eeeeeeee″. A temporary command been specified as ″cccccccc″. Move the
table member ″ffffffff″ has been created CMDAREA tag so that it is placed
on table file ″gggggggg″. before the SELFLD tag that defines the
menu choices and reconvert the panel.
Explanation: This message is self-explanatory.
Explanation: The CMDAREA tag was placed in the
User Response: Refer to ISPF Services Guide for
DTL source file following the SELFLD tag. The
explanations of table services return codes.
specified CMDAREA name ″cccccccc″ was not available
when the panel statements were generated.
| ISPC425 ISPC425W: Warning. Line aaaaaaaa of file
User Response: Move the CMDAREA tag so that it is
| ″bbbbbbbb″. ″cccccccc″ tag field name
placed before the SELFLD tag that defines the menu
| dddddddd exceeds the maximum field
choices. The specified name ″cccccccc″ will be used in
| width of eeeeeeee characters available for
the panel statements.
| the name. The NOZVARS option is
| ignored for field name ″dddddddd″.
ISPC432 ISPC432W: Warning. Line aaaaaaaa of file
| Explanation: This message is self-explanatory.
″bbbbbbbb″. ACTION tags following an
| User Response: Shorten the field name to be less than ACTION tag with the RUN attribute
| or equal to the field width and rerun the conversion specified are not valid and will be
| utility. ignored.
Explanation: This message is self-explanatory.
ISPC426 ISPC426E: Error. Line aaaaaaaa of file
User Response: Place the ACTION tag with the RUN
″bbbbbbbb″. ″LINE=cccccccc″is not valid
attribute after the other ACTION tags for this PDC or
because a previous variable model line
CHOICE tag and rerun the conversion utility.
definition list exists for this line.
Explanation: This message is self-explanatory.
| ISPC433 ISPC433W: Warning. Line aaaaaaaa of file
User Response: Specify a different line number for | ″bbbbbbbb″. TYPE=cccccccc on the SELFLD
this variable model line definition and rerun the | tag is not valid on a panel when the
conversion utility. | MENU keyword is not specified on the
| PANEL tag. This tag will be formatted
| as TYPE=SINGLE.
ISPC427 ISPC427E: Error. Line aaaaaaaa of file
″bbbbbbbb″. ″LINE=cccccccc″is not valid | Explanation: This message is self-explanatory.
because a standard model line
| User Response: Add the MENU attribute to the
definition list exists for this line.
| PANEL tag and rerun the conversion utility.
Explanation: This message is self-explanatory.
User Response: Specify a different line number for | ISPC434 ISPC434W: Warning. Line aaaaaaaa of file
this variable model line definition and rerun the | ″bbbbbbbb″. Only one occurance of a
conversion utility. | SELFLD tag with a TYPE attribute value
| of MENU, MODEL, or TUTOR can be
| specified on a panel. This tag will be
ISPC430 ISPC430W: Warning. Line aaaaaaaa of file | formatted as TYPE=SINGLE.
″bbbbbbbb″. This is a selection panel and
requires a command line, but no | Explanation: None.
CMDAREA tag was present. A
| User Response: Place each set of option menu
command line is being added to the
| selections on a separate panel.
panel.
Explanation: This message is self-explanatory.
User Response: Provide a CMDAREA tag to eliminate
this message.
| ISPC435 ISPC435W: Warning. Line aaaaaaaa of file ISPC502 ISPC502W: Warning. ISPDTLC received
| ″bbbbbbbb″. If an ACTION tag within a a non-zero return code from EXECIO
| SELFLD tag defined as TYPE=TUTOR is while processing ’aaaaaaaa’. Refer to the
| coded with the TYPE attribute, the ’bbbbbbbb’ documentation for an EXECIO
| TYPE value must be specified as Return code = ’cccccccc’.
| PANEL. The ACTION tag attribute
Explanation: This message is self-explanatory.
| TYPE=cccccccc is ignored.
User Response: Correct the condition causing return
| Explanation: This message is self-explanatory.
code cccccccc.
| User Response: Place each set of option menu
| selections on a separate panel.
ISPC503 ISPC503W: Warning. Data will not
replace the ’aaaaaaaa’ file because
| ISPC436 ISPC436W: Warning. Line aaaaaaaa of file NOREPLACE was specified on
| ″bbbbbbbb″. If an ACTION tag within a invocation.
| SELFLD tag is coded as TYPE=VAR, the
Explanation: This message is self-explanatory.
| RUN attribute must be specified as
| ″%varname″. The ACTION tag will be User Response: To replace the data on the aaaaaaaa
| processed as TYPE=CMD. file, change the invocation option to REPLACE or select
the Replace Panel/Message/Script option on the
| Explanation: This message is self-explanatory.
invocation panel.
| User Response: Place each set of option menu
| selections on a separate panel.
ISPC503A ISPC503AW: Warning. Data will not
replace the ’aaaaaaaa’ file because
ISPC500 ISPC500W: Warning. NLS language NOLOGREPL was specified on
literals could not be obtained by ISPF invocation.
for the requested language. The values
Explanation: This message is self-explanatory.
for the current session language will be
used. User Response: To replace the data on the aaaaaaaa
file, change the invocation option to LOGREPL or select
Explanation: This message is self-explanatory.
the Replace Log File Members option on the invocation
User Response: Contact your system programmer. panel.
System Programmer Response: Make sure that all
NLS modules have been made available to ISPF. Verify ISPC503B ISPC503BW: Warning. Data will not
that the user is running with enough virtual storage to replace the ’aaaaaaaa’ file because
allow ISPF to load the requested language module. If NOLISTREPL was specified on
the error persists, contact IBM support. invocation.
Explanation: This message is self-explanatory.
ISPC501 ISPC501W: Warning. NLS language
User Response: To replace the data on the aaaaaaaa
literals could not be obtained by ISPF
file, change the invocation option to LISTREPL or select
for the requested language. The default
the Replace List File Members option on the invocation
English literals will be used.
panel.
Explanation: This message is self-explanatory.
User Response: Contact your system programmer. ISPC504 ISPC504E: Error. Log file output is
directed to the ISPF log file. The ISPF
System Programmer Response: Make sure that all
log file is not allocated. Change ISPF
NLS modules have been made available to ISPF. Verify
Option 0 to allocate the log file or
that the user is running with enough virtual storage to
provide an ISPDTLC log file.
allow ISPF to load the requested language module. If
the error persists, contact IBM support. Explanation: The ISPF log file is not allocated and
cannot be used by ISPDTLC.
User Response: If the user intends to direct the log
file to the ISPF log and no ISPF log can be allocated,
then the Option 0 (ISPF Settings) update is required to
allow ISPF to allocate the log file. Alternatively, the
user can create a private log file and provide this log
file name to ISPDTLC. If the ISPDTLC command
syntax invocation is being used, the log file name is
ISPC506 ISPC506E: Error. File ’aaaaaaaa’ was not ISPC510 ISPC510E: Error. Incorrect syntax:
found or was empty. Option must be ″aaaaaaaa″ or ″bbbbbbbb″
but not both.
Explanation: This message is self-explanatory.
Explanation: This message is self-explanatory.
User Response: Provide a file that contains DTL
source records. User Response: Specify either option aaaaaaaa or
option bbbbbbbb.
ISPC507 ISPC507E: Error. Data cannot be written
to disk because a name conflict exists ISPC511 ISPC511E: Error. Incorrect syntax:
between input aaaaaaaa file ″bbbbbbbb″ aaaaaaaa=″bbbbbbbb″. Keylist Application
and output file cccccccc ″dddddddd″. ID must be from 1 to 4 characters in
length.
Explanation: The input file dddddddd will be
overwritten. Explanation: This message is self-explanatory.
User Response: Provide a unique output member User Response: Provide a 1 to 4 character application
name. ID.
The input and output file names may be the same, but
the member name for the output file must be different ISPC512 ISPC512E: Error. Incorrect syntax:
than the member name for the input file to avoid aaaaaaaa=″bbbbbbbb″ contains character(s)
overwriting the source data. cccccccc identifies the which are not valid. The first character
output file type where the conflict was found. of the Keylist Application ID must be
’cccccccc’or ’dddddddd’. Characters 2 - 4, if
entered, must be ’cccccccc’, ’dddddddd’ or
ISPC508 ISPC508W: Warning. Data cannot be
’eeeeeeee’.
written to the file name ’aaaaaaaa’. There
is a name conflict with active ISPF files. Explanation: This message is self-explanatory.
Explanation: The output name specified for the User Response: Provide a correct 1 to 4 character
ISPDTLC log or list file conflicts with the ISPF log or application ID.
list name.
User Response: Provide a unique output log or list ISPC513 ISPC513W: Warning. Conversion option
name. ’aaaaaaaa’ is valid only when running
ISPDTLC under ISPF Option 7 (Dialog
Test). ’aaaaaaaa’ changed to ’bbbbbbbb’.
Explanation: Option aaaaaaaa is valid only for ISPF
test mode processing and is changed to bbbbbbbb.
User Response: Remove the specification of option
Explanation: Option aaaaaaaa is not valid for batch User Response: If ISPDTLC was invoked with
processing and is changed to bbbbbbbb. command syntax, specify the NOPREP conversion
option. If the invocation was from the interactive panel,
User Response: Remove the specification of option deselect the Preprocess Panel Output option.
aaaaaaaa from the batch invocation.
Explanation: This message is self-explanatory. User Response: Issue the SAVELOG, SAVELIST, or
SAVEALL commands only when a log or list file
User Response: Change the log file disposition or member is to be written to a partitioned data set.
place log messages on an ISPDTLC log file.
ISPC518 ISPC518E: Error. Conversion Utility ISPC527 The ″aaaaaaaa″ file was defaulted to the
message number aaaaaaaa is missing in ISPF aaaaaaaa file. All records have
message file: ’bbbbbbbb’. previously been written.
Explanation: This message is self-explanatory. Explanation: The option to write the ISPDTLC log or
User Response: Contact your system programmer. list file to disk has been selected, but no log or list
name was provided. ISPDTLC has placed the log or list
System Programmer Response: Make sure that all output on the ISPF log or list file, respectively.
messages provided for ISPF have been properly
installed. If the error persists, contact IBM support. User Response: Issue the SAVELOG, SAVELIST, or
SAVEALL commands only when a log or list file
member is to be written to a partitioned data set.
ISPC519 ISPC519E: Error. Line aaaaaaaa of file
″bbbbbbbb″. The ISPF LIBDEF service for
″cccccccc″ has ended with return code: ISPC528 There are no records available to be
″dddddddd″. ″eeeeeeee″ will not be saved to the aaaaaaaa file.
updated. Explanation: No log or list records have been created
Explanation: This message is self-explanatory. since the last SAVELOG, SAVELIST, or SAVEALL
command was issued.
User Response: Refer to ISPF Services Guide for a
description of LIBDEF return codes. User Response: Issue the SAVELOG, SAVELIST, or
SAVEALL commands only when a log or list file
member is to be written to a partitioned data set.
ISPC529 The output library ″aaaaaaaa″ is being ISPC565 ISPC565W: Warning. Line aaaaaaaa of file
updated with member ″bbbbbbbb″. ″bbbbbbbb″. Tag ″cccccccc″ and its
attributes will be ignored in the
Explanation: This is an informational message. A
conversion process.
pending log or list file is being written to the specified
output file. Explanation: This is an informational message. The
cccccccc tag is not supported by ISPF.
ISPC560 ISPC560W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. There is a conflict in the use ISPC566 ISPC566W: Warning. Line aaaaaaaa of file
of ″cccccccc″ with ″dddddddd″. ″dddddddd″ ″bbbbbbbb″. Keyword ″cccccccc=dddddddd″
is being reset to ″eeeeeeee″. found on the eeeeeeee tag will be ignored
in the conversion process but will be
Explanation: This message is self-explanatory.
syntax checked.
User Response: Change either the cccccccc or the
Explanation: This is an informational message. The
dddddddd value to remove the conflict.
attribute cccccccc is not supported by ISPF.
ISPC572 ISPC572W: Warning. Line aaaaaaaa of file ISPC580 ISPC580E: Error. Line aaaaaaaa of file
″bbbbbbbb″. The attribute ″bbbbbbbb″. cccccccc=″dddddddd″ must be
″PMTWIDTH=cccccccc″ does not provide an integer.
enough space to format the ISPF prompt
Explanation: None.
indicator ″===>″. ″PMTFMT=ISPF″ will
be ignored. User Response: Change dddddddd to an integer value.
Explanation: The combination of the length of the
prompt text plus the length of the ISPF prompt ISPC581 ISPC581W: Warning. Line aaaaaaaa of file
indicator will not fit within the prompt width specified. ″bbbbbbbb″. cccccccc=″dddddddd″ must be
an integer. cccccccc will be set to
User Response: Increase the PMTWIDTH attribute
″eeeeeeee″.
value.
Explanation: None.
ISPC577 ISPC577W: Warning. Line aaaaaaaa of file User Response: Change dddddddd to an integer value.
″bbbbbbbb″. cccccccc=″dddddddd″ maximum
length is eeeeeeee character(s). cccccccc
will be truncated to ″ffffffff″. ISPC583 ISPC583W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. cccccccc=″dddddddd″ must be
Explanation: None. an integer eeeeeeee.. cccccccc will be set to
″eeeeeeee″.
User Response: Update the DTL source to the
appropriate maximum length. Explanation: None.
User Response: Change dddddddd to an integer value.
ISPC578 ISPC578W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. cccccccc=″dddddddd″ minimum
length is eeeeeeee character(s). cccccccc ISPC584 ISPC584E: Error. Line aaaaaaaa of file
will be set to ″ffffffff″. ″bbbbbbbb″. cccccccc=″dddddddd″ must be
an integer within a range of eeeeeeee to
Explanation: None. ffffffff..
User Response: Update the DTL source to the Explanation: None.
appropriate minimum length.
User Response: Change the value dddddddd to be
within the specified range.
ISPC579 ISPC579W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. cccccccc=″dddddddd″ contains
character(s) which are not valid. cccccccc ISPC585 ISPC585W: Warning. Line aaaaaaaa of file
will be set to ″eeeeeeee″. ″bbbbbbbb″. cccccccc=″dddddddd″ must be
an integer within a range of eeeeeeee to
Explanation: ffffffff.. cccccccc will be set to ″gggggggg″.
v For panel attributes, pad characters, or expand Explanation: None.
characters, the dddddddd character has been
previously used and another character should be User Response: Change the value dddddddd to be
specified. within the specified range.
v For CHECKI tag processing of the PICT attribute, the
dddddddd character(s) are invalid for the ″VER ISPC586 ISPC586E: Error. Line aaaaaaaa of file
(xxx,PICT,string)″ panel statement. ″bbbbbbbb″. Incorrect value ″cccccccc″
v For MSGMBR tag processing of the NAME attribute, specified for dddddddd=″cccccccc″.
the dddddddd character(s) do not follow the rules for
Explanation: None.
message member names.
v For MSG tag processing of the SUFFIX attribute, the User Response: Change the cccccccc value to a valid
dddddddd character(s) are invalid or the SUFFIX is choice.
more than two characters in length.
v For processing of the MSG attribute, the dddddddd ISPC587 ISPC587W: Warning. Line aaaaaaaa of file
character(s) do not follow the rules for message ″bbbbbbbb″. Incorrect value ″cccccccc″
names. specified for dddddddd=″cccccccc″.
v For other NAME (or %varname) validation dddddddd will be set to default ″eeeeeeee″.
processing, the dddddddd character(s) do not follow Explanation: None.
the rules for variable names.
User Response: Change the cccccccc value to a valid
User Response: Correct the dddddddd character(s). choice.
ISPC588 ISPC588W: Warning. Line aaaaaaaa of file ISPC605A ISPC605AW: Warning. Line aaaaaaaa of
″bbbbbbbb″. Duplicate field names are not file ″bbbbbbbb″. The ABC tag limit of
permitted by ISPF. cccccccc=″dddddddd″ ″cccccccc″ has been exceeded. Remaining
has already been defined as a panel action bar choices will be ignored.
field name. cccccccc will be set to
Explanation: This message is self-explanatory.
″eeeeeeee″.
User Response: Remove the extra ABC tags from the
Explanation: None.
DTL source.
User Response: Choose a different dddddddd value for
the cccccccc attribute.
ISPC605B ISPC605BW: Warning. Line aaaaaaaa of
file ″bbbbbbbb″. The PDC tag limit of
ISPC600 ISPC600E: Error. Line aaaaaaaa of file ″cccccccc″ has been exceeded. Remaining
″bbbbbbbb″. Multiple Action Bars not pull-down choices will be ignored.
allowed in panel definition.
Explanation: This message is self-explanatory.
Explanation: Only one AB tag group is allowed in a
User Response: Remove the extra PDC tags from the
panel definition.
DTL source.
User Response: Remove the multiple AB tag(s).
ISPC605C ISPC605CW: Warning. Line aaaaaaaa of
ISPC601 ISPC601E: Error. Line aaaaaaaa of file file ″bbbbbbbb″. The ASSIGNI tag limit
″bbbbbbbb″. No Action Bar Choices of ″cccccccc″ has been exceeded.
defined within AB Tag. Remaining ASSIGNI tags will be
ignored.
Explanation: A minimum of one ABC tag must be
specified within the AB tag. Explanation: This message is self-explanatory.
User Response: Add ABC tag definitions to the AB User Response: Remove the extra ASSIGNI tags from
tag. the DTL source.
ISPC602 ISPC602W: Warning. Line aaaaaaaa of file ISPC605D ISPC605DW: Warning. Line aaaaaaaa of
″bbbbbbbb″. The cccccccc tag ″dddddddd″ file ″bbbbbbbb″. The XLATI tag limit of
attribute value cannot be used without a ″cccccccc″ has been exceeded. Remaining
″eeeeeeee″ attribute value. XLATI tags will be ignored.
Explanation: This message is self-explanatory. Explanation: This message is self-explanatory.
User Response: Remove the dddddddd attribute or add User Response: Remove the extra ASSIGNI tags from
an eeeeeeee attribute, as appropriate. the DTL source.
| ISPC603 ISPC603W: Warning. Line aaaaaaaa of file ISPC606 ISPC606W: Warning. Line aaaaaaaa of file
| ″bbbbbbbb″. The RUN option for the ″bbbbbbbb″. Cursor Position ″cccccccc″
| ACTION tag can only be nested within exceeds the length (dddddddd) of the
| the PDC tag or within the CHOICE tag ″eeeeeeee″ field on the ffffffff tag. The
| when a TYPE of MENU, MODEL, or conversion utility will not use the
| TUTOR has been specified on the Cursor Position. ISPF will default the
| SELFLD tag. position to 1.
Explanation: This message is self-explanatory. Explanation: This message is self-explanatory.
User Response: Remove the RUN option for this User Response: Change the cursor position to a value
ACTION tag. within the length of the eeeeeeee field.
ISPC604 ISPC604W: Warning. Line aaaaaaaa of file ISPC607 ISPC607W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. Required cccccccc ″dddddddd″ ″bbbbbbbb″. A panel has been defined
was not provided and may affect with either a Width > 80 and/or a Depth
processing. > 24 and will require a device larger
than 24x80 for display of the panel.
Explanation: The cccccccc tag text described as
dddddddd is missing. Explanation: This message is self-explanatory.
User Response: Provide the appropriate description.
ISPC608 ISPC608W: Warning. Line aaaaaaaa of file ISPC614 ISPC614W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. No text encountered ″bbbbbbbb″. The cursor position ″cccccccc″
following the cccccccc tag. specified on the PANEL tag was not set
for any field found on the panel.
Explanation: This message is self-explanatory.
Explanation: This message is self-explanatory.
User Response: Add a description to to the cccccccc
tag definition following the close tag delimiter.
ISPC615 ISPC615W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. The cursor index to table row
ISPC609 ISPC609W: Warning. Line aaaaaaaa of file
″cccccccc″ specified on the PANEL tag
″bbbbbbbb″. No text encountered
was not set for any field found on the
following the TOPINST tag.
panel.
Explanation: This message is self-explanatory.
Explanation: This message is self-explanatory.
User Response: Add a description to be placed at the
top of the panel.
ISPC616 ISPC616W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. Duplicate Action Bar Choice
ISPC610 ISPC610W: Warning. Line aaaaaaaa of file description is not allowed. ABC will not
″bbbbbbbb″. cccccccc ″dddddddd″ larger than be included on Action Bar.
the maximum allowed. ″dddddddd″ will
Explanation: This message is self-explanatory.
be truncated to eeeeeeee bytes.
User Response: Provide a unique action bar choice
Explanation: dddddddd is longer than the maximum
description.
allowed length of eeeeeeee.
User Response: Reduce the length of dddddddd to
ISPC617 ISPC617W: Warning. Line aaaaaaaa of file
eeeeeeee.
″bbbbbbbb″. No pull-down choice(s)
found for Action Bar Choice being
ISPC611 ISPC611W: Warning. Line aaaaaaaa of file processed. ABC will not be included on
″bbbbbbbb″. The cursor field ″cccccccc″ Action Bar.
specified on the PANEL tag was not
Explanation: This message is self-explanatory.
matched to any field found on the
panel. User Response: Provide at least one pull-down choice
for each ABC tag.
Explanation: This message is self-explanatory.
User Response: Correct the field name specified on
ISPC618 ISPC618W: Warning. Line aaaaaaaa of file
the PANEL tag.
″bbbbbbbb″. Undefined value ″cccccccc″
specified for ″dddddddd=cccccccc″. cccccccc
| ISPC612 ISPC612W: Warning. Line aaaaaaaa of file has not been defined in a dddddddd tag.
| ″bbbbbbbb″. The cursor row will be set to
Explanation: This message is self-explanatory.
| ″cccccccc″ as requested on the dddddddd
| tag. ″cccccccc″ may not be a valid value. User Response: Provide an cccccccc definition using an
| The Cursor Index will be checked by dddddddd tag.
| ISPF for valid position.
Explanation: This message is self-explanatory. ISPC618A ISPC618AW: Warning. Line aaaaaaaa of
file ″bbbbbbbb″. Undefined value
″cccccccc″ specified for
ISPC613 ISPC613W: Warning. Line aaaaaaaa of file
″dddddddd=cccccccc″. ″cccccccc″ has not
″bbbbbbbb″. The attribute
been defined in a eeeeeeee tag.
″cccccccc=dddddddd″ will be ignored by
the conversion utility because the Explanation: This message is self-explanatory.
CURSOR attribute has not been
User Response: Provide an cccccccc definition using an
specified.
eeeeeeee tag. For a CHOICE tag, cccccccc can be either a
Explanation: This message is self-explanatory. system generated selection choice number or a value
specified using the SELCHAR attribute.
User Response: Add the CURSOR attribute to the
PANEL definition.
ISPC630 ISPC630W: Warning. Line aaaaaaaa of file ISPC634 ISPC634W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. The ENTITY ″cccccccc″ will ″bbbbbbbb″. The cccccccc tag attribute
override the system defined entity value ″dddddddd″ is not valid unless the
dddddddd with the new value eeeeeeee. ″eeeeeeee″ attribute is also specified.
″dddddddd″ will not be used.
Explanation: This message is self-explanatory.
Explanation: This message is self-explanatory.
ISPC631 ISPC631W: Warning. Line aaaaaaaa of file User Response: Remove the dddddddd attribute or
″bbbbbbbb″. The maximum number of include the eeeeeeee attribute as part of the cccccccc tag
single choices allowed within the limit definition.
of ″ENTWIDTH=cccccccc″ has been
exceeded. The remaining sequentially
ISPC635 ISPC635W: Warning. The aaaaaaaa option
numbered CHOICE tags will be
is not valid unless the bbbbbbbb option is
ignored.
also specified. aaaaaaaa will not be used.
Explanation: This message is self-explanatory.
Explanation: This message is self-explanatory.
User Response: Increase the ENTWIDTH value, if
User Response: Remove the aaaaaaaa option or add
possible, or remove the excess CHOICE tags.
the bbbbbbbb option.
ISPC701 ISPC701W: Warning. Line aaaaaaaa of file | ISPC703D ISPC703DW: Warning. Line aaaaaaaa of
″bbbbbbbb″. Panel width has been | file ″bbbbbbbb″. Description width
exceeded. cccccccc field data will be | ″cccccccc″ will not fit within the Panel
truncated. | width and will be changed to
| ″dddddddd″.
Explanation: This message is self-explanatory.
Explanation: This message is self-explanatory.
User Response:
v Increase the panel width, if possible. User Response:
v Review the generated ISPF panel source result and v Increase the panel width, if possible.
adjust field widths or spacing as necessary. v Review the generated ISPF panel source result and
adjust field widths or spacing as necessary.
ISPC702 ISPC702W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. cccccccc tag was specified ISPC704A ISPC704AW: Warning. Line aaaaaaaa of
without the NAME or DATAVAR file ″bbbbbbbb″. cccccccc tag entry width
keyword and will cause the absence of value is ″0″ and may affect the display
the field on the panel. of the entry field.
Explanation: The field could not be formatted because Explanation: There is insufficient space for the entry
no field identifier was provided. field.
User Response: Add the DATAVAR attribute to the User Response:
DTL source file. v Increase the panel width, if possible.
v Review the generated ISPF panel source result and
adjust field widths or spacing as necessary.
| ISPC703A ISPC703AW: Warning. Line aaaaaaaa of
| file ″bbbbbbbb″. Entry width ″cccccccc″
| will not fit within the Panel width and ISPC704B ISPC704BW: Warning. Line aaaaaaaa of
| will be changed to ″dddddddd″ . file ″bbbbbbbb″. cccccccc tag prompt width
value is ″0″ and may affect the display
Explanation: This message is self-explanatory.
of the prompt field.
User Response:
Explanation: There is insufficient space for the field
v Increase the panel width, if possible.
prompt.
v Review the generated ISPF panel source result and
adjust field widths or spacing as necessary. User Response:
v Increase the panel width, if possible.
v Review the generated ISPF panel source result and
| ISPC703B ISPC703BW: Warning. Line aaaaaaaa of
adjust field widths or spacing as necessary.
| file ″bbbbbbbb″. Prompt width ″cccccccc″
| will not fit within the Panel width and
| will be changed to ″dddddddd″. ISPC704C ISPC704CW: Warning. Line aaaaaaaa of
file ″bbbbbbbb″. cccccccc tag description
Explanation: This message is self-explanatory.
width value is ″0″ and may affect the
User Response: display of the description field.
v Increase the panel width, if possible.
Explanation: There is insufficient space for the field
v Review the generated ISPF panel source result and
description.
adjust field widths or spacing as necessary.
User Response:
v Increase the panel width, if possible.
| ISPC703C ISPC703CW: Warning. Line aaaaaaaa of
v Review the generated ISPF panel source result and
| file ″bbbbbbbb″. Choice width ″cccccccc″
adjust field widths or spacing as necessary.
| will not fit within the Panel width and
| will be changed to ″dddddddd″.
ISPC705A ISPC705AW: Warning. Line aaaaaaaa of
Explanation: This message is self-explanatory.
file ″bbbbbbbb″. The ″SELWIDTH″ value
User Response: of the SELFLD tag is not large enough
v Increase the panel width, if possible. to contain the entry field.
v Review the generated ISPF panel source result and
Explanation: This message is self-explanatory.
adjust field widths or spacing as necessary.
User Response:
v Increase the panel width, if possible.
v Review the generated ISPF panel source result and
adjust field widths or spacing as necessary.
Explanation: The REQUIRED and MSG attributes are User Response: Set the width of the scrollable area to
not valid for an output field. 20 or more.
| ISPC715A ISPC715AW: Warning. Line aaaaaaaa of | ISPC719A ISPC719AW: Warning. Line aaaaaaaa of
| file ″bbbbbbbb″. Duplicate ″CHECKVAR″ | file ″bbbbbbbb″. Inconsistent use of
| name ″cccccccc″ found on a CHOICE tag. | Mnemonics within ″cccccccc″ entries.
| The ″cccccccc″ variable name cannot be | CUA requires that all ″cccccccc″ entries
| repeated for more than one CHOICE if | must have a Mnemonic or none can.
| SELFLD TYPE=MULTI. This name will
Explanation: This message is self-explanatory.
| be accepted but results are
| unpredictable. User Response: ISPF supports the Mnemonic tag only
within the ABC and PDC tags.
Explanation: This message is self-explanatory.
If this message is the result of providing a Mnemonic
User Response: For a multi-choice selection list, each
tag within a CHOICE tag, consider removing the tag
CHECKVAR name should be unique.
from the DTL source file.
If this message relates to ABC or PDC tag processing,
| ISPC715B ISPC715BW: Warning. Line aaaaaaaa of
consider adding a Mnemonic tag to the ABC or PDC
| file ″bbbbbbbb″. Duplicate ″MATCH″
tag identified within the message.
| value ″cccccccc″ used on a CHOICE tag.
| The ″cccccccc″ value cannot be repeated
| for more than one CHOICE if SELFLD | ISPC719B ISPC719BW: Warning. Line aaaaaaaa of
| TYPE=SINGLE. This value will be | file ″bbbbbbbb″. A duplicate mnemonic
| accepted but results are unpredictable. | value has been found during processing
| of a ″cccccccc″ tag. Only one mnemonic
Explanation: This message is self-explanatory.
| may be specified for each ″cccccccc″.
| Mnemonic characters used within a set
| ISPC716 ISPC716W: Warning. Line aaaaaaaa of file | of tags (ABC, PDC or CHOICE) must be
| ″bbbbbbbb″. Inconsistent CHECKVAR | unique.
| value found on CHOICE tag. The
Explanation: This message is self-explanatory.
| CHECKVAR variable name must be the
| same for all CHOICE tags if SELFLD User Response: Remove the duplicate use of the M
| TYPE=SINGLE. This name will be (Mnemonic) tag coded on the ″cccccccc″ tag.
| accepted but results are unpredictable.
Explanation: This message is self-explanatory. ISPC719C ISPC719CW: Warning. Line aaaaaaaa of
file ″bbbbbbbb″. A DBCS mnemonic value
User Response: For a single choice selection list, each
has been found within a ″cccccccc″ tag.
CHECKVAR name should be unique.
Mnemonic characters must be single
byte format. The specified mnemonic
ISPC717 ISPC717W: Warning. Line aaaaaaaa of file character will not be used.
″bbbbbbbb″. Inconsistent use of MENU
Explanation: This message is self-explanatory.
keyword on the PANEL tag. No
selection choice list was created on User Response: Specify a single byte character for the
panel ″cccccccc″. mnemonic.
Explanation: A PANEL specified with MENU
keyword should include a SELFLD tag specified as ISPC719D ISPC719DW: Warning. Line aaaaaaaa of
TYPE=MENU. file ″bbbbbbbb″. The mnemonic ″cccccccc″
specified for the ″dddddddd″ tag
User Response: Remove the MENU attribute from the
description is not valid and will not be
PANEL tag, or add an option menu selection list with
used. The mnemonic character must be
the SELFLD tag.
in the range ″A-Z″, ″a-z″, or ″0-9″.
Explanation: The mnemonic character must be in the
ISPC718 ISPC718E: Error. Line aaaaaaaa of file
range A-Z, a-z, or 0-9.
″bbbbbbbb″. More than one ″cccccccc″ tag
found within ″dddddddd″. Only 1 User Response: Change the M tag to specify a valid
″cccccccc″ tag can be used within each character.
″dddddddd″ tag.
Explanation: The ″cccccccc″ tag can only be specified
one time within the ″dddddddd″ tag.
ISPC719F ISPC719FW: Warning. Line aaaaaaaa of | ISPC723 ISPC723W: Warning. Line aaaaaaaa of file
file ″bbbbbbbb″. A duplicate mnemonic | ″bbbbbbbb″. The tag language has been
value has been found during processing | changed for the cccccccc tag. The
of a ″cccccccc″ tag. The conversion utility | attribute ″dddddddd″ has been removed
will attempt to automatically select a | from the cccccccc tag and will be ignored
mnemonic character to replace the | in this conversion. You should remove
specified value. Review the generated | the dddddddd reference from your tag
panel and if the resulting mnemonic | source.
selection is unsatisfactory, add
Explanation: This message is self-explanatory.
Mnemonic tags to remove the duplicate
condition. User Response: Change the DTL source to remove the
entry ″dddddddd″.
Explanation: This message is self-explanatory.
User Response: Add additional Mnemonic tag(s) as
ISPC729 ISPC729W: Warning. Line aaaaaaaa of file
required to prevent the automatic mnemonic character
″bbbbbbbb″. The ″cccccccc″ attribute has
selection from generating a mnemonic which conflicts
been specified on a ″dddddddd″ tag but
with your choice for the current item.
the attribute ″eeeeeeee″ was not specified
(or is not valid). The ″cccccccc″ attribute
| ISPC720 ISPC720W: Warning. Line aaaaaaaa of file will be reset to blank.
| ″bbbbbbbb″. The tag language has been
Explanation: The use of cccccccc depends on the
| changed for the cccccccc tag. The
specification of eeeeeeee.
| attribute ″dddddddd″ has been replaced
| by ″eeeeeeee″. The conversion utility will User Response: Either add the eeeeeeee attribute to the
| use the value of ″dddddddd″ as ″eeeeeeee″. DTL source or correct other related coding to make the
eeeeeeee attribue valid.
Explanation: This message is self-explanatory.
User Response: Change the DTL source value
dddddddd to eeeeeeee.
| ISPC730 ISPC730W: Warning. Line aaaaaaaa of file
| ″bbbbbbbb″. The required attribute
| ″DATAVAR″ is missing from the
| ISPC721 ISPC721W: Warning. Line aaaaaaaa of file | DTAFLD tag. The ″NAME″ value will
| ″bbbbbbbb″. The tag language has been | become the panel field name. You
| changed for the cccccccc tag. The | should add the ″DATAVAR″ attribute to
| attribute value ″dddddddd″ has been | your tag source. It is recommended that
| replaced by ″eeeeeeee″. The conversion | you code both attributes with the same
| utility will accept the entry | value.
| ″ffffffff=dddddddd″. However, you should
Explanation: This message is self-explanatory.
| change your source to use the new
| attribute value (″ffffffff=eeeeeeee″). User Response: Add the DATAVAR attribute using
the same name value specified for the NAME attribute.
Explanation: This message is self-explanatory.
User Response: Change the DTL source value
ISPC731 ISPC731W: Warning. Line aaaaaaaa of file
″dddddddd″ to ″eeeeeeee″.
″bbbbbbbb″. Both ″DATAVAR″ and
″NAME″ are specified on the DTAFLD
| ISPC722 ISPC722W: Warning. Line aaaaaaaa of file tag, but they have different values. The
| ″bbbbbbbb″. The tag language has been ″DATAVAR″ value will become the
| changed for the cccccccc tag. The panel field name. It is recommended
| attribute value ″dddddddd″ has been that you code both attributes with the
| removed from the cccccccc tag and will same value.
| be ignored in this conversion. You
Explanation: This message is self-explanatory.
| should update your source file to
| remove the ″eeeeeeee=dddddddd″ entry. User Response: Change the NAME attribute to the
same value as the DATAVAR attribute.
Explanation: This message is self-explanatory.
User Response: Change the DTL source to remove the
entry ″eeeeeeee=dddddddd″.
ISPC732 ISPC732W: Warning. Line aaaaaaaa of file ISPC737 ISPC737W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. The ″AUTOTAB=YES″ ″bbbbbbbb″. Both ″PAD″ and ″PADC″
attribute is in conflict with ″USAGE″ on attributes have been specified on the
the cccccccc tag. AUTOTAB will be ″cccccccc″ tag. The value of ″PADC″ will
changed to ″NO″. be used.
Explanation: This message is self-explanatory. Explanation: This message is self-explanatory.
User Response: Change AUTOTAB=YES to User Response: Remove either the PAD or PADC
AUTOTAB=NO, or remove the AUTOTAB attribute attribute from the DTL source.
from the DTL source.
ISPC738A ISPC738AW: Warning. Line aaaaaaaa of
ISPC733 ISPC733W: Warning. Line aaaaaaaa of file file ″bbbbbbbb″. The ″EXTEND=ON″
″bbbbbbbb″. The ″cccccccc″ attribute is not attribute specification is not valid on a
valid without a valid ″DEPTH″ value. ″cccccccc″ tag within a horizontal region.
The ″cccccccc″ attribute will be ignored. The ″EXTEND″ attribute will be
ignored.
Explanation: This message is self-explanatory.
Explanation: This message is self-explanatory.
User Response: Remove the cccccccc attribute from the
DTL source. User Response: Remove the EXTEND attribute from
the DTL source.
ISPC734 ISPC734W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. The ″EXTEND″ attribute has ISPC738B ISPC738BW: Warning. Line aaaaaaaa of
already been specified for this panel or file ″bbbbbbbb″. The ″EXTEND=ON″
″EXTEND″ is not valid in this tag attribute specification is not valid on a
nesting configuration. The ″EXTEND″ ″cccccccc″ tag formatted horizontally. The
attribute will be ignored. ″EXTEND″ attribute will be ignored.
Explanation: This message is self-explanatory. Explanation: This message is self-explanatory.
User Response: Remove the EXTEND attribute from User Response: Remove the EXTEND attribute from
the DTL source. the DTL source.
ISPC735 ISPC735W: Warning. Line aaaaaaaa of file ISPC738C ISPC738CW: Warning. Line aaaaaaaa of
″bbbbbbbb″. The ″SCROLL″ attribute has file ″bbbbbbbb″. The ″EXTEND=FORCE″
already been specified for this panel attribute specification is coded on a
either on an enclosing AREA tag or on ″cccccccc″ tag within a horizontal region.
another DA tag. The ″SCROLL″ The resulting panel will not display
attribute for this DA tag will be unless the extendable portion of the
ignored. panel is below all other fields or text on
the panel.
Explanation: This message is self-explanatory.
Explanation: This message is self-explanatory.
User Response: Remove the SCROLL attribute from
the DTL source. User Response: Verify the panel by displaying it using
ISPF Dialog Test.
ISPC736 ISPC736E: Error. Line aaaaaaaa of file
″bbbbbbbb″. The ″cccccccc″ attribute has ISPC738D ISPC738DW: Warning. Line aaaaaaaa of
been specified for this panel and is in file ″bbbbbbbb″. The ″EXTEND=FORCE″
conflict with table display. The panel attribute specification is coded on a
will not be saved. ″cccccccc″ tag formatted horizontally. The
resulting panel will not display unless
Explanation: This message is self-explanatory.
the extendable portion of the panel is
User Response: Remove the cccccccc attribute from the below all other fields or text on the
DTL source. panel.
Explanation: This message is self-explanatory.
User Response: Verify the panel by displaying it using
ISPF Dialog Test.
ISPC767A ISPC767AW: Warning. Line aaaaaaaa of ISPC769 ISPC769W: Warning. Line aaaaaaaa of file
file ″bbbbbbbb″. A CHOICE tag that ″bbbbbbbb″. The number of SELFLD tags
specified the UNAVAIL attribute has containing unavailable choices has
also specified the RP (Reference Phrase) exceeded the maximum of 36.
tag as part of the CHOICE tag text. ISPF Remaining SELFLD tags will use the
does not support Reference Phrases on ″ZS#″ prefix for variable names used for
unavailable choices. The UNAVAIL (and unavailable choice text fields. If
UNAVAILMAT) attribute specifications duplicate field names result, the panel
are ignored. cannot be displayed.
Explanation: ISPF does not support Reference Phrases Explanation: The number of SELFLD tags containing
on unavailable choices. The conversion utility will unavailable choices has exceeded the maximum that
format the Reference Phrase and will ignore the can be successfully created by the conversion utility.
UNAVAIL (and UNAVAILMAT) attribute specifications.
User Response: Revise the panel to limit the number
User Response: If unavailable choice support is of SELFLD tags with unavailable choices to 36.
required for this CHOICE, remove the RP (Reference
Phrase) tag specification from the choice text and
ISPC770 ISPC770W: Warning. Line aaaaaaaa of file
reconvert the panel. If unavailable choice support is not
″bbbbbbbb″. The cccccccc tag text
required, remove the UNAVAIL (and UNAVAILMAT)
″dddddddd″ is not valid when the
attributes from this CHOICE tag.
TYPE=NONE attribute is either
specified or defaulted. The text is
ISPC767B ISPC767BW: Warning. Line aaaaaaaa of ignored.
file ″bbbbbbbb″. A CHOICE tag that
Explanation: Text on the cccccccc tag is in conflict with
specified the UNAVAIL attribute has
the TYPE=NONE attribute which is defined as creating
also specified the HP (Emphasized Text)
a blank divider line.
tag as part of the CHOICE tag text. ISPF
does not support Emphasized Text on User Response: Remove the text from the cccccccc tag,
unavailable choices. The UNAVAIL (and or change the TYPE attribute.
UNAVAILMAT) attribute specifications
are ignored.
ISPC771 ISPC771W: Warning. Line aaaaaaaa of file
Explanation: ISPF does not support Emphasized Text ″bbbbbbbb″. The cccccccc tag text
on unavailable choices. The conversion utility will ″dddddddd″ is not valid unless the
format the Emphasized Text and will ignore the FORMAT attribute is specified. The text
UNAVAIL (and UNAVAILMAT) attribute specifications. is ignored.
User Response: If unavailable choice support is Explanation: Text on the cccccccc tag is not accepted
required for this CHOICE, remove the HP (Emphasized unless the FORMAT attribute is also specified.
Text) tag specification from the choice text and
reconvert the panel. If unavailable choice support is not User Response: Remove the text from the cccccccc tag,
required, remove the UNAVAIL (and UNAVAILMAT) or add the FORMAT attribute.
attributes from this CHOICE tag.
ISPC772 ISPC772W: Warning. Line aaaaaaaa of file
ISPC768 ISPC768W: Warning. Line aaaaaaaa of file ″bbbbbbbb″. The cccccccc tag text
″bbbbbbbb″. A CHOICE tag that is used to ″dddddddd″ is not valid within a
build a COMBO list cannot have user horizontal region. The text is ignored.
defined ″cccccccc″ tag text. The ″cccccccc″ Explanation: Text on the cccccccc tag is not accepted
tag is ignored. within a horizontal region.
Explanation: The conversion utility automatically User Response: Remove the text from the cccccccc tag.
generates Point-and-Shoot entries for CHOICEs that are
part of a COMBO list.
ISPC773 ISPC773W: Warning. Line aaaaaaaa of file
User Response: Remove any Emphasized Text (HP), ″bbbbbbbb″. The CHDIV tag is not
Reference Phrase (RP), or Point-and-Shoot (PS) tag supported for selection lists that specify
definitions within CHOICE tag. LISTTYPE=COMBO. The tag is syntax
checked but will be ignored during
panel formatting.
Explanation: The LISTTYPE=COMBO specification
creates a single input field in the panel )BODY section.
Divider lines can only be used within choice lists
ISPC856 ISPC856W: Warning. Line aaaaaaaa of file ISPC868 ISPC868E: Error. Line aaaaaaaa of file
″bbbbbbbb″. The panel width ″cccccccc″ ″bbbbbbbb″. The use of the ″cccccccc″ tag
will not fit within the output file record is limited to the first 99 scrollable areas.
length of ″dddddddd″. The WIDTH of Panel will not be saved.
panels being converted with the
Explanation: The naming structure for Reference
NOPREP option must be less than or
Phrases is ZRPxxyyy, and the naming structure for
equal to the record length of the output
point-and-shoot entries is ZPSxxyyy, where xx is 00 for
panel file.
the panel body, or 01 - 99 for the number of the
Explanation: This message is self-explanatory. scrollable area, and yyy is the number of the entries
within area xx. The maximum number of scrollable
User Response: Reduce the value of the WIDTH
areas that can contain Reference Phrases or
attribute or specify an output panel file with a larger
point-and-shoot entries is 99.
record length.
User Response: Remove any RP or PS tags found in
the scrollable areas that are beyond the defined limit.
ISPC859 ISPC859W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. The LSTFLD tag (and nested
LSTCOL tags) will be formatted at the ISPC869 ISPC869E: Error. Line aaaaaaaa of file
bottom of the panel for use by ISPF ″bbbbbbbb″. The maximum of 999 uses of
table display. the ″cccccccc″ tag for a dddddddd panel
section has been exceeded. Panel will
Explanation: This message is self-explanatory.
not be saved.
User Response: This message is issued when the
Explanation: The naming structure for Reference
LSTFLD tag group is followed by other panel tags.
Phrases is ZRPxxyyy, and the naming structure for
point-and-shoot entries is ZPSxxyyy, where xx is 00 for
| ISPC865 ISPC865W: Warning. Line aaaaaaaa of file the panel body, or 01 - 99 for the number of the
| ″bbbbbbbb″. The comment ″cccccccc″ does scrollable area, and yyy is the number of the Reference
| not conform to DTL rules for the use of Phrase or point-and-shoot entry within area xx. The
| the ’-’ character. This comment is maximum number of entries within any area xx is 999.
| accepted for the conversion. Please
User Response: Remove any RP or PS tags found in
| update the tag source file to DTL
the dddddddd section that are beyond the defined limit.
| comment syntax standards.
Explanation: The rules for DTL comments allow only
| ISPC890A ISPC890AW: Warning. Line aaaaaaaa of
single ″-″ (dash) characters within the comment text.
| file ″bbbbbbbb″. The PARM1 attribute
Multiple contiguous ″-″ (dash) characters indicate
| must be specified to provide the
comment continuation text.
| mask-character for the PICTCN verify
User Response: Revise the comment to use only single | statement.
″-″ (dash) characters within the comment text.
| Explanation: The PICTCN verify statement requires a
| mask-character to represent a picture character in the
| ISPC866 ISPC866W: Warning. Line aaaaaaaa of file | field-mask. DTL does not allow characters C, c, A, a, N,
| ″bbbbbbbb″. The GML source ″cccccccc″ | n, X, x, 9, left parenthesis, right parenthesis, comma,
| does not conform to DTL rules for | single quote (’) or double quote (″) as the
| comment continuation. This syntax is | mask-character.
| accepted for the conversion. Please
| User Response: Provide the PARM1 attribute with a
| update the tag source file to DTL
| valid mask-character.
| comment syntax standards.
Explanation: Each line of a continued comment
| ISPC890B ISPC890BW: Warning. Line aaaaaaaa of
should begin with the characters ″--″. ISPDTLC treats
| file ″bbbbbbbb″. The PARM2 attribute
all lines following an open comment delimiter (″<!−−″)
| must be specified to provide the
as comment continuation until the ending comment
| field-mask for the PICTCN verify
delimiter (″ ″) is encountered.
| statement.
User Response: Correct the comment syntax by
| Explanation: The PICTCN verify statement requires a
placing the comment continuation characters ″--″ at the
| field-mask to describe the format of the field to be
start of each comment continuation line.
| verified. The field-mask is a combination of character
| constants and the mask-character specified with
| attribute PARM1.
| ISPC897 ISPC897W: Warning. Line aaaaaaaa of file ISPC909 ISPC909W: Warning. Line aaaaaaaa of file
| ″bbbbbbbb″. Position ″cccccccc″ (character ″bbbbbbbb″. CHECKI can be specified
| ″dddddddd″) of field-mask ″eeeeeeee″ does only once. First specification will be
| not correspond to a valid picture string used.
| character in verification string ″ffffffff″.
Explanation: This message is self-explanatory.
| Explanation: The PICTCN verify statement requires
User Response: ISPDTLC supports only one CHECKI
| that each mask-character within the field-mask
tag within each CHECKL definition.
| correspond to a valid picture string character in the
| relative position of the verification string.
ISPC910 ISPC910W: Warning. Line aaaaaaaa of file
| User Response: Provide the PARM3 attribute with a
″bbbbbbbb″. Variable by the same name
| valid verification string that contains a picture string
″cccccccc″ was already defined.
| character for each mask-character found within the
| field-mask. Explanation: This message is self-explanatory.
User Response: Each VARCLASS name and VARDCL
| ISPC898 ISPC898W: Warning. Line aaaaaaaa of file name must be unique.
| ″bbbbbbbb″. The constant in position
| cccccccc (character ″dddddddd″) of
| field-mask ″eeeeeeee″ does not correspond | ISPC911 ISPC911W: Warning. Line aaaaaaaa of file
| to the constant in the relative position | ″bbbbbbbb″. The VARCLASS attribute
| of verification string ″ffffffff″. | cccccccc requires a dddddddd value. The
| conversion process will continue but
| Explanation: The PICTCN verify statement requires | defaults may be affected. Please update
| that each character constant within the field-mask | your tag source file to contain a valid
| correspond to the relative position of the verification | dddddddd value.
| string.
Explanation: This message is self-explanatory.
| User Response: Provide the PARM3 attribute with a
| valid verification string that contains a matching User Response: Add the missing information to the
| character constant for each character constant found TYPE=cccccccc attribute.
| within the field-mask.
ISPC912 ISPC912W: Warning. Line aaaaaaaa of file
ISPC901 ISPC901W: Warning. Line aaaaaaaa of file ″bbbbbbbb″. cccccccc is a required attribute
″bbbbbbbb″. Horizontal AREA formatting when TYPE=dddddddd.. CHECKI tag will
has reached the panel width. Tags be ignored.
following this AREA will be formatted Explanation: The required attribute cccccccc is not
below the current AREA(s), beginning present.
at the left edge of the panel.
User Response: Add the required attribute
Explanation: An AREA tag specifying DIR=HORIZ is information.
in process, and the width of the AREA matches or
exceeds the PANEL width. ISPDTLC will format the
current AREA as specified. The next AREA or other tag ISPC913 ISPC913W: Warning. Line aaaaaaaa of file
will continue formatting at the left edge of the panel. ″bbbbbbbb″. cccccccc attribute value does
not correspond with dddddddd.. CHECKI
User Response: Review the WIDTH and DIR tag will be ignored.
attributes on the AREA tags. The combined width of
horizontally formatted AREAs cannot exceed the Explanation: The PARM2 data is not valid for
PANEL width. TYPE=CHARS.
User Response: Specify one of the listed character
ISPC908 ISPC908W: Warning. Line aaaaaaaa of file strings as documented in DTL Guide and Reference
″bbbbbbbb″. CHECKI tag syntax error.
CHECKI tag will be discarded. ISPC914 ISPC914W: Warning. Line aaaaaaaa of file
Explanation: This message is self-explanatory. ″bbbbbbbb″. PARM1 is larger than
PARM2. CHECKI tag will be ignored.
User Response: Refer to previous log messages for
more information about the syntax errors. Explanation: PARM2 specifies the high bound of a
RANGE check and must be larger than the low bound
specified by PARM1.
User Response: Adjust the range values so that
| ISPC935 ISPC935W: Warning. Line aaaaaaaa of file | ISPC939 ISPC939W: Warning. Line aaaaaaaa of file
| ″bbbbbbbb″. ″USAGE″ has been specified | ″bbbbbbbb″. The VARCLASS attribute
| on the XLATL tag. This attribute has | specified on a VARDCL tag found
| been removed from the tag language. | within the PANEL tag will be ignored.
| ″USAGE″ should be determined by the | VARDCL within the panel tag is
| referencing tag (explicit or implied). | supported for prior release level
| ″USAGE″ should be removed from the | attributes only. The VARCLASS
| XLATL tag. | attribute is valid only on VARDCL tags
| found outside the PANEL tag. You
Explanation: This message is self-explanatory.
| should update your tag source file to
User Response: Remove the USAGE coding from the | remove the complete
XLATL tag. | VARLIST/VARDCL tag group located
| within the PANEL tag.
ISPC936 ISPC936W: Warning. Line aaaaaaaa of file Explanation: This message is self-explanatory.
″bbbbbbbb″. ″VARDCL″ was not found for
User Response: Remove the VARLIST tag group
| variable cccccccc specified on the
within the PANEL definition.
dddddddd tag. Each variable should be
specified by a ″VARDCL″ tag.
ISPC940 ISPC940E: Error. Line aaaaaaaa of file
Explanation: This message is self-explanatory.
″bbbbbbbb″. The VARCLASS tag to define
User Response: Add a VARDCL tag for each panel ″cccccccc″ must precede the VARDCL tag
variable. which references ″cccccccc″.
Explanation: This message is self-explanatory.
| ISPC937 ISPC937W: Warning. Line aaaaaaaa of file
User Response: Place the VARCLASS tag for cccccccc
| ″bbbbbbbb″. A VARLIST tag has been
before the VARDCL tag which references it.
| found both outside and within the
| PANEL tag. The conversion utility does
| not support a mixed occurrence of ISPC941 ISPC941E: Error. Line aaaaaaaa of file
| VARLIST. The VARLIST found within ″bbbbbbbb″. All VARCLASS tags must
| the PANEL tag will be ignored for this precede any VARLIST tag in the source
| conversion. You should update your tag file.
| source file to remove the VARLIST tags
Explanation: This message is self-explanatory.
| found within the PANEL tag.
User Response: Place all VARCLASS tags before any
Explanation: This message is self-explanatory.
VARLIST tag group.
User Response: Remove the VARLIST tag group
within the PANEL definition.
ISPC943 ISPC943W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. Length=″cccccccc″ must be an
| ISPC938 ISPC938W: Warning. Line aaaaaaaa of file even number for ″TYPE=DBCS″.
| ″bbbbbbbb″. A VARDCL tag has been ″cccccccc″ has been changed to
| found within the PANEL tag for ″dddddddd″.
| variable ″cccccccc″. The VARDCL found
Explanation: This message is self-explanatory.
| within the PANEL tag will be ignored
| because a VARLIST was found outside User Response: Change the cccccccc value to an even
| the PANEL tag. You should update your number.
| tag source file to remove the complete
| VARLIST/VARDCL tag group located
| within the PANEL tag. ISPC944 ISPC944W: Warning. Line aaaaaaaa of file
″bbbbbbbb″. cccccccc=″dddddddd″ must be
Explanation: This message is self-explanatory. an even number for field ″eeeeeeee″
which is specified as DBCS. ″dddddddd″
User Response: Remove the VARLIST tag group
has been changed to ″ffffffff″.
within the PANEL definition.
Explanation: This message is self-explanatory.
User Response: Change the dddddddd value to an even
number.
ISPC970 ISPC970W: Warning. ISPDTLC received ISPC976 ISPC976E: Error. EXECIO completed
a non-zero return code from EXECIO unsuccessfully.
while processing ’aaaaaaaa’. Refer to the
Explanation: This message is self-explanatory. Review
’bbbbbbbb’ documentation for an
any immediately previous messages for additional
explanation of EXECIO return code
information.
’cccccccc’
User Response: If message recurs , notify IBM service.
Explanation: This message is self-explanatory.
User Response: Correct the condition causing return
code cccccccc.
| ISPC978 ISPC978W: Warning. ISPDTLC received
| a non-zero return code from ISPF
| service ’aaaaaaaa’ while processing
ISPC971 ISPC971E: Error. Check file allocation | ’bbbbbbbb’. Please refer to the ISPF
for ’aaaaaaaa..’. | documentation for an explanation of
| ’aaaaaaaa’ return code ’cccccccc’
Explanation: The ISPDTLC EXECIO write routine has
encountered an error on data set ’aaaaaaaa’. This Explanation: This message is self-explanatory.
message will be followed by message ISPC972 if space
User Response: Refer to the ISPF documentation for a
allocated is equal to space used. This message will be
more complete description of ’aaaaaaaa’ return codes.
followed by message ISPC973 if directory blocks
allocated is equal to directory blocks used.
ISPC979 ISPC979W: Warning. Refer to the
User Response: Reallocate the data set name with
’aaaaaaaa’documentation for a more
more space or with additional directory blocks.
complete description of EXECIO return
codes.
ISPC972 ISPC972W: Warning. File space allocated
Explanation: This message is self-explanatory.
= file space used.
User Response: Refer to the ’aaaaaaaa’ documentation
Explanation: This message follows message ISPC971 if
for a more complete description of EXECIO return
space allocated is equal to space used.
codes.
User Response: Reallocate the data set name with
more space.
ISPC980A ISPC980AE: Error. Do not specify a
member name for the aaaaaaaa file
ISPC973 ISPC973W: Warning. Directory blocks sequential data set ″bbbbbbbb″.
allocated = directory blocks used.
Explanation: A sequential data set name has been
Explanation: This message follows message ISPC971 if entered with a member name on the ISPDTLC
directory blocks allocated is equal to directory blocks invocation panel for the log file or list file.
used.
User Response: Correct the data set name by
User Response: Reallocate the data set name with removing the member name.
additional directory blocks.
ISPC980B ISPC980BE: Error. Do not specify a
ISPC974 ISPC974W: Warning. Data has been member name for the aaaaaaaa file
truncated during DISKW operation. partitioned data set ″bbbbbbbb″.
Explanation: The length of the output record exceeds Explanation: A partitioned data set name has been
the LRECL of the output file. entered with a member name on the ISPDTLC
invocation panel.
User Response: Verify that the record length of the file
is correct. User Response: Correct the data set name by
removing the member name.
ISPC975 ISPC975W: Warning. End of file reached
before the specified number of records
have been read.
Explanation: This message is self-explanatory.
User Response: If message recurs , notify IBM service.
ISPC992 ISPC992E: Error. Incorrect syntax: ISPD001 Allocation failed - DAIR RC = aaaaaaaa
aaaaaaaa=″bbbbbbbb″ contains character(s) dec, DARC = bbbbbbbb hex.
which are not valid. The first character
Explanation: A TSO allocation failed. The Dynamic
of ″bbbbbbbb″ must be ″A-Z″ or ″#, $, @″.
Allocation Interface Return Code (DAIR) and the
Remaining characters must be ″A-Z″, ″#,
Dynamic Allocation Return Code have been supplied.
$, @″ or ″0-9″.
For more information on these return codes, see the
Explanation: This message is self-explanatory. System Programmer response below.
User Response: Remove the invalid characters from User Response: Contact your system programmer.
the invocation syntax.
System Programmer Response: The DAIR and DARC
codes are listed in the ISPF tutorial. Enter HELP to get
ISPC994 ISPC994E: Error. Option is not valid: the first tutorial panel, then enter INDEX on the
″aaaaaaaa″. command line. Enter D on the command line to get to
the topics screen, and select D1 to get the listing of the
Explanation: The invocation syntax aaaaaaaa is not
DAIR and DARC codes.
valid.
User Response: Remove the invalid value aaaaaaaa
ISPD002 Data set not found - ’aaaaaaaa’ not on
from the invocation syntax.
volume ’bbbbbbbb’.
Explanation: The data set specified was not found on
ISPC996 ISPC996E: Error. Duplicate option:
the volume specified.
″aaaaaaaa″.
User Response: Verify the data set name and the
Explanation: The invocation syntax aaaaaaaa is a
volume. Contact your system programmer.
duplicate value.
System Programmer Response: Verify the data set
User Response: Remove the duplicate value aaaaaaaa
name and the volume. If the data set name is valid,
from the invocation syntax.
determine its volume location.
ISPC998 ISPC998E: Error. The ISPDTLC User Response: Contact your system programmer.
invocation syntax is: ″ISPDTLC
System Programmer Response: If you are unable to
source-filespec ( invocation options″.
determine the problem with the listed volume, contact
The ″(″ is required to identify the
IBM support.
invocation options.
Explanation: This message is self-explanatory.
ISPD004 Volume ’aaaaaaaa’ not avail - Volume not
User Response: The invocation syntax requires that mounted or not authorized for your use.
the ’source-filespec’ and invocation options be
Explanation: The volume you requested is not
separated by the character ″(″. Respecify the invocation
mounted, or you are not authorized to use this volume.
command, including the ″(″ delimiter.
User Response: Contact your system programmer.
ISPC999 ISPC999E: Conversion terminated due to System Programmer Response: Determine why this
severe error. user is unable to use the volume.
Explanation: This message is self-explanatory.
ISPD005 Data set in use - Data set ’aaaaaaaa’ in
User Response: This message follows one or more
use by another user, try later.
other errors in the log. Refer to the earlier error
messages for the problem explanation. Explanation: Another user is using this data set. Try
to access this data set later.
User Response: Try to access the data set later.
ISPD006 VTOC full on vol ’aaaaaaaa’ - No room ISPD012 Syntax error member name - Member
in volume table of contents for more name ’aaaaaaaa’ contains invalid special
data sets. character.
Explanation: The Volume Table of Contents (VTOC) Explanation: The member name specified contains an
on this volume is full. Another data set cannot be invalid special character.
added to the VTOC.
User Response: Correct the syntax of the member
User Response: Provide the above information to the name.
system programmer.
System Programmer Response: Correct the DASD ISPD013 Invalid data set name - Syntax error in
space problem. data set name ’aaaaaaaa’.
Explanation: This message is self-explanatory.
ISPD007 No space on vol ’aaaaaaaa’ - Insufficient
User Response: Correct the syntax of the data set
space for data set ’bbbbbbbb’.
name.
Explanation: The volume specified has insufficient
space for the data set specified.
ISPD014 Data set not cataloged - ’aaaaaaaa’ was
User Response: Contact your system programmer. not found in catalog.
System Programmer Response: Correct the DASD Explanation: The data set was not found in the
space problem. catalog.
User Response: Enter a valid data set name.
ISPD008 Invalid index structure - Dsname
’aaaaaaaa’ index conflict.
ISPD015 Dd dynams exhausted - Data set
Explanation: The TSO DAIR routine has reported a ’aaaaaaaa’ cannot be allocated.
problem with this data set.
Explanation: You will be unable to allocate additional
User Response: Contact your system programmer. ddnames.
System Programmer Response: Correct the DASD User Response: Contact your system programmer.
index problem.
ISPD016 Duplicate data set name - Data set
ISPD009 DDNAME not found - DDNAME ’aaaaaaaa’ already exists.
’aaaaaaaa’ not allocated.
Explanation: You cannot create a data set with this
Explanation: The ddname has not been allocated. name.
User Response: Allocate the ddname or contact the User Response: Create your data set using another
responsible programmer. name.
ISPD010 File name in use - File name ISPD017 Data set not partitioned - Member
(DDNAME) ’aaaaaaaa’ is allocated to ’aaaaaaaa’ was specified for data set
another data set. ’bbbbbbbb’.
Explanation: The ddname is not available for your use Explanation: This data set is not a partitioned data
at this time. set.
User Response: Contact the responsible programmer. User Response: Store this member in a partitioned
data set or store it as a sequential data set.
System Programmer Response: Correct the
allocations.
ISPD018 Multivolume data set - Data set
’aaaaaaaa’ occupies more than one
ISPD011 Syntax error in DDNAME - File name
volume.
(DDNAME) ’aaaaaaaa’ contains invalid
special character. Explanation: You do not have multivolume support.
Explanation: An invalid special character was found User Response: Contact your system programmer.
in the DDNAME.
User Response: Correct the syntax of the ddname.
ISPD019 Catalog error - Already cataloged, ISPD103 Invalid keyword given - ’aaaaaaaa’
VSAM protected, or other - ’aaaaaaaa’. invalid
Explanation: Catalog attempt was unsuccessful. Explanation: A keyword name is invalid for one of
the following reasons:
User Response: Use another name or contact the
v The keyword name is longer than 10 characters.
system programmer.
v The keyword name is not one of the valid keyword
names.
ISPD020 Data set already open - Data set v The MODE keyword is not used with PGM or CMD.
’aaaaaaaa’ is already in use on your
Programmer Response: Correct the keyword and try
behalf.
again.
Explanation: You are already using the data set and
you cannot open it again.
ISPD104 Invalid parameter given - ’aaaaaaaa’
User Response: Complete the other task that uses the invalid
data set, and then this task can use it.
Explanation: A keyword is invalid for one of the
following reasons:
ISPD021 Allocation denied - Data set ’aaaaaaaa’ - v A value is given in parentheses with no name before
request denied by installation exit. it.
v The keyword does not have an expected value.
Explanation: Your installation will not allow you to v The keyword is longer than 10 characters.
use this data set. v The value of the MODE keyword is not FSCR or
User Response: Contact your system programmer. LINE.
Programmer Response: Correct the keyword and try
ISPD022 Allocation failed - DAIR RC = ’aaaaaaaa’ again.
dec, CTRC = ’bbbbbbbb’ hex.
Explanation: Allocation failed, the return codes listed ISPD105 Insufficient storage - Unable to process
above will be required to determine why the allocation command.
failed. Explanation: A GETMAIN command for main storage
User Response: Contact your system programmer. failed while analyzing ISPF command syntax, or while
creating internal file control tables. The command was
System Programmer Response: The DAIR and DARC not processed.
codes are listed in the ISPF tutorial. Enter HELP to
reach the first tutorial panel, then enter INDEX on the Programmer Response: Try running the program in a
command line. Enter D on the command line to get to larger region.
the topics screen. Select D1 for the listing of the DAIR
and DARC codes. ISPD106 Conflicting parameters - CMD conflicts
with another parameter.
ISPD023 Tape not supported - ISPF does not Explanation: A keyword was found that is
support data sets on tape. inconsistent with the CMD keyword. For example,
Explanation: Allocation failed for a data set on tape. PGM and CMD cannot both be used in the same
ISPF does not support data sets on tape. command.
Programmer Response: Check the usage of the CMD
ISPD101 Invalid panel name - ’aaaaaaaa’ - 8 char keyword, and eliminate the conflict.
limit
Explanation: The panel name must be 8 characters or ISPD107 Conflicting parameters - PGM conflicts
fewer. with another parameter
Programmer Response: Use a shorter panel name. Explanation: A keyword was found which is
inconsistent with the PGM keyword. For example,
PGM and PANEL cannot both be used in the same
ISPD102 Invalid PGM name - ’aaaaaaaa’ - 8 char command.
limit
Programmer Response: Check the usage of the PGM
Explanation: The program name must be 8 characters keyword, and eliminate the conflict.
or fewer.
Programmer Response: Retry with a shorter program
name.
ISPD111 CMD did not complete - ’aaaaaaaa’ was ISPD117 The initially invoked CLIST ended with
terminated with an ATTENTION. a return code = aaaaaaaa.
Explanation: The command or CLIST did not Explanation: A CLIST or REXX procedure was
complete because an ATTENTION was signalled. This selected at ISPSTART time that ended with a return
probably happened because the PA1 key was pressed. code that was not 0 or 4. These are the only valid
values.
User Response: No response is required.
Programmer Response: If you wish to return a value
to the calling program or procedure, consider using the
ISPD112 Invalid PGM name - Link to ’aaaaaaaa’
ZISPFRC variable. See ISPF Dialog Developer’s Guide and
failed.
Reference for details.
Explanation: An MVS LINK to the program named
aaaaaaaa has failed. The reason could be one of the
ISPD118 The initially invoked module ended
following:
with a return code = aaaaaaaa.
v The program was not found.
v The program was not authorized. Explanation: A program module was selected at
ISPSTART time that set a return code value other than
Programmer Response: Check the name and
0 or 4. These are the only valid values.
authorization of aaaaaaaa for errors.
Programmer Response: If you wish to set a return
code for the program or procedure that invoked
ISPD113 Invalid panel - ’aaaaaaaa’ is not a valid
ISPSTART, consider using the ZISPFRC variable to
’selection’ panel.
return this value. See ISPF Dialog Developer’s Guide and
Explanation: The panel that was asked to display is Reference for details.
not a valid menu panel. This is probably because it
does not have a ZSEL variable.
User Response: Be sure that the panel name is that of
a menu panel.
ISPD150 Invocation error - System error ISPD157 Severe error - Select service start exit
encountered invoking authorized routine returned invalid code aaaaaaaa.
command ’aaaaaaaa’.
Explanation: The select service start exit routine
Explanation: ISPF cannot invoke an authorized returned an unexpected return code, which is shown in
command, such as LOGON. It is also possible that the the message.
TSO command start exit routine rejected the command.
Programmer Response: Examine the exit routine to
Programmer Response: Avoid usage of authorized see where the unexpected return code was generated.
commands in ISPF.
ISPD158 Invocation error - System error
ISPD151 Language qualifier error - The only encountered invoking command
value valid for the APL language is ’aaaaaaaa’.
START.
Explanation: Routine IKJTBLS abended while starting
Explanation: Some value other than START was this command.
specified for the APL language qualifier. Or START was
Programmer Response: Examine the abend
followed by something else, which is invalid.
information to determine cause of abend.
Programmer Response: Correct the syntax of the APL
language qualifier.
ISPD175 IKJADTAB interface error - RC =
’aaaaaaaa’ from TSO routine IKJADTAB,
ISPD153 PASSLIB spec invalid - NEWAPPL must function = ’bbbbbbbb’.
be specified to specify PASSLIB.
Explanation: During NEWAPPL processing of the
Explanation: The PASSLIB keyword was used but SELECT service, TSO routine IKJADTAB was invoked
NEWAPPL was omitted. to set up or free an ALTLIB table for the new select
level. IKJADTAB set return code aaaaaaaa, which is an
Programmer Response: Correct the syntax and retry
internal error. The service function bbbbbbbb is what
the command.
was passed to IKJADTAB.
Programmer Response: Contact your system
ISPD154 Storage release error - Error occurred
programmer.
when releasing application library
blocks. System Programmer Response: Contact IBM support.
Explanation: A severe error occurred while doing
FREEMAIN of LIBDEF control blocks. ISPD176 Interface error - RC = ’aaaaaaaa’ from
TSO routine IRXSTK, function =
Programmer Response: Contact your system
DROPTERM.
programmer.
Explanation: During NEWAPPL processing for the
System Programmer Response: Contact IBM support.
SELECT service, TSO routine IRXSTK is called to
remove a barrier (DROPTERM) from the REXX data
ISPD155 Deallocation failure - Deallocation stack. IRXSTK set return code aaaaaaaa, which is an
failure - check allocated data sets. internal error.
Explanation: The deallocation of LIBDEF data sets Programmer Response: Contact your system
failed during the termination of ISPEXEC. programmer.
User Response: Contact your system programmer. System Programmer Response: Contact IBM support.
ISPD210 CMD abended - ’aaaaaaaa’ terminated ISPD215 Option conflict - An OPT keyword
abnormally. conflicts with a previously specified
option.
Explanation: The aaaaaaaa command has abnormally
terminated. Explanation: The OPT keyword specifies an option on
the first menu. This keyword cannot be used more than
Programmer Response: Use the provided error
once.
message and log information to determine the cause of
the abend. Consider using the ENVIRON command Programmer Response: Retry the command with only
and the Dialog Test facility to aid in problem a single OPT keyword.
determination. See ISPF Dialog Developer’s Guide and
Reference for further help.
ISPD216 Option too long - Maximum option
length supported is 24 characters.
ISPD211 CMD did not complete - ’aaaaaaaa’ was
Explanation: The OPTION value has a length limit
terminated with an ATTENTION.
and this limit has been exceeded.
Explanation: The command or CLIST did not
Programmer Response: Use a shorter OPTION length.
complete because an ATTENTION was received,
probably because the PA1 key was pressed.
ISPD217 Initial CLIST RC > 4 - The initially
User Response: No response is required.
invoked CLIST ended with a return
code = aaaaaaaa.
ISPD212 Invalid PGM name - Link to ’aaaaaaaa’
Explanation: A CLIST or REXX procedure was
failed, abend code = x’bbbbbbbb’.
selected ending with a return code that was not 0 or 4.
Explanation: An MVS LINK to the program named These are the only valid values.
aaaaaaaa has failed. The reason could be one of the
Programmer Response: If you wish to return a value
following:
to the calling program or procedure, consider using the
v The program was not found.
ZISPFRC variable. See ISPF Dialog Developer’s Guide and
v The program was not authorized.
Reference for details.
Programmer Response: Check the name and
authorization of aaaaaaaa for errors.
ISPD218 Initial program RC > 4 - The initially
invoked module ended with a return
ISPD213 Invalid panel - ’aaaaaaaa’ is not a valid code = aaaaaaaa.
’selection’ panel.
Explanation: A program module was selected with a
Explanation: The panel you asked to display is not a return code value other than 0 or 4. These are the only
valid menu panel. This is probably because it does not valid values.
have a ZSEL variable.
Programmer Response: If you wish to set a return
User Response: Be sure that the panel name is that of code for the program or procedure, consider using the
a menu panel. ZISPFRC variable to return this value. See ISPF Dialog
Developer’s Guide and Reference for details.
Programmer Response: If necessary, add a ZSEL
variable to the panel definition.
ISPD219 Required parm missing - A select
parameter requires one of PGM, CMD,
ISPD214 Invalid NEWAPPL ID - ’aaaaaaaa’ is not
or PANEL.
a valid ’NEWAPPL ID’. Length exceeds
4 characters. Explanation: A required SELECT parameter was
omitted. If the OPT parameter was specified, then
Explanation: The NEWAPPL keyword requires a 1 to
PANEL was omitted. If the LANG parameter was
4 character application ID. The supplied ID was greater
specified, then CMD was omitted. If the PARM
than 4 characters.
parameter was specified, then PGM was omitted.
Programmer Response: Retry the command with a 1
Programmer Response: Add the required parameter
to 4 character NEWAPPL keyword value.
and retry the request.
ISPD244 Panel definition error - 100 panels ISPD250 Invocation error - System error
processed. No return key stop found. encountered invoking authorized
ZPARENT causing loop. command ’aaaaaaaa’.
Explanation: After executing the RETURN command, Explanation: ISPF cannot invoke an authorized
ISPF tries to display the primary option menu in the command, such as LOGON. It is also possible that the
hierarchy or explicit panel chain. If more than 100 TSO command start exit routine rejected the command.
panels are in the chain, ISPF assumes that there is an
Programmer Response: Avoid usage of authorized
error in the specification of ZPARENT that is causing
commands in ISPF.
an infinite loop in the panel chain. Processing stops.
ISPD251 Language qualifier error - The only ISPD258 Invocation error - System error
value valid for the APL language is encountered invoking command
START. ’aaaaaaaa’.
Explanation: Some value other than START was Explanation: Routine IKJTBLS abended while starting
specified for the APL language qualifier. Or START was this command.
followed by something else, which is invalid.
Programmer Response: Examine the abend
Programmer Response: Correct the syntax of the APL information to determine the cause of the abend.
language qualifier.
ISPD275 IKJADTAB interface error - RC =
ISPD253 PASSLIB spec invalid - NEWAPPL must ’aaaaaaaa’ from TSO routine IKJADTAB,
be specified to specify PASSLIB. function = ’bbbbbbbb’.
Explanation: The PASSLIB keyword was used but Explanation: During NEWAPPL processing of the
NEWAPPL was omitted. SELECT service, TSO routine IKJADTAB was invoked
to set up or free an ALTLIB table for the new select
Programmer Response: Correct the syntax and retry
level. IKJADTAB set return code aaaaaaaa which is an
the command.
internal error. The service function bbbbbbbb is what
was passed to IKJADTAB.
ISPD254 Storage release error - Error occurred
User Response: Contact your system programmer.
when releasing application library
blocks. System Programmer Response: Contact IBM support.
Explanation: A severe error occurred while processing
a FREEMAIN of LIBDEF control blocks. ISPD276 Interface error - RC = ’aaaaaaaa’ from
TSO routine IRXSTK, function =
User Response: Contact your system programmer.
’dropterm’
System Programmer Response: Contact IBM support.
Explanation: During NEWAPPL processing for the
SELECT service, TSO routine IRXSTK is called to
ISPD255 Deallocation failure - Deallocation remove a barrier (’DROPTERM’) from the REXX data
failure - check allocated data sets. stack. IRXSTK set return code aaaaaaaa which is an
internal error.
Explanation: Deallocation of LIBDEF data sets failed
during termination of ISPEXEC. User Response: Contact your system programmer.
User Response: Contact your system programmer. System Programmer Response: Contact IBM support.
ISPD286 Invalid PFSHOW parm - Valid ISPD291 Invalid CONTROL parm - ’aaaaaaaa’ is
PFSHOW parameters are ON, OFF, invalid option for CONTROL ERRORS
TAILOR, or blank. service request.
Explanation: An incorrect parameter was specified on Explanation: The CONTROL ERRORS service has
the PFSHOW command. Correct parameters are ON, been called with an option that is not valid. The valid
OFF, TAILOR, or no parameter. options are CANCEL and RETURN. CANCEL is the
default.
User Response: Correct the parameter and retry the
command. Programmer Response: Specify a valid option for
CONTROL ERRORS.
ISPD287 Key display forced off - Current
application does not allow ISPF to ISPD292 Invalid CONTROL parm - ’aaaaaaaa’ is
display function keys. invalid option for CONTROL DISPLAY
service request.
Explanation: The application that is running has set
the ZPFCTL system variable so that you cannot use Explanation: The CONTROL DISPLAY service request
PFSHOW to view the function key area. has been called with an option that is not valid. The
valid options are LOCK, LINE, SM, REFRESH, SAVE,
User Response: Try to use the application to do what
RESTORE, and ALLVALID.
you want. For example, the application may allow you
to select a Help function on the screen rather than by Programmer Response: Change aaaaaaaa to one of the
pressing a function key. options listed above.
ISPD288 Key display forced on - Current ISPD293 Invalid CONTROL parm - The start
application does not allow function key line-number is invalid for CONTROL
display to be removed. DISPLAY service request.
Explanation: The application that is running has set Explanation: The starting line number specified with
the ZPFCTL system variable so that you cannot use the CONTROL DISPLAY service request is invalid,
PFSHOW to remove the function key area. probably because it is a negative number.
User Response: This application is dependent on Programmer Response: Specify a valid start line
function keys. Contact your system programmer for number.
application information.
ISPD294 Missing CONTROL parm - A required
ISPD289 Mis-matched quotes - The string parameter is missing from the
contains an uneven number of quotes CONTROL service request.
Explanation: Unmatched quotes were found in a Explanation: The CONTROL service request requires a
parenthesized keyword value for an ISPF service parameter but none was specified. Valid parameters are
request. DISPLAY, NONDISPL, ERRORS, SPLIT, NOCMD, and
SUBTASK. Most of these parameters require other
Programmer Response: Correct the keyword value so
parameters which are described in ISPF Services Guide
there are no unmatched quotation marks.
Programmer Response: Supply a valid parameter for
the CONTROL request.
ISPD290 Invalid CONTROL parm - ’aaaaaaaa’ is
invalid as request type parameter to the
CONTROL service. ISPD295 Missing CONTROL parm - A required
parameter missing from CONTROL
Explanation: The CONTROL service has been called
DISPLAY service request.
with a parameter that is not valid. The valid request
type parameters for the CONTROL service in MVS are Explanation: The CONTROL DISPLAY service request
DISPLAY, NONDISPL, ERRORS, SPLIT, NOCMD, and requires another parameter. Valid parameters are
SUBTASK. LOCK, LINE, SM, REFRESH, SAVE, RESTORE, and
ALLVALID. One of these must be specified.
Programmer Response: Correct the CONTROL
parameter and retry. Programmer Response: Supply a valid parameter for
CONTROL DISPLAY.
ISPD296 Invalid CONTROL parm - ’aaaaaaaa’ is ISPD302 Invalid upload target – The target for
invalid option for CONTROL ABEND the upload must be a specific member
service request. of a PDS or a sequential data set.
Explanation: In CMS, the CONTROL ABEND service Explanation: When uploading a workstation file to the
request requires another parameter, either ON or OFF. host, the host file specified must be either a sequential
Another value aaaaaaaa was specified, which is data set or a member or a PDS. Something else was
incorrect. used, which is incorrect.
Programmer Response: Change aaaaaaaa to ON or User Response: Correct host data set name and retry.
OFF.
ISPD303 Member name not allowed – You cannot
ISPD297 Invalid CONTROL parm - ’aaaaaaaa’ is specify a member name for a sequential
invalid option for CONTROL data set.
CRETURN service request.
Explanation: When uploading a workstation file to the
Explanation: In CMS, the CONTROL RETURN service host, the host file specified must be either a sequential
request requires another parameter, either CSTART or data set or a member or a PDS. Something else was
CSTOP. An invalid value aaaaaaaa was used instead. used, which is incorrect.
Programmer Response: Change aaaaaaaa to CSTART User Response: Correct host data set name and retry.
or CSTOP.
ISPD801 TBOPEN failure - Return code aaaaaaaa
ISPD298 Invalid CONTROL parm - ’aaaaaaaa’ is from TBOPEN for table ″bbbbbbbb″. (1+)
invalid option for CONTROL
Explanation: The ISPPUP panel update utility could
NONDISPL service request.
not open the input table using the TBOPEN service due
Explanation: The CONTROL NONDISPL service to a severe error. The return code value and the table
request requires another parameter, which can be either name are given in the message. Processing is
ENTER or END. An incorrect value aaaaaaaa was used terminated.
instead.
System Programmer Response: Use the return code
Programmer Response: Change aaaaaaaa to ENTER or value to determine the reason for the severe error.
END.
ISPD802 Table not found - Table ″aaaaaaaa″ not
ISPD299 SPLIT not supported - The ISPF batch found in ISPTLIB, or ISPTLIB not
environment does not support SPLIT. allocated. (1+)
Explanation: The CONTROL SPLIT ENABLE service Explanation: The input table for the ISPPUP panel
request is not allowed while running in the ISPF batch update utility was not found. This could be because the
display environment. table name was misspelled, or the table library was not
allocated. The return code from TBOPEN is 8 or 16.
Programmer Response: Avoid using this request if the
Processing is terminated.
application is to be run in batch.
System Programmer Response: Make sure the desired
table is in the table library and that the correct library
ISPD301 Invalid FKA parm - Valid FKA
is allocated.
parameters are ON, OFF, PREFIX,
NOPREFIX, or blank. PREFIX and
NOPREFIX are only valid when running ISPD803 ISPPLIB error - The panel input library
in GUI mode. ISPPLIB is not open. (aaaaaaaa+)
Explanation: The parameter for the FKA command Explanation: The panel being updated for the ISPPUP
must be ON, OFF, PREFIX, NOPREFIX, or blank. panel update utility could not be found because the
PREFIX and NOPREFIX are only valid when running ISPPLIB panel library is not open. The modified panel
in GUI mode. Something else was used, which is output library (ISPPMOD) was searched and the panel
incorrect. was not there. Processing is terminated.
User Response: Correct the parameter to the FKA System Programmer Response: Make sure that the
command and retry. proper panel input library is allocated before running
ISPPUP.
ISPD804 Panel not found - Panel ″aaaaaaaa″ not ISPD809 GETMAIN error - Return code aaaaaaaa
found in panel input library ″ISPPLIB″. from common subroutine CSM. (1+)
(bbbbbbbb)
Explanation: While the panel update utility (IPSPUP)
Explanation: The ISPPUP panel update utility could was initializing, it attempted to get storage for a panel
not find the input panel aaaaaaaa in the panel input buffer or internal control blocks. The GETMAIN failed
library ISPPLIB. Processing continues with the next and processing has terminated.
panel.
System Programmer Response: Check to make sure
System Programmer Response: Correct the name of adequate main storage is allocated to the job.
the input panel, or make sure it is in a data set
allocated to ISPPLIB.
ISPD810 Read error - I/O error reading panel
″aaaaaaaa″ from ″bbbbbbbb″. (cccccccc)
ISPD805 BLDL error - I/O error during BLDL for
Explanation: An I/O error occurred in the Select
ddname ″aaaaaaaa″. (bbbbbbbb)
Panel Update Utility, ISPPUP, while reading panel
Explanation: The panel update utility, ISPPUP, had a definition aaaaaaaa from the library file defined by
severe error from the BLDL request when trying to find bbbbbbbb. Processing has terminated.
a panel member in the ISPPLIB or ISPPMOD library.
System Programmer Response: Determine the reason
The return code in the message indicates a severe error
for the I/O error, if possible. Contact IBM support for
for BLDL. Processing is terminated.
further help if needed.
System Programmer Response: Analyze the reason
why the BLDL failed. Contact IBM support if further
ISPD811 Panel too large - Definition for panel
help is needed.
″aaaaaaaa″ will exceed bbbbbbbb lines.
(cccccccc)
ISPD806 aaaaaaaa error - The panel output library
Explanation: The Selection Panel Update utility cannot
″aaaaaaaa″ has not been allocated. (1+)
handle a selection panel that has more than bbbbbbbb
Explanation: The ISPPUP panel update utility could lines. Processing continues with the next panel.
not continue because the ISPPMOD panel output
System Programmer Response: Remove unnecessary
library was not allocated. Processing is terminated.
lines from the panel and run the utility again.
System Programmer Response: Make sure the correct
library is allocated to ISPPMOD before running
ISPD812 Body size error - Body of panel
ISPPUP.
″aaaaaaaa″ is empty or larger than
bbbbbbbb lines. (cccccccc)
ISPD807 No asterisk found - The ″&ZSEL =″ in
Explanation: The Selection Panel Update utility,
panel ″aaaaaaaa″ has no asterisk
ISPPUP, was processing panel aaaaaaaa which has either
translation. (bbbbbbbb)
zero lines or more than bbbbbbbb lines in the body
Explanation: While the selection panel update utility, section. Processing continues with the next panel.
ISPPUP, was updating panel aaaaaaaa, no asterisk (*)
System Programmer Response: Correct the body
translation was found in the TRANS statement.
section of the panel so that it can be handled by the
Processing continues with the next panel.
utility, or update the panel by hand.
System Programmer Response: It is desirable to have
an asterisk selection in all selection panel TRANS
ISPD813 Missing )END stmt - End of file found
statements.
before )END statement for panel
″aaaaaaaa″. (bbbbbbbb)
ISPD808 Model section found - Panel ″aaaaaaaa″
Explanation: The Selection Panel Update utility,
is an invalid selection panel (model
ISPPUP, reached the end of the current panel, aaaaaaaa,
section found).(bbbbbbbb)
unexpectedly. The utility expects an )END statement to
Explanation: A )MODEL section should be used only complete the panel definition. Processing continues
in table display panels. The selection panel update with the next panel.
utility (ISPPUP) found a )MODEL section in a selection
System Programmer Response: Correct the
panel. Processing continues with the next panel.
incomplete panel so that it contains an )END statement.
System Programmer Response: Check to make sure
this panel is a selection panel.
ISPD814 No PROC section - ″aaaaaaaa″ is an ISPE000 Invalid return code (aaaaaaaa) received
invalid selection panel (no PROC from ISPF reserve exit.
section found). (bbbbbbbb)
Explanation: The Reserve installation exit has returned
Explanation: The Selection Panel Update utility, a return code other than 0 or 16.
ISPPUP, did not find a )PROC section in panel aaaaaaaa.
User Response: Contact your system programmer.
Selection panels must have a )PROC section. Processing
continues with the next panel. System Programmer Response: See ISPF Planning and
Customizing to determine which exit is the Reserve
System Programmer Response: Correct the panel so
installation exit, then determine the reason the exit is
that it has a )PROC section.
returning a return code other than 0.
ISPD816 Invalid option - Existing option ISPE002 Severe error - Display service exit
″aaaaaaaa″ in panel ″bbbbbbbb″ is too long. routine returned invalid return code
(cccccccc) aaaaaaaa.
Explanation: The Selection Panel Update utility, Explanation: The Display Service installation exit
ISPPUP, has found an option value in an input panel routine has returned a return code other than 0 or 4.
(panel being updated) that is too long. Processing
continues with the next panel. User Response: Contact your system programmer.
System Programmer Response: Make sure the option System Programmer Response: See ISPF Planning and
value is no more than 4 characters. Customizing to determine which exit is the DISPLAY
installation exit, then determine why the exit returned a
return code other than 0 or 4.
ISPD817 Long select string - Select string
specified for panel ″aaaaaaaa″ is too long.
(bbbbbbbb) ISPE003 Authorization failure - Command
’aaaaaaaa’ rejected by exit routine for
Explanation: The Selection Panel Update utility, TSO command start.
ISPPUP, tried to add the selection string text to the
)PROC section of a panel but the text would not fit into Explanation: A TSO command has been rejected by
the logical record (80 characters). The limit on selection the TSO Command installation exit.
string text is 30 characters. Processing continues with User Response: Contact your system programmer for
the next panel. a list of commands that are not allowed by your TSO
System Programmer Response: Shorten the selection Command installation exit.
panel text. System Programmer Response: See ISPF Planning and
Customizing to determine which exit is the TSO
ISPD819 Invalid option - Option ″aaaaaaaa″ for Command installation exit then determine why the exit
″bbbbbbbb″ has blanks, commas, or rejected the command.
periods. (cccccccc)
Explanation: The Selection Panel Update utility, ISPE004 TSO command error - Exit routine for
ISPPUP, found the OPTION field in the input table to command ’aaaaaaaa’ returned invalid
have a faulty value. The field is faulty because it code bbbbbbbb.
contains an imbedded blank, comma, or period Explanation: The TSO Command installation exit has
character. Processing continues with the next panel. returned a return code other than 0, 4, or 16.
System Programmer Response: Correct the option User Response: Contact your system programmer.
field in the input table that drives the ISPPUP.
ISPF117 )SEL error - )SEL ends in wrong )DOT, ISPF122 Service error - RC aaaaaaaa from
aaaaaaaa record-bbbbbbbb. bbbbbbbb, cccccccc record-dddddddd
Explanation: This is an internal error in ISPF. The Explanation: An error occurred in table processing for
internal stack pointers for )SEL and )DOT have become file tailoring, related to )DOT or )ENDDOT. The table
inconsistent and processing cannot continue. service is bbbbbbbb and the return code from the service
is aaaaaaaa. The error was discovered while processing
Programmer Response: Contact your system
record dddddddd of member cccccccc.
programmer.
Programmer Response: Use the return code value to
System Programmer Response: Contact IBM support.
help determine the nature of the problem.
User Response: The region size may not be large Explanation: An input I/O error occurred during file
enough. Check your region size, then contact IBM tailoring. The error may have occurred on the main
support. skeleton file, on a )DOT file, an )IM file, or while
reading a temporary file. aaaaaaaa. is the member name
that was being processed.
ISPF131 Build TFD error - Module aaaaaaaa
received RC-bbbbbbbb from ISPCBTFD. User Response: Check the input files for obvious
incompatibilities with the ISPF recommended values,
Explanation: An unexpected internal error occurred in such as wrong record length. Also make sure that
ISPF while trying to build an internal control block for variable and fixed record types have not been mixed in
file tailoring. The return code and the module name the concatenation of input data sets.
that received the return code are given in the message.
Programmer Response: Contact your system ISPF136 I/O error - Unrecoverable I/O error on
programmer. output data set.
System Programmer Response: Contact IBM support. Explanation: An I/O error occurred writing the
output data set for file tailoring.
ISPF132 Data set name error - Module aaaaaaaa User Response: Check the output data set for possible
received RC-bbbbbbbb from ISPCDSN. incompatibilities, such as wrong data set organization.
If further help is needed, call IBM support.
Explanation: An internal error occurred in ISPF
during file tailoring. Module aaaaaaaa called ISPCDSN
to get a data set name but ISPCDSN set return code
bbbbbbbb, which was unexpected. If the return code is 4,
ISPCDSN found no DD statement or the DDNAME in
the DCB was blank.
User Response: Contact your system programmer.
ISPF139 Output error - Output file is not a PDS. Explanation: A system abend occurred during file
tailoring. The system abend code is bbbbbbbb and the
Explanation: One of the following occurred: STAE exit routine which generated this message is in
v An FTCLOSE was attempted with a specified module aaaaaaaa. Data sets have been closed and
member name and the output file was not a dequeued.
partitioned data set,
v An FTCLOSE was attempted on a data set that was Programmer Response: Use the abend code to help
not a library, or discover the reason for the abend. Contact IBM support
v An FTERASE was attempted on a data set that was if further help is needed.
not partitioned.
Programmer Response: Correct the error. ISPF145 Output data conflict - Generated data in
last output column, last input column
cannot be moved.
ISPF140 Data set not allocated - aaaaaaaa data set
is not allocated. Explanation: Column 72 in the skeleton data file
already has data in it, and there is generated data that
Explanation: The input data set or an imbed data set would replace it. This existing data might be a
for file tailoring was not allocated. The ddname is sequence number which cannot be moved.
aaaaaaaa.
Programmer Response: Avoid generating data in
Programmer Response: Allocate the input data sets column 72 of the skeleton if the file contains sequence
and retry file tailoring. numbers.
ISPF141 ENQUEUE failed - Data set aaaaaaaa in ISPF151 Invalid tab position - Tab (aaaaaaaa) out
use, ENQUEUE failed. of range (1-255), bbbbbbbb record-cccccccc.
Explanation: During file tailoring the input, output, or Explanation: One of the tab values in the file tailoring
a temporary data set could not be enqueued. aaaaaaaa is )TB or )TBA statement is not in the correct range of 1
either the ddname or data set name that could not be through 255. The incorrect value is aaaaaaaa, and the
enqueued. The data set is in use by another task, and error was discovered in record cccccccc of member
file tailoring cannot continue. bbbbbbbb.
Programmer Response: Using aaaaaaaa as a guide, Programmer Response: Correct the )TB or )TBA
resolve the conflicting use of the data set. statement to use tab values in the range 1 to 255.
ISPF142 Variable truncation - Variable truncation ISPF152 Invalid tab position - Tab (aaaaaaaa)
has occurred. must exceed previous tab, bbbbbbbb
rec-cccccccc.
Explanation: During file tailoring, a file tailoring
variable was replaced with a value that was truncated. Explanation: The numeric tab positions in the )TB or
)TBA statement for file tailoring are not in increasing
Programmer Response: Correct the )TB or )TBA v TCP/IP must be installed and running.
statement so no more than 16 tab stops are specified. v FTP must be installed and running.
v The path specified must have write access (Review
ISPF154 Invalid LRECL - The limit of TRUSERS file).
input/output data set logical record v You must have read access to the MVS data set
length is 255. where ISPF Client/Server Component resides.
Explanation: File tailoring data sets cannot have a v The directory where ISPF Client/Server Component
logical record length greater than 255. This applies to is being copied must exist or you must have selected
both input and output data sets. the ’Create directory’ choice field.
v If you have asked to create the workstation directory,
Programmer Response: Check logical record length of you must be able to change directory to the parent of
input and output data sets for file tailoring, including the specified directory.
temporary data sets. Make sure none has a logical
record length greater than 255.
ISPF161 FTP command not found. - The ISPF
C/S INSTALL program received a severe
ISPF155 STOW password error - File tailoring error running the FTP command,
does not support password protected probably due to not being able to find
members. the FTP command.
Explanation: FTCLOSE or FTERASE is being Explanation: This is an informational message. This
attempted on a file tailoring output data set member message is issued by the FTP ISPF C/S INSTALL
and the member is password protected. File tailoring command.
output to password protected members is not
supported.
ISPF162 EXE not found - The workstation
Programmer Response: Select an output data set for executable part was not found in the
file tailoring that is not password protected. data set specified. Either the language
specified is not installed or the data set
ISPF156 Output overflow - Line to be written specified is incorrect.
greater than data set LRECL aaaaaaaa. Explanation: The EXE was not found in the data set
Explanation: During a file tailoring FTCLOSE, the last specified on the panel.
non-blank character of the tailored output data would User Response: Ask your system programmer for the
not fit within the logical record length of the output correct data set name in which the workstation
data set. The data set logical record length is aaaaaaaa. executables reside. Enter the correct data set name.
Programmer Response: Increase the logical record
length of the output data set or ensure that data will fit ISPF163 DLL not found - The workstation
within the output data set logical record. dynamic link library (DLL) part was not
found in the data set specified.
Explanation: The dynamic link library was not found
in the data set specified on the panel.
ISPG028 Invalid selection - Valid codes are B, S, ISPG040 Invalid DSORG - Data set organization
U, T or I, or a number if selection list must be partitioned or sequential.
present.
Explanation: The data set organization was entered
Explanation: An invalid code or selection number incorrectly.
entered on a tutorial panel.
User Response: Correct the data set organization.
User Response: You can view the tutorial sequentially
by leaving the command/option field blank and
ISPG041 Interface error - Rc = ’aaaaaaaa’ from
repeatedly pressing the Enter key.
TSO routine IKJADTAB, function =
Alternatively, you can select topics from lists displayed ENDTABLE
on many of the tutorial pages. For example, enter
Explanation: An error occurred on return from link to
OPTION ===> 3 IKJADTAB.
to select topic number three. User Response: Contact your system programmer.
You can also enter one of the following commands on System Programmer Response: Determine what the
any tutorial page: user was doing when the error occurred, then contact
BACK or B IBM support.
to back up to the previously viewed page.
SKIP or S
ISPG044 Concatenation failed - Unable to
to skip the current topic and go on to the next
concatenate the specified libraries.
topic.
UP or U Explanation: Concatenation failed, ISPCDAIR did not
to display a higher level list of topics. return with RC=0.
TOC or T
to display the table of contents. User Response: Contact your system programmer.
INDEX or I System Programmer Response: If the user’s action
to display the tutorial index. was correct, contact IBM support.
ISPG029 No index panel defined - The ZHINDEX ISPG045 STAE macro error - Unable to obtain
dialog variable is not set to a panel storage for STAE macro, subpool 0 full.
name.
Explanation: Storage has been exhausted, there was a
Explanation: The dialog variable ZHINDEX does not previous error that could have used all of the available
contain the name of the first INDEX panel. storage.
User Response: The variable ZHINDEX must contain User Response: Verify that your region size is large
the name of the first INDEX panel. The variable can be enough to run the task that just failed. If you still have
set in the beginning of the application to ensure that a problem, contact the system programmer.
the user can always display the INDEX panel
regardless of how tutorial was entered. ZHINDEX can System Programmer Response: Verify that the task is
also be set on the primary option menu. not looping and that the storage is sufficient to execute
the failing function.
User Response: Ensure that the specified data set is User Response: Contact your system programmer.
the correct data set. Note message number and text, Programmer Response: Verify that the program has
then contact your system programmer. been properly authorized.
System Programmer Response: Restore the specified
data set from backup, if possible. Contact IBM support ISPG047 IRXTERMA interface error - ISPF
if further assistance is required. received return code ’aaaaaaaa’ from TSO
routine IRXTERMA
Explanation: An error occurred while initializing the
REXX environment.
ISPG061 Invalid command name - The command ISPG066 Command abend - Abend aaaaaaaa hex
entered or contained in a CLIST is null occurred processing command ’bbbbbbbb’.
(all blanks).
Explanation: The command cannot be processed.
Explanation: This message is self-explanatory.
User Response: Contact the responsible programmer.
User Response: Contact the responsible programmer.
Programmer Response: If you are unable to determine
Programmer Response: Correct the CLIST by entering why the abend occurred, contact IBM support.
a valid command name.
ISPG067 PUTGET error - PUTGET return code
ISPG062 Invalid command - Unable to process aaaaaaaa hex. Notify your system
command. IKJSCAN return code = programmer.
aaaaaaaa.
Explanation: A system failure occurred.
Explanation: The command entered is unauthorized.
User Response: Contact your system programmer.
User Response: Enter the correct command name. If
System Programmer Response: An unexpected return
the command is correct, contact the responsible
code was received while executing a command. Refer
programmer.
to the PUTGET documentation for additional
Programmer Response: Verify that the command information about this return code.
name is an authorized command.
ISPG068 Member name too long - Member name
ISPG063 Command rejected - Command rejected must be less than or equal to 8
- ’aaaaaaaa’ command not supported characters.
under ISPF.
Explanation: The member name of the data set
Explanation: This command name cannot be used exceeds the 8 character limit.
while using ISPF.
User Response: Correct the member name.
User Response: Enter the name correctly, or contact
the responsible programmer.
ISPG069 No members in data set - The PDS
Programmer Response: Correct the command name to specified contains no members.
avoid conflict with ISPF.
Explanation: This is an informational message.
ISPG082 Data set not partitioned - Only ISPG086 Delete data set failed - ’aaaaaaaa’ is open,
partitioned data sets may be cannot be deleted.
concatenated.
Explanation: The data set is in use and cannot be
Explanation: A non-partitioned data set has been deleted.
entered in the concatenation sequence.
User Response: End the task that is using the data set.
User Response: Enter the correct data set names, or
delete any data sets that are not partitioned.
ISPG087 Data set in use - The data set is
currently in use by you.
ISPG083 Deconcatenation failed - Unable to
Explanation: The data set is being used in another
deconcatenate the specified libraries.
task.
Explanation: One of the libraries cannot be
User Response: End the other task before starting this
deconcatenated; it is probably still in use.
task.
User Response: End the job that is using one of the
libraries.
ISPG088 Dsn ALLOC check failed - Unable to
check if data set is already allocated.
ISPG084 Reallocation failed - DAIR RC =
Explanation: The allocation check failed.
aaaaaaaa dec, DARC = bbbbbbbb hex, dsn
= ’cccccccc’ User Response: Contact your system programmer.
Explanation: The data set could not be reallocated as System Programmer Response: Contact IBM support.
old.
User Response: Use the following return codes to ISPG090 Invalid data set name - Data set name
determine why the operation failed. Contact the system contains unbalanced apostrophes.
programmer, if necessary.
Explanation: The data set name entered contains
Following are the DAIR return codes: unbalanced apostrophes.
CODE MEANING
0 DAIR completed successfully. Secondary error User Response: Reenter the data set name with the
code in DARC field. correct apostrophes.
4 Invalid parameter list passed to DAIR.
8 Catalog Management error. Error code in ISPG091 Invalid data set name - Data set name
CTRC field. must be 1-44 characters in length
12 Dynamic Allocation error. Error code in DARC counting prefix (if any).
field.
16 No TIOT entries were available for use. Explanation: The data set name you entered had an
20 The DDNAME requested is unavailable. invalid length. It must be no more than 44 characters
24 The DSNAME requested is a member of a including the TSO prefix, if used.
concatenated group. User Response: Check the data set name, and reenter
28 DDNAME or DSNAME not allocated, or ATTR it correctly.
list name not found.
32 DISP=NEW specified for previously
permanently allocated data set. ISPG092 Invalid member name - Member name
36 Catalog information routine error. must be 1-8 characters and enclosed in
40 More index blocks exist than the program parentheses.
provided room for. Explanation: The member name that was entered was
44 DISP=OLD, MOD, or SHR for data set invalid. The member name must be 1 to 8 characters,
previously allocated for delete. enclosed in parentheses.
48 Reserved.
52 Request denied by Installation Exit. User Response: Reenter the member name using the
correct syntax.
ISPG105 Invalid block size - Block size of data ISPG110 Invalid record format - Variable length
set must not be zero. records invalid for this function.
Explanation: The block size of the data set specified Explanation: The data set specified for this function
must not be equal to zero. contains an invalid record format. The function does
not support variable length records.
User Response: Contact your system programmer.
User Response: Contact your system programmer.
System Programmer Response: Specify a data set
with a valid block size, or reallocate the data set so that System Programmer Response: Either specify a valid
it does not have a block size of zero. data set for the function or reallocate the data set with
a valid record format.
ISPG106 Invalid record length - Record length
exceeds maximum (’aaaaaaaa’) allowed ISPG111 Invalid block size - Data set block size
for this function. must be > 8 for RECFM=V.
Explanation: The data set specified contains an invalid Explanation: The data set specified for the function
record length for this function. contains an invalid block size. The data set block size
must be greater than 8 for a data set with a RECFM=V.
User Response: Contact your system programmer.
User Response: Contact your system programmer.
System Programmer Response: Specify a data set
with a valid record length for this function, or System Programmer Response: Update the data set
reallocate the data set. allocation to a valid block size.
ISPG107 Invalid record format - Fixed length ISPG112 Invalid record length - Data set LRECL
records not supported for this function. must be > 4 for RECFM=V.
Explanation: The data set specified contains an invalid Explanation: The data set specified for the function
record format for this function. The function does not contains an invalid record length. The data set record
support fixed length records. length must be greater than 4 for a data set with a
RECFM=V.
User Response: Contact your system programmer.
User Response: Contact your system programmer.
System Programmer Response: Specify a data set
with a valid record format, or reallocate the data set System Programmer Response: Update the data set
referenced. allocation to a valid record length.
ISPG108 Invalid record length - LRECL must be 0 ISPG113 Invalid record length - LRECL and
or equal to block size for unblocked block size are inconsistent for
RECFM=F. RECFM=V data set.
Explanation: The record length for an unblocked Explanation: The record length and block size
RECFM=F data set must be either zero or equal to the specified are inconsistent for data sets with RECFM=V.
block size.
User Response: Contact your system programmer.
User Response: Contact your system programmer.
System Programmer Response: Update the data set
System Programmer Response: Reallocate the data set allocation so that it has a valid block size and LRECL.
so that it has a valid record length for the block size
specified.
ISPG114 Invalid record format - RECFM=U is not
allowed for this function.
ISPG109 Invalid block size - Data set block size
Explanation: Data sets that have RECFM=U are not
is not a multiple of LRECL for
allowed for the specified function.
RECFM=FB.
User Response: Contact your system programmer.
Explanation: The block size of a fixed block data set
must be a multiple of the record length. System Programmer Response: Update the data set
allocation so that it has a valid record format.
User Response: Contact your system programmer.
System Programmer Response: Reallocate the data set
so that is has a valid block size for the record format
specified.
ISPG115 Invalid record format - Data set has ISPG121 I/O error - An I/O error was encountered
record format not supported by ISPF. reading the first record requested.
Must be F, V, or U.
Explanation: The data set cannot be read.
Explanation: The data set specified has a record
User Response: Contact your system programmer.
format that is not supported by ISPF and its services.
System Programmer Response: If this error is not
User Response: Contact your system programmer.
caused by a defective DASD, contact IBM support.
System Programmer Response: Specify a valid record
format for the data set. Valid formats are F, V, and U.
ISPG122 Insufficient storage - Not enough
storage is available for browse to
ISPG116 Open failed - Unable to open data set. proceed.
DCB open flag is not set.
Explanation: Storage has been exhausted.
Explanation: The data set could not be opened.
User Response: Contact your system programmer.
User Response: Contact your system programmer.
System Programmer Response: Verify that the user
System Programmer Response: Contact IBM support. has sufficient storage to meet the minimum ISPF
requirements. Contact IBM support if the storage is
sufficient.
| ISPG117 Open failed - Open for data set
| ’aaaaaaaa’ abended with abend code
| ’bbbbbbbb’. ISPG123 Invalid type of data set - Data set has
non-zero key. This data set is not
| Explanation: The data set could not be opened.
supported by ISPF.
| User Response: Contact your system programmer.
Explanation: This message is self-explanatory.
| System Programmer Response: Contact IBM support.
ISPG130 Reserve failed - Abend occurred during
ISPG118 Obtain failed - Unable to open data set. reserve processing. Unable to open data
Obtain returned non-zero return code. set.
Explanation: The DSCB for this data set could not be Explanation: ISPF was unable to reserve and open the
found, and the data set could not be opened. data set for your use.
User Response: Contact your system programmer. User Response: If the error continues, contact the
system programmer.
System Programmer Response: Contact IBM support.
System Programmer Response: Contact IBM support.
ISPI023 ISPI023 ENVIRON TERMTRAC ISPL010 Invalid variable name - LIST service
definition OFF, buffer could not be variable name, ’aaaaaaaa’, is syntactically
obtained. incorrect.
Explanation: Storage was not available for creating the Explanation: Specified variable name aaaaaaaa is
buffer and thus ENVIRON TERMTRAC is not syntactically incorrect.
available.
User Response: Enter a syntactically correct variable
User Response: Contact your system programmer. name. Dialog variables are referred to symbolically by a
System Programmer Response: Determine why name composed of 1 to 8 characters (6, for FORTRAN).
storage is not available. Alphanumeric characters A-Z, 0-9, #, $, or @ can be
used in the name, but the first character cannot be
numeric. APL variable names cannot contain #, $, or @.
ISPI024 ISPI024 TSO module IRXECUSP could
not be loaded.
ISPL011 Variable not found - LIST service dialog
Explanation: REXX could not be initialized. variable, ’aaaaaaaa’, does not exist.
User Response: Contact your system programmer. Explanation: The specified LIST service dialog
System Programmer Response: Determine if variable aaaaaaaa was not found.
IRXECUSP exists and why the load fails. Contact IBM User Response: Check the specified dialog variable
support for further assistance. name for incorrect spelling, and verify that the dialog
variable name exists.
ISPI025 ISPI025 TSO routine IRXINIT severe
error — REXX environment could not be ISPL012 Invalid line length - Minimum LIST
initialized. service line length is one when CC is
Explanation: A severe error occurred while initializing specified.
the REXX environment. Explanation: The specified LINELEN value for the
User Response: Contact your system programmer. LIST service is incorrect.
ISPL0999 Licensed Materials — Property of IBM User Response: Reenter the command using LOCATE,
5647–A01 (C) Copyright IBM Corp. 1980, LOC, or L and the library name.
1998. All rights reserved. US
Government Users Restricted Rights —
ISPL105 Library name invalid - ″aaaaaaaa″ is not a
Use, duplication or disclosure restricted
valid LIBDEF library name. The library
by GSA ADP Schedule Contract with
name must be 1 to 8 characters long and
IBM Corp.
cannot be ISPPROF. The value is
Explanation: This is an informational message. ignored.
Explanation: The ISPLIBD command of the LIBDEF
Display Utility requires a valid LIBDEF library name of
1 to 8 characters in length, and it cannot be ISPPROF.
User Response: Reenter the ISPLIBD command with a
valid LIBDEF library name.
ISPL106 ISPLIBD recursion - The ISPLIBD ISPN105 Multiple ddnames - Only one ddname
command may not be issued recursively may be specified when LIBRARY is
within the same logical screen. specified.
Explanation: You entered the ISPLIBD command more Explanation: The LIBRARY keyword on a LIBDEF
than once within the same logical screen. The ISPLIBD service request associates an allocated ddname with an
command may not be issued more than once within the ISPF lib-type. This is a one-to-one correspondence, thus
same logical screen. only one ddname can be specified using the LIBRARY
keyword on a LIBDEF service request.
User Response: Issue the ISPLIBD command only
once per logical screen. User Response: Remove all but one of the specified
ddnames from the LIBDEF statement.
ISPN101 Storage release error - Error occurred
when releasing application library ISPN106 Ddname not allocated - Ddname
blocks. ’aaaaaaaa’ specified on LIBDEF service
not allocated.
Explanation: An error occurred trying to FREEMAIN
the skeleton library block with the ddname, ISPSLIB. Explanation: Ddname aaaaaaaa is not allocated.
User Response: Contact your system programmer. User Response: Ensure correct spelling of the
ddname. Allocate the specified ddname prior to
System Programmer Response: Diagnose the
entering ISPF.
FREEMAIN error that occurred when releasing storage
for the skeleton library block, ISPSLIB. Contact IBM
support. ISPN107 Member name specified - Data set
member specification is invalid.
ISPN102 Storage obtain error - Error occurred Explanation: The LIBDEF service provides a data set
when obtaining storage for application list parameter. It does not support specifying member
library blocks. names of data sets. You can specify a single data set or
a list of data sets.
Explanation: An error occurred when obtaining
storage for application library blocks. User Response: Remove the member name
specification from the data set name specified on the
User Response: Contact your system programmer.
LIBDEF service statement.
System Programmer Response: Diagnose the
GETMAIN error which occurred when obtaining
ISPN108 Invalid dsname framing - Dsname
storage. Contact IBM support.
specification contains inconsistent
framing characters.
ISPN103 Invalid LIBDEF type - ISPPROF is not a
Explanation: The data set list parameter on the
valid LIBDEF type.
LIBDEF service has been coded incorrectly. The data set
Explanation: An application-level definition for name should be specified with a starting and ending
ISPPROF, the ISPF profile library, is not permitted single quote. For example,
because ISPPROF contains user-related data. DATASET(’PROJECT.LEVEL.USER1’). A list of data set
names must be separated by blanks or commas. For
User Response: ISPPROF is an invalid LIBDEF type. example,
Enter a valid LIBDEF type such as the ISPF ddname DATASET(’PROJECT.LEVEL.USER1’,’PROJECT.LEVEL.USER2’)
libraries: ISPMLIB, ISPPLIB, ISPSLIB, ISPTLIB,
ISPTABL, ISPFILE, ISPLLIB, or a valid generic library User Response: Correct the quotation marks for the
name. specified data set name.
ISPN104 Invalid dsname list - Data set name(s) ISPN109 Invalid dsname length - Data set name
incorrectly specified. specification cannot exceed 44
characters.
Explanation: The data set name or names are
incorrectly specified. Explanation: The data set name specified is longer
than 44 characters. Data set names must conform to
User Response: Correct spelling and statement format TSO data set naming conventions.
errors.
User Response: Verify the spelling of the specified
data set name. If the spelling is correct, contact your
system programmer.
Explanation: A severe error was returned from the User Response: Enter a character that is different than
user’s LIBDEF service exit. the command delimiter character.
ISPO005 Inconsistent parameters - Part may not ISPO010 Keylist does not exist - The keylist
be specified with 3278T. selected does not exist; therefore, it
cannot be changed.
Explanation: The screen format of PART (format using
hardware partitions) cannot be used for terminal type Explanation: The selected keylist does not exist for
3278T. The screen format of PART is valid only for the this application ID
3290 terminal type. Formats valid for 3278T terminal
User Response: Create a new keylist for this
types are STD and MAX.
application ID, or select the application ID that contains
User Response: Enter a screen format other than Part the required keylist.
for terminal type 3278T.
ISPO011 Keylist already exists - The keylist name
ISPO006 Display format invalid - Display format entered already exists; therefore, it
must be NO, SHORT, or LONG. cannot be created.
Explanation: For a keylist, the display format options Explanation: When creating a keylist, a keylist was
are: 1.)LONG indicates that the key label should be entered that already exists. To create a keylist, enter the
displayed in the function key area when the FKA name of a keylist that is not in the displayed list.
command is toggled to the first cycle after OFF.
User Response: Enter a valid keylist name that does
2.)SHORT indicates that the key label should be
not already exist.
displayed in the function key area when the FKA
command is toggled to the first or second cycle after
OFF. 3.) NO indicates that the key label should never ISPO012 Keylist not saved - The keylist changes
be displayed in the function key area. were not saved or the keylist was not
created.
User Response: Enter one of the correct Display
Format values: LONG, SHORT, or NO. Explanation: Either the changes to the keylist were
not saved, or the keylist was not created.
ISPO007 F key value required - A function key User Response: Either select the Save action to save
must be assigned a value in order to the keylist changes, or create a new keylist.
have a display format.
Explanation: When working with keylists, if a display ISPO013 Keylist not selected - Enter a keylist
format or a label is specified a definition must also be name or select one from the list and
specified. Any definition is valid. select an action.
User Response: Assign a value to the function key. Explanation: To create, change, delete, or browse a
keylist from the Keylist Utility, enter the keylist name
or select a keylist name from the displayed list. Next,
ISPO008 F key value required - A function key
select create, change, delete, or browse from the
must be assigned a value in order to
Functions pull-down.
have a label.
Explanation: When defining or changing keylists, if a
ISPO014 Keylist does not exist - The keylist
label or a display format is specified for the function
selected does not exist; therefore, it
key, the function key must have a definition. Any
cannot be browsed.
definition is valid.
Explanation: The keylist does not exist for this
User Response: Assign a value (definition) to the
application ID.
function key.
User Response: Either create the required keylist, or
select the application ID under which the keylist exists.
ISPO009 Invalid selection - Enter a keylist name
or select an existing keylist.
ISPO015 Keylist in use - The selected keylist is
Explanation: You must enter a new keylist name or an
currently being updated by you.
existing keylist name and then select the action.
Explanation: You have selected a keylist that you are
User Response: Enter or select a keylist, then select an
currently updating.
action.
User Response: Finish updating the keylist and save it
before performing another action on the specified
keylist.
ISPO016 Delete Warning - This keylist belongs to ISPO022 Input command error - Command
a currently running application. If this entered is not recognized.
keylist is deleted, a dialog error can
Explanation: When updating a command table from
occur if a current application panel
the Command Table Utility, you entered a command
references this keylist.
that was not recognized.
Explanation: A keylist for a currently running
User Response: Enter a valid command. Enter HELP
application cannot be deleted.
for a list of valid commands, or refer to ISPF User’s
User Response: To delete the keylist, press Enter on Guide
the confirmation panel. If you do not want to delete the
keylist, press Cancel.
ISPO023 Keylist not altered - The keylist was not
altered, therefore it is not saved.
ISPO017 Keylist tables in use - The internal
Explanation: This is an informational message. The
tables used by keylist are presently in
keylist was not altered.
use.
Explanation: The KEYLIST command may not be
ISPO024 Keylist not deleted - The keylist was not
issued from the Keylist Utility. However, you can split
found so it cannot be deleted.
the screen and issue the KEYLIST command on the
other screen. Explanation: The keylist was not found under this
application ID.
User Response: The KEYLIST command may not be
issued while actions are being performed on keylist User Response: Select the appropriate application ID
from a previous KEYLIST command. Splitting the from which to delete the keylist.
screen allows the user to access the KEYLIST command
on the other screen.
ISPO025 Keylist not deleted - The keylist
selected is not a private copy of the
ISPO018 Invalid Action - The action selected is keylist.
not defined for the keylist utility.
Explanation: The keylist selected is a shared keylist,
Explanation: An invalid action was selected. Select not a private copy, and cannot be deleted using
one of the valid actions displayed on the informational KEYLIST.
line of the keylist panel.
User Response: Only private copies of the keylist can
User Response: Enter a valid selection from the action be deleted using KEYLIST.
bar or enter N, E, V, or D as the selection character to
perform a New, Edit, View, or Delete action.
ISPO026 Profile not created - The profile table
could not be created and is required for
ISPO019 Keylist saved - The keylist changes were keylist. **** aaaaaaaa ****
saved or the keylist was created.
Explanation: The Keylist Utility could not create a
Explanation: This is an informational message. profile table, ISPPROF. A profile table is necessary
when working with keylists.
ISPO020 Invalid keylist name - The specified User Response: Note message ID and text. Contact
keylist name is invalid. your system programmer.
Explanation: The keylist name that was specified is System Programmer Response: Determine the reason
invalid. the profile was not created. Contact IBM support.
User Response: Enter a valid keylist name.
ISPO027 Keylist not saved - Internal error code
aaaaaaaa resulted in the keylist not being
ISPO021 Updates not allowed - No modifications
saved. **** bbbbbbbb ****
will be accepted while editing or
browsing a keylist. Explanation: ISPF’s attempt to save the keylist
resulted in an error and the keylist was not saved.
Explanation: No modifications to the profile will be
accepted while editing or browsing a keylist. User Response: Note the error message and text.
Contact your system programmer.
User Response: Finish editing or browsing the keylist
before updating the profile. System Programmer Response: Contact IBM support.
ISPO905 Starting a GUI session when running in ISPO910 The address for the workstation display
split screen mode or 3290 partition mode must be the same as the address already
is not supported. established for the workstation
connection (aaaaaaaa).
Explanation: You cannot start a GUI session if you are
in split screen mode or 3290 partition mode on your Explanation: You cannot start a GUI session at an
host session. address other than the one in which the workstation
connection has been established.
User Response: If you are in split screen mode,
terminate the other screen and select the Start GUI User Response: Do not change the workstation
session field. If you are in 3290 partition mode, go back address on the panel.
to the main Settings panel, select a screen format other
than PART, and exit ISPF. Then, to start a GUI session,
ISPO911 Connecting to a workstation when
invoke ISPF with the GUI parameter, or initiate it from
running 3290 partition mode is not
the ISPF Settings GUI option.
supported.
Explanation: You cannot start a GUI session if you are
ISPO906 Cannot connect to the workstation.
in 3290 partition mode on your host session.
Ensure that the communications from
MVS to the workstation are functioning User Response: If you are in 3290 partition mode, go
and that the correct level of the ISPF back to the main Settings panel, select a screen format
Client/Server component is running on other than PART, and exit ISPF. Then, to start a GUI
the workstation. Also, make sure that session, invoke ISPF with the GUI parameter, or initiate
you entered the correct machine address. it from the ISPF Settings GUI option.
Explanation: ISPF cannot make a connection to your
workstation. ISPO913 Valid values: FBA or VBA
User Response: Verify that the communications from Explanation: An invalid value has been entered.
MVS to your workstation are functioning and that the
correct level of the ISPF Client/Server component is User Response: Enter a correct value as shown above.
running on your workstation. Also, verify that you
specified your correct machine address. ISPO914 Valid values: 1 to 999 for FBA and 5 to
999 for VBA
ISPO907 Recursion error - GUI mode cannot be Explanation: An invalid value has been entered.
invoked recursively.
User Response: Enter a correct value as shown above.
Explanation: You are already in GUI mode. Invoking
GUI mode recursively is not supported.
ISPO915 Valid values: 80 to 160
ISPO908 Already connected - This session is Explanation: An invalid value has been entered.
already connected to the workstation User Response: Enter a correct value as shown above.
(aaaaaaaa).
Explanation: You are already in connected to the ISPO916 Changing the ″Always show split line″
workstation at the address specified in the message. setting has no effect in partition mode.
User Response: If the user would like to be connected Explanation: The user changed a setting that has no
to a different workstation, then the user must exit ISPF effect in partition mode.
before connecting to a new workstation address.
ISPO918 Changing the CUA colors will have no ISPO921 Unable to communicate with
effect in GUI mode unless you have workstation at the specified network
selected to use host colors on all fields address. Probable causes: (1) the
in the Global Color utility available specified network address does not exist
from the COLOR command or the Color or cannot be accessed; (2) if specified,
action bar choice on the ISPF Settings the SNA network address does not
panel. support APPC communication. Network
data:’aaaaaaaa’.
Explanation: ISPF allows a user to choose whether to
map host colors to the workstation or not. If the user Explanation: ISPF cannot make a connection to your
has chosen to not map host color for CUA fields (the workstation.
default), the user will be warned with this message that
User Response: Verify that the specified network
changes made in the CUA Attribute Utility will not be
address represents the workstation on which the ISPF
seen. The setting for using host colors is in the Global
Client/Server component is active. If you are using
Color utility available from the COLOR command or
TCP/IP verify that a dotted decimal IP address (for
the Color action bar choice on the ISPF Settings panel.
example, 9.67.224.96) was specified. If you are using
APPC verify that a fully qualified SNA network name
ISPO919 Valid number of keys are: 12 or 24 (for example, USIBMNR.NRI41H00) was specified.
Also, for APPC remember that the specified network
Explanation: An invalid value has been entered.
address must represent a SNA independent logical unit
User Response: Enter a correct value as shown above. type 6.2. SNA logical unit type 2 used for 3270 terminal
or emulator connectivity will not support APPC
communication.
ISPO920 Unable to communicate with ISPF
workstation agent at specified network Problem Determination: NETWORK DATA shows the
address. Probable causes: (1) the TCP/IP socket or SNA APPC function invoked, and
workstation agent is not active at the numeric code returned, that indicated the failing
specified network address; (2) the APPC condition. A complete explanation of MVS TCP/IP
transaction program names or TCP/IP socket return codes can be found in “Chapter 7.
port numbers specified are not identical TCP/IP Error Codes” on page 579. A complete
on the host and on the workstation. explanation of MVS APPC return codes can be found in
Network data:’aaaaaaaa’. Writing Transaction Programs for APPC/MVS. Any
additional message received with the prefix ″LSCX″ is
Explanation: ISPF can communicate with the TCP/IP issued by the SAS/C runtime support shipped with
or APPC subsystem at the workstation but is unable to ISPF. The message may provide additional helpful
communicate with the ISPF Client/Server component information for the user or for support personnel.
at the workstation.
User Response: Verify that you specified the network ISPO922 Unable to utilize local communications
address of a machine on which the ISPF Client/Server subsystem. Probable causes: (1) the
component is active. If you are using TCP/IP and a communications interface modules
port number was specified, verify that the specifed port could not be loaded; (2) the
number matches the port number specified or defaulted communications subsystem did not
at the workstation. If you are using APPC and a provide an acceptable response to the
transaction program name was specified, verify that the initialization request. Network
specified transaction program name matches the data:’aaaaaaaa’.
transaction program name specified or defaulted at the
workstation. Explanation: ISPF cannot make a connection to your
workstation.
Problem Determination: NETWORK DATA shows the
TCP/IP socket or SNA APPC function invoked, and User Response: Notify your MVS system support
numeric code returned, that indicated the failing personnel regarding the failure.
condition. A complete explanation of MVS TCP/IP
System Programmer Response: Verify that the
socket return codes can be found in “Chapter 7.
TCP/IP or APPC/MVS communications subsystem has
TCP/IP Error Codes” on page 579. A complete
been properly installed, configured, and activated on
explanation of MVS APPC return codes can be found in
the MVS system. Consult the ISPF installation
Writing Transaction Programs for APPC/MVS. Any
documentation for ISPF requirements. If you are using
additional message received with the prefix ″LSCX″ is
IBM TCP/IP for MVS ensure that the setting specified
issued by the SAS/C runtime support shipped with
or defaulted for the ″IPDATA″ or ″IPPREF″ parameter
ISPF. The message may provide additional helpful
value on the ISPMTAIL macro used to create the
information for the user or for support personnel.
ISPDFLTS module allows the TCP/IP system
parameters data set (tcpip.TCPIP.DATA) to be located.
ISPO932 Enter required field - Enter screen name Explanation: The download failed.
default at the cursor position.
User Response: Retry the download or use the
Explanation: The screen name default was left blank. Client/Server Component Download funtion of the
ISPF Utilities panel to download the workstation agent
User Response: Enter a valid choice for the screen manually.
name default.
Problem Determination: If problem persists, record
the return code reported in the message and contact
ISPO933 Download error RC = aaaaaaaa : An IBM Support.
unexpected error related to the host or
host data set, causing the download of
the workstation agent to fail. Verify the ISPO937 Agent not downloaded — The new
host data set, retry the download or use workstation agent was not downloaded.
the Client/Server Component Download You may download the agent manually
function of the ISPF Utilities panel to using the Client/Server Component
download the workstation agent Download funtion of the ISPF Utilities
manually. panel.
Explanation: The download failed. Explanation: The component was not downloaded.
User Response: Verify the host data set, retry the User Response: The user may wish to download the
download or use the Client/Server Component component.
Download funtion of the ISPF Utilities panel to
download the workstation agent manually.
ISPO938 You are using a downlevel version of
Problem Determination: If problem persists, record the ISPF workstation agent. Use the
the return code reported in the message and contact Client/Server Component Download
IBM Support. funtion from the ISPF Utilities panel to
download the latest version.
ISPO934 Download error RC = aaaaaaaa: An error Explanation: The workstation agent should be
related to the workstation or upgraded to thenew level.
workstation file caused the download of
User Response: The user should use the Client/Server
the workstion agent to fail. Check the
Component Download funtion of the ISPF Utilities
directory or try another directory.
panel to download the a new agent and then install the
Explanation: The download failed. There are several agent.
possible causes to the problem, including but not
limited to:
v out of space on disk
ISPP000 ISPF Log continued - - - Session # ISPP008 Trace: Command line - 2ND LEVEL
aaaaaaaa MSG NOT USED!!!, INSERTED
------------------------------------------------------- DIRECTLY IN TLD BY SEP
Explanation: This is an informational message. This Explanation: This is an informational message.
message is placed at the beginning of a continued ISPF
log file when the session number is available.
ISPP009 Start of ISPF Log - - - - Session # not
available
ISPP001 Start of ISPF Log - - - - Session # ----------------------------------------------
aaaaaaaa
Explanation: This is an informational message. This
-------------------------------------------------------
message is placed at the beginning of a new ISPF log
Explanation: This is an informational message. This file when the session number is not available.
message is placed at the beginning of a new ISPF log
file when the session number is available.
ISPP011 ISPF subtask abend - Completion code
= aaaaaaaa (No other information
ISPP002 End of ISPF Log - - - - - Session # available.)
aaaaaaaa
Explanation: The subtask failed.
-------------------------------------------------------
User Response: Contact your system programmer.
Explanation: This is an informational message. This
message is placed at the end of the ISPF log file when System Programmer Response: Contact IBM support.
the ISPF session is ended.
ISPP004 ***** Dialog Error ***** - ISPP013 Name aaaaaaaa EPA bbbbbbbb ISPSUBS
Application(aaaaaaaa); Function bbbbbbbb EPA cccccccc ISPTSI addr dddddddd
(cccccccc); Service(dddddddd)
Explanation: This is an informational message.
Explanation: This is an informational message. This
message is placed in the ISPF log file when a dialog
error occurs. ISPP014 Registers at - R0 aaaaaaaa R1 bbbbbbbb R2
cccccccc R3 dddddddd
ISPP006 Line from cmd: - aaaaaaaa ISPP016 Abend - R8 aaaaaaaa R9 bbbbbbbb R10
Explanation: This is an informational message. This cccccccc R11 dddddddd
message is added to the ISPF log file when a dialog Explanation: This is an informational message.
error pertains to the command syntax. ’aaaaaaaa’
contains the line where the error is found.
ISPP017 R12 aaaaaaaa R13 bbbbbbbb R14 cccccccc
R15 dddddddd
ISPP007 Line from skeleton: - aaaaaaaa
Explanation: This is an informational message.
Explanation: This is an informational message. This
message is added to the ISPF log file when a dialog
error occurs in skeleton processing. ’aaaaaaaa’ contains
the skeleton line where the error is found.
ISPP023 aaaaaaaa data set printed - bbbbbbbb ISPP028 Print utility exit - The print utility exit
cccccccc has been queued to dddddddd produced a return code of aaaaaaaa when
and deleted. processing bbbbbbbb cccccccc.
Explanation: This is an informational message. Explanation: This is an informational message.
ISPP023B aaaaaaaa data set printed - bbbbbbbb ISPP028B Print utility exit - The print utility exit
cccccccc has been queued to dddddddd produced a return code of aaaaaaaa on
and kept. request for batch job bbbbbbbb.
Explanation: This is an informational message. Explanation: This is an informational message.
ISPP024 aaaaaaaa print job error - bbbbbbbb cccccccc | ISPP031 Specify required field - Specify either
has been kept because of submit error. | the batch sysout class or the printer ID
| or writer-name.
Explanation: This message is self-explanatory.
Explanation: In order for ISPF to determine the
destination of the output, the batch sysout class OR the
ISPP025 aaaaaaaa not printed. - ISPP025 - ISPF
printer ID or writer-name is required.
Print RC = bbbbbbbb. See ISPF Messages
and Codes. cccccccc dddddddd has been User Response: Specify either the batch sysout class
kept. or the printer ID or writer-name.
Explanation: Possible return codes are:
2 The user cancelled local print.
ISPP103 Panel ’aaaaaaaa’ error - Attribute ISPP108 Panel ’aaaaaaaa’ error - Expected right
character found has already been parenthesis missing while processing
defined. keyword.
Explanation: A specific attribute character has been Explanation: A closing parenthesis (right parenthesis)
defined more than once in the attribute section. is missing from the keyword value of an attribute.
User Response: Contact the responsible programmer. Programmer Response: Check for a missing right
parenthesis on attribute keyword values in the attribute
Programmer Response: Examine the panel attribute
section.
section and determine which attribute character is
defined more than once. Ensure that each attribute
character is defined only once. ISPP109 Panel ’aaaaaaaa’ error - Invalid keyword
found within the )ATTR section.
ISPP104 Panel ’aaaaaaaa’ error - More than Explanation: A keyword that was not valid was found
bbbbbbbb attribute characters are defined. in the )ATTR section of a panel definition.
Explanation: The number of attribute characters The valid keywords for the )ATTR section are:
defined exceeds the maximum allowed, 127. This limit AREA, ATTN, CAPS, COLOR, DATAMOD,
includes the three default characters, attribute EXTEND, FORMAT, HILITE, INTENS, JUST,
overrides, and TBDISPL dual defaults. For action bar NUMERIC, OUTLINE, PAD, PADC, REP, SCROLL,
panels or panels with scrollable areas, you can specify a SKIP, TYPE, USERMOD
maximum of 110 attribute characters. This is because
Programmer Response: Check the )ATTR section for
ISPF uses some attribute characters internally for action
invalid or missing keywords.
bar panels or panels with scrollable areas.
Programmer Response: Limit the number of defined
ISPP110 Panel ’aaaaaaaa’ error - Attribute
attribute characters to a maximum of 127.
keyword found before an attribute
character.
ISPP105 Panel ’aaaaaaaa’ error - DEFAULT
Explanation: Each statement in the panel attribute
keyword out of order in )ATTR section
section, )ATTR, must begin with a single character or
of panel.
2-digit hexadecimal code. The remainder of the
Explanation: The DEFAULT keyword is not specified statement can contain keyword parameters.
correctly on the )ATTR section heading.
Programmer Response: Look for a keyword preceding
Programmer Response: Check the DEFAULT keyword the attribute.
on the )ATTR header statement. The )ATTR header
For example, the following statement produces this
statement allows only one DEFAULT keyword.
error:
PAD(’ ’) @ TYPE(INPUT) INTENS(HIGH)
ISPP106 Panel ’aaaaaaaa’ error - Invalid attribute
keyword value. The keyword, PAD(’ ’), should not precede the single
character attribute, @.
Explanation: The keyword value specified for an
attribute keyword is not one of the valid keyword
values. For example, the attribute keyword INTENS has
Explanation: The length of a panel record exceeds the Programmer Response: Ensure that the string of
defined screen width. variable names does not exceed the maximum size of
255 characters.
Programmer Response: Adjust any panel records that
exceed the screen width.
ISPP130 Panel ’aaaaaaaa’ error - A panel section is
out of order or has already been
ISPP125 Panel ’aaaaaaaa’ error - Duplicate panel defined.
field (or area) name defined.
Explanation: The panel definition sections must be
Explanation: The panel contains two fields or areas used in the following order:
with the same name. 1. )CCSID
ISPP131 Panel ’aaaaaaaa’ error - Required )BODY ISPP137 Panel ’aaaaaaaa’ error - Table display
records not found following heading. panel, duplicate )MODEL statement
found.
Explanation: A panel must have at least one line in
the )BODY section. Explanation: Only one )MODEL section is allowed per
panel.
Programmer Response: Check the )BODY section of
your panel and verify that the )BODY section has at Programmer Response: Remove the duplicate
least one line (record). )MODEL section from the panel definition.
ISPP132 Panel ’aaaaaaaa’ error - Invalid keyword ISPP138 Panel ’aaaaaaaa’ error - Invalid ″clear″
found in )INIT, )REINIT, or )PROC keyword value (not a literal or dialog
section. variable).
Explanation: An invalid keyword was found in the Explanation: The header CLEAR keyword value in the
)INIT, )REINIT, or )PROC sections of the panel. )MODEL section must be literal or a dialog variable.
Programmer Response: Check that valid keywords are Programmer Response: Verify that the section header
being used appropriately in the )INIT, )RENIT, and CLEAR keyword values in the )MODEL section are
)PROC sections of the panel. literals or dialog variables.
ISPP133 Panel ’aaaaaaaa’ error - Invalid statement ISPP139 Panel ’aaaaaaaa’ error - Something other
found within )INIT, )REINIT, or )PROC than CLEAR or ROWS keyword found
section. on )MODEL header statement.
Explanation: The )INIT, )REINIT, or )PROC section Explanation: The )MODEL section header contains an
contains an invalid statement. The valid statements for invalid keyword.
these panel sections are:
v Assignment Programmer Response: Use only the CLEAR or
v EXIT ROWS keywords on the )MODEL header statement.
v GOTO
v IF/ELSE ISPP140 Panel ’aaaaaaaa’ error - Built-in function
v REFRESH in the assignment statement is not
v TOG recognized.
v VER
v VEDIT Explanation: A built-in function defined in an
v VGET assignment statement is in error. Only the 4 built-in
v VPUT functions listed below are valid:
v PANEXIT v TRUNC (truncate)
v TRANS (translate)
Programmer Response: Verify that the panel v PFK (PF key)
statements in the )INIT, )REINIT, or )PROC section are v LVLINE (last visible line).
valid statements as shown in the list above.
ISPP146 Panel ’aaaaaaaa’ error - Invalid built-in ISPP151 Panel ’aaaaaaaa’ error - I/O error in
function variable specified. retrieving panel (CDG).
Explanation: The variable used within the built-in Explanation: An attempt to retrieve the panel to read
function is invalid. a logical record of the panel has failed.
Programmer Response: Check for invalid variables User Response: Try to display the panel again. If this
within the TRUNC and TRANS built-in functions. fails, contact your system programmer.
System Programmer Response: Contact IBM support.
ISPP147 RESTORE request error - A CONTROL
service request, for which there was no
ISPP152 Panel ’aaaaaaaa’ error - Invalid CDG
matching SAVE.
return code, system error.
Explanation: For each CONTROL service Restore
Explanation: An error occurred while trying to read a
request, there should be a matching CONTROL service
panel record.
Save request.
User Response: Try to display the panel again. If this
Programmer Response: Verify that the CONTROL
fails, contact your system programmer.
service Restore requests have matching Save requests.
System Programmer Response: Contact IBM support.
ISPP158 Panel ’aaaaaaaa’ error - Invalid field/area Explanation: The value used in the TRUNC built-in
name assigned to the .CURSOR control function is invalid. The value must be a literal or a
variable. dialog variable.
Explanation: The .CURSOR control variable is set to Programmer Response: Correct the value in the
an invalid panel field name or to a scrollable area TRUNC built-in function to be a literal or a dialog
name. variable.
ISPP167 Panel ’aaaaaaaa’ error - Invalid IF ISPP171 Panel ’aaaaaaaa’ error - Invalid value for
keyword value (not a literal, dialog or TYPE keyword found while initializing
control variable). panel.
Explanation: The IF statement keyword value is Explanation: A dialog variable was used for a TYPE
invalid. The IF statement keyword values must be keyword value and that TYPE keyword value must be
literals, dialog variables, or control variables. coded explicitly. The following TYPE values must be
coded explicitly. It is invalid to assign any of these
Programmer Response: Check the IF statements
values to dialog variables. The TYPE values are:
keyword values and verify that they are literals, dialog
AB
variables, or control variables.
NT
Programmer Response: Verify that the TYPE values in
ISPP168 Panel ’aaaaaaaa’ error - Invalid IF
the list above have been coded explicitly and not as
keyword operator found.
dialog variables.
Explanation: The operator used in the IF statements
basic value test expression is invalid. Valid operators
ISPP172 Panel ’aaaaaaaa’ error - Invalid TRUNC
are:
value (dialog var) found while
= EQ
processing panel.
¦= NE
< LT Explanation: The TRUNC built-in function value (a
> GT dialog variable) is neither a numeric quantity indicating
¦> NG the length of the truncated result, nor any special
¦< NL character indicating truncation at the first occurrence of
>= GE that character.
<= LE
Programmer Response: Check that the dialog variable
for the TRUNC value is a numeric quantity or a special
Character symbol operators must be specified in
character, whichever is appropriate.
uppercase.
If character symbols are used (for example, EQ or NE), ISPP173 Panel ’aaaaaaaa’ error - More than
use a blank to delimit them. Blanks cannot appear bbbbbbbb entries specified for a tutorial
between compound numeric (for example, >=, ¦<) or TRANS function.
character symbols.
Explanation: The maximum number of entries
Programmer Response: Examine the IF statement for allowed is 100.
invalid syntax.
Programmer Response: Limit the number of entries
specified for a tutorial TRANS function to 100.
ISPP169 Panel ’aaaaaaaa’ error - Invalid IF logical
expression (not a dialog or control
ISPP174 Panel ’aaaaaaaa’ error - Invalid value for
variable or VER statement construct).
a verify PICT string found while
Explanation: The IF statement syntax is invalid. The processing panel.
IF statement may contain dialog variables, control
Explanation: A PICT string in a VER statement in the
variables, or the VER statement construct.
)INIT, )REINIT, or )PROC section of a panel definition
Programmer Response: Examine the IF statement for is incorrect.
invalid syntax.
The valid syntax is VER (xxx,PICT,string), where xxx is
a variable. The string parameter can be composed of
ISPP170 Panel ’aaaaaaaa’ error - Invalid ATTR any of the following:
keyword value (dialog var) found while C Any character
initializing panel. A Any alphabetic character (A-Z, #, @, $)
N Any numeric character (0-9)
Explanation: The dialog variable used for an )ATTR 9 Any numeric character (same as ″N″)
section keyword value is invalid. The dialog variable is X Any hexadecimal character (0-9, A-F)
substituted after processing the )INIT section.
Programmer Response: Check the dialog variables In addition, the string can contain any special
used in the )ATTR section for keyword values. Ensure characters (except #, @, $) or lowercase alphabetic
that the dialog variables are set to valid values. characters.
ISPP183 Panel ’aaaaaaaa’ error - Incorrect # of ISPP186 Panel ’aaaaaaaa’ error - Invalid VERIFY
VERIFY values for verification type type given (second parameter must be a
indicated. literal).
Explanation: An incorrect number of verify values is Explanation: The VER statement second parameter,
specified for the verification type that is indicated. NONBLANK, is a literal. The literal, NB, may be used
as an abbreviation of NONBLANK.
Programmer Response: Check the syntax for the VER
statement that uses your keyword type for verification. Programmer Response: Update the second parameter
of the VER statement to either NONBLANK or NB.
ISPP184 Panel ’aaaaaaaa’ error - Invalid VERIFY
picture string given. ISPP187 Panel ’aaaaaaaa’ error - Invalid VERIFY
variable (must be a dialog variable).
Explanation: A PICT string in a VER statement in the
)INIT, )REINIT, or )PROC section of a panel definition Explanation: The first parameter of the VER statement
is incorrect. inside the parentheses specifies the name of the
variable to be checked. This first parameter must be a
The valid syntax is VER (xxx,PICT,string), where xxx is
dialog variable.
a variable and the ″string″ parameter can be composed
of any of the following: Programmer Response: Check the first parameter
specified and verify that this parameter is a dialog
C Any character
variable.
A Any alphabetic character (A-Z, #, @, $)
N Any numeric character (0-9) ISPP188 Panel ’aaaaaaaa’ error - Maximum of 100
list values exceeded on VER statement.
9 Ay numeric character (same as ″N″)
Explanation: In the VER statement construct
X Ay hexadecimal character (0-9, A-F) ″LIST,value1,value2,...″, the list of values cannot exceed
100.
In addition, the string can contain any special
characters (except #, @, or $) or lowercase alphabetic Programmer Response: Limit your list of values in the
characters. VER statement to fewer than or equal to 100.
Example: VER(xxx, PICT,’A/NNN’) The value of the ISPP189 Panel ’aaaaaaaa’ error - Control variable
variable must start with an alphabetic character compare value too long, maximum
followed by a slash, followed by 3 numeric characters. length is 8 bytes.
Programmer Response: Correct the VER statement Explanation: An error was found in the IF statement
picture string. processing comparing a control variable to a value that
exceeds the maximum length of 8 bytes.
ISPP185 Panel ’aaaaaaaa’ error - Invalid VERIFY Programmer Response: Verify that the IF statement
range value given. processing is comparing the control variable to a valid
Explanation: A RANGE limit in a VER statement in value.
the )INIT, )REINIT, or )PROC section of a panel
definition is not valid. | ISPP190 Enter required field - Enter required
The valid syntax is: | field at the cursor position.
VER (xxx,RANGE,lowerlimit,upperlimit) Explanation: A VER statement containing the
where: NONBLANK keyword failed. The field is blank.
xxx is a variable User Response: Enter the appropriate data into the
″Lowerlimit″ and ″upperlimit″ must be numeric field at the cursor position.
characters (0-9) of no more than 16 digits each.
Programmer Response: If the field is not defined in
Negative values can be specified. the panel )BODY section, define the field in the panel
Programmer Response: Correct the RANGE limit, )BODY section.
following the guidelines.
| ISPP190A Missing field definition - The field ISPP196 Must be a bit string - Enter all ’0’s or
| definition ’aaaaaaaa’ is missing in the ’1’s.
| panel )BODY section. When the field
Explanation: This is an ISPF-supplied message
| definition is missing, the cursor position
displayed as the result of a BIT verification failure.
| is unpredictable.
User Response: Enter a binary value into the field
| Explanation: A VER statement containing the
pointed to by the cursor.
| NONBLANK keyword failed. The field is not defined
| in the panel )BODY section.
ISPP197 Invalid fileid - Variable must contain a
| Programmer Response: If the field is not defined in
fileid (CMS syntax), valid with a
| the panel )BODY section, define the field in the panel
LISTFILE command.
| )BODY section.
Explanation: This is an ISPF-supplied message
displayed as the result of a FILEID verification failure.
ISPP191 Must be alphabetic - Enter alphabetic
The file name and type, if given, must be 1 to 8
characters (A-Z, a-z, #, $, or @).
alphanumeric characters, including A-Z, 0-9, $, #, @, +,
Explanation: This is an ISPF-supplied message - (hyphen), : (colon), and _ (underscore). The filemode
displayed as the result of an alphabetic verification must be a single letter (A-Z), optionally followed by a
failure. single digit (0-9). In addition, one or more fields of the
file ID can be an asterisk (*) or a string of characters
User Response: Enter the appropriate data into the
followed by an asterisk.
field pointed to by the cursor.
User Response: Enter a valid file ID in CMS syntax.
ISPP192 Must be hexadecimal - Enter
hexadecimal characters (0-9, A-F, a-f). ISPP198 Must be numeric - Enter a numeric
value between ’aaaaaaaa’ and ’bbbbbbbb’.
Explanation: This is an ISPF-supplied message
displayed as the result of a hexadecimal verification Explanation: This is an ISPF-supplied message
failure. displayed as the result of a RANGE verification failure.
User Response: Enter the appropriate data into the User Response: Enter a valid numeric value within
field pointed to by the cursor. the range specified.
ISPP193 Must be numeric - Enter numeric ISPP199 Invalid value - Field has failed
characters (0-9). verification. Reenter or press the End
key.
Explanation: This is an ISPF-supplied message
displayed as the result of a numeric verification failure. Explanation: This is an ISPF-supplied message
displayed as the result of a verification failure.
User Response: Enter the appropriate data into the
field pointed to by the cursor. User Response: Reenter data or press the END key.
ISPP194 Value out of range - Enter a numeric | ISPP200 Invalid name - Enter up to 8
value between aaaaaaaa. and bbbbbbbb. | alphanumeric chars (first must be
| alphabetic).
Explanation: This is an ISPF-supplied message
displayed as the result of a RANGE,lower limit,upper | Explanation: The variable must contain a valid name,
limit verification failure. | following the rules of member names, using up to eight
| alphanumeric characters (A-Z, #, $, @, 0-9). The first
User Response: Enter the appropriate data into the
| character must be alphabetic (A-Z, #, $, @).
field pointed to by the cursor.
| User Response: Reenter the member name, following
| the rules for member names.
ISPP195 Invalid value - Enter one of the listed
values. | Programmer Response: None
Explanation: This is an ISPF-supplied message
displayed as the result of a LIST,value1,value2,...
verification failure.
User Response: Enter one of the listed values into the
field pointed to by the cursor.
ISPP202 Invalid sign - Press the Help key for 999,765.800 is correct.
additional information. 999,7658.00 is incorrect (4 digits between the
Explanation: The correct sign notation was not used. numerical indicator and and the
Sign notation for a number is not required, but if you decimal).
do use it, remember the following rules:
v Indicate a negative number by a leading minus sign, ISPP205 Panel ’aaaaaaaa’ error - Invalid VERIFY
-695; a trailing minus sign, 695-; or a number length operator.
enclosed in parentheses, (695).
Explanation: The length of the variable (number of
v If the number is negative, you cannot use blanks characters) must satisfy the condition expressed by the
between the sign indicator and the number unless relational operator and expected length. You have used
the numerical delimiter is a blank. an invalid relational operator.
v Indicate a positive number by a leading plus sign,
User Response: Contact the responsible programmer.
+695; or a number with no sign, 695.
Programmer Response: Correct the invalid relational
User Response: Contact the responsible programmer.
operator. Valid relational operators are:
Programmer Response: Correct the sign notation. = or EQ
Refer to the discussion in ISPF Dialog Developer’s Guide ¦= or NE
ISPP212 Invalid DSN - length - Dsname must be ISPP216 Invalid DSN - qualifier - Each qualifier
1-44 chars in length, including prefix. must be 1-8 alphanumeric characters, the
Reenter dsname. first alphabetic.
Explanation: The VER statement with the DSNAME Explanation: The VER statement with the DSNAME
keyword has detected an invalid TSO data set name. keyword has detected an invalid TSO data set name.
The data set name must be 1-44 characters in length, The data set name qualifiers must contain from 1-8
including prefix. characters and the first character of each qualifier must
be alphabetic.
User Response: Reenter the data set name. The data
set name must be 1-44 characters in length, including User Response: Reenter the data set name. The data
prefix. set name qualifiers must contain from 1-8 characters
and the first character of each qualifier must be
Programmer Response: Verify that the data set name
alphabetic.
assigned to the variable in the VER statement complies
with the data set name length of 1-44 characters. Programmer Response: Verify that the data set name
assigned to the variable in the VER statement does not
contain qualifiers greater than eight characters or less
ISPP213 Invalid DSN - syntax - Dsname must
than one character. Also, verify that the first character
not end with a period. Reenter dsname.
of each qualifier is alphabetic.
Explanation: The VER statement with the DSNAME
keyword has detected an invalid TSO data set name.
ISPP217 Invalid number - A valid number
The data set name must not end with a period.
contains at least one digit (0-9).
User Response: Reenter the data set name. Do not
Explanation: A VER statement expected a valid
end the data set name with a period.
number. A valid number contains at least one digit
Programmer Response: Verify that the data set name (0-9).
assigned to the variable in the VER statement does not
User Response: Enter a valid number.
end with a period.
ISPP227 Panel ’aaaaaaaa’ error - Specify 255 or ISPP234 Panel ’aaaaaaaa’ error - The IF statement
less IF compare values for operator has an illegal format. A Boolean
’bbbbbbbb’. operator is specified with no following
logical expression.
Explanation: More than 255 compare values are
specified for the IF statement with the operator EQ (=) Explanation: The IF statement has a Boolean operator
or NE (¬=). but no following logical expression.
User Response: Contact the responsible programmer. User Response: Contact the responsible programmer.
Programmer Response: Limit the compare values to Programmer Response: Redefine the IF statement
255 values for the IF statement with the operator EQ following IF statement syntax:
(=) or NE (¬=).
IF (logical-expression Boolean operator logical
expression)
ISPP228 Panel ’aaaaaaaa’ error - MSG= parameter
is illegal in IF statement VER logical
ISPP235 Panel ’aaaaaaaa’ error - Invalid LISTV
expression.
value given for VERIFY statement (must
Explanation: The IF statement conditional-expression be a dialog variable).
supports the VER statement construct coded without
Explanation: The LISTV value is not a dialog variable.
the MSG=parameter.
The keyword LISTV on a VER statement allows the use
User Response: Contact the responsible programmer. of a dialog variable containing a list of values to be
used for the variable field verification.
Programmer Response: Remove the MSG=parameter
from the IF statement’s VER statement construct. User Response: Contact the responsible programmer.
Programmer Response: Place the list of values to be
ISPP229 Panel ’aaaaaaaa’ error - The IF statement used for variable field verification into a dialog
has an illegal format. More than 255 variable. The following example verifies an area code
logical expressions have been specified. field. In the )INIT section, the LISTV value &varlist is
set to the following area codes:
Explanation: The IF statement supports Boolean
operators and allows you to combine up to 255 logical &varlist = ’919 805 312’.
expressions. You have exceeded the limit of 255
In the )PROC section, the following VER statement is
expressions.
coded:
User Response: Contact the responsible programmer.
VER (&areacode,NONBLANK,LISTV,&varlist,
Programmer Response: Limit the number of logical
MSG=NSL011)
expressions specified on the IF statement to 255.
Programmer Response: Check the .ZVAR assignment Explanation: If a list of names is assigned to .ZVARS,
statement for duplicate names and ensure all names in the name list must be enclosed in parentheses. The
the list are unique. .ZVARS name list is missing a right parenthesis.
User Response: Contact the responsible programmer.
Programmer Response: Supply the missing right
parenthesis to the .ZVARS statement name list.
ISPP286 Panel ’aaaaaaaa’ error - The area ISPP290 Panel ’aaaaaaaa’ error - The EXPAND
referenced by the LVLINE function is designation is improperly used within
not a dynamic or graphic area on the the panel record.
panel.
Explanation: Within the panel body, the expand
Explanation: The LVLINE built-in function provides delimiters have been used improperly. The format of
the line number of the last visible line within a graphic the EXPAND keyword on the )BODY statement is:
or dynamic area on the currently displayed panel. The EXPAND(xy). The value, xy, represents the repetition
value parameter of the LVLINE function is the name of delimiter characters. Once defined, these delimiters can
the graphic or dynamic area. This function is valid for be used on any line within the panel body to enclose a
dynamic or graphic areas only. single character that is to be repeated to expand the
line to the required width. A missing right or left
Programmer Response: Verify that the value of the
delimiter around the single character to be expanded
LVLINE function is a literal that is the name of the
could cause this error.
graphic or dynamic area, or a dialog variable that
contains the name of the graphic or dynamic area. Programmer Response: Verify that the expand
character in the panel body record is enclosed by both
a starting and an ending delimiter.
ISPP287 Panel ’aaaaaaaa’ error - Invalid LVLINE
area name found while processing
panel. ISPP291 Panel ’aaaaaaaa’ error - EXPAND
keyword value may not be blank, ″&″,
Explanation: The LVLINE built-in function provides
or an attribute character.
the line number of the last visible line within a graphic
or dynamic area on the currently displayed panel. The Explanation: The format of the EXPAND keyword on
value parameter of the LVLINE function is the name of the )BODY statement is: EXPAND(xy). The value, xy,
the graphic or dynamic area. This function is valid for represents the repetition delimiter characters. The
dynamic or graphic areas only. delimiter characters cannot be blanks, dialog variables
(&xx), or attribute characters.
Programmer Response: Verify that the value of the
LVLINE function is a literal that is the name of the Programmer Response: Verify that the delimiter
graphic or dynamic area or a dialog variable that characters are not blanks, dialog variables, or attribute
contains the name of the graphic or dynamic area. characters.
ISPP288 Panel ’aaaaaaaa’ error - Invalid WIDTH ISPP292 Panel ’aaaaaaaa’ error - Invalid field/area
keyword value type (not a literal or name specified on REFRESH statement.
dialog variable). It must be less than or equal to 8
characters.
Explanation: An invalid WIDTH keyword value has
been found. The WIDTH keyword’s value on the Explanation: The field or area name specified on the
)BODY header statement can be a literal or a dialog REFRESH statement had an invalid length. The field or
variable. The WIDTH value must be numeric, not less area name must be fewer than or equal to 8 characters.
than 80 or greater than the width of the terminal on
Programmer Response: Correct the field or area name
which the panel is to be displayed.
to be fewer than or equal to 8 characters.
Programmer Response: Verify that the WIDTH
keyword value on the )BODY header statement is a
ISPP293 Panel ’aaaaaaaa’ error - REFRESH is
literal or a dialog variable.
specified for a field or area that is not
on the panel.
ISPP289 Panel ’aaaaaaaa’ error - Invalid WIDTH
Explanation: ISPF searched the fields in the panel
value, (must be numeric chars, >= 80, <=
body to find a match for the field area name specified
screen width).
on the REFRESH statement and could not find a match.
Explanation: An invalid WIDTH keyword value has
Programmer Response: Verify that the field or area
been found. The value of the WIDTH keyword on the
name specified on the REFRESH statement in the
)BODY header statement can be a literal or a dialog
)PROC or )REINIT section is spelled correctly or is
variable. The WIDTH value must be numeric, not less
actually the name of a field or area as defined in the
than 80 or greater than the width of the terminal on
panel body.
which the panel is to be displayed.
Programmer Response: Verify that the WIDTH
keyword value is numeric and not less than 80 or
greater than the width of the terminal on which the
panel is to be displayed.
ISPP305 Panel ’aaaaaaaa’ error - Invalid attribute ISPP311 Panel ’aaaaaaaa’ error - String of attribute
TYPE change attempted in an ATTR override keywords exceeds maximum
override statement. size of 255 characters.
Explanation: There is an invalid type attribute Explanation: The string of keywords on a .ATTR or
override. .ATTRCHAR statement exceeds 255 characters.
Programmer Response: For more information about Programmer Response: Correct the panel.
the .ATTR and .ATTRCHAR override conditions, see
ISPF Dialog Developer’s Guide and Reference
ISPP312 Panel ’aaaaaaaa’ error - ″Scrollable″ or
″extendable″ area not allowed in a table
ISPP306 Panel ’aaaaaaaa’ error -.ATTRCHAR display panel.
defines a new character that is not
Explanation: The SCROLL and EXTEND keywords are
DATAIN or DATAOUT.
not valid when defining an area in a TBDISPL panel.
Explanation: A new attribute character must be used
Programmer Response: Correct the panel.
on DATAIN or DATAOUT field.
Programmer Response: Do not use a new attribute
ISPP313 Panel ’aaaaaaaa’ error - An AREA
character unless it is for a DATAIN or DATAOUT field.
definition is not permitted within the
″)MODEL″ section.
ISPP307 Panel ’aaaaaaaa’ error - Invalid override
Explanation: Any attribute except those associated
of cmd field or scroll amt field to
with dynamic, graphic, or scrollable areas (AREA,
TYPE(OUTPUT)
EXTEND, SCROLL, USERMOD, and DATAMOD) can
Explanation: TYPE(OUTPUT) cannot be used to be used with any fields in the model lines.
override the command field or the scroll amount field.
Programmer Response: Correct the panel )MODEL
Programmer Response: Correct the override on the section.
panel.
ISPP314 Panel ’aaaaaaaa’ error - Invalid to specify
ISPP308 Panel ’aaaaaaaa’ error - Invalid PAD both PAD and PADC attributes for one
character specified in .ATTR or field.
.ATTRCHAR statement.
Explanation: You cannot specify both a pad character
Explanation: An .ATTR or .ATTRCHAR statement (PAD) and a conditional pad character (PADC) for the
used an invalid PAD character. same field.
Programmer Response: Correct the .ATTR or Programmer Response: Correct the attribute in the
.ATTRCHAR statement in the panel. panel.
ISPP309 Panel ’aaaaaaaa’ error -.AUTOSEL value ISPP315 Invalid MODEL definition - A variable
was not YES or NO or blank. model line may not be defined as a
variable itself.
Explanation: Set .AUTOSEL to YES to retrieve the
CSRROW, even if the user did not explicitly select the Explanation: If a variable begins in column 1 of any
row. Set .AUTOSEL to NO if the row is to be retrieved model line, the value of that variable defines the model
only if the user explicitly selects the row. line. The variable can contain any character string that
is a valid panel definition model line, except that the
Programmer Response: Correct the .AUTOSEL
variable cannot define a variable model line.
statement in the panel.
Programmer Response: Correct the model line in the
panel.
ISPP310 Panel ’aaaaaaaa’ error - Maximum
allowable number of attributes exceeded
by attribute override. ISPP316 Model line not defined - The variable
model line has not been initialized
Explanation: Attribute overrides plus attributes exceed
before the display.
255.
Explanation: All model line variables must be
Programmer Response: Correct the panel.
initialized before the table display service is called with
a nonblank panel name.
ISPP317 Invalid model definition - The variable ISPP323 Panel ’aaaaaaaa’ error - More than 126
model is the only information allowed pairs have been specified for the
coded on the line. TRANS function.
Explanation: For variable model lines, the variable Explanation: TRANS logic has exceeded the maximum
must be the only information on the model line. pairs allowed.
Programmer Response: Correct the model line on the Programmer Response: The TRANS function of the
panel. panel must use fewer than 126 pairs.
ISPP318 Invalid model definition - The variable ISPP324 Panel ’aaaaaaaa’ error - A panel cannot
model line width is greater than the be preprocessed when WIDTH is
panel width. specified as dialog variable.
Explanation: The value of the variable is greater than Explanation: The preprocessor will not preprocess
the panel width. panels that use a dialog variable with the WIDTH
keyword.
Programmer Response: Correct the model section of
the panel. Programmer Response: See ″Restrictions for using
ISPPREP″ in ISPF Dialog Developer’s Guide and Reference
ISPP319 Panel ″aaaaaaaa″ error - The command
field may not be located within the ISPP325 Panel ’aaaaaaaa’ error - A panel cannot
)MODEL section. be preprocessed with areas defined as
extendable.
Explanation: The command field is identified as either
the first input field in the panel, or by the CMD Explanation: The specification of EXTEND(ON) will
keyword of the )BODY statement. If the command field cause ISPPREP to bypass the panel during
is within the )MODEL section, an error occurs. preprocessing.
Programmer Response: Correct the )MODEL section Programmer Response: Determine if EXTEND(ON) is
by removing the command field. needed. If it is needed, the panel cannot be
preprocessed.
ISPP320 Panel ’aaaaaaaa’ error - Panel control
variable .PFKEY cannot be set by a ISPP326 Panel ’aaaaaaaa’ error - A panel cannot
dialog. be preprocessed when model lines are
specified as variables.
Explanation: .PFKEY cannot be set to a value, it is
read only. Explanation: Model lines cannot be defined as
variables if the panels are to be preprocessed.
Programmer Response: Remove the panel statement
that attempts to set .PFKEY. Programmer Response: If the panel must be
preprocessed, the model lines must not be specified as
variables.
ISPP321 Panel ’aaaaaaaa’ error - The INIT,
REINIT, AREA, or PROC section is too
long. ISPP327 Panel ’aaaaaaaa’ error - Variable name or
name-list not coded for ’bbbbbbbb’
Explanation: There is a potential 32KB internal table
statement.
overflow because of the number of statements in the
panel. Explanation: The panel statement requires additional
data.
Programmer Response: Either reduce the number of
statements in the panel or use more than one panel. Programmer Response: Complete the panel statement
by adding a variable or a name-list.
ISPP322 Panel ’aaaaaaaa’ error - A panel must
have at least one line in the )BODY
section.
Explanation: The body section defines the format of
the panel as seen by the user. A valid panel must have
at least one line in the )BODY section.
ISPP328 Panel ’aaaaaaaa’ error - Required keylist ISPP341 Panel ’aaaaaaaa’ error - Panel exit
’bbbbbbbb’ in applid ’cccccccc’ was not message ID must be literal or dialog
found. variable.
Explanation: This message is self-explanatory. Explanation: If the MSG keyword of the PANEXIT
statement is specified, the message id must be either a
Programmer Response: Create the proper named
literal value or a dialog variable.
keylist or use an existing keylist.
Programmer Response: Correct the panel exit routine,
MSGID must be a dialog variable or a literal value.
ISPP330 BDISPMAX exceeded - aaaaaaaa displays
exceeded in batch mode on panel
bbbbbbbb. ISPP342 Panel ’aaaaaaaa’ error - Panel exit type
must be a literal.
Explanation: Either the maximum number of displays
set in variable BDISPMAX on the ISPSTART command, Explanation: The exit type must be PGM or LOAD.
or the default value of 100 has been exceeded.
Programmer Response: Use the literal PGM or LOAD
Programmer Response: Verify that the batch job is not as the exit type.
looping and, if not, increase the value of BDISPMAX.
See ″Avoiding panel loop conditions in the Batch
ISPP343 Panel ’aaaaaaaa’ error - Valid panel exit
environment″ in ISPF Dialog Developer’s Guide and
type is PGM or LOAD.
Reference
Explanation: This message is self-explanatory.
ISPP331 BREDIMAX exceeded - aaaaaaaa .msg Programmer Response: Use PGM or LOAD for exit
redisplays exceeded in batch mode. type.
Explanation: The Batch redisplay value in BREDIMAX
on the ISPSTART command or the default value of 2 ISPP344 Panel ’aaaaaaaa’ error - Invalid dialog
has been exceeded. variable name length on panel exit
statement.
Programmer Response: Verify that the Batch job is not
looping on a redisplay and, if not, increase the value of Explanation: The variable name length on the panel
BREDIMAX. See ″Message processing in the Batch exit statement exceeds 8 characters.
environment″ in ISPF Dialog Developer’s Guide and
Reference Programmer Response: Use a variable name with a
length not exceeding 8 characters.
Explanation: A panel was displayed while in batch Explanation: The exit routine returned RC=8 but did
mode. The following message was displayed. not provide a MSGID to describe the failure. This
generic message is provided by ISPF.
Programmer Response: This is an informational
message. The message following this one may contain Programmer Response: If appropriate, provide a
important information. Refer to that message number meaningful error message for the user.
in this manual for additional information, if needed.
ISPP346 Panel ’aaaaaaaa’ error - Severe error
ISPP340 Panel ’aaaaaaaa’ error - Panel exit address encountered during panel exit routine.
must be dialog variable. Explanation: A severe error was encountered while
Explanation: The panel exit cannot be processed executing the panel exit routine.
because the address is not a variable. Programmer Response: The return code from exit
Programmer Response: Correct the panel exit to processing was not 0 or 8. The return code could have
include a variable for exit-add. See ″Invoking the panel been 20 for severe error or some other return code that
exit user routine″ in ISPF Dialog Developer’s Guide and was not recognized by ISPF. Verify that your exit
Reference returned valid data. If the data is valid, contact IBM
support for assistance.
ISPP380 Panel ’aaaaaaaa’ error - COLOR, ISPP383 Panel ’aaaaaaaa’ error - Invalid label on
INTENS, or HILITE keywords cannot be GOTO statement.
specified on CUA panel element
Explanation: The label for a GOTO statement is
attributes.
syntactically incorrect. Labels can only be 1 to 8
Explanation: Either COLOR, INTENS, or HILITE was characters long and must start with A-Z or a-z. The
specified on an attribute assignment that has a CUA remaining characters can be A-Z, a-z, or 0-9.
panel element as a TYPE. This is not allowed.
User Response: There was a programming error
User Response: There was a programming error defining the panel that you attempted to display. If you
defining the panel that you attempted to display. If you are running in TEST mode, you can either override the
are running in TEST mode, you can either override the error and attempt to continue running the dialog, or
error and attempt to continue running the dialog, or you can choose not to override the error. If you select
you can choose not to override the error. If you select the latter, the dialog will end and you will be returned
the latter, the dialog will end and you will be returned to the initial panel for the application.
to the initial panel for the application.
Programmer Response: Specify a correct label.
Programmer Response: Either remove the COLOR,
INTENS, or HILITE keyword, or do not use a CUA
ISPP384 Panel ’aaaaaaaa’ error - GOTO label
panel element for the TYPE.
’bbbbbbbb’ not found.
Explanation: The label specified on a GOTO statement
ISPP381 Panel ’aaaaaaaa’ error - The CAPS
was not found in the section in which the GOTO is
keyword value cannot be overridden on
specified. A label must be followed by a colon.
the CUA panel element attributes AB or
RP. User Response: There was a programming error
defining the panel that you attempted to display. If you
Explanation: Action bar and Reference phrase CUA
are running in TEST mode, you can either override the
panel element attributes cannot have the CAPS
error and attempt to continue running the dialog, or
keyword specified in the )ATTR section.
you can choose not to override the error. If you select
User Response: There was a programming error the latter, the dialog will end and you will be returned
defining the panel that you attempted to display. If you to the initial panel for the application.
are running in TEST mode, you can either override the
Programmer Response: Correct the label on the
error and attempt to continue running the dialog, or
GOTO or the label itself.
you can choose not to override the error. If you select
the latter, the dialog will end and you will be returned
to the initial panel for the application. ISPP385 Panel ’aaaaaaaa’ error - TYPE(RP)
attribute valid only on a panel
Programmer Response: Remove the CAPS keyword.
displayed by ISPF help.
Explanation: Reference Phrase CUA panel element
ISPP382 Panel ’aaaaaaaa’ error - TYPE(EE) valid
attributes are only allowed on panels being displayed
for overrides on input fields only.
by ISPF Help (Tutorial).
Explanation: The dialog attempted to override an
User Response: There was a programming error
attribute with an Error Emphasis (EE) CUA panel
defining the panel that you attempted to display. If you
element TYPE. This is only valid when the field being
are running in TEST mode, you can either override the
overridden is an input field.
error and attempt to continue running the dialog, or
User Response: There was a programming error you can choose not to override the error. If you select
defining the panel that you attempted to display. If you the latter, the dialog will end and you will be returned
are running in TEST mode, you can either override the to the initial panel for the application.
error and attempt to continue running the dialog, or
Programmer Response: Do not use TYPE(RP) in
you can choose not to override the error. If you select
panels that are not displayed by ISPF Help.
the latter, the dialog will end and you will be returned
to the initial panel for the application.
ISPP386 Panel ’aaaaaaaa’ error - TYPE(RP)
Programmer Response: Do not override the attribute
attribute usage requires )HELP section
with TYPE(EE).
definition.
Explanation: If a reference phrase attribute is used in
the )BODY section, an accompanying statement in the
)HELP section must exist to tell which panel is to be
displayed.
ISPP425 Choice value error - The pull-down ISPP430 Panel ’aaaaaaaa’ error - Invalid or
choice value length is not between 1 missing parameter on TOG statement.
and 8 characters.
Explanation: A syntax error was found on the TOG
Explanation: The selection for the pull-down choice statement.
was invalid. It cannot be more than 8 digits.
User Response: There was a programming error
User Response: Enter a valid pull-down choice defining the panel that you attempted to display. If you
selection. are running in TEST mode, you can either override the
error and attempt to continue running the dialog, or
you can choose not to override the error. If you select
ISPP426 Choice value error - The pull-down
the latter, the dialog will end and you will be returned
choice value must be numeric.
to the initial panel for the application.
Explanation: A non-numeric value was entered for the
Programmer Response: Correct the TOG statement.
pull-down choice. The value must be a number.
User Response: Enter a valid pull-down choice
ISPP431 Panel ’aaaaaaaa’ error - Too many tokens
selection.
given on TOG statement.
Explanation: Too many parameters were specified on
ISPP427 Choice value error - The pull-down
the TOG statement.
choice value must equal an available
choice number. User Response: There was a programming error
defining the panel that you attempted to display. If you
Explanation: The only values that are acceptable for a
are running in TEST mode, you can either override the
pull-down choice are those listed in the pull-down
error and attempt to continue running the dialog, or
menu.
you can choose not to override the error. If you select
User Response: Enter a valid pull-down choice the latter, the dialog will end and you will be returned
selection. to the initial panel for the application.
Programmer Response: Correct the TOG statement.
ISPP428 Panel ’aaaaaaaa’ error - Invalid UNAVAIL
variable name found on PDC statement.
ISPP432 Panel ’aaaaaaaa’ error - No dialog
Explanation: The UNAVAIL variable name is not a variable specified on TOG statement.
valid dialog variable name.
Explanation: The third parameter, the dialog variable,
User Response: There was a programming error was omitted from the TOG statement.
defining the panel that you attempted to display. If you
User Response: There was a programming error
are running in TEST mode, you can either override the
defining the panel that you attempted to display. If you
error and attempt to continue running the dialog, or
are running in TEST mode, you can either override the
you can choose to not override the error. If you select
error and attempt to continue running the dialog, or
the latter, the dialog will end and you will be returned
you can choose not to override the error. If you select
to the initial panel for the application.
the latter, the dialog will end and you will be returned
Programmer Response: Correct the dialog variable to the initial panel for the application.
name for the UNAVAIL keyword.
Programmer Response: Correct the TOG statement.
ISPP481 Panel ’aaaaaaaa’ error - A ’)PNTS’ section ISPP484 Panel ’aaaaaaaa’ error - Duplicate
statement contains two VAR() keywords FIELD(name) found in ’PNTS’ section.
or the statement’s VAL() keyword is
Explanation: The ’)PNTS’ statement contains a valid
missing.
FIELD(), VAR() and VAL() keyword followed by a
Explanation: The ’)PNTS’ statement contains an duplication of the FIELD() keyword.
invalid number of VAR() keywords or the VAL()
User Response: There was a programming error
keyword is missing.
defining the panel that you attempted to display. If you
User Response: There was a programming error are running in TEST mode, you can either override the
defining the panel that you attempted to display. If you error and attempt to continue running the dialog, or
are running in TEST mode, you can either override the you can choose not to override the error. If you select
error and attempt to continue running the dialog, or the latter, the dialog will end and you will be returned
you can choose not to override the error. If you select to the initial panel for the application.
the latter, the dialog will end and you will be returned
Programmer Response: Correct the ’)PNTS’ statement,
to the initial panel for the application.
ensuring that the statement contains only one of each
Programmer Response: Correct the ’)PNTS’ section keyword FIELD(), VAR() and VAL() per statement.
statement, ensuring that the statement contains only
one of each keyword FIELD(), VAR() and VAL(). The
ISPP485 Panel ’aaaaaaaa’ error - Invalid VAR()
keywords must be in the following order:
value in ’)PNTS’ section.
FIELD(field-name) VAR(variable-name) VAL(value).
Explanation: The value for the VAR() keyword is
invalid.
ISPP482 Panel ’aaaaaaaa’ error - Invalid
VAL(value) found in the ’)PNTS’ section User Response: There was a programming error
statement. defining the panel that you attempted to display. If you
are running in TEST mode, you can either override the
Explanation: The VAL() keyword contains an invalid
error and attempt to continue running the dialog, or
value.
you can choose not to override the error. If you select
User Response: There was a programming error the latter, the dialog will end and you will be returned
defining the panel that you attempted to display. If you to the initial panel for the application.
are running in TEST mode, you can either override the
Programmer Response: The value for the VAR()
error and attempt to continue running the dialog, or
keyword is incorrect. Ensure that the variable name
you can choose not to override the error. If you select
conforms to ISPF variable naming conventions.
the latter, the dialog will end and you will be returned
to the initial panel for the application.
ISPP486 Panel ’aaaaaaaa’ error - Invalid VAL()
Programmer Response: Correct the value contained in
value in ’)PNTS’ section.
the VAL() keyword for the ’)PNTS’ section statement.
Check for the correct value and the correct spelling. Explanation: The value for the VAL() keyword is
invalid.
ISPP483 Panel ’aaaaaaaa’ error - Invalid FIELD() User Response: There was a programming error
value found in the ’)PNTS’ section defining the panel that you attempted to display. If you
statement. are running in TEST mode, you can either override the
error and attempt to continue running the dialog, or
Explanation: The FIELD() keyword contains an invalid
you can choose not to override the error. If you select
value.
the latter, the dialog will end and you will be returned
User Response: There was a programming error to the initial panel for the application.
defining the panel that you attempted to display. If you
Programmer Response: The value for the VAL()
are running in TEST mode, you can either override the
keyword is incorrect. The value must be a dialog
error and attempt to continue running the dialog, or
variable or a literal.
you can choose not to override the error. If you select
the latter, the dialog will end and you will be returned
to the initial panel for the application. ISPP487 Panel ’aaaaaaaa’ error - Invalid keyword
found in ’)PNTS’ section.
Programmer Response: Correct the value contained in
the FIELD() keyword for the ’)PNTS’ section statement. Explanation: One of the keywords used in the ’)PNTS’
Check for the correct value and the correct spelling. statement is incorrect.
User Response: There was a programming error
defining the panel that you attempted to display. If you
are running in TEST mode, you can either override the
ISPP510 Panel aaaaaaaa error — The DEPTH ISPP513 Panel ’aaaaaaaa’ error - Invalid panel
keyword in a )PNTS section statement is statement syntax. The image-name is not
missing or out-of-order. defined for the IMAGE keyword on a
)PANEL statement or on a )PNTS
Explanation: The DEPTH keyword must be coded statement.
before the TEXT, PLACE, IMAGE, and IMAGEP
keywords and after the FIELD VAR and VAL keywords Explanation: The image-name for the IMAGE
in a )PNTS section statement. keyword on a )PANEL or )PNTS statement was not
specified. An image-name is required.
User Response: There is a programming error
defining the panel that you attempted to display. If you User Response: There was a programming error
are running in TEST mode, you can either override the defining the panel that you attempted to display. If you
are running in TEST mode, you can either override the
| Programmer Response: Correct the invalid value for | User Response: Enter the Julian standard date in the
| the verify PICTCN string. | correct numeric format YYYY.DDD. Valid values for
| YYYY are 0000-9999. Valid values for DDD are 001-365
| or 001-366 if the year is a leap year.
| ISPP525 PICTCN mask-char error - VER
| statement syntax error on PICTCN
| mask-char parameter. The | ISPP528 Verify JSTD error - VER statement
| mask-character parameter cannot be one | failed for Julian standard date (JSTD)
| of the picture string characters | day. The day was outside of the range
| (C,A,N,9,X, or c,a,n,x) | 001-365 or 001-366 for leap years.
| Explanation: The PICTCN mask-character used is | Explanation: The day was not within the range
| invalid. It cannot be one of the following picture string | 001-365 or 001-366 for leap years. Enter a day within
| characters (C,A,N,9,X, or c,a,n,x). | the range and in the format DDD.
| User Response: There was a programming error | User Response: Enter the day within the range and in
| defining the panel that you attempted to display. If you | the format DDD.
| are running in TEST mode, you can either override the
| error and attempt to continue running the dialog, or
| ISPP529 Verify error - VER statement failed for | ISPP532 Verify IDATE error - VER statement
| the national language date delimiter | failed for IDATE. The 2-digit year is not
| character. | within the range 00-99. The date must
| be expressed in a 2-digit year (YY),
| Explanation: The date delimiter character does not
| 2-digit month (MM) and 2-digit day
| match the national language date delimiter character.
| (DD). The year, month and day 2-digit
| For the U.S., the date delimiter character is a slash (/).
| values are separated by a delimiting
| User Response: Enter the correct national language | character.
| date delimiter character.
| Explanation: The year was not within the range 00-99.
| Enter numeric data for the 2-digit year within the range
| ISPP529A Verify error - VER statement failed for | 00-99. The date must be expressed in a 2-digit year
| Julian date or Julian standard date | (YY), 2-digit month (MM) and 2-digit day (DD). The
| delimiter. A period should be used as | year, month and day 2-digit values are separated by a
| the delimiter. For example: Julian date | delimiting character.
| format YY.DDD. Julian standard date
| User Response: Enter the month as a 2-digit month
| format YYYY.DDD.
| within the range 01-12.
| Explanation: The date delimiter character is not a
| period (.). The format for Julian date is: YY.DDD. The
| ISPP533 Verify IDATE error - VER statement
| format for Julian standard date is YYYY.DDD.
| failed for IDATE. The 2-digit day
| User Response: Use the period (.) as the date | entered is not within the 01-31 range for
| delimiter character in the Julian date or Julian standard | the months of January, March, May, July,
| date. | August, October or December, or the
| 2-digit day entered is not within the
| 01-30 range for the months of April,
| ISPP530 Verify IDATE error - VER statement | June, September or November.
| failed for IDATE. The year, day, or
| month is not numeric. The date must be | Explanation: The day entered was not a valid day of
| expressed as a 2-digit year (YY), 2-digit | the month. The 2 digit day must fall within the 01-31
| month (MM) and 2-digit day (DD). The | range for the months of January, March, May, July,
| year, month and day 2-digit values are | August, October, and December, or within the 01-30
| separated by the national language date | range for the months of April, June, September, and
| delimiter character. Valid year values are | November.
| 00-99, valid month values are 01-12, and
| User Response: Enter the day as a 2-digit day within
| valid day values are 01-31.
| the ranges for the appropriate months. Refer to the
| Explanation: The date was not numeric. Enter | explanation section.
| numeric data for the 2-digit year (00-99), the 2-digit
| month (01-12), and the 2-digit day (01-31). The format
ISPP533A Verify IDATE error - VER statement
| for the U.S. is YY/MM/DD.
failed for IDATE. The 2-digit day
| User Response: Enter numeric data for the 2-digit specified exceeds the days in the month
| year (00-99), the 2-digit month (01-12), and the 2-digit of February. February has a range of
| day (01-31). 01-29 in leap years and a range of 01-28
in non-leap years.
| ISPP531 Verify IDATE error - VER statement Explanation: The day specified exceeds the number of
| failed for IDATE. The 2-digit month is days in the month of February. In non-leap years the
| not within the range 01 - 12. The date range is 01-28 and in leap years the range is 01-29.
| must be expressed in a 2-digit year (YY),
User Response: Enter a valid 2-digit day for February.
| 2-digit month (MM) and 2-digit day
In non-leap years the range is 01-28 and in leap years
| (DD). The year, month and day 2-digit
the range is 01-29.
| values are separated by a delimiting
| character.
| ISPP534 Verify JDATE error - VER statement
| Explanation: The month was not within the range
| failed for Julian date (JDATE) day. The
| 01-12. Enter numeric data for the 2-digit month within
| day was outside of the range 001-365 or
| the range 01-12.
| 001-366 for leap years.
| User Response: Enter the month as a 2-digit month
| Explanation: The day was not within the range
| within the range 01-12.
| 001-365 or 001-366 for leap years. Enter a day within
| the range and in the format DDD.
| ISPP546 Verify ITIME error - VER statement | ISPP549A Verify STDTIME error - VER statement
| failed for International time (ITIME). | failed for standard time (STDTIME).
| The hour or minute value is not | The hour, minute, or second value is not
| numeric. Valid values are 00-23 for hour | within the valid range. Valid ranges are
| and 00-59 for minute. | 00-23 for hour and 00-59 for minute and
| second. For the U.S., the format is
| Explanation: The hour or minute specified was not
| HH:MM:SS.
| numeric. The value range for hour is 00-23 and for
| minute is 00-59. | Explanation: The hour, minute, or second specified is
| outside of the valid range. The valid ranges are 00-23
| User Response: Enter valid values for hour in the
| for hour, 00-59 for minute and second.
| range of 00-23 and for minute in the range of 00-59.
| User Response: Enter valid values for hour in the
| range of 00-23 and for minute and second in the range
| ISPP547 Verify ITIME error - VER statement
| of 00-59.
| failed for international time (ITIME).
| The hour or minute entered is outside
| of the valid range. The value range for ISPP600 No window to move - There is no active
| hour is 00-23 and for minute is 00-59. pop-up window to move.
| Explanation: The value entered for hour or minute Explanation: The WINDOW command was entered,
| falls outside of the valid range for hour or minute. The but no pop-up window was displayed in the logical
| value range for hour is 00-23 and for minute is 00-59. screen from which the command was entered.
| User Response: Enter the 4-digit year as numeric. User Response: Use the WINDOW command only
when a pop-up window is displayed.
| ISPP548 Verify STDTIME error - VER statement
| failed for standard time (STDTIME). ISPP601 Cannot move window - Pop-up window
| The national language time delimiter is cannot be moved while pull-down is
| invalid or position 3 and 6 do not displayed.
| contain the national language time
Explanation: The WINDOW command was entered
| delimiter.
while a pull-down menu was displayed. ISPF does not
| Explanation: The national language time delimiter is allow a pop-up window to be repositioned while a
| invalid for the national language or is not in character pull-down menu is displayed.
| position 3 and position 6.
User Response: Close the pull-down window and
| User Response: Enter the correct national language then reposition the window.
| time delimiter in positions 3 and 6. For the U.S. the
| time delimiter is a colon (:).
ISPP602 Invalid command - ″WINDOW MOVE″
is an invalid command in GUI mode.
| ISPP549 Verify STDTIME error - VER statement
Explanation: The WINDOW command was entered
| failed for standard time (STDTIME).
while running in GUI mode. ISPF does not support this
| The hour, minute, or second value is not
command on the workstation.
| numeric. Valid values are 00-23 for hour,
| 00-59 for minute, and 00-59 for second. User Response: Using the mouse, click on the title bar
| For the U.S., the format is HH:MM:SS. of the window and drag the window to a new position.
| Explanation: The hour, minute, or second specified
| was not numeric. Valid values for hour fall in the range ISPP603 Invalid command - ″PRINT″,
| of 00-23. Valid values for minute and second in the ″PRINT-HI″, ″PRINTL″, ″PRINTLHI″,
| range of 00-59. and ″PRINTG″ are invalid commands in
GUI mode.
| User Response: Enter valid values for hour in the
| range of 00-23 and for minute and second in the range Explanation: One of the PRINT commands was
| of 00-59. entered while running in GUI mode. ISPF does not
support these commands on the workstation.
| Explanation: The user has selected the ’Start a new Programmer Response: Either shorten the line in the
| application’ option, but the Application Name input )AREA section, or increase the width of the definition
| field is blank. of the scrollable area in the panel definition.
ISPP612 Panel ’aaaaaaaa’ error - A graphic area ISPP615 Panel ’aaaaaaaa’ error - )AREA section
cannot be defined within an )AREA defined out of order, It must appear
section. after the )BODY section and before the
)INIT, )REINIT, )PROC, or )HELP
Explanation: An attempt was made to define a
sections if coded.
graphic area within a scrollable area. This is not
allowed. Explanation: An attempt was made to define a
scrollable area, but the )AREA section was specified out
User Response: There was a programming error
of order in the panel definition.
defining the panel that you attempted to display. If you
are running in TEST mode, you can either override the User Response: There was a programming error
error and attempt to continue running the dialog, or defining the panel that you attempted to display. If you
you can choose not to override the error. If you select are running in TEST mode, you can either override the
the latter, the dialog will end and you will be returned error and attempt to continue running the dialog, or
to the initial panel for the application. you can choose not to override the error. If you select
the latter, the dialog will end and you will be returned
Programmer Response: A scrollable area cannot have
to the initial panel for the application.
a graphic area defined within it. Move either the
scrollable areas or the graphic area to the )BODY Programmer Response: Move the )AREA section after
section. the )BODY section and before the )INIT, )REINIT,
)PROC, or )HELP sections if they are coded in the
panel definition.
ISPP613 Panel ’aaaaaaaa’ error - An action bar
cannot be defined within an )AREA
section. ISPP617 Panel ’aaaaaaaa’ error - )AREA section is
not defined for an area section defined
Explanation: An attempt was made to define an
in the )BODY or an empty )AREA
action bar within a scrollable area. This is not allowed.
section was defined.
User Response: There was a programming error
Explanation: The )BODY section contains a field with
defining the panel that you attempted to display. If you
an attribute that indicates the field is scrollable, but no
are running in TEST mode, you can either override the
)AREA section exists or it has no lines defined in it.
error and attempt to continue running the dialog, or
you can choose not to override the error. If you select User Response: There was a programming error
the latter, the dialog will end and you will be returned defining the panel that you attempted to display. If you
to the initial panel for the application. are running in TEST mode, you can either override the
error and attempt to continue running the dialog, or
Programmer Response: A scrollable area cannot have
you can choose not to override the error. If you select
an action bar defined within it. Move the action bar to
the latter, the dialog will end and you will be returned
the )BODY section.
to the initial panel for the application.
Programmer Response: You must code an )AREA
ISPP614 Panel ’aaaaaaaa’ error - An area defined
section for the field in the )BODY section that has the
with SCROLL(ON) or EXTEND(ON)
attribute AREA(SCRL). That area must contain at least
cannot be defined within an )AREA
one line.
section.
Explanation: An attempt was made to define an area
ISPP618 Panel ’aaaaaaaa’ error - An )AREA
with SCROLL(ON) or EXTEND(ON) within a scrollable
section is defined without a section
area. This is not allowed.
defined in the panel )BODY section.
User Response: There was a programming error
Explanation: The )BODY section contains a field with
defining the panel that you attempted to display. If you
an attribute that indicates the field is scrollable, but no
are running in TEST mode, you can either override the
)AREA section exists with that field’s name.
error and attempt to continue running the dialog, or
you can choose not to override the error. If you select User Response: There was a programming error
the latter, the dialog will end and you will be returned defining the panel that you attempted to display. If you
to the initial panel for the application. are running in TEST mode, you can either override the
error and attempt to continue running the dialog, or
Programmer Response: A panel with a scrollable area
you can choose not to override the error. If you select
cannot have another area within it that has
the latter, the dialog will end and you will be returned
EXTEND(ON) or SCROLL(ON) specified. Change the
to the initial panel for the application.
EXTEND or SCROLL value to OFF.
Programmer Response: You must code an )AREA
section for the field in the )BODY section that has the
attribute AREA(SCRL).
ISPP628 Panel ’aaaaaaaa’ error - Variable cannot Programmer Response: Either reduce the depth
be used for depth specification. specified on the DEPTH() parameter of the )AREA
section panel statement or change the number of
Explanation: A variable was specified on the DEPTH() non-scrollable area lines defined in the )BODY section.
parameter of the )AREA section panel statement. This
is not allowed.
ISPP651 The cursor must be within a scrollable
User Response: There was a programming error area to perform the requested scroll.
defining the panel that you attempted to display. If you
are running in TEST mode, you can either override the Explanation: The cursor was not in a scrollable area
error and attempt to continue running the dialog, or when a command to scroll the screen was received.
you can choose not to override the error. If you select User Response: Place the cursor in the scrollable area
the latter, the dialog will end and you will be returned you wish to scroll before pressing the scroll function
to the initial panel for the application. key.
Programmer Response: You must code a number for
the depth of the scrollable area. This number specifies ISPP652 End of data - There is no additional
the minimum number of lines in the scrollable area (not information below this line.
including the scroll indicator). It must be greater than
or equal to the number of lines defined for the area in Explanation: This is an informational message. You
the )BODY section and less than or equal to the have scrolled to the end of the scrollable information.
number of lines in the )AREA section.
ISPP653 Top of data - There is no additional
ISPP629 Panel ’aaaaaaaa’ error - EXTEND(OFF) information above this line.
scrollable area must be a depth of at Explanation: This is an informational message. You
least 2 lines in the )BODY section have scrolled to the beginning of the scrollable
definition. information.
Explanation: When EXTEND(OFF) is specified for a
scrollable area, the scrollable area defined in the )BODY
section must have at least 2 lines. The scroll indicator
takes one line and you must have at least one line of
data to scroll.
ISPP654 The scrollable area must be visible to | ISPP659 Any application name and parameters
perform the requested scroll. | that are valid for the ISPF START
| command are valid in this field. If
Explanation: There is a scrollable area defined on the
| additional space is needed, press the
panel, but it does not fit on the display.
| Expand PF key while the cursor is in
User Response: There was a programming error | this field and a popup window will be
defining the panel that you attempted to display. You | displayed containing a longer input
might be able to make the scrollable area visible by | field.
using a display device with more lines per screen.
| Explanation: This message is field level help text for
Programmer Response: Too many lines have been | the Application Name input field.
defined outside the scrollable area so that the scrollable
area does not appear on the panel. Reduce the number
ISPP900 Panel ’aaaaaaaa’ error - Invalid
of non-scrollable lines in the )BODY section or move
ADDSOSI value (not a dialog variable).
some of them to the scrollable area.
Explanation: Only a dialog variable may be specified
in the ADDSOSI built-in function.
ISPP655 End of data - There is no additional
information below this line. Press Enter User Response: There was a programming error
or RIGHT again to display the next defining the panel that you attempted to display. If you
panel, if one has been defined. are running in TEST mode, you can either override the
error and attempt to continue running the dialog, or
Explanation: This is an informational message. You
you can choose not to override the error. If you select
have scrolled to the end of the scrollable information.
the latter, the dialog will end and you will be returned
to the initial panel for the application.
ISPP656 Top of data - There is no additional
Programmer Response: Specify a dialog variable for
information above this line. Press LEFT
the parameter to the ADDSOSI built-in function.
again to display the previous panel, if
one has been defined.
ISPP901 Panel ’aaaaaaaa’ error - Invalid DELSOSI
Explanation: This is an informational message. You
value (not a literal or dialog variable).
have scrolled to the beginning of the scrollable
information. Explanation: Something other than a literal or a dialog
variable was specified as a parameter on the DELSOSI
built-in function; for example, omitting the parameter
ISPP657 Panel ’aaaaaaaa’ error - A graphic area
to the function.
cannot be defined within a group box.
User Response: There was a programming error
Explanation: This is an informational message.
defining the panel that you attempted to display. If you
Graphic areas are not supported within group boxes.
are running in TEST mode, you can either override the
Programmer Response: There are three options: error and attempt to continue running the dialog, or
remove the group box definition from the panel, you can choose not to override the error. If you select
remove the graphic area from the group box, code the the latter, the dialog will end and you will be returned
graphic area outside of the group box. to the initial panel for the application.
Programmer Response: Specify only a literal or a
ISPP658 Invalid screen name - A screen name dialog variable on the DELSOSI built-in function.
must be more than one character, and all
alphanumerics, and cannot be LIST,
ISPP902 Panel ’aaaaaaaa’ error - Invalid
PREV or NEXT.
ONEBYTE value (not a dialog variable).
Explanation: The screen name entered was invalid.
Explanation: Something other than a literal or a dialog
User Response: Specify a valid screen name. variable was specified as a parameter on the ONEBYTE
built-in function; for example, omitting the parameter
to the function.
User Response: There was a programming error
defining the panel that you attempted to display. If you
are running in TEST mode, you can either override the
error and attempt to continue running the dialog, or
you can choose not to override the error. If you select
the latter, the dialog will end and you will be returned
to the initial panel for the application.
ISPR016 STOW service error - An unexpected ISPR022 Panel not processed - Panel ’aaaaaaaa’
error was received from the STOW already exists in output data set.
service (RC=aaaaaaaa).
Explanation: The output panel aaaaaaaa already exists
Explanation: This message is self-explanatory. in the output data set, and member replace was not
specified.
User Response: If the error continues, contact your
system programmer. User Response: Specify member replace, or choose a
different output panel name.
System Programmer Response: If you do not have
mixed levels of ISPF code, contact IBM support.
ISPR023 Conversion of aaaaaaaa panels in
progress.
ISPR017 I/O error on output - An unexpected
error was received from the put service Explanation: This is an informational message. This is
(RC=aaaaaaaa). a status message issued at the start of an ISPPREP
processing cycle.
Explanation: This message is self-explanatory.
User Response: If the error continues, contact your
ISPR024 Utility - ISPPREP - Data set ″aaaaaaaa″
system programmer.
contains no members.
System Programmer Response: If you do not have
Explanation: The data set aaaaaaaa(44) specified as the
mixed levels of ISPF code, contact IBM support.
input to ISPPREP has no members.
User Response: Verify the data set name.
ISPR018 Output service error - An unexpected
error was received from the output
service (RC=aaaaaaaa). ISPR025 No members in data set - Data set
″aaaaaaaa″ contains no members.
Explanation: This message is self-explanatory.
Explanation: The data set aaaaaaaa(44) specified as the
User Response: If the error continues, contact your
input to ISPPREP has no members.
system programmer.
User Response: Verify the data set name.
System Programmer Response: If you do not have
mixed levels of ISPF code, contact IBM support.
ISPR026 Utility - ISPPREP - Panel ’aaaaaaaa’ was
not found in the PDS directory.
ISPR019 Enter new member name - Member
must be renamed when From and To Explanation: ISPPREP could not find member aaaaaaaa
data sets are the same. in the input data set directory.
Explanation: ISPPREP does not allow the output
member name to be the same as the input member ISPR027 Member not found - Panel ’aaaaaaaa’ was
name when the output data set name is the same as the not found in the PDS directory.
input data set name.
Explanation: ISPPREP could not find member aaaaaaaa
User Response: Specify a different member name for in the input data set directory.
the output member.
ISPR028 Invalid output LRECL - ISPPREP output
ISPR020 Conversion of aaaaaaaa panels in data set has an invalid LRECL, valid
progress - bbbbbbbb panels processed. LRECL is between 80 160 for FB and 84
and 164 for VB.
Explanation: This is an informational message. This is
a status message issued every 50 panels when more Explanation: The record length of the output data set
than 50 panels are processed in a single ISPPREP cycle. is not supported by ISPF.
User Response: Use an output data set with a record
ISPR021 Utility - ISPPREP - Panel ’aaaaaaaa’ length between 80 and 160 for fixed blocked data sets,
already exists in output data set. and 84 and 164 for variable blocked data sets.
Explanation: The output panel aaaaaaaa already exists
in the output data set, and member replace was not
specified.
User Response: Specify member replace, or choose a
different output panel name.
ISPR030 Utility - preprocess - Panel ’aaaaaaaa’ has ISPR039 to data set aaaaaaaa, newname = bbbbbbbb
been successfully converted.
Explanation: This is an informational message. This is
Explanation: This is an informational message. a part of the ISPF log messages written at the end of
the ISPPREP conversion cycle. This message is issued
in place of message ISPR038 when a single member is
ISPR031 Panel aaaaaaaa converted - Panel
converted and the output member name is different
’aaaaaaaa’ has been successfully
from the input member name.
converted.
Explanation: This is an informational message.
ISPR040 Input parameter error - Required
keyword parameter INPAN is missing.
ISPR032 Utility - preprocess - aaaaaaaa panels
Explanation: This message is self-explanatory.
have been successfully converted.
User Response: Provide the INPAN keyword and
Explanation: This is an informational message.
input data set name.
ISPR037 From data set aaaaaaaa ISPR044 Input parameter error - Output member
name is invalid when entire input
Explanation: This is an informational message. This is
library selected.
a part of the ISPF log messages written at the end of
the ISPPREP conversion cycle. Explanation: This message is self-explanatory.
User Response: Remove the output member name.
ISPR038 to data set aaaaaaaa
Explanation: This is an informational message. This is ISPR045 Input parameter error - Required
a part of the ISPF log messages written at the end of keyword parameter OUTPAN is
the ISPPREP conversion cycle. This message is issued missing.
when either all members of the input data set have
Explanation: This message is self-explanatory.
been converted, or a single member is converted and
the output member name is the same as the input User Response: Provide the OUTPAN keyword and
member name. the output data set name.
| Problem Determination: Ensure that the TSO profile Explanation: This is an informational message.
| is set to WTPMSG and MSGID so that the system
| abend messages are seen for this error. Additional ISPS004 Trace - TGET - - Tldaaaaaaaa
| information can then be obtained from system length=bbbbbbbb option=cccccccc
| documentation.
Explanation: This is an informational message.
ISPS009 Tutorial test line - aaaaaaaa Cur panel = Explanation: This is an informational message. ISPF
bbbbbbbb Prev panel = cccccccc Last msg = error recovery is not available until you have processed
dddddddd an Enter on a primary option menu.
System Programmer Response: Ensure that the user’s User Response: Contact the responsible programmer.
region size satisfies the ISPF minimum storage Programmer Response: Determine why the dialog
requirement. fails. You may code a primary option menu to enable
ISPF error recovery.
ISPS012 User action for ISPS011 - ** Logon with
larger SIZE parameter ** ISPS018 Invalid ZISPFRC value (’aaaaaaaa’),
Explanation: This is an informational message. non-numeric character found.
Explanation: The value in ZISPFRC must contain a
ISPS013 Attach of PMD failed - ** Logical screen numeric value.
request failed - ATTACH RC= aaaaaaaa User Response: Contact the responsible programmer.
**
Programmer Response: Ensure that your dialog
Explanation: The task could not be processed. returns a numeric value to ZISPFRC.
User Response: Contact your system programmer.
Programmer Response: The ATTACH macro failed, ISPS019 Invalid ZISPFRC value (’aaaaaaaa’), out
contact IBM support. of allowable range.
Explanation: The value returned to ZISPFRC exceeds
ISPS014 Immediate PMD termination after 16777215.
ATTACH - ** Logical screen request User Response: Contact the responsible programmer.
failed - abend aaaaaaaa **
Programmer Response: Correct the value returned to
Explanation: The task could not be processed. ZISPFRC.
User Response: Contact your system programmer.
System Programmer Response: If the abend code is ISPS100 Invalid service name - ’aaaaaaaa’ exceeds
an ISPF user abend code, assume that the failure is the allowable length of 8.
caused by the user environment. If the abend is a Explanation: The user invoked an ISPF service and
system abend, take a subtask dump to determine the the service name’s length exceeded the 8-character
reason for the abend. limit.
User Response: Contact the responsible programmer.
Programmer Response: Correct the ISPF service name.
ISPS112 Var substitution error - Severe error ISPS117 Invalid service request - The ’aaaaaaaa’
while resolving symbolic variables in service is not allowed via the ISPEXEC
ISPEXEC statement. interface.
Explanation: A variable on the ISPEXEC statement Explanation: Several services are not available when
could not be resolved. you use the ISPEXEC interface, but are available when
you use the ISPLINK interface. The service given in the
User Response: Contact the responsible programmer.
message is one that is not allowed with the ISPEXEC
Programmer Response: Correct the ISPEXEC interface.
statement in the dialog.
User Response: Contact the responsible programmer.
Programmer Response: Correct the dialog to use only
ISPS113 Invalid name list - A name list must
valid ISPF services via the ISPEXEC interface.
begin with a left parenthesis.
Explanation: An ISPF service’s name-list parameter is
ISPS119 INVALID SERVICE - ’aaaaaaaa’ service
missing a left parenthesis. If the ISPF service’s name-list
not supported in the batch environment.
parameter consists of more than one name, it must be
enclosed in parentheses. Explanation: The service listed in the message is not
supported in the batch environment.
User Response: Contact the responsible programmer.
User Response: Contact the responsible programmer.
Programmer Response: Correct the ISPEXEC
statement in error. Programmer Response: Correct the erroneous
ISPEXEC statement.
ISPS114 Conflicting keywords - Keyword
’aaaaaaaa’ conflicts with a previously ISPS190 No ADDPOP specified - The FRAME or
specified keyword. BKGRND keyword was specified before
an ADDPOP keyword was found on a
Explanation: The ISPF service could not execute
SELECT statement.
because of an error in the keyword coding.
Explanation: You must code an ADDPOP keyword
User Response: Contact the responsible programmer.
before specifying FRAME or BKGRND.
Programmer Response: Correct the ISPEXEC
Programmer Response: Correct the SELECT service
statement in error.
parameters.
User Response: Contact the responsible programmer. Explanation: The FRAME keyword only accepts the
following values: FRAME(STD), FRAME(FIX),
Programmer Response: Correct the ISPEXEC FRAME(DLG).
statement in error.
Programmer Response: Correct the SELECT service
parameters.
ISPS116 PDF services unavailable - Insufficient
storage to load the PDF component of
ISPF. ISPS192 Invalid background - An invalid
BKGRND value was specified on a
Explanation: An error occurred attempting to load the SELECT service. The only valid values
PDF component of ISPF. The error indicates insufficient are STD or DLG.
storage for the PDF component.
Explanation: The BKGRND keyword only accepts the
User Response: Contact the system programmer. following values: BKGRND(STD) or BKGRND(DLG).
System Programmer Response: Verify that the user’s Programmer Response: Correct the SELECT service
region size meets the minimum requirements for ISPF. parameters.
If the problem continues, contact IBM support.
ISPT003 Internal table error - Row data area not ISPT008 GETMAIN error - aaaaaaaa received
large enough to contain the updated return code bbbbbbbb from GETMAIN.
row.
Explanation: The GETMAIN macro failed.
Explanation: The RDA control block is not large
User Response: Contact your system programmer.
enough for the row being modified.
System Programmer Response: Refer to the
User Response: Contact the responsible programmer.
appropriate system documentation on the GETMAIN
System Programmer Response: Try restoring the table macro for the return code information.
from a backup and retry the application. If the problem
still persists, contact IBM support.
ISPT009 FREEMAIN error - aaaaaaaa received
return code bbbbbbbb from FREEMAIN.
ISPT004 Internal table error - aaaaaaaa detected
Explanation: The FREEMAIN macro failed.
error during SAWA construction.
User Response: Contact your system programmer.
Explanation: An error was encountered building an
internal table control block. System Programmer Response: Refer to the
appropriate system documentation on the FREEMAIN
User Response: Contact the responsible programmer.
macro for the return code information.
System Programmer Response: Try restoring the table
from a backup and retry the application. If the problem
ISPT010 Internal table error - aaaaaaaa detected an
still persists, contact IBM support.
invalid name list work area.
Explanation: An error was encountered building an
ISPT005 Internal table error - aaaaaaaa detected an
internal table control block.
invalid name value work area.
User Response: Contact your system programmer.
Explanation: An error was encountered with an
internal table control block. System Programmer Response: Try restoring the table
from a backup and then retry the application. If the
User Response: Contact the responsible programmer.
problem persists, contact IBM support.
System Programmer Response: Try restoring the table
from a backup and retry the application. If the problem
ISPT011 DEQUEUE error - aaaaaaaa received
still persists, contact IBM support.
return code bbbbbbbb from DEQUEUE.
Explanation: An error occurred on the DEQUEUE
ISPT006 Variable services error - aaaaaaaa
macro.
received return code bbbbbbbb from
ISPDVCGT. User Response: Contact your system programmer.
Explanation: An error occurred while trying to System Programmer Response: Refer to the
retrieve variable for a table row. appropriate system documentation on the DEQUEUE
macro for the return code information.
User Response: Contact your system programmer.
System Programmer Response: This error should not
ISPT012 ENQUEUE error - aaaaaaaa received
occur. It could be caused by a storage overlay situation.
return code bbbbbbbb from ENQUEUE.
Contact IBM support.
Explanation: An error occurred on the ENQUEUE
macro.
ISPT007 Router service error - aaaaaaaa is
unknown table service. User Response: Contact your system programmer.
Explanation: An invalid internal table service request System Programmer Response: Refer to the
was issued. appropriate system documentation on the ENQUEUE
macro for the return code information.
User Response: Contact your system programmer.
System Programmer Response: ISPF issued an invalid
ISPT013 Internal table error - aaaaaaaa received
table service request through an internal interface. This
return code bbbbbbbb from TFD build.
should never occur. Obtain a dump at the time of the
error and contact IBM support. Explanation: An error occurred while trying to build
an internal control block.
User Response: Contact your system programmer.
ISPT202 Invalid number of rows - The number ISPT207 Invalid year offset - The year offset
of rows must be a positive number less must be a value from 1 to 7.
than 32768
Explanation: The year sort only accepts a variable
Explanation: The number of rows specified in the value with a maximum value of 8 characters where
MULT parameter of the TBADD service is greater than part of the value is a 2 digit year. Hence the offset to
or equal to 32 768. the beginning of the year can only be a value from 1 to
7.
Programmer Response: Specify a number for the
MULT parameter that is less than 32 768. Programmer Response: Specify a valid offset for the
year parameter.
ISPT203 Table row too long - aaaaaaaa was
requested for a row bbbbbbbb bytes long. ISPU330 Invalid command table - The command
Maximum length is 65536. table has keys, and therefore cannot be
processed.
Explanation: The requested table service request
would cause the table row to exceed 65 536 bytes. Explanation: The command table being read by the
Command Table utility has variables defined as keys.
Programmer Response: Decrease the size of the table
row. System Programmer Response: Check the ISPTLIB
concatenation for the table being read. The table name
Problem Determination: The length of a table row can
is xxxxCMDS, where xxxx is the application ID entered
be computed as follows:
by the user.
Row size = 22 + 4a + b + 9c
ISPF command tables should not have keys. This
where: condition could occur if users created their own
a Total number of variables in the row, including command tables with the TBCREATE service. The
extensions Display Status selection of Tables under Dialog Test can
b Total length of variable data in the row be used to get status information on the table, which
c Total number of extension variables in the row may be helpful in determining how the invalid table
was created.
ISPU336 Verb too short - Command table verbs ISPU341 Table in use - The command table
must be at least two characters long. specified is already open and cannot be
opened again.
Explanation: The command verb must be from 2 to 8
characters long, and must begin with an alphabetic Explanation: You have specified a command table that
character. has already been specified for the Command Table
Utility, and you have not exited from the utility yet.
User Response: Enter a valid name for the verb.
You may have specified the command table from
another screen, or you may have hidden the utility
ISPU337 Illegal verb - Command table verbs from view by going to another function using the
must begin with an alphabetic character. action bars.
Explanation: The command verb must be from 2 to 8 User Response: Close the other invocation of the
characters long, and must begin with an alphabetic Command Table Utility for that command table.
character.
User Response: Enter a valid name for the verb. ISPU342 Invalid line command - V is the only
valid line command.
ISPU338 Illegal T or Trunc value - Command Explanation: An invalid line command was entered.
table truncation values must be within D, I, E, and R are only valid on a table that can be
the length of the verb. updated.
Explanation: A truncation value was specified that is User Response: Either correct the invalid line
greater than the length of the command verb. command, or blank it out.
ISPV013 Variable exit error - Exit routine at ISPV017 Invalid format - Invalid VDEFINE
aaaaaaaa gave error code bbbbbbbb for format ’aaaaaaaa’ found for variable
cccccccc of dddddddd. ’bbbbbbbb’.
Explanation: A variable service exit encountered an Explanation: The format parameter supplied on the
unexpected return code. VDEFINE service was not a valid value.
User Response: Contact your system programmer. User Response: Contact the responsible programmer.
ISPV024 Invalid SET request - CLIST variable Explanation: ISPF called IKJCT441 to process a
’aaaaaaaa’ is a system variable. Not CLIST/REXX variable and got a return code of 40. This
modifiable. normally means that there was an invalid environment.
Explanation: ISPF was used to attempt to modify a User Response: Contact your system programmer.
TSO system variable.
System Programmer Response: The probable cause of
User Response: Contact the responsible programmer. this error is that a command was invoked with the
SELECT service and the command was in the ISPTCM
Programmer Response: Do not use ISPF services to table with a flag byte X'02' instead of X'42'. Any
modify TSO system variables. command processor that is in the ISPTCM table that
uses ISPF services should have the function pool flag
set.
ISPV029 IKJCT441 interface error - Severe error ISPV044 Invalid format data - Data contains
accessing CLIST variables. Return code invalid hex character for packed format
= ’aaaaaaaa’.
Explanation: The data for a format of PACK must be a
Explanation: A severe error occurred while processing numeric value (0-9).
CLIST variables. Refer to the appropriate TSO
Programmer Response: Ensure that valid numeric
documentation for an explanation of the IKJCT441 error
data is supplied for a variable with a format of PACK.
code.
System Programmer Response: Contact IBM support,
ISPV045 Invalid data length - Length of
if necessary.
″aaaaaaaa″ is bbbbbbbb - valid lengths are
4 and 8.
ISPV040 Invalid PACK(N) - N value of PACK(N)
Explanation: A variable with a format of FLOAT must
must be between 0 and 18.
have a length of either 4 or 8 bytes.
Explanation: The value of N must be greater than or
Programmer Response: Make sure that the length
equal to 0 and less than or equal to 18.
supplied on the VDEFINE service has a value of either
Programmer Response: Ensure a valid value is 4 or 8 when the format value is FLOAT.
specified with the PACK keyword.
ISPV046 Invalid data length - Length of
ISPV041 Incompatible pack length - PACK(N) ″aaaaaaaa″ is bbbbbbbb - valid lengths are
format specified requires a length 1 to 10.
greater than was specified.
Explanation: A variable with a format of PACK must
Explanation: The length specified on the VDEFINE have a length from 1 to 10 bytes.
service was not large enough to to contain the number
Programmer Response: Make sure that the length
of digits to the right of the decimal point as specified
supplied on the VDEFINE service has a value from 1 to
by the N value.
10 when the format value is PACK.
Programmer Response: Ensure that the length
specified with the VDEFINE service is large enough to
ISPV047 Invalid data length - Length of
contain the packed number. The value of N cannot be
″aaaaaaaa″ is bbbbbbbb - valid lengths are
greater than twice the length minus one.
2 to 32767.
Explanation: A variable with a format of BINSTR
ISPV042 Invalid VDEFINE syntax - A format of
must have a length greater than 1 and less than 32 768.
″*″ must have an ″*″ in the
corresponding name position in the Programmer Response: Ensure that the length
VDEFINE parameters. specifed on the VDEFINE for a variable with a format
of BINSTR is greater than 1 and less than 32 768.
Explanation: Using the LIST option, an ″*″ (asterisk)
was found in the format field array and the
corresponding entry in the variable name array was not ISPV048 Invalid data string - Variable ″aaaaaaaa″
an ″*″ (asterisk) also. must contain a null terminator.
Programmer Response: Make sure that the format Explanation: The last byte of a variable that has a
field array and name list array are paired properly. format of BINSTR must be a null terminator ( X'00').
Programmer Response: Ensure that the length
ISPV043 Invalid VDEFINE syntax - An ″*″ format supplied on the VDEFINE service for a BINSTR format
must be specified with at least one other variable allows for a null terminator (binary zero) to be
valid format and the list option placed in the last position of the variable value. ISPF
specified. will store up to ″length - 1″ of significant data and then
place a null terminator in the last position.
Explanation: A value of ″*″ (asterisk) is only valid
with the LIST option. Also, there must be at least one
valid format other than ″*″ (asterisk) in the format ISPV050 Invalid mask format - Format ″aaaaaaaa″
array. is not a valid mask format.
Programmer Response: Do not code all values in the Explanation: An invalid mask format was specified on
format array as ″*″ (asterisk). the VMASK service.
User Response: Contact the responsible programmer.
ISPV052 Invalid variable mask - The specified ISPV057 Invalid user mask - A mask should
mask contains invalid format characters. contain at least one of the following
characters: A, 9, H, N, or X.
Explanation: An invalid mask symbol was used in the
mask parameter of the VMASK service with a USER Explanation: The specified mask must contain at least
type of mask. one of the symbols A, 9, H, N, or X.
User Response: Contact the responsible programmer. User Response: Contact the responsible programmer.
Programmer Response: Correct the mask so it Programmer Response: Correct the code so it supplies
contains valid mask symbols as described by the a valid user mask.
VMASK service in ISPF Services Guide
ISPV058 Variable not VDEFINEd - The specified
ISPV053 Invalid variable data - The specified variable has not been VDEFINEd.
variable contains invalid data for the
Explanation: A VDEFINE has not been issued for the
specified variable mask.
variable associated with the VMASK.
Explanation: The variable value had data that did not
User Response: Contact the responsible programmer.
match the mask pattern. For example, if the mask
pattern was AAA and numeric data was supplied, this Programmer Response: Ensure that a VDEFINE is
error would occur. done for any variable that has a VMASK associated
with it.
User Response: Correct the variable value to fit the
mask pattern.
ISPV059 Invalid variable mask - ″B″ can only be
imbedded. Blanks cannot begin or end a
ISPV054 Invalid variable length - The specified
variable mask.
variable value is an invalid length.
Explanation: A VMASK was issued with a B at the
Explanation: The length of the variable value does not
beginning or end of the mask pattern.
match the length of the mask pattern.
User Response: Contact the responsible programmer.
User Response: Correct the variable value to match
the mask pattern. Programmer Response: Correct the code so it does not
specify a mask pattern with a B in the first or last
position of the mask.
ISPV055 Variable not masked - The specified
variable in the VEDIT is not a masked
variable. ISPWS000 Invalid CODEPAGE and CHARSET
values were specified on the WSCON
Explanation: A VEDIT was specified for a variable
service. Both parameters must be
that did not have a VMASK associated with it.
specified in order to be used.
User Response: Contact the responsible programmer.
Explanation: Invalid CODEPAGE and CHARSET
Programmer Response: Make sure that any variable values were specified on the WSCON service. Both
that has a VEDIT defined also has a VMASK associated parameters must be specified in order to be used.
with it.
User Response: If PANEL(YES) or
PANEL(ONERROR) is specified, then the user should
ISPWS004 The variable specified in the WSCON ISPWS008 An invalid value has been specified for
IP or LU parameter cannot be found or the aaaaaaaa parameter on the WSCON
has a blank value. A value is required service.
in order to make a connection to the
Explanation: A value other than STD, FIX, or DLG
workstation.
was specified for the FRAME parameter or a value
Explanation: The variable specified in the WSCON IP other than STD or DLG was specified for the BKGRND
or LU parameter cannot be found or has a blank value. parameter on the WSCON service.
A value is required in order to make a connection to
User Response: If PANEL(YES) or
the workstation.
PANEL(ONERROR) is specified, then the user should
User Response: If PANEL(YES) or select the appropriate GUI Window frame value or the
PANEL(ONERROR) is specified, then the user should Default Window Background color if the defaults from
enter the workstation address in the appropriate panel the system profile are not the preferred values.
field.
Programmer Response: Correct the value specified for
ISPW001 ADDPOP service error - ADDPOP ISPW009 Internal error - Service request to
service issued before first panel display. module ISPWIN specified invalid name.
Explanation: At least one panel must have been Explanation: This is an internal service call and
displayed before an ADDPOP can be issued. should not fail.
Programmer Response: ISPF normally displays panel User Response: Contact your system programmer.
ISPBLANK as a dummy panel prior to an ADDPOP if
System Programmer Response: Contact IBM support.
no previous panel exists. Make sure that this panel is in
the ISPPLIB concatenation sequence to ensure that
ADDPOP will work if the first panel to be displayed by ISPX001 Internal error - Service request to
ISPF is in a pop-up window. module ISPXFR specified invalid name.
Explanation: This is an internal service call and
ISPW002 ADDPOP service error - Consecutive should not fail.
ADDPOP services without a panel
display. User Response: Contact your system programmer.
Explanation: Two consecutive ADDPOP services have System Programmer Response: Contact IBM support.
been issued without an intervening display.
Programmer Response: Make sure that a panel ISPX002 Transfer completed — Transfer of host
display is done in between ADDPOP requests. data set to workstation completed
successfully.
Programmer Response: Ensure that all POPUP and Explanation: You must specify a ″HOST″ and a ″WS″
REMPOP services are paired properly. Use dialog test variable name for the FILEXFER service. The variable
to trace the ADDPOP and REMPOP services. must be defined and the value in the variable must not
be longer than 255 characters.
Problem Determination: Use dialog test to trace the
ADDPOP and REMPOP services. Programmer Response: Correct the specification of the
″HOST″ or ″WS″ variable on the FILEXFER service.
ISPX020 LMMSTATS failed – The file was Explanation: The file transfer service could not
successfully transferred, but ISPF was complete the file transfer to the host. The receiving host
unable to create the statistics for the file is in use or is open.
file.
User Response: Wait for the host file to be available.
Explanation: There is not sufficient directory space to
Programmer Response: The host file is enqueued.
create statistics.
Wait for the host file to be available and then try the
User Response: Re-allocate the data set with filexfer service.
additional directory blocks.
Problem Determination: Check to see who has data
set/member enqueued.
ISPX021 Transfer failed – An error occurred
while closing the workstation file. The
ISPX100 FILESTAT failed - The FILESTAT
file was not transferred.
service failed because there is no
Explanation: The file transfer failed. ISPF was not able connection to the workstation.
to close the workstation file. The file may be locked by
Explanation: You must be connected to a workstation
another process.
before the file FILESTAT service will function.
User Response: Make sure that no other processes are
User Response: Connect to a workstation from the
currently using the file you are attempting to transfer.
ISPF Settings panel GUI pull-down or by specifying the
GUI parameter on the ISPSTART command.
ISPX022 Transfer rejected – The user refused file
access when accepting the workstation
ISPX101 FILESTAT error - The ″file″ variable was
connection.
not specified properly in the FILESTAT
Explanation: When the user is presented with choice service.
to accept or reject a workstation connection, he or she
Explanation: You must specify a ″file″ variable name
is allowed to grant access to files or not. In this case,
for the FILESTAT service. The value in the variable
the user accepted the connection, but refused file
must not be longer than 255 characters.
access.
Programmer Response: Correct the specification of the
User Response: End the ISPF session and start it again
″file″ variable on the FILESTAT service.
granting file access.
Explanation: The user entered an invalid parameter Explanation: When NEWAPPL is selected, the
on the DTEST command. The valid parameters are a PASSLIB field must have an entry.
number 1 through 8 corresponding to the Dialog Test Programmer Response: Enter YES or NO in the field
options. that contains the cursor.
User Response: The user should specify a valid
parameter. ISPYF015 Enter one name only - More than one
name was entered for a panel,
ISPYB039 Switch to Test failed - ISPF was not able command, program, or request.
to switch from the user’s environment to Explanation: This panel allows execution of a panel, a
the Dialog Test environment. command, program, or a request. Only one name can
Explanation: When running the DTEST command, be entered for processing.
ISPF needs to switch from the user’s environment to Programmer Response: Enter only one panel,
the Dialog Test environment. This switch failed and command, program name, or request for processing.
ISPYF016 Language invalid - Language must be ISPYL014 I/O error - An I/O error was encountered
APL, CREX, or blank. reading the first record requested.
Explanation: When entering a command for Explanation: There was an error reading the log data
processing, set the LANG field to APL, CREX, or blank. set.
Programmer Response: Correct the LANG field. User Response: If the error continues, contact the
system programmer.
ISPYF018 MODE invalid - MODE must be either System Programmer Response: This may be a DASD
LINE, FSCR, or blank. problem. Attempt to delete the log data set and then
try to recreate the log entry. If the error continues,
Explanation: Enter LINE for line mode, FSCR for full
contact IBM support.
screen mode, or blank.
Programmer Response: Correct the entry for the
ISPYL015 Insufficient storage - Not enough
MODE field.
storage is available for browse to
proceed.
ISPYF019 Conflicting values - Selecting PASSLIB
Explanation: There was an error while attempting to
is valid only when NEWAPPL is also
browse the log data set.
specified.
User Response: Terminate ISPF and allocate more
Explanation: This message is self-explanatory.
region storage before running ISPF again. If the error
Programmer Response: Enter the correct value for the still occurs, contact the system programmer.
PASSLIB and NEWAPPL fields.
System Programmer Response: If the region size
satisfies the ISPF requirements, contact IBM support.
ISPYL011 ISPYLI failed - ISPYXEM returned
rc(aaaaaaaa) request(entry failed).
ISPYL016 Invalid browse panel - Panel ISPYLP1 is
Explanation: There was an error on an internal ISPF invalid. Contact the system programmer.
call.
Explanation: The ISPYLP1 panel being referenced
User Response: Contact your system programmer. cannot be used by the BROWSE service. Contact your
system programmer.
System Programmer Response: If you do not have
mixed levels of ISPF code, contact IBM support. System Programmer Response: Correct the problem
with ISPYLP1. If you cannot determine the error in the
panel, contact IBM support.
ISPYL012 ISPYLI failed - ISPYLS returned
rc(aaaaaaaa), more details precede this
message in the log. ISPYL017 Recursion error - Recursive use of ISPF
functions (in this case browse) is not
Explanation: There was a failure in the browse log allowed.
routine.
Explanation: BROWSE is already active, you cannot
User Response: Contact your system programmer. activate BROWSE again.
System Programmer Response: If you have User Response: End one of the BROWSE sessions.
preallocated your log data set, verify that it is allocated
correctly. A preallocated log data set with a disposition
of new or old cannot be browsed. If the disposition is ISPYL018 Browse severe error - Severe error
correct, this error could be caused by mixed levels of occurred in module ISRCBR.
ISPF code. If you do not have mixed levels of ISPF
Explanation: Browse has returned an RC=20. Contact
code, contact IBM support.
your system programmer.
System Programmer Response: If BROWSE functions
ISPYL013 Log data set empty - Log data is empty.
correctly using the BROWSE option, contact IBM
Browse cannot be performed.
support.
Explanation: This is an informational message. There
are no entries in the log.
ISPYP011 Parameter missing - Either panel name
or message must be entered.
Explanation: This panel requires either a panel name
or message ID.
ISPYR013 Invalid active status - Active status type ISPYR024 ISPYRFI failed - aaaaaaaa returned rc
not recognized, specify YES or NO. (bbbbbbbb) request (cccccccc failed during
initialize table).
Explanation: The Active field must be YES or NO.
Explanation: The trace function did not initialize.
Programmer Response: Correct the Active field status
to YES or NO. Programmer Response: If the problem continues,
contact the system programmer.
ISPYR044 Invalid variable name - A variable name ISPYS012 Service rc = aaaaaaaa - The specified
must not be longer than 8 characters. dialog service completed with a return
code of aaaaaaaa.
Explanation: The variable name exceeds 8 characters.
Explanation: This is an informational message.
Programmer Response: Correct the variable name.
ISPYS011 Enter dialog service - The desired dialog Programmer Response: Use Dialog Test option 6 and
service and its parameters must be the TBOPEN service to open the table.
entered.
Explanation: You must enter an ISPF service and any ISPYT011 Table not found - The specified table
required parameters. could not be found.
Programmer Response: Enter an ISPF service and any Explanation: The table could not be found in the
required parameters. ISPTLIB allocations.
User Response: Contact the responsible programmer.
Programmer Response: Correct the allocations to
ISPTLIB, or create the table.
ISPYT012 Invalid command - ’aaaaaaaa’ is not a ISPYT019 Invalid option - Your selection is not
valid command for this table operation. valid.
Explanation: The command entered is invalid for this Explanation: You must enter one of the numeric
panel. options that is listed.
User Response: Contact the responsible programmer. Programmer Response: Enter one of the numeric
options that is listed.
Programmer Response: Enter a valid command, such
as LOCATE.
ISPYT020 Name too long - Variable names are
eight characters maximum.
ISPYT013 ’aaaaaaaa’ not found - The key or name
’bbbbbbbb’ was not found in the table. Explanation: The variable name is too long.
Explanation: This is an informational message. Programmer Response: Correct the variable name.
ISPYT014 ’aaaaaaaa’ was found - The key or name ISPYT021 Row not added - Blank row was not
’bbbbbbbb’ was found in the table. added, operation was cancelled.
Explanation: This is an informational message. Explanation: This is an informational message. The
operation was cancelled; the blank row was not added.
ISPYT015 Table in use - The specified table is in
use by another user, it cannot be ISPYT022 Invalid hex data - Enter valid hex
opened. characters in multiples of two.
Explanation: This table is being used by another user Explanation: Hexadecimal characters must be entered
and cannot be used by you now. in multiples of two.
Programmer Response: The other user must close the Programmer Response: Correct the hexadecimal entry.
table before you can use it.
ISPYT024 Table aaaaaaaa opened - Table aaaaaaaa
ISPYT016 Library not allocated - The input table opened in bbbbbbbb mode by dialog test.
library is not allocated.
Explanation: This is an informational message.
Explanation: The library that contains the table has
not been allocated.
ISPYT025 Table aaaaaaaa closed - Table aaaaaaaa
User Response: Contact the responsible programmer. closed by dialog test.
Programmer Response: If the table is required, the Explanation: This is an informational message.
library must be allocated.
ISPYT031 No argument specified - A search
ISPYT017 Enter table name - The name of the argument is necessary for the LOCATE
table is required. command.
Explanation: You must enter a table name. Explanation: Before the LOCATE command can be
run, a value to be searched for must be entered.
User Response: Contact the responsible programmer.
Programmer Response: Enter a value following the
Programmer Response: Enter a table name to
LOCATE command.
continue.
ISPYT034 ’aaaaaaaa’ not found - Variable ’aaaaaaaa’ ISPYT041 Row exceeds table size - The specified
was not found in the row. row number is greater than the table
size.
Explanation: This is an informational message.
Explanation: The row number entered exceeds the
number of rows in the table.
ISPYT035 Command conflict - A line command is
within the range of the D command. Programmer Response: Display the structure to
Correct either one. determine the number of rows, or enter a correct row
number.
Explanation: There is a line command that would not
be processed because that line would be deleted when
the DELETE line command is completed. ISPYT042 Invalid row identity - The table row
must be specified as a number.
Programmer Response: Correct the conflicting line
commands. Explanation: This message is self-explanatory.
ISPYT036 Invalid name - Variable name ISPYT043 Row not identified - Enter a search
characters/syntax is not valid. argument or a row number.
Explanation: The variable name syntax is in error. Explanation: This option requires a row number or a
search argument.
Programmer Response: Correct the variable name.
Programmer Response: Enter a row number or search
argument.
ISPYT037 Too many parameters - No parameters
are defined for the ’CANCEL’ command.
ISPYT044 Function invalid - The function code is
Explanation: The CANCEL command does not allow
not valid.
parameters.
Explanation: The function code is invalid.
Programmer Response: Remove the data following
the CANCEL command. Programmer Response: If a valid option was entered,
this could be an internal error. Contact your system
programmer.
ISPYT038 Too many parameters - Only one
argument may be entered with the System Programmer Response: If you do not have
LOCATE command. mixed levels of ISPF code, contact IBM support.
Explanation: Only one name can be used with the
LOCATE command. ISPYT045 Row not found - No row matches the
search argument.
Programmer Response: Correct the LOCATE
command. Explanation: This message is self-explanatory.
ISPYT039 Use TOP - Use TOP for adding row 1. ISPYT046 Row found - A row matching the search
argument was found.
Explanation: Enter TOP to add a new row as the first
row. Explanation: This is an informational message.
Programmer Response: Enter TOP for row number.
ISPYT047 Row not deleted - The specified row
was not deleted from the table.
ISPYT040 Key/name protected - Key and name
variables may not be deleted. Explanation: This is an informational message. END
was entered, and the DELETE command was ignored.
Explanation: The DELETE command is not allowed
on key and name variables.
ISPYT048 Row aaaaaaaa deleted - Row aaaaaaaa was
Programmer Response: Do not attempt to delete
deleted from the table.
protected variables.
Explanation: This is an informational message.
ISPYT049 Row not deleted - No match searching ISPYT057 Invalid line command - Valid table
keyed table, or CRP was at top. commands are I (insert), R (repeat), and
D (delete).
Explanation: The row could not be deleted because no
match was found. Explanation: An invalid line command was used.
Programmer Response: Enter another search Programmer Response: Use only valid line
argument for the DELETE command. commands.
ISPYT050 Key/name not modifiable - Key and ISPYT058 Top is not valid - Top is only valid for
name variables may not be changed. adding a row.
Explanation: The key and names variable names Explanation: This message is self-explanatory.
cannot be changed.
Programmer Response: Do not attempt to change key ISPYT060 Enter WRITE or NOWRITE - Save
or names variable names. option is specified as WRITE or
NOWRITE.
ISPYT051 Keys are not unique - Another row in Explanation: This message is self-explanatory.
the table has the same key values.
User Response: Enter WRITE or NOWRITE.
Explanation: You cannot have two key variables with
the same value.
ISPYT070 Windowed panel - The panel or panels
Programmer Response: Provide another value for the for the selected option will appear in a
key variable. pop-up window.
Explanation: This is an informational message. The
ISPYT052 Row modified - The specified row has user selected a pull-down menu that changed the
been modified. display of an option from a full screen display to a
windowed display.
Explanation: This is an informational message.
ISPYT056 Table is at top - Display, modify and ISPYV001 Invalid pool specified - Enter F, I, S, or
CANCEL are not valid when the table is P.
at top.
Explanation: An incorrect variable pool was entered.
Explanation: This message is self-explanatory.
Programmer Response: Enter one of the correct
Programmer Response: Use a row number when the variable pools.
table is at top.
ISPYV002 Command not recognized - The valid ISPYV009 Variable name required - A variable
line commands are I (insert) and D name is required if data is entered for
(delete). pool or value.
Explanation: An incorrect line command was entered. Explanation: Variable pool information or a variable
value was entered, but the variable name was not
Programmer Response: Enter one of the correct line
entered.
commands.
Programmer Response: Enter a variable name.
ISPYV003 Duplicate variable - Variables within
each pool must have unique names. ISPYV011 Invalid hex data - Enter valid hex
characters in multiples of two.
Explanation: The variable name already exists within
the pool. Variable names must be unique. Explanation: Hexadecimal characters must be entered
in multiples of two.
Programmer Response: Enter a unique variable name.
Programmer Response: Correct the hexadecimal
character entry.
ISPYV004 Invalid command - The command
entered is not a valid variables
command. ISPYV012 aaaaaaaa failed - bbbbbbbb returned return
code cccccccc request (dddddddd).
Explanation: An invalid command was entered.
Explanation: The above service and request did not
Programmer Response: Enter a valid command, or
complete processing.
enter HELP for a list of valid commands.
Programmer Response: If the error continues, contact
the system programmer.
ISPYV005 No argument specified - A search
argument is necessary for the LOCATE System Programmer Response: This could be an
command. internal error or a system error. If you do not have
mixed levels of ISPF code, contact IBM support.
Explanation: The LOCATE command requires that
you enter the data to use for the search.
ISPYV013 Invalid variable syntax - Variable name
Programmer Response: Enter a search argument with
must be alphanumeric and the first
the LOCATE command.
character cannot be numeric.
Explanation: The variable name violates variable
ISPYV006 Variable name found - The specified
name syntax.
variable appears at the top of the
display. Programmer Response: Enter a valid variable name.
Explanation: This is an informational message.
ISPYV014 Delete not allowed - The indicated line
may not be deleted.
ISPYV007 Variable name not found - The specified
variable was not found in the variables Explanation: The DELETE command is not valid for
list. this line.
Explanation: The specified variable does not exist in Programmer Response: Do not attempt to delete
the variables list. variables that are not modifiable.
Programmer Response: Enter another variable, or
enter HELP for additional information. ISPYV015 Delete not allowed - Multiple DELETE
line command not allowed.
ISPYV008 Non-modifiable variable - This is a Explanation: The DELETE line command is limited to
system variable and may not be one line for each D.
altered/deleted by the user.
Programmer Response: Enter a D for each line to be
Explanation: This is an informational message. Type Z deleted.
system variables may not be altered or deleted.
ISPYV301 Internal test error - Unable to aaaaaaaa ISPYX002 Recursive Dialog Test - Dialog Test may
storage for variable bbbbbbbb. only be entered once in each screen.
Explanation: A storage problem prevented the Explanation: You attempted to enter Dialog Test for a
function from ending. second time in one screen. You may only enter Dialog
Test once per screen.
Programmer Response: If the problem continues,
contact the system programmer. User Response: Either split the screen and enter
Dialog Test from the new screen or back out of the
System Programmer Response: If you do not have
panels being displayed in the current screen until you
mixed levels of ISPF code, contact IBM support.
reach Dialog Test again.
ISPZZ101 aaaaaaaa
Explanation: This is an informational message. This is
a null message used for the top-row-displayed
indicator on table display panels when no rows are
being displayed.
ISRB012 Bad directory - Directory block size ISRB019 Label ’aaaaaaaa’ reassigned - Label
exceeds maximum of 256. ’aaaaaaaa’ is reassigned to line bbbbbbbb.
Explanation: The partitioned data set directory has an Explanation: This is an informational message.
incorrect blocksize.
User Response: Contact your system programmer. ISRB100 Panel error - The data display panel to
be used does not exist or is not usable.
System Programmer Response: Reproduce the
partitioned data set with a directory blocksize of 256. Explanation: The panel specified for use to display the
data does not exist or is unusable.
ISRB013 Enter label or number - Enter the line Programmer Response: Correct the BROWSE or BRIF
number or the label of the line to be service to use a valid data display panel.
displayed.
Explanation: The LOCATE command was entered ISRB101 Enter character string - Enter the string
with no parameter. of characters to be displayed.
User Response: Enter the LOCATE command Explanation: You entered the FIND command with no
followed by either a relative line number or a character string to find.
previously defined label.
User Response: Enter the FIND command followed
by the string of characters that you want to find.
ISRB014 Invalid parameter - A number or label
(.xxxx) is the only valid parameter.
ISRB102 Invalid keyword - Check spelling of
Explanation: The LOCATE command was entered keywords used with the FIND
with an invalid parameter. A valid parameter is either a command.
previously defined label or a relative line number. The
maximum length of the parameter is 8 characters. Explanation: The FIND command has an
unrecognizable keyword parameter. You may have
User Response: Enter the LOCATE command with a entered a FIND command with quotes that do not
valid parameter. correctly delimit the string that you want to find and
BROWSE is attempting to interpret the remainder of
the string as a keyword.
ISRB015 Label not defined - The label specified
has not yet been defined. User Response: Correct the spelling of the FIND
keywords, or correct the use of quotes to delimit the
Explanation: The LOCATE command was entered
string.
with a label that has not been defined.
User Response: Use a previously defined label or a
ISRB103 Enter a FIND command - The RFIND
relative line number as the parameter for the LOCATE
key works only after a FIND character
command.
string is entered.
Explanation: This is an informational message.
ISRB016 Invalid label - A label must be 1 to 8
chars long including the initial period.
Explanation: The LOCATE command was entered
with a label that is greater than 8 characters long.
User Response: Enter the LOCATE command with a
ISRB104 Put string in quotes - Put quotes (’ ’) ISRB110 Invalid data set - Data set for SUBMIT
around the string of characters to be command must be fixed 80.
displayed.
Explanation: The record format or LRECL of the data
Explanation: The FIND command was entered set you are browsing is not fixed 80. Only fixed 80 data
followed by two or more words (strings of characters sets can be processed by the SUBMIT command.
delimited by blanks) that are not recognized keywords
of FIND. To find these words, you must enclose them
ISRB111 SUBMIT not supported - SUBMIT
in single quotation marks to indicate that they are a
command is not supported for BRIF
single string.
service
User Response: Enclose the string for FIND in single
Explanation: This is an informational message.
quotation marks.
ISRB108 I/O error - An I/O error was encountered ISRB114 Partial data displayed - This is a
reading the first record requested. multivolume data set. If you did not
specify a volume, the data on all
Explanation: An I/O error occurred reading the first
volumes will be displayed. Otherwise,
record of the data set.
only the data on the volume that you
User Response: Retry the operation. If the error specified will be displayed.
recurs, contact your system programmer for assistance.
Explanation: This is an informational message.
System Programmer Response: Determine why the
data set is getting I/O errors and correct the problem.
ISRB115 Invalid data set - Data set for SUBMIT
command cannot contain packed data.
ISRB109 Insufficient storage - Not enough
Explanation: This is an informational message.
storage is available for BROWSE to
proceed.
ISRB116 SUBMIT not allowed - Your installation
Explanation: There is insufficient virtual storage for
does not allow the SUBMIT command
BROWSE to continue processing.
from Browse.
User Response: Reduce your use of virtual storage by
Explanation: Your installation has indicated in the
ending panels that you are not using, such as recursive
configuration table that the Browse SUBMIT command
BROWSE or EDIT sessions or other ISPF panels that
should be disabled.
you are using in pull-downs and so forth. Retry the
operation.
ISRB117 SUBMIT not executed - The member
you are browsing has changed. If you
exit from Browse and reenter, you will
see the changes that have been made.
Explanation: The Browse SUBMIT command is not
allowed if the member being browsed has been
Explanation: A string of characters was entered that User Response: Enter the character string that you
must be enclosed in single quotation marks to specify it want to find in the displayed file.
as a string to be found.
User Response: Enclose the string in single quotation ISRB162 Invalid hex string - The hex string must
marks. have an even number of hex digits.
Explanation: A hex string entered as a parameter to
ISRB154 Invalid keyword - The keywords the FIND command must have an even number of
’aaaaaaaa’ and ’bbbbbbbb’ cannot both be digits.
used. Delete one. User Response: Correct the hex FIND string.
Explanation: Two mutually exclusive keywords were
entered.
User Response: Use only one of the keywords.
ISRB163 No aaaaaaaa bbbbbbbb found - aaaaaaaa ISRB169 STAE macro error - Unable to obtain
bbbbbbbb - not found within cols cccccccc storage for STAE macro, subpool 0 full.
to dddddddd.
Explanation: ISPF was unable to obtain storage for the
Explanation: No occurance of the FIND string was STAE macro. Storage subpool 0 is full.
found within the boundaries specified on the FIND
User Response: Retry the operation. If the error
command.
recurs, contact your system programmer for assistance.
Programmer Response: Determine why subpool 0
ISRB164 Invalid hex string - The hex string must
storage is full and correct the problem.
contain only hex digits (0-9, A-F).
Explanation: Only hex digits (0-9, A-F) are valid when
ISRB180 Invalid BROWSE parameter - Member
specifying a hex FIND string (x’nnnn’).
name ″aaaaaaaa″ must be alphanumeric
User Response: Correct the FIND string. chars, starting with alpha.
Explanation: ISPF requires a member name that
ISRB165 * Top of data reached * - aaaaaaaa consists of alphanumeric characters with the first
bbbbbbbb not found. Press RFIND key to character being alpha.
continue from bottom.
User Response: Enter a valid member name.
Explanation: No occurance of the FIND string was
found from the point of the beginning of the search to
ISRB181 Invalid member name - ″aaaaaaaa″
the beginning of the data.
exceeds 8-character allowable member
User Response: Press RFIND to continue the FIND name length.
from the end of the data.
Explanation: Member names cannot be greater than 8
characters in length.
ISRB166 *Bottom of data reached* - aaaaaaaa
User Response: Enter a valid member name.
bbbbbbbb not found. Press RFIND key to
continue from top.
ISRB182 Member name invalid - A member
Explanation: No occurance of the FIND string was
name cannot be specified when
found from the point of the beginning of the search to
browsing sequential data set.
the end of the data.
Explanation: Sequential data sets do not contain
User Response: Press RFIND to continue the search
members.
from the beginning of the data.
User Response: Enter only the data set name in order
to browse a sequential data set. Do not enter a member
ISRB167 I/O error encountered - I/O error was
name.
detected while performing the FIND
command.
ISRB183 Recursion error - Recursive use of
Explanation: An I/O error occurred while reading
BROWSE is not allowed while browsing
data to process the FIND command.
the ISPF log.
User Response: Try the operation again. If the error
Explanation: Recursive BROWSE is not allowed when
recurs, contact your system programmer for assistance.
browsing the ISPF log data set.
System Programmer Response: Determine the cause
User Response: Do not use the BROWSE primary
of the I/O error, and correct the problem.
command when browsing the ISPF log.
ISRB185 Invalid format name - Specified format ISRB505 Too many parameters - A single
name contains invalid characters. character and/or (CC or NOCC) are the
only parameters allowed. One is
Explanation: The format name entered contains
required.
invalid characters. Format names must be
alphanumeric with the first character alpha. Explanation: The DISPLAY command accepts
parameters of only a single character (the character for
User Response: Use a valid format name.
non-displayable codes) and CC or NOCC to designate
whether or not to show carriage control characters. You
ISRB186 Invalid parameter - Extraneous or must enter at least one parameter.
invalid parameter specified with this
User Response: Correct the parameters.
command.
Explanation: Too many parameters or an invalid
ISRB506 Data set FREE error - An error was
parameter was entered.
encountered trying to free the data set(s)
User Response: Correct the parameters. being browsed
Explanation: An error prevented freeing the allocation
ISRB500 Too many parameters - For the ’aaaaaaaa’ for the data set being browsed. This data set may still
command. be allocated to your user ID. The allocation will be
freed when you log off.
Explanation: Too many parameters were entered for
the command. User Response: If the allocation interferes with the
use of the data set by other users, log off and log back
User Response: Correct the parameters. on.
ISRB501 Invalid parameter - ’aaaaaaaa’ is not a ISRB507 Parameter missing - A single character
valid parameter for the ’bbbbbbbb’ and/or (CC or NOCC) are the only
command. parameters allowed. One is required.
Explanation: An invalid parameter was entered for Explanation: The DISPLAY command accepts
this command. parameters of only a single character (the character for
User Response: Correct the parameters. non-displayable codes) and CC or NOCC to designate
whether or not to show carriage control characters. You
must enter at least one parameter.
ISRB502 Inconsistent parameters - ’aaaaaaaa’ and
’bbbbbbbb’ are inconsistent with ’cccccccc’ User Response: Correct the parameters.
command.
Explanation: The parameters entered were ISRB600 Command not supported - BROWSE
inconsistent or conflicting. command not supported by the dialog
supplied command routine.
User Response: Correct the parameters.
Explanation: The command routine used by your
dialog does not support BROWSE as a command.
ISRB503 String too long - The invalid character
for the DISPLAY command can only be
a length of one. ISRB601 Invalid record format - Record format
must be F, FA, FM, V, VA, VM, or U. If
Explanation: The ″character″ parameter of the the record format is other than U it may
DISPLAY command can only be one character in also be blocked (FB, VBA, etc.).
length.
Explanation: The data set selected for browsing has an
User Response: Correct the parameter. unsupported record format. You cannot browse this
data set.
ISRB504 Inconsistent parameters - A single
character and/or (CC or NOCC) are the ISRB602 Record length too large - Maximum
only parameters allowed. record length is 32760.
Explanation: The DISPLAY command accepts Explanation: The data set selected for browsing has a
parameters of only a single character (the character for record length greater than 32 760. You cannot browse
non-displayable codes) and CC or NOCC to designate this data set.
whether or not to show carriage control characters.
User Response: Correct the parameters.
ISRCP005 Command completed - The BROWSE ISRCS004 List not found - Shared personal list not
command completed successfully. found in library ISPTLIB. Defaulting to
private list in library ISPPROF. Shared
Explanation: This is an informational message.
personal list tables ISRPLSHR (personal
data set lists) or ISRLLSHR (personal
ISRCP006 Invalid parameter - Module ISRCPREC library lists), was not found in library
received an invalid parameter. ISPTLIB.
Explanation: The parameter passed to ISRCPREC is Explanation: This is an informational message. The
not EDIT or VIEW. shared personal list was not found in library ISPTLIB.
Referral list will default to user profile data set.
User Response: Contact your system programmer.
User Response: Contact your systems programmer.
System Programmer Response: This is a
programming error. Contact IBM support. Programmer Response: Create a common personal list
that is concatanated to the users ISPTLIB library.
ISRCP008 Recovery successful - Edit recovery User Response: Mark a list, then select a file action.
completed successfully.
Explanation: This is an informational message. ISRCS006 Required parm missing - Required
personal list name is blank or invalid. A
personal list name is required for this
ISRCS000 Invalid INTENS - Invalid INTENS - action. The list name must begin with
Enter HIGH, LOW, or NON. an alphabetic character followed by any
Explanation: An invalid INTENS value has been valid alphanumeric character for a total
entered. length of up to eight characters.
User Response: Enter HIGH, LOW, or NON for Explanation: An invalid command was entered for
INTENS value. this function.
User Response: Enter a personal list name as a
ISRCS001 Invalid COLOR - Invalid COLOR - parameter for command.
Enter - BLUE, GREEN, TURQ, YELLOW,
RED, PINK, or WHITE. ISRCS007 Reference list inactive - A reference list
Explanation: An invalid COLOR has been entered. has not been created yet. Enter
command REFLISTx, where ″x″ is either
User Response: Enter BLUE, GREEN, TURQ, an ″L″ for library, or a ″D″ for data set
YELLOW, RED, PINK, or WHITE for color value. reference list. To set list to update mode,
select action ″update on″ from action bar
ISRCS002 Invalid HILITE - Invalid HILITE - Enter ″List″. Data sets and libraries that are
- REVERSE, USCORE, BLINK, or referenced in your ISPF session will
NONE. now be added to the reference list.
Explanation: An invalid HILITE has been entered. Explanation: There is no reference list active for this
user.
User Response: Enter REVERSE, USCORE, BLINK, or
NONE for Hilite value. User Response: Activate reference list via the list
pull-down on the Reflist main panel.
Explanation: It is invalid to specify TSO without User Response: Correct the password and reenter. If
following it with a valid TSO command. you did not specify a password on this panel and this
is a recurring problem, you may have a variable named
User Response: Enter a valid TSO command after the PSWD in your ISPF profile pool that is being used by
word TSO. ISPF. If you suspect this is the case, you should do one
of the following:
ISRC605 Invalid password - The password field v Enter the Dialog Test Variables option (ISPF option
contains invalid characters. Valid 7.3) and issue ″LOCATE PSWD″ from the command
characters are (0-9, A-Z, #, $, or @). line. If the variable is found, use the D line command
to delete the variable.
Explanation: A password was entered that contained
invalid characters. An MVS password must: v Use the VERASE service to remove the variable by
v Be 1-8 characters in length invoking a CLIST or REXX exec that contains the
command ″ISPEXEC VERASE PSWD BOTH″.
| ISRDD021 Syntax error - The command entered ISRDS006 Multiple list actions - Only a single list
| contains an invalid indirect addressing can be processed. Multiple lists cannot
| string. be selected for updates or actions.
Explanation: Multiple lists were selected by the user.
| ISRDD030 Unavailable option - The ENQ displays
User Response: Select a single list from the name list.
| have been disabled by your system
| programmer.
ISRDS007 Delete not allowed - The currently
active list cannot be deleted unless it is
ISRDS000 Save As canceled - The name you
first opened. Perform an Open action
entered already exists as a personal list
and then select action ″D″ to delete the
name.
currently active list.
Explanation: A save-as list name already exists as a
Explanation: A list that is active cannot be deleted.
current list.
User Response: Select a list and use the file action
User Response: Enter a list name that is not a
Delete to delete list.
duplicate.
ISRD010 File name in use - File name (ddname) ISRD016 Duplicate data set name - Data set
’aaaaaaaa’ is allocated to another data set. ’aaa(44)’ already exists.
Explanation: PDF attempted to allocate a data set to Explanation: PDF received a return code 4, error code
ddname aaaaaaaa, but the ddname was already X'4704' from SVC 99 indicating that the data set aaa(44).
allocated. specified for creation already exists.
User Response: Free the existing allocation using the User Response: If the data set name was supplied to
TSO FREE FI(ddname) command. PDF by you, choose a new name and retry. If you were
running a local dialog, contact the responsible
programmer for assistance.
ISRD011 Data set not allocated - ’aaa(44)’ was not
allocated like ’bbb(44)’. The return code Programmer Response: If the data set name was
from SVC 99 was ’cccccccc’. supplied to PDF by you, choose a new name and retry.
If further help is needed, contact the system
Explanation: The data set being moved/copied to
programmer.
could not be allocated like the data set being
moved/copied from. System Programmer Response: Contact IBM support.
System Programmer Response: Contact IBM support.
ISRD019 Catalog error - Already cataloged,
VSAM protected, or other - ’aaa(44)’.
| ISRD012 No data to compare - SuperC returned a
| return code of 28. This means that either Explanation: PDF received a return code 4, error code
| both data sets being compared are X'5708' from SVC 99 indicating that a return code 8 was
| empty, or after input filtering there is no received from the CATALOG macro during processing
| data to compare. Input filtering causes of data set aaa(44).
| SuperC to not compare data such as
User Response: Contact your system programmer.
| comments or blank lines. You can check
| your filtering options by issuing the System Programmer Response: Refer to system
| COMPARE command with no message IDC3009I for assistance.
| arguments.
| Explanation: The COMPARE command was entered ISRD020 Data set is open - The ddname or
| in the editor but both the file being edited and the data dsname specified is associated with an
| set or member it is being compared to are empty or open data set.
| they have no data to be used for the comparison after
| filtering is completed. The input filtering is defined by Explanation: PDF received a return code 4, error code
| the panel which is displayed when the COMPARE X'0420' from SVC 99 indicating that the data you are
| command is entered without any operands. trying to process is currently open by you or another
user.
| User Response: Check to see if both files are empty. If
| not, enter the COMPARE command on the edit User Response: Contact your system programmer for
| command line and uncheck the filtering options. assistance in determining who has the data set open.
The data set must be closed before you can successfully
complete the function you requested.
ISRD014 Data set not cataloged - ’aaa(44)’ was not
found in catalog. System Programmer Response: Contact IBM support.
User Response: If the data set name was supplied to Explanation: PDF received a return code 4, error code
PDF by you, correct the name and retry. If you were X'021C' from SVC 99 indicating that the unit name
running a local dialog, contact the responsible specified (aaaaaaaa) is not defined to your MVS system.
programmer for assistance. User Response: Contact your system programmer.
Programmer Response: If the data set name was System Programmer Response: Contact IBM support.
supplied to PDF by you, correct the name and retry. If
further help is needed, contact the system programmer.
System Programmer Response: Contact IBM support.
Programmer Response: Have your tool or dialog System Programmer Response: If the data set name
specify a different data set (one that does not reside on specified is correct, contact IBM support.
TAPE).
System Programmer Response: If the data in the ISRD029 Uncatalog error - ’aaa(44)’ could not be
TAPE data set needs to be processed by PDF, copy the uncataloged.
data set to DASD using IEBCOPY, then process the Explanation: PDF received a non-zero return code
DASD copy. when attempting to uncatalog a data set (aaa(44))
during a data set deletion request.
ISRD024 Request failed - Allocation/deallocation User Response: You may not have authority to
failed. Press Help for more information. uncatalog the data set. Contact your system
Explanation: PDF received an SVC 99 return programmer to determine your RACF authority level,
code/error code combination for which there is no or have someone with higher authority uncatalog the
specific PDF message. Entering the HELP command data set using PDF option 3.2.U.
when this message is displayed will provide a tutorial System Programmer Response: Determine whether
panel with the error messages generated by the system, the user has the proper RACF authority to perform the
as well as the SVC 99 return code, error code, and uncatalog request. If yes, there may be a problem with
information code. the catalog itself and you should refer to the
User Response: Read the detailed message provided appropriate DFP manuals for assistance in problem
via the tutorial, and address the problems indicated. determination. If the user does not have the proper
RACF authority, you can raise the RACF level (if
appropriate) or have someone with the proper
ISRD026 Invalid index structure - Dsname authority level uncatalog the data set using PDF option
’aaa(44)’ index conflict. 3.2.U.
Explanation: PDF received a return code 12 or 16 from
the LOCATE macro, indicating a problem with the
index or generation data group specified (aaa(44)).
User Response: Contact your system programmer.
ISRD030 No space available - Insufficient space ISRD034 Volume not available - Volume ’aaaaaa’
for data set ’aaa(44)’. not mounted or not authorized for your
use.
Explanation: PDF received a return code 4, error code
X'4714' from SVC 99 indicating that there is insufficient Explanation: PDF received one of the following return
space for the data set specified (aaa(44)) on the volume codes while processing volume aaaaaa, indicating that
selected by the system. the volume specified is not available for your use:
User Response: Retry the allocation. The system may v Return code 4 from the OBTAIN macro
pick a different volume that has sufficient space to v SVC 99 return code 4 with one of the following error
satisfy the request. If you know of a specific volume codes: X'0214', X'0218', X'0220', X'0248', X'0498',
that has enough space, you may specify that volume X'049C', or X'6704'.
name on the Allocate New Data Set panel in PDF
User Response: Verify that the correct data set name
option 3.2.
and volume were specified to PDF, and correct them if
necessary. If the data specified looks correct, contact
| ISRD031 Member in use - The member is being your system programmer.
| updated by you or by another user.
| Explanation: The member specified is being updated ISRD035 Data set in use - Data set ’aaa(44)’ in use
| by you on another logical screen or by another user. by another user, try later or enter HELP
for a list of jobs and users allocated to
| User Response: Find out if the member is in use by
’aaa(44)’.
| another user, or release the member from another
| logical screen. Explanation: PDF received a return code 4, error code
X'020C' or X'0210' from SVC 99 indicating data set
aaa(44) is currently allocated to another job or user and
ISRD032 Data set not found - ’aaa(44)’ not on
is, therefore, unavailable to satisfy your request.
volume ’bbbbbb’.
User Response: If the data set is in use by another job,
Explanation: PDF received a return code 8 from the
wait for that job to finish, or have the submitter of the
OBTAIN macro, indicating that data set aaa(44) does
job cancel it, then retry your request. If the data set is
not exist on volume bbbbbb.
in use by another user, have that user free it, then retry
User Response: If you specified both the data set the request.
name and the volume, determine the correct volume
for the data set and retry the request. If you did not
ISRD036 VTOC full on vol ’aaaaaa’ - No room in
supply a volume, the data set is not on the volume
volume table of contents for more data
indicated by the catalog. This may indicate that there is
sets.
a catalog entry only but no data set, or it may indicate
a catalog error. Contact your system programmer for Explanation: PDF received a return code 4, error code
assistance in determining the correct action to take. X'4708' (return code 8 from DADSM allocate) indicating
that the volume table of contents for volume aaaaaa is
System Programmer Response: Consult the
full; therefore, the entry needed to satisfy your request
appropriate DFP documentation for problem
cannot be added.
determination.
User Response: If you are attempting to create a data
set, reissue the request and the system may choose a
ISRD033 Catalog or VTOC error - I/O,
different volume as the target for the create, or you can
insufficient storage, or unrecoverable
specify a specific volume on the Allocate New Data Set
error with volume aaaaaa.
panel in PDF option 3.2. If the problem persists, contact
Explanation: PDF received one of the following return your system programmer.
codes while processing volume aaaaaa, indicating an
error in processing the VTOC for that volume, or the
ISRD037 No space on vol ’aaaaaa’ - Insufficient
catalog:
space for data set ’bbb(44)’.
v Return code > 8 from the OBTAIN macro
v Return code 24 from the LOCATE macro Explanation: PDF received a return code 4, error code
v Return code 12 from DADSM allocate. X'4714' (return code 20 from DADSM allocate)
indicating that volume aaaaaa does not have sufficient
User Response: Contact your system programmer for
space available to satisfy your create request for data
assistance in problem determination.
set bbb(44).
System Programmer Response: Refer to the
User Response: Specify a different volume on the
appropriate IBM manuals for problem determination.
Allocate New Data Set panel, or leave the volume field
blank to take the system default. If the problem
ISREI012 Invalid edit length - The edit length ISREI023 EDIREC service error - EDIREC QUERY
must be less than or equal to the record or INIT is not allowed because recovery
length. is pending.
Explanation: An invalid edit length is specified for the Explanation: The QUERY or INIT option for the
EDIF service. EDIREC service is not allowed when recovery is
pending.
User Response: Contact the responsible programmer.
User Response: Contact the responsible programmer.
Programmer Response: Specifiy an edit length less
than or equal to the record length. Programmer Response: Invoke the EDIF service with
recovery-request = YES to recover the data, or invoke
the EDIREC service with the CANCEL or DEFER
ISREI013 Conflicting options used - The edit
options to dispose of the pending recovery condition.
length and the format are mutually
exclusive.
ISREI024 Invalid CANCEL request - EDIREC
Explanation: Conflicting options are specified for the
CANCEL request issued before query
EDIF service. The edit length and the format cannot be
for recovery pending.
used simultaneously.
Explanation: An invalid CANCEL request is issued
User Response: Contact the responsible programmer.
for the EDIREC service before the query for recovery
Programmer Response: Blank out one of the pending.
conflicting options.
User Response: Contact the responsible programmer.
Programmer Response: Use the QUERY option for the
ISREI020 Invalid EDIREC option - Only one of
EDIREC service before issuing a CANCEL request to
the following options allowed : QUERY,
scan the EDIF recovery table for an entry containing a
CANCEL, DEFER or INIT.
recovery pending condition.
Explanation: An invalid option is specified for the
EDIREC service.
ISREI025 Data in use - Data is being updated by
User Response: Contact the responsible programmer. another user or on other logical screen.
Programmer Response: Specify one of the allowed Explanation: The data set requested is being updated
options (QUERY, CANCEL, DEFER, or INIT) for the by another user or by you on another logical screen.
EDIREC service.
User Response: Check the data set name, find out if
another user is using the the data set, or release the
ISREI021 Invalid EDIREC parameter - The data set on another logical screen.
COMMAND parameter may only be
specified with the INIT option.
ISREI026 Recovery is not pending - The edit
Explanation: An invalid parameter is specified for the recovery cannot proceed when recovery
EDIREC service. The COMMAND parameter may only is not pending.
be specified with the INIT option.
Explanation: An edit recovery is requested while
User Response: Contact the responsible programmer. recovery is not pending.
Programmer Response: Either correct the option to User Response: Contact the responsible programmer.
INIT or blank out the COMMAND parameter out.
Programmer Response: Correct the recovery-request
option for the EDIF service.
ISREI022 EDIREC service error - EDIREC
CANCEL or DEFER issued, but recovery
ISREV000 Browse substituted - Browse was
is not pending.
substituted for View or Edit, since not
Explanation: The CANCEL or DEFER option is enough storage was available.
specified for the EDIREC service, but recovery is not
Explanation: This is an informational message. There
pending.
was not enough storage available for the VIEW or
User Response: Contact the responsible programmer. EDIT command to process correctly. Therefore Browse
was substituted.
Programmer Response: Use the QUERY option for the
EDIREC service to scan the EDIF recovery table for an
entry containing a recovery pending condition.
ISREV001 Browse substituted - Browse was ISREV005 VSAM browse rc = aaaaaaaa. - A VSAM
substituted for View or Edit, since browser ended with return code
neither data sets with a record length aaaaaaaa. It was substituted for Browse
less than 10 nor data sets with because of configuration table settings.
RECFM=U can be Viewed or Edited.
Explanation: If you try to browse a VSAM data set
Explanation: This is an informational message. You and a VSAM browser has been specified in the
can only edit or view data that has certain record configuration table, the VSAM browser is automatically
formats and record lengths. If Edit cannot process the invoked by ISPF.
data, Browse is substituted.
ISREV006 VSAM View rc = aaaaaaaa.. - A VSAM
ISREV002 Return ignored - The return command viewer ended with return code aaaaaaaa.
was preempted to allow the View It was substituted for View because of
Warning panel to display. configuration table settings.
Explanation: This is an informational message. Explanation: If you try to view a VSAM data set and
Changes were made from within a view session. In a VSAM viewer has been specified in the configuration
order to inform users that the changes will not be table, the VSAM viewer is automatically invoked by
saved, the RETURN command has been preempted. ISPF.
| ISREV003 Browse substituted - Browse was ISREV007 VSAM rc = aaaaaaaa. - ISPF attempted to
| substituted for View or Edit, because invoke a VSAM processor on bbbbbbbb.
| the amount of storage required to edit The VSAM editor, viewer, or browser
| or view the data set exceeded the exited with return code aaaaaaaa.
| maximum value allowed by your ISPF
Explanation: If you try to edit, view, or browse a
| system configuration or your editor
VSAM data set, ISPF looks at the configuration table to
| settings (aaaaaaaa.Kb). You can use the
determine if there is a VSAM editor, viewer, or browser
| EDITSET command to change this limit.
requested. If so, it is automatically invoked by ISPF.
| However, the limit you set in the editor
The return code variable is the value returned by the
| settings panel cannot be used to
processor, or the return code for the select service.
| increase limits set in the ISPF
| Configuration table. System Programmer Response: Install the VSAM
processor on your system, or change the configuration
| Explanation: The amount of storage required to read
table values to correctly invoke the VSAM processor.
| in the data to be edited or viewed exceeds the amount
| allowed by the PDF configuration table or the editor
| settings. When the amount of storage needed to edit a ISREV008 VSAM processing unavail. - aaaaaaaa is a
| data set exceeds the system defined limits, browse is VSAM data set. An attempt was made
| substituted for edit or view. You can change your editor to invoke a VSAM editor, viewer, or
| settings by using the EDITSET command from within browser, but it is not allowed, due to
| an edit session. The value you set in the editor settings configuration table settings.
| panel will not permit you to use more storage for edit
| or view than the ISPF configuration table allows. Explanation: If you try to edit, view, or browse a
VSAM data set, ISPF looks at the configuration table to
User Response: If you need to have this value determine if the VSAM data set is allowed to be
increased, contact your system programmer. processed.
System Programmer Response: To increase the System Programmer Response: Determine if this user
amount of storage allowed for the initial loading of should be allowed to change this data set. If so, update
data into edit or view, modify the value of EDITSTOR the configuration table.
in the PDF configuration table.
Explanation: When restricting VSAM processing Explanation: You are in text-entry mode. You may
through the ISPF Configuration Table, The ISPF type text without regard to end-of-line considerations.
Configuration Table Utility creates a load module called Press Enter to return to normal edit mode.
ISPCFIGV which contains the restriction information.
The ISPF Configuration Table currently in use indicates ISRE006 Edit - Save - aaaaaaaa(bbbbbbbb) - member
that VSAM restrictions are present, but load module saved.
ISPCFIGV cannot be found.
Explanation: This is an informational message.
User Response: Contact your system programmer.
System Programmer Response: Module ISPCFIGV ISRE007 Edit - Save - aaaaaaaa - data set saved.
may not have been moved into a library in the ISPF
search sequence, or may have been renamed or deleted. Explanation: This is an informational message.
The module can be recreated if necessary through the
ISPF Configuration Table utility and must be reside in a
ISRE008 Edit - Create - aaaaaaaa(bbbbbbbb) -
library in the ISPF search sequence.
member created.
Explanation: This is an informational message.
ISRE000 Invalid profile name - The profile name
must be blank, or be valid as part of a
data set name.
Explanation: The profile name entered is not a valid
data set group name.
ISRE009 Edit - Replace - aaaaaaaa(bbbbbbbb) - ISRE018 Member aaaaaaaa created - aaaaaaaa was
member replaced. added to bbbbbbbb
Explanation: This is an informational message. Explanation: This is an informational message.
ISRE010 Edit - Move - aaaaaaaa(bbbbbbbb) - ISRE019 Member aaaaaaaa replaced - aaaaaaaa was
member deleted. replaced in bbbbbbbb
Explanation: This is an informational message. Explanation: This is an informational message.
ISRE011 Edit - Move - aaaaaaaa deleted. ISRE020 Data saved - The data has been saved.
Explanation: This is an informational message. Explanation: This is an informational message. Data
saved from the EDIF session.
ISRE012 Member aaaaaaaa exists - aaaaaaaa already
exists. The CREATE command will not ISRE021 Member aaaaaaaa bbbbbbbb - Member
replace a member. aaaaaaaa was bbbbbbbb and cccccccc exists
in library.
Explanation: The member the user is trying to create
already exists in the TO library. Explanation: This is an informational message. The
requested MOVE or COPY action was completed
User Response: Enter a new CREATE member name.
successfully.
ISRE028 Invalid LRECL - Data length must be Explanation: This is an informational message. The
greater than 9 and less than 32761 for temporary JCL data set was empty.
fixed record length data sets and less
than 32757 for variable length data sets. ISRE035 Invalid left bound - Left bound was
Explanation: The ISPF editor only supports data invalid as entered and was reset to its
lengths from 10 to 32 760 for fixed length data sets default column.
(Record format F or FB) and from 10 to 32 756 for Explanation: The left bound entered was invalid. A
variable length data sets (Record format V or VB) valid left boundary is usually 1, 7, or 9 depending on
inclusive. the type of sequence numbering in effect and the
User Response: You may want to copy the data from record format of the data set being edited.
the data set you are trying to edit into a data set that User Response: Enter a valid left bound.
has a logical record length supported by ISPF edit. Edit
the temporary copy, then copy the temporary data set
back into the original data set. ISRE036 Invalid right bound - Right bound was
invalid as entered and was reset to its
default column.
ISRE029 Truncation error - The combined length
of the TABS and MASK lines is too Explanation: The right bound entered was invalid.
large. User Response: Enter a valid right bound. A valid
Explanation: This is an informational message. A right boundary is usually the record length or the
USER_STATE edit macro command was issued but the record length minus 8, depending on the type of
combined length of the TABS and MASK lines is too sequence numbering in effect and the record format of
large to save so they have been truncated. the data set being edited.
ISRE030 SUBMIT failed - SUBMIT abended or ISRE037 Some input data ignored - Data typed
gave non-zero return code, or attention into number fields is ignored while
occurred. numbering mode is on.
Explanation: SUBMIT processing ended abnormally. Explanation: The data entered into the number field is
ignored.
User Response: Contact your system programmer.
User Response: Reenter the data on a new line.
ISRE038 Some input data ignored - Data to be ISRE045 Command conflict - ″aaaaaaaa″ is within
moved outside of the data area of the the range of the ″bbbbbbbb″ command.
record was ignored. Correct one.
Explanation: The data entered outside the record field Explanation: The aaaaaaaa line command is within the
is ignored. range of the bbbbbbbb line command.
User Response: Reenter the data within the bounds of User Response: Blank out one of the conflicting line
the data area. commands.
ISRE039 Invalid/undefined label - Label aaaaaaaa ISRE046 Command conflict - ″aaaaaaaa″ conflicts
used in SUBMIT range is undefined or with a previous ″bbbbbbbb″ command.
has bad syntax. Delete one.
Explanation: An undefined label was used. Explanation: Both of the edit aaaaaaaa and bbbbbbbb
line commands require a destination command. They
User Response: Reenter a defined label.
cannot be used simultaneously.
User Response: Blank out one of the conflicting line
ISRE040 Block command incomplete - Enter a
commands.
matching ″aaaaaaaa″ command to
complete the block command pair.
ISRE047 Command conflict - Macro ″aaaaaaaa″
Explanation: An incomplete block command was
conflicts with the ″bbbbbbbb″ line
found.
command. Delete one.
User Response: Enter a matching aaaaaaaa line
Explanation: The aaaaaaaa command conflicts with the
command to complete the block command pair.
bbbbbbbb line command.
User Response: Blank out one of the conflicting
ISRE041 Command not recognized - ″aaaaaaaa″ is
commands.
not a valid line command. Correct it or
blank it out.
ISRE048 Command conflict - ″aaaaaaaa″ command
Explanation: aaaaaaaa is not a valid line command.
conflicts with prior ″bbbbbbbb″
User Response: Correct the aaaaaaaa line command or specification. Delete one.
blank it out.
Explanation: Two destination line commands have
been specified.
ISRE042 Number is invalid - A number is not
User Response: Blank out one of the conflicting
allowed with the ″aaaaaaaa″ line
destination line commands.
command. Blank it out.
Explanation: A number was found with the aaaaaaaa
ISRE049 Command conflict - ″aaaaaaaa″ is within
line command.
the range of the ″bbbbbbbb″ command.
User Response: Blank out the number. Correct one.
Explanation: The aaaaaaaa line command is within the
ISRE043 Invalid on this line - ″aaaaaaaa″ is not range of the bbbbbbbb line command.
valid on the line that it was entered.
User Response: Blank out one of the conflicting line
Blank it out.
commands.
Explanation: The aaaaaaaa line command entered is
not valid on the line where it was entered.
ISRE050 Command conflict - A text entry area is
User Response: Blank out the aaaaaaaa line command. within the range of the aaaaaaaa
command.
ISRE044 Command conflict - ″aaaaaaaa″ conflicts Explanation: A TE line command was issued along
with ″bbbbbbbb″ range specification. with another line command, such as Dn. The number
Blank it out. of lines affected by the second line command
overlapped the text entry area.
Explanation: The aaaaaaaa line command conflicts with
the bbbbbbbb range specification for the User Response: Remove the offending line command.
CREATE/REPLACE macro command.
User Response: Blank out the aaaaaaaa line command.
ISRE065 Invalid parameter - The parameter must ISRE072 Too many parameters - ON and OFF are
be a line number (8 digits or fewer). the only valid parameters for the SCAN
command.
Explanation: The line number specified for the
LOCATE primary command must be a number with 8 Explanation: Too many parameters are specified for
digits or fewer. the SCAN macro command.
User Response: Correct the line number parameter for User Response: Specify either the ON or OFF
the LOCATE primary command. parameter for the SCAN macro command.
ISRE066 Invalid parameter - Invalid line number ISRE073 Invalid parameter - ON and OFF are the
or label or LOCATE keyword. only valid parameters for the SCAN
command.
Explanation: An invalid parameter was specified for
the LOCATE command. Explanation: An invalid parameter is specified for the
SCAN macro command.
User Response: Correct the invalid parameter. For
further information on the LOCATE command, refer to User Response: Specify either the ON or OFF
ISPF Edit and Edit Macros parameter for the SCAN macro command.
ISRE067 Invalid parameter - The parameter must ISRE074 Inconsistent parameters - ″aaaaaaaa″ and
be a COBOL line number (6 digits or ″bbbbbbbb″ cannot both be entered with
fewer). SCAN command.
Explanation: The COBOL line number specified for Explanation: Inconsistent parameters are specified for
the LOCATE primary command must be a number the SCAN macro command.
with 6 digits or fewer.
User Response: Specify either the aaaaaaaa or bbbbbbbb
User Response: Correct the line number. parameter.
ISRE068 Insufficient storage - Insufficient storage ISRE075 Parameter unrecognized - ON and OFF
to perform the TF line command that are the only valid parameters for the
was entered. SCAN command.
Explanation: The TF line command requires more Explanation: An invalid parameter is specified for the
storage than is currently available. SCAN macro command.
User Response: Correct the name of the macro. User Response: Correct either the source lines or the
bounds and try the MOVE operaton again.
User Response: Invoke the END command without Explanation: There were more lines to be moved than
any parameters. lines to be overlaid. Extra lines were ignored.
User Response: Specify the same number of lines to
ISRE082 Line not deleted - MOVE changed to be moved as lines to be overlaid.
COPY. Data on receiving line(s)
prevented complete move. ISRE088 Workstation file saved - aaaaaaaa was
Explanation: A non-blank character(s) was found in saved on workstation.
the overlay lines. The MOVE operation was changed to Explanation: This is an informational message.
COPY so that the source line would not be deleted.
User Response: Correct the source or the target lines ISRE089 Edit - Save - aaaaaaaa - file saved on
so that they do not overlap each other. workstation.
Explanation: This is an informational message.
ISRE083 Lines not deleted - MOVE changed to
COPY. Data on receiving line(s)
prevented complete move. ISRE090 Invalid member name - Member name
aaaaaaaa not valid for partitioned data
Explanation: A non-blank character(s) was found in sets.
the overlay lines. The MOVE operation was changed to
COPY so that the source lines would not be deleted. Explanation: The member name aaaaaaaa specified is
not valid for partitioned data sets.
User Response: Correct the source or the target lines
so that they do not overlap each other. User Response: Specify a member name that does not
exceed 8 characters, begins with an alphabetic or
ISRE130 aaaaaaaa label invalid - Label aaaaaaaa is ISRE137 No variable name coded - No variable
not currently assigned to a line. name found between starting ″(″ and
ending ″)″.
Explanation: The label specified in the command
cannot be found. Explanation: A variable name is needed between the
parentheses.
User Response: Specify a label that is currently
assigned. User Response: Add a variable name between the
parentheses.
ISRE131 Variable name invalid - Variable name
″aaaaaaaa″ has a length greater than 8 or ISRE138 Invalid reset parameter - Enter a aaaaaaaa
a 0 length. range and/or X, ERR, CHG, CMD, SPE,
FIND, LAB.
Explanation: All variable names must be 1 to 8
characters long. Explanation: Either a partial range was entered, or a
range was entered with an invalid type of lines to reset.
User Response: Specify a variable name that is 1 to 8
characters long. User Response: If you have specified a partial range,
then enter the beginning or ending range value. If you
have specified a type of line to reset, be sure it is a
ISRE132 Invalid variable format - The ending ″)″
valid type for the reset command.
was not found for a variable name
format.
ISRE139 Inconsistent parameters - NOTE
Explanation: The command requires that variables be
command has one parameter: Specify
enclosed in parentheses.
either ON or OFF.
User Response: Add the closing parenthesis at the
Explanation: The only valid parameters for the NOTE
end of the variable string.
command are ON or OFF.
User Response: Specify the NOTE command with
ISRE133 Invalid variable format - The ending ″)″
either ON or OFF.
for a variable name is missing within a
template phrase.
ISRE140 Invalid/too many parms - ON or OFF
Explanation: Variable names within a template must
are the only valid parameters on the
be enclosed in parentheses.
NOTE command.
User Response: Add the closing parenthesis after the
Explanation: The NOTE command requires only one
variable name.
parameter. ON or OFF are the only valid parameters.
User Response: Correct the parameter on the NOTE
ISRE134 Invalid template format - The ending
command.
″>″ to indicate the end of a template
was not found.
ISRE141 Syntax is incorrect - Assignment
Explanation: A template must be enclosed by less
statement must use syntax ″ISREDIT
than (<) and greater than (>) signs.
aaaaaaaa = value″.
User Response: Add the greater than sign at the end
Explanation: This assignment statement is a single
of the template.
value phrase.
User Response: Correct the assignment statement.
ISRE135 Invalid template format - A template
number was not found when expected.
ISRE142 Syntax is incorrect - Assignment stmt
Explanation: A column number is needed to indicate
must use syntax ″ISREDIT aaaaaaaa lptr
where the variable or string is to be substituted.
= value″.
Explanation: This assignment statement requires a line
ISRE136 Invalid aaaaaaaa - The requested line
pointer argument.
was not found.
User Response: Correct the assignment statement.
Explanation: The line indicated in the line pointer
could not be found.
User Response: Correct the line pointer.
ISRE157 No aaaaaaaa bbbbbbbb found - aaaaaaaa ISRE162 No lines searched - No aaaaaaaa lines
bbbbbbbb - not found on any cccccccc lines were found for the FIND command to
from dddddddd to eeeeeeee. search.
Explanation: The find string was not found on any Explanation: No excluded or unexcluded lines exist in
excluded or non-excluded lines between the specified the file for the FIND command to search.
labels.
User Response: Change the FIND command to
User Response: Use RFIND to search other areas for remove the X or NX specification.
the string.
ISRE163 Invalid character - Invalid special
ISRE158 Invalid left boundary - aaaaaaaa (left character for a picture (P’xxx’) string.
bound) + bbbbbbbb (string size) greater
Explanation: An invalid character exists in a picture
than cccccccc (LRECL).
string specification on a FIND command. The character
Explanation: The left boundary plus the size of the may be an unusual hexadecimal code such as X'01' if
find string exceeds the record length. the command is issued from a macro.
User Response: Change the left boundary. User Response: Change the FIND command to specify
valid picture string characters.
ISRE159 Invalid column range - The aaaaaaaa
column range attempts a search beyond ISRE164 No aaaaaaaa bbbbbbbb found - aaaaaaaa
the last data column. bbbbbbbb - not found on any cccccccc lines
(cols ddddd to eeeee).
Explanation: This message is issued when a FIND,
CHANGE, or SEEK command is used in an edit macro Explanation: The search string was not found by the
and the column range is greater than the last column of FIND command on any excluded or non-excluded lines
data. between columns ddddd and eeeee.
User Response: Correct the column range. User Response: No action is required, but you may
want to check the string you are specifying, the current
bounds, or the column numbers on the command for
ISRE160 Disabled command - ’aaaaaaaa’ command
accuracy.
name has been disabled.
Explanation: The command called aaaaaaaa has been
ISRE165 *Bottom of data reached* - aaaaa bbbbbbbb
disabled by the DEFINE aaaaaaaa DISABLED command.
- not found. Press RFIND key to
Most likely this was done in order to prevent you from
continue from top.
causing damage to some appliction data. You cannot
enable the aaaaaaaa command. Explanation: The search string was not found by the
FIND command on any excluded or non-excluded
User Response: If you feel that you received this
lines, but part of the file has not been searched.
message in error, contact the authors of macros you are
using, or your system adminstrator. User Response: Press RFIND to search the beginning
of the file. You may want to check the string you are
Attempt to execute the aaaaaaaa command in a new edit
specifying, the current bounds, or the column numbers
session before issuing any commands. If it is disabled,
on the command for accuracy.
check for an initial macro to see if the command is
disabled there. Otherwise, check other macros you are
using for the DEFINE aaaaaaaa DISABLED command. ISRE166 * Top of data reached * - aaaaaaaa
bbbbbbbb - not found. Press RFIND key
to continue from bottom.
ISRE161 Enter character string - A character
string for FIND has not been entered (so Explanation: The search string was not found by the
* is invalid). FIND PREVIOUS command on any excluded or
non-excluded lines, but part of the file has not been
Explanation: A FIND command was entered using an
searched.
asterisk (″*″) as the first string operand (the FROM
string), but no previous FIND, CHANGE, SEEK, or User Response: Press RFIND to search from the end
EXCLUDE command was issued during this edit of the file. You may want to check the string you are
session. specifying, the current bounds, or the column numbers
on the command for accuracy.
User Response: Reissue the FIND command with a
valid FROM string. If you are trying to find an asterisk
character, put the asterisk in quotation marks.
ISRE167 Invalid parameters - The string will not ISRE173 Invalid EDIT/VIEW parm - When data
fit between the specified columns. set parameter is specified, do not code
DATAID, member or workstation file
Explanation: A string was specified on a FIND
name.
command that would not fit between the specified
boundary columns. Explanation: To invoke the EDIT or VIEW service,
you can specify either a data set name, DATAID, or
User Response: Reissue the FIND command with a
workstation file name. If a data set parameter is used, a
new string or different boundaries.
member name can be specified in the data set name. If
a DATAID is specified, the member parameter is used
ISRE168 Invalid hex string - The hex string must to specify a member name.
have an even number of hex digits.
User Response: Specify either data set, DATAID, or
Explanation: A hexadecimal string was specified on a workstation file.
FIND command that did not have an even number of
hexadecimal digits (0-9, A-F).
ISRE174 Invalid EDREC option - EDREC option
User Response: Reissue the FIND command with a is invalid.
valid hexadecimal string.
Explanation: Valid options for the EDREC service are
INIT, QUERY, PROCESS, CANCEL, and DEFER.
ISRE169 Invalid hex string - The hex string must
User Response: Specify a valid option for the EDREC
contain only hex digits (0-9,A-F).
service.
Explanation: A hexadecimal string was specified on a
FIND command that contained an invalid hexadecimal
ISRE175 Invalid CANCEL request - EDREC
digit.
CANCEL request issued before query
User Response: Reissue the FIND command with a for recovery pending.
valid hexadecimal string. Valid hexadecimal digits are
Explanation: The EDREC service must be invoked
0-9 and A-F.
with the QUERY option before being invoked with the
CANCEL option.
ISRE170 No members in data set - The PDS
User Response: Invoke EDREC with the QUERY
specified contains no members.
option before invoking EDREC with the CANCEL
Explanation: There are no members in the PDS option.
specified, so a member list cannot be displayed.
User Response: Select another data set to edit or ISRE176 Invalid command - Command aaaaaaaa is
specify a member name. undefined.
Explanation: There are no valid commands from this
ISRE171 I/O error - An I/O error occurred while panel.
reading the PDS directory.
User Response: Correct the command specified.
Explanation: An I/O error occurred while reading the
PDS directory to build a member list. The member list
ISRE177 Missing EDIT/VIEW parm - Either data
cannot be built.
set, DATAID or workstation file
User Response: Contact your system programmer. parameter is required.
Explanation: The EDIT or VIEW service was invoked
ISRE172 Open error - Open failed during without a data set, DATAID, or workstation file
member list processing. parameter.
Explanation: There was an error opening the PDS User Response: Specify either a data set, DATAID, or
directory. workstation file parameter.
ISRE189 Inconsistent parameter - Inconsistent ISRE194 Data parm omitted - You must specify a
parameters specified for the ’aaaaaaaa’ non-blank data parameter for the
command. LINE_BEFORE command.
Explanation: Inconsistent parameters were specified Explanation: The LINE_BEFORE command requires
for the given commands. that non-blank data be specified for the line being
added.
User Response: Contact the responsible programmer.
User Response: Contact the responsible programmer.
Programmer Response: Correct the parameter(s).
Programmer Response: Specify the data to be inserted
by the LINE_BEFORE command.
ISRE190 Too many parameters - Too many
parameters specified for LINE_BEFORE
command. Is data quoted? ISRE195 Too many parameters - Too many
parameters specified for the EXCLUDE
Explanation: The valid parameters for the
command.
LINE_BEFORE command are: the line pointer, the line
type, the data for the line, or a label or pointer to a line Explanation: The EXCLUDE command can contain
to be placed after the line pointed to by the line one string, one direction keyword, and one type
pointer. If the data for a line is not in quotes, the data keyword.
may be considered to be extra parameters.
User Response: Remove extraneous EXCLUDE
User Response: Contact the responsible programmer. parameters.
Programmer Response: Correct the parameter or put
the data in quotes. ISRE196 Inconsistent parameters - Inconsistent
keyword parameters specified for the
EXCLUDE command.
ISRE191 Invalid parameter - Extraneous or
invalid parameter was specified for Explanation: Two directional or two type keywords
LINE_BEFORE command. were specified.
Explanation: This is an informational message. An User Response: Remove one of the keywords.
incorrect line type may have been specified.
User Response: Contact the responsible programmer. ISRE197 Invalid parameter - Check for
misspelled keywords or too many
Programmer Response: Correct the LINE_BEFORE
bounds (numeric) parameters.
command.
Explanation: An invalid parameter has been entered
for the EXCLUDE command. Check the parameters.
ISRE192 Invalid parameter - Extraneous or
invalid parameter was specified for User Response: Correct the command.
LINE_BEFORE command.
Explanation: Either an extra parameter or an invalid ISRE198 Put string in quotes - Put quotes (’ ’)
parameter was specified for the LINE_BEFORE around the string of characters sought
command. for exclusion.
User Response: Contact the responsible programmer. Explanation: The EXCLUDE command contains more
than one string. Put the string in quotes.
Programmer Response: Correct the LINE_BEFORE
command. User Response: Enclose the string in single or double
quotation marks.
ISRE193 Line number omitted - Required relative
line number not specified (correctly) for ISRE199 Required string missing - The
LINE_BEFORE command. EXCLUDE command requires the
specification of a target string.
Explanation: A line number or a label must be
specified as the target for a LINE_BEFORE command. Explanation: A string was not specified for the
EXCLUDE command.
User Response: Contact the responsible programmer.
User Response: Add a target string to the EXCLUDE
Programmer Response: Correct the line number or
command.
label.
ISRE200 LMF Lock set - LMF Lock has been set ISRE212 aaaaaaaa bbbbbbbb changed - aaaaaaaa
to aaaaaaaa. bbbbbbbb - changed to cccccccc.
Explanation: No explanation available at this time. Explanation: This is an informational message.
ISRE205 Enter ’to’ string - Enter the replacement ISRE213 Invalid ’to’ string - The ’to’ string must
string of characters. be specific or equal length generic
string; not text.
Explanation: A FROM string was entered for the
CHANGE command but no TO string was entered. Explanation: When using the CHANGE edit
command and specifying a special string (picture (p’’),
User Response: Enter the TO string.
hex (x’’), text (t’’) or character (c’’)) as the source (or
’from’) string, the target (or ’to’) string cannot be a text
ISRE206 Enter a CHANGE command - The (t’’) string of a different length. For example, the
RCHANGE command only works when command
you have already used the CHANGE
CHANGE P’##’ T’ABCD’
command or when you have a CHANGE
command on the command line. is invalid because the target text string (T’ABCD’) is
not the same length as the source picture string.
Explanation: The RCHANGE command can only be
used after a CHANGE command has been entered or User Response: If you need to change the length of
when a CHANGE command is on the command line. the string, use a generic string as the target string, such
as:
User Response: Enter a CHANGE command.
CHANGE P’##’ ’ABCD’
ISRE207 Enter a CHANGE command - Command
with a ’to’ string must be entered before ISRE214 Invalid ’to’ string - The ’to’ picture
using the RCHANGE command. string must be the same length as the
’from’ string.
Explanation: The RCHANGE command has been used
following a FIND command. Enter a CHANGE Explanation: When using the edit CHANGE
command with a TO string to use the RCHANGE command and specifying a picture (p’’) string as both
command. the source (or ’from’) and target (or ’to’) string, the two
strings must be of the same length.
User Response: Enter a CHANGE command.
User Response: Modify the CHANGE command to
specify source and target strings of equal length, and
| ISRE210 COMPARE unavailable - The
retry the command.
| COMPARE command is not available
| from edit sessions created by the EDIF,
| VIIF, or EDIREC services when the ISRE215 aaaaaaaa bbbbbbbb cccccccc - bbbbbbbb
| NEXT or SESSION keyword is dddddddd - found aaaaaaaa times within
| specified. range eeeeeeee to ffffffff.
| Explanation: The COMPARE edit command was Explanation: This is an informational message.
| issued with the NEXT or SESSION keyword from an
| edit session which was initiated through the EDIF, VIIF,
ISRE216 aaaaaaaa bbbbbbbb found - Search for
| or EDIREC service. The COMPARE command is not
aaaaaaaa cccccccc from dddddddd to eeeeeeee
| supported from this environment because the EDIF and
was successful.
| VIIF interface edits data in storage, and the compare
| program requires a physical data set and a cataloged Explanation: This is an informational message.
| data set name.
User Response: If you want to compare the data, use ISRE217 aaaaaaaa bbbbbbbb changed - aaaaaaaa
the CREATE or REPLACE primary commands to save cccccccc - changed to dddddddd eeeeeeee
the data to a real data set and use the compare utility times from ffffffff to gggggggg.
(SuperC) to compare the data.
Explanation: This is an informational message.
Explanation: An edit CHANGE command was User Response: Review documentation for the
entered that specified a left boundary within the range MASKLINE command in ISPF Edit and Edit Macros
of the edit line numbers. A CHANGE command cannot
be used to change the sequence numbers of a file. The ISRE231 Invalid parameter - Extraneous or
minumum value that can be used as the left boundary invalid parameter was specified for
is aaaaaaaa. MASKLINE command.
User Response: Correct the left boundary specified on Explanation: An invalid MASKLINE command was
the CHANGE command and retry the request. entered.
User Response: Review documentation for the
ISRE224 Invalid right boundary - ’aaaaaaaa’ is the MASKLINE command in ISPF Edit and Edit Macros
last column that is not part of a
sequence number.
Explanation: An edit CHANGE command was
entered that specified a right boundary within the
range of the edit line numbers. A CHANGE command
ISRE237 Data parm omitted – Required data Explanation: An invalid INSERT command was
parameter not specified for the entered.
TABSLINE command.
User Response: Review documentation for the
Explanation: An invalid TABSLINE command was INSERT command in ISPF Edit and Edit Macros
entered.
User Response: Review documentation for the ISRE243 Required parm omitted – Required line
TABSLINE command in ISPF Edit and Edit Macros pointer parameter not specified for the
INSERT command.
Explanation: An invalid INSERT command was
entered.
User Response: Review documentation for the MOVE User Response: If you recently converted to a new
command in ISPF Edit and Edit Macros release of ISPF, try to process the recovery using the
old release. If this does not work, contact your system
programmer.
ISRE272 Invalid parameter - An extraneous or
invalid parameter was specified for the System Programmer Response: Contact IBM support.
MOVE command.
Explanation: An invalid MOVE command was | ISRE278 REPLACE not allowed - REPLACE is
entered. | not allowed on members of SCLM
| controlled data sets, use the SREPLACE
User Response: Review documentation for the MOVE | command from within SCLM Edit to
command in ISPF Edit and Edit Macros | replace an SCLM controlled member.
| Explanation: The member you are trying to replace is
ISRE273 Too many parameters - Too many | SCLM controlled.
parameters specified for the LINENUM
command. | User Response: Update the member using the SCLM
| editor.
Explanation: An invalid LINENUM command was
entered.
ISRE280 Too many parameters - Too many
User Response: Review documentation for the parameters specified for the CREATE
LINENUM command in ISPF Edit and Edit Macros command.
Explanation: An invalid CREATE command was
ISRE274 Invalid line number - Relative line entered.
number specified in ″aaaaaaaa″ command
does not exist. User Response: Review documentation for the
CREATE command in ISPF Edit and Edit Macros
Explanation: The command could not be executed
because the line number entered is invalid.
ISRE281 Parameter unrecognized - Extraneous or
User Response: Enter the command with a valid line invalid parameter was specified for the
number. CREATE command.
Explanation: An invalid CREATE command was
ISRE275 Invalid aaaaaaaa - Specification for entered.
LINENUM command exceeds actual
length of member. User Response: Review documentation for the
CREATE command in ISPF Edit and Edit Macros
Explanation: An invalid LINENUM command was
entered.
User Response: Review documentation for the
LINENUM command in ISPF Edit and Edit Macros
ISRE283 Too many parameters - Too many ISRE292 Invalid parameter - Check for
parameters specified for the LINE misspelled keywords or too many
command. Is data quoted? bounds (numeric) parameters.
Explanation: An invalid LINE command was entered. Explanation: An invalid parameter has been entered.
User Response: Review documentation for the LINE User Response: Correct the invalid parameter.
command in ISPF Edit and Edit Macros
ISRE293 Put string in quotes - Put quotes (’ ’)
ISRE284 Unrecognized parameter - Extraneous or around the source and target character
invalid parameter was specified for the strings.
LINE command.
Explanation: In order for the command to run, the
Explanation: An invalid LINE command was entered. source and target character strings must be enclosed in
single quotation marks.
User Response: Review documentation for the LINE
command in ISPF Edit and Edit Macros User Response: Enclose both the source and target
character strings in single quotation marks.
ISRE285 Invalid parameter - Extraneous or
invalid parameter was specified for the ISRE294 Required string missing - The CHANGE
LINE command. command requires the specification of a
target string.
Explanation: An invalid LINE command was entered.
Explanation: An invalid CHANGE command was
User Response: Review documentation for the LINE
entered.
command in ISPF Edit and Edit Macros
User Response: Review documentation for the
CHANGE command in ISPF Edit and Edit Macros
ISRE286 Line pointer invalid - Required line
pointer not correctly specified for LINE
command ISRE295 Required string missing - The CHANGE
command requires a second string of
Explanation: An invalid LINE command was entered.
source data.
User Response: Review documentation for the LINE
Explanation: An invalid CHANGE command was
command in ISPF Edit and Edit Macros
entered.
User Response: Review documentation for the
ISRE287 Data parm omitted - Required data
CHANGE command in ISPF Edit and Edit Macros
parameter not specified for LINE
command.
ISRE296 Too many parameters - You may specify:
Explanation: An invalid LINE command was entered.
COPY member name or data set name
User Response: Review documentation for the LINE AFTER aaaaaaaa
command in ISPF Edit and Edit Macros
Explanation: An invalid command has been entered.
User Response: Review documentation for the
ISRE290 Too many parameters - Too many
command entered in ISPF Edit and Edit Macros.
parameters specified for the CHANGE
command.
Explanation: An invalid CHANGE command was
entered.
ISRE319 UNDO not available - UNDO not ISRE324 Shift type required - ’(’-cols left; ’)’-cols
available when both SETUNDO and right; ’<’-data left; or ’>’-data right
RECOVERY are OFF or suspended.
Explanation: A SHIFT edit macro command was
Explanation: The UNDO command is not available issued without a shift type. The shift type, (, ), <, or >,
because both SETUNDO STORAGE and RECOVERY and a line pointer must be specified; a shift amount is
are off or suspended. optional.
User Response: Turn Recovery or Setundo on Programmer Response: Change the SHIFT command
(RECOVERY ON or SETUNDO STORAGE). If they are in the macro to include a shift type. Valid shift types
already on, turn them off and back on again. are:
( Left column shift
) Right column shift
ISRE320 Too many parameters - Too many
< Left data shift
parameters specified for the SHIFT
> Right data shift.
command.
Explanation: A SHIFT edit macro command was
ISRE325 Invalid line pointer - The line pointer
issued with too many parameters. A maximum of 3
given to the SHIFT command is invalid.
parameters is allowed: shift type, line pointer, and shift
amount. Explanation: A SHIFT edit macro command was
issued an invalid line pointer. The line pointer must be
Programmer Response: Change the SHIFT command
a valid, existing line number, or a valid, existing label.
in the macro to have a maximum of three parameters
(shift type, line pointer and shift amount). User Response: Correct the SHIFT command in the
macro to reference a valid line. The line pointer can be
either a label or a relative line number.
ISRE321 Invalid parameter - An invalid
parameter was specified for the SHIFT Verify that the line number or label exists. It is possible
command. that deletions or label changes have caused the line that
is referenced by the macro to be logically renumbered
Explanation: A SHIFT edit macro command was
or relabeled.
issued with at least one invalid parameter. The shift
type and a line pointer must be specified. A shift
amount is optional. ISRE327 Probable label error - ″aaaaaaaa″
recognized as invalid or undefined label
Programmer Response: Change the SHIFT command
in ″bbbbbbbb″ cmd.
in the macro to have a maximum of three parameters
(shift type, line pointer and shift amount). Explanation: The bbbbbbbb command has an operand
that looks like a label, but either the label does not exist
in the file, or it is syntactically incorrect.
ISRE322 Invalid parameter - An invalid
parameter was specified for the SHIFT Programmer Response: Correct the command or the
command. macro to insure that it is using a valid, existing label.
Labels may not have numbers or non-alphabetic
Explanation: A SHIFT edit macro command was
characters in them except for the period at the
issued with at least one invalid parameter. The shift
beginning.
type and a line pointer must be specified. A shift
amount is optional.
ISRE328 System table error - Unknown
Programmer Response: Change the SHIFT command
parameter type defined in edit
in the macro to have a maximum of three parameters
command definition table (TED).
(shift type, line pointer and shift amount).
Explanation: An error has occurred due to an
incorrectly defined internal PDF table.
ISRE323 Line pointer required - A line pointer
parameter must be specified for the User Response: If this problem is reproducible,
SHIFT command. contact IBM support.
Explanation: A SHIFT edit macro command was
issued without a line pointer value. The shift type and ISRE329 System table error - A message ID is
a line pointer must be specified, a shift amount is missing from the edit command
optional. definition table (TED).
Programmer Response: Change the SHIFT command Explanation: An error has occurred due to an
in the macro to include a line pointer. incorrectly defined internal PDF table.
ISRE359 Invalid column range - The aaaaaaaa ISRE365 *Bottom of data reached* - aaaaa bbbbbbbb
column range attempts a search beyond - not found. Press RFIND key to
the last data column. continue from top.
Explanation: An EXCLUDE command in an edit Explanation: The search string was not found by the
macro attempted to find a string outside of the current FIND or EXCLUDE command on any excluded or
data columns. non-excluded lines, but part of the file has not been
searched.
Programmer Response: Change the boundary
conditions so that the string fits within the specified User Response: Press RFIND to search the beginning
bounds. Use the DATA_WIDTH command to search the of the file. You may want to check the string you are
maximum data column. specifying, the current bounds, or the column numbers
on the command for accuracy.
ISRE361 Enter character string - A char string for
FIND/EXCLUDE has not been entered ISRE366 * Top of data reached * - aaaaa bbbbbbbb -
(so * is invalid). not found. Press RFIND key to continue
from bottom.
Explanation: A FIND or EXCLUDE command was
entered using an asterisk (*) as the first string operand Explanation: The search string was not found by the
(the FROM string), but no previous FIND, CHANGE, FIND PREVIOUS or EXCLUDE PREVIOUS command
SEEK, or EXCLUDE command was issued during this on any excluded or non-excluded lines, but part of the
edit session. file has not been searched.
User Response: Reissue the FIND or EXCLUDE User Response: Press RFIND to search from the end
command with a valid FROM string. If you are trying of the file. You may want to check the string you are
to find or exclude an asterisk character, put the asterisk specifying, the current bounds, or the column numbers
in quotation marks. on the command for accuracy.
ISRE367 Inconsistent parameters - The string will ISRE373 Required parm omitted - Required
not fit between the specified columns. aaaaaaaa parm omitted or invalid for the
TFLOW command.
Explanation: A string was specified on a FIND or
EXCLUDE command that would not fit between the Explanation: An ISREDIT TFLOW edit macro
specified boundary columns. command was incorrectly issued from an edit macro.
Most likely, the line pointer operand is invalid.
User Response: Reissue the FIND or EXCLUDE
command with a new string or different boundaries. User Response: Contact the responsible programmer.
Programmer Response: Correct the ISREDIT TFLOW
ISRE368 Invalid hex string - The hex string must command to have a valid line pointer and, optionally, a
have an even number of hex digits. valid column number.
Explanation: A hexadecimal string was specified on a
FIND or EXCLUDE command that did not have an ISRE374 Invalid aaaaaaaa - The aaaaaaaa given to
even number of hexadecimal digits (0-9, A-F). the TFLOW command is invalid.
User Response: Reissue the FIND or EXCLUDE Explanation: An ISREDIT TFLOW edit macro
command with a valid hexadecimal string. command was incorrectly issued from an edit macro.
The line pointer references a line that does not exist in
the edit data.
ISRE369 Invalid hex string - The hex string must
contain only hex digits (0-9,A-F). User Response: Contact the responsible programmer.
Explanation: A hexadecimal string was specified on a Programmer Response: Correct the edit macro to
FIND or EXCLUDE command that contained an invalid insure that the line number exists in the edit data
hexadecimal digits. before it issues the TFLOW command.
User Response: Reissue the FIND or EXCLUDE
command with a valid hexadecimal string. Valid ISRE375 Too many parameters - Too many
hexadecimal digits are 0-9 and A-F. parameters specified for TSPLIT
command.
ISRE370 Too many parameters - Too many Explanation: An ISREDIT TSPLIT edit macro
parameters specified for TFLOW command was incorrectly issued from an edit macro.
command. The TSPLIT command allows only 2 parameters: a line
pointer and a column number.
Explanation: An ISREDIT TFLOW edit macro
command was incorrectly issued from an edit macro. User Response: Contact the responsible programmer.
The TFLOW command allows only 2 parameters: a line
Programmer Response: Correct the ISREDIT TSPLIT
pointer and a column number.
command to have only a line pointer and a column
User Response: Contact the responsible programmer. number.
Programmer Response: Correct the ISREDIT TFLOW
command to have only a line pointer and, optionally, a ISRE376 Invalid parameter - Extraneous or
column number. invalid parameter was specified for
TSPLIT command.
ISRE371 Invalid parameter - Extraneous or Explanation: An ISREDIT TSPLIT edit macro
invalid parameter was specified for command was incorrectly issued from an edit macro.
TFLOW command. The line pointer or column number is invalid.
Explanation: An ISREDIT TFLOW edit macro User Response: Contact the responsible programmer.
command was incorrectly issued from an edit macro.
Programmer Response: Correct the ISREDIT TSPLIT
Possibly the line pointer was correctly specified, but the
command to a valid line pointer and column number.
column number was invalid.
User Response: Contact the responsible programmer.
ISRE377 Invalid aaaaaaaa - The aaaaaaaa given to
Programmer Response: Correct the ISREDIT TFLOW the TSPLIT command is invalid.
command to have a line pointer and, optionally, a valid
Explanation: An ISREDIT TSPLIT edit macro
column number.
command was incorrectly issued from an edit macro.
The line pointer refers to a line that is not in the edit
data.
User Response: Contact the responsible programmer.
ISRE387 Error creating data ID - An error was ISRE393 Invalid parameter - Extraneous or
encountered in LMINIT service, trying invalid parameter was specified for
to generate a data ID. (scroll) RIGHT command.
Explanation: An internal error occurred trying to Explanation: An incorrect parameter was specified for
create a data ID for edit macro execution. the RIGHT command.
System Programmer Response: Contact IBM support. User Response: Review documentation for the RIGHT
command. For further information on the RIGHT
command, refer to ISPF Edit and Edit Macros
ISRE388 Too many parameters - Too many
parameters specified for the (scroll) UP
command. ISRE394 Too many parameters - Too many
parameters specified for the (scroll)
Explanation: The UP command was specified with too
LEFT command.
many parameters.
Explanation: Too many parameters were specified for
User Response: Reissue the UP command using only
the LEFT command.
one parameter (MAX, DATA, HALF, PAGE, CSR, or a
number). User Response: Review documentation for the LEFT
command. For further information on the LEFT
command, refer to ISPF Edit and Edit Macros
ISRE389 Inconsistent parameters - ″aaaaaaaa″ and
″bbbbbbbb″ cannot both be specified for
(scroll) UP command. ISRE395 Inconsistent parameters - ″aaaaaaaa″ and
″bbbbbbbb″ cannot both be specified for
Explanation: The UP command was specified with
(scroll) LEFT command.
invalid parameters.
Explanation: Both parameters cannot be specified for
User Response: Reissue the UP command using only
the LEFT command.
one parameter (MAX, DATA, HALF, PAGE, CSR, or a
number). User Response: Review documentation for the LEFT
command. For further information on the LEFT
command, refer to ISPF Edit and Edit Macros
ISRE390 Invalid parameter - Extraneous or
invalid parameter was specified for
(scroll) UP command. ISRE396 Invalid parameter - Extraneous or
invalid parameter was specified for
Explanation: An invalid parameter was used with the
(scroll) LEFT command.
UP command.
Explanation: A parameter was incorrect for the LEFT
User Response: Review documentation for the UP
command.
command. For further information on the UP
command, refer to ISPF Edit and Edit Macros User Response: Review documentation for the LEFT
command. For further information on the LEFT
command, refer to ISPF Edit and Edit Macros
ISRE391 Too many parameters - Too many
parameters specified for the (scroll)
RIGHT command. ISRE397 Too many parameters - Too many
parameters specified for the (scroll)
Explanation: There were too many parameters
DOWN command.
specified for the RIGHT command.
Explanation: Too many parameters were specified for
User Response: Review documentation for the RIGHT
the DOWN command.
command. For further information on the RIGHT
command, refer to ISPF Edit and Edit Macros User Response: Review documentation for the DOWN
command. For further information on the DOWN
command, refer to ISPF Edit and Edit Macros
ISRE392 Inconsistent parameters - ″aaaaaaaa″ and
″bbbbbbbb″ cannot both be specified for
(scroll) RIGHT command. ISRE398 Inconsistent parameters - ″aaaaaaaa″ and
″bbbbbbbb″ cannot both be specified for
Explanation: Both parameters cannot be specified for
(scroll) DOWN command.
the RIGHT command.
Explanation: Both parameters cannot be specified for
User Response: Review documentation for the RIGHT
the DOWN command.
command. For further information on the RIGHT
command, refer to ISPF Edit and Edit Macros User Response: Review documentation for the DOWN
ISRE410 Requested line(s) copied - Lines aaaaaaaa ISRE417 Data set replaced - aaaaaaaa replaced by
- bbbbbbbb of member cccccccc were specified data.
copied.
Explanation: This is an informational message. The
Explanation: This is an informational message. The data set is sequential and has been replaced by the data
requested lines were copied. that was specified.
ISRE411 Requested line(s) copied - Lines aaaaaaaa ISRE418 File attributes changed - Reallocation
through bbbbbbbb of data set were after abend revealed different file
copied. attributes. Data not saved.
Explanation: This is an informational message. The Explanation: The data set file attributes have changed
requested lines were copied. and no data has been saved.
User Response: Check for a cause for the abend and
ISRE412 Requested line(s) copied - Lines aaaaaaaa the data set attributes.
through bbbbbbbb of data set were
Problem Determination: An abend occurred and the
copied.
reallocation of the data set contains different file
Explanation: This is an informational message. The attributes.
requested lines were copied.
ISRE419 Data set in use - Reallocation after
ISRE413 Requested line(s) copied - Lines aaaaaaaa abend failed. Cancel the edit session or
- bbbbbbbb of member cccccccc were use the extended CREATE or REPLACE
copied. command to save the member to another
data set.
Explanation: This is an informational message. The
requested lines were copied. Explanation: The data set is still in use after the
abend. To save the data, use the extended CREATE or
REPLACE command to save the data into another data
ISRE414 No lines found in range - No lines were
set. If you do not want to save the data, cancel the edit
found within the specified range of
session.
sequence numbers.
User Response: Either cancel the edit session (which
Explanation: The range specified contained no lines
will not save your data), or use the extended CREATE
for the COPY command.
or REPLACE command to save the data.
User Response: Verify the range for the lines and
reenter the command.
ISRE420 Missing parameter - Variable name
parameter required for the DATAID
ISRE415 Enter member name - A member list is command.
not supported with the aaaaaaaa
Explanation: The DATAID assignment statement is
command.
missing the required variable name for the data set
Explanation: This is an informational message. A currently allocated for editing.
member list is not supported for this command.
User Response: Correct the DATAID assignment
statement so that it includes the required variable name
ISRE416 aaaaaaaa not printed - aaaaaaaa bbbbbbbb for the data set currently allocated for editing.
but error encountered opening DCB for
input for printing.
ISRE421 Missing parameter - Variable name
Explanation: The member was not printed due to an parameter required for MEMBER
error in opening the DCB for print. command.
User Response: Contact your system programmer. Explanation: The Member assignment statement is
missing the required variable name for the member
System Programmer Response: Check the data set currently being edited.
member to see why the DCB did not open.
User Response: Correct the Member assignment
statement so that it includes the required variable name
for the member currently being edited.
ISRE422 Missing parameter - Variable name ISRE427 Invalid specification - GET assignment
parameter required for LRECL type unrecognized for the LRECL
command. command.
Explanation: The LRECL assignment statement is Explanation: Either the LRECL assignment statement
missing the required variable name for the maximum contains an invalid variable name or a parameter is
space in bytes available for data. missing.
User Response: Correct the LRECL assignment User Response: Verify that the LRECL assignment
statement to include the required variable name for the statement contains no syntax errors or missing
maximum space allowed in bytes for data. parameters.
ISRE423 Missing parameter - At least one ISRE428 Invalid specification - GET assignment
variable name parameter required for type unrecognized for the
FLOW_COUNTS command. FLOW_COUNTS command.
Explanation: The FLOW_COUNTS assignment Explanation: Either the FLOW_COUNTS assignment
statement is missing a variable name for the most statement contains an invalid variable name or a
recently entered TFLOW command. At least one parameter is missing.
FLOW_COUNTS assignment statement variable must
User Response: Verify that the FLOW_COUNTS
be coded.
assignment statement contains no syntax errors or
User Response: Correct the FLOW_COUNTS missing parameters.
assignment statement so that it contains at least one
variable name parameter.
ISRE429 Invalid specification - GET assignment
type unrecognized for the
ISRE424 Missing parameter - At least one EXCLUDE_COUNTS command.
variable name parameter required for
Explanation: Either the EXCLUDE_COUNTS
EXCLUDE_COUNTS command.
assignment statement contains an invalid variable name
Explanation: The EXCLUDE_COUNTS assignment or a parameter is missing.
statement is missing a variable name for the most
User Response: Verify that the EXCLUDE_COUNTS
recently processed EXCLUDE command. At least one
assignment statement contains no syntax errors or
EXCLUDE_COUNTS assignment statement variable
missing parameters.
must be coded.
User Response: Correct the EXCLUDE_COUNTS
ISRE430 Invalid keyword - Either X (excluded) or
assignment statement so that it contains at least one
NX (non-excluded) can be specified.
variable name parameter.
Explanation: The SORT command only allows X or
NX to be specified. You cannot use both in the same
ISRE425 Invalid specification - GET assignment
command.
type unrecognized for the DATAID
command. User Response: Change the SORT command to use
either X (excluded) or NX (non-excluded).
Explanation: Either the DATAID assignment statement
contains an invalid variable name or a parameter is
missing. ISRE431 Invalid SORT parameter - The only
valid parameters are X, NX, A, D and/or
User Response: Verify that the DATAID assignment
aaaaaaaa range.
statment contains no syntax errors or missing
parameters. Explanation: The SORT parameter that was entered is
invalid.
ISRE426 Invalid specification - GET assignment User Response: Correct the SORT parameter. The
type unrecognized for the MEMBER valid SORT parameters are X, NX, A, D, or a valid label
command. range.
Explanation: Either the MEMBER assignment
statement contains an invalid variable name or a ISRE432 Too many sort fields - A maximum of 5
parameter is missing. sort fields may be specified.
User Response: Verify that the MEMBER assignment Explanation: Too many sort field parameters have
statement contains no syntax errors or missing been entered. SORT allows a maximum of five sort
parameters. fields.
ISRE444 Invalid label specified - Label aaaaaaaa ISRE449 LOGIC not supported - HILITE LOGIC
specified in SORT command does not is only supported for languages BOOK,
exist. C, DTL, OTHER, PASCAL, PLI, REXX,
and SKEL.
Explanation: The SORT command was given a label
that does not exist. Explanation: HILITE LOGIC is only supported for
languages BOOK, C, DTL, OTHER, PASCAL, PLI,
User Response: Correct the sort label to a label that
REXX, and SKEL. The current language does not
exists.
support logic highlighting and thus does not allow the
LOGIC operand on the HILITE command.
ISRE445 Sort label range invalid - Specify exactly
two labels to indicate the range of lines
ISRE450 DEFINE name invalid - The name
to sort.
specified in the DEFINE command is
Explanation: One of the label ranges that was entered greater than 8 characters.
does not exist or is invalid.
Explanation: A name was specified on the DEFINE
User Response: Verify that the labels being used for command that was too long. Names on the DEFINE
the SORT command exist. Correct the label that is command can be no longer than 8 characters.
invalid.
User Response: Reissue the DEFINE command with a
valid name.
ISRE446 Inconsistent parameters - ’aaaaaaaa’ and
’bbbbbbbb’ cannot both be specified for
ISRE451 DEFINE syntax invalid - Specify:
the HILITE command.
DEFINE new-alias-name ALIAS
Explanation: The HILITE command was specified alias-of-name.
with an invalid combination of parameters. You may
Explanation: Invalid syntax was detected on an edit
not specify ON and OFF together, and you may not
macro DEFINE command that was issued to define an
specify LOGIC, IFLOGIC, and DOLOGIC together.
alias. The correct syntax is:
User Response: Remove the incorrect parameter and
DEFINE new-alias-name ALIAS alias-of-name.
reissue the HILITE command.
User Response: Reissue the command using the
syntax described above.
ISRE447 Invalid parameter - Valid parameters for
the HILITE command are: ON, OFF,
PAREN, LOGIC, IFLOGIC, DOLOGIC, ISRE452 DEFINE is invalid - A macro may not be
SEARCH, CURSOR, FIND, RESET, defined to override macro only
AUTO, DISABLED or a valid language commands.
name.
Explanation: An edit macro tried to override a macro
Explanation: The valid HILITE parameters are listed only command. The DEFINE edit macro command
above. To change the HILITE settings through a menu cannot be used in a macro to override commands that
interface, enter the HILITE command with no are edit macro commands and not interactive primary
parameters. commands.
User Response: Reissue the HILITE command with Programmer Response: Remove or change the
valid parameters. DEFINE command. If you want to define a macro
name, choose another name for the macro.
ISRE448 Search not allowed - HILITE SEARCH
is only allowed when HILITE is on and ISRE453 Command not found - ″aaaaaaaa″ is not
the language is not DEFAULT. an edit command or macro.
Explanation: HILITE SEARCH is only supported Explanation: A command was issued in the editor that
when highlighting is on and the language being edited is not a valid edit command. Valid edit commands may
is not DEFAULT. be:
v Built-in edit commands
User Response: Use HILITE SEARCH ON to turn
v Macro only commands (valid only in edit macros)
highlighting on and use the SEARCH operand. If this is
v CLISTs in SYSPROC
unsuccessful, use the PROFILE command to determine
v REXX EXECs in SYSPROC or SYSEXEC
the language being used by the edit highlighting. If the
Explanation: A severe error (return code 20) has been Programmer Response: Change the NUMBER
received using the SETUNDO macro command. The command to specify the proper parameters. Refer to
assignment type used with the command is invalid. ISPF Edit and Edit Macros for editor command syntax.
ISRE492 Missing parameter - Variable name User Response: Contact the responsible programmer.
parameter required for RANGE_CMD
Programmer Response: Change the MACRO_LEVEL
command.
command to specify the proper parameters. Refer to
Explanation: The RANGE_CMD edit macro command ISPF Edit and Edit Macros for editor command syntax.
was invoked, but no variable name was specified to
indicate where the editor should put the value of the
ISRE497 Invalid specification - GET assignment
current setting.
type unrecognized for the
User Response: Contact the responsible programmer. RANGE_CMD command.
Programmer Response: Change the RANGE_CMD Explanation: The PDF editor encountered an edit
command to specify the proper parameters. Refer to macro statement involving the command
ISPF Edit and Edit Macros for editor command syntax. RANGE_CMD, 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
ISRE493 Missing parameter - Variable name into a dialog-specified variable). A GET type request is
parameter required for the only valid request type for the RANGE_CMD
DATA_CHANGED command. macro command.
Explanation: The DATA_CHANGED edit macro User Response: Contact the responsible programmer.
command was invoked, but no variable name was
specified to indicate where the editor should put the Programmer Response: Change the RANGE_CMD
value of the current setting. command to specify the proper parameters. Refer to
ISPF Edit and Edit Macros for editor command syntax.
User Response: Contact the responsible programmer.
Programmer Response: Change the
DATA_CHANGED command to specify the proper
ISRE531 Invalid NUMBER cmd parm - Valid ISRE534 Invalid parameter - ON or OFF are the
NUMBER parms: ON/OFF, only valid parameters for the
STD/NOSTD, NOCOB/COBOL, AUTOLIST command.
NODISPL/DISPLAY
Explanation: The AUTOLIST edit command was
Explanation: A parameter was specified to the edit invoked with a parameter other than ON or OFF.
command NUMBER other than one of the allowed
User Response: Correct the parameters to the
values (ON, OFF, STD, NOSTD, COBOL, NOCOB,
AUTOLIST command and reissue the command or
NODISPL and DISPLAY).
rerun the macro. Refer to ISPF Edit and Edit Macros for
User Response: Correct the parameters to the editor command syntax. If the macro was supplied by
NUMBER command and reissue the command or rerun someone else, contact the writer for assistance in
the macro. Refer to ISPF Edit and Edit Macros for editor correcting the error.
command syntax. If the macro was supplied by
Programmer Response: Change the macro to correct
someone else, contact the writer for assistance in
the parameters to the AUTOLIST command. Refer to
correcting the error.
ISPF Edit and Edit Macros for editor command syntax.
Programmer Response: Change the macro to correct
the parameters to the NUMBER command. Refer to
ISRE536 Too many parameters - Only ON, OFF,
ISPF Edit and Edit Macros for editor command syntax.
WARN and NOWARN are valid for the
RECOVERY command.
ISRE532 Inconsistent parameters - ″aaaaaaaa″ and
Explanation: More parameters were specified to the
″bbbbbbbb″ cannot both be specified for
edit command RECOVERY then the allowed maximum.
NUMBER command.
User Response: Correct the parameters to the
Explanation: Mutually exclusive parameters (aaaaaaaa
RECOVERY command and reissue the command or
and bbbbbbbb) were specified on invocation of the
rerun the macro. Refer to ISPF Edit and Edit Macros for
NUMBER command.
editor command syntax. If the macro was supplied by
User Response: Change the command to specify the someone else, contact the writer for assistance in
proper parameter for the NUMBER command and correcting the error.
reissue the command or rerun the macro. Refer to ISPF
Programmer Response: Change the macro to correct
Edit and Edit Macros for editor command syntax. If the
the parameters to the RECOVERY command. Refer to
macro was supplied by someone else, contact the writer
ISPF Edit and Edit Macros for editor command syntax.
for assistance in correcting the error.
Programmer Response: Change the macro to specify
ISRE537 Invalid parameter - Only ON, OFF,
the proper parameters to the NUMBER command.
WARN and NOWARN are valid for the
Refer to ISPF Edit and Edit Macros for editor command
RECOVERY command.
syntax.
Explanation: A parameter was specified to the edit
command RECOVERY other than one of the allowed
ISRE533 Too many parameters - ON or OFF are
values (ON, OFF, WARN, and NOWARN).
the only valid parameters for the
AUTOLIST command. User Response: Correct the parameters to the
RECOVERY command and reissue the command or
Explanation: The AUTOLIST edit command was
rerun the macro. Refer to ISPF Edit and Edit Macros for
invoked with more than one parameter.
editor command syntax. If the macro was supplied by
User Response: Correct the parameters to the someone else, contact the writer for assistance in
AUTOLIST command and reissue the command or correcting the error.
rerun the macro. Refer to ISPF Edit and Edit Macros for
Programmer Response: Change the macro to correct
editor command syntax. If the macro was supplied by
the parameters to the RECOVERY command. Refer to
someone else, contact the writer for assistance in
ISPF Edit and Edit Macros for editor command syntax.
correcting the error.
Programmer Response: Change the macro to correct
ISRE538 Inconsistent parameters - ″aaaaaaaa″ and
the parameters to the AUTOLIST command. Refer to
″bbbbbbbb″ cannot both be specified for
ISPF Edit and Edit Macros for editor command syntax.
RECOVERY command.
Explanation: Mutually exclusive parameters (aaaaaaaa
and bbbbbbbb) were specified on invocation of the
RECOVERY command.
User Response: Change the command to specify the
ISRE541 Invalid parameter - ON, DISPLAY, STD, ISRE545 LRECL not large enough - LRECL is not
COBOL are the only valid RENUM large enough for COBOL and standard
parameters. numbers.
Explanation: The PDF edit RENUM command was Explanation: The Edit command equivalent to
invoked with a parameter other than ON, DISPLAY, NUMBER ON STD COBOL was entered, which
STD, or COBOL. requests that the editor maintain both standard line
numbers and COBOL line numbers. This requires that
User Response: Change the command to specify the
the record length of the data set be at least 15. The data
proper parameters for the RENUM command and
set you are editing is less than 15 bytes wide, making it
reissue the command or rerun the macro. Refer to ISPF
impossible for the editor to maintain both types of line
Edit and Edit Macros for editor command syntax. If the
numbers. The editor will maintain COBOL line
macro was supplied by someone else, contact the writer
numbers only.
for assistance in correcting the error.
User Response: If COBOL line numbers only are
Programmer Response: Change the macro to specify
sufficient for your needs, no action is required. If not,
the proper parameters for the RENUM command. Refer
issue the NUM ON STD, NUM OFF, or UNNUM
to ISPF Edit and Edit Macros for editor command
command to set the line numbering to meet your
syntax.
needs.
ISRE576 Invalid profile parm - Line-count, ISRE583 Not in STATS mode - VERSION or
profile-name, or LOCK/UNLOCK are LEVEL commands are valid only when
the only valid parameters. you are in STATS mode.
Explanation: An invalid parameter was specified on Explanation: The VERSION or LEVEL commands are
the PROFILE command. The valid parameters are only valid when in stats mode.
LOCK, UNLOCK, a profile name, or the number of
User Response: Specify STATS ON to get stats for a
profile lines to display.
member of a partitioned data set. The STATS command
User Response: Use valid parameters on the PROFILE cannot be specified for sequential data sets.
command.
ISRE584 Invalid in hex mode - TE is not valid ISRE590 Required parms missing - Specify:
when you are in hexadecimal mode. DELETE ALL X/NX or DELETE X/NX .A
.B or DELETE ALL .A .B
Explanation: The TE line command is not valid in
hexadecimal mode. Explanation: Not enough parameters were specified
on the DELETE command.
User Response: Specify HEX OFF to turn off
hexadecimal mode before using the TE line command. User Response: Ensure that parameters are specified
on the DELETE command. The parameters must
include a range. For example:
ISRE585 Invalid command - Hexadecimal mode
v ALL
is not valid when you are in text-entry
v .A .B
mode.
v ALL .A .B
Explanation: Hexadecimal mode cannot be entered
Unless ALL .A .B is specified, one of the parameters
while in text-entry mode.
must be X or NX to indicate how excluded lines are to
User Response: Press Enter to exit text-entry mode be processed.
before entering the HEX command.
ISRE591 Delete parameter omitted - If ALL is
ISRE586 Too many parameters - Valid parameters specified, then X, NX, or a label range is
for DELETE command are: ALL X/NX, required.
lptr-1, lptr-2.
Explanation: When the ALL parameter is specified on
Explanation: Too many parameters were specified on the DELETE command, one of the following
the DELETE command. parameters must be specified: X, NX, or a label range.
User Response: Specify the correct number of User Response: Update the command to specify one
parameters for the DELETE command. of the missing parameters.
ISRE588 Invalid parameter - Valid parameters for ISRE593 No lines deleted - No excluded lines
DELETE command are: ALL X/NX, existed to delete.
lptr-1, lptr-2.
Explanation: The X parameter was specified on the
Explanation: An invalid parameter was specified for DELETE command but no lines were excluded.
the DELETE command.
User Response: Exclude the lines to be deleted prior
User Response: Ensure that the DELETE command is to issuing a DELETE command with the X parameter.
using valid parameter names.
ISRE594 No lines deleted - No non-excluded
ISRE589 Invalid parameter - Valid parameters for lines existed to delete.
DELETE command are: ALL X/NX and a
Explanation: The NX parameter was specified on the
label range.
DELETE command but all lines had been excluded.
Explanation: An invalid parameter was specified for
User Response: Do not exclude the lines to be deleted
the DELETE command.
prior to issuing a DELETE command with the NX
User Response: Ensure that the DELETE command is parameter.
using valid parameter names.
ISRE644 Files Compared - No differences were ISRE723 Member name is required - In a macro a
found, but some differences may exist member name or a data set name and
which are not shown. Options were member are required by aaaaaaaa
selected on the Edit Compare Settings command
panel that may cause some data to be
Explanation: The member name was omitted.
ignored during the comparison. This file
was compared to ’aaa(56)’. User Response: Specify a valid member name.
Explanation: The COMPARE edit command detected
no differences. However, options were selected on the ISRE724 Too many parameters - You may specify
Edit Compare Settings Panel that filtered the input to a member name or a data set name and
the compare program. As a result, some differences member, and aaaaaaaa range on a
may have been ignored during the compare and may CREATE command.
not be highlighted in the editor.
Explanation: Too many parameters were specified.
ISRE648 Files compared - No differences were User Response: Remove the invalid parameter.
found, but some differences may not be
shown because SuperC ″don’t process″ ISRE725 Invalid parameter - You may specify a
options were selected on the Edit member name or a data set name and
Compare Settings panel. This file was member and aaaaaaaa range on a
compared to ’aaa(56)’. CREATE command.
Explanation: The COMPARE edit command detected Explanation: An invalid parameter was specified.
no differences. However, SuperC ″don’t process″
options were selected on the Edit Compare Settings User Response: Remove the invalid parameter and try
Panel. As a result, some differences may have been the CREATE command again.
ignored during the compare and may not be
highlighted in the editor. ISRE728 Too many parameters - You may specify
a member name or a data set name and
ISRE720 Too many parameters - You may specify member and an aaaaaaaa range with
a member name and AFTER or BEFORE REPLACE command
aaaaaaaa with MOVE command Explanation: Too many parameters were specified for
Explanation: Too many parameters are specified for the REPLACE command.
the MOVE command. User Response: Remove the excess parameters and try
User Response: Remove the invalid parameter. the operation again.
ISRE721 Invalid parameter - You may specify a ISRE729 Invalid parameter - You may specify a
member name and AFTER or BEFORE member name or a data set name and
followed by a aaaaaaaa. member and an aaaaaaaa range with
REPLACE command
Explanation: An invalid parameter was specified.
Explanation: An invalid parameter was specified for
User Response: Remove the invalid parameter and try the REPLACE command.
again.
User Response: Remove the invalid parameter and try
the command again.
ISRE722 Destination is required - aaaaaaaa
requires AFTER/BEFORE lptr. Member
name is also required. ISRE730 STAE macro error - Unable to obtain
storage for STAE macro, subpool 0 full.
Explanation: The destination parameter was omitted.
Explanation: This is an informational message.
User Response: Specify either AFTER or BEFORE and
the member name.
ISRE731 Invalid block size - Specified data set
has zero block size.
Explanation: The specified data set has a block size of
zero; this is invalid.
User Response: Either choose a different data set or
change the block size.
ISRE732 BLDL error - I/O error, insufficient ISRE738 Member aaaaaaaa created - aaaaaaaa was
virtual storage, or other BLDL error. added to bbbbbbbb
Explanation: This is an informational message. Explanation: This is an informational message.
User Response: Request additional virtual storage. If
the error recurs, contact your system programmer. ISRE739 Too many parameters - Too many
parameters were entered with the
System Programmer Response: This is a probable
scrolling command.
system failure. Isolate the reason for the failure.
Explanation: Too many parameters were entered for
the SCROLL command.
ISRE733 I/O error during read - Unable to read
data. User Response: Remove the invalid parameters.
Explanation: A failure occurred while attempting to
read a data set. ISRE740 Command is not a macro - ″aaaaaaaa″
does not contain an ISREDIT MACRO
User Response: Contact your system programmer.
statement.
System Programmer Response: This is probably a
Explanation: The command you entered is not a valid
system error. Isolate the error, contact IBM support.
edit macro.
User Response: Determine the correct edit macro
ISRE734 Member not found - The requested
name. If the edit macro name is correct, contact the
member was not found in the PDS
responsible programmer.
directory(s).
Programmer Response: Verify the macro name, add
Explanation: The member you specified was not
an ISREDIT MACRO statement to the macro.
found in the data set directory.
User Response: Verify that the member exists.
ISRE741 Command not executed - An ISREDIT
MACRO statement must precede any
ISRE735 Data set not partitioned - Member name executable statements.
specified, but the data set is not a
Explanation: The macro name you entered does not
partitioned data set.
have the ISREDIT MACRO statement as the first
Explanation: If you specify a member name, the data executable instruction.
set must be partitioned.
User Response: Contact the responsible programmer.
User Response: Either remove the member name or
Programmer Response: Verify that the first executable
correct the data set name.
instruction in the macro is the ISREDIT MACRO
instruction.
ISRE736 Member list update error - Member
name not added to member list. An
ISRE742 System error, no SYSPROC - Command
error occurred during update.
is invalid or a macro. Macros require an
Explanation: The attempt to update the member list allocated SYSPROC.
failed.
Explanation: Either you entered an invalid command
User Response: Contact your system programmer. or you requested that a macro be run but did not first
allocate a SYSPROC.
System Programmer Response: This is likely the
result of a system failure. Isolate the cause of the User Response: Allocate a SYSPROC and attempt the
failure. operation again or correct the command.
ISRE737 Invalid member name - Member name ISRE743 Command name invalid - ″aaaaaaaa″ is
aaaaaaaa not valid for partitioned data an invalid macro name; invalid
sets. SYSPROC member name.
Explanation: An invalid member name was entered. Explanation: Either you entered an invalid command
or macro name.
User Response: Correct the member name.
User Response: Correct the command or macro name.
Explanation: The data set you specified has no more Explanation: This is an informational message.
directory space for entries. User Response: See MVS Message Library: System Codes
for an explanation of the abend code if the tutorial
ISRE759 aaaaaaaa input error - VPUT failed to set Explanation: The member name is invalid for the
variable bbbbbbbb to value cccccccc EDIT, VIEW, or BROWSE command.
Explanation: An ISPF internal VPUT failed to set User Response: The member name must contain
variable bbbbbbbb in an edit macro. Possible causes for alphanumeric characters beginning with an alphabetic
this in a program macro are: character. Correct the member name and try the
v The value is longer than the variable VDEFINEd in command again.
the program.
v The value cannot be stored as the type VDEFINEd in
ISRE764 Invalid member name - Member name
the program.
″aaaaaaaa″ exceeds 8-character allowable
Additional possibilities, applicable to all types of length.
macros, are:
Explanation: The member name is invalid for the
v The length of all variables in the variable pool
EDIT, VIEW, or BROWSE command.
exceeds 32K.
v There is an error in your profile table (I/O or User Response: The member name may not exceed 8
internal format). characters. Correct the member name and try the
command again.
User Response: Contact the responsible programmer.
Programmer Response: Check for the problems listed
ISRE765 Member name not allowed - A member
above. If none of these problems exists, contact IBM
name cannot be specified when editing,
service.
viewing, or browsing a sequential data
set.
ISRE760 Too many parameters - The member
Explanation: The EDIT, VIEW, or BROWSE command
name is the only valid parameter for the
cannot be invoked with a member name when a
EDIT, VIEW, or BROWSE commands.
sequential data set is being edited, viewed, or browsed.
Explanation: Too many parameters were specified for
User Response: Specify EDIT, VIEW, or BROWSE with
the EDIT, VIEW, or BROWSE commands. The EDIT,
User Response: Contact your system programmer. User Response: Valid parameters are MAX, CSR,
PAGE, HALF, DATA, or the actual amount.
System Programmer Response: Contact IBM support.
ISRE778 System abend ’aaaaaaaa’ - An abend ISRE782 Issue a change command - RCHANGE
occurred while attempting to save the command works only after a valid
data. The previous information in the CHANGE command is issued.
target sequential data set has been
Explanation: The RCHANGE command was issued,
overwritten. The CANCEL command
but no CHANGE command was issued previously.
will not restore the data in the data set.
Press Help for further information. User Response: Issue a CHANGE command before
issuing the RCHANGE command.
Explanation: An 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 ISRE783 Issue a FIND command - RFIND
is no space in the data set to store the data. If an x37 command works only after a valid FIND
ABEND occurred writing to a sequential data set, that command is issued.
data set has been overwritten. The CANCEL command
will not restore the original contents. If UNDO is Explanation: The RFIND command was issued, but no
available, you may be able to undo all of your changes FIND command was issued previously.
and SAVE the data set to restore its original contents. User Response: Issue a FIND command before issuing
User Response: From within the edit session (the edit the RFIND command.
data display screen) you may:
v Split the screen and reallocate the data set. ISRE784 Level out of range - The level parameter
v Enter the CREATE or REPLACE command to save must be a positive number from 0 to
into another data set. 255.
v Enter the CANCEL primary command to exit from
EDIT without saving. Explanation: The level parameter specified was not in
the range 0 to 255.
From the create or replace menus you may:
v Split the screen and reallocate the data set User Response: Enter a value for the LEVEL
v Use END from the create or replace menu to exit parameter from 0 to 255 and try the command again.
without saving the data.
ISRE785 Invalid data sets - When comparing any
ISRE779 Panel not found - The panel name data set to a one which does not have a
specified in the PANEL field for fixed record length, neither data set can
EDIT/VIEW could not be found. have a record length greater than 32756.
Explanation: The EDIT service was invoked, passing Explanation: The Edit Compare command does not
the name of a panel to be used when displaying the allow comparisons of files when one or both of the files
edit data. The panel does not exist in the current has a logical record length greater than 32756 and at
ISPPLIB concatenation. least one of the files has a record format of variable(V)
or unblocked(U).
User Response: Determine what data set the panel
exists in, then modify your ISPF allocation clist or User Response: If you need to compare the files, use
logon proc to contain that data set. the SuperC utility to produce a listing instead of using
the edit COMPARE command.
ISRE781 Too many parameters - Do not specify Programmer Response: Specify the correct number of
parameters with the RCHANGE parameters for the LABEL command.
command.
Explanation: Parameters were specified with the ISRE791 Invalid label name - ’aaaaaaaa’ is an
RCHANGE command, but parameters are not allowed. invalid label name specified in the
LABEL command.
User Response: Remove the parameters and try the
command again. Explanation: The label name is invalid.
User Response: Contact the responsible programmer.
Programmer Response: Specify a label name for the User Response: Exit the application and try again. If
LABEL command. this message still appears, attempt to compress the
profile data set, or delete the edit profile table.
ISRE796 Invalid line pointer - The line pointer ISRE802 Invalid edit table - Table ’aaaaaaaa’
specified for the LABEL command does contains invalid variable(s). Table
not exist. service RC=bbbbbbbb.
Explanation: This is an informational message. The Explanation: The edit profile table contains invalid
line number specified on the LABEL command does variables.
not exist.
User Response: Delete the edit profile table from the
profile data set.
ISRE797 Required parm missing - Too few
parameters were specified for the
LABEL command. ISRE803 Edit profile error - Changes to any edit
profile will not be saved on disk this
Explanation: There were too few parameters specified edit session.
for the LABEL command.
Explanation: There was an error in the edit profile.
User Response: Contact the responsible programmer. Any changes to the edit profile will not be saved in this
Programmer Response: Specify all required edit session.
parameters for the LABEL command.
ISRE814 I/O error - I/O error while trying to ISRE822 Parameter unrecognized - ON/OFF are
build the member list. the only valid parameters for the PACK
command.
Explanation: An internal error has occurred.
Explanation: The parameter specified for the PACK
User Response: Contact your system programmer.
command is invalid.
System Programmer Response: Contact IBM support.
User Response: Specify either ON or OFF as the
parameter for the PACK command and try the
ISRE815 All lines excluded - aaaaaaaa lines were command again.
excluded
Explanation: This is an informational message. ISRE823 Invalid parameter - ON/OFF are the
only valid parameters for the PACK
command.
ISRE816 Range excluded - aaaaaaaa lines were
excluded in range bbbbbbbb to cccccccc. Explanation: The parameter specified for the PACK
command is invalid.
Explanation: This is an informational message.
User Response: Specify either ON or OFF as the
parameter for the PACK command and try the
ISRE817 No lines excluded - aaaaaaaa lines met command again.
EXCLUDE criteria
Explanation: This is an informational message. ISRE824 Required parm missing - NOWARN
parameter not accepted without OFF
ISRE818 BLDL error - I/O error, insufficient keyword being specified.
virtual storage, or other BLDL error. Explanation: The OFF keyword must be specified
Explanation: An internal error has occurred. with the NOWARN parameter.
User Response: Contact your system programmer. User Response: Specify the OFF keyword with the
NOWARN parameter and try the command again.
System Programmer Response: Contact IBM support.
ISRE820 Too many parameters - ON/OFF are the ISRE826 Required parm missing - WARN
only valid parameters for the PACK parameter not accepted without OFF
command. keyword being specified.
Explanation: Too many parameters were specified for Explanation: The OFF keyword must be specified
the PACK command. with the WARN parameter.
User Response: Specify ON or OFF as the parameter User Response: Specify the OFF keyword with the
for the PACK command and try the command again. WARN parameter and try the command again.
Explanation: The parameters entered for the PACK Explanation: The parameters specified for the
command are not consistent. AUTOSAVE command were not consistent.
User Response: Enter either ON or OFF as the User Response: Specify either ON or PROMPT as
parameter for the PACK command and try the parameters for the AUTOSAVE command and try the
command again. command again.
ISRE840 Too many parameters - A version ISRE846 Too many parameters - ON/OFF and
number is the only valid parameter for PROMPT/NOPROMPT are the only
the VERSION command. valid AUTOSAVE parameters.
Explanation: The VERSION command allows only a Explanation: Too many parameters were specified for
version number as a parameter. the AUTOSAVE command.
User Response: Specify only a version number for the User Response: Specify ON or OFF and PROMPT or
VERSION command and try the command again. NOPROMPT for the AUTOSAVE command and try the
command again.
ISRE841 Parameter unrecognized - A version
number is the only valid parameter for ISRE847 Inconsistent parameters - ″aaaaaaaa″ and
the VERSION command. ″bbbbbbbb″ cannot both be specified on
the AUTOSAVE command.
Explanation: The parameter specified for the
VERSION command is invalid. Explanation: Inconsistent parameters were specified
for the AUTOSAVE command.
User Response: Specify a version number as a
parameter for the VERSION command and try the User Response: Specify one but not both of the
command again. inconsistent parameters for the AUTOSAVE command
and try the command again.
ISRE842 Invalid parameter - A version number is
the only valid parameter for the ISRE848 Parameter unrecognized - ON/OFF and
VERSION command. PROMPT/NOPROMPT are the only
valid AUTOSAVE parameters.
Explanation: The parameter specified for the
VERSION command is invalid. Explanation: The parameter specified for the
AUTOSAVE command is not valid.
User Response: Specify a version number as the
parameter for the VERSION command and try the User Response: Specify ON/OFF and
command again. PROMPT/NOPROMPT for the AUTOSAVE command
and try the command again.
ISRE843 Required parm missing - A version
number parameter is required for the ISRE849 Invalid parameter - ON/OFF and
VERSION command. PROMPT/NOPROMPT are the only
valid AUTOSAVE parameters.
Explanation: The version number parameter is
required for the VERSION command. Explanation: The parameter specified for the
AUTOSAVE command is not valid.
User Response: Specify a version number as the
parameter for the VERSION command and try the User Response: Specify ON or OFF and PROMPT or
command again. NOPROMPT for the AUTOSAVE command and try the
command again.
ISRE844 Invalid version number - The specified
version number must be in the range: ISRE850 Too many parameters - A modification
1-99. level number is the only valid parm for
the LEVEL command.
Explanation: The version number specified for the
VERSION command is invalid. Explanation: The LEVEL command has too many
parameters. Only one parameter in the range 0-99 is
User Response: Specify a version number from 1 to 99
accepted.
for the VERSION command and try the command
again. User Response: Issue the LEVEL command with one
parameter in the range 0-99.
ISRE845 Assignment command error -
Assignment type (GET/SET) is ISRE851 Invalid modlevel number - A valid
unrecognized for the AUTOSAVE specification for LEVEL is in the range
command. 0-99.
Explanation: An internal error has occurred. Explanation: The LEVEL command parameter is out
of range. It must be in the range 0-99.
User Response: Contact your system programmer.
User Response: Issue the LEVEL command with one
System Programmer Response: Contact IBM support.
ISRE881 Member not found - Model member ISRE885 Model class changed - Model class is
desired was not found in ISPSLIB now set to ″aaaaaaaa″.
skeleton library.
Explanation: This is an informational message
Explanation: The name of a member in a skeleton indicating that the model class has been changed. This
library was not found. The name may be misspelled or message may appear after issuing the MODEL CLASS
the member may not be present in the skeleton library. command and selecting a different class.
User Response: Contact the responsible programmer.
ISRE886 DVPUT returning error - DVPUT to set
Programmer Response: Check the panel member for a
a variable for model function fails.
misspelled name and the skeleton library for a missing
member. Explanation: An ISPF system error, installation error,
or unrecoverable I/O error has occurred.
Problem Determination: The skeleton member name
may be misspelled in the panel member or be missing User Response: Contact your system programmer.
from the skeleton library.
ISRE887 DVDEF returning error - When defining
ISRE882 Member selection failed - Error received variables for model function fails.
during selection panel process to
Explanation: An ISPF system error, installation error,
determine a model.
or unrecoverable I/O error has occurred.
Explanation: The MODEL command was issued with
User Response: Contact your system programmer.
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 ISRE888 DVGET returning error - Attempt to
error. retrieve variable for model function
fails.
User Response: Reissue the MODEL command
without specifying a member name. Explanation: An ISPF system error, installation error,
or unrecoverable I/O error has occurred.
Programmer Response: Examine the edit macro for a
MODEL command that specifies a member name for User Response: Contact your system programmer.
the message class.
User Response: Contact the responsible programmer. Explanation: The MODEL macro command requires
the name of the model to be copied.
Programmer Response: Change the MACRO
command in the edit macro so the parameters have an User Response: Contact the responsible programmer.
ending parenthesis.
Programmer Response: The edit macro may contain a
MODEL macro command that does not specify the
ISRE894 aaaaaaaa macro error - Command as name of the model to be copied. The edit macro code
entered: ″bbbbbbbb″. may be changed so that the name of a model is
specified as part of the MODEL macro command.
Explanation: A command in an edit macro ended in
error. Problem Determination: Examine the edit macro for
MODEL commands that do not specify the name of a
User Response: Examine the parameters (if any) model.
specified for the edit macro. Invalid parameters passed
ISRE898 Member not found - Model ″aaaaaaaa″ ISRE901 Severe error - Unexpected return code
was not found in ISPSLIB skeleton from the dialog supplied read routine.
library.
Explanation: An unexpected return code was received
Explanation: The name of the model specified on the from the dialog supplied read routine. Expected return
MODEL macro command was not found in the ISPSLIB codes are 0, 8, 16, and 20.
skeleton library. The model may be missing from the
User Response: Contact your system programmer.
library or the model name may be misspelled.
System Programmer Response: The dialog supplied
User Response: Contact the responsible programmer.
read routine should be examined for errors. There may
Programmer Response: The edit macro may need to be a problem with the data being read.
be corrected with a proper spelling of the model name,
or the model may need to be added to the ISPSLIB
ISRE902 Data set too large - Insufficient storage
skeleton library.
to read in data set at this time.
Problem Determination: Examine the edit macro for a
Explanation: An out of storage situation has been
misspelled model name. If the model name is spelled
detected. There is insufficient storage for a GETMAIN.
properly, then the model may need to be added to the
ISPSLIB skeleton library. User Response: The region size may need to be
increased. Contact the system programmer if increased
region size does not solve the problem, or if the region
ISRE899 Class name not specified - The class
size is already at the maximum limit.
name desired must be specified on the
MODEL macro command. System Programmer Response: Examine the data set
to see if it is too large for the user environment. A
Explanation: The MODEL macro command class
larger region size may solve the problem.
syntax requires specification of a class name. There was
no class name specified.
ISRE903 I/O error reading data - I/O error
User Response: Contact the responsible programmer.
occurred reading the edit data.
Programmer Response: The edit macro may contain a
Explanation: An I/O error with a return code of 16
MODEL command that does not specify a class name
was encountered. This is an ISPF system error,
as per the macro command class name syntax. Change
installation error, or unrecoverable I/O error.
the macro so a class name is specified on the MODEL
CLASS command. User Response: Contact your system programmer.
Problem Determination: Examine the edit macro for a System Programmer Response: Investigate the cause
missing class name on the MODEL CLASS command. of the I/O error.
ISRE900 Invalid IMACRO name - Name must ISRE904 I/O error reading data - I/O error
follow member name rules or start with occurred reading the edit data. Check
″!″ followed by a valid name data set block sizes.
Explanation: The IMACRO command saves the name Explanation: An error occurred while reading the edit
of an initial macro in the current edit profile. A value of data.
NONE specifies that no macro is to be run at the
beginning of each edit session. The name must follow User Response: Contact your system programmer.
the rules for a member name or start with an System Programmer Response: Investigate the cause
exclamation mark ! followed by a valid name. of the I/O error.
User Response: Reissue the IMACRO command with Problem Determination: This should not be a packed
NONE or a valid name. Contact the edit macro data problem as errors from packed data result in a
programmer if the IMACRO command is issued in an different message. The data set block sizes may be
edit macro. causing the error.
Programmer Response: Examine the edit macro for an
IMACRO command with an invalid name. Replace the ISRE905 Invalid EDIT/VIEW parm - Password is
invalid name with a valid name. not allowed when DATAID is specified.
Explanation: A password and DATAID are present. A
password is not allowed with a DATAID.
User Response: Contact the programmer of the dialog
that invokes the EDIT or VIEW service.
| ISRE935 Data parm omitted - Required data ISRE943 Option unavailable - The only HILITE
| parameter not specified for services available when editing data sets
| LINE_STATUS command. with data lengths greater than 255
characters are FIND and CURSOR. All
| Explanation: An invalid LINE command was entered.
language sensitive hilighting is
| User Response: Review documentation for the LINE disabled.
| command in &ema..
Explanation: This is an informational message.
| Programmer Response: Correct the LINE_STATUS
| command using the syntax
ISRE944 HILITE unavailable - The HILITE
| ISREDIT (var) = LINE_STATUS line-pointer command is not available when
| enhanced edit color is not enabled.
ISRE938 Missing parameter - Variable name Enhanced edit color is either disabled in
parameter required for VOLUME the PDF configuration table, or the edit
command. panel in use does not support enhanced
edit color or you issued the HILITE
Explanation: The VOLUME assignment statement is disable command.
missing the required variable name for the volume of
the edit data set. Explanation: Enhanced edit color is not available
because it is disabled for one of the following reasons:
User Response: Correct the VOLUME assignment v The edit panel in use is not enabled for enhanced
statement so that it includes the required variable name color.
for the volume of the current edit data set. v The enhanced color capabilities were disabled when
ISPF was installed.
v The HILITE DISABLE command was entered on the
ISRE939 Invalid specification - GET assignment
command line or was run from an edit macro.
type unrecognized for the VOLUME
command. User Response: If enhanced color is unavailable
because the panel you are using is not enabled for it,
Explanation: Either the VOLUME assignment
change the edit panel you are using to enable it. The
statement contains an invalid variable name or a
panel must have a dynamic area called ZDATA, a
parameter is missing.
shadow variable called ZSHADOW, and special
User Response: Verify that the VOLUME assignment attributes in the )ATTR section. See the panel
statement contains no syntax errors or missing ISREDDE2 which is shipped with ISPF for an example.
parameters.
System Programmer Response: If you decide to
enable enhanced coloring, update the ISPF
ISRE940 Dialog unavailable - The HILITE dialog configuration table. See Planning and Customizing
cannot be started from an edit macro.
Explanation: The edit command HILITE without ISRE945 HILITE unavailable - The HILITE
operands was specified in an edit macro. The HILITE command is not available when an edit
dialog is not available from edit macros. format is used.
User Response: Specify at least one operand on the Explanation: This is an informational message.
HILITE command in the edit macro.
ISRE947 Invalid terminal - Enhanced coloring is
ISRE941 Invalid line number - The relative line not available on this terminal because
number of a line to be copied cannot be the terminal does not support extended
zero. highlighting.
Explanation: A relative line number for a copy Explanation: This is an informational message.
operation was specified as zero. The relative line
number must be one or greater.
ISRE948 HI DISABLE unavailable - Enhanced
User Response: Respecify the relative line number(s). coloring cannot be disabled with the
current edit panel. Only panels
ISREDDE2, ISREDDE3 and FLMEDDE
ISRE942 HILITE unavailable - The HILITE
support the HILITE DISABLE
command is not available in mixed
command.
mode edit sessions.
Explanation: Only panels ISREDDE2, ISREDDE3, and
Explanation: This is an informational message.
FLMEDDE support the HILITE DISABLE command.
These are the default panels shipped with ISPF for
ISRE985 Invalid line pointer - LPTR not numeric ISRE997 LMF lock not allowed - The member
or label in syntax ″ISREDIT (varname) = being edited belongs to an SCLM
aaaaaaaa LPTR″. controlled project.
Explanation: An assignment statement of the form Explanation: The member being edited is under the
above requires that the line pointer be either a valid control of both LMF and SCLM libraries. Saving the
label or line number. The line pointer used was invalid. member under LMF will invalidate the SCLM
accounting information for the member.
User Response: Contact the responsible programmer.
User Response: Contact your Library Administrator to
Programmer Response: Update the assignment
determine whether LMF or SCLM should be used to
statement in the Edit macro to specify a valid label or
edit the member.
line number.
Explanation: This is an informational message. The Explanation: A severe internal error has occurred. An
short message identifies a COBOL interactive debug unexpected return code was received from the table
session. The long message identifies the partitioned display service.
data set against which the COBOL interactive debug User Response: Contact your system programmer.
session is run.
System Programmer Response: Contact IBM support.
ISRF011 DISPLAY severe error - DISPLAY ISRF018 Operation cancelled - The requested
service severe error occurred. function was cancelled.
Explanation: A severe internal error has occurred. An Explanation: This is an informational message. The
unexpected returned code was received from the requested function was cancelled.
DISPLAY service.
User Response: Contact your system programmer.
System Programmer Response: Contact IBM support.
ISRF019 Normal completion - Requested ISRF026 Format name missing - This command
function successfully completed. requires a format name.
Explanation: This is an informational message. The Explanation: The FROM format name for the copy
requested function was completed successfully. operation in the Format Specification utility is missing.
ISRF020 Field length error - Zero length field is ISRF027 Duplicate name - Same format in same
defined. TABLE(ISRFORM) is specified for copy.
Explanation: An invalid field length of zero is Explanation: The same format in the same format
specified. table is specified for copy.
User Response: Specify a field length between 1 and User Response: Correct the format names.
71.
ISRF028 ″*″ is invalid - ″*″ cannot be specified
ISRF021 Odd length DBCS field - Odd length when the From table is ISRFORM.
DBCS field is defined.
Explanation: An asterisk (″*″) cannot be specified
Explanation: An odd field length is specified. when the FROM table is ISRFORM.
User Response: Specify an even number for the DBCS User Response: Specify a valid FROM format name,
field length. or specify a FROM table name other than ISRFORM.
ISRF022 Invalid command - aaaaaaaa is an invalid ISRF029 Duplicate format name - Format name
command. specified already exists.
Explanation: An invalid format selection list Explanation: The format name specified already exists.
command is entered.
User Response: Correct the format name.
User Response: Correct the invalid format selection
list command.
ISRF030 RECFM must be fixed - Variable length
records may not be used for the
ISRF023 Too many parameters - Too many formatted file.
parameters are specified in the
Explanation: Variable RECFM formatted data sets are
command area.
not supported.
Explanation: Too many parameters are specified in the
User Response: Specify a fixed RECFM formatted
command area.
data set or blank out the format name.
User Response: Blank out the extra parameters.
ISRF031 No format table - Format table
ISRF024 Invalid parameter - Invalid parameter is ISRFORM does not exist.
specified in the command area.
Explanation: A format name is specified, but the
Explanation: An invalid parameter is specified for the format table does not exist.
format selection list command.
User Response: Use the Format Specification utility
User Response: Correct the invalid parameter. (option 3.11) to add the new format.
ISRF025 ″aaaaaaaa″ does not exist - From format ISRF032 Format table is in use - Format table is
name ″aaaaaaaa″ does not exist. in use by another user or by you.
Explanation: The FROM format specified, aaaaaaaa, for Explanation: The format table is in use by another
the copy operation in the Format Specification utility user or by you on another logical screen.
does not exist.
User Response: Find out if another user is using the
User Response: Correct the FROM format name. format table, or release the format table on another
logical screen.
ISRF033 Library is not allocated - The table ISRF038 No formats found - No format table
library is not allocated. entries were found to process.
Explanation: The table library for ISPF is not Explanation: No format table entries were found to
allocated. process.
User Response: Refer to the Program Directory for User Response: Use option A to add a new format.
details on allocating the table library for ISPF.
ISRF040 Table does not exist - From table
ISRF034 Table service error - Severe table service ″aaaaaaaa″ does not exist.
error occurred.
Explanation: The FROM table aaaaaaaa specified for
Explanation: A severe table service error has occurred. the copy operation in the Format Specification utility
The table data set may be corrupted. does not exist.
User Response: Contact the responsible programmer. User Response: Correct the FROM table name.
Programmer Response: Check the integrity of the
table data set. Reallocate or restore from a backup if the ISRF041 Table is in use - From table ″aaaaaaaa″ is
table data set is corrupted. Otherwise, contact IBM in use.
support.
Explanation: The FROM table aaaaaaaa specified for
the copy operation in the Format Specification utility is
ISRF035 Format not found - The specified format in use by another user or by you on another logical
does not exist. screen.
Explanation: The specified format does not exist in the User Response: Find out if another user is using the
format table. table, or release the table on another logical screen.
User Response: Contact the responsible programmer.
ISRF042 Table service error - Severe table service
Programmer Response: Correct the spelling of the
error occurred with from table.
format name, or add the new format using the Format
Specification utility (option 3.11). Explanation: A severe table service error has occurred
with the FROM table. The FROM table may be
corrupted.
ISRF036 Invalid format - The maximum column
position in format exceeds record User Response: Contact the responsible programmer.
length.
Programmer Response: Check the integrity of the
Explanation: The maximum column position in the FROM table. Reallocate or restore from a backup if the
format exceeds the record length of the data set. table is corrupted. Otherwise, contact IBM support.
User Response: Contact the responsible programmer.
ISRF043 Invalid selection code - Valid codes are:
Programmer Response: Use the Format Specification
S (select), U (update), R (rename), or D
utility (option 3.11) to update the format so that the
(delete).
maximum column position in the format does not
exceed the record length of the data set. Explanation: An invalid selection code is specified.
User Response: Enter one of the valid selection codes
ISRF037 LRECL limit exceeded - LRECL plus (S, U, R, or D) for the format selection list.
formatted attribute bytes exceeds
edit/browse lrecl limit.
ISRF044 Invalid selection code - Valid code is: S
Explanation: The record length of the data set plus the (select).
formatted attribute bytes exceeds the Edit or Browse
Explanation: An invalid selection code is specified.
record length limit.
User Response: Enter the valid selection code (S) for
User Response: Contact the responsible programmer.
the copy format selection list.
Programmer Response: Divide the format into two
smaller formats and Edit or Browse the data set in two
steps.
ISRF900 Function ended RC=X’aaaa’ - The ISRF905 Invalid organization - Only partitioned
selected function completed with return and physical sequential data sets
code of X’aaaa.’. processed.
Explanation: This is an informational message. The Explanation: The PDF foreground option was invoked
selected foreground function is complete with a return specifying a data set that was other than partitioned or
code of aaaa hex. sequential.
User Response: Change the input data set to one that
ISRF901 ISRLEMX ended RC=aaaa - Member is partitioned or sequential and retry.
expansion completed with return code
of aaaa.
ISRF906 Invalid organization - Only partitioned
Explanation: The PDF Member Expansion routine data sets processed.
(ISRLEMX) failed with a return code of aaaa. The
Explanation: The PDF foreground Binder/Linkage
ISRLEMX return codes are:
Editor and VS COBOL II Interactive Debug options
1-15 Parameter n was too long, where n is the
only support partitioned data sets as input.
return code.
16 Too many parameters specified. User Response: Change the input data set to one that
17 Too few parameters specified. is partitioned and retry.
20 Severe error. Refer to the data set allocated to
DDNAME ISRLMSG for details on the failure.
ISRF907 Processor failed, RC=20 - The aaaaaaaa
User Response: Refer to ISPF Dialog Developer’s Guide language processor ended with a return
and Reference and ISPF Planning and Customizing for code of 20, possibly indicating that it
further information on the ISRLEMX routine. could not be found by ISPF.
Explanation: The PDF foreground processor attempted
ISRF902 No list file found - Unable to locate list to invoke the language processor you requested, but
file for aaaaaaaa or the file was empty. the ISPF SELECT service returned a return code 20.
This could be a return code 20 from the processor, or it
Explanation: This is an informational message. The
could be indicate that ISPF could not find the language
processing (indicated by variable aaaaaaaa) is complete,
processor.
but the expected listing data set was not found.
User Response: Verify that your MVS search sequence
includes the load module data set containing the
ISRF903 Invalid ZSEL variable - The ZSEL panel
processor requested is included, then retry the request.
variable must start with CMD or PGM.
If the same message is returned, the language processor
Explanation: The PDF foreground processor (ISRFPR) is returning the 20 and you should refer to the
is invoked passing the name of a panel to display. The documentation supplied with that processor for
)PROC section of this panel must set variable &ZSEL to problem determination.
an CMD(...) or PGM(...) string that PDF can pass to the
ISPF SELECT service. A ZSEL string was encountered
ISRF911 Specify list ID - Specify a ″list ID″ for
that does not start with CMD or PGM.
sequential file.
User Response: Contact the responsible programmer.
Explanation: The list ID, used as one of the qualifiers
Programmer Response: Correct the ZSEL string and for the listing data set name, normally defaults to the
retry the function. 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.
ISRF904 Non-zero return code - The selected
function terminated with return code of User Response: Specify a list ID and retry the
X’aaaa.’. function.
Explanation: This is an informational message. The
selected foreground function is complete with a return ISRF912 Invalid ZSEL2 variable - The ZSEL2
code of aaaa hex. If aaaa is X’63’ this indicates a clist panel variable must start with CMD or
error, probably caused by entering an arithmetic PGM
operator (*, /, +, -, etc.) in one of the panel input fields.
Explanation: The PDF foreground processor (ISRFPR)
Any other return code is the return code returned by
is invoked passing the name of a panel to display. The
the selected language processor.
)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
ISRF914 BLDL error - I/O error, insufficient ISRF919 Member not found - The requested
virtual storage or other BLDL error member was not found in the PDS
directory(s).
Explanation: PDF received an error from the BLDL
macro processing the the data set specified for Explanation: The member specified for foreground
foreground processing. processing does not exist in the library specified.
User Response: Contact your system programmer. User Response: Correct the data set name and
member name to specify an existing member and retry
System Programmer Response: Check your MVS the function.
console for messages caused by this error and refer to
the System Messages and Codes manual for problem
determination. If further assistance is needed, contact ISRF920 Style deleted - Selected style(s) deleted
IBM support. from style table.
Explanation: This is an informational message. The
ISRF915 No members in data set - The PDS selected style was deleted successfully from the Select
specified contains no members. Script/VS Formatting Style panel (panel ISRFP09T).
ISRF916 I/O error - An I/O error occurred while ISRF922 Bad directory - Directory block size
reading the PDS directory. exceeds maximum of 256.
Explanation: PDF received a return code 8 from the Explanation: The PDF common member list routine
BLDL macro while attempting to gather member detected a data set that had a directory block greater
statistics while building a foreground member list. than 256 bytes, the maximum supported by PDF.
User Response: Contact your system programmer. User Response: Copy the data into a new data set and
retry the request.
ISRF918 Member list error - Unexpected error User Response: Select a style using the S line
from member list display routine command, delete a style using the D line command, or
enter the END command to exit without a selection.
Explanation: The PDF foreground processor (ISRFPR)
received an unexpected return code from the PDF
member list processor (ISRCML).
User Response: Contact your system programmer.
ISRF939 Invalid data set name - The data set ISRG007 Vol serial not allowed - Use ″Other data
must be fully qualified and enclosed in set name″ field when specifying volume
apostrophes. serial.
Explanation: A data set name was entered in the Explanation: The Volume Serial input field invalidly
additional input libraries field that was not enclosed in contains a value when not specifying Other Data Set
apostrophes. Name field.
User Response: Correct the data set name and retry User Response: When using the ISPF Library input
the request. 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
ISRF940 Additional lib error - Additional input
Volume Serial input field contain a valid value.
library aaa(44) is not partitioned. All
libraries specified in the additional
input libraries fields must be ISRG010 Data set is open - Data set is currently
partitioned. being used by ISPF.
Explanation: Data set aaa(44), specifies as one of the Explanation: The specified data set is open and
additional input libraries specified at the bottom of one currently being used by ISPF.
of the compiler interface data entry panels is not
User Response: This message is issued when one of
partitioned. Only partitioned data sets may be specified
the data sets LIST, LOG, TEMPLIST, TEMPCNTL, or
in these fields.
EDIT RECOVERY is specified and ISPF is currently
User Response: Specifiy a partitioned data set and using the data set. The LOG and LIST data sets are
retry the request. 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.
ISRG002 Enter project name - Project name is
The TEMPLIST, TEMPCNTL, and EDIT RECOVERY
missing or invalid.
data sets need to be saved and closed in order to be
Explanation: The Project name field is blank or invalid used.
in the ISPF library data set input fields.
User Response: A valid Project name must be entered ISRG011 Unsupported data type - HFS data sets
for the ISPF library. An ISPF library is a cataloged are supported for data set creation, data
partitioned data set with a three-level data set name in set information, data set rename and
this format: data set delete only.
’project.group.type’
Explanation: An attempt was made to perform a PDF
function other than data set creation, data set
ISRG003 Enter group name - Group name is information, data set rename, or data set delete against
missing or invalid. an HFS data set.
Explanation: The Project name field is blank or invalid User Response: Use a supported data set type.
in the ISPF library data set input fields
User Response: A valid Project name must be entered ISRG040 Invalid DSORG - Data set organization
for the ISPF library. An ISPF library is a cataloged must be partitioned or sequential.
partitioned data set with a three-level data set name in
Explanation: The data set organization was entered
this format:
incorrectly.
’project.group.type’
User Response: Correct the data set organization.
ISRG004 Enter type qualifier - Type is missing or
invalid. ISRG044 Concatenation failed - Unable to
concatenate the specified libraries.
Explanation: The Type name field is blank or invalid
in the ISPF library data set input fields. Explanation: The concatenation failed, ISPCDAIR did
not return with RC=0.
User Response: A valid Type name must be entered
for the ISPF library. An ISPF library is a cataloged User Response: Contact your system programmer.
partitioned data set with a three-level data set name in
System Programmer Response: If the user’s action
this format:
was correct, contact IBM support.
’project.group.type’
ISRG045 STAE macro error - Unable to obtain ISRG076 Inconsistent record size - All libraries
storage for STAE macro, subpool 0 full. must have the same record length.
Explanation: Storage has been exhausted; there was a Explanation: An attempt was made to concatenate
previous error that could have used all of the available data sets with different record lengths. This action is
storage. not supported by ISPF.
User Response: Verify that your region size is large User Response: Check to be sure that the correct data
enough to run the task that just failed. If you still have sets are being allocated and that the record lengths and
a problem, contact the system programmer. record formats are the same for all of the data sets. You
may need to reallocate the data sets or copy the
System Programmer Response: Verify that the task is
contents to temporary data sets which you allocate
not looping and that the storage is sufficient to execute
instead.
the failing function.
ISRG080 Inconsistent data sets - Data set ISRG084 Reallocation failed - Reallocation failed
organizations are not the same. for data set ’aaaaaaaa’
Explanation: An attempt was made to concatenate Explanation: The attempt to allocate a data set
data sets with different data set organizations. This exclusively before deleting it failed. The data set may
action is not supported by ISPF. be in use by other users.
User Response: Check to be sure that the correct data User Response: Try the operation again later.
sets are being allocated and that the data set
organizations (sequential or partitioned) are the same
ISRG085 Deallocation failed - Deallocation failed
for all of the data sets. You may need to reallocate the
for data set ’aaaaaaaa’
data sets or copy the contents to temporary data sets
which you allocate instead. Explanation: The 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.
ISRG081 Data set not partitioned - Member name
specified, but the data set is not a User Response: Use the TSO FREE command to free
partitioned data set. all your allocations of the data set, and retry the
operation.
Explanation: A member name was specified with a
data set which is not partitioned.
ISRG086 Delete data set failed - ’aaaaaaaa’ is in
User Response: Remove the member name, or verify
use, it cannot be deleted.
that the data set was correctly specified and correctly
allocated. Explanation: The 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.
ISRG082 Data set not partitioned - Only
partitioned data sets may be User Response: Use the TSO FREE command to free
concatenated. all your allocations of the data set and retry the
operation. If other users are not using the data set and
Explanation: An attempt was made to concatenate
you are authorized to delete the data set, contact your
data sets that are not partitioned. ISPF does not
system programmer.
support concatenated sequential data sets.
User Response: Check to be sure that the correct data
ISRG087 Data set in use - The data set is
sets are being allocated and that the data set
currently in use by you.
organizations are all partitioned.
Explanation: An operation on a data set failed because
you are already allocated to the data set.
ISRG083 Deconcatenation failed - Unable to
deconcatenate the specified libraries. User Response: Return to the primary option menu
on all screens and retry the operation again. If that
Explanation: An attempt was made to unallocate a set
does not fix the problem, use the TSO FREE command
of concatenated libraries but the deconcatenate
to free the data set and retry the operation.
operation failed.
User Response: Since this is probably due to another
ISRG088 DSN alloc check failed - Unable to
allocation that uses the same ddname needed by the
check if data set is already allocated.
deconcatenation operation, you may need to use the
TSO FREE command to free ddnames. If it does not Explanation: An internal error occurred.
matter if you have the data sets allocated, you may be
able to ignore this message. However, if other users User Response: Log off the system and log back on.
may need the data sets, it may be a good idea to free Then retry the operation that failed.
the data sets manually with the TSO FREE command,
or to log off and back on. ISRG090 Invalid DSN - quotes - Data set name
Problem Determination: Determine what activity has contains unbalanced apostrophes.
occurred between the allocation and freeing of the Explanation: The data set name entered contains
failing concatenation. It is possible that some other unbalanced apostrophes.
allocation attempt failed and did not free all of its
allocations. These allocations may or may not have User Response: Reenter the data set name with the
been done by ISPF. correct apostrophes.
ISRG091 Invalid DSN - length - Data set name ISRG097 Inconsistent record type - All libraries
must be 1-44 characters in length must be the same record type.
counting prefix (if any).
Explanation: All libraries within a concatenation must
Explanation: The data set name you entered had an be defined with the same record type.
invalid length. It must be no more than 44 characters
Programmer Response: Review the libraries within
including the TSO prefix, if used.
the concatenation for the correct record type.
User Response: Check the data set name, and reenter
it correctly.
ISRG098 Inconsistent record size - The first
library must have the largest record
ISRG092 Invalid member name - Member name length.
must be 1-8 characters and enclosed in
Explanation: The first library within a concatenation
parentheses.
must be defined with the largest record length.
Explanation: The member name that was entered was
Programmer Response: Review the libraries within
invalid. The member name must be 1 to 8 characters,
the concatenation for the correct record length and
enclosed in parentheses.
concatenation sequence.
User Response: Reenter the member name using the
correct syntax.
ISRG099 Not generation data set - Data set is not
a generation data set.
ISRG093 Invalid DSN - syntax - Imbedded
Explanation: The data set specified is not a generation
blanks, parentheses, or apostrophes in
data set.
data set name are invalid.
Programmer Response: Check the specified data set
Explanation: The data set name that was entered
name.
contained blanks, apostrophes, or parentheses, which
are invalid in a data set name.
ISRG100 Vol serial not allowed - Use ″Other data
User Response: Reenter the data set name following
set name″ field when specifying volume
the correct syntax.
serial.
Explanation: A volume serial was specified on a panel
ISRG094 Data set not cataloged - Generation data
when the Project/Group/Type fields were used for the
set not found. Check catalog of
data set name. The volume serial may only be specified
generation group.
when you use the Other Data Set Name field for the
Explanation: The data set specified was not found. data set.
User Response: Check the data set name entered. User Response: If 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
ISRG095 Inconsistent block size - The first
in the Volume Serial field before pressing the Enter key.
library must have the largest block size.
Explanation: The first library of the concatenation
ISRG101 Load failed - The attempt to load the
must have the largest block size of the libraries within
data set allocation exit failed.
the concatenation.
Explanation: PDF attempted to load the allocation exit
System Programmer Response: Update the
specified in the PDF configuration table but was unable
concatenation so that the largest block size data is first
to do so. The exit may not have been found, may have
in the concatenation.
been non-executable, or you may not be authorized to
load it.
ISRG096 Inconsistent record size - All libraries
User Response: Ensure that the allocation exit is
must have the same record length.
correctly specified in the configuration table and is
Explanation: All libraries within a concatenation must available and executable in your load libraries or
have the same record length. system libraries before entering PDF.
Explanation: This is an informational message. The Explanation: The Enter key was pressed on either the
user entered the CANCEL command on the Batch Batch Selection panel (ISRJPA) or the Batch Termination
Termination panel to exit batch without submitting the panel (ISRJPB) without an option being selected.
generated JCL.
User Response: Specify the option desired on the
command line and press Enter.
ISRJ015 Invalid option - The option that was ISRJ906 Invalid organization - Only partitioned
entered was not valid. data sets processed.
Explanation: An invalid option was entered on either Explanation: The PDF batch Binder/Linkage Editor
the Batch Selection panel (ISRJPA) or the Batch option only supports partitioned data sets as input.
Termination panel (ISRJPB).
User Response: Change the input data set to one that
User Response: Specify a valid option and press is partitioned and retry.
Enter.
ISRJ908 Job skeleton not found - Job skeleton
ISRJ902 Skeleton not found - Skeleton ″aaaaaaaa″ file ISRJSJC not found.
or imbedded skeletons in ″aaaaaaaa″ not
Explanation: PDF batch skeleton ISRJSJC, used to set
found.
up the job cards for batch job submission, could not be
Explanation: PDF issued an ISPEXEC FTINCL for found in your ISPSLIB concatenation.
skeleton aaaaaaaa, but received a non-zero return code,
User Response: Check your ISPSLIB concatenation to
indicating the skeleton could not be found.
ensure the proper skeleton libraries are specified. After
User Response: Check your ISPSLIB concatenation to correcting your concatenation, retry the request.
ensure the proper skeleton libraries are specified. After
correcting your concatenation, retry the request.
ISRJ909 File tailoring error - File tailoring is
already in progress.
ISRJ903 Invalid ZSEL variable - The ZSEL panel
Explanation: The PDF batch option uses ISPF file
variable must start with CMD or PGM.
tailoring to create its jobstream; therefore, it cannot be
Explanation: The PDF batch processor (ISRJB2) is invoked when another file tailoring request is in
invoked, passing the name of a panel to display. The progress.
)PROC section of this panel must set variable &ZSEL to
User Response: Finish the in-process file tailoring
a CMD(...) or PGM(...) string that PDF can pass to the
request, then retry the batch request.
ISPF SELECT service. A ZSEL string was encountered
that did not start with CMD or PGM.
ISRLA000 Activity log error - See system
User Response: Contact the responsible programmer.
programmer - details in the LMF
Programmer Response: Correct the ZSEL string and address space ISPLOG.
retry the function.
Explanation: No explanation available at this time.
ISRLA005 Activity log free error - Data set ISRLA111 Activated successfully - All hierarchies
’aaaaaaaa..bbbbbbbb..ACTLOG’ could not in project ’aaaaaaaa’ are activated
be freed. successfully.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLA006 Activity log read error - Data set ISRLA112 Deactivated successfully - The hierarchy
’aaaaaaaa..bbbbbbbb..ACTLOG’ had a read ’aaaaaaaa’ is deactivated successfully.
error.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLA113 Deactivated successfully - All
ISRLA007 Activity log write error - An error hierarchies in project ’aaaaaaaa’ are
occurred writing deactivated successfully.
’aaaaaaaa..bbbbbbbb..ACTLOG’ to a
Explanation: No explanation available at this time.
temporary file.
Explanation: No explanation available at this time.
ISRLA114 Defined types - Structure for - aaaaaaaa
Date: bbbbbbbb Time: cccccccc
ISRLA100 Deactivate ID not match - User ID
Explanation: No explanation available at this time.
’aaaaaaaa’ does not match the deactivate
ID ’bbbbbbbb’.
ISRLA115 Where: - 1, 2 ... 50 indicates hierarchical
Explanation: No explanation available at this time.
position.
Explanation: No explanation available at this time.
ISRLA101 Bad deactivate IDs - Deactivate IDs are
not consistent. Deactivate and try again.
ISRLA116 *** No defined type *** - B indicates
Explanation: No explanation available at this time.
bottom group.
Explanation: No explanation available at this time.
ISRLA102 Already activated - The hierarchy
’aaaaaaaa’ has already been activated.
ISRLA117 The following groups were not
Explanation: No explanation available at this time.
activated.
Explanation: No explanation available at this time.
ISRLA103 Already deactivated - The hierarchy
’aaaaaaaa’ has already been deactivated.
ISRLA118 Top group Deactivate ID
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLA104 SCLM project deactivated - The project
is SCLM controlled, but has been ISRLA119 The following groups are active.
successfully deactivated.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLA122 No logical record length - Must specify ISRLA206 No types logged - There are no entries
the logical record length for the outlist in ’aaaaaaaa..bbbbbbbb..ACTLOG’.
data set.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLA208 Log not allocated -
ISRLA123 No lines per page - Must specify the ’aaaaaaaa..bbbbbbbb..ACTLOG’ may be in
lines per page for the outlist data set. use by another user.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLA218 Type ″aaaaaaaa″ browsed - The logged ISRLC012 Member entry not created - Member
activity for type ″aaaaaaaa″ was browsed. entry ’aaaaaaaa’ not created. The project
does not exist.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLA219 Activity log browsed - The activity in
log ’aaaaaaaa..bbbbbbbb..ACTLOG’ was ISRLC013 Entry not created - ’aaaaaaaa’ was not
browsed. created. It already exists.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLA220 Browse failed - An error occurred ISRLC014 Promote failed - The ’to’ data set was
browsing ’aaaaaaaa..bbbbbbbb..ACTLOG’. allocated as an alias. Aliases are not
allowed.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLA221 Parameter required - The LOCATE
command requires a valid type name as ISRLC015 ATTACH failed - ATTACH failed in
a parameter. module aaaaaaaa.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLA222 ’aaaaaaaa’ not located - The type name ISRLC016 ″aaaaaaaa″ not started - The LMF started
’aaaaaaaa’ would be after the end of the task ″aaaaaaaa″ was not found.
displayed list.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC017 Local lock failed - Local lock failed in
ISRLA223 Invalid command - The only valid the SVC.
command on this panel is LOCATE.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC018 SVC GETMAIN failed - GETMAIN
ISRLA224 Invalid parameter - The LOCATE failed in the library management facility
command requires a valid type name as SVC.
a parameter.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC019 SVC FREEMAIN failed - FREEMAIN
ISRLA225 Logging failed - The activity log is failed in the library management facility
defined with an alias data set name. SVC.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC010 Member entry not created - Member ISRLC020 SRB GETMAIN failed - GETMAIN
entry ’aaaaaaaa’ not created. The type failed in the SRB.
does not exist.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC022 SRB purged - The SRB was purged.
ISRLC011 Member entry not created - Member
Explanation: No explanation available at this time.
entry ’aaaaaaaa’ not created. The group
does not exist.
ISRLC023 GETMAIN failed - GETMAIN failed for
Explanation: No explanation available at this time.
a dynamic TLD.
Explanation: No explanation available at this time.
ISRLC024 Member in use - Member is edit locked ISRLC036 Promote failed - User is not current
by ’aaaaaaaa’. updater of member. current updater is
’aaaaaaaa’.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC025 User not authorized - Member ’aaaaaaaa’
could not be edit locked by user. ISRLC037 Abend ’aaaaaaaa’ occurred - ’aaaaaaaa’
abend during the processing of a library
Explanation: No explanation available at this time.
management request.
Explanation: No explanation available at this time.
ISRLC026 Ddname not found in TIOT - Ddname
not found in the TIOT.
ISRLC038 Promote failed - Entry level group
’aaaaaaaa’ could not be found.
ISRLC027 Library not deleted - Library controls
were not deleted. Member controls exist Explanation: No explanation available at this time.
for this library.
Explanation: No explanation available at this time. ISRLC039 Activity log not valid - Activity log for
type ’aaaaaaaa’ must be a sequential data
set.
ISRLC028 Update failed - The group hierarchy is
active. The update was not performed. Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC040 Edit lock failed - The member is in a
controlled library which is not active.
ISRLC029 Project in use - Project is currently
being updated by ’aaaaaaaa’. Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC041 Edit lock failed - Requestor is not an
authorized accessor.
ISRLC030 ″aaaaaaaa″ not active - The LMF address
space ″aaaaaaaa″ is not accepting any Explanation: No explanation available at this time.
requests.
Explanation: No explanation available at this time. ISRLC042 Edit lock failed - The member ″aaaaaaaa″
has a status or owner of ″bbbbbbbb.″.
ISRLC031 LMF start up in progress - The LMF Explanation: No explanation available at this time.
address space initialization is not
complete.
ISRLC043 Member entry not found - Member
Explanation: No explanation available at this time. entry ’aaaaaaaa’ could not be found in
the control file.
ISRLC033 Promote failed - The group ’aaaaaaaa’ is Explanation: No explanation available at this time.
not active.
Explanation: No explanation available at this time. ISRLC044 Promote failed - The ″to″ and ″from″
libraries have incompatible record
formats.
ISRLC034 Promote failed - From a non-controlled
lib. can only promote into an entry level Explanation: No explanation available at this time.
lib.
Explanation: No explanation available at this time. ISRLC045 Unable to promote data - Data contains
a user ttr, but is not a load module.
ISRLC035 Promote failed - Target group ’aaaaaaaa’ Explanation: No explanation available at this time.
could not be found.
Explanation: No explanation available at this time.
ISRLC046 Promote failed - The logical record ISRLC057 Project deleted - Controls for project
lengths are incompatible. ’aaaaaaaa’ were deleted from the control
file.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC047 Promote failed - The ″from″ library is
not allocated. ISRLC058 ENQUEUE failed - Member ’aaaaaaaa’ is
not available.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC048 SVC not installed - The library
management facility SVC is not ISRLC059 Promote failed - The member was not
installed. edit locked.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC049 Promote failed - Promote free is invalid. ISRLC060 Request failed - The project could not
Member does not exist. be locked or freed.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC050 Edit lock failed - Edit lock failed due to ISRLC061 Promote failed - Member ’aaaaaaaa’ is
an invalid condition on group ’aaaaaaaa’. not edit locked by user.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC051 Promote failed - The member is not ISRLC062 Promote failed - Current user for
available for update. desired member is ’aaaaaaaa’.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC052 Promote failed - Authorized promoter ISRLC063 Promote failed - Only predefined
for requested group is ’aaaaaaaa’. members can be promoted into this
hierarchy.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC053 Dist. table deleted - Distribution table
’aaaaaaaa’ was deleted from the control ISRLC064 Promote failed - ’aaaaaaaa’ is the only
file. authorized promoter of undefined
members.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC054 User-set deleted - User-set ’aaaaaaaa’ was
deleted from the control file. ISRLC065 Promote failed - Promote failed due to
invalid ″from″ data set organization.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC055 Type deleted - Controls for type
’aaaaaaaa’ were deleted from the control ISRLC066 Promote failed - Promote after system
file. failure must be identical to previous
promote.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC056 Group deleted - Controls for group
’aaaaaaaa’ were deleted from the control ISRLC067 Member entry not deleted - Member
file. entry ’aaaaaaaa’ is not a predefined
member.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC068 Get close out failed - Get close out ISRLC078 Distribution table error - Distribution
failed on the ″from″ library. table ’aaaaaaaa’ has not been created.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC069 Read error occurred - A read error ISRLC079 Group not found - Group found in
occurred on the ″from″ library. distribution table ’aaaaaaaa’ does not
exist.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC070 Member not found - The ″from″ library
member was not found. ISRLC080 Allocation failed - ″to″ library ’aaaaaaaa’
could not be allocated.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC071 Promote free failed - Member has not
been edit locked or does not exist. ISRLC081 Distribution table error - There are no
groups defined in distribution table
Explanation: No explanation available at this time.
’aaaaaaaa’.
Explanation: No explanation available at this time.
ISRLC072 Project has no groups - Project ’aaaaaaaa’
has no promote hierarchies defined.
ISRLC082 Distribution table error - Group
Explanation: No explanation available at this time.
’aaaaaaaa’ references the wrong
distribution table.
ISRLC073 Invalid hierarchy exists - Group
Explanation: No explanation available at this time.
’aaaaaaaa’ not in a valid hierarchy. Must
be corrected first.
ISRLC083 Distribution table error - Group in dist.
Explanation: No explanation available at this time.
tab. ’aaaaaaaa’ has inconsistent types
with other groups.
ISRLC074 Activity log not valid - Logical record
Explanation: No explanation available at this time.
length for member log ’aaaaaaaa’ is
invalid.
ISRLC084 Invalid user id - Invalid user id for
Explanation: No explanation available at this time.
request in the SVC.
Explanation: No explanation available at this time.
ISRLC075 Promote failed - Authorized promoter or
user-set for predefined member is
’aaaaaaaa’. ISRLC085 Type queue build failed - Type queue
build failed in module ’aaaaaaaa’.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC076 Multiple distrib tables - Hierarchy with
top ’aaaaaaaa’ has more than one dist. ISRLC086 Type queue free failed - Type queue
table defined. free failed in module ’aaaaaaaa’.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC077 Types are not identical - Hierarchy with ISRLC087 Hierarchy already deact - Hierarchy is
top group ’aaaaaaaa’ does not have already deactivated. Deactivate ID is
identical types. ’aaaaaaaa’.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC088 Hierarchy already deact - aaaaaaaa ISRLC098 STOW failed - STOW failed in module
hierarchy(s) already deactivated. They ’aaaaaaaa’.
are not deactivated again.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC099 Member not found - Member ’aaaaaaaa’
ISRLC089 Bad deactivate IDs - Deactivate IDs,top not found. control file/control lib
’aaaaaaaa’,inconsistent. Deactivate and try inconsistent.
again.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC100 Promote failed - Requested version code
ISRLC090 Not a complete activate - aaaaaaaa not in distribution table ’aaaaaaaa’.
hierarchy(s) not activated - they don’t
Explanation: No explanation available at this time.
belong to user.
Explanation: No explanation available at this time.
ISRLC101 Library not deleted - Group ’aaaaaaaa’
references the library as a target library.
ISRLC091 Groups already active - aaaaaaaa
Explanation: No explanation available at this time.
hierarchy(s) are already active.
Explanation: No explanation available at this time.
ISRLC102 Top group not controlled - Top group
’aaaaaaaa’ could not be found in the
ISRLC092 Invalid control block - Invalid control specified library.
block - request could not be processed.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC103 Type not controlled - Type entry
ISRLC093 Invalid hierarchy exists - An invalid ’aaaaaaaa’ could not be found in the
hierarchy exists, there are no valid specified library.
hierarchies defined.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC104 Member not controlled - Member
ISRLC094 Activation failed - Top group ’aaaaaaaa’ ’aaaaaaaa’ could not be found in the
deleted from hierarchy after ACTIVATE specified library.
command.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC105 Promotion successful - ’aaaaaaaa’ was last
ISRLC095 Change not allowed - Another project member successfully processed.
administrator must remove your id.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC106 Promote failed - Record formats of the
ISRLC096 Promote failed - Cannot promote ″from″ and ″to″ groups are incompatible.
″planned overlay″ load modules.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC107 Activ. log not allocated - Activity log
ISRLC097 To lib not controlled - ″to″ group ’aaaaaaaa’ could not be allocated. it may
’aaaaaaaa’ not a controlled library. not be cataloged.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC108 Promote failed - ″To″ data set ’aaaaaaaa’ ISRLC119 Invalid control file - The old control file
must be allocated as partitioned data contains invalid members.
set.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC120 Delete failed - Member was not deleted
ISRLC109 Distribution table error - Group because the controlled library is an
’aaaaaaaa’ references no distribution alias.
table.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC121 Invalid record format - The LMF control
ISRLC111 Promote failed - ″From″ record length is file record format must be variable
greater than ″to″ block size for record blocked. Dd ISRCFIL
format U.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC122 Secondary extents exist - The control file
ISRLC112 Exit type required - Activity log full exit must not have any secondary extents
was requested without specifying exit allocated.
type.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC123 Invalid command - Command is not
ISRLC113 Exit name required - Data set full exit valid. The only valid command is END.
was requested without specifying exit
Explanation: No explanation available at this time.
name.
Explanation: No explanation available at this time.
ISRLC124 Get closeout failed - Close out of control
file failed in module ’aaaaaaaa’.
ISRLC114 Exit type required - Data set full exit
Explanation: No explanation available at this time.
was requested without specifying exit
type.
ISRLC125 Not authorized - You are not authorized
Explanation: No explanation available at this time.
to change a log for project ″aaaaaaaa″.
Explanation: No explanation available at this time.
ISRLC115 Control file not valid - The control file
is not bound to any started task.
ISRLC126 Invalid members found - The new
Explanation: No explanation available at this time.
control file must not contain any
members.
ISRLC116 Control file not valid - The control file
Explanation: No explanation available at this time.
contains controls from a previous
ISPF/PDF version.
ISRLC127 Invalid control file - The old control file
Explanation: No explanation available at this time.
is not a valid control file.
Explanation: No explanation available at this time.
ISRLC117 Exit name required - Activity log full
exit was requested without specifying
exit name. ISRLC128 No updates made - No entries were
found which use activity log ’aaaaaaaa’.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC118 Record format not fixed - The activity
log must have a fixed record format. ISRLC129 Migration successful - Migration of old
control file to new control file was
Explanation: No explanation available at this time.
successful.
Explanation: No explanation available at this time.
ISRLC130 Data set not allocated - The output data ISRLC140 Activity log not valid - The activity log
set could not be allocated by user must have a logical record length of
’aaaaaaaa’. ’aaaaaaaa’.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC131 Data set LRECL too small - The output ISRLC141 Invalid member controls - Group
data set LRECL may result in truncation ’aaaaaaaa’ may have bad member
of records. controls. Activate cannot be done.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLC132 Member list failed - A member list ISRLC142 Invalid member controls - Use member
could not be created for group ’aaaaaaaa’. utilities options 2 or 4 to correct the
problem.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC133 Data set not allocated - Group ’aaaaaaaa’
could not be allocated. ISRLC143 Entries in data set - This hierarchy not
valid until problems in output data set
Explanation: No explanation available at this time.
are fixed.
Explanation: No explanation available at this time.
ISRLC134 Controlled data set full - A controlled
data set is out of space. See your library
administrator. ISRLC144 Controls cleared - All member controls
for this hierarchy have been cleared.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC135 Control file full - The LMF control file
is out of space. See your library ISRLC145 Verify required - Verify or initialize is
administrator. required before hierarchy can be
activated.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC136 Activity log full - The activity log is out
of space. See your library administrator. ISRLC146 Data set not allocated - The output data
set could not be allocated by started
Explanation: No explanation available at this time.
task ’aaaaaaaa’.
Explanation: No explanation available at this time.
ISRLC137 Administrator log full - The
administrator log is out of space. See
your library administrator. ISRLC147 Data set not opened - Group ’aaaaaaaa’
could not be opened.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC138 Write failed - Write failed to output data
set in module ’aaaaaaaa’. ISRLC148 Member name required - A member
name is required when a partitioned
Explanation: No explanation available at this time.
data set is specified.
Explanation: No explanation available at this time.
ISRLC139 Entries in data set - Entries were
recorded in the output data set. Please
review them. ISRLC149 Data set is not a PDS - LMF requires
that group ’aaaaaaaa’ be a partitioned
Explanation: No explanation available at this time.
data set.
Explanation: No explanation available at this time.
ISRLC150 Delete not allowed - Delete not allowed ISRLC160 Member not locked - Project ″aaaaaaaa″
on a member whose status is is an SCLM controlled project.
″Promote-in-process″.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLC161 SCLM warning - The project being
ISRLC151 Group not found - Use VERIFY updated is an SCLM controlled project.
CONTROLS option to determine the
Explanation: No explanation available at this time.
problem.
Explanation: No explanation available at this time.
Messages ISRLA000 through ISRLA229 are listed in
“Chapter 5. Library Management Facility (LMF)
ISRLC152 Allocate failed - Allocate failed in Messages” on page 549.
module ″aaaaaaaa″.
Explanation: No explanation available at this time. ISRLD000 Missing parameters - One or both of
level and volume must be specified for
LMDINIT.
ISRLC153 No members found - No physical
members were found to initialize with Explanation: Either a data set name level or a volume
member controls. or both must be specified for the data set list service.
Explanation: No explanation available at this time. User Response: Correct the LMDINIT command.
ISRLC154 Controls cleared - Member controls that ISRLD001 Insufficient storage - Not enough main
existed for the hierarchy were cleared. storage was available to satisfy request
for LMDINIT.
Explanation: No explanation available at this time.
Explanation: There is not enough storage available to
build the control block for processing LMDINIT.
ISRLC155 No controls exist - No member controls
exist to clear in the LMF hierarchy. User Response: Increase your region size and retry
the request.
Explanation: No explanation available at this time.
ISRLD032 Invalid CONFIRM value - Specify either ISRLE001 Enter group name - Group name is
YES or NO. missing or invalid.
Explanation: For the LMDDISP service, the only valid Explanation: Either no group name was entered on
values for the CONFIRM parameter are YES or NO. the Member Parts List panel or the group name entered
was syntactically incorrect.
Programmer Response: Use YES or NO with the
CONFIRM parameter. User Response: Correct the group value and retry the
request.
ISRLD033 Load failed for ISRUDL - The load of
the data set list utility load module ISRLE002 Enter type qualifier - Type is missing or
(ISRUDL) failed. invalid.
Explanation: The LMDDISP service was unable to Explanation: Either no type name was entered on the
load module ISRUDL. Member Parts List panel or the type name entered was
syntactically incorrect.
User Response: Contact your system programmer.
User Response: Correct the type value and retry the
System Programmer Response: Check the load library
request.
concatenation sequence (ISPLLIB, STEPLIB, and so
forth) to ensure that the library containing ISRUDL is
included. ISRLE003 DSN required - Output data set name
required for option 2.
| ISRLD034 Load failed for ISRUDA - The load of Explanation: When using Member Parts List option 2
| the Library Utility load module (Write Member Parts Data Set), the output data set
| (ISRUDA) failed. must be specified.
| Explanation: The MEMLIST service was unable to User Response: Specify a data set name in the Output
| load module ISRUDA. Data Set field and retry the request.
| User Response: Contact your system programmer.
ISRLE007 Allocate temp DSN failed - A temporary ISRLE014 Error: SPFnnn.OUTLIST - Please delete
output data set could not be allocated. all unneeded SPFnnn.OUTLIST data
sets.
Explanation: Member Parts List attempted to create a
temporary data set to hold the listing requested, but Explanation: Member Parts List attempted to create a
the allocation failed. temporary data set to hold the listing requested, but
could not find a name available to use for the
User Response: There may be no available data set
temporary data set.
names for Member Parts List to use, or an existing data
set that Member Parts List is trying to use may have User Response: Delete all existing data sets that
incorrect characteristics. Delete all existing data sets follow the Member Parts List naming convention, and
that follow the Member Parts List naming convention, retry the request. The data set names generated by
and retry the request. The data set names generated by Member Parts List have one of the following forms:
Member Parts List have one of the following forms: userid.SPFnnn.OUTLIST
userid.SPFnnn.OUTLIST
or
or prefix.userid.SPFnnn.OUTLIST
prefix.userid.SPFnnn.OUTLIST
ISRLE015 Invalid output data set - The output
ISRLE009 Enter valid LANG value - Minimum data set must be record format fixed
valid values are: ASM, COB, FOR/FTN, with record length >= 17.
PAS, PL1/PLI, SCR.
Explanation: The Member Parts List output data set
Explanation: The value entered in the language field must have a record format for Fixed or Fixed-Blocked
was not valid. The supported values and languages are: and a logical record length of 17.
ASM Assembler
User Response: Reallocate the data set with the
COB COBOL
correct characteristics, then retry the request.
FOR or FTN FORTRAN
PAS Pascal
ISRLE020 Enter project name - Project name is ISRLE026 Member name not allowed - A member
missing or invalid. name was specified for a sequential data
set.
Explanation: Either no project name was entered on
the Member Parts List panel or the project name Explanation: The data set specified in the Output Data
entered was syntactically incorrect. Set field is a sequential data set, but a member name
was specified. Member name is not valid for a
User Response: Correct the project value and retry the
sequential data set.
request.
User Response: Either specify a sequential data set
without a member name or a partitioned data set and
ISRLE021 Enter group name - Group name is
member in the Output Data Set field, then retry the
missing or invalid.
request.
Explanation: Either no group name was entered on
the Member Parts List panel or the group name entered
ISRLE027 Member name is required - A
was syntactically incorrect.
partitioned data set was specified with
User Response: Correct the group value and retry the no member name.
request.
Explanation: The data set specified in the Output Data
Set field is a partitioned data set, but no member name
ISRLE022 Enter type qualifier - Type is missing or was specified. A member name is required for a
invalid. partitioned data set.
Explanation: Either no type name was entered on the User Response: Either specify a sequential data set
Member Parts List panel or the type name entered was without a member name or a partitioned data set and
syntactically incorrect. member in the Output Data Set field, then retry the
request.
User Response: Correct the type value and retry the
request.
ISRLE029 Enter valid LANG value - Minimum
valid values are: ASM, COB, FOR/FTN,
ISRLE023 Invalid DSORG - Data set organization PAS, PL1/PLI, SCR.
must be partitioned (PO).
Explanation: The value entered in the language field
Explanation: Input to the Member Parts List function was not valid. The supported values and languages are:
must either be a partitioned data set or a concatenation ASM Assembler
of partitioned data sets. COB COBOL
User Response: Correct the input data set name to FOR or FTN FORTRAN
specify one or more partitioned data sets and retry the PAS Pascal
request. PL1 or PLI PL/I
SCR Script
ISRLE024 Skeleton not found - Skeleton for User Response: Enter a valid language value and
aaaaaaaa not found in skels data set. retry the request.
ISRLE025 DSN required - Data set name is ISRLI000A Messages ISRLI000 through ISRLI069
required for option 2. are listed in “Chapter 5. Library
Management Facility (LMF) Messages”
Explanation: When using Member Parts List option 2 on page 549.
(Write Member Parts Data Set), the output data set
must be specified. Explanation: This is an informational message.
ISRLK000A Messages ISRLK000 through ISRLK049 ISRLS001 Incomplete specification - Must specify
are listed in “Chapter 5. Library project, group1, and type for an ISPF
Management Facility (LMF) Messages” library.
on page 549.
Explanation: The LMINIT service was incorrectly
Explanation: This is an informational message. invoked. An incomplete ISPF library name (Project,
Group(s), and Type) was specified.
ISRLL000A Messages ISRLL000 through ISRLL309 User Response: Contact the responsible programmer.
are listed in “Chapter 5. Library
Programmer Response: Ensure that the project, group,
Management Facility (LMF) Messages”
and type are all correctly specified. If you are using a
on page 549.
compiled language, check to see that values shorter
Explanation: This is an informational message. than the maximum possible length are terminated with
at least one blank.
| ISRLO999 Licensed Materials - Property of IBM
| 5647- A01 (C) Copyright IBM Corp. 1980, ISRLS002 Invalid ENQ requirement - Specify
| 2000. All rights reserved. US either SHR, EXCLU, SHRW, or MOD.
| Government Users Restricted Rights -
Explanation: An LMINIT service was issued with an
| Use, duplication or disclosure restricted
invalid or missing value for the ENQ parameter.
| by GSA ADP Schedule Contract with
| IBM Corp. User Response: Contact the responsible programmer.
| Explanation: This is an informational message. Programmer Response: Ensure that the LMINIT
service specifies either SHR, EXCLU, SHRW, or MOD
for the ENQ parameter. In compiled languages, it is a
ISRLP100A Messages ISLRP100 through ISRLP109
good idea to pad the SHR parameter with a blank.
are listed in “Chapter 5. Library
Management Facility (LMF) Messages”
on page 549. ISRLS003 Invalid data set org - Data set is not
sequential or partitioned. Not supported
Explanation: This is an informational message.
by ISPF.
Explanation: An LMINIT service was issued for a data
ISRLQ000A Messages ISLRQ000 through ISRLQ039
set that has an organization not supported by ISPF.
are listed in “Chapter 5. Library
Management Facility (LMF) Messages” User Response: Specify another data set, or contact
on page 549. the responsible programmer.
Explanation: This is an informational message. Programmer Response: Ensure that the data sets used
by your application are either sequental data sets or
partitioned data sets.
ISRLS000 No data set specified - Must specify
either an ISPF library, data set, or
ddname for LMINIT. ISRLS004 Insufficient storage - Not enough main
storage was available to satisfy request.
Explanation: The LMINIT service was incorrectly
invoked. Either a complete ISPF library name (Project, Explanation: An LMINIT service was unable to obtain
Group(s), and Type), a data set name, or a ddname the storage it needed to complete.
must be specified.
User Response: Try to reduce the number of programs
User Response: Contact the responsible programmer. already running while this program is running. If that
is not feasible, try logging on with a larger region size.
Programmer Response: If you are using the ISPF
library keywords, insure that the project, group, and
type are all correctly specified. If you are using the data ISRLS005 Free storage failed - Free main storage
set or ddname keywords, insure that the values you are request failed.
passing to the service are complete and correct.
Explanation: Storage obtained by an ISPF service
If you are using a compiled language, check to see that could not be freed.
values shorter than the maximum possible length are
terminated with at least one blank. User Response: Contact the responsible programmer.
Programmer Response: Ensure 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 ISRLS010 Ddname not found - Ddname ’aaaaaaaa’
data sets can be allocated mod for not found.
LMINIT.
Explanation: An LMINIT by ddname was requested,
Explanation: An LMINIT service was issued to but the ddname specified is not currently allocated.
allocate a data set for disposition MOD but the data set
User Response: Contact the responsible programmer.
is not sequential.
Programmer Response: If the ddname specified is
User Response: Contact the responsible programmer.
correct, use the TSO ALLOCATE command to allocate
Programmer Response: Ensure that the application is the correct data sets to that ddname. If the ddname
allocating only sequential data sets with disposition specified is not correct, make the necessary corrections.
MOD.
ISRLS011 Invalid data set status - Data set is not
ISRLS007 Member name not allowed - Member allocated as NEW, OLD, SHARED, or
name not allowed in the specification of MOD.
data set parameter.
Explanation: An LMINIT by ddname was requested,
Explanation: An LMINIT service was issued with the but the ddname was allocated with a status other than
member name specified in the data set parameter. This NEW, OLD, SHARED, OR MOD.
is not supported by ISPF.
User Response: Contact the responsible programmer.
User Response: Contact the responsible programmer.
Programmer Response: Reallocate the ddname using a
Programmer Response: Change the application to correct status value and retry the LMINIT request.
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
| ISRLS012 Invalid concatenation - More than 16
BROWSE services.
| concatenated data sets not supported by
| ISPF.
Programmer Response: Change the LMPROM service, Programmer Response: Add an LMOPEN invocation
eliminating the TOMEMBER operand. The member for the data ID used in the LMMFIND service.
names cannot be changed when multiple members are System Action: LMMFIND ends with a return code of
being promoted. 12.
ISRLS037 Invalid parameter - With all or pattern ISRLS042 Data set not partitioned - LMMFIND
specified the ″to″ member parameter is service data set to be partitioned data
not valid. set.
Explanation: A pattern or more than one member Explanation: The LMMFIND service is used to find a
name was specified on the FRMEMBER operand of the member of a partitioned data set. The data set
LMPROM service, and the TOMEMBER operand was represented by the given data ID is not partitioned.
also specified. When a pattern or multiple names are
specified, the TOMEMBER operand is not valid. User Response: Contact the responsible programmer.
Programmer Response: Change the LMPROM service, Programmer Response: Change the DATAID
eliminating the TOMEMBER operand. The member parameter to the DATAID for the partitioned data set
names cannot be changed when multiple members are to find the member name.
being promoted. System Action: LMMFIND ends with return code 12.
ISRLS038 Invalid member name - ″From″ member ISRLS043 Member not found - Specified member
name ’aaaaaaaa’ is invalid. ’aaaaaaaa’ not found in data set(s).
Explanation: The source (or ″from″) member name Explanation: The given member was not found in the
(aaaaaaaa) specified on the LMPROM service is data set(s) specified by the given data ID.
syntactically incorrect.
User Response: Contact the responsible programmer.
Programmer Response: Correct the member name,
then reissue the LMPROM service. Programmer Response: The response depends upon
the design of the dialog. This may be an expected
response.
System Action: LMMFIND ends with return code 8.
ISRLS044 Severe error - Unexpected return code ISRLS048 Insufficient storage - Insufficient virtual
aaaaaaaa from common data set BLDL storage was available to search the
routine ISPCDB. directory.
Explanation: An unexpected error occurred during Explanation: There is not enough virtual storage for
BLDL processing. The return code may be one of the ISPF to be able to read the directory.
following:
User Response: Increase virtual storage.
24 OPEN was unsuccessful.
28 OBTAIN was unsuccessful.
32 Other BLDL error. ISRLS049 Promote successful - Member or data set
promoted successfully.
User Response: Contact the responsible programmer.
Explanation: This is an informational message.
Programmer Response: Verify the input parameters to
LMMFIND. Try accessing the member through Browse
(option 1) to verify that the member exists as expected ISRLS054 Incomplete specification - The project
in the data set(s). name must be specified.
System Programmer Response: Recover the data set, Explanation: The PROJECT parameter is not specified
if necessary. for the LMACT or LMDEACT service.
System Action: LMMFIND ends with return code 20. User Response: Contact the responsible programmer.
Programmer Response: Specify the PROJECT
ISRLS045 Severe error - I/O error trying to close parameter for the LMACT or LMDEACT service.
out on read.
System Action: LMACT or LMDEACT ends with
Explanation: This is an informational message. return code 12.
System Action: LMMFIND ends with return code 20.
ISRLS055 Incomplete specification - The group
name must be specified.
ISRLS046 Not open for input - LMMFIND service
requires the data set to be opened for Explanation: The GROUP parameter is not specified
input. for the LMACT or LMDEACT service.
Explanation: The data ID for the LMMFIND service User Response: Contact the responsible programmer.
must be opened for input before invoking the
LMMFIND service. Programmer Response: Specify the GROUP parameter
for the LMACT or LMDEACT service.
User Response: Contact the responsible programmer.
System Action: LMACT or LMDEACT ends with
Programmer Response: Change the OPTION to return code 12.
INPUT on the LMOPEN service for the specified data
ID.
ISRLS056 Invalid project name - Project must be
System Action: LMMFIND ends with return code 12. up to 8 alphanumeric chars (first must
be an alphabetic character).
ISRLS047 I/O error finding member - A permanent Explanation: The Project parameter contains invalid
I/O error was detected when searching characters for the LMACT or LMDEACT service.
the directory.
User Response: Contact the responsible programmer.
Explanation: BLDL ended with return code 8.
Programmer Response: Specify a valid project
User Response: Contact the responsible programmer. parameter for the LMACT or LMDEACT service.
Programmer Response: Verify the input parameters to System Action: LMACT or LMDEACT ends with
LMMFIND. Try accessing the member through Browse return code 12.
(option 1) to verify that the member exists as expected
in the data set(s).
ISRLS057 Invalid group name - Group must be up
System Programmer Response: Recover the data set, to 8 alphanumeric chars (first must be
if necessary. an alphabetic character) or ’*’.
System Action: LMMFIND ends with return code 8. Explanation: The group parameter contains invalid
characters for the LMACT or LMDEACT service.
User Response: Contact the responsible programmer.
ISRLS061 Data set not opened - Data set is not System Action: LMGET service ends with return code
opened for LMGET service. 12.
User Response: Contact the responsible programmer. User Response: Contact the responsible programmer.
Programmer Response: On the LMOPEN service for Programmer Response: Set the DATALOC variable to
the specified data ID, specify the INPUT option. a valid address.
System Action: LMGET service ends with return code System Action: LMPUT service ends with return code
12. 12.
ISRLS070 Invalid mode specified - Specify either ISRLS075 DATALOC var out of range - For MOVE
MOVE or INVAR for mode parameter. mode, DATALOC variable must have
value <= (2**31)-1.
Explanation: The valid modes for the LMPUT service
are: Explanation: For the LMPUT service, the DATALOC
variable must have a value of at least 1 but less than
MOVE Moves the data from the address specified by 2 147 483 647.
the DATALOC parameter
User Response: Contact the responsible programmer.
INVAR Stores the data from an ISPF dialog variable
specified by the DATALOC variable. Programmer Response: Set the DATALOC variable to
a valid address.
User Response: Contact the responsible programmer.
System Action: LMPUT service ends with return code
Programmer Response: Specify the MODE parameter 12.
as MOVE or INVAR.
System Action: LMPUT service ends with return code ISRLS076 I/O error on write - I/O error
12. encountered while writing data set.
Explanation: A severe error occurred while attempting
ISRLS071 Data set not opened - Data set is not to write to the the data set represented by the DATAID
opened for LMPUT service. parameter on the LMPUT service.
Explanation: The data set represented by the DATAID User Response: Contact the responsible programmer.
parameter of LMPUT must be open.
Programmer Response: Browse the data set to verify
User Response: Contact the responsible programmer. that it is not damaged.
Programmer Response: Open the data set for the System Programmer Response: Recover data, if
DATAID using the LMOPEN service before calling necessary.
LMPUT.
System Action: LMPUT service ends with return code
System Action: LMPUT service ends with return code 12.
12.
ISRLS077 Invalid record length - Record length ISRLS083 Member not found - The specified
must be positive and between 1 and member name ’aaaaaaaa’ not found in
(2**15)-1. the directory.
Explanation: For LMPUT, the DATALEN parameter Explanation: The requested member does not exist for
must not be negative, zero, or greater than 32 767. the LMMDEL or LMMREN service.
User Response: Contact the responsible programmer. User Response: Contact the responsible programmer.
Programmer Response: Set the DATALEN parameter Programmer Response: Ensure that the correct
to a valid data length. member name is requested. No action is usually
necessary for LMMDEL.
System Action: LMPUT service ends with return code
12. System Action: Service ends with return code 8.
ISRLS080 Invalid member name - Member name ISRLS084 Member added - Member added to the
’aaaaaaaa’ is invalid. data set. It did not previously exist.
Explanation: Member name parameter contains Explanation: This is an informational message. The
invalid characters. LMMREP service could not find a member to replace.
The member is added to the data set.
User Response: Contact the responsible programmer.
Programmer Response: Enter a valid member name in
ISRLS085 Not partitioned data set - Data set must
the member name parameter.
be partitioned for LMMADD, LMMREP,
System Action: Service ends with return code 12. LMMDEL or LMMREN.
Explanation: The LMMADD, LMMREP, LMMDEL,
ISRLS081 Invalid STATS parameter - STATS and LMMREN services all operate on members of
parameter is invalid. Specify either YES partitioned data sets.
or NO.
User Response: Contact the responsible programmer.
Explanation: The STATS parameter must be YES, NO,
Programmer Response: Either ensure that the data set
or blank.
for the requested data ID is partitioned, or use the
User Response: Contact the responsible programmer. appropriate service to operate on sequential data sets.
For example, to rename an entire data set, use the
Programmer Response: Enter a valid STATS LMRENAME service.
parameter.
System Action: Service ends with return code 8.
System Action: Service ends with return code 12.
ISRLS110 I/O error - I/O error closing data set Explanation: The Option parameter of the LMMLIST
represented by data ID ’aaaaaaaa’. service must be LIST, FREE, SAVE, or blank. Blank
defaults to LIST.
Explanation: An error occurred while attempting to
close the data set. User Response: Contact the responsible programmer.
User Response: Verify that the data set is not Programmer Response: Enter a valid value for the
damaged. OPTION parameter.
System Programmer Response: Back up the data sets System Action: LMMLIST service ends with return
if necessary. code 12.
System Programmer Response: Back up the data set if System Action: Service ends with return code 12.
necessary.
System Action: Service ends with return code 20. ISRLS122 Data set not open - LMMLIST requires
prior successful completion of
LMOPEN.
ISRLS112 Severe error - Directory block size
exceeds maximum of 256. Explanation: The LMOPEN service must be invoked
against the requested data ID before invoking the
Explanation: The PDF common member list routine LMMLIST service.
detected a data set that had a directory block greater
than 256 bytes, the maximum supported by PDF. User Response: Contact the responsible programmer.
User Response: Contact your system programmer. Programmer Response: Use the LMOPEN service to
ISRLS132 Member name too long - Member name ISRLS136 Invalid statistics value - Initial number
must be 1 to 8 characters long. of records must be a positive number
from 0 to 65535.
Explanation: The member name variable must be able
to contain a value with a length of 8 characters. Explanation: The LMMSTATS initial number of
records parameter contains an invalid value.
User Response: Contact the responsible programmer.
User Response: Contact the responsible programmer.
Programmer Response: If you are using a program
interface, declare the member name variable to be 8 Programmer Response: Set the initial number of
characters long. If you are using a command interface, records to be a positive integer between 0 and 65 535,
ensure that the member name variable contains 8 inclusive.
characters. Pad the member name with blanks if
System Action: The LMMSTATS service ends with
necessary.
return code 12.
System Action: The LMMLIST service ends with
return code 8.
ISRLS137 Invalid statistics value - Number of
modified records must be a positive
ISRLS133 Invalid statistics value - Version number number from 0 to 65535.
must be a positive number from 1 to 99.
Explanation: The LMMSTATS number of modified
Explanation: The LMMSTATS version number records parameter contains an invalid value.
parameter contains an invalid value.
User Response: Contact the responsible programmer.
User Response: Contact the responsible programmer.
Programmer Response: Set the number of modified
Programmer Response: Set the version number to be records to be a positive integer between 0 and 65 535,
a positive integer between 1 and 99, inclusive. inclusive.
System Action: LMMSTATS service ends with return System Action: The LMMSTATS service ends with
code 12. return code 12.
ISRLS134 Invalid statistics value - Modification ISRLS138 Invalid statistics value - Creation date or
level must be a positive number from 0 last modified date ’aaaaaaaa’ is out of
to 99. range.
Explanation: The LMMSTATS modification level Explanation: The creation date does not exist. Either
parameter contains an invalid value. the month value is greater than 12, or the day value
exceeds the number of days for the given month.
User Response: Contact the responsible programmer.
User Response: Contact the responsible programmer.
Programmer Response: Set the modification level to
be a positive integer between 0 and 99, inclusive. Programmer Response: Enter a valid creation date.
System Action: The LMMSTATS service ends with System Action: The LMMSTATS service ends with
return code 12. return code 12.
ISRLS135 Invalid statistics value - Current number ISRLS139 Invalid statistics value - Last modified
of records must be a positive number time ’aaaaaaaa’ is out of range.
from 0 to 65535.
Explanation: The last modified time does not exist.
Explanation: The LMMSTATS current number of Either the hours are not between 00 and 23 inclusive,
records parameter contains an invalid value. or the minutes are not between 00 and 59 inclusive.
User Response: Contact the responsible programmer. User Response: Contact the responsible programmer.
Programmer Response: Set the current number of Programmer Response: Enter a valid creation date.
records to be a positive integer between 0 and 65 535,
System Action: The LMMSTATS service ends with
inclusive.
return code 12.
System Action: The LMMSTATS service ends with
return code 12.
ISRLS155 Invalid ″to″ data set - The ″from″ data ISRLS159 Invalid ″to″ data set - ″To″ data set must
set is controlled. Do not specify ″to″ be ’controlled’ library.
data set.
Explanation: The TO library must be controlled by
Explanation: If the FROM library is LMF-controlled, LMF.
then LMF uses the control file to determine the TO
User Response: Contact the responsible programmer.
library. Do not specify the TO library.
Programmer Response: Specify the correct
User Response: Contact the responsible programmer.
LMF-controlled library into which the data is to be
Programmer Response: If the FROM library is promoted.
controlled, do not specify the TO library.
System Action: The LMPROM service ends with
System Action: The LMPROM service ends with return code 12.
return code 12.
ISRLS160 Close data set failed - Close the control
ISRLS156 No ″to″ group name - ″From″ data set file unsuccessfully.
not controlled. Must specify the ″to″
Explanation: The close of the control file failed.
group name.
User Response: If the problem persists, contact the
Explanation: If the FROM data set is not controlled by
system programmer.
LMF, then the TO project and type default to the
FROM project and type. However the TO group must System Programmer Response: Ensure that the
be specified, since LMF cannot determine this control file is not damaged and can be accessed from
information. the system.
User Response: Contact the responsible programmer.
ISRLS161 Free storage failed - Free the storage of
Programmer Response: Specify TO group and, if
TFD for the control file unsuccessfully.
necessary, the TO project and TO type.
Explanation: The storage for the TFD of the control
System Action: The LMPROM service ends with
file could not be freed.
return code 12.
User Response: If the problem persists, contact the
system programmer.
ISRLS157 No ″to″ member name - ″From″ data set
is sequential. Must specify the ″to″ System Programmer Response: If the problem
member name. persists, contact IBM support.
Explanation: The LMPROM service requires the TO
member name be specified when the FROM data set is ISRLS162 Close data set failed - Close ″from″ data
sequential. set failed.
User Response: Contact the responsible programmer. Explanation: The close of the FROM data set was not
successful.
Programmer Response: Specify the TO member name
for the LMPROM service. User Response: If the problem persists, contact the
system programmer.
System Action: The LMPROM service ends with
return code 12. System Programmer Response: Ensure that the FROM
data set is not damaged and can be accessed from the
system.
ISRLS158 Invalid ″to″ data set - ″From″ data set is
dsname. Must specify ″to″ ISPF library.
ISRLS163 Free data set failed - Free ″from″ data
Explanation: The LMPROM service requires that if the
set failed.
FROM data is specified as a data set, then the TO data
must be specified by project, group, and type. Explanation: The allocation of the FROM data set
could not be completed successfully.
User Response: Contact the responsible programmer.
User Response: If the problem persists, contact the
Programmer Response: Either specify the FROM data
system programmer.
as an ISPF library, or specify project, group, and type of
the TO data set. System Programmer Response: Ensure that the FROM
data set is not damaged and can be accessed from the
System Action: The LMPROM service ends with
system.
return code 12.
ISRLS164 Data set is not active - ″aaaaaaaa″ ISRLS170 Alias name not supported - LMERASE
controlled library is not active. service does not support erasing alias
data sets.
Explanation: The LMF controlled library has not been
activated. Explanation: The name that was specified is an alias.
LMERASE does not support alias names.
User Response: Notify the library administrator. The
library administrator should use option 8.4 to activate User Response: Use the data set name instead of the
the library. alias name.
System Action: The alias and data sets are not
ISRLS165 Data set not entry level - ″To″ controlled deleted.
library is not an entry level.
Explanation: Promote from a non-controlled data set ISRLS171 Data set not expired yet - The
must be into an entry level group of a controlled PURGE(YES) keyword must be used to
library. delete the data set.
User Response: Update the promote to promote into Explanation: The data set has an expiration date that
an entry level group. has not yet been reached. The PURGE(YES) keyword
must be specified to delete this data set.
ISRLS166 Invalid promotion action - ″From″ data User Response: Specify the PURGE(YES) keyword to
set is controlled. Promote action must be delete the data set.
MOVE.
System Action: The data set is not deleted.
Explanation: Promote action must be MOVE when
promoting from a controlled data set.
ISRLS172 Obtain macro failed - Obtain format 1
User Response: Update the promote to specify MOVE. data set control block failed.
Explanation: LMERASE was not able to access the
ISRLS167 No target group - ″From″ controlled format 1 data set control block.
library is the top group.
User Response: Verify that the data set name is valid
Explanation: The group specified as the FROM group and available.
is the top group in the library hierarchy. Since there is
System Programmer Response: Verify that the device
no higher group in the hierarchy, promotion cannot
containing the data set is online and can be accessed.
take place.
Verify that the catalog containing the data set is also
User Response: Verify that the correct group is being available.
specified for promotion.
System Action: The data set is not deleted.
ISRLS190 No new name specified - Must specify User Response: Verify that both data sets specified to
either NEWPROJ, NEWGROUP, or the LMRENAME service can be accessed through the
NEWTYPE for LMRENAME. catalog. Notify the system programmer of any catalog
problems.
Explanation: A new name was not supplied for the
LMRENAME command. One or more of the following System Programmer Response: Ensure that the
parameters must be supplied: NEWPROJ, NEWGROUP, catalog for the data sets specified to the LMRENAME
NEWTYPE. service exists, is open, and that the do not allocate bit is
not set.
User Response: Specify at least one of the values used
to form the new data set name. System Action: The data set is not renamed.
ISRLS191 Invalid new name - ’aaaaaaaa’ specified Explanation: The user is not authorized to update the
for ’bbbbbbbb’ is an invalid name. catalog with a new data set name.
Explanation: The value aaaaaaaa for the bbbbbbbb User Response: Verify that you have authority to
parameter forms an invalid data set name. update the data set name in the catalog.
User Response: Change the value for the bbbbbbbb Programmer Response: Ensure that the user has
parameter to specify a value that will create a valid authority to update the data set name in the catalog.
data set name.
System Action: The data set is not renamed.
System Action: The data set is not renamed.
ISRLS198 No space in catalog - There is ISRLS203 New name already exists - A data set
insufficient space on the catalog data with the new name already exists on the
set. volume.
Explanation: There is not enough space in the catalog Explanation: A data set with the same name as the
that would contain the new data set name to add it to new data set name already exists on the same volume.
the catalog. The existing data set may be uncataloged.
User Response: Notify the system programmer that User Response: Either remove the existing data set
the catalog does not have enough space. with the same name as the new data set name, or
specify a different new name.
System Programmer Response: Ensure that the
catalog for the new data set name is large enough.
ISRLS204 Permanent I/O error - Permanent I/O
System Action: The data set is not renamed.
error, invalid format-1 DSCB found, or
error from CVAF.
ISRLS199 Uncatalog error - Uncatalog failed for
Explanation: A permanent I/O error occurred when
data set aaa(44).
accessing the format-1 DSCB in the VTOC of the
Explanation: The old data set name aaa(44) could not volume of the data set that is being renamed.
be uncataloged because it could not be found in the
User Response: Notify the system programmer.
catalog.
System Programmer Response: Check the volume for
User Response: Verify that the old data set name was
I/O errors.
specified correctly.
System Programmer Response: Ensure that there are
ISRLS205 Volume not mounted - Volume not
no problems with the catalog for the old data set name.
mounted or no device available to
mount the volume.
ISRLS200 Data set not catalogued - Catalog error,
Explanation: The volume that contains the data set
Rtn code=aaaaaaaa (dec), r0=bbbbbbbb
being renamed is not mounted to the system.
(hex), r1=cccccccc (hex).
User Response: Mount the volume containing the
Explanation: An error occurred while attempting to
data set.
catalog or uncatalog a data set.
User Response: Contact the system programmer.
ISRLS206 Volume not mounted - The operator is ISRLS212 Members not replaced - aaaaaaaa
unable to mount the volume. members not replaced, bbbbbbbb
members cccccccc.
Explanation: The volume that contains the data set
being renamed is not mounted to the system. The Explanation: Members of the same name exist in the
mount request failed. source and target data sets. The members with the
same name as those in the target data set were not
User Response: Contact the system operator to
replaced since the REPLACE option was not specified.
determine the reason that the volume could not be
mounted. User Response: Either specify the REPLACE option or
specify a TOMEM name that does not match an
existing member in the target data set.
ISRLS207 Data set in use - Data set not renamed
because it is being used.
ISRLS213 ’To’ member in use - aaaaaaaa members
Explanation: The data set is currently allocated to a
not bbbbbbbb, cccccccc members bbbbbbbb
ddname.
Explanation: Target members of the copy or move
User Response: Ensure that you do not have the data
were in use.
set allocated to a ddname and that other users are not
using the data set. User Response: Ensure that you or another user are
not editing or in some other way using the member
that is the target of the operation.
ISRLS208 Authorization failed - Data set is RACF
protected. The user is not alter
authorized. ISRLS214 ’From’ member in use - aaaaaaaa
members not bbbbbbbb, cccccccc members
Explanation: The user does not have sufficient
bbbbbbbb
authority to rename the data set. ALTER authority is
required for data sets that are RACF protected. Explanation: Members were not copied or moved
since they were in use.
User Response: Ensure that you are given sufficient
authority to rename the data set. Authority is required User Response: Ensure that the members in the
for both the old and new data set names. FROM data set are not in use by edit or another utility.
ISRLS209 Rename error - Rename error, Rtn ISRLS260 Group not activated - LMHIER - group
code=aaaaaaaa (dec), status code=bbbbbbbb was found but not activated in
(dec). hierarchy.
Explanation: The rename service failed with return Explanation: No explanation available at this time.
code aaaaaaaa and status code bbbbbbbb.
User Response: Contact the system programmer. ISRLS261 Project not found - LMHIER - project
was not found in hierarchy.
System Programmer Response: Verify that the catalog
for the new and old data set names and the VTOC for Explanation: No explanation available at this time.
the volume containing the data set can be read and
updated.
ISRLS262 Invalid parameter value - LMHIER -
’aaaaaaaa’ is not a valid parameter value.
ISRLS211 Invalid ISPF libraries - Concatenated
Explanation: No explanation available at this time.
libraries must have same project and
type values.
ISRLS263 Severe error occurred - LMHIER - a
Explanation: All data sets in the ddname
severe error occurred while processing
concatenation must have the same project (high level
request.
qualifier) and type (last qualifier).
Explanation: No explanation available at this time.
User Response: Ensure that the data sets concatenated
to the ddname all have the same project and type
values. ISRLS264 Group not found - LMHIER - group was
not found in hierarchy.
Explanation: No explanation available at this time.
ISRLS265 VDEFINE error - LMHIER - a severe ISRLS280 Invalid type - LMREVIEW - type must
error occurred during VDEFINE. be 1-8 alphanumeric characters, the first
alphabetic.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLS270 Invalid control type - LMREVIEW -
control type must be LIBRARY or ISRLS281 Member name required - LMREVIEW -
MEMBER. member name is required if member
controls requested.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLS271 Data set or data ID req. - LMREVIEW -
data set name or data-id is required for ISRLS282 Invalid member name - LMREVIEW -
output data set. member must be 1-8 alphanumeric
characters, the first alphabetic.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLS272 Incompatible parameters - LMREVIEW -
data set name and data-id cannot both ISRLS283 DATAMEMB required - LMREVIEW -
be used. output data member is required if data
ID is partitioned.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLS273 Invalid data set name - LMREVIEW -
data set name is not valid. ISRLS284 Datamemb invalid - LMREVIEW - data
member must be 1-8 alphanumeric
Explanation: No explanation available at this time.
characters, the first alphabetic.
Explanation: No explanation available at this time.
ISRLS274 Data-id does not exist - LMREVIEW -
use LMINIT service to create a data-id.
ISRLS285 Data-id is concatenation - LMREVIEW -
Explanation: No explanation available at this time.
data ID must be for a single library.
Explanation: No explanation available at this time.
ISRLS275 Data-id is not open - LMREVIEW - use
LMOPEN service to open a data-id.
ISRLS286 Invalid project name - LMREVIEW -
Explanation: No explanation available at this time.
project must be 1-8 alphanumeric
characters, the first alphabetic.
ISRLS276 Project name required - LMREVIEW -
Explanation: No explanation available at this time.
enter name of controlled project.
Explanation: No explanation available at this time.
ISRLS287 Datamemb not allowed - LMREVIEW -
output data set is sequential.
ISRLS277 Group name required - LMREVIEW -
Explanation: No explanation available at this time.
enter name of controlled group.
Explanation: No explanation available at this time.
ISRLS288 Datamemb not allowed - LMREVIEW -
data set has member name imbedded.
ISRLS278 Invalid group name - LMREVIEW -
Explanation: No explanation available at this time.
group name must be 1-8 alphanumeric
characters, the first alphabetic.
ISRLS289 Gen load failed - LMREVIEW - Gen
Explanation: No explanation available at this time.
load of ISRLALIN failed.
Explanation: No explanation available at this time.
ISRLS279 Type required - LMREVIEW - enter
controlled type.
Explanation: No explanation available at this time.
Explanation: An I/O error occurred during a write to System Programmer Response: Determine if the
data set request.
ISRLS322 LMCOMP recursion error - Error User Response: Contact the responsible programmer.
attempting to use LMCOMP in a Programmer Response: Determine the reason for the
recursive fashion. failure.
Explanation: Your installation-defined compress user
exit routine identified a recursion error. ISRLS328 Compress exit error - Unable to execute
User Response: Contact the responsible programmer. compress exit.
Programmer Response: Verify the compress exit logic. Explanation: ISPF was unable to execute your
installation-defined compress exit.
ISRLS323 Compress failed - ISPF was unable to User Response: Contact the responsible programmer.
compress specified data set. Programmer Response: Verify the user exit exists and
Explanation: ISPF received a non-zero return code can be accessed.
from IEBCOPY when attempting to compress a data set
through the LMCOMP service. ISRLS329 Severe error - Unable to continue
User Response: The IEBCOPY messages were written LMCOMP service. Compress aborted.
to DDNAME ISPLSTx (where x is the logical screen Explanation: A severe error caused the compress to be
number that the request was issued from) if the aborted.
ISPLSTx DDNAMEs were preallocated before entering
ISPF, or to a data set named ’user ID.SPFLISTx.CNTL’. User Response: Contact your system programmer.
Refer to these messages for details on the IEBCOPY System Programmer Response: This is likely to be the
failure. result of a system failure. Isolate the cause of the error.
ISRLS324 Compress exit error - Unable to allocate ISRLS331 Directory error - Directory error on
data set while using the compress exit. member ’aaaaaaaa’.
Explanation: Your installation-defined user exit issued Explanation: An attempt to STOW the member failed.
a data set allocation error.
User Response: Contact your system programmer.
User Response: Contact the responsible programmer.
System Programmer Response: Check for a system
Programmer Response: Verify the data set allocation failure, such as a faulty pack.
logic in your compress exit.
Programmer Response: Verify that all data sets used User Response: Refer to the IEBCOPY listing and
documentation for assistance in debugging the error.
ISRLS333 Directory full - Directory full; unable to ISRLS337 Invalid open - Data set not opened for
STOW member ’aaaaaaaa’. input.
Explanation: The directory entries for the data set Explanation: The data set was opened but not for
have been filled. input.
User Response: If you are able: Programmer Response: If the LMMOPEN service was
v Copy the allocation attributes of the data set. used, verify that the data set was opened for input.
v Allocate a new data set.
v Copy the members. ISRLS338 Data set not partitioned - Sequential
data sets are not valid with the
v Delete or rename the old data set.
LMMSTATS service.
v Name the new data to the previous name of the old
data set. Explanation: The LMMSTATS service requires that the
data set be partitioned.
ISRLS334 RECFM = U not supported - Undefined User Response: Reallocate the data set as partitioned.
record formats are not supported in the
’aaaaaaaa’ service. ISRLS339 Compress failed - Compress done by the
Explanation: Record format U (undefined) is not compress exit failed.
allowed for the aaaaaaaa. service. Explanation: The installation-written compress exit
User Response: Determine the correct record format failed.
for this data set. User Response: Attempt the compress again. If the
failure recurs, contact your system programmer.
ISRLS335 IEBCOPY failed - IEBCOPY failed System Programmer Response: Verify that no system
during copy. An IEBCOPY listing was failures occurred.
created and is allocated to the ddname
reflected by SHARED pool variable
ZCMPLSTF. ISRLS340 Invalid record format - An undefined
record format can only exist as a
Explanation: A non-zero return code was returned partitioned data set.
from IEBCOPY during the Move or Copy operation.
PDF allocated the IEBCOPY error listing to an Explanation: A record format of U is only valid for
internally generated ddname, and placed the ddname partitioned data sets.
into ISPF dialog variable ZCMPLSTF. The error list can User Response: Verify that the number of directory
be displayed by doing the following: entries is greater than 0.
v Issue a VGET from the SHARED pool for variable
ZCMPLSTF
ISRLS341 Open error - FROM sequential data sets
v Issue an LMINIT, passing the value of ZCMPLSTF in cannot be open prior to using
the LMINIT ddname parameter. LMMOVE.
v Issue the BROWSE service, passing the data-id
created by LMINIT Explanation: The FROM data set was opened prior to
the LMMOVE service call.
RE>User response follows
User Response: Contact the responsible programmer.
User Response: Refer to the IEBCOPY listing and
documentation for assistance in debugging the error. Programmer Response: Verify that a previous service
did not leave the FROM data set open.
ISRLS343 DISP=MOD invalid - Disposition of ISRLS351 Data set unmovable - Input data set
mod not allowed for packed data sets. cannot be moved.
Explanation: Packed data sets are not allowed a Explanation: Unable to move this data set.
disposition of MOD.
User Response: Check that the data set you are
User Response: Either change the disposition or attempting to move is not the input data set.
remove the pack request.
ISRLS352 Output blksize too small - Output data
ISRLS344 Pack failed - Specifying DISP=MOD is set block size must be equal or greater
invalid if ″to″ data set has packed data. than input.
Explanation: When using LMCOPY and LMMOVE Explanation: A MOVE or COPY has been requested in
services and appending data to a sequential data set by which the TO data set has a smaller block size than the
using a TO data set disposition of MOD, the target FROM data set.
output data set cannot be an existing data set that
User Response: Reallocate the TO data set or choose
contains packed data.
another data set.
User Response: Either unpack the data in the target
sequential data set, or specify a different target data set
ISRLS354 ’aaaaaaaa’ terminated - ’aaaaaaaa’ has been
that is not packed.
terminated due to truncation continue
processing.
ISRLS345 Read error on get - Unable to read the
Explanation: Some records may be truncated in the
first record from the target sequential
TO data set due to block size incompatibility.
file.
User Response: Either accept the truncation or cancel
Explanation: When copying to a sequential data set,
the action.
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 ISRLS355 Member name is blank - Input member
cannot continue your request. name must be specified for partitioned
data sets.
User Response: Contact your system programmer for
assistance determining the cause of the I/O error. Explanation: An input data set member name must be
specified.
ISRLS348 Invalid record format - The ″from″ or User Response: Specify the member to MOVE or
″to″ data set has RECFM = U. They must COPY.
both be U.
Explanation: If either the FROM or TO data set has a ISRLS356 Member name is required - A new
record format of U (undefined), then both data sets member name must be specified when
must have record format U. from data set is sequential and to data
set is partitioned.
User Response: Reallocate one of the data sets or
forgo the MOVE/COPY. Explanation: An output member name for partitioned
data sets must be specified.
ISRLS349 Pack error - Packing is not allowed with User Response: Specify the output member to MOVE
undefined record formats. or COPY.
Explanation: A pack option cannot be requested for
data sets whose record format is U (undefined). ISRLS357 Member name not allowed - Member
name ’aaaaaaaa’ not allowed with a
User Response: Remove the pack request from the
sequential file.
service.
Explanation: A sequential file does not contain
members.
ISRLS350 Invalid option - Lock keyword is not
allowed for LMMOVE. User Response: Blank out the member name.
Explanation: The keyword LOCK is not allowed for
this service.
User Response: Remove the LOCK keyword.
ISRLS358 Invalid data sets - Same data sets not ISRLS364 Output name not allowed - Output
allowed when processing ’aaaaaaaa’ name ’aaaaaaaa’ not allowed when using
service. member lists.
Explanation: The TO and FROM data set names are Explanation: The TO member name is not allowed
identical. when using member lists.
User Response: Correct one of the data set names. User Response: Remove the TO member name.
ISRLS359 Concatenation is invalid - The ″to″ data ISRLS365 I/O error or BLDL - I/O error or BLDL
ID contains concatenated libraries. This on member build.
is not allowed.
Explanation: A severe internal error has occurred.
Explanation: Concatenated libraries are not allowed
User Response: Contact your system programmer.
for the TO data set.
System Programmer Response: Contact IBM support.
User Response: Contact the responsible programmer.
Programmer Response: Correct the concatenation
ISRLS366 ISPF library required - Controlled ISPF
error.
library required with lock function.
Explanation: A controlled ISPF library is required for
ISRLS360 New output name required - TO data
the lock function.
set name and From data set name are
the same. Enter a different TO data set User Response: Specify a controlled ISPF library.
name, or enter a member name (the
FROM member will be copied/moved
and renamed to the new member name). ISRLS367 Library required - Controlled ISPF
library required. Sequential data set not
Explanation: The TO data set name is the same as the allowed.
FROM data set name or blank.
Explanation: Sequential data sets are not allowed with
User Response: Specify a TO data set name that is the LOCK parameter.
different from the FROM data set name. Or enter a
member name (the member will be renamed). User Response: Specify a controlled ISPF library.
ISRLS361 Member not found - Member ’aaaaaaaa’ ISRLS368 Invalid ″to″ library - ″To″ library must
not found in specified input library. not be controlled.
Explanation: The member does not exist in the input Explanation: The TO library must not be a controlled
library. ISPF library.
User Response: Make sure the specified member User Response: Specify a data set that is not a
name is correct. controlled ISPF library.
ISRLS362 Open error - ’aaaaaaaa’ service requires ISRLS369 No members in data set - The
the ″to″ data IDs not to be opened. partitioned data set specified contains
no members.
Explanation: The specified service requires that the
TO data set be closed when the service is invoked. Explanation: There are no members in the partitioned
data set.
User Response: Contact the responsible programmer.
User Response: Specify a partitioned data set that
Programmer Response: Issue an LMFREE for the TO contains members.
data ID before invoking the service.
ISRLS371 Invalid format parameter - Format value ISRLS378 Print failed - Unable to allocate listing
’aaaaaaaa’ is not valid. Specify YES, NO, data set.
or blank.
Explanation: The print failed because the listing data
Explanation: The value specified for the FORMAT set could not be allocated.
parameter is not valid.
User Response: Contact your system programmer.
User Response: Specify YES, NO, or blank for the
System Programmer Response: Contact IBM support.
value of the FORMAT parameter.
ISRLS377 Print failed - Unable to write to the Explanation: An open error occurred while building
listing data set. the member list.
Explanation: The print failed because it was unable to User Response: Contact your system programmer.
write to the listing data set. System Programmer Response: Contact IBM support.
User Response: Contact your system programmer.
System Programmer Response: Contact IBM support.
ISRLS446 Severe error - An I/O error occurred ISRLS453 End of selections - No more members
while building the member list. were selected from this member list.
Explanation: An I/O error occurred while building Explanation: This is an informational message.
the member list.
User Response: Contact your system programmer. ISRLS454 End of display - END or RETURN was
entered to terminate the member list
System Programmer Response: Contact IBM support.
display.
Explanation: This is an informational message.
ISRLS447 Severe error - A BLDL error occurred
while building the member list.
ISRLS455 Member exists - The specified member
Explanation: A BLDL error occurred while building
already exists in the member list.
the member list.
Explanation: This is an informational message.
User Response: Contact your system programmer.
System Programmer Response: Contact IBM support.
ISRLS456 Member not found - The specified
member cannot be found in the data set
ISRLS448 Severe error - A severe BLDL error concatenation.
occurred while getting the next
Explanation: The specified member cannot be found
selection.
in the concatenation of data sets.
Explanation: A severe BLDL error occurred while
User Response: Specify a member that exists in the
getting the next selection.
data set concatenation.
User Response: Contact your system programmer.
System Programmer Response: Contact IBM support. ISRLS457 No matches found - No members
matched the specified pattern.
ISRLS466 No ZDATA area - The member list ISRLS472 Data set not open - LMMDISP requires
display panel must contain a ZDATA prior successful completion of
area. LMOPEN.
Explanation: There is no ZDATA area specified on the Explanation: The data set is not open. LMOPEN must
member list display panel. be issued for the data set before calling the LMMDISP
service.
User Response: Specify a member list display panel
that contains a ZDATA area. User Response: Call the LMOPEN service for the data
set before calling LMMDISP.
ISRLS467 Invalid CURSOR value - The valid
values for keyword CURSOR are ISRLS473 Invalid MEMBER name - The value for
ZCMD, ZLLCMD, and ZLUDATA. keyword MEMBER contains invalid
characters.
Explanation: The value specified for the CURSOR
keyword of the LMMDISP service is invalid. Explanation: There are invalid characters in the value
specified for the MEMBER keyword.
User Response: Specify ZCMD, ZLLCMD, or
ZLUDATA for the CURSOR keyword. User Response: Specify a valid pattern for the
member name. Asterisk and percent are allowed in the
pattern.
ISRLS468 Invalid COMMANDS value - The valid
values for keyword COMMANDS are S
and ANY. ISRLS474 Invalid PANEL name - The value for
keyword PANEL contains invalid
Explanation: The value specified for the COMMANDS
characters.
keyword of the LMMDISP service is invalid.
Explanation: There are invalid characters in the value
User Response: Specify S or ANY for the
specified for the PANEL keyword.
COMMANDS keyword.
User Response: Correct the invalid characters.
ISRLS469 Invalid STATS value - The valid values
for keyword STATS are YES and NO. ISRLS475 Invalid FIELD value - The valid values
for keyword FIELD are 1 and 9.
Explanation: The value specified for the STATS
keyword of the LMMDISP service is invalid. Explanation: The value specified for the FIELD
keyword is invalid.
User Response: Specify YES or NO for the STATS
keyword. User Response: Specify either 1 or 9 for the FIELD
keyword.
ISRLS470 Invalid member list - You may not use a
member list created by LMMDISP with ISRLS477 PQUERY error - A PQUERY error
the LMMLIST service. occurred. Contact your system
programmer.
Explanation: Member lists generated by LMMDISP
cannot be used with LMMLIST. Explanation: An error occurred while using PQUERY.
User Response: Free the member list using User Response: Contact your system programmer.
OPTION(FREE) when switching between LMMLIST
System Programmer Response: Contact IBM support.
and LMMDISP with the same data-id.
ISRLU022 Invalid newname - Newname field ISRLU034 Print failed - Print request failed. list
contains an invalid member name. data set may have more details.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLU023 Member not found - Selected member is ISRLU035 Open failed - I/O error occurred trying
not available for promotion. to open ’from’ data set for input.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLU024 BLDL error - Severe error performing ISRLU036 Delete failed - I/O error occurred trying
BLDL on selected member. to open ’from’ data set for output.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLU025 Cannot use ’top’ library - ’From’ library ISRLU037 Delete failed - Permanent I/O error.
cannot be a ’top’ or ’only’ library.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLU038 Delete failed - Data control block is not
ISRLU026 Data set aaaaaaaa - bbbbbbbb aaaaaaaa open or is open for input.
successfully
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLU039 Delete failed - Insufficient virtual
ISRLU027 to aaaaaaaa. storage is available to perform STOW
function.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLU028 Promotion error - Multiple messages
previously displayed. ISRLU040 Open failed - Open failed for selected
member.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLU029 ’To’ lib not cataloged - ’aaaaaaaa’ was not
found in catalog. ISRLU041 Region size too small - Insufficient
virtual storage to perform BLDL.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLU030 Write variables failed - Write variables
to shared pool for promote failed. ISRLU042 Program error in ISPCDB - Module
ISRLUPR22 or isrluprs received a return
Explanation: No explanation available at this time.
code of 36 from module ISPCDB.
Explanation: No explanation available at this time.
ISRLU031 Promotion not allowed - Promotion user
exit validation failed.
ISRLU043 Bad BLDL return code - A bad BLDL
Explanation: No explanation available at this time.
return code was returned from module
ISPCDB.
ISRLU032 aaaaaaaa bbbbbbbb - cccccccc(aaaaaaaa)
Explanation: No explanation available at this time.
bbbbbbbb successfully
Explanation: No explanation available at this time.
ISRLU044 Obtain failed - Obtain failed for BLDL
on selected member.
ISRLU033 Severe error occurred - Module aaaaaaaa
Explanation: No explanation available at this time.
received a return code bbbbbbbb from
module cccccccc.
Explanation: No explanation available at this time.
ISRLU045 I/O error on BLDL - I/O error on BLDL ISRLU057 ISPF library required - Controlled ISPF
for selected member. library required for lock function.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLU046 Promotion failed - Cannot promote from ISRLU058 Invalid ″to″ library - ″To″ library must
password protected data set. not be controlled.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLU047 After exit failed - Member promoted. ISRLU059 Unable to lock member - Member
Exit after promotion failed. ″aaaaaaaa″ exists at a lower level of the
hierarchy.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLU048 Seq. data set invalid - Use partitioned
data set, if ″from″ member not given. ISRLU060 Unable to lock member - Member
″aaaaaaaa″ exists at a lower level.
Explanation: No explanation available at this time.
bbbbbbbb members copy/locked.
Explanation: No explanation available at this time.
ISRLU050 Library required - Controlled ISPF
library required. Sequential data set not
allowed. ISRLU061 Severe error - see log - Copy and lock
failed for member ″aaaaaaaa″. See log for
Explanation: No explanation available at this time.
details.
Explanation: No explanation available at this time.
ISRLU051 ISRCFIL not allocated - Control file not
allocated to ddname ISRCFIL.
ISRLU062 Member already locked - Member
Explanation: No explanation available at this time.
″aaaaaaaa″ locked by ″bbbbbbbb″.
Copy/lock completed for cccccccc
ISRLU052 Library not controlled - Unable to lock members.
member. Library ″aaaaaaaa″ is not
Explanation: No explanation available at this time.
controlled.
Explanation: No explanation available at this time.
ISRLU063 Lock failed - Requestor is not
authorized to access ″aaaaaaaa″.
ISRLU053 Member already locked - Member
Explanation: No explanation available at this time.
″aaaaaaaa″ is locked by ″bbbbbbbb″.
Explanation: No explanation available at this time.
ISRLU064 Lock failed - Requestor is not
authorized to access ″aaaaaaaa″. bbbbbbbb
ISRLU054 Controls not active - Controls must be members copy/locked.
activated before copy and lock
Explanation: No explanation available at this time.
performed.
Explanation: No explanation available at this time.
ISRLU065 Lock failed - Promote is in process for
member ″aaaaaaaa″.
ISRLU055 Severe error - see log - Lock failed for
Explanation: No explanation available at this time.
member ″aaaaaaaa″. Copy/lock completed
for bbbbbbbb members.
ISRLU066 Lock failed - Promote is in process for
Explanation: No explanation available at this time.
member ″aaaaaaaa″. bbbbbbbb members
copy/locked.
ISRLU056 Copy and lock failed - Copy failed.
Explanation: No explanation available at this time.
Member is still locked with your ID.
Explanation: No explanation available at this time.
ISRLU100 Invalid option number - Enter one of ISRLW004 ISRLW004: LMF started task aaaaaaaa
the listed options. terminating - restart LMF.
Explanation: No explanation available at this time. Explanation: No explanation available at this time.
ISRLU110 Dynamic allocation error - Unavailable ISRLW006 ISRLW006: Control file version is not
resource with error code aaaaaaaa, press correct for LMF started task aaaaaaaa.
Help key for detail.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLW007 ISRLW007: LMF started task name
ISRLU111 Dynamic allocation error - Invalid aaaaaaaa is not bound to the control file.
parameter list with error code aaaaaaaa,
Explanation: No explanation available at this time.
press Help key for detail.
Explanation: No explanation available at this time.
ISRLW008 ISRLW008: LMF task aaaaaaaa could not
be started. Contact system programmer.
ISRLU112 Dynamic allocation error -
Explanation: No explanation available at this time.
Environmental error with error code
aaaaaaaa, press Help key for detail.
ISRLW009 ISRLW009: Please refer to the Planning
Explanation: No explanation available at this time.
and Customizing guide.
Explanation: No explanation available at this time.
ISRLU113 Dynamic allocation error - System
routine error with error code aaaaaaaa,
press Help key for detail. ISRLW014 Invalid control file - The current control
file has an invalid ZNAMES member.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLU114 No dynamic allocation - Installation
validation routine deny dynamic ISRLW015 aaaaaaaa has run out of space.
allocation/unallocation.
Explanation: No explanation available at this time.
Explanation: No explanation available at this time.
ISRLW001 ISRLW001: LMF started task ’aaaaaaaa’ Explanation: No explanation available at this time.
initialized.
Explanation: No explanation available at this time. ISRLW018 aaaaaaaa had a bbbbbbbb abend.
Explanation: No explanation available at this time.
ISRLW002 ISRLW002: LMF started task aaaaaaaa has
been stopped by user ″bbbbbbbb″. ISRLW019 The time that this event occurred was
Explanation: No explanation available at this time. aaaaaaaa.
Explanation: No explanation available at this time.
ISRLW003 ISRLW003: LMF unable to establish
ESTAE environment in started task ISRM000 Specify name or pattern - Command
aaaaaaaa. requires a member name or pattern be
Explanation: No explanation available at this time. specified.
Explanation: The SELECT command requires that a
member name or pattern be specified.
User Response: Reenter the SELECT command with a
member name or pattern, or choose another command.
ISRM001 Member not found - The requested ISRM008 Invalid panel width - ISRCML requires
member was not found in the PDS a panel that is 80 characters wide.
directory(s).
Explanation: The member list panel specified has a
Explanation: PDF was unable to locate the member width of fewer than 80 characters.
specified.
User Response: Verify that the member list panel
User Response: Check that the member name was being used has a width of 80 characters.
spelled correctly. If the member is known to exist,
System Programmer Response: Check user’s
contact your system programmer.
//ISPPLIB concatenation and any LIBDEFs to any
System Programmer Response: PDF received an panel libraries to ensure that the correct panel is being
RC=4 from a BLDL. Run the appropriate diagnostics picked up and that it has a width of 80 characters.
against the PDS (or PDSE) directory to verify that the
member does exist. If directory problems are found,
ISRM009 Pattern too long - Pattern must be less
contact IBM support for the DFP component.
than or equal to 8 characters.
Explanation: The pattern specified has more than 8
ISRM002 Invalid member name - Member name
characters.
specified contains invalid characters.
User Response: Reduce the pattern specified to 8 or
Explanation: One or more invalid characters were
fewer characters.
entered in the member name.
User Response: Check that the member name entered
ISRM010 Invalid sort field - Valid sort fields are
is a character string of up to 8 alphanumeric characters,
NAME, LIB, VV, MM, CRE, CHA, SIZE,
the first of which is either alphabetic or $, #, or @.
INIT, MOD and ID.
Explanation: An invalid sort field type was specified.
ISRM003 Invalid command - Valid member list
commands are SELECT, SORT, LOCATE, User Response: Enter one of valid listed sort fields.
RESET, REFRESH, SAVE, MLC, and
CONFIRM.
| ISRM011 Invalid sort field - Valid sort fields are
Explanation: A command other than SELECT, SORT, | NAME, LIB, SIZE, TTR, ALIAS, AC,
LOCATE, RESET, REFRESH, SAVE, MLC, or CONFIRM | AM, AR, ATTR, and SSI.
was entered.
| Explanation: An invalid sort field type was specified.
User Response: Check the spelling of the command
entered. Valid member list commands are SELECT, | User Response: Enter one of valid listed sort fields.
SORT, LOCATE, RESET, REFRESH, SAVE, MLC, or
CONFIRM. ISRM012 List in sorted order - The member list is
already sorted in the specified order.
ISRM006 Member name too long - Member name Explanation: This is an informational message.
must be less than or equal to 8
characters.
ISRM013 Panel not found - The specified member
Explanation: A member name of more than 8 list panel could not be found.
characters was entered.
Explanation: The panel specified for the LMMLIST
User Response: Verify the member name entered and service could not be found.
ensure it is less than or equal to 8 characters.
System Programmer Response: Verify that the panel
specified for the LMMLIST service exists in a library
ISRM007 Invalid select code - Use ″S″ to select or that is concatanated to ISPPLIB.
primary command RESET to erase all
line commands.
ISRM014 Invalid PDS directory - The directory
Explanation: A line command other than S was block size exceeds a maximum of 256.
entered on a BROWSE or EDIT member list.
Explanation: The directory for the specfied library
User Response: Make sure that BROWSE or EDIT is exceeds the maximum of 256.
where you want to be. If so, enter S next to the
member(s) to be selected, or enter RESET to clear all System Programmer Response: Allocate a data set
line commands. with a directory that is less than the maximum of 256.
ISRM015 Member deleted - The member you ISRM022 List saved - The member list was saved
selected has been deleted. Please select in the ISPF list data set.
again.
Explanation: This is an informational message.
Explanation: The user has selected a new action for a
member which has been deleted by a previous action.
ISRM023 List saved - The member list was saved
User Response: No further actions can be performed in ’aaaaaaaa’.
against a deleted member.
Explanation: This is an informational message.
ISRM029 Invalid changed string - ″aaaaaaaa″ is ISRM035 Invalid locate string - NX, DATA, OVLY,
invalid as a ″Changed″ date/time RU, RN, RF and TEST are the valid
LOCATE parameters when a member
Explanation: The member list has been sorted by date
list is sorted by ATTRIBUTES.
changed and a locate command has been entered that
is not a numeric value. Explanation: The valid LOCATE parameters are based
upon the most recent sort command. When a member
User Response: Enter a valid date/time
list is sorted by attributes, use one of the LOCATE
parameters listed.
ISRM030 I/O error - An I/O error occurred while
processing the member list SORT
ISRM036 Allocation error - An error occurred
command.
allocating ’aaaaaaaa’.
Explanation: An I/O error was detected during BLDL
Explanation: An error was encountered in allocating
processing against the member list data set.
the List data set while processing the SAVE primary
User Response: Retry the operation. command.
System Programmer Response: Verify that the data User Response: Contact your system programmer.
set is functional.
System Programmer Response: Verify that the data
set is functional.
ISRM031 BLDL error - A BLDL error occurred
while processing the member list SORT
| ISRM037 Invalid sort field - Valid sort fields are
command.
| NAME, LIB, VV, MM, CHA, SIZE, INIT,
Explanation: A BLDL error was detected against the | MOD, CRE, and ID.
member list data set.
| Explanation: An invalid SORT primary command
User Response: Retry the operation. | parameter was entered.
System Programmer Response: Verify that the data | User Response: Retry the operation with a valid SORT
set is functional. | parameter.
ISRM032 OPEN error - An OPEN error occurred | ISRM038 Invalid sort field - Valid sort fields are
while processing the member list SORT | NAME, LIB, SIZE, TTR, AC, AM, RM,
command. | ATTR, and SSI.
Explanation: An OPEN error was detected against the | Explanation: An invalid SORT primary command
member list data set. | parameter was entered.
User Response: Retry the operation. | User Response: Retry the operation with a valid SORT
| parameter.
System Programmer Response: Verify that the data
set is functional.
ISRM039 I/O error - An I/O error occurred while
saving the member list.
ISRM033 No members left - All members have
been deleted from the PDS(s). Explanation: An I/O was encountered while
processing the SAVE primary command.
Explanation: This is an informational message. All the
current members of the PDS have been deleted by a User Response: Retry the operation.
previous action.
System Programmer Response: Verify that the data
set is functional.
ISRM034 LOCATE command invalid - The
member list must be sorted again before
ISRM039A Confirm forced on - Confirm member
you can use the LOCATE command.
delete is forced on for default action
Explanation: This is an informational message. Delete.
Explanation: Informational only
ISRM039B Initial edit macro set - An initial edit ISRM046 Locate string too long - Locate string
macro is defined for actions Edit and ″aaaaaaaa″ must be less than or equal to
View. Enter a ″/″ in the prompt field for bbbbbbbb characters.
Edit or View Actions to display or
Explanation: The LOCATE parameter contains too
change Edit/View entry fields.
many characters.
Explanation: Informational only
User Response: Retry the operation with correct
number of characters.
ISRM040 Invalid data set name - The specified
data set name contains invalid syntax.
ISRM047 Invalid LRECL - Data set logical record
Explanation: A data set qualifier syntax is invalid. length must be greater than or equal to
80.
User Response: Correct and reenter the data set name.
Explanation: The list-id data set must have a LRECL
that is equal to or greater than 80.
ISRM041 Invalid sort field - Valid sort fields are
NAME, VV, MM, CRE, CHA, SIZE, User Response: Correct the list-id data set and retry
INIT, MOD, and ID. the SAVE operation.
Explanation: An invalid SORT primary command
parameter was entered. ISRM048 Error freeing data set - Error freeing the
list data set.
User Response: Retry the operation with a valid SORT
parameter. Explanation: The list data set encountered an error
while processing a FREE command.
| ISRM042 Invalid sort field - Valid sort fields are User Response: Contact your system programmer.
| NAME, SIZE, TTR, ALIAS, AC, AM,
System Programmer Response: Verify that the data
| RM, ATTR, and SSI.
set is functional.
| Explanation: An invalid SORT primary command
| parameter was entered.
ISRM049 Error closing data set - Error closing the
| User Response: Retry the operation with a valid SORT data set in which the member list was
| parameter. saved.
Explanation: An error was encountered while closing
| ISRM043 Invalid sort field - Valid sort fields are the list data set.
| NAME, VV, MM, CHA, SIZE, INIT,
User Response: Contact your system programmer.
| MOD, CRE, and ID.
System Programmer Response: Verify that the data
| Explanation: An invalid SORT primary command
set is functional.
| parameter was entered.
| User Response: Retry the operation with a valid SORT
ISRM050 List-id too long - The list-id must be
| parameter.
less than or equal to 8 characters in
length.
| ISRM044 Invalid sort field - Valid sort fields are
Explanation: The SAVE member list primary
| NAME, SIZE, TTR, AC, AM, RM,
command allows a list-id as a parameter. The list-id
| ATTR, and SSI.
must have 8 or fewer characters.
| Explanation: An invalid SORT primary command
| parameter was entered.
ISRM051 Invalid locate string - Enter numeric
| User Response: Retry the operation with a valid SORT characters (0-9) for locate string.
| parameter.
Explanation: The locate parameter must be a valid
number, if the list is sorted by LIB, VV, or MM.
ISRM045 No members selected - None of the
User Response: Reissue the LOCATE command with
members in the member list matched
a valid parameter.
the specified pattern.
Explanation: This is an informational message.
ISRM052 Invalid locate string - Enter hexadecimal ISRM059 Date incomplete - Enter complete date
characters (0-9,A-F) for locate string. in format YY/MM/DD.
Explanation: The locate parameter must be a valid hex Explanation: The LOCATE command requires a fully
number, if the list is sorted by SIZE, TTR, or AC. specified date.
User Response: Reissue the LOCATE command with User Response: Reissue the LOCATE command with
a valid parameter. a valid parameter.
ISRM053 ″*″ not supported. - The ″*″ pattern is ISRP000 There are no keywords defined for
not supported for this action. language aaaaaaa.
Explanation: This message is self-explanatory. Explanation: This is an informational message.
Language aaaaaaa has no keywords which the editor
specifically highlights, so you cannot look at the
ISRM054 Select code too long - Only 1 character
keyword list.
select codes are valid.
Explanation: The select primary command allows a
ISRP001 Settings for language aaaaaaa were reset
member name and a select code as parameters. For
to their original values.
normal member list panels, only 1-character select
codes are valid. Explanation: This is an informational message. All of
the settings for language aaaaaaa, including colors,
highlighting, intensity, and special characters to
ISRM055 Date not numeric - Enter numeric
highlight were reset to the values they had when the
characters for month, day, and year.
HILITE command was invoked.
Explanation: The LOCATE command requires that the
month, day, and year be expressed as numbers.
ISRP002 Colors for language aaaaaaa were reset to
User Response: Reissue the LOCATE command with their default values.
a valid parameter.
Explanation: This is an informational message. All of
the settings for language aaaaaaa, including colors,
ISRM056 Time not numeric - Enter numeric highlighting, intensity, and special characters to
characters for hour, minute and second. highlight were set to the default values defined by
ISPF. The default settings will be saved when you exit
Explanation: The LOCATE command requires that the the HILITE dialog unless you make further changes or
hour, minute and second be expressed as numbers. use the CANCEL command or pull-down choice.
User Response: Reissue the LOCATE command with
a valid parameter. ISRP003 No changes were made to language
aaaaaaa.
ISRM057 Locate string too long - Changed date Explanation: This is an informational message. The
must have a length less than or equal to language dialog for language aaaaaaa was exited
8. without any changes.
Explanation: The LOCATE command requires that the
month, day, and year be 2-digit numbers, separated by ISRP003A No changes were made to the FIND
one character. string color.
User Response: Reissue the LOCATE command with Explanation: This is an informational message. The
a valid parameter. FIND string color dialog was ended with the CANCEL
command. No changes were made to the FIND string
ISRM058 Locate string too long - Changed time color.
must have a length less than or equal to
5. ISRP003B No changes were made to the Cursor
Explanation: The LOCATE command requires that the phrase color.
hour and minute be 2-digit numbers, separated by one Explanation: This is an informational message. The
character. cursor phrase color dialog was ended with the
User Response: Reissue the LOCATE command with CANCEL command. No changes were made to the
a valid parameter. cursor phrase color.
Explanation: An error occurred processing an edit | User Response: Issue the INT ISPF command or select
recovery or undo request. This error indicates that the | the Workstation Tool Integration pull-down choice from
record of changes which is kept by PDF was corrupted. | the Workstation action bar pull-down on the View/Edit
| Entry Panel to configure the ISPF Workstation Tool
User Response: If you are in an edit session, do not | Integration.
save the data; it may have been corrupted.
Programmer Response: None.
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 ISRP102 Invalid VIEW/EDIT parm – When
IBM support. In addition, please write down workstation file parameter is specified,
everything you remember about the edit session that do not code DATAID or member.
originally created the recovery file or that you were in
Explanation: To invoke the VIEW or EDIT service,
when the UNDO failed. Useful information includes
you may specify either a data set name, DATAID or
messages you saw, what types of commands and
workstation file. When workstation file parameter is
macros you used, and any unusual data or system
specified, do not code DATAID or member.
conditions.
User Response: Remove the DATAID and member
parameters.
| ISRP100 No connection - This action requires a
| connection with the workstation to be
| established. A workstation connection ISRP103 File unavailable – File transfer failed,
| can be established from ISPF Settings the workstation file could not be
| panel, or enter WSCON from any opened or the file does not exist. For the
| command line. Java environment, files that exist on a
disk cannot be edited.
| Explanation: No connection to a workstation exists.
| The user must identify the workstation by specifying Explanation: The requested workstation file could not
| the GUI parameter on ISPSTART, by selecting the be accessed for one of the following reasons:
| Workstation pull-down choice from ISPF Settings panel, v The workstation file could not be opened
| or by entering WSCON from any command line.
v You are running with a Java client and the requested
User Response: Start a session with a workstation file does not exist in workstation memory.
before performing this action. Workstaion files on disk cannot be edited on the host
for the Java environment.
Programmer Response: None.
ISRP104 Error writing file – File transfer failed. ISRP110 Default configuration - ISPF
Error writing workstation file: aaaaaaaa.. Workstation Tool Integration was not
The workstation disk drive is full or the configured for the View/Edit actions.
subdirectories do not exist. Create the Default configuration will be used. You
subdirectories if they do not exist and may modify or save the default
try the action again. configuration.
Explanation: Error writing workstation file. Explanation: ISPF Workstation Tool Integration was
Workstation disk drive is full or the subdirectories do not configured for the View/Edit actions. Default
not exist. configuration will be used.
User Response: Check the workstation disk drive and User Response: Modify or save the default
retry. configuration.
Programmer Response: None.
| ISRP105 File transfer failed – Error returned by
| FILEXFER service, FILEXFER return
ISRP111 Edit not confirmed - The edit session
| code aaaaaaaa..
canceled at your request. Member
| Explanation: The FILEXFER service failed with a cannot be promoted with requested
| return code of aaaaaaaa. Refer to the ISPF Services authcode.
| Guide for an explanation of the return code.
Explanation: Entering END or EXIT on the SCLM Edit
Authcode Confirmation panel cancels the edit session.
ISRP106 Function not supported – Distributed
User Response: If you want to promote the member,
Browse is not a supported function. Try
try editing with a different authcode. If you need to
Distributed View.
change the authcode, use the SCLM library utility.
Explanation: Distributed Browse is not a supported
function.
ISRP112 WS command failed - Workstation
User Response: Try Distributed View. command failed. Return code =
aaaaaaaa..
ISRP107 Conflicting options - View on Explanation:
Workstation and Browse Mode options
The following return codes are possible if a panel is
cannot be selected simultaneously.
specified:
De-select one of the conflicting options.
0 Normal completion. The END command was
Explanation: View on Workstation and Browse Mode
entered from the selected menu.
options cannot be selected simultaneously.
4 Normal completion. The RETURN command
User Response: De-select one of the conflicting
was entered or the EXIT option was specified
options.
from the selected menu or from some
lower-level menu.
| ISRP108 No file access - File transfer failed. File
12 The specified panel could not be found.
| access on workstation rejected by ISPF
| Client/Server. 16 Truncation error in storing the ZCMD or ZSEL
variable.
Explanation: This message is self-explanatory..
20 Severe error.
ISRP109 File not saved - File not saved on
workstation. The following return codes are possible from a
MODAL workstation command:
Explanation: This message is self-explanatory.
20 Parameter or syntax on SELECT service (all
SELECTs) is not valid.
41 A null command was passed to the
workstation.
42 ISPF was not able to start the command at the
workstation.
43 Remote execution of commands was not
allowed by the user.
ISRP125 Build not allowed – An SCLM ISRP131 ’aaaaaaaa’ lines cut to ’bbbbbbbb’ —
Workstation Build cannot be performed ’aaaaaaaa’ lines were saved in clipboard
from the ISPF Java environment. ’bbbbbbbb’ for later retrieval by the paste
command.
Explanation: SCLM Workstation Build uses the ISPF
FILEXFER and WSCMDV services. These services are Explanation: The CUT command was successfully
not valid when used for a Workstation Build in the completed. The clipboard contains the lines that were
Java environment. most recently cut.
Programmer Response: None. Programmer Response: None.
System Programmer Response: Contact IBM support.
ISRP132 ’aaaaaaaa’ lines added to ’bbbbbbbb’ —
’aaaaaaaa’ lines were saved in clipboard
ISRP126 Assignment command error —
’bbbbbbbb’ for later retrieval by the paste
Assignment type (GET/SET)
command. These lines were added to
unrecognized for the PRESERVE
lines that were already saved by one or
command.
more CUT commands.
Explanation: A severe error (return code 20) has been
Explanation: The CUT command was successfully
received using the PRESERVE macro command. The
completed. The clipboard contains the lines that were
assignment type used with the PRESERVE command is
most recently cut in addition to lines that were already
invalid.
in the clipboard.
User Response: Correct the edit macro so that it uses
Programmer Response: None.
the correct assignment type for the PRESERVE
command.
ISRP133 Use CUT before PASTE — No lines
exist in the clipboard named ’aaaaaaaa’
ISRP127 PASTE data truncated - The Paste
or the clipboard does not exist. The
operation was successfully completed,
CUT command must be used before the
but some data may have been truncated.
PASTE command.
The data that was pasted into the
current edit session was CUT from a Explanation: A PASTE request was issued using the
data set with a longer logical record name of an empty or nonexistent clipboard.
length. Data past the end of the current
User Response: Use the CUT DISPLAY command to
record length was not copied into this
see the names of existing clipboards. Insure that you
edit session.
are using a clipboard that has had data placed in it by
Explanation: The data that was pasted into the current a previous CUT command.
edit session was CUT from a data set with a longer
Programmer Response: None.
logical record length. Some data may have been
truncated during the PASTE operation.
ISRP134 Clipboard limit reached — The
maximum number of clipboards have
ISRP130 Insufficient storage — CUT failed
been created. No new clipboards may be
because not enough virtual storage was
created. Use the CUT DISPLAY
available for saving the records being
command to see the names of existing
cut. ’aaaaaaaa’ bytes were required, but
clipboards.
only ’bbbbbbbb’ bytes were available in
the requested clipboard. Clipboard Explanation: Use the CUT DISPLAY command to see
’cccccccc’ was not changed. thenames of existing clipboards. You may want to
rename or reuse an existing clipboard.
Explanation: The ISPF editor reserves a certain
amount of space to save CUT lines and the cut request Programmer Response: None.
would use more than that reserved amount of space.
User Response: Reduce the number of lines being cut,
use the REPLACE parameter or specify a different
clipboard on the CUT request.
Programmer Response: None.
ISRP135 Invalid clipboard name — The ISRP140 Invalid clipboard name — The
clipboard name was greater than eight clipboard name entered is not a valid
characters long. Reenter the command name. Clipboard names follow the same
using a different clipboard name or use rules as PDS member names within
the CUT DISPLAY command to view ISPF.
existing clipboard names.
Explanation: A CUT or PASTE command was entered
Explanation: Clipboard names are 1 to 8 characters with an invalid clipboard name. Clipboard names are 1
long, contain alphanumeric characters and start with an to 8 alphanumeric characters starting with an
alphabetic character. alphabetic character.
User Response: Reenter the command using a valid User Response: Enter the command with a valid
clipboard name. clipboard name.
Programmer Response: None. Programmer Response: None.
ISRP137 No more clipboards — No clipboards ISPR142 Name change invalid — You may not
are available to use. Use the CUT change the name of the ISPF default
DISPLAY command to display the clipboard.
available clipboard names.
Explanation: An attempt was made to rename the
Programmer Response: None. ISPF default clipboard. This is not allowed because
ISPF reserves the name DEFAULT for the first
clipboard.
ISRP138 DISPLAY is invalid — DISPLAY is not a
valid operand on the CUT edit macro User Response: If you need additional clipboards, use
command. the CUT command to create them and specify the
clipboard name on the CUT command.
Explanation: The edit macro form of the CUT
command was specified incorrectly. Programmer Response: None.
User Response: Contact the author of the edit macro.
ISPR143 Invalid command— Valid commands are
Programmer Response: Change the edit macro to
B (Browse), E (Edit), C (Clear), D
remove the DISPLAY keyword of the CUT command.
(Delete), R (Rename), and O (Toggle
CUT DISPLAY is not supported from a macro.
read only).
Explanation: An invalid letter or symbol was placed
ISRP139 ’aaaaaaaa’ is empty — The requested
next to a clipboard name. Only the listed commands
clipboard (aaaaaaaaa) contains no lines to
are valid.
browse or edit.’
User Response: Enter one of the listed commands.
Explanation: A browse or edit request was made for a
clipboard that has no lines. Only clipboards containing Programmer Response: None.
lines may be browsed or edited.
User Response: Use the CUT command to add lines ISPR144 Invalid parameter— You must specify a
to the clipboard. ’aaaaaaaa’ range on a ’bbbbbbbb’command
and you may also specify a clipboard
Programmer Response: None.
name and the REPLACE keyword.
Explanation: An invalid parameter was specified on a
CUT command.
Explanation: The contents of clipboard bbbbbbbb were Programmer Response: Change the macro to specify
inserted into the current edit session. If the KEEP the proper parameter for the PRESERVE command.
keyword was used on the PASTE command, the Refer to ISPF Edit and Edit Macros for editor command
contents of the clipboard were not changed. Otherwise, syntax.
the clipboard was emptied.
ISRP282 Inconsistent parameters – ″aaaaaaaa″ and
ISPR148 ’aaaaaaaa’ is read-only — Clipboard ″bbbbbbbb″ cannot both be entered with
’aaaaaaaa’ cannot be changed using the PRESERVE command.
CUT command because it was marked
Explanation: Mutually exclusive parameters (aaaaaaaa
read-only by using the ’O’ line
and bbbbbbbb) were specified on invocation of the
command on the CUT DISPLAY panel.
PRESERVE command.
If you want to change this clipboard,
use the ’O’ line command in the CUT User Response: Change the command to specify the
DISPLAY entry panel to change the proper parameters for the PRESERVE command and
read-only status to read-write. reissue the command or rerun the macro. Refer to ISPF
Edit and Edit Macros for editor command syntax. If the
Explanation: The contents of clipboard aaaaaaaa were
macro was supplied by someone else, contact the writer
not changed.
for assistance in correcting the error.
User Response: If you want to change this clipboard,
Programmer Response: Change the macro to specify
use the ’O’ line commnad in the CUT DISPLAY entry
the proper parameter for the PRESERVE command.
panel to change the read-only status to read-write..
Refer to ISPF Edit and Edit Macros for editor command
syntax.
ISRP283 Too many parameters - Too many ISRP289 Parameter unrecognized – ON/OFF are
parameters specified for the the only valid parameters for the
SAVE_LENGTH command. Is data PRESERVE command.
quoted?
Explanation: The PDF edit PRESERVE command was
Explanation: An invalid SAVE_LENGTH command invoked with a parameter other than ON or OFF.
was entered.
User Response: Change the command to specify the
User Response: Review documentation for the proper parameters for the PRESERVE command and
SAVE_LENGTH command in ISPF Edit and Edit Macros. 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
ISRP284 Unrecognized parameter – Extraneous or
for assistance in correcting the error.
invalid parameter was specified for the
SAVE_LENGTH command. Programmer Response: Change the macro to specify
the proper parameter for the PRESERVE command.
Explanation: An invalid SAVE_LENGTH command
Refer to ISPF Edit and Edit Macros for editor command
was entered.
syntax.
User Response: Review documentation for the LINE
command in ISPF Edit and Edit Macros.
ISRRS000 aaaaaaaa - bbbbbbbb – Member or Member
pattern - aaaaaaaa - bbbbbbbb.
ISRP285 Invalid parameter – Extraneous or
Explanation: This is an informational message. The
invalid parameter was specified for the
member or pattern named in the message was
PRESERVE command.
Browsed, Printed, Renamed, Deleted, Moved, Copied,
Explanation: An invalid PRESERVE command was Edited, Reset, Viewed, or a command executed as
entered. specified.
ISRRS006 Workstation file aaaaaaaa - Workstation ISRS003 Bad sequence numbers - Abnormal
file aaaaaaaa successfully. completion (RC=6). See listing for
warning.
Explanation: Informational only.
Explanation: This is a warning message. The old data
set (OLDDD) does not contain proper sequence
ISRRS007 No default set - No default open action
numbers, or the sequence number intervals are not
has been defined, or open action
large enough to contain insert activity. This applies
requested from enhanced member list
only to UPDCMS8 or UPDMVS8 process options.
which does not support action ″OPEN″.
User Response: Verify that the old data set name is
Explanation: No explanation available at this time.
correct. Verify that sequence numbers exist in the old
User Response: Select a default for the Open action data set; create them if necessary. The NUMBER ON
on the Workplace settings panel. command in EDIT may be used. Use the RENUM
command in EDIT to expand the sequence number
intervals if necessary.
ISRRS008 Open not supported - The Open action
is not supported from LIBRARY or
DSLIST utility. ISRS004 Old input file error - Abnormal
completion (RC=8). See listing for
Explanation: No explanation available at this time. details.
Explanation: There is an error involving the old input
ISRRS009 List aaaaaaaa of bbbbbbbb - List aaaaaaaa of data set (OLDDD) and the compare was not performed.
bbbbbbbb For example, if you modified the JCL and inadvertently
Explanation: No explanation available at this time. 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.
ISRS000 No differences found - Normal
completion (RC=0). Files compare User Response: Check the SuperC listing data set for
equally. specific information describing the error. Correct the
JCL and resubmit.
Explanation: This is an informational message. No
differences were found by SuperC.
ISRS005 Bad grouping - Abnormal completion
User Response: See the SuperC listing data set for (RC=12). See listing for details.
further information.
Explanation: This message indicates inconsistent data
set organizations. The new and old data sets are not
ISRS001 Differences found - Normal completion both PDSs or sequential data sets. The compare was
(RC=1). Files are not the same. not run.
Explanation: This is an informational message. User Response: Mixed compares of PDS to seqential
Differences were found by SuperC. data sets are not permitted. The dialog interface
User Response: See the SuperC listing data set for the prevents this, but you may have incorrectly modified or
differences and further information. submitted JCL that attempts to allocate OLDDD to a
PDS and NEWDD to a sequential (or vice versa).
Correct the allocations and retry.
ISRS002 Invalid input detected - Abnormal
completion (RC=4). See listing for
warning. ISRS006 New input file error - Abnormal
completion (RC=16). See listing for
Explanation: This is a warning message. The compare details.
was performed; however, erroneous or conflicting input
options have been detected by SuperC and reported in Explanation: There is an error involving the new
the SuperC listing data set. input data set (NEWDD). The compare was not
performed. For example, if you modified the JCL and
User Response: Check the SuperC listing data set for inadvertantly omitted the NEWDD allocation, SuperC
explanations of the invalid input. The compare results would return code 16. This error is also received if the
may not be consistent with your expectations. new data set fails to open, perhaps because of an I/O
error.
User Response: Check the SuperC listing data set for
specific information describing the error. Correct the
JCL and resubmit.
User Response: Consider submitting the SuperC job Explanation: It is not valid to attempt to append to a
to batch, specifying a REGION= keyword and sufficient SuperC listing that is a member of a partitioned data
storage on the job card for the job to run. If batch is set. This action is only valid for sequential data sets.
unavailable, consult your system programmer for
Explanation: The attempt to create a profile was User Response: Monitor the job for completion. You
unsuccessful because the process option named in the need not remain in the SuperC dialog.
message is not valid.
User Response: Correct the spelling of the process
ISRS063 File tailor failure - File close. ISRS067 Hex character not paired - The hex
string has an uneven pair of hex
Explanation: This is a probable ISPF internal
characters.
processing failure. The JCL to be submitted was not
sucessfully generated. Explanation: The hexadecimal string you have
specified is incorrect. There must be an even number of
User Response: Save or print your ISPF LOG data set
hexadecimal characters for a valid string.
for your system programmer. This may be done by
temporarily exiting ISPF. Write down the circumstances User Response: Correct the hexadecimal string and
of the failure and contact your system programmer. retry. For example:
System Programmer Response: An ISPF FTCLOSE Use X'F0F0'
call has failed. There may be information in the user’s
Not X'F1F'
ISPF LOG data set or in the system log. If you are
unable to resolve the problem, contact IBM support.
ISRS068 Invalid hex string - The hex string has
an invalid character within the specified
ISRS064 Invalid search-string - Matching end
string
quote around string missing.
Explanation: Hexadecimal characters must be in the
Explanation: Unbalanced quotation marks were
range 0-9 or A-F.
detected in the search string(s). If you are attempting to
enter a DBCS string that contains a X ’7D’ as part of a User Response: Correct the hexadecimal string and
DBCS pair, you must use the Enhanced SearchFor retry.
option (Option 3.15) specifying the MIXED process
option. For example:
Explanation: SuperC has detected an invalid operand User Response: Correct the search string and retry.
outside of the search string itself. This may be because For example:
a quotation mark intended to be part of the search Use ’ ’
string has prematurely terminated the string. Data to
the right of the quotation mark is treated as a search Not ’
qualifier. to search for one blank character on a line.
User Response: Enclose the entire string in single
quotation marks and double any imbedded data ISRS077 Selections cancelled - User request
quotation marks. For example: ’DON’T RUN’ cancellation of new process option
Alternatively, correct the spelling of the search qualifier selections.
and retry.
Explanation: This is an informational message. This
message confirms that you have cancelled out of the
ISRS066 Search string required - The search process option selection dialog. The options are not
string must be specified or be in changed.
statements input.
Explanation: No search string was specified from ISRS079 Invalid imbedded quote - A quote may
option 3.13.S Search-For, either on the panel or in a be used as a delimiter or specified as
statements data set. two quotes.
User Response: Either specify one or more of the 5 Explanation: The search string contains an ambiguous
search string fields on the panel (CAPS or ASIS fields), quotation mark. Quotation marks are used in pairs to
or specify one or more SRCHFOR statements in the delimit the beginning and end of the search string if it
statements data set. The statements data set contains imbedded blanks. They may also be used to
specification will override the strings specified on the specify a searchable quotation mark, in which case two
panel. consecutive quotation marks are understood to be one
and are taken as data instead of as a delimiter. If you
ISRS093 Concatenation disallowed - All data set ISRS097 Concatenation specified - Select options
logical record lengths (LRECL) must be and press enter to display the
identical to concatenate. concatenation panel.
Explanation: An attempt has been made to Explanation: The user has requested either Extended
concatenate 2 or more data sets with different logical SuperC or Extended SearchFor from the Workplace and
record lengths. This is not allowed by MVS. Possibly has passed an ISPF library concatenation. The project,
one of the data set names is misspelled, or you are group(s), and type fields have been specified on the
inadvertently attempting to concatenate different types concatenation panel.
of data, such as source and listings.
User Response: Type options and press Enter to get
User Response: Check that the list of concatenated the concatenation panel.
data sets is the one you need. Use option 3.2 or 3.4
data set information functions to find the LRECLs of
ISRS101 Vol serial not allowed - Use ″Other data ISRS107 TBCREATE failure - Creating the table
set name″ field when specifying volume of member selections failed.
serial.
Explanation: This is an internal ISPF processing
Explanation: A volume serial was specified on a panel failure.
when the Project/Group/Type fields were used for the
data set name. The volume serial may only be specified User Response: Write down the circumstances of the
when you use the Other Data Set Name field for the failure and contact your system programmer. It may be
data set. helpful to print or save the ISPF log when you exit
ISPF.
User Response: If you are trying to access a data set
on a particular volume, type the data set name in the System Programmer Response: There may be
Other Data Set Name field and place the volume name information in the ISPF log that sheds light on this
in the Volume Serial field before pressing the Enter key. 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.
ISRS103 Member name required - Member name
is required for this partitioned data set.
ISRS108 TBPUT failure - TBPUT or TBADD to
Explanation: Add a member name to complete the table of member selections failed.
specification of the partitioned data set indicated by the
cursor. Explanation: This is an internal ISPF processing
failure.
User Response: Specify the member name and retry.
Browse the data set if you are uncertain which member User Response: Write down the circumstances of the
is correct. failure and contact your system programmer. It may be
helpful to print or save the ISPF log when you exit
ISPF.
ISRS104 Enter ″old″ PDS name - Cannot compare
″new″ PDS to ″old″ sequential data set System Programmer Response: There may be
or PDS member. information in the ISPF log that sheds light on this
failure. Perhaps there is a problem with the user’s
Explanation: Because the New data set is partitioned ISPTABL or ISPTLIB allocation. If you are unable to
(contains members), the Old data set must also be resolve the problem, contact IBM support.
partitioned. Valid combinations are PDS to PDS,
Sequential to Sequential, PDS(member) to
PDS(member), or Sequential to PDS(member). In other ISRS109 LMMDISP(get) failure - Internal ISPF
words, SuperC compares one to one or many to many, error processing member list.
but not one to many. Explanation: This is an internal ISPF processing
User Response: Specify a valid combination and retry. failure.
User Response: Write down the circumstances of the
ISRS105 Enter ″old″ member name - Cannot failure and contact your system programmer. It may be
compare ″new″ sequential data set or helpful to print or save the ISPF log when you exit
PDS member to ″old″ PDS. ISPF.
Explanation: Because the New data set is a sequential System Programmer Response: There may be
or a member of a PDS, the Old data set requires a information in the ISPF log that sheds light on this
member. Valid combinations are PDS to PDS, failure. If you are unable to resolve the problem,
Sequential to Sequential, PDS(member) to contact IBM support.
PDS(member), or Sequential to PDS(member). In other
words, SuperC compares one to one or many to many,
but not one to many.
ISRS123 Invalid profile - Too many options - no ISRU000 Invalid option - Select one of the listed
room to insert sequence option. options.
Explanation: The profile you are using contains so Explanation: No option was entered on the primary
many options that there is no room to add the option panel.
sequence number option (SEQ, NOSEQ, or COBOL)
specified from the panel without exceeding the User Response: Select one of the options available on
maximum string size for parameters passed to SuperC. this panel.
ISRU001 Data set not printed - Print control ISRU007 Enter member name - The selected
characters exist, press Help for option requires a member name.
additional information.
Explanation: Commands B, D, E, P, R, and V are
Explanation: The data set being printed contains print member commands and require a member name.
control characters.
User Response: Enter a member name.
User Response: Use the Hardcopy Utility, option 3.6,
to print the data set.
ISRU008 Pattern/name not allowed - The selected
option applies to the entire data set.
ISRU002 Prompt not valid - Prompt is entered
Explanation: Commands C, I, L, S, and X apply to the
only for the rename, move, copy, TSO
whole data set and a member name is not required.
command, WS command, edit, or view
actions. User Response: Do not use a pattern or a member
name.
Explanation: A Prompt is only allowed when the
option entered supports a prompt.
ISRU009 SYSCTLG not allowed - aaaaaaaa not
User Response: Clear the Newname field.
valid for the selected option.
Explanation: A CVOL catalog is not allowed for the
ISRU003 Enter new member name - Rename
option selected.
member option specified for member
aaaaaaaa. User Response: Change the data set name specified.
Explanation: A new member name is required for the
Rename option. ISRU010 Invalid data set name - Syntax error in
data set name aaaaaaaa.
User Response: Enter a new name for the member
being renamed. Explanation: A valid TSO data set name qualifier
begins with an alphabetic character (A-Z, $, @, or #).
The remaining characters must be alphanumeric or a
ISRU004 Invalid DSORG - ’aaaaaaaa’ organization
hyphen (-).
must be partitioned.
User Response: Correct the data set name.
Explanation: The option or line command selected
requires a partitioned data set.
ISRU011 Request failed - Catalog authorization
User Response: Enter a valid command for the data
failed for aaaaaaaa.
set selected.
Explanation: RACF authorization failed for cataloging
or uncataloging the data set.
ISRU005 Invalid DSORG - ’aaaaaaaa’ organization
must be partitioned or sequential. User Response: If you need this particular data set
cataloged or uncataloged, contact your systems
Explanation: Data set with this DSORG cannot be
programmer or RACF administrator for assistance.
printed.
Programmer Response: Catalog or uncatalog the data
User Response: Specify a data set to be printed that is
set as requested.
partitioned or sequential.
| ISRU014 Request failed - Data set is password ISRU021 Data set deleted - ’aaaaaaaa’ deleted from
| protected or is of unsupported volume bbbbbbbb.
| organization.
Explanation: This is an informational message. This
| Explanation: This message is self-explanatory. message is displayed when a data set is successfully
deleted.
| User Response: Enter the data set password.
ISRU027 Member aaaaaaaa bbbbbbbb - In data set ISRU034 aaaaaaaa already exists - Invalid to
’cccccccc’ rename member to an existing name.
Explanation: This is an informational message. The Explanation: The member name selected for this
member or pattern named in the message was rename operation already exists in the directory for this
Browsed, Printed, Renamed, Deleted, Moved, Copied, data set.
Edited, Reset, Viewed, or a command executed as
User Response: Select another member name for the
specified.
Rename Member operation.
ISRU031 Member not found - aaaaaaaa was not ISRU038 Utility - Delete - aaaaaaaa(bbbbbbbb)
found in the directory for bbbbbbbb. deleted.
Explanation: This message indicates that a member Explanation: This is an informational message. This
was not found by a BLDL command. The BLDL was message is recorded in the ISPF log and specifies the
issued by a member list command to Print, Rename, or member deleted.
Delete a member.
User Response: Use member list to determine what ISRU039 Conflicting selections - Enhanced
members are in the the partitioned data set selected. member list must be selected when
Display Edit/View panel is selected.
ISRU032 Member not printed - aaaaaaaa invalid Explanation: Enhanced member list must be selected
for printing or could not be read. for prompt Edit/View setting.
Explanation: This message is issued as a result of a User Response: Select enhanced member lists, or
BLDL for an error other than member not found. This de-select prompt Edit/View settings.
may be the result of an I/O error or a directory error.
User Response: Contact your system programmer. ISRU039A Partial list displayed - Referral library
list contained more than 30 data set
entries. Only the first 30 entry matches
ISRU033 Invalid member name - Member name
are shown.
aaaaaaaa not valid for partitioned data
sets. Explanation: Referral list DSLIST supports up to 30
data set name/filters. The referral library list contained
Explanation: The new name selected for a Rename
greater then 30 data set entries. The first 30 entry
operation is not a valid member name.
matches are shown.
User Response: Select a valid member name.
User Response: None, informational only.
ISRU040 Index printed - Index of aaaaaaaa placed ISRU047 Data set not printed - aaaaaaaa had a
in bbbbbbbb. directory error, index printed.
Explanation: This is an informational message. Explanation: An error occurred while reading the
directory or opening a data set.
ISRU041 Index not printed - Index of aaaaaaaa not User Response: Contact your system programmer.
placed in bbbbbbbb.
Explanation: Error opening temporary data set or ISRU048 Part of data set printed - aaaaaaaa
error writing line to ISPF list data set. partially placed in bbbbbbbb.
Explanation: There was an error when printing the
ISRU042 Member is empty - aaaaaaaa contains no data set. Messages are in the list data set.
records.
User Response: Check the list data set to determine
Explanation: A PRINT command was issued for an what the error was.
empty member.
ISRU049 OBTAIN failed - aaaaaaaa has unknown
ISRU043 Data set printed - Listing of aaaaaaaa attributes, OBTAIN RC = bbbbbbbb hex.
placed in bbbbbbbb.
Explanation: The DSCBs for this data set could not be
Explanation: This is an informational message. read. There is either an error in the VTOC or an I/O
error occurred. Information about the data set could
not be obtained.
| ISRU044 IGWFAMS failed - IGWFAMS failed
| with return code = aaaaaaaa decimal, User Response: Contact your system programmer.
| reason code = X’bbbbbbbb’. ISPF may be
| unable to obtain information about an
ISRU050 Utility - Allocate - aaaaaaaa allocated on
| HFS file because the HFS is not
volume bbbbbbbb.
| mounted on the current system or you
| do not have an OMVS segment. Explanation: This is an informational message. This is
a message written to the ISPF log data set.
| Explanation: ISPF invoked the IGWFAMS macro to
| retrieve the number of pages allocated, the number of
| pages used and the number of members for the data ISRU051 Data set allocated - aaaaaaaa allocated on
| set specified. IGWFAMS failed with the return code volume bbbbbbbb.
| listed in the message. This message commonly occurs
| when the HFS is mounted on a different system than Explanation: This is an informational message.
| the one you are running on or the user does not have
| an OMVS segment. ISRU052 Print failed - Unable to write to the list
| User Response: Contact your system programmer. data set. The logical record length of the
list data set must be greater than 8.
| System Programmer Response: Determine the cause
| of the problem by referring to the appropriate DFSMS Explanation: This is an informational message.
| manual and correct the problem. User Response: Increase the logical record length of
the list data set.
ISRU045 Data set not printed - aaaaaaaa has
invalid RECFM/LRECL, index printed. | ISRU053 Invalid record format - The record
Explanation: The record format is spanned, or the | format value is other than F, V, U or D.
LRECL is not between 0 and 300. The index is printed, | Explanation: Either an invalid record format was
but the data set could not be printed. | entered on the ″Allocate New Data Set″ panel, or the
User Response: To print the data set, reformat it with | record format field was left blank and the resulting
an LRECL of 300 or less. | data set was created with a record format other than F,
| V, U or D.
ISRU046 Data set not printed - aaaaaaaa is empty, | User Response: Specify the record format you want
index printed. | on the ″Allocate New Data Set″ panel.
ISRU054 Invalid record format - ’aaaaaaaa’ ISRU061 Invalid combination - One data set has
conflicts with another code. ″undefined″ record format, and the
other does not.
Explanation: Two codes for the same attribute, such as
Fixed and Variable, have been entered for the record Explanation: Record format U data sets can only be
format. moved or copied to another record format U data set.
User Response: Correct the record format. User Response: Specify two format U data sets.
ISRU055 Invalid record format - Record format F, ISRU062 Invalid block sizes - ″To″ block size is
V, or U required. less than ″from″ block size with record
format U.
Explanation: The record format must have a type of
Fixed, Variable, or Undefined. Explanation: For format U data sets, the block size of
the TO data set must be equal to or greater than the
User Response: Correct the record format.
block size of the FROM data set.
User Response: Specify a TO data set with a block
ISRU056 Invalid record length - Record length is
size that is at least as large as the FROM data set.
inconsistent with block size for this
record format.
ISRU063 Invalid member name - Member name
Explanation: The record length is greater than the
aaaaaaaa is not valid. First character must
block size or is inconsistent with the block size. For
be alpha or national.
fixed records, the block size should be divisible by the
record length. For variable records, the block size Explanation: Valid member names consist of 1-8
should be a multiple of the record length plus 4. alphanumeric characters (A-Z, #, $, @, 1-9). The first
character must be alphabetic.
User Response: Correct the record length or the block
size. User Response: Correct the member name.
| ISRU057 Numeric out of range - The number ISRU064 Invalid record format - Cannot move or
| entered must be greater than or equal to copy record format U sequential data
| aaaaaaaa.’ sets.
| Explanation: This message is self explanatory. Explanation: This is an informational message. Use a
partitioned data set to copy format U records.
| ISRU058 Rename not allowed - Rename is not
| allowed for indirectly cataloged data ISRU065 Invalid specification - ″From″ and ″to″
| sets on SYSRES volumes. data sets cannot be the same for
sequential data sets.
| Explanation: Rename of data sets on system residence
| volumes is not allowed as this might effect IPL. Explanation: When copying from a sequential data
set, a different data set must be the target of the COPY
command.
| ISRU060 Invalid combination - The input and
| output data sets cannot be the same if User Response: Specify a different data set for the
| the ISPF IEBCOPY interface is being COPY command.
| used.
| Explanation: The IEBCOPY interface used by ISPF to ISRU066 Invalid load module - Cannot move or
| copy load modules does not support specifying the copy ″planned overlay″ load modules.
| same data set as both input and output.
Explanation: This is an informational message. Load
User Response: If the function requested is Move, use modules that were created for planned overlay may not
option 3.1 to rename the member. If the function be moved or copied. ISPF does not support moving or
requested is Copy, the member must first be copied to copying data with note lists.
a second library, then back to the first.
ISRU067 Invalid specification - ″To″ member
cannot be specified if ″from″ member is
blank or *.
Explanation: When a member list is requested, the TO
member name should not be specified on the TO panel.
ISRU073 Data set aaaaaaaa - to data set bbbbbbbb Explanation: An I/O error occurred reading the
member named. The Move/Copy operation was
Explanation: This is an informational message. completed for the number of members specified.
User Response: Contact your system programmer.
ISRU074 Data set aaaaaaaa - to data set
bbbbbbbb(cccccccc)
Explanation: This is an informational message.
ISRU083 I/O error during write - Unable to write | ISRU090 Data set not printed - aaaaaaaa is an
member aaaaaaaa. Move/Copy completed | empty sequential data set.
for bbbbbbbb members.
| Explanation: This message is self explanatory.
Explanation: This is an informational message. An
I/O error occurred while writing the member named.
The Move/Copy operation was completed for the
| ISRU091 Enter Batch SYSOUT class - Batch
number of members specified.
| SYSOUT class required for this print
| operation.
| Explanation: This message is self explanatory.
ISRU084 No space on directory - Unable to
STOW member aaaaaaaa. Move/Copy
completed for bbbbbbbb members. | ISRU092 Enter printer id/writer - Printer id or
Explanation: This is an informational message. There
| writer-name is required, they are
is no space in the directory to stow the member named.
| assigned by your installation.
The Move/Copy operation is complete for the number | Explanation: This message is self explanatory.
of members specified.
ISRU112 I/O error on BLDL - BLDL error on ISRU120 aaaaaaaa members reset - Reset statistics
member aaaaaaaa on ″to″ data set. was completed successfully for aaaaaaaa
bbbbbbbb members processed. members.
Explanation: BLDL macro has failed. Open failed, Explanation: This is an informational message.
Obtain failed, or there is insufficient virtual storage for
the BLDL.
ISRU121 Member aaaaaaaa reset - Reset statistics
User Response: Increase virtual storage and retry. was completed successfully.
Explanation: This is an informational message.
ISRU113 Members not replaced - aaaaaaaa
members not replaced, bbbbbbbb
ISRU122 Member not found - Member aaaaaaaa
members cccccccc.
not found in data set.
Explanation: This is an informational message.
Explanation: This is an informational message.
User Response: Determine why the members were
not replaced and retry. One possible explanation is that
ISRU123 I/O error during search - Directory error
another user was accessing the member.
- member aaaaaaaa. Reset completed for
bbbbbbbb members.
ISRU114 to aaaaaaaa bbbbbbbb members not
Explanation: BLDL macro has failed. Open failed,
replaced
Obtain failed, or there is insufficient virtual storage for
Explanation: This is an informational message. the BLDL.
User Response: Determine why the members were User Response: Increase virtual storage and retry.
not replaced and retry. One possible explanation is that
another user was accessing the member.
ISRU124 No space on directory - Unable to
STOW member aaaaaaaa. Reset
ISRU115 aaaaaaaa not replaced - Like-named completed for bbbbbbbb members.
member already exists in ″to″ data set.
Explanation: Statistics could not be set because there
Explanation: This is an informational message. is no space in the directory to store the statistics.
User Response: Either delete members from the data
ISRU116 I/O error on BLDL - BLDL I/O error set to free space in the directory, or reallocate the data
member aaaaaaaa on ″to″ data set. set with more directory blocks.
bbbbbbbb members complete.
Explanation: BLDL macro has failed. Open failed, ISRU125 I/O error during STOW - Directory error
Obtain failed, or there is insufficient virtual storage for - member aaaaaaaa. Reset completed for
the BLDL. bbbbbbbb members.
User Response: Increase virtual storage and retry. Explanation: The MVS STOW system macro has
failed.
ISRU117 aaaaaaaa not bbbbbbbb - Cannot find User Response: Contact your system programmer.
member cccccccc on ″to″ data set.
System Programmer Response: This is likely the
Explanation: This is an informational message. result of an MVS system error. Correct the failure and
retry.
ISRU118 aaaaaaaa not bbbbbbbb - Cannot find
member cccccccc on ″to″ data set. ISRU126 I/O error during read - Unable to read
dddddddd members processed. member aaaaaaaa. Reset completed for
bbbbbbbb members.
Explanation: This is an informational message.
Explanation: The MVS GET system macro has failed.
ISRU119 I/O error on BLDL - I/O error on BLDL User Response: Contact your system programmer.
for member aaaaaaaa on ″to″ data set.
System Programmer Response: This is likely the
Explanation: BLDL macro has failed. Open failed, result of an MVS system error. Correct failure and retry.
Obtain failed, or there was insufficient virtual storage
for the BLDL.
User Response: Increase virtual storage and retry.
ISRU127 Statistics deleted - Delete statistics was ISRU136 Error in system ctlg - Contact system
completed successfully for member Programmer, rtn code = aaaaaaaa, r0 =
aaaaaaaa. bbbbbbbb, r1 = cccccccc (dec).
Explanation: This is an informational message. Explanation: A severe error has occurred while
processing a catalog request.
ISRU128 Utility - Reset - aaaaaaaa(bbbbbbbb) User Response: Give your system programmer the
information in the message.
Explanation: This is an informational message put in
the log data set. System Programmer Response: Correct the catalog
problem.
ISRU129 Utility - Reset - aaaaaaaa ---- All
members ISRU137 Request failed - Catalog return code =
aaaaaaaa, r0 = bbbbbbbb, r1 = cccccccc (dec).
Explanation: This is an informational message put in
the log data set. Explanation: A severe error has occurred while
processing a catalog request.
ISRU130 Data set cataloged - ’aaaaaaaa’ cataloged User Response: Give your system programmer the
on volume bbbbbbbb. information in the message.
Explanation: This is an informational message. System Programmer Response: Correct the catalog
problem.
ISRU131 Utility - Catalog - ’aaaaaaaa’ cataloged on
volume bbbbbbbb. ISRU138 Already cataloged - Entire or partial
name cataloged, data set ’aaaaaaaa’.
Explanation: This is an informational message.
Explanation: This is an informational message.
ISRU132 Data set uncataloged - ’aaaaaaaa’
uncataloged. ISRU139 Data set not cataloged - ’aaaaaaaa’ was
not found in catalog.
Explanation: This is an informational message.
Explanation: This is an informational message.
ISRU133 Utility - Uncatalog - ’aaaaaaaa’
uncataloged ISRU140 Compress successful - Compress listing
is in ’aaaaaaaa’
Explanation: This is an informational message.
Explanation: This is an informational message.
ISRU134 Catalog unavailable - The volume
containing the requested catalog is not ISRU141 Utility - Compress - ’aaaaaaaa’
mounted. compressed
Explanation: This message is self-explanatory. Explanation: This is an informational message.
User Response: Have your system programmer
mount the volume. ISRU142 Statistics deleted - Delete statistics was
completed successfully for aaaaaaaa
System Programmer Response: Mount the volume.
members.
Explanation: This is an informational message.
ISRU135 No space in system ctlg - Contact system
PGMer, rtn code = aaaaaaaa, r0 =
bbbbbbbb, r1 = cccccccc (dec). ISRU143 Utility - Compress - ’aaaaaaaa’ compress
failed, RC = bbbbbbbb hex
Explanation: There is no space in system volume to
process request. Explanation: This is an informational message put in
the log data set.
User Response: Give your system programmer the
information in the message.
ISRU145 Incomplete aaaa - ISPF does not support Explanation: The data set was not uncataloged,
copying PDSE program object aliases. probably because is resides on a volume for which a
One or more of the members you CONVERTV was issued, but not successfully
selected are program object aliases. completed. PDF issued the uncatalog request, received
These members were not copied, unless a return code zero, but on further inspection discovered
you also selected the member of which that the data set name still existed in the catalog.
it is an alias. User Response: Contact your system programmer for
Explanation: PDSE program object alias members are assistance in removing the data set from the datalog.
copied automatically when the member it of which is System Programmer Response: Refer to the
an alias is copied. ISPF will not copy an alias member appropriate DFP documentation for assistance in
if selected. If you need to process the alias member, removing the catalog entry.
you must use the binder.
User Response: Use the binder to process program ISRU150 BLDL error - I/O error, insufficient
object alias members. virtual storage, or other BLDL error.
Explanation: Either there was not enough storage to
ISRU146 Member not aaaaa - ISPF does not process BLDL, or another BLDL error has occurred.
support copying PDSE program object
aliases. The member you selected is a User Response: Either add more virtual storage, or
program object alias. To copy this correct the other BLDL error.
member, copy the member that it is an
alias of. ISRU151 I/O error during read - Unable to read
Explanation: PDSE program object alias members are data.
copied automatically when the member of which it is Explanation: The member is unreadable due to an I/O
an alias is copied. ISPF will not copy an alias member error.
if selected. If you need to process the alias member,
you must use the binder. User Response: Retry the operation. If the problem
persists, contact your system programmer.
User Response: Use the binder to process program
object alias members. System Programmer Response: Correct the I/O error.
ISRU147 Compress failed - Compress listing is in ISRU152 Unable to copy data – Data contains
’aaaaaaaa’, RC = bbbbbbbb hex. user TTR, but is not a load module.
ISPF cannot copy.
Explanation: The compress has failed for one of the
following reasons: Explanation: ISPF does not support the type of data
being copied.
4 Data set not eligible for compression. Set by
user exit only. User Response: Use an alternate copy method, such
as IEBCOPY.
8 Data set could not be allocated. Set by user
exit only.
ISRU153 Print failed – Move/Copy operation ISRU161 Empty member – Member aaaaaaaa is
encountered an error printing one or empty.
more members.
Explanation: This is an informational message.
Explanation: The Move/Copy operation could not
print all of the successfully copied members to the
ISRU162 I/O error – Unable to read member
print data set. This may be due to an out-of-space
aaaaaaaa.
condition on the print data set.
Explanation: The member is unreadable due to an I/O
User Response: Reallocate the print data set with
error.
more space.
User Response: Contact your system programmer.
ISRU154 Members may be copied – Only System Programmer Response: Fix the I/O error.
members from library aaaaaaaa will be
moved, all else will be copied.
ISRU163 VSAM data set - VSAM data set
Explanation: This is an informational message. organization is not supported for this
function.
ISRU155 Numeric out of range – The number Explanation: You cannot use the Rename, Catalog or
entered is too large or too small. Uncatalog functions of option 3.2 or option 3.4 against
a VSAM data set.
Explanation: This is an informational message.
User Response: Use IDCAMS to process the VSAM
data set.
ISRU156 Invalid date – The date must be
specified as one of the formats listed.
ISRU164 Empty data set - Data set aaaaaaaa is
Explanation: The date has been entered in an
empty.
unsupported format.
Explanation: This is an informational message.
User Response: Enter the date in a format that is
supported.
ISRU165 Invalid DSORG - Data set organization
must be partitioned or sequential.
ISRU157 Invalid date - The specified expiration
date has passed. Explanation: The data set organization must be
partitioned or sequential to process the operation you
Explanation: The expiration date entered has already
have requested.
passed.
User Response: Enter a valid DSORG and retry the
User Response: Enter a future date.
operation.
ISRU168 Member not found - Member aaaaaaaa ISRU175 Tbadd failure - Return code aaaaaaaa
was not found in data set bbbbbbbb received adding bbbbbbbb to table.
Explanation: The member specified on the hardcopy Explanation: A return code greater than 8 was
Utility panel does not exist in the data set specified. received from the TBADD or TBPUT service.
User Response: Correct the data set and/or member User Response: Log off and retry. If the error recurs,
and retry thr print request. contact your system programmer.
System Programmer Response: Contact IBM support.
ISRU169 Invalid disposition - A member cannot
be deleted using this function.
ISRU176 Data set list saved - The listing of data
Explanation: The PD option cannot be used of the sets was placed in ’aaaaaaaa.’
data to be printed is a member of a PDS.
Explanation: This is an informational message.
User Response: Use the PK option to print the
member.
ISRU177 VTOC information printed - The VTOC
information for aaaaaaaa was placed in
ISRU170 No data set names found - No data set the ISPF List data set.
names were found to satisfy the search
Explanation: This is an informational message.
argument(s).
Explanation: This is an informational message.
ISRU178 Volume not mounted - Volume aaaaaaaa
is not mounted or is unavailable.
ISRU171 No data set names found - No data sets
Explanation: The volume you are trying to access is
are cataloged that start with ’aaaaaaaa’.
not mounted.
Explanation: This is an informational message.
User Response: Contact your system programmer.
System Programmer Response: Mount the volume.
ISRU172 Dsname level error - Remove the quotes
from the Dsname Level.
ISRU179 Enter 2nd operand - A second operand
Explanation: The syntax of the Dsname Level is
is required for the LOCATE command.
invalid. Quotation marks are not needed around the
Dsname Level. Explanation: The LOCATE command requires that a
search string be entered.
User Response: Enter a Dsname Level without
quotation marks. User Response: Reissue the command with a search
string.
ISRU173 Catalog search error - Locate return code
for catalog search was aaaaaaaa decimal. ISRU180 Invalid LOCATE operand - Table is
sorted by aaaaaaaa. Operand is not a
Explanation: A catalog error has occurred during a
valid fixed value.
locate.
Explanation: An invalid LOCATE string was entered.
User Response: Contact your system programmer.
User Response: Enter a valid search string.
System Programmer Response: Correct the catalog
error.
ISRU181 LOCATE search error - Return code -
aaaaaaaa - received while searching table.
ISRU174 TBCREATE failure - Creating the table
of data set names resulted in return Explanation: A return code greater than 8 was
code aaaaaaaa. received from the TBSKIP service.
Explanation: A return code greater than 4 was User Response: Log off, log back on, and retry. If the
received from the TBCREATE service. error persists, contact the system programmer.
User Response: The error is probably due to the table System Programmer Response: Contact IBM support.
being in use by another session. Free the table from
that session and retry.
ISRU182 Invalid command - The command ISRU193 Vol aaaaaaaa not mounted - Volume must
entered is not valid for the Data Set List be mounted to list the VTOC.
Utility.
Explanation: The volume you are trying to get a
Explanation: A command was entered that is not VTOC list from is not mounted.
supported by the Data Set List.
User Response: Contact your system programmer.
User Response: Enter a valid data set list primary
System Programmer Response: Mount the volume.
command: CONFIRM, FIND, LOCATE, SAVE,
SHOWCMD, or SORT.
ISRU194 Compress not allowed - The specified
library is a PDSE and cannot be
ISRU185 Incomplete string - Put a quote to
compressed.
indicate the end of the string.
Explanation: This is an informational message.
Explanation: A 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 ISRU195 VTOC error - OBTAIN return code =
string. ’aaaaaaaa’.
User Response: Correct the FIND command string Explanation: An error was encountered reading a
and retry. format 4 DSCB.
Problem Determination: See the appropriate
ISRU186 Invalid date - Specify a date in the DFP/DFSMS documentation for return code
format YYYY/MM/DD. descriptions.
Explanation: When the data set list is sorted by one of
the date fields, the argument of the LOCATE command ISRU196 Free space error - LSPACE return code =
must be a valid date. ’aaaaaaaa’ decimal.
User Response: Correct the invalid date format as Explanation: An error occurred when issuing the
instructed and retry the LOCATE command. LSPACE macro to obtain VTOC free space information.
Problem Determination: See the appropriate
ISRU187 Enter required field - Dsname level DFP/DFSMS documentation for return code
and/or volume must be specified. descriptions.
Explanation: Either dsname level, volume or both
must be specified when requesting a data set list. ISRU197 VTOC error - CVAF macro (SVC139)
return code = ’aaaaaaaa’.
User Response: Specify a Dsname Level, a Volume
serial, or both to indicate which data sets are to be Explanation: An error occurred when issuing a CVAF
included in the list. Entering a Volume serial with a macro to obtain VTOC or data set information.
blank Dsname level will call up a list of all the data
sets on the volume. Problem Determination: See the appropriate
DFP/DFSMS documentation for return code
descriptions.
ISRU188 Duplicate data set name - Data set is
cataloged on a volume other than
aaaaaaaa. ISRU199 Invalid record format - A record format
of U is not valid when creating a PDSE.
Explanation: An SMS data set with the same name is
cataloged on another volume. Any attempt to allocate Explanation: A record format of U is not supported
the uncataloged version of the data set will result in the when creating a PDSE.
SMS version of the data set being allocated. User Response: Either enter a supported record
format for a PDSE, or allocate as a PDS.
ISRU190 aaaaaaaa VTOC printed - VTOC listing
of volume aaaaaaaa placed in bbbbbbbb. ISRU200 Rename failed - RACF RC=8 for rename
Explanation: This is an informational message. of aaaaaaaa.
Explanation: RACF has returned a return code of 8 on
a data set rename.
User Response: Check your RACF authorization.
User Response: Contact your system programmer. Explanation: This is an informational message. The
requested print function has ended.
System Programmer Response: Perform diagnostics
on the data set causing the error.
ISRU228 Invalid class - Class must be
alphanumeric (A-Z, 0-9).
ISRU220 Allocation failed - Allocation of print
data set failed. Explanation: This is an informational message. An
invalid class has been entered. The class must be either
Explanation: The allocation of the Print temporary A-Z or 0-9.
data set has failed.
User Response: Contact your system programmer. ISRU229 Member not found - Member ″aaaaaaaa″
System Programmer Response: Find out why the not found, only library 1 searched for
temporary data set was not allocated. Make sure that MOVE/PROMOTE services.
the packs that the user has access to are not full and Explanation: The member was not found in the
that a data set by the same name does not already specified library. Only one library was entered.
exist.
ISRU235 Invalid required parm - Select the ISRU241 Too many sort fields - You may specify
required parameter from the options up to two fields for use with the SORT
shown. command.
Explanation: Enter one of the valid options listed to Explanation: Too many SORT operands have been
complete the command. entered for the SORT command. A maximum of two
operands can be entered per SORT command.
User Response: Enter a listed valid option.
User Response: Correct the number of SORT
operands.
ISRU243 Invalid operand - Valid CONFIRM ISRU250 Four char. year invalid - The MVS
operands are ON and OFF. system must be MVS/XA, level MVS/SP
2.2.0 or higher.
Explanation: An invalid CONFIRM operand was
entered. The valid operands are ON and OFF. Explanation: This MVS system is not a level that will
support the 4 character year that has been entered.
User Response: Use a valid CONFIRM operand,
either ON or OFF. User Response: Enter a valid date that is supported
by this MVS system.
ISRU244 Data set saved - The data set was saved.
ISRU251 Value too large - The maximum
Explanation: This is an informational message.
retention period allowed is 9999.
Explanation: The retention period that has been
ISRU245 Invalid command – Only ISPF system
entered is greater than 9999. A retention period value
commands may be entered on this
must be less than or equal to 9999 days.
panel.
User Response: Enter a value for the retention period
Explanation: An invalid command was entered on the
less than or equal to 9999 days.
command line.
User Response: Specify a valid command. Enter HELP
ISRU252 Invalid date - The date specified
when this message is displayed for command
contains invalid values.
information.
Explanation: The date that has been entered into the
expiration date field has invalid values. These values
ISRU247 This list of data set names contains
could be an invalid day or month, or a character
entries from a CVOL catalog. The list
entered into the day, month, or year field.
exceeded the maximum number of
names allowed in the input area and User Response: Correct the incorrect value that has
may be incomplete. been entered for the day, month, or year.
Explanation: A data set list did not build completely
using the qualifiers entered. ISRU253 Date not allowed - The date specified is
only valid with 4 character year support.
User Response: Verify the qualifiers, then consult your
system programmer. Explanation: The date that was entered in Julian
format is not supported on the level of MVS that is on
System Programmer Response: Verify that all DASD
your system.
is operational and that valid qualifiers are being used.
User Response: Correct the Julian date, or enter the
date in character form using a 2 character year.
ISRU248 Incomplete list printed - The list of data
set names exceeded the allocated input
area. ISRU254 Compress successful - The data set was
successfully compressed by the
Explanation: An incomplete data set list was printed.
compress exit.
User Response: Verify the data set qualifiers.
Explanation: This is an informational message. The
data set that the compress was requested for has
ISRU249 Error during list print - An error was completed successfully.
encountered trying put list into the ISPF
List data set.
ISRU256 Severe error - A severe error was
Explanation: An error occurred while attempting to returned by ISPF compress.
print the ISPF list data set.
Explanation: ISPF ran a compress on a data set and a
User Response: Verify that the ISPF list data set is return code that was greater than or equal to 20 was
available and is large enough to retain your data. returned.
Problem Determination: Check the ISPF list data set User Response: See what data set the compress was
attributes. done against and check the the data set characteristics
to see if there is any problem with the data set.
ISRU257 Data set not partitioned - The data set ISRU264 No previous command - The ’=’
for compress must be partitioned. command cannot be used until a line
command has been entered.
Explanation: The data set that the compress was
issued against is not a partitioned data set, so the Explanation: A previous line command has not been
compress cannot be executed. To do a compress, the issued so the ″=″ command cannot be used.
data set must be partitioned.
User Response: Enter the line command you were
User Response: Do not compress data sets that are not attempting to retrieve.
partitioned.
ISRU265 Data set does not exist - ’aaaaaaaa’ was
ISRU258 Member aaaaaaaa saved - bbbbbbbb was deleted or uncataloged.
edited and saved.
Explanation: The data set requested is not cataloged,
Explanation: This is an informational message. The not uncataloged, not a GDG, or on a tape. It does not
data set listed was saved. exist.
User Response: Check to see if the data set has been
ISRU259 Data set not deleted - Delete request for removed from the system.
″aaaaaaaa″ was cancelled by user.
Explanation: This is an informational message. The ISRU266 Member too long - A member
data set was not deleted. The confimation of the data name/pattern must be 8 or less
set delete was cancelled. characters in length.
Explanation: The member name is greater than 8
ISRU260 Retrieving data set information to characters.
process your aaaaaaaa request.
User Response: Enter a valid member name or pattern
Explanation: This is an informational message. Your that is 8 characters or fewer.
request is being processed.
ISRU267 Data set not found - ″aaaaaaaa″ not
ISRU261 Invalid operand - Valid SHOWCMD found on volume bbbbbbbb.
operands are ON and OFF.
Explanation: The requested data set is not on the
Explanation: An invalid operand has been entered specified volume.
with the SHOWCMD command. Valid operands are
User Response: Either enter the correct volume for the
ON and OFF.
data set, or enter just the the data set name.
User Response: Enter the SHOWCMD command with
an ON or OFF operand.
ISRU268 Command too long - Command
expansion caused the command to
ISRU262 Panel not found - The specified data set exceed 255 characters.
list panel could not be found.
Explanation: The command that was entered exceeds
Explanation: The data set list panel requested could the maximum length of 255 characters.
not be found.
User Response: Reenter the command with fewer
User Response: Contact your system programmer. than 255 characters.
System Programmer Response: Check to see that the
specified data set list panel exists and can be displayed. ISRU269 Invalid DSORG - Data set organization
must be either partitioned or sequential.
ISRU263 Table processing error - An error Explanation: This is an informational message. The
occurred during control table data set organization is invalid. In order to execute a
processing. FREE command, the data set organization must be
partitioned or sequential.
Explanation: There is a problem in creating the table
needed to store the program state.
ISRU273 Delete confirmation on - A confirmation
User Response: Contact your system programmer.
panel will be displayed for data set
System Programmer Response: Check to see why the deletion requests.
requested table was not created.
Explanation: This is an informational message.
Confirmation has been set to ON for data set deletion
Explanation: A value of 0 was entered into the Explanation: This is an informational message. The
Primary Quantity field, but the Primary Quantity field listing file is being printed, and will be deleted when
of a partitioned data set cannot be set to 0. the print function is finished.
ISRU287 Utility - Com print – aaaaaaaa directed to ISRU291 Job skeleton not found - Job card
local printer bbbbbbbb and cccccccc skeleton ″ISRSCHPJ″ was not found.
Explanation: This is an informational message. The Explanation: The job card skeleton, ISRSCHPJ, cannot
list file is directed to the specified local printer ID. be found.
User Response: Contact your system programmer.
ISRU288 SMS not active – SMS is not active.
System Programmer Response: Verify that you have
Enhanced data set allocation is
the PDF skeletons in your system concatenations.
unavailable.
Problem Determination: The ISPF/PDF skeletons are
Explanation: SMS is not active on your MVS system.
not in your system concatenations.
User Response: Use the A fastpath command, or the
space pull-down to allocate the data set as a non-SMS
ISRU292 Enter option - Enter one of the listed
data set.
options.
Programmer Response: Informational.
Explanation: One of the highlighted options displayed
below on this panel should be entered.
ISRU289 20 or more volumes – The information
User Response: Enter one of the highlighted options.
displayed is for the first 20 volumes of
this data set. If there are more than 20
volumes, the information may be ISRU293 Data set not printed - An uncataloged
incorrect. data set cannot be printed using option
3.6 with a print mode of LOCAL if there
Explanation: No explanation available at this time.
exists a cataloged data set by the same
name.
ISRU290 Data set not printed. – aaaaaaaa has been
Explanation: The hardcopy utility cannot process an
kept. See the ISPF Messages and Codes
uncataloged data set if a cataloged data set by the same
or Help for Local Print RC = bbbbbbbb.
name exists on the system.
Explanation: The attempt to print the data set on a
User Response: Use another method to print the data
local printer was unsuccessful. The listing data set will
set.
be kept. Possible return codes are:
2 The user cancelled local print.
ISRU294 Unexpected return code - Return code
4 ISPF issued the TSO PRINTDS command, but ″aaaaaaaa″ from the print utility exit. The
the user pressed ATTENTION during listing is kept.
PRINTDS.
Explanation: An unexpected return code was received
6 Local print has been disabled by the system while attempting to exit from the print utility. The
programmer. Your system programmer has set listing data set will be kept.
the LOCALPRT field in ISRCNFIG to blank,
User Response: Contact your system programmer.
which disables local print.
System Programmer Response: Check the print utility
8 ISPF issued the TSO PRINTDS command, but
exit.
TSO PRINTDS abended. Further information
may be available from TSO PRINTDS by
setting WTPMSG and MSGID in your TSO ISRU295 TSO/E ICF not installed - The TSO/E
profile. information center facility (TSO/E ICF)
is not installed.
12 TSO PRINTDS had a return code greater than
zero. Further information may be available Explanation: The TSO/E Information Center Facility is
from TSO PRINTDS by setting WTPMSG and not installed on your system.
MSGID in your TSO profile.
User Response: Contact your system programmer.
16 Unexpected return code from local print.
System Programmer Response: Verfiy that the
User Response: Contact your system programmer. Information Center Facility (TSO/E ICF) is installed.
System Programmer Response: Verify that the local
print function is set up correctly.
ISRU296 Print utility exit - The print utility exit ISRU304 TSO/E ICF msg not found - TSO/E ICF
produced a return code of aaaaaaaa. message variable not found. Contact
your system programmer.
Explanation: This is an informational message. The
print utility exit produced a return code that was Explanation: TSO/E ICF encountered an error while
received on on the print utility exit. processing the specified print request, but no message
was found in ICF dialog variable QCPMSGID.
ISRU297 Submit error - An error occurred while User Response: Contact your system programmer.
submitting JCL generated by the print
System Programmer Response: Refer to the ICF
utility exit.
documentation for problem determination.
Explanation: An error occurred when the JCL
generated by the print utility exit was submitted.
ISRU305 Data set not deleted - Data set does not
User Response: Check the JCL for the error. exist or not sufficient authority
Explanation: PDF received a return code 8 from the
ISRU298 Utility - TSO/E ICF - aaaaaaaa printed by SCRATCH macro, indicating that the data set to be
TSO/E ICF and bbbbbbbb. deleted either does not exist, or you do not have
sufficient RACF authority to delete the data set.
Explanation: This is an informational message. The
TSO/E Information Center Facility print was invoked User Response: Verify that the data set exists. If it
to print the list file. 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,
ISRU299 Data set not renamed - The data set
either have the data set deleted by someone that does
rename request was cancelled by the
have sufficient RACF authority, or contact your RACF
user.
administrator to have your authority level changed.
Explanation: This is an informational message.
ISRU306 RECFM not supported - Standard
ISRU301 List data set not found - List data set records are not supported for the FREE
aaa(44) cannot be found. command.
Explanation: The list data set specified for printing Explanation: The PDF FREE command (the F line
(aaa(44)) does not exist; therefore, it cannot be printed. command from an option 3.4 data set list) is not
supported for Fixed Standard record formats.
User Response: Regenerate the listing and resubmit
the print job. User Response: Find an alternate way to free the
space in the data set.
User Response: Contact your system programmer. PDF successfully cataloged the new data set name, but
could not rename the data set from the old name to the
System Programmer Response: Refer to the ICF new name. PDF then attempted to uncatalog the new
documentation for problem determination. 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.
User Response: Contact your system programmer.
ISRU331 Invalid record format - U is not valid ISRU337 Invalid combination - Copy request
with B or S. incomplete due to invalid pack
combination. When copying to a
Explanation: Undefined format records cannot be
sequential data set with disposition of
Blocked, Standard, or Spanned.
mod and pack option of asis, you cannot
User Response: Choose another record format and copy both packed and unpacked data,
retry the function. nor can you copy multiple packed
members. aaaa members were
successfully copied during this
ISRU332 Numeric out of range - Record length of operation.
zero is valid only if record format is U.
Explanation: One of the two following conditions
Explanation: When allocating a data set using Fixed occurred during an attempt to copy multiple members
or Variable format records, a non-zero record length is of a PDS (or concatenation of PDSs) to a sequential
required. A zero record length is only valid for data set, using a disposition of MOD:
Undefined format records. v Both packed and unpacked members were selected
User Response: Specify a non-zero record length, or to be copied.
use record format U. v Multiple packed members were selected to be
copied.
ISRU334 Invalid disposition - Packing data is Either of these cases results in data that cannot be
invalid if DISP=MOD is specified. processed by ISPF.
Explanation: When copying to a sequential data set User Response: To copy multiple PDS members to a
with disposition MOD (which appends the copied data sequential data with a disposition of MOD, all PDS
to the existing data in the data set), the data being members must either be unpacked or copied with a
copied cannot be packed. If the data being copied is pack option of NO. In addition, the target sequential
packed, data will be created that ISPF cannot process. data set must either be empty or contain unpacked
data.
User Response: Either 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. ISRU338 Invalid member name - The member
name is invalid for a partitioned data
set.
ISRU335 aaaaaaaa failed - Specifying DISP=MOD
is invalid if ″to″ data set has packed Explanation: A member name containing invalid
data. characters was specified for processing.
Explanation: When copying to a sequential data set User Response: Correct the member name. A valid
that already contains packed data, you cannot specify a member name must be 1-8 characters in length, start
disposition of MOD (which appends the copied data to with an alphabetic or special character, and contain
the existing data in the data set) because data will be only alphabetic, numeric, and special characters.
created that ISPF cannot process.
User Response: Either use a disposition of OLD, or ISRU339 ″From″ data set empty - Empty ″from″
unpack the target sequential data set before attempting PDS member or sequential data set has
the COPY command. been requested.
Explanation: A request was made to copy from a PDS
ISRU336 Unable to read data set - An error was member or sequential data set that does not contain
encountered while reading the ″to″ data any data.
set. User Response: Specify a member or data set that
Explanation: When copying to a sequential data set contains data.
using a disposition of MOD, ISPF reads the first record
of the target sequential to determine whether or not the ISRU340 Error during list print - An error was
data set contains packed data. An I/O error was encountered trying to put list into
encountered while attempting to read that first record. ’aaa(44).’
User Response: Contact your system programmer. Explanation: ISPF encountered an internal table
services error while processing the SAVE command.
User Response: Contact your system programmer.
System Programmer Response: Contact IBM support.
ISRU341 List not printed - The list data set for ISRU345 Free failed - aaaa failed for data set
the option 3.4 SAVE command must be ’bbb(44)’.
a sequential data set with logical record
Explanation: ISPF could not free the unused space for
length greater than or equal to 132 for
data set bbb(44) due to a failure in either the OPEN or
RECFM F and greater than or equal to
RDJFCB macro (as indicated by aaaa above).
136 for RECFM V.
User Response: Contact your system programmer.
Explanation: The option 3.4 SAVE command was
issued, specifying a list-id to have the data set list System Programmer Response: Follow normal
information written to a data set named problem determination procedures.
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 132 for RECFM F and ISRU346 Utility - free - Any unused space freed
greater than or equal to 136 for RECFM V. for data set ’aaa(44)’.
User Response: Use a different list-id to have ISPF Explanation: This is an informational message. The
write the data set list information to another data set, ISPF data set list FREE command has been completed
or delete and reallocate the existing data set to have the successfully.
proper characteristics.
ISRU347 Free completed - Any unused space
ISRU342 Data set list printed - The listing of data freed for data set ’aaa(44)’. Enter HELP
sets was placed in the ISPF list data set. for further information on when space
may not be freed from the data set.
Explanation: This is an informational message. The
option 3.4 SAVE command was successfully processed Explanation: This is an informational message. The
and the requested information has been written to the ISPF data set list FREE command has been completed
ISPF list data set. successfully.
ISRU343 Invalid list-id - ″aaaaaaaa″ contains ISRU348 Internal program error - ESTAE failed
invalid characters. during initialization in module ISRUAF.
Explanation: The option 3.4 SAVE command was Explanation: ISPF encountered an error from the
invoked with a list-id parameter, indicating that the ESTAE macro while processing the data set list FREE
data set list information should be written to a data set. command.
The list-id parameter, used as the middle qualifier of User Response: Contact your system programmer.
the data set, did not conform to ISPF naming
conventions. System Programmer Response: Contact IBM support.
ISRU353 ″From″ data set in use - ″From″ data set ISRU359 Incomplete list - Insufficient work
is being updated by you or another user. space. Press Help key for additional
information.
Explanation: A Move, Copy, Copy/Lock, or Promote
request was issued, but the data set specified as the Explanation: The work area required to process the
source of the operation is currently in use by you or current data set list request exceeds the area currently
another user. available.
User Response: Identify the person using the data set User Response: Try one of the following:
and request that they release it, or try again later. v Reenter the %DSNAME LEVEL+ with an additional
full qualifier before any defaulted or partial
qualifiers. (As an example, specify ABC.XYZ instead
ISRU354 ″To″ data set in use - ″To″ data set is
of ABC.XYZ* or ABC.XY*.)
being updated by you or another user.
v Increase the region size.
Explanation: A Move, Copy, Copy/Lock, or Promote
request was issued, but the data set specified as the
ISRU360 SCLM warning - The project being
target of the operation is currently in use by you or
updated is an SCLM controlled project.
another user.
Explanation: This is an informational message. ISPF
User Response: Identify the person using the data set
has identified the data set you are processing as a
and request that they release it, or try again later.
possible SCLM-controlled library. If the library is
indeed SCLM-controlled and you continue with the
ISRU355 ″From″ member in use - ″From″ member request, you will invalidate the SCLM accounting
is being updated by you or another user. information stored in its VSAM database. This will not
result in a loss of data, but will require you to use
Explanation: A Move, Copy, Copy/Lock, or Promote either the SCLM Migrate utility (option 10.3.3) or
request was issued, but one or more of the members SCLM Edit (option 10.2) to correct the accounting
specified as the source of the operation are currently in information before building or promoting the member.
use by you or another user.
User Response: Identify the person(s) using the ISRU361 No changes made - No updates have
member(s) and request that they release them, or try been made to the member statistics.
again later.
Explanation: This is an informational message. The
user responded that no updates should be done after
ISRU356 ″To″ member in use - ″To″ member is being prompted with a warning that the library being
being updated by you or another user. processed may be an SCLM-controlled data set.
Explanation: A Move, Copy, Copy/Lock, or Promote
request was issued, but one or more of the members ISRU362 Duplicate data set - Requested data set
specified as the target of the operation are currently in was allocated and found to be cataloged
use by you or another user. on a volume other than aaaaaa. The
User Response: Identify the person(s) using the subsequent attempt to free the data set
member(s) and request that they release them, or try failed with SVC 99 error code bbbb,
again later. information code cccc.
Explanation: The user specified a data set and volume
ISRU358 aaaaaaaa failed - ″From″ record length is combination, but SVC 99 allocated a data set by the
greater than ″to″ block size for record same name on a different volume. This usually
format U. indicates that a data set with the same name as the
data set requested by the user exists on an SMS
Explanation: When copying or moving members controlled disk. To protect data set integrity, ISPF will
between 2 record format U libaries, the block size of not allow the request to be completed. However, when
the target library must be equal to or greater than that attempting to free the incorrect allocation, an SVC 99
of the source data set. error was encountered. SVC 99 returned an error code
User Response: Reallocate the target library so that it of bbbb, information code of cccc.
has an appropriate block size, or copy the member to a User Response: Contact your system programmer.
different library.
ISRU363 Recursion error - ISPF recursion error ISRU368 Catalog error - SVC 26 CAMLST locate
invoking the compress function. RC = aaaaaaaa dec., reason code bbbbbbbb
dec.
Explanation: ISPF does not support the recursive
invocation of functions that use file tailoring. An Explanation: A catalog error occured during a
attempt was made to invoke the ISPF compress CAMLST locate. The return code and reason code are
function while another file tailoring function is already specified in the message. System message IDC3009I
active on a previous command nesting level. The other documents return and reason codes for the CAMLST
file tailoring functions monitored for recursion are: macro.
v Foreground (option 4)
User Response: Contact your system programmer.
v Batch (option 5)
v Hardcopy utility (option 3.6)
v Outlist utility (option 3.8) ISRU369 Select options - Select the options
v SuperC (options 3.12, 3.13 and 3.14). needed for processing.
User Response: Complete the previously nested file Explanation: Informational message for SuperC and
tailoring function, then retry the compress request. Search-For issued from the ISPF Workplace.
| ISRU364 Unsupported data type - One or more ISRU370 aaaa failed - aaaa failed for member
| PDSE load module libraries have been bbbbbbbb.. Failure in IEWBIND cccccccc,
| detected in the input to the Move/Copy return code dddd reason code eeee.
| utility, the LMCOPY service, or the
| LMMOVE service. Data sets of this type Explanation: When processing a Move/Copy request
| are not currently supported by these for load data on a DFSMS 1.1 or later system, ISPF
| ISPF functions. Press Help for more invokes the binder to do the actual copy. ISPF
| information. encountered an error during the cccccccc phase of the
binder invocation. The following flow describes the
| Explanation: This message is self explanatory. binder calls made during a Move/Copy operation:
v IEWBIND STARTD - Start a binder dialog
| ISRU365 Unsupported data type - aaaaaaaa is a v IEWBIND CREATEW - Create a binder workmod
| PDSE load module library. Data sets of v For each member to be copied:
| this type are not supported for the
| Move/Copy utility, LMCOPY service or – IEWBIND INCLUDE - Specify the input member
| LMMOVE service. to be processed
– IEWBIND SAVEW - Save the member to the
| Explanation: This message is self explanatory. output library
– IEWBIND RESETW - Reset the workmod for the
ISRU366 Delete not supported - ″aaaaaaaa″ is an next member
uncataloged SMS data set. The delete v IEWBIND DELETEW - Delete the workmod
command is not supported for an
uncataloged SMS data set. v IEWBIND ENDD - End the binder dialog
Explanation: SMS data sets should always be User Response: Refer to the appropriate DFSMS
cataloged. The scratch macro does not support documentation for an explanation of the return code
uncataloged SMS data sets. and reason code from the binder, and follow the
recommended diagnostic steps to correct the problem.
User Response: Contact your system programmer.
Explanation: A catalog error occured during a A load data set is defined by ISPF as:
CAMLST locate. The data set name is listed without a v A PDS with record format U
volume. One reason for the failure may be an indirect v A PDSE that contains program objects (as determined
volser being offline. by invoking the DFP ISITMGD macro).
User Response: Contact your system programmer. All other data is considered non-load.
User Response: Correct the input data sets to specify
ISRU376 List not displayed. - The Data Set List ISRU402 TBTOP failure - Return code aaaa
Filter exit generated a return code other received from TBTOP command.
than 0 or 4 resulting in the data set list
Explanation: The data set list processor encountered
not being displayed.
an internal error while invoking the TBTOP service.
Explanation: The Data Set List Filter exit specified in
User Response: Contact your system programmer.
the ISPF Configuration Table returned a code other
than 0 or 4. This causes ISPF to stop building the data System Programmer Response: Contact IBM support.
set list and redisplay the Data Set List Utility panel.
ISRU414 Enter character string – A character ISRU419 aaaaaaaa bbb(44) found - Search for
string for FIND has not been entered (so aaaaaaaa bbb(44) was successful.
* is invalid).
Explanation: This is an informational message. A
Explanation: An asterisk (*) used as the target string FIND command was entered on a data set list, and the
of the FIND command indicates that the previous string was successfully located.
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. ISRU420 *Bottom of list reached* - aaaaaaaa
bbb(44) not found. Press the RFIND key
User Response: Enter a valid target string. Once a to continue the search from the top for
target string is entered, the asterisk may then be used the data set list.
on subsequent FIND commands.
Explanation: This is an informational message. The
data set list FIND command searches from the top of
ISRU415 FIND string too long – The FIND string the displayed data to the bottom of the list to find the
cannot be longer than 44 characters. target string. FIND has searched and reached the
Explanation: The FIND command searches for the bottom of that list without finding the target string.
specified target string within the list of data set names. Entering the RFIND command continues the search,
Since the maximum length of a data set in the list is 44 starting from the top of the data set list.
characters, the target string may not exceed 44
characters. ISRU421 * Top of list reached * - aaaaaaaa bbb(44)
User Response: Retry the command, entering a target not found. Press the RFIND key to
string that is equal to or less than 44 characters in continue the search from the bottom for
length. the data set list.
Explanation: This is an informational message. When
ISRU416 Invalid character string - The FIND the PREV keyword is specified, the data set list FIND
string cannot be a null (’’) string. command searches from the top of the displayed data
to the top of the list to find the target string. FIND has
Explanation: The FIND target string must be a searched and reached the top of that list without
minimum of 1 character in length. A target string of 0 finding the target string. Entering the RFIND command
characters was entered. continues the search, starting from the bottom of the
User Response: Retry the command, entering a target data set list.
string that is equal to or greater than 1 character in
length. ISRU422 No aaaaaaaa bbb(44) found - aaaaaaaa
bbb(44) - not found in any X’ed data set
ISRU417 Enter a FIND command - The RFIND names.
key works only after a FIND character Explanation: This is an informational message. A
string is entered. FIND or RFIND command was entered to cause the
Explanation: The RFIND command reissues the last data set list processor to search the entire data set list
FIND command that was entered. RFIND cannot be for the specified target string. The search was
issued until at least one FIND command has been completed, but the target string was not found.
processed.
User Response: Enter a valid FIND command. Once ISRU423 Invalid string type - Data set list FIND
entered, the RFIND command may be used to reissue command does not process picture
the same FIND command. (P’...’), hex (X’...’), text (T’...’) or char
(C’...’) strings.
Explanation: The data set list FIND command does
not support all of the keywords supported by the
editor FIND command. The following are not
supported:
v Picture strings (P’...’)
ISRU426 Severe error occurred - The data set list ISRU431 Invalid space units – Must be TRKS,
line command exit issued a return code BLKS, CYLS, KB, MB, BYTES, or
of 20. RECORDS.
Explanation: A data set list line command exit is Explanation: When creating a data set under ISPF
specified in the configuration table you are currently option 3.2, the space to be allocated must be specified
using. This exit has returned a return code of 20, as Tracks, Blocks, Cylinders, Kilobytes, Megabytes,
indicating a severe error has been encountered. Bytes, or Records.An unsupported value was entered.
User Response: Contact the author of the exit for help User Response: Correct the value for space units and
in determining the cause of the error. retry the request.
ISRU427 Unknown return code - The data set list ISRU432 Invalid request – Managed data sets
line command exit issued a return code cannot be cataloged.
of aaaa.
Explanation: Data sets managed by the SMS
Explanation: A data set list line command exit is subsystem cannot be cataloged or uncataloged.
specified in the configuration table you are currently
using. This exit has returned an unsupported return User Response: Verify that the data set name entered
code of aaaa. Supported return codes from the exit are is correct. If not, correct it and retry the request.
0, 4, 8, and 20.
User Response: Contact the author of the exit for help ISRU433 Invalid request – Managed data sets
in determining the cause of the unsupported return cannot be uncataloged.
code. Explanation: Data sets managed by the SMS
subsystem cannot be cataloged or uncataloged.
ISRU428 LOCATE failed - The LOCATE for User Response: Verify that the data set name entered
’aaa(44)’ failed, RC = bbbb. is correct. If not, correct it and retry the request.
Explanation: The data set list processor issued a
LOCATE macro to gather information on data set
ISRU448 Enter a number between 2 and 255. ISRU462 Type mismatch - The request type of the
member you are trying to get does not
Explanation: The STRNO value must be a decimal
match the request type being defined.
number between 2 and 255. Refer to the appropriate
IDCAMS documentation for specific information on Explanation: You cannot get a member if the data in
these options. 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
ISRU455 Command canceled - Profile command
cluster define.
has been canceled.
Explanation: This is an informational message.
ISRU463 Profile read error - A failure has
Changes made to the name of the profile data set have
occurred reading profile member.
not been made because the CANCEL command was
performed. Explanation: A LMGET call for data in the profile
data set has failed.
ISRU457 Enter a number 1 to 9999. User Response: Contact your system programmer.
Explanation: The file sequence field values must be a System Programmer Response: Contact IBM support.
number between 1 and 9999. Refer to the appropriate
IDCAMS documentation for specific information on
ISRU464 Allocate error - Unable to allocate the
these options.
profile data set: The data set must be a
variable partitioned data set with an
ISRU458 Member not found - The member you LRECL of 203.
are trying to get does not exist.
Explanation: The profile data set must be a variable
Explanation: The member cannot be retrieved because partitioned data set with an LRECL of 203.
it does not exist.
User Response: Enter an unallocated data set (PDF
User Response: Enter a member that exists, or enter a will allocate the data set) as the profile data set, or
GET command with no parameters and a list of allocate a profile data set with the correct allocations.
existing members will be displayed.
ISRU465 Enter a numeric value between ’0’ and
ISRU459 List action de-selected - List action ’16777215’.
erased. Any additional list actions will
Explanation: The primary and secondary quantity
be ignored.
valuse must between 1 and 16777215.
Explanation: An invalid list action was de-selected
and an action was requested against a different list
ISRU466 Data saved - Data has been saved to
entry. Only one list may be processed at a time.
profile.
User Response: Select a new list action or enter a list
Explanation: This is an informational message.
action to perform.
ISRU474 Enter decimal number between 1 and ISRU486 IDCAMS has returned a non-zero return
16776704. code.
Explanation: Valid Buffer Space value is a decimal Explanation: This is an informational message.
number between 1 and 16776704. Refer to the
appropriate IDCAMS documentation for specific User Response: See IDCAMS output for details.
information on this options.
ISRU487 Request canceled - Process request has
ISRU475 Enter a year between 1993 and 2099. been canceled.
Explanation: The year value of the Days To field must Explanation: This is an informational message.
be between 1993 and 2099. Refer to the appropriate
IDCAMS documentation for specific information on ISRU489 Enter Noerase or Erase.
this options.
Explanation: Valid calues for this field are ERASE or
NOERASE. Refer to the appropriate IDCAMS
ISRU476 Enter a day between 1 and 365. documentation for specific information on this options.
Explanation: The day value of the Days To field must
be between 1 and 365. Refer to the appropriate ISRU490 Enter Noforce or Force.
IDCAMS documentation for specific information on
this options. Explanation: Valid values for this field are FORCE
and NOFORCE. Refer to the appropriate IDCAMS
documentation for specific information on these
ISRU477 Return Code 0 - The IDCAMS command options.
processed for aaaaaaaa was successful.
Explanation: This is an informational message. ISRU491 Enter Nopurge or Purge.
Explanation: Valid values for this field are PURGE
ISRU479 Enter a decimal number between 1 and and NOPURGE. Refer to the appropriate IDCAMS
255. documentation for specific information on these
Explanation: The length value of the Keys field must options.
be between 1 and 255. Refer to the appropriate
ISRU508 Enter All, Allocation, History, Name, ISRU516 The choice selected is not valid for the
Volume or leave blank. request type selected.
Explanation: Valid values for this field are ALL, Explanation: The VSAM Data Type selected is not
ALLOCATION, HISTORY, NAME, VOLUME or blank. valid for the Process Request entered.
Refer to the appropriate IDCAMS documentation for
User Response: Correct either the VSAM Data Type or
specific information on these options.
the Process Request, then retry the request.
ISRU521 Invalid length qualifier - All Dsname ISRU527 Data set aaaaaaaa - Data set ’bbb(44)’
Level qualifiers must be 1 to 8 aaaaaaaa to library cccccccc.
characters in length.
Explanation: This is an informational message.
Explanation: There is a qualifier of 0 or more than 8
Programmer Response: None.
characters in the Dsname Level entered.
User Response: Correct the Dsname Level qualifier.
ISRU528 Catalog search error - The return code
Programmer Response: None. for a catalog search on ’aaaaaaaa’’ was
bbbbbbbb, the reason code was cccccccc,
Problem Determination: Verify the Dsname levels,
and the module id was dddddddd.
each must be 1 to 8 characters in length.
Explanation: The catalog search to find the requested
data set names failed.
ISRU522 Invalid VSAM delete - Delete is an
invalid command for VSAM data and User Response: Refer to the appropriate DFP
index components. Delete is only documentation for an explanation of the error.
allowed on the cluster component.
Programmer Response: None.
Explanation: If you want to delete a VSAM data set,
issue the delete command against the VSAM cluster.
ISRU529 List may be incomplete. - Catalog search
Programmer Response: None. error. The return code for a catalog
search on aaaaaaaa was bbbbbbbb, the
reason code was cccccccc, and the
ISRU523 Catalog search cancelled - Enter a
module id was dddddddd.
Dsname Level with a high level
qualifier other than ’*’ or ’**’. Explanation: The catalog search to find the requested
data set names failed.
Explanation: A high level qualifier of ″*″ (asterisk) or
″**″ (double asterisk) requires a search of all the User Response: Refer to the appropriate DFP
catalogs on the system. This may require a great deal of documentation for an explanation of the error.
time. You have chosen to cancel this search. Continue
Programmer Response: None.
by entering another dsname level.
User Response: Change the Dsname Level.
ISRU530 Data retrieved – The GET command
Programmer Response: None. completed. Data from the profile was
retrieved and stored into the panel input
Problem Determination: Change the first level of the
fields.
Dsname to some thing other than ’**’ or ’*’.
Explanation: This is an informational message.
ISRU524 RDJFCB failed - The RDJFCB macro
failed for data set ’aaa(44)’. ISRU531 Profile name set – The profile data set
name has been set and the data set was
Explanation: An attempt to read the JFCB for the the
allocated if it did not previously exist.
multivolume data set specified was not successful.
Explanation: This is an informational message.
User Response: Contact your system programmer.
Programmer Response: None.
ISRU532 Enter a decimal value between 0 and
Problem Determination: Verify the sort operand. 32768.
Explanation: Valid values for the Length value of the
ISRU525 Data set aaaaaaaa - Data set ’bbb(44)’ Keys option are a decimal number between 0 and
aaaaaaaa to data set ’ccc(44)’ 32768. Refer to the appropriate IDCAMS
documentation for specific information on these
Explanation: This is an informational message. options.
Programmer Response: None.
ISRU533 Enter a decimal value between 1 and
ISRU526 Data set aaaaaaaa - Data set ’bbb(44)’ 32768.
aaaaaaaa to data set ’ccc(56)’. Explanation: Valid values for Average Record Size are
Explanation: This is an informational message. a decimal number between 0 and 32768. Refer to the
appropriate IDCAMS documentation for specific
Programmer Response: None. information on these options.
ISRU563 Invalid string type - Data set list ISRU569 Volume not available - Volume ’aaaaaaaa’
EXCLUDE command does not process not mounted or not authorized for your
picture (P’...’), hex (X’...’), text (T’...’) or use.
char (C’...’) strings. Explanation: PDF received one of the following return
Explanation: The data set list EXCLUDE command codes while processing volume aaaaaaaa, indicating that
does not support all of the keywords supported by the the volume specified is not available for your use:
editor EXCLUDE command. The following are not v Return code 4 from the OBTAIN macro
supported: v SVC 99 return code 4 with one of the following error
v Picture strings (P’...’) codes: X'0214', X'0218', X'0220', X'0248', X'0498',
v Hex strings (X’...’) X'049C', or X'6704'.
v Text strings (T’...’)
v Character strings (C’...’) User Response: Verify 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 ISRU578 Copy failed - Copied failed for member
workstation file has been successfully aaaaaaaa. Members whose directory
saved. entries contain user TTRs cannot be
copied into a PDSE. Move/Copy
Explanation: Informational only. Workstation has been
completed for bbbbbbbb members.
saved.
Explanation: You attempted to copy a member that
contained user TTRs into a PDSE data set. PDSE’s do
ISRU571 Data Set Saved - Data set - ’aaaaaaaa’ -
not support user-supplied TTRS in the user data field
Saved.
of the directory entry.
Explanation: Informational only. The sequential data
set was saved.
ISRU579 Copy failed - Members whose directory
entries contain user TTRs cannot be
ISRU572 aaaaaaaa members bbbbbbbb - to data set copied into a PDSE.
cccccccc. One or more members was
Explanation: You attempted to copy a member that
passed to the Binder for processing but
contained user TTRs into a PDSE data set. PDSE’s do
was found not to be a load module
not support user-supplied TTRS in the user data field
(Binder message IEW2522S). These
of the directory entry.
members were successfully copied using
an alternate method.
ISRU580 IEBCOPY setup failed – The allocation
Explanation: ISPF passes all members of a record
of the IEBCOPY input data sets failed.
format U PDS data set to the Binder for processing as a
load module. If the Binder detects that the member is Explanation: The allocation of the specified input
not a load module, it issues message IEW2522S and libraries to separate DDNAMES needed for invocation
returns an error code of ’83000523’ to ISPF. ISPF will of IEBCOPY failed.
reprocess these members using a read-write loop and
User Response: Contact your system administrator for
the IEW2522S message should be ignored.
assistance.
System Programmer Response: Contact IBM service
ISRU573 Some entries not used - One or more
for assistance.
names in the specified personal list
could not be found. The data set list
was built using the entries that do ISRU581 IEBCOPY setup failed – The allocation
match existing data sets. of the IEBCOPY output data sets failed.
Explanation: One or more of the data sets specified in Explanation: The allocation of the specified output
the reference list passed to the DSLIST command do library to a separate DDNAMES needed for invocation
not exist and have therefore not been added to the data of IEBCOPY failed.
set list.
User Response: Contact your system administrator for
assistance.
ISRU574 Catalog error - Catalog/uncatalog
request via SVC 26 failed, return code = System Programmer Response: Contact IBM service
aaaaaaaa, reason code = bbbbbbbb, module for assistance.
id = cccccccc.
Explanation: The catalog search to process the ISRU582 aaaaaaaa members bbbbbbbb – to data set
requested data set failed. cccccccc..One or more members was
passed to the Binder for processing but
User Response: Refer to the appropriate DFP was found not to be a load module
documentation for an explanation of the error. (Binder message IEW2522S). These
members were successfully copied using
Programmer Response: None.
an alternate method.
Explanation: ISPF passes all members of a record
ISRU576 to aaaaaaaa
format U PDS data set to the Binder for processing as a
Explanation: This is an informational message written load module. If the Binder detects that the member is
to the ISPF log data set. not a load module, it issues an error code of ’83000523’
to ISPF. ISPF will reprocess these members using a
read-write loop and the IEW2522S message should be
ignored.
ISRU588 Copy failed – Copy failed for member | User Response: See you system programmer
aaaaaaaa.. Members whose directory
| Programmer Response: See your system programmer
entries contain user TTRs cannot be
copied into a PDSE. Move/Copy | System Programmer Response: Remove the ISPF
completed for bbbbbbbb members. | configuration table selection that disallows the use of a
| high level qualifier in ISPF option 3.4.
Explanation: You 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 | ISRU594 Catalog error - Errors were returned
of the directory entry. | from the search on one or more catalogs.
| Enter HELP for a list of catalog(s),
| return code(s), reason code(s), and
ISRU589 Copy failed – Members whose directory
| module id(s). See message IDC3009I to
entries contain user TTRs cannot be
| interpret these codes.
copied into a PDSE.
| Explanation: The catalog search to find the requested
Explanation: You attempted to copy a member that
| data set names failed for one or more catalogs.
contained user TTRs into a PDSE data set. PDSE’s do
not support user-supplied TTRs in the user data field | User Response: Refer to the appropriate DFP
of the directory entry. | documentation for an explanation of the error, in
| particular message IDC3009I.
ISRU590 File not replaced — Workstation file | Programmer Response: None.
’aaaaaaaa’ already exists and was not
replaced.
Explanation: A file transfer request was issued from
ISPF option 3.7.4 with the REPLACE option not
| ISRU595 Member name invalid - A qualifier in ISRV004 Invalid multivolume cmd - The data set
| parentheses may only be specified as a that this command has been issued
| GDG relative generation such as (0), against is a multivolume data set. The
| (-1), or (+1). command is invalid for multivolume
data sets that are displayed using a
| Explanation: The data set list search is for data set VTOC list.
| names only; member names are not included.
Explanation: The data set that this command has been
| User Response: Correct the DSname level by issued against is a multivolume data set. The command
| specifying a GDG relative generation or a valid is invalid for multivolume data sets that are displayed
| DSNAME level. using a VTOC list.
| Programmer Response: None. User Response: Remove the volume name from the
Volume Serial field and reissue the command.
ISRV000 Invalid combination - You have selected
Allocate Multiple Volumes. The
ISRV005 Invalid multivolume cmd - The data set
directory blocks field must be zero to
that this command has been issued
allocate a multivolume data set.
against is a multiple volume data set.
Multivolume data sets are sequential
The command is invalid for a
data sets.
multivolume data set using the volume
Explanation: The directory blocks field must be 0 to serial.
allocate a multivolume data set. Multivolume data sets
Explanation: The data set that this command has been
are sequential data sets.
issued against is a multivolume data set. The command
User Response: Either change the directory block field is invalid for multivolume data sets using the volume
to 0 or blank out the field to allocate multivolume data serial.
sets.
User Response: Remove the volume name from the
Volume Serial field and reissue the command.
ISRV001 Duplicate volumes - Duplicate volumes
have been entered for multivolume
ISRV006 Multivolume data set - The data set that
allocation. Correct or remove the
is being edited is a multivolume data
duplicate volume.
set. Edit does not support the input of a
Explanation: An attempt to allocate a multivolume volume in the Volume Serial field for
data set has been made using the volume name of a multivolume data sets.
volume that has been already entered.
Explanation: The data set that is being edited is a
User Response: Correct or remove the duplicate multivolume data set. Edit does not support the ability
volume name. to edit data on one volume of a multivolume data set.
User Response: Remove the volume name from the
ISRV002 More than 20 volumes - ISPF does not Volume Serial field when you are attempting to edit a
support multivolume data sets with multivolume data set.
more than 20 volumes. Information is
displayed about the first 20 volumes.
ISRV007 Volume ignored - The data set that is
Explanation: This is an informational message. The being viewed is a multivolume data set.
multivolume data set contains more than 20 volumes. The volume entered was ignored. All of
ISPF supports up to 20 volumes for a multivolume data the data set can be viewed, not just one
set. The information displayed is for the first 20 volume’s data. If you wish to see the
volumes. data on one volume only, use browse
instead of view.
ISRV003 Invalid multivolume cmd - The data set Explanation: For a multivolume data set, view always
that this command has been issued allocates all volumes even when a specific volume is
against is a multivolume data set. The specified. The data presented begins with volume one.
command is invalid for multivolume
data sets.
Explanation: This 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.
ISRV008 Volume ignored - This data set is an | ISRVI004 Invalid view length - The view length
SMS managed multivolume data set. | must be less than or equal to the record
The volume entered was ignored. You | length.
cannot allocate just one volume of an
SMS managed multivolume data set.
| Explanation: An invalid view length is specified for
The data displayed begins with volume
| the VIIF service.
one. | User Response: Contact the responsible programmer.
Explanation: For an SMS managed multivolume data | Programmer Response: Specifiy an view length less
set, you cannont allocate just one volume’s worth of | than or equal to the record length.
data. The whole data set is allocated and the display
begins with the data on volume one.
| ISRVI005 Conflicting options used - The view
| length and the format are mutually
| ISRVI000 View length not allowed - View length | exclusive.
| not allowed when processing View
| Recovery | Explanation: Conflicting options are specified for the
| VIIF service. The view length and the format cannot be
| Explanation: View length is specified for the VIIF | used simultaneously.
| service. This is not allowed when processing view
| recovery. | User Response: Contact the responsible programmer.
| User Response: Contact the responsible programmer. | Programmer Response: Blank out one of the
| conflicting options.
| Programmer Response: Blank out the view length
| from the EDIREC service.
| ISRVI006 Recovery is not pending - The view
| recovery cannot proceed when recovery
| ISRVI001 Missing record format - Specify the | is not pending.
| record format F or V for VIIF.
| Explanation: A view recovery is requested while
| Explanation: The required record format parameter | recovery is not pending
| for the VIIF service is not specified.
| User Response: Contact the responsible programmer.
| User Response: Contact the responsible programmer.
| Programmer Response: Correct the recovery-request
| Programmer Response: Specify either F or V for the | option for the VIIF service.
| record format parameter for the VIIF service.
| User Response: Contact the responsible programmer. | Programmer Response: Specify the view length with a
| value between 10 and 32760 for the VIIF service.
| Programmer Response: 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. | ISRVI008 aaaaaaaa name not allowed - aaaaaaaa
| name not allowed when processing
| View Recovery.
| ISRVI003 Missing profile name - Specify the
| profile name for VIIF. | Explanation: aaaaaaaa name is specified for the VIIF
| service. This is not allowed when processing View
| Explanation: The required profile name parameter for | Recovery.
| the VIIF service is not specified.
| User Response: Contact the responsible programmer.
| User Response: Contact the responsible programmer.
| Programmer Response: Blank out the aaaaaaaa name
| Programmer Response: Specify the profile name for | from the EDIREC service.
| the VIIF service.
| ISRVI009 Mixed mode not allowed - Mixed mode ISRZ003 aaaaaaaa - bbbbbbbb
| not allowed when processing View
Explanation: This is an informational message. This
| Recovery.
message may be used if an error is returned from a
| Explanation: Mixed mode is specified for the VIIF PDF dialog service. Variable &ZERRMSG will indicate
| service. This is not allowed when processing view the message id that is the source of the message text for
| recovery. ISRZ003.
| User Response: Contact the responsible programmer.
| Programmer Response: Blank out mixed mode from
| the EDIREC service.
FLMQ000 Data set unavailable — Data set aaaaaaaa FLMQ003 LMINIT error — Error for LMINIT of
could not be found or is not available data set aaaaaaaa .. LMINIT Return Code
for your use. Correct the data set name = bbbbbbbb.
and press Enter.
Explanation: An error occured on the ISPF LMINIT
Explanation: The data set entered on the SCLM service for the data set listed in the message.
Sample Project Create panel does not exist or is not
User Response: Consult the ISPF Services Guide for
available for your use. The data set may be enqueued
an explanation of the return code. Correct the problem
exclusively to another user or you may not have
and retry the operation.
authority to use the data set.
User Response: Correct the data set name or
FLMQ004 LMCOPY error — Error for LMCOPY of
determine why the data set is not available for your
member aaaaaaaa from data set bbbbbbbb.
use.
LMCOPY return code = cccccccc.
Explanation: An error occured on the ISPF LMCOPY
FLMQ001 Allocation error — Error allocating data
service for the data set and member listed in the
set aaaaaaaa. TSO messages should have
message.
been written to your screen, check the
setting of WTPMSG in your TSO User Response: Consult the ISPF Services Guide for
PROFILE. Names of data sets created for an explanation of the return code. Correct the problem
this project are in data set and retry the operation.
bbbbbbbb..PROJDEFS.DATASETS.
Explanation: An error occured creating a data set for FLMQ005 A fully qualified data set name enclosed
the sample SCLM project. TSO messages should have in quotes is required.
been written to the screen describing the error.
Explanation: You entered a data set name that is not
User Response: Correct the problem described in the fully qualified. The SCLM Sample Project Create
TSO messages. function requires all data set names except the High
Level Assembler Location be fully qualified and
enclosed in single quotes.
FLMQ002 Initialization error — Error initializing
VSAM file aaaaaaaa .. TSO messages User Response: Correct the data set name.
should have been written to your screen
describing the error. If TSO messages
were not written to your screen, check FLMQ006 A fully qualified data set name enclosed
the setting of WTPMSG in your TSO in quotes or LINKLIB without quotes is
PROFILE. required.
Explanation: An error occured initializing the VSAM Explanation: You entered a data set name that is not
data base file for the sample SCLM project. TSO fully qualified and is not LINKLIB without quotes. The
messages should have been written to the screen SCLM Sample Project Create function requires the data
describing the error. set name for the High Level Assembler Location be a
fully qualified data set name enclosed in quotes or the
User Response: Correct the problem described in the term LINKLIB.
TSO messages.
User Response: Correct the entry.
FLMQ007 Assembly error — Error assembling FLMQ011 PROMOTE failed — Error promoting
project definition the sample application from aaaaaaaa to
aaaaaaaa..PROJDEFS.SOURCE(aaaaaaaa) bbbbbbbb. Messages are in
with the ISPF Macros Data set and cccccccc.PROMOTE.MESSAGES. Listings
aaaaaaaa..PROJDEFS.SOURCE as are in cccccccc.PROMOTE.LISTINGS.
SYSLIB. The output is in bbbbbbbb. The PROMOTE report is in
cccccccc.PROMOTE.REPORT.
Explanation: Assembly of the project definition
resulted in a non-zero return code. Explanation: Promote of the sample application failed.
User Response: Attempt to assemble the project User Response: Correct the errors in the messages and
definition member using the ISPF Macros data set and listings data sets. Complete the sample project using
the project.PROJDEFS.SOURCE as SYSLIB. Use option the instructions in the SCLM Project Manager’s Guide,
4.1 or batch. Correct the ISPF Macros data set name if it Preparing the Example Project Data, by completing the
is incorrect. BUILD and PROMOTE steps. You may have to repeat
the BUILD step.
FLMQ008 Link error — Error linking project
definition FLMQ012 Project aaaaaaaa was successfully
aaaaaaaa..PROJDEFS.OBJ(aaaaaaaa) The deleted. All data sets for the project
output is in bbbbbbbb. were deleted.
Explanation: Link Edit of the project definition Explanation: Deletion of the sample project was
resulted in a non-zero return code. successful.
User Response: Attempt to link edit the project
definition member using the ISPF Macros data set and FLMQ013 Incomplete delete —Errors occurred
the project.PROJDEFS.OBJ to project.PROJDEFS.LOAD. deleting data sets for project aaaaaaaa.
Use option 4.7 or batch. Correct any errors you find. TSO messages should have been written
to your screen describing the errors. If
TSO messages were not written to your
FLMQ009 MIGRATE failed — Error migrating
screen, check the setting of WTPMSG in
members into project aaaaaaaa. Error
your TSO PROFILE.
messages are contained in
aaaaaaaa.MIGRATE.MESSAGES. Explanation: No explanation available at this time.
Explanation: The SCLM MIGRATE of members into
the project failed. FLMQ014 Project not deleted —You did not
confirm deletion of project aaaaaaaa.
User Response: Correct the errors described by the
Project aaaaaaaa was not deleted.
messages in project.FLMMSGS.
Explanation: No explanation available at this time.
FLMQ010 BUILD failed — Error building the
project aaaaaaaa. Messages are in FLMQ015 Project delete failed —Errors occurred
aaaaaaaa.BUILD.MESSAGES. Listings are allocating or reading the data set
in aaaaaaaa.BUILD.LISTINGS. The aaaaaaaa.PROJDEFS.DATASETS that
BUILD report is in contains the list of data sets for project
aaaaaaaa.BUILD.REPORT. aaaaaaaa. The project cannot be deleted
without this data set.
Explanation: Build of the sample project failed.
Explanation: Data set aaaaaaaa.PROJDEFS.DATASETS
User Response: Correct the errors in the messages and
contains the list of data sets for the project. It is
listings data sets. Complete the sample project using
required to delete the project.
the instructions in the SCLM Project Manager’s Guide,
Preparing the Example Project Data, by completing the User Response: Correct the project name or determine
BUILD and PROMOTE steps. why the required data set is not available.
FLM090C SCLM - Build - FLM090M Vol aaaaaaaa not found - Volume aaaaaaaa
aaaaaaaa..bbbbbbbb..cccccccc(dddddddd)- is not mounted or is not authorized for
RC=: your use.
Explanation: This is an informational message. Explanation: The volume could not be found or an
error occurred obtaining information about the volume.
User Response: For return codes greater than zero, see
the build messages. User Response: Request that the volume be mounted
if it is not. Otherwise, request the proper authorization.
FLM090D Volume should be blank - Leave
VOLUME blank for command SUB and FLM090N Vol aaaaaaaa not mounted - Volume
LISTINGS destination data set. aaaaaaaa is not mounted or is not
authorized for your use.
Explanation: Do not specify a volume name when
submitting a batch build in SCLM. SCLM uses the Explanation: The volume could not be found or an
default volume. error occurred obtaining information about the volume.
User Response: Blank out the volume name field. User Response: Request that the volume be mounted
if it is not. Otherwise, request the proper authorization.
FLM090F SCLM - Utility -
aaaaaaaa..bbbbbbbb..cccccccc(dddddddd) - Del FLM090P Data set kept - Data set aaaaaaaa
submitted for printing; data set kept.
Explanation: This is an informational message. SCLM
completed the request to delete member aaaaaaaa. Explanation: This is an informational message.
FLM090Q Job submission error - Job submission FLM090Y Enter option - Enter one of the listed
error. Invalid request. options.
Explanation: This is an informational message. Explanation: No option was selected.
User Response: Choose one of the options listed and
FLM090R Job submitted – SCLM submitted the press Enter.
job request to the specified output
control.
FLM090Z Invalid option - Enter one of the listed
Explanation: This is an informational message. options.
Explanation: An invalid option was selected.
FLM090S Promote completed – The return code
User Response: Choose one of the options listed and
from the Promote processor is aaaaaaaa..
press Enter.
Enter the HELP command for a
description of common errors.
FLM091 Arch report completed – The return code
Explanation: This is an informational message.
from the Architecture Report processor
is aaaaaaaa. Enter the HELP command for
FLM090T Build completed – The return code from a description of common errors.
the Build processor is aaaaaaaa.. Enter
Explanation: This is an informational message.
the HELP command for a description of
common errors.
FLM091B I/O error on Xref – An I/O error
Explanation: This is an informational message.
occurred while retrieving a
cross-reference record.
FLM090U Job queued - The job request is queued
Explanation: SCLM could not read a record from the
for later submission as a batch job.
VSAM cross-reference file.
Explanation: This is an informational message.
User Response: Contact your project administrator.
Project Manager Response: Isolate the failure using
FLM090V Invalid option - The option you entered
IDCAMS after making sure the cross-reference file
is invalid.
exists as defined for this project.
Explanation: An invalid option was specified on the
command line.
FLM091C Xref not found - Cannot find the
User Response: Enter a valid option. cross-reference record for selected
Compilation Unit.
FLM090W Invalid value - You cannot select Explanation: This is an informational message.
PRINTER for EXECUTE.
User Response: Save or migrate the member.
Explanation: You can only request output to be routed
to the printer if you submit the job to batch.
FLM091D Xref mismatch - Mismatch of
User Response: Either submit the job to batch, or xref/dependency information or
route the output to TERMINAL or data set. xref/code version.
Explanation: The member and dependency
FLM090X Invalid value - You cannot select information are out of synch.
TERMINAL for SUBMIT.
User Response: Parse the member and rebuild.
Explanation: You can only request output to be routed
to the terminal if you execute the job in foreground.
FLM091E Xref file missing - The project definition
User Response: Either route the output to PRINTER does not include a Cross-reference file.
or data set, or execute the job in foreground.
Explanation: The cross-reference file as specified by
the project definition does not exist, or the project does
not have a cross-reference file defined to it.
User Response: Contact your project administrator.
Project Manager Response: If the file does not exist,
Project Manager Response: Check all VSAM files Project Manager Response: A restriction of the
defined to the project using the IDCAMS utility. If an $list_info pointer parameter has been exceeded. See
alternate to the failing VSAM data set exists, use it. SCLM Services Guide for more information.
Otherwise, consider using a previous backup version.
FLM091N Parser not specified - Language
FLM091J Acct file I/O error - An I/O error definition does not include a parser or
occurred while writing to the accounting parser data set name.
file.
Explanation: Either SCLM could not locate the parser
Explanation: A failure occurred while writing to the as specified in the language definition, or a parser was
accounting VSAM file. not specified in the language definition.
User Response: Contact your project administrator. User Response: Contact your project administrator.
FLM092P Invalid member - Accounting FLM290A Invalid macro parameter – Invalid macro
information for member not found. parameter aaa(80)..
Explanation: SCLM could not find the accounting Explanation: An invalid parameter was specified for
record in the accounting VSAM file defined to this an edit macro. The long description contains the
project. parameter in error.
User Response: You can generate the accounting User Response: Correct the invalid parameter.
record for the member using the SCLM migrate utility,
or by editing the member and issuing the SPROF
FLM290B Parser error. Enter HELP for a detailed
command.
description of the error.
Explanation: The parse of the member that occurs
FLM092S Enter required field - Enter the data
while saving the member was not successful.
specified in the required field.
User Response: Enter HELP to display a panel with
Explanation: Enter a value for the field where the
any messages that were generated by the parser.
cursor is positioned.
System Action: The member data is saved to the PDS
User Response: Enter a valid value.
data set and an accounting record with LOCKOUT
state is saved, but accounting statistics and dependency
FLM092T Invalid promote to-group - Promote information that may have been returned by the parser
to-group must be a group in the project. are not saved.
Explanation: The promote service was invoked with Problem Determination: Refer to the parser messages
an invalid group name for the promote-to-group. to determine the actions to be taken to correct the
problem.
User Response: Correct the name of the
promote-to-group and reissue the command.
FLM290C Member in use – Either you or another
user is updating member aaaaaaaa..
FLM092V Enter required field - Enter a valid
member name which consists of Explanation: The member is currently being used in
alphanumeric characters. another operation. The member may be in use by:
v Another user
Explanation: An invalid member name was entered.
v The other section of a split screen
User Response: Enter a valid member name. v A recursive edit session.
User Response: The user’s action cannot be performed
FLM092W Member aaaaaaaa of bbbbbbbb - Member until the current operation using the member has been
aaaaaaaa of bbbbbbbb completed.
| User Response: For further information about the Explanation: An attempt was made to enter SCLM
| message, an SCLM message id appears at the View or Edit while an SCLM edit session was active.
| beginning of the message. The format of the message id User Response: Return to the current edit session and
| is FLMxxxxx, where xxxxx is a five digit number. The end the edit, or use the View or Edit primary
| message is described in ISPF Messages and Codes. commands. Alternatively, use split screen to perform
the intended operation.
FLM290 aaa(24) - bbb(512)
Explanation: An error occurred in a non-SCLM FLM290E Save warnings. aaaaaaaa has been stored.
service. The text of this message contains the message Enter HELP to display the warning
returned by the failing service. messages.
| User Response: Refer to the text of the message to Explanation: The member was saved but warning
| determine the cause of the failure. messages were generated while saving the member.
User Response: Enter HELP to display the warning
FLM290G Group warning - Group aaaaaaaa is not Explanation: The label specified for CREATE,
in the hierarchy view for group REPLACE, or MOVE was longer than 6 characters in
bbbbbbbb.. length. Edit labels must be 6 characters or fewer in
length.
Explanation: The hierarchy view for group bbbbbbbb is
the list of groups from bbbbbbbb to the top of the User Response: Enter the command specifying a valid
hierarchy as defined in the project definition. This edit label.
message is a warning that the group aaaaaaaa is not in
that list of groups. Specifying groups out of the FLM290L Invalid group – This project does NOT
hierarchy view may result in other error messages include group aaaaaaaa.
when you attempt to edit a particular member.
Explanation: The group, aaaaaaaa, specified by the user
User Response: Verify that the groups entered on the is not a group defined in the project definition.
edit panel are in the desired order.
User Response: Specify a group defined in the project
definition.
FLM290H aaaaaaaa saved - Member aaaaaaaa has
been parsed and stored by SCLM.
FLM290M Invalid library order - Groups not in
Explanation: This is an informational message. The hierarchical order. Enter HELP to
edit, parse, and store of member aaaaaaaa were all display group list.
completed successfully.
Explanation: A group higher in the hierarchy cannot
be specified before a group lower in the hierarchy on
FLM290I Invalid dev group - Group aaaaaaaa is the edit panel. At least one of the groups specified on
not the lowest group in the hierarchy. the edit panel is not in hierarchical order.
Explanation: The operation being requested may User Response: Specify the groups in hierarchical
result in the update of an SCLM-controlled member, order.
but the specified group is not a development group in
the project hierarchy. A development group is a group Problem Determination: Enter HELP to display up to
which has no other groups promoting into it. This 16 groups from the hierarchy in hierarchical order,
operation can only be performed on members that are beginning with the development group from the edit
in a development group. panel.
Explanation: The user requested to edit a member User Response: Enter a valid member name.
found in a group that was not specified on the edit
panel. This can occur if:
FLM290O Authorization code aaaaaaaa is invalid FLM290T Command conflict – You entered
for group bbbbbbbb. Enter HELP to incomplete or conflicting line
display an authorization code list. commands.
Explanation: Authorization code aaaaaaaa was not Explanation: The current edit line commands are
defined as a valid authorization code for group incomplete or conflicting. For example, an incomplete
bbbbbbbb in the project definition. The authorization line command might have the beginning of a block to
code was specified on the SCLM edit panel. be copied specified by ″CC″ but no end line specified.
An example of a conflicting edit line command is a
User Response: Either specify a valid authorization
block copy where the target of the copy is within the
code for the group, or leave the authorization code
block being copied.
field blank on the edit panel.
User Response: Ensure that the line commands in the
Problem Determination: Enter HELP to display a list
current edit session are complete and do not conflict.
of 30 valid authorization codes for group bbbbbbbb.
The RESET edit command can be used to reset the line
commands within the current edit session. Enter HELP
FLM290P NLS table error – An error occurred when this message is displayed to get more
while retrieving the NLS ID; code = aa. information on the edit line commands.
Explanation: The NLS ID could not be retrieved when System Action: The SCREATE, SMOVE, or
running a macro. The error codes are: SREPLACE operation is not performed.
User Response: Exit SCLM and PDF then retry the Explanation: If a pattern was specified on the panel,
operation. If the problem persists, contact the system then no members were found in the hierarchy of
programmer. groups from the panel that match the pattern. If no
pattern was specified, then no members were found in
Project Manager Response: Contact IBM support. any of the groups.
System Action: The macro is not run. User Response: To browse or edit an existing member,
ensure that the groups, type, and pattern will find the
FLM290Q Invalid parameter - Command format is desired member. To edit a new member in an empty
’SCREATE|SREPLACE member {label1 data set, specify the member name on the edit entry
label2}’. panel.
FLM290X Recovery failed - Edit recovery failed for FLM291B Invalid command - Command aaa(65) is
aaa(44)(bbbbbbbb). invalid.
Explanation: Edit recovery failed for member bbbbbbbb Explanation: The command aaa(65) is not a valid
in data set aaa(44). command.
User Response: Review the Edit Recovery User Response: Enter a valid change code or language
documentation for possible reasons that edit recovery and press Enter to update the language or change code
has failed. of the member. Enter CANCEL to cancel the update.
Enter a valid command on the command line to have
the command processed.
| FLM290Y You cannot use language aaaaaaaa for
| editable members.
FLM291C Command ignored - A RETURN or
Explanation: Language aaaaaaaa is not defined as
EXIT command was ignored in order to
editable in the project definition. Members that are
display the SCLM Edit Profile panel.
edited must be specified as editable in the project
definition. Explanation: SCLM must have the language for a
member in order to save it. The RETURN or EXIT
User Response: Specify a language that was defined
command was ignored in order to obtain the language
as editable in the project definition. Enter HELP to
for the member.
display a selectable list of editable languages from the
project definition. User Response: Enter a valid language for the project.
FLM290Z Invalid parameter - Command format is FLM291D This member cannot be promoted using
’SMOVE member {AFTER|BEFORE auth. code aaaaaaaa.
label}’.
Explanation: Authorization code aaaaaaaa is not
Explanation: An invalid parameter was specified on allowed for the next group in the hierarchy. This
an SMOVE macro command. member cannot be promoted using this hierarchy
unless the authorization code is changed.
User Response: Make sure that a member name was
specified. If AFTER or BEFORE was specified, then a User Response: If the member needs to be promoted
label must be specified and the label must have a ″.″ using this hierarchy, the authorization code needs to be
(period) as the first character. Enter HELP for more changed prior to promoting the member. The SCLM
information on the SMOVE macro command. library utility can be used to change the authorization
code.
FLM291 Allocation error - SCLM cannot allocate
the libraries you requested on the Edit FLM291E aaaaaaaa replaced - Member aaaaaaaa has
or View panel, or from the Edit service. been replaced, parsed, and stored by
SCLM.
Explanation: SCLM is unable to allocate or open the
data set(s) associated with the hierarchy specified on Explanation: This is an informational message.
the Edit or View panel. Member aaaaaaaa was replaced using the SREPLACE
macro command.
User Response: Check that the data sets are not
allocated exclusively to another user.
FLM291F aaaaaaaa moved - Member aaaaaaaa has
Project Manager Response: Ensure that the data sets
been moved and associated accounting
are properly allocated and that the users have sufficient
information deleted.
authority.
Explanation: This is an informational message.
Member aaaaaaaa was moved using the SMOVE macro
FLM291A Change code unavailable - No previous
command. The new member has been created and the
change code exists for this member.
old member deleted.
Explanation: Either the member did not previously
exist or the accounting information for the member
FLM291G aaaaaaaa created - Member aaaaaaaa has
does not contain any change codes.
been created, parsed, and stored by
User Response: Specify a change code instead of SCLM.
entering ″=″ to retrieve the previous change code.
Explanation: This is an informational message.
Member aaaaaaaa was created using the SCREATE
macro command.
FLM291M All groups unallocated - At least one User Response: Either specify an SCLM group name,
group must be allocated. or allocate the data set aaa(44).
FLM291N Group1 not cataloged - The data set for FLM291U Data loss warning - aaaaaaaa has been
the first group ’aaa(44)’ must be locked. Enter HELP to display the
cataloged. warning messages.
Explanation: Edit requires that the data set for the Explanation: The accounting and PDS data for the
first group in the hierarchy be allocated. The data set member being edited are not in sync.
name is aaa(44).
User Response: Enter HELP to display the panel with
User Response: Contact the project administrator to additional messages.
allocate the data set.
System Action: Edit continues.
Project Manager Response: Have the SCLM
FLM291V Group name is too long - The group FLM292B Invalid sort field - The sort field name
name must be fewer than or equal to 8 must match a heading on the panel.
characters.
Explanation: The field name specified on the sort
Explanation: The group name is longer than 8 command must match one of the field headings
characters. displayed on the panel.
User Response: Either specify a group name pattern User Response: Specify a valid field heading from the
(that may be longer than 8 characters), or specify a panel.
valid group name of 8 characters or fewer.
FLM292C Invalid language - The language you are
FLM291W Parameter required - A member name locating cannot be more than eight
must be specified after the LOCATE characters long.
command.
Explanation: The language parameter of the locate
Explanation: The member name parameter is required command must have eight or fewer characters.
for LOCATE commands.
User Response: Specify a valid language on the locate
User Response: Specify a complete or partial member parameter.
name on the LOCATE command.
FLM292D Enter a language - Enter a language to
FLM291X Invalid command - Command aaa(65) is locate.
invalid.
User Response: The locate command requires a
Explanation: The command aaa(65) is not a valid language parameter.
command.
Specify a valid language on the locate parameter.
User Response: Specify a valid command. Enter HELP
when this message is displayed for command
FLM292E Language not found - The language you
information.
are locating is not found.
Explanation: The language specified is not in the list
FLM291Y Invalid authcode - Commas are not
of valid languages.
allowed in authorization codes.
User Response: Verify that the language name was
Explanation: The authorization code specified contains
typed correctly. If not, retype the command with the
one or more commas. The authorization code is not
correct language. If so, see your project administrator.
valid.
User Response: Specify a valid authorization code.
FLM292F Invalid command - Valid commands are
Contact the project administrator to obtain valid
CANCEL, LOCATE, and END.
authorization codes, if necessary.
Explanation: The command is not valid.
FLM291Z Invalid change code - Commas are not User Response: Enter a valid command.
allowed in change codes.
Explanation: The change code specified contains one FLM292G Select a language - One and only one
or more commas. The change code is not valid. language can be assigned to a member.
User Response: Specify a change code that does not Explanation: More than one language was selected
contain commas. from the list.
User Response: Delete all but one S from the selection
FLM292A Invalid data set name - Member names field.
are not allowed for retrieval data sets.
Explanation: Member names are not allowed for FLM292H No languages - There are no languages
non-SCLM controlled retrieval data sets. defined in the project. See your project
administrator.
User Response: Enter either a sequential data set
name or a partitioned data set name without a member Explanation: SCLM must have the languages defined
name. for a project in order to save members.
User Response: See your project administrator.
Programmer Response: Add a language definition for
User Response: Start a session with a workstation Explanation: The selection entered is invalid. The only
before performing this action. valid selection is S.
User Response: Enter an S in the Select field for each
FLM390B Invalid selection - Use A, B, C, D, E, M, compilation unit that you want to review.
U, or V.
Explanation: The selection entered is not a valid FLM390M Unable to review - Data set aaaaaaaa is
Library Utility command. in use by another logical screen.
User Response: Choose one of the selections listed, or Explanation: The build map contents for the requested
enter the HELP command for further information. member are currently in use by another logical screen.
User Response: Exit the build map contents on the
FLM390C View error - SCLM is unable to view other logical screen.
requested member aaaaaaaa..
Explanation: An error occurred in attempting to view FLM390N Allocation failed - Data set aaaaaaaa
the member. This message may be issued for any of the already exists.
following reasons: Explanation: SCLM is attempting to create a
v A zero-length member of a partitioned data set was temporary data set to hold the build map contents. A
found. data set with that name already exists. SCLM was
v A specified member was not found. unable to delete the existing data set.
v No members matched the specified pattern, or no
members exist in the partitioned data set. User Response: Delete the existing copy of the
v Severe error; unable to continue. specified data set.
Project Manager Response: Contact IBM support. Explanation: SCLM has already deleted the version
and the audit information you selected.
User Response: Make another selection.
FLM391G Build map list I/O error - A severe I/O FLM391L Records not found - SCLM cannot find
error occurred while retrieving build any records at group aaaaaaaa..
map list.
Explanation: No records were found at the specified
Explanation: This message can be issued for any of group.
the following reasons:
User Response: Specify another group.
v The map information could not be decoded and is in
an invalid format.
v An invalid group was specified. FLM391M Records not found - SCLM cannot find
v A severe error occurred in accessing the VSAM any records for compilation unit
database. qualifier aaaaaaaa..
User Response: Exit SCLM and PDF then retry the Explanation: No records were found for the specified
operation. If the problem persists, contact the project CU Qualifier.
administrator.
User Response: Specify another Compilation Unit
Project Manager Response: Verify that the VSAM Qualifier.
database is operational and has not been corrupted.
User Response: Specify another member name. Exit Explanation: The group field was left blank. At least
and reenter the member list in order to display a more one group must be specified.
current list of members. User Response: Enter a valid group in the group field.
Explanation: This is an informational message. User Response: Specify ″/″ for hierarchy view on the
Library Utility panel.
User Response: Possible return codes are: Explanation: A VSAM error occurred while
attempting to purge accounting information for
4 An I/O error occurred while writing the member dddddddd.
member’s accounting information to the
secondary accounting data set. Because the User Response: Possible return codes are:
primary accounting data set was correctly 4 The member’s accounting record was not
updated, SCLM will use the correct found. The accounting record would have
information for all references. However, the been deleted anyway, so no action is required.
two accounting data sets are no longer However, to determine why the accounting
identical. Contact the project administrator. record was not found, view the audit record if
4 The member’s accounting record was not Explanation: The VERIFY translator indicates that the
found. The accounting record would have accounting information for the member must be
been deleted anyway, so no action is required. updated, but the member has not been drawn down to
To determine why the accounting record was the group at which the build or promote was invoked.
Explanation: An I/O error occurred while attempting 24 Define the cross-reference data set on the
to retrieve accounting information for the dependent FLMCNTRL macro of the project definition.
compilation unit aaa(55) bbb(55). More information on the FLMCNTRL Macro
can be found in ISPF Software Configuration and
User Response: Submit the job again. If the problem Library Manager (SCLM) Referenc
recurs, contact the project administrator.
Project Manager Response: Run IDCAMS against the FLM03502 ERROR UPDATING ACCOUNTING
cross-reference data set to determine the problem. INFORMATION FOR INTERMEDIATE
FORM OF
FLM03501 ERROR RETRIEVING ACCOUNTING
INFORMATION FOR INTERMEDIATE CU NAME: aaa(55) bbb(55)
FORM OF CU TYPE: cccc
CU QUALIFIER: dddddddd
CU NAME: aaa.(55) bbb.(55) CODE: eee.
CU TYPE: ccc. STARTING WITH GROUP: ffffffff
CU QUALIFIER: dddddddd TYPE: gggggggg MEMBER: hhhhhhhh
CODE: eee Explanation: An error occurred while attempting to
STARTING WITH GROUP: ffffffff update accounting information for the specified
TYPE: gggggggg MEMBER: hhhhhhhh intermediate form.
12 Verify that the cross-reference data set is User Response: Possible return codes are:
compatible with the current release of SCLM.
8 The accounting information for the
20 Run IDCAMS against the cross-reference data intermediate form of the compilation unit was
set to determine the problem. not found in the specified group. This means
that the compiled intermediate form is missing
24 Define the cross-reference data set on the or is out of date. The member containing the
FLMCNTRL macro of the project definition. compilation unit needs to be rebuilt.
More information on the FLMCNTRL Macro
can be found in ISPF Software Configuration and 12 SCLM internal error. Contact the project
Library Manager (SCLM) Referenc administrator.
20 An I/O error occurred while retrieving the
FLM03503 ERROR PURGING ACCOUNTING accounting information for the intermediate
INFORMATION FOR INTERMEDIATE form of the compilation unit. Contact the
FORM OF project administrator.
24 The cross-reference data set was not defined in
CU NAME: aaa(55) bbb(55) the project definition. Contact the project
CU TYPE: cccc administrator.
CU QUALIFIER: dddddddd CODE: eee
GROUP: ffffffff TYPE: gggggggg Project Manager Response: If the return code is:
MEMBER: hhhhhhhh
12 SCLM internal error. Report this message
Explanation: An error occurred while attempting to (including the message ID and all text fields)
purge accounting information for intermediate form to IBM support.
aaa(55) bbb(55).
16 Correct and reassemble the project definition.
User Response: Possible return codes are: Submit the job again, and verify that no errors
occurred.
8 An I/O error occurred while purging. Submit
the job again and if the error recurs, contact 20 Run IDCAMS against the accounting data set
the project administrator. to determine the problem.
16 Target data set enqueued. Submit the job again 24 Define the cross-reference data set on the
after the data set is no longer exclusively in FLMCNTRL macro of the project definition.
use by another job. More information on the FLMCNTRL Macro
can be found in ISPF Software Configuration and
24 The cross-reference data set was not defined in Library Manager (SCLM) Referenc
the project definition. Contact the project
administrator.
FLM03505 ERROR PURGING INTERMEDIATE
Project Manager Response: If the return code is: FORM OF
8 Run IDCAMS against the cross-reference data
set to determine the problem. CU NAME: aaa(55) bbb(55)
CU TYPE: cccc
24 Define the cross-reference data set on the CU QUALIFIER: dddddddd
FLMCNTRL macro of the project definition. CODE: eee
More information on the FLMCNTRL Macro GROUP: ffffffff TYPE: gggggggg
can be found in ISPF Software Configuration and MEMBER: hhhhhhhh
Library Manager (SCLM) Referenc
Explanation: The specified group is not valid for the User Response: Verify that the language of the
function requested and must be defined to SCLM as a member is defined in the project definition. If it is not,
development group. Contact the project manager for a specify a valid language and submit the job again.
list of valid groups. Contact the project manager for a list of valid
languages.
User Response: Select a group that is defined in the
project definition as a development group. Project Manager Response: Check the project
definition for valid language names.
Explanation: Member cccccccc has already been 12 Determine if group bbbbbbbb has been
updated in another hierarchy. The changes reside in incorrectly specified as input. Determine if
error group dddddddd, which is not in your hierarchy. group bbbbbbbb is not defined in the project
You cannot update the member because you would not definition (see the project manager).
be working with the most current version of the 16 No data sets have been physically allocated in
member. the hierarchy for type aaaaaaaa starting at
User Response: Have the member promoted into a group bbbbbbbb Determine if data sets should
group that is in your hierarchy (that is, one that be allocated, and allocate them if necessary.
appears on the SCLM Edit - Entry panel). If the See the project manager for assistance.
member cannot be promoted, the member and its 20 An error occurred during an attempt to
accounting information must be deleted in error group dynamically allocate a data set in the
dddddddd using the SCLM library utility or the DELETE hierarchical view to a ddname. Verify that data
service. You can also change the authorization code to sets in the hierarchical view are not allocated
restrict promotion. exclusively to another job, and resubmit the
job again.
FLM05020 ERROR ALLOCATING HIERARCHY Project Manager Response: Allocate the necessary
VIEW FOR TYPE: aaaaaaaa FROM data sets.
GROUP: bbbbbbbb CODE: ccc
Explanation: An error occurred during an attempt to FLM06501 TRANSLATOR RETURN CODE FROM
allocate all data sets that compose the hierarchical view ===> aaa(16) ===> bbb
for the current SCLM function. The hierarchical view is
for type aaaaaaaa, and begins with the corresponding Explanation: This message identifies the return code
data set at group bbbbbbbb received from translator aaaaaaaaaaaaaaaa. If the return
code indicates success as defined on the FLMTRNSL
Possible return codes are: macro, all output is saved in the hierarchy and no
4 A certain number of groups in the group response is necessary. If the return code from the
hierarchy was requested for allocation. The translator did not meet the GOODRC specified for the
number of requested groups exceeds the translator, SCLM saves translator output, such as
number of available groups in the hierarchy compiler listings, in the listings data set for the
starting with group bbbbbbbb. processor if requested in the language definition.
8 Type aaaaaaaa is not defined for the project. User Response: Use the listings data set to locate and
correct all errors identified by the translator. If the
translator is supplied with SCLM, check the return
Project Manager Response: Verify that the parameters Explanation: SCLM could not invoke the user exit.
of the FLMTRNSL macro, which are defined in the The load module containing the user exit might be
project definition, are correct. More information on allocated exclusively to another job. There is a possible
the.FLMTRNSL macro can be found in ISPF Software error in the project definition that defines the user exit.
Configuration and Library Manager (SCLM) Referenc User Response: If the user exit has been used
successfully in the past, submit the job again. If the
FLM06503 PROBABLE SYSTEM/USER ABEND user exit is new or the problem recurs, contact the
FOR TRANSLATOR: aaaaaaaa project administrator.
HEXADECIMAL VALUE OF RETURN Project Manager Response: Verify that the user exit
CODE: bbbbbbbb executes correctly outside of SCLM. Verify that the user
Explanation: SCLM issues this message when an exit is defined correctly in the project definition. For
abend occurs for translator aaaaaaaa. To determine the more information on user exits, see ISPF Software
cause of the abend, look up the return code in the Configuration and Library Manager (SCLM) Project
MVS/Extended Architecture Message Library: System Codes Manager’s Guide
manual.
User Response: Use the information provided in this FLM06512 VERIFICATION ERROR FROM USER
message to correct the cause of the abend, and submit EXIT ROUTINE: aaa(16), CODE: bbb
the job again. Explanation: The return code from user exit aaa(16)
did not meet the acceptable criteria specified for the
FLM06504 NO TRANSLATORS DEFINED FOR user exit. The output produced depends on the user
SCLM EXECUTION LANGUAGE: exit routine.
aaaaaaaa. User Response: Review the local software
Explanation: The translators defined for the language configuration management for information about the
definition do not contain any translators defined for user exit.
SCLM. If any translators are defined, they are defined Project Manager Response: For more information on
for use in external libraries. user exits, see ISPF Software Configuration and Library
User Response: Execute the function against Manager (SCLM) Project Manager’s Guide
languages defined with translators for SCLM execution.
24 A member of a PDS was requested but the If the return code is 38656, check to see if the
data set is not partitioned. FLMALLOC statement specifies
DSNTYPE=LIBRARY. If so, and your system
28 The requested member could not be found. or project is requesting that temporary data
32 The requested member was not available. sets be allocated to VIO, then try adding
CATLG=Y to the FLMALLOC statement.
36 The unit was not specified..
>64 SVC 99 error, reason code (decimal). FLM07012 ERROR SAVING MEMBER aaaaaaaa TO
528 Requested data set unavailable. The GROUP: bbbbbbbb TYPE: cccccccc, DATA
data set is allocated to another job SET NAME: ddd(44) CODE: eee
and its usage attributes conflict with Explanation: An error occurred during an attempt to
this request. copy member aaaaaaaa to data set ddd(44). This message
1040 Specify ddname unavailable. can be preceded by an MVS system error message.
Common errors are:
1156 Not enough space on any available
pack. Decrease the value specified for D37 Primary space is full and secondary space is
the RECNUM parameter on the not requested for for data set ddd(44)
FLMALLOC macro and try again. B37 or E37
5896 Data set does not exist. If a user The directory is full, or the maximum number
supplied data set naming convention of extents (123) was exceeded, or the volume
is used, try replacing the data set and VTOC of data set ddd(44) are full and
name for the FLMCPYLB macro with secondary volumes are not available.
variable @@FLMDSN. SVC99 error
38656 A data set could not be allocated. RECFM of target data set not the same as
Contact the project manager. RECFM as of source data set.
If you receive a return code of 8, 32, or >64, you should Possible return codes:
try the operation again. If the problem recurs or you
receive any other return codes, contact the project 12 A ddname is not allocated properly. A PDS
manager. was allocated without a member name, a
sequential data set was allocated with a
Project Manager Response: If the return code is : member name, or some other allocation error
8 Retry the operation. If the same problem occurred.
occurs, contact IBM support.
12 SCLM internal error. Contact IBM support. 16 The output data set is full.
20 RACF failed or the input member was not
Note: For the next set of codes, you should know that found.
the data set number corresponds to an
FLMALLOC macro associated with the specified 24 An input parameter was not valid.
translator (the first FLMALLOC is data set 1, the 28 A member entry could not be created because
second is data set 2 and so on). the input member is an alias or has TTR notes.
16 Check FLMALLOC to ensure that the data set
name has been specified correctly. 32 Open failed or TSOLNK failed.
20 Check FLMALLOC to ensure that all data set
User Response: Check the MVS system error
attributes have been specified correctly.
messages for detailed information. Refer to MVS/XA
24 Check FLMALLOC to ensure that a sequential
Message Library: System Messages for a description of the
data set was not specified when a partitioned
MVS error messages and the problem resolutions. If
data set was expected.
this message was not preceded by an abend code,
28 Check FLMALLOC to ensure that the correct
verify that the language definition in use does not
member name was specified.
Explanation: An error occurred while copying an User Response: Verify the data sets are allocated,
SCLM member to the versioning data set. The member cataloged, and accessible to SCLM; otherwise, contact
was not versioned. the project manager.
Possible codes for aaa are: Project Manager Response: Allocate, catalog, or make
the data sets accessible to SCLM.
8 The LRECL, DSORG, or RECFM of the version
PDS is invalid, a member within the version
PDS is corrupt or a temporary version data set FLM09002 THE REPORT WILL APPEAR IN aaa(26)
could not be allocated. See message FLM39203, Explanation: Data set aaa(26) will contain the report
FLM39222, or FLM39225. output. This message is provided for information only.
FLM20002 THE VERSION OF THE MEMBER YOU FLM32102 INVALID MIGRATE MODE: X
ARE EDITING DOES NOT HAVE AN SPECIFIED. VALID VALUES ARE C
ACCOUNTING RECORD AT THE (CONDITIONAL), U
HIERARCHY LEVEL IN WHICH IT (UNCONDITIONAL), OR F (FORCED).
WAS FOUND. ANOTHER VERSION
Explanation: The Migrate mode parameter on the
EXISTS IN THE SCLM CONTROLLED
FLMCMD service is not valid.
HIERARCHY.
User Response: Verify that the proper number of
Explanation: The member that you selected to edit
parameters have been specified. Use one of the
exists in the hierarchy in two different places. The
following values, and try again.
group at which the text of the member was found is
C Conditional (default)
not the same as the group at which the first occurrence
U Unconditional
of the accounting record was found. The version you
F Forced
are editing might be out of date. Someone might have
copied a version of this member into a group in the
hierarchy without doing a MIGRATE or a SAVE. FLM32201 UNABLE TO READ DIRECTORY FOR
DATA SET NAME: aaa(44) GROUP:
User Response: Verify that this is the correct version
bbbbbbbb TYPE: cccccccc CODE: ddd
of the member that you wish to edit. If not, cancel from
the current edit session, and use the Library Utility to Explanation: An error occurred while attempting to
delete the back-level version; then edit the member read the directory of the data set aaa(44).
again. You should not promote the member without
first checking to see whether the two versions need to Possible return codes are:
be manually merged to prevent loss of data. 16 SCLM is unable to open the data set
Project Manager Response: Check the project 20 An internal error occurred while attempting to
definition FLMALTC parameters. It is possible that you read the data set directory.
have two groups using the same data set to store
members, and accounting information. This could lead User Response: Verify that the data set directory can
to data integrity problems. Either change the promote be accessed by using the SCLM editor to browse the
path for one of the groups so that they cannot affect data set. If you cannot browse the data set, correct the
each other, or change the dsname specified on the problem and resubmit the job. Possible problems are
FLMALTC macro for one of the groups. that the data set is enqueued or the data set does not
contain a valid directory.
User Response: Verify that the user-supplied ddname | Explanation: The time must be in the National
for the migration messages is allocated. Resubmit the | Language format.
job. | User Response: Correct the time parameter on the
| Migrate service and run the service again.
FLM32320 USER DEFINED DDNAME: aaaaaaaa
FOR MIGRATION LISTING IS NOT | FLM32630 USER DEFINED DDNAME: aaa FOR
ALLOCATED | MIGRATE REPORT NOT ALLOCATED
Explanation: The ddname specified for the migration | Explanation: The report ddname of the Migrate
listing was not allocated. If the migration function is | service must be allocated before executing the Migrate
invoked through the services, the ddname for the | service. The ddname can be left blank to allocate the
migration listing is optional. If not specified, the | ddname to the default output device (such as the
migration listing is defaulted to the terminal. If a | terminal).
ddname is specified it must be allocated.
| User Response: Either allocate the data set before
User Response: Verify that the user-supplied ddname | invoking the Migrate service or set the ddname
for migration listing is allocated. Resubmit the job. | parameter to blank.
User Response: See the accompanying messages that | Explanation: The time parameter was requested, but
appear with this message on your screen for additional | the date parameter was not.
information regarding the status of this report. | User Response: To migrate with a date and time, add
| the date parameter to the service call. To migrate
Explanation: The member dddddddd does not exist in 4 Error freeing data set
the version gggggggggg data set. Code aaa will always 8 Error freeing DCB attributes list or getting
be 8. directory block information
User Response: Contact the project manager. 12 Could not obtain DCB attributes
Project Manager Response: Verify that the Version 16 Data set not found
PDS file has not been restored independently. The
Version VSAM file and the Version PDS file must stay 20 Severe internal error.
in sync at all times. If the Version PDS has not been
User Response: Verify that data set exists and is
restored or altered through manual manipulation, then
cataloged.
the file has been corrupted. Data has been lost.
Explanation: The first record of the version data is not 528 Requested data set unavailable. The
a header record. data set is allocated to another job
and its usage attributes conflict with
User Response: Contact your project manager. this request.
Project Manager Response: The version data has been 5896 Data set does not exist.
altered. Ensure that other version data sets are
protected by some data set security product. User Response: This message indicates that an error
occurred while allocating a data set to be used by a
translator.
FLM39220 ERROR in SUPERCU. CODE: aaa
If you receive a return code of 8, 32, or >64, you should
Explanation: An error was received from SUPERCU. try the operation again. If the problem recurs or you
Possible values for CODE, aaa, are: receive any other return codes, call the project manager.
16 Error on temporary input data set Project Manager Response: Verify that the Version
24 Error on temporary output data set VSAM file or the version PDS has not been restored
independently. They MUST stay in sync at all times. If
| 28 The requested member could not be found. Explanation: No translator was invoked for language
aaaaaaaa.
| 32 The requested data set could not be opened.
User Response: If a translation was expected, contact
| 36 Unit not specified. the project manager.
| >64 SVC 99 error, reason code (decimal): Project Manager Response: Examine the language
| 528 Requested data set unavailable. The definition to verify that a translation was expected for
| data set is allocated to another job language aaaaaaaa. If the language contains translators,
| and its usage attributes conflict with verify that at least one translator specifies the
| this request. FUNCTN=BUILD parameter on the FLMTRNSL macro.
20 Invalid file attribute specified. 12 SCLM internal error. Report this message
(including the message ID and all text fields)
24 A member of a PDS was requested but the to IBM support.
data set is not partitioned.
16 Missing or incorrect data set name.
28 The requested member could not be found.
20 Invalid file attribute specified.
32 The requested member was not available.
24 A member of a PDS was requested but the
>64 SVC 99 error, reason code (decimal). data set is not partitioned.
528 Requested data set unavailable. The 28 The requested member could not be found.
data set is allocated to another job
and its usage attributes conflict with 32 The requested member was not available.
this request.
>64 SVC 99 error, reason code (decimal).
5896 Data set does not exist.
528 Requested data set unavailable. The
User Response: This message indicates that an error data set is allocated to another job
occurred while allocating a data set to be used by a and its usage attributes conflict with
translator. this request.
If you receive a return code of 8, 32, or >64, you should 5896 Data set does not exist.
try the operation again. If the problem recurs or you
User Response: Contact the project administrator.
receive any other return codes, call the project manager.
Project Manager Response: Verify that data set aaa(44)
Project Manager Response: If the return code is :
exists and is cataloged.
8 Retry the operation. If the same problem
occurs, contact IBM support. for advice.
12 SCLM internal error. Contact IBM support. FLM40516 MEMBER: aaaaaaaa TYPE: bbbbbbbb WAS
UPDATED DURING THE BUILD
Note: For the next set of codes, you should know that
Explanation: The SCLM editor updated member
the data set number corresponds to an
aaaaaaaa during build processing. SCLM does not save
FLMALLOC macro associated with the specified
translator output because it might have been created
translator (the first FLMALLOC is data set 1, the
from the previous version of the member.
second is data set 2 and so on).
16 Check FLMALLOC to ensure that the data set User Response: Submit the job again.
name has been specified correctly.
20 Check FLMALLOC to ensure that all data set
FLM40517 DUPLICATE KEYREF=aaaaaaaa NOT
attributes have been specified correctly.
ALLOWED FOR TRANSLATOR
24 Check FLMALLOC to ensure that a sequential
OUTPUTS
data set was not specified when a partitioned
data set was expected. Explanation: The translator invoked has two
28 Check FLMALLOC to ensure that the correct temporary output data sets, allocated with either
member name was specified. IOTYPE=O or P, both targeted to the same output
32 See return code 8 for information. member (with the KEYREF parameter). The build
>64 An error was received from SVC 99 during the processor cannot copy multiple output data sets
allocation. The SVC 99 return code is specified produced by the translator to a single targeted member.
in the message (ddd). Reference OS/390 System
Codes, GC281780 , for a description of the SVC User Response: See the project administrator.
99 return codes. Project Manager Response: Verify in the language
definition that no two FLMALLOC macro calls with
either IOTYPE=O or P have the same KEYREF value
for a single translator. Also verify in the language
FLM42000 BUILD PROCESSOR INITIATED - User Response: Verify that the user-supplied ddname
aaaaaaaa ON bbbbbbbb for build report is allocated. Submit the job again.
20 A severe VSAM I/O error occurred. 8 Register both the specified member and the
referencing source member with SCLM using
24 An internal SCLM error occurred. the &sclm editor, SAVE service, or migration
utility. Submit the job again.
28 The type is not defined by the project
definition being used. If member dddddddd was excluded based on
change code, update the change codes
Possible problems: specified so that the required member will be
included in the build.
User Response: Verify that the member exists and that User Response: See the message data set for all the
the data set is not allocated exclusively to another job. messages related to this error.
Explanation: The architecture member aaaaaaaa in type This error can be caused when you delete a source
bbbbbbbb is involved in a recursive copy loop. Message member (using the library utility) but forget to delete
FLM43005 will be issued for all members involved in the intermediate forms produced by the compiler for
the loop. those compilation units contained in the deleted source
member.
User Response: Remove one or more of the COPY
statements in the listed architecture members to User Response: Delete the intermediate form from all
eliminate the recursive copy loop. groups in the hierarchy used in the build, then
resubmit the build.
FLM44050 ERROR, TYPE: aaaaaaaa MEMBER: is incorrect because SINCX is not a valid architecture
bbbbbbbb EXCEEDS MAXIMUM INPUT definition statement.
LINES VALUE: ccc, CURRENT SINC VERYLONGNAME SOURCE
STATEMENT COUNT: ddd
is invalid because the member name is longer than 8
Explanation: This message identifies that a single
characters.
member exceeds the SLOCLMT value specified in the
FLMLANGL macro. This member cannot be placed on
Correct the contents of the architecture member, and
any Input List for this language.
submit the job again.
User Response: Modify the contents of the specified
User Response: Correct the invalid architecture
member to place it within the limits of the SLOCLMT
statement.
or contact the project manager.
Project Manager Response: Modify the SLOCLMT
FLM44202 ARCHITECTURE MEMBER: aaaaaaaa
value of the FLMLANGL macro in the project
TYPE: bbbbbbbb ALL CCODE
definition.
STATEMENTS MUST CONTAIN THE
SAME INCLUDE FLAG VALUE
Explanation: Member aaaaaaaa in type bbbbbbbb
contains CCODE statements with conflicting include
flag values. All of the change codes specified within an
Explanation: No accounting information exists or User Response: Change the language of member
could be retrieved for the specified member within the aaaaaaaa if appropriate. Add a new member with the
hierarchy beginning in group bbbbbbbb. The member in compilation units contained in member aaaaaaaa at
question is a compool reference where type is defined group dddddddd. Remove the references to the
either by the CREF keyword in an architecture member compilation units in member aaaaaaaa at group
or the DFLTCRF parameter (FLMLANGL macro) in the dddddddd.
language definition.
User Response: Possible return codes are: FLM44311 ERROR PROCESSING COMPILATION
UNITS FOR MEMBER: aaaaaaaa TYPE:
8 The member’s accounting information was not bbbbbbbb
found. Build the member that creates the
specified compool. Explanation: An error occurred during processing of
the compilation units for the specified member. Other
12 The format of the member’s accounting messages are generated that describe the exact errors
information was incorrect. Delete the that occurred.
accounting information for the specified
compool and build the member that creates User Response: See the message data set for all the
the compool to regenerate the accounting messages related to this error.
information.
Project Manager Response: If the return code is: FLM44315 PURGE ROUTINE FOR
INTERMEDIATE FORM IS BEING
16 Verify that the specified group is in the project INVOKED
definition. If not, add it. Correct and
reassemble the project definition. CU NAME: aaa.(55) bbb.(55) CU TYPE:
20 A VSAM error occurred. Run IDCAMS against cccc CU QUALIFIER: dddddddd
the accounting data set to determine the OLD RECORD - TYPE: eeeeeeee
problem. MEMBER: ffffffff LANG: gggggggg
NEW RECORD - TYPE: hhhhhhhh
MEMBER: iiiiiiii LANG: jjjjjjjj
CODE: aaaa User Response: Restart the specified build, and SCLM
will continue the build process where it left off.
Explanation: The purge of the intermediate form was
not successful.
FLM44324 ERROR PROCESSING DYNAMIC
User Response: Submit the job again. If the error INCLUDE GROUP: aaaaaaaa
recurs, contact the project administrator. TYPE:bbbbbbbb MEMBER:cccccccc.
Project Manager Response: Verify that the sublibrary Explanation: A build translator returned member
containing the intermediate form is not corrupted. cccccccc in type bbbbbbbb as a dynamic include
dependency for the member being built. This member
FLM44320 ERROR, ACCOUNTING RECORD could not be found in the project hierarchy when
DATA CHANGED DURING CURRENT searching up the hierarchy from the group aaaaaaaa.
BUILD FOR TYPE: aaaaaaaa MEMBER: User Response: Determine if a statement in the source
bbbbbbbb is causing the include dependency to be generated. If it
Explanation: During the course of the build a user is and the statement is incorrect then update the
modified the source for member aaaaaaaa and type statement. If all of the source statements are correct
bbbbbbbb outside of SCLM. The SCLM accounting then contact the project manager.
information did not match the new member. Project Manager Response: Check the build translator
User Response: Use the SCLM editor to create valid which is returning the list of dynamic includes to
accounting information and restart the specified build. ensure that it only returns include names for members
SCLM will continue where it left off. which exist in the hierarchy. Dynamic includes can be
returned by build translators with @@FLMINC in the
translator’s options.
FLM44321 ERROR, NEW UPWARD
DEPENDENCIES FOUND THAT ARE
NOT IN THE CURRENT BUILD FOR FLM44500 >> INVOKING aaaaaaaa
TYPE: aaaaaaaa MEMBER: bbbbbbbb TRANSLATOR(S) FOR TYPE: bbbbbbbb
MEMBER: cccccccc
Explanation: A user has modified member bbbbbbbb
during the build process. SCLM has attempted to allow Explanation: The aaaaaaaa translators (where aaaaaaaa
the build to continue, but has identified new can be BUILD, COPY, PARSE, PURGE, or VERIFY) are
dependencies that are outside the scope of the current being invoked for member cccccccc. This member can
build. be either a source member or an architecture member.
This message is provided for information only.
User Response: Restart the specified build, and SCLM
will continue the build process where it left off.
FLM44501 REPORT: INVOKING aaaaaaaa
TRANSLATOR(S) FOR TYPE: bbbbbbbb
FLM44322 WARNING, TYPE: aaaaaaaa MEMBER: MEMBER: cccccccc
bbbbbbbb WAS MODIFIED DURING
THE CURRENT BUILD Explanation: The translators aaaaaaaa would be
invoked for member cccccccc if the build mode were not
Explanation: The user has modified member bbbbbbbb report-only.
during the build. However, the user modification did
not affect the current build process. This message is
provided for information only. FLM44502 >> INVOKING aaaaaaaa
TRANSLATOR(S) FOR INPUT LIST
LANGUAGE: bbbbbbbb.
Explanation: Translators are being invoked for input
list language bbbbbbbb. The members of the input list
will be specified by further messages. This message is
provided for information only.
FLM44510 >> DELETING OUTPUT(S) FOR TYPE: FLM44520 >> DELETING OBSOLETE OUTPUT(S)
aaaaaaaa MEMBER: bbbbbbbb
Explanation: SCLM has detected output from a
Explanation: The output member bbbbbbbb in type previous build that is out of date. The version of the
aaaaaaaa at the specified build group has been deleted. output that exists at a higher group in your hierarchical
view is up to date. Deleting the output is being
performed rather than regenerating the output to save
FLM44511 REPORT: DELETING OUTPUT(S) FOR
time and space. Only output found at the build group
TYPE: aaaaaaaa MEMBER: bbbbbbbb
is considered for deletion. Complete details on the
Explanation: The output member bbbbbbbb in type output deleted can be found in the build report.
aaaaaaaa at the specified build group would have been
This message is provided for information only.
deleted if the build was run in a non-report mode.
FLM44602 TYPE aaaaaaaa MEMBER bbbbbbbb NOT FLM51001 BLANK USERID IS SPECIFIED AS AN
BUILT INPUT TO THE PROMOTE
PROCESSOR.
Explanation: This message identifies members of the
current input list that were not built. Members of the Explanation: The promote process has started. A blank
input list will not be built when an error occurs when user ID was specified as an input parameter. If the
the translator encounters an error processing an earlier processor was invoked through the SCLM Promote
member of the Input List. This message is provided for panel, SCLM retrieves the user ID from the ISPF
information only. variable pool.
User Response: Use the listings data set to locate and User Response: Verify that the user ID specified in the
correct all errors identified by the translator. If the input parameter is correct and non-blank. For more
return code from the translator is acceptable and build information about the promote input parameters, see
indicated that the translator failed, contact the project ISPF Software Configuration and Library Manager (SCLM)
manager. Referenc
FLM44609 >>>>> TOTAL MEMBERS ===> aaa FLM51002 INVALID SCOPE SPECIFIED.
TOTAL SLOC = bbb
Explanation: The promote scope specified is invalid.
Explanation: This message describes the total number Valid promote scopes are NORMAL, SUBUNIT, and
of members and the total source lines of code (SLOC) EXTENDED.
in the preceding input list. This message is provided
User Response: Verify that the input parameters
for information only.
specified for the promote processor are correct.
User Response: Contact the project manager if you
want more members or SLOC per input list.
FLM51003 INVALID PROMOTE MODE
Project Manager Response: Change the MBRLMT SPECIFIED.
parameter, the SLOCLMT parameter, or both
Explanation: The promote mode specified is invalid.
parameters of the FLMLANGL macro for the desired
Valid promote modes are CONDITIONAL,
translator. The FLMLANGL macro is located in the
UNCONDITIONAL, and REPORT.
project definition.
User Response: Verify that the input parameters
specified for the promote processor are correct.
FLM45000 ERROR PROCESSING CURRENT
BUILD
FLM51004 PROMOTE BYPASSED, GROUP:
Explanation: An error was encountered during the
aaaaaaaa IS TOP GROUP.
processing of the current build.
Explanation: Group aaaaaaaa has no group defined to
User Response: Examine the build messages file to
promote to in this project definition. The promote
determine the cause of the error during the build.
report is created as if this were a report-only promote.
User Response: Verify that the group specified as an
FLM46000 BUILD PROCESSOR COMPLETED -
input parameter to the promote processor is the group
aaaaaaaa ON bbbbbbbb
containing the data to be promoted. Also verify that
Explanation: The build processor completed. you specified the correct project definition as an input
to the promote processor.
User Response: See the message data set for all the
messages related to the build.
FLM51006 SPECIFIED GROUP: aaaaaaaa IS A
PRIMARY NON-KEY GROUP
FLM49000 INVOKING BUILD PROCESSOR
Explanation: Group aaaaaaaa is a primary non-key
Explanation: This message is provided for information
group. Promoting from a primary non-key group is not
only.
allowed. For a definition of primary non-key groups,
see ISPF Software Configuration and Library Manager
FLM51000 PROMOTE PROCESSOR INITIATED - (SCLM) Project Manager’s Guide
aaaaaaaa ON bbbbbbbb
User Response: Verify that the group and project
Explanation: This message is provided for information definition specified as inputs to the promote processor
only. are correct. For more information about primary
non-key groups, see ISPF Software Configuration and
Library Manager (SCLM) Project Manager’s Guide
FLM51008 USER DEFINED DDNAME: aaaaaaaa FLM51103 NO KEY GROUP EXISTS BELOW
FOR PROMOTE MESSAGES NOT GROUP: aaaaaaaa
ALLOCATED
Explanation: Group aaaaaaaa is a non-key group and is
Explanation: The ddname aaaaaaaa , which was defined as one of the lowest groups in the hierarchy.
specified for the promote messages, was not allocated. No key group is defined below group aaaaaaaa in the
If the promote function is invoked through the SCLM hierarchy.
services, the ddname for the promote messages is
optional. If the ddname is not specified, the promote User Response: Contact the project administrator.
messages are sent to the terminal by default. If the Project Manager Response: The lowest groups of the
ddname is specified, it must be allocated. project hierarchy (the development groups) must be
User Response: Verify that the user-supplied ddname key groups. Modify the project definition to make the
for promote messages is allocated. Submit the job lowest group key and resubmit the job.
again.
FLM52000 INITIATING VERIFICATION PHASE -
FLM51009 USER DEFINED DDNAME: aaaaaaaa aaaaaaaa ON bbbbbbbb
FOR PROMOTE REPORT NOT Explanation: Indicates that the promote verification
ALLOCATED phase has been initiated. In this phase, SCLM verifies
Explanation: DDname aaaaaaaa , which was specified all members within the scope of the architecture
for the report, was not allocated. If the promote definition. All members must be up to date (for
function is invoked through SCLM services, the example, source matches object) and must have correct
ddname for the promote report is optional. If the accounting information. This message is for information
ddname is not specified, the promote report is sent to only.
the terminal by default. If the ddname is specified, it
must be allocated. FLM52001 VERIFICATION PHASE FOR GROUP:
User Response: Verify that the user-supplied ddname aaaaaaaa
for promote report is allocated. Submit the job again. Explanation: Indicates that the promote verification
phase has been initiated for group aaaaaaaa. This
FLM51010 USER DEFINED DDNAME&colon message is for information only.
aaaaaaaa FOR COPY ERROR
MESSAGES NOT ALLOCATED FLM52103 ERROR RETRIEVING BUILD MAP
Explanation: Ddname aaaaaaaa , which was specified INFORMATION,
for the promote copy error messages, was not allocated.
If the promote function is invoked through SCLM CODE: aaa TYPE: bbbbbbbb
services, the ddname for the copy error messages is MEMBER: cccccccc
optional. If the ddname is not specified, the copy error REFERENCED BY BUILD MAP AT
messages are sent to the terminal by default. If the TYPE: dddddddd MEMBER: eeeeeeee
ddname is specified, it must be allocated. Explanation: SCLM could not retrieve build map
User Response: Verify that the user-supplied ddname information for member eeeeeeee.
INPUT GROUP : aaaaaaaa TYPE: If the ACCESS KEY is not blank, refer to local &scm
bbbbbbbb MEMBER: cccccccc procedures to determine the cause of action based on
ERROR GROUP1: dddddddd the values of the access key. If the access key is eligible
DATE: eeeeeeee TIME: ffffffff for removal, use the UNLOCK service to reset the
ERROR GROUP2: gggggggg access key to blanks.
DATE: hhhhhhhh TIME: iiiiiiii If the ACCOUNTING RECORD TYPE is initial or
Explanation: The version of the member in dddddddd lockout and the member is not present in the group
was not based on the member in gggggggg. This error you are promoting from, delete the accounting
usually means that a version of the member between information using the library utility (or use an
the two groups has been deleted. equivalent function such as the UNLOCK service).
The predecessor Date and Time fields in the accounting If the member exists, use the SCLM editor or SAVE
information for the member in dddddddd should contain service to create correct accounting information.
the last modified Date and Time fields for the next Rebuild the architecture member being promoted after
occurrence of the member within the hierarchy. the accounting information has been either deleted or
updated.
The promote processor, in CONDITIONAL mode,
prevents the member in gggggggg from being replaced.
User Response: Verify that the member contains all of
FLM61035 TAILORED OUTPUT LINE LENGTH LEC For HL and LEC architecture members.
EXCEEDS LIMIT NONE For all architecture members and source
Explanation: The output line that is written to the members (no cutoff).
tailored file exceeded the 2048-character limit. TOP SOURCE
User Response: Verify that the length of the lines For all top source members and all
being written as output to the tailored file is not greater architecture members.
than 2048. If it is greater than 2048, change your
formatted report line to contain SCLM variables that FLM62010 REPORT DDNAME AND MESSAGE
write 2048 characters or less to the tailored file. DDNAME MUST BE DIFFERENT
Explanation: A function was invoked with the same
FLM62000 ARCHITECTURE REPORT ddname specified for both the report file and the
PROCESSOR INITIATED - aaaaaaaa ON messages file.
bbbbbbbb
User Response: Specify different ddnames for the
Explanation: Report processing has started. This report file and the messages file.
message is provided for information only.
User Response: Specify the listings ddname for the 528 Requested data set unavailable. The
given function and run the function again. data set is allocated to another job
and its usage attributes conflict with
this request.
FLM70600 DATE/TIME VERIFICATION FAILED
FOR GROUP: aaaaaaaa TYPE: bbbbbbbb 5896 Data set does not exist.
MEMBER: cccccccc User Response: Submit the job again. If the error
Explanation: The VERIFY translator was invoked as recurs, report this message (including the message ID
part of Build or Promote verification, and returned a and all text fields) to IBM support.
date/time indicating that the member cccccccc is out of
date. FLM71002 ERROR INVOKING TRANSLATOR:
User Response: Verify that the date is valid and aaa(16)
submit the job again. Explanation: SCLM could not invoke translator
aaa(16). The load module containing the translator
FLM70601 VERIFICATION TRANSLATOR might be allocated exclusively to another job, or there
FAILED FOR LANGUAGE: aaaaaaaa is an error in the language definition that defines the
translator.
Explanation: The return code from the verification
translator for language aaaaaaaa exceeded the allowable User Response: If the translator has been used
maximum good return code. successfully in the past and changes were not
anticipated (for example, a new compiler release),
User Response: Determine the reason for the bad invoke the processor again. If the translator is new or
return code from the verification translator and take the problem recurs, report this message (including the
appropriate action. message ID and all text fields) to IBM support.
FLM70801 ERROR DEALLOCATING DATA SET FLM71004 TRANSLATOR RETURN CODE FROM
NUMBER: aaa FOR LANGUAGE: ===> aaa(16) ===> bbbb
cccccccc TRANSLATOR: bbb (16) CODE:
ddd Explanation: The return code from the invoked
translator did not match the GOODRC parameter
Explanation: An error occurred while deallocating a specified for the translator. Translator output, such as
data set for the translator bbb (16). The data set number compiler listings, will be saved in the listings data set
aaa identifies the allocated data set for that translator.
>64 SVC 99 error; reason code (decimal): User Response: Edit the language defintion and
correct the WHEN keyword value on the FLMTCOND
528 Requested data set unavailable. The macro following the FLMTRNSL with
data set is allocated to another job COMPILE=aaaaaaaa. Reassemble and link the project
and its usage attributes conflict with definitions that use the language definition.
this request.
5896 The data set does not exist. FLM72001 INVALID OR MISSING VALUE FOR
User Response: Submit the job again. If the error PARAMETER: aaaaaaaa
recurs, report this message (including the message ID Explanation: The parameter aaaaaaaa has a invalid or
and all text fields) to IBM support. missing value. This message is issued by the
Project Manager Response: Contact IBM support for FLMTXFER translator.
assistance. User Response: Contact the project manager.
Project Manager Response: Update the call to the
FLM71010 ERROR: FLMTCOND macro keywords FLMTXFER translator to ensure that all required
GROUP and NOTGROUP specified parameters are passed and that all parameters have
together. FLMTCOND follows valid values.
FLMTRNSL with COMPILE=aaaaaaaa
Explanation: aaaaaaaa is the COMPILE keyword FLM72002 NO DATA SET ALLOCATED TO DD
value on the FLMTRNSL associated with this NAME: aaaaaaaa
FLMTCOND macro. This error should be trapped by
the FLMTCOND macro and should not occur at Explanation: The ddname aaaaaaaa is not allocated,
runtime. but is required for the FLMTXFER translator.
User Response: See the project adminstrator for User Response: Contact the project manager.
correction of the project definition. Project Manager Response: Update the call to the
User Response: Remove GROUP or NOTGROUP in FLMTXFER translator to ensure that all required
the FLMTCOND macro. The FLMTCOND macro will ddnames are allocated. The ddname can be a ddname
follow an FLMTRNSL macro with COMPILE=aaaaaaaa used directly by the FLMTXFER translator, or it can be
User Response: Contact the project manager. User Response: Contact the project manager.
Project Manager Response: Ensure that the transfer Project Manager Response: Update the call the
types passed in the FILES ddname to the FLMTXFER FLMTXFER to ensure that members being transfered to
translator are valid. the workstation exist on the host prior to the transfer.
FLM72011 TRANSFER MEMBER NOT IN BUILD FLM75003 ERROR: aaaaaaaa NOT SPECIFIED IN
SCOPE MEMBER: aaaaaaaa TYPE: PROXY FILE
bbbbbbbb
Explanation: The aaaaaaaa element was not found in
Explanation: Member aaaaaaaa in type bbbbbbbb is not the proxy file.
in the scope of the build and will not be transfered.
User Response: Verify that the CSP/370AD proxy
User Response: Contact the project manager. contains the parameter MEMBER(name) for the
CSP/370AD* GENERATE command.
Project Manager Response: Ensure that each
statement in the FILES ddname input that specifies an
SCLM member name uses only members in the build FLM75004 ERROR: COULD NOT OPEN
scope. The FLMTBMAP translator can be used to DDNAME = aaaaaaaa, PASCAL
obtain a list of inputs and outputs for a specific build. RUN-TIME ERROR = bbb
Explanation: The ddname aaaaaaaa could not be
FLM72012 UNABLE TO OBTAIN DATASET opened.
NAME FOR DD NAME: aaaaaaaa
User Response: Verify that the DDNAME = aaaaaaaa
Explanation: The FLMTXFER translator could not exists in your system. The codes for the PASCAL
obtain the data set name for ddname aaaaaaaa. run-time error bbb are described in the VS Pascal
Application Programming Guide A common error code is:
User Response: Contact the project manager.
v 048 - Missing member in File: member_library
Project Manager Response: Ensure that the ddname is
being allocated to a cataloged data set.
FLM75006 WARNING: THE FOLLOWING
PARAMETERS FOR THE CSP/370AD
FLM72013 FILE TRANSFER FAILED, RETURN GENERATE COMMAND WILL BE
CODE: aaaa, FROM FILE: bbbbbbbb, USED: SYSTEM(TARGET_SYSTEM),
TO FILE: cccccccc MAPS(NONE), TABLES(NONE), AND
Explanation: The ISPF FILEXFER service failed with a BATCH(N). THE CORRESPONDING
return code of aaaa in the transfer of file bbbbbbbb to file PARAMETERS IN THE PROXY FILE
cccccccc. WILL BE IGNORED.
User Response: Contact the project manager. Explanation: SCLM will append the CSP/370AD
GENERATE command with a list of parameters that
Project Manager Response: Refer to the ISPF use specific values. If the user specifies one of these
FILEXFER service documentation for an explanation of parameters, they will be ignored, and the SCLM
return code aaaa and additional responses. specified ones will be used instead. The value for
’target_system’ in SYSTEM(target_system) is obtained
from the SYSTEM= value of the OPTIONS parameter
FLM75001 INVALID OR MISSING DATA FOR
for the FLMTRNSL macro. This is the FLMTRNSL
INPUT PARAMETER aaaaaaaa
macro for the CSP/370AD Lista/Generate translator for
Explanation: In the Language Definition the input the language definition associated with the CSP/370AD
parameter aaaaaaaa is missing or is not valid. proxy member.
User Response: Contact the project administrator. User Response: Delete from the Proxy file any of the
parameters mentioned in the message.
Project Manager Response: Verify that the Language
Definition contains all the input parameters, and that
the parameters have the proper values. FLM75007 END OF PROXY FILE REACHED
BEFORE THE TAG aaaaaaaa WAS
FOUND.
FLM75002 ERROR: aaaaaaaa TAG NOT FOUND IN
PROXY FILE Explanation: The tags in the CSP/370AD proxy file
must come in pairs; for example, the :BUILD tag must
Explanation: The aaaaaaaa tag was not found in the
have an :EBUILD tag. This message indicates that a
proxy file.
corresponding end tag is missing.
User Response: Verify that the CSP/370AD proxy
User Response: Ensure that the tags are paired, such
contains a BUILD/EBUILD tag section. Optionally, if
as :BUILD with :EBUILD.
you have EZE and GROUP tags then they should have
a corresponding EEZE or EGROUP tag.
FLM75011 GROUP aaaaaaaa NOT FOUND IN Project Manager Response: Specify a Read/Write
SCLM HIERARCHY TABLE MSL.
FLM80011 CONFLICTING DEPENDENCY TYPE Explanation: The change code verification routine
FLAGS FOUND IN THE aaaaaaaa could not be invoked.
"ACCOUNTING LIST INFO ARRAY" User Response: Verify that the routine exists within
data set bbb(44). If the routine does not exist, move it
RECORD KIND: aaaa into the proper data set. If it does exist, report this
CU NAME: bbb(55) ccc(55) message (including the message ID and all text fields)
CU TYPE: d GENERIC FLAG: e to IBM support.
DEPEND NAME: fff(55) ggg(55)
DEPEND CU TYPE: h
Explanation: Different type flags exist for the same
Explanation: An I/O error occurred while trying to Explanation: The value entered to indicate whether or
retrieve a list of existing SCLM accounting records. not the export data set should be purged before
exporting is invalid.
User Response: Submit the job again. If the problem
recurs, contact the project manager. User Response: Enter either Y or N for the purge
option, and submit the export job again.
Project Manager Response: Run IDCAMS against the
export data set to determine the problem.
FLM85010 MEMBER aaaaaaaa CONTAINS
NON-BLANK AUTHCODE CHANGE
FLM85004 I/O ERROR RETRIEVING LIST OF FIELD. MEMBER NOT EXPORTED.
BUILD MAP RECORDS. GROUP:
aaaaaaaa TYPE: bbbbbbbb Explanation: Member aaaaaaaa was in the process of
having the authorization code changed when the tried
Explanation: An I/O error occurred while trying to to copy it.
retrieve a list of existing build map accounting records.
User Response: Submit the export job again.
User Response: Submit the job again. If the problem
recurs, contact the project manager.
FLM87100 ERROR, PARAMETER STRING MUST FLM87110 ERROR FOUND ON LINE aaaa OF
BE SHORTER THAN aaa CHARS bbbbbbbb DATA SET
LONG
Explanation: Check to see if another error message
Explanation: The input parameter string exceeded the was printed. If it was, correct the error indicated by the
maximum length. other error message first. If the error message
FLM87110 is the only error message printed, then an
User Response: Shorten the input parameter string to
error was found on line number aaaa of data set
a valid length.
bbbbbbbb. If FLMCMD FILE is used, the line number
refers to the number of prompts that have been
FLM87103 RECURSIVE "FILE" COMMAND displayed. The error occurred in the command issued
INVOCATIONS ARE NOT ALLOWED at the last prompt.
Explanation: A FILE command cannot be invoked User Response: The error should be corrected in the
within another FILE. data set. For more information about SCLM services,
see ISPF Software Configuration and Library Manager
User Response: Remove the recursive occurrence of (SCLM) Referenc
the FILE command. The contents of the referenced data
set can be copied directly into the original data set if
desired. FLM87115 DBUTIL aaa(9) AT bbbbbbbb, CODE: ccc
Explanation: Completion message for DBUTIL. This
FLM87105 THE COMMAND IS NOT SUPPORTED message is provided for information only.
User Response: For information on the return code,
COMMAND: aaa(60) see ISPF Software Configuration and Library Manager
Explanation: The command is not supported by this (SCLM) Referenc
release of SCLM.
User Response: For a list of and descriptions of valid FLM87120 ERROR, aaa(24) PARAMETER IN
SCLM service commands, see ISPF Software COLUMN bbb IS TOO LONG
Configuration and Library Manager (SCLM) Referenc Explanation: The parameter aaa(24) is longer than the
maximum allowed.
FLM87107 aaaaaaaa bbb(24) FOR MEMBER cccccccc User Response: Shorten the parameter. For more
AT dddddddd, CODE: eee details on the SCLM services, see ISPF Software
Explanation: The FLMCMD command termination Configuration and Library Manager (SCLM) Referenc
message aaaaaaaa represents the service that was
executed. bbb(24) represents the completion status of FLM87125 ERROR, aaa(24) PARAMETER MUST BE
the command. SPECIFIED
User Response: For information on the return code, Explanation: The parameter aaa(24) has not been
see ISPF Software Configuration and Library Manager specified.
(SCLM) Referenc
User Response: Add the parameter to the SCLM
service invocation. For more details on the SCLM
FLM87109 aaaaaaaa bbb(24) FOR GROUP cccccccc AT services, see ISPF Software Configuration and Library
dddddddd, CODE: eee Manager (SCLM) Referenc
Explanation: This service operates on an SCLM
controlled group rather than a member. The FLMCMD FLM87130 INVALID VALUE IN COLUMN aaa
command termination message aaaaaaaa represents the FOR bbb(24) PARAMETER
service that was executed. bbb(24) represents the
completion status of the command. cccccccc is the group Explanation: The value for the bbb(24) parameter is
processed by the service. dddddddd is the time stamp invalid. The column number (aaa(24)) identifies the
when the service ended. eee is the return code. This starting location of the invalid value with the
return code is documented in the description for each command.
service.
User Response: Correct the value of the parameter in
User Response: For information on the return code, the command data set. For more details on the SCLM
see ISPF Software Configuration and Library Manager services, see ISPF Software Configuration and Library
(SCLM) Referenc Manager (SCLM) Referenc
FLM87190 RECOVER TO DATA SET OR GROUP FLM87201 SCLM ID: aaaaaaaa IS NOT IN USE
AND TYPE MUST BE SPECIFIED
Explanation: The SCLM ID corresponds to members
Explanation: A value must be specified for the data that have been locked but not freed by either the
set to receive the recovered version or values must be UNLOCK or the STORE service. These will be
specified for the group and type in the SCLM project to converted from initial state to lockout. This is just a
receive the recovered member. warning message.
User Response: Specify a value for the recovery data
set or specify values for the SCLM group and type to FLM87202 INVALID SCLM ID: aaaaaaaa
receive the recovered version.
Explanation: The syntax of the SCLM ID is not valid.
SCLM IDs are generated in the format FLMddddd where
FLM87191 RECOVER TO DATA SET CAN NOT d represents a digit from 0-9.
BE SPECIFIED WITH TARGET GROUP
User Response: Check the SCLM ID specified for
OR TYPE
accuracy, or make sure you used the INIT service to
Explanation: A data set for recovery of a version and generate an SCLM ID before you try to use the FREE
a group and/or type for recovery of a version may not service on it.
be specified together.
User Response: Specify either a data set or a group FLM89001 NO ACCOUNTING INFORMATION
and type, not both. FOUND IN HIERARCHY VIEW FOR
GROUP: aaaaaaaa TYPE: bbbbbbbb
MEMBER: cccccccc
FLM87192 BOTH TARGET GROUP AND TYPE
MUST BE SPECIFIED Explanation: No accounting information was found
for the specified member in the hierarchy view
Explanation: Values were not specified for both the
beginning at the specified group.
target group and type in recovering a version of a
member. User Response: Verify selection parameters are correct
and resubmit.
User Response: Specify values for both the target
group and type to receive the version of a member.
FLM89002 ERROR ACCESSING PROJECT
DATABASE FOR PROJECT: aaaaaaaa
FLM87193 UNABLE TO STORE DATA IN
REQUESTED TABLE: aaaaaaaa Explanation: An error occurred while attempting to
access the project database for the specified project.
Explanation: The VERINFO service encountered an
error when storing change codes, includes, user entries,
or compilation units from the accounting record into FLM89004 INCOMPATIBLE ACCOUNT
the user defined table. INFORMATION TYPES. CURRENT
TYPE: a. SPECIFIED TYPE: b
User Response: Examine the user defined table that
holds the values from the VERINFO service. The table Explanation: The member specified has a status
may not be properly defined. (editable, non-editable, and so forth) that is
incompatible with the status specified in the update
accounting information.
FLM87194 INVALID DATA SET NAME -
MEMBER NAMES ARE NOT User Response: Enter compatible type and resubmit.
ALLOWED FOR RETRIEVAL DATA
SETS
FLM89005 CANNOT CREATE NEW
Explanation: The VERRECOV service does not allow ACCOUNTING RECORD OF
member names to be specified for non-SCLM controlled ACCOUNT INFO TYPE: a
retrieval datasets.
Explanation: No accounting information exists for the
User Response: Enter either a sequential data set specified member. New accounting records can only
name or a partitioned data set name without a member have the status INITIAL or NON-EDITABLE. The
name. status specified in the accounting information was
other than INITIAL or NON-EDITABLE.
User Response: Enter valid type and resubmit.
FLM89006 ERROR UPDATING ISPF STATS FOR FLM89011 LANGUAGE: aaaaaaaa NOT DEFINED
PROJECT: aaaaaaaa GROUP: bbbbbbbb FOR SCLM
TYPE: cccccccc MEMBER: dddddddd
Explanation: An attempt to update an accounting
Explanation: The service encountered an unexpected record failed because the language specified in the
error updating the ISPF statistics of the member. accounting information is not defined to SCLM.
User Response: Contact the System Administrator. User Response: Enter a valid language in the
accounting information and resubmit.
FLM89007 ERROR UPDATING PROJECT Project Manager Response: Define the language
DATABASE FOR PROJECT: aaaaaaaa specified to SCLM.
GROUP: bbbbbbbb TYPE: cccccccc
MEMBER: dddddddd
FLM89012 INVALID ACCOUNTING
Explanation: The service encountered an unexpected INFORMATION KEYWORD: aaaa
error updating the SCLM project database containing
Explanation: A keyword specified in the dynamic
the member’s information.
portion of the accounting record is not valid. The list of
User Response: Contact project manager. valid keywords is: INCL, CODE, and USER.
Project Manager Response: Run IDCAMS against the User Response: Correct the invalid keyword in the
data set to determine problem. dynamic portion of the accounting record and resubmit.
FLM89008 NO BUILD MAP INFORMATION FLM89013 INVALID BUILD MAP KEYREF: aaaa
FOUND IN HIERARCHY VIEW FOR
Explanation: A KEYREF specified in the dynamic
GROUP: aaaaaaaa TYPE: bbbbbbbb
portion of the build map information is not valid.
MEMBER: cccccccc
User Response: Correct the invalid keyword in the
Explanation: No build map information was found for
dynamic portion of the build map and resubmit.
the specified member in the hierarchy view beginning
at the specified group.
User Response: Verify selection parameters are correct
and resubmit.
ERROR - FLMTCOND SPECIFIED WITHOUT ERROR - GROUP NAME MUST ALSO BE DEFINED
MATCHING FLMTRNSL IN FLMGRP MACRO
Macro: FLMTCOND Macro: FLMAEND, FLMATVER, FLMGROUP
Explanation: An FLMTCOND macro precedes an Explanation: The value of the GROUP parameter on
FLMTRNSL macro or more than the maximum the FLMATVER macro is not a valid group defined in
FLMTCOND macros are specified for an FLMTRNSL the project definition.
macro.
Project Manager Response: Change the value of the
Programmer Response: Examine the language GROUP parameter to a valid group, or add the group
definitions in the project definition for an FLMTCOND with a FLMGROUP macro, and assemble the project
macro that precedes an FLMTRNSL macro or that is definition again.
present with other FLMTCOND macros following an
FLMTRNSL macro. Edit the language definition for
ERROR - GROUP: xxxxxxxx MUST BE A KEY
correct use of the FLMTCOND macro. Reassemble and
GROUP (DEVELOPMENT GROUP)
link the project definitions that use the language
definition. Macro: FLMAEND, FLMGROUP
Explanation: The development group xxxxxxxx does
ERROR - FLMTOPTS MUST FOLLOW AN not have the value of Y specified for the KEY
FLMTRNSL MACRO parameter. Development groups must be key.
Macro: FLMTOPTS Project Manager Response: Change the value of the
key parameter to Y, and assemble the project definition
Explanation: An FLMTOPTS macro precedes an
again.
FLMTRNSL macro.
Programmer Response: Examine the language
ERROR - HIERARCHY ALLOCATION FROM
definitions in the project definition for an FLMTOPTS
GROUP: xxxxxxxx EXCEEDS MAXIMUM ALLOWED
macro that precedes an FLMTRNSL macro. Edit the
OF: 123
language definition for correct use of the FLMTOPTS
macro. Reassemble and link the project definitions that Macro: FLMAEND, FLMGROUP
use the language definition.
Explanation: The hierarchical view from group
xxxxxxxx has more than 123 groups. See ISPF Software
ERROR - FLMTYPE EXTEND PARM USED TO Configuration and Library Manager (SCLM) Developer’s
REFERENCE UNDEFINED TYPE: xxxxxxxx Guide for more information.
Macro: FLMAEND, FLMTYPE Project Manager Response: Reduce the number of
groups in the view from group xxxxxxxx, and assemble
Explanation: Type name xxxxxxxx specified as the
the project definition again.
EXTEND parameter of an FLMTYPE macro is not a
valid type defined in the project definition.
ERROR - IF IOTYPE=L, PORDER IN FLMTRNSL
Project Manager Response: Make sure all EXTEND
MUST BE 2 OR 3
type names are defined in the project definition using
FLMTYPE macros, and assemble the project definition Macro: FLMALLOC, FLMTRNSL
again.
Explanation: The value of PORDER in FLMTRNSL
must be 2 or 3 when the IOTYPE value in FLMALLOC
ERROR - FLMTYPE MUST NOT REFERENCE is L.
ITSELF VIA THE EXTEND PARM
Project Manager Response: Change the IOTYPE or
Macro: FLMTYPE PORDER value in error, and assemble the project
definition again.
Explanation: The type name on the FLMTYPE macro
must not be used as the type name on the EXTEND
keyword parameter. ERROR - INVALID OR MISSING FUNCTION
PARAMETER SPECIFIED
Project Manager Response: Use a different type name
on the EXTEND keyword parameter, and assemble the Macro: FLMTRNSL
project definition again.
Explanation: The specified value of the FUNCTN
parameter is invalid or blank. Allowable values are
PARSE, VERIFY, BUILD, COPY, or PURGE.
Project Manager Response: Change the value to an
ERROR - INVALID SCOPE: aaaaaaaa FOR ERROR - INVALID VALUE SPECIFIED FOR FIELD
LANGUAGE: bbbbbbbb ″WHEN″
Macro: FLMLANGL Macro: FLMTCOND
Explanation: The value specified on the SCOPE Explanation: An FLMTCOND macro was specified
parameter (aaaaaaaa) is incorrect. SCOPE parameter with the WHEN keyword that has an invalid value.
values are LIMITED, NORMAL, SUBUNIT or
Programmer Response: Examine the language
EXTENDED.
definitions in the project definition for an FLMTCOND
Project Manager Response: Correct the value, and macro that uses the WHEN keyword. Edit the language
assemble the project definition again. definition for a correct WHEN keyword value for the
FLMTCOND macro. Reassemble and link the project
definitions that use the language definition.
ERROR - INVALID VALUE FOR ″ACTION″
PARAMETER
ERROR - KEY GROUP > 123 FOR GROUP: xxxxxxxx
Macro: FLMTOPTS
Macro: FLMAEND, FLMGROUP
Explanation: A value other than APPEND or
REPLACE was specified for the ACTION keyword. Explanation: The hierarchical view from group
xxxxxxxx has more than 123 key groups. See ISPF
Programmer Response: Change the value of the
Software Configuration and Library Manager (SCLM)
ACTION keyword to APPEND or REPLACE in the
Developer’s Guide for more information.
FLMTOPTS macro. The FLMTOPTS macro will follow
an FLMTRNSL macro in a language definition. Project Manager Response: Reduce the number of key
Reassemble and link the project definitions that use the groups in the view from group xxxxxxxx, and assemble
language definition. the project definition again.
ERROR - INVALID VALUE FOR FIELD ″ACTION″ ERROR - KEYREF AND DFLTTYP NOT FOUND:
aaaaaaaa bbbbbbbb
Macro: FLMTCOND
Macro: FLMAEND
Explanation: A value other than RUN or SKIP was
specified for the ACTION keyword. Explanation: A language definition contains multiple
translators with the FLMTCOND macro and a WHEN
Programmer Response: Change the value of the
clause specified. An output allocation for a translator
ERROR - LANGUAGE IS ONLY VALID FOR ERROR - MEMBER IS ONLY VALID FOR IOTYPE=P
IOTYPE=O OR P Macro: FLMALLOC
Macro: FLMALLOC Explanation: A value for the MEMBER parameter can
Explanation: A language can be specified only on the be specified only when the IOTYPE value is P.
LANG keyword parameter for IOTYPE values O and P. Members can be written only to partitioned data sets,
Different languages can only be assigned on build which are allocated using an IOTYPE value of P.
outputs. Project Manager Response: Remove the MEMBER
Project Manager Response: Change the IOTYPE to O parameter, or change the IOTYPE value to P, and
or P, and assemble the project definition again. assemble the project definition again.
Explanation: A user-specified pseudonym language Explanation: A VSAM accounting data set must be
name was not specified on the LANG keyword specified on the ACCT parameter.
parameter. See ISPF Software Configuration and Library Project Manager Response: Add the parameter and
Manager (SCLM) Referenc for more information. value, and assemble the project definition again.
Project Manager Response: Add a user-specified
| ERROR - NEW FORMAT PARAMETER USED WITH | routine specifications used in the project definition. Use
| OLD FORMAT EXIT USER EXIT: aaaaaaaa | only the new OR old format. After the change is made,
| assemble and link the project definition again.
| Macro: FLMCNTRL
| Explanation: The old format, aaaaaaaa, was used to | ERROR - OLD FORMAT PARAMETER USED WITH
| specify the user exit routine, but the new format was | NEW FORMAT EXIT. USER EXITaaaaaaaa
| used to specify one of the other parameters for the user
| exit. For example, BLDEXT1 (old format) was used to
| Macro: FLMCNTRL
| specify the user exit routine, but BLDNTFOP (new | Explanation: The new format, aaaaaaaa, was used to
| format) was used to specify the options for the user | specify the user exit routine, but the old format was
| exit. | used to specify one of the other parameters for the user
| Programmer Response: Update the FLMCNTRL
| exit. For example, BLDNTF (new format) was used to
| macro in your project definition to use either all new
| specify the user exit routine, but BEXTIOP (old format)
| format parameters OR all old format parameters for a
| was used to specify the options for the user exit.
| user exit, then assemble and link the project definition | Programmer Response: Update the FLMCNTRL
| again. | macro in your project definition to use either all new
| format parameters OR all old format parameters for the
ERROR - NOTGROUP AND GROUP CAN NOT BE
| user exit, then assemble and link the project definition
SPECIFIED TOGETHER
| again.
Macro: FLMTOPTS
ERROR - OPTIONS PARAMETER REQUIRED
Explanation: The GROUP and NOTGROUP keywords
Macro: FLMTOPTS
were both specified in an FLMTOPTS macro.
Explanation: The OPTIONS keyword must be
Programmer Response: Remove GROUP or
specified.
NOTGROUP in the FLMTOPTS macro. The FLMTOPTS
macro will follow an FLMTRNSL macro in a language Programmer Response: Examine the language
definition. Reassemble and link the project definitions definitions in the project definition for usage of the
that use the language definition. FLMTOPTS macro. Add the OPTIONS keyword to the
FLMTOPTS macros that do not specify the OPTIONS
keyword. Reassemble and link the project definitions
ERROR - NOTGROUP SPECIFIED WITH GROUP,
that use the language definition.
NOTGROUP IGNORED
Macro: FLMTCOND
ERROR - OUTPUT LANGUAGE NOT DEFINED
Explanation: The NOTGROUP and GROUP keywords
Macro: FLMAEND, FLMALLOC, FLMLANGL
were both specified in an FLMTCOND macro. The
NOTGROUP keyword value will be ignored and the Explanation: The language specified on the LANG
macro will be used as though only the GROUP parameter of an FLMALLOC macro is not defined. All
keyword value was specified. languages used as values for the LANG parameter
must be defined using the FLMLANGL macro.
Programmer Response: Remove GROUP or
NOTGROUP in the FLMTCOND macro. The Project Manager Response: Change the language
FLMTCOND macro will follow an FLMTRNSL macro specified for LANG, or define the specified language
in a language definition. Reassemble and link the using FLMLANGL, and assemble the project definition
project definitions that use the language definition. again.
| ERROR - OLD AND NEW FORMATS BOTH ERROR - PDSDATA VALUE MUST BE ″Y″ FOR
| SPECIFIED FOR USER EXIT. USER EXITaaaaaaaa BUILD/PARSE
| USER EXITbbbbbbbb
Macro: FLMTRNSL
| Macro: FLMCNTRL
Explanation: The specified value on the PDSDATA
| Explanation: Both the old format and new format parameter is incorrect. The allowable value for build
| were used to specify a user exit routine, where and parse translators is Y.
| aaaaaaaa is the old format and bbbbbbbb is the new
| format. For example, BLDNTF (new format) and Project Manager Response: Change the PDSDATA
| BLDEXT1 (old format) both appear as parameters on value to Y, and assemble the project definition again.
| the FLMCNTRL macro in the project definition.
| Programmer Response: Delete one of the user exit
ERROR - PRIMARY GROUPS > 123 FOR GROUP: ERROR - RECURSIVE ENTRY CAUSED BY
xxxxxxxx SPECIFIED AUTHCODE GROUP
Macro: FLMAEND, FLMGROUP Macro: FLMAGRP
Explanation: The hierarchical view from group Explanation: An authorization code specified on the
xxxxxxxx has more than 123 groups. See ISPF Software AC parameter is also the authorization code group
Configuration and Library Manager (SCLM) Developer’s name on the same FLMAGRP macro.
Guide for more information.
Project Manager Response: Change the authorization
Project Manager Response: Reduce the number of code or the group name, and assemble the project
groups in the view from group xxxxxxxx, and assemble definition again.
the project definition again.
ERROR - SPECIFICATION OF THIS MACRO
ERROR - PROBLEM IN FLMTRNSL NUMBER: nnnn EXCEEDS MAXIMUM ALLOWED
Macro: FLMAEND Macro: FLMALLOC, FLMATVER, FLMCPYLB,
FLMEXLIB, FLMGROUP, FLMLANGL, FLMTRNSL,
Explanation: This error occurs when all of the
FLMTYPE
FLMTRNSL macros for BUILD translators in a
language definition that use FLMTCOND with the Explanation: Each of these macros can be specified a
WHEN keyword do not have identical KEYREF and limited number of times in a project definition. In each
DFLTTYP keywords on the FLMALLOC macros. The case, the maximum number is 32 000.
FLMTRNSL number is the ordinal of the FLMTRNSL
Project Manager Response: Reduce the number of
macro in a language definition. This is one of several
instances of the macro producing the error, and
messages that describe the problem.
assemble the project definition again.
Programmer Response: Examine all of the messages
to determine the keyword mismatch. Browse the project
ERROR - SPECIFIED ALTC HAS BEEN
definition. The problem was found in FLMTRNSL
PREVIOUSLY DEFINED
number nnnn in a language definition. Edit the
language definition and make the KEYREF and Macro: FLMALTC
DFLTTYP keyword values consistent. Reassemble and
link the project definitions that use the language Explanation: The alternate control name specified has
definition. already been defined using an FLMALTC macro.
Project Manager Response: Change one of the
ERROR - PROBLEM IN LANGUAGE DEFINITION duplicate names, and assemble the project definition
NUMBER: nnnn again.
Macro: FLMAEND
ERROR - SPECIFIED AUTHCODE ALREADY
Explanation: This error occurs when all of the PROCESSED AS A MEMBER
FLMTRNSL macros for BUILD translators in a
language definition that use FLMTCOND with the Macro: FLMAGRP
WHEN keyword do not have identical KEYREF and Explanation: The name of the authorization code
DFLTTYP keywords on the FLMALLOC macros. The group has already been used as one of the
language definition number is the language definition authorization codes specified on the AC parameter of a
ordinal in the project definition. This is one of several previous FLMAGRP macro.
messages that describe the problem.
Project Manager Response: Change the name of the
Programmer Response: Examine all of the messages group, or remove the bad authorization code from the
to determine the keyword mismatch. Browse the project AC parameter of a previous FLMAGRP macro, and
definition. The problem was found in language assemble the project definition again.
definition number nnnn in the project definition. Edit
the language definition and make the KEYREF and
DFLTTYP keyword values consistent. Reassemble and ERROR - SPECIFIED AUTHCODE GROUP
link the project definitions that use the language CONTAINS DUPLICATE MEMBERS
definition. Macro: FLMAGRP
Explanation: The authorization code group name
specified has already been used as a group name on a
previous FLMAGRP macro.
Project Manager Response: Change the name of the
ISRLA000 Activity log error - See system ISRLA104 SCLM project deactivated - The project
programmer - details in the LMF is SCLM controlled, but has been
address space ISPLOG. successfully deactivated.
ISRLA001 Activity log allocation - Error data set ISRLA105 SCLM project activated - The project is
could not be allocated. SCLM controlled, but has been
successfully activated.
ISRLA002 Activity log unavailable - Data set
’aaaaaaaa..bbbbbbbb..ACTLOG’ could not ISRLA110 Activated successfully - The hierarchy
be opened. It may be in use. ’aaaaaaaa’ is activated successfully.
ISRLA003 Activity log write error - Data set ISRLA111 Activated successfully - All hierarchies
’aaaaaaaa..bbbbbbbb..ACTLOG’ had a write in project ’aaaaaaaa’ are activated
error. successfully.
ISRLA004 Act. log close out error - Data set ISRLA112 Deactivated successfully - The hierarchy
’aaaaaaaa..bbbbbbbb..ACTLOG’ had a write ’aaaaaaaa’ is deactivated successfully.
close out error.
ISRLA113 Deactivated successfully - All
ISRLA005 Activity log free error - Data set hierarchies in project ’aaaaaaaa’ are
’aaaaaaaa..bbbbbbbb..ACTLOG’ could not deactivated successfully.
be freed.
ISRLA114 Defined types - Structure for - aaaaaaaa
ISRLA006 Activity log read error - Data set Date: bbbbbbbb Time: cccccccc
’aaaaaaaa..bbbbbbbb..ACTLOG’ had a read
error.
ISRLA115 Where: - 1, 2 indicates hierarchical
position
ISRLA007 Activity log write error - An error
occurred writing
ISRLA116 *** No defined type *** - B indicates
’aaaaaaaa..bbbbbbbb..ACTLOG’ to a
bottom group
temporary file.
ISRLA102 Already activated - The hierarchy ISRLA120 No unit description - Must specify the
’aaaaaaaa’ has already been activated. unit description for the outlist data set.
ISRLA103 Already deactivated - The hierarchy ISRLA121 No block size - Must specify the block
’aaaaaaaa’ has already been deactivated. size for the outlist data set.
ISRLA122 No logical record length - Must specify ISRLA211 Log not sequential -
the logical record length for the outlist ’aaaaaaaa..bbbbbbbb..ACTLOG’ is not a
data set. sequential data set.
ISRLA123 No lines per page - Must specify the ISRLA213 ADMIN not allowed - You cannot
lines per page for the outlist data set. specify a group name of ADMIN for a
member activity log.
ISRLA124 No primary/secondary - Must specify
primary/secondary space quantity for ISRLA214 Invalid selection code - Type an ″s″ in
outlist data set. front of the type to be selected.
Explanation:
ISRLA125 No primary space - Must specify
primary space quantity for partitioned
ISRLA215 Invalid type name - You must enter a
outlist data set.
type name, an asterisk (″*″) or leave the
field blank.
ISRLA200 Enter group name - A group name is
required for this option.
ISRLA216 Group name required - Enter the group
name of the activity log.
ISRLA201 Type ″aaaaaaaa″ deleted - All entries for
type ″aaaaaaaa″ have been deleted.
ISRLA217 Project name required - Enter the project
name of the activity log.
ISRLA202 Type not found - No entries for type
″aaaaaaaa″ exist in the member activity
ISRLA218 Type ″aaaaaaaa″ browsed - The logged
log.
activity for type ″aaaaaaaa″ was browsed.
ISRLC010 Member entry not created - Member ISRLC026 Ddname not found in TIOT - Ddname
entry ’aaaaaaaa’ not created. The type not found in the TIOT.
does not exist.
ISRLC027 Library not deleted - Library controls
ISRLC011 Member entry not created - Member were not deleted. Member controls exist
entry ’aaaaaaaa’ not created. The group for this library.
does not exist.
ISRLC028 Update failed - The group hierarchy is
ISRLC012 Member entry not created - Member active. The update was not performed.
entry ’aaaaaaaa’ not created. The project
does not exist.
ISRLC029 Project in use - Project is currently
being updated by ’aaaaaaaa’.
ISRLC013 Entry not created - ’aaaaaaaa’ was not
created. It already exists.
ISRLC030 ″aaaaaaaa″ not active - The LMF address
space ″aaaaaaaa″ is not accepting any
ISRLC014 Promote failed - The ’to’ data set was requests.
allocated as an alias. Aliases are not
allowed.
ISRLC031 LMF start up in progress - The LMF
address space initialization is not
ISRLC015 Attach failed - Attach failed in module complete.
aaaaaaaa.
ISRLC033 Promote failed - The group ’aaaaaaaa’ is
ISRLC016 ″aaaaaaaa″ not started - The LMF started not active.
task ″aaaaaaaa″ was not found.
ISRLC034 Promote failed - From a non-controlled
ISRLC017 Local lock failed - Local lock failed in lib. can only promote into an entry level
the SVC. lib.
ISRLC018 SVC GETMAIN failed - GETMAIN ISRLC035 Promote failed - Target group ’aaaaaaaa’
failed in the library management facility could not be found.
SVC.
ISRLC036 Promote failed - User is not current
ISRLC019 SVC FREEMAIN failed - FREEMAIN updater of member. current updater is
failed in the library management facility ’aaaaaaaa’.
SVC.
ISRLC037 Abend ’aaaaaaaa’ occurred - ’aaaaaaaa’
ISRLC020 SRB GETMAIN failed - GETMAIN abend during the processing of a library
failed in the SRB. management request.
ISRLC022 SRB purged - The SRB was purged. ISRLC038 Promote failed - Entry level group
’aaaaaaaa’ could not be found.
ISRLC023 GETMAIN failed - GETMAIN failed for
a dynamic TLD. ISRLC039 Activity log not valid - Activity log for
type ’aaaaaaaa’ must be a sequential data
set.
ISRLC024 Member in use - Member is edit locked
by ’aaaaaaaa’.
ISRLC040 Edit lock failed - The member is in a
controlled library which is not active.
ISRLC025 User not authorized - Member ’aaaaaaaa’
could not be edit locked by user.
ISRLC041 Edit lock failed - Requestor is not an ISRLC056 Group deleted - Controls for group
authorized accessor. ’aaaaaaaa’ were deleted from the control
file.
ISRLC042 Edit lock failed - The member ″aaaaaaaa″
has a status or owner of ″bbbbbbbb.″. ISRLC057 Project deleted - Controls for project
’aaaaaaaa’ were deleted from the control
file.
ISRLC043 Member entry not found - Member
entry ’aaaaaaaa’ could not be found in
the control file. ISRLC058 ENQUEUE failed - Member ’aaaaaaaa’ is
not available.
ISRLC044 Promote failed - The ″to″ and ″from″
libraries have incompatible record ISRLC059 Promote failed - The member was not
formats. edit locked.
ISRLC045 Unable to promote data - Data contains ISRLC060 Request failed - The project could not
a user ttr, but is not a load module. be locked or freed.
ISRLC046 Promote failed - The logical record ISRLC061 Promote failed - Member ’aaaaaaaa’ is
lengths are incompatible. not edit locked by user.
ISRLC047 Promote failed - The ″from″ library is ISRLC062 Promote failed - Current user for
not allocated. desired member is ’aaaaaaaa’.
ISRLC048 SVC not installed - The library ISRLC063 Promote failed - Only predefined
management facility SVC is not members can be promoted into this
installed. hierarchy.
ISRLC049 Promote failed - Promote free is invalid. ISRLC064 Promote failed - ’aaaaaaaa’ is the only
Member does not exist. authorized promoter of undefined
members.
ISRLC050 Edit lock failed - Edit lock failed due to Explanation:
an invalid condition on group ’aaaaaaaa’.
ISRLC065 Promote failed - Promote failed due to
ISRLC051 Promote failed - The member is not invalid ″from″ data set organization.
available for update.
ISRLC066 Promote failed - Promote after system
ISRLC052 Promote failed - Authorized promoter failure must be identical to previous
for requested group is ’aaaaaaaa’. promote.
ISRLC053 Dist. table deleted - Distribution table ISRLC067 Member entry not deleted - Member
’aaaaaaaa’ was deleted from the control entry ’aaaaaaaa’ is not a predefined
file. member.
Explanation:
ISRLC054 User-set deleted - User-set ’aaaaaaaa’ was
deleted from the control file.
ISRLC068 Get close out failed - Get close out
failed on the ″from″ library.
ISRLC055 Type deleted - Controls for type
’aaaaaaaa’ were deleted from the control
ISRLC069 Read error occurred - A read error
file.
occurred on the ″from″ library.
ISRLC070 Member not found - The ″from″ library ISRLC084 Invalid user id - Invalid user id for
member was not found. request in the SVC.
ISRLC071 Promote free failed - Member has not ISRLC085 Type queue build failed - Type queue
been edit locked or does not exist. build failed in module ’aaaaaaaa’.
ISRLC072 Project has no groups - Project ’aaaaaaaa’ ISRLC086 Type queue free failed - Type queue
has no promote hierarchies defined. free failed in module ’aaaaaaaa’.
ISRLC073 Invalid hierarchy exists - Group ISRLC087 Hierarchy already deact - Hierarchy is
’aaaaaaaa’ not in a valid hierarchy. Must already deactivated. Deactivate ID is
be corrected first. ’aaaaaaaa’.
ISRLC074 Activity log not valid - Logical record ISRLC088 Hierarchy already deact - aaaaaaaa
length for member log ’aaaaaaaa’ is hierarchy(s) already deactivated. They
invalid. are not deactivated again.
ISRLC075 Promote failed - Authorized promoter or ISRLC089 Bad deactivate IDs - Deactivate IDs,top
user-set for predefined member is ’aaaaaaaa’,inconsistent. Deactivate and try
’aaaaaaaa’. again.
ISRLC076 Multiple distrib tables - Hierarchy with ISRLC090 Not a complete activate - aaaaaaaa
top ’aaaaaaaa’ has more than one dist. hierarchy(s) not activated - they don’t
table defined. belong to user.
ISRLC077 Types are not identical - Hierarchy with ISRLC091 Groups already active - aaaaaaaa
top group ’aaaaaaaa’ does not have hierarchy(s) are already active.
identical types.
ISRLC092 Invalid control block - Invalid control
ISRLC078 Distribution table error - Distribution block - request could not be processed.
table ’aaaaaaaa’ has not been created.
ISRLC093 Invalid hierarchy exists - An invalid
ISRLC079 Group not found - Group found in hierarchy exists, there are no valid
distribution table ’aaaaaaaa’ does not hierarchies defined.
exist.
ISRLC094 Activation failed - Top group ’aaaaaaaa’
ISRLC080 Allocation failed - ″to″ library ’aaaaaaaa’ deleted from hierarchy after ACTIVATE
could not be allocated. command.
Explanation:
ISRLC081 Distribution table error - There are no
groups defined in distribution table
ISRLC095 Change not allowed - Another project
’aaaaaaaa’.
administrator must remove your id.
ISRLC098 STOW failed - STOW failed in module ISRLC113 Exit name required - Data set full exit
’aaaaaaaa’. was requested without specifying exit
name.
ISRLC099 Member not found - Member ’aaaaaaaa’
not found. control file/control lib ISRLC114 Exit type required - Data set full exit
inconsistent. was requested without specifying exit
type.
ISRLC100 Promote failed - Requested version code
not in distribution table ’aaaaaaaa’. ISRLC115 Control file not valid - The control file
is not bound to any started task.
ISRLC101 Library not deleted - Group ’aaaaaaaa’
references the library as a target library. ISRLC116 Control file not valid - The control file
contains controls from a previous
ISPF/PDF version.
ISRLC102 Top group not controlled - Top group
’aaaaaaaa’ could not be found in the
specified library. ISRLC117 Exit name required - Activity log full
exit was requested without specifying
exit name.
ISRLC103 Type not controlled - Type entry
’aaaaaaaa’ could not be found in the
specified library. ISRLC118 Record format not fixed - The activity
log must have a fixed record format.
ISRLC104 Member not controlled - Member
’aaaaaaaa’ could not be found in the ISRLC119 Invalid control file - The old control file
specified library. contains invalid members.
ISRLC105 Promotion successful - ’aaaaaaaa’ was last ISRLC120 Delete failed - Member was not deleted
member successfully processed. because the controlled library is an
alias.
ISRLC106 Promote failed - Record formats of the
″from″ and ″to″ groups are incompatible. ISRLC121 Invalid record format - The LMF control
file record format must be variable
blocked. Dd ISRCFIL
ISRLC107 Activ. log not allocated - Activity log
’aaaaaaaa’ could not be allocated. it may
not be cataloged. ISRLC122 Secondary extents exist - The control file
must not have any secondary extents
allocated.
ISRLC108 Promote failed - ″To″ data set ’aaaaaaaa’
must be allocated as partitioned data
set. ISRLC123 Invalid command - Command is not
valid. The only valid command is END.
ISRLC109 Distribution table error - Group
’aaaaaaaa’ references no distribution ISRLC124 Get closeout failed - Close out of control
table. file failed in module ’aaaaaaaa’.
ISRLC111 Promote failed - ″From″ record length is ISRLC125 Not authorized - You are not authorized
greater than ″to″ block size for record to change a log for project ″aaaaaaaa″.
format U.
ISRLC126 Invalid members found - The new
ISRLC112 Exit type required - Activity log full exit control file must not contain any
was requested without specifying exit members.
type.
ISRLC127 Invalid control file - The old control file ISRLC141 Invalid member controls - Group
is not a valid control file. ’aaaaaaaa’ may have bad member
controls. Activate cannot be done.
ISRLC128 No updates made - No entries were
found which use activity log ’aaaaaaaa’. ISRLC142 Invalid member controls - Use member
utilities options 2 or 4 to correct the
problem.
ISRLC129 Migration successful - Migration of old
control file to new control file was
successful. ISRLC143 Entries in data set - This hierarchy not
valid until problems in output data set
are fixed.
ISRLC130 Data set not allocated - The output data
set could not be allocated by user
’aaaaaaaa’. ISRLC144 Controls cleared - All member controls
for this hierarchy have been cleared.
ISRLC131 Data set LRECL too small - The output
data set LRECL may result in truncation ISRLC145 Verify required - Verify or initialize is
of records. required before hierarchy can be
activated.
ISRLC132 Member list failed - A member list
could not be created for group ’aaaaaaaa’. ISRLC146 Data set not allocated - The output data
set could not be allocated by started
task ’aaaaaaaa’.
ISRLC133 Data set not allocated - Group ’aaaaaaaa’
could not be allocated.
ISRLC147 Data set not opened - Group ’aaaaaaaa’
could not be opened.
ISRLC134 Controlled data set full - A controlled
data set is out of space. See your library
administrator. ISRLC148 Member name required - A member
name is required when a partitioned
data set is specified.
ISRLC135 Control file full - The LMF control file
is out of space. See your library
administrator. ISRLC149 Data set is not a PDS - LMF requires
that group ’aaaaaaaa’ be a partitioned
data set.
ISRLC136 Activity log full - The activity log is out
of space. See your library administrator.
ISRLC150 Delete not allowed - Delete not allowed
on a member whose status is
ISRLC137 Administrator log full - The
″Promote-in-process″.
administrator log is out of space. See
your library administrator.
ISRLC151 Group not found - Use VERIFY
CONTROLS option to determine the
ISRLC138 Write failed - Write failed to output data
problem.
set in module ’aaaaaaaa’.
ISRLC154 Controls cleared - Member controls that ISRLF001 Internal program error - Module
existed for the hierarchy were cleared. ’aaaaaaaa’ received a return code bbbbbbbb
from module ’cccccccc’.
ISRLC155 No controls exist - No member controls
exist to clear in the LMF hierarchy. ISRLF002 Control file LRECL error - An invalid
record length detected in control file
member ’aaaaaaaa’.
ISRLC156 All members not deleted - Not all
physical members were deleted. VERIFY
CONTROLS recommended. ISRLF003 Member not found - Member ’aaaaaaaa’
could not be found in the control file.
ISRLC157 Data set full exit error - LMF services
cannot be issued from the lmf address ISRLF004 Member already exists - Member
space. ’aaaaaaaa’ not created. It already exists in
the control file.
ISRLC158 Lock not allowed - Lock not allowed on
a member whose status is ISRLF005 ZNAMES member not found - The
″Promote-in-process″. ZNAMES member could not be found
in the control file.
ISRLC159 Member ″aaaaaaaa″ in use - Member
″aaaaaaaa″ is in use. The physical ISRLF006 Project member not found - The
member cannot be deleted. ZPROJECT member could not be found
in the control file.
ISRLC160 Member not locked - Project ″aaaaaaaa″
is an SCLM controlled project. ISRLF007 Type member not found - Type member
’aaaaaaaa’ could not be found in the
control file.
ISRLC161 SCLM warning - The project being
updated is an SCLM controlled project. Explanation:
ISRLD000A Messages ISRLD000 through ISRLD049 ISRLF008 Group member not found - Group
have been moved to “Chapter 2. PDF member ’aaaaaaaa’ could not be found in
Messages” on page 203 the control file.
Explanation: The following messages can be found in
“Chapter 2. PDF Messages” on page 203. ISRLF009 Member not found - MEMBER member
v ISRLD000–009 ’aaaaaaaa’ could not be found in the
v ISRLD010–019 control file.
v ISRLD020–029
v ISRLD030–039
ISRLF010 Project not controlled - Project entry
’aaaaaaaa’ could not be found in the
ISRLE000A Messages ISRLE000 through ISRLE029 control file.
have been moved to “Chapter 2. PDF
Messages” on page 203
ISRLF011 Group not controlled - Group entry
Explanation: The following messages can be found in ’aaaaaaaa’ could not be found in the
“Chapter 2. PDF Messages” on page 203. control file.
v ISRLD000–009
v ISRLD010–019
ISRLF012 Type not controlled - Type entry
v ISRLD020–029
’aaaaaaaa’ could not be found in the
control file.
ISRLF000 Control file error - See system
programmer - details in the LMF
ISRLF013 Top group not found - Top group
address space isplog.
’aaaaaaaa’ could not be found in the
control file.
ISRLF014 Hierarchy group missing - Group ISRLF028 Ctl file concatenated - The control file is
’aaaaaaaa’ was not found within the concatenated.
promote hierarchy.
ISRLF029 Ctl file not a PDS - The control file is
ISRLF015 User set does not exist - User set not a partitioned data set.
’aaaaaaaa’ could not be found in the
control file.
ISRLF031 Invalid ctl file length - The control file
must have a record length of aaaaaaaa.
ISRLF016 User set not created - User set ’aaaaaaaa’
not created. The project does not exist.
ISRLF032 Ctl file obtain failed - An obtain failed
while allocating the control file.
ISRLF017 Dist. table not found - Distribution
table ’aaaaaaaa’ was not found in the
ISRLF033 Type not deleted - Type ’aaaaaaaa’ was
control file.
not deleted. It was not found in the
control file.
ISRLF018 Dist. table not created - Distribution
table ’aaaaaaaa’ not created. The project
ISRLF034 Userset member not found - User set
does not exist.
member ’aaaaaaaa’ was not found in the
control file.
ISRLF019 Group not defined - Group ’aaaaaaaa’
does not exist in the promote hierarchy.
ISRLF035 Dist. table member error - Distribution
table member ’aaaaaaaa’ was not found
ISRLF020 Hierarchy is ’active’ - Group ’aaaaaaaa’ in the control file.
must be deactivated before any changes
can be made.
ISRLF036 Not authorized - The project
administrator is ’aaaaaaaa’.
ISRLF021 Target group invalid - Target group
’aaaaaaaa’ could not be found in control
ISRLF037 Type queue failed - aaaaaaaa.
file.
ISRLI000 Internal program error - See system ISRLI015 I/O error on BLDL - I/O error on BLDL
programmer - details in the LMF in module ’aaaaaaaa’.
address space isplog.
ISRLI016 Put close out failed - Put close out failed
ISRLI001 Internal program error - Module in module ’aaaaaaaa’.
’aaaaaaaa’ received a return code bbbbbbbb
from module ’cccccccc’.
ISRLI017 I/O error on STOW - A permanent I/O
error occurred during a STOW in
ISRLI002 Invalid function code - Invalid function module ’aaaaaaaa’.
code. ’aaaaaaaa’.
ISRLI018 Invalid DCB on STOW - DCB either
ISRLI003 Region size too small - Insufficient closed or open for output on STOW in
virtual storage from module ’aaaaaaaa’. module ’aaaaaaaa’.
ISRLI004 Read failed - Read failed on member ISRLI019 Reserve failed - Reserve failed in
’aaaaaaaa’. module ’aaaaaaaa’.
ISRLI005 Read close out failed - Read close out ISRLI020 ENQUEUE failed - ENQUEUE failed in
failed on member ’aaaaaaaa’. module ’aaaaaaaa’.
ISRLI006 Free main storage failed - Free main ISRLI021 Release failed - Release failed in
storage failed in module ’aaaaaaaa’. module ’aaaaaaaa’.
ISRLI007 Put failed - Put failed in module ISRLI022 ENQUEUE/DEQUEUE failed - Invalid
’aaaaaaaa’. parameters passed to ISRLCEDQ.
ENQUEUE or DEQUEUE failed
ISRLI008 Znames member exists - ISRLCOPY
could not create the ZNAMES member. ISRLI023 Control file alloc fail - Invalid open
It already exists. parameter of ’aaaaaaaa’ passed to
ISRLCFAL..
ISRLI009 Close failed - Close failed in
module’aaaaaaaa’. ISRLI024 No directory space - Promote failed for
″to″ library ’aaaaaaaa’.
ISRLI010 Open failed - Open failed in module
’aaaaaaaa’. ISRLI025 Failure in SVC - ACEE control block not
found for batch request.
ISRLI011 No directory space - Member not created
or updated. No directory space for ISRLI026 Failure in SVC - ACEERACF = 0 - user
control file. ID is not defined to racf for batch
request.
ISRLI012 Program error in ISPCDB - Module
’aaaaaaaa’ received a return code of 36 ISRLI027 New statistics invalid - Statistics cannot
from module ispcdb. be updated for data sets with RECFM =
U.
ISRLI013 Bad BLDL return code - A bad BLDL
return code was returned for member ISRLI028 New access ID invalid - Existing owner
’aaaaaaaa’. cannot be determined for data sets with
RECFM = U.
ISRLI014 Obtain failed - Obtain failed for
member ’aaaaaaaa’.
ISRLI060 Internal program error - Invalid action ISRLK009 Member ’aaaaaaaa’ was not found in
’aaaaaaaa’ specified on promote. group ’bbbbbbbb’.
ISRLI061 ″From″ lib not closed - Unable to close ISRLK010 It should have been. member controls
″from″ library ’aaaaaaaa’. exist for it there.
ISRLI062 ″From″ library not freed - ’aaaaaaaa’ ISRLK011 Member ’aaaaaaaa’ was found in group
could not be freed by program ’bbbbbbbb’.
’bbbbbbbb’.
ISRLK012 It should not be found since no member
ISRLI063 Free library error - ’aaaaaaaa’ could not controls exist for it there.
be freed by program ’bbbbbbbb’.
ISRLK013 Member ’aaaaaaaa’ should be moved or
ISRLI064 ″From″ lib not opened - Unable to open deleted from ’bbbbbbbb’.
’″from″’ library ’aaaaaaaa’.
ISRLK014 Member ’aaaaaaaa’ was also found in
ISRLI065 User id - aaaaaaaa - ISRLI065 - ’bbbbbbbb’ group ’bbbbbbbb’.
is the message number of the following
message:
ISRLK015 If member controls are needed use
option 2 of member utilities.
ISRLI066 Format message error - Failure calling
ispcse with message number ’aaaaaaaa’.
ISRLK016 Member ’aaaaaaaa’ was locked in group
’bbbbbbbb’ by user ’cccccccc’.
ISRLK000 Member ’aaaaaaaa’ was edit locked by
’bbbbbbbb’.
ISRLK017 Member ’aaaaaaaa’ was locked in group
’bbbbbbbb’ by user ’cccccccc’.
ISRLK001 The member was in group ’aaaaaaaa’. the
controls are cleared.
ISRLK018 **************** (Member Utilities
Message ’aaaaaaaa’) *********************
ISRLK002 If member ’aaaaaaaa’ is needed in group
’bbbbbbbb’ it should be put there.
ISRLK019 If member controls are not needed
delete or move the member from
ISRLK003 Option 1 or 2 of member utilities can be ’aaaaaaaa’.
used to delete controls if necessary.
ISRLK020 Verify or initialize should then be used
ISRLK004 Controls for member ’aaaaaaaa’ in group to insure that the problem is fixed.
’bbbbbbbb’ are cleared.
ISRLK021 No top group record exists for member
ISRLK005 Controls for member ’aaaaaaaa’ were ’aaaaaaaa’. one is needed.
found for group ’bbbbbbbb’.
ISRLK022 Use the initialize member utility with or
ISRLK006 Controls for member ’aaaaaaaa’ were also without the preserve feature.
found for group ’bbbbbbbb’.
ISRLK023 Statistics for member ’aaaaaaaa’ in
ISRLK007 These groups are in conflicting paths to ’bbbbbbbb’ do not exist or are invalid.
the same top group.
ISRLK024 Statistics are needed for all LMF
ISRLK008 Member ’aaaaaaaa’ must be moved or controlled members.
deleted from one or both of these
groups.
ISRLK025 Use the PDF editor, pdf option 3.5, the ISRLK041 statistics for it.
LMMSTATS service or
ISRLL003 Invalid command - CAN or CANCEL
ISRLK026 Verify should then be used to ensure are the only valid commands.
that the problem is fixed.
ISRLL004 Verify required - Controls created on a
ISRLK027 Member ’aaaaaaaa’ is locked incorrectly group that exists. Verify 8.1.3.4 is
in group ’bbbbbbbb’. required.
ISRLK028 It should be available or edit locked by ISRLL006 Enter required field - Enter required
an updater. It is neither. field at the cursor position.
ISRLK030 Member ’aaaaaaaa’ should be locked ISRLL008 Promoter ID not allowed - Promoter ID
against update. must be blank when no target group is
specified.
ISRLK031 This is only an informational message.
The problem is fixed. ISRLL009 Invalid option - Enter 1, 2 or 3. for
information about the options press the
Help key.
ISRLK032 Duplicate member controls exist for
member ’aaaaaaaa’ in group ’bbbbbbbb’.
ISRLL011 Library not deleted - Controls for library
’aaaaaaaa..bbbbbbbb..cccccccc’ not deleted.
ISRLK033 Use the initialize members utility
without the preserve controls feature.
ISRLL012 Library deleted - Controls for library
’aaaaaaaa..bbbbbbbb..cccccccc’ deleted.
ISRLK034 Member ’aaaaaaaa’ is edit locked
incorrectly in group ’bbbbbbbb’.
ISRLL013 Target group invalid - Target group
cannot be changed. the hierarchy
ISRLK035 Member ’aaaaaaaa’ is available or edit
contains member entries.
locked in a group lower in hierarchy.
ISRLL019 Controls not modified - Controls for ISRLL078 Target group invalid - Library
library ’aaaaaaaa..bbbbbbbb..cccccccc’ not ’aaaaaaaa..bbbbbbbb..cccccccc’ in target
modified. hierarchy uses a dist. table.
ISRLL050 Update in progress - Updates can be ISRLL079 Dist. table error - Distribution table
performed on only one screen. being added to a hierarchy with more
than one entry level.
ISRLL051 ’aaaaaaaa’ not valid - The group must be
a ″top″ group. ISRLL090 No members modified - Member entries
were not created or modified.
ISRLL052 Invalid input - Enter blank, ’*’, or valid
logon id or user set. ISRLL091 Invalid member name - Member name
specified is incorrect.
ISRLL053 Update successful - The data set full
parameters have been successfully ISRLL092 Update not allowed - Hierarchy with top
updated. group ’aaaaaaaa’ is active. update not
allowed.
ISRLL055 Exit name invalid - Exit name must be
up to 8 alphanumeric characters (1st ISRLL093 Command not allowed - Only the ’end’
must be alpha). command is valid from this panel.
ISRLL056 Target group invalid - A ″circular″ ISRLL094 ADMIN not allowed - Libraries with a
hierarchy cannot be defined. group name of ADMIN cannot be
controlled.
ISRLL057 Controls not modified - The data set full
controls were not modified. ISRLL095 ADMIN not allowed - The group name
of ″admin″ cannot be used for a member
activity log.
ISRLL071 Dist. table error - Target library must be
an ″entry″ level library.
ISRLL096 SCLM project updated - The project is
SCLM controlled, but has been
ISRLL072 Dist. table error - Library
successfully updated.
’aaaaaaaa..bbbbbbbb..cccccccc’ already
references a dist. table.
ISRLL170 Update not allowed - Member ’aaaaaaaa’
of type ’bbbbbbbb’ is currently being
ISRLL073 Dist. table error - Dist. table referenced
updated by ’cccccccc’.
at lower level library
’aaaaaaaa..bbbbbbbb..cccccccc’.
ISRLL171 Update not allowed - Member ’aaaaaaaa’
of type ’bbbbbbbb’ is currently being
ISRLL074 Dist. table error - Controlled library
updated by ’cccccccc’.
hierarchy contains more than one
″entry″ level.
ISRLL172 Update not allowed - Member ’aaaaaaaa’
of type ’bbbbbbbb’ must be promoted into
ISRLL075 Dist. table error - Library is not valid
the top group.
with specified target group.
ISRLL190 ’aaaaaaaa’ not deleted - User set ’aaaaaaaa’ ISRLL212 Update not allowed - Group ’aaaaaaaa’
was not deleted. must be deactivated before any changes
can be made.
ISRLL191 ’aaaaaaaa’ saved - User set ’aaaaaaaa’ was
saved. ISRLL213 Update not allowed - Groups from the
same hierarchy cannot be in the same
dist. table.
ISRLL192 ’aaaaaaaa’ saved - Distribution table
’aaaaaaaa’ was saved.
ISRLL300 CLEAR request cancelled - Request to
clear member controls was cancelled by
ISRLL193 ’aaaaaaaa’ not deleted - Distribution table
end command.
’aaaaaaaa’ was not deleted.
ISRLP102 Invalid type - Type must be 1-8 ISRLQ023 Page size too small - List data set lines
alphanumeric characters, the first per page must be at least 16.
alphabetic.
ISRLQ024 Record length too small - aaaaaaaa record
ISRLQ001 FREEMAIN failure - System unable to length must be at least 160.
process a FREEMAIN request.
ISRLQ025 Invalid parameter - Parameter passed
ISRLQ004 Activity log open failed - Open failed from activity and status listings panel is
on activity log ’aaaaaaaa’. see ISPF log invalid.
for details.
ISRLQ026 Read failed - Read from sort file failed
ISRLQ005 Sort failed - External sort program in module aaaaaaaa.
returned an error code of ’aaaaaaaa’.
ISRLQ027 No controlled members - No controlled
ISRLQ006 Listing printed - Listing printed for members exist for the library specified.
controlled library
aaaaaaaa..bbbbbbbb..cccccccc.
ISRLQ028 Member name required - A member
name must be provided when the data
ISRLQ007 Listing printed - Listing printed for set is a PDS.
activity log aaaaaaaa..ADMIN.ACTLOG.
ISRLQ029 Data set is sequential - A member name
ISRLQ008 Data set created - Data set created for is not permitted for a sequential data
control library aaaaaaaa..bbbbbbbb..cccccccc. set.
ISRLQ009 Data set updated - Data set updated for ISRLQ030 Member not controlled - Controls for
control library aaaaaaaa..bbbbbbbb..cccccccc. member ″aaaaaaaa″ not found in
specified library.
ISRLQ012 Open outlist failed - Open failed on
outlist file ’aaaaaaaa’. ISRLQ031 Configuration error - Record length for
control status is too short in
configuration table.
ISRLQ015 Outlist close out failed - Unable to
perform clean up on outlist file
’aaaaaaaa’. ISRLQ033 Enter required field - Activity log group
name is a required field.
ISRLQ016 Write failed - Write to outlist data set
failed in module ’aaaaaaaa’. ISRLQ034 Log group name error - Activity log
group name must be a valid ISPF
″group″ name.
ISRLQ017 Read failed - Read failed on activity log
data set.
ISRLS000A Messages ISRLS000 through ISRLS219
have been moved to “Chapter 2. PDF
ISRLQ020 Listing print failed - Print to list file
Messages” on page 203
failed, see details in list file.
Explanation: The following messages can be found in
“Chapter 2. PDF Messages” on page 203.
ISRLQ021 Listing has no members - Listing
v ISRLS000–009
produced, member: ’aaaaaaaa’ not found.
v ISRLS010–019
v ISRLS020–029
ISRLQ022 Listing has no members - Listing v ISRLS030–039
produced, no members were found for v ISRLS040–049
the library specified. v ISRLS050–059
v ISRLS060–069
v ISRLS070–079
v ISRLS080–089
v ISRLS090–099
ISRLS289 Gen load failed - LMREVIEW - Gen ISRLT008 Duplicate found - Duplicate table rows
load of ISRLALIN failed. exists. Make changes before saving.
ISRLS290A Messages ISRLS290 through ISRLS499 ISRLT009 Invalid parameter length - Parameter for
have been moved to “Chapter 2. PDF LOCATE command cannot be more than
Messages” on page 203 8 characters.
Explanation: The following messages can be found in
“Chapter 2. PDF Messages” on page 203. ISRLT010 ’aaaaaaaa’ found - ’aaaaaaaa’ is located,
v ISRLS290–299 and appears on the first line.
v ISRLS300–309
v ISRLS310–319
ISRLT011 Delete not allowed - A member with
v ISRLS320–329
delete status of ″I″ is within range of a
v ISRLS330–339
DELETE command.
v ISRLS340–349
v ISRLS350–359
v ISRLS360–369 ISRLT012 Line command invalid - The numeric
v ISRLS370–379 portion of the line command must be
v ISRLS440–449 greater than zero.
v ISRLS450–459
v ISRLS460–469
v ISRLS470–479 ISRLU000 No members in data set - The PDS
v ISRLS480–489 specified contains no members.
v ISRLS490–499
ISRLU001 Data set aaaaaaaa - To data set bbbbbbbb.
ISRLT000 Invalid primary command - ’aaaaaaaa’ is
not a valid command. ISRLU002 Not entry level library - ’To ISPF
library’ must be an entry level
ISRLT001 Enter LOCATE parameter - Enter the controlled library.
argument to be located.
ISRLU003 Library is deactivated - Control library
ISRLT002 Parameter not allowed - No parameter is must be activated before promotion can
allowed for the CANCEL command. be done.
ISRLT003 Too many parameters - Too many ISRLU004 Error on member list - Severe error
parameters are defined for this creating member list.
command.
ISRLU005 Free error - Severe error freeing input
ISRLT004 Command not recognized - Valid line data set.
commands are: I (insert), D (delete), R
(repeat). ISRLU006 Close error - Severe error closing input
data set.
ISRLT005 Command conflict - ’aaaaaaaa’ is within
range of the D command. Correct either ISRLU007 Invalid name - Reenter a valid name at
one. cursor location.
ISRLT006 ’aaaaaaaa’ not found - ’aaaaaaaa’ not ISRLU008 Required field - Enter a valid name at
located. cursor location.
ISRLT007 Delete not allowed - Member has a ISRLU009 Not a controlled library - ’To ISPF
delete status of ″I″. library’ must be a controlled library.
ISRLU011 Data set not aaaaaaaa - Data set was not ISRLU028 Promotion error - Multiple messages
processed for promotion. previously displayed.
ISRLU012 Close error - Cannot close control files. ISRLU029 ’To’ lib not cataloged - ’aaaaaaaa’ was not
found in catalog.
ISRLU013 aaaaaaaa member bbbbbbbb - to data set
cccccccc. ISRLU030 Write variables failed - Write variables
to shared pool for promote failed.
ISRLU014 aaaaaaaa members bbbbbbbb - to data set
cccccccc. ISRLU031 Promotion not allowed - Promotion user
exit validation failed.
ISRLU015 FREEMAIN error - Cannot FREEMAIN
control files storage. ISRLU032 aaaaaaaa bbbbbbbb - cccccccc(aaaaaaaa)
bbbbbbbb successfully
ISRLU016 No members aaaaaaaa - No members
were processed for promotion. ISRLU033 Severe error occurred - Module aaaaaaaa
received a return code bbbbbbbb from
module cccccccc.
ISRLU017 Severe error from service - Severe error
defining ISPF dialog variables.
ISRLU034 Print failed - Print request failed. list
data set may have more details.
ISRLU018 Severe error from service - Severe error
deleting ISPF dialog variables.
ISRLU035 Open failed - I/O error occurred trying
to open ’from’ data set for input.
ISRLU019 Member aaaaaaaa bbbbbbbb - Member
’aaaaaaaa’ is now bbbbbbbb to data set
’cccccccc’. ISRLU036 Delete failed - I/O error occurred trying
to open ’from’ data set for output.
ISRLU020 Invalid select code - Type ’s’ for select
or ’b’ for browse in front of the member ISRLU037 Delete failed - Permanent I/O error.
desired.
ISRLU038 Delete failed - Data control block is not
ISRLU022 Invalid newname - Newname field open or is open for input.
contains an invalid member name.
ISRLU039 Delete failed - Insufficient virtual
ISRLU023 Member not found - Selected member is storage is available to perform STOW
not available for promotion. function.
ISRLU024 BLDL error - Severe error performing ISRLU040 Open failed - Open failed for selected
BLDL on selected member. member.
ISRLU025 Cannot use ’top’ library - ’From’ library ISRLU041 Region size too small - Insufficient
cannot be a ’top’ or ’only’ library. virtual storage to perform BLDL.
ISRLU026 Data set aaaaaaaa - bbbbbbbb aaaaaaaa ISRLU042 Program error in ISPCDB - Module
successfully ISRLUPR22 or isrluprs received a return
code of 36 from module ispcdb.
ISRLU043 Bad BLDL return code - A bad BLDL ISRLU059 Unable to lock member - Member
return code was returned from module ″aaaaaaaa″ exists at a lower level of the
ispcdb. hierarchy.
ISRLU044 Obtain failed - Obtain failed for BLDL ISRLU060 Unable to lock member - Member
on selected member. ″aaaaaaaa″ exists at a lower level.
bbbbbbbb members copy/locked.
ISRLU045 I/O error on BLDL - I/O error on BLDL
for selected member. ISRLU061 Severe error - see log - Copy and lock
failed for member ″aaaaaaaa″. See log for
details.
ISRLU046 Promotion failed - Cannot promote from
password protected data set.
ISRLU062 Member already locked - Member
″aaaaaaaa″ locked by ″bbbbbbbb″.
ISRLU047 After exit failed - Member promoted.
Copy/lock completed for cccccccc
Exit after promotion failed.
members.
This section explains the SuperC message format and the messages you may
receive.
Message Format
ISRSnnns
where:
ISRS is the program identifier for SuperC
nnn represents a particular message number
s is the message severity level:
I Informational message
W Warning message
E Error message
ISRS034W CMPCOLM STMT(S) HAS TOO MANY ISRS038W SRCHFORC MUST BE PRECEDED BY
RANGES. ONLY FIRST 15 RANGES A VALID SRCHFOR /SRCHFORC
WILL BE USED. STATEMENT. STATEMENT REJECTED.
Explanation: More than the permitted maximum of 15 Explanation: The SRCHFORC process statement is a
ranges/individual columns specified for the continuation of the preceding SRCHFOR (or
CMPCOLM process statement. Extraneous information SRCHFORC) statement and therefore must always be
ignored. preceded by one of those statements.
System Action: The SuperC run continues. System Action: The SuperC run continues.
Programmer Response: Limit ranges/individual Programmer Response: Ensure the first “search”
columns to a maximum of 15 for each run of SuperC. statement is a SRCHFOR followed, if necessary, by a
Additional ranges/individual columns can be specified SRCHFORC statement containing “continuation”
in a separate run. information.
Refer:
ISRS035W INVALID CHANGE TEXT Process Statements in the SuperC Appendix of the
COMBINATION OF NEW TEXT > OLD User’s Guide
TEXT AND LINE LENGTHS > 256
ATTRIBUTE.
ISRS039W ONLY ONE GROUP OF FILES OR
Explanation: The length of the search text in a MEMBERS MAY BE PROCESSED
NCHGT or OCHGT process statement can not be USING SELECTF STATEMENTS.
greater than the length of the change text when a STATEMENT REJECTED.
record is greater than 256 characters.
Explanation: SelectF does not allow multiple wildcard
System Action: The SuperC run continues. selection (except when used for filemode).
Programmer Response: Correct process statement. System Action: The SuperC run continues.
Programmer Response: Correct process statement.
ISRS057E THE INPUT FILES/DATA SETS COULD ISRS062E UPDATE FILE/DATA SET, DELDD,
NOT BE PROCESSED. BOTH MUST MISSING OR INCOMPATIBLE
BE SEQUENTIAL OR A WHOLE ATTRIBUTES/LRECL FOR
PDS/MACLIB. PDS/MACLIB. UPDATE OPTIONS
CANCELLED.
Explanation: Cannot compare a
PDS/MACLIB/TXTLIB/Librarian with a sequential Explanation: Update/delta file requested but there is
file/dataset. no assignment for it.
System Action: The SuperC run terminates. System Action: The SuperC run terminates.
Programmer Response: Ensure input files are Programmer Response: Refer to your systems
comparable. programmer.
System Action: The SuperC run continues (without Explanation: A Y2PAST process statement has been
this member). used but there are no accompanying Year 2000 Date
Definition process statements.
Programmer Response: Inspect output listing for
further details. System Action: The Y2PAST process option is ignored.
The SuperC run continues.
ISRS070W REQUEST FOR WIDE OPTION NOT Programmer Response: Check that you are using the
SUPPORTED BY SYSLST. NARROW Year 2000 process statements correctly. Either the
OPTION WILL BE SUBSTITUTED. Y2PAST process statement should be removed—or one
or more date definition process statements should be
Explanation: The WIDE process option requires a included.
printing device capable of printing lines up to 202
characters long. The 55-character side-by-side Refer:
NARROW option has been used instead. Process Statements in the SuperC Appendix of the
User’s Guide
System Action: The SuperC run continues.
Programmer Response: Refer to your systems ISRS074W FOCUS/EXCLUDE PROCESS
programmer. STATEMENTS ARE IGNORED WHEN
USING THE Y2DTONLY PROCESS
ISRS071W SIDE BY SIDE LISTINGS NOT OPTION.
ALLOWED WHEN USING COLHEAD Explanation: NFOCUS, OFOCUS, NEXCLUDE, and
PROCESS STATEMENT. OEXCLUDE process statements have no effect when
Explanation: The NARROW process option cannot be the Y2DTONLY process option is used.
used with the COLHEAD process statement. System Action: The FOCUS/EXCLUDE process
System Action: The COLHEAD statements are statements are ignored. The SuperC run continues.
accepted and the NARROW (side-by-side) process Programmer Response: Check that you are using the
option is ignored. The SuperC run continues. correct process options and statements.
Programmer Response: Check that you are using the Refer:
correct process options and statements. Process Options in the SuperC Appendix of the
Refer: User’s Guide
Process Options in the SuperC Appendix of the Process Statements in the SuperC Appendix of the
User’s Guide User’s Guide
Process Statements in the SuperC Appendix of the
User’s Guide
At termination, ISPF copies the value from ZISPFRC and passes it to the invoking
application (or Terminal Monitor Program) in register 15. If the value in ZISPFRC
is not within the valid range or is otherwise not valid, such as a value that is not
numeric, ISPF issues an appropriate line message and passes a return code of 908.
If the dialog has not set ZISPFRC to a value, ISPF returns a value of 0.
Notes:
1. CLIST procedures that invoke ISPSTART can check the CLIST variable LASTCC
for the ISPF return code. In REXX, check the variable rc after an ISPF function.
2. Even though ISPF restricts the return code value to the range 0 to 16777215,
other products or subsystems, such as JES when processing JCL condition
codes, can be more restrictive on return code values. See documentation for the
affected product for more information.
3. ZISPFRC should not be confused with the normal dialog return code set by the
function; it has no effect on ISPF log/list termination processing.
ISPF checks for the existence of ZISPFRC only at ISPF termination. If ZISPFRC is
set by any dialog other than the one invoked by the ISPSTART command, ISPF
ignores the value.
ISPF issues a line message that indicates which of these errors caused the
998 return code.
999 ISPF environment not valid. A 999 error code can result from:
v TSO/MVS environment not valid
v Unsupported screen size
ISPF issues a line message that indicates which of these errors caused the
999 return code.
Diagnostic Information
This section is intended to help you gather information in order to diagnose ISPF
problems.
You can issue the ENVIRON command at any time during an ISPF session.
[TERMTRAC [ON|ERROR|DUMP|OFF]]
[TERMSTAT [QUERY]]
With ENBLDUMP active, even when ISPF is not running in TEST mode,
abnormal termination of a subtask results in a dump being taken and control
being returned to TSO. ISPF execution is not resumed.
Prior to using the TERMTRAC option, you must define to ISPF the ddname for
the data set to be used for the SNAP macro, which ISPF invokes to provide
data stream dumps. The ddname can be defined by specifying it on the panel
displayed as a result of either issuing the ENVIRON command with no
parameters, or selecting the Environ settings... choice from the Environ
pull-down on the ISPF Settings panel. You must follow the data set
The terminal data stream buffer used for ENVIRON TERMTRAC data
collection is not reset to zeroes.
Data stream.
TPUTNER
‘TPUTNER ’ –return from noedit TPUT macro. 4-byte pointer to
previous entry. General purpose register 15:
R15 = TPUT return code
PUTLINE
‘PUTLINE ’ –prior to issuing the PUTLINE macro. 4-byte pointer to
previous entry 12-byte PUTLINE parameter block:
Control flags (2 bytes)
2-byte TPUT options field
4-byte address of message
4-byte address of format-only line
If your terminal is one that supports extended data streams, such as an IBM
3279, but is connected to a non-EDS port, you can issue ENVIRON TERMSTAT
QUERY to force ISPF to return information from list C. Be aware that if you
issue ENVIRON TERMSTAT QUERY, and your terminal is not a type that
supports extended data streams, such as the IBM 3277, you will receive an
ORDER STREAM CHECK error.
Error Recovery
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * ISPF processor ended abnormally * *
* * * *
* * * *
* * Reason code * *
* * * *
* * * *
* * * *
* * NOTE: The ABEND and REASON codes displayed above are * *
* * HEXADECIMAL values for "SYSTEM" abends and DECIMAL * *
* * values for "USER" abends. * *
* * * *
* * Enter HELP command for list of common ABEND codes. * *
* * Press ENTER key for additional DIAGNOSTIC information. * *
* * Enter END command to display primary option menu. * *
* * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Command ===> _________________________________________________________________
F1=Help F2=Split F3=Exit F9=Swap F12=Cancel
If you are not running in an MVS/XA environment, the reason code will be blank.
If you are running in an MVS/XA environment and the SDWA (System Diagnostic
Work Area) Reason Code is not supplied, that is, the SDWA reason code flag bit is
If you enter HELP, the panel shown in Figure 3 displays a list of the common
abend codes.
To return to the Error Recovery panel, enter end from the Common ABEND panel.
If you press Enter from the Error Recovery panel, the panel shown in Figure 4 on
page 594 is displayed:
Register content:
R0 00806000 R1 80806000 R2 000526E0 R3 0009DDA0
R4 00000058 R5 008FD568 R6 008C7850 R7 000526E0
R8 0009DD30 R9 008C7850 R10 81005342 R11 00000C00
R12 00000000 R13 008C7850 R14 810056C6 R15 0000001C
Entry point, PSW, and register values are in hexadecimal. Abend code and reason
code are in hexadecimal for system abends and in decimal for user abends.
Meanings for the entries on the Additional Diagnostic Information panel are:
Abend code
Abend completion code, identified on the panel as “user” or “system”.
Reason code
Component reason code or return code associated with the abend.
ISPF Release Level
ISPF version/release/modification level.
Module Name
Name of abending program or *NOT SPECIFIED* if no name is available.
Entry Point Address
Entry point address of abending program.
PSW Program-Status Word at time of error.
Register content
General Purpose register content at time of error.
If the Recovery Termination Manager (RTM) could not get storage for the System
Diagnostic Work Area (SDWA) or an error occurred within the error routine, all
fields on this panel will contain 0’s, with the exception of the abend code and ISPF
release level. Those fields will contain the correct data.
You can enter the HELP command from this panel as well to display the list of
common abend codes. Information associated with an abend is available from the
ISPF log file.
Pressing the END function key returns you to the primary option menu.
Messages
v IKJ56500I COMMAND NOT FOUND
I/O error messages cannot be issued when there is a problem with the ISPMLIB
concatenation since messages cannot be located due to the I/O error. Message
CMG999 occurs when there is an I/O error due to an ISPMLIB concatenation
problem.
v CMG999
CMG999 is issued with an appropriate description of the error condition for any
problem with accessing a message. Refer to ISPF Dialog Developer’s Guide and
Reference for further information on how to define a message.
Unexpected Output
v ISPF services do not pick up updated copies of messages or panels.
When not in TEST mode, the most recently accessed panel and message
definitions are retained in virtual storage for performance reasons. If you have
modified a panel or message file, using TEST mode ensures that the latest copy
of each message or panel is accessed. Refer to ISPF Services Guide for more
information on executing ISPF in TEST mode.
v ISPF commands such as WINDOW, COLOR, CUAATTR, EXIT, CANCEL,
ACTIONS, KEYSHELP, KEYLIST, EXHELP, FKA, and ISPDTLC are not
recognized as valid commands, or function keys defined as these commands do
not function properly.
The user issuing these commands or pressing the function keys defined as these
commands has a private copy of ISPCMDS in the ISPTLIB concatenation. The
user’s private copy of ISPCMDS is missing some or all of the new commands
supplied in the new command table, ISPCMDS, shipped with ISPF.
Users experiencing this problem should either replace their private copy of
ISPCMDS with the ISPF supplied copy, or update their private ISPCMDS with
the missing commands.
Under normal conditions (that is, when processor and controller dumps have not
been requested by specifying the ISPSTART TEST command):
The controller and processor tasks issue the ABEND system service and allow
dumps under certain situations. The ISPF modules that issue ABENDs and their
associated codes and reasons are listed below:
ABEND0C1 in various common ISPF subroutines
In several ISPF modules, an invalid operation code of (X’00’) is executed to
force an abend at the point that an unexpected condition occurs. Contact
IBM support if this condition occurs within an ISPF module.
ABEND0C4 in ISPDVCGT, ISPDVCPT, or ISPDVCFD
These abends are often caused by mismatched VDEFINE and VDELETE
services in a user’s program. The VDEFINE service gives ISPF
addressability to user storage. This storage is used by variable services any
time the variable that has been established by the VDEFINE service is
referenced. If this storage is released back to the system, an ABEND0C4
may occur depending on whether the storage is still accessible. Following
are two common scenarios that often show these abends:
v A program establishes a variable in a called subroutine using the
VDEFINE service and subsequently uses an ISPF service that references
this variable in another routine. If the called subroutine was dynamically
loaded and therefore released its storage, an ABEND0C4 could occur
when the subroutine references a VDEFINEd variable.
v A program establishes a variable in a called subroutine using the
VDEFINE service and then calls another program without using the
SELECT service. Then the called program VDEFINEs a variable with the
same name, but does not VDELETE it on exit. If the calling program
references that variable after the called program returns control to it, an
ABEND0C4 can occur. Since a VDELETE has not been done, ISPF
services still reference the variable VDEFINEd by the called program.
If the program intent is to use the same variable in the main and called
routines, the variable should be VDEFINEd only in the main routine. If the
program intent to isolate a variable to be used only in the routine in which
it is VDEFINEd, then the program should also VDELETE the variable
before it ends. To diagnose whether the user application has this problem,
a function trace on VDEFINE, VDELETE, and the SELECT services (Option
7.7.1) is very helpful.
Abend codes 111 or 222
To produce these abends, the user must be in test mode and request
processor dumps by entering one of the following commands on the ISPF
command line. With exception of the user completion code, both
commands function in the same manner.
ABEND
Terminates ISPF with user completion code 111.
Usually when an abend occurs within ISPF code, register 12 points to the entry
point of the abending CSECT.
If you are not in TEST mode, split the screen, enter option 7, Dialog Test, and swap
back to the screen containing the error.
You can use the either of the following methods to get the message ID:
v Enter print on the panel displaying the error message. The message ID, along
with the displayed message text and screen output, appears in the LIST data set.
The LIST data set can be printed using the LIST command.
v With the short message displayed:
1. Press the function key assigned to Help (default is F1) or type help on the
command line. This displays the long message text for the error.
2. Press the function key assigned to Help or type help on the command line
once more to display the Tutorial panel associated with the error. The bottom
lines of the Tutorial panel contain fields that list the current panel name, the
previous panel name, and the message ID. The value following LAST MSG= is
the message ID associated with the error.
Problem:
New levels of code residing in STEPLIB do not appear to be executed. This
includes changes to customer applications, new levels of code, and changes
made by PTFs, for example.
Cause: This problem can occur when internal LINKS and LOADs are used in
conjunction with the ISPF ISPLLIB DCB.
Solution:
When using STEPLIB to test new maintenance, releases, or versions of
products and an ISPLLIB is allocated, data sets allocated to STEPLIB
should also be allocated to ISPLLIB.
Problem:
Abends occur when invoking or exiting HELP, KEYS, or ISPPREP.
Cause: An older level of ISPF exists in LPA or LINKLIB; an ISPLLIB or STEPLIB is
used to allocate libraries for the new release of ISPF; and a LIBDEF for
ISPLLIB that does not include the new level of ISPF libraries has been
issued.
Not all of ISPF is loaded at initialization, for example, ISPTUTOR is linked
when HELP is requested. The LIBDEF of ISPLLIB results in the older level
of any modules that are not loaded on ISPF entry to be picked up from
LPA or LINKLIB due to internal search orders. For further information,
refer to the LIBDEF command in ISPF Services Guide
Solution:
Include the new level of ISPF in any LIBDEFs issued for ISPLLIB.
Problem:
ABEND806 for ISPLINK or ABEND0C1 in user application.
Cause: During installation, the SMP/E install logic for ISPF deletes the existing
ISPLINK load module.
Solution:
Relink-edit ISPLINK to user application.
Problem:
Abends in load modules IGC0009C and IGC0009D.
Cause: Failure to install ISPF in the same zone as TSO/E will result in the
supplied ISPF SVC 93 and SVC 94 exits (ISPSC93, ISPSC94), creating SVC
93 and SVC 94 load modules without the proper link edit information.
Failure to use the correct version of either IGC0009C or IGC0009D or both.
Solution:
TSO/E, ISPF, and ISPF/PDF must all be installed in the same zone. Verify
that the correct versions are copied from a test system to the production
system.
Problem:
ISPP150 PANEL ’name’ ERROR NO ″)END″ FOUND BEFORE REACHING
END OF FILE
or
Problem:
ISPF Version 3 specific commands such as WINDOW, COLOR, CUAATTR,
EXIT, CANCEL, ACTIONS, KEYSHELP, KEYLIST, EXHELP, FKA, and
ISPDTLC are not recognized as valid commands or function keys defined
as these commands do not function properly.
Problem:
Receiving error messages such as: ’PROFILE TABLE NOT FOUND,
UNABLE TO ACCESS ISRPROF TABLE FOR VAR ’ZERRMSG’’ or
ABEND3E7 or ABENDU999.
Cause: The profile data set may run out of directory space as Version 3 adds more
members to the profile, or the logon allocation of ISPTLIB may be pointing
to an old Version 2 or Version 3 table library. Another common cause of
this symptom is that an application that link-edits the ISPF load module
ISPTASK into it has not been relink-edited after installing a new version of
ISPTASK.
Solution:
Add more directory blocks to the profile data set and ensure that the
Version 4.1 table library containing ISPKEYS is in the ISPTLIB
concatenation. Verify that the application that link-edits ISPTASK is
relink-edited after a new release of ISPF is installed or after maintenance
that updates ISPTASK is installed.
Problem:
Attempting to start an ISPF session with a workstation connection using
ISPF Client/Server gets error messages such as: CSV003I REQUESTED
MODULE LSCSIO NOT FOUND. +LSCX012 UNABLE TO LOAD
RUNTIME I/O ROUTINES, EXECUTION CANNOT CONTINUE.
Cause: Library SISPSASC is not in the normal MVS load module search order.
This library is NOT searched using the ISPLLIB allocation. It must be in
STEPLIB or LNKLST.
Solution:
Put the SISPSASC library in STEPLIB or LNKLST. For more information
about SISPSASC, refer to the ISPF Planning and Customizing manual.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non_IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to the IBM
Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY
10504–1785, USA.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries in writing to
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, and service names may be trademarks or service marks
of others.
Overall, how satisfied are you with the information in this book?
How satisfied are you that the information in this book is:
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you.
Name Address
Company or Organization
Phone No.
___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
GC28-1326-04 IBMR Along Line
_ _ _ _ _ _ _Fold
_ _ _ and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
IBM Corporation
Software Reengineering
Department G7IA / Bldg 503
Research Triangle Park, NC
27709-9990
_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
GC28-1326-04 Along Line
IBMR
GC28-1326-04