IBM Rational Developer for z Systems Messages and Codes Guide

IBM Rational Developer for z Systems Version 9.5.1

Messages and Codes Guide


SC14-7497-08


Note

Contents

Note

Before using this information, be sure to read the general information under Notices for IBM Rational Developer for z Systems documentation

Ninth edition (December 2015)

This edition applies to IBM® Rational® Developer for z Systems™ Version 9.5 (program number 5724-T07) and to all subsequent releases and modifications until otherwise indicated in new editions.

Order publications by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30 a.m. and 7:00 p.m. eastern standard time (EST). The phone number is (800) 879-2755. The fax number is (800) 445-9269. Faxes should be sent Attn: Publications, 3rd floor.

You can also order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below.

IBM welcomes your comments. You can send your comments by mail to the following address:

IBM Corporation
Attn: Information Development Department 53NA
Building 501 P.O. Box 12195
Research Triangle Park NC 27709-2195.
USA

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

About this book

This guide provides information about the messages in Rational Developer for z Systems. This document contains information about client messages and host messages.

Who should read this book

This book is intended for all users of Rational Developer for z Systems who want information about messages that the product displays.

Client messages

The topics in this portion of the documentation contain information about the client messages in Rational Developer for z Systems.

Most client message IDs in Developer for z Systems have the format CRRZcnnnnL, where:
CRRZ
The message prefix for Rational Developer for z Systems
c
The component identifier
nnnn
A four-digit message number that is unique in that component
L
The message level: S for severe error, E for error, W for warning, or I for informational

This message documentation is also included in IBM Knowledge Center.

Messages for Integrated Debugger

These are the messages that pertain to Integrated Debugger.

AQEDB0000E
An invalid module name was given for a load occurrence breakpoint.

Explanation

User response

AQEDB0001E
A TCP/IP link to z/OS was broken by a z/OS session.

Explanation

User response

AQEDB0002E
The z/OS probe connected to port {1} is at protocol version {2}. This is incompatible with the engine protocol version {3}.

The link to the probe will be terminated and the application allowed to run.

Explanation

{1}
Port number
{2}
Protocol version
{3}
Protocol version

User response

AQEDB0003E
The z/OS probe was unable to locate the listing file dated {2} for COBOL compilation unit {1}.

Explanation

{1}
The name of a compilation unit
{2}
A date and time

User response

AQEDB0004E
The z/OS probe located the listing file dated {2} for COBOL compilation unit {1}, but it does not contain all the information required for debugging. The compiler options SOURCE, LIST, XREF, and MAP will create the required debugging information.

Explanation

{1}
The name of a compilation unit
{2}
A date and time

User response

AQEDB0005I
You cannot step a thread after hitting a load breakpoint; you can only resume. If required, breakpoints should be set before resuming.

Explanation

User response

If breakpoints are required, set them before you resume.
AQEDB0006I
You cannot step the child process; you may only resume. If required, breakpoints should be set before resuming.

Explanation

User response

If breakpoints are required, set them before you resume.
AQEDB0007I
From this location, you must set any breakpoints you need and then resume.

Explanation

User response

Set any breakpoints that you need, and then resume.
AQEDB0008E
The z/OS probe was unable to locate the SYSADATA file dated {2} for HLASM compilation unit {1}.

Explanation

{1}
The name of a compilation unit
{2}
A date and time

User response

AQEDB0009I
Compilation unit {1} will be treated as nondebuggable.

Explanation

{1}
The name of a compilation unit
This message is for informational purposes only.

User response

No action is required.
AQEDB0010E
The z/OS probe was unable to locate the DWARF side file dated {2} for compilation unit {1}.

Explanation

{0}
Name of compilation unit
{1}
Date

User response

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 z Systems.

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.

Explanation

{0}
File name
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
CRRDG2221E
Address Error
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:
CRRDG2226E
Edit failed
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?

Explanation

{0}
Port number
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.

Explanation

{0}
Line number
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.
CRRDG3173E
Internal error
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.

Explanation

{0}
Field name
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 BMS Screen Designer (BMS Map Editor)

The following messages pertain to the BMS Screen Designer (BMS Map Editor) in Rational Developer for z Systems.

CRRZB0136E
Errors occurred.

Explanation

This message is typically displayed when some type of validation is in progress, and further explanation is provided.

User response

Follow the instructions or look up the message that is provided in the message window as further explanation.
CRRZB0137E
The field name is a duplicate.

Explanation

The field name is the same as another field name in the map.

User response

Change the field name to a unique field name.
CRRZB0138E
The length of the field name exceeds 30 characters.

Explanation

The length of a field name cannot exceed 30 characters.

User response

Specify a field name whose length is 30 or fewer characters.
CRRZB0139E
The field name contains an invalid @ character.

Explanation

A field name cannot contain the @ character.

User response

Specify a field name that does not contain the @ character.
CRRZB0140E
The field name contains one or more spaces.

Explanation

A field name cannot contain spaces.

User response

Specify a field name that does not contain spaces.
CRRZB0141E
The field name does not start with an alphabetic character.

Explanation

The field name must start with an alphabetic character.

User response

Choose a field name that starts with an alphabetic character.
CRRZB0142E
The length of the initial value exceeds the field length.

Explanation

The length of the initial value cannot exceed the field length.

User response

Specify an initial value whose length does not exceed the field length.
CRRZB0143E
The row is empty.

Explanation

A row cannot be empty.

User response

Specify content for the row.
CRRZB0144E
The column is empty.

Explanation

A column cannot be empty.

User response

Specify content for the column.
CRRZB0145E
The row value is not valid.

Explanation

The value that is used for the row is not allowed.

User response

Change the value to an allowed entry.
CRRZB0146E
The column value is not valid.

Explanation

The value that is used for the column is not allowed.

User response

Change the value to an allowed entry.
CRRZB0147E
Row or column values are not valid.

Explanation

The value that is used for the row or column is not allowed.

User response

Change the value to an allowed entry.
CRRZB0148E
The field position or length is not valid.

Explanation

The value that is used for the field position or length is not allowed.

User response

Change the value to an allowed entry.
CRRZB0149E
The group name exceeds 30 characters.

Explanation

A group name cannot exceed 30 characters.

User response

Specify a group name whose length is 30 or fewer characters.
CRRZB0150E
An OCCURS value is specified when a group name is specified.

Explanation

You cannot specify an OCCURS value if a group name is specified.

User response

Specify either an OCCURS value or a group name.
CRRZB0151E
The field name contains an invalid character not supported by the Mapset language.

Explanation

The characters in field names must conform to the character set that is supported by the programming language of the application that uses the map.

User response

Refer to the appropriate Language Reference manual for information about supported characters.
CRRZB0153E
The name contains one or more spaces.

Explanation

A name cannot contain spaces.

User response

Specify a name that does not contain spaces.
CRRZB0154E
The map name is a duplicate.

Explanation

The map name must be unique.

User response

Specify a unique map name.
CRRZB0155E
The length of the map name exceeds 30 characters.

Explanation

The length of a map name cannot exceed 30 characters.

User response

Specify a map name whose length is 30 or fewer characters.
CRRZB0156E
The map name contains an invalid @ character.

Explanation

A map name cannot contain the @ character.

User response

Specify a map name that does not contain the @ character.
CRRZB0157E
The row is not a numeric value.

Explanation

A row must be a numeric value.

User response

Specify a row that is a numeric value.
CRRZB0158E
The column is not a numeric value.

Explanation

A column must be a numeric value.

User response

Specify a numeric value for the column.
CRRZB0182E
No column is defined.

Explanation

At least one column must be defined.

User response

Define a column.
CRRZB0183E
The total width exceeds the defined table width.

Explanation

The sum of the width of the columns in the table is greater than the table width.

User response

Do one of the following steps:
  • Adjust the columns so that their sum is less than or equal to the table width.
  • Adjust the table width so that it is greater than or equal to the sum of the column width.
CRRZB0192E
No map has been selected.

Explanation

You must select at least one map.

User response

Select one or more maps.
CRRZB0270E
An error occurred when creating a nested text editor.

Explanation

A nested text editor is a text editor that is part of a multi-page editor in Rational Developer for z Systems. For the BMS editor, the Source page is the nested text editor. In this case, there was a problem when the Source page was created.

User response

Try closing the BMS file and opening it again.
CRRZB0271E
The input is not valid; it must be IFileEditorInput.

Explanation

The BMS editor is expecting a different type of input.

User response

Contact IBM Software Support.
CRRZB0272W
This map set will not assemble correctly. A map must be specified for this map set.

Explanation

The map set does not contain any maps.

User response

Using the palette that is associated with the editor, select the map, and then select the design canvas to create a map.
CRRZB0273W
This map set will not assemble correctly. At least one field must be specified for each map.

Explanation

A map in the map set does not contain any fields.

User response

Using the palette that is associated with the editor, select a field, and then select the design canvas to create a field.
CRRZB0296E
The specified map set name is not valid.

Explanation

A map set name that contains one or more invalid characters was specified.

User response

Specify a map set name that contains any of the following characters: letters; digits; the symbols #, $, and @
CRRZB0297E
No name has been specified for the map set.

Explanation

A name must be specified for the map set.

User response

Specify a name for the map set.
CRRZB0299E
The file name does not end in ".{0}".

Explanation

The file name must end in the particular file name extension.

User response

Specify a file name that ends in the required file name extension.
CRRZB0306E
No valid location is selected.

Explanation

A valid location must be selected.

User response

Select a valid location.
CRRZB0360E
No valid field name is entered.

Explanation

You must enter a valid field name.

User response

Enter a valid field name.
CRRZB0361E
No valid input field length is specified.

Explanation

You must specify a valid input field length.

User response

Specify a valid input field length.
CRRZB0362E
No valid label field length is specified.

Explanation

You must specify a valid label field length.

User response

Specify a valid label field length.
CRRZB0363E
The length of the fields is greater than {0}.

Explanation

The length of the fields cannot be greater than the limit that is shown in the message.

User response

Specify a length that is not greater than the limit.
CRRZB0364I
A portion of the caption will be trunctated.

Explanation

The length of the caption exceeds the available space in the caption.

User response

No action is required. To display the entire caption, increase the length of the Caption field, or decrease the length of the caption text.
CRRZB0367I
A portion of the initial value will be truncated.

Explanation

The length of the initial value exceeds the available space.

User response

No action is required. To display the entire initial value, decrease the length of the initial value or increase the size of the field that is associated with the initial value.
CRRZB0377I
A dynamic web project has not been created.

Explanation

You must create a dynamic web project first.

User response

Create a dynamic web project.
CRRZB0381I
The file should be saved. Would you like to save the file now?

User response

Save the file to prevent losing any changes.
CRRZB0396E
No map has been selected.

Explanation

You must select at least one map.

User response

Select one or more maps.
CRRZB0401E
The number of rows exceeds {0} rows.

Explanation

The number of rows cannot exceed the maximum that is shown in the message.

User response

Specify a number of rows that does not exceed the maximum.
CRRZB0402E
The defined number of rows is not an integer.

Explanation

The defined number of rows must be an integer.

User response

Define the number of rows to be an integer.
CRRZB0403E
Column {0} has an invalid field prefix defined.

Explanation

The prefix that is defined for the column that is shown in the message is not valid.

User response

Specify a valid field prefix.
CRRZB0404W
The total width exceeds the defined table width. {0} characters will be truncated.

Explanation

The content of the table is too wide for the table.

User response

Make the table wider or the contents narrower.
CRRZB0441E
An invalid value was specified for an OCCURS clause. Enter a numeric value between 1 and 99.

Explanation

An OCCURS clause entry has an invalid value.

User response

Determine the position of the invalid value and enter a numerical value 1 - 99.
CRRZB0442E
The field length is not numeric and between 1 and 99.

Explanation

The field length must be numeric and 1 - 99.

User response

Specify a numeric field length in the range 1 - 99.
CRRZB0443E
The field distance is not between 1 and 99.

Explanation

The field distance must be 1 - 99.

User response

Specify a field distance in the range 1 - 99.
CRRZB0444E
The dimensions of the structure exceed the available space.

Explanation

The structure is too large.

User response

Make the structure smaller.
CRRZB0448W
The field positions specified will cause overlapping.

Explanation

The values that are entered for the field positions overlap.

User response

Enter values that do not overlap.
CRRZB0449E
The BMS file name is a duplicate.

Explanation

The value that is entered for the BMS file is already in use.

User response

Specify a unique file name.
CRRZB0450I
{0} was added to the MVS subproject {1}.

Explanation

{0}
name of the generated symbolic map
{1}
name of the MVS™ subproject
A symbolic map was generated and added to the specified MVS subproject.

User response

No action is required.
CRRZB0455I
A symbolic map has been created.

Explanation

The symbolic map was created successfully in the destination location you specified.

User response

No action is required.
CRRZB0456I
The symbolic map file has been created.

Explanation

The symbolic map was created successfully in the destination location you specified.

User response

No action is required.
CRRZB0457E
The file name is not valid.

Explanation

The specified file name is not valid.

User response

Specify a valid file name.
CRRZB0458E
A duplicate file name was specified.

Explanation

The specified file name is already used.

User response

Specify a unique file name.
CRRZB0459E
The initial value can only contain numeric characters for a Numeric only field.

Explanation

Input other than numeric characters was provided to a numeric field.

User response

Remove any non-numeric characters in the numeric field.
CRRZB0460E
The first character in the alternate map name entered is invalid.

Explanation

The alternative map name starts with an invalid character.

User response

Remove the invalid character and ensure that the alternative map name begins with a character from the set [a-Z].
CRRZB0461E
The value entered in the alternate map name is invalid.

Explanation

The name that is provided as the alternative map name is not valid.

User response

Provide a valid alternative map name.
CRRZB0462E
The alternate map name contains one or more spaces.

Explanation

The alternative map name cannot contain spaces.

User response

Remove all spaces from the alternative map name.
CRRZB0466I
A file has been added to the MVS subproject.

Explanation

A newly generated BMS file was added to the MVS subproject by the new BMS map set wizard.

User response

No action is required.

Messages for Common Access Repository Manager (CARMA)

These are the messages that pertain to the Common Access Repository Manager (CARMA) in Rational Developer for z Systems.

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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 Rational Developer for z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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.
CRRZC2950E
The compare with action on {0} encountered an error.

Explanation

{0}
0
Unexpected error trying to perform a compare with action. The CARMA member might not exist.

User response

Refresh the parent of the CARMA member in the CARMA view, and try again.
CRRZC2951E
The compare with action on {0} encountered an error.

Explanation

{0}
0
Unexpected error trying to perform a compare with. The CARMA member might not exist.

User response

Refresh the parent of the CARMA member in the CARMA view, and try again.
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

{0}
0
{1}
1

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.
CRRZC7001I
Views have been exported successfully.

Explanation

Information message that states that the CARMA views that were selected for export were successfully exported.
CRRZC7002W
The identifier of this repository does not match the identifier of the repository from which this file was exported. Importing this file can create invalid views. Are you sure that you want to import these views?

Explanation

The views were exported from a CARMA RAM that represented views differently that the RAM into which you are importing the view.

User response

Choose to import the view if you want. Importing the view can cause unexpected errors to occur in the RAM. If problems occur, remove the imported views from the RAM.
CRRZC7003E
Invalid view file selected.

Explanation

The file that was selected for import is not correctly formatted as a CARMA view file.

User response

Try the import again with a file of the correct format.
CRRZC7004I
Views have been imported successfully.

Explanation

Informational message that the CARMA views that were selected for import were successfully imported.
CRRZC7005E
An error occurred while CARMA was trying to save the view-export file.

Explanation

CARMA encountered an error while it was saving the view-export file.

User response

Verify that you have the correct access to the save location on the client. Check the client error log for more information.

Client messages for Enterprise Service Tools

The following client messages pertain to the Enterprise Service Tools (EST) component in Rational Developer for z Systems.

The EST messages are grouped into the following subdivisions:

  • Messages that are displayed by the service flow project tools:
    • CRRZE2000E-CRRZE2004E: Messages that are displayed by the remote system editor
    • Messages that are displayed by the Generate Runtime Code wizard:
      • CRRZE7200E-CRRZE7220E: Errors that can occur when you perform an action on a remote z/OS system
      • CRRZE7000E-CRRZE7343W: Errors that can occur when you generate COBOL source code
        • CRRZE7300E-CRRZE7315W: COBOL source code generation, General errors
        • CRRZE7316E-CRRZE7323E: COBOL source code generation, Internal errors
        • CRRZE7324E-CRRZE7328E: COBOL source code generation, Miscellaneous errors
        • CRRZE7329W-CRRZE7343W: COBOL source code generation, Generation errors
      • CRRZE7400E-CRRZE7401E: Errors that can occur when you generate an invocation of an outbound web service
      • CRRZE7500E-CRRZE7512W: Errors that can occur when you generate a macro for the HATS runtime environment
    • Messages that are displayed by the WebSphere® Message Broker component (BIP*)1
  • CRRZX0047E-CRRZX0132E: Messages that are displayed by the single-service project tools

1WebSphere Message Broker error messages begin with the characters BIP, as in BIP2001E. For information about these messages, see Diagnostic messages in the WebSphere Message Broker Version 6.1 Information Center.

CRRZE2000E
An internal error has occurred. See the error log for more details.

Explanation

The remote system editor encountered an internal error.

User response

See the error log.

CRRZE2004E
The host editor could not establish a connection to the remote z/OS system.

Explanation

The remote system editor displays this error message whenever it cannot connect to the remote z/OS system that is specified in the current remote system connection.

User response

The connection can fail for any network reason. To troubleshoot connection problems:
  1. Verify that the properties of the remote system connection are correct. For more information about remote system connection properties, see Modifying the properties of a host connection.
  2. Determine whether the remote z/OS system is accessible from another program such as a browser. If not, then rerun any programs that you customarily use to prepare your local system for a connection with a remote z/OS system.
  3. Try the connection again. For more information about connecting to a remote system, see Opening a host connection.
CRRZE7200E
JCL file {0} could not be submitted to remote system {1}.

Explanation

{0}
File name
{1}
Remote system name

The Generate Runtime Code wizard was unable to submit the JCL file to the remote z/OS system.

User response

Make sure that you are logged on to the JES connection for the system you are deploying to by using the Remote Systems view. Make sure the data set you are moving your JCL files to is configured to support JCL files.

CRRZE7201E
Pipeline {0} could not be scanned: {1}

Explanation

{0}
Pipeline name
{1}
Error message

This error indicates that the specified pipeline was not successfully rescanned.

User response

If the reason indicates that the selected CICS System/Region was not found, ensure the System/Region is defined by using the connection preferences and that you are connected.

If the reason indicates that a CRD error occurred, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about these errors, see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.

CRRZE7202E
Program resource {0} could not be created on CICS System/Region {1}: {2}

Explanation

{0}
Resource name
{1}
Error message

This error indicates a failure to create a program resource on the selected CICS System/Region. The probable reason is that the CICS Resource Definition (CRD) server encountered a problem while it was creating this resource.

User response

If the reason indicates that it is a CRD error, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about these errors, see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.

CRRZE7204E
Transaction resource {0} could not be created on CICS System/Region {1}: {2}

Explanation

{0}
Resource name
{1}
Error message

This error indicates a failure to create a transaction resource on the selected CICS System/Region. The probable reason is that the CICS Resource Definition (CRD) server encountered a problem while it was creating this resource.

User response

If the reason indicates that it is a CRD error, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about these errors, see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.

CRRZE7206E
Process type resource {0} could not be created on CICS System/Region {1}: {2}

Explanation

{0}
Resource name
{1}
Error message

This error indicates a failure to create a process type resource on the selected CICS System/Region. The probable reason is that the CICS Resource Definition (CRD) server encountered a problem while it was creating this resource.

User response

If the error message that is represented by {1} indicates that the error occurred in the CICS Resource Definition (CRD) server, then follow these steps:
  1. Find the CICS Resource Definition server reason code and the CICS RESP2 code corresponding to the error. These codes begin with the letters CRRZA (new style) or WZAD (old style).
    • Typically the reason code and the CICS RESP2 code are included in the error message section of this message.
    • If not, then examine the CICS MSGUSR log for error details and determine the reason code and the CICS RESP2 code.
  2. See the online help for the CICS Resource Definition server reason code and the CICS RESP2 code for steps to resolve the error:
CRRZE7208E
A Program, Transaction, or ProcessType resource could not be created on CICS System/Region {0} because the CICS System/Region {0} was not found.

Explanation

{0}
Resource name

This message indicates that the connection to the CICS System/Region selected in the Generate Runtime Code wizard was not found.

User response

Ensure that the System/Region is defined by using the connection preferences and that you are connected.

CRRZE7209E
The service flow pickup directory could not be rescanned because the selected CICS System/Region is not CICS Transaction Server for z/OS V3.2 or later.

Explanation

An error occurred in the CMIT transaction for the CICS Service Flow Runtime because the selected CICS System/Region is not CICS Transaction Server for z/OS V3.2 or later.

User response

The CMIT transaction is installed only in CICS Transaction Server for z/OS V3.2 or later. Select the correct CICS System/Region in the Generate Runtime Code wizard.

CRRZE7210E
An error occurred while creating file '{0}' in '{1}'.

Explanation

{0}
File name
{1}
Location

This message is displayed if you skip over replacing a pre-existing file or if the Application Deployment Manager subsystem encountered an error while it was creating the file at the specified location.

User response

Ensure that your remote systems are connected. Ensure that your target directories or data sets are entered correctly and that you have write access to those destinations. Check the Application Deployment Manager log for more details. The location of the Application Deployment Manager log is specified in the Preferences page for the Application Deployment Manager.

CRRZE7211E
The service flow pickup directory could not be rescanned because the Service Flow Runtime flow scan program DFHMAINS failed.

Explanation

An error occurred in the CMIT transaction of the CICS Service Flow Runtime because the SFR flow scan program DFHMAINS ended abnormally.

User response

Examine the CICS MSGUSR log and look for a message that indicates that DFHMAINS ended abnormally. The message contains a specific four-character abend code.

CRRZE7212E
The service flow pickup directory could not be rescanned because a program link failure occurred. RESP={0} and RESP2={1}.

Explanation

{0}
A response code

An error occurred in the CMIT transaction of the CICS Service Flow Runtime because of a program link failure.

User response

See the RESP and RESP2 values for the LINK command in the CICS Application Programming Reference. For more information about the CICS response 2 codes, see also CICS response 2 (RESP2) codes: CRRZA1200E - CRRZA1211E in the online help for the Application Deployment Manager).

CRRZE7213E
The service flow pickup directory could not be rescanned because the CICS System/Region {0} was not found.

Explanation

{0}
Resource name

An error occurred in the CMIT transaction of the CICS Service Flow Runtime because the CICS System/Region selected in the Generate Runtime Code wizard could not be found.

User response

Ensure that the System/Region was defined by using the connection preferences and that the connection is open.

CRRZE7214E
The service flow pickup directory could not be rescanned because the Application Deployment Manager encountered an error. The Application Development Manager reason code is: {0}.

Explanation

{0}
Reason code

This message indicates an internal error.

User response

The reason code that is returned by the Application Development Manager is a CICS Resource Definition server reason code. For more information about the reason code, see CICS Resource definition server reason codes: CRRZA1400E - CRRZA1469E in the online help for the Application Deployment Manager. Contact IBM Software Support to resolve the problem.

CRRZE7218E
The default Application Deployment Manager attributes for RDO programs could not be downloaded.

Explanation

The Generate Runtime Code wizard was not able to retrieve the default values for RDO program resources from the CICS Resource Definition server.

The wizard uses these default values to create the program resources for the flow. These default values are set by the system administrator.

User response

Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about the errors, see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.

CRRZE7219E
The default Application Deployment Manager attributes for RDO transactions could not be downloaded.

Explanation

The Generate Runtime Code wizard was not able to retrieve the default values for RDO transactions from the CICS Resource Definition (CRD) server.

The wizard uses these default values to create transaction resources for the flow and also to add a transaction resource to a manifest file. These default values are set by the system administrator.

User response

Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about the errors, see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.

CRRZE7220E
The default Application Deployment Manager attributes for RDO process types could not be downloaded.

Explanation

The Generate Runtime Code wizard was not able to retrieve the default values for RDO ProcessType resources from the CICS Resource Definition (CRD) server.

The wizard uses these default values to create ProcessType resources for the flow. These default values are set by the system administrator.

User response

Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about the errors, see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.

CRRZE7300E
COBOL generation stopped with an error. An unknown exception occurred. Exception text: {0}

Explanation

{0}
Error message

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7301E
COBOL generation stopped with an error. The {0} named {1} contains an invalid value for generation property {2}. Method: {3}

Explanation

{0}
Node type
{1}
Node name
{2}
Property name
{3}
Method name

The generation property that is specified by the error message contains an invalid value.

The node type element in the error message can be either of the following node types:
  • Invoke: The node is an Invoke nonterminal node, an Invoke screen operation node, or an Invoke outbound web service node.
  • Subflow: The node is an Invoke flow node.

User response

To resolve this problem:
  1. Specify a valid value for the generation property in the generation properties file for the flow.
  2. If the problem persists, resolve any errors or warning messages that are shown in the Problems view.
CRRZE7302E
COBOL generation stopped with an error. There are too many Receive nodes. A flow can contain only one Receive node. Remove the extra Receive nodes and run the Generate Runtime Code wizard again.

Explanation

The flow that you are attempting to generate contains more than one Receive node. Only one Receive node is allowed on a flow.

User response

Modify your flow so that it contains only one Receive node.

CRRZE7303E
An ESQL expression is missing or invalid for {0} node {1}.

Explanation

{0}
Node type
{1}
Node name

This message is displayed when an ESQL expression associated with a Switch or While node is missing or has invalid contents.

User response

Correct the problems with the referenced ESQL resource and run the Generate Runtime Code wizard again.

CRRZE7304E
COBOL generation stopped with an error. {0} were not found in the {1} named {2}. Method: {3}

Explanation

{0}
Resources
{1}
Containing resource
{2}
Resource name
{3}
Method name

The Generate Runtime Code wizard did not find the specified resources in the specified containing resource as expected.

User response

  1. Provide the missing value and run the Generate Runtime Code wizard again.
  2. If the problem persists, resolve any errors or warning messages that are shown in the Problems view.
CRRZE7305E
Invalid syntax was found for {0} in an expression in resource {1}. Method: {2}

Explanation

{0}
Language
{1}
Resource name
{2}
Method name
One of the ESQL expressions in your service flow contains a syntax error.
Note: The language element in the error message is always "ESQL".

User response

Open the referenced resource and correct the ESQL expression. The expression that prevented successful generation is also listed as an error in the Problems view.

CRRZE7307E
COBOL generation stopped with an error. A field that does not have a BMS name cannot be used in a screen descriptor for screen description {0}. Change the screen descriptors associated with this screen description to use only fields with BMS names.

Explanation

{0}
Screen description name

When you generate a terminal service flow of flow type Link3270 Bridge, only fields that are named in the imported BMS maps can be referenced in the user-created screen descriptors.

User response

A descriptor in the screen description uses a default field name instead of a BMS field name. For more information about field names and descriptors, see Default field name and Handling of String and Field Pattern descriptors when the flow type is Link3270 Bridge. Follow these steps:
  1. Open the referenced screen message in the screen messages editor.
  2. Select the Screen Descriptions tab.
  3. Expand the relevant screen description.
  4. Identify any descriptor that uses a default field name (such as Field30) instead of a BMS field name. For more information about default field names, see Default field name.
  5. For each descriptor that uses a default field name, either modify the descriptor so that it uses a BMS field name or delete the descriptor.
Note: The restriction that screens in a Link3270 Bridge flow cannot use String or Field pattern descriptors for non-BMS-named fields as recognition criteria is lifted when you generate a flow for CICS Transaction Server for z/OS V3.2 or later.
CRRZE7310E
COBOL generation stopped with an error. A message used in node {1} having node type {0} is not valid for use as a flow {0} message. Method: {2}

Explanation

{0}
Node name
{1}
Node type
{2}
Method name

The COBOL generator could not create a COBOL data structure from one of the messages that are used by the specified node.

User response

To resolve this problem:
  1. Specify a valid message for the node.
  2. If the problem persists, resolve any errors or warning messages that are shown in the Problems view.
CRRZE7311E
COBOL generation stopped with an error. The invoke type of node {0} conflicts with the flow type of the flow.

Explanation

{0}
Invoke name

Depending on the flow type of your service flow (Non-Terminal, FEPI, Link3270 Bridge), only certain invoke types are supported. As specified in your Generation Properties, one of the invoke nodes in your service flow is of an invoke type that is not supported by the flow type of your flow. For more information about invoke types and flow types, see About invoke types and About flow types.

User response

Revise or remove from the flow any invoke node that has an invoke type that is not supported by the flow type of the flow.

CRRZE7312E
COBOL generation stopped with an error. A Link3270 Bridge flow requires the use of imported BMS maps.

Explanation

If the target runtime environment in the generation properties file is CICS Transaction Server for z/OS V3.1 and the flow type of the flow node in the generation properties file is Link3270 Bridge, each screen message that is referenced in the flow must contain BMS information. For more information about this requirement, see When the flow type is Link3270 Bridge -- BMS map information.

User response

When the target runtime environment is CICS Transaction Server for z/OS V3.1 and the flow type is Link3270 Bridge, each screen message must contain BMS map information.

To create a screen message that contains BMS map information, do one of the following steps:
  • Import a BMS Map directly into the service flow project to create a screen message.
  • Use the Assign BMS Field Names feature to update an existing screen message with BMS information.
For more information about these steps, see Working with information from BMS maps.

After you do these steps, you must re-record the flow before you generate runtime code.

Note: This limitation is removed when the target runtime environment is CICS Transaction Server for z/OS V3.2 and later.
CRRZE7313E
COBOL generation stopped with an error. The generation of copybook {0} failed in method: {1}

Explanation

{0}
Copybook name
{1}
Method name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

This error message can occur if you accidentally delete a message resource that is referenced in your service flow. Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7315W
String element {0} in message {1} does not have a length value. A default length value is assumed.

Explanation

{0}
Element name
{1}
Message name

A length value was not specified for the String element. A default length value of 255 was used.

User response

To set a value for the referenced message element:

  1. Use the flow message editor to open the message file that contains the message.
  2. In the editor area, select the Properties tab.

  3. In the Outline view, in the Types hierarchy, select the type specification of the element that was specified in the error message:
    1. In the Outline view, expand Types.
    2. Expand the complex type to which the element specified in the error message belongs.
    3. Within the complex type, expand the element that was specified in the error message.
    4. Within the element, select the simple type xsd:string.

    In the editor area, in the left pane, the flow message editor displays the Properties Hierarchy for this instance of the simple type xsd:string.

  4. In the editor area, in the Properties Hierarchy, select Logical properties > Value Constraints.

  5. In the right pane, in the Length Constraints group, in the Max field, type the maximum value that you want to use.

The maximum length for the element is set to the value that you typed in the Max field.

CRRZE7316E
COBOL generation stopped with an error. The VectorElement named {0} is not a Command or a Navigator. Method: {1}

Explanation

{0}
Element name
{1}
Method name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7317E
COBOL generation stopped with an error. The VectorElement named {0} does not contain a Branch. Method: {1}

Explanation

{0}
Element name
{1}
Method name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7318E
COBOL generation stopped with an error. The MessageQualifier array has no elements in node {0}. Method: {1}

Explanation

{0}
Node name
{1}
Method name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7319E
COBOL generation stopped with an error. The references array in a Branch is empty for node {0}. Method: {1}

Explanation

{0}
Node name
{1}
Method name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7320E
COBOL generation stopped with an error. A VectorReference was not found in a Branch for node {0}. Method: {1}

Explanation

{0}
Node name
{1}
Method name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7321E
COBOL generation stopped with an error. An element was not found or is null for {0} in node {1}. Method: {2}

Explanation

{0}
Resource type
{1}
Node name
{2}
Method name

This message can be displayed when a referenced file could not be found.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7322E
COBOL generation stopped with an error. A value was not found or is null for an expression in node {0}. Method: {1}

Explanation

{0}
Node name
{1}
Method name

An internal error occurred during the process to generate the runtime code for the service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7323E
COBOL generation stopped with an error. A VectorElement is not of type {0} for {1}. Method: {2}

Explanation

{0}
Resource type
{1}
Resource name
{2}
Method name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7324E
An ESQL expression contained more than the maximum number of CAST operations.

Explanation

An ESQL expression can have at most five CAST operations for a particular data type.

User response

Rewrite your ESQL expressions so that they do not have more than the maximum number of CAST operations.

CRRZE7325E
The {0} named {1} contained elements of ESQL that are not supported by the COBOL generator.

Explanation

{0}
Resource type
{1}
Resource name

Only a subset of the ESQL Operations is supported by the service flow project tools.

User response

For the list of supported language elements, see ESQL reference. Remove the unsupported language element from the specified resource.

CRRZE7326E
The flow is too large to document in the service flow properties file. Componentize segments of the flow as subflows.

Explanation

The service flow properties file has a maximum size limit of 32,600 characters. The size of the service flow properties file increases with each invoke node in the flow.

User response

Decrease the number of invoke nodes in your service flow until the size of the service flow properties file falls under its maximum size limit of 32,600 characters.

CRRZE7327E
An unexpected exception occurred because an index was out of bounds. Method: {0}

Explanation

{0}
Method name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7328E
An unexpected exception occurred involving component {0}. Exception: {1}. Method: {2}

Explanation

{0}
Component name
{1}
Error message
{2}
Method name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7329W
The {0} in the screen description {1} in screen message {2} is not supported for screen recognition in this context. The {0} is ignored.

Explanation

{0}
Resource type
{1}
Screen description name
{2}
Screen message name

Depending on the target runtime environment and whether you specified a flow type of FEPI or Link3270, certain screen descriptors might not be supported.

User response

Verify that the descriptors in the specified screen description are supported in the target runtime environment that you specified when you created the generation properties file. For more information about supported screen descriptors, see Support for screen descriptors in the runtime environments.

Note: For the Number of Fields, Number of Input Fields, and Fields Checksum descriptors: If the flow type specified in the generation properties file is Link3270 Bridge, and a screen message contains no BMS map information, and the screen description contains one of these three descriptors, then the Generate Runtime Code wizard processes the descriptor differently depending on the target runtime environment that is specified in the generation properties file:
  • If the target runtime environment is CICS Service Flow Runtime: Level 2.0, then the wizard processes the descriptor normally.
  • If the target runtime environment is CICS Service Flow Runtime: Level 1.0, then the wizard terminates with this error.
For more information about CICS service flow runtime levels, see CICS Service Flow Runtime Levels 1.0 and 2.0.
For more information about the descriptors, see Handling of Number of Fields, Number of Input Fields, Fields Checksum, and Cursor Position descriptors when the flow type is Link3270 Bridge.
CRRZE7330W
The field pattern descriptor or string descriptor in screen description {0} in screen message {1} contains invalid data for screen recognition. The field pattern descriptor or string descriptor is ignored.

Explanation

{0}
Screen description name
{1}
Screen message name

An internal error occurred during the process to generate the runtime code for your service flow.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7331W
Field {0} in screen description {1} in screen message {2} has a length greater than the maximum of 160 characters. Screen recognition will be performed using only the first 160 characters.

Explanation

{0}
Field name
{1}
Screen description name
{2}
Screen message name

Screen recognition criteria can be matched against only the first 160 characters of any field.

User response

There is no workaround to this limitation. If this truncation results in a screen not being uniquely identified, add more recognition criteria to the screen description.

CRRZE7332E
A code page conflict occurred. The host code page for the flow is {0} but the host code page for screen description {1} is {2}.

Explanation

{0}
Code page
{1}
Screen description name

The code page of a screen description must be the same as the code page specified in the generation properties file. For more help with this error, see CRRZE7333E.

User response

  • If the code page in the generation properties file is incorrect:
    1. Open the generation properties file in the generation properties editor.
    2. Set the Host Code Page field to the correct code page.
  • If the code page in one or more screen descriptions is incorrect, then follow these steps:
    1. For each screen description that has the incorrect code page:
      1. If the screen description contains BMS map information:
        1. Specify the correct code page in the BMS map.
        2. Reimport the screen description by using the Import BMS Map wizard.
      2. If the screen description does not contain BMS map information:
        1. Set the correct code page in Windows > Preferences > Enterprise Service Tools > Service Flow Projects > Code Page Settings.
        2. Recapture the screen description.
    2. Re-record the service flow.
CRRZE7333E
A code page conflict between screen descriptions occurred. Screen description {0} has a code page of {1}, but screen description {2} has a code page of {3}.

Explanation

{0}
Screen description name
{1}
Code page

All the screen descriptions in a terminal flow must use the same code page, and this code page must also be the same as the code page specified in the generation properties file for the flow. For more help with this error, see CRRZE7332E.

