Messages for the Debug Tool for z/OS
These are the messages that pertain to the Debug Tool for z/OS® in Rational Developer for System z.
CRRDG1001E
Source file not found.
CRRDG1002I
To add a new source lookup path location, click the button below.
CRRDG1003E
Source file {0} was not found.
CRRDG1010E
Selection already on source lookup path.
CRRDG1011E
Invalid selection.
CRRDG1012E
Error occurred.
CRRDG1013E
Selection must be a jar or zip.
CRRDG1014E
Selection must be a folder.
CRRDG1015E
Selected project is closed.
CRRDG1016E
Unable to add source location to lookup path.
CRRDG1017E
Unsupported action.
CRRDG1018E
Could not save launch configuration.
CRRDG1019E
Unable to initialize source location.
CRRDG1020W
More than one source was found for '{0}'.
Explanation
- {0}
- The name of a source file
CRRDG1030E
Variable name cannot contain the '=' character
CRRDG1031E
Variable name is already defined
CRRDG2001E
Value must be an integer between {0} and {1}
CRRDG2002E
Value must be an integer between the current pace value and {0}
CRRDG2003E
Value must be an integer between {0} and the maximum pace value
CRRDG2201E
"{0}" is not a valid group for this layout.
CRRDG2202E
The group named "{0}" is reserved and cannot be used.
CRRDG2203E
Unable to build map from {0}: address is of mixed endianness.
CRRDG2204E
Unable to open {0}: the file no longer exists.
CRRDG2211E
File {0} could not be opened.
CRRDG2212E
File {0} could not be parsed.
CRRDG2213E
File {0} has an incorrect layout format.
CRRDG2214E
Invalid Hex Value
CRRDG2222E
An incorrect layout format was encountered while building layout elements.
CRRDG2223E
Bit {0} does not belong to a valid Bit Mask Field
CRRDG2224E
Specified length of layout is incorrect
CRRDG2225E
This element is out of the bounds of the layout:
CRRDG2227E
Unable to retrieve all the bytes from address 0x{0}
CRRDG2228E
Failed to build memory map:
CRRDG2229E
Unable to create memory map:
CRRDG2230E
Failed to edit the selected field:
CRRDG2231E
Directory {0} does not exist.
CRRDG2232E
Set Directory Failed
CRRDG2233E
Unable to set to the specified directory.
CRRDG2234E
Unable to refresh the base address of the memory block.
CRRDG2241E
The memory map cannot be copied to the clipboard.
CRRDG2251E
The group name is reserved and cannot be used:
CRRDG2252E
The group already exists:
CRRDG2253E
Error adding group:
CRRDG2254E
Unable to save file:
CRRDG2255E
File(s) already exist:
CRRDG2256E
Export map file failed.
CRRDG2261E
Minimum block size must be greater than 256 and less than the maximum.
CRRDG2262E
Maximum block size must be less than {0} and greater than the minimum.
CRRDG2263E
Block sizes must be valid integers
CRRDG2271E
Unable to continue expanding the map
CRRDG2272E
Could not continue full expansion because of the following error:
CRRDG2273W
Note: Due to this error, the Find dialog may not contain all the elements in the map.
CRRDG2281E
Cannot export {0} because you do not have write permissions for this file.
CRRDG2282W
This rendering shares one or more files with other renderings. If the following files are overwritten, those renderings will be affected. {0} Continue?
CRRDG2283E
You cannot edit groups or descriptions because the file {0} is read-only.
CRRDG2284E
Malformed offset: offset must be a positive integer.
CRRDG2285E
Malformed offset: absolute offsets must be a positive integer.
CRRDG2286E
Specify an org element, offset, or '*none'. The offset must evaluate to an integer >= 0.
CRRDG2287E
Expression {0} does not evaluate to a positive offset.
CRRDG2291E
The selected element instance does not support memory mapping
CRRDG3001E
Communications failure
CRRDG3002E
Connection with the debug engine was lost
CRRDG3003W
Connection to engine was terminated by user
CRRDG3004W
The program has been terminated.
CRRDG3011E
Source file {0} was not found.
CRRDG3012E
The source file {0} was found by an unsupported source container type and cannot be displayed by this editor. The result of this source lookup was an object of type {1}
CRRDG3013E
Unsupported action.
CRRDG3021W
Request not supported.
CRRDG3031E
File {0} could not be opened
CRRDG3041E
Base address not set
CRRDG3042E
Length requested not supported
CRRDG3043E
Invalid address
CRRDG3044E
Unable to retrieve memory contents
CRRDG3045E
Unable to write changes to memory
CRRDG3046W
Memory operations are not supported by this debug engine
CRRDG3047E
Invalid parameters used to request memory
CRRDG3048E
Location for address expression is invalid
CRRDG3049W
Enhanced memory support not available
CRRDG3050E
Unable to convert expression to address
CRRDG3060E
Failed to register the breakpoint '{0}' with the client breakpoint manager.
CRRDG3061W
Engine is busy.
CRRDG3062E
Request to engine failed.
CRRDG3063E
Unsupported debug engine. Connection terminated.
CRRDG3064E
The debug engine reported an error, but no error message text was provided. The error return code was {0}
CRRDG3065E
Debug engine failed to start.
CRRDG3066W
Debug engine is terminated.
CRRDG3067I
The program {0} was not compiled with debug information.
CRRDG3071E
Invalid library name.
CRRDG3072E
Invalid address or expression.
CRRDG3073E
Invalid program location.
CRRDG3074E
Invalid line number.
CRRDG3075E
Invalid resource specified. Check that the project and source names are correct.
CRRDG3076E
Macro "{0}" not found.
CRRDG3077E
Function or entry point must be specified.
CRRDG3078E
Invalid address or expression.
CRRDG3079E
Invalid number of bytes monitored. Enter a positive integer value.
CRRDG3080E
No debug session available.
CRRDG3081E
From must be an integer greater than or equal to 1
CRRDG3082E
To must be an integer greater than or equal to From
CRRDG3083E
Every must be an integer between 1 and (To - From + 1)
CRRDG3091W
A compiled language debug target must be selected to use this function.
CRRDG3102E
Continue waiting for the engine to respond?
CRRDG3103E
The Compiled Language Debugger was unable to contact the local debugger engine on port {0}. Retry?
CRRDG3111W
More than one launch configuration exists for the debugger program name: {0} Select which configuration to use for this debugging session:
Explanation
- {0}
- The name of the program that you are debugging
CRRDG3112W
Launching this launch configuration type directly is not supported. Start your program from the remote system and connect to this workstation, and this launch configuration will be used if the program name matches the program name launched by the remote system.
CRRDG3113E
Daemon failed to start.
CRRDG3114E
The process ID is not a positive integer.
Explanation
The process ID must be a positive integer.
User response
Specify a process ID that is a positive integer.
CRRDG3115E
The process ID is not valid.
CRRDG3121E
The selection in the Debug view is either not valid or has terminated.
CRRDG3122E
An error was encountered in getting the register name.
CRRDG3123E
An error was encountered while opening the Monitors view.
CRRDG3124I
No block of text is selected.
Explanation
A block of text must be selected to evaluate.
User response
Select a block of text to evaluate.
CRRDG3125E
The line number {0} returned by the editor is not valid.
CRRDG3126E
The selection in the Debug view is either not valid or has terminated.
CRRDG3127E
The expression could not be monitored, because an unknown editor input was encountered.
CRRDG3128E
The editor for this action could not be found.
CRRDG3129E
This file could not be linked to an existing debugging session.
CRRDG3130W
No block of text is selected.
Explanation
A block of text must be selected to evaluate.
User response
Select a block of text to evaluate.
CRRDG3131E
The selection in the Debug view is either not valid or has terminated.
CRRDG3132E
The editor for this action could not be found.
CRRDG3135I
Multiple monitors are available for this selection.
CRRDG3136E
The selected expression is not valid.
CRRDG3137E
Failed to monitor the given expression.
CRRDG3138E
The selected expression is too long. It exceeds {0} characters.
Explanation
- {0}
- Number of characters
The maximum length is
{0} characters.
User response
Select an expression whose length does not exceed
the limit.
CRRDG3141W
{0} already exists. Do you want to replace it?
Explanation
- {0}
- The name of the text file that you have chosen to export the console
text into
You can export the contents of the Debug Console
view. If you try to export to an existing file, you get this message.
User response
If you want to overwrite the existing file, choose Yes;
otherwise, choose No.
CRRDG3151W
Debugger information could not be obtained for this source file.
CRRDG3161E
The string was not found.
CRRDG3162E
Function or entry point not found
CRRDG3163E
Procedure not found
CRRDG3164W
Feature not supported
CRRDG3171E
This source file does not support any alternate views.
CRRDG3172E
An error occurred while populating the editor with line content.
CRRDG3181E
A temporary directory was not found.
CRRDG3201E
A function was not found.
Explanation
The requested breakpoint entry function was not found.
User response
Specify another breakpoint entry function.
CRRDG3202E
Request cannot succeed from this location.
CRRDG3211W
This change to the source search path for the debugger engine will not take effect until the debugger session has been restarted.
CRRDG3240E
Invalid user id
CRRDG3241E
Invalid password
CRRDG3250W
Number of source file lines does not match debug information. File content may not be correct.
CRRDG3311E
The contents of the "{0}" field are not recognised as a number.
CRRDG3312E
In the range the "{0}" value is not less than or equal to the "{1}" value.
Explanation
- {0}
- The first value in the specified range
- {1}
- The second value in the specified range
The range must be specified such
that the {0} value is less than or equal to the {1} value.
User response
Specify a range such that the {0} value is less than
or equal to the {1} value.
CRRDG3316E
Error reading available registers.
CRRDG3317E
Could not get the list of available modules from the engine.
CRRDG3318E
Could not get the sublist of available modules from the engine.
CRRDG3319E
Could not get the list of module objects from the engine.
CRRDG3320E
Invalid condition or exception.
Messages for Common Access Repository Manager (CARMA)
These are the messages that pertain to the Common Access
Repository Manager (CARMA) in Rational Developer for System z.
CRRZC0201E
CRASERV: The communication is not formatted correctly.
Explanation
The communication to the CARMA server was not formatted
correctly. A non-EBCDIC host code page that is set for the CARMA connection
can cause incorrectly formatted communication.
User response
Disconnect from the CARMA server, check the host code
page setting for the CARMA connection, reconnect, and try the action
again.
CRRZC0202E
CRASERV: Unknown function
Explanation
The CARMA server received a request for an unknown
function. Version mismatch between the CASERV load module and the
CARMA RSE miner can cause unknown functions to be called.
System programmer response
Verify that all host PTFs are properly
installed and configured.
User response
Contact your system programmer.
CRRZC0203E
CRASERV: CARMA has not been initialized.
Explanation
A CARMA function was called before CAMA was initialized.
User response
Disconnect from CARMA, reconnect, and try the action
again.
CRRZC0204E
CRASERV: The command was canceled.
Explanation
The CARMA server received a request to cancel the
command.
User response
No action required.
CRRZC0205E
CRASERV: Could not allocate enough memory.
Explanation
The CARMA server was unable to allocate memory.
User response
In the client, disconnect, reconnect, and try again.
If it persists, increase the amount of memory available in the address
space.
CRRZC0207E
CRASERV: Error encountered writing to the socket.
Explanation
The CARMA server was unexpectedly unable to write
to the socket.
User response
No action is required. CARMA automatically attempts
to reconnect. If this problem persists, have your system programmer
check your TCP/IP settings.
CRRZC0208E
CRASERV: The RAM id is not valid.
Explanation
The client attempted to connect to a RAM ID that is
not valid. Most likely, this error is caused when the client attempts
to connect to or perform an action against a RAM ID that is not valid.
A change in the host RAM configuration can cause a RAM ID to become
invalid.
User response
Restart the workbench and connect to CARMA before
you attempt any CARMA actions.
CRRZC0209E
CRASERV: The trace level is not valid.
Explanation
The value that is specified for the trace level is
invalid.
User response
In the client, disconnect from CARMA, open the CARMA
connection properties, and set the trace level to the correct level.
Reconnect and try your action again.
CRRZC0210E
CRASERV: A valid locale was not provided.
Explanation
The value that is specified for the local was invalid.
User response
In the client, disconnect from CARMA, open the CARMA
preferences, and specify a valid local parameter. Reconnect and try
your action again.
CRRZC0211E
CRASERV: Expected parameters were not passed.
Explanation
An expected parameter was not provided to the CARMA
server from the client.
User response
If you receive this error when you are performing
an action against a repository instance or the RAM itself, make sure
the CARMA host components (CARMA server) are updated to the same level
as the client. If you are using a custom client, have your client
developer confirm the custom action ID is properly provided to the
perform action method.
CRRZC0212E
CRASERV: The contents were not provided.
Explanation
CRASERV did not receive contents from the CARMA server
for the putMember action.
User response
Try your upload again, possibly with a different
code page. You can change the host code page for an individual member
in the properties for that member.
CRRZC0213E
CRASERV: Internal error
Explanation
An unexpected, internal error occurred.
User response
Disconnect from CARMA, reconnect, and try your action
again. If the problem persists, contact support.
CRRZC0214E
CRASERV: The instance ID or filter was not provided.
Explanation
The CARMA server did not receive the expected instance
ID or filter.
User response
Disconnect from CARMA, reconnect, and try the action
again.
CRRZC0215E
CRASERV: The instance ID or member ID was not provided.
Explanation
The CARMA server did not receive the expected instance
ID or member ID.
User response
Disconnect from CARMA, reconnect, and try the action
again.
CRRZC0216E
CRASERV: The lrecl or numRecords is not valid.
Explanation
- lrecl
- the length of a record (a line in a host file)
- numRecords
- the number of records (lines in the host file) being sent
This error happens either when a
putMember action
is called on a record that has a file length of less than 0 or when
the number of records sent is less than 0.
User response
Disconnect from CARMA, reconnect, and try your upload
again. If the problem persists, contact support.
CRRZC0217E
CRASERV: There were fewer records than specified.
Explanation
The CARMA server expected more records than the number
provided for the putMember action
User response
Disconnect from CARMA, reconnect, and try your action
again. If the problem persists, try with a different host code page.
You can change the host code page for an individual member in the
properties for that member.
CRRZC0218E
CRASERV: The line is longer than the specified record length.
Explanation
A line is the member is longer than the maximum line
length (lrecl).
User response
Ensure that all lines are within length limits and
try the upload again.
CRRZC0219E
CRASERV: The instance ID, member ID, metadata key name, or metadata value was not provided.
Explanation
The CARMA server did not receive the expected instance
ID, member ID, metadata key name, or metadata value.
User response
Disconnect from CARMA, reconnect, and try the action
again.
CRRZC0220E
CRASERV: A timeout occurred while waiting for data on the socket.
Explanation
The CARMA server timed out while it was waiting for
a command.
User response
No action is required. The CARMA server is scheduled
to timeout after a certain time to keep host resources available for
other users.
If the CARMA server is timing out too frequently,
have your system programmer increase the timeout value. If the system
uses CRASTART, modify the crastart.timeout value in CRASRV.properties.
If the system uses batch submit, change the PROC 1 PORT TIMEOUT(420) line
in the CRASUB* CLIST.
For more information about increasing the
timeout value, see the Host Configuration Guide.
CRRZC0221E
CRASERV: An expected parameter is missing for the putMember command.
Explanation
The expected parameter for the putMember function
was not provided to the CARMA server from the client.
User response
If you receive this error when you are performing
an action against a repository instance or the RAM itself, make sure
the CARMA host components (CARMA server) are updated to the same level
as the client. If you are using a custom client, have your client
developer confirm the custom action ID is properly provided to the
perform action method.
CRRZC0222E
CRASERV: Error retrieving the Custom Action Framework parameter list.
Explanation
The CARMA server was unable to retrieve the custom
action framework parameter list for the RAMtext.
User response
Disconnect from CARMA, reconnect, and try again.
If the problem persists, confirm that the CRADEF VSAM file is properly
setup.
CRRZC0223E
CRASERV: An expected Custom Action Framework parameter is missing.
Explanation
An action was called that required a custom action
framework parameter that was not provided.
User response
Shut down and restart the client. Reconnect to CARMA
and the RAM before you try the action again. If you are using a custom
client, have your client programmer confirm the client is providing
all required parameters.
CRRZC0224E
CRASERV: Unknown type specified for the Custom Action Framework parameter.
Explanation
An invalid type was specified for a parameter or return
value in the CRADEF configuration VSAM.
User response
Confirm that the CRADEF VSAM file is properly set
up and contains valid types for parameters and return values. Valid
types are STRING, DOUBLE, LONG,
and INT. For more information about valid parameter
and return value types, see the CARMA Developer's Guide.
CRRZC0225E
CRASERV: Error gathering Custom Action Framework returns
Explanation
The CARMA server encountered an error while reading
the custom return values from the RAM.
User response
Have your system programmer confirm that the CRADEF
VSAM file is properly set up and that the RAM is returning the expected
results. For more information about formatting return values, see
the CARMA Developer's Guide.
CRRZC0299E
CRASERV: Unknown error
Explanation
An unknown error occurred in the CARMA server.
User response
Disconnect from CARMA, reconnect, and try again.
CRRZC0301E
The required RAMID is missing.
Explanation
The CARMA Miner received a command that requires
a RAM ID but one was not supplied by the client.
User response
Disconnect from the CARMA host, reconnect, and try
the command again. If you are using a custom client, confirm that
the client is calling the command correctly.
CRRZC0302E
The CARMA protocol is not identified properly in the header: {0}
Explanation
- {0}
- the unexpected protocol provided
The communication between the CARMA
Server and the CARMA Miner was corrupted. CARMA Miner was expecting
a protocol that begins with "
CARMA/" and instead
received {0}.
User response
Disconnect from the CARMA host, reconnect, and try
the command again. If you are using a custom RAM, confirm that you
are not experiencing a buffer overflow condition.
CRRZC0303E
Unsupported CARMA Protocol version: {0}
Explanation
- {0}
- the unsupported CARMA protocol version
CARMA expected a protocol version of 2 or greater,
but received {0}.
User response
Disconnect from the CARMA host, reconnect, and try
the command again. If you are using a custom RAM, confirm that you
are not experiencing a buffer overflow condition.
CRRZC0304E
Server Error: Unsupported CARMA return code {0}.
Explanation
- {0}
- the unexpected integer return code
CARMA expected an integer return code, but instead
received {0}
User response
Disconnect from the CARMA host, reconnect, and try
the command again. If you are using a custom RAM, confirm that you
are not experiencing a buffer overflow condition.
CRRZC0305E
The CARMA response header could not be read.
Explanation
The response header from the CARMA Server contains
an unexpected character.
User response
Disconnect from the CARMA host, reconnect, and try
the command again. If you are using a custom RAM, confirm that you
are not experiencing a buffer overflow condition.
CRRZC0306E
An unexpected end of server response has been reached.
Explanation
The server response ended unexpectedly. An unexpected
end of server response can occur when the socket disconnects prematurely.
User response
Disconnect from the CARMA host, reconnect, and try
the command again. If you are using a custom RAM, confirm that you
are not experiencing a buffer overflow condition.
CRRZC0310E
The RAM initialization state could not be located.
Explanation
The CARMA Miner does not have the initialization information
that is needed to restart a connection to the RAM.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and then try your action again.
CRRZC0311W
The file code-page conversion mapping is missing. Assuming the client is using the default UTF-8:LocalCP.
Explanation
The local and code page information was not sent to
the host, so the default code page was used.
User response
This situation is most likely caused by an outdated
client. No response is required. To remove this message, update the
client.
CRRZC0312E
The file code-page conversion mapping is formatted incorrectly.
Explanation
The code page conversion information that is used
to download a file from CARMA is incorrectly formatted.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try your operation again. If the problem persists,
verify that there is not a problem with custom client code.
CRRZC0313E
Illegal CARMA object type. Expecting {0}, received {1}
Explanation
- {0}
- the object type that is expected by CARMA
- {1}
- the invalid object type provided
CARMA expected an object of type
{0}, but instead had an object of type {1}
User response
Disconnect from the CARMA host at the Remote Systems
view, refresh the parent container, reconnect, and try again. Confirm
that any custom client code is sending the correct object types.
CRRZC0315E
CARMA Expected {0,number,integer} attributes and received {1,number,integer} attributes.
Explanation
- {0}
- the expected number of attributes from the CARMA server
- {1}
- the number of attributes that are received from the CARMA server
The CARMA Miner received the incorrect
number of attributes from the CARMA server. This situation can be
caused by a socket communication error.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try the command again. If the problem persists,
ensure that all host components of CARMA are at the same level.
CRRZC0316E
A duplicate item (Id={0}) was encountered in the response.
Explanation
- {0}
- the id that has a duplicate
A list was returned from the RAM
that included duplicates of the same ID.
User response
The RAM developer must update the RAM to ensure that
duplicate elements are not returned with the same ID.
CRRZC0317E
Internal error: The response body is empty.
Explanation
The CARMA Miner received an empty response body from
the CARMA server, possibly caused by a socket communication error.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try the command again. If the problem persists,
ensure that all host components of CARMA are at the same level.
CRRZC0318E
Internal error: The response processor is not set.
Explanation
The CARMA Miner was not able to parse a response from
the CARMA Server because of an internal error.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try the command again. If the problem persists,
contact technical support.
CRRZC0320E
Server Error: The metadata key could not be read.
Explanation
The CARMA Miner was unable to read a metadata key.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try again. If you are using a custom RAM, ensure
that the RAM does not return any special characters within metadata
keys.
CRRZC0321E
Server Error: The metadata value could not be read.
Explanation
The CARMA Miner was unable to read a metadata value.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try again. If you are using a custom RAM, ensure
that the RAM does not return any special characters within metadata
values.
CRRZC0350E
Server Error: The return contents size from the response could not be determined.
Explanation
The CARMA Miner received an invalid response from
the CARMA server, possibly caused by a socket communication error.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try again. If the problem persists, ensure that
all host components are at the same level.
CRRZC0351E
Server Error: The returns contents size "{0}" is improperly formatted.
Explanation
- {0}
The CARMA Miner received an invalid
response from the CARMA server, possibly caused by a socket communication
error.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try again. If the problem persists, ensure that
all host components are at the same level.
CRRZC0352E
Server Error: The CARMA Response Body could not be processed.
Explanation
The CARMA Miner received an invalid response from
the CARMA server, possibly caused by a socket communication error.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try again. If the problem persists, ensure that
all host components are at the same level.
CRRZC0360E
Server Error: The Container check failed due to an improperly formatted CARMA response body.
Explanation
While the CARMA Miner was getting container contents,
it received an invalid response from the CARMA server. This situation
can be caused by a socket communication error.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try again. If the problem persists, confirm
that all host components are at the same level. If you are using
a custom RAM, ensure that control characters are not used in MemberIDs.
CRRZC0370E
Expected {0} attributes and received {1} attributes.
Explanation
- {0}
- the expected number of attributes
- {1}
- the received number of attributes
While the CARMA Miner was getting custom action
framework information, it received an invalid response from the CARMA
server. This situation can be caused by a socket communication error.
User response
Disconnect from the CARMA host at the Remote Systems
view, reconnect, and try again. If the problem persists, ensure that
all host components are at the same level. Ensure that no newline
characters are used in the VSAM configuration files.
CRRZC0371E
A duplicate item (Id={0}) encountered in the response. Error in CARMA's Custom Action Framework configuration.
Explanation
- {0}
- the duplicate id
Two items in the CARMA VSAM configuration files
have the same id, {0}.
User response
Have your system programmer or Custom RAM Developer
check the CRADEF VSAM file and modify it so that
the id provided is not duplicated. More information
about the VSAM configuration files can be found in the Rational Developer for System z Common
Access Repository Manager (CARMA) Developer's Guide.
CRRZC0385E
Improper custom action configuration section count ({0}).
Explanation
- {0}
- the number of custom action information received
Not enough custom action information
was returned by the CARMA server, possibly due to a socket error.
At least four sections of information was expected, but only {0}
were received.
User response
Disconnect from the CARMA host, reconnect, and try
again. If the problem persists, ensure that all CARMA files on the
host are at the same level.
CRRZC0392E
Invalid custom parameter type "{1}"
Explanation
- {0}
- the custom parameter
- {1}
- the invalid type
A custom parameter or return value
has an invalid type. Valid types are "
STRING", "
DOUBLE",
"
LONG", and "
INT".
User response
Have your system programmer or Custom RAM Developer
check the CRADEF VSAM file and modify it so the custom
parameters and return values all have valid types. More information
about the VSAM configuration files can be found in the Rational Developer for System z Common
Access Repository Manager (CARMA) Developer's Guide.
CRRZC0393E
The default value does not match with given type: type={0}, value={1}.
Explanation
- {0}
- A specified type that is required for the value
- {1}
- The default value of a custom parameter
A custom parameter has a default value of
{1},
which is not a valid example of the type specified.
User response
Have your system programmer or Custom RAM Developer
check the CRADEF VSAM file and modify it so the custom
parameters all have valid default values that are based on their type.
More information about the VSAM configuration files can be found in
the Rational Developer for System z Common
Access Repository Manager (CARMA) Developer's Guide.
CRRZC0394E
The parameter length for (Parameter Id={0}) is not an Integer: {1}.
Explanation
- {0}
- the parameter id
- {1}
- 1
A custom parameter has a non-integer value for length
in the CARMA configuration VSAM file.
User response
Have your system programmer or Custom RAM Developer
check the CRADEF VSAM file and modify it so the custom
parameters all have valid lengths. More information about the VSAM
configuration files can be found in the Rational Developer for System z Common
Access Repository Manager (CARMA) Developer's Guide.
CRRZC0398E
Invalid custom parameter identifier ({1}) associated with action "{2}".
Explanation
- {0}
- the custom parameter
- {1}
- the custom return value
- {2}
- the action
An action defined in the CARMA configuration
VSAM file does not have a valid custom parameter or return value.
The ID is not a valid integer or is not defined.
User response
Have your system programmer or Custom RAM Developer
check the CRADEF VSAM file and modify it so all actions
have valid ids for the custom parameters and return values. All parameters
or return values must also be defined in the VSAM file. More information
about the VSAM configuration files can be found in the Rational Developer for System z Common
Access Repository Manager (CARMA) Developer's Guide.
CRRZC0400E
The method has already been executed. The method cannot be executed twice.
Explanation
The CARMA miner attempted to run the same command
twice.
User response
Disconnect from RSE, reconnect, and try your CARMA
command again.
CRRZC0401E
Server Error: The Command subject could not be located on the host
Explanation
The CARMA object (member, container, repository instance)
was not found on the host.
User response
Refresh the parent container, and try the action
again.
CRRZC0402E
The required parameters are missing.
Explanation
The CARMA client did not provide the required parameters
to the CARMA miner.
User response
Disconnect from RSE, reconnect RSE, reconnect CARMA,
reconnect to the RAM, and then try your command again. If you are using
a custom client, ensure that all required parameters are being sent
to the RAM.
CRRZC0403E
The CARMA connection was not initialized.
Explanation
CARMA was not initialized before a CARMA command was
issued.
System programmer response
Check the CARMA startup configuration
on the host.
User response
Disconnect from the CARMA connection, reconnect,
and try the action again.
CRRZC0405E
The server is not loaded properly. Contact the system programmer.
Explanation
The CARMA miner was unable to start the CARMA server.
User response
Have your system programmer check the CARMA startup
configuration. More information about configuring CARMA can be found
in the Rational Developer for System z Host
Configuration Guide.
CRRZC0407E
The server startup was interrupted.
Explanation
While the CARMA Server was waiting to connect to the
CARMA Miner, there was an interruption, possibly caused by a socket
error or the RSE Miner shutting down unexpectedly.
User response
Disconnect from the CARMA host, reconnect, and try
your command again.
CRRZC0408E
Too many parameters to the REXX startup script.
Explanation
More parameters than expected were passed to the carma.startup.rex
script.
User response
Confirm that all of the CARMA host code is at the
same level. If the carma.startup.rex was modified for your installation,
confirm that it is working as expected.
CRRZC0409E
Could not access the configured CLIST.
Explanation
The CLIST defined in CRASRV.properties was not found
by the carma.startup.rex script. The user might not have the required
permissions to access the CLIST, or the location is incorrect.
User response
Confirm that the correct CLIST is defined in CRASRV.properties
and that the user has permission to access it.
CRRZC0410E
Server Error: The command is not supported.
Explanation
CARMA miner encountered a command that was unsupported.
System programmer response
Verify that the host and client versions
of the product are the same.
User response
Disconnect from CARMA, reconnect, and try the action
again.
CRRZC0411E
Missing the port argument for the CARMA Host server.
Explanation
The carma.startup.rex script did not receive a port
parameter, most likely caused by a modified or out of date carma.startup.rex.
User response
Confirm that all of the CARMA host code is at the
same level. If the carma.startup.rex was modified for your installation,
confirm that it is working as expected
CRRZC0412E
Could not locate the REXX startup script.
Explanation
The CARMA Rexx script was not found. Possibly caused
by the location not being an absolute location.
User response
Check the location that is defined for the CARMA
startup script name in the CRASRV.properties file. "startup.script.name"
provides the absolute location of the startup script.
CRRZC0413E
Missing the CLIST argument for the CARMA Host server.
Explanation
The carma.startup.rex script did not receive a CLIST
parameter, most likely caused by a modified or out of date carma.startup.rex.
User response
Confirm that all of the CARMA host code is at the
same level. If the carma.startup.rex was modified for your installation,
confirm that it is working as expected.
CRRZC0415E
Starting the CARMA Host server encountered an unknown error. Please check the log.
Explanation
The CARMA startup script encountered an unknown error
while it was trying to start the CARMA Server.
User response
Check the rsecomm.log file for output from the CARMA
startup script. This error can be caused by errors in the CARMA Server
configuration or the user not having the required permissions to start
the CARMA server.
CRRZC0420E
The upload did not complete successfully. Disconnect and retry the upload.
Explanation
An I/O error occurred while the file was uploading from
the CARMA RSE Miner to the CARMA server. Check the rsecomm.log for
more information.
User response
Disconnect from CARMA, reconnect, and try the action
again.
CRRZC0421E
Codepage mapping is not supported by the CARMA host.
Explanation
The local or remote code page that is set for the
target CARMA member is not supported by the Host system.
User response
The code page settings for the CARMA Member can be
modified on its properties page. Change the remote code page to something
supported by the host system and try your file download or upload
again.
CRRZC0430E
The key/value set on the member could not be retrieved.
Explanation
The CARMA Miner encountered an invalid key or value
while it was setting or retrieving metadata info. This situation
can be caused by a socket error on the host.
User response
Disconnect from the CARMA host, reconnect, and try
your command again. If you were retrieving metadata information,
make sure the RAM that you are using does not use special characters
for keys or values for metadata information. If you were setting
metadata information, make sure that all values were non-null and
did not use special characters.
CRRZC0433E
DataStore State Exception: The Instance container was not found in the required location.
Explanation
The datastore that is used by the CARMA Miner has
incorrect entries and an appropriate container cannot be found for
the CARMA Object being worked against.
User response
Disconnect from the CARMA host, reconnect, and try
your action again. If you are using custom client code, confirm it
is operating correctly. If the problem persists, delete the CARMA
connect, re-create it, and try your action again.
Note: Deleting the
CARMA connect breaks any associations between CARMA members and local
or z/OS projects.
CRRZC0450E
The download location argument could not be found.
Explanation
The CARMA Miner did not receive the location to download
the member to, most likely caused by an out of date client or host.
User response
Make sure that your client and host are both at the
same level. A difference greater than two levels apart is not supported
CRRZC0451E
LRECL changed value during the download.
Explanation
The RAM reported a different LRECL value for the CARMA
member while in the process of downloading the member.
User response
Have your RAM developer correct this error in the extractMember function.
CRRZC0452E
RECFM changed value during the download.
Explanation
While the CARMA miner was chunking a file download,
it received a different LRECL (logical record length) value than the
download started with.
User response
Disconnect from the CARMA host, reconnect, and try
transferring the file again. If you are using a custom RAM or client,
make sure that LRECL is handled correctly.
CRRZC0480E
The Upload handler is in an invalid state. You need to reset.
Explanation
While the CARMA miner was trying to upload a member
from the client to the host, it encountered an invalid state.
User response
Disconnect from the CARMA host, reconnect, and try
the upload again. If the problem persists, have your systems programmer
restart Developer for System z on the host.
CRRZC0490E
Error in checking container property.
Explanation
While the CARMA miner was trying to refresh the contents
of a CARMA container or Repository Instance, it was not able to verify
the container information.
User response
Disconnect from the CARMA host, reconnect, and try
your command again. If the problem persists, try to refresh the container's
container first. This problem can also be caused by incompatible
versions of CARMA on the host and client. Make sure that your host
and client are on the same level.
CRRZC0499E
An unidentified error occurred during upload.
Explanation
An unexpected error occurred while the file was uploading
to CARMA.
User response
Check the rsecomm.log file for more information about
what caused the error. Disconnect from the CARMA host, reconnect,
and try your upload again.
CRRZC1010E
Invalid member Id search parameter: null or ""
Explanation
A find resource, or a query for a container or element
supported on CARMA container or repository instances, was called with
an empty or null parameter ID.
User response
Refresh the parent container and try again.
CRRZC1100E
Required parameters (LRecl or RecFM) are not set. The contents cannot be uploaded.
Explanation
The file was not transferred in the proper format.
User response
Verify that the transfer format is specified correctly
and try again.
CRRZC1101E
Custom actions are not available: Not synchronized
Explanation
The CARMA and RAM connections are no longer
synchronized.
User response
You need to disconnect and reconnect your CARMA and
RAM connection.
CRRZC1102E
Custom actions are not available: Not synchronized
Explanation
The CARMA and RAM connections are no longer synchronized.
User response
You need to disconnect and reconnect your CARMA and
RAM connection.
CRRZC1103E
An Error occurred while writing new member contents. See the Error log for more details.
Explanation
The specified character encoding is not supported
when creating the new CARMA member.
User response
Change the character encoding of the source member
and try again.
CRRZC1201E
The RAM connect method is disabled.
Explanation
In the RAM configuration, "Connect to RAM" has been
disabled.
User response
Enable "Connect to RAM" in the RAM configuration.
For additional information on enabling "Connect to RAM", see "Customizing
a RAM API using the CAF" in the Rational Developer for System z
Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
CRRZC1202E
Could not load the Repository Instances. The operation is not supported by the host Repository.
Explanation
In the RAM configuration, "Get Instances" has been
disabled.
User response
Enable "Get Instances" in the RAM configuration.
For additional information on enabling "Get Instances", see "Customizing
a RAM API using the CAF" in the Rational Developer for System z
Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
CRRZC1300E
The CARMA Transport Service was not initiated.
Explanation
The transport service is the communication bridge
between CARMA and the Remote System Explorer (RSE) on the client.
In this case, this communication bridge was not initialized.
User response
Restart the workbench with the -clean flag.
CRRZC1304E
Problems loading configuration for '{0}'
Explanation
- {0}
- 0
Either there was a connection problem while trying
to load the custom action framework (CAF) for the RAM or the configuration
VSAMs (CRADEF and CRASTRS) are incorrect.
User response
Disconnect and reconnect from CARMA/RSE and try again.
Additionally, have your systems administrator check the RAM setup
on the host by verifying the CRADEF and CRASTRS files.
CRRZC1400E
The transport layer connection was not created properly.
Explanation
The transport service is the connection bridge between
CARMA and the Remote System Explorer (RSE) on the client. In this
case, this communication bridge was not create properly.
User response
Restart the workbench with the -clean flag.
CRRZC1401E
The Repository Manager transport service connection was not created properly.
Explanation
Your CARMA connection is no longer working.
User response
Disconnect from CARMA, reconnect, and try again.
CRRZC1402E
The repository instances were not found because CARMA is not properly connected.
Explanation
Your CARMA connection is no longer working.
User response
Disconnect from CARMA, reconnect, and try again.
CRRZC1403E
The CARMA transport service could not be accessed.
Explanation
The transport service is the communication bridge
between CARMA and the Remote System Explorer (RSE) on the client.
In this case, this communication bridge could not be accessed.
User response
Restart the workbench with the -clean flag.
CRRZC1404E
Could not access Repository transport service: {0}
Explanation
- {0}
- 0
The transport service is the communication bridge
between CARMA and the Remote System Explorer (RSE) on the client.
In this case, this communication bridge was not accessible.
User response
Restart the workbench with the -clean flag.
CRRZC1450E
The repository managers were not loaded because CARMA is not properly connected.
Explanation
Your CARMA connection is no longer working.
User response
Disconnect from CARMA, reconnect, and try again.
CRRZC1490W
Skipping extension '{0}' because of an invalid property priority: {1}. Priority must be an integer greater than 0.
Explanation
- {0}
- 0
- {1}
- 1,number,integer
If a transport layer has an invalid priority, then
the transport layer will not be loaded.
User response
If the process works, then ignore the message. Otherwise,
restart the workbench and try again.
CRRZC1501E
The back end transport service could not be located using key: {0}
Explanation
- {0}
- 0
CARMA is no longer associated with the RSE connection.
User response
Delete the CARMA connection and Create a new CARMA
connection.
CRRZC1502E
Could not load the TransportServiceFactory extension
Explanation
The TransportServiceFactory, which contains all loaded
transport layers, was not loaded.
User response
If the process works, then ignore the message. Otherwise,
restart the workbench and try again.
CRRZC1550W
Could not load the CARMA compare configuration, using the default (file) compare criteria.
Explanation
The CARMA compare configuration file, syncConfig.xml cannot
be found.
User response
None needed, CARMA will check the bytes of the compare
files.
CRRZC1551W
Could not load the CARMA compare configuration, using the default (file) compare criteria.
Explanation
The CARMA compare configuration file, syncConfig.xml cannot
be found.
User response
None needed, CARMA will check the bytes of the compare
files.
CRRZC1601W
Could not load the structured type value ({0}): {1}
Explanation
- {0}
- 0
- {1}
- 1
CARMA stores its model containing the CARMA connections
and any cached containers and members to disk at workspace shut down
and reloads at workspace startup. In this case, there was a problem
reloading this CARMA model.
User response
If CARMA connections appear broken, recreate them
and try again. Otherwise, restart your workbench and try again.
CRRZC1602W
Could not convert the structured type value ({0}): {1}
Explanation
- {0}
- 0
- {1}
- 1
CARMA stores its model containing the CARMA connections
and any cached containers and members to disk at workspace shut down
and reloads at workspace startup. In this case, there was a problem
reloading this CARMA model.
User response
If CARMA connections appear broken, recreate them
and try again. Otherwise, restart your workbench and try again.
CRRZC2001E
Could not locate the CARMA Project for temporary downloads.
Explanation
When editing through the CAMRA editor, CARMA makes
use of a temporary location to store temporary downloads. While processing,
CARMA could not locate this temporary location.
User response
Retry opening the file. If reopening the file does
not work, restart the workbench.
CRRZC2002E
An error occurred creating and opening the CARMA download project.
Explanation
CARMA stores temporary downloaded files to a hidden
CARMA download project. In this case, there was a problem creating
or opening this project.
User response
Restart the workbench and try again. If this doesn't
work, create a new workspace and try again.
CRRZC2003E
An error occurred retrieving the file from the server.
Explanation
There was an error retrieving the file, and more information
should be provided in an accompanying error message.
User response
Check error log for accompanying messages.
CRRZC2004E
Communication error[LRecl Format]-- See the error log for details.
Explanation
CARMA has returned an invalid record length when trying
to open a member.
User response
If the problem persists, have the RAM developer confirm
an integer is returned for the LRecl or open the file in binary transfer
mode.
CRRZC2005E
The temporary element type is not valid.
Explanation
CARMA encountered an error when making a temporary
element for communication with the host.
User response
Refresh the parent of the current item, and try again.
CRRZC2007E
Error uploading file: {0}
Explanation
- {0}
- File name
There was an error uploading a file to CARMA.
User response
Disconnect from CARMA, reconnect, and try again.
CRRZC2008E
The CARMA command timed out. The operation was cancelled.
Explanation
While CARMA was waiting for a response from the host,
it timed out.
User response
Disconnect from RSE, reconnect, and try again. If
the problem persists, it could be a configuration problem on the host.
CRRZC2009E
Error uploading file: {0}
Explanation
- {0}
- 0
There was an error uploading the file.
User response
Refresh the parent of the current item, and try again.
CRRZC2010E
Error uploading file: {0} {1}
Explanation
- {0}
- 0
- {1}
- 1
There was an error uploading the file, and an additional
message with more information will be provided.
User response
Follow the steps in the additional message. If still
unsuccessful, then disconnect from CARMA, reconnect, and try again.
CRRZC2011E
The key to find is not set.
Explanation
There was an unexpected error during file upload.
Please report this error to technical support.
User response
Please report this error to technical support.
CRRZC2012E
The line length is greater than the record size of {2} (line {0} is {1} characters long).
Explanation
- {0}
- 2
- {1}
- 0
- {2}
- 1
The file could not be uploaded as the specified line
number is longer than the line record length.
User response
Modify the given line of the file so that the length
is shorter than the given record size.
CRRZC2013E
Error uploading file: {0} {1}
Explanation
- {0}
- 0
- {1}
- 1
There was an error uploading the file, and an additional
message with more information will be provided.
User response
Follow the steps in the additional message. If still
unsuccessful, then disconnect from CARMA, reconnect, and try again.
CRRZC2014I
Interrupted while waiting for the upload return
Explanation
CARMA finished sending the file to the host but was
interrupted before it could get final confirmation.
User response
Confirm the contents of the file on the host, or
perform the upload again.
CRRZC2017E
Error uploading file: {0}
Explanation
- {0}
- 0
There was an error uploading the text file.
User response
Disconnect from CARMA, reconnect and try again.
CRRZC2018E
The LRecl is not formatted correctly: {0}
Explanation
- {0}
- The value for LRecl received from the RAM
The logical record length (LRecl)
is not properly defined in the RAM.
User response
Contact the RAM developer to modify the RAM to return
the LRecl in the proper format. For additional information on RAMs,
see the Rational Developer for System z Common Access Repository
Manger (CARMA) Developers Guide (SC23-7660).
CRRZC2027E
Error uploading file: {0}
Explanation
- {0}
- 0
There was an error uploading the binary file.
User response
Disconnect from CARMA, reconnect and try again.
CRRZC2044E
Communication error[LRecl Format]-- See the error log for details.
Explanation
The value for the logical record length (LRecl) is
not valid.
User response
Contact the RAM developer to modify the RAM to return
the LRecl in the proper format. For additional information on RAMs,
see the Rational Developer for System z Common Access Repository
Manger (CARMA) Developers Guide (SC23-7660).
CRRZC2070E
StatusChangeListener.{0} communications diagnostic started.
Explanation
- {0}
- 0
A time out occurred while waiting for an update from
the host.
User response
Disconnect from RSE, reconnect, and try again. If
the problem persists, have your system's administrator check
your host configuration and tune Rational Developer for System z for
the number of users connecting concurrently.
CRRZC2071E
StatusChangeListener.{0}: done = {1}; cancelled = {2}; _networkDown = {3}
Explanation
- {0}
- status of the listener; possible values: started, working, done
- {1}
- true or false, if the upload completed
- {2}
- true or false, if the upload was canceled
- {3}
- true or false, if the network is down
This message provides the diagnostic
information for message CRRZC2070E.
CRRZC2072E
StatusChangeListener.{0}(DataStore): isConnected = {1}; isWaiting = {2}
Explanation
- {0}
- status of the listener; possible values: started, working, done
- {1}
- true or false, if the connection to the host is active
- {2}
- true or false, if the connection
This message provides the diagnostic information
for message CRRZZC2070E.
CRRZC2073E
StatusChangeListener.{0}.child{1}(DataElement): {2}
Explanation
- {0}
- status of the listener; possible values: started, working, done
- {1}
- index of the child data element (member, member attribute, container)
- {2}
- underlying data element representation of the CARMA object
This message provides the diagnostic information
for message CRRZZC2070E.
CRRZC2074E
StatusChangeListener.{0}.child{1}(Descriptor): {2}
Explanation
- {0}
- status of the listener; possible values: started, working, done
- {1}
- index of child data element (member, member attributes, container)
- {2}
- description of child data element, such as the attribute data
that describes the child data element
This message provides the diagnostic information
for message CRRZZC2070E.
CRRZC2075E
StatusChangeListener.ICommunicationsDiagnostic exception
Explanation
A timeout occurred and an exception was caught while
running diagnostics.
User response
Follow the user response for any messages included
in the exception; otherwise, disconnect from RSE, reconnect, and try
again. If the problem persists, have systems administrator check your
host configuration and tune Rational Developer for System z for the
number of users connecting concurrently.
CRRZC2101E
An object found in the DataStore is not valid.
Explanation
The host returned an invalid type of object for CARMA.
User response
Disconnect from the remote system explorer, reconnect,
and try again.
CRRZC2102E
An object found in the DataStore is not valid.
Explanation
The host returned an invalid type of object for CARMA.
User response
Disconnect from the remote system explorer, reconnect,
and try again.
CRRZC2103E
An object that is not valid was found in the CARMA Transport.
Explanation
The host returned an invalid type of object for CARMA.
User response
Disconnect from the remote system explorer, reconnect,
and try again.
CRRZC2104E
An object that is not valid was found in the CARMA Transport.
Explanation
The host returned an invalid type of object for CARMA.
User response
Disconnect from the remote system explorer, reconnect,
and try again.
CRRZC2105E
CARMA Transport State Exception: The member information referenced by key ({0}) was not found.
Explanation
- {0}
- 0
CARMA requested member information for a given key,
which was not found for this CARMA resource.
User response
No user response is required. The particular piece
of information is not set or valid on the CARMA resource.
CRRZC2106E
An object that is not valid was found in the CARMA Transport.
Explanation
The host returned an invalid type of object for CARMA.
User response
Disconnect from the remote system explorer, reconnect,
and try again.
CRRZC2107E
The temporary element was not created properly.
Explanation
An error occurred that prevented the temporary element
from being created properly.
User response
Disconnect you CARMA connection, reconnect, and try
again.
CRRZC2108E
The DataStore transport was not synchronized with CARMA. Re-create your connection.
Explanation
The CARMA connection could not be synchronized with
the underlying host transport layer.
User response
Remove the CARMA connection, recreate the connection,
and try again.
CRRZC2109E
The command was not found: {0}
Explanation
- {0}
- 0
The CARMA command could not be located on the host.
User response
Disconnect from the remote system explorer, reconnect,
and try again. If the problem persists, confirm with a system programmer
that CARMA is installed on the host and is the correct version.
CRRZC2110E
The file transfer conversion mapping is not set.
Explanation
A third-party plug-in tried to set the contents of
a CARMA member using internal API's.
User response
Make use of the method CARMAMember.setMemberContents() when
setting the contents of a CARMA member in a third-party CARMA plug-in.
CRRZC2111E
The CARMA transport cannot locate the element. Refresh at a higher level in the hierarchy.
Explanation
The host side temporary cache of the resource is missing.
User response
Try the following:
- refreshing the object again
- refreshing the parent object
- disconnect and reconnect to the CARMA connection
CRRZC2112E
RAM Error: The resource returned from the host changed type. The attempted command is no longer available.
Explanation
A record in the member is too long. The member has
not been saved on the host.
User response
Modify the length of the line and save again.
CRRZC2113E
Could not initialize. CARMA is not connected.
Explanation
CARMA is unable to connect to the Host. This can occur
when CARMA is not properly configured.
User response
Check the log to see if an error was received from
the CARMA Host (CRRZC2220E). If this error has occurred, contact your
system programmer to verify that the host is properly configured as
outline in the Rational Developer for System z Common Access Repository
Manger (CARMA) Developers Guide (SC23-7660).
CRRZC2114E
A temporary element for the CARMA resource, {0}, was not created.
Explanation
- {0}
- 0
Could not create a temporary object to communicate
with the host for the given resource.
User response
Refresh the resources parent, and try again.
CRRZC2115E
The CARMA Transport element associated with the CARMA member is not set.
Explanation
A third-party plugin tried to set or get the contents
of a CARMA member using internal API's.
User response
Use the CARMAMember.setMemberContents() and CARMAMember.getMemberContents() methods
to set and get CARMA member contents respectively.
CRRZC2116E
The CARMA connect operation was not successful.
Explanation
CARMA is unable to connect to the Host. This can occur
when CARMA is not properly configured.
User response
Check the log to see if an error was received from
the CARMA Host (CRRZC2220E). If this error has occurred, contact your
system programmer to verify that the host is properly configured as
outline in the Rational Developer for System z Common Access Repository
Manger (CARMA) Developers Guide (SC23-7660).
CRRZC2117E
The CARMA system did not connect properly after calling the connect operation.
Explanation
CARMA is unable to connect to the Host. This can occur
when CARMA is not properly configured.
User response
Check the log to see if an error was received from
the CARMA Host (CRRZC2220E). If this error has occurred, contact your
system programmer to verify that the host is properly configured as
outline in the Rational Developer for System z Common Access Repository
Manger (CARMA) Developers Guide (SC23-7660).
CRRZC2118W
The terminate CARMA job command did not succeed. Attempting to disconnect the system.
Explanation
There was an error trying to terminate the CARMA job
during disconnect.
User response
No user action is necessary.
CRRZC2119E
The CARMA disconnect operation was not successful.
Explanation
CARMA is unable to disconnect from the Host. This
can occur when CARMA is not properly configured.
User response
Check the log to see if an error was received from
the CARMA Host (CRRZC2220E). If this error has occurred, contact your
system programmer to verify that the host is properly configured as
outline in the Rational Developer for System z Common Access Repository
Manger (CARMA) Developers Guide (SC23-7660).
CRRZC2122E
Could not execute {0}: {1}
Explanation
- {0}
- the CARMA command name
- {1}
- a message describing the problem
The first part of the error message
will provide the CARMA command name. The second part of the message
includes a meaningful message of the problem.
User response
Follow the user response instruction for the second
part of the message to resolve the problem.
CRRZC2123E
An object that is not valid was found in the CARMA Transport.
Explanation
The host returned an invalid type of object for CARMA.
User response
Disconnect from the remote system explorer, reconnect,
and try again.
CRRZC2124E
An object that is not valid was found in the CARMA Transport.
Explanation
The host returned an invalid type of object for CARMA.
User response
Disconnect from the remote system explorer, reconnect,
and try again.
CRRZC2126E
An object that is not valid was found in the CARMA Transport.
Explanation
The host returned an invalid type of object for CARMA.
User response
Disconnect from the remote system explorer, reconnect,
and try again.
CRRZC2128E
Could not retrieve the member contents from CARMA.
Explanation
There was an error retrieving the file, and more information
should be provided in an accompanying error messages.
User response
Check the error log for additional messages.
CRRZC2129E
Could not upload the file to the host.
Explanation
There was an error uploading the file to the host.
User response
Follow the user response in the additional message
provided.
CRRZC2200E
An error was received from the CARMA Host [{0}]: [{2}] {1}
Explanation
- {0}
- host name
- {1}
- error number
- {2}
- error message
The error message provides more
information about the problem.
CRRZC2201E
CARMA Initialization is not supported.
Explanation
CARMA has been configured with the initialization
function disabled and cannot start.
User response
Have the system programmer or RAM developer modify
the CRADEF configuration VSAM on the host to not disable action ID
80.
CRRZC2202E
The custom action framework description could not be located: This operation is not supported.
Explanation
CARMA has been configured with the custom action framework
function disabled.
User response
Have the system programmer modify the CRADEF configuration
VSAM on the host not to disable action ID 83.
CRRZC2203E
RAM Initialization is not supported: The RAM could not be initialized.
Explanation
The RAM has been configured with the RAM initialization
function disabled and cannot start.
User response
Have the system programmer modify or RAM developer
the CRADEF configuration VSAM on the host not to disable action ID
0. Additionally, the intRAM() function in the RAM should not return
107 or RAM_ERR_FUNC_NOT_SUPPORTED, which states a
function is not supported.
CRRZC2205E
Binary Transfer is not supported.
Explanation
The version of CARMA installed on the host is out
of date, and it does not support binary transfers. This error can
occur when you attempt to retrieve the binary version of a file from
CARMA rather than the text version.
User response
Set the transfer type to text. Alternatively, if
you need the file in binary, have your system programmer update the
host installation.
CRRZC2220E
CARMA is not available on the specified host.
Explanation
The required CARMA jar file is not found in the class
path in the Server. The Rational Developer for System z server was
not properly installed and configured.
User response
Contact your system programmer and report the the
problem. For information on installation and configuration, see the Rational
Developer for System z Host Configuration Guide (SC23-7658).
CRRZC2230E
An error was encountered while processing the custom action descriptions from the host.
Explanation
When connecting to CARMA, there was an error getting
the custom action descriptions.
User response
Disconnect from RSE, reconnect, and try again. Additionally,
if there is an additional message included, follow the user response
for that particular error message.
CRRZC2300W
Could not access the key '{0}' from the RAM.
Explanation
- {0}
- 0
CARMA could not find the stated metadata key when
refreshing the metadata information.
User response
No action needs to be taken as this is an informational
warning.
CRRZC2301E
The connection alias name is not specified.
Explanation
CARMA could not find the stated metadata key when
refreshing the metadata information.
User response
No action needs to be taken as this is an informational
error message.
CRRZC2301W
Could not access the key '{0}' from the RAM.
Explanation
- {0}
- 0
CARMA is no longer associated with the RSE connection.
User response
Delete the existing CARMA connection and Create a
new CARMA connection.
CRRZC2302E
The connection with alias, '{0}', was not found.
Explanation
- {0}
- 0
CARMA is no longer associated with the RSE connection.
- 0
- The name of the connection
User response
Delete the existing CARMA connection and Create a
new CARMA connection.
CRRZC2303E
Connection ({0}) does not have a CARMA subsystem established.
Explanation
- {0}
- 0
The CARMA connection is no longer associated with
an RSE connection. The RSE connection could have been deleted or renamed.
User response
Recreate an RSE connection with the same name and
host, and try connecting to CARMA again. Alternatively, you can remove
the CARMA connection and create a new CARMA connection. Removing the
CARMA connection will remove the associations between CARMA and any
members extracted to remote and local projects.
CRRZC2304E
The repository manager {0} was not found in the DataStore.
Explanation
- {0}
- 0
The local Cache does not match what is on the host.
User response
Disconnect, reconnect, and refresh CARMA.
CRRZC2305E
The repository instance {0} was not found in the DataStore.
Explanation
- {0}
- 0
The local Cache does not match what is on the host.
User response
Disconnect, reconnect, and refresh the repository
manager.
CRRZC2401E
Invalid parameter default value '{0}' for {1,choice,0#custom parameter|1#custom return value|2#custom field} (parameterId={2})
Explanation
- {0}
- 0
- {1}
- 1,choice,0#custom parameter|1#custom return value|2#custom field
- {2}
- 2
The default value set in the configuration VSAM is
not of the proper type.
User response
The RAM developer should modify the configuration
VSAMs to have a default value of the proper type for the parameterID
listed in the message.
CRRZC2402E
Invalid parameter default value '{0}' for {1,choice,0#custom parameter|1#custom return value|2#custom field} (parameterId={2})
Explanation
- {0}
- 0
- {1}
- 1,choice,0#custom parameter|1#custom return value|2#custom field
- {2}
- 2
The default value set in the configuration VSAM is
not of the proper type.
User response
The RAM developer should modify the configuration
VSAMs to have a default value of the proper type for the parameterID
listed in the message.
CRRZC2403E
Invalid parameter default value '{0}' for {1,choice,0#custom parameter|1#custom return value|2#custom field} (parameterId={2})
Explanation
- {0}
- invalid type that is specified in the configuration VSAM file;
valid types are STRING, INT, LONG,
and DOUBLE
- {1}
- values can be "custom parameter", "custom return value", or "custom
field"
- custom parameter
- a parameter that is passed to the RAM
- custom return value
- a return value that is passed back from the RAM
- custom field
- a field that is defined by the RAM
- {2}
- The parameter id that is specified in the configuration VSAM files.
The default value set in the configuration
VSAM is the wrong type.
User response
The RAM developer should modify the configuration
VSAMs to have a default value of the proper type for the parameterID
listed in the message.
CRRZC2405E
DataStore state exception: An element type that is not allowed was found in parameter container: {0}
Explanation
- {0}
- 0
A custom parameter, custom return value, or CARMA
field is being reported as having an unsupported type.
User response
Disconnect CARMA, reconnect, and try again. If the
problem persists, have the RAM developer change the parameter type
to a supported one, or update the client to the same version as the
host to support the new parameter type.
CRRZC2406E
Cannot create the resource: The LRecl(record length) or recFM (record format) is missing from the command returns.
Explanation
CARMA or the RAM did not provide a valid for LRecl
or recFM when the create member call was made.
User response
Refresh the parent container to see if the member
was created by the RAM. If not, then retry the action. If the problem
persists, confirm the RAM developer is setting these values.
CRRZC2407E
Cannot create the resource: The name or member Id is missing from the command returns.
Explanation
CARMA or the RAM did not provide a valid name or memberID
when the create member call was made.
User response
Refresh the parent container to see if the member
was created by the RAM. If not, then retry the action. If the problem
persists, confirm the RAM developer is setting these values.
CRRZC2410E
Invalid parameter length ({0}) for {1,choice,0#custom parameter|1#custom return value|2#custom field} (parameterId={2})
Explanation
- {0}
- 0
- {1}
- 1,choice,0#custom parameter|1#custom return value|2#custom field
- {2}
- 2
The length set for the parameter in the VSAM configuration
is not a valid number.
User response
The RAM developer should modify the configuration
VSAMs to have the parameter of the proper length for the parameterID
listed in the message.
CRRZC2900W
The CARMA miner version, {0}, was not parsed.
Explanation
- {0}
- 0
Could not parse the CARMA
User response
Disconnect from RSE, reconnect, and try again. If
the message persists or other problems arise, then update your client
to the same version as the host.
CRRZC2901W
Could not load the Repository Managers. The operation is not supported by the host Repository.
Explanation
CARMA has been configured not load the repository
manager.
User response
Have the system programmer or RAM developer modify
the CRADEF configuration VSAM on the host not to disable action ID
82.
CRRZC2902E
RAM disconnect Unsupported: Could not disconnect from the RAM.
Explanation
The terminate RAM action is disabled, so CARMA returned
with an error when trying to disconnect from the RAM.
User response
Have the system programmer or RAM developer modify
the CRADEF configuration VSAM on the host not to disable action ID
01.
CRRZC2903E
A RAM termination exception occurred.
Explanation
An error occurred when disconnecting the RAM.
User response
If there is an associated exception, follow the user
response in that. Otherwise, no action is required.
CRRZC2904I
Requesting file download to: {0}
Explanation
- {0}
- Location to which the file is downloaded to
Informational log message that provides the location
in the local file system to which a file is downloaded.
CRRZC2905I
Setting the trace level for the connection to {0}.
Explanation
- {0}
- Integer value that represents the host CARMA trace level
Informational message that provides the trace level
of the connection. This message is expected to be logged at every
CARMA connection.
CRRZC5000E
The subproject '{0}' is already associated with another Repository Instance: {1}
Explanation
- {0}
- The name of a subproject
- {1}
- The name of a repository
A subproject can only be associated with one repository
instance. This error message shouldn't appear in versions 8.0.1 or
later.
User response
Remove the association of the subproject from CARMA
before trying to associate it with a new repository instance.
CRRZC5001E
Extracting to a z/OS project resulted in an error. See the error log for more details.
Explanation
The local cache for CARMA is out of sync with the
local host, which has caused an error during extract.
User response
Refresh the parent in the CARMA view, and try again.
CRRZC5002E
Extracting to a z/OS project resulted in an error. See the error log for more details.
Explanation
CARMA unexpectedly lost connection to the host during
an extract.
User response
Check your network connection, reconnect to CARMA,
and try again.
CRRZC5004E
The subproject '{0}' is already associated with another Repository Manager: {1}
Explanation
- {0}
- The name of a subproject
- {1}
- The name of a repository
CARMA unexpectedly lost connection to the host during
an extract.
User response
Check your network connection, reconnect to CARMA,
and try again.
CRRZC5010E
The z/OS resource was not located on the host: {0}. Verify that the resource exists.
Explanation
- {0}
- The name of a remote system
During an extract from CARMA, the host resource
could not be found after the RAM was instructed to create it.
User response
During an extract, the RAM must create the host resource
before returning control back to CARMA. If this problem persists,
talk to your RAM developer.
CRRZC5100E
All the resources could not be copied into the RAM.
Explanation
When trying to copy multiple resources into the RAM
a subset of the resources did not copy.
User response
Verify which resources did not copy into the RAM
and retry. Also check the log for messages regarding the resources
that did not copy successfully.
CRRZC5101E
The CARMA resource associated with '{0}' was not found.
Explanation
- {0}
- 0
The mapping between the resource and the CARMA resource
is incorrect.
User response
Reassociate the resource with CARMA.
CRRZC5102E
Could not copy the resource: {0}
Explanation
- {0}
- Resource name
The local cache for CARMA is out of sync with the
local host, which has caused an error.
User response
Refresh the parent in the CARMA view, and try again.
CRRZC5103E
Could not copy the resource: {0}
Explanation
- {0}
- 0
CARMA unexpectedly lost connection to the host during
extract.
User response
Check your network connection, reconnect to CARMA,
and try again.
CRRZC5111E
The z/OS project resource, {0}, was not created.
Explanation
- {0}
- 0
Error adding the host resource to the z/OS sub project.
User response
Disconnect from RSE and reconnect, then try extracting
again.
CRRZC5200E
The project properties could not be retrieved for all members.
Explanation
There was an error receiving project properties for
one or more of the members.
User response
Check for associated error messages and follow their
user response.
CRRZC5201E
The CARMA resource associated with '{0}' was not found.
Explanation
- {0}
- 0
When attempting to retrieve properties for the listed
resource, CARMA could not find the associated CARMA object. This could
be caused by the identifier changing for CARMA object, possibly because
of an update to the RAM.
User response
Refresh the parent of the CARMA object, and extract
it again to the same location.
CRRZC5202E
The properties for resource {0} were not retrieved.
Explanation
- {0}
- 0
The mapping between the resource and the CARMA resource
is incorrect.
User response
Reassociate the resource with CARMA.
CRRZC5303E
The properties for resource {0} were not retrieved.
Explanation
- {0}
- 0
CARMA unexpectedly lost connection to the host while
retrieving project properties.
User response
Check your network connection, reconnect to CARMA,
and try again.
CRRZC5305W
Project properties cannot be copied from {0} because the SubProject is associated with {1}. Properties will still be copied from below this level and any previously copied project properties have not been changed.
Explanation
User response
CRRZC5400E
The remote member was not located. Verify that the remote member or dataset exists and try again.
Explanation
The sequential data set or PDS member that is selected
for extract into a z/OS project or upload into CARMA was not found.
User response
Verify that the remote member or data set exists,
and try the action again.
CRRZC5950E
The z/OS Subproject could not be associated with CARMA. See the error log for more details.
Explanation
CARMA encountered one or more errors when trying to
associate the z/OS subproject with CARMA.
User response
Check for associated messages and follow their UR.
Otherwise disconnect/reconnect RSE and try the extract again.
Messages for the z/OS Integrated Development Environment (zIDE)
These messages pertain to the z/OS Integrated Development Environment (zIDE)
in Rational Developer for System z.
CRRZI0001E
The backup of an existing workspace has failed. Contact your IBM technical support representative.
Explanation
Workspaces from WebSphere Developer 6.0 or 7.0 or
Rational Developer for System z 7.1 are updated to work in the latest
version of Rational Developer for System z when you open the workspace in Rational Developer for System z. The workspace is backed up before it is updated. This
message indicates that the backup operation failed.
User response
Contact IBM Software Support.
CRRZI0002I
A copy of your old workspace has been saved. It can be found at '{0}'.
Explanation
Workspaces from WebSphere Developer 6.0 or 7.0 or
Rational Developer for System z 7.1 are updated to work in the latest
version of Rational Developer for System z when you open the workspace in Rational Developer for System z. The workspace is backed up before it is updated. This
message indicates the location of the backup copy.
User response
No response is required.
CRRZI0003E
The workspace migration has failed. A backup copy of the original workspace can be found in '{0}'. Contact your IBM technical support representative.
Explanation
Workspaces from WebSphere Developer 6.0 or 7.0 or
Rational Developer for System z 7.1 are updated to work in the latest
version of Rational Developer for System z when you open the workspace in Rational Developer for System z. This message indicates that the update operation failed.
User response
Contact IBM Software Support.
CRRZI0004I
In IBM WebSphere Developer for zSeries 6.0.1, the Remote Error List view replaces the Problems view. Select Window->Show View->Other...->TPF Toolkit->Remote Error List or Window->Reset Perspective to open this view.
Explanation
The Remote Error List view is
not visible in the perspective in a workspace updated from a release
older than IBM WebSphere Developer for zSeries 6.0.1. This message
explains how to open the Remote Error List view,
which was introduced in WebSphere Developer for zSeries 6.0.1 to replace
the Problems view.
User response
Select Window>Show View>Remote Error List or Window>Reset Perspective to open the Remote
Error list view.
CRRZI0005E
The {0} environment variable is not set. Set the environment variable in the System Variables table of your operating system's environment variables. The value should point to the Developer for System z installation directory.
CRRZI0006E
The compiler option "CICS({0})" is not applicable for a build operation. Remove the suboption "{0}" and try again.
Explanation
The CICS suboption CTS31, CTS32, or CTS41 was specified
for a local build. These suboptions are valid only in the context
of syntax check.
User response
If you are running a local build, remove the CICS
suboption CTS31, CTS32, or CTS41.
CRRZI0007E
The compiler option "CICS('CTS32')" is not applicable for a build operation. Remove the suboption "CTS32" and try again.
Explanation
The CICS suboption CTS32 was specified for a local
build. This suboption is valid only in the context of syntax check
when the source code is being checked against the syntax of CICS Transaction
Server for z/OS 3.2.
User response
If you are building a local application, remove the CTS32
suboption from the CICS compiler option.
CRRZI0008E
The compiler option "CICS('CTS41')" is not applicable for a build operation. Remove the suboption "CTS41" and try again.
Explanation
The CICS suboption CTS41 was specified for a local
build. This suboption is valid only in the context of syntax check
when the source code is being checked against the syntax of CICS Transaction
Server for z/OS 4.1.
User response
If you are building a local application, remove the CTS41
suboption from the CICS compiler option.
CRRZI0009W
Data set {0} may be under SCLM control. To continue, type your user ID for the system.
Explanation
An attempt was made to delete a data set that might
be under control of SCLM.
User response
To continue deleting the data set, type your user
ID and password for the SCLM system and click OK.
CRRZI0010I
Resource {0} is under SCLM control. The file will be opened in read-only mode.
Explanation
An attempt was made to edit a resource that is under
control of SCLM.
User response
To edit the resource, access it by using the SCLM
Developer Toolkit.
CRRZI0011W
Resource {0} may be under SCLM control. Are you sure you want to proceed?
Explanation
An attempt was made to delete a resource that might
be under control of SCLM.
User response
To continue deleting the resource, click OK.
CRRZI0012E
{0} is under control of SCLM and cannot be modified.
Explanation
An attempt was made to modify a resource that is under
control of SCLM.
User response
To modify the resource, access it by using the SCLM
Developer Toolkit.
CRRZI0013I
An SCLM project definition module is found for {0}.
Explanation
The resource that is indicated in the message might
be under control of SCLM.
User response
No response is required.
CRRZI0014E
The include file cannot be opened until it is added to the current workspace. To import this file, select File -> Import.
Explanation
An attempt was made to open an include macro by using
the Open Include Macro action. The macro was
not added to the current workspace.
User response
To add the macro to the current workspace, use the File > Import action.
CRRZI0015E
The macro file cannot be found in the SYSLIB library. Verify that both the file and the library are allocated properly.
Explanation
An attempt was made to open an include macro by using
the Open Include Macro action. The macro cannot
be found in the SYSLIB library.
User response
To verify that the file was allocated properly, locate
the file in the
Remote Systems view by expanding
the
MVS Files subsystem in the remote system
connection.
To verify that the SYSLIB is specified correctly, do
these steps:
- Edit the property group associated with the resource.
- Click the Assembler tab in the property
group editor.
- Expand the procedure, select the step name, and click Edit in the Step Options area
of the page.
- Verify that the data sets specified in the Macro Libraries field is correct.
CRRZI0016E
The macro file could not be opened. Connect to the system before attempting this action.
Explanation
An attempt was made to open an include macro by using
the Open Include Macro action. The macro cannot
be opened because the remote system on which it is located is not
connected.
User response
To connect to the remote system, open the Remote
Systems view, select the remote system connection, and click Connect on the menu.
CRRZI0017I
You must add a corresponding filter for the data set before the member can be added to the project.
Explanation
You requested to add a copy member to a project from
an edit session, but there is no current filter for the data set name.
User response
In the Remote Systems view,
select MVS Files, and then select New > Filter to add a filter for the data set name.
CRRZI0018E
The copy library cannot be opened until it is added to the current workspace. To import this file, select File -> Import.
Explanation
You requested to open a copy library from an edit
session, but it is not yet added to your workspace.
User response
From the menu bar, click File > Import and browse to the copy library location to import it into your workspace.
CRRZI0019E
The copy file cannot be found in the SYSLIB library. Verify that both the file and the library are allocated properly.
Explanation
You requested to open or browse a remote copy member
from an edit session, but the file cannot be found in the SYSLIB.
User response
In the Remote Systems view, verify that the SYSLIB
library was allocated and that the copy member exists in this library.
Try the action again.
CRRZI0020E
The copy member could not be opened. Connect to the system before attempting this action.
Explanation
You requested to open or browse a remote copy member
from an edit session, but there is no connection to the remote system.
User response
In the Remote Systems view, select the remote system
and click Connect. After a connection is established,
try the action again.
CRRZI0021I
No text was highlighted. Highlight the copy member name.
Explanation
You requested to open a copy member in an edit session,
but no copy member was highlighted.
User response
Highlight the copy member name and try the action
again.
CRRZI0022E
The data set member '{0}' cannot be found. Verify that the data set and member exist on the remote system.
Explanation
You requested to open a data set or partitioned data
set member from a JCL edit session, but the file cannot be found.
User response
Verify that you selected a member name. In the Remote
Systems view, verify that the data set and member exist on the remote
system. Try the action again.
CRRZI0023I
The selected file '{0}' is already open in another edit session as a stored procedure. As a result, no additional edit session will be opened.
Explanation
You requested to edit a file that is already open
for editing.
User response
Look for the file name in another editor session
and edit it in that session.
CRRZI0024I
The selected file '{1}' is already open in the editor under a different project as '{0}'. As a result, no additional edit session will be opened.
Explanation
You requested to edit a file that is already open
for editing.
User response
Look for the file name in another editor session
and edit it in that session.
CRRZI0025E
The file cannot be opened until it is added to the current workspace. To import this file, select File -> Import.
Explanation
An attempt was made to open an include file by using
the Open Include File action. The file is not added
to the current workspace.
User response
To add the include file to the current workspace,
use the File > Import action.
CRRZI0026E
The file could not be opened. Connect to the system before attempting this action.
Explanation
An attempt was made to open an include file by using
the Open Include File action. The file cannot
be found in the SYSLIB library.
User response
To verify that the file exists in one of the data
sets specified in the SYSLIB concatenation, locate the data sets in
the
Remote Systems view. Expand the
MVS Files subsystem in the remote system connection.
Expand each data set in SYSLIB to find the member.
To verify that
the SYSLIB is specified correctly, do these steps:
- Edit the property group associated with the resource.
- Click the PL/I tab in the property group
editor and then select Procedures and Steps.
- Expand the procedure, select the step name, and click Edit in the Step Options area
of the page.
- Verify that the data sets specified in the Include
Libraries field is correct.
CRRZI0027E
The include file could not be opened. Connect to the system before attempting this action.
Explanation
An attempt was made to open an include file by using
the Open Include File action. The file cannot
be opened because the remote system on which it is located is not
connected.
User response
To connect to the remote system, open the Remote
Systems view, select the remote system connection, and click Connect on the menu.
CRRZI0029I
Local syntax check of a remote file is available only if the file is opened or edited from an MVS subproject.
Explanation
Attention: Local syntax check is deprecated.
An attempt was made to run a local syntax check on a file
that was opened for editing from the Remote Systems view.
User response
- Close the current edit session.
- Add the file to an MVS subproject.
- Try the local syntax check request again.
CRRZI0030W
The file cannot be saved. Do you want to check the syntax on the last saved copy of this file?
Explanation
Attention: Local syntax check is deprecated.
An attempt was made to run a local syntax check on a file
that was opened for editing. The latest changes to the file cannot
be saved, but the syntax check operation can be run on the copy stored
in the local cache.
User response
Click Yes to run the syntax
check on the cached copy.
CRRZI0031E
This file cannot be deleted because this is an offline remote file that has not been downloaded. To delete the file, you must move the project back online.
Explanation
You requested to delete a placeholder file in an offline
project. A placeholder file represents a remote file that is not downloaded
and does not exist in the local workspace. This message usually results
from an API operation rather than a user-interface operation.
User response
Move the project to online state and try the operation
again.
CRRZI0032E
This file cannot be deleted because this is an online remote file and the associated system is not connected. To delete the file, you must connect to the associated system.
Explanation
You requested to delete a file in a remote project,
but you are not connected to the remote system.
User response
Connect to the remote system and try the operation
again.
CRRZI0033E
This file cannot be moved because this is an offline remote file that has not been downloaded. To move the file contents you must move the project back online.
Explanation
You requested to move a placeholder file in an offline
project. A placeholder file represents a remote file that is not downloaded
and does not exist in the local workspace. This message usually results
from an API operation rather than a user-interface operation.
User response
Move the project to online state and try the operation
again.
CRRZI0034E
This file cannot be moved because this is an online remote file and the associated system is not connected. To move the file, you must connect to the associated system.
Explanation
You requested to move a file in a remote project,
but you are not connected to the remote system.
User response
Connect to the remote system and try the operation
again.
CRRZI0035E
This file's contents are not available because this is an offline remote file that has not been downloaded. To view the file's contents, you must move the project back online.
Explanation
You requested to open a placeholder file in an offline
project. A placeholder file represents a remote file that is not downloaded
and does not exist in the local workspace. This message usually results
from an API operation rather than a user-interface operation.
User response
Move the project to online state and try the operation
again.
CRRZI0036E
This file's contents are not available because this is an online remote file and the associated system is not connected. To view the file's contents, you must connect to the associated system.
Explanation
You requested to open a file in a remote project,
but you are not connected to the remote system.
User response
Connect to the remote system and try the operation
again.
CRRZI0037E
This file's contents cannot be modified because this is an offline remote file that has not been downloaded. To update the file's contents, you must move the project back online.
Explanation
You requested to edit a placeholder file in an offline
project. A placeholder file represents a remote file that is not downloaded
and does not exist in the local workspace. This message usually results
from an API operation rather than a user-interface operation.
User response
Move the project to online state and try the operation
again.
CRRZI0038E
This file's contents cannot be modified because this is an online remote file and the associated system is not connected. To update the file's contents, you must connect to the associated system.
Explanation
You requested to edit a file in a remote project,
but you are not connected to the remote system.
User response
Connect to the remote system and try the operation
again.
CRRZI0041E
Could not create IResources for {0}.
Explanation
An error occurred while accessing the contents of
a remote resource in a z/OS project.
User response
- Check the connection to determine whether the project is an online
project and then try the operation again.
- Clear the remote system cache files by selecting Window
> Preferences > Remote Systems > File Cache > Clear Cached Files, and then try the operation again.
- Re-create the project.
If the error occurs during normal use, contact IBM Software Support
to report the problem.
CRRZI0042E
Could not download {0}.
Explanation
Rational Developer for System z failed to download the file from the remote system to
the local cache.
User response
Check connection and try the operation again. If
the problem still occurs, contact IBM Software Support to report the
problem.
CRRZI0043E
Could not find file {0}.
Explanation
Rational Developer for System z failed to find the local cache file when reading or writing
contents of a remote resource in a z/OS project.
User response
If the project is online, check the remote system
connection and try the operation again. If the problem persists, contact
IBM Software Support to report the problem.
CRRZI0046E
Could not upload {0}.
Explanation
Rational Developer for System z failed to upload the file from local cache to the remote
system.
User response
Check the remote system connection and try the operation
again. If the problem still occurs, contact IBM Software Support to
report the problem.
CRRZI0047E
Could not write to {0}.
Explanation
An error occurred while writing contents to a file
in a z/OS project.
User response
Check the remote system connection and try the operation
again. If the problem still occurs, contact IBM Software Support to
report the problem.
CRRZI0048E
{0} is not a valid URL.
Explanation
An error occurred while accessing an internal resource
in a z/OS project.
User response
Contact IBM Software Support to
report the problem.
CRRZI0049E
The class '{0}' is not a valid classifier.
Explanation
An error occurred while creating an internal resource.
User response
Contact IBM Software Support to
report the problem.
CRRZI0050E
The data type '{0}' is not a valid classifier.
Explanation
An error occurred while creating an internal resource.
User response
Contact IBM Software Support.
CRRZI0051E
The system '{0}' is currently under host-based control but one or more remote projects associated with the same system already exist in this workspace. The non-host-based projects must be deleted before any host-based projects can be opened.
Explanation
A connection was made to a remote system on which
host-based projects are defined. One or more workstation-based projects exist
in the workspace. Host-based projects and workstation-based projects
associated with the same remote system cannot exist in the same workspace.
User response
Delete the workstation-based projects. Reconnect
to the remote system.
CRRZI0052E
An I/O error occurred while loading the host-based project configuration file: '{0}'.
Explanation
A connection was made to a remote system on which
host-based projects are defined. A host-based project cannot be loaded
into the z/OS Projects view because of an I/O error in the configuration
file shown.
User response
Contact your system administrator.
CRRZI0053E
A workbench error occurred while loading the host-based project configuration file: '{0}'.
Explanation
A connection was made to a remote system on which
host-based projects are defined. A host-based project cannot be loaded
into the z/OS Projects view because of a workbench error.
User response
Contact your system administrator.
CRRZI0054E
An I/O error occurred while loading the host-based project definition file: '{0}'.
Explanation
A connection was made to a remote system on which
host-based projects are defined. A host-based project cannot be loaded
into the z/OS Projects view because of an I/O error in the configuration
file shown.
User response
Contact your system administrator.
CRRZI0055E
Unable to find the project definition file '{0}' specified by the configuration file '{1}'.
Explanation
A connection was made to a remote system on which
host-based projects are defined. A host-based project cannot be loaded
into the z/OS Projects view because the project definition file shown
cannot be found.
User response
Contact your system administrator. The error can
have one of the following causes:
- The project definition file does not exist.
- The path name for the project definition file is specified incorrectly
in the configuration file.
CRRZI0056E
A workbench error occurred while loading the host-based project definition file: '{0}'.
Explanation
A connection was made to a remote system on which
host-based projects are defined. A host-based project cannot be loaded
into the z/OS Projects view because of a workbench error.
User response
Contact your system administrator.
CRRZI0058E
An I/O error occurred while loading the host-based subproject definition file: '{0}'.
Explanation
A connection was made to a remote system on which
host-based projects are defined. A host-based project cannot be loaded
into the z/OS Projects view because of an I/O error in the configuration
file shown.
User response
Contact your system administrator.
CRRZI0060E
A workbench error occurred while loading the host-based subproject definition file: '{0}'.
Explanation
A connection was made to a remote system on which
host-based projects are defined. A host-based project cannot be loaded
into the z/OS Projects view because of a workspace error.
User response
Contact your system administrator.
CRRZI0062E
A resource with the name '{0}' already exists in '{1}'. Make sure all the resources have a unique name and try again.
Explanation
An attempt to rename a resource failed because another
resource by that name exists.
User response
Try the operation again with a different name.
CRRZI0063E
The system name '{0}' found in the subproject definition file for subproject '{1}' does not match any currently defined systems.
Explanation
A subproject was loaded from a host-based project.
The remote system with which the subproject is associated does not
exist among the currently defined remote system connections.
User response
Contact your system administrator to modify the subproject
definition file to specify the correct remote system name.
CRRZI0065E
The subproject definition file for subproject '{0}' did not contain a system name.
Explanation
A subproject was loaded from a host-based project.
The subproject is not associated with a remote system.
User response
Contact your system administrator to modify the subproject
definition file to specify the correct remote system.
CRRZI0066E
The subproject definition file for subproject '{0}' did not contain any system information.
Explanation
A subproject was loaded from a host-based project.
The subproject is not associated with a remote system.
User response
Contact your system administrator to modify the subproject
definition file to specify the correct remote system name.
CRRZI0068I
The JCL member '{0}' is generated in data set '{1}'.
Explanation
This message reports the results of a generate JCL
action. In this message, {0} is the JCL file that
is generated and {1} is the name of the partitioned
data set to which the JCL file is added.
User response
No action is necessary.
CRRZI0069E
The operation did not complete because resource '{0}' is locked. Another person or program might be using the resource. Try the operation again when the resource is available.
Explanation
This message displays in response to an attempt to
update a locked resource.
User response
You can see the lock status of a remote file by looking
in the Properties view for the file. A locked
file shows a user ID in the Lock Owner row
of the properties table. An unlocked file shows no user ID in this
row.
CRRZI0070E
The specified data set for the generated JCL does not exist. Verify the name of the target data set and try again.
Explanation
A request was made to generate a JCL file, but the
target data set does not exist.
User response
Request a different data set or allocate the target
data set and resubmit the generation request.
CRRZI0071I
A member by this name already exists. Do you want to replace the existing member?
Explanation
You submitted a generate JCL request and specified
a JCL file name that exists in the partitioned data set.
User response
To generate the JCL and overwrite the existing JCL
file, click Yes. To cancel the generate JCL
request, click No.
CRRZI0073E
The system submitted a job based on your current user ID to perform a syntax check or a build. The status of this job cannot be determined because the JES filter might be incorrect or the job card might be invalid. Create a JES filter that matches this user ID, verify the job card, and try again.
CRRZI0074E
The JES subsystem is not connected. Connect to the subsystem and try the operation again.
Explanation
The JES subsystem is not connected.
User response
In the Remote Systems view, locate the remote system
on which the resource you are working with is located. Expand the
remote system connection, select JES, and then
click Connect on the menu.
CRRZI0075E
The submitted job has ended abnormally.
Explanation
A submitted job ended abnormally. This message also
includes the following message text:Click {0} to
view the job output or click {1} to view the build
properties currently in use.In
this message {0} is a link to the job output and {1} is
a link to the property group associated with the resource.
User response
To check the job output, click the job output link.
To check the build properties for the resource, click the property
group link.
CRRZI0076E
The submitted job ended with a JCL error.
Explanation
The submitted job failed because of a JCL error. This
message also includes the following message text:
Click {0} to view the job output or click {1}
to view the build properties currently in use.
In this message
{0} is a link to the job output and
{1} is a link to the property group associated with the resource.
User response
To check the job output, click the job output link.
To check the build properties for the resource, click the property
group link.
CRRZI0077W
The operation has been canceled on the workstation. The job {0} might need to be purged from JES.
Explanation
The execution of a job submission action was canceled.
User response
To purge the job, do these steps:
- In the Remote Systems view, locate the remote system on which
the resource you are working with is located.
- Expand the remote system connection and then expand JES > My Jobs.
- Select the job name indicated in the message and then select Purge from the menu.
CRRZI0078E
There is no property group associated with the subproject '{0}'. Associate a property group with the subproject and try the operation again.
Explanation
While running a build request for a subproject, the
system detected that no property group is associated with the subproject.
A property group is required to build a subproject. In this message, {0} is the subproject name.
User response
- From the z/OS Projects view, select the subproject
and then click .
- In the Associate Property Group window, choose
a property group to associate with the subproject and click OK.
- Try the build operation again.
CRRZI0079I
The alias, or the file it refers to, is already open in the editor.
Explanation
A request to edit an alias or the file it refers to
was made, but the file is already open in an editor.
User response
No response is required.
CRRZI0080W
This action deletes the alias '{0}'. Deleting an alias does not delete the referenced data set. Do you want to proceed?
Explanation
This message displays in response to a Delete menu
action when the resource selected in the view is a data set alias.
User response
- If you intend to delete the alias, click Yes.
- If you intend to delete the referenced data set, click No,
select the referenced data set in the view, and then try the Delete action
again.
- To disable this warning, open the MVS Files preference page and
clear the Show warning message on deleting alias check
box.
CRRZI0081W
This data set contains {0} members, and the expansion of the data set might take a long time. Do you want to proceed?
Explanation
The number of members in the partitioned data set
exceeds the warning threshold set in the MVS Files preference
page. This message gives you an opportunity to cancel the expansion
request.
User response
- To continue expanding the partitioned data set, click Yes.
- To cancel the expansion request, click No.
- To disable the warning, open the MVS Files preference
page and clear the Show warning message on expansion check
box.
- To change the warning threshold, open the MVS Files preference
page and specify a different number in the Maximum number
of members expanded without warning field.
CRRZI0082W
There is 1 line in the file '{0}' on the {1} with contents exceeding the maximum line length (see Details). Saving the file will result in truncation of this line. Do you want to continue?
Explanation
During a file comparison, a line in file {0} was modified so that its line length exceeds the maximum
length allowed by the data set characteristics. This message warns
that the line is truncated when the file is saved.
User response
- To save the file with the truncated line, click Yes.
- To cancel the save operation, click No.
You can then return to the editor, correct the line in error, and
try to save the file again.
CRRZI0083W
There are {0} lines in the file '{1}' on the {2} with contents exceeding the maximum line length (see Details). Saving the file will result in truncation of these lines. Do you want to continue?
Explanation
During a file comparison, multiple lines in file {1} were modified so that their line length exceeds the
maximum length allowed by the data set characteristics. This message
warns that the lines are truncated when the file is saved.
User response
- To save the file with the truncated lines, click Yes.
- To cancel the save operation, click No.
You can then return to the editor, correct the lines in error, and
try to save the file again.
CRRZI0084W
The file '{0}' is locked. It is either open in another edit session or locked by another user. This file will be opened in read-only mode. Do you want to continue?
Explanation
During a file comparison operation, the system found
that the file indicated by {0} is already open
in an edit session or locked by another user. This message gives you
an opportunity to cancel the file comparison operation or to continue
the operation with the file in read-only mode. If you continue with
the comparison operation, you are not able to edit the locked file.
User response
- To continue with the file comparison operation, click Yes. The file is opened in read-only mode and you are
not able to edit it.
- To cancel the file comparison operation, click No.
- To open the file in the comparison editor in edit mode, do one
of the following actions:
- Close the file in the current edit session.
- Wait until the file is no longer locked and try again.
CRRZI0085W
Both files are locked. They are either open in other edit sessions or locked by other users. The files will be opened in read-only mode. Do you want to continue?
Explanation
During a file comparison operation, the system found
that both files are already open in an edit session or locked by another
user. This message gives you an opportunity to cancel the file comparison
operation or to continue the operation with the files in read-only
mode. If you continue with the comparison operation, you are not able
to edit the locked files.
User response
- To continue with the file comparison operation, click Yes. The files are opened in read-only mode and you are
not able to edit them.
- To cancel the file comparison operation, click No.
- If you want to open the files in the comparison editor in edit
mode, do one of the following actions:
- Close the files in the current edit session.
- Wait until the files are no longer locked and try the file comparison again.
CRRZI0086W
The file '{0}' has a record format of '{1}' and the file '{2}' has a record format of '{3}'. The record formats do not match. Do you still want to continue?
Explanation
- {0}
- One of two files that are being compared.
- {1}
- The record format of file 0.
- {2}
- One of two files that are being compared.
- {3}
- The record format of file 2.
During a file comparison, the record format of file
{0} and
record format of file
{2} are displayed. If the
record formats of both files do not match, then the user is prompted
to confirm whether to continue with the file comparison.
User response
To continue with the file comparison, click Yes.
To cancel the file comparison operation, click No.
CRRZI0087W
The file '{0}' has a record length of '{1}' and the file '{2}' has a record length of '{3}'. The record lengths do not match. Do you still want to continue?
Explanation
- {0}
- One of two files that are being compared.
- {1}
- The record length of file 0.
- {2}
- One of two files that are being compared.
- {3}
- The record length of file 2.
During a file comparison, the record length of file
{0} and
record length of file
{2} are displayed. If the
record lengths of both files do not match, then the user is prompted
to confirm whether to continue with the file comparison.
User response
To continue with the file comparison, click Yes.
To cancel the file comparison operation, click No.
CRRZI0088E
The associated subsystem is not connected. Connect to the subsystem and try the operation again.
Explanation
The requested operation requires access to a remote
subsystem, such as MVS Files, z/OS UNIX Files, or JES.
User response
Connect to the subsystem and try the operation again.
CRRZI0089I
The data set is of type LIBRARY(PDSE). Compression is not required.
Explanation
The Compress or Compress with Backup action was requested for a data
set of type LIBRARY(PDSE). These actions are not supported for this
type of data set.
User response
No action is required.
CRRZI0090I
Success
Explanation
The installation verification procedure completed
successfully.
User response
No action is required.
CRRZI0091E
I/O Error
Explanation
An I/O error occurred when gathering data set information.
User response
CRRZI0092E
Write failed
Explanation
An I/O error occurred while uploading the file.
User response
CRRZI0093E
Read failed
Explanation
An I/O error occurred while downloading a file or
finding a record in it.
User response
CRRZI0094E
Write Initialization failed
Explanation
The process failed to initialize output while writing
to a file.
User response
CRRZI0095E
Read Initialization failed
Explanation
The process failed to initialize a file while reading
the file.
User response
CRRZI0096E
Dynamic allocation failed.
Explanation
A request to allocate a data set failed.
User response
CRRZI0097E
Open failed
Explanation
A request to open a data set failed.
User response
CRRZI0098I
The resource is not immediately available.
Explanation
The data set cannot be updated because it is being
updated by another user.
User response
Wait for the data set to become available, and try
the operation again.
CRRZI0099I
A previous request for control of the same resource was made for the same task.
Explanation
The data set cannot be updated because it is being
opened by other task.
User response
Disconnect from the remote system, and try the update
operation again. If the update fails again, collect the product
log files and contact IBM Software Support.
CRRZI0130E
Locate a catalog entry failed
Explanation
The LOCATE macro failed while retrieving information
from the catalog.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Return codes from LOCATE.
CRRZI0131E
ESTAE or GETMAIN return code was nonzero.
Explanation
The ESTAE or GETMAIN macro failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 164.
CRRZI0132E
DELETE failed because of unmatched device type causing a SCRATCH failure.
Explanation
An attempt to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 168.
CRRZI0133E
DELETE failed because of data set being currently open, causing a SCRATCH failure.
Explanation
An attempt to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 184.
CRRZI0134E
There was an I/O or unrecoverable error.
Explanation
A request to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 24.
CRRZI0135E
Unable to allocate a required catalog.
Explanation
A request to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Code, code 4.
CRRZI0136E
Insufficient space was supplied. The size of the calculated space is returned in the CTGFDBK area of the catalog parameter list.
Explanation
A request to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 40.
CRRZI0137E
Insufficient space was supplied. The size required is not known.
Explanation
A request to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 44.
CRRZI0138E
The function was not valid.
Explanation
A request to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 48.
CRRZI0139E
Security or password verification failure.
Explanation
A request to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 56.
CRRZI0140E
Either the data set was not found or the catalog could not be opened.
Explanation
A request to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 8.
CRRZI0141E
DELETE failed because of unexpired purge date causing a SCRATCH failure.
Explanation
An attempt to locate a catalog entry failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400):
Catalog Processor Return Codes, code 84.
CRRZI0142E
Read a DSCB failed
Explanation
A request to read a data set control block (DSCB)
failed with a return code of 4, 8, 12 or 16.
User response
CRRZI0143E
A permanent I/O error was encountered, or an invalid format-1 DSCB was found when processing the specified volume, or an unexpected error return code was received from CVAF (common VTOC access facility).
Explanation
A request to read a data set control block (DSCB)
failed with return code 12. This error can occur for the following
reasons:
- A permanent I/O error was encountered.
- An invalid format-1 DSCB was found when processing the specified
volume.
- An unexpected error return code was received from the common VTOC
access facility (CVAF).
User response
CRRZI0144E
Invalid work area pointer.
Explanation
A request to read a data set control block (DSCB)
failed with return code 16. This error is caused by an invalid work
area pointer.
User response
CRRZI0145E
The required volume was not mounted.
Explanation
A request to read a data set control block (DSCB)
failed with return code 4. This error can occur when the required
volume is not mounted.
User response
CRRZI0146E
The format-1 DSCB was not found in the VTOC of the specified volume.
Explanation
A request to read a data set control block (DSCB)
failed with return code 8. This error occurs when the format-1 DSCB
is not found in the VTOC of the specified volume.
User response
CRRZI0147E
Migrated Data Set failed
Explanation
A request to retrieve a migrated data set failed.
Retrieval of migrated data sets is not supported because of long recall
and transmission times.
User response
No action is required.
CRRZI0148E
Close failed
Explanation
During a request to rename or delete a file, the close
file operation failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0149E
Termination failed
Explanation
During a request to rename or delete a file, the termination
operation failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0151E
Get Directory failed
Explanation
The DFSMS macro DESERV GET_ALL function failed.
User response
CRRZI0152E
Start Command Server failed
Explanation
This error results from an APPC setup problem for
the TSO Commands service.
User response
CRRZI0188E
Create a thread failed.
Explanation
During a request to connect to a remote system server,
the process to create a thread failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821):
pthread_create()–Create a Thread.
CRRZI0189E
The system lacks the necessary resources to create another thread.
Explanation
During a request to connect to a remote system server,
the process to create a thread failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821):
pthread_create()–Create a Thread, error code
EAGAIN.
CRRZI0190E
The value specified by thread is not valid.
Explanation
During a request to connect to a remote system server,
the process to create a thread failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821):
pthread_create()–Create a Thread, error code
EINVAL.
CRRZI0191E
There is not enough memory to create the thread.
Explanation
During a request to connect to a remote system server,
the process to create a thread failed.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821):
pthread_create()–Create a Thread, error code
ENOMEM.
CRRZI0193E
Client/Server version mismatch
Explanation
An attempt was made to connect to a remote system
server from a version of the client that is not supported on that
server.
User response
Verify the client and server versions of Rational Developer for System z. Install the correct version of the client or connect
to a remote system that is compatible with the client.
CRRZI0194E
Record format not allowed
Explanation
This error occurs when downloading a load module or
program object. The transfer types of the source and target data sets
are different.
User response
- Diagnosing the problem
- Left-click the destination data set. Look at the Property view (the two-column table with headings Property and Value). Expand the Mapping property. You must see Transfer Binary in
both the source data set and the destination data set.
- This feature requires the client and server to be at least at
version 8.0.1.
- Solving the problem
- If the destination data set is Transfer Text, change it to Transfer Binary by doing one
of the following actions:
- For a single file:
- Right-click the destination data file and click Properties.
- Click Mapping.
- Click Other beneath Transfer
mode, click binary, and then click OK.
- For all files with a particular low-level qualifier:
- Click Window > Show View > z/OS file System Mapping. The view opens near the bottom of the workspace window.
- Right-click in the view and click Add data set mapping.
- Type a pattern in the Mapping Criterion field, for example, **LOADMOD. This mapping will apply to all future
data sets with that low-level qualifier.
- Click Other beneath the Transfer
mode, click binary, and then click OK.
CRRZI0195E
Unable to delete file
Explanation
A request to delete a data set failed.
User response
CRRZI0196E
Unable to rename file
Explanation
A request to rename a data set failed.
User response
CRRZI0197E
Directory update failed
Explanation
The STOW macro, update Partitioned Data Set Directory
(BPAM), failed.
User response
Ensure that you have write authority for the data
set. Contact your system administrator if you need assistance with
obtaining write authority.
CRRZI0198E
No space left in the directory.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed because there is no space left in the directory.
User response
Verify the amount of space in the directory. For
more information about this error, see the following topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408):
STOW Completion Codes.
CRRZI0199E
A permanent input or output error was detected. Control is not given to the error analysis (SYNAD) routine.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. A permanent input or output error was detected. Control
is not given to the error analysis (SYNAD) routine.
User response
Contact IBM Software Support. For more information
about this error, see the following topic in
z/OS V1R10.0 DFSMS
Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0200E
The system found an I/O error while trying to read or write the VTOC.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The system found an I/O error while trying to read
or write the VTOC.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0201E
A permanent I/O error occurred while attempting to write the EOF mark after the member. Control is not given to the error analysis (SYNAD) routine.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. A permanent I/O error occurred while attempting to
write the EOF mark after the member. Control is not given to the error
analysis (SYNAD) routine.
User response
Contact IBM Software Support. For more information
about this error, see the following topic in
z/OS V1R10.0 DFSMS
Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0202E
The system was unable to update the VTOC.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The system was unable to update the VTOC.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0203E
Either no secondary space is available or a DADSM user exit error occurred. The error occurred when trying to write an EOF; all primary space has been used.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. Either no secondary space is available or a DADSM
user exit error occurred. The error occurred when trying to write
an EOF; all primary space is used.
User response
Verify the availability of secondary space. For more
information about this error, see the following topic in
z/OS
V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes. For more information
about abend codes X'737', X'B37', X'D37', and X'E37', see
z/OS V1R10.0 MVS System Codes.
CRRZI0204E
Either no secondary space is available or a DADSM user exit error occurred.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. Either no secondary space is available or a DADSM
user exit error occurred.
User response
Verify the availability of secondary space. For more
information about this error, see the following topic in
z/OS
V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes. For more information
about abend codes X'737', X'B37', X'D37', and X'E37', see
z/OS V1R10.0 MVS System Codes.
CRRZI0205E
An error occurred while writing data buffered in system buffers. Control is not given to the error analysis (SYNAD) routine.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. An error occurred while writing data buffered in system
buffers. Control is not given to the error analysis (SYNAD) routine.
User response
Contact IBM Software Support. For more information
about this error, see the following topic in
z/OS V1R10.0 DFSMS
Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0206E
The specified data control block is not open or is opened for input, or a DEB error occurred.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The specified data control block is not open or is
opened for input, or a DEB error occurred.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0207E
The initialize function was specified but the PDSE was allocated with DISP=SHR. Use DISP=OLD or DISP=MOD.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The initialize function was specified, but the PDSE
was allocated with DISP=SHR.
User response
Use DISP=OLD or DISP=MOD. For more information about
this error, see the following topic in
z/OS V1R10.0 DFSMS Macro
Instructions for Data Sets:
STOW Completion Codes.
CRRZI0208E
Insufficient virtual storage was available to perform the STOW function.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. Insufficient virtual storage was available to run
the STOW function.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0209E
The caller attempted to issue add or replace for a member of the Program Management Library, which is a PDSE that contains program objects.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The caller attempted to issue add or replace for a member of the Program Management
Library, which is a PDSE that contains program objects.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0210E
The alias has an invalid TTR.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The alias has an invalid TTR.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0211E
The directory already contains the specified new name.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The directory already contains the specified new name.
User response
Verify the directory name. For more information about
this error, see the following topic in
z/OS V1R10.0 DFSMS Macro
Instructions for Data Sets:
STOW Completion Codes.
CRRZI0212E
User-supplied TTRs are in the user data field of the directory entry.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. User-supplied TTRs are in the user data field of the
directory entry (PDSEs only).
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0213E
The replace failed because you cannot replace an alias name if it is the same name as the primary member.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The request to replace the file failed because you
cannot replace an alias name if it is the same name as the primary
member (PDSEs only).
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0214E
The add or replace failed when attempting to add or replace an alias, but the member identified by the TTR did not exist.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The add or replace failed when attempting to add or replace an alias, but the member
identified by the TTR did not exist (PDSEs only).
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0215E
The replace failed when attempting to replace a primary member name while the PDSE is open for update and the member name identified an existing alias.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The replace failed when attempting to replace a primary
member name. The PDSE is open for update and the member name identified
an existing alias (PDSEs only).
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0216E
The replace failed when attempting to replace a primary member name while the PDSE is open for update, but the input TTR has not been defined for that member.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The replace failed when attempting
to replace a primary member name. The PDSE is open for update, but
the input TTR is not defined for that member (PDSEs only).
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0217E
The add failed because you cannot add a primary member name while the PDSE is open for update.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The add failed because you cannot
add a primary member name while the PDSE is open for update (PDSEs
only).
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0218E
The replace failed because you cannot replace a primary member name while the PDSE is open for update and the specified name does not exist.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The replace failed because you
cannot replace a primary member name while the PDSE is open for update
and the specified name does not exist (PDSEs only).
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0219E
One or more members were placed in a pending delete state; the space taken by those modules is not immediately available for reuse.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. One or more members were placed in a pending delete
state; the space taken by those modules is not immediately available
for reuse.
User response
For more information about this error, see the following
topic in
z/OS V1R10.0 DFSMS Macro Instructions for Data Sets:
STOW Completion Codes.
CRRZI0220E
The specified name could not be found.
Explanation
The STOW macro, updating partitioned data set directory
(BPAM), failed. The specified name cannot be found.
User response
Verify the name. For more information about this
error, see the following topic in
z/OS V1R10.0 DFSMS Macro Instructions
for Data Sets:
STOW Completion Codes.
CRRZI0221E
Dynamic allocation failure for PDS directory
Explanation
Allocating a data set by using dynalloc() failed.
User response
CRRZI0222E
Get all member names from PDS failed.
Explanation
The DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
User response
CRRZI0223E
The ID, length, or level of the parameter list is invalid.
Explanation
The DESERV macro GET_ALL function failed. The ID,
length, or level of the parameter list is invalid. This function retrieves
all member names and directory entries from a PDSE or PDS.
User response
CRRZI0224E
This function requires a PDSE data set.
Explanation
The DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
It requires a PDSE data set.
User response
CRRZI0225E
The concatenation number specified is greater than the concatenation number of the last data set in the concatenation.
Explanation
The DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS,
failed. The concatenation number specified is greater than the concatenation
number of the last data set in the concatenation.
User response
CRRZI0226E
Address of the DEB is 0 or DEB is input but the DCB pointed to by the DEB does not point back to the DEB.
Explanation
DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS. The
address of the DEB is 0 or the DEB is input but the DCB that the DEB
points to does not point back to it.
User response
CRRZI0227E
The passed DCB is not open.
Explanation
DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
The passed DCB is not open.
User response
CRRZI0228E
The address of the DCB is zero.
Explanation
DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
The address of the DCB is zero.
User response
CRRZI0229E
To pass the DEB the caller must be supervisor state or a system key.
Explanation
DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
To pass the DEB the caller must be in supervisor state or a system
key.
User response
CRRZI0230E
The FUNC value is incorrect.
Explanation
The DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
The FUNC value is incorrect.
User response
CRRZI0231E
The gap specified is too large. The gap must be larger than DESP_ENTRY_GAP_MAX.
Explanation
The DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
The gap specified is too large. The gap must be larger than DESP_ENTRY_GAP_MAX.
User response
CRRZI0232E
The address of the AREAPTR is 0.
Explanation
The DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
The address of the AREAPTR is 0.
User response
CRRZI0233E
The connect intent specified is not valid with this function.
Explanation
The DESERV macro GET_ALL function failed This function
retrieves all member names and directory entries from a PDSE or PDS.
The connect intent specified is not valid with this function.
User response
CRRZI0234E
The CONN_INTENT(HOLD) requires the caller of function GET_ALL to be in supervisor state or system key.
Explanation
DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
The CONN_INTENT(HOLD) requires the caller of function GET_ALL to be
in supervisor state or system key.
User response
CRRZI0235E
The DEBCHK macro failed. The DCB or DEB is invalid.
Explanation
The DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
The DEBCHK macro failed. The DCB or DEB is invalid.
User response
CRRZI0236E
FREEMAIN failure.
Explanation
The DESERV macro GET_ALL function failed. This function
retrieves all member names and directory entries from a PDSE or PDS.
FREEMAIN failure.
User response
CRRZI0237E
No members in directory.
Explanation
The DESERV GET_ALL function failed. This function
retrieves SMDEs for all member names (primary and alias) of a PDSE
and can establish connections to members. The directory contains no
members.
User response
CRRZI0238E
Get PDS directory information failed.
Explanation
The BLDL macro failed. This macro obtains a list of
information from the directory of a partitioned data set or partitioned
data set extended (PDSE).
User response
CRRZI0239E
One or more entries in the list could not be filled; the list supplied can be invalid.
Explanation
The BLDL macro failed. This macro obtains a list of
information from the directory of a partitioned data set or partitioned
data set extended (PDSE). One or more entries in the list cannot be
filled; the list supplied can be invalid.
User response
CRRZI0240E
A permanent I/O error was detected when the system attempted to search the directory.
Explanation
The BLDL macro failed. This macro obtains a list of
information from the directory of a partitioned data set or partitioned
data set extended (PDSE). A permanent I/O error was detected when
the system attempted to search the directory.
User response
CRRZI0241E
Insufficient virtual storage was available.
Explanation
The BLDL macro failed. This macro obtains a list of
information from the directory of a partitioned data set or partitioned
data set extended (PDSE). Insufficient virtual storage was available.
User response
CRRZI0242E
Invalid data extent block (DEB), or the DEB is not owned by a TCB in the current family of TCBs, or the UCB address in the DEB is zero.
Explanation
The BLDL macro failed. This macro obtains a list of
information from the directory of a partitioned data set or partitioned
data set extended (PDSE). This error has one of the following causes:
- A data extent block (DEB) is invalid.
- The DEB is not owned by a TCB in the current family of TCBs.
- The UCB address in the DEB is zero.
User response
CRRZI0275E
Operation terminated.
Explanation
A Language Environment operation failed.
User response
Verify that you are using the correct version of
Language Environment and that it is set up correctly. For more information
about this error, see the
rsecomm.log and
ffs*.log files on the remote system. For more information
about these files, see Chapter 12, "Troubleshooting configuration
problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290).
CRRZI0277E
System ABEND {0}.
Explanation
- {0}
- The abend code.
A system ABEND occurred.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0278E
The OPEN/EOV volume security exit requested that the volume be rejected.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0279E
An OPEN was issued for a RACF-protected data set to which the caller was not authorized.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0280E
A data set opened for output used all the primary space, and no secondary space was requested.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0281E
An installation DADSM exit, IGGPRE00, rejected the extend request.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0282E
A data set opened for output used all space available to or on the current volume, and no more volumes were available.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0283E
A multi-volume physical sequential data set was being written on a direct access device. All space was filled on the volume, and an attempt was made to obtain space on the next specified volume. Either the space was not available on that volume, the data set already existed on that volume, or there is no space available in the VTOC or the VTOC index.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0284E
I/O operation failed.
Explanation
An I/O operation failed when renaming data set.
User response
Determine whether there is a resource shortage and
try the operation again.
CRRZI0285E
TGET macro failed.
Explanation
An I/O operation failed because the TGET macro failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0286E
TPUT macro failed.
Explanation
An I/O operation failed because the TPUT macro failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0287E
Provide relative position failed.
Explanation
An I/O operation failed because an attempt to provide
a relative position failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0288E
DEVTYPE macro failed.
Explanation
An I/O operation failed because the DEVTYPE macro
failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0289E
RDJFCB macro failed.
Explanation
An I/O operation failed because the RDJFCB macro failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0290E
TRKCALC macro failed.
Explanation
An I/O operation failed because the TRKCALC macro
failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0291E
Cataloging a non-VSAM data set failed.
Explanation
An I/O operation failed because an attempt to catalog
a non-VSAM data set failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0292E
Uncataloging a non-VSAM data set failed.
Explanation
An I/O operation failed because of an attempt to uncatalog
a non-VSAM data set failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0293E
Renaming a data set in the VTOC failed.
Explanation
An I/O operation failed because an attempt to rename
a data set in the VTOC failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0294E
No volume containing any part of data set was mounted, nor was there a unit available for mounting.
Explanation
An I/O operation failed because no volume that contains
any part of the data set was mounted and no unit was available for
mounting.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0295E
An unusual condition was encountered on one or more volumes.
Explanation
An I/O operation failed because an unusual condition
was encountered on one or more volumes.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0296E
Deleting a data set from the VTOC failed.
Explanation
An I/O operation failed because an attempt to delete
a data set from the VTOC failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0297E
Position for access failed.
Explanation
An I/O operation failed because a request for the
position for access failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0298E
Dynamic allocation failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0299E
Duplicate data set name on the volume.
Explanation
Dynamic allocation failed because of duplicate data
set names on the volume.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0300E
The volume table of contents (VTOC) for the specified or defaulted volume for a new data set request had insufficient space in the VTOC index for a new entry, or did not have the minimum number of data set control blocks (DSCBs) required to allocate the data set.
Explanation
Dynamic allocation failed for one of the following
reasons:
- The volume table of contents (VTOC) for the specified or defaulted
volume for a new data set request had insufficient space in the VTOC
index for a new entry.
- The VTOC did not have the minimum number of data set control blocks
(DSCBs) required to allocate the data set.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0301E
Space on the direct access storage device (DASD) containing the requested volume could not be obtained.
Explanation
Dynamic allocation failed because space on the direct
access storage device (DASD) containing the requested volume cannot
be obtained.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0302E
Requested absolute track is not available.
Explanation
Dynamic allocation failed because the requested absolute
track is not available.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0303E
More space was requested than is available on the DASD volume, or the DASD volume's VTOC is full, or the DASD volume's VTOC Index (VTOCIX) is full.
Explanation
Dynamic allocation failed for one of the following
reasons:
- More space was requested than is available on the DASD volume.
- The VTOC of the DASD volume is full.
- The VTOC Index (VTOCIX) of the DASD volume is full.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0304E
The average block length specified on text unit key DALAVGR (key 0009) was greater than the track capacity of the requested DASD volume.
Explanation
Dynamic allocation failed because the average block
length on text unit key DALAVGR (key 0009) was greater than the track
capacity of the requested DASD volume.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0305E
Invalid DADSM REALLOC parameter list.
Explanation
Dynamic allocation failed because of an invalid DADSM
REALLOC parameter list.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0306E
The system did not allocate the directory for a new partitioned data set (PDS) because the space requested for the directory on text unit key DALDIR (key 000C) exceeded the space available on the specified volume.
Explanation
Dynamic allocation failed because the system did not
allocate the directory for a new partitioned data set (PDS). The space
requested for the directory on text unit key DALDIR (key 000C) exceeded
the space available on the specified volume.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0307E
No space parameter given for a new data set or zero space requested at absolute track zero.
Explanation
Dynamic allocation failed because no space parameter
was given for a new data set or zero space was requested at absolute
track zero.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0308E
A profile for the specified data set on this volume already exists in the Resource Access Control Facility (RACF) data set.
Explanation
Dynamic allocation failed because a profile for the
specified data set on this volume exists in the Resource Access Control
Facility (RACF) data set.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0309E
User is not authorized to define this data set. The user has the automatic data set protection characteristic without the RACF authorization to define data sets.
Explanation
Dynamic allocation failed because the user is not
authorized to define this data set. The user has the automatic data
set protection characteristic without the RACF authorization to define
data sets.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0310E
Installation exit rejected this request.
Explanation
Dynamic allocation failed because the installation
exit rejected this request.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0311E
Space request was rejected by installation exit.
Explanation
Dynamic allocation failed because a space request
was rejected by the installation exit.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files
on the remote system. For more information about these files, see
Chapter 12,
"Troubleshooting configuration problems", in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0312E
Non-SMS managed data set cannot be created on an SMS-managed volume.
Explanation
Dynamic allocation failed because a non-SMS managed
data set cannot be created on an SMS-managed volume.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0313E
An unexpected or internal error code was received by Allocation.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0314E
Required CATALOG volume is currently not mounted.
Explanation
Dynamic allocation failed because a required CATALOG
volume is currently not mounted.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0315E
Either the existing catalog structure is inconsistent with the operation, or the program was not authorized to perform the operation.
Explanation
Dynamic allocation failed because either the existing
catalog structure is inconsistent with the operation, or the program
was not authorized to run the operation.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0316E
The index structure necessary to catalog the data set does not exist.
Explanation
Dynamic allocation failed because the index structure
necessary to catalog the data set does not exist.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0317E
CATALOG space is exhausted on the control volume.
Explanation
Dynamic allocation failed because CATALOG space is
exhausted on the control volume.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0318E
A CATALOG I/O error has occurred.
Explanation
Dynamic allocation failed because a CATALOG I/O error occurred.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0319E
CATALOG error.
Explanation
Dynamic allocation failed, because of a CATALOG error.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0320E
Data set not on volume as indicated in the catalog or volume text unit.
Explanation
Dynamic allocation failed, because the data set was
not on the volume as indicated in the catalog or volume text unit.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0321E
OBTAIN I/O error. During data set allocation, an uncorrectable I/O error occurred when the system attempted to obtain a data set control block (DSCB).
Explanation
Dynamic allocation failed because of an OBTAIN I/O
error. During data set allocation, an uncorrectable I/O error occurred
when the system attempted to obtain a data set control block (DSCB).
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0322E
An invalid work area pointer was supplied.
Explanation
Dynamic allocation failed because an invalid work
area pointer was supplied.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0323E
The absolute address passed was not within the boundaries of the VTOC.
Explanation
Dynamic allocation failed because the absolute address
passed was not within the boundaries of the VTOC.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0324E
Virtual storage unavailable.
Explanation
Dynamic allocation failed because virtual storage
is unavailable.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0325E
Request for exclusive use of a shared data set cannot be honored.
Explanation
Dynamic allocation failed because a request for exclusive
use of a shared data set cannot be completed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0326E
Requested data set is unavailable. The data set is allocated to another job and its usage attribute conflicts with this request.
Explanation
Dynamic allocation failed because the requested data
set is unavailable. The data set is allocated to another job and its
usage attribute conflicts with this request.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0327E
Device(s) not available.
Explanation
Dynamic allocation failed because one or more devices
are not available.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0328E
Specified volume or an acceptable volume is not mounted, and user does not have volume mounting authorization through the DYNALLOC request.
Explanation
Dynamic allocation failed. The specified volume or
an acceptable volume is not mounted, and the user is not authorized
to mount a volume through the DYNALLOC request.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0329E
Device name specified is undefined.
Explanation
Dynamic allocation failed because the device name
specified is undefined.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0330E
Requested volume is not available.
Explanation
Dynamic allocation failed because the requested volume
is not available.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0331E
Eligible device types do not contain enough devices.
Explanation
Dynamic allocation failed because eligible device
types do not contain enough devices.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0332E
Specified volume or device in use by system.
Explanation
Dynamic allocation failed because the specified volume
or device is in use by the system.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0333E
Volume mounted on ineligible permanently resident or reserved device.
Explanation
Dynamic allocation failed because the volume is mounted
on an ineligible permanently resident or reserved device.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0334E
Permanently resident or reserved volume on required device.
Explanation
Dynamic allocation failed because a permanently resident
or reserved volume is on the required device.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0335E
More than one device required for a request specifying a specific device.
Explanation
Dynamic allocation failed because more than one device
is required for a request that specifies a device.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0336E
Space unavailable in task input output table (TIOT).
Explanation
Dynamic allocation failed because space is unavailable
in the task input/output table (TIOT).
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0337E
Required catalog is not mounted, and user does not have volume mounting authorization.
Explanation
Dynamic allocation failed because the required catalog
is not mounted, and the user is not authorized to mount a volume.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0338E
CATALOG LOCATE error. Either the data set name specified is in error, or a system error occurred when processing the data set name.
Explanation
Dynamic allocation failed because of a CATALOG LOCATE
error. Either the data set name specified is in error, or a system
error occurred when processing the data set name.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0339E
Permanent I/O error processing cataloged data set.
Explanation
Dynamic allocation failed because of a permanent I/O error while
processing the cataloged data set.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0340E
Insufficient real or virtual storage for processing cataloged data set.
Explanation
Dynamic allocation failed because of insufficient
real or virtual storage for processing the cataloged data set.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0341E
An unsuccessful attempt was made to access a catalog that was locked for recovery. The job does not have the proper authorization to perform this function.
Explanation
Dynamic allocation failed because an unsuccessful
attempt was made to access a catalog that was locked for recovery.
The job does not have authorization to run this function.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0342E
An unexpected return code was returned by catalog LOCATE.
Explanation
Dynamic allocation failed because an unexpected return
code was returned by catalog LOCATE.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0343E
Dynamic allocation of new file failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0344E
Dynamic deallocation failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0345E
Output data was truncated.
Explanation
An I/O operation failed because the output data was
truncated.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0346E
FCB is corrupted.
Explanation
An I/O operation failed because the file control block
is corrupted.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0347E
There was no room left in a physical record for anymore DBCS characters.
Explanation
An I/O operation failed because there was no room
left in a physical record for any more DBCS characters.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0348E
There was not enough room in a record to start any DBCS string or a redundant SO was written to the file before an SI.
Explanation
An I/O operation failed for one of the following reasons:
- There was not enough room in a record to start any DBCS string.
- A redundant SO was written to the file before an SI.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0349E
There was not enough room to start a DBCS string and data was written anyway, with an SI to end it.
Explanation
An I/O operation failed because there was not enough
room to start a DBCS string and data was written anyway with an SI
to end it.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0350E
An SI was written before the last double byte character is completed, thereby forcing z/OS to fill in the last byte of the DBCS string with a padding byte X'FE'.
Explanation
An I/O operation failed because an SI was written
before the last double byte character was completed. z/OS must complete
the last byte of the DBCS string with a padding byte X'FE'.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0351E
An attempt was made to extend a file that allows writing, but the file cannot be extended.
Explanation
An I/O operation failed because an attempt was made
to extend a file that allows writing, but the file cannot be extended.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0352E
OPEN macro failed.
Explanation
An I/O operation failed because the OPEN macro failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0353E
CLOSE macro failed.
Explanation
An I/O operation failed because the CLOSE macro failed.
User response
For more information about this error, see the
rsecomm.log and
ffs*.log files on
the remote system. For more information about these files, see Chapter
12, "Troubleshooting configuration problems," in the
IBM Rational Developer for System z Host Configuration
Reference (SC14-7290). Consult with your system administrator.
If you cannot solve the problem, contact IBM Software Support.
CRRZI0354E
Find a data set member failed.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member.
User response
CRRZI0355E
Name not found.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member. The data set
name was not found.
User response
CRRZI0356E
The PDSE is open for output and the FIND macro was issued to point to a member other than the one currently processing.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member. The PDSE is
open for output and the FIND macro was issued to point to a member
other than the one currently processing.
User response
CRRZI0357E
The caller has only RACF execute authority to the PDSE.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member. The caller has
only RACF execute authority to the PDSE.
User response
CRRZI0358E
The PDSE member's share options do not allow you to access it.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member. The share options
of the PDSE member do not allow you to access it.
User response
CRRZI0359E
Permanent I/O error during directory search.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member. A permanent
I/O error occurred during the directory search.
User response
CRRZI0360E
An I/O error occurred while flushing system buffers containing member data.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member. An I/O error
occurred while flushing system buffers containing member data.
User response
CRRZI0361E
No DCB address was input.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member. No DCB address
was provided.
User response
CRRZI0362E
Insufficient virtual storage available.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member. Insufficient
virtual storage is available.
User response
CRRZI0363E
Invalid DEB, or DEB is not owned by a TCB in the current family of TCBs.
Explanation
The FIND macro, Establish the Beginning of a Data Set
Member (BPAM), failed when finding a data set member. The DEB is invalid
or not owned by a TCB in the current family of TCBs.
User response
CRRZI0365E
Out of memory.
Explanation
An out of memory error occurred.
User response
Verify memory usage and increase the memory heap
size.
CRRZI0366E
Code page conversion failed with {0}.
Explanation
- {0}
- The name of the function for which the code page conversion failed.
User response
CRRZI0367E
Code page {0} is not supported.
Explanation
- {0}
- The unsupported code page.
The code page conversion failed because the code
page is not supported.
User response
Verify that the correct code page is used. If correcting
the code page does not resolve the error, contact IBM Software Support.
CRRZI0369E
Lock failed.
Explanation
An attempt to lock the requested file failed. Another
user might have a lock on the file.
User response
Verify whether another user locked the file and try
the operation again. If the file is not locked by another user, verify
that you have authority to lock the file.
CRRZI0370E
A previous request for control of the same resource has been made for the same task. The task does not have control of the resource.
Explanation
An attempt to lock the requested file failed. Another
user might have a lock on the file.
User response
Verify whether another user locked the file and try
the operation again. If the file is not locked by another user, verify
that you have authority to lock the file.
CRRZI0371E
Invalid resource name.
Explanation
An attempt to lock the requested file failed. The
resource name that was provided is invalid.
User response
Verify whether another user locked the file and try
the operation again. If the file is not locked by another user, verify
that you have authority to lock the file. If these actions do not
solve the problem, contact IBM Software Support.
CRRZI0372E
The resource is not immediately available.
Explanation
An attempt to lock the requested file failed. Another
user might have a lock on the file.
User response
Verify whether another user locked the file and try
the operation again. If the file is not locked by another user, verify
that you have authority to lock the file.
CRRZI0373E
A previous request for control of the same resource has been made for the same task. The task has control of the resource.
Explanation
An attempt to lock the requested file failed. Another
user might have a lock on the file.
User response
Verify whether another user locked the file and try
the operation again. If the file is not locked by another user, verify
that you have authority to lock the file.
CRRZI0374E
Unlock failed.
Explanation
An attempt to lock the requested file failed. Another
user might have a lock on the file.
User response
Verify whether another user locked the file and try
the operation again. If the file is not locked by another user, verify
that you have authority to lock the file.
CRRZI0375E
The resource has been requested for the task, but the task has not been assigned control of it. The task continues waiting.
Explanation
An attempt to lock the requested file failed. Another
user might have a lock on the file.
User response
Verify whether another user locked the file and try
the operation again. If the file is not locked by another user, verify
that you have authority to lock the file.
CRRZI0376E
Control of the resource has not been requested by the active task, or the resource has already been released.
Explanation
An attempt to lock the requested file failed. Another
user might have a lock on the file.
User response
Verify whether another user locked the file and try
the operation again. If the file is not locked by another user, verify
that you have authority to lock the file.
CRRZI0377E
Internal server error occurred.
Explanation
An unexpected internal server error occurred.
User response
CRRZI0378E
Exception occurred.
Explanation
An unexpected server error occurred.
User response
CRRZI0379E
The request has timed out because there is no response from the server.
CRRZI0380E
No response from TSO command server.
Explanation
This error can occur while attempting to allocate
a partitioned or sequential data set. Your user ID does not have the
necessary permission and there is no ISPF Client Gateway in /var/rdz/WORKAREA. This work area must be allocated and
all Rational Developer for System z users must have permission to write to the work area.
User response
- To determine whether the work area was created, issue the following
commands from either telnet or MVS:
cd /var/rdz
ls -al
- If the WORKAREA directory does not exist,
then create it by issuing the following command:
mkdir WORKAREA
- Set the permissions so that all users have write authority:
chmod 777 /var/rdz/WORKAREA
- To ensure that a log directory is created and that users have
write authority for it, issue the following commands and look for
the logs directory:
cd /var/rdz
ls -al
- If the "logs" directory does not exist, then create it by issuing
the following command:
mkdir logs
- To set the permissions so that all users have write authority
to the /var/rdz/logs directory, issue the following
command:
chmod 777 logs
CRRZI0383E
The data set compression has failed.
Explanation
A request to compress a partitioned data set failed.
If you used the Compress with Backup action,
then a backup copy of the data set is saved. In some cases, the failure
might occur before the data set is backed up. In this case, a backup
copy is not created.
User response
If you used the Compress with Backup action and the failure occurred after the backup, then you can restore
the data set from the backup copy.
CRRZI0384E
The data set compression has failed. Data Set is missing.
Explanation
A request to compress a partitioned data set failed
because the target data set cannot be found. A backup data set is
not created.
User response
Select a valid data set and try the operation again.
CRRZI0385E
The data set compression has failed. The data set is not a PDS.
Explanation
A request to compress a data set failed because the
target data set is not a partitioned data set. The compress action
is not valid for data sets of type sequential or PDSE (Library). A
backup data set is not created.
User response
Select a partitioned data set and try the operation
again.
CRRZI0386E
Data set compression has failed. Problems in allocating SYSUT data set. See the Error log for more details.
CRRZI0387E
Data set compression has failed. Problems creating the backup data set. See the Error log for more details.
Explanation
A request to compress a data set failed. An attempt
to back up the data set before compressing it failed.
User response
CRRZI0388E
The data set compression has failed. See the Error log for more details.
CRRZI0389E
Copy command has failed.
CRRZI0390E
Copy command has failed. Problem in allocating SYSUT data set. See the Error log for more details.
Explanation
A copy command failed, because the request to allocate
the SYSUT data set failed.
User response
CRRZI0391E
Copy command has failed. See the Error log for more details.
CRRZI0393E
ALLOCATE failed. Record length is inconsistent with block size for this record format.
CRRZI0394E
Server initialization failed.
CRRZI0395E
Migrate failed.
CRRZI0396E
Recall failed.
Explanation
An HRECALL command failed.
User response
CRRZI0397E
Delete failed.
Explanation
An HDelete operation for a migrated
data set failed.
User response
CRRZI0398E
Server internal error. TSO server cannot be located.
Explanation
The TSO command server did not start normally.
User response
CRRZI0399E
Server internal error. Bad TSO server response {0}.
Explanation
The TSO command server returned a bad response.
User response
CRRZI0400E
Server internal error. Command target is not set.
Explanation
An internal command that was sent by the Rational Developer for System z client is incomplete. This message indicates an internal
logic error.
User response
CRRZI0401E
Server internal error. Unsupported command {0}.
Explanation
File Manager Integration detected an unsupported
command sent by the Rational Developer for System z client.
User response
Contact IBM Software Support.
CRRZI0402E
Server internal error. Undefined message number {0}.
Explanation
- {0}
- An undefined message number.
A server internal error occurred, but the message
number is not defined in the resource file. This error might be caused
by an inconsistency between the installed modules.
User response
Check that the installation finished correctly. If
completing the installation does not solve the problem, contact IBM
Software Support.
CRRZI0405E
Server internal error. Bad resource type {0}.
Explanation
- {0}
- The resource type is:
- 1: Sequential data set
- 2: Partitioned data set
- 3: Migrated data set
- 4: Offline data set
- 5: Alias
- 6: VSAM data set
- 7: Undefined
- 8: Volume serial number
- 9: PDS(E)
- 10: Generation data group
- 12: Cluster
A severe internal error occurred while synchronizing
the
Rational Developer for System z client and server.
User response
CRRZI0408E
Server internal error. Exception occurred.
Explanation
A severe internal error occurred.
User response
CRRZI0410E
Server internal error. Unknown target container type.
Explanation
The target data set is not supported as a target data
set for a COPY or MOVE operation.
User response
Select the correct target data set for the COPY or
MOVE operation.
CRRZI0411E
Server internal error. Bad ENQUEUE name {0}.
Explanation
- {0}
- An invalid ENQUEUE name.
An internal server error occurred.
User response
Contact IBM Software Support.
CRRZI0412E
Failed to open file {0} in the editor.
Explanation
- {0}
- File name.
An internal error occurred while
the product was opening a file in an editor.
User response
No action is required.
CRRZI0414W
The build dependencies might have changed since the last syntax check. You might want to recheck its dependencies before proceeding with the syntax check.
Explanation
Copybook or include files changed since the last
syntax check.
User response
Request the Check Dependencies action
and then try the operation again.
CRRZI0415W
Check the dependencies before proceeding with the syntax check.
Explanation
The product must gather information that pertains
to the copybooks or include files that are used by the source program.
User response
Request the Check Dependencies action.
CRRZI0416W
File type {0} is not a local file.
Explanation
- {0}
- File type.
An internal error occurred when the product was
opening a remote resource.
User response
No action is required.
CRRZI0417E
Could not retrieve an editable file for resource {0} of type {1}.
Explanation
- {0}
- Resource name
- {1}
- Resource type
An internal error occurred.
User response
No action is required.
CRRZI0418E
Could not retrieve an editor object for resource {0} of type {1}.
Explanation
- {0}
- Resource name
- {1}
- Resource type
An internal error occurred.
User response
No action is required.
CRRZI0419E
Could not retrieve a remote file for resource {0} of type {1}.
Explanation
- {0}
- Resource name
- {1}
- Resource type
An internal error occurred.
User response
No action is required.
CRRZI0420I
The file {0} will be opened for read only.
Explanation
- {0}
- File name
A request was made to open a file, but the user
is not authorized to write to the file.
User response
Obtain write access to file and try the operation
again. If you cannot obtain write access, copy the file to a partitioned
data set that you have write access to and edit the copied file.
CRRZI0421E
Could not perform the refresh dependencies operation.
Explanation
The job that was submitted to the remote system failed.
User response
To determine whether the job completed or JCL errors
occurred, examine the job output under the JES node in the Remote
Systems view. If there are JCL errors, the entry fields
in the compilation step of the Procedures and Steps page
might point to data sets that do not exist. To verify that the specified
data sets exist, click Validate Data Sets.
CRRZI0422I
For local syntax check to perform correctly, make sure that all the dependent libraries referenced by this file are also added to this MVS subproject. You can use "Show Dependencies" to reveal the dependent libraries, and then add them to your MVS subproject.
CRRZI0423E
This operation cannot be performed because error feedback is not supported when either the DB2 precompiler or the CICS translator option is set.
Explanation
The product relies on error feedback from the compiler
to check syntax remotely. When error feedback is not available, a
remote syntax check cannot be completed.
User response
Verify that the DB2 precompiler or the CICS translator
options are required. If so, then remote syntax check cannot be completed.
CRRZI0424E
Could not perform the remote syntax check operation.
Explanation
The compilation job that was submitted to the remote
system failed.
User response
To verify that the job completed successfully, look
in the job output under the JES node in the Remote Systems view.
If there is a syntax error, verify that the entry fields in the compilation
step on the Procedure and Steps page are correct.
To verify that the partitioned data sets that are specified exist,
click Validate Data Sets.
CRRZI0425E
Could not perform the show dependencies operation.
Explanation
The job that was submitted to the remote system failed.
User response
Examine the job output to see whether the job completed
or JCL errors occurred. If JCL errors occurred, the entry fields in
the compilation step of the Procedures and Steps page
might point to data sets that do not exist. To verify that the specified
data sets exist, click Validate Data Sets.
CRRZI0426E
The property group associated with this resource does not have the "Support Error Feedback" option selected. Modify the property group and try again.
CRRZI0427E
Could not retrieve a USS file for resource {0} of type {1}.
Explanation
- {0}
- Resource name
- {1}
- Resource type
An internal error occurred while the product was
opening a file in an editor.
User response
No action is required.
CRRZI0428E
Could not retrieve a remote file for resource {0} of type {1}.
Explanation
- {0}
- Resource name
- {1}
- Resource type
An internal error occurred while the product was
opening a file in an editor.
User response
No action is required.
CRRZI0429I
The system default values have been updated for system {0}. Do you want to replace the previous defaults with the new ones?
Explanation
A Rational Developer for System z administrator
can configure site-specific defaults for particular properties in
a property group. This message indicates that the default values were
changed for the remote system indicated by {0}.
User response
Click Yes to accept the updates
or No to leave your property groups unchanged.
CRRZI0430I
The system property groups have been updated for system {0}. Do you want to replace the ones that were already loaded?
Explanation
A Rational Developer for System z administrator
can set up predefined property groups for a remote system. These property
groups are downloaded to your workspace when you connect to the remote
system. This message indicates that the system property groups were
changed for the remote system indicated by {0}.
User response
Click Yes to accept the updates
or No to leave your property groups unchanged.
CRRZI0431W
The file {0} already exists. Do you want to overwrite it?
CRRZI0432E
'{0}' is not a valid local project properties file. Make sure the file you are trying to import defines properties for a local project.
Explanation
- {0}
- File name
An error occurred during an import of a local project
properties file that was requested on the
Import Property
Group window. The import file is not in the expected format.
Although
project properties are stored in property groups, the product still
supports the local project properties file for backward compatibility.
CRRZI0433E
'{0}' is not a valid MVS subproject properties file. Make sure the file you are trying to import defines properties for an MVS subproject.
Explanation
- {0}
- File name
An error occurred during an import of an MVS subproject
properties file that was requested on the
Import Property
Group window. The import file is not in the expected format.
Although
project properties are stored in property groups, the product still
supports the MVS subproject project properties file for backward compatibility.
CRRZI0434E
'{0}' is not a valid MVS Files subsystem properties file. Make sure the file you are trying to import defines properties for an MVS Files subsystem.
CRRZI0435E
Unable to import properties from file '{0}'. Make sure the file you are trying to import is a valid .xml or .properties file.
Explanation
- {0}
- File name
An error occurred during an import of a property
group file that was requested on the
Import Property Group window.
The import file is not in the expected format.
CRRZI0436W
Are you sure you want to delete the overrides for this resource?
Explanation
This message confirms a request.
User response
Click Yes to delete the property
group overrides defined for the resource or No to
cancel the request and leave the overrides in place.
CRRZI0437W
Are you sure you want to delete property group {0}?
Explanation
This message confirms a property group Delete request.
User response
Click Yes to delete the property
group or No to cancel the request.
CRRZI0438E
A property group exists with name {0}. Change the name to a unique name.
Explanation
An attempt was made to create a property group with
the same name as an existing property group
User response
Specify a new name for the property group.
CRRZI0439W
The property file you are importing is an old version. Property group {0} will be created to hold the values. Do you want to proceed?
Explanation
The current Rational Developer for System z version uses property groups to define the
build properties for z/OS resources. The file you are importing contains
properties from an earlier release. This message indicates that the
properties are to be imported into a property group.
User response
Click Yes to import the properties
into a property group or No to cancel the import
request.
CRRZI0440E
The resource '{0}' does not have a property group associated with it. Choose an action and then try the operation again:
Explanation
You requested an operation that requires the resource
to have a property group associated with it. No property group is
associated with the resource.
User response
Choose one of the following options:
- To choose an existing property group to associate with the resource,
click Associate an existing property group.
After making this selection and associating the property group, try
the operation again.
- To create a property group and associate it with the resource,
click Associate a new property group. After
making this selection, creating a property group, and associating
it with the resource, try the operation again.
- To cancel the operation, click Do not associate a property
group.
CRRZI0441E
Could not open file {0}.
Explanation
During a property group export operation, the target
export file, indicated by {0}, cannot be opened.
User response
Ensure that the file name specified is valid and
that you have write access to the target location. Try the operation
again. If the error persists, contact your system administrator.
CRRZI0442E
Error writing to file {0}.
Explanation
During a property group export operation, the target
export file, indicated by {0}, cannot be written
to.
User response
Ensure that the file name specified is valid and
that you have write access to the target location. Try the operation
again. If the error persists, contact your system administrator.
CRRZI0443E
{0} is not a registered category.
Explanation
The
.xml file that is being imported
during a property group or workspace import operation contains an
invalid category. The property group or workspace is not imported.
The following sample messages show examples of this error:
CRRZI0443E USE_LOCAL_PREPROCESSORS is not a
registered category.
CRRZI0443E RUN_FOR_CODECOVERAGE is not a
registered category.
This error can occur when you try
to import a property group or workspace from a later
Rational Developer for System z version into an earlier version, for example, importing
a version 8.0 property group into a version 7.6 workspace. Later versions
of
Rational Developer for System z clients are not compatible with earlier versions.
User response
Manually create a workspace or property group with
the characteristics you want.
CRRZI0444W
Some property groups cannot be imported due to name conflicts.
Explanation
During a property group import operation that involves
multiple property groups, some of the groups cannot be imported because
groups with the same names exist. The groups that do not present name
conflicts are imported
User response
No action is required.
CRRZI0445E
Error reading from file {0}.
Explanation
In an attempt to import property groups from the file
indicated by {0}, the import file cannot be read.
User response
Ensure that the file you specified is a valid property
group .xml file. Try the operation again. If
the error persists, contact your system administrator.
CRRZI0446E
A duplicate category instance was detected in property group {0}. The category of the instance is {1}.
Explanation
A property group import file has more than one instance
of a property group category for the property group indicated by {1}. The property group is not imported.
User response
Remove the duplicate category instance and try importing
the property group again.
CRRZI0447E
{0} is not a registered property.
Explanation
The .xml file that is being imported
during a property group import operation contains an invalid property
name. The property group is not imported.
User response
Correct the property name and try the import operation
again.
CRRZI0448W
The system default values have been updated for system {0}. Do you want to replace the previous defaults with the new ones?
Explanation
A Rational Developer for System z administrator can configure site-specific defaults for
particular properties in a property group. This message indicates
that the default values were changed for the remote system indicated
by {0}.
User response
Click Yes to accept the updates
or No to leave your property groups unchanged.
CRRZI0449W
The system property groups have been updated for system {0}. Do you want to replace the ones you previously loaded?
Explanation
A Rational Developer for System z administrator can set up predefined property groups for
a remote system. These property groups are downloaded to your workspace
when you connect to the remote system. This message indicates that
the system property groups were changed for the remote system indicated
by {0}.
User response
Click Yes to accept the updates
or No to leave your property groups unchanged.
CRRZI0450E
The check dependencies operation could not be performed. See details for more information.
Explanation
A Check Dependencies request
was made, but could not be completed.
User response
For more information about the errors that occurred
during this operation, click Details.
CRRZI0451E
Copying a partitioned data set or folder is not supported.
Explanation
This message displays in response to an attempt to
copy a folder or a partitioned data set into an MVS subproject by
dragging it.
User response
To copy the contents from a source folder or partitioned
data set into an MVS subproject:
- Create a partitioned data set in the MVS subproject.
- Copy the members from the source folder or partitioned data set.
- Paste the members into the new partitioned data set.
CRRZI0452E
Resource '{0}' is locked and cannot be deleted. Another person or program might be using the resource. Try the operation again when the resource is available.
Explanation
A remote resource cannot be deleted if it is locked
by another user or program.
User response
To determine the lock owner of a remote resource,
open the properties view and expand the Info category
to see the Lock owner property.
CRRZI0456E
Local project names are case insensitive. There is an existing project that conflicts with '{0}'. Choose another name for the project.
Explanation
A name specified for a new local project exists in
the workspace. Because names are not case-sensitive, the names "MyNewProject" and "Mynewproject", for example, conflict.
User response
Choose a unique name for the project.
CRRZI0457E
An internal error occurred during creation of local project '{0}'. Contact your IBM technical support representative.
Explanation
An internal error occurred during creation of local
project '{0}'.
User response
Contact IBM Software Support.
CRRZI0458I
The JCL was submitted to remote system '{1}' and the Job ID is '{0}'. Click Locate Job to locate the job in the Remote Systems view.
Explanation
During execution of the DCLGEN utility wizard, Rational Developer for System z generates and submits JCL to generate copybooks, include
files, macros, and C/C++ header files from database table information by
using the DB2 utility DCLGEN. This message indicates that the job
was submitted.
User response
To check the job output, do these steps:
- In the Remote Systems view, locate the remote system on which
the DB2 table you are working with is located.
- Expand the remote system connection and then expand JES > My Jobs.
- Look for the job name indicated in the message and expand it to
see the job output.
CRRZI0459E
The job has not been submitted because the Job Monitor server is not connected. Contact your System Administrator to start the Job Monitor server. After the server is started, you may resubmit the job.
Explanation
The Job Monitor server must be started before jobs
can be submitted.
User response
Contact your system administrator to start the Job Monitor
server
CRRZI0460E
A problem occurred while creating or saving the properties. See the log for further information.
Explanation
During an export properties operation, the export
file cannot be created or saved.
User response
To open the log file, open workspace/.metadata/.log (Windows) or workspace\.metadata\.log (Linux) on your workstation file system.
CRRZI0461E
No connection is defined for '{0}'. Define a connection and import the project again.
Explanation
To import a remote z/OS project, you must be connected
to the remote system that contains the project resources.
User response
- Define a connection to the remote system indicated by {0}.
- Connect to the remote system.
- Try to import the project again.
CRRZI0462E
The project to be imported is named '{0}'. There is a project in the workspace with this name. Specify a unique name for the new project and try again.
Explanation
During a project import operation, an existing project
with the same name was found in the workspace. Projects must have
unique names.
User response
Specify a new name for the project.
CRRZI0463E
A file with the name '{0}' already exists in '{1}'. Make sure all the files have a unique name (excluding extension) and try again.
Explanation
Attention: The work offline and work
online operations for a remote resource are deprecated.
- {0}
- File name
- {1}
- Location of file
A work online operation found a
file with the same name, but without the file extension, in the current
folder.
User response
Make sure that the file names in the folder are
unique with or without the extensions. Specify a new unique name
for the files in the folder.
CRRZI0464E
Invalid MVS name. A member name cannot be more than 8 characters. Return to the offline project, rename the member, and try the operation again.
Explanation
Attention: The work offline and work online
operations for a remote resource are deprecated.
During
a work online upload operation, an invalid MVS name was found. Member
names cannot be more than eight characters.
User response
Correct any member names that do not confirm to data
set member naming rules and try the operation again.
CRRZI0465E
Invalid MVS name. The member name must not have a period. Return to the offline project, rename the member, and try the operation again.
Explanation
Attention: The work offline and work online
operations for a remote resource are deprecated.
During
a work online upload operation, an invalid MVS name was found. The
member name must not have a period.
User response
Correct any member names that do not confirm to data
set member naming rules and try the operation again.
CRRZI0466E
Invalid MVS name. Each segment of a data set name can have no more than 8 characters. Return to the offline project, rename the member, and try the operation again.
Explanation
When a project is offline, you can rename data sets
or add new data sets to it. This message indicates that a new or renamed
data set does not conform to data set naming rules.
User response
Be sure that any new or renamed data sets use no
more than 8 characters in each segment of the data set name. Correct
any data set names that do not conform to data set naming rules and
try the operation again.
CRRZI0467W
{0} has the following encoding mismatch:
Explanation
Attention: The work offline and work
online operations for a remote resource are deprecated.
- {0}
- The item that contains an encoding mismatch
The work online upload operation
checks for any encoding mismatch between a local resource and the
corresponding remote resource. If encoding for SO/SI is specified
for a local resource, the operation compares it to the host encoding
of the remote resource. If the encodings do not match, the user is
asked to override the host encoding with the SO/SI encoding or cancel
the operation.
User response
The encoding mismatch must be resolved. To change
the host code page of the remote resource to the SO/SI encoding of
the local resource, click Yes. To leave the
host code page of the remote resource unchanged and cancel the operation,
click No.
CRRZI0468E
Another properties provider is registered for the resource.
Explanation
A team provider plug-in can add properties to resources
owned by Rational Developer for System z by registering its own properties provider. The message
indicates that the registration failed because another properties
provider is already registered.
User response
Contact IBM Software Support.
CRRZI0469E
The object does not have properties.
Explanation
A team provider plug-in can add properties to resources
owned by Rational Developer for System z by registering its own properties provider. The message
indicates that the registration failed because the specified resource
does not support properties.
User response
Contact IBM Software Support.
CRRZI0470I
z/OS UNIX Files and Shells are hidden by the server setting.
Explanation
A setting on the remote system is causing z/OS UNIX
Files and Shells to be hidden on the client user interface.
User response
If you believe this setting is incorrect, contact
your systems administrator.
CRRZI0471E
While synchronizing changes resulting from a request to rename a shared folder from {1} to {2}, the rename operation for the sandbox resource {0} failed. The sandbox resource will be unloaded from the z/OS project. Resolve the error described below and reload the shared resource to the project.
Explanation
- {0}
- Resource name
- {1}
- Folder name
- {2}
- Folder name
CRRZI0472E
While synchronizing changes resulting from a request to delete the shared resource {1}, the delete operation for sandbox resource {0} failed. The sandbox resource will be disconnected. Resolve the error described below or the sandbox might not be available for use.
Explanation
- {0}
- Resource name
- {1}
- Resource name
CRRZI0473E
While synchronizing changes resulting from a request to rename a shared resource from {1} to {2}, the rename operation for the sandbox resource {0} failed. The sandbox resource will be unloaded from the z/OS project. Resolve the error described below and reload the shared resource to the project.
Explanation
- {0}
- Resource name
- {1}
- Resource name
- {2}
- Resource name
CRRZI0474E
While synchronizing changes resulting from a request to update Failed to update the shared resource {1}, the update operation for the sandbox resource {0} failed. The sandbox resource will be unloaded from the z/OS project. Resolve the error described below and reload the shared resource to the project.
Explanation
- {0}
- Resource name
- {1}
- Resource name
CRRZI0475E
The data set {0} does not exist.
Explanation
This message displays in response to a Check
Data Sets request on a Procedures and Steps page
of the property group editor. It indicates that the data set name
specified does not exist.
User response
Specify another data set name and try again.
CRRZI0476E
The data set {0} is already specified in the text field.
Explanation
This message displays in response to a Check Data Sets request on a Procedures and
Steps page of the property group editor. It indicates that
the data set name specified was already added to the field.
User response
Specify another data set name and try again.
CRRZI0477E
Invalid source {0} for this text field. Drag and drop a valid data set onto this text field.
Explanation
This message displays in response to a drag operation
on a Procedures and Steps page of the property
group editor. It indicates that an object other than a data set was
dragged to the field.
User response
Drag a data set name into the field.
CRRZI0478E
This text field specifies one data set name. Drag and drop one data set onto this text field.
Explanation
This message displays in response to a drag operation
on a Procedures and Steps page of the property
group editor. It indicates that the field to which a data set name
was dragged can contain only one data set name.
User response
To replace the data set name already in the field,
clear the filed and then drag another name to the field.
CRRZI0479W
The length of the data set name might exceed the maximum of 44 characters, depending on the length of the high-level qualifier.
Explanation
Data set names in the fields on the Procedures
and Steps page of the property group editor are limited
to 44 characters. This warning indicates that the current data set
name is nearing this limit and might exceed it if the high-level qualifier
is too long.
User response
Check the length of the high-level qualifier to ensure
that it does not result in a data set name that exceeds the maximum
length.
CRRZI0480E
The system {0} is not connected. Connect to the system and try again.
Explanation
- {0}
- The name of a remote system.
Data set validation for a property
group requires a connection to a remote system.
User response
Connect to the remote system and try the operation
again. To connect to the remote system:
- On the Information page of the property group
editor, identify the system that the property group belongs to.
- To connect to the system, locate the system in the Remote
Systems view, right click, and select Connect.
CRRZI0481E
There is no name for the property group.
Explanation
During a property group create operation, the property
group name was found to be missing.
User response
Specify a name for the property group on the Property
Group Information page and try saving the property group
again.
CRRZI0483E
While synchronizing changes to the sandbox resource {1}, a delete operation for the shared resource {0} failed. The resource is not synchronized. Resolve the error described below and share the sandbox or reload the shared resource.
Explanation
- {0}
- Resource name
- {1}
- Resource name
CRRZI0484E
While synchronizing changes resulting from a request to rename the sandbox from {1} to {2}, the rename operation for the shared resource {0} failed. The resource is not synchronized. Resolve the error described below and share the sandbox or reload the shared resource.
Explanation
- {0}
- Resource name
- {1}
- Sandbox name
- {2}
- Sandbox name
CRRZI0485E
The editor contains characters that cannot be transferred correctly between the local and remote systems. Saving the file on the remote system will cause these characters to become corrupted. Do you want to continue?
Explanation
The Rational Developer for System z editors are able to preserve the integrity of characters
as they are transferred from the remote system to the workstation
and back again. For some code pages, however, it is not possible to
preserve round-trip integrity of certain characters. This message
warns that the file under edit contains characters whose round-trip
integrity cannot be preserved.
User response
To save the file with corrupted characters, click Yes. To close the file without saving your changes, click No.
CRRZI0487E
File '{0}' contains characters that cannot be transferred correctly between the local and remote systems. These characters will be highlighted. The file will be opened in read-only mode.
Explanation
The Rational Developer for System z editors
are able to preserve the integrity of characters as they are transferred
from the remote system to the workstation and back again. For some
code pages, however, it is not possible to preserve round-trip integrity
of certain characters. This message warns that the file under edit
contains characters whose round-trip integrity cannot be preserved.
One cause of this message can be the definition of an inappropriate
alternative logical NOT symbol. Because the file is being edited from
the remote system, it is opened in read-only mode.
User response
To edit the file, copy it to a local project in your
workspace and change the corrupted characters before you copy it to
the remote system. For instructions for setting an alternative logical
NOT symbol, see the related topics.
CRRZI0489E
An attempt to move the logical resource '{0}' to '{1}' has failed.
Explanation
An error occurred while a remote resource was being
shared with a team provider and creating a local copy of the resource.
- {0}
- Resource name
- {1}
- Resource name
User response
For details about this error, see the .log file
in the .metadata folder of the current workspace.
CRRZI0490E
The logical resource '{0}' is not a subproject.
Explanation
When you load a team resource into the remote file
system, the remote resource must be added to a subproject. A subproject
was not specified by the team provider application.
- {0}
- Resource name
User response
Contact your systems administrator.
CRRZI0491E
The remote sandbox file path name '{0}' is not found on the system '{1}'.
Explanation
When you load a team resource into the remote file
system, a local copy of the remote resource is also downloaded to
the client. The remote resource was not found.
- {0}
- Path name
- {1}
- System name
User response
Contact your systems administrator.
CRRZI0492E
There are no systems found for the logical subproject '{0}'.
Explanation
When you load a team resource into the remote file
system, the remote system is inferred from the target subproject.
No remote system was associated with the subproject.
- {0}
- Subproject name
User response
Contact your systems administrator.
CRRZI0493E
An attempt to load resource '{0}' to the subproject '{1}' has failed.
Explanation
When you load a team resource into the remote file
system, the remote resource must be added to a subproject. An error occurred when
the remote resource was added to the subproject.
- {0}
- Resource name
- {1}
- Subproject name
User response
For details about this error, see the .log file in the .metadata folder
of the current workspace.
CRRZI0494E
The local sandbox path '{0}' specified for the team resource '{1}' is invalid.
Explanation
When you share a remote resource with a team provider,
a local copy of the remote resource is downloaded to the client. The
team provider application specified an invalid local destination.
- {0}
- Path name
- {1}
- Resource name
User response
Contact your systems administrator.
CRRZI0495E
The resource '{0}' is already registered with a team provider. Registering a resource with multiple team providers in not allowed.
CRRZI0496E
The resource '{0}' is already shared with a team provider. Sharing a resource with multiple team providers is not allowed.
CRRZI0497E
The resource '{0}' is not shared with a team provider. The disconnect operation can be performed only on a shared resource.
CRRZI0498E
The sandbox prefix was specified for '{0}', but the remote sandbox file name is required. Specify the remote sandbox file name and try the operation again.
Explanation
- {0}
- Sandbox prefix
During a resource check-in operation, a sandbox
prefix was provided when the remote sandbox file name was expected.
User response
Try the operation again. Specify the remote sandbox
file name.
CRRZI0499I
Data set validation is complete. All validated data sets exist.
Explanation
This message displays in response to a Check
Data Sets request on a Procedures and Steps page
of the property group editor. It indicates that the data set names
specified are valid.
User response
No response is required.
CRRZI0500W
Data set validation is complete. One or more data set names contain the variable <HLQ> and these data sets cannot be validated.
Explanation
This message displays in response to a Check
Data Sets request on a Procedures and Steps page
of the property group editor. It indicates that the data set names
specified cannot be validated because they contain the <HLQ> variable.
The data set names might or might not be valid.
User response
No response is required.
CRRZI0501E
Data set {0} already exists.
Explanation
- {0}
- The name of a data set.
The target of the copy or rename operation exists,
but the option to replace an existing data set was not specified.
User response
Try the operation again and either choose a different
target name or specify the replace option.
CRRZI0502E
Data set {0} has conflicting attributes.
Explanation
- {0}
- The name of a data set.
A target data set was found, but its characteristics
do not match the characteristics of the source data set.
User response
Specify a different source or target data set so
that the characteristics match or specify a target that does not exist
so that it can be allocated with the same characteristics as the source
data set.
CRRZI0503E
Member {0} already exists.
Explanation
- {0}
- Member name
The target of the copy or rename operation exists
but the option to replace an existing data set was not specified.
User response
Try the operation again and either choose a different
target name or specify the replace option.
CRRZI0504I
The closed project {0} contained one or more shared resources. They have been unloaded. You will need to reload them when you reopen the project later.
CRRZI0505E
Overrides are being edited for property group '{0}'. Close the edit session for the overrides before editing the property group.
Explanation
During a property group edit operation, for the property
group indicated by {0}, the property group was
found to be open for a property group override request. You cannot
edit a property group while it is open for overrides.
User response
Close the Property Group Editor and then try the edit operation again.
CRRZI0506E
The property group '{0}' is being edited. Close the edit session for the property group before attempting to override it.
Explanation
During a property group override operation for the
property group indicated by {0}, the property group
was found to be open for a property group edit request. You cannot
override a property group while it is open for edit.
User response
Close the Property Group Editor and
then try the override operation again.
CRRZI0507E
Possible reason for failure: An invalid CICS Debug profile server port ({0}) is being used for the CICS region {1}. Contact the administrator for the valid port and update the port in the CICS Debug Configuration preference page.
Explanation
An attempt to create a CICS debug configuration failed.
A possible reason for the failure is an invalid CICS Debug profile
server port number specified on the CICS Debug Configuration preference
page.
User response
Contact your system administrator to obtain the correct
CICS Debug profile server port number. Specify the port number on
the CICS Debug Configuration preference page
and then try to create the debug configuration again.
CRRZI0508I
Specify the CICS Debug profile server port for the CICS region {0}.
Explanation
An attempt was made to create a debug configuration,
but there is no CICS Debug profile server port associated with the
CICS region.
User response
Contact your system administrator to obtain the correct
CICS Debug profile server port number. Specify the port number on
the CICS Debug Configuration preference page
and then try to create the debug configuration again.
CRRZI0509E
The remote sandbox resource {0} has been updated by another person or program. Resolve the conflict and then try the operation again.
CRRZI0510W
The data set '{0}' contains {1} members. Working with a large number of members in a subproject might take a long time. To improve performance, add only required members to the subproject. Do you want to proceed?
Explanation
The number of members in the partitioned data set
exceeds the warning threshold set in the MVS Files preference
page. This message gives you an opportunity to cancel the request
to add the partitioned data set to the subproject.
User response
- To continue adding the partitioned data set to the subproject,
click Yes.
- To cancel the request, click No.
- To disable the warning, open the MVS Files preference
page and clear the Show warning message on adding to subproject check
box.
- To change the warning threshold, open the MVS Files preference
page and specify a different number in the Maximum number
of members added to subproject without warning field.
CRRZI0511E
CICS region ({0}) does not exist. Make sure the appropriate CICS connection is connected.
Explanation
The region specified on the CICS page
of the Debug Configurations > Remote CICS Application wizard
does not exist.
User response
On the CICS page of the Debug
Configurations > Remote CICS Application wizard, click
the Define CICS Connection link to open the CICS
Explorer > Connections preference page. Use this page to
connect to a CICS region and then try again to define the CICS debug
configuration.
CRRZI0512W
The size of file '{0}' is {1} KB, which exceeds the threshold defined in the z/OS Solutions preferences. Opening large files can cause out-of-memory errors leading to a forced shutdown of the workbench. Do you want to continue?
Explanation
The Rational Developer for System z preferences provide a warning threshold for opening large
files. This warning helps to prevent out-of-memory errors.
User response
- To continue opening the file click Yes.
- To cancel the file open operation, click No.
- To disable the warning, click . Select z/OS Solutions in the Preferences window and clear the Show warning message on opening
files check box.
- To change the file size threshold for the warning, specify a new
value in the Maximum file size to open without warning
(in KB) field.
CRRZI0513W
Some categories will not be imported because this version of Rational Developer for System z does not support them.
Explanation
The property group that is being imported contains
property group categories that are not supported by the current version.
The supported categories are imported and the unsupported categories
are ignored.
User response
No response is required.
CRRZI0514E
The operation did not complete successfully. Verify that the JCL procedure on the remote system has the error feedback compiler options configured correctly to support this operation.
Explanation
The operation requires the error feedback compilation
option to be specified.
User response
Enable the error feedback option and try the operation
again. To enable the error feedback option:
- Edit the property group associated with the resource.
- Select the category appropriate for the resource type: Assembler,
COBOL, or PL/I.
- In the Procedure and Step Table, click
a step name to display the step options.
- Select the Support Error Feedback check
box.
CRRZI0515W
The file '{0}' contains characters that cannot be transferred correctly between the local and remote systems. This file will be opened in read-only mode. Do you want to continue?
Explanation
The Rational Developer for System z editors are able to preserve the integrity of characters
as they are transferred from the remote system to the workstation
and back again. For some code pages, however, it is not possible to
preserve round-trip integrity of certain characters. This message
warns that the file under edit contains characters whose round-trip
integrity cannot be preserved.
User response
To open the file in the comparison editor, click Yes. To cancel the file comparison request, click No.
CRRZI0516W
Both files contain characters that cannot be transferred correctly between the local and remote systems. The files will be opened in read-only mode. Do you want to continue?
Explanation
The Rational Developer for System z editors are able to preserve the integrity of characters
as they are transferred from the remote system to the workstation
and back again. For some code pages, however, it is not possible to
preserve round-trip integrity of certain characters. This message
warns that the files under edit contain characters whose round-trip
integrity cannot be preserved.
User response
To open the files in the comparison editor, click Yes. To cancel the file comparison request, click No.
CRRZI0518W
A decoding error occurred while fetching the keymapping file. The system will be processed as though there were no keymapping file.
Explanation
While attempting to export configuration files, Rational Developer for System z encountered problems with the keymapping.xml file and
cannot update the file. A new keymapping.xml file is generated and
uploaded to the remote system.
User response
No action is required. The new key mapping file contains
settings for only the configuration files included in the current
export request.
CRRZI0519I
There are no connected remote systems with the push-to-client function enabled. Connect to a remote system with the push-to-client function enabled and try again.
Explanation
You requested to export configuration files, but none
of the remote systems to which you are connected are enabled for push-to-client.
User response
Connect to a remote system that has the push-to-client
function enabled and try again. Contact your system administrator
if you do not know which remote systems are enabled for push-to-client.
CRRZI0521E
The error feedback file cannot be parsed because its format or content is invalid or incomplete. Check the build properties and view the job output for unrecoverable errors.
Explanation
The file specified in the Error Feedback
XML File Name field of the Local Preprocessor page of the current property group contains formatting or content
errors.
User response
- Open the property group in the Property Group Editor and verify
that the Error Feedback XML File Name field refers to
the correct file.
- To view the job output, expand the JES subsystem in the Remote Systems view and look for the job name.
CRRZI0522W
The Rational Developer for System z server has been configured to automatically download product updates to the client when you connect to the remote system. Current Product Version shows the product version currently installed on your workstation. A new version will be installed when you click OK.
Explanation
The remote system to which you are connecting is configured
to automatically install product updates when you connect to it. Product
updates are available for installation.
User response
Click OK to install the product
updates. Your workbench is shut down and IBM Installation Manager
is started to install the product updates. Restart Rational Developer
for System z when the product installation is complete.
CRRZI0523E
The member {0} is the alias of {1}. Support for copying aliases has been disabled in the preference settings. Copying an alias without copying its primary is not supported.
Explanation
You attempted to copy a partitioned data set member
that is an alias. The copy operation cannot be completed because alias
processing is disabled.
User response
To enable alias processing, click
Window
> Preferences, then expand the
Remote Systems and
z/OS sections and click
MVS
Files. On the MVS Files preference page, select the
Process member aliases on module copy option. For more
information about enabling alias processing, see
MVS Files.
CRRZI0524E
The member {0} is the alias of {1}, which does not exist. Copying an alias without copying its primary is not supported.
Explanation
You attempted to copy a partitioned data set member
that is an alias. The copy operation cannot be completed because the
primary member does not exist.
User response
For more information about copying data set aliases, see
Copying load modules. For more information about
enabling alias processing, see
MVS Files.
CRRZI0525E
The member {0} is an alias or has one or more aliases. The copy target cannot be the same as the copy source.
Explanation
You attempted to copy a partitioned data set member
that is an alias or has an alias defined. The copy operation cannot
be completed because the copy source and the copy target are the same.
User response
Try the copy operation again and specify a different
target. For more information about copying data set aliases, see
Copying load modules.
CRRZI0526E
IEBCOPY has failed. See {0} for more details.
Explanation
- {0}
- The log file name.
The copy command failed because the request to allocate
a data set before the IEBCOPY command failed.
User response
CRRZI0527W
Both files use an encoding that permits bidirectional characters. The files will be opened in read-only mode. Do you want to continue?
Explanation
The comparison editor does not support edit of bidirectional
file content.
User response
To open the files in the comparison editor, click Yes. To
cancel the file comparison request, click No.
CRRZI0528W
The file '{0}' uses an encoding that permits DBCS characters. The file will be opened in read-only mode. Do you want to continue?
Explanation
The comparison editor does not support edit of double-byte
character set (DBCS) file content.
User response
To open the file in the comparison editor, click Yes. To
cancel the file comparison request, click No.
CRRZI0529W
Both files use an encoding that permits DBCS characters. The files will be opened in read-only mode. Do you want to continue?
Explanation
The comparison editor does not support edit of double-byte
character set (DBCS) file content.
User response
To open the files in the comparison editor, click Yes. To
cancel the file comparison request, click No.
CRRZI0530W
The file '{0}' uses an encoding that permits bidirectional characters. The file will be opened in read-only mode. Do you want to continue?
Explanation
The comparison editor does not support edit of bidirectional
file content.
User response
To open the file in the comparison editor, click Yes. To
cancel the file comparison request, click No.
CRRZI0532I
You are requesting to export to primary system {1}. Primary system {0} was used last to export the configuration files. Verify that {1} is the correct primary system.
Explanation
You are currently connected to primary system {1} and initiated an export configuration files action.
The last time you requested this action, you were connected to primary
system {0}. This message is a reminder to verify
that you intend to export configuration files to a different primary
system than the one to which you exported previously.
User response
If you intend to export to a different primary system,
no action is required. You can continue with the export action.
If you did not intend to export to a different system:
- Cancel the current export action.
- Disconnect from primary system {1}.
- Connect to primary system {0}.
- Try the export action again.
CRRZI0533I
Two or more primary systems are connected. Only one connection to a primary system is allowed. Disconnect from all but one primary system.
Explanation
You are connected to two or more remote systems that
are defined as the primary system in a push-to-client environment.
The push-to-client feature allows only one connection to a primary
remote system.
User response
Disconnect from all but one primary remote system.
Contact your system administrator if you do not know which remote
systems are primary.
CRRZI0534E
Insufficient permission to the directory {0} when exporting {1}.
Explanation
An attempt to export a configuration file to a remote
system failed. Your user ID does not have the correct file permissions
to write to the parent directory. To export system or global configuration
settings to the remote system, you must have write access to the push-to-client
configuration directories on the remote system. File permissions for
the push-to-client directory on the remote system are set by using
the file.permission directive in the pushtoclient.properties file.
User response
CRRZI0535I
There are no changes between the workstation copy and the remote copy.
Explanation
This message displays in response to a request. It indicates that the local and remote resources
are synchronized.
User response
No response is required.
CRRZI0536E
Errors occurred moving changed files
Explanation
This message displays in response to a request. It indicates that an error occurred while
synchronizing the local and remote files.
User response
Contact your system administrator.
CRRZI0537E
No remote systems are defined. Cancel this action, define a remote system, and try the operation again.
Explanation
This message displays in response to a request. It indicates that no remote system is defined.
User response
Define a connection to a remote system, connect to
the system, and try the operation again.
CRRZI0538E
Could not mark {0} as merged
Explanation
A Mark as Merged request in
the Synchronize perspective failed.
User response
Contact your system administrator.
CRRZI0539E
You must be connected to the remote system and have at least one filter defined to use the <HLQ> variable.
Explanation
Attention: The push-to-host (remote synchronization)
function is deprecated.
For some operations,
such as Enable Remote Synchronization, you can type the <HLQ> variable
in the high-level qualifier field of the user interface. Use of this
variable requires a connection to a remote system for the variable
to be correctly substituted.
User response
Connect to a remote system and try the operation
again.
CRRZI0540E
You are going to overwrite changes that have been made on the remote system. Commit these changes?
Explanation
Synchronizing the local project with the remote system
results in overwriting changes that were made on the remote system.
User response
Click Yes to continue and
overwrite the remote changes or No to cancel
the request.
CRRZI0541E
Error copying {0} to the local workspace
Explanation
An inbound change cannot be copied to the local project
in the synchronize perspective.
User response
Contact your system administrator.
CRRZI0542E
Error copying {0} to the remote system
Explanation
An outbound change cannot be copied to the remote
system in the synchronize perspective.
User response
Contact your system administrator.
CRRZI0543W
The chosen remote system location differs from the project's target remote system. Would you like to change the project's target remote system to match the chosen remote system location?
Explanation
The remote system specified in the Pushable
Manifest Editor differs from the remote system associated
with the local project.
User response
To change the remote system associated with the local
project, click Yes. To leave the remote system
associated with the project unchanged, click No.
CRRZI0544W
The extension is already in the mapping.
Explanation
A local file extension specified in the Pushable Manifest Editor is already added to the mapping.
User response
Specify a different file extension.
CRRZI0545W
You are going to overwrite changes that have been made in the local workspace. Update the workspace?
Explanation
Synchronizing the local project with the remote system
results in overwriting changes that were made on the local system.
User response
Click Yes to continue and
overwrite the local changes or No to cancel
the request.
CRRZI0546E
Failed to connect to {0}.
Explanation
Attention: The remote synchronization
function is deprecated.
During a remote synchronization
operation, the product could not connect to the remote system.
- {0}
- The name of a remote system.
User response
Ensure that the remote system connection is defined
in the Remote Systems view and that the connection
properties are defined correctly. Contact your systems administrator
for the correct connection properties.
CRRZI0547E
Could not find {0} on {1}.
Explanation
Attention: The push-to-host (remote synchronization)
function is deprecated.
A request was made to
copy a local resource to the remote system by using the push-to-host or operation. The target data set
was not found on the remote system.
- {0}
- The name of a remote data set.
- {1}
- The name of a remote system.
User response
You must allocate the target remote data set before
you can copy a local resource to it. Allocate the data set on the
remote system. Ensure that the remote data set name and the remote
system are specified correctly in the remote mapping. Try the operation
again.
CRRZI0548E
Failure to retrieve modification stamp.
CRRZI0549E
Contents cannot be retrieved from {0}.
CRRZI0550E
Failure to retrieve member contents {0}.
CRRZI0551E
Contents cannot be set on {0}.
CRRZI0552E
Failure to write member contents.
CRRZI0553E
Failed to connect to {0}.
CRRZI0554E
Could not find {0} on {1}.
CRRZI0555E
Contents cannot be retrieved from {0}.
CRRZI0556E
Contents cannot be set on {0}.
CRRZI0557E
Could not access properties.
CRRZI0558E
Syntax check not successful.
CRRZI0559W
Some project resources are not synchronized. Would you like to stop the syntax check and open the Team Synchronizing perspective?
CRRZI0560E
Invalid Format. Expected a path, but found {0}.
Explanation
A file referenced in the .RemoteMapping pushable manifest editor file is in an unsupported format. A non-path
item was found when a path was expected.
User response
Open the .RemoteMapping file
in a text editor and correct the line in error.
CRRZI0562E
A remote system must be specified.
Explanation
Attention: The remote synchronization
function is deprecated.
An error occurred while
a mapping for remote synchronization was being created. The remote
system name is missing.
User response
Open the Pushable Manifest Editor and specify a valid
remote system location.
CRRZI0563E
The local resource does not exist.
Explanation
Attention: The remote synchronization
function is deprecated.
An error occurred while
a mapping for remote synchronization was being created. The local
resource that is specified in a mapping does not exist.
User response
Either create the local resource or clear the mapping
from the editor.
CRRZI0564E
Unrecognized remote resource type {0}.
Explanation
Attention: The remote synchronization
function is deprecated.
An error occurred while
a mapping for remote synchronization was being created. The remote
resource type is incorrect for a mapping. Valid resource types are
MVS and USS.
User response
Open the Pushable Manifest Editor and set a valid
remote resource type, or clear the mapping for that item.
CRRZI0565E
Unspecified remote resource type.
Explanation
Attention: The remote synchronization
function is deprecated.
An error occurred while
a mapping for remote synchronization was being created. The remote
resource type is missing.
User response
Open the Pushable Manifest Editor and specify a remote
resource type, or clear the remote location.
CRRZI0566E
The same remote resource is specified multiple times.
Explanation
Attention: The remote synchronization
function is deprecated.
An error occurred while
a mapping for remote synchronization was being created. More than
one local resource is mapped to the same remote resource.
User response
Open the Pushable Manifest Editor and specify a different
remote resource for each local resource, or remove duplicate entries
from the manifest.
CRRZI0567E
Unrecognized remote resource location.
Explanation
Attention: The remote synchronization
function is deprecated.
An error occurred while
a mapping for remote synchronization was being created. The remote
resource that is specified in a mapping cannot be found.
User response
Open the Pushable Manifest Editor and set a valid
remote resource location, or allocate the remote data set that is
specified in the mapping.
CRRZI0568E
Could not determine if the project is pushable: {0}
CRRZI0569W
This action removes all COBOL feature customization and returns to the product defaults. Are you sure?
Explanation
This message prompts you to confirm a Restore
Defaults action on the Features preference
page for COBOL.
User response
Click OK to remove all COBOL
feature customization or Cancel to cancel the
restore defaults request.
CRRZI0570W
This action deletes the selected feature(s). Are you sure?
Explanation
This message prompts you to confirm a delete action
on the Features preference page for COBOL.
User response
Click Yes to delete the feature
or No to cancel the delete request.
CRRZI0571W
The file already exists. Do you want to replace it?
Explanation
A request was made to export the customizable features
for COBOL programs to an XML, but the file exists in the same location
on the file system.
User response
To replace the file, click Yes.
To cancel the export operation, click No.
CRRZI0572W
Overwrite '{0}' ?
Explanation
- {0}
- The name of the feature that is being imported.
During an import operation, a feature was found
to exist.
User response
To replace the feature, click Yes.
To cancel the import operation, click No.
CRRZI0573E
Not a valid COBOL comment.
Explanation
While a COBOL code template was being edited, an invalid
COBOL comment was provided.
User response
Type a valid COBOL comment and save the template.
CRRZI0574E
Missing required variable '{0}'.
Explanation
- {0}
- The name of the missing variable.
While a code template was being edited, a required
variable was omitted.
User response
Type a variable or select one by clicking Insert
Variable.
CRRZI0575W
Unrecognized or illegal variable '{0}'.
Explanation
- {0}
- The name of a variable that is not recognized or is invalid in
the template.
While a code template was being edited, one of the
following situations occurred:
- A variable was used that is not predefined.
- The predefined variable that was used is not valid for the template.
User response
Use a different variable and save the changes to
the template.
CRRZI0576I
The selected configuration file updates have been downloaded.
Explanation
The remote system to which you are connected uses
the push-to-client feature to distribute workspace configuration updates
to Rational Developer for System z clients. Your workspace was updated with new configurations.
User response
No action is required. If you would like to suppress
this message the next time you connect to the remote system, click Do not show this message again on the message window.
CRRZI0577I
You are requesting to import configuration files from the group {1}. The group {0} was used last to import the configuration files. Verify that {1} is the correct group.
Explanation
The push-to-client feature allows a workspace to be
associated with only one access group. You previously imported configuration
files from group {0} and are now requesting to
import configuration files from group {1}.
User response
- If you intended to import the configuration files a different
group, click OK.
- If you intended to import files from group {1} to a different workspace, click Cancel, switch
to a different workspace, and then try the import operation again.
CRRZI0579W
Your authorization to access group {0} has changed since you last connected to this remote system. The configuration updates will not be imported into this workspace.
Explanation
The remote system to which you connected uses push-to-client
access groups to control access to configuration updates. Since you last connected to this system, you
were removed from access group {0}. While you can
still connect to this remote system, you can no longer receive push-to-client
updates from it.
User response
If you do not need any configuration updates from
this remote system, then no action is required. If, however, you need
to receive updates from this remote system, contact your system administrator.
CRRZI0580W
Configuration groups have been disabled since you last connected to this remote system. The configuration updates for group {0} will not be imported into this workspace.
Explanation
The remote system to which you connected previously used
push-to-client access groups to distribute configuration updates.
Since you last connected to this system, access groups were disabled.
While you can still connect to this remote system, you can no longer
receive push-to-client updates from group {0}.
User response
No action is required.
CRRZI0582E
The backup of an existing workspace has failed. Make sure that there is sufficient free disk space and that none of the files in the workspace has a path that is too long. Do you want to continue without backing up the workspace?
Explanation
When you open a workspace that was created in an earlier
version of the product, it is migrated to the current version. Before
the migration, the workspace is backed up. This message indicates
that the backup operation failed.
User response
To continue migrating the workspace without backing
it up, click Yes. To stop the migration and
correct the problems, click No.
CRRZI0583E
A NullPointerException was encountered during migration of the workspace.
CRRZI0584E
Workstation folder {0} under the offline project cannot be migrated.
CRRZI0585E
Unable to find the VisualAge CICS Translator or the Transaction Server Translator
CRRZI0586E
Unable to find the CICS TX Series Translator. If you are using Windows, install the CICS TX Series Translator. Support for the CICS TX Series Translator is not available on Linux platforms.
CRRZI0588E
Local build and local syntax check require a database connection. The database for connection {0} is not connected. The operation will continue. The SQL coprocessor will not be invoked.
Explanation
Attention: Local syntax check is deprecated.
- {0}
- The name of a database connection.
A local build or syntax check operation
was requested, but the database connection in the
Data Source
Explorer is not connected
User response
Switch to the Data Perspective.
In the Data Source Explorer, connect to the database
that matches the database that is specified in the Local
Compiler Options page of the property group that is associated
with the resource for which the operation was requested.
CRRZI0589E
A valid database connection is required for this operation. Make sure that you have the correct connection properties, a valid user ID, and a valid password.
Explanation
An operation that requires a database connection opened
the database connection window. A connection cannot be made with the
credentials that were used.
User response
Switch to the Data Perspective.
In the Data Source Explorer verify the database
name, IP address, port number, user ID, and password. Try to connect
to the database again.
CRRZI0590E
Problems occurred while determining build dependencies.
Explanation
One or more errors occurred while the product was
attempting to determine the build dependencies of the selected resource.
The detailed message for each error was collected and associated
with the original error message.
User response
Examine the detailed error message for each error
and take the appropriate remedial action.
CRRZI0591W
Resource type {0} is not supported.
Explanation
- {0}
- The name of the resource that was selected for an action.
The current action was expecting
the input resource to be a member of an MVS subproject.
User response
Select an MVS subproject or one of its members and
try the action again.
CRRZI0592E
'{0}' was found while processing file '{1}' at line '{2}'. The dependency list might be incomplete.
Explanation
- {0}
- An error condition.
- {1}
- The name of a file.
- {2}
- The line number in the file.
Because of the specified error, the dependency list
of the selected resource might be incomplete.
User response
Correct the condition that caused the specified error
and try the action again.
CRRZI0593E
An exception occurred during file operation validation.
Explanation
A validation error occurred when you attempted one
of the following actions:
- An action on a file, such as read, create, write, or copy.
- An operation on a data set such as COMPRESS, MIGRATE, or HRECALL.
You might not have the correct authority to do these actions.
User response
Make sure that you have the correct authority on
the remote system to do the operation. Ask your systems administrator
to grant you the authority that you need.
CRRZI0595I
The Java Virtual Machine (JVM) has not yet terminated. Click OK to terminate the JVM, wait 30 seconds for it to terminate on its own, or click Cancel to cancel the installation of Rational Developer for System z product updates.
Explanation
The remote system to which you are connecting is configured
to automatically download product updates. During the process of shutting
down Rational Developer for System z, the Java virtual machine (JVM) failed to terminate in
a short amount of time.
User response
- To terminate the Java virtual machine immediately, click OK. Rational Developer for System z shuts down and IBM Installation Manager starts to begin
the product update. After the product update completes, Rational Developer for System z restarts automatically.
- To cancel the product update and shut down Rational Developer for System z, click Cancel. The next time you
start Rational Developer for System z and connect this remote system, you are prompted to install
the product update again.
- To allow more time for the Java virtual machine to terminate,
wait 30 seconds. If it does not terminate within 30 seconds, click OK or Cancel.
CRRZI0596E
'{0}' is not a valid PL/I logical NOT symbol.
Explanation
- {0}
- A symbol
The specified symbol cannot be used as the PL/I
logical NOT symbol.
User response
Refer to the PL/I language reference for a list
of valid symbols and try the action again.
CRRZI0597E
The file operation type {0} for resource {1} is not valid.
Explanation
- {0}
- A file operation
- {1}
- A resource name
A problem was encountered while attempting to carry
out the requested operation which prevents the operation from completing.
User response
Examine the detailed error message for the problem
and take the appropriate remedial action.
CRRZI0598E
Failed to load BCT file {0}. See log file for details.
Explanation
- {0}
- The name of a bidirectional conversion table
A problem was encountered when trying to set the
path of the bidirectional conversion table (BCT) file.
User response
For details about this error, see the .log file
in the .metadata folder of the current Rational Developer for System z workspace.
CRRZI0599E
Failed to load mapping from file {0}.
Explanation
- {0}
- The name of an MVS mapping file.
A problem was encountered when trying to read the
specified MVS mapping root file.
User response
For details about this error, see the .log file
in the .metadata folder of the current Rational Developer for System z workspace.
CRRZI0601E
Resource {0} is already locked.
Explanation
- {0}
- The name of a file
The current operation requires an exclusive lock
on the specified file but the file is already locked.
User response
If you are not already working with the file, contact
your systems administrator for assistance locating the source of the
lock.
CRRZI0602E
Could not find the log in DataStore.
Explanation
The current operation requires a DataStore log, but
one was not available.
User response
Disconnect from the remote system and connect again.
Try the operation again. If you continue to receive this error, contact
your systems administrator.
CRRZI0603E
The high-level qualifier {0} cannot be added.
Explanation
- {0}
- A high-level qualifier
The high-level qualifier that is associated with
the target of the move or copy operation cannot be found.
User response
Check that you entered the correct target name and
try the operation again.
CRRZI0604E
The upload failed.
Explanation
A problem occurred while attempting to upload the
file contents to the remote system.
User response
Examine the detailed error message for the problem
and take the appropriate remedial action.
CRRZI0605E
An unexpected error occurred during exception handling. {0}
Explanation
- {0}
- A file operation
An unexpected error occurred when attempting to
validate the requested file operation.
User response
For details about this error, see the .log file
in the .metadata folder of the current Rational Developer for System z workspace.
CRRZI0606E
Failed to set the browse request for file {0}.
Explanation
- {0}
- A file name
A problem occurred while attempting to set the browse
request session property on the file.
User response
Examine the detailed error message for the problem
and take the appropriate remedial action.
CRRZI0607E
The file is already locked by alias or reference.
Explanation
The current operation requires an exclusive lock on
the specified file, but an alias of or reference to the file is already
locked.
User response
If you are not already working with the alias or
reference, contact your systems administrator for assistance locating
the source of the lock.
CRRZI0608E
The file cannot be downloaded.
Explanation
An unexpected error occurred when Rational Developer for System z attempted
to download the requested remote file.
User response
For details about this error, see the .log file
in the .metadata folder of the current Rational Developer for System z workspace.
CRRZI0609E
Resource type {0} is not supported.
Explanation
- {0}
- A resource type
A remote error marker cannot be created because
the selected resource is not an MVS resource.
User response
Select an MVS resource and try the action again.
CRRZI0610E
SCLM status unknown.
Explanation
Certain operations are not allowed when a resource
is under SCLM control, but the Rational Developer for System z server
code does not support this check.
User response
Contact your systems administrator.
CRRZI0611E
Failed to store mapping to file {0}.
Explanation
- {0}
- The name of an MVS mapping file.
A problem occurred when
Rational Developer for System z attempted
to save the current file system mappings.
User response
Examine the detailed error message for the problem
and take the appropriate remedial action.
CRRZI0612E
The system is not connected. Connect to the remote system and try the operation again.
Explanation
You must be connected to a remote system to work with
remote z/OS resources.
User response
Connect to the remote system and try the operation
again.
CRRZI0613I
The specified member '{0}' does not exist in the data set '{1}'. Do you want to create this new member?
Explanation
On the Find Member window, you typed
a member name that does not exist in the partitioned data set.
User response
- To create a member, click Yes. The new
member is created in the data set.
- To close this message and return to the Find Member window without creating a member, click No. If you mistyped the member name, you can try the search again.
CRRZI0614W
The result set contains {0} matches. A maximum of {1} matches can be displayed. Refine the member name pattern or change the preference and try again.
Explanation
On the Find Member window, you typed
a member name pattern that results in more matches than the current
limit.
User response
- To refine the member name pattern, try including more characters
in the name. Instead of searching for MY*, for example, search for
MYFIL*.
- To increase the result set limit:
- Click Window > Preferences. The Preferences window opens.
- Expand the Remote Systems and z/OS sections and click MVS Files.
- In the Maximum results for Find Member field,
specify the maximum number of search results to return with the Find
Member action. The default value is 1000 members.
CRRZI0615I
Request was submitted for '{0}'.
Explanation
- {0}
- A data set name.
The requested action for the data set indicated
by
{0} completed successfully.
User response
No action is required.
CRRZI0616I
Request was submitted for {0} data sets.
Explanation
- {0}
- The number of data sets for which the request was submitted.
The requested action for the number of data sets
indicated by
{0} completed successfully.
User response
No action is required.
CRRZI0617I
Request was submitted for {0} of {1} selected data sets.
Explanation
- {0}
- The number of data sets for which the action completed.
- {1}
- The number of data sets for which the action was requested.
The requested action for some data
sets completed successfully. The action was requested for the number
of data sets indicated by {1} and completed successfully for the number
of data sets indicated by {0}.
User response
No action is required.
CRRZI0618E
Request was not submitted.
Explanation
The requested action for the selected data set did
not complete successfully.
User response
Try the operation again. If the failure recurs, contact
your systems programmer.
CRRZI0619W
Are you sure you want to delete mapping '{0}'?
Explanation
This message prompts you to confirm a request to delete
a z/OS file system mapping.
User response
Click Yes to delete the mapping
or No to cancel the request.
CRRZI0620W
The result set contains {0} matches. A maximum of {1} matches can be displayed. Refine the data set name pattern and try again.
Explanation
In the Retrieve Data Set window
a maximum of {1} matching data sets can be displayed.
The data set name pattern entered matches more data set names than
the maximum allowed.
User response
Use a data set name pattern that results in fewer
matches. For example, if you previously typed USERID.TEST.C*,
typing USERID.TEST.COB* might result in fewer
matches.
CRRZI0621I
'{0}' has been compressed successfully.
Explanation
This message indicates that the Compress action
for the data set indicated by {0} completed successfully.
User response
No action is required.
CRRZI0622I
{0} data sets have been compressed successfully.
Explanation
This message indicates that the Compress action
for a number of data sets indicated by {0} completed
successfully.
User response
No action is required.
CRRZI0623I
{0} of {1} data sets have been compressed successfully.
Explanation
This message indicates that the Compress action
for some data sets completed successfully. The action was requested
for the number of data sets indicated by {1} and
completed successfully for the number of data sets indicated by {0}.
User response
No action is required.
CRRZI0624E
The data set was not compressed.
Explanation
This message indicates that the Compress action
for the data set indicated by {0} did not complete
successfully.
User response
Attempt the compress again. If the failure recurs,
contact your systems programmer.
CRRZI0626I
Are you sure you want to remove the selected global variable?
Explanation
This message is a prompt to confirm the removal of
a global variable.
User response
Select Yes or No.
CRRZI0627I
Are you sure you want to remove the selected user variable?
Explanation
This message is a prompt to confirm the removal of
a user variable.
User response
Select Yes or No.
CRRZI0628I
Are you sure you want to remove the preprocessor?
Explanation
This message is displayed when you remove a local
preprocessor on the Local Preprocessor page of
the property group editor. There is no undo action for removing a
local preprocessor.
User response
To delete the local preprocessor, click OK.
To keep the local preprocessor, click Cancel.
CRRZI0629I
Are you sure you want to remove the step?
Explanation
This message is displayed when you remove a step from
a Procedures and Steps table in the property
group editor. There is no undo action for removing a step.
User response
To remove the step, click OK. To keep the
step, click Cancel.
CRRZI0630E
Cannot open a null resource.
CRRZI0631E
Cannot find {0}.
Explanation
- {0}
- The path of the z/OS UNIX file.
User response
Ensure that the z/OS UNIX file exists. Try the operation
again.
CRRZI0632I
For successful generation from this copybook, the copybook should be self-contained.
Explanation
For the operation to work successfully for this copybook,
the copybook must not have any dependencies.
User response
Make sure that the copybook does not have any dependencies.
Try the operation again.
CRRZI0635I
This kind of project is associated with the {0} perspective. Do you want to switch to this perspective now?
Explanation
This message displays in response to successful creation
of a new project. It prompts you to switch to the perspective that
is most commonly used to work with the project type.
User response
Click Yes to switch to the
perspective or No to remain in the current
perspective.
CRRZI0636I
This kind of project, including MVS subprojects, workstation COBOL projects, and workstation PL/I projects, is associated with the z/OS Projects perspective. Do you want to switch to this perspective now?
Explanation
This message displays in response to successful creation
of a new project. It prompts you to switch to the z/OS Projects perspective, which is most commonly used to work with this project
type.
User response
Click Yes to switch to the
z/OS Projects perspective or No to remain in
the current perspective.
CRRZI0637W
The project {0} cannot be built because it is offline.
Explanation
A build request was submitted for an offline project.
A project must be online to be built.
User response
Move the project to online state and try the build
operation again.
CRRZI0638W
Contact your administrator to ensure that the build server is running on the remote system and that the correct port is specified.
Explanation
A build request was submitted, but the build server
cannot be found.
User response
Contact your system administrator.
CRRZI0642W
The file {0} is locked by another user and will be opened in read-only mode.
Explanation
An edit request was submitted for a locked file. The
file can be opened for read-only access, but it cannot be edited.
User response
To determine the lock owner of a remote resource,
open the properties view and expand the Info category
to see the Lock owner property.
CRRZI0643W
The file {0} is locked by '{1}' and will be opened in read-only mode.
Explanation
An edit request was submitted for the specified file,
which is locked by the specified user. The file can be opened for
read-only access, but it cannot be edited.
User response
No response is required.
CRRZI0644W
An error occurred while attempting to obtain a file lock. The file {0} will be opened in read-only mode. Disconnect and reconnect all z/OS remote systems.
Explanation
An edit request was submitted for a locked file. The
file can be opened for read-only access, but it cannot be edited.
User response
You can continue to browse the file in read-only
mode, but to correct the file lock problem you need to reconnect to
the remote system.
CRRZI0645W
'{0}' already exists. Would you like to overwrite it?
Explanation
- {0}
- A file name.
A request was made to export a property group, z/OS
project, or z/OS file system mapping to a file, but the target file
exists.
User response
To overwrite the file, click Yes.
To cancel the export operation, click No.
CRRZI0665E
Could not perform the project build operation.
Explanation
A Rebuild Project or Rebuild
Subproject request cannot be completed.
User response
Before building a project or subproject:
- Ensure that you are connected to the remote system.
- Verify that the build settings in the property group are specified
correctly.
CRRZI0666W
Could not open file {0}.
Explanation
- {0}
- The name of a file.
The editor tried to open the file, but the open operation failed
with an exception. The file cannot be opened.
User response
Verify that the file exists and try the operation
again.
CRRZI0667W
Could not open file {0}: {1}.
Explanation
- {0}
- The name of a file.
- {1}
- A message that indicates the exception that occurred.
The editor tried to open a file,
but failed with an exception. The file cannot be opened
User response
Verify that the file exists and try the operation
again.
CRRZI0668I
The z/OS project has been exported successfully. The source files in the project are not exported in this operation. Only the project structure and the associated property groups are exported.
Explanation
This message indicates a successful export z/OS project
operation.
User response
No response is required.
CRRZI0669E
A resource exists with a different case:
Explanation
A request to drag a local file into a local folder
in the z/OS Projects view failed. The file cannot
be copied because a resource with the same name but in a different
case exists in the target folder.
User response
Verify the source file name and target folder and try the operation
again.
CRRZI0671W
Failed to download {0}.
Explanation
Attention: The work offline and work online
operations for a remote resource are deprecated.
- {0}
- The name of a remote resource.
A problem occurred during the download
action of a work online operation. A local copy of the resource cannot
be created in the offline project.
User response
No action is required.
CRRZI0672W
Unable to migrate property {0}.
Explanation
Attention: The work offline and work online
operations for a remote resource are deprecated.
- {0}
- The name of a property in a property group.
As part of a work offline operation,
all the selected remote resources are downloaded to a local project
and all the properties that are associated with the remote resource
are migrated to the local resource. An error occurred while the operation
was migrating a property.
User response
Check the property for which the migration failed
and make sure to set it before you run operations like syntax check,
which uses the properties of the local resource.
CRRZI0673W
Any non-uploaded changes will be lost. Are you sure you want to continue?
Explanation
Attention: The work offline and work online
operations for a remote resource are deprecated.
Before
you take a project online by using the
Work Online action,
you must upload the changes that you made to the resources when the
project was offline. If you click
Work Online without
uploading the changes that were made locally (while the project was
offline), the changes are lost. You must confirm that the work online
operation can continue, which causes the local changes to be lost.
User response
- Before you click Work Online, upload any
changes that you made to the resources when the project was offline.
- To upload any changes that you made while the project was offline,
select them in the Changes view and then select Upload from
the menu.
- After you upload all the changes that you want to save, click Work
Online.
CRRZI0674W
At least one of the values of your SYSLIB or local compiler options has changed since the project was taken offline. These changes will be lost when the project is online. Click OK to continue, or click Cancel to return to the wizard.
Explanation
When a project is offline, the resources on the remote
system are still accessible to others. You must merge your changes
with any changes other users made to resources.
User response
To upload and changes that you made while the project
was offline, select them in the Changes and then select Upload from
the menu. After you upload all the changes you want to save, click Work
Online.
CRRZI0675W
Failed to upload {0}.
Explanation
- {0}
- The name of a local resource.
During the upload action of a work
online operation, a problem occurred while the operation was uploading
the local resource and creating a remote resource.
User response
No action is required.
CRRZI0676I
You are requesting to export configuration files to group {1}, which is different from the group {0} currently associated with your workspace. Click OK to continue or Cancel to return to the Export wizard.
Explanation
The push-to-client feature allows a workspace to be
associated with only one access group. You previously exported configuration
files to group {0} and are now requesting to export
these configuration files to group {1}.
User response
- If you intended to export the same configuration files to both
groups, click OK.
- If you intended to export files to group {1} from a different workspace, click Cancel,
switch to a different workspace, and then try the export operation
again.
CRRZI0677W
Your authorization to access product group {0} has changed since you last connected to this remote system. The product updates will not be imported into this workspace.
Explanation
The remote system to which you connected uses push-to-client
access groups to control access to product updates. Since you last connected to this system, you
were removed from access group {0}. While you can
still connect to this remote system, you can no longer receive push-to-client
updates from it.
User response
If you do not need any product updates from this
remote system, then no action is required. If, however, you need to
receive updates from this remote system, contact your system administrator.
CRRZI0678W
Product groups have been disabled since you last connected to this remote system. The product updates for group {0} will not be imported into this workspace.
Explanation
The remote system to which you connected previously used
push-to-client access groups to distribute product updates. Since
you last connected to this system, access groups were disabled. While
you can still connect to this remote system, you can no longer receive
push-to-client updates from group {0}.
User response
No action is required.
CRRZI0687E
System z Data Editor failed to open the file {0}.
Explanation
The System z Data Editor could not open the specified
file. This error occurs when the downloaded cache files are not valid.
User response
Clear the local downloaded cache and open the dataset
again.
CRRZI0691E
System z Data Editor failed to save the file {0} on the remote system.
Explanation
The System z Data Editor cannot save the data set
and the editing content cannot be saved to the remote system.
- {0}
- File name
User response
Confirm that the data set is not locked by another
editor. If the data set is open in another editor, close the editor
and the System z Data Editor. Reopen the data set with the System
z Data Editor.
CRRZI0735I
A folder was passed to the LogicalFSFileStore#getContents() method, which requires a file as input.
Explanation
Getting the contents of a LogicalFSFileStore is valid
only when the resource associated with the store is a file.
User response
No action is required.
CRRZI0736I
This file's contents are not available because the scheduling rule for the current job does not contain all the necessary resources.
Explanation
This message can occur when you add a remote partitioned
data set (PDS) to a subproject. To update the content-type file decoration,
the Eclipse system must query the contents of the Eclipse file system resource
that represents one of the members of the added PDS. To read its contents,
however, it is using a scheduling rule that does not include the cached
files folder. The request to add the resource to the subproject completed
successfully.
User response
No action is required.
CRRZI0737W
The Rational Developer for System z server has been configured to automatically download product updates to the client when you connect to the remote system. Current Product Version shows the product version currently installed on your workstation. A new version cannot be rejected and will be installed when you click OK.
Explanation
The remote system to which you are connecting is configured
to automatically download product updates. You are not allowed to
reject these updates. When you click
OK, your
workbench is shut down and IBM Installation Manager is started to
install the product updates. The workbench is automatically restarted
after the product update completes.
If you are operating
Rational Developer for System z on a Linux platform, the following message text also displays:
Rational Developer for System z will shut down but
you will not see any status. The product will
restart automatically in a few minutes.
User response
Click OK.
CRRZI0738E
Update of a remote file failed.
Explanation
A request to update a remote file failed.
User response
CRRZI0739E
An error occurred when downloading the preprocessor output.
Explanation
The product attempts to download the remote preprocessor
output after it runs the remote preprocessor. An error while the product
was downloading the output.
User response
Verify that you are still connected to the system
on which the remote preprocessor runs and that you have read access
to the data set that contains the preprocessor output.
CRRZI0740E
The remote preprocessor ended with an error.
Explanation
The script that runs the remote preprocessor finished
with an error.
User response
To see the error, click Details.
CRRZI0741E
The preprocessor output {0} was not found.
Explanation
- {0}
- The file that contains the preprocessor output.
The product ran the script that starts the remote
preprocessor, but cannot find the preprocessor output.
User response
Verify that you are running the script that you intend
to run. If so, verify that the script is executing correctly.
CRRZI0742E
The remote preprocessor {0} was not found.
Explanation
- {0}
- The preprocessor name.
The product cannot find the remote preprocessor
that is specified in the property group.
User response
Verify that the remote preprocessor has the data
set and member name that is specified in the property group and that
you have read access to the data set that contains the preprocessor.
CRRZI0745E
The project '{0}' does not have a property group associated with it. Associate a property group and then try the project build operation again.
Explanation
To build a project, you need associate a property
group with it. No property group is associated with the project.
User response
Use the Associate Property Group action to associate
a property group with a subproject and then try the build operation
again.
CRRZI0746E
VSAM data set allocation failed.
Explanation
A New > Allocate VSAM Data Set operation failed to
allocate the data set. The most common reason for this failure is
missing values for the space unit, primary unit, and secondary unit
parameters.
User response
Check the allocation parameters on page 3 of the
wizard and try the operation again. Contact your system administrator
for guidance on specific allocation parameter values.
CRRZI0747E
The compiler option "CICS('CTS42')" is not applicable for a build operation. Remove the suboption "CTS42" and try again.
Explanation
The CICS suboption CTS42 was specified for a local
build. This suboption is valid only in the context of syntax check
when the source code is being checked against the syntax of CICS Transaction
Server for z/OS 4.2.
User response
If you are building a local application, remove the
CTS42 suboption from the CICS compiler option.
CRRZI0748E
Record length is not available
Explanation
The record length information is not available from
the property associated with the data set.
User response
Check the status of the server to see if there are
errors. Try connecting to the server again.
CRRZI0749E
The dataset cannot be opened because data format is Undefined.
Explanation
The file cannot be open because the data set record
is defined as RECFM=U. The System z Data Editor cannot open a data
set whose record format is undefined because the editor uses the record
format and length to determine each record of the sequential data
set.
User response
Use a different editor to open the data set.
CRRZI0750E
File '{0}' contains characters that cannot be transferred correctly between the local and remote systems. The file will be opened in read-only mode.
Explanation
The Rational Developer for System z editors are able to preserve the integrity of characters
as they are transferred from the remote system to the workstation
and back again. For some code pages, however, it is not possible to
preserve round-trip integrity of certain characters. This message
warns that the file under edit contains characters whose round-trip
integrity cannot be preserved. Because the file is being edited from
the remote system, it is opened in read-only mode.
User response
To edit the file, copy it to a local project in your
workspace and change the corrupted characters before you copy it to
the remote system.
CRRZI0752E
Unable to communicate with the server. Verify the port number and Debug Tool classpath variables in job IPVGSVRJ on the remote system.
Explanation
A connection to the debug tool cannot be made.
User response
Verify the port number and try the operation again.
CRRZI0753I
Specify the required information to connect to IBM Problem Determination Tools Common Components Server.
Explanation
This message displays when you save a new DB2 and
IMS debug configuration. It prompts you to define connection settings
for the DB2 and IMS debug configuration.
User response
Click OK. The DB2
and IMS Debug Configuration preferences window opens. Use
this window to define connection settings.
CRRZI0754E
Unable to update the debug profile. The profile data set "{0}" might be in use or you do not have write access.
Explanation
The Debug Configurations wizard
cannot update the debug profile data set.
User response
Ensure that you have write access to the debug profile
data set and that it is not in use and try the operation again.
CRRZI0755W
You are requesting to export configuration files to group {0}. This action creates an association between the workspace and configuration group {0}.
Explanation
When you export a configuration file from a workspace
to a configuration group, the workspace is bound to that
group. All subsequent export requests from this workspace are exported
to the same group.
User response
No response is required.
CRRZI0756I
You are opening a file that has an associated property group that specifies remote libraries on the system "{0}". To access the include files in those libraries, connect to the remote system.
Explanation
Access to remote libraries requires access to the
remote system on which they are located.
User response
Connect to the remote system.
CRRZI0757E
The copy function doesn't support a record length that exceeds the maximum block size.
Explanation
This error occurs when attempting to copy and paste
from a local text file with a large record length to a new MVS sequential
data set. Rational Developer for System z cannot allocate a data set with a record length that is
longer than the maximum block size. The data set is not created.
User response
No response is required.
CRRZI0758E
Resources with an undefined record format cannot be copied.
Explanation
An attempt was made to copy a binary file (such as
a load module) from one remote system to another or between local
and remote systems. This operation is not supported.
User response
No response is required.
CRRZI0759E
Resources with an undefined record format cannot be copied across systems.
Explanation
An attempt was made to copy a binary file (such as
a load module) from one remote system to another or between local
and remote systems. This operation is not supported.
User response
No response is required.
CRRZI0760W
This filter contains {0} data sets, and the expansion of the filter might take a long time. Do you want to proceed?
Explanation
The number of data sets in a filter exceeds the threshold
set in the Default expansion page size for filters and
data sets field of the MVS Files preferences
page.
User response
Click
Yes to continue expanding
the filter or
No to cancel the operation. To
change the warning threshold:
- To open the MVS Files preferences page, select and then expand and click MVS
Files.
- Type a number in the Default expansion page size for
filters and data sets field.
CRRZI0761E
The selected remote system is not connected. Connect to the remote system and try again.
Explanation
On the Add Include Library, Edit
Include Library, Add Copy Library,
or Edit Copy Library window, the remote system
that is selected is not connected.
User response
Connect to the remote system and try the operation
again.
CRRZI0762E
Could not read a remote file that has invalid block size.
Explanation
An attempt was made to open, browse, or view a data
set with a block size of 0.
User response
Modify the data set characteristics to specify a
valid block size and try the operation again.
CRRZI0763I
You are opening a remote file with an external editor. As a result, any changes made to the file cannot be saved on the remote system.
Explanation
Remote files that are edited with an external editor
cannot be saved to the remote system.
User response
To edit a remote file and save the changes to the
remote system, use an internal editor, such as the System z LPEX Editor,
COBOL Editor, or PL/I Editor.
CRRZI0764W
Migrated data sets will not be considered in the look up path. Select the '{0}' in the Remote Systems view and perform the HRECALL action.
Explanation
- {0}
- The migrated data set
The JCL procedure lookup path contains a data set
that is migrated. Migrated data sets are not accessible for JCL navigation.
User response
To recall a migrated data set, select the data set
name in the Remote Systems view and then select HRECALL from
the menu.
CRRZI0765E
The data set '{0}' could not be found. Verify that both the data set name was highlighted correctly and the data set exists.
Explanation
- {0}
- The data set name
A data set highlighted in the editor cannot be found
by using the
Navigate to data set action.
User response
Verify the data set name and try the action again.
CRRZI0766E
The JCL procedure cannot be found in the JCL procedure look up path. Verify that both the file and the library are allocated properly.
Explanation
A JCL procedure name highlighted in the editor cannot
be found by using the Open JCL Procedure action.
User response
Verify that the libraries specified in the Include
and procedure search libraries property are correct and
that the member name is correct. Try the action again.
CRRZI0767W
The resource '{0}' does not have a property group associated with it. A property group contains information required to resolve dependencies and enable advanced editor features. Click OK to open the resource without associating a property group or choose an action.
Explanation
- {0}
- A partitioned data set member
When you open a file in an editor, it checks for
a property group associated with the file. Property groups contain
settings that enable the editor the resolve dependencies, such as
copybooks and include files. This message prompts you to either open
the file without a property group or to create or associate a property
group with the file.
User response
To open the file without associating a property group,
click
OK. To create or associate a property
group, click one of the following links:
- Associate an existing property group: Opens the Associate
Property Group window so that you can choose a property
group to associate with the file.
- Associate an existing property group with the parent data set:
Opens the Associate Property Group window so
that you can choose a property group to associate with the file and
with the file's parent data set.
- Associate an existing property group with parent MVS subproject:
Opens the Associate Property Group window so
that you can choose a property group to associate with the file and
with the subproject that contains the file.
- Create and associate a new property group: Opens the property
group editor so that you can create a property group and associate
it with the file.
- Create and associate a new property group with the parent data
set: Opens the property group editor so that you can create a property
group and associate it with the file and with the file's parent data
set.
- Create and associate a new property group with parent MVS subproject:
Opens the property group editor so that you can create a property
group and associate it with the file and with the subproject that
contains the file.
If you choose to associate an existing property group, the file
is opened after the association is made. If you choose to create a
property group, you need to request the file open action again.
CRRZI0768I
{0} of {1} jobs were submitted successfully. To see a list of jobs and their status, click Details. From the Details view, you can select one or more successfully submitted jobs to locate in the Remote Systems view.
Explanation
- {0}
- The number of jobs that were submitted successfully
- {1}
- The total number of jobs that were submitted
User response
No action is required. For more information about
submitting multiple jobs, see the related topics.
CRRZI0769E
The Work Offline action is disabled for remote system {0}.
Explanation
Attention: The work offline and work
online operations for a remote resource are deprecated.
- {0}
- The name of a remote system
The remote system is configured to deny permission
to work offline.
User response
Consult your systems administrator if you have questions
about offline permissions on a remote system.
CRRZI0770E
The remote system {0} associated with this project is not connected. Connect to the remote system and try the operation again.
Explanation
Attention: The work offline and work
online operations for a remote resource are deprecated.
- {0}
- The name of a remote system
Systems administrators have the
ability to configure remote systems to deny permission to work offline.
To determine if working offline is allowed on the remote system, you
must be connected to the remote system before you request the
Work
Offline action.
User response
Connect to the remote system and try the Work
Offline action again.
CRRZI0771E
The configuration group name {0} contains the invalid character {1}. Contact your administrator to have the name changed.
Explanation
- {0}
- The name of a push-to-client configuration group.
- {1}
- The character that is invalid.
Configuration groups are created and administered
on the remote system. If a configuration group name contains invalid
characters, then the configurations that it controls cannot be downloaded
to the workstation.
User response
CRRZI0772W
The server does not have enough memory available to perform the search.
Explanation
A partitioned data set member is tool large for the
server to search.
User response
Do one of the following actions:
- Specify more specific search conditions.
In the Remote z/OS Search window, click Search
Options and specify a smaller number in the Search
results limit field.
- To expand the server memory size, specify a larger value for the
Java maximum heap size in the rsed.envvars file
on the server. For more information about this file, see the Rational Developer for System z Host Configuration
Guide (SC23-7658).
CRRZI0773E
The server does not have enough memory available to download {0}.
Explanation
- {0}
- A data set name.
A data set is tool large for the server to download.
User response
CRRZI0774E
Some characters cannot be mapped using host code page '{0}'. Either change the host code page or remove the characters which are not supported by the host code page '{0}'.
Explanation
- {0}
- The host code page.
This error occurs when you create or save a remote
file that uses characters that are not supported by the host code
page of the container.
User response
Modify the host code page property of the remote
container:
- To open the container Properties window,
do one of the following actions:
- Right-click the container and select Properties from
the menu.
- Select the container and press Alt+Enter.
- From the list on the left side of the Properties window,
click Mapping.
- In the Host code page area of the window,
click Other and specify a host code page.
CRRZI0775E
Some characters cannot be mapped using local code page '{0}'. Either change the local code page or remove the characters which are not supported by the local code page '{0}'.
Explanation
- {0}
- The local code page.
This error occurs when you create or save a local or remote
file that uses characters that are not supported by the local code
page of the container.
User response
To modify the local code page property of a remote
container:
- To open the container Properties window,
do one of the following actions:
- Right-click the container and select Properties from
the menu.
- Select the container and press Alt+Enter.
- From the list on the left side of the Properties window,
click Mapping.
- In the Local code page area of the window,
click Other and specify a local code page.
To modify the local code page property of a local container:
- To open the container Properties window,
do one of the following actions:
- Right-click the container and select Properties from
the menu.
- Select the container and press Alt+Enter.
- From the list on the left side of the Properties window,
click Resource.
- In the Text file encoding area of the window,
click Other and specify a local code page.
CRRZI0776E
Failed to get the characteristics of the data set.
Explanation
An attempt to obtain the characteristics of the data
set, such as DSN type, data set organization, or record format, failed.
This error might be caused by a TSO command server error.
User response
CRRZI0777E
Problems occurred while adding Data Access Support to the selected resource.
CRRZI0778E
Problems occurred while removing Data Access Support from the selected resource.
CRRZI0779E
The options data set exists, but is not a sequential data set. Delete the data set before attempting to update the profile.
CRRZI0780E
The options data set is migrated. From the Remote Systems Explorer view, perform HRECALL on the sequential data set.
CRRZI0781E
The options specified "{0}" contains a string of more than 72 consecutive characters with no comma to break the string.
CRRZI0782E
An error occurred writing to the profile data set "{0}".
CRRZI0783E
The EQAOPTS data set "{0}" was unable to be allocated. {1}
CRRZI8502E
The format of the stored procedure source location is invalid.
Explanation
The stored procedure file in the Data Development
project no longer contains the name of a valid source file on a valid
MVS System.
User response
- If the source file exists as a member in a partitioned data set
on a system that is defined in the Remote Systems Explorer,
rename or copy the source file to a safe location.
- Delete the stored procedure in the Data Development Project.
- Re-create the stored procedure by using the Create Stored
Procedure Wizard.
- When the stored procedure is created, copy the saved source file
to the location of the default source file that was created by the
wizard.
- Try the action again.
CRRZI8503E
The source file is not available. You might need to connect to a z/OS system.
Explanation
A deployment operation was attempted, but you are
not connected to an MVS system in the Remote Systems view.
User response
Connect to the MVS system in the Remote
Systems view and try the operation again.
CRRZI8504E
Unable to locate source file '{0}' on system '{1}'.
Explanation
- {0}
- The name of a stored procedure source file.
- {1}
- The name of a remote system.
The source file that is associated with the stored
procedure is no longer available on the remote system. It might be
in a different location on your MVS system or renamed to a different
data set member name.
User response
Delete the stored procedure from the Data Development
project and re-create the stored procedure. If the source file is
available on the remote system, copy the source file to the location
of the default source file that was created by the Stored
Procedure Creation Wizard.
CRRZI8505E
The z/OS system definition for '{0}' does not exist. Switch to the z/OS Projects perspective and define '{0}' as a z/OS system with the appropriate IP address.
Explanation
- {0}
- The name of a remote z/OS system.
The data set member that is associated with the
stored procedure belongs to an MVS system in the
Remote
Systems Explorer with the name
{0}.
The system no longer exists.
User response
Switch to the z/OS Projects perspective
and define {0} as a z/OS system with the appropriate
IP address.
CRRZI8506E
The data set '{0}' is migrated. Select the data set in the Remote Systems view and perform the HRECALL action.
Explanation
You submitted a generate JCL request and specified
the partitioned data set name indicated by {0} as
the target data set for the generated JCL file. This data set is migrated
and is not available.
User response
In the Remote Systems view,
select the partitioned data set and then select HRECALL from the menu.
CRRZI8508E
'{0}' is not connected. Switch to the z/OS Projects perspective and connect to the z/OS system.
Explanation
- {0}
- The name of a remote z/OS system.
an edit or deploy operation for a stored procedure
was requested, but the MVS system that is associated with the stored
procedure is not connected. The source file cannot be accessed.
User response
in the Remote Systems Explorer,
connect to the remote system. Try the operation again.
CRRZI8509E
The volume '{0}' is offline. Contact your systems programmer to bring the volume online.
Explanation
- {0}
- The name of a data set.
The stored procedure source is in a data set that
is offline or migrated.
User response
Contact your systems programmer to bring the volume
online.
CRRZI9501W
There is 1 line with contents that exceed the maximum line length. Saving the file will result in truncation of this line. Do you want to continue?
Explanation
Whenever you save a file in the System z LPEX Editor,
COBOL Editor, or PL/I Editor, it checks for any lines that exceed
the record length limit. This warning opens when a line in the file
exceeds the record length limit.
User response
Click Yes to continue with
the file save operation or No to return to
the editor to fix the line in question. The editor positions the file
at the line that exceeds the record length limit.
CRRZI9502W
There are {0} lines with contents that exceed the maximum line length. Saving the file will result in truncation of these lines. Do you want to continue?
Explanation
Whenever you save a file in the System z LPEX Editor,
COBOL Editor, or PL/I Editor, it checks for any lines that exceed
the record length limit. This warning opens when more than one line
in the file exceeds the record length limit.
User response
Click Yes to continue with
the file save operation or No to return to
the editor to fix the lines in question. The editor positions the
file at the first line that exceeds the record length limit.
CRRZI9503W
The source has been modified since the backup copy was saved.
Explanation
Rational Developer for System z has an autosave function that creates a backup copy of
editor files on the local system. This warning indicates that the
backup copy created by an autosave operation is based on an earlier
copy of the source. The backup copy is opened in the editor.
User response
Use File > Save As to save
the backup to a different location and then use the compare tool to
merge changes from the backup with the source.
CRRZI9504I
A backup copy from {0} exists for the source you are opening. This occurred when your previous editing session ended abnormally. Would you like to open the backup copy in the editor?
Explanation
Rational Developer for System z has an autosave function that creates a backup copy of
editor files on the local system.
User response
Click Yes to open the backup
copy.
CRRZI9505W
The file cannot be saved on the host system. A backup copy has been created locally. You will be prompted to restore from this backup file the next time you open the remote file.
Explanation
Rational Developer for System z has
an autosave function that creates a backup copy of editor files on
the local system. This warning indicates that a backup copy is created
for a file that cannot be saved on the remote system.
User response
No action is required.
CRRZI9506W
The file has been changed on the file system. Do you want to replace the System z LPEX Editor contents with these changes?
Explanation
A file was changed in another editor on the file system.
Its contents no longer match the contents that are shown in the System
z LPEX Editor.
User response
Click Yes to update the contents
in the System z LPEX Editor. Click No to keep
the current contents of the editor. If you save the file without refreshing
the contents, the changes that are made in the other editor are lost.
Messages for TPF Toolkit Core
These are the messages that pertain to TPF Toolkit Core.
TPFC1001E
The file name field for {1} is empty.
Explanation
User response
TPFC1002E
The file name field for {1} is not unique.
Explanation
User response
TPFC1003E
The file name field for {1} is invalid.
Explanation
User response
TPFC1004E
The selected file {1} is not remote.
You cannot set remote properties on a local file.
Explanation
User response
TPFC1005E
The selected file {1} is not a TPF DLL configuration file.
The file is probably a dynamic link library.
Explanation
User response
TPFC1006E
The file cannot be created. The parent folder is not valid.
Select a valid parent folder.
Explanation
User response
TPFC1007I
File creation has been cancelled.
Explanation
User response
TPFC1008W
A file by the name of {1} already exists. Do you want to overwrite the existing file with the build script you are generating?
Explanation
User response
TPFC1010E
Error creating file.
Explanation
User response
TPFC2001E
The field {1} must be numeric.
Explanation
- {1}
- The content of the field
User response
TPFC2002E
The LINECOUNT value is invalid.
The value must be 0, or between 10 and 32767, inclusive.
Explanation
User response
TPFC2003E
The N field value is invalid.
The value must be numeric or "*" (asterisk).
Explanation
User response
TPFC2004E
M value must be less than N value.
Explanation
User response
TPFC2005E
The {1} value is invalid.
The value must be between 0 and 32767, exclusive.
Explanation
- {1}
- The content of the value
User response
TPFC2100E
No fields included.
Select one or more fields to be written to the output file.
Explanation
User response
TPFC2101E
No line-specific fields included.
Operation will continue with file information only. Select one or more line-specific field.
Explanation
User response
TPFC2102E
Unknown error occured while writing to file {1}.
Ensure the file can be accessed.
Explanation
User response
TPFC2103I
Successfully wrote {1} messages to file {2}
Explanation
- {1}
- The content of the message
- {2}
- File name
User response
TPFC2104E
Action unavailable - Remote Search view contains no results.
Explanation
User response
TPFC3000I
Filter name cannot be empty.
Explanation
User response
TPFC3001E
Filter name is not unique.
Filter names must be unique.
Explanation
User response
TPFC3002E
Filter name is not valid.
Explanation
User response
TPFC3003E
The folder {1} does not contain a valid {2} file.
Select a folder that represents a z/OS UNIX {3} and contains a {2} file with valid content.
Explanation
- {1}
- Folder name
- {2}
- File name
- {3}
- The name of a remote system
User response
TPFC3004E
The file {1} does not contain content that is valid for representing a z/OS UNIX {3}.
Select a folder that represents a z/OS UNIX {3} and contains a {2} file with valid content.
Explanation
- {1}
- File name
- {2}
- File name
- {3}
- The name of a remote system
User response
TPFC3005E
None of the {1} XML files in the folder {2} contain valid {3} file content.
Select a folder that represents a z/OS UNIX {4} and contains a {3} file with valid content.
Explanation
- {1}
- The name of an XML file
- {2}
- Folder name
- {3}
- File name
- {4}
- The name of a remote system
User response
TPFC3006E
The folder {1} does not represent a z/OS UNIX subproject. It has no {2} file and no child z/OS UNIX Filter folders.
Select a folder that has a {2} file or has child folders with a {3} file in them.
Explanation
- {1}
- Folder name
- {2}
- File name
- {3}
- File name
User response
TPFC3007E
The folder {1} does not represent a subproject.
Select a folder that represents a z/OS UNIX subproject. Folders that represent subprojects contain a {2} file.
Explanation
- {1}
- Folder name
- {2}
- File name
User response
TPFC3008E
The subproject {1} is not a z/OS UNIX subproject.
Select a folder that was created by exporting a z/OS UNIX subproject.
Explanation
- {1}
- The name of a subproject
User response
TPFC3009E
The {1} in subproject {2} could not be accessed.
Ensure the {1} file exists and has appropriate read permission.
Explanation
- {1}
- File name
- {2}
- The name of a subproject
User response
TPFC3010E
TPF Toolkit v2 and v3 projects cannot be selected in a single import.
Explanation
User response
TPFC3011E
A target environment must be selected.
Explanation
User response
TPFC3012E
The folder {1} does not contain a valid {2} file.
Select a folder that represents a HFS {3} and contains a {2} file with valid content.
Explanation
- {1}
- Folder name
- {2}
- File name
- {3}
- The name of an HFS folder
User response
TPFC3050I
Filter string cannot be empty.
Explanation
User response
TPFC3051E
There is already an identical filter string in the filter.
Change the path or file name pattern to make the filter string unique.
Explanation
User response
TPFC3052E
Filter string is invalid.
Explanation
User response
TPFC3053E
An existing, broader filter exists. It will override the current filter information.
Explanation
User response
TPFC3054E
Parent z/OS UNIX subproject must be specified.
Explanation
User response
TPFC3055W
The filter string you are attempting to add includes one or more files that are already included by an existing filter string. If you add this filter string, it will be merged with the existing filter strings.
Explanation
User response
TPFC3056E
There are already one or more filter strings that include files from the same location with a different user ID. You cannot include files from the same location with different user IDs in the same filter.
Explanation
User response
TPFC3060E
Connection type is invalid.
Explanation
User response
TPFC3061E
System name must be specified.
Explanation
User response
TPFC3062E
User name must be specified.
Explanation
User response
TPFC3063E
Path must be specified.
Explanation
User response
TPFC3064E
Path is invalid.
Explanation
User response
TPFC3065E
File pattern must be specified.
Explanation
User response
TPFC3066E
File pattern is invalid.
Explanation
User response
TPFC3070E
Filter creation failed.
Explanation
User response
TPFC3071E
Filter creation cancelled.
Explanation
User response
TPFC3072E
Error loading filter: {1}
The filter could not be loaded. Its filter.xml file may be corrupted.
Explanation
User response
TPFC3075E
One or more filter strings in filter {1} could not be resolved.
Explanation
User response
TPFC3080E
Files from {0} cannot be shown in filter {1} with user ID {2} because they are already shown with user ID {3}.
Files from {0} cannot be shown in filter {1} with user ID {2} because they are already shown with user ID {3}.
Explanation
- {0}
- The name of a remote system
- {1}
- Filter name
- {2}
- A user identifier
- {3}
- A user identifier
User response
TPFC3081W
The files from {0} are already shown in filter {1} under a different parent.
The files from {0} are already shown in filter {1} under a different parent. The existing and new filter strings will be merged.
Explanation
- {0}
- The name of a remote system
- {1}
- Filter name
User response
TPFC3082I
All files and folders from {0} are already shown in filter {1} by {2}.
All files and folders from {0} are already shown in filter {1} by {2}. The new filter string will not be added.
Explanation
- {0}
- The name of a remote system
- {1}
- Filter name
- {2}
- A user identifier
User response
TPFC3083W
All files and folders from {0} are included in {1} by the new filter string {2}.
All files and folders from {0} are included in {1} by the new filter string {2}. The existing filter string will be replaced with the new one.
Explanation
- {0}
- The name of a remote system
- {1}
- Filter name
- {2}
- The content of filter string
User response
TPFC3084I
The filter {0} already contains a filter string {1}.
The filter {0} already contains a filter string {1}. The new filter string will not be added.
Explanation
- {0}
- Filter name
- {1}
- The content of filter string
User response
TPFC3085W
Could not find files from folder {1} on host {2}. {3}
Explanation
- {1}
- Folder name
- {2}
- The name of a remote system
- {3}
- The error message returned by the failure
User response
TPFC3086W
Could not show files from host {1}. {2}.
Explanation
- {1}
- The name of a remote system
- {2}
- The error message returned by the failure
User response
TPFC3087W
Could not find some or all of the files from {1}. {2}
Explanation
- {1}
- A list of remote system names
- {2}
- The error message returned by the failure
User response
TPFC3100E
Cannot paste into folder {1} because the folder does not exist.
Check that the folder has not been deleted from the file system.
Explanation
User response
TPFC3101E
Cannot paste {1} to folder {2} because {1} does not exist.
Check that the file has not been deleted, renamed or moved on the file system since it was copied.
Explanation
- {1}
- File name
- {2}
- Folder name
User response
TPFC3102E
Error pasting {1} to folder {2}.
Check that the parent folder exist and has write access.
Explanation
- {1}
- File name
- {2}
- Folder name
User response
TPFC3103E
Cannot paste items into filter {1} because the filter does not reference any folder.
You must paste the filter strings or choose a filter that represents a folder.
Explanation
User response
TPFC4000W
Remote working directory has not been specified. Some actions may not work.
The subproject's remote working directory cannot be empty.
Explanation
User response
TPFC4001E
The subproject's remote working directory is invalid.
Explanation
User response
TPFC4050E
Subproject creation failed.
Explanation
User response
TPFC4051I
Subproject creation cancelled.
Explanation
User response
TPFC4052E
Error loading subproject: {1}.
The subproject could not be loaded. One or more of its filters may be corrupted.
Explanation
- {1}
- The name of the subproject
User response
TPFC4053I
Executed subproject create user exit {1}. Return code was {2}
Explanation
- {1}
- A command
- {2}
- The message returned by the command
User response
TPFC4054I
Executed filter create user exit {1}. Return code was {2}
Explanation
- {1}
- A command
- {2}
- The message returned by the command
User response
TPFC4055I
Executed target environment user exit {1}. Return code was {2}
Explanation
- {1}
- A command
- {2}
- The message returned by the command
User response
TPFC4080E
The subproject's build list is empty.
Explanation
User response
TPFC4081I
Building {1} with {2}...
Explanation
- {1}
- The item being built
- {2}
- The build action
User response
TPFC4082E
{1} is already included in the build list.
Explanation
User response
TPFC4083E
{1} cannot be added to the build list.
Only remote files with extension {2} can be added to the build list.
Explanation
- {1}
- File name
- {2}
- A list of file-name extensions; for example, *.c, *.cpp,
*.asm
User response
TPFC4084I
{1} has been successfully added to the build list.
Explanation
User response
TPFC4085E
Subproject Build List does not exist.
Explanation
User response
TPFC4086E
Subproject Build failed.
{1}
Explanation
- {1}
- Detailed messages for the build error
User response
TPFC4087I
Subproject Build has been cancelled.
Explanation
User response
TPFC4088I
Select the items to add to the build list.
Only remote files with extension {1} can be added to the build list.
Explanation
- {1}
- A list of file-name extensions; for example, *.c, *.cpp,
*.asm
User response
TPFC4089E
The build action with ID {1} could not be found.
The action may have been deleted. Use the Menu Manager to create the action.
Explanation
- {1}
- The name of an action
User response
TPFC4090E
The build item {1} could not be found.
The file may have been deleted.
Explanation
User response
TPFC4091E
The build item {1} does not have an associated build action ID.
Check the subproject's build list and assign a build action to the build item.
Explanation
User response
TPFC4092W
The build action with ID {1} could not be found. Now building with default build action {2}.
Explanation
- {1}
- An action identifier
- {2}
- An action name or identifier
User response
TPFC4093E
Unexpected exception occurred: Subproject is not valid.
Explanation
User response
TPFC4094I
Building subproject using subproject build list...
Explanation
User response
TPFC4095E
Build Actions List is Empty.
Make sure you have defined a valid build action for the specified file type.
Explanation
User response
TPFC4096W
Invalid build action found
One or more build actions referenced in the build list are not valid based on the menu option of the current target environment. Click OK to continue building the subproject or click Cancel to abort the build.
Explanation
User response
TPFC4100E
Action failed. MakeTPF control file {1} cannot be found in the subproject's remote working directory. Subproject's remote working directory has not been specified.
Specify the remote working directory for the subproject and try again.
Explanation
- {1}
- The name of the control file
User response
TPFC4101E
Action failed. TPF Make control file {1} cannot be found in the subproject's remote working directory {2}.
Explanation
- {1}
- The name of the control file
- {2}
- The name of the subproject's directory
User response
TPFC4102E
Action failed. A default build action cannot be found for the TPF Make control file.
Verify that a default build action is associated for *.cntl file in the Default Build Action preferences page.
Explanation
User response
TPFC4103E
Building project using TPF Make build tools...
Explanation
User response
TPFC4104E
Action failed. TPF Make control file {1} cannot be found.
Explanation
- {1}
- The name of a TPF Make control file
User response
TPFC4108E
Subproject build failed. A default build action cannot be found for submitting JCL.
Verify that a default build action is associated for *.jcl file in the Default Build Action preferences page.
Explanation
User response
TPFC4109E
Subproject build failed. A JCL file has not been specified to build the subproject.
Verify that a JCL file has been specified in the Build Mechanism preferences page.
Explanation
User response
TPFC4110E
Subproject build failed. The JCL file {1} required for building the subproject could not be located.
Verify that a valid JCL file has been specified in the Build Mechanism preferences page.
Explanation
- {1}
- The name of a JCL file
User response
TPFC4111E
Subproject build failed. The JCL file {1} is not on the same remote system as the subproject's remote working directory {2}.
Specify a JCL file that is on the same remote system as the remote working directory or modify the remote working directory.
Explanation
- {1}
- The name of a JCL file
- {2}
- The location of a directory
User response
TPFC4112E
Building subproject using JCL file {1}.
Explanation
- {1}
- The name of a JCL file
User response
TPFC4120E
Specify a valid JCL file.
Explanation
User response
TPFC4121E
A valid build action must be selected.
Explanation
User response
TPFC4130E
Cannot register subproject for debug. Either the subproject's build list is empty or the subproject's build list does not contain any programs that can be registered.
Only DLMs, LLMs and BAL programs can be registered.
Explanation
User response
TPFC4131E
Cannot register subproject for debug. The build mechanism for the subproject is invalid. The subproject's build list cannot be determined.
Explanation
User response
TPFC4132E
Registering the following programs from the subproject's build list:{1} {2}
Explanation
- {1}
- A line-break character
- {2}
- A list of program names
User response
TPFC4200E
Subproject references an invalid target environment - {1}.
Use the subproject's target environment properties page to remove the invalid target environment from the list.
Explanation
- {1}
- The target environment
User response
TPFC4300E
Select a parent project or subproject for the imported filter.
Explanation
User response
TPFC4301E
Subproject names cannot be empty.
Specify a unique and valid subproject name for source folder {1}.
Explanation
- {1}
- The name of the source folder
User response
TPFC4302E
{1}
Specify a unique and valid subproject name for source folder {2}.
Explanation
- {1}
- The name of a subproject
- {2}
- The name of the source folder
User response
TPFC4303E
There is already a subproject in the workspace with the name {1}.
Specify a unique subproject name for source folder {2}.
Explanation
- {1}
- The name of a subproject
- {2}
- The name of the source folder
User response
TPFC4304E
Cannot import multiple subprojects with the name {1}.
Specify a unique name subproject name for all source folders.
Explanation
- {1}
- The names of the subprojects
User response
TPFC4310E
Cannot set current target environment {1} for subproject {2}. The target environment exit failed with a return code of {3}.
Explanation
- {1}
- A target environment name; for example, My Target Environment
- {2}
- A subproject name; for example, My SubProject
- {3}
- The return code of the failure
User response
TPFC5000E
Script name cannot be empty.
Specify a name for the script.
Explanation
User response
TPFC5001E
Build script name exceeds limit of {1} characters.
Specify a name up to {1} characters.
Explanation
- {1}
- The maximum length of the name
User response
TPFC5002E
Build script file name and location cannot be empty.
Select a remote location and specify a build script file name.
Explanation
User response
TPFC5003E
Build script location is not remote.
Select a remote location for the build script.
Explanation
User response
TPFC5004E
Build script for {1} must have a {2} extension.
Specify a {2} extension for the file name.
Explanation
- {1}
- File name
- {2}
- File-name extension
User response
TPFC5010E
Configuration file {1} could not be found.
Explanation
- {1}
- The name of the configuration file
User response
TPFC5011E
Specify a valid data file.
The data file must be a valid remote file on the same remote host as the build script.
Explanation
User response
TPFC5012E
Specify a JCL template file.
Explanation
User response
TPFC5013E
Specify a valid system name. The system must be defined in the preferences page.
Explanation
User response
TPFC5014E
Specify a valid name for GDS output.
Explanation
User response
TPFC5015E
Specify the volume for the GDS output.
Explanation
User response
TPFC5016E
Specify a valid system name for VRDR output. The name must be defined in the preferences page.
Explanation
User response
TPFC5017E
Specify a user ID for VRDR output.
Explanation
User response
TPFC5018E
The selected build script file does not mention a valid module.
The selected build script file does not indicate that it is for a DLM, DLL or LLM.
Explanation
User response
TPFC5020E
Specify the output location for the module.
Explanation
User response
TPFC5021E
Specify inputs for the module.
Explanation
User response
TPFC5022E
Specify the right value for {1}. The current one is invalid.
Explanation
- {1}
- The name of the item for which an invalid version was specified
User response
TPFC5030E
Specify the system name.
Explanation
User response
TPFC5031E
Specify the system ID.
Explanation
User response
TPFC5032E
Specify SALVERS.
Explanation
User response
TPFC5033E
Specify PATVERS.
Explanation
User response
TPFC5034E
System already exists.
Explanation
User response
TPFC5035E
PDS member name {1} exceeds 8 character limit.
Specify a PDS member names with 8 characters or fewer.
Explanation
- {1}
- The name of a PDS member
User response
TPFC5036E
PDS member {1} is already an input.
Specify a different PDS member.
Explanation
- {1}
- The name of a PDS member
User response
TPFC5037E
The file {1} is already an input.
Specify a different file name.
Explanation
User response
TPFC5038E
PDS member {1} is specified twice.
Remove one instance of {1} from the list.
Explanation
- {1}
- The name of a PDS member
User response
TPFC5100E
Specify a valid TPF build script file.
The build script file must be a valid remote file.
Explanation
User response
TPFC5101E
Specify a valid *.lsc file.
The lsc file must be a valid remote file.
Explanation
User response
TPFC5102E
Error parsing {1}.
The BSC file must be a valid remote file.
Explanation
- {1}
- The name of a BSC file
User response
TPFC5103E
The bsc file {1} cannot be used to create a {2} build script.
The selected bsc file is for creating a {3}.
Explanation
- {1}
- File name
- {2}
- DLM, DLL,
or LLM
- {3}
- DLM, DLL,
or LLM
User response
TPFC5110E
Specify a valid file extension to append to the input files.
Explanation
User response
TPFC5112E
The file {1} is already listed as a configuration file.
Choose a unique file name to add to the list.
Explanation
User response
TPFC5200E
Error generating the build script.
Explanation
User response
TPFC5500E
The file {1} is already included in the source segment list.
Explanation
User response
TPFC5501E
Source segment must have a {1} file extension.
Explanation
User response
TPFC5502E
The file {1} is already included in the dependency list.
Explanation
User response
TPFC5503E
Dependency must have a {1} file-name extension.
Explanation
User response
TPFC5504E
Name field contains duplicate name {1}.
Ensure all names listed are unique.
Explanation
- {1}
- The content of name field
User response
TPFC5505E
Specify the program name.
The program name must be four characters.
Explanation
User response
TPFC5506E
Specify a valid program name.
The program name must be four characters.
Explanation
User response
TPFC5507E
Specify a function name for the App entry point.
An app entry point must be specified if export file is used.
Explanation
User response
TPFC5508E
Export file cannot be specified if app entry point is {1}
Explanation
- {1}
- One of the following constants: Main, Locale, Iconv
User response
TPFC5509E
Invalid makefile target.
Explanation
User response
TPFC5510E
Specify at least one source segment.
Explanation
User response
TPFC5511E
BAL name must be in lower case.
Explanation
User response
TPFC5516E
Specify a value for {1}.
Explanation
- {1}
- The label of the corresponding text field
User response
TPFC5517E
Error parsing control file {1}.
Verify that the control file is valid.
Explanation
User response
TPFC5518E
Control file {1} could not be found in the subproject's working directory {2}.
Verify that the control exists in the subproject's working directory
Explanation
- {1}
- File name
- {2}
- Directory name
User response
TPFC5519E
Specify a valid timeout value.
Explanation
User response
TPFC5520E
Specify the program name.
Explanation
User response
TPFC5521E
Specify the number of passes required in build (1 or 2).
Explanation
User response
TPFC5522E
Specify the makefile name.
Explanation
User response
TPFC5523E
Specify the target environment.
Explanation
User response
TPFC5524E
Specify the load attribute.
Explanation
User response
TPFC5525E
Specify the program type.
Explanation
User response
TPFC5526E
Program name is not valid.
Program name must be four characters only.
Explanation
User response
TPFC5527E
Program name must match makefile name. Makefile name is {1}.
Explanation
- {1}
- The name of the makefile
User response
TPFC5528E
MakeTPF build list cannot be saved. Subproject's remote working directory has not been specified.
Specify the remote working directory for the subproject and try again.
Explanation
User response
TPFC5529E
MakeTPF build list cannot be saved. Error writing to the control file {1}.
Verify that the control file {1} is not locked and is not write-protected.
Explanation
User response
TPFC5530E
Makefiles must have a {1} extension.
Specify a {1} extension for the file name.
Explanation
- {1}
- A file-name extension, for example, .mak
User response
TPFC5531E
Error writing to the subproject stub makefile {1}.
Verify that the subproject stub makefile {1} is not locked and is not write-protected.
Explanation
- {1}
- The name of the makefile
User response
TPFC5532E
Error generating the subproject stub makefile {1}. The subproject's control file could not be found.
Verify that the subproject's remote working directory is specified.
Explanation
- {1}
- The name of the makefile
User response
TPFC5533E
Error generating the subproject stub makefile {1}. No owning environment has been specified for the stubs.
Explanation
- {1}
- The name of the makefile
User response
TPFC5534E
Error generating the subproject stub makefile {1}.
Verify that the subproject's remote working directory is specified.
Explanation
- {1}
- The name of the makefile
User response
TPFC5535E
Error generating the subproject stub makefile. The subproject is invalid.
Explanation
User response
TPFC5536W
Error finding or loading the subproject stub makefile {1}.
Verify that a makefile exists by that name or regenerate the stub makefile from this page.
Explanation
- {1}
- The name of the makefile
User response
TPFC5537E
Specify at least one environment for the stub generation.
Explanation
User response
TPFC5538E
Specify an external control file.
Explanation
User response
TPFC5539E
Error parsing configuration file {1}.
Verify that the TPF Make configuration file is valid.
Explanation
User response
TPFC5541E
Sub-system name is invalid.
Explanation
User response
TPFC5542E
Specify at least one z/OS UNIX source location.
Explanation
User response
TPFC5543E
Specify at least one application source location.
Explanation
User response
TPFC5544E
MakeTPF configuration file cannot be found.
Make sure maketpf.cfg exists in your project working directory or TPF_CFG variable is set.
Explanation
User response
TPFC5545E
The project's configuration file cannot not be found.
Make sure maketpf.cfg exists in your project working directory or TPF_CFG variable is set.
Explanation
User response
TPFC5546E
Error generating project's configuration file.
Explanation
User response
TPFC5547E
Error generating maketpf.cfg.
Explanation
User response
TPFC5548E
Subproject cannot be built.
Explanation
User response
TPFC5549E
MakeTPF configuration cannot be saved. Subproject's remote working directory has not been specified.
Specify the remote working directory for the subproject and try again.
Explanation
User response
TPFC5550I
A MakeTPF configuration file was not found in the subproject's remote working directory. Specify the appropriate values to generate a new one.
Explanation
User response
TPFC5580W
The MakeTPF configuration file {1} was not found. The remote working directory has not been specified.
Explanation
User response
TPFC5590E
Action failed. The selection is invalid.
You can only run this action on a z/OS UNIX subproject.
Explanation
User response
TPFC5591I
Running MakeTPF target {1}...
Explanation
- {1}
- A make target label; for example, clean, objs,
or hfs2pds
User response
TPFC5592I
Action failed. The MakeTPF based build mechanism of the current target environment {1} for subproject {2} references an invalid action.
Verify that the action exists in the Menu Manager.
Explanation
- {1}
- The name of a target environment
- {2}
- The name of a subproject
User response
TPFC5593I
Action failed. The MakeTPF based build mechanism of the current target environment {1} for subproject {2} is invalid.
Verify that the build mechanism information exists in the Build Mechanism building block preference page.
Explanation
- {1}
- The name of a target environment
- {2}
- The name of a subproject
User response
TPFC5594I
Action failed. The MakeTPF based build mechanism of the current target environment {1} for subproject {2} references an invalid action. An action with ID {3} cannot be found.
Verify that the build mechanism is referring to a valid action.
Explanation
- {1}
- The name of a target environment
- {2}
- The name of a subproject
- {3}
- An action ID
User response
TPFC5600E
The LoadTPF file action definition could not be found.
Verify that there is a file action definition in the Menu Manager for the loadtpf command and it is assigned as a default build action for *.loadtpf file type.
Explanation
User response
TPFC5601E
The LoadTPF file action has failed.
The project MakeTPF control file cannot be found or it is empty.
Explanation
User response
TPFC5602E
The LoadTPF file action has failed. A valid TPF IP address was not specified.
Explanation
User response
TPFC6000W
The file {0} will still be shown in filter {1} after the move because of a broad filter.
Explanation
- {0}
- File name
- {1}
- Filter name
User response
TPFC6001W
The folder {0} will still be shown in filter {1} after the move because of a broad filter.
Explanation
- {0}
- Folder name
- {1}
- Filter name
User response
TPFC6002W
Some items may still be shown in their parent filters due to broad filters.
Explanation
User response
TPFC6003E
The folder {0} is a parent of the folder {1}. The folder cannot be moved into one of it's children.
Select a different parent folder that is not already a child of the folder being moved.
Explanation
- {0}
- Folder name
- {1}
- Folder name
User response
TPFC6004E
The folder {0} cannot be a source folder and a destination folder.
Select a different parent folder.
Explanation
User response
TPFC6005E
Move validation cancelled. Change the selection to revalidate.
Explanation
User response
TPFC6006E
Move cannot be completed. Source folders and destination folder are related.
Select a different parent folder.
Explanation
User response
TPFC6007E
Move cannot be completed. The selected filter contains files from {0} with user ID {1}; you cannot add files from the same location with user ID {2}.
Select a different parent filter.
Explanation
- {0}
- The name of a remote system
- {1}
- A user identifier
- {2}
- A user identifier
User response
TPFC6008E
No parent filter selected.
Select a parent filter for moved files and folders.
Explanation
User response
TPFC6009E
Can't move files or folders.
Select a different physical location or a different parent filter to complete the move.
Explanation
User response
TPFC6100W
Download action failed because a file named {1} already exists in folder {2}.
Select a target folder that does not contain a file with the same name, or choose to overwrite the existing file when prompted.
Explanation
- {1}
- File name
- {2}
- Folder name
User response
TPFC6101E
Download action failed because the file {1} could not be accessed.
Check the connection and retry the download action.
Explanation
User response
TPFC6102E
Download of file {1} failed because folder {2} could not be accessed.
Check the connection and retry the download action.
Explanation
- {1}
- File name
- {2}
- Folder name
User response
TPFC6103E
Download of file {1} failed because the file is not remote.
Only remote files can be downloaded.
Explanation
User response
TPFC6104E
Download of file {1} failed because the file is disconnected or inaccessible.
Explanation
User response
TPFC6105E
Upload of file {1} failed because the file is disconnected or inaccessible.
Explanation
User response
TPFC6106E
Upload of file {1} failed because the file is not remote.
Only remote files can be uploaded.
Explanation
User response
TPFC6107E
Upload of file {1} failed because the file was never properly downloaded.
Explanation
User response
TPFC6108E
File {1} is disconnected.
Enter connected mode for host {2} and retry.
Explanation
- {1}
- File name
- {2}
- The name of a remote system
User response
TPFC6109E
The file {1} does not exist in folder {2}.
Select the local folder where {1} was originally downloaded.
Explanation
- {1}
- File name
- {2}
- Folder name
User response
TPFC6110E
The file {1} has been modified on the remote system since it was downloaded.
Explanation
User response
TPFC6111I
The file {1} was successfully downloaded.
Local copy is: {2}
Explanation
- {1}
- The name of a remote file
- {2}
- The name of a local file
User response
TPFC6112E
Paste action failed because the clipboard is empty.
You must copy a file, folder, z/OS UNIX Filter, or z/OS UNIX Subproject before performing a paste.
Explanation
User response
TPFC6113E
Paste action failed because the clipboard contains invalid items.
When pasting to a folder, only files and folders can be pasted. Copy only files and/or folders to the clipboard and retry.
Explanation
User response
TPFC6114E
Paste action failed because the clipboard contains invalid items.
When pasting to a z/OS UNIX filter, only files and folders can be pasted. Copy only files and/or folders to the clipboard and retry.
Explanation
User response
TPFC6115E
Paste action failed because the clipboard contains invalid items.
When pasting to a z/OS UNIX subproject, only z/OS UNIX Filters can be pasted. Copy only z/OS UNIX Filters to the clipboard and retry.
Explanation
User response
TPFC6116E
Unexpected error pasting {1} into folder {2}.
Ensure folder {2} is not read-only and that there is enough disk space.
Explanation
- {1}
- File name or folder name
- {2}
- Folder name
User response
TPFC6117E
Paste failed because the folder {1} is read-only.
Select a destination that is not read-only.
Explanation
User response
TPFC6200E
Link action failed because a default build action was not found for *.o or *.obj files.
Explanation
User response
TPFC6500W
Download of file {1} failed because the copy operation to folder {2} was cancelled.
Retry the download operation.
Explanation
- {1}
- File name
- {2}
- Folder name
User response
TPFC6501W
Download action failed because a file named {1} already exists in folder {2}.
Select a target folder that does not contain a file with the same name, or specify the -r flag to replace the existing file.
Explanation
- {1}
- File name
- {2}
- Folder name
User response
TPFC6502I
The file {1} was successfully copied to {2}.
Explanation
- {1}
- File name
- {2}
- Folder name
User response
TPFC6503I
The folder {1} was successfully copied to {2}.
Explanation
- {1}
- Folder name
- {2}
- Folder name
User response
TPFC6504E
Copy of file {1} failed.
Ensure that the source and target are accessible and that the target is not write protected.
Explanation
User response
TPFC6505E
Copy of {1} failed.
Ensure that the source exists and is accessible.
Explanation
User response
TPFC6506E
Copy of {1} to folder {2} failed.
Ensure that the target folder exists and is accessible.
Explanation
- {1}
- File name or folder name
- {2}
- Folder name
User response
TPFC6507I
The file {1} was changed on the remote system since it was downloaded.
Explanation
User response
TPFC6508E
Deletion of file {1} failed because the file could not be accessed.
Explanation
User response
TPFC6509E
Deletion of folder {1} failed because the folder could not be accessed.
Explanation
User response
TPFC6510I
File {1} successfully deleted.
Explanation
User response
TPFC6511I
Folder {1} and it's contents were successfully deleted.
Explanation
User response
TPFC6512E
Delete action failed with an unexpected error.
Explanation
User response
TPFC6513E
Upload of file {1} from folder {2} failed because the folder {2} could not be accessed.
Explanation
- {1}
- File name
- {2}
- Folder name
User response
TPFC6514I
File {1} was successfully uploaded and remote changes were overwritten.
Explanation
User response
TPFC6515I
File {1} was successfully uploaded as {2}.
Explanation
- {1}
- File name
- {2}
- The name of a remote file
User response
TPFC6516E
Upload of file {1} failed because the remote version was modified.
Explanation
User response
TPFC6517I
The file {1} was successfully uploaded.
Explanation
User response
TPFC6518E
Upload of file {1} failed with an unknown error.
Explanation
User response
TPFC6519E
CreateFolder failed because the subproject {1} does not exist.
Explanation
- {1}
- The name of a subproject
User response
TPFC6520E
CreateFolder failed because the filter {1} does not exist in the subproject {2}.
Explanation
- {1}
- Filter name
- {2}
- The name of a subproject
User response
TPFC6521E
CreateFolder failed because the folder argument (-o) was invalid or not specified.
Explanation
User response
TPFC6522I
CreateFolder successfully created the folder {1} in the folder {2}.
Explanation
- {1}
- Folder name
- {2}
- Folder name
User response
TPFC6523I
CreateFolder successfully created all folders on the path {1}.
Explanation
User response
TPFC6524E
CreateFolder failed to create folder(s) {1} because an unexpected error occurred.
Explanation
User response
TPFC6525E
Could not create a filter string to show the folder {1} in the filter {2}.
There may be a user ID conflict.
Explanation
- {1}
- Folder name
- {2}
- Filter name
User response
TPFC6526I
CreateFolder failed to create {1} because the folder already exists.
Explanation
User response
TPFC6527I
setProperties failed because the subproject {1} or the filter {2} does not exist.
Explanation
- {1}
- The name of a subproject
- {2}
- Filter name
User response
TPFC6528E
QueryVariables failed because the subproject {1} does not exist.
Explanation
- {1}
- The name of a subproject
User response
TPFC6529E
QueryVariables failed because the filter {1} does not exist in the subproject {2}.
Explanation
- {1}
- Filter name
- {2}
- The name of a subproject
User response
TPFC6530E
QueryVariables failed because the file {1} does not exist in the filter {2}.
Explanation
- {1}
- File name
- {2}
- Filter name
User response
TPFC6531E
QueryVariables failed because there are no substitution variables named {1}.
Explanation
- {1}
- The name of a variable
User response
TPFC6532E
QueryVariables failed because the variable {1} cannot be resolved for the specified target.
Explanation
- {1}
- The name of a variable
User response
TPFC6533E
QueryVariables failed to write output to file {1}.
Explanation
User response
TPFC6534I
The variable is resolved successfully.
Explanation
User response
TPFC6535E
Open file failed because the file {1} could not be opened.
Explanation
User response
TPFC6536I
Open file success. File {1} opened.
Explanation
User response
TPFC6537W
Filter string added. Warning: {1}
Explanation
- {1}
- The returned warning message
User response
TPFC6538E
The name {1} is invalid for type {2}. Valid names for type {2} are: {3}.
Explanation
- {1}
- A name
- {2}
- An option-set type
- {3}
- Valid names for the type of option set
User response
TPFC6539E
The property {1} cannot be set at the file level. Specify a subproject only.
Explanation
- {1}
- The name of a property
User response
TPFC6540E
The folder {1} is not a valid remote working directory.
Explanation
User response
TPFC6541E
The subproject {1} does not exist.
Explanation
- {1}
- The name of a subproject
User response
TPFC6542E
A file named {1} already exists and will not be replaced.
Specify a new file name or add the -r flag to replace the existing file.
Explanation
User response
TPFC6543E
Migration scan cancelled by user. No results written to output file.
Explanation
User response
TPFC6544E
Migration scan failed writing output to file {1}. Error {2}.
Explanation
- {1}
- File name
- {2}
- The returned message
User response
TPFC6545I
Migration scan successfully completed. {1} results written to file {2}.
Explanation
- {1}
- The number of results
- {2}
- File name
User response
TPFC6546E
Migration results file {1} contains invalid date {2}.
Explanation
User response
TPFC6547E
File {1} is not a valid migration scan results file because it does not contain a scan date.
Explanation
User response
TPFC6548I
Successfully listed {1} results from {2}.
Explanation
- {1}
- The number of results
- {2}
- File name
User response
TPFC6549E
Failed reading results from file {1}. Error: {2}
Explanation
- {1}
- File name
- {2}
- The returned error message
User response
TPFC6550I
Successfully read and fixed {1} problems from results file {2}.
Explanation
- {1}
- The number of problems
- {2}
- File name
User response
TPFC6551E
{1} results successfully read from file {2}.
{3} errors fixed. {4} warnings fixed. {5} problems not resolvable. {6} problems not resolved due to overlap. {7} potential errors ignored.
Explanation
- {1}
- The number of results
- {2}
- File name
- {3}
- The number of errors
- {4}
- The number of warnings
- {5}
- The number of problems
- {6}
- The name of the problems
- {7}
- The number of potential errors
User response
TPFC6552E
Compare file with migrated version action was unable to repair all {1} problems in file file {2}.
{3} errors fixed. {4} warnings fixed. {5} problems not resolvable. {6} problems not resolved due to overlap. {7} potential errors ignored.
Explanation
- {1}
- The total number of problems
- {2}
- File name
- {3}
- The number of errors
- {4}
- The number of warnings
- {5}
- The number of problems that are not resolvable
- {6}
- The name of the problems
- {7}
- The number of potential errors
User response
TPFC6553E
{1} cannot be resolved, do not specify both a subproject and a target environment.
Explanation
User response
TPFC6554E
The {1} subproject does not have a current target environment associated with it.
Explanation
- {1}
- The name of a subproject
User response
TPFC6555E
The {1} target environment does not exist.
Explanation
- {1}
- The specified target environment
User response
TPFC6556E
Failed to resolve {1}. Make sure that this target environment variable is defined.
Explanation
- {1}
- The specified target environment
User response
TPFC6557E
Additional flags not required by the specified launch type was set. Check your options again to verify that your settings are correct.
Explanation
User response
TPFC6558E
The connection could not be created. Since a launch option was not selected, no optional flags, aside from -w, should be set.
Explanation
User response
TPFC6559E
The connection could not be created. Enter a valid port number.
Explanation
User response
TPFC6560E
The connection could not be created. Ensure that the connection does not already exist, and that all specified parameters are valid.
Explanation
User response
TPFC6561I
The connection was created successfully.
Explanation
User response
TPFC6562I
The filter string(s) for {1} are listed below.
Explanation
- {1}
- The specified target environmen
User response
TPFC6563E
Query failed because the subproject {1} does not exist.
Explanation
- {1}
- The name of a subproject
User response
TPFC6564E
Query failed because the filter {1} does not exist.
Explanation
User response
TPFC6565I
The import was completed successfully.
Explanation
User response
TPFC6566E
Import failed. The specified file {1} does not exist.
Explanation
User response
TPFC6567E
Import failed. The specified file {1} is not a valid .xml file. Verify that this file contains proper target environment definitions, and that it is a Local file.
Explanation
User response
TPFC6568E
Import failed. The specified target environment {1} does not exist in the file {2}. Verify that the correct target environment was specified for this file.
Explanation
- {1}
- The specified target environment
- {2}
- File name
User response
TPFC6569E
Import failed. Specify either a target environment, or the -all option.
Explanation
User response
TPFC6570E
Import failed. Do not specify both the -all and the -targetEnv options.
Explanation
User response
TPFC6571E
Import failed. The file {1} does not contain any target environment definitions.
Explanation
User response
TPFC6572E
Import failed due to conflicting target environment names.
Explanation
User response
TPFC6573W
Import completed. Some option sets are conflicting, and were not imported.
Explanation
User response
TPFC6574I
The outcomes of each individual target environment import is listed below.
Explanation
User response
TPFC6575E
Export failed. Ensure that the file name is valid, and that it ends with a XML extension.
Explanation
User response
TPFC6576E
Export failed. Specify either the -a flag to export all blocks of this type, or the -n flag to export a specific building block.
Explanation
User response
TPFC6577E
Export failed. The specified building block {1} could not be found.
Explanation
- {1}
- The specified building block
User response
TPFC6578E
The export was completed successfully.
Explanation
User response
TPFC6579I
The Action file was imported successfully.
Explanation
User response
TPFC6580W
Import successful. Warning: An absolute path was used to reference the action file. It is not recommended that you use an absolute path to reference a shared file. If you intended to use an environement variable in this path, use the appropriate escape characters to prevent the variable from being prematurely resolved.
Explanation
User response
TPFC6581E
Import failed, invalid Options specified.
Explanation
User response
TPFC6582E
Import failed. This Action file is already known to Menu Manager. Specify the -promote option to promote the existing file to the Enterprise level.
Explanation
User response
TPFC6583E
Import failed. The file is not a valid Action file.
Explanation
User response
TPFC6584E
Import failed. The file {1} already exists at the Enterprise Level.
Explanation
User response
TPFC6585I
Import succeeded. The file {1} was successfully imported.
Explanation
User response
TPFC6586I
Import succeeded. The file {1} was successfully imported.
Explanation
User response
TPFC6587I
The Action file was promoted to Enterprise level.
Explanation
User response
TPFC6588E
The target environment name was not specified.
Specify the name of an existing target environment.
Explanation
User response
TPFC6589E
The target environment {1} does not exist.
Specify the name of an existing target environment.
Explanation
- {1}
- The specified target environment
User response
TPFC6590E
The type {1} is not a valid option set type.
Specify a valid option set type (BuildAndLink, BuildMechanism, EditorOptions, LoadOptions, MenuOptions, TargetEnvVars, TPFMakeConfig).
Explanation
- {1}
- A specified option set type
User response
TPFC6591E
The option set type was not specified.
Specify an option set type. (e.g. BuildAndLink)
Explanation
User response
TPFC6592E
An unknown error occurred while processing the QueryTargetEnv command.
Explanation
User response
TPFC6593I
The command completed successfully.
Explanation
User response
TPFC6594I
The command completed successfully. No results were found.
Explanation
User response
TPFC6595E
The connection could not be created. A user ID must also be specified if you specify the password.
Explanation
User response
TPFC6596I
The query variable succeeded without user ID.
Explanation
User response
TPFC6597I
Import completed. However, conflicting target environments or building blocks were not imported.
Explanation
User response
TPFC6598I
Import completed. Any conflicting target environments and Option Sets have been overwritten.
Explanation
User response
TPFC6599E
The rule group {1} does not exist.
Specify the name of an existing rule group.
Explanation
- {1}
- The name of a rule group
User response
TPFC6600I
The import was completed successfully.
Explanation
User response
TPFC6601I
Import completed, but some templates were not imported due to conflicts. These are listed below.
Explanation
User response
TPFC6602I
The specified file {1} was not found.
Explanation
User response
TPFC6603I
The specified file {1} is invalid. Please specify a file with a .xml extension.
Explanation
User response
TPFC6604I
The specified target environments(s) were deleted successfully.
Explanation
User response
TPFC6605I
The specified target environments(s) along with their referenced option sets were deleted successfully.
Explanation
User response
TPFC6606E
Invalid parameters. Please specify either a target environment to delete, or the -alltargetEnv option.
Explanation
User response
TPFC6607E
The specified target environment {1} was not found.
Explanation
- {1}
- The specified target environment
User response
TPFC6608E
Specify either a target environment to delete, or the -allTargetEnv option, but not both.
Explanation
User response
TPFC6609I
Some referenced option sets could not be deleted, because they are referenced by other target environments. These option sets are listed below.
Explanation
User response
TPFC6610E
The specified option sets were deleted successfully.
Explanation
User response
TPFC6611E
The specified option set {1} does not exist.
Explanation
- {1}
- The name of an option set
User response
TPFC6612E
Specify either an option set name, or the -allOptionSet option.
Explanation
User response
TPFC6613I
All specified option sets have been deleted. target environments that are now invalid are listed below.
Explanation
User response
TPFC6614I
Option sets that were referenced by other target environments were not deleted, and are listed below.
Explanation
User response
TPFC7000E
Unable to create connection path for TPFFile {0}.
Explanation
User response
TPFC7001E
Unable to create connection path for TPFFolder {0}.
Explanation
User response
TPFC7002E
Unable to refresh IResource object {0} before performing eclipse actions.
Explanation
- {0}
- The name of an IResource object
User response
TPFC7003E
A user ID conflict will prevent the files from {0} from showing with user ID {1} in filter {2}.
Explanation
- {0}
- The name of a remote system
- {1}
- A user identifier
- {2}
- Filter name
User response
TPFC7004I
A conflict between filter string {0} and filter string {1} was found and resolved while loading filter {2}
Details: {3}
Explanation
- {0}
- A specified filter string
- {1}
- A specified filter string
- {2}
- The name of a filter
- {3}
- The returned message
User response
TPFC7005I
Ensure the environment variable is set, and the location can be accessed. Restart once problems have been resolved.
If the variable is set to an NFS or SMB mounted location, ensure the connection has been established.
Explanation
User response
TPFC8000E
Parent filter must be specified.
Explanation
User response
TPFC8010E
Select a remote file or folder. If browsing for an NFS/SMB connected system, browse under LOCAL for the mounted drive letter.
Explanation
User response
TPFC8011I
Select a remote file. If browsing for an NFS/SMB connected system, browse under LOCAL for the mounted drive letter.
Explanation
User response
TPFC8012I
Select a remote folder. If browsing for an NFS/SMB connected system, browse under LOCAL for the mounted drive letter.
Explanation
User response
TPFC8015E
Only select one folder.
Explanation
User response
TPFC8016E
Only select folders.
Explanation
User response
TPFC8017E
Only select files.
Explanation
User response
TPFC8018E
Path already exists.
Explanation
User response
TPFC8020I
Select a file.
Explanation
User response
TPFC8021I
Select a folder.
Explanation
User response
TPFC8024E
Select a filter that is not the source filter.
Explanation
User response
TPFC8025E
The selected subproject is the source subproject. Select a different subproject as the destination.
Explanation
User response
TPFC8026E
Select a destination subproject.
Explanation
User response
TPFC8027E
No target subproject selected.
Select an existing subproject to merge the imported subproject into.
Explanation
User response
TPFC8028E
No file selected.
Select a file.
Explanation
User response
TPFC8029E
No folder selected.
Select a folder.
Explanation
User response
TPFC8030E
No z/OS UNIX Subproject selected.
Select a z/OS UNIX Subproject.
Explanation
User response
TPFC8031E
No z/OS UNIX Filter selected.
Select a z/OS UNIX Filter.
Explanation
User response
TPFC8032E
The file {1} does not reside in TPFPROJ ({2}).
Choose a file from the TPFPROJ directory.
Explanation
- {1}
- File name
- {2}
- The path name of the TPFPROJ
User response
TPFC8501E
The selected resource is not a valid trace file.
Explanation
User response
TPFC8502E
The file {1} could not be read.
Check that a connection to access the file exists and is connected.
Explanation
User response
TPFC8601E
The port number specified is out of bound.
Explanation
User response
TPFC8602I
The TPFtool server is started on port {0}.
Explanation
User response
TPFC8603I
The TPFtool server has stopped listening on port {0}.
Explanation
User response
TPFC8604E
The TPFtool server cannot be started on port(s) {0}. Change the port list and restart the server.
Explanation
- {0}
- A port number or port numbers
User response
TPFC8605I
You have entered a new Available Ports list for the TPFtool server. Would you like to restart the TPFtool server now to reflect the change?
Explanation
User response
TPFC9050E
Internal error. Could not resolve the resource.
Explanation
User response
TPFC9051E
Internal error. Could not initialize the z/OS UNIX Navigator.
Explanation
User response
TPFC9052E
Internal error. z/OS UNIX Navigator action failed.
Explanation
User response
TPFC9053E
Internal error. Could not initialize the z/OS UNIX Toolkit Perspective.
Explanation
User response
TPFC9200E
No files selected.
Select at least one file to be available while disconnected.
Explanation
User response
TPFC9201E
Unable to download file {1}. The file will not be available in disconnected mode.
The system may have been disconnected or there is not enough space.
Explanation
User response
TPFC9202E
Unable to find a connection to host {1}.
Explanation
- {1}
- The name of a remote system
User response
TPFC9203E
Unable to access folder {1} on host {2}.
Explanation
- {1}
- Folder name
- {2}
- The name of a remote system
User response
TPFC9204E
Local changes made in folder {1} on host {2} can't be uploaded because the remote folder does not have write permission.
The local changes will not be uploaded to the remote system.
Explanation
- {1}
- Folder name
- {2}
- The name of a remote system
User response
TPFC9205W
An internal error occurred while detecting changes on host(s): {1}.
Only new and changed files will be uploaded, deletions are lost.
Explanation
- {1}
- The name or names of one or more remote systems
User response
TPFC9206E
No hosts selected to enter disconnected mode.
Check at least one host that you want to use disconnected mode on.
Explanation
User response
TPFC9207E
No hosts are in disconnected mode.
In order to upload changes, one or more systems must already be in disconnected mode.
Explanation
User response
TPFC9208E
The remote version of the file {1} was changed while in disconnected mode.
Both the local replica and the remote version of the file {1} have different changes.
Explanation
User response
TPFC9506E
{1} cannot be blank.
Explanation
- {1}
- The name of a component
User response
TPFC9507E
{1} already exists.
Explanation
- {1}
- The name of a component
User response
TPFC9508E
{1} cannot contain ; or |.
Explanation
- {1}
- The name of a component
User response
TPFC9510E
Invalid IP Address
Specify in the format a.b.c.d, where a,b,c,and d must be integers between 0 and 255.
Explanation
User response
TPFC9599E
Error saving file {1}
Explanation
User response
TPFC9600E
Specify the IP address.
Specify "?" if the IP address is not known.
Explanation
User response
TPFC9601E
Select at least one build option set
Explanation
User response
TPFC9602E
Select a build mechanism
Explanation
User response
TPFC9603E
Select an editor option set
Explanation
User response
TPFC9604E
Select at least one load option set
Explanation
User response
TPFC9605E
Select at least one make option set
Explanation
User response
TPFC9606E
Select a menu option set
Explanation
User response
TPFC9607E
Select a user exit set
Explanation
User response
TPFC9608E
Select a user variable set
Explanation
User response
TPFC9609E
Select a make option set
Explanation
User response
TPFC9610E
This name is already in use. Specify a unique name.
Explanation
User response
TPFC9611E
Specify a valid name
Explanation
User response
TPFC9612E
Select at least one link option set
Explanation
User response
TPFC9620E
Select at least one target environment.
Explanation
User response
TPFC9621E
Set a current target environment.
Explanation
User response
TPFC9630E
Specify the base comment for Autocomment.
Explanation
User response
Messages for TPF Toolkit Connection Manager
These are the messages that pertain to TPF Toolkit Connection
Manager.
TPFR1000E
The device '{1}' does not exist on the local file system.
Explanation
- {1}
- The name of the device
User response
TPFR1001E
The path '{1}' is invalid.
Explanation
- {1}
- An absolute path name
User response
TPFR1002E
Empty input could not be used to locate any files.
Explanation
User response
TPFR1003E
The file name '{1}' is invalid.
Explanation
User response
TPFR1004E
No host information found for UNC path '{1}'.
Explanation
- {1}
- An absolute Universal Naming Convention path name
User response
TPFR1005E
No path information found for UNC path '{1}'.
Explanation
- {1}
- An absolute Universal Naming Convention path name
User response
TPFR1006E
The location '{1}' does not represent a file.
Explanation
User response
TPFR1007E
Could not find an NFS, SMB or RSE connection for host '{1}'.
Explanation
- {1}
- The name of a remote system
User response
TPFR1008E
Invalid UNC syntax: '{1}'.
Explanation
- {1}
- A specified value that does not use valid Universal Naming Convention
syntax
User response
TPFR1009E
Empty input could not be used to locate any folders.
Type a folder name.
Explanation
User response
TPFR1010E
Empty input could not be used to locate any files or folders.
Explanation
User response
TPFR1011E
File name cannot be empty.
Explanation
User response
TPFR1012E
No file name specified for path '{1}'.
Explanation
- {1}
- An absolute path name
User response
TPFR1013E
Could not find '{1}' on host '{2}'. Connected locations on host '{2}' are {3}.
Explanation
- {1}
- The name of a file or folder
- {2}
- The name of a remote system
- {3}
- One or more currently connected locations
User response
TPFR1014E
There are no NFS or SMB connections for host '{1}'.
Explanation
- {1}
- The name of a remote system
User response
TPFR2000W
No connections to host '{1}' could be found.
Explanation
- {1}
- The name of a remote system
User response
TPFR2001W
The local file system does not have a device named '{1}'.
Explanation
User response
TPFR2002W
No NFS or SMB connections could be found to access '{1}' on host '{2}'.
Explanation
- {1}
- The name of a device
- {2}
- The name of a remote system
User response
TPFR2003W
The folder '{1}' does not exist on host '{2}'.
Explanation
- {1}
- The name of a folder
- {2}
- The name of a remote system
User response
TPFR2004W
The host '{1}' is already in disconnected mode.
Only previously downloaded content will be available.
Explanation
- {1}
- The name of a remote system
User response
TPFR2010E
No connections to host '{1}' could be found.
Create a new z/OS or Linux on System z connection in RSE to access host '{1}', or create an NFS or SMB connection.
Explanation
- {1}
- The name of a remote system
User response
TPFR2011E
No connections to host '{1}' with user ID '{2}' could be found.
Create a new z/OS or Linux on System z connection in RSE to access host '{1}', or create an NFS or SMB connection.
Explanation
- {1}
- The name of a remote system
- {2}
- A user identifier
User response
TPFR2012E
Unable to connect to host '{1}'.
RSE was unable to establish a connection to host '{1}'. Try again.
Explanation
- {1}
- The name of a remote system
User response
TPFR2013E
Unable to locate a host connection to access '{1}'.
Ensure there is an RSE, NFS or SMB connection that allows access to the location.
Explanation
- {1}
- The name of a remote system
User response
TPFR2014E
'{1}' does not exist on host '{2}'.
Make sure the file or folder exists.
Explanation
- {1}
- The name of a file or folder
- {2}
- The name of a remote system
User response
TPFR2015E
'{1}' is currently available in disconnected mode only.
To perform remote operations on the file or folder, you must enter connected mode for host '{2}'.
Explanation
- {1}
- The name of a file or folder
- {2}
- The name of a remote system
User response
TPFR2016E
The host '{1}' is in disconnected mode and '{2}' does not exist in local replicas.
If the file or folder does exist on the remote system, enter connected mode to locate the file or folder.
Explanation
- {1}
- The name of a remote system
- {2}
- The name of a file or folder
User response
TPFR2017W
There are no matches for file pattern '{1}' in folder '{2}'.
Explanation
- {1}
- The specified file-name pattern
- {2}
- The name of a folder
User response
TPFR2100I
Export succeeded. Results written to file: '{1}'.
Explanation
User response
TPFR3000E
The file '{1}' cannot be accessed.
Ensure there is a connection available to access the file.
Explanation
User response
TPFR3001E
Action unavailable - Remote Error List contains no errors.
Run actions that produce error messages to populate the Remote Error List and retry.
Explanation
User response
TPFR3002E
No fields included.
Select one or more fields to be written to the output file.
Explanation
User response
TPFR3003E
Unknown error occured while writing to file '{1}'.
Ensure the file can be accessed.
Explanation
User response
TPFR3004I
Successfully wrote {1} messages to file '{2}'
Explanation
- {1}
- The number of messages written to the file
- {2}
- The name of a file
User response
TPFR3005E
Action unavailable - Ignored Error List contains no errors.
Run actions that produce error messages to populate the Ignored Error List and retry.
Explanation
User response
TPFR6001E
The login was incorrect.
Check that the user ID and password are set correctly.
Explanation
User response
TPFR6002W
The messages exceed the buffer size.
Some of the messages may not appear.
Explanation
User response
TPFR6003W
Host name {1} was found associated with more than one system type and the first one will be picked up.
Open the preferences page and update the saved passwords information.
Explanation
- {1}
- The name of a remote system
User response
TPFR6011I
The command {2} is running on remote system {1}
Explanation
User response
TPFR6012I
The following is the output of the command:
{1}
Explanation
- {1}
- The output of the command
User response
TPFR6013I
The following is the output of the user exit:
{1}
Explanation
- {1}
- The output of the user exit
User response
TPFR6041E
The action cannot be performed against the selected object.
Please check that the right object is selected.
Explanation
User response
TPFR6042E
Cannot find the project directory.
Ensure that the environment variable BBSPROJ is set up correctly.
Explanation
User response
TPFR6043E
The action command is not a valid one.
Explanation
User response
TPFR6044E
Cannot find an existing connection to the remote host.
Explanation
User response
TPFR6045E
Failed in removing the command script file.
Explanation
User response
TPFR6046E
Cannot open the file to read.
Explanation
User response
TPFR6047E
Invalid connection type.
Explanation
User response
TPFR6048E
Host name is missing.
Explanation
User response
TPFR6049E
Cannot find the file bbsjcl.cfg in the project directory.
Explanation
User response
TPFR6050E
Failed processing the BBSOUT card in the configuration file.
Explanation
User response
TPFR6051E
Failed adding error message to the task list.
Explanation
User response
TPFR6052E
Cannot find the JCL template file for loadset generation in the project directory.
Explanation
User response
TPFR6053W
DSN TLDROUT and OUTPUT are found in the JCL template file. OUTPUT is used.
Explanation
User response
TPFR6054E
Cannot find the target system for the selected resource.
Explanation
User response
TPFR6055W
The action configuration set on the Multi System Script action page is ignored.
Explanation
User response
TPFR6062E
Login failed. Password not specified.
Explanation
User response
TPFR6063E
Login failed. User ID not specified.
Explanation
User response
TPFR6141E
File {1} could not be found.
Explanation
User response
TPFR6142E
Failed processing command header {1}.
Explanation
- {1}
- The header of the command
User response
TPFR6143E
The length of command exceeds the command length limit {1}.
Explanation
- {1}
- The limit of command length
User response
TPFR6144E
Failed processing the file {1}.
Explanation
User response
TPFR6145E
Failed running the user exit {1}.
Explanation
- {1}
- The name of a local log file
User response
TPFR6146E
The active connection to the host {1} cannot be found.
Explanation
- {1}
- The name of a remote system
User response
TPFR6147W
Failed to find the offset in the file {1}.
Explanation
User response
TPFR6148E
Cannot find the file {1}.
Explanation
User response
TPFR6149E
Found the wrong file {1}.
Explanation
User response
TPFR6150E
Failed moving the file to {1}.
Explanation
User response
TPFR6151E
Failed deleting the file {1}.
Explanation
User response
TPFR6152E
Failed connecting to {1}.
Explanation
- {1}
- The name of a remote system
User response
TPFR6153E
Failed finding root on {1}.
Explanation
- {1}
- The name of a remote system
User response
TPFR6154E
Cannot find the configuration for the system {1} in the configuration file.
Explanation
- {1}
- The name of a remote system
User response
TPFR6155I
The file filter {1} cannot be resolved.
Explanation
- {1}
- The name of a file filter
User response
TPFR6156E
Failed processing the file {1}.
Explanation
User response
TPFR6157E
The object '{1}' matched the filter '{2}' but could not be used as a file.
Explanation
- {1}
- The name of an object
- {2}
- The name of a file filter
User response
TPFR6158E
The working directory TEMPDIR can't be found for the user '{1}'
Explanation
User response
TPFR6159I
Filter matched {1} of {2} messages
Explanation
- {1}
- The number of messages matched
- {2}
- The total number of messages
User response
TPFR6200E
Error Creating File: File Exists.
Explanation
User response
TPFR6201E
Error Creating File: No Write Permission.
Explanation
User response
TPFR6202E
Unknown error creating file. File not created.
Explanation
User response
TPFR6203E
Error Creating Folder: Folder Exists.
Explanation
User response
TPFR6204E
Error Creating Folder '{1}' in '{2}': No write Permission.
Explanation
- {1}
- The name of a folder to be created
- {2}
- The name of a folder
User response
TPFR6205E
Unknown error creating folder. Folder not created.
Explanation
User response
TPFR6206E
Failed transferring the file.
Explanation
User response
TPFR6207E
Failed processing the JCL file.
Explanation
User response
TPFR6208E
Failed opening the JCL file.
Explanation
User response
TPFR6209E
The host name is unknown.
Explanation
User response
TPFR6210E
Cannot read from the file bbsjcl.cfg in the project directory.
Explanation
User response
TPFR6211E
Unknown error while creating file '{1}'.
Explanation
User response
TPFR6212E
Unknown error while creating folder '{1}'.
Explanation
User response
TPFR6213E
Failed to locate '{1}' because a connection can not be established during a user exit.
Create a connection to '{2}' and try again.
Explanation
- {1}
- The name of a file or folder
- {2}
- The name of a remote system
User response
TPFR8020E
No folder selected.
Select a folder or a system filter with a filter string for the desired location.
Explanation
User response
TPFR8021E
No file specified.
Select a file or select a parent folder and type in the name of a new file.
Explanation
User response
TPFR8022E
File does not exist.
Select a file.
Explanation
User response
TPFR8023E
No file or folder selected.
Select a file or folder.
Explanation
User response
TPFR8024E
File name cannot be empty.
Type in a name for the new file.
Explanation
User response
TPFR8027E
Folder name cannot be empty.
Type in a name for the new folder.
Explanation
User response
TPFR8028E
Files are not a valid selection.
Select the parent folder of the file.
Explanation
User response
TPFR8029E
The file name filter cannot be empty.
Specify a file filter (For example, *.*).
Explanation
User response
TPFR8030E
The file '{1}' already exists in the folder '{2}'.
Enter a new unique name for the file.
Explanation
- {1}
- The name of a folder
- {2}
- The name of the containing folder
User response
TPFR8031E
The folder '{1}' already exists in the folder '{2}'.
Enter a new unique name for the folder.
Explanation
- {1}
- The name of a folder
- {2}
- The name of the containing folder
User response
TPFR8032E
The folder '{1}' does not have the necessary permissions to create the file '{2}'.
Select a parent folder that you have write permission on.
Explanation
- {1}
- The name of a folder
- {2}
- The name of a file
User response
TPFR8033E
The folder '{1}' does not have the necessary permissions to create the folder '{2}'.
Select a parent folder that you have write permission on.
Explanation
- {1}
- The name of a folder
- {2}
- The name of a folder
User response
TPFR8034E
File name cannot be empty.
Enter a file name.
Explanation
User response
TPFR8035E
Folder name cannot be empty.
Enter a folder name.
Explanation
User response
TPFR8036E
The name '{1}' contains invalid file name characters.
Remove all invalid characters from the file name.
Explanation
User response
TPFR8037E
The name '{1}' contains invalid folder name characters.
Remove all invalid characters from the folder name.
Explanation
User response
TPFR8038E
The name '{1}' does not identify a file in the folder '{2}'.
Specify a file in the folder '{2}'.
Explanation
- {1}
- The name of a file
- {2}
- The name of a folder
User response
TPFR8039E
The file '{1}' does not exist in the folder '{2}'.
Specify an existing file name.
Explanation
- {1}
- The name of a file
- {2}
- The name of a folder
User response
TPFR8040E
The connection type '{1}' is invalid.
Specify a location on '{2}'.
Explanation
- {1}
- A connection type
- {2}
- The name of a remote system
User response
TPFR8041E
The host name '{1}' is invalid.
Specify a location on host '{2}'.
Explanation
- {1}
- The name of a remote system
- {2}
- The name of a remote system
User response
TPFR8042E
The path '{1}' does not exist.
Specify an existing path.
Explanation
- {1}
- An absolute path name
User response
TPFR8043E
The file is not remote.
Select a remote file. {1}
Explanation
User response
TPFR8044E
The folder is not remote.
Select a remote folder. {1}
Explanation
User response
TPFR8045E
Multiple paths entered.
Enter a single location.
Explanation
User response
TPFR8046E
The file extension '{1}' is invalid.
The file extension must be '{2}'.
Explanation
- {1}
- The specified file-name extension
- {2}
- A file-name extension
User response
TPFR8047E
The file name '{1}' is invalid.
The file name must have the format {2}.
Explanation
- {1}
- A file name
- {2}
- A file-name format
User response
TPFR8048E
The file '{1}' could not be created in the folder '{2}'.
Ensure the folder '{2}' exists and there is not already a file with the name '{1}' in '{2}'.
Explanation
- {1}
- The name of a file
- {2}
- The name of a folder
User response
TPFR8049E
The folder '{1}' could not be created in the folder '{2}'.
Ensure the folder '{2}' exists and there is not already a folder with the name '{1}' in '{2}'.
Explanation
- {1}
- The name of a folder
- {2}
- The name of a folder
User response
TPFR8050E
The file is not local.
Select a local file.
Explanation
User response
TPFR8051E
The folder is not local.
Select a local folder.
Explanation
User response
TPFR8052E
The filter '{1}' is ambiguous as a folder selection because it contains filter strings for multiple folders ({2}, {3} ...).
Select a folder, or a filter that references files from a single folder only.
Explanation
- {1}
- The name of a filter
- {2}
- The name of a folder
- {3}
- The name of a folder
User response
TPFR8053E
The selection contains a non-file.
Select one or more files and clear any folder selections.
Explanation
User response
TPFR8054E
{1} contains duplicate name '{2}'.
Make sure the {1} field contains a list of unique names.
Explanation
- {1}
- The name of a field
- {2}
- The specified name
User response
TPFR8055E
Multiple parents selected for new folder(s).
Select one parent folder and type one or more new folder names.
Explanation
User response
TPFR8056E
Multiple parents selected for new file(s).
Select one parent folder and type one or more new file names.
Explanation
User response
TPFR8057E
The file '{1}' is selected twice.
Remove one occurrence of '{1}' from the selection.
Explanation
User response
TPFR8058E
The folder '{1}' is selected twice.
Remove one occurrence of '{1}' from the selection.
Explanation
User response
TPFR8059E
The folder '{1}' does not have read access.
Select a folder that has read access permission.
Explanation
User response
TPFR8060E
The folder '{1}' does not have write access.
Select a folder that has write access permission.
Explanation
User response
TPFR8061E
The file '{1}' does not have read access.
Select a file that has read access permission.
Explanation
User response
TPFR8062E
The file '{1}' does not have write access.
Select a file that has write access permission.
Explanation
User response
TPFVAL1000E
Sample validation error message
Explanation
User response