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

Note
Ninth edition (December 2015)
About this book
- Who should read this book
Client messages
Host and runtime messages
Notices for IBM Rational Developer for z Systems documentation

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.

{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

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.

Explanation

{0}: name of the generated symbolic map

{1}: name of the MVS™ subproject

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

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

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.

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

{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

{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.

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

Restart the workbench with the -clean flag.

CRRZC1304E

Problems loading configuration for '{0}'

Explanation

{0}: 0

{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.

{0}: 0
{1}: 1

{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.

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

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.

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

{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.

Explanation

{0}: host name
{1}: error number
{2}: error message

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

{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

{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

{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.

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

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

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*)¹
CRRZX0047E-CRRZX0132E: Messages that are displayed by the single-service project tools

¹WebSphere 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:

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

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:

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.
See the online help for the CICS Resource Definition server reason code and the CICS RESP2 code for steps to resolve the error:
- CICS Resource definition server reason codes: CRRZA1400E - CRRZA1469E
- CICS response 2 (RESP2) codes: CRRZA1200E - CRRZA1211E

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.

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

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

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:

Specify a valid value for the generation property in the generation properties file for the flow.
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

Provide the missing value and run the Generate Runtime Code wizard again.
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:

Open the referenced screen message in the screen messages editor.
Select the Screen Descriptions tab.
Expand the relevant screen description.
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.
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:

Specify a valid message for the node.
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:

Use the flow message editor to open the message file that contains the message.
In the editor area, select the Properties tab.
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.
In the editor area, in the Properties Hierarchy, select Logical properties > Value Constraints.
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.

{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

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.
Re-record the service flow.

CRRZE7334E

An error occurred during Web service generation in {0}: {1}

Explanation

{0}: Method name
{1}: Error message

{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:

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.
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:

Rename and refactor the field in the message.
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:

Rename and refactor one of the messages.
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:

Select the flow node that is specified in the error message.
Calculate the maximum length that is required for the COMMAREA that is passed to the program specified in the Link to Program Name field.
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

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

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

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

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

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.
Resolve any errors or warning messages that are shown in the Problems view.
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

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

{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).

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.

To verify that the file was allocated properly, locate the file in the Remote Systems view by expanding the MVS Files subsystem in the remote system connection.

To verify that the SYSLIB is specified correctly, do these steps:

Edit the property group associated with the resource.
Click the Assembler tab in the property group editor.
Expand the procedure, select the step name, and click Edit in the Step Options area of the page.
Verify that the data sets specified in the Macro Libraries field is correct.

To verify that the SYSLIB is specified correctly, do these steps:

Edit the property group associated with the resource.
Click the PL/I tab in the property group editor and then select Procedures and Steps.
Expand the procedure, select the step name, and click Edit in the Step Options area of the page.
Verify that the data sets specified in the Include Libraries field is correct.

CRRZI0027E

The include file could not be opened. Connect to the system before attempting this action.

Explanation

An attempt was made to open an include file by using the Open Include File action. The file cannot be opened because the remote system on which it is located is not connected.

User response

To connect to the remote system, open the Remote Systems view, select the remote system connection, and click Connect on the menu.

CRRZI0029I

Local syntax check of a remote file is available only if the file is opened or edited from an MVS subproject.

Explanation

Attention: Local syntax check is deprecated.

An attempt was made to run a local syntax check on a file that was opened for editing from the Remote Systems view.

User response

Close the current edit session.
Add the file to an MVS subproject.
Try the local syntax check request again.

CRRZI0030W

The file cannot be saved. Do you want to check the syntax on the last saved copy of this file?

Explanation

Attention: Local syntax check is deprecated.

An error occurred while accessing the contents of a remote resource in a z/OS project.

User response

Check the connection to determine whether the project is an online project and then try the operation again.
Clear the remote system cache files by selecting Window > Preferences > Remote Systems > File Cache > Clear Cached Files, and then try the operation again.
Re-create the project.

Contact your system administrator.

CRRZI0054E

An I/O error occurred while loading the host-based project definition file: '{0}'.

Explanation

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

The JES subsystem is not connected.

User response

In the Remote Systems view, locate the remote system on which the resource you are working with is located. Expand the remote system connection, select JES, and then click Connect on the menu.

CRRZI0075E

The submitted job has ended abnormally.

Explanation

A submitted job ended abnormally. This message also includes the following message text:Click {0} to view the job output or click {1} to view the build properties currently in use.In this message {0} is a link to the job output and {1} is a link to the property group associated with the resource.

User response

To check the job output, click the job output link. To check the build properties for the resource, click the property group link.

CRRZI0076E

The submitted job ended with a JCL error.

Explanation

The submitted job failed because of a JCL error. This message also includes the following message text:

Click {0} to view the job output or click {1} 
to view the build properties currently in use.

In this message {0} is a link to the job output and {1} is a link to the property group associated with the resource.

User response

To check the job output, click the job output link. To check the build properties for the resource, click the property group link.

CRRZI0077W

The operation has been canceled on the workstation. The job {0} might need to be purged from JES.

Explanation

The execution of a job submission action was canceled.

User response

To purge the job, do these steps:

In the Remote Systems view, locate the remote system on which the resource you are working with is located.
Expand the remote system connection and then expand JES > My Jobs.
Select the job name indicated in the message and then select Purge from the menu.

CRRZI0078E

There is no property group associated with the subproject '{0}'. Associate a property group with the subproject and try the operation again.

Explanation

While running a build request for a subproject, the system detected that no property group is associated with the subproject. A property group is required to build a subproject. In this message, {0} is the subproject name.

User response

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

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

CRRZI0149E

Termination failed

Explanation

During a request to rename or delete a file, the termination operation failed.

Diagnosing the problem

Left-click the destination data set. Look at the Property view (the two-column table with headings Property and Value). Expand the Mapping property. You must see Transfer Binary in both the source data set and the destination data set.
This feature requires the client and server to be at least at version 8.0.1.

Solving the problem

If the destination data set is Transfer Text, change it to Transfer Binary by doing one of the following actions:

For a single file:
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

CRRZI0196E

Unable to rename file

Explanation

A request to rename a data set failed.

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.

User response

Determine whether there is a resource shortage and 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). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.

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.

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.

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

CRRZI0344E

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.

Verify memory usage and increase the memory heap size.

CRRZI0366E

Code page conversion failed with {0}.

Explanation

{0}: The name of the function for which the code page conversion failed.

User response

CRRZI0367E

Code page {0} is not supported.

Explanation

{0}: The unsupported code page.

An unexpected internal server error occurred.

User response

CRRZI0378E

Exception occurred.

Explanation

An unexpected server error occurred.

User response

CRRZI0379E

The request has timed out because there is no response from the server.

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

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

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.

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

{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

{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

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.

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

User response

Click Yes to accept the updates or No to leave your property groups unchanged.

CRRZI0450E

The check dependencies operation could not be performed. See details for more information.

Explanation

A Check Dependencies request was made, but could not be completed.

User response

For more information about the errors that occurred during this operation, click Details.

CRRZI0451E

Copying a partitioned data set or folder is not supported.

Explanation

This message displays in response to an attempt to copy a folder or a partitioned data set into an MVS subproject by dragging it.

User response

To copy the contents from a source folder or partitioned data set into an MVS subproject:

Create a partitioned data set in the MVS subproject.
Copy the members from the source folder or partitioned data set.
Paste the members into the new partitioned data set.

In the Remote Systems view, locate the remote system on which the DB2 table you are working with is located.
Expand the remote system connection and then expand JES > My Jobs.
Look for the job name indicated in the message and expand it to see the job output.

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

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

CRRZI0480E

The system {0} is not connected. Connect to the system and try again.

Explanation

{0}: The name of a remote system.

Data set validation for a property group requires a connection to a remote system.

User response

Connect to the remote system and try the operation again. To connect to the remote system:

On the Information page of the property group editor, identify the system that the property group belongs to.
To connect to the system, locate the system in the Remote Systems view, right click, and select Connect.

CRRZI0481E

There is no name for the property group.

Explanation

During a property group create operation, the property group name was found to be missing.

User response

Specify a name for the property group on the Property Group Information page and try saving the property group again.

CRRZI0483E

While synchronizing changes to the sandbox resource {1}, a delete operation for the shared resource {0} failed. The resource is not synchronized. Resolve the error described below and share the sandbox or reload the shared resource.

Explanation

{0}: Resource name
{1}: Resource name

CRRZI0484E

While synchronizing changes resulting from a request to rename the sandbox from {1} to {2}, the rename operation for the shared resource {0} failed. The resource is not synchronized. Resolve the error described below and share the sandbox or reload the shared resource.

Explanation

{0}: Resource name
{1}: Sandbox name
{2}: Sandbox name

CRRZI0485E

The editor contains characters that cannot be transferred correctly between the local and remote systems. Saving the file on the remote system will cause these characters to become corrupted. Do you want to continue?

Explanation

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

{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

{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

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

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.

Edit the property group associated with the resource.
Select the category appropriate for the resource type: Assembler, COBOL, or PL/I.
In the Procedure and Step Table, click a step name to display the step options.
Select the Support Error Feedback check box.

CRRZI0515W

The file '{0}' contains characters that cannot be transferred correctly between the local and remote systems. This file will be opened in read-only mode. Do you want to continue?

Explanation

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 copy command failed because the request to allocate a data set before the IEBCOPY command failed.

If you intend to export to a different primary system, no action is required. You can continue with the export action.

If you did not intend to export to a different system:

Cancel the current export action.
Disconnect from primary system {1}.
Connect to primary system {0}.
Try the export action again.

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.

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.

CRRZI0561E

The specified remote system {0} is unknown.

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.

{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.

{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.

{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.

{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.

{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.

Attention: The work offline and work online operations for a remote resource are deprecated.

{0}: The name of a remote resource.

A problem occurred during the download action of a work online operation. A local copy of the resource cannot be created in the offline project.

User response

No action is required.

CRRZI0672W

Unable to migrate property {0}.

Explanation

Attention: The work offline and work online operations for a remote resource are deprecated.

{0}: The name of a property in a property group.

As part of a work offline operation, all the selected remote resources are downloaded to a local project and all the properties that are associated with the remote resource are migrated to the local resource. An error occurred while the operation was migrating a property.

User response

Check the property for which the migration failed and make sure to set it before you run operations like syntax check, which uses the properties of the local resource.

CRRZI0673W

Any non-uploaded changes will be lost. Are you sure you want to continue?

Explanation

Attention: The work offline and work online operations for a remote resource are deprecated.

Before you take a project online by using the Work Online action, you must upload the changes that you made to the resources when the project was offline. If you click Work Online without uploading the changes that were made locally (while the project was offline), the changes are lost. You must confirm that the work online operation can continue, which causes the local changes to be lost.

User response

Before you click Work Online, upload any changes that you made to the resources when the project was offline.
To upload any changes that you made while the project was offline, select them in the Changes view and then select Upload from the menu.
After you upload all the changes that you want to save, click Work Online.

CRRZI0674W

At least one of the values of your SYSLIB or local compiler options has changed since the project was taken offline. These changes will be lost when the project is online. Click OK to continue, or click Cancel to return to the wizard.

Explanation

When a project is offline, the resources on the remote system are still accessible to others. You must merge your changes with any changes other users made to resources.

User response

To upload and changes that you made while the project was offline, select them in the Changes and then select Upload from the menu. After you upload all the changes you want to save, click Work Online.

CRRZI0675W

Failed to upload {0}.

Explanation

{0}: The name of a local resource.

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

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

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.

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

Click Yes to continue expanding the filter or No to cancel the operation. To change the warning threshold:

To open the MVS Files preferences page, select Window > Preferences and then expand Remote Systems > z/OS and click MVS Files.
Type a number in the Default expansion page size for filters and data sets field.

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:

To open the container Properties window, do one of the following actions:
- Right-click the container and select Properties from the menu.
- Select the container and press Alt+Enter.
From the list on the left side of the Properties window, click Mapping.
In the Host code page area of the window, click Other and specify a host code page.

CRRZI0775E

Some characters cannot be mapped using local code page '{0}'. Either change the local code page or remove the characters which are not supported by the local code page '{0}'.

Explanation

{0}: The local code page.

This error occurs when you create or save a local or remote file that uses characters that are not supported by the local code page of the container.

User response

To modify the local code page property of a remote container:

To open the container Properties window, do one of the following actions:
- Right-click the container and select Properties from the menu.
- Select the container and press Alt+Enter.
From the list on the left side of the Properties window, click Mapping.
In the Local code page area of the window, click Other and specify a local code page.

To modify the local code page property of a local container:

To open the container Properties window, do one of the following actions:
- Right-click the container and select Properties from the menu.
- Select the container and press Alt+Enter.
From the list on the left side of the Properties window, click Resource.
In the Text file encoding area of the window, click Other and specify a local code page.

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.

{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.

{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.

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

Verify with your system administrator that the remote system is available and that the JES Job Monitor is installed and running.
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.

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.

{0}: A host code page.

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.

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

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 remote folder must exist before the bundle is transferred to z/OS.

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.

{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.

{0}: Represents a hyperlink on the z/OS Automated Unit Testing Framework Runner Configuration or Runner Results user interface.

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

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.
Verify or update the values that are specified in the zUnit category of the property group.
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:

In the Remote Systems view, expand the name of the remote system that is shown in the message.
Select JES.
Verify the connection status in the Properties view.
If the Connection field displays No, connect to the JES subsystem.
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:

In the Remote Systems view, retrieve the job that is identified in the message.
Select the job name.
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.

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

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.

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.

{0}: The file name of a converter program that imports file data.

{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.

{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

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:

Edit the property group that is associated with the resource.
On the Categories page of the property group, select JCL Job Card and Data Set.
Ensure that the JCL job card specified on the JCL page of the property group is valid for your site.

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.

{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.

{0}: The name of a variable.

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 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

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

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

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

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

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

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

{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

{1}: The content of the value

{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

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

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.

{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

{1}: The name of a TPF Make control file

{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

{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.

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

{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

{1}: The name of the item for which an invalid version was specified

User response

TPFC5101E

Specify a valid *.lsc file.

The lsc file must be a valid remote file.

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.

{1}: One of the following constants: Main, Locale, Iconv

{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

{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.

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

{1}: File name

{1}: File name

User response

TPFC5590E

Action failed. The selection is invalid.

You can only run this action on a z/OS UNIX subproject.

{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.

{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.

{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.

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.

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.

{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.

{1}: File name

{1}: The specified building block

{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

{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

{1}: The name of a rule group

{1}: File name

User response

TPFC6603I

The specified file {1} is invalid. Please specify a file with a .xml extension.

Explanation

{1}: File name

{1}: The specified target environment

{1}: The name of an option set

{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.

User response

TPFC9207E

No hosts are in disconnected mode.

In order to upload changes, one or more systems must already be in disconnected mode.

User response

TPFC9599E

Error saving file {1}

Explanation

{1}: File name

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.

User response

TPFR1010E

Empty input could not be used to locate any files or folders.

Explanation

User response

TPFR1011E

File name cannot be empty.

User response

TPFR3002E

No fields included.

Select one or more fields to be written to the output file.

TPFR6063E

{1}: The name of a folder to be created
{2}: The name of a folder

{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

TPFR8035E

Folder name cannot be empty.

Enter a folder name.

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

{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

{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

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.

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

{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.

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.

Host messages for Application Deployment Manager

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.

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

{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.

{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:

Disconnect from the CARMA connection.
Right click the disconnected CARMA connection, and select Properties.
In the Remote Locale menu, select a locale that is supported by the RAM.

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 member was not successfully created.

User response

In the client, attempt to do the following steps:

Refresh the parent container and confirm that the member is not already present.
Disconnect, reconnect, and try the create the member again.
Try to create a different member under a different container.

{0}: the VSAM record name

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.

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:

Verify that the path of the property group file is specified correctly in the input data.
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.
Verify that the include file specified in the error message exists in the specified directory, and that the user has permission to access it.
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:

Verify that the path of the property group file is specified correctly in the input data.
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.
Verify that the copybook specified in the error message exists in the specified directory, and that the user has permission to access it.
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

Verify that the path of the z/OS File System Mapping file is specified correctly in the input data.
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.
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

Verify that the property group file is a properly formatted XML file and that the user has permission to access it.
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

Verify that the property group file is a properly formatted XML file and that the user has permission to access it.
If the problem persists, export the property group file again and upload it to z/OS UNIX System Services.
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:

Verify that the path of the workspace is specified correctly in the input data.
Verify that the workspace exists and that the user has permission to access it.
Try the operation again.
Check the workspace log for errors.
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

Verify that the path of the custom rule and categories file is specified correctly in the input data.
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.
If the problem persists, export the custom rules and categories 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

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.

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.

{0}: A user ID.

{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.

{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 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:

BookManager® format:
PDF format:
- z/OS V1R10.0 Language Environment Run-Time Messages (SA22-7566-09)

Notices for IBM Rational Developer for z Systems documentation

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