User response

  1. For each screen description that has the incorrect code page:
    1. If the screen description contains BMS map information:
      1. Specify the correct code page in the BMS map.
      2. Reimport the screen description by using the Import BMS Map wizard.
    2. If the screen description does not contain BMS map information:
      1. Set the correct code page in Windows > Preferences > Enterprise Service Tools > Service Flow Projects > Code Page Settings.
      2. Recapture the screen description.
  2. Re-record the service flow.
CRRZE7334E
An error occurred during Web service generation in {0}: {1}

Explanation

{0}
Method name
{1}
Error message

The service flow project tools use the batch processor utility (from the single-service project tools) in bottom-up mode to create the WSDL and WSBind files that are needed to invoke the generated service flow as a web service. An error was reported from the batch processor utility.

User response

For troubleshooting information for single-service projects, see Batch processor.

CRRZE7335E
Web service generation failed. File {0} was not generated. No additional information is available. Runtime code was successfully generated.

Explanation

{0}
File name

The service flow project tools use the batch processor utility (from the single-service project tools) in bottom-up mode to create the WSDL and WSBind files that are needed to invoke the generated service flow as a web service. An error was reported from the batch processor utility.

User response

For troubleshooting information for single-service projects, see Batch processor.

CRRZE7336E
An error occurred during Web service generation in method {0}. See the error log for more information.

Explanation

{0}
Method name

The service flow project tools use the batch processor utility (from the single-service project tools) in bottom-up mode to create the WSDL and WSBind files that are needed to invoke the generated service flow as a web service. An error was reported from the batch processor utility.

User response

For troubleshooting information for single-service projects, see Batch processor. For more information about the error log, see the topic "Error Log" in the top-level folder Eclipse documentation in the online help.

CRRZE7337E
The field named {0} in the message {1} generates to the same value as the COBOL PROGRAM-ID {2}. This name conflict will cause a compile error.

Explanation

{0}
Field name
{1}
Message name
{2}
ID
Because the field and the PROGRAM-ID have the same name, the following compile error occurs. In the program output, the following error message is printed all on one line.
IGYDS1266-E   The name xxxxxxxx was used for an 
   item that was not defined as a data-name.  
   References to this name may be resolved 
   incorrectly.

User response

Follow these steps:
  1. Make either of the following changes:
    • Modify the value of the Program Name that is specified for the flow in the generation properties file.
    • Rename and Refactor the field in the message.
  2. Rerun the Generate Runtime Code wizard.
CRRZE7338E
The field {0} in message {1} generates to the same value as the COBOL keyword {2}. This name conflict will cause a compile error.

Explanation

{0}
Field name
{1}
Message name
{2}
Keyword

A compilation error occurs because the field is named the same as a COBOL reserved word.

User response

Follow these steps:
  1. Rename and refactor the field in the message.
  2. Run the Generate Runtime Code wizard again.
CRRZE7339E
Two messages with different data structures have the same name: {0}. This conflict will cause data reference errors at compile time. Rename and refactor one of the messages.

Explanation

{0}
Message name

A compilation error occurs because references to two different data structures have the same name.

User response

Follow these steps:
  1. Rename and refactor one of the messages.
  2. Run the Generate Runtime Code wizard again.
CRRZE7340E
The {0} named {1} references the field {2}. This field does not have a BMS name and therefore cannot be used in a Link3270 Invoke screen operation node.

Explanation

{0}
Resource type
{1}
Resource name
{2}
Field name

When you extract data from a screen message that has BMS information that is associated with it, you can extract data only from fields that were named in that BMS map. This situation holds true whether you are extracting from a single field or from a rectangular area.

User response

Open the resource that contains the reference to the non-named field. Remove any references to the non-named field. During the import process, fields that were not named are given default names that are based on the position where they are found. Field30, for example, is the default name that is given to an unnamed field at position 30 of an imported BMS map. For more information about field names, see Default field name and Handling of String and Field Pattern descriptors when the flow type is Link3270 Bridge.

CRRZE7341E
COBOL generation stopped with an error. The maximum COMMAREA length for Invoke node {0} cannot be calculated. Manually enter a valid length value in the generation properties editor.

Explanation

{0}
Invoke name

The Generate Runtime Code wizard could not calculate the COMMAREA length automatically for the Invoke nonterminal node that is specified in the error message.

User response

In the generation properties editor, for the flow node that is specified in the error message, in the Maximum COMMAREA Length field, you selected Generate length value, a selection that usually causes the Generate Runtime Code wizard to calculate the maximum length of the COMMAREA automatically. However, in this case the wizard could not calculate that length. Therefore, you must calculate the length manually and type it into the field.

In the generation properties editor:
  1. Select the flow node that is specified in the error message.
  2. Calculate the maximum length that is required for the COMMAREA that is passed to the program specified in the Link to Program Name field.
  3. Type the length value into the Maximum COMMAREA Length field.

For more information about the generation properties, see Generation properties of the LINK with COMMAREA invoke type.

CRRZE7342W
The length {0} of a message specified for use with the Invoke nonterminal node {1} is greater than the maximum COMMAREA length specified for this node in the generation properties editor. This problem can cause a storage violation error at run time.

Explanation

{0}
Numeric value
{1}
Node name

For the Invoke nonterminal application node that is specified in the error message, the length of the input messages or the length of the output messages (which are specified in the mappings for this node) is greater than the value specified in the Maximum COMMAREA Length field for this node in the generation properties editor

User response

Because this message is a warning rather than an error, no action is required. However, because this length discrepancy can cause a storage violation at run time, consider making one of the following changes in the Maximum COMMAREA Length field in the generation properties editor:

  • Set the value to a number greater than the calculated length of the input message and greater than the calculated length of the output message.

  • Select Generate length value so that the Generate Runtime Code wizard calculates the value automatically.

For more information about generation properties, see Generation properties of the LINK with COMMAREA invoke type.

CRRZE7343W
The flow contains multiple output paths. Web service artifacts can be generated only for a single input path and a single output path. Web service artifacts for the output path resulting in a Reply node were generated, and the other output paths were ignored.

Explanation

Restriction: When the Generate Runtime Code wizard creates COBOL source code for a web service, and the flow from which the wizard creates the web service contains a Throw node, then the wizard ignores the Throw node and does not create a return point for the web service at the corresponding point in the COBOL source code.
The reason is that the generated COBOL source code for a web service can include only two interface points with the invoking program:
  • One input point, corresponding to the Receive node in the flow.
  • One output point, corresponding with the Reply node in the flow.

The source code cannot contain more return points that are associated with Throw nodes.

It is valid for a flow to contain one or more Throw nodes. But currently, when the Generate Runtime Code wizard is creating a web service and encounters a Throw node, the wizard ignores the Throw node and does not create a corresponding return point in the COBOL source code.

User response

Modify the design of the flow so that it does not rely on a Throw node as a return point to the program that invokes the flow.

For more information about this restriction, see Restrictions on execution within flows.

CRRZE7400E
COBOL generation stopped with an error. An input message was not found in the interface operation associated with an Invoke outbound Web service node.

Explanation

An Invoke outbound web service node in the flow is associated with an interface operation that does not contain an input message, or the Invoke outbound web service node does not have an interface operation that is associated with it.

User response

Open the .wsdl files in the Operations folder of your outbound web service subproject with the operations editor until you find the operation that is missing an input message. Add an input message to that operation, save the operations file, and run the Generate Runtime Code wizard again.

CRRZE7401E
COBOL generation stopped with an error. Neither an output message nor a fault message were found in the interface operation associated with an Invoke outbound Web service node.

Explanation

An Invoke outbound web service node in the flow is associated with an operation that does not have an output message or a fault message. An outbound web service operation must contain either an output message or a fault message, or can contain both.

User response

Open the .wsdl files in the Operations folder of your outbound web service subproject with the operations editor until you find the operation that lacks both an output message and a fault message. Add an output message or a fault message to that operation, save the operations file, and run the Generate Runtime Code wizard again.

CRRZE7500E
Flow playback or HATS macro generation stopped with an error. An unknown exception occurred. Exception text: {0}

Explanation

{0}
0

An unexpected exception occurred during flow playback or during HATS macro generation.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7501E
Flow playback or HATS macro generation stopped with an error. An internal error occurred.

Explanation

An internal error occurred during flow playback or during HATS macro generation.

User response

Resolve any errors or warning messages that are shown in the Problems view.

CRRZE7502E
Flow playback or HATS macro generation stopped with an error. Switch nodes are not supported in this context.

Explanation

Flow playback and HATS macro generation do not support Switch nodes. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime, you might not need to change the flow at all because Switch nodes are supported in the Service Flow Runtime context.
  • However, if you are required to use flow playback or HATS macro generation, and the Switch node is an essential component, then modify the flow to fix the problem:
    1. Delete the Switch node from the flow.
    2. Modify the flow so that the Switch node is not required.
CRRZE7503E
Flow playback or HATS macro generation stopped with an error. Invoke flow nodes are not supported in this context.

Explanation

Flow playback and HATS macro generation do not support Invoke flow nodes. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime, you might not need to change the flow at all because Invoke flow nodes are supported in the Service Flow Runtime context.
  • However, if you are required to use flow playback or HATS macro generation, and the invoked flow is an essential component, then modify the flow to fix the problem:
    1. Delete the Invoke flow node from the flow.
    2. Modify the flow so that the Invoke flow node is not required.
CRRZE7504E
Flow playback or HATS macro generation stopped with an error. An input message for the flow was not found.

Explanation

The interface operation for the flow does not contain an input message, or the flow is not associated with an interface operation.

User response

  1. Determine why the input message was not found and modify the flow to fix the problem. This problem can have the following causes:
    • The interface operation for the flow does not include an input message.
    • No interface operation is associated with the flow.
    • The interface operation that was previously associated with the flow was deleted from the flow.
  2. Resolve any errors or warning messages that are shown in the Problems view.
CRRZE7505E
Flow playback or HATS macro generation stopped with an error. Node {0} was not found or was null.

Explanation

{0}
Node name

The flow contains an invalid reference to the flow node specified in the error message. Either the reference is null or it refers to a flow node that could not be found in the flow.

User response

  1. Determine why the reference to the flow node failed and then modify the flow to fix the problem. This problem can have the following causes:
    • The reference is null.
    • In the reference, the name of the flow node is misspelled.
    • The flow node was renamed or was deleted from the flow.
  2. Resolve any errors or warning messages that are shown in the Problems view.
CRRZE7506E
Flow playback or HATS macro generation stopped with an error. An input screen message for the Invoke screen operation node {0} was not found or was null.

Explanation

{0}
0

The Invoke screen operation node that is specified in the error message is associated with a screen operation that has an invalid reference to an input screen message. Either the reference is null or it refers to an input screen message that could not be found in the flow.

User response

  1. Determine why the reference to the input screen message failed and then modify the flow to fix the problem. This problem can have the following causes:
    • The screen operation that is associated with the Invoke screen operation node is invalid.
    • The screen message that is referenced by the screen operation was deleted.
  2. Resolve any errors or warning messages that are shown in the Problems view.

Make sure that the specified node is associated with a valid screen operation.

CRRZE7507E
Flow playback or HATS macro generation stopped with an error. An output screen message for the Invoke screen operation node {0} was not found or was null.

Explanation

{0}
0

The Invoke screen operation node that is specified in the error message is associated with a screen operation that has an invalid reference to an output screen message. Either the reference is null or it refers to an output screen message that could not be found in the flow.

User response

  1. Determine why the reference to the output screen message failed and then modify the flow to fix the problem. This problem can have the following causes:
    • The screen operation that is associated with the Invoke screen operation node is invalid.
    • The screen message that is referenced by the screen operation was deleted.
  2. Resolve any errors or warning messages that are shown in the Problems view.
CRRZE7508E
Flow playback or HATS macro generation stopped with an error. Variable updates for flow node {0} could not be generated because variable {1} was not found.

Explanation

{0}
0
{1}
1

The flow node that is specified in the error message contained an instruction to write data into the specified variable, but the variable could not be found in the flow.

User response

  1. Determine why the reference to the variable failed and then modify the flow to fix the problem. This problem can have the following causes:
    • The variable was renamed without refactoring.
    • The variable was moved into a different data structure in the same message, or into another message in the same message file, or into another message file.
    • The variable was deleted.
  2. Resolve any errors or warning messages that are shown in the Problems view.
  3. If the error still occurs, try rebuilding the service flow project. For help with problem determination, see Problem determination.
CRRZE7509E
Flow playback or HATS macro generation stopped with an error. Mapping routine {0} contains invalid ESQL syntax.

Explanation

{0}
0

The mapping routine that is specified in the error message uses an element of ESQL syntax that is not supported in flow playback or in HATS macro generation. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.

User response

  1. Modify the flow to fix the problem. In the mapping routine, modify the ESQL syntax so that it is valid for flow playback or in HATS macro generation.
  2. Resolve any errors or warning messages that are shown in the Problems view.
CRRZE7510W
An unsupported ESQL keyword {0} was found in mapping routine {1} during flow playback or HATS macro generation. The mapping expression was ignored.

Explanation

{0}
0
{1}
1

The macro routine that is specified in the error message contained the specified ESQL keyword. Most elements of ESQL are not supported during flow playback or HATS macro generation. For more information about this restriction, see Restrictions on using ESQL.

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime, you might not need to change the mapping routine at all because some elements of ESQL are supported in the Service Flow Runtime context. For more information about ESQL, see ESQL reference.
  • However, if you are required to use flow playback or HATS macro generation, and the macro routine is an essential component, then modify the mapping routine to fix the problem:
    1. Delete the ESQL keyword (and any other ESQL elements) from the mapping routine.
    2. Modify the mapping routine or the flow so that the ESQL is not required.
CRRZE7511W
An unsupported mapping transform {0} was found in mapping routine {1} during flow playback or HATS macro generation. The transform was changed to a simple Move.

Explanation

{0}
0
{1}
1

Some mapping transforms are not supported by flow playback and HATS macro generation. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime environment, you might not need to change the mapping routine at all because all mapping transforms are supported in the Service Flow Runtime context. For more information about ESQL, see ESQL reference.
  • However, if you are required to use flow playback or HATS macro generation, and the macro routine is an essential component, then modify the mapping routine to fix the problem:
    1. Remove the unsupported mapping transform.
    2. Modify the mapping routine or the flow so that the unsupported mapping transform is not required.
CRRZE7512W
A unsupported mapping condition was found in mapping routine {0} during flow playback or HATS macro generation. The mapping condition was assumed to be true.

Explanation

{0}
0

Flow playback and HATS macro generation do not support conditions in mapping transforms. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime, you might not need to change the mapping routine at all because mapping conditions are supported in the Service Flow Runtime context. For more information about transforms and conditions, see Working with transforms and conditions.
  • However, if you are required to use flow playback or HATS macro generation, and the macro routine is an essential component, then modify the mapping routine to fix the problem:
    1. Delete the condition from the mapping transform.
    2. Modify the mapping transform or the flow so that the condition not required.
CRRZX0047E
Element "{0}" must include the required attribute "{1}".

Explanation

{0}
WSDL2ELS specification
{1}
File container

User response

CRRZX0092E
Unable to create a unique service parameter name for XML element "{0}".

Explanation

{0}
The name of an XML element
CRRZX0130E
Unique driver file names with prefix "{0}", suffix "{1}", and maximum length {2} have been exhausted in file container "{3}".

Explanation

{0}
File name prefix
{1}
File name suffix
{2}
Number of characters
{3}
Container name

The Batch Processor could not form a unique name for a converter driver file in the file container that is specified in DriverSpec/@fileContainer because no more unique eight-character file names could be generated from the specified prefix.

User response

Specify a shorter prefix in DriverSpec/@fileNamePrefix to allow larger values of the ordinal that is used to resolve file name collisions.

CRRZX0131W
No language structures were generated for global XSD element "{0}" referenced by Operation "{1}" because no mappable elements or attributes were found.

Explanation

{0}
Global element name
{1}
Operation name
WSDL2PLI determined that a global XSD element referenced by an operation in the WSDL defines a message that is empty. This message is issued to indicate that a language binding was not provided and to ensure that the empty message definition is intentional.

User response

If the empty message definition is intentional, no action is required, otherwise correct the XML schema and try again.

CRRZX0132E
No language structures could be generated for global XSD element "{0}" referenced by Fault "{1}" in Operation "{2}" because no mappable elements or attributes exist.

Explanation

{0}
Qualified element name
{1}
Qualified fault name
{2}
Operation name
WSDL2PLI and Compiled XML Conversion do not support the concept of a generic binding. Therefore, when a global XSD element describes the contents of the detail element of a fault message, it cannot be of an empty complex type. The complex type must contain at least one mappable XML element or XML attribute.

User response

Add at least one XML element or XML attribute to the complex type referenced by the global XSD element.
CRRZX0133E
Request and response elements have the same name "{0}" and the same namespace "{1}". The request and response elements must have different names or must be in different namespaces.

Explanation

{0}
Element name
{1}
Namespace name
XsdSpecIn and XsdSpecOut specifications in the ServiceSpecification.xml file contained identical values for element specification (xsdElemName="{0}") and identical target namespace values (targetNamespace="{1}").

User response

CRRZX0134E
An Operation with name "{0}" was not found in Binding "{1}" of Port "{2}" of Service "{3}".

Explanation

{0}
Operation name
{1}
Binding name
{2}
Port number
{3}
Service name

User response

CRRZX0135E
The maximum XSD array dimension limit of {0} has been exceeded at XSD XPath: {1}.

Explanation

{0}
An integer that specifies the maximum XSD array dimension limit
{1}
An XSD path name

User response

CRRZX0136E
The correlator file {0} could not be updated because it is either invalid or needs to be migrated to the current release. Correlator files may be migrated using the IMS Enterprise Suite SOAP Gateway deployment utility.

Explanation

{0}
The name of the correlator file

User response

Check the correlator file to ensure that it is valid and that it was upgraded to the current release.

Messages for the z Systems LPEX Editor

The following messages pertain to the z Systems LPEX Editor in Rational Developer for z Systems.

CRRZG0001E
The editor is unable to find the lexer from the stream.

Explanation

This error might be caused by a custom extension to the editor or a product defect.

User response

If you are using a custom extension to the editor, disable it. Otherwise, contact IBM Software Support.
CRRZG0010E
The editor could not display the message "{0}" at position {1}.

Explanation

The embedded language parser was attempting to display an annotation through the editor, but an error caused the process to stop. A custom extension to the editor might cause such an error.
{0}
Message text
{1}
The current position in the file that you are editing.

User response

If you are using a custom extension to the editor, disable it. Otherwise, contact IBM Software Support for assistance.
CRRZG0020E
Some of the required files were not found.

Explanation

The Show Expanded Source action was requested, but the include preprocessor could not locate some of the copybooks or include files.

User response

Associate a property group with the source file. The property group must specify these options:
  • In the SYSLIB field of the property group, specify a search path for copybooks and include files.
  • On the Local Preprocessors page, select -INC/++INCLUDE Preprocessor.
  • In the Preprocessor arguments field, specify CMT(ON).
Ensure that the search path specified in the SYSLIB field includes all copybooks or include files.
CRRZG0050E
Due to a null parsing job the editor is unable to perform the action.

Explanation

The error occurs when a declaration is opened in an item where parsing did not occur. The error can occur if annotations and tools are disabled and the F3 key is pressed to open a declaration.

User response

Verify that the tools or annotations are enabled. Try the process again. If the tools and annotations are enabled or the problem persists, contact IBM Software Support.
CRRZG0051E
Due to parsing errors the editor is unable to perform the action.

Explanation

This error might occur if the F3 key is used to open a declaration when there is a parsing error.

User response

Resolve parsing errors and try the process again. If the problem persists, contact IBM Software Support.
CRRZG0052E
Due to an invalid selection the editor is unable to perform the action.

Explanation

The selected item is not valid.

User response

Select a different item, and try the operation again.
CRRZG0053E
Due to a null parsing job the editor is unable to perform the action.

Explanation

This error occurs if you try to open the perform hierarchy in an item where parsing did not occur.

User response

Enable tools or annotations and tools, and try the operation again. Contact IBM Software Support to report the problem.
CRRZG0054E
Due to parsing errors the editor is unable to perform the action..

Explanation

An error occurred when opening the perform hierarchy because of a parsing error.

User response

Resolve the parsing errors, and try the action again. Contact IBM Software Support for assistance.
CRRZG0055E
Due to an invalid selection the editor is unable to perform the action.

Explanation

The selected item cannot be used because it cannot be resolved.

User response

Select a different item. If the problem persists, contact IBM Software Support for assistance.
CRRZG0056E
The editor is unable to create a perform graph..

Explanation

The argument that was passed to the perform graph function is incorrect.

User response

Try the function again with a different selection. If the problem persists, contact IBM Software Support for assistance.
CRRZG0057E
An attempt to add a part listener to the workbench failed.

Explanation

To add listeners to the workbench, they must be registered during startup. Listeners were not registered during startup. This situation can happen if the software is already running in nondisplay mode when the product is started.

User response

If the error occurs during normal use, contact IBM Software Support for assistance.
CRRZG0060I
An availability check failed.

Explanation

An unknown error occurred during the availability checking of the Open Declaration action.

User response

Contact IBM Software Support for assistance.
CRRZG0061I
An availability check failed.

Explanation

An error occurred during the availability check of the Open Perform Hierarchy action.

User response

Contact IBM Software Support for assistance.
CRRZG0062I
An availability check failed.

Explanation

An error occurred during the availability check of a Refactor action.

User response

Contact IBM Software Support for assistance.
CRRZG0100E
The editor is unable to locate a declaration for {0}.

Explanation

The editor cannot locate a declaration for the {0} paragraph. The location of the declared paragraph cannot be determined.
{0}
The name of the paragraph being referenced.

User response

Verify that the paragraph being referred to is declared, and try the operation again.
CRRZG0101E
The editor is unable to add performee {0} to the perform graph..

Explanation

An incorrect argument was passed to the perform graph function.
{0}
Performee name

User response

Contact IBM Software Support for assistance.
CRRZG0102E
The editor is unable to add a performer to the perform graph, node {0}, with declaration {1}..

Explanation

The argument passed to the perform graph function is incorrect.

User response

Contact IBM Software Support for assistance.
CRRZG0110E
The program {0} associated with file {1} could not be loaded..

Explanation

{0}
A COBOL or PL/I source program file name.
{1}
A COBOL copybook or PL/I include file.
The source program file that was associated with the included file by using the Associate Complete Program menu item cannot be loaded.

User response

  • Ensure that the file type of the included file that you want to associate with a complete program file matches the COBOL Copybook File or PL/I Include File content type. For more information about content types, see Setting content type associations.
  • Associate a property group with the program file. The editor uses the SYSLIB property group setting to locate included files. For more information about associating a property group with a program file, see Associating a property group with a resource.
CRRZG0111E
The content type of included file {0} is not supported..

Explanation

{0}
A COBOL copybook or PL/I include file.
The file type of the included file that you want to associate with a complete program file does not match the COBOL Copybook File or PL/I Include File content type.

User response

Ensure that the file type of the included file that you want to associate with a complete program file matches the COBOL Copybook File or PL/I Include File content type. For more information about content types, see Setting content type associations.

Messages for the z/OS Integrated Development Environment (zIDE)

These messages pertain to the z/OS Integrated Development Environment (zIDE) in Rational Developer for z Systems.

CRRZI0001E
The backup of an existing workspace has failed. Contact your IBM technical support representative.

Explanation

Workspaces from IBM WebSphere Developer for System z® v6.0 or v7.0 or IBM Rational Developer for System z v7.1 are updated to work in the latest version of Rational Developer for z Systems are updated to work in the latest version of Rational Developer for z Systems when you open the workspace in Rational Developer for z Systems. 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 IBM WebSphere Developer for System z v6.0 or v7.0 or IBM Rational Developer for System z v7.1 are updated to work in the latest version of Rational Developer for z Systems when you open the workspace in Rational Developer for z Systems. 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 IBM WebSphere Developer for System z v6.0 or v7.0 or IBM Rational Developer for System z v7.1 are updated to work in the latest version of Rational Developer for z Systems are updated to work in the latest version of Rational Developer for z Systems when you open the workspace in Rational Developer for z Systems. 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 v6.0.1. This message explains how to open the Remote Error List view, which was introduced in IBM WebSphere Developer for zSeries v6.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 z Systems 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:
  1. Edit the property group associated with the resource.
  2. Click the Assembler tab in the property group editor.
  3. Expand the procedure, select the step name, and click Edit in the Step Options area of the page.
  4. 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:
  1. Edit the property group associated with the resource.
  2. Click the PL/I tab in the property group editor and then select Procedures and Steps.
  3. Expand the procedure, select the step name, and click Edit in the Step Options area of the page.
  4. 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

  1. Close the current edit session.
  2. Add the file to an MVS subproject.
  3. 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

  1. Check the connection to determine whether the project is an online project and then try the operation again.
  2. Clear the remote system cache files by selecting Window > Preferences > Remote Systems > File Cache > Clear Cached Files, and then try the operation again.
  3. 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 z Systems 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 z Systems 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 z Systems 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:
  1. In the Remote Systems view, locate the remote system on which the resource you are working with is located.
  2. Expand the remote system connection and then expand JES > My Jobs.
  3. 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

  1. From the z/OS Projects view, select the subproject and then click Property Group > Associate Property Group.
  2. In the Associate Property Group window, choose a property group to associate with the subproject and click OK.
  3. 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

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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0092E
Write failed

Explanation

An I/O error occurred while uploading the file.

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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0093E
Read failed

Explanation

An I/O error occurred while downloading a file or finding a record in 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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0094E
Write Initialization failed

Explanation

The process failed to initialize output while writing to a file.

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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0095E
Read Initialization failed

Explanation

The process failed to initialize a file while reading the file.

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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0096E
Dynamic allocation failed.

Explanation

A request to allocate a 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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0097E
Open failed

Explanation

A request to open a 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 z Systems Host Configuration Reference (SC14-7290).
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
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 z Systems 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 z Systems 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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
CRRZI0152E
Start Command Server failed

Explanation

This error results from an APPC setup problem for the TSO Commands service.

User response

For information about tuning considerations when using APPC to start the TSO Commands service, see the IBM Rational Developer for z Systems Host Configuration Reference (SC14-7290).
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 z Systems. 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
  1. 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.
  2. 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:
    1. Right-click the destination data file and click Properties.
    2. Click Mapping.
    3. Click Other beneath Transfer mode, click binary, and then click OK.
  • For all files with a particular low-level qualifier:
    1. Click Window > Show View > z/OS file System Mapping. The view opens near the bottom of the workspace window.
    2. Right-click in the view and click Add data set mapping.
    3. 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.
    4. 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

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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0196E
Unable to rename file

Explanation

A request to rename a 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 z Systems Host Configuration Reference (SC14-7290).
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

For more information about this error, see the following topic in z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821): dynalloc() -- Allocate a Data Set.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
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

For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
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

For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
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

For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
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

For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
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

For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
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

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 z Systems Host Configuration Reference (SC14-7290).
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

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 z Systems Host Configuration Reference (SC14-7290). Contact IBM Software Support.
CRRZI0378E
Exception occurred.

Explanation

An unexpected server 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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0379E
The request has timed out because there is no response from the server.

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 z Systems Host Configuration Reference (SC14-7290).
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 z Systems users must have permission to write to the work area.

User response

  1. To determine whether the work area was created, issue the following commands from either telnet or MVS:
    cd /var/rdz
    ls -al
  2. If the WORKAREA directory does not exist, then create it by issuing the following command:
    mkdir WORKAREA
  3. Set the permissions so that all users have write authority:
    chmod 777 /var/rdz/WORKAREA
  4. 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
  5. If the "logs" directory does not exist, then create it by issuing the following command:
    mkdir logs
  6. 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.

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 z Systems Host Configuration Reference (SC14-7290).
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

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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0388E
The data set compression has failed. See the Error log for more details.

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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0389E
Copy command has 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 z Systems Host Configuration Reference (SC14-7290).
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

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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0391E
Copy command has failed. See the Error log for more details.

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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0393E
ALLOCATE failed. Record length is inconsistent with block size for this record format.

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 z Systems Host Configuration Reference (SC14-7290). Contact IBM Software Support.
CRRZI0394E
Server initialization 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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0395E
Migrate 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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0396E
Recall failed.

Explanation

An HRECALL command 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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0397E
Delete failed.

Explanation

An HDelete operation for a migrated 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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0398E
Server internal error. TSO server cannot be located.

Explanation

The TSO command server did not start normally.

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 z Systems Host Configuration Reference (SC14-7290). Collect the ffs*.log files and contact IBM Software Support.
CRRZI0399E
Server internal error. Bad TSO server response {0}.

Explanation

The TSO command server returned a bad response.

User response

Collect the fek*.log files and contact IBM Software Support. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for z Systems Host Configuration Reference (SC14-7290)
CRRZI0400E
Server internal error. Command target is not set.

Explanation

An internal command that was sent by the Rational Developer for z Systems client is incomplete. This message indicates an internal logic error.

User response

Collect the fek*.log files and contact IBM Software Support. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for z Systems Host Configuration Reference (SC14-7290)
CRRZI0401E
Server internal error. Unsupported command {0}.

Explanation

File Manager Integration detected an unsupported command sent by the Rational Developer for z Systems 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 z Systems client and server.

User response

Collect the fek*.log files and contact IBM Software Support. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for z Systems Host Configuration Reference (SC14-7290)
CRRZI0408E
Server internal error. Exception occurred.

Explanation

A severe internal error occurred.

User response

Collect the fek*.log files and contact IBM Software Support. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for z Systems Host Configuration Reference (SC14-7290)
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 z Systems 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 z Systems 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?

Explanation

{0}
File name

User response

Click Yes to overwrite the file or No to cancel the operation.
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.

Explanation

{0}
File name

User response

Select a different import file.
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 Property Group > Delete Overrides 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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:
  1. Create a partitioned data set in the MVS subproject.
  2. Copy the members from the source folder or partitioned data set.
  3. 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 z Systems 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:
  1. In the Remote Systems view, locate the remote system on which the DB2 table you are working with is located.
  2. Expand the remote system connection and then expand JES > My Jobs.
  3. 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

  1. Define a connection to the remote system indicated by {0}.
  2. Connect to the remote system.
  3. 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 z Systems 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 z Systems 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:
  1. On the Information page of the property group editor, identify the system that the property group belongs to.
  2. 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 z Systems 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 z Systems 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 is not allowed.

Explanation

{0}
Resource name

User response

No response is required.
CRRZI0496E
The resource '{0}' is already shared with a team provider. Sharing a resource with multiple team providers is not allowed.

Explanation

{0}
Resource name

User response

No response is required.
CRRZI0497E
The resource '{0}' is not shared with a team provider. The disconnect operation can be performed only on a shared resource.

Explanation

{0}
Resource name

User response

No response is required.
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.

Explanation

{0}
Project name

User response

No action is required.
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.

Explanation

{0}
Resource name
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 or open the member in the z Systems Data Editor?

Explanation

The Rational Developer for z Systems 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 Continue.
  • To open the file by using the z Systems Data Editor, which is better able to handle large data files, click Use z Systems Data Editor.
  • To cancel the file open operation, click Cancel.
  • To disable the warning, click Window > Preferences. 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 z Systems 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:
  1. Edit the property group associated with the resource.
  2. Select the category appropriate for the resource type: Assembler, COBOL, or PL/I.
  3. In the Procedure and Step Table, click a step name to display the step options.
  4. 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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

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 z Systems Host Configuration Reference (SC14-7290).
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:
  1. Cancel the current export action.
  2. Disconnect from primary system {1}.
  3. Connect to primary system {0}.
  4. 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

For more information about push-to-client file permissions and configuring push-to-client support on z/OS, see the IBM Rational Developer for z Systems Host Configuration Guide (SC23-7658).
CRRZI0535I
There are no changes between the workstation copy and the remote copy.

Explanation

This message displays in response to a Team > Synchronize with remote 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 Team > Synchronize with remote 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 Team > Synchronize with remote 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. Do you want 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 Remote > Copy to Remote or Remote > Synchronize with Remote 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.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0549E
Contents cannot be retrieved from {0}.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0550E
Failure to retrieve member contents {0}.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0551E
Contents cannot be set on {0}.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0552E
Failure to write member contents.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0553E
Failed to connect to {0}.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0554E
Could not find {0} on {1}.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0555E
Contents cannot be retrieved from {0}.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0556E
Contents cannot be set on {0}.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0557E
Could not access properties.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0558E
Syntax check not successful.

Explanation

Attention: The remote synchronization function is deprecated.
CRRZI0559W
Some project resources are not synchronized. Do you want to stop the syntax check and open the Team Synchronizing perspective?

Explanation

Attention: The remote synchronization function is deprecated.
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.
CRRZI0561E
The specified remote system {0} is unknown.

Explanation

A remote system referenced in the .RemoteMapping pushable manifest editor file is unknown.

User response

Open the Pushable Manifest Editor and specify a valid remote system location.
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}

Explanation

Attention: The remote synchronization function is deprecated.
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 z Systems 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.

Explanation

The workspace was not migrated.

User response

For information about migrating workspaces, see Migrating workspaces.
CRRZI0584E
Workstation folder {0} under the offline project cannot be migrated.

Explanation

Attention: The work offline and work online operations for a remote resource are deprecated.
{0}
A folder name.
The specified folder is not migrated.

User response

No action is required.
CRRZI0585E
Unable to find the VisualAge CICS Translator or the Transaction Server Translator

Explanation

The operation requires the VisualAge® CICS Translator or the Transaction Server Translator, but these tools were not found.

User response

Install one of these translators and try the operation again.
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.
CRRZI0587E
Local build and local syntax check require an application driver JDBC connection. The driver associated with connection {0} is not an application driver connection. The operation will continue. The SQL coprocessor will not be invoked.

Explanation

{0}
The name of a database connection definition.

User response

If you want to the SQL coprocessor top be started, use a database connection that has application driver associated with it. Otherwise, no action is required.
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 z Systems 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 z Systems, 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 z Systems shuts down and IBM Installation Manager starts to begin the product update. After the product update completes, Rational Developer for z Systems restarts automatically.
  • To cancel the product update and shut down Rational Developer for z Systems, click Cancel. The next time you start Rational Developer for z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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 z Systems 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:
    1. Click Window > Preferences. The Preferences window opens.
    2. Expand the Remote Systems and z/OS sections and click MVS Files.
    3. 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.

Explanation

An editor could not open on the selected resource.

User response

Select a different file and try the operation again.
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. Do you want 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

  1. Before you click Work Online, upload any changes that you made to the resources when the project was offline.
  2. 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.
  3. 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
z Systems Data Editor failed to open the file {0}.

Explanation

The z Systems 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
z Systems Data Editor failed to save the file {0} on the remote system.

Explanation

The z Systems 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 z Systems 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 z Systems 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 z Systems on a Linux platform, the following message text also displays:
Rational Developer for z Systems 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

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 z Systems Host Configuration Reference (SC14-7290).
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 z Systems 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 z Systems 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.
CRRZI0751E
An error occurred when creating the remote preprocessor input data set {0}.

Explanation

When you start a remote preprocessor, the input for the remote preprocessor is written to a file in a sequential data set. Then, the remote preprocessor can read from the sequential data set to get the information it needs. An error occurred allocating the data set or writing to it.
{0}
A data set name.

User response

Verify with your systems administrator that you have permission to allocate and write to sequential data sets on the remote system where the remote preprocessor runs.
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 z Systems 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:
  1. To open the MVS Files preferences page, select Window > Preferences and then expand Remote Systems > z/OS and click MVS Files.
  2. 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 z Systems 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

Contact your systems administrator. For more information about configuration groups, see the Rational Developer for z Systems Host Configuration Reference (SC14-7290).
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 z Systems 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

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 z Systems Host Configuration Guide (SC23-7658).
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:
  1. 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.
  2. From the list on the left side of the Properties window, click Mapping.
  3. 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:
  1. 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.
  2. From the list on the left side of the Properties window, click Mapping.
  3. 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:
  1. 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.
  2. From the list on the left side of the Properties window, click Resource.
  3. 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

Try the operation again. 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 z Systems Host Configuration Reference (SC14-7290).
CRRZI0777E
Problems occurred while adding Data Access Support to the selected resource.

Explanation

Data Access Support was not added to the resource.

User response

Try the operation again.
CRRZI0778E
Problems occurred while removing Data Access Support from the selected resource.

Explanation

Data Access Support was not removed from the selected resource.

User response

Try the operation again.
CRRZI0779E
The options data set exists, but is not a sequential data set. Delete the data set before attempting to update the profile.

User response

Specify a sequential data set.
CRRZI0780E
The options data set is migrated. From the Remote Systems Explorer view, request HRECALL for the sequential data set.

User response

Recall the data set and try the operation again.
CRRZI0781E
The options specified "{0}" contain a string of more than 72 consecutive characters with no comma to break the string.

Explanation

{0}
The Language Environment options that were specified in the debug profile.

User response

Specify a string of 72 characters or less.
CRRZI0782E
An error occurred while writing to the profile data set "{0}".

Explanation

{0}
A data set name.

User response

Make sure you have write access to the data set and try the operation again.
CRRZI0783E
The EQAOPTS data set "{0}" could not be allocated. {1}

Explanation

{0}
A data set name.
{1}
A return code.
CRRZI0784I
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. Click Notify to be notified when the job completes.

Explanation

{0}
The job ID of a job that was submmitted to JES.
{1}
A remote system name.

User response

No action is required.
CRRZI0785W
The file {0} is locked by another user and cannot be opened.

Explanation

{0}
A file name.
Another user has a lock on the specified file.

User response

Wait until the file is no longer locked and try the operation again.
CRRZI0786W
The file {0} is locked by ''{1}'' and cannot be opened.

Explanation

{0}
A file name.
{1}
A user ID.
Another user has a lock on the specified file.

User response

Ask the user to release the file or wait until the file is no longer locked and try the operation again.
CRRZI0787W
The program {0} is duplicated elsewhere in the scan.

Explanation

{0}
A program name.
The COBOL call analyzer determined that the program name shown in the message is duplicated in another program source file.

User response

Consider updating the source programs to ensure that each program source file specifies a unique name in the PROGRAM-ID statement.
CRRZI0788E
{0} is using {1} parameters but {2} expects {3} parameters.

Explanation

{0}
The name of a calling program.
{1}
The number of parameters that the calling program is passing to a called program.
{2}
The name of the called program.
{3}
The number of parameters expected by a called program.
The COBOL call analyzer determined that the calling program name shown in the message is calling another program with an unexpected number of parameters. The message shows the number of parameters expected by the called program.

User response

Consider updating the parameters in the call to the target program.
CRRZI0789E
{0} is using {1} parameter but {2} expects {3} parameters.

Explanation

{0}
The name of a calling program.
{1}
The number of parameters that the calling program is passing to a called program.
{2}
The name of the called program.
{3}
The number of parameters expected by a called program.
The COBOL call analyzer determined that the calling program name shown in the message is calling another program with an unexpected number of parameters. The message shows the number of parameters expected by the called program.

User response

Consider updating the parameters in the call to the target program.
CRRZI0790E
{0} is using {1} parameter but {2} expects {3} parameter.

Explanation

{0}
The name of a calling program.
{1}
The number of parameters that the calling program is passing to a called program.
{2}
The name of the called program.
{3}
The number of parameters expected by a called program.
The COBOL call analyzer determined that the calling program name shown in the message is calling another program with an unexpected number of parameters. The message shows the number of parameters expected by the called program.

User response

Consider updating the parameters in the call to the target program.
CRRZI0791E
{0} is incompatible with {1}; parameter {2} has a size of {3} but {4} is expecting a size of {5}.

Explanation

{0}
The name of a calling program.
{1}
The name of a called program.
{2}
The order of a parameter in a program call.
{3}
The size of the parameter
{4}
The name of the called program.
{5}
The expected size of the parameter.
The COBOL call analyzer determined that the calling program name shown in the message is calling another program with a parameter that has an unexpected size. The message shows the size of the parameter that is exepcted by the called program.

User response

Consider updating the parameter in the call to the target program.
CRRZI8501E
A connection to {0} is required to complete this action.

Explanation

{0}
A database system.

User response

Connect to the specified database and try the operation again.
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

  1. 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.
  2. Delete the stored procedure in the Data Development Project.
  3. Re-create the stored procedure by using the Create Stored Procedure Wizard.
  4. 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.
  5. 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.
CRRZI8507E
'{0}' already exists in '{1}'. Select a different source data set.

Explanation

{0}
A member name.
{1}
A partitioned data set name.
An attempt was made to save a stored procedure to a partitioned data set, but the partitioned data set contains a member with the same name.

User response

Select a different partitioned data set.
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.
CRRZI8510I
The selected file '{0}' is already open in another edit session. Close the edit session before opening this file as a stored procedure.

Explanation

{0}
A file name.
An attempt was made to open the file as a stored procedure, but the file is open in another edit session.

User response

Close the editor and try the operation again.
CRRZI8511W
The stored procedure already exists. Replace the existing stored procedure?

Explanation

An attempt was made to save a stored procedure with the same name as an existing stored procedure.

User response

Click Yes to replace the existing stored procedure or No to return to the editor. Save the stored procedure with a different name.
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 z Systems 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 z Systems 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 z Systems 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. Do you want to open the backup copy in the editor?

Explanation

Rational Developer for z Systems 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 z Systems 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 z Systems 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 z Systems 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 the JES Job Monitor

These messages pertain to the Job Entry System (JES) Job Monitor in Rational Developer for z Systems.

CRRZI0072E
The job submission failed because the job card is incomplete or invalid. Verify the job card and submit the job again.
CRRZI9001I
This job output contains {0} lines. Specify the starting line and number of lines to retrieve.

Explanation

This message displays as a result of the Open from line action in the Remote Systems view. It shows the number of lines in the currently selected job output. It also prompts you to enter the starting line and the number of lines of the job output to display.

User response

Type the starting line number in the Retrieve output starting at line field and the number of lines to display in the Number of lines to retrieve field and click OK. To display 100 lines of output that start at line 500, for example, type 500 in the Retrieve output starting at line field and 100 in the Number of lines to retrieve field and click OK.
CRRZI9002I
This job output contains {0} lines, which exceeds your specified job output retrieval limit. How do you want to proceed?

Explanation

This message displays when you request to open job output for a job whose number of lines exceeds the Max Number of Lines to Download setting in the JES preferences. It prompts you to specify how you want to open the output.

User response

You can choose from the following two options for displaying job output:
  • Show output from the first line to line number: Choose this option to open a portion of the job output. Specify a line number in the input field to open output from line 1 to the line number entered.
  • Show the complete job output: Choose this option to open the complete job output.
CRRZI9003E
Unable to connect to the JES Job Monitor on port {1} of host {0}.

Explanation

Rational Developer for z Systems was unable to establish a connection to JES on the port number shown on the remote system (host) shown.

User response

  1. Verify with your system administrator that the remote system is available and that the JES Job Monitor is installed and running.
  2. Open the JES properties page by selecting JES in the Remote Systems view and then selecting Properties. Verify with your system administrator that the correct port is specified.
CRRZI9004E
Not authorized for job {0}.

Explanation

You are not authorized to do the requested action for the job number shown.

User response

Verify that you selected the correct job ID. Select a job that you are authorized to do the action on and try again.
CRRZI9005I
Cancel has been issued for job {0}.

Explanation

A Cancel action was issued for the job ID shown.

User response

No action is required.
CRRZI9006E
Job {0} cannot be canceled.

Explanation

A Cancel action was issued for the job ID shown, but the job is complete.

User response

No action is required.
CRRZI9007E
The entry for Job class is an empty string.

Explanation

The Job class field on the New JES Job Filter window is required, but this field is empty.

User response

Specify a value in the Job class field.
CRRZI9008I
Hold has been issued for job {0}.

Explanation

A Hold action was issued for the job ID shown.

User response

No action is required.
CRRZI9009W
No information is available for job {0}. Unable to update the status.

Explanation

A Refresh Status action was issued for the selected job, but no information is available. The job might be complete.

User response

No action is required.
CRRZI9010W
No jobs match the search criteria.

Explanation

A filter string entered into the Retrieve Job window resulted in no matches.

User response

Enter another filter string and try again.
CRRZI9011W
No output for job {0}.

Explanation

An Open action for the job ID shown failed because the job produced no output or is not yet complete.

User response

Wait for the job to complete or select another job and try again.
CRRZI9012E
The entry for Job output class is an empty string.

Explanation

The Job output class field on the New JES Job Filter window is required, but this field is empty.

User response

Specify a value in the Job output class field.
CRRZI9013E
The entry for Job owner is invalid.

Explanation

The Job 0wner field on the New JES Job Filter window is required, but this field is empty or the value specified is not valid.

User response

Specify a value in the Job owner field. To specify the user ID with which you logged in to the remote system, specify &USERID.
CRRZI9014E
The entry for Job name prefix is an empty string.

Explanation

The Job name prefix field on the New JES Job Filter window is required, but this field is empty.

User response

Specify a value in the Job name prefix field.
CRRZI9015I
Print has been issued for job {0}.

Explanation

A Print action was issued for the job ID shown.

User response

No action is required.
CRRZI9016I
Purge has been issued for job {0}.

Explanation

A Purge action was issued for the job ID shown.

User response

No action is required.
CRRZI9017I
Release has been issued for job {0}.

Explanation

A Release action was issued for the job ID shown.

User response

No action is required.
CRRZI9018I
Restart has been issued for job {0}.

Explanation

A Restart action was issued for the job ID shown.

User response

No action is required.
CRRZI9019E
The entry for Job status is an empty string.

Explanation

The Job status field on the New JES Job Filter window is required, but this field is empty.

User response

Specify a value in the Job status field.
CRRZI9020E
Login failed. The user ID or password is incorrect.

Explanation

An attempt to log on to the JES subsystem failed because the password specified is incorrect.

User response

Specify a different password and try again.
CRRZI9021E
The entry for the maximum number of lines to download ({0}) is invalid.

Explanation

The value specified in the Max Number of Lines to Download field of the Properties for JES window is invalid.

User response

Specify a value 1 - 2147483647.
CRRZI9022E
The password has expired.

Explanation

Your password for the remote system to which you are trying to connect expired.

User response

Enter a new password when prompted. If you are not able to reset your password, contact your system administrator.
CRRZI9023E
The new password is not valid. Reenter a valid password.

Explanation

The password entered does not match the security requirements of your site.

User response

Consult with your system administrator to obtain valid password requirements and try again.
CRRZI9024E
The entry for port {0} is invalid.

Explanation

The value specified in the JES Job Monitor Port field of the Properties for JES window is invalid.

User response

Consult your system administrator for the correct port number and try again.
CRRZI9025E
Unsupported server protocol level {0}.

Explanation

The Job Monitor server and the RSE JES Miner were unable to negotiate an acceptable command protocol level.
{0}
The server protocol level that is unsupported.

User response

Either the Job Monitor server (load module FEJJMON) or the RSE JES Miner (jesminers.jar) is not at the latest level. Make sure that you correctly installed these components.
CRRZI9026E
Unexpected RACF error encountered.

Explanation

A RACF error occurred while attempting to log on to the remote system.

User response

Contact your system administrator.
CRRZI9027I
The session has been idle more than {0} seconds. The connection has been terminated.

Explanation

The connection to the remote system ended because of inactivity.

User response

Connect to the remote system again.
CRRZI9028E
Unable to allocate session code page conversion ({0}). Continue using default conversion.

Explanation

The Job Monitor server (JMON) attempted to allocate a code page converter, but the allocation failed.

User response

Make sure that enough memory is available to the Job Monitor server (JMON).
CRRZI9029E
Unable to set the JES Job Monitor host code page to {0}. Continuing with the default host code page.

Explanation

The host code page cannot be set to the value specified in the system code page mapping.
{0}
A host code page.

User response

Check that the JMON job is running on the host, and that it is at the correct level.

Messages for Deep Program Analysis Tools for COBOL and PL/I

These messages pertain to the common program analysis tools for deep program analysis of COBOL and .PL/I code.

CRRZJ0001I
No unreachable code was detected in the program.

Explanation

The Source > Identify Unreachable Code action was requested, but the file contains no unreachable code.

User response

No action is required.
CRRZJ0002E
The view cannot be opened because the program cannot be parsed or parsing has not completed.

Explanation

The Open Program Control Flow function was requested in the COBOL Editor or z Systems LPEX Editor. This function uses an internal COBOL parser to analyze program control flow in a source file. Either the analysis cannot be completed because of syntax errors in the source file, or the analysis is still in progress.

User response

Check for syntax errors in the file. Correct the errors, and try the operation again.
CRRZJ0003E
An unexpected error was found while selecting a diagram node in the Program Control Flow view.

Explanation

An internal error occurred in the Program Control Flow diagram.

User response

Try the operation again. If the problem persists, contact IBM Software Support.
CRRZJ0004E
An unexpected error was found while opening the view.

Explanation

An internal error occurred during a request to open the Program Control Flow view.

User response

Try the operation again. If the problem persists, contact IBM Software Support.
CRRZJ0005E
An unexpected error was found while analyzing the program for unreachable code.

Explanation

An internal error occurred during an Identify Unreachable Code request

User response

Try the operation again. If the problem persists, contact IBM Software Support.
CRRZJ0006I
Unreachable code calculation is based on source analysis and not on the compiler results. You may want to verify the results for your program before taking further action.

Explanation

Because the Identify Unreachable Code feature uses a static analysis of the program source to identify potential dead code, it is not a reflection of the actual execution path.

User response

Before you delete any code, verify that the code is correctly identified as unreachable.

This message is displayed each time that you use the Identify Unreachable Code function. To prevent this message from being displayed, click Do not show this message again.

CRRZJ0007E
The program can not be analyzed for unreachable code because it cannot be parsed.

Explanation

The Identify Unreachable Code function was requested in the COBOL Editor or z Systems LPEX Editor. This function uses an internal COBOL parser to analyze a source file. The analysis cannot be completed because of syntax errors in the source file.

User response

Check for syntax errors in the file. Correct the errors, and try the operation again.
CRRZJ0008E
Unexpected internal error found: {0}. Additional information may be written to trace if enabled.

Explanation

{0}
An internal code location to help identify the source of the error. This code location might be accompanied by more log or trace messages.
An internal error occurred during a request to show the source file in the Data Elements view.

User response

  • Examine the log and trace files for error messages. The product log and trace files are in the .metadata folder of the workspace path. To see the path name of the workspace, click File > Switch Workspace > Other. The Launch Workspace window opens and displays the path of the current workspace.
  • To turn on tracing for the deep code analysis feature:
    1. Click Window > Preferences and select Tracing.
    2. In the Tracer Name column, select com.ibm.systemz.common.analysis.
    3. In the Tracing Level column, choose a tracing level option.
CRRZJ0009E
An unexpected error was found while updating the view.

Explanation

An internal error occurred in the Program Control Flow diagram.

User response

Try the operation again. If the problem persists, contact IBM Software Support.
CRRZJ0010W
Program Control Flow diagram may not be accurate for this program because it contains one of the following unsupported statements: EXEC CICS HANDLE, EXEC CICS IGNORE, EXEC CICS PUSH, EXEC CICS POP, and EXEC SQL WHENEVER.

Explanation

The program control flow diagram does not display control flow nodes for control transfers that are generated by the following statements:
  • EXEC CICS HANDLE
  • EXEC CICS IGNORE
  • EXEC CICS PUSH
  • EXEC CICS POP
  • EXEC SQL WHENEVER

User response

Use the Show In > Program Control Flow function in programs that do not contain these statements.
CRRZJ0011E
The unreachable code feature does not support programs containing the following statements: EXEC CICS HANDLE, EXEC CICS IGNORE, EXEC CICS PUSH, EXEC CICS POP, and EXEC SQL WHENEVER.

Explanation

The Identify Unreachable Code function has several restrictions:
  • Copy books that are associated with the open file are not included in the program analysis. The analysis works within the boundary of the file.
  • Quick fix is not available.
  • Not available for programs that contain the following statements:
    • EXEC CICS HANDLE
    • EXEC CICS IGNORE
    • EXEC CICS PUSH
    • EXEC CICS POP
    • EXEC SQL WHENEVER
  • CALL statements that do not return to the calling program can result in results that are not correct. Statements after a CALL statement are not marked as unreachable.
  • Unreachable code is reported on a per line basis. If a line contains both code that is reachable and code that is unreachable, the reported results might be incorrect. Use the COBOL formatting tool to enforce the one-verb-per-line rule to prevent reachable and unreachable code in the same line.

User response

Use the Identify Unreachable Code function in programs that do not contain these statements.

Messages for MFS Screen Designer (MFS Map Editor)

These are the messages that pertain to the MFS Screen Designer (MFS Map Editor) in Rational Developer for z Systems.

CRRZM0159E
The input is not valid.

Explanation

The input is not valid.

User response

Remove the invalid input, and provide valid input.
CRRZM0161E
The inital value not valid.

Explanation

The initial value that was provided is not valid.

User response

Remove the invalid initial value, and provide a valid initial value.
CRRZM0162E
The row is null.

Explanation

The row value in the definition of a new MFS Device field was left null.

User response

Provide a row value when defining a new MVS Device field.
CRRZM0163E
The position is not valid.

Explanation

The selected position is not within the map boundaries.

User response

Select a position that is within the map boundaries.
CRRZM0164E
The column is null.

Explanation

You must define at least one column.

User response

Define one or more columns.
CRRZM0165E
The length of the group name is not valid.

Explanation

The group name entered is too long/short.

User response

Enter a shorter/longer group name.
CRRZM0177E
An error occurred while parsing the source.

Explanation

A syntax error in the source caused an error.

User response

Open the Source Page and modify the source so that the error is resolved.
CRRZM0178E
An invalid name was specified.

Explanation

The specified name is either invalid or empty.

User response

Specify a valid name.
CRRZM0178E
An invalid name was specified.

Explanation

The specified name is either invalid or empty.

User response

Specify a valid name.
CRRZM0241E
File container must be specified

Explanation

The location for the destination of a process is not specified.

User response

Provide the destination location for the process.
CRRZM0242E
File name must be specified

Explanation

The file name is required to perform the process.

User response

Specify a valid file name.
CRRZM0243E
File extension must be mfs

Explanation

The file extension is not correct.

User response

Change the file extension to mfs.
CRRZM0323E
Device format name is not valid.

Explanation

The device format name is not defined or not correct.

User response

Enter a valid device format name.
CRRZM0324E
The device format name is null.

Explanation

The device name is missing.

User response

Enter a valid device format name.
CRRZM0325E
The message definition name is not valid.

Explanation

The message definition name is not defined or not correct.

User response

Enter a valid message definition name.
CRRZM0326E
The message definition name is null.

Explanation

The message definition name is missing.

User response

Enter a valid message definition name.
CRRZM0331E
The file name is null.

Explanation

A file name cannot be null.

User response

Specify a file name that is not null.
CRRZM0332E
The file name is not valid.

Explanation

The file name used is not correct.

User response

Change the file name.
CRRZM0333E
A duplicate file name has been specified.

Explanation

The file name entered is already in use.

User response

Enter a different file name.
CRRZM0350E
No column has been defined.

Explanation

Table does not have a defined column.

User response

Select a valid column or insert a column into the table.
CRRZM0370E
The total width exceeds the defined table width.

Explanation

Size of insert is greater than table width..

User response

Insert a smaller selection.
CRRZM0437E
The width value is not valid. It must be in the range 1-120.

Explanation

The width value is not valid.

User response

Enter a valid value in the range of 1-120.
CRRZM0438E
The Features value is not set.

Explanation

The features value is missing.

User response

Enter a valid features value.
CRRZM0450E
The exit number value is not valid.

Explanation

The exit value i snot defined or not correct.

User response

Enter a valid exit number value.
CRRZM0451E
The exit vector value is not valid.

Explanation

The exit vector value is missing.

User response

Enter a valid exit vector value.
CRRZM0452E
A literal is longer than 255 characters.

Explanation

The literal value is over 255 characters.

User response

Enter a literal value of less than 255 characters.
CRRZM0453E
An extended attribute value is not between 1 and 10.

Explanation

An extended attribute value is not in the range 1-10.

User response

Specify an extended attribute value in the range 1-10.
CRRZM0454E
The length of the value does not equal the field length.

Explanation

The length of the value does not equal the field length.

User response

Enter a valid length value.
CRRZM0455E
The field length is 0.

Explanation

The length of the value does not equal the field length.

User response

Enter a valid length value.
CRRZM0456E
The row is null.

Explanation

You must define at least one row.

User response

Define one or more rows.
CRRZM0457E
The column is null.

Explanation

You must define at least one column.

User response

Define one or more columns.
CRRZM0458E
The field position is not valid.

Explanation

The entry used is not correct.

User response

Change or delete the field position value.
CRRZM0459E
The value of the offset is not valid.

Explanation

The entry is not correct.

User response

Change or delete the offset value.
CRRZM0460E
An invalid division name was entered.

Explanation

The entry used is not correct.

User response

Change or delete the division name value.
CRRZM0463E
The value of PAGE is not valid.

Explanation

The entry used is not correct.

User response

Change or delete the PAGE value.
CRRZM0464E
The value entered for Device Field cannot be used.

Explanation

The entry used is not correct.

User response

Change and delete the Device Field value.
CRRZM0465I
The COPY keyword is not supported.

Explanation

The COPY keyword is not supported.

User response

Remove any instance of the COPY keyword.
CRRZM0467I
The selected statement cannot be edited. It is read-only.

Explanation

The statement is a read-only statement and cannot be modified.

User response

No action required.
CRRZM0470E
Copy file {0} was not found at the specified location.

Explanation

The path to the field is not valid or the file name is not valid.

User response

Verify both the path to the file and the file name.
CRRZM0471E
An error occurred when opening the file.

Explanation

An error occurred that kept the file from opening.

User response

This message is the header to additional messages. See the documentation for the additional message.
CRRZM0474E
Invalid character {0} was found after {1} at line {2} and column {3}..

Explanation

The character you entered is not allowed at the indicated location.

User response

Change or delete the character.
CRRZM0475E
The editor failed to parse statement {0} at line {1} column {2}.

Explanation

A parse error was found at the indicated location.

User response

Change or delete the parse statement.
CRRZM0477E
A lexical error was encountered at line {0} and column {1}.

Explanation

A lexical error was found at the indicated location.

User response

Change or delete the character.
CRRZM0480E
An invalid location is selected.

Explanation

The location that is selected is not valid.

User response

Select a valid location.
CRRZM0481E
An invalid field name is entered.

Explanation

The field name that is entered is not valid.

User response

Enter a valid field name.
CRRZM0482I
A copybook file was created.

Explanation

The requested copybook file was created successfully.

User response

No action required.
CRRZM0483I
The copybook file has been created.

Explanation

The requested copy book file was created successfully.

User response

No action required.
CRRZM0484E
The file name is not valid.

Explanation

A file name was specified that is not valid.

User response

Specify a valid file name.
CRRZM0485E
EGCS value range should be between X'40' and X'FE'

Explanation

The EGCS value that was provided does not fall within the range X'40' and X'FE'.

User response

Change the EGCS value so that it falls within the range X'40' and X'FE'.
CRRZM0486E
Programmed Symbol value range should be between X'40' and X'FE'

Explanation

The Programmed Symbol value range that was provided does not fall within the valid range of X'40' and X'FE'.

User response

Change the Programmed Symbol value range so that it falls within the range of X'40' to X'FE'.
CRRZM0487E
Fill value is invalid. Enter a valid HEX value

Explanation

The FILL value that is specified violates the valid format.

User response

Replace the specified fill value with a correctly formatted hex value, for example FILL X'00'.
CRRZM0488E
Fill value is invalid. Enter a valid Fill character

Explanation

The FILL value that is specified violates the valid format.

User response

Replace the specified fill value with a correctly formatted character, for example FILL C'c'.
CRRZM0489E
A duplicate name has been specified.

Explanation

Names in MFS must be unique, and the name that is specified is not unique.

User response

Modify the name that you entered to be unique.
CRRZM0490E
Device Page cannot accept multiple physical pages.

Explanation

A physical page was attempted to be created on a device page that already had a single physical page and did not specify the MULT=YES attribute.

User response

To specify that the device page can accept multiple physical pages, select the device page in the outline view. In the properties view, mark the Multiple physical pages check box. The MULT=YES attribute is added to the device page in the source and physical pages can be added without error.
CRRZM0491E
The file type is invalid. Please select a valid MFS file.

Explanation

The file that is selected as the target for the created MFS message is not a correctly formatted MFS file.

User response

Select a file that has a MFS extension and contains no parse errors when opened with the MFS editor.
CRRZM0492E
MFS Message cannot be created because the selected file has syntax errors.

Explanation

The file that is selected as the target for the MFS message creation contains syntax errors. Syntax errors in the MFS source prevent the MFS message from being appended to the file.

User response

Open the file in the MFS editor, view the source page, and correct any syntax errors. After you correct any syntax errors, save the file and try creating the MFS message again.
CRRZM0493E
Field will overlap an existing field in the specified Physical Page

Explanation

A field is modified with new a new location that, if placed, will overlap with an existing field in the specified physical page. This overlap can happen when the row, column, or physical page attributes of a field are updated.

User response

Correct the position attribute, or attributes, that causes the overlap.
CRRZM0494E
The copybook generation for this MFS file failed.

Messages for source code generation in Rational Developer for z Systems

The following messages pertain to generating source code in Rational Developer for z Systems.

CRRZP0001E
Container {0} does not exist.

Explanation

{0}
The name of a container
The specified container was not found.

User response

Create the specified container, or specify another container.

Messages for Common Access Repository Manager (CARMA) Endevor

The following messages pertain to Common Access Repository Manager (CARMA) Endevor in Rational Developer for z Systems.

CRRZR1001E
Unsupported editor input type.

Explanation

The input type is an unsupported type for the CA Endevor Package Editor. The Endevor Package Editor requires any custom editor to implement org.eclipse.ui.IStorageEditorInput.

User response

Change the input type to a type that is supported by the CA Endevor Package Editor. If you are working on a custom client, contact your client developer to investigate whether the package editor is implementing org.eclipse.ui.IStorageEditorInput.
CRRZR1002E
The Endevor Package Editor was unable to open the source for reading.

Explanation

The source file was not open and read successfully.

User response

In the client, close the file and try again. If the problem persists, restart the workbench.
CRRZR1003E
The Endevor Package Editor was unable to parse the source into valid SCL.

Explanation

The file is not valid SCL and cannot be opened by the CA Endevor Package Editor.

User response

If you believe that the file is valid SCL, open the file in the text editor by right-clicking the file and selecting Open With > Text Editor. Fix any errors before you open the files again in the Endevor Package Editor.
CRRZR1004E
The Endevor search failed. Ensure that you are connected to the host and that the host is running a current version.

Explanation

The Endevor search did not complete successfully.

System programmer response

Verify that the current version of the Endevor RAM is installed and running on the remote system.

User response

Verify that you are connected to the remote system. If the problem persists, contact the system programmer.

Messages for CICS Service Component Architecture (SCA)

The following messages pertain to the CICS Service Component Architecture (SCA) in Rational Developer for z Systems.

CRRZS1000E
An internal error occurred while parsing the source code for SCA references.

Explanation

This message indicates an unexpected error.

User response

Try the action again. If the error persists, contact IBM Software Support.
CRRZS1001W
A reference was found in the source code at line {0}, column {1} for which a name could not be determined.

Explanation

{0}
Line number
{1}
Column number
The New CICS Component Type wizard examines the program source and creates a component reference element for each occurrence of EXEC CICS INVOKE SERVICE or EXEC CICS INVOKE WEBSERVICE that is found. If the name of the service that is started by the EXEC CICS command cannot be determined because a data item is being used instead of a string literal, this warning is logged.

User response

Examine the EXEC CICS command at the specified line and column numbers in the program source to determine a correct name to use for the newly created component reference. After you determine the value, update the component reference name by using the Properties view.
CRRZS1002E
An error occurred while trying to download the default Application Deployment Manager attributes for RDO bundles.

Explanation

The default attributes for RDO bundles must be defined by your CICS system administrator.

User response

Verify with your CICS system administrator that the default attributes for RDO bundles are defined. This task is described in the topic about the CICS administrative utility in the chapter that explains the Application Deployment Manager in the Rational Developer for z Systems Host Configuration Guide.
CRRZS1003E
An error occurred while creating the bundle archive file. Deployment stopped.

Explanation

The resources in a bundle are packaged into an archive file for transfer to z/OS. After the transfer is complete, the archive is unpacked.

User response

Check the error log for more details, and try the action again. If the error persists, contact IBM Software Support.
CRRZS1004E
An error occurred while unpacking the bundle archive.

Explanation

The resources in a bundle are packaged into an archive file for transfer to z/OS. After the transfer is complete, the archive is unpacked.

User response

Review the results of the unpacking operation, check the error log for more details, and try the action again. If the error persists, contact IBM Software Support.
CRRZS1005E
An error occurred while deleting the contents of the remote folder.

Explanation

You selected to delete the contents of the remote bundle before deployment; however, an error occurred.

User response

Verify that the remote folder exists and that the permissions are configured correctly, check the error log for more details, and try the action again. If the error persists, contact IBM Software Support.
CRRZS1006E
An error occurred while transferring the bundle archive to the remote system.

Explanation

The resources in a bundle are packaged into an archive file for transfer to z/OS.

User response

Verify that a connection to the remote system exists, that the remote folder exists, and that the permissions are configured correctly.
CRRZS1007W
Unable to retrieve the complete results of the unpack operation from the remote shell.

Explanation

No response was received from the remote shell after the unpack operation for the archive file that contains the bundle resources.

User response

Verify that all the bundle resources exist in the remote folder.
CRRZS1008I
Review the results of the unpacking operation:

Explanation

The resources in a bundle are packaged into an archive file for transfer to z/OS. After the transfer is complete, the archive is unpacked.

User response

Review the results of the unpacking operation.
CRRZS1009E
An error occurred while validating the existence of the remote folder.

Explanation

The remote folder must exist before the bundle is transferred to z/OS.

User response

Verify that the remote folder exists and that the permissions are configured correctly, check the error log for more details, and try the action again. If the error persists, contact IBM Software Support.
CRRZS1010W
Unable to retrieve the complete results of the install BUNDLE resource operation.

Explanation

The attempt to verify the installation operation did not return a valid response.

User response

Verify that the BUNDLE resource was installed.
CRRZS1011E
The selected CICS system or region does not support BUNDLE resources.

Explanation

The selected CICS system or region does not support BUNDLE resources. BUNDLE resources are supported in CICS TS version 4.1 and later.

User response

Select a CICS system or region that supports BUNDLE resources.
CRRZS1012E
An internal error occurred while removing the CICS Service Component Architecture 1.0 facet.

Explanation

This message indicates an unexpected error.

User response

Try the action again. If the error persists, contact IBM Software Support.
CRRZS1013E
An internal error occurred while adding the CICS Service Component Architecture 1.0 facet.

Explanation

This message indicates an unexpected error.

User response

Try the action again. If the error persists, contact IBM Software Support.
CRRZS2001E
The "Component type" attribute defined in the CICS Implementation properties of the component contains a path to a file that does not exist.

Explanation

Either the path name is incorrect or the file is missing.

User response

Correct the path name or create the file that is referenced.
CRRZS2002E
The "Bind file" attribute defined in the CICS Binding properties contains a path to a file that does not exist.

Explanation

Either the path name is incorrect or the file is missing.

User response

Correct the path name or create an appropriate file at the specified location.
CRRZS2003E
The "Call type" attribute defined in the CICS Implementation properties of the component contains an invalid value.

Explanation

The value of the call type attribute must be COMMAREA or CHANNEL.

User response

Specify a value of either COMMAREA or CHANNEL.
CRRZS2004E
The "Program" attribute defined in the CICS Implementation properties of the component is blank.

Explanation

You must specify a program attribute in a component's CICS Implementation properties.

User response

Specify a program attribute in a component's CICS Implementation properties.
CRRZS2005W
A policy set has been defined for the CICS SCA 1.0 resource.

Explanation

Policy sets are not supported for CICS SCA 1.0 resources.

User response

Remove the policy set.
CRRZS2006W
An intent has been defined for the CICS SCA 1.0 resource.

Explanation

An intent is defined for the CICS SCA 1.0 resource.

User response

Remove the intent from the CICS SCA 1.0 resources.
CRRZS2007W
A property has been defined for the CICS SCA 1.0 resource.

Explanation

Properties are not supported for CICS SCA 1.0 resources.

User response

Remove the property from the CICS SCA 1.0 resources.
CRRZS3001W
File {0} already exists. To confirm overwriting of {1} to project {2}, select Yes. To use the existing file {0}, select No.

Explanation

{0}
The name of a file
{1}
The name of a file
{2}
The name of an MVS subproject
The specified file exists in a particular project.

User response

To overwrite the file in the project, click Yes. To keep the existing file, click No.
CRRZS3002E
Errors exist in the project. Proceed with deployment?

Explanation

The project contains errors.

User response

To deploy the project anyway, click Yes. Otherwise, click No.
CRRZS3003W
Warnings exist in the project. Proceed with deployment?

Explanation

The project contains warnings.

User response

To deploy the project anyway, click Yes. Otherwise, click No.

Messages for the z/OS Automated Unit Testing Framework (zUnit)

The following messages pertain to the z/OS Automated Unit Testing Framework (zUnit) in Rational Developer for z Systems.

CRRZT0001E
The default template file '{0}' was not found.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot locate the template file that is needed to generate a test case.
{0}
The name of a zUnit test-case wizard template file that is used to generate a COBOL or PL/I test case.

User response

Ensure that the zUnit feature is installed correctly. The default location for the template file is com.ibm.etools.zunit.gen\template. Verify that the template file is in the default directory, and try to generate the test case again.
CRRZT0002E
An I/O error occurred while closing a file.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot save the generated test-case file.

User response

Ensure that you have write access to the target for the test-case program, and try the operation again.
CRRZT0003E
An I/O error occurred while creating the file URL.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot create the generated test-case file.

User response

Ensure that you have access to the target for the test-case program, and try the operation again.
CRRZT0004E
An I/O error occurred while opening a file.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot open the generated test-case file.

User response

Ensure that you have access to the target for the test-case program, and try the operation again.
CRRZT0005E
An I/O error occurred while parsing the template file.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot correctly load the template file that is required to generate a test-case program.

User response

Ensure that the zUnit feature is correctly installed, and try the operation again.
CRRZT0006E
An I/O error occurred while writing to a file.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot write to the generated test-case file.

User response

Ensure that you have write access to the target for the test-case program, and try the operation again.
CRRZT0007E
An attempt to create a directory failed.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot create the directory that is specified in the File container field of the wizard.

User response

Ensure that you have write access to the target for the test-case program, and try the operation again.
CRRZT0008E
The test parameter is not defined.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard generated an internal error.

User response

Contact IBM Software Support.
CRRZT0009E
The template file '{0}' was not found.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot locate the template file that is required to generate a test case.
{0}
The name of a zUnit test-case wizard template file that is used to generate a COBOL or PL/I test case.

User response

Ensure that the zUnit feature is installed correctly. The default location for the template file is com.ibm.etools.zunit.gen\template.
CRRZT0010E
The template file caused a formatting error.

Explanation

The test-case program that the z/OS Automated Unit Testing Framework (zUnit) test-case wizard generated by using the default template file has formatting errors.

User response

Ensure that the zUnit feature is correctly installed, and try the operation again.
CRRZT0011E
The <{0}> tag was not found in the template file.

Explanation

One of the tags that are needed to correctly generate a test case program was not found in the default template file.
{0}
A tag that is required to correctly generate a test-case program.

User response

Ensure that the zUnit feature is correctly installed, and try the operation again.
CRRZT0012E
The file creation operation failed.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot create the generated test-case file.

User response

Ensure that you have write access to the target for the test-case program, and try the operation again.
CRRZT0013E
The member creation operation failed.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot create the data set member for the generated test-case file.

User response

Ensure that you have write access to the target for the test-case program, and try the operation again.
CRRZT0014E
The remote resource properties update failed.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot update the properties of the target data set for the generated test-case file.

User response

Ensure that you have write access to the target for the test-case program, and try the operation again.
CRRZT0015E
The test case source generation failed.

Explanation

This error occurs when the z/OS Automated Unit Testing Framework (zUnit) test-case source-code generator throws an exception. The content of the exception is in the detail area of the error window.

User response

For more information about responding to this error, see the error details.
CRRZT0016E
The member lock operation failed.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot obtain a lock on the data set member for the generated test-case file.

User response

Ensure that the member is not open in another program or locked by another user, and try the operation again.
CRRZT0017E
An exception occurred while updating the remote resource properties.

Explanation

This error can occur when a remote member is modified with Interactive System Productivity Facility (ISPF) so that the local cache is out-of-date. The Rational Developer for z Systems client fails to update a property of the local cache that is overwritten.

User response

Update or delete the local cache, and try the operation again.
CRRZT0018I
No additional information is available for ({0}).

Explanation

This message indicates that a hyperlink on the user interface was clicked and the system has no information to display for that item.
{0}
Represents a hyperlink on the z/OS Automated Unit Testing Framework Runner Configuration or Runner Results user interface.

User response

No action is required.
CRRZT0019E
An error occurred while saving the configuration.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) test runner configuration editor cannot save the configuration file.

User response

Ensure that you have write access to the target for the configuration file, and try the operation again.
CRRZT0020E
The Save As operation failed.

Explanation

By clicking File > Save As in the z/OS Automated Unit Testing Framework (zUnit) Runner Configuration editor and Runner Results editor, you can create a copy of the current file on a local or remote file system. Loss of connectivity, storage constraints, or other conditions can cause the copy operation to fail. This message reports other messages that are received from the local or remote file system when the operation fails.

User response

This message is normally accompanied by messages from the local or remote file system. Use the accompanying messages to determine the appropriate corrective actions. For example, when you attempt a Save As operation that targets a z/OS partitioned data set that is out of space, the CRZZI0197E and CRZZI0198E messages might be received. For help with resolving the problem, see the documentation for the accompanying messages.
CRRZT0021E
An error occurred while loading the z/OS Automated Unit Testing Framework (zUnit) property group category. Verify that the zUnit category is enabled in the property group associated with resource {0}.

Explanation

{0}
The name of the file or load library for which a Run As Test Case or Run All As Test Case action was requested.
The Run As Test Case and Run All As Test Case actions require certain options to be set in a property group. The property group that is associated with the resource does not include the z/OS Automated Unit Testing Framework (zUnit) category.

User response

  1. Do one of these actions:
    • Associate a property group that includes the zUnit category.
    • Edit the property group that is associated with the resource and enable the zUnit category.
  2. Verify or update the values that are specified in the zUnit category of the property group.
  3. Try the Run As Test Case or Run All As Test Case action again.
CRRZT0022E
The error "{0}" was received from the JES job monitor on remote system {1}.

Explanation

{0}
An error message that is returned by the Job Entry Subsystem (JES) job monitor.
{1}
The name of the remote system on which the job was submitted.
When you request a test case, the z/OS Automated Unit Testing Framework (zUnit) submits a JES job to run the test runner on the remote system. zUnit then polls JES at varying intervals, 1-6 seconds, to check whether the job finished. If a general communication error occurs with the JES job monitor during job submission or polling, the zUnit Eclipse task is canceled and this message is issued.

User response

If the error message returned by the JES job monitor indicates a communication error, such as java.net.SocketException: Connection reset, verify that the JES job monitor is running on the remote system.
To verify that you are connected to JES on the remote system:
  1. In the Remote Systems view, expand the name of the remote system that is shown in the message.
  2. Select JES.
  3. Verify the connection status in the Properties view.
  4. If the Connection field displays No, connect to the JES subsystem.
  5. If you cannot connect to JES, contact your systems administrator.
CRRZT0023E
JES job submission failed. Verify that the JCL property group category is enabled for resource {0} and that the specified JCL job card is valid.

Explanation

{0}
The name of the file or load library for which a Run As Test Case or Run All As Test Case action was requested.
When you request a test case, the z/OS Automated Unit Testing Framework (zUnit) submits a Job Entry Subsystem (JES) job that runs on the remote system. The job submission failed. The most common cause is a bad or missing JOB card.

User response

To verify that the property group that is associated with the resource includes the zUnit category, edit the property group, open the Categories page, and verify that z/OS Automated Unit Testing Framework (zUnit) is selected.

To edit the job card, open the JCL page of the property group and edit the job card in the JCL job card field.

CRRZT0024E
Failed to retrieve JES job with job ID {0} on remote system {1}. The job might be purged.

Explanation

{0}
The job ID of the Job entry Subsystem (JES) job that was submitted by the z/OS Automated Unit Testing Framework (zUnit).
{1}
The name of the remote system on which the job was submitted.
When you request a test case, zUnit submits a JES job to run the test runner on the remote system. zUnit then polls JES at varying intervals, 1-6 seconds, to check whether the job finished. The job can no longer be found on the remote system. It might be purged by another user or process.

User response

Inspect the z/OS system log (SYSLOG) or JES job monitor log on the remote system to determine why the JES job was purged.
CRRZT0025W
The action was canceled on the workstation only. It might still be necessary to purge JES job with job name {0} and job ID {1} on remote system {2}.

Explanation

{0}
The name of the job that was submitted by the test runner.
{1}
The ID of the job that was submitted by the test runner.
{2}
The name of the remote system on which the job was submitted.
When you request a test case, the z/OS Automated Unit Testing Framework (zUnit) submits a JES job that runs on the remote system. If you cancel the test case operation either by clicking Cancel on the job submission window or by clicking Stop on the Progress view and the JES job is already submitted to the remote system, this warning message is displayed.

User response

To cancel or purge the job on the remote system:
  1. In the Remote Systems view, retrieve the job that is identified in the message.
  2. Select the job name.
  3. Right-click and select Cancel or Purge.
CRRZT0026E
The error "{0}" was received while attempting to upload runner configuration file {1} to remote system {2}.

Explanation

{0}
An error message.
{1}
The name of a test runner configuration file.
{2}
The name of the remote system to which the configuration file is uploaded.
While you run a test case, the z/OS Automated Unit Testing Framework (zUnit) generates a configuration file and uploads it to the remote system. If the upload fails, this message reports the message that is received from the remote system.

User response

Verify that the MVS data set or z/OS UNIX folder that is specified in the Runner configuration destination container field of the property group has sufficient space and that you have write access to it.
CRRZT0027E
Runner result file {0} does not exist on remote system {1}.

Explanation

{0}
The name of a z/OS Automated Unit Testing Framework (zUnit) test runner result file.
{1}
The name of the remote system on which the test runner job was submitted.
When you run a zUnit test case, the test runner generates a test result file and opens it in the Runner Results viewer. The test result file was not found on the remote system.

User response

Verify that the MVS data set or z/OS UNIX folder that is specified on the zUnit page of the property group exists on the remote system, that it has sufficient space, and that you have write access to it. Verify that no other process or user is concurrently using the MVS data set or z/OS UNIX folder.
CRRZT0028E
JES job with job name {0} and job ID {1} failed on remote system {2}. Return information: {3}.

Explanation

{0}
The name of the job that was submitted to the remote system.
{1}
The ID of the job that was submitted to the remote system.
{2}
The name of the remote system.
{3}
Information that is returned from the Job entry Subsystem (JES) about the job.
When you run a z/OS Automated Unit Testing Framework (zUnit) test case, zUnit submits a JES job that runs on the remote system and polls JES until the job finishes. If a JES job fails, this error is raised and the high-level cause is given in the return information: JCLERROR, ABENDED, CANCELED, or SECERROR.

User response

To diagnose the failed job, inspect the return information and the output of the job on the remote system. If the return information is JCLERROR or SECERROR, verify that the value that is specified in JCL job card on the JCL Job Card and Data Set page of the property group category is correct and specifies user credentials that are required by your site.
CRRZT0029E
The test runner encountered a severe error RC={0}. Refer to JES job with job name {1} and job ID {2} for more details.

Explanation

{0}
The Job Entry Subsystem (JES) job return code.
{1}
The name of the job that was submitted to the remote system.
{2}
The ID of the job that was submitted to the remote system.
When you request a test case, the z/OS Automated Unit Testing Framework (zUnit) submits a JES job that runs on the remote system. The test runner encountered a severe problem and the JES job ended with a return code higher than U0008.

User response

Inspect the JES job to determine the cause of the error. Search for messages that begin with the prefix AZU, which are issued by the test runner, for example AZU0006S.

By default, the test runner does not generate a Language Environment memory dump if it can consume the exception that caused the severe error. To cause a limited memory dump to be generated along with detailed English-only tracing, select the Enable runner trace output option in the zUnit property group category.

If the test runner generated a result file, discard the file because the test results are not reliable.

CRRZT0030E
The runner result file {0} on remote system {1} was not generated by this instance of action {2}.

Explanation

{0}
The name of a z/OS Automated Unit Testing Framework (zUnit) test runner result file.
{1}
The name of the remote system on which the test runner job was submitted.
{2}
The name of the zUnit action that started the test runner job.
When you run a test case by using the Run As Test Case or Run All As Test Case action, zUnit generates a runner configuration file and starts an Eclipse task that submits the test runner job. A unique ID is included in the runner configuration file. This ID is also included in the runner result file for the job. zUnit verifies that the runner configuration file and the runner result file are a matched pair because the runner result file is not created by the test runner until the run finishes. To ensure that the runner configuration file and runner result file are a matched pair, zUnit saves the value of the runner configuration ID attribute before it uploads the runner configuration file to the remote system. When zUnit opens the runner result file, it compares the value of the runner result ID attribute to the value of the runner configuration ID attribute. If the IDs do not match, the zUnit Eclipse task is canceled.

This error most likely occurs when multiple Run As Test Case or Run All As Test Case actions are started concurrently and the names of the runner result files for each task are not unique.

User response

To prevent this error, specify unique runner result file names for each concurrent action instance, for example USER.AZURES(RUN01) and USER.AZURES(RUN02) or /u/zunit/result/run01.azures and /u/zunit/result/run02.azures.
CRRZT0031E
{0} of {1} does not match parameter {2}

Explanation

{0}
A parameter element in a test data XML file.
{1}
The name of the test data XML file.
{2}
A program parameter.
The New COBOL z/OS Automated Unit Testing Framework (zUnit) Test Case Template wizard cannot import the {0} element in the {1} test data file.

Programmer response

Ensure that the test data XML file was generated from the test data schema XSD file of the specified program parameter.
CRRZT0032E
The valid range of a repeating group or repeating item was exceeded while processing {0} of {1}.

Explanation

{0}
An element in a test data XML file.
{1}
A test data XML file.
The New COBOL z/OS Automated Unit Testing Framework (zUnit) Test Case Template wizard cannot import all elements of a test data file.

Programmer response

Ensure that the repeating elements in the test data XML file are specified correctly.
CRRZT0033E
Grammar error:

Explanation

TheEnterprise COBOL zUnit Test Data Schema wizard cannot identify parameter information to generate a test data schema XSD file. The wizard uses the COBOL importer to parse the source file. This message includes error information from the COBOL importer.

Programmer response

Look up the COBOL importer error message and correct the problem in the COBOL source file.
CRRZT0034E
{0} is not defined correctly in {1}. No items were processed.

Explanation

{0}
An element in a test data XML file.
{1}
The name of a test data XML file.
The New COBOL z/OS Automated Unit Testing Framework (zUnit) Test Case Template wizard cannot import the test data XML file.

Programmer response

Ensure that the test data XML file includes a &lt;Record> element.
CRRZT0035E
COBOL parser error {0}

Explanation

{0}
A COBOL parser error message.
The New COBOL z/OS Automated Unit Testing Framework (zUnit) Test Case Template wizard cannot identify parameters of the COBOL source file.

Programmer response

Ensure that the COBOL source file is free of compiler errors.
CRRZT0036E
An I/O error occurred while parsing {0}.

Explanation

{0}
The name of a COBOL source file or a test data XML file.
The New COBOL z/OS Automated Unit Testing Framework (zUnit) Test Case Template wizard cannot parse a COBOL source file or a test data XML file because of an I/O error.

Programmer response

Ensure that you have access to the file and try the operation again.
CRRZT0037E
The {0} file cannot be parsed. The file might contain syntax errors.

Explanation

{0}
A COBOL source file.
The New COBOL z/OS Automated Unit Testing Framework (zUnit) Test Case Template wizard cannot parse the target source file.

Programmer response

Ensure that the test target source is free of compiler errors.
CRRZT0038E
A parser configuration error occurred while parsing {0}.

Explanation

{0}
A test data XML file.
The New COBOL z/OS Automated Unit Testing Framework (zUnit) Test Case Template wizard cannot import the test data XML file.

Programmer response

Ensure that the zUnit feature is installed correctly and try the operation again.
CRRZT0039E
An SAX error occurred while parsing {0}.

Explanation

{0}
A test data XML file.
The New COBOL z/OS Automated Unit Testing Framework (zUnit) Test Case Template wizard cannot import the test data XML file.

Programmer response

Ensure that the test data XML file is well-formed.
CRRZT0040E
{0} language property "{1}" is invalid or missing.

Explanation

{0}
A COBOL source file.
{1}
A language property.
The Enterprise COBOL zUnit Test Data Schema wizard cannot load the language model from the test target source with the specified option.

Programmer response

Ensure that the zUnit feature is installed correctly and try the operation again.
CRRZT0041E
The model could not be read from {0}, exception [{1}].

Explanation

{0}
a COBOL source file.
{1}
An exception message.
The Enterprise COBOL zUnit Test Data Schema wizard cannot load the language model from the test target source.

Programmer response

Ensure that the test target source file does not contain syntax errors.
CRRZT0042E
Types cannot be imported from {0}.

Explanation

{0}
A COBOL source file.
The Enterprise COBOL zUnit Test Data Schema wizard cannot load the language model from the test target source file. No parameter is identified.

Programmer response

Ensure that parameters are defined in the program entry or subprogram call of the test target source file.
CRRZT0043E
This XSD type name already exists.

Explanation

The Enterprise COBOL zUnit Test Data Schema wizard cannot generate a test data schema file from the test target source file.

Programmer response

Ensure that the test target source file is free of compiler errors.
CRRZT0044E
Non unique items "{0}" found while importing.

Explanation

{0}
A data item.
The Enterprise COBOL zUnit Test Data Schema wizard cannot generate a test data schema file from the test target source.

Programmer response

Change name of the items that are listed in the message so that each data item can be identified by unique reference ID.
CRRZT0045E
Record index {0} is specified in multiple data structures {1}.

Explanation

{0}
A record index.
{1}
A data structure.
A duplicate record index is specified in a data structure.

User response

Ensure the test data XML file does not contain duplicate record indexes.
CRRZT0046E
An I/O error occurred while loading {0}.

Explanation

{0}
A test case generation configuration file.
During a z/OS Automated Unit Testing Framework (zUnit) operation, an I/O error occurred while loading the test case generation configuration file.

User response

Ensure that the test case generation configuration file exists in the partitioned data set that is specified in the property group. If the file is a member of a different partitioned data set, update the data set name in the Test case generation configuration file field of the property group that is associated with the source program file.
CRRZT0047E
An I/O error occurred while saving {0}.

Explanation

{0}
A test case generation configuration file.
During a z/OS Automated Unit Testing Framework (zUnit) operation, an I/O error occurred while saving the test case generation configuration file.

User response

Ensure that the test case generation configuration file exists in the partitioned data set that is specified in the property group. If the file is a member of a different partitioned data set, update the data set name in the Test case generation configuration file field of the property group that is associated with the source program file.
CRRZT0048E
Attribute "{0}" is not specified in Element "{1}".

Explanation

{0}
An XML attribute name used in the test case generation configuration file.
{1}
An XML element name used in the test case generation configuration file.
The attribute that is specified in the message cannot be found in the element. The format of the test case generation configuration file is not valid.

User response

If the test case generation configuration file was edited manually, delete it and request the Generate Test Case action again.
CRRZT0049E
Element "{0}" is not specified in the test data generation configuration file.

Explanation

{0}
An XML element name used in the test case generation configuration file.
The XML element cannot be found in the test case generation configuration file. The format of the test case generation configuration File is not valid.

User response

If the test case generation configuration file was edited manually, delete it and request the Generate Test Case action again.
CRRZT0050E
No entry is specified.

Explanation

The test case generation configuration file does not contain a test entry. The format of the test case generation configuration file is not valid.

User response

If the test case generation configuration file was edited manually, delete it and request the Generate Test Case action again.
CRRZT0051E
File "{0}" could not be read.

Explanation

{0}
A test case generation configuration file.
The test case generation configuration file was not found in the path specified in the property group.

User response

Specify a different partitioned data set in the property group, or ensure that the correct property group is associated with the source program file.
CRRZT0052E
Invalid element "{0}" was found while parsing {1}.

Explanation

{0}
An XML element name used in the test case generation configuration file.
{1}
The test case generation configuration file.
The test case generation configuration file contains an invalid element. The format of the test case generation configuration file is invalid.

User response

If the test case generation configuration file was edited manually, delete it and request the Generate Test Case action again.
CRRZT0053E
A method received an invalid identifier: "{0}".

Explanation

{0}
A general identifier used in z/OS Automated Unit Testing Framework (zUnit).
The identifier is not a valid zUnit object. The format of the test case generation configuration file is invalid.

User response

If the test case generation configuration file was edited manually, delete it and request the Generate Test Case action again.
CRRZT0054E
A method received a null or invalid argument.

Explanation

An invalid argument was specified when z/OS Automated Unit Testing Framework (zUnit) was started.

User response

Ensure that command arguments are specified with the correct format.
CRRZT0055E
"{0}" is specified as a remote resource.

Explanation

{0}
A file name.
The remote attribute is set for the file in the test case generation configuration file. The format of the test case generation configuration file is not valid.

User response

If the test case generation configuration file was edited manually, delete it and request the Generate Test Case action again.
CRRZT0056E
The converter could not be generated because no element-to-data-name mappings exist. Verify that the source file is syntactically correct.

Explanation

The converter generation encountered an internal error.

User response

See the log file for more information.
CRRZT0057E
An error occurred while writing to a file. See the log file in the current workspace for details.

Explanation

An error occurred while generating the converter program to import file data.

User response

See the log file in the current workspace for details.
CRRZT0058E
Unicode data items could not be processed because the selected out-bound XML code page is not Unicode.

Explanation

An internal error occurred while generating the converter program to import file data.

User response

See the log file in the current workspace for details.
CRRZT0059E
The in-bound converter could not be generated because an internal error occurred. See the log file in the current workspace for details.

Explanation

An internal error occurred while generating the converter program to import file data.

User response

See the log file in the current workspace for details.
CRRZT0060E
The converter driver could not be generated because an internal error occurred. See the log file in the current workspace for details.

Explanation

An internal error occurred while generating the converter program to import file data.

User response

See the log file in the current workspace for details.
CRRZT0061E
An error occurred while creating or writing to a file. Check local and remote file system connectivity and permissions. The write failed for file "{0}".

Explanation

{0}
The file name of a converter program that imports file data.
An write error occurred while generating the converter program to import file data.

User response

Check local and remote file system connectivity and permissions.
CRRZT0062E
DBCS data items could not be processed because DISPLAY-1 usage was not specified.

Explanation

A DBCS data item was imported to the data item without DISPLAY-1 usage.

User response

Ensure that the imported file matches the specified file structure.
CRRZT0063E
The import of language types failed because of an internal error. See the log file in the current workspace.

Explanation

An internal error occurred while importing file data.

User response

See the log file in the current workspace for details.
CRRZT0064E
Unsupported data types were selected. See the log file in the current workspace for details.

Explanation

The file structure contains unsupported data types.

User response

See the log file in the current workspace for details.
CRRZT0065E
The length of an XML document that can be derived from the out-bound data structure exceeds 16,777,210 bytes.

Explanation

The size of imported file data exceeded the limit.

User response

Remove unnecessary records from the file so that import action can work correctly. Try the operation again.
CRRZT0066E
The length of an XML document that can be derived from the out-bound data structure exceeds 33,554,420 bytes.

Explanation

The size of imported file data exceeded the limit.

User response

Remove unnecessary records from the file so that import action can work correctly. Try the operation again.
CRRZT0067E
The converter could not be generated because an internal error occurred. See the log file in the current workspace for details.

Explanation

An internal error occurred while generating the converter program to import file data.

User response

See the log file in the current workspace for details.
CRRZT0068E
The converter could not be generated because an attempt to get the Unicode representation of a string failed.

Explanation

An internal error occurred while generating the converter program to import file data.

User response

See the log file in the current workspace for details.
CRRZT0069E
DBCS data items could not be processed because the selected out-bound XML code page is not Unicode.

Explanation

An internal error occurred while generating the converter program to import file data.

User response

See the log file in the current workspace for details.
CRRZT0075W
The test case is not generated. Before you can build the test case, you must generate the test case.

Explanation

A Build Test Case action was requested for a source program, but no test case was generated for the program.

User response

Use the Generate Test Case menu item to generate a test case for the source file.
CRRZT0076E
The remote container "{0}" for the test case generation configuration file is not found.

Explanation

{0}
A partitioned data set name.
The partitioned data set that is specified in the Test case generation configuration file field of the property group does not exist.

User response

Either allocate the partitioned data set that is specified in the property group, or specify a partitioned data set that exists on the remote system.
CRRZT0077E
The remote container "{0}" is not found

Explanation

{0}
A partitioned data set name.
The partitioned data set does not exist.

User response

Either allocate the partitioned data set or update the property group or the generation configuration file to specify a partitioned data set that exists on the remote system.
CRRZT0078E
Internal error. The remote container name is not specified

Explanation

An internal error occurred.

User response

Contact your IBM technical support representative.
CRRZT0079E
Internal error. The file name is not specified

Explanation

An internal error occurred.

User response

Contact your IBM technical support representative.
CRRZT0080E
The test case load module "{0}" is not found.

Explanation

{0}
The name of a test case load module.
The Run Test Case action was requested for a source program, but no test case load module exists for the source file.

User response

Before you can issue the Run Test Case action for a source program, you must generate a test case for the source file and build the test case load module.
CRRZT0081W
The test case is not built. Before you can run the load module as a test case, you must generate and build a test case.

Explanation

The Run Test Case action was requested for a source program, but no test case load module exists for the source file.

User response

Before you can issue the Run Test Case action for a source program, you must generate a test case for the source file and build the test case load module.
CRRZT0082E
An error occurred while loading the z/OS Automated Unit Testing Framework (zUnit) property group category. Verify that the zUnit category is enabled in the property group associated with resource {0}.

Explanation

{0}
A partitioned data set member name.
A zUnit action was requested, but the property group that is associated with the selected member does not have the zUnit category enabled.

User response

Do one of these steps:
  • Associate a property group that has the zUnit category enabled.
  • Edit the property group that is associated with the resource and select the z/OS Automated Unit Testing Framework (zUnit) category on the Categories page.
CRRZT0083E
JES job with job name {0} and job ID {1} failed on remote system {2}. Return code: {3}.

Explanation

{0}
The job name of a JES job that was submitted for a zUnit operation.
{1}
The job ID of a JES job that was submitted for a zUnit operation.
{2}
The name of the remote system to which the job was submitted.
{3}
The return code for the submitted job.
The z/OS Automated Unit Testing Framework (zUnit) processes Generate Test Case, Build Test Case, and Run Test Case operations by submitting jobs to JES. A submitted job failed to run successfully.

User response

To see the job output, open the My Jobs filter in the JES subsystem of the Remote Systems view.
CRRZT0084E
JES job with job name {0} and job ID {1} failed on remote system {2}. Return information: {3}.

Explanation

{0}
The job name of a JES job that was submitted for a zUnit operation.
{1}
The job ID of a JES job that was submitted for a zUnit operation.
{2}
The name of the remote system to which the job was submitted.
{3}
Return information for the submitted job.
The z/OS Automated Unit Testing Framework (zUnit) processes Generate Test Case, Build Test Case, and Run Test Case operations by submitting jobs to JES. A submitted job failed to run successfully.

User response

To see the job output, open the My Jobs filter in the JES subsystem of the Remote Systems view.
CRRZT0085E
Failed to retrieve JES job with job ID {0} on remote system {1}. The job might be purged.

Explanation

{0}
The job ID of a JES job that was submitted for a zUnit operation.
{1}
The name of the remote system to which the job was submitted.

User response

To see the status of jobs that were submitted to JES, open the My Jobs filter in the JES subsystem of the Remote Systems view.
CRRZT0086E
JES job submission failed. Verify that the JCL property group category is enabled for resource {0} and that the specified JCL job card is valid.

Explanation

{0}
A partitioned data set member name.
The z/OS Automated Unit Testing Framework (zUnit) processes Generate Test Case, Build Test Case, and Run Test Case operations by submitting jobs to JES. A job could not be submitted to JES.

User response

Do these steps:
  1. Edit the property group that is associated with the resource.
  2. On the Categories page of the property group, select JCL Job Card and Data Set.
  3. Ensure that the JCL job card specified on the JCL page of the property group is valid for your site.
To obtain a valid JCL job card, ask your systems administrator.
CRRZT0087E
An error occurred while getting include files.

Explanation

While processing a Generate Test Case operation, the z/OS Automated Unit Testing Framework (zUnit) parses the source program to obtain information from include or copybook files. zUnit could not process the include files.

User response

Ensure that include files for the source program are accessible. Verify that the SYSLIB setting in the property group that is associated with the source program points to the correct include libraries.
CRRZT0088E
The test case is inconsistent. Before you can build the test case, you must generate the test case again.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) parses the source program to generate a test case file. During a Build Test Case operation, zUnit detected that the source program was changed after the test case file was generated.

User response

Select the source file and request the Generate Test Case action to generate the test case file again.
CRRZT0089E
Internal error. The test case container name is not found in the generation configuration file.

Explanation

The generation configuration file stores test case program information in an OutputProgramArray tag, as in the following example:
<OutputProgramArray fileContainer="<HLQ>.ZUNIT.COBOL">
    <OutputProgram fileName="TSAMP01" programType="Driver"/>
</OutputProgramArray> 
This error occurs when the fileContainer attribute is empty ("").

User response

Generate test case again. If the error occurs again, contact your IBM technical support representative.
CRRZT0090E
Test data {0} is not based on test data layout {1}.

Explanation

{0}
The name of a test data file.
{1}
The name of a test data layout file.
The test data file and the test data layout file are inconsistent. The AZUGEN, AZUTDT, or AZUSCH files might be corrupt.

User response

To generate a new test data generation, test data, and test data layout file, update the source program file. Then, select the updated source program and request the Generate Test Case action.
CRRZT0091E
Internal error. The test case file name is not found in the generation configuration file.

Explanation

The generation configuration file stores test case program information in an OutputProgramArray tag, as in the following example:
<OutputProgramArray fileContainer="<HLQ>.ZUNIT.COBOL">
    <OutputProgram fileName="TSAMP01" programType="Driver"/>
</OutputProgramArray> 
This error occurs when the fileName attribute is empty ("").

User response

Generate test case again. If the error occurs again, contact your IBM technical support representative.
CRRZT0092E
The container "{0}" for the test case generation configuration file does not have a record format of VB or VBA.

Explanation

{0}
The name of a partitioned data set.
The partitioned data set that contains test case generation configuration files, must have a record format (RECFM) of VB or VBA.

User response

Allocate a partitioned data set with record format VB or VBA and specify the data set name in the Test case generation configuration file field of the property group.
CRRZT0093E
The stub program name ''{0}'' is invalid.

Explanation

{0}
The name of a stub program.
An internal error occurred.

User response

Contact your IBM technical support representative.
CRRZT0094E
The remote member "{0}" does not exist.

Explanation

{0}
A partitioned data set member name.
A partitioned data set member that the z/OS Automated Unit Testing Framework (zUnit) must access to process an operation does not exist.

User response

Create the data set member and try the operation again.
CRRZT0095E
An error occurred while running the converter. See the JES job output for details.

Explanation

during an Import Test Data operation, an error occurred while running the converter.

User response

For more information, see the JES job output or the log file.
CRRZT0096W
The test target source program is not built. Before you can build the test case, you must build the test target source program and any stub programs that were generated.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) requires that load modules doe the source program and any stub programs that were generated by zUnit be generated before it can build a test case program.

User response

Before building a test case program, generate and submit JCL to compile and link the source program and the generated stub programs.
CRRZT0097E
Cannot read a data file: {0}

Explanation

{0}
The name of a test data XML file.
A test data XML file is corrupt.

User response

Verify that the partitioned data set member containing the test data XML is valid. If the member is valid, close the Test Entry Data Editor and reopen it to download the member again. If the member is not valid, remove the test entry that uses the corrupt test data file before opening the editor.
CRRZT0098E
Cannot read a layout file: {0}

Explanation

{0}
The name of a test data layout file.
A test entry layout file is corrupt.

User response

Update test target program source, and reopen the Test Entry Data Editor. Test entry layout files are recreated when you open the Test entry Data Editor.
CRRZT0099E
The members of {0} are different from the members of {1}.

Explanation

{0}
The target to be given the assignment.
{1}
The source of the assignment.

User response

Verify that the assignment statement is valid.
CRRZT0100E
{0} is not valid. The target in a BY NAME assignment must be a structure.

Explanation

{0}
The target to be given the assignment.

User response

Correct the assignment statement.
CRRZT0101E
{0} is not declared in the program.

Explanation

{0}
The name of a variable.
Implicit declaration is not supported.

User response

Specify declare statement for {0}.
CRRZT0102E
PL/I parser error {0}

Explanation

{0}
Error messages from the PL/I parser.

User response

Complete a remote syntax check on the source program and verify that it has no compilation errors.
CRRZT0103E
This xsd type name already exists.

Explanation

Variables that have the same name as a parameter are not supported in zUnit.

User response

Check if the source has a variable with the same name as the parameter.
CRRZT0104E
The object of the array is not part of the selected record.

Explanation

The referred element cannot be identified in the source program.

User response

Check if the source has a variable with the same name.
CRRZT0105W
The test case is not built. Before you can run code coverage for the load module, you must generate and build a test case.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) > Code Coverage menu option was requested for a test target source file, but a test case was not generated and built.

User response

Generate and build a test case program for the test target source and then try the Code Coverage action again.
CRRZT0106W
The test case is not built. Before you can debug the load module, you must generate and build a test case.

Explanation

The z/OS Automated Unit Testing Framework (zUnit) > Debug menu option was requested for a test target source file, but a test case was not generated and built.

User response

Generate and build a test case program for the test target source and then try the Debug action again.
CRRZT0107E
The source program language is different from the language used in the previous test case generation configuration file.

Explanation

This error can occur when two different test target source programs, one written in COBOL and one written in PL/I, have the same file name and the property group that is associated with each program points to the same location for the test case generation configuration file. For example, if you have two files named ANAGRAM.cbl and ANAGRAM.pli, and the property group defines the location for the test case generation configuration file as <HLQ>.ZUNIT.GEN, then the z/OS Automated Unit Testing Framework (zUnit) attempts to create a test case generation configuration file named <HLQ>.ZUNIT.GEN(ANAGRAM.xml) for each source file. This situation creates the conflict described in this message.

User response

You can address this situation in any of these ways:
  • Define separate property groups for COBOL and PL/I files and point to different locations for the test case generation configuration file, such as <HLQ>.ZUNIT.COBOL.GEN and <HLQ>.ZUNIT.PLI.GEN.
  • Use unique names for COBOL and PL/I test target source files.
CRRZT0108E
An error occurred while loading the COBOL settings property group category. Verify that the COBOL settings category is enabled in the property group associated with resource {0}.

Explanation

{0}
A test target source file
While running a z/OS Automated Unit Testing Framework (zUnit) operation, the product could not load the COBOL settings for the test target source file.

User response

Verify that the property group that is associated with the test target source file has the COBOL category enabled and that it contains valid settings for COBOL programs.
CRRZT0109E
An error occurred while loading the PL/I settings property group category. Verify that the PL/I settings category is enabled in the property group associated with resource {0}.

Explanation

{0}
A test target source file
While running a z/OS Automated Unit Testing Framework (zUnit) operation, the product could not load the PL/I settings for the test target source file.

User response

Verify that the property group that is associated with the test target source file has the PL/I category enabled and that it contains valid settings for PL/I programs.
CRRZT0110E
An error occurred while loading the z/OS Automated Unit Testing Framework (zUnit) property group category for selecting a debugger. Verify that the zUnit category is enabled in the property group associated with resource {0}.

Explanation

{0}
A test target source file
While running a z/OS Automated Unit Testing Framework (zUnit) operation, the product could not load the runtime debugging settings for the test target source file.

User response

Verify that the property group that is associated with the test target source file has the Runtime Options category enabled and that it contains valid settings for the Debug page.
CRRZT0111E
An error occurred while refreshing from the test source program

Explanation

User response

CRRZT0112E
An error occurred while validating test data with schema. Specified test data expression is not supported: {0}

Explanation

{0}
Test data specified by the user.

User response

The data format is not supported. Correct the data in Test Entry Data Editor.
CRRZT0113E
A memory shortage occurred while creating data layouts

Explanation

User response

CRRZT0114E
An error occurred while uploading test case generation configuration file to remote container "{0}".

Explanation

{0}
A remote data set name.
The remote data set to which you are trying to save the test case generation configuration file is full.

User response

Either expand the data set or save the file to a different data set.
CRRZT0115E
An error occurred while uploading test case to remote container "{0}".

Explanation

{0}
A remote data set name.
The remote data set to which you are trying to save the test case file is full.

User response

Either expand the data set or save the file to a different data set.
CRRZT0116E
An error occurred while uploading test data to remote container "{0}".

Explanation

{0}
A remote data set name.
The remote data set to which you are trying to save the test data file is full.

User response

Either expand the data set or save the file to a different data set.
CRRZT0117E
An error occurred while uploading test data layout to remote container "{0}".

Explanation

{0}
A remote data set name.
The remote data set to which you are trying to save the test data layout file is full.

User response

Either expand the data set or save the file to a different data set.
CRRZT0118E
Remote syntax error found while checking dependencies. The source program must be compilation error-free.

Explanation

The source file contains syntax errors.

User response

Resolve all syntax errors and try the Generate Test Case action again.
CRRZT0119E
The specified data set name "{0}" is too long. Shorten the data set qualifier for error feedback in the property group.

Explanation

{0}
The data set name of the error feedback file.
The data set name of the error feedback file exceed length limitations.

User response

Edit the property group that is associated with the source file and specify a shorter high-level qualifier in the Data set qualifier for compiler errors field. Save the property group and try the Generate Test Case action again.

Messages for Code Review for COBOL and PL/I

These are the messages that pertain to Code Review for COBOL and Code Review for PL/I.

CRRZV0000E
The COBOL source file could not be closed: {0}. Error message: {1}

Explanation

{0}
File name
{1}
Exception message

User response

Verify that other program is using the COBOL source code file, and then try running the code review again.
CRRZV0001E
An error occurred during the parsing of the COBOL source file {0}. Error message: {1}

Explanation

{0}
File name
{1}
Exception message

User response

Verify that the COBOL source code file does not contain any syntax errors, and then try running the code review again.
CRRZV0002E
The backup of the launch configuration file failed: {0}. Error message: {1}

Explanation

{0}
File name
{1}
Exception message

User response

Verify that no other program is using the launch configuration file. Restart the product and accept the push-to-client updates if prompted.
CRRZV0003E
The launch configuration files could not be copied. Error message: {0}

Explanation

{0}
Exception message

User response

Verify that no other program is using the launch configuration files. Restart the product and accept any push-to-client updates if prompted.
CRRZV0004E
The export of the launch configuration files failed. Error message: {0}

Explanation

{0}
Exception message

User response

Verify that no other program is using the launch configuration files. Then try exporting the launch configuration files again.
CRRZV0005E
The launch configuration files could not be loaded. Error message: {0}

Explanation

{0}
Exception message

User response

Verify that no other program is using the launch configuration files. Restart the product and accept any push-to-client updates if prompted.
CRRZV0006E
An error occurred during the refreshing of the local workspace. Error message: {0}

Explanation

{0}
Exception message

User response

Verify that no other program is using files in the local workspace, then try running the code review again.
CRRZV0007E
The following launch configuration file could not be copied: {0} The copy destination is: {1} The error message is: {2}.

Explanation

{0}
File name
{1}
File name
{2}
Exception message

User response

Verify that no other program is using the launch configuration file. Restart the product and accept any push-to-client updates if prompted.
CRRZV0008E
A metadata collector plug-in could not be loaded. Error message: {0}

Explanation

{0}
Exception message

User response

Restart the product. If the problem persists, contact your system administrator.
CRRZV0009E
The following files contained syntax errors and were not processed.

Explanation

The code review program detected syntax errors in the specified COBOL source code files.

User response

  1. If you need more information about the error, see the Error Log view or the log file workspace\.metadata\.log, where workspace is the name of your workspace.
  2. Fix the syntax errors in the specified COBOL source files and then try running the code review again.
CRRZV0100E
The PL/I source file could not be closed: {0}. Error message: {1}

Explanation

{0}
Source file
{1}
Exception message

User response

Verify that no other program is using the PL/I source code file, and then try running the code review again.
CRRZV0101E
An error occurred during the parsing of the PL/I source file {0}. Error message: {1}

Explanation

{0}
PL/I source file
{1}
Exception message

User response

Verify that the PL/I source code file does not contain any syntax errors, and then try running the code review again.
CRRZV0201E
An error occurred during the translation of data to the Cobol Application Model: ({0})

Explanation

{0}
Exception message

User response

  1. Determine whether the failing program fragment contains one of the documented limitations of the COBOL Application Model API. For more information see the technote "The COBOL Application Model (CAM) API in Code Review for COBOL: Limitations in Version 8.5.0.1" at http://www.ibm.com/support/docview.wss?uid=swg21598204.
  2. If the fragment does not contain a documented limitation, and if the problem persists, contact your system administrator.
CRRZV0202E
An error occurred during the translation of the environment division to the Cobol Application Model: ({0})

Explanation

{0}
Exception message

User response

  1. Determine whether the failing program fragment contains one of the documented limitations of the COBOL Application Model API. For more information see the technote "The COBOL Application Model (CAM) API in Code Review for COBOL: Limitations in Version 8.5.0.1" at http://www.ibm.com/support/docview.wss?uid=swg21598204.
  2. If the fragment does not contain a documented limitation, and if the problem persists, contact your system administrator.
CRRZV0203E
An error occurred during the translation of the procedure division to the Cobol Application Model: ({0})

Explanation

{0}
Exception message

User response

  1. Determine whether the failing program fragment contains one of the documented limitations of the COBOL Application Model API. For more information see the technote "The COBOL Application Model (CAM) API in Code Review for COBOL: Limitations in Version 8.5.0.1" at http://www.ibm.com/support/docview.wss?uid=swg21598204.
  2. If the fragment does not contain a documented limitation, and if the problem persists, contact your system administrator.
CRRZV0204E
An exception was thrown during the translation of the following statement to the Cobol Application Model: {0}

Explanation

{0}
Statement

User response

  1. Determine whether the failing program fragment contains one of the documented limitations of the COBOL Application Model API. For more information see the technote "The COBOL Application Model (CAM) API in Code Review for COBOL: Limitations in Version 8.5.0.1" at http://www.ibm.com/support/docview.wss?uid=swg21598204.
  2. If the fragment does not contain a documented limitation, and if the problem persists, contact your system administrator.
CRRZV0205E
An error occurred during the translation of an expression to the Cobol Application Model: ({0})

Explanation

{0}
Exception message

User response

  1. Determine whether the failing program fragment contains one of the documented limitations of the COBOL Application Model API. For more information see the technote "The COBOL Application Model (CAM) API in Code Review for COBOL: Limitations in Version 8.5.0.1" at http://www.ibm.com/support/docview.wss?uid=swg21598204.
  2. If the fragment does not contain a documented limitation, and if the problem persists, contact your system administrator.
CRRZV0206E
An exception was thrown during the translation of the following expression to the Cobol Application Model: {0}

Explanation

{0}
Expression

User response

  1. Determine whether the failing program fragment contains one of the documented limitations of the COBOL Application Model API. For more information see the technote "The COBOL Application Model (CAM) API in Code Review for COBOL: Limitations in Version 8.5.0.1" at http://www.ibm.com/support/docview.wss?uid=swg21598204.
  2. If the fragment does not contain a documented limitation, and if the problem persists, contact your system administrator.
CRRZV0207E
A statement contains a reference that could not be translated to the COBOL Application Model. The statement is: {1}. The reference is: {0}

Explanation

{0}
Reference
{1}
Statement

User response

Verify that the program does not contain unresolved references. Verify that all the required copy books are present. Then try running the code review again.
CRRZV0208E
Unable to resolve reference '{0}' in '{1}'

Explanation

{0}
0
{1}
1

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

{1}
File name

User response

TPFC1002E
The file name field for {1} is not unique.

Explanation

{1}
File name

User response

TPFC1003E
The file name field for {1} is invalid.

Explanation

{1}
File name

User response

TPFC1004E
The selected file {1} is not remote.

You cannot set remote properties on a local file.

Explanation

{1}
File name

User response

TPFC1005E
The selected file {1} is not a TPF DLL configuration file.

The file is probably a dynamic link library.

Explanation

{1}
File name

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

{1}
File name

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

{1}
File name

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

{1}
Filter name

User response

TPFC3075E
One or more filter strings in filter {1} could not be resolved.

Explanation

{1}
Filter name

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

{1}
Folder name

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

{1}
Filter name

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

{1}
File name

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

{1}
File name

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

{1}
File name

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

{1}
File name

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

{1}
File name

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

{1}
File name

User response

TPFC5200E
Error generating the build script.

Explanation

User response

TPFC5500E
The file {1} is already included in the source segment list.

Explanation

{1}
File name

User response

TPFC5501E
Source segment must have a {1} file extension.

Explanation

{1}
File name

User response

TPFC5502E
The file {1} is already included in the dependency list.

Explanation

{1}
File name

User response

TPFC5503E
Dependency must have a {1} file-name extension.

Explanation

{1}
File-name extension

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

{1}
File name

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

{1}
File name

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

{1}
File name

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

{1}
File name

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

{0}
Folder name

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

{1}
File name

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

{1}
File name

User response

TPFC6104E
Download of file {1} failed because the file is disconnected or inaccessible.

Explanation

{1}
File name

User response

TPFC6105E
Upload of file {1} failed because the file is disconnected or inaccessible.

Explanation

{1}
File name

User response

TPFC6106E
Upload of file {1} failed because the file is not remote.

Only remote files can be uploaded.

Explanation

{1}
File name

User response

TPFC6107E
Upload of file {1} failed because the file was never properly downloaded.

Explanation

{1}
File name

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

{1}
File name

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

{1}
Folder name

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

{1}
File name

User response

TPFC6505E
Copy of {1} failed.

Ensure that the source exists and is accessible.

Explanation

{1}
File name

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

{1}
File name

User response

TPFC6508E
Deletion of file {1} failed because the file could not be accessed.

Explanation

{1}
File name

User response

TPFC6509E
Deletion of folder {1} failed because the folder could not be accessed.

Explanation

{1}
Folder name

User response

TPFC6510I
File {1} successfully deleted.

Explanation

{1}
File name

User response

TPFC6511I
Folder {1} and it's contents were successfully deleted.

Explanation

{1}
Folder name

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

{1}
File name

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

{1}
File name

User response

TPFC6517I
The file {1} was successfully uploaded.

Explanation

{1}
File name

User response

TPFC6518E
Upload of file {1} failed with an unknown error.

Explanation

{1}
File name

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

{1}
Path name

User response

TPFC6524E
CreateFolder failed to create folder(s) {1} because an unexpected error occurred.

Explanation

{1}
Folder names

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

{1}
Folder name

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

{1}
File name

User response

TPFC6534I
The variable is resolved successfully.

Explanation

User response

TPFC6535E
Open file failed because the file {1} could not be opened.

Explanation

{1}
File name

User response

TPFC6536I
Open file success. File {1} opened.

Explanation

{1}
File name

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

{1}
Folder name

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

{1}
File name

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

{1}
File name
{2}
A date

User response

TPFC6547E
File {1} is not a valid migration scan results file because it does not contain a scan date.

Explanation

{1}
File name

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

{1}
Query options

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

{1}
Filter name

User response

TPFC6565I
The import was completed successfully.

Explanation

User response

TPFC6566E
Import failed. The specified file {1} does not exist.

Explanation

{1}
File name

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

{1}
File name

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

{1}
File name

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

{1}
File name

User response

TPFC6585I
Import succeeded. The file {1} was successfully imported.

Explanation

{1}
File name

User response

TPFC6586I
Import succeeded. The file {1} was successfully imported.

Explanation

{1}
File name

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

{1}
File name

User response

TPFC6603I
The specified file {1} is invalid. Please specify a file with a .xml extension.

Explanation

{1}
File name

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

{0}
File name

User response

TPFC7001E
Unable to create connection path for TPFFolder {0}.

Explanation

{0}
Folder name

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

{1}
File name

User response

TPFC8601E
The port number specified is out of bound.

Explanation

User response

TPFC8602I
The TPFtool server is started on port {0}.

Explanation

{0}
A port number

User response

TPFC8603I
The TPFtool server has stopped listening on port {0}.

Explanation

{0}
A port number

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

{1}
File name

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

{1}
File name

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

{1}
File name

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

{1}
A file name

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

{1}
A specified location

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

{1}
The name of a device

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 z Systems 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 z Systems 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

{1}
The name of a file

User response

TPFR3000E
The file '{1}' cannot be accessed.

Ensure there is a connection available to access the file.

Explanation

{1}
The name of a file

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

{1}
The name of a file

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

{1}
Value
{2}
Value

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

{1}
The name of a file

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

{1}
The name of a file

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

{1}
The name of a file

User response

TPFR6148E
Cannot find the file {1}.

Explanation

{1}
The name of a file

User response

TPFR6149E
Found the wrong file {1}.

Explanation

{1}
The name of a file

User response

TPFR6150E
Failed moving the file to {1}.

Explanation

{1}
The name of a file

User response

TPFR6151E
Failed deleting the file {1}.

Explanation

{1}
The name of a file

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

{1}
The name of a file

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

{1}
A user ID

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

{1}
The name of a file

User response

TPFR6212E
Unknown error while creating folder '{1}'.

Explanation

{1}
The name of a folder

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

{1}
The name of a file

User response

TPFR8037E
The name '{1}' contains invalid folder name characters.

Remove all invalid characters from the folder name.

Explanation

{1}
The name of a folder

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

{1}
The name of a file

User response

TPFR8044E
The folder is not remote.

Select a remote folder. {1}

Explanation

{1}
The name of a folder

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

{1}
A file name

User response

TPFR8058E
The folder '{1}' is selected twice.

Remove one occurrence of '{1}' from the selection.

Explanation

{1}
The name of a folder

User response

TPFR8059E
The folder '{1}' does not have read access.

Select a folder that has read access permission.

Explanation

{1}
The name of a folder

User response

TPFR8060E
The folder '{1}' does not have write access.

Select a folder that has write access permission.

Explanation

{1}
The name of a folder

User response

TPFR8061E
The file '{1}' does not have read access.

Select a file that has read access permission.

Explanation

{1}
A file name

User response

TPFR8062E
The file '{1}' does not have write access.

Select a file that has write access permission.

Explanation

{1}
A file name

User response

TPFVAL1000E
Sample validation error message

Explanation

User response

Messages for TPF Toolkit Utilities

These are the messages that pertain to TPF Toolkit Utilities.

TPFU9009E
TPF launch user exit failed with RC {1}.

TPF Toolkit perspective and views will be disabled. Although other Eclipse functions are not affected, you must correct the cause of the user exit failure to use the TPF Toolkit functions. Then, shut down the workbench and restart.

Explanation

{1}
A return code

User response

TPFU9010W
'{1}' is not a valid environment variable name.

Specify a non-null value as an environment variable name.

Explanation

{1}
A name specified as an environment variable name

User response

TPFU9011W
'{1}' could not be resolved as an environment variable.

Ensure that the variable '{1}' has been defined and set.

Explanation

{1}
The name of an environment variable

User response

TPFU9012W
The folder '{1}' referenced by the environment variable '{2}' does not exist.

Specify an existing, accessible folder as the value of '{2}'.

Explanation

{1}
A folder name
{2}
The name of an environment variable

User response

TPFU9013W
The folder '{1}' referenced by the environment variable '{2}' does not have write permission.

Specify an existing folder with write permission as the value of '{2}'.

Explanation

{1}
A folder name
{2}
The name of an environment variable

User response

TPFU9014W
The folder '{1}' referenced by the environment variable '{2}' is not local.

Specify an existing local folder as the value of '{2}'.

Explanation

{1}
A folder name
{2}
The name of an environment variable

User response

TPFU9020E
More than one password is associated with host {1} and user ID {2}.

Open the preferences page and update the saved passwords information.

Explanation

{1}
The name of a remote system
{2}
A user identifier

User response

TPFU9021E
A cached password is already associated with host {1} and user ID {2}.

The input you just made is ignored.

Explanation

{1}
The name of a remote system
{2}
A user identifier

User response

TPFU9025E
Failed to run command '{1}'. The message from the command is '{2}'.

Explanation

{1}
The name of a command
{2}
The error message returned by the command

User response

TPFU9030I
Running action {1} ...

Explanation

{1}
An action

User response

TPFU9040E
Invalid host name or IP address.

Explanation

User response

TPFU9050W
The index that you are searching is outdated. Do you want to update the index and perform the search again?

Explanation

User response

TPFU9051W
Do you want to delete all index data from the removed index locations?

Explanation

User response

TPFVAL1000E
Sample validation message

Explanation

This is a sample validation message.

User response

No user response is required.

Messages for zSeries Utility

These messages pertain to the zSeries Utility.

TPFVAL1000E
Sample validation messages.

Explanation

This is a sample validation message.

User response

No user response is required.
TPFZ1001E
A connection to the {1} host cannot be established. The host is unknown.

Explanation

{1}
The name of a remote system
The remote system is unknown.

User response

Verify that the host name is correct and that the host is available.
TPFZ1002E
A connection to the {1} host at the {2} port could not be established.

Message from host: {3}

Explanation

{1}
The name of a remote system
{2}
The port number
{3}
The message received from the remote system

The remote system sent the message that is displayed.

User response

Verify that the host is available and that the host name and port number are correct.
TPFZ1003E
The host name or the user ID cannot be found.

Explanation

The connection failed because the host name or user ID is unknown.

User response

Verify that the host name and user ID are correct and available.
TPFZ1004E
User {1} cannot log on to the {2} host.

Explanation

{1}
A user ID
{2}
The name of a remote system
The entered password for user {1} for the {2} host is incorrect.

User response

Verify that the password for the specified user ID is correct.
TPFZ1005I
Starting Remote System Explorer host server using SSH.

Explanation

The Remote System Explorer is starting with the SSH proxy.

User response

No user response is required.
TPFZ1006E
SSH key authentication could not be completed.

Explanation

Secure Shell key authentication could not be completed. A password is required to establish the SSH session and exchange public keys so that the next key authentication request can be completed.

User response

Enter the password to exchange keys and continue.
TPFZ1007E
Password authentication failed.

Explanation

The provided password is incorrect.

User response

Enter the correct password for authentication.
TPFZ1008E
No connection exists to the SSH server on the {1} host at the {2} port.

Explanation

{1}
The name of a remote system
{2}
The number of a communications port
An SSH connection does not exist at the specified port.

User response

Verify that the host system has an SSH server running at the specified port.
TPFZ1009E
The SSH server was not found on the {1} host at the {2} port.

Explanation

{1}
The name of a remote system
{2}
The number of a communications port
A Secure Shell server on the specified host at the specified port could not be found.

User response

Verify that the host system has an SSH server running at the specified port.
TPFZ1010E
The SSH server on the {1} host at the {2} port is not compatible with TPF Toolkit.

Explanation

{1}
The name of a remote system
{2}
The number of a communications port
The version of SSH server that was found is not compatible with TPF Toolkit. TPF Toolkit requires that the SSH server be compliant with OpenSSH 3.4 or later.

User response

Check the version of the SSH server that is running on the host.
TPFZ1011E
A connection to the SSH server on the {1} host at the {2} port was not established.

Explanation

{1}
The name of a remote system
{2}
The number of a communications port

User response

Try your request again. If the connection fails again, obtain a trace by following the instructions in IBM Knowledge Center, and analyze the output in the TPF_Toolkit_installaton_directory\eclipse\workspace\.metadata\ssh.log file.
TPFZ1012E
Authentication failed during the attempt to connect to the SSH server on the {1} host at the {2} port.

Explanation

{1}
The name of a remote system
{2}
The number of a communications port
If you are using password authentication, an incorrect user ID or password was used to access the system. If you are using key authentication, an invalid key or user ID was used.

User response

Correct the user ID or password, and try your request again.
If you use key authentication, correct the user ID, delete the TPF_Toolkit_installaton_directory\eclipse\workspace\.metadata\id_dsa file, and try your request again.
TPFZ1013E
An unknown error occurred while the connection to the SSH server on the {1} host at the {2} port was in use.

Explanation

{1}
The name of a remote system
{2}
The number of a communications port

User response

Try your request again. If the connection fails again, obtain a trace by using the instructions in IBM Knowledge Center, and analyze the output in the TPF_Toolkit_installaton_directory\eclipse\workspace\.metadata\ssh.log file.
TPFZ1014E
Failed to disconnect from host {1}.

Message from host: {2}

Explanation

{1}
The name of a remote system
{2}
The message received from the remote system
An error was encountered when disconnecting from the remote system.

User response

Try to disconnect again. If disconnection attempt fails again, contact IBM Software Support.
TPFZ6001W
A connection with the remote system cannot be established.

Explanation

The name of a remote system is not specified.

User response

Specify the name of a remote system.
TPFZ6002W
The specified system cannot be used.

Explanation

A system that already exists has been specified. You must specify an unused system.

User response

Specify another system.

Host and runtime messages

The topics in this portion of the documentation contain information about the host and runtime messages for Rational Developer for z Systems.

Most IDs for host and runtime messages in Developer for z Systems have the format xnnnnL, where:
x
A prefix such as CRAZ or FEK that indicates the product and component
nnnn
A message number that is unique in that component
L
The message level: S for severe error, E for error, W for warning, or I for informational

This message documentation is also included in IBM Knowledge Center.

Host messages for the z/OS Automated Unit Testing Framework (zUnit)

These host messages pertain to the zUnit component of Rational Developer for z Systems.

AZU0001S
The error "ERROR-TEXT" was received from the XML Toolkit for z/OS while parsing the test runner configuration XML file "FILE-NAME".

Explanation

zUnit uses the XML Toolkit for z/OS XML Parser, C++ Edition, to parse the test runner configuration XML file. Errors that are produced by the XML parser are detected by zUnit and converted to Language Environment conditions.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1.

Programmer response

Look up the ERROR-TEXT error message in the XML System Services User's Guide and Reference to diagnose and correct the problem.
AZU0002S
The error "ERROR-TEXT" was received from the z/OS XL C/C++ dlopen library function while attempting to load test case module "MODULE-NAME".

Explanation

zUnit uses the XL C/C++ dlopen and dlsym library functions to load zUnit test case modules. The dlopen library function loads the test case module into memory. The dlsym library function locates an entry point whose name matches the test case module name.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 2.

Programmer response

Verify these items:
  • The test case module is compiled and linked as a DLL.
  • The load module name matches the program name that is supplied in the test runner configuration XML file.
The following options are expected:
  • COBOL compile options: DLL and EXP.
  • PL/I compile options: RENT and LIMITS(EXTNAME(8)).
  • Link options: DYNAM=DLL and REUS=RENT.
AZU0003S
The error "ERROR-TEXT" was received from the z/OS XL C/C++ dlsym library function while attempting to load entry "ENTRY-NAME" in test case module "MODULE-NAME".

Explanation

zUnit uses the XL C/C++ dlopen and dlsym library functions to load zUnit test case modules. The dlopen library function loads the test case module into memory. The dlsym library function locates the entry point whose name matches the test case module name.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 3.

Programmer response

Verify these items:
  • The test case module is compiled and linked as a DLL file.
  • The load module name matches the program name that is supplied in the test runner configuration XML file.
The following options are expected:
  • COBOL compile options: DLL and EXP.
  • PL/I compile options: RENT and LIMITS(EXTNAME(8)).
  • Link options: DYNAM=DLL and REUS=RENT.
AZU0004S
The supplied test runner configuration XML file "FILE-NAME" did not specify any test cases to execute.

Explanation

The supplied test runner configuration XML file was successfully parsed, but no valid RunnerConfiguration/testCase elements were found.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 4.

Programmer response

Add at least one element with XPath RunnerConfiguration/testCase to the test runner configuration XML file, and start the test runner again. Ensure that each RunnerConfiguration/testCase element contains a RunnerConfiguration/testCase/@moduleName attribute.
AZU0005S
An attempt to initialize test case module "MODULE-NAME" failed.

Explanation

The test runner successfully called an entry point in the test case module MODULE-NAME, whose name matches MODULE-NAME, to allow for test case initialization. Either the AZUTCINI API was not started in the entry point or the call failed.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 5.

Programmer response

Ensure that a call to the AZUTCINI API exists in the entry point whose name matches MODULE-NAME. If a call to the AZUTCINI API exists, check for an instance of the AZU1000S message to determine whether incorrect parameters were supplied to AZUTCINI.
AZU0006S
The error "ERROR-TEXT" was received from the XML Toolkit for z/OS while generating the test runner results XML file "FILE-NAME".

Explanation

zUnit uses the XML Toolkit for z/OS DOM implementation, C++ Edition, to model and generate the test runner results XML file. Exceptions that the DOM implementation throws are caught by zUnit and converted to Language Environment conditions.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 6.

Programmer response

Look up the error message ERROR-TEXT in the XML Toolkit for z/OS User's Guide to diagnose and correct the problem.
AZU1000S
An invalid pointer was specified to API "API-NAME" in parameter "PARM-NAME".

Explanation

An API named API-NAME detected that the pointer value supplied in a parameter named PARM-NAME was invalid.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1000.

Programmer response

Assign a valid pointer value to the PARM-NAME parameter before you call the API-NAME API.
AZU1001S
An invalid value of "PARM-VALUE" was specified to API "API-NAME" in parameter "PARM-NAME".

Explanation

An API named API-NAME detected that the value given in PARM-VALUE is not valid or is out of range for the parameter named PARM-NAME.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1001.

Programmer response

Assign a valid value to the PARM-NAME parameter.
AZU1002S
The test "TEST-NAME" failed due to an assertion. The test is a member of test case module "MODULE-NAME", which set a test case name of "TEST-CASE-NAME" and an id of "TEST-CASE-ID" when initialized.

Explanation

A test named TEST-NAME failed in the test case module named MODULE-NAME because of a call to the AZUASTFA assertion API. The test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1002.

Programmer response

Modify the TEST-NAME test and run the MODULE-NAME test case again. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the version that you intended to run.
AZU1003S
The test "TEST-NAME" failed due to an assertion. The user-supplied text "USER-TEXT" is associated with the assertion. The test is a member of test case module "TEST-CASE-MODULE" which set a test case name of "TEST-CASE-NAME" and an id of "TEST-CASE-ID" when initialized.

Explanation

A test named TEST-NAME started the AZUASTFM assertion API in a test case module named MODULE-NAME. The text USER-TEXT was supplied on the call to the AZUASTFM API. The test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1003.

Programmer response

Modify the TEST-NAME test and run the MODULE-NAME test case module again. Use the UUID to ensure that the test case module that was located by using the standard MVS search order is the most recent version or the version that you intended to run.
AZU1004S
The test "TEST-NAME" failed due to the unexpected error "ERROR-TEXT". The test is a member of test case module "MODULE-NAME", which set a test case name of "TEST-CASE-NAME" and an id of "TEST-CASE-ID" when initialized.

Explanation

A test named TEST-NAME encountered an unexpected error (for example, SOC4) in a test case module named MODULE-NAME. The text of the error is given as ERROR-TEXT. The test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1004.

Programmer response

Modify the TEST-NAME test and run the MODULE-NAME test case module again. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
AZU1005S
The test case module "MODULE-NAME", which set a test case name of "TEST-CASE-NAME" and an id of "TEST-CASE-ID" when initialized, failed because TEST-FAIL-COUNT out of TEST-TOTAL-COUNT tests failed due to assertions or unexpected errors.

Explanation

A test case module named MODULE-NAME failed because at least one of its test members failed because of an assertion or an unexpected error. This test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1005.

Programmer response

Modify the tests in the MODULE-NAME test case module and run the test case module again. At least one instance of message AZU1002S, AZU1003S, or AZU1004S is issued before this message. See the instances of AZU1002S, AZU1003S, or AZU1004S that are displayed before this message to determine which tests failed within the test case module. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
AZU1006S
A test with name "TEST-NAME" has already been added by test case module "MODULE-NAME", which set a test case name of "TEST-CASE-NAME" and an id of "TEST-CASE-ID" when initialized.

Explanation

A test with name TEST-NAME was previously added to the test case module named MODULE-NAME in a prior call to the AZUTCINI API.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1006.

Programmer response

Supply a unique name for each test within a test case module when you call the AZUTCINI API. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
AZU1007S
A test entry with address 0xENTRY-ADDR has already been referenced by test "TEST-NAME" in test case module "MODULE-NAME", which set a test case name of "TEST-CASE-NAME" and an id of "TEST-CASE-ID" when initialized.

Explanation

A test with entry address ENTRY-ADDR was previously added to the test case module named MODULE-NAME in a prior call to the AZUTCINI API.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1007.

Programmer response

Supply the address of an entry that was not already referenced in a prior call to the AZUTCINI API. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
AZU1008S
An attempt to initialize test case module "MODULE-NAME", which set a test case name of "TEST-CASE-NAME" and an id of "TEST-CASE-ID" when initialized, failed because the test case module is already initialized.

Explanation

A duplicate attempt to initialize a test case module failed. The test case token that is supplied to the AZUTCINI API indicates that the test case module MODULE-NAME was successfully initialized on a previous call to the API.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1008.

Programmer response

Correct the test case module so that it does not call the AZUTCINI API multiple times. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
AZU1009S
The test case module "MODULE-NAME", which set a test case name of "TEST-CASE-NAME" and an id of "TEST-CASE-ID" when initialized, failed because it did not add at least one test using the AZUTCADD API.

Explanation

A test case module named MODULE-NAME did not add any tests by using the AZUTCADD API when the ADDTESTS entry was called by the test runner. This test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1009.

Programmer response

Modify the MODULE-NAME test case module to add at least one test when the test runner calls the ADDTESTS entry. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
AZU1010S
The test case module "MODULE-NAME", which set a test case name of "TEST-CASE-NAME" and an id of "TEST-CASE-ID" when initialized, encountered the unexpected error "ERROR-TEXT" outside of a test entry.

Explanation

A test case module named MODULE-NAME encountered an unexpected error outside of a test entry, possibly in the ADDTESTS, SETUP, or TEARDOWN entries. This test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization,

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1010.

Programmer response

Check for logic errors in the ADDTESTS, SETUP, and TEARDOWN entries. Check the entry whose name matches MODULE-NAME (the entry that is expected to call the AZUTCINI API) for logic errors. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
AZU1011S
An internal error occurred in API "API-NAME". Check that the parameters supplied to the API are of the correct type (for example, pointer) and mode (for example, byvalue).

Explanation

An API named API-NAME encountered an internal error. This error can occur when an interface mismatch exists between the calling program and the API; for example, a by-value parameter that is accidentally passed by-reference.

System action

The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1011.

Programmer response

Check that all required parameters are passed to the API by the calling program. Confirm that by-value parameters are passed by-value and that by-reference parameters are passed by-reference.

Messages for the SCLM Development Toolkit

These messages pertain to the SCLM Development Toolkit in Rational Developer for z Systems.

BWB00001
ERROR in Allocation/Write to:

Explanation

An attempt to write the client parameter input to a temporary data set has failed.

User response

Review the operations log to further determine any errors.
BWB00003
Following function has failed:

Explanation

Indicates which function or operation request failed.

User response

Review additional error messages and the operations log to determine error.
BWB00004
ISPF initialization has failed

Explanation

The ISPF/SCLM session has failed to initialize. Processing is terminated.

User response

Review additional error messages and the operations log to determine error.
BWB00005
Review your ISPF properties and load library

Explanation

This is an additional error message to indicate a reason for ISPF/SCLM initialization failure.

User response

The Systems programmer should review the ISPF.conf configuration file in the directory pointed to by CGI_ISPCONF in rsed.envvars to determine the correct ISPF data set allocations have been set.
BWB00006
Ensure the load library data set is APF authorized

Explanation

The SCLM Developer Toolkit Loadlib data set may not be APF-authorized, resulting in ISPF/SCLM initialization failure.

User response

The Systems programmer should ensure that the Loadlib is APF-authorized or that no non-APF authorized data sets have been included in the STEPLIB configured in rsed.envvars.
BWB00007
ISPF or SCLM service has ended abnormally

Explanation

An ISPF/SCLM internal error has caused the session to terminate. The function request is cancelled.

User response

Review the operations log to further determine any errors.
BWB00008
Review Log for error details

Explanation

Review the Client operations log for further messages or error analysis.

User response

To review the operations log, right click in the SCLM View and select Operations Log.
BWB00009
Error reading the ISPF.conf configuration file

Explanation

ISPF.conf should be located in the directory that is specified by CGI_ISPCONF in rsed.envvars.

User response

The Systems Programmer should check the specified directory to ensure ISPF.conf exists and the user has read access to it.
BWB00010
Ensure file exists in directory specified by environment variable CGI_ISPCONF set in the server configuration

Explanation

Configuration files such as ISPF.conf should be located in the directory specified by CGI_ISPCONF in rsed.envvars.

User response

The Systems Programmer should check the specified directory to ensure ISPF.conf exists and the user has read access to it.
BWB00011
If error on ISPSPROF table then a background session may already be using the profile data set

Explanation

Two concurrent sessions have been initiated and are using the same ISPF profile data set.

User response

Check that another session is not running concurrently and preventing this session to establish.
BWB00012
Error in ISPF data set allocation : See the error message below:

Explanation

An error in one of the ISPF data set allocations. Specific allocation error messages follow.

User response

The Systems Programmer should check ISPF.conf to ensure valid ISPF DD names and correct ISPF data sets.
BWB00013
Error in allocating the following DD and data set names:

Explanation

The following data set could not be allocated to that DD name.

User response

The Systems Programmer should review the DD and data set allocation (ISPF.conf).
BWB00014
Verify that the ISPF configuration file ISPF.conf on the host is correct

Explanation

An error in the ISPF data set allocations has occurred.

User response

The Systems Programmer should check ISPF.conf to ensure valid ISPF DD names and correct ISPF data sets.
BWB00015
*** Edit cancelled ***

Explanation

EDIT processing has been cancelled due to an error.

User response

Review additional error messages and the operations log to determine error.
BWB00016
The selected group not in development group hierarchy

Explanation

The group selected is not valid because it does not reside in the user's development hierarchy.

User response

Choose a valid group or operate from a different development group.
BWB00017
Unable to locate data set for :

Explanation

An error has occurred in locating a valid data set for that particular project/group/type.

User response

The SCLM administrator should check that a valid data set exists for that project/group/type.
BWB00018
*** Edit/Browse cancelled ****

Explanation

An error has occurred in EDIT/BROWSE and the function is cancelled.

User response

Review additional error messages and the operations log to determine error.
BWB00019
Member selected resides in lower hierarchy group

Explanation

The member can not be edited from the selected group because a member of the same name exists in the hierarchy at a lower group.

User response

Select member from lower hierarchy group. You might also want to synchronize the IDE view with the SCLM repository, or repopulate the SCLM Developer View or SCLM Explorer View.
BWB00020
The member should be selected from group:

Explanation

Additional message indicating which member should be selected for this operation.

User response

Select recommended member and repeat function.
BWB00021
Repository view mismatch

Explanation

The user's repository view and SCLM are not synchronized.

User response

Synchronize the IDE view with the SCLM repository, or repopulate the SCLM Developer View or SCLM Explorer View.
BWB00022
Re-filter using Populate SCLM Project View or re-synchronize the IDE view

Explanation

The repository view or IDE view are not synchronized with SCLM.

User response

Re-populate project if explorer mode or developer mode are not synchronized. Otherwise re-synchronize IDE view.
BWB00023
*** Add new member function cancelled ***

Explanation

The Add new member function has been cancelled due to errors.

User response

Review additional error messages and the operations log to determine error.
BWB00024
Member does not reside in user's development group

Explanation

An invalid SCLM operation has occurred as the member does not reside in the user's development group.

User response

Select a valid member.
BWB00025
*** No member to Browse ***

Explanation

A valid SCLM member with text was not found.

User response

None
BWB00026
*** Member copy into HFS failed ***

Explanation

The operation involves copying the member to the z/OS HFS. This operation failed.

User response

The Systems programmer should review the operations log for further explanation of this error.
BWB00027
Edit failed - copy failure :

Explanation

As part of the EDIT function a copy of the SCLM member to a temporary data set has failed.

User response

Review additional error messages and the operations log for further information.
BWB00028
Error returned on member lock

Explanation

SCLM lock on member for edit failed. Member may already be locked for edit by another user.

User response

Use the View SCLM status action to determine if member is locked for EDIT by another user.
BWB00029
Binary formatted members not valid for Edit

Explanation

Binary object type members of NON-EDIT are not eligible to be selected for EDIT. Function cancelled.

User response

None
BWB00030
*** Copy to HFS failed ***

Explanation

The operation involves copying the member to the z/OS HFS. This operation failed.

User response

The Systems programmer should review the operations log for further explanation of this error.
BWB00031
*** Error in ASCII/EBCDIC translation ***

Explanation

An error has occurred in the translation from ASCII to EBCDIC when checking in a file.

User response

Ensure the file to be checked in is not empty and contains no invalid characters. Otherwise the ASCII EBCDIC code pages used should be verified.
BWB00032
*** Error in member copy to SCLM ***

Explanation

The member being checked in wasn't successfully copied into the MVS data set. The operation has failed.

User response

The Systems programmer should review the operations log for further explanation of this error.
BWB00033
*** Save function failed ***

Explanation

The SAVE function has failed.

User response

Review additional error messages and the operations log to determine error.
BWB00034
*** Save function cancelled ***

Explanation

The check-in function to SCLM was cancelled.

User response

Review additional error messages and the operations log to determine reason.
BWB00035
Member not previously locked for Edit

Explanation

Associated with the SAVE / CHECK-IN function where a member has to be SCLM locked or checked out first.

User response

The user should lock or check-out the member first using the EDIT function.
BWB00036
Error returned from ACCTINFO status on member

Explanation

The requested function internally performs an SCLM ACCTINFO request which has failed.

User response

Review additional error messages and the operations log to determine error. Check the validity of the member.
BWB00037
*** Save function successful ***

Explanation

The SAVE or Check-in operation was successful.

User response

None.
BWB00038
Error returned on SAVE for :

Explanation

Lists member details for the failed SAVE request.

User response

Review additional error messages and the operations log to determine error.
BWB00039
Delete successful for member:

Explanation

The selected member was deleted successfully.

User response

None.
BWB00040
Delete failed for member:

Explanation

Delete function failed for requested member.

User response

Review additional error messages and the operations log to determine error.
BWB00041
Error returned on delete

Explanation

The SCLM delete command has returned a non-zero return code.

User response

Review additional error messages and the operations log to determine error.
BWB00042
Please check the log file for information messages

Explanation

Additional messaging may be contained in the operations log.

User response

To review the operations log, right click and select operations log.
BWB00043
Unlock failed for member:

Explanation

The SCLM unlock command on a cancel EDIT request has failed.

User response

Review the SCLM status of the member.
BWB00044
Unlock successful for member:

Explanation

A member previously locked for EDIT has been successfully unlocked.

User response

None.
BWB00045
Failed allocation of build parameters data set:

Explanation

The temporary data set userid.SCLMDT.VCMISPF.IDnnnnnn containing the build parameters could not be allocated. Processing terminated.

User response

The Systems programmer should review the operations log for additional error messages.
BWB00046
Unable to read build parameters

Explanation

The temporary data set containing the build parameters was allocated but an error occurred while reading or the data set was empty.

User response

The Systems programmer should review the operations log for further explanation of this error.
BWB00047
Warning - Unable to allocate build messages data set

Explanation

The specified Build message data set could not be allocated. Processing continued.

User response

Review the Build messages data set that was user specified from the Build request. Review MVS SYSLOG for any security violations.
BWB00048
Warning - Unable to allocate build report data set

Explanation

The specified Build report data set could not be allocated. Processing continued.

User response

Review the Build report data set that was user specified from the Build request. Review MVS SYSLOG for any security violations.
BWB00049
Warning - Unable to allocate build list data set

Explanation

The specified Build list data set could not be allocated. Processing continues.

User response

Review the Build list data set that was user specified from the Build request. Review MVS SYSLOG for any security violations.
BWB00050
Warning - Unable to allocate build exit data set

Explanation

The specified Build exit data set could not be allocated. Processing continues.

User response

Review the Build exit data set that was user specified from the Build request. Review MVS SYSLOG for any security violations.
BWB00051
Build failed

Explanation

The build request has failed.

User response

Review additional error messages and the operations log to determine error.
BWB00052
Error reading build messages

Explanation

The Build messages data set could not be read.

User response

Review operations log for successful data set allocation.
BWB00053
Error reading build report

Explanation

The Build report data set could not be read.

User response

Review operations log for successful data set allocation.
BWB00054
Error reading build listing

Explanation

The Build listing data set could not be read.

User response

Review operations log for successful data set allocation.
BWB00055
Error reading J2EEBLD report

Explanation

The Build J2EEBLD report data set could not be read.

User response

Review operations log for successful data set allocation.
BWB00056
BATCH skeleton error (Administrator customization error)

Explanation

The SCLM batch skeletons FLMDSU$ FLMB$ could not be included. Build processing terminates.

User response

Review message BWB00057.
BWB00057
Check SCLMDT Skeleton concatenated in ISPSLIB as specified in the file ISPF.conf

Explanation

Extended messaging from message BWB00056.

User response

The Systems programmer should check that the base SCLM skeletons are allocated to ISPSLIB in the HFS configuration file ISPF.conf.
BWB00058
No BATCH submission information returned

Explanation

No BATCH Job information was returned or captured from TSO.

User response

Review the MVS SYSLOG to determine if a batch job was submitted successfully or the Job resides in an SDSF queue.
BWB00059
*** Promote cancelled ***

Explanation

The Promote function has been cancelled.

User response

Review message BWB00016.
BWB00060
Warning - Unable to allocate messages data set

Explanation

The temporary data set to receive SCLM messages USERID.SCLMDT.DTnnnn.FLMMSGS could not be allocated. Processing continues.

User response

The Systems programmer should review the operations or MVS log for additional error messages.
BWB00061
Failed allocation of promote parameters data set:

Explanation

The temporary data set userid.SCLMDT.VCMISPF.IDnnnnnn containing the promote parameters could not be allocated. Processing terminates.

User response

The Systems programmer should review the operations log for additional error messages.
BWB00062
Unable to read promote parameters data set

Explanation

The temporary data set containing the promote parameters was allocated but an error occurred while reading or the data set was empty.

User response

The Systems programmer should review the operations log for further explanation of this error.
BWB00063
Warning - Unable to allocate promote messages data set

Explanation

The specified Promote message data set could not be allocated. Processing continues.

User response

Review the Promote messages data set that was user specified from the promote request. Review MVS SYSLOG for any security violations.
BWB00064
Warning - Unable to allocate promote report data set

Explanation

The specified Promote report data set could not be allocated. Processing continues.

User response

Review the Promote report data set that was user specified from the promote request. Review MVS SYSLOG for any security violations.
BWB00065
Warning - Unable to allocate promote exit data set

Explanation

The specified Promote exit data set could not be allocated. Processing continues.

User response

Review the Promote exit data set that was user specified from the promote request. Review MVS SYSLOG for any security violations.
BWB00066
Warning - Unable to allocate Authcode messages data set

Explanation

The temporary authcode messages data set USERID.SCLMDT.AUTHMSG could not be allocated. Processing continues.

User response

Review MVS SYSLOG for any security violations.
BWB00067
Ensure build was successful

Explanation

Promote failed. Possible reason is invalid Build map.

User response

Review previous build request or view build map.
BWB00068
Breeze is configured for this project, check log for Breeze messages

Explanation

The Breeze flag is set, review additional Breeze messages in operations log.

User response

None.
BWB00069
Error reading promote messages

Explanation

The Promote messages data set could not be read.

User response

Review operations log for successful data set allocation.
BWB00070
Error reading promote report

Explanation

Error reading promote report.

User response

Review operations log for successful data set allocation.
BWB00071
Populate view of project failed

Explanation

Either Project Initialization has failed or the development group specified is invalid for the project.

User response

Review any additional SCLM messages in the operation log and check your development group, Project and filter parameters.
BWB00072
Reading ARCHDEF directly because no BLDMAP was found

Explanation

Populate project by ARCHDEF will generate the request using DBUTIL and the build map for the ARCHDEF. If no build map exists (i.e. the ARCHDEF has not been built) then members will be read directly from the ARCHDEF.

User response

None.
BWB00073
Only members in lowest hierarchy (latest) listed

Explanation

Additional to message BWB00072. As there is no ARCHDEF build map from which to generate the report, the populate will only report on members at the lowest group in the hierarchy.

User response

If not acceptable then use a populate project filter other than ARCHDEF or build the ARCHDEF first to populate full list.
BWB00074
No project view information returned

Explanation

No project information was returned using the specified filters.

User response

Review your filter parameters.
BWB00075
Review your filter parameters

Explanation

Information for message BWB00074.

User response

None.
BWB00076
The following ARCHDEF include was not found in the hierarchy :

Explanation

An INCLD statement for a member was found in the selected ARCHDEF but the member was not found in any group up the development hierarchy.

User response

If the member is invalid, remove it from the ARCHDEF.
BWB00077
*** Update function failed ***

Explanation

The update function failed as the member could not be locked for edit/update.

User response

Review SCLM status of member.
BWB00078
Error returned on LOCK

Explanation

Unable to obtain lock on member for EDIT or Update. Member may already be locked (checked out) by another user.

User response

Review SCLM status of member.
BWB00079
*** Update function cancelled ***

Explanation

Update is cancelled as member was not previously locked for edit.

User response

Review SCLM status of member.
BWB00080
Member not previously locked for edit

Explanation

This is an informational message.

User response

Retry function.
BWB00081
*** Update function successful ***

Explanation

The function completed successfully.

User response

None.
BWB00082
*** AUTHCODE retrieval failed ***

Explanation

Unable to retrieve authcode on selected member.

User response

Review SCLM status of member. Review any SCLM messages in operation log.
BWB00083
*** AUTHCODE update failed ***

Explanation

The update of authcode on the member has failed. Processing terminates.

User response

Review SCLM status of member. Review any SCLM messages in operations log.
BWB00084
*** VERINFO command failed ***

Explanation

The VERINFO request failed with a return code > 8.

User response

Review any SCLM messages in operations log.
BWB00085
No version records were found that match the supplied criteria

Explanation

This is an informational message.

User response

No action is required.
BWB00086
*** VERRECOV command failed ***

Explanation

A version recover request has failed with a return code > 0.

User response

Review any SCLM messages in operations log.
BWB00087
*** VERDEL command failed ***

Explanation

A version delete request has failed with return code > 0.

User response

Review any SCLM messages in operations log.
BWB00088
Severe error in catalog search routine

Explanation

An error has occurred in the IGGCSI00 Catalog search program with a project list request.

User response

The Systems programmer should review the operations and MVS log for further error messages. Retry request.
BWB00089
Warning - No Projects returned on filter:

Explanation

This is an informational message.

User response

Review project filter request.
BWB00090
Error reading translate table:

Explanation

An error has occurred reading the translate table. Processing continues, but there will be errors in the longname to shortname retrieval and updates.

User response

The Systems Programmer should verify correct translate table name: _SCLMDT_TRANTABLE variable in the rsed.envvars configuration file. Run the installation IVP to also verify installation.
BWB00091
Long/short name translation may be in error

Explanation

A previous error with the Longname to shortname translation file has occurred.

User response

The Systems programmer should review the operations log for further error messages.
BWB00092
Error reading file:

Explanation

The displayed HFS file contained the files to migrate could not be read. Migration terminates.

User response

Review the operations log for further error messages.
BWB00093
Error returned from SCLMINFO file allocation

Explanation

Error on allocation of new temporary data set userid.vcm.temp.projinf DCB: SPACE(1,1,20) TRKS RECFM(FB) LRECL(40) BLKSIZE(27960) VIO

User response

Review the MVS SYSLOG for additional messages for data set allocation failure.
BWB00094
Error returned from SCLMLOAD file allocation

Explanation

Unable to allocate DISP=SHR to the data set Project.projdefs.load.

User response

Determine the data set Project.projdefs.load exists, where project is the project name specified.
BWB00095
Error returned on call to ISRFLMGI

Explanation

Unable to call ISPF/SCLM module ISRFLMGI for retrieving group information for project.

User response

None.
BWB00096
Unable to re-allocate SCLMINFO (no groups returned)

Explanation

Unable to allocate temporary data set for project group information retrieval.

User response

Review the operations log for further error messages.
BWB00097
Unable to read SCLMINFO (no groups returned)

Explanation

Unable to read allocated SCLMINFO temporary data set. No project information will be returned.

User response

Review the operations log for further error messages.
BWB00098
Unable to retrieve the list of groups in the specified project

Explanation

No group information for selected project is returned due to function failure.

User response

Review the operations log for further error messages.
BWB00099
Build map deleted for member:

Explanation

The delete request was successful. Build map deleted.

User response

None.
BWB00100
Job id must have valid job name in request

Explanation

No Jobname was passed through in JOB status request with JOBID.

User response

Retry with valid JOB Name specified.
BWB00101
No job name was specified. Your user id will be used by default.

Explanation

No Jobname or Jobid details were passed. Function will report on all jobs starting with USERID as Jobname.

User response

None.
BWB00102
For job retrieval a valid job name and job id must be provided

Explanation

No valid Jobname / Jobid was passed for Job output retrieval.

User response

Retry with valid Jobname / Jobid.
BWB00103
No job output found

Explanation

The requested Batch job was not found on the SDSF queue.

User response

Check on z/OS in SDSF if the batch job still resides on an output queue or has been purged.
BWB00104
Warning - Refer to additional SCLM messages

Explanation

Additional SCLM warning messages have been issued.

User response

View additional SCLM messages in operations log.
BWB00105
Error - SCLM is unable to load the SCLM table

Explanation

Error on SCLMINFO call for project/Project definition.

User response

Check Project and project definition are valid.
BWB00106
Check that the following project definition is valid:

Explanation

Extends message BWB00105.

User response

Check Project and project definition are valid.
BWB00107
Error - The maximum application ID limit was exceeded

Explanation

SCLMINFO request has returned return code 12.

User response

Check Project and project definition are valid. Inform SCLM administrator of error.
BWB00108
Errors initializing project:

Explanation

Extends message BWB00107.

User response

Reference message BWB00107.
BWB00109
Error - An invalid version of the SCLM table was loaded

Explanation

SCLMINFO request has returned return code 16.

User response

Check Project and project definition are valid. Inform SCLM administrator of error.
BWB00110
Error - An invalid parameter list was passed to the SCLMINFO service

Explanation

SCLMINFO request has returned return code 32.

User response

Check Project and project definition are valid. Inform SCLM administrator of error.
BWB00111
Error - Refer to SCLM messages manual on SCLMINFO codes

Explanation

The SCLM messages manual will give additional information on the SCLMINFO return codes.

User response

Review the SCLM messages manual.
BWB00112
No project specific entries in project configuration file:

Explanation

The SITE.conf file has not been tailored for use.

User response

None.
BWB00113
Failed allocation of migrate parameters data set:

Explanation

The Temporary MIGRATE data set USERID.SCLMDT.VCMISPF.IDnnnnnn could not be allocated. Processing terminates.

User response

The Systems programmer should review the operations log for additional error messages.
BWB00114
Failed read of migrate parameters

Explanation

Error reading allocated parameter data set.

User response

The Systems programmer should review the operations log for additional error messages.
BWB00115
Error on directory:

Explanation

Error in creating or locating specified directory in HFS which is used to process the current function.

User response

The Systems programmer should review the operations log for additional error messages.
BWB00116
PUT command failed for the following:

Explanation

A copy of a member from an SCLM data set into a HFS directory has failed.

User response

Check SCLM status of member. Review the operations log for additional error messages.
BWB00117
Error threshold of 5 errors reached in copy

Explanation

An error threshold of 5 bad member copies between SCLM and the HFS directory has occurred in the Java/J2ee build translators. Processing terminates.

User response

Review the operations log for additional error messages. Rectify problem and retry function request.
BWB00018
Errors in code page conversions - Review the log file

Explanation

Errors have occurred in the ASCII / EBCDIC codepage conversions.

User response

Review the operations log for additional error messages.
BWB00119
The JAR command was unable to create :

Explanation

An error has occurred in creating a Java JAR file. This function uses Java to JAR up a zip file for transferring files across the network.

User response

Review the operations log for additional error messages. The Systems Programmer should ensure a valid Java path exists in rsed.envvars and check for space problems within the users WORKAREA directory.
BWB00120
JAVA_PATH in httpd.env or rsed.envvars file may not be valid. Check with your administrator

Explanation

An error occurred starting a Java command.

User response

The Systems Programmer should ensure a valid java path exists in httpd.env for the HTTP server.
BWB00121
Error found in DBUTIL report - Review the log file

Explanation

A failure has occurred with an SCLM DBUTIL request for producing a member list. Further error messages may be displayed.

User response

Review the operations log for additional error messages.
BWB00122
No project information returned by filter

Explanation

The USER specified filter list has returned no project information.

User response

Review your filter parameters and retry.
BWB00123
SCLM import successful for the following number of members:

Explanation

This is an informational message only.

User response

None.
BWB00124
No files to migrate specified in migrate file:

Explanation

No files were found to be migrated.

User response

If an error review the operations log for additional error messages.
BWB00125
Invalid Host name convention for:

Explanation

The file to be stored is being stored with a language that does not allow long names but the file has a name that is not a valid host member name. Host member names must be characters or less.

User response

If the file needs to be stored as a long language type i.e. converted to a short name then ensure the language type matches the LONGLANG keywords in TRANSLATE.conf (see the administrator).
BWB00126
Invalid short name conversion for:

Explanation

An error occurred when translating a long file name to a short name. The short name is used by SCLM to store the file as a member of an SCLM library.

User response

Review the operations log for further errors. Report this problem to the systems programmer or SCLM administrator.
BWB00127
Check access permissions on translate table:

Explanation

Redundant message.

User response

Ignore.
BWB00128
Error threshold reached in short name

Explanation

The error threshold of 5 shortname error conversions has been reached, the migrate process terminates.

User response

Review the operations log for further errors. Report this problem to the systems programmer or SCLM administrator.
BWB00129
Member being migrated already exists - not migrated. Member:

Explanation

An attempt to migrate in a member was made where the member already exists in the group hierarchy and the force option was not used.

User response

If needed, members can be force migrated by setting the 'force' flag on from the migrate panel. Warning: this is not advised because normal checkout/checkin processing should be used. Forced migration can cause members which are already in SCLM to be overwritten.
BWB00130
Copy failed:

Explanation

A copy of an SCLM member from the HFS to an SCLM data set has failed.

User response

The Systems Programmer should check the output data set is valid and there are no space problems or security violations.
BWB00131
Check MVS SYSLOG for possible security violation

Explanation

Informational: extends BWB00130.

User response

Inform Systems Programmer of this message.
BWB00132
Error threshold of 20 errors reached in copy

Explanation

For a migrate or import the error threshold of 20 has been reached for copy failures from HFS to/from SCLM. Processing terminates.

User response

Review the operations log for further errors. Report this problem to the systems programmer or SCLM administrator.
BWB00133
Error reading migrate Messages

Explanation

In Migrate processing an error occurred when reading the Messages data set. Processing continues but Migrate messages will not be included in the display output.

User response

Review the operations log for additional error messages.
BWB00134
SCLM migration successful for the following number of files:

Explanation

This is an informational message.

User response

None.
BWB00135
Migration message data set:

Explanation

This is an informational message.

User response

None.
BWB00136
Migration report data set:

Explanation

This is an informational message.

User response

None.
BWB00137
SCLM migration unsuccessful for the following number of files:

Explanation

Errors occurred with a number of files during migration processing and are listed here. Migration may have only partially succeeded for some files/members.

User response

Review the operations log for additional error messages.
BWB00138
Refer to migration message data set:

Explanation

Migration messages have been written to this data set on z/OS for reference.

User response

Review the migration data set if required.
BWB00139
SCLM Update error for project architecture definition :

Explanation

An ARCHDEF was selected which was to be updated with the names of the members that were migrated, but the ARCHDEF could not be updated.

User response

Check the ARCHDEF selected within SCLM for errors and review the operations log for further errors. Archdef may have to be manually updated with members if required.
BWB00140
Following project ARCHDEF updated:

Explanation

Informational: The ARCHDEF was successfully updated with the names of the members that were migrated.

User response

None.
BWB00141
An error occurred reading ARCHDEF:

Explanation

The ARCHDEF member to be updated with migrating members already exists but the read has failed. Migration continues without ARCHDEF update.

User response

Check the validity of the selected ARCHDEF. Archdef may have to be manually updated with members if required.
BWB00142
An error occurred updating ARCHDEF:

Explanation

An ARCHDEF was selected to add migrating members to but the SCLM update to the ARCHDEF has failed. Bad allocation of ARCHDEF member at the development level.

User response

Check the ARCHDEF selected within SCLM for errors and review the operations log for further errors. Archdef may have to be manually updated with members if required.
BWB00143
UNJAR failed on following file:

Explanation

An error has occurred in unzipping a file using the Java JAR command. This function uses Java to UNJAR a zip file for transferring files across the network.

User response

Review the operations log for additional error messages. The Systems Programmer should ensure a valid Java path exists in rsed.envvars and check for space problems within the user's WORKAREA directory.
BWB00144
Your system administrator should check the _SCLMDT_CONF_HOME variable in rsed.envvars

Explanation

The variable _SCLMDT_CONF_HOME specified in the rsed.envvars file may not be correct. This Environment variable determines the directory path where the configuration files reside for SCLM Developer Toolkit.

User response

Systems programmer should investigate the _SCLMDT_CONF_HOME setting in rsed.envvars.
BWB00145
J2EEPUT in httpd.conf must be CGI_DTWORK/WORKAREA/*

Explanation

This message is not valid for Rational Developer for z Systems and should be ignored.

User response

Ignore this message.
BWB00146
Error reading listing file:

Explanation

Files to be migrated are contained in a HFS listing file. An error occurred while reading this file and migration processing terminates.

User response

Systems programmer should check HFS file permissions for specified user and available space.
BWB00147
Error in ASCII/EBCDIC conversion:

Explanation

An error has occurred during an ASCII to EBCDIC file conversion. DT uses the iconv routine within HFS to codepage convert.

User response

Systems programmer should check ASCII/EBCDIC customization parameters in TRANSLATE.conf. Check file being converted for special characters or empty file.
BWB00148
Invalid hostname structure (directory/filename)

Explanation

Host file structure does not contain a '/' as first character.

User response

Review operations log to view Host File name passed to transfer routine.
BWB00149
An invalid value was received by the file transfer service: DIRECTION=

Explanation

The direction keyword is not valid for file transfer. Valid direction keywords are TOHOST or FROMHOST.

User response

Review operations log for direction keyword passed and retry.
BWB00150
An invalid value was received by the file transfer service: FILETYPE=

Explanation

The filetype keyword for transfer is not valid. Valid filetype is BINARY or TEXT.

User response

Review operations log for filetype keyword passed and retry.
BWB00151
ZIP option only valid for TOHOST transfer

Explanation

ZIP option (ZIP = yes) is only valid for transfer direction TOHOST.

User response

Retry operation without ZIP flag set if transferring from host.
BWB00152
ZIP option only valid for BINARY transfer

Explanation

ZIP = YES has been set for transferring a file other than of filetype BINARY. This is not valid.

User response

Retry operation without ZIP flag set if transferring text file.
BWB00153
Check valid host name or file permissions

Explanation

Accompanies message BWB00130. Copy has failed.

User response

Review that the file permissions on the HFS directories or Host file name are valid.
BWB00154
Unable to locate host directory :

Explanation

The host directory is part of the HOSTFILE name specified. The HFS directory does not exist.

User response

Systems programmer should check the HFS directory name specified.
BWB00155
UNZIP Failed on following file :

Explanation

An unzip has failed on the transferred file. SCLM DT uses the Java JAR command to unzip (unjar) this file.

User response

The Systems Programmer should ensure a valid Java path exists in rsed.envvars and check for space problems within the user's WORKAREA directory.
BWB00156
ZIP File copied

Explanation

This is an informational message.

User response

None.
BWB00157
Unable to delete HFS file :

Explanation

The cleanup routine to delete HFS workarea files after operation has completed has failed.

User response

Systems programmer should check listed file and delete/remove manually if desired.
BWB00158
Select DETAILS>> button for build messages, reports, listings

Explanation

This is an informational message.

User response

Select DETAILS to view build messages, reports and listings.
BWB00159
Select DETAILS>> button for promote messages and reports

Explanation

This is an informational message.

User response

Select DETAILS to view promote messages, reports and listings.
BWB00160
Failed read of migrate job dataset

Explanation

The temporary skeleton file that is used for creating the batch job could not be read: USERID.SCLMDT.DTSKEL. Migration processing terminates.

User response

Review the operations log for additional error messages.
BWB00161
*** Temporary recover data set allocation failed ***

Explanation

In version processing a temporary recovery data set: USERID.SCLMDT.FORMAT.DTnnnn could not be allocated.

User response

Systems programmer should review the MVS log for any data set allocation failures.
BWB00162
ANT build failure

Explanation

In a Java or J2EE build an error has occurred running the ANT script in HFS. This may just be Java compile errors.

User response

Review the ANT build listing returned in the operations log to resolve any build errors.
BWB00163
Review ANT Listing in Log

Explanation

This is an informational message.

User response

Review the listing.
BWB00164
Review failure - Build continues

Explanation

A copy of a member from an MVS data set to a HFS file has failed. Build processing continues.

User response

Review the operations log for further error messages.
BWB00165
Member account record deleted from development group

Explanation

During a checkout (lock) an SCLM member account record was created in the development group. The unlock or lock failure results in the account record being deleted.

User response

None.
BWB00166
ADD new member cancelled as member exists at group :

Explanation

An add new member was attempted but the member already resides up the group hierarchy chain. Processing terminates.

User response

None.
BWB00167
Error in short name translation

Explanation

An error has occurred in translating the longname file to an SCLM host shortname. This is often the result if a error in the installation of the SCLM Developer Toolkit components on the host, or an inability to read the translation file (LSTRANS) at the host.

User response

Review the operations log for further error messages.
BWB00168
Ensure check-in member was not an empty file

Explanation

A codepage translation error occurred when saving a file/member. Ensure the file saved was not an empty file.

User response

Check that the file was not empty. Otherwise, review operations log for further error messages.
BWB00169
Member being migrated already exists - not migrated. Member:

Explanation

A member was selected to be migrated but already exists in the group hierarchy chain.

User response

Use normal EDIT/checkout processing, otherwise use the migrate command with the force flag set. Warning: This is not advised, because previous versions of the member may be overwritten.
BWB00170
Error threshold of 5 errors reached in ASCII/EBCDIC conversion

Explanation

An error threshold of 5 members being migrated has resulted in codepage conversion errors. Migrate processing terminates.

User response

Review the operations log to determine errors with migrated members.
BWB00171
No members selected to copy and migrate

Explanation

There were no valid members selected to be migrated into SCLM. Processing terminates.

User response

If this is an error then review the operations log for further error messages.
BWB00172
Promote has Failed - Check Promote messages

Explanation

The promote has failed. Promote messages will be returned in the log or reside in the promote messages data set if specified in the request.

User response

Review the failing messages.
BWB00173
ERROR - Unable to allocate temp translate data set

Explanation

For migrate and import the files requiring long/short name conversion are written to a temporary sequential data set DD LSTRNPRC of attributes SPACE(1,1) RECFM=VB LRECL=1036 UNIT=VIO. This data set could not be allocated. Processing terminates.

User response

Systems Programmer should check the MVS SYSLOG for any data set allocation errors or violations.
BWB00174
ERROR - In translate table routine : FLMLSTRAN

Explanation

A shortname longname translation has occurred calling the translate module FLMLSTRAN. Additional error messages will be displayed.

User response

Review the operations log for additional error messages and reasons provided.
BWB00175
No associated long names will be displayed

Explanation

A previous error in retrieving longnames has occurred and any longnames associated with an SCLM host shortname will not be displayed in the project view.

User response

Review the operations log for other error messages pertaining to translation services.
BWB00176
WARNING in EBCDIC/ASCII conversion. Unprintable characters or empty file

Explanation

An EBCDIC to ASCII codepage translation error has occurred. Likely causes are unprintable special characters or an empty file.

User response

View the member being translated. Special characters or null characters (X'00') may cause this error when browsing/editing a file.
BWB00178
Warning - Unable to allocate data set:

Explanation

Failure in allocating data set on z/OS host.

User response

Review operations and MVS systems log for further error messages . Contact your SCLM administrator for assistance.
BWB00179
No records returned for DBUTIL report

Explanation

An SCLM DBUTIL report was run for this function call but failed to return any records.

User response

Warning only - Review your filters or parameters in request.
BWB00180
Accounting record and Build map deleted for member:

Explanation

The SCLM accounting record and build map have been deleted for that member at the requested group.

User response

None. This is an informational message only.
BWB00181
Failed allocation of DBUTIL parameter data set:

Explanation

Failure in allocating data set userid.SCLMDT.VCMISPF.IDnnnnnn on z/OS host. Function failed.

User response

Review operations and MVS systems log for further error messages. Contact your SCLM administrator for assistance.
BWB00182
Failed read of DBUTIL parameters

Explanation

Failure in read of temporary data set userid.SCLMDT.VCMISPF.IDnnnnnn. Function failed.

User response

Review operations and MVS systems log for further error messages. Contact your SCLM administrator for assistance.
BWB00183
Selected file does not exist in SCLM project

Explanation

The CLASS, JAR, WAR, or EAR specified in the request was not located in the SCLM project hierarchy.

User response

Review your file name requested . Re-run the request.
BWB00184
Invalid classpath directory

Explanation

The CLASS, JAR, WAR, or EAR specified in the request was not located in the SCLM project hierarchy.

User response

Ask the System administrator to check in the z/OS Unix systems services that the directory specified exists. Also check that write access permissions on that data set for your userid are set.
BWB00185
Read of member $GLOBAL of type J2EEBLD failed

Explanation

Failure in trying to read the member $GLOBAL that should reside in SCLM type J2EEBLD.

User response

Ensure a $GLOBAL member exists in the SCLM project hierarchy in SCLM type J2EEBLD. Contact your SCLM administrator for assistance.
BWB00186
Ensure variables CGI_DTCONF, CGI_DTWORK, ANT_BIN and JAVA_BIN are set in $GLOBAL

Explanation

One of the above property variables is not set in $GLOBAL. Function cancelled.

User response

Check that all property variables are set and the format is correct. Re-run the request. Contact your SCLM administrator for assistance.
BWB00187
Error reading J2EE build script member

Explanation

There was a failure on reading the J2EE build script member specified in Type J2EEBLD.

User response

Review the operations log for further details on the build script. Ensure that build script which is referenced by the ARCHDEF keyword SINC exists in the SCLM project in type J2EEBLD. Contact your SCLM administrator for assistance.
BWB00188
Variable SCLM_ARCHDEF not set in build script member

Explanation

The property variable SCLM_ARCHDEF is not set in the J2EE build script or the format is incorrect.

User response

Review the operations log to read the J2EE build script mentioned. Ensure that property is set and re-run the function request.
BWB00189
ANT build failed - Review ANT Listing in log

Explanation

The JAVA/J2EE build has failed in the ANT build step on z/OS.

User response

Review the ANT listing which will list the compilation or build errors . Rectify project errors and re-run.
BWB00190
Variable SCLM_ANTXML not set in build script member

Explanation

The property variable SCLM_ANTXML was not set in the build script or the format was wrong.

User response

Ensure the variable is set. SCLM_ANTXML should reference a skeleton ANT XML member in type J2EEBLD.
BWB00191
Error copying ANT XML member into HFS

Explanation

An error occurred while copying the ANT XML member into the z/OS Unix file system for processing.

User response

Review the operations log for further errors. This copy is part of the build process. Contact your SCLM administrator for assistance.
BWB00192
Error reading Translation configuration file TRANSLATE.conf

Explanation

There was an error in reading the TRANSLATE.conf configuration file located in the SCLM DT CONFIGURATION directory in the z/OS Unix file system.

User response

Ask the systems administrator to check that a valid TRANSLATE.conf exists at the configuration directory (by default /var/rdz/sclmdt/CONFIG ). Contact your SCLM administrator for assistance.
BWB00193
Errors in copying source members to HFS for build

Explanation

There was an error in copying SCLM source members into the z/OS Unix file system for processing.

User response

Review the operations log to determine the members that failed. Ensure these members exist in SCLM . Review the MVS systems log for further error messages. Contact your SCLM administrator for assistance.
BWB00194
Errors in processing HL architecture definition includes

Explanation

Errors occurred while processing an INCL ARCHDEF within the ARCHDEF.

User response

Check with the SCLM administrator that the included ARCHDEF is valid. Review the operations log for further error messages.
BWB00195
Error on account record call (ACCTINFO) for J2EEBLD member

Explanation

Error occurred on an SCLM ACCTINFO function request on the member.

User response

Ensure the member has a valid SCLM account record. It is possible the member may be corrupted. Contact your SCLM administrator for assistance.
BWB00196
No JAR, WAR, or EAR property name set in Build script

Explanation

The function was expecting either JAR_FILE_NAME, WAR_NAME, or EAR_NAME properties to be set in build script.

User response

Check the nature of the project and ensure a valid property variable is set for that project in the build script.
BWB00197
Error in storing JAR, WAR or EAR details in profile variable

Explanation

Internal error in build process occurred while storing archive file information in an ISPF profile variable.

User response

Review operations log for further error messages such as JAR, WAR or EAR was not created or other build failures. Contact your SCLM administrator for assistance.
BWB00198
BWBJ2OBJ - no generated Jar, War, or Ear found

Explanation

The ARCHDEF translator J2EEOBJ could not locate a generated JAR WAR or EAR to store back into SCLM.

User response

Review the operations log for other build failure messages. Contact your SCLM administrator for assistance.
BWB00199
BWBJ2OBJ - LISTING file not copied to SCLM

Explanation

Error encountered in copying build listing file into SCLM . Error occurred in ARCHDEF translator J2EEOBJ.

User response

Review the operations log for other build failure messages. Contact your SCLM administrator for assistance.
BWB00200
BWBJ2OBJ - Error in copying Jar, War, or Ear into SCLM

Explanation

There is an error in the copy of the generated archive object (JAR, WAR,EAR) from z/OS Unix file system into SCLM.

User response

Review the operations log for other build failure messages. Contact your SCLM administrator for assistance.
BWB00201
Error copying object file from SCLM to HFS

Explanation

An error occurred during the copy from SCLM of a class, JAR, WAR, or EAR into the classpath directory specified as part of the function request.

User response

Review the operations log for other error messages. From the log determine the SCLM file and ensure the member is valid. Check that the destination classpath directory in the z/OS Unix Systems file system exists and write permissions are set. Contact your SCLM administrator for assistance.
BWB00202
Error encountered for property SCLM_ANTXML in build script

Explanation

An error occurred while copying the customized ANT script referenced by property SCLM_ANTXML from SCLM into the z/OS Unix Services file system in the ANTCOPY procedure of the build.

User response

Review the operations log for further error messages. Ensure the member referenced by property SCLM_ANTXML in the build script exists in the SCLM hierarchy. Contact your SCLM administrator for assistance.
BWB00204
Warning - File(s) copied from higher in hierarchy than selected development group

Explanation

The selected member was not found in the users development group but retrieved from further up the group hierarchy in SCLM.

User response

This is an informational message. The Messages or operations log should detail what group the member was retrieved from.
BWB00205
Invalid J2EE INCL architecture definition (no SINC keyword specified)

Explanation

An INCL ARCHDEF was found inside the J2EE ARCHDEF which was not a valid J2EE ARCHDEF. This was determined not to be a valid JAVA/J2EE ARCHDEF because the SINC keyword was missing. Processing terminates.

User response

Validate that the INCL ARCHDEF is a JAVA/J2EE ARCHDEF . Ensure the format of the ARCHDEF is correct (Valid SINC , LKED, & OUT1 keywords).
BWB00206
Member referenced by SCLM_ANTXML in build script not found

Explanation

The member referenced by property variable SCLM_ANTXML in the JAVA/J2EE build script was not found in the SCLM hierarchy.

User response

Ensure a valid member exists in the SCLM hierarchy and resides in SCLM type of J2EEBLD.
BWB00207
Verification error from SCLM user exit routine (CCVFY or VERCC)

Explanation

A change code verification user exit (CCVFY or VERCC) indicated that an invalid change code was entered for the operation.

User response

Check the log for any messages the local user exit may have provided. If the problem is not visible from the messages returned by the user exit, contact your SCLM project administrator for assistance.
BWB00208
Report MODE only selected for DEPLOY

Explanation

The user has initiated a DEPLOY in report mode only. Information on the Deploy script, destination, and selected options will be returned. No Deploy processing takes place.

User response

None. This is an informational message only.
BWB00209
Error reading J2EE Deploy script member

Explanation

Error reading J2EE Deploy script member

User response

Ensure the selected Deploy script exists and is valid in the SCLM hierarchy and resides in SCLM type J2EEBLD. Contact your SCLM administrator for assistance.
BWB00210
EAR file deployed from selected group

Explanation

The EAR file was successfully deployed from the selected group.

User response

None. This is an informational message only.
BWB00211
Deploy of EAR file has failed

Explanation

The Deploy of the selected EAR file has failed.

User response

Review the operations log for further error details. Contact your SCLM administrator for assistance.
BWB00212
Review deploy listing if available

Explanation

The Deploy listing is the listing output from the ANT deploy script.

User response

Review the Deploy listing in the operations log for detailed information regarding success or failure of the deploy operation.
BWB00213
Deploy of EAR file successful

Explanation

The Deploy of the selected EAR has been successful.

User response

Review the messages or operations log for further information regarding the Deploy operation.
BWB00214
Error in copying Deploy ANT XML to z/OS HFS

Explanation

An error occurred while copying the dynamically customized deploy ANT script from SCLM into the z/OS Unix Services file system for processing.

User response

Review the operations log for further error messages. Contact your SCLM administrator for assistance.
BWB00215
Error allocating Translate table

Explanation

An error occurred while trying to allocate the short name / long name translate table in the deploy function.

User response

Reason messages regarding this error will be found in the operations log. Either ensure variable TRANTABLE in $GLOBAL is set, or check the data set referenced by variable TRANTABLE is correct. Contact your SCLM administrator for assistance.
BWB00217
Warning - No Datasets returned on filter:

Explanation

The catalog search routine failed to return any data sets on the user's requested data set filter.

User response

Revise the data set filter used and re-run.
BWB00218
Warning - No Members returned on filter:

Explanation

No members were returned from the data set using the selected member filter.

User response

This is an informational message. If required, revise selected filters.
BWB00219
Severe error in Library Management routines

Explanation

While trying to list members by filter from the selected data set, the Library managements services routines returned an error.

User response

Review the Operations log for further error messages. Review your member filter and re-run. Contact your SCLM administrator for assistance.
BWB00220
User not authorized for requested build

Explanation

Build security is on for this project, and the requesting userid does not have security access for this selected build request. Processing terminates.

User response

Check with the SCLM security administrator.
BWB00221
User not authorized for requested promote

Explanation

Promote security is on for this project, and the requesting user ID does not have security access for this selected promote request. Processing terminates.

User response

Check with the SCLM security administrator.

Host messages for CRASTART

These host messages pertain to CRASTART in Rational Developer for z Systems.

CRAD0001I
Config File:{1}

Explanation

This message shows the configuration file name from which CRASERV receives the commands to run.

Response

No response is required.
CRAD0002I
Config handle {1}

Explanation

This message shows the hhhh internal file number, which is associated with a reading of the CRASERV configuration file. The config handle is for diagnostic purposes only.

Response

No response is required.
CRAD0003I
A:{1} {2}

Explanation

This message displays the standard command that is read from the CRASERV configuration file. This is a diagnostic message.

Response

No response is required.
CRAD0004I
C:{1}

Explanation

This message displays the dynamic allocation command that was read from the CRASERV configuration file. This is a diagnostic message.

Response

No response is required.
CRAD0005I
{1} OPEN

Explanation

This message displays the dddddddd value that CRASERV uses as a ddname.

Response

If the ddname is not the same as is expected, verify that the correct ddname is specified in the CRASERV configuration file.
CRAD0006I
P:{1} {2}

Explanation

This message displays the program invocation command that was read from the CRASERV configuration file. This is a diagnostic message.

Response

No response is required.
CRAD0007I
{1} Attach

Response

No response is required.
CRAD0008I
{1} {2}

Explanation

This message displays the program name (cccccccc) and parameters (p1 and p2) that CRASERV is about to run. This is a diagnostic message.

Response

Verify that any variable substitutions are correct.
CRAD0009I
CRASERV ended by user initiated disconnect.

Explanation

A CARMA user explicitly ended his or her connection.

Response

No response is required.
CRAD0010I
CRASERV ended due to a normal timeout.

Explanation

A CARMA user's session timed out after inactivity.

Response

No response is required.
CRAD0011I
Referback {1}

Explanation

A dynamic allocation was completed for the dsname data set by using a referback.

Response

See the previous allocation statement for details about the referback.
CRAD1001W
{1} Returned {2}, May be ABEND {3}

Explanation

A program started by CRASTART ended with an aaaaa return code, which might indicate a bbb abend code.

Response

This might not indicate a problem, but if the started program did not complete correctly, diagnose the failing program by using the bbb abend code.
CRAD1002W
{1}

Explanation

The content of this returned message comes from dynamic allocation (BPXWDYN) that CRASERV called.

Response

Your response depends on the message contents.
CRAD1003W
DYNALLOC return {1}

Explanation

This message shows the cccc return code from dynamic allocation (BPXWDYN) that CRASERV called.

Response

Your response depends on the message contents.

Host messages for Application Deployment Manager

These are the host messages that pertain to Application Deployment Manager (ADM) in Rational Developer for z Systems.

The messages in this section are not shown to you on a workstation. They exist only in the CICS log on the host system.

CRAZ1650E
Router GET CONTAINER failure

Explanation

An error occurred while processing a web service request.

User response

No user response is required.

Administrator response

See the CICS documentation for RESP and RESP2 codes of the GET CONTAINER service.
CRAZ1651E
Router PUT CONTAINER failure

Explanation

An error occurred while processing a web service request.

User response

No user response is required.

Administrator response

See the CICS documentation for RESP and RESP2 codes of the PUT CONTAINER service.
CRAZ1652E
ADNREST Write HTTP header error

Explanation

An error occurred writing an HTTP header.

User response

No user response is required.

Administrator response

See the CICS documentation for WEB WRITE to evaluate the RESP and RESP2 codes.
CRAZ1653E
ADNREST Web Send error

Explanation

An error occurred writing an HTTP header.

User response

No user response is required.

Administrator response

See the CICS documentation for WEB SEND to evaluate the RESP and RESP2 codes.
CRAZ1654E
ADNREST CRDserver Link error

Explanation

An error occurred writing an HTTP header.

User response

No user response is required.

Administrator response

See the CICS documentation for LINK to evaluate the RESP and RESP2 codes.
CRAZ1655E
ADNREST Assign error

Explanation

An error occurred during an ASSIGN USERID() operation.

User response

No user response is required.

Administrator response

See the CICS documentation for ASSIGN to evaluate the RESP and RESP2 codes.
CRAZ1656E
ADNREST Extract error

Explanation

An error occurred during a WEB EXTRACT operation.

User response

No user response is required.

Administrator response

See the CICS documentation for WEB EXTRACT to evaluate the RESP and RESP2 codes.
CRAZ1657E
ADNREST Read HTTP header error

Explanation

An error occurred during a WEB READ operation.

User response

No user response is required.

Administrator response

See the CICS documentation for WEB READ to evaluate the RESP and RESP2 codes.

Host messages for Common Access Repository Manager (CARMA)

The following host messages pertain to the Common Access Repository Manager (CARMA) in Rational Developer for z Systems.

CRRZC0020E
Internal Error: {0}

Explanation

{0}
An error message.
The CARMA server encountered an unexpected internal error.

User response

Confirm that the VSAM files are correct. If you modified the VSAM file, verify that you followed the guidelines in the CARMA Developer's Guide. Otherwise, verify that the files were created properly by using the directions in the Host Configuration Guide.
CRRZC0022E
No RAMs defined for this locale

Explanation

There are no RAMs defined that are associated with the current language.

User response

Do one of the following actions:
  • In the client, change the language locale that is used by CARMA.
    1. Disconnect from the CARMA connection.
    2. Right-click the disconnected CARMA connection, and select Properties.
    3. In the Remote Locale menu, select a locale that is supported by the RAM.
  • On the remote system, the systems programmer can update the configuration VSAM files on the remote system as defined in the CARMA Developer's Guide to support the additional locale.
CRRZC0024E
CRADEF could not be opened for reading

Explanation

The CARMA server was unable to open the CRADEF VSAM file for reading.

User response

Have your systems programmer confirm that the file exists and is accessible from the user's account.
CRRZC0025E
CRASTRS could not be opened for reading

Explanation

The CARMA server was unable to open the CRASTRS VSAM file for reading.

User response

Have your systems programmer confirm that the file exists and is accessible from the user's account.
CRRZC0026E
No RAM records found in CRADEF

Explanation

No RAMs are defined in the CRADEF configuration VSAM file on the remote system.

User response

Do one of the following actions:
  • Have your systems programmer re-create the CRADEF VSAM file from the source files as described in the Host Configuration Guide.
  • Define a RAM in the CARDEF as described in the CARMA Developer's Guide.
CRRZC0028E
CRADEF read error

Explanation

The CARMA server encountered an error while it was reading the CRADEF configuration file.

User response

On the client, disconnect from CARMA, reconnect, and try again. If the problem persists, have your systems programmer verify that the file is accessible from the user's account.
CRRZC0032E
Invalid CRADEF record found: {0}

Explanation

{0}
An eight-character string that is the name of the record.
The specified VSAM record in the CRADEF file is invalid.

User response

Have your systems programmer correct the specified record. For more information about the correct record format, see the CARMA Developer's Guide.
CRRZC0034E
Requested RAM not found: {0}

Explanation

{0}
The RAM ID number.
The Rational Developer for z Systems client tried to connect to a RAM that is not defined on the remote system.

User response

In the client, disconnect the CARMA connection and restart the workspace. Then, connect to the CARMA connection before you try any other actions. If the RAM you require is no longer listed, contact the systems programmer. The RAM might be removed or the RAM ID number might be changed.
CRRZC0036E
Could not load RAM module: {0}

Explanation

{0}
The RAM load module.
The CARMA server was unable to load the RAM load module.

User response

Have your systems programmer confirm the following information:
  • The RAM load module exists.
  • It is accessible from CARMA.
  • It is accessible from the user's ID.
  • It is a properly compiled DLL.
CRRZC0038E
Could not load pointer to RAM function: {0}

Explanation

{0}
A RAM function.
The RAM does not have the specified function.

User response

If the function is required, recompile the RAM with the required function. For more information about developing a RAM, see the CARMA Developer's Guide.
CRRZC0040E
Requested RAM ({0}) has not been loaded

Explanation

{0}
The RAM ID.
The function was not called because the compiled RAM was not loaded by CARMA on the remote system.

User response

Disconnect, reconnect, and try the action again. If you are using a custom remote system client, have your systems programmer verify that the initRAM function was called. If the problem persists, contact IBM Software Support.
CRRZC0042E
Invalid CRASTRS record found: {0}

Explanation

{0}
A CRASTRS record.
The CRASTRS record that is specified is invalid.

User response

Have your systems programmer or RAM developer, if you are using a custom RAM, verify that the CRASTRS VSAM file was properly created and that the specified record is correct.
CRRZC0044E
CARMA has not been initialized

Explanation

The initCARMA function was not initialized.

User response

Disconnect, reconnect, and try the action again. If you are using a custom remote system client, verify that the initCARMA function was called. If the problem persists, contact IBM Software Support.
CRRZC0046E
Failed attempting to load the RAM list

Explanation

CARMA did not successfully load the RAM list.

User response

Disconnect, reconnect, and try the action again.
CRRZC0048E
Out of memory

Explanation

The CARMA address space is out of memory.

User response

Have your systems programmer increase the memory that is allocated to CARMA address spaces.
CRRZC0050W
Record {0} in CRADEF does not have equivalent in CRASTRS for this locale

Explanation

{0}
A record name.
The specified record is not defined in the CRASTRS file for the current locale.

User response

This message is only a warning and does not require any action by the user.

If local specific strings are required for this record, then create an appropriate record in the CRASTRS file to provide the strings. A CRASTRS record can also be created to stop this warning from being written to the log files. Contact your systems programmer for these modifications.

If you are experiencing these errors while you are using the CA Endevor RAM, have your systems programmer install APAR PM56551 to fix this problem.

CRRZC0052E
Action {0} references unknown parameter

Explanation

{0}
An action name.
One or more parameters that are referenced by the specified action do not exist in the CRADEF VSAM file.

User response

Have your RAM developer add any missing parameters to the CRADEF VSAM file.
CRRZC0054E
Action {0} references unknown return type

Explanation

{0}
An action name.
One or more return types that are referenced by the specified action do not exist in the CRADEF VSAM file.

User response

Have your RAM developer add any missing return types to the CRADEF VSAM file.
CRRZC0056E
CRASTRS read error

Explanation

The CARMA server encountered an error while it was reading the CRASTRS configuration file.

User response

On the client, disconnect from CARMA, reconnect, and try again. If the problem persists, have your systems programmer verify that the file is accessible from the user's account.
CRRZC0058E
Neither the specified locale nor EN_US 00037 could be found in CRASTRS

Explanation

CARMA could not find a locale to use for this RAM.

User response

Have your systems programmer or RAM developer confirm that the CRASTRS VSAM file was properly created. If the problem persists, do one of the following actions:
  • Have your RAM developer create the missing locales in the CRASTRS VSAM file.
  • Change the properties on the CARMA connection to use the locale that is specified by the RAM.
To change the language locale that is used by CARMA in the client:
  1. Disconnect from the CARMA connection.
  2. Right click the disconnected CARMA connection, and select Properties.
  3. In the Remote Locale menu, select a locale that is supported by the RAM.
CRRZC0060E
CRAMSG not found

Explanation

CARMA was unable to find the CRAMSG VSAM file.

User response

Have your systems programmer confirm that the file exists and is accessible from the users account.
CRRZC0062E
CRAMSG read error

Explanation

The CARMA server encountered an error white it was reading the CRAMSG configuration file.

User response

On the client, disconnect from CARMA, reconnect, and try again. If the problem persists, have your systems programmer verify that the file is accessible from the user's account.
CRRZC0064E
CRADEF error: Action 16 can not have custom parameters and/or returns

Explanation

Action 16 is the performAction function and is used to call custom actions in CARMA. The parameters that are associated with the called custom action are used as parameters to action 16. Providing your own custom parameters and returns interferes with the passing of the custom action that is called, and is not allowed.

User response

Have the RAM developer remove the VSAM record for action 16 from CRADEF.
CRRZC0066E
Invalid type specified in VSAM record {0}

Explanation

{0}
A VSAM record name.
The type that is specified in the VSAM record is invalid.

User response

Have your RAM developer update the VSAM record file to have one of the following types: "STRING", "DOUBLE", "LONG", or "INT."
CRRZC0068E
Invalid default value in VSAM record {0}

Explanation

{0}
A VSAM record name.
The default value for the VSAM record is invalid.

User response

Have your RAM developer ensure that the default value of the VSAM record matches the type and length that is specified for that record.
CRRZC0101E
Could not allocate memory

Explanation

The RAM was unable to allocate memory.

User response

Have your systems programmer increase the memory that is allocated to CARMA address spaces.
CRRZC0102E
TSO/ISPF Library functions not available

Explanation

The TSO or ISPF library function is not available to the RAM.

User response

Have your systems programmer confirm that the TSO and ISPF environments are properly started with the CARMA server. This process is explained in the Host Configuration Guide.
CRRZC0103E
Invalid member identifier

Explanation

The member identifier that is provided to the RAM is incorrect or out of date. This problem can occur because the RAM was updated, or the RAM developer changed the way RAM IDs are represented to the CARMA server.

User response

In the client, refresh the parent container and try the action again. If the problem persists, contact your RAM developer.
CRRZC0104E
Cannot allocate (out of space)

Explanation

The RAM was unable to allocate memory.

User response

Have your systems programmer increase the memory that is allocated to CARMA address spaces.
CRRZC0105E
Member not found

Explanation

The RAM was unable to locate the requested number.

User response

In the client, refresh the parent container and try again. If the problem persists, contact your RAM developer.
CRRZC0106E
Instance not found

Explanation

The RAM was unable to locate the requested instance.

User response

In the client, refresh the RAM and try again. If the problem persists, contact the RAM developer.
CRRZC0107E
Function not supported

Explanation

The requested function is not supported by the RAM.

User response

No action is required.
CRRZC0108E
Member is not a container

Explanation

The function that was called expected a container as a parameter, and instead it received a member.

User response

In the client, refresh the parent container and try the action again. If you are using a custom remote system client, notify the developer. If the problem persists, notify your RAM developer.
CRRZC0109E
Invalid parameter value

Explanation

A parameter with an invalid value was passed to the action.

User response

Confirm that all parameters contain the correct values and try the action again.
CRRZC0110E
Member cannot be updated

Explanation

The target member was unable to update successfully.

User response

In the client, disconnect, reconnect, and try the action again. If the problem persists, specify a different target member. If the problem still persists, contact your RAM developer.
CRRZC0111E
Member cannot be created

Explanation

The member was not successfully created.

User response

In the client, attempt to do the following steps:
  1. Refresh the parent container and confirm that the member is not already present.
  2. Disconnect, reconnect, and try the create the member again.
  3. Try to create a different member under a different container.
If the problem persists, contact your RAM developer.
CRRZC0112E
Not authorized

Explanation

The user is not authorized to do this action.

User response

If you think this message is in error, disconnect, reconnect, and try the action again. If the problem persists, contact your RAM developer.
CRRZC0113E
Could not initialize

Explanation

The RAM did not initialize.

User response

In the client, disconnect from CARMA, reconnect, and try again. If you are still unable to do the action, have your systems programmer confirm that you have access to all files that are needed by the RAM. If you still experience problems, contact your RAM developer.
CRRZC0114E
Could not terminate

Explanation

The RAM was unable to terminate properly.

User response

No action is required.
CRRZC0115E
Resource out of sync

Explanation

The RAM is reporting that the resource is out of sync.

User response

Refresh the parent container, and try the action again. If the problem persists, contact your RAM developer.
CRRZC0116E
File locked

Explanation

The file is locked and is most likely in use by another user or process.

User response

You can wait until the file is freed and try again. Additionally, verify that you have the correct permissions to access the file.
CRRZC0117E
Specified next record out of range

Explanation

The client is requesting a starting record number that does not exist. The client is calling the extractMember function, which retrieves chunks of records that start with a specific record number. In this case, the starting record number parameter is an invalid number that does not correspond with a record number.

User response

In the client, attempt to open the file again. If the problem persists, contact your RAM developer. If you are using a custom remote system client, contact your client developer.
CRRZC0118E
Unsupported record format

Explanation

The target member has a record format that is unsupported by this RAM.
Note: If you are using the sample RAMs provided with CARMA, they do not support the 'U' (undefined) record format.

User response

If you are using the sample RAMs provided with CARMA, work with members that have a record format of FB (fixed block) or VB (variable block).
CRRZC0119E
Invalid LRECL

Explanation

LRECL is the length of the record. For the RAM putMember function, the client specifies the maximum length of the record. For the RAM createMember function, the length of the record of the created member is returned. For some reason, the length of the record is invalid.

User response

Download a new copy of the file from the RAM, and try the action again. If the problem persists, contact your RAM developer.
CRRZC0120E
Invalid metadata key

Explanation

The metadata key is the key in a key-value pair to a property of a CARMA resource. The requested key is not valid.

User response

Refresh the properties of the CARMA resource. If the problem persists, contact the RAM developer.
CRRZC0121E
Cannot update property value

Explanation

The property value was unable to update. It is most likely read only.

User response

No action is required.
CRRZC0122E
Invalid metadata value

Explanation

The metadata value was invalid.

User response

Try the operation again with a valid metadata value. If you are unsure of correct metadata values, contact your RAM developer.
CRRZC0123E
Property value is read-only

Explanation

The target metadata value is read-only and cannot be updated.

User response

No action is required.
CRRZC0124E
Requested member is empty

Explanation

The RAM attempted to open a member that was empty.

User response

If you believe that this message is in error, contact your RAM developer.
CRRZC0125E
Empty instance

Explanation

The repository instance was unable to expand because it was empty.

User response

No action is required.
CRRZC0126E
No members found

Explanation

The container was unable to expand because it was empty.

User response

No action is required.
CRRZC0127E
Reset error

Explanation

An error occurred while the CARMA server was resetting the RAM.

User response

In the client, disconnect and reconnect from CARMA and try the action again. If the problem persists, contact your RAM developer.
CRRZC0128E
Delete error

Explanation

The RAM encountered an error it was trying to complete a Delete operation.

User response

In the client, refresh the parent container to confirm that the delete was unsuccessful and try again.
CRRZC0129E
Member/Version is read-only

Explanation

Version is a previous view of the member in the CARMA Version History view. The target member or version is read-only.

User response

No action is required.
CRRZC0130E
Versioning not supported on member

Explanation

The selected CARMA member does not support the Show History action. This message does not mean that the Show History action is disabled for all members.

User response

No action is required.
CRRZC0196E
Could not setup ISPF variables

Explanation

The RAM encountered an error it was trying to access ISPF variables.

User response

In the client, disconnect from CARMA, reconnect, and try again. If the problem persists, confirm that the ISPF system is properly set up at CARMA startup by reviewing the Host Configuration Guide.
CRRZC0197E
(encapsulated ISPF/LMF error message)

Explanation

The RAM encountered an error from an ISPF or LMF system call. This ISPF or LMF error message is provided by the RAM.

User response

Check the response to the ISPF or LMF message that is included. Additionally, confirm that the ISPF or LMF system is properly set up at CARMA startup by reviewing the Host Configuration Guide.
CRRZC0198E
Unable to access log file

Explanation

The RAM was unable to access the log file.

User response

Confirm that the CARMALOG is properly set up and that the user has access to the log file. If the problem persists, contact your RAM developer.
CRRZC0199E
Unknown RAM error

Explanation

The RAM encountered an unexpected error.

User response

In the client, disconnect from CARMA, reconnect, and try again. If the problem persists, contact your RAM developer.
CRRZC4011W
Could not load RAM. Not adding it to the list.

Explanation

The initRAM function call cannot be completed successfully, so the RAM was not loaded.

User response

If the failed RAM is not required, no action is required. Otherwise, make sure that the VSAM configuration is correct and that the target RAM is accessible to the CARMA user. If you are using a custom RAM, make sure that the initRAM function is operating as expected. Check the CARMALOG or job spool for RAM initialization errors.
CRRZC4038W
Could not terminate the RAM.

Explanation

The terminateRAM function call returned an error from the RAM. If the RAM has state information that must be saved, this error can cause problems.

User response

If you are using a non-custom RAM, no action is required . If you are using a custom RAM, check with your RAM developer to verify that this error is not a problem.
CRRZC4039I
Custom action {0} disabled.

Explanation

{0}
The ID of a custom action.
The action with the displayed action ID was disabled in the configuration VSAM file.

User response

No action is required. You can find a list of action IDs in the Rational Developer for z Systems CARMA Developer's Guide.
CRRZC4040I
VSAM record {0} requires '|' after parameter list for 6.0.1.x compatibility

Explanation

The specified VSAM action record does not have a '|' character after the list of parameters, or has an empty parameter and return list. Earlier versions of CARMA required the separating character even if a return list was not specified.

User response

No action is required.
CRRZC4041W
Warning: {0} Perform Action (id=16) can not be disabled

Explanation

The VSAM configuration erroneously tries to disable the performAction call, which is used to call custom actions. This action cannot be disabled in the VSAM configuration.

User response

Have your RAM developer remove the record to disable action 16. Have your RAM developer confirm that the record to disable action 16 was not a typographical error and that the correct action IDs are disabled. A list of action IDs can be found in the Rational Developer for z Systems CARMA Developer's Guide.
CRRZC4042W
Warning: Attempt to disable action that does not exist in VSAM record {0}

Explanation

{0}
the VSAM record name
The VSAM configuration erroneously tries to disable an action that does not exist. This situation can occur when you are using an earlier version of the CARMA remote system code, where the disabled action is not yet supported.

User response

Have your RAM developer confirm that the correct action IDs are disabled.
CRRZC4043W
Warning: No prompt given for VSAM record {0}

Explanation

A prompt was not supplied for the custom parameter. CARMA uses the custom parameter name in place of the prompt when it is asking for the custom parameter.

User response

If you want a prompt, have your RAM developer add it to the VSAM record.
CRRZC4044W
Warning: No description given for VSAM record {0}

Explanation

A description was not provided for the custom parameter.

User response

No action is required, but if you want a description, have your RAM developer add it to the custom parameter.
CRRZC4045W
Warning: Could not find RAM(s) for locale {0}, using default locale of EN_US 00037

Explanation

No RAMs were found that use the specified locale. CARMA is using the default locale instead. A RAM is enabled only for the locales specified. This action allows RAM developers to release multiple versions for different locales, and display only one at a time to the user.

User response

Specify a different locale under the CARMA connection properties. If you do not want to use RAMs for the default locale, have your RAM developer add support for your locale.
CRRZC4050I
RAM {0} does not support function {1} ({0})

Explanation

The specified function is not supported by the RAM. New functions added to the CARMA API can cause this condition. This condition is not an error.

User response

No action is required. To remove this error message, have your RAM developer either implement the new functions or disable them in the configuration VSAM files.

Host messages for Code Review for COBOL and PL/I

These are the host messages that pertain to Code Review in Rational Developer for z Systems.

The messages in this section are not shown to you on a workstation. They exist only in the workspace log on the host system.

CRRZW0000E
An error occurred while reading the rule file {0}. Error message: {1}

Explanation

The code review application cannot read the rule file.

User response

  1. Verify that the path of the rule file is specified correctly in the input data.
  2. Verify that the rule file exists in the specified directory, that the user has permission to access it, and that it contains readable text encoded in UTF-8 format.
  3. If the problem persists, export the rule file again and upload it to z/OS UNIX System Services.
CRRZW0001E
An error occurred while closing the rule file {0}. Error message: {1}

Explanation

The code review application cannot close the rule file.

User response

  1. Verify that the path of the rule file is specified correctly in the input data.
  2. Verify that the rule file exists in the specified directory, that the user has permission to access it, and that it contains readable text encoded in UTF-8 format.
  3. If the problem persists, export the rule file again and upload it to z/OS UNIX System Services.
CRRZW0002E
An error occurred while transferring PDS members to the workspace.

Explanation

The code review application transfers the members of the PDS to an Eclipse workspace in z/OS UNIX System Services for processing. An error occurred during a member transfer.

User response

  1. Verify that PDS and the path of the workspace are specified correctly in the input data.
  2. Verify that the PDS members exist and that the user has permission to access the PDS.
  3. Verify that the workspace exists and that the user has permission to access it.
CRRZW0003E
An error occurred while retrieving the PL/I include file {0}. Error message: {1}

Explanation

The code review application cannot access a PL/I include file.

User response

When the code application parses a PL/I program it accesses PL/I include files. This includes PL/I include files that are shipped with the compiler:
  1. Verify that the path of the property group file is specified correctly in the input data.
  2. Verify that the path of the include file is specified correctly in the property group file. To do this, open the LOCAL PL/I property group in the product workbench. Then verify that the path of the include file is specified in the SYSLIB field of the property group. If not, then enter the correct path, close the property group, and go to Step 4.
  3. Verify that the include file specified in the error message exists in the specified directory, and that the user has permission to access it.
  4. If the problem persists, export the property group file again and upload it to z/OS UNIX System Services.
CRRZW0004E
An error occurred while retrieving the COBOL copybook file {0}. Error message: {1}

Explanation

The code review application cannot access a COBOL copybook.

User response

When the code application parses a COBOL program it accesses COBOL copybooks. This includes COBOL copybooks that are shipped with the compiler:
  1. Verify that the path of the property group file is specified correctly in the input data.
  2. Verify that the path of the copybook is specified correctly in the property group file. To do this, open the LOCAL COBOL property group in the product workbench. Then verify that the path of the copybook is specified in the SYSLIB field of the property group. If not, then enter the correct path, close the property group, and go to Step 4.
  3. Verify that the copybook specified in the error message exists in the specified directory, and that the user has permission to access it.
  4. If the problem persists, export the property group file again and upload it to z/OS UNIX System Services.
CRRZW0005E
An error occurred while reading file {0}. The default mapping will be used.

Explanation

The code review application cannot read the z/OS File System Mapping file (that is, the file extension mapping file) that is specified in the input data.

User response

  1. Verify that the path of the z/OS File System Mapping file is specified correctly in the input data.
  2. Verify that the z/OS File System Mapping file exists in the specified directory, that the user has permission to access it, and that it is a correctly formatted zip file.
  3. If the problem persists, export the z/OS File System Mapping file again and upload it to z/OS UNIX System Services.
CRRZW0006E
An error occurred while associating the property group {0} with the data set {1}.

Explanation

The code review application extracted a property group from the property group file but cannot associate the property group with a data set.

User response

  1. Verify that the property group file is a properly formatted XML file and that the user has permission to access it.
  2. If the problem persists, export the property group file again and upload it to z/OS UNIX System Services.
CRRZW0007E
An error occurred while setting up the property group.

Explanation

The code review application cannot read the property group file.

User response

  1. Verify that the property group file is a properly formatted XML file and that the user has permission to access it.
  2. If the problem persists, export the property group file again and upload it to z/OS UNIX System Services.
  3. Verify that the version of the client is not later than the version of the host Batch Runtime.
CRRZW0008E
The code review application cannot find the workspace.

Explanation

The code review application cannot initialize the Eclipse workspace.

User response

The code review application uses the Eclipse workspace as a work area. Verify that the workspace exists and is accessible:
  1. Verify that the path of the workspace is specified correctly in the input data.
  2. Verify that the workspace exists and that the user has permission to access it.
  3. Try the operation again.
  4. Check the workspace log for errors.
  5. If the problem persists, contact IBM Software Support.
CRRZW0009E
An error occurred while setting up custom rule definitions.

Explanation

The code review application cannot read the custom rules and categories file (that is, the custom validation rules file) that is specified in the input data.

User response

  1. Verify that the path of the custom rule and categories file is specified correctly in the input data.
  2. Verify that the custom rule and categories file exists in the specified directory, that the user has permission to access it, and that it contains readable text.
  3. If the problem persists, export the custom rules and categories file again and upload it to z/OS UNIX System Services.
CRRZW0010E
Software analysis cannot continue. The {0} parameter was not specified.

Explanation

A required input parameter to the code review application is missing.

User response

Verify that the parameter identified by the error message is specified correctly in the input data.
CRRZW0011E
Software analysis cannot continue. The rule file {0} does not exist.

Explanation

The code review application cannot find the rule file.

User response

  1. Verify that the path of the rule file is specified correctly in the input data.
  2. Verify that the rule file exists in the specified directory and that the user has permission to access it.
  3. If the problem persists, export the rule file again and upload it to z/OS UNIX System Services.
CRRZW0012E
Software analysis cannot continue. The data set {0} does not exist.

Explanation

The code review application cannot find the PDS.

User response

  1. Verify that PDS is specified correctly in the input data.
  2. Verify that the PDS exists.
CRRZW0013E
Software analysis cannot continue. The rule file {0} does not contain any rules.

Explanation

The code review application cannot process the rule file.

User response

  1. Verify that the path of the rule file is specified correctly in the input data.
  2. Verify that the rule file exists in the specified directory, that the user has permission to access it, and that it contains readable text encoded in UTF-8 format.
  3. If the problem persists, export the rule file again and upload it to z/OS UNIX System Services.
CRRZW0014E
Software analysis cannot continue. The baseline {0} does not exist.

Explanation

The code review application cannot find the baseline file.

User response

  1. Verify that the path of the baseline file is specified correctly in the input data.
  2. Verify that the baseline file exists in the specified directory and that the user has permission to access it.
  3. If the problem persists, export the baseline file again and upload it to z/OS UNIX System Services.
CRRZW0015E
Software analysis cannot continue. The list file {0} does not exist.

Explanation

{0}
0
CRRZW0016W
Non-fatal warnings occurred while processing the list file {0}.

Explanation

{0}
0
CRRZW0017W
The list file record does not specify a data set name. The record will be ignored: {0}

Explanation

{0}
0
CRRZW0018W
The list file record does not contain a language. The record will be ignored: {0}

Explanation

{0}
0
CRRZW0019W
The list file record has an illegal value {0} for the select keyword. The record will be treated as if SELECT=INCLUDE.

Explanation

{0}
0
CRRZW0020W
The list file record specifies a data set that does not exist. The record will be ignored: {0}

Explanation

{0}
0
CRRZW0021W
The list file record specifies a member that does not exist. The record will be ignored: {0}

Explanation

{0}
0
CRRZW0022E
An error occurred while processing the list file {0}. Error message: {1}

Explanation

{0}
0
{1}
1
CRRZW0023W
The list file record specifies an unsupported language. The record will be ignored: {0}

Explanation

{0}
0

Host messages for Configuration Utility

The following host messages pertain to the Configuration Utility in Rational Developer for z Systems.

FEKM001A
Java directory invalid

Explanation

The Java location field does not contain a valid directory name, or the directory that is specified does not exist or does not contain /bin/java. This error might also occur if your TSO region size is too small and Java failed to run.

User response

Correct the Java directory name or ensure that the TSO region size is 128M (SIZE=128000).
FEKM002A
Directory invalid

Explanation

The directory name that is specified for Rational Developer for z Systems configuration files contains invalid syntax.

User response

Correct the directory name.
FEKM003A
Directory invalid

Explanation

The directory name that is specified for the installation does not exist.

User response

Correct the directory name.
FEKM004A
HLQ invalid

Explanation

Unable to locate &RDZHLQ..SFEKLOAD. The high-level qualifier that is specified might be invalid.

User response

Correct the high-level qualifier for the SFEKLOAD data set.
FEKM006A
Data set name invalid

Explanation

The data set name does not comply with z/OS standards.

User response

Specify a valid data set name.
FEKM007I
Invalid Delete

Explanation

The DEFAULT user ID cannot be deleted.

User response

No action is required. This message is for informational purposes only.
FEKM011I
Invalid Work Flow

Explanation

The DEFAULT user ID does not have a work flow.

User response

Run the G Generate configuration jobs to create a work flow.
FEKM015I
Invalid Prefix Command

Explanation

Valid prefix commands are C, D, F, L, N, S, or W.

User response

Use a valid prefix command.
FEKM016I
Invalid Prefix Command

Explanation

Valid prefix commands are C or V.

User response

Use a valid prefix command.
FEKM017I
Invalid Prefix Command

Explanation

Valid prefix commands are A, C, or E

User response

Use a valid prefix command.
FEKM019I
Invalid Prefix Command

Explanation

Valid prefix commands are N or S until configured.

User response

Use a valid prefix command.
FEKM020I
No Log Available

Explanation

There is no log available for this work flow request because the request was not Actioned.

User response

Action the work flow request.
FEK0000W
Message {1} Undefined

Explanation

This message is an internal warning.

User response

If this message is issued with an error, contact IBM Software Support.
FEK0001I
{1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK0002E
Malformed XML header: line={1} text={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0003E
Malformed XML attribute: line={1} text={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0004E
Incorrect XML class terminator: line={1} text={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0005E
New XML class started before class end: line={1} text={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0006I
XML {1} class processing complete

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK0007E
Unknown XML class specified: line={1} text={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0008E
Invalid command environment attribute: environment={1} xmlid={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0009E
EXECIO for {1} failed: rc={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0010E
'{1}' Trapped on line {2}, rc {3} - '{4}'

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0011E
Unrecoverable error - processing terminates

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0012I
FEK Processing completed successfully for {1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK0013E
EXECIO DISKR from {1} failed: rc={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0014E
EXECIO DISKW to {1} failed: rc={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0015W
FEK routine {1} gave bad return code {2}

Explanation

The work flow routine run failed.

User response

Review the work flow routine and any other associated error messages. Make the necessary corrections and run the routine again.
FEK0016E
z/OS UNIX command {1} gave bad return code {2}

Explanation

The work flow routine run failed.

User response

Review the work flow routine and any other associated messages. Make the necessary corrections and run the routine again.
FEK0017E
TSO command {1} gave bad return code {2}

Explanation

The work flow routine run failed.

User response

Review the work flow routine and any other associated messages. Make the necessary corrections and run the routine again.
FEK0018E
Member {1} of data set {2} not found

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK0019E
Invalid selection

Explanation

The selected value is invalid.

User response

Select a valid command.
FEK0020I
Copy attempt FAILED, attempt to copy to user directory

Explanation

The copy to the user directory failed.

User response

Be sure that the user has write access to the specified directory or that there is available space in that directory.
FEK0030I
Work Flow actioned by {1} on {2} {3}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK0031I
Work Flow processing commands from: {1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK0032I
Copy from {1} to {2} completed successfully

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK0033E
Copy from {1} to {2} failed , rc={3}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEK1001I
File {1} created.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1002I
HFS file {1} created.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1003I
Panel {1} displayed.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1004I
PDS file {1} created.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1005I
OCOPY {1} to {2}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1006I
{1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1007I
Unknown file type specified in file class.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1008I
Run REXX exec {1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1009I
Include ISPF skeleton {1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1010I
Job {1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1011I
... submitted

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1013I
Command {1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1014I
...issued in environment {1}, rc= {2}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1015I
Action manually completed by {1} on {3} {3}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1016I
Command response: {1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1017I
Syscall environment not available.

Explanation

This message is an internal warning.

User response

If this message is issued with an error, contact IBM Software Support.
FEK1018I
All returns are 0, this means the dir exists.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1019I
Retval= {1} errono= {2}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1020I
The directory probably does not exist, attempting to create directory

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1021I
After mkdir rc= {1}, retval= {2}, errorno= {3}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1022I
lrc= {1}, retval= {2}, errorno= {3}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEK1023I
Could not create {1}.

Explanation

This message is issued with message FEK1024I. The specified directory could not be created.

User response

The systems programmer must modify user authority so the user can create this directory.
FEK1024I
...ensure you have authority to create this directory.

Explanation

This message is issued in conjunction with message FEK1023I. The specified directory could not be created.

User response

The systems programmer must modify user authority so the user can create this directory.
FEK1025I
Directory {1} created.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR000W
Message {1} Undefined

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR001I
{1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR002E
Malformed XML header: line={1} text={2}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR003E
Malformed XML attribute: line={1} text={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR004E
Incorrect XML class terminator: line={1} text={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR005E
New XML class started before class end: line={1} text={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR006I
XML Class parsing complete for {1} name {2}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR007E
Unknown XML class specified: line={1} text={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR008E
Invalid command environment attribute: environment={1} xmlid={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR009E
EXECIO for {1} failed: rc={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR010E
'{1}' Trapped on line {2}, rc {3} - '{4}'

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR011E
Unrecoverable error - processing terminates

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR012I
Processing completed: RC={1}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR013E
EXECIO DISKR from {1} failed: rc={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR014E
EXECIO DISKW to {1} failed: rc={2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR015W
Routine {1} gave bad return code {2}

Explanation

An internal error occurred.

User response

Contact IBM Software Support.
FEKR101I
File {1} created.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR117I
Syscall environment not available.

Explanation

This message is an internal warning.

User response

If this message is issued with an error, contact IBM Software Support.
FEKR118I
All returns are 0, this means the dir exists.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR119I
Retval= {1} errono= {2}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR120I
The directory probably does not exist, attempting to create directory

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR121I
After mkdir rc= {1}, retval= {2}, errorno= {3}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR122I
lrc= {1}, retval= {2}, errorno= {3}

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR123I
Could not create {1}.

Explanation

This message is issued with message FEKR124I. The specified directory could not be created.

User response

The systems programmer must modify user authority so the user can create this directory.
FEKR124I
...ensure you have authority to create this directory.

Explanation

This message is issued with message FEKR123I. The specified directory could not be created.

User response

The systems programmer must modify user authority so the user can create this directory.
FEKR125I
Directory {1} created.

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR201I
Java {1} ICSF and RACF

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR202I
Java {1} ICSF and no RACF

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR204E
z/OS UNIX command {1} failed.

Explanation

The work flow routine run failed.

User response

Review the work flow routine and any other associated messages. Correct the errors and run the routine again.
FEKR205I
z/OS UNIX command {1} Returned:

Explanation

This message is for informational purposes only.

User response

No action is required.
FEKR206I
{1}

Explanation

This message is for informational purposes only.

User response

No action is required.

Host messages for RSE daemon and RSE server

These host messages pertain to the RSE daemon or the RSE server in Rational Developer for z Systems.

FEK001I
RseDaemon being initialized in {0} bit mode

Explanation

{0}
The addressing mode: 31 or 64.
This message is shown when the Rational Developer for z Systems daemon is started. It provides information about the addressing mode: 31 or 64.

System programmer response

No action is required.
FEK002I
RseDaemon started. (port={0})

Explanation

{0}
The daemon port for each Rational Developer for z Systems client user to log on.
This message indicates that the Rational Developer for z Systems daemon was started successfully and provides information about the daemon port for each Rational Developer for z Systems client user to log on.

System programmer response

No action is required.
FEK003I
Stop command being processed

Explanation

The operator entered the Rational Developer for z Systems STOP command.

System programmer response

No action is required.
FEK004I
RseDaemon: Max Heap Size={0}MB and private AS Size={1}MB

Explanation

{0}
The JVM maximum heap size.
{1}
The private address space size of the application.
This message provides the JVM maximum heap size and the private address space size of the application.

System programmer response

No action is required.
FEK005I
Server process started. (processId={0})

Explanation

{0}
The process ID with which the started server process is associated.
This message provides information about the process ID with which the started server process is associated

System programmer response

No action is required.
FEK009I
RseDaemon is waiting for the server process to start.

Explanation

This message is issued every time that it takes more than 30 seconds for the server process to start.

System programmer response

If the server process never starts, contact IBM Software Support.
FEK010I
(rsed.envvars location = {0})

Explanation

{0}
The location of the active rsed.envvars file.
This message provides the location of the active rsed.envvars file.

System programmer response

No action is required.
FEK011I
(log directory = {0})

Explanation

{0}
The location of the rsedaemon.log and rseserver.log.
This message provides the location of rsedaemon.log and rseserver.log. When the enable.standard.log parameter is set to true in rsed.envvars, the standard out and error logs are also in the same directory.

System programmer response

No action is required.
FEK012I
(RSE home directory = {0})

Explanation

{0}
The location of the active Rational Developer for z Systems modules.
This message provides the location of the active modules that are related to Rational Developer for z Systems.

System programmer response

No action is required.
FEK100E
Daemon port/timeout value must be digits

Explanation

The daemon port and timeout values are provided as a parameter of the JVM start command and must be digits.

System programmer response

Correct the daemon port and timeout value in the Rational Developer for z Systems started procedure.
FEK101E
JRE {0} or higher required

Explanation

{0}
The minimum level of the JRE that is required to run the Rational Developer for z Systems daemon.
This message provides the minimum level of the JRE that is required to run the Rational Developer for z Systems daemon.

System programmer response

Change the rsed.envvars file to use the JRE that the error message indicates.
FEK102E
REGISTRATION HAS BEEN DENIED FOR PRODUCT WITH {0} DUE TO {1}

Explanation

{0}
The name of the invalid argument in the console command. The only valid argument name is Process_ID.
The console command contains invalid arguments.

System programmer response

Enter the correct process ID for the command.
FEK103E
Almost Disk-Full in {0}

Explanation

{0}
The directory that is almost full.
The z/OS UNIX System Services directory that is shown in the message is almost full. This message is issued when the log becomes 80% full.

System programmer response

To prevent the loss of log contents, increase the size of the directory.
FEK104E
Maximum number of processes has been reached

Explanation

The maximum number of Rational Developer for z Systems server processes was reached.

System programmer response

Increase the value that is specified for the maximum.threadpool.process parameter in the rsed.envvars file.
FEK105E
Error in sending audit data (rc={0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): send.
An error occurred when the Rational Developer for z Systems server process tried to send audit data to the Rational Developer for z Systems daemon process.

System programmer response

Contact IBM Software Support.
FEK106E
No Resource Bundle of {0}

Explanation

{0}
0

System programmer response

FEK107E
Almost Disk-Full in {0}, existing {1} removed

Explanation

{0}
The directory that is almost full.
{1}
The log file to be removed to clear space in the directory.
This message is issued when the directory that contains the ffs*.log and rsecomm*.log files becomes 95% full. The log file that is shown in the message was removed to clear space in the directory.

System programmer response

To determine the timeframe of messages that were removed from the log file, see the rseserver.log file or ffs.log file.
FEK110E
socket() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): socket.
The TCP/IP socket failed for the reason code that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK111E
setsockopt() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): setsockopt.
The TCP/IP setsockopt call failed for the reason code that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK112E
bind() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): bind.
The TCP/IP bind call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK113E
listen() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): listen.
The TCP/IP listen call failed for the reason that is specified in the message

System programmer response

Contact IBM Software Support.
FEK114E
accept() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): accept.
The TCP/IP accept call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK115E
write() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): write.
The TCP/IP write call failed for the reason that is specified in the message

System programmer response

Contact IBM Software Support.
FEK116E
pipe() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): pipe.
The PIPE that is used between the Rational Developer for z Systems daemon and server processes failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK117E
socketpair() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): socketpair.
The socketpair call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK118E
select() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): select.
The select call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK119E
_console() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in XL C/C++ Run-Time Library Reference (SA22-7821): _console().
The _console() call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK120E
REGISTRATION HAS BEEN DENIED FOR PRODUCT WITH {0} DUE TO {1}

Explanation

{0}
Product name and identifier information that is reported by the registration service.
{1}
The reason for the denial that is reported by the registration service.
When the product server software starts, it registers with z/OS to verify that it is being started on a licensed CPU. This message displays when the product registration is denied. It reports information about the product and the reason for the denial.

User response

Check that the product has been correctly enabled. For more information about enabling the product with the registration service, see Product enablement in IFAPRDxx.
FEK130E
gsk_environment_open() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_environment_open.
The gsk_environment_open() system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK131E
gsk_attribute_set_enum(GSK_PROTOCOL_SSLV2) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_enum.
The gsk_attribute_set_enum(GSK_PROTOCOL_SSLV2) system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK132E
gsk_attribute_set_enum(GSK_PROTOCOL_SSLV3) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_enum.
The gsk_attribute_set_enum(GSK_PROTOCOL_SSLV3) system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK133E
gsk_attribute_set_enum(GSK_PROTOCOL_TLSV1) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_enum.
The gsk_attribute_set_enum(GSK_PROTOCOL_TLSV1) system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK134E
gsk_attribute_set_buffer(GSK_KEYRING_FILE) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_buffer.
The gsk_attribute_set_buffer(GSK_KEYRING_FILE) system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK135E
gsk_attribute_set_buffer(GSK_KEYRING_PW) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_buffer.
The gsk_attribute_set_buffer(GSK_KEYRING_PW) system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK136E
gsk_environment_init() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_environment_init.
The gsk_environment_init() system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK137E
gsk_secure_socket_open() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_secure_socket_open.
The gsk_secure_socket_open() system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK138E
gsk_attribute_set_numeric_value(GSK_FD) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_numeric_value.
The gsk_attribute_set_numeric_value(GSK_FD) system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK139E
gsk_attribute_set_buffer(GSK_KEYRING_LABEL) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_buffer.
The gsk_attribute_set_buffer(GSK_KEYRING_LABEL) system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK140E
gsk_attribute_set_enum(GSK_SESSION_TYPE) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_enum.
The gsk_attribute_set_enum(GSK_SESSION_TYPE) system SSL call failed for the reason code that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK141E
gsk_attribute_set_callback(GSK_IO_CALLBACK) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_callback.
The gsk_attribute_set_callback(GSK_IO_CALLBACK) system SSL call failed for the reason that is specified in the message.

System programmer response

Contact IBM Software Support.
FEK142E
gsk_secure_socket_init() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_secure_socket_init.
The gsk_secure_socket_init() system SSL call failed for the reason that is specified in the message.

System programmer response

A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
FEK143E
gsk_attribute_set_enum(GSK_CLIENT_AUTH_TYPE) failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_set_enum.
The gsk_attribute_set_enum(GSK_CLIENT_AUTH_TYPE) system SSL call failed for the reason that is specified in the message.

System programmer response

A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
FEK144E
gsk_get_cert_info failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_attribute_get_cert_info.
The gsk_attribute_get_cert_info system SSL call failed for the reason that is specified in the message.

System programmer response

A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
FEK145E
gsk_secure_socket_read() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_secure_socket_read.
The gsk_secure_socket_read() system SSL call failed for the reason that is specified in the message.

System programmer response

A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
FEK146E
gsk_secure_socket_write() failed. reason=({0})

Explanation

{0}
The reason code. For a list of reason codes, see the following topic in z/OS Cryptographic Services System Secure Sockets Layer Programming (SC24-5901): gsk_secure_socket_write.
The gsk_secure_socket_write() system SSL call failed for the reason that is specified in the message.

System programmer response

A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
FEK150E
RseDaemon abnormally terminated; {0}

Explanation

{0}
The code that is returned by the Java virtual machine (JVM).
The RSE daemon terminated because of an unrecoverable TCP/IP error.

System programmer response

Contact IBM Software Support.
FEK201I
{0} Command has been processed

Explanation

{0}
A Rational Developer for z Systems command.
A Rational Developer for z Systems command was processed successfully.

System programmer response

No action is required.
FEK202E
Invalid Command Entered

Explanation

An invalid Rational Developer for z Systems command was issued.

System programmer response

Correct the command parameters and issue the command again.
FEK203E
Invalid Display Command: Display Process|Client|Owner

Explanation

An invalid Rational Developer for z Systems Display command was entered. The Display command must be Display Process or Display Client.

System programmer response

Correct the command and try again.
FEK204E
Invalid Cancel Command: Cancel ID=|User=

Explanation

An invalid Rational Developer for z Systems Cancel command was entered. The command must be Cancel ID=nnnn or Cancel User=userid, where nnnn is a user display ID that is shown in the Display Client command.

System programmer response

Correct the Cancel command parameters and try again.
FEK205E
Command was not processed owing to consecutive SWITCHs

Explanation

The SWITCH audit log command cannot be processed because a previous SWITCH command is not yet processed.

System programmer response

Wait for the completion of the previous SWITCH command and try again.
FEK206E
Audit Log facility is not active

Explanation

The SWITCH audit log command was entered, but the audit log facility is not active.

System programmer response

Verify the settings that are related to the audit log in the rsed.envvars file and try again.
FEK207I
No Client to be displayed

Explanation

A Rational Developer for z Systems Display Client command was issued, but there is no client that the Rational Developer for z Systems server serves.

System programmer response

No action is required.
FEK208I
{0} canceled

Explanation

{0}
A user ID.
The specified user was successfully canceled by a Rational Developer for z Systems Cancel User command.

System programmer response

No action is required.
FEK209I
No Process to be displayed

Explanation

The Rational Developer for z Systems Display Process command was issued, but no server process is running.

System programmer response

No action is required.
FEK210I
{0} was disconnected forcibly because of the active single.logon directive.

Explanation

The client user who logged on was canceled because the single logon capability is enabled.

System programmer response

No action is required unless you want to disable the single logon capability. To disable the single logon capability, change the settings for the single.logon parameter in the rsed.envvars file. The FEK010I message shows the location of the rsed.envvars file.
FEK211W
User, {0}, not logged on

Explanation

{0}
The user ID
A cancel ID command was invalid because the user ID is not logged on. This warning is sometimes issued when a cancel ID command is issued for a user ID that has not yet been logged on.

System programmer response

No action is required.
FEK212E
Invalid {0} command option: {1}

Explanation

{0}
The command that was entered: Display Process or Display Process,CPU
{1}
The invalid command option
A Display Process or Display Process,CPU command with an invalid command option was entered.

System programmer response

Correct the command option and issue the command again.
FEK215W
Command {0} is not processed by all thread pools

Explanation

{0}
The command that was issued
When a command is issued to multiple thread pool processes, the DaemonMonitor receives confirmations from each process and displays the command results. If the timer expires before the DaemonMonitor receives all of the confirmations, then the DaemonMonitor issues this message to show that some processes timed out before processing the command.

System programmer response

No action is required.
FEK216W
Unable to process command, busy processing previous command.

Explanation

A command was entered before the system completed processing a previous instance of the same command.

System programmer response

Wait for the system to process the previous command and then enter the second command again.
FEK217I
{0} is locked by {1}

Explanation

{0}
A data set.
{1}
A user ID.
A DISPLAY OWNER command was issued. This message shows the lock owner of a data set.

System programmer response

No action is required.
FEK218I
{0} is not locked

Explanation

{0}
A data set.
A DISPLAY OWNER command was issued to display the lock owner of a data set. The data set is not locked.

System programmer response

No action is required.
FEK219E
Failed to determine lock owner for {0}

Explanation

{0}
A data set.
A DISPLAY OWNER command was issued, but the lock owner could not be determined.

System programmer response

No action is required.
FEK220I
LOGS Command has been started to write onto {0} for the requester, {1}

Explanation

{0}
The location of the output file.
A command was issued to collect host log files. This message shows the location of the output file. The default name for the output file is $TMPDIR/feklogs.%sysname.%jobname.log.
$TMPDIR
The default directory is /tmp.
%sysname
The z/OS system name.
%jobname
The name of the RSE daemon.

System programmer response

No action is required.
FEK221E
{0} was interrupted because of {1}

Explanation

{0}
The process of the tool or program that was interrupted.
{1}
The reason for the interruption.
The process of the tool or program was interrupted for the specified reason.

System programmer response

If the specified reason is a timeout, check whether the tool or program was hung.
FEK301E
{0} (uid:{1}) does not own the directory of {2} (file_owner uid:{3})

Explanation

{0}
A log file name.
{1}
The user ID that attempted to access the log file.
{2}
The directory where the log file is stored.
{3}
The user ID that owns the directory.
An attempt was made to access a log file, but the user ID does not have the correct authority.

System programmer response

Ensure that your user ID is authorized to access the log file.
FEK302E
The requester, {0}, of the {1} command does not have authority to access the profile of {2}

Explanation

{0}
The user ID that requested the command.
{1}
The command that was requested.
{2}
A security profile.
A command was issued, but the user ID does not have the correct authority to access the specified security profile.

System programmer response

Ensure that your user ID is authorized to access the specified security profile.
FEK303E
The symbolic link, {0}, cannot be used as a log directory

Explanation

{0}
0
FEK304W
Invalid {0}, {1}, was specified. The default mode, {2}, is used instead.

Explanation

{0}
0
{1}
1
{2}
2
FEK305E
The ID, {0}, does not have appropriate privileges to access {1}.

Explanation

{0}
0
{1}
1
FEK800S
{0} {1}

Explanation

{0}
0
{1}
1
FEK900I
{0} IVP: {1}

Explanation

{0}
The IVP (Installation Verification Program) name. This name can be one of the following values:
  • DAEMON: Daemon IVP
  • PASSTICKET: PassTicket IVP
  • ISPF: ISPF IVP
{1}
A message that is issued by the IVP.
This message is a response that is issued when an operator runs the IVP program by using a Rational Developer for z Systems console command.

System programmer response

No action is required.
FEK901I
{0} IVP Exit code = {1}

Explanation

{0}
The IVP name. This name can be one of the following values:
  • DAEMON: Daemon IVP
  • PASSTICKET: PassTicket IVP
  • ISPF: ISPF IVP
{1}
The exit code.
This message shows the exit code that is provided by the IVP program.

System programmer response

No action is required.
FEK910I
{0} EXIT: {1}

Explanation

{0}
AUDIT indicates that the message originates in an audit exit program.
{1}
A message that is issued by the audit exit program. The audit exit program is created by the customer.
This message is a response for an audit exit program or logon exit program.

System programmer response

No action is required.
BPXM023
(stclock) data set[(member)] NOT LOCKED

Explanation

This message is a response for a lock daemon query command.

System programmer response

No action is required.
BPXM023
(stclock) data set[(member)] LOCKED BY userid

Explanation

This message is a response for the lock daemon query command. The specified data set was locked by the specified user ID.

System programmer response

No action is required.
BPXM023
(stclock) command, WRONG COMMAND

Explanation

An invalid lock daemon command was entered.

System programmer response

Correct the lock daemon command and try again.
BPXM023
(stclock) command, MISSING ARGUMENT

Explanation

An argument for the lock daemon command is missing.

System programmer response

Supply the missing argument for the lock daemon command and try again.
BPXM023
(stclock) argument, WRONG ARGUMENT

Explanation

An invalid argument was specified for the lock daemon command.

System programmer response

Correct the argument for the lock daemon command and try again.
CEARC-87
A TSO logon parameter (for example, procedure name or account number) is not valid.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-88
Conflicting parameters are specified on the gateway request.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-89
A message was received on the message queue with a message type of ISPF. This is not expected.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-90
An error occurred on a call to the iconv_close() function.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-91
An error occurred on a call to the iconv_open() function.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-92
An error occurred on a call to the iconv() function.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-93
An error occurred on a call to the msgsnd() function.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-94
An error occurred on a call to the __msgrcv_timed() function.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-95
An error occurred on a call to the setenv() function.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-96
The response contains no text.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-97
No data was read from STDIN.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-98
A parameter value on the gateway request is bad.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.
CEARC-99
A required parameter is missing on the gateway request.

Explanation

This message describes a return code for a TSO command execution error from the Interactive ISPF Gateway.

System programmer response

For information about the return code, see "Interactive ISPF Gateway return codes" in z/OS V2R2.0 ISPF Planning and Customization.

Runtime messages for Enterprise Service Tools

The following runtime messages pertain to the Enterprise Service Tools component (EST) in Rational Developer for z Systems.

The IRZ runtime messages for Enterprise Service Tools are not displayed in the workbench. They are written to a log on the remote system.

These runtime messages are written by a COBOL or PL/I program that is created by using the single-service project tools in Enterprise Service Tools.

The IRZ messages are grouped into the following subdivisions:

  • IRZ0001S-IRZ0499S: COBOL Compiled XML Transformation Conversion
  • IRZ0500S-IRZ0999S: PL/I Compiled XML Transformation Conversion
For more information about COBOL and PL/I runtime messages, see z/OS V1R10.0 Language Environment Run-Time Messages (SA22-7566-09), chapters 6 and 7. These documents are available through the following links:
IRZ0279S
XML to language structure conversion could not complete in program PROGRAM-NAME because conversion of the character content of an XML element or attribute that is of type xsd:boolean did not match 'true', 'false', '1', or '0'. The error occurred at XML path XML-PATH with the character content CHARACTER-CONTENT.

Explanation

XML to language structure conversion detected that the content of an XML element or attribute that is of type xsd:boolean did not match 'true', 'false', '1', or '0'.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.

IRZ0280S
XML to language structure conversion could not complete in program PROGRAM-NAME because an error return code of RETURN-CODE was received from the XML PARSE statement. The error occurred at XML path XML-PATH with the character content CHARACTER-CONTENT.

Explanation

XML to language structure conversion uses the COBOL XML PARSE statement. When the XMLPARSE(COMPAT) compiler option is in effect, the return code is provided from the XML PARSE statement and is described in the Enterprise COBOL Programming Guide. When the XMLPARSE(XMLSS) compiler option is in effect, the return code is provided from the z/OS XML System Services Parser and is described in the XML System Services User's Guide and Reference.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Use the return code to determine the error and correct the input XML message.

IRZ0281S
XML to language structure conversion could not complete in program PROGRAM-NAME because the valid range of a repeating group or repeating data item was exceeded. The error occurred at XML path XML-PATH.

Explanation

XML to language structure conversion might encounter errors when it transforms an XML message to a language structure. These errors are distinct from XML PARSE errors.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.

IRZ0282S
XML to language structure conversion could not complete in program PROGRAM-NAME because none of the elements in the input XML document matched a mapped element in the XML Schema upon which the XML converter is based.

Explanation

XML to language structure conversion might encounter errors when it transforms an XML message to a language structure. These errors are distinct from XML PARSE errors.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.

IRZ0283S
XML to language structure conversion could not complete in program PROGRAM-NAME because the character content for XML path XML-PATH was longer than the mapped language structure member's maximum of LIMIT characters.

Explanation

XML to language structure conversion might encounter errors when it transforms an XML message to a language structure. These errors are distinct from XML PARSE errors.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.

IRZ0284S
XML to language structure conversion could not complete in program PROGRAM-NAME because conversion of the character content of an XML path that is mapped as numeric failed. The error occurred at XML path XML-PATH with the character content CHARACTER-CONTENT.

Explanation

XML to language structure conversion might encounter errors when it transforms an XML message to a language structure. These errors are distinct from XML PARSE errors.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.

IRZ0285S
XML to language structure conversion could not complete in program PROGRAM-NAME because the length of the XML document is LENGTH characters, which exceeds the maximum of MAXIMUM characters for this converter.

Explanation

XML to language structure conversion imposes a limit on the length of XML documents that can be converted into language structures. The maximum length in bytes of the input XML document is 16 MB when version 3 of Enterprise COBOL for z/OS is used and 32 MB when version 4 of Enterprise COBOL for z/OS is used.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

IBM Rational Developer for z Systems normally prevents generation of XML to language structure converters when it is detected that an input XML message can exceed the 16 MB or 32 MB limit. Check that the input XML message conforms to the XML schema upon which it is based and that any white space outside of element content is trimmed.

IRZ0286S
XML to language structure conversion could not complete in program PROGRAM-NAME because the character content for XML path XML-PATH had a length greater than or equal to LENGTH characters, which was too long for the converter to process.

Explanation

XML to language structure conversion maintains a buffer for character content that has a maximum size equal to 10 times the size of the largest item in the target data structure. The content of an element was longer than expected.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.

IRZ0287S
Language structure to XML conversion could not complete in program PROGRAM-NAME because the maximum output message length of LENGTH characters was exceeded while generating the XML document.

Explanation

Language structure to XML conversion processes white space processing and expands entity references expansion when it generates the XML document. Entity reference expansion increases the length of data which is included as element content and can cause it to grow up to six times the original length of the data (the longest predefined entity is six characters long).

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that the language structure was not changed after the Language structure to XML converter was generated. Regenerate the XML converter if changes were made to the language structure.

IRZ0288S
conversion could not complete in program PROGRAM-NAME because a non-zero return code was received from the Unicode Conversion Service CUNLCNV while converting from CCSID SOURCE-CCSID to CCSID TARGET-CCSID.

Explanation

XML Conversion might convert XML and language data to and from Unicode during parsing and generation of XML if XML is expected to be exchanged in Unicode.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Check that conversion services are properly installed, and that the Unicode conversion attempted by the XML Converter is supported by the installation of conversion services on the target system.

IRZ0289S
Language structure to XML conversion could not complete in program PROGRAM-NAME because the content of non-numeric member MEMBER-NAME of language structure STRUCTURE-NAME contained characters that are not legal in an XML document.

Explanation

Certain COBOL data declarations allow characters that are not allowed in an XML document. The allowed characters are defined by the XML specification at http://www.w3c.org.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that the language structure member is properly initialized and does not contain any characters that are not allowed in XML before you attempt conversion.

IRZ0290S
Language structure to XML conversion could not complete in program PROGRAM-NAME because the content of numeric member MEMBER-NAME of language structure STRUCTURE-NAME is invalid.

Explanation

Language structure to XML conversion determined that the contents of the storage that is occupied by a numeric language structure member is invalid for the type.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that the numeric language structure member is properly initialized according to COBOL semantics.

IRZ0291S
XML to language structure conversion could not complete in program PROGRAM-NAME because the maximum XML element nesting depth was exceeded. The error occurred at XML path XML-PATH with character content CHARACTER-CONTENT.

Explanation

The language structure to XML converter maintains an internal stack which represents the full qualification of the current element that is being processed in the XML document. If extraneous XML elements not described in the XML schema to which the converter is bound are present in the XML document, they might exceed the maximum supported element depth.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that the numeric language structure member is properly initialized according to COBOL semantics.

IRZ0292S
XML conversion could not complete in program PROGRAM-NAME because an attempt to register an exception handler failed with Language Environment error LE-ERROR

Explanation

XML conversion uses Language Environment callable services to register a user-written handler to handle errors that occur during conversion. An attempt to register such a handler failed.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that Language Environment is configured correctly and that no conditions that could prevent correct operation exist in the chain of execution that leads up to the XML converter.

IRZ0293S
XML conversion could not complete in program PROGRAM-NAME because an attempt to unregister an exception handler failed with Language Environment error LE-ERROR.

Explanation

XML conversion uses Language Environment callable services to register a user-written handler to handle errors that occur during conversion. An attempt to unregister such a handler failed.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that Language Environment is configured correctly and that no conditions that could prevent correct operation exist in the chain of execution that leads up to the XML converter.

IRZ0294S
XML conversion could not complete in program PROGRAM-NAME because the address of one or more required parameters to the main entry point did not have valid addresses.

Explanation

The converter detected that one or more of the parameters that were passed to its main entry point do not have valid storage addresses to which the converter could refer and obtain the value.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that each parameter passed to the XML converter has a valid non-null storage address unless a particular parameter can be null as defined by the converter call interface. For example, passing the XML converter a null value for the XML buffer address to the language structure does not perform XML conversion, but returns the required size of the XML buffer instead.

IRZ0295S
XML to language structure conversion could not complete in program PROGRAM-NAME because a response code of RESPONSE-CODE with reason code REASON-CODE was received from the bidirectional data conversion module MODULE-NAME while processing the XML path XML-PATH.

Explanation

XML to language structure conversion uses an external module to handle bidirectional data conversions.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Refer to the bidirectional data conversion module documentation for explanations of return codes.

IRZ0296S
Language structure to XML conversion could not complete in program PROGRAM-NAME because a return code of RETURN-CODE with reason code REASON-CODE was received from the bidirectional data conversion module MODULE-NAME while processing member MEMBER-NAME of language structure STRUCTURE-NAME.

Explanation

Language structure to XML conversion uses an external module to handle bidirectional data conversions.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Refer to the bidirectional data conversion module documentation for explanations of return codes.

IRZ0298S
XML to language structure conversion could not complete in program PROGRAM-NAME because the target namespace of XML path XML-PATH was NAMESPACE-ACTUAL which is inconsistent with the expected target namespace of NAMESPACE-EXPECTED.

Explanation

XML to language structure conversion can optionally validate the namespace name of XML elements.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the XML instance document such that the XML elements have namespace names consistent with the names specified in the XML schema.

IRZ0299S
XML to language structure conversion could not complete in program PROGRAM-NAME because the minimum count of language structure STRUCTURE-NAME was not met.

Explanation

XML to language structure conversion can optionally validate the namespace name of XML elements.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the XML instance document such that the XML elements have namespace names consistent with the names specified in the XML schema.

IRZ0300S
XML to language structure conversion could not complete in program PROGRAM-NAME because the maximum count of language structure STRUCT-NAME was exceeded.

Explanation

XML to language structure conversion detected that the count of a language structure exceeds the maximum that was specified when the XML converter was generated.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the XML document or replace the XML converter with one having a higher maximum.

IRZ0301S
Language structure to XML conversion could not complete in program PROGRAM-NAME because the total count of language structure instances received was ACTUAL-COUNT which is less than the minimum of MINIMUM-COUNT instances required by the message layout.

Explanation

Language structure to XML conversion detected that the language structure buffer it received contained fewer language structure instances in total than is required by the message layout.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the language structure buffer so that each language structure occurs at least as many times as is required per the message layout.

IRZ0302S
Language structure to XML conversion could not complete in program program-name because the length prefix of language structure STRUCTURE-NAME specified a length of SPECIFIED-LENGTH bytes, which is less than the structure's minimum length of MINIMUM-LENGTH bytes.

Explanation

Language structure to XML conversion detected that the length prefix of a language structure specified a length that is less than the minimum length of the structure. The minimum length of a language structure is computed as the sum of the bytes consumed by all subordinate fields. For fields that specify OCCURS DEPENDING ON, the minimum number of occurrences is assumed.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correctly set the 2-byte length prefix of each language structure in the language structure buffer.

IRZ0303S
Language structure to XML conversion could not complete in program PROGRAM-NAME because the total count of language structure instances received was ACTUAL-COUNT which is greater than the maximum of MAXIMUM-COUNT instances allowed by the message layout.

Explanation

Language structure to XML conversion detected that the language structure buffer it received contained more language structure instances in total than is allowed by the message layout.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the language structure buffer so that it contains no more than the maximum number of instances of each language structure in the message layout.

IRZ0500S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because a return code of RETURN-CODE was received from the API DFSXSETS when attempting to store language structure STRUCTURE-NAME into the IMS Connect message output buffer.

Explanation

In the IMS top-down scenario, XML to language structure conversion starts an API named DFSXSETS to store one or more language structures into the IMS Connect message output buffer according to a symmetric protocol. A nonzero return code from DFSXSETS indicates that a language structure could not be stored in the IMS Connect message output buffer and therefore cannot be sent to the IMS application.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

For explanations of DFSXSETS return codes, see the IRZPWSIO module documentation, which is located in the Rational Developer for z Systems online help.
IRZ0501S
Language Structure to XML coversion could not complete in procedure PROCEDURE-NAME because a return code of RETURN-CODE was received from the API DFSXGETS hen attempting to retrieve language structure STRUCTURE-NAME from the IMS Connect message input buffer.

Explanation

In the IMS top-down scenario, language structure to XML conversion starts an RDz-provided API named DFSXGETS to retrieve one or more language structures from the IMS Connect message input buffer according to a symmetric protocol. A nonzero return code from DFSXGETS indicates that a language structure could not be retrieved from the IMS Connect message input buffer and therefore cannot be converted to XML.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

For explanations of DFSXGETS return codes, see the IRZPWSIO module documentation, which is located in the Rational Developer for z Systems online help, .

IRZ0502S
Language Structure to XML coversion could not complete in procedure PROCEDURE-NAME because the array counter variable COUNTER-NAME for array ARRAY-NAME specified a value of COUNTER-VALUE which exceeds the array's limit of ARRAY-LIMIT.

Explanation

Explanation: In the top-down scenario language structure to XML conversion provides an application programmer the ability to specify the count of entries that XML conversion reads from an array by using generated counter variables. This message is issued if a counter variable is found to contain a value that exceeds the limit of its corresponding array.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Set the counter variable to a value that does not exceed the limit of the corresponding array.

IRZ0960S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because an error return code of RETURN-CODE was received from the PLISAX FUNCTION-SUFFIX built-in function. The error occurred at element ELEMENT-NAME with the character content CHARACTER-CONTENT.

Explanation

XML to language structure conversionuses the PL/I PLISAXx built-in function. The return code that is provided is from the PL/I PLISAXx built-in function as described in Enterprise PL/I for z/OS Programming Guide Version 3, SC27-1457-05 (or later).

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Use the return code to determine the error and correct the input XML message.

IRZ0961S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the valid range of a repeating group or repeating data item was exceeded. The error occurred at element ELEMENT-NAME.

Explanation

XML to language structure conversion might encounter errors that are distinct from PLISAXA/B errors.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message. Check that the input XML document has the correct number of occurrences of all entries that repeat.

IRZ0962S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because no element names in the XML document were recognized by the converter.

Explanation

XML to language structure conversion might encounter errors that are distinct from PLISAXA/B errors.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Supply the correct XML message corresponding to this converter.

IRZ0963S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the character content for element ELEMENT-NAME was longer than the element's maximum of LIMIT characters.

Explanation

XML to language structure conversion might encounter errors that are distinct from PLISAXA/B errors.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message.

IRZ0964S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because conversion of the character content of an element that is mapped as numeric failed. The error occurred at element ELEMENT-NAME with the character content CHARACTER-CONTENT.

Explanation

XML to language structure conversion might encounter errors that are distinct from PLISAXA/B errors.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message.

IRZ0965S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the size of the input XML message was LENGTH characters, which exceeds the maximum of MAXIMUM characters for this converter.

Explanation

XML to language structure conversion supports parsing XML messages whose length falls within certain compiler limits.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message or define an auxiliary language structure to process the XML in segments.

IRZ0966S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the character content for element ELEMENT-NAME had a length equal to or greater than LENGTH characters which was too long for the converter to process.

Explanation

The XML converter maintains a buffer for character content whose size is equal to that of the largest character member in the language structure or 128, whichever is larger.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correct the input XML message. Check for any excessive white space in the element content.

IRZ0967S
Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because the maximum output message size of SIZE characters was exceeded while creating the outbound XML document.

Explanation

Language structure to XML conversion supports generation of XML messages whose length falls within certain compiler limits. White space suppression and entity reference expansion are performed during creation of the XML document. Entity reference expansion increases the size of a message in relation to the number of special characters in the source language structure that must be represented as one of the five predefined entity references in XML.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Avoid the use of the five predefined entries in XML when you populate the language structure or define an auxiliary language structure to generate the output XML in segments.

IRZ0968S
XML Conversion could not complete in procedure PROCEDURE-NAME because a non-zero return code was received from the Unicode Conversion Service CUNLCNV while converting from CCSID SOURCE-CCSID to CCSID TARGET-CCSID.

Explanation

XML Conversion uses PL/I built-in support for UNICODE when the input XML or output XML is encoded in either UTF-16 or UTF-8.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Check that z/OS Support for UNICODE is properly installed and that the conversion attempted by the XML Conversion is supported by the current conversion image.

IRZ0969S
Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because the content of non-numeric member MEMBER-NAME of language structure STRUCTURE-NAME contained characters that are not legal in an XML document.

Explanation

Certain language structure members allow storage of characters that are not valid in an XML document. The allowed characters are defined by the XML specification at http://www.w3c.org.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that the language structure member is properly initialized and does not contain any characters that are not allowed in XML before you attempt conversion.

IRZ0970S
Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because the content of numeric member MEMBER-NAME of language structure STRUCTURE-NAME is invalid.

Explanation

Language structure to XML conversion determined that the contents of the storage that is occupied by a numeric data structure member is invalid for the type.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that the numeric data structure member is properly initialized following the semantics of the language.

IRZ0971S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the maximum XML element nesting depth was exceeded. The error occurred at element ELEMENT-NAME with character content CHARACTER-CONTENT.

Explanation

XML to language structure conversion maintains an internal stack which represents the full qualification of the current element that is being processed in the XML document. If extraneous XML elements not described in the XML schema to which the converter is bound are present in the XML document, they might exceed the maximum supported element depth.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Either supply XML documents to the converter that validate against the bound XML schema or remove the extraneous element that causes the failure from the input XML document.

IRZ0972S
XML conversion could not complete in procedure PROCEDURE-NAME because an attempt to register an exception handler failed with Language Environment error LE-ERROR.

Explanation

The converter uses Language Environment callable services to handle errors that might occur during conversion. An attempt by the converter to register a Language Environment condition handler failed.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that Language Environment is configured properly and that no conditions that would prevent correct operation exist in the chain of execution that leads up to the converter.

IRZ0973S
XML conversion could not complete in procedure PROCEDURE-NAME because an attempt to unregister an exception handler failed with Language Environment error LE-ERROR.

Explanation

The converter uses Language Environment callable services to handle errors that might occur during conversion. An attempt by the converter to register a Language Environment condition handler failed.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that Language Environment is configured properly and that no conditions that would prevent correct operation exist in the chain of execution that leads up to the converter.

IRZ0974S
XML conversion could not complete in procedure PROCEDURE-NAME because the address of one or more parameters was not valid.

Explanation

The converter detected that one or more of the parameters that were passed to its main entry point do not have valid storage addresses to which the converter could refer and obtain the value.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Ensure that each parameter passed to the converter has a valid storage address unless a particular parameter can be null as defined by the converter call interface. For example, a null message address that is passed to the outbound converter is interpreted as a request for the maximum outbound message size to be returned instead of a conversion.

IRZ0975S
XML to language structure conversion could not complete in procedure PROCEDURE-NAME because a response code of RESPONSE-CODE with reason code REASON-CODE was received from the bidirectional data conversion module MODULE-NAME while processing element ELEMENT-NAME.

Explanation

XML to language structure conversion uses an external module to handle bidirectional data conversions.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Refer to the bidirectional data conversion module documentation for explanations of return codes.

IRZ0976S
Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because a response code of RESPONSE-CODE with reason code REASON-CODE was received from the bidirectional data conversion module MODULE-NAME while processing member MEMBER-NAME of language structure STRUCTURE-NAME.

Explanation

Language structure to XML conversion uses an external module to handle bidirectional data conversions.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Refer to the bidirectional data conversion module documentation for explanations of return codes.

IRZ0977S
Language Structure to XML conversion could not complete in procedure PROCEDURE-NAME because the length prefix in the language structure STRUCTURE-NAME specified a length of SPECIFIED-LENGTH bytes, which is less than the structure's minimum length of MINIMUM-LENGTH bytes.

Explanation

Language Structure to XML conversion detected that the length prefix of a language structure specified a length that is less than the minimum length of the structure. The minimum length of a language structure is computed as the sum of the bytes used by all subordinate fields.

System action

The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

System programmer response

Correctly set the 2-byte length prefix of each language structure in the language structure buffer.

IRZ1000S
CEEGTST failed in Compiled XML Conversion module MODULE-NAME with message number MESSAGE-NUMBER when attempting to allocate COUNT-BYTES bytes of storage for STORAGE-USAGE.

Explanation

The Compiled XML Conversion module cited in this message encountered an error when it attempted to allocate storage by using the Language Environment CEEGTST callable service.

System action

The module either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

Programmer response

Increase the amount of storage available to Compiled XML Conversion by increasing the maximum size of the region in which the module runs.
IRZ1001S
CEEFRST failed in Compiled XML Conversion module MODULE-NAME with message number when attempting to free storage for STORAGE-USAGE located at address STORAGE-ADDRESS.

Explanation

The Compiled XML Conversion module cited in this message was unable to free storage by using the Language Environment CEEFRST callable service.

System action

The module either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

Programmer response

Ensure that all pointers and associated lengths that are supplied to the Compiled XML Conversion module mentioned in the message are valid. Additionally, check for and correct any storage allocation failures that might occur before the raising of this condition.
IRZ1002S
CUNLCNV failed in Compiled XML Conversion module MODULE-NAME with return code RETURN-CODE and reason code REASON-CODE when attempting to convert from CCSID FROM-CCSID to CCSID TO-CCSID.

Explanation

The Compiled XML Conversion module cited in this message encountered an error when it used z/OS unicode services character conversion service CUNLCNV to convert a code page.

System action

The module either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.

Programmer response

Determine the cause of the error by looking up the return and reason codes in the z/OS Unicode Services User's Guide and Reference.

Notices for IBM Rational Developer for z Systems documentation

Copyright IBM Corporation - 2009, 2014

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Programming interfaces: Intended programming interfaces allow the customer to write programs to obtain the services of Rational Developer for z Systems.

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
3-2-12, Roppongi, Minato-ku, Tokyo 106-8711 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Intellectual Property Dept. for Rational Software
IBM Corporation
20 Maguire Road
Lexington, Massachusetts 02421-3112
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

Copyright license

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Trademark acknowledgments

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Other product and service names might be trademarks of IBM or other companies.


Feedback